yashsingh1/xdaforums huggingface dataset:
[Magisk] samsungFanboy85:
I know hardware key

Sir thank you sir!

Thank you sir, im gonna ready it couple of times before ask any more things barely :) now how would u spoof a config on G server? Ok but again thank you as your info and refs im atm trying to grasp it... Hmm tommorow i also will try a little experiment... Game devs say:

If your device is not listed above but you are still able to purchase XCOM 2 Collection, your device is capable of running the game but is not officially supported. Devices that are not capable of running XCOM 2 Collection are blocked from purchasing it."

Yes before Props config setup i confirm not visible however post fingerprint and is right back up for 27e... You think they might however stupid may sound this : verification of what is it running on? Im 99% no my fantasy.. However 27euro lost because im sure refund wont apply... :) G only sales platform & once payments are done G is out... Be protection only developer side if would exist... Just curious because first ever developer of yet uncracked i think non game they did... Seriously amazed about it

Wow ... I asked them 30min ago can i try game mr dev? Yes you can give it a go ...Unoffically supported whatever means
[Magisk] zgfg:
His repo or not, but it gave me the options to update BusyBox and Riru - since being in Alpha, I was not aware that one was updated on Oct 3 and another October 10.

That's why is usuful to have the Repo in Magisk app :)

If there was no WebView broken, I would stay on TheHitMan7's Magisk

Now alteady back to the latest Alpha (instructions for anybody who is willing to switch between Stable, Alpha, TheHitMan, back and forth)

- while still on TheHitMan7, I replaced its magisk.db with the magisk.db I copied/stored when I was on Alpha (before moving to TheHitMan7)

- then uninstalled TheHitMan7 Magisk app

- rebooted to TWRP (use Fastboot if TWRP N/A for your device) and flashed my saved boot.img previously patched by Alpha

- rebooted and installed Alpha apk again

And everything was back as I left on Alpha before experimenting with TheHitMan7 (root apps, Zygisk, DenyList, modules, you name it) - I only needed to let the Alpha app download the SafetyNet checker stuff again
[Magisk] LNS:
@pndwal

@zgfg

Thanks guys, complete uninstall let me install stable magisk with root.
[Magisk] samsungFanboy85:
But stealing is bad dont do that #copyright
[Magisk] pndwal:
I agree it's not clear if issue is actually that you didn't restore hidden Magisk App to normal before reverting.

FWIW, I put some tips on removing a conflicting App here:

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

Edit: Scratch that. 👍 🙃
[Magisk] pndwal:
True... Also proof of concept for custom repos supporting dev information and update flagging in upcoming TJW builds w/ official repo gone. 😛

Interestingly I did something very similar but it didn't work...

I backed up Alpha /data/adb directory, did complete uninstall, set up and played with TheHitMan Custom Magisk, restore whole (Alpha) /data/adb directory before installing Alpha App and Alpha patched image, BUT got bootloop on reboot! ☹️

Had to boot TWRP and remove whole /data/adb directory before Magisk would stick / boot. - Can you put a finger on the reason backup / restore db only might work better? Any idea what may be causing conflict? Ta. PW
[Magisk] zgfg:
I did backup the whole adb folder (just in case) but restored only magisk.db (since it worked, did not try restoring the whole adb backup)

That way, now back on Alpha, I of course also have the new BusyBox and Riru that I updated from the Repo when I was shortly on TheHitMan7

Btw, when I was switching from Alpha to TheHitMan, I also did not uninstall Magisk (just uninstalled the app). In TheHitMan7 I had to configure MagiskHide and also apps granted root - that's strange because Policies table (apps granted root) in his db looks exactly the same as in Alpha and Stable/Canary,

I'd say its Magisk found the different db (basically Denylist table instead of Hidelist) and deleted/recreated the whole db

Differencies between databases are simple: denylist vs hidelist table, and denylist vs magiskhide in settings table - metadata and policies table are the same.

Edit: empty strings table (whatever it is) in TheHitMan7 vs long keystore string in Alpha and Stable/Canary
[Magisk] wilsonhlacerda:
Hi all! Stuck on boot with Alpha, can you help me?

So doing some tests on an old Galaxy S4 Mini running LOS 17.1 (Android 10) and TWRP.

Stable Magisk v23 works just fine, all features. Can install it on TWRP or by patching boot.img without problems. Can uninstall by unhiding Manager and renaming Magisk file to uninstall.zip and flashing in TWRP. All perfect.

