yashsingh1/xdaforums huggingface dataset:
[Magisk] Captain_cookie_200:
i thought since my e fuse is tripped even if i went to non rooted stock integrity will still fail?
[Magisk] Lord Sithek:
out of curiousity - which Knox-backed feature can be regained with Magisk and which module?
[Magisk] Captain_cookie_200:
also for some reason flashing univeral safety net fix somehow made my device think it was in an official state while i was rooted with bootloader unlocked. it was pretty wierd. i was also on an outdated version of firmware and it even tried to software update but failed. (thankgod)
[Magisk] pndwal:
Nah... ROM w/ AVB will run fine again; You just lost their Knox secure partition/folder (whatever their secure enterprise mode data vault is called(?)) and other knox-reliant features as mentioned... I believe it's only stuff (exclusive to Sammy) that corporate players may want or require...

But it'll be fine for running PI strongIntegrity dependant software for general users... PW
[Magisk] Captain_cookie_200:
oh. thats great.
[Magisk] pndwal:
Not exactly sure what you mean, but basically 'official states', ie. Compatibility Test Suite compliance etc, are what USNF is supposed to spoof!? 🤔 PW
[Magisk] Captain_cookie_200:
i have no idea. but my device thought it wasnt tempered with. (i am pretty sure knox features still wont work) it tried to OTA update etc.
[Magisk] pndwal:
They won't, as I said...

Actually it seems you may have lost some Sammy features in addition to 'corporate' ones incl. Samsung Pay... See this:

What happens if I root my device that is running a Knox service?

https://docs.samsungknox.com/admin/knox-platform-for-enterprise/faqs/faq-115013719548.htm

I think that can happen simply by rooting... Hence John's 'OTA Upgrade Guides' doc says:

https://github.com/topjohnwu/Magisk/blob/master/docs/ota.md#prerequisites

👀 PW
[Magisk] 73sydney:
Samsung Health - up until about 3 weeks ago, i had a long time "fix" for it, but that stopped working. Then another member here found talk of a new way to cheat it. I packaged that up as a magisk module, which is linked in my signature, or here:

GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices

Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...

github.com

all the active code is in just the install.sh file

SamsungHealthSecurityProps/install.sh at main · stylemessiah/SamsungHealthSecurityProps

Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted devices - SamsungHealthSecurityProps/install.sh at main · stylemessiah/SamsungHealthSecurityProps

github.com

It removes (systemlessly of course, so its reversible) a security key type from /vendor/build.prop (if it finds it exists). At time of writing no side effects have been noted. Tested by me personally on stock Samsung ROM, slightly debloated (custom?) stock ROM (BeyondROM for my S20+), and android 13 GSI, and tested by others.

Myself and Dante63 of Samsung Health Monitor (reversing for Watch 4/5) fame had been looking into reversing Samsung Health, but it was (and is) slow going. So this "fix" was timely, because i like being able to fully use my Watch 4 for tracking
[Magisk] 73sydney:
Yup Samsung Pay and Secure Folder go bye byes....i never used the latter in all my years...i did use Samsung Pay on my Active 2 back when my bank didnt support GPay...this was on my Pixel mind you, where Samsung Pay didnt care because it wasnt a Samsung device and that it was rooted (it very much cares when youre on a rooted Samsung device though)
[Magisk] 73sydney:
Nope, my S20+ 5G is hella fuse tripped, like from the moment i got it, *i bank on it every day like a king with Google Pay. The only untripped/unrooted device i own is my Watch 4...and the day isnt far off probably till thats got root availability

* No GPay Magisk module needed :)
[Magisk] Captain_cookie_200:
i never used Gpay in my life nor samsung pay. so i think i am fine
[Magisk] Captain_cookie_200:
wow- it failed anyways. sometimes it did brick itself but i was done with one ui for this phone anyways
[Magisk] badabing2003:
For heaven's sake I only have a handful of posts in this thread.

The last I checked you can turn of signature display,

Yeah, I'm detracting people asking questions because I'm asking a relevant question? in 53k + posts thread?

To answer my questions they don't have to be active developers, they just have to be knowledgeable (and courteous) which most are.

Care to suggest which device development thread I should post Magisk questions (which is not a device by the way), take a look where this thread is under.

I get it, you don't like me, that's fine, you don't have to, I see that you get irritated easily, I'm not hijacking the thread, unlike endless other discussions.

