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.
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.
Hey guys so I have a weird problem.
I can't restore my new backups.
That means all backups I did 2 weeks ago are restorable but now, when I do a backup of my current cyanogenmod rom and try to restore it, I get stuck at the HTC boot screen.
I heard it's because I used rom manager and sometimes rom manager destroys the PC10IMG, is that true??
Same thing happened to me. I had to do everything all over again. It will be nice if there is some more information about the problem. Thank you.
whitis said:
Hey guys so I have a weird problem.
I can't restore my new backups.
That means all backups I did 2 weeks ago are restorable but now, when I do a backup of my current cyanogenmod rom and try to restore it, I get stuck at the HTC boot screen.
I heard it's because I used rom manager and sometimes rom manager destroys the PC10IMG, is that true??
Click to expand...
Click to collapse
don't trust rom manager to perform recovery operations through its gui with any consistency.
if you're going to perform a recovery operation, just do it through CWM and save the hassle.
Well I did it all /backups & recovery/ through CWM and just hang on the welcome screen. Not that it was important because I only wanted to back up something I forgot after intending of installing a new rom, but still the question remains and it will be helpful for future time
I've found that Nandroid backups are unreliable if I'm at all low on free space on the SD Card. Even if there are no errors during the backup. I make sure I've got at least room for two whole backups now. Seems to solve the problem.
For some reason my phone got totally hosed up this evening. Everything was fine and I turned the screen off, I then immediately tried to turn it back on and nothing happened. So I hard rebooted (hold down power) and the phone never went past the boot screen. Tried wiping cache, which got it past the boot screen, then it went through the upgrading apps process, then when that was done it got stuck at "starting apps". It seemed like the System UI would not start. I left it for 5-10 mins and it never booted into my launcher.
So at that point, I decided to do a nandroid backup, then wipe my phone completely, and reinstall AOKP. That got me back into the phone, but my plan was to use the "Extract from Nandroid" feature built into Titanium Backup Pro to restore my apps and data from my nandroid backup. When I tried this, TB saw my nandroid backup, but selecting it brought up an empty apps list. I have successfully used this feature in the past without any issue - though I am not sure if I have used it since Android 4.2 was released.
So, I decided, let me see if I can browse my nandroid manually via Root Explorer. I navigated to the clockworkmod directory on my sdcard, where nandroid backups have usually been kept and it was also empty! So, I launched ROM Manager and sure enough it sees my nandroid there as well. Then I noticed the fine print:
In Android 4.2, backups are placed in secure directory, inaccessible to other apps. Backups can be pulled with ADB or by using ROM Manager Backup Download Server
Click to expand...
Click to collapse
So, I am currently in the process of using the Download Server to download my backup to my PC. My question is, is there a way to get Titanium to read this zip file I am downloading and extract apps/data out of it like I used to do? Do I just copy the zip back to the /sdcard/clockworkmod directory?
If anyone has already been through this on 4.2 I would appreciate the advice. Thanks! :good:
Hi,
I had a similar problem on my N7 tb wasn't displaying anything from my twrp backups, try appextractor 2 beta from the play store. Worked for me took a few mins to process my back up but then displayed everything perfectly.
Hope this helps
SD.
Same problem... appextractor cannot find anything
This is because nandroids are now saved in a secure file. I'm pretty sure it's /mount/shell/clockworkmod. There's some apps on the play store like cwm backup manager that allow you to make copies to your pc.
Sent from my Nexus 4 using xda app-developers app
mustangtim49 said:
This is because nandroids are now saved in a secure file. I'm pretty sure it's /mount/shell/clockworkmod. There's some apps on the play store like cwm backup manager that allow you to make copies to your pc.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am dealing with the same problem right now...
The reason for your problem is probably that you made your backup with CMW 6 and not 5. Neither Appextractor nor Titanium Backup can currently work with the new backups it seems.
I would greatly appreciate any ideas/solutions!
So basically Titanium is useless with 4.2.2?
texaslittleangel said:
So basically Titanium is useless with 4.2.2?
Click to expand...
Click to collapse
Never had a problem with Titanium and 4.2.2 ever.
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...