Database Info

Where is the guide on installing SuperSU on the original Google Pixel on 8.1?

Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.

SuperSU is not working in the Pixel with 8.1

Sh0X31 said:
SuperSU is not working in the Pixel with 8.1
Click to expand...
Click to collapse
Oh. I had no idea.
Do any root methods that aren't Magisk work?

daddylonglegs said:
Oh. I had no idea.
Do any root methods that aren't Magisk work?
Click to expand...
Click to collapse
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage

TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me

daddylonglegs said:
1) Magisk doesn't work with StickMount. I need a way for my USB-C flash drive to mount as something all file explorer programs can see. There seems to be no way to do this with Magisk
2) Magisk does not work with WifiTetherRouter. I need to use it to tether without being capped at 512kbps. It only works with "real root" like SuperSU.
3) I don't benefit at all from systemless modules because I use GravityBox, which makes the whole systemless thing pointless for me
Click to expand...
Click to collapse
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.

TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
1) OTG
2) There are tether modules on magisk and other tether apps that will work with magisk
3) How does gravity box make systemless pointless? To my knowledge gravity box just builds custom rom features on top of stock, systemless modules should work regardless and provide things GB cannot
Lastly SuperSU isn't to be trusted anymore as it is no longer owned and maintained by chainfire. And could you explain the "real root" thing because magisk is a very real tangible root.
Click to expand...
Click to collapse
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.

daddylonglegs said:
1) Doesn't that depend on the phone? Does my phone support OTG? And if so, why does my USB flash drive not show up in a bunch of apps?
2) None of them work with WiFi tethering except for WifiTetherRouter. PDANet works but it requires a PDANet program to be installed on the receiving computer, which means I am out of luck on stuff like the Nintendo Switch
3) Because from what I understand the entire point of Systemless root is to pass SafetyNet, and SafetyNet fails if you have GravityBox installed.
As for the "real root" thing, the developer of Auto Call Recorder here on XDA told me the newest version is not compatible with Magisk, only "real root" (his words). The developer of WifiTetherRouter told me the same thing.
Click to expand...
Click to collapse
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough

TENN3R said:
Looks like Magisk is becoming more and more popular nowadays, so I don't think any other method with 8.1 works.
What's the problem with magisk? It's super easy and you can also install systemless modules, which is a big advantage
Click to expand...
Click to collapse
KittyRgnarok said:
Pretty sure otg should work but I could be wrong. Try mounting otg via twrp. And ohh my bad I see what you mean about the tethering thing I misunderstood. As far as the magisk thing meh safetynet isn't that important and u can have a second slot that is properly intact and idk about the real root business but if that's what the devs said then fair enough
Click to expand...
Click to collapse
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?

daddylonglegs said:
Thanks so much for the reply!
For some reason when I flash TWRP on this phone my phone will only boot into recovery until I flash back the stock boot.img (or the patched Magisk one). I am using the newest TWRP. Anyone else with this problem?
Anyway I mounted OTG in TWRP using the bootable image for TWRP. Would it make a difference? Does it have to be done in the installed version of TWRP where TWRP is my actual recovery?
After enabling OTG in TWRP I still can't find my SD/USB store in storage/emulated which is where I need it to be if I want all my apps to see it. Is there any way to do that?
Click to expand...
Click to collapse
I don't flash twrp zip, just boot it, I know twrp on pixel oreo has still some troubles.
You can try to put your pin and AFTER (when you are on the main scrren with all the actions) plug the otg. On nougat this worked for me, now I just put the 2 or 3 files in internal storage so I don't use otg anymore from recovery so I don't know if this method works or not.

daddylonglegs said:
Hi,
I am trying to root my Google Pixel on 8.1. I was on Magisk for a long time but I gave up on it because a few root apps I was trying to use aren't compatible.
I read some guides but they are ridiculously out of date. They say to use an experimental version of TWRP because it fails unlock codes and such; a lot of really out of date stuff. Some don't mention the ElementalX step, and then other guides say a custom kernel is required for rooting. But I had root with Magisk and never had to install a custom kernel. Other guides are still telling me to use the signature zips which supposedly hasn't been needed in forever. Trying to piece this all together is causing me to rip my hair out.
Anyway this is what I did, and it kept failing (I kept getting a "patching sepolicy" error in TWRP).
1) I booted the TWRP.img
2) I installed the twrp.zip
3) I booted into recovery
4) I installed Elemental X 13.3 zip
5) I installed SuperSU zip
6) I installed SuperSUHide zip
This isn't working. Every time I try to open SuperSU it says I don't have root. I also get an error every time I boot about their being an internal problem with my hardware and to contact the manufacturer. I believe Elemental X 13.3 is the cause. I wiped my phone and reinstalled stock and I am no longer getting that error.
Can anybody let me know what the deal is? Do I still have to install a custom kernel to install SuperSU? If so, what are the steps? Obviously whatever I am doing is wrong. Thanks so much in advance.
Click to expand...
Click to collapse
Install ElementalX before TWRP if you wish to install TWRP.
SuperSU is no longer maintained and will not work any longer on modern versions of Android until further notice.
About the "internal problem" this can be completely ignored and does not harm the functionality of the device whatsoever.
Magisk 16.3 is the best version of Magisk and mounting USB-OTG shouldn't be problematic whatsoever. Mounting the drive in TWRP has no effect on it mounting in the system and vice-versa.
To mount the OTG in TWRP, plug it in, go to "mount" and select storage location, here you can choose between the internal sdcard and the USB-OTG storage device.
Regarding the mounting of the USB-OTG device in Android the drive must be formatted using a filesystem/partition scheme that Android is capable of mounting. I think FAT32 is the most compatible option.
Applications won't just magically see the external storage unless they're made to support such devices. Google kinda messed up some external storage functionality in Nougat and Oreo, it's kind of quirky. :silly:

