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????
Related
Hi developers!
So my rooted htc gsm version has a 'android system recovery installed'. And im needing android 4.0 for some app development.
I can't seem to flash a new recovery since "ClockworkMod Recovery" does not support older devices. I downloaded an older version of the ClockworkMod Recovery but trying to flash the recovery says that there's error. I need ClockworkMod Recovery to be installed on my phone to be able to install android 4.0.
Anyone has other methods to install ClockworkMod Recovery rather using their servers?
thank you
The recovery you got from cwm is enough to install CM9, check your CM9 zip, its probably a bad download
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 followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Did you fiqure it out
Sent from my SM-G900P using XDA Free mobile app
lsdyna said:
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Click to expand...
Click to collapse
You should be suing TWRP 2.7.0.1 and do not use goo manager.. Go to their site and click on the alternate download.. I do believe TWRP mentioned they disable the goo manage download because of issues.. Make sure you are also choosing the right phone.. I have choosing the wrong phone more than once.. Also when your done flashing in odin, and you reboot into recovery manually, make sure you wait until you see the line about recovery, before you release the 3 buttons, or you will just boot into your desktop.. Also you can use TWRP on KItKat firmware as many have done so..
Mid year I decided to root and flash Cm 11 onto my little s3 mini (gt-i8190) and everything went great. Recently I read on the Novafusion website that they recommend using TWRP instead of CWM, searched on Google and saw it was safe to flash over custom recoveries. I used Odin to flash over the TWRP I downloaded from the Novafusion site. When odin completed its process my phone rebooted into TWRP and it all seemed fine, then I proceeded to flash the latest version of the Cm 11 4.4.4 rom. Again everything went great and my phone booted up normally.
I got the zip file for the Android L keyboard and I used Rom manager to reboot into recovery and showed the "Samsung Galaxy sIII mini gt-i8190 screen and just went black for 10 seconds, rebooted and continued going black then rebooting. I pulled the battery out and booted up my phone again then used rom manager to flash CWM again and it worked! I used CWM to flash the keyboard apk and it worked.
I was a little bit worried about the recovery bootloop and decided to make a nandroid backup. I couldnt reboot into recovery, manual way or with Rom manager.
I have used odin to flash CWM and TWRP a few times now without any luck. My phone just reboots normally when odin finishes.
If anyone could shed some light on this issue I would be grateful.
Thank you.