Develop Bugs

Can a t-mobile tp2 flashed with a cdma rom be brought back to a gsm radio rom?

Hi. Can a T-mobile HTC TOUCH PRO2 (US version) which was stupidly flashed with a SPRINT CDMA ROM be brought back to GSM by reflashing it with a GSM flash ROM file using a PC running Windows? If so, where can I obtain the flash ROM file from, as well as the utility to flashing it back with.
PS: HTC Techs wouldn't help me except telling me to send it in so they can charge me more than I already paid for this phone already. Thanks in advance for helping or trying to help.

Did you brick you device?

Kevinik said:
Did you brick you device?
Click to expand...
Click to collapse
Well, my "know-it-all" buddy who's had great success with tinkering & flashing my other phones, B-R-I-C-K-E-D this one. Now he and I have been through the gamut on trying to reset this TP2 with the problems listed in another thread here using forum members' suggestions as well as the resetting tips for this model found on HTC.com with no success. So I had a thought in my sleep. Maybe, just maybe, I can reflash it?
Symptoms: There is no screen on this phone now. My PC tries to recognize it for about 1 minute or two, after it displays it's hardware signature in Device Manager 2-3 minutes showing up as "Qualcomm CDMA Technologies MSM" with an exclamation point under "Other Devices", then, the phone's hardware signature disappears from my hardware list in Windows 7's Device Manager listing. It didn't do that before.
"My Other thread" referring to all I did in trying to revive this phone with the help of other members here.

suzukii said:
Hi. Can a T-mobile HTC TOUCH PRO2 (US version) which was stupidly flashed with a SPRINT CDMA ROM be brought back to GSM by reflashing it with a GSM flash ROM file using a PC running Windows? If so, where can I obtain the flash ROM file from, as well as the utility to flashing it back with.
PS: HTC Techs wouldn't help me except telling me to send it in so they can charge me more than I already paid for this phone already. Thanks in advance for helping or trying to help.
Click to expand...
Click to collapse
You should be able to connect the USB, go into bootloader mode, and then run update the ROM. You should probably run task29 first to clear the memory. If you can't get the USB to work, you can flash from your SD card. Check the first several posts of the ROM forum, rather than this GENERAL forum.

find an official T-mobile HTC TOUCH PRO2 rom and flash it.
and if your device has hard-spl then you can flash any full gsm rom.
some roms here

faria said:
find an official T-mobile HTC TOUCH PRO2 rom and flash it.
and if your device has hard-spl then you can flash any full gsm rom.
some roms here
Click to expand...
Click to collapse
Yep it all started with the Hard-SPL from the Rhodium.htc-unlocks.com guys.
PS: your link above doesn't seem to work.

suzukii said:
Yep it all started with the Hard-SPL from the Rhodium.htc-unlocks.com guys.
PS: your link above doesn't seem to work.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=544538
and here you shoul find a t-mobile rom
http://www.xda-roms.com/

faria said:
http://forum.xda-developers.com/showthread.php?t=544538
and here you shoul find a t-mobile rom
http://www.xda-roms.com/
Click to expand...
Click to collapse
Will do. Thanks.

faria said:
http://forum.xda-developers.com/showthread.php?t=544538
and here you shoul find a t-mobile rom
http://www.xda-roms.com/
Click to expand...
Click to collapse
Nope no good. These tips all expect some sort of interactivity between the use & the phone present like being able to go into bootloader mode or expecting something visual on the screen. My TP2 doesn't do anything after flashing it with the CDMA process (provided by the Rhodium.htc-unlocks.com website), except turn on the little orange LED ever couple of minutes until the battery just dies out.

You now have a nice paper weight or brick. Flashing a cdma radio and/or bootloader/unlocker is NOT reversible. If you had only flashed a cdma rom then that could have been reversed.

suzukii said:
Nope no good. These tips all expect some sort of interactivity between the use & the phone present like being able to go into bootloader mode or expecting something visual on the screen. My TP2 doesn't do anything after flashing it with the CDMA process (provided by the Rhodium.htc-unlocks.com website), except turn on the little orange LED ever couple of minutes until the battery just dies out.
Click to expand...
Click to collapse
If you cant get into bootloader I'm almost certain that means the phone's bricked. I realize that's likely not the information you want to here but you need at least a FEW things working on the thing to be able to flash it to a different rom. Bootloader being one of them.

