Tab Mini C boot loop. Help please.

[Anghirrim]

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?

[Renate]

Originally Posted by Anghirrim

What I did:

Well, that should have worked, but who knows if the mods came through correctly.
In any case, you wouldn't have been rooted or permissive.

[Anghirrim]

Originally Posted by Renate

Well, that should have worked, but who knows if the mods came through correctly.
In any case, you wouldn't have been rooted or permissive.

Yeah, I was actually just trying to get adb working from recovery to be able to "adb reboot edl" in case something bad happens (which did ).

For rooted and permissive, I guess you have to modify the prebuilt kernel?

[Renate]

Eh, making progress with my stuff.
I still need to patch SELinux policy.

C:\>adb shell
Poke5P:/ #