Anyone know of a exfat mounting solution that will work with Pie? Seems all the Magisk modules are for everything but Pie. Been flashing stuff with Magisk and TWRP all day, and (shockingly) haven't bootlooped yet. I want to make this boot.img my 6itch.
Related
Hello xda community.
I got some knowledge about flashing stuff on my oneplus 3. But Since I use Android oreo beta 29, 30, or stable 5.0 OOS version even when I use the aroma installer from Freedom OS. Magisk doesn't install propobly. .
Im using latest Twrp from Bluespark 3.2.1 -X
I can flash most off the magisk versions 15.0 - 15.1 - 14.6 without bootloops. I tried alot off them but when I boot the phone magisk is not installed.(there is no Magisk app)
When I install the magisk apk. the magisk is also telling me magisk is not installed.
On beta 29 SuperSU was working didn't try it yet on beta 30 but I really want to use Magisk.
I'm reading the forums here also on the OP community but seems like I'm the only one with this problem.
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
theduke7 said:
uninstall magisk app from the rom, flash rom again and then flash magisk 15.3... works fine
Click to expand...
Click to collapse
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Ghost123NL said:
Thanks for your reply.
I did a clean flash Beta 29 also on 30.
15.3 is not working to for me....
Click to expand...
Click to collapse
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
theduke7 said:
flash the rom then reboot to recovery then flash magisk... don't flash immediately after the rom ....
Click to expand...
Click to collapse
Also not working.
same steps with supersu is working only
Ghost123NL said:
Also not working.
same steps with supersu is working only
Click to expand...
Click to collapse
maybe the only way to make sure is to wipe everything , did you try with custom kernel?
try to flash rom reboot to recovery, then derp kernel (tested and works on latest beta) , then flash magisk... that worked for me at 1st try.
Flash magisk 14.0 and boot see magical working and then update magisk15.3 via magisk manager application.
Use OOS debloater from the themes and apps section to remove some apps from the system. Then reinstall magisk. Problem solved. We have a lot less space left in the system partition and that's the reason magisk is silently failing to install.
Facing same issue
Yesterday I updated to the latest Cosmic-OS Oreo ROM and lost my magisk root. So went to TWRP and tried flashing Magisk but it failed with a "cannot mount /vendor" error. I've already tried all the different rooting guides on XDA specific to Oreo and also tried patching the boot image from the magisk app but the result is my phone gets stuck in a bootloop and never boots. Using ls in twrp terminal to find the vendor boot device in /dev shows it doesn't exist. Not sure what to do next any input appreciated! :crying:
Using Alberto's 8.1 AOSP.
I found recently that if I try to flash 16.4 it gives me a lot of red stuff, so I went back to 16.0
I then flash the universal fix version of magisk.
I forget whether I had to boot in between there and if I had to let it load magisk mgr in there somewhere.
I use root for things like TBPro.
Works fine for me in Alberto's AOSP 8.1 which is my daily.
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Shakti Panda said:
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Click to expand...
Click to collapse
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Growtopia Jaw said:
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Click to expand...
Click to collapse
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Shakti Panda said:
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Click to expand...
Click to collapse
Sure, no problem
Hello,
I tried flashing Magisk-v20.4 and the phone wouldn't boot...
Now I'm playing around with the previous versions trying to figure how to make this work....
Hey,
Just for information, I am using OOS 9.0.9 and my Magisk version is 20.4.
Maybe problem is somewhere else?
Samurai_Brick said:
Hey,
Just for information, I am using OOS 9.0.9 and my Magisk version is 20.4.
Maybe problem is somewhere else?
Click to expand...
Click to collapse
I have 20.4 working...
I first tried to flash the ElementalX kernel, then Magisk, and when I tried to reboot, it just got stuck on the OnePlus logo. I thought it was a version issue, so I tried others and still the same problem.
Finally I thought to flash Magisk first, then boot up the phone and then flash the kerenel and then Magisk over, so I did this, and it all worked...
I guess something has changed in regards to Ramdisk, and Magisk needs to be flashed first, then the Kernels...
I'm flashing TWRP version from official TWRP website for poco F3. Successfully flash temporary and make it permanent using flash this TWRP version.
Boot up to stock miui (im not flashing custom rom yet), work fine. I want to flash magisk, but TWRP wong detect storage or the magisk zip. Anyone can help?
Official TWRP doesn't support Android 12's Encryption yet, that's why /data partition appears empty.
You need to use unofficial TWRP "skkk": https://dl.akr-developers.com/?dir=skkk/TWRP/A12
cyanGalaxy said:
Official TWRP doesn't support Android 12's Encryption yet, that's why /data partition appears empty.
You need to use unofficial TWRP "skkk": https://dl.akr-developers.com/?dir=skkk/TWRP/A12
Click to expand...
Click to collapse
Thank you. I will try this version.
Edit: It works. Thank you sir!!