Folks, I modified the Odin package that installs clockwork recovery so that it *should* work on any future versions without reflashing kernels, and without rooting your device.
This provides a nice way of rooting your device, because as long as you have the cwm update.zip on your sdcard (at the base) and this Odin flashed, you can root your device by merely installing ChainsDD's superuser package via clockwork recovery.
Odinhttp://www.mediafire.com/?qzcq15423z9i1g7
http://adrynalyne.us/files/odin/Odin3v1.3.exe
The Odin package:
http://adrynalyne.us/files/odin/CWMRecovery_DJ05_DL09.tar.md5
ChainsDD's superuser
[APP] Superuser 2.3.6.1 - Now on the Market [2010-09-05] - xda-developers
(you want the ef version)
My modified ChainsDD superuser +busybox package
http://adrynalyne.us/files/odin/su-2.3.6.1+busybox1.19.zip
update.zip to use with clockwork (goes on base of sd card)
http://dl.dropbox.com/u/2056318/update.zip
If this update.zip gives you trouble, please get it from the source. You will need to rename this file to update.zip.
http://koush.tandtgaming.com/recoveries/recovery-clockwork-fascinate.zip
Simply flash the Odin, boot to recovery, apply update.zip and load the superuser package. Done and done. No rage exploit, no fighting with one click methods.
Or, if you are feeling adventurous, you can try Clockwork Recovery RED, which works 100 times better, but has not been heavily tested with non-voodoo installs. It should be ok though.
http://adrynalyne.us/files/odin/CWMRecovery_DJ05_DL09_RED.tar.md5
This method requires ONLY this Odin method. You do not need update.zip unless using rom manager. Credit jt1134 and supercurio for Red cwm. Credit to squash/times-infinity for the idea
Note to Stock UsersI have found that the stock Samsung kernel is very sneaky and replaces clockwork on the next reboot...it seems to be most common with those who have updated using Verizon's OTA updates. Odin users usually do not see the issue and hence, was tough to track down.
So to alleviate this, please add an extra option to your list of things to do. On FIRST boot into clockwork recovery, please flash your appropriate kernel of choice. For simplicity, I have added a rather plain kernel (non-voodoo) for those who may want to flash their choice of kernel later. This must be done for those who have this problem, no matter if clockwork is red or green.
Kernel download
http://www.mediafire.com/?qzcq15423z9i1g7
So does this effect the red/voodoo CWM that most of us use?
If you are already on red cwm/voodoo, its a non issue.
This only flashes green cwm right now, for the purposes of easy rooting, kernel installing, etc.
like a charm
thanks
Is it impossible to flash D101 without odin? Dumb question i know. Lol
Z an B son!
zachsx said:
Is it impossible to flash D101 without odin? Dumb question i know. Lol
Z an B son!
Click to expand...
Click to collapse
you can install any dl01 rom from cw recovery but you need a the 01 modem to go with it for sms and haptic feedback to work properly.
That modem has to be flashed in odin, if that's what your asking
obededom said:
you can install any dl01 rom from cw recovery but you need a the 01 modem to go with it for sms and haptic feedback to work properly.
That modem has to be flashed in odin, if that's what your asking
Click to expand...
Click to collapse
That's what i thought i was double checking. Thnks for the quick response
Z an B son!
Is anything removed from this package? Like debloated or anything?
Sent from my SCH-I500 using Tapatalk
mamoru16 said:
Is anything removed from this package? Like debloated or anything?
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
it's not a rom, it's some tools to regain root after losing it via OTA update
this is good, much appreciated
-banblah
Hmm the update.zip did not work. I Odined the full DL09 package, and then after a reboot or two, Odined the CWM file. But once I got into normal recovery and tried to apply the update.zip I get this:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?
Probably the third try doing this, but still no luck =( I'll try the older one click and if that doesn't work I'll have to adb it.
I got the same error and something about IP_PREVIOUS_*_*. *'s denote what I can't remember.
Sent from my SCH-I500 using Tapatalk
I need a full error.
I will re-upload the update.zip.
Actually, I downloaded the update.zip and it works fine.
[[email protected] Desktop]$ adb shell
bash-4.1# rm /sdcard/update.zip
bash-4.1# cd /sdcard
bash-4.1# wget http://dl.dropbox.com/u/2056318/update.zip
Connecting to dl.dropbox.com (50.16.211.15:80)
update.zip 100% |*******************************| 1345k 00:00:00 ETA
Failure of update.zip
I downloaded and it failed also.
Error is: signature verification failure.
Thanks for any help.
Norm883
I had to do it twice. the 1st time it didn't work, and usb stopped working. so i odin'd DL09 again and re- did the process, and re-downloaded the files. It works. Step 1 oden fresh DL09. Step 2 drag and drop update.zip and the su- bla bla bla..zip files to the root of the sd card. Step 3, odin CWM bla bla bla.md5. step 4, boot into recovery. Step 5 update.zip. Step 6, select install .zip, go to SU bla bla bla .zip file and yes to install. reboot and superuser, yay.
SuperOneClick v1.5.5 - Nice work for DL09
Try this one.
SuperOneClick v1.5.5 - Nice worked in DL09 for ROOTED
http://forum.xda-developers.com/showthread.php?t=803682
apnews said:
Try this one.
SuperOneClick v1.5.5 - Nice worked in DL09 for ROOTED
Click to expand...
Click to collapse
No, DON'T.
Any flasher is going to need to Odin in CWM anyway, and screwing around with One Click apps isn't going to advance the ball at all. The method in the first post here not only unlocks recovery and gives root, it teaches the novice flasher how installations will work in the future (get into Clockwork and then apply a zip that's not called update.zip).
Odin Files Link broken
I can not get the new odin files via the link provided
Which? There are several links in the first post.
Related
Hey guys!
The ClockworkMod recovery has been released. http://forum.xda-developers.com/showthread.php?t=787168 Check out this post and do what it says. Once it is finished go download ROM Manager from the Market and update your recovery! I will have a rom out ASAP after I get it tested :] If you wanna test email me at [email protected]
Which of those 3 zip files needs to be flashed ?
So does that mean that samsung reviewed and fixed the code they released or was there something that the devs were missing when trying to build the kernel?
CheetoDroid said:
Which of those 3 zip files needs to be flashed ?
Click to expand...
Click to collapse
the captivate one.
SeaWo|f said:
So does that mean that samsung reviewed and fixed the code they released or was there something that the devs were missing when trying to build the kernel?
Click to expand...
Click to collapse
this is for the recovery... i dont think the kernel or the source is building yet.
SeaWo|f said:
So does that mean that samsung reviewed and fixed the code they released or was there something that the devs were missing when trying to build the kernel?
Click to expand...
Click to collapse
This is not built from source, this is a duct taped together version of recovery, it should work for now though.
I've got CWM running on my Fascinate! =)
Too bad it doesn't mount the SDcard and it places nandroid backups in /data, but it's a start. =)
Do we flash it in ODIN using the PDA box ?
geeknik said:
I've got CWM running on my Fascinate! =) Ran Nandroid as well and it backed up to /sdcard/clockworkmod/backup. =) Can't wait to get some ROM love now.
Click to expand...
Click to collapse
thanks to geeknik he was the lab rat.
Fascinate is in rom manager options. Sweet
Sent from my SCH-I500 using Tapatalk
good stuff!
Very exciting news.. Looking forward to coming home and giving it a try.. at least making a full nandroid backup.. I've had to rebuild this phone from scratch way too many times now.
I'm not really clear on the instructions.
I have downloaded the captivate_recovery.zip but I'm not sure how to proceed from that point. Am I using Odin?
This isn't working for me, I flashed the tar file in ODIN and then installed clockwork from rom manager. When I click reboot into recovery it loads up a stock recovery and gives some errors under it.
Update with more info:
When I reboot into recovery from RomManager I get
e: failed to verify whole-file signature
e: signature verification failed
Installation aborted
I'm thinking this means the ODIN flash didn't work correctly
Maybe someone could post clear step-by-step instructions?
what tar file cheeto. all i'm seeing is three zip files, that when unzipped have no extension. a little help?
CheetoDroid said:
This isn't working for me, I flashed the tar file in ODIN and then installed clockwork from rom manager. When I click reboot into recovery it loads up a stock recovery and gives some errors under it.
Update with more info:
When I reboot into recovery from RomManager I get
e: failed to verify whole-file signature
e: signature verification failed
Installation aborted
I'm thinking this means the ODIN flash didn't work correctly
Click to expand...
Click to collapse
You flashed a new recovery kernel with the clockworkmod recovery binary. I'm confused why you would try and install again, on top of it, from ROM manager? (Don't take that the wrong way.. that's not an "OMG Why would you do that?!" It's an "I'm not following your logic".. )
Re-do your initial step (flash recovery via odin) and that should be it, unless I'm missing something here.
and for those of us still out of the loop... how do you flash the recovery via odin? add a .tar to the file in the zip? rename the .zip file to .tar? help us out please.
sonofskywalker3 said:
and for those of us still out of the loop... how do you flash the recovery via odin? add a .tar to the file in the zip? rename the .zip file to .tar? help us out please.
Click to expand...
Click to collapse
Hang in there, I know it's frustrating. Let us get some more feedback on this and how it's working before the steps are broken down so that anyone can follow along. The last thing we all want to see is post after post from people who did this not knowing how to fix their phones if something goes wrong.
If you're confident you know what's going on, the posts are there, in the Fascinate forum, on how to use odin. Feel free to check them out.
BE CAREFUL EVERYONE. there are quite a few issues with cwm still, It doesn't detect the sdcard, so you wont be able to flash a backup. and you can only get into recovery by rebooting into recovery through rom manager.
My Vibrant used to be rooted. I just updated Tmobile Froyo KA6. I try rooting using Z4root, but it won't do anything. I manually try and getting:
"E: signature verification failed
Installation aborted"
I read this could be the problem on the forum, but I don't know how to fix it:
"Android system recovery <3e>
Samsung Recovery Utils
-for BML-"
ps.don't know if this information of the phone help:
Froyo 2.2
T959UVKA6
Kernel 2.6.32.9
Can't anyone help this rockie?
Thanks
Try One Click Root.
I tired both...neither works. I read something that Froyo's (legitimately.Froyo) folder structure or.something.of that nature has.changed. Not sure though...I'm a bit of a nub in the realm of.development. Can anyone confirm rooting by any.of.the normal conventional methods (z4, 1click, etc.
Sent from my SGH-T959 using XDA App
Super one click worked for me
I have gotten the same error with One Click
lbridges said:
Super one click worked for me
Click to expand...
Click to collapse
Thank you Ibridges! the superoneclick from TheUnlockr work for me.
Super On Click Root worked for me but I get the same message while trying to install a new ROM.
I got the "E:signature verification failed" message on my Motorola Defy (Android 2.1 Eclair with Motoblur) while rooting in recovery mode. It was using the SuperOneClick method connecting the phone to a Mac. Actually, that version of the software says once installed in your Mac that is for Samsung Galaxy S, but root all models. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=739304
I have to say that I tried z4root and was useless; so now I see little alternatives...
USB debugging, SD mount and everything is in the way it should... Anyone can help me please?
Edit: I saw in the mentioned thread that many are having similar problems. Someone said that manually copying the update.zip file in the SD card and then doing the whole thing in recovery mode worked. I wasn't that lucky. Now, at the bottom of the phone screen I get the following lines in yellow:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
So I am stuck here.
Same thing happened to me when I did the kies update for 2.2 ka6 and hated froyo stock. I tried to root and couldn't. Long story short, I Odin'ed back to 2.1 and used one click root which worked perfectly. Running Bionix V now no problems .
I would try to use odin to go back to 2.1 and use super one click root from the unlockr.
Sent from my SGH-T959 using XDA App
I am now having this issue as well. Do I really need to odin it back to 2.1?
I am trying to put Simply Galaxy/Sweet Honey 2.7.1 on my STOCK 2.2 .
Answer is appreciated .
Noob
Yes, you do have to go back to 2.1 before being able to flash any custom rom.
Guys,
I have resolved this many many times... Just follow these steps -
Pre-requisite - Enable USB debugging on your phone and connect it to your pc.
1. Root your phone using SuperOneClickv1.6.5-ShortFuse. You can get it at 'http://forum.xda-developers.com/showthread.php?t=803682'
2. Go to this thread and download the two files 'http://forum.xda-developers.com/showthread.php?t=833423' - '3e_recovery_installer.zip' and 'update.zip (1.34 mb)'
2. Run install.bat from 3e_recovery_installer folder to rectify the the recovery signature checking.
3. Keep the just downloaded update.zip (1.34 mb) in your internal sdcard and boot under recovery. Select reinstall package option. Update.zip will get installed and phone will reboot.
Its not done yet.
4. Now get the actual clockwork mod recovery update.zip (1.72 mb). You can get this using ROM manager. Now put this update.zip (1.72 mb) in your internal sdcard and boot under recovery. Select reinstall package option. Update.zip will get installed and phone will reboot and will be back in samsung recovery mode. Select reinstall package again and bang... You should now be at cwm recovery
Did this help?
axesd said:
I am now having this issue as well. Do I really need to odin it back to 2.1?
I am trying to put Simply Galaxy/Sweet Honey 2.7.1 on my STOCK 2.2 .
Answer is appreciated .
Noob
Click to expand...
Click to collapse
Before installing a custom ROM, it is not mandatory to go back to stock 2.1. Generally it is just recommended when you are going from one custom ROM to another custom ROM and by going back to stock you avoid taking ghosts (issues) of one custom ROM to another.
So if you follow my instructions to resolve your cwm recovery for Stock 2.2, you should be good to go to Simply Galaxy/Sweet Honey 2.7.1 without going back to Stock 2.1.
Hope this helps...
Its a normal occurrence after upgrading through Kies to 2.2. The 3e recovery always used to work for me regarding the signature verification error. Accept the last time I tried it about a week ago it coukdnt get it to work for whatever reason.
So what I did was use odin & revert back to 2.1. Then root using one click root. Then just flash a 2.2 rom in clock work, Bionix for example. Then you will on 2.2. You will have no problem with the signature verification this way. Gluk
Sent from my SGH-T959 using XDA Premium App
kisfit2000 said:
Guys,
I have resolved this many many times... Just follow these steps -
Pre-requisite - Enable USB debugging on your phone and connect it to your pc.
1. Root your phone using SuperOneClickv1.6.5-ShortFuse. You can get it at 'http://forum.xda-developers.com/showthread.php?t=803682'
2. Go to this thread and download the two files 'http://forum.xda-developers.com/showthread.php?t=833423' - '3e_recovery_installer.zip' and 'update.zip (1.34 mb)'
2. Run install.bat from 3e_recovery_installer folder to rectify the the recovery signature checking.
3. Keep the just downloaded update.zip (1.34 mb) in your internal sdcard and boot under recovery. Select reinstall package option. Update.zip will get installed and phone will reboot.
Its not done yet.
4. Now get the actual clockwork mod recovery update.zip (1.72 mb). You can get this using ROM manager. Now put this update.zip (1.72 mb) in your internal sdcard and boot under recovery. Select reinstall package option. Update.zip will get installed and phone will reboot and will be back in samsung recovery mode. Select reinstall package again and bang... You should now be at cwm recovery
Did this help?
Click to expand...
Click to collapse
This is exactly what I did to get my Clockwork Recovery to work.
Jo3f1sh said:
This is exactly what I did to get my Clockwork Recovery to work.
Click to expand...
Click to collapse
Glad I could help
dissable signature verification
DISABLE E: SIGNATURE VERIFICATION ON SAMSUNG VIBRANT
Here goes steps to install this modified 3e Recovery:
PREREQUISITE
Working USB connection between your Vibrant and computer. You may setup ADB or install Kies on your computer.
INSTRUCTIONS
Disclaimer: Proceed at your own risk. We are not responsible if your device gets bricked or damaged during the process.
1. Download Modified Recovery 3e for Vibrant on to your computer and extract it’s content.
2. Put your Samsung Vibrant into “USB Debugging Mode”. To do it, go to “Applications”—> “Settings” –> “Applications” –> “Development” –> and check the box “USB debugging”.
3. Connect the Vibrant to computer via USB cable.
4. Run the “install.bat” file located in the extracted content.
5. Wait till the process completes.
That’s it. Your Vibrant should now have modified 3e Recovery that disables signature verification. You may now root the Samsung Vibrant or install ClockworkMod Recovery on it.
now try rooting with one click or manual
What I did is, I odin back to 2.1
Then I used an app called Z4root to root the phone. Once there download CWM from tom manager and enjoy
Sent from my SGH-T959 using XDA Premium App
After hours of failing to root the device, I found this thread and thanks to Kisfit2000 I finally got this damn Vibrant root access. Thank you!
I am not able to flash Villain ROM 2.3 or anything else. The reason is that when it reboots into recovery mode, it starts with: -
_ Installing package...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted
Any idea what's going on, I just recovered my SGS2 from almost being a brick!
Cheers!
It sounds like a corrupted file. Your download might not have completed or you are having hardware issues such as faulty ram.
Before updating a ROM, try to checking the MD5 checksum to see if they are correct if the chef provides it.
Go into your recovery and press the Choose zip to flash option, there you can select 'turn off signature verification, now you can happily flash.
Sorted!
Thanks God I got it sorted...thanks for the help of some guys in VillainROM thread.
Actually, what happened was that after flashing Chainfire's kernel, to get rid of the Yellow triangle, I was supposed to flash the Samsung stock kernel. That's what I did. BUT, after that you had to further extract the same CHAINFIRE's kernel, NOT the stock kernel to its zImage and had to put it on the root of the internal sd_card.
But, unfortunately, I being, careless extracted Samsung's stock kernel to its zImage and copied that to the sd_card. Now after flashing Samsung's stock kernel to remove the yellow triangle, it's important to flash the ChainFire's kernel's zImage so that it could again ROOT, install busy box and add CWM on the phone.
So, guys if you still having the same problem, remove the zImage you already have on your sd_card and replace it with the 1 from ChainFire's kernel and it will sort your problem and you will be able to see CWM again with FULL options.
Chillaxxxx!
hey i have copied the zimage to my sd card, but in android 3e recovery i cannot flash it .. i only see apply update zip option. but i cant select the zImage file please!!
In CWM, Flash kernel and select the zImage.zip, phone will reboot, done.
Sent from GT-I9100
The thing is how do I get cwm in the first place?? Total confusion
ashvincj said:
The thing is how do I get cwm in the first place?? Total confusion
Click to expand...
Click to collapse
If you are rooted then CWM is already installed in your device.
okkkkkk tankss
I rooted using insecure kernel but I dont see cwm app in my phone!!
ashvincj said:
I rooted using insecure kernel but I dont see cwm app in my phone!!
Click to expand...
Click to collapse
Can't say about an unsecured kernel but with CF root it is there.
Sent from GT-I9100
I used S2 Root, and insecure kernal.. doesnt not include CWM, so install RomManager, isntalled CWM but when reboot in boots to android recovery, and i get the verificaiton error, so it wont even load cmw so I cant chose the optin to disable the verification check!!
e: failed to verify whole-file signature
DocSoton said:
I used S2 Root, and insecure kernal.. doesnt not include CWM, so install RomManager, isntalled CWM but when reboot in boots to android recovery, and i get the verificaiton error, so it wont even load cmw so I cant chose the optin to disable the verification check!!
Click to expand...
Click to collapse
I have the same problem, does anyone has a solution for that. All I want to do is backup the ROM via ROM manager and I couldn't bypass the signature verification. I am also rooted via superoneclick and odin 1.85.
waiting for a response.
Thanks in advance.
antzlisoul said:
I have the same problem, does anyone has a solution for that. All I want to do is backup the ROM via ROM manager and I couldn't bypass the signature verification. I am also rooted via superoneclick and odin 1.85.
waiting for a response.
Thanks in advance.
Click to expand...
Click to collapse
Backup works via CWM and root .
Rom manager not working mostly on SGS2 .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Can anyone give me a link from where I can download the latest version of CWM which can be used for SGS II? Is CWM Manager v3.0.0.5 the latest version?
I have the latest version of ROM Manager Premium, can that help?
EDIT :
I figured I could download the latest version of CWM using my Rom Manager Premium. But I'm still stuck! I figured that I had to "Flash update" using my existing CWM Manager to flash the file update.zip. Ok, done that. But after rebooting when I again open the CWM app it is still showing as version 2.0!!!! What exactly do I have to do with the update.zip file which is there on my sdcard to make me show the CWM Manager v4..0.1.5??? If only Chainfire had bundled the latest version of CWM with his CF Root kernels rather than the ancient version he has! How unthoughtful on his part!
I have been trying to get answers since yesterday and no knowledgeable developer/senior has come forward to give any proper answer. Do all of them go on a holiday on weekends? I am having to figure out everything myself by hit and trial method, using my own common sense and some well intentioned help from junior members! If this is the way this forum is going......then I'm sorry to say that this forum is going down the drain!!
ClockworkMod recovery or the app?
If you want a kernel with CWM (as in samsung land the recovery and the kernel and linked togethet) and everything else stock try cf root, most kernels come with CWM, but not all will work with rom manager.
Sent from my GT-I9100 using XDA Premium App
I already have a CF rooted kernel which came bundled with a CWM Manager v2.0. But that version seems to be a very old one. It is of no use to me in flashing modded files. Now how do I update the CWM installed in my SGS II with the latest version of CWM? I wonder why Chainfire is not putting the latest version of CWM in his root kernels.....have asked him this question on his CF Root thread also. Meanwhile, can anyone here tell me how to upgrade my current CWM Manager v2.0 to the latest version? Surely, a stand alone file of CWM Manager must also be in existence for installation into our phones? Or do we necessarily have to get it bundled in the CF Root kernels only? I am on CF Root KF3
Oh ok, never mind! I found the file with help from another member, Arhtard, on another thread. And I just figured, I can simply upgrade it by using the Rom Manager that I already have.
TheMegastar said:
I already have a CF rooted kernel which came bundled with a CWM Manager v2.0. But that version seems to be a very old one. It is of no use to me in flashing modded files. Now how do I update the CWM installed in my SGS II with the latest version of CWM? I wonder why Chainfire is not putting the latest version of CWM in his root kernels.....have asked him this question on his CF Root thread also. Meanwhile, can anyone here tell me how to upgrade my current CWM Manager v2.0 to the latest version? Surely, a stand alone file of CWM Manager must also be in existence for installation into our phones? Or do we necessarily have to get it bundled in the CF Root kernels only? I am on CF Root KF3
Click to expand...
Click to collapse
CWM manager is an app like rom manager.
Chainfire includes an upto date version of ClockworkMod recovery in the newer versions of cf root.
Using rom manager to just update CWM without updating the kernel won't stick, and the version will go back down on reboot.
Sent from my GT-I9100 using XDA Premium App
veyka said:
CWM manager is an app like rom manager.
Chainfire includes an upto date version of ClockworkMod recovery in the newer versions of cf root.
Using rom manager to just update CWM without updating the kernel won't stick, and the version will go back down on reboot.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
1. KF3 is hardly one month old! And Chainfire's bundling of version 2.0 with that is just not right. He should have bundled the v4.0XX with it. Now because of that ancient version installed on my phone, I can't install any mods that I make in the UOT Kitchen.
2. I have the latest version of ROM Manager Premium. I used it to download the latest version of CWM v4.0.1.5. I have tried to update my existing CWM v2.0 by flashing the update.zip file......but after reboot I again see the version as 2.0 only! So how do I upgrade my CWM to 4.0.1.5??? And you seem to be right in saying, "Using rom manager to just update CWM without updating the kernel won't stick, and the version will go back down on reboot. "...... so does this mean I cannot get the latest version of CWM installed on my phone if I want to remain with KF3 Stock Kernel? So what is the workaround to this problem?
Do I have to flash again with a later CF Root kernel like say for example, CF Root KG3 and then flash the Stock KF3 Kernel back? I want to remain on KF3 stock kernel for a while till I get the official Firmware update in India via Kies.
3. My whole problem began when I downloaded a modded file from UOT Kitchen to change my Boot Screen, Icons, Windows, Battery Icon, Fonts etc. And while rebooting in the recovery mode of my ANCIENT CWM Manager, I get an error due to "signature verification". Now the developer of UOT Kitchen tells me to "disable signature verification" to be able to flash the UOT .zip file. But he does not tell me how to "disable signature verification". He must have assumed that I have the latest CWM installed. So now in order to use the modded file I created on the UOT Kitchen, I need to have the latest version of CWM installed. But you are telling me that I cannot install the latest version of CWM while still on KF3. So I'm back to square one!
4. And has anyone using the SGS II successfully installed the modded boot animations, fonts, icons etc. from files cooked in the UOT Kitchen??? If after wasting so much time & effort in trying to install the latest CWM Manager I find that the SGS II boot animation, fonts, icons cannot be modded, then I'm going to get really mad!
TheMegastar said:
3. My whole problem began when I downloaded a modded file from UOT Kitchen to change my Boot Screen, Icons, Windows, Battery Icon, Fonts etc. And while rebooting in the recovery mode of my ANCIENT CWM Manager, I get an error due to "signature verification". Now the developer of UOT Kitchen tells me to "disable signature verification" to be able to flash the UOT .zip file. But he does not tell me how to "disable signature verification". He must have assumed that I have the latest CWM installed. So now in order to use the modded file I created on the UOT Kitchen, I need to have the latest version of CWM installed. But you are telling me that I cannot install the latest version of CWM while still on KF3. So I'm back to square one!
Click to expand...
Click to collapse
On my phone I have CWM 4.0.0.2 when in the actual recovery mode but the apk version is 2.0
According to the cf-root thread kf3 had cwm4 so have you tried rebooting into recovery then IN IT choose to install the zip and then you should see a option to toggle the signature verification that isn't in the app.
Even after having flashed the update.zip file (v4.0.1.5 downloaded via Rom Manager) through the CWM app, I get only the following options when I go in recovery mode:
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
I choose "apply update from sdcard", then I get to choose the file to install from sdcard. I choose the UOT File, and I get these two lines of errors in RED color
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted
Same errors show up if I choose the update.zip file instead of the UOT .zip file.
"According to the cf-root thread kf3 had cwm4 so have you tried rebooting into recovery then IN IT choose to install the zip and then you should see a option to toggle the signature verification that isn't in the app.".............
That is the reason I'm upset with Chainfire....he has written on his thread that it has CWM v4 but you find out later that it's only v2.0. And YES, I tried rebooting into recovery from the option given inside the CWM manager app only. And I DO NOT see any option to toggle the signature verification when in recovery mode, simply because the ANCIENT version of CWM does not have this option!
And as per Veyka, it is not possible to upgrade the CWM manager without upgrading the Kernel also. And he seems to be right. I have the update.zip file on my sdcard but I am still unable to effectively install it so that the upgraded CWM Manager will show as v4.0.1.5. So as per him, if I want the new CWM then I will be forced to flash a newer stock Rom. This is coercion! I do not want to flash any unoffical Roms at this point of time, I want to stay with KF3 till an official firmware update comes from Kies.
Does someone know what to do with my CWM update.zip file so that it gets installed and the CWM Manager stops showing as v2.0?? I guess no one knows. The only way out is if Chainfire makes amends and recreates a CF Root Kernel for KF3 with the latest version of 4.0.1.5
And one more thing I'd like to know, will Kies update firmware after we install the modded UOT zip file?
try "install zip from sdcard" not apply update
shadowofdarkness said:
try "install zip from sdcard" not apply update
Click to expand...
Click to collapse
Where do I get this option "install zip from sdcard"??? I DON'T HAVE THIS OPTION ANYWHERE! There are only TWO options in the CWM Manager that I have, "flash an update.zip" and "install an APK"
That's what the whole problem is : I have an ANCIENT CWM Manager app (thanks to Chainfire) and I CANNOT UPGRADE TO THE LATEST VERSION OF CWM unless I flash a later kernel.
Don't use the manager just reboot into recovery
shadowofdarkness said:
Don't use the manager just reboot into recovery
Click to expand...
Click to collapse
How to "just reboot into recovery"???
All done!
Ok....finally figured it all out on my own, without any/much help coming from the veterans on this board. Managed to install the CWM latest version via Odin. And got my UOT Kitchen mods to work also (well most of them worked like fonts, notification screen, windows animation, icons.....but boot animation did not work. No worries, am happy with the changes I made in the appearance of my phone.....will try some more later. Cheers!
TheMegastar said:
I have been trying to get answers since yesterday and no knowledgeable developer/senior has come forward to give any proper answer. Do all of them go on a holiday on weekends? I am having to figure out everything myself by hit and trial method, using my own common sense and some well intentioned help from junior members! If this is the way this forum is going......then I'm sorry to say that this forum is going down the drain!!
Click to expand...
Click to collapse
Oddly enough, developers have families/outside interests aswell, which means they aren't sat staring at a pc screen just waiting to help you with your problem. That with a bit of reading you could easily solve.
Sent from my GT-I9100 using XDA Premium App
rom manager isn't compatible with cfroot. it's stated in the cfroot thread. also, stop blaming chainfire. afaik, the latest version of the CWM manager (THE APP) is v2.0, that's what you keep seeing. the version of the CWM (THE RECOVERY) he bundles with his kernels is, iirc, v4.0.0.2. all you need to do is read more thoroughly.
fyre31 said:
rom manager isn't compatible with cfroot. it's stated in the cfroot thread. also, stop blaming chainfire. afaik, the latest version of the CWM manager (THE APP) is v2.0, that's what you keep seeing. the version of the CWM (THE RECOVERY) he bundles with his kernels is, iirc, v4.0.0.2. all you need to do is read more thoroughly.
Click to expand...
Click to collapse
Untrue. He did not bundle v4.0.0.2 with KF3. If he had, then I wouldn't have faced so much trouble. He had bundled some ancient version which showed only 4 options, as compared to the current version which has more than double the options. All I needed to do was to disable one option of CWM Recovery, but was unable to do so because that option was NOT THERE in the version CF had bundled with KF3. As a result, I kept wondering what other people were talking about....as I didn't see those options in the version I had.
Having said that, I do appreciate all the good work CF does for getting us new root kernels everytime and have also pressed the THANK YOU button several times on his profile.
@stoney73 : I do understand and appreciate that people have a life other than sitting in front of their comps, but this is a very very large community of people living in different time zones, and at any given time there are like a 100 people logged into the site. And it was probably sheer bad luck that no one knowing about my problem came forward to help for nearly two full days.
Cheers!
Would you mind sharing, TheMegastar how you flashed the latest CWM via Odin? Perhaps you could provide a link, that would help others who would come and read this thread.
Megastar.please share I have the same issue with kf4
Sent from my GT-I9100T using Tapatalk
tonycfc said:
Would you mind sharing, TheMegastar how you flashed the latest CWM via Odin? Perhaps you could provide a link, that would help others who would come and read this thread.
Click to expand...
Click to collapse
You need to have the CWM file in .tar format to be flashed via Odin. I don't have the link, but I'm sure you will find it somewhere in this forum itself. It should be version 4+ to work. Just do a search for this version and then flash it just like flashing any root kernel, putting it in the PDA space.
xd4d3v said:
Megastar.please share I have the same issue with kf4
Sent from my GT-I9100T using Tapatalk
Click to expand...
Click to collapse
Hi, xd4d3v......I hope my reply to Tonycfc also addresses your issue. If your issue is different then please be specific, so I can give a specific reply.
I read a blog post sometime a while back about booting into standard recovery and flashing a .zip package that installs SU and...something else but otherwise didn't change anything besides giving you root access. Does anyone know how this would be possible and if so how to do it? I just want to get rid of bloatware but nothing else. Any suggestions or links for further reading would be appreciated. Thanks.
PS. I've got a recovery-clockwork.img file and a CWMSuperSu_BusyBox.zip file on my external SD but am a little confused as to how to use them. I can get into the stock recovery and have the ability to flash .zip files but I'm not sure what order to do so in or what the .img is for.
If I flash the superSu.zip file will that alone give me root access enough to get rid of bloatware and dig around in my system files with Root Explorer?
My reply won't be too helpful (no links or suggested readings), but I've often completed a basic root on my devices without using custom ROMs. The first 6 months of having my original galaxy s (captivate) I just rooted and kept stock. It was fun to have some advanced control and do basic mods.
The root is incredibly easy, I'm sure there's a great guide in the Note forums. I've got an s3 and it was a snap.
Good luck!
Sent from my SGH-I747 using xda app-developers app
nogloww said:
I read a blog post sometime a while back about booting into standard recovery and flashing a .zip package that installs SU and...something else but otherwise didn't change anything besides giving you root access. Does anyone know how this would be possible and if so how to do it? I just want to get rid of bloatware but nothing else. Any suggestions or links for further reading would be appreciated. Thanks.
PS. I've got a recovery-clockwork.img file and a CWMSuperSu_BusyBox.zip file on my external SD but am a little confused as to how to use them. I can get into the stock recovery and have the ability to flash .zip files but I'm not sure what order to do so in or what the .img is for.
If I flash the superSu.zip file will that alone give me root access enough to get rid of bloatware and dig around in my system files with Root Explorer?
Click to expand...
Click to collapse
UPDATE: I found the thread I was referring to: http://forum.xda-developers.com/showthread.php?p=28178105
I just can't seem to find .zip files of the recovery and su installer that work. I get an error about an unsigned package and failed to recognize package every time I try and install the CWM Recovery .zip file.
If you know another way of accomplishing the same thing, again, any help would be appreciated.
Go Here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look under the big green arrow in the OP:
Get drivers
Flash recovery
Root
Remove recovery
rangercaptain said:
Go Here:
http://forum.xda-developers.com/showthread.php?p=28040353
Look under the big green arrow in the OP:
Get drivers
Flash recovery
Root
Remove recovery
Click to expand...
Click to collapse
I used the files from the link you provided and I am still getting an error when installing the CWM.zip file "E:failed to verify whole-file signature" and "E:signature verification failed" Do you know what could be causing this?
nogloww said:
I used the files from the link you provided and I am still getting an error when installing the CWM.zip file "E:failed to verify whole-file signature" and "E:signature verification failed" Do you know what could be causing this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1581185
you downloaded this file from this thread see above and you flashed it like a ROM but no wipes, and you still get this errors?
are the files on your inter sd, not exter sd (memory card) ?
They were on my SD card. No matter now. I finally got my hands on a windows computer and used the Odin way. Thanks for your help though.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
but to answer your question, zips cannot be flashed from stock recovery without being properly signed....And Samsung are the only ones with the signing tool.
so if you try and flash a zip from 3e recovery, you will get that verification error.
And Joe, he was trying to flash cwm with a zip, and then the su zip. And was failing to get cwm.
studacris said:
but to answer your question, zips cannot be flashed from stock recovery without being properly signed....And Samsung are the only ones with the signing tool.
so if you try and flash a zip from 3e recovery, you will get that verification error.
And Joe, he was trying to flash cwm with a zip, and then the su zip. And was failing to get cwm.
Click to expand...
Click to collapse
thx i was trying to fig out what he was saying...as usual i got lost, thx stud...let's see what the op fig outs
Studa if you would, pronounced stooooda
Although i am pretty studly, don't call me stud
http://forum.xda-developers.com/showthread.php?t=1763896
Sent from my SAMSUNG-SGH-I717 using xda premium