My phone is Samsung Galaxy S4 SHV-E330S with a broken screen (cannot see or touch anything)

For more context please see my old questions here and here.

I have already tried these:

Can I enable USB debugging using adb?


Nothing seems to work. I have pushed the adbkey.pub file in .android folder in the PC to /data/misc/adb/adb_keys in the phone while in recovery. On rebooting to android it was still unauthorized. I am pretty sure that before the screen c\broke AI had developer mode and USB debugging enabled on this phone. regardless, I executed the commands shown here

adb shell mount /system
abd shell

echo "persist.service.adb.enable=1" >> default.prop 
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop 
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop  

since I found out that the above lines of text were not in the original default.prop and /system/build.prop (even though I am pretty sure I had enabled USB debugging before the screen broke). Even after adding these lines, the phone is still unauthorized when I reboot to android. Since then I have recovered the original default.prop and /system/build.prop into the phone.

What else can I try now to bypass the RSA authentication dialog box? I have another rooted android phone (different model and OS version) which I have full access to through adb, but it does not even have an adb_keys folder inside /data/misc/adb/adb_keys, so I can't just copy over from that phone to this phone either.

What else can I do to bypass the RSA authentication dialog box on this phone?

1 Answer 1


This was solved using clues from this post

If you only need to authorize one computer:
Simply copy the adbkey.pub
onto the device location:
/data/misc/adb/ and rename it from
adbkey.pub to adb_keys
chmod 0644 and then reboot.

I forgot to do the chmod but still works.

  • 1
    So you passed the RSA Authentication this way, not bypassed. Commented Nov 17, 2019 at 17:47
  • more safe method is 'adb push adbkey.pub /data/local/tmp; adb shell cat /data/local/tmp/adbkey.pub >> /data/misc/adb/adb_keys' that won't erase existing RSA keys or change file permissions
    – alecxs
    Commented Oct 31, 2021 at 9:19
  • The question is how to bypass this prompt for all devices. Just connect without authorization at all.
    – W.M.
    Commented Jun 3, 2023 at 8:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .