Develop Bugs

[Q] Phone has no signal

This is my first smart phone, I had a Asus TF700 tablet that i unlocked and did a lot of custom ROM work on. Well I am military moving back to the US soon and i was visiting to take my wife back. I bought a Verizon M8 that of course was unlocked but i was going to use t-mobile. While in the states i had the issues that is common with this setup and was losing 4g, couldnt text while on 4g, etc. At this point i flew back over to europe and thought i could use t-mobile's deal of unlimited text and data in other countries. But i dont receive a signal at all. Started looking into how to unlock and custom ROM to fix the issues. I watched all the videos and read the how-tos that i could find and did the firewater to S-off and unlock. I installed TWRP 2.7.1.0 since it was the latest on the TWRP website. I changed over to superCID. I have installed viperONE M8 ROM. I tried flashing the ATT radios that i could find in tread on the regular M8 boards but after i flashed it, it would boot up all the way, i still didnt get any bars for signal but after about 5 minutes it would just reboot. i reflashed my originial radio and it worked fine again. Well i just tried to flash the WWE radio and same thing happened. Is there something i am missing to flash radios and not have it bootloop? Also, anyone have any ideas on what i can do to get signal on my phone? I have data roaming enabled and anything else i can find about roaming enabled. Thanks for any help.

In a nutshell you purchased the wrong unit.
The Verizon unit is a CDMA based version of the HTC One M8. So the Sprint and verizon share similar radios.
Your trying to use that on a GSM network. Not compatible.
You would need an AT&T / T-Mobile or Google Play Edition version for what your trying to do.
Some people have bricked their phones flashing CDMA to GSM and visa verse so be careful. Theres a lot more detail there but that pretty much covers it.

[Australia] HTC 10 Australian

Hi guys,
I got my HTC 10 last week - phone is a big improvement from the m8.
I am running Telstra's latest firmware - Have s-off already...
Telstra's latest firmware is 1.53.841.6 with Leedroid ROM - have been trying to get VOLTE.
I never got VOLTE with stock because I rooted so fast and S-OFF and installed custom ROMs.
So I had to install stock system image 1.53.841.6, reinstall stock recovery and factory reset and VOLTE icon shows up instantly. Install TWRP and VOLTE remains. But if you install a custom rom and do a full wipe seem to lose VOLTE. Also have to have the telstra firmware to VOLTE to work, I tried with WWE and no go. Also had to ring up telstra as it wasn't activated. So if you are having trouble getting it - might be best to double check. Even though my provisioned flag was on. *#*#4636#*#* to check - tap phone info.
@xlrate reported not wiping data and installing VIPER was able to keep VOLTE. (Updated the customize folder in the rom with my Telstra back up, also the build prop to do this) Also TELST001 cid has to be on.
Has anyone got VOLTE working on a custom ROM on WWE Firmware?
So Aussies... Who's got their new HTC 10?
Update - 15/10/16
Thanks to @brantp for providing TWRP backups & OTAs
https://drive.google.com/drive/folders/0B6MWrHVBWC-xZlBQN1BqYUNPRW8
TWRP Backup (untouched System Image + Boot)
- 1.21.841.8 (+ Recovery)
- 1.53.841.6
- 1.80.841.1
- 1.95.841.3
Stock Recovery
- 1.53.841.6
- 1.80.841.1
- 1.95.841.3
OTA
1.21.841.8 --> 1.53.841.6
1.53.841.6 --> 1.80.841.1
1.80.841.1 --> 1.95.841.3
Firmwares- Refer to http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520 for more info
https://docs.google.com/spreadsheets/d/1EdAHLDDxqf9jH65me_8bY9oXdaYusI0eedpwO6yUY2s/pubhtml
Thanks to @Sneakyghost
Roms- Leedroid, ICE and Viper now support Telstra with carrier support.
If anyone has any of the other australian carriers firmware please post and I will add them to OP.
15/08/16
https://www.androidfilehost.com/?w=files&flid=60869
Telstra RUU provided by @Sneakyghost - Will restore OTA's if anyone has broken them
12/03/18
Telstra OREO update
http://fotadl-az.htc.com/secure/OTA....48.841.31_release_519847tp9bagwfkglchg5u.zip
@Sneakyghost isn't doing the firmware updates anymore.
If you need to use the firmware.zip out of the OREO zip and need to a custom recovery either replace the recovery.img with twrp.img (rename it of course) in the firmware.zip - or flash one after installation.

