Develop Bugs

[Q] Help Needed

Hi guys,
i seemed to have bricked my phone because all i can do is boot into bootloader, download mode, recovery mode. it has stock recovery and relocked bootloader.
i want it boot into android anyway possible stock or not. I can provide anydetails required about my phone. I have tried several RUUs and 0PJAIMG.zip files but nothing seems to be working.
For RUUs i get the error "Please get the correct Rom Update Utility and try again" and for 0PJAIMG.zip files my phone says "SD CARD NOT MOUNTED" in download mode. Please help me revive my phone and sorry for a long.
Thanks in Advance.
Edit: Even if anyone can link me to a x.xx.425.xx ruu, that would be great.
1.40.425.10 or 1.34.425.7 or 1.34.425.5 or 2.11.425.7

This is my phone's information
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.425.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA13000
(bootloader) cid: HTC__059

hassam_tariq2003 said:
This is my phone's information
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.425.7
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.04_U11440601_71.02.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA13000
(bootloader) cid: HTC__059
Click to expand...
Click to collapse
I assume your phone is S-ON. You can't downgrade or flash RUUs for different SKUs than 425.
The problem: There are only RUUs for firmware 1.34.425.7 and 1.34.425.8. So unless you don't have S-OFF you can't use them.

Flippy498 said:
I assume your phone is S-ON. You can't downgrade or flash RUUs for different SKUs than 425.
The problem: There are only RUUs for firmware 1.34.425.7 and 1.34.425.8. So unless you don't have S-OFF you can't use them.
Click to expand...
Click to collapse
how can i get s-off when my phone won't go past the bootloader?
can you provide me with the links to x.xx.425.x RUUs?

