WhatsApp SMS Verification screen blocking ADB input/injection

[kevin105]

Hi everyone,
I’m encountering a persistent issue while trying to automate the WhatsApp setup process via ADB on Android. Everything works fine until I reach the SMS Verification Code entry screen.
The Problem: As soon as the verification code screen appears, any ADB command related to touch or input fails to register. Specifically:

• Running adb shell input tap X Y or input swipe causes the UI cursor to disappear immediately.
• Once the cursor disappears, the screen becomes completely unresponsive to further ADB commands.
• The only way to regain control or input the code is via a physical touch on the device.

What I’ve already tried (without success):

1. Standard Injection: adb shell input tap and input text.
2. Advanced Injection: adb shell input swipe X1 Y1 X1 Y1 100 to simulate a long press.
3. D-PAD Navigation: Sending KEYCODE_TAB and KEYCODE_ENTER to gain focus.

Has anyone found a way to bypass this "Secure Surface" or force a hardware-level touch event via ADB? I am looking for a way to complete the verification flow remotely.

Thanks for any insights!

 

[kevin105]

I would like to add an important detail to my previous post: I am specifically using ZDE (ZennoDroid Enterprise) for this automation.

The issue where the UI cursor disappears and the screen becomes unresponsive happens within the ZDE instance during the WhatsApp SMS verification step. It appears that WhatsApp's security layer is specifically detecting the ZDE interaction method or the virtual environment at this critical stage.

Has anyone using ZennoDroid encountered this "input freeze" on the verification screen, and is there a specific setting in ZDE (such as a different Input Method or Hardware Simulation mode) that can bypass this hardware-level touch requirement?

Thanks again for the help!

 

[Dmitriy_Zenno]

Hi everyone,
I’m encountering a persistent issue while trying to automate the WhatsApp setup process via ADB on Android. Everything works fine until I reach the SMS Verification Code entry screen.
The Problem: As soon as the verification code screen appears, any ADB command related to touch or input fails to register. Specifically:

• Running adb shell input tap X Y or input swipe causes the UI cursor to disappear immediately.
• Once the cursor disappears, the screen becomes completely unresponsive to further ADB commands.
• The only way to regain control or input the code is via a physical touch on the device.

What I’ve already tried (without success):

1. Standard Injection: adb shell input tap and input text.
2. Advanced Injection: adb shell input swipe X1 Y1 X1 Y1 100 to simulate a long press.
3. D-PAD Navigation: Sending KEYCODE_TAB and KEYCODE_ENTER to gain focus.

Has anyone found a way to bypass this "Secure Surface" or force a hardware-level touch event via ADB? I am looking for a way to complete the verification flow remotely.

Thanks for any insights!

Hello,

I suggest you try performing a click using AppiumDriver:
Documentation:
AppiumDriver API
Element API

You could also try Search by picture