Database Users

Diagnostic Mode code

I would love to lock this phone into 3G-only mode like I had with my Vibrant. I tried entering the code *#*#197328640#*#* as I did on the OS 2.1 Vibrant, and it didn't work. The *#*#4636#*#* does however show the mode and allow for the change there, but if I remember correctly, it resets to default after reboot.
I'm not surprised, as surely many things have changed since then. Does anyone know what we can enter on the NS?

allen099 said:
I would love to lock this phone into 3G-only mode like I had with my Vibrant. I tried entering the code *#*#197328640#*#* as I did on the OS 2.1 Vibrant, and it didn't work. The *#*#4636#*#* does however show the mode and allow for the change there, but if I remember correctly, it resets to default after reboot.
I'm not surprised, as surely many things have changed since then. Does anyone know what we can enter on the NS?
Click to expand...
Click to collapse
Download anycut from the market and create a shortcut to an activity called "testing". This will open the same menu as *#*#4336#*#* only this one does not reset on reboot.
Took me some time to figure this one out.
Sent from my GT-P1000 using XDA App

can any one tell me how exactly to put google nexus s in diag mode because i need to flash it to boost mobile. thank you

Once you get into diag mode using *#*#4636#*#* just change it to wcdma only and instead of going back go to home directly. that's what i did. it sticks even after reboot.

Joeykrim and nemith have dialer codes working in cdma cyanogen nightly. The code is *#*#8778#*#*
Or *#*#3282#*#*
Uncle Jimmy says hello

U will do the *#*#8778#*#* to connect to qpst. From qpst you can get your MSL. Write that down.
Uncle Jimmy says hello

how to get MSL
Don't need QPST. If rooted, just launch terminal, type getprop and look for the line that says "[ril.MSL]: [xxxxxx]" -- that's your MSL. Could also do it with adb shell getprop from your computer.

kashah said:
Don't need QPST. If rooted, just launch terminal, type getprop and look for the line that says "[ril.MSL]: [xxxxxx]" -- that's your MSL. Could also do it with adb shell getprop from your computer.
Click to expand...
Click to collapse
Sweet. Way easier than configuring qpst
Uncle Jimmy says hello

secret code Zte blade (san francisco)

I'm not responsible for what might happen on your phone if you choose to dial any of these!
These are the codes that work on the standard phone dialler app on the Orange San Francisco, but I'm pretty sure they'll be almost identical on other models that we collectively know as "ZTE Blade". Known small differences (in texts) are down to whether the firmware expects to be running on an OLED or TFT display, and whether you've deleted seemingly unused apps like ChiperTest.apk, fcctest.apk and QcNvTest.apk. Most are prefixed with "*983*", which is "*ZTE*" in phone letters -- I've added a mnemonic for the other part where I think it's obvious (feel free to suggest better ones!).
"Automatic Inspection" runs through the basic tests automatically (usually you need press a button to move on to the next bit -- don't get thrown by any blank colour test screens!). There are a number of interesting items for developers, with hardware info and other goodies. If any of the descriptions don't make the function obvious then it's either poorly written or I don't know exactly what it does (I'll happily update this if others can explain better).
If the code has been recognised by the dialler then it will react immediately when you enter the final "#". If nothing happens when you've done that, don't press Dial!
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dial Mnemonic Operation
*983*0# Menu (20:Battery/OLED/Back Light/Vibrator/Ringer/LED/Key/OLED off/SD/BT address/Radio Info/Memory/TouchPaint Test/Audio Loop/FM/Camera/GPS Test/IMEI/IMSI)
*983*3640*01# IMSI
*983*25# Battery Info[/COLOR]
*983*31# OLED Test
*983*26# Backlight Test
*983*850# Radio Test 0
*983*86# Vibrator & LED Test
*983*84# Ringer Test
*983*07*01# Headset Test
*983*07*02# Key Test
*983*3470# LCD Test
*983*81# SD Test
*983*890# -
*983*26*# Radio Test 1
*#06# IMEI
*983*27274# CRASH Reboot
*#08# Test Flag [Note: requires QcNvTest.apk in /system/app]
*#09***# BT Test
*983*1275# _ASK Dev Info
*983*7# Menu (4:Version/IMEI/IMSI/BT address)
*983*3640# DOH+ Phone Info (inc ping test, radio on/off)
*983*636# MEM Memory Test
*983*28# BT Emode BT Test
*983*477# GPS GPS Test
*983*21# Audio Loop Test
*983*70# Automatic Inspection
*#18# LED Test
*#19# TouchPaint Test
*983*36# FM FM Test
*983*57# Factory Reset
*983*473# Camera
*#23# Video Camera
*983*10# Delete (Touchscreeen) Calibration File
*#25# FM Test
*983*2726# SIM Contacts Op 1
*983*37# SIM Contacts Op 2
*983*6726# SIM Contacts Op 3
*983*154# "test" Menu (12:Self-starting/Software
Version/Hardware Version/PSN/Test Flag/[Completed]/Board Serial/Bluetooth
Address/SMS security/SMS Registration Status/Flash Type/PRL Version/Serial Configuration)
*983*07# Menu (9LED/Ringer/Vibrator/Key Test/Audio Loop/Headset Test/FM/Camera/SD)
*983*5182# Dev Info
*983*7469# SHOW Automatic Inspection
*#26***# Sensor Test
*983*7936# QXDM Save Qxdm in log system
*987*0# Menu (4roduce Information[->"test" Menu]/Automatic Inspection/Factory data reset/Battery information)
*#27***# Compass Test
*983*87274# USBSI USB Switch Test
*983*06# BT Test
*983*564738# LOGSET LOG Set (inc sys_rw)
*983*93# FCC Test [Note: requires fcctest.apk in /system/app]
*983*2377# CFQP Call Forwarding Query with PowerOn
*983*24474636# CHIPINFO Chiper Test (chip info) [Note: requires
ChiperTest.apk in /system/app]
*983*29873283# AXUPDATE Touchscreen Updater
*983*73564# SDLOG SD Log​
Note: the above are for the standard ROM (well, apps) running 2.1. The current Froyo ROM (with standard dialler, etc.) does not have the Touchscreen Updater, but adds:
Dial Operation
*987*123456# DM Test
IN modaco