Now with device clean (completely uninstalled Magisk v23, reboot and fine without root) if I try newest Alpha from here:

https://github.com/vvb2060/magisk_files/tree/alpha

1- flashing as zip on TWRP everything runs without errors, but when booting to system won't boot. Get stuck on boot, with frozen "Samsung" logo. LOS boot never starts.

By rebooting to recovery and uninstalling Alpha or flashing stock boot.img the boot problem is fixed and can boot LOS.

2- installing as apk and then running it to patch the stock boot.img and flashing this on TWRP to boot, everything runs without errors, but when booting to system won't boot.

Everything just like 1.

Well, do you have any tips?

Are there reported bugs like that with newest Alpha release? I couldn't find.

When flashing Alpha is it necessary to do any additional procedure than when flashing stable Magisk?

I really want to try those new Magisk flavors, with the upcoming new hiding approaches.

Thanks in advance!
[Magisk] zgfg:
Maybe you have issue with some module left from Magisk Stable (you didn't uninstall/disable them?)

From TWRP, Advance, File Mngr, go to /data/adb/modules and put an empty file named disable to each subfolder (for each module) and reboot
[Magisk] wilsonhlacerda:
I always thought that when flashing Magisk file as uninstall.zip under TWRP would also delete all modules besides Magisk itself. So I haven't considered and even checked that!

I'll do it again and see if some modules are left. And if it solves the booting problem or not, then I'll report back.

Thanks for replying!
[Magisk] zgfg:
Sorry, if you flashed uninstall.zip, modules and everything from Magisk should have been wiped

Have you checked /cache/magisk.log

For the reference, mine attached (Alpha working fine)
[Magisk] nickster_uk:
Thanks pndwal 👍

I didn't realise it would be as simple as removing the renamed Magisk. I did that and installed the version of MM that I originally flashed with. It detected Magisk, root was still working but I still wasn't able to access Magisk settings and no su prompts were being generated for any new root apps. I then tried a newer version which I had stored on my device and everything is now working perfectly.

Not gonna update Magisk as I'm still going to flash with 11 over the next few days but pleased it's now working as it should.

Appreciate the help.
[Magisk] nickster_uk:
Thanks Philnicolls89 👍

I didn't realise TiBu was that outdated, but you're right.

It used to be my #1 root app!

Appreciate the tip on Migrate. It looks very good tbh and I've just taken a full backup with it which I will flash with 11.
[Magisk] ipdev:
Hi all. :)

Just a quick note for those using newer (test/unofficial) builds that have the online Module Repo removed.

Magisk-Modules-Repo - GitHub - Link

Magisk-Modules-Repo - Repositories - GitHub - Link

If you keep an eye on the repo, you will see when the developer(s) push an update.

Most of the modules have links to support threads and/or another spot that you can download the updated module.

Didgeridoohan uses the GitHub releases option for MHPC. 🙃​

If no other option is available, you can clone or download the specific module repo and then zip it into a new Magisk module zip file. ;)

---

I Hope the option of a custom module repo is not too far down the list. ;)

State of Magisk: 2021 - WebSite - medium.com - Link

I have been a little curious since I mentioned it in a prior post that Magisk was once on PlayStore.

If I remember correctly, this was the main reason Magisk was booted from PlayStore. :unsure:

Now that the module repo is removed, does Magisk now fit Google's criteria for PlayStore?

Cheers all. :cowboy:
[Magisk] J.Michael:
Did you try reinstalling Alpha *before* restoring /data/adb from earlier use of Alpha?
[Magisk] Philnicolls89:
Has anyone from Australia managed to get the 'foxtel go' app to work? It has been well and truly kicking my butt with detecting root!

I can open and login but as soon as I try to stream or watch anything it detects that I'm rooted.

I've tried basically every method or piece of advice on this thread and it's the only app on my phone that I can't get to work, not even my bank apps or gpay have given me this much trouble.

I never used to use it that much anyway so it's not to important, but I've gotten to the point where it's now about principle lol!
[Magisk] pndwal:
I'm assuming you

- have 'Device is certified' PlayProtect status in PlayStore settings.

- hid Magisk App in App settings.

- hid (tv) app from root in MagiskHide list.

- wiped (tv) app's data, set up & tried again AFTER all above.

- read MagiskHide wiki info:

https://www.didgeridoohan.com/magisk/MagiskHide

I don't use Foxtel etc, but I am aware that TV apps like European SkyGo have detected isolated process(es) for some time, and other TV apps are following suit.