Please ignore me and my posts, just like I will to you, and if you see me violating any forum rules, please bring it up to the attention of forum moderators, all I'm trying to do is learn and help the best way I can.
[Magisk] badabing2003:
Hope you're right, but I'm seeing useless apps checking for root.

Can you guess what app is this?

Hint, it's not a bank app ;)
[Magisk] Captain_cookie_200:
even my stupid chinese unsecure filled with ads camera app detects root. although i was able to bypass it somehow. i am running a gsi that passes safety net automatically once i use shamiko to hide magisk from play services. all apps do not detect root and run fine now
[Magisk] grep_i:
And I'm still the lucky guy none of the safetynet updates came my way so everything still works.

But I'm not using Magisk yet.
[Magisk] Captain_Throwback:
Then I don't understand why your comment is here in the Magisk thread? :confused:

It seems Magisk is what's being detected (somehow).
[Magisk] Triviox:
Delete
[Magisk] D4UN7L355:
Having trouble uninstalling magisk. I have magisk uninstaller 20161004 and all it does is remove v8. I still see v7 in the manager. I'm on an N6P with suhide .55 Xposed 86.2 chain fires sr1 root. Systemless. MM 6.0.1 Any help would be appreciated.
[Magisk] Apexpredator12:
I am having a bit of a problem I tried to install the latest Magisk and followed instructions completely, but it gets to the samgung screen and just stays there, Im on MM Galaxy s6 G920F
[Magisk] htko89:
I just wanted to add that I had bootloops on nexus 6p coming from v7 magisk into v8 magisk. Did not realize it was magisk at the moment but my phone worked after I flashed the boot.img from the nexus factory images google website that corresponds to my build and device. I also flashed system.img but I didn't really have to. The explanation is here:

I suggest [MENTION=4470081]topjohnwu[/MENTION] to add a warning to those wishing to update. Many people depend on their phone for work and this put my phone out of order for a few days.
[Magisk] rgawenda:
Which doesn't take much effort as magiskhide only deals with mounts, but Google just needs to read the result of "getprop magisk.version"
[Magisk] hokiealumnus:
Confirmed. Had to fully uninstall magisk to pass safety net on vs985, cm 14.1 based ROM. It has been working a good two weeks with magisk hide and phh. Guess they finally caught on. Sigh.
[Magisk] DeadlyByNite:
Well I need Magisk for the XSetProp module. Without it ro.boot.verifiedbootstate won't be green to let me pass SN. Magisk is still very young, and I believe that there are many great active devs hanging around this thread to find a workaround. Until then I can do without any apps that use SN.
[Magisk] lonewy2005:
Dear Little Nugget,

I am happy to see some samsung device is finally working.

I have tried the same method on my TMobile Galaxy Note 4 with Stock rom, but xposed didn't work after disabling it from root switch. May I know what rom exactly are you on? I think that is the only difference.

Thanks!
[Magisk] G U C C I:
Can confirm safteynet was updated. At about 5pm EST I was playing Pokemon GO just fine and at about 7pm when I went to play again, I failed safteynet so the update must have been pushed somewhere near there. Hopefully a fix can be found soon! :)
[Magisk] taller238:
Hi, I encountered the same problem but on Sprint Note 3 - magisk hide cannot be enabled.

Could you suggest where you got the modified kernel "RamKernel v1"? Does it apply to my Note 3?

And why this can fix the issue?

Thanks!
[Magisk] topjohnwu:
Dang!!!

I have been doing some updates to Magisk to fix issues and prepare for multirom support, with some quite significant changes. One thing I did is a complete rewrite of magiskhide.

However, our mighty Google decide to screw me, they updated the detection method just before I finish the refactor.......literally!!

Right now I can't even find what Safety Net is detecting, it'll take me more time to investigate. However next week is my midterm. Crap.

:eek::eek::eek:

I think I'll release this maintenance update regardless whether SN is bypassed or not.

After the exams I'll start finalizing and push out the multirom update!
[Magisk] DeadlyByNite:
I have successfully got safety net to pass with Magisk v8, Xposed 86.2, SuperSU 2.78-SR2, suhide 0.55, and RootSwitch 1.3.3.2. This is what I did...

- from a clean install (I use CM 13)

- flash SuperSU 2.78-SR2

- Then I booted into CM 13, deleted /system/bin/su

