Develop Bugs

[Q] One M8 HTC__001 CID, Firmware/No Wifi problem

Hello, I've been a long time xda lurker (Never thought I could really add much anyhow) since I had my Dell Streak and I think for the first time since I got my M8 I need a bit of help.
They rolled out the lollypop OTA update here in Ireland and figured It was time to update to a stock ROM from here or a slightly improved one but ever since then I have lost my WiFi completely.
Sorry If this makes no seance- at all I'm a little burnt out trying to solve this on my own but even going back to 4.4.3 ROMs I still have no WiFi at all and any help at all would be greatly appreciated.
This is all the info I took from fastboot and the bootloader I thought would be needed
Bootloader Info
*** Tampered ***
*** Unlocked ***
M8_UL PVT SHIP S-ON
HBOOT - 3.18.0.0000
RADIO - 1.19.21331147A1.09G
OpenDSP - v38.2.2-00542-M8974.0311
OS - 2.22.401.4
Fastboot Getvar All Info
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.19.21331147A1.09G
version-cpld: None
version-microp: None
version-main: 2.22.401.4
version-misc: PVT SHIP S-ON
serialno: xxx
imei: xxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 5e4b24e4
hbootpreupdate: 11
gencheckpt: 0
Thanks again for even looking!

First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10

If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone

ckpv5 said:
First - remove the serial no. & imei no. as those are sensitive info.
The details that you have does not show that you did OTA. You are still two versions behind.
Restore your stock ROM, flash a matching stock recovery (no custom recovery) then do OTA ... multiple OTAs up to the latest 4.16.410.10
Click to expand...
Click to collapse
Thank you I didn't even think of that I edited them out.
EddyOS said:
If you're willing to set the phone up from scratch you can just update straight to Lollipop using the RUU available on here. If you want to go that route then you can following this guide I wrote:
http://forum.xda-developers.com/showthread.php?t=2735235
Basically, step 3 covers what you need to do as step 1 and 2 are already done and at least once that's done if you still have issues you know it's not the software on the phone
Click to expand...
Click to collapse
I will try that right away thank you for your help I'll post back here when I'm done

No luck, kept getting error 99 with the 'htc_fastboot" from the thread and with my normal fastboot it gives me the error 32 'header error' I only noticed the thread was for s-off phones, I don't care about my phone saying tampered, unlocked or anything but I'm assuming that's stopping the flash from happening.

You must relock your device first ... then try again with flash the ruu.zip

Isotopes said:
You must relock your device first ... then try again with flash the ruu.zip
Click to expand...
Click to collapse
Haha yeah that worked now, ignoring the guide at the start and just leaving it with the relocked warning it's flashing now via the RUU
Thanks to the both of you for your help.

[Q] AT&T M8. Worst case scenario, basically. Phone recoverable?

****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.
The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVD SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.14.21331931.LA02_2G
OpenDSP-v32.2.2-00542-M8974.0213
OS-2.12.1700.1
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Here's the output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45P
(bootloader) imei: 35871
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.131s
If anyone has advice, I'd appreciate it. Thanks!

Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.

redpoint73 said:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.
Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.
An AT&T RUU should work.
Click to expand...
Click to collapse
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.

BaconSupreme said:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.
Click to expand...
Click to collapse
That's because I reported to the mods to delete the personal data.
BaconSupreme said:
It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work..
Click to expand...
Click to collapse
Your CID and MID are the correct one for AT&T.
BaconSupreme said:
If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
Click to expand...
Click to collapse
That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:
http://forum.xda-developers.com/showthread.php?t=2751432

Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Thanks for the help, redpoint.

BaconSupreme said:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.
Click to expand...
Click to collapse
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
BaconSupreme said:
Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!
Click to expand...
Click to collapse
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.

redpoint73 said:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Instead of incorrectly sending you to the "bootable" RUU.
Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).
You actually never mentioned what the original issue with CWM was. Did it not boot?
I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
Click to expand...
Click to collapse
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.

Please Help: HTC One M8

Its been few days that I am going through HTC M8 forums and nothing seems to help. I got a HTC One M8 which is rooted now there are updates available but they won't install because its a custom software and I should revert to Official stock.
My Question is Simple, How can I revert to original stock?
My Phone is S-OFF
****Unlocked****(But I can lock if needed)
Software Number: 4.16.401.10
HTC Sense 6.0
CID:1111111
I have TWRP recovery 3.2 installed.
Somebody, anybody please give me a link to Rom that will take me back to official and Can I actually install Marshmallow?
Any help is appreciated.
:::Life is so much easier with samsung but I just love this phone.

