Develop Bugs

Endless Boot Loop Gnex

I have been most recently running AOKP Milestone 6, and flashed to the JB build last night. I wiped, cleared cache, etc, and everything was fine; I went about restoring my apps and settings. My battery died shortly thereafter and now I'm stuck in an endless boot loop.
I tried restoring my backup, but still get the boot loop. I've even went as far as restoring my stock recovery of 4.0.3, but get "error restoring /data" when doing so.
How boned am I? I'd love to avoid going all the way back to factory settings and lose my data.
Any help is greatly appreciated.

Did you try to just reflash the ROM itself that you were using? If that doesn't work just wipe everything again and reinstall. If you have app backups it's no biggie.
Sent from my Galaxy Nexus using Tapatalk 2

codacrawford said:
I have been most recently running AOKP Milestone 6, and flashed to the JB build last night. I wiped, cleared cache, etc, and everything was fine; I went about restoring my apps and settings. My battery died shortly thereafter and now I'm stuck in an endless boot loop.
I tried restoring my backup, but still get the boot loop. I've even went as far as restoring my stock recovery of 4.0.3, but get "error restoring /data" when doing so.
How boned am I? I'd love to avoid going all the way back to factory settings and lose my data.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Did you flash a new bootloader or anything? Flashing the latest JB bootloader might help.

There's a thought that JB may run a file system check during the early boot phase in certain situations which is causing a lot of people to freak out because the phone stays at the Google splash screen for a long time. It's been reported that if you wait it out (can take up to tens of minutes) your phone should boot up normally.
I've myself have ran into this problem a few times but I've never tried waiting it out. What I've done is boot into CWM and use adb to pull the contents of my internal storage (/data/media) which includes my nandroid backups and then use "fastboot -w" to wipe the entire userdata partition. Afterwards I let the phone boot up to rebuild the userdata partition, copy my internal storage backup, and restore my nandroid backup.

silow said:
There's a thought that JB may run a file system check during the early boot phase in certain situations which is causing a lot of people to freak out because the phone stays at the Google splash screen for a long time. It's been reported that if you wait it out (can take up to tens of minutes) your phone should boot up normally.
I've myself have ran into this problem a few times but I've never tried waiting it out. What I've done is boot into CWM and use adb to pull the contents of my internal storage (/data/media) which includes my nandroid backups and then use "fastboot -w" to wipe the entire userdata partition. Afterwards I let the phone boot up to rebuild the userdata partition, copy my internal storage backup, and restore my nandroid backup.
Click to expand...
Click to collapse
I'm not stuck at the splash screen, it loops through the splash screen and the boot animation. Could you give me a little more detail on the process of pulling my data through adb?

Try this, wipe /system then reflash your old ROM again. Once that's flashed wipe davlik and cache and try a reboot. That should keep your data intact and just reload your old rom. Then you can renandroid and reflash.
Edit: just for safe measures makes sure you have any kernel software or tweaks disabled when you flash the new JB build. Of course if you are doing a clean install this won't matter. You just want to make sure things like overclocking or undervolting aren't crossong over to the new ROM, as say a 1.8 overclock might work on ICS kernel but not on a JB kernel. Hopefully that makes sense.
G-Nexus Sent

If all fails, use adb to pull all the important files, then use adb to push super wipe, and then flash it using your recovery. This will make sure that it wipes EVERYTHING. After that, just use adb to push Rom of your choice and then flash it.
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

codacrawford said:
I'm not stuck at the splash screen, it loops through the splash screen and the boot animation. Could you give me a little more detail on the process of pulling my data through adb?
Click to expand...
Click to collapse
1.) Boot into CWM
2.) Go to the "Mounts and Storage Menu" and "mount /data"
3.) Plug in your phone to the PC
4.) adb pull /data/media c:\gnex_sdcard_backup

[Q] Jelly Bean Boot Loop at Animation

