Develop Bugs

HTC one M8 software probliem

Hi there im new with htc phones i have buy htc one m8 and there was 4.4.3 android operating system when i buy there was unlocked bootloader but s-on and i have tryed install with twrp android 5.0.1 but its only boots once and bick after reboot so i wanna stock rom to use phone normal and all the rom's ruu dosn't installs i get error so can any one say what firmware version are for my htc ? here is bootloader info
imei:
imei2: Not Supported
meid: 00000000
product: m8_ul
platform: hTCB
modelid: 0P6B10000
cidnum: ORANGB10
battery-status:Good
battery-voltag
partition-layoout:Generic
security: on
build-mode: SH
boot-mode: FAS
commitno-bootl
hbootpreupdate
gencheckpt: 0
After Xperia phone this phone gives me to many questions about software ...

Ainster said:
was unlocked bootloader but s-on and i have tryed install with twrp android 5.0.1 but its only boots once and bick after reboot
Click to expand...
Click to collapse
You need to update your firmware to run Android 5.0 ROMs.
Ainster said:
all the rom's ruu dosn't installs i get error
Click to expand...
Click to collapse
What error number(s)?
You need to run the RUU that matches your CID and MID. It sounds like you may have tried more than one (and possibly RUUs not meant for your CID,MID).
Also, since you are s-on, you need to relock the bootloader to RUU. This is done with fastboot, using the command: fastboot oem lock
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
Ainster said:
here is bootloader info
imei: Delete
imei2: Not Supported
meid: 00000000
product: m8_ul
platform: hTCB
modelid: 0P6B10000
cidnum: ORANGB10
battery-status:Good
battery-voltag
partition-layoout:Generic
security: on
build-mode: SH
boot-mode: FAS
commitno-bootl
hbootpreupdate
gencheckpt: 0
Click to expand...
Click to collapse
You left out much of the important getvar data, while leaving in something you should never post online (IMEI) since its personal data. I've notified the mods to delete your IMEI.

I have deleted imei i got error that ruu cant read bootloader if i remember 199 error and what kind of information you need to help me find what software match for my htc ? By the way i was tryed with locked bootloader still same error

Ainster said:
i got error that ruu cant read bootloader if i remember 199 error
Click to expand...
Click to collapse
Not familiar with that error. Are you sure that is what it says? You can run the RUU again to make sure.
Ainster said:
what kind of information you need to help me find what software match for my htc ?
Click to expand...
Click to collapse
hboot number
main version number
What RUUs you are trying.

redpoint73 said:
Not familiar with that error. Are you sure that is what it says? You can run the RUU again to make sure.
hboot number
main version number
What RUUs you are trying.
Click to expand...
Click to collapse
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .

Ainster said:
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Click to expand...
Click to collapse
I don't know if there is an RUU for your CID. I'm guessing no.
If that is the case, you can try to return to stock 4.4.2 ROM (for your CID) and stock recovery, OTA update all the way up to Lollipop (which will update the firmware). Then you can run the current custom ROMs.

redpoint73 said:
I don't know if there is an RUU for your CID. I'm guessing no.
If that is the case, you can try to return to stock 4.4.2 ROM (for your CID) and stock recovery, OTA update all the way up to Lollipop (which will update the firmware). Then you can run the current custom ROMs.
Click to expand...
Click to collapse
So i whould try the RUU of 4.4.2rom with this CID ? By the way did i need to find my cid rom becouse when i buy phone there was unoficial rom with sence ... And bootloader unlocked only this CID can match on my htc ?

Ainster said:
So i whould try the RUU of 4.4.2rom with this CID ? By the way did i need to find my cid rom becouse when i buy phone there was unoficial rom with sence ... And bootloader unlocked only this CID can match on my htc ?
Click to expand...
Click to collapse
You can flash most 4.4.2 ROMs (stock or custom), and it will at least get the running again.
If you can find an RUU for your CID, it doesn't matter which build. It will re-image all software and firmware. The only restriction is that you cannot go backwards ("downgrade") with s-on. Otherwise, you can RUU to 4.4.3, 4.4.4 or 5.0. But the RUU must match your CID and MID.
The only way to change CID and MID is with s-off. S-off is by sunshine, and requires a device that can boot into OS.

