Database Develop

Magisk General Support / Discussion

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread

Oh wowww. Thanks!!
Error in the thread title: 2015.8.4

Yay it's finally here!
I'm already using it and I must say it works fine

Man, this "universal MultiROM support" left me full of hope. I hope it works out. And it was time for a mods manager on Android, thanks topjohnwu

Working great on my N6!
topjohnwu has my vote for President!
(and a well deserved donation)

AMAZING!, now to be sure, if i have a rom and want to integrate Magisk, the correct order of flashing is:
1-rom
2-magisk
3-modded su (magisk compatible)
it's that the way?

topjohnwu said:
....Magisk Is A Magic Mask to Alter System Systemless-ly.
If you are running custom roms, dirty flash the rom again to remove all possible issues. If the rom includes SuperSU, unzip the boot image from the rom zip, and flash it through TWRP, flashify, fastboot etc. to restore to stock ramdisk......
....... you can now download Magisk and flash to your device.
To remove Magisk, restore your boot image back (Magisk will backup your boot image automatically in /data/stock_boot(md5).img.gz), then delete /data/magisk.img.
Click to expand...
Click to collapse
is the following still applicable in the case of custom roms?
smohanv said:
1. Boot in to TWRP
2. go to Advanced / File Manager and delete folder named supersu
3. go to Advanced / Terminal and enter these two commandsecho SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu​The first one forces systemless, the second prevents /su/xbin_bind from existing.​4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.
5. Reboot device and enjoy systemless
6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".
7. I rebooted in to TWRP and flashed xposed 85.1 (also updated with 85.2 later) and installed the apk (Material design apk from this thread)
8. All done and my xposed works.....
Click to expand...
Click to collapse

Awesome....
Sent from my AO5510 using Tapatalk

Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?

So wait, before i get excited this means things like viper4android can be installed without messing with system?

swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
Click to expand...
Click to collapse
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app

grep_i said:
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.
Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock marshmallow, flashed via twrp, and yes i followed the op correctly. No custom kernel.

swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ��
Click to expand...
Click to collapse
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.

Nezorflame said:
[/COLOR]
Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
Click to expand...
Click to collapse
The threads download section. Should i have downloaded from phhs thread?

swipp3r said:
The threads download section. Should i have downloaded from phhs thread?
Click to expand...
Click to collapse
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.

Nezorflame said:
Nah, you did right, I checked just in case, because thought of it myself. Need the developer's help then.
Click to expand...
Click to collapse
Thanks for trying bro.....

@topjohnwu this new "magisk" method. It doesn't allow Android Pay to work on custom roms like CyanogenMod does it? If I remove SU from CyanogenMod and use your root.

Magisk on (Yu Yureka) ARM64 device
i did a full clean wipe and then flashed rom, magisk and 'Magisk Compatible phh's SuperUser' - in that order. magisk manager app does not open.

Holy crap.. everything universal with support for extensions. This platform could be the beginning of a new era in mods. @topjohnwu amazing work. Don't want to be rude, but personally I think the name of the project is not as awesome as the project itself. "Magisk" sounds a bit cheesy.. :silly:

great work, will try it out soon! one little thing i noticed in the thread title...i guess it should be 2016

Magisk and root

can i flash magisk using twrp and get root?

It worked for me using twrp from https://forum.xda-developers.com/p10/development/recovery-twrp-3-2-1-0-emui-8-0-4-04-2018-t3773449 and magisk 16.0 on oreo firmware.

Quick answer...yes.
On Oreo (VTR-L09C432B360), I installed the 15.4 version from here... https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 (it's for the P10 Plus but works on P10's as well)
You can then update to the latest version (v16) via the Magisk Manager app.
Nougat here... https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151

colthekid said:
Quick answer...yes.
On Oreo (VTR-L09C432B360), I installed the 15.4 version from here... https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 (it's for the P10 Plus but works on P10's as well)
You can then update to the latest version (v16) via the Magisk Manager app.
Nougat here... https://forum.xda-developers.com/p10/how-to/guide-huawei-p10-root-magisk-magisk-t3625151
Click to expand...
Click to collapse
It's doable on any p10's right like I have the dual sim version.
One more question....to get the treble ROM I have to root right?

