yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S9 series] Sizukaze:
Hello, thank you for your production!

Can this support Samsung Galaxy Tab S9 Ultra Wifi (SM-X910)?
[Samsung Galaxy Tab S9 series] ArchVisions:
Well, I am not sure about Docker. KVM as in you can run Linux virtual machines not containers, but I will see on what I can do in the future. It really just depends.
[Samsung Galaxy Tab S9 series] ArchVisions:
Yeah, totally! You just need to provide me your boot.img so I can repack the kernel in it.
[Samsung Galaxy Tab S9 series] Raphael Valyi:
Hello, for Docker, the Kernel options to enable are listed here:

This tutorial shows how to run docker natively on Android, without VMs and chroot.

This tutorial shows how to run docker natively on Android, without VMs and chroot. - docker.md

gist.github.com

I can imagine this is what is needed for kvm too, but if you could confirm or enable them that would be terrific. Having Docker on the device without too much hassle is a game changer for lots of people I think.
[Samsung Galaxy Tab S9 series] ArchVisions:
Ok, this is not bad. I may do it, but as a seperate kernel. Not everyone wants to run Docker on their tablets. Most people just want to root. I personally prefer Incus or LXC or Docker, but it isn't bad.
[Samsung Galaxy Tab S9 series] Sizukaze:
Hello, I extracted the boot.img from the firmware.

from Galaxy Tab S9 Ultra (Wi-Fi) SM-X910 X910XXS2BXD2
[Samsung Galaxy Tab S9 series] Raphael Valyi:
anybody can comfirm KVM really works with the tab s9 ultra and this kernelSU kernel (the post says "kvm enabled") ? I'm about to buy the device and these Docker or KVM things are a deal breaker for my developper usage... I understand that theorically Docker can be enabled by tweaking the Kernel, but I have more doubts with my ability to build a Kernel thay will actually work normally... KVM would save me anyay. But does it really work?
[Samsung Galaxy Tab S9 series] ArchVisions:
Hey sorry it took so long, I was busy. Just download the tar corresponding .tar file from the Github release page and flash it in AP using Odin.
[Samsung Galaxy Tab S9 series] ArchVisions:
Someone else needs to try it. For now, I am only going to be updating this kernel. I just haven't been having so much time building kernels.
[Samsung Galaxy Tab S9 series] andre_ferreira:
Hi, brother, I didn't find the xd2 tar file, could you put the link?
[Samsung Galaxy Tab S9 series] ArchVisions:
xd2?
[Samsung Galaxy Tab S9 series] Sizukaze:
Hello, you don't need to feel sorry. Everything is the result of your hard work.

I won't feel anxious because I am just waiting patiently.

I saw that there is a new file on the GitHub Release page, but is the naming incorrect?

SAMSUNG Galaxy Tab S9 Ultra 5G SM-X916

SAMSUNG Galaxy Tab S9 Ultra Wifi SM-X910

The SM-X910 is the WiFi-only model of the Tab S9 Ultra, not the Tab S9.

View attachment 6105622
[Samsung Galaxy Tab S9 series] Ravindu_Deshan:
nice💚
[Samsung Galaxy Tab S9 series] thiefxhunter:
Thanks for the work! Working o Tab S9 Ultra X910 perfectly
[Samsung Galaxy Tab S9 series] ArchVisions:
You're welcome!
[Samsung Galaxy Tab S9 series] ArchVisions:
Hey, I will fix it tomorrow.
[Samsung Galaxy Tab S9 series] essence25:
Here is the boot.img for the TAB S9+! Thank you!!!

Galaxy Tab S9+ (WiFi) SM-X810 X810XXS3BXE1

Android 14 (current latest)
[Samsung Galaxy Tab S9 series] ArchVisions:
Hey, the boot.img with KSU is now available. Just download it from the second post.