Converting a user app to system app corrupts phone on 9.0

Does anyone have experience with turning a user app into a system app on 9.0?
I tried using terminal emulator + app systemizer on magisk and Link2DS both ways have corrupted the phone.

kittygotwet said:
Does anyone have experience with turning a user app into a system app on 9.0?
I tried using terminal emulator + app systemizer on magisk and Link2DS both ways have corrupted the phone.
Click to expand...
Click to collapse
Are you able to recover? If so, you may have to settle without it. I know Systemizer works on 8.1, but I didn't try it on 9.0 before I downgraded. I'm not aware of any other options besides manually moving it, but that would break your systemless root, and would also need to be done after every update.
If you can't recover but can get into fastboot, you can boot into TWRP and flash "Magisk Mount". That will allow you to remove the Systemizer module manually from the Magisk image and boot back into the OS. As for Link2SD, I've never used it, so I'm not sure what changes it made that would have to be undone in order to recover.

jallenhayslett said:
Are you able to recover? If so, you may have to settle without it. I know Systemizer works on 8.1, but I didn't try it on 9.0 before I downgraded. I'm not aware of any other options besides manually moving it, but that would break your systemless root, and would also need to be done after every update.
If you can't recover but can get into fastboot, you can boot into TWRP and flash "Magisk Mount". That will allow you to remove the Systemizer module manually from the Magisk image and boot back into the OS. As for Link2SD, I've never used it, so I'm not sure what changes it made that would have to be undone in order to recover.
Click to expand...
Click to collapse
I just flash-all to fix it then reroot with Magisk. How do I convert an app to system through recovery (in twrp)?

kittygotwet said:
I just flash-all to fix it then reroot with Magisk. How do I convert an app to system through recovery (in twrp)?
Click to expand...
Click to collapse
As long as you dont care about remaining systemless and passing SafetyNet, you could simply move the apk folder into the system app folder manually. You could do it either through TWRP's built in file manager, or do it live with a root capable file manager. Either way should work.
Again, it's not ideal as it will trip SafetyNet and must be done after every ROM update/flash. So, if you have anything that depends on SafetyNet, that's not an option for you.
Another possibility would be to look at the Magisk documentation for module building and make your own module which would inject whatever apk you need systemlessly. You could accelerate the learning process by downloading one that already does something similar and reverse engineering it to fit your needs.

jallenhayslett said:
As long as you dont care about remaining systemless and passing SafetyNet, you could simply move the apk folder into the system app folder manually. You could do it either through TWRP's built in file manager, or do it live with a root capable file manager. Either way should work.
Again, it's not ideal as it will trip SafetyNet and must be done after every ROM update/flash. So, if you have anything that depends on SafetyNet, that's not an option for you.
Another possibility would be to look at the Magisk documentation for module building and make your own module which would inject whatever apk you need systemlessly. You could accelerate the learning process by downloading one that already does something similar and reverse engineering it to fit your needs.
Click to expand...
Click to collapse
damn, i need safetynet for google pay. crap hopefully the apps update for 9.0 and fixes itself.

Android 10: unable to "Mount R/W", what do I do?

I just installed the latest Android 10 for Pixel/Sailfish. I have use Magisk to root using the Boot Image Patching, as TWRP doesn't works yet for Android 10/Sailfish. I have enabled systemless host in Magisk and rebooted.
Now I have installed the latest version of FX File manager. When I goto root (granted root) within FX, I click mount R/W, it said that the folder is read-only. I had the same issue with EX file explorer.
I mainly want to edit a few files in /etc/permissions/ and move a few apps to system apps
What can I do to get the mount R/W to work? These are my normal steps on Android 9 to get this to work, I am unsure if I am missing anything

