##4636## is one of Android’s most useful diagnostic codes, offering access to hidden engineering menus. However, as Android evolves, this code has stopped working for many users. In this guide, I’ll explain why it doesn’t work anymore, share alternative ways to access its features, and provide fixes for Android devices.
There are a lot of memories attached to this code from my childhood. Of course, it has things that can help you; it’s included in most tips and tricks YouTube videos. Anyways, let’s dive in.
How I Fixed This Instantly
While the ##4636## code no longer works directly on many devices, there’s a workaround that can help you access the same features.! See, this is the Samsung device in the screenshots below, running on Android 14, yet I’m able to open this menu.
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 manufacturer 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 temporarily 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 analyze network settings.
❌ Ignoring poor signal or network issues that may prevent 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.
Here’s an ultimate table summarizing the causes of *#*#4636#*#* not working, along with the right and wrong fixes. This includes advanced methods and insights not commonly found online.
Beyond Common Sense Fixes and Unique Insights
ADB Commands for Diagnostics:
Advanced users can use ADB commands to directly open hidden diagnostic menus, bypassing blocked USSD codes.
Battery Optimization Conflicts:
Some Android systems may block USSD codes when battery-saving features restrict dialer apps.
Regional Restrictions:
USSD codes like *#*#4636#*#* might not work in certain countries due to regulatory or carrier-specific restrictions.
Network Diagnostics via Apps:
Apps like Network Signal Guru and Force LTE Only offer a richer diagnostic experience compared to outdated USSD codes.
Rooting Risks:
While rooting can unlock hidden menus, it often voids warranties and exposes devices to security threats.
For devices running Android 12 or later (including Samsung, Realme, and others), Google has restricted the use of ##4636## for security reasons. However, you can use third-party apps to access similar diagnostic data.
To try this workaround, download an app like Force LTE Only or Phone Info from the Google Play Store. These apps replicate the diagnostic menu, giving you access to network settings, device details, and more
However, there’s a trick or a quick shortcut to access that menu instantly.
To do this, download the app called “Force LTE Only” and open it. There are three ways to access this menu: Method 1 is for Android 11 or below, Method 2 is for Android 11 and higher, and Method 3 is for legacy users. Select your preferred option, and it will load or open the USSD menu.
Why the USSD Code *#*#4636#*#* Stop Working? (All Android)
In my experience, there are a few potential culprits when *#*#4636#*#* stops working:
Android Version Restrictions: Starting with Android 12, Google has increased security measures to prevent unauthorized access to sensitive diagnostic menus. As a result, ##4636## is no longer functional on most devices running newer Android versions.. They have disabled *#*#4636#*#* on many devices, likely to prevent misuse. If you’re on the latest Android, this may be why it’s not working.
Manufacturer Variations: For example, Samsung users may need to use the Samsung Members app to access diagnostic data instead of relying on USSD codes. While it may be standard on some devices, manufacturers like Samsung often use custom codes or disable *#*#4636#*#*. If you have a Samsung, this could be why you can’t use it.
App Interference: In some cases, third-party dialer apps can interfere with *#*#4636#*#*. If you have one installed, I suggest temporarily disabling it to test if that’s the culprit.
User Error: It’s easy, but double-check that you entered *#*#4636#*#* correctly. I recommend carefully typing in the code rather than copying and pasting, which can sometimes swap characters.
Alternative Paths to Diagnostics
Even if *#*#4636#*#* doesn’t work, fret not! Here are some alternatives:
Manufacturer Diagnostic Tools: If ##4636## doesn’t work, check if your phone’s manufacturer provides alternative tools.
Samsung: Use the Samsung Members app.OnePlus: Dial *#808# for a similar engineering menu.Google Pixel: Diagnostic features are often retained but require Developer Options to be enabled.”
For example:. 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 similar diagnostic data without the hidden code hassle.
Additional Alternatives
ADB Commands: If you’re comfortable with advanced methods, use ADB to launch the hidden Testing Settings menu:bashCopy codeadb shell am start -n com.android.settings/.TestingSettings
Third-Party Apps: Download apps like Network Signal Guru or Phone Info to access diagnostic data.
How To Use Or Activate *#*#4636*#*# On Android 11 Or Below
If you have an Android 11 or earlier device like I do, you luckily still have the ability to utilize this handy engineering code. I know many users miss the convenience of *#*#4636#*#* after upgrading OS versions and lamenting its absence. But for those of us still on older Android iterations, the power remains in our hands! Personally, I use *#*#4636#*#* regularly to view detailed technical specifics about my mobile network performance that are normally hidden from view in settings. I find it helpful for diagnosing connectivity issues. Activating it is simple enough for us. All I need to do is open my phone dialer as if making a call, carefully enter in those 10 digits *#*#4636#*#*, and tap the call button. Depending on your device, this will then launch a special menu detailing device identifiers, connection status, signal strengths, nearby cell towers, troubleshooting tests, and advanced configuration options. If for some reason it doesn’t automatically launch the hidden engineer menu, try inputting the code and tapping call a second time. I’ve found it can take a couple tries to get working properly on some finicky models. But once connected, I have full access to all that lovely geeky data us Android enthusiasts crave!
I suggest taking full advantage of the engineering goodness while you still can if on Android 11 or lower. Rumor has it that even these versions will restrict things further in the coming years. But for now, input *#*#4636#*#* and tap away without worry – you deserve it!
Why Does *#*#4636#*#* Work for Some People but Not for Others?
Carrier Limitations:
“Some carriers, like AT&T, block diagnostic codes network-wide to prevent users from accessing advanced settings that could disrupt connectivity.”
R1: Google and Phone Manufacturers Limit Hidden Menu Access
For instance, Samsung often disables engineering codes like #*#*4636#*#* or replaces them with custom ones. So Samsung users may find *#*#4636#*#* blocked while LG and Pixel owners retain access.
Manufacturers control hidden menu availability. This leads to functional inconsistencies between various phone brands.
As you indicated originally, Google heightens built-in security protections within newer Android releases.
In particular, they carefully limit internal debugging access that could leak sensitive device details if compromised by hackers. Features like *#*#4636#*#* fall victim to removal.
Users who have updated to the latest OS versions lose previous testing abilities, though *#*#4636#*#* persists on older Androids.
R3: Installed Apps Can Block Engineering Codes
Some carriers emulate Google’s security mindset by disabling developer options network-wide.
Carriers Now Disable Developer Options Network-Wide
For example, AT&T blocks engineering screen codes across all devices on their infrastructure.
Specific applications can obtain permissions to intercept dialer inputs and calls.
If installed, they may actively clash with or disable dial codes like *#*#4636#*#* from functioning correctly.
Removing such apps often resolves problems entering engineering screens.
Not all solutions apply to all devices. Research specific methods for your phone model and Android version.
Modifying hidden settings carries risks. Proceed with caution and only if you understand the potential consequences.
I hope this comprehensive guide empowers you to navigate the world of hidden codes and diagnostic information on your Android device. If you have any further questions, feel free to ask!
Quick Summary:
The hidden code *#*#4636#*#* used to access diagnostic information on Android may not work for several reasons.
Newer Android versions (12+) often disable it for security reasons.
Different device manufacturers have variations or may use entirely different codes.
Third-party dialer apps can interfere, and user error (typos, incorrect dialing) is also possible.
Alternatives include manufacturer-specific codes, hidden menus, or third-party apps like “Network Signal Info”.
Modifying hidden settings carries risks, so proceed with caution and research specific solutions for your device.
In this guide, we’ve explored why *#*#4636#*#* stopped working and shared practical solutions to regain access to diagnostic tools. Whether you’re using a newer Android device or an older version, these tips will help you troubleshoot connectivity issues, access advanced settings, and make the most of your phone. Still facing issues with *#*#4636#*#*? Let us know in the comments below! Found this guide helpful? Share it with fellow Android enthusiasts and subscribe for more troubleshooting tips., and we will update the blog post accordingly.
However, if you are worried about this code not working, listen to this: Don’t despair if *#*#4636#*#* stops working for you. While unfortunately, Google prioritizes increased mobile security over access to engineering test menus, there are alternatives. My top recommendation is to try a dedicated network diagnostics app from the Play Store. These apps provide detailed technical data much like the hidden code used. Your provider’s customer support also offers troubleshooting if connection issues arise. However, whenever you face any tech-related issues, feel free to contact us.
Kunal Kashyap, the tech guru behind FixItKunal.com, simplifies complex tech issues with clear and user-friendly guides. With expertise in Android, iOS, and more, his tutorials empower users to tackle tech problems confidently. Kunal's engaging style makes technology accessible to both beginners and experts. Beyond tech, he explores psychology and keeps up with tech and business trends awarded by the Government and Namita Thapar.
