Please, My M9 Is usually on a same boot loop situation.
When I start it it shows just this screen
Software status MODIFIED
LOCKED
S-ON
Security warning (Sometimes it disappear)
REBOOT
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
POWER DOWN
Phone not detected to use adb commands.
Please, I need this phone and I donn't have a warranty.
There is no solution to go out from this screen? There is no software to force flash or flash a dead phone.
There is no hardware tweak to bypass this situation...I don't know anything please.
Please my friends Help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
freshmike said:
I have exactly the same
Click to expand...
Click to collapse
Sadly, I have exactly the same answer. Sorry, but you're probably out of luck.
computerslayer said:
I'm sorry to report that this is almost assuredly a hardware failure (dead chip on your motherboard).
You could contact one of the repair services listed in the readme thread or HTC itself, but if a repair is possible - and it may not be - you'll have to pay for someone to help with this level of problem.
Click to expand...
Click to collapse
Thank you very much
Just to clarify, status modified on a non rooted, bootloader locked, s-on, never touched phone most likely means a dead nand which is unrecoverable.
Beamed in by telepathy.
my phone is S-ON unlocked .
Today my phone turn off and after stay on boot loop . When i try go to recovery mode or download mode just restart to fastboot.
I connect to computer but only what i can get after command: fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT558YJ00694
all:
I think my nand memory is F...ck ?
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
shivadow said:
If you're s-on, never modded, bootloader locked and your phone won't boot, won't do anything except boot loop.. Borked nand.
Beamed in by telepathy.
Click to expand...
Click to collapse
I do not know if it's worth repairing on htc. Used on ebay 150 €.
freshmike said:
I have exactly the same:
Software status MODIFIED
LOCKED
S-ON
Boot to bootloader (When I chose this option phone restart and come back to the same screen so nothing)
Boot to download mode (result: failed to boot to download mode press volumt up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volumt up or down...)
the only thing that works is:
D:\Incomming>fastboot devices
FA54LYJ00638 fastboot
I'm was running Stock HTC__001. Any idea what could be done ?
Thanks for any help
Click to expand...
Click to collapse
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
obywatel2x said:
I do not know if it's worth repairing on htc. Used on ebay 150 €.
Click to expand...
Click to collapse
Consider Swappa as well - good prices and often it's XDA users (who care more about caring for their phones) upgrading/changing phones & selling their old ones.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
If the phone is assuredly duff then I'd try this too, even if I'm yet to know of an instance where it actually worked.. Either that or smack it one time with something really heavy. It won't fix it but you'll feel better!.
Beamed in by telepathy.
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
freshmike said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Tried this:
D:\Incomming>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:FA54LYJ00638
D:\Incomming>fastboot flash hosd hosd_signed.img
target reported max download size of 536870912 bytes
sending 'hosd' (33344 KB)...
OKAY [ 1.063s]
writing 'hosd'...
OKAY [ 0.821s]
finished. total time: 1.884s
Nothing has changed. Still same, can't get to bootloader nor downlaod mode, nor recovery.
Click to expand...
Click to collapse
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
blueberry60 said:
If you can type "fastboot devices" on bootloader mode and output of command is just like above that, extract hosd.img from your last original firmware.zip and flash it via bootloader mode:
Code:
fastboot flash hosd hosd_signed.img
you might be able to boot DL mode again.
Don't forget to copy "hosd_signed.img" file into fastboot folder of your PC.
Click to expand...
Click to collapse
blueberry60 said:
This is a good new, at least it writes hosd.ımg and last chance for you need to be done:
Extract all img files from firmware.zip below that and flash them one by one:
Code:
fastboot flash partition gpt_main_32g.img
fastboot flash aboot aboot_signed.img
fastboot flash boot boot.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash rfg_1 rfg_1.img
fastboot flash rfg_2 rfg_2.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
If you succeed to get into download mode flash firmware.zip via download mode:
Code:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
freshmike said:
Well, I guess no luck
D:\Incomming\ROM>fastboot flash partition gpt_main_32g.img
target reported max download size of 536870912 bytes
sending 'partition' (17 KB)...
OKAY [ 0.047s]
writing 'partition'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 0.063s
Click to expand...
Click to collapse
Have you flashed other img files?
blueberry60 said:
Have you flashed other img files?
Click to expand...
Click to collapse
Yes, none of them went though. All command report you need to be s-off
FAILED (remote: cannot flash this partition in s-on state)
The only one which worked was hosd_signed.img, but that didn't change anything in the state of the phone.
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
freshmike said:
is there another way to s-off without going though HTCDev ?
as this ain't working:
D:\Incomming\ROM>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.014s
Click to expand...
Click to collapse
You are in download mode?
sipas4 said:
You are in download mode?
Click to expand...
Click to collapse
Boot to bootloader (When I chose this option phone restart and come back to the same screen does nothing)
Boot to download mode (result: failed to boot to download mode press volume up or down...)
Boot to recovery mode (result: failed to boot to recovery mode press volume up or down...)
Looks like bootloader/recovery/download mode have been wiped out from the OTA update.
Related
Hi all, I have a big problem with my htc one m9. Today I was trying to get in recovery mode but the phone was rebooting itself, so I tryed to flash a ruu (via oem rebootRUU) but maybe something went wrong (hboot pre-update) and now the phone reboots when I try to enter in download mode via bootloader and also I canno't enter in "oem rebootRUU".
I have S-OFF.
Someone can help me? Thanks..
Insaniity said:
Hi all, I have a big problem with my htc one m9. Today I was trying to get in recovery mode but the phone was rebooting itself, so I tryed to flash a ruu (via oem rebootRUU) but maybe something went wrong (hboot pre-update) and now the phone reboots when I try to enter in download mode via bootloader and also I canno't enter in "oem rebootRUU".
I have S-OFF.
Someone can help me? Thanks..
Click to expand...
Click to collapse
can you provide more information please, (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n), but since you can't get to download mode, can we have some screenshots of bootloader, a copy/paste of your command prompt output when typing the fastboot commands
and most important, what were you trying to flash (link to thread and file please)
nkk71 said:
can you provide more information please, (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n), but since you can't get to download mode, can we have some screenshots of bootloader, a copy/paste of your command prompt output when typing the fastboot commands
and most important, what were you trying to flash (link to thread and file please)
Click to expand...
Click to collapse
I can do all command on bootloader so :
C:\minisdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno: FA54SYJ03650
all:
Insaniity said:
I can do all command on bootloader so :
C:\minisdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno: FA54SYJ03650
all:
Click to expand...
Click to collapse
that's what I meant with "usually" (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n, but since you can't get to download mode)
on the M9, the "fastboot getvar all" informational data, comes from download mode, not bootloader, so unfortunatly the above is quite useless,
let's go back to
* some screenshots
* copy/paste of fastboot commands (fastboot devices, fastboot oem rebootRUU, fastboot oem reboot-download)
EDIT: and what were you trying to flash (link to thread and file please)
nkk71 said:
that's what I meant with "usually" (usually I'd ask for a "fastboot getvar all" excluding IMEI and s/n, but since you can't get to download mode)
on the M9, the "fastboot getvar all" informational data, comes from download mode, not bootloader, so unfortunatly the above is quite useless,
let's go back to
* some screenshots
* copy/paste of fastboot commands (fastboot devices, fastboot oem rebootRUU, fastboot oem reboot-download)
Click to expand...
Click to collapse
Ok, I managed to get into download mode by writing this in bootloader mode ( I used the firmware 2.10.401.x )
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash cota cota.img
fastboot flash cpe cpe.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash modem_st1 modem_st1.img
fastboot flash modem_st2 modem_st2.img
fastboot flash persist persist.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
This is getvar
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.17
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
It is very strange, If i try to flash another firmware, for example 1.32.401.xx, after flashing I can't get to download mode again.
Insaniity said:
fastboot flash aboot aboot_signed.img
fastboot flash adsp adsp.img
fastboot flash cota cota.img
fastboot flash cpe cpe.img
fastboot flash hosd hosd_signed.img
fastboot flash hyp hyp-8994-1.img
fastboot flash modem_st1 modem_st1.img
fastboot flash modem_st2 modem_st2.img
fastboot flash persist persist.img
fastboot flash pg2fs pg2fs_ship_signkey.img
fastboot flash pmic pmic-8994-1.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash rpm rpm-8994-1.img
fastboot flash sbl1 sbl1-8994-1.img
fastboot flash sdi sdi.img
fastboot flash sensor_hub sensor_hub.img
fastboot flash tz tz-8994-1.img
This is getvar
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.32.401.17
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
It is very strange, If i try to flash another firmware, for example 1.32.401.xx, after flashing I can't get to download mode again.
Click to expand...
Click to collapse
Please dont do firmware/low-level stuff that way, unless you are sure what you're doing
baseband has been updated to 2.10.401.1 firmware, obviously version-main wont reflect that change since it's not a "proper" flash... and serisously don't mess with "fastboot flash aboot, hosd, sbl, etc" .... you're heading into trouble
stop rushing things, relax, and take it one step at a time (slowly)
nkk71 said:
Please dont do firmware/low-level stuff that way, unless you are sure what you're doing
baseband has been updated to 2.10.401.1 firmware, obviously version-main wont reflect that change since it's not a "proper" flash... and serisously don't mess with "fastboot flash aboot, hosd, sbl, etc" .... you're heading into trouble
stop rushing things, relax, and take it one step at a time (slowly)
Click to expand...
Click to collapse
Ok, now I'm here.
C:\minisdk>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
I can access only to download mode and my firmware is ok.
It is matching with the download mode.
What should I do now?
Insaniity said:
Ok, now I'm here.
C:\minisdk>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.10.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__031
all:
I can access only to download mode and my firmware is ok.
It is matching with the download mode.
What should I do now?
Click to expand...
Click to collapse
I'd recommend taking a break; I have no idea how you got there, because you keep forgetting that we need to know what you are flashing and how
for example, this is me flashing my firmware:
http://forum.xda-developers.com/showpost.php?p=62552232&postcount=646
and how I choose to copy/paste my information
^^ you don't need to follow those steps, I'm just saying you're going from:
I'm at location D ... okay now I'm at location K ... you're probably doing just fine, but not saying what and how you are flashing, it's difficult to help
nkk71 said:
I'd recommend taking a break; I have no idea how you got there, because you keep forgetting that we need to know what you are flashing and how
for example, this is me flashing my firmware:
http://forum.xda-developers.com/showpost.php?p=62552232&postcount=646
and how I choose to copy/paste my information
^^ you don't need to follow those steps, I'm just saying you're going from:
I'm at location D ... okay now I'm at location K ... you're probably doing just fine, but not saying what and how you are flashing, it's difficult to help
Click to expand...
Click to collapse
I know how to flash a firmware....
Now I'm tryng to flash a RUU
Insaniity said:
I know how to flash a firmware....
Now I'm tryng to flash a RUU
Click to expand...
Click to collapse
fine, have it your way
flashing RUU is exactly the same procedure as flashing firmware
but you continuously refuse to say, what you are flashing or how, if you look at my first reply, I asked for more details, including what you are trying to flash ("link to thread and file please")
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I see some things change and some things never do
as a final hint (dont know if that's the case or not, since you wish not to share, the information), in a word: htc_fastboot.exe (try version 3.0.9.2)
do you try the ruu.exe or the zip? it will be MUCH better to use the zip. also mostly only the zip seems to work
DeeZZ_NuuZZ said:
...also mostly only the zip seems to work
Click to expand...
Click to collapse
elaborate, thank you
I have something similar, I flashed NoRedTxt_Aboot+2.11.531.19 once in my m9 tmo. Supposlly it flashed good. Now I can't get to download mode or ruu mode. In ruu mode after 1 sec it gets me back to download mode. Which is where it takes me everytime, besides that twrp is the other place I ca go too.
---------- Post added at 11:51 AM ---------- Previous post was at 11:44 AM ----------
Insaniity said:
Hi all, I have a big problem with my htc one m9. Today I was trying to get in recovery mode but the phone was rebooting itself, so I tryed to flash a ruu (via oem rebootRUU) but maybe something went wrong (hboot pre-update) and now the phone reboots when I try to enter in download mode via bootloader and also I canno't enter in "oem rebootRUU".
I have S-OFF.
Someone can help me? Thanks..
Click to expand...
Click to collapse
I'm stuck in same place as you. But different reason.I'm running stock 2.11.531.19 tmo m9. Just twrp s off and unlocked. What can I do to get to work again ruu or download again
Hello Guys,
I have a problem with my HTC M9 prime Camera Edition yesterday I paid 25 $ for S-Off with sunshine App everything was working great (great App thanks)
after that my phone was S-OFF i was excited and wanted to flash a other Stock Rom but something went wrong and my download mode is deleted now or not more availlable.
Information about my Phone: HTC_Himar 128 SHIP S-OFF
before CID was HTC__034 CID
before MID was 2PRG10000 MID
LK-1.01.0000
OS-2.18.401.10
Bootloader UNLOCKED
The device is rooted and recovery is twrp-3.0.2-0-himar
Android version: marshmallow 6.0
What i did is i wanted to flash the 3.35.401.12-Firmware to change my stock i did it with renaming the file in 0PJAIMG.zip and flashing with sd card in download mode
file could be not flashed some zip error displayed i rebooted the phone everything was ok no problems after that.
I also changed the MID before flashing to: OPJA10000 and CID to HTC__J15. After that i wanted to try it again with the firmware from xda forum 3.35.401.12-Firmware.zip
Phone was flashing the file after that i rebooted and i opened the developer options to check the firmware info but the firmware stayed the same 2.18.401.10
and after that i wanted to reboot to Download mode but it seems after the last flash the Download mode is deleted or missing.
I can boot into Bootloader mode recovery twrp is working very fine system is working very fine everything is working just the problem is that i want the download mode back
but i can´t flash my stock rom without download mode. I was sitting yesterday half night and reading and searching for solutions and help, but withoud success so im now here and hope that someone of u guys
can help me to solve my problem. The thing is that i wanted to change my stock because i am not able with the 2.18.401.10 to flash any custom rom for the M9 nothing is working for example the viper rom
or cyanogenmode also the recovery name is different for my HTC M9 prime CE name is himar and on the M9 original is hima nothing is working for this phone..... please help
hi, i have the same probleme, but I can't flash anything, since My M9 have s-on :S
soo, I cant install a ruu exe, because it says low battery (by go to log_ruu I see it cant do adbdevices)
I can't enter in download mode, it jumbps to bootloader
I can do only some commands on fastboot, for exemple Fastboot oem get_identifier_token don't work, only in download mode (I can't go to download mode, because it doesnt exists)
I can't do comands by adb
C:\adb>fastboot flash zip M9_2.10.401.1_NoWipe_TWRP_2871b1_rename_to_ROM.zip
target reported max download size of 536870912 bytes
sending 'zip' (64024 KB)...
OKAY [ 1.418s]
writing 'zip'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.436s
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:MB523YJ06983
all:
finished. total time: 0.138s
Click to expand...
Click to collapse
C:\adb>Fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse
Guys ,pls share hosd_signed himaul img for m9.I don't have download,recovery mode with s on too..pls help me
Way forward
EclipseX said:
hi, i have the same probleme, but I can't flash anything, since My M9 have s-on :S
soo, I cant install a ruu exe, because it says low battery (by go to log_ruu I see it cant do adbdevices)
I can't enter in download mode, it jumbps to bootloader
I can do only some commands on fastboot, for exemple Fastboot oem get_identifier_token don't work, only in download mode (I can't go to download mode, because it doesnt exists)
I can't do comands by adb
Click to expand...
Click to collapse
Hi, were you able to fix this eventually?
Yeah, did send it to HTC without invoice. HTC change the entire motherboard for free
lubaid said:
Hi, were you able to fix this eventually?
Click to expand...
Click to collapse
I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .
What's your CID and latest ROM version? And what did you try to flash?
Dont know anything here... I dont know what was the ROM version at the time of root... now no information available... what can I do ...
When I try to flash anything via fastboot it says partion not exist
RUU also not working says battery is less than 30% but actually battery is full...
Does charging led turns green..
@Sneakyghost could help
cutecool said:
Does charging led turns green..
@Sneakyghost could help
Click to expand...
Click to collapse
no it doesnt... the battery icon comes up and then boot loop starts again...
Since you're in Qatar, you're probably on the 401 software. Did you get a software update in the last 2-3 weeks?
If not, download this: https://www.androidfilehost.com/?fid=24686681827312455
Relock your bootloader (fastboot oem lock), and flash this RUU (fastboot flash zip "name of zip").
If you got the recent update, then you're likely on 1.95, and you'll have to wait until there's an RUU, or take it to a service center.
This is as much help as I can give. Good luck.
I wouldn't lock the bootloader until you know your device fully boots.
Stephen said:
I wouldn't lock the bootloader until you know your device fully boots.
Click to expand...
Click to collapse
The 401 RUU zip won't flash on unlocked. This has been documented and I have gone through it myself. Do you have any alternate suggestions?
Why wouldn't you lock without a working system? My understanding is that unlocking via HTCdev would still be possible.
I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>
abidpioneer said:
I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .
Click to expand...
Click to collapse
You need to be in download mode then use the getvar all command. All fastboot commands are done in downlaod mode. How are you trying to flash RUU?
I am unable to use download mode..it says download mode failed in red
abidpioneer said:
I am unable to use download mode..it says download mode failed in red
Click to expand...
Click to collapse
You'll need a service center.
Yes. Service center. I don't think it's a brick since there's still a boot process but at this time I also wouldn't know how to force it to flash stuff, since it seems at least one vital partition is broken. So, call it a semi-brick with currently no way out...
Sorry that I can't offer any help here...
abidpioneer said:
I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>
Click to expand...
Click to collapse
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk
I will check dear..thanks
dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Click to expand...
Click to collapse
What is hosd.. ? Never heard about it...
I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...
abidpioneer said:
I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...
Click to expand...
Click to collapse
What happened? Did it flash successfully? Any errors?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Interesting facts there, mate. Thought you retired. Obviously I'm much more retired than you, considering I never knew HOSD is directly flashable like aboot...
Good to see you around!
(Besides, is it a true story that you retired? People were telling me that...)
I'll try my best to be as detailed as possible.
I have an HTC One M9 from Sprint. Custom rom on it, I believe it was either Viper Rom or BadBoyz. Running a TWRP PRE 3.0 recovery.
My phone had a pattern lock screen.
I had let the phone sit for about a month with out use, after which I attempted to turn it back on to use it, what I got was a continuous HTC loading screen. So I'm thinking no big deal, all I gotta do is boot into recovery and reflash it.
I boot into recovery, It won't format a number of partitions (I.E. data, system, cache) to allow the flash.
I follow instructions in this video:
with no luck, still won't flash.
So after a few hours of research and attempting different versions of twrp and cwm, it no longer has a bootable recovery. any TWRP 3.0 and up wouldn't run at all, no CWM recovery would run.
My understanding is that those partitions were encrypted and pre 3.0 for twrp can't handle the encryption or some such. I flash a few different versions, going from pre 3.0 to post 3.0, with post 3.0 still not booting but pre 3.0 booting.
THEN
After trying to flash back to a pre 3.0 twrp, it acts as it takes it, but when i go to boot into recovery i get:
"Failed to boot to recovery mode"
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\PropertyCO\twrp.img
target reported max download size of 800000000 bytes
sending 'recovery' (36288 KB)...
OKAY [ 3.063s]
writing 'recovery'...
(bootloader) HOSD CL#695981
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.562s]
finished. total time: 5.629s
is what fastboot returns, yet it won't boot to recovery.
So, my next attempt was to run an RUU.
RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.41
I run it, starting with my phone in download mode, RUU sees it just fine, goes to reboot into bootloader. with out assistance when it reboots it just brings up a metalic HTC logo and sits there, so when it reboots i'll hold volume up and down to get it to the boot loader. after some processing from the RUU it gives me the error 170 - USB connection error. Me thinking it's either some drivers messing it up or the cable, i try another laptop, and a series of different cables, no luck there.
I find out that I have to have the bootloader locked to run a RUU, so I attempt to relock the bootloader to see if that fixes the error.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
(bootloader) RELOCK device
OKAY [ 0.286s]
finished. total time: 0.287s
phone reboots, i force it into bootloader cause it doesn't automatically go to it, still says "*** UNLOCKED ***" up at the top.
fastboot getvar all:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himawhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) version-main: 3.41.651.4
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA20000
(bootloader) cid: SPCS_001
all:
finished. total time: 0.048s
Thanks in advance!
Edit:
Attempted the ZIP method in this forum and failed too:
https://forum.xda-developers.com/showthread.php?t=1928439
Your nand is corrupt. Dead phone.
Beamed in by telepathy.
I've been trying for days now to rollback but, finally, I found a solution (also posted on youtube with little adjustments):
- Download HTC_Version_Tool;
- Boot to TWRP Recovery;
- Download a stock Firmware (search on XDA) with android 6.0 (M60_Sense80);
- Change your OS version to the one that you're trying to rollback (for example from 3.16.401.2 to 1.30.401.1) using HTC version tool;
- Extract zip_0.zip from the Firmware zip (the firmware zip should look like this: "2PS6IMG_PE[email protected]60331.4_41.13_F_release_478442_combined_signed_2_4");
- Inside that zip, you will find an image called "hosd_signed.img" or "hosd_signedEU.img";
- Before flashing hosd image in bootloader, first flash the zip firmware in RUU mode (fastboot oem rebootRUU), you will get an error, don't panic;
- After the failed flash attempt, do fastboot reboot-bootloader, flash hosd image by fastboot flash hosd hosd_signed.img, reboot back to RUU mode and flash again the zip and VOILA!
The little adjustment I was talking about was that I couldn't flash 1.30.401.1 with its own hosd image, so instead I used the 1.21.401.4 hosd image. If upper instructions won't help you, do as I did.
I might help you occurring difficulties, if my time allows me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all, thank you !
I spent all day trying to downgrade from oreo to nougat and you came to the rescue.
I didnt exactly follow your steps but the hosd part was what made it all work for me.
So make it clear and for anyone who's finding a difficulty in downgrading here are my steps:
Prerequisites:
-HTC Drivers
-Adb Drivers
-HTC Version Tool
-Unlocked phone with stock Oreo installed,twrp and unlocked bootloader
-Firmware zip (I got mine from here https://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520 , download a full stock zip that corresponds to the SKU version you have and want to flash) > For example, my phone is PME UHL International 3.16.401.2 Oreo so I chose PME UHL International 2.41.401.3 Nougat.
-Stock Nougat RUU zip for your device. You need to search around for this one because there arent many sources for Nougat zips but mine was from here
-SD Card
Steps:
1. Boot into TWRP then connect your phone to your pc then open adb terminal and run HTC Version Tool then change to the version of the RUU youre going to flash.
2.Reboot into download mode then run
Code:
fastboot getvar all
make sure that the (version-main) is the one you changed. Then lock your bootloader with
fastboot oem lock
(This is to be able to flash the RUU)
3.Next, you have to flash the firmware zip so run
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip YOUR_FIRMWARE.zip
(If it gives error that's ok)
4.Open firmware zip then extract hosd_signed.img to adb directory then run
Code:
fastboot reboot-bootloader
Code:
fastboot flash hosd YOUR_HOSD.img
5.Reboot to RUUmode then flash firmware zip again
6.You need to put the RUU.zip you have in the sd card then rename it to "2PS6IMG.zip" ( Make sure its not 2PS6IMG.zip.zip) then reboot to download mode and choose to flash it (Vol up)
7.That should be it. If you boot into system and find youre stuck on HTC logo but somehow volume controls and power menu work then reboot to recovery and do a format then boot back into system then hold (Vol up + vol down+ power) for around 5 seconds until the setup screen displays. I don't know why this happens but it just does.
8.To restore IMEI and signal unlock bootloader,flash twrp then from recovery :
sabpprook said:
I found a post explain how to get IMEI back.
original post: http://bbs.gfan.com/android-9272781-1-1.html
Two methods for S-ON or S-OFF device, please do it under Nougat 7.0 firmware installed.
S-ON
1. Reboot to TWRP recovery
2. Use the command below to erase persist partition
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
Click to expand...
Click to collapse
Note: If you soft-brick your phone and lose recovery, system, bootloader unlock, then flash the same RUU zip as your version and android from external sd card through download mode. (It happened to me :/ )
I hope this helps you guys out. If I missed any step or something isnt well explained, please tell me.
zr_hazem said:
2.Reboot into download mode then run
Code:
fastboot getvar all
make sure that the (version-main) is the one you changed. Then lock your bootloader with
Code:
fastboot oem lock
(This is to be able to flash the RUU)
Click to expand...
Click to collapse
Do not relock bootloader, leave bootloader unlocked still have ability to flash RUU
sabpprook said:
2.Reboot into download mode then run make sure that the (version-main) is the one you changed. Then lock your bootloader with
Do not relock bootloader, leave bootloader unlocked still have ability to flash RUU
Click to expand...
Click to collapse
Hm. Are you sure about that? Because whenever i tried to flash anything it gave me an errror so I searched it up and read that bootloader needs to be relocked (at least when flash stock RUUs).
zr_hazem said:
Hm. Are you sure about that? Because whenever i tried to flash anything it gave me an errror so I searched it up and read that bootloader needs to be relocked (at least when flash stock RUUs).
Click to expand...
Click to collapse
The information is out date, HTC with download mode devices can flash RUU even bootloader is unlocked.
sabpprook said:
The information is out date, HTC with download mode devices can flash RUU even bootloader is unlocked.
Click to expand...
Click to collapse
That's odd. Alright, anyway I crossed it out but kept it in the post just in case because those exact steps worked fine for me.
Thanks for your input!
What is and where I can get the HTC Version Tool?
Im currently on LOS 15.1 but i Want to downgrade.
Installed the Simple CID Getter and it shows T-MOB101 TDM
How to start? Or how i can downgrade?
StarSix01 said:
Im currently on LOS 15.1 but i Want to downgrade.
Installed the Simple CID Getter and it shows T-MOB101 TDM
How to start? Or how i can downgrade?
Click to expand...
Click to collapse
Follow my guide 2nd post in this thread.
X46X said:
What is and where I can get the HTC Version Tool?
Click to expand...
Click to collapse
It's a tool that just changes your firmware version so you can downgrade. You can get it here
I have flashed HOSD but still getting error when I trying to flash Nougat firmware. I'm S-on. Can anyone help? I think I need a signed firmware but I can't find it. Mine is from Sneakyghost thread (PMEUHL_2.41.401.41_FullStock.zip) md5 matched..
Code:
C:\Android\com>fastboot flash zip firmware_n.zip
target reported max download size of 1578400000 bytes
sending 'zip' (107187 KB)...
OKAY [ 5.131s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) GPT (gpt_main_32g.img) is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) WARN Skip partition_info due to unmatched partition name
(bootloader) get 36 images from zip(zip_type=3)
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] Not allow flash image except boot/recov
(bootloader) ery/system
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: fail to flash zip: 1
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 14
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 14
(bootloader) [email protected]
FAILED (remote: 14 RU_ZIP_INFO_ERROR android-info missing or malformed )
finished. total time: 8.697s
X46X said:
I have flashed HOSD but still getting error when I trying to flash Nougat firmware. I'm S-on. Can anyone help? I think I need a signed firmware but I can't find it. Mine is from Sneakyghost thread (PMEUHL_2.41.401.41_FullStock.zip) md5 matched..
Click to expand...
Click to collapse
are you sure you downloaded the right firmware for your device
zr_hazem said:
are you sure you downloaded the right firmware for your device
Click to expand...
Click to collapse
yes, 401 wwe which I have..
X46X said:
yes, 401 wwe which I have..
Click to expand...
Click to collapse
Did u use the version tool and changed ur version to 2.41.401.41? If youve done all that then maybe get a firmware from somewhere else. It's weird because it should work for u since youre the same version as mine. I'm sure youll find a solution its just trial and error
zr_hazem said:
Did u use the version tool and changed ur version to 2.41.401.41? If youve done all that then maybe get a firmware from somewhere else. It's weird because it should work for u since youre the same version as mine. I'm sure youll find a solution its just trial and error
Click to expand...
Click to collapse
Yes I changed the version to the firmware version. But there is only one thread about firmware and I can't find firmware from another source..
While you are S- on follow this (I did it just like that and everything working, so don't worry):
1. Boot into TWRP run HTC Version Tool and change the version of the RUU youre going to flash.
2. Reboot into download mode then run
Code:
fastboot getvar all
make sure that the (version-main) is the one you changed.
3. Use HTC Decrypt Tool to extract the signed RUU.zip (not only firmware, just whole RUU)
4. Open decrypt output, find hosd_signed.img and flash it
Code:
fastboot reboot-bootloader
Code:
fastboot flash hosd hosd_signed.img
5. Put the RUU on your SD Card, name it "2PS6IMG.zip" and reboot to download mode. Press volume up and wait till the end. Then shut down and boot up your phone (after phone boot up you see a HTC logo for a few minutes - calm down and wait . Now you are on Nougat - without signal.
6. Alow ADB and flash TWRP recovery
7. Boot into recovery and do this in ADB:
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
8. Thats It, you have everything working after downgrade
X46X said:
Thats It, you have everything working after downgrade
Click to expand...
Click to collapse
My RUU file is PERFUME_UHL_N70_SENSE80GP_MR_HTC_Europe_2.41.401.3 [email protected]_79.07_F_release_493442_signed.zip
I decrypted and extracted hosd_signed.img from the RUU zip above, then
C:\fastboot>HTC_Version_Tool.exe
HTC Version Tool, code by [email protected]
-- misc: /dev/block/mmcblk0p38
-- offset: 2208
-- version: 3.16.401.2
new version: 2.41.401.3
Press ENTER to continue...
-- Erase version...
-- Write version [2.41.401.3]...
-- current version: 2.41.401.3
Finish!
then
C:\fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno:
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei:
(bootloader) version-main: 2.41.401.3
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: HTC__034
all:
finished. total time: 0.016s
while I have tried to flash hosd_signed.img this happened
C:\fastboot>fastboot flash hosd hosd_signed.img
target reported max download size of 1578400000 bytes
sending 'hosd' (52525 KB)...
OKAY [ 1.594s]
writing 'hosd'...
(bootloader) HOSD CL#1012001
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT hosd)
finished. total time: 2.609s
Do you have any idea what I did wrong?
Best regards
Witek
wtosta said:
My RUU file is PERFUME_UHL_N70_SENSE80GP_MR_HTC_Europe_2.41.401.3 [email protected]_79.07_F_release_493442_signed.zip
I decrypted and extracted hosd_signed.img from the RUU zip above, then
C:\fastboot>HTC_Version_Tool.exe
HTC Version Tool, code by [email protected]
while I have tried to flash hosd_signed.img this happened
C:\fastboot>fastboot flash hosd hosd_signed.img
target reported max download size of 1578400000 bytes
sending 'hosd' (52525 KB)...
OKAY [ 1.594s]
writing 'hosd'...
(bootloader) HOSD CL#1012001
FAILED (remote: 35 RU_PARTITION_NOT_SUPPORT hosd)
finished. total time: 2.609s
Do you have any idea what I did wrong?
Best regards
Witek
Click to expand...
Click to collapse
Are u using HTC decrypt tool to get hosd from RUU?
X46X said:
Are u using HTC decrypt tool to get hosd from RUU?
Click to expand...
Click to collapse
Yes. Exactly this one hosd_signed.img from the RUU, that I was going to install from sdcard after successful hosd operation.
But I have not tried another RUU so far presumably compatible with my phone.
wtosta said:
Yes. Exactly this one hosd_signed.img from the RUU, that I was going to install from sdcard after successful hosd operation.
But I have not tried another RUU so far presumably compatible with my phone.
Click to expand...
Click to collapse
Please reboot to bootloader (white background) and then flash hosd file again
sabpprook said:
Please reboot to bootloader (white background) and then flash hosd file again
Click to expand...
Click to collapse
Interesting thing. When I run the fastboot reboot-downloader command (white background), the windows system says that the USB device was not recognized. That's why I did not execute the fastboot reboot-downloader command and maybe that's why the fastboot flash hosd command did not work. In Windows_10_x64 I have installed only driver HTC Driver 4.10. When I turn on the phone with the buttons VOL DOWN + PWR and the system enters the Download Mode, the HTC device is correctly recognized in Windows, and no longer in the bootloader mode.
hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(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: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
any help is appreciated, thank you
redstonedudeHD said:
hello! my new member to the rooting community and i'm looking to get some help. i have a htc one m8s that is softbricked, i can flash twrp to recovery but when i use fastboot reboot-bootloader and enter recovery, it just reboots back into stock recovery.
i tried this, https://forum.xda-developers.com/general/help/phone-booting-default-recovery-flashing-t3720282. didnt work for me, i put the twrp file in the adb folder, renamed it recovery and flashed it. however when i did fastboot boot recovery.img it just said downloading boot.img.
twrp file used: twrp-3.0.2-0-m8ql.img
getvar info:
(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: 2.11.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: VODAP001
(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: 0b9a12e3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
any help is appreciated, thank you
Click to expand...
Click to collapse
It isnt working for you because you have to boot directly into recovery, you can't let the device boot to any other mode, if you boot to any mode other than recovery, a device will revert back to stock recovery. You are rebooting to bootloader mode instead of recovery mode, this is causing the device to revert to stock recovery instead of booting into the TWRP that you flashed.
After flashing TWRP, instead of using the fastboot reboot-bootloader command, use the adb reboot command, enter it as soon as you are done flashing the recovery.
Use the adb command below:
adb reboot recovery
Then you should boot into TWRP.
Sent from my SM-S767VL using Tapatalk
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Ok, let's take a couple of steps back. Do you know if your bootloader is unlocked? Flashing TWRP won't work if the bootloader is locked.
@xunholyx, could there be something that is HTC specific that they are overlooking?
Sent from my SM-S767VL using Tapatalk
bootloader is unlocked
redstonedudeHD said:
bootloader is unlocked
Click to expand...
Click to collapse
Try flashing the TWRP using the fastboot flash recovery command
Then try using this command:
fastboot boot recovery (name of your recovery file)
Sent from my SM-S767VL using Tapatalk
flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory
@Droidriven any idea what i can do?
double send
redstonedudeHD said:
hey, thanks for helping me out, but i cant get adb to detect my device, if tried multiple drivers for my phone and cant seem to get it to detect, any help with this one? thanks. also, fastboot can detect my phone just fine. ive tried the official htc drivers using sync manager, android bootloader interface, android adb composite interface and android adb interface. any help is appreciated, thank you!
as a side note, while trying to resolve this myself i found a post that said it was very hard to break the phone with s-on, which gives me hope.
Click to expand...
Click to collapse
Do you have USB debugging turned on in developer options? ADB commands won't work if you don't.
---------- Post added at 11:55 AM ---------- Previous post was at 11:50 AM ----------
redstonedudeHD said:
flashed twrp using the fastboot command returns this:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
sending sparse 'recovery' (14415 KB)...
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 6096896 is not a multiple of the block size 4096
OKAY [ 1.541s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.560s
using the htc_fastboot returns this
c:\adb>htc_fastboot flash recovery recovery.img
sending 'recovery' (30006 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but both htc_fastboot and fastboot both return this
c:\adb>htc_fastboot boot recovery recovery.img
cannot load 'recovery': No error
c:\adb>fastboot boot recovery recovery.img
cannot load 'recovery': No such file or directory
Click to expand...
Click to collapse
It seems to have flashed properly with htc_fastboot.
Try flashing it again, then
htc_fastboot reboot bootloader
then select boot to recovery from the bootloader menu on your phone from there.
It should take you to TWRP
hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.
redstonedudeHD said:
hey @xunholyx there is no command for that in the htc fastboot, just brings up the help menu for fastboot. would normal reboot from fastboot work? or would twrp be overwritten by stock recovery? thanks for the help.
Click to expand...
Click to collapse
It should work with regular fastboot reboot bootloader then selecting recovery from there via your phone
EDIT: I have never had to use HTC's fastboot myself. It is necessary for flashing large files from your PC. I always flashed the large files (eg: RUUs) via the SD card method. But that wasn't for recovery.img s, it was for RUUs
EDIT #2: I'm going to request to the moderators to have this thread moved to a forum where you might find other help. You don't have to do anything about it. It will just get moved. The forum I'm moving it to is for the regular M8 and not the M8s, but people there will be able to offer help that you won't get here. I'll continue to monitor this thread there and offer help if I can.
hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!
redstonedudeHD said:
hey @xunholyx, sorry i havent been active, got burnt out on trying to fix it lol, but im back again.
found a way to use the normal fastboot to flash recovery (i think im no genius) using this command
c:\adb>fastboot flash:raw recovery recovery.img
sending 'recovery' (30006 KB)...
OKAY [ 2.121s]
writing 'recovery'...
OKAY [ 0.745s]
however when i use fastboot reboot or fastboot boot-bootloader ect, recovery just brings me back to fastboot. anyone any ideas?
i still cant adb to detect my device either. i know this might sound stupid but does my phone have to be in a specific state to use adb commands? i can only access the stock recovery so anything other then that and im screwed lol, thanks for the help!
Click to expand...
Click to collapse
Sorry I haven't responded sooner.
I would suggest you run an RUU. The problem is, I don't know of any RUUs myself for your current firmware version, and since you are S-On, you can't roll back to an older version.
If you can find an RUU for 2.11.161.1 download it and flash it. The only ones I can find are from a previous Android version. (1.xx.xxx.x)
Also, there is a newer TWRP version than the one you are using. Maybe that might be the issue? I can't be sure about this, since I'm familiar with the HTC M8, but not the HTC M8s.
You can download the updated TWRP version from here.
I believe it was updated to work with 2.xx.xxx.x firmware. But I'm not positive. It can't hurt to try it out.
hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/
redstonedudeHD said:
hey @xunholyx i found a one that matches my os and my cidnum, now what do i do with it? also, i found it on this website, hopefully it will help a few others, https://www.hardreset.info/devices/htc/htc-one-m8/faq/firmware/
Click to expand...
Click to collapse
There's two there. I don't know what the difference between "partial" and the other one is. I would assume the partial one has the boot.img and maybe the recovery.img removed?
Use the other one. There are two ways to flash it since it is an RUU.zip.
#1: In fastboot: fastbbot flash zip **drag and drop the zip here**
#2: Rename the zip by deleting everything in the name of it except for 0PKVIMG (and .zip of course) and place that onto your extSD card (must be formatted to FAT32)
Put that into your phone then bot to bootloader. It should find the file automatically. If it doesn't, boot to hboot from boot loader.
From there it's super easy. Follow the on screen prompts. Volume up to confirm the flash. Power button to reboot after the flash is done.
Good luck! I hope you get everything up and running again.