cryptdweller said:
Its been few days that I am going through HTC M8 forums and nothing seems to help. I got a HTC One M8 which is rooted now there are updates available but they won't install because its a custom software and I should revert to Official stock.
My Question is Simple, How can I revert to original stock?
My Phone is S-OFF
****Unlocked****(But I can lock if needed)
Software Number: 4.16.401.10
HTC Sense 6.0
CID:1111111
I have TWRP recovery 3.2 installed.
Somebody, anybody please give me a link to Rom that will take me back to official and Can I actually install Marshmallow?
Any help is appreciated.
Click to expand...
Click to collapse
Excellent guide and needed files to return to stock for OTA: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Now the question is, which stock backup and recovery do you need to use? Is the version number you posted (4.16.401.10), the OS number shown on the bootloader screen (this is what you want to match) or is it the software number in Settings?
No need to relock bootloader to OTA. And since you are s-off, there is really no reason to relock; and I do not recommend relocking (it actually doesn't "enable" anything to relock, that s-off already doesn't allow - but if you relock, that will prevent you from flashing things like custom recovery).
cryptdweller said:
:::Life is so much easier with samsung but I just love this phone.
Click to expand...
Click to collapse
Every device has its nuances, and learning curve. When I got my first Samsung device, I didn't know what Odin or any of that was, and had to learn.

thank you mate, I'll go through the link and i hope it works...
Oh its the Software number in the setting that I have written here, can I download any rom or should I match the number?
Thank you again.

cryptdweller said:
thank you mate, I'll go through the link and i hope it works...
Oh its the Software number in the setting that I have written here, can I download any rom or should I match the number?
Click to expand...
Click to collapse
You definitely can NOT install any ROM, if you want OTA updates. You need to match the version number shown under "OS" on the bootloader screen.
Additionally, SuperCID does not make the phone "universal" (as you suggested in your PM to me). You need to match the firmware version number (OS number on bootloader screen, as mentioned) and you need to also match MID, in order for OTAs to work.
What does it say for OS on the bootloader screen?
If you installed a custom ROM, the software number in Settings won't match the OS number on the bootloader screen. The software number in Settings just refers to the custom ROM, which is pretty much irrelevant when returning to stock for OTA.

M8_UL PVT SHIP S OFF
CID 111111111
HBOOT - 3.19.0.0000
OS:4.28.502.1
How do I check the MID?

cryptdweller said:
M8_UL PVT SHIP S OFF
CID 111111111
HBOOT - 3.19.0.0000
OS:4.28.502.1
How do I check the MID?
Click to expand...
Click to collapse
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting). I need to see more info, not just the MID, in order to see what's going on. Reason being, the OS number (x.xx.502.x) is for the AT&T version, but the product ID is not (AT&T version is M8_UL_CA).