hassam_tariq2003 said:
how can i get s-off when my phone won't go past the bootloader?
can you provide me with the links to x.xx.425.x RUUs?
Click to expand...
Click to collapse
Did you try re-unlocking via HTCdev? The M9 has some security checks which prevent the phone from booting if the bootloader is locked/relocked and the phone is not completely stock. If that doesn't help you may need to look for someone with a java card.
For answering your second question I'm qoting myself from another thread:
Flippy498 said:
ir-file.com
But you need to pay if you want to download files from that site. Since I know someone who has an account I may be able to get one of the RUUs for you. (Can't guarantee anything.)
Click to expand...
Click to collapse
As far as I know the 1.34.425.7 RUU is getting uploaded on AFH at the moment. But as said before you won't be able to use it without S-OFF.

Flippy498 said:
Did you try re-unlocking via HTCdev? The M9 has some security checks which prevent the phone from booting if the bootloader is locked/relocked and the phone is not completely stock. If that doesn't help you may need to look for someone with a java card.
For answering your second question I'm qoting myself from another thread:
As far as I know the 1.34.425.7 RUU is getting uploaded on AFH at the moment. But as said before you won't be able to use it without S-OFF.
Click to expand...
Click to collapse
I can't re-unlock my phone i tried like 3 times already.
That would be great if you could upload the file and link it here...

There you go (thanks to Handy-FAQ.de). But as said before it's useless if you don't have S-OFF.
Edit: I guess the option OEM Unlock (located in developer options) hasn't been activated before you relocked the bootloader, am I right? That's why you can't re-unlock. But you could still look for someone who owns a java card to get S-OFF, use the RUU service on Llabtoofer's website or hope that someone creates and uploads a TWRP backup that contains an untouched system image, the boot image and the stock recovery of your currently installed firmware.

Flippy498 said:
There you go (thanks to Handy-FAQ.de). But as said before it's useless if you don't have S-OFF.
Edit: I guess the option OEM Unlock (located in developer options) hasn't been activated before you relocked the bootloader, am I right? That's why you can't re-unlock. But you could still look for someone who owns a java card to get S-OFF, use the RUU service on Llabtoofer's website or hope that someone creates and uploads a TWRP backup that contains an untouched system image, the boot image and the stock recovery of your currently installed firmware.
Click to expand...
Click to collapse
Thank You.....i will look for someone with a java card

M9 won't boot ROM(s), only boots to fastboot/bootloader/recovery

Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,

Can you install a custom ROM with S-ON?
I don't think you can ...

andTab said:
Can you install a custom ROM with S-ON?
I don't think you can ...
Click to expand...
Click to collapse
I haven't touched the Android scene since the M7, so it's been a while for me. But if I recall correctly, S-OFF isn't a prerequisite to installing custom roms, as S-OFF is only required to run custom firmware or to run special fastboot commands. Perhaps somethign has changed over the past few years, but I'd be unaware.

Realized the getvar output was clipped:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227xxxxxxxxx
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s

I started my Android experiences with the One S in 2012. Since that time S-OFF has never been needed for custom roms. It's only needed for firmware downgrades, flashing unsigned/unofficial firmware packs or flashing RUUs with a different SKU than your phone was shipped with.
@kikokazuma: It's almost impossible to help you without knowing you firmware version (version-main) since your phone is S-ON.
Edit: Seems like I didn't type fast enough. Maybe you should take a look at the AT&T forum of the M9. They might have a RUU or a TWRP Backup you could use.

Since I am in the same boat with exactly the same results, I don't think it is possible to flash custom ROMs without S-OFF
I have now tried at least 10x flashing CandySix ... same result: Just stuck on the HTC logo (HTC This build is for development purposes only ....)
TWRP (the latest recommended beta version BTW) even says that everything flashes fine ... just no booting to the OS.

Your firmware needs to match the rom base. Many of the latest custom rom versions need a 3.x firmware. Not every SKU already got the Android M update so it's no miracle that some roms don't boot if you use a 2.x firmware like the OP does. This has nothing to do with S-OFF. The only difference for S-OFF users is that they can change their SKU to one that already got the Android M update. But according to Llabtoofer more M9 updates are goint to be distributed during the next week.
Nevertheless every custom rom has an older version that is compatible with the 2.x firmware. For example if you want to flash the Viper rom then you need to use version 3.5. So either wait for the update or look for older versions of the rom you want to flash.
Edit @andTab: In your case it's the other way round.

Flippy498 said:
Your firmware needs to match the rom base. Many of the latest custom rom versions need a 3.x firmware. Not every SKU already got the Android M update so it's no miracle that some roms don't boot if you use a 2.x firmware like the OP does. This has nothing to do with S-OFF. The only difference for S-OFF users is that they can change their SKU to one that already got the Android M update. But according to Llabtoofer more M9 updates are goint to be distributed during the next week.
Nevertheless every custom rom has an older version that is compatible with the 2.x firmware. For example if you want to flash the Viper rom then you need to use version 3.5. So either wait for the update or look for older versions of the rom you want to flash.
Edit @andTab: In your case it's the other way round.
Click to expand...
Click to collapse
The unofficial version DOES support 3.x firmware so that can't be it!
See here: http://forum.xda-developers.com/showpost.php?p=64892501&postcount=249

andTab said:
The unofficial version DOES support 3.x firmware so that can't be it!
See here: http://forum.xda-developers.com/showpost.php?p=64892501&postcount=249
Click to expand...
Click to collapse
And in post #250 someone says that he can't get them to boot. So it's obviously a problem caused by the rom and not the phone. Please go and ask the dev in his thread what to do or just wait until there is official 3.x support. I don't think that it is very polite to hijack kikokazuma's thread with problems that clearly do not belong to the OP's problems.
Edit @kikokazuma: I forgot that HTC US itself provides RUUs for the US carriers. Here's the download link for the RUU you need.

andTab said:
Can you install a custom ROM with S-ON?
I don't think you can ...
Click to expand...
Click to collapse
You definitely can !
I'm still with S-ON and I just installed ViperOne 4.2.1 few days ago.

Flippy498 said:
And in post #250 someone says that he can't get them to boot. So it's obviously a problem caused by the rom and not the phone. Please go and ask the dev in his thread what to do or just wait until there is official 3.x support. I don't think that it is very polite to hijack kikokazuma's thread with problems that clearly do not belong to the OP's problems.
Edit @kikokazuma: I forgot that HTC US itself provides RUUs for the US carriers. Here's the download link for the RUU you need.
Click to expand...
Click to collapse
Gotcha, so basically the newer ROMs require 3.x firmware or higher, and since I'm S-On with 2.x, I can either:
- Pay for Sunshine and load a firmware of my choice, or
- Wait for the official RUU to marshmallow to get the latest firmware, and THEN unlock + load ROM.
Makes sense. Thanks for the help!

You don't need to wait for a Android M RUU. If you use the RUU I linked to get back to stock you can install Android 6 with the update function in settings>about once HTC distributes the update for your SKU. From my experiences OTAs get distributed a bit earlier than RUUs.

Flippy498 said:
You don't need to wait for a Android M RUU. If you use the RUU I linked to get back to stock you can install Android 6 with the update function in settings>about once HTC distributes the update for your SKU. From my experiences OTAs get distributed a bit earlier than RUUs.
Click to expand...
Click to collapse
Would that update also upgrade my firmware so I could then install custom ROMs? I'm not trying to stay on a stock ROM. Just making sure I understand
Thanks again,

Yes it would. Btw: You can already flash custom roms. You only need to look for the Android LP versions of the roms.

Flippy498 said:
Yes it would. Btw: You can already flash custom roms. You only need to look for the Android LP versions of the roms.
Click to expand...
Click to collapse
Oh but who would want LP with all this cutting edge technology around? My bad, I thought my search for Marshmallow was a given!

kikokazuma said:
Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,
Click to expand...
Click to collapse
So after playing around with any possible combination of flashing, here is the fix:
1. Flash the ROM
2. Flash Gapps
3. Flash a Kernel!!!!!!
Without #3, no ROM worked for me on S-ON.
Since most ROM's actually ONLY work with 2.xx you may be better off with it at the moment.
3.xx is the problem, since it requires some fix to get sound to work.

andTab said:
So after playing around with any possible combination of flashing, here is the fix:
1. Flash the ROM
2. Flash Gapps
3. Flash a Kernel!!!!!!
Without #3, no ROM worked for me on S-ON.
Since most ROM's actually ONLY work with 2.xx you may be better off with it at the moment.
3.xx is the problem, since it requires some fix to get sound to work.
Click to expand...
Click to collapse
That only applies to CM roms and it's derivates (or maybe only to CandySix; I don't use Sense-less roms so I'm not completely sure). Sense roms work perfectly fine with the latest firmware.

please help me here. i am now really confused
Elixir_ said:
You definitely can !
I'm still with S-ON and I just installed ViperOne 4.2.1 few days ago.
Click to expand...
Click to collapse
hello i own a htc one m9 with unlocked bootloader, fully rooted with twrp v3.0 which was the only one that worked, fully s-off using sunshine app and supercid 11111111, i have tried to install viperone m9 5.3 on my phone it wipes successfully with twrp recovery but after the installation process i wont boot OS, instead it boots straight to bootloader, i can access recovery and download very well. i have restored backup on my phone inorder to get my phone back. i really need viperone on my phone because i have also tried to install other lower versions of viperone still the same problem all. please help me here i really need help. what am i not doing right here?

Did you ever get this resolved??
kikokazuma said:
Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,
Click to expand...
Click to collapse
I'm having the same issue and I can't even flash the RUU because USB debugging is not on because I wiped with out a backup stupid me I know so any way I'm stuck did you resolve your problem

kikokazuma said:
Good afternoon all,
Trying my luck at loading a custom ROM on this M9 but hit a brick wall.
What I've done so far:
- Unlocked bootloader successfully
- Installed TWRP 2.8.7.0 successfully
Here's a quick getvar for you all:
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: 357227062034218
(bootloader) version-main: 2.11.502.18
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_72.02.50602A_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: CWS__001
all:
finished. total time: 0.016s
Bootloader screen currently displays:
*** Software status: Official ***
*** UNLOCKED ***
*** S-ON ***
So I can install any ROM of my choosing from the external SD card with no errors during install. So far I've installed both ARHD and Viper with wipes in between. After successful install my phone continues to boot straight to fastboot, never loading the ROM. I can boot into recovery, fastboot and bootloader with no issues, but the ROM never seems to load.
What gives?
Thanks in advance,
Click to expand...
Click to collapse
First you need to install stock rom(with stock recovery,boot,kernel etc) in ur htc and update the mobile using OTA(over the air) updates to marshmallow or higher
Then try installing rom custom rom
Note:- S-off is not required to install custom rom

How to flash ROM to my HK M9?

I went thru a few threads but couldn't find any direct tutorial to flash my m9. I downloaded ota, but i cant s-off my unit(sunshine doesn't work), thus i cant flash it. maybe its running new OS?
I wanted to flash any rom to my m9, either stock or wwe or cyanogenmod, but all seems to require s-off.
my play store is missing & even though i did a master reset(tried from normal menu n also bootloader mode), playstore just wont appear.
here are my details :
Non-rooted
S-ON
LK-1.0.0.0000
firmware 3.42.708.3
fastboot result :
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: Mod Edit: Removed
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
I went thru about 5 threads but cant find a direct solution, I hope I'm not asking something that is widely posted here, seems i just can't S-off. Any helps to flash roms in my situation?

