Database Info

Service Mode Not Supported- AQG5 UK Update Galaxy S8+ G955F

I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code •#0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?

bump

bump, come on people someone must have some info

have you tried *#2263# ??

It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect

esjames said:
have you tried *#2263# ??
Click to expand...
Click to collapse
that is for the snapdragon version, i have the international exynos version and the *#2683662# code used to work but after the update it now says unsupported

bluheart said:
It's disabled on my Indian set also.
Maybe the 6gb set suffers with this aspect
Click to expand...
Click to collapse
possibly yes, im not sure which soc the indian version has whether its snapdragon or exynos but if its exynos then seems samsung have disbaled it after a recent update for whatever reason

After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.

Bryan48765 said:
After months there is still no information for it on the Internet other than that it's not working, so, let's start.
What's in
Code:
logcat -b all -s RILD -s RILD2 -s RILS -s ServiceModeApp_RIL -s XMLParser
?
Which CSCs have it disabled?
Is it accessible with root?
That menu *#2683662# allowed the selection of antennas on a cell tower; channel selection (12 channels in UMTS band 1 as an example); band selection; CA enable/disable; LTE CAT selection; UMTS/LTE Release selection; viewing of 2G/3G neighbours by arfcn/uarfcn; 256QAM/4x4(but no one got it to rank 4, not working? no antenna for the BTS?); reject codes; displayed supported bands and CA Combinations; etc.
Click to expand...
Click to collapse
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
With regards to the CSC's, i can only comment on the XEU CSC which is part of the OXM multi csc and the one my phone is on and on that it says not supported for the code.
I haven't checked on root, don't really want to root my device

hamzahshakeel said:
the logcat command you provided doesn't really give any useful information which can pinpoint any potential solution.
Click to expand...
Click to collapse
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?

Bryan48765 said:
But it could be compared with the logs of a working 2683662. How many of those names appear? Maybe Samsung has changed those names. It's the system wide no-root logcat "adb logcat"?(not sure about the /data/log one) It's while the RIL service mode is starting?
Click to expand...
Click to collapse
i tried the logcat using the filters you provided (i.e. RILS, RILD etc) and yes it does bring back logs relating to those services however its not enough, all it outlines is when i type the code and monitor the logs subsequnt to the typing of the code the log just shows it trying to open the process associated with the menu, it doesnt show what it tries to do in between me sending the code and the response coming back so comparing that with a working code log will bring back nothing of note
however having said that i did try the full system wide log which was a bit teidous given it logs everything so going through it and pinpointing the relevant piece of log was a bit hard, i will attempt to log again using my s8+ and another samsung phone for which the same code works on and then post it here

try install phone info . this programm has all codes inside

Guys, the same in brazil. Since the begining of the year I've tried to activate 256QAM+MIMO 4x4 in my sumsung galaxy s8 using *#2683662# and by now it doen't work as return the message "not supported". Do you guys has reached some progress on it?

Seems they changed something inside the CP (modem.bin) and disabled the code. Flashing back the AQF7 - CP file will get back the code, but don't know the effect.

Yes I also noticed this a couple months back and made my own thread on it. So far there has been no progress except to flash a previous older update

Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.

no_name_no said:
Hi, you can get into advanced service menu with the app called phone info. Look for code 27663368378 and click Launch 0. Tested on rooted android 7, exynos galaxy s7.
Click to expand...
Click to collapse
Ive tried this but not work
Enviado desde mi SM-G935F mediante Tapatalk

