I read a similar post to what I'm about to say, but no one answered their question so I'm posting mine. I have a rooted Captivate with Froyo. I installed ROM Manager, attempted to flash Clockwork Recovery and it now says that Clockwork is my current recovery. I tried to backup my current ROM and it went into recovery and then rebooted. Nothing is listed under Manage and Restore Backups. When I went to CyanogenMod.com to download their ROM, it said you can't flash Clockwork to Froyo. Is this true and if so, is there an easier way to flash Cyanogen other than flashing back to Eclair, flashing Clockwork, reflashing Froyo, and then installing Cyanogen?
Im having the same problem so i will bump this.
Same here...
I'm seeing same behavior. Did anyone solve this yet?
Related
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Handalaan said:
So here's the deal:
I've been working with a pretty decently running version of Cognition for the last two weeks on my Captivate. I decided to give Perception II a try and check out some gingerbready goodness. That's where the problem started. Perception for some reason wouldn't allow me back into Recovery Mode no matter what I try so I forced the phone to download and flashed back to 2.1 stock with ODIN. I then reinstalled CWM Recovery and tried to flash back to my Cognition backup I made in ROM manger.
The process looks like everything completed fine but when my phone boots, it loads the AT&T screen for a minute or two and then reboots into recovery mode.
What's the deal?
The details I had when using Cognition was:
CWM Recovery (I believe with LagFix)
Overstock Kernel
It didn't work with my original 2.2 backup either, I still get the same boot into recovery problem.
Any ideas?
Click to expand...
Click to collapse
Let me guess, you didn't convert back to RFS before flashing??
Try Factory reset. And don't use the backup you have for Cognition, Flash a fresh full ROM. Your backup could be messed up.
EDIT: Studa beat me to it.. Grrrr
studacris said:
Nandroid backups don't actually restore the rom, just your settings and **** of that particular rom. You have to Flash cognition then restore the backup and it'll be like you never changed anything.
Click to expand...
Click to collapse
This is exactly what I needed to do. Apparently, (after finding a link I somehow overlooked before posting this) it had something to do with the format of the partition so upgrading the Stock to Cognition forced the RFS to EXT3 change allowing -all- of my backups to work. Thanks guys for getting me in the right direction.
Perhaps Im a little Slow
So Im suffering the same issue. Running Serendipity 7 update 2
I looked down at my phone one day and it was in clockwork recovery v2.5.1.2
I figured I had loaded it by an errant button press. So I selected reboot system now. It goes back into Clockwork right after the serendipity 7 splash screen.
Tried Factory Reset
Tried doing a restore
Tried doing a serendipity 7 re install Original and update.
I can install zips from sd card including the external one.
Any Recommendations ?
I have a kind of complex, quick question. After I rooted stock but before I flashed CM7 on my G2x, I followed the guide on the CM wiki for flashing clockworkmod recovery through ROM Manager and ended up "fake flashing" my phone back to factory settings. However, I made a nandroid backup first and then followed the guide here on XDA for flashing NVFlash using the NVIDIA drivers, and successfully flashed CM7. My question is, I want to go back to stock to upgrade to the OTA with the new baseband and was wondering if it's safe to flash that backup i made with the clockworkmod recovery that fake flashed my phone or if I should just play it safe and download the stock 2.2 rom listed on the guide here?
http://forum.xda-developers.com/showthread.php?t=1088728
Thanks for your help.
I went ahead and flashed the backup in question and it seemed to work. I then reverted everything to stock (ROM, recovery, unroot), tried the LG updater which failed, bricked my phone (stuck on S/W Upgrade), followed the unbrick guide, and successfully got GB OTA running on my phone, so mods can close this thread.
Hi guys I really hope someone can help me with this. I was running CM7 Nightly rom and decided to try and flash eaglesblood 2.3.5 and it flashed ok but the problem is that when I tried restoring my back-up on it I get an clockworkmod recovery error. Any Ideas?
I don't know what phone you have or which version of clockwork you are using, but for some phones clockwork recently got an upgrade to 5.x.x. If you upgraded your clockwork after you made your backup, the previous backups will not work with the new version. You may have to downgrade. Like I said, I don't know your issue, but that is a possible solution.
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
CZ Eddie said:
I have:
Infuse
Infused ROM V2
So today I downloaded "ROM Manager" and "ROM Manager Premium" from the market. AFAIK, this means they are up to date as of today.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a nandroid backup.
Then booted normally.
Then attempted to install MYUI via ROM Manager download.
It bricked the phone.
Restored the phone with Odin.
Rooted.
Then installed both ROM Managers.
Then installed CWM Recovery.
Then installed the 3e mod fix.
Then booted to CWM and did a restore from the new backup done earlier in the day.
Now it just hangs at the Samsung splash screen.
Any ideas? I have a LOT of investment in the backed up ROM and don't want to lose it.
Click to expand...
Click to collapse
I dont know what ALOT of investment is.......but what i think happened here is this<<
You were on Gingerbread right, Infused v2.x.x and you made a Nandroid(thats fine)
u installed miUi and didnt have the luck you wanted...Thats fine
You went back to stock, and rooted and modded the Recovery so you could restore your nandroid....Thats fine
But if you went back to stock(Froyo Right) and try to load up a Gringerbread Nandroid on top it shouldnt work. Nandroids only back up the ROM not the Kernel......so you were in a sense trying to run a Gingerbread Rom on a Stock Froyo Kernel......
Go into CWM flash your Kernel, or use odin and flash a Ginger Kernel then go into CWM and RESTORE.
Happy FLashing
Didn't know that! That may explain a lot of my ROM frustrations.
I'll try this and report back.
Off to go find a suitable kernel....
I really should get my post count up so I can get past this horrible 10 post restriction.
Did you try initiating the flash through CWM or through ROM Manager? Honestly I don't prefer to do any work via ROM Manager, I always have more luck going through CWM and starting a flash from there. Kernel is the first place I'd start but you should also Factory Wipe and Cache Wipe each time you move between ROMs, sometimes you get very lucky and don't need to, most times you bork your phone, and if you're nandroiding back from a backup wiping before you restore is good practice just to make sure you don't leave anything behind from your old ROM.
I installed a gingerbread kernel:
http://forum.xda-developers.com/showthread.php?t=1212485
Version 1.1.
But it didn't work out.
So now I'm fighting with trying to get a stock Infused V2 ROM on there.
No luck yet. Once I do, I'll try the recovery again.
Btw, I'm using CWM for everything.
Go to mounts and storage in clockwork recovery then select format system then do your nand restore ...
Sent from my Samsung Infuse 4G - 1.6ghz
Wow, I was totally making some rookie (which I am) Android mistakes today.
Every time I tried to restore the backup image, I was doing it in CWM by selecting "install .zip from SD card". When I SHOULD have been using the "backup/restore" function.
I'm up & running again. All original apps/settings are restored. Great!
Now to start breaking things again, since I know how to restore from backup now.
Hey guys,
I searched around and only found some old posts for this topic.
I just bought this phone, I rooted it, simunlocked it, and added two day old CWM recovery. Its a S4 Canadian (Bell) version in case that helps..
Is there a way to apply the OTA update WITHOUT having to wipe my data and settings and reflashing a rom?
Hlep will be greatly appreciated!
THANKS :good:
I got the same thing going on. I have a TMOUS HTC One S stock with CWM Rooted and such. I just changed it back to the Stock recovery, but doesn't seem to help. Is there something else I need to do? Maybe I need to flash a newer recovery version?
I have the stock recovery from a MoDaCo topic I can't list because I don't have 10 posts yet.
its topic/353006-interim-clockworkmod-touch-recovery-for-the-htc-one-s-stock-download/ though.
Are you sure your Rom is absolutely stock. For example if the rom is tweaked in any way or if bloatware has been deleted then you won't recieve the update
Ok so I got the update to work. This is what I did: in CWM I backed up a nandroid. I flashed a stock BACKUP for the HTC One S (I moved the zip to the clockwork > backups folder on the sd card). Rebooted into bootloader, flashed a stock recovery from modaco, rebooted, ran the update (I had to update twice, from 1.53 to 1.84 to 2.35). Then I restored my original nandroid. Problem is, the update didn't stick. And now I'm getting an error when I try to turn on wifi. Any ideas? I feel like I got so close...
Tough to see what went wrong.
I had a brand new stock rom with no modifications.
Then I flashed stock recovery,
Did a root keeper (play store app)
Then did the update
And restored root.
Worked out fine for me!
I think you should flash a stock rom and not a backup..