I moved my nandroid files onto my PC and moved back to the phone and now I can't restore my nandroid backup flashing from the recovery screen, what the heck am I doing wrong
can I just adb push the backup?
Chad
make sure the path to your backup is correct then try re flashing the recovery image. either that or your backup got corrupted when you copied it. this has happened to me a few times..
thedudejdog said:
make sure the path to your backup is correct then try re flashing the recovery image. either that or your backup got corrupted when you copied it. this has happened to me a few times..
Click to expand...
Click to collapse
yeah...definitely not doing that again (removing the backups from phone)
oh well starting off again w/ an untouched 2.2 MoDaCo...and now taskiller for w/e reason is killing my 3g/mobile connection every time I use the widget, never had that issue before.
Chad
Did you copy the Nandroid folder into the SD root? I've copied the Nandroid folder to the computer plenty of times and transfered back over to the phone with no problems.
Hello,
When I try to resore my nandroid backup with the google nexus 7 toolkit (by mskip) after the files are pushed It says that i must click on "backup and resore" and than "restore" (in cwm recovery). When i do that I get the error "could't open directory. No files found". I tried to reboot into recovery a couple of times, but nothing changed. I also clicked on "fix permissions", but that didn't help too. Could someone please help a poor noob trying to restore his nandroid backup?:fingers-crossed:
Anyone?
Where are the files being pushed? I believe CWM needs them in /data/media/clockworkmod, not /sdcard/clockworkmod.
Thanks for your reply,
After looking at your reply, I put my backup in the folder you mentioned and tried to do the restore. Sadly, that did not work. So I tried to make a backup of the rom I was currently running to see where that gets saved. Seems to be a "backup" folder in the folder you mentioned. after moving the backup there it worked fine, thanks.
I am not sure why but when I backup using TWRP Recovery it completes successfully but there is nothing written to the Data partitions. If I try to backup just the data I get a 25 MB file. It should be nearer to 6 GB. Whats more weird is the backup did work a while back and if I restore to that one I can make one more backup with Data included. After that one it stops backing up the Data partition again. Has anyone had an issue where Data is not actually being backed up even though it is selected and shows successful? Any thoughts?
I have a stock rooted Sprint Galaxy S4 on NAE. I have not taken the update.
Update: I tried updating from TWRP 2.6.3.1 to 2.8.0.1. That did seem to resolve the problem but left a new issue. After the backup is complete I always go to the file explorer in TWRP and make sure its there, which is was. But with 2.8.0.1 after I reboot the backup is gone. So I backed up again, and again checked the file explorer and it was there, powered the phone off and put the sd card in my pc and I can see the backup is there. Put the card back in my phone and turn it on, and the backup is gone. ???????
So I tried a different version of TWRP recovery. I installed 2.7.1.0 this time and now I'm back to the original issue. The backup is made, and I can see it again after the phone reboots but there is no data partitions being backed up even though during the process it says it is.
I have attached the TWRP log for assistance. The log shows it wrote quite a bit to data.ext4.win000 but this is 0 bytes in the backup directory. At the top of the log it says "Total size of all data: 7438MB" which I believe is accurate since my last good backup with data was 6.5GB. At the end of the log it says "Data backup size is 5052MB" but the directory properties show the backup size is really 2.2GB. This is because nothing is written to the data archive.
Could someone please help?
Anyone?
I noticed this same thing of 0 byte with data.ext4.win000 file in my TWRP backup 2.7
Viper41086 said:
Update: I tried updating from TWRP 2.6.3.1 to 2.8.0.1. That did seem to resolve the problem but left a new issue. After the backup is complete I always go to the file explorer in TWRP and make sure its there, which is was. But with 2.8.0.1 after I reboot the backup is gone. So I backed up again, and again checked the file explorer and it was there, powered the phone off and put the sd card in my pc and I can see the backup is there. Put the card back in my phone and turn it on, and the backup is gone. ???????
So I tried a different version of TWRP recovery. I installed 2.7.1.0 this time and now I'm back to the original issue. The backup is made, and I can see it again after the phone reboots but there is no data partitions being backed up even though during the process it says it is.
I have attached the TWRP log for assistance. The log shows it wrote quite a bit to data.ext4.win000 but this is 0 bytes in the backup directory. At the top of the log it says "Total size of all data: 7438MB" which I believe is accurate since my last good backup with data was 6.5GB. At the end of the log it says "Data backup size is 5052MB" but the directory properties show the backup size is really 2.2GB. This is because nothing is written to the data archive.
Could someone please help?
Click to expand...
Click to collapse
I noticed this same thing of 0 byte with data.ext4.win000 file and similar other conditions in my TWRP backup 2.7 on N7100 DN3 5.5. I am worried there's some corruption with data partitions. I have then redone the TWRP backup without compression and now the file is of reasonable size. Earlier my phone had gone into sudden bootloops for no apparent reason. Only after I changed the battery (which I had thought was the lamest thing to try) did it come back to normal. My phone however seems very slow and wonky. Now I am going back to dealing with those more serious issues.
I had problems with TWRP also not backing up correctly. I'm not sure why that is the problem, but I use Clockworkmod due to this issue. TWRP was not backing up Touchwiz roms correctly so my restores never worked. It seemed to work fine for ASOP roms though. At any rate, I never found TWRP reliable and I recommend anyone I know to use old school CWM instead.
I had a problem with TWRP a long time ago. Can't remember exactly what it was. I just like TWRP because it's touch but I went with Philz recovery and it never fails and is also touch or you can use the volume keys to navigate along with customize the look. It's the best recovery in my opinion. You should flash Philz recovery.
Here's the link for the Sprint Galaxy S4
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/
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 ??
So the phone was going crazy with frequent FCs so I decided to wipe it clean and install a new Resurrection Remix ROM.
Did a nandroid with TWRP 2.8.x.x before wiping and now I have trouble restoring in the new ROM using titanium backup PRO. In TB, I can get to the app selection screen and when the loading bar appears, it never gets past 0%. But it just magically says restore completed after some time. None of the app I chose ever gets restored.
So now I'm trying to extract the apps and data on a PC, and copying them into the phone manually. Question is, how do I get my hands on the files (extensions *.win000,*.win001...) in the nandroid?
I'm not sure about extracting it on a PC as I've never tried, but I believe the archives are multi-part tar.gz files.
If all else fails, you can use an app like Nandroid Manager to browse/extract the contents of a backup.