I have loaded and reloaded many ROMs and always end up in a boot loop. I can get the ROM loaded and fully configure the device but eventually I will find myself in a boot loop after a reboot. I did load and use Vagan 5.1 for a long time but decided to try try Gingeredition. Yes I have restored to factory using NVflash everytime.
Sounds like a conflict between a 1.1 and 1.2 to me.
Related
Long story, but here goes...
About a week ago I turned off my Droid. When I attempted to turn it back on it got stuck at the Motorola logo screen. After a few minutes it would reboot and do the same over and over. I had never rooted or done anything custom to the phone at any point. It was 100% stock original. Nothing had changed recently to suddenly cause an issue, no new apps or anything. I spoke with Verizon about it and they walked me through the process of attempting to boot to the recovery screen. During this call we found that I could not even boot to the recovery screen. I am outside of the warranty and inside of my renewal date.
Since I don't intend to pay for a new one I decided to try to fix it myself. My first attempt was simply to get to a point that I could boot to recovery. I flashed the phone with SPRecovery and sure enough I was able to boot to recovery. I then attempted to flash it with 2.2 and ended up back in the same situation with the boot loop. During all of this I noted that the Bootloader version was 2C.7C.
I then decided to go back to the SPRecovery/rooted configuration and attempted to load a custom ROM from Liquid. This also failed.
My next train of thought was to flash back to an older version of the Droid OS. I chose to flash to VZW_A855_ESD56_QSC6085BP_C_01.3E.01P_SW_UPDATE_03. Low and behold, that worked and the phone booted up and ran fine. It immediately updated to 2.1 update 1. I noticed after this flash that I was on Bootloader version 2C.6C.
Shortly afterwards I was prompted to install the OTA 2.2 update. After accepting and installing I was back to having a bricked phone. This was through the OTA update. Nothing I did or forced.
So basically, I can flash the phone back to VZW_A855_ESD56_QSC6085BP_C_01.3E.01P_SW_UPDATE_03 again and it works fine. But the second it tries to install the 2.2 OTA update or if I attempt to flash to the 2.2 image it gets stuck in the loop.
Notes that may be important:
1. I get the "E:Can't open /cache/recovery/command" error when I am able to get into recovery.
2. I have been sure to wipe data, cache, etc and formatted the SD Card through the phone OS when possible.
3. I use Ubuntu to flash the phone as it seems more stable and easier for my preference (I like Linux commands )
Any help would be greatly appreciated!!
I'm also stock in a bootloop, lost count already...
flashed b3 virus rom and whenever i boots up ithe android process forces closes and it reboots it boot loops on my htc evo i wiped everything so i dont understand why i got the boot loop
And what you want from us? If you got bootloop you just need to restore your backup(if you have) or flash new rom.
P.S.
Before doing something try to fix uid mismatches from recovery. It rather doesn't help but who knows.
When I flash merely anything, my tablet gets stuck on the Samsung boot logo (I have waited, and waited, and waited, until the battery dies). Sometimes even installing ClockWorkMod Recovery (official) will do this. But I managed to get the latest official CWM flashed. But I can't get ANY other rom to work. Even roms I have successfully flashed before.
Note: If it flashes it gets stuck at the Samsung boot logo. But I have also had it not flash sometimes too, giving me error code 7 in CWM which is an authentication/permission/certificate problem.
I am going to try right now using Odin to flash to stock, and work from there, maybe it will completely clean out any crap in the memory.
My tablet is the P3113 model.
Ok! So after flashing stock rom, then cleaning all the cache stuff, then attempting to install CM it fails with CWM Error code 7. And when I just reboot system, it gets stuck at the boot logo. Damn, I get stuck there without even flashing!!
Well, I may have figured it out..... ummm i guess *cough! cough!* I somehow changed kernels *cough! cough!* dang, my allergies! Hahaha, anyways, I flashed a kernel compatible with stock rom and cm10.1 and it has gotten past the flash of cm10.1 and seems to be booting up right now.
Ok, so my OPO got into a boot loop. I was running latest SlimKat weekly when suddenly during web browsing session the device rebooted itself and got into a boot loop. Well then I booted into TWRP recovery and wiped all the caches (cache, dalvik) and still no use. Then I did a factory reset and still I got a boot loop. Next thing I installed latest 3 SlimKat weeklys (had them on sd card) with factory resets between them and still the boot loop was there. Then the next few hours I spent installing stock roms from fastboot (22R, 25R, 30O, 33R) and still all I got was the boot loop.
Next morning I booted the device to recovery and did a factory reset and restarted (with 30O rom inside this time). Suddenly the device booted all the way to the Android and I was able to install few apps. Then I installed Whatsapp and launched the app. After the SMS confirmation the device rebooted again and proceeded to a boot loop. I turned the device off and let it settle for about 10 minutes. Then I booted in to the recovery and did the factory reset again and was able to boot all the way to the home screen again! Then after some more app installations came the reboot and boot loop.
Since then I haven't got past the boot animation.
In short terms:
- Was running latest SlimKat weekly
- Reboot and boot loop during normal web browsing
- Did factory reset, didn't help
- Installed stock roms from fastboot (22R, 25R, 30O, 33R), didn't help
What is your opinion? Could there be some hardware issue causing the reboot?
Video: https://www.youtube.com/watch?v=ChC58GHbSW4&list=UUHbkAIAVULcCb2pGa2lKIiQ
Sometimes device reboots before the actual CM boot animation, sometimes it reboots during the CM boot animation (usually straight after factory reset or flash from fastboot).
I think the hardware is faulty. I got my device to boot with the official AOSP rom and I even managed to install few apps. The device always reboots or completely shuts down when there is something more intensive going on, like downloading file from web site and installing app at the same time. I will try to investigate cpu and battery temperatures after work today.
I accidentally (don't ask) wiped my system while trying to install cyanogenmod. After doing that CM seemed to finally successfully install but it was stuck at a bootloop. I went back into recovery to restore my backup but it resulted in an error the first time. I tried it again and it said it was successful. I tried booting that up but the boot logo looked different than before and it wouldn't boot. It wasn't a bootloop but it was stuck on the boot logo. After trying a few more different things nothing worked and I decided to flash the stock firmware back. When I tried RSDlite failed the flashing process. Maybe I don't have the right firmware for my phone or something. I can't figure it out. I'd really appreciate anyone input on this. I need to get my phone up and going again as soon as possible. It's a Droid Maxx. It's not the Dev Edition but it does have an unlocked bootloader.
Thanks
EDIT:
I tried flashing that firmware again and for some reason it worked the second time. This thread can be deleted.
If you find it wont boot past the CM bootanimation, go back to recovery and Factory Reset - that normally will get it to complete the boot process. Make a backup first so you can easily restore back if you choose. Beats RSD back to stock and starting over...
I also run an unlocked Droid Maxx, non dev, currently on AICP ROM or CM, whatever flavor I feel like and who is updating their ROM the most often.