yashsingh1/xdaforums huggingface dataset:
[Magisk] zjbbhsso:
Well ... Because that's all I need in my HTC 10.

At first, I already installed Xposed Installer, Magisk Manager and Root Switch.

The author of Root Switch said you need to reflash SuperSu to patch it if you want systemless root, so that's first step.

Then I started flash SuperSU, and my HTC 10 is s-off, locked bootloader, which is acting like unlocked bootloader.

I won't pass Safetynet with unlocked bootloader, so I used xSetProp to set ro.boot.verifiedbootstate=green, and xSetProp is a module of Magisk.

After Enable Magisk Hide, reboot, and toggled disable in Root Switch, it passed Safetynet.

However, I need Xposed, so I flashed Xposed 86.2, which requires SuperSU, not Magisk.

After flashed Xposed, reboot, and toggled disable in Root Switch, it failed.

Then I flashed suhide, reboot, and toggled disable in Root Switch, it passed!

Xposed 86.2 is under /su, Xposed 86.6 is under /magisk, I think that's why suhide works with Xposed 86.2.

With this method, you don't need reboot to disable Xposed.

Although you enter Xposed Installer, and saw Xposed Framework is not installed, it seems like it's still working.

Because when I open some apps, the ads still gone, which is the function of MinMinGuard.

---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------

Yes, according to the author, you put these 2 files with command, when flash the SuperSu, it will auto patch SuperSU.
[Magisk] dimm0k:
some help... in an attempt to use Android Pay, I went ahead and disabled the phh supersu module from Magisk and now I'm unable to get root back. I see the disable file in /magisk/phh, but no way to remove this file... any suggestions?

EDIT: re-flashing phh supersu fixed it...
[Magisk] htb2050:
Okay cool. I think I am using Samsung software so emoji aren't being set because of different file names.

I will give viper a try tomorrow then.
[Magisk] zapahacks:
Thanks for your help, unfortunately it did´nt work for me
[Magisk] ChokingHazard91:
I gave up about a week ago actually. I am not giving up Xposed for pogo so I have deleted the game. But please let me know of you find a working solution :)
[Magisk] knipp21:
To aid with confusion.. Please post your device type if you have SN working

To my knowledge you cannot pass with a nexus device if your BL is unlocked.

Anyone passing with a nexus device on N please confirm or deny
[Magisk] edyny1:
What exactly is this module for? What are the steps to install that module and can it be installed on a Galaxy S6 Edge???
[Magisk] jcrompton:
Hopefully I'm not pushing my luck with the questions:

I have Nexus 6 with Nitrogen android 7 N ROM

Had it rooted with SuperSu 2.78

Did full unroot and chose to restore stock boot image

Made sure root was gone with root validator

Flashed Magisk 8

Then phh 259

Then the ver2 xsetprop

I'm able to run the xsetprop commands but Safety Net still fails

Any thoughts?
[Magisk] chrisc93:
Running PureNexus with phasma kernel on my Nexus 5X.

SN is working with xSetprop v0.2
[Magisk] yochananmarqos:
Thanks! FYI, xsetprop ro.boot.flash.locked 1 does not persist upon reboot. I set Tasker to run it on boot.

