*** WARNING!! THESE SETTING ARE PRIMARILY FOR MOD DEVELOPERS OR FOR PEOPLE LIKE ME WHO CONSTANTLY RESET TO FACTORY DEFAULTS. WHILE THESE SETTING CAN BE APPLIED WITHOUT FACTORY RESETTING, IT IS A LITTLE MORE DIFFICULT -- YOU HAVE BEEN WARNED!! ****
**UPDATE** Great supplementary guide by Amil: http://www.amilkhanzada.com/2012/03/how-to-enable-select-network-on.html?m=1
Hello All! I'll get straight to the point.
I was playing around with some files, and noticed a bunch of configuration files in the '/system/etc/motorola/' directory. This directory is filled with custom setting that are applied after a factory reset. Here are some examples that I have played with:
File: /system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso:
Setting: - Enable the 'Unknown sources' check box (Allows you to install non-market apps)
Code:
force_only_market_apps=0
File: /system/etc/motorola/com.motorola.blur.setup/defaults.xml
Setting: - Allow you the option of bypassing the Motoblur setup altogether
Code:
<boolean name='ShowSkipSetupMenu' value='true'/>
File: /system/etc/motorola/com.android.phone/defaults.xml
Setting: - Unlocks the mobile networks, 'Select network' and 'Operator selection
Code:
<boolean name='network_select_menu' value='true'/>
jjwatmyself said:
I have completed a test and can confirm that "Use Wireless Network" check box is "agps and wifi positioning" controlled with one check box. I would argue that the suggested modification to display the AGPS checkbox is legacy feature and unneccasary. Exposing both check boxes in the GUI will most likely get the files out of sync that these check boxes write to. You can confirm that the "Use Wireless Network" check box enables agps by using maps over cellular data (3G required) with GPS and wifi turned off. You'll notice that maps will find your location. This is agps. While we are on the subject, the menu option with the "2G check box", has been replaced with the 'Select network' menu with 2G/3G/Automatic.
I kind of wish that the original posts would be updated as people are being mislead in this thread. The AGPS configuration does not need to be modified. In this situation, the stock settings are already optimized for agps, wifi and gps as well as the optimal server.
Click to expand...
Click to collapse
*** CONFIRMED NO IMPROVEMENT ***
File: /system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso:
Setting: - Enables the Assisted GPS option in the "locations and security" menu page
Code:
agps_feature_enabled=1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Here are some other interesting setting that I haven't had a chance to play with yet:
File: /system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso
Setting: - Unknown
Code:
dun_enable=1
Bluetooth_Dun_Enabled=true
Not sure what these do, but if you find out, please post it in this thread.
Thanks and I hope you all find these settings useful. Also, from my limited testing, the settings are only applied after a factor reset. This helpful for mod developers and those of use who that factory reset our devices often--the setting are automatically applied after a hard reset.
[size=+2]*** ADDITIONAL INFO ON HOW TO APPLY THESE MODIFICATION WITHOUT FACTORY RESETTING****[/size]
Great explanation provided by forum member jjwatmyself:
jjwatmyself said:
This is the Atrix, proof of concept for Enable mobile networks settings: 'Select network' and 'Operator selection' that are greyed out in 4.1.83.
FALSE
INCOMPLETE METHOD
Here is the complete method. I decided to post as I had some issues getting the described methods to work also.
Thanks to to mistadman and crnkoj and liranm2. My post is simply to join all of the items into a single method and provide information on what the resulting un-greyed settings do.
End result is that this method works flawlessly providing that all of the following steps are completed.
1) Edit the following files:
/system/etc/motorola/com.android.phone/defaults.xml
/data/data/com.android.phone/shared_prefs/settings.xml
/data/data/com.android.phone/shared_prefs/com.android.phone_preferences.xml
/data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
Setting:
2) When I initially tested, I found that the files would revert to their original state after rebooting, but on http://forum.xda-developers.com/showthread.php?t=1108181 member liranm2 states that YOU MUST DELETE THE BACKUP XML FILES THAT ROOT EXPLORER CREATES.
3) Reboot phone.
In summary, the above changes provide un-greyed options under Settings, Wireless & networks, Mobile networks as follows:
1) Select network
2) Operator selection
'Select network' provides the following options:
2G only = GSM only = lowest battery consumption, with slowest data speeds
3G only = WCDMA only = highest battery consumption, with fastest data speeds
Automatic = GMS auto (PRL) = medium battery consumption, with fastest data speeds when 3G towers are 'preferred' over 2G towers. This is based on what the towers advertise as being available. i.e. if a 2G tower has a stronger signal than another 2G/3G capable tower, then use 2G.
Automatic uses less juice becasue:
2G uses less juice
a stronger signal will yield lower transmit power consumption by the phone, i.e. don't force 3G if there is a stronger signal available at 2G.
'Operator selection':
Search networks = see all of the providers that your radio is compatible with, i.e. providers transmiting on frequencies your device supports.
Select automatically = will prompt every time your phone moves between different services that your provider offers that are not considered roaming.
On AT&T's network, using Any Cut to run Activity, GSM/UMTS Options provides a slight variation of the above menu. This can be used without modifying files. Instead we get a 'Use only 2G networks' check box which causes the phone to switch between GSM Only and GSM auto (PRL).
All of the methods described have the same result as dialing *#*#4636#*#*, then Phone Information, Set preferred network type. The acronyms shown on this menu most likely do not mean what you think they mean, hence the descriptions included in this post. Alternate method is to use Any Cut to run Activity and select Phone Information (thanks Vangelis13).
I'll post a link to this on the GingBlur thread to see if Ken will include these changes in his next version. My opinion is that having these settings would take the phone closer to a native build.
BTW Nice comments from crnkoj. Although I did not need to modify any settings.db files in any way, those files have some pretty interesting fields in them, just nothing that appears to be network_select_menu related.
Files listed below are for references purposes only. DO NOT MODIFY!!!
/data/data/com.andoird.providers.settings/databases/settings.db
/data/data/com.motorola.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
So the unlock mobile networks hack will basically unlock the phone to other networks? (Asking because I need to unlock my at&t phone to rogers)
Sent from my MB860 using XDA App
TheToiletSpaula said:
So the unlock mobile networks hack will basically unlock the phone to other networks? (Asking because I need to unlock my at&t phone to rogers)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
No this is not a sim unlock, it is supposed to allow you to select EDGE instead of HSPA+ however I was not able to get this to work after rebooting.
eheh sideload enable....nice =)
Unfortunately, you will have to perform a factory reset in order for the changes to apply. As I said before, this only works after a factory reset.
chria01 said:
No this is not a sim unlock, it is supposed to allow you to select EDGE instead of HSPA+ however I was not able to get this to work after rebooting.
Click to expand...
Click to collapse
basically there are even more hacks possible in the subdirectories of the /system/etc/motorola/ directory. Thers one for sms delivery notification aswell, and the max allowed number of sent MMS/SMS at once (to different recipients), thers more things in there that i dont even know what the parameters mean. As for some of the hacks the values are being duplicated in /data/data/ and than com.each.particular.setting at first boot (ie when the phone is new, factory restored or sbf flashed) and is than maintained there, so even if you would change some of the settings in /system/etc/motorola/ it might not have an effect until you either factory restore (which is mega unconvenient) or go to the respective directory in /data/data/ and edit (mostly the files are saved in settings.db in those directories) the values in the settings.db there. by cleverly modifying those in the /data/data/bla bla and putting in read only tags into the settings.db you can in fact modify some things that are at times rather bothersome.
mistadman said:
Unfortunately, you will have to perform a factory reset in order for the changes to apply. As I said before, this only works after a factory reset.
Click to expand...
Click to collapse
you dont have to factory restore it as a matter of fact. just go to:
/data/data/com.android.phone/shared_prefs edit this file: _has_set_default_values.xml which is a duplicate of the one from the /system (the defaults.xml) and write true in it, reboot and voila you have 2g/3g selector enabled.
crnkoj said:
you dont have to factory restore it as a matter of fact. just go to:
/data/data/com.android.phone/shared_prefs edit this file: _has_set_default_values.xml which is a duplicate of the one from the /system (the defaults.xml) and write true in it, reboot and voila you have 2g/3g selector enabled.
Click to expand...
Click to collapse
Crnkoj, you are absolutely correct! However, making changes there will be lost after a factory reset. The beauty of modifying the configurations via the '/system/etc/motorola' directory is that the changes will become permanent.
So modifying both locations would probably be best for those who don't factory reset as much as I do Thanks for pointing this out crnkoj. I should have mentioned this in my original post.
mistadman said:
Crnkoj, you are absolutely correct! However, making changes there will be lost after a factory reset. The beauty of modifying the configurations via the '/system/etc/motorola' directory is that the changes will become permanent.
So modifying both locations would probably be best for those who don't factory reset as much as I do Thanks for pointing this out crnkoj. I should have mentioned this in my original post.
Click to expand...
Click to collapse
yes i meant you have to change both and many are using gingerblur so a factory reset rather ****s up the phone, so thats a better solution than factory reset
I am not clear on this:
Change
/system/etc/motorola/com.motorola.blur.setup/defaults.xml
and
/data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
to be the same?
crnkoj said:
you dont have to factory restore it as a matter of fact. just go to:
/data/data/com.android.phone/shared_prefs edit this file: _has_set_default_values.xml which is a duplicate of the one from the /system (the defaults.xml) and write true in it, reboot and voila you have 2g/3g selector enabled.
Click to expand...
Click to collapse
doesn't work for me even though I changed at both places and did a reboot ..
ParrotSquawk said:
I am not clear on this:
Change
/system/etc/motorola/com.motorola.blur.setup/defaults.xml
and
/data/data/com.android.phone/shared_prefs/_has_set_default_values.xml
to be the same?
Click to expand...
Click to collapse
this line must be like that in both:
<boolean name='ShowSkipSetupMenu' value='true'/> value true cuz defualt is value false
hmm does any one know how to get motoblur back. I didnt turn it off using one of those methods im not even sure how my account got deleted but does anyone know if theres a way to get motoblur account back. none of my facebook contacts are syncing
Tried too changing in both files, and 2g/3g menu didn't appear!!
I never use mob net to access the web..
For motoblur account, if you intalled gingerblur, try restoring bloatware
Sent from my MB860 using XDA App
milesjohnson said:
hmm does any one know how to get motoblur back. I didnt turn it off using one of those methods im not even sure how my account got deleted but does anyone know if theres a way to get motoblur account back. none of my facebook contacts are syncing
Click to expand...
Click to collapse
I've gotten it back before when I disabled it doing the keypress during first boot. It prompted me again trying to do a software update, which I ended up doing as I was to lazy to use rsd
natboy said:
I've gotten it back before when I disabled it doing the keypress during first boot. It prompted me again trying to do a software update, which I ended up doing as I was to lazy to use rsd
Click to expand...
Click to collapse
Yeah I figure ill just sbf because Ihavebt found an easier way out
Sent from my Motorola Atrix using Tapatalk
awesome POST. thanks brother =)
BUT... it looks like my speeds are super similar with 2G enabled vs not... ? =/
I do believe on att network this option even if enabled, doesnt change your connection type...
So is there a way to enable the sideloading without using another method (ie sideloading wonder machine, gladenable) and without having to do a factory reset? Is there some other file we can edit that will enable it?
You need to be rooted, than you can change these settings/databases to enable sideloading.
I have been successfully using the Verizon FIOS remote control app to control my TV FIOS STB and it is much nicer to use than the standard IR remote.
To get it to work originally using a nightly (circa 128), I had to persuade the Nook that it had a phone number as this is registered against one set in the STB. I did this by going into Settings/Call Settings/Additional Settings. This gives a network or SIM card error but when OK'd allow me to manually enter a phone number which then worked fine and continued to work through many nightly updates.
Something has now changed (I am currently on nightly 200) as I find that I have to re-register the FIOS app almost daily to get it to work.
On checking I find that the Phone Number setting gets lost periodically and set back to Unknown and I have to manually enter it again.
Does anybody know whether CM7 behaviour has changed with respect to the storage of the Phone Number? I realise it would normally be on a SIM, but it does seem to stick around for quite a while on the Nook before getting lost.
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
dgibb2000 said:
Any luck with this? I've been trying to figure out a way to do this for a while. I am unable to set a number as you described as all settings are greyed out. I'm also on nightly 200+. Seems like there would be a system file we could edit to fake the number, or something like that. Was thinking about setting up a SIP account to try it, but I doubt that will work.
Click to expand...
Click to collapse
I have made some progress investigating this but have not got a final solution yet.
First, I can set my phone number up even though it is not a phone. I go into Settings, Call Settings, Additional Settings. The screen blurs and brings up a dialog box saying Call settings Error - Network or SIM card error. If I OK that then I see 3 menu items. The first 2 are grayed out but the 3rd "My Phone Number" is enabled. I select that and can enter a Phone Number. Are you saying you get the error and then all 3 options are grayed out?
Once entered I can view the Phone number via Settings, About Tablet, Status.
So far so good. The phone number setting does not normally survive a reboot, and also typically reverts to Unknown after a couple of days even without a reboot.
I have traced the Phone number setting to be stored in com.android.phone_preferences.xml which is in /data/data/com.android.phone/shared_prefs
But when the Phone number disappears it doesn't disappear from this file so there is some more complex interaction with trying to read a non-existent SIM first. So far I have traced the code involved to MyPhoneNumber.java and MSISDNEditPreference.java which are in the CyanogenMod-android_packages_apps_Phone-5d2764c.
I am still working on understanding this to see if there is some work-around to make the setting stick better. Currently I just have to check the phone number manually and set it again when it disappears.
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
dgibb2000 said:
Hmmm. When I go into call settings, all settings are greyed out except for internet call settings at the very bottom. I see the additional settings field you are speaking of but as its greyed out nothing happens if I click it. Weird.
Click to expand...
Click to collapse
Yes. That is strange. All my settings in Call Settings are enabled even though most are inapplicable. I don't think I have done anything to explicitly enable them and I'm on a standard Nightly 240 with the updated SystemUI.apk which turns off the phone signal bars. But I've never had these greyed out with any nightly build before.
Anybody else comment on whether their whole Call settings are enabled / disabled?
There is also a setting in build.properties in the system folder with a key called
keyguard.no_require_sim
I think this may have effect on how the OS treats calls which access the SIM. On my system this is currently set to 1. I might try playing with other values like true, 0 to see what effect that has.
Another theory as to why your call settings may be greyed out is that it they may get disabled in airplane mode.
Now this could be an issue even if you have set and subsequently cleared airplane mode as I believe the airplane mode setting doesn't go away entirely and can cause problems.
There is a command line way of clearing this setting completely which I did once when I set airplane mode on. Search for something like airplane sqlite to find the instructions.
That was it. I was stuck in airplane mode, and must have been for a long time. I used Android Assistant to clear the setting and it worked. I'm able to set my number and use fios mobile remote now! Thanks for your help.
Where did you get that updated systemui.apk to clear the cell signal bars? Now that I got the airplane mode off I have the signal strength there for no reason.
I got the SystemUI.apk from here
http://forum.xda-developers.com/show...60542&page=547
I just replaced the one in system/app. If you overwrite then you might get status bar forced close but a system reboot will sort that out and I haven't had signal bars since.
I've now put this in a zip that I can use to install after any nightly update I do as I've now found there is a wifi patch to deal with any remaining SOD issues although I haven't had one of those for a long time now.
Hopefully this stuff will get put into the main build before too long.
Looks like your link got clipped. Getting a page not found error.
Also, do you have any instructions on how to put the .apk into a zip for re-install after you do an upgrade? I'm assuming its not as easy as just ziping the file up?
Updated link
http://forum.xda-developers.com/showthread.php?t=960542&page=547
Yes. It is as easy as zipping the file up, but you have to create a matching folder structure to determine where the file goes. So in the case of the SystemUI file you create a folder called system containing a folder called app, put the file in the app folder and zip it so that system is in the root of the zip.
Correction: I thought that zip method was working but it wasn't. I had manually put the files in anyway and that worked OK. Then I was testing the zip, but it was actually failing.You need to put the files in a zip with the meta-inf etc. I think this link gives instructions
http://alldroid.org/default.aspx?g=posts&t=855
No. That doesn't work either as it uses an older method of scripting no longer supported. Apparently it needs to use Edify scripting now. It looks like some people add files to the gapps package, but I'm not clear yet whether it has to be re-signed, and I don't particularly want to redo gapps just to do this minimal patch.
I think I now understand how to produce an update zip that works.
I first took a gapp zip and stripped out all the existing files under system leaving the meta-inf alone. I put in the patch files in the appropriate folders under system. I then modified the updater-script in the meta-inf tree to just mount system, run package_extract_dir("system", "/system"); and unmount system with changes to the ui_print
I then signed the zip using the win-sign utility available here
http://forum.xda-developers.com/showthread.php?t=629151&highlight=sign+zip+files
I tried this out by first updating to nightly 246 and then applying my patch containing the SystemUI and the wifi driver that fixes SOD and that seemed to work OK.
Hi, as the title of the thread says I am trying to figure out how to edit certain settings via build.prop, rather than ##PROGRAM.
This is because of two things: I flashed my bionic to page plus, using the stock rom, then I installed Carbon ROM in slot1. To make 3G operate correctly, you have to change certain settings using ##PROGRAM. The stock rom works great after using the program menu. Unfortunately, the Carbon Rom, although fantastic, does not have this menu.
One of the settings is to change Sim type to 3G. The other is to set lte bppanic to disable. Then disable class 1 and class 2 apns.
If anyone knows how to do this, I would be thrilled, as would other Page Plus users, I imagine. Thanks.
Bump
This may be off by a long shot, but relating to radios..
http://www.droidrzr.com/index.php?/topic/22660-help-pls
typed on my Bionic
Hi, I think that is the right direction. However, so far I cannot find out how to change sim type to 3g or set lte bppanic to disable using a database.
There are similar "name" inputs there, like network mode, etc, but nothing indicating those exact settings. I wonder if I find the settings under the stock rom, can i import them into carbon? Or are they motorola-rom-specific?
I think that these are actually important questions for flashed users, and we will see this becoming more and more of an issue as 3G phones become obsolete, and the only way for a Page Plus or other Verizon MVNO user to have a workable smartphone is to flash a 4G one,
On the Bionic (and I imagine on other models), the only option for now will be the stock rom; any rom without access to the ##PROGRAM menu will be left short as far as advanced network settings goes. Of course, I think this might vary depending on how you flashed in the first place. I used a free tutorial that was quite simple.
chrisp6825 said:
This may be off by a long shot, but relating to radios..
http://www.droidrzr.com/index.php?/topic/22660-help-pls
typed on my Bionic
Click to expand...
Click to collapse
I honestly couldn't input much on this, as I've never had to dabble with this area ( well just once, quite a long time ago), but I'd imagine you could check out the data bases ( maybe take a "snapshot" or copy/download it) from a stock rom, make your changes using that ##program menu, then compare the new/changed database to the prior one.
That would be a quick way to detect if any values are being affected there, and where. Then you may as well check if those values exist on other roms, and try them out. Couldn't hurt, with safestrap/recovery backups and all.
typed on my Bionic
I believe that you should check out the setup for page plus on howard forums. It goes thru the changes to make the bionic 3g and turn off 4g completely. But the links to the apps and basic principles should still apply. Good luck, if you can't find it let me know. I'll send you a link.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
.
[size=+1]Use your phone anywhere[/size]
[size=+1]Have you ever wondered why your phone doesn't work nearly as well when you travel?[/size]
Or tried to change carriers only to be told that you'd need to buy a different version of your high end phone for it to work properly?
It's happened to a lot of us and there is no good reason for it. Other than greedy carriers that is.
Most phones should work on a lot more bands. And have good reception when roaming. The S5 in particular is one of the first phones that is fully capable of working on every GSM and LTE frequency in the world. So.. why doesn't it actually do that? Well because your carrier doesn't want to make it easy for you to leave. And because Samsung and other manufacturers want to force you to buy a new phone everytime you change telephone companies. So they put restrictions in your phone to limit how many bands you can use. Wouldn't you rather have your phone work on all carriers?
This guide will show you how to do that.
Okay okay, I'm convinced already.
I don't want to read any more. I'm a power user (or reckless).. just show me how to do the hack!
[size=+1]The lawyers made us do it[/size]
We have to post an obligatory warning
We don't think that this mod will cause you any problems. But we can't guarantee that.
You assume all risks if you proceed, including the risk that your phone might object, meltdown, brick or void your warranty.
[size=+1]Quick Start Guide[/size]
This mod makes a night and day difference when you travel, roam or change carriers. It's a dramatic improvement.
But it's not an easy, one click process. There are a lot of steps to add this to your phone.
And due to minor differences between brands (finding the hidden USB settings menu), it may take a little experimenting to succeed. So this mod won't be for everyone. But if you have some patience, you can add a lot of bands to your phone. Just post in the thread and we'll figure it out as we go. This Quick Start guide will show you how to add bands to a Samsung S5. It can also be used on dozens of other Samsung, Sony, LG, HTC, Nexus, etc phones with minor differences in the steps here. I'll add comments for other brands when I have them. If you get stuck anywhere, post in the thread for guidance.
[size=+1]The Mod:[/size]
Step by step guide
1. You need a phone with a Qualcomm processor that has been rooted.
2. If you need to root your phone, click on the button below for guidance. Otherwise skip to step 3.
How to root your phone
There are a lot of XDA threads explaining how to root your phone. Towel root will work with almost all phones (and doesn't increment the Samsung Knox flag, if you care about that). You need a pre June 6, 2014 firmware build for the original Towel Root method to work. Otherwise, downgrade to an older firmware first (Use Odin software for Samsung), then root with Towel root. Or you can look for the modified Towel root that is said to work with newer firmware (unconfirmed by me). Another excellent root method is CF-Autoroot which works with most popular phones.
3. If you are running a custom ROM and kernel that were compiled from source code, well done. Skip to Step 4.
Otherwise click on the button below for more information.
Custom ROM & kernel
Qualcomm apparently reads XDA too and appears to have added some anti-tamper code to keep this hack or similiar mods from working. Drat! Until we figure out exactly what they added, you will need a custom ROM & kernel for this mod to work. This works because a kernel made from scratch won't have the anti-tamper code in it. Probably you only need the custom kernel and not the full custom ROM (unconfirmed). Configurations known to work include CM11 + Ark kernel. And Phoenix V3 ROM + kernel. But any custom ROM + kernel that is made from source, rather than modified stock will probably work fine. If anyone is still running Jelly Bean (firmware versions 4.2.2. and below), you probably don't have the anti-tamper code and won't need a custom ROM or kernel.
You can go ahead and try adding bands without a custom kernel. It probably won't work, but you can leave the custom kernel as the very last step if you want to and see if adding bands without a custom kernel succeeds. Note that installing a custom kernel on a Samsung phone will increment the Knox flag if you care about that (the Knox flag might affect a warranty claim).
If you have a Verizon or ATT phone, you should know that these two carriers do something that almost no other carrier does. These two carriers lock the bootloader which prevents installing a custom kernel in the normal manner. The Safestrap program can emulate another ROM, but we won't know if that is sufficient or not for this mod. If you are with Verizon or ATT, let us know if you were able to add bands or not.
Follow this link for details about the Phoenix ROM + kernel for the S5.
You can find CM11 downloads here for various phones. Then look for an XDA support thread for your phone.
Ark kernel
4. Download and install QPST. We will use this program to edit your phone settings. This runs best on Windows XP. But you can use Windows 7 (and probably Win 8, if you must). Right click on setup.exe (not the .msi file) and choose run as adminstrator.
5. Download and install QXDM. We will use this program to "write enable" your phone settings. QXDM won't work unless QPST is also installed, so you need both programs. Right click on setup.exe and choose run as administrator to install.
6. Open the USB settings screen on your phone. Change USB from AP to CP. And USB settings from MTP + ADB to RNDIS + DM + Modem mode (after you have finished making edits in your phone's memory, remember to revert the original settings in this screen).
This is the hardest part of this mod as the USB setting menu is usually hidden and the method to access it is slightly different on some brands. For the S5, you can open it by dialing *#0808# . Other phones may use *#7284# , *#8778# , *#*#8778#*#* , ##3424# or something else entirely. If those codes don't work on your phone, try a Google search for keywords like those below to find out how to open the USB settings menu for your phone:
Google: USB settings <brand> xda
Google: how to use QPST <brand> xda
6a. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
For Sony, the following CLI commands have been reported to work. These may or may not work for other brands.
You can enter these using a terminal emulator app or from an adb shell.
From terminal emulator:
Code:
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable
Or using adb:
Code:
adb start-server
adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/class/usb_composite/modem/enable
exit
If you use either of these, remember to revert the USB settings after you finish your phone edits. e.g.
Code:
su
setprop persist.usb.eng 0
setprop usb.rndis.enable 0
echo 0 > /sys/class/usb_composite/modem/enable
6b. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an LGE phone, try the dialer codes here and change the USB mode from AP to CP (Modem mode). If that doesn't work, then it has been reported that the following commands will also enable diagnostic mode for you:
Code:
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
6c. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an HTC phone, this diagnostic driver may work for your phone.
6d. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have an Opo phone, it been reported that the following commands will enable diagnostic mode for your phone.
Code:
su
setprop sys.usb.config diag,adb
6e. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you have a custom kernel installed (which has permissive permissions) then you can probably enable diagnostic USB mode from the EFS Professional program menu.
6f. If you have enabled RNDIS + DM + Modem mode already, skip to step 7.
If you cannot find out how to access the USB settings on your phone anywhere, you may be able to force diagnostic mode by installing the Windows USB drivers for your phone in advance. You can download Motorola /Sony/ LG/ HTC/ ASUS/ Huawei /Google, etc drivers here. Otherwise do a Google /XDA search to find USB drivers for your phone. Install the USB driver.
7. Enable USB debugging on your phone. This is a hidden menu. Look for Settings menu > System > About Device > Developer. If you don't see a Developer option, then tap on the firmware build number about ten times to unhide it.
8. Connect your phone to your phone to an USB port on your PC. Do not use an USB hub, connect directly to your computer. Windows will install a diagnostic driver.
9. Open the Windows (Control panel) Device Manager and confirm that you see something like "Samsung Mobile USB Serial Port" listed there. If you see a yellow triangle there > right click and update the driver.
10. Open the "QPST Configuration" program > Ports > Add new port > choose the port labeled diagnostic > OK.
If you do not see a diagnostic port listed and you were not able to explictly able to set USB diagnostic mode earlier, then right click on the driver that Windows has assigned to your phone in the Windows (Control panel) Device Manager > Update Driver Software > Browse. Choose the folder where you extracted the USB driver that you downloaded for your phone. This forces Windows to use the downloaded driver.
11. Now select the QPST Start Clients > Software download > Backup > Start. This saves a backup copy of your phone's stock NV memory to your computer in case you need it later.
12. Navigate to the C:/Program Files/Qualcomm/QPST/bin folder.
13. Right click on ServiceProg.exe > run as administrator.
14. Choose Phone > Read from phone > UMTS System. This will show which 3G bands are currently enabled. Add checkmarks to the additional 3G bands that you would like to add. Resist the temptation to check everything unless you are prepared to troubleshoot possible issues with non-existant bands, slow boot times and other issues. Just add specific bands that you need for another carrier or are missing in the areas you travel. If you aren't sure what to add, then don't check any extra bands for now - you can always come back later after you find out which 3G bands you can actually make use of.
Either way, do not click write to phone yet. And do not close the Service Programming window either.
15. Before we write anything to your phone, we need to write enable the locations we are going to edit. Navigate to the C:/Program Files/Qualcomm/QXDM/bin folder.
16. Right click on QXDM.exe > run as administrator. If you are not adding any new 3G bands at this time, skip to step 21.
17. In the NV Browser window, scroll down to ID 01877 (aka NV 1877) > Read.
Then write "0" to NV 01877 with QXDM. This initializes (write enables) the item for QPST. We need to do the same for several more NV items.
18. Select ID 00441 > Read. > Write "0" to NV 00441 with QXDM. This initializes (write enables) the item for QPST.
19. Select ID 00946 > Read. > Write "0" to NV 00946 with QXDM. This initializes (write enables) the item for QPST.
20. Select ID 02954 > Read. > Write "0" to NV 02954 with QXDM. This initializes (write enables) the item for QPST.
21. If you do not intend to add any new LTE bands, skip to step 24. Otherwise,
Select ID 06828 > Read. > Write "0" to NV 06828 with QXDM. This initializes (write enables) the item for QPST.
22. Select ID 06829 > Read. > Write "0" to NV 06829 with QXDM. This initializes (write enables) the item for QPST.
23. If you wish to add LTE bands and have already calculated a custom value from the instructions in the thread, then use QXDM to write that value to both ID 06829 and ID 06829, writing one item at a time.
Otherwise, write (decimal) "17592185995263" to both ID 06828 and ID 06829, writing one item at a time. This will enable all LTE bands.
Note that LTE edits will only work if your firmware has an LTE modem. If you already have at least one LTE band active, then you are OK. If your current firmware is from a carrier that does not use LTE at all, then you'll also need to update your modem to an LTE capable version as well.
24. Now go back to the Service Programming window that you left open. If you added any new 3G bands, click on write to phone to write the current selection of 3G bands to your phone. Otherwise do not click write, simply continue on to the next step.
25. You are now finished editing the NV values in your phone.
26. Reboot your phone.
27 In the Service Programming screen, choose Phone > Read from phone > UMTS System to confirm that your new 3G band selection are persistent. If they revert and you don't have a custom kernel installed, this confirms that you will need a custom kernel for this mod to work.
28. In the QXDM NV Browser screen, scroll down to ID 06828 > Read. Note the value.
29. In the QXDM NV Browser screen, scroll down to ID 06829 > Read. Note the value.
ID 06828 and ID 06829 should both show the custom value that you wrote. i.e. "17592185995263" (or hex "0xFFFFFFF3FFF") or the custom value, if you had used one.
30. Remember to change your USB settings back to normal mode, e.g. on the S5, dial *#0808# again and choose USB = AP and USB Settings = MTP + ADB > Click OK.
31. Celebrate! And let us know about your success (or sticking points).
32. You can test your results by checking whether your phone uses the new bands when you roam onto other systems that use them. Or if you have a SIM card for an alternate carrier. To tell if your phone is using the new bands, you can look at the current band being used in the Service menu or with various apps, e.g. LTE Discovery.
.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[size=+1]So now what?[/size]
Well, if you decided to jump in and follow the Quick Start Guide.. that's it. The Quick Start Guide has everything that you need to add new bands to your phone. Unless you run into difficulties, you don't need anything else. The guide is a bit terse as I don't have a lot of spare time to rewrite or polish it. But all of the important information is there.
If something doesn't make sense or you get stuck somewhere, you can (and should) try a quick search for details. If that doesn't resolve your issue, then post in this thread for help. If you want to learn more about how this works, why more bands is a good thing. Or how to make custom edits that choose particular frequency bands, then keep reading this post and the rest of the thread.
This is a proven working method, despite a few trolls claiming otherwise. It's also new territory and there are model specific quirks.
If you run into problems, most likely you missed a step somewhere. Less likely, you may have discovered something new that needs to be unraveled.
The purpose of this thread is to discuss new findings and suggest ways to improve this method.
This is not a support thread, although if you make an effort to provide enough detail about your situation, someone will probably try to help you.
[size=+1]Is this mod hard to do?[/size]
No. There really isn't anything hard about it. But it's not a one click kind of mod either. These are recent discoveries and there are a lot of steps needed to make these changes. Samsung doesn't want to make it easy for you - they'd rather sell you another phone. In particular, there is one hidden menu (USB settings) that is hard to find because it's in a different place on almost every brand of phone. So we have to Google around for details and experiment a bit to find the hidden menu for some brands. But the mod works. If you have a little patience and don't get frustrated at temporary obstacles, then you can add bands to your phone!
One surprising finding was that people with older phones were having better results. Why? It seems that Qualcomm quietly added some anti-tamper code into recent Android versions to keep us from doing this. It's almost like they read our forum and know what we're trying to mod. But they wouldn't spy on us like that, would they?
We don't know where the anti tamper code was added yet but we found that we can avoid it on newer phones by installing a custom kernel & ROM. So until we discover where they added the anti tamper stuff, you also need a custom kernel & ROM (probably the custom kernel is the essential part) to make this mod work. Unless you happen to have an older phone that is still running Jelly bean (4.2.2) firmware. So that's it in a nutshell.
[size=+1]Okay. So give me a quick overview again[/size]
Our phones have artificial restrictions in them so that they only work properly on the original carrier. If you travel (roam) or change phone companies, your phone won't work 100% because it will have gaps in coverage. It will be missing some of the frequency bands that the other carrier uses. This isn't a technological limitation. It's just your wireless carrier siphoning more money out of your pocket by forcing you to buy a new phone when you change carriers.
This mod has a lot of steps in it, so it won't be for everyone. But if you have some patience or enjoy a challenge then it's a great way to really improve how well your phone works when you roam onto another carrier. There are three parts to this mod. You need:
1. A phone with a Qualcomm processor, that is rooted.
2. (For now) Install a custom ROM & kernel to get rid of the anti-tamper code
3. Edit six values in your phone's non volatile (NV) memory to enable a lot of additional frequency bands
That's it. It takes about thirty steps to do those three things but nothing really good ever turns out to be easy, right?
.
[size=+1]Success stories[/size]
Some documented successes - various models
Congrats @BlackSoulxxx
Samsung S5 Int. version (SM-G900F) (added LTE bands) - details CM11 + Ark, custom ROM & kernel.
Added 35 LTE bands i.e. all LTE bands (not all bands confirmed as operational).
Congrats @regspy
Verizon HTC One M8 (added LTE bands 3,7) - details
Congrats @bpear96
Moto G (added AWS RF band 25) - details
Congrats @drnizeguy
Opo OnePlus One (added LTE band 20) - details here, here & here
Congrats @OP
Samsung S3/S4/S5
S3 - added AWS (RF band 25) to SGH-I747M
S4 - added AWS (RF band 25) to SGH-I337M
S5 - added LTE band 13 to SM-G900T - details custom Phoenix kernel and ROM
XXU1ANG2, NV 6828, 6829: decimal 139710 i.e. LTE bands 1/2/3/4/5/7/8/13/17
Currently testing 47 added bands. It's frankly difficult to confirm that most of the additions are operational as no local carriers
use most of the newly enabled bands. So far, 7 new LTE & 3 new 3G bands confirmed as actually in use.
Congrats @ JustLiveIt - details here
LG G3 D855 - Added LTE bands 2/4.
Congrats @ kroukes2000 - details here
LG G3 - Added LTE bands 3/7.
According to this Japanese site (Google translation), there have been successes with a variety of models
e.g. Nexus 5, Nexus 7 LG G2, Moto G, Sony Xperia Z, Z1, ZL, ZR & HTC J.
Samsung SM-G900F - added LTE band 4. Confirmed operation on new band
Samsung SM-G900P - added LTE band 4/14
Samsung SM-G906L - added LTE band 4
Congrats @ Guiper - details here
Nexus 5 (LG D820) - Added LTE band 3
Congrats @ Trak-X - details here
Samsung SM-G900V - Added LTE band 3
.
.
[size=+1]The Gory details[/size]
If you are following the Quick Start guide, you can probably skip this section for now. This is a detailed explanation of how to calculate values for custom configurations. And other gory details.
This is an S5 forum, but you're welcome to post here if you own a different brand of Qualcomm based phone.
This mod should work for almost any Qualcomm based phone which is a lot of Samsung, Sony, LG, Opo, Nexus, and other models.
If you own a Samsung phone, you should know that installing a custom kernel will increment something called the Knox flag. Most of us don't care about Knox, but some people do because it might affect your phone's warranty. Samsung threatens to void your warranty if the Knox flag changes. That still doesn't affect most warranties because most people make warranty claims through their carrier, rather than directly with Samsung. And most carriers don't care about Knox. It's also illegal for Samsung to void warranties this way in the E.U. Anyway, what you need to know is that if you install a custom kernel it will increment your Knox flag. And that might afffect you if your phone is still under warranty.
The actual information in your phone's non-volatile (NV) memory is formatted in byte swapped, little endian hex. Huh? Just something that programmers did to confuse the rest of us. If you're really curious, you can read about it here. We start off with a binary number because it's easy to represent what bands we want that way. Then we use a calculator to convert that number to decimal or hex, depending on which NV editor program we use. Windows has a built in calculator that you can use, just set it to scientific mode. Or there are a plethora of online calculators.
Note that some NV editors use a non-standard binary format as well.
e.g. if we want to represent an NV edit for bands 1/4/5/6/15, we can write it in binary as follows
1000000001110010
15 <------------------ 0
bands 1/4/5/6/15 (standard notation)
We write the bands we want as "1", meaning that they are enabled. We start with a placeholder for zero on the right side. Then construct or read the number, right to left. So band 1 is the second position from the right. This is the standard way of doing things and what most of your NV editors will use (newer tools may take decimal numbers instead).
Just to complicate things though, QXDM lops off the zero placeholder just to be different.
100000000111001
15 <------------------ 1
bands 1/4/5/6/15 (QXDM notation)
It's all arbritrary, so the editor still works fine. It just creates unnecessary confusion because calculations will now be different from a standard editor than the renegade. So double check your writes to see that the expected value was written. And of course the best test of all is finding that the new band works properly!
[size=+1]What bands do you want?[/size]
We need to make a list of 2G/3G bands. And a second list for LTE bands. Your list should probably include the bands that your phone already has, plus the ones that you want to add. You can find out what bands your phone already supports with a search. Be sure to use your actual S5 model, e.g. sm-g900t for TMobile, sm-g900v for Verizon, etc.
Google: sm-g900a specs site:samsung.com
S5 models (variants)
Asia sm-g900i
ATT sm-g900a
BMC sm-g900w8
Canadian S5's sm-g900w8
China sm-g9006v
China ZM sm-g9008v
China CTC sm-g9008d
Claro PR sm-g900w8
Europe sm-g900f
Japan DCM sm-g900d
Japan KDI sm-g900j
Korea KTC sm-g900k
Korea STC sm-g900s
Sprint sm-g900p
TMobile sm-g900t
US Cellular sm-g900r4
Verizon sm-g900v
Vodafone sm-g900m
Note that the sm-g900h is not supported
because it uses a different processor
[size=+1]NV editors[/size]
QPST v. 2.7.411 download . (QPST v. 2.7.323)
QXDM v. 3.12.714 download
EFS Professional v. 2.1.73
CDMA Workshop (Demo)
Caution, some antivirus programs flag this as a generic trojan. Appears to be a false alarm, they've categorized it as a "hacker tool" and lumped it in with trojans! Political Correctness /FUD to the rescue. Yes Virginia, we do want to hack our phone. No apparent evidence of actual malware, but use at your own risk
DFS Tool (Demo)
QRCT
QDART
Untested downloads. Download the following links at your own risk!
These are Google search hits that I haven't found time to check out yet. Be sure to scan these for malware and viruses.
These QXDM 3.14.x builds are not usable unless you have already have a license.
QXDM v. 3.14.514, unlicensed
QXDM v. 3.14.594, expired license
NV writes don't succeed? You may need to enable the NV parameter first (write enable it) - details
NV changes revert? - This may mean that the NV wasn't write enabled (see above).Or that you need a custom ROM and kernel to avoid the apparent anti-tamper code added to Kitkat. e.g. CM11 & Ark kernel or Phoenix v3 ROM & kernel.
[size=+1]An example[/size]
Say that you want to use an ATT phone on TMobile?
The ATT version S5 is missing the AWS band (RF band 25) that TMobile uses.
So we will want to add the AWS band to the ATT version S5 i.e. the sm-g900a.
Determine what bands you want
In this case, the bands that TMobile uses.
Google: specs sm-g900t site:samsung.com
samsung.com said:
Network
LTE bands 1/2/3/5/7/8/4/17
HSPA+/UMTS: 850/AWS/1900/2100MHz
GSM: 850/900/1800/1900MHz
Click to expand...
Click to collapse
Using our table of bands (post No. 3), we can cross reference that to:
LTE (4G) bands 1/2/3/5/7/8/4/17
RF (UMTS /3G) bands 26/25/23/22
RF (GSM /2G) bands 19/8/7/21
So we end up with a total of these bands:
RF Bands 7,8,19,21,22,23,25,26
LTE Bands 1,2,3,4,5,7,8,17
Now that we know which bands we need to change six settings in the phone's non volatile (NV) memory. Some NV editors may let you choose the desired bands from a menu. Try the QPST service programming menu for that. If your editor doesn't have let you do this, then you need to calculate the six raw numbers and write them to your phone.
Calculate the required NV values
We write the two band lists as binary numbers, with "1"s representing the bands that we want. And "0"s for non-selected bands. Then we use a calculator to convert the binary number to decimal or hex number that your NV editor will need (see note about hex conversion, here).
#1 NV 1877
RF Bands 7,8,19,21,22,23,25,26
Now just to confuse you.. I know from looking at the stock Tmobile sm-g900t that it also includes RF band 9. This is a subset of band 8. As band 8 incorporates band 9 it might seem redundant to list both. It's done to ensure compatibility with roaming networks that are not band 8 aware.
So we'll revise our list to include band 9
RF Bands 7,8,9,19,21,22,23,25,26
binary 110111010000000001110000000
Remove any leading zeros = 110111010000000001110000000
decimal 115868544 = hex 6E803280
hex 6E80380 = byte swapped hex 80 03 E8 06
As a check, we find that this value is the same as the stock Tmobile NV (yea!)
#2 NV 6828
LTE Bands 1,2,3,4,5,7,8,17
binary 100000000110111110
Remove any leading zeros = 100000000110111110
decimal 131518
hex 201BE = byte swapped hex BE 01 02
#3 NV 441
Copy bits 0 - 15 from NV 1877 = 0000001110000000
Remove any leading zeros = 1110000000
decimal 896
hex 380 = byte swapped hex 80 03
#4 NV 946
Copy bits 16 - 31 from NV 1877 = 11011101000
Remove any leading zeros = 11011101000
decimal 1768
hex 6E8 = byte swapped hex E8 06
#5 NV 2954
Copy bits 32 - 63 from NV 1877 = N/A
Remove any leading zeros = N/A
We don't have any bits in this range, so write 0
decimal 0
hex 0
#6 NV 6829
Copy bits 0 - 63 from NV 6828 = 100000000110111110
Remove any leading zeros = 100000000110111110
decimal 131518
hex 201BE = byte swapped hex BE 01 02
Write the edits to your phone
Now you need to write (save) the changes to your phone:
Back up your phone, including your IMEI and EFS just in case
Open your NV editor
Enable USB debugging enabled in the Settings menu.
Put your phone into diagnostic mode.
Then use the dialer code *#0808# to enter the USB settings menu.
Set USB = CP (Modem) and USB settings to RNDIS + DM + Modem (USB mode)
Use QXDM to write enable a NV parameter by reading it. Then writing "0" to it.
Then write your intended NV edit with QXDM or other NV editor. The leaked versions of QPST are too old to write enable a field directly.
You can only write one NV parameter at a time, unless you found a copy of the more capable QRCT software.
Do the same for the remaining five NV parameters.
Return your phone to normal USB mode AP (CPU) and MTP + ADB USB mode.
Reboot your phone
Confirm that it worked by viewing what band is in actual use in the Service menu or with a monitor app e.g. LTE Discovery.
Celebrate! And tell us about your success.
[size=+1]Reference[/size]
Some existing threads
How to enable 3G on TMobile AWS 1700MHz for ATT Galaxy S3 i747
[WIP] How to enable Tmobile AWS 1700 band on S3 I747 and I747M (NV backup method)
Summary of cross model success (Japanese language - Google translation)
How modify a qcn file to enable AWS band
Unlock all bands of your Qualcomm device! Use your phone globally! No bs!
[size=+2]Caution: If using the NV calculator app advertised in the next post[/size]
[size=+1]The app is producing erroneous results[/size]
The app author was made aware of the errors earlier in this thread but refuses to address the errors. He is convinced that no errors exist. And being dogmatically certain, he won't actually take a little time to confirm that his app works with the various popular NV editors. He posted that he will rely upon people using his app to report if there are any issues. Since you are being set up as an unwitting guinea pig, you should know that the app may work fine for you or cause much frustration, depending on what NV editor you use. If you decide to use his app, ensure that you check the results and confirm that it is compatible with the particular NV editor you are using.
The app appears to work correctly with some NV editors. And clearly does not with others. This is logical as various editors require different input formats. The author hasn't provided for this, making his app incompatible with some popular NV editors. If you use this app, you need to be diligent in checking that it is producing accurate results for you. A lot of people have been asking me whether this app works as the app author is actively promoting it in this thread. And has even deleted some of his posts where he asked me how to use this method and how to make calculations (replacing his questions with ads for his new app) and quoted my instructions out of context to assure users that his app works correctly.
.
I have made this app for your convenience in calculation of NV items: Qualcomm NV Calculator
This app can show the calculation result in 3 formatS: Decimal, Hexadecimal and Byte-swapped Hex.
DOWNLOAD: https://play.google.com/store/apps/details?id=org.vndnguyen.nvcalc
Some screenshots:
This thread has finally been created! Thanks for posting this. I've been looking for someone to solve this.
vndnguyen said:
Thanks for the guide. Very informative and comprehensive guide
May I ask the question, why don't we enable all the bands, instead of only some bands?
This way we just need to put all '1' into the number, i.e 1111111111111111.....11111111111111
I think that will be simpler for the users.
Click to expand...
Click to collapse
There is no reason why someone couldn't try enabling every possible band.
But two possible issues come to mind. If literally everything is enabled, even non-existant bands we may get undefined or out of bounds errors. And possibly it might bog the system down if too many bands are enabled. We won't know until someone tries and finds out.
.
My phone alreay has activated the LTE band..You can read on the original box.
ionutmaruta said:
My phone alreay has activated the LTE band..You can read on the original box.
Click to expand...
Click to collapse
You didn't say what phone you have.
Regardless, I'm not aware of any stock phone that has all LTE bands enabled. I think that you'll find it only supports a subset of LTE bands 1,2,3,4,5,6,7,8,9,10,11,12,13,14,17,18,19,10,21,22,23,24,25,26,27,28,29,30,31.32,33,34,35,36,37,38,39,40,41,42,43, & 44.
.
FYI of any early birds who are already testing.
There was a typo saying write NV 6929 with the same value as NV 6828.
That should have read NV 6829, not 6929.
.
This guide only applies to Qualcomm based phones.
That is a lot of phone models, including most Samsung S5's. However the SM-G900H S5 used in some parts of the Middle east and Latin America uses a different processor, Exynos instead of Qualcomm.
This will not help 900H owners.
.
fffft said:
tt
Click to expand...
Click to collapse
Not all, of course. But who need to enable all LTE bands, because this is no implemented in all countries.
In my country is implemented 4G, but I never see the download speed more than 10 MB/s
Only H+ and 3G
OK, your turorial is fine, but like I said, there are no many peoples which want to enable all LTE bands. Our infrastructure is down !
I think that is a narrow view. There are a lot of people that would benefit from a greatly expanded set of bands. Some people travel extensively and have mediocre roaming experiences due to many inaccessible bands.
Another situation would be changing carriers. Having a richer palette of service bands could obviate the need to buy a new phone to get full coverage under a new carrier's spectrum allocation.
.
I am one of them. I travel extensively and would like them all enabled just in case.
Sorry but I already tried in S5 and it keep reset nv 1877 because in the kernel and ROM has "safety" procedure (actually it's vary from Kernel to kernel and rom to rom...) so I have to decompile everythings and disable it. Hope it can help....
BlackSoulxxx said:
Sorry but I already tried in S5 and it keep reset nv 1877 because in the kernel and ROM has "safety" procedure (actually it's vary from Kernel to kernel and rom to rom...) so I have to decompile everythings and disable it. Hope it can help....
Click to expand...
Click to collapse
Interesting. Which S5 variant did you try?
It works with the S5 (Phoenix custom) ROM /kernel, which was compiled from source.
It'll be interesting to hear if it works with other S5 (stock) variants or not.
.
fffft said:
This guide only applies to Qualcomm based phones.
That is a lot of phone models, including most Samsung S5's. However the SM-G900H S5 used in some parts of the Middle east and Latin America uses a different processor, Exynos instead of Qualcomm.
This will not help 900H owners.
.
Click to expand...
Click to collapse
Hi fffft,
Fantastic, I absolutely am going to test it.
Well the guide suit the Korean version of SGS5 namely SM-G906K running on QC805 you think?
botwa2000 said:
Fantastic, I absolutely am going to test it.
Well the guide suit the Korean version of SGS5 namely SM-G906K running on QC805 you think?
Click to expand...
Click to collapse
I don't have a G906K to test. And Qualcomm doesn't believe in sharing their technical documentation.
So we won't know until someone tries it.
You have a derivative of the original S5, usually referred to as the S5 LTE-A aka the infamous S5 Prime. It's Qualcomm based and running Kitkat so it will probably work on your phone as it does on a dozen other brands of Qualcomm based phones.
However, we may need to develop ROM or kernel mods before you'll succeed with your phone as post No. 14 above suggests that Samsung may be trying to thwart us on recent models.
.
fffft said:
I don't have a G906K to test. And Qualcomm doesn't believe in sharing their technical documentation.
So we won't know until someone tries it.
You have a derivative of the original S5, usually referred to as the S5 LTE-A aka the infamous S5 Prime. It's Qualcomm based and running Kitkat so it will probably work on your phone as it does on a dozen other brands of Qualcomm based phones.
However, we may need to develop ROM or kernel mods before you'll succeed with your phone as post No. 14 above suggests that Samsung may be trying to thwart us on recent models.
.
Click to expand...
Click to collapse
If im reading this right would this allow me to add verizon 4g bands to my g900f so i can get phone working fine once im there
fffft said:
I don't have a G906K to test. And Qualcomm doesn't believe in sharing their technical documentation.
So we won't know until someone tries it.
You have a derivative of the original S5, usually referred to as the S5 LTE-A aka the infamous S5 Prime. It's Qualcomm based and running Kitkat so it will probably work on your phone as it does on a dozen other brands of Qualcomm based phones.
However, we may need to develop ROM or kernel mods before you'll succeed with your phone as post No. 14 above suggests that Samsung may be trying to thwart us on recent models.
.
Click to expand...
Click to collapse
Thanks. I'm fairly new in the field, do you mind posting a guide on how to backup/restore the current settings should the procedure go wrong.
Or point me to a direction where such a guide is already available.:thumbup:
fffft said:
Interesting. Which S5 variant did you try?
It works with the S5 (Phoenix custom) ROM /kernel, which was compiled from source.
It'll be interesting to hear if it works with other S5 (stock) variants or not.
.
Click to expand...
Click to collapse
I have Int' LTE variant of S5
And I also forget to tell you that modem is involved in too