- Reboot to TWRP, deleted /system/xbin/su (it wouldn't let me delete unless I was in TWRP)

- Flashed Systemless Xposed 86.2 and suhide 0.55

- Reboot into CM 13 and install RootSwitch 1.3.3.2 and Magisk Manager. Magisk said I don't have latest Magisk installed when I opened it so it asked to install it, I tapped yes and reboot

- Then flashed XSetProp rebooted to CM 13

- Open Xposed and installed No Device Check module, activated it, and rebooted

- When I checked SN it was showing a blue screen so I opened RootSwitch and ticked stop all su daemons and then disabled root, and SN passed with a beautiful green screen.
[Magisk] mathy007:
I think that's the right decision for now let SN be focus on other important issues with bugs and fixes for magisk and multi ROM support, with Google involved it's a cat and mouse race
[Magisk] ert69:
Thats cool but a) wouldnt magisk overwrite chainfire root and b) what about people who are on CM14.1? There is no Xposed SDK24 yet.
[Magisk] DeadlyByNite:
It says that the latest Magisk is built to be compatible with SuperSU. It's in OP. Magisk won't have to edit boot partition if SuperSU is installed, and Magisk even adds a script to survive updates of SuperSU from what I understand. This is just what I have found from experimenting, and I don't have a device that has Android N SDK24 yet so this would just be a guide for those who are still on MM only.
[Magisk] mathy007:
Can you send me the Xposed 86.2 can't find a link to get it now
[Magisk] ert69:
I see, cool. I guess I'll wait 2 weeks till magisk gets updated then.
[Magisk] DeadlyByNite:
Here is the only link I can find for it. Hopefully it works for you.

http://xdaforums.com/attachment.php?attachmentid=3897543&d=1475913773
[Magisk] wugga3:
Still haven't gotten the stupid weather network app to work with root... Don't use payment apps but 2 big bank apps and one payroll app all still work so I'll stick to OnePlus weather app lol

Edits:. OnePlus gets me the Weather Channel... so good enough ...
[Magisk] Captain_cookie_200:
weather.... looks like soon every calculator app will not run on rooted devices anymore..
[Magisk] zgfg:
Huawei AI Life for BT headset also complains about root - but can be easily tricked
[Magisk] pndwal:
Different story that, but does make the subset bigger...

mymaccas?, Some game? Controller app for your smart washing machine etc?

www.twitter.com/topjohnwu/status/1381735155044249601

... Or wanna Join John's magisk Slack group?

This:

www.twitter.com/topjohnwu/status/1440764583589728264

-------​

www.twitter.com/topjohnwu/status/1277683005843111936

www.twitter.com/topjohnwu/status/1445598606346444807

😝 PW
[Magisk] badabing2003:
The Weather Network - Apps on Google Play

Local weather forecasts, storm alerts, weather radar maps, news & video, widgets

play.google.com

I can't I'm on a rooted phone ;)
[Magisk] pndwal:
That's the point... He wants you there if you can crack it... Just like maccas do... 😋

Give the weather app a crack... PW
[Magisk] adfree:
I can confirm GW4 SM-R870 is rooted with help of Magisk Version 25.2...

Firmware GVH2...

And since few hours I realized I have write access to /system

https://xdaforums.com/t/firmware-an...-csc-change-and.4323469/page-27#post-87541353

Still not solved to bypass netOdin Security Check:

Rooting Galaxy Watch4

I've unlocked bootloader, got boot.img(hashes match in update.zip and my boot.img + it boots fine), patched it and vbmeta in tar by magisk 24.3, but when i flash new boot.img, it throws me "SECURE FAILED: BOOT" error on watch and system doesn't...

xdaforums.com

I have only success with attached USB cable... and Odin.

Maybe somebody could help to solve the riddle about

wirelessd

In recovery.img

Magisk for instance delete during patching the text stringS:

SignerVer03

In Footer...

Only SEANDROIDENFORCE textstring is still inside...

But all other Samsung crap like user frp mrk is erased...

Please help.

Thanx in advance.

Best Regards
[Magisk] 73sydney:
never said i "didnt like you" thats a construct thats been chosen to create conflict. Read my comments again, ive argued the points/topic, not the person, as i always do. Im an emotionless robot with aspergers, i literally dont care what people think of me and i dont attribute emotions to things others do, because its an absolute waste of my brain cycles to employ emotions for non-critical things that are in most cases (on here) niche or arbitrary to me in my larger life. If others chose to dwell on things and get a dose of red mist, thats a personal choice that cant be attributed to me