Those have flashed successfully, did your SafetyNet pass completely? ctsProfile is the only issue I'm having right now

naeemomr said:
It's doable on any p10's right like I have the dual sim version.
One more question....to get the treble ROM I have to root right?
Click to expand...
Click to collapse
Works on all P10's as far as I'm aware. Don't know about Treble, I'm on stock.
MrDanMak said:
Those have flashed successfully, did your SafetyNet pass completely? ctsProfile is the only issue I'm having right now
Click to expand...
Click to collapse
Yes SafetyNet passes fine

colthekid said:
Works on all P10's as far as I'm aware. Don't know about Treble, I'm on stock.
Yes SafetyNet passes fine
Click to expand...
Click to collapse
Damn, didn't work for me. Just the ctsProfile: False issue I'm having. On the B360 firmware using the latest TWRP that works for the P10 as well. Know of anything else I can do to fix this perhaps?

Try Magisk in core only mode and turn on Magisk Hide, other than that I don't know I'm afraid.

-i instaled magisk manager (16)
-patched the original boot parition (you have to untrigger both options in magisk manager..."keep force encryption" "keep AVB 2.0/dm-verity)
-flashed modified boot parition with TWRP
-all OK, safetynet OK

DallasCZ said:
-i instaled magisk manager (16)
-patched the original boot parition (you have to untrigger both options in magisk manager..."keep force encryption" "keep AVB 2.0/dm-verity)
-flashed modified boot parition with TWRP
-all OK, safetynet OK
Click to expand...
Click to collapse
Hi DallasCZ,
May I ask you to be more specific?
I just ordered a P10 and I would like root it with Magisk (I alrady have a Lenovo Tab3 8Plus (TB-8703F) and successfully routed with Magisk (Safety Net check is green))
So, what are the steps? Can I use the original Magisk, or should I use a P10 specific? And how the OTA updates work with the Magisk? Eg.: Do you have to disable it before update? I hope not, since Magisk is systemless and the Oreo ROM is Treble "compatible". Oh, and could you give me a link to a working TWRP, which is compatible with the latest Oreo?
Thanks everything in advance!

So, is it not possible to flash ramdisk without unlocking bootloader?

cesedy said:
So, is it not possible to flash ramdisk without unlocking bootloader?
Click to expand...
Click to collapse
Yes you jave to unlock bootloader first.

Finally I got my phone. Now I'm testing, and getting familiar with it. But after that, I really need some help / advice ...
So my questions are the follows:
If I open the bootloader (no root, no other modifications), will I get OTA updates, and will they work?
Which TWRP is recommended? twrp 3.2.1-0 OREO or TWRP 3.2.1-0 for EMUI 8.0 or another one? What is the difference between the first two?
Can I use the official Magisc? I'm on VTR-L29 8.0.0.360(C432)
And the "really big" question: Is it possible to have OTA updates and Magisk at the same time? If yes, how?

Dexterova said:
Finally I got my phone. Now I'm testing, and getting familiar with it. But after that, I really need some help / advice ...
So my questions are the follows:
If I open the bootloader (no root, no other modifications), will I get OTA updates, and will they work?
Which TWRP is recommended? twrp 3.2.1-0 OREO or TWRP 3.2.1-0 for EMUI 8.0 or another one? What is the difference between the first two?
Can I use the official Magisc? I'm on VTR-L29 8.0.0.360(C432)
And the "really big" question: Is it possible to have OTA updates and Magisk at the same time? If yes, how?
Click to expand...
Click to collapse
Guys, don't bother with answering my question. It seems that Huawei removed the possibility to get unlock code. So, right now it seems I'll never be able to root my device

Dexterova said:
Guys, don't bother with answering my question. It seems that Huawei removed the possibility to get unlock code. So, right now it seems I'll never be able to root my device
Click to expand...
Click to collapse
Apparently you can contact customer service and receive the unlock code after a couple of days.

M1chiel said:
Apparently you can contact customer service and receive the unlock code after a couple of days.
Click to expand...
Click to collapse
Are you sure? How? Just write an e-mail to [email protected]? But why they shut down the request page / site? This does not make any sense.

Dexterova said:
Are you sure? How? Just write an e-mail to [email protected]? But why they shut down the request page / site? This does not make any sense.
Click to expand...
Click to collapse
Huawei Reddit

M1chiel said:
Huawei Reddit
Click to expand...
Click to collapse
OK, I'll give it a try...
... (other) question(s):
If I open (no root) the bootloader, will I get OTA updates?
In other words: you guys, with Magisk, how do you update your devices?

Because we do not make a list of which modules work 100% in magisk in P10, since for example xposed produces a hard brick.
Sorry my bad english

Is this still available [email protected]?
I got this error message:
The response from the remote server was:
550 5.1.1 Error: invalid recipients is found from 209.85.216.178

Kernel with dm-verity disabled?

Since the sources are out, is there a kernel with dm-verity disabled?
I want to be able to root and keep TWRP, make some changes (hosts, restore some titaniumbackup files), unroot and still pass the checks, which normally fails due to safetynet detecting the unlocked bootloader. If I understood correctly, disabling dm-verity will allow safetynet to pass even with unlocked BL?
Or is that outdated info?

I pass safetynet with an unlocked bootloader,TWRP and root (Magisk). Just install the MagiskHide Props Config module via Magisk Manager->Modules and in a terminal type:
su
props
and apply the fix and select mate 10 as device

I'm trying to avoid using magisk to avoid losing safetynet access when an update comes. I really only need root once.

I believe you can fully uninstall magisk and pass safetynet as it was stock again

No, unfortunately not, since safetynet detects the unlocked bootloader.

Arak0n said:
No, unfortunately not, since safetynet detects the unlocked bootloader.
Click to expand...
Click to collapse
Oh sorry didn't knew that, thought maybe just using unsu.zip would do the trick

When I get onto huawei with a legal threat of GPL violation, hopefully the kernel sources will build a working bootable image, rather than the broken, unbootable one I have installed right now. Side note: I need the working stock kernel & ramdisk if anyone has it.
Sent from my kminiltexx using XDA Labs

hackintosh5 said:
When I get onto huawei with a legal threat of GPL violation, hopefully the kernel sources will build a working bootable image, rather than the broken, unbootable one I have installed right now. Side note: I need the working stock kernel & ramdisk if anyone has it.
Sent from my kminiltexx using XDA Labs
Click to expand...
Click to collapse
Can't you use Huawei Firmware Finder and Huawei Update Extractor to get stock kernel & ramdisk? I could send you these extracted from an full OTA update.zip. What I can't do is send you these files extracted from my phone because it took a long time going back to stock and get safetynet running, so I don't want to risk that by unlocking the bootloader and flashing twrp again. Just tell me if the extracted files would be enough for you.

kaiomatico said:
Can't you use Huawei Firmware Finder and Huawei Update Extractor to get stock kernel & ramdisk? I could send you these extracted from an full OTA update.zip. What I can't do is send you these files extracted from my phone because it took a long time going back to stock and get safetynet running, so I don't want to risk that by unlocking the bootloader and flashing twrp again. Just tell me if the extracted files would be enough for you.
Click to expand...
Click to collapse
The files are great, but, sorry to tell you, someone else already sent them to me.
However, there's good news, I got Honor Support to escalate my request to a supervisor so maybe someone will actually give me sources now! Yay.

[TOOL] KnoxPatcher - use Secure Folder after root

I have finally figured out a way to use Secure Folder with a rooted / knox tripped phone!
So far this is WIP, but I have tested it to work on an SM-G960F running April 2019 rom.
You will need a GNU/Linux machine to patch your system, but a flashable zip is coming soon.
Instructions (note these are github links, I can't post actual links):
Get the tool at nm111/knoxpatch2
Install dexpatcher. You can use DexPatcher/dexpatcher-gradle-tools
Install vdexExtractor and compact_dex_converter (both can be found at anestisb/vdexExtractor)
Run ./pull_files.sh
Run ./patch.sh
Copy out/services.jar back onto the device.
Edit build.prop and remove ro.config.iccc_version.
Now secure folder will work.
Proof coming soon.

You would be our hero if you can complete this project

I have done some research, and I think it is unlikely that a flashable zip would work, unless someone could get compact_dex_converter running in TWRP (it just segfaults). I added some more scripts to download and deodex services.jar. Also I have uploaded my own patched build PPR1.180610.011.G960FXXS3CSD1 services.jar at drive[.]google[.]com/file/d/1AW7urpwMzjj3gorumsmfMeu6qh3cxD6J/view?usp=sharing. BTW, this works perfectly as far as I can see. Could someone try it out and post what happens?

It's just for pie?

denkazzzget said:
It's just for pie?
Click to expand...
Click to collapse
In theory, it should work on oreo, but I haven't tried it. You need to patch yourself though.

Good news bro and good work, i wait the flashable Zip

Nice work hope we can get the flushable soon

Eagerly waiting. The only thing stopping me from rooting is Knox tripper!!! Don't want to lose my last 6 months of warranty.
By the way, Wil this be universal and not processor specific? Curious me!

Are other features like samsung pass / pay accessible with this patch ? Normally you also lose these with root

effry said:
Are other features like samsung pass / pay accessible with this patch ? Normally you also lose these with root
Click to expand...
Click to collapse
Samsung pass would probably never work as it checks the warranty status internally in the trustlet and just never allows storage of data if WB is blown. Samsung pay may work if I can bypass the signature check (I am working on it now).

zeyaan said:
Eagerly waiting. The only thing stopping me from rooting is Knox tripper!!! Don't want to lose my last 6 months of warranty.
By the way, Wil this be universal and not processor specific? Curious me!
Click to expand...
Click to collapse
You will still lose warranty if you root, this is just so you can use Knox apps.
It might work on other phones (i think that's what you mean), but I don't have any other phones so can't check.

Will test this on my N9 and I will report back

nm111 said:
I have finally figured out a way to use Secure Folder with a rooted / knox tripped phone!
So far this is WIP, but I have tested it to work on an SM-G960F running April 2019 rom.
You will need a GNU/Linux machine to patch your system, but a flashable zip is coming soon.
Instructions (note these are github links, I can't post actual links):
Get the tool at nm111/knoxpatch2
Install dexpatcher. You can use DexPatcher/dexpatcher-gradle-tools
Install vdexExtractor and compact_dex_converter (both can be found at anestisb/vdexExtractor)
Run ./pull_files.sh
Run ./patch.sh
Copy out/services.jar back onto the device.
Edit build.prop and remove ro.config.iccc_version.
Now secure folder will work.
Proof coming soon.
Click to expand...
Click to collapse
Can you share the zip please

Update:
I have created a better version which bypasses all integrity checks but SPAY and SPASS still do not work due to them using their own trustlets. Also it is highly insecure as it forces all signature checks to return true. If I get DexPatcher to work on this then I will fix the signatures (or make an xposed module?) but if not I will release this later.
A zip will 100% not work. I have tried for ages and no luck. This is because the Samsung libraries are not loaded when in recovery so the patcher and deodexer do not work. The likely result will be a Magisk module or app which does the patching.
I am still working on this so please wait!

nm111 said:
Update:
I have created a better version which bypasses all integrity checks but SPAY and SPASS still do not work due to them using their own trustlets. Also it is highly insecure as it forces all signature checks to return true. If I get DexPatcher to work on this then I will fix the signatures (or make an xposed module?) but if not I will release this later.
A zip will 100% not work. I have tried for ages and no luck. This is because the Samsung libraries are not loaded when in recovery so the patcher and deodexer do not work. The likely result will be a Magisk module or app which does the patching.
I am still working on this so please wait!
Click to expand...
Click to collapse
Thank you <3 , We are waiting :good:

nm111 said:
Update:
I have created a better version which bypasses all integrity checks but SPAY and SPASS still do not work due to them using their own trustlets. Also it is highly insecure as it forces all signature checks to return true. If I get DexPatcher to work on this then I will fix the signatures (or make an xposed module?) but if not I will release this later.
A zip will 100% not work. I have tried for ages and no luck. This is because the Samsung libraries are not loaded when in recovery so the patcher and deodexer do not work. The likely result will be a Magisk module or app which does the patching.
I am still working on this so please wait!
Click to expand...
Click to collapse
Would appreciate if you will be able to record to process how to do it as well. Thank you and we are all waiting for this method.

So, how is the progress going so far? All good?
Sorry for that basic question, I'm eagerly waiting, I only want the Secure folder, that's it.
Thank you and keep going!

I think this is a cagada de toro, he have proof nothing

Secure folder is working on dr ketan roms with root

halo87 said:
Secure folder is working on dr ketan roms with root
Click to expand...
Click to collapse
Great,, is there Rom for S9?

[2022][ROOT] [Extreme Syndicate] [G960U/U1/W][G965U/U1/W][N960U/U1/W]

Info For U Model Bootloader Unlocking Can Be Found
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
Below US snapdragon devices can be bootloader unlocked with above service as long as bootloader version meets below criteria. Bootloader version can be determined from the 5th character from the right on the baseband version or build number, in some cases from kernel version
Below Method is no longer supported if you choose to use the unstable method below you do so on your own
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It​
EXTREME SYNDICATE ROOT METHOD
​OEM Toggle Does Nothing On US Model Phones
This root method breaks things and most likely will not be able to be used as a daily driver
You can be on any version bootloader. This will update you to V9 bootloader
This method will work if you are on Android 10 or Android 9 Pie but will put you on Android 8 Oreo. There is no root for Android 10 or Android 9 Pie
You will not be able to use magisk
You will not be able to flash full custom rom like Lineage or any other AOSP roms however GSI system images can be used
You cannot flash custom boot images or recovery images such as regular TWRP
Odin does not work on some later computers with USB 3.1 chip controllers the only work around is using a USB 2.0 mini hub
It is your responsibility to make sure you can use adb properly
Root will break things such as safetynet so deal with it
Disclaimer:
The Extreme Syndicate team and it's affiliates are not responsible for your actions or your device if any issues are to arise. You flash this and utilize these files at your own risk. You have been warned!
Notes:
- Safestrap recovery is now available with working MTP while in Safestrap
- This does NOT trip KNOX so don't ask.
- Bootloader is of course still locked.
- This uses some partitions from combo firmware which means 80% battery.
- Each variant will have its own post in its own download section. Download the right stuff!
* Variants this should work on are: N960U/U1/W, G965U/U1/W, G960U/U1/W. If you do not have one of these variants then this forum is not for you!
- Initial files/method will leave you on Oreo stock root.
- It works on latest rev's from rev1 up to the most recent revs.
- As of the initial first release, all variants have an issue with MTP not working except while in Safestrap
- S9 and S9+ also might have some issues with the selfie cam.
- Note 9 @elliwigy
- S9+ @klabit87
- S9 @jrkruse
- Telegram Support Group for All 3: https://t.me/joinchat/DxwvAlhtzHjg4EI9973BGQ
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed as a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Downloads S9 Files:
Safestrap_S9_Cmd_Line.7z
Download S9+ Files:
Safestrap_S9_Plus_Cmd_Line.7z
Download Note9 Files: -- Only For Bit 8 Or Lower
Safestrap_N9_Cmd_Line_Bit8.7z
Instructions to Inject Safestrap:
1. Download and unzip Safestrap_S9__Cmd_Line.7z for your device
2. Plug phone into computer and run Safestrap.exe
3. Follow instructions on screen to enable USB Debugging
4. Then from there the process will be mostly automatic just follow prompts on screen
5. When done flashing BootSwap file you need to hold the buttons to boot to recovery but since we swapped boot and recovery images it will boot system.
Instructions For Flash Rom:
1. Download below files and copy files for rom to phone system img and vendor img and odm zip
Downloads S9 Files:
Stock_Rom_G960.7z
GSI_Rom_G960.7z
Download S9+ Files:
Stock_Rom_G965.7z
GSI_Rom_G965.7z
2. In safestrap flash system img then vendor img and odm zip .
3. Choose data wipe and advance and check data
4.. Now reboot system you will have to hold buttons to reboot to recovery until you see safestrap splash then click continue. You must do this on every reboot. If you do not it will reboot to stock recovery. If it reboots to stock recovery just reboot system and hold buttons to reboot to recovery again.
5. When rom is booted up your computer will not recognize the phone for mtp file transfer. Adb does still work so you can transfer stuff that way (you need to switch to ptp transfer method in the dropdown) or use USB adapter and use a thumb drive.
6. Biometrics do not work so don’t try to setup fingerprint or face recognition.
The GSI rom mtp works GSI rom is rooted already just flash phhsupersu.apk found in GSI_Rom zip
If using other GSI roms you have too choose A_Only ones and will probably need to flash the Sh_Remover.zip found in the GSI_Rom zip
ShoutOuts:
@elliwigy For the method and help and everything else
@klabit87 - Ditto
@me2151 - Ditto
@gsm-CHEN - Ditto
@mweinbach - For always posting my achievements on the XDA News portal as well as giving me someone to troll sometimes when bored.
@ShaDisNX255 - He was our best tester, give him credits for testing out GSI as well!
@everyone else I am forgetting!
ENJOY!

Mine

Wow, this is actually pretty good. S9 Snapdragon + treble enabled device? Man, this is going to change everything! I hope something good comes out of this

Does it work on the U/U1 variants of the S9+ as well?

krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified

krion64 said:
Does it work on the U/U1 variants of the S9+ as well?
Click to expand...
Click to collapse
It’s confirmed working on both SM-G960U/U1 and SM-G965U/U1
Sent from some device I modified

Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.

Argyrus said:
Any chance that this might be used and not trip knox? This sounds like a similar method that was used in previous devices.
Click to expand...
Click to collapse
You cannot trip knox on a locked bootloader
Sent from some device I modified

jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?

Argyrus said:
Gotcha, any idea of when you might get this working for G965U or if you will allow testers?
Click to expand...
Click to collapse
Did you not read la couple post above yoir question
Sent from some device I modified

jrkruse said:
Did you not read la couple post above yoir question
Sent from some device I modified
Click to expand...
Click to collapse
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.

Argyrus said:
I did, but you made two posts, one that you said no files have been created and not tested then also state that it has been confirmed.
Since that seems to be the case then my bad for being confused.
Click to expand...
Click to collapse
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified

jrkruse said:
When it was tested I posted it was confirmed. Stuff will be released soon
Sent from some device I modified
Click to expand...
Click to collapse
Awesome, sorry for any confusion.

jrkruse said:
You cannot trip knox on a locked bootloader
Sent from some device I modified
Click to expand...
Click to collapse
jrkruse said:
It probably will but no files have been made for s9+ yet and not yet tested
Sent from some device I modified
Click to expand...
Click to collapse
That means I can have root and have Samsung pay? God damn that makes me wet

Dhdeanha said:
That means I can have root and have Samsung pay? God damn that makes me wet
Click to expand...
Click to collapse
As of right now it's still detecting su binaries. So Samsung Pay probably may not work.

On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?

elguy said:
On my G965/U1 I do not even see a "/system/etc/init/init.lab.rc" file on my device, is this because I am updated to the latest Android 9 December 1st security patch?
Click to expand...
Click to collapse
Don't worry about it. It will work on it, it's been proven to work exactly on Android 9, Dec 2019 security patch.

Wow! that's exciting, I can't wait until this releases. Looks like I'm not updating my phone anymore until then. Especially exciting if it works on Android 9 December 2019 security patch

the question is how likely this will be patched in Samsung's next update and how much time this may cause them to delay their next security patch.

Extreme Syndicate Root for S9 is live!!