I recently updated my HTC One SV (K2_CL) to 4.2.2. I did what I would usually do; restore a stock rom (without root) and re-flash the stock recovery. Then I update from there. Now I want to install root. However, after I flash TWRP recovery to flash root from there, when I try going into recovery mode it just stays at the HTC splash screen with the red text at the bottom.
What I would like to know is if the new update somehow added a security feature, because after I re-flash the stock recovery, I am successfully able to boot into recovery (which there is no point in doing so).
Make sure, you use a recovery for boost from here.
old.splatterhand said:
Make sure, you use a recovery for boost from here.
Click to expand...
Click to collapse
Thank You soooo much!:laugh: I never would have thought that I needed a new version of TWRP. I have successfully booted into TWRP and will begin restoring my data.
Related
Hi guys still a neewbi here I have a Motorola Photon Q 4g lte it has boot loader unlock and rooted Im trying to do a update to software 77.8.14 xt897 it keeps failing ........I dont have any custom roms install .......I also seem that I cant boot back to recovery mod ....help.thanks
Did you have a custom recovery installed...? Or were you stock completely?
You said you had the bootloader unlocked and it rooted, so I'm going to assume you were on CWM or TWRP... so did you put stock recovery back on before updating? You can't take system updates if you're on custom recovery.. you have to put the stock recovery back on, then update, then re-do recovery & root.
no stock
arrrghhh said:
Did you have a custom recovery installed...? Or were you stock completely?
You said you had the bootloader unlocked and it rooted, so I'm going to assume you were on CWM or TWRP... so did you put stock recovery back on before updating? You can't take system updates if you're on custom recovery.. you have to put the stock recovery back on, then update, then re-do recovery & root.
Click to expand...
Click to collapse
ok thanks for the reply...............no i'm on cwm so I need stock recovery is there a site or link...........thanks
gtuck1002 said:
ok thanks for the reply...............no i'm on cwm so I need stock recovery is there a site or link...........thanks
Click to expand...
Click to collapse
Well, here's a good guide from the last update. Probably still applies for this update.
This thread might help as well.
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4
LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi
Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??
808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.
It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...
LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.
Hello experts,
As the title states I ignorantly took the OTA 4.4.3 with TWRP installed. After downloading the phone asked if I wanted to install the new firmware. I clicked yes and my phone went right into recovery. I tried to nan droid back to Venom 1.8 and It just stuck on the splash screen. I tried multiple venom rom nan droids and none would boot.
I was able to nan droid back to my stock back up (not stock recovery but everything else). I flashed the stock recovery through adb/fastboot and am now trying the OTA again. I assume the OTA should work now ( unless I am missing something ?).
Once the OTA takes, assuming it does, should I be able to restore back to venom ? What was preventing the restore from working originally?
Thank you so much for any help you can offer.
-Tony
Trantzz said:
Hello experts,
As the title states I ignorantly took the OTA 4.4.3 with TWRP installed. After downloading the phone asked if I wanted to install the new firmware. I clicked yes and my phone went right into recovery. I tried to nan droid back to Venom 1.8 and It just stuck on the splash screen. I tried multiple venom rom nan droids and none would boot.
I was able to nan droid back to my stock back up (not stock recovery but everything else). I flashed the stock recovery through adb/fastboot and am now trying the OTA again. I assume the OTA should work now ( unless I am missing something ?).
Once the OTA takes, assuming it does, should I be able to restore back to venom ? What was preventing the restore from working originally?
Thank you so much for any help you can offer.
-Tony
Click to expand...
Click to collapse
Twrp recovery doesn't flash firmware. If all you want is the updated firmware, go to tigerstown's thread and flash the firmware only zip and stay on venom the whole time.
College assisten
dottat said:
Twrp recovery doesn't flash firmware. If all you want is the updated firmware, go to tigerstown's thread and flash the firmware only zip and stay on venom the whole time.
Click to expand...
Click to collapse
Yes, going forward I will install the firmware via fast boot . Since I had a stock backup ( so I thought) I wanted to try it this way.
Everything is working as intended now. Once I flashed the stock recovery the phone updated and I was able to restore Venom 1.8.
Thanks for your input.
-T
Hello it's been several days i can't find a solution to my problem. I flash official RTFR 4.1.2 via RDS Lite and then i upgrade to Kitkat 4.4.2 via OTA update.
When my phone reboot i have The Unlocked Bootloader Warning logo on the screen, but i lost the root.
This is the version i have: 180.46.127.XT925.CEE-Retail.en.EU.
I did install a recovery (Philz Touch, CWM,) but when i reboot to recovery it was not working and i had the google Droid with a red triangle.
I'd like to know if it is possible to root my phone in order to flash the CM12 ROM? Or with this official update i'm stuck with 4.4.2 and won't be able to root?
Thanks for your help.
When you install a custom recovery after taking the OTA, the recovery will usually ask you to disable stock recovery restore. If you don't, then the stock recovery will be reinstated upon next boot. Once you've got a custom recovery installed and disabled the stock recovery, you should be able to root it from there. Most modern recoveries will handle both the disabling of stock recovery restoration and install root (su) for you.
I know the one I use does.
CWGSM3VO said:
When you install a custom recovery after taking the OTA, the recovery will usually ask you to disable stock recovery restore. If you don't, then the stock recovery will be reinstated upon next boot. Once you've got a custom recovery installed and disabled the stock recovery, you should be able to root it from there. Most modern recoveries will handle both the disabling of stock recovery restoration and install root (su) for you.
I know the one I use does.
Click to expand...
Click to collapse
When i installed the recovery it didn't ask me to disable stock recovery restore. Where do i get that request, on my phone or on my PC? Which custom recovery that allow me to disable the stock recovery do you recommand?
After you install recovery, immediately power off your phone, boot straight back into recovery (not the OS, otherwise stock recovery will over ride the aftermarket recovery), once in recovery the update script will complete and the installation will be complete. Once in the recovery, you can choose the option that CW mentioned.
RikRong said:
After you install recovery, immediately power off your phone, boot straight back into recovery (not the OS, otherwise stock recovery will over ride the aftermarket recovery), once in recovery the update script will complete and the installation will be complete. Once in the recovery, you can choose the option that CW mentioned.
Click to expand...
Click to collapse
Thanks for you help!!!!! It did work!!! My phone is rooted now and i installed cyanogen 11. Getting ready to try CM12.
Thanks a lot
sjcbboy said:
Thanks for you help!!!!! It did work!!! My phone is rooted now and i installed cyanogen 11. Getting ready to try CM12.
Thanks a lot
Click to expand...
Click to collapse
Yay!
Sent from my HTC6525LVW using Tapatalk
Is it possible to root and keep the stock recovery? If so dose any one have a guide?
Can you obtain root without unlocking the boot loader? if not can I lock it after I obtain root?
If i do a full ADB backup can I restore it after I root the phone?
Yes it's possible to root and keep the stock recovery. But you'll have to be unlocked. Put supersu on your device. Then boot, not flash, twrp recovery
fastboot boot twrp.img
When booted into twrp flash supersu
When you reboot your device you'll be rooted with the stock recovery.
Pro tip, I really don't recommend you root with the stock recovery. You can make nandroid backups with a custom recovery and if you screw something up playing with a rooted device you can easily restore it
Likewise, you can lock the device when rooted, but unlocking it will wipe the device if you screw something up.
Sent from my Nexus 5 using XDA Free mobile app
Now that Android will not apply OTA updates if you're rooted there is really no reason to keep the stock recovery. In the past I would use OTA rootkeeper along with a stock recovery to keep root and still have OTA updates work properly but Google ruined that.
You can relock the bootloader any time you want. Unlocking it will wipe your device though.
Not sure about the ADB question. Typically anything you did to your phone would be lost and your phone would return to the state it was in at the time of a backup though. I have never done a backup in ADB to test what it does to the system partition though.
I forgot about the backup function with custom recovery. The last time I rooted an android phone was a Galaxy s2. What is the latest and greatest custom recovery now a days?
with the custom recovery how would I go about updating the OS if say 5.1.1 were to come out without having to do a clean wipe?
jd1639 said:
Yes it's possible to root and keep the stock recovery. But you'll have to be unlocked. Put supersu on your device. Then boot, not flash, twrp recovery
fastboot boot twrp.img
When booted into twrp flash supersu
When you reboot your device you'll be rooted with the stock recovery.
Pro tip, I really don't recommend you root with the stock recovery. You can make nandroid backups with a custom recovery and if you screw something up playing with a rooted device you can easily restore it
Likewise, you can lock the device when rooted, but unlocking it will wipe the device if you screw something up.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
TheDroidKid said:
I forgot about the backup function with custom recovery. The last time I rooted an android phone was a Galaxy s2. What is the latest and greatest custom recovery now a days?
with the custom recovery how would I go about updating the OS if say 5.1.1 were to come out without having to do a clean wipe?
Click to expand...
Click to collapse
I recommend twrp recovery. Google nexus 5 teamwin.
To up date from a 5.1 to a 5.1.1 I just flash the system, boot, and radio images using fastboot. If it's a bigger version change you'll likely have to flash the whole factory image and deal with the wipe.