Ainster said:
hboot - 3.16.0.0000
CID - ORANGB10
But no main versions its showing nothing i have tryed many off RUUs can you give me one RUU with ones you thin should work ill try and say all the errors if i get them .
Click to expand...
Click to collapse
Try changing you CID. Just connect your device to a computer and open ADB. Boot your phone into fastboot (it should say "Fastboot USB"). Then copy paste:
fastboot oem writeCID T-MOB010
Sent from my HTC One_M8 using XDA Free mobile app

note_3_t-mo said:
Try changing you CID. Just connect your device to a computer and open ADB. Boot your phone into fastboot (it should say "Fastboot USB"). Then copy paste:
fastboot oem writeCID T-MOB010
Click to expand...
Click to collapse
You need s-off to change CID.

Tryed one got error 130 model id error so id dosn't match ... Maybe some one have ideas how to find RUU with same ID and CID ? Becouse HTC is hard to find Sony much easyer download xperia firm and choose any of words rom's on htc I dosn't think sometink like that program are ??? Or any other solutions maybe with out S-Off?

Ainster said:
Tryed one got error 130 model id error so id dosn't match ... Maybe some one have ideas how to find RUU with same ID and CID ?
Click to expand...
Click to collapse
It seems you are just running RUUs without much reason or methodology? Any saying "one" gave you an error without any info on which RUU doesn't tell us enough for us to help you properly.
The carrier name is usually indicated in the RUU file name, plus the build number is also indicated. For instance, it looks like ORANGB10 corresponds to software build numbers xx.xx.69 where the "69" is specific to your CID. Therefore, you want to be looking for an RUU with the build number xx.xx.69 in the filename, assuming such an RUU exists.
But honestly, I've searched around and don't seen any reference to an RUU for ORANGB10, so I'm inclined to believe you are looking for something that doesn't exist.
Ainster said:
Or any other solutions maybe with out S-Off?
Click to expand...
Click to collapse
I've already given you 2 solutions that will work with s-on:
1) Flash a stock or custom ROM with Android 4.4.2 base, using TWRP. This will at least get the phone bootable again. The firmware will still be outdated, and you won't be able to run any current ROMs. But at least the phone will work.
2) Revert to the stock nandroid backup you made before flashing any ROMs, if you made one (and you really always should before flashing any ROMs on any Android device). From there, return to stock recovery, and you should be able to OTA update in order to update firmware.
Stock recovery files can be found here: http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
Note that if the exact stock recovery for your main/build version is not available, the recovery for the same "base" should work (as noted in Post #3 of the above linked thread). Example, if your stock main version is 1.54.69, than any stock recovery corresponding to build 1.54.xx should work.
3) If you didn't make a nandroid backup, you can try to find the stock nandroid for your CID. You will want the stock nandroid that corresponds to your present main version, which you say is not listed (common TWRP bug) but based on your hboot number (3.16) your main version is proabably 1.xx
I don't see a stock nandroid posted for your CID on the following threads. So you may post to one of those threads, and see if someone can post a nandroid for you:
http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The goal here is to get back to the stock ROM (and the build number that corresponds to your firmware) and stock recovery, same as Method 2 above. Then OTA up to Lollipop in order to update firmware.
4) Get the phone running again, per Method 1 above. Then run sunshine to S-off. Once you have s-off you can "manually" update the firmware. It seems you want to avoid paying for sunshine. But if none of the above methods are satisfactory, this may be your last option.

