So, I have unlocked bootloader, rooted, running custom recovery and amd currently running MDK baseband.
I do see that there have been several updates to the radio (baseband) but also a lot of stuff that gives me pause.
Is it possible for me to upgrade the baseband without loosing the unlocked bootloader, SU, and custom recovery?
If it is, is there any advantage?
I have tried almost every radio from the various updates . . none are any better in my opinion. I say leave it alone.
Sent from my Galaxy S4
RedBullet said:
So, I have unlocked bootloader, rooted, running custom recovery and amd currently running MDK baseband.
I do see that there have been several updates to the radio (baseband) but also a lot of stuff that gives me pause.
Is it possible for me to upgrade the baseband without loosing the unlocked bootloader, SU, and custom recovery?
If it is, is there any advantage?
Click to expand...
Click to collapse
I would agree, but if you want to change things, I'd recommend backing up in recovery before making any changes so you can revert easily. A lot of the custom ROMs will also update the radio, and you get a lot of other nice features and improvements (ie. better batterylife).
y157 said:
I would agree, but if you want to change things, I'd recommend backing up in recovery before making any changes so you can revert easily. A lot of the custom ROMs will also update the radio, and you get a lot of other nice features and improvements (ie. better batterylife).
Click to expand...
Click to collapse
So, can I flash the radio without impacting my unlocked bootloader/root/custom recovery? If so, what the latest and how?
RedBullet said:
So, can I flash the radio without impacting my unlocked bootloader/root/custom recovery? If so, what the latest and how?
Click to expand...
Click to collapse
For boatloads of information I would refer you to:
Sticky at the top of general
In here I think the post on the radio is in the second posting.
I still think the hassle to do the radio change only is not worth the effort.
RedBullet said:
So, can I flash the radio without impacting my unlocked bootloader/root/custom recovery? If so, what the latest and how?
Click to expand...
Click to collapse
You can flash radios without affecting anything else if you do it correctly. Go to the modems thread on the first page of this section and follow the instructions Surge posted.
Usually the radios don't make much difference, but you could at least update to mj7, which enables LTE band 4, a new & faster band if it is activated in your area.
Sent from my SCH-I545 using XDA Premium 4 mobile app
HELLO!
Alright, this might be a difficult question to get a simple answer but I'm willing to learn a few new things from this in return!
The other day I decided to try out a new custom rom on my HTC One M7ATT, and with great success I was able to flash the latest Insert Coin rom running Android 4.4.2 and Sense 6. My problem formed when I tried to flash another rom to see whats out there. I decided that latest AOKP would be a nice choice. Once I was back into my recovery and ready to flash, I found out that my phone changed over to a M7WLV, and from what I found online, my phone now thinks that it's a HTC One from Sprint. In result, I can't flash the AOKP zip through TWRP
My questions are...
#1. How do I revert my M7WLV back into a M7ATT so that I could flash my roms, without going through RUU.
#2. How come there isn't really any information out there for this magical M7WLV
I totally appreciate any and all responses, and I'll be as informative as possible at working with anyone! Thanks! : )
What exactly is saying that model number?
Sent from my HTC One using XDA Premium 4 mobile app
seventiespaintbox said:
HELLO!
Alright, this might be a difficult question to get a simple answer but I'm willing to learn a few new things from this in return!
The other day I decided to try out a new custom rom on my HTC One M7ATT, and with great success I was able to flash the latest Insert Coin rom running Android 4.4.2 and Sense 6. My problem formed when I tried to flash another rom to see whats out there. I decided that latest AOKP would be a nice choice. Once I was back into my recovery and ready to flash, I found out that my phone changed over to a M7WLV, and from what I found online, my phone now thinks that it's a HTC One from Sprint. In result, I can't flash the AOKP zip through TWRP
My questions are...
#1. How do I revert my M7WLV back into a M7ATT so that I could flash my roms, without going through RUU.
#2. How come there isn't really any information out there for this magical M7WLV
I totally appreciate any and all responses, and I'll be as informative as possible at working with anyone! Thanks! : )
Click to expand...
Click to collapse
The problem you will run into it that the hardware radio on the ATT phone is not the same as the Verizon phone. That being said there are some Verizon AWS bands used for data that the ATT phone won't support and there is no magic bullet for this issue.
Solarenemy68 said:
The problem you will run into it that the hardware radio on the ATT phone is not the same as the Verizon phone. That being said there are some Verizon AWS bands used for data that the ATT phone won't support and there is no magic bullet for this issue.
Click to expand...
Click to collapse
So what I'm picking up from this is that when I flashed the rom that I originally wanted to use, I ended up flashing it along with a kernel that changed my radio over to Verizon from ATT. From what my bootloader is telling me, my radio's image 4A.14.3250.13
Since I'm still getting service through my carrier (ATT) I imagine that the M7WLV was due to something else
Would you think that it would be safe to try to wipe my phone back into it's original unlocked state and start over?
Thanks for getting back to me on this man!!
seventiespaintbox said:
So what I'm picking up from this is that when I flashed the rom that I originally wanted to use, I ended up flashing it along with a kernel that changed my radio over to Verizon from ATT. From what my bootloader is telling me, my radio's image 4A.14.3250.13
Since I'm still getting service through my carrier (ATT) I imagine that the M7WLV was due to something else
Would you think that it would be safe to try to wipe my phone back into it's original unlocked state and start over?
Thanks for getting back to me on this man!!
Click to expand...
Click to collapse
relock the bootloader and RUU back to stock
fastboot oem lock
try this one first
http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
alt download site http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if you have problem with those try the 4.4.2 RUU here
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
i wanna get an s-off with sunshine and install arhd rom after but my firmware isnt up to date so i was told to get a stock rom and update there.
Any suggestions on where i start and how to do it please?
Thanks
dimakiller3 said:
i wanna get an s-off with sunshine and install arhd rom after but my firmware isnt up to date so i was told to get a stock rom and update there.
Any suggestions on where i start and how to do it please?
Thanks
Click to expand...
Click to collapse
I can't make sense of your post so I can't help you. Maybe you could reword what your trying to do because firmware has nothing to do with a stock ROM.
basically i installed a new custom rom ARHD and my wifi doesnt work there. After searching on the web apparently it's a firmware problem. I was told that if i install a stock rom and update the firmware there and reinstall the ARHD again my wifi will work.
dimakiller3 said:
basically i installed a new custom rom ARHD and my wifi doesnt work there. After searching on the web apparently it's a firmware problem. I was told that if i install a stock rom and update the firmware there and reinstall the ARHD again my wifi will work.
Click to expand...
Click to collapse
OK so you need the latest firmware are you S-Off? If so You need to download your device latest firmware an fastboot it. I would try that before I reflashed ROM..if you still don't have WiFi then I would a restore a stock backup you should have made or go to the development section an find an flash a stock rom
dimakiller3 said:
basically i installed a new custom rom ARHD and my wifi doesnt work there. After searching on the web apparently it's a firmware problem. I was told that if i install a stock rom and update the firmware there and reinstall the ARHD again my wifi will work.
Click to expand...
Click to collapse
No, for the AT&T version that actually will not work. OTA will only update you to 4.4.4, and current ARHD is 5.0 (assume current Lollipop based ARHD is what you want).
Further, if you update to 4.4.4 OTA, this will break sunshine, and you won't be able to get s-off. So you will be essentially stuck on 4.4.4 firmware until AT&T releases Lollipop.
If you want to run Lollipop now (and any current ROM based on it, like ARHD) my advice is to s-off now. Then update to LP firmware manually.
redpoint73 said:
No, for the AT&T version that actually will not work. OTA will only update you to 4.4.4, and current ARHD is 5.0 (assume current Lollipop based ARHD is what you want).
Further, if you update to 4.4.4 OTA, this will break sunshine, and you won't be able to get s-off. So you will be essentially stuck on 4.4.4 firmware until AT&T releases Lollipop.
If you want to run Lollipop now (and any current ROM based on it, like ARHD) my advice is to s-off now. Then update to LP firmware manually.
Click to expand...
Click to collapse
I have 4.4.4 and don't know the firmware number (because of the known bug in a previous version of TWRP).
You've probably described why I can't get S-Off with Sunshine to flash the latest AT&T rom so I can know my firmware number.
I need to know it so I can flash stock backup & recovery and then viper.
Any recommendations? My thanks in advance!
Wombat Pete said:
I have 4.4.4 and don't know the firmware number (because of the known bug in a previous version of TWRP).
Click to expand...
Click to collapse
Look at your hboot number in bootloader.
3.16 = 1.x software (Android 4.4.2)
3.17 = 2.x (4.4.3)
3.19 = 3.x (4.4.4)
Lollipop (Android 5.0) also uses hboot 3.19. But as already mentioned, AT&T hasn't released an offiicial LP update yet. So this can't be the case for you.
Wombat Pete said:
You've probably described why I can't get S-Off with Sunshine to flash the latest AT&T rom so I can know my firmware number.
Click to expand...
Click to collapse
If you are hboot 3.19, sunshine won't work. Any earlier hboot, and it should work. If you updated to 4.4.4 by official means (OTA or RUU) then you have hboot 3.19, and sunshine won't work.
Wombat Pete said:
I need to know it so I can flash stock backup & recovery and then viper.
Click to expand...
Click to collapse
I don't understand what you hope to accomplish by flashing stock back and recovery. Neither will affect your firmware.
If you want to run any Lollipop based ROM (including current Viper) you need to update firmware, and on the AT&T device that means you need s-off. At least until AT&T releases LP officially.
So no, what you suggested won't work.
redpoint73 said:
I don't understand what you hope to accomplish by flashing stock back and recovery. Neither will affect your firmware.
If you want to run any Lollipop based ROM (including current Viper) you need to update firmware, and on the AT&T device that means you need s-off. At least until AT&T releases LP officially.
So no, what you suggested won't work.
Click to expand...
Click to collapse
What I'm trying to do is simply what is described on this page: http://venomroms.com/viperonem8_3-0-0-requirements/
Am I misunderstanding it? I also felt there's something odd there - or, at least, I don't understand WHY flashing the stock back-up and recovery would be necessary to flash Viper. But isn't that what it says?
I would LOVE to understand the process - what's described in that process - better!
Any guidance will be greatly appreciated.
Wombat Pete said:
What I'm trying to do is simply what is described on this page: http://venomroms.com/viperonem8_3-0-0-requirements/
Am I misunderstanding it? I also felt there's something odd there - or, at least, I don't understand WHY flashing the stock back-up and recovery would be necessary to flash Viper. But isn't that what it says?
Click to expand...
Click to collapse
You're missing a key step(s): its restore stock ROM and stock recovery for the purpose of then updating via OTA. Reason for this, is that the OTA will update your firmware (for most carriers, that means updating firmware to Lollipop).
This won't work for you (having the AT&T version), since you appear to already be on the most current AT&T OTA (4.4.4). That means you are on KitKat firmware, but need Lollipop firmware to run any LP based Sense ROMs.
Also note that the page you linked is outdated, as it refers to 4.4.4, since that was what ViperOne was based on at the time (but its been updated to LP for a while now).
I have just read that sunshine has been updated to work on 4.4.4. I think this has literally happened just on the last day or so. So your options are to sunshine s-off and update your firmware. Or else wait for AT&T to release LP, and update by official OTA or RUU.
redpoint73 said:
You're missing a key step(s): its restore stock ROM and stock recovery for the purpose of then updating via OTA. Reason for this, is that the OTA will update your firmware (for most carriers, that means updating firmware to Lollipop).
This won't work for you (having the AT&T version), since you appear to already be on the most current AT&T OTA (4.4.4). That means you are on KitKat firmware, but need Lollipop firmware to run any LP based Sense ROMs.
Also note that the page you linked is outdated, as it refers to 4.4.4, since that was what ViperOne was based on at the time (but its been updated to LP for a while now).
I have just read that sunshine has been updated to work on 4.4.4. I think this has literally happened just on the last day or so. So your options are to sunshine s-off and update your firmware. Or else wait for AT&T to release LP, and update by official OTA or RUU.
Click to expand...
Click to collapse
Redpoint, thanks! As posted on the other site, the new Sunshine option worked perfectly - I now have S-Off. Very, very cool.
So I'm on to your option one - update firmware so I can get viper on the device. Is there a recommended firmware update? How would I find this myself the next time?
Wombat Pete said:
So I'm on to your option one - update firmware so I can get viper on the device. Is there a recommended firmware update? How would I find this myself the next time?
Click to expand...
Click to collapse
The "right" firmware is a tricky question. I'd start with the 4.16.1540 firmware posted along with the ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
This is US Dev Edition firmware, which is specifically intended for AT&T's network.
Now whether it plays well with Viper or ARHD, is another question. Or whether those ROMs play well on AT&T's network is also another complicated question. AT&T does some annoyingly unique things to their network, that doesn't always play well with the "international" based ROMs. In particular, AT&T's LTE seems to be playing havoc on some "international" ROMs; possibly due to AT&T beginning implementation of HD Voice (Voice over LTE or VoLTE).
Trial and error is the best you can do. Start with the 1540 firmware I suggested, and your desired ROM, and see how it goes. But WiFi will be fixed, I can tell you that.
Also, the ROM included on the link I provided is intended specifically for use on AT&T (one of the few current ROMs that is). So if you want a LP ROM that will work seamlessly on AT&T's network, flash WNC's ROM and the 1540 firmware.
redpoint73 said:
The "right" firmware is a tricky question. I'd start with the 4.16.1540 firmware posted along with the ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
This is US Dev Edition firmware, which is specifically intended for AT&T's network.
Now whether it plays well with Viper or ARHD, is another question. Or whether those ROMs play well on AT&T's network is also another complicated question. AT&T does some annoyingly unique things to their network, that doesn't always play well with the "international" based ROMs. In particular, AT&T's LTE seems to be playing havoc on some "international" ROMs; possibly due to AT&T beginning implementation of HD Voice (Voice over LTE or VoLTE).
Trial and error is the best you can do. Start with the 1540 firmware I suggested, and your desired ROM, and see how it goes. But WiFi will be fixed, I can tell you that.
Also, the ROM included on the link I provided is intended specifically for use on AT&T (one of the few current ROMs that is). So if you want a LP ROM that will work seamlessly on AT&T's network, flash WNC's ROM and the 1540 firmware.
Click to expand...
Click to collapse
Perfect, that's all helpful and good to know.
For full disclosure: I'm on T-Mobile; it's the same network, I believe, so that probably doesn't change anything, but I mention it just in case.
So the process I'm planning to do it:
1.) Flash the ATT_4_16_1540_8_M8_Lollipop_Firmware and ROM
http://goo.gl/iumj9r
2.) Flash the latest Viper ROM.
3.) If it gives me trouble, flash firmware & from 1., above, to go back to that.
Does that sound right?
Also, do people restore s-on when they have their desired setup, or just leave the phone S-off?
Wombat Pete said:
For full disclosure: I'm on T-Mobile; it's the same network, I believe, so that probably doesn't change anything, but I mention it just in case.
Click to expand...
Click to collapse
T-Mobile and AT&T are not even remotely the same network. I know for a fact, the 1540 firmware I previously suggested (thinking you were on AT&T) does not include the AWS band that T-Mobile most commonly uses for 3G. And T-Mobile uses some different bands for LTE than AT&T.
T-Mobile has deployed 1900 MHz 3G band in select markets, in hopes of luring AT&T users (without having to swap devices). But only in certain cities.
Its best you flash T-Mobile firmware, for use on T-Mobile's network.
Wombat Pete said:
Also, do people restore s-on when they have their desired setup, or just leave the phone S-off?
Click to expand...
Click to collapse
Typically, no. In fact, if you ever want to s-off again, I believe you have to pay the $25 for sunshine again.
For the most part, there is no real downside to staying s-off, in my opinion. Just be careful that you only flash anything meant specifically for the M8 (and the GSM version, at that, nothing for the CDMA). As s-off means many checks are bypassed, and you can accidentally flash something meant for another device that bricks the phone, if you are careless. But always be careful about what you flash, and staying s-off is fine.
redpoint73 said:
T-Mobile and AT&T are not even remotely the same network. I know for a fact, the 1540 firmware I previously suggested (thinking you were on AT&T) does not include the AWS band that T-Mobile most commonly uses for 3G. And T-Mobile uses some different bands for LTE than AT&T.
T-Mobile has deployed 1900 MHz 3G band in select markets, in hopes of luring AT&T users (without having to swap devices). But only in certain cities.
Its best you flash T-Mobile firmware, for use on T-Mobile's network.
Typically, no. In fact, if you ever want to s-off again, I believe you have to pay the $25 for sunshine again.
For the most part, there is no real downside to staying s-off, in my opinion. Just be careful that you only flash anything meant specifically for the M8 (and the GSM version, at that, nothing for the CDMA). As s-off means many checks are bypassed, and you can accidentally flash something meant for another device that bricks the phone, if you are careless. But always be careful about what you flash, and staying s-off is fine.
Click to expand...
Click to collapse
Understood. Is there a similar link to recommended firmware for T-Mobile?
And then the main thing - is the process I suggest right? 1.) Flash new LP firmware; 2.) Flash the latest viper ROM; 3.) If I have trouble with viper that I can't solve, flash a ROM made for T-Mobile. Does that sound right? If so, i just need to determine the best firmware choice... and what are criteria might I use for that?
Wombat Pete said:
Understood. Is there a similar link to recommended firmware for T-Mobile?
Click to expand...
Click to collapse
I can't actually find the Lollipop T-Mobile US firmware at first glance. The firmware collection is below (with instructions how to flash). But if you go to the firmware collection link (531 folder under HTC M8 is for T-Mobile) it only has 3.x firmware (Android 4.4.4):
http://forum.xda-developers.com/showthread.php?t=2696282
I'll look some more, but you can search as well.
Now, if I understand you have the AT&T version (please confirm)? If so, flashing T-Mobile firmware (once we find it) is a little more complicated than flashing AT&T firmware on an AT&T device. You will need to change your CID and MID to T-Mobile's, in order to flash the T-Mobile firmware.
The following guide shows how to change the CID and MID. But you will need to find the T-Mobile US CID. I don't know if off hand (or where to find it quickly), so you might do your own research on that one. Keeping in mind that T-Mobile is also a carrier in Europe, so make sure is the T-Mobile US CID.
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
Wombat Pete said:
And then the main thing - is the process I suggest right? 1.) Flash new LP firmware; 2.) Flash the latest viper ROM; 3.) If I have trouble with viper that I can't solve, flash a ROM made for T-Mobile. Does that sound right? If so, i just need to determine the best firmware choice... and what are criteria might I use for that?
Click to expand...
Click to collapse
I don't think T-Mobile is nearly as troublesome as AT&T (although you might check the T-Mobile M8 forum section on that, or the Viper thread). I have a feeling that once you are on the T-Mobile firmware, and flash Viper, you will be fine.
redpoint73 said:
I can't actually find the Lollipop T-Mobile US firmware at first glance. The firmware collection is below (with instructions how to flash). But if you go to the firmware collection link (531 folder under HTC M8 is for T-Mobile) it only has 3.x firmware (Android 4.4.4):
http://forum.xda-developers.com/showthread.php?t=2696282
I'll look some more, but you can search as well.
Now, if I understand you have the AT&T version (please confirm)? If so, flashing T-Mobile firmware (once we find it) is a little more complicated than flashing AT&T firmware on an AT&T device. You will need to change your CID and MID to T-Mobile's, in order to flash the T-Mobile firmware.
The following guide shows how to change the CID and MID. But you will need to find the T-Mobile US CID. I don't know if off hand (or where to find it quickly), so you might do your own research on that one. Keeping in mind that T-Mobile is also a carrier in Europe, so make sure is the T-Mobile US CID.
http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
I don't think T-Mobile is nearly as troublesome as AT&T (although you might check the T-Mobile M8 forum section on that, or the Viper thread). I have a feeling that once you are on the T-Mobile firmware, and flash Viper, you will be fine.
Click to expand...
Click to collapse
Confirming: I am using T-Mobile as the carrier, but the device was made for AT&T.
Is this what we're looking for? http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
And, if so... as I'm S-off, I don't need to go through the stock ROM/stock recovery steps, and there's also no need to re-lock, RIGHT? I'd like to be as sure as possible that I'm doing the right steps in the right order.
Wombat Pete said:
Is this what we're looking for? http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
And, if so... as I'm S-off, I don't need to go through the stock ROM/stock recovery steps, and there's also no need to re-lock, RIGHT? I'd like to be as sure as possible that I'm doing the right steps in the right order.
Click to expand...
Click to collapse
You are correct. RUU will give you a complete stock T-Mobile image, not just the firmware you want, but also stock T-Mobile Lollipop ROM, stock recovery, etc. Its a bit of a nuclear option, if the main intent is to just update firmware and install Viper. But it will get the job done.
Also correct that there is no need to relock bootloader to RUU, since you are s-off. But you need to change to T-Mobile CID and MID to run the RUU.
What you will have after changing CID/MID and running the T-Mobile RUU is essentially a T-Mobile M8, in everything except the stupid AT&T logo on back of the phone!
If you want to install a custom ROM after that, just flash TWRP back onto the phone, and flash the desired ROM.
redpoint73 said:
You are correct. RUU will give you a complete stock T-Mobile image, not just the firmware you want, but also stock T-Mobile Lollipop ROM, stock recovery, etc. Its a bit of a nuclear option, if the main intent is to just update firmware and install Viper. But it will get the job done.
Also correct that there is no need to relock bootloader to RUU, since you are s-off. But you need to change to T-Mobile CID and MID to run the RUU.
What you will have after changing CID/MID and running the T-Mobile RUU is essentially a T-Mobile M8, in everything except the stupid AT&T logo on back of the phone!
If you want to install a custom ROM after that, just flash TWRP back onto the phone, and flash the desired ROM.
Click to expand...
Click to collapse
OK... so I think this makes sense. Is this the process, then?
1.) I change to T-Mobile CID and MID
2.) Then... to run the RUU, do I need to be in fastboot? Just have the phone plugged in? Run it from the fastboot directory? Put it in the phone memory?
I'd be running THIS, I gather: RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
Wait... that can't be right, given that the name includes "ATT" and "Cingular". I suppose they mean I have to find it myself... here? http://www.htc.com/us/support/htc-one-t-mobile/news/ Yes, the download at the end of this page, right? And it won't brick the phone so long as I'm S-off...
...does that seem right?
3.) Then I flash VIPER over that. If I have any problems with VIPER, I should be able to run this RUU again? Is that the best approach, do you think?
---------- Post added at 12:36 AM ---------- Previous post was at 12:24 AM ----------
Two additional things:
First, HTC (not surprisingly) refuses to say whether the RUU will work, even with S-off.
Second, a note from the chat, which I post for common interest here:
ME: T-Mobile and AT&T are the same, physically, right? Only SOFTWARE differences, right? Not hardware differences, right?
HTC Agent: Almost everything is the same. But the frequencies of the antenna are different.Don't know whether this affects our process here, but thought it might be interesting.
Also, after the RUU I'd be S-Off, but locked? Unlock again? Not that that should be difficult...
Wombat Pete said:
OK... so I think this makes sense. Is this the process, then?
1.) I change to T-Mobile CID and MID
2.) Then... to run the RUU, do I need to be in fastboot? Just have the phone plugged in? Run it from the fastboot directory? Put it in the phone memory?
I'd be running THIS, I gather: RUU_M8_[email protected]41216A_40.34.C35006.02_F_release_407726_signed_2.exe
Wait... that can't be right, given that the name includes "ATT" and "Cingular". I suppose they mean I have to find it myself... here? http://www.htc.com/us/support/htc-one-t-mobile/news/ Yes, the download at the end of this page, right? And it won't brick the phone so long as I'm S-off...
...does that seem right?
3.) Then I flash VIPER over that. If I have any problems with VIPER, I should be able to run this RUU again? Is that the best approach, do you think?
Click to expand...
Click to collapse
1) Correct
2) Normally, you just have the phone booted; and the RUU will reboot the phone to fastboot automatically. There are a few instances where some folk have to put the phone into fastboot mode manually. But it will normally work the way the instructions tell you.
Run the RUU executable from your PC. It doesn't matter where the file is located.
Use the RUU linked at the bottom of the HTC support page for the T-Mobile version.
3) After RUU, you will need to flash TWRP again; as RUU write stock recovery over whatever was there before (TWRP in your case). After flashing TWRP, then you can flash Viper.
Yes, if Viper give you trouble you can always use the RUU again.
Wombat Pete said:
Two additional things:
First, HTC (not surprisingly) refuses to say whether the RUU will work, even with S-off.
Click to expand...
Click to collapse
They won't say that the T-Mobile RUU will run on the AT&T version, if that is what you asked them. HTC doesn't want you "converting" the device from one carrier version to another; since it contrary to what the carriers want.
Similarly, they won't want to acknowledge s-off since they don't like the mod community hacking/exploiting s-off in the first place.
Wombat Pete said:
Second, a note from the chat, which I post for common interest here:
ME: T-Mobile and AT&T are the same, physically, right? Only SOFTWARE differences, right? Not hardware differences, right?
HTC Agent: Almost everything is the same. But the frequencies of the antenna are different.Don't know whether this affects our process here, but thought it might be interesting.
Click to expand...
Click to collapse
I think that agent is simply wrong here. Snapdragon 801, band support is software based, for all but CDMA bands (which require different hardware).
If you search the forums, I'm pretty certain there are other users on these forums that have done exactly what you are proposing: converting the AT&T version to T-Mobile. I may have even helped one or 2 users do it.