Anyone care to help out?

There is no other publicly available RUU for your SKU than a 1.32.708.15 one which you can't use due to downgrades not being possible without S-OFF.
Taken from my sticky thread in the general section:
Flippy498 said:
Llabtoofer's RUU Service
he can help you out if there is no freely available RUU for your phone​
Click to expand...
Click to collapse

dear flippy, can i install custom rom while its S-ON? I know how 2 do it on prev HTCs(unlock bootloader, flash recovery, flash rom, flash boot.img), but no sure if m9 is applicable..

Yes, you can. However you need to re-flash the stock boot.img of your phone afterwards or you'll loose your mobile reception (this only applies to sense-based roms). If you want to use a non-sense-based rom like cm you need to flash thicklizard's mono kernel instead of the stock boot image.
Sent from my HTC One M9 using XDA Labs

Soft Bricked HK M9 - OS-3.42.708.3

need your help guys
i really dont know how the phone got to the position where it says that the software modified, as far as i know, no one tried to flash any 3rd party roms.
current status:
software: modified
Locked
S-on
whats available:
bootloader, recovery, download modes are available, phone is recognized via fastboot, but not much info there
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: 35xxxxxxxxxxxxx350
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__622
what's impossible:
*can't unlock officially - as i don't have working system to enable oem unlock at dev options
*can't flash twrp backup as i cant flash different recovery - s-on
*can't flash any ota update with working system.img - s-on
*can't flash RUU zip as there isn't one with my current version and can't downgrade - s-on
any suggestions whats available for me to fix it?

