Database Info

[SafetyNet] Stock Kernel + TWRP + Magisk + Magisk Manager for Z5P Single/Dual

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BOOT "Android 7.1.1 32.4.A.0.160" - only dual (provide single sim kernel.sin file)
dm-verity disabled
Sony RIC disabled
DRM fix installed
Click to expand...
Click to collapse
TWRP by @kv123
version 3.1.1-0
Click to expand...
Click to collapse
Magisk
version v13
use latest
Click to expand...
Click to collapse
Magisk Manager
version v5
use latest
Click to expand...
Click to collapse
Download
Google Drive
Latest Magisk & Magisk Manager
Installation
Download all files
Copy satsuki_twrp, satsuki_device_boot, MagiskManager-v5-latest into "C:\Flashtool\x10flasher_lib"
Reboot device into Fastboot mode
Press LEFT SHIFT and click right mouse button into x10flasher_lib folder, then press "Open command window here" option
Flash boot "fastboot.exe flash boot satsuki_device_boot.img"
Flash twrp "fastboot.exe flash recovery satsuki_twrp.img"
Open device into Recovery mode (vol down + power)
Flash "Magisk-v13-latest.zip" file
Flash "SafetyNet Cleaning Tools.zip" file
Reboot device
Connect device with ADB mode
Remove Magisk Manager pre-installed app "adb.exe uninstall com.topjohnwu.magisk"
Install Magisk Manager latest app "adb.exe install MagiskManager-v5-latest.apk"
Do NOT forget to hit Thanks button :fingers-crossed:​

I need dual kernel.sin file, feel free to PM me

HI.please share modules suitable for z5p
I insatall some modes and after reboot phone my phone is unrooted and no root with flash latest supersu.zip
and please say this need rooted phone?or this is root our phone too?I dont know anything about this
thanks

arshia.sunboy said:
HI.please share modules suitable for z5p
I insatall some modes and after reboot phone my phone is unrooted and no root with flash latest supersu.zip
and please say this need rooted phone?or this is root our phone too?I dont know anything about this
thanks
Click to expand...
Click to collapse
To do this you must have BL unlocked device. Magisk is also root your phone. After this process you will have SafetyNet pass, ROOT, TWRP. I don't understand what you ask to me.

sceryavuz said:
To do this you must have BL unlocked device. Magisk is also root your phone. After this process you will have SafetyNet pass, ROOT, TWRP. I don't understand what you ask to me.
Click to expand...
Click to collapse
yes my phones bl unlocked.you say with install this magisk step by step in stock rom no need to supersu or another root?
sorry for question again.
thanks

arshia.sunboy said:
yes my phones bl unlocked.you say with install this magisk step by step in stock rom no need to supersu or another root?
sorry for question again.
thanks
Click to expand...
Click to collapse
Yes, only follow this turorial. Then you have TWRP, ROOT and Magisk. Magisk is an alternative Root Management and Module Management (SuperSU & Xposed). It has all you need :fingers-crossed:

sceryavuz said:
Yes, only follow this turorial. Then you have TWRP, ROOT and Magisk. Magisk is an alternative Root Management and Module Management (SuperSU & Xposed). It has all you need :fingers-crossed:
Click to expand...
Click to collapse
thanks bro....I understad.I wish see what modules work in z5 premium dual

arshia.sunboy said:
thanks bro....I understad.I wish see what modules work in z5 premium dual
Click to expand...
Click to collapse
Use search function : https://forum.xda-developers.com/search.php?searchid=437022131
Magisk section : https://forum.xda-developers.com/apps/magisk

sceryavuz said:
Use search function : https://forum.xda-developers.com/search.php?searchid=437022131
Magisk section : https://forum.xda-developers.com/apps/magisk
Click to expand...
Click to collapse
final question.I have drm fix kernel+recovery.May I unroot phone and use this mode or need to clean flash rom on my phone?

arshia.sunboy said:
final question.I have drm fix kernel+recovery.May I unroot phone and use this mode or need to clean flash rom on my phone?
Click to expand...
Click to collapse
Flashing boot and twrp on this thread will clean your kernel and twrp. No need to flash ftf or unroot, but if you want to start with a clean install flash ftf.
If you have SuperSU app as a system app, use Full unroot function on SuperSU app to clean SuperSU app.

Connect device with ADB mode
please explain this step.....
conect to usb when phone is on and usb debuging is on?

I install sucsessfully but why my xternal sd card hide?

comeback to stock root kernel...magiask has bug now for Z5P dual

