Hi guys,
I have been trying to unbrick my Turbo to get my pics back but not having any luck... hoping someone can help.
Background:
Bought this phone refurbished about 1 1/2 yrs ago and used Sunshine to unlock bootloader, installed TWRP, rooted, all was fine until last weekend. Battery was totally dead (battery icon wouldn't even show up with power button press). Plugged it in to charge and when I came back to it it was on the bootloader screen (robot lying down with his hatch opened). I can go to the Logs entry and it says 'Failed to validate boot image'. Any other option does nothing (except power off and Barcodes). Cannot boot into recovery. I can see phone info on bootloader screen along with "Device is UNLOCKED. Status Code: 3" "Software Status: Modified" but flashing has not helped.
Tried reflashing TWRP and stock Recovery and Boot with mfastboot, the phone seems to take them (no errors from mfastboot) but no change. I tried to flash the logo.bin from a stock image and the phone seemed to take it ok but after rebooting, the robot image and menu are gone (the text is still there... 'AP Fastboot Flash Mode (Secure)' with other info). The battery icon is also gone and all I see is 'static' when the low battery icon should be displayed attempting to power up with low battery. Same static seems to have replaced the 'Bootloader Unlocked' warning screen which flashed briefly before stopping on bootloader.
Are there any suggestions of how to get this phone back to life? I am really only concerned with getting the photos off (I already have a replacement; G5+). For some reason ADB does not see the phone. Any help would be appreciated!
Thanks
Hank
Related
My base state was after running all the instructions here: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Phone had been working fine in this state.(Rooted/locked bootloader) I also have a backup of the TA partition
With the new 5.0.2 release, I upgraded via instructions/files at http://forum.xda-developers.com/z3-compact/development/stock-firmware-23-1-0-690-generic-t3056413 with the addition of flashing 2.8.3 lockeddualrecovery
Phone was working fine on first boot and rebooted(as needed) a few times fine. However I then attempted to enable encryption(via settings->security). The phone began boot looping(which I assumed was normal) however it is now 20 hours later and it is still boot looping. Occasionally(1/30 reboots) the phone will show a padlock icon that will show a circular loading icon for a couple seconds and then reboot. I can get in to fastboot mode but can't seem to do anything since my bootloader is locked. Also cannot boot into recovery via any button combination. Attaching adb for logs never sees the device.
Bootloop: No led-> sony logo(red led) -> sony logo(no led) -> sony logo(orange led) -> dim "powered by android(orange led) -> reboot
Any suggestions? I can't send it to Sony for repair as it is a UK unit and I am in the US(Not worth paying another ~$100 in shipping plus whatever the repair cost will be). Warranty is already void and I can recover the TA, so I'm willing to try anything.
[edit] can also get phone into flash mode. however trying to flash generic D5803_23.0.1.A.5.77_US.ftf still causes boot loop
[edit2] fixed, this thread can be deleted. After flashtools "finished" the first time it wasn't really done and I needed to reattach the phone in flashmode again to finish. I'm now booting to the homescreen.
I understand you're glad to fixed the bootloop.
On the other hand the issue itself isn't fixed.
I believe encryption to be very valuable and I really want it to be fixed.
Anybody else has any ideas or succes combing root & encryption?
Hello guys,
I finally got this great phone but I'm having all kind of problems here.. missing my old samsung s3 mini
As said in the title I managed to unlock the bootloader but, for some strange and unknown reason, i decided to lock it back again. The problem is that I don't have a custom recovery or root.. but security is on (S-On).
While being in fastboot I've no problems with the fastboot "flash unlocktoken Unlock_code.bin" string. After I confirm that I want to unlock it, a quick white boot page with the HTC logo appears for a super short time and then it boots off showing a battery image and a blinking red light. (just to be clear; fix to this is to press volume up, volume down and power button for a while).
After the boot the bootloader is still locked.. or relocked I should say.
I'm thinking that -cause I'm also having some issues with battery heat, reaching easily 50celsius, and battery drain- the problem is the battery.
Do you have any idea of what to do? Having this phone and not being able to "make it mine" is slowly killing me.. day by day. So If you DO have any idea, please, please help me.
PS
if i unplug the phone after the fastboot flash string and, just after having it unplugged, confirm to unlock the bootloader, the phone just boot off -not having the red light problem tho-
Sorry if not clear.. not mother tongue ^^
No? Nothing I can do about this? Guess I'll keep everything on stock
XT1092 flashing (as in on screen flashing) recovery "no command" screen. Bricked?
Apparently I did something stupid. I had 5.1 which didn't OTA on its own to 6.0. So I thought it maybe had something to do with a past root i had and TWRP recovery. As solution I went and flashed a stock 5.1 rom in fastboot, which worked fine. Still no OTA though, and adb sideloading gave a status 7 error. Then I fastbooted the 6.0 stock rom, but that wouldn't boot (phone would hang in the white "unlocked bootloader" warning screen. I re-flashed 5.1 in fastboot.
Probably not a smart move, cause now I'm stuck in a bootloop to recovery mode where it's flashing the "no command" recovery screen for a fraction of a second, then black screen for 4 seconds, repeating over and over. I can trigger some orange log error by pressing VOL*UP like when you go to recovery mode, but it disappears in the bootloop. (it says qe 1/1 though, which suggests its rooted I read somewhere). So I can't do anything with it anymore. I read tons of threads here of which I found 2 with a similar problem:
http://forum.xda-developers.com/moto-x-2014/help/xt1092-flashing-command-boot-attempt-to-t3259287
http://forum.xda-developers.com/moto-x-2014/help/possibly-soft-bricked-moto-x-flashing-t3195103
It's the same problem I have now, and one of them says that "with some luck" he got into fastboot, but doesn't describe how.
Googling "flashing" related to recovery and/or "no command screen" in this context does'nt yield much result unfortunately.
For the love of god, I can't get it into fastboot mode anymore to do something/anything about it. I pressed, hold, tapped POWER and VOL*UP on countless ways, and it does a "deeper" reboot with appearance of the white unlocked bootloader screen, but it just keeps bootlooping.
How can I fix this? Did I brick it by fastboot flashing 6.0 and then fastboot flashing 5.1? Is it hard bricked and useless?
What do I have to flash when I manage to get in fastboot?
OK, I fixed it. Discovered it when the battery was drained. When the phone is OFF, holding POWER+VOL*UP+VOL*DOWN for 5 seconds and then releasing triggers the fastboot. Problem then is that you can't flash anything cause the battery is nerely depleted. So I let it charge in the bootloop for a bit and I found out I can hard reboot and get into fastboot by holding POWER+VOL*UP+VOL*DOWN for about 10 seconds and then releasing it. It probably turns off and then triggers the fastboot/bootloader mode.
Afraid of bricking it with OTA as I've downgraded to 5.1 from a (non-functioning) 6.0 I've manually flashed a 6.0 stock ROM in fastboot using this guide including mfastboot. So no sideloading or anything. Now it properly boots and I've got a stock 6.0.
Hopefully this helps someone in the future.
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.