Verizon to US Unlocked Questions - HTC 10 Questions & Answers

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.

Related

[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.

Problems installing Sense based roms

For some reason, every time I try to install a sense based rom, it never boots.
I'm fairly new to flashing, and have flashed 4 or 5 aosp roms. Every time I install one of those, it always works correctly, no issues.
I have tried to flash several Sense based roms, such as ARHD 20.1, Insert Coin, and nv, and each time, it never works. I always do a factory wipe beforehand as well as a wipe in the aroma installer. It will go thru the process and install, and then prompt me to reboot, which it does. Once the screen comes back onm however, it just hangs on the white htc screen with the red development text. When i get back to the hboot, itll show nothing for os.
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom. Also, I just tried the NV rom which is based off my firmware, and it still gives me the same trouble. Does anyone know what I'm doing wrong?
I'm running an ATT Htc One m8, rooted, unlocked, s-off with sunshine, twrp recovery
mattprice86 said:
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom.
Click to expand...
Click to collapse
Give the ROMs about 10 minutes, and I bet they will boot. The extremely long boot time, and lack of boot animation (another symptom of this issue) makes a lot of folks believe the phone is stuck/frozen, when in fact its just taking a reeeeeally long time to boot.
If its true that the ROMs in fact never boot, it might just be an issue with your recovery. fastboot erase cache and either re-install recovery, update to the latest version, or try another recovery (Philz).
Even if the Sense ROMs boot, you might find some serious things are broken with your outdated firmware, such a broken WiFi. So I suggest either update your firmware or stick or ROMs based on your present firmware.
Ok thanks, i will try again. Ive read a bunch of threads about updating my firmware but couldnt find an answer to a question I have about it.
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
mattprice86 said:
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
Click to expand...
Click to collapse
Firmware includes the radio baseband, so it may cause issues with reception on AT&T. It seems at least a couple folks have been flashing the 3.28 firmware, but I haven't seen enough reports to give me a warm and cozy feeling. With S-off (which is required to flash the firmware, anyway) you can always revert. But still, basic reception is more important to me than a couple updated features. Personally, I'll probably wait until the 3.x firmware specific to AT&T starts rolling out.
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Leads me to believe that the radio does not matter like the N5 where the 820 and 821 radios were interchangeable.
HTC One M8
Thanks redpoint, you were right, I gave it some time and it did come on. You always seem to be the one answering my questions, I appreciate it.
As for the new fw, I was thinking that would happen too from what I've read, I just needed someone more experienced to confirm that. I think I'll wait as well.
Thanks again
Elisha said:
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Click to expand...
Click to collapse
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
mattprice86 said:
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
No probs.
redpoint73 said:
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
Click to expand...
Click to collapse
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former. For the record, my M8 is a "whelp", and I had to pay for Sunshine.
OMGMatrix said:
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former.
Click to expand...
Click to collapse
My guess would be the former as well. Keep mind that AT&T uses five different bands for LTE depending on your market region. Also keep in mind that travelling to another location may result in losing LTE reception (when you otherwise would have LTE on a AT&T specific radio).
Although none of this explains why I've seen some folks get NO SIGNAL whatsoever on AT&T's network after flashing the international firmware (2.x version, haven't seen any complaint yet on 3.28). Even if no LTE, those folks still should have been able to get HSPA and/or GSM since those AT&T bands appear to be supported by EMEA specs. So it leads me to believe there is something else going on aside from just band compatibility. Such as the network not falling back properly to HSPA/GSM.
I certainly don't have an issue if folks want to experiment with the 3.28 firmware on the AT&T network (as long as you know what you are doing, and are aware of the possible issues). Its certainly tempting with the 3.x based custom ROMs coming out. I might even experiment myself if I free up some time. But that spare time is a bit of a premium for me right now; and I also can't really afford ATM to have the possibility of reception issues or no service.
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
mattprice86 said:
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
Click to expand...
Click to collapse
You could always restore the backup you should be making before you do any mods on your phone. That would be the safest way.
So if I upgrade my fw then restore a backup, I will lose my fw changes?
I make nandroid backups before I do any, so I have approximately 60gb of backups on an external HD, and I always keep 1 or 2 on my internal and external storage

[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

Why can't you update PRL and profile in Lineage and other customs - and can we fix it

So as I've looked into it, it appears that nothing has changed here in the 2-3 years since I last explored this issue. I'm talking about the fact that you can't successfully update PRL and profile on CDMA carriers in LOS and AOSP ROMS. The usual behavior if you even have the option in the UX is that you get a force close. I'd love to understand why this hasn't been addressed.. It's a huge reason someone would stay on stock over AOSP/LOS. I saw someone suggesting a Nexus 5 dev had some success using a couple of APKs including OmaDmclient.apk, and a few threads here and on Reddit talking about how it must've been broken by an AOSP contributor, but in any event it still doesn't work. Isn't this something that the LOS team could fix if they wanted to?
The issue with CDMA is that most of the stuff isn't open source. This is why the aosp source code is targeted to GSM. So I sought this will get fixed any time soon.
Same problem... I think
My neighborhood has excellent Sprint 4G LTE coverage and it's much faster than T-Mobile. I happen to use Ting (which allows you to choose between T-Mobile GSM and Sprint CDMA, although to switch from one to the other costs $20). GSM isn't really an option for me.
Anyway, I used to have this problem with my LG Volt LS740. I could work around it by forcing a PRL and profile update on stock and then flashing to Cyanogenmod.
That phone finally bit the dust. I have now inherited my wife's Moto G 2015 (osprey) XT1548. Really nice phone.... but the issue is, the latest stock I can find is Android 6.0. I can activate the phone and get great 4G LTE on stock, but to flash to Lineage OS 14.1 (or AOSP) I have to wipe the device. I simply can't get it to pick up the 4G LTE service on the custom ROM's (tried both). This is a real problem.
As I understand it (admittedly from reading Wikipedia), the PRL contains an "acquisition table" that prescribes the frequencies/modes that the device will communicate on... so I think that's probably my issue. After doing the prescribed wipes in the ROM installation documentation, flashing the ROM, and booting the device, I think I've lost the PRL somewhere in that process.
Is there some way to retrieve the PRL while the device is on stock and put it back when flashing custom? If the PRL is indeed stored on the R-UIM, should I just remove the R-UIM during the first boot? Maybe I'm wrong and the problem isn't really the PRL.
Any thoughts? Please don't tell me to switch to GSM. The GSM coverage here is just plain bad from both carriers who offer it in my neck of the woods.
I have this same exact question. Ting, N910P note 4 that was originally Sprint, and days-old Lineage 16 / Andorid 9.0 . The latest stock rom is 6.0.1, and works fine. Lineage 16 works 99% fine and I'd really rather use that. But LTE doesn't work. If I force it to use 3G only, it actually all works. data, voice, text, bluetooth, gps… and being Lineage, I don't have to try to surgically remove all the spyware and other crapware without breaking it. It's just not in there in the first place. I'd really rather use that.
I would be fine having to extract things from the stock rom and edit files or whatever if it were at least just known what needed to be done. I'm fine with the fact that Lineage nor anyone else can actually include and redistribute any carrier proprietary stuff.
it should be possible
Has anyone figured this out?
I too have devices on ting, fantastically built devices that run amazingly thanks to a solid construction, the support of many many developers who are craft some of the best ROMs for any device I've ever seen, considering the limited specs of the XT1031s. Fortunately/adequately enough though, they only run on 3G Sprint, Boost originally, moved to Ting for their great rates for FreedomPop customers when they bought them out.
Anyway, currently to get a device on ting, I have to flash the latest 5.1 official stock Boost Mobile Rom with the latest radio baseband and firmware and such. A process thats pretty involved. I'm hoping that I can backup the stock image using TWRP, as when I went through the process of reloading the official image through the individual files via mfastboot, I skipped the logo and recovery files, and since I was able to retain my custom logos for boot and bootloaderunlocked screens, and the recovery, I'm hoping to be able to make an image of the stock ROM, which if at all possible, I'm going to do my best to make as bare bones as possible. May start with flashing the bloatware removed version of stock thats available, then going through and removing basically every app on the phone with the exception of settings and anything to do with phone, phone/carrier services, sim toolkit, etc, so I can have the smallest image possible that could maybe be restored everytime/anytime that I want to update the PRL or Profile. Which it looks like theres a new version of each released at a minimum every 3 months, as I just activated another device this way and there was only an incremental update of the last digit. If this works, great. If it doesn't then I hope that theres an answer to the question in the initial post of this thread;
Is there a way to update the CDMA PRL and Profile on a device that is running a custom ROM? If so, is it something the ROM needs to specifically support or is it something that is possible to do with a bundle of apks? Like sim toolkit and the like?
If its ROM related, are there, or would it be possible to take the necessary components from the stock files and install them in Xposed or Magisk? Or perhaps the buttons in the settings panel of the stock rom simply executes a series of commands that can be executed within a terminal CLI on the custom ROM? I assume that since the custom ROM clearly has access to the 3G radio since I can make and recieve calls, I have data, and text messaging (haven't tried MMS, but I assume it works) so why couldn't it do one more thing and initiate the PRL update?
I assume that even the stock rom doesn't ever touch the PRL or Profile, seeing as they remain even after a user data wipe, and are available for the radio to continue to use with custom roms, which means that the radio chip has to be the one storing the PRL Profile, so I bet that the radio also directly downloads those files from the carrier when asked to do so, and the stock rom must only come into play for the base logicstics of it all such as radio-"is this prl/profile a newer version than the one that i have now?" and phone-"yes, download new, purge old, flash new, tell me when done and leave me alone" Since the radio doesn't have its own processor for those sorts of things perhaps? If thats the case, then that should imply that theres nothing particularly proprietary or licensed, etc, that a rom would explicitly need to have in order to initiate these updates since it would never directly need to touch/see the files, just know that they were updated and what version number they are. What also lends me to believe this is the case is the fact that you can't select to downgrade the prl/profile, rollback, or load one manually, at least not that I can see.
So basically I'm saying that I hope it should be something simple to do. And if it is simple to do, you would think that custom roms would be able to read the carrier correctly too? Right now my new device reads "Boost" still. My previous one when I got it on ting I wanna say actually read ting afterwards. But when I loaded ressurrection remix, I had no cell/data/voice nothing, It just kept asking me for a sim card, which this phone doesnt have at all. When I loaded Lineage, everything cell related work. But can't update prl/profile, and carrier reads as "3G Roming Indicator Off" Which idk why thats the case.
Perhaps I'm missing something
Perhaps custom roms are missing a few somethings.
The only sure thing is that carriers need to just not be so greedy/dumb/uselessly difficult, and make giving them money for service easier, preferably without questions. Or at the very least actually provide some security so all this nonsense is at least worth something in the end to the end user, instead of being done so that they can try to spy on your unencrytped texts and calls to sell to advertisers, and selling access to the higest bidders such as the government and bounty hunters, whilst preventing you from restricting that information.

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.

Categories

Resources