Mur Posted August 22, 2021 Share Posted August 22, 2021 Hi, I'm opening this topic because I need some help trying to execute my Rubber Ducky on an Android phone. The target is a LG X Power (LG-K220) running on Android 6.0 (Mashmallow), no root and ADB debugging disabled. It's currently locked with a pattern and an alternative PIN that can be input after 5 incorrect attempts over the pattern lock. The reason I got my ducky in the first place was to bruteforce the PIN, as it has no maximum attempts before it blocks nor cooldown. I load a simple test payload into the ducky to try its behavior on the phone, but it won't load when I try to connect it to it via the USB adapter. I've tried to connect the ducky into a PC just to see if the device was broken but my PC detects it and works fine (green led is shown too). Whenever I plug it into the phone, no led is shown. I've tried a couple different USB adapters but none of them worked. I was afraid it could be some hardware issue, so I connected the phone to my PC but it was recognized as an external device. Also, the charger works fine. I also tried to add a DELAY 10000 into my payload just to see if it was some kind of problem recognizing the device, but it didn't work Please, could you help me with this issue? Thank you in advance. Link to comment Share on other sites More sharing options...
chrizree Posted August 22, 2021 Share Posted August 22, 2021 What adapter are you using? Is it an OTG one? I tried a simple payload script now with a Google Nexus 5 and a Sony Xperia Z3 that is running 6.x and both worked/executed fine. Link to comment Share on other sites More sharing options...
Mur Posted August 23, 2021 Author Share Posted August 23, 2021 Hi chrizree, yes that is correct. I used two different OTG Type B adapters, the standard one provided with the Rubber Ducky and another one I bought the next day just to try. Link to comment Share on other sites More sharing options...
chrizree Posted August 23, 2021 Share Posted August 23, 2021 OK, no idea what's wrong then, I can't reproduce/recreate your failing scenario sadly Link to comment Share on other sites More sharing options...
Mur Posted August 23, 2021 Author Share Posted August 23, 2021 Could it be a problem of the phone? I don't have the knowledge of how the ducky works at a hardware/firmware level. Is there maybe any kind of update for either the phone or the Ducky I could install? Maybe some kind of insufficient voltage amount for the phone to detect the ducky? Any idea is appreciated. Thank you! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.