Database Users

How modify a qcn file to enable AWS band

Hi.
I come from another post looking for a solution to my dilemma (http://forum.xda-developers.com/galaxy-s5/help/switch-stock-rom-t2866861#post55236673), thanks to fffft member found that I can open the band 4 of my cell S5 using the QPST program, however I can not find a modified .qcn file that corresponds to my model (G900F).
What I have done is make a backup of my original .qcn (which understand not share because there goes my IMEI) and I need advice from someone who knows that is the parameter that should change to open the AWS band 4.
Much appreciate your help.

I see that nobody has answered, if it was not for lack of cooperation, or because no one has had this problem.
Continue researching and achieve get qcn file G900M, which is super, but not left so installed as well, the QPST program generates an error and does not let install, so proceeded to compare them to see how different they are, and actually they are very different in their hexadecimal setting.
The issue now is, I need someone to tell me what are the parameter I have to modify my original qcn (my G900F) to enable AWS band 4.
Thank you for your help.

..

Hello again fffft.
I will try to explain everything in the best way. I can not send the file qcn G900M, because I have understood that within the IMEI can be identified, and the first thing I asked the person I give it to me was that change could not deliver it to anyone.
Now step by step to do was the following (taken from this forum http://forum.xda-developers.com/showthread.php?t=2291589 ):
Install phoneutil.apk in my phone.
Install QPST 2.7 build 323.
Choose the usb connection “RNDIS + DM + MODEM” from the menu that comes by typing *#0808#.
On the Ports tab of the program QSPT set the COM port corresponding to the cell (seeing that port recognizes the cell through Device Manager).
Choose “Start Clients” and choose “SOFTWARE DOWNLOAD”.
Hit the “Restore” tab, set port to COM number, choose the QCN file, and start.
Attached two images, one in which it is seen that the process is running smoothly, and a second in which shows the error.
With regard to your question about the RMNET protocol, for I must say I have no idea regards, because as I said I am still a newbie.
Finally and with respect to qcn file G900T me would be very very difficult to get the file G900M was relatively easy (not as easy lol) but because here in my country is the model that is sold, but the model does not get G900T no way.
I remain attentive to your suggestions, and thanks again for the help.

..

I thought S5 supports AWS band as well as other bands? I bought S5 from Rogers and use it with Wind mobile (Canada).

..

Hi.
Well, with my answer are attached to the two qcn files, not if it's okay to post them because I do not know which is the information that I'm giving, but I'll trust you fffft.
Review the entries with IMEI and clear, making this process and I thought this would be a very good explanation of why not to overwrite the original file leaves the cell, because the second IMEI not for the phone, but even if this were true, no understand how in the above forum they spread a qcn file for S4 that everyone could use.
Anyway, I hope that with this we can advance the issue to see if I can get out of this mess.
Thanks again.

..

Ok fffft, I found the parameter you say, but now my question is, as I edit the file qcn? I need some special program?

Loperaco said:
Ok fffft, I found the parameter you say, but now my question is, as I edit the file qcn? I need some special program?
Click to expand...
Click to collapse
Well, download the program XVI32 to edit the hexadecimal, apparently was successful but eventually the program generated the same mistake I had already seen, indicating "Could not reset the phone. COmmunication Errors Occurred".
Will you help me?

..

Hi there.
I have an interesting fact to share, because I could not properly complete the process to overwrite the qcn file then started to review the QPST program and its functions, among these I found the display content on qcn files through this for any entries who had been unable to write and determine that it was possible to write the file so qcn "hot" (ie directly on the phone) Oh and surprise! when I saw that the code / parameter that indicated fffft if I had changed even though the restore process had not been successful.
Anyway achieved modify the parameter in question and probe the cell after this, but still not achieve even connect AWS band 4, so despite the success the result was a failure.
Knowing this now accept suggestions from all of you experts.

..

Got a little further, but the bands did not get enabled...
fffft said:
Docx? Shouldn't those be .qcn files?
Anyway, you should try encouraging someone to post a NV dump from their 900T for comparison. You can check the existing AWS threads to confirm, but as I recall to enable AWS on earlier Galaxy models, required editing NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06
So ostensibly you will want to make the same change on your 900F. Comparing your NV to a 900T would lend confidence to that presumption.
.
Click to expand...
Click to collapse
fffft, Laperaco,
I am pursuing the same Band change as described here and have an update of the things that I was able to discover:
1) I was able to use QPST and pull NV backup from my phone - see my JJ_ATT_S5_Bands_Tester_No_IMEI (IMEI removed in Line 550)
**Note that I was not able to restore any QCN back to my phone in either USB mode (and I think this is what Loperaco was talking about), but...
2) I was able to program my phone directly using RF NV Item Manager, but did not get desired results (see below):
- a) I changed 1877 NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06 and nothing changed - i.e. radio still worked and I was still getting EDGE (no HSPA+)
- b) I tried changing the next line 1878 NV_RF_HW_CONFIG_I from f6 to 2c, because I saw that in another QCN file I found online. That actually "killed" my radio altogether, at least until I changed it back to f6
- c) Upon further inspection of the SM-N900T file I found online (too big to upload here), I saw that there are quite a few differences, which leads me to believe that additional configurations must be made to take advantage of the HSPA+ bands.
!! Please !! If someone with T-Mobile SGS5 looking at this, could you pull your QCN, mask IMEI if you'd like and post it here for comparison.
Otherwise, fffft, do you have any other thoughts regarding the changes needed...?
Last note that files are posted as .qcn.txt, becuase forum does not allow posting of qcn file extensions. Just remove .txt and you will have original qcn.
Thanks,
JJ