Now just the Tab S9. Hopefully, then I can make the title shorter!
[Samsung Galaxy Tab S9 series] ArchVisions:
Ok fixed it.
[Samsung Galaxy Tab S9 series] essence25:
What do you mean by this "Now just the Tab S9", I need for the S9+
[Samsung Galaxy Tab S9 series] ArchVisions:
Sorry, for confusing you. I meant now someone has to give me the boot.img for the Tab S9 to complete the series. I edited the release page, so just use the link from the second post and download the corresponding .tar. It should say TabS9+ at the end.
[Samsung Galaxy Tab S9 series] essence25:
Got it.. Never mind. Thank you!!!
[Samsung Galaxy Tab S9 series] ArchVisions:
Tell me how everything goes after flashing. :)
[Samsung Galaxy Tab S9 series] essence25:
Will do.

And this should be ok with latest stock firmware "X810XXS3BXE1" v:20240510165111?

Is the kernel version same as in this last fw?
[Samsung Galaxy Tab S9 series] ArchVisions:
No the kernel is based from the OneUI 6.0 update. Just because it has been 6 months to release source code for the Tab S9 series for the latest firmware. I am still waiting for them to release the source code for the OneUI 6.1 update as the only device they have released source code for it is the S24. Short answer, yes the kernel works just fine on 6.1, it is just the version is 5.15.94 instead of 5.15.123.

Sent from SM-A156U using ReLabs
[Samsung Galaxy Tab S9 series] essence25:
If I want to backup the original kernel, in case I need to switch back without flashing whole firmware again, how would I do it?

Also how can we disable "forced encryption" if possible.

This is for my curiosity: If using the KernelSU apk I noticed it shows "install". What happens if we use that to patch the boot.img instead of using this kernel you provided? Would it work on latest kernel 5.15.123?
[Samsung Galaxy Tab S9 series] essence25:
UPDATE: It is working. What I did. I reflashed again with official FW, did not reboot. Flashed "NinjaSU_v0.9.4_TabS9+_SM-X810.tar" in the same Odin session. Now reboot. Got error message below, then I selected "Factory Data Reset", reboot and start initial setup. Installed KernelSU manager APK. Shows not installed but shows NinjaSU kernel. Reboot again, now KernelSU shows "Working GKI" = Success. What next? what to test!

What I learned, we cannot keep data when changing kernels. Is this true? We have to reset data every time we flash boot.img?

Thank you!!!

Ok here is what I did.

Bootloader Unlocked!

1. Flashed current latest firmware X810XXS3BXE1 (which does not allow downgrading that fuse is at 3 now it was at 1 and allowed to downgrade to android 13) No problem we have latest 14 now.

2. Reboot, set up new system, internet and log in google account. (no updates except some google apps)

3. Reboot into download mode.

4. Flashed "NinjaSU_v0.9.4_TabS9+_SM-X810.tar" with Odin3 v3.14.4 under the "AP" , auto reboot.

5. Tablet automatic enter recovery with errors below.

6. I extracted boot.img from original md5 file and compressed it with 7zip .tar and flash again with odin "AP" , reboot = same problem. So not sure what I'm doing wrong.

View attachment 6106725

View attachment 6106726

View attachment 6106727

View attachment 6106729
[Samsung Galaxy Tab S9 series] ArchVisions:
Yes, I mentioned these things in the first post. The error message is supposed to happened when you switch to a custom kernel as Android doesn't know what to do a there are some things like the su binary that get injected into the system after the reset. That is the things the gives you root. I just simply made some minor optimizations to the kernel,

