HID Attack Issues [Android-PIN-Bruteforce]

[matr3p]

Hi, firstly I apologize if my topic maybe off but since it's part of using nethunter thought of giving it a shot to see if anyone can help me with my debugging.

I'm using Google Pixel 2 XL with nethunter-2022.1-generic-arm64 installed on said device. I have the package of android-pin-bruteforce in the device as well.

Well, apparently the errors I always get is;
1. usb-devices script failed. Return code 1. (Been trying to make sense of this but still can't)
2. Permission denied for keyboard (Tried chmod a+x, 755, 777 but nothing works as permission not updated)
3. File/directory doesn't exist when it clearly does

Attached some screenshot for reference. Any advice is appreciated.

https://user-images.githubusercontent.com/64389552/176118437-a10ff30c-8573-43a0-92b2-973d2374b72b.png

(https://user-images.githubusercontent.com/64389552/176118437-a10ff30c-8573-43a0-92b2-973d2374b72b.png)https://user-images.githubusercontent.com/64389552/176118994-5f14f9b8-3e86-420d-aebf-61007ee2ead6.png

https://user-images.githubusercontent.com/64389552/176121608-b123d721-ee21-458c-afbd-d35dae25f2f6.png

[Fred Sheehan]

Look at the 'permissions' on your 'file'

it is a symlink only, as shown by the l as the first letter..

If it was a directory it would be a d..

If it was an actual file then no letter would be in first position at all..

you need to create the file first..

touch /system/bin/setprop

[matr3p]

Thanks for the response. I've tried but was unable to as the system is read only file system.

I've tried to remount too but was unable too.

At this point, I'm just lost and adrift... :confused:

[Fred Sheehan]

try with sudo..

sudo touch /system/bin/setprop

[matr3p]

Hey thanks for the suggestions.

However, trust me when i say I've tried all methods including Sudo. Apparently the partition is read only. I have tried to remount the partition but only to met with repetitive failure. I'm not sure if my partition is corrupted or just a permission issue though.

[Fred Sheehan]

do you have a rooted device, does sound like permissions issue but you have to set permissions in bootloader..