Develop Bugs

[Q] Restoring from CWM 3.1.0.1 not working

I created a backup using CWM 3.1.0.1 (from rooted EC05). I then flashed one of the new roms, and today wanted to go back, so i booted into 3.1.0.1 and did the restore (from cw). Now the phone boots up to the Samsung screen and sits there. What am I doing wrong? Sorry if this has already been asked, I did a search but couldn't find this particular issue. Thanks for any and all help.

both backups were made using 3.1.0.1? and were both made in 3finger recovery? and when you restored you were in 3 finger recovery, not reboot recovery?

chris41g said:
both backups were made using 3.1.0.1? and were both made in 3finger recovery? and when you restored you were in 3 finger recovery, not reboot recovery?
Click to expand...
Click to collapse
I only did 1 backup, not sure what you mean by 3 finger recovery? I booted in CWM (purple) and did the back-up. I then put on the "Bamboozle" rom (and yes, I wiped everything 3x like qb shows in the vid) then installed the rom. I ran it for the past week (loved the rom, but it was eating my battery really bad) so wanted to try a different rom. I thought the easiest way to start was to restore the backup I made, so I booted back into cwm and selected Backup/Restore, Restore, Yes and it ran and said it restored fine. I reboot, but all I get to now is the Samsung screen, no further.

libracolo said:
I only did 1 backup, not sure what you mean by 3 finger recovery? I booted in CWM (purple) and did the back-up. I then put on the "Bamboozle" rom (and yes, I wiped everything 3x like qb shows in the vid) then installed the rom. I ran it for the past week (loved the rom, but it was eating my battery really bad) so wanted to try a different rom. I thought the easiest way to start was to restore the backup I made, so I booted back into cwm and selected Backup/Restore, Restore, Yes and it ran and said it restored fine. I reboot, but all I get to now is the Samsung screen, no further.
Click to expand...
Click to collapse
Let me just say, I think I f'ked my phone up. So I gave up trying to restore, just odin'd back to stock (ec 05). Which I then re-rooted and re-installed CWM 3.1.0.1 (I have titanium backups as well). However, now the phone runs really, really slow and when I try to restore apps from titanium it just sits there (in batch mode). Sorry, for being a noob; hey, if nothing else, maybe I'm making someone smile at my dumb a$$. But now, if I can be even more stupid, is there a way to just "reset" the phone, by that I mean put it back to a "true stock" form so I can start over? And then, can I just delete these backups, and roms from the sd card (just hookup to laptop and delete from the sd-card)? I think maybe it'd be easier to just start from scratch again...thanks for the help, I try to keep up with the forums, but so many posts....

What he means by 3 finger is the ONLY way to get into recovery for proper operation. With power off press and hold camera, volume down, and power. Holding all 3 until you see the recovery menu. If you use any other method such as ROM Manager or Quick Boot you will more than likely screw up your phone. Neither application is recommended for recovery operations.
Sent from my SPH-D700 using XDA App

I believe clockwork does not backup the kernel. You may need to install a kernel.
Just a thought...

libracolo said:
I created a backup using CWM 3.1.0.1 (from rooted EC05). I then flashed one of the new roms, and today wanted to go back, so i booted into 3.1.0.1 and did the restore (from cw). Now the phone boots up to the Samsung screen and sits there. What am I doing wrong? Sorry if this has already been asked, I did a search but couldn't find this particular issue. Thanks for any and all help.
Click to expand...
Click to collapse
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App

crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Thanks, that must have been it. I was on Bamboozle, which is based on Gingerbread.

libracolo said:
Thanks, that must have been it. I was on Bamboozle, which is based on Gingerbread.
Click to expand...
Click to collapse
Wait, did you wipe data/system,cache, and Dalvik Cache then restore your nandroid? I have a SRF 1.2, an Urban Regeneration, and a CM7 nandroid. As long as I wipe everything then restore I have no problems. I have bounced between all three today with no issues
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
Wait, did you wipe data/system,cache, and Dalvik Cache then restore your nandroid? I have a SRF 1.2, an Urban Regeneration, and a CM7 nandroid. As long as I wipe everything then restore I have no problems. I have bounced between all three today with no issues
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah, the issue was I was running bamboozle (GB leaked rom), so once I odin'd back to EC05, I was able to run the restore without problem. I am now running SRF 1.2 (awesome rom btw) and I was able to restore when trying to install that rom (and the genocide kernel). Thanks for all the helpful answers.

crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I would have thought the same thing. However, I simply restored my SFR 1.2 nandroid right over the gingerbread rom. With a few glitches smoothed out I am running fine again with no Odin involved.
Sent from a secret underground bunker

mjben said:
I would have thought the same thing. However, I simply restored my SFR 1.2 nandroid right over the gingerbread rom. With a few glitches smoothed out I am running fine again with no Odin involved.
Sent from a secret underground bunker
Click to expand...
Click to collapse
Yeah, I have gotten the dreaded Google Services Framework FC's a couple of times but for the most part I can wipe everything and restore a Froyo setup even when on a Gingerbread ROM. The purp recovery is good like that.
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
Yeah, I have gotten the dreaded Google Services Framework FC's a couple of times but for the most part I can wipe everything and restore a Froyo setup even when on a Gingerbread ROM. The purp recovery is good like that.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the info. I will have to remember that and try it out in the future.

crawrj said:
Thanks for the info. I will have to remember that and try it out in the future.
Click to expand...
Click to collapse
Hey, no problem crawrj. It definately comes in handy with all of the testing I do for sure.
Sent from my SPH-D700 using XDA Premium App

When restoring across different OS versions it is handy to do a Restore>Advanced Restore Data from the Nand backup. There may be the occasional FC if the data format has changed but that usually can be fixed by clearing data of the offending app, especially for Google sevice framework.

kennyglass123 said:
When restoring across different OS versions it is handy to do a Restore>Advanced Restore Data from the Nand backup. There may be the occasional FC if the data format has changed but that usually can be fixed by clearing data of the offending app, especially for Google sevice framework.
Click to expand...
Click to collapse
Kenny - I did try that as well. I tried everything, I did the "Restore" option like 4 separate times, I wiped data, cache, dalvik cache 3 x, even did the Advanced option and went down the list. None of that helped. Now it may be that I just didn't wait long enough, but I figured 4-6 minutes of the "Samsung" screen meant it had stopped responding (I see that all that time in MS apps). I finally odin'd back to stock ec05, re-rooted (and updated back to cwm 3.1.0.1), then I ran the restore (not advanced), and it worked like a charm. Thanks for all the suggestions on this.

libracolo said:
Kenny - I did try that as well. I tried everything, I did the "Restore" option like 4 separate times, I wiped data, cache, dalvik cache 3 x, even did the Advanced option and went down the list. None of that helped. Now it may be that I just didn't wait long enough, but I figured 4-6 minutes of the "Samsung" screen meant it had stopped responding (I see that all that time in MS apps). I finally odin'd back to stock ec05, re-rooted (and updated back to cwm 3.1.0.1), then I ran the restore (not advanced), and it worked like a charm. Thanks for all the suggestions on this.
Click to expand...
Click to collapse
Sometimes our phones can be so finicky. Glad you got it working. Usually when Dalvik is rebuilding it takes awhile at the S screen, so you are correct that 4-6 minutes at Samsung is a cry for help from your phone.

crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Not true. I always go from froyo to gingerbread with backups. What he Did wrong was not wipe when he tried to restore his back up that's why he got stuck on the Sammy screen. Also if he tried to restore a rfs froyo rom it could've gotten stuck there also since bammbozle was ext4.
Sent from my SPH-D700 using XDA Premium App

Esteway.619 said:
Not true. I always go from froyo to gingerbread with backups. What he Did wrong was not wipe when he tried to restore his back up that's why he got stuck on the Sammy screen. Also if he tried to restore a rfs froyo rom it could've gotten stuck there also since bammbozle was ext4.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You can restore from EXT4 to RFS with advanced restore data nand. He said he tried all of this and still got stuck. But I think you are correct and the first restore attempt borked everything. From there a reflash then advanced restore data should have worked.

