Hey All,
Yesterday I started looking at flashing a custom ROM onto my Galaxy Mega (I9205) but I'm having real issues. I've tried multiple ROMs and recoveries and I run into errors every time. Hopefully I'm being a moron and have missed a step somewhere but I really don't think that's the case. I've trawled these forums to see if I can work out why this might be happening but with no luck.
The procedure I've used so far:
Use ODIN to flash custom recovery (tried both CWM and TWRP from http://forum.xda-developers.com/showthread.php?t=2369998)
Factory Reset, clear cache and dalvik cache.
Install ROM from recovery (I've tried PAC-man, CyanogenMod and LiquidSmooth.)
Errors have ranged from generic failures to "incorrect device" type messages and "Status 7".
A curious issue I ran into was with PAC-man. When I tried to flash the meliusltexx version, the install script detected my device as the melius3g. I can say categorically that my device is the I9205 NOT the I9200. I removed the assert section from the updater script and although the script now runs, it fails later in the process.
I've attached a log from the last attempt I made. This was using TWRP to flash pac_meliusltexx-nightly-20140306.
Thanks for any advice in advance.
I'm not the best at helping at problems, but I give it a try.
I noticed you used the TWRP from a pretty outdated thread.
Silesh.Nair has a few download links in his signature, which leads to the most updated recovery.
Also Philz Recovery (the one I use the most) has a separate thread.
Have you tried those recoveries too? Maybe you should flash them through odin first, and then install the roms.
Brilliant that did it. Used Philz recovery and ROMs are now installing correctly. Where do you find info on things such as the latest recoveries? I've been searching and the most up to date I came up with were the ones mentioned in the original post.
Thanks a lot for your help - glad it turned out to be something simple.
demented_goose said:
Brilliant that did it. Used Philz recovery and ROMs are now installing correctly. Where do you find info on things such as the latest recoveries? I've been searching and the most up to date I came up with were the ones mentioned in the original post.
Thanks a lot for your help - glad it turned out to be something simple.
Click to expand...
Click to collapse
We are here to help. Glad I helped! I had the same problem, and I found Philz recovery the original development (Philz Recovery Have fun with flashing, and don't forget:
We are here to help you
Related
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Anyone please?
rozel said:
Hi
I am running a Stock LSD 4.1.2 JB Rom on my I9100 and do not wish to Root my phone. Yes it was rooted once but I have a specific reason for not wanting to revert back to root.
On a few occasions over the past year I have wanted to flash an app via "Recovery Mode", a .zip file located on the phone's external SD card.
On trying to flash, the following is displayed in yellow: -
E: failed to verify whole-file signature
E signature verification failed
Installation aborted.
I have searched and searched this and other forums and although I can find many many instances when this has ocurred with other people I have not yet seen a generic solution to this problem.
It must ocurr because of a certain situation being prevelant within my phone and the references to it on forums usually suggest they are because someone is messing with a Custom Rom and/or a Rooted Kernal etc etc.
Could someone please tell what is happening, why this is the case and what can be done to sort it please.
I would say that my phone is just over 18 months old, never has had a problem, has been flashed with "Stock Roms" quite a few times and all without wiping or restoring to the factory settings. I do not want to wipe it to sort this problem out and am hoping an easy fix is available.
Hope someone can help
ps - I am trying to install the 4.2 Camera via the patched.zip and have tried to install the "Temporary" Clockwork Recovery" app with exactly the same problem. I stress I do not want to Root.
Click to expand...
Click to collapse
You need root access to flash apps or modify your system
pasanjay said:
You need root access to flash apps or modify your system
Click to expand...
Click to collapse
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
rozel said:
Ermm, do not think so. Please review this thread before making wild comments like this: -
http://forum.xda-developers.com/showthread.php?t=2082103
I know in some way though that you probably thought you were helping.
Surely this problem has a cause and a solution?
Click to expand...
Click to collapse
u have to first flash the 'Temporary CWM recovery .zip' then select 'reboot to recovery' option in stock recovery to enter 'temporary cwm recovery' there u select the 'Camera zip file' to flash.
PS- after flashing 'Temporary CWM recovery.zip' do not reboot ur phone the normal way by doing so u will lose ur temporary recovery.
each time before flashing any zip file u have to flash 'temporary cwm.zip' file first.
Hi thanks but I know this.
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
rozel said:
Can we get back to my topic please? I would not have posted if I could flash the Temp CWM Recovery. zip file
I just need to know what causes the error I am getting and how I can irradicate it.
Click to expand...
Click to collapse
As the error indicates, it fails to verify the file's signature. You can't flash unsigned packages via stock recovery. The solution is exactly what was already mentioned to you:either root and install a custom kernel/recovery (you don't want it, that's fine), or use a temporary custom (non-stock) recovery. While I had problems with the stock recovery flashing unsigned zips (obviously), I never had an issue with flashing a temp recovery. Try redownloading and reinstalling it - it could be a corrupt file. Which recovery are you trying to use? I recommend the temp touch CWM by Phil (the dev of the PhilZ kernel; use link in his signature). Always works like a charm.
kt-Froggy said:
Try redownloading and reinstalling it - it could be a corrupt file.
Click to expand...
Click to collapse
Nice one! Thank you
It must have been a duff file (temp touch CWM by Phil) as the one I just downloaded, installed without a problem. It was the very same program file but from a different source.
Just installed the 4.2 Camera too so now going to play
Thank you again
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.
Hello,
I want to mess around with WinSuk's great work (and the androidarmv6 team), but I'm a bit lost with recoveries.
I can't check right now, but I think the phone currently has 4EXT, or maybe an old CWM.
I've always used CWM, but I've been trying TWRP on my Moto G for a while and I like it better I think.
Will this TWRP 2.2.2.0 http://forum.xda-developers.com/showthread.php?t=1886046 work?
Do I absolutely need this CWM 6.0.2.8 http://forum.xda-developers.com/showthread.php?t=2474662?
Or is this one http://download.androidarmv6.org/_builds/liberty/recovery-liberty.img more up to date?
Thanks!
Edit:
I have tried all of them, and I cannot seem to install cm-11-20140726-NIGHTLY-liberty.zip
E:Error in /sdcard/cm-11-20140726-NIGHTLY-liberty.zip
(Status 0)
I have wiped and formatted everything before trying, I have also tried with cm-11-20140725-NIGHTLY-liberty.zip, I checked the md5sum both on my disk and on the phone, everything is ok.
It did work once, I think it was with the recovery linked in the thread, but then flashing gapps gave the same error.
Djon_ said:
It did work once, I think it was with the recovery linked in the thread, but then flashing gapps gave the same error.
Click to expand...
Click to collapse
I tried again with everything, and I was able to install the ROM with the recovery from androidarmv6.
But now it gives me the same error for the gapps, complaining about /misc missing in the logs.
Well I finaly did it!
Installed cm-11-20140726-NIGHTLY-liberty.zip with recovery-liberty.img from androidarmv6 and gapps-4.4-tocache-20140605.zip with cwm-6.0.2.8-UNOFFICIAL-liberty.zip.
It's still booting, and I haven't tested TWRP but the thread is more than one year old so I probably won't.
I was only able to flash the CM11 Nightlies using the recovery-liberty.img from androidarmv6.org builds, but as of 9/6/2014 it seems to no longer be there.
I also found that flashing CM11 Nightlies required that version of recovery, but in order to flash gapps, I needed to use 6.0.2.8 from WinSuk, otherwise I would get an error.
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..
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?