Develop Bugs

HTC One M8 O2 UK - Help and advice

Hi Guys
This is a n00bish post so please excuse if in wrong forum section. If so please redirect.
I was having really bad battery issues after the last O2 OTA update and my micro USB is borked. Requires me to wiggle and prop USB cable up to get the charger to work. Such a pain. I thought this may due to firmware / OS as it may have been linked to other battery issues. I think this may be due to hardware damage. and a separate issue. I am going to return to HTC but have installed a custom ROM Viper 3.2.
The battery issues have been resolved (still having charging issues possible hardware damage / fault).
After I installed Viper I realised my WiFi no longer worked.
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Phone details
...
(bootloader) cid: O2___001
OKAY [ 0.001s]
finished. total time: 0.002s
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45BWM02810
(bootloader) imei: Mod edit: IMEI removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

odeatomas said:
Hi Guys
This is a n00bish post so please excuse if in wrong forum section. If so please redirect.
I was having really bad battery issues after the last O2 OTA update and my micro USB is borked. Requires me to wiggle and prop USB cable up to get the charger to work. Such a pain. I thought this may due to firmware / OS as it may have been linked to other battery issues. I think this may be due to hardware damage. and a separate issue. I am going to return to HTC but have installed a custom ROM Viper 3.2.
The battery issues have been resolved (still having charging issues possible hardware damage / fault).
After I installed Viper I realised my WiFi no longer worked.
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Phone details
...
(bootloader) cid: O2___001
OKAY [ 0.001s]
finished. total time: 0.002s
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45BWM02810
(bootloader) imei: Mod edit: IMEI removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hi there. I can't really help with your problem, I'm only posting here because I was assigned to move your thread from the general section to the q&a section. I did notice that you included your IMEI number in your post, I've removed it for you, don't ever post your IMEI publicly, or tell anyone what it is. Your IMEI is a unique device identifier, if it falls into the hands of the wrong people they can cause all sorts of problems for you. Anyway, good luck with your problem, just wanted to give you that advice.

