Thread: Go6 unboxing
View Single Post
Old 10-22-2024, 06:26 PM   #16
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 4,068
Karma: 18028039
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
I just found out that some late model Poke5 do have the Carta 1300. Without opening the case you won't be able to tell.

I've had this rooted and most of the things fixed and working before. I've just customized sepolicy, patched /vendor, patched /system, patched the boot image. Now I'm running with SELinux enforcing.
Code:
C:\>adb shell
BOOX:/ # id
uid=0(root) gid=0(root) groups=0(root) context=u:r:su:s0
BOOX:/ # getenforce
Enforcing
BOOX:/ # su
/system/bin/sh: su: inaccessible or not found
Yeah, the whole procedure is a bit complicated and mainly for experimenters. (OTOH, you could learn a lot.) The nice part is with the "Windows Subsystem for Linux" I can manipulate the ext4 partitions right on my Windows desktop. I can also do a sepolicy compilation with secilc directly in Debian Linux and it's compatible with Android.

I've also disabled the ADB authorization popup so no additional computers can be authorized. I've put my computers' public keys into the image so that I can connect with ADB but no one else can. It's really not that cloak-and-dagger, but why not do it?

Last edited by Renate; 10-22-2024 at 06:35 PM.
Renate is offline   Reply With Quote