Issues with clockwork recovery/kernal

[Roberts.Tyler3289]

Alright.... I rooted my phone and flashed clockwork recovery. Since day one i did not have the option to choose .zip from sd card. But i never worried about it because there weren't any roms i was interested in. Now that there are roms out there i want to try, i can't flash them because they are not named "update.zip" and if i rename them "update.zip" the recovery says it can't install because the signature verification failed. this has happened with several different roms as well as a clockwork update. I tried using odin and setting my epic back to defaults, which worked, but didn't get rid of the recovery like i was hoping. I tried the oneclick exploit which did nothing for me so i extremely confused. Today i downloaded rom manager as well as the clockworkmod kernal. put the kernal on the root of the sd and as always it would not flash. so i chose to "flash clockworkmod recovery" in rom manager, chose the epic, it flashed just fine, i then chose "reboot into recovery" where the kernal should have installed automatically, and it did try but then failed and say the following: failed to verify whole-file signature, then it says below that signature verification failed installation aborted. if anybody has any ideas i would really appreciate it... i would really like to try some of these overclocked kernals that are out!!!

thanks,

4nic8

 

[ragnarokx]

Here is my response from the thread where you originally posted this question.

I have been having all kinds of problems with the clockwork recovery and mod in general. first off my recovery does not have "choose .zip from sd" so i can't flash anything through the recovery.

You were in stock recovery (blue text), which cannot flash roms/kernels. You need to be in ClockworkMod Recovery (green text).

so then when i found this thread, i downloaded the kernal ( which won't flash through the recovery) so i downloaded rom manager, chose to "flash clockwork recovery" it was successful and says i now have version 2.5.1.0 but when i choose "boot into recovery" it starts installing and then says failed to verify whole-file signature, then it says below that signature verification failed installation aborted. Any ideas? I really just want to find a recovery that will allow me to flash a rom, and so far nothing has worked. oh and by the way if i try to rename whatever rom i'm trying to flash to "update.zip" i get signature verification failed! please help!!!!!!!

You need root access to install ClockworkMod recovery. Did you root your phone before trying any of this?

 

[Roberts.Tyler3289]

yeah man... i have re-rooted after i used odin. i used the oneclick exploit which but super user on my phone, and i used titanium backup, shoot me, and busy box to test root. oh, and i used the sdx stock removal app too. so i'm confident that i have root, but you are correct i am booting into the stock recovery, but rom manager saysi have successfully downloaded clockworkmod recovery,but when i boot into recovery to flash it, it fails. and when i tried to load clockwork from my pc i get device not found.

 

[ragnarokx]

Try booting into Clockwork this way: while phone is off, hold vol down and camera button, then power on the phone. If you still boot into stock recovery, then try installing Clockwork this way (taken from XDA):

1. you need samsung galaxy s drivers
64-bit OS http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
32-bit OS http://firon.net/xda/usb_drivers_GalaxyS_x64.zip

2. push MENU, select Applications > Development, then enable USB debugging.

3. extract and run runtryfirst.bat or runtrylast.bat

4. enjoy!

 

[Roberts.Tyler3289]

i have already tried both of those ideas. when i run either bat file i get failed to read from /sdcard/zimage (bad file number) then my phones reboots and i get:

cleanup
rm failed for /sdcard/zimage, no such file or directory
done
press any key to continue

When i press any key command prompt closes. I originally thought i needed to extract the zimage file to the sd so i extracted the whole zip file to the root of the sd and still get this error. any idea what this means? oh and i verified i can connect to the device through adb devices. it shows my phone

 

[ragnarokx]

Perhaps something you already did is preventing an install. If I were you I'd try wiping completely back to stock using Odin (see the thread in this sub-forum called "[How To] Factory Restore"). Then do the one click root, confirm you have root using Wireless Tether/Titanium Backup/etc, then make sure Debugging Mode is on and try running the bat files (don't download ROM Manager before this).

 

[Andrew Ruffolo]

you need to remount the /system file... not easy to do. What I eventually got to work was install adb wireless. use command prompt to cd to the tools folder of the directory. then type in adb connect and the ip address the app gives you XXX.XXX.XXX.XXX:5555 is the format. Then type:
adb shell
su
when superuser permissions pops up, select allow
then
remount rw
then re-run the bat file for the 1-click (hahaha) clockwork

 

[Roberts.Tyler3289]

you need to remount the /system file... not easy to do. What I eventually got to work was install adb wireless. use command prompt to cd to the tools folder of the directory. then type in adb connect and the ip address the app gives you XXX.XXX.XXX.XXX:5555 is the format. Then type:
adb shell
su
when superuser permissions pops up, select allow
then
remount rw
then re-run the bat file for the 1-click (hahaha) clockwork

