[DEV] AoL - Android ON Linux - GM-T810 Edition [CLOSED]

[ashyx]

I tried all sorts to get adb working fully, was always able to get offline mode (according to my tester)
It seems kernel related, but I don't see what in the kernel is preventing it. Even with a permissive kernel the result is the same.
It's not the ramdisk as the same ramdisk works on my tab s with the Tab S kernel and can get a root shell no problem.

 

[workdowg]

With LPM I mean charging mode, with the big battery. Usually it would gain me full adb access but it would take about a min until adb started.

I was also able to adb in while charging... no root of course... to even get twrp to see the device I had to disable mtp in the mount menu but still no adb.... Thanks anyhow.

Sent from my SM-T810 using Tapatalk

 

[CTXz]

I was also able to adb in while charging... no root of course... to even get twrp to see the device I had to disable mtp in the mount menu but still no adb.... Thanks anyhow.

Sent from my SM-T810 using Tapatalk

LPM should always be based on the kernel/boot partition. Is you kernel rooted? Does it say kernel not seandroid enforcing in LPM? The best way to force it to root it to disable samsungs root restrictions and selinux.

 

[workdowg]

LPM should always be based on the kernel/boot partition. Is you kernel rooted? Does it say kernel not seandroid enforcing in LPM? The best way to force it to root it to disable samsungs root restrictions and selinux.

It's ashyx's permissive. All mine boot loop

Sent from my SM-T810 using Tapatalk

 

[workdowg]

@ashyx @CTXz or anyone browsing here....

So to sum up what is happening at the moment:

1) Unpack and repack ashyx's kernel and it works flawless
2) Unpack and modify his ramdisk (add files or modify some), repack and it works also
3) Unpack his kernel, swap the init with my script, repack and /mnt/root disappears from the ramdisk and it doesn't boot, no logging either(well placed echo commands to a log file on a busybox mounted mmcblk0p22)
4) Manually repack ramdisk and manually repack kernel (pulled all mkimage parameters from CarlivImageKitchen scripts) and add the old dt.img and nothing

I'm sure the issues now have to do with the dt.img file and the fact the repack is removing the ramdisk directories I made (See this blog post). The documentation for dt.img is light and over my programing head to figure out. There are 2 tools to create the file but not explaination of what to use as input for it (ramdisk compressed???).

This is a Samsung issue because this manner of swapping the init with a script works on 2 other devices I own (Nexus 9, YT2).

Again any input would be great....

 

[moonbutt74]

W,

hi, this is just a thought,

it looks like you need to export the mount point properly,
for my setup i stated the mount point in my fstab and also needed to export the mount point's environment variable in init.environ.rc.
The dt.img from stock/functional custom kernel should be fine, but some of your post is unclear.

Repeat your modification process step by test by step and isolate the issue.

On swapping out init binary for a "dummy" init, if i'm understanding correctly, look up the recovery.img from the galaxy tab/note kali project from a few years back and disassemble that image to see what was done. I am thinking you would need to slay selinux as well via a kernel patch to force disable it.

http://docs.kali.org/kali-on-arm/kali-linux-on-galaxy-note

Edit - try using @osm0sis 's AIK toolkit as well.
m

 

[workdowg]

W,

hi, this is just a thought,

it looks like you need to export the mount point properly,
for my setup i stated the mount point in my fstab and also needed to export the mount point's environment variable in init.environ.rc.
The dt.img from stock/functional custom kernel should be fine, but some of your post is unclear.

Repeat your modification process step by test by step and isolate the issue.

On swapping out init binary for a "dummy" init, if i'm understanding correctly, look up the recovery.img from the galaxy tab/note kali project from a few years back and disassemble that image to see what was done. I am thinking you would need to slay selinux as well via a kernel patch to force disable it.

http://docs.kali.org/kali-on-arm/kali-linux-on-galaxy-note

Edit - try using @osm0sis 's AIK toolkit as well.
m

I used his tool also. Thanks for the pointers...

 

[CTXz]

I used his tool also. Thanks for the pointers...

You said your kernel isn't booting, right? How are you compiling it?

 

[workdowg]

You said your kernel isn't booting, right? How are you compiling it?

Sorry if this is a bit of a retelling, but I want to give the full picture to everyone...

I've been unpacking ashyx kernel (Unpacking and repacking his kernel works fine with all the tools I tried) and using my ramdisk (here it is just uncompressed and zipped, just so you can see the structure). All the tools to repack the kernel remove the /mnt/root directory from /mnt in my ramdisk.

So because it wouldn't boot, I was decided to build the kernel to add framebuffer support at boot to debug and see any messages. I decided to build the straight up permissive one first to ensure my kernel builds were good. But, I couldn't get any of my builds to boot past the second splash (Samsung).

