Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CiLocks , device not detected #36

Open
abidmaria opened this issue Dec 2, 2022 · 0 comments
Open

CiLocks , device not detected #36

abidmaria opened this issue Dec 2, 2022 · 0 comments

Comments

@abidmaria
Copy link

abidmaria commented Dec 2, 2022

Hello ,

I had an issue that the adb didn't recognize the device , for that i made the below change :

  1. vi /etc/udev/rules.d/51-android.rules

add the below line :

SUBSYSTEMS=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="6860", MODE="0666", GROUP="kali"

  1. create the file ~/.android/adb_usb.ini and place on a single line , the prefix 0x followed by the vendor id:

vi adb_usb.ini

add the below line :

0x04e8

  1. run the below command :
  • adb kill-server
  • adb start-server
  • adb devices

with the above procedure still i cannot see the devices by running ### dba devices , also i cannot use cilocks , since the device was not detected , the only way to make this working is enable usb debugging on my phone as per the below procedure :

Pull down from top two times and click the tooth-wheel icon, or choose "Settings" from the app menu.
Settings -> About the phone -> click multiple times on build number
Settings -> Developer settings -> enable USB Debugging

The question is if i enable usb debugging on phone , it means i know the password , in that case what is the extra value of cilocks ??

Please correct me if i am wrong maybe i missed something

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant