Related
I actually have two questions here.
I'm trying to do an advance restore of the data from a previous backup using CWM. recovery 5.0.2.7 and having some problems.
In recovery, when I click on 'advanced restore' I am told there are no files. I then choose the regular 'restore' option and it shows the files to choose from.
I can then go back one screen and select 'advanced restore' again and it will now display the list of backups. When I select a backup and try to restore the data, I get a MD5 mismatch error. This happens when I try to do an advanced restore with any of my backups, not just a certain one. Also, I can do a normal restore without any problems.
I tried this:
http://www.geekdevs.com/2011/10/solved-md5-mismatch-error-on-clockworkmod/
Then this:
http://forum.xda-developers.com/showthread.php?t=1606047
I've read several threads but most of them seem to be solved after trying one of the above methods. I also haven't seen any that describe the backup list not displaying at first.
Secondly, I found this problem because I'm running Pyr'o'Ice ICS Desensed 1.1.3 and stupidly tried to tether with wifi and my phone got stuck in a reboot loop. I want to restore the userdata via Nandroid recovery, but will that also restore the tether setting that causes that bug?
My main issue is with the Nandroid recovery, but I thought someone reading this might also know the answer to that question also.
Any help is greatly appreciated.
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
This doesn't appear to do anything
xmc wildchild22 said:
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
Click to expand...
Click to collapse
I'm having exactly the same problem as the OP, and I'm not sure how this will help as all md5sum does is give the md5s listed in the nandroid.md5 file. Using this method, all one is doing is putting the exact same md5s over what is there in the nandroid.md5 file.
I really need a method to make the Nandroid Advance Restore work in order to get back my data after updating to 1.63.531.2.
Any other suggestions? --
--
KingCheetah
y do u guys need to advanced restore...just restore
xmc wildchild22 said:
y do u guys need to advanced restore...just restore
Click to expand...
Click to collapse
Heh, well, in my case, I'm trying not to have to restore my phone from scratch after updating to 1.63.531.2, as well as keep the update. A straight restore will just take me back to DS Mod 1.55.531.3. Advanced Restore would allow restoration of data without overwriting the boot.img, system, etc.
So, no further methods to try to address this error?
--
KingCheetah
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
xmc wildchild22 said:
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
Click to expand...
Click to collapse
The md5s are already the same.
That also doesn't address the issue why I am told that there are no files found when I try the advanced restore option without first going to the regular restore and backing out.
Investigation ongoing, but an idea to help
paperskye said:
The md5s are already the same.
That also doesn't address the issue why I am told that there are no files found when I try the advanced restore option without first going to the regular restore and backing out.
Click to expand...
Click to collapse
This may have something to do with the way in which CWM 5.0.2.7 saves the majority of data to tar files instead of img files. This behavior of CWM is part of the discussion in this thread: http://forum.xda-developers.com/showthread.php?t=1624516
Yogi2010 made the suggestion of using the Modaco 4.0.0.9 recovery for backups that can be successfully used with Advanced Restore. I believe Modaco's AR works because it saves all data to img files.
I'm going to attempt an update to 1.63 using Modaco for backup and then AR of data afterward. If successful, we know that Modaco is the key for utilizing AR due to the file type it uses for data storage.
Why CWM 5.0.2.7 behaves as it does regarding AR remains an open question.
I'll report back to this thread with results after my update attempt --
--
KingCheetah
Modaco functional with Advanced Restore
I used the Modaco 4.0.0.9 recovery for my backup prior to updating to 1.63, then followed with an Advanced Restore of data afterward, which successfully restored my phone environment. So AR is functional with Modaco, but not CWM 5.0.2.7. I don't know for certain if the fact that CWM uses tar files has something to do with its inability to execute AR, but it certainly seems like this is a contributing factor.
I'm going to Google this and see if I can come up with any further info on CWM that might explain its behavior.
So far, it's Modaco FTW. Itz on my fone, reestoring my data --
--
KingCheetah
Did you use this to get Modaco? I noticed it says you must have s-off but in your thread you said you have s-on.
http://forum.xda-developers.com/showthread.php?t=1179125
My problem is that with the data I want to restore, my phone gets stuck in a boot loop. I am thinking that I might be able to install Modaco, restore the data where I can't start up my phone and then do a Modaco backup while still in recovery. Then restore a functioning backup (so my phone boots up) and finally do an advanced restore where I only restore the data I need from the bootloop backup.
paperskye said:
Did you use this to get Modaco? I noticed it says you must have s-off but in your thread you said you have s-on.
http://forum.xda-developers.com/showthread.php?t=1179125
Click to expand...
Click to collapse
That's the original thread Paul (Modaco's creator) posted. I downloaded my copy via Blue's invaluable Developers Reference: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7. Scroll down to the Recovery section, and under Clockworkmod 4.0.0.9 Recovery there's a download link; but it's the same file.
As to being s-off, I think that's how things used to be. Obviously, all you need now is the bootloader to be unlocked so you can fastboot flash the recovery img file. Otherwise, I couldn't have been doing all the monkeying I've been doing recently.
paperskye said:
My problem is that with the data I want to restore, my phone gets stuck in a boot loop. I am thinking that I might be able to install Modaco, restore the data where I can't start up my phone and then do a Modaco backup while still in recovery. Then restore a functioning backup (so my phone boots up) and finally do an advanced restore where I only restore the data I need from the bootloop backup.
Click to expand...
Click to collapse
My experience is limited, but from your description, I'm not sure if the Advanced Restore option will be the smoking gun for your problem. The way I understand it, ClockworkMod recovery--of which Modaco is an unofficial flavor--takes the equivalent of a disk image of your phone while the OS is inactive (like many disk imaging programs for the PC). If you've got some ratty data causing the boot looping, that data is going to be stored along with everything else in the snapshot during backup. It will also be restored using regular restore or Advanced. So, I'm not certain how using a different recovery module will accomplish your goal of stopping the boot loop. Also, remember that any backups made with CWM 5.0.2.7 will be incompatible with Modaco recovery since it uses only img files.
This definitely needs to go to someone more experienced in troubleshooting Android, I think. Maybe you could edit the title of this thread to reflect the boot looping problem. This will hopefully get someone like Blue involved to help out. Sorry not to have a definitive answer for this. I suppose you could flash Modaco (same as you flashed CWM 5.0.2.7) and see if it does what you're hoping it will do. Best advice I can give.
Apologies for not having a concrete solution, and best of luck --
--
KingCheetah
Same problem, with ANY restore
I'm running cwm 5.0.2.7 and can't restore any previous backups. When I run restore it restores a few things, but then it just stops and cwm recovery seems to abruptly reset. After that I get stuck on the splash screen after rebooting.I verified the md5s in the backup folder, also. All match.
I DID change the backup filename so I could find it easily in my backup folder, but it was doing the same thing even before I changed it.
Anyone else have the same issue?
Also, is there a way to restore the images through adb/fastboot, even though they were created by cwm recovery?
A small suggestion
IBtokin said:
I'm running cwm 5.0.2.7 and can't restore any previous backups. When I run restore it restores a few things, but then it just stops and cwm recovery seems to abruptly reset. After that I get stuck on the splash screen after rebooting.I verified the md5s in the backup folder, also. All match.
I DID change the backup filename so I could find it easily in my backup folder, but it was doing the same thing even before I changed it.
Click to expand...
Click to collapse
Check your backup filenames and make sure they don't have any spaces. If that isn't an issue, you might try reflashing CWM and see if that resolves its difficulties. CWM shouldn't be behaving as you describe if it has been installed properly. Only other thing I can think of is looking into any item installed on your phone that could possible not play nice with CWM. I don't know of any myself, but it's a possibility.
IBtokin said:
Also, is there a way to restore the images through adb/fastboot, even though they were created by cwm recovery?
Click to expand...
Click to collapse
Not that I know of; hopefully someone with more CWM knowledge will chime in on this thread.
Purrs --
--
KingCheetah
Hmm...I'll have to check to see if the old fastboot method can still be used.
---------------------------------------------------------------------------
Nope. Nandroid used to save the files in .img format instead of the current one. This means no fastboot restore.
Sent from Spaceball One.
Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors )
Reboot your phone and enter Recovery mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Credit goes to UsmanJ member. I have just shared with you guys with more good explanation.
Original thread HERE
Click to expand...
Click to collapse
No need these at all you need "root toolbox". and ut works perfectly by the way thanks for sharung this way too
Tapatalk 2 ile GT-I9003 cihazımdan gönderildi
If you do this you can't be sure that your backup isn't broken. md5 needs exactly for checking this. Yes, you cheated the check system, but are you sure that your backup integrity is fine?
This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.
silentvisitor said:
This problem is mainly due to folder name change. If you don't change folder name you shouldn't be having this problem.
Click to expand...
Click to collapse
Ya but sometimes we have to face this problem even if we dont change folder name like how it was happened in my case few days ago.
Well, I think this is no hint you should use. When creating a new backup md5 hashsums are calculated for each file. If you now want to restore it these hashsums are calculated again and compared to the previous ones. Only if the data is the same as before , in other words your backup hasn't been damaged, the checksums match. You may have had some luck that the error happened in a file that does not get used very often but in general you do not want to do that, just imagine your kernel backup is broken!
Sent from my GT-I9003 using XDA
Thanks, worked just fine for me.:good:
The error is not only because of changing the name of folder, as vishal says md5 mismatch can occur.
I even encountered the following problem with nandroid backup.
stock gb,xxkpu nandroid not compatible over cm9 or miui.
Or miui/CNET not compatible over stock rooted ROM.
I'm not sure of the reason why this error occurs while reporting the nandroid backup, but according to my limited knowledge of Android, I suppose either ext4 partition is not compatible over rfs of stock and vice versa or, out might be a kernel clash.
To be true, I didn't even try to search much about the issue as I'm mostly free and take the pain of customizing three new firmware as power my preference and reinstalling the app
Sent from my GT-I9003 using xda premium
If anyone is sure of the error and it's solution, the answer is most welcome.
P.s. while restoring out doesn't say md5 mismatch (I've also come across this though), the error I stated cannot restore the boot image atty the first place.
Sent from my GT-I9003 using xda premium
@ Iambalvindar
You are right bro. There can be number of reasons about this md5 mismatch error. Actually the solutuion which I have provided is just an option to correct error If error is due to other reason such corrupted backup then obviously the solution given in my thread will not be applicable.
The first two commands ('su' and 'mount') are not necessary because:
You don't need root permissions to edit stuff in /sdcard
/sdcard is always mounted as RW (that's what the second command does.)
EDIT:
I've just remembered that if you don't have busybox installed you don't have the 'md5sum' command avaible for the user.
However our CF-root kernels come with an inbuilt busybox, but it can't be used as normal user, because if I remember correctly all the symlinks are in /sbin, where the user has no access. So, probably, you need to do this as root (= type the 'su' command as in the OP).
Anyway, nandroid.md5 is the last thing made during a backup. That means if you don't have enough space for the backup and it stops, this file is not created. So, when you go to restore that backup, you have the mismatch error. In this case, if you create the nandroid.md5 as vishal wrote, you'll have a usable and damaged backup. So, before doing this, check if nandroid.md5 is there or, when you run "rm nandroid.md5", make sure the output is not "No such file or directory", because it means that most likely the backup is not complete.
All of these to say: be careful and do this if necessary (unless you know what you are doing of course).
A suggestion:
In this situation you can do an "advanced restore" and restore only /data and /datadata if you are using the same ROM you used for the backup (maybe a slightly different ROM is good too). The only things not restored are the mods you applied and system apps, but for the mods, simply reflash them, for the system apps, well, they are always the same. All the apps installed through the market are in /data.
Maybe this will cause bootloops, but in this case you can simply reboot in recovery and do a data wipe/factory reset. This will let you boot without the need of a reflash. You have of course to reinstal all your apps etc, but it's better than starting from scratch.
Or, even better, do a backup before the restore of /data and /datadata, so that in case of problems you can always restore everything.
EDIT 2:
I think you can do this even when you change ROM, as long as it's a stock ROM. That's because stock ROMs are intended to be flashed over another stock ROM and they are made in a way that you don't need to wipe your /data partition. When you use kies to upgrade, you don't loose anything. Restoring /data and /datadata should have the same effect (it's better to wipe the dalvik-cache after this).
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Ya its because different kernels have different cwm version & also different kernels creat different md5 code as per backup.
iAmBalvinder said:
@vishal: I'm not referring to corrupted backups. Sometimes later, even working backups fail to be restored after some ROM and kernel change.
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore from a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backup are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Cool, thx for the info. Nv knew the difference between the kernels
Sent from my GT-I9003 using xda app-developers app
loSconosciuto said:
I think you can do it, nandroid backups are the exact copy of the ROM you are running (the radio is not backed up).
The problem is that maybe you did a backup of Gingerbread using amit's CWM. His CWM is able to backup the kernel (normalboot.img), but he disabled this feature because he couldn't test it, so he thought it would be safer not to enable it. UC team however enabled it (that's what I can see from their recovery.fstab).
If you used amit's recovery to backup the ROM, when you restored it from CyanogenMod you didn't restore the kernel. So, when you turned the phone on, you tried to boot a stock ROM with a CM kernel.
Maybe if you flash a stock kernel after the restore with odin it will boot.
And if you tried to restore a CM backup (so with the kernel backed up) with amit's kernel, you didn't restore the kernel amit's recovery ignores it, so you tried to boot CM with a stock ROM kernel.
Maybe backups made from different CWM versions are not compatible, but I think Koush is trying to avoid this, but I'm not sure.
Another problem could be that CM is not yet finished and the continous changes in recovery cause new bugs that could affect the way backups are done (it recently happened).
Maybe I'm saying stupid things, but that's what I know. I'm not so interested in backups and restores, I rarely use them, so I've never tried to study well enough how they work etc. Correct me if I wrote something stupid.
Anyway, I'm sure that the md5sum error has nothing to do with the kernel you used to make the backup.
Every file has a unique md5 hash, it doesn't matter if you calculate it with your phone, with your computer or with your fridge (if you can ), the result is always the same. What CWM does before starting a restore is to re-calculate the md5 of each file inside /sdcard/clockwrockmod/backup/XXXXX/ and to compare them with the ones stored in /sdcard/clockwrockmod/backup/XXXXX/nandroid.md5 when you made the backup (open this file with a text editor and see). If they are all equal, it means the backup is not corrupted, so it's safe to start the restore.
I think you could even restore a backup of another phone (maybe there are some other check here and there to prevent this), but of course don't try it .
Click to expand...
Click to collapse
Yeah, most probably be that was the issue... Kernels needed to be changed.
Thanks
And I already saw that my backup was not corrupted with md5 check.
Moreover, I also don't use nandroid much, I always configure new ROM I try, from the scratch.
It's just that I needed to use USB storage urgently, which sadly doesn't work on any ics based ROM. So tried to restore the backup. Alas !
Had to flash again from scratch to get to stock gb, as I didn't have any gb.zip in sd card or computer.
Sent from my GT-I9003 using xda premium
i am not able to restore my backup due to mismatch md5
vishal24387 said:
Few days ago I faced MD5 mismatch error while restoring my backup after messed with my phone. But due to this error I couldn't restore backup. I asked many people but people said that I should now flash sock firmware which was really a headache for me.
Anyway I searched alot on xda & I found very easy solution.
It don't require pc or adb shell etc. It only requires rooted phone with Terminal Emulator app
STEP 1: Open Terminal Emulator
Step 2: Use the following commands. (DON'T FORGET TO REPLACE "2012-01-01.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME WHICH WILL BE PRESENT IN folder /clockworkmod/backup/)
Code:
su
#mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-01-01.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
STEP 3: (This will create a new "nandroid.md5" file without ANY "md5 mismatch" errors )
Reboot your phone and enter Recovery mode & then restore.
I hope it will help you in future
ENJOY...
IMP NOTE :- Many times people change backup folder name which can create this error. So be sure that you have not changed your backup folder name & also be sure that there is no space in backup folder path.
Click to expand...
Click to collapse
i was using another bootloader and another cwm
Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium
ganeshbiyer said:
Vishal, can you summarize every thing and update first post.
According to my understanding,
1. Do not change backup folder name.
2. Do not restore backup using different recovery than the one used, i.e. Use gb recovery to restore gb Rom, cm7 recovery to restore cm7 Rom and so on.
These are the main cause of md5 error, else better to assume the backup is corrupted.
Recalclating the md5 and restoring could have adverse effect on the system.
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
ok buddy I will update information in few minutes
I am still waiting for ur test kernel with modules inbulit in it.
I was on the same issue as all people with MD5 failure, then I rename my backup name with a short name with no space or blank and the it run like a charme !.
Hope it could help.
I created an update.zip with my apps+data using Titanium Backup (Pro) on 5.0.1 before I updated to 5.1. I then did a completely clean flash of the 5.1 image (following these instructions, method 2). After that, I did the basic setup of Android and installed Titanium Backup again from the store. I rebooted, flashed and booted into TWRP, then flashed SuperSU 2.46. Rebooted into the system, gave TiBu root access (since other threads said you need to do that before update.zip files can be flashed). Rebooted back into TWRP, finally try to flash update.zip, but I get the error below. Does anyone know why this would be the case?
Additionally, since receiving the error, I have installed busybox and tried fixing my SD card permissions in case they were the problem, no dice.
I do have all of the individual app backups on my computer if update.zip isn't going to work for some reason, and I took a full TWRP backup before upgrading as well (transferred all to my computer since the instructions clear personal data).
Error message:
Installing '/sdcard/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Failed to sysMapFile '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
UPDATE: Just discovered that Android is doing the "Optimizing apps" process at every single normal boot, whether I flash something or not.
vaindil said:
I created an update.zip with my apps+data using Titanium Backup (Pro) on 5.0.1 before I updated to 5.1. I then did a completely clean flash of the 5.1 image (following these instructions, method 2). After that, I did the basic setup of Android and installed Titanium Backup again from the store. I rebooted, flashed and booted into TWRP, then flashed SuperSU 2.46. Rebooted into the system, gave TiBu root access (since other threads said you need to do that before update.zip files can be flashed). Rebooted back into TWRP, finally try to flash update.zip, but I get the error below. Does anyone know why this would be the case?
Additionally, since receiving the error, I have installed busybox and tried fixing my SD card permissions in case they were the problem, no dice.
I do have all of the individual app backups on my computer if update.zip isn't going to work for some reason, and I took a full TWRP backup before upgrading as well (transferred all to my computer since the instructions clear personal data).
Error message:
UPDATE: Just discovered that Android is doing the "Optimizing apps" process at every single normal boot, whether I flash something or not.
Click to expand...
Click to collapse
You have TWRP and you flash successfully supersu2.46. Why you need update.zip? what is this?
just in case run in terminal:
Code:
su
restorecon -FR /data/media/0
maybe it help.
I installed TWRP 2.8.6.2 from the link in the first post of the Lollipop thread (http://forum.xda-developers.com/photon-q-4g-lte/development/cyanogenmod-12-1-photon-q-t3073781 ). I assume this is the latest/correct version for PQ?
I want to backup data so I can reformat data as f2fs and be able to use latest kernel.
I've tried backing up just data, or all four selections, with and without compression. Everything I've tried fails with error 255.
The log shows /data/data/com.skype.radier failed. So I deleted skype cache, data, then uninstalled. Retried backup again and still fail. Tried to manually delete folder, it won't delete nor will any of the subfolders (error 39 from es explorer). Tried to delete using TWRP's file manager, still won't delete (ERROR=1)/
a piece of TWRP log where it shows the errors.
I:addFile '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' including root: 1
E:Error adding file '/data/data/com.skype.raider/files/myskype.name/media_messaging/emo_cache/^80485FFBB32073DC42B65F944722AD423320F0EA974A6BF94F^pthumbnail_5b11e5f1-d716-4f57-842d-6ffdb8b257f3_distr' to '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q//data.f2fs.win000'
I:ERROR tarList for thread ID 0
E:Error creating backup.
I:InfoManager saving '/external_sd/TWRP/BACKUPS/T0695028XX/2015-12-15--15-40-38_cm_moto_msm8960_jbbl-userdebug_4.4.4_KTU84Q/data.info'
E:createTarFork() process ended with ERROR=255
Backup Failed.
Well just great. I wanted to backup but instead deleted everything. After posting I kept searching and trying ways to be able to delete that. Finally came to something that suggested using fcsk to check/repair the filesystem. Said to boot to recovery, adb shell, unmount and then run it. That didnt work cuz there was no unmount command in adb shell that I could find. Then I found in the TWRP menu there was a repair filesystem command, thought that was great! Ran it. And it wiped my data folder completely.
Not very happy right now.
I had the same problem as you when trying to convert to F2FS, and lost many hours of work as well! In my case the backup actually worked when using compression, so I thought all was good even though I never could get it to restore. I was able to get some of the data back by untarring the backup files themselves though, so you could maybe even look at the unsuccessful backup files if you had something important to recover.
In post 161 of this thread http://forum.xda-developers.com/pho...anogenmod-12-1-photon-q-t3073781/post64064173 a developer has compiled TWRP 2.8.7.0 for the Photon Q and it appears backup works. I never have tried it myself though as I hadn't seen the post in time. I just ended up using titanium backup.
Well I'm in an even worse situation now. I tried restoring from the failed backup and now my phone crashes and reboots a minute or two after booting. So I figured I better reinstall gapps. However, I can't get into recovery anymore. Just sits forever of the TeamWin screen. Reloaded recovery thru adb fastboot and it still does the same thing. So I can't even get into recovery to try flashing gapps again or if it came to it wipe data and start clean. I'm phoneless.
RSD Lite back to stock...
Hi, I'm restoring from a nandroid backup but once it starts restoring data it fails with error 255. I have no 999 files, and ran the steps here: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632 to remove 999 folders (it didn't work but I looked in those folders and saw no 999 folders) and have NEVER used Paralell Apps.
Is the backup salvageable?
NateDev said:
Hi, I'm restoring from a nandroid backup but once it starts restoring data it fails with error 255. I have no 999 files, and ran the steps here: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632 to remove 999 folders (it didn't work but I looked in those folders and saw no 999 folders) and have NEVER used Paralell Apps.
Is the backup salvageable?
Click to expand...
Click to collapse
Can you still boot into your OS?
mikex8593 said:
Can you still boot into your OS?
Click to expand...
Click to collapse
No, because I was on the P beta, but wiped everything including system. I tested a restore with everything else except data and it worked, just data failes, and recovery.log says "==> extracting: //data/reserve-lib/com.oneplus.soundrecorder/ (mode 40755, directory)
tar_extract_file(): failed to extract //data/reserve-lib/com.oneplus.soundrecorder/ !!!" so I'm assuming that's the issue, but I don't think there's any way to edit nandroid backup files like a filesystem, is there?
Edit: So I made the data backup into a .tar file and I can see the offending folder, but can't delete it from within WinRar, but I can make it a folder and delete it. Once I have that, how do I make it back into a .win000 file?
NateDev said:
No, because I was on the P beta, but wiped everything including system. I tested a restore with everything else except data and it worked, just data failes, and recovery.log says "==> extracting: //data/reserve-lib/com.oneplus.soundrecorder/ (mode 40755, directory)
tar_extract_file(): failed to extract //data/reserve-lib/com.oneplus.soundrecorder/ !!!" so I'm assuming that's the issue, but I don't think there's any way to edit nandroid backup files like a filesystem, is there?
Edit: So I made the data backup into a .tar file and I can see the offending folder, but can't delete it from within WinRar, but I can make it a folder and delete it. Once I have that, how do I make it back into a .win000 file?
Click to expand...
Click to collapse
I think you may be able to just rename .tar to .win000, try it and see.
JazzieBoi said:
I think you may be able to just rename .tar to .win000, try it and see.
Click to expand...
Click to collapse
Yea I editited it saying I did that, but can't figure out how to make it back into .win000. I guess I will just transfer it onto the phone, backup that and then restore (as just transfering will probably mess something up)
i'm having hte same problem , i never used parallel apps and i'm getting the same error on a restore for no freaking reason!
I need to restore so badly, i can get into OS just fine now but i didn't backup my apps prior to doing the wipe after the backup.. any ideas please?
NateDev said:
Yea I editited it saying I did that, but can't figure out how to make it back into .win000. I guess I will just transfer it onto the phone, backup that and then restore (as just transfering will probably mess something up)
Click to expand...
Click to collapse
Did you get this working? I'm not very good with TWRP yet so I don't know all the lingo, but I too made a backup and receive the error 255 when trying to restore using TWRP. When I restored the backup and unchecked data like you mentioned, it finishes without error but get this error "Your device is corrupt. It can’t be trusted and may not work properly" when I try to boot it. Restoring the backup without the data box checked still doesn't restore everything obviously. I'd like to restore the data too. Did you get it all working to where you can restore all?
R0ttenB4ndit said:
Did you get this working? I'm not very good with TWRP yet so I don't know all the lingo, but I too made a backup and receive the error 255 when trying to restore using TWRP. When I restored the backup and unchecked data like you mentioned, it finishes without error but get this error "Your device is corrupt. It can’t be trusted and may not work properly" when I try to boot it. Restoring the backup without the data box checked still doesn't restore everything obviously. I'd like to restore the data too. Did you get it all working to where you can restore all?
Click to expand...
Click to collapse
So I edited the backup and removed the offending files and then put the file back into the backup but that didn't work because I guess it broke the signature or something but it wouldn't restore data at all once I edited it. Idk.
I just don't bother with backups anymore, too much of a hassle haha, and it makes no sense why it fails, since I have no parallel apps or anything
Thanks very much for the response and info! No backup at all? Bummer. I've tried to backup several times using twrp and keep asking around. In the root directions it's said how to backup and restore. Surely it's been done in this os since instructions are there.
The second time I tried, I was able to backup and restore all partitions "successfully" using the newest bluespark twrp version from a couple days ago... But I get this boot issue saying the device can't be trusted and doesn't boot.