[HowTo] Magisk install without TWRP

[katerpanne]

I tried different Module's and on every module its gets a bootloop into the recovery of "MIUI Recovery 5.0" After a few reboots in to this recovery the phone boots finnaly up in the normale mode...

hm… could it be the magisk version? I did not have this issue with all modules

 

[Hippa12345]

hm… could it be the magisk version? I did not have this issue with all modules

Which Magisk version do you use then?
For example, Im installing 1 of these tweaks:

- Magisk Hide props config module from Github (finding on Magisk is not working anymore)
- Universal Safety net Fix .2.1.1 from Github (finding on Magisk is not working anymore)

It doesnt matter which one I installed first, after the reboot when 1 tweak/module is being installed then its boot automaticly to the MUIU Recovery 5.0.

 

[katerpanne]

Which Magisk version do you use then?
For example, Im installing 1 of these tweaks:

- Magisk Hide props config module from Github (finding on Magisk is not working anymore)
- Universal Safety net Fix .2.1.1 from Github (finding on Magisk is not working anymore)

It doesnt matter which one I installed first, after the reboot when 1 tweak/module is being installed then its boot automaticly to the MUIU Recovery 5.0.

why do you install this modules? I dont need them, only a question. Is magisk working without this modules or is a bootloop with any other module?

 

[Hippa12345]

why do you install this modules? I dont need them, only a question. Is magisk working without this modules or is a bootloop with any other module?

Is it right that you dont need to wipe the phone after its being flashed with the modified_Boot.img (root)?
I need these 2 modules. Passing SafetyNet , fingerprint adjust. It doesnt matter which module I install after the first module installed, and after a restart its boots into Muiu recovery 5.0.


What I bassicly did was this:

1. Find or redownload the zip file for your current ROM (Xiaomi_EEA\star_eea_global_images_V13.0.5.0.SKAEUXM-fastboot .zip)
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V25.2)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, suggest USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot fastboot flash boot magiskXXXX.img

Installing the tweaks through Magisk install from storage / .zip

 

[katerpanne]

Is it right that you dont need to wipe the phone after its being flashed with the modified_Boot.img (root)?
I need these 2 modules. Passing SafetyNet , fingerprint adjust. It doesnt matter which module I install after the first module installed, and after a restart its boots into Muiu recovery 5.0.


What I bassicly did was this:

1. Find or redownload the zip file for your current ROM (Xiaomi_EEA\star_eea_global_images_V13.0.5.0.SKAEUXM-fastboot .zip)
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V25.2)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, suggest USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot fastboot flash boot magiskXXXX.img

Installing the tweaks through Magisk install from storage / .zip

aha… does it mean that you have installed / flashed a rom and everything is working fine. then you select another rom where you find a boot.img and patched it?

that will not work in 99% if i understand correctly. you have to use the boot.img from installed rom

 

[Hippa12345]

aha… does it mean that you have installed / flashed a rom and everything is working fine. then you select another rom where you find a boot.img and patched it?

that will not work in 99% if i understand correctly. you have to use the boot.img from installed rom

No Im using the official rom for this phone, instead of a China build I use the EEA (Europe) version, instead of the Global version. Why? Less adds, more updates. More capable GPS Antennas to get a fix. Im using unlocked bootloader ofcourse for this. But passing Safetynet, I need these 2 tweaks/modules.

(psssst.... I was capable to fix it! )
Lets jump on how I fix this getting Root acces WITHOUT/NON-TWRP:

1. Start from scratch, download and flash the current ROM/ Xiaomi_EEA\star_eea_global_images_V13.0.5.0.SKAEUXM-fastboot
2. Walk through the wizard steps to setup, skip it.
3. Install the desired version of Magisk app (V25.2)
4. fastboot flash boot magisk_patched-25200_xxxxx.img Get Root access by NON-TWRP method, by flashing modified Magisk_Boot.img (get the Boot.img from the current ROM - then modified it with Magisk)
5. Installed the 2 tweaks:
- Magisk Hide props config module from Github (finding on Magisk is not working anymore)
- Universal Safety net Fix .2.1.1 from Github (finding on Magisk is not working anymore)
6. Now comes the tricky part. I'm testing almost the whole day on this problem, sometimes its boot-loops into the MUI Recovery by installing 1 of the first tweaks above this line, and sometimes it boot-loops into the MUIU Recovery direct after installing a third or in this case, a Callrecorder: callrecorder-skvalex or callrecorder-axet github.
7. Phone gets boot into the MUIU Recovery OR Early on, do the following:
Choose option - Wipe data - Wipe Data
8. Phone is being reset, Continue setup from beginning the wizard plan/steps.
9. Magisk is already being installed with root.
10. Install the 2 modules without no problem.
11. third module call recorder doesnt give a problem from this stage.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

