hello,
i wanted to try out new 1.7.15 and did full backup of my nandroid... now if i try to restore i get an md5 mismatch...
i renamed the backup at pc to romname... can i do anything to rescue my backup....?
edit:
can i flash each .img maybe via fastboot ?
when you rename your backup make sure there are no spaces in the name or recovery will not read the backup thus you having md5 mismatch
your my personal hero today :* - thanks, works fine now.
After making full backup using cwm is there a way to make sure the md5 is correct, the way I have been doing it is do a backup and then do a full restore which checks the md5 at restore time. It would be nice just to do the md5 checking and then give you the option to continue. I have not found if it can be done. Thanks
Sorry if this is the wrong place. I have made several nandroid backups using Philz Touch recovery (6.0.4.7 i believe) and my ROM is Negalite Wonderom NG2 v3. All of the backups fail the MD5 check. I have made the backups from both the recovery and an app (online nandroid backup). I looked at the backups using nandroid manager, and the same file causes the backups to fail the md5 check. After re-generating the md5sum using nandroid manager, then immediately checking them via the in-app verify function, the same file (system.ext4.tar.gz.a) fails the check. Why is this, and how can I fix it? Any help would be appreciated.
I lost my phone's IMEI trying to do a backup of it, and also lost my baseband. Backups of IMEI didn't work, and also the backup of the rom made with Nandroid backup.
I wanted to copy the folder EFS, cauase someone recommended to backup the IMEI this way. I did it by ES File Explorer, but when copying the folder EFS, appeared an error message like this: "Failed to copy NVRAM" or something like that.
I do not know if it happened in this process or if the EFS folder had already corrupted with other IMEI backups made with various applications (backups that did not serve me at all). Considering that my IMEI continued null / null when I tried to restore them with a lot of applications (Partitions Backup & Restore, Samsung Tools etc)
Maybe it's important to say that before attempting to restore the IMEI by several backups I had done before tried to install other modems to see if the network appears again. But did not.
Finally, I reinstalled the rom stock by Odin and nothing resolved. I continue with the IMEI issue null/null and unknown baseband.
My last attempt was to restore the backup I made the rom the first day I picked up the phone.
The backup I made with Online Nandroid Backup application. Be safe with this backup because on any topic roms here from XDA, the developers says "Do a nandroid backup first." And that's what I did.
In momement when I did the backup with this application, my recovery installed was Philz Recovery (which is based on CWM), it may be important to say that.
But anyway, the backup is saved on my PC, and I had not needed to use it, and thought it would work when I needed it, but it did'nt work.
Once installed the rom again by Odin, did root, and installed the same Philz Recovery (to have less doubt that the backup can be restored without problems with Nandroid Manager), but it didn't work.
I created a folder called "backup" in the clockworkmod folder "and put my backup there (one who has the time and date of creation in the name).
And when I tried to restore the backup by Nandroid Manager application, the only thing that happens is the phone to reboot, without even access at first the recovery. So the backup can't be restored again.
Then I converted the file to ".zip" and I went to recovery and tried to install it, also failed. It appeared some problem related to the "MD5".
So I installed CWM Recovery (not Philz) and tried to restore the backup with Nandroid Manager, did not work, the phone again, just restarted. So I tried to install the backup as a ".zip" from CWM Recovery, and again, there was a new message regarding the "MD5".
So I installed TWRM Recovery, and tried to restore the backup by Nandroid Manager (but the application said the backup was originated by CWM and it could not be restored by another recovery) then I tried installing the ".zip" file by TWRM recovery, and gave some kind of failure, can not remember exactly what, but I think also related to "MD5".
So I tried to fix the problem related to MD5, I saw some threads on XDA saying how to do ... basically tried two methods.
The first attempt was to delete the file "Nandroid.MD5" by Root Explorer and create a new file with the same name and with the same extension.
So I tried again to restore the backup by Nandroid Manager (with Philz Recovery and CWM Recovery), but also failed. Also failed to install a ".zip" file driectly by the recovery with the new file "nandroid.MD5" created. This file ".zip" with MD5 file "probably fixed" I tried to install with the 3 recoveries already mentioned. Did not work. It continued an error related to "MD5".
The second attempt was to try to correct the "MD5" file with the Terminal Emulator, by this commands:
su
# Mount -o remount rw / sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
# md5sum * img> nandroid.md5
Again, I tried to restore the file by Nandroid Manager (with philz Recovery and CWM Recovery) ... And also tried to restore the file ".zip" by both recoveries,includint TWRP Recovery. Nothing worked.
In the backup name has no spaces. And the files inside it are:
boot.img
cache.ext4.tar
data.ext4.tar
efs.ext4.tar
modem.img
recovery.img
recovery.log
system.ext4.tar
I have a backup intact without modification for future experiments.
I do not know what else to do, I just want to restore the backup to see if the network went back, with my IMEI and my baseband losted.
-
I tried to do the right things and looks like it was worse than if I had done nothing.
For example, trying to save the EFS folder by ES Explorer, apparently that destroyed this folder.
But before It had already made a backup of the rom, but I can not restore it.
It would was better If I did nothing to try to forearm... Cause for now I do not know what to do whit these problems...
My last step will be to gather cash to buy a box to put my IMEI back to the phone... = (
Sorry for my Inglês... Translated by Google Translator.
My phone is SM-N9005.
LeandritoG said:
I lost my phone's IMEI trying to do a backup of it, and also lost my baseband. Backups of IMEI didn't work, and also the backup of the rom made with Nandroid backup.
I wanted to copy the folder EFS, cauase someone recommended to backup the IMEI this way. I did it by ES File Explorer, but when copying the folder EFS, appeared an error message like this: "Failed to copy NVRAM" or something like that.
I do not know if it happened in this process or if the EFS folder had already corrupted with other IMEI backups made with various applications (backups that did not serve me at all). Considering that my IMEI continued null / null when I tried to restore them with a lot of applications (Partitions Backup & Restore, Samsung Tools etc)
Maybe it's important to say that before attempting to restore the IMEI by several backups I had done before tried to install other modems to see if the network appears again. But did not.
Finally, I reinstalled the rom stock by Odin and nothing resolved. I continue with the IMEI issue null/null and unknown baseband.
My last attempt was to restore the backup I made the rom the first day I picked up the phone.
The backup I made with Online Nandroid Backup application. Be safe with this backup because on any topic roms here from XDA, the developers says "Do a nandroid backup first." And that's what I did.
In momement when I did the backup with this application, my recovery installed was Philz Recovery (which is based on CWM), it may be important to say that.
But anyway, the backup is saved on my PC, and I had not needed to use it, and thought it would work when I needed it, but it did'nt work.
Once installed the rom again by Odin, did root, and installed the same Philz Recovery (to have less doubt that the backup can be restored without problems with Nandroid Manager), but it didn't work.
I created a folder called "backup" in the clockworkmod folder "and put my backup there (one who has the time and date of creation in the name).
And when I tried to restore the backup by Nandroid Manager application, the only thing that happens is the phone to reboot, without even access at first the recovery. So the backup can't be restored again.
Then I converted the file to ".zip" and I went to recovery and tried to install it, also failed. It appeared some problem related to the "MD5".
So I installed CWM Recovery (not Philz) and tried to restore the backup with Nandroid Manager, did not work, the phone again, just restarted. So I tried to install the backup as a ".zip" from CWM Recovery, and again, there was a new message regarding the "MD5".
So I installed TWRM Recovery, and tried to restore the backup by Nandroid Manager (but the application said the backup was originated by CWM and it could not be restored by another recovery) then I tried installing the ".zip" file by TWRM recovery, and gave some kind of failure, can not remember exactly what, but I think also related to "MD5".
So I tried to fix the problem related to MD5, I saw some threads on XDA saying how to do ... basically tried two methods.
The first attempt was to delete the file "Nandroid.MD5" by Root Explorer and create a new file with the same name and with the same extension.
So I tried again to restore the backup by Nandroid Manager (with Philz Recovery and CWM Recovery), but also failed. Also failed to install a ".zip" file driectly by the recovery with the new file "nandroid.MD5" created. This file ".zip" with MD5 file "probably fixed" I tried to install with the 3 recoveries already mentioned. Did not work. It continued an error related to "MD5".
The second attempt was to try to correct the "MD5" file with the Terminal Emulator, by this commands:
su
# Mount -o remount rw / sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
# md5sum * img> nandroid.md5
Again, I tried to restore the file by Nandroid Manager (with philz Recovery and CWM Recovery) ... And also tried to restore the file ".zip" by both recoveries,includint TWRP Recovery. Nothing worked.
In the backup name has no spaces. And the files inside it are:
boot.img
cache.ext4.tar
data.ext4.tar
efs.ext4.tar
modem.img
recovery.img
recovery.log
system.ext4.tar
I have a backup intact without modification for future experiments.
I do not know what else to do, I just want to restore the backup to see if the network went back, with my IMEI and my baseband losted.
-
I tried to do the right things and looks like it was worse than if I had done nothing.
For example, trying to save the EFS folder by ES Explorer, apparently that destroyed this folder.
But before It had already made a backup of the rom, but I can not restore it.
It would was better If I did nothing to try to forearm... Cause for now I do not know what to do whit these problems...
My last step will be to gather cash to buy a box to put my IMEI back to the phone... = (
Sorry for my Inglês... Translated by Google Translator.
My phone is SM-N9005.
Click to expand...
Click to collapse
try this
plumzup67 said:
try this
Click to expand...
Click to collapse
This is for what?
LeandritoG said:
This is for what?
Click to expand...
Click to collapse
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
plumzup67 said:
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
Click to expand...
Click to collapse
Hi friend, reading this thread I think it isn't my case...
http://forum.xda-developers.com/showthread.php?t=2507403
Buy thanks anyway... =)
plumzup67 said:
It will restore things you lost just try it you got nothing to lose
Sent from my SM-A800F using Tapatalk
Click to expand...
Click to collapse
Well, I tried flash it two times... Continues with imei null and unknown baseband...
Now I will try this...
http://forum.xda-developers.com/showthread.php?t=2567133
You never backed up the EFS originally ??
Or if you did what tool did you use ??
Hey guys, I hope you could answer some questions about nandroid backup and custom/stock ROMS.
Currently I have installed on my Note 3 SM N900 Android Lollipop 5.0, it is a stock samsung ROM. I've never flashed a custom ROM before. Recently I flashed a Custom Recovery and Rooted my phone. I would like to install a CM 12.1 ROM, I really hate all the bloatware on samsung stock ROM (Although I used Root Uninstaller, I'd like a clean android OS).
Searching on Google I found that doing a Nandroid Backup is as easy as going into recovery mode (Custom Recovery) and make a Back Up of everything, I mean "boot, System, Data, Cache, EFS, Radios", that is how is showed on TWRP v2.8.7.0. But there are other things showing up below this options, like "enable compression, skip MD5 generation during back up, disable free space check"
which options do I need to select if a want to make a full nandroid backup?
what does "skip MD5 generation during back up, disable free space check" options mean?
let's say I do a full nandroid backup, and a EFS folder (which I did the second I rooted my phone), and then I flash a Custom ROM, but there are too many bugs, or I just miss samsung stock ROM and I wanna go back to my previous ROM.
I'd just need to enter in recovery mode and do a restore of my previous nandroid backup (a stock ROM backup) and that's it? It'd be that simple? I'm thinking I'm missing something here.
Hope you can answer these doubts of mine. Thanks in advanced! :good:
YES Its that simple backup to ext sd card restore that backup .
.
"skip MD5 generation exactly what it says it generated no MD5 signature ( see Google md5)
Skipping MD5 generation means that you won't be able to check file integrity when restoring it. Not advised.
Disable free space check means that recovery won't check if it can store the backup files in the available space. Again, not advised.
totalnoob34 said:
Skipping MD5 generation means that you won't be able to check file integrity when restoring it. Not advised.
Disable free space check means that recovery won't check if it can store the backup files in the available space. Again, not advised.
Click to expand...
Click to collapse
JJEgan said:
YES Its that simple backup to ext sd card restore that backup .
.
"skip MD5 generation exactly what it says it generated no MD5 signature ( see Google md5)
Click to expand...
Click to collapse
Thank you very much for answering my questions!