yashsingh1/xdaforums huggingface dataset:
[Magisk] 5m4r7ph0n36uru:
Never mind. My mistake.
[Magisk] MystaMagoo:
It was very late last night I decided to take supersu out of a rom and insert magisk 16.7.

Basically to hide my sons oralb app so he could use it.

Magisk hide seems to work,oral b app now works and a roor checker app confirms root hidden.

Safetynet totally fails though.

Tried a couple of suggested fixes but no joy.

After work today I can get logs etc was too late last night.

Rom is pre-rooted but after flashing 16.7 philz touch says root not active,re-root yes or no,I choose no.

I deleted su from rom so that does not get installed.

Phone is a note 3 so that may be the problem but search brings up nothing to confirm/deny.

Is it common for hide to work but safeyynet fails on both?
[Magisk] Didgeridoohan:
Ha! Thank you for being observant. My fingers went full auto when I typed that out...

I've edited my original post in case someone stumbles across it.
[Magisk] m0h1t:
Magisk 16.7 beta working just fine on Android P August release
[Magisk] Itachisasuke:
I can confirm this as well using the Magisk-v16.7-1674-.zip on my Pixel 2 XL. The only issue I am currently seeing is that when I check "Preserve Force Encryption" in the Magisk Manager and close the app and reopen it. It goes back to being unchecked. Just a minor annoyance but everything else is working as intended.
[Magisk] arsenal3010:
Zenfone 5.

OK I will try to run adb shell mount -o remount,rw /system. Is it 1 command or 2 commands ?
[Magisk] Äptiva:
1 command.

adb shell mount -o remount,rw /system
[Magisk] arsenal3010:
C:\Users\HUONG\Desktop\ADB Fastboot Tool>adb shell mount -o remount,rw /system

mount: can't find /system in /proc/mounts

cannot run
[Magisk] Äptiva:
Hmm do me this. Manually mount system in your recovery and then try and flash it.
[Magisk] arsenal3010:
Thanks. Could you give me a command. I am not quite familiar with this stuff
[Magisk] Äptiva:
In TWRP:

Touch Mount > System
[Magisk] arsenal3010:
Yes now I can run your command without error.

Shall I flash Magisk again ?
[Magisk] Äptiva:
Give it a go
[Magisk] arsenal3010:
Still I got the same error :(

- Mounting /system(ro), /cache, /data

! Failed: /system could not be mounted!

I put Magisk zip file in my internal storage. Does it cause problem ?
[Magisk] topjohnwu:
Finally, all issues ironed out :)

It has been a loooong journey lol

After doing some final touches to the Manager and the repo system, the goodies are about to come!
[Magisk] Äptiva:
No. That's a bit strange though. This is a bit beyond my scope of tinkering
[Magisk] _XblackshadowX_:
Can someone please backport Magisk for jellybean?? Since this tool is very great...
[Magisk] arsenal3010:
i tried to run adb shell mount and found that /system is still read only. I think it is problem. Could you take a look ?

C:\Users\HUONG\Desktop\ADB Fastboot Tool>adb shell mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)

devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,seclabel,relatime)

selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

tmpfs on /tmp type tmpfs (rw,seclabel,relatime)

pstore on /sys/fs/pstore type pstore (rw,relatime)

/dev/block/by-name/factory on /factory type ext4 (rw,seclabel,nosuid,nodev,noati

me,data=ordered)

adb on /dev/usb-ffs/adb type functionfs (rw,relatime)

/dev/block/mmcblk0p6 on /cache type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk0p10 on /data type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk0p10 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)

/dev/block/mmcblk0p9 on /system type ext4 (ro,seclabel,relatime,data=ordered)
[Magisk] Äptiva:
JB? Not likely to happen as KK isn't even on the radar right now.

---------- Post added at 08:19 AM ---------- Previous post was at 08:16 AM ----------

what twrp version are you using?
[Magisk] arsenal3010:
It's 2.8.7.0