If Foxtel is doing this it is likely detecting the Digital Rights Management related VGDRM Helper service isolated process specifically.

Solutions:

1) There are a number of current efforts to hide isolated processes. I recommend trying this by canyie:

- Riru - MomoHider module (aka IsolatedMagiskHider)

You can also try:

- riru-unshare module (Enhanced mode for Magisk Hide by vvb2060)

To check detection, vvb2060 provides:

- Momo Detection app; can check verbose log too

- Magisk Detector app

Links for these solutions and more comprehensive information here:

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

(Check last link, 'my setup', if trying MomoHider.)

2) You could try a more specific isolated process solution that simply blocks problem services, working for a number of TV apps if it uses VGDRM Helper service (or similar) Isolated process:

- Download AppManager

https://github.com/MuntashirAkon/AppManager

- Open and check Services tab for your app, and block the VGDRM Helper service (click on the crossed circle icon) and click 'apply rules' in top (3 dot) menu.

- Thanks to @Longhorn87 for this solution! 👍

https://xdaforums.com/t/skygo-app-detected-root.4128933/post-84688731

Nb. There may be other useful tips in that thread for detection issues w/ TV / streaming apps etc.

3) You may also have a Widevine certification issue.

Use DRM Info app from PlayStore to check if Widevine CDM security is 'L1' (HDCP level 2.3?) on your device. If so, all should be good here.

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

Many tv / streaming apps work with limited functionality / lower video resolution if limited to 'L3' but some may require L1 to work at all.

If not on L1 you may need to search for a solution to restore this specific to your device. It seems some devices can be restored by flashing Vendor or other, but w/ other devices it may prove impossible to regain L1 once widevine is tripped even w/ bootloader lock, and some may not retain L1 at all (unsure about this) once unlocked.

Hope something here works for you. 🤠 PW
[Magisk] pndwal:
No.

My thinking was that that restoring Alpha /data/adb first should remove any conflicting Magisk setup data prior to Alpha setup allowing it to succeed...

I guess after bootloop / cleanup / fresh Alpha flash I could have tried pasting Alpha /data/adb back again, but I didn't... 😆 PW
[Magisk] darkjake:
Hey guys,

Just having a big bloody problem installing magisk on LOS 18.1 on my Oneplus 8 pro.

Whenever I do the device will get hot, reception will be gone, system ui will keep crashing, device will operate on fullbright then eventually after about 2-5 mins qualcomm crashdumps to mdm_force_reset.

And even with all that happening Magisk still doesn't appear to have been installed according to MagiskManager :D

I have tried:

Factory reset

Magisk canary

patching boot image

reflashing rom

flashing via the (wip) twrp

flashing via sideload

All resulting in the same situation.

I have attached a full logcat dump below, device will continue to work properly with stock boot image and with stock or non stock kernal. This works on OOS just not LOS. During installation no errors occure for magisk so this has me stumped.
[Magisk] darkjake:
logcat : https://drive.google.com/file/d/163yX9hv7KgQU56N9DgeOC0Sdu6qK9SqX/view?usp=sharing
[Magisk] zgfg:
If you have TWRP, can you get /cache/magisk.log

Also, you say Magisk not installed (per the app).

Do you have a terminal app, then execute:

magisk -v

It will print the Magisk version, if Magisk is running
[Magisk] H4X0R46:
You pass safety net by removing root? Supposedly there was an update where safety net trips when your bootloader is unlocked, haven't seen it for myself quite yet.
[Magisk] :
Not the case on my galaxy s5 g900w8

I don't even have to dirty flash but i do because its quicker.

As long as i remove root i can pass.

But maybe if people are not passing it is because they have left over files that are being detected.

So installing supersu and suhide. And then flashing unsuhide then from inside the supersu app using full clean up to remove root and restore stock boot, that this could cleanup any left over files. I'm not sure on this but its a guess.

Seems the bootloader thing is certain models. I imagine google really made things complicated this time around. My bootloader is factory unlocked. My kernel is stock enforced.

For HTC maybe this will help. http://xdaforums.com/showpost.php?p=69219980&postcount=954
[Magisk] Iceyogurt:
This is a confirmed problem with modules containing binary and lib64. It's not proper time to port viper|atoms, which I did as well and made my phone stuck at boot.

Check the problem here. https://github.com/topjohnwu/Magisk/issues/4
[Magisk] nkk71:
Have you tried other colours :p

getprop | grep verifiedboot
[ro.boot.verifiedbootstate]: [pink]