Hello, what code shude I use to know if my SF is TFT or Amoled?
Regards!

Check the build number in Settings>About Phone. AMOLED ends in 05, LCD ends in 08. IIRC all white SF models are 08 and most grey are 05 (unless its a newer unit which will likely be 08).

Thank´s man.

Mine is 01. What that means?
Looking at the screen characteristics it seems like LCD.

Thanks man. great post

Really nice. Works on Boost Mobile Warp Sync N9515.
Would you happen to have a code that forces prompt for unlock? (Changing sim cards doesn't trigger anything)

same here... up for this....

No Boost Mobile ZTE Warp Sync N9515 Unlock Screen
chinnyss said:
same here... up for this....
Click to expand...
Click to collapse
I think unlocking the Boost Mobile is a lost cause. I've tried several other sims and the only codes I've found to show the unlock menu don't work:
1) Alright then please remove the SIM card and try this code ###825*09#,
2) Got the prompt for code? Please enter the code you received,
3) Failed above, try *983*8284# to access the Unlock Menu,
4) Failed above, finally try *983*865625# to access the Unlock Menu.

zte warp elite n9518 rooted but still i can't use MSL reader or alogcat it says in root checker verify root congrats and after rebooting i got to root again please help just need to get SPC and or MSL code

You the MAN! THA KS.

kelvinpacquette said:
zte warp elite n9518 rooted but still i can't use MSL reader or alogcat it says in root checker verify root congrats and after rebooting i got to root again please help just need to get SPC and or MSL code
Click to expand...
Click to collapse
Can u tell me rhat what do i need to enable usb debigging or adb mode ?? I have to connect my zte z982 device to miracle sodtware, but unable to connect because frp lock.
I cant enable usb debugfing

techeligible3322 said:
Can u tell me rhat what do i need to enable usb debigging or adb mode ?? I have to connect my zte z982 device to miracle sodtware, but unable to connect because frp lock.
I cant enable usb debugfing
Click to expand...
Click to collapse
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dialing the first set of numbers made it possible for me to turn on abd....
Sent from my SM-G550T using Tapatalk

Alright
paigesdavis1996 said:
Edit: on the ROMs based on the Japanese 2.2 you need to put the phone into "Engineering Mode" first, by dialling *ZTE*OPENEM# (*983*673636#) -- this action will be confirmed by a quick pop-up. To close this mode, dial *ZTE*CLOSEEM# (*983*2567336#) -- this then prompts whether you want to do a Factory Reset, which you do not have to do (you can simply Back away from this screen).
Dialing the first set of numbers made it possible for me to turn on abd....
Sent from my SM-G550T using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply

How did you enter / enable adb? I have a 971 and the 2nd code from your site doesn't work, I am able to enable eng. mode
I also tried the connect to computer in control panel and that doesn't do anything either.
Frp locked

Trick

techeligible3322 said:
Thank you for your reply
Click to expand...
Click to collapse
This worked for me and I have the ZTE z blade max thank you

Has this been proven to root the phone yet ? Please leave feedback .

Good News
#Starlord37# said:
This worked for me and I have the ZTE z blade max thank you
Click to expand...
Click to collapse
That's very good to know you are welcome

I haven't had a chance to try it fully yet as I have been trying to root my girlfriends Moto e4 with magisk which I will probably have done by the end of the night and then I plan to tackle my z982 will keep you posted though

