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.
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.
I put the latest touch recovery from clockworkmod into a flashable zip.
It works with ICS. It is the same recovery as the one you would have to pay for to install with ROM manager.
TO INSTALL CWM TOUCH RECOVERY........
Flash this in recovery as you would any ROM or mod.
Here is the link:
http://db.tt/Ud9qVq7V
I found the recovery http://www.clockworkmod.com/rommanager
**** This is different than sk8tr's version btw. His has a custom ui and this is CWM official. ****
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
If anyone is wondering this doesn't look like its a disaster just as 5.8.4.3 was. I flashed miui and it booted up fine but if anyone has any issues please share.
Sent from my SGH-I727 using xda premium
Working good on my Hercules just flashed aokp jb and aint need any superwipe scripts either
thank you, works great!
Updated op to avoid confusion.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Thanks for the info!
sent from a device using an app
Okay, so I ran a backup and restore test on cm9 and cm10. I thought it was sk8t's version causing me problems restoring backups but the issue is similar on this build.
The backup file that gets created doesn't contain all the data for a full restore -- much of it gets stored in the "blobs" folder in cwm (someone more knowledgeable than me can probably explain better). Also, it takes a REALLY long time to create a backup.
Using the standard restore doesn't work on (on this or on sk8t's version). I keep getting "error restoring system" message and it won't restore. I tried to do an advanced restore doing each part individually but that didn't work either.
Restoring an old rom from before they changed the backup method works fine though. I haven't tried restoring using ROM Manager yet but I may try that next--I'm thinking that's what the new system is designed for...
EDIT: Rom manager fails too. Same error restoring system message.
Please post here if you can successfuly backup and restore cm9 or cm10 (or any other roms) so we can figure out if its just me
skrambled said:
Okay, so I ran a backup and restore test on cm9 and cm10. I thought it was sk8t's version causing me problems restoring backups but the issue is similar on this build.
The backup file that gets created doesn't contain all the data for a full restore -- much of it gets stored in the "blobs" folder in cwm (someone more knowledgeable than me can probably explain better). Also, it takes a REALLY long time to create a backup.
Using the standard restore doesn't work on (on this or on sk8t's version). I keep getting "error restoring system" message and it won't restore. I tried to do an advanced restore doing each part individually but that didn't work either.
Restoring an old rom from before they changed the backup method works fine though. I haven't tried restoring using ROM Manager yet but I may try that next--I'm thinking that's what the new system is designed for...
EDIT: Rom manager fails too. Same error restoring system message.
Please post here if you can successfuly backup and restore cm9 or cm10 (or any other roms) so we can figure out if its just me
Click to expand...
Click to collapse
Did a backup on CM10 Alpha 1. It took awhile but didn't seem to take any longer than a CM 5.x backup. Modified a few things, updated a couple apps, and then did another backup - went a bit quicker. Doing a restore now but it's past the restoring system portion so I'm assuming it'll all be good. I'll edit this if it craps out at some point.
As for the blobs, this is new to CM6.x and from what I understand is supposed to make backups a little quicker and use less space as it will only backup what's been changed since a previous backup instead of the entire thing like CM5.x. Not sure at all on all the technical details but I'd suspect the blobs contain what's been changed at the point of backup and each backup "container" file indicate which blobs to restore...
EDIT: Restore completed just fine.
so you're saying that if I have a backup stored and create a new back up it only backs up the changes since the last one? If so, that sucks. I always like to keep a solid backup and then after numerous changes back up again and delete the old one. Looks like it's back to old faithful 5.8.1.3 for me.
(UPDATE) confirmed. My new backup was 20MB.
Honestly i prefer twrp recovery.. just wanted to provide this for those that needed it.
But, since TWRP does an UNCOMPRESSED backup i can have a nandroid backup done in a little over 2 minutes. Same for restore.. very fast.
TWRP can be set to compress the backup.. but i prefer speed over less space.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
copene said:
so you're saying that if I have a backup stored and create a new back up it only backs up the changes since the last one? If so, that sucks. I always like to keep a solid backup and then after numerous changes back up again and delete the old one. Looks like it's back to old faithful 5.8.1.3 for me.
(UPDATE) confirmed. My new backup was 20MB.
Click to expand...
Click to collapse
Here's the explanation of how it works:
https://plus.google.com/u/0/103583939320326217147/posts/L5aVZe7C9vg
pixelens said:
Here's the explanation of how it works:
https://plus.google.com/u/0/103583939320326217147/posts/L5aVZe7C9vg
Click to expand...
Click to collapse
Thanks. There should be a "FULL backup" and "BLOB backup" option. I'm rolling with 5.8.1.3 cause it's never fu**ed me over (yet).
copene said:
Thanks. There should be a "FULL backup" and "BLOB backup" option. I'm rolling with 5.8.1.3 cause it's never fu**ed me over (yet).
Click to expand...
Click to collapse
I'm not sure if I follow what the point would be? I thought the same, but after reading that and doing a few tests, I'm confident this will do just as well - if not better.
Might be worth mentioning/requesting from Koushik Dutta depending on your reasoning or need.
I think I figured out what the problem was for me in not getting backups to restore (but someone please post if you disagree). I was getting an "Error while restoring /system!" message every time.
Every time I make a backup I go into Root Explorer and change the backup name so that I know which rom it is. Today I did a backup and didn't change the backup name and I was able to restore it successfully.
Changing the name of yesterday's backup to it's original name, however, did not fix the problem. Those backups still won't restore.
skrambled said:
I think I figured out what the problem was for me in not getting backups to restore (but someone please post if you disagree). I was getting an "Error while restoring /system!" message every time.
Every time I make a backup I go into Root Explorer and change the backup name so that I know which rom it is. Today I did a backup and didn't change the backup name and I was able to restore it successfully.
Changing the name of yesterday's backup to it's original name, however, did not fix the problem. Those backups still won't restore.
Click to expand...
Click to collapse
I've always changed the name of my backup folder to make it more descriptive. One thing I read along time ago was that it only works if you don't include any spaces in the changed folder name. And I've never had any problems with restoring any of them. However, if you indeed did not include any spaces, then maybe it's been changed in CWM 6.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
plwalsh88 said:
I've always changed the name of my backup folder to make it more descriptive. One thing I read along time ago was that it only works if you don't include any spaces in the changed folder name. And I've never had any problems with restoring any of them. However, if you indeed did not include any spaces, then maybe it's been changed in CWM 6.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
skrambled said:
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
Click to expand...
Click to collapse
Gotcha. That's interesting then; don't know what it could be.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hey majic I got a suggestion to cut down on confusion. Put official in the title. At first I thought sk8 had to threads. I thank you kind sir for zipping and uploading this official version. You da man....
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
skrambled said:
Didn't add any spaces. I only added cm9 or cm10 to the end of the file name (that's how I know I changed it back to the original names when I tried to restore yesterday's backups).
Click to expand...
Click to collapse
never had issues changing names of back up folders, what did you use to change the folder name , you could have a space at the end of the file name and dont even know it, use backspace to delete it, if u know dos try its naming conventions
sorry but how is this recovery different from sk8's recovery? That one's also CWM Touch 6.0.1.0 and also flashable zip ... ?
Thanks!
So I just bought this phone, came in Monday, got it activated the same day, was excited! I had many Android phones and rooted without any problems. This one was far easiest the root. I had the stock ROM of course, followed the easy bootloader unlock method, bam! Phone fully unlocked! Fast boot and ADB were openly available, used ADB to reboot into bootloader again to flash CMW with fast-boot. Sweet, now I have recovery! That was a lot less painful process then I had with any phone. After reaching the recovery menu via ADB reboot recovery, I flashed SuperUser for root, and was cheering in victory, then did a clean factory reset to start using my phone as if new (with SU and CMW). At this point I had no idea I could access CMW without a computer (which I should I knew I could after so many roots and unlocks), and this option for a extended reboot to recovery menu was infront of me, waiting to be flashed. http://forum.xda-developers.com/showthread.php?t=1884282 .
Now, I went ahead and try to flash this zip for those extended options, and that is where I went wrong. The zip file screwed my phone so that it would get stuck on the Sprint Logo, and then I realized I forgot to make a nandroid backup. I went ahead and try to fix it, I didn't want to deoxed my phone, wanted to keep it as Factory OEM as possible. Look a glance at the guy's update script, and realized he removed a necessary .odex file and did not include it in the stock power menu to flash back to normal, so now I was stuck w/o that necessary .odex file and a phone that gets stuck at the sprint loading screen. At this point I was still okay, but was questioning this uploader's work, he never mentioned that a deoxded was needed, and his "stock" wasn't stock, it was deoxded without the .odex.
I wanted to clean the "contamination" and start over without a clean untouched ROM, which was a terrible idea. Still forgetting to make a nandroid backup though, and went ahead and found a system dump and system images (system.img.ext4, etc), did a FULL Wipe with (no nandroid backup!) And now my system partition and user data partition in wiped clean. Of course I tried flashing the system.img.ext4 and userdata.img.ext4 and what not with fastboot to get back to clean slate but that wasn't the case. Now I got stuck on WARNING BOOTLOADER UNLOCKED, and it will not even go to a sprint logo boot.
Now I realize I never made a nandroid backup, and kept putting myself in a bigger hole without making one from the start. I tried everything, fastboot flashing, I even make a system.zip update file for CMW to copy a system dump directly to the system partition, phone boots up, flickers, goes to CMW (thought that was going to work for a second). Now I'm stuck with a semi-bricked phone not-so-brand-new-anymore Motorola Photon Q, desperately searching for a way to flash it back in working order.
I have tried and flash various system dumps from users to no avail, and there not any full roms available that can get me out of this mess. Is it anyway method I'm missing to flashing these system dumps to get my phone back online, or will I be stuck without a phone until a rom comes out? I have been using these provided dumps
http://forum.xda-developers.com/showthread.php?t=1856456
http://forum.xda-developers.com/showthread.php?t=1874359 (Bought a Hotfile prem to download this, regular was taking forever, I could reup on my faster FTP if someone wants to give it a shot).
Please help if you know a way to get my beloved phone online! I only had it for a day and I'm in love with it, have no idea where I don't hear more about this awesome phone, I was sold when I saw it in the sprint store. (Reminds me of my old galaxy s1, it was a champ!)
*EDIT*
Problem solved! Thanks arrghhh for his backup files!
1. Use fastboot to flash TWRP to recovery.
2. Make a folder and put these files in that folder!
https://dl.dropbox.com/u/12691845/system.ext4.win
https://dl.dropbox.com/u/12691845/system.ext4.win.md5
https://dl.dropbox.com/u/12691845/boot.emmc.win
https://dl.dropbox.com/u/12691845/boot.emmc.win.md5
3. Place this folder in the following directory.
[Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / [your folder] ( so if your folder is called "argh_restore", it should be found in [Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / argh_restore ) , and inside that folder, the files you downloaded.
4. Boot into recovery, I assume you know how to do this since you unlocked your bootloader to mess up your phone in the first place .
5. TWRP should load, press restore, your folder should show up, select it, select system and boot, enable MD5 checking, and restore your phone.
**IF YOUR FOLDER DOES NOT SHOW UP, directory may be incorrect. You can make a backup and see where it goes to figure out where to place your backup folder!
6. Reboot your phone, your good to go!!
PS. This backup is NOT CLEAN stock! It is stock with deoxed, battery & toggle mod, and extended menu mod, I BELIEVE. Those are the only mods really available so that's my assumption, but arrghhh may know since it is HIS backup that he provided. So far, I've been using phone all day, seems to be running well. Just like stock! Also, I can't forget, shabby's awesome SuperUser mod for root! (You won't need CMW since you have TWRP, but if you want to swtich recovery, thats up to you. CMW is most popular recovery but TWRP is really great as well)!
I'd say you're going to NEED a nandroid backup to restore...
I was hoping flashing the de-odexed would work for ya. Would a nandroid backup of the system partition work? Hopefully it does, because that's about all I can think of to provide for you...
And lesson learned, I hope. Anytime, you do ANYTHING in recovery - MAKE A BACKUP!!
Edit - I re-read your post, did you try flashing the full de-odexed version? Seems like you have some hatred of it, lol... but if it saves your butt who cares.
I did flash a odex system dump, a deoxed system dump, and a system.img.ext4 dump to no avail.
But when the issue first occurred after I flashed the new power menu, I never flash the deoxed version to get the new menu to work. I know it was needed the issue but wanted to restore the original odex. I wanted to keep the phone system as OEM as possible (had some bad experience with modding to much, things don't work they way they use too). I could have done that to fix the issue before, but since I wiped it won't make a difference now (formatted /system /data /cache in CMW).
A Nandroid backup should definitely work I can though!!!!
If I can use someone working Motorola photon Q Nandroid backup I should be able to do a restore all of the system files I wiped (I'm not sure if any other partition other then the /system in the Nandroid backup would have to be restored to get the phone working, I know there /data but I think /system adds the files on first boot to /data?). I can still fully boot into recovery/fastboot but just need recover the system files back.
Sorry to hear you had problems i have supplied links in previous posts to all files Deodexd and back to original odex
PhotonQ stock Deodexd
PhotonQ stock Odexd
hope one of these help you get going
Yea, I meant try flashing the de-odexed version... even now after you're busted. Rangerbry kindly posted both tho. Hopefully that gets you back in business.
Just read he formated /system tho i can upload all that unless someone beats me to it
Sent from my XT897 using Tapatalk 2
Rangerbry said:
Just read he formated /system tho i can upload all that unless someone beats me to it
Click to expand...
Click to collapse
I get that he wiped /system. I thought what you posted would restore that? I guess not "all" of it eh?
I can take a nandroid backup of /system, but at this point it's been modified - it's far from OEM...
I have a few old nandroid backups, but I don't know if I kept the completely stock one. I should have in retrospect, so I'm going to hope I can find it...
Edit - the only backup of /system I have is a .win file for TWRP... sorry.
If it works I'll take it! lol. Stock would be nice but I have no choice at the moment. I could use a modded rom until a stock rom comes out, just don't want to be with a paper weight lol. I'm trying the Photon Q stock Odexed.zip right now though.
I have a full stock pull i keep on hard drive but cant get it till after work
Sent from my XT897 using Tapatalk 2
Ya may need full stock pull, flashed odex with no avail .
SleepyPanchoo said:
Ya may need full stock pull, flashed odex with no avail .
Click to expand...
Click to collapse
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
I know shabby has stock images pulled from the Motorola Photon Q here : http://forum.xda-developers.com/showthread.php?t=1856456
I did fastboot flash the system.img.ext4 (523 mb - seems like a full system image!) he has provided to no avail. But I'm thinking it should have worked? Its looks like a full system.img that should write all the necessary data to the /system partition to get me going, unless I have to rename system.img.ext4 to system.img before flashing, I'd have to get that a try and see if that makes a difference.
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
SleepyPanchoo said:
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
Click to expand...
Click to collapse
No prob and last i checked this is XDA no ones ever alone in getting problems fixed here. Still going to be several hrs until i get home tho
Sent from my XT897 using Tapatalk 2
arrrghhh said:
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
Click to expand...
Click to collapse
Just flashed TWRP 2.2.2.2 gonna give your system.img a shot!
Looks like it help me resotre your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
*EDIT*
I'm using shabby's stock images to fastboot flash userdata.img.ext4 but does not seem to have any effect. Data is still the same size. I may need a full nandroid backup to get this phone recovered, guess I will have to wait Rangerbry to upload that backup. hopefully that will work.
SleepyPanchoo said:
Looks like it restored your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
Click to expand...
Click to collapse
Did you restore "everything" or what was checked on restore?
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
SleepyPanchoo said:
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
Click to expand...
Click to collapse
Why would you need my /data? Or /cache!?! That doesn't make any sense.
I can provide a backup of /boot and /recovery.
Edit - Hrm... Well, /recovery shouldn't be needed. boot.emmc.win / md5
Wouldn't data have some required files for android to work? I know it contains user data as well (such as apps) but a nandroid backup, factory reset, then 2nd android backup that is given out can be made. Im sure cache is not necessary, but I'm trying everything at the moment, nothing seems to work when it feels like it should...!! I guess I can give your /boot a try. Don't think its /recovery since Im using your recovery now lol.
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta
Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.
Hi, I have my phone rooted, magisk'd, xposed etc etc and with a lot of apps and tweaks done to it.
Is there any way at all I could make a flashable image of it instead of having to make a backup of it in TWRP and then restoring it from there? (The TWRP method has never failed me but I was just curious about whether the question below could be done)
I'd like to be able to have a copy of the entire phone as a backup on the PC so I could then flash the phone back to its current state (if I mess anything up) using SP Flash Tool?
Forgive me if this is a stupid question or a task so complicated that it would just be easier to continue using TWRP.
The reason I ask is if the TWRP backup on the phone gets corrupted somehow then I'd like a copy of the phone so I could restore using that.
MrGRiMv2 said:
Hi, I have my phone rooted, magisk'd, xposed etc etc and with a lot of apps and tweaks done to it.
Is there any way at all I could make a flashable image of it instead of having to make a backup of it in TWRP and then restoring it from there? (The TWRP method has never failed me but I was just curious about whether the question below could be done)
I'd like to be able to have a copy of the entire phone as a backup on the PC so I could then flash the phone back to its current state (if I mess anything up) using SP Flash Tool?
Forgive me if this is a stupid question or a task so complicated that it would just be easier to continue using TWRP.
The reason I ask is if the TWRP backup on the phone gets corrupted somehow then I'd like a copy of the phone so I could restore using that.
Click to expand...
Click to collapse
You can store a copy of your TWRP backup on PC, then, if the backup that is stored on the device gets corrupted, you can use the copy that is stored on PC.
Sent from my SM-S767VL using Tapatalk
I have a copy of it on PC just in case, I thought I remembered reading a thread on here quite a few years back about creating a custom ROM from your existing installation with SPFlashtool or a similar program but it was so long ago that I might have mistaken it for another backup method.
Either way the TWRP backup is still quick enough to recover from and was thinking about the SPFlashtool way as an experiment. Thanks for replying.
You should be able to make partition image backups in TWRP. System, data and boot. Then you can Fastboot flash those partitions back.
I am not familiar with the MTK devices but it must be similar.
You can also use SuperR's kitchen to easily build a ROM from the images.
MrGRiMv2 said:
Hi, I have my phone rooted, magisk'd, xposed etc etc and with a lot of apps and tweaks done to it.
Is there any way at all I could make a flashable image of it instead of having to make a backup of it in TWRP and then restoring it from there? (The TWRP method has never failed me but I was just curious about whether the question below could be done)
I'd like to be able to have a copy of the entire phone as a backup on the PC so I could then flash the phone back to its current state (if I mess anything up) using SP Flash Tool?
Forgive me if this is a stupid question or a task so complicated that it would just be easier to continue using TWRP.
The reason I ask is if the TWRP backup on the phone gets corrupted somehow then I'd like a copy of the phone so I could restore using that.
Click to expand...
Click to collapse
Please check if this will help you out, I know it can save app, app data and roms. I used it on my device. Though some apps have problem using the app data which was backed up, most apps worked
https://play.google.com/store/apps/details?id=balti.migrate&hl=en_US
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
gopikrishnanrmg said:
Please check if this will help you out, I know it can save app, app data and roms. I used it on my device. Though some apps have problem using the app data which was backed up, most apps worked
https://play.google.com/store/apps/details?id=balti.migrate&hl=en_US
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
Click to expand...
Click to collapse
That is useless for what they are trying to do. That only backs up and restores user apps and user data, it helps you keep your data when switching ROMs. That doesn't help restore the system if the device gets corrupted.
Sent from my SM-S767VL using Tapatalk
Can't believe nobody on XDA told you about dd in 361 days!
Abstract:
Twrp have constant problem with encrypted data. The goal to achieve is make full backup of encrypted phone, when is unlocked, and be able copy on another same model of phone, and again encrypt it.
Same question here.
Im currently working on this.
Will update soon...
-`chiron` -> lineage-18.1-20210722
1. First try:
Code:
a) adb shell
b) su
c) dd if=/dev/block/by-name/system of=/mnt/sdcard/system.img
d) copied /mnt/sdcard/system.img to windows file system
e) dd if=/dev/zero of=/dev/block/by-name/system (after that phone restarted and automaticly went into fastboot)
(adb exited)
f) fastboot flash system system.img
g) Flashed with success, system animation showing, but after longer time phone turning off.
Data looks to dumped correctly, but now question is how to restore it correctly? (i didnt check it well: todo)
Copy full disk image from Android to computer
I have a smartphone without the possibility to insert an SD-card. I would like to make a dump of the biggest partition (cause I lost files and I'd like to use a dump to recover them). The partition...
stackoverflow.com
How to stream an encrypted backup of the entire device to remote host?
I have an Android device that has no free space and no SD-card that I can replace (thanks to OnePlus policy). I also have no free space on PC to accommodate the backup so I wanted to upload it to the
android.stackexchange.com