Related
OKAY so I decided to update this thread:
There are two versions of the One X. One with aws bands and one without. I have a device without AWS (I am about 80 % sure). There are reports of people getting 4g on AWS with the Rogers Version as of now, and more testers need to check it out as it could still be possible on ATT.
This flash here theoretically could enable the One X radio to lach onto AWS (The radios here are for the One S Ville.)
http://ville.giev.de/?page_id=42
I have flashed all three, and although I did not get 4g, I got faster ping and a near immediate connection onto T-mobile. To all the people saying this will "brick" the phone, it does not and you have nothing to worry. But as always make sure to do a backup. The radio hacks for the Skyrocket/Note were also based on flashing the Galaxy S2 radio directly on top. This should work the same.
I'm interested in this as well. What does is involved and the risk? I don't have warranty on my phone, so I'm a little bit leery in being first.
ver2go said:
I'm interested in this as well. What does is involved and the risk? I don't have warranty on my phone, so I'm a little bit leery in being first.
Click to expand...
Click to collapse
if your rooted ull should be fine just make a back up of ur current set up. this is just a clockwork flash, it may not even flash, but if it does then there's a high chance of 4g.
i've done radio hacks before for the droid 3/skyrocket/note all from a similar concept. ex. flashing the t-mobile galaxy s2 radio on the note, to enable 4g.
if anyone could provide me with a better solution for an unlock i am sure i can get this to work. seems that the htc unlocker server is down right now
it's the same thing as flashing different radios via clockwork posted in the One X android dev forum
I'll give it a try, hopefully it won't mess anything up. So I just flash the radio in recovery. If no good, I just flash the correct radio again?
There is a one click no HTC Dev bootloader unlock in the Dev forum.
http://forum.xda-developers.com/showthread.php?t=1734558
---------- Post added at 07:57 PM ---------- Previous post was at 07:25 PM ----------
I flashed:
Radio from RUU_Ville_U_HTC_Europe_1.78.401.2 [Recommended] (update by rhcp)
0.16.31501S.17_2_10.23.31501S.10L
From your link. It flashed correctly. The phone on data and voice still works. I confirmed the version in Settings is not my original:
0.17.32.09.12_10.86.32.08L
I'm still on Edge, but I'm in a crappy cell area, so still not certain if radio or my area. I might give the:
Radio from Stock T-Mobile US (update by rhcp)
0.16.31501S.02_10.18.31501S.08L
Radio a try too.
good to hear no negative results got my phone unlocked so i will be testing tonight. also do u guys have the newer sims or older ones?
I have an older sim I believe. It is one that came from an activation kit I bought off ebay. I tried the T-Mobile radio and same results, still on Edge, but still could be my location.
What in gods name are you guys doing! ? Are you trying to brick your phones? It's already been confirmed that the hardware on this phone does not support the proper bands for T-Mobile 3g!
seh6183 said:
What in gods name are you guys doing! ? Are you trying to brick your phones? It's already been confirmed that the hardware on this phone does not support the proper bands for T-Mobile 3g!
Click to expand...
Click to collapse
Prove it. Why would the phone soc be any different than the one s one.
Sent from my HTC One X using xda premium
ECEXCURSION said:
Prove it. Why would the phone soc be any different than the one s one.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
It's not just the SOC that determines hardware compatibility. There are various radio amplifiers and filters which are tuned to the specific frequencies that the phone is likely to encounter. If a phone is going to be sold in multiple markets, sometimes the hardware filters are set up for all frequencies and some are disabled via software, but often times this is not the case.
It's not impossible that a radio reflash can make it work, though highly improbable.
sassafras
Interested in this. There might be better luck flashing the tmo radio since I don't think any European operators use AWS bands, correct me if I'm wrong.
Can anyone explain why flashing this radio from a different device won't brick our phones?
tspx23 said:
good to hear no negative results got my phone unlocked so i will be testing tonight. also do u guys have the newer sims or older ones?
Click to expand...
Click to collapse
I have a tmobile one s, but i also have the one from att and i am so interested on using this phone over tmobile 4g let me know if i can of help. I am using my micro sim that came with the one s and i am getting edge (asume its the latest from tmobbile 4g mucro sim. I am on 1.85 rooted but i did not unlock. though i am sure we can flash through CWM. any ways i am sure there is a way out to get 3g or 4g on the one x on tmobile did not find the way yet.
flashed both of the t-mobile modems no luck for me either, although my ping is significantly higher and connects to t-mobile a LOT quicker.
does anyone know how to edit the LTE settings. it is odd but for most ATT LTE phones they have the 1700mhz frequency i think it would be a matter of just defaulting that....
the radios also show up in my baseband so i have successful flashes
EDIT: one more thing, before i was not able to use data at all considering i had the newer t-mobile sims but now data works but on edge speed.
danada said:
Interested in this. There might be better luck flashing the tmo radio since I don't think any European operators use AWS bands, correct me if I'm wrong.
Can anyone explain why flashing this radio from a different device won't brick our phones?
Click to expand...
Click to collapse
it's just a file in your system. it could potentially brick your phone but you can always get into recovery and restore. which is why i stated you should create a back up of your device before trying it out.
however, i was fairly certain it wouldn't do that because the internals of the One S/One X are nearly identical, they both share the same processor and most likely similar (if not same, radios).
either way, the the radios work, getting me higher ping, and working data without having to switch out my sim for an older one, hope there is a way to activate the 1700 band !
http://www.gsmarena.com/htc_one_x_at&t-4614.php
EDIT 2: apparently there are two models of the ATT One X/XL one with the 1700 band and one without
tspx23 said:
flashed both of the t-mobile modems no luck for me either, although my ping is significantly higher and connects to t-mobile a LOT quicker.
does anyone know how to edit the LTE settings. it is odd but for most ATT LTE phones they have the 1700mhz frequency i think it would be a matter of just defaulting that....
the radios also show up in my baseband so i have successful flashes
EDIT: one more thing, before i was not able to use data at all considering i had the newer t-mobile sims but now data works but on edge speed.
Click to expand...
Click to collapse
Likely the software has been changed to support T-Mobile, but the hardware (filters, amplifiers, etc) are non-existent, so you'll never get actual 1700 MHz AWS support.
Of course, this is just a 50,000 foot view perspective without actually trying it myself.
sassafras
sassafras_ said:
Likely the software has been changed to support T-Mobile, but the hardware (filters, amplifiers, etc) are non-existent, so you'll never get actual 1700 MHz AWS support.
Of course, this is just a 50,000 foot view perspective without actually trying it myself.
sassafras
Click to expand...
Click to collapse
you might be right about this one but there are certain One X/XL's that do have the 1700 band found out through some searching and trying to figure out the reason behind it.
If that's correct.... the people with the 1700 band would have 4g when they flash this radio! also use *#*#4636#*#* to change network type to lte/gsm
--- for other phones though like the Skyrocket/Note they were directly compatible with T-mobile radios.
Okay, I flashed the Tmo One S radio and did not receive a brick. What I did receive is a not-so-good connection that will switch between HSPA+ and 3G quite often.
I don't have a WIND sim to test with, but I tried running AT commands on my phone and they don't seem to be working. I tried doing a network scan with AT+COPS=? waited forever and had nothing displayed.
Strange...
--edit--
Rebooted and ran the commands again. Still don't see any AWS carriers.
uid=0 [email protected]:/ # +COPS: (1,"CAN Rogers Wireless Inc.","ROGERS","302720",7
),(2,"ROGERS","","302720",2),(1,"CAN Rogers Wireless Inc.","ROGERS","302720",0),
(1,"","","302220",2),(1,"","","302610",2),(1,"","","302610",7),(1,"","","302220"
,7),,(0,1,2,3,4),(0,1,2)
Click to expand...
Click to collapse
danada said:
Okay, I flashed the Tmo One S radio and did not receive a brick. What I did receive is a not-so-good connection that will switch between HSPA+ and 3G quite often.
I don't have a WIND sim to test with, but I tried running AT commands on my phone and they don't seem to be working. I tried doing a network scan with AT+COPS=? waited forever and had nothing displayed.
Strange...
--edit--
Rebooted and ran the commands again. Still don't see any AWS carriers.
Click to expand...
Click to collapse
Don't you need a wind sim to connect im pretty sure the Canadian version will work on aws
Confirmed on my end that even with the T-Mobile radio, I'm not getting HSPA+. Even when I drove by the Moscone center where 1900Mhz was refarmed during Apple's WWDC (maybe it was just that day?). I was hoping this would be like the Note and Rocket where I can flash different radios.
Any other new phone capable of this? The S III? If not, I may have to either wait for 1900MHz refarm or switch to Straight Talk.
ver2go said:
Confirmed on my end that even with the T-Mobile radio, I'm not getting HSPA+. Even when I drove by the Moscone center where 1900Mhz was refarmed during Apple's WWDC (maybe it was just that day?). I was hoping this would be like the Note and Rocket where I can flash different radios.
Any other new phone capable of this? The S III? If not, I may have to either wait for 1900MHz refarm or switch to Straight Talk.
Click to expand...
Click to collapse
Picking up an att s3 today to test it out. Most likely there's two versions of one x one with aws and one without. I know mine doesn't though.
tspx23 said:
Don't you need a wind sim to connect im pretty sure the Canadian version will work on aws
Click to expand...
Click to collapse
I'm not exactly sure of this one.
If someone is willing to let me cut up their WIND sim (or lend me their WIND microsim), I'll re-flash the tmo radio and meet you somewhere to test it (Toronto, please).
~dan
-----edit-----
Just popped in an old WIND sim that I used to test AWS connectivity at first. Saw WIND Away with the standard radio, and after flashing the Tmo radio I see WIND Away and AT&T (AT+COPS=? shows Rogers, ATT, Telus, Bell).
I live by the lake, that would explain why ATT shows up.
-----edit again-----
Check this out http://imgur.com/Nb984,rUvM6. Not using the One S radio...
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...
As the title says, I am on Sprint and looking at the Network Mode options. LTE seems like the obvious choice since Im stuck here in the US. But, tell me if I am wrong or what the advantages/disadvantages are of both settings.
Mindspin_311 said:
As the title says, I am on Sprint and looking at the Network Mode options. LTE seems like the obvious choice since Im stuck here in the US. But, tell me if I am wrong or what the advantages/disadvantages are of both settings.
Click to expand...
Click to collapse
Best to leave it on global, it will usually revert anyway ,if you change it to lte
sent from my HAMMERHEAD neXus
Also, is it known that the N5 cannot handle a call and still keep LTE data going at the same time?
Mindspin_311 said:
Also, is it known that the N5 cannot handle a call and still keep LTE data going at the same time?
Click to expand...
Click to collapse
No carriers have voice on LTE. I know that on T-Mobile, my Nexus 4, Moto X and IPhone 5 all revert to HSPA+ when I get a call. They will go back to LTE at some point afterwards.
I'm wondering what the actual difference is between LTE and Global. So here is what I did. First, I set it to LTE Preferred and unlike what was said earlier in this thread and by others on the internet, it did not reset on boot, it stayed at LTE. I check the info menu and it said LTE/CDMA as the option. I then set it back to Global, and then rechecked the info menu, it is now LTE/GSM/CDMA. I'm betting that if I move him over to T-Mobile from Sprint that Global will stay the same but that LTE Preferred will likely then say LTE/GSM like my Nexus 4 does.
Just thought this might help folks. I would think that LTE Preferred is just fine for someone using Sprint in the US but that you'd want Global if you were traveling and getting a local SIM.
peterb
I know this may be a bit of a thread resurrection but I think it might be related to some of issues that peeps are now seeing on the Nexus 6 devices with Sprint
Also a good read on Sprints triband setup / issues (yea the article may be dated now but still relevant)
http://s4gru.com/index.php?/blog/1/...-due-to-circuit-switched-fallback-technology/
Is it really at&t I have to blame for no marshmallow on my tablet?
I have grown so irritated with the lag behind updates with every single phone I have owned in the past 8 years or so.
But this tablet was bought unlocked! Why does at&t have a say in when I get the update? They have 0 bloatware to inject onto this thing.
And why now? Every other update was prompt along with the WiFi version.
I know y'all probably have no idea what the hold up is I just needed to vent. Peace!
Sent from my SHIELD Tablet using Tapatalk
Yeah... I'm just as frustrated as you mate.
No MM on the LTE version because AT&T hey.. FFS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
I see there is a ROW (rest of world) LTE rom out. Is there a way we can just flash that (without being routed?)
This may sound like a silly question, but did you buy it from At&T directly? did you buy it used? is it the first y01 battery? The US LTE rolled out nearly two weeks ago and I'm in Canada! Currently using the US LTE b01 version received from Nvidia.
I manually flashed the ROW LTE version at first with no problems at all, then a week or so after I got the US LTE marshmallow update. Flashed it like normal and all is well.
Clselfridge said:
Is it really at&t I have to blame for no marshmallow on my tablet?
I have grown so irritated with the lag behind updates with every single phone I have owned in the past 8 years or so.
But this tablet was bought unlocked! Why does at&t have a say in when I get the update? They have 0 bloatware to inject onto this thing.
And why now? Every other update was prompt along with the WiFi version.
I know y'all probably have no idea what the hold up is I just needed to vent. Peace!
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
kyleruggles said:
This may sound like a silly question, but did you buy it from At&T directly? did you buy it used? is it the first y01 battery? The US LTE rolled out nearly two weeks ago and I'm in Canada! Currently using the US LTE b01 version received from Nvidia.
I manually flashed the ROW LTE version at first with no problems at all, then a week or so after I got the US LTE marshmallow update. Flashed it like normal and all is well.
Click to expand...
Click to collapse
I bought the first one from amazon and then it was recalled and this is the replacement that I have now. It wasn't used as far as I know. And I don't buy anything but service from at&t anymore.
Still everytime I check for an update it says your tablet is up to date. Still running lollipop.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Same story here. Not using ATT sim though, I use a vmno Consumer Cellular instead. No update on replacement tablet here.
Sent from my SHIELD Tablet using Tapatalk
I bought the LTE version from Amazon too, using it in Australia on Vodafone 4G network. Came with AT&T sim but never used it. Mine was replaced by Nvidia in the battery recall saga.
Can you flash the ROW LTE rom through the stock recovery?? Any help much appreciated
---------- Post added at 12:02 PM ---------- Previous post was at 11:54 AM ----------
Does anyone have the stock US LTE marshmellow OTA and can post it or a link to it here?
Still nothing. Android N will be here before this tablet gets M at this rate...
Sent from my SHIELD Tablet using Tapatalk
I'm still waiting for mine as well. Got it on Amazon and it was replaced in the recall.
As an alternative to waiting, you could check the VulKan Preview thread where there is a link to the US LTE for that (which is actually a later build than the 4.0.1 A6.0 as it is A6.0.1).
zarish said:
As an alternative to waiting, you could check the VulKan Preview thread where there is a link to the US LTE for that (which is actually a later build than the 4.0.1 A6.0 as it is A6.0.1).
Click to expand...
Click to collapse
I have seen that. Seems interesting. Might check it out at some point.
I don't mind waiting. I just wish they laid out a timetable like some of these other oem's. At least HTC and Samsung both have a (ever changing)roadmap that you can check the status of your devices update.
Sent from my SHIELD Tablet using Tapatalk
kyleruggles said:
This may sound like a silly question, but did you buy it from At&T directly? did you buy it used? is it the first y01 battery? The US LTE rolled out nearly two weeks ago and I'm in Canada! Currently using the US LTE b01 version received from Nvidia.
I manually flashed the ROW LTE version at first with no problems at all, then a week or so after I got the US LTE marshmallow update. Flashed it like normal and all is well.
Click to expand...
Click to collapse
Wait is that the Vulcan update that you are referring to or some other?
Nah no Vulkan update, since I had installed the ROW LTE version to get it asap, a few weeks later I got the US LTE update in the Nvidia Shield Update page, I updated it and now back on US LTE version. You can flash the ROW on top of the US version, no issues, may have some LTE bands missing but with my tests in Canada, I had a pretty decent speed of 8mbit/5mbit over LTE.
Dedren said:
Wait is that the Vulcan update that you are referring to or some other?
Click to expand...
Click to collapse
kyleruggles said:
Nah no Vulkan update, since I had installed the ROW LTE version to get it asap, a few weeks later I got the US LTE update in the Nvidia Shield Update page, I updated it and now back on US LTE version. You can flash the ROW on top of the US version, no issues, may have some LTE bands missing but with my tests in Canada, I had a pretty decent speed of 8mbit/5mbit over LTE.
Click to expand...
Click to collapse
How did you manage to flash the RoW rom? I don't see any flashable zips available.
I have not been able to get an MM update for my US LTE either. I'm using an RMA replacement for the one they shipped me for the battery recall.
pyro9219 said:
I have not been able to get an MM update for my US LTE either. I'm using an RMA replacement for the one they shipped me for the battery recall.
Click to expand...
Click to collapse
That's because the MM update is being held up by AT&T for the US LTE model.
To work around this, one can flash the RoW image instead. The tablet will from now on receive timely OTA updates and AFAIK, there are no repercussions as the US LTE modem firmware files are included with the RoW image. Basically you now have an AT&T crapware-free tablet!
Isira said:
That's because the MM update is being held up by AT&T for the US LTE model.
To work around this, one can flash the RoW image instead. The tablet will from now on receive timely OTA updates and AFAIK, there are no repercussions as the US LTE modem firmware files are included with the RoW image. Basically you now have an AT&T crapware-free tablet!
Click to expand...
Click to collapse
Whats the best way to flash this on the Shield Tab? Mine is stock unrooted.. Cheers
W. T. F. !! Can not believe the US LTE is still not getting updated...
Sent from my SHIELD Tablet using Tapatalk
Isira said:
That's because the MM update is being held up by AT&T for the US LTE model.
To work around this, one can flash the RoW image instead. The tablet will from now on receive timely OTA updates and AFAIK, there are no repercussions as the US LTE modem firmware files are included with the RoW image. Basically you now have an AT&T crapware-free tablet!
Click to expand...
Click to collapse
I have a stock unrooted tablet. I was hoping MM and a factory reset would fix the couple things I get irritated with without rooting. But I guess if that's what I need to do...
Sent from my SHIELD Tablet using Tapatalk
How exactly do you flash this RoW LTE MM Image? The thread was a little confusing.
You can just download the files from nvidia's site and do it fastboot flash everything. They provide clear instructions with the file. There was a RoW LTE flashable zip but the creator removed it. I used it and for some reason or another I couldn't get it to work w/ external SD card. So while the LTE worked, not being able to write on the external SD was a no go for me. Just using RR for now until they finally release the US LTE version and hopefully with external SD write issue fixed. Already tried all kinds of xposed modules but none worked.
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.