Related
Hi
I just bought an unlocked i727 (AT&T Skyrocket). In addition to unlocking it, the previous owner also modded the phone to work on AWS bands (HSDPA 1700/2100). I was all impressed by this feat, but now that I come to XDA, I find all the guy probably really did is flash the radio, which probably both unlocked the phone and enabled AWS (explained here: http://forum.xda-developers.com/showthread.php?t=2029650). Currently in "About phone", the Build Number is IMM76D.UCLF6 and the Baseband version says unknown.
The phone is running stock Android 4.0.4 (ICS), and I want to put on the latest CM10.1 stable build, but when I go to this page, it says I need a Jelly Bean radio: http://www.teamchopsticks.org/p/cm101-release-notes2.html
So now I'm worried that if I choose the wrong radio, I'll no longer have AWS bands, which I need since those are the only bands my carrier (Mobilicity) uses. Can someone please tell me which of the radios listed on the teamchopsticks blog I should use to keep the AWS bands on CM10? I'm guessing its the T-mobile version (UVMC6)...?
Thanks!
Edit: Alternatively, could I just install CM9 and leave the current radio as is? I don't really care if I have the latest android version, I just want to get rid of the stock AT&T rom and its associated bloatware.
Sandmonkee said:
Hi
I just bought an unlocked i727 (AT&T Skyrocket). In addition to unlocking it, the previous owner also modded the phone to work on AWS bands (HSDPA 1700/2100). I was all impressed by this feat, but now that I come to XDA, I find all the guy probably really did is flash the radio, which probably both unlocked the phone and enabled AWS (explained here: http://forum.xda-developers.com/showthread.php?t=2029650). Currently in "About phone", the Build Number is IMM76D.UCLF6 and the Baseband version says unknown.
The phone is running stock Android 4.0.4 (ICS), and I want to put on the latest CM10.1 stable build, but when I go to this page, it says I need a Jelly Bean radio: http://www.teamchopsticks.org/p/cm101-release-notes2.html
So now I'm worried that if I choose the wrong radio, I'll no longer have AWS bands, which I need since those are the only bands my carrier (Mobilicity) uses. Can someone please tell me which of the radios listed on the teamchopsticks blog I should use to keep the AWS bands on CM10? I'm guessing its the T-mobile version (UVMC6)...?
Thanks!
Edit: Alternatively, could I just install CM9 and leave the current radio as is? I don't really care if I have the latest android version, I just want to get rid of the stock AT&T rom and its associated bloatware.
Click to expand...
Click to collapse
You can't unlock the operator lock with a radio. You need both a specific radio and a specific firmware.
AWS support is not a special feature that can be enabled, afaik it's a standard function of this phone.
The Radios made specifically for this phone (Rogers & AT&T) should have full AWS support, I don't know about the others.
Also the TeamChopsticks site is mighty dated.
You should check out the official threads in General and Development.
Also these links are always good to have:
http://get.cm/?device=skyrocket
http://10.1.cmxlog.com/?device=skyrocket
http://changelog.bbqdroid.org/#/skyrocket/next
Hmmm... well do you know if its true that CM10 requires a "Jelly Bean Radio"?
Or am I better off just loading CM9? That way I shouldn't have to modify the radio, right?
Thanks!
Sandmonkee said:
Hmmm... well do you know if its true that CM10 requires a "Jelly Bean Radio"?
Or am I better off just loading CM9? That way I shouldn't have to modify the radio, right?
Thanks!
Click to expand...
Click to collapse
You could try flashing CM9, then it might even say in what radio you have.
Yes, CM10 requires a Jellybean radio.
If you flash the Rogers radio in my signature or the AT&T radio you'll still have AWS and it won't relock your phone.
There's really no reason not to flash a JB radio and CM10.1.. you're not losing out on anything by doing it.
Official JB radios:
R UXUMA7 http://forum.xda-developers.com/showpost.php?p=38195641&postcount=44
UCMC1 http://forum.xda-developers.com/showthread.php?t=2228292
CM10.1 Discussion http://forum.xda-developers.com/showthread.php?t=2138102
CM10.1 Development http://forum.xda-developers.com/showthread.php?t=2138102
Good luck!
lingowistico said:
You could try flashing CM9, then it might even say in what radio you have.
Yes, CM10 requires a Jellybean radio.
If you flash the Rogers radio in my signature or the AT&T radio you'll still have AWS and it won't relock your phone.
There's really no reason not to flash a JB radio and CM10.1.. you're not losing out on anything by doing it.
Official JB radios:
R UXUMA7 http://forum.xda-developers.com/showpost.php?p=38195641&postcount=44
UCMC1 http://forum.xda-developers.com/showthread.php?t=2228292
CM10.1 Discussion http://forum.xda-developers.com/showthread.php?t=2138102
CM10.1 Development http://forum.xda-developers.com/showthread.php?t=2138102
Good luck!
Click to expand...
Click to collapse
AWS band in HSDPA (or HSPA+) is not enabled in at&t or Roger's radios,since those 2 networks don't use it for HSDPA.. It's used for LTE (700,1700/2100)
AWS 1700/2100 band in HSDPA can be enabled by flashing T-Mobile blaze JB radio...It should work on cm10.1 since it is a JB radio...
So I spent pretty much all of yesterday reading up on the subject. Since we were under a tornado watch all day anyways, I really had nothing else to do!
After a while, I found the "secret codes" (listed here: http://forum.xda-developers.com/showthread.php?t=1492700), and punched in *#1234#. This told me that my radio was "T769-UVLB7", which I believe is the 4th one from the bottom on this page: http://forum.xda-developers.com/showthread.php?t=1895400, ie the Blaze radio. That would make sense because it gels with my Android version (4.0.4). Anyways, googling that radio eventually led me to this link: http://forum.xda-developers.com/showthread.php?t=1507825 which had a ton of useful information. So thats the radio mystery solved.
From the same info screen, I could see that my ROM was i727-UCLF6, a somewhat outdated stock ICS rom. So now I know what my phone's current status is in case I need to bring it back because my other combinations don't work for some reason.
So I think I've decided to go with the Pacman JB rom (http://forum.xda-developers.com/showthread.php?t=2178402) and if it doesn't work with my current radio, I'll first try the updated Blaze radio, UVMB1, listed third in that same list I linked to above. If that doesn't work, I'll try the others in that list until I get a combination that does (probably starting with UCMC1). I'm also considering the Jedi Mind Trick T989 rom (http://forum.xda-developers.com/showthread.php?t=1818305). I'll post results when I have them!
Thanks for the help everyone!
mahanddeem said:
AWS band in HSDPA (or HSPA+) is not enabled in at&t or Roger's radios,since those 2 networks don't use it for HSDPA.. It's used for LTE (700,1700/2100)
AWS 1700/2100 band in HSDPA can be enabled by flashing T-Mobile blaze JB radio...It should work on cm10.1 since it is a JB radio...
Click to expand...
Click to collapse
So what you're saying is: AWS for LTE is enabled in Rogers and AT&T, but, it's disabled for HSPA by default.
I was under the impression that 2100 is used for 3G/HSPA by default eitherway, but you're saying it's not?
mahanddeem said:
AWS band in HSDPA (or HSPA+) is not enabled in at&t or Roger's radios,since those 2 networks don't use it for HSDPA.. It's used for LTE (700,1700/2100)
AWS 1700/2100 band in HSDPA can be enabled by flashing T-Mobile blaze JB radio...It should work on cm10.1 since it is a JB radio...
Click to expand...
Click to collapse
Didn't notice any difference after flashing Blaze LB7 radio. Vodafone has 2100 for 3G/HSPA. Already had full signal with RUXUMA7 and it was still full with LB7 and speed was the same (3.7Mbit down/2.6Mbit up)..
lingowistico said:
Didn't notice any difference after flashing Blaze LB7 radio. Vodafone has 2100 for 3G/HSPA. Already had full signal with RUXUMA7 and it was still full with LB7 and speed was the same (3.7Mbit down/2.6Mbit up)..
Click to expand...
Click to collapse
Skyrocket
2G 850/900/1800/1900
3G 850/1900/2100
4G(LTE) 700/1700/2100
http://m.gsmarena.com/samsung_galaxy_s_ii_skyrocket_i727-4303.php
Blaze
2G 850/900/1800/1900
3G 850/1700/1900/2100
4G(LTE) (none)
http://m.gsmarena.com/samsung_galaxy_s_blaze_4g_t769-4420.php
I would recommend you do more reading and reading before you mess with the radio flashing
Good luck
---------- Post added at 04:35 PM ---------- Previous post was at 04:18 PM ----------
lingowistico said:
So what you're saying is: AWS for LTE is enabled in Rogers and AT&T, but, it's disabled for HSPA by default.
I was under the impression that 2100 is used for 3G/HSPA by default eitherway, but you're saying it's not?
Click to expand...
Click to collapse
AWS (Advanced Wireless Service) protocol uses the 2100 for downlink
and the 1700 for uplink..
http://en.m.wikipedia.org/wiki/Advanced_Wireless_Services
The skyrocket has the 2100 in 3G and LTE
but 1700 is not enabled in 3G
Hence the AWS band (UMTS band 4) is not supported in 3G
mahanddeem said:
...
Click to expand...
Click to collapse
Thank you for explaining this, I didn't know all the specifics.
You are correct, the Blaze radio disables LTE and enables AWS.
As you can see here 1700 is not in use in Europe. So the Blaze JB radio is of no use to me.
So in the end, the Pacman JB 4.2.2 ROM worked without a hitch. I did not have to flash the radio at all, it is still working as before.
Baseband still shows up as unknown (the nifty secret codes no longer work), and kernel is now 3.0.72 cyanogenmod.
The phone's working greatI love it when a plan comes together!
What speeds do you get currently on speed test app ?
If your goal is a rom with no bloatware you can debloate a stock tw one...Personally I can never live with cm camera...
At the moment, only about 1.5 MBps, but I am not in a good service area. Even so, everything seems to load quickly.
My only complaints so far would be the ROM itself... already crashed a couple of times, and it has a bizarre way of connecting to the computer (no USB storage mode).
mahanddeem said:
AWS band in HSDPA (or HSPA+) is not enabled in at&t or Roger's radios,since those 2 networks don't use it for HSDPA.. It's used for LTE (700,1700/2100)
AWS 1700/2100 band in HSDPA can be enabled by flashing T-Mobile blaze JB radio...It should work on cm10.1 since it is a JB radio...
Click to expand...
Click to collapse
So it turns out that it may noit have been the ROM after all, but GO Launcher. Everytime I get a new phone, I get sucked in by GO Launcher's sexy looks, but the result is always the same: lagginess and crashes. After switching to Apex launcher, things seem to have settled down.
In terms of the radio, I did some more traveling around today and I would have to say that reception is not as good as it is on my AWS Nexus S, so I might try some different radios after all. Just want to confirm though that if I use an i727 radio (like UCMC1) instead of a T989 radio (like the Blaze radio), I will no longer have access to AWS. Is that right?
Right now I'm thinking UVMB1 from here might be the first stop: http://forum.xda-developers.com/showthread.php?t=1895400
If you ask me , TW stock debloated and tweaked by me is my and always be my rom ...
For the reception, if you have to have the best reception for a network that uses AWS 1700/2100mhz bands for HSDPA/HSPA+ , the skyrocket is not your phone...Or you have to live with issues every now and then...
That's why your nexus s(the T version) has better reception it's a device with native 1700/2100 band support...
Try some other T mobile radios from the blaze,Hercules or galaxy note 1 (remeber you have to use jellybean radios with any jeallybean based rom) and see what gives you best reception, but again don't expect miracles...
Or another note, try a stock jb uvmc6 rom (flash a skyrocket kernel for the roation problem) and uvmc6 radio or another T-Mobile radio as a combo if it is better regarding general network performance...
Edit: answering your question,yes ..skyrocket or Roger's modem will not have 1700/2100 AWS HSPA connectivity...And that "first stop" was my first advice for you...UVMB1 radio...
mahanddeem said:
If you ask me , TW stock debloated and tweaked by me is my and always be my rom ...
Click to expand...
Click to collapse
Hey mahanddeem,
Thanks again for the help. Even after removing Go Launcher, I'm still getting a few random reboots/shutdowns per day - enough to annoy me. I did some searching and found out about the sticky button issue, but I have a feeling thats not my problem. Usually when the phone shuts down on its own, I have to remove the battery before the phone will turn on again. I'm not completely discounting the possibility that I have a sticky button, it just seems odd that the solution involves pulling the battery. That makes it seem more like a software/Rom issue to me, so I'm thinking of going back to a TW-based rom, but I don't want to restore my original stock with all its extra bloat-ware. All that to say that I was hoping you could tell me which de-bloated TW Rom you are using. I've found Embryo, which looks interesting: http://forum.xda-developers.com/showthread.php?t=2074328. Is that what you have?
Or another note, try a stock jb uvmc6 rom (flash a skyrocket kernel for the roation problem) and uvmc6 radio or another T-Mobile radio as a combo if it is better regarding general network performance...
Click to expand...
Click to collapse
Thanks for the suggestion. I'm trying to avoid a full stock ROM, mostly because of the bloatware and branding (I can't stand seeing a corporate logo every time I start my phone!) - this is basically the reason I put a custom ROM on in the first place - plus the extra control of course. If this is the only thing that will stop my phone from randomly rebooting and shutting down though, then I'll have to consider it. Hopefully the stripped down TW version that you recommend will help though.
Edit: answering your question,yes ..skyrocket or Roger's modem will not have 1700/2100 AWS HSPA connectivity...And that "first stop" was my first advice for you...UVMB1 radio...
Click to expand...
Click to collapse
Heh heh true enough I still haven't tried flashing anything - I'm still educating myself. The last thing I want to do is start something I can't recover from!
Sandmonkee said:
Hey mahanddeem,
Thanks again for the help. Even after removing Go Launcher, I'm still getting a few random reboots/shutdowns per day - enough to annoy me. I did some searching and found out about the sticky button issue, but I have a feeling thats not my problem. Usually when the phone shuts down on its own, I have to remove the battery before the phone will turn on again. I'm not completely discounting the possibility that I have a sticky button, it just seems odd that the solution involves pulling the battery. That makes it seem more like a software/Rom issue to me, so I'm thinking of going back to a TW-based rom, but I don't want to restore my original stock with all its extra bloat-ware. All that to say that I was hoping you could tell me which de-bloated TW Rom you are using. I've found Embryo, which looks interesting: http://forum.xda-developers.com/showthread.php?t=2074328. Is that what you have?
Thanks for the suggestion. I'm trying to avoid a full stock ROM, mostly because of the bloatware and branding (I can't stand seeing a corporate logo every time I start my phone!) - this is basically the reason I put a custom ROM on in the first place - plus the extra control of course. If this is the only thing that will stop my phone from randomly rebooting and shutting down though, then I'll have to consider it. Hopefully the stripped down TW version that you recommend will help though.
Heh heh true enough I still haven't tried flashing anything - I'm still educating myself. The last thing I want to do is start something I can't recover from!
Click to expand...
Click to collapse
I take it you don't know how to root a stock Rom and delete the bloatware yourself?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
I'm pretty sure I could root it, that much seems within my limited skill set. But first determining HOW to remove the bloatware, and then WHICH things I can safely remove... That I'm not sure of. Besides, if there are already ROM's out there that have done this, why would I duplicate the effort? I'm all in favour of doing things just so I can learn how to do them, but the fact is I have other things I need to do with my time besides fiddling with my phone (family, work, motorbike.... and seemingly endless friggin yardwork!)
Sandmonkee said:
I'm pretty sure I could root it, that much seems within my limited skill set. But first determining HOW to remove the bloatware, and then WHICH things I can safely remove... That I'm not sure of. Besides, if there are already ROM's out there that have done this, why would I duplicate the effort? I'm all in favour of doing things just so I can learn how to do them, but the fact is I have other things I need to do with my time besides fiddling with my phone (family, work, motorbike.... and seemingly endless friggin yardwork!)
Click to expand...
Click to collapse
It's very simple, there are plenty of ways to remove bloat, plenty of guides to do it, and charts that show what things are and if you should remove them.
Embryo would be a nightmare for you. Read the thread. If you don't have the time to research and learn, you should not be flashing things on your phone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
Do your researches, it's not gonna happen that anyone here would put a long extensive guide for you so you can "take a look" at it during your coffee time...
Everybody here is learning everyday from others' posts, problems and discussions...So either you put some effort into learning or nobody's gonna spoon feed you..
As a clue , look at Mohan deodexed stock UCMC1,flash,root,start freezing apps that you know you'll not use...Then using any root explorer you can permanently uninstall system apps...And by the way you can use a custom boot animation even on stock,search for how to...
Hello,
I recently purchased a note 5 duos SM-N9208 from Taiwan. I was led to believe that the device was unlocked GSM, but had EV-DO capabilities. My understanding was that this would work on Verizon's network, because it had both radio chips inside. I was told by Verizon that "there is no approved way" for them to get me up and running on their network. The tech made a point of saying there is a difference between approved, and no way. This leads me to believe that something can be done. I'm wondering if someone would be kind enough to help me out. Phone is running original Rom, unrooted, and is basically useless to me right now, as I'm desperately clinging on to my unlimited data with Verizon. Is it possible to root the device, and flash the modem with Verizon note 5 baseband info? Any help anyone can offer would be very much appreciated.
XDA Visitor said:
Hello,
I recently purchased a note 5 duos SM-N9208 from Taiwan. I was led to believe that the device was unlocked GSM, but had EV-DO capabilities. My understanding was that this would work on Verizon's network, because it had both radio chips inside. I was told by Verizon that "there is no approved way" for them to get me up and running on their network. The tech made a point of saying there is a difference between approved, and no way. This leads me to believe that something can be done. I'm wondering if someone would be kind enough to help me out. Phone is running original Rom, unrooted, and is basically useless to me right now, as I'm desperately clinging on to my unlimited data with Verizon. Is it possible to root the device, and flash the modem with Verizon note 5 baseband info? Any help anyone can offer would be very much appreciated.
Click to expand...
Click to collapse
Hi, and welcome to XDA!
When I looked up the specs on the Note 5 Duos, unfortunately it says nothing about CDMA. Having both "radio chips inside" can be taken two ways, in this case, this phone has the capability to handle two GSM carriers (and in this case, like most dual-sim phones, only the first SIM can do 3G/4G/LTE speeds).
Network Technology GSM / HSPA / LTE
2G bands GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
3G bands HSDPA 850 / 1900 / 2100
4G bands LTE
Speed HSPA 42.2/5.76 Mbps, LTE
GPRS Yes
EDGE Yes
Click to expand...
Click to collapse
It seems the only option (if you want to use this phone), is to join a GSM carrier like AT&T, T-Mobile, or one of their MVNO's (like MetroPCS).
Hope this helps.
joel.maxuel said:
Hi, and welcome to XDA!
It seems the only option (if you want to use this phone), is to join a GSM carrier like AT&T, T-Mobile, or one of their MVNO's (like MetroPCS).
Hope this helps.
Click to expand...
Click to collapse
Thank you, Joel! I'm excited to learn as much as possible from tgis forum. I actually changed over to T-Mobile, and have been good for the most part. The problem i'm having now is related to finding a way to flash the radio to all of their Rf's. I rooted, and attempted to flash the modem and bootloader from N920T, but it failed. I am still having a hard timr understanding why the identical hardware will not accept firmware from different model numbers. Again, very inexperienced, so it may be something very obvious i dont know about. If could offer any assistance, or provide and thread links that may be useful, i wpuld very grateful. Ive been searching nonstop, reading, and still cant seem to find a way.
Rockstah said:
Thank you, Joel! I'm excited to learn as much as possible from tgis forum. I actually changed over to T-Mobile, and have been good for the most part. The problem i'm having now is related to finding a way to flash the radio to all of their Rf's. I rooted, and attempted to flash the modem and bootloader from N920T, but it failed. I am still having a hard timr understanding why the identical hardware will not accept firmware from different model numbers. Again, very inexperienced, so it may be something very obvious i dont know about. If could offer any assistance, or provide and thread links that may be useful, i wpuld very grateful. Ive been searching nonstop, reading, and still cant seem to find a way.
Click to expand...
Click to collapse
Well, the hardware (particularly the modem) is not compatible, hance the failed install. You are lucky it cancelled out as you could have had worse problems on your hands.
The way i see it, you will have to wait for other regions for the Note 5 Duos to open up before you get flashing options. I would even question the need for that, if you get a decent range of bands with T-Mo (I am assuming you can get 4G).
If you want to explore further anyway, please check out this thread:
> Samsung Galaxy Note5 > Galaxy Note5 Q&A, Help & Troubleshooting > [Help Thread][Galaxy Note5] Ask Any Question, Noob Friendly
Hope this helps.
joel.maxuel said:
Hope this helps.
Click to expand...
Click to collapse
It did, thank you! I get decent service (including LTE) almost everywhere. Problem is, once I get to my.house, I go completely out of service. No call.I no text. It wouldn't be a big deal, but the Taiwanese phone doesn't have a way to turn WiFi calling.
Rockstah said:
It did, thank you! I get decent service (including LTE) almost everywhere. Problem is, once I get to my.house, I go completely out of service. No call.I no text. It wouldn't be a big deal, but the Taiwanese phone doesn't have a way to turn WiFi calling.
Click to expand...
Click to collapse
Aha. That and no sign of the 700mHz band (which may not be part of your phone anyway, not just hidden by the current firmware).
Since the firmware would need deep support of Wifi Calling (or VoLTE), as in more than just an App, I am afraid you will have to wait until the Duos releases into an area with that support in their firmware (and hope that, that area's firmware doesn't disable a frequency you use).
Makes scraping all the lead paint[*] off the house the more manageable task, doesn't it?
[*] I really don't know if your house does indeed have lead paint. I am assuming it's coated in something metal, or concrete, which avoids typically high frequency radio waves from entering. I never had that problem with my house (which may be strange, since it was built in the 40's), but maybe creating ways to boost the existing signal may be in order instead.
Sorry, I'm not too much in the know, but I heard there is some sort of new update coming in the near future that will improve various aspects of the S7 like better in building reception etc.
So what do I need to be on the look out for? This deal from Target is pretty fair on top of my 5% Red Card bonus. Would this phone work with whatever update Tmo pushes out to receive the full benefits vs a tmobile puchased S7?
http://www.target.com/p/unlocked-samsung-galaxy-s7-edge-g930f-32gb-gsm-black/-/A-51032209
bump
Nope, your link is for the international version, which won't get VoLTE, wifi calling, or updates. You want either the 930T or 930u. Anything else won't work properly.
Edit for clarification - The upcoming changes for the S7 are for more advanced LTE functionality. The extended range/building penetration are already in place, it's Band 12 LTE. The international version you linked will receive data on this band, but you CANNOT call/sms on it, as it's a data only band. The only calling/SMS that can be done on it would be on VoLTE, which you will not have.
So yeah, you'd be getting a crippled phone with none of the advantages you want.
In the last week, the rom maker below got a Note 7 port working on a 930f with T-mobile VOLTE + wifi calling + video calling. Assuming you root and want custom roms, there is an viable option in the international model.
http://forum.xda-developers.com/s7-edge/development/rom-n7-rom-port-romcontrol-t3430358
That being said for the OP:
Why target, swappa is $200 less on either model.
The international model has no US warranty.
The international model is faster with a better battery life but is slighltly weaker playing games: having both for now, completely stock, the 930f is slightly faster feeling. On the other hand, it is like night and day to compare a custom/tweaked rom/kernel of a 930F to a engineering bootloader based 930t's stock rooted rom (the custom roms seem to remove video calls)
The US model (if root matters) has a root solution that can be negated in future builds.
The international model's root trips knox, unlike the US version, reducing the resale value.
entropism said:
Nope, your link is for the international version, which won't get VoLTE, wifi calling, or updates. You want either the 930T or 930u. Anything else won't work properly.
Edit for clarification - The upcoming changes for the S7 are for more advanced LTE functionality. The extended range/building penetration are already in place, it's Band 12 LTE. The international version you linked will receive data on this band, but you CANNOT call/sms on it, as it's a data only band. The only calling/SMS that can be done on it would be on VoLTE, which you will not have.
So yeah, you'd be getting a crippled phone with none of the advantages you want.
Click to expand...
Click to collapse
As the title says I'm on the latest Panama CSC firmware but I've seen many references to the BTU firmware, which should be this one here at SamMobile? I just traded my Nexus 6P for this phone, I don't want/need to root don't want to flash a custom ROM I just want to make sure that I have the best/most correct stock ROM for me in the US on AT&T. I've noticed that my Tab S2 is running a BTU ROM, granted it's a WiFi only tablet but I know it works here for me, which makes me question if I shouldn't switch from the Panamanian ROM.
Questions:
What advantage does switching to the BTU firmware give me?
Will the BTU ROM get me Nougat sooner than others?
Will OTAs still happen (will they happen on the Panama version for that matter?)
Is it as simple grabbing the firmware from SamMobile and flashing it to the phone using Odin?
Or -- should I just stick with the ROM I have now?
I just got this device to use in the US as well, only with T-Mobile. When I got it, it was running the Italian firmware which worked fine except no Samsung Pay. So, I dug around and found a thread here on XDA on how to get Samsung Pay working on this model. That lead me to flash the Australian firmware (XSA) in order for working Samsung Pay (which it is working beautifully now!). That was my only reasoning for flashing a new firmware ... However, I am seeing certain firmwares have historically had faster updates. (From what I have seen around, people mentioned BTU & XSA have seen faster updates - nothing concrete on this, just something I remembered seeing in a post or two ... I assume (and hope) OTAs will happen as normal)
If you want to flash a new firmware, yes, it's as simple as downloading it and flashing with Odin. It will wipe internal storage, so be sure to backup accordingly.
Sent from my SM-G930F using Tapatalk
I've also seen references to the XSA firmware as well. I think that Samsung Pay is now working on BTU as well. SPay is working, upto the point of actually buying something, on my phone right now with the Panamanian Firmware so I'm assuming that SPay is working most everywhere now. If I do flash I'll go BTU simply because it's an English language native version, yeah I realize it shouldn't matter but I feel better. Also my Samsung Tablet is on a BTU firmware and it gets OTAs so I know that should also work.
Thanks for confirming.
YankInDaSouth said:
I just got this device to use in the US as well, only with T-Mobile. When I got it, it was running the Italian firmware which worked fine except no Samsung Pay. So, I dug around and found a thread here on XDA on how to get Samsung Pay working on this model. That lead me to flash the Australian firmware (XSA) in order for working Samsung Pay (which it is working beautifully now!). That was my only reasoning for flashing a new firmware ... However, I am seeing certain firmwares have historically had faster updates. (From what I have seen around, people mentioned BTU & XSA have seen faster updates - nothing concrete on this, just something I remembered seeing in a post or two ... I assume (and hope) OTAs will happen as normal)
If you want to flash a new firmware, yes, it's as simple as downloading it and flashing with Odin. It will wipe internal storage, so be sure to backup accordingly.
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
Okay.. so there's a short answer and a long answer.
The short answer - If you look at all the firmware news and firmware download sites (Sammobile, etc) - you will notice that historically, XSA and BTU variants are the fastest to market with some other variants quickly following and some taking a lot longer. (also go to the end of this reply to see a note about the US market)
Now for the long answer (it's quite long.. so if you don't really care about the details just skip it..)
The CSC is country specific for a reason - it can contain changes to the cellular modem behavior and optimizations (for example, band preference), support advanced features (VoLTE - or HD Voice as it's sometimes referred to, WiFi calling), and compliance with local regulatory requirements (for example, camera shutter sound control, use of Samsung Pay).
As such, is most cases, you are better off using the version specifically optimized for your carrier and country, which usually translates into better cell performance (signal strength, dl/ul speeds) and the ability to leverage advanced features (VoLTE, WiFi Calling) as supported by your carrier. It's actually something quite annoying with Samsung, iPhones (and even some android phones) don't need all these local adaptations.
The issues with using your country and carrier-specific firmware are that you will probably get some additional bloatware, updates may take longer, and some features like Samsung Pay will not be available. In recent years, the modem optimization part (signal strength, and speeds) has been improving to a point where most firmware work well in most places and networks.
So basically it's a trade off - do you want a phone that is optimized for your network and will give you best cell reception, speeds, and potentially support VoLTE, etc.
or do you care more about timely security updates, and potentially support of services not available in your original firmware.
If it's the latter, than you may consider flashing a different region's firmware.
That changes a when dealing with the US market (and some others)
In the US, the big carriers (Verizon, AT&T, T-Mobile, Sprint) actually implement hardware (and / or low level firmware) changes directly with Samsung.
Aside from the obvious changes (using SD820 instead of Exynos 8890) the cellular modem (and supporting software) are completely different and the carriers add specific software to optimize its services and offer advanced features (besides filling your phone with tons of bloatware and taking forever to certify new builds)
So as a US AT&T customer, you will not get any advanced features (HD Calling, Wifi calling) regardless of which firmware region you use. In that case, using XSA or BTU have no downside to them.
The only way to get these advanced features is to get an unlocked SD820 variant (SM-930U) and flash AT&T's (or you respective carrier's) CSC on it (using TWRP) but that means using 3rd party ROMS and manually updating your phone. (and tripping knox).
N-way said:
Okay.. so there's a short answer and a long answer.
The short answer - If you look at all the firmware news and firmware download sites (Sammobile, etc) - you will notice that historically, XSA and BTU variants are the fastest to market with some other variants quickly following and some taking a lot longer. (also go to the end of this reply to see a note about the US market)
Now for the long answer (it's quite long.. so if you don't really care about the details just skip it..)
The CSC is country specific for a reason - it can contain changes to the cellular modem behavior and optimizations (for example, band preference), support advanced features (VoLTE - or HD Voice as it's sometimes referred to, WiFi calling), and compliance with local regulatory requirements (for example, camera shutter sound control, use of Samsung Pay).
As such, is most cases, you are better off using the version specifically optimized for your carrier and country, which usually translates into better cell performance (signal strength, dl/ul speeds) and the ability to leverage advanced features (VoLTE, WiFi Calling) as supported by your carrier. It's actually something quite annoying with Samsung, iPhones (and even some android phones) don't need all these local adaptations.
The issues with using your country and carrier-specific firmware are that you will probably get some additional bloatware, updates may take longer, and some features like Samsung Pay will not be available. In recent years, the modem optimization part (signal strength, and speeds) has been improving to a point where most firmware work well in most places and networks.
So basically it's a trade off - do you want a phone that is optimized for your network and will give you best cell reception, speeds, and potentially support VoLTE, etc.
or do you care more about timely security updates, and potentially support of services not available in your original firmware.
If it's the latter, than you may consider flashing a different region's firmware.
That changes a when dealing with the US market (and some others)
In the US, the big carriers (Verizon, AT&T, T-Mobile, Sprint) actually implement hardware (and / or low level firmware) changes directly with Samsung.
Aside from the obvious changes (using SD820 instead of Exynos 8890) the cellular modem (and supporting software) are completely different and the carriers add specific software to optimize its services and offer advanced features (besides filling your phone with tons of bloatware and taking forever to certify new builds)
So as a US AT&T customer, you will not get any advanced features (HD Calling, Wifi calling) regardless of which firmware region you use. In that case, using XSA or BTU have no downside to them.
The only way to get these advanced features is to get an unlocked SD820 variant (SM-930U) and flash AT&T's (or you respective carrier's) CSC on it (using TWRP) but that means using 3rd party ROMS and manually updating your phone. (and tripping knox).
Click to expand...
Click to collapse
Excellent information, that was exactly what I needed to know. I went into this knowing I wouldn't have all the features I could but I have what I want and need. I was using a nexus 6P prior so none of them were available to me before. I'll grab the BTU firmware and flash that.
Thank you for this detailed and concise answer! This is exactly the kind of information that I have been looking for to help me make a decision on whether to get this device or not!
I'm on AT&T now and wanted the unlocked bootloader in order to use custom recovery (TWRP), which is why I was looking at the Exynos variant of the S7 in the first place. But after reading your explanation, it seems like far too many tradeoffs to make the purchase worthwhile for me.
Hi folks,
I've got the US LTE original Shield tablet, which is the replacement that NVidia sent me for my original "pyro edition" tablet. Since ATT haven't released the Nougat (Android 7, software package 5.0 or 5.1) builds for this tablet, but the ROW tablets are able to get this update, I flashed my tablet using adb/fastboot with the full ROW 5.0 package downloaded from the NVidia site. I then connected to WIFI, and let it pull down the 5.1 update. Factory reset, flash TWRP, rooted with SuperSU. Easy peasy. Then I set up the tablet with my accounts and such.
Based on good info from user @Son-j I made two build.prop edits, changing ro.build.flavor to wx_na_do-user (was wx_un_do-user) and ro.product.name to wx_na_do (was wx_un_do). This changed the reported signal type from H+ to 4G. Unfortunately I'm having trouble finding the thread where he suggested doing this. I think it was on the geforce web forum.
The only problem I've found so far is that I'm not getting LTE speeds. I was in Chicago for a couple days, in an area with strong LTE signal, and my other devices were reporting LTE and getting ~20Mbps down / 10+ Mbps up. My Shield was pulling maybe 8 Mbps down at best , and 1-2 Mbps up. At home in my suburban location, the difference is negligible (most devices here do 5 Mbps down / 1 Mbps up, LTE or 4G).
Still, I'd like to fix this if possible. Are there further edits or flashings that will let my US device running the ROW build get LTE? I have gone in and verified that my APN settings are the recommended ones from ATT. These showed up automatically, and matched the ATT recommendations.
Thanks in advance!
Hi I'm not sure but I there was a thread here in XDA that says it's still difficult to change the LTE (RoW to US, and vice versa) bands because developers couldn't find yet which part of the code to modify... It's not also confirmed if it is indeed possible to change the LTE bands to support.
So basically, flashing RoW LTE on US LTE device will still result in US-LTE supported bands. That's what I understood.
But what you did is quite a revelation. Can anyone else confirm that modifying the build prop will work? Boy I'm excited!
Son-j said:
Hi I'm not sure but I there was a thread here in XDA that says it's still difficult to change the LTE (RoW to US, and vice versa) bands because developers couldn't find yet which part of the code to modify... It's not also confirmed if it is indeed possible to change the LTE bands to support.
So basically, flashing RoW LTE on US LTE device will still result in US-LTE supported bands. That's what I understood.
But what you did is quite a revelation. Can anyone else confirm that modifying the build prop will work? Boy I'm excited!
Click to expand...
Click to collapse
Hi @Son-j -
Thanks! Do you happen to remember which thread had those two buildprop edits? I found them after seeing a post from you a few days ago, but now I can't find it at all. My google mojo has fled me.
I'd like to have a link there so others can see the original source.
It would be nice to get LTE speed, if someone knows how, but most places where I use the tablet don't have super fast LTE, so the difference for me isn't enough to make me downgrade to the marshmallow US LTE build. I'll stick with nougat for now, and hope eventually to get full speed. Who knows, maybe ATT will eventually release the 5.1 US LTE build...
For clarity here is the set of APN settings I'm using. I'm going with the column in the center at the bottom for Tablets:
https://www.att.com/esupport/article.html#!/wireless/KM1062162
All of this was correctly entered by default except I did need to edit two keys:
APN was listed as broadband instead of Broadband (yes, I'm picky, but wanted to match case)
APN type was listed as just default. I edited it to match the listed setting of: default,mms,supl,hipri,fota
Also I'm set to LTE for "Preferred network type"
Ok I think there's a misunderstanding. Uhm, I'm trying to look for the related posts here at the Nvidia threads but it seems to have disappeared.
Just to set something straight, LTE speed is influenced by:
1. LTE device with specific supported LTE bands
2. LTE sim
3. Location with LTE signals
I take it that for your specific device - US LTE Shield Tablet (just like mine) - you satisfy all 3.
For the record, flashing RoW LTE on our US device won't change the supported LTE bands (check baseband code in About Tablet section of settings). So if you used to have AT&T LTE speeds/signals using US LTE ROMs, it shouldn't change if you flashed RoW LTE ROM on the same device.
We are speculating though that there might be a way, software/firmware speaking. We are hoping it's not hardware-baked.
Son-j said:
Ok I think there's a misunderstanding. Uhm, I'm trying to look for the related posts here at the Nvidia threads but it seems to have disappeared.
Just to set something straight, LTE speed is influenced by:
1. LTE device with specific supported LTE bands
2. LTE sim
3. Location with LTE signals
I take it that for your specific device - US LTE Shield Tablet (just like mine) - you satisfy all 3.
For the record, flashing RoW LTE on our US device won't change the supported LTE bands (check baseband code in About Tablet section of settings). So if you used to have AT&T LTE speeds/signals using US LTE ROMs, it shouldn't change if you flashed RoW LTE ROM on the same device.
We are speculating though that there might be a way, software/firmware speaking. We are hoping it's not hardware-baked.
Click to expand...
Click to collapse
Thanks Son-j. It kind of freaks me out that just a week ago I found the thread that recommended those two changes in buildprop, but now I can't find it, and apparently neither can you! So maybe I'm not crazy, since it's more than just me having problems finding it.
Anyway, yes, I used to get the LTE indicator on the tablet, when in an area that has decent reception of those bands. At my workplace, which is a building built like a Faraday cage, we can get only ATT service, via repeaters spread throughout the building (I switched from Verizon in part due to this). Phones almost always report ~3 bars of LTE in places I usually find myself within the building. However, speeds tend to be <10 Mbps (tested using Speedtest.net from either my phone or tablet). So, despite getting "LTE service" there (prior to my software update), the speeds were nothing so great. For this reason, I'm not TOO worked up that my US tablet running ROW software isn't reporting LTE... most places where I use the tablet don't have blazing fast LTE, and the difference between the 4G service it actually gets and the LTE it "used to get" is not that great.
I would like to fix the problem if possible, but it's not a critical thing, and I may just put it on the back burner until the US LTE 5.1 image comes out, then flash back to that. I've got lots of other fish to fry these days.
Always interesting discussion. Thanks Son-j!
Marc
If it's just a speed issue, that will be the provider's end. If it's a signal issue, that's device problem.
It's possible to get an LTE signal but with HSPA speed in some areas.
There is an app called LTE Discovery. It will tell you which band it is currently connected to. I've got it on my tablet on T-Mobile. I am having problems with it connecting to anything other than 3G. But I have read others with the Shield tablet having similar problems with T-Mobile.
Sent from the Delta Quadrant using Tapatalk
caseyatbt said:
There is an app called LTE Discovery. It will tell you which band it is currently connected to. I've got it on my tablet on T-Mobile. I am having problems with it connecting to anything other than 3G. But I have read others with the Shield tablet having similar problems with T-Mobile.
Sent from the Delta Quadrant using Tapatalk
Click to expand...
Click to collapse
Thanks @caseyatbt,
I was unaware of that app. I downloaded it on my phone (which gets LTE just fine at my house, most of the time) and it reports all kinds of fun stuff about the LTE signal it's connected to. On the US Shield tablet running ROW stock, this is what I get, which frankly makes me think the tablet is connecting via CDMA of all things, despite having chosen all the correct options in the Settings / Mobile section:
The fact that my radio seems to be connecting to WCDMA instead of GSM is kinda freaking me out, folks.
I'm tempted to try flashing the US LTE device Marshmallow recovery image, and see if that fixes it. I understand the flashes don't change the baseband, but since I flashed 5.0 and the the device did an OTA update to 5.1, that might have changed the baseband, eh?
So, if me flashing the marshmallow files doesn't fix it, I might reflash an earlier edition and let it OTA to latest edition, which presumably would install correct "latest" baseband for the model.
We'll see ... I'm still not committed to one direction or another.
Marc
OK, I just flashed the 4.4.0 version of Marshmallow. (full flash of all Nvidia recovery image files). After letting it reboot the first time, it checked for update and found none, as expected.
NO LTE. Downloded the LTE Discovery app, and it still only sees WCDMA signals. Uggh.
Now I'm going to install the 4.3, and let it OTA to 4.4, and hope that refreshes the modem/radio. If anybody is following this, wish me luck!
EDIT: OK, I'm in idiot mode. I downloaded what I thought was the 4.3 US LTE image and it was actually the 4.3 ROW image. I didn't notice this until after flashing, and seeing the H+ icon, and noticing lack of ATT usage tracking app. Oops.
I don't see the 4.3 US LTE image on the site; I'm now downloading the 4.1 image, and will do OTA updates from there, checking as I go how which signal my radio is getting.
No Joy.
I flashed US LTE 4.1 image. AFter the flash, LTE Discovery still reports just HSPA+ signal from WCDMA towers. I then let it take the OTA for 4.4... the latest available for the US LTE tablet, and after it ran through its update process, I'm still on WCDMA.
Uggh. I doubt there's any WCDMA signal where I work so I may have killed my tablet, at least as far as using it at work is concerned.
I'm sure there IS a path back, I just can't imagine what it might be, at the moment. I'll start a new thread to be more specific to this current problem.
Sigh.
Frankenscript said:
Thanks Son-j. It kind of freaks me out that just a week ago I found the thread that recommended those two changes in buildprop, but now I can't find it, and apparently neither can you! So maybe I'm not crazy, since it's more than just me having problems finding it.
Click to expand...
Click to collapse
Eventually found that thread with the buildprop changes, see here if interested or if you ever need to find it.
I just checked my Shield on T-Mobile. In the same area on LTE Discovery that yours says W-CDMA mine says the same thing (under Neighbor Cells). When you scroll to the bottom, what does it say for carrier?
Carrier: AT&T (310410)
caseyatbt said:
I just checked my Shield on T-Mobile. In the same area on LTE Discovery that yours says W-CDMA mine says the same thing (under Neighbor Cells). When you scroll to the bottom, what does it say for carrier?
Click to expand...
Click to collapse
Here are screen shots of my sim status (personal details redacted) and the LTE discovery window:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
caseyatbt said:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
Click to expand...
Click to collapse
I talked to ATT. It's sort of their backup network, not available everywhere. My other devices definitely show LTE. Will post a screen so from my phone a bit later which shows that.
Sent from my LG-D851 using Tapatalk
caseyatbt said:
I am thinking that it is possible that W-CDMA doesn't mean what we think it means. It shows you connected to AT&T so you are not on someone elses network.
Click to expand...
Click to collapse
Here are some pictures taken from my phone, which is working properly. In settings, you can see the LTE network type and in the LTE Discovery app screen capture, all the LTE towers.
ATT maintains a "vestigial" WCDMA to allow some level of connectivity by devices that don't have GSM/LTE, but it's not everywhere and it's pretty slow.
The Shield used to show LTE in the Settings Cellular network type, as well as giving the LTE icon, when appropriate. Now it's just HSPA. Sigh.
Frankenscript said:
Here are some pictures taken from my phone, which is working properly. In settings, you can see the LTE network type and in the LTE Discovery app screen capture, all the LTE towers.
ATT maintains a "vestigial" WCDMA to allow some level of connectivity by devices that don't have GSM/LTE, but it's not everywhere and it's pretty slow.
The Shield used to show LTE in the Settings Cellular network type, as well as giving the LTE icon, when appropriate. Now it's just HSPA. Sigh.
Click to expand...
Click to collapse
My T-Mobile phone shows similar to your phone with LTE. T-Mobile must have a similar vestigial WCDMA that is showing up on my tablet. I still haven't found anyone that was able to get T-Mobile LTE working after it was only giving them 3G and HSPA. I have heard it either worked or it didn't.