I think anyone who tried flashing Magisk on any of the latest phh GSI discovered that wifi, mobile data and calls suddenly get their teeth kicked in.
Since nobody appears to care about that issue much, we have to make do with a workaround.
Credits go to @xJovs for being the one to actually provide proper steps in this post, but since not many people will be lucky enough to stumble upon it while desperately searching through threads, I decided to make a thread here for all the lost souls.
Although the custom kernel part is supposedly optional, one can't say no to a functional custom kernel on Pie.
1. Download the ab superuser and the superuser apk from HERE and the SmurfKernel
2. Get your hands on a TWRP image
3. Boot into it with fastboot ( at the moment we can only boot into TWRP since Magisk is a no go )
4. Flash the SmurfKernel
5. Reboot into the OS
6. Boot into TWRP again
7. Flash the superuser ab zip
8. Boot into the OS and install the Superuser apk
9. Enjoy raw root permissions ( without all the Magisk goodies but still better than nothing )
Niiiiiiice
Also no one cares that substratum still won't work with this root method anyone found also a workaround for that ?
CroW_D said:
Also no one cares that substratum still won't work with this root method anyone found also a workaround for that ?
Click to expand...
Click to collapse
Yeah, I don't know why it won't work. Root permission should be root permission, after all.
The Marionette said:
Yeah, I don't know why it won't work. Root permission should be root permission, after all.
Click to expand...
Click to collapse
I thinks since it needs vendor 9.0 and not 8.1 could be
CroW_D said:
I thinks since it needs vendor 9.0 and not 8.1 could be
Click to expand...
Click to collapse
Vendor should have no effect on root permission.
And we can't use the 9.0 vendor on any phh GSI due to incompatibility.
The Marionette said:
Vendor should have no effect on root permission.
And we can't use the 9.0 vendor on any phh GSI due to incompatibility.
Click to expand...
Click to collapse
I tried with coming from h2os last time and magisk and subs was working but breaking other things. So I guess it should be vendor
This method kinda roots the phone. You can't use system root. Things like moving files through root explorer won't work cause you can't access system root. Things like substratum won't work cause of that
Nice Work and thanks for sharing!
romen288 said:
This method kinda roots the phone. You can't use system root. Things like moving files through root explorer won't work cause you can't access system root. Things like substratum won't work cause of that
Click to expand...
Click to collapse
I guessed that but didn't get to confirm it since I switched back to OOS Beta 1.
Related
Hi guys,
My Pixel are systemlessly rooted with Magisk since many months now, but for some reasons I'm tired by the method of Magisk: I want to touch at the /system partition, move or delete or edit system files and apps, and with Magisk I can't do it.
Okay, Magisk was pretty useful for keeping Safetynet pass, but with Xposed this ability becomes useless for me. Only things I'm still using is Magisk Hide for using Netflix or NFC paiment app, and Sony Framework module for using PS4 Remote Play.
Before I'm using Magisk and his systemless mode I was using SuperSU, and with it I had no problem with the system partition or with différents things like flashing Viper4android (didn't works whatever the way I use, magisk module or old system mode, it says the drivers need to be reinstalled), mouting partition/making file partition in Linux Deploy, stop background app, modifying the booting apps...
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
billiepreks said:
So I'm here now: are they exist a method for having system mode root and still using magisk modules ? Or maybe I've using the wrong way with Magisk and I've missed something for properly having root access ?
Thanks for your help ?
Click to expand...
Click to collapse
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
nine7nine said:
the whole point of magisk is to systemless modifications. I'm not sure that I follow all of the modifications that you want to make to the system partition?? or rather the specific apps that you want to use... but I can tell you that your /system partition (and others) are just mirrored with magisk and are tmpfs file systems...
I think the real /system lives in /dev/magisk/mirror/system, unless I'm mistaken....
question though; if you prefer SuperSU and only use magisk for safetynet, then why not just use a custom kernel that passes safetynet + SuperSU + suhide?. ... and then use that xposed or whatever....
anyhoo, you definitely have root access. but the intention with magisk and it's modules is to modify the system without actually modifying it directly....
Click to expand...
Click to collapse
Thanks for your help ?
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
- installing Viper4android drivers, it says "drivers needs to be reinstalled" everytime I launch it
- Linux Deploy, an app for running GNU/Linux distrib on your device, works the first time I launch it, but after reboot he said he didn't get root permission or found busybox, it's very strange.
Many things who worked before with SuperSU 2.79.
Edit : and what about SuperSU and CCMT ?
billiepreks said:
If Magisk create a mirror of /system as your said, this explain many things that I didn't knew since now.
This night I've made a clean installation of my Pixel, on stock 7.1.2 NJH47F with ElementalX 1.15 for hiding the unlocked bootloader, then I've flashed SuperSU 2.82 SR5. On xda I've seen that suhide 0.55 are discontinued since one year, and suhide-lite 1.09 who works with SuperSU 2.89 are uncompatible with Xposed, so I didn't flash it. There is a way to hide SuperSU with Xposed ?
Click to expand...
Click to collapse
You should look in Magisk's log to get a better idea of how it changes your system. trting to modify /system is pointless since it is a tmpfs mount (temperary)...
unfortunately, i can't help much with xposed. i don't use it. after it didn't work with Nougat, i ported a couple of it's modules to my rom (at the time) and then i got the pixel and i run Oreo + my own custom kernel + magisk...
xposed isn't providing any 'suhide' tyype functionality?
billiepreks said:
For my needs with the /system partition, I'll try to explain better myself, I give you some examples:
- Uninstalling system app in ES Explorer or TiBu, it works but after reboot those apps are still here.
- Editing files like build.prop, unable to save the edited file or to replace original file by a modified one
Click to expand...
Click to collapse
again, no point in editing your /system partition, it's a tmpfs mount, of course - any modifications will disappear on reboot.... you probably need to edit the real /system partition to make any change stick.
as far as the other apps, they obviously are trying to modify your aystem partition, which is why they don't work.... i think that you could install soumd mods via magisk modules?
i would recommend.consulting relevant forum threads on specific topics/apps though. u are bound to get better solutions&.
@billiepreks
Did you find the solution?
I'm in the same situation.
Did you try using TWRP's filemanager? I think it has true system access. You just need to mount the partition.
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:
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.
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.
Android 10 has this messed up file system that does not allow any writing of the system files. While I have root neither Root Explorer or any other third party apk can force it over. I also cannot install any application with Root Explorer. What's the good of root if we can't actually mod our own system files?
Also, since debloating everything and removing google everything, I can't use instacart anymore. It says I need Google Play Services. This NEVER was an issue on my Moto G7 Power.
At the very least is there a tool where I can unpack Super.Sparsechunk files and then repack them so I can flash them as stock via fastboot. All I want to do is delete the stock ringtones on this phone and replace them with my own .ogg files (as I've done on every Moto I've ever had). Thanks.
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
mingkee said:
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
Click to expand...
Click to collapse
I did all that. It still will not go to R/W. This seems to be an Android 10 issue.
Here you go my friend. Enjoy!
lebigmac said:
Here you go my friend. Enjoy!
Click to expand...
Click to collapse
Your method as of now is not working.
It's working fine on my Xiaomi (which is A slot only device) but you are right. The current version is not as universal yet as I'd like it to be. There seems to be an lpmake error at the very end of the script for those with A/B slot device.
Don't worry I am working very hard on identifying and fixing the error.
Soon your system shall be RW!