Even I check /system is rw, it still has same error :(
[Magisk] esrvR:
Can't wait my dude, so hyped for this update :cool:
[Magisk] Gamu79:
is it possible to make a xposed-v75-sdk21-arm-snapdragon for GT 9505 ?

installed all the steps and it works great , but exposed systemless is not working

would love to use exposed systemless :)
[Magisk] shoey63:
I think it's time to update your device. Surely there must be something within your budget that has at least LP.
[Magisk] carlshark:
Support for Mediatek Based Phones?

I have a cheap Mediatek based cellphone (Cherry Mobile Flare S4 Lite) on Stock Android 5.1. Running the v6 installer returns an "Unable to detect boot image" error.

I am attaching boot.emmc.win from the TWRP backup if it would help things. If you need anything else or if support for Mediatek-based devices is not possible, please let me know. Many thanks for your work!
[Magisk] mathy007:
Am still getting unable to detect boot image on HTC one M7 dual SIM running lollipop 5.0.2 what could be the issue
[Magisk] Neverendingxsin:
Any information on if the latest beta works with Android P official release on pixel 2xl?
[Magisk] stanley321:
I'm on 16.7 and I want to update to Android Pie via OTA.

When I click "Uninstall, Restore Images", it said "Stock backup does not exist"

Can I put the stock backup boot.img back to a location? Should I still gzip it? Where should I put it?

I know I can just fastboot and flash boot.img, but I just wanna try the official way.
[Magisk] peterlee928:
hey all, having an issue this time around w/ 16.7 beta. i flashed official P without "-w", then reboot. everything ok so far. then i go to magisk manager (latest version) to install the latest beta version. already something seems to be off - doesnt give me the option to install directly (recommended). but i go ahead and download the latest beta version, then flash to twrp, install magisk zip, then reboot. but now the os is stuck on the "G" page. am i missing something? any help would be greatly appreciated, much thanks in advance!
[Magisk] Ja_som:
Did you read the post right above yours?

Also

https://twitter.com/topjohnwu/status/1026522815086845952?s=09
[Magisk] Badger50:
What device?
[Magisk] zfk110:
Hi, Im running on MM base rom with stock boot and kernel, but no matter which Magisk I tried 15.3 to 16.7 I couldn't pass

ctsProfile:false

basicintergrity:true

there is the log
[Magisk] peterlee928:
oh man noob mistake sorry... pixel 2 xl. no custom roms/kernels. only tweak is busybox (stericson) and xposed.
[Magisk] Badger50:
This is what I did :good:

https://xdaforums.com/pixel-2-xl/development/2017-11-6-root-pixel-2-xl-t3701176/post77264251
[Magisk] peterlee928:
fantastic, will give it a shot :) do u need to flash "flash kernel 3.0"? if so, where can i find this file?
[Magisk] Badger50:
Don't know if you need to, but why not? Flash always makes good stuff! :cool:

But here ya go :laugh: https://xdaforums.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057/post77263877
[Magisk] peterlee928:
you are the man, thanks! unfortunately, i cant get the uninstaller file to flash in twrp... keep getting an error message. any tips on how to fix that?
[Magisk] Badger50:
Do you have the latest uninstaller zip? Found here..

https://drive.google.com/file/d/1g5vu2L4eGHk3EzjQ2WhmQPkdbgF4Tl8g/view?usp=drivesdk

Then maybe try fastbooting into twrp and go from there :good:
[Magisk] peterlee928:
you are a saint and i love you. ur instructions worked perfectly. much thanks for all the patience and instructions! sadly, i just realized that xposed doesnt have a P update out... so after all of this, i might just go back to 8.1 lol...
[Magisk] shadow321337:
Anyone have any luck getting SafetyNet to pass on Android Pie running Magisk? I'm on a Pixel 2 XL and can't get it to work.

*Editing my post after trying the v16.7 beta, so others can see. It does pass SafetyNet. I was using stable v16.0 prior.
[Magisk] LeftDarkneesGo:
HELP ME !

- Copying image locally

- Target image: /data/user/0/com.topjohnwu.magisk/install/boot.img

- Device platform: arm64-v8a

- Extracting files

- Unpacking boot image

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/data/user/0/com.topjohnwu.magisk/install/boot.img]

KERNEL [7899408]

RAMDISK [2504800]

SECOND [0]

EXTRA [0]

PAGESIZE [2048]

NAME [B3CCJ0J0BX00]

CMDLINE [console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk androidboot.bootloader=L3CCJ0J0BX00]

CHECKSUM [c01237dccb6c5e309f1f7a85e6ccb83f9a02155d]

DTB [214005]

KERNEL_FMT [gzip]

RAMDISK_FMT [gzip]

- Checking ramdisk status

MagiskBoot v16.0(1600) (by topjohnwu) - Boot Image Modification Tool

Loading cpio: [ramdisk.cpio]

! Boot image patched by other programs

! Please restore stock boot image

Failed!

! Installation failed

I try to install it on my Idol 4 6055B Use this boot. img I can patch it fix

https://mega.nz/#!L7ZHUChR!frg4x3-ukpD0xHZM_vAjzCOL5W7-KQGmqCZf-ppHLg0
[Magisk] martyfender:
I noticed this in your log:

So did you have SuperSu installed or did the rom have root built in?

I would flash the UnSu.zip and maybe even a fresh, stock boot.img for your specific rom then try again.

https://www.didgeridoohan.com/magisk/MagiskInstallationIssues
[Magisk] LeftDarkneesGo:
The ROM has built-in root, but all are so :L

---------- Post added at 04:10 AM ---------- Previous post was at 04:01 AM ----------

Well, I just tried UnSu. zip, but still not let me install the Magisk
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228

Flashing unSU won't remove the patches from the boot image... You'll have to find a ROM that's not pre-rooted or try to remove the patches yourself (no, I've no idea how).
[Magisk] FSOP:
Hey all, also having issue with v16 on the final "Pie" release. on my Pixel 2 XL

Flashed 16.7 however after boot it tells me my PIN is incorrect, tried this 3 times now, any ideas?

Thanks
[Magisk] Didgeridoohan:
Double posting... Hm... :( Anyway...

Should be fixed, but not released yet. Try an unofficial snapshot if you really must have the latest and greatest.
[Magisk] FSOP:
Sorry, I realised I probably didn't post in the right thread then realised I couldn't delete my other post.

No worries, i'll wait for the fix if it's a known issue :) Thanks
[Magisk] alone in lonely:
First of all,thanks to your invention that I can use root on my phone.To the problem i'm facing,for some reason,downloading the zip to install the magisk is not easy,so could you please add a function that I can install the magisk.zip in the app,not only download and install with the recovery or other two choices.

Maybe you want to tell me that flash the zip with the recovery,but sorry,till now my phone can only run a recovery which cant read the sdcard correctly.

Thanks a lot to your hard work,again.
[Magisk] martyfender:
Sorry, I guess I was wrong. I thought I had read in one of these threads that UnSu.zip removed root from roms that had it built in.
[Magisk] Didgeridoohan:
It's possible to install Magisk without using recovery. You patch a copy of your device's boot image with the Magisk Manager and then you flash that manually to your device with fastboot (or whatever is applicable for your device). There are instructions in the release thread, and you'll also find some info here if you need further guidance.

If you're already rooted with Magisk and you want to install a Magisk zip you've already downloaded, you can do that in the Modules section of the Manager. Just press the "+" and choose the zip.

You're half right. It'll remove all root related files, but the boot image will still be patched. It even says that you'll need to flash a stock boot image after you've flashed the zip.
[Magisk] stewie2806:
Hi folks

Lloyds bank app update recognises root,

I even tried uninstalling both Lloyds and magisk, rebooting, installing Lloyds again and logging in, flash magisk, reboot and then use hide on the banking app, reboot and it works the first time.

Then when I logout and login with lloyds it's kicks me out with the 'we've detected root' warning.

*edit: I'm using magisk 16.7 on G930f with TGP

