I believe when you update your phone to android 5.0 OTA the boot loader is also upgraded(I did this). I eventually ended up with no OS on my phone messing around with flashing things causing me to not be able to boot up. I was eventually able get stock OS back on but I still get stuck at the Motorola logo. I tried restoring my it in recovery mode and RSD lite. Is this because my boot loader version is to high for stock OS? I really am clueless on how I could fix this problem. Any help would be greatly appreciated.
Related
At&t xt1097 Android 5.0.2. While on the charger last night something happened and the phone stops loading at the att logo. I tried recovery, which is successfully goes through, but have the same issue on reboot.
Is there a way to repush the image 5.0.2 image to the phone using adb? Is that the best thing to try? If so anyone know where I can find the stock image?
Thanks much
Hi
I have an AT&T XT1058 with locked bootloader, on 4.4.4
I tried to rest it to factory, but it got stuck on 'Erasing...' (with the little droid) for more than an hour, so I reset it.
Since then it won't boot, only keep stuck on 'Erasing...'. I've tried reflashing it with ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF both using RSD lite and manually using mfastboot, but no luck - the phone still boots to 'Erasing...' and sometimes after that to the recovery.
I didn't find anything in relevant threads. Does anyone have an idea?
Selecting 'Factory' in the bootloader seemed to fix it.
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
mokagi said:
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
Click to expand...
Click to collapse
Were you able to get this resolved? I have a xt1095 doing the same thing when I flash a stock recovery. Just shows the android guy and just stuck at erasing... When I flash TWRP it doesn't get stuck at the "erasing..." anymore but just boots straight into TWRP.
Sorry for the late response, I missed the notification on your message.
I wasn't able to fix it, returned it to motorola.
Currently stuck on G900AUCU3BOC4 (LRX21T) and can't get anywhere. I've been stuck on the boot screen with the unlocked padlock but can't seem to find any way to unbrick. Since I'm on the OC4 bootloader, I understand that I can't downgrade. I already tried reflashing the kernel and stock partitions, but I'm still stuck on the boot screen. Any ideas? Thanks.
Same
Also have the same problem, anyone have any idea how to fix this problem?
same here olny gets samsung logo
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
I have a 5th gen Kindle (Kids Edition) that is bone stock. With the recent update it received to 5.6.2.0, it seems like it's stuck in this endless upgrade/downgrade loop. It runs 5.3.6.4, then it will upgrade to 5.6.2.0, reboot automatically. After awhile, it will download the 5.3.6.4 automatically to "upgrade" it, auto reboot to 5.3.x, then after awhile, it will find the 5.6.2.0 upgrade and upgrade it.
It seems to do this constantly and I can't figure out a way to get it out of this loop! I've reset it to factory, did the boot loader wiped the davlik, did a factory wipe/reset from there, and still nothing. The exact same thing.
I was hoping somebody could share a hint on how I can get this device out of the loop and back working normally again.
Thanks!