Help with magisk - ZTE Axon 7 Questions & Answers

Hey guys
I'm running stock nougat B29 (err, B25 I think I mean) rooted and BL unlocked.
I installed magisk, with superSU already there because I read it will remove it.
It didn't seem to do so. So then I used the 'unroot' option in SuperSu, used the uninstaller flash for magisk, then reflashed magisk.
Now I get 'Rooted but no root access" status in magisk.
Presumably what I need to do is somehow flash boot partition from stock, but I'm not aware that is available by itself. Is there another option to fix this?
EDIT: Ok, so I reflashed stock B25, then flashed magisk, and I still get "rooted but no root access" and there's no magisksu in my list of apps. I thought this was supposed to be automatic, so maybe I'm doing something wrong.
thanks

Related

SuperSU

I'm on a B09, bootloader unlocked and rooted with SuperSU 2.65 A2017G.
Except from the 2.65 version, is there another one working for the A2017G?
I want to get Xposed and if I do understand I need SuperSU 2.75 or above to get Xposed to work in systemless.
If there isn't another version could you guys help to get Xposed working on my phone?
That would be much appreciated.
EDIT: Well I'm dumb, I assumed Oki's guide only worked on the A2017U variant. Sorry guys :/
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Yeah I figured it out with the help of Oki's guide.
Thanks for the answer!
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
nuserame said:
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
Click to expand...
Click to collapse
Did you make sure to disable system write protection? Boot into TWRP, open up the terminal emulator, and issue the command: reboot disemmcwp
I'm having a similar problem while flashing superuser. The error happens after the "patching sepolicy" line runs. The error prevents SuperSU from being installed at all. Any suggestions?
You need to flash twrp 3.0.3 or above and flash SuperSU 2.79
Latest SuperSU Causes Endless Loops on the Axon 7
Literally, every time I install the latest version of SuperSU on my axon I get an endless bootloop. These are SuperSU files I get directly from chainfire's website. There must be something im missing, or maybe im downloading the wrong version? Im not sure i was hoping to get some help. I just tried installing: SR3-SuperSU-v2.79-SR3-20170114223742.
>> Can anyone point me in the right direction of the latest SuperSU that works with the Axon 7 that doesnt bootloop it.
I remember that the Pixel phones had SuperSUs that were made for it. I am wondering does the same thing apply here?
I have installed everything right on my phone to the T. Everything was brand new stock.
Kinanizer said:
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Click to expand...
Click to collapse

Not sure if rooted? Problems with Busy Box

Any help would be greatly appreciated!
Stock 7.1.1
Unlocked BL
TWRP 3.0.4.1
SuperSU 2.79 systemless
I followed this thread to get Viper - https://forum.xda-developers.com/axon-7/help/dac-dobly-viper4android-v4a-t3448726
This was immediately after I installed TWRP and SuperSU. Busy Box said it installed but maybe not the version I selected, which I never saw before. Then SELinux said I don't have root. SuperSU seems to be working, root checker says I'm rooted.
I haven't restarted my phone since installing TWRP /rooting. What gives?
Same thing here, really want Viper4android working :/

I am rooted, but not happy with my current state

Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??

Any root method for C432B380?

I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377

[question] remove magisk modules without TWRP on Oreo?

Hello guys,
I had been using Magisk & Xposed on Nougat before Oreo rolled out in December. However after update I lost root. When I flashed patched_boot.img I got stuck in bootloop (So I returned to stock boot.img). I am pretty sure bootloop was caused by some incompatible Magisk module. The problem is that I don't know how to disable them now - I don't want to install TWRP (because I want to be able to get OTAs) and when I use only "bootable" version of TWRP, it can not detect any files/partitions, so I am unable to use "mount-magisk.zip" to remove wrong Magisk modules. So I am kind of stuck.
Here is what I want to achieve:
- remove incompatible magisk modules
- gain root without permanent TWRP
- profit
I have been searching this forum for quite a while but couldn't find some relevant consistent information. Any tips how to deal with this?
At the moment I am running Oreo /w January update.
Thank you
For others looking for similar answers, I was able to solve it:
I flashed TWRP, then using "mount-magisk" removed all modules, then using MiFlashTool flashed original rom (you can do that without loosing data) and then I just followed guide to root using patched boot.img.
Good luck
gexcube said:
Hello guys,
I had been using Magisk & Xposed on Nougat before Oreo rolled out in December. However after update I lost root. When I flashed patched_boot.img I got stuck in bootloop (So I returned to stock boot.img). I am pretty sure bootloop was caused by some incompatible Magisk module. The problem is that I don't know how to disable them now - I don't want to install TWRP (because I want to be able to get OTAs) and when I use only "bootable" version of TWRP, it can not detect any files/partitions, so I am unable to use "mount-magisk.zip" to remove wrong Magisk modules. So I am kind of stuck.
Here is what I want to achieve:
- remove incompatible magisk modules
- gain root without permanent TWRP
- profit
I have been searching this forum for quite a while but couldn't find some relevant consistent information. Any tips how to deal with this?
At the moment I am running Oreo /w January update.
Thank you
Click to expand...
Click to collapse

Categories

Resources