Hey guys, I'm trying to restore my stock rooted ROM, but it keeps telling me md5 mismatch? I wiped everything and now have no idea what to do. Is it because there was a change in CWM recoveries when I backed it up? I had 3.0 ext when I backed those up and then I had upgraded to 4.0.0.2 afterwards.
How would I get around to doing this? Because I want to get the OTA update?
Anyone please help?
Did you rename your backup? There should be no spaces or special characters in the name of the backup.
pettigrew95 said:
Did you rename your backup? There should be no spaces or special characters in the name of the backup.
Click to expand...
Click to collapse
Damnit! Your right, I did rename it and never got to restore it until now, lmaoo, poor stock, left and forgotten but now needed. Thanks, I'll change the names later!
Mikeglongo said:
Damnit! Your right, I did rename it and never got to restore it until now, lmaoo, poor stock, left and forgotten but now needed. Thanks, I'll change the names later!
Click to expand...
Click to collapse
No problem. Glad I could help
It worked, now can I get the OTA update? Can I keep cwm? or do I need to go back to stock recovery? because that's going to be annoying...
Mikeglongo said:
It worked, now can I get the OTA update? Can I keep cwm? or do I need to go back to stock recovery? because that's going to be annoying...
Click to expand...
Click to collapse
You can use the LG Update Utility just make sure you have the latest G2x driver which you can get from LG. After it updates to GB you will have to NVflash again and install CWM etc etc. The link for the LG Updater is here along with the driver download: http://wwwstg.lg.com/us/mobile-phones/G2X-Driver/index.jsp
So like I said, do I have to go into stock recovery first? or can I leave cwm on there without it effecting the update process?
Mikeglongo said:
So like I said, do I have to go into stock recovery first? or can I leave cwm on there without it effecting the update process?
Click to expand...
Click to collapse
That I am not sure. I think you can do it with CWM still on there it might wipe it out though and restore factory recovery.
Which I wouldn't mind doing, just don't feel like instaling stock recovery
Mikeglongo said:
Which I wouldn't mind doing, just don't feel like instaling stock recovery
Click to expand...
Click to collapse
I followed the unlocker vid all the way through and have had no issues. To be safe I would recommend ditching the custom recovery and reinstalling the stock recovery.
It would seems some upgraded with no issues either way, but I have seen a ton of folks that have issues. There is one foolproof way.
I think I'll just do stock recovery tonight and then figure it out from there honestly, if I want to wait for OTA or manual, I'm worried to do it manually if I'm going to get it a brick or not
What if you get a MD5 mismatch but didn't rename a backup folder? Did nothing except wipe to flash a different rom, tried to go back to previous rom via nandroid restore and then get a MD5 mismatch?
nvm found a fix
g0dsgreen said:
What if you get a MD5 mismatch but didn't rename a backup folder? Did nothing except wipe to flash a different rom, tried to go back to previous rom via nandroid restore and then get a MD5 mismatch?
nvm found a fix
Click to expand...
Click to collapse
im having the same problem i was trying to restore from a stock back up and i keep getting md5 mismatch i have not changed the file name i have wiped everything multiple times i cant even flash a new rom i have tried three different ones each say cant open zip (bad) please help phone wont boot at all
Just a quick question regarding backups. I know we all have different steps when it comes to flashing roms, but how often should you make a nandroid backup?
96traxx said:
Just a quick question regarding backups. I know we all have different steps when it comes to flashing roms, but how often should you make a nandroid backup?
Click to expand...
Click to collapse
Everytime you are going to flash a zip from SD card or a new ROM. Basically anything that will modify your existing ROM except clearing /cache or dalvik-cache you don't need to nandroid but anything else it is highly recommended.
pettigrew95 said:
Everytime you are going to flash a zip from SD card or a new ROM. Basically anything that will modify your existing ROM except clearing /cache or dalvik-cache you don't need to nandroid but anything else it is highly recommended.
Click to expand...
Click to collapse
Thanks, I just recently went from stock to Xboarders rom & now I'm going to try Whitehawk's rom & I didn't want to have several backups of the stock rom on the card. Thanks again
thefurb said:
im having the same problem i was trying to restore from a stock back up and i keep getting md5 mismatch i have not changed the file name i have wiped everything multiple times i cant even flash a new rom i have tried three different ones each say cant open zip (bad) please help phone wont boot at all
Click to expand...
Click to collapse
If you have no rom to use and you can adb into the phone:
adb shell
changedirectory to the backup
rm nandroid.md5
md5sum *.img > nandroid.md5
If you do still have a rom you can boot into, go into terminal, su, change directory to where the backup is. then:
rm nandroid.md5
md5sum *.img > nandroid.md5
I searched and was just trying anything that I might think could help me. Found the instructions I'm giving you in one of the droid help forums. While our situations are not entirely the same, I do hope this works for you. Good luck.
Related
Hi,
I tried to modify the build.prop file of my LG Optimus 2X to simply disable the animation during the boot. It didn't really worked well because my cellphone is now looping during the boot. I think I saved the build.prop on my sdcard but now I don't know what to do...! I tried to hard reset and wipe date, but it's still no booting. I have clockwork mod instal.
Thank you!
EjasRus said:
Hi,
I tried to modify the build.prop file of my LG Optimus 2X to simply disable the animation during the boot. It didn't really worked well because my cellphone is now looping during the boot. I think I saved the build.prop on my sdcard but now I don't know what to do...! I tried to hard reset and wipe date, but it's still no booting. I have clockwork mod instal.
Thank you!
Click to expand...
Click to collapse
Well, first, I'd like to ask if you have a CWM backup of your system before you edited your build.prop? I assume that since you can wipe the data, you can reach CWM. If you can and have a backup, try recovering that backup and see if that works. If you do not, then you can always try to find an RUU (ROM update utility) that should return your phone to an unrooted, stock ROM. I don't know of any other options, all I can say now is become best friends with that search bar up there.
Hope you manage to get your phone back. :fingers-crossed:
revert to stock, oh just reflash whatever custom ROM you have been using (if you have any), you should be able to mount SD card from CWM and copy your ROM in there and flash away. I am under the assumption that since you were doing your DIY mods there, you should have knowledge of flashing back to stock or Custom Roms of choice. Good luck.
TekGadgt said:
Well, first, I'd like to ask if you have a CWM backup of your system before you edited your build.prop? I assume that since you can wipe the data, you can reach CWM. If you can and have a backup, try recovering that backup and see if that works. If you do not, then you can always try to find an RUU (ROM update utility) that should return your phone to an unrooted, stock ROM. I don't know of any other options, all I can say now is become best friends with that search bar up there.
Hope you manage to get your phone back. :fingers-crossed:
Click to expand...
Click to collapse
No I don't have a CWM backup :S Do you know where I could get a RUU for my phone?
EjasRus said:
No I don't have a CWM backup :S Do you know where I could get a RUU for my phone?
Click to expand...
Click to collapse
Here's a start. http://forum.xda-developers.com/showthread.php?t=1035041
The search bar on top is very useful if that doesn't help...
Foreverme89 said:
The search bar on top is very useful if that doesn't help...
Click to expand...
Click to collapse
That it is. Half of the time when helping people out, that is my starting point I'm really new to this, but know my way around a search engine and how to read
Boot into recovery, wipe cache and dalvik cache, and flash the same ROM you were already using
Sent from my MB508 using xda premium
do a full wipe or flash with the original rom
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
Hi,
So I used the Revolutionary method to s-off and root my phone - this was successful. I then made a full backup using Titanium and a few other things like SMS and contact backups, which are on my laptop now.
I then installed SVHD v1.7.4 using Clockworkmod v4.0.1.4. It ran fine, but try as I might I couldn't load my contacts and SMS back into it. So I tried to restore is back to the stock rom by going into Clockwork's Recovery, wiping cache, data and system.
When I tried to restore to a previous point, it gave me an error message saying system.img, data.img and so on not found, so all restore has been skipped. Now I'm stuck at the 3 splash screen. I can still get into the bootloader though, and can potentially install SVHD again as it's still on the SD card.
A quick search through the forums shows users with similar problems from 2012, but I'm afraid of buggering up my phone further so I'm hoping someone could be so kind as to walk me through what I need to do.
xTheLostProphetx said:
Hi,
So I used the Revolutionary method to s-off and root my phone - this was successful. I then made a full backup using Titanium and a few other things like SMS and contact backups, which are on my laptop now.
I then installed SVHD v1.7.4 using Clockworkmod v4.0.1.4. It ran fine, but try as I might I couldn't load my contacts and SMS back into it. So I tried to restore is back to the stock rom by going into Clockwork's Recovery, wiping cache, data and system.
When I tried to restore to a previous point, it gave me an error message saying system.img, data.img and so on not found, so all restore has been skipped. Now I'm stuck at the 3 splash screen. I can still get into the bootloader though.
A quick search through the forums shows users with similar problems from 2012, but I'm afraid of buggering up my phone further so I'm hoping someone could be so kind as to walk me through what I need to do.
Click to expand...
Click to collapse
Have you make a nandroid backup
in recovery?- sorry i didn`t see it mentioned,...
if you haven`t, then there is nothing to restore...
system ( the whole nand image ) could only be restored,
when it was previously been written...
try to mount sd card- while in recovery,
and look for: Clockworkmod/backups/.....
if there is nothing, i`m afraid you`re ......
asgardr said:
Have you make a nandroid backup
in recovery?- sorry i didn`t see it mentioned,...
if you haven`t, then there is nothing to restore...
system ( the whole nand image ) could only be restored,
when it was previously been written...
try to mount sd card- while in recovery,
and look for: Clockworkmod/backups/.....
if there is nothing, i`m afraid you`re ......
Click to expand...
Click to collapse
Ah sorry, I forgot to mention. Yes, I have two backups in CWM. Neither of which seem to work.
xTheLostProphetx said:
Ah sorry, I forgot to mention. Yes, I have two backups in CWM. Neither of which seem to work.
Click to expand...
Click to collapse
have you been changing recovery version lattely?
what i mean is: if you have, then try to revert back
to the version you used to create nandroid with,
and if you haven`t, then try to grab 4ext recovery-
possibly newest release you can put your hands on,
and try to restore nandroid from there...
...there is also a tool called:
< CWM2update.zip.creator > by @ss429842,
that may partly be a cure for your trouble- perhaps....
asgardr said:
have you been changing recovery version lattely?
what i mean is: if you have, then try to revert back
to the version you used to create nandroid with,
and if you haven`t, then try to grab 4ext recovery-
possibly newest release you can put your hands on,
and try to restore nandroid from there...
...there is also a tool called:
< CWM2update.zip.creator > by @ss429842,
that may partly be a cure for your trouble- perhaps....
Click to expand...
Click to collapse
I don't think I've changed the recovery version, no. But I clearly did something very wrong. I couldn't access my SD card as it's internal and I was afraid I was stuck.
What I've done instead is find the SVHD zip file and installed that. Hopefully this will work and I can at least turn my phone on and proceed from there. It sucks being a noob!
Well, me being me, screwed up rooting this thing by putting the wrong system.img.gz version into my B1-710. Is there a way to fix this bootlooping or not?
Shark0727 said:
Well, me being me, screwed up rooting this thing by putting the wrong system.img.gz version into my B1-710. Is there a way to fix this bootlooping or not?
Click to expand...
Click to collapse
80% not ...
on the other side if you replace files from your stock system.img to the one which you just flashed, and than flash it again after replacing files..
You may be able to save your data and boot.
Else you can save your data by taking a CWM backup, and again flashing your ROM and from advance restore, Restore data only.
droid-devz said:
80% not ...
on the other side if you replace files from your stock system.img to the one which you just flashed, and than flash it again after replacing files..
You may be able to save your data and boot.
Else you can save your data by taking a CWM backup, and again flashing your ROM and from advance restore, Restore data only.
Click to expand...
Click to collapse
I see but, I didn't take a CWM backup or get my stock system.img. As well, I havent found the clockwork recovery for the B1-710. I do have a sd-card for it. But all I require is the firmware for it. Anything on that?
I made a backup with the stock "android recovery 3e". Anyway to extract it? It's a ".backup" file and I can't open it whatever i try. It's not a nandroid backup, but with an "backup" extension. I've been searching for three days now and so far haven't found anything. There were some other threads with the same topic too but no solution was posted. Any help would be greatly appreciated, thanks.
How big is the file?
orangekid said:
How big is the file?
Click to expand...
Click to collapse
It's about 3gb.
Blufloyd said:
It's about 3gb.
Click to expand...
Click to collapse
Can you use the same recovery to restore this nandroid file or is that not an option?
I am not finding anything on actually extracting it..
orangekid said:
Can you use the same recovery to restore this nandroid file or is that not an option?
I am not finding anything on actually extracting it..
Click to expand...
Click to collapse
It's not a nandroid file. I can restore it but it's not much of a help cause I forgot my lock pattern with wifi and data off. Debugging was not enabled and it's a new phone didn't even root it yet. I thought i'll just backup everything, factory reset and then extract my data from the backup file.
Now back to the point, i know there doesn't seem to be any way to extract it. Never made a backup with the stock android recovery before. I just needed to recover some imp photographs. Xda was my last resort lol.
Blufloyd said:
It's not a nandroid file. I can restore it but it's not much of a help cause I forgot my lock pattern with wifi and data off. Debugging was not enabled and it's a new phone didn't even root it yet. I thought i'll just backup everything, factory reset and then extract my data from the backup file.
Now back to the point, i know there doesn't seem to be any way to extract it. Never made a backup with the stock android recovery before. I just needed to recover some imp photographs. Xda was my last resort lol.
Click to expand...
Click to collapse
Is there any way at all to root it once you restore it? If it's a full system backup then it's a "nandroid" (which means a ROM backup whether stock or custom).
But yeah can't seem to find any way to extract it, only hope is to restore it and try to do something with the ROM.
orangekid said:
Is there any way at all to root it once you restore it? If it's a full system backup then it's a "nandroid" (which means a ROM backup whether stock or custom).
But yeah can't seem to find any way to extract it, only hope is to restore it and try to do something with the ROM.
Click to expand...
Click to collapse
Idk, aren't nandroid files .tar or .zip? I was thinking of doing that. But i had some doubts. Like will the custom recovery be able to restore this file? Because I'm pretty sure i've never seen a .backup file in cwm or twrp.
Blufloyd said:
Idk, aren't nandroid files .tar or .zip? I was thinking of doing that. But i had some doubts. Like will the custom recovery be able to restore this file? Because I'm pretty sure i've never seen a .backup file in cwm or twrp.
Click to expand...
Click to collapse
"nandroid" just means a ROM backup, doesn't matter which recovery or what the extension is.
I mean anything is worth a try at this point. I doubt any recovery will recognize it, but I am thinking use the recovery that made the file to restore it, THEN root that ROM if you can somehow. What phone do you have? Most older Samsung phones can be rooted in Odin regardless of the actual ROM state etc...
edit: moved to Android Q&A forum too...
orangekid said:
"nandroid" just means a ROM backup, doesn't matter which recovery or what the extension is.
I mean anything is worth a try at this point. I doubt any recovery will recognize it, but I am thinking use the recovery that made the file to restore it, THEN root that ROM if you can somehow. What phone do you have? Most older Samsung phones can be rooted in Odin regardless of the actual ROM state etc...
edit: moved to Android Q&A forum too...
Click to expand...
Click to collapse
No I can't root it after restoring. I'm locked out and there's nothing I can do about it. It's HTC desire 816g.