Hey guys, tried flashing the newest nightlies to my phone this morning the file was produced on 2-28. I made a backup, rebooted, returned to recovery, then installed the update zip and rebooted. Once I did this somehow I was stuck in boot loop. I let the phone go for 5 minutes with the same result so turned it off and back on and still would not come out of the boot loop. Has anyone else had this issue? Is there something I am missing? I did apply this nightly as an "update zip" in the sense that I didn't wipe or clear caches. If anyone has any thoughts on this feel free to let me know, I would like to keep up with the nightlies .
coltlacey1 said:
Hey guys, tried flashing the newest nightlies to my phone this morning the file was produced on 2-28. I made a backup, rebooted, returned to recovery, then installed the update zip and rebooted. Once I did this somehow I was stuck in boot loop. I let the phone go for 5 minutes with the same result so turned it off and back on and still would not come out of the boot loop. Has anyone else had this issue? Is there something I am missing? I did apply this nightly as an "update zip" in the sense that I didn't wipe or clear caches. If anyone has any thoughts on this feel free to let me know, I would like to keep up with the nightlies .
Click to expand...
Click to collapse
Jep. The 20130228 fails to boot. You're not the only one who's stuck in a bootloop.
Just flash today's nightly (20130301) and everything should work again.
Thanks for they reply man
Related
I tried to install Cognition 1.5.1 zip which CWM4 showed as successful, but am running into a problem of constant reboots to recovery. I wiped data and cache before installing the zip too. If i try to select power off it just reboots back into recovery. pulled battery turned phone on still goes recovery. any suggestions?
Edit: ended up going download mode and flashing base KH3, still could use suggestions on what to do to avoid it happening again.
Bmmaximus said:
I tried to install Cognition 1.5.1 zip which CWM4 showed as successful, but am running into a problem of constant reboots to recovery. I wiped data and cache before installing the zip too. If i try to select power off it just reboots back into recovery. pulled battery turned phone on still goes recovery. any suggestions?
Edit: ended up going download mode and flashing base KH3, still could use suggestions on what to do to avoid it happening again.
Click to expand...
Click to collapse
its nothing major mate once u restored/reflashed to make it work again. it could be corrupted flash that coudlnt let u boot. thanks god u are back on track..
Try reading the sticky.
Ya i figured out how to get it to boot properly, so is the problem with the download of the rom? Cuz it did the boot loop both times i flashed the rom. Would redownloading the file work?
ok im stock with no nvflash backup need help with bootloop.
tried to clear cache rebooted, loop still there.
restored, loop still there.
reapplied latest update, loop still there(recover doesnt come up now just update indicator.).
help please.
thanks in advance for any assitance.
love this forum.
ps: have rma want to try to fix personaly first.
also will be installing vegan or cyanogen on it when fixed.
update
nv flashed and got it booting.
other threads helped alot
update:2
new update i can get it to boot but if i install anything it gets stuck.
Installed latest CM10 nightly. Now just sits at boot animation. Attempted to restore. Backups gone. All other ROMS gone for SD card. Can get into recovery, but am lost at that point. Tried clearing cache several times through fastboot. Have no clue how to use adb to sideload. Rate myself as an almost noob. Any help appreciated.
johnpius said:
Installed latest CM10 nightly. Now just sits at boot animation. Attempted to restore. Backups gone. All other ROMS gone for SD card. Can get into recovery, but am lost at that point. Tried clearing cache several times through fastboot. Have no clue how to use adb to sideload. Rate myself as an almost noob. Any help appreciated.
Click to expand...
Click to collapse
I'm in the same boat, stuck at the CM boot animation. How did you get back to recovery? I hold the power button and the home and back buttons flash and that's it.
Edit: The whole "hold the phone up to a bright light while holding the power button" trick did the job. I was flashing from Android Revolution to CM10.1 and I did perform a factory reset and sideloaded CM through CWM. After another wipe everything worked out fine.
Are you coming from another rom? If so, did you factory reset after flashing ?
cschmitt said:
Are you coming from another rom? If so, did you factory reset after flashing ?
Click to expand...
Click to collapse
Im assuming based on his post he is not coming from another rom and has been flashing CM nightlies regularly and this latest flash was done per routine but is not working for some reason.
I updated the latest 6-23 nightly and its working fine so far, sorry to hear about your issues.
Sent from my Nexus 7 using Tapatalk 2
I dirty flashed the latest nightly as well, no issues.
I've been having a problem getting any 4.3 ROM to boot after the initial boot. I've seen a few other people with the same problem and I can't figure out a fix. Thought I'd ask the general Q&A.
I've used Beanstalk and Carbon (great ROMs) a few carbon 4.3 nightlies and Beanstalk 4.3.00. I installed their 4.3 builds (after checking sums to verify download) flash gapps, wipe cahce/dalvik and boot up. Set up goes great and rom runs great. but even without installing any other apps, using no backups or anything if I reboot it sticks on samsung screen and can't get past it. Every time, I even rebooted without finishing setup and wouldnt advance past samsung.
I even flashed 4.3 rom and gapps, let it reinstall apps from market then booted to recovery and made a backup. Then could'nt reboot. But if I wipe and restore the backup it will boot fine the 1 time, but again any attempts to reboot stick on samsung screen. Wiping cache/dalvik from recovery does not help, fix permissions from recovery does not help.
Anybody have this problem and find a fix?
Ok, I tried slim bean beta 2, no luck, tried ktoons kernel, no luck. Guess I'm staying with 4.2.2 until there is some movement on this issue.
I have been trying to upgrade from CM10.1 stable to CM10.2 stable. I am using CWM 6.0.2.9 internal. I originally flashed both CM10.2 and Gapps jb-20130813 and get stuck at a blank screen. I then restored to my 10.1 and used the CM updater to install 10.2. It came up fine but google apps were not working (gray internet connection instead of blue). I rebooted into recovery and flashed the 20130813 gapps zip file and once again was stuck at a blank screen. I tried clearing the cache and dalvik but it didn't seem to help. Am I using the wrong version of gapps or something?
mogators1 said:
I have been trying to upgrade from CM10.1 stable to CM10.2 stable. I am using CWM 6.0.2.9 internal. I originally flashed both CM10.2 and Gapps jb-20130813 and get stuck at a blank screen. I then restored to my 10.1 and used the CM updater to install 10.2. It came up fine but google apps were not working (gray internet connection instead of blue). I rebooted into recovery and flashed the 20130813 gapps zip file and once again was stuck at a blank screen. I tried clearing the cache and dalvik but it didn't seem to help. Am I using the wrong version of gapps or something?
Click to expand...
Click to collapse
I think I have it figured out. I posted the following in the developers section where others had been complaining of a similar issue:
mogators1 said:
Still not working for me. I went from CM10.1 stable and cleared cache and dalvik. I then flashed CM10.2 stable and the signed google apps (20130813). It booted the first time and wifi would not turn on. I rebooted to recovery and cleared cache's again and rebooted to a "black" screen. It's been sitting like that for over 10 minutes.
May have figured something out. After waiting a few more minutes, I plugged the Nook into my computer so that it could pull some charge while I continued to wait to see if anything happened. In less than a minute, I heard my computer make the sound it makes when something is plugged into the USB port. I looked over and saw the Nook was booting. I unplugged it and rebooted to see if it would boot this time. Still nothing, so I plugged in again and it booted shortly afterwards again. I noticed there was a status message saying that USB debugging was on. I turned that off and now have rebooted twice in a row without being connected to the PC. I think I'm good to go. Hopefully this will help someone else.
Click to expand...
Click to collapse