yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 Guides, News, & Discussion] penguinthatflew:
Oreo workaround

Hey guys,

Just wanted to post at least the way I have managed to gain a similar result as this method on Android 8.0 Oreo.

*Note*

I have only tested this on a Galaxy S8+ unlocked.

This method assumes you already have the apps installed for your new gesture keys that are explained in the original post of this thread and have cloned it successfully.

There is a small fee to this method but I can't for the life of me find another way.

This method may be out there already somewhere but I couldn't find it or at least find instructions for someone like me.

*Method*

Ok so first you will need to install the following apps on your device:

Substratum

https://play.google.com/store/apps/details?id=projekt.substratum&hl=en
​

Andromeda

https://play.google.com/store/apps/details?id=projekt.andromeda&hl=en
​

[Substratum] Samsung System Mods

https://play.google.com/store/apps/details?id=substratum.draco.systemmods&hl=en​

Immersive - Low-Level Immersive Mode

https://play.google.com/store/apps/details?id=com.draco.immersive&hl=en​

You will get a red box when opening andromeda but this is fine, I will explain this in a bit.

Next open the immersive app and enable immersive full from within it. (Note you will have to go onto a computer to run the adb command from within cmd.exe. Just type it as it tells you to)

Once you have done this, open Andromeda. A red box should appear. Go back onto your computer and install the appropriate program for your machine from step one of this thread "https://xdaforums.com/apps/substratum/andromeda-desktop-clients-release-notes-t3668682"

Extract the downloaded file and open the readme.txt file. Plug your device into your computer. Then click on the "start_andromeda" file, run it then hit any key.

Return to your device and substratum should open fine. The andromeda desktop client should connect fine and you should get a green box when checking the status. Substratum will then reopen and you should see the samsung system mods as a black box option upon launch.

Click on the system mods option. Scroll down to the orange system ui and toggle the check box on the right. Then click the down arrow below it and search for "Oreo (S8) Narrow Nav" Click this. Then click the grey circle at the bottom right and select "build and enable".

Once you have done this go back within the app. Click "manager" at the bottom and then select the check box next to the narrow nav overlay you just "built". Click the grey circle again and choose "enable selected".

I have been faffing around with methods for hours now so I don't know if it is required to restart your phone but I did and it seems to be working fine. Hey now I seem to have the hard press function back over the original method in this thread.

Sorry if my instructions aren't clear but this is my first time at this. If you need a hand I'll be more than happy to try and help but to be honest I was so excited to get this to work after hours of experimenting.
[Samsung Galaxy S8 Guides, News, & Discussion] Parsonsowen27:
Thank you so much for sharing this! I will have to try it once I get home. So I imagine this gives the exact effect/function that this current method has but has the benefit of the hard press? Sounds even better! Does the phone need to be rooted? My S8 isn't rooted atm and the current method works so I imagine you wouldn't?
[Samsung Galaxy S8 Guides, News, & Discussion] penguinthatflew:
No this doesn't require a root. There are ways to do it with a root all over the internet I found but doing it without a root was my priority. To be honest, the hard press isn't anything to write home about. Haven't really found a use for it yet. Only difference I can see is that when opening the keyboard there is a more white space at the bottom as oppose to the more "keyboard coloured?" space of the current nougat method. Also seems to be a bit more clunky trying to back off the keyboard but I'm sure that can be figured out.

By all means though, I do not recommend upgrading to android 8.0 to use this method. I feel the current one listed in this thread is far easier to do and more finished as a result. I hope with time this method can be improved. Please let me know if it works and if you have any suggestions for improvement!
[Samsung Galaxy S8 Guides, News, & Discussion] josezr:
This process is permanent or I have to do the process

Every time when I reboot the phone?
[Samsung Galaxy S8 Guides, News, & Discussion] penguinthatflew:
No once you do it its all set. I created a new thread for this method to avoid any confusion. https://xdaforums.com/galaxy-s8/how...d-8-0-root-t3770895/post76069541#post76069541
[Sony Ericsson Xperia Neo, Pro] :
Hello , I am a Noob ,

I have a few questions ,

My Device

Xperia Neo V

MT11i

Android Version:

2.3.4

Build:

4.0.2.A.0.62

Kernel:

2.6.32.9.-perf ....... [did not write the entire thing]

I never updated it ,

Now , I want

1.Make a Complete Recoverable Backup of my Current OS (2.3.4)

