So i rooted my phone manually (ran rage.bin, pushed su, busybox, and Superuser) and then used odin to flash the CWM_recovery_DL09.tar. to get to CWM recovery i had to go through blue recovery every time (apply update.zip). Once i got into CWM i flashed a DL30 rom and my phone wouldnt boot. not only wouldnt it boot but blue recovery wouldnt apply the update.zip. i had to odin back to DJ01 stock.
Now i flashed the EB01 root/recovery/superclean and then flashed the red CWM-all.
I have two questions. Did my phone originally brick because i was supposed to flash a DL09 rom instead of DL30 rom? And now that i can get into red recovery directly, am i safe to flash whatever i want?
I assume that since i dont have to go through blue recovery, and i can go directly to red CWM, i should always be able to get into CWM and restore a backup if i hose my system right?
unbelievable
Did the dl30 rom have a kernel? If not you were trying to run froyo with the stock eclair kernel. Can't imagine that works to well. And yes now that cmw is properly flashed, barring a major snafu, you should always new able to enter cmw using the 3 key method.
Sent from my SCH-I500 using XDA App
So i used to have CWM 3 (orange). Everytime i wanted to get into it i had to go through the stock blue recovery and flash update.zip. I tried to flash a DL30 rom through CWM and my phone wouldnt boot. Not only would it not boot but i couldnt get past stock blue recovery, the update.zip failed. so i had to odin a stock build.
Now i have red CWM installed, and i dont have to go through blue recovery to get to it. Am i safe to flash any ROM/kernel/theme now that i can get right into red CWM?
yes.
good day.
Amazing
10 chars
'm running stock Froyo on a T-mobile Vibrant. I tried to get Rom Manager to backup the current rom. When it boots into recovery and I select reinstall packages it fails on signature. Apparently this is a 2E/3E Recovery issue.
So I went ahead and ran the 3e_recovery installer
http://forum.xda-developers.com/showthread.php?t=833423
which says it succeeded. Now when I run backup the current rom, it boots to recovery, and reinstall packages no longer complains about signature. instead it just reboots back into recovery so quickly that I can't really read the 4 lines of messages, though I can just make out a "replacing stock .. " as one of the last lines.
Reboot system still does work, so I can get back into normal operation, but I'm stuck as far as gettting a backup.
Help!
Well things have changed a bit.
I went ahead and did the KB5 upgrade, which got me back to stock recovery. So now I'm back to the case where CWM will fail on signature.
How are other Vibrant users dealing with this?
- what color is it?(lol, thats funny. I werk in parts)
- is there an update zip? what happens if you flash that?
kmandel said:
'm running stock Froyo on a T-mobile Vibrant. I tried to get Rom Manager to backup the current rom. When it boots into recovery and I select reinstall packages it fails on signature. Apparently this is a 2E/3E Recovery issue.
So I went ahead and ran the 3e_recovery installer
http://forum.xda-developers.com/showthread.php?t=833423
which says it succeeded. Now when I run backup the current rom, it boots to recovery, and reinstall packages no longer complains about signature. instead it just reboots back into recovery so quickly that I can't really read the 4 lines of messages, though I can just make out a "replacing stock .. " as one of the last lines.
Reboot system still does work, so I can get back into normal operation, but I'm stuck as far as gettting a backup.
Help!
Click to expand...
Click to collapse
i have exactly the same issue...i tried everything posted here but not working...last chance is to odin back i guess
If I were you I would do a back up then> odin back to stock then> root then> download Rom manager Then> Flash a new custom Rom. The Stock TMO one is sucky and does not run as smooth as the custom ones. Then you will an awesome phone
Hey,
I am somewhat familiar with all the things we need to do but I seem to have lost the ability to do some things last night.
I am going to ODIN back to DL09 with repartition and atlas 2.2 pit just to ensure on stock then going to update all I can through OTA
(FIXED)
After I get to this point what is the best way to get onto the New GB roms.
I was on the test 2 from JT and then went back to stock and to evil fascinate. From there I went to the recovery and installed the MIUI and then the .1 patch both from andmer. I was able to install titanium backup and recover all the apps but did not do any system data. But for some reason after playing around I can no longer install anything from the market. says I am out of room but i can verify there is over 500 MB at least on the SD and internal storage.
So I read some people talking that it should be done in yellow recovery and I am not quite seeing how to get this. I am in the orange recovery currently.
So My plan again is to just start again from stock.
I just need to know how to go from stock to the yellow CWM so I can flash the MIUI from my SD card. Is there a file I can ODIN to go straight to the Yellow CWM and then flash the other files from the yellow CWM.
EDIT:
So the reason why I wen back to stock was that my wifi was erroring out and also could not install new apps as was saying there was no room when there was. So I ODIN to the DL09 w pit file and repartition and then ODIN CWM 3. Then installed the evil fascinate rom while waiting for a response here. I got ansy and in evil fascinate through the power menu booted into orange recovery. and then reflashed the MIUI rom. Then when on the regular rom I tried to install the terminal emulator and I could so then from there I went into su > reboot recovery. Finally success into Yellow to install the patch and the new Kernal. Now installing apps works agani and Wifi is not getting errors.
I feel like such a n00b but I've literally flashed dozens of ROM's between my Captivate and my Infuse.
Thanks for Entropy, I have my modem back so I can make calls (thank you!).
Now I'm trying to get back into CWM but everytime I flash it in Rom Manager...then reboot into recovery I get this error..
E:failed to verify whole-file signature
E:signature verification failed
And that's in 3e...it won't boot into CWM.
I tried rerooting and using the SGH-I777_ClockwordMod-Reovery_5.0.2.3.tar in Odin...when I reboot in recovery...it freezes up...
Any suggestions?
Hmm that one is odd.
Until further notice - don't use ROM Manager on our device. Kernel-included CWM is the way to go. My guess is that somehow ROM manager dorked up your system partition. You may need to Odin/Heimdall back to stock, then flash codeworkx's CWM kernel, although I'm surprised you weren't able to enter CWM after flashing codeworkx's kernel...
Edit: When you say it "freezes up" - do you mean stuck at the Samsung Galaxy S II screen, or does CWM come up?
If I flash back to stock and try to get into recovery...I get stuck at the above mentioned screen.
If I Odin the CWM 5.0.2.3 package and try to get into recovery...I get into the light blue recovery screen but every option I click on just brings me to the Rom Manager Hat Icon and does nothing (even though I don't have Rom Manager installed anymore). I get stuck in that menu...pull the battery...reboot...still in light blue CWM menu but every option just brings up the Rom Manager Icon.
Only way to "fix" is to get back into download mode, odin back to stock or re-odin the CWM 5.0.2.3 tar again. But, again, if I try to get into recovery from stock...3e recovery (ie useless) if I Odin back to CWM.tar...I get stuck in Rom Manager Icon hell.
Entropy512 said:
Hmm that one is odd.
Until further notice - don't use ROM Manager on our device. Kernel-included CWM is the way to go. My guess is that somehow ROM manager dorked up your system partition. You may need to Odin/Heimdall back to stock, then flash codeworkx's CWM kernel, although I'm surprised you weren't able to enter CWM after flashing codeworkx's kernel...
Edit: When you say it "freezes up" - do you mean stuck at the Samsung Galaxy S II screen, or does CWM come up?
Click to expand...
Click to collapse
Furthermore, the first day I had the phone, I used Rom Manager to install MUIU and it worked fine! Except I had the wrong modem (which I just found out today). I thought MIUI screwed up my phone (because I was unable to make calls) so I then flashed back to stock. Luckily someone posted the stock modem up and I installed that...phone works fine.
I'd like to get MIUI on again because it was smooth as butter and all I did is download the Rom Manager version...i Know it's not supposed to work but it did.
Drew489 said:
If I flash back to stock and try to get into recovery...I get stuck at the above mentioned screen.
If I Odin the CWM 5.0.2.3 package and try to get into recovery...I get into the light blue recovery screen but every option I click on just brings me to the Rom Manager Hat Icon and does nothing (even though I don't have Rom Manager installed anymore). I get stuck in that menu...pull the battery...reboot...still in light blue CWM menu but every option just brings up the Rom Manager Icon.
Only way to "fix" is to get back into download mode, odin back to stock or re-odin the CWM 5.0.2.3 tar again. But, again, if I try to get into recovery from stock...3e recovery (ie useless) if I Odin back to CWM.tar...I get stuck in Rom Manager Icon hell.
Click to expand...
Click to collapse
Might be because the buttons aren't the same as they are on the Captivate and each time you hit power or menu (which used to be select on the Captivate) it kinda blanks out the menu until you press it again. Use the volume keys to move up and down, home button to select, and back button to go back.
whoa, I'm retarded...that worked...thanks!
Yeah I was losing my mind too when I was first trying to flash Cognition. Just started mashing buttons and got lucky
Drew489 said:
Furthermore, the first day I had the phone, I used Rom Manager to install MUIU and it worked fine! Except I had the wrong modem (which I just found out today). I thought MIUI screwed up my phone (because I was unable to make calls) so I then flashed back to stock. Luckily someone posted the stock modem up and I installed that...phone works fine.
I'd like to get MIUI on again because it was smooth as butter and all I did is download the Rom Manager version...i Know it's not supposed to work but it did.
Click to expand...
Click to collapse
I9100 roms will work to an extent, but like you noticed there roms do not support our modems or capacitive keys. Could be other things that are unsupported as well.
Drew489 said:
If I flash back to stock and try to get into recovery...I get stuck at the above mentioned screen.
If I Odin the CWM 5.0.2.3 package and try to get into recovery...I get into the light blue recovery screen but every option I click on just brings me to the Rom Manager Hat Icon and does nothing (even though I don't have Rom Manager installed anymore). I get stuck in that menu...pull the battery...reboot...still in light blue CWM menu but every option just brings up the Rom Manager Icon.
Only way to "fix" is to get back into download mode, odin back to stock or re-odin the CWM 5.0.2.3 tar again. But, again, if I try to get into recovery from stock...3e recovery (ie useless) if I Odin back to CWM.tar...I get stuck in Rom Manager Icon hell.
Click to expand...
Click to collapse
I lost 4 hours of kernel development time to this thinking I broke something - see below.
tysj said:
Might be because the buttons aren't the same as they are on the Captivate and each time you hit power or menu (which used to be select on the Captivate) it kinda blanks out the menu until you press it again. Use the volume keys to move up and down, home button to select, and back button to go back.
Click to expand...
Click to collapse
This is correct - it's why you see a bunch of posts between myself, codeworkx, and atinm in the CWM thread.
The current behavior is a bit odd, but it is usable, it's just not documented properly right now.
I have a similar problem, I've found that whenever I get that message, and none of the options on cwm work I pull the battery and turn it back on and the install resumes. Not sure why it hangs up like that but its led to a few tense moments already