So, I just did a backup of my Glorious Overdose setup using the voodoo recovery it comes with and I got MD5 errors while trying to restore...
Anyone else have this issue?
I never restored from a cwm successfully, I think its not fully functional. Red nor orange... luckily I saved my apps & settings using mybackup
I have also had this problem. if anyone knows why, please let us know. I was able to restore data, but a couple funny things happened. when restoring, i get error restoring boot image or md5 sum mismatch. when restoring data, my phone stuck at restoring android_secure. i pulled the battery and rebooted. luckily that didnt brick my phone.
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
sidekick_fanatic said:
fiveseven808, did you flash cwm through rom manager? if so, i think that might be the problem. i flashed through rom manager and was having problems backing up/restoring. i went to this thread: forum.xda-developers.com/showthread.php?t=1124453 and downloaded the update.zip file in the first post, saved in my download folder. i then went to the root of my sd card and deleted the update.zip file that was there. i moved the other update.zip from my download folder to the root of my sd card. rebooted into cwm and took a backup no problem.
Click to expand...
Click to collapse
I did! But I was unable to use it... or something really strange happened..
Before Glorious Overdose, I could boot into CWM 3 using the recovery boot method. After Glorious Overdose, I realized I could boot into CWM Voodoo with the three button method getting around the stock recovery, and boot into a VERY broken CWM 4 via ROM manager.
Will your advice fix whatever I did wrong?
I have no idea, but you could try it and see. if it doesnt, your no worse off than you were to start with.
Update: I now know for sure that having the right update.zip file will fix the issue. I had to restore my phone today due to issues caused by unknown sources. I tried to fix the issues before doing a restore, but no luck. so I booted into cwm and hit restore. it worked without a single hitch. So the problem (for me at least) was definitely having the wrong update.zip file.
I have never had this issue, with VooDoo or regular CWM... Bad update.zip sounds like it would be the problem, as you said
i believe the issue is in the update.zip file. when flashing cwm through rom manager, i was unable to properly backup and restore. after switching the update.zip with the one found in the dev thread, i can backup and restore to my hearts content. i am very glad to have fully functional cwm on this device, as i had it on my last phone, the tmobile comet. the comet was my first android device. i was not entirely happy with it, but it gave me enough of a taste of android to figure out i wasnt going back to blackberry. prior to android, the best phone i had ever owned was a blackberry pearl. now, the sk4g is the best phone i have ever had, even better than the blackberry pearl. for me, this keyboard has no parallel, and the setup and ui is nowhere near as tough to get used to as people had been saying it was on the forums. but i digress. cwm is the best alternative to the stock recovery, and its good to have it working on this phone.
Related
Oh boy. I think I really messed up here. I have searched these forums and others. But I made some big mistakes (I think) which I cant find help for.
Root method: unrevoked. Rom: cm7. Attempted to flash savage zen kernal via kernal manager (for the first time).
Ok so I have been sucessful in flashing roms with rom manager. So I thought I would give kernal manager a try. I did not back up before flashing the kernal ( I understand now that I should have just like I ALWAYS do for a rom). I attempted to flash the kernal and the process stopped at hboot. I then went into recovery and installed the kernal from the "intall zip from sd card." I was then back in fastboot unable to get back to a working phone.
So I took out the sd card out and put in on my mac. I then took a old nandroid back up file and put it on the sd card. I then put the sd card back on the phone thinking I could restore back to that back up. THe file could not be found. While the phone was sitting on my desk at the backup/recovery I bumped the phone pushing it into backing up. Geezzzeee. I have wiped cache and davik cache. Anyway, now the only back up I see is the mistaken one (the one that I just did, but didnt mean to do). So here I am. HELP.
Please dont be too harsh. And thank you.
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 tried installing xionia custom recovery with an ez installer but it didn't install xionia and it seems like it uninstalled my stock recovery or it really messed it up. When booting into recovery phone won't go past the LG logo. I have tried everything I can think of to try to install a few different recoveries that I have found that work with this phone including stock recovery but nothing is working. Maybe a setting is preventing my phone from going into recovery? I have no idea and I don't know what else I can do to get a nandroid backup. I am dying to get rid of this sprint crap cuz this phone hardly has any space as it is and I have to keep uninstalling apps so I can receive text messages cuz it's so full.
I'm not sure if there's anything else I can try, after trying to install the recoveries I have found- xionia, amon ra, stock recovery, and one other I can't remember the name, I've tried installing them all through android terminal, from my computer using adb shell, and I have even tried different one click tools. I have unrooted and re-rooted my phone and I have uninstalled alot of apps so I'd have more space for recoery incase that was a problem but nothing has worked.
If anyone can think of anything else I'd appreciate your suggestions!
the only reason why you would need a recovery is if you want to flash a custom rom. if you only want to uninstall the bloatware, just use root uninstaller or titanium backup.
now if you just want a custom recovery, try this. if that doesnt work, post what happened earlier (step by step)
Thanks sweetnsour for replying, I gave up for a little while cuz it seemed I had tried everything and i was getting real annoyed cuz it seemed nothing was working. I tried installing the recovery you mentioned but it didn't work either but I think I figured out what my problem was, IDK if there's supposed to be a minimum amount of space on your phone when you flash recoveries, I assumed when you uninstall the stock recovery that'd make room for the new one. I finally got xionia to install after I uninstalled a bunch of apps and got a new sd card. There was virutually no space on my phone or sd card so maybe that was the problem when I was trying to install the recoveries before cuz it uninstalled the stock recovery but then I couldn't get any of the custom recoveries installed and then I finally made some room on my phone and got a new sd card and it finally worked. Hopefuly this can help anyone else who happens to have this problem. I can't wait to see what's up with all of these custom roms now!
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
ihabelnaccash said:
Currently I am in a soft brick state- I cant remember which CM- 9 either cm-9-20120614-EXPERIMENTAL-skyrocket-alpha5.zip, or cm-9-20120709-NIGHTLY... (I can see that those are the only two I have on my sd card. I am on an ATT GS2 skyrocket
If I boot normally - it stays stuck on the CM9boot screen.
I can use the 3 finger method to boot into CWM 5.8.4.3
While searching for answers I read that this CWM is broken.
Initially I was trying to go back to an earlier recovery. CWM would see the recoveries on the SDcard, but when I tried to recover- it would not mount from the SD card.
I got to CM( by using odin to put an earlier CWM, and superuser on the phone, then installed Rom manager, then used rom manager to flash CWM (via tmobile sgs2) then updated to CWM touch...
When I tried using the CWM to factory restore and cache wipe it starts then hangs I cant install zips from the external SD card, or any recoveries...
I'm figuring worst case - I can go back to ODIN, and do stock recovery http://forum.xda-developers.com/showthread.php?t=1342348 , then flash the non touch CWM, superuser http://forum.xda-developers.com/showthread.php?t=1340526, then flash a recovery from my sd card??
Is there something else I might have missed in trying to get back to a functional state without going to odin?
Many thanks in advance for any assistance
Ihab
Click to expand...
Click to collapse
Hi there,
I recently experienced the same thing, and it was a hassle to fix--but I have got my phone working each time. The downside being that I /had/ to switch over to Odin. Mind you, I am not necessarily experienced with Android, so I can't really say that this is the only way.
At any rate, here's what I did to get it back to normal:
Load up Odin
Put it in download mode -- I assume you know to hold the volume keys and then plug in the USB.
Flash either the ICS leak or the stock 2.3.5 Gingerbread.
You should be back to good. I hope you backed everything up in either Kies or some other resource...else you're in for a hell of a time setting stuff up.
Oh: bad news about the 2.3.5 stock is that, as far as I can tell, you're unable to upgrade to 2.3.6. In turn, you're then unable to update to the official ICS through Kies or OTA. I assume you don't mind, considering you're trying to flash a new rom anyway.
Anyway, I do hope there is some bit of clarity on getting CM9 on the Skyrocket. As of now I have still been unable to do it. Just as you, no matter the settings I try, I end up being stuck at that screen. The only difference between your method and mine is that I completely did mine through CWM...nothing through ROM Manager. (Actually, I believe I tried a few differing methods involving the CWM touch and non-touch...followed many different guides but still no good.)
Hope you get it back to a functioning state. If you get CM9 working on the Skyrocket, I'd appreciate you sending a bit of details on how to do so.
EDIT: I am now on CM9. Through magic, ponies and friendship I have failed to accomplish this feat. But by pure science and the blood of a pony, I have successfully installed CM9.
After you've restored to 2.3.5 or the ICS leak (the one I was on), do the following:
- Grab the recovery-clockwork-touch U27 described below. Flash it.
- Download both the newest CM9 build from their website, as well as Google Apps, and then copy those to your external SD.
- Follow this guide: http://www.teamchopsticks.org/p/install-guide.html. Here's what's relevant to you:
Wipe data/factory reset.
Format /system (mounts and storage->format /system).
Install the CM9 zip from SD card.
Install the gapps zip from SD card.
ONLY IF YOU ARE ON TOUCH CWM RECOVERY: Format /cache (mounts and storage->format /cache)
Reboot. Let it sit for a few minutes after the first boot. Be patient.\
Click to expand...
Click to collapse
After ~10 minutes you should be fine. Mine took less, but I'd bet it could take longer. Please follow those directions above EXACTLY. I'll be happy to help you in any way I can if you reply to this thread/ send me a PM.
When I softbricked with the latest CWM I wasn't able to return back since it wouldnt detect my SDcard so I just loaded up odin and used recovery-clockwork-touch-5.8.1.3-hercules.tar and was able to read my SDcard again which had all my backups and CM9 files. I have flashed every version of CM9 every since and still using this CWM version and havent had any problems. :good:
All better now- I used ODIN to restore to stock, then used it again to put CWM (non-touch) back on, then added superuser, then just did a restore from SDcard! Muchas Gracias all!
Should I be able to then use a restore of when I had a working CM9 (and backed up with CWM)? Or would I have to do all the cache wiping/ factory reset like I did to install it the first time before using such a recovery? (and I will try that recovery- clockwork touch hercules... latrer tonight from home)
ODIN tar to restore back to factory. I got the boot loop too. Only until after I flashed CM9 then flashed dark side wipe cache only would CM9 work for me. Only on regular CWM though. Try and give that a go.
Sent from my SAMSUNG-SGH-I727
My old phone got lost so I am using my Infuse again. I decided to update it since it is still on the old version from when it first came out. I was trying forever to update through the kies software until I realized I rooted it and so this won't work. So then I found out there are roms for way better versions anyways. So I found the Cyanfox rom and I wanted to do that, but I needed to first upgrade to cm9 so I went and downloaded the cm9 file and got the clockworkrecovery, and I installed it.
Now my phone will not turn on, it sits as samsung screen. And if you try to go to recovery it is just a messed up screen with all different colors as if the screen was broken. So now my only option to bea ble to install anything on it is through odin. I can get to download mode fine.
But this damn odin software will not detect my phone for the life of me. It literally will not work. I don't understand. I have spent hours upon hours on this between the past few days. I just want to update my damn phone.
Now I have to leave for work in 30 minutes and my phone doesn't work. This is just great.
How did you install CWM?
Sent from my Asus MeMO Pad 8"
Well I tried clockworkmod through the rom manager app, but I was running the android recovery 3e and it said I needed a modified version of that to be able to install 3e. So I replaced the recovery file with the one I was given, and then I manually installed cwm by naming it update.zip and running it on the recovery
The only problem was that every time I wanted to use cwm, it would go back to android recovery 3e, and I would have to click install again to get it to go into cwm.
Either way, it doesn't work anymore and I just need the damn thing to connect to Odin so I can flash it back.
Are you using a desktop or laptop? If desktop, are you using the USB ports in the back? If laptop, have you tried different USB ports? Maybe try a different computer? I've heard that USB 3.0 doesn't play nicely with ODIN so it's good to find some 2.0 connections. What Windows version? I've heard that Win8 can cause problems. Could also try Heimdall instead of Odin.
Unless I think of anything else, is the cable in good working order (recent successful file transfer)?
Alright. I got things working somewhat. I had to use different drivers for each program for it to be able to detect it. I don't know, its annoying as hell, but it worked when I went back and forth between drivers.
Anyways, I got my device restored. But the whole point of this was that I was trying to get to the KitKat rom(Cyanfox). I am still quite a few steps away from that. I am actually further away than when I started,
This is what originally happened: I had my device rooted(from when I last used it, 1-2 years ago) and had the 3e recovery. So I found out I needed a modified 3e so I could install Clockworkmod. Got that, all was well, and the thing basically got bricked when I went to update to a new rom. It wasn't the kitkat rom, but a CM9 rom that I needed to go to first so that I could then update to kitkat.
Now I got it unbricked, and I updated it using kies. So now I am on gingerbread. So then I rooted it again. So now I have the 3e recovery again, the only problem is when I go to system/bin/ there is no file called recovery, and I can put one there but it does not affect the recovery, it still looks for signed files, meaning I cannot install Clockworkmod.
Not sure what to do...
Seems everyone follows this process (looks like you already did step one) now....
1. Either use Odin or Heimdall One-Click. Follow instruction on how to do it.
2. While phone running install sgs kernel flasher from Market/Google Play.
2a. Copy/transfer Synthesis GB Kernel to your Internal SD card.
2b. Start up sgs kernel flasher and choose it from your Internal SD card. Phone will auto-reboot after done flashing.
2c. Wait a bit while your phone convert to new partition format and activate lagfix. Your CWM recovery version should be 2.5.1.3
3. Reboot phone into CWM Recovery and DISABLE vodoo lagfix and /system lagfix. Reboot once done. Phone will convert partition to old format. If you don't turn the lagfix off the phone will hang at Samsung logo when you install new rom.
4. Prepare your flavor rom/gapp for installation by copying them to your Internal SD card.
4a. Go into CWM Recovery mode and install the rom. You will need to do this twice since the 1st time was just a warning about partition format being different.
4b. Reboot once done. You will need to REMOVE the battery to power down the booting process and put it back in.
4c. Go into the New CWM Recovery and install the rom again since the previous attempt only install the new CWM Recovery.
5. Install Gapp.
6. a. Wipe: Cache / Factory Reset <--- Probably don't need it since it's new install from stock unless you installed stuff. Just to be safe.
b. Wipe: Cache Partition
c. Wipe: Dalvik Cache
7. Reboot
Click to expand...
Click to collapse
I never tried step two myself, as I found a flashable download for ODIN that did this for me. But mine is a Rogers phone (not AT&T) so that would not work for you. Hope this helps.
Thanks you so much man. I know that is just copy/paste but I didn't see it, and it works. I was looking in Cyanfox thread, never looked at the Beanstalk thread.
Anyways I am in the process of doing this and it seems like it will work. Appreciate all your help!
Edit: Boom. Worked like a charm. Thanks so much. I am very happy now The funny thing is, half the reason I wanted this is cause everyone was group messaging, and I didn't have that capability anymore when I lost my phone(I was on such an old version). Again thanks so much.