My native Arch Linux environments failed before even starting the building so I was used a fresh (Virtualbox) Ubuntu 14.04 build environment with java 7, linaro 4.8, and the other suggested libraries (build-essential, lzop, libc6:i386, libstdc++6:i386, etc...). I used these sources SM-T810_NA_LL_Opensource.zip (also tried the older - SM-T810_LL_Opensource.zip). A fresh kernel .config with selinux turned to false. Then I used the ramdisk from ashyx kernel. And I followed this guy's post.

Late last night I found this build environment Virtualbox VM and will try that in a while.

 

[workdowg]

Suprise!!!

Apparently AIK was the ticket!!! I also had a bad rootfs (someone somewhere had said to use GPT for the sdcard... GRRR). Arch linux is now in charge and "letting" Android run on my tablet! I have to get the internet working from Linux (systemd issue...) but Android works flawlessly as before. Stay tuned!

This will be an easy no consequence install process (just flash the old kernel back... Don't know why though ).

This is the rough draft for a microsd install (internal coming soon!!!)

1) Root and install TWRP
2) **** Most important****
..a) Goto SuperSU app and do a "cleanup for reinstall from Playstore"
..b) Reboot
..c) DO NOT REINSTALL SuperSU app (or be ready to flash a stock image in ODIN and start all over)
2) Partition an sdcard - Partition1 - Fat32, Partition2 EXT4 and insert into tablet
3) Extract rootfs to partition 2 (ext4) of mircosd
4) Extract aol-sm-t810.7z to root of sdcard of tablet
5) Boot to TWRP (backup if you wish)
6) Install>>image - aol-sm-t810-boot.img
7) Reboot
8) Oh, yeah... profit!!

You will be able to ssh in from localhost or you pc.
Setting up a GUI will come later...

 

[workdowg]

Ok, so I have a working rootfs and a working kernel (thanks to @ashyx (permissive kernel), @moonbutt74 for pointing me to AIK and @osm0sis for making AIK!!!!). I'll be packing up the rootfs as is (simple root and 1 regular user) and anyone who would like to try it shoot me a PM.

I'll run some testing but I'm confident this is a good build. I'll post a rootfs and kernel once at least 2 people PM me and try it... Also eventually my rootfs builder and kernel init's...

My new priority is repartitioning mmcblk0 to add 2 new partitions for Linux to be installed.

 

[workdowg]

OP - Updated

I updated the OP with the instructions (no files yet) for a MicroSD install of AoL - SM-T810 Edition.



BTW... @ionioni double check my work as always...

 

[workdowg]

Success!!!! Again!!!

12/22/2015
- SUCCESS!!!! AGAIN!!!
After much testing and then a total fail (partitions got corrupted), I now have a working internal AoL install on my tablet. I resized /data (mmcblk0p22) and added 2 new partitions (mmcblk0p23 + 24).
After I work out the kinks in the installer I'll post it. The internal installer will also need a fresh rootfs but I will help with that via a menu driven script similar to my AKBI-TF700 project. It will be better to do the two separately, especially if someone just needs to split their /data partition ( @moonbutt74 ).

 

[CTXz]

12/22/2015
- SUCCESS!!!! AGAIN!!!
After much testing and then a total fail (partitions got corrupted), I now have a working internal AoL install on my tablet. I resized /data (mmcblk0p22) and added 2 new partitions (mmcblk0p23 + 24).
After I work out the kinks in the installer I'll post it. The internal installer will also need a fresh rootfs but I will help with that via a menu driven script similar to my AKBI-TF700 project. It will be better to do the two separately, especially if someone just needs to split their /data partition ( @moonbutt74 ).

Glad to hear it turned out well!

 

[workdowg]

1700 views and not 1 PM... I have it working flawlessly on my tablet but no one else that is interested.... Guess this project is done. I'll move on to the Nexus 9....

 

[jan rinze]

1700 views and not 1 PM... I have it working flawlessly on my tablet but no one else that is interested.... Guess this project is done. I'll move on to the Nexus 9....

I tried to PM but it seems that PM doesn't work. Perhaps that's why you did not get any PM?
Would love to try this out. If there is a way to download the rootfs and such then much obliged.

 

[workdowg]

I tried to PM but it seems that PM doesn't work. Perhaps that's why you did not get any PM?
Would love to try this out. If there is a way to download the rootfs and such then much obliged.

PM received and replied!

 

[Glotzie]

Well I can only speek for myself...I was waiting for the files and some kind of presentation video of the performance or something. Maybe i should have made a post for that. Sorry

 

[workdowg]

Well I can only speek for myself...I was waiting for the files and some kind of presentation video of the performance or something. Maybe i should have made a post for that. Sorry

Can't post files until at least 1 more person steps up willing to test... I just had my first PM about this... Other than moonbutt74 wanting to repartition his device (not this tab...), there has been no interest.
I have a script that does the repartitioning only but unfortunately wipes data. That is not bad except it means a clean device. I haven't gone further because of time constraints and lack of outside interest. I'm more that willing to use my device as a guinea pig but only if others will use the results of it.

 

[workdowg]

Some info....