No error at flashing TWRP, but can't boot into it - HTC 10 Questions & Answers

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.

Related

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?).

Soft Brick Help Needed.. :(

I seem to have soft bricked my m9 hima while trying to go back to stock in order to update the firmware to the latest rev. (Yes, I have read the other threads, but I Think this might be a little more unique to my situation? )
I cannot get into my stock recovery, or my TWRP(which is what I used before).
Download mode appears to work.
I can't install TWRP with fastboot/adb, might be because device is S-on.
Tried running RUU, but says my device isn't compatible.
I would really appreciate anyones' input!
Nanometer45 said:
I seem to have soft bricked my m9 hima while trying to go back to stock in order to update the firmware to the latest rev. (Yes, I have read the other threads, but I Think this might be a little more unique to my situation? )
I cannot get into my stock recovery, or my TWRP(which is what I used before).
Download mode appears to work.
I can't install TWRP with fastboot/adb, might be because device is S-on.
Tried running RUU, but says my device isn't compatible.
I would really appreciate anyones' input!
Click to expand...
Click to collapse
Useful information that will help us help you:
CID (Carrier ID)
MID (Model ID)
Firmware version that you're currently on
Steps you took that led to your current situation
Like you said, this is a soft brick. Odds are good we can help.
---------- Post added at 04:39 PM ---------- Previous post was at 04:32 PM ----------
If you're new to ADB & fastboot, check out this thread
Once you've installed those:
- plug your phone into your computer while it is in download mode
- open a command prompt
- run the command "fastboot getvar all"
Phone is:
MID 0PJA11000
CID CWS__001
Firmware I tried to flash was this:
RUU_HIMA_UL_L51_SENSE70_ATT_MR_Cingular_US_2.11.502.18
It looks like the firmware update failed, but when the RUU program tries to read the firmware it now shows as the new one listed above.
I got to this point by trying to update the firmware. I had problems getting the new TWRP working, and I got impatient :-\
Make sure you double check the md5 hash and filesize of twrp before you flash it.
Sent from my HTC One M9 using Tapatalk
I tried flashing TWRP, and it seems to have taken it, but phone says it cannot boot intothe boot loader, it said that before I started running into soft brick issues i believe.
Try my copy https://drive.google.com/folderview?id=0B4vTiHTBB629QmxGTkpyZWlCR28
Sent from my HTC One M9 using Tapatalk
Which do you recommend, your twrp?
I know mine works..
Sent from my HTC One M9 using Tapatalk
Can't get it to flash:
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash recovery T1F.img
target reported max download size of 800000000 bytes
sending 'recovery' (30912 KB)...
OKAY [ 2.444s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.651s]
finished. total time: 5.096s
Says:
Failed to boot to recovery mode
Flash the twrp 2.9.0.1 in the link i gave. See what that does.
Sent from my HTC One M9 using Tapatalk
Nanometer45 said:
Can't get it to flash:
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot flash recovery T1F.img
target reported max download size of 800000000 bytes
sending 'recovery' (30912 KB)...
OKAY [ 2.444s]
writing 'recovery'...
(bootloader) HOSD CL#591203
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.651s]
finished. total time: 5.096s
Says:
Failed to boot to recovery mode
Click to expand...
Click to collapse
I'm pretty sure 2.9.x and later versions only work on MM, and you're on LP firmware. Try one of the 2.8.x versions from here: https://dl.twrp.me/hima/
Doesn't boot into TWRP. Maybe S-off is a problem.
Missed your post, I'll try an older build. Though I was running Cyanogenmod 13, so I don't see how that invited the problem. Doesn't hurt to try.
Older TWRP worked. Now I just need to get the latest firmware on it without android installed. Any tips?
Was able to finally get the RUU to take. Thanks for helping out. Is there no MM update for the ATT M9? That would explain some of the issues I was having. Only custom roms for options then.

Help! Can't install TWRP

I recently got a replacement HTC 10 unit from HTC. I am attempting to install TWRP on it, but am unable to.
I did the standard unlock method from HTCdev.com. Everything there worked fine and the device is unlocked.
I have downloaded multiple versions of the twrp.img but am having the same issue across the board. I can't figure out what is wrong, as I had no issues on my previous HTC 10 unit.
C:\HTC>fastboot flash recovery twrp.img
target reported max download size of 1579200000 bytes
sending 'recovery' (47708 KB)...
OKAY [ 2.668s]
writing 'recovery'...
(bootloader) HOSD CL#857212
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.074s]
finished. total time: 5.773s
Everything seems like it's fine, but when I try to boot into bootloader and then recovery it gives me the htc, this build is intended for develpment purposes... screen and then goes directly into the rom never loading TWRP.
I can't figure this out, as I never had any issue before. My device is updated with the latest US version.
Can anyone help?
Thanks
I was having the exact same issue and was literally typing the same post as you when I saw yours.
I found this link with the unofficial TWRP builds and flashed 3.0.3.3. That finally got me into TWRP. You'll still see the gray HTC letters with the red disclaimer, but wait a few seconds and it should boot into recovery.
Hopefully that helps.
yoderz said:
I was having the exact same issue and was literally typing the same post as you when I saw yours.
I found this link with the unofficial TWRP builds and flashed 3.0.3.3. That finally got me into TWRP. You'll still see the gray HTC letters with the red disclaimer, but wait a few seconds and it should boot into recovery.
Hopefully that helps.
Click to expand...
Click to collapse
That worked!
Thanks!

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

TWRP 3.3.1-0 stuck on logo

Hello,
I have some problem on my phone (AOSP 9) but I didn't know why (I didn't download any new apps, last thing was Magisk update). Now more than the half of the apps don't work, battery drain very fast and I can't restart and shutdown the phone (or I need to do soft reset).
I tried to do a factory reset directly from Android but it doesn't work.
I tried to flash TWRP and and I got this message.
Code:
Y:\Download>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15864 KB) OKAY [ 0.512s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.204s]
Finished. Total time: 0.919s
According to other subjects it's not a big deal so I decided to restart in bootloader but now I'm stuck on TWRP logo. I waited more than 1h30 and nothing happens.
Have you got an idea ?
Thank you
Do a clean flash of the stock ROM.
Thank you, it works, and I was able to reinstall AOSP.
Thank you again

Categories

Resources