disabled Knox, and added the KernelSU drivers so the kernel actually knows what to do with root.
[Samsung Galaxy Tab S9 series] ArchVisions:
Oh and no you don't have to reset when updating KernelSU, in fact, since you have root on your tablet, you can flash the updates in the future without a PC. When you are updating the firmware though, you have to reset as you go back to stock.
[Samsung Galaxy Tab S9 series] ArchVisions:
@essence25 @TxT-1 @DocSnyder75 @thiefxhunter @Sizukaze I will be making another kernel, but this time without any KernelSU. I will only be disabling Knox and adding some minor optizmations. This is because I would like to create a kernel that can also use KernelSU's LKM mode. This in turn is a win-win. The difference between GKI and LKM mode is LKM injects KernelSU as a loadable-kernel-module meaning it can be easily updated to the latest version. GKI on the other hand integrates KernelSU only at build time. If I create a kernel that is compatible with LKM, I wouldn't have to update it so much - besides every firmware update - and you guys wouldn't have to wait for me to update the kernel. Plus, with LKM, once you have it, you can update KernelSU, directly on the device without a PC. The only time you would even need a PC, is when you update the firmware or update the kernel version (like 5.15.94 to 5.15.123). Let me know what you guys think. It is more work at the start, but so much easier in the future. Although, if most of you just want to stick with GKI I can keep that. I am not sure whether you would have to reset the tablet to flash the LKM kernel.
[Samsung Galaxy Tab S9 series] DocSnyder75:
sounds good! :)
[Samsung Galaxy Tab S9 series] thiefxhunter:
Sounds amazing to me, all the effort will be recompensated i think, cause, in LKM mode, like you said, you will be pushing updates directly to the "module" and the rebuild of the kernel everytime will not be necessary.

I will test as soon as available :)
[Samsung Galaxy Tab S9 series] ArchVisions:
So what is funny, is I built the kernel yesterday, but Samsung just a little bit ago, release source code from the April security patch update, so now I have to rebuild the kernel again, but instead of it being 5.15.95 it will be 5.15.123 which has some bug fixes as well as some fixes with the efficiency of the kernel.
[Samsung Galaxy Tab S9 series] ArchVisions:
You can try it now. Just follow the instructions and download the .tar.
[Samsung Galaxy Tab S9 series] thiefxhunter:
Hi, i just tested with x910 version, and it not worked, followed the upgrade form gki tutorial, but no success, it shows "not installed"

LKM Version:

View attachment 6108401

GKI Version Works well:

View attachment 6108403
[Samsung Galaxy Tab S9 series] essence25:
Wow that is amazing!!!

And lastly, how can I enable ADB root support so we can use the USB adb in root mode etc.

So far using the .94 kernel with no problems. I do have issues installing busybox, for some reason it has issues with permissions from all installers. I did give the installer root. But we can work on this later.

Can I switch to the .123 ninja kernel without losing data partition or need to reset etc.

I'm stuck here (looks like a paradox):

If you have the firmware of your tablet you can instead use the init_boot.img (not lz4 compression) as this is preferred.

Can you clarify above? So I can use either YOUR modified boot.img or my own unmodified init_boot.img extracted from latest firmware with kernel XXX.123 ?

The file init_boot.img is 1.7mb and the file you provided boot.img is 44mb files are different size and type...

Thank you!!!
[Samsung Galaxy Tab S9 series] essence25:
Hmm that happened to me with GKI and had to do 2 reboots and then it worked. I'm sure you probably tried that.

Did you lose the data partition when you switched kernels? Or the device ask to reset all data?
[Samsung Galaxy Tab S9 series] thiefxhunter:
Yeah, tried to restart a couple times, but no success.

