Related
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
cytherian said:
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
Click to expand...
Click to collapse
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Shelnutt2 said:
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Click to expand...
Click to collapse
Thanks for the info, Shelnutt.
I'm kind of in a peculiar "Nexus" that I'm trying to extricate myself from. I have S-ON presently. I would like to change it to S-OFF, but I can't seem to do it. I suspect it's the bootloader preventing me, which is hboot 1.7. So, I tried to replace the bootloader and the attempts fail. I've tried it through the adb shell, fastboot, terminal emulator on the phone, and via the recovery manager (TWRP). Attempting to replace the bootloader results in "signature verify fail". Through TWRP, it also said verification failed.
I also tried to retrieve the identifier token (HTC dev) so that I could unlock the phone that way, but "fastboot oem get_identifier_token" fails with a "Command error" (although I can execute "fastboot oem rebootRUU" with no problem).
I also tried to use Regaw's boot mod tool, which replaces the bootloader and turns S-OFF. But it aborts because my Hero is already rooted. So I went into my z4Root application and selected "un-root". It said "done", but the phone remains rooted. I even tried to "Re-root" but it wouldn't complete (thinking if I root it again, I could then try another un-root).
I'm thinking I should just flash back to stock, but... I don't have any fresh nandroid backups to use. TWRP doesn't do nandroid. It does its own thing, which becomes a problem because TWRP needs Android 2.2 or higher. So... does that mean I need to install ROM Manager again, do a nandroid backup, then run an RUU back to full stock again?
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Shelnutt2 said:
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Click to expand...
Click to collapse
Thanks, you're right... in TWRP there's a checkbox to control that. There's also one to verify md5, but it requires a file (I guess it looks for [filename].md5). In any case, getting past that resulted in failure to load hboot 1.46 as you surmised.
The issue with Regaw doesn't seem to be the radio. It simply reports that there's nothing to do because the phone is already rooted. Apparently it will only run if the phone is not rooted. And to unroot, it appears the only way is by RUU. Z4Root is supposed to allow it, but when selected it doesn't do anything.
So, I finally came up with something that got me on the right path. :good:
I re-installed ROM Manager and flashed the latest ClockworkMod to Recovery. From there I could apply the hboot 1.46 ENG-SPL with no issues. I rebooted into the bootloader and saw................ HERO XC ENG S-OFF, HBOOT-1.46.2000. :highfive:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this
MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.
ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.
Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app
hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19
Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA
still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.
1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.
Hey Guys,
Really strange situation here with my HTC One:
It is originally from T-Mobile US although I have brought it to Europe now.
Basically, and I think this happened when implementing an OTA update from my rom, I have lost all access to recovery... any recovery
1) I have erased and re flashed recovery from fastboot, tried both TWRP and Clockwork.
2) I have tried different firmware versions, albeit I don't know which combination is most likely to work...
3) cannot access recovery from phone or via fastboot/adb command, cannot factory reset, cannot flash another rom...
4) Even with hboot locking unlocking and then reflashing of Recovery, still no access.
Funnily, the rom was working fine, but I could not upgrade or change it without recovery...
Phone details below, any help you can provide would be most welcome, I'm not a developer but I've been using custom android roms on phones and tablets for some years and have never encountered this.
Many Many thanks!
Phone Details:
- Carrier Unlocked with T-Mobile code
- Bootloader unlocked with HTC Dev method
- Super CID
- S-OFF
- HBOOT 1.54 (was also on 1.57 but have changed as part of trouble shooting)
- Radio 4T.29.3218.08
- OS 6.09.401.5 (have tried a couple of firmware versions)
- Rom MaximusHD 44.0.1 (now wiped due to troubleshooting with locked/unlocked hboot)
Ammon-Ra said:
Hey Guys,
Really strange situation here with my HTC One:
It is originally from T-Mobile US although I have brought it to Europe now.
Basically, and I think this happened when implementing an OTA update from my rom, I have lost all access to recovery... any recovery
1) I have erased and re flashed recovery from fastboot, tried both TWRP and Clockwork.
2) I have tried different firmware versions, albeit I don't know which combination is most likely to work...
3) cannot access recovery from phone or via fastboot/adb command, cannot factory reset, cannot flash another rom...
4) Even with hboot locking unlocking and then reflashing of Recovery, still no access.
Funnily, the rom was working fine, but I could not upgrade or change it without recovery...
Phone details below, any help you can provide would be most welcome, I'm not a developer but I've been using custom android roms on phones and tablets for some years and have never encountered this.
Many Many thanks!
Phone Details:
- Carrier Unlocked with T-Mobile code
- Bootloader unlocked with HTC Dev method
- Super CID
- S-OFF
- HBOOT 1.54 (was also on 1.57 but have changed as part of trouble shooting)
- Radio 4T.29.3218.08
- OS 6.09.401.5 (have tried a couple of firmware versions)
- Rom MaximusHD 44.0.1 (now wiped due to troubleshooting with locked/unlocked hboot)
Click to expand...
Click to collapse
So what exactly is the problem, does the flash fail? Or successfully flashing but won't load? Does it bootloop or get stuck on a particular screen?
Ammon-Ra said:
Hey Guys,
Really strange situation here with my HTC One:
It is originally from T-Mobile US although I have brought it to Europe now.
Basically, and I think this happened when implementing an OTA update from my rom, I have lost all access to recovery... any recovery
1) I have erased and re flashed recovery from fastboot, tried both TWRP and Clockwork.
2) I have tried different firmware versions, albeit I don't know which combination is most likely to work...
3) cannot access recovery from phone or via fastboot/adb command, cannot factory reset, cannot flash another rom...
4) Even with hboot locking unlocking and then reflashing of Recovery, still no access.
Funnily, the rom was working fine, but I could not upgrade or change it without recovery...
Phone details below, any help you can provide would be most welcome, I'm not a developer but I've been using custom android roms on phones and tablets for some years and have never encountered this.
Many Many thanks!
Phone Details:
- Carrier Unlocked with T-Mobile code
- Bootloader unlocked with HTC Dev method
- Super CID
- S-OFF
- HBOOT 1.54 (was also on 1.57 but have changed as part of trouble shooting)
- Radio 4T.29.3218.08
- OS 6.09.401.5 (have tried a couple of firmware versions)
- Rom MaximusHD 44.0.1 (now wiped due to troubleshooting with locked/unlocked hboot)
Click to expand...
Click to collapse
i guess your problem is you see that written " Entering Recovery " but it wont . right ? if it is the case then you have to lock the bootloader and unlock it again after you unlock it type fastboot erase cache in the fastboot mod and then flash the recovery and then clear cache again ( reboot bootloader maybe and then enter recovery )it will definitely work. Well worked for me Best of Luck
Danny201281 said:
So what exactly is the problem, does the flash fail? Or successfully flashing but won't load? Does it bootloop or get stuck on a particular screen?
Click to expand...
Click to collapse
When you enter recovery, be it from reboot or from bootloader, it shows "entering recovery", then goes dark for a second (you'd expect TWRP screen next) and then goes back to "entering recovery" and doesn't move.
Ammon-Ra said:
When you enter recovery, be it from reboot or from bootloader, it shows "entering recovery", then goes dark for a second (you'd expect TWRP screen next) and then goes back to "entering recovery" and doesn't move.
Click to expand...
Click to collapse
Try this one http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Code:
fastboot flash recovery "name-of -recovery".img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu. :good:
Danny201281 said:
Try this one http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Code:
fastboot flash recovery "name-of -recovery".img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu. :good:
Click to expand...
Click to collapse
Tried playguy1 method but with the 2.7 TWRP I was originally on. No luck, after relock/unlock/wipe cache/flash/rewipe Cache I was still stuck in entering recovery.
After that tried reboot/wipe cache/ flash Danny201281's suggested openrecovery-twrp-2.6.3.3-m7 and erased cache / reboot...
WORKED!!!!! Many thanks to both guys!
Seems related to ROM/Firmware/Radio/TWRP version combination but it worked fine before.
Danny201281: Is there a particular reason you pointed towards openrecovery-twrp-2.6.3.3-m7 ? Most stable version for HTC One?
Again, great help! Thank you both. :good:
Ammon-Ra said:
Tried playguy1 method but with the 2.7 TWRP I was originally on. No luck, after relock/unlock/wipe cache/flash/rewipe Cache I was still stuck in entering recovery.
After that tried reboot/wipe cache/ flash Danny201281's suggested openrecovery-twrp-2.6.3.3-m7 and erased cache / reboot...
WORKED!!!!! Many thanks to both guys!
Seems related to ROM/Firmware/Radio/TWRP version combination but it worked fine before.
Danny201281: Is there a particular reason you pointed towards openrecovery-twrp-2.6.3.3-m7 ? Most stable version for HTC One?
Again, great help! Thank you both. :good:
Click to expand...
Click to collapse
It's not the first time I've come across this problem here on the forums, and in every case that is the version that always works. Unfortunately it doesn't necessarily mean an end to your problem you may find that is the only recovery that will successfully load.
You can try some different recoveries and see what happens but when all else fails use TWRP 2.6.3.3.