< waiting for device >
(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: 4.28.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(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: 6768a7b1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.197s

Wow, well it looks like it was originally a T-Mob US version, made s-off and SuperCID, flashed with AT&T firmware, and Euro based custom ROM installed.
Complicated, eh?
How you return to "stock" (and what "stock" means) is somewhat up to you, and also the requirements of your local carrier.
Do you know what bands your carrier uses for 3G and LTE?

Serious problem

Hi,
A few weeks ago my M8 developed a serious problem - basically all calling functionality stopped working. The android basic dialer get's stuck dialing a number and eventually the system presents the standard 'Dialer is not responding' message, calling my number from another phone always gets an engaged tone, Skype and Whatsapp calling fails without any error messages. Also data connection fails, text messaging fails intermittently, music player fails to play through speakers and fails intermittently through Bluetooth.
This didn't occur after the install of any apps and the phone didn't experience any physical shocks, but seemed to happen after a Skype call.
Naturally, I tried factory reset first, but to no avail.
As the phone is now out of warranty I rooted it and installed the Android Revolution ROM onto it. (PS thanks to everyone for the wealth of help and guides to carrying this out.) I was hoping a new ROM would fix the problem, but it hasn't.
So, I'm assuming the problem is at a very low level, with some device driver(s).
My question is, does the ROM include all of the device drivers? Do I need to do something else to get the basic device drivers reinstalled? I note the download site for the Android Revolution ROM also has links to firmware downloads - should I also install the firmware download?
Any help would be much appreciated.
usmhot

I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
I'd try RUU, if you M8 version has one. Otherwise, yes, I'd try to flash firmware, than re-install stock or custom ROM onto the phone. I don't think the AR firmware collection is very current. I'd use the stock, signed firmwares from ckpv5's thread (post #5): https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you need help determining if your version has RUU, or what firmware number to use, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0

Bump. Can anyone tell me if there is an RUU available for my variant?
usmhot said:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.29.214500021.12G
version-cpld: None
version-microp: None
version-main: 6.13.771.4
version-misc: PVT SHIP S-ON
serialno:
imei:
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: H3G__001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 76df2b54
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse

usmhot said:
Mine's an Irish (so I assume international) variant - so I'm not sure if there's an RUU available (some google result seemed to imply HTC only release RUUs for the States??)
Click to expand...
Click to collapse
Some other versions (besides US) have RUU, but unfortunately I don't think your version (H3G) is one of those.
One idea, which I touched upon before, is to flash the firmware (since you don't think flashing the ROM alone won't help - the firmware is basically the "lower level drivers" you are talking about), then restore a stock TWRP backup (ROM). Its as close to a RUU "factory image" as you'll get, since there is no RUU (that I am aware of).
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.

redpoint73 said:
To do this, you'll need to relock the bootloader, and flash the 6.13.771.4 from Post #5 of the following thread:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Then you'll need to unlock the bootloader again, install TWRP back to the phone (flashing the firmware overwrites TWRP with stock recovery). Then flash the stock TWRP backup 6.13.771.4 from Post #3 of the same thread, using instructions in Post #1.
Click to expand...
Click to collapse
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
i.e. using the following sequence of commands
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
Click to expand...
Click to collapse
but it's not working for me - it still shows as *** Unlocked ***
Couple of things:
1. if I issue the command adb devices (after a full reboot to system) first I get an error message "adb server version (31) doesn't match this client (36)" and my device id is listed anyway, but if I reissue the command I get my device id listed without the error. Do I need a different version of adb?
2. do I need to unroot as well as relock? (If so, is there a guide somewhere?)

usmhot said:
I've had a go at relocking the bootloader following the instructions in http://www.droidviews.com/how-to-reset-unlocked-status-to-locked-on-htc-one-m8/
Click to expand...
Click to collapse
You're making much harder on yourself than need be.
The process to relock the bootloader is in the instructions for flashing the firmware, which I already directed you to (Post #5 of the previously linked thread). Near the bottom of that post, below all the download links (so maybe you missed seeing the instructions).
Relocking the bootloader is a single, easy fastboot command:
fastboot oem lock
This will make the bootloader say RELOCKED, which is sufficient to flash the firmware.
The guide you linked is to make it say LOCKED (versus RELOCKED) and the only reason to do that is to fool HTC into thinking it was never UNLOCKED for warranty purposes. You don't need to do this, and you can't since the guide clearly says s-off is required, which you do not have (you are s-on).

Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.

usmhot said:
Sorted :good:. And it did indeed fix the core problem with the dialer etc. I know have an apparently fully working phone again.
Many many thanks for this.
Click to expand...
Click to collapse
Glad it worked. You're quite welcome, and happy to have helped!

Need help updating M8 to Marshmallow

I have a 'new in the box' M8 that appears to be an AT&T UK model
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OTA does not show any updates available (I am in the USA), and none of the RUU or ROM.zip files I can find for AT&T, unlocked, sense, Google, etc will run without failing.
Can anyone please walk help me find the necessary files, fix any settings already in the phone and walk me through updating/changing the phone to US AT&T or, preferably, Sense Marshmallow.
Thanks.

dale_j said:
I have a 'new in the box' M8 that appears to be an AT&T UK model
Click to expand...
Click to collapse
I think you mean "US model" as there is no AT&T UK model.
dale_j said:
(bootloader) version-main: 3.28.401.9
(bootloader) modelid: 0P6B63000
OTA does not show any updates available (I am in the USA), and none of the RUU or ROM.zip files I can find for AT&T, unlocked, sense, Google, etc will run without failing.
Click to expand...
Click to collapse
I think your main problem is that your firmware number (3.28.401.9) doesn't jive with your model ID (0P6B63000), therefore preventing any OTA updates, or RUUs from being run.
dale_j said:
Can anyone please walk help me find the necessary files, fix any settings already in the phone and walk me through updating/changing the phone to US AT&T or, preferably, Sense Marshmallow.
Click to expand...
Click to collapse
Is AT&T your carrier. And do you want the AT&T branded stock ROM, or no?
---------- Post added at 10:06 AM ---------- Previous post was at 10:05 AM ----------
You should also delete your IMEI and serial number from your post, as these are private info.

redpoint73 said:
I think you mean "US model" as there is no AT&T UK model.
I think your main problem is that your firmware number (3.28.401.9) doesn't jive with your model ID (0P6B63000), therefore preventing any OTA updates, or RUUs from being run.
Is AT&T your carrier. And do you want the AT&T branded stock ROM, or no?
---------- Post added at 10:06 AM ---------- Previous post was at 10:05 AM ----------
You should also delete your IMEI and serial number from your post, as these are private info.
Click to expand...
Click to collapse
According to HTC's warranty site, the serial belongs to an AT&T phone from the UK/Europe.
My carrier is US AT&T through NET10, so I need the AT&T APN info, but would prefer either plain vanilla android or HTC's SENSE version, and can edit that info once the phone is running Marshmallow.
Following another thread here, I tried using adb shell to change the MID to 0p6b61000. The shell went to a $ prompt and not the # prompt the instructions called for. I tried 'us' as suggested and got a 'not found' response. I still tried the lengthy command listed, and got a restricted/locked/no permission/etc. (can't remember exact wording) response.
I joined HTC's DEV, so I could unlock the bootloader, and tried everything above and all the ROM files I have both as RRU and as ROM.zip on the SD card with the bootloader locked, unlocked and again with it relocked.
I did try editing out the serial and imei yesterday. I will try again after replying here.
I have an email into HTC's tech and so far no response from them.
Thanks again,
Dale

dale_j said:
According to HTC's warranty site, the serial belongs to an AT&T phone from the UK/Europe.
Click to expand...
Click to collapse
Probably a mistake. No AT&T in UK or Europe. And your product code m8_ul_ca signifies AT&T US or US Developer's Edition.
Doesn't really matter, in any case.
dale_j said:
My carrier is US AT&T through NET10, so I need the AT&T APN info, but would prefer either plain vanilla android or HTC's SENSE version, and can edit that info once the phone is running Marshmallow.
Click to expand...
Click to collapse
Based on that description, I'd suggest the US Developer's Edition RUU (6.12.1540.4). It is unbranded Sense, but already has the proper radio bands and APN setup for AT&T.
dale_j said:
Following another thread here, I tried using adb shell to change the MID to 0p6b61000. The shell went to a $ prompt and not the # prompt the instructions called for. I tried 'us' as suggested and got a 'not found' response. I still tried the lengthy command listed, and got a restricted/locked/no permission/etc. (can't remember exact wording) response.
Click to expand...
Click to collapse
Is the phone rooted? It needs to be, to change the MID. I'm guessing that is why you aren't getting the # prompt.
dale_j said:
I joined HTC's DEV, so I could unlock the bootloader, and tried everything above and all the ROM files I have both as RRU and as ROM.zip on the SD card with the bootloader locked, unlocked and again with it relocked.
Click to expand...
Click to collapse
If using the SD card install method, did you rename the RUU to 0P6BIMG.zip
With s-off, the RUUs will work whether the bootloader is locked or not. So it's kind of a waste of time changing it back and forth. I'd suggest leaving it unlocked, as that gives you the most options.
Also, most the Marshmallow RUUs for the US versions, have a weird requirement, where the firmware (hboot, radio, etc.) need to be updated, before the RUU will work.
So my suggestion would be:
1) Root and fix the MID to be AT&T/US Dev Edition
2) Flash the 6.12.1540.4 firmware from here: https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
3) Flash the 6.12.1540.4 RUU

