I'm sorry for the noob question, but I have an ATT One M8 and I would like to convert to the developer edition to get rid of all of this ATT nonsense.
I had a couple of questions:
1. If I do, the LTE radios are different for the ATT version and the developer version, if I use the ruu from a developer edition, will I limit the LTE frequencies I can use?
2. If I convert to developer using this method http://forum.xda-developers.com/showthread.php?t=2721435, will I be able to get developer updates and pretend that I'm fully unlocked and stock?
Anyways, sorry if these are covered, but I have had a difficult time finding clear answers regarding the radio
k3y0n4 said:
I'm sorry for the noob question, but I have an ATT One M8 and I would like to convert to the developer edition to get rid of all of this ATT nonsense.
I had a couple of questions:
1. If I do, the LTE radios are different for the ATT version and the developer version, if I use the ruu from a developer edition, will I limit the LTE frequencies I can use?
2. If I convert to developer using this method http://forum.xda-developers.com/showthread.php?t=2721435, will I be able to get developer updates and pretend that I'm fully unlocked and stock?
Anyways, sorry if these are covered, but I have had a difficult time finding clear answers regarding the radio
Click to expand...
Click to collapse
Well first you need to convert your phone to the GPE edition before you do anything else, according to that link. Plus is your bootloader unlocked and are you Supercid?
Tower1972 said:
Well first you need to convert your phone to the GPE edition before you do anything else, according to that link. Plus is your bootloader unlocked and are you Supercid?
Click to expand...
Click to collapse
Ok, fair enough, I suppose maybe this is a better guide: http://forums.androidcentral.com/ht...238-convert-att-device-developer-edition.html
I think the point is, if I s-off and install the developer RUU, then I assume that will use developer radios right? Can I flash the ATT radios after the developer edition RUU?
Maybe a tangential question is how the cell radio frequencies work. ATT uses, 700, 1700 AWS, 1900 PCS, 2300 WCS LTE bands. I would assume, different towers will broadcast different bands. So if you had the developer edition which just supports the 700MHz band, then if you came across a tower that broadcast another, you wouldn't be able to connect. Is that basic premise correct? Is it possible all towers broadcast all bands?
k3y0n4 said:
Ok, fair enough, I suppose maybe this is a better guide: http://forums.androidcentral.com/ht...238-convert-att-device-developer-edition.html
I think the point is, if I s-off and install the developer RUU, then I assume that will use developer radios right? Can I flash the ATT radios after the developer edition RUU?
Maybe a tangential question is how the cell radio frequencies work. ATT uses, 700, 1700 AWS, 1900 PCS, 2300 WCS LTE bands. I would assume, different towers will broadcast different bands. So if you had the developer edition which just supports the 700MHz band, then if you came across a tower that broadcast another, you wouldn't be able to connect. Is that basic premise correct? Is it possible all towers broadcast all bands?
Click to expand...
Click to collapse
Hot damn thats a loaded question and alittle out of my realm lol. Hopefully someone will answer!!!!
k3y0n4 said:
I think the point is, if I s-off and install the developer RUU, then I assume that will use developer radios right? Can I flash the ATT radios after the developer edition RUU?
Maybe a tangential question is how the cell radio frequencies work. ATT uses, 700, 1700 AWS, 1900 PCS, 2300 WCS LTE bands. I would assume, different towers will broadcast different bands. So if you had the developer edition which just supports the 700MHz band, then if you came across a tower that broadcast another, you wouldn't be able to connect. Is that basic premise correct? Is it possible all towers broadcast all bands?
Click to expand...
Click to collapse
As long as you are s-off, you can flash whatever radio you want. You also need SuperCID according to the radio thread (since the AT&T CID does not match your device CID): http://forum.xda-developers.com/showthread.php?t=2736921
I don't know where you are getting that the Dev Edition is only compatible with 700 MHz. According to HTC specs, it supports LTE Bands 17/4/2/5, which corresponds to Bands 4 and 17 (700 and 1700 MHz)used by AT&T.
http://shopamerica.htc.com/cell-phones/productdetail.htm?prId=42973
My understanding is that the US unlocked and DE versions are both intended for use on AT&T. Also my understanding is the hardware is identical to the AT&T variant. I don't see a reason the band compatibility in the radio firmware would be any different.
Moved to Q&A forum.
redpoint73 said:
As long as you are s-off, you can flash whatever radio you want. You also need SuperCID according to the radio thread (since the AT&T CID does not match your device CID): http://forum.xda-developers.com/showthread.php?t=2736921
I don't know where you are getting that the Dev Edition is only compatible with 700 MHz. According to HTC specs, it supports LTE Bands 17/4/2/5, which corresponds to Bands 4 and 17 (700 and 1700 MHz)used by AT&T.
http://shopamerica.htc.com/cell-phones/productdetail.htm?prId=42973
My understanding is that the US unlocked and DE versions are both intended for use on AT&T. Also my understanding is the hardware is identical to the AT&T variant. I don't see a reason the band compatibility in the radio firmware would be any different.
Click to expand...
Click to collapse
Oh, thanks. For some reason, when I looked previously I couldn't find the frequency specs on the HTC website before. I likely skipped the 'summary' page and went straight to the specs, where it oddly isn't listed. I was assuming the developer edition was the same as the GPE edition, which lists only 700MHz.
So then as a follow up, I'm sort of new to this, but I would like to convert my unit to a developer edition, would the best method be using a developer RUU? And if I do, that would likely flash the developer radio, which is likely the same as the ATT, but would I need to flash the ATT radio? Does an RUU contain radio information? How would OTA updates work? If I kept my CID as a superCID, then can I get OTA updates from HTC? Would it reflash the radio? Does it matter?
Thanks again for the previous clarification, and sorry if this is clearly stated elsewhere. I seemed to be finding conflicting advice and was completely unable to find any radio information.
k3y0n4 said:
Ok, fair enough, I suppose maybe this is a better guide: http://forums.androidcentral.com/ht...238-convert-att-device-developer-edition.html
Click to expand...
Click to collapse
That guide is for the M7. AFAIK, there is currently no RUU for the Dev Edition for the M8. So your questions regarding the RUU don't really apply. But in general yes, they include a radio. RUU is a complete image, it includes all software (ROM, radio, hboot, and more).
If the goal is simply to get rid of the AT&T bloat, gimped features, etc., then my advice would be that it would be to unlock the bootloader, install custom recovery, and flash a custom ROM.
redpoint73 said:
That guide is for the M7. AFAIK, there is currently no RUU for the Dev Edition for the M8. So your questions regarding the RUU don't really apply. But in general yes, they include a radio. RUU is a complete image, it includes all software (ROM, radio, hboot, and more).
Click to expand...
Click to collapse
Ok, I'm an idiot. Here is the guide I am going to follow. http://forum.xda-developers.com/showthread.php?t=2758812
I'll take most of my further questions over to it's thread. Thank you for bearing with the nonsense.
If the goal is simply to get rid of the AT&T bloat, gimped features, etc., then my advice would be that it would be to unlock the bootloader, install custom recovery, and flash a custom ROM.
Click to expand...
Click to collapse
My goal is primarily to get rid of ATT bloat and have easy access to up to date 'stable' feature releases from HTC. I'm coming from a S3 with CM11 which I loved from a software standpoint and may end up with before too long, but for the time being I would like to stick with stock. The stock sense is nice enough to use and I appreciate the added stability which was a frustration with the custom ROMs that I've tried. Bluetooth was always a sore spot.
Again, thanks for the help.
k3y0n4 said:
My goal is primarily to get rid of ATT bloat and have easy access to up to date 'stable' feature releases from HTC.
Click to expand...
Click to collapse
In any case you will be unlocking the bootloader (modding the phone) in order to remove AT&T bloat. And IMO official OTA updates have no place on modded phones. Updated features come to XDA in the form of custom ROMs, rooted stock ROMs, etc. soon after their "official" release. So to me, that is not an issue. You can try to jump through hoops turning it into a DE phone, and hope you get OTAs (not sure if you will or not). Or you can have complete freedom to flash and mod whatever you want.
To me, its a pretty easy choice.
Related
If anyone can get my Pro to work on T-Mobiles 3G network. I heard they are going to carry it and that hardware is the same its just the software....
Shoot me if its not passable but im trying :/
Wow, that's practically a 3rd of the devices price :O. I'm sure people would help you without offering the money. I would wait for the cooked ROMs as the might just fix the issue.
O yea
EDIT: You have to show me how to instal it and give me everything I need to instal it
thanks
GlobalM3 said:
O yea
EDIT: You have to show me how to instal it and give me everything I need to instal it
thanks
Click to expand...
Click to collapse
I assume you're kidding right? As the Raphael forum is brand spankin' new I'll throw you a bone and guide you to ROM upgrading guide for the Kaiser from the Kaiser's Wiki. Upgrading the Raphael's ROM will be similar. BTW, seems nobody knows for sure if the UK version of the Raph has the necessary hardware for UMTS with AT&T or T-mobile.
bersca said:
I assume you're kidding right? As the Raphael forum is brand spankin' new I'll throw you a bone and guide you to ROM upgrading guide for the Kaiser from the Kaiser's Wiki. Upgrading the Raphael's ROM will be similar. BTW, seems nobody knows for sure if the UK version of the Raph has the necessary hardware for UMTS with AT&T or T-mobile.
Click to expand...
Click to collapse
Thanks for the help.
Im just lazy to look at all the numbers and roms and threads on if and what works. I just want the radio for 3g T-Mobile to work. It be nice to have some other cool features as well but I really need 3G
thanks again
Yea, as i stated earlier, you have to try out the different ROMs and have the exact settings to get it to work.
kareem9nba said:
Yea, as i stated earlier, you have to try out the different ROMs and have the exact settings to get it to work.
Click to expand...
Click to collapse
I heard that it can brick your phone.....
thanks again
If you follow the instructions, you should be good to go. Just read and once you feel comfortable, do it.
See theproblem is its all over whelming to me.
I don't know if its 1700 or 2100 the phone has to have to work on tmo. And I also seen that the diamond shows 1700/1900 and 2100 umts but they are not active when someone selects it....
Kind of understand my position?
Tnx again for your reply
GlobalM3 - why don't you call TMO support phone number and ask which band to choose for 3G? Probably you also need to try to activate hsupa/hsdpa.
p.s.: anyway you should flash your phone to newest rom and radio available, possibly the fix is already in it...
GlobalM3 said:
See theproblem is its all over whelming to me.
I don't know if its 1700 or 2100 the phone has to have to work on tmo. And I also seen that the diamond shows 1700/1900 and 2100 umts but they are not active when someone selects it....
Kind of understand my position?
Tnx again for your reply
Click to expand...
Click to collapse
t-mobile uses umts 2100
it not being active can have many origins
u need a abbo for it , a login, server ip etc
best to check with the customerservice or on the t-mobile website
you can register your account there and the phone
once on the customerpage of your account you can choose to have the settings send by sms
this will auto-configure the proper settings
Guys I am referring to T-Mobile USA 3G not Euro T-Mobile.
THanks for the shot at help
GlobalM3 said:
Guys I am referring to T-Mobile USA 3G not Euro T-Mobile.
THanks for the shot at help
Click to expand...
Click to collapse
T-mobile usa uses 1700 and 2100.
GlobalM3 said:
I heard that it can brick your phone.....
thanks again
Click to expand...
Click to collapse
Well that's propably why you'll be seeing Rom's being singed to flash to Oli's SPL just like in th Diamond forum's
The main setup is safety.
Bricked devices being sent back to the Provider or HTC is in no one's Best interest (Excuse me if i used the incorrect phrasing here, but you know what i'm trying to say)
Heck i think if you donated 75 to XDA and 75 to anyone willing to help you flash and get the right tools there'd be plenty of users willing to help you out.
I think the most posters above are only trying to save you some money.
You'll need to flash a radio ROM from the AT&T ROMs. In fact, if you can, flashing the whole AT&T ROM may help.
I know AT&T and T-Mo USA have different bands, but the AT&T ROM is the only US ROM/Radio ROM, and so is the most likely to work (unless the devices ship with a radio ROM that covers all bands).
ROM flashing may come with a risk of bricking. Nothing is risk free, but the official RUUs are likely to work best (if the device is not CID locked that is)
Then I will donate some of that money to XDA
I wonder if att has the right band... but why would it :./
Thanks
It may not have the right band, but it's the only radio ROM that'll work at all on US 3G networks.
l3v5y said:
It may not have the right band, but it's the only radio ROM that'll work at all on US 3G networks.
Click to expand...
Click to collapse
So you are saying that the radio supports it but no the software?
GlobalM3 said:
So you are saying that the radio supports it but no the software?
Click to expand...
Click to collapse
I don't know. But without the software, there's no change the hardware will work fully.
As stated, T-mo US uses UMTS 1700 and 2100. The problem is T-mo is separating HSPA between the two bands: 1700 for the uplink (HSUPA) and 2100 for the downlink (HSDPA). I may be wrong, but I don't think any other carrier does this (AT&T 3G uses 850/1900, but both links are available in both bands).
It is unclear at this time whether any of the radio chipsets in current Europe/Asia 3G handsets can support this split implementation, henceforth referred to as AWS (even though AWS is a bit of a misnomer, since AWS refers only to the US 1700/2100 frequencies and not necessarily the split-HSPA configuration T-mo US is using).
We will probably have to wait until T-mo/HTC puts out an AWS-capable device and dissect it to see which radio chipset it uses. If the Pro has the same chipset, there might be a good chance of flashing the radio to support T-mo 3G.
Further Reading:
http://www.phonescoop.com/articles/aws/index.php?p=i
http://www.breakitdownblog.com/3g-iphone-may-not-work-on-t-mobile-3g-network/
As posted here: http://forum.xda-developers.com/showthread.php?t=2188467
Do you guys think the devs will be able to enable AWS HSPA bands on the ATT / Rogers / Bell / TELUS devices?
Many of us in Canada use Roam Mobility (T-Mo MVNO) when we roam in the USA. Having access to AWS + 1900 HSPA would be great so that we're camping on 2G less often.
It is in there, the problem is unlocking it. ATT may have required an efuse based lock that cannot be changed once set at the factory.
Sent from my HTC One using xda app-developers app
Interesting thing is htc has listed data speeds for canadian version via hsdpa is up to 42mb and it's the same for t-mobile USA, only At&t has different one. This could mean, that Canadian version might be similar to T-mobile version. But, this could just mean at&t's network doesn't support speeds of 42mb on hsdpa. I'm leaning toward network limitations.. But, I'm hoping I'm wrong haha
htc fan89 said:
Interesting thing is htc has listed data speeds for canadian version via hsdpa is up to 42mb and it's the same for t-mobile USA, only At&t has different one. This could mean, that Canadian version might be similar to T-mobile version. But, this could just mean at&t's network doesn't support speeds of 42mb on hsdpa. I'm leaning toward network limitations.. But, I'm hoping I'm wrong haha
Click to expand...
Click to collapse
ATT does not support 42mbit (network limitation).
Hunt3r.j2 said:
It is in there, the problem is unlocking it. ATT may have required an efuse based lock that cannot be changed once set at the factory.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It was so easy on the S3 / Note 2 (using Qualcomm software). I'm using a Bell version of the HTC One.
WorldIRC said:
It was so easy on the S3 / Note 2 (using Qualcomm software). I'm using a Bell version of the HTC One.
Click to expand...
Click to collapse
Once I get mine I will take a look on a telus model with the Qualcomm baseband software, like I did on my note 2.
Dazog said:
Once I get mine I will take a look on a telus model with the Qualcomm baseband software, like I did on my note 2.
Click to expand...
Click to collapse
Thanks! I look forward to your findings.
WorldIRC said:
It was so easy on the S3 / Note 2 (using Qualcomm software). I'm using a Bell version of the HTC One.
Click to expand...
Click to collapse
That's great, but Samsung's lock was superficial, incredibly easy to bypass. Maybe flashing TMOUS radios will do it, but there's no guarantees and it requires S-OFF.
Hunt3r.j2 said:
That's great, but Samsung's lock was superficial, incredibly easy to bypass. Maybe flashing TMOUS radios will do it, but there's no guarantees and it requires S-OFF.
Click to expand...
Click to collapse
We know, but the hack or mod will allow us to keep the latest radio's released modded for all frequencies.
Instead of cross flashing all the time.
Dazog said:
We know, but the hack or mod will allow us to keep the latest radio's released modded for all frequencies.
Instead of cross flashing all the time.
Click to expand...
Click to collapse
Honestly I don't think this is something worth investigating until S-OFF is achieved. Then we have to figure out whether or not the lock on AWS WCDMA can be removed with software means.
The iPhone 5 had the same exact problem. For T-Mobile they released a phone with the same model number as the ATT version but with AWS WCDMA unlocked. Apple was unable to do anything for the ATT users because the lock went so low level that no software could change it, so they had to just change the software from the factory instead.
The same thing may be happening here.
Has anyone figured this out yet using the QPST method in the Qualcomm software like we do with Samsung?
WorldIRC said:
Has anyone figured this out yet using the QPST method in the Qualcomm software like we do with Samsung?
Click to expand...
Click to collapse
Is there any update on this?
I can understand them locking the AT&T version down at hardware, but no the International version.
Anyone know if I can flash the International to open up 1700 AWS?
Does anyone know if the AT&T HTC One has the 2600 Mhz 4G/LTE band?
The International model does, but not sure if after converting the AT&T one changing the MID, CID and RUU will unlock the band.
I have the unlocked version sitting on my desk right now.
The only difference seems to be that the radios are not the same?
But I've been reading that the radio might be flashable so it can accept Tmobile frequencies.
One question though, can ROMs from the unlocked version be used on the Tmobile version? Thanks
teatime0315 said:
I have the unlocked version sitting on my desk right now.
The only difference seems to be that the radios are not the same?
But I've been reading that the radio might be flashable so it can accept Tmobile frequencies.
One question though, can ROMs from the unlocked version be used on the Tmobile version? Thanks
Click to expand...
Click to collapse
From what I have read, the T-Mobile H1 can flash any ROM.
The radio flashing is an open question. So far attempts to get the AWS working on the dev / unlocked models have not worked. HTC says they have different radio hardware, but at this point it is anyone's guess if we will ever get AWS working on dev.
If you use the unlocked / dev on TMO, you will get 21 Mb on the 1900 refarmed band, and eventually LTE if you live in an area that has it. Right now there are maybe three areas with LTE.
If you got the 32 Gb unlocked, in my opinion it has no advantage over the T-Mobile model. The Dev edition has 64 gb of storage.
stevedebi said:
From what I have read, the T-Mobile H1 can flash any ROM.
The radio flashing is an open question. So far attempts to get the AWS working on the dev / unlocked models have not worked. HTC says they have different radio hardware, but at this point it is anyone's guess if we will ever get AWS working on dev.
If you use the unlocked / dev on TMO, you will get 21 Mb on the 1900 refarmed band, and eventually LTE if you live in an area that has it. Right now there are maybe three areas with LTE.
If you got the 32 Gb unlocked, in my opinion it has no advantage over the T-Mobile model. The Dev edition has 64 gb of storage.
Click to expand...
Click to collapse
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
zaos said:
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
Click to expand...
Click to collapse
I don't think anyone has tried that yet. I suspect AWS wouldn't work without some modification because the ROM would not support AWS. But I don't think it would hurt anything either.
zaos said:
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
Click to expand...
Click to collapse
Yes, flashing ROMs doesn't affect frequency compatibility. All GSM One variants have the same hardware and ROMs/kernels are cross-compatible (international HSPA-only, and EMEA/AT&T/T-moblie LTE). ROMs don't include radio software, and so far at least, radio software hasn't affected available frequency bands.
teiglin said:
Yes, flashing ROMs doesn't affect frequency compatibility. All GSM One variants have the same hardware and ROMs/kernels are cross-compatible (international HSPA-only, and EMEA/AT&T/T-moblie LTE). ROMs don't include radio software, and so far at least, radio software hasn't affected available frequency bands.
Click to expand...
Click to collapse
If flashing ROMs (not radios) to/from intl, US, EMEA models don't affect supported bands, I don't see why it would affect tmobile -> unlocked. Advantages would be no tmobile bloat, no hacks to please the tmobile overloads, etc.
zaos said:
If flashing ROMs (not radios) to/from intl, US, EMEA models don't affect supported bands, I don't see why it would affect tmobile -> unlocked. Advantages would be no tmobile bloat, no hacks to please the tmobile overloads, etc.
Click to expand...
Click to collapse
It sounds like you're disagreeing with me or something, but yes, flashing an international ROM on tmo One is great because it gets rid of bloat, can edit APNs to enable tethering, and always based on latest firmware rather than waiting for tmo to push an update. Only downside I know of is no wifi calling. I'm running TrickDroid on mine and it works great.
teiglin said:
It sounds like you're disagreeing with me or something, but yes, flashing an international ROM on tmo One is great because it gets rid of bloat, can edit APNs to enable tethering, and always based on latest firmware rather than waiting for tmo to push an update. Only downside I know of is no wifi calling. I'm running TrickDroid on mine and it works great.
Click to expand...
Click to collapse
Sorry, that was more directed at stevedebi's comment. Wifi calling can be replaced with SIP calling so that should be fine.
Warranty problems?
One potential issue with getting the T-Mobile version could have to do with the warranty. U.S. carriers seem squeamish about people modding their phones and threaten to void the warranty for unlocking bootloaders, rooting, etc. That said, I don't have specific info at hand that HTC unlocked phones are much more lenient but seems worth looking into.
zaos said:
Sorry, that was more directed at stevedebi's comment. Wifi calling can be replaced with SIP calling so that should be fine.
Click to expand...
Click to collapse
Well, most of the new T-Mobile plans come with unlimited hotspot and WiFi calling. I'm not planning to unlock mine. My One is performing fine on the stock ROM, and TMO will update the software (eventually).
As noted above, I'm not sure that T-Mobile looks kindly on having TAMPERED show up on a phone. They might well deny a warranty claim.
For me get the T-Mobile HTC one I had the 64gb edition got tired of the stupid refarm 1900mhz frequency my icon was switching from H to 3G. Now with my original T-Mobile HTC one I get steady 4g icon and good speeds
Sent from my HTC One using xda app-developers app
stevedebi said:
Well, most of the new T-Mobile plans come with unlimited hotspot and WiFi calling. I'm not planning to unlock mine. My One is performing fine on the stock ROM, and TMO will update the software (eventually).
As noted above, I'm not sure that T-Mobile looks kindly on having TAMPERED show up on a phone. They might well deny a warranty claim.
Click to expand...
Click to collapse
Same here mine is stock Rom with no root or unlocked bootloader only have about 5 T-Mobile apps that don't worry me.
Sent from my HTC One using xda app-developers app
ahernandez4110 said:
For me get the T-Mobile HTC one I had the 64gb edition got tired of the stupid refarm 1900mhz frequency my icon was switching from H to 3G. Now with my original T-Mobile HTC one I get steady 4g icon and good speeds
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Switching from H to 3G is just what the radio does; it's how the interface is supposed to work. The T-Mobile version works exactly the same way--and you can see this if you flash an international ROM on your tmo One--but tmo assumes Americans are idiots who a. don't know what HSPA+ is, and b. get confused if the radio idles at "3G" when they expect to have "4G" coverage. So stock tmo ROM just shows 4G all the time, but it is just themed connection icons really. Seems like they're right to do this, which is a bit sad.
Of course, that doesn't mean that you would be getting the same speeds with the dev edition, since even in refarmed areas, you could well get better UMTS coverage over AWS than PCS.
teiglin said:
Switching from H to 3G is just what the radio does; it's how the interface is supposed to work. The T-Mobile version works exactly the same way--and you can see this if you flash an international ROM on your tmo One--but tmo assumes Americans are idiots who a. don't know what HSPA+ is, and b. get confused if the radio idles at "3G" when they expect to have "4G" coverage. So stock tmo ROM just shows 4G all the time, but it is just themed connection icons really. Seems like they're right to do this, which is a bit sad.
Of course, that doesn't mean that you would be getting the same speeds with the dev edition, since even in refarmed areas, you could well get better UMTS coverage over AWS than PCS.
Click to expand...
Click to collapse
Not to mention that in many cases you get EDGE on 1900 even in refarmed markets.
yeah I was thinking of getting the DE because its 64gb but then I realize that with wifi everywhere, I can just upload pictures or videos to you box account, then delete them to make room, and keep installing apps I want and delete those you dont.
After dealing with 16gb in a Gnexus, you learn how to manage to space
teiglin said:
Switching from H to 3G is just what the radio does; it's how the interface is supposed to work. The T-Mobile version works exactly the same way--and you can see this if you flash an international ROM on your tmo One--but tmo assumes Americans are idiots who a. don't know what HSPA+ is, and b. get confused if the radio idles at "3G" when they expect to have "4G" coverage. So stock tmo ROM just shows 4G all the time, but it is just themed connection icons really. Seems like they're right to do this, which is a bit sad.
Of course, that doesn't mean that you would be getting the same speeds with the dev edition, since even in refarmed areas, you could well get better UMTS coverage over AWS than PCS.
Click to expand...
Click to collapse
You are right if you go to phone settings-about- network you could see UMTS and HSPS+ it swicthes between UMTS 3g and 4g HSPS+ and my 4g icon stays the same, this also happen to my old HTC one 64gb developer edition but it never showed the 4g icon like T-Mobile HTC one all it showed was 3g and H icons this happens in a 1900mhz refarm area. Look at T-Mobile HTC One as example thank god it has 1700mhz built-in that's why I got ridoff my developer Edition
Sent from my HTC One using xda app-developers app
zaos said:
The tmobile version flashed to the unlocked ROM should retain AWS on HSPA+, correct? That's the route I will probably be taking. The additional LTE bands are inconsequential for me - mainly south america and Philippines.
Click to expand...
Click to collapse
yes flashing the TMO version on an unlocked rom will allow you to retain the AWS bands tmobile uses for 3g/HSDPA/HSPAP(HSDPA+)
i bought the TMO HTC one and am now using ordroid 4.2.0 on se7en kernel and i have AWS signal. and not just refarmed signal also umts signal as well.
I need some assistance from the Pros on this one.
Problem: phone only connects to 4G HSPA, will not connect to 4G LTE no matter what I've tried. AT&T tier 3 technical support said by all means the phone should be connecting to 4G LTE. Unless the phone was falsely advertised as having support for 4G LTE.
This is the phone I bought for my wife: http://www.newegg.com/Product/Product.aspx?Item=9SIA2NR2977129
It advertises 4G LTE Support 700/900/1800/2100/2600 MHz
Also supports: GSM/GPRS/EDGE: 850/900/1800/1900 MHz and UMTS/HSPA: 850/900/1900/2100 MHz with HSPA+ up to 42 Mbps
The IMEI number shows in the IMEI database as supporting 4G LTE and all associated bands.
Phone Info:
HTC One M8 (International Version)
Model: M8_UL (the AT&T version is M8_UL_CA)
Stock MID: 0P6B11000 (I changed this to the AT&T MID of 0P6B12000 since I'm using it on AT&T network)
S-OFF
Unlocked
SuperCID: 11111111
HBOOT: 3.19.0.0000
Current Firmware: 4.16.401.10
Tried This Firmware: 4.16.1540.8
Current Radio: 1.25.214500021.06G
Tried This Radio: 1.24.21331147A1.09G
Running ARHD ROM 34.6 Lollipop 5.0.1
default.xml modified to SKU: 7 and Region 1 (for AT&T support)
What else can I try to enable 4G LTE? I already took the SIM out of my phone and put it in my wife's phone. Still her phone will not connect to LTE.
Are you checking the status in settings>about>network or going by the icons in the status bar? I'm using a "multi-carrier" ROM and the status bar icons show 4G for LTE and H for HSPA. I believe the ROMs built on ATT base will show 4GLTE and 4G, respectively.
Dial *#*#4636#*#* and Confirm Network Type
BYOBret said:
Are you checking the status in settings>about>network or going by the icons in the status bar? I'm using a "multi-carrier" ROM and the status bar icons show 4G for LTE and H for HSPA. I believe the ROMs built on ATT base will show 4GLTE and 4G, respectively.
Click to expand...
Click to collapse
You can't really rely on the icon, it's best to check the connected band by using this method:
Tap Phone
Dial *#*#4636#*#*
Tap Phone Information
You can change your radio frequency to USA or International
Select the Bands you want your phone to support
View Network Type: LTE, HSPA etc (it should always read LTE if you have an LTE plan and your near an LTE capable tower. My phone reads LTE always, my wife's reads HSPA)
Run Diagnostics etc.
TrickMasterPC said:
You can't really rely on the icon
Click to expand...
Click to collapse
Right. That was my point. Just making sure you weren't being duped by the status bar icons, as they are different for ATT and other carriers.
You might want to try running a full RUU for ATT to see if it will connect to LTE. That way you will be sure that all firmware, radio, system match for ATT.
BYOBret said:
Right. That was my point. Just making sure you weren't being duped by the status bar icons, as they are different for ATT and other carriers.
You might want to try running a full RUU for ATT to see if it will connect to LTE. That way you will be sure that all firmware, radio, system match for ATT.
Click to expand...
Click to collapse
You're on the right track! That was the first thing I did, I installed this ROM 4.28.502.1 from here: http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Latest official AT&T, still no LTE, HSPA only. Sad Face.
TrickMasterPC said:
You're on the right track! That was the first thing I did, I installed this ROM 4.28.502.1 from here: http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
Latest official AT&T, still no LTE, HSPA only. Sad Face.
Click to expand...
Click to collapse
Ah bummer. What phone are you using? Does her sim card connect to lte on yours? I have read some posts where a new sim card from ATT store fixed this issue, but I know you tried yours already. Maybe hardware problem with the phone itself? I'm out of ideas, sorry.
BYOBret said:
Ah bummer. What phone are you using? Does her sim card connect to lte on yours? I have read some posts where a new sim card from ATT store fixed this issue, but I know you tried yours already. Maybe hardware problem with the phone itself? I'm out of ideas, sorry.
Click to expand...
Click to collapse
I put my SIM in her phone and visa versa, and both SIMs get LTE on my phone, but not on her phone. Here's what I think. The seller on Newegg changed the IMEI and falsely represented the phone as supporting LTE. That's really the only think I can conclude. The IMEI number it shipped with states LTE support in the IMEI look-up database. OR the IMEI information in the database is inaccurate for the phone.
The hardware is identical to the AT&T version, as are all "GSM" M8 versions (meaning Verizon and Sprint are excluded). So there shouldn't be any reason why LTE shouldn't work, as long as you are on the correct radio.
Its not a hardware issue, and something else is going on. It seems from your OP and subsequent posts, that you've tried a variety of things. You radio and ROM are kind of a mish-mosh right now. I'd suggest RUU back to stock Dev Edition or stock AT&T (latter probably being the best bet) and let us proceed from there to make things less confusing.
redpoint73 said:
The hardware is identical to the AT&T version, as are all "GSM" M8 versions (meaning Verizon and Sprint are excluded). So there shouldn't be any reason why LTE shouldn't work, as long as you are on the correct radio.
Its not a hardware issue, and something else is going on. It seems from your OP and subsequent posts, that you've tried a variety of things. You radio and ROM are kind of a mish-mosh right now. I'd suggest RUU back to stock Dev Edition or stock AT&T (latter probably being the best bet) and let us proceed from there to make things less confusing.
Click to expand...
Click to collapse
I flashed the latest official AT&T ROM, but this made no difference what-so-ever. I'm currently using the exact same ROM and firmware on my HTC One M8. I get LTE all-day-long no problem, my wife's phone does not. I already changed the MID to match my AT&T MID and also the CID, but that made no difference. The only thing I haven't tried is changing the model name. My model name is M8_UL_CA and hers is M8_UL. I can't figure out how to change this value, but I'm not sure it makes any difference.
AT&T LTE bands
Band2 1900MHz
Band4 1700MHz
Band5 850MHz
Band17 700MHz
Band 17 is AT&T's primary LTE band.
Phone is advertised as supporting the following LTE Bands
LTE: 700/900/1800/2100/2600 MHz
TrickMasterPC said:
I flashed the latest official AT&T ROM, but this made no difference what-so-ever.
Click to expand...
Click to collapse
Just the ROM, or the whole RUU? There is a huge difference. There are something like 36 partitions, and ROM (/system) is just one of them. The RUU flashes every partition.
I know you mentioned you previously flashed the AT&T RUU. But its also clear that you did a bunch of other things since then. The reason (as already stated) I want you to RUU now, is to put you on a stock AT&T software to give us a clean "blank slate" to work forward from here. As opposed to having too many other variables that can cause problems. For instance, its a known issue that Euro ROMs (such as ARHD) have some issues on AT&T's LTE network. So being on that ROM just compounds another layer of issues on top of issues. Going to a stock AT&T software configuration is a much cleaner state to troubleshoot your from.
TrickMasterPC said:
The only thing I haven't tried is changing the model name. My model name is M8_UL_CA and hers is M8_UL. I can't figure out how to change this value, but I'm not sure it makes any difference.
Click to expand...
Click to collapse
Model name does not make any difference, that I have seen. I've seen plenty of folks "convert" from one carrier version to another, and the steps of s-off, change CID and MID, flash RUU is all it takes (changing model name not required).
And that is probably also the reason that I've never seen a mod for changing model name (it doesn't actually affect anything as far as device checks).
I'd say, don't worry about it and don't waste your time trying.
TrickMasterPC said:
AT&T LTE bands
Band2 1900MHz
Band4 1700MHz
Band5 850MHz
Band17 700MHz
Band 17 is AT&T's primary LTE band.
Phone is advertised as supporting the following LTE Bands
LTE: 700/900/1800/2100/2600 MHz
Click to expand...
Click to collapse
By "primary" band, I assume you mean the one most commonly used by AT&T. Your phone needs to support the band that AT&T is using in your area. So unless you know for fact that 700 Mhz is what they are using in your area, it can be any of the four bands.
I mentioned that that this is not a hardware issue. But I should clarify, its not a matter of a difference in hardware between GSM versions (since they are actually all the same). But it occurs to me that it is fully possible that there may simply be a hardware defect that means your LTE simply broken, and the seller should replace the device.
If we can successfully confirm that you are on full stock AT&T software by RUU (confirm proper radio, main version, etc.) and LTE is still not working (and we know the SIM is good); then I pretty much have to conclude the phone is simply defective/broken.
redpoint73 said:
Just the ROM, or the whole RUU? There is a huge difference. There are something like 36 partitions, and ROM (/system) is just one of them. The RUU flashes every partition.
I know you mentioned you previously flashed the AT&T RUU. But its also clear that you did a bunch of other things since then. The reason (as already stated) I want you to RUU now, is to put you on a stock AT&T software to give us a clean "blank slate" to work forward from here. As opposed to having too many other variables that can cause problems. For instance, its a known issue that Euro ROMs (such as ARHD) have some issues on AT&T's LTE network. So being on that ROM just compounds another layer of issues on top of issues. Going to a stock AT&T software configuration is a much cleaner state to troubleshoot your from.
Model name does not make any difference, that I have seen. I've seen plenty of folks "convert" from one carrier version to another, and the steps of s-off, change CID and MID, flash RUU is all it takes (changing model name not required).
And that is probably also the reason that I've never seen a mod for changing model name (it doesn't actually affect anything as far as device checks).
I'd say, don't worry about it and don't waste your time trying.
By "primary" band, I assume you mean the one most commonly used by AT&T. Your phone needs to support the band that AT&T is using in your area. So unless you know for fact that 700 Mhz is what they are using in your area, it can be any of the four bands.
I mentioned that that this is not a hardware issue. But I should clarify, its not a matter of a difference in hardware between GSM versions (since they are actually all the same). But it occurs to me that it is fully possible that there may simply be a hardware defect that means your LTE simply broken, and the seller should replace the device.
If we can successfully confirm that you are on full stock AT&T software by RUU (confirm proper radio, main version, etc.) and LTE is still not working (and we know the SIM is good); then I pretty much have to conclude the phone is simply defective/broken.
Click to expand...
Click to collapse
I installed the HTC One M8 AT&T full RUU from this webpage: http://www.htc.com/us/support/rom-downloads.html (made no difference) and I tried it twice just to be sure so... it must be that AT&T in my area is using an unsupported LTE band, OR like you said something's wrong with the radio. Doesn't the radio hardware have specific frequency crystals to send/receive only on certain frequencies? Or is this is a fully digital self-tuning radio that receives/transmits on any frequency as programmed.
TrickMasterPC said:
I installed the HTC One M8 AT&T full RUU from this webpage: http://www.htc.com/us/support/rom-downloads.html (made no difference) and I tried it twice just to be sure so... it must be that AT&T in my area is using an unsupported LTE band, OR like you said something's wrong with the radio. .
Click to expand...
Click to collapse
I've never heard of AT&T using a band not supported by this phone. Their LTE network is fairly mature at this point, at least to the degree that they aren't adding bands not previously used, and not supported by relatively current (AT&T branded) devices.
If you confirmed that the proper AT&T radio was properly installed by the RUU, and checked the APN is good; have to conclude there is a hardware defect.
Normally, I'd suggest in that case that you contact the seller for an exchange or refund. But this is a tricky situatin, in that you've modified the phone, and trying to get it to work on LTE bands not specified for the device as it was manufactured.
TrickMasterPC said:
Doesn't the radio hardware have specific frequency crystals to send/receive only on certain frequencies?
Click to expand...
Click to collapse
Nope. Not sure about "crystals". But while you are correct that in older phones the band compatibility was set in hardware; the Snapdragon 801 was one of the first smartphone chipsets (if not the first) where band compatibility is determined solely by software (within reasonable limits - CDMA bands require different hardware). When I said the GSM variants are identical in hardware, I meant it.
Im sure someone has had you check this already but goto phone press *#*#4636*#*# scroll down there will be a drop down menu. See if you can select it.
Also att has been throttling back their users. So if you use to much net I think limit is 5gig they cut your speeds down and you want be able to connect any higher.
-Epix- said:
Also att has been throttling back their users. So if you use to much net I think limit is 5gig they cut your speeds down and you want be able to connect any higher.
Click to expand...
Click to collapse
It should be noted that this is only for those on grandfathered unlimited data plans. Those on tiered data plans will not be throttled, but be charged an overage once your allotment is used up.
Compare nv item 6828 and 6829 between yours and your wife phone using QXDM and QPST. You will get the answer why cannot receive LTE.
did you manage to solve the issue? I am having a similar problem with my htc one m8, it locks only to edge and cannot get it to work with LTE or 3G. I have super CID and MID is 0P6B10000, however the model is M8_UL_CA which is on ATT as far as I know, I am in EU. my SIM card works on my M7 with LTE and 3G but in my M8 I got only EDGE
waseem86 said:
did you manage to solve the issue? I am having a similar problem with my htc one m8, it locks only to edge and cannot get it to work with LTE or 3G. I have super CID and MID is 0P6B10000, however the model is M8_UL_CA which is on ATT as far as I know, I am in EU. my SIM card works on my M7 with LTE and 3G but in my M8 I got only EDGE
Click to expand...
Click to collapse
Post your full details and I can try to troubleshoot. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Does the AT&T M8 have the same radio bands/frequencies as the developer edition?
As far as the specs listed, and as far as I know, yes.
Although some folks have found that the versions sometimes contain band support for bands not listed in a particular versions specs. So the longer answer, is that there may be some small hidden differences (additional support bands on one versus the other).
It might be more useful for you to describe your intent, what you are trying to accomplish etc.
For instance, if you have the necessary bands for your carrier on the Dev Edition, changing to AT&T won't change that.
But the band support is either identical or at the most, minor differences.
I have a gold AT&T M8... It's unlocked s-off, etc... (bought it off Swappa loaded with Dev edition, s-off/unlocked, etc)
My carrier is T-Mobile... currently I have it flashed with the Dev edition of Marshmallow... I THINK my radio's the MM edition... (H-boot shows the radio is listed as 1.29.214500021.24_2G/OS as 6.12.1540.4)
Just trying to make sure I'm running something that won't leave me hanging on radio's... I've dabbled with GPE and T-Mo roms... but wasn't sure if the Dev radio would try and support bands that the hardware won't actually support...
Is there a real way to verify the bands the hardware will support?
scifan said:
I have a gold AT&T M8... It's unlocked s-off, etc... (bought it off Swappa loaded with Dev edition, s-off/unlocked, etc)
My carrier is T-Mobile... currently I have it flashed with the Dev edition of Marshmallow... I THINK my radio's the MM edition... (H-boot shows the radio is listed as 1.29.214500021.24_2G/OS as 6.12.1540.4)
Just trying to make sure I'm running something that won't leave me hanging on radio's... I've dabbled with GPE and T-Mo roms... but wasn't sure if the Dev radio would try and support bands that the hardware won't actually support...
Is there a real way to verify the bands the hardware will support?
Click to expand...
Click to collapse
The hardware is identical between the T-Mob, AT&T, Dev Ed and most other M8 versions. Band support is determined by the radio baseband firmware.
That being said, you do indeed have the MM radio, and most likely the Dev Ed radio (can't seem to find that radio number, at the moment), which is designed to work on AT&T's network. That means on T-Mob, you will have 2G (voice and EDGE data), 3G 1900 MHz (Band 2) and LTE (AWS); but you will not have 3G (HSPA) where T-Mob is using the HSPA AWS band (3G Band 4). This may or may not be an issue depending on your location. From what I'm reading, T-Mob is in the process of shutting down 3G service on the AWS band anyway, and migrating all 3G service to 1900 MHz (HSPA Band 2), one market region at a time. So you may not need the 3G AWS band, anyway.
However, if you find you need 3G AWS band at your location, you may want to go the the MM T-Mob radio once that update rolls out. Another option (if you really need the 3G AWS band now) might be to roll back to T-Mob Lollipop firmware, but that may cause its own complications.
redpoint73 said:
The hardware is identical between the T-Mob, AT&T, Dev Ed and most other M8 versions. Band support is determined by the radio baseband firmware.
That being said, you do indeed have the MM radio, and most likely the Dev Ed radio (can't seem to find that radio number, at the moment), which is designed to work on AT&T's network. That means on T-Mob, you will have 2G (voice and EDGE data), 3G 1900 MHz (Band 2) and LTE (AWS); but you will not have 3G (HSPA) where T-Mob is using the HSPA AWS band (3G Band 4). This may or may not be an issue depending on your location. From what I'm reading, T-Mob is in the process of shutting down 3G service on the AWS band anyway, and migrating all 3G service to 1900 MHz (HSPA Band 2), one market region at a time. So you may not need the 3G AWS band, anyway.
However, if you find you need 3G AWS band at your location, you may want to go the the MM T-Mob radio once that update rolls out. Another option (if you really need the 3G AWS band now) might be to roll back to T-Mob Lollipop firmware, but that may cause its own complications.
Click to expand...
Click to collapse
The last time I ran a T-Mo radio on my M8 HSPA wouldn't work at all because even though they'd refarmed my area, it would try and run on frequencies my phone didn't have... (it was LTE or no data)
And I either was able to get a stable Bluetooth connection, or a stable cellular data connection... but I couldn't get both to be happy at the same time... (I found switching from WiFi to Cellular was problematic under some of the 4.x stock OS's... and then bluetooth was spotty under most of the stock 5.x rom's... and cellular switching wasn't consistent under ASOP...)
I don't know... I think at this point, I'm going to see what happens after the rest of the Sense MM releases come out... if I can't get something consistent, I'll probably work on selling this one and move to a new phone... it's nearly time anyway.
scifan said:
The last time I ran a T-Mo radio on my M8 HSPA wouldn't work at all because even though they'd refarmed my area, it would try and run on frequencies my phone didn't have... (it was LTE or no data)
Click to expand...
Click to collapse
I don't know what you mean that "it would try and run on frequencies my phone didn't have" as that really doesn't make sense (or I'm not properly understanding what you mean).
T-Mob radio is designed to run on their network, so 3G should work whether its refarmed (1900 Band 2) or not (AWS Band 4).
scifan said:
And I either was able to get a stable Bluetooth connection, or a stable cellular data connection... but I couldn't get both to be happy at the same time... (I found switching from WiFi to Cellular was problematic under some of the 4.x stock OS's... and then bluetooth was spotty under most of the stock 5.x rom's... and cellular switching wasn't consistent under ASOP...)
Click to expand...
Click to collapse
Hard to speculate what the issue there was, as I don't know the specifics of what ROM(s) you were on (version, stock, custom) as well as what firmware number. But what I normally would have recommended, is to baseline to full stock T-Mob using RUU, and go from there; to eliminate mismatches between ROM, firmware, etc.
But it sounds like you are past that point, and not necessarily looking for fixes for things that happened in the past.
redpoint73 said:
I don't know what you mean that "it would try and run on frequencies my phone didn't have" as that really doesn't make sense (or I'm not properly understanding what you mean).
T-Mob radio is designed to run on their network, so 3G should work whether its refarmed (1900 Band 2) or not (AWS Band 4).
Click to expand...
Click to collapse
I've read elsewhere that if your baseband/radio includes frequencies your phone actually doesn't have hardware to support, that you can get stuck where your device will try and utilize that frequency and not realize that it's failing to communicate... I don't know if this was the situation, but it was significantly impacting my cellular data experience...
redpoint73 said:
Hard to speculate what the issue there was, as I don't know the specifics of what ROM(s) you were on (version, stock, custom) as well as what firmware number. But what I normally would have recommended, is to baseline to full stock T-Mob using RUU, and go from there; to eliminate mismatches between ROM, firmware, etc.
But it sounds like you are past that point, and not necessarily looking for fixes for things that happened in the past.
Click to expand...
Click to collapse
When I originally moved to 4.4.x on T-Mobile, I RUU'd the phone... I want to say that I've had to do this once or twice when I soft bricked my phone in the past as well... I've made too many changes to speculate on one baseband/rom or another... I've flopped back and forth between being fully GPE and a combo of Sense Firmware and GPE rom...
At this point, I'm running the MM Dev firmware and rooted Dev Rom from This thread.
Btw, normally, the bluetooth issues I've experienced are pauses in music playback... with my current configuration sometimes I'll see bluetooth disconnect once after it initially connects.... Pandora controls work well. and everything else works as expected.
scifan said:
I've read elsewhere that if your baseband/radio includes frequencies your phone actually doesn't have hardware to support, that you can get stuck where your device will try and utilize that frequency and not realize that it's failing to communicate... I don't know if this was the situation, but it was significantly impacting my cellular data experience...
Click to expand...
Click to collapse
The only such instance I am aware of on the M8 that is similar to what you describe, is if you try to flash a "GSM" radio (basically any non-CDMA version) to one of the CDMA variants (Sprint, Verizon) which results in a radio brick. Meaning the phone doesn't work, but it breaks the radio. But this is an issue unique to Sprint, Verizon M8.
All other M8 versions (with the odd exceptions of the dual SIM, and M8 Eye - which are really different devices) are identical in hardware and the radios are interchangeable.
Even with the CDMA M8, from what I understand, the hardware is the same as the GSM versions. Its just the partitioning that is different that causes the radio brick.
redpoint73 said:
The only such instance I am aware of on the M8 that is similar to what you describe, is if you try to flash a "GSM" radio (basically any non-CDMA version) to one of the CDMA variants (Sprint, Verizon) which results in a radio brick. Meaning the phone doesn't work, but it breaks the radio. But this is an issue unique to Sprint, Verizon M8.
All other M8 versions (with the odd exceptions of the dual SIM, and M8 Eye - which are really different devices) are identical in hardware and the radios are interchangeable.
Even with the CDMA M8, from what I understand, the hardware is the same as the GSM versions. Its just the partitioning that is different that causes the radio brick.
Click to expand...
Click to collapse
I know I've flashed back and forth between T-Mobile, AT&T, GPE and Dev radio's without breaking things... it just seemed that some radio frequencies didn't work...
Actually the reason I got a att m8 off swappa was because of the increased amount of bands over the tmobile version
Holds all lte and hspa bands along with additional lte ones