Database Info

Root broken and can't unroot

Hi, so I've been trying to root my FDR-L09 for a couple of days, already unlocked the bootloader and installed TWRP.
I also tried to flash a SuperSU Version through TWRP, but at first, it didn't show a SuperSU app. So I tried the Google Play version, which showed me the SuperSU icon (and Root Checker says my phone is rooted / Reboot apps work flawlessly), but Viper4Android says it can't detect root and BusyBox just won't install, so I suspected something went wrong with the root. So I tried to unroot my phone through SuperSU, didn't work. Then tried to manually delete su files in /system/app, /system/bin and /system/xbin, but I couldn't find any su files there.
There was a folder in / called su, where a bin folder was located with su files. So I tried to remove that one, and it works (Root Checker says my phone is not rooted and other apps that need root permission also don't work), but as soon as I reboot my phone the folder appears.
How do I permanently remove this folder? Because I want to start again from the point where I installed TWRP, but I want to prevent having to reset my phone again, since it takes a very long time to transfer files to my PC and back.
Also, for future root attempts, do you have any root tutorials which worked for you? Tried a SuperSU ZIP from here and here, also tried some kind of pph superuser, nothing worked properly.
I would be eternally greatful for any help. I just wanted to have Viper4Android on my new phone

just simply download current the firmware zip from official site and unzip copy update.app to sd card/dload and power off your device ..press all 3 buttons...boom ..your phone will be completely unrooted and bootloader locked with stock recovery!!{ from this now u can proceed to as your wish unlock bootloader and flash twrp and viper...}}NO NEED TO RESET YOUR DEVICE AND LOOSE DATA

VenuGopalu said:
just simply download current the firmware zip from official site and unzip copy update.app to sd card/dload and power off your device ..press all 3 buttons...boom ..your phone will be completely unrooted and bootloader locked with stock recovery!!{ from this now u can proceed to as your wish unlock bootloader and flash twrp and viper...}}NO NEED TO RESET YOUR DEVICE AND LOOSE DATA
Click to expand...
Click to collapse
Hi, thanks for replying.
I'm not really sure if I have found the correct firmware, I've downloaded Firmware Finder and selected the update.zip from the FRD-L09C432B381 package. But there are also hw/eu update_full_hw_eu.zip and public update_data_full_public.zip available. Which one do I pick?
Also, when I copy the update.app to the sd card, does it have to be any specific folder or just somewhere on the SD card? Thanks.
EDIT: Also, my current firmware is FRD-L09C432B380. Do I need to select the B380 one or B381? B381 is Full OTA, B380 is not.

Windowscratcher said:
Hi, thanks for replying.
I'm not really sure if I have found the correct firmware, I've downloaded Firmware Finder and selected the update.zip from the FRD-L09C432B381 package. But there are also hw/eu update_full_hw_eu.zip and public update_data_full_public.zip available. Which one do I pick?
Also, when I copy the update.app to the sd card, does it have to be any specific folder or just somewhere on the SD card? Thanks.
EDIT: Also, my current firmware is FRD-L09C432B380. Do I need to select the B380 one or B381? B381 is Full OTA, B380 is not.
Click to expand...
Click to collapse
go for full OTA and copy the update.app in dload folder {{create one folder name it dload }}
enough and power the device off and press 3 buttons:angel:
p.s
I think that the firmwares available in ff have 50-50% compitable they will work or they will not work :good:

VenuGopalu said:
go for full OTA and copy the update.app in dload folder {{create one folder name it dload }}
enough and power the device off and press 3 buttons:angel:
p.s
I think that the firmwares available in ff have 50-50% compitable they will work or they will not work :good:
Click to expand...
Click to collapse
Okay, I've tried the UPDATE.APP from the B381 and the B380 package, shut off my phone and rebooted it with all three buttons pressed, update fails at 5%. Tried to do an update through the stock update manager with FF, B381 gives an authenticate error, B380 boots at first, gets me into TWRP, and then gives me an error during the update process. And on top of that, I can't delete the dload folder I created with any file manager, also tried through PC.
Is there anything else I can try? Another source for B380/B381 maybe? I really want to avoid having to delete all my files.
And speaking of the worst case, what would be the best way to go about it? Would a factory reset from the normal menu do the trick, or do I have to do some kind of full wipe from TWRP? If it comes this far, I'd like to revert everything, so locked bootloader again, no TWRP, no root.
EDIT: Could delete the files through TWRP.