What is the easiest/safest way to root my M8?
Thanks,
Dale

dale_j said:
What is the easiest/safest way to root my M8?
Click to expand...
Click to collapse
With bootloader unlocked, flash TWRP 3.1.1 using fastboot. Then flash SuperSU 2.82 in TWRP.
https://twrp.me/devices/htconem8gsm.html
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

Thank you for all the help.
I have Marshmallow DEV running on the new M8, but still have a couple questions and possible help issues.
Current getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Should the bootloader version still be the same and not a newer version?
Is there a newer DEV version? AT&T ver is 6.2.................. DEV is 6.1...............
Will there be any connection issues with the baseband not matching the 4.0.U605................... version in my original AT&T M8?
Will it matter that the security patch level on the original AT&T M8 is 2016-13-01 and the new (now DEV) M8 is 2015-12-01?
What is the best free app to transfer everything between the phones?
I tried HTC's builtin app, but custom ringtones, alarms, WiFi connections and PWs, custom wallpapers and about 60% of my phone contacts did not transfer. I ran the app twice.
I also could not get the NFC transfer to work. WiFi, BT and NFC were all on on both phones, however following the instructions on the screen (tap and hold backs together until sound signals) did nothing with several tries and holding them together in excess of 5 minutes.
Thanks again for all the help,
Dale