SafetyNet passes, but for some reason Google Play Services freezes trying to add a card.
[Magisk] 09eric09:
Does anyone have a link to the viper4android_magsik (not sure if that's the right name) zip file? It's not in the OP anymore.
[Magisk] jcrompton:
It's in the downloads of Magisk manager
[Magisk] waylo:
Try clicking the magiskhide option in the Magisk manager.
[Magisk] lolvatveo:
help, root permission is temporary and fake. can't affect anything on the system

https://xdaforums.com/t/editing-sys...and-flashing-our-modifications.4196625/page-5
[Magisk] pndwal:
Looks like another victim of this issue affecting Samsung Note 4 and other armeabi-v7a devices running stock Android 6, 7

https://github.com/topjohnwu/Magisk/issues/4174

No pull request yet, but good recent progress in this longstanding issue.

You can try the last working test build(s) Canyie supplied; he and vbb2060 look close to supplying proper PR / fix...

👀 PW
[Magisk] GauchoTche:
I have installed magisk alfa 23015 in my ZUK Z2 and shamiko. Shamiko is returning the following error: post-fs-data.sh fails to run. Magisk is broken on this device.

Any ways to fix this?
[Magisk] GauchoTche:
is app-debug.apk the file to install magisk canary latest version?
[Magisk] GauchoTche:
what's the diference between Canary, VVB and Hitman's version? I can see the zygisk/Denylist/Hide differences in the table, but other than that why 3 different versions, does it has anything to do with hiding magisk for bank apps for example? is anything besides Shamiko working?
[Magisk] zgfg:
Latest (and last but one) Alpha is 23016.

You can update Alpha apk directly from the Magisk Alpha apk

For Shamiko, Zygisk must be turned on, and there must be no Riru modules

Finally, you must Confugure DenyList but after that you must disable Enforce DenyList and reboot (Shamiko will take over DemyList)

Btw, by switching Update channel to Canary, you can update/switch to Canary (assuming you did not run Alpha in the MagiskHide mode)
[Magisk] zgfg:
All your questions have already been addressed (and not once) in the thread - please take some time and study

E.g, for differences between the Magisk flavors, see the excellent post #49314
[Magisk] GauchoTche:
Changing from alpha to canary inside the app is not working. It does shows a download link to canary, but after starting the process It asks to replace the apk but then nothing happens. Is there a link for that latest canary apk so that I can manually install it?
[Magisk] zgfg:
Of course. TJW Magisk Github page, download link for Canary

If needed, get familiar with the links you have in your Magisk app as well as the stuff on the Magisk Github page, what can you download there, documentation, etc
[Magisk] GauchoTche:
i've followed the steps but I still get:

post-fs-data.sh fails to run. Magisk is broken on this device.
[Magisk] GauchoTche:
I've come to this list:

is the right file app-debug.apk?
[Magisk] zgfg:
I don't know and absolutely don't care

I wrote you where to go.

Now I'm asking you - what happens when you click to Magisk Canary on that Github page as on the screenshot?!

Does it maybe start to download latest Canary apk?!
[Magisk] GauchoTche:
app-debug.apk is the right file indeed.
[Magisk] GauchoTche:
So I've tried both the Alpha and the Canary versions and both are giving me this same error. If anyone with deeper knowledge can help I would thanks very much.
[Magisk] pndwal:
Assuming issue is with Magisk settings / database (this can become corrupted especially when switching between various Magisk builds) / modules and not with patched boot image, you are probably best to start setup (only) completely fresh. Simply delete everything inside /data/adb with a root explorer and reboot...

This will effectively restore whatever Magisk version is currently installed to clean settings / setup and force Magisk to re-initialise.

Nb all modules will be removed along with db etc. This is usually fine, but may not fully revert modifications made in /data by all modules; uninstalling all modules first within Magisk is the best approach if possible as this will run their uninstall scripts for proper cleanup... If you intend to install any removed modules again later this shouldn't matter however, and they can always be properly uninstalled after that...

Hope this helps. 🙂 PW
[Magisk] Johnson_Ran:
and now,offical magisk alpha already fixed ramdisk issue

Telegram

t.me

yay!
[Magisk] pndwal:
Yup, just noticed this... Thanks Guacamole! PW
[Magisk] pndwal:
alpha changelog​

Magisk (558710bb-alpha-2)​

[App] Support SharedUserId

[App] Delete the backup file after restoring the boot image

[App] Built-in current version update log

[App] Use local version when unable to download stub

[App] Modern time API using Java 8

[General] No longer automatically unlock device blocks

[General] Use MagiskHide to hide when Zygisk is closed

[App] Remove markdown rendering

[General] Do not execute scripts that ignore loaded modules

[App] Fix the second click of hide app button may be unresponsive

[App] Enhance the function of repairing environment

[App] Support setting PATCHVBMETAFLAG flag to handle vbmeta in boot image

[App] Adapt to Android 12L

[MagiskInit] Refactor the processing method of two-step startup

[General] Skip mirror overlayfs partition

[MagiskInit] Support handling force_debuggable flag

[App] Fix SnackBar popup position

[App] Remove install to unused slot limit

[MagiskBoot] Speed up zopfli compression

[App] Fix can't be opened in some cases

[App] Patching the image no longer affects the current environment when there is root

[App] Disable return action when reboot is required

[General] Forced not to install to recovery when ramdisk exists
[Magisk] zgfg:
Sorry but what was actually the fuss about Ramdisk and the fix - something specific for Samsung?

On my Xiaomi, Magisk app still (Alpha 558710bb-2), as always, displays Ramdisk No although when patching it finds ramdisk in boot.img and properly installs Magisk (as always)
[Magisk] GauchoTche:
Hello! Thanks for the reply! my /data doesn't have an ADB folder. Only com.keramidas.titaniumbackup. I've done a search for ADB in all disk and it doesn't find an ADB folder. I am using ES FILE EXPLORER with root
[Magisk] pndwal:
Nah... Discussion started with this one (OnePlus 7 Pro):

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86211569

LoveSy's fix / PR (OnePlus 7 / 7 Pro issue) here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86212585

(You tried the test build next post. 😉 )

User found another workaround:

Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86215113

@Johnson_Ran merged LoveSy's proper fix in his personal Alpha fork and made it available since still wasn't merged in Canary or Alpha:

Post in thread 'Magisk General Support / Discussion' https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86216333

Another user tried this on a Sammy device, got confused about Alpha MagiskHide w/ denylist... Discussion ensued...

Last @Johnson_Ran post was PSA that LoveSy fix is in 558710bb-alpha-2. This change:

• [General] Forced not to install to recovery when ramdisk exists.

Hard to keep up with Alpha, Custom and all this, I know! 😀 PW
[Magisk] pndwal:
So are you looking in root directory?... Try Root Explorer... Select New, then Root Tab... PW
[Magisk] zgfg:
If Magisk was installed (and if you didn't uninstall), you must have /data/adb - that's folder where is e.g., Magisk.db (database with info about apps granted root, MagiskHide/DenyList, also modules folder with all your modules.

If not present, you don't have Magisk and the stuff

Instead of the old ES Explorer use the newer/much better MiXplorer (PlayStore or XDA thread)

But why don't you scroll down in Magisk app, see a big Uninstall button, and accept to fully uninstall Magisk, its modules, everything (it will delete /data/adb/

Important: Do not just uninstall Magisk app - in that case Magisk itself remains (with /data/adb folder, modules, everything) -yoz just don't have the front-end app to manage them
[Magisk] pndwal:
I suggested rather than than reflash, just fix current installation by uninstalling modules (optional), deleting all /data/ADB contents and rebooting, that's why. 😁 PW
[Magisk] HippoMan:
You appear to be looking in the /data directory under /sdcard (which is also called /storage/emulated/0), not under the device's / file system.
[Magisk] zgfg:
Since he cannot find (?!) /data/adb...
[Magisk] GauchoTche:
Used the Uninstall, did all the install process again, (still no /data/adb) UPDATE: I do have the /adb folder now. Still the same Shamiko error =( (now using a proper root explorer in the right /data folder)
[Magisk] traversone:
On LOS 17.1 (Samsung S4 and A3), Magisk-558710bb-alpha-2 makes denylist aborting once trying to open, it reverts back to launcher directly.

Zygisk is enabled and working properly.

Magisk-558710bb-alpha (not alpha-2) works normally in same environment.

edit: on Samsung S8 (Hades ROM) same behaviour: Magisk aborts to launcher when trying to open denylist (both with Zygisk and MagiskHide enabled)
[Magisk] zgfg:
Provide the screenshots how do you use your root explorer to look for /data/adb.

Step by step

Compare the screenshots fron MiXPlorer

You must not be looking under /sdcard

And in /data you must see all the other folders like /data/app (all your user apps installed), /data/user/0 (settings for your apps), etc.

If you don't see them, you use wrong 'root explorer', or it was not granted root, or you don't know how to use
[Magisk] pndwal:
So have you tried simply deleting all contents / rebooting (with root)? What happens? PW
[Magisk] GauchoTche:
Yes, had to do the Zygisk again, reboot, Shamiko again, reboot, same error.
[Magisk] traversone:
Honestly speaking, GauchoTche's issue is also present on all Android Box I tried with same Magisk release. Shamiko refuses to work with same error. Same LOG
[Magisk] pndwal:
Interesting... Still, looks like a magisk issue... Is the box old? Launch w/ Android 6-ish ?

@GauchoTche's device is Lenovo, LV Android 6, seems to have stock Android 8 now:

https://m.gsmarena.com/lenovo_zuk_z2-8125.php

Ok, at least definitely clean magisk install tried... Sorry didn't solve. 😕

I saw you attempted to open issue ticket but bot knocked you back... Probably good to try again as seems likely Magisk is broken as reported. - I searched and couldn't find similar / duplicate issue reports...

You didn't provide any proper details, which is the problem; you need to follow (fill out) the issue template and give device, ROM and other relevant details. Especially need to be reporting on latest Canary build ONLY. (Since that has all latest merged fixes, John doesn't waste time on issues reported for earlier builds... also since canary is debug build it's logs are more useful / verbose...

Tip: check / copy required details from other recent open issues. You'll see you need info in first post like this:

Device: xxx

Android version: xx

Magisk version name: 0c1f688

Magisk version code: 23016

Supply any logs you can using Canary ONLY.

👍 PW
[Magisk] GauchoTche:
Problem is in the rules they say they don't accept hiding stuff!?
[Magisk] pndwal:
Actually it depends... Some hiding issues have been accepted since that rule (I'll dig up example and post it for interests sake...), but I think this will get traction as underlying reported issue is NOT a hiding issue... Don't worry, if magisk is broken they won't fob you off... It should be appreciated! 😋 PW
[Magisk] GauchoTche:
Fantastic. I've open the bug.
[Magisk] pndwal:
Note this example, still open, taken seriously by all concerned incl. TJW:

https://github.com/topjohnwu/Magisk/issues/2406

Some good comments re. the real intent of that rule here too...

Also, note that many major magisk collaborators contrib like vvb2060 etc have fingers in LSPosed pie and thrive on hiding solution challenges anyway! 😁

👀 PW
[Magisk] traversone:
just for clarity: issue on 4 different Android Box is present on Nougat, Pie (2 of them), Q and on S905X3 and Rk3328 architecture
[Magisk] pndwal:
Thanks... Could you help by commenting here also?

https://github.com/topjohnwu/Magisk/issues/5185

😀 PW
[Magisk] pndwal:
Good stuff...

You hadn't mentioned using custom ROM (I think):

BootleggersROM-Oreo4z2_plus. 2.3-Stable-Shishufied-20180708

Guessing now it may be a ROM issue... Any knowledge of Shamiko on ZUK Z2 w/ stock ROM?

Also, you'll probably be asked to supply proper logs. Basics here:

https://github.com/topjohnwu/Magisk#bug-reports

Comprehensive info here:

https://www.didgeridoohan.com/magisk/MagiskHelp#

👍 PW
[Magisk] GauchoTche:
I mean, yeah, sometimes different roms have different working, but it would be good if the app is updated to work with this kind of rom also.
[Magisk] GauchoTche:
It would be good if Shamiko was on github... so that we could check on what problem that specific error message triggers. Do we have access to the source code?
[Magisk] pndwal:
Sure... Magisk can bypass some ROM / kernel issues, unsupported functions, even bad code... but not all. We'll see; this may well occur on stock also, just would be good to know.

It may well be on GitHub...

No. (If on GitHub it will be in private / restricted repo.)

- https://t.me/c/1414270883/27125

👀 PW
[Magisk] traversone:
this alpha-3 version is unable to patch boot, at least on arm7a !! it seems a regression to me.

previous behaviour (abort on denylist gathering) is not present anymore
[Magisk] zgfg:
Frankly, with 558710bb-2 I did not have any issue - it was not crashing for me when opening Configure DenyList

But with 558710bb-3 something is indeed bad: It patches the img but that patched boot img is not flashable as img file through TWRP (I didn't try with fastboot)

I tried couple of times (patching again) but TWRP never recognized as an image file (extension was correct but apparently something is wrong with the format)
[Magisk] pndwal:
& @zgfg

Interesting.

Just took Direct install on RN8T. No issues... PW
[Magisk] pndwal:
@zgfg & @traversone

Alpha admin (Canyie I believe) would appreciate logs for these issues... Could you post here or reply here?

https://t.me/c/1414270883/34299... Ta.

( https://t.me/c/1414270883/ )

Nb. You'll now need Nekogram X to translate Alpha group... 👍 PW
[Magisk] traversone:
here you are (LOS 17.1 Samsung S4 and Android Box PIE armeabi-v7a).

on Samunsg S8 (Hades Q ROM, arm-v8a) it works well, though

- Target image: /dev/block/mmcblk0p20

- Device platform: armeabi-v7a

- Installing: 558710bb-alpha-3 (23016)

- Unpacking boot image

Segmentation fault

! Unable to unpack boot image

! Installation failed
[Magisk] pndwal:
Deleted (duplicate)
[Magisk] pndwal:
Thanks. 👍 Can you supply full Magisk log though?...

In Logs, clear logs (bin symbol), perform patch, save log (disk symbol), retrieve from set download folder... Ta. 😛.PW
[Magisk] traversone:
Magisk Install LOG is saved exactely as reported before (nothing more).

Attached the full LOG after a reboot.
[Magisk] zgfg:
Interesting. Downloaded today 558710bb-3 apk again (from the same TG Alpha channel), installed, patched my boot img and although the patched img is slightly bigger than with all previous Alpha versions (yesterday it was also that bigger), today I flashed with no problem (OrangeFox correctly recognized as img file - yesterday it did not want to) and now running 558710bb-3 with no problems

Unfortunately I deleted yesterday the apk, several patched img files (tried several times, always the sme) and even the patching log file (but I shortly opened yesterday and as far as I remember everything looked correct)

But OrangeFox was always recognizing the patched boot img as zip file (?!)

Today, yesterday and every other time I always patch and flash the same way. Don't know what went wrong yesterday

Nwm
[Magisk] koala86:
Hello everyone,

I attempted to unroot my phone by uninstalling Magisk; however, my phone is not able to go to the home screen anymore. The phone is only able to cycle through a few pages such as fastboot mode, or the page, which indicates "The boot loader is unlocked and software integrity cannot be guaranteed... The third option is recovery mode, but that leads me to nowhere. I looked up many tutorials and tried to use the MSM tool, but I did not have any luck. When I used the MSM tool, my phone showed up as COM3, but the tool said "Waiting for device."

Can someone link me to a step-by-step guide, or assist me? My phone is a One Plus 7 Pro (unlocked T-Mobile version).

I attached a few images of the only options that I can see. Also, does this indicate that my phone is soft bricked, or hard bricked?

Thank you!
[Magisk] yujincheng08:
send boot.img
[Magisk] traversone:
here you are, thank you for supporting
[Magisk] pndwal:
Soft brick...

Hopefully you have / know current ROM installed...

I believe 7 Pro is ramdisk yes, A/B, recovery/recovery ramdisk in boot device...

Just extract boot.img from ROM package and flash it. (I'm unfamiliar with A/B devices: may need to flash to both slots or check guides...) Boot and should be fixed...

Alternatively, if stock ROM package / utility allows you to flash whole fastboot type ROM w/o data wipe, this should also fix boot issue.

Nb. Possibly you're reverting Magisk install due to this OnePlus 7 / 7 Pro w/ Android 12 compatibility issue:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86212585

FYI, this has already been fixed by LoveSy (@yujincheng08 ) and fix was merged in unofficial Alpha Magisk just yesterday...

I've also linked his working test fix built in LSPosed Magisk fork; It's latest TJW Canary + LoveSy fix.

Hopefully his Pull Request will be merged before next TJW build. 😀 PW
[Magisk] pndwal:
Further to https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86229453

@koala86, OnePlus 7 / 7 Pro users:

I notice that a competing fix for this Android 12 issue from vvb2060 now exists:

https://github.com/topjohnwu/Magisk/pull/5184

Test build:

https://github.com/topjohnwu/Magisk/actions/runs/1669969534

👀 PW
[Magisk] zgfg:
Don't be kidding. Not only that he constantly pushes their TG channel to be ZH only (dispite that vvb2060, lead developer of Alpha opposed to that restriction), but he now effectively blocked copying from TG to make sure that one could not use Translation in Telegram even for reading
[Magisk] F308:
Advise please one thing, related to soft brick.

I mean - situation with developer options disabled.

How to flash boot.img or the whole clean ROM without USB debuging?

I mean - in situatlion when there's no TWRP for particular model.
[Magisk] martyfender:
I have been using Magisk alpha for sometime with riru, momohider and riru version of safetynet-fix. I had zygisk disabled and magiskhide enabled.

I decided to to remove those modules and try shamiko with zygisk enabled and the zygisk version of safetynet-fix. Under the module section for shamiko I get:

_post-fs-data.sh fails to run. Magisk is broken on this device, just like a previous users post. This is despite the magisk log showing all of the scripts ran. I am attaching logs. I have only tried this on the latest alpha 3. Does anyone have any ideas?

Thanks
[Magisk] J.Michael:
I've lost track of what device you have but, in general, there is a way to apply an "official" ROM. I think most devices have an "Emergency Download Mode".

Try to find a forum for your device. There will probably be a description of where to find a "stock ROM", and how to install it.
[Magisk] pndwal:
Yes, discussed this with @GauchoTche & @traversone here. Issue on TJW builds also.

Thanks for confirmation / logs. Please post them / comment in @GauchoTche's new GitHub thread to assist with proper fix / experienced Magisk collaborators... We are mostly amateurish here. 😜

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-86224535

👍 PW
[Magisk] martyfender:
Doesn't one need to be on canary builds to post logs there? I don't really want to switch to the canary build. The alphas have been good for some time.
[Magisk] pndwal:
Fastboot flashing should just work without usb debugging. ADB commands require debugging mode... If I'm not wrong you can just follow standard instructions... PW
[Magisk] pndwal:
To make issue, yes... But comments with confirmation / complimentary information should be appreciated.

Also, main reasons for Canary requirement are latest commits / fixes are merged, and has verbose debug logging. Alpha logs are also useful as they are generally synced w/ Canary and are debug builds...

😛 PW
[Magisk] martyfender:
You are far from an amateur poster here. I did post those logs there, Thanks

although I can easily find new builds on Telegram, I feel that it is a mess to post bugs there. From what I have seen there on various threads, often it is even unwelcome, so I refrain from reading much there.