How to replace the /adb_keys in device after obtain shell sudo access? #13
Labels
No Label
Customized PKG
Dup
Enhancement
Help Needed
Invalid
Official PKG
Question
Script Bug
Taobao PKG
Wont Fix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: happyz/dpt-tools#13
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Great works bro! Thanks for creating such a convenient tool!
It works like a charm when I use to unlock my DPT-RP1.
But I am confused about after obtain shell sudo access, how can I replace the adb_keys file in device to my own public key for security reasons?
I am not familiar with Android system, when I use
suand replace the adb_keys file, it works and accept my public key. But every time I reboot the device it will recover to its original version.Is there any other solution to do that except repack and flash the boot image? Thanks in advance!
Good catch. I should put the master public key in
/data/misc/adb/adb_keysand set it permission 0766. When I get a chance, I will change theboot.imgand write the keys there instead.But for now, you are right. For better security, you will have to repack and flash the boot image without
/adb_keys(after you put yours to/data/misc/adb/adb_keys).I have removed it. However, I did substitute with an insecure
adbdfor the purpose of another rescuing plan. In short term I plan to keep it as it is.