Database Develop

ZTE axon7 installed magisk 11.1.zip and magisk manager problem?

Hi,
I tried clean install official nougat on my phone, after I setup the phone and went back to twrp to install magisk 11.1zip and the magisk manager, I open magisk manager and it only show rooted, but no root permission, also when I go to settings the only option is dark theme, update notify, 2 developer logs, nothing else. The boot image location is blank. Does anyone know what is the problem, did I do something wrong?
PS: there was no Supersu or other root installed, only magisk 11.1 and magisk manager.
Thanks!!!

LazyJr said:
Hi,
I tried clean install official nougat on my phone, after I setup the phone and went back to twrp to install magisk 11.1zip and the magisk manager, I open magisk manager and it only show rooted, but no root permission, also when I go to settings the only option is dark theme, update notify, 2 developer logs, nothing else. The boot image location is blank. Does anyone know what is the problem, did I do something wrong?
PS: there was no Supersu or other root installed, only magisk 11.1 and magisk manager.
Thanks!!!
Click to expand...
Click to collapse
Did you try building from here? https://github.com/therealahrion/Collective-Dolby-Atmos-Ports/tree/master/axon7

LazyJr said:
Hi,
I tried clean install official nougat on my phone, after I setup the phone and went back to twrp to install magisk 11.1zip and the magisk manager, I open magisk manager and it only show rooted, but no root permission, also when I go to settings the only option is dark theme, update notify, 2 developer logs, nothing else. The boot image location is blank. Does anyone know what is the problem, did I do something wrong?
PS: there was no Supersu or other root installed, only magisk 11.1 and magisk manager.
Thanks!!!
Click to expand...
Click to collapse
Did you enable magisk hide? Reboot until root options show up again and disable it

Meowdib said:
Did you try building from here? https://github.com/therealahrion/Collective-Dolby-Atmos-Ports/tree/master/axon7
Click to expand...
Click to collapse
I think that his phone is the ZTE Axon 7 rather than using the Axon 7 Dolby Atmos.

Why magisk doesn't work with PIE Roms ?

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

No root prompt in Lineage OS 16.0 with Magisk installed

Dear XDA,
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.
Already have tried:
Disabling power optimization entry for MagiskManager
Reinstall Magisk using MagiskManager
What might be the reason of no prompt issue?
Why not AddonSU: this addon disables some applications to use such as Bank or GooglePay which are important here.
Why not SuperSU: is it worth to tell why?
Thank you very much for any working suggestion.

No root prompt in Lineage OS 16.0 with Magisk installed

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

Update lineageos OTA update and keep root access.

Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?

mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.

mtuxz said:
Hi
I installed LineageOS 20 on OnePlus 9 with the instructions on official wiki. Then I root my phone with Magisk. I install Magisk by sideloading the Magisk ZIP file and then install the apk as it's been explained in this video. Now I can't update the OS with updater in system settings. I find this guide that explained I need to uninstall and restore images in magisk then update my phone and reinsatall magisk before reboot. But magisk didn't create a backup during installation.
I followed this instructions to fix magisk stock backup does not exist
I create a backup with this guide and lineageos boot.img file and I can now restore images in magisk but I get the same error when trying to install the updates. I noticed that there is also dtbo in backup function and I did the same thing for backing up dtbo.img and it doesn't solve the problem. Is there anything I'm missimg. Should I use vendor-boot.img instead of boot.img?
Click to expand...
Click to collapse
ethical_haquer said:
I just learned that Magisk doesn't work after an OTA update. What I do is I normally update, uninstall Magisk, boot into Lineage Recovery, sideload the Magisk .zip file via ADB, reboot, and finish setting up Magisk through the app. There are other ways to do this, but this method works well and doesn't need anything special. Works for me!
Alteratively, look here.
Click to expand...
Click to collapse
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???

Minionguyjpro said:
I was exactly looking for this for my SM-T290, which also runs LineageOS 20. I think it is the most easy to deinstall Magisk root from the Magisk Manager, apply the update and then reinstall it. I think this also works with TWRP???
Click to expand...
Click to collapse
I'm installing an update right now. I would imagine it works with TWRP as well, but I only recently started using it.

I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).

droidman1992 said:
I realize that this may be a late reply, however, there is no need to do any of these convoluted processes.
Here is what I do, flash the Magisk as a .zip in Lineage recovery once and set everything up. Once the Magisk install is working you can apply OTA updates normally without Magisk and root being removed. On my OnePlus 7 Pro which is an A/B device I just install the OTA and hit reboot with Magisk seamlessly persisting and nothing else being required to preserve or reinstall it. The reason that this works is because the Magisk.zip installs an addons.d script which automatically runs after OTA updates and takes care of Magisk for you.
I installed many Lineage OS 20 OTAs and I never had to touch Magisk at all, it is always installed and working with no intervention whatsoever. Keep in mind that this will only work on A/B devices with Lineage recovery (which you should all be using anyway).
Click to expand...
Click to collapse
Well, I came to the fact I have a problem with TWRP. It uses OpenRecoveryScript for OTA updates and should also run addon.d scripts after it (Magisk uses this to survive an OTA). The only problem is that the scripts should run after the OTA flash, but for me, it doesn't. So I need to manually reflash Magisk and Gapps after installing an update. My data is encrypted, but I edited the addon.d script to flash the ZIP from the external SD card.