Develop Bugs

PRI Checksum 00000000

I went ##786# then PRI cheksum and i got 00000000 . I s any thing wrong with it?
I unroot to stock rom 132.651.1 then i did automatically download with 3G up to 147.651.1. My PRI still in 134.003 and doesnt change to 140.003
Anyway to fix that to get 140.003 and 00000 checksum is normal?

cocobongo77 said:
I went ##786# then PRI cheksum and i got 00000000 . I s any thing wrong with it?
I unroot to stock rom 132.651.1 then i did automatically download with 3G up to 147.651.1. My PRI still in 134.003 and doesnt change to 140.003
Anyway to fix that to get 140.003 and 00000 checksum is normal?
Click to expand...
Click to collapse
once you've rooted your phone, the PRI will be 134.xxx the stock one is 140.xxx

campchi said:
once you've rooted your phone, the PRI will be 134.xxx the stock one is 140.xxx
Click to expand...
Click to collapse
I unrooted my phone to factory stock 132.651.1 and automatically download by 3G up to 147.651.1 and still in 134.003 doesnt change to 1.40
If the phone do automatically download by 3g , obviously is unrooted.

cocobongo77 said:
I unrooted my phone to factory stock 132.651.1 and automatically download by 3G up to 147.651.1 and still in 134.003 doesnt change to 1.40
If the phone do automatically download by 3g , obviously is unrooted.
Click to expand...
Click to collapse
this has been covered numerous times. It appears that if you have rooted in the past, you can not ever get pri 1.40 even if you go back to unrooted shipped rom which you did. I would be curious to know if anyone has started with the first shipped rom (RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe), unrooting their device, then instead of accepting the ota, flashed the second shipped rom (RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed.exe) to see if anything would change, then flashed the 3rd and most up to date shipped (RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe). I bet its been done already but figured I would ask.

rileyd5 said:
this has been covered numerous times. It appears that if you have rooted in the past, you can not ever get pri 1.40 even if you go back to unrooted shipped rom which you did. I would be curious to know if anyone has started with the first shipped rom (RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe), unrooting their device, then instead of accepting the ota, flashed the second shipped rom (RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_rele ase_171253_signed.exe) to see if anything would change, then flashed the 3rd and most up to date shipped (RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_rele ase_CL195459.exe). I bet its been done already but figured I would ask.
Click to expand...
Click to collapse
I called Sprint and explain the situation, and they give me with them a hard full reset by AIR as new and reactivate the phone and nothing. They told me go tomorow to a store tecnician and they do by wires. I dont think will be a fix, wil be same issue
I gonna do is flash the seccond 132.651.6 manually then the third one if it fixe it as you said, Let you know

cocobongo77 said:
I called Sprint and explain the situation, and they give me with them a hard full reset by AIR as new and reactivate the phone and nothing. They told me go tomorow to a store tecnician and they do by wires. I dont think will be a fix, wil be same issue
I gonna do is flash the seccond 132.651.6 manually then the third one if it fixe it as you said, Let you know
Click to expand...
Click to collapse
thanks for doing this. I guess we will see if what happens.

rileyd5 said:
thanks for doing this. I guess we will see if what happens.
Click to expand...
Click to collapse
Dammm, still same 134.003

cocobongo77 said:
Dammm, still same 134.003
Click to expand...
Click to collapse
crap... how are you flashing the shipped roms if you dont mind me asking. just running the ruu.exe? or some other method. thanks for trying man!

rileyd5 said:
crap... how are you flashing the shipped roms if you dont mind me asking. just running the ruu.exe? or some other method. thanks for trying man!
Click to expand...
Click to collapse
First i went to the bootloader page then fastboot 2) connect the usb cable 3) press fastboot until show up fastboot usb and then run the RUU.exe
Other option is using ht sync until connect then run the RUU.exe

evo4
any fix for this i have same problem

badboy22 said:
any fix for this i have same problem
Click to expand...
Click to collapse
Why not just flash 1.77 zip? It is located on the development forums.

