Develop Bugs

I just want a normal phone again...

I am s-off and this is my getvar: http://pastebin.com/x4YZ3G34
---
I currently have some type of developer edition firmware that doesnt let me update because it knows I have the wrong phone.
I have changed my CID to H3G_001 as this is what it should be as I am with Three (H3g) in the UK.
I understand an RUU would be best but there are none for my carrier.
What would you do in my situation?
PLease help - I just want my normal phone bac with software that can install updates

Try changing CID to 1111111 through fastboot (cmd - fastboot OEM writeCID 1111111) then fastboot flash a GPE RUU (you can find em through graffixnyc.com).
Sent from my m8 using Tapatalk

FlubbyHF said:
I have changed my CID to H3G_001 as this is what it should be as I am with Three (H3g) in the UK.
I understand an RUU would be best but there are none for my carrier.
What would you do in my situation?
PLease help - I just want my normal phone bac with software that can install updates
Click to expand...
Click to collapse
Your paste.bin doesn't show that you changed the CID back to H3G__001
After you change the CID back to H3G__001, you can restore H3G__001 stock ROM backup and its matching stock recovery then do update.
You need to restore 4.20.771.2 backup.
You can read post #1 on how-to, files available on post #3 and #4
--> http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Any further question, you can ask in that thread to get my faster respond.

FlubbyHF said:
I am s-off and this is my getvar: http://pastebin.com/x4YZ3G34
---
I currently have some type of developer edition firmware that doesnt let me update because it knows I have the wrong phone.
I have changed my CID to H3G_001 as this is what it should be as I am with Three (H3g) in the UK.
I understand an RUU would be best but there are none for my carrier.
What would you do in my situation?
PLease help - I just want my normal phone bac with software that can install updates
Click to expand...
Click to collapse
The developer edition is a normal version - just minus the carrier additions. I would suggest altering your CID/MID to match the developer edition. You already know how to change the CID, so set that to BS_US002. Then change MID using this post http://forum.xda-developers.com/showthread.php?t=2708581.
At this point, you should be able to get OTA updates if you haven't modified the OS. If you have, re-run the developer edition RUU from HTC.
When you are done, you will have a bog-standard "normal" phone in every way - and you will get your updates a heck of a lot faster than you will with any carrier.

[SOLVED]How to get official updates after relocking bootloader?

