Related
Hi guys, I've been having problems getting magisk v11.1 to install correctly.
I have a Samsung galaxy s5 which I use to play about with. I flashed magisk v11.1 which installed properly. After starting up my phone and getting the Magisk manager app it's telling me magisk is not installed. Yet the manager also tells me its properly rooted 6:MAGISKSU (topjohnwu)
The manager gives me the option to download and install v11.1 when I install it through the manager app it says installation succeeded, yet when I reboot I get the same results again. Magisk is not installed, properly rooted.
Does anyone have any ideas what I might be doing wrong?
Ok. This has been reported a few times, but I've not seen it properly troubleshooted yet.
1 - Root is working on your device? You can grant root to root apps?
2 - Do you have a file called magisk.img in /data?
I can't see the file in that directory. I also did a search and nothing came up
I can use root explorer in ES file explorer
Just to make sure: it's supposed to be in the /data folder found in root (where you'll also find /etc, /system, and so on), not in your main storage. If it's not there, that's your problem. That the Magisk image isn't installing correctly.
Could you also upload a recovery log from flashing Magisk in recovery?
Sorry I made a mistake, I was looking in Data>Magisk folder, in / Data there is a file called magisk.img
Awesome. Then that's not the issue then...
Recovery log and Magisk log, please...
Sorry for the noob question, but where do I find the logs?
Exactly the same problem with my NOTE 4 on Android 6.0.1. After Reboot Magisk is gone. Without Reboot works perfect (SU and Safetynet).
Looks like temporary "magisk".
The Boot Image Path is automatic (mmcblk0p17). Maybe change. But which one? There are about 20 paths.
I did a quick search and found another couple of posts in the support thread about this issue. Guess what you all have in common? Samsung... The statistical material is way to small to make any definite assumptions, but it points to a trend. And we know that Samsung doesn't always play nice with Magisk.
Have you guys tried a custom kernel? No guarantees, of course...
Possibly useful logs for troubleshooting:
- Recovery log from installation (saved in recovery right after flashing Magisk, can also possibly be found in /cache/recovery after booting up the device).
- Magisk log. Found and exported from the Manager (make sure verbose logging is enabled), or if that doesn't work it can be found in the /cache folder (accessible though TWRP if nothing else works).
- Logcat from boot. Use a computer, connect the device and use ADB to catch a logcat from boot up until you can confirm that Magisk reports "not installed" (How to logcat).
If nothing works, open an issue on GitHub with a detailed description, logs and boot image attached (just make sure no-one else has opened one before, if so post your information to that issue).
Same problem
Same problem here in a G900F (galaxy s5) with [ROM][G900F][ALEXNDR] CQBW, i can grant access to apps and the magisk.img is in /data, but magisk manager says that magisk is not installed.
Attached magisk and recovery logs
recovery and magisk logs
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
K3vG said:
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
Click to expand...
Click to collapse
Did somebody knows something like this above for the NOTE 4 SM-N910F? I have no experience with custom kernels.
Since @K3vG managed to fix the problem with a custom kernel it's very probable that this is a compatibility issue with the stock boot image.
Would any of you fine gentlemen like to contribute to the community and development of Magisk? It'd be helpful if one of you could open an issue on GitHub about this, with details and a copy of the problem boot image. It'd probably also be helpful if the rest of you then could add your boot images...
Of course, there are no guarantees, but if there's an open issue on GitHub with the above mentioned information there's at least a chance that @topjohnwu can take a look at it and possibly even fix the compatibility issue.
Didgeridoohan said:
Since @K3vG managed to fix the problem with a custom kernel it's very probable that this is a compatibility issue with the stock boot image.
Would any of you fine gentlemen like to contribute to the community and development of Magisk? It'd be helpful if one of you could open an issue on GitHub about this, with details and a copy of the problem boot image. It'd probably also be helpful if the rest of you then could add your boot images...
Of course, there are no guarantees, but if there's an open issue on GitHub with the above mentioned information there's at least a chance that @topjohnwu can take a look at it and possibly even fix the compatibility issue.
Click to expand...
Click to collapse
There is already an open issue https://github.com/topjohnwu/Magisk/issues/94
ccerrillo said:
There is already an open issue https://github.com/topjohnwu/Magisk/issues/94
Click to expand...
Click to collapse
Awesome! I checked but missed that one. Then someone should upload a boot image to that issue.
Didgeridoohan said:
Awesome! I checked but missed that one. Then someone should upload a boot image to that issue.
Click to expand...
Click to collapse
What is that image? /data/magisk.img??
ccerrillo said:
What is that image? /data/magisk.img??
Click to expand...
Click to collapse
You'll find boot.img in your ROM zip or factory image. Alternatively you can make a backup of Boot in TWRP and upload that.
K3vG said:
I tried a custom kernel like you said and it seems to work now. The status is all passes. I used this [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
Click to expand...
Click to collapse
I flashed that kernel too, and then i can install magisk, but magisk manager tell's "SafetyNet failed CTS profile missmatch"
What i do:
1.- Flash Alexndr rom (G900FXXS1CQBW_DevBase_v3.8.zip << Android 6.0.1 - stable)
2. Reboot
3.- Flash [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
4.- Reboot
5.- Flash Magisk V11.1
6.- Reboot
7.- Enable Magisk Hide
8.- Reboot
9.- "SafetyNet failed CTS profile missmatch" :crying:
What i'm missing?? What steps did you follow to bypass SafetyNet??
---------- Post added at 09:11 PM ---------- Previous post was at 09:06 PM ----------
Didgeridoohan said:
You'll find boot.img in your ROM zip or factory image. Alternatively you can make a backup of Boot in TWRP and upload that.
Click to expand...
Click to collapse
I got it!! Thanks!
ccerrillo said:
I flashed that kernel too, and then i can install magisk, but magisk manager tell's "SafetyNet failed CTS profile missmatch"
What i do:
1.- Flash Alexndr rom (G900FXXS1CQBW_DevBase_v3.8.zip << Android 6.0.1 - stable)
2. Reboot
3.- Flash [EOL][KERNEL] [SM-G900F] [Samsung Stock M/LP] Boeffla-Kernel (25-11-2016) kernel
4.- Reboot
5.- Flash Magisk V11.1
6.- Reboot
7.- Enable Magisk Hide
8.- Reboot
9.- "SafetyNet failed CTS profile missmatch" :crying:
What i'm missing?? What steps did you follow to bypass SafetyNet??
---------- Post added at 09:11 PM ---------- Previous post was at 09:06 PM ----------
I got it!! Thanks!
Click to expand...
Click to collapse
did u manage to get this fixed?
I mean, did you found a way to get safetynet to pass with a custom kernel?
Here I'm going to explain how to flash magisk or use magisk with magisk modules in non-primary (i.e. secondary, data, ext-sd slot) ROMs in dual boot patcher environment.
What's needed?
ROM or boot.img (Which should be flashed as non-primary ROM)
Magisk manager app
X-plore file manager (or any other file manager)
Now,
Install magisk manager app (latest)
Extract boot.img from ROM mentioned above
Now,
Patch boot.img using using magisk manager app,
To do so, open magisk manager, go to install/install/patch boot image file so file manager will be opened up, select extracted boot.img file.
Magisk will patch it then and save file in sdcard/MagiskManager folder with name patched_boot.img
Now,
Rename patched_boot.img to boot.img & replace boot.img of ROM.
Now flash ROM using dual boot patcher app.
Reboot
Non-primary flashed rom will be booted
Here install magisk manager app
Download magisk v14.3/ v14.0 from install/install/Download Zip Only
(Or you can download it from official magisk xda thread)
Flash magisk.zip manually just like flashing any other module.
Reboot
Done.
Enjoy magisk in non-primary dual booted ROMs!
Thanks!
Better & best method is here:
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
Method 2..
Just patch Magisk v12.0
Flash from dual boot patcher
Reboot to non-primary ROM
Install magisk manager app (latest)
Flash magisk v14.0/14.3 manually
Reboot
Done.
How to flash magisk 14 manually in 2nd method?
lolnwl said:
How to flash magisk 14 manually in 2nd method?
Click to expand...
Click to collapse
Just open magisk manager app & flash magisk 14.3 just like flashing any other module.
lolnwl said:
How to flash magisk 14 manually in 2nd method?
Click to expand...
Click to collapse
Better try this..
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
And can you give advice on how to install magisk on primary ROM (I mean after I installed Dual patcher)?
@dr.bathman Does "Flash from dual boot patcher" is same as flash rom on dual boot patcher app?
exodius48 said:
@dr.bathman Does "Flash from dual boot patcher" is same as flash rom on dual boot patcher app?
Click to expand...
Click to collapse
Download magisk v14.3 from attachment of below link
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
Flash it just like flashing any other zip file (means patch it & flash)
little help
i did as mentioned in the DPB thread about flashing the modified magisk 13.4 for non primary rom and everything is ok but i dont know i try to install modules like viper4andrpod or adblock its there in installed but i cannot see viper in my system or can activate the adblock by terminal android ... should i patch the modules with the dual boot patcher !!?
thanks in advance
dr.bathman said:
Download magisk v14.3 from attachment of below link
https://forum.xda-developers.com/showthread.php?t=2447534&p=74551998
Flash it just like flashing any other zip file (means patch it & flash)
Click to expand...
Click to collapse
Do you have v14.0 stable?
exodius48 said:
Do you have v14.0 stable?
Click to expand...
Click to collapse
No, but v14.3 is working perfectly.
how i can activate the modules in the secondary rom should i patch the modules ?
I can't find the path to patch the boot img in magisk manager 5.5.5 (magisk 15.3)
Simonex16 said:
I can't find the path to patch the boot img in magisk manager 5.5.5 (magisk 15.3)
Click to expand...
Click to collapse
Open magisk manager, click on install. It will ask you if you want to patch a boot.img.
kloosgj said:
Open magisk manager, click on install. It will ask you if you want to patch a boot.img.
Click to expand...
Click to collapse
It asks me to flash magisk 15.3,nothing else
Easy step for Xiaomi MI Max2 & solution to lock screen issue.
--------------------------ROM1----------------------------
1.flash Custom-ROM-1 + flash magisk-v15.3-DBP-max2.zip--->reboot
2.setup Custom-ROM-1 + install DualBootPatcher.apk---->set kernel
=Now (Ramdisk is already up to date.)Status=
--------------------------ROM 2---------------------------
Patch Custom-ROM-2 with "DualBootPatcher-9.3.0.r409.g1ccd3798-win32.7z"
3.flash ROM-2_data-slot-1.zip--->reboot
4.setup ROM-2_data-slot-1 --->reboot
5.flash Magisk.v14.3(1437).zip
-IF Not show magisk'icon
5.1 install magisk-manager-v.555.apk
5.2 tap install update magisk.v15.3.zip
6.install DualBootPatcher.apk--->get Root -->set kernel
Note--Not try to pass safetyNet Check with "safetyNet Fix module".
https://mega.nz/#F!VuQmmKZS!qLT99EL17SKJ-7eevo9zzw
https://www.youtube.com/watch?v=yLSvCpZXZWI
Sorry need to ask the same: How can I install Magisk on my secondary ROM using DualBootPatcher? The "normal" way (patching and installing it) does not work - just brings me an error message.
Also installing MagiskManager and trying to install ZIP from there does not work.
So do I have to patch my secondary ROM ZIP with MagiskManage first and afterwards with DualBootPatcher and need to install the entire ROM again (loosing all data and settings)? Or can I install Magisk onto it somehow? (Reason is: 2nd ROM is RRemix and I cannot get root access besides using ADB and internal setting [which I did not try yet] - nothing worked yet to get it rooted!)
can Magisk 19.3 be installed
smallville7123 said:
can Magisk 19.3 be installed
Click to expand...
Click to collapse
Yes if you patch the bootimage of your RRemix ROM using Magisk. Then it can be used even with DualBootPatcher. But be warned! Do not update bootimage from within your secondary RRemix Magisk-rooted ROM - you won't be able to boot anymore afterwards (reflashing RRemix as secondary did the job and repaired it). If you want to update Magisk Bootimage you need to download it, patch your secondary RRemix bootimage with it and reflash secondary RRemix ROM completely using the patched bootimage.
I tried the first method and it worked thanks body.
I remember when I'm using Magisk 14.0 on Nougat 7.1.2 and Oreo 8.0 when i install module and then when i check module on Magisk Manager the module was installed
But when i install Magisk 15.3 on Oreo 8.1 when i install the module and then check on Magisk Manager the module doesn't installed properly even in twrp say instalation complete i try to install module via Magisk Manager first it was installed but when i reboot to recovery to install Magisk module which can be installed via recovery and then opening again module menu the module doesn't installed properly again instead it makes me more confused how to install module on Magisk 15.3
I forgot this
ZidanBlaster said:
I forgot this
Click to expand...
Click to collapse
Instead of all those screenshots it would have been more useful if you had provided the installation log, recovery log and Magisk log...
One thing to try is a complete uninstall and reinstall of Magisk.
Didgeridoohan said:
Instead of all those screenshots it would have been more useful if you had provided the installation log, recovery log and Magisk log...
One thing to try is a complete uninstall and reinstall of Magisk.
Click to expand...
Click to collapse
Ok when i trying to unistall and reinstall Magisk some of module can be installed but some of module doesn't installed properly when i check it the problem was being caused by this
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
Here's the recovery log
ZidanBlaster said:
Ok when i trying to unistall and reinstall Magisk some of module can be installed but some of module doesn't installed properly when i check it the problem was being caused by this
I:Found no matching fstab entry for uevent device '/devices/virtual/block/loop1' - change
Here's the recovery log
Click to expand...
Click to collapse
And what about the Magisk log? Even better would be if you could install the v15.3 beta (only difference is more verbose logging) and provide the magisk_debug.log from /data/adb.
Didgeridoohan said:
And what about the Magisk log? Even better would be if you could install the v15.3 beta (only difference is more verbose logging) and provide the magisk_debug.log from /data/adb.
Click to expand...
Click to collapse
Ok i try later
Every time I try to install a Magisk module, I get the error "magisk.img mount failed"
I've looked online and found a F2FS patch zip that didn't work, but someone has made a kernel for Qualcomm versions of this device
Is there any patches for the Mediatek version?
Huades said:
Every time I try to install a Magisk module, I get the error "magisk.img mount failed"
I've looked online and found a F2FS patch zip that didn't work, but someone has made a kernel for Qualcomm versions of this device
Is there any patches for the Mediatek version?
Click to expand...
Click to collapse
Go to twrp and format data and type yes
That will fix magisk
If you are facing "! /data/adb/magisk_merge.img mount failed" move to thread https://forum.xda-developers.com/app...uding-t3577875. Flash last zip. Move to magisk manager, install updated (2018.3.6) version. All modules should now install fine.
I know how to root with magisk and enable camera2api module. (by flashing patched_boot.img) but then , phone wont update, it shows up error. Is there a way to have google camera working and OTA enabled? many thanks
djavo22 said:
I know how to root with magisk and enable camera2api module. (by flashing patched_boot.img) but then , phone wont update, it shows up error. Is there a way to have google camera working and OTA enabled? many thanks
Click to expand...
Click to collapse
No you temporarily have to flash stock boot, do the update, flash patched boot image and enable camera2api again
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
Did you relock bootloder or get the ota with unlock bootloader?
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
can you please post further instructions step by step?
ki69 said:
Did you relock bootloder or get the ota with unlock bootloader?
Click to expand...
Click to collapse
Not needed.
minnuss said:
If you wish to install root just to enable camera2 api, do it via adb shell.
Then uninstall magisk, flash stock boot on partition a, check the camera2 api is it still enabled, it should be.
Do not change any other setting to the system or system files, just enable camera2 api via adb shell, and after root is gone, when you uninstall it, the OTA will work.
Mine is working, I updated last OTA with no problems, so I'm talking in first hand here.
O yeah, and mine camera2 api stayed enabled after OTA update.
Click to expand...
Click to collapse
Bro can u shw us step by step process !!
Sid.Boi said:
Bro can u shw us step by step process !!
Click to expand...
Click to collapse
X2
Sid.Boi said:
Bro can u shw us step by step process !!
Click to expand...
Click to collapse
Follow what he said, it's not hard and all the information can be found easily.
Can any of you that have enabled Cam2API tell us, does it make a difference in the OEM Cam app? I know it allows a GCam port to work, which is awesome, but any difference in OEM app?
thnx
You can all do it if you are still in software version 9.6.10.0 (Android One August update), or if you knew how to root your phone on the version that you have right now.
Go to this tool, https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Then follow this steps.
https://forum.xda-developers.com/showpost.php?p=77611720&postcount=51
I edited this quote for all of you for better understanding.
"Then I tried to use number 7. enable camera2 api, and the problem is that it did not install root correctly, when phone reboots, the user must download full magisk, then the proper root will function.
After enabling camera2 api, which i did manually with adb shell, it will pop up on screen to allow access with root privileges.
adb shell
su
When you enter su, it will pop up on phone screen to allow access with root privileges, allow it for one time, if it is not pop upping on the phone for root, then the root on the phone is not properly installed.
And then type
setprop persist.camera.HAL3.enabled 1
After that, complete uninstall of magisk from option within magisk itself, and when magisk reboot the phone in the process of uninstalling, quickly hold power and down volume button, go to fastboot and flash on both partitions stock boot.img.
Put the stock boot.img of the version of the phone you currently have to adb folder.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Check is the camera2 api enabled after the restart.
That was the correct steps for me."
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Does anybody know if the Video is also improved when using Gcam apk?
I can't find any online samples.
Nebrassy said:
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Click to expand...
Click to collapse
Can You Please Tell Me The Proper Proceedure. .
I Don't want my phone bricked.
I'm in august patch and having magisk installed with some system changes.
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Nebrassy said:
For me I used MagiskHide props config module to enable camera2
you don't need to fully uninstall magisk to receive otas, just restore images from magisk, receive the update and then install magisk to the inactive slot and use the reboot option in magisk (don't reboot normally)
Click to expand...
Click to collapse
Can U Please Tell The Steps Broadly?
rafihasan710 said:
Can You Please Tell Me The Proper Proceedure. .
I Don't want my phone bricked.
I'm in august patch and having magisk installed with some system changes.
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
Can U Please Tell The Steps Broadly?
Click to expand...
Click to collapse
If you only used magisk modules and didn't touch /system, just follow the instructions here
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you made any modifications to /system or just mounted it writable, you need to re flash the system image
Get the august fastboot image, unpack and flash system.img to your current slot, then follow the guide i linked
And don't worry you won't brick it, the update will just fail if you did anything wrong
Nebrassy said:
If you only used magisk modules and didn't touch /system, just follow the instructions here
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
If you made any modifications to /system or just mounted it writable, you need to re flash the system image
Get the august fastboot image, unpack and flash system.img to your current slot, then follow the guide i linked
And don't worry you won't brick it, the update will just fail if you did anything wrong
Click to expand...
Click to collapse
Thank You For The Instruction..
I've modified the system like camera2api and some magisk module....
If i flash the system.img what will change?
And how to do that?
How to flash system.img in current slot?
rafihasan710 said:
Thank You For The Instruction..
I've modified the system like camera2api and some magisk module....
If i flash the system.img what will change?
And how to do that?
How to flash system.img in current slot?
Click to expand...
Click to collapse
That restores the system to stock without modifications
Alternatively, you can just download the latest fastboot image and just flash the whole thing so you won't need to update after that
If you want to just flash system.img and then let your phone update, download the image I linked, extract it, open the images folder, it has system.img
open cmd/terminal, type fastboot getvar current-slot
if the current slot is a, then fastboot flash system_a <path to system.img>
like fastboot flash system_a D:\images\system.img
if the slot is b then use system_b
If you decide to just download the latest image instead, use miflash, instructions are on miui website, just be careful not to wipe data or lock the bootloader (it does that by default)
Nebrassy said:
That restores the system to stock without modifications
Alternatively, you can just download the latest fastboot image and just flash the whole thing so you won't need to update after that
If you want to just flash system.img and then let your phone update, download the image I linked, extract it, open the images folder, it has system.img
open cmd/terminal, type fastboot getvar current-slot
if the current slot is a, then fastboot flash system_a <path to system.img>
like fastboot flash system_a D:\images\system.img
if the slot is b then use system_b
If you decide to just download the latest image instead, use miflash, instructions are on miui website, just be careful not to wipe data or lock the bootloader (it does that by default)
Click to expand...
Click to collapse
Thanks.....
Can You Give The Download Link Of August System.img file.
Jeez what a nightmare... I'm not able to flash the system image at all, fastboot keeps giving random errors on both linux and windows.
rafihasan710 said:
Thanks.....
Can You Give The Download Link Of August System.img file.
Click to expand...
Click to collapse
extract from this
http://bigota.d.miui.com/V9.6.10.0....0.ODIMIFE_20180731.0000.00_8.1_2aeda83301.tgz