Magisk General Support / Discussion

Search This thread
By:
Advanced…
blakegriplingph

blakegriplingph

Senior Member
May 13, 2011
1,076
159
Amazon Fire
Realme C3
Any idea on what to do with this? I've got a LeapFrog Epic running on 4.4.2 which I had to sign the patched boot image using the Mediatek sign tool due to secure boot check being implemented on the tablet. Magisk did show up as enabled upon flashing said boot image, but for some reason I get request rejected errors whenever I try to invoke root. SuperSU's already uninstalled prior to installing Magisk, btw.

Code: 
02-20 18:01:56.445   127   127 I Magisk  : * Creating /sbin overlay
02-20 18:01:56.468   129   129 I Magisk  : * Device API level: 19
02-20 18:01:56.468   129   129 I Magisk  : Magisk v18.1(18100) daemon started
02-20 18:01:56.473   129   130 I Magisk  : ** post-fs-data mode running
02-20 18:01:56.473   129   130 I Magisk  : * Initializing Magisk environment
02-20 18:01:56.633   129   130 I Magisk  : * Mounting mirrors
02-20 18:01:56.634   129   130 I Magisk  : mount: /sbin/.magisk/mirror/system
02-20 18:01:56.635   129   130 I Magisk  : link: /sbin/.magisk/mirror/vendor
02-20 18:01:56.635   129   130 I Magisk  : bind_mount: /sbin/.magisk/mirror/bin
02-20 18:01:56.635   129   130 I Magisk  : * Setting up internal busybox
02-20 18:01:56.672   136   136 I Magisk  : Magisk v18.1(18100) logger started
02-20 18:01:56.703   129   130 I Magisk  : * Running post-fs-data.d scripts
02-20 18:01:56.704   129   130 I Magisk  : * Mounting /data/adb/magisk.img
02-20 18:01:56.705   143   143 E Magisk  : execve /system/bin/e2fsck failed with 2: No such file or directory
02-20 18:01:56.841   129   130 I Magisk  : * Running module post-fs-data scripts
02-20 18:01:56.841   129   130 I Magisk  : * Loading modules
02-20 18:01:56.872   129   147 I Magisk  : * Starting MagiskHide
02-20 18:01:56.872   129   147 I Magisk  : hide_utils: Hiding sensitive props
02-20 18:01:56.873   129   147 I Magisk  : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:56.895   129   147 E Magisk  : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:01:57.399   129   286 I Magisk  : ** late_start service mode running
02-20 18:01:57.400   129   286 I Magisk  : * Running service.d scripts
02-20 18:01:57.409   129   286 I Magisk  : * Running module service scripts
02-20 18:01:57.560   129   287 I Magisk  : * Starting MagiskHide
02-20 18:01:57.560   129   287 I Magisk  : hide_utils: Hiding sensitive props
02-20 18:01:57.561   129   287 I Magisk  : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:57.592   129   287 E Magisk  : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:03:59.521  4167  4167 W Magisk  : su: request rejected (10127->0)
02-20 18:04:20.310  4194  4194 W Magisk  : su: request rejected (10101->0)
02-20 18:04:52.495  4380  4380 E Magisk  : write failed with 32: Broken pipe
02-20 18:05:20.441  4677  4677 W Magisk  : su: request rejected (10101->0)
02-20 18:08:59.777  5210  5210 E Magisk  : write failed with 32: Broken pipe
 
K

KaXaSA

New member
May 26, 2016
4
0
demonoidmaster said:
In 18.1, but then again it could either be that specific kitkat rom made for his phone that could be the problem or the phone itself, he would have to find out what target partition his device has and do the magisk patched boot img manually since the installer cant
Click to expand...
Click to collapse

I downloaded both the kitkat¹ and what I assume it's the lolipop² rom ("Android L"):

¹ https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.22.40.540-user.zip
² https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-3.24.40.87-user.zip

The second one when I tried to 'patch boot image' (Magisk Manager) gave me a different log:

