Repository navigation
Replies: 17 comments 40 replies
|
If your phone's kernel version is 5.10 or higher, you can absolutely use https://github.com/WildKernels/GKI_KernelSU_SUSFS to find a matching GKI kernel for your device and install it, then use Droidspaces hassle-free. No kernel source needed. If your kernel version is 5.4 or below, the chances of getting Droidspaces working are really low if the kernel is fully closed source and there's no kernel source available for a similar model of your device. The stuff Droidspaces needs has to be enabled when the kernel is built, so it can't be added by just patching the boot image. |
|
Hey, thanks. This is my kernel version |
Congrats ! You have a GKI Kernel. So, you can install a kernel from Wild kernels repo right now and start using droidspaces today ! |
|
On 2 October 2026 17:56:55 BST, Ravindu Deshan ***@***.***> wrote:
> Hey, thanks.
>
> This is my kernel version 6.1.145-android14-11-gec45f20f38ea-ab15260282
#1 Mon Apr 20 12:39:01 UTC 2026 You think droidspaces would be implemented
for that?
Congrats ! You have a GKI Kernel. So, you can install a kernel from Wild
kernels repo right now and start using droidspaces today !
The next question is if there is a version for my specific version, thatll
boot, do I have to use the same subversion from what I have now for Google
pixels? I'm on axionOS at the moment.
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
If you go to the latest release page of the Wild Kernels repo, you can see there are few different kernel releases for 6.1.145. If you picked the right kernel that matches your exact KMI and flashed it, it should boot regardless of the OEM :) Since AxionOS doesn't tell you the KMI version, you can try both 
|
|
On 2 October 2026 19:00:38 BST, Ravindu Deshan ***@***.***>
wrote:
> On 2 October 2026 17:56:55 BST, Ravindu Deshan ***@***.***> wrote: >
Hey, thanks. > > This is my kernel version
6.1.145-android14-11-gec45f20f38ea-ab15260282 #1 Mon Apr 20 12:39:01 UTC
2026 You think droidspaces would be implemented for that? Congrats ! You
have a GKI Kernel. So, you can install a kernel from Wild kernels repo
right now and start using droidspaces today !
> The next question is if there is a version for my specific version,
thatll boot, do I have to use the same subversion from what I have now for
Google pixels? I'm on axionOS at the moment.
> […](#)
> --- Thanks! "I'm not a very positive person" - Linus torvalds
If you go to the latest release page of the Wild Kernels repo, you can see
there are few different kernel releases for 6.1.145.
If you picked the right kernel that matches your exact KMI and flashed it,
it should boot regardless of the OEM :)
Since AxionOS doesn't tell you the KMI version, you can try both
`android14-2025-08` and `android14-2025-09` and see what kernel boots.
Make sure to have a proper boot image backup in case if something went
wrong 🙏
I have root, any commands to use in case I fuck up? 😓🙏
…
<img width="1080" height="2208" alt="Screenshot_20261002_232455_Brave"
src="https://github.com/user-attachments/assets/759cd802-9c29-4bdf-9f1f-fc1c2d28be07"
/>
--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
This is the only command you need to backup your existing boot.img to the internal storage:
If your device has boot_a or boot_b like layout, so you can backup boot_a like this:
Make sure to store boot-backup.img in somewhere safe like your PC, if your custom recovery cannot mount the encrypted internal storage. Then, flash the Wild Kernels ZIPs, see what kernel boots, if nothing booted, restore the boot-backup.img we've backed up to your boot partition from a custom recovery like TWRP. |
|
Hmm, isn't Pixel kernel open source? |
|
What would be your bet? 😅 I would HATE if I bootloop without a recovery method, does it particularly matter? |
yeah but I think axion built it closed? Cuz I don't see 145 on googlesource :( |
Without a PC, I don't recommend you to do this experiment 😶 Once you have access to a PC, you can definitely it out. Just a tip: if you really want to know the KMI version, check what KMI version does the latest stock Pixel 7 uses. You can unpack the boot.img using magiskboot, then run |
Bootloop is normal. What I don't know is whether you can access the recovery mode without plugging into a PC or not. In Samsung, you can't. But, a PC isn't mandatory. You can even plug the phone to anything that has USB data lines like a TV, then access the recovery mode using the key combination..😅 |
|
On 2 October 2026 19:20:57 BST, Ravindu Deshan ***@***.***> wrote:
> Hmm.. I have no PC or other device at the moment, I have orangefox
(sigh) but I'd want to be sure what one to flash
>
> My device is the pixel 7, AxionOS 2.7
Without a PC, I don't recommend you to do this experiment 😶
I think I could decrypt my ofox data.
Once you have access to a PC, you can definitely it out.
Just a tip: if you really want to know the KMI version, check what KMI
version does the latest stock Pixel 7 uses.
%s version %s ***@***.***) (Android (10087095, +pgo, +bolt,
+lto, -mlgo, based on r487747c) clang version 17.0.2
(https://android.googlesource.com/toolchain/llvm-project
d9f89f4d16663d5012e5c09495f3b30ece3d2362), LLD 17.0.2) %s
Linux version 6.1.157-android14-11-gbd23337e42e7-ab14791245
***@***.***) (Android (10087095, +pgo, +bolt, +lto, -mlgo, based
on r487747c) clang version 17.0.2
(https://android.googlesource.com/toolchain/llvm-project
d9f89f4d16663d5012e5c09495f3b30ece3d2362), LLD 17.0.2) #1 SMP PREEMPT Wed
Jan 28 05:34:14 UTC 2026
Linux version 6.1.157-android14-11-gbd23337e42e7-ab14791245
***@***.***) (Android (10087095, +pgo, +bolt, +lto, -mlgo, based
on r487747c) clang version 17.0.2
(https://android.googlesource.com/toolchain/llvm-project
d9f89f4d16663d5012e5c09495f3b30ece3d2362), LLD 17.0.2) #1 SMP PREEMPT Wed
Jan 28 05:34:14 UTC 2026
enabled_cfi_clang
…You can unpack the boot.img using magiskboot, then run `strings kernel |
grep -I clang` ; it will show the kernel version, which reveals the KMI
(the android14-2025-XX thing)
--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
I wouldn't think that is correct. fsck will not be happy.. I wanna know my 145 KMI? |
|
fsck can work as long as KMI is SAME |
I'm not no Mr pixel genius here but I'd reckon that the subversion would have to be the same, no |
|
The subversion doesn't have to be always the "same" But if you really wanna go for same subversion, go for 6.1.145 since that's what you have in stock AxionOS |
|
And this is android lol, some clean upstream logic doesn't apply here |
|
@fatalcoder524 Can you tell what kernel does he need to pick? What is that 2025-XX part? |
|
Security patch version! |
|
On 2 October 2026 19:48:32 BST, Subham Nayak ***@***.***> wrote:
And this is android lol, some clean upstream logic doesn't apply here
I think I know that.. I've not been living under a rock, I do android
sometimes.
also wdym by "clean upstream logic", I do contribute to Linux, but I'd
imagine how did u find out lolll ✌️
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
What i mean by "clean upstream logic" is that in mainline linux, there is no KMI whitelist unlike in android kernel world. And even if subversion does shift in Android GKI kernel, it will NOT cause a catastroplic failure as long as it doesn't have any KMI upgrade and also as long as it doesn't break any module layouts |
|
And speaking of how i found out your KMI? Yours is 6.1.145-android14-11. Where the "-11" you see is your KMI version |
|
And in Android world, google freezes their module KMI (if everything is stable), which we say KMI enforcement. |
Negative, how did u find out I contributed to Linux lol |
|
I didn't found out lol. Someone provided me one of your contribution link in lore.kernel.org: https://lore.kernel.org/all/?q=Bradley+Morgan This is where i came to knew lol |
|
On 2 October 2026 20:01:55 BST, Subham Nayak ***@***.***> wrote:
I didn't found out lol. Someone provided me one of your contribution link
in lore.kernel.org:
https://lore.kernel.org/all/?q=Bradley+Morgan
This is where i came to knew lol
HAH, who did? Do yk?
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
Ahh a guy in droidspaces group gave the link and that's where i knew |
|
On 3 October 2026 04:42:28 BST, fatalcoder524 ***@***.***> wrote:
Security patch version!
Vendor SP level:
5 December 2025
ASP level:
1 April 2026
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
Then, the answer is obvious 😄 Try this variant: 6.1.157-android14-2025-12-KernelSU-Next-AnyKernel3.zip |
|
On 3 October 2026 11:48:26 BST, Ravindu Deshan ***@***.***>
wrote:
> On 3 October 2026 04:42:28 BST, fatalcoder524 ***@***.***> wrote:
Security patch version!
> Vendor SP level: 5 December 2025 ASP level: 1 April 2026
> […](#)
> --- Thanks! "I'm not a very positive person" - Linus torvalds
Then, the answer is obvious 😄
Try this variant:
[6.1.157-android14-2025-12-KernelSU-Next-AnyKernel3.zip](https://github.com/WildKernels/GKI_KernelSU_SUSFS/releases/download/r21/6.1.157-android14-2025-12-KernelSU-Next-AnyKernel3.zip)
Does this include droidspaces? And root? The basics really...
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
Yes it is It has Droidspaces support and KernelSU-Next |
|
On 3 October 2026 11:52:59 BST, Ravindu Deshan ***@***.***>
wrote:
> On 3 October 2026 11:48:26 BST, Ravindu Deshan ***@***.***> wrote:
> > On 3 October 2026 04:42:28 BST, fatalcoder524 ***@***.***> wrote:
Security patch version! > Vendor SP level: 5 December 2025 ASP level: 1
April 2026 > […](#) > --- Thanks! "I'm not a very positive person" - Linus
torvalds Then, the answer is obvious 😄 Try this variant:
[6.1.157-android14-2025-12-KernelSU-Next-AnyKernel3.zip](https://github.com/WildKernels/GKI_KernelSU_SUSFS/releases/download/r21/6.1.157-android14-2025-12-KernelSU-Next-AnyKernel3.zip)
> Does this include droidspaces? And root? The basics really...
> […](#)
> --- Thanks! "I'm not a very positive person" - Linus torvalds
Yes it is
It has Droidspaces support and KernelSU-Next
The entire suite of support? Like everything?
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
Yes |
|
On 3 October 2026 11:55:26 BST, Ravindu Deshan ***@***.***> wrote:
Yes
Including virtual ap and openwrt? Absaloyely everything?!
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
Yes yes yes 🧤 |
|
On 3 October 2026 11:57:28 BST, Ravindu Deshan ***@***.***> wrote:
Yes yes yes 🧤
Wait, 145 > 157 ?
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
As i said, it should boot since KMI is same |
|
On 3 October 2026 12:00:34 BST, Subham Nayak ***@***.***> wrote:
As i said, it should boot since KMI is same
Hmm, you sure? I heard you need the same subversion too, no?
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
Subversion does matter, but in GKI world, it's not a big deal |
|
bro, I booted 5.15.178 on a device that had 5.15.148 in the stock ROM. Basically, I booted Android 16's kernel on Android 14 and it worked. SUBLEVEL doesn't matter as long as the KMI remains the same |
|
Exactly what i said man, it should boot as long as KMI is same |
|
On 3 October 2026 12:03:56 BST, Subham Nayak ***@***.***> wrote:
Subversion does matter, but in GKI world, it's not a big deal
Exactly! I don't particularly wanna have fsck getting mad, idk why Dec
patch and .145 patch. It's odd. No?
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
NO |
|
Don't scream bro |
|
Bro... fsck will NOT get mad at you 😭 |
|
On 3 October 2026 12:05:47 BST, Ravindu Deshan ***@***.***> wrote:
bro, I booted 5.15.178 on a device that had 5.15.148 in the stock ROM.
Basically, I booted Android 16's kernel on Android 14 and it worked.
SUBLEVEL doesn't matter as long as the KMI remains the same
Hmm, ok then! I'll trust u :)
…--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
On 3 October 2026 12:10:28 BST, Subham Nayak ***@***.***> wrote:
Bro... fsck will NOT get mad at you 😭
It booted dw guys, droidspaces fully works
--- Thanks!
"I'm not a very positive person" - Linus torvalds
|
|
Told ya' |
|
So, now you can mark this as the answer and close the case 🙏 |
Uh oh!
There was an error while loading. Please reload this page.
Hey, what if you don't have a kernel source. How could you add droidspaces support through the boot image, and/or the GKI image?
All reactions