alright so i remounted/system, it said remounting then command prompt went to the next line with just #, so i ran both bat files and they both say device not found, i tried plugging it in, and they still say device not found, am i doing something wrong?

edit: i tried with the phone plugged in again and it still gives error failed to read from /sdcard/zimg?

 

[Andrew Ruffolo]

alright so i remounted/system, it said remounting then command prompt went to the next line with just #, so i ran both bat files and they both say device not found, i tried plugging it in, and they still say device not found, am i doing something wrong?

edit: i tried with the phone plugged in again and it still gives error failed to read from /sdcard/zimg?

It took me several tries, and I'm not quite sure what made it work. Sorry. I felt like the guy trying to crack the safe and just when I was about to give up, I slammed my head on the safe and it opens up.

 

[Roberts.Tyler3289]

It took me several tries, and I'm not quite sure what made it work. Sorry. I felt like the guy trying to crack the safe and just when I was about to give up, I slammed my head on the safe and it opens up.

lololololol no worries thanks for the help! I didn't have the newest ota before i rooted anyway, so i went back to stock and i'm wiating for the ota, i also backed up and formatted my sd card. Once i get the ota i will try this over again and see where i get!

 

[Roberts.Tyler3289]

update: went back to stock, did ota. backed up and formatted sd card, and i am still getting the failed /sdcard/zimg error. should i be extracting the one click clockwork mod to the sd card? can i push the file manually through adb?

 

[Andrew Ruffolo]

the 1-click method is something you run on the computer (pc).

 

[Roberts.Tyler3289]

thank you for all the help... i'm not too sure how exactly i got this working, i have tried so many different times. but i know i did mount the /system folder using root explorer, and verified i could access the sd card and /system folder by using adb to delete a "test" pic from the sd and an old apk from /system/app. then i ran the run.bat as administrator. i read a post that said when your phone reboots unplug it and pull the battery BEFORE it gets past the initial samsung screen, then boot into recovery and viola!!!!!!!!!!!!!

 

[iceman19631]

thank you for all the help... i'm not too sure how exactly i got this working, i have tried so many different times. but i know i did mount the /system folder using root explorer, and verified i could access the sd card and /system folder by using adb to delete a "test" pic from the sd and an old apk from /system/app. then i ran the run.bat as administrator. i read a post that said when your phone reboots unplug it and pull the battery BEFORE it gets past the initial samsung screen, then boot into recovery and viola!!!!!!!!!!!!!

OMG...After two weeks of trying to get this stuff achieved, you come up with the most simpliest solution. I have tried everything concerning rooting and afterwards, I could not get into Clockwork recovery. Thanks to your findings, I have now been able to get there and can now install roms. A big THANKS goes out to each and everyong one of you guys for helping to make this all possible. I'm curious as to where you read that post from, you got the address to it? I want to bookmark it as I do with all helpful addresses....Thanks again

 

[persianpimp]

One thing that i see everyone missing is that, BEFORE YOU CAN ROOT, you need ANDROID SDK. For the longest time i was wondering with the commands would not work LOL. Lots of people forget to mention that... which is really important

 

[jademan]

I have been searching for this simple but ultimately helpful tidbit for a looong time. Thank you so much for taking the time to post our success story here, 4nic8!! The battery trick allowed me to finally get into clockwork recovery instead of system default recovery!

It seems I need to do this every time though... even clicking ROM Manager's "Reboot into (ClockworkMod) Recovery" button still brings me back to system default recovery with the E:signature error... Bringing up issue 2 - I have used clockwork to disable signature verifications, but system recovery still fails at updates... I assume I should just use clockwork every time? Not a biggie... except for having to open the case for battery each time.... Did you manage to get around this? or just not have the same issues? Is there one more elusive but oh-so-important piece I'm probably missing? Or just use adb?

This site (http://forum.xda-developers.com/showthread.php?t=798067) was very helpful (going back to there for clockwork recovery issue), but the old yank-the-battery-out-during-start-up trick sure wasn't in there...

obviously ima noob... but feel I am so close!

EDIT: Success was not far behind... now running standard SydicateROM 1.0.2 with Xtreme kernel! **grins**

 

[Andrew Ruffolo]

One thing that i see everyone missing is that, BEFORE YOU CAN ROOT, you need ANDROID SDK. For the longest time i was wondering with the commands would not work LOL. Lots of people forget to mention that... which is really important

Technically, you don't. They include the adb application that is required. Doesn't hurt to have it installed. First thing I do when I get a new PC/ work from a different computer.