Related
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?).
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I want to get the latest android available for my HTC M8 (AT&T). I'm currently on Android 4.4.2. I have an mdnsd battery drain bug, and the bluetooth has a bug that causes it to break whenever I get around too many bluetooth devices.
I've tried flashing to TWRP, flashing back to the factory recovery, multiple RUU files, and a SkyDragon ROM. All either don't update or cause a boot loop, and I end up doing a nandroid restore to my old ROM.
I get the impression that I need the correct version of the boot loader, which is included in the right firmware.zip file. I've tried to find the right file, but when I go to the mike1986 page to download the firmware, I'm not sure which version to try. What is the latest official firmware that will work for my phone, and what is the latest official version of Android I can update to?
Any help is greatly appreciated!
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
ckpv5 said:
Read this - https://forum.xda-developers.com/showthread.php?t=2751432
and this - https://forum.xda-developers.com/att-htc-one-m8/general/marshmellow-update-t3379303
everything that you need is there.
The latest version is Marshmallow 6.20.502.5
Click to expand...
Click to collapse
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
kentuckythrash said:
Thanks! I notice that the firmware isn't flashing, either hanging indefinitely or giving an error message:
C:\adb>fastboot flash zip fw_6.20.502.5.zip
target reported max download size of 1772113920 bytes
sending 'zip' (57092 KB)...
OKAY [ 2.585s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.924s
Do I have to have S-off? I was trying to get around paying $25 for the software.
Click to expand...
Click to collapse
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
ahmed.ismael said:
repeat the flashing command immediately after you see this error
no need for s-off to flash signed firmware only relocked/locked bootloader
Click to expand...
Click to collapse
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
kentuckythrash said:
Thanks! I ended up getting the " FAILED (remote: 90 hboot pre-update! please flush image again immediately)" multiple times, apparently going 7/8s of the way through. I ended up trying the RUU, and it got much further and right now has been on "Updating...(1/1) Sending...." for about 20 minutes. The same window has "Remember, the operation will take about 10 minutes." Should I keep waiting or try the RUU again? I don't know if it's hung or not, and there's no real progress meter.
Click to expand...
Click to collapse
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
ahmed.ismael said:
actually in my first respond i was mistaken about the error 99
i was talking about error 90 sorry about that
now wait for the RUU to complete the process or return with an error
if something changed please post it here
Click to expand...
Click to collapse
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
kentuckythrash said:
It's been an hour and no change... should I let it continue? Seems like it should have finished by now.
Click to expand...
Click to collapse
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
what is the current status for the phone ?
If the flashing didn't start then try to flash the firmware again
Another question : did you relocked the bootloader ?
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
kentuckythrash said:
The phone screen has the htc gradient logo. The bootloader is relocked.
I've attached an image of the ROM update window.
Click to expand...
Click to collapse
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Ok open cmd window and type
fastboot reboot-bootloader
Then flash the firmware
From where you got the firmware ?
and try with another USB 2 port don't use USB 3 type
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
kentuckythrash said:
I got the firmware from:
https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU
I tried the 'fastboot reboot-bootloader' command and see:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
and it won't go past that point.
Click to expand...
Click to collapse
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
Close the RUU setup wizard if it still didn't flash anything or hanging on the same screen
And restart your pc then try to flash the firmware again on the device ( as it's on RUU mode )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
kentuckythrash said:
Thanks for your prompt responses! I managed to successfully update the firmware, seeing a completed message in the command prompt, and green bar on the HTC screen. However, now I'm still stuck on "
Updating...(1/1) Sending.......
Updating the ROM image on your Android phone...
"
I've rebooted my workstation and the phone multiple times. Not sure where to go from here.
Click to expand...
Click to collapse
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
another solution you can extract the rom.zip from the RUU.exe
By start it and goto %temp% folder and you will find rom.zip
Here what you need to do
press ctrl+r and type %temp% it will open a folder,delete everything in this folder
start the RUU.exe again,once it starting and hang goto %temp% folder again you will find a folder and the rom.zip inside it copy it and flash using fastboot or
rename it to 0P6BIMG.zip and put it in your sd card ( formatted as fat32 ) then reboot into bootloader the update process should start automatically
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
kentuckythrash said:
OK. There were 2 .zip files, rom_01.zip and rom_02.zip. Here's what happened when I tried to flash each:
--------------------------------------------------------------------------------
C:\adb>fastboot flash zip rom_01.zip
target reported max download size of 1826418688 bytes
sending 'zip' (493 KB)...
OKAY [ 0.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) total_image_number=1
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
OKAY [ 2.260s]
finished. total time: 2.480s
C:\adb>fastboot flash zip rom_02.zip
target reported max download size of 1825775616 bytes
sending 'zip' (1584998 KB)...
OKAY [ 48.647s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 106.973s
C:\adb>
--------------------------------------------------------------------------------
So I guess the problem is the FAILED "remote:12 signature verify fail"
Click to expand...
Click to collapse
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
rom_02 rename it to 0P6BIMG.zip and put it in your sd card and reboot to bootloader,have you tried to do that ?
rom_01 is hboot as shown in the output
rom_02 supposed to be the RUU
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
That worked! Thank you very much for your help. These M8s are really hard to update!
kentuckythrash said:
That worked! Thank you very much for your help. These M8s are really hard to update!
Click to expand...
Click to collapse
Not hard but tricky
Glad i helped
Sent from my HTC M8 using XDA Labs
Good day everyone.
After two weeks of trying and searching the web for an answer I have finally given up and decided to post my question here, perhaps someone has an idea that can help.
I have an HTC One M9 that was stashed away in a cupboard, I decided that I am going back to it as my current phone is just not working for me, however, I LOVE the hardware on the One M9 but I do not like the HTC Sence UI and decided that I will flash it with a custom ROM. Needless to say I completely stuffed it up. (I probably should have S-OFF and unlocked before I tried flashing. (Also didn't enable developer options or USB debugging - stupid stupid me)
Herewith the symptom. I can boot into download mode but not recovery, when i boot into recovery the black HTC logo appears and then disappears, appears, disappears etc etc so ABD does not work.
I have tried the RUU route but as soon as the installer reboots the phone it does the whole black logo loop thing. the get_identifier_token command also returns bank (see output below) so can't even use the htcdev procedure.
I have tried manually flashing zip and img files and get a 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCK also tried flashing stock recovery.img rom.
Rom:
M9_3.35.401.12_FullStock_wipe.zip
M9_3.35.401.12_NoWipe_TWRP2871b1.zip
0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
RUU_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.17_Ra dio_01.01_U11440261_56.02.50306G_2_F_release_42934 0_signed_2_4.exe
Manually flashing with extracted rom in RUU file
hima_uhl_n70_hosd_signed.img
HTC_One_M9_1.32.401.8_recovery_signed.img
twrp-3.2.1-0-hima.img
Used the SDCARD option
I did the fastboot erase cache process
At some point I was able to htc_fastboot flash zip rom.zip and it sent up to 50% but just remained there
Original Software
LOCKED
S-ON
htc_fastboot "works"
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXX
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__016
all:
finished. total time: 0.004s
htc_fastboot finished. total time: 1.143s
flash example:
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe flash zip d:\roms\M9_3.35.401.12_FullStock_wipe.zip
htc_fastboot.exe v3.0.7 (2015-03-30)
target reported max download size of 800000000 bytes
sending 'zip' (134610 KB)...
OKAY [ 8.962s]
writing 'zip'...
(bootloader) HOSD CL#671758
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 10.121s
htc_fastboot finished. total time: 12.576s
D:\Desktop\HTC\HTC One M9 Toolkit 2 1.6.1\adb>htc_fastboot.exe oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.162s]
finished. total time: 0.162s
htc_fastboot finished. total time: 1.335s
Please help or even tell me I am doing something wrong.
Thank you
The only ruu you can flash with s-off is this: 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
So, don't try another ruu, they will never work.
You just need to rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download and follow on-screen instructions.
The second method is with htc_fastboot.
Boot in download and do "htc_fastboot flash zip 0PJAIMG_HIMA......zip" - do the same command again when it asks(phone reboots itself in download mode).
After the process is complete do "fastboot reboot".
lucyr03 said:
The only ruu you can flash with s-off is this: 0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.1 2_Radio_01.01_U11440792_97.00.51203G_F_release_sig ned.zip
So, don't try another ruu, they will never work.
You just need to rename the zip to 0PJAIMG.zip and put in the root of your fat32 formatted sdcard.
Then boot in download and follow on-screen instructions.
The second method is with htc_fastboot.
Boot in download and do "htc_fastboot flash zip 0PJAIMG_HIMA......zip" - do the same command again when it asks(phone reboots itself in download mode).
After the process is complete do "fastboot reboot".
Click to expand...
Click to collapse
Hi, thanks, however, I did that previously no luck, problem is that S is on and I never enabled USB Debug before I started
neetekweet said:
Hi, thanks, however, I did that previously no luck, problem is that S is on and I never enabled USB Debug before I started
Click to expand...
Click to collapse
Neither being S-ON nor not having enabled the USB debugging prevents you from flashing a RUU that has the same firmware version as your phone.
If flashing the RUU that lucyr03 mentioned fails then you need to check whether the MD5 checksum of the downloaded file is correct and whether your SD card is broken.
Sent from my HTC One M9 using XDA Labs
Probably wrong firmware. You need a stock signed zip of 3.35.401.12 and use the sdcard method.
shivadow said:
Probably wrong firmware. You need a stock signed zip of 3.35.401.12 and use the sdcard method.
Click to expand...
Click to collapse
Hi
Thank you kindly, tried with Lucy's and a few others on the sdcard method.
Its starts the process "updating_ui" it reboots and then it just starts looping again.
I have basically given up, I am going to try one more thing and that is to take it to a repair shop and see if they can fix it.
neetekweet said:
Hi
Thank you kindly, tried with Lucy's and a few others on the sdcard method.
Its starts the process "updating_ui" it reboots and then it just starts looping again.
I have basically given up, I am going to try one more thing and that is to take it to a repair shop and see if they can fix it.
Click to expand...
Click to collapse
I can tell you now the phone is bricked.
Hey, guys,
my 10 is s-on and locked and starts only in bootloader or download mode, token query does not work, says oem locked.
I think the only option is a ruu.exe or ruu.zip.
here's the problem.
cid is htc__102 and I can't find an appropriate one anywhere, does someone have a link for me or another solution?
I hope you can help me.
wolfi05 said:
Hey, guys,
my 10 is s-on and locked and starts only in bootloader or download mode, token query does not work, says oem locked.
I think the only option is a ruu.exe or ruu.zip.
here's the problem.
cid is htc__102 and I can't find an appropriate one anywhere, does someone have a link for me or another solution?
I hope you can help me.
Click to expand...
Click to collapse
You start with looking at your OS/Firmware line in the download mode, then search here for the corresponding RUU. I bet if you use the search box you will definitely find it. I can so you can too.......
Verstuurd vanaf mijn HTC 10 met Tapatalk
Mr Hofs said:
You start with looking at your OS/Firmware line in the download mode, then search here for the corresponding RUU. I bet if you use the search box you will definitely find it. I can so you can too.....
Click to expand...
Click to collapse
If it were that simple .......
the cid is htc__102 .......
the firmware is 1.30.401.1........
the only thing I could find would be a cid o2__102, does this fit...... .
So if you had a match, I'd be very grateful.
wolfi05 said:
If it were that simple .......
the cid is htc__102 .......
the firmware is 1.30.401.1........
the only thing I could find would be a cid o2__102, does this fit...... .
So if you had a match, I'd be very grateful.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=818070582850508041
Mr Hofs said:
[ww.androidfilehost.com/?fid=818070582850508041[/url]
Click to expand...
Click to collapse
mmmmmm.........
actually, that's a htc__034 , do you think this is gonna work?
i have slow internet and i have to think very carefully about what i download
wolfi05 said:
mmmmmm.........
actually, that's a htc__034 , do you think this is gonna work?
i have slow internet and i have to think very carefully about what i download
Click to expand...
Click to collapse
Don't look at cid, this version is just like yours the WWE version. Look at your firmware region number the. 401 part. I would not have linked this if it would be the wrong one
Mr Hofs said:
Don't look at cid, this version is just like yours the WWE version. Look at your firmware region number the. 401 part. I would not have linked this if it would be the wrong one
Click to expand...
Click to collapse
first of all thank you for your support.................
fastboot says about the file:
\fastboot-win> .\htc_fastboot flash zip 2PS6IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.41.401.41
found large-zip header, file count: 25
processing file 1/25...
sending 'zip' (108173 KB)...
OKAY [ 5.272s]
writing 'zip'...
(bootloader) HOSD CL#738269
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 8.942s
htc_fastboot finished. total time: 10.833s
I tried another ruu.exe with the same version number, with the same result.
I think I need a htc_102 otherwise it won't work.
I'm missing something?
wolfi05 said:
first of all thank you for your support.................
fastboot says about the file:
\fastboot-win> .\htc_fastboot flash zip 2PS6IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.41.401.41
found large-zip header, file count: 25
processing file 1/25...
sending 'zip' (108173 KB)...
OKAY [ 5.272s]
writing 'zip'...
(bootloader) HOSD CL#738269
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 8.942s
htc_fastboot finished. total time: 10.833s
I tried another ruu.exe with the same version number, with the same result.
I think I need a htc_102 otherwise it won't work.
I'm missing something?
Click to expand...
Click to collapse
I told you it's the correct one, HTC 102 is the same firmware as HTC 34 or any other WWE firmware, it stands for the European firmware. You can't flash any other. Of you look at the O2 102 cid you will also see that it's a completely different firmware number and that there is NO .401 in it because it's a carrier locked firmware.
The only thing that is possible is that the jump from 1.30.401 to 2.41.401 is to big, you might need a 1.90.401 or 1.30.401 ruu first as the 1.30.401 is VERY old !
Do this :
Put the 2.41 RUU on your sdcard and boot into the download mode (file named as 2PS6IMG.ZIP) and flash the file. See if that works.
Believe me i know what i am talking about......
Edit 1 :
Please post the outcome of :
Fastboot getvar all
Paste the whole outcome EXCEPT the imei and serial number.
Edit 2 :
https://www.androidfilehost.com/?fid=24533103863140111
https://www.androidfilehost.com/?fid=24671318762849319
2 other RUU zips you can try.
fastboot getvar all :
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) imei: 0000000000000000
(bootloader) version-main: 1.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__102
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.342s
When I start in download mode the 2PS6img should be found, or?
It says "file not found" on the display of the htc.
so far I have tried this without success:
2PS6IMG......1.30.401.
2PS6IMG......1.80.401.
..............................2.41.401.
RUU.....2.41.401
flash with the 2PS6img on my pc:
.\htc_fastboot flash zip 2PS6IMG.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 2.41.401.41
found large-zip header, file count: 25
processing file 1/25...
sending 'zip' (108173 KB)...
OKAY [ 5.250s]
writing 'zip'...
(bootloader) HOSD CL#738269
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 6.296s
htc_fastboot finished. total time: 8.139s
wolfi05 said:
fastboot getvar all :
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) imei: 0000000000000000
(bootloader) version-main: 1.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__102
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.342s
When I start in download mode the 2PS6img should be found, or?
It says "file not found" on the display of the htc.
so far I have tried this without success:
2PS6IMG......1.30.401.
2PS6IMG......1.80.401.
..............................2.41.401.
RUU.....2.41.401
Click to expand...
Click to collapse
Be careful you didn't name the file .zip.zip as windows automatically hides extensions.
And yes download mode should autodetect them
And these are absolutely the correct files.
Mr Hofs said:
Be careful you didn't name the file .zip.zip as windows automatically hides extensions.
And yes download mode should autodetect them
And these are absolutely the correct files.
Click to expand...
Click to collapse
so stay try and error..................
wolfi05 said:
so stay try and error..................
Click to expand...
Click to collapse
Try them all with the sdcard method, 1 by 1. I can't offer anything else as this what you need. If the download mode doesn't detect the file you named it wrong.
Mr Hofs said:
Try them all with the sdcard method, 1 by 1. I can't offer anything else as this what you need. If the download mode doesn't detect the file you named it wrong.
Click to expand...
Click to collapse
I have formatted the sd card at the pc and only the zip on it, zip.zip in no case
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode) <<---- which means?
Which fastboot version would you recommend?
The problem with the sd card has been solved. There was a hidden partition of samsung on it. After reformatting the htc recognizes the file.
Okay, I tried them 1 by 1
Always with the same result :
"Fail 7 RU_CID_FAIL cid in androidinfo mismatched"
.........
Then the last method to update is to flash the 2.41.401 standalone firmware (not the RUU), locate it, download it, OPEN the firmware.zip with 7zip and drag out android info.txt, edit the file and add your CID (HTC__102) save the text and flash the firmware via fastboot. Be aware that your device has to be in RUU mode. After you flashed the firmware you should be able to flash the full 2.41.401 RUU.
That's all i can think of. You should have updated your phone long way back then you would not have this problem. Your current OS is like the stoneage is in time ! For all i know it has something to do with the problem why it only starts to bootloader and/or download mode, maybe the problem is bigger than just to flash a RUU.
wolfi05 said:
The problem with the sd card has been solved. There was a hidden partition of samsung on it. After reformatting the htc recognizes the file.
Okay, I tried them 1 by 1
Always with the same result :
"Fail 7 RU_CID_FAIL cid in androidinfo mismatched"
.........
Click to expand...
Click to collapse
Ok, as last way I will try. . . . . . but just to understand it, the new firmware doesn't change the cid, then the ruu doesn't care the cid?
I have entered the cid htc__102 in the ruu and it has aborted.
I will report...thanks
wolfi05 said:
Ok, as last way I will try. . . . . . but just to understand it, the new firmware doesn't change the cid, then the ruu doesn't care the cid?
I have entered the cid htc__102 in the ruu and it has aborted.
I will report...thanks
Click to expand...
Click to collapse
You can't change a cid in the RUU, unless you decrypt it ? A firmware can't change your cid because your device is S-ON. Only with s-off you can change the cid.
I told you to change the Android info.txt file which is inside the firmware (not the RUU) so that the firmware knows your cid is supported.
Mr Hofs said:
You can't change a cid in the RUU, unless you decrypt it ? A firmware can't change your cid because your device is S-ON. Only with s-off you can change the cid.
I told you to change the Android info.txt file which is inside the firmware (not the RUU) so that the firmware knows your cid is supported.
Click to expand...
Click to collapse
You may have to flash hosd_signed.img at bootloader (not download) before you flash the firmware. Extract the hosd_signed.img from the firmware zip and do 'fastboot flash hosd hosd_signed.img' in the bootloader mode; followed by flashing the firmware in the download mode.
rln_xda said:
You may have to flash hosd_signed.img at bootloader (not download) before you flash the firmware. Extract the hosd_signed.img from the firmware zip and do 'fastboot flash hosd hosd_signed.img' in the bootloader mode; followed by flashing the firmware in the download mode.
Click to expand...
Click to collapse
No that's not needed because this is not about downgrading the bootloader/firmware. That's only needed when you want to downgrade the firmware on an S-ON device.
Edit :
To Wolf
Here is the 130.401 to 180.401 firmware.
https://androidfilehost.com/?fid=24591020540821778
Open the firmware (NOT EXTRACT) and drag out the Android info txt file and edit in your exact CID. Save it and drag it back in the firmware.zip. then flash the zip as intended. Please check how to properly flash the firmware for a S-ON device.
i believe you have to enter RUU mode first before you can flash it so please check that out !!!
//You can't change a cid in the RUU, unless you decrypt it ? //
I started the ruu, then I went to the temp folder and changed the android-info, then I started the htc and started the flash process (it was worth a try)
//A firmware can't change your cid because your device is S-ON. Only with s-off you can change the cid. //
That's probably it....that's why I wonder why the ruu should work with another firmware(because the cid error always comes) and if the flashing of the firmware works, but the ruu doesn't, then the htc is an organ donor (more than now)?
now I'm confused:
firmware 1.8 ---> firmware 2.41 -----> Ruu 2.41 or
firmware 1.8 ----> Ruu 2.41 or
firmware 2.41 ---> Ruu 2.41 how would you do that?
So, like I found in another threads my old phone, has not sound at all. I tried to fix it years ago, with not luck, but I wanna give it another chance since still it's a great phone.
This is my getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---------
(bootloader) imei: ----------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing. It's UNLOCKED.
If anyone would give me a hand with this, would be awesome.. since my actual phone is broke, like my wallet. :crying:
Thanks! :fingers-crossed:
Stranyer said:
I tried almost everything, it's currently S-ON, I tried a millon times going S-OFF with HTCDev steps, but nothing.
Click to expand...
Click to collapse
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
redpoint73 said:
HTCDev is not a process to get s-off. It is a process to unlock the bootloader (but you say it's already UNLOCKED). Sunshine is the only valid method to s-off. You can try anything else a billion times, and it will never work.
You most likely also do not need s-off to get the phone working properly again.
I have a feeling that no sound is due to outdated firmware, possibly in conjunction with a custom ROM (ROM - firmware mismatch).
My suggestion, try to relock the bootloader (command: fastboot oem lock) then the following RUU:
http://gsm-firmware.com/index.php?a=downloads&b=file&id=14070
The RUU will wipe all personal data on the phone.
Click to expand...
Click to collapse
Hey thanks for replying!
I tried that, I keep getting this error
Code:
target reported max download size of 1826418688 bytes
sending 'zip' (1734001 KB)...
OKAY [ 49.344s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 112.683s
I tried doing a reboot and reinstaling.. but still getting error 12 :/
Any clue?
Stranyer said:
I tried that, I keep getting this error
Code:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
redpoint73 said:
"Signature verify fail" usually means the bootloader is unlocked. Did you relock the bootloader as I advised (mandatory in order to install the RUU)? Or if you did, can you verify is says RELOCKED near the top of the bootloader screen?
Click to expand...
Click to collapse
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Stranyer said:
Yeah, I did relocked the bootloader. And it does says RELOCKED.
Click to expand...
Click to collapse
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
ckpv5 said:
I believe you need to flash 6.13.631.7 firmware first before you can install the RUU
https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Also you need htc_fastboot to fastboot flash RUU zip
Click to expand...
Click to collapse
redpoint73 said:
Good point, and makes sense, as most of the US M8 variants require firmware to be flashed for Marshmallow RUU. Even though Rogers is Canadian, that version tends to follow the same rules as the US versions!
Click to expand...
Click to collapse
Sorry I took long time to reply.
I tried flashing the firmware, using htc_fasboot and fastboot. Both will give me this error.
Code:
c:\adb>htc_fastboot flash zip fw.zip
sending 'zip'... (53849 KB) OKAY
sending time = 2.408 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILnot allowed
FAILED (remote: not allowed)
Execution time is 5(s)
And still, won't flash RUU.zip
----
I retried a few more times, and it worked! It flashed firmware and ruu
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Stranyer said:
But now is stuck on HTC logo boot. Won't let install a rom over fastboot :/
Code:
sending 'zip'... (360264 KB) OKAY
sending time = 10.763 secs
writing 'zip'... FAILnot allowed
FAILED (remote: not allowed)
Execution time is 11(s)
Click to expand...
Click to collapse
Hard to tell exactly what you tried to do here, since you didn't include the actual command, name of the file you tried to flash, etc. Always include as much specific info as possible. "install a rom" is not sufficient info.
You tried flashing a custom ROM over fastboot? If so, that isn't the proper way to flash a custom ROM. You need custom recovery (TWRP) to do that. So that is the reason for "not allowed" (since it isn't).
But before doing so, we should look closer at the RUU (why it isn't booting) first. Since installing TWRP requires unlocking the bootloader, etc. Better to eliminate the RUU as a solution first, so we don't have to keep going back and forth unlocking/relocking bootloader.
Did the RUU finish successfully without any errors? If there were errors, what did it say specifically? If you don't know the answers to those questions, you can run the RUU again. Even cut/paste the output so we can look at it.