There is something to wait to reset/wipe. So I did that, and now the phone has no problem running root WITHOUT TWRP / NON-TWRP. Thank you for thinking with me, and collaborating with me.

Next problem.....
Every root installed module such as Skvalex or Axet callrecording app, its not include in the settings of MIUI to Autostart these root apps/tweaks. There simply not listed in these menus. I can disable the battery saver activity, but there is no setting to Autostart it, what is need it. Every other native or downloaded app is listed.

How to fix this?

 

[katerpanne]

No Im using the official rom for this phone, instead of a China build I use the EEA (Europe) version, instead of the Global version. Why? Less adds, more updates. More capable GPS Antennas to get a fix. Im using unlocked bootloader ofcourse for this. But passing Safetynet, I need these 2 tweaks/modules.

(psssst.... I was capable to fix it! )
Lets jump on how I fix this getting Root acces WITHOUT/NON-TWRP:

1. Start from scratch, download and flash the current ROM/ Xiaomi_EEA\star_eea_global_images_V13.0.5.0.SKAEUXM-fastboot
2. Walk through the wizard steps to setup, skip it.
3. Install the desired version of Magisk app (V25.2)
4. fastboot flash boot magisk_patched-25200_xxxxx.img Get Root access by NON-TWRP method, by flashing modified Magisk_Boot.img (get the Boot.img from the current ROM - then modified it with Magisk)
5. Installed the 2 tweaks:
- Magisk Hide props config module from Github (finding on Magisk is not working anymore)
- Universal Safety net Fix .2.1.1 from Github (finding on Magisk is not working anymore)
6. Now comes the tricky part. I'm testing almost the whole day on this problem, sometimes its boot-loops into the MUI Recovery by installing 1 of the first tweaks above this line, and sometimes it boot-loops into the MUIU Recovery direct after installing a third or in this case, a Callrecorder: callrecorder-skvalex or callrecorder-axet github.
7. Phone gets boot into the MUIU Recovery OR Early on, do the following:
Choose option - Wipe data - Wipe Data
8. Phone is being reset, Continue setup from beginning the wizard plan/steps.
9. Magisk is already being installed with root.
10. Install the 2 modules without no problem.
11. third module call recorder doesnt give a problem from this stage.

There is something to wait to reset/wipe. So I did that, and now the phone has no problem running root WITHOUT TWRP / NON-TWRP. Thank you for thinking with me, and collaborating with me.

Next problem.....
Every root installed module such as Skvalex or Axet callrecording app, its not include in the settings of MIUI to Autostart these root apps/tweaks. There simply not listed in these menus. I can disable the battery saver activity, but there is no setting to Autostart it, what is need it. Every other native or downloaded app is listed.

How to fix this?

if i understood corectly… the modules are working fine if you wiped data? or do you mean wipe cache ? i never had to wipe data partition…

i dont know the modules but they should start if they are in magisk / lsposed on system start. or did i not understand it

on the other side… this is a detailed description

 

[Hippa12345]

if i understood corectly… the modules are working fine if you wiped data? or do you mean wipe cache ? i never had to wipe data partition…

i dont know the modules but they should start if they are in magisk / lsposed on system start. or did i not understand it

on the other side… this is a detailed description

Yeah, the modules work fine after wipe data. No, it's data, not Cache. I uploaded the pictures of it. What I did.
Yeah, it's really strange that this works now... Which version of Magisk are you running?

In the native settings of the orginal apps, there is under Permissions: AutoStart.
The tweaks or Module there is no AutoStart settings are defined... Thats really strange..How do I force these apps to be started?

UPDATE: Fixed by:
Delete the module without disabling the module and now the phonecallrecorder-app appears in Autostart(Apps-Autostart) Also disable in battery optimization.

 

[Hippa12345]

@katerpanne
How do I should update my phone on the propper way if there is a OTA update with Root available?

 

[katerpanne]

@katerpanne
How do I should update my phone on the propper way if there is a OTA update with Root available?

if you update your device, root will be history, but the modules are there. if they are not compatible with new rom it can end in bootloop

i suggest to disable the modules, update your rom and install magisk. then enable step by step the modules