Related
I am already rooted and i am running macnut12
I simply can not get in to recovery..
Even the basic recovery, you know how sometimes you would reboot in to recovery and the reboot script would not run the update.zip.. and you would be in the real recovery with the option to "install package". Well... it does not even get there.
i just get stuck on the vibrant screen, i have re downloaded clockwork, all kinds of stuff..
I just wanted to get in to recovery to wipe my battery stats yet for some reason it just don't work
I can at least use adb on the vibrant screen and get back in to the OS that way.
Any ideas?
I am at a loss..
I assume you flashed the recovery from rom manager?
Try Quick Boot, app
i did
i even tried to flash an older version from within clockwork
Good news is i can continually get back in to the OS via ADB, but i would like to have access to recovery with out flashing again via odin
Edit: Forget it... i just ODIN zapped it.
Thanks anyway
I'm having similar issues w/ r12 I posted on the macnut thread but nobody answers me. When I try to use recovery or clockwork recovery it says E: signature verification failed. I really would like to avoid using odin. Any ideas on how to fix
Sent from my GT-I9000 using XDA App
Your issue sounds a little different than the one i had/have (it's doing it again)
It seems that
Macnut R12 + EB-Productions Kernel #2 = no access to recovery
I did not get any error's, just a vibrant boot screen
I am trying to put Clockwork Recovery on the Vibrant and when I first boot it I need to manually select "reinstall packages". I usually have to do this two times in a row and then it boots into the cw recovery. But when I reboot into the recovery it boots back into the samsung recovery and I have to select "reinstall packages" again to get into cw. This isn't normal correct? I saw that I should only have to do this once and then it should boot into cw recovery everytime with no problems. The phone came with 2.2 stock.
In my experience with stock roms, i have to hit re-install packages twice to go to clockwork recovery.
Well what I am wondering is do you have to do that everytime you want to go into the recovery? Also could that possibly affect the phone to where I would not be able to restore it back to factory if something were to go wrong if I flashed a new ROM?
i assume you have rom manager right? You can do select reboot into recovery so that it will bring you straight to clockwork mod recovery. Also there's an app called "quick boot", that can make you go to recovery or download mode faster.
And no that won't affect anything when you want to flash another rom.
Your fine. Recovery will not effect going to back to stock because odin overrides all. Like the other guy said when your using a stock rooted rom you almost always have to hit it twice. Flash a custom rom and it will always go into recovery with out a hitch.
Sent from premium app
rom:trigger 2.9.3
kernel;overstock 1.4.3
theme:custom mash of all orange/tangerine
Ok, thank you for your help. I didn't know if it was having a problem or something.
Sorry for the bump, but I didnt want to start a new thread.
I'm having this same problem, but reinstalling the packages isnt working. I've done it 3 or 4 times
Tbry said:
Sorry for the bump, but I didnt want to start a new thread.
I'm having this same problem, but reinstalling the packages isnt working. I've done it 3 or 4 times
Click to expand...
Click to collapse
This should help you out.
Thanks for the link. I decided it is probably a better idea just to get a new kernal. My vibrant has andriod 2.1.1 right now. I read elsewhere that custom kernals come with clockwork recovery, plus that would eliminate any problems with my current kernal and the 2.2.1 ROM I am about to flash... Right?
Just need a guide for it.
Edit: I'm trying this. How long is it supposed to take?
Edit2: it failed when it trys to stop the adb server.
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
You can't get in CW recovery or stock recovery?
Sent from my ADR6400L using Tapatalk
Did you try reflashing CW through ROM Manager?
Yep. very strange. I even tried to wipe the phone with factory reset, and just get stuck on white HTC screen. I had deleted rom manager because of something else I read, and can't get it back, But I can't even get to recovery from bootloader.
You can get to recovery through the bootloader by shutting off the phone and turning it back on holding down the volume button and pressing power toggle down to the recovery option and press the power button
Sent from my ADR6400L using XDA App
Orio56 said:
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
Click to expand...
Click to collapse
Actually I spent a good few hours yesterday trying to help Orio out and we attempted a quite a few things to try and fix the recovery issue, this post should offer a bit more insight to the methods used;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Never once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!
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