Related
Hey guys!
I'm pretty new here and pretty new to ROMs/Flashing (which is PROBABLY the reason this bug occured.)
Basically what happened is I have a stock Lollipop Moto X 2nd Gen, I unlocked the bootloader, rooted it. Everything worked fine.
Now yesterday I installed the Xposed Alpha (I wanted a better shutdown Menu and stuff like that). Pushed the zip to SD.
Installed it via recovery. Bootloop.
Went into recovery again, wiped Cache+Dalvik.
Booted up fine.
Didn't notice any issues until I noticed that I couldn't take pictures anymore. The Camera app would claim that the storage was full even though I have 8GB free. Then I tried screenshots. Error taking screenshots the phone said it was either full or not allowed. Then I tried to upload a file to the phone via PC. Error. Via Airdroid - Error: No Permission to write on SD card. Then I got suspicious. DId my phone turn my internal storage to read only?
I can still install apps. It just doesn't make sense to me.
I googled a bit and found a thread where people fixed the issue by running a fsck_msdos via terminal.
I wanted to try that too but I can't make out anything from the mountpoints though (Sorry I'm reall bad with Linux).
The xposed log has a few errors in it altough the tested module (SnapPrefs) seems to work just fine
Heres what it says in the log:
02-16 03:31:27.562 F/libc (2065): Fatal signal 11 (SIGSEGV) in tid 2068 (Compiler driver)
02-16 03:31:27.562 F/libc (2065): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb32870c0 in tid 2065 (main)
02-16 03:31:27.562 F/libc (2065): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb32870c0 in tid 2069 (Compiler driver)
02-16 03:32:27.622 E/DEBUG ( 356) unexpected waitpid response: n=2065, status=00000000b
Click to expand...
Click to collapse
Now of course I thought I made a backup but I didn't.
Is there a way to save the phone without having to result to a factory reset?
Would it help if I posted the output the phone gives me when I type in mount for you guys to tell me the right fsck_msdos input?
Thanks in advance for any help!
Reflash xposed in recovery.
diggitydogg said:
Reflash xposed in recovery.
Click to expand...
Click to collapse
Tried that. Didn't fix the problem.
Flashed Stock Lollipop Rom - working fine again.
Sadly, it doesn't seem to work yet with the Moto X yet.
Thank you though!
I'm using xposed fine on mine. The other thing I did was download sel mode change and set it to permissive. Also try a clear cache in twrp.
Try flashing the uninstaller xposed and then flash the xposed again, but wiping dalvik/cache
This is a thread to track known workarounds for known issues for Magisk Beta.
DO NOT post any questions or random stuff in this thread as they will be ignored. The point is to have a clear tracking table for known workarounds as they
are currently getting lost in the post spam of the official beta thread. Discussions on workarounds or the problems they aim to fix/alleviate, should happen in the official
thread.
ONLY post known workarounds with references to the posts that introduce them and validate them and I will add them to the list. What you are reporting
must be related to the Magisk Beta. This thread is not about generic issues unrelated to the beta.
Error 1 during installation of v13.0 (96f8efc)
Users who get Error 1 during installation of v13.0 (96f8efc), specifically those who get the following error in the recovery log:
Code:
ioctl LOOP_SET_FD failed: Device or resource busy
@jenslody has made a modified version of (96f8efc) that fixes the problem for many users. LINK HERE. This version uses an older updater-binary script that correctly identifies non-64-bit paths to install Magisk (afaik).
The .zip package has been updated and now also includes the fix for very slow installation on some devices (described below).
Apparently the real issue behind this error is the toolbox failing to mount the loop device as reported by @Deic here: LINK HERE
The fix is moving the bundled busybox path variable earlier in the path export. I have modified the current update-binary script (which also includes the very slow installation on some devices fix) in the .zip attached here: LINK HERE
SafetyNet fails with v.13.0 (96f8efc)
@Deic has made a module that might solve the issue. LINK HERE. It should be noted that this doesn't fix every possible issue, since some modules like Xposed Framework will trigger SafetyNet no matter what you do. Try disabling all your modules, verify that SafetyNet passes, then one-by-one reactivate the modules to identify the culprit.
Viper4Android doesn't work (multiple causes)
Status: Abnormal
If you are using v.13.0 (96e8efc) and V4A installs but the Driver Status says "Status: Abnormal," user @LazerL0rd provided a solution HERE. Download the .txt file and place it in /magisk/.core/post-fs-data.d/, then change the '.txt' to '.sh'. Change the permissions to 0755.Processing: No in apps like YouTube
This can be remedied in some devices by removing the deep_buffer in the various audio_policy and audio_effects system files. You can make a script to remove these lines yourself or use the Universal Deep_Buffer Remover [AUDMODLIB] module by @ahrion if you are already using his ViPER4Android FX 2.5.0.5 [AUDMODLIB] module (note that this is not the one found in the Magisk Manager modules repo!).
Installation of v.13 beta takes hours!
According to many patient users, the installation will succeed, even if it takes hours. @Nodens explains what the problem is, and a solution for it, in this informative post: LINK HERE.
Modded 96f8efc .zip package by @tdunham : LINK HERE.
This is fixed in current beta.
MagiskHide failing to start.
Magisk log shows the following error:
Code:
bind_mount: /dev/magisk/mirror/system/xbin/dexlist -> /system/xbin/dexlist
* Running module post-fs-data scripts
[B]resetprop: prop [persist.magisk.hide] does not exist[/B]
** late_start service mode running
* Running service.d scripts
@_litz explains the problem and how to fix it here: LINK HERE.
Magisk Manager is not getting installed / Magisk Manager FCing
A lot of users report that the installer is not installing the manager automatically for them.
The Manager is included in the .zip file, in directory "common" and is named "magisk.apk. Extract it and install manually.
@p34rp34r also reports that reinstalling it manually has fixed the Manager FCing for him and other users: LINK HERE.
Module installed through Magisk Manager not visible on reboot
There have been several reports about installations of modules through Magisk Manager that are not visible in the Manager on reboot.
The big majority of those reports also report that on second reboot the module is properly listed.
It has also been reported that this never happens when modules are installed through TWRP instead.
According to my tests this also looks fixed on the latest beta. If someone still experiences this on the latest beta, please report it on main thread.
Magisk is not available on boot after installation but no error in shown in TWRP
@jenslody explains the issue and offers a modded zip here: LINK HERE.
Credits: The initial list was compiled by @p34rp34r in this post: LINK HERE.
*reserved*
*reserved2*
*reserved3*
*reserved4*
*reserved5*
I also linked my post (link is on the OP here already) for the slow install issue and added to your comment for Magisk issues on Github.
https://github.com/topjohnwu/Magisk/issues
I updated my post ( https://forum.xda-developers.com/showpost.php?p=72704270 ) and attached the zip-file directly, because my server is currently down, due to technical problems of my hoster.
The updated zip ( https://forum.xda-developers.com/attachment.php?attachmentid=4187406&d=1497908496 ) also includes the fix for very slow loading by @tdunham .
I'll also add this for MagiskHide failing to start ....
Check your Magisk log for the following error:
bind_mount: /dev/magisk/mirror/system/xbin/dexlist -> /system/xbin/dexlist
* Running module post-fs-data scripts
resetprop: prop [persist.magisk.hide] does not exist
** late_start service mode running
* Running service.d scripts
If you see this, the installer failed to setup default props on your device. You can verify this by issuing the "getprops" command from an ADB shell, and looking specifically for :
persist.magisk.hide
persist.magisk.root
They should be missing. You can add them with the following commands, then rebooting :
RESETPROP persist.magisk.hide 1
RESETPROP persist.magisk.root 3
After reboot, you should see the following indicating MagiskHide correctly loads:
* Running module post-fs-data scripts
resetprop: getprop [persist.magisk.hide]: [1]
* Starting MagiskHide
hide_pre_proc: Hiding sensitive props
resetprop: getprop [ro.debuggable]: [0]
resetprop: getprop [ro.secure]: [1]
hide_list: initialize...
hide_list add: [com.google.android.gms.unstable]
IMPORTANT! : if MagiskHide does not start, SafetyNet will never pass!
"Device or resource busy" – This is caused by "too many days links" as seen sometimes in failing to flash stock firmware on Nexii. I have noticed it may be caused by MTP so restarting your phone a few times AND DISCONNECTING from your PC is a massive help.
LazerL0rd said:
"Device or resource busy" – This is caused by "too many days links" as seen sometimes in failing to flash stock firmware on Nexii. I have noticed it may be caused by MTP so restarting your phone a few times AND DISCONNECTING from your PC is a massive help.
Click to expand...
Click to collapse
Mind giving me some more info? Where does the "Device or resource busy" error pop up? In a log? Magisk? Recovery? What behavior is associated with it? (Failure to install? Some component or function not working?)
Nodens said:
Mind giving me some more info? Where does the "Device or resource busy" error pop up? In a log? Magisk? Recovery? What behavior is associated with it? (Failure to install? Some component or function not working?)
Click to expand...
Click to collapse
After copying lots of files to a device, you see this error when trying to flash an image to your device.
It's an error limited to the io governors which cancel out tasks after some time "deadline" AND (correctly me if I'm wrong) any NON-UFS storage devices (as ufs can read and write same time {double helix} therefore it doesn't need to wait to do one task at a time).
This error will occur if there eMMC device is being used to read and write too much or previously didn't finish clearing itself out (fsync or fflush or something it's called). By restating your phone and avoiding connection to your PC (which'll trigger MTP and cause more reads) you'll avoid this error.
Thanks allot for reading, this is based on my previous knowledge of flashing firmware unto Nexii and I'll be happily corrected of I'm wrong; live and learn, right?
Sorry mate but what you're describing is an issue with flashing roms to Nexus devices. This thread tracks verified workarounds for known issues pertaining to the Magisk Beta only.
It's not even about general Magisk issues. So generic issues on flashing roms to specific devices do not belong here. Everything on the list must and will pertain to the beta only.
Nodens said:
Error 1 during installation of v13.0 (96f8efc)
Users who get Error 1 during installation of v13.0 (96f8efc), specifically those who get the following error in the recovery log:
Code:
ioctl LOOP_SET_FD failed: Device or resource busy
@jenslody has made a modified version of (96f8efc) that fixes the problem for many users. LINK HERE. This version uses an older updater-binary script that correctly identifies non-64-bit paths to install Magisk (afaik).
The .zip package has been updated and now also includes the fix for very slow installation on some devices (described below).
Click to expand...
Click to collapse
That error is because is not used busybox to mount the loop device. The toolbox one gives that busy error.. and that is due to the built-in busybox path is the last in the PATH var of the updater-binary script.
Deic said:
That error is because is not used busybox to mount the loop device. The toolbox one gives that busy error.. and that is due to the built-in busybox path is the last in the PATH var of the updater-binary script.
Click to expand...
Click to collapse
Ok this makes sense. So
Code:
export PATH=$BUSYBOX:/system/bin:/system/xbin
should fix it.
Is there any reason why busybox variable should not be first in the path? Comment instructs to prefer system binary in bin instead of bundled busybox.
EDIT: Attaching here modded .zip so I can link it to the OP.
_litz said:
I'll also add this for MagiskHide failing to start ....
Check your Magisk log for the following error:
bind_mount: /dev/magisk/mirror/system/xbin/dexlist -> /system/xbin/dexlist
* Running module post-fs-data scripts
resetprop: prop [persist.magisk.hide] does not exist
** late_start service mode running
* Running service.d scripts
If you see this, the installer failed to setup default props on your device. You can verify this by issuing the "getprops" command from an ADB shell, and looking specifically for :
persist.magisk.hide
persist.magisk.root
They should be missing. You can add them with the following commands, then rebooting :
RESETPROP persist.magisk.hide 1
RESETPROP persist.magisk.root 3
After reboot, you should see the following indicating MagiskHide correctly loads:
* Running module post-fs-data scripts
resetprop: getprop [persist.magisk.hide]: [1]
* Starting MagiskHide
hide_pre_proc: Hiding sensitive props
resetprop: getprop [ro.debuggable]: [0]
resetprop: getprop [ro.secure]: [1]
hide_list: initialize...
hide_list add: [com.google.android.gms.unstable]
IMPORTANT! : if MagiskHide does not start, SafetyNet will never pass!
Click to expand...
Click to collapse
That's one of the issues @topjohnwu asks for help with in the beta thread. Could you maybe provide him with some logs for that one? Instructions as to which logs are in the OP of the beta thread.
Thanks for making this thread and the credit; I did worry about my post being lost to the ether and making a thread never crossed my mind! But credit where it's due - all the other great users in these threads. All of these answers are buried in those 100+ pages somewhere. Enough OT though...
One user here had an issue with the Magisk Manager FCing after successfully flashing the Magisk beta. I recall seeing somewhere something about extracting the apk and installing it manually. This worked for me. Perhaps it can be added to the list of possible fixes?
Nodens said:
Ok this makes sense. So
Code:
export PATH=$BUSYBOX:/system/bin:/system/xbin
should fix it.
Is there any reason why busybox variable should not be first in the path? Comment instructs to prefer system binary in bin instead of bundled busybox.
EDIT: Attaching here modded .zip so I can link it to the OP.
Click to expand...
Click to collapse
I updated my original post accordingly and linked to yours.
Hello i have a problem installing magisk 13 beta , i dont get error 1 it just dont install, i needed force shutdown i waited 10 min
It stays on constructing evoriment
Device sm-g928f with khongloi 11
Wesley_NL said:
Hello i have a problem installing magisk 13 beta , i dont get error 1 it just dont install, i needed force shutdown i waited 10 min
It stays on constructing evoriment
Device sm-g928f with khongloi 11
Click to expand...
Click to collapse
Did you try the installer from this thread ?
https://forum.xda-developers.com/showpost.php?p=72734887&postcount=15
Phone: Moto Z Play
OS: Lineage OS 14.1
Magisk Version: 14.0
Log:
Code:
--------- beginning of main
I( 444: 444) Magisk v14.0(1400) daemon started
I( 444: 446) ** post-fs mode running
--------- beginning of system
I( 444: 461) ** post-fs-data mode running
I( 444: 461) * Mounting mirrors
I( 444: 461) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system
I( 444: 461) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I( 444: 461) bind_mount: /dev/magisk/mirror/bin
I( 444: 461) * Mounting /data/magisk.img
E( 444: 461) mount /dev/block/loop0->/magisk failed with 13: Permission denied
I( 444: 620) ** late_start service mode running
I( 444: 620) * Running service.d scripts
I( 444: 620) * Running module service scripts
--------- beginning of crash
Selecting an app in Magisk Hide does nothing. It gets unselected when exiting the app or menu and has no effect.
If there is other info that's necessary, don't hesitate to ask.
Known issue with Moto devices (it's stated in the release thread).
Solution:
Custom kernel with a fixed f2fs or you can try to enable Core Only Mode in the Manager settings (note that the Hide list will be reset on a reboot).
Didgeridoohan said:
Known issue with Moto devices (it's stated in the release thread).
Solution:
Custom kernel with a fixed f2fs or you can try to enable Core Only Mode in the Manager settings (note that the Hide list will be reset on a reboot).
Click to expand...
Click to collapse
Core only mode doesn't work either
Anyone have any other ideas? I couldn't find any mention of this in the thread either
I read somewhere that if your Linux kernel is lower than 3.8 it ain't gonna work. Check that.
Cassious said:
I read somewhere that if your Linux kernel is lower than 3.8 it ain't gonna work. Check that.
Click to expand...
Click to collapse
That's true, but I don't think that's the case here. Without actually knowing for sure, I have a feeling the Moto Z Play is new enough to have a supported kernel.
yw3cur said:
Anyone have any other ideas? I couldn't find any mention of this in the thread either
Click to expand...
Click to collapse
Have you tried changing your data partition to ext4?
It is for me ? I'm currently trying to find a way to get my snapchat to work on my s2(that's how I stumbled on to ur post)...I think I might be SOL. Well good luck!
Any updates on this one? I just got a Moto G5 Plus and Magisk Hide is not working for me. Doesn't matter if core-only mode is enabled.
May be try this fix [Magisk v14.0] Universal SafetyNet Fix | Universal Hide [v2 Beta 5]
I don't know if it works for you but you can try
kramer04 said:
May be try this fix [Magisk v14.0] Universal SafetyNet Fix | Universal Hide [v2 Beta 5]
I don't know if it works for you but you can try
Click to expand...
Click to collapse
Thanks I will give this one a try -- sounds promising and will keep my fingers crossed.
Bumping an old thread. Were you able to get blackberry work to run with the new versions of magisk?
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
dknight178 said:
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
Click to expand...
Click to collapse
Hello,
I had the same problem. My device is encrypted and for me the solution has been to install magisk via magiskmanager then sideload again the rom and magisk via adb, set magisk manager and reboot.
Remember the last twrp has problems to decrypt android 8 encryption.
Let us know
dknight178 said:
I'm using stock Note 3 (N9005DXSGBQA1) and followed instructions for magisk manager. I got it rooted but magiskhide does NOT work - NOT SAVING ANY SELECTION.
I tried using "core only" and tried inserting a new hidelist but both failed. I badly need the hidelist feature. How can I make magiskhide work? Thanks
Click to expand...
Click to collapse
Is your kernel the right version to support magisk hide? Need at least 3.8
madbat99 said:
Is your kernel the right version to support magisk hide? Need at least 3.8
Click to expand...
Click to collapse
Hi. Yes my kernel does not support magiskhide
Universal safety net fix is working on note 4 with lineage 14 ROM. Have to use that and manually hide apps in magisk. I did try core only mode use to work on magisk 14 but have to use this fix on magisk 16. Down side is when using the fix u know longer can see su permissions granted and some apps no longer are able to get root access or ask an hr after closing app
XxdeadhatexX said:
Universal safety net fix is working on note 4 with lineage 14 ROM. Have to use that and manually hide apps in magisk. I did try core only mode use to work on magisk 14 but have to use this fix on magisk 16. Down side is when using the fix u know longer can see su permissions granted and some apps no longer are able to get root access or ask an hr after closing app
Click to expand...
Click to collapse
That module is very old and not recommended. Find out why safetynet fails and address that. Likely a device fingerprint issue. There is a module to get the correct fingerprint for your device.
@topjohnwu
Its been long i have been experiencing this same problem since magisk v15 and i am not the one who is getting this issue.
When you flash magisk everything is fine and you get su prompt without any issue.
But if you see after sometime maybe like 10 or15days its not sure it comes random and new app you install yoj never get prompt of su request.
Issue in magisk log is same as others
04-26 07:54:08.656 26879 26879 E Magisk : write failed with 32: Broken pipe
04-26 07:54:23.254 27099 27099 W Magisk : su: request rejected (10240->0)
04-26 07:54:57.742 27473 27473 W Magisk : su: request rejected (10230->0)
04-26 07:55:06.003 27527 27527 E Magisk : write failed with 32: Broken pipe
04-26 07:55:12.932 27541 27541 W Magisk : su: request rejected (10262->0)
04-26 07:55:18.934 27571 27571 W Magisk : su: request rejected (10211->0)
04-26 07:55:26.091 27612 27612 W Magisk : su: request rejected (10217->0)
04-26 07:55:26.093 27613 27613 W Magisk : su: request rejected (10217->0)
04-26 07:58:20.432 27670 27670 W Magisk : su: request rejected (10211->0)
Click to expand...
Click to collapse
that 10412 is random number maybe uid
But saved su request apps keeps working as fine they can execute su commands which are saved in magisk manager but new apps never get the prompt.
So i think this issue is somewhat related to magisk manager app which doesnot repond, even though i have made sure magisk manager is in my recent app not killed still no prompts.
Now i am fed up with this so posted this issue.
The only thing which works for me i have taken data backup of magisk manager and restore it so my apps stays working fine.
Temp fix whivh always work for me is i have tk flash system image in twrp backup restore and then after sometime after reboot magisk shows prompt, dont know whats this.
My devices are s7 and s9+ exynos same issue on both since v15 i started using magisk.
Full logs attached.
I think I faced the same issue (or at least something similar) two or three times, I will try to get some logs for the next time.
This needs to be analyzed properly every user gets this but we ignore wven for me it is not working even after jninstalling and installing magisk
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Didgeridoohan said:
Every user is not experience this... As an example, I've never seen it. But, that doesn't mean that there isn't an issue, of course.
You're completely correct that it would need further analysis to know what's going on with your device. To me it sounds like your system is killing of the Magisk daemon (or something similar).
Your mention that you have to reflash the system to get things working, but that sounds a bit drastic. What else have you tried? Have you tried simply force closing the Magisk Manager, etc?
And of course, if you're really serious about analysing things you'll have to grab logs showing exactly what's going on.
Click to expand...
Click to collapse
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
BytesReverser said:
hi this issue has been reported many times in this magisk sections you can search and find this,even google search can brings many issues like this.
i dont know what fixes the issue cus nothing works, but flashing system and starting then popup doesnot come immediately it takes time to come even when you ran app 5mins back then back to normal
full magisk logs attached
Click to expand...
Click to collapse
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Didgeridoohan said:
I've seen reports of it, yes, but it's far from a universal issue. The main problem is that the required details for any kind of "fix" generally is missing from the reports (just a plain Magisk log is usually inadequate).
My guess is that it's likely caused by to aggressive OEM implementations of battery optimisation or the likes thereof.
Click to expand...
Click to collapse
I have already added magisk manager to unoptimized apps in battery, dont know what is wrong only @topjohnwu can help.
Right now i didnot flashed system because i want to figure jt out whh this is happening, i can test if topjohnwu guides what he needs
hope topjohnwu will fix it soon
I managed to get it work again. Sharing what i did in sequence:
1. Delete all module in magisk. Trash can icon. Reboot.
2. In magisk manager, uninstall > clear images. Reboot.
3. In magisk manager, uninstall > complete uninstall. Reboot automatically.
4. Reboot to recovery. Flash magisk uninstaller .zip. clear dalvik/cache. Reboot to system.
5. Install magisk manager apk. Reboot.
6. Reboot to recovery. Flash magisk 19.1 zip. Clear dalvik/cache. Reboot to system.
Try su at terminal trigger magisksu prompt after step 6.
Hope this helps.
I have a blu dash l 4.4.2 with twrp and I'm also facing this or similiar issue with su request rejected in log, permission denied in terminal, modules flash but magiskhide and superuser do not. I have tried many things with no luck.
No display over other apps, battery, or any other permission settings included. Only 20.4 flashes on my devices others say unsupported image format. 7.1.1 magisk manager seems to be only one which says additional update but then goes to setup failed. Magisk app settings others ok, tried toggling root access, canary settings crash. Have tried to copy and chmod rw 600 to libdirect file from another device to vendor and lib folders because my device does not appear to have it included. Minimal adb fastboot module tip no luck as well as reflashing stock.
Would like to try to add "(sleep) 1 to early_mount " as I read somewhere but not sure how exactly. No luck yet manually updating magisk.db but I am hoping there is someway to have it fully functioning automatically somehow. Any help much appreciated
i have the same issue ,i was rooting my huawei with magisk ..
To resolve this you need to go to magisk manager press install (the first one) ,recovery mode (if needed) and then direct install ,this worked for me
Hi,
I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.
Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.
There is clearly something wrong with the installation of Magish.apk, but what?
So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.
Help would be very much appreciated.
thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DiracDeBroglie said:
Hi,
I installed Magisk.zip v23 into the system through TWRP, and Magisk.apk v23, on my Samsung Galaxy J5 (2016) Nougat 7.1.1
The phone is clearly rooted as some of the tested apps request root, which I gave.
I noticed that something is not quite alright when I open the Magisk app (see attached image)
In the image, the second part is about the App and shows the latest verion 23.0, so that looks OK.
The first part shows the value of the settings A/B, SAR, Ramdisk and the Installed version (=N/A) .
The setting Installed should show the Magisk version 23.0 instead of N/A, and that is clearly wrong.
Also, clicking the settings cogwheel (top/right) should show a long list of settings, including MagiskHide.
However, that is not the case and the options are just a few.
There is clearly something wrong with the installation of Magish.apk, but what?
So, how can that be fixed?
How do I get back all the missing settings, including MagiskHide.
Help would be very much appreciated.
thanks
View attachment 5416439
Click to expand...
Click to collapse
Search for kdragon safety net fix
John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.
@DiracDeBroglie since your Magisk app doesn't recognise that you have Magisk installed, none of the options you're mentioning will be available.
First thing I would check is if the Magisk app is installed to the internal storage. If it isn't, things won't work correctly.
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Revolver said:
John Wu, the main contributor to Magisk, now works for Google in their Android Platform Security department. So now his job is to prevent MagiskHide to work, and now it seems he removed it from Magisk.
Click to expand...
Click to collapse
But that will have no effect on Magisk v23, that the OP is talking about. And, if you take a quick peek on GitHub and the commits over the past month (or follow the conversations in the general Magisk thread) you'll see that MagiskHide still exists, but in the new form of the deny list. Exactly how that'll work will have to wait until John releases the next Canary.
toolhas4degrees said:
Search for kdragon safety net fix
Click to expand...
Click to collapse
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.
Didgeridoohan said:
OP has a device from 2016. I very much doubt that it uses hardware backed key attestation... Besides, that has nothing to do with the described issue.
Click to expand...
Click to collapse
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
toolhas4degrees said:
Actually it does be the new zip I told him to get ere3nables magisk hide and repo....
Click to expand...
Click to collapse
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...
And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
Thanks for the reply.
I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.
Then I installed Magisk.zip again through TWRP, and that went well too.
Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.
But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.
My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.
The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.
Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).
So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?
If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.
Any suggestions ....
Didgeridoohan said:
The latest release of USNF (currently v2.1.1) adds back a few of the props that MagiskHide currently changes, apart from disabling hardwarebacked key attestation. That is not relevant for the OP, since Magisk v23 still has all of that. The issue here is something else...
And it sounds like you're talking about the unofficial Alpha Magisk releases rather than the SafetyNet Fix, since the latter doesn't include anything that has to do with the soon to be removed modules repo.
Click to expand...
Click to collapse
DiracDeBroglie said:
Thanks for the reply.
I unstalled Magisk with uninstall.zip. That worked fine, rootchecker said that root was gone and banking and ID apps were working again.
Then I installed Magisk.zip again through TWRP, and that went well too.
Following reboot there was some sort of little Magisk app in the app folder (see first image). I double clicked it and it installed the full version of Magisk app (13MB), also that went well.
But the problem persists as before with Magisk app, that is: Installed=N/A and the important Settings, like Magiskhide and the Modules part, are missing, which means btw that Universal SafetyNet Fix cannot be installed anyhow.
My device is from 2016 (design 2015), so I have very strong doubts my device supports any hardware-backed attestation.
The Magisk core elements work flawlessly, Root Checker shows root, root apps like VPN hotspot work fine, and the banking and ID apps .... well, they detected root and refuse to continue working. So root is clearly OK.
Somehow the Magisk app in the user/data partition does not/cannot communicate with the Magisk core elements (sitting in the boot ramdisk I presume).
So, is there any app, tool or software to analyze, study or have a closer look at the communication between the app and the core elements?
If this doesn't work out with v23, then I won't have much of a choice but to install lower versions, v22, v21, ... until I come across a version that works, but that is really my last resort as my preference is v23.
Any suggestions ....
Click to expand...
Click to collapse
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...
Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
@toolhas4degrees I'm not sure what you mean by that screenshot, but it just shows exactly the same thing I was talking about in the post you quoted.
Didgeridoohan said:
Did you check if the app has been installed to external/adoptable storage? That would cause this exact behaviour...
Also, did you previously have Magisk installed with the app repackaged with a random name? If so, that app might still be present and could be the source of your problem. If so, you can uninstall that app and try again (but you might also have to uninstall and reinstall the regular Magisk app as well).
https://www.didgeridoohan.com/magisk/Magisk#hn_There_are_two_Magisk_apps
Click to expand...
Click to collapse
No, at the last install there was not any external SD card present.
No, never installed Magisk under any another name, neither did I try to hide it or so.
However, ... I did install the app Magisk.apk first a few days ago at first contact with Magisk, and then later I installed Magisk.zip through TWRP while there was an external SD present. So, .... maybe there is some remnant code laying around in the system.
I could uninstall.zip Magisk again and then look for remnants in the system and delete those. If there are any remnant left, those should probably have "magisk" in their name. Do you have any idea where to look for Magisk remnants after uninstallation?
Remember the device is a Samsung Galaxy J5 (2016) and I am not all too sure if Odin is really the most handy tool to look for code remnants. I got ADB and Fastboot installed that I used before for testing my Asus tablets. Also Terminal in TWRP I can use. If I only knew what exactly and where to look for the stuff ....
Here is an update.
As my device is still rooted by Magisk I checked out the filesystem starting from root with Solid Explorer File Manager (SE).
I found folders and files from Magisk in /root/data/adb/magisk (folder), /root/data/adb/modules (empty folder) and the file /root/data/adb/magisk.db
I uninstalled Magisk by installing uninstall.zip (from Magisk.zip) through TWRP.
And as SE needs root, I installed SuperSU-v2.82-SR5.zip through TWRP, which then worked fine.
With SE I removed magisk.db and any magisk folder at /root/data/adb/
Next thing I did was to remove, uninstall and unroot SuperSU through its own settings.
But after having clean-installed Magisk.zip again from TWRP, having installed the Magisk app using the Magisk preinstaller app in the apps folder and rebooting the device a few times, the problem hasn't gone!
And so the Magisk app pane still shows Installed = N/A, and MagiskHide, Modules and the other options are also still missing from Settings.
Any suggestions for a next move would be welcome.
thanks
DiracDeBroglie said:
installed the Magisk app using the Magisk preinstaller app in the apps folder
Click to expand...
Click to collapse
What does this mean? What's a preinstaller?
Didgeridoohan said:
What does this mean? What's a preinstaller?
Click to expand...
Click to collapse
If one performs a clean installation of Magisk.zip -- so there is no Magisk on the phone anywhere -- through TWRP, not only the core elements are installed, but also in the /data part some little Magisk app is installed that shows up in the apps folder, which I call a (pre)installer. See first image #9. Double clicking that will install the full Magisk app in the user or /data part.
So all looks ok during the installation, and rooting definitely works, but that annoying problem just persists.
I would be glad to hear any suggestions...
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.
I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
Didgeridoohan said:
Ah... Now I get it. It sounded like you were using some custom unofficial stuff, and that would definitely have been a possible source of issues.
I have no suggestions, but you haven't posted any Magisk log, have you? Might be a good idea, to see if anything shows up in there. First it would be good if you could install the Canary release though, since it has more verbose logging.
Click to expand...
Click to collapse
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
DiracDeBroglie said:
I just had a look for those log files but couldn't find any. Any idea where to look for? In /root/data/adb/ there are no log files.
Click to expand...
Click to collapse
The Magisk log is in /cache.
Didgeridoohan said:
The Magisk log is in /cache.
Click to expand...
Click to collapse
So this is what I have in the log.
01-05 19:43:01.276 262 262 I : Magisk 23.0(23000) daemon started
01-05 19:43:01.281 262 262 I : * Device API level: 25
01-05 19:43:01.296 262 264 I : ** post-fs-data mode running
01-05 19:43:01.297 262 264 I : * Mounting mirrors
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/system
01-05 19:43:01.298 262 264 I : mount: /sbin/.magisk/mirror/data
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/cache
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/persist
01-05 19:43:01.299 262 264 I : link: /sbin/.magisk/mirror/vendor
01-05 19:43:01.299 262 264 I : * Initializing Magisk environment
01-05 19:43:02.901 262 264 I : * Running post-fs-data.d scripts
01-05 19:43:02.906 262 264 I : * Running module post-fs-data scripts
01-05 19:43:02.906 262 264 I : * Loading modules
01-05 19:43:07.207 262 538 I : ** late_start service mode running
01-05 20:43:07.209 262 538 I : * Running service.d scripts
01-05 20:43:07.227 262 538 I : * Running module service scripts
09-25 19:09:50.969 262 2470 I : ** boot_complete triggered
09-25 19:31:29.395 262 12576 W : su: request rejected (10166)
09-25 19:31:41.551 262 12618 W : su: request rejected (10166)
09-25 19:31:53.716 262 12667 W : su: request rejected (10166)
09-25 19:32:05.877 262 12707 W : su: request rejected (10166)