Web USB Tools

Not Connected

💡 Which Connection?

📱 Connect Serial: Enable ADB, read info, AT commands
🔌 Connect Device: FRP erase, factory reset, file manager (needs ADB ON)

📘 How to Enable ADB

Step-by-Step Guide:

1. Click "Connect Serial" button (green button above)

2. Select your device from the serial port list

3. ⚠️ CRITICAL STEP:

On your phone, dial: *#0*#

Service Menu (hardware test screen) should appear immediately

⚠️ DO NOT CLOSE SERVICE MENU - Keep it open during entire process!

4. Keep Service Menu OPEN on your phone screen

5. Choose one Enable ADB method below and click it

6. Confirm the popup (check Service Menu is still open!)

7. Wait for all commands to complete (15-20 seconds)

Choose Your Method:

📱 Enable ADB [NEW] - Try this first (fastest, 1 command)

📱 Enable ADB [OLD] - For older devices like J330FN (6 commands)

🚀 Enable ADB [A16] - For Android 16+ and FRP locked devices (advanced APK injection)

⚠️ Service Menu Not Opening?

• Service Menu is a hardware diagnostic screen (shows color tests, sensors, etc.)

• If *#0*# does nothing, your device may not support it

• Alternative: Enable ADB manually in Settings → Developer Options → USB Debugging

• Some Samsung models use different codes: *#0*# or *#7353#

💡 After ADB is enabled: Check your device screen for ADB authorization prompt & allow it

Web Serial Operations

🔌

Connect Device (WebUSB) - Use AFTER ADB is enabled

Requirements: ADB enabled + USB Debugging ON + Computer authorization
Use for: FRP erase, factory reset, reboot, ADB terminal, file manager, screen preview

⚠️ Authorization prompt not showing? Click here for help

1. Check ADB is actually enabled:

• Settings → Developer Options → USB Debugging = ON
• You should see "USB debugging connected" notification
• Try: adb devices in PC terminal

2. USB Connection mode:

• Swipe down notification → Tap USB notification
• Select "File Transfer (MTP)" or "PTP" mode
• NOT "Charging only" mode

3. Try these:

• Unplug and replug USB cable
• Developer Options → Revoke USB debugging authorizations → Try again
• Different USB port on computer
• Use Chrome browser (Chrome 61+ or Edge 79+)

💡 What to expect:
After clicking "Connect Device", browser shows USB device picker → Select your phone → Phone shows "Allow USB debugging?" dialog → Check "Always allow" → Tap OK

WebADB Operations

Power & Reboot

⚡ Advanced AT Commands

🔌 Not Connected
Connect Serial device to use AT commands.

⚠️ Test Recovery Alternatives:
Try these if Recovery button doesn't work:

📋 Common Commands:
AT+DEVCONINFO - Device info
AT+SWVER - Software version
AT+CFUN=1,1 - Normal reboot ✅
AT+SUDDLMOD=0,1 - Download mode ✅
AT+REBOOT=1 - Recovery (try first)

💻 ADB Web Terminal

🔌 Not Connected
Connect Device (WebUSB) to use ADB terminal.

shell@device:/ $ Waiting for ADB connection...
                            

⚡ Quick Commands:

📁 ADB File Manager

🔌 Not Connected
Connect Device (WebUSB) to use the file manager.

Waiting for ADB connection...

📺 Screen Preview (ADB)

🔌 Not Connected
Connect Device (WebUSB) to start screen preview.

Idle

No preview yet.

Console

> Welcome to Web USB Tools v1.0

---

⚠️ Notice: Some features are experimental. Use at your own risk.

📥 Samsung USB Driver

For proper communication with Samsung devices, install the official Samsung USB driver.

⬇️ Download Samsung USB Driver

Note: After installation, restart your browser.

About Web USB Tools

Web USB Tools is a browser-based ADB interface that lets you manage Android devices directly from your computer via WebUSB. No drivers needed, no bloatware—just your browser, a USB cable, and your phone with ADB enabled.

What You Can Do

Browse device file system in real-time
Transfer files to and from your device
Take screenshots and screen capture
Execute ADB shell commands
Attempt FRP removal using multiple methods
Remove Google accounts from locked devices
Enable service menus (device-dependent)

Important Limitations

⚠️ Cannot replace professional tools: This tool is experimental and designed for testing, learning, and niche use cases. For production repair shops, dedicated unlock hardware remains the recommended solution. Many functions may fail on newer devices and freshly patched security systems.

Better on older devices: Success rates are significantly higher on devices running Android 10 and earlier, pre-2023 models, and stock ROMs without additional security hardening. Newer flagships, custom ROMs with hardened systems, and recent security patches may not work.

Prerequisites: Your device must have ADB (Android Debug Bridge) enabled before you can connect. This typically requires device-specific bootloader access or engineering modes—knowledge or tools external to this page.

Found a bug or have a feature idea? Request a feature or report an issue

Device Information