Code: 
- Copying image to cache
- Device platform: x86
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.029 secs (36673379 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER      [0]
KERNEL_SZ       [1464750080]
RAMDISK_SZ      [1702126437]
SECOND_SZ       [1679840844]
EXTRA_SZ        [174351732]
RECOV_DTBO_SZ   [0]
PAGESIZE        [1702126437]
NAME            [d
]
CMDLINE         [b Version: 1.4 ...
e820 table
]
CHECKSUM        [6f756e640a]
Segmentation fault 
- Checking ramdisk status
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
- Stock boot image detected
- Backing up stock boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Compressing to [stock_boot_0f88936f61def2f10d692ac0beecd3a532e9e0f5.img.gz]
- Patching ramdisk
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Segmentation fault 
- Repacking boot image
MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/data/com.topjohnwu.magisk/install/boot.img]
PXA_BOOT_HDR
HEADER_VER      [0]
KERNEL_SZ       [1464750080]
RAMDISK_SZ      [1702126437]
SECOND_SZ       [1679840844]
EXTRA_SZ        [174351732]
RECOV_DTBO_SZ   [0]
PAGESIZE        [1702126437]
NAME            [d
]
CMDLINE         [b Version: 1.4 ...
e820 table
]
CHECKSUM        [6f756e640a]
Segmentation fault 
! Unable to repack boot image!
! Installation failed

So the first one (kitkat) failed to unpack and this one (lolipop) failed trying to repack the boot image. :confused:

Should I even try to flash the lolipop rom to see if Magisk works or based on this log it would be completely pointless?
 
D

demonoidmaster

Senior Member
Nov 19, 2015
1,035
331
KaXaSA said:
I downloaded both the kitkat¹ and what I assume it's the lolipop² rom ("Android L"):

¹ https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.22.40.540-user.zip
² https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-3.24.40.87-user.zip

The second one when I tried to 'patch boot image' (Magisk Manager) gave me a different log:



So the first one (kitkat) failed to unpack and this one (lolipop) failed trying to repack the boot image. :confused:

Should I even try to flash the lolipop rom to see if Magisk works or based on this log it would be completely pointless?
Click to expand...
Click to collapse
Don't know, you should forward that log to someone who knows a bit more about manual boot patching or wait and see if someone replies

But tbh it might just be those roms Asus provides, try patching a boot img from a custom rom for your device (assuming said rom is newer and still being updated), it can be any one.. Just for a test
 
  • Like
Reactions: KaXaSA
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
parag60288 said:
Can any third party app be responsible for triggering safetynet?
My device fails on basic integrity as well as ctsProfile.
Screenshots of magisk as well as list of apps installed.

My device showed safetynet passed for a day. But now it is showing as failed.
Usb debugging is also disabled.
Click to expand...
Click to collapse

Yes, third party apps can definitely be responsible for triggering SafetyNet. But, based on the apps you have and your description of the problem, I don't think that's the issue. Since you did pass SN initially, you're likely experiencing the intermittent failure of MagiskHide bug in Magisk v18.0 and v18.1.

In the current Canary releases (currently 18108), MagiskHide has been completely rewritten and this bug should be gone. You could either try the Canary builds (be warned, they may be buggy, make sure to have a backup) or wait for the next stable release.

blakegriplingph said:
Any idea on what to do with this? I've got a LeapFrog Epic running on 4.4.2 which I had to sign the patched boot image using the Mediatek sign tool due to secure boot check being implemented on the tablet. Magisk did show up as enabled upon flashing said boot image, but for some reason I get request rejected errors whenever I try to invoke root. SuperSU's already uninstalled prior to installing Magisk, btw.
Click to expand...
Click to collapse

If the requests are rejected, are there entries for the app(s) in the Superuser menu in the Manager (that you could toggle to enabled)? KitKat support is in its infancy, and Mediatek devices are often troublesome, so it can be used to say what the actual issue is. A logcat when a Superuser request is rejected might show something...

KaXaSA said:
I downloaded both the kitkat¹ and what I assume it's the lolipop² rom ("Android L"):

¹ https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.22.40.540-user.zip
² https://dlcdnets.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-3.24.40.87-user.zip

The second one when I tried to 'patch boot image' (Magisk Manager) gave me a different log:

So the first one (kitkat) failed to unpack and this one (lolipop) failed trying to repack the boot image. :confused:

Should I even try to flash the lolipop rom to see if Magisk works or based on this log it would be completely pointless?
Click to expand...
Click to collapse

Based on that log you will not be able to install Magisk on the Lollipop ROM either. It looks like Magisk can't handle Asus' boot image compression (or something similar). Wouldn't be the first time Asus does weird things...

You could upload that patching image log together with the boot image to a GitHub issue (with a detailed description of the problem) for possible future compatibility. Just remember that it might not be high in the priority list.

If you're lucky, some of the recent tweaks that haven't been released yet could fix the problem, but it's far from certain.
 
  • Like
Reactions: ipdev, KaXaSA, parag60288 and 1 other person
blakegriplingph

blakegriplingph

Senior Member
May 13, 2011
1,076
159
Amazon Fire
Realme C3
Didgeridoohan said:
If the requests are rejected, are there entries for the app(s) in the Superuser menu in the Manager (that you could toggle to enabled)? KitKat support is in its infancy, and Mediatek devices are often troublesome, so it can be used to say what the actual issue is. A logcat when a Superuser request is rejected might show something...
Click to expand...
Click to collapse
The app list on the Superuser menu doesn't show anything, unfortunately. All what I can tell so far is that whenever I try to invoke root in terminal, the terminal simply stalls without any error messages.
 
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
blakegriplingph said:
The app list on the Superuser menu doesn't show anything, unfortunately. All what I can tell so far is that whenever I try to invoke root in terminal, the terminal simply stalls without any error messages.
Click to expand...
Click to collapse

And, just to make sure, the option for Superuser access is set to "Apps and ADB", the Manager is installed to internal storage, and the SuperSU app is uninstalled?
 
  • Like
Reactions: blakegriplingph
M

Mr.A9323