I am stumped at my situation here. I just installed TWRP 2.3 recovery on my Kindle Fire and was looking to flash a Jelly Bean ROM to make my device more usable. I have tried flashing CM10, Jandycane, and AOSP ROMs. All of them I made sure to wipe/ do factory reset, and wipe dalvik and cache. On every rom it sits at the ROMs initial boot loop. In Jandycase and AOSP the colorful 3D triangles just spun in circles forever, and with CM10 the CM logo was just spinning for a long time. I let them do this 10 minutes and no change, it was stuck in a boot loop for sure.
I restored back to the default Kindle Fire ROM and that booted back up just fine.
I have tried to switch TWRP to rm -rf setting and I downgraded TWRP to 2.2.2.1 to see if those made any changes. They did not help, I am still getting bootloops from every ROM.
Does anyone else have any idea why I can't load a custom ROM?
Also- I did md5 checks and they passed on the ROMs.
Thanks!

Wipe factory reset, wipe cache, wipe dalvik, wipe system, flash rom.zip, flash gapps.zip reboot then system if prompted. Initial boot takes awhile.

I've done those steps in order multiple times and still the same result. I seriously can't figure this out.

Somewhere along the way your doing something wrong. Your not extracting the ROM and gapps are you? Because they are flashed in zip form. Try to overwrite your recovery again if you feel you are doing all the right things and try flashing this rom no gapps needed just a full wipe minus your external storage/sdcard not the altrom that's for dual boot http://forum.xda-developers.com/showthread.php?t=1439916 .
Just a thought reset twrp defaults you did say something about the rm -rf setting going back to traditional formatting would be better.

Restore to Default for TWRP settings worked!
Thank you!

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!

Stuck in boot loop after flashing CM7

Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...

You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.

[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!

Flashing any rom results in infinite boot

I have tried the roms below:
Pac-rom
LiquidSmooth
CyanogenMod 12.1
CyanogenMod 11
And the result is it always gets stuck at boot where the boot animation continues infinitely. I have gave it about 30 minutes to boot.
With LiquidSmooth I was able to run logcat, but CM12.1 I am not able to.
I have tried resetting system, data, caches in twrp and using the reset for new rom in philz.
I have tried flashing with both TWRP and Philz.
I am using the latest Philz and TWRP.
The only thing that has worked for me is samsung stock ROM, but I do not like the stock ROM.
Are there SPH-L900 phones you have to do something different?
Is there a way to get boot logs from CM12?
Am I doing something wrong?
See attachment from LiquidSmooth.

After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.

GRMrGecko said:
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
Click to expand...
Click to collapse
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks

Raziel10000 said:
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Click to expand...
Click to collapse
Followed this guide from some post I found after reading for 8 hours, LOL. Don't remember who it is from... It's for the Cyanide ROM but worked perfect for CM12.1 latest nightly with the latest GAPPs
1.) revert everything to stock
Using Odin3 v3.09 I first flashed this: L900VPUCNE2_L900SPTCNE2_SPR.zip
2.) Reboot and verify it's not bricked, then use ODIN to flash Philz philz_touch_6.15.4-l900.tar.md5
3.) Reboot into Philz recovery and follow these steps exactly
1. Mounts and Storage
Format / system
Format / cache
Format / data
Format / data and /data /media (/sdcard)
(note this isn't the EXTERNAL sdcard, on to which I had loaded the ROM, Shift and gapps)
2. Power Options > reboot recovery
3. Wipe cache partition
4. Advanced > Wipe dalvik cache
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
At one point Philz asked me if I wanted to root and I said yes.
3.) Flash (from the external sdcard) the ROM (Tablet style ROM found in OP "5.0.2-RC-7.1-tablet"), Then flash Shift (Shift-LP-4.3 other versions DID NOT WORK), then flash gapps (GApps-5.0.2-20150315-signed NO OTHER VERSION WOULD FLASH, got Error 20 every time) Here's the
After everything was flashed I rebooted and got stuck at boot animation AGAIN, so I rebooted into recovery and wiped cache. Just cache, not dalvik or user data, rebooted, and it worked.
Installed Netflix from appstore, when I logged in to netflix it asked me to update google play services (I've seen it do this on other devices as well). Updated google play services and went back to Netflix, chose a random show and tapped on it, stuck at "loading" screen. Rebooted phone, tried netflix again and it works.
This was a tough one! But it's working now and I've saved all these files in one place incase it bricks again. Now to install the Note 3/4 style faux-stitched-leather back cover I got off Amazon.
Thanks all!