odeatomas said:
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Click to expand...
Click to collapse
You can update the firmware or a stock ROM (that matches your current firmware) but you don't need to do both.
I don't think your version has an RUU (many don't).
The stock ROM that matches your current firmware is 1.54.206.5, as determined by main version on your getvar output. The stock nandroid for 1.54.206.5 can be found on the following thread (with instructions to restore found in Post #3 of that thread, under Questions & Answers):
http://forum.xda-developers.com/showthread.php?t=2701376
Also, trial and error while flashing firmware is mostly going to fail, since with s-on you can only flash a firmware with "206" in the third number position (x.xx.206). Also, you need to have the bootloader relocked.
Additionally, I'm not sure how warranty is handled where you are. But in many places, its best practice when returning phone for warranty to s-off (by sunshine) and change the bootloader to LOCKED. UNLOCKED or RELOCKED bootloader in many places will void the warranty. The only way to make it back to LOCKED is with s-off.

odeatomas said:
Hi Guys
This is a n00bish post so please excuse if in wrong forum section. If so please redirect.
I was having really bad battery issues after the last O2 OTA update and my micro USB is borked. Requires me to wiggle and prop USB cable up to get the charger to work. Such a pain. I thought this may due to firmware / OS as it may have been linked to other battery issues. I think this may be due to hardware damage. and a separate issue. I am going to return to HTC but have installed a custom ROM Viper 3.2.
The battery issues have been resolved (still having charging issues possible hardware damage / fault).
After I installed Viper I realised my WiFi no longer worked.
Basically I would like the correct firmware and possibly stock OS ( Any OS that makes WiFi work is good for now)
I have been through quite a bit of searching and trial and error but cant seem to find the right firmware and stock image to to run on my M8.
This is o2 UK specific. A O2 UK RUU would be super.
Phone details
...
(bootloader) cid: O2___001
OKAY [ 0.001s]
finished. total time: 0.002s
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: Mod edit: IMEI removed
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First things first, since I represent Venom ROMs. Your wifi didn't work because you firmware is super old.
Secondly, you extSD is probably borked because you skimped and bought a cheap one. They don't last long.
You USB charging issues are either bad cable, charger, or charging port. The first two are easy fixes, the last is something you'll have to get repaired by a shop or HTC.
You'll have to go back to stock to update being S-On. If you can find a stock backup (or if you have one yourself ~ you should just sayin....) Yo can restore that and get the OTA.
After the OTA is downloaded, copy it from your phone to your PC (it's in the sdcard/download folder probably) and open it with 7zip.
Find the firmware.zip and unzip it. The recovery.img is in there.
Place the .img into your fastboot folder.
Hook up you phone to your PC and get into fastboot (obviously), and enter fastboot flash recovery recovery.img
Then fastboot reboot and disconnect your phone.
Now that you have the stock ROM and recovery, you should be able to flash the stock OTA.

thanks guys all sorted
had the recovery in slightly wrong folder needed to have device serial as the parent folder.
All back to stock and ticking over nicely

Heisenberg said:
Hi there. I can't really help with your problem, I'm only posting here because I was assigned to move your thread from the general section to the q&a section. I did notice that you included your IMEI number in your post, I've removed it for you, don't ever post your IMEI publicly, or tell anyone what it is. Your IMEI is a unique device identifier, if it falls into the hands of the wrong people they can cause all sorts of problems for you. Anyway, good luck with your problem, just wanted to give you that advice.
Click to expand...
Click to collapse
Removing the serial# would also be a good idea.

xunholyx said:
Removing the serial# would also be a good idea.
Click to expand...
Click to collapse
The serial number isn't really a big issue like the IMEI is, the shady types can't really do anything with that.

Desperate: HTC Reboot Hell, even recovery

First of all thanks for anyone who can help me.
I'm quite desperate after spending countless hours on XDA trying to get my phone to work.
I received the phone (international HTC one M8) in a somewhat broken state and I am trying to fix it.
Originally the phone had a 4.4 rom on it which caused the phone to reboot constantly, I couldn't get the rom to update either so I decided to flash it to Marshmallow.
Set S-off, I flashed TWRP and installed the latest Skydragon rom. Wifi wasn't working though so I flashed ruu firmware 6.12.401.4b. The rom worked, Wifi worked, but only downside, it only booted while being charged with a cable, and the sudden reboots started occurring again. So I think the battery might be shotty too. Anyway, I got a device tree warning too, so I reflashed a different Ruu, reboots started occurring even when trying to get to recovery. So I went back to the 6x ruu, tried to flash Skydragon again and then I spiraled into real trouble. Each time I tried to flash a rom, the phone reboots while installing. I even tried the MeID changer to make sure it fits with the firmware.
Long story short, the reboots got worse, I can't get into recovery without rebooting. If I run recovery over fastboot, I get into the recovery, but it reboots when I try to flash anything. I also tried Phil's revovery but same problem.
I can get into fastboot, hboot and bootloader just fine though.
Any help is greatly appreciated.

Need more info to proceed. Please do a fastboot getvar all, and post the results (delete IMEI and serial number before posting).

Sure Thing! Thanks!
(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: 6.12.401.4
(bootloader) version-misc: XF SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: 3XXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Vprnl said:
Sure Thing! Thanks!
(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: 6.12.401.4
(bootloader) version-misc: XF SHIP S-OFF
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: 3XXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
It is indeed an M8_UL which is the GSM/Int version.
However version-mics shows: XF SHIP S-OFF
M8_UL_XF is something I have heard of before on a forum (few pages back, there's a thread with a similar case).
Anyway, an ordinary M8_UL will show 'PVT SHIP S-OFF'.
XF is either a 'different' variant or some type of engineer/prototype device.
What do you think @redpoint73?
Code:
(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: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(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
Here is the getvar all from my M8.
Notice the version-misc.

Thanks @murtaza02, I finally got the damn thing to work because of your comment I realized my CID was bogus and wasn't corresponding with the MID, so I fixed that using fastboot, flashed the EU 6x FUU and the corresponding RUU (https://www.androidfilehost.com/?fid=24369303960687057). And behold, It booted into Marshmellow!!
Now though, the phone still keeps shutting down (not even rebooting) and won't start android without being plugged in. Could this be software related at all? Getvar says the battery is good and when it craps out, (most often when trying to enable WIFI) it shows the battery charging just fine. I still see the device tree warning on boot btw.

Vprnl said:
Thanks @murtaza02, I finally got the damn thing to work because of your comment I realized my CID was bogus and wasn't corresponding with the MID, so I fixed that using fastboot, flashed the EU 6x FUU and the corresponding RUU (https://www.androidfilehost.com/?fid=24369303960687057). And behold, It booted into Marshmellow!!
Now though, the phone still keeps shutting down (not even reboting) and won't start android without being plugged in. Could this be software related at all? Getvar says the battery is good and when it craps out, (even when plugged in) it shows the battery charging just fine. I still see the device tree warning on boot btw.
Click to expand...
Click to collapse
As I said, yours is XF and a normal M8 is PVT.
Your device will accept a MM firmware, however there may be a SLIGHT difference in partition/partition sizes hence the device tree error and irregular behavior.
Your CID was not bogus, it was just SuperCID which is used to bypass the CID check during an RUU/FUU flash.
I'm still trying to figure out why (and how) yours is different.
Sent from my Nexus 6

murtaza02 said:
As I said, yours is XF and a normal M8 is PVT.
I'm still trying to figure out why (and how) yours is different.
Click to expand...
Click to collapse
I don't know much about the XF variant, either. But I recall @ckpv5 pointing out the difference to an XF user a week or 2 ago. So maybe @ckpv5 can jump in and give some advice here?

@redpoint73, Thanks but I fear @ckpv5 might not have any more info to go on. I found his post where he referred to the XF variant. He said it's quite possible a US variant, definitely has different partitioning than the PVT version, but didn't know more. I've also seen posts of people suggesting it's a Canadian version.
I bought it on Aliexpress if that is any lead. But in all honestly, I'm really starting to worry I have an expensive paperweight.
One more potential clue, the Alie page suggests the phone only has WCDMA, no LTE, could that be a lead? Ow and one more clue, the model number on the back of the phone is: OP6B100x

Vprnl said:
@redpoint73, Thanks but I fear @ckpv5 might not have any more info to go on. I found his post where he referred to the XF variant.
Click to expand...
Click to collapse
Can you link the post, so I can take a look? I remember reading the postat the time, but the details are foggy; and maybe there is something useful there.

redpoint73 said:
Can you link the post, so I can take a look? I remember reading the postat the time, but the details are foggy; and maybe there is something useful there.
Click to expand...
Click to collapse
Sure thing! Thanks again!
http://forum.xda-developers.com/htc-one-m8/help/ruu-warning-device-tree-totally-matched-t3356722
Verstuurd vanaf mijn Nexus 6P met Tapatalk

T-Mobile Data dropps every 5 minutes

Hello!
I have an unlocked HTC M8 and I'm using it with T-Mobile. During almost a year I never had any issues with it but since January I having a recurrent issue: I can only have data for a few minutes. To solve it, I need to continuously disconnect and connect data.
During this time, I tried some "solutions" I found online:
_Install different ROM
_Add new APN
_Go to #*#*INFO*#*# and change to US band
The phone is still S-ON so I didn't change the radio (actually there is something that bothers me: the phone should be from T-Mobile but the model number is M8_UL_CA that, accordingly with the internet, it's from ATT...)
I noticed this after I returned from vacations in Portugal where I used a local SIM card...
Does anyone suffer(ed) from the same problem? I'm getting so frustrated...
Thanks

Hello, no one had experienced this before?

I'm on t-mobile with no issues.
Herkatus said:
Hello, no one had experienced this before?
Click to expand...
Click to collapse
To start with I would do the 'adb reboot bootloader' then do the 'fastboot getvar all' and post it (removing the imei and serialno). Mine is below as a reference. Also a little history - my is an actual t-mobile branded phone, I was rooted with lollipop and unrooted and had t-mobile upgrade my phone to MM. Once done I dev-unlocked and then did a backup and have installed custom ROMS. Currently I am using ACIP by coachcrey and I don't have any issues.
-brad
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.213311491.05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: **************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s

Hey brad,
Here's my info:
(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-ON
(bootloader) serialno: *******
(bootloader) imei: *****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I bought the phone on Swappa from a seller that said it was bought from HTC directly. After I start having the issue, I rooted and installed a couple of different ROMs until I decided to go back to stock
Thanks for any help you might give me

Herkatus said:
I bought the phone on Swappa from a seller that said it was bought from HTC directly.
Click to expand...
Click to collapse
The product ID m8_ul_ca can be AT&T or Developer's Edition.
The main version indicated with digits "1540" agrees with Developer's Edition. So it may be true it was purchased from HTC directly.
We have seen a lot of AT&t variants "converted" to be unbranded (Euro, Dev Ed, etc.). But since the ATT version has the ATT logo on the back of the phone, they would have to have replaced the back plate to remove all the branding. The model number on the back of the phone (fine print near the bottom) may also give a clue to its origins (although if it was replaced, it may not even agree with the product name in getvar - which is the most reliable info).
Herkatus said:
After I start having the issue, I rooted and installed a couple of different ROMs until I decided to go back to stock
Click to expand...
Click to collapse
How exactly did you return to stock? Your own nandroid, stock nandroid from XDA thread, or RUU? If not your own nandroid, what version number?
Although, the fact your data issues coincided with using a foreign SIM; I'm inclined to believe that was the cause, rather than anything to do with custom ROMs, restoring stock ROMs, or the fact its the Dev Edition.

redpoint73 said:
How exactly did you return to stock? Your own nandroid, stock nandroid from XDA thread, or RUU? If not your own nandroid, what version number?
Although, the fact your data issues coincided with using a foreign SIM; I'm inclined to believe that was the cause, rather than anything to do with custom ROMs, restoring stock ROMs, or the fact its the Dev Edition.
Click to expand...
Click to collapse
Sorry, I can't remember how... I followed a guide and I think I downloaded HTC official ROM.
As for the foreign SIM, how could that affect the phone? maybe it damaged the SIM tray? How can I solve it?

"New" M8 - Need help - No signal - questions on actual model supplied

Hi all
Just bought an M8 for the wife from ebay (I know) described as new, sold in the UK, I'm trying to get it set up with Cyanogenmod before letting her loose
I've rooted and put CM on our previous phones (HTC Desire, Galaxy S3, LG G3) without incident
I managed to get root, bootloader unlocked, TWRP and then CM12.1 snapshot installed - booted fine but wouldn't connect to any networks, no voice, no data at all - tried a known working SIM in this phone and it didn't work, tried the original SIM in another phone and it works fine so there's definitely an issue with this handset
I thought it could be the radio so I updated the firmware using the instructions in this thread. Now the phone boots fine but says "No SIM card"
Now I'm beginning to suspect the provenance of this phone, fastboot getvar all gives:
Code:
C:\Users\...\adb>fastboot getvar all
(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: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <deleted>
(bootloader) imei: <deleted>
(bootloader) imei2: Not Support
(bootloader) meid: <deleted>
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.171s
Now I'm getting suspicious, the model code on the back case of the phone is 0P6B100, yet the modelid reported in fastboot is 0P6B700, and fastboot also reports that the product as m8_whl which according to this website makes the phone a US Sprint model
Have I been sold a dog here? Or is there another explanation for this?

maybe you bricked the radio or it was already bricked and you confirmed it by flashing GSM firmware on CDMA device
M8_whl is sprint device which means it's CDMA device and flashing GSM firmware causing radio brick
BTW :- the thread you followed it's instruction to update the firmware is all about GSM devices and providing GSM firmwares only
Maybe you need to flash the stock sprint firmware and flash stock RUU then unlock the sim card to work on your carrier but i doubt it will work
anyone feel free to correct me if i'm wrong
Sorry for that
Sent from my HTC One M8 using XDA Labs

Thanks for that
I suspected as much, I just wanted to confirm before I messaged the seller
I should be able to get the phone returned for being "not as described"

[Q] Converting Canadian M8 to Anything Else - Avoid 7.0 boot loops

I decided to start using my M8 again after a couple of years and after flashing some new Nougat ROMs I have had the Canadian Carrier boot loop issue. In most cases I can go a day or two until I have to yank the sim and reboot to stop the loop. I had a thought though; could I convert my M8 into a US, GPE or international version so I can get around this problem? I know beanstalk works but I don't prefer it. My M8 is a Telus phone unlocked and currently on Bell network. It is rooted and the following are fastboot details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Also mid: 0P6B16000
If this will work what is the best way to it and maintain root? A lot of the guides are outdated so I'm not sure if this can even work.

your device is s-off you can convert it to any GSM variant but i don't know if it will work with your carrier
covert to WWE 6.12.401.4 and see how it goes
if it didn't work with your carrier revert the conversion by flashing the proper firmware ( telus firmware is 6.13.661.9 )

Bell uses the same bands as US AT&T, from what I can tell. Reason being, AT&T used to own portion of Canada Bell, and they still have a close working relationship. They seem to maintain their networks for the same or similar band support.
Flashing the Euro radio will result in you missing most of the LTE bands used by Bell, as well as one of the two used for 3G by Bell.
I would suggest flashing AT&T or US Developer's Edition firmware (or RUU) for proper bands support on Bell.
https://en.wikipedia.org/wiki/Bell_Mobility
http://www.gsmarena.com/htc_one_(m8)-6074.php

jets76 said:
I decided to start using my M8 again after a couple of years and after flashing some new Nougat ROMs I have had the Canadian Carrier boot loop issue. In most cases I can go a day or two until I have to yank the sim and reboot to stop the loop. I had a thought though; could I convert my M8 into a US, GPE or international version so I can get around this problem? I know beanstalk works but I don't prefer it. My M8 is a Telus phone unlocked and currently on Bell network. It is rooted and the following are fastboot details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Also mid: 0P6B16000
If this will work what is the best way to it and maintain root? A lot of the guides are outdated so I'm not sure if this can even work.
Click to expand...
Click to collapse
I'm also experiencing the same issue here with my phone. The difference is, i'm on telus and i'm pretty sure this phone was originally a t-mobile phone. Anyone have any idea why this actually happens in the first place? Maybe there's a way to make a flashable patch to use any nougat rom?

nate_benji said:
I'm also experiencing the same issue here with my phone. The difference is, i'm on telus and i'm pretty sure this phone was originally a t-mobile phone. Anyone have any idea why this actually happens in the first place? Maybe there's a way to make a flashable patch to use any nougat rom?
Click to expand...
Click to collapse
the thing is it's not the device firmware
It's on the carrier itself,there is some builds which have the gps disabled at all and it works for the Canadian carriers
Check the nougat discussion thread for that
Sent from my HTC M8 using XDA Labs

jets76 said:
I decided to start using my M8 again after a couple of years and after flashing some new Nougat ROMs I have had the Canadian Carrier boot loop issue. In most cases I can go a day or two until I have to yank the sim and reboot to stop the loop. I had a thought though; could I convert my M8 into a US, GPE or international version so I can get around this problem? I know beanstalk works but I don't prefer it. My M8 is a Telus phone unlocked and currently on Bell network. It is rooted
Click to expand...
Click to collapse
Hi Jets76,
I'm in the exact same situation you were in right now. I got my old M8 from Telus and am on bell right now. No nougat ROM (Lineage, RR, Cypher) seem to work. I haven't tried any android M roms. Before settling with M roms, I want to know if there is any work around to use android N roms.
Did you manage to make it work somehow?
I'm more curious on how to make it work than actually use one of the N roms.
Thanks,
Praveen Kumar