redpoint73 said:
It seems you are just running RUUs without much reason or methodology? Any saying "one" gave you an error without any info on which RUU doesn't tell us enough for us to help you properly.
The carrier name is usually indicated in the RUU file name, plus the build number is also indicated. For instance, it looks like ORANGB10 corresponds to software build numbers xx.xx.69 where the "69" is specific to your CID. Therefore, you want to be looking for an RUU with the build number xx.xx.69 in the filename, assuming such an RUU exists.
But honestly, I've searched around and don't seen any reference to an RUU for ORANGB10, so I'm inclined to believe you are looking for something that doesn't exist.
I've already given you 2 solutions that will work with s-on:
1) Flash a stock or custom ROM with Android 4.4.2 base, using TWRP. This will at least get the phone bootable again. The firmware will still be outdated, and you won't be able to run any current ROMs. But at least the phone will work.
2) Revert to the stock nandroid backup you made before flashing any ROMs, if you made one (and you really always should before flashing any ROMs on any Android device). From there, return to stock recovery, and you should be able to OTA update in order to update firmware.
Stock recovery files can be found here: http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
Note that if the exact stock recovery for your main/build version is not available, the recovery for the same "base" should work (as noted in Post #3 of the above linked thread). Example, if your stock main version is 1.54.69, than any stock recovery corresponding to build 1.54.xx should work.
3) If you didn't make a nandroid backup, you can try to find the stock nandroid for your CID. You will want the stock nandroid that corresponds to your present main version, which you say is not listed (common TWRP bug) but based on your hboot number (3.16) your main version is proabably 1.xx
I don't see a stock nandroid posted for your CID on the following threads. So you may post to one of those threads, and see if someone can post a nandroid for you:
http://forum.xda-developers.com/showthread.php?t=2701376&highlight=orangb10
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
The goal here is to get back to the stock ROM (and the build number that corresponds to your firmware) and stock recovery, same as Method 2 above. Then OTA up to Lollipop in order to update firmware.
4) Get the phone running again, per Method 1 above. Then run sunshine to S-off. Once you have s-off you can "manually" update the firmware. It seems you want to avoid paying for sunshine. But if none of the above methods are satisfactory, this may be your last option.
Click to expand...
Click to collapse
The reasion why im not takes backup of my stock androdi that there was other android system not stock this is freands phone hes buy it in shop but when he buy it phone was unlocked and with other wersion of android not stock one and thet was 4.4.3 android with ones dosn't get updates by default and google play dosn't connect to servers .
Yes searching for that RUU is hard no probliem i have installed 4.4.2 with recovery good thing phone works.
I read about sunshine its easyest way when s-off but there is another probliems thanks for help ill check all the things what you writted me .

Ainster said:
The reasion why im not takes backup of my stock androdi that there was other android system not stock this is freands phone hes buy it in shop but when he buy it phone was unlocked and with other wersion of android not stock one and thet was 4.4.3 android with ones dosn't get updates by default and google play dosn't connect to servers .
Yes searching for that RUU is hard no probliem i have installed 4.4.2 with recovery good thing phone works.
I read about sunshine its easyest way when s-off but there is another probliems thanks for help ill check all the things what you writted me .
Click to expand...
Click to collapse
You can start with 1.54.69.5 backup.
Then do multiple OTA 1.54.69.5 --> 1.70.69.2 --> 2.26.69.1 --> 3.33.69.1 --> 4.19.69.3
Don't have time to upload my TWRP backups but you can get a Philz recovery backup here (belongs to someone else) - https://drive.google.com/file/d/0BxUEBSB4XdsRa3RoS3JBVjVQREk/edit
Please note you need Philz recovery installed then restore the backup which already include a stock recovery in it. Restore (select all) then do OTA.

One M8 GPE unable to do OTA

Hello all,
Newbie to the forum. I bought a refurbished HTC one M8 (European version), the phone was already rooted with super SU. I managed to install GPE 5.1 rooted version from GraffixNYC, though however when I checked for OTA update via software updates in the phone, there was an incremental update waiting for 23 MB (LMR1). When I tried to install to update, phone goes to the regular android update screen and goes into error (with the android logo). I tried a few times in vain.
Need your advice how do I get the OTA update back and running
Cheers.