If you cant get into bootloader mode,then i dont currently know any other way of reviving the device at home.sorry.
edit
to the poster above....
it seems we posted at the same time

drewcam888 said:
You now have a nice paper weight or brick. Flashing a cdma radio and/or bootloader/unlocker is NOT reversible. If you had only flashed a cdma rom then that could have been reversed.
Click to expand...
Click to collapse
YEP. Thanks. I just got a RMA from HTC to send it in for repairs. They'll probably rape my credit card. Oh well.

suzukii said:
YEP. Thanks. I just got a RMA from HTC to send it in for repairs. They'll probably rape my credit card. Oh well.
Click to expand...
Click to collapse
you rigth there!problably cheaper to buy a new one

Aaron McCarthy said:
If you cant get into bootloader I'm almost certain that means the phone's bricked. I realize that's likely not the information you want to here but you need at least a FEW things working on the thing to be able to flash it to a different rom. Bootloader being one of them.
Click to expand...
Click to collapse
I'll keep that in mind next time. For now the phone is on it's way back to Oz. What sux about this is that I could've had the pleasure of bricking my own phone, instead my pal got to enjoy this phones' trial & tribulations. thanks anyhow guys.
Now lets see what happens with my T-mobile HD2-Leo, eh,eh

suzukii said:
YEP. Thanks. I just got a RMA from HTC to send it in for repairs. They'll probably rape my credit card. Oh well.
Click to expand...
Click to collapse
RMA usually it's totally free you only have to pay to send in the phone. I know cause I did the same thing kind of... I flashed a GSM rom on a CDMA phone and totally bricked it. My phone connection led didn't light up when connected. Then I call HTC, they sent me to call another company that handles US Cellular and got it RMA paid only shipping.
If your led connection lights up there might be a possibility you can flash your stock rom with a clean Micro SD Card. Just search for this method on the forums, it has been a working life saver to many.

suzukii said:
Nope no good. These tips all expect some sort of interactivity between the use & the phone present like being able to go into bootloader mode or expecting something visual on the screen. My TP2 doesn't do anything after flashing it with the CDMA process (provided by the Rhodium.htc-unlocks.com website), except turn on the little orange LED ever couple of minutes until the battery just dies out.
Click to expand...
Click to collapse
The only thing that might work is to go back over the the CDMA forum and find out how the CDMA version invokes the bootloader. Maybe it is different than the GSM version? If you can't get to bootloader you are in trouble.

Kevinik said:
RMA usually it's totally free you only have to pay to send in the phone. I know cause I did the same thing kind of... I flashed a GSM rom on a CDMA phone and totally bricked it. My phone connection led didn't light up when connected. Then I call HTC, they sent me to call another company that handles US Cellular and got it RMA paid only shipping.
Click to expand...
Click to collapse
Bear in mind that (I believe) the OP said he Hard-SPL'd the device. I've seen numerous tales on here, of HTC declining to repair under warranty in those cases, citing 'Illegal software'. They usually then quote a couple of hundred dollars to change the motherboard, or a fee to return the phone unrepaired (the fee is their charge for the diagnostics).

I have the same error. Any new guess? In my country there aren't HTC repair stores

hi all:
anyone here know how to reboot the tmobile tp2 after I think I brick it? probably flash with wrong rom. now the phone will not turn off. stuck at "stick together".
Thanks
De

Data stuck at 2G on T-Mobile