How did it end up in that state?.
Beamed in by telepathy.

im not sure, the device belong to a friend, its not mine, im just trying to help out

It looks like it got "killed" by trying to set back "unlocked" and "S-OFF" to "locked" and "S-ON". Your only hope is llabtoofer's RUU service because as you already found out there is no publicly available RUU for that phone. Direct links can be found in my sticky thread in the general section or in my google sheet.
Sent from my HTC One M9 using XDA Labs

sh33z0r said:
im not sure, the device belong to a friend, its not mine, im just trying to help out
Click to expand...
Click to collapse
I can help you with this RUU....

shivasrage said:
I can help you with this RUU....
Click to expand...
Click to collapse
Have same problem too. Any help would be much appreciated.

same problem here

Variant System Version OTA Update Error

After a long wait I finally got my ota update to Nougat.
But there is another problem, I cant finish the update because my phone showed that error.
I'm on stock M9 in bootloader it says software status official, locked, and s-on. No root, as I have checked it using root checker. Recovery is there.
I never modified my phone. And its fine back when I updated from lollipop to mm via ota, there is no problem.
And as far as I know, my phone is on correct mid and cid, SKU 708, mid 0PJA10000 exactly the same with mid engraved on my phone, and cid HTC__044
But when I update mm to nougat, this variant system version error shows up
I have tried to flash RUU of my current firmware, but still nothing.
Please help me, where did I do wrong? or how can I solve this problem?

Bumping this because I got the same thing too.
My device is not even rooted!

Did you guys flash a RUU for your current firmware and try to download the OTA, again?

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I did, but the problem stays there.

Flippy498 said:
Did you guys flash a RUU for your current firmware and try to download the OTA, again?
Click to expand...
Click to collapse
I dont know how to flash the RUU.
But anyway, is there a way to check whether i can flash the OTA on my own?

