"Failed to boot to Recovery Mode" : TWRP and CWM - Upgrading, Modifying and Unlocking

[SOLVED] Recent TWRP, CWM, and Philz recoveries all fail. Using an older (3.0.0.1) version of TWRP allows the HTC One A9 to successfully enter recovery.
I've tried installing both TWRP and CWM recovery. In both cases, ADB reports that I've successfully updated the partition. When I select "Boot to Recovery Mode" with CWM, I get the error "Failed to boot to Recovery Mode". When I select "Boot to Recovery Mode" with TWRP, it boots to normal, not recovery.
I'm using the most recent .img from both, for the HTC One A9. Here's what ADB reported:
C:\Users\Oifle\Desktop\fastboot-win>fastboot flash recovery twrp3310hiae.img
sending 'recovery' (38038 KB)...
OKAY [ 3.057s]
writing 'recovery'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.246s]
finished. total time: 6.304s
Ideas, please?

Related

Complications during CM install. Can't find HTC__Y13 firmware; CWM recovery bootloops

I've been trying to install CyanogenMod for my endeavoru by the instructions in their wiki. These are the steps I took in the very beginning:
Unlock via HTC Dev
Flashed CWM
Entered CWM
Ran the CWM backup function
Wipe data/factory reset
Transferred over the .zip file
Attempted to flash from sdcard
The installation aborted because I apparently have an insufficient version of HBOOT (1.12.0000). The page on endeavoru itself had a note on this, but the install page doesn't, so like a fool I thought there would be instructions relating to that when it became relevant. Thinking what to do, I figured maybe upgrading HBOOT is the same as flashing boot.img (which IS mentioned in the install guide), so I did that as well, but the HBOOT version stayed the same.
I was uncomfortable with not feeling in control of events, so I thought I'd get back to the stock OS as a way to reassure myself and make an external (nandroid?) backup. I thought using CWM's backup/restore function would make that possible, but when I did a restore and rebooted it just went into a bootloop. (There was a FAQ item on this, but it assumed I had a zip file to get the boot.img out of, which I don't -- this was a recovery).
Easier than finding a stock rom would seem to be just to upgrade HBOOT. I found this guide on the topic, but the link to firmware doesn't work. I've found others using Search, but they don't work either. (I have HTC__Y13.) One site that has files is here, but I'm being cautious because the phone isn't cheap and I'm trying hard not to brick it. First, the site is in German (I speak a little, but I can't bee 100% sure what these things are saying); second, the link didn't come from xda-developers, so I'm wary of trusting it out of hand.
Would you suggest going on a search for another ROM (2.17.401.2), or flashing HBOOT (with a file from the German site or from somewhere else), or some other thing? The main thing I'm concerned about for the moment is having a functional phone in the next few days.
Also, can I generally expect the battery to not run out while plugged in by USB?
Thanks in advance.
Grab the firmware.zip from the german site, it seems good.
You can get the boot.img for your nandroid backup by selecting mounts and storage > mount usb storage > /sdcard/clockworkmod/backup/
Your device will charge, provided that you are booted in recovery and the version is 5.8.4.0.
Sent from my One X using xda premium
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
hallydamaster said:
Also, you shouldn't be concerned when flashing a HBOOT, because the package will have to be signed by HTC.
And before flashing anything you will have to flash original recovery, and relock bootloader. This basically means you will be unbrickable!
Unless something goes wrong in the process ofcourse (unlikely)
Click to expand...
Click to collapse
To flash the hboot you don't need to flash back the stock recovery first ...... Just relock, flash the firmware, unlock, flash a custom recovery again and install a new rom
Thanks. It looks like I got the lock and flash done fine, but it hangs on unlock:
Code:
[~/endeavory] fastboot oem lock
...
OKAY [ 0.000s]
finished. total time: 0.001s
[~/endeavory] fastboot oem rebootRUU [13:14]
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]finished. total time: 0.190s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
sending 'zip' (12876 KB)...
OKAY [ 1.757s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 5.116s
[~/endeavory] fastboot flash zip firmware.zip [13:15]
< waiting for device >
sending 'zip' (12876 KB)...
OKAY [ 1.661s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) Format partition LNX done
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) Format partition SOS done
(bootloader) [RUU]WP,recovery,100
(bootloader) ERASE backup cid
OKAY [ 3.176s]
finished. total time: 4.837s
[~/endeavory] fastboot flash unlocktoken
Unlock_code.bin [13:16]
sending 'unlocktoken' (0 KB)...
OKAY [ 0.021s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
What I'm seeing right now is a black screen with a htc logo and a full green status bar. It's been this way for a while.
What should I do? Is it safe to terminate the unlock command?
Yeah press ctrl+c and reboot phone.
Sent from my One X using xda premium
All right, I'm happily using HBOOT 1.39 now with a CyanogenMod nightly running, and ready to explore this supermarket of excitement and possibility.
I terminated the process and rebooted, which worked fine, and flashed boot.img and CWM and then CM from recovery.
Thanks again to all of you.

Can't Flash TWRP "Signature Verify Fail"

This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>
Try the HTC_fastboot adb package. It's posted several times here on xda.
Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)
Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions
rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).

No error at flashing TWRP, but can't boot into it

