I am using magisk 16.0 in stock marshmallow, but my problem is magisk modules are not installing out show 'mount failed' while flashing please help me
Is system mounted read only? In TWRP go to mount and check that the box isn't ticked.
So did I have to tick that box
please help me
no system mounted read only is'nt ticked
philje123 said:
Is system mounted read only? In TWRP go to mount and check that the box isn't ticked.
Click to expand...
Click to collapse
please help me
you need the "F2FS Loopback Bug Workaround“ module, you can download it from magisk manager, then flash it through recovery.
https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
borisxiao said:
you need the "F2FS Loopback Bug Workaround“ module, you can download it from magisk manager, then flash it through recovery.
https://forum.xda-developers.com/apps/magisk/guide-magisk-official-version-including-t3577875
Click to expand...
Click to collapse
this file is not also installing
Will they install via TWRP?
philje123 said:
Will they install via TWRP?
Click to expand...
Click to collapse
Yes!! I always install magisk modules via TWRP?
Related
Hi
On stock rom (ascend y300) I installed the app simple root checker from the play store, says I have root. But in twrp when I try to flash cyanogenmod I get this error:
set_perm: some changes failed
E:Error executing updater binary in zip '/sdcard (truncated)
Error flashing zip '/sdcard/cm-10.2.......
Failed
Click to expand...
Click to collapse
Please help I can't stand emotion ui.
Is there a way to grant full permissions to twrp?
ttouchpadd said:
Hi
On stock rom (ascend y300) I installed the app simple root checker from the play store, says I have root. But in twrp when I try to flash cyanogenmod I get this error:
Please help I can't stand emotion ui.
Click to expand...
Click to collapse
Does your TWRP has SELinux Enabled? Since TWRP has a Disabled and a Enabled version.
Fantassy123 said:
Does your TWRP has SELinux Enabled? Since TWRP has a Disabled and a Enabled version.
Click to expand...
Click to collapse
When opening terminal in TWRP (v2.6.3.3) I get "Full SELinux support is present", but I have no idea how to check its status, or change it?
The solution for me was to install CWM instead of TWRP, in which I found that the "system" and data folders were not mounted. I did, and after that I flashed my rom successfully. I didn't make any changes to SELinux settings.
Credits to
Thanks for the help ey
The solution for me was to install CWM instead of TWRP, in which I found that the "system" and data folders were not mounted. I did, and after that I flashed my rom successfully. I didn't make any changes to SELinux settings.
Thanks for the help ey
ttouchpadd said:
Hi
On stock rom (ascend y300) I installed the app simple root checker from the play store, says I have root. But in twrp when I try to flash cyanogenmod I get this error:
Please help I can't stand emotion ui.
Click to expand...
Click to collapse
i had the same error once but im not using ascend think this might help you try flashing to CWM and try installing even if it doesnt work re root the the device and try..
Good Luck
Hit thanks if it helped
Hello,
I have a problem and I will try to explain that precisely.
(I'm on Galaxy S6 G920F Stock Firmware)
I have tried to flash SuperSU in Systemless mode and I have followed this tutorial : http://forum.xda-developers.com/showpost.php?p=69412347&postcount=1215&branch_used=true
1st try :
Wiped all partitions and Flash Stock Firmware
Flash TWRP
SN Green response
Push Ramdisk and .supersu patch with ADB
In TWRP : Terminal : echo "SYSTEMLESS=true" > /data/.supersu
Flashed SuperSU SR2
Succeed with no error
And then... "Binaries need to be updated" in SuperSU app (even with reboot) and Root not working.
Then, I have tried with SR1 and SR3, not working too.
2nd try :
I have re-flashed the stock firmware (and wipe all partitions)
And tried again the same steps BUT NOW with Arter Kernel.
Not working too with SR1, SR2 and SR3.
I have missed something?
Thanks in advance!
Did you wipe data after install the SuperSU zip?
forumber2 said:
Did you wipe data after install the SuperSU zip?
Click to expand...
Click to collapse
I have a fresh install of the firmware, before installing the rom I have wipe data / system and all other
So no data left from my other rom
LucaXperia said:
I have a fresh install of the firmware, before installing the rom I have wipe data / system and all other
So no data left from my other rom
Click to expand...
Click to collapse
I mean did you wipe after install SuperSU zip, not before
forumber2 said:
I mean did you wipe after install SuperSU zip, not before
Click to expand...
Click to collapse
I have to wipe all my personal data after flashing SuperSU ?
LucaXperia said:
I have to wipe all my personal data after flashing SuperSU ?
Click to expand...
Click to collapse
You have to NOT wipe data after flashing SuperSU
forumber2 said:
You have to NOT wipe data after flashing SuperSU
Click to expand...
Click to collapse
Yeah, look at the first post, I updated it
I've had this same problem too. Here's what I did to resolve the problem
Code:
1. Clear all PHH SuperUser app data
2. Uninstall PHH SuperUser
3. Flash the latest version (r266 ATM)[URL="http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921"]HERE[/URL] phh super user binaries
4. Reboot and re-install PHH Superuser from market
5. Haven't had the issue since.
One thing I did notice was as long as you didn't need to request /new/ admin rights, things would still work. It was when you needed to grant a new app root access.
nolimit78 said:
I've had this same problem too. Here's what I did to resolve the problem
Code:
1. Clear all PHH SuperUser app data
2. Uninstall PHH SuperUser
3. Flash the latest version (r266 ATM)[URL="http://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921"]HERE[/URL] phh super user binaries
4. Reboot and re-install PHH Superuser from market
5. Haven't had the issue since.
One thing I did notice was as long as you didn't need to request /new/ admin rights, things would still work. It was when you needed to grant a new app root access.
Click to expand...
Click to collapse
I would like to use SuperSU
And PHH seems to be not Systemless
LucaXperia said:
I would like to use SuperSU
And PHH seems to be not Systemless
Click to expand...
Click to collapse
PHH was specifically created to handle systemless.
*UPDATED TO WORK WITH S244
*I can confirm this is working with the latest version of Magisk (v16.0)
you may not need to execute the script so install the SafetyNetFix first and test.
Hope all goes well, instructions below:
Install TWRP
Follow instructions on this Forum, easy to find.
Convert System from f2fs to ext4
System-less SU does not work on f2fs so you will need to reformat System to ext4,
In TWRP go to:
Wipe > Advanced Wipe.
Check System and Click 'Repair or Change File System' > Change File System > Select EXT4
You'll need to reinstall your firmware after you have formatted. (P2a42_S233/S244 Supports System in ext4 by default)
I would go for a clean install but you could try without wiping.
Run UnSU
Download UnSu here
Run UnSU in Recovery, this may mean you can miss the next step, try with or without (flashing boot image)
Flash original boot.img
This is only if you have tried rooting before (and System is already set to ext4) but failed safety checks, skip if not
Can be found on this forum in the Deodexed_P2a42_S233_170404_ROW.zip or Deodexed_P2a42_S244_170725_ROW.zip
(as long as you are on this firmware of course.)
Download Magisk v16.0
Click here to download latest Magisk
Install using TWRP, this will also install MagiskSU
Reboot, download and install MagiskManager.apk
Turn on Magisk Hide, Systemless Hosts
Hide Google Services Framework and Google Play Store
(I don't think this is necessary but no harm in doing so)
Download Kernel Adiutor from PlayStore
Could also run this in Terminal Emulator but with Kernel Adiutor the script is saved to run again if necessary
Click top left Menu, scroll down to: init.d (don't swipe to activate) Click + for new script and paste:
Code:
#!/system/bin/sh
echo "deleting magisk properties"
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
resetprop --delete ro.magisk.disable
resetprop --delete magisk.version
resetprop --delete persist.magisk.busybox
resetprop --delete persist.magisk.hide
Save then click and execute the script.
Install Safety net fix
(This may not be necessary, so reboot and check if you pass before installing this, if you do then no worries, you're good to go!)
Download and install the stable version from here
Install using Magisk Manager
Reboot phone and Open MagiskManager
Check that Safety Net Passes
Some apps may have detected your rooted phone prior to this and blacklisted your device ID
I recommend trying the app Device ID Changer
find here
Thanks to:
Magisk, TWRP, This thread for script and every contributor and developer for the Lenovo P2
Videophile said:
So this is how I was successful, I started with installing v13.1 and updating to v13.3
but you may have success directly installing v13.3.
Hope all goes well, instructions below:
Install TWRP
Follow instructions on this Forum, easy to find.
Convert System from f2fs to ext4
System-less SU does not work on f2fs so you will need to reformat System to ext4,
In TWRP go to:
Wipe > Advanced Wipe.
Check System and Click 'Repair or Change File System' > Change File System > Select EXT4
You'll need to reinstall your firmware after you have formatted. (P2a42_S233 Supports System in ext4 by default)
I would go for a clean install but you could try without wiping.
Flash original boot.img
This is only if you have tried rooting before (and System is already set to ext4) but failed safety checks, skip if not
Can be found on this forum in the Deodexed_P2a42_S233_170404_ROW.zip
(as long as you are on this firmware of course.)
Download Magisk v13.1
Install using TWRP, this will also install MagiskSU
Reboot, download and install MagiskManager.apk
Turn on Magisk Hide, Systemless Hosts
Hide Google Services Framework and Google Play Store
(I don't think this is necessary but no harm in doing so)
Download Kernel Adiutor from PlayStore
Click top left Menu, scroll down to: init.d (don't swipe to activate) Click + for new script and paste:
Code:
#!/system/bin/sh
echo "deleting magisk properties"
resetprop --delete init.svc.magisk_pfs
resetprop --delete init.svc.magisk_pfsd
resetprop --delete init.svc.magisk_service
resetprop --delete persist.magisk.hide
resetprop --delete ro.magisk.disable
resetprop --delete magisk.version
resetprop --delete persist.magisk.busybox
resetprop --delete persist.magisk.hide
Save then click and execute the script.
Reboot phone and Open MagiskManager
Check that Safety Net Passes
Update Magisk to v13.3
Update inside the Magisk Manager and reboot phone
Thanks to:
Magisk, TWRP, This thread for script and every contributor and developer for the Lenovo P2
Click to expand...
Click to collapse
I actually did not understand thid line -
You'll need to reinstall your firmware after you have formatted.
Why do i need to reinstall it after formation. After changing to ext4 cant i just boot the mobile. . And then root it with magisk. ? ??
If you format the system they'll be nothing there, hence why you'll have to reinstall firmware, or at the very least reinstall system. It will be blank after formatting.
Videophile said:
If you format the system they'll be nothing there, hence why you'll have to reinstall firmware, or at the very least reinstall system. It will be blank after formatting.
Click to expand...
Click to collapse
What if i dont format the system. Then??? Just wipe cache. Internal sd n data.
Well, as Systemless Su relies on your system being formatted as ext4 you would need to format, unless your System is already ext4 then as I stated in instructions you can skip that step. If your system is f2fs then you will need to format it to ext4 thus clearing it which will mean you will have to reinstall system to the newly formatted ext4 partition. I believe you could flash the system.img just as you would have done with the boot.img
Finally got this to work. Completely passes safetynet. Note: Do not install update from the app, it will cause bootloop. Download version 13.3 separately and then flash it using twrp. I also used lenovo p2 sefetynet fix magisk module along with the script above.
Uibon said:
Finally got this to work. Completely passes safetynet. Note: Do not install update from the app, it will cause bootloop. Download version 13.3 separately and then flash it using twrp. I also used lenovo p2 sefetynet fix magisk module along with the script above.
Click to expand...
Click to collapse
I know someone on this forum made changes that allowed them to update directly through the Magisk Manager.
Anyway, I have given up on Magisk. Modules that fails to install causing the Manager to crash, incompatibility with previous modules, difficulties upgrading to newer versions, official versions becoming as unreliable as betas, Google being a pain in the ass with frequent SN updates etc.
Can the files needed for this to work be added to the first post? Just to be sure it's been done right
Download Kernel Adiutor from PlayStore: is this really needed ?
robuser007 said:
Download Kernel Adiutor from PlayStore: is this really needed ?
Click to expand...
Click to collapse
It makes it easier to run the script but feel free to use an alternate script executor if you wish.
test passed on RR 5.8.2 but with "universal safetynet fix" MODULE................
I tried to install Magisk again (stock rom) just for the fun of it. Turned out I didn't need the safetynet fix...
eried1 said:
I tried to install Magisk again (stock rom) just for the fun of it. Turned out I didn't need the safetynet fix...
Click to expand...
Click to collapse
An easier guide: boot from twrp: backup all and safe it on your computer, convert only data partition to ext4(not the system partition!), reboot recovery and install magisk frop twrp: done!
Use magiskhide to hide root/bootloader.
If I rethink: is it really needed to convert data partition to ext4?
robuser007 said:
If I rethink: is it really needed to convert data partition to ext4?
Click to expand...
Click to collapse
I know you had to do it in the past. It's possible it isn't required any longer.
For magisk you still need to convert /data to ext
Will formatting from f2fs to ext4 result in lower performance of the internal partition?
will i be able to pass safetynet after installing xposed????
mdvamik said:
will i be able to pass safetynet after installing xposed????
Click to expand...
Click to collapse
No
---------- Post added at 03:52 PM ---------- Previous post was at 03:52 PM ----------
robuser007 said:
For magisk you still need to convert /data to ext
Click to expand...
Click to collapse
Yes
s251 ??
I'm on S251 now, can I still install magisk v.13.3 + root? Thanks in advance
nerofox said:
I'm on S251 now, can I still install magisk v.13.3 + root? Thanks in advance
Click to expand...
Click to collapse
You can, just flash the s244 boot image.
Is this possible using an SDCard? If yes, please share how.
I want to flash Android 9.0 boot.img modified to support Magisk.
Need the SafetyNet bypass module.
Will appreciate any inputs on how to install magisk on stock android 9.0 rom on a PX5 MTCE unit.
Thanks.
No image file exists.
marchnz said:
No image file exists.
Click to expand...
Click to collapse
You mean that the boot.img can't be flashed alone?
Thanks.
tribalfs said:
You mean that the boot.img can't be flashed alone?
Thanks.
Click to expand...
Click to collapse
Update.img is a full image. It can be used to flash a coreboard directly connected to a PC
marchnz said:
No image file exists.
Click to expand...
Click to collapse
ennysubo said:
Update.img is a full image. It can be used to flash a coreboard directly connected to a PC
Click to expand...
Click to collapse
Any other way to install magisk? Thanks.
Code:
tribalfs said:
Any other way to install magisk? Thanks.
Click to expand...
Click to collapse
Download the latest Firmware, open the update.zip and replace the boot.img and flash it via USB or SD-Card and Show If it booting
When it's finaly booted, Install Magisk Manager and show if you has Root Access!
tribalfs said:
Is this possible using an SDCard? If yes, please share how.
I want to flash Android 9.0 boot.img modified to support Magisk.
Need the SafetyNet bypass module.
Will appreciate any inputs on how to install magisk on stock android 9.0 rom on a PX5 MTCE unit.
Thanks.
Click to expand...
Click to collapse
1-Download adbkit
2-Connect device to wifi and PC to same wifi
3- copy your boot.img to internal memory
4- write the command
adb shell busybox dd if=/sdcard/boot.img of=/dev/block/by-name/boot
tuga_z said:
1-Download adbkit
2-Connect device to wifi and PC to same wifi
3- copy your boot.img to internal memory
4- write the command
adb shell busybox dd if=/sdcard/boot.img of=/dev/block/by-name/boot
Click to expand...
Click to collapse
Thank you. I will try.
Edit: Tried it but ended bootloop. Maybe a problem on boot.img patching. Not supported by Magisk?
Someone who has properly patched Px5 android 9.0 boot.img?
jamal2367 said:
Code:
Download the latest Firmware, open the update.zip and replace the boot.img and flash it via USB or SD-Card and Show If it booting
When it's finaly booted, Install Magisk Manager and show if you has Root Access!
Click to expand...
Click to collapse
I have tried this one but no success. Fails package validation. I guess it has to do with how the update.zip should be repacked. I just use 7zip in replacing the boot.img.
at this time magisk does not correctly do the patch in the rockchip boot.img so it's more accurate not to boot
jamal2367 said:
Code:
Download the latest Firmware, open the update.zip and replace the boot.img and flash it via USB or SD-Card and Show If it booting
When it's finaly booted, Install Magisk Manager and show if you has Root Access!
Click to expand...
Click to collapse
tribalfs said:
Thank you. I will try.
Edit: Tried it but ended bootloop. Maybe a problem on boot.img patching. Not supported by Magisk?
Someone who has properly patched Px5 android 9.0 boot.img?
Click to expand...
Click to collapse
tuga_z said:
at this time magisk does not correctly do the patch in the rockchip boot.img so it's more accurate not to boot
Click to expand...
Click to collapse
Any possible solution? I think it's still possible. @Hal9k_ has made it in his custom ROM. Thanks.
tribalfs said:
Any possible solution? I think it's still possible. @Hal9k_ has made it in his custom ROM. Thanks.
Click to expand...
Click to collapse
Not yet. I'm working on that
Does anyone figured how to install magisk ? I think Hal9k keeps it secret.
im using this guide
at section 4.
and i cant understand something.
i have Edxposed module, i need to delete it also or just call recording and themes modules should be removed?
please help me, thank you.
and one more thing, the app of magisk was changed, how do i get this line? :
Step 4: Click the back button in the top left, followed by the hamburger menu in the top left as well (3 horizontal lines). Click Magisk and then click the top Install button, followed by Install again, then Install to Inactive Slot. You may now click Reboot.
My way to update with root + twrp:
disable magisk modules
reboot in twrp
install full ota
install twrp
reboot twrp
install magisk
wipe dalvik cache
reboot system
enable magisk modules
provit!
ghost323 said:
My way to update with root + twrp:
disable magisk modules
reboot in twrp
install full ota
install twrp
reboot twrp
install magisk
wipe dalvik cache
reboot system
enable magisk modules
provit!
Click to expand...
Click to collapse
When you say to install twrp. What do you mean? Which file should i install when im already in twrp?
For example the latest twrp.zip. (twrp-3.4.0-0-guacamole-unified-installer.zip)
The boot.img is overwritten during the update. Therefore it is necessary to install twrp again. Then restart directly into the twrp. Now install magist ... As I wrote it before.
Very simple and reliable method. I've only had good experiences with it.
ghost323 said:
For example the latest twrp.zip. (twrp-3.4.0-0-guacamole-unified-installer.zip)
The boot.img is overwritten during the update. Therefore it is necessary to install twrp again. Then restart directly into the twrp. Now install magist ... As I wrote it before.
Very simple and reliable method. I've only had good experiences with it.
Click to expand...
Click to collapse
my phone is stuck on the red circle with the 2 white circle.
what can i do?
i did it:
Step 1: If you have any themes installed, such as Renovate ICE, Swift Themes, RoundyUI, or Substratum themes, remove them before continuing. Remove the Call Recording Enabler module if you have it. Restart if needed.
Step 2: Click on the system update notification. If it does not appear, open Settings, scroll to the bottom and click System, scroll to the bottom and click System updates. Click on the Install or Download and Install button and let it complete. Do NOT click Reboot.
Step 3: Open Magisk Manager and click the hamburger menu in the top left (3 horizontal lines). Click Downloads and then click the search icon (magnifying glass) in the top right corner. Type "TWRP" and click enter. Click the download arrow beside the module named TWRP A/B Retention Script. Do NOT click Reboot.
Step 4: Click the back button in the top left, followed by the hamburger menu in the top left as well (3 horizontal lines). Click Magisk and then click the top Install button, followed by Install again, then Install to Inactive Slot. You may now click Reboot.
Click to expand...
Click to collapse
I followed these steps but since the layout of Magisk Manager is changed, I don't know what to do after step 3:
https://forum.xda-developers.com/showpost.php?p=79741573&postcount=5
I followed the steps but I don't know what I should do at step 4. Can you guys help?
Open Magisk, click magist insatall "direct install" , click install again "Install to Inactive Slot"
Reboot
ghost323 said:
Open Magisk, click magist insatall "direct install" , click install again "Install to Inactive Slot"
Reboot
Click to expand...
Click to collapse
Thanks a ton man! It worked for me.
Abdülcelil said:
Thanks a ton man! It worked for me.
Click to expand...
Click to collapse
ghost323 said:
My way to update with root + twrp:
disable magisk modules
reboot in twrp
install full ota
install twrp
reboot twrp
install magisk
wipe dalvik cache
reboot system
enable magisk modules
provit!
Click to expand...
Click to collapse
when to flash custom kernel and edxposed?
aaryan45 said:
when to flash custom kernel and edxposed?
Click to expand...
Click to collapse
I don't use a custom kernel.
But as far as I know that will be installed last. So after you've installed magisk.
Edxposed doesn't have to be uninstalled to update. If it happened anyway, install it when everything else is gone.
Delete.
ghost323 said:
I don't use a custom kernel.
But as far as I know that will be installed last. So after you've installed magisk.
Edxposed doesn't have to be uninstalled to update. If it happened anyway, install it when everything else is gone.
Click to expand...
Click to collapse
what about DFE? when to flash that?
aaryan45 said:
what about DFE? when to flash that?
Click to expand...
Click to collapse
DFE?
ghost323 said:
DFE?
Click to expand...
Click to collapse
disable force encryption zip!
aaryan45 said:
disable force encryption zip!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-decrypt-oneplus-7-pro-t3951131