Let me preface this: I don't need to use this phone regularly, as my Nexus One is now my primary, but it'd be nice to get this phone back to bootable again.
I loaded up the OpenRecovery version suggested for the CyanogenMod Alpha. From there I took a nandroid backup of my existing ROM (Telus Milestone) and then successfully booted up Cyanogen. After experiencing some of the bugs I decided it was time to roll back.
So I went back into OpenRecovery and restored the full nandroid backup. Well, now I boot up and all I get is the "M". Won't go any farther than that.
So then I tried to flash the GOT version of Telus 2.1 from RSD Lite. It flashed, and then rebooted to... again, the "M", didn't boot further after several minutes. Battery pull again.
Next try - the non-service Telus firmware via RSDLite
(A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf). Rebooting... PHEW! Android bootup screen appears. And it boots, yay. Flashed the vulnerable recovery and returned to OpenRecovery. Nandroid restore but this time *only* system and data. Ick, and once again it hangs... bad backup? Trying a data wipe... it's still not happy, so I guess the system partition is the problem with my backup.
Anyways I have no idea why the backup won't boot, but I suppose I can set it aside, sleep, get done what I need to tomorrow and revisit it on the weekend.
the problem is in your backup. It happened to me twice now that I have to flash the original firmware because the backup also has a problem.
I think I've concluded what the problem is. The modded OpenRecovery that is suggested on the CM6 thread is no good at restoring the system partition. The backup I took from GOT OpenRecovery earlier in September restores fine from GOT OpenRecovery. But none of my backups restore to a bootable state from the other OpenRecovery.
So what I had to do was restore the older backup from GOT, then switch back to the modded recovery and restore only the data partition. And next time I try this I will take my final backup from GOT.
Related
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.
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
I rooted my HTC Desire CDMA from USCC okay, flashed a Froyo ROM with USCC stuff, and everything was okay. I made a nandroid backup, flashed CyanogenMod 7 RC4 and it seem to work okay, except I was having trouble entering my password when checking voice mail. Anyway, I decided to go back to Froyo. I used ROM Manager to restore the backup and got into ClockworkMod. However, none of the options work. If I go down to recovery, I go to the next screen, but no matter which option I select I end up with a black screen and nothing happens! I can't restore my backup! If I just try to press power on, I end up with the blue CyanogenMod screen and the arrow just goes round and round. Nothing happens. Please, if anyone has any suggestions, it would be greatly appreciated.
I remember hearing that because CM7 is a Gingerbread mod, it must use ClockworkMod v3 and to go back to your Froyo backup you'll need to downgrade to Clockwork Recovery 2.x. I'm not sure if things has changed, though, this was what I read a month or two ago.
Are you by any chance able to fastboot?
Reflash your CWM (if you are using NAND version) or get it again on your SD (if your are using SD version).
The problem is I can't do anything in ClockworkMod (version 2.5). Every option I select gives me a blank screen! I made a nandroid backup before flashing CyanogenMod, but I have no way of getting to my backup if I can't use ClockworkMod. Also, if I try to boot the phone, i just get the CyanogenMod 7 startup screen with the arrow going round and round. It will still be there 30 minutes later. I have to do a battery pull to start over with anything.
I was able to boot my phone after wiping all user data. I would like to use my nandroid backup to return to the previous ROM, but clockworkmod doesn't seem to work. I tried reflashing it in ROM manager and it only downloads a second or so and isn't really doing anything. I'm wondering if clockworkmod is defective. Is there any other way to flash it again without using ROM Manager?
If you are able to fastboot, you could try to restore a nandroid by flashing three files (boot.img, system.img, data.img) from your nandroid backup using:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
Disclaimer: I've not actually tried this procedure before! I got this info from here
You could use a similar procedure to flash a new ClockworkMod since your recovery may be corrupted: fastboot flash recovery recovery-clockwork-3.0.0.5-vision.img
You can download the image from Koush's website, under HTC G2.
This happened to me yesterday trying out the Alpha Build for the Fascinate. I was getting a dev block error and datadata would not mount. I had to go back to stock on heimdall. I don't know if this helps for your phone, but maybe somone with more knowledge can tell you if this may be happing to you and what the fix is, if that's not a fix for you.
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
So I made a Nandriod backup, installed a new rom. I didn't like it so I restored my Nandroid backup. But instead of rebooting, I installed a new update of the rom which I restored through the Nandroid backup. Due to this I could boot into my rom but I didn't have a cell signal. I also couldn't boot into my recovery(tried flashing boot.img of latest recovery through Flashify but that didn't work either). It directly booted into my rom. Phone didn't have any problem booting into the fastboot mode. Anyways, I then connected the phone to my computer, booted it into recovery with terminal, restored my Nandroid+EFS backup and now have a fully functioning phone.
I want to understand what I did wrong here so that this doesn't happen again. How did my IMEI get corrupted? Was it because I restored my nandroid backup and installed a new version of the same rom without rebooting? Or was it something else?