[Q] Can't Restore Nandroid Backup - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

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.

Related

Does it matter if i do my nandroid backup on CW3 or CW2?

CW 3.0.0.5 or cw 2.5.1.2?
Does it make a difference which I use to do my nandroid backups? I'm using Nebula which still requires flashing in CW 2.5...so that's why I ask.
Also I did a backup yesterday in each, and when I tried to restore from both they both said md5 checksum fail. I had to restore from an older backup. What would cause that?
Did you rename the backup? That messes it up.
I dont think the CWM version matters, I restored a backup from 2.5 in 3 after an upgrade
Yeah I renamed them. thanks for the answer on that.
When renaming don't use space and keep it simple some characters don't work (for me).
dito33
Not sure how it's done on the epic side of things, but nobody does nandroid backups in the captivate, vibrant, or i9k forums. Clockworkmod doesn't save the modems or kernals and such all the time so it doesn't back em up. Therefore you can be restoring a rom over a bad kernal flash, or incompatible modem, ect. Just keep the cw update.zip on the sd, odin to stock, use titanium backup to restore apps. Android ID changer to restore id and your good.

Anyone else experiencing unreliable CWM, Titanium backups?

Hi
In preparation for a flash to stock (a la undercover and efrant), I backed up twice via cwm and downloaded to my PC via the browser server and also carried out app backups to each of drop box and box using Titanium.
Having flashed a stock image as described, I find that neither cwm backup works (unexpected end of archive and md5 mismatch) and when I restore either Titanium backup the data for the Safe Notes app isn't restored.
So my question is mainly: how do I ensure a reliable backup?
Secondly, does anyone have any ideas how to restore my important Safe Notes data?
Sent from my Nexus 4 using xda premium

Can't Restore Backup TWRP

Last night I made a backup to try out a couple different ROMs, but I wasn't able to restore it. I chose compression and skip MD5 when creating the backup, but when I tried to restore it, it told me to deselect MD5 file check, even though it's unchecked. I looked everywhere within TWRP and nothing regarding MD5 is enabled except the "skip MD5 creation" when backing up.
TL;DR: I told TWRP not to make MD5 when backing up, when I went to restore it told me there was no MD5 even though verify was disabled.
Why am I unable to restore backups? And am I just stuck now? Do we need to use MD5 with TWRP?
Sent from my LG-D800 using XDA Free mobile app
Caught by the same thing
My solution was to just regen the md5sums. Use this one line after you start an adb shell in root mode and move into the folder containing your backup.
for i in *.win*; do md5sum $i > $i.md5 ; done
This will generate md5 files for your backup and you'll be able to restore.
or use philz touch recovery and enable twrp mode

[Q] Nandroid Error backup and restore

Device: Samsung Galaxy S4 (SGH-I337M)
Android:5.0.1
Rooted
cwm custom recovery touch version.
When I do a Nandroid backup it seems to do successfully but I see errors in the log file.
And when I restore using the same backup after it finishes restore process, all the services stop working (example: google.app ....)
I attach screenshots and log file for backup process.
Please explain why this is happening and how to fix it.
Thanks
Sam
____________
As lennyz & Reaper suggested I switched to twrp, both backup and restore are working smoothly.
Thanks for help.
CWM isn't updated anymore. So you should either swith to TWRP or Philz (thought Philz isn't updated anymore either but it still works).
Maybe that could fix it. Also make sure you have plenty of space left when you make a nandroid. Something like 5gb when you are on TW rom.
Use PhilZ, as it is based on CMW, so it should work with your backups. If you don't care about the backups anymore then go with TWRP. Haven't had any problems with TWRP so far.

IMEI null. Unknown baseband. EFS IMEI Backup by Wanam and Nandroid Backup didn't work

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 ??

Categories

Resources