I've been trying to go from 5.7.893 to the official OTA 5.5.893, but I was unable to get it to flash properly. I went back to 5.7.893 but every time my phone boots it goes into the boot menu. I can obviously work around this easily, but it's inconvenient. Is there a fix for this so the Bionic will continue to boot into the OS again?
you can't downgrade from 5.7.893.
Does it go into the boot menu, or does it go to a flashboot screen that says across the very top (flash failed)?
Related
My out of the box Nexus 6 is now stuck looping on and off at the Google boot screen after it tried to install the system update.
I've used the toolkit 1.9.8 to go back to stock. It goes thru the steps appearing to show OKAY and finished at each step. It never reboots the phone at the end. I try to force reboot after waiting for several minutes and it still boot loops. I try again the process again and sometimes it loops and a few times it actually starts up to the welcome screen. However, if I try to root or update recovery (using the toolkit), I get the boot looping again.
Did google bork my phone during a failed update? Is there anything else I can do to completely restore the phone? I've also downloaded the images on google and flashed---same boot loop.
Ultimately, my phone is now booting up to the welcome screen as expected and shows LRX21O. BUT, if I try to do anything (root or recovery), boot loop results again.
(I was able to unlock the phone and know about the usb debug and OEM unlock settings in dev menu, fyi).
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.
Hi guys,
So I had a stock T-Mobile LG G4 H811 that I had unlocked and booted into twrp version 3.1.1-1-g4. I wasn't able to actually flash recovery of this .img becuase of a write failure. So I booted into it instead and then installed it from within twrp into the recovery partition. The actual stock software was the ORIGINAL original, which I think was android 5.1.1
From there, I cleared the cache and delvik cache and installed the G4-H811-10N-xTreme-2.0 Rom. Now, I can't boot into recovery mode anymore, and all I get is the bootloop.. but it's not dead yet because it's a software issue on my part and not a hardware failure.
Any advice on how to get it to recovery mode or at least so I can boot into twrp somehow to try and get this fixed? I tried Power+Volume Down and then let go a sec and Power+Vol Down again and it won't work at all. Just goes straight to bootloop.
Thanks in advance.. I know I screwed up somewhere.. just so many loopholes, it's easy to miss.
Best,
Johnnie
Got somewhere, still broke
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
jtlefebvre said:
Well, somehow I managed to boot into recovery mode only 1 time and installed the stock Tmobile rom. It installed, but now I get a white T-Mobile screen on boot up and it stays there. I tried using the LG Flash Tool 2014 and the stock T-Mobile H811 10N firmware for T-Mobile, but all I get is connection to server errors and the software won't install to the phone over download mode. Anyone else have this problem? I've been trying to figure this stupid thing out for 6 hours. Also, I'm wondering if installing the stock firmware caused the original recovery partition to go back to stock too which is the reason I'm no longer able to boot into recovery mode? It just doesn't recognize it. Power+vol down and then vol down doesn't do anything.
When using the LG Flash Tool 2014, all I get is Connection to Server Failed, Try again. So I do, and nothing. It fails at 9%
Thanks.
Click to expand...
Click to collapse
try using LGUP
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
ibphantom said:
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
Click to expand...
Click to collapse
Make sure you are using the latest adb/fastboot binaries (April, 2020). Flash the stock boot.img from the same guide. You will be unrooted but will be able to boot into System. Now read up on how to patch your own boot.img, it really is very simple. Personally I do not depend on, wait on, or use OTA's. The full image is available the first Monday of every month, and I extract/patch the boot.img from it. The whole operation including rooting takes just a few minutes. It's just one extra step. Once you get the pattern down it can be done very quickly, consistently and you're not depending on someone else's files. If you are bound and determined to use this method, you should seek out more guidance in the tutorial thread itself. Good luck. :good:
I was trying to flash a new rom couple days ago and I feel I did a mistake somewhere which led to an issue and I can't manually boot into recovery (I have tried reflashing recovery) when ever I try to boot into recovery or rom does it for Android updates it gets stuck in fastboot from here I can't turn on the phone, when ever I try to turn it on, it boots back into fastboot, the only way for me to actually get back into my device is by using a pc with fastboot boot recovery.img. It usually updates the rom and I can get back to my device from here. I've tried a couple of things but I'm not able to go to recovery without my pc. Suggest me some fixes that could possibly fix the phone
Thanks in advance