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.
Related
*This is risky! I am not responsible for any damage to your device*
Download this zip http://d-h.st/0Me
Extract it and install QPST from that zip
Boot your Moto G into bootloader by powering off, then hold volume down while you power on
Select BP Tools by pressing volume down, then press volume up when hovering over BP Tools
Phone will reboot in diag mode (Nothing will look different in phones UI)
Make sure USB debugging is OFF
Go to device manager and make sure Motorola QC Diag is installed. If not go here http://forum.xda-developers.com/showpost.php?p=54338876&postcount=3
Press start button and navigate to QPST -> QPST Configuration. You should see your device there.
Navigate to QPST/bin and open RF_NV_Manager.exe *(C:\Program Files (x86)\Qualcomm\QPST\bin)
Continue on step 20 here http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
Make sure to check off your original bands before you add more!
My XT1032 went from this http://puu.sh/bAQMi/2f9bb440d0.png
To this http://puu.sh/bARDH/f6f182bea9.png
for the stock bands on the xt1032 + 1700mhz the Verizon pre-defined is what you want http://puu.sh/bBUq2/43ff4423c7.png
I do seem to be picking up tmobiles 1700mhz hspa now.
bpear96 said:
*This is risky! I am not responsible for any damage to your device*
Download this zip http://d-h.st/0Me
Extract it and install QPST from that zip
Boot your Moto G into bootloader by powering off, then hold volume down while you power on
Select BP Tools by pressing volume down, then press volume up when hovering over BP Tools
Phone will reboot in diag mode (Nothing will look different in phones UI)
Make sure USB debugging is OFF
Go to device manager and make sure Motorola QC Diag is installed. If not go here http://forum.xda-developers.com/showpost.php?p=54338876&postcount=3
Press start button and navigate to QPST -> QPST Configuration. You should see your device there.
Navigate to QPST/bin and open RV_NV_Manager.exe *(C:\Program Files (x86)\Qualcomm\QPST\bin)
Continue on step 20 here http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
My XT1032 went from this http://puu.sh/bAQMi/2f9bb440d0.png
To this http://puu.sh/bARDH/f6f182bea9.png
I do seem to be picking up tmobiles 1700mhz hspa now.
Click to expand...
Click to collapse
At #9 in folder C:\Program Files (x86)\Qualcomm\QPST\bin I cannot see RV_NV_Manager.exe the closest one is RF_NV_Manager.exe!!?
guliver365 said:
At #9 in folder C:\Program Files (x86)\Qualcomm\QPST\bin I cannot see RV_NV_Manager.exe the closest one is RF_NV_Manager.exe!!?
Click to expand...
Click to collapse
Yeah sorry RF_NV_Manager.exe is the correct program,
This phone is connecting to DC 42Mbps HSPA+ so confirms that 1700mhz aws is working.
Oh also for the stock bands on the xt1032 + 1700mhz the Verizon pre-defined is what you want http://puu.sh/bBUq2/43ff4423c7.png
bpear96 said:
Yeah sorry RF_NV_Manager.exe is the correct program,
Click to expand...
Click to collapse
got stuck now please redmyposthttp://forum.xda-developers.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269/page36
anyway here a copy
On a moto G XT 1045 LTE US
In a folder C:\Program Files (x86)\Qualcomm\QPST\bin I was not able to find RV_NV_Manager.exe but RF_NV_Manager.exe So I assumed RF_NV_Manager.exe could be used instead so I did and followed the guide usingMotorola Qc Diag port but on reboot at my place no service except LTE ( inside my home LTE does not stick) but no more HSPA or HSPA+ I probably selected only the Europe band in WDCMA column maybe I should added the US Band anyway when I tried to reverse it , RF_NV_Manager.exe stop in the middle of reading the phone with:
Exception Thrown!!
NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)
what i need to do it is ge tback my HSPA or HSPA+ band + add LTE for europe Helppppppppp!
guliver365 said:
got stuck now please redmyposthttp://forum.xda-developers.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269/page36
anyway here a copy
On a moto G XT 1045 LTE US
In a folder C:\Program Files (x86)\Qualcomm\QPST\bin I was not able to find RV_NV_Manager.exe but RF_NV_Manager.exe So I assumed RF_NV_Manager.exe could be used instead so I did and followed the guide usingMotorola Qc Diag port but on reboot at my place no service except LTE ( inside my home LTE does not stick) but no more HSPA or HSPA+ I probably selected only the Europe band in WDCMA column maybe I should added the US Band anyway when I tried to reverse it , RF_NV_Manager.exe stop in the middle of reading the phone with:
Exception Thrown!!
NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)
what i need to do it is ge tback my HSPA or HSPA+ band + add LTE for europe Helppppppppp!
Click to expand...
Click to collapse
What is the decimal nv code you wrote?
bpear96 said:
What is the decimal nv code you wrote?
Click to expand...
Click to collapse
Do you know your original decimal?
guliver365 said:
got stuck now please redmyposthttp://forum.xda-developers.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269/page36
anyway here a copy
On a moto G XT 1045 LTE US
In a folder C:\Program Files (x86)\Qualcomm\QPST\bin I was not able to find RV_NV_Manager.exe but RF_NV_Manager.exe So I assumed RF_NV_Manager.exe could be used instead so I did and followed the guide usingMotorola Qc Diag port but on reboot at my place no service except LTE ( inside my home LTE does not stick) but no more HSPA or HSPA+ I probably selected only the Europe band in WDCMA column maybe I should added the US Band anyway when I tried to reverse it , RF_NV_Manager.exe stop in the middle of reading the phone with:
Exception Thrown!!
NvManager::getNvItemsFromPhone( const string comPort ) - QpstServer::sendSyncImpl - Bad response from phone (DM packet commands 19-24)
what i need to do it is ge tback my HSPA or HSPA+ band + add LTE for europe Helppppppppp!
Click to expand...
Click to collapse
After a reboot, I think i am back in business what band should I enable to get HPA HPA+ and LTE all over the world?
You have to check your original bands too. You have less bands then stock now. Try this 844425063825536 http://puu.sh/bC4YM/0d68001e79.png
bpear96 said:
You have to check your original bands too. You have less bands then stock now. Try this 844425063825536 http://puu.sh/bC4YM/0d68001e79.png
Click to expand...
Click to collapse
Well I checked everything (2307813334319039360) now I got LTE at my place LLama can see 7cells tower from my place in USA , I used to get 2 only so it is already much better but do not know if LTE is working in France is there in the phone a place to see what frequencies are enabled?
QXDM for LTE
Well in fact i need a tutorial for using QXDM witch unlock LTE frequencies no Idea how I got better LTE reception by unlocking HSPA!
Are you all actually getting LTE??!! HOWW?!
mashaal95 said:
Are you all actually getting LTE??!! HOWW?!
Click to expand...
Click to collapse
My Moto G XT1045 is a LTE variant
---------- Post added at 07:12 PM ---------- Previous post was at 07:01 PM ----------
bpear96 said:
Do you know your original decimal?
Click to expand...
Click to collapse
For the time being I had to reversed it to the original 562950069289344 since 2307813334319039360 works for a while but all of sudden the radio turn off and no signal until next reboot did you experienced this behavior?
Can we get 42mbit maximum download speed for xt1033 using alternate values with this utility? Xt1033 max dl speed is 21mbit
I tried changing the decimal on my xt 1034, it accepted the changes, but I'm still stuck on edge here in Europe. Any ideas what went wrong?
Try to find an apk the name is
Network or 4G LTE Switch you should be able to change this
Sorry to sound stupid, can someone explain what this will do to me on a UK network using a XT1032?.
Sent from my Moto G using XDA Premium 4 mobile app
Do I need root to do this?
gunner4 said:
I tried changing the decimal on my xt 1034, it accepted the changes, but I'm still stuck on edge here in Europe. Any ideas what went wrong?
Click to expand...
Click to collapse
Hey, did you ever get this working on your xt1034, in the same boat myself with it stuck on edge
thanks
Paul
As I brought Band3 for NEXUS5, here, we are bringing 4G LTE band1 IMT 2100MHz for users such as, but
not limited to:
China Telecom,
Japan AU/NTT Docomo/Softbank,
Korea LG U+ /SK Telecom,
Philippines Smart,
Thailand DTAC/TrueMove-H
according http://en.wikipedia.org/wiki/List_of_LTE_networks#Asia and more:
Czech Republic Vodafone
Poland Play/P4
according http://en.wikipedia.org/wiki/List_of_LTE_networks#Europe
20150412 UPDATE: we are in Trial of more bands,as attachment names at POST#33:
Band 2 and band 4 for XT1100 View attachment 3257101
and Band 1 and band 8 or Band 1/9/19 or Band 1/8/9/19 for XT1103 View attachment 3257100
I am sorry below English language is not good, it is come from Google Translation^_^ from my Chinese post.
attachment docx is more clear since more detail images can are attched inside:
EN:View attachment 3187257
CN:View attachment 3187214
NEXUS 6 US MOTO XT1103 Band1 Enablement Tutorials
Foreword:
With the US version NEXUS6 XT1103 Chinese users, most of them come for China Telecom
, but is there such a telecommunications in many indoor shopping centers and car parks, do 4G LTE band1 2100MHz coverage, but also greater bandwidth than band3 15MHz with 20MHz bandwidth with China Telecom license.
What is a pity, XT1103 band1 RF front-end is shipped out without factory calibration, so only official usage is [email protected] only for China Telecom.In fact, as NEXUS5 band3 enablement, NEXUS6 RF front-end hardware also left a tiny space to enable it. The following tutorial is the first edition, With more extensive testing,It will needs correction on your demands.
I am sorry I do not have English version computer to reworks the Chinese screen captures,
I believe you have some way to understand around.
STEP1: using TWRP backup EFS
you can nexus6 of TWRP-Backup-EFS. More insurance after the phone Root, you canalso EFS Professional to backup your original EFS.
Thus, When need to restore the original state , Just use TWRP-Restore- to select the original EFS and slide the button to restore any changed below.
STEP2: Install the driver Moto BP Tools Driver
Mobile side: the phone off, then press the power button + volume down key, enter fastboot mode, use the volume keys to select BP Tools, and then turn the power button to confirm. Open usb diag device port.
{
"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"
}
View attachment 3187207 View attachment 3187208
1. Connect your phone to your computer, then prompted to install "diag_mdm" drive (or right-click "My Computer" and select "Properties" - "Device Manager" to install "diag_mdm" drive)
2. Right-click on the "diag_mdm", select "Update Driver Software" and then select "Browse my computer for driver software."
3. Select "choose from a list of device drivers in your computer."
4. Select "Show all devices", the "Next" button.
5. select "Disk"
6. Click "Browse"
7. Select the folder where you drive, point to open after selecting "momdm", then OK.
8. Select the "Motorola USB Diagnostic Port", click "Next."
9, warning, Click "Yes"
10, in the Device Manager port as shown below to show that the installation was successful (Note: The port number com93 vary)
STEP3: Write qcn
Phone side: the phone off, then press the power button + volume button, enter fastboot mode, use the volume keys to select BP Tools, and then turn the power button to confirm, so you can open the usb diag device port.
1.the installation QPST. Do not use lower version 2.7 build 422, otherwise it will not recognize the device. please find such installation by yourself.
2. open QPST configuration, the first point of Ports tab, select the device displayed, the first point below "remove", Prompt window popuped, and then point "Yes".
3, Chick "Add New Port".
4. Select the port of your device com port, and then "OK" button.
5, open the folder points QPST Software Download, click on "Restore" tab, click Browse to select the desired brush into qcn file:
View attachment XT1100_LTE_B1_To_XT1103_24226_6735_6736_RxAdded_TxOverrided.qcn.zip
(Here, the only difference vs nexus5 enabled band3 ,XT1103 purchased from Google Play, MOTO did not change default SPC, 000000),
Check Allow phone / file ESN mismatch, the final blow: Point Start, Errors box appears Could not Reset the Phone error normal, qcn has finished writing, after using the Power button off, then boot directly out LTE signal, the restart, do not use QuickBoot like Reboot, to ensure safety.
FINALLY: Check Whether Band1 Enablement successful methods
Method 1: Insert China telecom USIM cards, confirming a place where band1 with LTE Cell ID can be found with the end of HEX is 00,01,02,03,04,05 of LTE base stations (in the dial-up interface, enter * # * # 4636 # * # *, open "mobile phone information ", the" Set preferred network type "to LET ONLY, and then find the" Location: LAC = 7101 CID = 1924c01 "in this column, the CELL ID is inside this CID.
Method 2: Use the LTE Discovery watch band states.
NOTE: These two methods are there GCI (CID) guessing band, is only applicable to some of operators such as China Telecom, the absence of good planning China Unicom 4G CellID, and also China Mobile is not applicable for this .
[email protected]， we have LTE Discovery update to 3.19， support NEXUS6 display the real MODEM LTE Band!! thanks for Danial and his great team!!
While you want to Check real band PC tool QXDM may help if you have such tool, menu path is View-LTE- RRC layer-RRC/NAS Status Screen- Frequency band, wait for 10mintues for update or use airplane mode on/off to Tigger update.
In case you are not in LTE covered area, but just want to check the qcn is applied or not, reset your phone in boot loader mode, select BP TOOLS again,them use QXDM-view-NV Browser-Item 06828- read to get the value, it should be 1099830466655 for add band1 while stock default is 1099830466654,
Other qcn XT1103 add:
B1/8 1099830466783
B1/9/19 1099830729055
B1/8/9/19 1099830729183
XT1100 add:
B2/4 1099646632415, @default 1099646632405
Here we must thank:
Q39705630 enthusiastic and efficient testing and Draft this tutorial V0.1 version;
Q562552826 provide XT1103 of qcn file, doing preliminary analysis;
Q386499038 provide XT1100 qcn file, do the final release qcn file parameter reference;
Other Reference Tutorial IN Chinese:
1. CN version band1 enablement:
http://bbs.gfan.com/android-7863761-1-1.html
2.NEXUS6 RF parameters such as PC-side backup method qcn
http://bbs.gfan.com/android-7741730-1-1.html
3. Some tools on LTE band1 signal monitoring
http://bbs.gfan.com/android-7684876-1-1.html
。chinese here hei
Sent from my SPH-L720 using XDA Premium 4 mobile app
Could you send the xt1100'qcn to me? Q2954103426 . If I retore xt1100's qcn to xt1103, it only can make xt1103 support band same as xt1100?
Hi, I messed up my NV values and I can't get signal anymore. Can you please post original XT1103 QCN file so we can restore the backup? Thanks.
Done! Working here in philippines smart user here! Thanks OP!
MrDreamSky said:
。chinese here hei
Click to expand...
Click to collapse
Yes. I can not Choose where I was born, But I can choose whether I can contribute.
While American Dream is on the Sky, Chinese Dream is running on the ground even we are weak, I am expecting to contribute for the global. haha
MaxChuang said:
Could you send the xt1100'qcn to me? Q2954103426 . If I retore xt1100's qcn to xt1103, it only can make xt1103 support band same as xt1100?
Click to expand...
Click to collapse
No, you can not enable all the band but some, and it need some technical filtering job,
RF front end hardware is arm and body of RF driver software soul.
I will try to bring band8, but need more weeks to find time gap during my work.
messedupqcn said:
Hi, I messed up my NV values and I can't get signal anymore. Can you please post original XT1103 QCN file so we can restore the backup? Thanks.
Click to expand...
Click to collapse
Please note the normal QPST-Software Download backup qcn will not works for restoring,
and older QPST-RF NV Item manager backuped Qcn can not cover all RF nv now, so it is also not good choice for you to restore Solutions for your issue,
Soution1. In case you only lost your signal after you use 4636-Phone Info-Select UMTS band- US band, Try to set NV00441 to 0xFFFF with this qcn, by QPST-Software Download, an old post is here:
http://forum.xda-developers.com/nexus-6/help/help-locked-nexus-to-usa-band-t2975290/page2
Solution2. for others failture reason, To NEXUS6 reflash the factory images will help to reset all your nv from backup eMMC partition,
How to is here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Just wondering though, the com should be com93? Ir it could be any digit? Because i got com25 and i still insist it im flashing..it worked but it cannot tell the band im using that should be band 1.
Azlun said:
No, you can not enable all the band but some, and it need some technical filtering job,
RF front end hardware is arm and body of RF driver software soul.
I will try to bring band8, but need more weeks to find time gap during my work.
Click to expand...
Click to collapse
Thanks for your contribution !
I am curious if carrier aggregation can be configured ,too.
Yeah, I would like to know if carrier aggregation can be configured
Azlun said:
Please note the normal QPST-Software Download backup qcn will not works for restoring,
and older QPST-RF NV Item manager backuped Qcn can not cover all RF nv now, so it is also not good choice for you to restore Solutions for your issue,
Soution1. In case you only lost your signal after you use 4636-Phone Info-Select UMTS band- US band, Try to set NV00441 to 0xFFFF with this qcn, by QPST-Software Download, an old post is here:
http://forum.xda-developers.com/nexus-6/help/help-locked-nexus-to-usa-band-t2975290/page2
Solution2. for others failture reason, To NEXUS6 reflash the factory images will help to reset all your nv from backup eMMC partition,
How to is here: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks! Is fastboot flash radio enough to restore everything to normal? :laugh:
edit: looks like you have to reflash everything. Oh well.
---------- Post added at 06:28 AM ---------- Previous post was at 06:14 AM ----------
I restored the factory image and it's fine. There's a bug with the current factory image where it doesn't flash system and userdata when you run flash-all.sh, but it seems to have flashed the nv value backup without that. I didn't reflash system and userdata manually so I get to keep my phone without wiping.
Any idea why line 6828 in NV browser says 268501086 in my XT1103? According to LTE band calculator, this means the phone supports band 2/3/4/5/7/17/29. But Google Play says the phone supports 2/3/4/5/7/12/13/17/25/26/29/41. Any idea why this supports seemingly less bands?
Looks like some Moto X have this band configuration, but my Nexus 6 shouldn't. Can someone confirm their stock line 6828?
Will this change stick even after a firmware upgrade, say, after upgrading to Lollipop 5.1?
Is this technique applicable to a D820 Nexus 5 as well?
mimsiroll said:
Just wondering though, the com should be com93? Ir it could be any digit? Because i got com25 and i still insist it im flashing..it worked but it cannot tell the band im using that should be band 1.
Click to expand...
Click to collapse
COMxx is depand on PC, it can be any number.
messedupqcn said:
Thanks! Is fastboot flash radio enough to restore everything to normal? :laugh:
edit: looks like you have to reflash everything. Oh well.
---------- Post added at 06:28 AM ---------- Previous post was at 06:14 AM ----------
I restored the factory image and it's fine. There's a bug with the current factory image where it doesn't flash system and userdata when you run flash-all.sh, but it seems to have flashed the nv value backup without that. I didn't reflash system and userdata manually so I get to keep my phone without wiping.
Any idea why line 6828 in NV browser says 268501086 in my XT1103? According to LTE band calculator, this means the phone supports band 2/3/4/5/7/17/29. But Google Play says the phone supports 2/3/4/5/7/12/13/17/25/26/29/41. Any idea why this supports seemingly less bands?
Looks like some Moto X have this band configuration, but my Nexus 6 shouldn't. Can someone confirm their stock line 6828?
Click to expand...
Click to collapse
1: Is fastboot flash radio enough to restore everything to normal?
Az:I never try, may be you can try when you have enough partition backuped.
2. for nv6828, the stock default is 1099830466654
and after my qcn written, it should be changed to 1099830466655 (add band1)
in fact there is many other nv added and overrided, so a EFS backup before qcn write in is suggested.
I can not understand why your value become an unknow one.
<!-- Add Band1 in LTE bands over XT1103
default 1099830466654 decially = binary:
00000000 00000000 00000001 00000000 00010011 00000001 00011000 01011110B
(band 41 29/26/25 17 13/12 7/5/4/3/2 )
= 1099830466655 decially = binary:
00000000 00000000 00000001 00000000 00010011 00000001 00011000 01011111B
(band 41 29/26/25 17 13/12 7/5/4/3/2/!1!)
** other referenece,
ONLY Band8 = 128
-->
<NvItem id="6828" subscriptionid="0" name="NV_LTE_BC_CONFIG_I" mapping="direct" encoding="dec" index="0">1099830466655,0</NvItem>
Biggster said:
Will this change stick even after a firmware upgrade, say, after upgrading to Lollipop 5.1?
Is this technique applicable to a D820 Nexus 5 as well?
Click to expand...
Click to collapse
1 my NV items will be kept in EFS until a factory restore including erase EFS partition to trigger factory EFS restoring.
so OTA upgrade will be fine, but next factory image whole reflashing will erase nv items in this qcn.
That is MOTO design while LG NEXUS5 have not such issue.
2. NEXUS5 D820 can enabled band3 band8 in the same way if you are in track of http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561
but qcn in that post will NOT bring CDMA+LTE 1xSRLTE dual-stanby working, it is still in LTE only mode.
why NEXUS6 support 1xSRLTE is come from facotry by default, DI4.0 new modem firmware and trigger by right carrier_policy.xml from m_bing.
Hmm, I seem to remember my line 6828 was the same unknown value before I changed anything. Stock. Then when I flashed your qcn, it became the 1099830466655. I have no idea why my phone came with less bands stock. it is XT1103 Bought from moto US store. no way to test it either, until I am out of the US
Solved.
Anyone know how to get the SPC/MSL code if it's not all zeros? My N6 is Amazon sprint version but I'm using it out of US.
Sent from my Nexus ⑥
XT1100 to XT1103?
Is it possible to convert an XT1100 to an XT1103? Is it a hardware thing?
I would like to enable band 2 and 4 in the XT1100, is that at all possible?
I have both an XT1103 (borrowed) and my own, an XT1100. Could I copy the NV values from the 1103 onto the 1100? Would it cause any damage to try?
I dont mind formatting, but I also don't want a brick.
Thanks,
Sam.
How could I enable LTE band 4? Really thats the only one I need to enable. Any help is much appreciated. I am more than willing to test as well.
hi
my friends gave his n4 to enable LTE.. i tried lte enable zip but didnt go well.. and i cant read whole froum..
can any1 suggest me a rom (mm would be nice) having lte by default?
plz help me
Download the 1.07/.33 hybrid LTE modern from here
https://drive.google.com/folderview...&usp=sharing&tid=0B77BTW0zStYCSTRIYWpZQS1nOWs
Flash the hybrid modern in recovery, then go to the dialer and enter *#*#4636#*#*. Then go to phone information, scroll down to the network type, and choose lte/gsm auto. This will only work if your network provider supports lte on the band the nexus 4 supports, so please double check that.
here is my network specs :
https://en.m.wikipedia.org/wiki/List_of_LTE_networks
MTN Irancell 1800 3 FDD Nov 2014 10 MHz in use [1][608][609][610][611][612]
does it support?
and this link u gave me.. does it work on mm or lp 5.1.1 ?
ty for help
It should work on mm and lollipop. I'm not sure if it works on those bands, the only way is for you to try. If it doesn't work, just reflash the original modem for your rom.
LTE enabler zip 2.13 flashes hybrid modem and also changes settings. db so 4G appears in Settings/Cellular Network and preferred network type is permanently set to LTE/GSM/auto in Phone info.
So if you are not seeing this may be try flashing again. Flashing hybrid modem by itself does not force LTE setting.
Sent from my Nexus 4 using Tapatalk
CalculatedRisk said:
It should work on mm and lollipop. I'm not sure if it works on those bands, the only way is for you to try. If it doesn't work, just reflash the original modem for your rom.
Click to expand...
Click to collapse
The enabler script does NOT work on marshmallow/Android 6, FYI. I've had a hybrid modem on my phone and used LTE on both Android 4 and 5, but it's a no-go with 6. Even if you change the settings in the 4636 menu, but it doesn't make the modem actually change modes.
Check out this commit (referring to CyanogenMod 13, maybe other ROMs are different):
http://review.cyanogenmod.org/#/c/125897/1/overlay/frameworks/base/core/res/res/values/config.xml
Look at this string of available modem modes:
<string translatable="false" name="config_radio_access_family">GPRS|EDGE|UMTS|HSDPA|HSUPA|HSPA|HSPAP|GSM|WCDMA</string>
Notice how LTE isn't anywhere in that string? I think it needs to be to be able to use LTE. Otherwise switching to LTE mode in the 4636 menu doesn't work.
Thanks for letting me know, I'll keep that in mind.
Yeah, I just tried adding a local.prop file in /data with the following content:
Code:
telephony.lteOnGsmDevice=1
ro.telephony.default_network=9
ro.ril.def.preferred.network=9
which didn't work, so I then edited my /system/build.prop itself to insert that code (deleted the telephony.lteOnCdmaDevice=0 line as well), which also didn't work.
And neither worked. Switching to LTE/GSM (auto) in the 4636 menu has no effect, and when going into cellular networks to choose preferred mode, the only choices are 2G and 3G.
Damn it. I really like CM13, I don't want to move to some random AOSP build...
Yeah I hear you man. I think you'll just have to sit tight until they update it.
In order to make this good phone great it needed two things:
1. VoLTE - that was added by the MM update
2. For US, T-Mobile needs also the LTE band 12. This is VERY close to B17 (both 700MHz bands, blocks "a,b" for 12 and "b" for 17) so enabling it in the radio might work (analog side allowing the extra band). Asus filled with FCC test reports that show Band 12 as "passed" the testing. And somehow choose not to enable it.
What I did for now. I downloaded a package from around here that contains the Qualcom diag software QPST and QXDM Pro. Search for them.
1. Enable USB Debugging on the phone. Plug in the phone and the diag drivers will install (I'm on Windows 10 here, I have installed previously the drivers from Asus). Now the diag mode can be enabled in ADB:
ADB shell (should connect to the phone)
setprop sys.usb.config diag,adb
2. After drivers install automatically (Windows 10), the QPST server recognize the phone on COM4
3. Now the QXDM Pro can read the NV values. I am interested in LTE part - add B12. I recalculated the values for existing ones against the published specs and they matched, so the software that calculate the values seemed to work correctly. For LTE bands 1,2,3,4,5,7,8,17,20 the NV 06828 value is 590047. IMO nothing else need to change in the other sections of NV.
4. Calculated the new value with the band 12 added. New value that resulted is 592095. Insert the value in the field, pressed "Write". Then pressed "Read" and the value was there. Cool, now is time to reboot the phone, to activate the new value.
5. Phone rebooted, nothing different. Read again the NV 06828 and... it's back to the original value! Seems that at reboot the firmware rewrites that value. Not cool!!!
Now I am not sure if the drivers prevent the actual write to the chip or if the firmware re-writes at boot time the OE values.
Luk1337 stated that "/system/bin/rmt_storage overwrites the settings".
Maybe someone can patch that?
PS: This was my inspiration: http://forum.xda-developers.com/showpost.php?p=56577252&postcount=455
If someone is able to enable Band 12 in the firmware, do you think T-Mobile's network will recognize that a ZE551KL running Asus's official version of MM has VoLTE support and immediately allow those phones to use Band 12?
Yes, it has VoLTE now (CM13 too), it is just missing the B12 for T-Mobile.
LE: On CM13 Enhanced LTE is available starting with the 20160707 nightly.
SoNic67 said:
Yes, it has VoLTE now (CM13 too), it is just missing the B12 for T-Mobile.
Click to expand...
Click to collapse
We don't have VoLTE in CM fyi. You just had a testing build with it.
Sorry. Forgot that I was special . I was using lately the SIM in my other phone (that has band 12), so I didn't noticed.
PS: It's the future though, every carrier wants to get rid of all different standards and simplify - LTE equipment is common for everyone.
Update:
Since I had another Snapdragon device, I decided to try it on that too. It's an Alcatel Onetouch Fierce XL sold by MetroPCS (T-Mobile network in US) - Snapdragon 210, MSM8909, Alcatel 5054N. The FCC registration for that phone shows LTE bands 2, 4, 5, 7, 12. The phone has natively Enhanced LTE which include VoLTE and HD audio. Also it has WiFi calling.
Good stuff.
I tried the same procedure as above and read the NV06828. In the MetroPCS phone this was 2058. Using the calculator I find out that the active bands are only 2, 4, 12 (the bands that T-Mobile operates).
Well, band 5 and 17 are needed for AT&T/Cricket (well maybe I needed to add only 5, since AT&T was forced recently by FCC to allow band 12 devices on it's band 17 and they even started selling band 12 devices).
So I did go ahead and change the NV06828 with the new value. Write, Reboot, Read... The setting "sticked"! Now, I don't have a way to test the actual functionality since I would need a Cricket SIM and drive away in a area served only by band 5, but I have a feeling that it will work (because FCC registration includes that band, I assume that the hardware can handle it).
The stock FW, when presented with the "setprop sys.usb.config diag,adb", it just closes the ADB connection, so I cannot enter diag mode like in CM13.
UPDATE: Since I have moved today to AT&T, I don't need the B12 anymore.
However, the stupidity of Asus is overwhelming - the FCC testing letter includes the B12 (passed) for the ZE551KL (Z00TD):
https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm
Search for the FCCID: MSQ Z00TD and hit one of the 700MHz reports. You will get the attached pdf.
Even if OP gave up, some people like me still wants to enable some bands back too.
If you find something, please post (guides, clues, etc) it here.
SoNic67 said:
UPDATE: Since I have moved today to AT&T, I don't need the B12 anymore.
However, the stupidity of Asus is overwhelming - the FCC testing letter includes the B12 (passed) for the ZE551KL (Z00TD):
https://apps.fcc.gov/oetcf/eas/reports/GenericSearch.cfm
Search for the FCCID: MSQ Z00TD and hit one of the 700MHz reports. You will get the attached pdf.
Click to expand...
Click to collapse
It's stupid for clients like us for sure, but for Asus it's market segmentation and planned obsolescence.
I'm the OP. I have asked a support question and Asus said this:
Sorry for the inconvenience and I'll convey your request to the related department for further help on this issue.
Click to expand...
Click to collapse
Whatever...
I have decided to sell my Asus. Sure, I lost money by doing this (the guy who bought it is happy about that I guess), but I now know better than buy from Asus anything. I thought it will be a great unlocked phone, but Asus managed to screw it up for me in several ways. They might fix this issue in later firmware updates, or they might not. I just don't have patience.
It might be a great phone for many users around here, more power to them.
PS: For future reference, those are the original NV values:
Code:
For Asus ZE551KL (Z00TD)
ID Description Name Category Size Value
01877 RF Band Configuration rf_bc_config CDMA 64 562950069289856
00441 Band Class Preference band_pref CDMA 8 0
16 0x380
00946 Expand Band Preference band_pref_16_31 System 8 0
16 0x0EE8
02954 Bits 32 to 63 Of Band Pref band_pref_32_63 System 8 0
32 268566528
06828 LTE BC Config LTE_BC_CONFIG_type.lte.config UINT64 64 590047
LTE_BC_CONFIG_type.lte.config_extUINT64 64 0
06829 LTE BC Config DIV lte_bc_config_div UINT64 64 0
UINT64 64 0
Change to add B12 (but reverts to stock at reboot):
06828 592095
SoNic67 said:
I'm the OP. I have asked a support question and Asus said this:
Whatever...
Click to expand...
Click to collapse
Obviously some pure bull**** from Asus...
SoNic67 said:
I have decided to sell my Asus. Sure, I lost money by doing this (the guy who bought it is happy about that I guess), but I now know better than buy from Asus anything. I thought it will be a great unlocked phone, but Asus managed to screw it up for me in several ways. They might fix this issue in later firmware updates, or they might not. I just don't have patience.
It might be a great phone for many users around here, more power to them.
PS: For future reference, those are the original NV values:
Code:
For Asus ZE551KL (Z00TD)
ID Description Name Category Size Value
01877 RF Band Configuration rf_bc_config CDMA 64 562950069289856
00441 Band Class Preference band_pref CDMA 8 0
16 0x380
00946 Expand Band Preference band_pref_16_31 System 8 0
16 0x0EE8
02954 Bits 32 to 63 Of Band Pref band_pref_32_63 System 8 0
32 268566528
06828 LTE BC Config LTE_BC_CONFIG_type.lte.config UINT64 64 590047
LTE_BC_CONFIG_type.lte.config_extUINT64 64 0
06829 LTE BC Config DIV lte_bc_config_div UINT64 64 0
UINT64 64 0
Change to add B12 (but reverts to stock at reboot):
06828 592095
Click to expand...
Click to collapse
Thanks for the reply and sorry for the delay !
How did you find these values ? Do you have any sources ?
My guess is your modifications always gets erased on reboot because something is write-protected like the RIL, RUU (HTC), CSC (Samsung), etc. It happens on most branded phones an that's a real bummer.
So the next step would be to unlock that part, unfortunately I'm only able to do that on branded HTCs and Samsung phones. But there may be a generic way to do it through adb shell or fastboot for not branded phones ?
Edit: The closest way I've found for that comes from that topic: http://forum.xda-developers.com/zenfone-2-laser/help/ze550kl-stuck-edge-modem-reflashing-t3427402
Values are read by me from my device and hand written in a file.
However, like I said above, I have moved on (to a Moto G4 Plus)...
SoNic67 said:
Values are read by me from my device and hand written in a file.
However, like I said above, I have moved on (to a Moto G4 Plus)...
Click to expand...
Click to collapse
Oh sorry, by sources I mean do you have any links showing you how to change these values ?
Same for links showing you what are the values, where the files are, etc.
Anything is good
First post.
is there a way today to unlock all bands. i just bought the zenfone 2 laser, i can install cyanogenmod 13 on it, but is there a tutorial how to unlock bands once i install cyanogenmod 13?
thank you
Ben
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?