hamzahshakeel said:
I recently received the July AQG5 UK update for my Galaxy S8+ G955F (Exynos) and the service mode menu (*#2683662#) now says not supported when in the prior firmware version it worked fine. the service mode menu allows you to lock onto specific LTE bands and enable more advanceed features such as 4x4 MIMO and 256QAM as well as other things, as i mentioned earlier it worked fine in the previous update but now just says not supported.
The service mode code #0011# still works fine, its just the other one mentioned that no longer works, anyone know why or if can get it back without having to flash back to a previous firmware version?
Click to expand...
Click to collapse
Unfortunately starting with Android v8.x.x (Oreo), test codes sent to the RilServiceModeApp via android_secret_code://<code> even by root are being denied.
If the test menu *#2263# or *#2683662# or *#2766338378# doesn't work with your current sim card, then try the following.
Find a couple of other active or inactive sim cards (can be another local carrier or from abroad), let the phone reboot and reconfigure its CSC while on the blue bootup screen, then try the code again, since test codes are CSC specific. It's a hit and miss affair, so be persistent.
If your phone is rooted, you can try these methods one at a time.
After each step, reboot the phone and try the test codes *#2263# or *#2683662# or *#2766338378#.
1. Using Shortcut Master (free version) from the PlayStore, tap on the menu, Secret Code Explorer, scroll down to 2263 or 2683662 or 2766338378 (or Menu > Search for "band"), tap on Launch0.
2. On combination firmware edit the file /efs/carrier/HiddenMenu and /efs/FactoryApp/keystr to be "ON", which will persists even after flashing back to stock firmware.
3. Copy the <CSC>_keystrings.dat from system/etc to root/etc and set permissions to 0744.
4. Try replacing the /system/priv-app/ModemServiceMode/ModemServiceMode.apk=com.sec.android.RilServiceModeApp from a previous Android version which had the codes working, and set the permissions to 0744.
5. Flash an earlier radio (CP) which had the codes working, if the current bootloader allows it to be downgraded.
This last method works on all Samsung models/firmwares without root, but requires a special test cable, which is only available for micro-USB ports at this time.
If you can find a similar cable with a USB-C connector, then it should work just fine. By the way, using an micro to C adapter does not work.
The following is only for phones with a micro-USB port, nonetheless it makes an interesting way to enable the hidden test menus.
You can actually enable most test codes (including RIL test codes which fail to execute on Oreo of newer even while rooted, such as *#2263# band change, *#2683662 lab test mode, and *#2766338378# engineering test menu, etc) on pretty much any model/firmware/region by simply plugging in a test cable into the phone (the other end doesn't have to be plugged in anywhere, it's just the built in resistor which enables test mode/FactoryMode).
It's important to follow the next steps exactly in this order: Open the dialer, exit the dialer with the Back key (not the Home button!), reopen the dialer and now it should accept most test codes.
These cheap test cables can be found on Ebay or AliExpress, just search for "Samsung 523K uart cable" or "Samsung 619K uart cable". Some come as a combo where you can simply switch the resistor values via a switch, but you must try both values, since only one or the other will work on certain models/firmwares/regions.
I've been using this method successfully for many years (currently on my Samsung S7 with the latest 2019 firmware), unfortunately these test cables are only available for micro-USB connectors, so it won't work on the newer USB-C phones even with an adapter (because it doesn't extend the resistor lines, only the data lines). If anyone finds a solution for USB-C, please post a message here.

How to enable Preferred WiFi Calling on Android P Developer Preview?

As was shown here: https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/ you could enable WiFi calling as your preferred calling method with this nice little ADB command. I can confirm with Oreo it worked, and stuck through reboots and all. I have however now sideloaded my Verizon Pixel with the Developer Preview of Android P. It was a smooth upgrade, however I can no longer get WiFi calling to be preferred with the ADB command. It was originally still listed there, and was still containing the "2" value, but the setting no longer worked. I did a factory reset to start fresh, and I notice that the setting is no longer present when doing the “settings list global” command. I tried adding the line and it still does not work. Anyone have a workaround or any ideas on what I can try to get the WiFi calling to be preferred again? I really rely upon it at work, as we have almost no cell signal, and I have come to love the previous ability I had to have it be the Preferred method for all my calls. Since I have one of the jacked Verizon Pixels, I was never able to unlock the Bootloader, so there is no going back for me! I do also want to say on that note though, for the last week, since I did the factory reset and re-did everything, my phone has been rock solid on the "P" Developer Preview!

Stealth111 said:
As was shown here: https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/ you could enable WiFi calling as your preferred calling method with this nice little ADB command. I can confirm with Oreo it worked, and stuck through reboots and all. I have however now sideloaded my Verizon Pixel with the Developer Preview of Android P. It was a smooth upgrade, however I can no longer get WiFi calling to be preferred with the ADB command. It was originally still listed there, and was still containing the "2" value, but the setting no longer worked. I did a factory reset to start fresh, and I notice that the setting is no longer present when doing the “settings list global” command. I tried adding the line and it still does not work. Anyone have a workaround or any ideas on what I can try to get the WiFi calling to be preferred again? I really rely upon it at work, as we have almost no cell signal, and I have come to love the previous ability I had to have it be the Preferred method for all my calls. Since I have one of the jacked Verizon Pixels, I was never able to unlock the Bootloader, so there is no going back for me! I do also want to say on that note though, for the last week, since I did the factory reset and re-did everything, my phone has been rock solid on the "P" Developer Preview!
Click to expand...
Click to collapse
I know there was a flashable magisk module that enabled the options, but it doesn't help with the actual ims status(*#*#4636#*#*, phone settings, ims status). It might be that you need the official Verizon rom that includes the necessary lib files, or that the dev preview doesn't include those and therefore you can't yet enable it?

Xdevillived666 said:
I know there was a flashable magisk module that enabled the options, but it doesn't help with the actual ims status(*#*#4636#*#*, phone settings, ims status). It might be that you need the official Verizon rom that includes the necessary lib files, or that the dev preview doesn't include those and therefore you can't yet enable it?
Click to expand...
Click to collapse
I though about the Verizon thing as well, but I also used the Developer Preview for Oreo, and it worked with it just fine, so I am thinkning they have just moved it somewhere else in the "P", or something of that nature, but I am hoping that someone here can possibly figure it out!

Stealth111 said:
I though about the Verizon thing as well, but I also used the Developer Preview for Oreo, and it worked with it just fine, so I am thinkning they have just moved it somewhere else in the "P", or something of that nature, but I am hoping that someone here can possibly figure it out!
Click to expand...
Click to collapse
I'm having the same problem after a recent update. WiFi calling no longer works, and the option has disappeared from settings.
Dialing *#*#4636#*#* no longer brings up the menu, either.
I tried via adb shell to set wfc_ims_mode=2, but that doesn't work. `settings list global` shows that it is set to 2, but even after reboot wifi calling still doesn't work.

euhn said:
I'm having the same problem after a recent update. WiFi calling no longer works, and the option has disappeared from settings.
Dialing *#*#4636#*#* no longer brings up the menu, either.
I tried via adb shell to set wfc_ims_mode=2, but that doesn't work. `settings list global` shows that it is set to 2, but even after reboot wifi calling still doesn't work.
Click to expand...
Click to collapse
Probably just something that handy yet been implemented, being it is a Dev preview . Same thing with the lockscreen shortcut icons for camera and phone.

Just an update. I stuck a T-Mobile SIM card in my phone and after using the magisk module I mentioned, the options appeared for the advanced and wifi calling. I'll do it again tomorrow and pay a screen . It's almost midnight here so gonna crash

I'm running stock p on verizon. Hoping someone comes up with a solution.

Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first

Xdevillived666 said:
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first
Click to expand...
Click to collapse
Experiencing this issue after upgrading my Pixel XL and my wife's Pixel 2 to the Verizon Pie.
Details for my Pixel XL:
Android Version 9
Android Security Patch Level: August 5th, 2018
Kernel Version: 3.18.10-ga765425
Build Number: PPR1.180610.009
I used to use the ADB hack flawlessly, now I can't seem to make WiFi Calling Preferred over mobile network. So even though I have one bar that goes in and out, it uses the network then drops.

murraj2 said:
Experiencing this issue after upgrading my Pixel XL and my wife's Pixel 2 to the Verizon Pie.
Details for my Pixel XL:
Android Version 9
Android Security Patch Level: August 5th, 2018
Kernel Version: 3.18.10-ga765425
Build Number: PPR1.180610.009
I used to use the ADB hack flawlessly, now I can't seem to make WiFi Calling Preferred over mobile network. So even though I have one bar that goes in and out, it uses the network then drops.
Click to expand...
Click to collapse
I'm gonna pm ya

I haven't even updated to P yet and mine stopped working on the last security patch. I can set it back using adb. Reboot and wifi calling comes on. The first phone call works for about 5 minutes, then drops. The settings database values go back to default. The only way to get it to work again is to go through the whole process again.
Too much trouble. Sure would be nice to just turn it on and have it work.
Sent from my Pixel using Tapatalk

If you've already had WiFi calling working previously with pixel (I can only confirm first gen works with this)
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first and then add the following (see doc).

Doc here
Just copy paste all lines according to instructions from previous post. Check and make sure under phone menu that you are instructions registered

Xdevillived666 said:
If you've already had WiFi calling working previously with pixel (I can only confirm first gen works with this)
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first and then add the following (see doc).
Click to expand...
Click to collapse
I'm new to all this, what do you mean by, "Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first"

XDA won't let me put the text needed in the comments. Dload my PDF and copy paste the text from there to your buildprop

Does Google Pay still work after you edit the build.prop file?
Sent from my Pixel 2 XL using Tapatalk

abuttino said:
Does Google Pay still work after you edit the build.prop file?
Click to expand...
Click to collapse
I didn't not know. Can't use it in France anyways so I'm not worried about it.

Doesn't work in DP5
Hoping that someone else here can verify it in the regular version of pie.
I didn't switch to the RTM because WiFi calling is too important and I did want to test it though.
Sent from my Pixel 2 XL using Tapatalk

Google Fi/Project Fi

Hi All,
It is my request that if you have not tried this or witnessed it first hand, do not reply. I've siphoned through entirely too many threads with those quick to respond no only to have the "no" be proven wrong within the same thread.
That being said: Project Fi
Officially only supported on several devices. The biggest feature lost to those who do not use a supported device is the ability to switch between networks. While I'm still on the fence with rooting my S9 (assuming I'll have to), one thread I found with several confirmations seemed a bit promising to keep the roaming feature.
Editing build.prop to reflect a Pixel 2 allows the device to be activated. While several individuals confirmed this works to activate, none have confirmed whether the roaming feature works as well. Theoretically, it should. Others have lost this feature because the IMEI of the 'surrogate' phone is whats being registered. Makes sense since Sprint (and I believe US Cellular as well) is like Verizon in that they register the device vs the sim (Of course more complex than that, just typing through the logic).
Therefore, if editing the build.prop allows you to activate Google Fi then theoretically the IMEI of said device should also be registered and should work. I'm looking for confirmation on this. There's also a big question about the ability to edit build.prop without rooting and implications on KNOX, Samsung Pay, etc which is why I'm hesitating. Just looking for this first bit of information first.

iAmJG said:
Hi All,
It is my request that if you have not tried this or witnessed it first hand, do not reply. I've siphoned through entirely too many threads with those quick to respond no only to have the "no" be proven wrong within the same thread.
That being said: Project Fi
Officially only supported on several devices. The biggest feature lost to those who do not use a supported device is the ability to switch between networks. While I'm still on the fence with rooting my S9 (assuming I'll have to), one thread I found with several confirmations seemed a bit promising to keep the roaming feature.
Editing build.prop to reflect a Pixel 2 allows the device to be activated. While several individuals confirmed this works to activate, none have confirmed whether the roaming feature works as well. Theoretically, it should. Others have lost this feature because the IMEI of the 'surrogate' phone is whats being registered. Makes sense since Sprint (and I believe US Cellular as well) is like Verizon in that they register the device vs the sim (Of course more complex than that, just typing through the logic).
Therefore, if editing the build.prop allows you to activate Google Fi then theoretically the IMEI of said device should also be registered and should work. I'm looking for confirmation on this. There's also a big question about the ability to edit build.prop without rooting and implications on KNOX, Samsung Pay, etc which is why I'm hesitating. Just looking for this first bit of information first.
Click to expand...
Click to collapse
Are you talking in terms of just activating service? if so, i have a vzw s9+ and i switched to fi, just flashed to xaa and popped in the fi sim. no problems.

iAmJG said:
Hi All,
It is my request that if you have not tried this or witnessed it first hand, do not reply. I've siphoned through entirely too many threads with those quick to respond no only to have the "no" be proven wrong within the same thread.
That being said: Project Fi
Officially only supported on several devices. The biggest feature lost to those who do not use a supported device is the ability to switch between networks. While I'm still on the fence with rooting my S9 (assuming I'll have to), one thread I found with several confirmations seemed a bit promising to keep the roaming feature.
Editing build.prop to reflect a Pixel 2 allows the device to be activated. While several individuals confirmed this works to activate, none have confirmed whether the roaming feature works as well. Theoretically, it should. Others have lost this feature because the IMEI of the 'surrogate' phone is whats being registered. Makes sense since Sprint (and I believe US Cellular as well) is like Verizon in that they register the device vs the sim (Of course more complex than that, just typing through the logic).
Therefore, if editing the build.prop allows you to activate Google Fi then theoretically the IMEI of said device should also be registered and should work. I'm looking for confirmation on this. There's also a big question about the ability to edit build.prop without rooting and implications on KNOX, Samsung Pay, etc which is why I'm hesitating. Just looking for this first bit of information first.
Click to expand...
Click to collapse
I read here on XDA that Google Fi would be able to be activated on other devices and I'm almost positive the S9/9+ were included. You wouldn't need to edit build.prop or anything. You wouldn't get automatic network switching though since that's a hardware / firmware thing from what I remember reading. The service itself would work and you wouldn't need a surrogate phone to make it work initially.
Whether that's live or not yet I don't know. Rooting any Samsung device past the S4 or S5 I believe trips Knox permanently. That's also assuming you don't have a u965 / u960 device, which can't be unlocked / rooted.
Edit: appears to be love for the "majority of Android phones". https://www.google.com/url?sa=t&sou...BBAB&usg=AOvVaw0Yb-mP_-PqDTtcLG7TWkwM&ampcf=1

