Trying to get my first rom on to this note.
Ive tried twrp 2.7.1 / 2.8.0 and cwmr 5.5 / 6.0.4.3 and I havent managed to get one installed yet.
Current error im trying to get past is
"radio must be newer than ucmd3." on CWMR
"E:Error executing updater binary in zip" In TWRP I'm getting
dzee206 got me up to the latest CWMR which helped but now I'm stuck.
Currently on stock 4.0 rooted with custom recovery
----------------------------------------------------------------------------------------------------------------------------------------
SOLVED
apparently you need a new radio from the factory image. if you return to stock using odin and the imgs for stock linked here apparently it puts an old radio in.
you need this radio to flash 4.4+ in both TWRP and CWMR
http://forum.xda-developers.com/showthread.php?t=2261713
oscar the grouch said:
Trying to get my first rom on to this note.
Ive tried twrp 2.7.1 / 2.8.0 and cwmr 5.5 / 6.0.4.3 and I havent managed to get one installed yet.
Current error im trying to get past is
"radio must be newer than ucmd3." on CWMR
"E:Error executing updater binary in zip" In TWRP I'm getting
dzee206 got me up to the latest CWMR which helped but now I'm stuck.
Currently on stock 4.0 rooted with custom recovery
----------------------------------------------------------------------------------------------------------------------------------------
SOLVED
apparently you need a new radio from the factory image. if you return to stock using odin and the imgs for stock linked here apparently it puts an old radio in.
you need this radio to flash 4.4+ in both TWRP and CWMR
http://forum.xda-developers.com/showthread.php?t=2261713
Click to expand...
Click to collapse
That is why i always suggest to odin the latest firmware if coming from ics and wanting to flash a jb or kitkat rom… its actually a partition issue involving the modem partition. Which is very important to booting up.
I couldnt find that info. Samsung needs a fastboot feature. odin is a pain
Related
I have a HTC One from T-mobile and it is currently stuck on a GPE rom I got from HTConeroot.com - m7_GPe_JWR66V_deodexed-signed.zip. I tried to upgrade to android kitkat 4.4 using the same website I mentioned earlier and followed directions to install rom manager so I could get CWM recovery instead of TWRP. I flashed CWM 6.0.3.1 and then rebooted into recovery to flash the latest 4.4 ROM but the flash failed. I had a backup at the time to stock Sense but somehow deleted it out of frustration. The phone then became bricked. I sideloaded the above mentioned GPE rom w/4.3 and now I'm stuck here. I have a Dell Windows 8.1 computer and can no longer use fastboot to flash any other recoveries. Rom manager says it has flashed TWRP but when I reboot it is still CWM 6.0.3.1. Does anyone have any suggestions on how to flash a different recovery or a different rom????
I have Safestrap up and running again but I'm wondering how can you install other recoveries like TWRP and CWM so I can boot directly into the custom recovery without a splashscreen I believe it's called (newbie here). I followed instructions online with GooManager for TWRP and ROM Manager for CWM but neither will actually boot into the custom recovery.
In GooManager after it says the TWRP recovery has been installed, it will reboot but then take me to the downloading boot screen and say "could not do a normal boot." What's with that? I actually had to use ODIN again to flash the stock ROM back (I tried this three times to no avail...)
And for CWM it says it successfully flashed in ROM Manager but when I actually reboot into recovery, whether it be from the app or manually, it will just boot into the stock Android recovery. I don't get it...
What am I doing wrong and/or is my phone not compatible with these recoveries?
Specs:
Verizon Galaxy S4
Android 4.3
Build MK2
Kernel MK2
Also are there any other recoveries that might work with my phone?
Thanks!
....
Bootloader is locked and custom recovery can't be installed on newer/updated S4. Do some reading to find out what is and is not possible with a locked bootloader.
the immunity said:
I have Safestrap up and running again but I'm wondering how can you install other recoveries like TWRP and CWM so I can boot directly into the custom recovery without a splashscreen I believe it's called (newbie here). I followed instructions online with GooManager for TWRP and ROM Manager for CWM but neither will actually boot into the custom recovery.
In GooManager after it says the TWRP recovery has been installed, it will reboot but then take me to the downloading boot screen and say "could not do a normal boot." What's with that? I actually had to use ODIN again to flash the stock ROM back (I tried this three times to no avail...)
And for CWM it says it successfully flashed in ROM Manager but when I actually reboot into recovery, whether it be from the app or manually, it will just boot into the stock Android recovery. I don't get it...
What am I doing wrong and/or is my phone not compatible with these recoveries?
Specs:
Verizon Galaxy S4
Android 4.3
Build MK2
Kernel MK2
Also are there any other recoveries that might work with my phone?
Thanks!
Click to expand...
Click to collapse
I'm not sure how any one misses a sticky thread like this one:
http://forum.xda-developers.com/showthread.php?t=2606501
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 switch from CWM to TWRP.
The problem is, that when I flashed CWM, my android was 4.1.2 version, and so was the recovery.
I've already flashed newer rom than 4.1.2, and now I want to switch to TWRP.
My concern is: Now that I downloaded the latest TWRP and I use Nandroid, it prompts me that the TWRP .img file is built for 4.1.2 android, so can I still flash the TWRP although I have higher version than 4.1.2?
*Also, is Nandroid a working way to switch between recoveries? I've never done that before, and I just came across a thread that suggests using Nandroid to flash new reocvery over the existing one.
Thanks!
TWRP or CWM Recoveries will work in all android versions. Just download twrp-2.8.6.1-i9300.tar flash it via odin. Here is the link - https://dl.twrp.me/i9300/
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?