set sim pin

hi,
is there any way to set the sim pin by my applikation?
we don't want our customers to know the sim pin, so our applikation will know it (encrypted config file). if the device needs the sim pin, it shouldn't prompt the user for a sim pin. my application should set it for the user.

Maybe the following code would be helpful for you:
Code:
TelephonyManager tm =
(TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE);
Class clazz = Class.forName(tm.getClass().getName());
Method m = clazz.getDeclaredMethod("getITelephony");
m.setAccessible(true);
ITelephony it = (ITelephony) m.invoke(tm);
it.supplyPin("1111");
Please keep in mind that you also need ITelephony.aidl from Android sources.

rwxer said:
Maybe the following code would be helpful for you:
Code:
TelephonyManager tm =
(TelephonyManager)context.getSystemService(Context.TELEPHONY_SERVICE);
Class clazz = Class.forName(tm.getClass().getName());
Method m = clazz.getDeclaredMethod("getITelephony");
m.setAccessible(true);
ITelephony it = (ITelephony) m.invoke(tm);
it.supplyPin("1111");
Please keep in mind that you also need ITelephony.aidl from Android sources.
Click to expand...
Click to collapse
thank you very much.
can you please tell me, where to get the right ITelephony.aidl? i tried searching in my sdk folder, but didn't found anything. google found a couple of different versions. what should i do exactly with the aidl file?

bassmaster said:
thank you very much.
can you please tell me, where to get the right ITelephony.aidl? i tried searching in my sdk folder, but didn't found anything. google found a couple of different versions.
Click to expand...
Click to collapse
I used aidl from source repository http://android.git.kernel.org/ , version 2.2. You can try the one you found.
bassmaster said:
what should i do exactly with the aidl file?
Click to expand...
Click to collapse
Did you try to google?
http://developer.android.com/guide/developing/tools/aidl.html
Place ITelephony.aidl in package com.android.internal.telephony in your source dir. After that java classes should be generated from .aidl files and compiled if you're using standard build script.

I added “ITelephony.aidl” and the code to my app. It all works fine. Thank you.
But now I have the following problem:
My App starts within the device. While booting, the sim pin dialog request appears. This screen is blocking everything - including the start of my app.
How can I avoid that?
The only workaround known to me is to do the following:
I enabled the flight mode before I shut down the device. After reboot my app starts, disables the flight mode and sets the pin.
But I don't know an efficient way that always starts the device in flight mode.
Can you help me please?

You can try to handle android.intent.action.BOOT_COMPLETED intent (see example http://www.androidcompetencycenter.com/2009/06/start-service-at-boot/) and provide sim pin code just after boot. Don't forget to add permission android.permission.RECEIVE_BOOT_COMPLETED

Enable Quick Capture in India (by disabling Emergency Affordance Service)

Hi Guys
So, as you all know, Quick capture is disabled in devices connected to an Indian network and this had me pissed off for a very long time.
I looked into the Emergency Affordance Service which is responsible for identifying Indian SIMs and found a way to disable it (at least on the 5t).
But a word first.
DISCLAIMER: The Govt of India has stated that it is mandatory for all phone manufacturers to add this functionality for the right reasons. By disabling the feature you will NOT be able to use the triple-press power button for emergency call. I do not take responsibility for any damage caused due to the actions described in this post.
Alright, lets jump into it.
Step 1. Install a terminal emulator app (or connect via adb shell)
Step 2. Enter the following command without quotes:
"settings put global emergency_affordance_needed 0"
(You may use the "settings get global emergency_affordance_needed" command to confirm if it worked.)
Step 3. Check the OnePlus Camera app - the Quick capture option should be there.
Step 4. Profit!?
Notes:
My 5t was rooted with magisk, but I ran the command on a normal ($) prompt so I'm not sure if this requires root or not. Please try it on unrooted devices and let me know so I can update this post accordingly. Also, I haven't checked if it persists after a reboot.

Not working on non rooted device.

It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?

abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.

any idea how the phone detects that its india? Could we spoof that?

Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)

zeeshanonlyme said:
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
Click to expand...
Click to collapse
Use ADB shell instead of doing in on your phone

Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Edit: Found It
https://www.reddit.com/r/oneplus/comments/6ur1ma/double_tap_power_button_setting/
The devs name is Mishaal Rahman ...Maybe he could help us out.

abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.

dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.

Sorry for bumping an old thread but has anybody figured out how do get this working permanently with xposed or magisk ? I bought a OP6 and miss this feature coming from a Nokia 7+

MAGISK Module!
Hi,
Was able to create a magisk module to do this automatically every boot and also got wifi auto turn on to work, check out the thread here.

kashyapha1994 said:
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
Click to expand...
Click to collapse
Might be possible to override this with an overlay (non-root Substratum.)

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