Attention Everyone, I have an Announcement~!
It took a dang year but I finally figured out how to get the kernel and the ramdisk files from the boot.img. I had to use ubuntu to get it to work. Here's a visual for anyone interested
EDIT THERE'S A WINDOWS TOOL SEE THE SHARE FROM RENATE BELOW
boot.img tool:
drive.google.com
I specifically used the premade ubuntu machine in the comments of this thread
Hello Friends~! I decided to write out a step by step guide to install WSL - Windows Subsystem for Linux, with an Ubuntu Distro, and integrated GUI using Xserver. As well as how to update WSL to WSL2. Open Powershell as Admin, then paste: wsl...
forum.xda-developers.com
Hopefully if that one stupid step was holding anyone else up from trying to make a Real Rom, this will help them get by.
I posted the extracted system text files, apks and the kernel and ramdisk from both the stock and dev 8.2.3 firmware on the COMMUNITY EDITION section of this Guide.
Normal Users seeking only Backup Stock Copies should use the Stock Recovery Images Below. AI Upscaling Works. Using the Developer Only Rooted (Full Read Write) Images will break AI upscaling [/SPOILER] [/SPOILER] [/SPOILER]...
forum.xda-developers.com
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
For later: The readme shows how to build Magisk into the rom using android studio
Right now the main goal is get su while keeping AI upscaling.
The idea here is to either get su on the STOCK image (as the su binaries are absent on stock), which would require repacking the system.img with the su binaries from the DEV image but would also require modifying the boot.img.. OR get the dependencies needed from the STOCK image for the AI Upscaler pushed onto the DEV image which would only involve an adb push command, but however long it takes to research the dependencies. Whichever is achieved first.
So as you can see we have a zimage file which is peculiar as the shield is 64 bit arch and according to this link zimages are typically associated with 32 bit
Hello everyone I have been trying to figure out how to make my android kernel a zImage or boot.img. I tried to figure it out with no luck. I was told that zImage isnt possible for my device becaus...
stackoverflow.com
"zimage is a self extracting gzip compressed image, you might be able to decompress it by finding the starting offset of the data in the file"