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
Related
So I got Cm7 running using rom manager, used titanium backup to restore apps + system data, then fixed permissions. For the last 10 minutes it's been stuck in the CM7 screen....
What should I do? Can I pull the battery without harm? Does it take that long to boot after fixing permissions?
Edit: pulled the batter and am trying to boot into recovery...going to wipe the dalvik/cache again.
Edit2: same thing for the last 6 minutes....dang. I guess I'll just nandroid in 5 minutes if it doesn't' get out of it.
Edit3: going to nandroid back. I might try it again later flashing from a Zip instead of using rom manager. I probably won't restore system data either next time. If anyone has any suggestions though please post them.
Edit4: not good...phone is bootlooping cyangen screen after nandroid.
Edit5: Cleared factordata, cache, and when I go to clear dalvik I'm getting
e unknown volume for path sd-ext
Any ideas here?
Edit6: I'm reflashing 6.1.2....okay...got through the boot and now I'm setting up the phone.
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
housry23 said:
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
Click to expand...
Click to collapse
Will do....I know I had been installing apps to the SD card using CM6 and when I first got CM7 up it said my phone memory was low. I thought it would say on the SD card.
I'll probably try tomorrow again if I get the courage and I most definitely will DL Calkun's tools.
Thanks!
I'm going to guess the nandroid didn't work either because of the phone memory low issue?
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
teh roxxorz said:
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
Click to expand...
Click to collapse
Wiped manually, installed from zip, and didn't restore system data. CM7 has been running for about an hour now.
Thanks everyone!
Glad that you got it working man.
Is ANY system data safe to restore from Titanium?
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
phsteve said:
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
Click to expand...
Click to collapse
You should never restore system settings.
For contacts, open accounts and sync, tap your google account, then sync contacts, and that'll be done.
For texts, people highly recommend sms backup or my backup. Then backup apps and data, then restore only apps and data, and you'll be set.
I cannot get past the bootanimation screen. This just happened this morning out of the blue. It's been rooted since Dec, and been running fine since. I can get to recovery, but it just reboots and hangs from there on it's own. I'm using AOKP MS2, and FrancoKernel, which probably doesn't matter, but I just need to get this at least back to stock. What do you guys suggest? I have done a battery pull, entered recovery through fastboot, but it just won't boot up.
Since you can access recovery, just restore a nandroid backup. That will get your phone up and running again.
lonnyrs said:
I cannot get past the bootanimation screen. This just happened this morning out of the blue. It's been rooted since Dec, and been running fine since. I can get to recovery, but it just reboots and hangs from there on it's own. I'm using AOKP MS2, and FrancoKernel, which probably doesn't matter, but I just need to get this at least back to stock. What do you guys suggest? I have done a battery pull, entered recovery through fastboot, but it just won't boot up.
Click to expand...
Click to collapse
If you have a nandroid then flash that, if not you will have to wipe cache, system,dalvik and data and flash the rom again.
That should solve your problems.
Maybe try just wiping cache, dalvik and system and leave data alone and flash the rom again. That way all your apps etc will still be there.
If you get bootloops after that then full wipe and flash.
Can aokp m4 be flashed via fastboot? Not sure this is possible , anyone ever fastboot a custom rom? Or push it with fastboot and then flash it in cwm?
¢ £®0π π€XU$ |||
Hello,
My Galaxy Nexus went in to a boot loop for some reason on it's own, it's been working fine for the last few months (I'm on AOKP b24) but today during the middle of the day it just rebooted and then went in to a boot loop. No matter what I do, I can't get it to boot up without hard wiping it. I've pulled the battery for a while, charged it up etc but it's still stuck in the boot loop.
I can still get in to CWM, so that's the good news.
The BAD NEWS is that I don't know how pull my Titianium Backup files from the phone. I'm trying to use the Galaxy Nexus Toolkit, but when I go to option 15 to pull the files, it asks me if I'm running a custom ROM. I answer yes and then it asks me for a path. I've tried entering these: /sdcard, /sdcard/, /mnt/sdcard/titaniumbackup, /mnt/sdcard/titaniumbackup/ etc. but no matter what I enter, it gives me an error saying I'm not running an insecure boot image.
How can I pull down my nandroid backups from the phone so that I can wipe it and then get my data back? Please help..
have you tried clearing the cache partition and delvik cache? lots of bootloops can be fixed by just doing this.
if you have a nandroid backup theres no need to wipe anything before doing the restore.
Nandroid's won't restore? The correct path is: /sdcard/TitaniumBackup/ but if the toolkit is giving you no love I'd try it via adb.
adb pull /sdcard/TitaniumBackup/
For nandroids: adb pull /sdcard/clockworkmod/backup/
BUT
If you do a wipe data/factory reset your backup folders aren't lost, so a completely fresh ROM install won't affect your existing b/u's as long as you don't format your sd card.
neotekz said:
have you tried clearing the cache partition and delvik cache? lots of bootloops can be fixed by just doing this.
if you have a nandroid backup theres no need to wipe anything before doing the restore.
Click to expand...
Click to collapse
Yep, tried wiping cache and dalvik a few times, no dice. I also tried a nandroid restore from CWM but it errors out and doesn't restore..
CMNein said:
Nandroid's won't restore? The correct path is: /sdcard/TitaniumBackup/ but if the toolkit is giving you no love I'd try it via adb.
adb pull /sdcard/TitaniumBackup/
For nandroids: adb pull /sdcard/clockworkmod/backup/
BUT
If you do a wipe data/factory reset your backup folders aren't lost, so a completely fresh ROM install won't affect your existing b/u's as long as you don't format your sd card.
Click to expand...
Click to collapse
Thank you. I managed to get the files pulled, just had to manually kill adb and restart it and then I could pull the files.
Now I have also done a factory reset through CWM and the flashed the same ROM again, it's still in a boot loop!!
I'm at a complete loss.. what else can I try?
Could a part of the internal memory be corrupted or something like that?
was the phone a yakju build? if so you can use fastboot or the toolkit to flash them, this will flash the stock bootloader, recovery, kernel and system image.
https://developers.google.com/android/nexus/images#yakju
neotekz said:
was the phone a yakju build? if so you can use fastboot or the toolkit to flash them, this will flash the stock bootloader, recovery, kernel and system image.
https://developers.google.com/android/nexus/images#yakju
Click to expand...
Click to collapse
Thanks, that's exactly what I just did and it worked. No more bootloop! Phone booted up and I'm now in process of flashing my old rom and then hopefully restoring the nandroid.
I have no idea what caused all this after months of stable operation, but at least the phone is alive now..
Thanks all!
Is there a way to pull files/photos from a boot looping phone that's unrooted? :-/
lKoRTy said:
Is there a way to pull files/photos from a boot looping phone that's unrooted? :-/
Click to expand...
Click to collapse
Install the Galaxy nexus Toolkit (search for this on xda), then get it connected to your phone by following instructions in the tool.
Then select the option to pull files and give it the right path, which should be \sdcard\DCIM\Camera\.
This will pull the files to your computer where the Toolkit is installed.
Hope this helps!
the7thson said:
Install the Galaxy nexus Toolkit (search for this on xda), then get it connected to your phone by following instructions in the tool.
Then select the option to pull files and give it the right path, which should be \sdcard\DCIM\Camera\.
This will pull the files to your computer where the Toolkit is installed.
Hope this helps!
Click to expand...
Click to collapse
For some reason while reading about toolkit last night I gathered that it wouldn't work.. Perhaps I was wrong so this morning went ahead and did a reset to factory :-/
Thanks for the suggestions - I will definitely look into it if it occurs again. If it does, I will be posting a video on YouTube of burning it down
my phone was running amazing
then i turned off my phone so that i could turn it back on it wouldnt got past the google boot screen
now every rom i flashed and kernal and radio combo
has rebooted it self at boot animation to repeat
Any Sugestions?
Wipe data
wiped data and cache and dalvik while doing this
jett1217 said:
my phone was running amazing
then i turned off my phone so that i could turn it back on it wouldnt got past the google boot screen
now every rom i flashed and kernal and radio combo
has rebooted it self at boot animation to repeat
Any Sugestions?
Click to expand...
Click to collapse
restores with stock 4.0.4 .....
even tried restoring another rom but it goes all fine till /data then in the middle of restoring /data it has error on all my restores and fails
when i did the google factory image restore it wiped everything now how do u put files on sd card without going into usb debugging
Are these verified working restores?
If not... .img's over 2gigs cannot be restored.
This is an AOSP issue...
(TWRP allows you to enable compression...thus shrinking you're backups to smaller than 2gigs...but that's of no use to you currently).
A few users have also reported bootlooping after flashing something else...or nandroid restoring even without errors.
I had no such problems.
Flash stock images, if all else fails.
Jubakuba said:
Are these verified working restores?
If not... .img's over 2gigs cannot be restored.
This is an AOSP issue...
(TWRP allows you to enable compression...thus shrinking you're backups to smaller than 2gigs...but that's of no use to you currently).
A few users have also reported bootlooping after flashing something else...or nandroid restoring even without errors.
I had no such problems.
Flash stock images, if all else fails.
Click to expand...
Click to collapse
i have flashed 4.0.4 stock image
holy **** right as i was typing this my phone booted properly
jett1217 said:
i have flashed 4.0.4 stock image
holy **** right as i was typing this my phone booted properly
Click to expand...
Click to collapse
Same thing happened to me on v2 and I was using TWRP. Backed up /data/media rebooted into boot loader and ran fastboot -w and it booted right up. Using cwm to be safe now
EDIT: MAKE SURE YOU BACKUP /DATA/MEDIA BEFORE DOING FASTBOOT -W OR ALL YOUR SDCARD DATA WILL BE GONE!!!
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!