Senior Member
Dec 1, 2015
65
27
Xiaomi Poco X2
Dev please help, I'm on Havoc os, pie ( redmi 3s prime) no matter what rom I try, once I install any magisk module, safetynet breaks, please suggest any fix, I have tried many other roms available for my device but the problem persist.
:(
 
Didgeridoohan

Didgeridoohan

Retired Senior Moderator
May 31, 2012
12,300
1
14,850
Gone
Google Nexus 4
Nexus 6
V

Valeryan24

Member
Feb 12, 2019
12
6
Didgeridoohan said:
Probably. The last factory image for the 6P had security patch 2018-12-05, so the fingerprint from that won't work with any other patch date. You could use my MagiskHide Props Config module and set a custom prop for ro.build.version.security_patch to 2018-12-05.
Click to expand...
Click to collapse

Hi, thanks a lot !

So I ran "su props" in Termux, then "ro.build.version.security_patch 2018-12-05" and rebooted smartphone, security patch date well changed to 2018-12-05 and finally Safetynet ctsProfile test in Magisk was successful !

No I learned what to do in case of LineageOS update.

I still have PokemonGo and Ingress (just with root, no spoofing nor GPS app) which fail and refuse to run, but I'll post in the dedicated topic.
 
Last edited:
  • Like
Reactions: Didgeridoohan
Z

Zico 10

Senior Member
Feb 27, 2010
251
81
HTC Sensation
Google Nexus 5
Zico 10 said:
Hoping someone can assist, I've tried searching the thread but didn't find what I was looking for.

I was running Magisk 16.7 with Magisk Manager 5.9 without issues, but as soon as I update either to anything newer, on the next reboot my network (LTE, 4G, 3G) is completely disabled and I can't enable it.

If I remove Magisk and reboot, it works again.

I disable and remove all modules prior to updating and it still happens.
Click to expand...
Click to collapse
No one?

Device is a HTC U11, and this is extremely frustrating
 
doomscooter

doomscooter

Senior Member
Feb 1, 2009
610
188
Jakarta - Dumai
Xiaomi Poco F3

Attachments

  • Screenshot_20190221-192030.jpg
    Screenshot_20190221-192030.jpg
    204.3 KB · Views: 714
RandomPooka

RandomPooka

Senior Member
Oct 14, 2010
4,055
2,525
Kent, OH
OnePlus 8
Zico 10 said:
No one?

Device is a HTC U11, and this is extremely frustrating
Click to expand...
Click to collapse

I had zero issues using Magisk 18.1 and Manager 7.0.0 on my HTC U11 (Sprint variant) on stock Oreo for nearly 2 weeks. I've since switched to LineageOS, and still not having any problems with signal. Have you tried it on a clean install/RUU? Or by flashing the uninstaller in recovery, making sure the manager app was deleted entirely from your previous magisk setup, and then flashing 18.1 and installing the 7.0.0 manager after rebooting to system?
 
  • Like
Reactions: Zico 10
C

CritPlusPlus

New member
Feb 21, 2019
1
0
Magisk Hide Problems (OnePlus 6T, v 18.1)

Hi guys, loving Magisk so far. I am using Magisk Hide to hide root from a company provided app. It works when I toggle it on, but after a random amount of time (sometimes within a few hours, sometimes not until the next day), the app will detect it again. I can toggle Magisk Hide in the settings (as a whole) to get it to work again immediately. I know its not just the company app because it affects Google Pay too (these are the only two apps I use that don't want root). Any ideas on a fix for this?

Using a OnePlus 6T, stock ROM, with Magisk v 18.1.
 
habylab

habylab

Senior Member
Dec 3, 2010
6,228
1,200
CritPlusPlus said:
Hi guys, loving Magisk so far. I am using Magisk Hide to hide root from a company provided app. It works when I toggle it on, but after a random amount of time (sometimes within a few hours, sometimes not until the next day), the app will detect it again. I can toggle Magisk Hide in the settings (as a whole) to get it to work again immediately. I know its not just the company app because it affects Google Pay too (these are the only two apps I use that don't want root). Any ideas on a fix for this?

Using a OnePlus 6T, stock ROM, with Magisk v 18.1.
Click to expand...
Click to collapse
Latest Canary works, use that if you wish.
 
  • Like
Reactions: kotuamoalt
blakegriplingph

blakegriplingph

Senior Member
May 13, 2011
1,076
159
Amazon Fire
Realme C3
Didgeridoohan said:
Logs it is then...
https://didgeridoohan.com/magisk/MagiskHideHelp
Click to expand...
Click to collapse

I have this if it helps:
Code: 
02-20 18:01:56.445   127   127 I Magisk  : * Creating /sbin overlay
02-20 18:01:56.468   129   129 I Magisk  : * Device API level: 19
02-20 18:01:56.468   129   129 I Magisk  : Magisk v18.1(18100) daemon started
02-20 18:01:56.473   129   130 I Magisk  : ** post-fs-data mode running
02-20 18:01:56.473   129   130 I Magisk  : * Initializing Magisk environment
02-20 18:01:56.633   129   130 I Magisk  : * Mounting mirrors
02-20 18:01:56.634   129   130 I Magisk  : mount: /sbin/.magisk/mirror/system
02-20 18:01:56.635   129   130 I Magisk  : link: /sbin/.magisk/mirror/vendor
02-20 18:01:56.635   129   130 I Magisk  : bind_mount: /sbin/.magisk/mirror/bin
02-20 18:01:56.635   129   130 I Magisk  : * Setting up internal busybox
02-20 18:01:56.672   136   136 I Magisk  : Magisk v18.1(18100) logger started
02-20 18:01:56.703   129   130 I Magisk  : * Running post-fs-data.d scripts
02-20 18:01:56.704   129   130 I Magisk  : * Mounting /data/adb/magisk.img
02-20 18:01:56.705   143   143 E Magisk  : execve /system/bin/e2fsck failed with 2: No such file or directory
02-20 18:01:56.841   129   130 I Magisk  : * Running module post-fs-data scripts
02-20 18:01:56.841   129   130 I Magisk  : * Loading modules
02-20 18:01:56.872   129   147 I Magisk  : * Starting MagiskHide
02-20 18:01:56.872   129   147 I Magisk  : hide_utils: Hiding sensitive props
02-20 18:01:56.873   129   147 I Magisk  : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:56.895   129   147 E Magisk  : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:01:57.399   129   286 I Magisk  : ** late_start service mode running
02-20 18:01:57.400   129   286 I Magisk  : * Running service.d scripts
02-20 18:01:57.409   129   286 I Magisk  : * Running module service scripts
02-20 18:01:57.560   129   287 I Magisk  : * Starting MagiskHide
02-20 18:01:57.560   129   287 I Magisk  : hide_utils: Hiding sensitive props
02-20 18:01:57.561   129   287 I Magisk  : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-20 18:01:57.592   129   287 E Magisk  : proc_monitor: Your kernel doesn't support mount namespace :(
02-20 18:03:59.521  4167  4167 W Magisk  : su: request rejected (10127->0)
02-20 18:04:20.310  4194  4194 W Magisk  : su: request rejected (10101->0)
02-20 18:04:52.495  4380  4380 E Magisk  : write failed with 32: Broken pipe
02-20 18:05:20.441  4677  4677 W Magisk  : su: request rejected (10101->0)
02-20 18:08:59.777  5210  5210 E Magisk  : write failed with 32: Broken pipe
Do I need more than just the logs above?
 
D

demonoidmaster

Senior Member
Nov 19, 2015
1,035
331
Didgeridoohan said:
Based on that log you will not be able to install Magisk on the Lollipop ROM either. It looks like Magisk can't handle Asus' boot image compression (or something similar). Wouldn't be the first time Asus does weird things...

You could upload that patching image log together with the boot image to a GitHub issue (with a detailed description of the problem) for possible future compatibility. Just remember that it might not be high in the priority list.

If you're lucky, some of the recent tweaks that haven't been released yet could fix the problem, but it's far from certain.
Click to expand...
Click to collapse

His best bet tbh would be to use a custom rom (assuming his device is still getting life in the XDA forums) and then try magisk again.. if not he'd need a new phone
 
You must log in or register to reply here.

Similar threads

T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
T
  • Locked
[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
Replies
7K
Views
3M
T
topjohnwu
Heisenberg
[Discussion] PokeMon Go Magisk Discussion Thread
Replies
5K
Views
649K
beneditodragon
beneditodragon
Didgeridoohan
[Discussion] Google Pay Magisk Discussion Thread
Replies
3K
Views
572K
I
ihavenolifee
yochananmarqos
Collection of Magisk Modules v2
Replies
1K
Views
1M
あなたの
あなたの

Top Liked Posts

24 Hours 30 Days All time
  • 1
    D
    dronkit
    UPDATE: I got it to work by extracting and flashing the stock boot.img and recovery.img via odin. I guess that's a dirty fix and IDK why this worked and flashing the whole stock rom didn't
    J.Michael said:
    If you flashed a stock ROM, you effectively uninstalled Magisk, except for the /data/adb directory.
    Click to expand...
    Click to collapse
    Ii'll check that folder (if I can install TWRP or something) in order to clean up, but my goal now is to reroot it.
    J.Michael said:
    Did the flashing of the stock ROM involve doing a "factory reset / wipe data"?
    Click to expand...
    Click to collapse
    No, but, I did one factory reset from Android's configuration menu in order to clean up, set up the phone and debloat it (I bought it used). It worked afterwards but I screwed up when debloating so then I did the stock rom flash.
    J.Michael said:
    If you have a problem after trying to reinstall Magisk, the things to check are:
    • did you patch and flash the right file?
    • did you change the version of Magisk?
    • did you change the version of Android?
    Click to expand...
    Click to collapse
    I'll keep that in mind when I try to reroot.
    Thanks for your response!
    View
    1
    P
    pndwal
    dronkit said:
    UPDATE: I got it to work by extracting and flashing the stock boot.img and recovery.img via odin. I guess that's a dirty fix and IDK why this worked and flashing the whole stock rom didn't
    Click to expand...
    Click to collapse
    Keep in mind that official instructions still state:

    Important Notes​

    • Never, ever try to restore either boot, init_boot, recovery, or vbmeta partitions back to stock! You can brick your device by doing so, and the only way to recover from this is to do a full Odin restore with data wipe.
    • To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always patch AP in the Magisk app and use that instead.
    Click to expand...
    Click to collapse
    although I know many Sammy users have been able to recover from this mistake without wiping data... Seems you've put your finger on the working method for your device... Not sure if trick would work for any Samsung device however, but may be useful for others...

    Take care with upgrades in future! 😉

    dronkit said:
    Ii'll check that folder (if I can install TWRP or something) in order to clean up, but my goal now is to reroot it.
    Click to expand...
    Click to collapse
    If goal is to reroot, you can leave configuration as-is... Only modules that become incompatible with later Android versions may cause bootloop, but normally the previous Magisk configuration files are OK... If you want to force a configuration rebuild (restore clean Magisk, no modules, superuser list, DenyList etc) after installation, just delete everything in /data/adb after rooted with a root explorer and reboot; configuration files will then be rebuilt.

    🤠 PW
    View
    1
    J
    J.Michael
    dronkit said:
    UPDATE: I got it to work by extracting and flashing the stock boot.img and recovery.img via odin. I guess that's a dirty fix and IDK why this worked and flashing the whole stock rom didn't

    Ii'll check that folder (if I can install TWRP or something) in order to clean up, but my goal now is to reroot it.

    No, but, I did one factory reset from Android's configuration menu in order to clean up, set up the phone and debloat it (I bought it used). It worked afterwards but I screwed up when debloating so then I did the stock rom flash.

    I'll keep that in mind when I try to reroot.
    Thanks for your response!
    Click to expand...
    Click to collapse
    I think you are confused. (I know I am.)

    You said you flashed the stock ROM. Then you said you patched and flashed, which implies that the device was running after flashing the stock ROM. So you never mentioned trying to recover from the bootloop by flashing the entire stock ROM. I believe it would have worked, you just didn't do it.

    The thing that needed to be fixed was the bootloop after patching and flashing. I listed the first few things that came to mind that would explain why you got a bootloop. Those are the things that you need to be careful of the next time you try to install Magisk.

    If you have never had Magisk installed, you can ignore everything that refers to a previous installation of Magisk. Your bootloop was probably a matter of patching and flashing the boot from a different version of the ROM. Or maybe it was patching the boot image when you need to patch the recovery image.

    When installing Magisk on a Samsung device, you should "patch" the entire AP.tar file. Magisk will patch three images within the tar file (assuming either the Recovery option is selected by default, or you specifically select it). Then you hand the patched AP.tar to Odin and everything in it gets "flashed". After you've gotten it working, if you're a glutton for punishment you can see if you can patch and flash less than the full AP.tar, but I think you still have to give a tar file to Odin.
    View
    1
    P
    pndwal
    J.Michael said:
    I think you are confused. (I know I am.)

    You said you flashed the stock ROM. Then you said you patched and flashed, which implies that the device was running after flashing the stock ROM.
    Click to expand...
    Click to collapse
    My take: Neither worked...

    Flashing stock caused boot to Odin (download) mode with 'red errors' (because something in /data is set to accept patched vbmeta or other)... John W indicates factory reset may be needed to fix this but it ain't always so...

    Next, member patched AP (presumably on another device?), then flashed (with other binaries?) which failed... This was likely because selinux/module rule directory will be wrong in modern Magisk unless patching is done on the same device (with system booted)... It probably would have worked if pre 26.0 Magisk had been used for patching however, then simply Direct install taken to update to latest Magisk, but most users won't know this.

    Finally, extracting and flashing boot.img independently of AP worked as vbmeta (and/or other?) partition is presumably still patched (and needed) for (some?) Samsung devices (it's not for most other devices since major 2SI init refactoring in 25.0 however) and the previous failed patch/flash attempt (w/ Magisk patched AP) presumably achieved that...

    Ie. My best guess is that 1) stock /boot couldn't work with stock /vbmeta without full /data wipe, 2) 26.0+ /boot patched on a different device couldn't work with patched/vbmeta, but the combination of stock /boot and Magisk patched /vbmeta worked as stock /boot uses correct factory set selinux rules directory...

    Good luck or good management, this seems to have saved the day. 😜

    J.Michael said:
    So you never mentioned trying to recover from the bootloop by flashing the entire stock ROM. I believe it would have worked, you just didn't do it.
    Click to expand...
    Click to collapse
    Well, member did that first, no?...
    J.Michael said:
    The thing that needed to be fixed was the bootloop...

    ...Your bootloop was probably a matter of patching and flashing the boot from a different version of the ROM.
    Click to expand...
    Click to collapse
    Don't think so... Said "patched the stock ROM"... I think only patching of current AP / flashing via Odin was attempted(?)

    Initial bootloop (or rather, boot failure/soft brick) was clearly caused by "try(ing) to restore either boot... (without) a full Odin restore with data wipe"...
    J.Michael said:
    Or maybe it was patching the boot image when you need to patch the recovery image.
    Click to expand...
    Click to collapse
    /recovery won't/can't/shouldn't be patched on that device as it launched with Android 10 so is 2SI and definitely has ramdisk in /boot (so Recovery mode option wouldn't even show)... However, maybe when patched on another device (as I presumed), if that happened to be an A-only device launched with Android 9 and Recovery mode was selected when patching, recovery.img in AP may have been patched erroneously and that would likely cause issues...
    J.Michael said:
    When installing Magisk on a Samsung device, you should "patch" the entire AP.tar file. Magisk will patch three images within the tar file (assuming either the Recovery option is selected by default, or you specifically select it).
    Click to expand...
    Click to collapse
    Please say which 3... I believe only 2, if not 1(?)...
    J.Michael said:
    Then you hand the patched AP.tar to Odin and everything in it gets "flashed". After you've gotten it working, if you're a glutton for punishment you can see if you can patch and flash less than the full AP.tar, but I think you still have to give a tar file to Odin.
    Click to expand...
    Click to collapse
    Not doing this is apparently what allowed stock boot image to work on Sammy previously hosting Magisk w/o wiping /data however. (Ie. to get patched /vbmeta + stock /boot and /recovery).

    ... But yes, I believe patching AP on another device using pre-26.0 Magisk (or any Magisk if it could have been done on the A12 itself) and flashing all binaries via Odin would probably have worked too.

    🤠 PW
    View
  • 5
    Lughnasadh
    Lughnasadh
    HippoMan said:
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Click to expand...
    Click to collapse
    Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.

    EDIT: Ninja'd 🙃
    View
    4
    zgfg
    zgfg
    Jaitsu said:
    Is the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
    Click to expand...
    Click to collapse
    Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or Debug

    Set your Update Channel to Stable and you will see (just like you can see also on GitHub) that latest Stable is v27000, there was never Stable v27001 or v27002

    Generally, Stable is always Nx100

    So, you cannot downgrade to Stable v27001 but Canary v27001 should be just like Stable v27000 (same codebase). That's also the general policy, whenever Nx100 Stable is released, then immediately comes Canary Nx100 +1, on the same code-base

    Therefore, downgrade to Stable v27000 instead
    View
    4
    P
    pndwal
    forserg said:
    Direct Install with recovery mode checked worked for me. You were right.

    After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
    Click to expand...
    Click to collapse
    Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls! 😬

    Are you flashing patched AP (Application Processor binary) along with all the other package binaries (X4?) for your S10+ (also in Magisk Installation page, Samsung section)??

    CP is Cellular Processor (Nb. Oft repeated references to CP as 'core processor' may be misleading) binary package (also referred to as Baseband Modem) so that should have fixed mismatched baseband etc... correct CSC (Consumer Software Customization; region, APN and carrier specific software packages/settings) and even BL (Bootloader) are most likely also important...

    Nb. BL doesn't always update bootloader version, but if later firmware has been flashed be aware that these can also cause anti-roll back version for bootloader to be incremented (in the event that an update patches serious vulns) so you original firmware may be blocked and you may need to use later packages only...

    If flashing latest complete firmware package via Odin doesn't fix your IMEI / baseband issues it may be that you've messed with partitions that contain unique device values in the past... You may need to ask in Galaxy, S10 or S10+ XDA forums for that. 🤠 PW
    View
    4
    bombadier
    bombadier
    HippoMan said:
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Click to expand...
    Click to collapse
    Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it
    View
    3
    zgfg
    zgfg
    waldmax said:
    Thanks for your reply.
    So I stay for the moment at Magisk 26.4 für my Xiaomi 14 Ultra. Because there is xiaomi.eu ROM for my phone available since 2 hours, I will flash this tomorrow und with the Module from Xiaomi.eu Team I do not need Playintegrity anymore.

    So do I understand correct, to hide root I should use Shamiko? Latest Shamiko can be found here https://github.com/LSPosed/LSPosed.github.io/releases correct?
    Click to expand...
    Click to collapse
    Since Xiaomi eu is a custom ROM, their devs made the injector, 'module' that tricks DroidGuard and injects the spoofs with no need for Magisk/root and Zygisk

    And as that, you achieve Device Integrity without the Magisk.
    But if you install Magisk, you have to hide Magisk and Zygisk by your own

    So yes, you can use Shamiko and it should work (I used that kind of setup at the beginning of this year, for like two weeks, with no problems)

    But then ask yourselves - what for do you need Magisk. If using like Viper4Android, useful LSPosed modules - then, yes

    If not, better uninstall Magisk and you will only have Xiaomi.eu injector. Btw, yes, it is rather injector than a module, it's full name is XiaomiEUInject

    Regarding the prints - there are now no more publicly available working prints, hence a vast majority of rooted users use the prints 'stolen' from the Xiaomi.eu injector. When Google bans them, both sides will be equally affected. And assuming that Xiaomi.eu team quickly publishes their new version of injector, (last time it was in a matter of hours) with the new prints, all those rooted users will jump again to their new prints from tha new injector (new version of PIF was published less than an hour upon the Xiaomi.eu injecto was updated)

    But if Google makes a slaughter like last time (now there are about 20 times less working prints than previously) and if Xiaomi.eu team does not come up (quickly) with the new injector (and the new working prints), than better don't think what could happen.
    Btw, Wallet can run about half a day on the cached previous Play Integrity pass

    Hence, with the Xiaomi.eu injector or with PI Fix (with its built-in prints), PI Fork with the corresponding autopif script, etc, you are equally exposed to the Google's mercy

    Therefore, if you really need Magisk, you can also keep using the PI Fix/For with the disabled Xiaomi.eu injector. It will be easier for your maintenance than to struggle with both worlds in parallel (although, that can work as well)
    View
  • 1103
    T
    topjohnwu
    This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
    All information, including troubleshoot guides and notes, are in the Announcement Thread
    View
    156
    T
    topjohnwu
    Hello, I haven't given much support on XDA lately. It can be resulted from
    • University started and I have limited free time. In fact, I mostly develop during midnight
    • I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
    • The new version is about to come, I don't want to spend effort on supporting old releases
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    New Forum!
    As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
    **For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
    It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about :D

    The Pixel Phone
    Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things ;)

    Current Progress
    In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
    To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
    After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)

    Safety Net Disaster
    Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
    However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
    I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.

    Conclusion
    Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.

    Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!
    View
    121
    Chainfire
    Chainfire
    Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.

    First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.

    -------------------------

    What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!

    Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).

    He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.

    It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
    @topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.

    tl;dr Towards @topjohnwu, I have:
    - expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
    - expressed surprise he is using SuperSU binaries in a competing superuser without permission
    - expressed surprise he is posting a modified LiveBoot without permission
    - informed him of issues with the modified SuperSU he has posted
    - let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser

    To be crystal clear:
    - I have not asked for an apology
    - I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
    - I have not made an issue of any of this anywhere, until this post
    - I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
    - I have not reported this thread to XDA moderators for copyright violations or otherwise

    While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.

    To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.

    I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake :)

    Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.
    View
    76
    nathanchance
    nathanchance
    Thread temporarily closed so everyone sees this.

    The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.

    The Flash
    Forum Moderator

    EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.
    View
    75
    T
    topjohnwu
    Hello everyone!

    I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.

    Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.

    So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.

    Google, how will a few systemless mods do any harm :p:p
    View

New posts