I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
Related
Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
This morning, my Samsung Captivate would not boot. I used Odin 1-click to restore it back to a stock ROM. Then, I re-rooted the phone and attempted to use Clockwork ROM Manager to restore a backup from several weeks ago.
Clockwork seems to run ok. It sees my backup directory and attempts to load the backup. Then it asks if I want to reboot the phone and restore the backup. When I do, it goes directly into manual recovery mode and the backup is not restored.
What am I doing wrong?
Can you boot the phone into recovery then select backup/restore and find your backup in that list? then restore it from there. I always boot into recovery then do whatever i want from there.
Recovery doesn't give me a backup/restore option. Only Reboot, Reinstall files, etc. I thought that it was only Clockwork that has the backup/restore option?
Wait a sec. you went back to a stock rom then rerooted? did it unroot on u? some of the one click roots will unroot you phone if ran while phone is already rooted. kinda a click on click off thing. If you unrooted the phone then it would not let you do a restore. You can do a full factory reset> install clockworkmod,boot into recover and restore backup. just an idea
No, the phone is definitely rooted. The problems I'm having seem to be with Clockwork. I couldn't get clockwork 2.5.1.2 to ever restore, so I downgraded it to 2.5.1.1. I was able to restore, but when I did, I got a whole series of processes with FC loops. It appears that Clockwork did something wrong when it restored my backup.
I finally did the Odin 1 click again, and gave up on restoring. At this point, I'll just re-install everything. I'm disappointed with Clockwork. I would like to find a ROM manager that's more dependable.
woody1 said:
This morning, my Samsung Captivate would not boot. I used Odin 1-click to restore it back to a stock ROM. Then, I re-rooted the phone and attempted to use Clockwork ROM Manager to restore a backup from several weeks ago.
Clockwork seems to run ok. It sees my backup directory and attempts to load the backup. Then it asks if I want to reboot the phone and restore the backup. When I do, it goes directly into manual recovery mode and the backup is not restored.
What am I doing wrong?
Click to expand...
Click to collapse
I just ran into this with my phone..took me quite a while to figure out what I had done wrong.
I had Perception 10.2 ROM on my phone, with Voodoo Lag fix. Today, I decided to try out the official 2.2. release for the Captivate, so I made a Clockwork backup, did an Odin 1-Click back to stock, and installed 2.2. I decided I liked Perception better, so I tried to recover it.
I did another Odin back to original stock, then loaded Clockword and tried to recover my backup. It acted like it worked, unpacking everything, but then booted back to manual recovery mode, and got into an endless loop.
What I wound up doing was running another Odin back to stock, reinstalling the Perception ROM, and THEN restoring with Clockwork. The problem appeared to have been with the Voodoo Lag Fix, which uses a different filesystem.
So, try reinstalling the ROM you made the backup with FIRST, then do your recovery. Good luck!
The rom I was restoring was the same one that I already had on my phone. I think the problem might be this:
I originally had 2.1.1 which was rooted and had one-click-lag-fix installed. When my phone was borked, I used Odin to flash back the same rom. But I think the problem may have been caused because I didn't install OCLF again before I did the restore. I'm not sure, but I have a guess that it might have worked had done that.
Hello, I'm new to the forums and I feel bad I'm already screwing things up :/
Anyway on to the problem... I've had CM9 running on my phone for about two weeks now but I wanted to get rid of the rainbows in CWM and at boot. Today I downloaded Rom Manager from the market place, and when I ran it, it prompted me to install CWM recovery to my SD card, although I already had it installed I thought I'd give it a try. Bad idea, now I can't leave recovery mode, my phone will continually reboot into recovery, I've tried wiping all data and clean installing CM9 again and still nothing. I've even tried the exitrecovery.zip script to no avail
Any suggestions or ideas on how to fix it and boot into my ROM again?
Thanks!!
I would venture to say you might have to reflash...or start over from stock...
i would reload stock....then reload ics or the rom of your choice...
Thanks a lot! Worked like a charm, I used Odin and flashed factory stock 2.2.1, now I'm off to getting ICS back.
Thanks again!
Does anyone know why this happens? I've noticed that anytime I open CWM and choose the boot to recovery option is when I get stuck with CWM Recovery looping. I then have to go back to stock and start over again.
I'm not entirely sure why it happens, my guess was that it puts up a bad flag not compatible with ICS that keeps it from booting that, that was why I tired the exitrecovery script, I looked through it and it appeared to me to change a flag for booting. I'm not sure why it happens but I'd say just use the reboot to recovery option that the ROM provides in the shutdown menu, I know that always works.
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
bejahu said:
Using ROM Manager and the latest version of CWM I tried installing today's (12-08) nightly build of CM11 to try it out. After doing a complete backup and then wipe data/cache the install failed. I'm not sure why but it said it was aborted and to check log and report the error to ROM Manager.
After that it asked if I wanted to reboot and I wanted to make sure I restored from my backup so I backed out of the screen but then it booted up on its own. It did not get past the S3 loading screen with the CM Android/alien guy it just turned off, back to that screen again and then back into recovery.
At this point I went to recover from my backup file and it said MD5 mismatch and won't load. I've since tried wiping data/cache/dalvik cache all manually and then boot up, or wipe everything and try to install the rom again... every time it just loops back to recovery mode. The last time I tried installing the rom again it told me I might have lost root access and asked if I wanted to repair it... I'm not sure what that means.
Any suggestions? I am lost at this point. I have no experience with ADB (I'm not sure if that's my only option) but I've used ODIN mode a few times. Easiest solution would be best.
Click to expand...
Click to collapse
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Badouken said:
I had the exact same issue when trying to flash that same CM11 nightly build but with TWRP...
I just pulled the battery took my SD card out and reinserted it and I just kept booting into recovery and turning the phone off until it let me reflash a rom or backup. Obviously this isnt the most legitimate solution but that could work for you! It did for me!...
This could have been caused by needing an update of CWM or TWRP to better support 4.4 perhaps?
Click to expand...
Click to collapse
I tried that to no avail. I unfortunately had to revert to stock unrooted via ODIN mode and it got me to boot back up. I can just reroot now. Luckily I made a backup with Titanium and uploaded it to my Google Drive.
Hi everyone!
I figured, why not give MIUI a try. I downloaded the rom, made a full TWRP backup, then installed the ROM. It just froze after the MIUI logo appeared, so I decided to restore.
All the while, I noticed a new red Oneplus logo where the old one had been white. But even after restoring my backup, the startup logo was still red, and my previous rom was freezing during the boot animation. I tried again, no luck.
Then I thought, I'll just load my old rom (Vanir/Exodus) from the downloaded zip OVER my restored rom, maybe that will fix things. It won't let me do that, however, due to an error in TWRP which I've never gotten -- "Error executing updater binary in zip".
So I went to the bootloader to update TWRP, and noticed the whole bootloader looks different and is in Chinese. So it must've been part of the MIUI ROM.
What do I do now? I'd love to just fix the bootloader but not sure how. Maybe if I did that I could then restore my backup. As a precaution, I've ADB Pulled the backup folder just in case I have to start over, then I can copy the backup folder back in and try to restore it........
Thanks for the help!
Well, I figured it out on my own. I went to download the latest version of CM12 from here, and ADB Pushed it while in TWRP. I then installed it, and it didn't give me that assert error. I rebooted, but powered down while it was starting up, went back to TWRP, and restored my backup, no problemo. I wonder what happened.
It would be nice to understand what the issue was that prevented me from restoring it initially, and what I could have done manually to update the particular thing that I needed to update.
Pretty sure it was an the firmware ColorOS uses and is incompatible with the newest roms based on the CM firmware