kennyglass123 said:
You can restore from EXT4 to RFS with advanced restore data nand. He said he tried all of this and still got stuck. But I think you are correct and the first restore attempt borked everything. From there a reflash then advanced restore data should have worked.
Click to expand...
Click to collapse
So if I understand what you guys said, I should have wiped first (before the initial restore), which I didn't do. When the first restore didn't work, then I did the wipe x3, but it sounds like by that point it was already too late. So should you always wipe before restoring? I only ask, because once I got everything back to a good place I flashed the sfr 1.2. The first attempt caused the phone to boot up with that annoying "Android" screen, so I just booted into CWM and restored. That time I just restored (no wipes, no advanced) and it restored fine. I then re-flashed and all was good. So it seems like you don't always have to wipe x3 before restoring? Thanks btw, all good info for future ref.

Nandroid md5 mismatch cwm5.0.2.7

I made a nandroid last night on my buddies epic touch, the nandroid restored fine last night, however, tonight I'm receiving the md5 mismatch, I am used to using amon ra recovery on my EVO 4g, am I missing something simple, thanks in advance. By the way you guys have a beast of phone.
Sent from my PC36100 using xda premium

did you rename the backup? I did that and it gave me the same error.

sickboy82 said:
I made a nandroid last night on my buddies epic touch, the nandroid restored fine last night, however, tonight I'm receiving the md5 mismatch, I am used to using amon ra recovery on my EVO 4g, am I missing something simple, thanks in advance. By the way you guys have a beast of phone.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Amon or Clockwork it can happen on both, his backup file probably got corrupted somehow on his sdcard and now it wont restore. It has happened to me before. I normally keep a couple of backups on my phone just incase that happens. Dont think there is anything he can do but make another backup...
I am a former OG Evo Amon lover myself and wish he did a recovery for this phone but the Team Rogue recovery is quite nice as a replacement for Amon at the moment
---------- Post added at 08:02 AM ---------- Previous post was at 08:02 AM ----------
patrao_n said:
did you rename the backup? I did that and it gave me the same error.
Click to expand...
Click to collapse
no spaces in the name when you rename it

sickboy82 said:
I made a nandroid last night on my buddies epic touch, the nandroid restored fine last night, however, tonight I'm receiving the md5 mismatch, I am used to using amon ra recovery on my EVO 4g, am I missing something simple, thanks in advance. By the way you guys have a beast of phone.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Check out the following thread:
http://forum.xda-developers.com/showthread.php?t=714114
Worked for me; although if you ignore the md5 mismatch you might have problems later if it was indeed corrupted.

patrao_n said:
did you rename the backup? I did that and it gave me the same error.
Click to expand...
Click to collapse
No I did not rename it, neither did he.
Sent from my PC36100 using xda premium

Yamuu said:
Check out the following thread:
http://forum.xda-developers.com/showthread.php?t=714114
Worked for me; although if you ignore the md5 mismatch you might have problems later if it was indeed corrupted.
Click to expand...
Click to collapse
I will give this a shot when I get the time, thanks was hit.
Sent from my PC36100 using xda premium

I had the same issue. Just got my Epic on Tuesday, rooted it, and I needed to restore my backup yesterday. Said the MD5 sums did not match. I'm using EL29, and the Team Rogue recovery, aka CWM 5.0.2.7. I'll check out that link that was posted by Yamuu, for future reference.

I screwed up a file on my SE4GT and ended up in a reboot, which ended up turning the device off. This happened multiple times.
Luckily, (cough!) I had 2 Backups on my sd card.
Well, I got the MD5 mismatch on the most recent Backup. I transferred the folder to another card (cough!) and wasted about an hour and a half trouble shooting, when I Finally thought to try the earlier Backup, which worked.
I've learned a few things, maybe, from this>
1) always have at least 2 back ups in case one fails.
2) check the MD5 sums to make sure they match, but they can corrupt later, I would think.
3) make a Backup to the Internal Storage also (May have less of a chance to corrupt, but I'm unsure of this.)
4) It's quite possible, because the 2 Backups were about a month apart, that I changed the Version of CWM, and that the Version has to match the version used when making the Backup, of which I'm not sure.
But if that was the case , the later backup would have worked, instead of the earlier Backup.
5) Try the other Backup next time

sickboy82 said:
I made a nandroid last night on my buddies epic touch, the nandroid restored fine last night, however, tonight I'm receiving the md5 mismatch, I am used to using amon ra recovery on my EVO 4g, am I missing something simple, thanks in advance. By the way you guys have a beast of phone.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Team Rogue recovery is great for this because it creates the backup and automatically generates the md5 sum, not giving you the option to name it.
Mi nuh tek intimidation...

