Flashing KSUnext init_boot not working anymore on my Xiaomi 17 (pudding)

[pcboy]

I was originally rooted with ksunext while on xiaomi.eu_PUDDING_OS3.0.305.0.WPCCNXM_16 on my Xiaomi 17 global, everything was working fine.
Then ksunext manager had an update from 3.1.0 to 3.2.0, which I did, and I patched again the init_boot img with "direct install".
After reboot, I only got a bootloop, which was weird.
Since there was also a new version of xiaomi.eu, I decided to simply upgrade to xiaomi.eu_PUDDING_OS3.0.306.0.WPCCNXM_16 . Achieved to boot fine, but of course lost my root.

Now I tried again to use ksunext manager to patch the init_boot.img of that latest OS3.0.306.0. I got the patched init_boot.img from ksunext manager, and I just did `adb reboot bootloader` and then in fastboot `fastboot flash init_boot_ab ksu_patched.img`.
Flashing worked fine, but after a `fastboot reboot`, I just get into bootloops.
This method used to work fine previously, what am I missing?

 

[Bamn09]

I managed to get it working with the (latest) spoofed APK version (and flashing through TWRP).
But although it's working fine, my bank and government apps are not working.

 

[pcboy]

I'm also using the latest spoofed version.
I just can't boot after flashing that init_boot. Could it be due to the vbmeta partition? I thought on xiaomi.eu the avb is off though. I have no issue flashing the original init_boot and booting afterwards. But any other init_boot fails.

 

[Bamn09]

Strange, for me no such issues.
It took some effort to install, but no bootloops on my side.
For met the main issue was that the install was not recognized. (App kept saying "not installed")

 

[pcboy]

Okay I made it work in the end. Very weird.

Here is what I did:

- I installed the latest TWRP, which is now working on the xiaomi 17 to decrypt storage.
- I rm -rf /data/adb/modules , as I suspected that maybe some previously enabled was causing an issue.
- I then flashed directly with TWRP the init_boot I wanted to flash.

Rebooted, and it's now working. It seems one of my modules in /data/adb/modules is responsible for my bootloop. Not sure which one yet.

 

[Bamn09]

Great!
For me it also flashed properly only when using recovery.

Are your bank apps etc working?

 

[pcboy]

I don't really use much bank apps on my phone to be honest. Only revolut, and revolut works.
Google wallet do not. I used to make it work with tricky store etc but that's a cat & mouse game a bit so not worth bothering with it. Maybe check https://xiaomi.eu/community/threads/xiaomi-17-google-wallet-banking-fix-for-rooted-global-rom.76464/

 

[dudijack]

Okay I made it work in the end. Very weird.

Here is what I did:

- I installed the latest TWRP, which is now working on the xiaomi 17 to decrypt storage.
- I rm -rf /data/adb/modules , as I suspected that maybe some previously enabled was causing an issue.
- I then flashed directly with TWRP the init_boot I wanted to flash.

Rebooted, and it's now working. It seems one of my modules in /data/adb/modules is responsible for my bootloop. Not sure which one yet.

Provide a list of the modules you have. I'll point you to the one responsible for bootlop.

 

[pcboy]

isI found the responsible module actually. It's a custom one I did some time ago that was simply using the meta overlayfs to add a /system/lib/libz.so.1 as curl needed it and I only add /system/lib/libz.so . Seems like it's not needed anymore as ldd on my curl now is correctly pointing to /system/lib/libz.so, so I just deleted my module and everything works!

 

[susanmark]

I was originally rooted with ksunext while on xiaomi.eu_PUDDING_OS3.0.305.0.WPCCNXM_16 on my Xiaomi 17 global, everything was working fine.
Then ksunext manager had an update from 3.1.0 to 3.2.0, which I did, and I patched again the init_boot img with "direct install".
After reboot, I only got a bootloop, which was weird.
Since there was also a new version of xiaomi.eu, I decided to simply upgrade to xiaomi.eu_PUDDING_OS3.0.306.0.WPCCNXM_16 . Achieved to boot fine, but of course lost my root.

Now I tried again to use ksunext manager to patch the init_boot.img of that latest OS3.0.306.0. I got the patched init_boot.img from ksunext manager, and I just did `adb reboot bootloader` and then in fastboot `fastboot flash init_boot_ab ksu_patched.img`.
Flashing worked fine, but after a `fastboot reboot`, I just get into bootloops.
This method used to work fine previously, what am I missing? Looking for a relaxing and professional massage experience in the heart of South Korea's capital? Seoul offers a wide range of wellness and therapeutic massage services that cater to both locals and tourists alike. Whether you need stress relief or muscle recovery, 서울출장안마 is your go-to solution for premium mobile massage services delivered right to your location. Skilled therapists are available around the clock to provide personalized treatments tailored to your needs. Booking is simple and convenient, making it easier than ever to enjoy a high-quality massage without leaving your hotel or home. Experience true relaxation and rejuvenation in Seoul today.

Most likely the KSUNext 3.2.0 update is bugged for your device. Download 3.1.0 APK manually, patch init_boot.img from the 306 ROM with that, and reflash. Also make sure you're checking your active slot first with fastboot getvar current-slot and flashing only that slot instead of using init_boot_ab.

 

[xchatter]

Most likely the KSUNext 3.2.0 update is bugged for your device. Download 3.1.0 APK manually, patch init_boot.img from the 306 ROM with that, and reflash. Also make sure you're checking your active slot first with fastboot getvar current-slot and flashing only that slot instead of using init_boot_ab.

Thanks brother, that helped me!