backup my original firmware , and stock OS . So that if in future i want to go back to it , i can just use that to go back . (i hope i am able to make you guys understand)

As far as my knowledge goes , i should need TWRP Recovery , or CWM Recovery or something similar . Correct me if i am wrong .

2.Unlock the Boot-loader and Root it.

3.Install Last Officially available update , Manually and Try it out

Which is the last officially updated version available ?

4.If i Like it then OK , if not then

i will Install other Custom ROMs or CM13

Q1. i heard that Many Custom ROMs dont have FM and Camera Functions ?

Which Custom ROM has all the functionality as the Stock One ?

and is based on most updated version of android ?

5.KERNEL.

I just CANT understand this one , please help me understand it

Does any of the above need the kernel to be replaced ? by some other kernel ?

I dont have much knowledge of kernel

...................................

Other Questions:

1.Why we are Flashing both .562 kernel .587 kernel one by one ?

Shouldn't we need only one ?

2. Can i update to Latest ICS via PC Companion and then root it ?

Will it affect anything ?

3.

Quote:

Disadvantages

1. Warranty is void..gone.. ---------- No Problem

2. You cannot update using PCC or SUES( if you try them..then u'll get a message saying that the software is modified and it wont proceed) ---------- No Problem since no update will come in future

3. No more DRM(Digital Rights Management)..things like Trackid, music like..etc - I like TrackID , but TrackID works with any mobile isnt it ? so what will change ? in Track ID ?

And which Custom ROMs require Unlocked Bootloader ?

Does CM Require it ?

Please help how can i do these and please educate me about kernel too .

P.S.

I tried posting this before in the [NEO/V/L Q and A THREAD]HELP THREAD (N00B friendly) Thread but No One Replied

Very Sorry i posted it here

i already tried the other place

https://xdaforums.com/xperia-neo/help/xperia-neo-questions-please-answer-t3658062
[Sony Ericsson Xperia Neo, Pro] veloo:
did you find any of the answers? i have just been handed down this phone, and i seem to have the same questions as you..
[Sony Ericsson Xperia Neo, Pro] Iqbal Ansari:
Are people still using this phone in 2018?

Thats great!
[Sony Ericsson Xperia Neo, Pro] veloo:
i guess not :/ probably why i got this handed down
[Sony Ericsson Xperia Neo, Pro] Iqbal Ansari:
Yeah I had the Xperia pro 5 years back and it was laggy as hell then and I can only wonder how laggy it would be now.
[Magisk] :
Has anyone gotten Samsung Pay to work with Magisk? I've got it installed as a gear plugin and safetynet passes. However, somehow Samsung Pay still detects root, even though it's hidden in magisk hide.
[Magisk] davekaz:
Same. Then this droidx program protecting pay app
[Magisk] candiesdoodle:
Try the universal safteynet net module
[Magisk] grymkmb:
Is your Knox tripped? Samsung Pay might check that independently of the root-status of your phone.
[Magisk] hkbladelawhk:
I'm on an LG
[Magisk] sevenday4:
I've got the same issue with galaxy tab 3

I got warranty bit warning was showing on the boot screen, so I'm pretty sure I triggered Knox. The reason I was using magisk was to prevent this issue, but I guess Google figured out how to detect its presence. I downloaded a fresh copy of the firmware, which will cause Knox to reset but it also factory resets the tablet. I will still use magisk on my new s8+ phone. I hope magisk will work more effectively to where I can use exposed and its modules. After jellybean, magisk wasn't able to allow exposed to be used because of the way Android sets up its environment to execute apps. Hopefully soon a work around will be accomplished especially since Oreo is coming to my two devices by the end of the year, I guess if not sooner. :D
[Magisk] vooks:
Same problem here; Magisk works but Samsung pay won't work
[Magisk] hkbladelawhk:
Even tried freezing magisk. Though still no go must be detecting something.
[Magisk] alexbelgium:
I tried the same thing but couldn't make it work. I think it is due to the fact that the "System Status" is custom (or modified) since magisk modifies the "boot" partition, and that you probably installed a custom recovery to install magisk. That's why OTA also don't work without first flashing back the original boot and recovery images. I don't have an LG to verify that the "System Status" appears on those.

If it does, what could be tried is to install xposed and a module that fakes the system status (if you've got marshmallow or before)

Sorry, once knox is tripped there is no going back. However, installing Magisk fools the phone into thinking knox is still untriggerred (0x0). By reflashing the original firmware, what you did is restore the "boot" partition that was modified by magisk. By doing that, your phone should get back its "official status", allowing OTA. However, Knox will stay tripped. Anyway, Knox does little... and is only used by samsung softwares.
[Magisk] Iradj:
There is nothing that we can do about it because Samsung Pay checks the tripped status on kernel level so it's impossible.
[Magisk] hkbladelawhk:
Booo!
[Magisk] Schuan:
someone please made an apps that can hide or fake the Knox status.
[Magisk] filjusz:
This is possible by disabling safetynet check at boot level before compiling the kernel
[Magisk] gghose:
Does this apply for non-Samsung phones? I understand that Knox has a tripped flag, but on a non-Samsung phone, what exactly is "tripped"? As with everyone else, I'm pretty frustrated that I still can't use Samsung pay, even on a phone that passes safety checks and has MagiskHide.
[Magisk] Yeti47:
Works for me on a Samsung phone, after hide I just had to rename all busybox exe's.
[Magisk] dcbii:
Doesn't work for me on a OnePlus 3T, OOS 4.1.7, rooted with Magisk 14.0. This stopped working after the Samsung Pay (Gear version) was updated right around August 21st. Maybe I'm just missing one or more binaries or apps that still must be hidden. I don't have any busybox apps installed, though I previously did, and I removed the busybox binaries where I knew to find them. Maybe it's detecting Magisk's su install, or some other binary I still need to remove. SafetyNet passes just fine, and I can use AndroidPay and CapitalOneWallet on the phone, but I can't use the SPay tab in the Gear app without getting the "rooted phone" message.
[Magisk] menkent:
Magisk hide 14

Hi Yeti47: I have a samsung galaxy s8 sm-g950f. It is rooted wit renovate ice and magisk 14. What modules I have to check in magisk hide to make samsung pay working? Please answer me in menkent33@gmail.com. Thank you so much. Bye.
[Magisk] dcbii:
Finally solved it. Busybox can be installed in /data/local, apart from /system/xbin or /system/bin. Samsung Pay will find it there. After I removed it, I was able to get Samsung Pay (Gear Version) working again on my OnePlus 3T.
[Magisk] jknaggs:
Spot on fella, just got it working on OP5 with lineage ROM.
[Magisk] schmaltzy:
Root explorer won't let me remove it from xbin. How exactly did you do it?
[Magisk] Phreaker47:
Just came to report this! Confirmed here too. At least, I got past the initial welcome screen, so it must be working! Woohoo!
[Magisk] Tripledrop:
Works perfectly for me with 17.2!
[Magisk] driverdis:
17.2 fixed spay, preciously I had to add cards via a bug that I found that allowed me to add cards anyway despite the unauthorized message nagware and use them on my gear S3 as long as I never opened the spay app again (or it would disable it on the S3). Now I can actually check my purchase history and use the Samsung Rewards I have stacked up from never being able to use the app.
[Magisk] rockingondrums:
Care to share that process? This is bound to happen again.
[Magisk] TheUndertaker21:
17.2 doesn't work on stock rooted note 9

It doesn't work on any custom roms eieher

Except one gsi one. A pixel experience pie rom.

Root is detected.

Here's the log.

Maybe someone can help me.

Thanks

View attachment com.samsung.android.samsungpay.gear.log
[Magisk] driverdis:
Probably, just as likely as Samsung fixing this bug I (and probably others) found.

BTW, I am running Samsung Pay on a non Samsung phone via the Gear app, I don't know if this works on a legit Samsung Phone.

The bug has to do with being able to navigate the menus really fast in-between the error messages that force close the app.

Basically, clear data then start fresh on Samsung Pay.

Open Samsung Pay then very fast click on login, the login should pop up despite the root message. Login to the app.

Next, launch Samsung Pay and try to browse quickly to the add card screen where you scan your card. Let it sit there not scanning anything and with the error message still there.

Now just wait until it gives up and goes to have you hand type the card, which surprisingly lets you type the card in and verify it with the bank with no root messages.

When you get to the page where you press done or to add a new card, be careful as adding a new card can trigger the message again and require you to start over with the process or getting to the scan card screen.

For pressing done, do that then quickly exit the app via the home button or the recents button and quit Samsung Pay. That should allow the cards to be added to the watch and function.

If you accidentally open Samsung Pay, it will trip the check and block the watch from making payments until you add a new card using the above method then pressing done which resets that on the watch.
[Magisk] rockingondrums:
I really don't have any knowledge on this but I took a look to compare against my previous logs. Mine just listed Magisk repeatedly. I see your log lists a /data/su directory. Does the ROM have it's own inbuilt su option? If so, maybe that directory is part of the ROM and that's a way the Samsung app checks?

I was thinking about this recently: the older CM App Ops would feed a blank or null value to apps if the permission was revoked. I wonder how Lineage handles it now. I revoked Storage Permissions with Pie inbuilt function and that doesn't work. Galaxy Wear app won't even stay open in that case. But if it could be fed a spoofed internal storage directory/file readout, I think it would pass.

If someone wants to test, that'd be cool. I'm also kicking around the idea of trying Lineage out, but I may not get around to it for awhile.
[Magisk] TheUndertaker21:
Hope someone have a look at my logs.

This is the same issue with every roms I tried except one.

I think all of them flashed some type of su in other to boot up.
[Magisk] Phreaker47:
Yes, and there is also /sbin/.core/img/.core/hidelist

Just guessing, but is that a previously used Magisk Hide directory, or maybe, some other "hide my root" app dir? Either way, it must be something leftover that Magisk 17.2 is not using. Someone more knowledgeable should confirm, but it's likely those two should be deleted.

Maybe the best solution is:

- TiBU backup

- Full wipe (inc data), clean rom install

- Magisk 17.2

- TiBU restore
[Magisk] Barracuda77777:
Xiaomi Mi6 running omnirom 8.1 with MicroG, had the latest Samsung Pay working with the canary 17.2, then uninstalled it, installed the beta 17.2, hid Samsung pay and everything Samsung, latest Samsung Pay is working with zero issues.
[Magisk] sid8840:
Latest Gear pay plugin and google pay works with 17.2. confirmed!!
[Magisk] olivercervera:
Hope I'm not off topic here... But how did you install Samsung Pay on a non-Samsung device? Did you just take the APK from APKmirror or other stuff is needed?
[Magisk] MrBrady:
On my Pixel 2 XL its the Gear Plugin version that's installed. App doesn't actually appear in the Drawer, but it's accessable from the Samsung Gear App.
[Magisk] olivercervera:
Allright, I don't have a Gear smartwatch. I though it was possible using NFC from the smartphone
[Magisk] Barracuda77777:
very easy, once Magisk is installed, I use Yalp to download gear software, hide it with magisk, then install all the plugins, hide the plugins, then setup and use Samsung Pay.
[Magisk] Phreaker47:
Yeah, people forget sometimes to mention whether they are using a watch or the phone app. Of course with a watch you can use SP on any phone through the galaxy wear app plugin.

There was at least one period of time where the phone version of spay was detecting root while the older gear software never checked. More recently, they've added the check there as well so it's the same battle both ways now.
[Magisk] TheUndertaker21:
hey guys

can someone help me out.

Spay worked fine on GSI roms for note 9

but on stock it kept giving me this error on the gear spay

on GSI roms, you get log on the sd card but on stock there aren't any log

if anyone can help that would be great

i already checked the system

there aren't any busybox or anything like that

no data/su folder either.

View attachment 4605570
[Magisk] TheUndertaker21:
I fixed that issue

on stock

any knox related apps will trigger that stupid message

so it's best to delete them or run a debloat script

i'm good now. on note 9

17.2 rocks
[Magisk] ttabbal:
I got a notification for an update to the s-pay plugin for the Gear S3. It doesn't look to have installed. Anyone installed it to verify? I'm currently on 1.7.3006.
[Magisk] Orka82:
I have the latest version installed (the plugin, watch). With the latest, not official Magisk (kantjer), spay works on my oneplus 3 with Android 8.0. Woho!
[Magisk] sobirin90:
Note 5 Duos spay not working

I'm on latest stock nougat, installed latest magisk, before this I couldn't even get Samsung health to work, but now can by editing the build.prop

Is there any way for me to use the Samsung pay? Help much appreciated as I just started to use Samsung device back. Thanks.
[Magisk] olivercervera:
I'm in the same situation, just got a S9+ after years away from Samsung.

I am using stock ROM + Magisk 17.2.

I have hidden (repackaged) Magisk Manager, and hidden SPay and Spay framework, but I still can't use Samsung Pay: I get blocked at the very beginning saying the device has been modified.

What packages are we missing?
[Magisk] gsmsource:
There are no packages missing, it just doesn't work for Samsung devices. Looks like Samsung is using a different method for detecting "magisk" root.

---------- Post added at 06:01 PM ---------- Previous post was at 05:58 PM ----------

I have an old note edge and if I flash magisk I can't use spay. If I remove magisk it works fine. It's possible Samsung detects TWRP also.
[Magisk] johnp357:
does any one have any updates on this? still not able to trigger pay anymore on my rooted lgv30
[Magisk] koniuu:
I found solution how to add cards to Spay no rooted S7 and Gear S3 (at least working in Sweden)

1.	Connect Gear S3 as a new watch

2.	Open Spay and (with warning) and wait

3.	You will get information that Spay need to be updated on the watch, press ok.

4.	Still wait with opened Spay on the phone.

5.	After updating I do not know why but warning disappears and you can add card.

It is working until Spay is working in background, so up to next restart, but long enough to add a card, after this you can pay witch watch without any problems.
[Magisk] johnp357:
dang.. this really worked... sigh. thanks.

last time the system allowed us to trick it by clicking ok a bunch of times worked only to have it eventually disappeared and fail... hope it holds. thanks again.
[Magisk] ReyStunner:
I had a Nexus 6P before with my S3 Classic and stayed on an older version of spay/gear plugin because everytime I updated it wouldnt let me use samsung pay because the phone is rooted on Android 8.1

I recently moved on to a Pixel 2 XL and said F-it and updated everything. On 17.3 Magisk and Magisk Hide all 4 samsung apps related to gear and sure enough, everything still works. IDK why. My 6P was on the same version of Magisk, both phones are bootloader unlocked running Nitrogen OS (XL 2 @ Android Pie).

Im happy with my results because I was able to add my cards in S-Pay and everything. The only thing im hesitant on is when I open the Spay app on my phone, there is a notification in the settings area for an update to support Gear Sport but its nothing that pops up, I have to go looking for that notification so I can ignore it. Everything is running great, im on the newest Gear app with the battery drain fix so im good.
[Magisk] sobirin90:
So I suppose if we flash magisk uninstaller then our phone can use Samsung pay again?
[Magisk] Minotaur:
I doubt it, unless somehow you got Magisk installed without tripping the Knox counter..
[Magisk] gsmsource:
You will need to flash the original firmware or extract the boot and recovery image from it and flash via odin. There is a tool on the forum that converts the two files into a format odin can recognize.
[Magisk] Peetahs:
this will not untrip Knox. As of now Samsung pay can never be used again on a modified device, even if it is returned to stock condition
[Magisk] gsmsource:
I was under the impression we were still talking about Samsung Gear S3 because if you follow the steps i said earlier spay will work on the Gear s3 even if it doesn't work on the phone.
[Magisk] Peetahs:
ah, my bad. I didn't realize the two worked differently
[Magisk] Minotaur:
I have an S7 Edge with Knox tripped and a Gear S3 Frontier. Even with Magisk installed, I cannot use the latest version of SPay for Gear on the phone as it still detects root/Knox/something. I have to manually install version 1.6.6306 and disable auto updates in order to use SPay on my watch.
[Magisk] tigersaid:
Is there any hope for me?

Galaxy Watch

Rooted Samsung Galaxy s8+ (7.0) with magiska v15

SafetyNet controll both True/Green

Knox void = 0x0.
[Magisk] my370z:
Have you try Magisk 18 and use Magisk hide? It has been working great for my S3 classic with rooted pixel 2 XL.
[Magisk] tigersaid:
I tried last night to upgrade to v18 from v15, I got into a boot loop ? the samsung logo was showing 10 min...

I then managed to downgrade to v15 and now my phone works.

I don't understand why I couldn't upgrade to v18...
[Magisk] my370z:
I've been using Spay since I got my pixel 2 XL in April and always using the latest stable Magisk. So far Magisk 18 is the version work best for hide root. Try to figure out why your phone doesn't work with Magisk 18? By the way, I'm on the latest pie with December security update
[Magisk] Minotaur:
Samsung have other methods of detecting root that Magisk can't cover.

It may well work on a Pixel or another non-Samsung phone, but not on a Samsung phone.

I have a Gear S3 Frontier, and have to use version 1.6.6306 of the Samsung Pay for Gear plugin. All newer versions fail as they still detect that my S7 Edge has been modified, even with latest Magisk installed.
[Magisk] tigersaid:
I want to be on the latest android for my phone and use magisk 18 and to be able to use spay also ?