Develop Bugs

Has anyone rooted a Bell Canada HTC 10?

Hi everyone,
I've been researching for a couple days and I'm pretty much ready to root my phone. I have the Bell Canada version. All I want to do is unlock the bootloader, root it, and install Xposed. From what I can tell, I shouldn't have any problems. But I've been seeing a lot about the radio not working, and I'm concerned I might be screwing myself since there is no RUU for the international version of the HTC 10. Which means, as far as I can tell, that if I screw up my phone there's no going back. I haven't seen many threads addressing specifically the Bell/international version, so I want to be clear before I try anything. I have much experience rooting phones, but I'm new to HTC and it seems much more complicated and risky.
So I have a few questions:
- Has anyone successfully rooted the Bell/international variant of the HTC 10 without issues or radio loss?
- Further, has anyone gotten Xposed framework working?
- Is there a way to revert the phone back to stock/fully functioning in the case that the radio stops working or some other problems arise?
Thanks in advance.

I plan on getting one soon and root it. Would be fun to know if someone did it already.
Sent from my Nexus 5 using XDA-Developers mobile app

Found some information on reddit
https://www.reddit.com/r/htc/comments/4tap0f/bell_stock_rom_htc10/d5lszn8

Were you guys able to root and/or flash a ROM on the Bell model?

I am running Leeroid ROM on my Bell HTC 10. Very easy. Unlock bootloader, install twrp with fastboot and you're gold
Xposed works great too. Never had an issue with radio since rooting. I do have a minor problem which only started happening since i removed the rom encryption and my lte wont work until i go into mobile networks and reset apn to default. Once i do that my lte works like normal until i reboot and have to repeat the 10 second process.
And you can always save a twrp backup of your stock ROM if you want to go back.

sweet, thanks for confirming! Did you manage to get a Sharp display by chance? I have a feeling that literally all of the Bell ones are of Tianma.

Bell user here. I'm on stock rom with latest update with some mods. Phone runs pretty good now,
1.90.666.4 OS
Sunshine > $25 dollar paypal (S-OFF)
TWRP for recovery
AcoustiX_Audio_ZeroInfinity_v30 (make speaker louder)
ElementalX-HTC10-0.25-Sense (Plus $3.00 EX Kernal Manager Paypal)
Tweaked_pnp_thermal_ivicask_v19

I've rooted my HTC 10 using sunshine. I'm currently on Leedroid's ROM.
As anyone successfully restored to stock? I need to do so to unlock. I want to use a different SIM.

There was a bell ruu somewhere around. Just run that and you'll be back to full stock.

Do you have a link?

No but @xunholyx might be able to help

I have the 2.41.666.3 RUU. You can download it here.

Thanks a lot. I also need a stock recovery. Is it included?

Yes. RUUs always contain the stock recovery. They restore everything to stock. Also, it will wipe your phone, so backup anything you don't want to lose.

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

Having so many issues since trying to Flash LeeDroid ROM

Hi all,
I have the EE UK HTC 10.
Managed to get TWRP and SuperSU flashed fine and rebooted into system with no problems.
Copied over the LeeDroid Latest ROM, I forgot to address the firmware issue, so the one I'm running is older than the ROM's one. Causing my fingerprint sensor/home button to stop working...
I've been looking around thee internet for hours now and cannot find the RUU for my UK EE HTC 10 to be able to update the Firmware, and in general cannot find any way to update Firmware now.
Can someone please help? I'm not a complete noob to this, just haven't messed with Root and so on in a few years. (Not had the time, lol.)

corydor13 said:
Hi all,
I have the EE UK HTC 10.
Managed to get TWRP and SuperSU flashed fine and rebooted into system with no problems.
Copied over the LeeDroid Latest ROM, I forgot to address the firmware issue, so the one I'm running is older than the ROM's one. Causing my fingerprint sensor/home button to stop working...
I've been looking around thee internet for hours now and cannot find the RUU for my UK EE HTC 10 to be able to update the Firmware, and in general cannot find any way to update Firmware now.
Can someone please help? I'm not a complete noob to this, just haven't messed with Root and so on in a few years. (Not had the time, lol.)
Click to expand...
Click to collapse
Do you have a backup of your stock rom? If so flash that and see if you can upgrade using the official OTA.
Else, check out this thread for firmwares, on the last couple pages there are a bunch of versions posted.
https://forum.xda-developers.com/ht...-collection-recovery-ruu-ota-t3359297/page183
Also, from a couple threads below yours:
https://forum.xda-developers.com/htc-10/help/home-button-fingerprint-doesnt-nougat-t3558961