From my limited understanding and a few brief trawls of Google you can't write to system on 10 as you could in 9 or lower. Probably a job for a magisk module/terminal and edit it in a systemless way so to speak.
You can fastboot boot twrp 3.3.1-0, decryption works, it may show mounting errors but it does work, been using it to flash magisk and ROMs on my sailfish without problem.

junglism93 said:
From my limited understanding and a few brief trawls of Google you can't write to system on 10 as you could in 9 or lower. Probably a job for a magisk module/terminal and edit it in a systemless way so to speak.
You can fastboot boot twrp 3.3.1-0, decryption works, it may show mounting errors but it does work, been using it to flash magisk and ROMs on my sailfish without problem.
Click to expand...
Click to collapse
This is what I suspect also. I do know 10 is quite new.
I have been able to flash Magisk no issues. Root access is fine (adblock, titanium backup works). HOwever, I can't seem to mount r/w using a file explorer. I suspect this has to do with the way Google have upgraded its security, but I'm not fully sure.

pennywaltz said:
I just installed the latest Android 10 for Pixel/Sailfish. I have use Magisk to root using the Boot Image Patching, as TWRP doesn't works yet for Android 10/Sailfish. I have enabled systemless host in Magisk and rebooted.
Now I have installed the latest version of FX File manager. When I goto root (granted root) within FX, I click mount R/W, it said that the folder is read-only. I had the same issue with EX file explorer.
I mainly want to edit a few files in /etc/permissions/ and move a few apps to system apps
What can I do to get the mount R/W to work? These are my normal steps on Android 9 to get this to work, I am unsure if I am missing anything
Click to expand...
Click to collapse
You can't do anything. As you've been told before, the system partition can't be edited by the user on Android 10. Whether it is because of security or something else I don't know, but it's not possible at the moment.

Here is the explanation:
https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/
There are some workarounds detailed in this article but I haven't been able to get them to work.

Can't modify system even after root

Hello people,
I have unlocked my phone yesterday and installed Magisk and root explorer.
I would like to replace the files in /system/fonts to change the default fonts. I tried to flash a twrp zip with new fonts and also manually tried to replace the fonts. But the system cannot be mounted as r/w in root explorer even after granting root permissions and flashing twrp zip does nothing. Is there any way to overcome this issue to mount system as r/w?
I mean what is the point of rooting if we cannot modify system!
Thanks!

Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.

Many modifications are starting to be systemlessly. Like viper4android and others. The worst is not being able to flash system/vendor images in recovery.

wopr33 said:
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Click to expand...
Click to collapse
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?

I don't know how TWRP works for the Poco X3, but for the Redmi Note 4 I copied the file using the built-in explorer, with no errors.
I think you need to activate the system partition in R/W in TWRP.

htcmusic said:
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
Click to expand...
Click to collapse
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html

Slim K said:
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Click to expand...
Click to collapse
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer

htcmusic said:
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
Click to expand...
Click to collapse
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.

wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ?
Click to expand...
Click to collapse
You don't need twrp to install a Magisk module. You can do that through the Magisk Manager just as easily.

wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
Click to expand...
Click to collapse
I just installed the magisk module with custom fonts in internal storage as mentioned in the github page. It was magical, I was trying to replace the fonts for the whole day and it didn't work. Somehow this magisk module does the job.

Question Pixel 7 Pro Stuck in read only mode (rooted with magisk 26.1) Am I missing something? HELP

Everything ive tried in FX Explorer fails. No matter what I try, for example editing build.prop or anything else, it constantly says read only. i cannot use any method to allow write access.
Did i miss something when i rooted with Magisk? I dont remember anything setting root to read only.
Anyone can help id appreciate any help.
Details on my root process...
Google Pixel 7 Pro, Factory Unlocked,
Android 13
Rooted using init.boot.img & magiskpatched.img
LSPosed 1.8.6 (6712) zygisk running, Magisk 26.1 with the following modules:
1. app systemizer
2. magiskhide props config
3. system apps (lucky patcher module)
4. systemless hosts
5. universal safetynet fix
6. zygisk LSPosed
Im not sure how to configure superuser in Magisk other than default settings such as mount namespace mode...Should any of this matter?

1st: props config is not needed. USF is good enough.
2nd: ofc you can't just edit any system file. The /system partition is RO by default to protect itself from idiots. For you to write anything to it, you need to enable root access (in the upgrade FX menu, swipe all the way to the right)
using root mode, you can now mount system RW temporarily, remember to mount it back to RO after you're done messing with it, a RW /system will not boot.

I thought magisk will just allow a remote link to a /system file, not actually write on it. It replaces via link, it does not actually change the file.