Hi to all
I have rooted OP3T and every time when I install new update, BETA small or full version zip file, I need again to install stock.zip from boatloader , then again, install TWRP and Super Su.
I hear that with Magisk I can easy install any update without lost TWRP and Root. I have flash Magisk and install from Google Store Magisk Manager.
So my question is how to install new update with Magisk and dont lost TWRP and Root?
Please tell me step by step
thx a lot for your answers
Magisk doesn't touch the recovery. And you'll still have to flash the Magisk zip since the boot image is updated whenever you update your system (Magisk modifies the boot image).
What does stay after an update (as long as you don't wipe /data) is any Magisk modules that you have installed. If you have a bunch of modules that change build.prop values, debloat system apps, change screen density, replaces system UI sounds, etc, you won't have to do those changes again after an update. They are found in the Magisk image in /data and will be loaded by Magisk at boot.
Even if you've wiped /data, it's just a matter of flashing the Magisk and module zips in TWRP after updating your system. No tedious manual editing of build.prop or deleting apps, etc. It literally takes seconds...
If you have issues with loosing TWRP after an update, you can easily fix that, right after updating. Just keep a copy of the recovery image on your device and flash it in TWRP.
Hi
Since PIE roms for santoni are available, some people, including me, can't root their santoni.
I don't know why.
Flash looks ok in recovery, but after reboot, Magisk Manager says that Magisk isn't installed.
I tried every solution found in forums here, but everytime, same result : "magisk isn't installed"...
So sad !
Could you guys (and girls) centralize here your solutions, step by step, from flash the rom to root it...
It would be so nice for helping desperate people...
I also tried SuperSU and am having the same problem. I've tried Magisk 17.1, 17.2 and the Canary build along with the newest SuperSU and the result is always the same. Flashes fine but Magisk Manager and SuperSU apps can't find root.
The weird thing is that Enpass always tells me that my device is rooted and that it's a security risk even though Magisk Manager can't find root.
Also, I'm positive Magisk is patching the ramdisk. The Uninstaller always finds a Magisk-patched image. I'm assuming something has to be happening during boot that's cancelling root.
Two things I don't understand :
- why some people, with same configuration, don't have root problem ?
- why, with same recovery, same flash method, root works with nougat/oreo rom, and doesn't work with pie...?
Just like that : do you think problem could come from the sd card ?
I'm using à 128 gb samsung sd-card. Maybe I should format it before trying again root ?
I'm not sure it's the problem, since I can flash all roms, but I could try...
Or flash Magisk from internal storage ?
Really desperate...
Hi,
I´m in the same situation like you.
Yesterday I made a new experience of that without solution:
- Backuped all
- Uninstalled magisk at twrp
- Installed santoni_twrp_silent 27_treble (recommended from dev to install havoc)
- Rebooted
- Formated data with factory reset
- Wiped vendor, cache, data... (everything)
- Installed havoc (version 2018-09-08)
- Rebooted
- Installed magisk at twrp
- Rebooted
Same issue like before...
If I try to install magisk on magisk manager I get the following log:
Copying image to cache
Device platform: arm64-v8a
Existing zip found
Extracting files
boot_patch.sh[73]: can't create /proc/self/fd/: Is a directory
MagiskBoot v17.1(17100) (by topjohnwu)
Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
No boot image magic found!
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory
boot_patch.sh[91]: can't create /proc/self/fd/: Is a directory!
Installation failed
It seems magisk can´t install correct in cause of failing permissions to create new directories. But why?
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Edit:
I think there´s an old magisk information written in device system who has to removed manually, cause magisk uninstaller is not able to do
Click to expand...
Click to collapse
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
newbie_or_not_newbie said:
Ok, but I wiped AND format data of internal storage, same results.
Do you think I should format/wipe micro-sd too ?
Click to expand...
Click to collapse
I don´t think so. Well, if you like you can try, but I think it´s an internal problem, not an external
So,
I tried another wipe of internal storage, made a format data with recovery. Then I flashed another pie rom, then magisk. And after reboot : tada !! still not working...
try with version 16.6 of magisk
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Lemmy554 said:
Great news, actually my magisk works on Pixys 2.1!
I installed this twrp:
https://drive.google.com/file/d/1RR-8WMNSQgx6QzQv5U4i-sST1Af42nrI/view
What I did:
Uninstalled old magisk, rebooted to twrp, installed magisk 17.2, rebooted, installed magisk manager 6.0 and it works.
The only thing is I didn´t rebooted until now, maybe it still works after next reboot or not...
Click to expand...
Click to collapse
I just tried this and it didn't work for me either. I tried multiple clean flashes, flashed MIUI then back to Pie and flashing things in different orders last night and nothing worked. I'm tired of messing with it. I don't know how to get logs without root. I've come to the conclusion that for now I either have Pie or root. Not both. lol
Me too. I stop trying every day a solution.
For the moment, no root for pie roms, so I keep staying with oreo roms (nice dot OS...) I can root.
Hope next builds of pie roms will accept to be rooted on our santoni...
You can try this:
1 Flash Magisk v 17.2, Reinica in fast boot mode, turn it off and turn the phone on again
2 Install Magiskmanager V6 APK, do not open and restart in recovery
3 Flash Magisk v 16.6 and ready...
It worked for me... important, do not update magisk... The root is lost again
Best regards
Thanks for your reply.
Did you have root trouble before trying your solution ?
yes, when installing Pie only. In oreo no, I tried it in havoc and pixys
Try OrangeFox recovery for flashing magisk.
hyperkin said:
Try OrangeFox recovery for flashing magisk.
Click to expand...
Click to collapse
That's what I've been using. Also tried TWRP. Neither worked for me. The flash always looks good with no errors but when I boot the ROM Magisk says it's not installed.
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
Sounds like a plan! I'll try it out when I get home from work and let you know how it goes!
Trying asap.
Thanks
neijzen said:
I just realize to make magisk work on pie roms i realize that i need dev miui firmware not stable miui firmware the file you need is named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1.zip i not sure why stable firmware wont work on magisk.
i used OrangeFox Recovery Project R8.1 for recovery
1. install rom PixysOS 2.1 as normal (clean flash). Note: LineageOS 16.0 also works I have tested it
2. boot up os to make sure it that everything is working
3. then reboot back to recovery
4. flash firmware zip file named fw_santoni_miui_HM4XGlobal_8.9.20_3219de02e5_7.1
5. reboot to system making sure that it still boots in os
6. reboot back to recovery
7. flash magisk 17.2 beta i think magisk 17.1 also works
8. reboot up back to system
9. installl magisk manager apk
10. done
i just uplolad screenshot just to prove it
Click to expand...
Click to collapse
This post right here works, thank you so much
Dear XDA,
Model: Xiaomi Redmi 4X(Santoni)
Used TWRP:
Installed latest Lineage OS 16.0 of November 20, 2019 with formatting internals and wiping system, vendor, dalvik and cache.
Installed lastest Magisk v20.1 from GitHub page
Booted ROM and installed "MagiskManager-v7.4.0.apk" from above link
As the result:
MagiskManager shows everything green
No root prompt in any application and Root Checker shows that root is not installed.
"Settings -> System -> 'Developer options' -> 'Root access'" have only two options: Disabled and "ADB only"
Already have tried:
Disabling power optimization entry for MagiskManager
Reinstall Magisk using MagiskManager
What might be the reason of no prompt issue?
Why not SuperSU: is it worth to tell why? For example, basically Netflix won't work etc.
Thank you very much for any working suggestion.
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
I Have Nexus 5x and Lineage OS 15.1.
For me it was Lineage OS issue. Instead 20191118 I flashed 20191105. I had some other weird bugs too.
Ænimal said:
This happened to me too once. What helped was simply re-flashing the 20.1 Magisk zip. It contains the Manager apk, so no need to install it separately.
Click to expand...
Click to collapse
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
vv77vv said:
What do you mean by reinstall? Something like that:
Wipe phone
Install Lineage OS image
Install Magisk zip
Boot
Reboot into recovery
Install Magisk zip
Boot
Are above the full steps you suggesting?
Click to expand...
Click to collapse
I thought I expressed myself pretty clearly. Well, a clean install of your system is always a good idea (given you backed up all your personal data) .You can also just extract the boot.img from your LOS image and flash that in twrp prior to flashing magisk. But what I did when the root prompt didn't pop up was simply flashing the magisk zip again in twrp, (maybe wiping caches as well) and after rebooting magisk su was working as intended.. Good luck
I have several modules in Magisk app and couple of apps having root authority after get root with Magisk (like Tasker). Now I want to update system while keeping my magisk apps and root-to-use apps working without any risk of stucking in reboot after install a new ROM.
Could I just firstly patch the boot.img of objective ROM in Magisk, replace the boot.img with magisk_pathed_XXXX.img and flash all the .img files needed? Will this way work? Or any other ways?
while flashing a newer rom version, the magisk modules are not deleted. After flashing the new version install magisk again and everything is working well. Before updatating the rom version "restore hide magisk by itself" if you have enabled it.
If you have modules like SmaliPatcher - These will cause a bootloop after update.
Disable all modules before any update and make sure to Restore the Magisk App if its hidden.
zuize411 said:
I have several modules in Magisk app and couple of apps having root authority after get root with Magisk (like Tasker). Now I want to update system while keeping my magisk apps and root-to-use apps working without any risk of stucking in reboot after install a new ROM.
Could I just firstly patch the boot.img of objective ROM in Magisk, replace the boot.img with magisk_pathed_XXXX.img and flash all the .img files needed? Will this way work? Or any other ways?
Click to expand...
Click to collapse
I take from your description that you are flashing a fastboot ROM. In that case you are correct, i.e.
take boot.img from new ROM, patch in Magisk and copy back into the original installation folder. Simplest is to rename the original boot image and name the new magisk boot image: boot.img
now you can simply start the installation batch and it will automatically install the magisk-patched boot.img
If you are using TWRP to flash the ROM this is not needed, just flash the corresponsing magisk installation ZIP/APK in TWRP right after the system update and BEFORE rebooting.
In addition @JazonX gave a good advice , but it really depends on which modules you use.
Hello,
I stuck in quite specific situation. I am using OnePlus 7T Pro (HD1913) with installed the most recent stock Oxygen OS 12.1 MP2 - 11.F.17. EU (Android 12) and Magisk 25.2 (25200)(33) stable release.
What I did I used Magisk hide option and renamed package to random one. After this operation succeeded by mistake I uninstalled Magisk Manager from my device, and that was big mistake. Since I installed Magisk Manager from apk file once again it doesn't detect Magisk root installation anymore. In result installed apps for which there were granted root privileges when Magisk Manager properly detected Magisk Root installation (before hiding operation) still have root privilleges (e.g. Tasker, Total Commander in my configuration). Of course for new apps Magisk Manager behaves like there would be no root so it doesn't ask for granting root privilleges.
What can I do now to make Magisk Manager aware that Magisk root is installed in my system? Is there any way to achieve that (below there is some explanation why it is a bit tricky to root Oxygen OS 12.1 MP2)?
Below there are steps which I already done and some explanation why I cannot simply re-root my device with Magisk package with e.g. TWRP etc.
1. Currently there is no working TWRP compatible with Oxygen OS 12.1 MP2. Whenever I try to perform 'fastboot boot twrp.img' (and many other users confirm that in this forum) bootloader stuck and TWRP is not being loaded. I didn't found any resolution for that. This is the reason why I cannot simply reroot my device with Magisk package again.
2. I tried to extract 'boot.img' from Oxygen OS 12.1 MP2 firmware and used Magisk Manager to patch it. Unfortunately it didn't resolve the issue becasue after command 'fastboot boot patched_magisk_boot.img' Magisk Manager still doesn't detect Magisk root.
3. Before the whole described here issue occurred in order to root my device I had to use Magisk Manager with the last version of Oxygen OS working on Android 11 (rooted with Magisk) and performed patching to inactive slot directly from Magisk Manager just after installation (before reboot) of Oxygen OS 12.1 MP2. This is the only way which worked for me. This is the reason why I cannot simply perform this process again now because I would have to erase all my data / configuration and revert to the previous Oxygen OS.
Thanks
A new APP desktop shortcut will be generated after random naming. Please look for it on your mobile phone
Hi phidix, have you solved the problem? I got into exactly the same trap and still looking for a way out...
It looks like I found the solution.
First, I ensured that I had the latest stock ROM installed without any modifications. For that, I downloaded the official ROM and flashed it manually using the old system updater with the local upgrade option. Just to be on the safe side, I had repeated that twice, so both A and B slots eventually contained the same stock ROM.
Then I installed Cygisk, the same steps as for Magisk (I extracted boot.img from the firmware, patched it with Cygisk and flashed with fastboot).
Voilà, my phone reverted to being rooted.