yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] pootown:
I bought my N5 thu amazon and a soon to be returned Moto X thru Motorola. I am sending the Moto X back and want to try the N6. Any reason not to get it thru T-mobile?

Wifi calling, tethering, anything I will be left out of?

The main plus for me is from my recent issue with the Moto X. I had no roaming on the Moto X in Canada. T-Mobile tried to help me out but took them 3 days to verify nothing was wrong. Found out I needed to create a new APN. After doing so and confirming it was correct with Moto cust. support it still did not work. Had I not been within my 14 days I wouldn't be able to return, if same happens thru T-Mobile they would replace.
[Nexus 6 Q&A, Help & Troubleshooting] chrisram88:
Wifi calling is said to be here hopefully before Q1 ends. Thats a month or so left. I got my 32 variant in store so im not sure how tmobile is dealing with the N6 shimpments. In short, i dont see why you would have a problem getting it thru Tmo.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
i bought mine over the phone, and got it shipped next day, back in november. im paying $27 a month for it, and am very happy with the n6 and tmobile :)
[Nexus 6 Q&A, Help & Troubleshooting] pootown:
So the only benefit Amazon has is a 30 day return vs a 14 day.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
i guess?
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
APN's won't help make roaming work, unless you are only having problems obtaining data service. The APN settings are ONLY responsible for the DATA portion of the connection, and can't even be tried until after the phone is already connected to a network.

In Canada, a tmobile sim will roam on either Wind (same AWS spectrum as tmobile US) or Rogers (different frequencies from tmobile, but same as ATT). It is *unlikely* that you would be able to obtain any LTE service in Canada, Wind doesn't have any, and Rogers has everything completely screwed up. As a Wind customer, I am *supposed* to be able to roam on Rogers LTE when outside of my area, but it just does not work.

So to obtain service in Canada, you would need to make sure that your phone isn't forced/restricted to LTE. To obtain data service, you would have to make sure that you have selected TMO's UMTS APN, not their LTE APN.
[Nexus 6 Q&A, Help & Troubleshooting] pootown:
Yeah, I was on both Rogers and Telus but needed to roam on the 2G network. I was in country just a couple days and didn't need the LTE, plus it they don't have it way up north where I was at. I am with T-mo specifically because of the free 2G roaming they offer. The new APN was supposed to resolve the problem specifically for 2G roaming. I think now I'll exchange the MotoX and ask for an extended trial since I will leave the country again in a couple weeks. If that doesn't work I'll give the Moto a try. It's the same as the Moto but if I buy N6 thru T-Mobile they will be responsible for assuring the 2G roaming features work.
[HTC Desire 510] Alex2x:
Ok I recently boight this phone and found that every time I use the GPS with an Sat Nav. app it loses its GPS straight away, anybody else notice this, and is there a fix for this.
[AT&T HTC One (M8)] dimakiller3:
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
[AT&T HTC One (M8)] Tigerstown:
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.
[AT&T HTC One (M8)] dimakiller3:
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.
[AT&T HTC One (M8)] Tigerstown:
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
[AT&T HTC One (M8)] redpoint73:
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.
[AT&T HTC One (M8)] Wombat Pete:
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!
[AT&T HTC One (M8)] redpoint73:
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.

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.

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.
[AT&T HTC One (M8)] Wombat Pete:
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.
[AT&T HTC One (M8)] redpoint73:
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.
[AT&T HTC One (M8)] Wombat Pete:
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?
[AT&T HTC One (M8)] redpoint73:
The "right" firmware is a tricky question. I'd start with the 4.16.1540 firmware posted along with the ROM here: http://xdaforums.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.
[AT&T HTC One (M8)] Wombat Pete:
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?
[AT&T HTC One (M8)] redpoint73:
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.
[AT&T HTC One (M8)] Wombat Pete:
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?
[AT&T HTC One (M8)] redpoint73:
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://xdaforums.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://xdaforums.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.
[AT&T HTC One (M8)] Wombat Pete:
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.
[AT&T HTC One (M8)] redpoint73:
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.
[AT&T HTC One (M8)] Wombat Pete:
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_UL_K444_SENSE60_ATT_MR_Cingular_US_3.42.502.1_Radio_4.0.U606061@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.
[AT&T HTC One (M8)] Wombat Pete:
Also, after the RUU I'd be S-Off, but locked? Unlock again? Not that that should be difficult...
[AT&T HTC One (M8)] redpoint73:
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.

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.

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.
[AT&T HTC One (M8)] Wombat Pete:
I think this should set the CID: fastboot OEM writecid T-MOB010

From this thread: http://xdaforums.com/showthread.php?t=1444836

Does that look right?

The process for setting MID seems clear there.
[AT&T HTC One (M8)] redpoint73:
Mostly right. I think it should be:

fastboot oem writecid T-MOB010

Lowercase "oem" based on later posts in that thread (and my own experience also).

Alternately, you can also do:

fastboot oem writecid 11111111

