Related
Hey all,
When I had my Windows mobile phone, I could use Sprite Backup to make a backup that basically acted as an image that I could store on the SD Card. I could then do anything possible to my phone, and then I could simply restore the image, and it went back to the EXACT state it was when i took the image - registry, ALL apps, messages, icons, etc..., just like a 100% hard drive image.
I have Sprite backup on my Samsung Epic now, and was wondering if it acted the same way?
That is, if I install a custom rom, I would like to be able to factory restore it, then apply the backup to take it back to the exact state it was.
Is this how it works?
Thanks,
Matt!
It's called a nand backup and one of the benefits of rooting
Sent from my SPH-D700 using XDA App
Great,
I'm rooted, so I'll. Check it out....
Thanks!
Get the one click root and recovery. Once you have clockwork mod you can do a full backup. Also you can do an "advanced restore" and just restore your /data.
I have found that sometimes a restore doesn't work correctly and I have to reflash the rom and just restore /data to put my apps and settings back.
A word of warning, sometimes when you flash an old /data to a new rom it causes issues with programs. Personally, I have had very few issues doing it, even when moving between 2.1 and 2.2.1, but ymmv.
So, I just rooted my Mytouch 4G a few days ago using the 'Ultimate' guide on this forum. I had root access and I disabled and deleted some stock apps from my phone. I was using LauncherPro instead of the HTC Sense launcher. I made a backup in Clockworkmod recovery immediately after installing Clockworkmod, before I'd made any major changes.
So, I spent the past few days removing and tweaking things. I had my phone working extremely well. But then I realized that I actually wanted an .apk file (the stock visual voicemail app) that I'd already deleted from the phone. It should be in my original backup file, right? So I figured that I'd make a new backup, restore my old backup containing the .apk file, copy the .apk file off of the phone, then restore my recent backup. Well...this didn't work.
When I restored either the original backup or the more recent backup, the phone would boot up and I'd get a message that the System UIDs are inconsistent. The phone would let me make phone calls, but 95% of my apps were missing from the loader. Most of the icons on my home screens were grayed out and would tell me the applications were missing when I tried to click on them.
I tried Fix Permissions in Clockworkmod recovery, but it didn't help. My Android Market app and all of my file manager apps didn't work, so I couldn't reinstall any apps. When I'd wipe all the data on my phone, but only restore the System backup, the Android Market would work and the phone basically returns to stock. But as soon as I restore my Data backup, everything breaks.
At this point, I've already wiped the phone and started over from scratch, but I'm afraid to rely on Clockworkmod/Rom Manager for backups again. Any ideas what went wrong?
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
this happens when your backups/card gets corrupted... it could of been a number of things... changing the name of something to how much you scan the card... hard to say exactly what caused it... If your really worried about it I would suggest making a backup of your backup on your computer just to be safe...
Hmm. Mine does.
mr.tenuki said:
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
Click to expand...
Click to collapse
Sent from my stickie key HTC Glacier using XDA App
I did make a backup of my backup, but it's not like these backups sat on the memory card for months before they got used. I ran the restore within minutes of when I made the last backup. Besides, aren't the backups hashed with md5 and then retested before restoring? So, if the files did get corrupted, I would think Clockworkmod would have notified me, no?
I just wish that after making a backup, there was some way to test it out without taking the chance of trashing my phone.
Regarding using a different kernel, I did not. I did not flash any experimental/downloaded images, these were simple backups and restores of my existing phone data.
mr.tenuki said:
did you flash a different kernel? this may be the issue, as I know that for other devices CWM does not restore the kernel.
Click to expand...
Click to collapse
This is for phones that dont support Nand like the vibrant. HTC phones is a full backup including kernel.
sundayhustler said:
I did make a backup of my backup, but it's not like these backups sat on the memory card for months before they got used. I ran the restore within minutes of when I made the last backup. Besides, aren't the backups hashed with md5 and then retested before restoring? So, if the files did get corrupted, I would think Clockworkmod would have notified me, no?
I just wish that after making a backup, there was some way to test it out without taking the chance of trashing my phone.
Regarding using a different kernel, I did not. I did not flash any experimental/downloaded images, these were simple backups and restores of my existing phone data.
Click to expand...
Click to collapse
Your right, CWM does do a md5 check when restoring. I'm sorry, I don't know what could be wrong. I currently have like 5 backups of 4 ROMS and have to restored to just to play around. Did you do apps2sd? This can cause major issues when switching ROM's.
I am also having a problem restoring to my stock rom. how big does my backup file have to be?
I have had this problem before. I think in my case my issue was caused by and incompatible version of CWM. I found that to be safe, I usually make two back ups, one with recovery in 2.5.12 and one with 3.0.0.6.
It was the file. It was only 60mb, apparently I ran out of memory thanks though my other backups work fine and I found the stock rom on a thread.
Sent from my HTC Glacier using XDA App
oh haha i was about to post.
I have a T-Mo G2 and want to keep my Froyo image to reinstall later if I cannot get theGingerbread to work right. I want to make an image file that will restore the phone to exactly how it is now. I have tried all kinds of stuff, but am not able to make the "img" file so that I ca do a restore when booting...
Can someone point me to what I need to install to do this, and if possible some directions on what/how to create the "img" or restore file ?
I would be most appreciative, as I had to reverse everything from the OTA of Gingerbread, since too many apps didn't work, ESPECIALLY the GPS!
My current Froyo is a temp-root system.
Thank you all!
Aloha. .
I would do full root via the wiki, and then install 4EXT (the full one that's like $2) - it will keep your old stuff straight
Ditto on previous reply
Root your G2
Backup all your apps with using Titanium backup
Get Clockwork mod ROM manger or 4ext ( I prefer 4ext) and backup your stock rom. You can download new ROM CM7 for first ROM.
If you don't like the ROM you can restore your stock ROM with CWM or 4ext at anytime.
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
WTF? said:
I have a theory that Ti Backup or any backing up of apps is a bad plan. I know you can do it no problem, and that it is a great time saver, but I have a strong feeling that this ultimately results in an unstable phone with mysterious force closes etc.
Even though it's a real pain, I think you are always better off reinstalling your apps from scratch after changing to a new ROM and wiping caches.
Click to expand...
Click to collapse
1. I have had zero problems with TB personally.
2. Without it your app data is gone.
3. Triple wipe, takes a few extra minutes and makes a world of a difference.
4. Do not restore system data!
5. Check md5 sums BEFORE doing anything!!!!
6. Make sure you have a recent nandroid backup and you'll be fine either way.
7. triple wipe before flashing anything including nandroids. Preferably with different wipes aka factory reset, superwipe+ ext4, then recovery wipe!
Just my 2 cents, it's saved my a$$ more then a few times...
Some apps not working after updated to 4.2, so I'm considering back to 4.1.2.
Though I never done this before since the day I get Nexus 7,
I think use Wug's Nexus Root Toolkit should get it done.
But just for sure:
1. Do I need to unlock/root to flash factory 4.1.2 image? (I think it is not but not so sure)
2. Directory structure seems different from 4.1.2, is it OK just using Toolkit to backup/restore settings?
(Sorry for my English if anything looks impolite)
1) unlock bootloader yes; root no, as you're going to overwrite the system anyways.
Also I'd suggest not using a toolkit, just download the factory image off google's page and run the "flash-all.bat"
2) Use Titanium Backup to backup all app data, wipe after flashing 4.1.2 and then restore apps + data with Titanium again
I just downgraded this morning. All your data will be wiped .. ALL YOUR DATA ... meaning, after I got back to 4.1.2 I was having 13GB of free space on the tablet (out of 13 possible) .
So, if you HAVE a nandroid from the 4.1.2 days, save it to your computer (along with all your files).
If you don't have a 4.1.2 nandroid, at least create now a backup repository with whatever tool you prefer and then save the respective files to PC.
Then, flash the factory image for 4.1.2.
Then copy all your files back to the internal memory, install the backup tool and restore your apps.
The reason behind this is that the update from 4.1.2 to 4.2 has some scripts that are porting the original /data and /sdcard mounts to the new structure used in 4.2
When downgrading, you no longer have scripts to do that for you so the newly installed 4.1.2 will not recognize anything so it will bootloop like crazy (I tried first to restore just the /system ... but all the other data was already affected by the update so was no longer usable).
My thoughts:
If you got the ota, and things messed up, try flashing the 4.2 factory image. That seemed to help me. If you're not rooted already, I would recommend becoming familiar with the adb backup command to backup apps before doing anything else. You have to unlock the boot loader to downgrade or flash the factory 4.2 image, and this will wipe the device.
Once you update either way, definitely take the time to root. You can then use adb restore or titanium backup to restore from the adb backup you made before unlocking.
Just be aware that adb backup doesn't seem to backup all apps, and that titanium backup isn't exactly fast parsing through a big adb backup file.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
step by step?
srry, very nooby questions:
how do i flash my nexus?
where do i find the factory image?
what is the backup tool?
ro_explorer said:
I just downgraded this morning. All your data will be wiped .. ALL YOUR DATA ... meaning, after I got back to 4.1.2 I was having 13GB of free space on the tablet (out of 13 possible) .
So, if you HAVE a nandroid from the 4.1.2 days, save it to your computer (along with all your files).
If you don't have a 4.1.2 nandroid, at least create now a backup repository with whatever tool you prefer and then save the respective files to PC.
Then, flash the factory image for 4.1.2.
Then copy all your files back to the internal memory, install the backup tool and restore your apps.
The reason behind this is that the update from 4.1.2 to 4.2 has some scripts that are porting the original /data and /sdcard mounts to the new structure used in 4.2
When downgrading, you no longer have scripts to do that for you so the newly installed 4.1.2 will not recognize anything so it will bootloop like crazy (I tried first to restore just the /system ... but all the other data was already affected by the update so was no longer usable).
Click to expand...
Click to collapse
HellcatDroid said:
1) unlock bootloader yes; root no, as you're going to overwrite the system anyways.
Also I'd suggest not using a toolkit, just download the factory image off google's page and run the "flash-all.bat"
2) Use Titanium Backup to backup all app data, wipe after flashing 4.1.2 and then restore apps + data with Titanium again
Click to expand...
Click to collapse
restoring my apps with Titanium Backup is unsuccessful , when i first tried a full app+data restore it freezes at 0 percent
and when i tried backuping app the missing apps , it worked but after i rebooted it . It went into a bootloop
Youssef Hossam said:
restoring my apps with Titanium Backup is unsuccessful , when i first tried a full app+data restore it freezes at 0 percent and when i tried backuping app the missing apps , it worked but after i rebooted it . It went into a bootloop
Click to expand...
Click to collapse
Assumed you are referring to downgrade from 4.2.1 to 4.1.2 and rooted to run TB, so the basic stock rom is up & running otherwise, correct?
Let's try Plan B instead - go into (Custom) Recovery and wipe dalvik cache first, then reboot. Give it a few minutes to settle and try to do your TB restore WITHOUT data, and see if it works. The /SD and/or /SD/0 directory structures are setup differently on the N7 and trying to retore with your custom settings will just make it more difficult & complicated. If this works, you can then try to selectively restore one or more with data and hopefully without going into endless bootloop again.
Plan C - go to Play Store, then Settings and "All" - you should see all of your Apps and what's installed, etc. - and install from there, it's semi-manual but it works for me 99.8% of the time when it would otherwise freeze within TB, especially true when switching custom Rom & kernels.
I usually manually copy & move back items such as documents, pictures & mp3's, etc. from standalone/usb backup drives or cloud storage back into the device once everything else are up & running properly.
Let us know if this helps & working for you or not.
Thankss !
Letitride said:
Assumed you are referring to downgrade from 4.2.1 to 4.1.2 and rooted to run TB, so the basic stock rom is up & running otherwise, correct?
Let's try Plan B instead - go into (Custom) Recovery and wipe dalvik cache first, then reboot. Give it a few minutes to settle and try to do your TB restore WITHOUT data, and see if it works. The /SD and/or /SD/0 directory structures are setup differently on the N7 and trying to retore with your custom settings will just make it more difficult & complicated. If this works, you can then try to selectively restore one or more with data and hopefully without going into endless bootloop again.
Plan C - go to Play Store, then Settings and "All" - you should see all of your Apps and what's installed, etc. - and install from there, it's semi-manual but it works for me 99.8% of the time when it would otherwise freeze within TB, especially true when switching custom Rom & kernels.
I usually manually copy & move back items such as documents, pictures & mp3's, etc. from standalone/usb backup drives or cloud storage back into the device once everything else are up & running properly.
Let us know if this helps & working for you or not.
Click to expand...
Click to collapse
Thanks for your help , but I think the problem was that there were apps in the backup only compatible with the custom ROM I had and android 4.2.1 xD
I restored the apps one by one , but I think if I deleted the extra custom rom apps , the process would have finished without any problems
Hi fellow people,
i'm a noob just made my xda account like 5 mins ago. I've been trying to search for my problem but I haven't really a found a direct answer. So yesterday I just got my Samsung Galaxy nexus update to 4.2.1. I was really excited until I started having the battery issues, screen lock issues, and overheating problem. I really don't like 4.2.1 and want to downgrade my version back 4.1.2. My carrier is the Mobicility (Canadian). I did not do anything previously with this phone such as rooting it, doing all the funky stuff that will void my warranty. I heard about flashing some google images to get back 4.1.2 but I'm not sure if I need to root or how to like do it through the gnex toolkit that mskip made. As well what if the difference between yakju and maguro? I heard if you flash the wrong image it will brick your phone or something like that. If there is a method without having to root it and lose all my contacts, then I would prefer that a lot.
Thanks,
mleung754
mleung754 said:
Hi fellow people,
i'm a noob just made my xda account like 5 mins ago. I've been trying to search for my problem but I haven't really a found a direct answer. So yesterday I just got my Samsung Galaxy nexus update to 4.2.1. I was really excited until I started having the battery issues, screen lock issues, and overheating problem. I really don't like 4.2.1 and want to downgrade my version back 4.1.2. My carrier is the Mobicility (Canadian). I did not do anything previously with this phone such as rooting it, doing all the funky stuff that will void my warranty. I heard about flashing some google images to get back 4.1.2 but I'm not sure if I need to root or how to like do it through the gnex toolkit that mskip made. As well what if the difference between yakju and maguro? I heard if you flash the wrong image it will brick your phone or something like that. If there is a method without having to root it and lose all my contacts, then I would prefer that a lot.
Thanks,
mleung754
Click to expand...
Click to collapse
You dont have to root but you need to UNLOCK the bootloader which will obviously erase all your data(and VOID your warranty). you can find the factory image here https://developers.google.com/android/nexus/images . just flash the appropriate image and you should be as good to go.
mleung754 said:
Hi fellow people,
i'm a noob just made my xda account like 5 mins ago. I've been trying to search for my problem but I haven't really a found a direct answer. So yesterday I just got my Samsung Galaxy nexus update to 4.2.1. I was really excited until I started having the battery issues, screen lock issues, and overheating problem. I really don't like 4.2.1 and want to downgrade my version back 4.1.2. My carrier is the Mobicility (Canadian). I did not do anything previously with this phone such as rooting it, doing all the funky stuff that will void my warranty. I heard about flashing some google images to get back 4.1.2 but I'm not sure if I need to root or how to like do it through the gnex toolkit that mskip made. As well what if the difference between yakju and maguro? I heard if you flash the wrong image it will brick your phone or something like that. If there is a method without having to root it and lose all my contacts, then I would prefer that a lot.
Thanks,
mleung754
Click to expand...
Click to collapse
mleung754,
You are posting in the wrong forum.
Asus Nexus 7 is not the same thing as a Samsung Galaxy Nexus.
Ignore mmystere68's remarks.
Ok so after rooting and using Flashify to install Loki'd TWRP 2.3.6.2, I backed up my stock rooted. Then, I wiped and flashed PA 3.99. Other than this phone taking forever to do anything in TWRP, everything seemed fine. I booted into PA, installed my normal software setup, rebooted to recovery, and made a backup.
Now, if I try to restore (either stock rooted or PA, it fails. It says something about unchecking the MD5 verification option, which I have done in the general TWRP settings, as well as making sure it stays unchecked in the restore preferences. Have tried restoring to both stock rooted and PA from both a PA install, and a fresh stock rooted install. Both fail with the same error.
I'm backing up/restoring to/from the internal SD, not an OTG cable. my cable that worked fine for my Note 2 and HTC One does not work with my G2. I have also tried re-flashing TWRP in case it was a bad install or something.
Does anybody have any thoughts/suggestions on what I can do to be able to restore roms? I've never had any issues like this with any other device.
I'm interested in this as well. But honestly I haven't been able to restore a damn backup in quite some time using my Galaxy Nexus using TWRP and CWM. It just seems like it tries to, but fails toward the end.
I did a backup of my stock/unrooted but haven't tried to restore it yet. Have you thought or tried to use one of the GUI Apps from the Play Store that does Restore/Backups? I would also pull those backups off of your phone and onto a PC. You can always copy them back later but I've erased everything using TWRP a few too many times.
I would also suggest trying to use CWM to restore the backups. I've never tried to restore a Nandoid from one recovery using another, but it may work.
Sadly with restore not working, it is kind of scary to even attempt it. I would make sure I have some stock images laying around with the ability to adb push if need be. Keep this updated please with either findings or solutions. If I knew 100% that my Nandroid backup was able to be restored, I would attempt to try some of the custom roms out there.
player911 said:
I'm interested in this as well. But honestly I haven't been able to restore a damn backup in quite some time using my Galaxy Nexus using TWRP and CWM. It just seems like it tries to, but fails toward the end.
I did a backup of my stock/unrooted but haven't tried to restore it yet. Have you thought or tried to use one of the GUI Apps from the Play Store that does Restore/Backups? I would also pull those backups off of your phone and onto a PC. You can always copy them back later but I've erased everything using TWRP a few too many times.
I would also suggest trying to use CWM to restore the backups. I've never tried to restore a Nandoid from one recovery using another, but it may work.
Sadly with restore not working, it is kind of scary to even attempt it. I would make sure I have some stock images laying around with the ability to adb push if need be. Keep this updated please with either findings or solutions. If I knew 100% that my Nandroid backup was able to be restored, I would attempt to try some of the custom roms out there.
Click to expand...
Click to collapse
Thanks for the reply.
I have only tried directly through TWRP. I've been flashing phones and tablets for years, but only using TWRP and CWM. I've been using TWRP lately because it's gui is nicer and until now, I've never run into any problems with it.
And yes, restore not working scares me. I know I can adb stock if I screw things up, but I hope it doesn't come to that. I guess for now I'll keep running stock rooted (despite it's horribly ugly unlock animations) and just wait for official AOKP with 4.4...