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.

can't flash any costum rom after screen fix

after 8 hours traying to fix it i'm done and need help/advice
i tray to mak it short as possible:
Htc M8 previous Hongkong covertet to
m8_ul, cidnum: HTC__001 and modelid: 0P6B10000 Unlocked SOFF running MM wolla
screen got crashed => first fix came back with screen ok but no camera and no ext Sd card
second Fix came back with everything working but
M8_TL, cidnum: HTCCN(somthing more) and modelid: 0P6B5000 Locked SON running stock chines LP rom
ok, i tough: no problem going back to europe WWE.
so, now im Unlocked, SOFF (need to pay twice because they change something in the hardware) and supercid
but wile changing the Modelid i get always 00 to much! i tray 0P6B10000 and 0P6B12000 and get 0P6B100000 and 0P6B1200000
but what disturb me more is the fact i cant flash any custom rom without bootloop. or even going directly in to bootloader by flashing just boot from a nandroid backup i go one step further but stock in the boot screen.
i flashed already firmware 4.16.401.10 and 6.12.1540.4 twice and tray lots of Wolla version and SD MM ROM version and my MM nandroid all end in bootloop the
only the SD10.2 LP with a boot from a original nandroid came to live. What should i do first to get the ModelID right and second how to fix the aditional flashing boot issues and MM bootloop. Can i somehow change M8_TL back to M8_UL?
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.24_2G
version-cpld: None
version-microp: None
version-main: 6.12.1540.4
version-misc: PVT SHIP S-OFF
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_tl
platform: hTCBmsm8974
modelid: 0P6B1200000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

Sounds like a good mess. I conjecture that your phone's board was entirely changed on that "second fix"; hence, the different mid, fw, etc...
I also think you've somehow ended up with incoherent data, i.e. unmatching product, software version, mid, etc...
LolliPop 401 MEA firmware (Middle-east Europe Africa), MarshMallow USA software, M8 (China Locked) product name, with some bogus model ID.
Its cool that you got it working. But, I want to suggest that you start over with a full RUU flash That way, you put everything back in order and start fresh. From there on, you can restore a stock MM backup or flash a custom ROM with firmware that corresponds your new model ID.
I hope this helps, and let us know how things turn out.
Cheers
P.S. just curious, did your phone's serial number change after the 2nd repair job?

I did some research and found out that I need different kernel and most likely need also the original firmware for the HTC m8tl
Does anyone know where I can get it from? Even though my name is Chinese I can't understand it
And witch RUU should I try Europe or Chinese L?

ACCORDING the fixer guy they just swap the sister board

I can't honestly claim that I know something about your m8_tl otger than that it should be a network-locked m8 (locked to China Mobile), and runs a different radio chip than m8_ul.
My understanding, however, is that if you intend to run a marshmallow, then you will first need to flash:
1. A marshmallow compatible kernel firmware that corresponds to your specific hardware (m8_tl) that contains radio, bootloader, adsp images, etc...
2. Flash a compatible recovery (since firmware will overwrite your current one): the latest twrp is good.
3. Flash your favorite marshmallow rom. Hopefully, this will come with a kernel.
Here is a link to the spectacular FUU thread. Has great reads in post #4
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792

lu_peng2 said:
I did some research and found out that I need different kernel and most likely need also the original firmware for the HTC m8tl
Does anyone know where I can get it from? Even though my name is Chinese I can't understand it
And witch RUU should I try Europe or Chinese L?
Click to expand...
Click to collapse
Here is a link to stock marshmallow and stock firmware. Make sure you fully read the 1st post, as there are crucial instructions.
http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894

well thanks for both link they would help me yesterday to safe time i was too concerned to change the modelid but with soff and the trick to change it in the firmware zip it doesn't mater at all. And in fact i should't change it from the original one. but anyhow:
my touchscreen has still a spot where it does'nt works well and it is exactly over the virtual keyboard => cant write without turning my phone sideways and back.
=> need a new phone, and the M9 prices are low here., just need carefully check what version i get
thanks, the links i can use in future. the first is fantastic explaining all my doubt from yesterday

My pleasure. I wish you good luck

