So i have tried searching, but i keep reaching dead-ends or answers that have no details what-so-ever.
Im on t-mobile, and can get an unlocked ATT M8... what would i need to do to get that m8 as close to a stock t-mobile m8 as possible? can i just bootloader unlock and then just flash a t-mobile RUU? is it safe to do that to radios aswell, or would that break it? Also, is there any way to get it so far into a t-mo m8 that it can get t-mo software updates?
also, i understand there is no aws HSPA on the att variant, but im in a refarmed area, and get good LTE coverage, so i should be fine there.
as far as I am concerned all i need to to do is...
-Unlock Bootloader (which i understand costs $25 now... anyway around that?)
-Root
-S-off
-Flash Stock T-mo RUU
-change CID to T-mo...
and thats it? in that order?
You may be able to run the T-Mob RUU with the proper CID and MID. But you may need to S-off as well. Relocking the bootloader is required to run any RUU, if S-on.
Unlocking the bootloader doesn't cost anything. Its Sunshine s-off that costs $25. So you might try to unlock the bootloader, root, change CID and MID, then relock the bootloader and see if the T-Mob RUU will run, before paying for Sunshine S-off.
Running the RUU will put the T-Mob radios on your device. It won't break anything. All M8's actually have the same hardware, so installing software for another version is safe. In fact, you should also gain support for T-Mob's HSPA network by flashing T-Mob's RUU.
Myst3ry said:
as far as I am concerned all i need to to do is...
-Unlock Bootloader (which i understand costs $25 now... anyway around that?)
-Root
-S-off
-Flash Stock T-mo RUU
-change CID to T-mo...
and thats it? in that order?
Click to expand...
Click to collapse
Change MID too. I did this on the M7, no reason why it won't work on the M8. Everything worked perfect including Wi-Fi calling. Unlocking bootloader is free via HTCDEV, not sure about S-Off, I did it with Firewater for free, but maybe that doesn't work anymore?
redpoint73 said:
You may be able to run the T-Mob RUU with the proper CID and MID. But you may need to S-off as well. Relocking the bootloader is required to run any RUU, if S-on.
Unlocking the bootloader doesn't cost anything. Its Sunshine s-off that costs $25. So you might try to unlock the bootloader, root, change CID and MID, then relock the bootloader and see if the T-Mob RUU will run, before paying for Sunshine S-off.
Running the RUU will put the T-Mob radios on your device. It won't break anything. All M8's actually have the same hardware, so installing software for another version is safe. In fact, you should also gain support for T-Mob's HSPA network by flashing T-Mob's RUU.
Click to expand...
Click to collapse
I am going to try what you said, so i just find the tmobile m8 ruu and flash it ? and also i have the red text i was going to flash the custom hboot that removes it. i have a att m8, can i flash the tmobile custom hboot?
jordy787 said:
I am going to try what you said, so i just find the tmobile m8 ruu and flash it ? and also i have the red text i was going to flash the custom hboot that removes it. i have a att m8, can i flash the tmobile custom hboot?
Click to expand...
Click to collapse
Yes, both T-Mob RUU and modified hboot should be fine if you are s-off.
redpoint73 said:
Yes, both T-Mob RUU and modified hboot should be fine if you are s-off.
Click to expand...
Click to collapse
Okay thanks ! And also flashing those will gain the extra T-Mobile frequency bands ?
jordy787 said:
Okay thanks ! And also flashing those will gain the extra T-Mobile frequency bands ?
Click to expand...
Click to collapse
Yes.
redpoint73 said:
Yes.
Click to expand...
Click to collapse
Okay thanks man , Can i get the same effect by just flashing the tmobile radio ? and if i was to convert my m8 to gpe will i be able to do that method to get the tmobile bands ? Thanks
jordy787 said:
Okay thanks man , Can i get the same effect by just flashing the tmobile radio ?
Click to expand...
Click to collapse
You'll get the T-Mob bands by flashing the proper radio, yes. But you won't get official T-Mobile OTAs (just by flashing the radio) if that is the goal.
jordy787 said:
and if i was to convert my m8 to gpe will i be able to do that method to get the tmobile bands ? Thanks
Click to expand...
Click to collapse
I have to plead ignorance on that one. I believe GPE is intended to be fully compatible with AT&T's network, but is the same true for T-Mobile? If so, then yes doing the GPE conversion should give you the T-Mob bands, as well as allow you to get GPE OTAs.
redpoint73 said:
You'll get the T-Mob bands by flashing the proper radio, yes. But you won't get official T-Mobile OTAs (just by flashing the radio) if that is the goal.
I have to plead ignorance on that one. I believe GPE is intended to be fully compatible with AT&T's network, but is the same true for T-Mobile? If so, then yes doing the GPE conversion should give you the T-Mob bands, as well as allow you to get GPE OTAs.
Click to expand...
Click to collapse
Okay thanks for your help. I was going to sell my phone and try a g3 or one plus one. Do you think I could get away with selling it as a T-Mobile m8? If I flash the hboot,ruu ,T-Mobile ROM and all that is there any other way they could find out its originally a att model ? I know the back housing has the logo engraved but i was going to replace it with one that doesn't have that. Not just for that reason but because i also have some dents on mine.
jordy787 said:
I was going to sell my phone and try a g3 or one plus one. Do you think I could get away with selling it as a T-Mobile m8?
Click to expand...
Click to collapse
Why would you do such a thing? You would also have to change the MID, CID, and it might still be linked to AT&T somehow. Seems like a lot of effort, and I don't see much reason for it. Why not just sell it as an AT&T model, since it is?
Also, changing the housing is not that easy. You might mess up the phone cosmetically and do more harm than good; unless you know you are good at such replacements. Again, seems like a lot of work for nothing.
I haven't done much rooting/flashing in a while and just got an M8 that I need to move to a Tmob RUU. Currently on the ATT RUU.
From what I gathered, I need:
- Download Latest Tmob RUU
- unlock bootloader
- Change CID (MID also?)
- relock bootload
- run Tmob RUU
Is the above correct? Will I never get OTA updates? It seems that s-off and/or root is required for CID/MID changes, is that correct?
TeckniX said:
Is the above correct? Will I never get OTA updates? It seems that s-off and/or root is required for CID/MID changes, is that correct?
Click to expand...
Click to collapse
Once you are "fully converted" by RUU, you should get OTAs.
Not sure about needed s-off to change CID and MID, but I think you are correct that s-off is needed.
Thanks for the quick reply - I managed to get s-off along with the CID and MID updated. Thankfully Firewater worked for me after the 3rd bottle
Now I just need to flash the stock Tmob RUU and get the proper radios, then perhaps flash one of the lightly modded Tmob RUU.
Or can I skip the 'stock Tmob' RUU and just flash something like htc_m8_1.57_DEODEXED_InstallerFix.zip and still get the radio+OTA?
TeckniX said:
I haven't done much rooting/flashing in a while and just got an M8 that I need to move to a Tmob RUU. Currently on the ATT RUU.
From what I gathered, I need:
- Download Latest Tmob RUU
- unlock bootloader
- Change CID (MID also?)
- relock bootload
- run Tmob RUU
Is the above correct? Will I never get OTA updates? It seems that s-off and/or root is required for CID/MID changes, is that correct?
Click to expand...
Click to collapse
I don't think you need to relock the boot loader before you flash the ruu if you're soff
Related
i dont know if there is a thread about this. i really need to know how to update the rezound software on a non verizon network?
When an OTA becomes available, it won't take long before you can obtain an RUU of it which you can use. Just wait a bit and it won't matter what network you are on. You might need to unlock your bootloader to use it though.
thanks for ur information.
I thought you need the phone locked to install a RUU...
if its an official RUU, then yes, you leave your phone locked.
voxigenboy said:
if its an official RUU, then yes, you leave your phone locked.
Click to expand...
Click to collapse
Well you can unlock it and root etc., then when the RUU is available just relock it to run the RUU.
Sent from my ADR6425LVW using Tapatalk
I have an at&t branded phone. I recently switched to T-Mobile and would like to get T-Mobile ROM installed on it.
I started with a phone which was NOT rooted, had stock AT&T rom.
I have done the following so far:
*
Unlocked my boot loader - worked flawlessly
Installed TWRP - worked flawlessy
Attempted to install Super SU - I think it worked
Attempted to install a T-Mobile ROM - Getting a "Error flashing zip" error
I download official T-Mobile ROM installer from HTC website. I let the installer run until I saw "Rom.zip" in the temp folder.
A website on google told me that i can use this file to flash my phone. I did have some doubts about this file as I am able to unzip only half the file's contents using winrar. But anyways, I went ahead and used this ROM file.
I rebooted my phone in Recovery mode (TWRP). I clicked on Install and selected rom.zip from my SD Card. When I attempt to install rom.zip, I received following messages:
Installing '/external_sd/tmobile_rom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip 'external_sd/tmobile_rom.zip'
Updating partition details...
....done
I tried a few different ROM's I found on the internet with the same error message.
So now I am stuck with no OS on the phone. I can only go to bootloader or TWRP.
If someone can suggest a more appropriate ROM file, I can give that a try.
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
I have s-on. Yes, I want the full T-Mobile firmware...mixing up my terms as I am new to this.
Since I don't have an OS right now, I will first try to restore to AT&T firmware by using the stock RUU on htc website. If that's successful, I will proceed with rest of the steps.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
So I was able to get back to AT&T firmware using below steps:
booted my phone to boot fastboot mode
I re-locked my bootloader using following command: fastboot oem lock
I download the AT&T HTC One M8 Stock RUU
Ran the installation until my firmware was flashed again
I am just so happy to have a phone that works now. I will continue soon with the rest of your instructions to get T-Mobile firmware.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
After spending few hours, I have successfully installed T-Mobile firmware on my AT&T M8.
I pretty much followed your instructions. For anyone else looking to this this, here are the complete instructions.
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
And now I am enjoying a beer
Thanks redpoint73 for your helpful reply.
deepak528 said:
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
Click to expand...
Click to collapse
I think this is slightly out of sequence. You need to s-off before changing CID and MID. CID and MID cannot be modified with s-on.
wouldnt a simple rom without the firmware provide wifi calling?
PunishedSnake said:
wouldnt a simple rom without the firmware provide wifi calling?
Click to expand...
Click to collapse
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
redpoint73 said:
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
Click to expand...
Click to collapse
Agreed
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
ad4mydev said:
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
Click to expand...
Click to collapse
The RUU isn't recognizing your phone because you have a non HTC rom on your phone. Just flash one of the various stock roms from this forum and then you can use the RUU. Secondly, you don't have to re-lock your bootloader if you are s-off to run the RUU.
Fixing the Device
ad4mydev said:
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
Click to expand...
Click to collapse
<br />
Hi, Since you do have a working device with a rom on it, all you need to do is find a T-Mobile Rom that is compatible with the At&t version. Make sure this is a stock rom because an accidental flash can hard brick your device. Thanks.
johnnyutah22 said:
The RUU isn't recognizing your phone because you have a non HTC rom on your phone. Just flash one of the various stock roms from this forum and then you can use the RUU. Secondly, you don't have to re-lock your bootloader if you are s-off to run the RUU.
Click to expand...
Click to collapse
AFAIK, the ROM doesn't need to be stock to RUU, only to OTA. There doesn't even need to be a ROM on the device to RUU.
Also, if there was something wrong with the phone's configuration, an error message would have been the result; not failing to connect to the phone.
If the RUU isn't recognizing the device at all, there is probably a fundamental USB connectivity issues. OP should try to :
- Make sure phone is booted into OS, or into bootloader-fastboot mode to RUU. "Regular" bootloader mode or recovery won't work.
- Try another USB cable or port, even another computer if possible (in particular USB 3.0 doesn't play well with RUUs).
- Uninstall and re-install HTC Sync and Drivers.
Also, keep in mind that in order to run an RUU that is different from your version (which is the case for T-Mob RUU or GPE RUU on an AT&T device) you need to change the CID and MID to correspond to the RUU. This won't cause failure to connect, but will cause the RUU to fail with an error message.
---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------
kps2501 said:
Hi, Since you do have a working device with a rom on it, all you need to do is find a T-Mobile Rom that is compatible with the At&t version.
Click to expand...
Click to collapse
The AT&T variant won't support all 3G (HSPA) and 4G (LTE) bands used by T-Mobile if you just flash a T-Mob ROM. You need to install the T-Mob firmware to enable full T-Mob band support; which the RUU does.
Also, the RUU will "fully convert" to the T-Mob or GPE versions; and allow official OTA updates for that version, if that is what the OP is looking for. But the band support is the more important factor.
kps2501 said:
Make sure this is a stock rom because an accidental flash can hard brick your device.
Click to expand...
Click to collapse
Not sure what is trying to be conveyed here. No ROMs (stock or custom) meant for the "GSM" versions of the M8 (meaning stay away from Sprint and Verizon specific ROMs) will brick your phone.
Flashing a ROM meant for another device can brick your phone (and may be possible with s-off), but again, that isn't what you stated (although may be what you meant)
Thanks to all.
I ended up figuring it out using the steps below.
•ADB sideload CM12 via TWRP
•Once booted started USB debugging
•Changed the MID to the GPe (using ADB shell)
•Changed CID from CWS__001 to GOOGL001
•Rebooted into bootloader (fastboot oem rebootRUU)
•Found the RUU zip (can't post the link- too new)
•Pushed it to the phone (fastboot flash zip)
•Failed
•Flashed again
•Success
Sent from my HTC One_M8 using XDA Free mobile app
ok i have a htc one M8 AT&T i have 4.4.4 android o.s. its rooted and unlocked (network).
I just need some help ive tried to update it with ruu but i get a connection error 170 and when i turn my phone off and boot to fast boot usb it verifys info on my device and starts to update but never gets passed 1/7 update signatures
also another thing id like help with is my m8 is AT&T but if i could id like to flash it(if thats correct termi) to a tmobile rom because i have tmobile also for mms capabilities please someone help and be as thorough as possible im not stpid but i cant follow steps if you skip something
Is your bootloader locked or unlocked? Is S-on or S-off?
troysyx said:
Is your bootloader locked or unlocked? Is S-on or S-off?
Click to expand...
Click to collapse
boot loader is unlocked but tampered and s-on
Have you verified the CID is correct?
sniper7777777 said:
boot loader is unlocked but tampered and s-on
Click to expand...
Click to collapse
RUU you alway fail with an unlocked bootloader.
You need to relock the bootloader with fastboot command: fastboot oem lock
---------- Post added at 10:14 AM ---------- Previous post was at 10:10 AM ----------
sniper7777777 said:
also another thing id like help with is my m8 is AT&T but if i could id like to flash it(if thats correct termi) to a tmobile rom because i have tmobile also for mms capabilities please someone help and be as thorough as possible im not stpid but i cant follow steps if you skip something
Click to expand...
Click to collapse
Those statements don't tell me what you actually want to do. You should be able to get MMS working on T-Mobile by one of the following:
1) Enter the proper T-Mob APN. Although I think I might recall that some folks still have trouble with MMS on T-Mob using the AT&T version M8, even when the correct APN is used (so that may be what you are talking about).
2) Flash a custom ROM that specifically supports the T-Mob network.
3) "Fully convert" your phone to the T-Mob version. This may be the most desirable option, as it allows you to get future OTA updates for the T-Mob version, ensures the best compatibility with T-Mobs network. In order to fully convert, you need s-off (by sunshine), and to change the CID and MID. The following thread describes the process. But you only have to do steps 1 and 2 (change to T-Mob CID and MID) and after that you can flash the latest T-Mob RUU: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...any senior members willing to point me in the right direction? I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
HTCFAN0923 said:
So I've been unlocking and rooting/flashing phones since the HTC Universal but i'm stumped. I've downloaded the toolkit to unlock my bootloader, downloaded my .bin file and the toolkit says my bootloader is unlocked but the screen on my phone asking me whether i want to unlock it never comes out...
Click to expand...
Click to collapse
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
HTCFAN0923 said:
I'm using my AT&T M8 on T-mobile and i haven't had a single update since i bought the M8 so i need to update it ASAP.
Click to expand...
Click to collapse
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
HTCFAN0923 said:
Update: So I used the sunshine method to try and finally root my phone. Now I'm in the interesting situation where my boot loader is unlocked, it's s-off, yet there is still the stock recovery and not rooted yet. Quite the last 12 hours trying to get root access. I should be able to root it on the PC now that my boot loader is unlocked.
Click to expand...
Click to collapse
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
redpoint73 said:
The Toolkit hasn't been updated in forever, is very obsolete, and will therefore cause more problems than anything.
Toolkit just does functions that are easy to do yourself "manually" anyway. You don't need the toolkit, and you didn't need to s-off to unlock the bootloader (although it can be handy for other things).
OTA updates for the AT&T version will only be received when connected to AT&T's network (an AT&T specific annoyance). You could have updated to Lollipop using RUU.
---------- Post added at 11:28 AM ---------- Previous post was at 11:26 AM ----------
Now that the bootloader is unlocked, just flash TWRP via fastboot. Then flash SuperSU 2.46 using TWRP to obtain root.
But your OP says you want to update. Here it says you want to root. Those are 2 very different things, so its not clear what your actual goal is.
Click to expand...
Click to collapse
Thanks for the help and sorry for the confusion.
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
thanks again!
HTCFAN0923 said:
I'm looking to update my phone AND root just because I've always rooted my phones but just now got a replacement for my old laptop that broke down shortly before I got the M8. I figured since I was on T-Mobile my best bet to update it would be to root it and upload a new ROM anyway. Your suggestion is easy enough so I'll be doing that after work.
Click to expand...
Click to collapse
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
HTCFAN0923 said:
My last question is this: On the M7, I was able to use an international M7 ROM as everything apart from the radios was the same. Is that the case with the M8 as well? I typically like having Sense ROM's but hate the bloat carriers put on their RUU's....
Click to expand...
Click to collapse
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
redpoint73 said:
In that case, I would suggest updating by RUU first, and then root.
Reason I say that, is that RUU would wipe out root anyway, so no point in having to do it twice.
Whether you unlock the bootloader (via HTCDev.com) before or after RUU is somewhat irrelevant. Especially since you have s-off, so its not required to relock the bootloader to RUU (which is required with s-on).
But one other thing to consider. Since you are using the AT&T version on the T-Mobile US network; the ATT version is actually missing support for the AWS band that T-Mob uses in most areas for HSPA (3G). If you are in an area with good LTE coverage (and I'll assume NYC is) you may have not even noticed this. But if you move into an area where T-Mob doesn't have LTE, you might find that you don't have 3G either, and be pushed down to 2G (EDGE) data speed.
One cool thing about the M8, is the band support is actually software based. So one option would be to change your device's carrier ID (CID) and model ID (MID) which are possible with s-off, then flash the T-Mobile firmware or RUU to "convert" the phone to a T-Mob device including the proper T-Mob band support. After that, you can unlock the bootloader, root, flash a custom ROM.
Yes, its a similar situation on the M8. All international ROMs should work on the M8. But note that your firmware (hboot, radio, etc.) needs to be the proper version supported by the ROM. So for instance, if you are still on KitKat (sounds like you are) you will want to update firmware first, otherwise if you flash a Lollipop ROM, you will likely suffer major issues such as broken WiFi and extreme long boot times (10+ min).
Click to expand...
Click to collapse
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
HTCFAN0923 said:
Crap....went back to the toolkit to flash twrp and root it and lo and behold, my phone is now stuck in the entering recovery screen....How ****ty is that toolkit that it can't do even do a proper recovery flash right...8 years on XDA and I've never had such a headache from rooting/flashing a device....
Click to expand...
Click to collapse
I gave previous advice to stop using the toolkit, so I don't know why you insist on ignoring that advice.
Older versions of TWRP don't work on newer hboots; and the opposite is true where older hboots don't work with newer TWRP builds. This is the most frequent reason for TWRP not working properly.The toolkit worked fine at the time it was updated. But it hasn't been updated in a very long time, and therefore won't work on many M8 versions now. The issue is more your lack of understanding, and lack of following advice given to you.
Flashing TWRP is just a matter of downloading the proper version, and flashing with a single fastboot command (2 commands, if you want to be thorough and wipe cache before flashing TWRP). You don't need a toolkit for that, and again I advise stopping its use altogether.
Its not clear whether you chose to update before TWRP and root (current device status) and once I know the main version (OS number on bootloader screen) and present hboot number I can probably advice what version TWRP you need to flash.
And you're absolutely right about that. It was my fault for not listening. I was being lazy about it honestly.
I did end up using the lollipop pre rooted RUU and that worked after two atttempts. I think the issue was that the toolkit flashed the recovery without root. Add that to the fact that the toolkit caused the SD card issue to pop up made it a nightmare. Thankfully, I was able to fix it and now I'm running the AT&T lollipop ROM rooted.
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
HTCFAN0923 said:
I think the issue was that the toolkit flashed the recovery without root.
Click to expand...
Click to collapse
I don't follow. Root isn't needed to install custom recovery; nor does flashing custom recovery automatically root the phone (this has to be done as an additional step, usually by flashing SuperSU in TWRP).
I think the main issue was that the toolkit flashed an old TWRP version that was not compatible with the software/firmware that was on your phone.
HTCFAN0923 said:
You truly are the best and I thank you for the advice and help. Let me know your PayPal so I can send you beer money for the trouble.
Click to expand...
Click to collapse
I appreciate the thought; but your thanks is all I expect in return. I've benefited plenty from XDA from folks that don't ask for any monetary compensation; so I just like to give back to the community by helping how I can.