Update: I tried to install another B380 package through the FF app (there were 3 B380s showing, one OTA-MF, and two FullOTA-MF-PV), stock updater verified successfully and TWRP installed the update correctly. After reboot, my phone said something like "update failed", but the root is finally gone! So thank you for leading me in the right direction!

Windowscratcher said:
Update: I tried to install another B380 package through the FF app (there were 3 B380s showing, one OTA-MF, and two FullOTA-MF-PV), stock updater verified successfully and TWRP installed the update correctly. After reboot, my phone said something like "update failed", but the root is finally gone! So thank you for leading me in the right direction!
Click to expand...
Click to collapse
:good:

[SOLVED] hosts file restored at boot

Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231

bel3atar said:
Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231
Click to expand...
Click to collapse
If you used PHH to root, open the zip, open config.txt in a text editor, change "verity" to "noverity". Save and flash again.
You might need to flash back your stock boot image before flashing.
Edit: That link you posted there is full of misinformation.
Keeping system RO is best. It's not read-only/read-write that's causing it to roll back hosts.

I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip

bel3atar said:
I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip
Click to expand...
Click to collapse
Did you restore your stock boot image first?
Post your full build if you don't have it.
MHA/LON-LxxCxxxBxxx

ante0 said:
did you restore your stock boot image first?
Post your full build if you don't have it.
Mha/lon-lxxcxxxbxxx
Click to expand...
Click to collapse
mha-l29c432b182

bel3atar said:
mha-l29c432b182
Click to expand...
Click to collapse
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt

ante0 said:
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt
Click to expand...
Click to collapse
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?

bel3atar said:
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?
Click to expand...
Click to collapse
If you don't modify anything in /system, /product or /vendor you should still get OTA.
For example: installing Busybox modifies /system. Viper4Android modifies /vendor and /system.
If you need Busybox you should consider switching to Magiskv12. Its busybox is systemless (Doesn't modify anything).
And with Magisk you can use Android Pay and PokemonGO (and other apps that use SafetyNet).
MagiskHide is a little buggy on Mate 9, and other Huawei devices that use Nougat. If you enable it, fingerprint and pin will break after you reboot. If you just enable, run Android Pay, and disable after you will be fine.

Trying to Root phone using SuperSu - need help.

Hi.
This is my first post, I hope i'm in the correct forum.
I have a friend whom I requested to Root, Flash TWRP and Install LineagOS and GAAP on my OnePlus One phone.
He successfully flashed TWRP and installed LineagOS & GAAP but could not root my OnePlus One using SuperSu. He mentioned permission issue trying to root.
He went back to his country, so I am stuck trying to root my phone.
I would like to root my LineagOS (formally OnePlus One) using SuperSU.
I have downloaded/copied the latest SuperSu zip file into the Phone Sd/Download folder.
I went into custom recovery (TWRP).
Click on the Install button and verified I can see my SuperSu zip file.
Since this is my first time performing a phone root, I did not click SuperSu zip to install, until some experts can assist. me.
Just a few (Q's).
Questions:
a) Should I run any preliminary steps prior to clicking install SuperSu.zip?
b) Since I have LineagOS, GAAP apps already installed, will they be wiped after rooting SuperSu. If (Yes), any software available to backup/restore LineagOS & GAAP prior to the root process?
c) My friend mention “Permission problems with OPO”. Are there some options to open OPO and allow rooting SuperSu?
BTW: I do have the adb & fastboot installed if I need to enter some commands to get this done.
Thanks.
Tom.