About losing data, the device booted wihtout asking to format /data, so i didn`t lose any data in the process.
[Samsung Galaxy Tab S9 series] ArchVisions:
@thiefxhunter sorry about the late response are you on GKI right now?
[Samsung Galaxy Tab S9 series] thiefxhunter:
No problem, im on GKI right now, reverted to last 0.9.4.
[Samsung Galaxy Tab S9 series] ArchVisions:
@thiefxhunter OK so, click the working GKI box, click direct install, let it do its thing, reboot, then reboot to bootloader and flash LKM.
[Samsung Galaxy Tab S9 series] essence25:
OK so you ODIN flash provided Kernel...123 tar, reboot, install KernelSU.apk v0.9.4, copied your init_boot.img 1.7mb to device and patched it with KernelSU and lastly ODIN flashed the kernelsu_patched_xxxx.img?

So did you patch the init_boot.img 1.7mb or the provided boot.img 44mb seems we have two posibilities here, which one of the two did you fash in the last step?
[Samsung Galaxy Tab S9 series] thiefxhunter:
@ArchVisions Wow, now its working, just followed your last steps, with direct install and flash of the created boot.img (tar file)

Thanks for the steps to correct that issue :)

View attachment 6108417
[Samsung Galaxy Tab S9 series] thiefxhunter:
I had just patched the boot.img inside the tar file (like the tutorial said). Just follow the steps and lastly follow the last response of the dev, will work.
[Samsung Galaxy Tab S9 series] ArchVisions:
@essence25 just follow what I told @thiefxhunter. And no data loss.
[Samsung Galaxy Tab S9 series] essence25:
Ok, its working. All I did is this:

1. From Working GKI, direct install.

2. Reboot

3. Reboot again to bootloader

4. Flash the new LKM tar.

5. Reboot and check for Working new kernel version and LKM

Thats it!
[Samsung Galaxy Tab S9 series] ArchVisions:
Awesome. I complicated things myself. Sorry about that. I will go ahead and add these new instructions. :)
[Samsung Galaxy Tab S9 series] essence25:
A new update has been released. I downloaded "KernelSU_v0.9.5_11872-release.apk" and installed it on Tablet. Then used direct install. Reboot and now LKM is at v11872.

Do I need to do anything else?
[Samsung Galaxy Tab S9 series] ArchVisions:
Nope! This is why I made the LKM kernel. It makes it so much easier for everyone to update.
[Samsung Galaxy Tab S9 series] Raphael Valyi:
Hello. Thank you ArchVisions for your work: I could finally get a tab s9 ultra X910 and I could get your GKI 0.94 KernelSU working fine.

However I then tried your latest LKM 5.15.123 Kernel I have an issue: the KernelSU app is creating a kernelsu_patched_xxxx.img file but it seems I have issues when I flash it. In fact my PC is Ubuntu, so I don't have ODIN, only heimdall (in fact this fork that flashed me the GKI image properly https://github.com/amo13/Heimdall ) and I have also tried with the "heimdoo" app on my phone.

I renamed kernelsu_patched_xxxx.img image to boot.img and I tried to flash it with both tools: with these commands successfuly:

heimdall flash --BOOT boot.img

-> it boots and in the KernelSu app, I can see the name of the new Kernel 5.15.123 but there is the read button suggesting to install it (means it is not installed/LKM not running)

then I tried again copying boot.img as init_boot.img on my PC and I did:

heimdall flash --INIT_BOOT init_boot.img

-> it tells it flashed with success, I can boot but the result is the same as previous (not installed)

heimdall flash --BOOT boot.img --INIT_BOOT.img init_boot.img

-> it tells it flashed with success, I can boot but the result is the same as previous (not installed)

So I endeed up flashing the 0.94 GKI again...

Any suggestion how to flash the kernelsu_patched_xxxx.img with heimdall or heimdoo? In the instruction page you tell "put it in the AP slot and flash it". But I have no idea how that would translate to an heimdall command...

Same when you wrote "flash the new LKM tar", could tell an heimdall equivalent command? Thanks.
[Samsung Galaxy Tab S9 series] ArchVisions:
Ok, so normally it doesn't seem like the LKM patch tool doesn't necessarily know what to do with patching with the boot.img. But, the step you did wrong, was renaming boot.img to init_boot.img. These are actually 2 completely separate partitions of the device. I over complicated things. For most people it is just easier if they flash the GKI kernel first, and then switch to LKM. Basically, since you are on GKI now, just follow the instructions on switching. :)
[Samsung Galaxy Tab S9 series] Raphael Valyi:
Ok, so I finally got it working. Well, let me make a few suggestions to the GKI to LKM instructions for people who discover KernelSU or the LKM mode like me, because believe me it's easy to miss the proper install mode in KernelSU or mix the boot images with the one that KernelSU can generate...

From Working GKI, direct install in the KernelSU app.

-> From a working rooted KernelSU GKI, in the KernelSU app choose the "Install directly" installation mode (that will prepare the INIT_BOOT partition for the new "LKM" Kernel you will flash later).

Reboot

Reboot again to bootloader

Flash the new LKM tar.

-> Flash the new "LKM" Kernel tar for the device provided in the link bellow to the BOOT partition.

Reboot and check for Working new kernel version and LKM.

Thank you again. So now I'll fork your Kernel git repo to try bringing Docker support. I spent a couple of hours trying to compile that Kernel (on Ubuntu) without success yet. I assume I will end up succeeding, but If you could give hints to do the compilation on Ubuntu or Debian that would be really appreciated...
[Samsung Galaxy Tab S9 series] ArchVisions:
Awesome! Good luck!

Well about building the kernel, honestly, I don't have much to say other than to be patient as it takes some time to troubleshoot. I can help you along the way though.
[Samsung Galaxy Tab S9 series] ArchVisions:
Just make sure you have the right packages installed and your environment variables are set correctly. I may try building a Docker capable kernel myself in the upcoming days. Not sure though.
[Samsung Galaxy Tab S9 series] essence25:
Is it possible to add the path for busybox that comes with KernelSU so it can be executed from any shell? I believe its in the /data/adb/ksu/bin/busybox location.

Or tell me how to add the path and survive a reboot.

None of the busyboxes from play store install properly in Android 14. (even with root permissions)
[Samsung Galaxy Tab S9 series] flanter21:
Hi I'm back. My S9 is working (for now). I've got the boot.img from the latest OTA (SM-X710_2_20240405114420_7z6nw4wzuw_fac). It's identical to last month's one that I gave before. I'm ready to test KSU if you are, but don't rush! I'm not rushing either.
[Samsung Galaxy Tab S9 series] zahidkhan91631:
Plz some help me for tab s8 plus sm x800 i need costum kernels for higher performance plz help
[Samsung Galaxy Tab S9 series] ArchVisions:
Hey so sorry for not responding. I will work on it tomorrow.
[Samsung Galaxy Tab S9 series] flanter21:
No worries. As I said please take your time. I would do it myself but I don't have 64GB ram or an x86 laptop. I did double check the boot.img though and actually the april and may versions are different. I've attached the April version in my previous post, but here's the May (20240510162800) version which is newer but not the latest. I could also download the new 20240530165200 version though if you'd like.
[Samsung Galaxy Tab S9 series] ArchVisions:
Yeah whatever version you are on is fine.
[Samsung Galaxy Tab S9 series] elesbb:
Hey would you mind helping me out with compiling a kernel? Don't mean to hijack the thread but you have PMs turned off.

I have it mostly working, but get an implicit definition error despite including the necessary header file where it has the function
[Samsung Galaxy Tab S9 series] ArchVisions:
Do you mind sharing the error?

Send a PM if you want now.
[Samsung Galaxy Tab S9 series] elesbb:
Sent the PM. Thanks so much for the assistance!
[Samsung Galaxy Tab S9 series] essence25:
Heya master Arch, a new firmware is available X810XXS4BXG5/X810OXM4BXG5/X810XXS4BXG5(SM-X810_2_20240712114251),

if I were to take that update over OTA, its 340MB or so, would that replace your XX.123-NSU custom kernel that I have installed? (do you know what kernel version is in this July update?) Should I take the update?

Some other scenarios:

1. If I were to have a new device out of the box with this new update installed via ODIN, would KernelSU be able to root it without your custom kernel, is it supported?

2. What about if we have the latest firmware but then flash the older 5.15.123-NinjaSU kernel over that and THEN install KernelSU would that work? (assuming a new kernel is included in upate)

Can you give me some advice on what to do when new firmwares come out. I assume the kernel source will be available in a few months if the kernel has been updated in the July 2024 firmware.

And one more super important question, can userdata forced encryption be disabled via custom kernel compilation, can this be done in kernel image? or we need USERDATA_AIO_SYS_RW_MANUAL_ROOT_FORCE_WIPE_NO_ENCRPTION.tar.

Thank you! Please answer all questions when you have the time.
[Samsung Galaxy Tab S9 series] theclev:
work for tab s9+ 5g? sm-x818U I think it is
[Samsung Galaxy Tab S9 series] TxT-1:
x916b no longer works in latest update flash boot process works but kernelsu indicator does not show that it is working
[OnePlus 6T  Questions & Answers] hunchozy:
Hi everyone I have tried to fastboot my oneplus 6t OS 9.0.8 but still not able ,please provide any instightful information on the same thanks
[Honor 20 Questions & Answers] tigersusyt:
Hello!

I am wondering if anyone knows what command in fastboot you use to unlock the bootloader on newer versions (it was 'fastboot oem unlock xxxxxxxxxxxxxxxx' on Android 9, and whatever the magic ui version was) but it has been changed since , i am just wondering if anyone knows what it's changed to, because i have a brute force code, but it only works on the Android 9 version, not on Android 10 (which i have).

I can't roll back because hisuite is dumb, and doesn't give the option.

Please help!

My software version is in the attached imageView attachment 6101875

I am trying to do this so i can keep using this device when android 10 gets obsolete (also i want to poke around with root)
[Asus ROG Phone 6 / 6 Pro] ngx091:
Hello,

does anyone have ROG6 with already unlocked bootloader? If so, could you share abl, devcfg, sysinfo, xbl images? I have spare device that went through a lot of pain(erased all fingerprints with EDL, restored with .177 backup, which disabled abl flashing) Yet somehow i managed to bring it back to life with engineering rom, so i'm willing to use it for experimental purposes.
[Asus ROG Phone 6 / 6 Pro] AresKING108:
Same question.
[Asus ROG Phone 6 / 6 Pro] ngx091:
Bump. I believe there're some people here, but mostly inactive or online only in case something happens.
[Samsung Galaxy A32 5G] KamDaTechDude:
Wsg everyone so recently since i updated my galaxy a32 5g to the latest firmware ive noticed that sometimes when i try to call someone sometimes the phone says theres no network avalible n itll stay like that , anyways tis is how i tempoarily fix it

first turn off youre a32 5g

next hold the volume up and power button till u see the android recovery screen

next use the volume down button to scroll down to "wipe cache partiton" n click it using the power button

next scroll down n click yes

next wipe the cache partition again

lastly reboot the system

(sorry bout the bad spelling i didnt have much time to write this)
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] ryu-ryuk:
This did not happen to me!

I'm posting this to know what could be done to solve the issue out of curiousity.

So, I came across someone with his poco f5 in bootloop.

Decided to help him, he was stuck in fastboot.

Told him to flash stock using Mi flash

He was getting an error saying "set_active a"

He was using an old version of miflash, using the latest one, solved that issue.

After he successfully flashed the rom via miflash, the phone rebooted on its own but didn't boot and stayed in bootloop.

I advised him to try flashing hyper os eu, he tried the script but still the same result.

I told him to flash ofox, format data, transfer eu zip and flash it. Again THE SAME RESULT!! Bootloop.

And he told me that, "the stock roms just aren't able to boot on his device".

After this, he flashed an android 13 based custom rom and it successfully booted somehow!??

My purpose of this post is to ask for opinions on this. Why is he not able to flash the hyper os or miui based stock roms?? What is going wrong here?

If you have any questions, please let me know. And thanks for your attention on this post :)
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] NOSS8:
Miflash is not configured correctly.

Are you sure this is an Indian version?

MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL

FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED MIUI https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html HYPEROS GLOBAL https://xdaforums.com/t/how-to-unlock-bootloader-on-xiaomi-hyperos.4654009/...

xdaforums.com
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] ryu-ryuk:
Yes sir, I followed the instructions carefully. And it was going to bootloop each time