I got mine about a month ago.. All I've done so far is root it.. (even after all these years, it still sounds wrong)
I normally run ARHD, but, Mike hasn't mentioned developing for the 10, so, I'm stuck atm, not really interested in running a massively modded ROM. But, last night the OTA notification popped up for 1.53.841.6.. So, I'm going to have to do something - the notification is annoying me. So, I guess I have to work out how to update it.
I hadn't even considered the VoLTE requirements.. I just assumed it would all work, even on a custom ROM. 4G did, I didn't think this would be any different.
Is VoLTE worth hanging on to? I don't really get it.. Is it like VOIP for mobiles?

Vampyric said:
I got mine about a month ago.. All I've done so far is root it.. (even after all these years, it still sounds wrong)
I normally run ARHD, but, Mike hasn't mentioned developing for the 10, so, I'm stuck atm, not really interested in running a massively modded ROM. But, last night the OTA notification popped up for 1.53.841.6.. So, I'm going to have to do something - the notification is annoying me. So, I guess I have to work out how to update it.
I hadn't even considered the VoLTE requirements.. I just assumed it would all work, even on a custom ROM. 4G did, I didn't think this would be any different.
Is VoLTE worth hanging on to? I don't really get it.. Is it like VOIP for mobiles?
Click to expand...
Click to collapse
I have had VoLTE working with Leedroid after I used the telstra 1.53 system/customize & parts of the build.prop on the 1.30 base... Haven't been able to get it working on 1.80 base.
Have had to use the telstra firmware for it work, doesn't work on WWE. So it is kinda a pain to get working.
VoLTE is better call quality and if you are on a call you can use LTE/4g to use the internet... Without VoLTE when on calls your phone 3g
EDIT - don't think OTA will work since you are rooted unless you went systemless root

I guess I don't 'appreciate' VoLTE as much as I should, because I rarely make phone calls..
Sadly, not Systemless root. So, I think I need to go back to stock, update and re-root. It's not something I've had to worry about before. So, it's kinda frustrating, and a little too complicated for me to totally understand.
I was going to de-brand it, and just run the WWE RUU.. But, maybe I'll wait for the 1.80 Telstra update and worry about it then.
I got rid of the notification
**Sent from a uranium powered typewriter**

Anyone experiencing an issue with NFC? While on stock 1.21.841.8 (and locked), worked without issue. Since updating to 1.53.841.6 (and unlocked), can't read my Opal card now ie no vibration, no sound, no anything. Haven't tested my tap & pay banking app yet (which did work without issue prior to updating).

Yes I also had and issue with NFC. Would not read opal card and was an absolute pain to try and read my Amex and Visa card.
Ended up getting another issue with it and returned the phone under warranty for NFC and the other issue.
Still waiting to get a phone back ?
Sent from my HTC One_M8 using Tapatalk

Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......

pablo11 said:
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
Click to expand...
Click to collapse
Thats if we get 1.8
I have a feeling we will miss that and get the one after that.

xlrate said:
Thats if we get 1.8
I have a feeling we will miss that and get the one after that.
Click to expand...
Click to collapse
Aparently they have stoped rolling the 1.80 update. Im on vodafone and there website has no update for the htc 10 so i agree that we wont get it

yldlj said:
Aparently they have stoped rolling the 1.80 update. Im on vodafone and there website has no update for the htc 10 so i agree that we wont get it
Click to expand...
Click to collapse
Tried reflashing the 1.53 firmware again (twice) to see if it fixes it, but it's still not working ie Can switch it on and off, but it does not respond to my opal card.
It's only taken Telstra until this month to push out 1.53, so who knows when (or if) 1.80 will happen. Now I'm trying to decide whether it's worth sending back for another handset or waiting to see if the next OTA will fix it. My biggest concern is that the replacement could be on 1.21 and I could possibly end up with the same issue all over again!

pablo11 said:
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
Click to expand...
Click to collapse
I just tried to NFC on 1.53 and it isn't working very well, hardly at all. I got it to work 3 times in about 15 mins...
Previously I think when I was on 1.30 firmware it was working well before but just had to hold it near the head phone jack.
Any Telstra users want to test out the Telstra firmwares
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Make sure you back-up the rom & back up internal storage refer to later posts in that thread.

