Related
Been using the Alpha version of CM7 for the t989 for over 2 weeks now. Seems like when I rebooted it today it managed to corrupt the data partition.
Symptoms:
-Normal starts loop just after the kernel screen.
-CWM boots and works
-ODIN boots.
-CWM crashes when doing factory reset or restoring the data partition of a backup or formatting the data partition
This happened to me 2 days after installing CM7, the same version I'm still using. I was similarly stuck, but then I tried restoring my nandroid backup and eventually I could re-apply the CM7 zip and the phone started fine to a blank android.
Is there a way to solve this issue with my partitions? I am not too comfortable with re-partitioning it because I'm awake this can damage the boot sectors and brick it quickly if I don't do it just right.
Advice?
Just flash this http://forum.xda-developers.com/showthread.php?t=1391174 from Odin, reflash cwm, cm7, and you are done. I have done this thrice.
Sent From The Best Phone of 2011
GBGamer said:
Just flash this http://forum.xda-developers.com/showthread.php?t=1391174 from Odin, reflash cwm, cm7, and you are done. I have done this thrice.
Sent From The Best Phone of 2011
Click to expand...
Click to collapse
did it work???
Thank you
I'm so glad I found this thread, I thought my phone may be unreparable. I was experiencing exactly the same symptoms as the OP on my skyrocket and had considered using ODIN to restore to stock, but I thought the corrupted data partition could cause it to crash during the restore and hard brick the phone.
The restore was successful, but it boot looped for some reason. I then followed the ODIN root method to flash CWM recovery, flashed CM7 from there, booted and used the ROM Manager app to apply a recent backup. All is well.
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
Long story short, I've spend the better part of 2 days trying to get my phone to working order.
I tried to flash the stock 4.0.4 rom into my phone. After I did that, the radio stopped working so i wanted to go back to my previous All-star-v7 rom that i had backup in the external sdcard.
When I was installing 4.0.4 i had to switch from CWM to TWRP to get it to install. I switched back to CWM using ODIN but now when i try to wipe the phone so i can restore a backup, it hangs up on wiping /cache and if i try to restore it hangs up on restoring cache....
What do i do? I had used the infamous super wipe and cache wipe to get the phone into 4.0.4 I think i messed up something because of using those...
update: Strangely, I can restore a backup of 2.3.6 and even though it hangs on restoring /cache. I restart the phone and it boots up to it. I also find that google play is unable to update any of my apps, it looks like it's because of the corrupted /cache. how would i fix it?
update2: i used odin to flash into TWRP 2.6.3.1 and did a cache wipe and it's stuck at "unable to open '/cache/recovery/.version'. anyone know how to fix that?
Hi,
I was frustrated with the delay in T-Mobile's release of KitKat for the GSIII, so I decided to root my phone last night in order to try flashing CM11 on it. Rooted my phone with Towelroot, installed ROM Manager and CWM, and created backups on Kies and through CWM. Then I proceeded to do data wipe/factory reset, cache wipe, and /system format. Tried to flash CM11, but got a status 7 error.
I freaked out, so I decided to restore everything from the backup I'd created. Restoration seemed like a success, but now I get the error "Unfortunately, the process com.google.process.gapps has stopped" in an endless loop, and it prevents me and any apps from doing anything. I tried clearing dalvik cache in recovery, but the problem still persists. Read on a few threads that I should flash to stock firmware via Odin, but I'm currently on a macbook, so I can't install it.
tl;dr - Prepped to flash CM11, reached status 7 error, got freaked out, and did restore via CWM, only to get infinite loop of gapp crashes. No access to Odin or PC. Not hard bricked or soft bricked, but essentially useless phone. Help? );
if you can still get to recovery, download latest gapps and flash that
Did you factory reset before or after you restored your back up?
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Try to factory reset again
vvnn said:
Yeah, I've tried flashing gapps--no avail.
And yeah, I did factory reset/data wipe, cache wipe, /system format 3x each before attempting to restore. Was that wrong? /:
Click to expand...
Click to collapse
If I'm not mistaken, there is some device ID that will change each time you flash a new rom. It may be something to do with this ID not matching the one in the restored data. Purely a guess but seems logical to me.
Anyway, factory resetting will most likely solve this for you, but I wanted to add that except in certain circumstances, you shouldn't ever manually format /system. (and one format on any partition is sufficient. There shouldn't be any need to format multiple times). If you format /system, you are wiping the O/S off of your device. Then what happens if you have problems flashing a rom, or firmware? I've seen it happen many times and I often end up spending a couple of days working with them just to get the thing to boot up again!
When you flash a rom, the first thing it does is format /system. So there is just no need to do this manually. At least if the rom fails to flash (such as failing the assert checks), youll still have something to boot into. Hope this helps in the future!
I have had the exact same issue. I have a Samsung note 2 N7105. I rooted made a backup in CWM and flashed ditto n3/s5 rom made another backup in CWM. No issues. Got a bit cocky seen as it was my first time doing anything like that. My next adventure was to try a custom kernel (agni). This didn't go so well, so I tried to do a restorw to my working backup of ditto n3/s5 rom through CMW. restore went smoothly and the phone booted. once I opened the lock screen I got the gapps error as described. I had to do a factory reset to get the phone working and then re-flashed ditto n3/s3. I've since flashed other roms and when ever I try to do a restore, I get the issue described. Note I am using the latest CWM. I putting off flashing and trying any other ROMs because of this issue. I do love dn3/s5 but id love to try others. Anyone can help it would be appreciate.
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again.
Click to expand...
Click to collapse
I don't think the recovery was "restored" / flashed to the boot partition but maybe try just in case. Flash the boot.img for Viper ROM and see if it stops the bootloop. After that you can make a clean wipe and install the ROM again, not restore but INSTALL. You surely have the ROM's .zip still?
Reason I suggested boot.img: i cannot get anything to restore with the h3g__001 backups keep getting recovery.emmc.win' is larger than target device '/dev/block/mmcblk0p42 error
mmcblk0p42 is the boot partition, so I don't know why TWRP tried to restore/flash a recovery to boot partition. He solved it by manually flashing boot.img after renaming.
if anyone gets this error heres how i solved it.change the boot.emmc.win to boot.img and it let me restore
Just a suggestion...
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
OMGMatrix said:
So this has been thoroughly confusing.
It seems that I had to clear the cache several times in PhilZ in order to resolve the first error. I tried to flash the original rom zip for Viper, but it still failed even though the "E: can't mount" messages weren't showing any more. However, I was able to re-flash the rom zip for PA, and upon booting, I found that Many of my apps were still there dispite the fact that they should have not been.
I then was able to reboot to recovery and flash the zip for Viper.
No clue what happened, but at least if anyone else has this problem, they'll be able to see how I fixed it
Click to expand...
Click to collapse
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Not sure if you have to actively choose whether to flash over data or not, I'm not that big into custom ROMs, only tried Viper ROM and even then I kept my original data.
OMGMatrix said:
I'm using an AT&T M8, BL unclocked through HTCdev, Sunshine S-OFF, SuperCID.
Yesterday, I flashed PA. Today, I decided to restore my nandroid for Viper.
I rebooted to recovery (TWRP), wiped my data, and then told it to restore my backup of Viper. Almost immediately after doing so, my phone rebooted without completing the restore. I tried then rebooting to recovery, and wiping /system before doing the restore, in the belief that it was a Sense/AOSP conflict. However, TWRP decided to reboot before I could even start the restore.
Now, I don't have an OS to boot to, and TWRP continually reboots 10-15 seconds after it boots.
I've tried updating my recovery, which was successful, but this did not seem to have an effect.
I've also tried clearing cache with fastboot, and while this was also successful, it also has not had an effect.
Has anyone seen this happen before?
Edit:
I've installed PhilZ recovery, and it no longer reboots immediately after booting to recovery. However, each time it starts, it gives a series of "E: Can't Mount /cache/recovery"...etc.
When I try to wipe data in PhilZ, it reboots again. I've tried reflashing PA, but it gave me a "E: failed to set up expected mounts for install; aborting".
Click to expand...
Click to collapse
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
I ended up just running an RUU and starting over. I was able to adb pull all my files from internal sd card before i ran it.
mattprice86 said:
Had that exact same issue as you. What version of twrp were you running when the issue started? Also, did you make any firmware upgrades or downgrades recently?
Click to expand...
Click to collapse
I was using a version of TWRP that had been bundled with a previous version of Viper that was supposed to have been newer, but was actually 2.7.0.1. I updated to the newest (2.8.0.3) from the TWRP site through fastboot, but that didn't change anything. I had somewhat recently updated to the 3.xxx.xxx.7 firmware, but had flashed other roms since that without issue.
BerndM14 said:
The apps will be there if you restored without making changes to the data partition which contains the your userdata. I've converted and changed over from International to Developer edition quite a few times now and not once in all those times did I lose my data, I just never restored the data partition.
Click to expand...
Click to collapse
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
OMGMatrix said:
I did a factory reset (cache, Dalvik, data) before attempting the nandroid restore.
It looks like TWRP failed to actually do the reset in the first place, which caused it to get hung up thinking that the storage was actually being used.
Click to expand...
Click to collapse
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
BerndM14 said:
Doesn't matter mate, if you restore the data partition the backup that you made of data gets restored, period. It'll be another issue worth interest if you deselected "data" while doing the restore. As you clearly stated yourself, you did a factory reset(wipe all) BEFORE you did the nandroid restore(In which case you might have restored "Data" as well), in that case the factory reset doesn't matter at all. If you did it after you restored then, again, it's something different.
Click to expand...
Click to collapse
I don't think you understand.
The restore never happened. It rebooted before anything happened when I told it to restore. Nothing got restored.