OK, I'm having an odd issue with my phone. After flashing ICZenwich rc1.4 I decided to restore a backup I made of rc1.3. However it won't properly restore... I keep getting this in CWR...
Checking MD5 sums . . .
Erasing boot before restore . . .
Restoring boot image . . .
Restoring system . . .
Restoring data . . .
Can't mount /data!
Click to expand...
Click to collapse
Then the restore process stops. I've tried starting from scratch via Odin and then again attempted to restore. Nothing works. Help would be greatly, greatly, appreciated!
I had this issue several times with previous versions of ICZen...I saw an app in Xda called Nandroid Browser but i never used it...
Sent from my SGH-T959 using XDA
Thanks for the suggestion, but that didn't really solve the issue. Luckily I frequently backup with Titanium Backup so I was able to upgrade to rc1.4 and restore. Everything seems to be working. Maybe later I'll try what dougfresh suggested and try flashing the Glitch B6 kernel and try to see if the restore works. However at the current I think I'll hold off on any nandroid backups for a while .
i tried also to restore the nandroid after flashing another kernel and still had the same issue...maybe the problem is not with the restore but the backup with the previous versions of MP kernels...
Got an idea Noob. Try to do an advanced restore and restore everything one by one except the boot.img. if it is a kernel issue then this might be a way to bypass it for now until MP or Br1ck'd gets a look at it.
Hey noob, do you remember what kernel you were on when you made the nandroid backup? I think mikka is on the right track, probably an issue with the backup itself rather than the restore operation.
Sent from my ICS'd Vibrant, melting all over XDA Premium
Br1cK'd said:
Hey noob, do you remember what kernel you were on when you made the nandroid backup? I think mikka is on the right track, probably an issue with the backup itself rather than the restore operation.
Sent from my ICS'd Vibrant, melting all over XDA Premium
Click to expand...
Click to collapse
The kernel that was backed up was MP's "cwm-subZero-Vibrant-1.0.1VC_build26-BFS_BLN" kernel. However it wouldn't restore even when attempting to restore after flashing the build 26 kernel. It was a very odd issue, during which I couldn't even mount nor unmount /data in CWR. However it apparently works now. Perhaps I'll start testing backups again at a later date, I've already got everything setup again anyhow. I'm again settled down with your amazing work!
PS- Working on a "Royale with Cheese" boot animation. May take some time, but it's in the works
I got the same Can't mount /data! error when trying to restore a backup after trying a build of CM10.
I just did a wipe data/factory reset, then the restore worked.
Related
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Click to expand...
Click to collapse
Any help would be appreciated.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
Are you sure you wiped data and cache. Also dalvic. I always flash miui twice also. That happened to me once before and I re flagged and all is well. The reason it is overheating is cause it stays at Max frequency ( CPU). Anyways check out the Miui thread in development if you want to try it again.
As far as your restore error, I don't know.
One time at football camp, I put my shoulder pads in my arse.
I may try miui again in the future, just want to get back where i was before. Thanks.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
creepyncrawly said:
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
Click to expand...
Click to collapse
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
gadget069 said:
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
Click to expand...
Click to collapse
sdcard/.android_secure is the hidden folder where apps2sd puts apps. It might be specific to cyanogen mod and miui, but not sure.
It happened when you first made your nandroid backup via cwm. The other day when I did a backup I watched it and saw the error skipping sdcard cause of no . android_secure . It has to do with cwm not being able to do a restore backup to our external sd. If you go in your external sdcard dir you will see the android secure file. So if next time you want your apps just move the file over for the backup and restore
Sent from my SAMSUNG-SGH-I777
Hello,
I've been lurking around here for a while now... reading and learning.
I started playing with ROMs for my SGSII a few weeks ago. I've successfully created and restored nandroid backups of my daily driver(rooted stock ROM) many times. I also backed up unnamed ROM once and it restores fine too.
MY PROBLEM:
I have 2 different Nandroids of two different nightlies of CM7 and neither of them will restore. Both give an MD5 sum error. How can i Nandroid backup CM7 and and restore it correctly?
Thanks!
frankos72
frankos72 said:
Hello,
I've been lurking around here for a while now... reading and learning.
I started playing with ROMs for my SGSII a few weeks ago. I've successfully created and restored nandroid backups of my daily driver(rooted stock ROM) many times. I also backed up unnamed ROM once and it restores fine too.
MY PROBLEM:
I have 2 different Nandroids of two different nightlies of CM7 and neither of them will restore. Both give an MD5 sum error. How can i Nandroid backup CM7 and and restore it correctly?
Thanks!
frankos72
Click to expand...
Click to collapse
I have had this happen a lot to older backups that I have made. This thread here has worked for me.
http://forum.xda-developers.com/showthread.php?t=976453
Solution:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick
Click to expand...
Click to collapse
Enjoy
Thanks, I'll give it a go.
Oh boy that was quite a ride. For some reason when I restored the bu after using adb to fix the md5 sums I went into a reboot loop that would cross the sgs2 splash.
I had to reflash the stock plus root with odin and then a UN New kernel with cwm so I could get back to my DD. That was a bit scary just hours ahead of the SOPA blackout.
So, is there some reason that only cm7 roms are having a bad md5 sum? I really wanted to work on making cm7 My dd, but that won't be possible if I can't count on it too backup and restore reliably.
Got any tips?
Sent from my SAMSUNG-SGH-I777 using Tapatalk
You can either flash the same nightly you were on, let it reboot, then exit back out to recovery and restore your nandroid backup.
Here is another option to try. Flash the kernel zip I am attaching here: http://db.tt/wlfhSfag in cwm, then go and restore your nandroid backup. The file I am linking is JUST the kernel for CM7.
The reason you are having the issue is due to the OTHER roms using a different version/ version number of CWM. So once you flash the kernel and MAYBE try to boot it up( it will be stuck on the cyanogenmod boot screen), then 3 button back into recovery, now you will have a different version of CWM, which should allow you to restore your nandroid now.
Sent From My KickAss ATT SGS2 SPORTING CM7
^^^RockRatt definitley knows what he is talking about when it comes to cm7. I have never had an issue going from asop to Samsung based roms restoring from a backup. I read somewhere on here that if you rename your backups and you put a space in the name that this will cause issues with the md5 sum match. Did you happen to do this?
RockRatt said:
The reason you are having the issue is due to the OTHER roms using a different version/ version number of CWM. So once you flash the kernel and MAYBE try to boot it up( it will be stuck on the cyanogenmod boot screen), then 3 button back into recovery, now you will have a different version of CWM, which should allow you to restore your nandroid now.
Click to expand...
Click to collapse
Thank You! I haven't tried it but my gut says that you are spot on. I figured it was something like that because I had read about how entropy's DD kernel is for stock based roms and doesn't work with CM7. I just didn't really know what to do about it. I'm going to try the flash a CM7 kernel then restore and I'll report back my results.
moustro said:
I read somewhere on here that if you rename your backups and you put a space in the name that this will cause issues with the md5 sum match. Did you happen to do this?
Click to expand...
Click to collapse
Nope I read that and haven't renamed any of my backup..... yet. It's good to know just in case I ever do rename them. Thanks!
Decided I better ask for help before digging a deeper hole...
I had rooted my Vibrant around September 2010 and tried some ROM at the time, don't remember which one. I didn't keep it for very long...I accepted one or two stock OTA updates thereafter, ending up with 2.1-update1/KA6.
Fast forward to yesterday, when I decided to try to go to Gingerbread so as to be able to install an app I wanted. I chose CM7.2. I presumed I wasn't rooted anymore after the OTA's, so used CWM to run the update.zip that I still had on the SD card from 2010. I did a Titanium backup. I started following the abbreviated directions, then went to the full directions here:http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
So I actually made two nandroid backups as a result of switching between the two sets of directions and getting distracted after I made the first one.
All went well, except after CM7.2 was booted and everything restored from Titanium, I had the following issues:
1. Messaging was broken
2. Most contacts were missing
3. GPS wouldn't lock
I poked around for fixes and tried some, but it was not looking promising. I decided I didn't really need that new app after all, and today tried to revert to stock. I supposed it would be a simple matter of a nandroid restore followed by a Titanium restore. Unfortunately the nandroid restore failed.
Research revealed this is a known issue with "different hboots".
I then compounded the issue by accidentally pressing the power button while in Recovery. The phone rebooted but stuck on the "Vibrant" splash screen, because of the corrupted restore attempt. No amount of 3-button resets got me back to Recovery. The phone is now connected to my laptop in Download mode.
I think what I now need to do is odin, per http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
I will then be able to do a nandroid restore and Titanium restore and be back where I started? Any additional hints, warnings, etc?
Thanks in advance.
Be careful about what you backup with Titanium on stock and then restore on CM. Did you backup your Messaging app or any system data? If you restored system apps or data from a TI backup onto CM from stock, that could cause issues.
And about the contacts, where did you store them before? On Google, SIM, or in memory?
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
m3rb said:
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
Click to expand...
Click to collapse
If you do a nandroid restore you don't need to do a TI restore as nandroid will restore all your apps and data. (Even down to which wallpaper you're using and Wifi networks)
If the KA6 modem works best for you then go for it.
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
You don't need to be rooted, you just need a way to install. For example when you install from stock, you don't need to root it, only flash the custom kernel that has CWM, and then flash, since root is a state of the ROM.
Sent from my SGH-T959 using xda premium
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Well, in our case we can use download mode + heimdall to flash a kernel that has the CWM recovery included.
Sent from my SGH-T959 using xda premium
Hello, I have a major problem with something that should have been a minor project. I used System Recovery to do a backup of the phone. The only thing I can think of there that I might have done differently is save the backup to the external SD card, instead of internal. After the backup completed, I went to reboot the phone and it's stuck on the Motorola splash screen. I tried to pull the battery and go into that general Android Recovery in order to wipe data and try again, but I just get the Android with an exclamation point over his head. I've tried booting it without the SD card too. I was using CM7
Can anyone help please!
EDIT: A couple hours later, since it was my work phone, I had to do something. I reverted the SBF, re-rooted and tried to restore from the backup I made and the same thing happened. I'm going to try to revert to my previous backup. I have a full backup from Titanium Backup if it comes down to it. The phone was working fine, I just can't figure out why it blew up on me after I ran the backup. Grr..
iceolate said:
Hello, I have a major problem with something that should have been a minor project. I used System Recovery to do a backup of the phone. The only thing I can think of there that I might have done differently is save the backup to the external SD card, instead of internal. After the backup completed, I went to reboot the phone and it's stuck on the Motorola splash screen. I tried to pull the battery and go into that general Android Recovery in order to wipe data and try again, but I just get the Android with an exclamation point over his head. I've tried booting it without the SD card too. I was using CM7
Can anyone help please!
EDIT: A couple hours later, since it was my work phone, I had to do something. I reverted the SBF, re-rooted and tried to restore from the backup I made and the same thing happened. I'm going to try to revert to my previous backup. I have a full backup from Titanium Backup if it comes down to it. The phone was working fine, I just can't figure out why it blew up on me after I ran the backup. Grr..
Click to expand...
Click to collapse
sounds like a bad backup. i always use external sd for nandroids and it has never had issues.i would just re-flash. as for stock recovery with andy with an exclamation , push both volume keys. should work regardless of what state the phone is in. i have had it completely unusable and it still worked.
Lorenzo VonMatterhorn said:
sounds like a bad backup. i always use external sd for nandroids and it has never had issues.i would just re-flash. as for stock recovery with andy with an exclamation , push both volume keys. should work regardless of what state the phone is in. i have had it completely unusable and it still worked.
Click to expand...
Click to collapse
OK - You mean to flash cleanly with CM7 and then restore from Titanium backup instead of my previous nandroid backup?
I'm slightly confused about that System Recovery tool, because first I had ROM Manager and it says that CWM is installed, but it doesn't work. Do I have to manually install that System Recovery APK each time I do stuff like this, or does it stay installed? And if so, from a powered off state, how do you enter it? Or do you have to boot up to Android and enter recovery mode from the app? Thanks.
iceolate said:
OK - You mean to flash cleanly with CM7 and then restore from Titanium backup instead of my previous nandroid backup?
I'm slightly confused about that System Recovery tool, because first I had ROM Manager and it says that CWM is installed, but it doesn't work. Do I have to manually install that System Recovery APK each time I do stuff like this, or does it stay installed? And if so, from a powered off state, how do you enter it? Or do you have to boot up to Android and enter recovery mode from the app? Thanks.
Click to expand...
Click to collapse
yes i would try that. second, dont use rom manager. dont delete it either. but it doesnt work on our phone. the bootstrap recovery that you install would only need to be reinstalled if you delete cache in recovery. otherwise it should always work. hope this helps. im not completely sure exactly what you are asking.
try just restoring system part of backup, see if phone will boot, then restore user data
or reinstall cm7 and restore just user data
Sent from my XT862 using xda premium
sd_shadow said:
try just restoring system part of backup, see if phone will boot, then restore user data
or reinstall cm7 and restore just user data
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
I should be fine now, thanks for the advice. I don't know why that backup blew up the phone, but it was sure an inconvenience haha! I just reflashed CM completely, and now I'm gonna roll out my Titanium backup. I don't have a lot of stuff, just the essential stuff for work, so it shouldn't take too long.
No matter what rom I use, AOSP or TouchWiz, I get a bootloop. Usually I can solve these issues myself, I've softbricked my Android devices tons of times since I got my first Android (Samsung Fascinate) in 2010, and I've managed to get out of all those situations, but this one has me stumped.
The problem began today. Randomly after booting into Philz Touch recovery, I got an error that read "could not mount /data to setup /data/media path." I used this fix and it worked, unfortunately, I lost all of my internal SD card data. However, since then, every 4.3 and 4.4 rom I've flashed (TouchWiz and AOSP) just doesn't work. To be more specific, I initially tried today's (8/02) Cyanogenmod nightly...bootlooped. Then I tried the rom I was on when the problem initially occurred...bootlooped. Then I flashed this rom later...bootlooped. Naturally, I did a factory reset/dalvik wipe/cache wipe before each rom flash.
Do I have to flash stock 4.1.2 again? I really don't want to if I can avoid it, but I'm downloading the rom anyway.
EDIT: I flashed 4.1.2...it bootlooped. I performed a factory reset and cache wipe and it STILL bootloops. Something I did notice is that it says "E: failed to mount /efs (Invalid Argument)." I noticed that earlier back when I was using Philz recovery as well. Could that be a reason for all of these bootloops?
Did you backup your efs data? I'll been flashing for years and never gave it a 2nd thought... until a few weeks ago when my kids while playing with the phone froze it... and I had efs errors and bootloops. ..
I was able to odin the efs backup but unfortunately I've also locked my bootloader (still not sure how I did that)...
Currently I'm running safe strap with 4.3 skynote-n3bula hybrid... do I miss kk? Yepper... but at least I have my phone back...
The efs fix is in this forum.. try search? ... I will look to see if I saved the files some where...
Sent from my SCH-I605 using Tapatalk
kingamra said:
Did you backup your efs data? I'll been flashing for years and never gave it a 2nd thought... until a few weeks ago when my kids while playing with the phone froze it... and I had efs errors and bootloops. ..
I was able to odin the efs backup but unfortunately I've also locked my bootloader (still not sure how I did that)...
Currently I'm running safe strap with 4.3 skynote-n3bula hybrid... do I miss kk? Yepper... but at least I have my phone back...
The efs fix is in this forum.. try search? ... I will look to see if I saved the files some where...
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I unfortunately didn't backup my efs. I didn't know anything about efs until today when I ran into this problem and started googling around. Do you know of an efs backup that works? I'll give a search around the forums for a fix.
Tkun said:
I unfortunately didn't backup my efs. I didn't know anything about efs until today when I ran into this problem and started googling around. Do you know of an efs backup that works? I'll give a search around the forums for a fix.
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...w-to-unbrick-hard-bricked-i605-n7100-t2825222
kingamra said:
http://forum.xda-developers.com/not...w-to-unbrick-hard-bricked-i605-n7100-t2825222
Click to expand...
Click to collapse
Thanks! I'll test this out.