asbjörn said:
Team Rogue recovery is great for this because it creates the backup and automatically generates the md5 sum, not giving you the option to name it.
Mi nuh tek intimidation...
Click to expand...
Click to collapse
Hit the Thanks in error
I was going to say that if you go directly into Recovery from the phone, instead of through ROM Manager, then Team Rogue does Name the Backup, and CWM flashes the Backup.
I made a Backup from ROM Manager to the External SD card, then I also made a another Backup to the Internal Storage, directly from Rogue Recovery.
Of course, CWM is flashing the Nandroid.
With the above being said, is it better to run the backup, whether it's to the internal or SD Card, directly from Rogue Recovery, rather than through ROM Manager, or does it matter?
I write about my experience, as it relates to the op's, and may help others who are having the same issues

Biker1 said:
Hit the Thanks in error
I was going to say that if you go directly into Recovery from the phone, instead of through ROM Manager, then Team Rogue does Name the Backup, and CWM flashes the Backup.
I made a Backup from ROM Manager to the External SD card, then I also made a another Backup to the Internal Storage, directly from Rogue Recovery.
Of course, CWM is flashing the Nandroid.
With the above being said, is it better to run the backup, whether it's to the internal or SD Card, directly from Rogue Recovery, rather than through ROM Manager, or does it matter?
I write about my experience, as it relates to the op's, and may help others who are having the same issues
Click to expand...
Click to collapse
Really? Because I don't use Rom Manager at all. I always go thru Rogue Recovery to create and restore backups. Taking the direct route always proves less problematic than alternative methods. Whenever I do, it looks like this, auto generated file name:
I was trying to upload my screenshot but the new XDA update is preventing it from happening.
Mi nuh tek intimidation

[Q]Bad Nandroid?

So it's my day off, so I thought I'd spend some of that time messing around with my phone. First thing I do is create a nandroid with CWM, because I'm not an idiot.
Only apparently I am, because after fouling up a restore of a new rom with an unrelated to my nandroid issue I'm working on resolving (Something in my TB backedup data causes Android.process.acore to force close) I restored my nandroid.
Only to be stuck staring at the Galaxy SII logo.
Does anyone know what can cause a bootlock like this just from restoring a nadroid? I've tried just rebooting into recovery and restoring it, wiping cache/dalvik and restoring, full wipe and restore.... nothing. Bootlock.
Please help, and a million thanks in advance.

Are you sure it actually backed up properly. I got caught out there like that one time where I thought I backed up my rom but it failed and did not notice it till I restored.
Check the folder size that your actual backup is in and compare it the file size of another backup you hopefully have

playya said:
Are you sure it actually backed up properly. I got caught out there like that one time where I thought I backed up my rom but it failed and did not notice it till I restored.
Check the folder size that your actual backup is in and compare it the file size of another backup you hopefully have
Click to expand...
Click to collapse
It's the right size. The other nandroid I had was 1.08 gb, this one is 1.1 gb, so
it's definitely the right size.

If it was on ics and you used el26cwm then you have to restore the nandroid backup then flash an ics kernel.
Sent from my SPH-D710 using XDA

peanut1596 said:
If it was on ics and you used el26cwm then you have to restore the nandroid backup then flash an ics kernel.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
O my ruttin god, thank you. I could've sworn I've restored nandroids with EL26CWM, but I guess I've always restored from Agats...thanks.

Formatting system...?!?

I used to format /system every time I flashed a ROM on my gs2, but I saw in the numerous imei threads some posts about not doing so because it may be part of the lost imei issues. Do you do it ? Have you had issues ? I'm reluctant to do so , but feel it will be " beneficial to my flashing" if I did...
Sent from my SGH-T999 using Tapatalk 2

jasonren29 said:
Format system does not wipe out imei. It's when you root it the wrong way. If you want to play safe, you can go to development section use imei back up method to back it up
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
+1
Sent from my SGH-T999 using xda premium

No lie I formatted my system the other day and right after tried to revert to a stock android backup that I made. And wasn't able to do so because it told me M.D.5 sum mismatch after I reverted to it earlier in the day. Huh is what I was like and after that clockwork mod recovery would let me restore a cm10 backup I made said something about couldnt restore system. So out of frustration I went back to being unrooted. Just couldn't take the problems with clockwork mod because that's what where the problems ly. It wasn't me it was the recovery
Sent from my SGH-T999 using xda premium

