[Q] Flashing T-mobile radio on SnowJB ? - AT&T LG Optimus G

Has anyone tried/attempted flashing the t-mobile radio from the N4 conversion thread onto the SnowJB ROM
Is there a remote possibility of this working on SnowJB (Considering that the HW and the OS version is same).. ?
I am a t-mobile user on LGOG and have been getting 4g speeds only in patches where refarming is complete.. I would love to have hsdpa speeds and sacrifice LTE capabilities for that.

Please search before posting.
http://forum.xda-developers.com/showthread.php?t=2205771

Related

[Q] Atrix 3G?

Well, i was searching and i noticed that here is no section here for the 3G GSM version of ATRIX, just the 4G US version.
What about the european or south american (or even asian) versions? Does all this custom roms works for them too?
ravefolk said:
Well, i was searching and i noticed that here is no section here for the 3G GSM version of ATRIX, just the 4G US version.
What about the european or south american (or even asian) versions? Does all this custom roms works for them too?
Click to expand...
Click to collapse
They are the same device essentially, and I'm pretty sure they're 4G enabled, just worded differently. They support HSDPA 14mbps (Cat 10) / HSUPA 2.0mbps which is HSPA in the US I think.
just the at&t atrix is currently unlockable but likely the international ones are getting unlocked with update so currently it is just possible for at&t atrix to flash custom roms, and the thing with the 3g/4g naming is region specific but the same hardware.
Here in germany 4g is lte, actually lte is called 3.9g so we donĀ“t even have 4g
tehrules said:
They are the same device essentially, and I'm pretty sure they're 4G enabled, just worded differently. They support HSDPA 14mbps (Cat 10) / HSUPA 5.76mbps which is HSPA in the US I think.
Click to expand...
Click to collapse
Fixed that for ya!
It's the same phone
Just switches automatically to 3g. But in EU the carriers have very expensive prices for hdspa connection. So i use it in 2g mode (leeeesss of battery consume).
Ok thanks to all of you very much. I'm a little outdated about wireless technologies and i tought 4G was cdma-based stuff. So hsdpa-hsupa are 4g gsm based technologies? I can flash my atrix with a custom rom with no problems?
Another thing that bothers me is all that acessories that comes in the pack. Remote control, dock, hdmi... will all this stuff work with the custom roms?
One last thing: Can i use it on hdmi without that "hdmi modes", just displaying whats on my screen like a game or movie, like i do with my xoom?
Sent from my Xoom | Tapatalk
Just out of curiosity, do all Atrix use the same 3G bands?
If not, wouldn't that affect software porting?
CaelanT said:
Fixed that for ya!
Click to expand...
Click to collapse
but th eofficial specs on motorola's website say 14.4 down and 2.0 upload, not 5.76. are you sure its 5.76Mbps HSUPA?

latest ota and gsm support question

hi, I have a quick question with the latest OTA and the GSM (global support) on the rezound. If you flash with the latest OTA, would you get 2g, 3g speed on ATT and T-Mobile? Has anyone tried it?
I think you get the same speeds as before. The physical hardware only supports certain bands and you can't change that with software.
The rezound is only able to do 3g on the 2100mhz band, so no, you'll only get EDGE on both T-Mobile and ATT.
Sent from my ADR6425LVW using Tapatalk 2

Unlocked or get the Tmobile version?

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.

SM-G925F on T-Mobile performance?

Just really want that Emerald Green color and don't mind the extra cost. Anyone have a SM-G925F that they use on T-Mobile and can describe their experience, and if LTE is working properly? Thank you.
shouldn't be a problem. seems all he bands line up so it would work with lte and everything. just not wifi calling... unless you flash a tmobile based custom rom
Hey @kaydash did you end up getting the g925f? how's the internet speed with T-mobile? I'm considering getting the same but I read that it wasn't compatible with the AT&T LTE frequency bands so I was wondering whether there would be a problem with T-mobile too...thanks in advance!

AT&T Radio bands info

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

Categories

Resources