a) No.
Download flashable supersu zip and flash it from here and flash it via TWRP https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
b) No.
But you can take nandroid backup through twrp in case something goes wrong.
c) As far as I know there is no problem with "permission" for rooting.
Happy flashing

Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.

tomx2x said:
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
Click to expand...
Click to collapse
I think I'm missing something. Did you tried any other method to root? I recommend a clean flash.
1. Download Sultanxda's unofficial lineageOS from here
2. Download Gapps from here. ( ARM-7.1-nano)
3.Download SuperSU from here
4. [Optional] take back up of your apps (No need to back up medias like photo,video,etc)
5.Got Recovery>wipe>advanced wipe
select system,data,cache and dalvik cache (DO NOT SELECT INTERNAL)
6.flash the zips you already downloaded in this order - ROM- Gapps - SuperSU
do not wipe anything after this step
7.Reboot
1st reboot will take some time (10-20 min ). Do not interrupt this process.
PS: I totally recommend Sultan's LineageOS over official LOS. You can actually feel the difference in smoothness and performance. Especially the Camera.
Feel free to check device specific forum for OnePlus One
Happy flashing!

@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.

tomx2x said:
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
Click to expand...
Click to collapse
Yes. Copy all 3 zip (rom,gapps,supersu) to you phone.
Let me know how it goes..

@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.

tomx2x said:
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
Click to expand...
Click to collapse
Can you send me a screenshot of supersu app?
I'm using the exact settings and I don't have any problem at all.
Do not let TWRP install supersu.

@psxda97
As you know the Supersu is a zip file. When I open/ then extract, the display will show folders & their contents.
I have attached all the folders & contents from supersu extract for your review.
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Here is the website link where I downloaded SuperSu 2 days ago.
" https://download.chainfire.eu/1114/...r&utm_medium=referral&utm_source=DonanimHaber “

tomx2x said:
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Click to expand...
Click to collapse
I meant this
Edit : So you've no supersu app on you phone?

@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.

tomx2x said:
[MENTION=7046372]
Should supersu app be on my phone after installation/rebooting?
Tom.
Click to expand...
Click to collapse
Yes.
Go to recover and flash it one more time
Then go to Advanced on twrp and select copy log (without kernel log).
Log will be on root folder of internal. attach the log in your next post
Also send me the screenshot of your about phone settings.
You're still missing something.

tomx2x said:
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
Click to expand...
Click to collapse
Go to system settings>developer options>root access and set it to "apps and adb"
If you flash the SuperSU.zip in TWRP on your device then you should have root.
I think you misunderstood from the beginning, did you download the SuperSU.zip and then extract it on PC and then try to install it? If so, that was completely the wrong thing to do. You might have to remove what you've done so far and then try again from a clean start, you might gave to flash your stock firmware to get a clean start.
Have you looked into whether you need normal SuperSU or whether you need systemless SuperSU?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Additional info provided - Anyone with advice.
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.

tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
The problem might be in the LineageOS ROM that you're using, I've seen others have this issue on other devices using LineageOS.
I don't recall what some of the solutions were.
@Sam Nakamura is pretty knowledgeable about the OnePlus devices, maybe he has some useful input.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs

Sam Nakamura said:
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
I haven't used LineageOS yet so I'm not familiar with its details, I was pretty sure you'd know though. [emoji106]
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