fffft said:
Your reluctance to document what you have done in detail is unfortunate because it prevents us from confirming that you did as you summarized or possibly discern any errors along the way. Nor did you tell us how you concluded that the phone did not connect to AWS, whether the changes were persistent after a reboot or what the service mode showed for activity after using the diagnostic menu to lock the handset to AWS, et cetera.
Of particular value would be a before and after NV dump from your phone, alongside a 900T NV dump. Which would illustrate both the required changes and any progress made with the attempted write.
To reply to your question, two obvious possibilities are apparent
1. That you changed the parameter as you summarized and that was insufficient to effect the desired change. Which would mean that the required parameter is different for the S5 than preceding Galaxy models for some reason e.g. that a different parameter needs editing or that radio changes are needed as well, even though that was not the case for the S3 & S4.
2. That you made some inadvertent error in your procedure that you didn't discern. No one can look for possible errors in the absence of you providing a detailed, step by step description of what you did though.
.
Click to expand...
Click to collapse
Ok ok, let me see how I can solve this.
First of all is not reluctance, I tried to be clear in how I do things, but I'll try again:
1. I bought a model of cell G900F that has disabled the AWS band 4.
2. I tried using the QPST program to replace the qcn file with one that corresponded to a G900M model, since in this model if the band 4 is enabled, but the process to make it in the program generated the error "Could not reset the phone. Communication Errors Occurred ".
3. I do not know how or if the QPST program writes an error log, so I do not know where to look it can be sent. I explain how to install and run the program each button is a bit wasteful, but I followed the steps in this forum http://forum.xda-developers.com/showthread.php?t=2291589
4. After this, and having received suggestions from fffft, I tried modifying the original qcn file from my phone, because I thought that perhaps the problem was because they were different models and finally the phone would not allow me to put a qcn file of another model. The modifications I did was change the parameter NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06. This is done by the program XVI32 modifying the hexadecimal.
5. I tried again using the option to restore the qcn file in QPST program, but got the same error "Could not reset the phone. Communication Errors Occurred".
6. I assumed I had to think of something else so it was when using the RF NV Manager (included in the installation program QSPT) for locate the actual file contents qcn on my phone, and I realized that despite the error obtained in restoring the file using the QPST program the parameter indicated in paragraph 4 of this list if it had changed.
7. I proceeded to check the signal and actually still had no access to the 4G network, the most that is connected to the HSDPA + network.
8. I read the comments from fffft and now I'm writing this.
I hope I was clear in my problem and have made a good step by step.
Now the issue is that:
A. I do not know how to access the diagnostic menu that enables or disables the AWS band, so I do not understand fffft what you're talking about.
B. I agree that modify only the parameter in question is not sufficient, otherwise the matter would be solved.
C. It is possible that I made ​​a mistake as you point out, I finally am new to this, but still I explained my process so I am attentive to suggestions.
Thanks for the help.

JJ_Boja said:
fffft, Laperaco,
I am pursuing the same Band change as described here and have an update of the things that I was able to discover:
1) I was able to use QPST and pull NV backup from my phone - see my JJ_ATT_S5_Bands_Tester_No_IMEI (IMEI removed in Line 550)
**Note that I was not able to restore any QCN back to my phone in either USB mode (and I think this is what Loperaco was talking about), but...
2) I was able to program my phone directly using RF NV Item Manager, but did not get desired results (see below):
- a) I changed 1877 NV_RF_BC_CONFIG_l from 80 03 e8 04 to 80 03 e8 06 and nothing changed - i.e. radio still worked and I was still getting EDGE (no HSPA+)
- b) I tried changing the next line 1878 NV_RF_HW_CONFIG_I from f6 to 2c, because I saw that in another QCN file I found online. That actually "killed" my radio altogether, at least until I changed it back to f6
- c) Upon further inspection of the SM-N900T file I found online (too big to upload here), I saw that there are quite a few differences, which leads me to believe that additional configurations must be made to take advantage of the HSPA+ bands.
!! Please !! If someone with T-Mobile SGS5 looking at this, could you pull your QCN, mask IMEI if you'd like and post it here for comparison.
Otherwise, fffft, do you have any other thoughts regarding the changes needed...?
Last note that files are posted as .qcn.txt, becuase forum does not allow posting of qcn file extensions. Just remove .txt and you will have original qcn.
Thanks,
JJ
Click to expand...
Click to collapse
Hi JJ.
We are indeed talking about the same issue, however I see a difference and that is that despite not having the band 4 AWS enabled on your phone, this only gives you the edge band, however my phone without enabling the band 4 gives me HSDPA+, so my question, just out of curiosity, is what is the frequency at which your operator transmits the EDGE network?

Loperaco said:
5. I tried again using the option to restore the qcn file in QPST program, but got the same error "Could not reset the phone. Communication Errors Occurred".
6. I assumed I had to think of something else so it was when using the RF NV Manager (included in the installation program QSPT) for locate the actual file contents qcn on my phone, and I realized that despite the error obtained in restoring the file using the QPST program the parameter indicated in paragraph 4 of this list if it had changed.
Click to expand...
Click to collapse
Laperaco,
1) I was also unable to load qcn file from backup even without modifications, so...
2) I made modifications directly to the phone using RF NV Item Manager*
*Note from my post that changing line 1877 made no difference in connectivity for me.
3) This specific connection is below (although it naturally fluctuates):
Network Type: EDGE:2
GSM RSSI: -89db (63%) 12 asu
GSM Signal Strength: 13db (42%)
Preferred Network Type is LTE/GSM autio (PRL)*
*Non-GSM selections (WCDMA, LTE-only, etc) simply do not connect, so no HSPA+ for me
JJ

JJ_Boja said:
Laperaco,
1) I was also unable to load qcn file from backup even without modifications, so...
2) I made modifications directly to the phone using RF NV Item Manager*
*Note from my post that changing line 1877 made no difference in connectivity for me.
3) This specific connection is below (although it naturally fluctuates):
Network Type: EDGE:2
GSM RSSI: -89db (63%) 12 asu
GSM Signal Strength: 13db (42%)
Preferred Network Type is LTE/GSM autio (PRL)*
*Non-GSM selections (WCDMA, LTE-only, etc) simply do not connect, so no HSPA+ for me
JJ
Click to expand...
Click to collapse
Ok JJ, we are going through the same steps, we must wait for more help, I'll keep researching but I see that not many people have our problem.
I have a question is that with that code or through option that could see data that you send me.
Any information or change that has put it in the post.

..

[Guide] Unlock Z3c international band(s)