corydor13 said:
Hi all,
I have the EE UK HTC 10.
Managed to get TWRP and SuperSU flashed fine and rebooted into system with no problems.
Copied over the LeeDroid Latest ROM, I forgot to address the firmware issue, so the one I'm running is older than the ROM's one. Causing my fingerprint sensor/home button to stop working...
I've been looking around thee internet for hours now and cannot find the RUU for my UK EE HTC 10 to be able to update the Firmware, and in general cannot find any way to update Firmware now.
Can someone please help? I'm not a complete noob to this, just haven't messed with Root and so on in a few years. (Not had the time, lol.)
Click to expand...
Click to collapse
Read the aroma installer. Install the rom again and when you get the question on what firmware you are, select marshmallow firmware. The fingerprint and home button will work again.

Mr Hofs said:
Read the aroma installer. Install the rom again and when you get the question on what firmware you are, select marshmallow firmware. The fingerprint and home button will work again.
Click to expand...
Click to collapse
Yeah, sorry mate. I thought it was asking which version of the OS I want to install. LOL.
Thanks for that though! :good:

UK Three stock ROM

Does anyone know where to get hold of the UK stock ROM.
P2a42_S056_161130_uk
Made the rookie mistake of not backing up before change to the stock Row rom.

Could do with this too, the Row rom is proving to be really buggy and unstable despite factory reset. I've read it's difficult to downgrade though?

4GB Super Voice
I would also like a copy of this, I think the stock firmware contained settings for 4G Super Voice which made 4G reception better. - three.co.uk/Discover/network/4G-Supervoice
I am finding myself on HSDPA allot more since going to the ROW ROM.

On the stock Three firmware there were no settings for VOLTE/4G super voice.
I flashed the ROW firmware and it been running really well. No crashes, no bugs and the 4G reception is very good.
There are also now settings inside the network settings for "Enhanced 4G voice" or something along those lines which is VOLTE/Super voice.
However it doesn't appear to work and it still switches to 3G to make calls.

Because the UK is better than the ROW rom? They are the same with the only difference than the stock Three UK rom has a preinstalled bloatware!

My only reason is that my LG urbane on aw 2.0 connected fine with that ROM, But does not seem to the ROW Rom.
If i could get a resolution for that i would be happy, but can't seem to get any other advised than reset both and try again, which has been done a few times.

911-Future_Maker said:
Because the UK is better than the ROW rom? They are the same with the only difference than the stock Three UK rom has a preinstalled bloatware!
Click to expand...
Click to collapse
Which bloatware?

All I found were the 3x Three apps. My Three, Three in Touch and another one which I can't remember (Three suggestions or something).
They can just be uninstalled if you don't want them.

I need this too as my device has to go in for service. Anyone have access to the stock Three UK firmware?

The nougat update.zip file in developer section is an official firmware i was using it for about 2 months untill i rooted. Now i am using the Nougat deodexed version which is also the same rom but with a few tweaks here and their and all bloat removed and i seem to get volte in even more locations now.

sam00561 said:
The nougat update.zip file in developer section is an official firmware i was using it for about 2 months untill i rooted. Now i am using the Nougat deodexed version which is also the same rom but with a few tweaks here and their and all bloat removed and i seem to get volte in even more locations now.
Click to expand...
Click to collapse
Thanks, but the Three UK FW is customised. need this version installed before I send for service.

oh sorry i didnt realise it was for sending in for service what happened?

Actually, I have resolved the issue now but I still would like the FW for the future if anyone has access to it. As for the problem had: I foolishly set the band to USA in the service menu. This made it impossible to make calls or connect to a 2G/3G network. I tried resetting the handset, rolling back to MM, upgrading back to N but nothing resolved the issue until I came across a post earlier today on an old Moto thread. A simple modem erase using ADB resolved the issue. All back to normal now. Phew!

Anybody got a link to this firmware ?