jasonren29 said:
Did you changed the backup in any format? Change name or date? Any minor changes to the backup will fail md5 check
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
None what so ever. I really just flashed the stock back up right before I flashed my gsfree back up so no I made no changes what also ever. Some times when you format systems in clockworkmod recovery this could happen because it happen to me. Can't wait till ext4 touch recovery comes to us here in this forum. Not saying cwm recovery isn't nice but I never had any problems with other recoveries that have been offered.
Sent from my SGH-T999 using xda premium

einrae214 said:
No lie I formatted my system the other day and right after tried to revert to a stock android backup that I made. And wasn't able to do so because it told me M.D.5 sum mismatch after I reverted to it earlier in the day. Huh is what I was like and after that clockwork mod recovery would let me restore a cm10 backup I made said something about couldnt restore system. So out of frustration I went back to being unrooted. Just couldn't take the problems with clockwork mod because that's what where the problems ly. It wasn't me it was the recovery
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
There are ways to fix that issue with the MD5 sum mismatch. I've had it happen a few times and ran a few commands thru ADB and got it working.

Kid Poker said:
There are ways to fix that issue with the MD5 sum mismatch. I've had it happen a few times and ran a few commands thru ADB and got it working.
Click to expand...
Click to collapse
Yes you are right. But I didn't want to go thru all of that. Really didn't have time so just unrooted my phone so there would be no more problems. I get like alot of people and become flash aholics. So I just stop it from being problem later down the road. Look I like rooting and adding mods to my phone like the next guy but there comes to a point where unnecessary issues can be avoided. Like the one I had.... but on the real tip I really enjoy the phone just the way it is STOCK I have zero issues and love the battery life that I have. So until some cooler roms come out I just don't have interest in cm9 or cm10 base roms. I mean I came from the sensation where I could flash a lot more variety of roms. I like this phone the way it is and really that's why I bought it.
Sent from my SGH-T999 using xda premium

Latest CWM?

I have been running AOKP ICS for a while now and I had TWRP as my recovery. Well after flashing around a bit I had to reflash a rom and was unable to inject TWRP for it to boot. As a result I have CWM 6.0.1.3 I think. Is this the latest and why would I have a backup fail to create a MD5, therefore rendering that backup useless? CWM seems fine for flashing and wiping, but backups are super important. Any help would be awesome!
sent from the other woman

bryanfritz1 said:
I have been running AOKP ICS for a while now and I had TWRP as my recovery. Well after flashing around a bit I had to reflash a rom and was unable to inject TWRP for it to boot. As a result I have CWM 6.0.1.3 I think. Is this the latest and why would I have a backup fail to create a MD5, therefore rendering that backup useless? CWM seems fine for flashing and wiping, but backups are super important. Any help would be awesome!
sent from the other woman
Click to expand...
Click to collapse
6.0.1.3 is the latest and I know, it can't make a nandroid backup
If you want make a backup on CWM just back to 5.0.2.7
Or use TWRP, I like TWRP
Sent from my SPH-D700 using xda app-developers app

Dropple said:
6.0.1.3 is the latest and I know, it can't make a nandroid backup
If you want make a backup on CWM just back to 5.0.2.7
Or use TWRP, I like TWRP
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
What is the point of a "RECOVERY" if it cant make backups? WTF over. confused

zman519 said:
What is the point of a "RECOVERY" if it cant make backups? WTF over. confused
Click to expand...
Click to collapse
I'm kinda in the same boat. I ran into this issue when I was trying-out CM9. Now I'm on CM10 9/14 Nightly, which installed with CWM 6.0.1.3. I'm ready to flash the NS4G modem AIO and give it a spin now that the roaming issue is fixed. However, I want to be safe about it and run a nandroid backup first. If I can't restore my nandroid using CWM 6.0.1.3, can I use 5.0.2.7 with CM10?
Can I just CWM flash 5.0.2.7 over 6.0.1.3 or am I better off flashing TWRP?
Thanks in advance,
Al