Taking things personally, thats a conscious choice, lets make that crystal clear right now....

ive said my piece and objected at the hijacking the thread (yet again) for a particular members software purposes, i dont believe this is the place for it, and this is being proven (again) by:

a) creating more off topic posts

b) introducing drama that doesnt exist or need to, to top things off

c) issuing "gotcha" statements

Everything spoken about could be handled via PM to those people who think can asisst...i have to carry on PM convos because theyre not germaine to the topics of threads in im, i have one PM thread 27 pages long discussing things we have had purged from this thread and others for not being on topic.

My suggestion, which i use myself, is if you want to develop software, create a thread/PM thread for it, and invite the people you think can help you from here on that thread by tagging them, or create a PM thread with them. Thats how i often rope people into helping me with things...even the mighty didgeridoohan has given up his time to come and respond to a thread/PM thread he's been tagged in on more than a 1,000 occasions by someone (a few times by me) developing something magisk related. Why do you think this doesnt apply in this instance? i dont get it, its good enough for everyone else to use that tagging paradigm and either create a targetted thread or PM thread

You seem to have spent a lot of time trying to make it personal....when it wasnt and doesnt need to be

Im personally tired of pointing out the bleeding obvious, this is not a dev thread, and its not designed for someone to hijack multiple times to write their own software. Period. I dont understand how thats not obvious or getting lost in translation somehow....

Notice i didnt use the word you once.....dont make it personal.....

p.s. i shouldnt have to turn off everyones signature display just because over and over it can be overwhelming with a graphic in it,and ideally, i dont like to ignore people, you really have to get on my nerves to be on that list. Id personally like to see where your software ends up, but in its own thread...
[Magisk] 73sydney:
I have been watching your progress and your bravery at hacking the Watch, and sacrificing one

Thats a younger mans game, and i like to be blissfully aware of the inner workings, but ready to heap praise on when you finally nail it
[Magisk] zgfg:
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com
[Magisk] 73sydney:
Exactly, why is it spread over here...
[Magisk] pndwal:
Mate, it wasn't a development question!... Legitimate query re. generated patch files having the wrong sha1 md5 and Magisk possibly using the wrong boot image files (other than user selected) in the Magisk download folder, or potentially the wrong backup images from /data/magisk_backup_xxxx folder...

... Here he continues tests using Magisk App UI:

Clearly this discovery may have sprung from Pixel Flasher testing, but reveals potential serious underlying bugs in Magisk code...

Other posts indicate that this may be connected with other user's issues with backup files generated/used... I'm guessing if Magisk can pick up incorrect files from Download folder also, some unsolved issues may also be indicated here...

This may be a complex issue but is potentially a serious one we may all benefit from a resolution to.

Further, issues like this may never be solved without dev interaction with userbase like this... I see this as a positive thing!...

... But wouldn't some dev interaction, esp. some from the LSP associated Devs who's Magisk contributions are prolific, be a good thing?... Don't these very dev's often simply shut down issues without explanation or user interaction even in GitHub issues resulting in these simply being shelved/ignored/simply accepted?... And Oh how I wish they'd simply show a modicum of respect for the general Magisk user base/community, let alone poll for some user input on issues here...

... And I don't see such development happening, or dev-related questions in this case at all... That's a s t r e t c h...

I'd like to say 'keep it up' to any experienced Devs who ask questions here, especially those who also contribute positively like @badabing2003... We don't have nearly enough... And let's be careful not to alienate them... 🙃 PW
[Magisk] Captain_cookie_200:
i just installed to see it. And yep there it was. Although i bypassed it. i am using shamiko and i added this app to denylist and rebooted. I dont see the root warning anymore.
[Magisk] badabing2003:
Yes, it passes for me too even without Shamiko, by just adding to Magisk denylist.

The concern being for now, and for how long before even unimportant apps start checking for meeting strong integrity.
[Magisk] Captain_cookie_200:
yeah ... soon lock screens are gonna start checking for root too? 🤔
[Magisk] 73sydney:
This isnt a dev/support thread for a users software, which is what it feels like....thats my objection