I had a similar experience with HTC repair, when the screen was broken, while fixing the screen they changed the board and my harman kardon edition came with regular software with boomsound. I had to speak to the next level explaining the mess and finally after many phone calls, I receieved a brand new phone with a different device serial number. I think messing up that way, you may not receive regular software update you tend to receive

shirreer said:
My pleasure. I wish you good luck
Click to expand...
Click to collapse
it can run with a htc_UL and also htc_TL firmware?!? does this means that doesn't mater witch i use?
can i convert it complete to a UL device?

lu_peng2 said:
it can run with a htc_UL and also htc_TL firmware?!? does this means that doesn't mater witch i use?
can i convert it complete to a UL device?
Click to expand...
Click to collapse
The truthful answer is: I don't know
But, evidently, you can run UL software on top of TL firmware. A critical fact is that your TL radio (running TD-SCDMA) isn't the same as the UL's (running GSM/WCDMA). Therefore, you'll need to definitively know whether the UL & TL have the exact same hardware before changing your mid and flashing the UL's firmware.
I hope this helps.

shirreer said:
The truthful answer is: I don't know
But, evidently, you can run UL software on top of TL firmware. A critical fact is that your TL radio (running TD-SCDMA) isn't the same as the UL's (running GSM/WCDMA). Therefore, you'll need to definitively know whether the UL & TL have the exact same hardware before changing your mid and flashing the UL's firmware.
I hope this helps.
Click to expand...
Click to collapse
i already can run a UL software on a UL firmware but need a TL kernel (or a TWRP boot backup from a TL software) or it doesn't boot. what is i the difference between TD and GSM? China mobil is usually GSM just 4G doesn't work

TD-SCDMA is basically a WCDMA implementation that's currently used only in China and only by China Mobile, to which your phone is supposedly locked
Its main technical objective is to provide 3G services in very densely populated areas.
Further Info:
https://en.wikipedia.org/wiki/TD-SCDMA
You shouldn't have any problem running M8_UL software, just don't mess with the radio firmware from M8_TL. It'd be prudent if you have an M8_TL RUU handy, or stock backup + corresponding stock firmware.

shirreer said:
TD-SCDMA is basically a WCDMA implementation that's currently used only in China and only by China Mobile, to which your phone is supposedly locked
Its main technical objective is to provide 3G services in very densely populated areas.
Further Info:
https://en.wikipedia.org/wiki/TD-SCDMA
You shouldn't have any problem running M8_UL software, just don't mess with the radio firmware from M8_TL. It'd be prudent if you have an M8_TL RUU handy, or stock backup + corresponding stock firmware.
Click to expand...
Click to collapse
thanks,
btw i'm running now my old MM Rom with a MM TWRP boot backup from a chines MM ROM that i just install shortly to make a boot backup

How to unroot htc one m8??(thanks Redpoint3)

I got an update from the factory but it wan't work tell i unroot my phone , how can i do that??
guys the problem is more then unroot the device if you have the time read the comments and post any help
thanks

"Themes and apps" is a really weird section to post your question in. I'll ask the mods to move it to "Q&A, Help" where it belongs.
To unroot, you need to restore a stock TWRP backup. Either one you made before rooting, or get one from here (and restore with the instructions):http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can relock the bootloader and RUU (RUU will wipe the phone).

redpoint73 said:
"Themes and apps" is a really weird section to post your question in. I'll ask the mods to move it to "Q&A, Help" where it belongs.
To unroot, you need to restore a stock TWRP backup. Either one you made before rooting, or get one from here (and restore with the instructions):http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can relock the bootloader and RUU (RUU will wipe the phone).
Click to expand...
Click to collapse
Sorry man it was a miss click , how can I move it to other section?

jonasess said:
how can I move it to other section?
Click to expand...
Click to collapse
You don't have the ability to move threads, after they are created. The mods can, and have already moved it to the right section (Q&A). It usually takes someone else to report the thread (which I did), and I don't think you can report your own thread.
But back to the topic at hand, I hope the info I posted was useful to you. Let us know if you have further questions.