Why does cm roms install a recovery any ways?!? I remember back in froyo rom days around hear. Some Devs *****ing about roms installing recoverys & apks to /data/ every one at that time came to agree that Roms SHOULD NOT INSTALL A RECOVERY.
I mean if a new cm rom needs a new cwm recovery then FLASH the new recovery reboot recovery & flash the rom
Rocking cm9.1

zman519 said:
Why does cm roms install a recovery any ways?!? I remember back in froyo rom days around hear. Some Devs *****ing about roms installing recoverys & apks to /data/ every one at that time came to agree that Roms SHOULD NOT INSTALL A RECOVERY.
I mean if a new cm rom needs a new cwm recovery then FLASH the new recovery reboot recovery & flash the rom
Rocking cm9.1
Click to expand...
Click to collapse
Believe it had to do MTD. Last I read about this, been a while, the 5.5 version of CWM was specifically for MTD and the 5.0 version was BML. I could very well be incorrect, but that's what I recall reading a while ago.

5.0.2.7 works on MTD
IDK I just miss having the cmw flashable cwm recovery zips. Luckely I have got gotten in to a pickle like many have
Rocking cm9.1

nikon120 said:
Believe it had to do MTD. Last I read about this, been a while, the 5.5 version of CWM was specifically for MTD and the 5.0 version was BML. I could very well be incorrect, but that's what I recall reading a while ago.
Click to expand...
Click to collapse
OK -- Now I get why I couldn't flash 5.0.2.7 over 6.0.1.3 when I was trying to get back out of CM9 a month or so ago. However, I ended up Odining back to stock and installed TPR MTD and I could swear that I ended up with CWM 5.0.2.7 on MTD.
I'm soooo confused.....
I just want to make a restorable nandroid of my CM10.
Thanks,
Al

zman519 said:
Why does cm roms install a recovery any ways?!? I remember back in froyo rom days around hear. Some Devs *****ing about roms installing recoverys & apks to /data/ every one at that time came to agree that Roms SHOULD NOT INSTALL A RECOVERY.
I mean if a new cm rom needs a new cwm recovery then FLASH the new recovery reboot recovery & flash the rom
Rocking cm9.1
Click to expand...
Click to collapse
Oh ya?, TWRP can flash cm9/cm10, without need a new recovery like 6.x CWM
Sent from my SPH-D700 using xda app-developers app

Are you guys actually having trouble with backups? I backup and restore with 6.0.1.3 almost every day.
Sent from my SPH-D700 using xda app-developers app

bbelos said:
Are you guys actually having trouble with backups? I backup and restore with 6.0.1.3 almost every day.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Yup. I've never been able to restore a nandroid using 6.0.1.3. I always get an MD5 checksum error. To be honest, I haven't tried in a while, but that was my experience a month or so ago when on CM9. I have no idea if the problem lies in the CWM backup or the restore process.
I'll give it another shot now to see if I can backup and restore my CM10. Stay tuned.
Edit ----
Well, Ahhhl be! (my best Gomer Pyle impression -- you youngsters can Google Gomer Pyle). I ran a nandroid in 6.0.1.3 and advance-restored data successfully. I don't understand what all the complaining is about....
Al

bbelos said:
Are you guys actually having trouble with backups? I backup and restore with 6.0.1.3 almost every day.
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
No problems hear. Just confused as to why roms now days install recovery?
BTW your Kernels are the Shizt
Rocking cm9.1
---------- Post added at 12:45 PM ---------- Previous post was at 12:40 PM ----------
arschend said:
Yup. I've never been able to restore a nandroid using 6.0.1.3. I always get an MD5 checksum error. To be honest, I haven't tried in a while, but that was my experience a month or so ago when on CM9. I have no idea if the problem lies in the CWM backup or the restore process.
I'll give it another shot now to see if I can backup and restore my CM10. Stay tuned.
Edit ----
Well, Ahhhl be! (my best Gomer Pyle impression -- you youngsters can Google Gomer Pyle). I ran a nandroid in 6.0.1.3 and advance-restored data successfully. I don't understand what all the complaining is about....
Al
Click to expand...
Click to collapse
I know that just about every time I have had problems nandroiding my sdcard was on the way out:banghead:
I forget the name of the program (Windows) but it has a Black Cats face (head shot) for in icon & its really good at testing flash media.
Rocking cm9.1