all i have to say on it, ill just ignore him and shake my head at having to do that.....worth pointing out the only people on my ignore list are 2 trolls you know about.....but i guess thread breaking is normal now
[Magisk] pndwal:
Sorry mate, but I simply haven't seen any evidence of what you're asserting on this one... Can you please tell me what queries were made relating to development of said utility?...

As for the issues touched on that I'm aware of, I'd be happy to see any possibility that Magisk is mishandling backup images for restoring unrooted system or mishandling downloaded images for patching or perhaps failing to create backups at all, eliminated...

I don't want to see either users of a 'Pixel Flasher' utility affected by any buggy Magisk code or those using Magisk's UI, and I dare say that goes for most...

That's why I think these issues are potentially quite important and I have no issue with the original clearly stated reason for posting here:

... I might be pedantic and point out that Magisk Manager has been dead since v22.0, but the well intentioned purpose here is not only clear as far as I'm concerned, it's also a perfect example of protocol being followed as this thread is top-of-list of "XDA Community Support - Please ask and answer questions here" link

https://xdaforums.com/f/magisk.5903/

suggested by John in New Issues page...

I think it's great to see an experienced dev take the lead here; might make some 'needy' users who don't bother to read before they make dumb GitHub issues adjust their behaviour... or pigs will fly...

Personally I haven't seen any posts I'd add to an Ignore / Irrelevant / shake head list, or that fall outside the general spirit of the conversation in this thread... Sorry (once again)... PW
[Magisk] Stillhard:
Nice, now everyone can do the same trick(s)?

I need my Ponkles back
[Magisk] pndwal:
Wot twiks? PW

... Perspective is a funny thing...
[Magisk] HippoMan:
Yes, of course it's Devs and not Google who are increasingly creating their apps to be non-functional or crippled in rooted/modded environments. I never tried to assert otherwise. And of course the Devs have the right to do so.

These Devs are using tools for this (mainly but not exclusively supplied by Google) which are more and more difficult to thwart. As time goes on, we have to deal with more convoluted complexity and thereby suffer more headaches and bootloops in trying to hide root and modding from this increasingly sophisticated root-and-modding-detection software.

And for many of us, the "(small) subset" of apps in this category happens to contain some programs that we consider to be desirable and important. And this subset continues to grow.

The result of this is that we users who want rooted devices are having to deal with increasing complexity and headaches in using and maintaining our devices as time goes on.

There is no end in sight for this trend, and that's the point I'm trying to make.
[Magisk] rocketda7331:
I made a dum-dum and tried editing some files in /odm/etc/ I should not have and now magisk and its modules have issues related to /vendor/ folder. With viper4android enabled the phone wont boot and I checked the module has /vendor/lib/.... modifications. Oneplus 48MP camera enabler does not work either and that also makes changes to /vendor/ folder.

I looked through logs and I can see these two lines that seem relevant(the rest of magisk log is basically successfully doing everything else):

01-25 02:19:23.810 726 728 E : mount /dev/ihNk06/.magisk/block/vendor->/dev/ihNk06/.magisk/mirror/vendor failed with 6: No such device or address

....

01-25 02:19:23.929 726 728 E : lstat /dev/ihNk06/.magisk/mirror/vendor/lib64/hw/com.qti.chi.override.so failed with 2: No such file or directory

the last line is related to the camera mod. Anyways - magisk doesn't seem to be able to "find" /vendor anymore. What do?
[Magisk] pndwal:
Simply dirty flashing full ROM should restore system setup...

Be aware that fastboot ROMs are more complete than recovery ones and I'm not sure which you need to restore affected structures...

Next you'll need to flash Magisk again per method for initial installation for your device as boot image w/ Magisk will be overwritten...

🙂 PW
[Magisk] rocketda7331:
I don't use fastboot rom, I have Lineageos 19 installed on OnePlus 8T.

I will try dirty flashing ROM and magisk again.

e:

The issue persists. Dirty flash + reboot to system. Confirmed magisk is not enabled - reinstall. Reboot. Same errors in logs.
[Magisk] pndwal:
I have no idea if LOS recovery ROM includes /odm (files from Original Device Manufacturer)... Guess if it doesn't work you could restore latest stock, then migrate back to LOS... You will likely be able to flash just /odm from stock fastboot ROM however... PW
[Magisk] rocketda7331:
I extracted LOS payload and saw that they do have these files. However dirty flashing LOS on its own did not fix that issue.