Quote:
Originally Posted by Renate
You know what ADB is, right?
The stock recovery has ADB, but it's also ro.adb.secure=1 so you can't connect.
My custom recovery has accessible, rooted ADB and the SELinux is permissive.
|
Dang!!! That's what I was trying to do (at least get adb working) with my modified recovery that sent me into the bootloop on my Page. I saw that adbd was inside, so decided to try my chance.
What I did:
- Dumped stock recovery via EDL
- Unpacked the recovery.img using Magisk Tools (
https://topjohnwu.github.io/Magisk/tools.html)
- Opened the ramdisk.cpio archive
- Edited the prop.default with the following options:
- ro.secure=0
- ro.adb.secure=0
- ro.debuggable=1
- Saved my changes and repacked the recovery.img
- Booted into bootloader and ran "fastboot boot patched-recovery.img"
Do you mean that just changing the ro.adb.secure line from 1 to 0 would have been sufficient?