CalyxOS - Pixel 4a - network issues

Installed CalyxOS on Pixel 4a. Very easy install.
Now have internet access through Wifi only. Can make phone calls (Sprint network) but no internet.
Anyone willing to help or redirect to source of CalyxOS support? Doesn't appear to be much online support.

Doesn't seem to be a lot of traffic on this forum.
In case anyone is interested, conclusion on Reddit forum is that my Sprint sim card may be the problem with CalyxOS. Wish I would have known this before suffering through the install and then return to stock.
All I am really trying to do is find an alternative to stock unrooted phone so I can better manage various things as I have done with all of my previous android phones. First attempt using rooted Android 11 was successful. Unfortunately both Adaway and Titanium BU failed to function. So now back to unlocked unrooted Android 11.

Also have the same phone and issue with trackphon.

@CarlInMO All Sprint users who don't automatically switch to T-Mobile are not currently able to use CalyxOS (or GrapheneOS or similar) until T-Mobile allows open network Pixel phones to use a service called TNX. TNX will allow Sprint phones to use T-Mobile SIMs or eSIMs.
You can read more here:
PSA: Does not work with Sprint ESIM : r/CalyxOS
Just wanted to let everyone know. I tried to activate it via the chat and it wouldn't even download the sim. Switched ba
teddit.net