Root, custom recovery (TWRP), and wrong ROM (not the ROM for your CID, MID) will all make the OTA fail.
Basically, your current setup is not suitable for OTA. You would need an unrooted stock (Sense) ROM that corresponds to your CID/MID, and stock recovery for OTA.
If your intent is to stay with GPE, your choices are:
1) Flash GPE ROM that incorporates the update, if/when that is available
2) S-off and "fully convert" the phone to GPE by RUU.

redpoint73 said:
Root, custom recovery (TWRP), and wrong ROM (not the ROM for your CID, MID) will all make the OTA fail.
Basically, your current setup is not suitable for OTA. You would need an unrooted stock (Sense) ROM that corresponds to your CID/MID, and stock recovery for OTA.
If your intent is to stay with GPE, your choices are:
1) Flash GPE ROM that incorporates the update, if/when that is available
2) S-off and "fully convert" the phone to GPE by RUU.
Click to expand...
Click to collapse
Thanks for the response.
I am quite new to all this. Sorry about it. But I know that I want to stay with GPE. My phone is S-OFF and I also unlocked the bootloader. Also changed the CID to GOOGL01 already. Only then I went ahead to flash the GPE ROM. Would you be able to help me with the steps of what should I be doing next to get regular OTA updates?
Perhaps is it something like this?
1. Change CID and Flash stock sense rom?
2.Change back CID to GOOGL01 and flash GPE non-rooted ROM this time?
3. With this I can check if OTA is successful?
Forgot to add I already tried flashing GPE non-rooted ROM on top of my exisiting set up. It didnt go through, it stops "Sending ZIP" and doesnt do anything. Am I missing something?
Thanks again

My responses below in red font:
deeepraveen said:
I am quite new to all this. Sorry about it.
The absolute best thing to do when you are new to this, is to read and research, and read and research some more. Learn and understand, and gain a basic level of knowledge before modding the phone, or you can really get yourself into trouble. Especially with s-off, you can easily brick the phone if you do something wrong!
But I know that I want to stay with GPE. My phone is S-OFF and I also unlocked the bootloader. Also changed the CID to GOOGL01 already. Only then I went ahead to flash the GPE ROM.
Meaning you flashed a ROM zip in TWRP? Or you ran an RUU application from PC? If you flashed a ROM in TWRP, the steps you describe are odd, expensive, and unecessary (you don't need s-off or Google CID to flash a GPE ROM).
Would you be able to help me with the steps of what should I be doing next to get regular OTA updates?
Perhaps is it something like this?
1. Change CID and Flash stock sense rom?
2.Change back CID to GOOGL01 and flash GPE non-rooted ROM this time?
3. With this I can check if OTA is successful?
No, don't do this. Its overly complicated, and won't work, for a variety of reasons. Now that I understand you want to stay GPE (and with OTA updates) what you (in brief) want to do is:
a) Make sure you model ID (MID) is one of the acceptable ones listed in the thread: http://forum.xda-developers.com/showthread.php?t=2708589
b) RUU to "fully" convert the phone to GPE. You may need to flash the (MM GPE) firmware first (then RUU again) if you get Error 155. Flashing firmware is described in the same GPE RUU thread.
c) You should then be on official GPE Marshmallow; and get OTA update, if there is one.
Forgot to add I already tried flashing GPE non-rooted ROM on top of my exisiting set up. It didnt go through, it stops "Sending ZIP" and doesnt do anything.
Again, I'm confused about whether you are trying to install a ROM or an RUU. ROM and RUU are very different things. A ROM isn't installed from the computer, you flash it in TWRP. What is the exact name of the file you are trying to install?
Click to expand...
Click to collapse
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
You should also do fastboot getvar all, and post the output (delete IMEI and serial number before posting). That info will let me verify a lot of info on the phone, and see better what you've done.