This is known as "SuperCID" which will essentially pass any CID check, regardless of the required CID. No difference in this specific instance versus the correct T-Mobile US CID (for running the corresponding RUU). But might be handy if you want to flash other things later that require a different CID (won't need to change CID again). However, if a MID check is also involved, you will still need the correct MID.
[AT&T HTC One (M8)] Wombat Pete:
OK! Here are some "fastboot getvar" results - I think I've set the MID and CID correctly.

Am I ready to try the RUU?

C:\miniadb_v1031>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 4.0.U606061@41216A

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: MB505WM14975

(bootloader) imei: 35***

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B13000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 56f9ae32

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

C:\miniadb_v1031>fastboot getvar mid

mid: 0P6B13000

finished. total time: 0.004s

C:\miniadb_v1031>fastboot getvar cid

cid: CWS__001

finished. total time: 0.004s

NB: In the following list (from the "Just a quick guide on how to change GSM M8s to other variants" thread), I've done only steps One and Two.

STEPS TO FOLLOW BELOW

- Step 1 - changing MID

- Step 2 - changing CID

- Step 3 - restoring relevant nand backup

- Step 4 - firmware flashing

- Step 5 - OTA downloading/updating

After doing them, I did install Nandroid and made a back-up image (but from the app, not from TWRP, I imagine that's ok or it wouldn't have worked).
[AT&T HTC One (M8)] redpoint73:
You have the correct MID now, but the CID is clearly wrong.

The getvar outputs indicate your current CID is CMW_001, which is the AT&T CID. You want CID to be T-MOB010.

I'm not familiar with what app that is. I personally recommend installing TWRP manually, not using some app. The apps don't do much that you can't do with TWRP itself, or with fastboot, and often just "middlemen" that cause more problems than they solve.

If you boot TWRP, and you can browse to the recent nandroid backup in the "Restore" menu option, you are probably ok. But I just don't see a reason to do it from an app.
[AT&T HTC One (M8)] Wombat Pete:
FYI: The backup app is the nandroid app I downloaded. TWRP does find the backup. From now on I'll use TWRP for it, though.

More importantly:

I went for the SuperCID version. When I boot into backup, I see:

MB_US_CA PVT SHIP S-OFF

CID-11111111

etc.

But if getvar outputs CMW_001, does that mean that I don't have the 11111111? What should getvar output instead of CMW_001 if I *do* have superCID?

---------- Post added at 06:37 PM ---------- Previous post was at 06:28 PM ----------

And I opened a command window again and now I get:

C:\Users\->fastboot getvar mid

mid: 0P6B13000

finished. total time: 0.004s

C:\Users\->fastboot getvar cid

cid: 11111111

finished. total time: 0.003s

C:\Users\->​
[AT&T HTC One (M8)] Wombat Pete:
Given the last thing, above, then, I'll go ahead with the RUU, then?
[AT&T HTC One (M8)] redpoint73:
Sorry, I didn't realize you were waiting for validation!

Yes, you have the proper model ID, and SuperCID. So you should be able to run RUU.

Backup any personal data that you want to keep, before RUU (as the phone will be wiped).
[AT&T HTC One (M8)] Wombat Pete:
I *was* waiting for validation, yes))) - I already have the "badge of honor" of having bricked the thing once, seeing no upside in risking a second time)

Anyway - yes, it's done! Amazing that the phone is now converted fully to T-Mobile. There were a few issues, but I figured them out. Very, very cool! Let me post a getvar all, just to make sure it all looks right:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.23.213311491.05G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.20.531.4

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: MB5...

(bootloader) imei: 35...

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B13000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 06f11f5b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.023s

In the software:

Android 5.0.1

Sense version: 6.0

Software number: 4.20.531.4

HTC SDK API level: unknown

Build number: 4.20.531.4 CL464190 release-keys

So now just two steps left, right?

1.) Flash TWRP recovery again, and then

2.) Flash the latest viper ROM - which, I think, is THIS one: VZW 4.17.605.5, found on THIS page: http://venomroms.com/htc-one-m8/

and that's it?
[AT&T HTC One (M8)] Wombat Pete:
Success!

For anyone tracking this - had to reinstall SuperSU, busybox, nandro!!!id back-up, but then it worked perfectly.

Viper is on the machine, looks smooth, setting it up now.

Thanks to everyone, and enormous appreciate to redpoint73!!!

---------- Post added at 04:23 AM ---------- Previous post was at 04:19 AM ----------

...and then, partway through the installation, when creating a venom account, the phone just went dead and now seems to react to nothing.
[AT&T HTC One (M8)] redpoint73:
Ohhh, I hope you didn't flash that. "VZN" is the Verizon version. And being a CDMA variant, actually has different hardware from all the other "GSM" variants of the M8 (yours is a GSM).

This is not spelled out very clearly on the Viper download page.

---------- Post added at 09:33 AM ---------- Previous post was at 09:31 AM ----------

Any LED lights (and if so, what color)? Try connecting to charger for a while. Try holding down various button combos for maybe 30 seconds or more: power; or power + vol up; power + vol down, and see if any change.

Hopefully, you did not brick the phone by flashing the CDMA ROM.