getprop | grep verifiedboot
[ro.boot.verifiedbootstate]: [really_dark_green]
[Magisk] linkultima:
Hi, I installed Magisk V8 and phh superuser magisk r259 but cant seem to make root work, It keeps telling me the binaries are outdated and I cant get any app to get root access.

What am i doing wrong?
[Magisk] waylo:
Did you install the phh superuser app?

Alternatively, this happened to me when I had some weird left over supersu files. Magisk did an alternate install (seen on the TWRP install log) and root would not work afterwards.

If this is the case, flash magisk uninstaller, flash your stock boot.img, then flash magisk v8 and phh superuser.
[Magisk] :
Superuser has two parts. One is flashed through recovery or the magisk manager app can install the module (i flashed through twrp). Open up magisk manager and check under modules to make sure superuser shows up. If not you can get it from the download section in the magisk manager. If it won't show up there then maybe try flashing superuser through recovery.

The second part is the phh superuser app from the playstore.

Sounds like you're missing the first part.
[Magisk] linkultima:
Hi, I flashed magisk and then I flashed superuser via TWRP. After flashing I installed the apk via playstore but still no luck.

I checked under the modules and super user is listed but when any app asks for SU access, they fail.
[Magisk] :
Have you started clean before flashing magisk or were you rooted with something else?

If you we're rooted. Then what i had to do was flash my stock rom. Then i flashed superuser then magisk.

I'm on a galaxy s5 so this may not work for you if you are having a bootloader problem like others are having.
[Magisk] :
V8 broke phh's root for me too. only solution is to retrace your steps and go back to v7 to get back root. Or use supersu which works okay with v8.
[Magisk] linkultima:
[MENTION=7135029]babalou62[/MENTION] Yes I was rooted before but v7 worked fine even if I was rooted. All I did was removing root, flash v7 and then flash phh superuser.

Now that I do the same procedure with V8, phh superuser is not working as it was not installed but it shows under magisk manager as installed.

Will try [MENTION=5518680]bumjrah[/MENTION] sugestion but as I am aiming to play pokemon go again, I read that it is only working with phh superuser... do you know if it is working with chain's supersu+magisk v8?
[Magisk] DeadlyByNite:
If I'm not mistaken, I believe that you own an HTC One A9. Have you gotten the A9 to pass SN? I will try this here and see if it seems to work. In terminal getprop currently shows ro.boot.verifiedbootstate [orange]

Thanks for this tip ????
[Magisk] linkultima:
Hi, as I use a custom rom, restoring stock boot.img does not work for me :(
[Magisk] Captain_Throwback:
You won't be able to change this prop.
[Magisk] midgarsormr:
Sucks... I'm on a nexus 5 and using magisk or supersu and su hide and still can't open pogo. I wonder if it is indeed on certain devices, or it is being handed down slowly.
[Magisk] :
Instead of having to flash a stock boot, maybe you could flash uninstall magisk, then flash supersu. If that achieves root then open the app settings and do a full unroot cleanup and restore stock boot. This should cleanup any residual files. Even flash unsuhide if you had that installed at one point.

This is what i did when i upgraded from magisk v7 to v8
[Magisk] topjohnwu:
Please check out the new POC of Magisk Universal MultiROM!!!

http://xdaforums.com/showpost.php?p=69226527&postcount=6
[Magisk] KaMyKaSii:
Wow! Cool! And now you have a face. Blurry, but a face :silly:
[Magisk] :
Thanks so much :)
[Magisk] medohatem:
where to get viper4audio ver 2.5.0.5 ?

and on the Official ViPER4Android v2.4.0.1
[Magisk] darkjake:
Thanks for the reply, Magisk -v does not work (inaccessible or not found error)

Here is the magisk.log

magisk.log

drive.google.com
[Magisk] ipdev:
I am surprised you can even open the Magisk app. 🙃

That is one ugly logcat. :sick:

I almost want to see the matching kernel log. :giggle:

I see it is microG lineage build, not sure if that is what is causing the problem.

You might want to offer that logcat to the rom developer. ;)

They might be able to figure out if it is related to the microG implementation.

Why did Magisk destroy their build. :oops:

Would you be willing to do a clean flash using the regular lineage build and test Magisk again?

[ROM][OFFICIAL][instantnoodlep][11] LineageOS 18.1 - xdaThread - Link

LineageOS Downloads - WebSite - OnePlus 8 Pro - Link

If Magisk works with the regular lineage build, you could try a clean flash and include microG.