redpoint73 said:
My responses below in red font:
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
You should also do fastboot getvar all, and post the output (delete IMEI and serial number before posting). That info will let me verify a lot of info on the phone, and see better what you've done.
Click to expand...
Click to collapse
Thanks so much for that detailed explanation.
Please see my response below.
Meaning you flashed a ROM zip in TWRP? Or you ran an RUU application from PC? If you flashed a ROM in TWRP, the steps you describe are odd, expensive, and unecessary (you don't need s-off or Google CID to flash a GPE ROM)
---- I ran RUU from PC, basically the refurb phone was running 5.0.1 with some mod and rooted when it arrived. I went ahead and ran RUU from my PC and flashed 5.1 from graffix website after unlocking the bootloader thats all I did.
Please see my getvar all results and advise me further on what to do.
C:\Users\One M8\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.122s
C:\Users\One M8\platform-tools>

deeepraveen said:
---- I ran RUU from PC, basically the refurb phone was running 5.0.1 with some mod and rooted when it arrived. I went ahead and ran RUU from my PC and flashed 5.1 from graffix website after unlocking the bootloader thats all I did.
Click to expand...
Click to collapse
Okay, now I better understand what you did. Installing RUU is completely different from flashing a ROM, so avoid using the terms interchangeably, to avoid confusion:
Flash ROM: 2 partitions (system and boot.img) flashed in TWRP custom recovery
RUU: Complete system re-image, around 40 partitions, done by PC fastboot RUU mode or SD card method (again, in fastboot RUU mode). Cannot be installed by TWRP.
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
You can't OTA with root, so that is probably your main problem.
Installing the unrooted RUU 4.04.1700.6, then OTA is probably your best bet. And your current configuration looks okay to RUU.
deeepraveen said:
I already tried flashing GPE non-rooted ROM on top of my exisiting set up. It didnt go through, it stops "Sending ZIP" and doesnt do anything.
Click to expand...
Click to collapse
This is a somewhat common issue. Try killing the process, and starting again. If the problem persists (stalls at "sending") try a different USB port or cable. Or try the SD card method (if you have an SD card) described in the GPE RUU thread as "Method 2".
You can also try one of the Marshmallow RUUs 5.07.1700.x, but if you get Error 155, you may need to flash the 5.07.1700 firmware first (also described in the GPE RUU thread) then run the RUU again.

redpoint73 said:
My responses below in red font:
---------- Post added at 09:55 AM ---------- Previous post was at 09:52 AM ----------
You should also do fastboot getvar all, and post the output (delete IMEI and serial number before posting). That info will let me verify a lot of info on the phone, and see better what you've done.
Click to expand...
Click to collapse
redpoint73 said:
Okay, now I better understand what you did. Installing RUU is completely different from flashing a ROM, so avoid using the terms interchangeably, to avoid confusion:
Flash ROM: 2 partitions (system and boot.img) flashed in TWRP custom recovery
RUU: Complete system re-image, around 40 partitions, done by PC fastboot RUU mode or SD card method (again, in fastboot RUU mode). Cannot be installed by TWRP.
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
You can't OTA with root, so that is probably your main problem.
Installing the unrooted RUU 4.04.1700.6, then OTA is probably your best bet. And your current configuration looks okay to RUU.
This is a somewhat common issue. Try killing the process, and starting again. If the problem persists (stalls at "sending") try a different USB port or cable. Or try the SD card method (if you have an SD card) described in the GPE RUU thread as "Method 2".
You can also try one of the Marshmallow RUUs 5.07.1700.x, but if you get Error 155, you may need to flash the 5.07.1700 firmware first (also described in the GPE RUU thread) then run the RUU again.
Click to expand...
Click to collapse
Thanks again, that did it. Flashed the 6.0 firmware, but still was unable to flash 6.0. However though I managed to flash non-rooted 5.1 instead and bingo. I got the OTA for 6.0. Works great.
Cheers.

HTC M9 bricked after udpate ...can't see the end of it

Hello,
I bought an HTC M9 Hima uhl yesterday, and of course as soons as home I checked the latest official rom available and the one installed on my phone.
Mine was 2.10 something and I saw there was a 3.35 on some website.
So first things before playing to much with the phone, update to last official rom.
First I unlocked the bootloader, S was already OFF and it is SUPERCID.
I downloaded this RUU...exe and started the update. Everything went fine until 50% of the update, and I got an error saying my device is not the correct model for this udpate.
You could not check that before starting the update!?!?!?!
Indeed, the RUU I got was fro HIMA UL and not UHL ! A mistake on the website I downloaded the file from... and I did not check it ...:crying:
My phone is now stuck on the HTC first splash screen, I can access download mode etc...
It seems this update messed with my phone as now, in download mode it says it is himaulatt !!! not himauhl anymore! (but still unlocked, supercid and S-off)
So I managed to find an 0PJAIMG 3.35 fro Hima uhl, I used HTC_fastboot to udpate my phone again, but each time I got this error:
(bootloader) HOSD CL#669696
(bootloader) ERR Model ID not matched
(bootloader) ERR [SD_UPDATE_ERR] MODEL ID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 10
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 10
(bootloader) [email protected]
FAILED (remote: 10 RU_MODELID_FAIL modelid in android-info mismatched )
I don't get it, if I am supercid it should not be a problem, right? Or is it because the first update messed with the model ID ?? (himaulatt instead of himauhl)
I tried the same thing with a 1.32v of an 0PJAIMG image... but still the same problem.
I also tried with TWRP but it says it cannot find the carrier and something wrong with the zip file.
Right now I am trying to get a RUU for HIMA UHL, downloading it....
But if anyone has an other idea of what I can do... please help:crying:
Thank you so much!!!

Change your MID to PJA11000.
fastboot oem writemid 0PJA11000
run RUU again.

side_flip15 said:
Change your MID to PJA11000.
fastboot oem writemid 0PJA11000
run RUU again.
Click to expand...
Click to collapse
Thanks I will try
What is this MID ?
SHould I run RUU UHL or UL will be ok this time?
Is it going to put back the correct model HIMA UHL in the bootloader?

Error 157 with the same RUU HIMA UL ... same error than before actually

and now with a RUU HIMA UHL (ASIA_TW) error 155 :crying::crying::crying:
That was my last solution... I don't know what to do now:crying:

Here is my bootloader screen after the first update with HIMA UL (while it was hima uhl):
Some errors !
Before it was fine

This > dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
This will convert your M9 to dev edition.
here's the link fyr..
http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123

side_flip15 said:
This > dl3.htc.com/application/RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.12.exe
This will convert your M9 to dev edition.
here's the link fyr..
http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
Click to expand...
Click to collapse
Actually this is exactly this RUU I downloaded first and with which I had this error and my phone bricked
So this HIMA UL or HIMA UHL is not important ? I can use both is ok?

Actually, I finally managed to flash a 0PJAIMG but an UHL version, unfortunately it is a 1.35 version for the rom ....
I have downloaded again the RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35. 617.12.exe
And again it stopped at 75% (stuck there for half an hour, no activity anymore) this time with no error message until I unplugged the usb cable and I got an error 155.... and of course my phone was bricked again..
Now I am reflashing the 0PJAIMG and I am trying to find the same in a more recent version..

The error you got during first ruu is because your MID does not match with the ruu. That is why I asked you to change MID.
Also you should never interrupt RUU flashing. You might end up with a paper weight device.
In the images you attached looks like you are alread in the latest dev edition firmware. Easiest possible option you can do is flash twrp recovery and flash custom rom of your choice.
Get the latest twrp img here
Flash in download mode
fastboot flash recovery <filename.img>
Download rom your choice and flash in twrp

side_flip15 said:
The error you got during first ruu is because your MID does not match with the ruu. That is why I asked you to change MID.
Also you should never interrupt RUU flashing. You might end up with a paper weight device.
In the images you attached looks like you are alread in the latest dev edition firmware. Easiest possible option you can do is flash twrp recovery and flash custom rom of your choice.
Get the latest twrp img here
Flash in download mode
fastboot flash recovery <filename.img>
Download rom your choice and flash in twrp
Click to expand...
Click to collapse
I did change the MID as you ask me to do, but I still have an error if I do so, Error 157. I did not interrupt RUU update, it was totally crashed.
I tried to use TWRP to flash a custom ROM but here again it fails or I got stuck on the splash screen.
So here is what I managed to do:
-I went back to a stock rom HIMA UHL (1.32) and I finally got my phone working ( I had to put back my MID to 0PJA10000) => this put back my bootloader in order, no more error and back to himauhl.
-I flashed the international Firmware for HIMA UHL (3.35.401.12 with TWRP included)
-I flashed Leedroid ROM latest version and everything is fine !!:laugh:
I still have this question, I feel it is not possible to change an HIMA UHL WWE to HIMA UL Developer. Let me know if I am wrong but each time I tried it bricked my phone and messed with my bootloader.

Mittel said:
I did change the MID as you ask me to do, but I still have an error if I do so, Error 157. I did not interrupt RUU update, it was totally crashed.
I tried to use TWRP to flash a custom ROM but here again it fails or I got stuck on the splash screen.
So here is what I managed to do:
-I went back to a stock rom HIMA UHL (1.32) and I finally got my phone working ( I had to put back my MID to 0PJA10000) => this put back my bootloader in order, no more error and back to himauhl.
-I flashed the international Firmware for HIMA UHL (3.35.401.12 with TWRP included)
-I flashed Leedroid ROM latest version and everything is fine !!:laugh:
I still have this question, I feel it is not possible to change an HIMA UHL WWE to HIMA UL Developer. Let me know if I am wrong but each time I tried it bricked my phone and messed with my bootloader.
Click to expand...
Click to collapse
Yes you can. Mine is actually converted from WWE Asia.
You don't really need to go back to 1.32, you're already in 3.35 firmware looking at the images you posted. You just need to flash TWRP and flash Leedroid ROM. Saves you a lot of time but glad you made it work again.

side_flip15 said:
Yes you can. Mine is actually converted from WWE Asia.
You don't really need to go back to 1.32, you're already in 3.35 firmware looking at the images you posted. You just need to flash TWRP and flash Leedroid ROM. Saves you a lot of time but glad you made it work again.
Click to expand...
Click to collapse
Ok weird that each time I did my phone ended bricked even after changing MID etc....
Thanks anyway for the help

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.

Boot Loop directly into Fastboot Carrier Unlocked HTC One M8

Morning,
I've been into this phone for two days now, the phone would not Update OTA to Android 6 it was on stock 4.4.4 so I figured I'd install the RUU from HTC's site, I unlocked the bootloader and acquired S-OFF, I tried several RUU's (GEp, UNlocked/dev, android 5, 6, even tried to go back to stock 4.4, I know I'm doing many things wrong so I now ask for direction) since I knew nothing about CID and MID, the exe's did not work and the zips would flash via fastboot oem rebootRUU I even (regrettably) flashed several firmwares as it stands now with most hopes lost my phone has this values:
Bootloader is "relocked" since it was said to be required for RUU.
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eee2521c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, I can no longer unlock the bootloader using my Unlock_code.bin file, nor can I install a recovery image I get a "FAILED (remote:" error each time.
Thanks.

This is really bad. This looks to be a result of improper research by your part, and I hope the damage is not permanent (although it may possibly be).
Reason I say this, is that your product ID (m8_whl) indicates you have the Sprint version M8. This version is fairly unique (along with Verizon M8) in that its designed to work on the Sprint CDMA network (along with GSM networks). Due to this, the Sprint version has different partitioning and different radios from most other "GSM" M8 versions. And one should never attempt to convert a Sprint M8 to any other version; by flashing another version's RUU or firmware.
I also do not recommend ever changing the MID on the Sprint device (from its original MID), as there is no valid, safe reason to do so (for reasons mentioned above).
Mods with s-off can be extremely dangerous, as they can result in bricking your phone. You may already have a permanent radio brick (as we've seen happen after folks have flashed another version's RUU or firmware to a Sprint M8). The moment you started having trouble flashing an RUU, you should have backed off, and come here for help. Guessing, and trying multiple random things (like RUUs/firmwares) on these devices, especially with s-off, is a recipe for disaster.
When you say "boot loop" do you mean the phone is actually restarting itself over and over to fastboot? Or it simply can't boot to OS, and goes to fastboot (and if you manually reboot it, it goes again to fastboot)?
---------- Post added at 12:10 PM ---------- Previous post was at 12:07 PM ----------
Herzchell said:
Bootloader is "relocked" since it was said to be required for RUU.
Click to expand...
Click to collapse
This is only a requirement when s-on. Relocking the bootloader to RUU not needed when s-off. With s-off, you can RUU with the bootloader unlocked.
---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------
Herzchell said:
nor can I install a recovery image I get a "FAILED (remote:" error each time.
Click to expand...
Click to collapse
You can try it a million times, and it won't make a difference. You can't install custom recovery with bootloader locked or relocked. That is the exact reason to have a locked bootloader, to prevent custom recovery from being installed.

Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?

Herzchell said:
Thank you for your answer, got the thing unlocked again and restored a previous backup I made, the phone would restart constantly so I flashed the stock kernel for the phone, its back to how it was first.. I think..
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
for a sprint device with the things you have made you are so lucky :laugh:
Any way all you need is in this thread flash firmware then flash the RUU
https://forum.xda-developers.com/showthread.php?t=2729173
Edit: you maybe need to revert mid to it's stock but try it if it fail revert it
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.

Herzchell said:
OK Ismael, I kind of got that idea last night so I got this file "Sprint_HTC_One_M8_1.54.651.8_RUU.zip" which coincides with the kernel I installed "1.54.651.8", also, this RUU seems to be the oldest they have there so I would think it's as stock and back in time as I'm going to get.
I'm cautious now though, it was hard to get back to where I am now.
Click to expand...
Click to collapse
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
either ways you need the firmware and the RUU,pick a version of those according to your device ( it won't harm if you pick wrong ) and flash both firmware and RUU by following the thread instruction
You don't need anything else ( i hope )
and don't relock the bootloader ( you don't need that as long is your device s-off )
Sent from my HTC M8 using XDA Labs
Click to expand...
Click to collapse
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"

Herzchell said:
Thanks, I'll try that, should I change my CID to install RUU's, I was under the impression that a super CID overrides the need for a specific CID, the RUU I mentioned before complains about "FAILED (remote: 24 parsing android-info fail)"
Click to expand...
Click to collapse
error 24 means one of the following
1- the .zip is corrupted
2- the .zip is an OTA package ( and it can't be flashed in fastboot mode )
3- android-info.txt have something wrong ( if this is the meant error you will need to change the cid and mid )
so you can tell which one of those is the meant error
about cid it's correct that it eliminate the needs of a specific cid ( and in some cases it passes the mid check )

ahmed.ismael said:
you need the latest not the oldest
download 6.20.651.3 if your device non h/k
Download 6.20.654.3 if your device h/k
Click to expand...
Click to collapse
Since the OP is SuperCID, I believe he can pick either. Same model hardware, the only difference is software.
---------- Post added at 10:34 AM ---------- Previous post was at 10:30 AM ----------
Herzchell said:
The phone appears to be rooted ir something because it still wont update OTA and that was the problem un the first place, any advice?
Click to expand...
Click to collapse
Most US carriers, you can only OTA update if connected to that specific carrier (in this case, Sprint).
That being the case, your best bet is to RUU to latest Marshmallow image, as ahmed instructed.
And since RUU is a fully image (not just an update "patch") it doesn't matter the current configuration (as long as CID, MID checks pass or bypassed). Meaning you don't need to install any "older" RUUs before the current MM one.

Thanks,
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
You have both been very helpful.

Herzchell said:
The phone is running marshmallow now, the only issue I have now is that the bottom speaker does not reproduce sound.
Click to expand...
Click to collapse
Did this phone have an issue with the speaker before you started messing around with it?