Related
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.
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
Hey people.I have a friends sgs4g...Not sure what they did to it,but cwm boots up,but when you flash a rom,it reboots into cwm and says
it cant mount cache/recovery/command,cant mount/cache/recovery logs.
What should I do here?I have sgs2,so this is a little different for me
I would use the Heimdal One-Click for back-to-stock (GB), then the one-click for AntonX kernel (same thread), then you should have a functional phone again (with CWM) and can go from there.
Or one click gremlin remover which will give you stock 2.3.6 with cwmr,& rooted. And no need to flash anything else,unless of course you wanna flash a custom rom
You can find it in the development section of this forum
Also just skip to part 3 of his instructions
well here is the thing..he tried to put on cm9 or miui...he said cm9miui,but I always thought those were two different dev trees?Anyhow,he got it on,it started,then now it just reboots back to recovery...he tried nand recovery,and it just did same.Now he has tmob loaner phone or what not with his original sd card in that phone..doesnt cwm put some file folder on sd once installed?If there is a new empty sd card,can I do what was said above without bricking anything.I had this phone last year,and forgot everything about it,so thanks for the help fellahs
Anything that it puts on the SD card can be deleted/removed/missing...if it needs it ....it will replace it...without issues
See image attachment first: I beloved the SD card slot on my infuse is corrupted or broken. Would this keep a custom recovery from installing or being usable? Every time I flash back to stock and then flash an insecure kernel with cwm and root and busybox and what not I try to boot back into recovery and the 3e recovery is still on there. I'm almost positive the SD card slot is broken cause it doesn't detect it even when I flash to stock and boot normal. Will this keep me from getting a custom recovery?
Have you tried backing up and reformating your internal USB storage (the one that is approx. 13.3GB in total size)? The one the phone calls SD Card is actually your external SD card. Confusing, because in CWM sdcard is internal storage and and sd-ext refers to an app2sd partition not supported by Infuse kernels.
That's assuming that the SD card is the issue. You may just not have root permissions required to flash the kernel from the phone or CWM.
Best bet is to use Heimdall (recommended) or Odin (also good but a bit more finicky) to flash the kernel you desire. This should get you an unsecure kernel that you can use to flash the rom of your choice. Make sure your internal sdcard is working properly first and copy at least one rom install file to your internal sdcard before starting.
Follow the link in my sig to the super everything thread (ISET) for Heimdall and Odin options (should be in the first group, might be in the 2nd or 3rd post of the thread).
Yeah let me give you a little more background on the device. Ive odin'd and heimdalled it back to stock multiple times at which the device works, but the play store and multiple other apps do not work. The Sd card (external) I am assuming, cannot be recognized either. Ive fixed this phone before for a friend but IDK if I ever got the sd card to work but everything else did. Now I'm trying (and I had problems with this before) to get a custom recovery on here but the SD card error I keep getting (internal or external I dont know) keeps me from doing that. It keeps reverting back to the 3e recovery. I have flashed many different heimdalls icluding Entrophy's kernel that is supposed to give me CWM but it never works. Is there a heimdall one click that also includes kernels, custom recoveries, and so on? Cause I have searched trust me it took like 5 days of searching last time to fix it and now I have to do it again. Thanks! Oh and P.S. Odin keeps failing to flash tar.md5 files as well. Idk if its the version im using (Odin3 v1.7) or what. Oh and the phone is now in the connect phone to PC screen and not download mode. Thats happened before so I know its not bricked but I forget how I got it out of that mode. Thanks again Zen!
Oh and also every time I use Heimdall and install the drivers so it can comunicate with my infuse it causes Odin to not detect the device and vice versa. If I want to use odin I have to install a different driver, and with heimdall I need a different one haha. Its a dumb circle I'm stuck in ;P
Last item first. I've been able to get around the Odin vs Heimdall thing by using different USB ports for each. If you've been trying both on multiple ports you may need to run device mgr on your PC and remove some hidden devices. See here for instructions:
http://forum.xda-developers.com/showpost.php?p=33980291&postcount=11
As for the sdcard, I'm still recommending that you backup both sd cards and try a reformat. You can do this via the phone, or while connected via USB. You may also want to flash a stock package (with pit) after backups and before the formats.
The recovery is part of the kernel, so something else may be at work here.. if you get a good kernel flash you should get the recovery that comes with it. Try running CPU Spy and look at the bottom of the page to see the details. Post a screenie if you can.
The problem you described could be due to where installed apps are stored on the phone. Android creates a hidden area on one of your two SD cards (somewhat annoying if it ends up being the removable one..)
If the sd card is a problem this would explain why some things don't work correctly. You can try via the Settings-->Manage Applications interface to move apps to the phone. This relocates them to the /data partition and off either SD Card. If you get errors attempting this that further confirms sd card problems.
Not sure why a blown SD card would block a kernel flash though... have you confirmed that you have root? Have you tried flashing a zImage file directly using SGS Kernel flasher? Try to extract a zImage from a CWM zip file and copy to your phone then run the app to flash. Make sure the kernel matches the firmware (i.e. Froyo, GB, etc..)
Wow that was a lot of information haha. Alright I got my phone out of the connect to pc screen and i used odin to fully reformat including PIT, PDA, and Phone files. After that completed flashing it rebooted into 3e recovery on its own for some reason and it comes up with some errors saying it cant mount /data. This i believe is on the internal SD card and has to do with the system apps. The phone bootlooped at the att splash screen. After that I used another Heimdall reformat "Stock_SGH_I997_UCLB3_Repartition-One-Click" which successfully flashed but still bootloops at the att screen. I got it fixed before but I have do idea how haha. If I can get it to boot back up I'm just gonna tell my friend I cant fix it because I believe there are deeper problems at hand here. Any tips on how to fix the boot looping? Cause two successful flashes via heimdall and odin didn't do it :/
Here's a screen shot of what I have now. I went back to odin and did a full reformat and repartition witht the pit pda and phone this time without the sd card in it and I'm still getting the /data doesn't exist. Quick question: I work at a cell phone repair shop and I know some devices internal memory is actually just an sdcard covered by a shield that can be replaced. If that were the case with the Infuse could I possibly put another sd card in that slot and fully reformat it on the new card? Seeing as this could be a corrupt internal sd card just currious.
jtl_777 said:
Here's a screen shot of what I have now. I went back to odin and did a full reformat and repartition witht the pit pda and phone this time without the sd card in it and I'm still getting the /data doesn't exist. Quick question: I work at a cell phone repair shop and I know some devices internal memory is actually just an sdcard covered by a shield that can be replaced. If that were the case with the Infuse could I possibly put another sd card in that slot and fully reformat it on the new card? Seeing as this could be a corrupt internal sd card just currious.
Click to expand...
Click to collapse
you're still on secure stock kernel..that is what you're seeing.
in the heimdall uclb3 thread, after you flash the uclb3 stock, put phone back in download mode.
flash the kernel in the second or the third post to get your cwm recovery
qkster said:
you're still on secure stock kernel..that is what you're seeing.
in the heimdall uclb3 thread, after you flash the uclb3 stock, put phone back in download mode.
flash the kernel in the second or the third post to get your cwm recovery
Click to expand...
Click to collapse
Even if I were to flash the stock uclb3 it will just bootloop. The phone isn't cooperating with either heimdall or odin. Well I guess I shouldn't say that b/c they both flash fine but the phone doesn't boot straight to the system, as soon as a flash is finished it reboots into recovery (3e) and installs some update package. I'm not sure what it is but it never boots straight to the system. Then after the update finishes it just bootloops :crying:
I'm losing hope. But I'll give your advice a try. Heimdall or Odin?
is there a way to format /data on the internal memory? I read your post and it says it does not wipe the data partition. I think that may solve my problem, but probably not lol
Flashing Odin or Heimdall stock with a pit file should take care of that... You could try qkster's cwm wipe or the infuse toolkit complete wipe.. That will clear /data.
The bootloops sound like non-stock file systems with a stock kernel/recovery.... Likely, since you are still seeing stock recovery.... The real mystery is why this is so after apparently successful flashes of a new kernel and rom..
What was running on the phone before all this? What exactly are you flashing now?
Sent from my SAMSUNG-SGH-I997 using xda premium
Okay I fianally got it to boot up and I am putting this thing away FOR GOOD! No root, no custom recovery just stock JB haha. Let me see if I can describe this to you guys and get your opinion it is literally the weirdest thing. I remember the Sd card messing it up the last time and i remember what I had to do to fix it and tell me if this makes sense. If I had the sd card in the phone and tried to boot up it would boot loop or if I tried to boot into recovery I would get all those red errors. So what I did to remedy this was to somehow put the sd card in AFTER I had applied power to it with the 3 finger technique. This was done by putting the sd card in its slot but not clicking it, taking a small flat blade and putting it against it, putting the battery in the device with the blade in between the battery and the unlicked sd card, used the 3 finger method to get into recovery and just before it starts up i clicked the sd card in place with the blade..... No clue why this worked but when recovery started up I had absolutely no errors, it finally was able to find AND format /data and I did a factory data reset and wiped cache and rebooted to stock JB. Dont ask why it worked but it did? haha I remember having to do this last time I just couldn't remember the sequence. Does that make any sense to you guys? why would this happen, if you know?
so now that I finally got it booted and the market and all is working would it be possible to flash a kernel with the SGS kernel flasher that has cwm in it cause I dont wanna deal with either odin or heimdall again. would this bypass those or do I need root first?
That's a wacky fix for a wacky problem. Glad to hear you got it working.
I'll bet that you'd be OK just leaving that external card out. Reformat still recommended...
You will need root to use sgs kernel flasher. If you are running uclb3 (gb) stock you will need to flash a custom kernel via the dreaded Odin or Heimdall method. Try with the sdcard removed... Maybe you will have better luck....
Sent from my SAMSUNG-SGH-I997 using xda premium
what do you mean by reformat still recommended? I wouldn't wanna have to go through all that again by flashing someother insecure kernel or another version of android or something. Its weird though why do you think when I flash a kernel that has a different recovery on it it doesnt stick?
Backup and reformat the external sdcard since that seems to be an issue...
The rest is if you want the ability to flash custom kernels and roms. If you are good as is... Well, there you go...
Sent from my SAMSUNG-SGH-I997 using xda premium
Hi
Sent from my SGH-I997 using xda premium
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.