Related
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.
..
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?
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.
Have anyone tried this method ?
I tried it recently. Did everything correctly, but after rebooting the device ; no effect.!!
:crying:
So i rechecked again via QXDM for LTE BC CONFIG & LTE BC CONFIG DIV for the values,it was the same which i gave
So, Anyone tried ?
Got it working ?
or
Same Result as mine ?
Hello. I am trying hard to add LTE band 4 to this device. I have QPST "talking" to the phone and QXDM "talking" to QPST's service programming. But when I try to read almost any item, I get an error - Item Not Active (or something like that). I am using the latest QPST I can find 2.7.474 and the latest QXDM I can find 3.14.594. This all worked fine against my test phone - a Note 3 - but I am getting nowhere fast with the Zenfone. Perhaps it is because the Zenfone is 64 bit and the tools I have are not new enough? I welcome any suggestions. Thanks
Nokia, OnePlus and Asus Zenfone Max Pro M1 does not have a programmable radio firmware like Motorola via QPST, QXDM. Network parameters are pre-installed in mcfg_sw.mbn files, also the per carrier volte parameters are embedded in this folder. mcfg_sw.mbn files can be deleted and installed by QFIL in QPST. Nokia 1 , an entry level phone has LTE band 41 which Asus does not. These files no not contain any serial numbers or IMEI mappings so can be flashed. A few guides are there for Pixel phones where they have used OnePlus mcfg_sw.mbn to enable German carrier VOLTE. The available bands in Asus Zenfone Max Pro can be locked unlocked by Network Signal Guru APK after root.
dr.faramroze said:
Nokia, OnePlus and Asus Zenfone Max Pro M1 does not have a programmable radio firmware like Motorola via QPST, QXDM. Network parameters are pre-installed in mcfg_sw.mbn files, also the per carrier volte parameters are embedded in this folder. mcfg_sw.mbn files can be deleted and installed by QFIL in QPST. Nokia 1 , an entry level phone has LTE band 41 which Asus does not. These files no not contain any serial numbers or IMEI mappings so can be flashed. A few guides are there for Pixel phones where they have used OnePlus mcfg_sw.mbn to enable German carrier VOLTE. The available bands in Asus Zenfone Max Pro can be locked unlocked by Network Signal Guru APK after root.
Click to expand...
Click to collapse
Thanks for this tip/info. A friend of mine, not understanding, purchased an Asus Zenfone Max Pro M1 for himself that was made for use in India (I think). But he is in the USA on T-Mobile and needs different frequency bands that those that are supported. Because he has to use a TMobile CellSpot device at his home (due to no signal from any towers) he needs:
Band 4 LTE (2100 MHz)
Band 2 UMTS/WCDMA/HSPA (1900 MHz)
And neither of these are supported on the model he purchased. I was hoping to succeed in adding LTE 4 to his device using the Qualcomm tools. But I was not successful in doing so. Following some online guides I was able to change the supported LTE bands on an old Note 3 (not able to actually test them though) so that Network Signal Guru showed them in its list of frequencies. But I could not even read the data for this on the Zenfone. From what you say this now makes some sense to me.
Is it somehow possible to add these bands (at least the LTE 4) to the Zenfone? I know the Network Signal Guru can block bands. But I did not think it could add or remove them. If you can point me to something regarding this process, if possible, that would be great. Thanks
dr.faramroze said:
Nokia, OnePlus and Asus Zenfone Max Pro M1 does not have a programmable radio firmware like Motorola via QPST, QXDM. Network parameters are pre-installed in mcfg_sw.mbn files, also the per carrier volte parameters are embedded in this folder. mcfg_sw.mbn files can be deleted and installed by QFIL in QPST. Nokia 1 , an entry level phone has LTE band 41 which Asus does not. These files no not contain any serial numbers or IMEI mappings so can be flashed. A few guides are there for Pixel phones where they have used OnePlus mcfg_sw.mbn to enable German carrier VOLTE. The available bands in Asus Zenfone Max Pro can be locked unlocked by Network Signal Guru APK after root.
Click to expand...
Click to collapse
Just went looking again for Network Signal Guru on Play Store. It no longer exists! Even the link at QTRUN no longer works. Rats! Anyone have a good source for this or know what happened here?
You mean this? My backup from what was available on the playstore last month.....can be trusted.
MD5 Checksum ccfb4ab7ddd9708b2299c57d7e74b654
SHA-1 Checksum f6e99855875c35ad64d7b51c21a95b1fee135c5d
Cookie Ninja said:
You mean this? My backup from what was available on the playstore last month.....can be trusted.
MD5 Checksum ccfb4ab7ddd9708b2299c57d7e74b654
SHA-1 Checksum f6e99855875c35ad64d7b51c21a95b1fee135c5d
Click to expand...
Click to collapse
Yes indeed. Thanks very much!
If you are facing problems of poor natwork whatever network on are u there is something for you to get Best network coverage
There are money tips n tricks are making round all over the internet
I'm also the one of them who has searched n searched on google about jio network
Than i found artical about network band
Band 3(1800)
Band 5(850)
Band 40(2300)
All above all are Lte band is jio provide to us
In my case I'll always get band 40 it's slowest band in my area why beacuse a phone automatically switches between band according to the strength of the signal in different locations
So 1thing i know that i have to control my network band or lock band 40
Than i searched and searched on google
I have read lot of article about changing your band easily
Read about different code for different mobile
For example *#*#4636#*#* or phone info to select network mode lte only nothing change same result
Than shortcut master to creat "service menu" or "Engineering mode" still no luck with different 2 device
Than *#001# it's work but can't change or lock anything
Than i finally found on Xda a magical code *#2263#
this is really magical code for Samsung devices
If it is work for you than you don't need any apps or U don't need to root your phone
Stil no luck
It doesn't work on my phone
Than searched about how to make this code to work i found small artical on xda and it's work
But you need root to access system file this guide is not work for non-rooted samsung phone
i have just tested on my s7 cutome rom of kill-switch black diomaond v7
So u need esfile explore
To perform this action
In Esfile explore goto
System/csc/etc Or System/omc/INS itc
Now look for the file name with
INS_keystrings.dat and rename it to something like xyz.keystrings.dat
Now go back to System/omc/XXV/etc and copy the xxv_keystrings.dat and paste the same where u have change file name
Omc/ins/etc and rename it INS_keystrings.dat now reboot phone
And U will see *#2263# code will stated to run
Now u can chhose any band you want or lock any band which u don't want
Note:-- what if you dont have xxv or sin csc than you look for xxv or sin csc and flash it
I think it will work without above trick but it doesn't than do it manually