In the TWRP i had installed, to launch it I need to press volume up when the device is in the Sony white screen.....
But in this recovery why I have to press the volume down and power once. Can you make it like above
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
Flashed this kernel + TWRP + Magisk + Other things
But still safety net shows CTS Profile Mismatch

Today I stopped showing in green

May I use this tutorial but with my own kernel with my DRM keys. I have one made with topoc and tried to inastll Magisk but no success with net check

anjelz2012 said:
Today I stopped showing in green
Click to expand...
Click to collapse
I don't know the reason. Google did something We will wait the new update..

I use Mokee opensource, but ctsProfile is false, have other ways?

why after install sucsessfully external Memory card hide in phone ?even not shown in twrp?

tommy1616 said:
I use Mokee opensource, but ctsProfile is false, have other ways?
Click to expand...
Click to collapse
No Google works hard on Security.. They want to be Apple

[Oreo] [TWRP 3.2.1-0] [0.3] [+Capacitive fix]

This is my custom TWRP for the Honor9 (STF) phone. Finally after more than 2 weeks I've successfully added encryption support. I plan to keep it updated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an alpha release and many features of TWRP are untested! Let me know if you find anything that is not working.
ONLY for Oreo 8.0 firmwares​
Download:
stf-twrp-zxz-0.3.img
stf-twrp-zxz-0.2.img
stf-twrp-zxz-0.1.img
Problems:
Mount system rw
Custom kernel required because of Huawei MMC protection (check second post)
Bugreport:
Post /tmp/recovery.log and full dmesg output in comments
Install:
Put phone into fastboot
Run fastboot.exe flash recovery_ramdisk [imgfile]
Changelog:
Code:
0.3:
- Fix problem with different firmware versions
- Fix busybox zip utility
0.2:
- Implement decryption native
0.1:
- Initial release
XDA:DevDB Information
TWRP for Honor9, Tool/Utility for the Honor 9
Contributors
zxz0O0
Version Information
Status: Alpha
Created 2018-02-24
Last Updated 2018-03-26

Capacitive button fix
Some people have the problem of missing capacitive buttons. The reason for this problem is not flashing a recovery but probably because something during firmware upgrade went wrong.
I made a custom kernel which should fix the capacitive button problem. This kernel also allows disable of SELinux with setenforce command.
ONLY for OREO
New: Proto8 kernel includes my capacitive fix. Download it here: https://forum.xda-developers.com/honor-9/development/kernel-proto8-kernel-t3780551
Old method with kernel compiled by me (not recommended, use Proto8 kernel instead):
Download kernel
B360: http://www.mediafire.com/file/6n1wfbxtp09orda/KERNEL_B360a_TOUCH_FIX.img
B362: http://www.mediafire.com/file/c6yayg8sp2tvach/KERNEL_B362_TOUCH_FIX.img
B366: http://www.mediafire.com/file/opc9ilg6x5uzyvk/KERNEL_B366_TOUCH_FIX.img
Flash with fastboot.exe flash kernel KERNEL_BXXX_TOUCH_FIX.img
Reboot into android and check capacitive buttons (enable them in settings if necessary)
Flash stock kernel again if you want

After flashing and used this TWRP the capacitive buttons and camera flashlight are still working?

walter4991 said:
After flashing and used this TWRP the capacitive buttons and camera flashlight are still working?
Click to expand...
Click to collapse
Yes they do, atleast on my phone. Haven't tested other functions yet.

WidosFTW said:
Yes they do, atleast on my phone. Haven't tested other functions yet.
Click to expand...
Click to collapse
You are on Oreo right? Anyway have you tried to root? Works all?

walter4991 said:
You are on Oreo right? Anyway have you tried to root? Works all?
Click to expand...
Click to collapse
Yes I am B360 to be exactly, and I can confirm that rooting with Magisk works perfectly, buttons and flash keep working and safety net is not triggered.

Well tried to do a backup of my system and noticed that it failed to mount /system.
Logs are attached
Edit:
It can't mount rw, read only works as expected.

WidosFTW said:
Yes I am B360 to be exactly, and I can confirm that rooting with Magisk works perfectly, buttons and flash keep working and safety net is not triggered.
Click to expand...
Click to collapse
Via custom recovery:
Download the latest Magisk zip file
Reboot to a custom recovery and flash the flashable zip
Reboot to system, and check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install/upgrade it manually!
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This method and Magisk v16.0 right?

walter4991 said:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This method and Magisk v16.0 right?
Click to expand...
Click to collapse
Yeah, should work