@Sam Nakamura.
Thanks for the info.
I have previously executed the steps in the order you posted. I was just asking if other sequences to flash these apps were plausible.
With the help of member psxda97, he documented similar steps 1-7 for me. (Please read Post #4 on this thread and my results in Post #7). It's basically a snapshot of what you posted regarding the order seq.
Unfortunately, my phone still did not root after applying the ROM, GAAP & Supersu in this order. I'm not sure why the root is declared successful in TWRP, and the phone remain un-rooted.
Do you suggest I rerun steps1-7 from Post#4 and include your echo statement before installing supersu?
The LineageOS extras, (you mentioned) has a built-in root.
I now have LineagOS from Sultanxda's installed on my phone. It is highly recommended by XDA members over the official LOS, for it's smoothness and camera enhancements. Sultanxda' release is 06/25/2017.
LOS extras has a release date of 06/21/2017. My only issues, whether to choose LOS extras. I will subsequently get the next “Official” LOS release for 6/25 and loose LOS Sultanxda installation.
Tom.

Tried Installing LOS extras 14.1
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.

tomx2x said:
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
Click to expand...
Click to collapse
Did you choose the correct arm(32) version of lineageOS su? I'd try the following:
Backup all partitions with twrp so you can return to your set-up later on..
Wipe everything except internal storage
Flash rom, (custom kernel), gapps and su
Boot up and check if it's working now
If not restore your backup and check next point
Alternatively:
Have you tried superSU with forced systemless via twrp terminal (by the way, if done correctly there shouldn't fallow a output with this command line..)
Flash supersu from here:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I never had issues with the beta but you can also use the stable version, downloads on post 1
Using Magisk as root and root management tool
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashable zip via twrp, if successful go to magisk settings, and check superuser and read the rest of Magisk's potential on the linked thread, my preferred method as it allows you to hide root from certain apps which deny service to rooted devices..
Important, it's not a good idea to flash lineageOS su, then supersu, then magisk after each fails, at least restore your clean boot partition from twrp or flash the boot.img from within your rom zip... Best would be clean of course - but as you have a backup of your previous system you can play around and make errors...
Sent from my OnePlus 2 using XDA Labs

System Download running continuously

Hi,
First post. New to Android. Have a 'systemless' rooted Pixel 2 with Magisk. It has the lated OS and security update, but the 'System Update' is stuck at 'System Update Downloading....'. I've tried:
1. Restart.
2. Turn off Automatic System Update.
3. Delete and reinstall primary account.
There must be some way to clear the system download app! I'd rather not start over...
Thanks for any help!
Tom

Did you ever figure out a solution? I have the same problem.

GreenRaccoon said:
Did you ever figure out a solution? I have the same problem.
Click to expand...
Click to collapse
Yes, I ended up flashing the latest image (walleye for me). The basic steps were fairly quick:
Open Magisk and click 'Restore'
Download latest OS image files (walleye for the pixel 2)
Edit flash-all.bat (or flash-all.sh for mac) to remove the -w (this stops the flash from wiping your phone)
follow normal install process for OS
reactivate Magisk using twrp, following the process for systemless rooting.
Hope this helps...
Tom

Is root available on EMUI9. 1?

Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!

htcdesire-hd said:
Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!
Click to expand...
Click to collapse
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk

zgfg said:
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk
Click to expand...
Click to collapse
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?

htcdesire-hd said:
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?
Click to expand...
Click to collapse
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)

zgfg said:
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)
Click to expand...
Click to collapse
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!

htcdesire-hd said:
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!
Click to expand...
Click to collapse
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.

irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
Ok I understand...
I saw that you can unpack the EROFS partition in a virtual environment, remove or modify system files and repack it...
But that's to complicated for my purpose...

irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?

htcdesire-hd said:
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?
Click to expand...
Click to collapse
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.

irony_delerium said:
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.
Click to expand...
Click to collapse
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...

htcdesire-hd said:
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...
Click to expand...
Click to collapse
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk

irony_delerium said:
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
Click to expand...
Click to collapse
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
One last question: how can I prevent update notifications now?

htcdesire-hd said:
One last question: how can I prevent update notifications now?
Click to expand...
Click to collapse
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc

zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
Thank you very much, that worked!

htcdesire-hd said:
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
Click to expand...
Click to collapse
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171

zgfg said:
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
Thank you for the tip!

zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?

htcdesire-hd said:
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?
Click to expand...
Click to collapse
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)

zgfg said:
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)
Click to expand...
Click to collapse
I didn't make a backup with HiSuite...
But I solved the problem by resetting the network settings:
Settings -> System -> Reset -> Reset Network Settings