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...
Related
I haven't used adb cuz i havent been able to set it up. But i have flashed Damaged control succesfully by mounting the zip on the sd card. i flashed it a couple times since ive tried installing Nexus one launcher by flashing from sd card but nothing just messed up rosie. i couldnt restore my older Rom it kept telling me use adb. Fail lol but i flashed damage control 2.05 back and working fine maybe faster. What i want to know is how to get the nandroid restore fixed or working for emergencies.
alt f4 fixes it all
huh? Confused..
he was trying to be "smart" and gave you a bogus answer if you combo press alt + F4 it will exit your screen... Not really sure what your question is though if you are asking as to why your Nandroid won't restore properly it's because you have to "wipe" your cache before doing a nandroid if you are going back to a version that is different than the currently flashed rom. Hope this helps if not then ... perhaps you could re-phrase your question.
~Danny
Rsoehelk said:
I haven't used adb cuz i havent been able to set it up. But i have flashed Damaged control succesfully by mounting the zip on the sd card. i flashed it a couple times since ive tried installing Nexus one launcher by flashing from sd card but nothing just messed up rosie. i couldnt restore my older Rom it kept telling me use adb. Fail lol but i flashed damage control 2.05 back and working fine maybe faster. What i want to know is how to get the nandroid restore fixed or working for emergencies.
Click to expand...
Click to collapse
The only way I fixed that is by running the nandroid restore through adb like it says to do. I don't understand how you don't have adb installed but you have the phone rooted? I had to get all that working to root my phone and having adb is an invaluable tool anyway.
I did read that the nandroid error sometime comes up when the sdcard is too full so you could see if that is the case. Also, as someone suggested you could try a factory reset/wipe and then try again to nandroid through recovery.
richse said:
The only way I fixed that is by running the nandroid restore through adb like it says to do. I don't understand how you don't have adb installed but you have the phone rooted? I had to get all that working to root my phone and having adb is an invaluable tool anyway.
I did read that the nandroid error sometime comes up when the sdcard is too full so you could see if that is the case. Also, as someone suggested you could try a factory reset/wipe and then try again to nandroid through recovery.
Click to expand...
Click to collapse
theres different ways to root your phone lol
The only way I fixed that is by running the nandroid restore through adb like it says to do. I don't understand how you don't have adb installed but
Click to expand...
Click to collapse
theres different ways to root your phone lol
Click to expand...
Click to collapse
Yup,i don't even have a pc (seriously I don't)
I did run into this problem though, not sure exactly what I did but it worked itself out, maybe try flashing a different recovery image,Or try keeping phone plugged into charger(not sure what significance that has but it did seem to go for me after I was having those problems) which recovery image do you have?
Did you rename the Nandroid backup you were trying to restore to? If you did, and the file name has a space in it, it will tell you to restore via ADB. Just a thought from the limited info you provided.
I had this problem and it fixed itself out and all i did was wipe everything thats under the wipe option in recovery and it worked for me.
Yeah it was actually the cache you guys were right. i did it on my own and thought that might be it. and now i know that was it from checkin the thread. yeah i used pre kitchen to auto root my phone. im actually running damage control 2.05 now the newest sprint leak.damn i love it lol. but imma reflash it cuz i tried to flash a nexus theme/ no luck i want a nexus one interface!!!!!
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 was reading FadedLite's Guide to root the Nexus 7, and one of the commentors posted that you should create a nandroid backup and bootable image after installing CWM but before adding SU. I'm not entirely sure what the purposes of these backups would be, but anyone can download the factory image from google here. So is a nandroid backup really necessary?
This is my first post on xda (although I've been here since March and have rooted 2 devices already) so I'm really hoping I posted this correctly.
I would say, and a lot of XDA users will tell ALWAYS make a backup. Although there might be factory image at Google backing up your own system is a very good idea.
Well, it's not necessary but it's always that just in case notion. I mean what about that slim chance that your USB port was not working and it suddenly stopped working properly?
I make nandroid backups only when I'm testing new ROMs and PLAN to go back to my original. I made a nandroid backup of my Galaxy S III stock ROM and then tried out jelly bean, once I was sick of it I switched back to the stock ROM because it worked obviously
I was just thinking that a backup stored locally would take up a lot of the tablet's very limited space. As long as you can boot into recovery, couldn't I just store it on another device and move the file over while in recovery? While there is a chance of usb malfunction, it is a slim chance... then again I have already perma-bricked one of my devices already, but that was an issue trying to install cwm so I couldn't have made a backup anyways.
Well, if your USB port goes, wifi or Bluetooth transfer would allow you to transfer your backup over. Unless you also don't have a bootable rom at the same time.
Nandroids are huge but it might be a good idea to have a working flashable build on internal memory at all times so you can boot up and transfer stuff.
Koush is developing a new CWR that creates TINY backups, I have no clue how he does it but he does.
unless you are running pure stock from google or a full final rom like cyanogen final, you should always have a backup.
You can download the image, but you lose ALL of your data. A nandroid backup keeps your apps and data.
A nandroid backup of ICS/JB is around 1.5-2GB in size. and yes that is a huge file size. And yes you can remove it from the device and put it back on. i STRONGLY recommend copying the entire directory and then erasing the individual files from your device so you don't forget where they're suppose to go.
If you are planning on doing custom roms or any root activity a nandroid is basically required.
Going to update to a new release? nandroid.
going to install a new theme, boot animation, metamorph? nandroid.
Are the chances small that something will go wrong? yes. But if it does, do you really want to have to redo EVERYTHING on your device?
I do a backup once a week on my galaxy nexus through clockwork mod that way i don't ever have to worry about something going wrong. restore the backup and at the most i'm back to where i was 7 days before.
Also, with USB-OTG you can connect the nexus 7 to a portable hard drive and store your backups there.
Not all flashable zips wipe the device. I actually find it very annoying when devs add wiping to their zips. I flash without wiping a lot and rarely have problems.
I believe I've had this problem in the past with other android devices but I don't recall how I solved it.
Basically I unlocked, rooted, and flashed CWN using the nexus tool kit (I am very capable of using adb just felt like simplifying). I then made a nandroid backup using the CWM that the tool kit flashed. Later, i updated to CWM touch with Rom manager. I don't think the new CWM caused this but for some reason i am unable to delete that first nandroid i made. I've made other backups since and have had no problem deleting them, it's just this first one that i made that isn't deleting for some reason. Any ideas? It's pretty much just dead weight on my storage at this point.
randroid123 said:
I believe I've had this problem in the past with other android devices but I don't recall how I solved it.
Basically I unlocked, rooted, and flashed CWN using the nexus tool kit (I am very capable of using adb just felt like simplifying). I then made a nandroid backup using the CWM that the tool kit flashed. Later, i updated to CWM touch with Rom manager. I don't think the new CWM caused this but for some reason i am unable to delete that first nandroid i made. I've made other backups since and have had no problem deleting them, it's just this first one that i made that isn't deleting for some reason. Any ideas? It's pretty much just dead weight on my storage at this point.
Click to expand...
Click to collapse
im having the same issue and am working on it right now, will keep ya posted.
edit: i just flashed all the way back to stock and rerooted, started fresh basically. i wonder, can you just partition the "sdcard", effectively erasing the entire clockworkmod folder?
I had that problem and tried root explorer, astro, rom manager to delete the folders and nothing was working until I actually booted CWM and deleted the backup through CWM, it deleted just fine.
SoHaunted said:
I had that problem and tried root explorer, astro, rom manager to delete the folders and nothing was working until I actually booted CWM and deleted the backup through CWM, it deleted just fine.
Click to expand...
Click to collapse
that was my first thought but i wasnt able to locate the option to do so in the version of CWM i was using- honestly i dont recall which it was. now that im on a fresh system though, i think ill switch to TWRP. i use it on my one X and like it just fine.
Hey everyone, I'm new to android game, I've been cracking iPhones since 1st gen, decided to challenge myself. I have an S4, rooted, but no CWM installed. I want to save the recovery so if any issues ever occur, I can just flash it and have it covered under warranty, and also to be ble to return to stock wen I sell the phone.
Is there a tool i can use to make a nandroid backup? On my Nexus 7, There is an all-in-one tool and I can make a nandroid straight from my PC. Is there anything similar for the s4? If not, how to I make a nandroid backup? thank you everyone for your help, I appreciate it
Odin back to stock if you ever need to.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Dimon1990 said:
Hey everyone, I'm new to android game, I've been cracking iPhones since 1st gen, decided to challenge myself. I have an S4, rooted, but no CWM installed. I want to save the recovery so if any issues ever occur, I can just flash it and have it covered under warranty, and also to be ble to return to stock wen I sell the phone.
Is there a tool i can use to make a nandroid backup? On my Nexus 7, There is an all-in-one tool and I can make a nandroid straight from my PC. Is there anything similar for the s4? If not, how to I make a nandroid backup? thank you everyone for your help, I appreciate it
Click to expand...
Click to collapse
I'm not entirely sure it's possible to do a nandroid backup without first having a custom recovery. However, it is "always" possible to use the Odin method to return to stock (including stock recovery). Personally, I installed TWRP and immediately did a full nandroid (including system, boot, cache, etc...) and I've frequently found myself restoring pieces of it as I manage to screw up different things. I did return my recovery back to stock once by using the "dd" method to flash the stock recovery.img onto the correct emmc block. There's instructions how to do this exactly on the TWRP homepage (make sure you get the correct phone - block numbers are different for different devices) - but instead of re-flashing TWRP, I pulled the recovery.img from the giant Odin image available here on XDA.
It may also be possible to use "dd" to pull a copy of your existing recovery image as well, but I've never tried it.
Aou said:
I'm not entirely sure it's possible to do a nandroid backup without first having a custom recovery. However, it is "always" possible to use the Odin method to return to stock (including stock recovery). Personally, I installed TWRP and immediately did a full nandroid (including system, boot, cache, etc...) and I've frequently found myself restoring pieces of it as I manage to screw up different things. I did return my recovery back to stock once by using the "dd" method to flash the stock recovery.img onto the correct emmc block. There's instructions how to do this exactly on the TWRP homepage (make sure you get the correct phone - block numbers are different for different devices) - but instead of re-flashing TWRP, I pulled the recovery.img from the giant Odin image available here on XDA.
It may also be possible to use "dd" to pull a copy of your existing recovery image as well, but I've never tried it.
Click to expand...
Click to collapse
Thank you! I'll be installing TWRP today, what is Odin if I can ask? I've never heard of any of it from Nexus 7.
Also, If i do a titanium backup, can I easily restore apps with setting and save games while I'm running CM10.1?
Dimon1990 said:
Thank you! I'll be installing TWRP today, what is Odin if I can ask? I've never heard of any of it from Nexus 7.
Also, If i do a titanium backup, can I easily restore apps with setting and save games while I'm running CM10.1?
Click to expand...
Click to collapse
You better find out what odin is because it's the only way you'll be installing twrp. And don't count on tibu restoring all your apps seamlessly. Never reinstall system apps.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
You better find out what odin is because it's the only way you'll be installing twrp. And don't count on tibu restoring all your apps seamlessly. Never reinstall system apps.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I installed TWRP through GooManager. I looked up ODIN and got general info, hopefully I won't get stuck, but I'm sure I'll find my way around. Thank you so much for your help! I figured that sys apps will just be for stock, but i have a MC4 save that i don't want to lose ::cyclops: it looks like it's CM10.1 time for me!
Dimon1990 said:
Thank you! I'll be installing TWRP today, what is Odin if I can ask? I've never heard of any of it from Nexus 7.
Also, If i do a titanium backup, can I easily restore apps with setting and save games while I'm running CM10.1?
Click to expand...
Click to collapse
Here's the thread that explains how to return to stock using Odin. Be prepared for a large download.
http://forum.xda-developers.com/showthread.php?t=2261573
In short, "Odin Mode" is the download mode that's built-in to just about every modern Samsung device, beginning as far back as the Captivate, afaik. Each device has a button combination to enter "download mode" or "odin mode". This special mode sometimes requires specific drivers to connect to your PC. Flashing stock firmware using this method is common, but with an unlocked bootloader, it could be used to flash about anything. It's like a secondary recovery in a sense. It's harder to destroy download mode, but still possible if you mess up the bootloader somehow.
For our device the easiest methods to get to download mode are:
- Hold down the power button until the device force-resets itself. The moment the device turns black, release the power button and begin holding down the Vol-Down button. The device with vibrate once as usual, but then you'll see a screen that you've never seen before (begins with "Warning!!").
- Using any shell, such as ADB Shell or a terminal emulator, give the command "reboot download". This may require root privileges, I'm not sure.
- There's apps for this - haven't tried them yet.
As for Titanium backup - I love this program and have purchased Pro (totally worth it). As others have said, it's a bad idea to backup/restore System apps. Only do so with extreme caution. It is possible to restore only the data from system apps, but again do so with caution.
While Google does its own job at re-installing apps after a factory reset (if you allow it to), it usually doesn't backup data for each app. I have a couple authenticator apps that I backup this way, and it works great for this. I've also managed to keep my copy of Angry Birds Samsung Edition from my Infuse. Other applications that have since disappeared from Google Play are still backed up and get migrated to each new device I purchase.
And for that matter, with almost every User application, you can easily back it up (with data) and restore it on a completely different ROM. When changing major android versions, you sometimes will find apps force-closing on you, requiring that you wipe their data... but I haven't had that problem in a long time.
You'll see some other things that you can backup, like SMS, Access Points, Bluetooth Pairings, etc. .... I recommend only restoring these with caution - especially cross-ROM or cross-device.
Okay, I'm done being long-winded. Good luck, have fun.
Good write up
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Aou said:
Here's the thread that explains how to return to stock using Odin. Be prepared for a large download.
http://forum.xda-developers.com/showthread.php?t=2261573
Thank you so much!
In short, "Odin Mode" is the download mode that's built-in to just about every modern Samsung device, beginning as far back as the Captivate, afaik. Each device has a button combination to enter "download mode" or "odin mode". This special mode sometimes requires specific drivers to connect to your PC. Flashing stock firmware using this method is common, but with an unlocked bootloader, it could be used to flash about anything. It's like a secondary recovery in a sense. It's harder to destroy download mode, but still possible if you mess up the bootloader somehow.
For our device the easiest methods to get to download mode are:
- Hold down the power button until the device force-resets itself. The moment the device turns black, release the power button and begin holding down the Vol-Down button. The device with vibrate once as usual, but then you'll see a screen that you've never seen before (begins with "Warning!!").
- Using any shell, such as ADB Shell or a terminal emulator, give the command "reboot download". This may require root privileges, I'm not sure.
- There's apps for this - haven't tried them yet.
As for Titanium backup - I love this program and have purchased Pro (totally worth it). As others have said, it's a bad idea to backup/restore System apps. Only do so with extreme caution. It is possible to restore only the data from system apps, but again do so with caution.
While Google does its own job at re-installing apps after a factory reset (if you allow it to), it usually doesn't backup data for each app. I have a couple authenticator apps that I backup this way, and it works great for this. I've also managed to keep my copy of Angry Birds Samsung Edition from my Infuse. Other applications that have since disappeared from Google Play are still backed up and get migrated to each new device I purchase.
And for that matter, with almost every User application, you can easily back it up (with data) and restore it on a completely different ROM. When changing major android versions, you sometimes will find apps force-closing on you, requiring that you wipe their data... but I haven't had that problem in a long time.
You'll see some other things that you can backup, like SMS, Access Points, Bluetooth Pairings, etc. .... I recommend only restoring these with caution - especially cross-ROM or cross-device.
Okay, I'm done being long-winded. Good luck, have fun.
Click to expand...
Click to collapse
Thank you so much!