Hello to everyone!
I have HTC M8(second hand...) I check the IMEI and i see is from Australia - Sold to Singapore. I don't know if it means something.
It was unlocked bootloader and modified software(Custom ROM-android 6), S-OFF and CID was 11111111(I don't know what was the original CID, because this is how i bought the phone)
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
There is a message:
'Variant system version - We have determined that your phone may be running a modified version of its system software. For your protection, we cannot update your phone. Please revert your phone to the official HTC system software to update your phone. If you did not modify your system software or would like help reverting your system please contact us via the support section at HTC - Mobile Phones, Smartphones, Cell Phones, Tablets'
I'm sure i have official software, stock recovery and boot.img, but i have no idea why this message appears.
Right now i am using InsertCoin ROM and i have noticed the message, that tells "Software status: Modified or Official" Mine tells always OFFICIAL. No matter if i have installed insertcoin or stock rom.
Here is the infor from my bootloader:
***Software status: Official*** (Just to remind... I'm with insertcoin rom)
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
RADIO-1.25.214500021.06G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.16.401.10
eMMC-boot 2048MB
Jan 15 2015, 22:51:08.0
Can anyone tell me how to download the official updates?
(sorry for my english)

No one can help with this ?

Jared89 said:
I decided to get it back to stock. I found a few threads about how to get the HTC M8 fully stock, but nothing works for now. l have the the stock recovery, stock boot.img and locked the bootloader.
Click to expand...
Click to collapse
None of that includes an actual stock ROM, which is required to OTA.
Jared89 said:
When i installed/restored from the RUU file it was ok. When i check for updates it's downloading, but cannot install.
Click to expand...
Click to collapse
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?

redpoint73 said:
None of that includes an actual stock ROM, which is required to OTA.
You're sure the RUU installed correctly, with no errors?
Did you try to update immediately after RUU, with not mods at all (unlocking the bootloader, root, custom ROM)?
Click to expand...
Click to collapse
Yes. I have no errors during the installing process and after that...
And yes... I try to update immediately after the phone boot to the home screen. I have no idea how to fix this. With my previous HTC M8 i was using the same custom rom(InsertCoin) and when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.

Jared89 said:
when i decidet to go back to stock, all i was doing is to lock the bootloader and install the RUU. Then i'm able to get the updates with no problems.
Click to expand...
Click to collapse
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.

redpoint73 said:
Yes, its strange. RUU by definition should put you on a fully stock image, and therefore allow OTA updates.
You can try to RUU straight to 6.12.401: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Curious to see if you get the same error with that RUU.
Click to expand...
Click to collapse
I was trying this a few times. It says there is not enough space or something. C

I'm still looking for solution. Any suggestion is welcome!

Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine ?.

Yes, i'm still S-OFF.
Thanks! I will try it and i will let you know if it works.

HTCNerdYoda said:
Are you still S-OFF? On the M9 one hast to change the CID from SuperCID (11111111) back to a WWE CID to take the update to MM, as HTC uses a new routine to check the state of the phone.
In your case you'd have to reboot to fastboot mode, open a command prompt and change the CID to HTC__001 (8 digits!!) by using the command "fastboot oem writecid HTC__001"
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?

Jared89 said:
I just try your method, but when i try to get it back to stock with RUU.exe i get Error 130, which means is a wrong device. I gues i will have to get back the super CID?
Click to expand...
Click to collapse
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine ?.

HTCNerdYoda said:
Which RUU are you using? In case of an x.xx.401.x RUU it is indeed WWE. Thus the CID should be HTC__001 or HTC__102.
maybe you should tray to RUU with the later one and if it doesn't work go back to SuperCID.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
4.16.401.10 Europe.
I can't use the latest RUU, because is only on ZIP file. When i try to install it with fastboot it says there is no space or something.

You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine ?.

HTCNerdYoda said:
You could rename the RUU zip to 0P6BIMG.zip and copy it to the root direction of a - at max - 32GB microSD card that has been formatted to fat32.
Insert this SD into your M8 and reboot to bootloader. It will then recognize the RUU and start to flash it automatically.
After a full flash you got to take the SD Card out again, to prevent it to start again during the next reboot
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...

Jared89 said:
I'll try this later. Just flashed the RUU(4.16.401.10_Europe), but even with CID HTC__02 i get "Variant system version" message...
Click to expand...
Click to collapse
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine ?.

HTCNerdYoda said:
Sure you took HTC__02, as it hast to have 8 digits and thus HTC__102. In case it doesn't help return to SuperCID 11111111.
Send by the swarm intelligence of my coffee machine .
Click to expand...
Click to collapse
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!

Jared89 said:
Nothing works for now. I bring it back to InsertCoin rom.
My phone is from Singapore, so i might need the correct RUU for it. I have no idea!
Click to expand...
Click to collapse
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.

ckpv5 said:
Your problem is not the SuperCID 11111111 but wrong MID for the ROM that you installed.
To run a EU RUU x.xx.401.x, the MID must be 0P6B10000
You said your device is from Singapore, most probably the MID is 0P6B11000 and that's the reason for your "Variant System Version" error.
You can check your current MID by running command fastboot getvar mid
And for S-Off, there is no need to relock bootloader for OTA or running a RUU.
Click to expand...
Click to collapse
Didn't think about that. MID is 0P6B11000, as you said. I have changed it to 0P6B10000. I'll try later if i get the updates. Thanks a lot for the info!

Ok, when i changed MID the problem was solved! Now i get all the updates! Thanks a lot!
I followed instructions from this post:
http://forum.xda-developers.com/showthread.php?t=2708581

Trying to revert to stock, soft-bricked my phone

Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone, now the only thing I have is an s-on unlocked bootloader and twrp. All the roms I tried installing using TWRP keep saying that the updater binary failed or something. When I try to do RUU, it just doesn't work. Can anyone help me restore functionality to my phone?

Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
TheOnlyLite said:
Hi, I am trying to revert my m8 to stock with no root, but I just formatted and wiped my phone
Click to expand...
Click to collapse
Did you think that would return your phone to stock?

redpoint73 said:
Need to provide more info.
Do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
What ROMs did you try?
What version TWRP?
What RUU? You need to relock the bootloader to RUU. But if its not the right RUU for your version (CID), it won't work and you'll be stuck unlocking the bootloader again. So don't relock the bootloader until you provide all the info requested.
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
Did you think that would return your phone to stock?
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0321
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: 11111111
(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: fd3e0448
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I just tried a bunch of random ones online tbh. I can't find any that match my phone's CID or MID even thought my CID is 1111111.
I have twrp 2.8.1.0 right now.
I am just trying to get the os working for now because everything I tried flashing didnt work.

You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

redpoint73 said:
You have the Verizon version.
Randomly looking online for ROMs is not a good idea. Stick to XDA, and in your case, stick to the Verizon Dev forums.
Also, what RUUs did you try (don't like asking the same question twice)? If it wasn't a Verizon RUU, you are lucky it didn't work, since any other RUUs can radio brick your phone. Again, flashing random things is not a good idea, especially with s-off and SuperCID, the results can be disastrous.
You have a couple things going on:
1) Your firmware (hboot, radio, etc.) is woefully outdated. It won't work on any of the current ROMs.
2) Only ROMs meant for the Verizon version will work, due to kernel differences.
I'd advise run an Lollipop or Marshmallow Verizon RUU, which will get you to stock, and with updated firmware. I'll see if I can find the VZN RUUs.
EDIT: Here you go: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.

TheOnlyLite said:
I tried just any RUU that I found that was for the HTC One M8 like things from android revolution, but they all just failed.
Click to expand...
Click to collapse
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
TheOnlyLite said:
Also, I have S-ON right now because of a guide online telling me to do that, but it was wrong. Is there a way I could change it back to S-ON without os?
Click to expand...
Click to collapse
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
TheOnlyLite said:
edit: i tried using the RUU exe on the link you put, but it didn't work and it says to get the correct firmware update utility. I don't know what I'm doing wrong.
Click to expand...
Click to collapse
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.

redpoint73 said:
Of course, any RUU not intended for the VZN version will fail, by design. You can't run an RUU for a different CID and MID. And I must stress do not change the CID and/or MID in an attempt to flash another version's RUU. As mentioned, if any other RUU actually flashed, it would probably radio brick your phone. VZN version (along with Sprint version) has different radio, partitions, and kernel from all other M8 versions. FOr this reason, RUUs are not interchangeable in your case (VZN version). You should not try to run any RUU except those specifically for the VZN M8.
The guide isn't wrong, if the intent is to return to full stock, for which s-on is the stock condition.
Usually, the only reason to do so (return to s-on) would be if you were trying to return the phone for warranty purposes; which I do not believe is the case for you.
I agree that for the purposes of what you wanted to do, s-on limits your options and was not a good idea.
But no, there is no way to return to s-off with no OS.
I don't know what you did wrong either, if you don't specify which file you tried.
If you tried the Marshmallow RUU, you may need to run the corresponding stock MM firmware before you can RUU. Try the LP RUU and see if that works.
Click to expand...
Click to collapse
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd? The exe keeps saying "The Firmware Update Utility cannot update your Android phone." and when I flash using adb or fastboot, it just fails.
edit: Actually I don't even know. I'm pretty dumb when it comes to this kinda stuff. What do you suppose I do step by step? I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.

TheOnlyLite said:
So I tried all the RUUs, exe and flashing with rebootRUU. Nothing worked. Would the only way to rename the file to 0P6BIMG.zip and having the phone detect it in my external sd?
Click to expand...
Click to collapse
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
TheOnlyLite said:
when I flash using adb or fastboot, it just fails.
Click to expand...
Click to collapse
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
TheOnlyLite said:
I still have access to bootloader and TWRP, but I just can't flash anything for some reason. Or the roms that I try always end up with an error.
Click to expand...
Click to collapse
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.

redpoint73 said:
I wouldn't say the SD card method is the "only way". But if you have an SD card, and a way to put the file on the card (USB card reader) then its probably the easiest way to RUU. At least, the least points of failure, as the exe can be finicky depending on your PC setup, and the fastboot method has some pitfalls as well (more on that below).
If you are trying adb commands, there is no method to flash RUUs with adb. You need to use fastboot. If you are using adb, I don't know what you are doing or why.
"It just fails" meaning what? Is there an error message (if so, what is it exactly?) or it just hangs?
Try the method posted here: http://forum.xda-developers.com/htc-one-m8/help/help-htc-one-m8-bricked-t3298412
Not the actual RUU zip posted (its the Euro RUU, not for your Verizon version). But download the htc_fastboot.exe where it says: 2. Download htc_fastboot.exe here : https://drive.google.com/file/d/0B8L...dKVEdHX1U/view
Then do as it says:
Make a folder say "RUU" on your desktop and put both RUU zip and htc_fastboot.exe in this RUU folder
fastboot reboot-bootloader (reboot to bootloader to ensure the connection is good)
fastboot oem rebootRUU (put the device in RUU mode)
htc_fastboot flash zip RUU.zip (to install RUU)
I already stated in Post #4 above that none of the current ROMs will work on your device.
You're also making it harder for folks to help you, if you don't give any details. What ROMs did you try exactly (link them if you can)? What are the specific error messages, and at what point do they fail?
But flashing a ROM is contradictory to what you were originally trying to do (return to stock). Do you want to return to stock, or flash a custom ROM? Is the intent in flashing a ROM to just get the phone back up and running?
You need to pick one path, and stick with it; at least for a bit. Flip flopping back and forth is just going to complicate matters, and cause more problems.
For instance, if the bootloader currently relocked or unlocked? You need to have it relocked in order to RUU (as I previously stated) but having it unlocked is needed if you want to flash custom ROMs.
Click to expand...
Click to collapse
Sorry for being so vague about everything. So I guess all the RUUs that I tried flashing failed because of bootloader. I just relocked it and it worked. It was giving me error: 99 or unknown error when I tried any RUU including stock ones. And right now I just want my phone to work again haha. Now that I have that, I would like to return my phone to non-rooted, because some apps/games I have detect root somehow and I would like to use my phone to access them. After getting a working OS on my phone, how would I be able to return it to stock, and maybe install cyanogenmod?
Thanks for the help.
edit: Actually nevermind. My phone is unrooted now lol. Again thanks for the help

So you were able to successfully RUU? If so, which one?
TheOnlyLite said:
Again thanks for the help
Click to expand...
Click to collapse
There's a button for that.

redpoint73 said:
So you were able to successfully RUU? If so, which one?
There's a button for that.
Click to expand...
Click to collapse
So I flashed the 5.0.1 rom on that first link you provided with the official stock roms, but I'm sure the other ones would have worked. I was severely outdated with the one I flashed and had to update like 10 times to get back to the most recent ota lol.

Htc m9 bootloop after flashing recovery...

Hello,
So i wanted to uptade my htc m9u to 7 nougat. i unlocked my bootloader then i flashed twrp recovery and installed root, but when i tried to reboot it remains stuck on loop with logo screen and the red text under it...what can i do?
i found some useful files here: androidfilehost.com/?w=search&s=3.36.709.3&type=files
this is the file that passed the loop: boot_3.36.709.3_root.img....but now my touchscreen is not working at all...
please help...
thanks...

Are you aware that only certain versions of twrp work with certain firmwares.
You need to try to return your phone to its stock state. See flippy's or sneakyghosts threads for help before you completely knacker your phone.
Beamed in by telepathy.

I did not know that only certain version of twrp work with my firmware....
I found a stock recovery for my version i flashed it but it is still looping bootscreen...
In the bootloader it says. Unlocked s-on software status:modified

That may be because you flashed all sorts.. As I already said, you need to go back to stock state with the proper ruu for your phone otherwise you dont know what is stopping the phone from booting so it'll stay like that.
Most likely you've flashed a firmware for the wrong device and that'll be it, dead phone.
As far as I know, you can't flash standard m9 firmware on an m9u.
Beamed in by telepathy.

Ok...but i flashed one stock that paseed the bootloader but the touch is not working...what can i do?
That means that i have a bricked phone ...it cant be undone?

shivadow said:
As far as I know, you can't flash standard m9 firmware on an m9u.
Click to expand...
Click to collapse
Not sure how you define "standard" but the M9u is a overall name for the GSM M9 that doesn't distinguish between hima_ul and hima_uhl. The version with SKU 709 is the same as the 401 one if you look at the hardware.
@Tymmybike: As already mentioned by shivadow, read my thread (and flash a RUU).
However, I don't know what you've been doing there or why you've been doing it. If you want to update your phone's firmware you just need to use the software update function of the stock rom. Flashing TWRP and rooting your phone doesn't make any sense at all since they can break the OTA function if not used correctly due to the block-based OTAs that google introduced with android 5.
And just for the record: The bootloop probably got caused by flashing an incompatible SuperSU version. You wouldn't be the first who did that mistake.
Sent from my HTC One M9 using XDA Labs

I made that mistake too.. I make a lot of mistakes.. Dont know if you noticed.. Its quite difficult..
Beamed in by telepathy.

Flippy498 said:
Not sure how you define "standard" but the M9u is a overall name for the GSM M9 that doesn't distinguish between hima_ul and hima_uhl. The version with SKU 709 is the same as the 401 one if you look at the hardware.
@Tymmybike: As already mentioned by shivadow, read my thread (and flash a RUU).
However, I don't know what you've been doing there or why you've been doing it. If you want to update your phone's firmware you just need to use the software update function of the stock rom. Flashing TWRP and rooting your phone doesn't make any sense at all since they can break the OTA function if not used correctly due to the block-based OTAs that google introduced with android 5.
And just for the record: The bootloop probably got caused by flashing an incompatible SuperSU version. You wouldn't be the first who did that mistake.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I can't find the correct RUU for my model:
kernel: lk
product: htc_himauhl
version: 1.0
version-main: 3.36.709.3
boot-mode: download
version-baseband: 01.01_U11440792_97.00.51203G_F
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: HTC__032
i tried from sku 709 and says didn't match cid, also the one in 401 is not working either...
what can i do?
Flippy498 i wanted to uptade normally but it said: your phone is not using a stock rom or sometging like that.

Tymmybike said:
I can't find the correct RUU for my model
version-main: 3.36.709.3
mid: 0PJA10000
cid: HTC__032
i tried from sku 709 and says didn't match cid, also the one in 401 is not working either...
what can i do?
Flippy498 i wanted to uptade normally but it said: your phone is not using a stock rom or sometging like that.
Click to expand...
Click to collapse
That doesn't surprise me if I look at the data you gave me. (For your own safety: remove your IMEI from your post, btw.) Your CID doesn't belong to your SKU. Is the phone S-OFF? I guess you bought it second hand since it looks like the previous owner borked it. However, the problem should be fixable.
What do you mean with you tried "the one" 401 RUU. There are 7 different 401 RUUs in the ReadMe thread. Try to flash the 3.x one. If that isn't possible and if the phone isn't S-OFF then you'll need to use sunshine for getting S-OFF and being able to fix the phone. If you're lucky and the previous owner used sunshine, as well, then you won't have to pay, again.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
That doesn't surprise me if I look at the data you gave me. (For your own safety: remove your IMEI from your post, btw.) Your CID doesn't belong to your SKU. Is the phone S-OFF? I guess you bought it second hand since it looks like the previous owner borked it. However, the problem should be fixable.
What do you mean with you tried "the one" 401 RUU. There are 7 different 401 RUUs in the ReadMe thread. Try to flash the 3.x one. If that isn't possible and if the phone isn't S-OFF then you'll need to use sunshine for getting S-OFF and being able to fix the phone. If you're lucky and the previous owner used sunshine, as well, then you won't have to pay, again.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i tried to flash the 3.35.401.12 and it's not working...
for what and why i have to pay?
how do i install sunshine? because i saw it's a .apk

"Doesn't work" can mean anything. What's the exact error message?
Sunshine gets installed like any other apk. Open the file with a file explorer on your phone and let android install the app. It's a paid app. That's why I said you might need to pay. However, that might be unnecessary if your phone already is S-OFF.

Flippy498 said:
Well, it would help if you would use the correct RUU for your firmware and not just a random one...
Sunshine is a paid app.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
i tried to install 3.36.709.3 but is not working because it has the wrong cid, like you said i think the previous owner messed it up.
i downloaded form the sunshine website the latest apk(when do i have to pay), sorry but i dont't understand...how can i install the apk if my phone is not booting?
sorry if i am annoing but i can't seem to understand...

Tymmybike said:
i tried to install 3.36.709.3 but is not working because it has the wrong cid, like you said i think the previous owner messed it up.
Click to expand...
Click to collapse
Yeah, I know. I edited my last post. I confused this thread with another one I'm currently writing in. Sorry. If the phone isn't booting then you aren't able to install/use sunshine.
Edit: Didn't you say earlier that you got out of the bootloop? Is your bootloader still unlocked? Is TWRP still installed? If the last two questions can be answered with yes you could restore the stock backup that corresponds your current firmware via TWRP. This would at least solve the bootloop problem. If needed, you could then use the sunshine app to set the phone S-OFF.

Flippy498 said:
Yeah, I know. I edited my last post. I confused this thread with another one I'm currently writing in. Sorry. If the phone isn't booting then you aren't able to install/use sunshine.
Click to expand...
Click to collapse
well when i installed the 3.35.401.32 from cid: HTC__032 it says: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
when i intsall the 3.36.709.3 from vid CID: HTC__621 it says: 7 RU_CID_FAIL cid in android-info mismatched

As far as I know there is no 3.35.401.32 RUU. I guess that's just a typo and you meant a 12 at the end, didn't you?
Is the phone S-ON or S-OFF? Depending on that answer we would need to set it S-OFF before we can continue (c.f. the edit of my last post)...

Flippy498 said:
As far as I know there is no 3.35.401.32 RUU. I guess that's just a typo and you meant a 12 at the end, didn't you?
Is the phone S-ON or S-OFF? Depending on that answer we would need to set it S-OFF before we can continue (c.f. the edit of my last post)...
Click to expand...
Click to collapse
yeah it wa a typo i meant 12
the phone is s-on
i got out of bootloop if i flashed boot_3.36.709.3_root.img but the touchscreen is not working at all....
the bootloader is unlocked and the twrp is still installed(i installed it now)....

Alright. Then restore the backup that corresponds to your current firmware version. Files and instructions are located in the ReadMe thread. After that you need to install the sunshine app and get S-OFF. Then you need to follow the conversion guide in the ReadMe thread. Choose the CID and the RUU according to the firmware that you actually want to use. If you want to use the 401 firmware then please try HTC__001 instead of the CID that your phone is using at the moment. After that your phone should be fixed.
Sent from my HTC One M9 using XDA Labs

help me fast please! cannot install RUU.EXE OR ZIP (stucked on white screen logo)

hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
when i set up ruu.exe after two steps of the setup by click (next)..nothing happen!(although my htc m8 in the black and grey screen logo)
can you help me friends ?what can i do?by the easiest way.
thank you

audi19844 said:
hello,
i really need help because my htc m8 stuck in ( htc white screen logo ) after trying installing a custom rom.
now i want to restore stock rom and i tried more methods but it failed.
i downloaded both of ruu exe and zip file
Click to expand...
Click to collapse
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.

redpoint73 said:
Your post creates far more questions in my head, than answers.
It would make far more sense to try to figure out what went wrong with the custom ROM install, since that is what you were trying to accomplish from the start.
Most issues flashing custom ROM are due to outdated firmware on phone, old version TWRP, or wrong variant of M8. To determine which of those applies to you, we would need more info:
What custom ROM did you try to install? What version TWRP?
Also need to do fastboot getvar all, and post the results (delete IMEI and serial number).
If you still want to use the RUU:
How do you know it was the proper RUU version for your M8 variant (there are dozens)?
What is the file name or version number of the RUU(s) you tried?
Also need the getvar info indicated above, to know more info about the M8 variant, and therefore what determine what RUU to use.
You also need a relocked bootloader to RUU (unless the phone is s-off). But if it is still unlocked, I would recommend you leave it that way, and instead try to troubleshoot why the custom ROM is not working, rather than going backwards and relocking the bootloader, RUU, etc.
Also, when flashing a custom ROM, you should always make a backup in TWRP of the existing (such as stock) ROM before trying to flash a custom ROM. If you had done that, you could just restore the TWRP backup you made, instead of messing with RUUs.
Click to expand...
Click to collapse
Thank you for your importance,
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong

audi19844 said:
For now a successful ruu.zip flash done by HTC fastboot command prompt.
But the system looks like HTC one m7 Rom!!
Not the HTC m8
What is the wrong
Click to expand...
Click to collapse
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?

redpoint73 said:
I asked a number of questions, zero of which you answered. I can't help you, if you don't provide any useful information. You haven't given a single piece of information about your device or the files you tried to flash. How do you think anyone can help you?
Click to expand...
Click to collapse
sorry for missing information .
- i tried to install ( [ROM][UNOFFICIAL] LineageOS 15.1 for HTC One M8 )
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
-my big fault also was not making backup for my stock rom.
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
the rom utility cannot update your android phone please get the correct rom utility and try again)
i tried to flash the ruu.zip by htc fastboot,and after many times it was succeeded to be flashed by htc fastboot
so this is my htc info
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4*********
(bootloader) imei: 3591970********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__M27
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
thank you for your patience.

audi19844 said:
sorry for missing information .
Click to expand...
Click to collapse
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
audi19844 said:
-by twrb recovery 2.7.0.2 may be the recovery was old and i get fail when flashing the rom,so i sucked in the recovery between cant flash the custom rom or returning to the stock one.
Click to expand...
Click to collapse
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
audi19844 said:
so i thought after that to use the ruu.zip files or ruu.exe
i tried to flash the ruu.exe but after 2 steps i see that (
erorr 130 model id error
Click to expand...
Click to collapse
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
audi19844 said:
the ruu zip file i used was this one ( RUU-4.16.401.10-0P6BIMG.zip )
i dont know if this is true or not one.
the ruu file was successfully flashed but the result was the (m7) like software not m8
Click to expand...
Click to collapse
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?

redpoint73 said:
No worries. Thanks for providing the info. You're doing much better now. Now we can get somewhere!
That version is really old, over 3 years old. It's not compatible with current ROMs, and not compatible with your current firmware (which is Marshmallow as shown in the getvar output).
Fail to flash the ROM is an expected result.
If you still want to flash Lineage, you need to flash a more current version (latest is TWRP 3.2.1-0) which you can get from here: https://dl.twrp.me/m8/
But you've also flashed an old RUU, and downgraded the firmware to Lollipop. It's probably not a big deal, but you're going backwards here. You might also find that you need to play around with TWRP versions to get one that works with Lollipop firmware. Not sure, but I think TWRP 3.2 (maybe earlier even) or later does not play well with Lollipop. And the 2.7 is way too old. So a version in between may be needed (2.8.7 is tried and trusted in many cases).
Probably better to RUU back to Marshmallow (I'll describe that below). Then from there, you can flash latest TWRP and then Lineage, if you like.
Sounds like you are flashing multiple RUU versions. But we can't troubleshoot the error message, if you don't tell us what RUU's resulted in the error. RUU 4.16.401.10 clearly didn't give you that error, since it works. So it must have been other RUUs that you trie.
First of all, as the error message makes clear, the RUU for the wrong model (or wrong Carrier ID also) will result in RUU failure.
Also, flashing RUU's randomly, without knowing if it is the right one for your device is really dangerous, and can result in permanent damage if you flash the RUU for the wrong M8 version!
Be aware that flashing RUU (and some other things) is very risky with s-off, if you don't know exactly what you are doing!
You flashed the Lollipop RUU. You basically downgraded the OS, as you started with Marshmallow. That is probably why you think the software looks like that of the M7.
The Marshmallow RUU is here:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
After that, if you still want to flash Lineage, put TWRP back on the phone (such as version 3.2.1-0) and you should be able to flash Lineage successfully. I assume your bootloader is still shown as UNLOCKED on the bootloader screen?
Click to expand...
Click to collapse
I would like to thank you for your big help, thank you very much
I successfully used Marshmallow RUU
and my phone is now ok.
I learned now what i shoud do next time before installing a custom rom.
Thank you again.