asuh said:
@CarlInMO All Sprint users who don't automatically switch to T-Mobile are not currently able to use CalyxOS (or GrapheneOS or similar) until T-Mobile allows open network Pixel phones to use a service called TNX. TNX will allow Sprint phones to use T-Mobile SIMs or eSIMs.
You can read more here:
PSA: Does not work with Sprint ESIM : r/CalyxOS
Just wanted to let everyone know. I tried to activate it via the chat and it wouldn't even download the sim. Switched ba
teddit.net
Click to expand...
Click to collapse
I don't know what's going on but I've been having problems just trying to get signal once I put my metropcs card in my pixel 4a

VoLTE/VoWiFi device model spoofing when device not allowed by carrier

Hi,
I've got several devices with VoLTE/VoWiFi capacity (like Xiaomi mi 9T Pro, OnePlus 8T, Xiaomi Mi 9 SE, Google Pixel 3...), but that are not supported by my carrier (Orange France). They only allow it for the devices on this list, according to tests they performed in their lab to ensure there aren't any issues to register them on their network :
https://reseaux.orange.fr/famille/appels-wifi
However, the other carriers in France I tested (SFR and Bouygues Télécom) are allowing these devices to have VoLTE/VoWiFi (I used both sim slots, and I have LTE data access on both. It's always the non-Orange SIM which can make LTE or Wifi calling).
Does someone know how to fake my device model in a carrier perspective ? I tried Device Faker plus and Android faker (on this thread : Android Faker) Xposed modules (on different LineageOS versions with Magisk installed and Riru/LSXposed loaded), but it's quite hasardous to make any random changes, without being sure which one could be effective to change.
Thank you in advance if someone has a solution !

Hi,
I'm sorry to answer so late but i just subscribe to orange, and i have a poco f3, i think this device isn't compatible with this carrier, and i want to know if you find a way to get it work.
Thank you

titou4488 said:
Hi,
I'm sorry to answer so late but i just subscribe to orange, and i have a poco f3, i think this device isn't compatible with this carrier, and i want to know if you find a way to get it work.
Thank you
Click to expand...
Click to collapse
If the carrier doesn't support the device, there is nothing you can do.

No, sorry, I didn't find anything. It seems all you can do is related to play store, and so on. I was able to fake my phone model to be able to install certificates from my company (for emails sync, through exchange), but that's it. It seems it's handled directly by the chipset, and you won't be able to change that within Android.

A year later, I'm on the same boat. Is there anything new around this?