[APP] microG GmsCore - lightweight free software clone of Google Play Services - xdaThread - Link

microg - GmsCore - GitHub - Link

microg - GmsCore - Releases - GitHub - Link

Then try Magisk again.

Note:

I am not that familiar with microG and not sure what the advatage of baking it into the rom gives.

I know some devices need patches to support microG.

I am not sure if microG works with the official lineageOS for OnePlus 8 Pro.

Cheers. :cowboy:
[Magisk] pndwal:
Nb. There are a number of open issues for LOS 18.1.

Here's one w/ a number of OnePlus users commenting:

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

- Many are getting bootloops here, but one user w/ Fairphone 3 reports similar stability / forced reboot problems:

https://github.com/topjohnwu/Magisk/issues/4213#issuecomment-846555592

- OnePlus 5T user fixed issue after determining his was caused by PlayStore issue by using NikGapps:

https://github.com/topjohnwu/Magisk/issues/4213#issuecomment-842971119

He mentions solution from here:

https://gitlab.com/LineageOS/issues/android/-/issues/3460

Hope it helps, PW
[Magisk] ipdev:
Looking a bit more into the errors.

I found an odd reference to the Bluetooth error.

Clear PlayStore cache and data.​

Not sure if it will help but, maybe just try wiping the cache and data of microG core after installing Magisk.

¯\_(ツ)_/¯

Cheers. :cowboy:
[Magisk] Philnicolls89:
Yes I have previously tried all of the above mentioned methods of hiding root detection.

I have tried both momohider module and riru-unshare module both with no success, I've attached the results from magisk Detector and momo app (momo still detects traces of root eg, magisk, twrp, bootloader etc, so the app I'm trying to use may be doing the same thing).

The app does not use VGDRM Helper service as seen in screenshot.

It does not seem to be a widevine issue either as my security level is L1.

Unfortunately I think I'm back to square 1 with this, you have definitely given me some tips and things to think about though in my ongoing quest to get a streaming app to work that I barely use anyway😅.

Thank your the time to provide this information for me, it's been an interesting and enlightening read at least. 😁
[Magisk] 73sydney:
Did you use Momohider with any options enabled? (empty files under /data/adb/modules/riru_momohider/config)

see https://github.com/canyie/Riru-MomoHider under "Background"

Have you tried looking for and removing the TWRP folder on internal memory? (making sure to copy any backups off device if present first)

fwiw, Momo detects most of the same stuff for me, although all my root detector hungry apps still dont find root - always been this way...i dont have 100% faith in Momo as a result

your Magisk Detector results look correct, same as mine (i use Riru-Momohider)
[Magisk] Philnicolls89:
Yes, I have all 4 options enabled in momohider (creating a blank file and placing it in /data/adb/modules/riru_momohider/config)

The only thing I can think of that I haven't tried is what you suggested, which is to rename or remove all files with magisk or TWRP in the name.

That seems like a lot of trouble for one rouge app that refuses to work!! Seeing as I didn't use it often when it was working.

I agree with not being able to entirely trust momos results either, as all of my root consious apps still work fine (of course with this one exception!)
[Magisk] j0110:
What is the current status of development of Zygisk ?

Is there an official repo hosting it ?
[Magisk] zgfg:
TJW works on Zygisk (did a lot of commits so far) on his Magisk Github project but he has not released a new Magisk (Canary or so) yet

However, there are other developers who branched his code and already deployed new Magisk builds with Zygisk - it's been discussed here a lot, particularly there are lot of users here using Magisk Alpha (from vvb2060).

I'm currently on the Magisk from TheHitMan7.

Both have Zygisk (based on commits from TJW)

And you don't nneed a module for Zygisk, it's in the new Magisk (core)
[Magisk] zgfg:
Testing today the new TheHitMan7 build 7b5f065e from t.me/custommagisk (not released yet to Github)

WebView is fixed now in this build

However, seems it doesn't support Riru
[Magisk] rodken:
How are you fairing with the version from 'TheHitMan7' versus the version from 'vvb2060'?
[Magisk] rogers11:
Hello, my Pixel 4a with LOS 18.1 got android-11_r46 today and now SafetyNet does not pass anymore (Magisk 23, Riru 26, USNF 2.1.1), ctsProfile fails. Is there anything else I have to install now?
[Magisk] rodken:
You would need to do your due diligence and perform a search utilizing the 'Search This Thread' feature and type in the keys words "ctsProfile".

There are lots of info regarding the do's and dont's of how to regain passage of SafetyNet.