2.2.2
[Magisk] casouzaj:
Have you tried hiding Magisk Manager in its settings?
[Magisk] zfk110:
genius !!! it worked now I can pass both!!
[Magisk] ericjwg:
anyway to uninstall magisk on a bootloop device with no custom recovery to flash mount_magisk?

i know i can get the device boot up by flashing the stock boot.img. but it wont uninstall those modules....
[Magisk] stewie2806:
No, it dosent work. It stil detects root
[Magisk] tire_007:
Is there any way to force remove a module (i installed a module to enable digital wellbeing but it dosn't want to unistall now) without loosing root?
[Magisk] casouzaj:
Moderators, please delete my post!
[Magisk] psychaox:
An app has found a new way to detect root since the latest update in the late July, despite Magisk hide working behind the scenes.

First of all, I have limited knowledge of computer language, and am not a native English speaker. Therefore, there might be misunderstandings or wrong attempts in this post. Please bear with me.

An app named Kirara Fantasia (a mobile game) has started to detect root since March. By means of the Magsik hide and rename package’s name tricks, I can play the game without error. But the app adds a new root check in the latest update and magisk hide has failed since then.

Here are my attempts so far:

Rename Magisk Manager’s package name and app checked in Magiskhide for sure

Upgrade Magisk from v16.0 to v16.7(1671) beta

Rename magisk manager or uninstall it (inspired by NemID’s case)

Change prop values back and forth via MagiskHide Props Config

Manually add Magsik hide rule (inspired by this reply https://xdaforums.com/showpost.php?p=77233157&postcount=6308)

Things as far as I know:

My device is HTC 10, with rom Leedroid v5.2.1 Oreo and kernel CleanSlate v3.7.10

Rootbeer sample all green

Safety net all green

Selinux status: enforcing (according to other user’s report, must to be enforcing, or the app will force quit)

Magisk core only mode activate

The app does not detect busybox. I still uninstall it, though.

The app requires no permission.

Google Play certification: certified

Magisk hide triggered successfully every time I tried to open the app

No other root apps installed (except for Leedroid tweak)

The app does not search for other apps named as Magisk Manager. I once changed one app’s name (in my case: matlog) to "Magisk Manager" after I uninstalled Magisk. And the game still worked fine.

Clear app’s data before every attempts.

The app detects USB debugging.

The app also detects non-stock rom, such as LineageOS and aosp roms.

I have uploaded two logcats with filter “kirara”. One is failed to pass the root check. The app was forced to quit few seconds after I opened the app. The other one is activating normally. And I manually quit the app a minute later. Also, whenever the app detects root, the game shuts down and a webpage directing to customer service pops out.

Compared with other cases, such as banking apps or mobile pay apps, mine seems to be much more childish. But still, I will be very grateful if anyone takes a look at it.

root detected http://txt.do/dzi9f

normal http://txt.do/dzi9p

magisk log http://txt.do/dzi09

latest app apk https://drive.google.com/open?id=1ao7-KawEEwXVp7_SvJKx9er9v7FNvGPN
[Magisk] casouzaj:
I posted this in the beta thread: https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post77218782

Would it apply to your case?
[Magisk] stewie2806:
No, as you can see both are true
[Magisk] casouzaj:
That procedure supposes that the Safety net tests pass. It is intended to try to pinpoint the sub-process which is still detecting root.
[Magisk] Didgeridoohan:
[MENTION=9348154]psychaox[/MENTION] You should follow [MENTION=4470081]topjohnwu[/MENTION] on Twitter:

https://twitter.com/topjohnwu/status/1026758148919455744
[Magisk] zfk110:
USAA app does the same thing, passing Safetynet doesn't matter for it, it still finds root, only way I can use it if I use web base interface it wont let me use app
[Magisk] Cuancena:
Where would I go to learn to make a module for a specific purpose? I'm trying to make a module that re-adds the down arrow and home button beneath the keyboard when using immersive mode in Android Pie. It baffles me that Google removed this, but I figured it would be pretty easy to make a Magisk module to reverse this one change. I'm just not sure where to start.
[Magisk] psychaox:
Thanks for your quick reply.

Such embarrassing...I'll wait and looking forward to it.
[Magisk] zeroprobe:
I posted an issue about Magisk not increasing the image size correctly for my module.

I am using the module template, [MENTION=4470081]topjohnwu[/MENTION] said the template handles the resizing.

Am I missing a line in the module template you need to include?

https://github.com/topjohnwu/Magisk/issues/434
[Magisk] Didgeridoohan:
The template does take care of resizing the image, and there's nothing you need to do or add if you're using the template.

My first guess is that your recovery is causing issues. Do you have issues when installing modules through the Manager?
[Magisk] dunjamon:
I've noticed the same thing with Halifax just this week. Just trying to see if anyone has any fixes, but nothing found yet.
[Magisk] Didgeridoohan:
And I'm assuming you've toggled MagiskHide off and on again, or?
[Magisk] Ketawa:
FWIW, I have a Pixel XL on Android 9.0 using Magisk 16.7 (1671). My device passes SafetyNet, but I had to add the USAA app to Magisk Hide for it to pass root checking.
[Magisk] JimZiii:
Toggled it on/off, tried reinstalling, tried older manager and older magisk root (was on 16.7 now on 16.0)

Checked that logging and mountnamespace is working.

Googled a bit but I'm not finding anything useful
[Magisk] Didgeridoohan:
Sounds like you've tried most things... But I don't think you've posted any logs yet.
[Magisk] xXCoolGuYXx:
Install failed for New magisk I'm on LG v20h918 on superv20 rom v4. 0 here the log file from magisk

Update it worked with TWRP
[Magisk] JimZiii:
do you need anything else?

EDIT: so i just tried the older rom where i had magiskhide and safetynet working before i updated my phone and i get the same thing.

when this happened i tried a new way of flashing, with HuRUpdater, so i tried flashing the old rom (b394) both with the hurupdater zip in twrp and also flashing b394-PV just regularly through twrp to see if this had anything to do with it which it didn't. i then updated through OTA's in system and tried flashing magisk on every OTA and had the same result. i factory reset and wiped system before flashing the rom just to be sure and as soon as my phone booted up i flashed magisk before anything else. right after a clean boot i pass on basic integrity but as soon as magisk is installed i fail on both.

i'm back on b407 and completely clueless to what to try next
[Magisk] dkadds2:
SOLVED.

Details at:

https://xdaforums.com/showpost.php?p=77282578&postcount=1912

####

Hi Guys,

Need small help - I've Magisk 16.7 installed on S9 using boot.img patching and flashing. Magisk itself is all good with SafetyNet pass. I don't have TWRP (at least yet).

Trying to add BusyBox (osm0sis) it downloads it, installation seems to go smoothly, though after reboot under modules it shows:

busybox-ndk

(No infor provided)

(No infor provided)

(No infor provided)

Under Downloads it shows that BusyBox update is available. Tried it to no effect.

p.s. I did check thread but haven't found anything on this. Not sure if it is Magisk or BusyBox from osm0sis issue?

How to get Busybox working?

Logs in Magisk show:

08-09 00:03:46.771 4199 4199 I Magisk : ** Initializing Magisk
08-09 00:03:46.933 4199 4199 I Magisk : * Creating /sbin overlay
08-09 00:03:46.937 4199 4199 I Magisk : * Mounting mirrors
08-09 00:03:46.938 4199 4199 I Magisk : mount: /sbin/.core/mirror/system
08-09 00:03:46.938 4199 4199 I Magisk : mount: /sbin/.core/mirror/vendor
08-09 00:03:46.938 4199 4199 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-09 00:03:47.051 4207 4207 I Magisk : Magisk v16.7(1671) logger started
08-09 00:03:47.051 4203 4203 I Magisk : Magisk v16.7(1671) daemon started
08-09 00:03:47.061 4203 4210 I Magisk : ** post-fs-data mode running
08-09 00:03:47.187 4203 4210 I Magisk : Upgrade/New module: busybox-ndk
08-09 00:03:47.187 4203 4210 I Magisk : Create /data/adb/tmp.img with size 64M
08-09 00:03:47.297 4203 4210 I Magisk : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img
08-09 00:03:47.580 4203 4210 I Magisk : * Move /data/adb/tmp.img -> /data/adb/magisk.img
08-09 00:03:47.580 4203 4210 I Magisk : * Mounting /data/adb/magisk.img
08-09 00:03:47.673 4203 4210 I Magisk : * Running post-fs-data.d scripts
08-09 00:03:47.673 4203 4210 I Magisk : * Running module post-fs-data scripts
08-09 00:03:47.673 4203 4210 I Magisk : * Loading modules
08-09 00:03:47.673 4203 4210 I Magisk : busybox-ndk: constructing magic mount structure
08-09 00:03:47.676 4203 4254 I Magisk : * Starting MagiskHide
08-09 00:03:47.676 4203 4254 I Magisk : hide_utils: Hiding sensitive props
08-09 00:03:47.676 4203 4254 I Magisk : hide_list: [com.google.android.gms.unstable]
08-09 00:03:48.708 4203 4505 I Magisk : ** late_start service mode running
08-09 00:03:48.708 4203 4505 I Magisk : * Running service.d scripts
08-09 00:03:48.708 4203 4505 I Magisk : * Running module service scripts
08-09 00:04:03.338 4203 4254 I Magisk : proc_monitor: com.google.android.gms.unstable
08-09 00:04:19.218 4203 4254 I Magisk : proc_monitor: com.google.android.gms.unstable
08-09 00:04:53.953 4203 4254 I Magisk : proc_monitor: com.google.android.gms.unstable
08-09 00:10:22.107 4203 4254 I Magisk : proc_monitor: com.google.android.gms.unstable

Same question raised under osm0sis thread: https://xdaforums.com/showpost.php?p=77282578&postcount=1912
[Magisk] Bigal098:
Honor 9
[Magisk] Didgeridoohan:
I'm going to take a wild guess that you're using an unofficial build. Please don't report on issues with those outside their respective threads. It's bound to cause all kinds of confusion. But, the fix for the issue you saw has already been posted:

https://github.com/topjohnwu/Magisk/commit/ff36f2ba17a63359395daa1bced28e2a12c17859

Your logs look perfectly normal... I'm gonna have to join you on the clueless bench.
[Magisk] Nixsliu:
I'm trying to root Android 9.0 at the step "patching boot.img" in Magisk, got a failure, mentioned it as below.

- Copying image locally

- Target image: /data/user_de/0/com.topjohnwu.magisk/install/boot.img

- Device platform: arm64-v8a

- Extracting files

! Invalid Uri

! Installation failed

Anyone has insights about this error? Appreciate your help!
[Magisk] dkadds2:
Check if you've same Magisk version set as stream (Beta/Stable) as installed at boot level.

https://xdaforums.com/showpost.php?p=77282578&postcount=1912
[Magisk] JimZiii:
Ok, thnx for your time anyways. I think last time I had it working I had flashed a really old rom and updated up to 394 so tonight after work I'm gonna try doing that again and see if that helps. I just wish I had remembered that before spending all this time restoring my phone, again, lol
[Magisk] Groot:
Good evening!

I installed magisk v16.0 stable via the patched boot.img method.

Question: is it safe to update to the beta version of Magisk inside the Magisk manager without patching another boot.img? Thank you!
[Magisk] Badger50:
"I am Groot" Great movie :laugh:

I've done that exact same thing before without issue going stable to beta and visa versa. Can't imagine it would cause you any grief. However, always a good idea to have your magisk zips on your internal storage before you begin just in case :good:
[Magisk] kantjer:
I don't expect your phone to explode but you can expect problems if you don't keep MM and the patched boot.img in sync.
[Magisk] Krunk_Kracker:
Delete