https://crowdsupport.telstra.com.au/t5/Device-Updates/Software-Updates-01-07-2016/td-p/585953 Telstra 1.80.841.8 firmware is coming 25-Jul
Leedroid is the best rom for Telstra users. Running it myself and working perfectly, now supports Telstra with carrier support & VoLTE working - thanks @LeeDroid
*Only works on Telstra firmware.

Install Ice yesterday (only got my phone Friday ), really like it over the stock rom.
Some people complained about the LED but I like it. My only complaint about my M8 was how bright the LED was specially in the dark when you're trying to get to sleep.
Another problem I'm having is file transfers freeze when using a USB 2 port on Windows 10.
I like my new M10 but not sure if I like it over the M8 as of yet. I preferred the speaker arrangement on the M8 and having the home, back buttons etc on the screen rather then down the bottom.
I have to admit I'm not a fan of the "Samsung" look at all which is why I bought HTC in the past to begin with. I didn't want to be a part of the flock.

Hey guys,
I'm looking to get the 10 but imported, could someone (especially looking for someone with Optus) check their box to see what specific model it is (e.g. 10h or 10u)?
Thanks guys

The Telstra model is a HTC 10h

ICE (InsertCoin) v2.0.6 supports Telstra also now too. Thanks @baadnewz

morgy59 said:
The Telstra model is a HTC 10h
Click to expand...
Click to collapse
Awesome, thanks morgy59

Found out that Telstra's policy for DOA/ELF replacements are within 30 days of purchase. Since a return will result in a repair, I'll wait to see if the OTA will fix the NFC issue first before sending back.
Has anyone experienced an NFC issue on Telstra stock, only to have it disappear after switching to a cusom ROM?

brantp said:
Found out that Telstra's policy for DOA/ELF replacements are within 30 days of purchase. Since a return will result in a repair, I'll wait to see if the OTA will fix the NFC issue first before sending back.
Has anyone experienced an NFC issue on Telstra stock, only to have it disappear after switching to a cusom ROM?
Click to expand...
Click to collapse
I found it worked perfectly fine on wwe 1.30 firmware using Leedroid. Now I'm on 1.53, hardly works at all
Sent from my SM-P605 using Tapatalk

It's doesn't read card on 1.53 on Optus build 710

Verizon to US Unlocked Questions

I've been reading around and mostly want to know everything for this for that time when CM becomes stable.
Anyways:
Do you lose Verizon network functionality? By this I really mean, calls, SMS, SMS, voice mail, and 4G LTE.
When converted...just act like it's the US unlocked model when flashing ROMs? Do I need to flash the Verizon radio?
I'm confused...and the final question..
To convert it requires a SuperCID and then RUU flash, right? I've seen Sprint owners do it and one Verizon owner, but the instructions were all very unclear to me.
Thanks!
Answers are on post #4, tested it out after being sure of how to do this. If you're lazy, click here...

I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.

I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.

Tested it out...
Tarima said:
I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.
Click to expand...
Click to collapse
afuller42 said:
I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.
Click to expand...
Click to collapse
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.

Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
I was the guinea pig for this in regards to Sprint, but you've seem to partially answer a question I had.
I know that the Verizon and US Unlocked use the same model ID, but the Sprint and internal do not. Leaves me wondering if I could just run the RUU for my Sprint phone.

Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
Does your volte work ? Something you can try is flash Viper10 and select as a verizon model instead of the unlocked version, this will add get you on global mode and I think will fix your signal issues. You list your on Viper10 just dirty flash it again selecting verizon version and give it a try. If it does not help you can always just dirty flash again and go back selecting the unlocked version. Just do a back up before doing this and you will covered if you just want to restore the back up. From my experience this might help just do not try running a custom kernel for the verizon version if you converted to the unlocked as your camera may not work and keep forcing close but you can run a custom kernel for the unlocked if you converted to unlocked. My recommendation would be to run the Elite kernel as I have had really good luck with the Elite kernel on the Htc 10 and I think theirs is what I run well on my Motorola nexus 6 also.

Ariac, regarding OTA software updates on the phone, I think you get that "corrupt" message because you flashed a different radio and twrp. Might be worth flashing the original Unlocked radio/recovery back and see if it at least detects the latest update. If it does, you'll also need to remove superCID to be able to take the update.
I reflashed the RUU yesterday, removed superCID and I was able to take the OTA.

Anyone with Unlocked HTC 10 and TMO as carrier who have upgraded to N?

