Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing. I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery. I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature". Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Bklynrx7 said:
Hello everyone,
I recently picked up a couple GS2's for dirt cheap just to mess around with. I am having a very hard time getting any custom recovery installed on them and I was wondering if there is a trick to it that I am not seeing.
Click to expand...
Click to collapse
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
I've tried flashing various CWM modified kernels using odin with no luck. They flash successfully but still boot to 3e when I boot into recovery.
Click to expand...
Click to collapse
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I tried flashing a modified update.zip from the CM website and it fails with the error "failed to verify whole-file signature".
Click to expand...
Click to collapse
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Most recently I did a complete restore using odin with a rooted image, then used Rom manager to install CWM. Rom managed says it is successful, but when I reboot into recovery it launches 3e and attempts to do something that returns the same error "failed to verify whole-file signature". Any input of suggestions would be appreciated.
Click to expand...
Click to collapse
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
creepyncrawly said:
The recovery is compiled into the kernel on this phone, but it seems that you understand that already. The kernel and system must match. You probably need to be rooted. You have not given any specifics about the firmware, what is already installed, what specific item you are trying to install, etc.
This does not actually seem logical. I'm wondering if you are not mentioning something that I would need to know to determine why you are getting this result. If you install a custom kernel containing a custom recovery, you should then be able to boot into the custom recovery. If you still have 3e recovery, it indicates that you still have the stock kernel installed.
I would not expect that to be successful. Among other things, it is probably not specific for the I777.
Do not use Rom manager. It does not work with the I777, and can cause unrecoverable damage in some cases. There is a sticky post about it here in the forums.
You can find various resources in the Download Repository. See the link in my signature.
Here's what I would do:
Flash the latest stock Jellybean firmware, UCMD8, from the Repository.
Root using Framaroot with the Aragorn exploit.
Flash the AJK v4.9 NoSwap kernel using Mobile Odin Pro or Mobile Odin Lite. You have to extract the boot.img from the kernel zip and flash that, but don't let it boot into system. Instead, you can boot directly into CWM and flash the AJK v 4.9 NoSwap kernel zip, or if you prefer, you can flash some other custom firmware at this point.
Click to expand...
Click to collapse
Sorry if I want clear. The phones are currently on 2.3.6. I tried using framaroot but it was not successful. The app said it was successful, but there was no supersu after I rebooted. I successfully got the phone rooted using one of the one-click odin flashers posted on these forums that are said to return it to factory + root. I then tried to use rom manager which said it was successful, but wasn't. That makes sense now that you're telling me its not compatible. Ill try upgrading to the JB firmware first, then ill try framaroot. Thanks for the suggestion
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Bklynrx7 said:
I just wanted to update the thread and say that this worked. Thanks again. I'm having an issue getting Gapps flashed but that's another topic. My big concern was that the phones wouldn't charge without boot looping because they had the wrong battery installed. The Stock Jellybean with the kernel you suggested fixed that.
Click to expand...
Click to collapse
Maybe I could help. What error does it give when you flash gapps?
Related
Hello ... I ask you a little help on ROM Manager and Recovery.
I just root the galaxy S2 with the procedure supercurio, so my ROM is pretty much stock ... I was a XWKDD.
ROM Manager (in his opinion) regularly install ClockworkMod 4.0.0.2, but when I restart in recovery and launch the update.zip I get the following error message:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Googling a little I found how to sign files.zip, moddied 3e recovery and also to ignore the signs in zip files ... but none of these workarounds work ...
So how I can use this 3e recovery with unsigned files?
Or ... how can I replace the 3e with the 2e recovery? (There ROM with the 2e which do not differ much from the stock ROM?)
recovery 4 you are using old methods .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
JJEgan said:
recovery 4 you are using old methods .
http://forum.xda-developers.com/showthread.php?t=1103399
jje
Click to expand...
Click to collapse
I am still getting the same error I have rooted the fone with the above mentioned guide...
I am using Frankenstein_I9100XXKF2_I9100XXKF2_I9100XEUKD1
and I am want to install the CM7 or MIUI beta version but I am not able to do so...
E:failed to verify the whole file signature
E; signature verification failed
Installation aborted
...
Please help If I am missing something..
Thanks
Help needed aswell
EDIT: I do not like the CWM4 as the recovery deletes it's self after about a day for some reason, then i have to reflash.
I am using the Stock XWKF4 rom (rooted) with superuser and busybox and i also can't use ROM to install clockwork mod recovery.
I get the same error as the guy above me.....Help
Please, Thanks,
Andrew.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Having this problem too.
In ROM Manager, I flashed the latest CWM, then reboot into recovery.
It reboots to Android system recovery (3e).
Any idea how I can get recovery working. Do I need to flash a different kernel?
I actually JUST dealt with this issue myself. I had the same kernel as you.
You need to flash a new stock ROM in odin, I used KG6. I just used the stock kernel, not the whole package.
The stock ROMs can be found here :
http://forum.xda-developers.com/showthread.php?t=1075278
Then when this is done, you use odin to flash a CF Root for that kernal following these instructions:
http://forum.xda-developers.com/showthread.php?t=1103399
Thanks.
Got this working yesterday by flashing this kernel:
http://forum.xda-developers.com/showthread.php?t=1118918
I am also having issues. I have an SGS2 with 2.3.3..
I have rooted the phone and am trying to install Cyanogenmod7 (nightly build #22) to my phone.
I have downloaded ROM Manager, Flashed Clockwork Mod Recovery (4.0.1.5) and have tried to 'Install ROM from SD Card', then selected the cyanogenmod. However, its coming up with the following message:
Finding update package ...
Opening update package ...
Verifiyng update package ...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
I have tried to download 3e without signature verification "3e_recovery_no_sig_check" but this has not worked. I am a bit of a noob at this so appreciate any lamens terms help anyone can provide!!
Hey guys. I tried the KG6 and CF kernel, and the lulz kernal. Both are giving me t 3e error on CWM. What else can I do?
cant flash roms
Hey guys,
I too am having this problem. I have completely lost the ability to flash roms from cwm. It says "Installing update" when its a new rom and it flashes it in less that 3 seconds and then it gets stuck at the boot. If I use rom manager it just says "E: signature verification failed on the whole file". I have tried the following:
-restoring stock rom (KE2) and then using cf-root which installs 4.0 and cwm 4.0.0.2
-formatting sdcard
It's really bad, I am dwelling on just one nandroid backup of Cognition and I can't even update it!
Thanks for your help
You cannot use 3e to install custom roms. 3e (blue color) is the default samsung recovery. When you try to flash custom rom with 3e, it will fail verification.
You need to use Clockwork Recovery (orange color).
Try installing Speedmod Kernel instead of using CF-Root kernel and see what happens.
Mate that totally fixed it thanks so much for the help! Now I can get back to flashing stuff!!
Sent from my GT-I9100 using XDA Premium App
Problem to flash CWM
Hi,
Here are the steps that got me into this situation:
1. My provider installed a test version on my Galaxy S2 in order to resolve some problems.
2. After the above I rooted my device using ODIN 1.85 and SuperOneClick 2.1.1 using XWKDD kernel.
The versions of my phone now are:
Model Number GT-I9100T
Android version 2.3.4
Baseband version I9100TJIKI1
Kernel version 2.6.35.7-I9100XWKDD-CL161513 [email protected]#2
Build Number GINGERBREAD.JIKI2
My intention is to flash CWM in order to install Cyanogenmod ROM. When I tried to flash the CWM using ROM Manager it failed. From what I read it is because I have 3e recovery.
I saw some suggestions for resolution, like flashing a stock kernel and than flash CWM again to avoid the invalid signature problem.
However, I couldn't find any kernel that fits my device situation.
Any suggestions for a route I can take to resolve the situation?
a route that will leave my device functioning
Thanks, Nissim
You should try and install a custom kernel which also flashes clockwork mod recovery on your phine like speedmod, ninphetamine or hellcat's kernel.
taqri85 said:
You should try and install a custom kernel which also flashes clockwork mod recovery on your phine like speedmod, ninphetamine or hellcat's kernel.
Click to expand...
Click to collapse
Thank you for the advise.
Unfortunately digging into the above kernels you suggested, I couldn't find that any of them fits my situation (Build:GINGERBREAD.JIKI2 and kernel:XWKDD).
I saw clear warnings not to select the wrong kernel.
Look for cfroot kernel. It is almost stock. Just rooted. I think i saw ki2 over there.
Sent from two cans and a string.
plazzTT said:
Thanks.
Got this working yesterday by flashing this kernel:
http://forum.xda-developers.com/showthread.php?t=1118918
Click to expand...
Click to collapse
Worked for me!
nathsgames said:
Worked for me!
Click to expand...
Click to collapse
which link? many link, i duno which 1 need to select, we re in the same problem, help...
I was trying to switch my phone over to CWM from TWRP. I tried flashing using ROM manager but it was always rewritten. I decided to grab the .img file from the CWM site and flash it in terminal emulator like I had done with TWRP before. It seemed to flash but when i rebooted I got the message that the system software was not authorized. I thought the file I downloaded was loki but I guess not. Do I have to odin back to stock now or is there another method?
So I just realized it was being stupid and was stuck trying to boot recovery. I booted to download mode and selected cancel to force it out of this loop. Once it did this I was able to boot the system and restore a proper recovery.
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
thecaptain0220 said:
On a side note, does anyone know why flashing CWM doesn't stick. I read some things about the recovery being flashed every boot but all the information was out dated, I couldn't find anything about the S4.
Click to expand...
Click to collapse
ROM manager does work...try flashing then reboot at least once before booting recovery...and if you are running a stock tw rom some will attemt to overwrite custom recovery...in newer cwm it will ask you if you want to disable recovery install...clicking yes will stop the process keeping custom cwm
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.
Hey everyone. I decided to revive my S2 but I ran into a problem and I can't solve it. I lost count of threads I read and I still don't have an answer. Can someone guide me step by step how to flash CWM and ROM to my SGS2 (i9100)?
At the moment I have stock ROM flashed using Odin since all my tries to flash latest CWM and ROM ended in a bootloop or I didn't even manage to flash anything. If I try to flash CWM through stock Android recovery, it says "Signature verification failed". I flashed Dorimanx kernel using Odin to get the recovery but then I couldn't flash ROM because it said "E: Can't mount sd card". I tried flashing Resurrection Remix ROM.
I have no idea what to do because everytime I think something new, I run into these 2 errors. It would be great to get some help.
Ignas.
Read about philz kernel zip. This can be flashed through stock recovery and it will give you what you need . root and cwm
andrewwright said:
Read about philz kernel zip. This can be flashed through stock recovery and it will give you what you need . root and com
Click to expand...
Click to collapse
I downloaded the kernel from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100 but I get this error: E:Error in /tmp/sideload/package.zip (Status 7). Above this, in the yellow font, it says This pacakge is for galaxys2, i9100, GT-I9100, GT-I9100M, GT-I9100P, GT-I9100T, SC-02C', devides: this is a ' '. How can I fix this?
http://forum.xda-developers.com/gal...lz-cwm6-stock-kernel-cwm6-root-exfat-t1877270
Kernel not just recovery.
I think you need to read the thread before flashing away and possible bricking you're phone.
Rooting and installing cwm is basic stuff. Bricking is common place too.
andrewwright said:
http://forum.xda-developers.com/gal...lz-cwm6-stock-kernel-cwm6-root-exfat-t1877270
Kernel not just recovery.
I think you need to read the thread before flashing away and possible bricking you're phone.
Rooting and installing cwm is basic stuff. Bricking is common place too.
Click to expand...
Click to collapse
Do you mean this http://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/Stock (Download doesn't work) ? I can't find any other links there for the latest version.
I'm not really scared of bricking my phone since I won't use it without flashing it correctly anyway. I have flashed it few times successfully in the past but now I can;t do this and it's really annoying. I flashed my friend's phone without any problems but I can't do that for myself.
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..