Don't currently own one, just want to make sure about a few things. Searched through the Dev forum but still I am not 100% sure and that's why I am asking here, just to confirm.
1. Is the bootloader unlocked for all firmware so I can flash custom ROMs or do I need to check something to determine if the bootloader is unlocked? I read somewhere that firmware 2.3.5 9 or above cannot be unlocked.
2. Does it come carrier unlocked by default to be used in countries other than the US, I mean use any GSM SIM?
3. What other phone can you tell me to look at, with similar specs and price range? I am interested in unlocked GSM, doesn't matter if its CDMA or not.
lamborg said:
Don't currently own one, just want to make sure about a few things. Searched through the Dev forum but still I am not 100% sure and that's why I am asking here, just to confirm.
1. Is the bootloader unlocked for all firmware so I can flash custom ROMs or do I need to check something to determine if the bootloader is unlocked? I read somewhere that firmware 2.3.5 9 or above cannot be unlocked.
2. Does it come carrier unlocked by default to be used in countries other than the US, I mean use any GSM SIM?
3. What other phone can you tell me to look at, with similar specs and price range? I am interested in unlocked GSM, doesn't matter if its CDMA or not.
Click to expand...
Click to collapse
1) Need to be on 2.3.4 in order to unlock bootloader. If ordering from sprint, it might already come with 2.3.5. Buy from eBay and make sure to have the seller confirm its on 2.3.4.
2) Its a world phone. Its only carrier locked in the united states. But there are ways around this.
3) As far as used price range, the GS2 is probably the closest mainstream competitor on sprint. Galaxy nexus being just a bit more expensive. But you lack world phone capabilities and the photon is arguably a better phone all around depending on who you ask.
Acvice said:
1) Need to be on 2.3.4 in order to unlock bootloader. If ordering from sprint, it might already come with 2.3.5. Buy from eBay and make sure to have the seller confirm its on 2.3.4.
2) Its a world phone. Its only carrier locked in the united states. But there are ways around this.
3) As far as used price range, the GS2 is probably the closest mainstream competitor on sprint. Galaxy nexus being just a bit more expensive. But you lack world phone capabilities and the photon is arguably a better phone all around depending on who you ask.
Click to expand...
Click to collapse
Thanks for that.
So if its 2.3.5, there's no way to unlock it? Something like Torpedo or 1 click unlock for Droid 3 would help?
lamborg said:
Thanks for that.
So if its 2.3.5, there's no way to unlock it? Something like Torpedo or 1 click unlock for Droid 3 would help?
Click to expand...
Click to collapse
You can root 2.3.5. but not unlock currently.
mof9336 said:
You can root 2.3.5. but not unlock currently.
Click to expand...
Click to collapse
Ok so it means that I cannot flash custom ROMs right? But I can gain root access to modify the OS installed.
Thanks
lamborg said:
Ok so it means that I cannot flash custom ROMs right? But I can gain root access to modify the OS installed.
Thanks
Click to expand...
Click to collapse
2.3.5. locked means you have to use locked roms or the phone will fail to boot.
mof9336 said:
2.3.5. locked means you have to use locked roms or the phone will fail to boot.
Click to expand...
Click to collapse
can you link me to something to read to understand what I can do/not do with root and what with unlock? I searched, got something but its quite confusing. What I understand is Root = admin access like but don't know about the unlock.
I think bootloader should be unlocked to install custom ROM but then there's something called fastboot which only requires Root. Confused here. BTW does Unlock means Unlocked Bootloader?
I want to know that if I have 2.3.5 can I install ICS or JB?
lamborg said:
can you link me to something to read to understand what I can do/not do with root and what with unlock? I searched, got something but its quite confusing. What I understand is Root = admin access like but don't know about the unlock.
I think bootloader should be unlocked to install custom ROM but then there's something called fastboot which only requires Root. Confused here. BTW does Unlock means Unlocked Bootloader?
I want to know that if I have 2.3.5 can I install ICS or JB?
Click to expand...
Click to collapse
The rules are simple: You need to unlock the bootloader to install custom ROMs that use custom kernels. You can't unlock if you are on 2.3.5. You do not need to be unlocked to use custom ROMs that use STOCK kernels. We only have two ROMs that use stock kernels. The rest, including ICS and JB, use custom kernels so you need to be unlocked to use them.
I am new to HTC as a whole. And I'm sorry if I'm missing something here. I've been spending my time reading the past couple of days trying to learn about this all.
It is mentioned but I never found a good explanation of CID and how it is relevant to anything that I have control over?
I'm currently running Trickdroid and I don't understand all of this 1.29 talk. From what I'm gathering from reading you can flash the Rom but it will not update things like the radio? Ok, How do I check my firmware/radio? version I am currently running?
Specifically am I reading beginning of dev posts and don't need to worry about this anymore because you wonderful devs have found a way to incorporate all this in just flashing a Rom?
Feeling a little overwhelmed coming from a Samsung device to all of this. So far so good, but confused and any help would be greatly appreciated..
Thank you in advance.
Dex954 said:
I am new to HTC as a whole. And I'm sorry if I'm missing something here. I've been spending my time reading the past couple of days trying to learn about this all.
It is mentioned but I never found a good explanation of CID and how it is relevant to anything that I have control over?
I'm currently running Trickdroid and I don't understand all of this 1.29 talk. From what I'm gathering from reading you can flash the Rom but it will not update things like the radio? Ok, How do I check my firmware/radio? version I am currently running?
Specifically am I reading beginning of dev posts and don't need to worry about this anymore because you wonderful devs have found a way to incorporate all this in just flashing a Rom?
Feeling a little overwhelmed coming from a Samsung device to all of this. So far so good, but confused and any help would be greatly appreciated..
Thank you in advance.
Click to expand...
Click to collapse
Radio aka baseband is almost never included in a ROM.
CID is carrier ID and every phone HTC makes has one. CID is what prevents you from installing say a UK carrier's official RUU on your At&T device.
HTC also utilizes something called SuperCID which is a carrier ID of 111111111 which allows you to install any firmware on your device. The only way at this time to get superCID is to gain S-off which is a security measure that restricts which parts of the phone software you can change.
With the HTC One, HTC changed what you have access to with an unlocked bootloader, previously, even with an unlocked bootloader you couldn't flash a kernel or a radio via recovery, now you can flash insecure kernels and HTC signed (approved) radios.
For flashing purposes, you can ignore the firmware requirements and flash the ROMs in the international section without issues.
gunnyman said:
Radio aka baseband is almost never included in a ROM.
CID is carrier ID and every phone HTC makes has one. CID is what prevents you from installing say a UK carrier's official RUU on your At&T device.
HTC also utilizes something called SuperCID which is a carrier ID of 111111111 which allows you to install any firmware on your device. The only way at this time to get superCID is to gain S-off which is a security measure that restricts which parts of the phone software you can change.
With the HTC One, HTC changed what you have access to with an unlocked bootloader, previously, even with an unlocked bootloader you couldn't flash a kernel or a radio via recovery, now you can flash insecure kernels and HTC signed (approved) radios.
For flashing purposes, you can ignore the firmware requirements and flash the ROMs in the international section without issues.
Click to expand...
Click to collapse
Ok. Thank you for that explanation. How do I check what radio/baseband I am currently using? RUU, though it can still not be changed because we have no s_off, what is it? I
Also how do I find out what CID I am?
Thank you again..
Dex954 said:
Ok. Thank you for that explanation. How do I check what radio/baseband I am currently using? RUU, though it can still not be changed because we have no s_off, what is it? I
Also how do I find out what CID I am?
Thank you again..
Click to expand...
Click to collapse
your CID if you have an AT&T HTC One is CWS_001
radio version can be found in about phone.
gunnyman said:
your CID if you have an AT&T HTC One is CWS_001
radio version can be found in about phone.
Click to expand...
Click to collapse
Ok would this be considered up to date? Why would I need to lock the bootloader again in order to update the firmware if I can just flash a Rom and it updates it for me?
Dex954 said:
Ok would this be considered up to date? Why would I need to lock the bootloader again in order to update the firmware if I can just flash a Rom and it updates it for me?
Click to expand...
Click to collapse
you are up to date, and there's no need to relock the bootloader and revert to stock for an update UNLESS HTC releases a new HBOOT (the bootloader) and the developers here will let you know if and when that's necessry
gunnyman said:
you are up to date, and there's no need to relock the bootloader and revert to stock for an update UNLESS HTC releases a new HBOOT (the bootloader) and the developers here will let you know if and when that's necessry
Click to expand...
Click to collapse
One last question as it seems you would know. Is there a thread on the s-off process and how that is coming? Or is that just background dev?
I'm sure it's being worked on by someone.
I can get back into recovery but ever since I've attempted to flash a costum rom such as Viper or Revolution it gets stuck in the splash screen.
I'm not sure whats going on but I can boot into AOKP. If someone can help me out with the appropriate steps to take to flash one of those roms OR to flash back to stock I'd really appreciate because I've been at this for a couple of hours now and my head is starting to hurt :/
You need to update your firmware to run a Sense 2.22 based ROM: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
From the linked post:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
redpoint73 said:
You need to update your firmware to run a Sense 2.22 based ROM: http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592
From the linked post:
The issues you will see without the new firmware include long boot times with no boot animations and some users on 9.1 reported wifi and bluetooth issues.
Click to expand...
Click to collapse
I see you helping a lot people here redpoint so first of all thanks.
I just used the RUU.exe to return to at&t stock software number 1.58.502.1
I've read exactly what you said about being on Sense 2.22 but that's where I'm not sure what to do since AT&T hasn't release 4.4.3 yet and theres nothing for me to update to.
Do I have to S-off to obtain Sense 2.22? And also how difficult is it to S-ON? Again thanks so much.
afrojoc said:
I just used the RUU.exe to return to at&t stock software number 1.58.502.1
Click to expand...
Click to collapse
Kind of did things the hard way, although you are back up and running. Now you will need to unlock the bootloader and install custom recovery again, to get back to where you were.
All you really needed to do was either restore your nandroid (you should always make one before flashing anything) or get a different ROM (Sense 1.xxx base) onto the phone and flash it.
Also, the phone was likely not really "stuck", just taking a REALLY LONG time to boot, like 10 minutes.
afrojoc said:
I've read exactly what you said about being on Sense 2.22 but that's where I'm not sure what to do since AT&T hasn't release 4.4.3 yet and theres nothing for me to update to.
Click to expand...
Click to collapse
The post I linked previously includes the specific firmware package for US users, and a link to detailed instructions. 2.22.1540 is what you want to use, its pulled from the US Dev Edition OTA. While its not the "official AT&T" firmware, the DE is identical to the AT&T version in everything except AT&T branding (band support, etc.) and designed specifically for use on AT&T. Users here (including myself) can confirm it works seamlessly on the AT&T version.
2.22.1540 is also specifically advocated for use on the AT&T version in the following ROM post, along with great instruction (this is personally the one I used). Although you have to download the whole ROM, as the firmware is packed with it:
http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
afrojoc said:
Do I have to S-off to obtain Sense 2.22?
Click to expand...
Click to collapse
To update the firmware as I've described, yes. Reason being, the partitions that need to be updated by the firmware (radio, hboot, etc.) can't be modified without either S-off, or "official" update meant for your version.
The other option is to remain S-on and wait until AT&T releases the OTA. But who knows when that will be . . .
afrojoc said:
And also how difficult is it to S-ON?
Click to expand...
Click to collapse
S-on isn't really necessary. As long as you understand the implications of s-off, its usually better to be s-off. More freedom, and more options to recover if you have issues.
Also, AT&T doesn't care about s-off in terms of warranty service. They only care about physical damage or water damage.
afrojoc said:
Again thanks so much. I see you helping a lot people here redpoint so first of all thanks
Click to expand...
Click to collapse
No problem at all. I've benefited a lot from XDA, and its my way of contributing.
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.
how do i root the htc one m8 I am familiar with rooting as i had a s4 rooted with gpe but i am confused with the htc one m8 plz help
xCellHD said:
how do i root the htc one m8 I am familiar with rooting as i had a s4 rooted with gpe but i am confused with the htc one m8 plz help
Click to expand...
Click to collapse
How to root (with links) is explained on my thread here: http://forum.xda-developers.com/showthread.php?t=2751432
Also, much of the "HTC specific" lingo is explained here: http://forum.xda-developers.com/showthread.php?p=52484527
I would suggest reading up (and making sure you understand all the terms and processes) for at least a couple hours before trying anything on the phone. I do this every time I buy a new device, even having own quite a few HTC phones. In fact, I usually start reading and researching before I have the phone in hand.
.
also is there a way were i can go back to stock when i need to thanks
xCellHD said:
also is there a way were i can go back to stock when i need to thanks
Click to expand...
Click to collapse
If your talking about ROM, then take a full backup of your ROM before flashing custom ROM using titanium/nandroid etc.
Or if your talking about root,
Just unroot using unroot apps from play store or the respected app you get after rooting.
xCellHD said:
also is there a way were i can go back to stock when i need to thanks
Click to expand...
Click to collapse
As the above reply stated, it depends on what you are talking about.
If you just want the stock ROM, recovery, etc. one option is to relock the bootloader and just run the RUU. It will return you to stock software. The only thing not "stock" will be the bootloader will say RELOCKED instead of LOCKED. You need s-off to make it say LOCKED again (after unlocking it).
?
so this is what i want to do i want to unlock bootloader then root which i know how to do but i was woundering would i be able to install this rom http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367
would i be able to install that rom soon as i am done unlocking the bootloader and rooting or would i have extra stuff sorry for the dumb questions
xCellHD said:
so this is what i want to do i want to unlock bootloader then root which i know how to do but i was woundering would i be able to install this rom http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367
would i be able to install that rom soon as i am done unlocking the bootloader and rooting or would i have extra stuff sorry for the dumb questions
Click to expand...
Click to collapse
What are your current hboot and radio numbers?
redpoint73 said:
What are your current hboot and radio numbers?
Click to expand...
Click to collapse
my hboot is 3.19 and my radio is [email protected]
xCellHD said:
my hboot is 3.19 and my radio is [email protected]
Click to expand...
Click to collapse
You should be good to go, then. Just unlock the bootloader, install custom recovery and flash the Skydragon ROM you linked.
would i need to be s-off and would i be able to go back stock and relock the bootloader with s-on again sorry for the manny questions i am new to this phone
xCellHD said:
would i need to be s-off and would i be able to go back stock and relock the bootloader with s-on again sorry for the manny questions i am new to this phone
Click to expand...
Click to collapse
You can return to stock with a RELOCKED bootloader with s-on.
You do need s-off if you want to make the bootloader say LOCKED as it was from the factory. But the only reason to ever do this is for warranty purposes. And if you bought the phone from AT&T, you should note that your warranty is through AT&T, not HTC. And AT&T doesn't give a crap if the bootloader is unlocked, or whatever (folks have even successfully sent in phones for warranty with custom ROMs on them).
If you are seeing warranty service through HTC (you didn't purchase from AT&T) that is another story. But that is the only reason I'd bother going back to LOCKED.
In normal usage, I recommend leaving the bootloader UNLOCKED as it give you more flexibility to flash ROMs whenever you want, etc. The only reason IMO to relock the bootloader in normal usage is to run the RUU.
S-off is nice have if you want to flash radios, modified hboots, and some other things (you also don't need to relock to RUU with s-off). It certainly doesn't hurt, and some folks like to make the phone as customizable as possible right away. In fact, I did s-off to the phone the second day I had it (although s-off was free back then). But for you, its not strictly "needed" at this time unless you want to do the things mentioned.
so heres the thing again sorry for the manny questions i am just making sure if i do this everything will work so heres the thing the rom i linked if i were to flash it will my at&t sevice work since it would be a different baseband
can you link me the latest twrp recovery for the at&t htc m8 so i can flash once i unlock the boatloader
xCellHD said:
can you link me the latest twrp recovery for the at&t htc m8 so i can flash once i unlock the boatloader
Click to expand...
Click to collapse
https://twrp.me/devices/htconem8gsm.html
the latest twrp 2.8.6.0 should work with my at&t m8 ?
xCellHD said:
so heres the thing again sorry for the manny questions i am just making sure if i do this everything will work so heres the thing the rom i linked if i were to flash it will my at&t sevice work since it would be a different baseband
Click to expand...
Click to collapse
The baseband isn't determined by the ROM, its determined by flashing a different baseband/radio (which requires s-off).
There are some folks that have had issues on AT&T's LTE network using some custom ROMs. Namely, not receiving or sending voice calls while on LTE. But this seems somewhat random, and not the ROMs fault per se; but probably changes that AT&T is making to their network. The most you can do is flash the Skydragon ROM, and if you have problems, try another ROM or revert to stock.
Make a backup of your stock ROM with TWRP before you flash anything, to be sure you have something to revert to if you have problems. This is good general advice before you flash any custom ROMs, root mods, etc.
I'm using the ROM your linked (Skydragon Sense 7) on AT&T, and it works fine for me.