Closed ProcessDuck closed 4 months ago
Shouldn't you be patching/flashing init_boot.img for your device per instructions? (There's generally no generic ramdisk in boot.img of devices launched with Android 13+.)
Shouldn't you be patching/flashing init_boot.img for your device per instructions? (There's generally no generic ramdisk in boot.img of devices launched with Android 13+.)
i tried that too but magisk didnt patch the init_boot.img but kernelsu patched it but it looped on the mi logo
How are you patching it?... What errors?...
Also, did you restore boot.img (and any other changed images) before flashing init_boot.img and booting?
How are you patching it?... What errors?...
Also, did you restore boot.img (and any other changed images) before flashing init_boot.img and booting?
i have the stock boot.img that boots to hyperos and i patch it from magisk app
?... That could be the issue... You shouldn't be patching that...
?... That could be the issue... You shouldn't be patching that...
then what image i should patch
i patched init_boot.img and flashed it to init_boot_a and init_boot_b . the mistake ive made is i tried flashing without a-b slots.
Ah, sorted then...
So fastboot flash init_boot /path/to/magiskpatched[random_strings].img doesn't work??
Device:Mi 13T Pro Android version:14 Magisk version name:27002 Magisk version code:81658d45 (27002) (D)
there is no custom recoverys for mi 13t pro and because of that i patched my boot img. it said its pached and i moved it to my pc and i opened cmd and i rebooted my phone to bl. i typed fastboot flash boot_a patched.img and fastboot flash boot_b patched.img. and it said thats flashed. i rebooted my phone and it booted normally without root. and yes i download my current hyperos rom and extracted the right boot img.