topic Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery. in XPERIA archive

[MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Evangeder — Fri, 29 May 2015 17:37:17 GMT

I know how to fix the bootloop, but that will destroy all my internal data. And i don't want that.

The internal and SD drives are invisible to my PC. Windows do see the drives and installs drivers for them, but that's all.

They do not show up at My Computer screen, but the E:\ drive shows up at Device Manager.

USB drive is recognized as: SEMC Mass Storage USB Device.

When i want to access it using windows command line, it shows me that: " Device is not ready".

PC Companion does recognize the phone as MT11, and it shows the popup "yeah, there's an android device plugged in there", but the main screen still shows up: "There aren't any tablet/phone plugged into PC".

How do i access internal memory? I need to backup the application data (mostly the google authenticator), and everything else can be trashed. I also heard that deleting application cache and bluetooth folder helps to get out of the bootloop... but as i said, i cannot access the internal (nor external) memory.

The phone itself is rebooting as soon as it gets to XPERIA logo.

Sony -> XPERIA -> Blackscreen -> Sony -> XPERIA -> Blackscreen... repeat.

Holding volume down makes the vibration but the phone restarts anyways. So that won't help with anything. PC Companion wants to format my internal phone drive so big NO NO for that.

Any help?

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Uliwooly — Fri, 29 May 2015 17:44:50 GMT

@Evangeder

You could try by removing both the SIM and SD cards, if that doesn't work you could boot on safe mode but I doubt it'll go that far.

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Evangeder — Fri, 29 May 2015 17:50:13 GMT

I just said that safe mode does not work.

It's the bluetooth that caused the bootloop. After enabling it phone just died and started to restart everytime it went to XPERIA logo screen.

It goes just that far and restarts again. Even if safe mode turns in (because vibrations) - it still restarts.

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Uliwooly — Fri, 29 May 2015 17:55:28 GMT

@Evangeder

I'm sorry to say this, but you won't be able to recover your data

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Evangeder — Fri, 29 May 2015 17:59:54 GMT

Then how the people who repair phones for money can do that.

I know that there's one way, but it requires to mess with circuits in order to show up the internal phone storage to the PC.

I have no idea how to do this, but i heard i have connect battery to golden dot below black void label. Anyone knows how to do that?

The tutorial was in spanish when i've seen it, so i didn't understand what the guy was doing.. i'll try to find it.

Edit: ...is not a bad word, that censorship, lol

Edit2: found it, https://www.youtube.com/watch?v=6n6nmWjewdk

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Uliwooly — Fri, 29 May 2015 18:08:41 GMT

Good luck

Edit: the video is to unlock the bootloader, your issue its a bootloop

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Evangeder — Fri, 29 May 2015 18:10:39 GMT

Thanks, but i asked if anyone know how does this work and how do i do that in a way that doesn't destroy my phone :x

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Uliwooly — Fri, 29 May 2015 18:13:31 GMT

@Evangeder

Have you unlocked the bootloader?

Have you flash any Custom ROM?

Have you rooted your phone?

Could you elaborate on how the bluetooth cause this?

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Uliwooly — Fri, 29 May 2015 18:14:49 GMT

@Evangeder

You could check the XDA Forum or Google

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Thommo — Fri, 29 May 2015 18:23:12 GMT

People like me who know how and do fix phones can retain info but you will need a .ftf firmware file for your device and a program called flashtool then when you go to manually flash your phone you need to untick the boxes that say wipe data and cache

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Uliwooly — Fri, 29 May 2015 18:27:31 GMT

http://talk.sonymobile.com/t5/Xperia-arc-Xperia-arc-S/How-to-manually-update-2011-Xperias-to-android-4-0-build-number/td-p/158964

There you go

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Evangeder — Fri, 29 May 2015 18:31:25 GMT

I have found on the internet that this is a common problem with XPERIA's from 2011 year.

They sometimes randomly get stuck at bootloop after turning on the bluetooth option.

Some phones do manage to load to the lock screen, and then reboot. So it's possible to turn of bluetooth if you're lucky enough and it will stop rebooting.

My phone doesn't even want to go past XPERIA logo. I have no idea why is this a thing, but i lost my data 2nd time right now, and i'm probably never going to buy another XPERIA series phone. It could be everything. Everytime i enabled bluetooth it worked. Besides few months ago which this thing had happened. I used PC Companion to wipe my phone. Now this problem came back to me after the same action - turning on the bluetooth switch.

I managed to get QHSUSB_DLOAD device to appear in my computer, but there are no drivers for it, and i don't know what to do beyond this point. I'm polish, not spanish :x

I guess i gotta move to ye olde bricky 3310, at least there are no problems with phones from ~1999 year.

Edit: oh, okay, thanks! will definitely check that out

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Evangeder — Fri, 29 May 2015 19:06:18 GMT

29/005/2015 21:05:35 - INFO - Start Flashing
29/005/2015 21:05:35 - INFO - Processing loader.sin
29/005/2015 21:05:35 - INFO - Checking header
29/005/2015 21:05:35 - ERROR - Processing of loader.sin finished with errors.
29/005/2015 21:05:35 - INFO - Ending flash session
29/005/2015 21:05:36 - ERROR - Error in processHeader : 31 : Urządzenie dołączone do komputera nie działa.
29/005/2015 21:05:36 - ERROR - Error flashing. Aborted
29/005/2015 21:05:36 - INFO - Device connected in flash mode

"Urządzenie dołączone do komputera nie działa." means "Device connected to the computer does not work"

Meh, i give up. I'll just throw this phone to a trashcan.

Re: [MT11 / Neo V] Enabling bluetooth caused bootloop brick. Can't access recovery.

Thommo — Fri, 29 May 2015 19:33:55 GMT

Error In Processheader 31 and other critical errors can occur when your Windows operating system becomes corrupted. There can be numerous causes of this error including excessive startup entries, registry errors, hardware/RAM decline, fragmented files, unnecessary or redundant program installations and so on.