New method to hide the root


very well clean data from google services and you are good to go :)


settings -> apps -> see all -> show system -> google services framework -> clear storage + cache --> still not allowed :(

I then cleared: google play services + playstore, google services framework --> reboot
login back into play store. test integrity= basic + device
wallet --> clean data + cache, open the app --> still "device doesn't meet security requirements"
 
  • Like
Reactions: masterross
settings -> apps -> see all -> show system -> google services framework -> clear storage + cache --> still not allowed :(

I then cleared: google play services + playstore, google services framework --> reboot
login back into play store. test integrity= basic + device
wallet --> clean data + cache, open the app --> still "device doesn't meet security requirements"
of course when you have eu modul installet you not gonna pass so install termux

su
pm uninstall -k --user 0 eu.xiaomi.module.inject


install new Yuri reboot pick action to Yuri
pick Play Integrity Fix Inject modul - Advansed This must be ON Use preview fingerprint, Spoof Build, and hit Fetch pif.json
Go to settings Apps Manage Apps find Services for google play clear data log out form google account log in again Done
 
Last edited:
of course when you have eu modul installet you not gonna pass so install termux

su
pm uninstall -k --user 0 eu.xiaomi.module.inject


install new Yuri reboot pick action to Yuri
pick Play Integrity Fix Inject modul - Advansed This must be ON Use preview fingerprint, Spoof Build, and hit Fetch pif.json
Go to settings Apps Manage Apps find Services for google play clear data log out form google account log in again Done
not sure what you mean in "eu modul".

Any way I've tried to run your code, and get this error:
"Failure calling service package: Failed transaction (2147483646)"

I have CrDroid 11.6 installed on my phone (note 13 pro 5G), with global firmware.
My Kernel don't have SuSFS support (still looking for this)
I've installed the Yuri V1.5 and clicked on it's "play" icon.
In Play Integerty Fix Inject I only have these option. I don't find "use preview fingerprint" / spoff build

3.png
 
not sure what you mean in "eu modul".

Any way I've tried to run your code, and get this error:
"Failure calling service package: Failed transaction (2147483646)"

I have CrDroid 11.6 installed on my phone (note 13 pro 5G), with global firmware.
My Kernel don't have SuSFS support (still looking for this)
I've installed the Yuri V1.5 and clicked on it's "play" icon.
In Play Integerty Fix Inject I only have these option. I don't find "use preview fingerprint" / spoff build

View attachment 56050
This is very good you dont say you a re on CrDroid rom. When you are here i thing you are on xiaomi.eu rom so... what can i say i dont have CrDroid to told you the correct way, i use EU rom so....... pointless for me
 
  • Like
Reactions: bob987
I am trying to root my mi 11 ultra (star) with kernel 5.4.274. I can't find it on the SukiSU github, as they start from 5.10. What should i do to root my mi 11 ultra?
 
hi , my Kernel is 6.6.3 cant find it on the github page
device xiaomi 15 ultra
you can try with a larger version and hope it works. this mean android15-6.6.66-2025-02-boot.img download the file flash it via fastboot

fastboot flash boot_ab android15-6.6.66-2025-02-boot.img

and reboot if something goes wrong (bootloop) just restore your previous boot img. go to the foldre where you download the eu rom /images find boot.img and flash it via fastboot open terminal there in that folder and hit comand

fastboot flash_ab boot.img and you are good to go. you can try
 
witch android version is your kernel
Android 14 hyperos 1.0 latest. I have rooted using Magisk using VirusTotal's latest method. and all is working. Is there a reason to switch to susfs? If it is supported and you think it will be more stable then I am happy to try and switch.
 
Android 14 hyperos 1.0 latest. I have rooted using Magisk using VirusTotal's latest method. and all is working. Is there a reason to switch to susfs? If it is supported and you think it will be more stable then I am happy to try and switch.
no my frend your kernel version not the sistem look you kernel version what say there
 
View attachment 56073
Kernel version is 5.4.274?
yes it is. unfortunately not supported by sukisu-ultra, but you can try patch it byself just copy init_boot.img from your xiaomi EU rom folder to your phone install sukisu-ultra patch the kernel copy the file to your PC, enter your phone in fastboot mode again after that flash it in fastboot and reboot and look whats gonna say sukisu the comand after patch the fail is:

fastboot flash init_boot (patchet file name or drag and drop the file in the terminal)

if you have bootloop just flash the original init_boot.img from the xiaomi eu rom and you are good to go
 
yes it is. unfortunately not supported by sukisu-ultra, but you can try patch it byself just copy init_boot.img from your xiaomi EU rom folder to your phone install sukisu-ultra patch the kernel copy the file to your PC, enter your phone in fastboot mode again after that flash it in fastboot and reboot and look whats gonna say sukisu the comand after patch the fail is:

fastboot flash init_boot (patchet file name or drag and drop the file in the terminal)

if you have bootloop just flash the original init_boot.img from the xiaomi eu rom and you are good to go
My phone uses flash boot_ab not init_boot. I have already installed Magisk and got root that way and play integrity fix. Is there any benefit switching to sukisu for me would you say? I have only had Magisk for a day so I am not sure about the stability or anything like that just yet.
 
My phone uses flash boot_ab not init_boot. I have already installed Magisk and got root that way and play integrity fix. Is there any benefit switching to sukisu for me would you say? I have only had Magisk for a day so I am not sure about the stability or anything like that just yet.
do you now what is init_boot.img and boot.img ? this is 2 different type of file. Your phone use flash boot_ab if you want to flash the boot file and i speak for init_boot witch you can flash it with flash init_boot. Actually i don't understand what exactly you want if you have root. If you want to try SukiSU-Ultra just try it, if you don't want stay in old method for hiding root with Magisk. So The choice is yours. You say in the previous post before:

Is there a reason to switch to susfs?

What is susfs you can read here This module provides root hiding for KernelSU on the kernel level. So, you say: I have rooted using Magisk using VirusTotal's
What the hell is VirusTotal's and who use this method ? I can't believe it what the people say. The people with less or zero knowledge is better to don't touch nothing. I just gonna leave you to use whatever you want. :emoji_blush:
 
do you now what is init_boot.img and boot.img ? this is 2 different type of file. Your phone use flash boot_ab if you want to flash the boot file and i speak for init_boot witch you can flash it with flash init_boot. Actually i don't understand what exactly you want if you have root. If you want to try SukiSU-Ultra just try it, if you don't want stay in old method for hiding root with Magisk. So The choice is yours. You say in the previous post before:

Is there a reason to switch to susfs?

What is susfs you can read here This module provides root hiding for KernelSU on the kernel level. So, you say: I have rooted using Magisk using VirusTotal's
What the hell is VirusTotal's and who use this method ? I can't believe it what the people say. The people with less or zero knowledge is better to don't touch nothing. I just gonna leave you to use whatever you want. :emoji_blush:
I think i will stick to magisk for now as it is working, and then attempt susfs if magisk is unstable or has issues. This is the guide by virustotal i was referring to.

The reason i asked about init_boot and boot, is i do not think my phone has an init_boot partition. The rom version for my phone only has boot.img in the images folder, and my phone only recognises the fastboot boot_ab command. fastboot init_boot says there is no partition for this.

But thank you for the help. I will stick with magisk for now and then try susfs later if this does not work.
 
  • Like
Reactions: Tears Burn
If for your phone doesn't exist init_boot image file into the rom installation package and also if you take a look with any text editor into any of the rom instation script for init_boot and find nothing, then in your case have to patch the boot.img file instead init_boot.img.
 
If for your phone doesn't exist init_boot image file into the rom installation package and also if you take a look with any text editor into any of the rom instation script for init_boot and find nothing, then in your case have to patch the boot.img file instead init_boot.img.
init_boot.img refers to the way Android systems boot the operating system. boot.img contains the main part of the system image needed to boot the Android device. Includes the operating system kernel, as well as the necessary modules and files needed to boot the system. On most devices, boot.img is used for traditional boot processes. While init_boot.img is newer phenomenon in Android systems. Like boot.img, init_boot.img contains various files needed for system initialization, but is optimized to work with new versions of Android. Often contains specific initialization files that help to quickly boot devices with new architectures. In summary, the main difference is in the way it works and is optimized. init_boot.img is a more modern and specialized version of boot.img used by newer devices. So if you don't have an init-boot file in your rom folder you can't patch the file. init-boot is for kernel su. If you want to patch the boot.img file you have to use magisk. If you don't understand what you're doing, don't touch these files at all.
 
  • Like
Reactions: Gershy13 and ciubex
Just wondering is this method still functional for your gpay?

I'm Poco F3 with xiaomi.eu 14.0.8.0.
I've done kernelSU+ ReZygisk + Treat Wheel + LSPosed + SUSFS + PIF + TS + VBMeta Fixer + Yuri Keybox + Hide My Applist (HMA) + Cleaning up

Got basic and device integrity (no strong integrity)
Got Native Detector shows all good
Got Applist Detector shows all good

... annnnd GPay still detect root for some reason.
All bank app works good though.
 
Last edited:
Just wondering is this method still functional for your gpay?

I'm Poco F3 with xiaomi.eu 14.0.8.0.
I've done kernelSU+ ReZygisk + Treat Wheel + LSPosed + SUSFS + PIF + TS + VBMeta Fixer + Yuri Keybox + Hide My Applist (HMA) + Cleaning up

Got basic and device integrity (no strong integrity)
Got Native Detector shows all good
Got Applist Detector shows all good

... annnnd GPay still detect root for some reason.
All bank app works good though.
log out from google account clear data and cashe on google services clean data on gpay uninstall it. reboot your phone log in again in playstore download gpay and you are good to go
 
log out from google account clear data and cashe on google services clean data on gpay uninstall it. reboot your phone log in again in playstore download gpay and you are good to go
Already done that for multiple times...
- uninstall update and delete all data from google play, google service
- uninstall google wallet
- re-boot, re-install and re-login.
... and gpay still insist I'm rooting.

Do you mean I need to log out google account before I uninstall updates & clean up data?
And by Cleaning up I supposed it means clean data from google play, google service and google wallet? Is there anything else I should clean?
 
Already done that for multiple times...
- uninstall update and delete all data from google play, google service
- uninstall google wallet
- re-boot, re-install and re-login.
... and gpay still insist I'm rooting.

Do you mean I need to log out google account before I uninstall updates & clean up data?
And by Cleaning up I supposed it means clean data from google play, google service and google wallet? Is there anything else I should clean?
yes i mean exactly that you say. and what you use sukisu or magisk ? and you have device integrity right ?
 
yes i mean exactly that you say. and what you use sukisu or magisk ? and you have device integrity right ?
Yes I have basic + device integrity.
I'm using RKSU (a branch of KernelSU by Rissu) since the only Poco F3 kernel with SUSFS I can found (here) is requiring RKSU...
SUSFS4KSU works fine, not sure why Gpay still detect the root with everything pass on Native Detector.

Don't know if I can find another kernel good for SUKISU.
 
Yes I have basic + device integrity.
I'm using RKSU (a branch of KernelSU by Rissu) since the only Poco F3 kernel with SUSFS I can found (here) is requiring RKSU...
SUSFS4KSU works fine, not sure why Gpay still detect the root with everything pass on Native Detector.

Don't know if I can find another kernel good for SUKISU.
hm... sound intresting its not the kernel if you pass everything its good. Generate new keybox and try again the problem here is integrity not the kernel not the susfs all is good. you must try something. new keybox + generate new pif and try again.
 
Great post, my phone a little mess, currently is

Magisk
|--Busy box for android
|--Play Integrity Fix
|--Systemless Host
|--Zygisk -LSPosed
|---lucky patch
|---refusebrightness
|--Zygisk Assistant (hide root)

My question is do i need uninstall any thing before follow your guide to install SukiSU?
I’m out of touch, not sure if Busy box and Systemless Host still useful in 2025..
 
Great post, my phone a little mess, currently is

Magisk
|--Busy box for android
|--Play Integrity Fix
|--Systemless Host
|--Zygisk -LSPosed
|---lucky patch
|---refusebrightness
|--Zygisk Assistant (hide root)

My question is do i need uninstall any thing before follow your guide to install SukiSU?
I’m out of touch, not sure if Busy box and Systemless Host still useful in 2025..
yes, you must uninstall magisk before using sukisu