I just bought a factory unlocked htc one m9 and plugged the sim card in.
After cache partition wipes, two hour-long customer support calls, a factory reset, and a bottle of Tylenol, nothing happened.
(Okay, I'm joking about the Tylenol.)
The big issues are that the only mobile network operator detected in settings is AT&T, and that I can not change any APN settings (though they are T-mobile anyway, so that shouldn't matter.)
The T-mobile rep and I both checked, and the phone IS compatible with the t-mobile data bands in my area, so there is no physical reason that it shouldn't work.
Any help with this would be massively appreciated!

iateapietod said:
I just bought a factory unlocked htc one m9 and plugged the sim card in.
After cache partition wipes, two hour-long customer support calls, a factory reset, and a bottle of Tylenol, nothing happened.
(Okay, I'm joking about the Tylenol.)
The big issues are that the only mobile network operator detected in settings is AT&T, and that I can not change any APN settings (though they are T-mobile anyway, so that shouldn't matter.)
The T-mobile rep and I both checked, and the phone IS compatible with the t-mobile data bands in my area, so there is no physical reason that it shouldn't work.
Any help with this would be massively appreciated!
Click to expand...
Click to collapse
I had a similar problem with my phone (developer edition) when I first put in the sim card. A phone restart with the sim in it solved it right off.

computerslayer said:
I had a similar problem with my phone (developer edition) when I first put in the sim card. A phone restart with the sim in it solved it right off.
Click to expand...
Click to collapse
Okay, I just tried that and it didn't help.

iateapietod said:
Okay, I just tried that and it didn't help.
Click to expand...
Click to collapse
Now that you've restarted, try going into the network settings and manually choosing T-Mobile.
(Settings, Mobile Data, Network operators, search for networks)

It doesn't find anything other than AT&T.

I'm guessing that choosing the automatic option dues any good.
My next move would be to redo the setup process.... probably by resetting the phone. I'm off to Google the issue and see if anything comes up.
[EDIT] Before you do that, double check that your network mode is set to GSM/WCDMA/LTE auto. Anything else will (artificially) limit you to 2G or 3G [/EDIT]
[EDIT #2] T-Mobile has the APN information for manual input. It may be worth trying to create a new APN profile to see if that makes a difference [/EDIT]

I tried both of those. Now I'm having issues even just connecting it to my computer over USB. (HTC site says there's a software update that I think might help, but the phone isnt detecting it)

iateapietod said:
I tried both of those. Now I'm having issues even just connecting it to my computer over USB. (HTC site says there's a software update that I think might help, but the phone isnt detecting it)
Click to expand...
Click to collapse
Ah. Probably worth applying the latest RUU. The executable is here - best to install it with your phone connected to your computer in download mode. Alternatively, you can use the SD card method, though you'll have to search around for the Android 7 Rui zip file.

computerslayer said:
Ah. Probably worth applying the latest RUU. The executable is here - best to install it with your phone connected to your computer in download mode. Alternatively, you can use the SD card method, though you'll have to search around for the Android 7 Rui zip file.
Click to expand...
Click to collapse
I think I'm going to have to use the SD card method - the m9 keeps disconnecting randomly over usb and if that happens during the install.... I'd really like to not brick the phone.
I've been looking around all over google and can't seem to find a .zip for the update, I found one in a thread on here (still can't link things yet, under ten posts) but the download site said file not found.
In addition, do I need to use S-Off before trying the update? In some of the forums that was mentioned but I think it was for a different version of the phone. HTC has the update files and doesn't say anything about it, but it also doesn't say anything about updating over SD card.

iateapietod said:
I think I'm going to have to use the SD card method - the m9 keeps disconnecting randomly over usb and if that happens during the install.... I'd really like to not brick the phone.
I've been looking around all over google and can't seem to find a .zip for the update, I found one in a thread on here (still can't link things yet, under ten posts) but the download site said file not found.
In addition, do I need to use S-Off before trying the update? In some of the forums that was mentioned but I think it was for a different version of the phone. HTC has the update files and doesn't say anything about it, but it also doesn't say anything about updating over SD card.
Click to expand...
Click to collapse
Head on over to the General forum and check out the thread by Flippy498 about stock ROMs. It should be a few posts in, but the zip file is linked!

For anyone else having this type of issue - even though they're all unlocked, some versions of the htc one m9 (potentially other phones by HTC as well) are produced in different regions. The Taiwanese version does not have band 12, and others potentially lack other bands.

iateapietod said:
For anyone else having this type of issue - even though they're all unlocked, some versions of the htc one m9 (potentially other phones by HTC as well) are produced in different regions. The Taiwanese version does not have band 12, and others potentially lack other bands.
Click to expand...
Click to collapse
Oh dear. I assumed that you were referring to the unlocked version sold directly from HTC, as opposed to a branded M9 (produced for a specific carrier & region) that had subsequently sim-unlocked.

computerslayer said:
Oh dear. I assumed that you were referring to the unlocked version sold directly from HTC, as opposed to a branded M9 (produced for a specific carrier & region) that had subsequently sim-unlocked.
Click to expand...
Click to collapse
That's fine, I assumed I was too. Thank you again for all of the help computerslayer!

iateapietod said:
That's fine, I assumed I was too. Thank you again for all of the help computerslayer!
Click to expand...
Click to collapse
My pleasure. Did you end up successfully getting the phone on T-Mobile?

computerslayer said:
My pleasure. Did you end up successfully getting the phone on T-Mobile?
Click to expand...
Click to collapse
Nope! I'm trying to unlock the lte bands before using S-off (just because it doesn't seem like anyone's tried it yet.) I'll post results as soon as I finish trying, but it's slow-going.

I think I messed up again

For starters, I have an AT&T HTC M9. I unlocked the bootloader, and after a while, got TWRP 3.0.2.0 installed as the custom recovery. I decided to flash ARHD, since that's my personal favorite that I've used on my M7 and M8. After flashing and clearing cache, the phone optimizes apps, reboots, and then stays at the HTC screen for a bit. Finally, the screen will turn off as if it's booted in. I could then wake the device and adjust volume and such, but I still had the HTC logo covering what would be the UI. After a bit more time, the setup menu finally came up. I couldn't set up wifi, as it got stuck on the "connecting" screen. Wiped, re-flashed ARHD. Same thing. Finally got through the setup, and I had no service. What am I doing wrong? Do I need to install a corresponding firmware or something? This happens to me every time. Also the M9 had Android 6.0 with Sense 7.0, for the record.

Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.

shivadow said:
Have you made sure that the rom is compatible with your phones firmware?.
Beamed in by telepathy.
Click to expand...
Click to collapse
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?

manlavi95 said:
The thread says it's built off of 3.35.401.12, and my phone is running 3.38.502.12. The thread goes on to say "- If your current firmware version doesn't match ROM firmware version, wiping data inside AROMA is highly recommended!" so I figured if I wiped the data inside AROMA it would still work. Am I just dumb?
Click to expand...
Click to collapse
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs

Flippy498 said:
Please read the FAQ section of the Readme thread which is pinned above the normal questions here in the Q&A section. There you'll find the reason and the solution for the no service problem.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Edit: I've got an RUU that I was thinking of using and then just rooting the stock ROM and then going about my day. I'd be ok with that if I knew for a fact that it wouldn't remove TWRP. That and I was looking forward to the ARHD battery life.

manlavi95 said:
"For Sense-based roms you just need to re-flash the stock boot image of your current firmware version." I'm now at a loss. I am in way over my head right now. So technically speaking, I'd be able to get ARHD to run on my ATT M9? That quoted sentence gave me an anxiety attack.
Click to expand...
Click to collapse
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).

Flippy498 said:
Keep calm. All you need to do is downloading the RUU for your current firmware and the decryption tool that is linked in my thread. Drag'n'drop the RUU onto the *.exe file of the tool and wait some minutes. When it's finished it will give you an output folder. Inside you'll find a firmware folder and inside that one you'll find the needed boot image. All you need to do then is booting your phone to download mode and connecting it via USB with your pc. Copy the boot.img into your adb/fastboot folder and use
Code:
fastboot flash boot <enter name of the boot image - including its file extension - here and delete the less/greater symbols>
E.g. if the file is named boot_signed.img the command would be
Code:
fastboot flash boot boot_signed.img
The next time you boot your rom everything should be working, fine.
Edit: Your edit didn't exist when I wrote this post... The RUU will remove TWRP if you flash it. RUUs always reflash the whole phone (in other words: the system and the firmware).
Click to expand...
Click to collapse
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?

manlavi95 said:
It appears that I may have given some misinformation. Looking in the ROM that I had flashed (Official Build ATT 3.38.502.12 ROM 7-12-2016), the firmware appears as (obviously) 3.38.502.12. However, looking in download mode, OS appears to actually be 3.38.502.41. Are the instructions you gave me still pertinent, or do I need to try something else?
Click to expand...
Click to collapse
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.

Flippy498 said:
In that case you will need the boot image of firmware 3.38.502.41. The correct firmware version of your phone is stated in the download mode. You're lucky since HTC released a RUU for that firmware, as well.
There are two main problems with HTCs website:
a) They only provide RUUs for their US customers. So be happy that you bought a US varaint of the M9.
b) They don't update their website that regularly although the files are already available. Since the URL isn't that complicated you can simply guess the correct one for newer RUUs.
Click to expand...
Click to collapse
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?

manlavi95 said:
Done deal. So after flashing ARHD and then re-flashing the boot image, I can happily go on my way with a nifty AT&T M9 with ARHD?
Click to expand...
Click to collapse
Based on my previous experiences with the M9 I'd say yes.

Flippy498 said:
Based on my previous experiences with the M9 I'd say yes.
Click to expand...
Click to collapse
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.

manlavi95 said:
Thank you for preventing me from dying today. I'll see what I can do. Also, I was sitting here, looking at the HTC site, and I found all the ROMs, but for the life of me could not find the right one. That was when I noticed you had linked it to me. Now I'm actually wondering where you're finding these.
Click to expand...
Click to collapse
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.

Flippy498 said:
On their website. Take a look at the URL of the download for the older 3.38.502.12 RUU you can find there, then take a look at your current firmware. If you now look at the link for the latest RUU I posted you'll understand how I guessed the correct link. It's no magic.
Click to expand...
Click to collapse
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Another edit: I also don't see SuperSU anywhere, and that's confusing me just a bit.

manlavi95 said:
Ok, so I flashed the ROM, (ARHD 20.0, 6.0, Sense 7.0) and then flashed the boot. Phone boots up fine, I now have signal and data, but there is one issue. I have no wifi. Is this...radio-related?
Click to expand...
Click to collapse
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.

Flippy498 said:
No, the radio/baseband doesn't deal with the WIFI reception. There are other parts of the firmware like the wcnss that are responsible for that. You may want to ask in the dedicated rom thread for further help. I haven't heard of such wifi problems before.
In regard to your edit: I never flashed ARHD. I can't even tell you whether it's using SuperSU or any other superuser app.
Click to expand...
Click to collapse
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.

manlavi95 said:
Alrighty, so it appears support has ended for ARHD. I'll go ahead and ask in the thread anyway, but out of curiosity, I checked out Viper. Looks like that won't work with AT&T. I'll try out ICE maybe. I need more practice.
Click to expand...
Click to collapse
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.

Flippy498 said:
Well, you could use viper. You just need to choose default in the aroma installer. But I don't know whether your reception is supported out of the box or not. And since viper 5 is based on a HTC 10 port the boot image trick might not work, either. Viper 4 on the other hand should be working fine in case you need to reflash the boot image since it's based on the latest wwe M9 firmware.
Click to expand...
Click to collapse
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.

manlavi95 said:
Would you... recommend Viper by chance? I'm trying to weigh my options at this point.
Click to expand...
Click to collapse
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)

Flippy498 said:
I guess my signature should be sufficent for answering that question.
(And yes, I do know that my firmware and the TWRP version I'm using are outdated. I didn't have the time nor the motiviation that would be needed for updating them. I'll probably just wait until HTC distributes android 7 for my SKU.)
Click to expand...
Click to collapse
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.

manlavi95 said:
I hope I'm not taking up too much of your personal time from asking such questions, as the thread's original question has been answered. I'm currently looking at how to install 5.3, because it looks like a wonderful ROM to have.
Click to expand...
Click to collapse
Flash it like any other rom. The aroma installer is actually pretty straight forward. Choose default since there is nor AT&T specific installation.
Just make sure that you read what it wants you to do. Sometimes it asks which apps you want to install and sometimes which you want to uninstall.

I have an unlocked HTC 10 with flashed verizon's radios, Need help reflashed ASAP

My radios no longer work and I need my phone to work ASAP. Please help me I will be in your debt forever!!!! I'm desperate!!

RUU it?

Black_magic100 said:
My radios no longer work and I need my phone to work ASAP. Please help me I will be in your debt forever!!!! I'm desperate!!
Click to expand...
Click to collapse
If you have US unlocked HTC 10, see if this will work for you. There is a link to file at the bottom. http://www.htc.com/us/support/htc-10/news/

Charkatak said:
If you have US unlocked HTC 10, see if this will work for you. There is a link to file at the bottom. http://www.htc.com/us/support/htc-10/news/
Click to expand...
Click to collapse
My phone says it is already up to date.

Black_magic100 said:
My phone says it is already up to date.
Click to expand...
Click to collapse
The link is to an ruu, which will reflash all partitions to stock, including radios.

Tarima said:
The link is to an ruu, which will reflash all partitions to stock, including radios.
Click to expand...
Click to collapse
But I don't want stock radios, right? I have an unlocked 10 that I am trying to make work with Verizon's radios without converting it to a Verizon phone.

Black_magic100 said:
But I don't want stock radios, right? I have an unlocked 10 that I am trying to make work with Verizon's radios without converting it to a Verizon phone.
Click to expand...
Click to collapse
OK it sounded like you wanted to get back to fully stock.
So you flashed the VZW radios and it stopped working? Not sure what steps you followed but the procedure is detailed in this thread and includes steps to reset your modems, which you will probably need to do to get things working properly.
https://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743

Tarima said:
OK it sounded like you wanted to get back to fully stock.
So you flashed the VZW radios and it stopped working? Not sure what steps you followed but the procedure is detailed in this thread and includes steps to reset your modems, which you will probably need to do to get things working properly.
https://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Click to expand...
Click to collapse
NO. I bought an unlocked HTC 10 phone brand new. I updated the phone, flashed the verizon radios, s offed and all that jazz. It is still an unlocked phone, but it worked with verizon's radios for several months. Yesterday, I factory reset the phone because people told me I wouldn't need to reflash the radios so I reset the phone and now my data does not work (i.e. the radios aren't working). Not sure what I need to do to fix it.

Black_magic100 said:
NO. I bought an unlocked HTC 10 phone brand new. I updated the phone, flashed the verizon radios, s offed and all that jazz. It is still an unlocked phone, but it worked with verizon's radios for several months. Yesterday, I factory reset the phone because people told me I wouldn't need to reflash the radios so I reset the phone and now my data does not work (i.e. the radios aren't working). Not sure what I need to do to fix it.
Click to expand...
Click to collapse
No data does not necessarily equal radios not working. It could be a settings thing, especially after a factory reset.
Again, have you looked at the thread I linked you, including the OP which tells you how to enter the "secret menu" of the dial pad? Reset your modems?

Tarima said:
No data does not necessarily equal radios not working. It could be a settings thing, especially after a factory reset.
Again, have you looked at the thread I linked you, including the OP which tells you how to enter the "secret menu" of the dial pad? Reset your modems?
Click to expand...
Click to collapse
Ok IDK how to reset modems, but I did check the secret menu before making this thread; I failed to mention it. The preferred network type is LTE/WCDMA/GSM auto (PRL) and the thread says "CDMA/EvDOGSM/WCDMA/LTE Auto". I do not see this option. Last night I went to sunshines live chat support and talked to beaups, but he sounded confused with my situation. Perhaps I was not explaining it clear enough. How do I get this "radio" to appear in the drop down box?

Black_magic100 said:
Ok IDK how to reset modems, but I did check the secret menu before making this thread; I failed to mention it. The preferred network type is LTE/WCDMA/GSM auto (PRL) and the thread says "CDMA/EvDOGSM/WCDMA/LTE Auto". I do not see this option. Last night I went to sunshines live chat support and talked to beaups, but he sounded confused with my situation. Perhaps I was not explaining it clear enough. How do I get this "radio" to appear in the drop down box?
Click to expand...
Click to collapse
Steps for resetting/wiping your modem settings are in the thread I linked you, from the thread do a search for 'modemst1' and you'll see it.
Other than that not sure what else to suggest, but you're probably better off asking in that thread and perhaps @dottat can help you.

updating t-mo ruu manually.

So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.

So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.

Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.

Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).

Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.

myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs

Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly: