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...
I saw that the Binaries for GSM/LTE were posted, but didn't see anything for CDMA. I can't find the thread now, but I recall reading a post where somebody mentioned that AOSP ROMS wouldn't be fully functional on N5 phones on Sprint's network. Does anybody know what I'm talking about? If you do, please elaborate. I want to slap on AOKP or CM 11 once they are available. Since this is a Triband device, I hadn't consider AOSP ROMS would be an issue using Sprint.
It's disappointing isn't it ? Developers ignoring a genuine question because the lot if then don't care about CDMA even though it's a nexus and their supposed to improve upon the device and they completely alienated sprint users on aosp Roms. They refuse to even acknowledge LTE not working on aosp roms and don't even treat it as a bug.
mhsbrian said:
It's disappointing isn't it ? Developers ignoring a genuine question because the lot if then don't care about CDMA even though it's a nexus and their supposed to improve upon the device and they completely alienated sprint users on aosp Roms. They refuse to even acknowledge LTE not working on aosp roms and don't even treat it as a bug.
Click to expand...
Click to collapse
I have had the ****s of CDMA anyhow -- I'm tired of the locked down mentality. I use Ting (and love their service), but they use Sprint as their backbone and, just once, it'd be nice if I could use any damn phone I want simply by popping in a SIM and adjusting the APN settings. I think I need to try a decent ATT MVNO for a while. I returned my nexus 5 and will try again in January. The audio issues caused by software and manufacturing goofs are unacceptable to me. I'm more than happy to switch to a GSM Gnex for now, to get away from CDMA.
Is there a list of AOSP ROMs that will allow full functionality on Ting (or any CDMA network, if they're all the same)? Are there viable alternatives?
On my Galaxy S3, I ran a Touchwiz-based ROM to work around the issue. I don't mind using the stock ROM for now, but I'd like to know if I should just look for a new MVNO that won't cause these headaches.
Hey guys, I think I know the answer to this but I wanted to ask those who might have a better idea...
I'm using an unlocked AT&T G3 on T-Mobile - the only difference radio-wise is the absence of one of the HSPA+ bands but I haven't noticed any difference in network speed, etc. Regardless, I want to flash a new ROM on this bad boy but I think I'm locked to the 850 development, right? I'm assuming that the restrictions in flashing a ROM for a different variant are due to hardware differences and not software/radio/carrier issues, right? Just want to make sure I'm not going to brick my new phone. Thanks!
RamosDevil said:
Hey guys, I think I know the answer to this but I wanted to ask those who might have a better idea...
I'm using an unlocked AT&T G3 on T-Mobile - the only difference radio-wise is the absence of one of the HSPA+ bands but I haven't noticed any difference in network speed, etc. Regardless, I want to flash a new ROM on this bad boy but I think I'm locked to the 850 development, right? I'm assuming that the restrictions in flashing a ROM for a different variant are due to hardware differences and not software/radio/carrier issues, right? Just want to make sure I'm not going to brick my new phone. Thanks!
Click to expand...
Click to collapse
Although I don't know for certain, I would tend to agree with your line of thinking here.
I am doing the same thing as op but I'm wanting a tmo stock ROM to be ported
Greetings,
I have a the above mentioned phone on the Sprint US network.
A friend of mine on Sprint recently got a letter stating that they will be shutting down their 4G WiMax while they do upgrades and focus on 4G LTE. It is a stupid question, probably, but will this impact my phone's ability to get 4G and/or LTE?
Also, I am running Cyanogen Mod 12.1... I saw before something about builds for ms8960 and then now it seems it is going back to xt879/c. I have been downloading the Cyanogen for xt897, is this the correct one for this phone? Because I also see a download for xt897c, but I do not know the difference... other than CM is at 10 for the C and 12.1 for the xt897.
Every new version I will wipe the phone and do a clean install of CM... I created a custom boot animation and flashed the bootlogo.bin, so I know how to use ADB and a little bit of the shell...
I am also wondering though, about this f2fs file system... I wiped the data and cache and gave every possible partition the f2fs. Then I read something about zcache not working correctly or not using f2fs? I'm a little confused. Can someone clarify this?
Sorry for so many questions but I can't find this info through the searches. Or rather I can't make sense of it either. If there is any other information for me to supply just ask, and I will gladly provide it.
Thanks in advance!
The Q is not capable of WiMax, so you have nothing to worry about.
As for your other questions, they are pretty much all answered in the CM thread.
arrrghhh said:
The Q is not capable of WiMax, so you have nothing to worry about.
As for your other questions, they are pretty much all answered in the CM thread.
Click to expand...
Click to collapse
Thank you sir! That is reassuring that I don't have to get a new phone come November. And that also means their 4G LTE coverage will be improved so I should have faster network speeds eh? And clearer calls? Will this phone be able to make "HD" calls using the LTE?
Sorry for the follow up but maybe I'm just dense as I didn't really ascertain the answers... could you point me to the right thread? I know there's the 12.1 and then the [Q&A]... would this be a better place to ask?
I'm also curious about the Mobile Networks settings. Is there a primer somewhere on this? I want to know what I should select as the preferred network type... I'm in the San Diego market and I want to make use of LTE when it's available but I only ever seem to get 3G... also I have data roaming and all that included so is it possible the you can have the phone elect to use another carrier's LTE if available over Sprint's 3G? Does it matter which option I select in the preferred networks list - i.e. if I pick something with GSM and the phone doesn't do GSM will it ignore my preference and choose what works? I also don't know the difference between the CDMA Subscription RUIM/SIM vs. NV. I have seen the question asked but didn't find the answer.
Thanks again, any help is appreciated, even if it's just a link or something general. I just want to do the best to get the best network experience with this phone.
Thanks!
nasch007 said:
Thank you sir! That is reassuring that I don't have to get a new phone come November. And that also means their 4G LTE coverage will be improved so I should have faster network speeds eh? And clearer calls? Will this phone be able to make "HD" calls using the LTE?
Sorry for the follow up but maybe I'm just dense as I didn't really ascertain the answers... could you point me to the right thread? I know there's the 12.1 and then the [Q&A]... would this be a better place to ask?
I'm also curious about the Mobile Networks settings. Is there a primer somewhere on this? I want to know what I should select as the preferred network type... I'm in the San Diego market and I want to make use of LTE when it's available but I only ever seem to get 3G... also I have data roaming and all that included so is it possible the you can have the phone elect to use another carrier's LTE if available over Sprint's 3G? Does it matter which option I select in the preferred networks list - i.e. if I pick something with GSM and the phone doesn't do GSM will it ignore my preference and choose what works? I also don't know the difference between the CDMA Subscription RUIM/SIM vs. NV. I have seen the question asked but didn't find the answer.
Thanks again, any help is appreciated, even if it's just a link or something general. I just want to do the best to get the best network experience with this phone.
Thanks!
Click to expand...
Click to collapse
I would ensure everything works network-wise on stock before flashing CM. If it doesn't work on stock, get the provisioning etc sorted before going to CM.
arrrghhh said:
I would ensure everything works network-wise on stock before flashing CM. If it doesn't work on stock, get the provisioning etc sorted before going to CM.
Click to expand...
Click to collapse
Thank you and that's good advice my friend, but the horse is waaaaayyy outta the barn on that one. I've been using CM now since 10. Now on to 12 which is going ok. Has its issues but most of the time (when at home or near a reliable LTE signal) things work alright!