I've been trying out some roms... I did The Base, restored to stock, followed by Slick, restored to stock, finally GINSIX.
Ginsix had a few qwerks so I decided to restore. The very first time I went back to stock after The Base, I got the MD5 mismatch thing, I followed the directions on how to delete it and create a new one from the command line... No big deal. Worked Perfectly. NOW HOWEVER, I have 3 backups (one after each restore) I get the MD5 mismatch for all of them even after recreating them. tried each of them 3 times even verified that it was creating the files with TotalCommander. So I decided to flash to stock with LGNPST. I downloaded it and followed the directions on the #lg-optimus-g irc channel but All of the options on LGNPST are greyed out and inaccessible. So What Do I Do? Thanks Everybody for helping me.
SOLVED!!!
I was using CWM v6.0.1.2 I upgraded it to v6.0.2.7 Touch v14.4.7 available with instructions HERE
After Rebooting to Recovery I disabled the md5 check... extras > misc nadroid setting > Toggle md5 checksum
After that it was a restore as usual. No issues.
EricErb said:
I've been trying out some roms... I did The Base, restored to stock, followed by Slick, restored to stock, finally GINSIX.
Ginsix had a few qwerks so I decided to restore. The very first time I went back to stock after The Base, I got the MD5 mismatch thing, I followed the directions on how to delete it and create a new one from the command line... No big deal. Worked Perfectly. NOW HOWEVER, I have 3 backups (one after each restore) I get the MD5 mismatch for all of them even after recreating them. tried each of them 3 times even verified that it was creating the files with TotalCommander. So I decided to flash to stock with LGNPST. I downloaded it and followed the directions on the #lg-optimus-g irc channel but All of the options on LGNPST are greyed out and inaccessible. So What Do I Do? Thanks Everybody for helping me.
Click to expand...
Click to collapse
Turn off md5 check.
Sent from my LG-E970
Which recovery are you using? The original non-touch cwm or one of sk8's touch recoveries?
Sent from my LG-E970 using xda premium
Neroga said:
Turn off md5 check.
Sent from my LG-E970
Click to expand...
Click to collapse
I didn't know that was an option. I'll see if I can figure that out.
Deaf Mute said:
Which recovery are you using? The original non-touch cwm or one of sk8's touch recoveries?
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
I was using the original non-touch but after upgrading to sk8's I figured it out.
Related
When I try to open Clockwork Recovery to flash roms, I keep getting the error
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I am running v. 3.0.0.8, it will not let me downgrade.
How would I get around this error?
try booting into CWM>advanced>toggle signature verification
odin coming your way if you want it fixed. Here is my collection of others work with my easy to follow walkt hrough if you need that. and at the bottom is a link to GizmoDroids post about CWR, it's very educational.
http://forum.xda-developers.com/showthread.php?t=1026746
Onlyonebowman said:
When I try to open Clockwork Recovery to flash roms, I keep getting the error
I am running v. 3.0.0.8, it will not let me downgrade.
How would I get around this error?
Click to expand...
Click to collapse
I get the same error, but I may be arriving at it from a different method. I'm new to this, so I wanted to get all the pieces together before flashing anything. I got rom manager from the market, the fixed cwm (not loaded yet), sc 2.9.2, and odin. I was looking at rom manager, and saw the option to "flash recovery" so I thought this would be a shortcut. I did it, and it says I have 3.0.0.8. So then I wanted to backup my current rom (stock). When I selected "create backup", it prompt for a name, then reboots (into recovery) and that's when I get that error. Recovery text is blue. When I select "apply update.zip", I get nothing but a blank screen with the triangle and droid image.
Another thing that concerned me was that the market description of rom manager says that samsung users have to flash a compatible kernel first. That made me nervous, because I didn't want to flash anything until I had a backup.
I get the feeling that using the 3/30 cwm fix will resolve that issue.
Sent from my SCH-I500 using XDA App
aaronDroid80 said:
I get the same error, but I may be arriving at it from a different method. I'm new to this, so I wanted to get all the pieces together before flashing anything. I got rom manager from the market, the fixed cwm (not loaded yet), sc 2.9.2, and odin. I was looking at rom manager, and saw the option to "flash recovery" so I thought this would be a shortcut. I did it, and it says I have 3.0.0.8. So then I wanted to backup my current rom (stock). When I selected "create backup", it prompt for a name, then reboots (into recovery) and that's when I get that error. Recovery text is blue. When I select "apply update.zip", I get nothing but a blank screen with the triangle and droid image.
Another thing that concerned me was that the market description of rom manager says that samsung users have to flash a compatible kernel first. That made me nervous, because I didn't want to flash anything until I had a backup.
I get the feeling that using the 3/30 cwm fix will resolve that issue.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes, following GizmoDroid's steps for the 3/30 cwm fix should help. The other thing that will help is leaving rom manager alone and not touching it at all. It no workie for our Fascinates right now. Neither does the orange cwm 3.0.0.8. But I believe I read that several of the devs want to start pushing toward that cwm. For now though stick with the 03/30 and don't touch rom manager for anything.
Is there any other app to use for backing up roms? Or should I just get the stock ea28 rom to keep as a backup?
Sent from my SCH-I500 using XDA App
aaronDroid80 said:
Is there any other app to use for backing up roms? Or should I just get the stock ea28 rom to keep as a backup?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I use titanium backup to backup my apps, sms backup for my text messages, sync my contacts to my gmail account, and now that these great devs have given us a working cwm that allows us to do nandroid backups and restores, you can use that to save a snapshot of pretty much your entire phone except I think I read somewhere it does not backup your kernel and modem.
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
I made a backup of my HTC EVO LTE Stock ROM in TWRP, I flashed CMX, now I want to go back to Stock, so I went to TWRP>Install, I can see my backup folder under /sdcard/TWRP/BACKUPS/name of backup.. but I when I select the folder it does not give me the option to Install it. It just opens as an empty folder. I did notice the folder is not in a .zip format. Is this the reason why? Did I miss something during the back up process? And if so, how can I fix it? Is it as easy as just converting the regular folder into a .zip folder then try to install it this way?.. Please tell me not everything is lost, lol.. Any suggestions are greatly appreciated.
onavarro said:
I made a backup of my HTC EVO LTE Stock ROM in TWRP, I flashed CMX, now I want to go back to Stock, so I went to TWRP>Install, I can see my backup folder under /sdcard/TWRP/BACKUPS/name of backup.. but I when I select the folder it does not give me the option to Install it. It just opens as an empty folder. I did notice the folder is not in a .zip format. Is this the reason why? Did I miss something during the back up process? And if so, how can I fix it? Is it as easy as just converting the regular folder into a .zip folder then try to install it this way?.. Please tell me not everything is lost, lol.. Any suggestions are greatly appreciated.
Click to expand...
Click to collapse
There should be a restore option on the main screen in twrp recovery. If you hit that it will allow you to choose what file you want to restore
Sent from my EVO using xda app-developers app
Seconded. Choose "restore" to restore nandroid backups.
krobinso2295 said:
There should be a restore option on the main screen in twrp recovery. If you hit that it will allow you to choose what file you want to restore
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I see that now!. I can see what the difference is now. THANKS SO MUCH! :laugh:
Hello I'm coming from clockwork mod and now using Twrp. I renamed my backup and when I go to restore my backup I do not see it in tarp>backups? Any ideas? Thanks in advance!
shane1diamond said:
Hello I'm coming from clockwork mod and now using Twrp. I renamed my backup and when I go to restore my backup I do not see it in tarp>backups? Any ideas? Thanks in advance!
Click to expand...
Click to collapse
You can't restore back up made in clockwork mod using twrp recovery.
Sent from my lair.
Need to Restore But Getting Black Screen
Okay so my situation is similiar to the OP.
I was running CM10 then a custom sense Rom.
I made an original backup, but when I restore it I get a black screen at boot.
Typically when I flash a Rom I have to fastboot flash the boot.img which is no biggie, but there's no boot.img that I can find in the twrp backup.
Might be just as easy to flash a stock Rom, but not sure exactly where to find one. Everything I've found is rooted or custom in some way.
Thanks in advance for any replies.
tankerkevo said:
Okay so my situation is similiar to the OP.
I was running CM10 then a custom sense Rom.
I made an original backup, but when I restore it I get a black screen at boot.
Typically when I flash a Rom I have to fastboot flash the boot.img which is no biggie, but there's no boot.img that I can find in the twrp backup.
Might be just as easy to flash a stock Rom, but not sure exactly where to find one. Everything I've found is rooted or custom in some way.
Thanks in advance for any replies.
Click to expand...
Click to collapse
Download the rom you are trying to restore, and fast boot that bootimg.
Sent from my EVO using Tapatalk 2
thicklizard said:
Download the rom you are trying to restore, and fast boot that bootimg.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
The ROM I'm trying to restore is the original state of my phone. Would this be a stock ROM with a versioning date of October 28th(the day I got my phone and made the backup), current stock ROMs, or launch stock ROMs. Basically will any boot.img work from a stock ROM?
I do see the boot sector being written during the restore process. There is a boot.something.win file in the backup folder for the backup. Can this be fastbooted? I'm a bit timid to try that, but thinking it may be worth a shot...
tankerkevo said:
The ROM I'm trying to restore is the original state of my phone. Would this be a stock ROM with a versioning date of October 28th(the day I got my phone and made the backup), current stock ROMs, or launch stock ROMs. Basically will any boot.img work from a stock ROM?
I do see the boot sector being written during the restore process. There is a boot.something.win file in the backup folder for the backup. Can this be fastbooted? I'm a bit timid to try that, but thinking it may be worth a shot...
Click to expand...
Click to collapse
I think this is what you would need
http://themikmik.com/showthread.php...oted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Just download the kernel/bootimg and fast boot it and you should be good to go
Sent from my EVO using Tapatalk 2
clockwork recovery f's up your misc partition on this phone.. DO NOT use clockwork mod recovery on this phone! it f ed up mine.. mines fixed now but it was a pain to fix
thicklizard said:
I think this is what you would need
LINK REMOVED SO I COULD POOST
Just download the kernel/bootimg and fast boot it and you should be good to go
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply, QuickWizard is very fitting. I actually got it after I finished going my own route though.
I grew a pair and went with my got and I went ahead and flashed the boot.emmc.win from the twrp backup in flashboot. It successfully got me booted and logged into the phone. That said the stock rom is so crappy...
But, I was having issues on CM10 with MHL, on a "stock rom with goodies" I was having radio issues with the latest firmawares, so now it's back to my rooted stock backup and I'm doing the HTC System OTA update... Should be interesting what happens next...
Again thank you all with the quick replies!
Ok. so long story short, I rooted, unlocked my bootloader, made a backup in cwm(when i went to restore it i got (md5 mismatch) and then proceeded to install the base .7. after starting installation i clicked reboot now and it's been stuck on the nexus 4 boot animation. Any ideas why?
I've also run into this issue. Havent managed to find any fixes so far. Done full wipes and flashes back to stock and back to base and back and back, no dice on anything I've tried.
Hell, sometimes the ROM decides to skip the semantics and locks up my phone during installation. Have to hard reset & flash backups.
Anyway, back to the point on hand -- I'd also greatly appreciate any input on this issue.
I'd recommended installing the flashable stock ROM available in The Development section. Then flash The Base without wiping anything.
Sent from my A500 using XDA Premium HD app
ChefAnt said:
Ok. so long story short, I rooted, unlocked my bootloader, made a backup in cwm(when i went to restore it i got (md5 mismatch) and then proceeded to install the base .7. after starting installation i clicked reboot now and it's been stuck on the nexus 4 boot animation. Any ideas why?
Click to expand...
Click to collapse
If you got md5 errors you're using an early release of cwm for us that doesn't work right. You need to update it to a good recovery if you can and flash that first. It will help with the wipe issues too. That recovery, if I'm not mistaken, had some issues wiping, too. sk8terwitskil put out a new one early this morning.
Sent from my LG-E970 using xda app-developers app