My EVO checksum is 00000000 and it's now updated to V1.90_03.
Is this okay?
Thanks!

[Q] converted vzw M8 to Tmo, but can't update firmware

Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant

Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.

xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?

Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.

xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?

Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.

xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help

Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.

xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up

Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?

possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery

Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.

where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do

xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.

nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.

Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.

xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?

SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.

Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:

Yeah and the guy from Germany doesn't have the time to look into this anyway...

[Q] Unlocked Sprint update

Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!

domt91 said:
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
Click to expand...
Click to collapse
You need a stock recovery to flash the OTA.

domt91 said:
Hello everyone!
I would greatly appreciate if someone could show the right way to get my phone fully functional;
SPRINT HTC ONE M8
GSM SIM UNLOCKED for use on GSM networks
S-OFF
Rooted
TWRP
HBOOT 3.18.0.0000
RADIO 1.08.20.0612_4
CID-11111111
software version: 2.16.654.4
android: 4.4.3.
Issue:
1. I can not install any OTA updates, and the notification keeps popping out.
2. Mobile data is just not working properly even though I did everything as said here;
http://forum.xda-developers.com/sprint-htc-one-m8/general/enabling-3g-umts-countries-t2847461
As I did my research, it was some kind of a major bug on this series of Sprint M8 phones with breakdowns in mobile data. However, since I can not get any updates, the problem perists.
I tried installing custom ROM's, but so far ARHD 22 didn't even boot and LiquidSmooth couldn't detect the SIM card at all.
I know there are quite a few tutorials and "how-to" threads explaining all you need to know about RUU, cusotm ROM's, etc. However if someone could tell me what exactly to do and in which order (return to stock, then update?) I would greatly appreciate it.
Many many thanks!
Click to expand...
Click to collapse
Easiest way to get it back to stock is just flash the Sprint H/K RUU. You can download it from HERE. Just run it and connect your phone when prompted and follow the instructions (I'd probably change your CID back to the Sprint one first to be on the safe side but as you're S-OFF it shouldn't be needed). You might also need HTC Sync Manager installed. If so, you can get it HERE
This process will wipe the phone completely so back up any data first but other than that you'll at least be back to stock and then troubleshoot any issues from there

Thanks
Many thanks to everyone.
Any chances of loosing the SIM UNLOCK when going back to stock completely?

Nope, that shouldn't be touched but as I've not had a SIM-locked device in years I can't say for certain

EddyOS said:
Nope, that shouldn't be touched but as I've not had a SIM-locked device in years I can't say for certain
Click to expand...
Click to collapse
OK, many thanks!

:good:

domt91 said:
:good:
Click to expand...
Click to collapse
Mine did the same this morning just flash twrp recovery and boot into it and you should be fine I don't know why it did this since I'm used to it popping up with a screen asking if I want to unlock boot loader but if it told you it was good then push twrp and you're good

tjeeeeee said:
Mine did the same this morning just flash twrp recovery and boot into it and you should be fine I don't know why it did this since I'm used to it popping up with a screen asking if I want to unlock boot loader but if it told you it was good then push twrp and you're good
Click to expand...
Click to collapse
Yeah, I just did that, no problems at all.
Tried to delete the previous post, but you got ahead of me
Let's see if I can get the mobile data to work without flaws.

domt91 said:
Yeah, I just did that, no problems at all.
Tried to delete the previous post, but you got ahead of me
Let's see if I can get the mobile data to work without flaws.
Click to expand...
Click to collapse
Are you trying to run any specific roms? I know with Sprint it's a bit limited

tjeeeeee said:
Are you trying to run any specific roms? I know with Sprint it's a bit limited
Click to expand...
Click to collapse
I want to try ARHD v22

domt91 said:
I want to try ARHD v22
Click to expand...
Click to collapse
Why not 34? Lol Sprint is up to date on its software you could just update to the lollipop firmware, and I could pull some of the files I've got to see if I can help you get it running, I'm on Leedroid right now so the process should be the same for ARHD.

tjeeeeee said:
Why not 34? Lol Sprint is up to date on its software you could just update to the lollipop firmware, and I could pull some of the files I've got to see if I can help you get it running, I'm on Leedroid right now so the process should be the same for ARHD.
Click to expand...
Click to collapse
Sorry if some of my questions are a bit dum, I just got from a long trip and have been out of this all rooting busines for a while...
Do i need to install a new stock firmware from Sprint with Lolipop to get the 34 runing?
I have been told v34 won't be working with this software I have right now on the phone.

domt91 said:
Sorry if some of my questions are a bit dum, I just got from a long trip and have been out of this all rooting busines for a while...
Do i need to install a new stock firmware from Sprint with Lolipop to get the 34 runing?
I have been told v34 won't be working with this software I have right now on the phone.
Click to expand...
Click to collapse
You can or you can go to the Sprint android development and flash the updated recovery since you are s-off and it'll permit you to flash lollipop roms without many issues but there is still the files that need to be modified for ARHD to work correctly like the boot.img and a few others.

tjeeeeee said:
You can or you can go to the Sprint android development and flash the updated recovery since you are s-off and it'll permit you to flash lollipop roms without many issues but there is still the files that need to be modified for ARHD to work correctly like the boot.img and a few others.
Click to expand...
Click to collapse
I just installed ARHD, everything went well and when it rebooted, the phone won't turn on... just black screen.
Any ideas??

domt91 said:
I just installed ARHD, everything went well and when it rebooted, the phone won't turn on... just black screen.
Any ideas??
Click to expand...
Click to collapse
Power+vol up for about 15 seconds then power+vol down to get into recovery. You cant flash it unless you swap out Sprint specific files otherwise you'll get what just happened or boot directly into boot loader.
Like I mentioned I can pull the files together and see if I can get it working for Sprint tonight when I get home but until then flash either fluent Rom or stock if you want lollipop or just flash bad boyz if you don't mind kitkat

tjeeeeee said:
Power+vol up for about 15 seconds then power+vol down to get into recovery. You cant flash it unless you swap out Sprint specific files otherwise you'll get what just happened or boot directly into boot loader.
Like I mentioned I can pull the files together and see if I can get it working for Sprint tonight when I get home but until then flash either fluent Rom or stock if you want lollipop or just flash bad boyz if you don't mind kitkat
Click to expand...
Click to collapse
I will go with installation of
Sprint_HTC_One_M8_non-HK_4.20.651.2_RUU
Sounds good?

domt91 said:
I will go with installation of
Sprint_HTC_One_M8_non-HK_4.20.651.2_RUU
Sounds good?
Click to expand...
Click to collapse
Yes and ill put the Sprint ARHD together tonight and test

tjeeeeee said:
Yes and ill put the Sprint ARHD together tonight and test
Click to expand...
Click to collapse
Many thanks!
For me, the biggest issue is the mobile data breakdowns... I know I read somewhere a while ago it was an issue with some Sprint M8 models. I would like to get everything working w/o problems since it is GSM unlocked, and via QPST I unlocked all the bands.

domt91 said:
Many thanks!
For me, the biggest issue is the mobile data breakdowns... I know I read somewhere a while ago it was an issue with some Sprint M8 models. I would like to get everything working w/o problems since it is GSM unlocked, and via QPST I unlocked all the bands.
Click to expand...
Click to collapse
Also, I just found some official EU RUU's with different radio's as far as I can tell from the filename.
Maybe that could be the final solution to all the problems?

T-Mobile LTE is virtually nonexistent/very weak and slow

When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Update:
Here are some videos I made showing the issue:
Part 1
Part 2
I will add another one using the stock ROM to further prove the issue exists on both the unlocked firmware, and T-Mobile one.

You root your phone, mess it up and then send it back? Kinda messed up.

Did you try flashing the latest modem?
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.

iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
No, I stated the issue was there before then. I only unlocked it and flashed updated firmware in an attempt to fix the issue which it didn't. Clearly we all need to read thoroughly before responding to an OP so we don't look arrogant in the end.
Now, on another note I mentioned this issue was already present from the moment I started using the phone 100% stock. It will sometimes still get LTE, but it only sticks for 10-30 seconds then drops to H/H+ immediately. My S7 Edge and Nexus 6P do not have this issue whatsoever therefore I'm certain something with the firmware is not right.

geoff5093 said:
Did you try flashing the latest modem?
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
Click to expand...
Click to collapse
Thank you, for reading the OP , and no I don't have just the modem files, although I do have the RUU so I know it's in there

Pilz said:
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Click to expand...
Click to collapse
Did you try 1.53 us unlocked ruu that's worth a try

bbell101584 said:
Did you try 1.53 us unlocked ruu that's worth a try
Click to expand...
Click to collapse
No, I can't get it to flash, but I'm going to try another method for updating it to that version

Mine has been extremely inconsistent in sticking to LTE. Sometimes I have to force it to LTE only and then when I switch back to GSM/WCDMA/LTE auto, it ****s the bed for a few minutes before correcting itself.

Pilz said:
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Click to expand...
Click to collapse
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out

I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.

bbell101584 said:
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
Click to expand...
Click to collapse
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
frankcck said:
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
Click to expand...
Click to collapse
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.

Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Boot into download mode and run RUU again.

frankcck said:
Boot into download mode and run RUU again.
Click to expand...
Click to collapse
That's exactly what I did, and I just confirmed the error code was "155 unknown error"

Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
Redownload the ruu or just try from a whole different computer if you have access to one

bbell101584 said:
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
Click to expand...
Click to collapse
Yep, following the instructions to the t (so to speak), it ran fine, booted into whatever that weird screen is with the % on it then after about 15 seconds gave me the error

I just gave the extSD method again, now it is saying
Code:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 22 RU_HEADER_ERROR

Pilz said:
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Click to expand...
Click to collapse
I did not boot into download mode. Left it on the home screen, Just made sure USB debugging was on. The RUU handled everything after that.

Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?

Pilz said:
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Click to expand...
Click to collapse
Have them re register the device on the network? The US unlocked base should work fine on TMOUS, I know as I have used it and both LTE, VoLTE, and WiFi calling fully work.

Mikee4fun said:
Looks like a sim issue. Try re seating the sim and if that does not work have TMO give you another sim from the store.
Click to expand...
Click to collapse
I have another sim, and I've reinserted it s few times now without success. I might call them and activate the other sim. It's just odd how it works flawlessly with LTE on every phone but this one.

Can't connect to my home network carrier

OK, I install the RR Nougat 7.1.1 android version on my htc one m8. I have been using it for a while now without issues,
but just yesterday, my phone had low battery and it turn off.
After restarting the phone, could not connect it to my home country network.
I can't access the carrier settings menu as the 'com.android.phone has stopped' pops up.
I have most tuts on the forum but not much help. Even factory reset does not work.
After factory reset, Sprint apns settings are on the apn setup menu but after i delete them, still can't connect to my home country network carrier.
Please some help here guys.

iyassa said:
OK, I install the RR Nougat 7.1.1 android version on my htc one m8. I have been using it for a while now without issues,
Click to expand...
Click to collapse
Try flashing the ROM again, to try to get the "process has stopped" error to keep coming up.
iyassa said:
After factory reset, Sprint apns settings are on the apn setup menu but after i delete them, still can't connect to my home country network carrier.
Click to expand...
Click to collapse
Does this mean you have your local network's APN info entered, or no?
Do you have voice service at least?

redpoint73 said:
Try flashing the ROM again, to try to get the "process has stopped" error to keep coming up.
Well tried that several times but to no avail
Does this mean you have your local network's APN info entered, or no?
Yeah, I deleted the sprint APNS and registered that of my local network carrier but still no avail
Do you have voice service at least?
Click to expand...
Click to collapse
No voice

iyassa said:
No voice
Click to expand...
Click to collapse
Then this has nothing to do with APN, since voice service does not rely on APN (APN only applies to data cell service).
A few folks have had this issue of "no SIM" and no service after letting the battery die on the Sprint version M8. But I'm not sure what the solutions is. You may search around, as I know the issue has been posted a couple times recently. I suggested the Sprint RUU for one user. But it inexplicably caused the device to brick.

iyassa said:
No voice
Click to expand...
Click to collapse
redpoint73 said:
Then this has nothing to do with APN, since voice service does not rely on APN (APN only applies to data cell service).
A few folks have had this issue of "no SIM" and no service after letting the battery die on the Sprint version M8. But I'm not sure what the solutions is. You may search around, as I know the issue has been posted a couple times recently. I suggested the Sprint RUU for one user. But it inexplicably caused the device to brick.
Click to expand...
Click to collapse
ok thanks will keep on looking around

Hello there,
I was wondering, is this problem already fixed? I'm having the exact same problem...
Thanks in advance for your reply!
Rob

robjuh007 said:
Hello there,
I was wondering, is this problem already fixed? I'm having the exact same problem...
Thanks in advance for your reply!
Rob
Click to expand...
Click to collapse
NOPE

iyassa said:
NOPE
Click to expand...
Click to collapse
You might try Sprint RUU.

redpoint73 said:
You might try Sprint RUU.
Click to expand...
Click to collapse
Tried that already but didn't work either

iyassa said:
Tried that already but didn't work either
Click to expand...
Click to collapse
If s-off, try a lower level (such as kitkat 4.4.2 or 4.4.3) Sprint RUU and see if that helps.
You can only try this with s-off. If s-on, you can't "downgrade" (run older RUU then version presently on the phone) by RUU as it will fail the version check.
Also, don't flash any other carrier version RUU (only Sprint) as doing so with s-off may lead to permanent damage on a Sprint device due to incompatibility (even on a properly working Sprint M8).

redpoint73 said:
If s-off, try a lower level (such as kitkat 4.4.2 or 4.4.3) Sprint RUU and see if that helps.
You can only try this with s-off. If s-on, you can't "downgrade" (run older RUU then version presently on the phone) by RUU as it will fail the version check.
Also, don't flash any other carrier version RUU (only Sprint) as doing so with s-off may lead to permanent damage on a Sprint device due to incompatibility (even on a properly working Sprint M8).
Click to expand...
Click to collapse
I downgraded right down to version 4.2.2 with s-off and still could not solve it. Guess will just have to get a new smartphone and strike off htc products on my wish list

iyassa said:
I downgraded right down to version 4.2.2 with s-off and still could not solve it. Guess will just have to get a new smartphone and strike off htc products on my wish list
Click to expand...
Click to collapse
The main issue, is that you bought the wrong version for your location. It's my strong opinion, that the Sprint version should never be bought by anyone except those using the US Sprint network. It's intended primarily for the Sprint CDMA network.

redpoint73 said:
The main issue, is that you bought the wrong version for your location. It's my strong opinion, that the Sprint version should never be bought by anyone except those using the US Sprint network. It's intended primarily for the Sprint CDMA network.
Click to expand...
Click to collapse
Yeah, your probably right, but I learnt that by flashing a new radio (radio frequency in HTC phones directly installs the network carrrier base band) can solve it but can't get the right radio image. Though am not a 100% sure but have tried some radio images but still no result.

iyassa said:
Yeah, your probably right, but I learnt that by flashing a new radio (radio frequency in HTC phones directly installs the network carrrier base band) can solve it but can't get the right radio image. Though am not a 100% sure but have tried some radio images but still no result.
Click to expand...
Click to collapse
If you are talking about radio images from other (non-Sprint) versions of the M8; radio from any other version is not compatible, meaning it won't work with the Sprint version, and can possibly lead to a permanent radio brick. This is for the same reason as I previously cautioned you not to run RUUs for another version M8.
If you are talking about flashing different radios specifically intended for the Sprint M8, that isn't any different from trying the various Sprint M8 RUUs (which install different radio image along with every other partition).