redpoint73 said:
You don't have the ability to move threads, after they are created. The mods can, and have already moved it to the right section (Q&A). It usually takes someone else to report the thread (which I did), and I don't think you can report your own thread.
But back to the topic at hand, I hope the info I posted was useful to you. Let us know if you have further questions.
Click to expand...
Click to collapse
Thanks men but there is one thing , the bootloader is already locked I didn't unlock it before , so I was wondering whether I have to unlock the bootloader and install CM13 room or not doing that and unroot the phone because may be there is a chance that the company send an update for 6.0
I only have two questions
Is there is an official update to 6.0 from HTC company?
Or should I go with CM13
Also is there are any risks in bootloader unlock?
I successfully unlocked the bootloader in lg g2 mini before and it was very easy without any big risks
And now with HTC one m8 I don't know if it is the same or not.

My responses below in red font:
jonasess said:
the bootloader is already locked I didn't unlock it before
How did you root? Was it kingroot, or similar root app?
so I was wondering whether I have to unlock the bootloader and install CM13 room or not doing that and unroot the phone because may be there is a chance that the company send an update for 6.0
Is there is an official update to 6.0 from HTC company?
Android 6 came to this phone a really long time ago, about a year ago (Dec 2015) for most M8 versions. If you didn't get the update, it may due to being rooted, which typically prevents OTA update.
Alternately, depending on what version M8 you have, you can just RUU to Marshmallow (Android 6) without unrooting (although it will wipe all data on the phone). Do you know your phone's CID, or at least provide the OS number on the bootloader screen? From that, I can possibly tell you if there is an RUU.
Or should I go with CM13
You're talking about 2 completely different things, unrooting to OTA, or installing a custom ROM. I can't make that decision for you, you need to do it yourself.
Also is there are any risks in bootloader unlock? Not really. The bootloader can still be relocked, and you can restore to stock. I don't recall seeing any brick reports from unlocking the bootloader. The critical "brick" partitions (hboot and radio) aren't accessed by unlocking the bootloader, and any partitions that are accessed (system, recovery, etc.), can be easily rewritten/repaired if anything goes wrong.
Click to expand...
Click to collapse

redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
It wasn't me because i got the phone from a friend , anyway the phone is rooted but the bootloader is locked because when i reboot to the bootloader mode i find it locked
about cid it's 11111111
OS-1.29.708.4
anyway how to unroot the phone , i'm going to try if it is possible to get the official 6.0 from the factory or not
if not i will unlock the bootloader and try to install ROM
so if it is possible i need the way how to unroot the phone and also how to unlock the bootloader
thanks

jonasess said:
anyway the phone is rooted but the bootloader is locked because when i reboot to the bootloader mode i find it locked
Click to expand...
Click to collapse
This doesn't tell me anything, you didn't already post before.
jonasess said:
about cid it's 11111111
OS-1.29.708.4
Click to expand...
Click to collapse
I don't recognize that OS version number. I Googled it, and I think you have the M7, not the M8.

redpoint73 said:
This doesn't tell me anything, you didn't already post before.
I don't recognize that OS version number. I Googled it, and I think you have the M7, not the M8.
Click to expand...
Click to collapse
i didn't get it , because there is a different between m8 and m7
m7 contain only one camera in the back
m8 contain 2 camera in the back
also the m7 doesn't support Card slot , m8 does
and a lot of other different
how could m8 phone contain an os of m7?

This all the information from bootloader mode
*** software status : official ***
*** locked ***
M8_UL_CA PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
[email protected]
openDSP-V47.2.2-00564-118974_F0.1024
OS-1.29.708.4
2MMC-boot 2048MB
mar 20 2015,03:01:11.90025771
Also when i use an app to get the information it gives the CID CWS_001
and the OS version is LRX22C
Also the app shows that the bootloader version is 3.19.0.0000

jonasess said:
This all the information from bootloader mode
*** software status : official ***
*** locked ***
M8_UL_CA PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
[email protected]
openDSP-V47.2.2-00564-118974_F0.1024
OS-1.29.708.4
2MMC-boot 2048MB
mar 20 2015,03:01:11.90025771
Also when i use an app to get the information it gives the CID CWS_001
and the OS version is LRX22C
Also the app shows that the bootloader version is 3.19.0.0000
Click to expand...
Click to collapse
post the result of ( fastboot getvar all ) after removing seialno and imei
this output info will be useful to identify the right path you should take
and the info you already posted is a little mixed up NOT CORRECT
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
post the result of fastboot getvar all after removing seialno and imei
this output info will be useful to identify the right path you should take
and the info you already posted is a little mixed up NOT CORRECT
Click to expand...
Click to collapse
What should I do , where can I get these information? From an app or..?