HTC MM Firmware for some reason didn't use the TMO frequencies/bands effectively. This caused caused a weaker or an erratic signal compared to TMO stock firmware (radio, etc).
I was wondering if anyone who is aware of this issue has had better luck with the HTC Unlocked N software that was released recently. Since TMO has not released N yet, I was considering just running the HTC RUU or take the OTA, but if the signal is still a problem, I will wait for the TMO RUU to extract parts of its firmware before upgrading.

I never had a problem with US unlocked HTC 10 and TMO. Radio connection was fine with all bands. There was an issue with WiFi calling not working properly but they fixed that a while ago in MM. N runs great on TMO with VoLTE and WiFi calling as well. Maybe it was the WWE HTC 10 with the band issues on MM?
Sent from my iPhone using Tapatalk

effortless said:
I never had a problem with US unlocked HTC 10 and TMO. Radio connection was fine with all bands. There was an issue with WiFi calling not working properly but they fixed that a while ago in MM. N runs great on TMO with VoLTE and WiFi calling as well. Maybe it was the WWE HTC 10 with the band issues on MM?
Click to expand...
Click to collapse
I had discussed this with 1 or 2 others earlier (maybe 2 months ago) and they confirmed this issue and instructed me to change CID and flash TMO firmware (basically the radio). However, I never did get around to finishing extracting a "nowipe" TMO firmware. So I'm not going to worry about it. Incidentally, my Wi-Fi calling has not worked in a long time. I'm currently on 1.96.617.2.
And since N has been released now by HTC, I'm thinking of just upgrading.
Incidentally, how did you upgrade? Did you just RUU and then re-root (assuming you are S-off)? Was thinking of doing that (although it's a hassle) or... just upgrading firmware and flashing a custom N Rom but it's unlikely that they have Wi-Fi calling. So let me know what you did. I stopped getting OTA awhile ago and would have to flash a pristine system stock anyway if I wanted to upgrade by OTA...I figure either way will be kind of a chore.
Sent from my HTC 10 using XDA Labs

syntropic said:
I had discussed this with 1 or 2 others earlier (maybe 2 months ago) and they confirmed this issue and instructed me to change CID and flash TMO firmware (basically the radio). However, I never did get around to finishing extracting a "nowipe" TMO firmware. So I'm not going to worry about it. Incidentally, my Wi-Fi calling has not worked in a long time. I'm currently on 1.96.617.2.
And since N has been released now by HTC, I'm thinking of just upgrading.
Incidentally, how did you upgrade? Did you just RUU and then re-root (assuming you are S-off)? Was thinking of doing that (although it's a hassle) or... just upgrading firmware and flashing a custom N Rom but it's unlikely that they have Wi-Fi calling. So let me know what you did. I stopped getting OTA awhile ago and would have to flash a pristine system stock anyway if I wanted to upgrade by OTA...I figure either way will be kind of a chore.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Changed the CID and used the RUU. Everything is working so far with Elemental/Magisk Pixel Dialer. Having the same quality of Service while I was using Stock MM T-Mobile.

Tachi91 said:
Changed the CID and used the RUU. Everything is working so far with Elemental/Magisk Pixel Dialer. Having the same quality of Service while I was using Stock MM T-Mobile.
Click to expand...
Click to collapse
Why did you change the CID? Had you changed it once already from the CID it came with (unlocked version)? It wouldn't need to be changed.
So you ran the RUU to upgrade to N (plus using the EX kernel and the pixel dialer?)
Sent from my HTC 10 using XDA Labs

syntropic said:
Why did you change the CID? Had you changed it once already from the CID it came with (unlocked version)? It wouldn't need to be changed.
So you ran the RUU to upgrade to N (plus using the EX kernel and the pixel dialer?)
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Had it as SuperCID and for some reason the RUU didn't like it so changed to the Dev CID. EX kernel runs on N now and Pixel Dialer since for some dialers cause issues or don't support VoLTE or Wifi Calling. So far so good

syntropic said:
HTC MM Firmware for some reason didn't use the TMO frequencies/bands effectively. This caused caused a weaker or an erratic signal compared to TMO stock firmware (radio, etc).
I was wondering if anyone who is aware of this issue has had better luck with the HTC Unlocked N software that was released recently. Since TMO has not released N yet, I was considering just running the HTC RUU or take the OTA, but if the signal is still a problem, I will wait for the TMO RUU to extract parts of its firmware before upgrading.
Click to expand...
Click to collapse
I had both, the T-Mobile branded HTC 10 with Android 6 and an unlocked HTC 10 with Android 7. The signal itself, could be -1 or 2 dBm less than other phones that I had, but and both of the phones didn't have issues with erratic signal.
I had couple of other issues with Bluetooth and WiFi connection.

Tachi91 said:
Had it as SuperCID and for some reason the RUU didn't like it so changed to the Dev CID. EX kernel runs on N now and Pixel Dialer since for some dialers cause issues or don't support VoLTE or Wifi Calling. So far so good
Click to expand...
Click to collapse
Really? Dialers cause problems with Wi-Fi calling?? I would think HTC would have worked that out for those TMO customers ergo bought their unlocked phone.
So I'm going to run the RUU I guess to upgrade to N. After, do I just push the latest TWRP from the thread in the development forum? [The working TWRP with a GUI was called "test3" a few days ago.]
Lastly, what is the status on SuperSu? I originally downloaded Chainfire's interim Supersu for N, but that may be obsolete now.
I hate asking, but the questions I have involve threads like the TWRP one which is 1200+ pages long. I'm leaving to go on a brief vacation, and would love to upgrade, but I have this nightmare that something gets screwed up and I have to leave before I have time to sort it all out....And end up going on vacation with a non-working phone...
Thanks for the info!
Paul
Sent from my HTC 10 using XDA Labs

Charkatak said:
I had both, the T-Mobile branded HTC 10 with Android 6 and an unlocked HTC 10 with Android 7. The signal itself, could be -1 or 2 dBm less than other phones that I had, but and both of the phones didn't have issues with erratic signal.
I had couple of other issues with Bluetooth and WiFi connection.
Click to expand...
Click to collapse
So you still have the unlocked version? How did you upgrade it to N? And what TWRP/SuperSu did you use to root it?
I will rip apart a TMO N RUU as soon as it appears and create a NoWipe zip to upgrade/modify the firmware on the unlocked version (I.e., change the radio and other components, while still keeping it unlocked). If that happens to improve my signal, I'll be happy to upload it for any of us on the unlocked HTC 10 with TMO as carrier...
Thanks!
Syntropic
Sent from my HTC 10 using XDA Labs

effortless said:
I never had a problem with US unlocked HTC 10 and TMO. Radio connection was fine with all bands. There was an issue with WiFi calling not working properly but they fixed that a while ago in MM. N runs great on TMO with VoLTE and WiFi calling as well. Maybe it was the WWE HTC 10 with the band issues on MM?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Please tell me what N Rom you are using on T-mobile with VOLTE AND Wifi-Calling working, because every rom i've seen and used so far these do not work.

I'm using the stock US Unlocked HTC 10 Firmware/ROM. I have the US Unlocked HTC 10.

syntropic said:
Really? Dialers cause problems with Wi-Fi calling?? I would think HTC would have worked that out for those TMO customers ergo bought their unlocked phone.
So I'm going to run the RUU I guess to upgrade to N. After, do I just push the latest TWRP from the thread in the development forum? [The working TWRP with a GUI was called "test3" a few days ago.]
Lastly, what is the status on SuperSu? I originally downloaded Chainfire's interim Supersu for N, but that may be obsolete now.
I hate asking, but the questions I have involve threads like the TWRP one which is 1200+ pages long. I'm leaving to go on a brief vacation, and would love to upgrade, but I have this nightmare that something gets screwed up and I have to leave before I have time to sort it all out....And end up going on vacation with a non-working phone...
Thanks for the info!
Paul
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Earlier when GPE was going around xda it would randomly not support wifi calls back in Android 6. So far Pixel and the HTC stock dialer are pretty consistent.
The new RUU 2.38.617 is out (updates thread where I got it). Has some bug fixes etc. I flashed the 3.0.3 TWRP that's in the Downloads tab of the HTC 10 TWRP thread. And flashed SuperSu 2.79. So far so good

Whether stock TMO or US Unlocked MM or N, the radios are fricken horrible. I have to have mine converted to International version just to have a properly working radio here in the U.S.
I have a thread on all of this if you search.
Sent from my HTC 10 using Tapatalk

What are my options on a 2PS6400 with Android versions Rooting and S-OFF

I bought this new off eBay for development only. I have no plans to Activate it.
I would love to just run RUU for Android 6, 7, or 8 as needed.
Which RUU's do I need for a 2PS6400
I'm confuse what this phone is. It was advertised as "Sprint Unlocked". It was brand new sealed.
I put an old Sprint SIM in it, just to get rid of some warnings and wasn't sure if it would help GPS quality by pinging towers. GPS is running pretty poorly. Runs fine on Deactivated M9.
It doesn't have any Sprint Crap on it, which is really nice.
I would like to avoid S-OFF and rooting if possible. But I don't mind using the ZIP RUU on the SD Card to switch.
I just noticed this thread of someone switching from Nougat to Marshmallow but he was S_OFF, Rooted, TWRP etc.
But based on the Video he posted to finally make it work, if he put the ZIP on the SD Card my recollection is S-OFF wouldn't matter.
Anything other than RUU makes me nervous trying to go backwards manually flashing old firmware with S-OFF (with partition changes etc.).
I've also lost S-OFF that I paid for in the M9. I don't mind at all in paying once, but I'm not paying multiple times.
Also it shows 2.42.651.66 Are their Android 7 updates I can apply?
If I check for software updates, it might kick off the Android 8 update and I may not be able to stop it. What are my options there?

boot into download mode. If it was a true brand new sprint phone that was unlocked it would still have sprint apps. People on ebay are either buying new phones and flashing new roms themselves or buying new phones thatve been flashed by some other company.
Hold vol down and power button until the htc logo lights up and it should boot into download mode. Take note of the red colored data up top and write down the radio and os. Also do a imei and serial number check. If its anything other than an htc 10 send it back

mswlogo said:
I bought this new off eBay for development only. I have no plans to Activate it.
I would love to just run RUU for Android 6, 7, or 8 as needed.
Which RUU's do I need for a 2PS6400
I'm confuse what this phone is. It was advertised as "Sprint Unlocked". It was brand new sealed.
I put an old Sprint SIM in it, just to get rid of some warnings and wasn't sure if it would help GPS quality by pinging towers. GPS is running pretty poorly. Runs fine on Deactivated M9.
It doesn't have any Sprint Crap on it, which is really nice.
I would like to avoid S-OFF and rooting if possible. But I don't mind using the ZIP RUU on the SD Card to switch.
I just noticed this thread of someone switching from Nougat to Marshmallow but he was S_OFF, Rooted, TWRP etc.
But based on the Video he posted to finally make it work, if he put the ZIP on the SD Card my recollection is S-OFF wouldn't matter.
Anything other than RUU makes me nervous trying to go backwards manually flashing old firmware with S-OFF (with partition changes etc.).
I've also lost S-OFF that I paid for in the M9. I don't mind at all in paying once, but I'm not paying multiple times.
Also it shows 2.42.651.66 Are their Android 7 updates I can apply?
If I check for software updates, it might kick off the Android 8 update and I may not be able to stop it. What are my options there?
Click to expand...
Click to collapse
The last update for the Sprint HTC 10 was for 2.51.651.31
You can download the RUU.exe directly from HTC for it, or you could check for updates in settings > about for the OTA
Here's a link for the RUU.exe Scroll down to the "Manual System Update Instructions" and read them. The download is at the end of the instructions.
If you would prefer to flash the RUU via your SD card, or you don't have a Windows computer (you need one for the .exe), let me know and I'll extract the ROM.zip (RUU.zip) for you so you can flash it that way. You could also probably just find the .zip with a Google search.
EDIT: Apparently Sprint has released Oreo via OTA, but there isn't an RUU for it yet

Cool it's already S-Off, Unlocked. I think it's an "HTC 10 Unlocked/Developer" but it's hard to confirm a matching RUU with the 2PS6400 model number.
It was factory sealed. But I still don't know what RUU's are safe to use with it.
https://c1.staticflickr.com/1/795/39021848390_abec02a7e9_c_d.jpg

mswlogo said:
Cool it's already S-Off, Unlocked. I think it's an "HTC 10 Unlocked/Developer" but it's hard to confirm a matching RUU with the 2PS6400 model number.
It was factory sealed. But I still don't know what RUU's are safe to use with it.
https://c1.staticflickr.com/1/795/39021848390_abec02a7e9_c_d.jpg
Click to expand...
Click to collapse
Hmmm, well 2PS640000 is Sprint's MID so you should be careful with that. In general flashing, GSM firmware to a CDMA phone can be dangerous and lead to a brick. There is a way to convert the HTC 10, but I'm not up to speed on it. Since your phone is S-Off I have a feeling someone might have done that. You could try to do an ESN check with the IMEI and see what that brings up as far as what is was originally.
US Unlocked's MID is 2PS650000, and with your current MID you wouldn't be able to flash a US Unlocked RUU

xunholyx said:
Hmmm, well 2PS640000 is Sprint's MID so you should be careful with that. In general flashing, GSM firmware to a CDMA phone can be dangerous and lead to a brick. There is a way to convert the HTC 10, but I'm not up to speed on it. Since your phone is S-Off I have a feeling someone might have done that. You could try to do an ESN check with the IMEI and see what that brings up as far as what is was originally.
US Unlocked's MID is 2PS650000, and with your current MID you wouldn't be able to flash a US Unlocked RUU
Click to expand...
Click to collapse
Nobody did anything to it. He sold 60 of them and it was clearly factory sealed. I see it mentioned a lot when googling around with other people just as puzzled exactly what it is. It's some sort of developer phone.
Someone had a 2PS500 as well that sounded identical. It had S-Off and same bare bones Sprint firmware version.
Ting says it will activate. But it says no on other carriers. I don't care though, but if I ever sold it, it looks like Ting (at least) would work.
It would not let the Unlocked ( *.617.*) RUU Run firmware flash.
The current firmware it had is 2.42.651.66 which is a Sprint Variant.
The CID is set to 1111111
So I tried the Sprint 2.51.651.31 RUU update and it flashed fine. And now has all the Sprint Garbage on it. I don't care. I now know what I can flash to it or not.
It still shows S-Off and Unlocked and Official after Sprint RUU.
It would be nice to know if I could safely flash the Oreo Sprint RUU (which I highly suspect will also flash fine once released) and then go BACK to the Nougat Sprint one as needed back and forth.
Since it's S-Off etc. It would be handy to be to test Android 7 and 8 with one phone.
If I bricked it, I can return for 30 days. So I rather brick it now than later

I took a shot at updating to Android 8 OTA and it worked fine. Will test if I can flash back to Android 7 with the same RUU I used above.
I can't get a very good GPS lock on this thing. Every other deactivated phone I have can get a good lock.

sounds a bit like mine... a 2PS6500, came pre-Soff with SuperCID 111111 and MID converted to 2PS6200... had Nougat WWE.401 installed & GPS was great.
once i took the OTA to Oreo, i now have issues with GPS, as I can see all the satellites, but can't get any GPS-lock at all anymore

I can still get a gps lock just not a great one and sluggish to get a lock.

Tried flashing back to Android 7 with the RUU (I used earlier), no go. Once Android 8 is on their seems no easy way of going back and I'm not gonna try manually doing it as I'll brick it for sure.
Gonna probably send it back. I was willing to live with marginal GPS (which I need for my app debug) but was going to keep it if I could easily switch between Android 7 and 8 (and back).
But it doesn't look that way.
Charger just died too.

kimba99 said:
sounds a bit like mine... a 2PS6500, came pre-Soff with SuperCID 111111 and MID converted to 2PS6200... had Nougat WWE.401 installed & GPS was great.
once i took the OTA to Oreo, i now have issues with GPS, as I can see all the satellites, but can't get any GPS-lock at all anymore
Click to expand...
Click to collapse
Did you find a solution?
I think I have the same phone from ebay - pre-Soff Sprint that was converted.
And no GPS lock. (running Oreo US Unlocked.)

JohnSoong said:
Did you find a solution?
I think I have the same phone from ebay - pre-Soff Sprint that was converted.
And no GPS lock. (running Oreo US Unlocked.)
Click to expand...
Click to collapse
unfortunately no... still trying to hunt for a solution. so yours was a 2PS6400 before... sprint? mine was a 2PS6500 though, as written on its backside (XC edition with 64GB internal btw)

mswlogo said:
Tried flashing back to Android 7 with the RUU (I used earlier), no go. Once Android 8 is on their seems no easy way of going back and I'm not gonna try manually doing it as I'll brick it for sure.
Gonna probably send it back. I was willing to live with marginal GPS (which I need for my app debug) but was going to keep it if I could easily switch between Android 7 and 8 (and back).
But it doesn't look that way.
Charger just died too.
Click to expand...
Click to collapse
Just a follow up. I sent mine back. Got a new real Verizon one for $200.00 on eBay (had no box but it looks new with fairly recent build date too). Works perfect, including GPS without being activated.
I had to manually flash it to the last Android 7 update via adb/fastboot couldn't do it OTA (WIFI) which I thought was a little odd.