The code #4636## has long been one of Android’s most precious diagnostic shortcuts, granting access to hidden engineering menus. However, as Android continues to evolve, many users have found that this code no longer functions on their devices. In this guide, we’ll explore why the code may not work anymore, discuss alternative ways to access its features, and provide solutions for Android devices.
This code is nostalgic for many, me included, as it was a staple in numerous childhood tech explorations and a repeated highlight in Android tips and tricks videos. Let’s delve into the details!
Why ##4636## Doesn’t Work on Samsung and Huawei
On some Android phones, entering ##4636## may not work if it’s input incorrectly. It’s important to type the code exactly as it is, as even a minor mistake—like adding an extra * or #—can cause it to fail.
- For Samsung devices, this certain code doesn’t function. Instead, you can use #0# to access test mode to estimate screen colors, touch functionality, and more.
- For Huawei phones, the equivalent code to access phone information is ##2846579##.
Battery information with This Secret Code
By entering the code, you’ll collect access to a wide range of information about your battery’s status. This includes real-time data such as the current charge level and remaining autonomy, which are easy to find through other methods. However, what makes this specifically useful is the capability to monitor detailed metrics like voltage and temperature. This awareness can help you identify the cause when your battery’s performance starts to decline, making it easier to pinpoint why it no longer lasts as long as it once did.
How I Fixed This Instantly
Although the ##4636## code no longer works directly on many devices, there’s a workaround that allows you to access the same features. For example, the screenshots below show a Samsung device running Android 14, where this menu is successfully accessed using the workaround.
Here we go:
| Cause | Right Fix (✅) | Wrong Fix (❌) | |
| Android Version Restriction | ✅ Use a third-party app like Force LTE Only or Phone Info to access similar diagnostics. | ❌ Trying *#*#4636#*#* repeatedly on unsupported Android versions (12+). | |
| Manufacturer Disabling the Code | ✅ Check if your maker provides alternative codes (e.g., Samsung’s #0# diagnostic menu). | ❌ Assuming all manufacturers use the same USSD codes without checking brand-specific alternatives. | |
| Third-Party Dialer App Interference | ✅ Disable third-party dialer apps in the meantime and retry *#*#4636#*#*. | ❌ Uninstalling essential apps indiscriminately without confirming they interfere with the code. | |
| Carrier Blocking Engineering Menus | ✅ Contact your carrier to verify restrictions and explore developer tools like ADB commands to bypass. | ❌ Flashing unofficial firmware to bypass carrier restrictions without knowing the risks. | |
| Misentered USSD Code | ✅ Enter *#*#4636#*#* manually using the system dialer app; avoid copy-pasting. | ❌ Copy-pasting the code, which might introduce hidden formatting errors (e.g., trailing spaces). | |
| System-Level Security Restrictions (Android 12+) | ✅ Enable Developer Options and use ADB commands to access diagnostic menus. | ❌ Downgrading your Android version to access *#*#4636#*#* without understanding the risks. | |
| Battery Optimization Conflicts | ✅ Disable battery optimization for dialer apps in Settings > Battery > Optimize Apps. | ❌ Ignoring battery optimization settings that might block system functions like USSD codes. | |
| Corrupted Cache in System Apps | ✅ Clear cache for the Phone and Dialer apps in Settings > Apps > Clear Cache. | ❌ Clearing all app data without testing if cache clearing resolves the issue. | |
| Samsung-Specific Restrictions | ✅ Use the Samsung Members app for diagnostics or dial #0#. | ❌ Assuming Samsung supports all generic USSD codes, like *#*#4636#*#*. | |
| Network Signal Issues Affecting Diagnostics | ✅ Use diagnostic apps like Network Signal Guru to evaluate network settings. | ❌ Disregarding poor signal or network issues that may avoid proper code execution. | |
| App Permissions Blocking Access | ✅ Grant phone and SMS permissions to the default dialer app in Settings > Apps > Permissions. | ❌ Using apps with restrictive permissions to execute system-level USSD codes. | |
| Regional Restrictions (Europe/Asia) | ✅ Use a U.S.-based VPN server to access hidden engineering codes if restricted in your region. | ❌ Assuming all regions provide unrestricted access to *#*#4636#*#*. | |
| Advanced Diagnostic Access via ADB | ✅ Use ADB commands to launch the diagnostic menu: adb shell am start -n com.android.settings/.TestingSettings. | ❌ Using ADB commands without proper understanding, which may disrupt system settings. | |
| Hidden Menus Access | ✅ Access hidden settings via Developer Options > Testing Settings. | ❌ Attempting unauthorized access to restricted menus through unsafe third-party tools. | |
| Google’s Security Updates Disabling Codes | ✅ Research alternative methods (e.g., hidden settings or apps) and check developer forums for updates. | ❌ Assuming Google will re-enable the code in future updates without looking for workarounds. | |
| Hardware-Specific Diagnostics | ✅ Use manufacturer diagnostic tools for hardware checks (e.g., Samsung Members, Mi Diagnostics). | ❌ Assuming all diagnostic needs can be met through *#*#4636#*#* alone. | |
| Rooting the Device for Access | ✅ Research and understand the risks before rooting to enable hidden codes. | ❌ Rooting your phone hastily without understanding warranty implications or security risks. | |
I have provided a comprehensive table outlining the reasons why ##4636## might not be working, with the correct and incorrect fixes. This includes advanced methods and insights rarely found online.
Why the USSD Code *#*#4636#*#* Stop Working? (All Android)
In my understanding, there are a few prospective culprits when *#*#4636#*#* stops working:
Android Version Restrictions: Starting with Android 12, Google has added security measures to avoid unauthorized access to vulnerable diagnostic menus. As a result, ##4636## is not extensive functional on most devices running newer Android versions. They have disabled *#*#4636#*#* on many devices, likely to prevent exploitation. If you’re using the latest version of Android, this may be the reason it’s not functioning.
Manufacturer Variations: Samsung users might have to use the Samsung Members app to access diagnostic data instead of relying on USSD codes. Though it may be normal on some devices, manufacturers like Samsung often use routine codes or disable *#*#4636#*#*. If you’re using a Samsung device, this may be the reason it’s not working.
App Interference: In a few cases, third-party dialer apps may disrupt *#*#4636#*#*. If you have one installed, I recommend temporarily disabling it to see if that’s the cause of the issue.
User Error: It’s easy but double-check that you entered *#*#4636#*#* correctly. I recommend precisely typing in the code rather than copying and pasting, which can occasionally swap characters.
Alternative Paths to Diagnostics
Even if *#*#4636#*#* doesn’t work, fret not! Here are some substitutions:
- Manufacturer Diagnostic Tools: If ##4636## doesn’t work, see if your phone’s manufacturer offers alternative tools.
- Samsung: Use the Samsung Members app One Plus: Dial *#808# for a similar engineering menu. Google Pixel: Diagnostic features are usually still available but need Developer Options to be enabled.
For example, *#06# displays your IMEI on most devices.
- Hidden Menus: Some devices offer hidden menus accessible through specific key combinations (e.g., Power + Volume Up). Consult your device manual for details.
- Third-Party Apps: Apps like “Network Signal Info” or “Phone Info” offer related diagnostic data without the hidden code annoyance.
How to Access or Enable ##4636## on Android 11 and Earlier
If you’re using a device running Android 11 or earlier, you’re in luck—this handy engineering code is still available! Many users lament the loss of the ##4636## shortcut after advance to newer OS versions, but those on older Android iterations can still harness its power.
Personally, I rely on ##4636## often to access detailed technical information about my mobile network functioning, which is usually hidden in standard settings. It’s an essential tool for troubleshooting connectivity problems.
Using it is straightforward: just open your phone’s dialer as if you’re making a call, gently input the 10-digit code ##4636##, and hit the call button. This activity should launch a special menu that grants in-depth details like device identifiers, connection status, signal strength, nearby cell towers, troubleshooting options, and advanced configuration settings.
If the menu doesn’t open immediately, try entering the code and tapping the call button again. Some devices can be a bit finicky, but with persistence, you’ll unlock a treasure trove of geeky data that any Android enthusiast would appreciate!
Why ##4636## Is Accessible to Some Users and Not Others
Restrictions Imposed by Carriers:
Certain carriers, including AT&T, restrict diagnostic codes across their networks to prevent users from accessing advanced settings that might potentially interfere with connectivity.
Restrictions Imposed by Carriers
Some third-party dialer apps interfere with system-level codes, blocking the proper execution of ##4636##.
Google and Manufacturers Restrict Access to Hidden Menus
For example, Samsung frequently disables engineering codes like ##4636## or substitutes them with custom codes. As a result, Samsung users may find ##4636## blocked, whereas LG and Pixel users typically retain access.
Diagnostic Shortcuts Removed in Recent Android Updates
As you mentioned earlier, Google has strengthened the built-in security measures in newer Android versions.
Specifically, they tightly restrict internal debugging access to prevent sensitive device information from being exposed to hackers. As a result, features like ##4636## are often removed.
After updating the latest OS version, the users lose access to previous testing features, while ##4636## continues to function on older Android devices.
Installed Apps May Block Engineering Codes
Some carriers adopt Google’s security approach by disabling developer options across their entire network.
Carriers Now Block Developer Options Across Their Networks
For instance, AT&T restricts access to engineering screen codes on all devices within their network infrastructure. Some apps may acquire permissions to interrupt dialer inputs and calls.
Conclusion
In this article, I have provided you the solution of why *#*#4636#*#* stopped working. If you are using a new Android device or an older one, these steps will help you to solve connectivity issues, explore advanced settings, and maximize your phone’s performance.
If you are upset about the code not working, I will advise you to try a devoted network diagnostics app from the Play Store. These apps offer technical data similar to the information found in hidden code. I hope you found this article helpful.