WidosFTW said:
Well tried to do a backup of my system and noticed that it failed to mount /system.
Logs are attached
Edit:
It can't mount rw, read only works as expected.
Click to expand...
Click to collapse
Does TWRP need system rw for backup? Anyway, Huawei added write protection in memory controller. So in order to mount system rw, a custom kernel is required. If you need it I can compile a custom kernel. Note that recovery and system have the same kernel now in Oreo.

zxz0O0 said:
Does TWRP need system rw for backup? Anyway, Huawei added write protection in memory controller. So in order to mount system rw, a custom kernel is required. If you need it I can compile a custom kernel. Note that recovery and system have the same kernel now in Oreo.
Click to expand...
Click to collapse
To be honest I am not sure, you can back up without a problem (system) but I needed a few tries to restore but it worked. But I can't back up data.

WidosFTW said:
To be honest I am not sure, you can back up without a problem (system) but I needed a few tries to restore but it worked. But I can't back up data.
Click to expand...
Click to collapse
Data backup in TWRP does not work because the data decryption is not officially supported by TWRP.

WidosFTW said:
Yeah, should work
Click to expand...
Click to collapse
Ok, i've flashed this TWRP, buttons and flashlight still working. Flashed Magisk v16.0. Root works, but SafetyNet is triggered.
------- EDIT -------
After reboot, SafetyNet now is not triggered! :laugh:

Not compatible with RR-OS Oreo Treble 8.1
Stuck on Teamwin screen, no menu displayed.

fl0wfr said:
Not compatible with RR-OS Oreo Treble 8.1
Stuck on Teamwin screen, no menu displayed.
Click to expand...
Click to collapse
https://drive.google.com/open?id=1Gzt3IzBYdOgZ3oKKEHxZyOzR4Vuzkm5W
try it

gaguga said:
https://drive.google.com/open?id=1Gzt3IzBYdOgZ3oKKEHxZyOzR4Vuzkm5W
try it
Click to expand...
Click to collapse
It works, thanks!

If i remove Magisk and flash SuperSU NetSafety will be triggered? In a future a flash of stock rom and a total remove of root will turn off SafetyNet or it will be triggered forever?
A working version of SuperSU with this TWRP and Oreo B360?

WidosFTW said:
To be honest I am not sure, you can back up without a problem (system) but I needed a few tries to restore but it worked. But I can't back up data.
Click to expand...
Click to collapse
New version released. Fixed native decryption now and backup of /data should work properly. Let me know if it's working.

zxz0O0 said:
New version released. Fixed native decryption now and backup of /data should work properly. Let me know if it's working.
Click to expand...
Click to collapse
For me working [emoji16]. I am on B360a now. Thanks.
Wysłane z mojego STF-L09 przy użyciu Tapatalka

Just flash the new version over the old via fastboot?

OTA update & Magisk : Bootloop. Please help!

