Related
I saw Online Nandroid Backup / Nandroid Backup without re-booting in the featured page. Would it work fot our g3?? Well i did try it and made a backup but a few steps failed but it did make a successful backup. But didn't yet try a restore. Has anybody tried it ??? BTW i am on ICS. Also the backup files contain the following -->
android_secure.vfat.tar
cache.rfs.tar
data.ext3.tar
efs.rfs.tar
nandroid.md5
sd-ext.ext4
system.ext2.tar
nishant_713 said:
I saw Online Nandroid Backup / Nandroid Backup without re-booting in the featured page. Would it work fot our g3?? Well i did try it and made a backup but a few steps failed but it did make a successful backup. But didn't yet try a restore. Has anybody tried it ??? BTW i am on ICS. Also the backup files contain the following -->
android_secure.vfat.tar
cache.rfs.tar
data.ext3.tar
efs.rfs.tar
nandroid.md5
sd-ext.ext4
system.ext2.tar
Click to expand...
Click to collapse
Install device specific patch from here for backing up boot partition. http://bit.ly/OnlineNandroid-partitionbug
I saw many people getting md5 mismatch while doing backup. So, I wrote this thread to help them.
Today I am going to share with you a method of restoring backups easily without an md5 error.
1ST METHOD:
Here are the steps:
1)Go to the folder where you saved your backup.
2)Open nandroid.md5 file with any text editor on your phone.
3)Delete all the lines from starting to end.
4)Save the file and close it.
5)Now restore your backup through CWM or Philz Touch or TWRP.
2ND METHOD:
If you changed the name of the backup folder, then, that is causing the problem. Try to change the name without adding spaces and/or special characters.
3RD METHOD:
Also you can use nandroid manager to recreate md5 sums.
Link in the next post by akiratoriyama
Thanks to @akiratoriyama
Or if you don't want to use nandroid manager, then you can use terminal emulator to recreate those sums:
Open terminal emulator then,
Use the following commands. (DON'T FORGET TO REPLACE "2012-04-17.10.09.36" WITH YOUR OWN BACKUP FOLDER NAME)
su
# mount -o remount rw /sdcard
#cd /sdcard/clockworkmod/backup/2012-04-17.10.09.36
#rm nandroid.md5
#md5sum *img > nandroid.md5
Don't forget to put the spaces!!
Voila, now your backup will restore properly without any md5 error:beer:
Sent from my GT-I9082 using Tapatalk Pro
Ateekujjawal said:
I saw many people getting md5 mismatch while doing backup. So, I wrote this thread to help them.
Today I am going to share with you a method of restoring backups easily without an md5 error.
1ST METHOD:
Here are the steps:
1)Go to the folder where you saved your backup.
2)Open nandroid.md5 file with any text editor on your phone.
3)Delete all the lines from starting to end.
4)Save the file and close it.
5)Now restore your backup through CWM or Philz Touch or TWRP.
2ND METHOD:
If you changed the name of the backup folder, then, that is causing the problem. Try to change the name without adding spaces and/or special characters.
Voila, now your backup will restore properly without any md5 error:beer:
Sent from my GT-I9082 using Tapatalk Pro
Click to expand...
Click to collapse
Alternate method
Use Nandroid Manager to recreate md5 sums
Sent from my GT-I9082 using Tapatalk
i tried the first method and it works for me
i cant backup my rom
i tried flashing the zip version of the s4 launcher and widget on my sgg-gt i-9082,,as instructed i backed up my stock rom but it didnt complete the backup..when i tried restoring the rom i get the error "md5 mismatch"..i wanted to try the methods youve posted but i cannot locate the nandroid.md5 file...i tried to install the touchwiz.apk (both in the system and user option) but the app just closes"unfortunately touchwiz has stopped working"..
so i have these questions:
1.is there a way i can still resore my stock rom?
2.i was running on jb 4.1.2..if i download the 4.2.2 update from the samsung website and flash my phone..wil i hav my touchwiz back?coz i dont like the holo launcher thaaaat much..
i'd be grateful for your help..
g_javella said:
i tried flashing the zip version of the s4 launcher and widget on my sgg-gt i-9082,,as instructed i backed up my stock rom but it didnt complete the backup..when i tried restoring the rom i get the error "md5 mismatch"..i wanted to try the methods youve posted but i cannot locate the nandroid.md5 file...i tried to install the touchwiz.apk (both in the system and user option) but the app just closes"unfortunately touchwiz has stopped working"..
so i have these questions:
1.is there a way i can still resore my stock rom?
2.i was running on jb 4.1.2..if i download the 4.2.2 update from the samsung website and flash my phone..wil i hav my touchwiz back?coz i dont like the holo launcher thaaaat much..
i'd be grateful for your help..
Click to expand...
Click to collapse
No way to restore stock rom. You didn't complete the backup.
Yes you can flash 4.2 to get TouchWiz back.
Sent from my GT-I9082 using Tapatalk Pro.
Ateekujjawal said:
No way to restore stock rom. You didn't complete the backup.
Yes you can flash 4.2 to get TouchWiz back.
Sent from my GT-I9082 using Tapatalk Pro.
Click to expand...
Click to collapse
thank you so much....
i tried the nandroid manager method and it worked..turns out my data was the one that didnt fully backup...i lost some-most-of my data but its better than losing my rom--...
thanks again..you are a life saver..
This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
my roms use stock kernel, comes from Open_C_upgrade_Tool: http://alturl.com/2bpns
vampirefo said:
This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
Click to expand...
Click to collapse
Thank you so much vampirefo, I am loving this build so far!
KUPOinyourWINDOW said:
Thank you so much vampirefo, I am loving this build so far!
Click to expand...
Click to collapse
This is the best build of Firefox OS I have ever used, omg. I don't know what it's like for you, but I can't find many bugs.
thanks man
overall i like it
the only negative is when unstick App Transition, opening/closing app/setting becomes very slow (in 1.4 i did unstick to make it faster/smooth)
2.1 works well, however 1.4 is more refined, closer to being released, Once 2.1 gets closer to being released it will be the preferred firefox version.
vampirefo said:
..in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
Click to expand...
Click to collapse
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
YemSalat said:
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
Click to expand...
Click to collapse
You don't have to adb push the recovery to sdcard, use fastboot to boot recovery.
fastboot boot cw_recovery_50.img
or to install recovery
fastboot flash recovery cw_recovery_50.img
happyass**** said:
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Click to expand...
Click to collapse
do you have a micro sdcard installed? did you extract the backup in correct place?
vampirefo said:
do you have a micro sdcard installed? did you extract the backup in correct place?
Click to expand...
Click to collapse
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
happyass**** said:
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
Click to expand...
Click to collapse
Unless you have used recovery to make a backup, then you need to create all the folders, if you have used recovery to make a backup, folders would have been created except for new_2.1, which is made when you extract 2.1.
if you don't have /clockworkmod/backup folders on your sdcard you need to make them, then in /clockworkmod/backup extract 2.1
in recovery mount external_sd
then post output of
adb shell ls /external_sd/
adb shell ls /external_sd/clockworkmod/backup/
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
YemSalat said:
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
Click to expand...
Click to collapse
That usually means bad download, you may need to redownload 2.1.
vampirefo said:
That usually means bad download, you may need to redownload 2.1.
Click to expand...
Click to collapse
I re-downloaded it and it now falls with hash mismatch for system.ext4.tar.a
I tried formatting the sd card with .50 recovery but it still gives that error.
Is there any way to do the update via fastboot by any chance?
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
vampirefo said:
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
I just did an adb push to the card:
adb push new_2.1 /sdcard/clockworkmod/backup/new_2.1/
But when I'm in .50 recovery - it does not see the new_2.1 folder. It only sees the one it created earlier when I did a backup.
Any idea what the heck could be wrong? xP
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
vampirefo said:
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Sorry about all the stupid questions, just the last one - can it be done via 'zip install' in recovery by any chance? Or does it have to be through restore?
The version I uploaded is restore only, you could make a zip install if you want, use Google to find info how to build cwm installation zip.
sent from my kingSing T1 via taptalk
Ok, thanks for the help!
I'll post the zip here if I succeed in making one.
Usually i would make ROM backups using the dd command. i come into a problem when i try to dd the data partition since the sdcard is syslink to /data/media in this device. it wants to pull a 25GB file.
is there any way to omit /data/media from the dd command when backing up /data partition?
thanks.
I don't think so, dd acts independently of the file system and hence isn't able to deal with directories.
Why don't you use nandroid or TiBu?
luckyrumo said:
I don't think so, dd acts independently of the file system and hence isn't able to deal with directories.
Why don't you use nandroid or TiBu?
Click to expand...
Click to collapse
thanks for the reply.
i dont use nandroid or TiBu because that is a extra step, when loading multiple devices with a rom it can get really time consuming to flash a recovery then copy a backup then run the backup then reflash a stock recovery.
i reason i want to have a userdata.img is so i can unlock the bootloader and flash in fastboot. its by far the quickest solution.
there just has to be a way to unlink /data/media from the partition. then dd the rest.
tronoftroy said:
thanks for the reply.
i dont use nandroid or TiBu because that is a extra step, when loading multiple devices with a rom it can get really time consuming to flash a recovery then copy a backup then run the backup then reflash a stock recovery.
i reason i want to have a userdata.img is so i can unlock the bootloader and flash in fastboot. its by far the quickest solution.
Click to expand...
Click to collapse
That makes sense, thanks for the explanation.
tronoftroy said:
there just has to be a way to unlink /data/media from the partition. then dd the rest.
Click to expand...
Click to collapse
Just an idea: Maybe you can get a hint by finding out how TWRP manages to wipe /data without /data/media?
luckyrumo said:
That makes sense, thanks for the explanation.
Just an idea: Maybe you can get a hint by finding out how TWRP manages to wipe /data without /data/media?
Click to expand...
Click to collapse
i was actually just looking at the source code for CWM and it seem similar to TWRP. they use a archive like Tar. TWRP just calls it .win. and will work directly with the filesystem. but i will check for how they wipe. thanks!
Before I handing in my OnePlus 6T for repair, I want to create a full system backup and reset the phone to factory defaults. Afterwards, I want to restore the original state. My phone is rooted with Magisk.
How do I do a full system backup?
What I tried:
adb backup -apk -obb -shared -all -system: This finishes, but at 5.5GB, even if compressed, the backup file is suspiciously small. According to the settings app, my phone uses 55GB of storage, so ten times that!
OK, so I thought adb root needs to be run before. However, that doesn't work: adbd cannot run as root in production builds
So I installed the adb_root module. But now when I run the above backup command, then it simply quits. No backup is created.
feklee said:
Before I handing in my OnePlus 6T for repair, I want to create a full system backup and reset the phone to factory defaults. Afterwards, I want to restore the original state. My phone is rooted with Magisk.
How do I do a full system backup?
What I tried:
adb backup -apk -obb -shared -all -system: This finishes, but at 5.5GB, even if compressed, the backup file is suspiciously small. According to the settings app, my phone uses 55GB of storage, so ten times that!
OK, so I thought adb root needs to be run before. However, that doesn't work: adbd cannot run as root in production builds
So I installed the adb_root module. But now when I run the above backup command, then it simply quits. No backup is created.
Click to expand...
Click to collapse
Do you have TWRP on your device? If so, just backup everything with it and copy the TWRP backup folder elsewhere.
ALSO (with the help of PC) copy the /sdcard (emulated sdcard; media storage). TWRP itself does not do that.
Done.
The reinstall TWRP in your device and restore everything. And copy back /sdcard
By the way, this is not Magisk related. For more information, better ask in your device specific section.
wilsonhlacerda said:
Do you have TWRP on your device? If so, just backup everything with it and copy the TWRP backup folder elsewhere.
Click to expand...
Click to collapse
Thanks for pointing me in the right direction! Here's how I proceeded in the end:
Downloaded TWRP for my device.
Rebooted the phone into fastboot mode by pressing volume down plus the power button and following the menu displayed on the phone. Note the process of entering fastboot mode varies from phone to phone.
Connected the phone to the PC, then booted TWRP from the Windows command line (cmd.exe):
Code:
fastboot boot twrp-3.4.0-0-fajita.img
I installed fastboot as part of the Chocolatey package adb.
In TWRP, I entered my password, then selected Backup.
Backed up all partitions to internal storage. See also the TWRP FAQ: What should I back up in TWRP?
Note that not all partitions need to be backed up, and in fact, according to the TWRP FAQ, it may be a bad idea to restore certain partitions. Still, it doesn’t hurt to have the backup of all of them.
Not included is /data/media (internal storage). This needs to be backed up separately. See the TWRP FAQ: What is EXCLUDED from a TWRP backup?
With TWRP running, I connected the phone via USB to my PC. Then I moved the following folder to my PC, which contains the TWRP backup of the phone:
Code:
This PC\OnePlus A6013\Internal Storage\TWRP
This step is not strictly necessary as in the following step I did back up the entire internal storage. However, it makes the next step execute faster as less data needs to be copied. The next step does not give feedback about progress.
For backing up internal storage I decided on the method found in Tadej Janež’s article Backing up Android's /data/media (i.e. internal storage) using adb and TWRP. From the Windows command line I ran:
Code:
adb exec-out "tar --create data/media/0 2>/backup-errors.txt | gzip" >internal_storage.tar.gz
After completion, to check for errors, I ran (no errors):
Code:
adb shell cat /backup-errors.txt
To leave TWRP, I rebooted the phone. Note that it is not necessary to install TWRP.
Restoration still needs to be tested.
By the way, this is not Magisk related. For more information, better ask in your device specific section.
Click to expand...
Click to collapse
I thought there was a Magisk way of doing a full system backup, making use of root privileges. Now I know better.
you can also try Migrator of vr25.
{Mod Edit: TG link removed}
https://github.com/VR-25/migrator
Just use Migrate
End of story.....
datsoy said:
you can also try Migrator of vr25.
{Mod Edit: TG link removed}
https://github.com/VR-25/migrator
Click to expand...
Click to collapse
Thanks! This looks nice, but I already backed up with TWRP. The idea was to get a 1:1 binary backup, and the backup did work. However, I am running into issues during restore of the Data partition: Error 255 when trying to restore Data