Hi all,
I just installed ClockworkMod Recover using ROM Manager on my G1, replacing Amon_RA. Immediately before replacing, I did a Nandroid backup using Amon_RA. No problems, lots of dots and then it returned. After I installed ClockworkMod, I tried creating another Nandroid backup, first from the recovery screen and then from the ROM Manager app. Both times the backup hung on the message "Backing up .android_secure..." and required a battery pull to get back. The last time I let it go for over an hour before giving up. I'm running CM6 stable, if that matters.
Any idea? I'm about to put Amon_RA back on, so I can get good Nandroid backups again.
I know this is an old post but I am getting the same thing. Going to continue researching.
hmmm last time i had an issue kinda like this it was the recovery... need to re flash it somehow.. maybe the sd ext has something to do with it also...? im not sure but i would try to re flash recovery or maybe switch back to amon-ra if all else fails can always re-root
Mine took over 20 minutes today. Just when I was about to pull the battery, it moved on. Probably down the amount of stuff you have on your phone I guess.
I'm running a 32GB card stuffed with apps
havent used clockworkmod in a long time, i stick with amonra -- but if i remember right with clockwork isnt there an option to have a status bar so you can see how things are moving along? maybe not...
Related
I was using KangORama and loving it but decided to give Rodriguezstyle a chance. I had done a nandroid backup and flashed the Rodgriguezstyle ROM. I didn't particularly care for it so I went into recovery and tried to do a nandroid restore. It went through the motions and got to "as is" then froze. For at least 15 minutes. I had to remove the battery and now when I reboot, it stays on the Google colored "X" screen. What do I do to fix this??
I rebooted into recovery and reflashed Rodriguezstlye (only ROM I had on sd card) and the phone is back. I'll move back to Kang-O-Rama now. Why would nandroid backup cause this?
So tonight I was close to a freak out. I made a Nandroid backup of my CM 6.1.1 system. And then I restored a backup of an old 2.2 stock rom. After that I did a wipe / factory reset thing since I wanted to play with plane untweaked and new stock rom. When I got bord of it I booted into recovery mode via "power + volume down" and tried to restore the CM Rom which it refused to do. One point showed up and then it aborted and said something about "something wrong, nandroid restore doesn't work" - cant remember the exact words. So I thought "**** maybe the backup is corrupt". So I tried another one. Which didn't work either. So I actually ended up trying every single of my 22-ish backups. None of them worked. So instead of having a heart failure I just went to bed and told myself I would deal with it today. So today I wanted to boot into recovery mode so instead of dealing with my broken power button I installed 1-click universal androot and quick boot. I soft rooted the phone (obviously stock roms are not known for its rootedness) and rebooted into recovery mode where my restoration attempt succeeded like it always does. So now I'm curious why it worked today. And I must admit it sounds obvious. But it has to have something to do with the fact that I rooted my phone. So is that true? Can recovery managers only write the images of a nandroid backup when the phone is rooted. I thought the fact that there is a recovery image that is capable of backing up and restoring a system has all necessary rights through its bare existence? Just curious... =)
arminsoyka said:
So tonight I was close to a freak out. I made a Nandroid backup of my CM 6.1.1 system. And then I restored a backup of an old 2.2 stock rom. After that I did a wipe / factory reset thing since I wanted to play with plane untweaked and new stock rom. When I got bord of it I booted into recovery mode via "power + volume down" and tried to restore the CM Rom which it refused to do. One point showed up and then it aborted and said something about "something wrong, nandroid restore doesn't work" - cant remember the exact words. So I thought "**** maybe the backup is corrupt". So I tried another one. Which didn't work either. So I actually ended up trying every single of my 22-ish backups. None of them worked. So instead of having a heart failure I just went to bed and told myself I would deal with it today. So today I wanted to boot into recovery mode so instead of dealing with my broken power button I installed 1-click universal androot and quick boot. I soft rooted the phone (obviously stock roms are not known for its rootedness) and rebooted into recovery mode where my restoration attempt succeeded like it always does. So now I'm curious why it worked today. And I must admit it sounds obvious. But it has to have something to do with the fact that I rooted my phone. So is that true? Can recovery managers only write the images of a nandroid backup when the phone is rooted. I thought the fact that there is a recovery image that is capable of backing up and restoring a system has all necessary rights through its bare existence? Just curious... =)
Click to expand...
Click to collapse
1) Paragraphs...look it up
2) When you reloaded your stock rom you lost custom recovery. That's why you couldn't re-flash your cm backup.
hey everyone, i'm new here. Sorry if this has been posted before, but i'm having a bit of a problem right now.. I rooted my CDMA hero last night. I made a nandroid backup of my phone before i flashed any roms. I flashed a rom and did something wrong, so i tried to restore my nandroid backup... and i got stuck at the "htc - quietly brilliant" screen. i then found out i'm supposed to wipe all data, so i did, and flashed the nandroid backup again.. same problem. so i flashed a different ROM and it loaded up.. so, again, i wiped all data and tried to restore my stock ROM (google didn't back up contacts when it said they were, so i'm trying to restore to get them back)... and i'm STILL getting the quietly brilliant screen. Any help? Thanks!
When you restore - it does take a while to boot up. How much time did you wait on the white screen? Also, did you get any errors during the nand restore?
no, no errors.. and i waited a pretty long time. Enough to allow the "Quietly Brilliant" screen to flash black, then come back up a few times... i'll do another nandroid restore though and watch for errors. But when i did it before, I didn't see any.
this can happen if you don't have enough space on your sd card during the backup. it has been my experience that nand will not give you an error when it runs out of space, everything appears to have completed as it should, but when you go to restore not everything is there, thus causing the phone not to boot.
also as someone else stated the first boot after a wipe can take a very very long time. 10-15+ mins. (this is not always the case)
my advice (for what it is worth) try a full wipe, and load a new rom. another thing to consider is that most (should be all) roms do not come with gapps built in. once you flash the new rom, before you try and boot it, you should also flash gapps. for instance aospCMod will not load without it.
my sd card actually got messed up before all of this (pulled the battery out when phone froze) so i reformatted it.. it was almost completely empty when I did the backup. It's an 8gb card, too.
yeah i'm actually using a version of aosp, and i installed gapps. i'm currently running it now, but i lost all of my contacts (100+... haha)
I'll charge the phone up, restore and let it be for 10-15 mins like you suggested, when I get home later today. Thanks everyone so much for the help.
daveishere911 said:
my sd card actually got messed up before all of this (pulled the battery out when phone froze) so i reformatted it.. it was almost completely empty when I did the backup. It's an 8gb card, too.
yeah i'm actually using a version of aosp, and i installed gapps. i'm currently running it now, but i lost all of my contacts (100+... haha)
I'll charge the phone up, restore and let it be for 10-15 mins like you suggested, when I get home later today. Thanks everyone so much for the help.
Click to expand...
Click to collapse
Are you using Firerat mod? That happens when the partition is too small.
Sent from my HERO200 using XDA Premium App
aqualls said:
Are you using Firerat mod? That happens when the partition is too small.
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
no
Sent from my HERO200 using XDA Premium App
i was hoping maybe someone could help me with the fact that i can't boot up past the htc screen. i did a search, but couldn't find anything that worked. anyway, i haven't changed anything on my phone - same rom and all - but it was getting laggy lately, and so i thought i would clear the data and dalvik and all that. i figured i'd do a backup first - using RA 1.6.2 it said "performing backup" and the dots kept filling the page, but 15 minutes later it wasn't done so i pulled the battery. now i can't boot the phone (which i find weird since i didn't pull the battery during a restore or anything, so it shouldn't have messed with any files). i did give it over an hour to boot up btw, in case it just needed time to rebuild. tried a backup again (figuring the one i stopped would be corrupt, and thought maybe the phone thought it was still backing up and wanted a complete nandroid to be done?) and it said run via adb. so, i tried flashing clockwork 2.5.0.7 and it looked like it was working at first, but then it just got stuck on "sysinit." i wiped everything and formatted the sd card in case something was corrupt, but still no luck. i realize i COULD reinstall a rom (i'm using aosp froyo) but i'd prefer not to only because i don't have a backup and i'd rather not lose my texts and voicemails if i don't have to.
hopefully i provided enough information. and the battery is fully charged btw. thanks for any help you could provide
That run via ADB message pops up when the battery is below 30%. At this point don't worry about saving the ROM you have right now, all the text messages and voicemails are erased when you do all the wipes. Download a new ROM, put it on the SD card, Wipe everything and flash.
In the future, if you port your number to google voice all your texts and voicemails will be accessible from any computer or new phone no matter what you do.
So I installed Phoenix Rom and clockwork 2.5 last year on my device. I have not done anything since then.
Last night my phone started to play music at full volume in the middle of the night. Since I couldn't find any programs running that are playing music, I pulled the battery. Ever since, it gets stuck at the phoneix boot flash animation (shows the animation for a while, vibrates, and re-runs the animation from the start)
I CAN access the clockwork recovery mod, but I'm afraid to do much because I don't want to lose my data. I was using a backup software but I think it is backing up to my internal sd, not my external sd card.
The only clockwork backup I performed was at one of the steps when flashing the Phoenix rom. Can I use any part of that backup to fix the issue? Should I simply flash the phone to a new rom and hope that my data stays?
No matter how long I let it sit, it stays at the flash animation of the phoenix rom logo.
what backup program were you using?
it doesn't matter if its on the internal...hell i don't even have an external.
(By the way, I was using titanium backup, but i'm not sure if the data has been saved on my internal card or external sd card)
So boot into recovery, mount your sdcard to your PC and check where it is...
No need for a pc. Just use My Files to look for a folder labeled Titanium Backup.
How do you do that without being able to boot into Android?
He's stuck in a bootloop...
studacris said:
How do you do that without being able to boot into Android?
He's stuck in a bootloop...
Click to expand...
Click to collapse
Exactly, I'm stuck in a bootloop. I don't have the drivers on my work computer so I'll have to check when I get home. I think what I'm going to do is simply find a stable cooked rom and install a new one, hopefully I can find a recent titanium backup, but even then, I could never manage to find which packet I needed to backup text messages, so i know those will be lost.....
Sigh, what a pain in the @$$
studacris said:
How do you do that without being able to boot into Android?
He's stuck in a bootloop...
Click to expand...
Click to collapse
Duh, where's my sign? Your right. Was trying to speed read the post while on break.
@op, listen to studa. He obviously had his coffee this morning.