Bought Japan Variant HTC 10,
S-off, Bootloader Unlocked.
[flashed TWRP once and did Backup.]<-yeah i did
Changed CID to US Unlocked one and RUUed Android 7.0
All went great at this point.
Then I tried to flash TWRP again and now i just can't boot into it.
flashing went smoothly, at leat log says;
fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (21992 KB)...
OKAY [ 1.717s]
writing 'recovery'...
(bootloader) HOSD CL#831921
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.529s]
finished. total time: 4.249s
fastboot reboot-bootloader
AAAAAAAAAAAAAAAND I just can't boot into TWRP.
Phone just showing htc logo for a while and reboot to ROM.
So i tried fastboot boot twrp.img method, still not working.
download mode screen
Am I missing sth? like key combo to show twrp or bug at twrp 3.0.2.6?
I had the exact same problem, I solved it by flasing the twrp 3.0.3-0 unofficial version that you can find on the twrp recovery's thread
Edit: I don't know if this is the right way to do it, it worked for me but I'm new in the modding world and I'm not sure it will work for you too or if it's safe. Maybe is better to wait for someone that knows more than me.
solved
Since I did OTA from 2.28.617.8 to 2.38.617.6,
I googled and RUUed 2.38.617.6, not 2.28.617.8 from official HTC US hp.
and I flashed twrp 3.0.3.0 unofficial, instead of 3.0.2.6 official.
I don't know which one was critical, but everything went fluently.
Seems like 3.0.3.0 was the critical one.
Thx @fratorga100, for the reply.

Flash TWRP but never replaces original recovery

Hi
I have flashed the latest 3.1.1 TWRP to my son's phone successfully three times this morning, and when I reboot to download mode, twrp does not show, the original recovery shows instead. As you see below, it flashes fine, but somehow does not!!
On this TWRP website, it mentions "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery."
But a search in Google results in me finding the page which tells me to look on Google! Does anyone know if this is "key combo" is how we have to flash TWRP properly? This phone is not rooted.
Tx
Mark.
D:\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (53680 KB)...
OKAY [ 2.946s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.232s]
finished. total time: 6.180s
fredphoesh said:
Hi
I have flashed the latest 3.1.1 TWRP to my son's phone successfully three times this morning, and when I reboot to download mode, twrp does not show, the original recovery shows instead. As you see below, it flashes fine, but somehow does not!!
On this TWRP website, it mentions "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery."
But a search in Google results in me finding the page which tells me to look on Google! Does anyone know if this is "key combo" is how we have to flash TWRP properly? This phone is not rooted.
Tx
Mark.
D:\Android\android-sdk\platform-tools>fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (53680 KB)...
OKAY [ 2.946s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.232s]
finished. total time: 6.180s
Click to expand...
Click to collapse
Bootloader is unlocked? If not then you can't flash it. Or won't flash
Sent from my HTC 10 using XDA Labs
You can get to recovery from bootloader.
Ie. Vol down + power gets you to download mode, then select reboot bootloader, from the bootloader, select reboot recovery.
DeeZZ_NuuZZ said:
Bootloader is unlocked? If not then you can't flash it. Or won't flash
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Hi, yes unlocked.
Sent from my SM-N950F using Tapatalk

weird recovery problem

Hi, I have weird problem with my recovery, I have been ignoring this for few months but I finally want to fix it, but i don't know how. I flash it normally, here are logs from bootloader ( its newest TWRP. named it because i had another older TWRP in same folder)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (25328 KB)...
OKAY [ 0.681s]
writing 'recovery'...
OKAY [ 0.384s]
finished. total time: 1.066s
The problem is, the "fastboot reboot recovery" command just doesn't work, and in bootloader there is no option such as recovery, the vol up + power button is just booting me in system.
In android i can normally do reboot to recovery in magisk or if there's a system option to do it, but the manual option is almost needed for me, because everytime my system installation doesnt go properly, I must plug my phone into computer and do "fastboot boot twrp2.img", and thats pretty annoying.
Pawlash said:
Hi, I have weird problem with my recovery, I have been ignoring this for few months but I finally want to fix it, but i don't know how. I flash it normally, here are logs from bootloader ( its newest TWRP. named it because i had another older TWRP in same folder)
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp2.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (25328 KB)...
OKAY [ 0.681s]
writing 'recovery'...
OKAY [ 0.384s]
finished. total time: 1.066s
The problem is, the "fastboot reboot recovery" command just doesn't work, and in bootloader there is no option such as recovery, the vol up + power button is just booting me in system.
In android i can normally do reboot to recovery in magisk or if there's a system option to do it, but the manual option is almost needed for me, because everytime my system installation doesnt go properly, I must plug my phone into computer and do "fastboot boot twrp2.img", and thats pretty annoying.
Click to expand...
Click to collapse
u tried install via twrp?
- send twrp2.img to device storge
- u make again fastboot boot twrp2.img via adb
- go it twrp Install>Install Image>select twrp2.img> select recovery and then swipe to confirm flash
Astridxx said:
u tried install via twrp?
- send twrp2.img to device storge
- u make again fastboot boot twrp2.img via adb
- go it twrp Install>Install Image>select twrp2.img> select recovery and then swipe to confirm flash
Click to expand...
Click to collapse
same, the phone can boot into TWRP through android(in magisk, reboot recovery or system option), but in bootloader, the "recovery" option just isnt showing up, and if i press vol up + power button the phone boots into system.

Categories

Resources