hello guys
please help me here, i got a mobile from a friend and it is AT&T One M8, it has lot of unnecessary apps and its not possible for me to share net via hotspot.
So i went and done root but can not able to get S-off and i really can't pay $25.
please can any one tell me how get at least official Asia or Indian OS.
Mobile condition
Rooted
CID HTC__001
factory unlocked.
Please help me to get another OS. Thanks in Advance.:angel::crying:
Not at this time. Your only option is to pay. Firewater was the last option to s-off and that project was abandoned
If you're looking to delete at&t apps to free up space, ROM toolbox and Titanium Backup in the play store will work just fine to delete those apps
You have a few options:
1) Unlock bootloader, flash custom recovery. Then flash just about any ROM that is not AT&T based, that supports your firmware (hboot, radio, etc.). Basically, any ROM is better than AT&T stock, in my opinion.
2) Unlock bootloader, flash custom recovery and root. Than manually delete what apps you want (as suggested above) and apply WiFi tethering hack.
3) Pay for sunshine s-off, and convert to another CID, such as Developer Edition. Not only will this get you on a clean (no AT&T branding or limitations) stock base (and Lollipop at that), but allow OTA updates as well.
Firewater was discontinued (as mentioned above). Firewater was an online service, so it no longer works now that the dev has stopped supporting it. Sunshine is the only s-off method at this time, so you can stop trying to s-off by some "other" method unless you have some advanced development skills and intend to find you own exploit.
redpoint73 said:
3) Pay for sunshine s-off, and convert to another CID, such as Developer Edition. Not only will this get you on a clean (no AT&T branding or limitations) stock base (and Lollipop at that), but allow OTA updates as well.
Firewater was discontinued (as mentioned above). Firewater was an online service, so it no longer works now that the dev has stopped supporting it. Sunshine is the only s-off method at this time, so you can stop trying to s-off by some "other" method unless you have some advanced development skills and intend to find you own exploit.
Click to expand...
Click to collapse
I would suggest to do this. Converting an AT&T branded phone to Developer Edition is fantastic because of all the benefits that were already mentioned. Believe me, you won't be disappointed. I had to pay $25 to get S-off but I don't regret my decision, since immediately I got Lollipop and had the option to tethering and without bloatware.
neha12347 said:
please help me here, i got a mobile from a friend and it is AT&T One M8
Mobile condition
Rooted
CID HTC__001
factory unlocked.
Click to expand...
Click to collapse
Hold on, that isn't the AT&T CID. So either the CID has been modified (s-off required to do so), its not the AT&T version, or CID listed incorrectly above.
AT&T version of the M8 has the AT&T "globe" logo on the back of the phone.
Related
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Famous22 said:
I recently unlocked my bootloader and rooted my phone. I installed TWRP and flashed a couple of custom roms ( GPE & Revolution HD ) I decided i want to go back to stock. I understand so far i gotta unroot, flash stock rom and re lock bootloader. I read something about RUU files. Any one have suggestion or help how i go about this? Again, i have AT&T varient, currently on Revolution HD Rom
Click to expand...
Click to collapse
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
TheEmpyre said:
There is currently no RUU available as of right now. I think the best you can do for now is to a TWRP restore. There is a stock rooted TWRP in the Android Dev forum. Although this won't un-root you, its closest to stock that you will get. For the future, always make a backup before you root and then you won't have to worry
Click to expand...
Click to collapse
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
brianray14 said:
I just ordered my device and still waiting on it to be delivered. I'm already debating on whether or not to root as I've never owned an android phone that i didn't root. From what i understand, the bootloader needs to be unlocked, then s-off, flash recovery and then root. Now, if i'm to do a nandroid of the stock ROM before I root, will I be able to lock the bootloader again, nandroid and s-on in case I need to utilize the warranty? Also, will any warranty bits show up or a tampered flag or any other problem arise that'll indicate it's been farked with? Is there a way to undo those flags? Thanks in advance to TheEmpyre or whomever else can shed some light on this.
EDIT: If the s-off is the only step that will trip the flag, is it possible to leave S, er, ON?
Click to expand...
Click to collapse
Unlocking the bootloader trips a flag. When you relock it gets rid of one flag but trips the relocked flag. Soff can get rid of all flags but you have to leave it soff. Turning it back on throws a security flag.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
redpoint73 said:
If you are current AT&T customer, and can go through them for warranty, they do not care in the least whether you are bootloader unlocked, rooted, s-off, etc.
I know AT&T written policy says otherwise (they have the right refuse warranty on modded phones) but in reality they cherish you paying that nice monthly bill every month over the modest cost of a refurb phone.
I've come over from the One X (EVITA) forum, and there were many (possibly dozens) of report from XDA users successfully returning their devices for warranty with bootloader RELOCKED, UNLOCKED, and in some cases even with custom ROMs installed! And I haven't seen any reports otherwise (AT&T denying warranty due to modded phone).
If you are not a current AT&T customer, and have to go through HTC, that is a different story.
But if you are an AT&T customer, my personal opinion is that you do not need to care about being able to return to stock, tripping flags, etc. Just mod away.
Click to expand...
Click to collapse
I can second this. I just had to replace my m8 because the speakers were crackling like crazy, my bootloader showed relocked and they told me straight up that they didn't care about that as long as it was a hardware problem and not a software problem and replaced it on the spot.
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
brianray14 said:
I was under the impression that if you were in your first year of owning the device that faulty hardware would be covered under HTC's factory warranty and not AT&T?
Click to expand...
Click to collapse
Looking at the return info, I can see where the confusion might come from. It says "Return directly to manufacturer" for 15 days or more:
http://www.att.com/shop/wireless/returnpolicy.html#fbid=KMGdewZyG_f
But AFAIK, all warranty returns go to AT&T when you work through their warranty department. You send them your defective phone, and they send you a refurb. I haven't had to go through this process myself, but this is what has been reported many times on XDA and other forums.
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
im2c0ol said:
Any update on this how to lock bootloader for HTC M8 AT&T with 4.4.3 InsertCoin 4.1.1 Rom S-On of course.
How do I lock the bootloader in order to upgrade to stock 4.4.4?
Click to expand...
Click to collapse
No "update" on this issue is required. The process has been the same for a couple years or more. Further, you've posted the same/similar question to multiple places, and its been answered already in multiple places.
Connect phone to computer in fastboot mode.
Open command prompt, and type: fastboot OEM lock
From there, you can run the RUU.
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
some_douchebag said:
if HTC allows downgrading the bootloader so I can install a custom rom after I make the mistake of taking an OTA update from ATT. With the S4 this wasn't possible. but since this is my first android phone, I was wondering if it was Samsung trying to keep the device "secure" or ATT forcing these companies to keep their bootloaders locked.
Click to expand...
Click to collapse
Once you unlock the boot loader no update can relock it. HTC offers a lot more freedom than samsung, but at the price of no warranty. So if you unlock it and shatter your screen, don't be upset like other people when htc will not warranty it. As long as you have a custom recovery, your phone cannot even physically take an ota update so nothing to worry about either way.
The Magnuson–Moss Warranty Act is in place for us consumers for this reason. The company has to prove that any modification you did, is the cause of the trouble. So if you unlock your bootloader, root, etc, then crack your screen, as the poster above mentioned, the company can not void your warranty since what you did has nothing to do with cracking your screen.
This was huge for me when I modified my car and I found this here on XDA after doing more searching
http://www.xda-developers.com/xda-tv-2/your-warranty-is-not-void-xda-tv/
Oh and yeah,,if you are outside the US, it wont work lol
some_douchebag said:
if HTC allows downgrading the bootloader
Click to expand...
Click to collapse
That depends on what you mean by "allow". You cannot downgrade the bootloader by any "official" means. You will fail version check when you try to install, as you can "normally" only flash a equal or great version number hboot.
But if you are s-off, version check is bypassed, and any hboot version can be flashed.
Similar to a previous response, my advice would be to unlock the bootloader (required if you want to flash custom ROMs anyway) and S-off the phone soon after you get it. Neither of those can be changed by any OTA.
Also, accepting OTA is not recommended on a modded phone, anyway. Whatever came in the update will usually get posted in a stock rooted form in the Development forum, and/or incorporated into custom ROMs, often within days of the OTA rolling out. And OTA will not install on a modded phone (stock recovery needs to be present). OTAs also may plug existing s-off or other exploit; preventing you from doing them if you haven't already (but as mentioned, can't make the phone s-on again). Moral of the story, I strongly recommend against OTA on any modded phone.
Some of these terms/concepts are HTC specific, so may be a bit confusing for you. I would suggest reading up on these forums, if you aren't familiar with s-off, HTC's bootloader unlock process, etc.
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
Got a stupid question and can't find the stupid question section on this forum for the M8 as in the M7 section. But, I have a new phone which I have upgraded to . I am not new to the rooting and switching roms I have done it since the One X, but , can I flash a custom recovery without unlocking the bootloader? Reason is , I use a app called Privacy Star for call blocking and just discovered by means of me having two identical phones except for the color . One has all the OTA's up to Android version 5.0.2 HTC Sense 6.0 the other is straight ouf the box and no updates, software Android 4.4.2 Sense 6.0. The app seems to work fine with 4.4.2 but the app makes the phone ringer silent after a blocked call and it has to be put in recovery and recovered or reboot the phone to get the ringer back. I know that flashing a custom recovery removes the ability to take OTA's and want to keep the phones at 4.4.2 , at least for a day or two. So can I flash a custom recovery such as TWRP without rooting? and RUU the one phone with the updates back to 4.4.2? Make sense? I hope so.
leesumm said:
Got a stupid question and can't find the stupid question section on this forum for the M8 as in the M7 section.
can I flash a custom recovery without unlocking the bootloader? I know that flashing a custom recovery removes the ability to take OTA's and want to keep the phones at 4.4.2 , at least for a day or two. So can I flash a custom recovery such as TWRP without rooting?
and RUU the one phone with the updates back to 4.4.2? Make sense?
Click to expand...
Click to collapse
I think someone did a "stupid question" thread for this section at one point, long ago. But nobody really used it, it didn't get stickied, and quickly became buried among the other threads.
No, you can't install custom recovery without unlocking the bootloader. But you can restore to stock recovery when/if you want to install an OTA.
You can RUU back to 4.4.2 if you use sunshine ($25) to s-off the phone; which removes the version check, and allows you to "downgrade".
redpoint73 said:
I think someone did a "stupid question" thread for this section at one point, long ago. But nobody really used it, it didn't get stickied, and quickly became buried among the other threads.
No, you can't install custom recovery without unlocking the bootloader. But you can restore to stock recovery when/if you want to install an OTA.
You can RUU back to 4.4.2 if you use sunshine ($25) to s-off the phone; which removes the version check, and allows you to "downgrade".
Click to expand...
Click to collapse
Thanks, wasn't sure and its been a long time since I have messed with a stock phone . I really didn't want to void the warranty just yet as the phone isn't much over 24 old so far and wanted to let it "settle" in before doing any mods on it.
leesumm said:
Thanks, wasn't sure and its been a long time since I have messed with a stock phone . I really didn't want to void the warranty just yet as the phone isn't much over 24 old so far and wanted to let it "settle" in before doing any mods on it.
Click to expand...
Click to collapse
If you want, since the phone has older software (4.4.2) you should be able to temp root and s-off with sunshine ($25) which can also unlock the bootloader without using HTCDev.com. And HTC will therefore not have a record of you unlocking the bootloader. And with s-off, all can be returned to full stock (LOCKED bootloader, s-on, etc.) so HTC would never be any the wiser.
But also note that if you purchased the phone through AT&T, modifying the phone by unlocking the bootloader (root, etc.) does not actually void your warranty. AT&T actually changed their warranty terms a year or 2 ago. The only thing that voids the warranty are physical damage and water damage. There have been numerous reports of folks that successfully got warranty service from AT&T with unlocked bootloaders. But that is just through AT&T. HTC is a whole other story.
redpoint73 said:
If you want, since the phone has older software (4.4.2) you should be able to temp root and s-off with sunshine ($25) which can also unlock the bootloader without using HTCDev.com. And HTC will therefore not have a record of you unlocking the bootloader. And with s-off, all can be returned to full stock (LOCKED bootloader, s-on, etc.) so HTC would never be any the wiser.
But also note that if you purchased the phone through AT&T, modifying the phone by unlocking the bootloader (root, etc.) does not actually void your warranty. AT&T actually changed their warranty terms a year or 2 ago. The only thing that voids the warranty are physical damage and water damage. There have been numerous reports of folks that successfully got warranty service from AT&T with unlocked bootloaders. But that is just through AT&T. HTC is a whole other story.
Click to expand...
Click to collapse
One phone has 4.4.2 software and the other has 5.0.2 software, I didn't catch the newest one soon enough and my wife did the OTA without me knowing it. The only reason I wanted the older software was the fact the app I like has a glitch in it with the newer software update and it silences the ringer . The app works fine on the phone with the 4.4.2 software I just wanted to make sure it didn't update itself
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.