Main thread: http://forum.xda-developers.com/z3-compact/general/unlock-bands-regions-z3c-root-required-t2940959
Originial thread here: http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
This thread server as a step-by-step guide for the unlocking process, but please takecare of all your personal/important information before modding your phone.
It is your own responsibility to backup all your data, including online and offline backup. I take no responsibility for any broken devices/sdcards/your house going down on fire and everything else.
This mod in fact does NOT unlock any sim lock, don't ask such a question.
And I do NOT think it will unlock [email protected], [email protected] (TBC, no such environment)
What you need:
Sony Xperia Z3 Compact (can be D5803/5833/SO-02G...)
Firmware rooted
Win7 PC with z3c ADB driver installed (I use the one come with flashtool)
QPST / QXDM / mzTool / z3c diag driver (http://goo.gl/pyN5fo, password: [email protected])
terminal emulator installed on z3c (can be optional, but will be easier when switching engineer mode on usb)
Give thanks to @BlackSoulxxx
Optional: FlashTool
Optional: Firmware stock FTF, the version must match your z3c running build (in case of recovery) you can get using XperiFirm
The following Guide assume you have: gain root access, installed SuperSU on phone, installed QPST/QXDM on PC.
I only tested on my D5833 and SO-02F, using Windows 7 Pro x64 SP1.
My originial plan is modding my SO-04E, to enable LTE in my area.
But I pass it to my girlfriend few days before I found this mod.
(her F-07E always boot to safe-mode, should be hardware failure)

Part 1: Connect to the phone's diagnostics mode
1. Enable superuser access in SuperSU if you have disabled it.
2. Go to: Setting -> Developer Option, make sure you turn on "Developer Option" on the top and turn OFF "USB Debugging"
3. Open terminal emulator, type the following command one by one:
Code:
su
setprop persist.usb.eng 1
4. Turn on "USB Debugging" under "Developer Option"
5. Connect your phone to PC via USB. Windows should found a few new hardware, wait until all driver installation fail.
6. Open "Device Manager" in "Computer Management", you should see some device named same as your device model, icons with yelow exclaimation mark.
7. Right-Click the first one, select Properties. Go to Detials tab, and under "Property" label, find the item called "Hardware Ids".
8. There should be some lines under the label Value. Notice the longest one, which should end with something like MI_01/MI_02 etc.
9. Your job is to find the correct device, which should end with MI_04. If you cannot find such device, either you have done something wrong, or your PC's usb fail to operate correctly. In later case, please switch to another PC. (My first trial end with this situation)
10. Once you find the correct device, go to Driver tab and press "Update Driver". Install the usb diag driver from the package, when asked about driver signature, just force insall it. Please make sure driver build match your window build, and do NOT use x86 driver on x64 windows.

Part 2: Unlock GSM/CDMA band(s)
11. Go to Start -> All Programs -> QPST, open "QPST Configuration". In the "Ports" tab, click the "Add New Port..." button in lower right corner.
12. In the Add New Port window, untick the option called "Show Serial and USB/QC Diagnostic ports only".
13. You should find an entry with the name saying z3c USB Modem. Select it and press OK.
14. Make sure the newly added port is "Enabled", under "Phone" block is MSM8974, Link is "USB".
15. Keep the configuration application running in background. Close the application will loose your connection to the phone.
16. Navigate to the installation path of QPST, in the /bin folder, find and execute "RF_NV_Manager.exe".
17. Go to "Setting" -> Comport, select the correct port you created in step 14.
18. In the top menu, "File" -> "Read from Phone". It should start reading your phone but take times.
19. After reading operation finished, in the lower left panel find the item with number 1877 (NV_RF_BC_CONFIG_I).
20. In the right panel, take a note on the originial value in case of recovery need.
21. Open mzTool, under "Band Preference (Bit info)", select "Decimal" under "Input Radax". In the "RF BC Config", enter the number you noted at step 20. It will list out all your current band supported by your headset, in the bit information box.
22. Still in mzTool, go to next tab named "Band Preference (NV Value)", select the band(s) you need. You can select all, but I personally recommand what you really need plus "[60] Reserved for BC10-1700", at lest those originally come with your phone.
23. After selecting band(s) you need, Copy the decimal value in the "RF BC Config" box below the selection area, and remove all space in between.
24. Go back to QPST again, find item #1877 (NV_RF_BC_CONFIG_I), paste the new value you calculated in step 23 into the right panel, and press the "Write NV"Button.
25. Go to "File" -> "Write Changes NV Items To Phone".
26. Close and reopen "RF_NV_Manager.exe", repeat step 17-19. If #1877 show you the value same as the one you calculated in step 23, then you are OK to proceed. If it revert back to the originial value (you should noted down at atep 20), sorry this mod is NOT for your headset and proceed to last part for quitting diagnositc mode.
27. Close RF NV Manager, unplug your headset and reboot it. If you got reception after reboot, then you are good. Please give thanks to @BlackSoulxxx
27a. Open dialer, type *#*#7378423#*#* (*#*#SERVICE#*#*), goto "Service info" -> "Configuration", you should see your unlocked band. If not, that means your phone reset it while reboot. You can do nothing unless you know how to disable the reset.
27b. If your phone cannot get signal after the mod, flash your phone with the stock FTF, do NOT select anyone under "Wipe:", select all under "Exclude:" but keep "BASEBAND" selected. This should flash the originial baseband firmware, hence remove this mod.
27c. If you still cannot get any reception, flash the whole stock FTF. This will wipe all your data, but reset it to factory installed status.
28. You are done for this section, you may continue for LTE band(s) unlock, or jump to last part for quitting diagnositc mode.

Part 3: Unlock LTE band(s)
29. Make sure you have unlocked "[60] Reserved for BC10-1700" in previous part.
30. Go to Start -> All Programs -> QXDM Professional, open "QXDM Professional". In the top menu select "Option" -> "Communication".
31. Under "All Ports in System:" select your port (should me same port as you use in QPST) and press "OK. QXDM should load all data automatically once you press ok.
32. In top menu, select "View" -> "New" -> "Common" -> "NV Browser". In the newly opened window, select "LTE" next to the "Category Filter".
33. Select the item with ID 06828 (Description = LTE BC Config, Full Path Name = LTE_BC_CONFIG). It should display "input" and "Value" of 0 under "Fields".
34. Press the "Read" button in the lower right corner, it should show a non-zero number under "Value". Please also write it down for recovery.
35. Convert the number, noted at step 34, to binary form. It will show which LTE bands your phone currently supported ...
35a. Start reading from right to left, the 1st digit from the right (right-most) will be corresponding to LTE Band 1, the 2nd digit will be for LTE Band 2, the 3rd digit will be for LTE Band 3. So the rule will be [ N-th digit will be for LTE Band N ].
35b. For each digit, 1 means the phone support that particular band while 0 means no support. For example in D5833, it should be 549890031829 = "1000000000001000000000000000000011010101" (LTE Band 1,3,5,7,8,28,40).
35c. So if you want to unlock some LTE band(s), filp such bit to 1. In case you have a gap like band 28-40, make sure you fill it with 0, or you will fail to unlock such channel.
36. Please work out our own value that suit your need. In my case I need LTE Band 1,3,5,7,8,9,19,21,28,38,39,40,41 so my value will be "11110000000001000000101000000000111010101" = 2061719830997
37. Go back to QXDM, double-click the 0 under "Input", replace it with the number you calculated at step 36 in decimal form.
38. Write the value to your phone by pressing the "Write" button next to "Read" button.
39. Close and reopen QXDM. Repeat step 31-35 and double check the number under "Value".
40. Close QXDM, unplug your phone and reboot it. If you got reception after reboot, then you are good. Please give thanks to @BlackSoulxxx
40a. Open dialer, type *#*#7378423#*#* (*#*#SERVICE#*#*), goto "Service info" -> "Configuration", you should see your unlocked band. If not, that means your phone reset it while reboot. You can do nothing unless you know how to disable the reset.
40b. If your phone cannot get signal after the mod, flash your phone with the stock FTF, do NOT select anyone under "Wipe:", select all under "Exclude:" but keep "BASEBAND" selected. This should flash the originial baseband firmware, hence remove this mod.
40c. If you still cannot get any reception, flash the whole stock FTF. This will wipe all your data, but reset it to factory installed status.
41. If you still cannot connect via LTE, open dialer and type *#*#4636#*#* (*#*#INFO#*#*), find "preferred network" and select "LTE".
41a. If it fail to connect, either is hardware restriction, or more software setting has to be done (some carrier has different APN for 3G/LTE)
42. You are done for this section, please continue for quitting diagnositc mode.

Part 4: Quit Diagnostics mode
43. Unplug your headset if you still connect it.
44. Turn off "USB Debugging" in "Developer Option".
45. Open terminal emulator, type the following command one by one:
Code:
su
setprop persist.usb.eng 0
46. You may either turn on "USB Dibugging", or just leave it as is.
46a. You can also turnoff superuser access in SuperSU, to enjoy Puzzle and Dragon (JP).
99. Don't forget to give thanks to @BlackSoulxxx

Thanks very much for this guide... before I attempt it, a dumb question;
Is this only of benefit for people that roam internationally often? Or can it improve the phone signal overall? (im in the UK)
Kind regards

Still Lte band 20 is not working in D5833, while it is listed in service menu((( I guess there are some hardware differences in radio module between D5833 and D5803

mamumba said:
Still Lte band 20 is not working in D5833, while it is listed in service menu((( I guess there are some hardware differences in radio module between D5833 and D5803
Click to expand...
Click to collapse
Thanks for the confirmation.
I own D5833, but live in Europe, and the available LTE bands in my country are 3 and 20.
I guess I won't be able to use the band 20, shame.

Can anyone, who own D5803 using this manual copy configuration of their phone in QXDM and PM me this file?

Wow, Much thanks. Very good. Great guide...
{
"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"
}

Excellent guide I will try it later, I had a D5833 and I need to get working the LTE 1700/2100 band
Noob question;
If you flash the FTF BASEBAND to revert de mod to it's original state, flashing the BASEBAND of a D5803 FTF to a D5833 model would not do the same trick?? (i suposse not but I'm asking anyway )

nmercy said:
Excellent guide I will try it later, I had a D5833 and I need to get working the LTE 1700/2100 band
Noob question;
If you flash the FTF BASEBAND to revert de mod to it's original state, flashing the BASEBAND of a D5803 FTF to a D5833 model would not do the same trick?? (i suposse not but I'm asking anyway )
Click to expand...
Click to collapse
You may try that, I won't take any production device on such risk anymore:angel:
Why do you flash d5803 Baseband to d5833 device ?
Quick note: someone reported Band4 AWS will not work even we modded the phone to support it ...

Every time I try this, I get a note that write protection on and read only? What am I doing wrong?

i want to try this with a xperia m2 model d2306 i need the band 3 for my lte please some help

Works great for me. Thanks heaps.

Has anyone successfully done this with a a D5803 to unlock TMobile's LTE Band 12 (700mHz)?

I have D5833 and tried to enable LTE band 4(AWS) and 2 to use it with T-Mobile.
Sadly, it doesn't work. The configuration page tells me that both 4 and 2 are enabled, but my phone can't get the signal.
I guess it's because of a hardware difference between D5833 and D5803

Quick note that worked for me on Windows 8 though I don't know if it's the limitation.
When I try to enter the new decimal for 3g bands, it doesn't seem to matter what I choose because as long as I select band 60 the software won't accept the number because its too long. If I change to selecting hex then there's fewer digits and it writes to the phone correctly without issue.

Anybody manage to unlock LTE band 20 ( 800 MHz ) on D6653 ( Z3 ) ???
Do you guys think it's possible or is it hardware limitation ( hope not ) ?

bofis said:
Has anyone successfully done this with a a D5803 to unlock TMobile's LTE Band 12 (700mHz)?
Click to expand...
Click to collapse
Bump. In the same boat (D5803 on T-Mobile) and wondering if it is worth performing all of the steps to unlock Band 12.

[GUIDE] Enable LTE bands on surnia

After some trial and error I was able to successfully enable LTE band 12 on my xt1527 with the 5.1 baseband. This procedure only seems to work with the stock ROM, but then after it's done you might need to install a custom ROM like Cyanogenmod to actually make use of all the bands. Many people have done a lot of previous work to make this possible and they deserve credit, so don't forget to hit thanks on the linked threads. It might be possible to unlock different bands on the different models depending on what the radio will support. I have done my best to try to make sure that this is thorough, but there could be errors, so please let me know if any of the steps need to be revised or corrected.
**** Please note that by doing this it may be possible to permanently damage your phone, make it unable to access mobile networks, or cause radio interference, so you are doing this at your own risk! I am not responsible for any problems! ***
1. Be on a stock ROM (only tested on 5.0.2 and 5.1, see forums for how to restore stock ROM if you need help) Update: also works on 6.0
2. Make sure the Motorola Device Manager is installed https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
3. Select "BP Tools" from the bootloader menu (power off, hold vol-down, power on). The phone will look like it's booting normally.
4. You need to enable usb debugging in developer options. In Windows device manager you should see 3 USB devices without drivers loaded. I picked the first device and updated the driver by selecting Browse computer / Let me pick, and selecting Ports (Com&LPT), Motorola, Motorola QC Diag port. See this post for more info http://forum.xda-developers.com/showpost.php?p=54338876&postcount=3 You should now see Motorola QC Diag Port (COMx)
5. Install QPST and QXDM from steps 4 and 5 in this thread http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
6. In QXDM select Communications and you should see the COMx that you saw in Device Manager. Make sure the Target Port has this COM port selected as well. If it's not connecting double check that the driver is still loaded in Device Manager.
7. In the View box select NV Browser towards the top of the list, and in the window that opens choose LTE for Category filter.
8. The value that we want is in location 6828. Click on it and choose Read. Write this number down in case you have a problem! Convert this number to binary (I use Windows calculator) and these are your current LTE bands. Read from right to left and 0 means the band is disabled, 1 is enabled.
For example, the xt1527 has LTE bands 2,4,5,7, and 17 per the Motorola website.
The value in location 6828 is 65626, or 0001 0000 0000 0101 1010‬ in binary.
Code:
Binary Value 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 1 1 0 1 0
Active Bands[B] - - - 17 - - - - - - - - - 7 - 5 4 - 2 -[/B]
All Bands 20 ? ? 17 ? ? ? ? 12 ? ? ? ? 7 6 5 4 3 2 1
As you can see from this example, each bit corresponds to an LTE band being on or off. Different models (xt1521, xt1528, etc.) will obviously have different bands enabled. To help fill in the missing info on the bands please post a reply with your model, the value of 6828, and the bands that your phone supports according to Motorola.
To enable band 12, I changed the bit in that position to a 1 and converted the entire binary number back to decimal.
Code:
Binary Value 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 1 1 0 1 0
Active Bands[B] - - - 17 - - - - 12 - - - - 7 - 5 4 - 2 -[/B]
All Bands 20 ? ? 17 ? ? ? ? 12 ? ? ? ? 7 6 5 4 3 2 1
So this new binary number 0001 0000 1000 0101 1010 = 67674 in decimal.
9. After you have calculated your new value, type it into the 6828 input field and click Write.
10. Reboot to recovery, make a backup of the stock ROM, and then install your favorite custom ROM, such as Cyanogenmod. The stock ROM might still restrict bands even if they have been enabled in the baseband. You can use the LTEdiscovery app to check your bands, and there are probably other apps as well.
11. If you have any problems try writing the original value that you wrote down earlier back into location 6828 (you did write it down, right?). If that doesn't work, see the modem thread, or extract NON-HLOS.bin and fsg.mbn from your stock image and flash them using the following commands in fastboot.
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Good luck, and don't forget that with the extended range LTE bands you might have data but not be able to make a voice call. You would have to go into Network settings and change the preferred network type to 3G to make an emergency call. Maybe a future project will be looking into putting the baseband from other SD410 devices that support VoLTE on surnia and then using this method to set the correct bands... Something to think about.
Update 17 Oct, 2016: Unknown bands have been replaced with question marks. Driver and utility installation instructions have been updated.

I think this is a great tutorial! I wonder if by adding the USA band (which I have achieved in the past) other carriers could be used? Just thinking out loud.

hydroman202 said:
I think this is a great tutorial! I wonder if by adding the USA band (which I have achieved in the past) other carriers could be used? Just thinking out loud.
Click to expand...
Click to collapse
It's possible to make changes to 2G/3G bands also, so it might work if you add the right bands and the radio hardware supports the frequencies.

spiked_mistborn said:
It's possible to make changes to 2G/3G bands also, so it might work if you add the right bands and the radio hardware supports the frequencies.
Click to expand...
Click to collapse
First thing i thought..
I was assuming this was a hardware issue more than a software config issue.
I had done similar on phones before too so i see what your doing
but i had no knowledge on doing this with more recent phones.
I use to use com ports with QPST (a Qualcom leaked tool) and some other phone tools..
to clone my one pay/go phone from one company to another or vice versa.
I cloned them back & forth because sometimes i bought the wrong type of minutes LOL
For example i had my favorite phone from Telus and i sometimes used another one from Virgin
Different phones totally Samsung + LG and both ran very different systems too.
But get this..
I actually cloned EVERYTHING.
Data settings + MEID / Phone # and even managed to get free unlimited TX messages which were suppose to be 50 cents each. HAHAHAHA
I told my brother and his wife and they laughed and he said you got it on you?
I pulled out both and he phoned then txt'd me
And both phones received the call and received the TXT simultaneously.
So.. OP
Thanks for the info i might want to play around with that sometime.
I had struggled losing LTE support to on my Canadian Telus phone before after using US retail firmware.
I had to put it into 3G mode
So i am curious if this will actually work properly though.
Just because you change a setting does not necessarily mean there is actual physical hardware support for it.
I learned something i think here cool good work!
I like the manually installing Windows Drivers tip too.
I tried side-loading for the first time the other day and i had to manually install the driver for it to work.
So lets see if people come forward proving this works.. i hope so
EDIT:
I will be clicking Thanks simply for showing me what the "BP Tools" was for hahahha

spiked_mistborn said:
It's possible to make changes to 2G/3G bands also, so it might work if you add the right bands and the radio hardware supports the frequencies.
Click to expand...
Click to collapse
I talked with a sprint rep, according to him, anyone on my particular carrier (sprint), needs an msl code to change two specific values (I can't remember the names right this second) to reprogram it to a different carrier. I'm not sure about it, but there it is if anyone wants to give it a shot. I think one of the values was mdn, if that helps.

Wondering if it works on the Marshmallow update too ?

xpmule said:
I use to use com ports with QPST (a Qualcom leaked tool) and some other phone tools..
...
I will be clicking Thanks simply for showing me what the "BP Tools" was for hahahha
Click to expand...
Click to collapse
QPST will interface with this phone also, but it seems to be out of date because it doesn't read the full range of NV values. It would probably work for making 2G/3G or other changes like you mentioned, but it wouldn't read any LTE related values.
BP tools probably stands for "baseband programming" or something similar.

clee666 said:
Wondering if it works on the Marshmallow update too ?
Click to expand...
Click to collapse
I never updated past the 5.1 bootloader, so I haven't tested it, but if you try booting with the BP tools option and see the 3 devices missing drivers let us know.

spiked_mistborn said:
I never updated past the 5.1 bootloader, so I haven't tested it, but if you try booting with the BP tools option and see the 3 devices missing drivers let us know.
Click to expand...
Click to collapse
Either i am crazy or the new Marshmallow Bootloader removed the Wifi Flash option.
I seen it before on lollipop now i don't on 6.0.

spiked_mistborn said:
I never updated past the 5.1 bootloader, so I haven't tested it, but if you try booting with the BP tools option and see the 3 devices missing drivers let us know.
Click to expand...
Click to collapse
I never updated away from 5.0.2, I didn't wan't to lose LTE Band 12.

clee666 said:
I never updated away from 5.0.2, I didn't wan't to lose LTE Band 12.
Click to expand...
Click to collapse
Before doing this I had gone back to the 5.0.2 baseband to get band 12 back, but the wifi reboot issues were starting to get annoying. Being able to add band 12 to the later basebands is nice because I don't have the wifi reboot issues and it's much more stable.

This guide is awesome

Can activate all bands? xD or is bad idea?

Anyone managed to use the Verizon version on T-Mobile band 12?

clee666 said:
I never updated away from 5.0.2, I didn't wan't to lose LTE Band 12.
Click to expand...
Click to collapse
I don't remember if I did or not, is there anyway to check for LTE Band 12 to see if I still have it?
And if I did is there any way to restore it?
---------- Post added at 06:23 PM ---------- Previous post was at 06:17 PM ----------
spiked_mistborn said:
Before doing this I had gone back to the 5.0.2 baseband to get band 12 back, but the wifi reboot issues were starting to get annoying. Being able to add band 12 to the later basebands is nice because I don't have the wifi reboot issues and it's much more stable.
Click to expand...
Click to collapse
Can I reflash the original stock rom to get baseband 12 back, before installing a cyanogenmod update?

dreyeth said:
I don't remember if I did or not, is there anyway to check for LTE Band 12 to see if I still have it?
And if I did is there any way to restore it?
Click to expand...
Click to collapse
You can use an app like LTE Discovery to check when you are in a known band 12 area. I have an area near me that I drive through frequently surrounded by farms where I get a strong band 12 signal, but basically no service if I just have band 4. You could also check the value in NV location 6828 and use the method in the OP to calculate your current LTE bands.
dreyeth said:
Can I reflash the original stock rom to get baseband 12 back, before installing a cyanogenmod update?
Click to expand...
Click to collapse
That should work, but CM13 works best with 5.1 and newer basebands. You will likely have wifi and reboot issues. That was the whole reason for finding a way to add band 12 to newer basebands.

ijasonx said:
Can activate all bands? xD or is bad idea?
Click to expand...
Click to collapse
Probably a bad idea. The RF hardware in the phone can only physically support a few different frequencies, and it might vary by model, so probably only Motorola and Qualcomm know what will actually work. Best case if you try to activate all bands would be you just don't get a signal, worst case maybe you melt something in the phone radio, or get agents from your government radio frequency enforcement agency show up in black vans and take you away.

realdreams said:
Anyone managed to use the Verizon version on T-Mobile band 12?
Click to expand...
Click to collapse
Are you getting LTE band 4 on T-Mobile currently? It might work. If you try it let us know.

spiked_mistborn said:
You can use an app like LTE Discovery to check when you are in a known band 12 area. I have an area near me that I drive through frequently surrounded by farms where I get a strong band 12 signal, but basically no service if I just have band 4. You could also check the value in NV location 6828 and use the method in the OP to calculate your current LTE bands.
That should work, but CM13 works best with 5.1 and newer basebands. You will likely have wifi and reboot issues. That was the whole reason for finding a way to add band 12 to newer basebands.
Click to expand...
Click to collapse
Did everyone have them? and across all the various original modem firmware?
Also amongst the firmware that have band 12 is there one that was more up to date then the others?
Band 12 got stripped out of all the 5.1 firmware and all the 5.0 or older firmware had band 12, which probable
means no right?

dreyeth said:
Did everyone have them? and across all the various original modem firmware?
Also amongst the firmware that have band 12 is there one that was more up to date then the others?
Band 12 got stripped out of all the 5.1 firmware and all the 5.0 or older firmware had band 12, which probable
means no right?
Click to expand...
Click to collapse
Band 12 was and still is active on the XT1526.
Band 12 was active on the XT1527's launch firmware, but was removed in the first OTA update.
The other models did not have Band 12.

Yotaphone 2 signal boost trick/unlock band ?

Helo from Slovenia,
perhaps i found a way to boost signal or unlock bands in Yotaphone 2.
Go to android secret menu *#*#4636#*#*
Then go information about phone menu and scroll down.
There is a option for choosing priority band, normaly its choosen LTE/WCDMA
Klick on this and switch the options to TD-SCDMA,GSM/WCDMA and LTE or TD-SCDMA,LTE,CDMA,EvDo GSM, WCDMA
Now watch the signal boosting
I checked same locations driving yesterday and today with car. Where i yesterday got no signal, today i got fully edge signal.
And no signal outage today no matter the location
Check this option and let me know if it works there too. I tried on Android 4.4.3 and 5 work both.

I put the first one, but how can I see the difference? the problems was not getting the 2G signal at all if I force in 2G. But if I force it now, your suggested settings will change.
What is the difference between TD-SCDMA,GSM/WCDMA and LTE or TD-SCDMA,LTE,CDMA,EvDo GSM, WCDMA?
May I ask you which mobile operator you have and which radio & firmware you use on your YotaPhone2?

TheArt. said:
I put the first one, but how can I see the difference? the problems was not getting the 2G signal at all if I force in 2G. But if I force it now, your suggested settings will change.
What is the difference between TD-SCDMA,GSM/WCDMA and LTE or TD-SCDMA,LTE,CDMA,EvDo GSM, WCDMA?
May I ask you which mobile operator you have and which radio & firmware you use on your YotaPhone2?
Click to expand...
Click to collapse
you have to go to spots/locations where you got no signal before and try it now ?

Setting your phone to the wrong settings so it fails over to 2G will no doubt improve your signal strength no end. But personally I would prefer to get fast internet on the move, and leave your radio settings well alone!
There are apps you can get that are called 'signal boosters' they just work by turning off your phone radio and then on again. If you were not connected to a nearby cell but one farther away this will 'boost your signal' ...
You're probably experiencing either or both of these effects. as well as the 4G effect - which is that if you have a local 4G aerial all the cellphones that can do so will be connecting to that, leaving you free to connect to an empty 3G cell instead with lots of bandwidth. Maybe not what you had planned to do, but actually improving your performance by setting the wrong settings

Did anyone already find the secret USB menu code to put the device into Modem mode? As the YotaPhone has a Qualcomm processor, this could be used to enable additional LTE bands, which really would help with reception like in [GUIDE] Add all GSM and LTE bands to your phone.

seems cool! We have to test

Crazyphil01 said:
Did anyone already find the secret USB menu code to put the device into Modem mode? As the YotaPhone has a Qualcomm processor, this could be used to enable additional LTE bands, which really would help with reception like in [GUIDE] Add all GSM and LTE bands to your phone.
Click to expand...
Click to collapse
Modem mode can setted by change buildprop sys.usb.config=diag.
Next read this.

w()$k said:
Modem mode can setted by change buildprop sys.usb.config=diag.
Next read this.
Click to expand...
Click to collapse
Ah, I haven't noticed that post, so we're making progress but no clear results yet :fingers-crossed:
here on XDA there's also this thread about unlocking frequencies: https://forum.xda-developers.com/yotaphone-one/help/unlocking-additional-radio-basebands-t3523000

TD-WCDMA won't work in spain. TD stands for Time Division and many countries work with FD (Frecuency Division)

Hi,
I am much interested in changing the LTE of YD206, has anyone suceed yet on this phone? A tuto would be really awesome! As I am new to android it would definitly help!
@TheArt. could you eventually translate the post please? My russian is far not good enought and google translated does not make much sens...! Did you succeed modifying the bands?

UNLOCK LTE BAND B20 - 800Mhz and B38
I will translate here the work of three 4pda users who must be thanked a lot for their work! unkernet, ssho and BoyNG. Thank also to mamant1988 who put everything together.
The original 4pda guide can be found here (in russian): http://4pda.ru/forum/index.php?showtopic=797643&view=findpost&p=59716629
UNLOCK B20 LTE BAND ON YD206​
Starting point is a rooted YD206 with latest RU 134 firmware, TWRP and ADB-USB-debug enabled. Do this procedure carefully and write down all the modifications and default values. The changes are performed on NVRAM level, so flashing firmwares will not affect them. Flashing firmwares will, however, affect modified baseband, as any other "radio" part as usual.
Download here the .zip archive which contains what is needed for this guide, including some screenshots of how things should be displayed.
Download the modified baseband RU-CN here and put it into the internal memory of the phone: it will be flashed in the end.
Install QPST and QXDM Qualcomm programs on Windows, they are in the above archive.
Enable the installation of unsigned drivers in Windows (like this). This is needed to install drivers for the diagnostical port later on.
Download Terminal Emulator from Play Store.
In the Terminal, write the following to get root access:
Code:
su
then:
Code:
setprop sys.usb.config diag,adb
Connect the phone via USB to the PC, in the Device Manager it should pop up as "Android Device" or similar, without a specific driver.
Right click on it and perform these actions: update drivers, search on this computer, choose driver from already installed drivers, show all devices, next, install from disk, there point to the .inf file corresponding to your system (32bit -> x86, 64bit -> x64) found in \YotaLTE\Modified HTCDiagDriver\Win x64HtcUsbMdmV64.inf (for 64bit).
After installation, go to properties of this new driver HTC USB Modem and check the number of the port displayed there, COM3 or COM4, for example.
Lower the 38400 value which you find there, click OK.
Execute as an admin C:\Program Files (x86)\Qualcomm\QPST\bin\QPSTConfig.exe.
Choose the second section Ports, then "Add new port".
In the field Port put the one which was displayed in the modem section, COM3 for example.
In Port Label field write "Yota" or whatever, and then OK.
In the first section Active Phones the smartphone should be displayed.
KEEP QPSTConfig.exe PROGRAM OPENED.
Also, start C:\Program Files (x86)\Qualcomm\QXDM\Bin\QXDM.exe using admin privileges
Here, click Option, then Communications.
In the Target Port choose the same port as before, then OK.
Click View, New, Common, NV Browser. In the Category Filter choose LTE.
Choose 06828 LTE BC Config and then press "read".
Correct the number you see, for example 1099511627781 in 1099512152069 for B20 and click Write to save.
Close all the programs, and reboot the phone directly into TWRP (VOL UP + POWER), here find the update_S01_003_4240_RU1_M05_patched.zip baseband and flash it.
At this point it is advised to clean dalvik cache and cache with TWRP.
Done! Reboot.
If it is not working, reset everything by flashing stock baseband, putting back the values changed above and start again. It is not necessary to flash the modified RU-CN baseband, if with the CN one the phone is performing at 100%. I suggest to flash to see the differences. By the way, remember to unlock one band at a time.
To unlock B38 band (there is lack of information about YD206 already having it or not) the number is 1236951105541. For example, if the initial number found in LTE config was: 1236950581253, it means that the bands LTE B1/B3/B38/B41 were active. To verify by yourself download LTE Band Calculator.
Some attempts have been made also to unlock B7 band, but without success for now. It seems that the baseband crashes after a second when triying to connect to that LTE band. Further research needed!

After all the hassle I just went through to obtain a YD201 instead of a YD206 so I could have Band 20
Great news for YD206 owners anyway, thanks for sharing!

hippy dave said:
After all the hassle I just went through to obtain a YD201 instead of a YD206 so I could have Band 20
Great news for YD206 owners anyway, thanks for sharing!
Click to expand...
Click to collapse
Me too.
Tried drivers installation with a yd201 (just for take a look about the wifi issue) and they are not compatible.
I guess modifying the inf files would do the trick.

Hi, I try to unlock LTE band, but su command doesn't work in terminal .... it said su: not found.

velociraptor68 said:
Hi, I try to unlock LTE band, but su command doesn't work in terminal .... it said su: not found.
Click to expand...
Click to collapse
Do you have root? Do you give root permission to Terminal Emulator?

Just did the procedure, can't confirm if it's working on 800MHz B20 yet because I can't find a way to force it or even know if its available in my region from my Network, because I live in the city and they use mostly the 1800MHz, 2G Only works correctly and it seems that somehow it also solves the Proximity Sensor, I will give feedback at how it behaves tomorrow when I will be on the move, but until now everything seems well and smooth, Many Thanks for the persons that worked on the fix, I guess Yota should be hiring! And to @TheArt who translates all the good stuff!

band17
Hello,
Would it work to unlock band 17 At&t? Is that enough modify config 6828 number by calculator?

Hello,
I am from Bosnia and got Yotaphone 2 from China (YD206) and installed latest RU software 1.132, but I noticed that my phone only works in big cities. As soon as I leave for the countryside, there is no signal/service.
Is there another version of software I can try to upgrade to, to get these bands in the countryside as well, or the problem is with the limitation of phone's hardware?
Thanks!

Miroslav1999 said:
Hello,
I am from Bosnia and got Yotaphone 2 from China (YD206) and installed latest RU software 1.132, but I noticed that my phone only works in big cities. As soon as I leave for the countryside, there is no signal/service.
Is there another version of software I can try to upgrade to, to get these bands in the countryside as well, or the problem is with the limitation of phone's hardware?
Thanks!
Click to expand...
Click to collapse
Whats the coverage in your contry?
Maybe outside big cities there are not mobile connection in the frequency that yotaphone can support

borekon said:
Whats the coverage in your contry?
Maybe outside big cities there are not mobile connection in the frequency that yotaphone can support
Click to expand...
Click to collapse
GSM : 900 (E-GSM) 1800 (DCS)
UMTS: B1(2100) UMTS B8 (900 GSM)
That is what I found out from google. I am not sure what is the better way to find out what Yota covers and what is available here.
If someone knows please let me know.
If I perhaps flash the phone with EU software rather than RU which I currently have, would that unlock some bands?

[GUIDE] How to enable additional LTE bands

This guide will add LTE bands 2, 4, 12, 17, 23, 28, to Motorola G5 XT1676. Other variants may work as well, but are not tested.
Other bands are possible, you need to copy those specific RFNV files and PolicyMan files from a phone that supports those bands to your device.
Disclaimer: Unlocking LTE bands may be illegal in your area. Please check local laws before doing so.
I am not responsible for bricked/damaged devices/angry service providers/FCC violations/fried radios/etc. as a result of these modifications. Use at your own risk.
Software included may be subject to copyright.
I was able to unlock US LTE bands on my XT1676 by copying calibration data to the modem's NVRAM from my XT1671.
Here is how to do so:
1. Install QPST and QXDM Professional and drivers. Follow guide https://forum.xda-developers.com/2015-moto-g/general/unlocking-bands-moto-g-2015-partially-t3283608 for driver install.
Google is your friend for finding QPST/QXDM. I used QPST Version 2.7 Build 460 and QXDM 03.12.714.
The driver I used was "Motorola QC Diag Port" - Version 5.1.0.0 (3/1/2013)
2. Install TWRP 64 bit
3. CRITICAL -- Backup your MODEM, MODEMST1 and MODEMST2 in TWRP.
If anything goes wrong, or if you want to revert - you need these backup files. I backed these files up using ADB inside TWRP.
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/backup/modem
dd if=/dev/block/bootdevice/by-name/modemst1 of=/sdcard/backup/modemst1
dd if=/dev/block/bootdevice/by-name/modemst2 of=/sdcard/backup/modemst2
4. Install an Oreo 64-bit rom and root your device
5. Boot device and enter diagnostic mode by entering the following commands into terminal or ADB over network.
su -c 'echo 0 > /sys/class/android_usb/android0/enable'
su -c 'echo 22B8 > /sys/class/android_usb/android0/idVendor'
su -c 'echo 2EC1 > /sys/class/android_usb/android0/idProduct'
su -c 'echo diag > /sys/class/android_usb/android0/f_diag/clients'
su -c 'echo diag > /sys/class/android_usb/android0/functions'
su -c 'echo 1 > /sys/class/android_usb/android0/enable'
6. Device will enter diag mode. Check that driver is installed in device manager. "Motorola QC Diag Port" under Ports (COM & LTP)
7. Open QXDM Professional, open NV browser. If dual sim device, check dual sim box and select sim slot you want to modify.
8. Adjust item 06828 to 17592185995263 in the input field and press write to upload the new value. This will unlock all LTE bands the device is calibrated for.
If your device already has calibration data for these bands, you may not need to perform the next steps. You can check your LTE bands using Network Signal Guru (Step 14)
To add calibration data:
9. Close QXDM, and Open QPST. go to Start Clients > EFS Explorer. Select your device from the window and use SPC code 000000
10. Navigate to EFS > NV > item_files > rfnv
11. Copy calibration data files (enablebands.zip) into RFNV. Do not overwrite if any already exist.
12. Return to EFS root, navigate to policyman.
13. Replace files device_config and rat_mask and rat_mask_Subscription01
These files are from an XT1671, and may limit or remove bands. You may need to find the device_config and rat_mask files from other Moto G5 variants if you want those bands.
14. Install netowrk signal guru (https://play.google.com/store/apps/details?id=com.qtrun.QuickTest&hl=en_US)
Enable desired LTE bands.
15. Reboot device, LTE should now work on those bands.
If you find your phone is screwed up, restore your backup of ModemST1 and ModemST2 using TWRP.
Restore by entering TWRP, connecting ADB and entering the following:
dd if=/sdcard/backup/modem of=/dev/block/bootdevice/by-name/modem
dd if=/sdcard/backup/modemst1 of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/backup/modemst2 of=/dev/block/bootdevice/by-name/modemst2
-------------------------------------------------------------------------------------------
The calibration data and policyman files from my XT1671 are attached as enablebands.zip
NV_Item spreadsheet is attached if anyone wants to identify LTE calibration data files from other G5 variants. This spreadsheet is not complete and is missing many files for some LTE bands, but it's all we have for now.
Also attached is SpecialCalibrationData.zip. The contents of these files differed across identical phones. I suspect each device gets its own calibration data at the factory for each band, and these files contain that data for certain bands. This could explain why the upstream signal is much weaker for band 4 on my patched XT1676 device than the XT1671 the calibration data was copied from. If anyone has any insight into these files, and how to fine-tune them to fix poor calibration issues - I'd love to hear it.
Good luck.

Awesome work, thanks for your time! I buy an xt1676 in Ukraine and live in Argentina. We use band 4 and 28 for LTE, but the xt1676 only have the band 28. I gonna try this and comment later.

Have you tried this on your XT1671? If so, would it enable Band 20 LTE on the XT1671? It seems like it should since the XT1676 has it natively.

bonchien said:
Have you tried this on your XT1671? If so, would it enable Band 20 LTE on the XT1671? It seems like it should since the XT1676 has it natively.
Click to expand...
Click to collapse
I imagine it would work. The hard part will be finding the B20 calibration data from the 1676's nvram.

Hey! I'm gonna try this, here in Argentina we almost don't have band 28 and it's annoying af. Do you have Telegram so I can contact you quickly? If you don't, can you create one? Is this *really* dangerous? Thanks a LOT

Just want to add that this works even on a Treble-enabled 32 bit Oreo ROM as well. My world-enabled xt1676 now supports US LTE bands much more effectively. Thanks jfarre20!

Do I need this in Europe/Germany?

Thanks a lot for this information (about the app Network Signal Guru). Finally I can lock the LTE bands that I don't want to use (very slow bands). A lot of months searching how to do it and finally I found it thanks to you. Really a lot of thanks sir.
Regards.

Suitable for Xiaomi Redmi Note 8 Pro?
krafg said:
Thanks a lot for this information (about the app Network Signal Guru). Finally I can lock the LTE bands that I don't want to use (very slow bands). A lot of months searching how to do it and finally I found it thanks to you. Really a lot of thanks sir.
Regards.
Click to expand...
Click to collapse
Would this work for Xiaomi Redmi Note 8 Pro? Please, give us some light! :fingers-crossed:

Will this work for a SD625 device, the Lenovo P2? I need b5 & b28 here in PH.

Can anybody confirm if this method actually works? I'd like to add LTE band 4 to my Motorola G5 XT1676.