My responses below, in red font:
dale_j said:
Is there a newer DEV version? AT&T ver is 6.2.................. DEV is 6.1...............
No newer Dev Ed version. 6.12 is the last (final) one. I wouldn't have suggested it, if there was a newer one.
The difference in the numbering between Marshmallow AT&T versus Dev Ed is probably not too significant. Probably based on the same software base, just that AT&T takes so darned long to test and approve the updates (plus adding their branding and bloat), so it was one of the last MM updates to be released. In other words, not really a newer "version" in any significant way. Just released later.
Will there be any connection issues with the baseband not matching the 4.0.U605................... version in my original AT&T M8?
I wouldn't expect any. AT&T and Dev Ed are supposed to support the same bands. I've often wondered why AT&T version uses the strange baseband numbers (most other use 1.25, 1.29, etc.). But again, I suspect the actual differences are minimal or none.
Will it matter that the security patch level on the original AT&T M8 is 2016-13-01 and the new (now DEV) M8 is 2015-12-01?
Not sure if the patch date for the Dev Ed is correct. It would mean the patch level was almost a year old (when the RUU was released Dec. 2015), which is a bit excessive.
In the big picture, we are using Android versions with patch levels that are over a year old (unless you run an AOSP based custom ROM). So technically, there are more vulnerabilities (newer patch level is better). But how much difference this actually makes in practice is debatable.
In any case, I wouldn't personally run the AT&T stock ROM, just because it has a newer patch level (if that is what you are thinking). I personally hate the AT&T branding and crappy bloatware, it just wouldn't be worth it to me.
What is the best free app to transfer everything between the phones?
I tried HTC's builtin app, but custom ringtones, alarms, WiFi connections and PWs, custom wallpapers and about 60% of my phone contacts did not transfer. I ran the app twice.
I would recommend storing your contacts via Google. This way, it's on the cloud, and always backed up (automatically, and requires no additional action by you), and easily accessed. When you setup a new Android phone, and login to your Google account, your contacts will automagically just sync to the phone. It's one of the great things about Android. Doing it this way, might not be for everyone (for instance, you might have work and personal contact you like to keep separate). But I personally love it.
Files such as ringtones and wallpapers can be easily migrated. Literally, you can just copy and paste them. But you'll need an intermediary place to put them. Whether that be on a computer, cloud, etc. is up to you. It can be as simply as connected the "old" phone to a PC, copy/paste the desired files. Then connect the "new" phone to PC, and drag/drop the files to the correct locations.
WiFi connections and passwords, I don't usually migrate. I don't have that many of them, so I literally just enter them in again, when migrating to a new phone. Titanium Backup (requires root) and some other apps can migrate such data (as well as apps and app data).
Click to expand...
Click to collapse

Thanks again.
That is largely what I was thinking/hoping.
I also hate bloatware, and wanted the DEV edition instead of a branded AT&T (or anyone else's) version.
Unrelated to this thread:
For what I do, I really like the M8, plus it is within my price range now that it is a few years old. Have you tried any of the custom Android 7 ROMs? If so, is there one you would recommend for the M8. I thought I would play around with the old phone and Nougat now that I have a good running phone again.
I love tinkering and challenges, so I am also going to try replacing the battery and charging port in the old phone. According to the couple YouTube videos I watched., it looks like it is well within the scope of my skill set.
Many thanks for your help with my M8, and any future help.
Dale

dale_j said:
Have you tried any of the custom Android 7 ROMs?
Click to expand...
Click to collapse
I haven't. I have been mostly a Sense user on this device, therefore it's stuck on Marshmallow.
There is a thread in the M8 General forum section, discussing ROM recommendations. You might check that out.