jonasess said:
What should I do , where can I get these information? From an app or..?
Click to expand...
Click to collapse
*get a working adb&fastboot by going to this thread
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
after installing it with success
*reboot to fastboot and connect your device to pc
*open cmd window
* type ( fastboot getvar all ) and press enter
*post the result here after removing serialno and imei
Sent from my HTC M8 using XDA Labs

ahmed.ismael said:
*get a working adb&fastboot by going to this thread
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
after installing it with success
*reboot to fastboot and connect your device to pc
*open cmd window
* type ( fastboot getvar all ) and press enter
*post the result here after removing serialno and imei
Click to expand...
Click to collapse
Thank I will

This is all the informations
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.708.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s

This phone is a mess. Its the AT&T version (m8_ul_ca), but its been rooted, s-off, SuperCID, and some other firmware installed, or partially installed.
Reason I say "partially installed" is that the firmware number (version-main) 1.29.708.4 isn't one I recognize. But 1.xx main versions typically correspond to KitKat on this device. Which doesn't correspond to hboot 3.19 (which is for Lollipop or Marshmallow), nor the radio number [email protected] which is for AT&T Lollipop firmware.
You should re-baseline this device by RUU. But which RUU is the question. Since you have s-off and SuperCID, you run most RUUs.
The main version "708" corresponds to the Hong Kong version. Is that where you are located? What bands does your carrier use for 3G, and for LTE? These things will determine with RUU to use.

redpoint73 said:
This phone is a mess. Its the AT&T version (m8_ul_ca), but its been rooted, s-off, SuperCID, and some other firmware installed, or partially installed.
Reason I say "partially installed" is that the firmware number (version-main) 1.29.708.4 isn't one I recognize. But 1.xx main versions typically correspond to KitKat on this device. Which doesn't correspond to hboot 3.19 (which is for Lollipop or Marshmallow), nor the radio number [email protected] which is for AT&T Lollipop firmware.
You should re-baseline this device by RUU. But which RUU is the question. Since you have s-off and SuperCID, you run most RUUs.
The main version "708" corresponds to the Hong Kong version. Is that where you are located? What bands does your carrier use for 3G, and for LTE? These things will determine with RUU to use.
Click to expand...
Click to collapse
َAm not sure but i guess it's not AT&T version because i can use any SIM card i want , AT&T version use specific SIM card i guess !!
Any way i'm not from Hong Kong , i use MOBILS SIM card (From the company MOBILIS) for 3g and LTE .
Also i forgot to motion that when i go to software update i find that there is a system update (Software update :4.16.401.13 (57.45 MB)) when i download it , it wan't install because it says (We determine that your phone maybe running a modified version pf 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.

My responses below in red font:
jonasess said:
ÙŽAm not sure but i guess it's not AT&T version because i can use any SIM card i want , AT&T version use specific SIM card i guess !!
You shouldn't be "guessing' anything, and your guesses would be wrong, anyway. As I've already stated, the product ID m8_ul_ca means its US variant AT&T (that product ID also US Developer's Edition, but ATT is much more common). That much is an absolute fact, and not a guess on my part. Being SIM locked or not, has little bearing on what version you have. Any of these versions can be SIM unlocked with the proper code. So stop guessing at answers, as its not particularly useful.
I'll also guess that the back cover has been replaced. As the AT&T version has the AT&T "globe" logo on the back. We've seen a good number of devices "debranded" by having the back covers replaced to remove carrier logos. I'll guess it has a model/carrier number on the back cover, that also doesn't match any of the getvar info.
Any way i'm not from Hong Kong , i use MOBILS SIM card (From the company MOBILIS) for 3g and LTE .
None of this tells me anything useful. What country are you actually from? More importantly, what specific band (or bands) number does your carrier use for 3G, and what band(s) do they use for LTE?
Also i forgot to motion that when i go to software update i find that there is a system update (Software update :4.16.401.13 (57.45 MB)) when i download it , it wan't install because it says (We determine that your phone maybe running a modified version pf 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.
The carrier version of the OTA is Euro (401) so it won't install on a phone what has firmware for the Hong Kong version (708). Additionally, you have to install the OTAs sequentially, without skipping. So if you currently have 1.xx version, you can't skip 2.xx and 3.xx and go straight to 4.xx. In other words, there is no way you will get that OTA to install in your current configuration.
Which is why I am suggesting RUU. The RUUs do not need to be installed sequentially. Its a complete re-image, and it would also fix the mismatch you have between the main version (HK) and the hboot, radio (AT&T Lollipop).
Click to expand...
Click to collapse

redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
I'm from Algeria , i guess my country is not supported from the HTC company .
Also as i said i use MOBILIS sim (http://www.mobilis.dz/) i didn't try the 3g or 4g because i use wifi to connect to the internet
Another qeustion : is that mean i can't unlock the bootloader and install the recovery to install CM rooms
In other word there is a risk for that?
++
thanks for the help

jonasess said:
Also as i said i use MOBILIS sim (http://www.mobilis.dz/) i didn't try the 3g or 4g because i use wifi to connect to the internet
Click to expand...
Click to collapse
Again, you are providing info that doesn't answer the questions I asked; and is not particularly useful. You didn't try 3G or 4G. So what? Does that mean you never want to use them, and will never use cell data? Or otherwise?
The following states that Mobilis uses 2100 MHz for 3g, but doesn't state info on 4G: http://www.worldtimezone.com/gsm.html
You can typically call your carrier, and get the answer to the question.
jonasess said:
Another qeustion : is that mean i can't unlock the bootloader and install the recovery to install CM rooms
In other word there is a risk for that?
Click to expand...
Click to collapse
You should be able to unlock the bootloader. But whether you can run any current ROMs is questionable.
Your firmware is a mess. The old firmware number 1.xx won't work with any current ROMs. You should fix your firmware first. But again, by RUU and I need more info before I can direct you to an RUU.
Also the version TWRP custom recovery you will need to flash custom ROMs, depend on what firmware version you have. And your firmware is all screwed up (seems to be partially modified) so again, its best you fix the firmware by RUU before proceeding with anything else.

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.

Converting Unlocked H10 to latest TMobile Nougat

HI,
I have an Unlocked H10 (soff'd bootloader unlocked w. sunshine), that I want to put the latest TMobile Stock Nougat on, before I attempt to activate and become a new customer. Purpose is to make sure no hitches during activation, afterwards I will use LOS 14.x which I have on the device now sans service.
However I'm having trouble figuring out these final things can anyone please advise:
1 Which RUU to use (I want latest compatible tmobile nougat)
2 What CID to use (supercid 11111111 works for activation ? I read problems with OTA so...)
3 What MID to use (I have no idea)
Phones current info from download page:
*** UNLOCKED ***
htc_pmeuhl PVT S-OFF
CID-HTC__001
MID-2PS620000
ColorID-WHT00 (oddly it's red)
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.8996.00007_0809
OS-2.4.401.4
Jan 25 2017,18:33:04(857212)
thank you very much in advance for any help

In case it helps anyone in future, after much poking around as near as i can tell cid is most likely T-MOB010 mid 2PS650000 and ruu http://dl3.htc.com/application/RUU_PERFUME_UL_N70_SENSE80GP_MR_TMOUS_2.51.531.32.exe
I'll update this with results.

generalnod said:
In case it helps anyone in future, after much poking around as near as i can tell cid is most likely T-MOB010 mid 2PS650000 and ruu http://dl3.htc.com/application/RUU_PERFUME_UL_N70_SENSE80GP_MR_TMOUS_2.51.531.32.exe
Click to expand...
Click to collapse
Hmm the RUU_PERFUME_UL_N70_SENSE80GP_MR_TMOUS_2.51.531.32.exe runs, then eventually just exits no errors, same with any RUU I've tried in fact . Doesn't seem to matter what the CID or MID is, running in download mode doesn't help. Tried restoring phone to full stock including recovery, except for bootloader being unlocked and soff, seems to make no difference.