Database Users

[MYSTERY] Unlocked SGS can't make calls

I recently bought a second-hand SGS, supposedly locked to 3. The firmware was from 3 UK, but when I punched in *#7465625# it showed all locks are OFF.
Hot for tasty Froyo, first thing i did was to upgrade from the branded Eclair ROM the phone came with to an unbranded stock Froyo ROM. Kies gave me a hard time so I used ODIN. Then I inserted my SIM and realized I could not make calls or even register on my GSM network. (Had not tried the SIM before, so I don't know if the flash caused this)
I found out that the flash had changed my Product Code to KOR, but I managed to change it using THIS GUIDE. However, the step "rm -rf /efs/nv_data.bin.md5" did not work as it was write/read protected. After reboot, the SIM didn't work so I did the "busybox chown 1001:1001 /efs/nv_data.bin". The procedure changed the Pcode to H3G, which I think is the original code, although I was going for XEE.
IMEI has not changed (*#06# gets same no. as is printed below battery)
I live in Sweden, my present CSC is XEE, Product Code is H3G. Network Control Key is 00000000, could this be related?
I considering doing the Product Code change procedure again and see if I can change it too XEE hoping that will fix it, but I'm not even sure this is related to my problem.
Other than that, I'm running out of ideas. However, I'm new to the SGS scene. I'm reaching out for someone with more experience to give me some new ideas.
I've spent hours and hours at this and I've googled like possessed. If I'm being a noob or have overlooked something, let me know - just tell me what I should do to fix this phone.

Go into Settings > Wireless and Network > Mobile Networks and check that Network Mode reads as auto mode. Then open Access Points Names and check that APNs are listed that suit your carrier.
If all of that checks out, go into an app like SGS Tools and use the secret code to check Band Selection.

Thanks for your reply!
I have inserted APN for data. Though, is this really necessary just for 2G calls and SMS?
When I choose "Select Automatically" in Settings/Wireless and network/Mobile Networks/Network Operators then I sometimes get "Registered on network". Then, when trying to call, I get "Data network not available". Band Selection (from SGS Tools secret codes) show:
= BAND SELECTION =
[1] AUTOMATIC []
[2] WSCDMA BAND []
[3] GSM BAND []
[4] COMBI BANDS []
When I select the network operator manually, I get "Unable to select network. Select automatically".

An alternative Go to Rom Kitchen build a rom with
XWJS8 > Hardcore Kernel >CSC CPW > Modem JPY and whatever else you require that should give all UK main networks .
http://romkitchen.org/sgs/?s=generator
jje

losdrivare said:
Thanks for your reply!
I have inserted APN for data. Though, is this really necessary just for 2G calls and SMS?
When I choose "Select Automatically" in Settings/Wireless and network/Mobile Networks/Network Operators then I sometimes get "Registered on network". Then, when trying to call, I get "Data network not available". Band Selection (from SGS Tools secret codes) show:
= BAND SELECTION =
[1] AUTOMATIC []
[2] WSCDMA BAND []
[3] GSM BAND []
[4] COMBI BANDS []
When I select the network operator manually, I get "Unable to select network. Select automatically".
Click to expand...
Click to collapse
I got Data Network not available when I was investigating my phone (that is, messing about) and changed my Network Mode. Go to Settings > Wireless and Network > Network Mode and choose GSM/WCDMA Auto mode. If you don't have connection, then try first GSM Only, then WCDMA Only...then back to both.
And yes, you need to have a data network connection to make calls. Not sure why. Must be something to do with billing.

I would hate to be right but are you sure, as you've bought it second hand, that it hasn't been registered as stolen? Do you know any history of the phone?

Product code should be GT-I9000HKDXXX, where XXX should be your CSC which is XEE that makes it: GT-I9000HKDXEE, you should not use H3G at all.

double post...sorry

JJEgan said:
An alternative Go to Rom Kitchen build a rom with
XWJS8 > Hardcore Kernel >CSC CPW > Modem JPY and whatever else you require that should give all UK main networks .
Click to expand...
Click to collapse
Thanks, but I would need the Swedish networks. The phone is from UK whereas I live in Sweden and have a Swedish operator (halebop).
rschenck said:
I got Data Network not available when I was investigating my phone (that is, messing about) and changed my Network Mode. Go to Settings > Wireless and Network > Network Mode and choose GSM/WCDMA Auto mode. If you don't have connection, then try first GSM Only, then WCDMA Only...then back to both.
And yes, you need to have a data network connection to make calls. Not sure why. Must be something to do with billing.
Click to expand...
Click to collapse
Weird, I was sure APN is only required for MMS and Internet, not for calls and SMS. Anyway, I have APN so that's not it.
ross_ctr said:
I would hate to be right but are you sure, as you've bought it second hand, that it hasn't been registered as stolen? Do you know any history of the phone?
Click to expand...
Click to collapse
No, I don't and I can't be 100% sure it's not stolen. However, I have a bill of sale with all his information and I know where he lives so if that's the case, it can be sorted.
[Ramad] said:
Product code should be GT-I9000HKDXXX, where XXX should be your CSC which is XEE that makes it: GT-I9000HKDXEE, you should not use H3G at all.
Click to expand...
Click to collapse
I think you are right, and I managed to change it so now both CSC and Product Code reads XEE, which should be correct for Sweden. However, the problem remains the same.

There is a possible solution from HERE, however it seems rather ...old. Having no other ideas I'll try it unless someone comes up with a better idea:
Richthofen said:
Possible problems (I had them all due trying different thing to solve it):
No service.
There is no service even a functional SIM card is inserted.
You cannot receive or make calls, receive or send sms, etc (obviously).
Freeze / lock-down.
The phone will not react to anything besides pressing power key.
You cannot unlock the display to enter PIN code.
Wrong PIN code.
The phone will not accept any PIN code on any SIM (even the correct one ).
Phone displays "wrong PIN code" message even the try counter (three strikes you know) does not change.
Product code changed to KOR.
= Blocked Kies updates (without a registry "hack")
Here is how to fix any or all of them:
Downgrade to I9000XWJM9 firmware with Odin (as usual).
Remove SIM card from the phone (to be able to boot in first place) and start the phone.
Gain root access and install "Root Explorer" (or similar), ADB works too.
Open Root Explorer and go to the "EFS" folder in the root.
Check the date on .nv_data.bak and .nv_data.bak.md5 files.
If it is earlier than 08/26/2010 you´re clear, if it is later then you may stop reading.
Once the date has been checked, select files nv_data.bin and nv_data.bin.md5 simultaneously and delete (yes, delete) them. Reboot the phone.
Now your phone is in the same condition (atleast permanent memory wise) as it was prior I9000XXJPC update.
There is a safety feature I would call "a dead mans switch".
If the current nv_data files are deleted, the phone will make new nv_data files from the .bak (backup) files (if they excist). The new nv_data files will be signed automatically so they pass the checks (none of the errors listed above will occur). However if they do not excist, the phone will just write an empty / test file (= IMEI corrupted, no service, etc). Also if you just rename .bak files they will have wrong signatures and the same problems will occur.
There is no bootloaders included, so it is safe to flash for everyone.
Click to expand...
Click to collapse

Have you tried doing a factory reset? May not work but may be worth a try.
Could only be either apn related (doubtful), faulty sim or stolen/lost phone. Unless hardware related.
Sent from my GT-I9000 using XDA App

losdrivare said:
Thanks, but I would need the Swedish networks. The phone is from UK whereas I live in Sweden and have a Swedish operator (halebop).
XEE-JS1 Nordic (default XWJS7) CSC then .
jje
Click to expand...
Click to collapse

JJEgan said:
losdrivare said:
Thanks, but I would need the Swedish networks. The phone is from UK whereas I live in Sweden and have a Swedish operator (halebop).
XEE-JS1 Nordic (default XWJS7) CSC then .
jje
Click to expand...
Click to collapse
Thanks, it seems a long shot but I will try it tomorrow.
I've already flashed the phone to XWJM9 with correct CSC folllowing the guide in my previous post. Restoring nv_data.bin and nv_data.bin.md5 from the .bak files didn't help, the .bak files were just three days old so the data there might have been contaminated.
As far as I can tell there's either a hardware fault, the phone is stolen, or I've messed up the precious data in /EFS by my first ODIN flash, before I did the back-up. Every guide should have that backup procedure as first step, mine didn't. :'(
I've mailed my operator so hopefully I'll get an answer tomorrow to whether the IMEI is blocked.
"No service" sucks...
Click to expand...
Click to collapse

How modify a qcn file to enable AWS band

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

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

..

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

..

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

..

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

..

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

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

..

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

..

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

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

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

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

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

..

Yotaphone 2 signal boost trick/unlock band ?

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

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

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

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

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

seems cool! We have to test

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

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

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

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

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

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

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

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

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

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

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

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

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

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

How to force 4G only (LTE only) Mode?

Can someone help me I am trying to force my Huawei P10 Plus to use LTE/4G only mode. I have latest Firmware/Patch Level.
I have tryed many service codes in format like *#*#.....#*#* codes but I can not set the LTE Only mode.
Isn't it possible without "root"?

It is possible to force "4G only" without root. First download "Setting Database Editor" from playstore. Open it and look for "hw_networkmode_preferences". I use this value "9,3,2,1,11" on my phone. Save it and restart your phone. If you still don't get "4G only" option then you need to open the "Setting Database Editor" again and look for "hw_add_4g_only". Mine was set to "250". You need to change it according to your country mobile code. Look for your mobile country code here: https://en.wikipedia.org/wiki/Mobile_country_code. In my case I change the value to "250;502" since 502 is my country code. Save it and restart your phone.
Tested on rebranded P10 Plus 256GB.

jula182 said:
It is possible to force "4G only" without root. First download "Setting Database Editor" from playstore. Open it and look for "hw_networkmode_preferences". I use this value "9,3,2,1,11" on my phone. Save it and restart your phone. If you still don't get "4G only" option then you need to open the "Setting Database Editor" again and look for "hw_add_4g_only". Mine was set to "250". You need to change it according to your country mobile code. Look for your mobile country code here: <1. o prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!>. In my case I change the value to "250;502" since 502 is my country code. Save it and restart your phone.
Tested on rebranded P10 Plus 256GB.
Click to expand...
Click to collapse
Thank you very much for your Help! I already installed the DB Settings Editor and found out that hw_networkmode_preferences were already "9,3,2,1,11" so this wasn't the case. Additionally I found that I have to add "hw_add_4g_only" so I added it with the wrong Country Code because I didn't know what the hw_add_4g_only means. I was searching for it a few days now and never got an answer, so I was trying to ask here. And you made it clear now. The Wikipedia Link was very helpful and it works now for my Country. I have to set it 262 for O2 Telefonic Germany.
So again Thank you very very much!

Using Huawei P10 (VTR-L29) 8.0.0.374 (185) solution above works for me too.

jula182 said:
It is possible to force "4G only" without root. First download "Setting Database Editor" from playstore. Open it and look for "hw_networkmode_preferences". I use this value "9,3,2,1,11" on my phone. Save it and restart your phone.]
For me, It works. Huawei P10 Lite
Thanks
Click to expand...
Click to collapse

Worked on my Samsung Galaxy S9

Honor 6X is stubborn as heel... Nothing works.
Can't even find the commands... Sigh!

First Method :
1. Use SIM 1 as the default connection setting
2.
You need to install this app for FREE
at Google Play
https://play.google.com/store/apps/details?id=com.teknokia.force4glteonly
pro version : https://play.google.com/store/apps/details?id=com.teknokia.force4glteonlypro
galaxy store: https://apps.samsung.com/appquery/appDetail.as?appId=com.teknokia.force4glteonly
pro version : https://apps.samsung.com/appquery/appDetail.as?appId=com.teknokia.force4glteonlypro
3. Run the application, press the SIM 1 only or Android testing button. You will enter two LTE Switcher options and also 2 Android testing options.
4. You can try all of them which support your phone.
If the telecommunication operator you are using does not support VoLTE (Voice over LTE) and uses LTE Only Mode, so regular calls will be blocked.
Second Method :
1. DOWNLOAD Force 4G LTE Only 2020 Pro application from Google Play
2. Run the Application
3. Select SIM 1 Only menu, then Hidden Activity
4. wait to load until 100%
5. tap the search box type RadioInfo
6. In the DEvice Info app section, there is a RadioInfo activity.
7. Long Tap 3 options will appear: Create Shortcut, Launch Activity, Edit Shortcut. I recommend Select Create Shortcut to make it easier for us to enter network activity mode without having to bother opening the Force 4G LTE Only 2020 Pro application.
8. Please select Launch Activity to enter the Radio Info
9. Select LTE Only in set preferred network type

I was able to get it working on my huawei y7a sometime last year using settings database editor. Abouy 2 weeks ago i factory reset my device due to an unrelated issue and now when i try to enable it again i get an error saying my system software has rejected the edit. I tried with the version of setedit from f-droid and got the following "Unexpected failure you shouldn't not change private system settings." does anyone know what the problem could be?

K.Hatake said:
I was able to get it working on my huawei y7a sometime last year using settings database editor. Abouy 2 weeks ago i factory reset my device due to an unrelated issue and now when i try to enable it again i get an error saying my system software has rejected the edit. I tried with the version of setedit from f-droid and got the following "Unexpected failure you shouldn't not change private system settings." does anyone know what the problem could be?
Click to expand...
Click to collapse
I have the same issue with p30 pro. It seems to me that after some recent updates, they've locked those settings somehow.

alesu69 said:
I have the same issue with p30 pro. It seems to me that after some recent updates, they've locked those settings somehow.
Click to expand...
Click to collapse
did you find the solution for this problem because i have the same issue and i get the error message from setedit if you have the solution plz respond to me . thx

Make a shortcut to the activity .settings.radioInfo (phone info) of the app com.android.phone (telephone)

namous zakarya said:
did you find the solution for this problem because i have the same issue and i get the error message from setedit if you have the solution plz respond to me . thx
Click to expand...
Click to collapse
I found a solution. You would have to use "Adb shell" (usb debugging).
The code is:
adb shell settings put system hw_networkmode_preference 11

Techie0fficial said:
I found a solution. You would have to use "Adb shell" (usb debugging).
The code is:
adb shell settings put system hw_networkmode_preference 11
Click to expand...
Click to collapse
This worked for me. Thanks

Oxygen OS, root, APN and the meaning of life

Hi All,
I appeal to you keepers of the knowledge to enlight me on some points I need to clarify.
The situation:
I recently bought an unbranded Oneplus 6T and I (still) use stock oxygen OS V9.0.17.
Since a couple of years I've been using a data-only plan with a VOIP SIP account as my main phone service. It was working great on my beloved almost-6-years-old Nexus 5 until I dropped it to it's death. I chose the 6T as replacement because it seemed a good option for rooting and custom ROMs.
My service provider is FIDO in Canada. They offer a very good value data-only plan (15$ CAD for 4GB), but for an UNKNOWN reason to me, with FIDO the SIP calls drop automatically if I use the default autoconfigured APN for LTE. The simple solution to that is to create a new empty APN config and fill it manually. Once done, SIP calls work like a charm (again, I don't know what causes this).
On my Nexus, I was running Android 8.0 which permitted me to modify the APN. But since Android 8.1 Google (don't be evil right) introduced the APN locking for participating providers. FIDO seems to be one of them since I cannot change any APN configuration on Oxygen OS 9.0.17. That renders my phone useless (unless I choose the 3G apn, which honestly sucks).
Now that you know a little bit about my life, here are my questions.
First thing I did:
I rooted my phone with Magisk 20.0 with the intention of modifying the /system/etc/apns-conf.xml and try changing the default FIDO APN configuration with the hope it would work.
I tried by many ways to modify it (using ADB, root browser, root explorer, solid explorer) and I couldn't change the content. Even worse, when I tried to change the permissions to the file to RW using root explorer, the file turned empty (0b) and it's still impossible to modify it (I tried editing it, deleting, replacing it, nothing works).
Question 1: The simplest of ways would be to be able to change the APN. Does anybody knows a trick (using root or not) to do that on stock OOS 9.0.17. Anybody ever tried changing apns-conf.xml?
Question 2: Did anybody succefylly edit system files onstock OOS 9.0.17 using root?
Question 2-A: Does anybody know why I break the file when I change the permission? I'd like to understand what's going on.
Another option that I am considering is using a custom ROM that disables this nonsense APN lock mechanism.
Question 3: Does anybody have a good ROM suggestion that is positively disabling this APN lock and that would allow me to change my APN with FIDO? (I was considering Lineage but I couldn't get a firm answer on the APN unlock capability).
I searched the web for many hours without success, I hope you can help me with this.
Thank you all for your insight.

jfmartel said:
Hi All,
I appeal to you keepers of the knowledge to enlight me on some points I need to clarify.
The situation:
I recently bought an unbranded Oneplus 6T and I (still) use stock oxygen OS V9.0.17.
Since a couple of years I've been using a data-only plan with a VOIP SIP account as my main phone service. It was working great on my beloved almost-6-years-old Nexus 5 until I dropped it to it's death. I chose the 6T as replacement because it seemed a good option for rooting and custom ROMs.
My service provider is FIDO in Canada. They offer a very good value data-only plan (15$ CAD for 4GB), but for an UNKNOWN reason to me, with FIDO the SIP calls drop automatically if I use the default autoconfigured APN for LTE. The simple solution to that is to create a new empty APN config and fill it manually. Once done, SIP calls work like a charm (again, I don't know what causes this).
On my Nexus, I was running Android 8.0 which permitted me to modify the APN. But since Android 8.1 Google (don't be evil right) introduced the APN locking for participating providers. FIDO seems to be one of them since I cannot change any APN configuration on Oxygen OS 9.0.17. That renders my phone useless (unless I choose the 3G apn, which honestly sucks).
Now that you know a little bit about my life, here are my questions.
First thing I did:
I rooted my phone with Magisk 20.0 with the intention of modifying the /system/etc/apns-conf.xml and try changing the default FIDO APN configuration with the hope it would work.
I tried by many ways to modify it (using ADB, root browser, root explorer, solid explorer) and I couldn't change the content. Even worse, when I tried to change the permissions to the file to RW using root explorer, the file turned empty (0b) and it's still impossible to modify it (I tried editing it, deleting, replacing it, nothing works).
Question 1: The simplest of ways would be to be able to change the APN. Does anybody knows a trick (using root or not) to do that on stock OOS 9.0.17. Anybody ever tried changing apns-conf.xml?
Question 2: Did anybody succefylly edit system files onstock OOS 9.0.17 using root?
Question 2-A: Does anybody know why I break the file when I change the permission? I'd like to understand what's going on.
Another option that I am considering is using a custom ROM that disables this nonsense APN lock mechanism.
Question 3: Does anybody have a good ROM suggestion that is positively disabling this APN lock and that would allow me to change my APN with FIDO? (I was considering Lineage but I couldn't get a firm answer on the APN unlock capability).
I searched the web for many hours without success, I hope you can help me with this.
Thank you all for your insight.
Click to expand...
Click to collapse
Have you tried creating a new apn with the info and settings you need?

jestyr8 said:
Have you tried creating a new apn with the info and settings you need?
Click to expand...
Click to collapse
Yes! I tried that many times.
So, what happens is when you have an "APN locked SIM" inserted in the device, you have no access to any edit option. No editing, no adding, nothing. You are in view mode for the APN settings (which is useless really).
In my research I found that if you insert a "not APN locked SIM" you get acces to creating a new APN (and of course editing the actual SIM APN settings).
I happen to have a SIM card (my girlfriend's) that is not APN locked on hand. I tried a couple of times creating a new APN with the FIDO settings but when I inserted back the FIDO SIM my new APN was not in the list of options.
... I should have deepened my research! I failed at that...
What I didn't realize at the time is that when you create a new APN, Android defaults the MCC and MNC parameters with the values associated with the currently inserted SIM!!! I tought it was some kind of black magic settings used by the service provider for it's network to work. But not later than TODAY (I did more research today...) I learned that: MCC = Mobile Country Code and MNC = Mobile Network Code. ****!!!
Sooooo, all I had to do is create a new APN with my girlfriend's SIM inserted and set (along with all the other settings) the MCC and MNC to the values corresponding to FIDO config (which in the past I left as is since I didn't know what they were). Save. Shut down my device. Insert FIDO SIM, reboot, and fuc**ng VOILA!!! The newly created APN is now available and... wait for it... EDITABLE!!! So if I messed-up any setting I can change it and play around with everything like we did when Google was not Evil.
So here I am with my un-activated FIDO SIM and I can confirm that my newly created APN is selectable, but I cannot try a SIP call for now since I've closed my account. Tomorrow I'll get a new subscription & SIM and update this post. But I think this part is solved.
All that being said, Question 1 is partially answered to my greatest pleasure. But I'd still like to hear your experiences about modifying sytem files on OOS with root access.