vglaksana said:
I did, but the problem stays there.
Click to expand...
Click to collapse
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
-marco- said:
I dont know how to flash the RUU.
Click to expand...
Click to collapse
Well, there is a thread pinned above all the other threads in this section that is even called "ReadMe" and people still tend to completely ignore it...
-marco- said:
But anyway, is there a way to check whether i can flash the OTA on my own?
Click to expand...
Click to collapse
If you can't flash an OTA via the software update function then you can't flash it via fastboot, either. Your phone doesn't pass the security checks that google implemented with android 5 so the method you use for flashing the OTA doesn't matter.
Flash a RUU and re-try to install the OTA. If that still doesn't matter then please copy and paste your fastboot getvar all output here (without your IMEI!), as well.

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
Here it is
C:\Users\Vito G. Laksana\Desktop\New folder>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U114,10801_97.64.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC 044
all: inished. total time: 0.016s
Above is getvar all from before I flashed my current RUU. I believe it wouldn't change anything, as I can't get fastboot getvar all working now.

vglaksana said:
(bootloader) cid: HTC 044
Click to expand...
Click to collapse
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
If that is an exact copy of the output then it's no miracle that you can't install the OTA. That CID doesn't exist. It needs to be HTC__044 (8 letters, numbers or symbols in total and no spaces). You need S-OFF for being able to correct your CID.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ah my bad. The correct CID is HTC__044, as I mentioned in the thread first post.
I just using image to text converter because I have screencap of the output and didn't see that straight away.

Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Ah ok. And I already hoped that we found the cause of the problem... There have been some threads about devices that got bought in the US, S-OFFed and reflashed to non-US versions for selling them in other countries, in the past (around the time when firmware 2.x was the latest one). In most cases the sellers didn't convert the phones correctly and the buyers faced similar errors to your one when they tried to install an OTA.
Unfortunately there's nothing strange I can find in that output, then.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thanks for helping me figuring out the problem.
If that is the problem, then why I have successfully update from lollipop to mm?
Yes i did buy it second hand, he said that the phone is from Singapore, and from the getvar output it is make sense that my phone came from Singapore.
Soo...I believe my only option is to S-OFF and convert to other version to get the update, is that correct?

I just re-read your opening post. Looks like I missed the part with the engraving. The US variant has a different engraving than the one you mentioned. So my assumption is probably wrong.
Since I have no clue what might cause your problem I actually don't see any other solution than getting S-OFF and converting the phone.
If there was a publicly available 4.x RUU for your SKU you could have asked Sneakyghost whether he creates a firmware package for you. By flashing that (S-OFF needed) you would have been able to use the 4.x RUU although you never installed the corresponding OTA. This way you could have kept your SKU. However, I haven't seen a public download link for such a RUU, yet. Therefore, you'll need to convert to a different SKU if you want the latest firmware.
Since you're still on firmware 3.x you need to flash one of Sneakyghost's 4.x packages before you can flash a 4.x RUU of the SKU that you want to convert to. Or you use a 3.x RUU for converting and try to install the OTA of the new SKU, afterwards. (The latter will probably take longer in total.)
Alternatively, you can wait some more days and see if some else has a better idea.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you please copy and paste the fastboot getvar all output here (without your IMEI!)? It might help us to help you.
Click to expand...
Click to collapse
I rebooted into bootloader to get the getvar but it doesnt work.
adb lists no devices.
Also, see the enclosed pic. that's as far as i managed to get.

Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Adb won't work if the device isn't booted to system or recovery mode.
And since the fastboot mode doesn't exist anymore on the M9 and all newer HTC phones you need to boot to download mode.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
booted to system: adb sees device but says it's offline
booted to dl mode: adb can't see the device.
anyway, i took picture of what dl mode looks like. Attached.

Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Yeah, that's how it's supposed to be. ADB can only be used if the phone is booted to the system or the recovery mode. You can't use ADB commands while it's booted to the bootloader or the download mode. You need to use fastboot commands in these modes.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
apparently i had a problem with drivers. i have fixed it now, that's why it gave empty devices.
Ok went back to bootloader mode. run fastboot getvar all:
Code:
(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:HT54GYJ05021
all:
finished. total time: 0.132s
this is instead the same taken from dl mode:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) version-main: 3.42.708.3
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_97.04.60111G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__044
all:
finished. total time: 0.006s
what now?

Mhm, there's nothing strange in that output, either.
Can you flash a RUU and re-try installing the OTA? If that doesn't fix the problem then the only other option is converting the phone as I already suggested to vglaksana.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Can you flash a RUU and re-try installing the OTA?
Click to expand...
Click to collapse
can you point me to a guide on how to do this?
and also where can i find my relevant RUU?
thanks.

I already did so in my first reply to you.
Sent from my HTC One M9 using XDA Labs