Hello, this morning I thought I'd try to apply Oneplus OTA update, but while keeping Magisk and its modules installed.
So I googled it and I was candid enough to follow this tutorial.
Here are the exact steps I followed:
Apply the Oneplus OTA update (download & install) BUT did not reboot
Magisk Manager → Uninstall → Restore Images (Maybe that's where I screwed up as I should have run this before above step?)
installed TWRP A/B Retention Script from Magisk Manager (installed module but did not reboot).
Magisk Manager → Install Magisk → Install to Inactive Slot
Pressed the reboot button in Magisk Manager
Now the phone rebooted, oneplus boot logo, then phone unlock screen and automatically "restarted" as shown on this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then it rebooted into TWRP, asking for my password. After I enter the password, TWRP decrypt my partition and then I don't know what to do.
I flashed magisk again, but with no luck.
Thanks a lot in advance for your help and suggestions!
[EDIT] here is what happen when I flash twrp zip installer
Shoud I flash FULL oneplus firmware from this link?

I solved it by flashing oneplus full update image, then directly flashing twrp (from twrp), then flashing magisk, and finally rebooting.

I spoke too fast.
I was able to boot into oneplus system, but Magisk was not there anymore.
So I booted into recovery (twrp), flashed magisk (it said flashing on slot A this time), rebooted: Bam, same bootloop issue than before!!
Is it related to magisk modules that were not disabled? Or what?
Any feedback would be much appreciated! Thanks

Ok, so finally I did identified the root problem : Magisk module incompatibility! The faulty module is LOS Call Recorder, so I had to do this:
Removing the los call recorder module folder from TWRP file explorer (/data/adb/modules/folder_to_remove) worked!

Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.

larsdennert said:
Yes the guide specifies you disable modules. If you skip that you will boot loop. You could have gone back to the other slot and disabled them or disabled them from TWRP and then booted the new slot.
Click to expand...
Click to collapse
I agree, and to elaborate one step further than this, I had the exact same issue and found that you don't just have to disable the modules, but you have to fully remove them (using the little trash icon in Magisk). I've heard the call recording module causes issues, but from now on I remove all of them to avoid the issue.
The way that I solved it post-bootloop was by booting to TWRP (either your phone retained it or use Fastboot boot with the .img file), and then using the function in TWRP 'Advanced > File Explorer' browsing to access 'Data\adb\modules'. For each offending module, browse into the module folder, then hit the blue folder icon on the bottom right to select and delete the entire folder. Be sure to only do this to the specific modules, I don't want you accidentally removing anything core to the OS.
That's the steps that worked for me I hope this helps you!

You actually don't have to trash them but it makes it clearer to most people. The issue is that after the update, Magisk thinks a particular module is installed when it isn't. If you simply disabled it previously, you can boot no problem after the OTA however if you then reenable the module, your next boot will loop because the module isn't there. Confusing so really the best advice is to uninstall modules and reinstall them so that nobody will simply reenable a dead module.

I'm having this exact issue, except I DON'T HAVE ANY MODULESSS
I don't know what to do... I've completely factory reset and it still didn't help

Have you flashed full stock without root?

larsdennert said:
Have you flashed full stock without root?
Click to expand...
Click to collapse
Haha, I actually did and that was the fix... After many Magisk Uninstaller flashes and Magisk installations, I realised the issue was with the OS itself, and flashing the stock image replaced the boot image which was causing the problem (I think... Idk if I'm right about this)

Depending on the phone model you'll need another rooted boot image. If you need a current one for the 1917, I can get you one.

Hi so i'm having this exact problem. Is there any solution that doesn't include a factory reset? Currently I'm stock os android 10 and was running magisk 20.4. had a bootloop uninstalled all modules etc and still bootloop. Only when I uninstall magisk does my phone boot to system. Reflash and we get a bootloop. Does anyone know what could be corrupted etc to stop magisk from rooting my phone? I'm sure a factory wipe will fix this but surely theres a better way.
Again,works perfectly without magisk installed. Then install magisk and we get a bootloop. Please help.

Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.

larsdennert said:
Try removing magisk manager and then flash magisk. How are you doing magisk? With an image or twrp? Could be you are using a bad boot image.
Click to expand...
Click to collapse
Magisk has been fully removed by flashing the zip file in twrp. Everything is deleted. When I reflash the zip in twrp I get a bootloop. It's the same steps as I originally used to root the phone without issue.

You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?

larsdennert said:
You understand that magisk is two parts? Boot code and an apk to manage settings. Was the apk also removed?
Click to expand...
Click to collapse
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.

Bxperiaz3 said:
Yes when you run the installer it removes the apk also. So when I can boot back to the os there is no trace of the manager apk.
Click to expand...
Click to collapse
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted

Joker123## said:
Try checking the /data/adb/modules to see if any modules is present,magisk don't result in bootloop unless it's one of the modules that you installed.
Uninstaller should have removed the modules,just check in twrp
You can also try flashing magisk after flashing stock boot image(use the correct versions one),maybe boot image might be corrupted
Click to expand...
Click to collapse
All modules have been removed. I might try flashing the stock boot image and see if that helps. my other plan was to dirty flash the stock rom and the magisk again to see if this repairs the problem.
---------- Post added at 10:49 PM ---------- Previous post was at 10:23 PM ----------
SOLVED!
In case anyone runs into this issue in future. I'm guessing something must have happened to the boot image because I fired up TWRP, cleared Dalvik, flashed the stock os, booted straight back to recovery, flashed TWRP again, then magisk 20.2. Then I switched slots and did the same thing and then rebooted. Now I have everything working again, magisk updated to 20.4 and no data or app loss. Very happy

How To Guide New firmware "keep root" WW-18.0840.2103.26

Okay so I went to the Asus website
https://www.asus.com/supportonly/ROG Phone 5 (ZS673KS)/HelpDesk_Download/
Got the latest firmware which is the most recent one for this month with the latest security patch. I remember doing this method with the OnePlus 8 pro same process worked for me I downloaded the firmware from the website put it in the root of my phone, the phone detected the update immediately I got to pop up on the screen and it started installing the update. Then it asked if you want to reboot or reboot later "do not reboot" then go into magisk, then go into "install"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it will give you an option to keep root after an OTA. So once you choose the option as you can see on the screenshot let it patch and do its thing and reboot. I hope this helps somebody.

Whenever i dump payload.bin using payload dumper to get boot.img and patching it using magisk when i flash it causes bootloop! So i can't root it. I think it's payload dumper's issue. Btw can you give me the patched boot.img?

sorankira said:
Whenever i dump payload.bin using payload dumper to get boot.img and patching it using magisk when i flash it causes bootloop! So i can't root it. I think it's payload dumper's issue. Btw can you give me the patched boot.img?
Click to expand...
Click to collapse
What formal version were you in before? Would you like to try my patched boot image?

chairman011 said:
What formal version were you in before? Would you like to try my patched boot image?
Click to expand...
Click to collapse
I just bought the Rog 5 and upgraded to last firm and never had problem to dumpa boot img ( my phone before Rog 5 was Nubia Redmagic 5G). Yes I like to try your boot img, my last firm is WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46. Thanks!

chairman011 said:
What formal version were you in before? Would you like to try my patched boot image?
Click to expand...
Click to collapse
Yes i would like to use your patched boot.img
And anyway to disable HardwareStub Service notification? V

how to solve this ? i follow your method to upgrade my rooted firmware to latest version , but my safetynet not passed ? before uograde my firmware , the safetynet passed without error

Quiinny said:
how to solve this ? i follow your method to upgrade my rooted firmware to latest version , but my safetynet not passed ? before uograde my firmware , the safetynet passed without errorView attachment 5400203
Click to expand...
Click to collapse
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com

twistedumbrella said:
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com
Click to expand...
Click to collapse
already installed it. but still not passed the safety net

Quiinny said:
already installed it. but still not passed the safety net
Click to expand...
Click to collapse
Clear Data of Google Playstore and Play Services.
Ensure Magisk hide is enabled and Magisk app is hidden with a different package name.

OP your advice worked perfectly for me.
I wanted to note that my phone didn't see the update file right away, but I was prompted immediately after exiting my adb shell session and unplugging the phone from my laptop.

Nexus 6P - Lineage OS 15.1 - Magisk fails CTS Profile check

Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

StyleM said:
Hi,
I'm trying to install a custom rom (Lineage OS 15.1), and gain super user access without failing the safetynet checks.
I have TWRP as my recovery and I was able to sideload the LineageOS and GApps and Magisk without a problem (with clearing caches).
I installed the latest magisk version (23.0) - I enabled MagiskHide, and hid the name of the magisk package (I forgot the name of the option, but now it says "restore the magisk app").
I also tried installing the Magisk Hide Props config module.
Once I managed to gain root access without tripping the safetynet checks through a combination of Magisk, Smali patcher and App Systemizer module (I was running android 8.0 version at that time) - however I do not remember the process and cannot find the thread again.
One thing I noted was that magisk still says install (even tho it says installed), see below image for details.
When iImanaged to run this process on stock android 8.0, I remember that these options where ticked and green (installing magisk and app)
I do have root access and am able to install apps as system and etc. The safety net checks are what I'm missing.
Does anyone have any idea what am I missing? Any help would be really appreciated.
View attachment 5324283View attachment 5324285View attachment 5324287
Click to expand...
Click to collapse
try using magisk 20.4 n dont update just keep the 20.4 version

howdeedodat said:
try using magisk 20.4 n dont update just keep the 20.4 version
Click to expand...
Click to collapse
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.

StyleM said:
Hey man thanks for the tip. I first wiped data, cache, dalvik and system, then flashed lineageos 15.1 with magisk 20.4 and gapps. I setup magiskhide and changed the package name. I also installed the magisk hide props. What am i missing
I noticed on a forum somewhere that for magisk hide module you're supposed to open a terminal and run props command... What do you do from there? I'm so confused, i have no clue whats wrong.
Fyi the error is still the same see below images.
One thing i did differently now was that i didnt reflash stock first (just flashed lineage magisk and gapps after wiping)... Do you think it makes a difference?
I'll give it a try tomorrow as i was in a rush.
Click to expand...
Click to collapse
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?

howdeedodat said:
the 5th picture which is show the emulator function, it will help u to change device fingerprint, just make sure u found the correct one for ur phone n u will be totally succesfull passing the safety net, but before u do that might be this thread could fix ur safety net without using the terminal emulator ?
Click to expand...
Click to collapse
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)

StyleM said:
Do i need to sideload this on the rom, or is it a magisk module (magisk didnt like thst zip tile)
Click to expand...
Click to collapse
flash it in magisk or sideload theres no different as long u have tha magisk on ur phone because its a magisk module