Magisk SafetyNet failed cts profile mismatch (help!) - Xperia Z5 Q&A, Help & Troubleshooting

Hey there! I am definetly not a newbe when it comes to rooting, but sinsce xposed seems to fail with Android N and Netflix now wants "google certified" devices, which means not rooted or unlocked devices, I switched to Magisk...
The problem is, I can#t make SafetyNet to work!
my phone: xperia z5 e6653
Android 6.0.1 (5.11 build)
stock repack patched kernel (dm verity off, dmr patch, twrp)
Magisk 12.0
deodexed
developer settings off, usb debugging off
why cant I pass SafetyNet?
Is it because my ROM is deodexed? I made a reset using a clean ftf before rooting!
is it because of the patched kernel? How am I able to flash the magisk zip without a custom kernel which includes a recovery?
note: developer options OFF, Magisk Hide ON, BusyBox OFF
can anybody provide help?

Read this #4 and apply all solutions.
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4
---------- Post added at 06:14 PM ---------- Previous post was at 06:11 PM ----------
or Try unofficial v13
https://github.com/stangri/MagiskFiles

ok I reinstalled Android 6.0.1 and flashed a stock based kernel which only difference is that it has a dmr fix and a recovery
then I flashed magisk 12.0
developer options off
magisk hide on (I tested it with Titanium Backup, works just fine!)
so now my phone:
Sony Xperia E6653
Android 6.0.1 rooted via Magisk 12.0
unlocked Bootloader
TWRP recovery
dmr patched kernel
no deodex etc, but it still fails when checking SafetyNet!

sceryavuz said:
Read this #4 and apply all solutions.
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4
---------- Post added at 06:14 PM ---------- Previous post was at 06:11 PM ----------
or Try unofficial v13
https://github.com/stangri/MagiskFiles
Click to expand...
Click to collapse
Basic integrity doesnt pass

I found the problem: I need a kernel that supports SElinux enforcing!!!! anybody has a link?

freaky2xd said:
I found the problem: I need a kernel that supports SElinux enforcing!!!! anybody has a link?
Click to expand...
Click to collapse
SElinux isn't the problem, but you want to try
Use that : https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
Direct link : http://forum.xda-developers.com/devdb/project/dl/?id=12506

sceryavuz said:
SElinux isn't the problem, but you want to try
Use that : https://f-droid.org/repository/browse/?fdfilter=selinuxmodechanger&fdid=com.mrbimc.selinux
Direct link : http://forum.xda-developers.com/devdb/project/dl/?id=12506
Click to expand...
Click to collapse
I've tried that, but even though I have root it stays at permessive. commands via terminal doesnt change anything either!
my kernel is Androplus v42

freaky2xd said:
I've tried that, but even though I have root it stays at permessive. commands via terminal doesnt change anything either!
my kernel is Androplus v42
Click to expand...
Click to collapse
Androplus not stock, contact with developer. Stock changed permissive to enforcing, or enforcing to permissive with this APK.

freaky2xd said:
I've tried that, but even though I have root it stays at permessive. commands via terminal doesnt change anything either!
my kernel is Androplus v42
Click to expand...
Click to collapse
Try with terminal, type :
su
setenforce 1

sceryavuz said:
Androplus not stock, contact with developer. Stock changed permissive to enforcing, or enforcing to permissive with this APK.
Click to expand...
Click to collapse
I don't get it
I managed to set SElinux to enforcing using the terminal and then a apk which keeps it that way after every boot, but I still get that stupid SafetyNet error where CTS and basic Integrity fail

Any updates to this? I can't pass SafetyNet using Magisk either.

sceryavuz said:
Read this #4 and apply all solutions.
https://forum.xda-developers.com/showpost.php?p=71154562&postcount=4
---------- Post added at 06:14 PM ---------- Previous post was at 06:11 PM ----------
or Try unofficial v13
https://github.com/stangri/MagiskFiles
Click to expand...
Click to collapse
Very useful link !
A Linux kernel version of at least 3.8 or a kernel that has the necessary features (mount namespace) backported.
Click to expand...
Click to collapse
doesn't tell me really much though
Is CONFIG_USER_NS meant ?
cause that afaik is used for chrome on Linux to sort of enforce security (sandboxing without suid)
well, the thing is that memcg is recommended in combination with it, too
but since we're not using it for CarbonROM, LineageOS, etc.
Also CONFIG_USER_NS is disabled in the kernel and not really sure if stock ROM would even boot with it (currently just switched to RR so can't and won't test)
edit:
CONFIG_NAMESPACES=y
is enabled by default, the others are off
CONFIG_NAMESPACES=y
# CONFIG_UTS_NS is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
CONFIG_NET_NS=y
Click to expand...
Click to collapse
Some explanation:
https://github.com/netblue30/firejail/issues/1347#issuecomment-311038614
https://unix.stackexchange.com/questions/92177/kernel-namespaces-support

Try to repatch your kernel without busybox and any root.

gemenee said:
Try to repatch your kernel without busybox and any root.
Click to expand...
Click to collapse
Busybox was the problem. Thanks mate!

Related

[CLOSED] SELINUX Android 5.1.1 Samsung Disable

Hello, I need to disable Selinux (SEANDROID) many apps that i have not working i have 0x0 flag Custom Recovery, Rooted,Xposed Installed, I tryed all tutorials but none of them work, Enforcing Restarts when it was permissive apps wasn't crashing like App Name Has Stopped or Selinux need to be set to permissive for this app to work i need help with disabling SELINUX Now i get while booting to recovery "Recovery Is Not Seandroid Enforcing" how can i disable Selinux? Samsung Galaxy Grand Prime SM-G531F Lollipop 5.1.1
TheSMGCraft said:
Hello, I need to disable Selinux (SEANDROID) many apps that i have not working i have 0x0 flag Custom Recovery, Rooted,Xposed Installed, I tryed all tutorials but none of them work, Enforcing Restarts when it was permissive apps wasn't crashing like App Name Has Stopped or Selinux need to be set to permissive for this app to work i need help with disabling SELINUX Now i get while booting to recovery "Recovery Is Not Seandroid Enforcing" how can i disable Selinux? Samsung Galaxy Grand Prime SM-G531F Lollipop 5.1.1
Click to expand...
Click to collapse
it has to be done in the kernel aka boot.img. im not a kernel dev, so you will probably get the best results by looking around the forums for a kernel dev and pm ing them
toolhas4degrees said:
it has to be done in the kernel aka boot.img. im not a kernel dev, so you will probably get the best results by looking around the forums for a kernel dev and pm ing them
Click to expand...
Click to collapse
well thats bad, selinux keeps changing to permissive... i really need boot.img modded? i created my own Custom Firmware and flashed it, it doesn't flagged/tripped knox warrenty void upload here boot.img?
i found in root directory /SYS/FS/SELINUX some files like policy,disable,access,enforce Many files give's access denied or Re-Create's Disable file set to 1 Re-creates same with enforce change to 0 inside re-creates
i'm sick of this selinux ! ! help
Custom Kernel
toolhas4degrees said:
it has to be done in the kernel aka boot.img. im not a kernel dev, so you will probably get the best results by looking around the forums for a kernel dev and pm ing them
Click to expand...
Click to collapse
I Made with DadziokPL Custom Kernel with selinux permissive
***THREAD CLOSED!***

Upgrade from 32.2.A.0.305 to 32.2.A.5.11

Hi!
Did anybody managed to upgrade from unlocked an rooted 32.2.A.0.305 to 32.2.A.5.11?!
I tried it at least five times and I failed.
Everything seems to work, except unlocking the bootloader and gaining root access.
1) Flashed the new firmware with Flashtool (without TA partitions!).
2) Tried to unlock the bootloader but this is not working as expected.
The service menu tells me that I can unlock my bootloader.
But when I try to unlock it via fastboot I am getting a message, that my device is already rooted/unlocked.
FAILED (remote: Device is already rooted)
So I locked it again using the "Sony Mobile Flasher". After a reboot the "fastboot -i 0x0fce oem unlock 0x....." command gives me an OKAY and after the next reboot my device is automatically wiped.
But the service menu still tells me that my bootloader is unlockable and not that is unlocked!
Installing the patched kernel and TWRP seems to work because fastboot returns an "OKAY".
But neither I can access the TWRP recovery (LED won't get amber) nor the device is rooted.
Okay.... does anybody can give me a hint, how to root the current FW version?!
Ok, I downgraded to 32.2.A.0.305 and everything is working fine again!
I have root access and I can boot into recovery!
What is wrong with 32.2.A.5.11?
im on .I 1 , bootloader unlocked , rooted
got same error as u
device already rooted
so i just didnt check what services menu say and rooted my z5
mohalazio said:
so i just didnt check what services menu say and rooted my z5
Click to expand...
Click to collapse
How did you do this?
I flashed a modifyed kernel (dm-verity: off, RIC: off, TWRP: no, DRM fix: yes, busybox: no) with
fastboot flash boot boot.img
But I cannot install SuperSU from PlayStore.
It sais that the su binary is missing and that it cannot be installed.
So, next I tried to install TWRP with
fastboot install recovery twrp-3.0.2-0-E6653-20160504.img
But on a reboot the LED is not getting amber and I cannot enter recovery.
It seems that neither the patched kernel nor the recovery has been installed. Even though fastboot returned with an OKAY for both install commands!
First I thought that something went wrong patching the kernel with rootkernel5.0. So I downloaded and flashed an already patched one for 32.2.A.5.11. But I have still no root access!
From loud despair I flashed the SLIMX REBORN ROM (1.17BEATMODE). Now I have full root access again, but on 32.2.A.0.305 with my old problems: a) The SU binary cannot be updated from within SuperSU app and b) SONY annoys me to update to the new version every day.
I can't believe that it is not possible to root the new version or that it just doesn't work for my device.
u missed 1 small detail
first : download flashable supersu ( supersu. zip )
then put it in rootkernel folder
build the kernel
u will get extra question asking u to install supersu ( the answer is yes )
flash ur boot. img
thats it
Hi!
I know that I can integrate SuperSU into the kernel image.
But I cannot upgrade a su binary installed that way by using the SuperSU app from playstore.
The PlayStore / TWRP method for SuperSU works like a charm on 32.2.A.0.305.
But I will give it a seventh try with "AndroPlusKernel Permissive v42" instead of the patched stock kernel.
mohalazio said:
u missed 1 small detail
first : download flashable supersu ( supersu. zip )
then put it in rootkernel folder
Click to expand...
Click to collapse
Okay, I am giving up for now!
Buying a SONY phone was one of my worst decisions in 2016.
After a Samsung Galaxy Nexus and a HTC One M8 the SONY Z5 drives me crazy.
After installing 32.2.A.5.11, SuperSU 2.79 and AndroPlus kernel v42 I still have a phone that is unrooted!
And TWRP is reporting the unknown partition "/keymaster"....
so u have supersu installed and working ?
if thats the case i also have binary update problem when updating it from playstore
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
i would suggest one way
first u have 2 IMEI
try unlocking the bootloader with the the other IMEI
UNLOCK using flashtool
then root kernel
---------- Post added at 10:58 PM ---------- Previous post was at 10:53 PM ----------
if things didnt work out
use this rom on .305
http://forum.xda-developers.com/xpe...m-32-2-0-305-e6653-e6683-1-0-0-t3498626/page1
mohalazio said:
so u have supersu installed and working ?
Click to expand...
Click to collapse
I managed to install it via TWRP but as you can see "Root Check" says that my device is not rooted and that the SU binary cannot be found! The same error with the SuperSU app itself. The message means that the su binary cannot be found and SuperSU is not able to install it!
mohalazio said:
i would suggest one way
first u have 2 IMEI
try unlocking the bootloader with the the other IMEI
UNLOCK using flashtool
then root kernel
Click to expand...
Click to collapse
Two IMEI?! My Z5 is the single SIM model.
what supersu version u used?
mohalazio said:
what supersu version u used?
Click to expand...
Click to collapse
SuperSU-v2.79-201612051815
try 2.78
Still not working!
Damn, why I am the only person on this planet that fails to root its XPeria Z5?!
good news for u
new rom based on .11
http://forum.xda-developers.com/xpe...m-32-2-0-305-e6653-e6683-1-0-0-t3498626/page1
Thank you!!
I'll give it a try!

ViperAudio on latest betas/Magisk 13+

Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
I believe It's because it requires new magisk template. Give developers some time to update.
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
MarcTremonti said:
working absolutely fine here on latest FreedomOS CE, which is based on BETA 19.
Click to expand...
Click to collapse
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
theduke7 said:
may i ask which module are you using!!! and if you did something after installing it, or just installed via Magisk!
that's said, to OP, this is the wrong forum for the post, there's a questions forums where this will be more appropriate.
Click to expand...
Click to collapse
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
MarcTremonti said:
Latest freedomOS came with magsik 13 beta, but also this worked.
But i updated magisk manually also to 13.1. installed magisk manager update und flashed magisk13.1.zip. done.
FreedomOS also comes with compatibility modules for Arise, but afaik these are only needed because freedomOS comes with enforcing kernel. And the kernel i use now (bluspark) is also enforcing.
Stock OOS comes with permissive kernel and these modules shouldnt be needed there.
AFAIK, dont quote me on that.
Click to expand...
Click to collapse
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
theduke7 said:
i;m using Blu_Spark too, so i think my kernel is Enforcing, are these Magisk modules (for freedom) available to download!!!
Click to expand...
Click to collapse
Yea bluspark is enforcing. I guess they are on gitlab from freedomOS.(check FOS thread for gitlab link)
But i guess easiest way would be just to flash freedomOS. Its nothing else anyway, than debloated stock ROM with a few tweaks. Everything selectable in aroma to your needs.
Try this...
kokesh said:
Anyone got Viper to work on latest Magisk?
None of them install the driver and does anything soundwise, even you can turn the effects on.
Click to expand...
Click to collapse
You can try this:
Update to the latest Magisk version and get everything set. for example, Snapchat and other apps that you might need to pass safety.
After that, you can downgrade to the V.12.0. And V4A it should work fine.
The only bad thing here is that you can't use Android pay or pass safetynet.
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
I use the one from ahrion, too. Works fine.
I am 6
Sent from my ONEPLUS A3000 using Tapatalk
siwan05 said:
This one is working fine for me with OB19/Magisk13/FCkernel25:
https://forum.xda-developers.com/apps/magisk/module-viper4android-fx-2-5-0-5-t3577058
also with dolby atmos:
https://forum.xda-developers.com/apps/magisk/soundmod-axon-7-dolby-atmos-t3412342
Click to expand...
Click to collapse
I've tried both. It installs, but once I launch Viper, it asks either for driver install, or shows the driver state as abnormal. Never has any effect on the audio.

How to root magisk on my mate 9 oreo? Help request

Hello,
I would like to install on my Huawei Mate 9 MHA-L29 c432 root using magisk. I have the current updates etc.
I currently have twrp and a unlocked bootloader. So how do i get magisk root? There are many post about flashing stuff but in the other they dont mention that so i'm a bit confused
its a QA thread
calby17 said:
Hello,
I would like to install on my Huawei Mate 9 MHA-L29 c432 root using magisk. I have the current updates etc.
I currently have twrp and a unlocked bootloader. So how do i get magisk root? There are many post about flashing stuff but in the other they dont mention that so i'm a bit confused
its a QA thread
Click to expand...
Click to collapse
You are on Oreo, yes?
If so, flash this TWRP (3.2.1): https://mega.nz/#!4DYngAxL!OJEgQ4a4cSTypHgRBbMQbok2BRDuVHSDXNktAJ_PnKQ
Or this (3.0.3): https://mega.nz/#!AWpymRbC!ncVMIZL177b2OssrjSuKVq2AyyxzUqj_BKfsMEAajhw
Doesn't matter which you choose, both work fine.
And Magisk v16: http://tiny.cc/latestmagisk
(The reason for flashing TWRP is because of the fixlinks.sh script. Magisk installer can't find ramdisk otherwise without modifying the Magisk zip).
ante0 said:
You are on Oreo, yes?
If so, flash this TWRP (3.2.1): https://mega.nz/#!4DYngAxL!OJEgQ4a4cSTypHgRBbMQbok2BRDuVHSDXNktAJ_PnKQ
Or this (3.0.3): https://mega.nz/#!AWpymRbC!ncVMIZL177b2OssrjSuKVq2AyyxzUqj_BKfsMEAajhw
Doesn't matter which you choose, both work fine.
And Magisk v16: http://tiny.cc/latestmagisk
(The reason for flashing TWRP is because of the fixlinks.sh script. Magisk installer can't find ramdisk otherwise without modifying the Magisk zip).
Click to expand...
Click to collapse
Thank you aigen. I m now running magisk v16.0 on my phone, cool! Thanks :good::good:
ante0 said:
You are on Oreo, yes?
If so, flash this TWRP (3.2.1): https://mega.nz/#!4DYngAxL!OJEgQ4a4cSTypHgRBbMQbok2BRDuVHSDXNktAJ_PnKQ
Or this (3.0.3): https://mega.nz/#!AWpymRbC!ncVMIZL177b2OssrjSuKVq2AyyxzUqj_BKfsMEAajhw
Doesn't matter which you choose, both work fine.
And Magisk v16: http://tiny.cc/latestmagisk
(The reason for flashing TWRP is because of the fixlinks.sh script. Magisk installer can't find ramdisk otherwise without modifying the Magisk zip).
Click to expand...
Click to collapse
Dear friend I've install like this and everything is running good except for safety net test see
albertobom said:
Dear friend I've install like this and everything is running good except for safety net test see
Click to expand...
Click to collapse
Well, what firmware build are you on? And what mods are you using? That battery doesn't look stock
ante0 said:
Well, what firmware build are you on? And what mods are you using? That battery doesn't look stock
Click to expand...
Click to collapse
I'm on c432B365 and that is just a from the play store. No mods installed except for magik.
albertobom said:
I'm on c432B365 and that is just a from the play store. No mods installed except for magik.
Click to expand...
Click to collapse
Ah. B365 is some test build, it will probably never pass. I have the same on my Mate 9 and it fails for me too (even with the Huawei fix module).
ante0 said:
Ah. B365 is some test build, it will probably never pass. I have the same on my Mate 9 and it fails for me too (even with the Huawei fix module).
Click to expand...
Click to collapse
Well for now I can live with it. I'll try on later updates. :good:
ante0 said:
You are on Oreo, yes?
If so, flash this TWRP (3.2.1): https://mega.nz/#!4DYngAxL!OJEgQ4a4cSTypHgRBbMQbok2BRDuVHSDXNktAJ_PnKQ
Or this (3.0.3): https://mega.nz/#!AWpymRbC!ncVMIZL177b2OssrjSuKVq2AyyxzUqj_BKfsMEAajhw
Doesn't matter which you choose, both work fine.
And Magisk v16: http://tiny.cc/latestmagisk
(The reason for flashing TWRP is because of the fixlinks.sh script. Magisk installer can't find ramdisk otherwise without modifying the Magisk zip).
Click to expand...
Click to collapse
Im running oreo...when I flashed the Magisk file it gives me error...
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
calby17 said:
Hello,
I would like to install on my Huawei Mate 9 MHA-L29 c432 root using magisk. I have the current updates etc.
I currently have twrp and a unlocked bootloader. So how do i get magisk root? There are many post about flashing stuff but in the other they dont mention that so i'm a bit confused
its a QA thread
Click to expand...
Click to collapse
When I flashed the magisk v16? successfully, then my phone get rooted? I want to flash p20 pro camera on my mate 9. please help
toto2011 said:
Im running oreo...when I flashed the Magisk file it gives me error...
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
When I flashed the magisk v16? successfully, then my phone get rooted? I want to flash p20 pro camera on my mate 9. please help
Click to expand...
Click to collapse
And what error does it give?
ante0 said:
Ah. B365 is some test build, it will probably never pass. I have the same on my Mate 9 and it fails for me too (even with the Huawei fix module).
Click to expand...
Click to collapse
Hi,
Which build would you advise then that is official and would pass safety net ? B366 ? B367?
Surfinette said:
Hi,
Which build would you advise then that is official and would pass safety net ? B366 ? B367?
Click to expand...
Click to collapse
B366. 367 is a test i think, it doesn't pass safetynet anyway.
ante0 said:
You are on Oreo, yes?
If so, flash this TWRP (3.2.1): https://mega.nz/#!4DYngAxL!OJEgQ4a4cSTypHgRBbMQbok2BRDuVHSDXNktAJ_PnKQ
Or this (3.0.3): https://mega.nz/#!AWpymRbC!ncVMIZL177b2OssrjSuKVq2AyyxzUqj_BKfsMEAajhw
Doesn't matter which you choose, both work fine.
And Magisk v16: http://tiny.cc/latestmagisk
(The reason for flashing TWRP is because of the fixlinks.sh script. Magisk installer can't find ramdisk otherwise without modifying the Magisk zip).
Click to expand...
Click to collapse
Please help everytime I flashed Magisk.zip it give me error:
Unmounting / system and /vendor
Done!
Updating partition details....
...done
Installing zip file '/external_sd/Magisk-v16.0.zip
Checking for digest file...
Skipping digest check:no Digest file found
Magisk installer
Mounting /system ,/vendor
!unable to detect boot image
-Unmounting partions
Updater process ended with error: 1
Error installing zip file '/external_sd/Magisk-v16.0zip
---------- Post added at 10:24 AM ---------- Previous post was at 10:21 AM ----------
ante0 said:
And what error does it give?
Click to expand...
Click to collapse
Please help everytime I flashed Magisk.zip it give me error:
Unmounting / system and /vendor
Done!
Updating partition details....
...done
Installing zip file '/external_sd/Magisk-v16.0.zip
Checking for digest file...
Skipping digest check:no Digest file found
Magisk installer
Mounting /system ,/vendor
!unable to detect boot image
-Unmounting partions
Updater process ended with error: 1
Error installing zip file '/external_sd/Magisk-v16.0zip
toto2011 said:
Please help everytime I flashed Magisk.zip it give me error:
Unmounting / system and /vendor
Done!
Updating partition details....
...done
Installing zip file '/external_sd/Magisk-v16.0.zip
Checking for digest file...
Skipping digest check:no Digest file found
Magisk installer
Mounting /system ,/vendor
!unable to detect boot image
-Unmounting partions
Updater process ended with error: 1
Error installing zip file '/external_sd/Magisk-v16.0zip
Click to expand...
Click to collapse
Which twrp are you using?
ante0 said:
Which twrp are you using?
Click to expand...
Click to collapse
Id been trying so many version of twrp..3.2. 3.1 3.3 but same give error. Im on android 8.0 c636B362
toto2011 said:
Id been trying so many version of twrp..3.2. 3.1 3.3 but same give error. Im on android 8.0 c636B362
Click to expand...
Click to collapse
Try this one: https://mega.nz/#!AP5DRA4Q!i02i8cCi_UWoF2XZl5gjLb5ESpeilpR_OD0MHSh6Ezg
I have one on my Mate 9 with decryption support as well, but it's at home :/
It's basically this one but updated which partitions you can flash: https://forum.xda-developers.com/honor-9/development/oreo-t3754483
That one works for Mate 9 so if you need decryption you could use it.
ante0 said:
Try this one: https://mega.nz/#!AP5DRA4Q!i02i8cCi_UWoF2XZl5gjLb5ESpeilpR_OD0MHSh6Ezg
I have one on my Mate 9 with decryption support as well, but it's at home :/
It's basically this one but updated which partitions you can flash: https://forum.xda-developers.com/honor-9/development/oreo-t3754483
That one works for Mate 9 so if you need decryption you could use it.
Click to expand...
Click to collapse
Same error! ??? Other flashable file flashed through twrp were successful. Im.just wondering why I cnt on flash magisk any version via twrp. Is there any way to flsh magisk ? I just wanted to root my phone. I flashed SU but when it boots theres nothing install. When I check my root access my phone is not rooted. I almost give up trying! ???
toto2011 said:
Same error! Other flashable file flashed through twrp were successful. Im.just wondering why I cnt on flash magisk any version via twrp. Is there any way to flsh magisk ? I just wanted to root my phone. I flashed SU but when it boots theres nothing install. When I check my root access my phone is not rooted. I almost give up trying!
Click to expand...
Click to collapse
Although the Fixlinks TWRP should've found ramdisk, try this magisk: https://mega.nz/#!dLwByZhA!4liVsBY4N-o3FiRKDs7pxpoW2H_vDWksQbMYqiXJmNU
toto2011 said:
Id been trying so many version of twrp..3.2. 3.1 3.3 but same give error. Im on android 8.0 c636B362
Click to expand...
Click to collapse
If you've been still having issues flashing magisk through TWRP then i recommend doing it the alternative way. It's the way I first did it and have always done it since.
I actually just wrote up and posted a guide...https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878

About Beta...

I am using OnePlus 8 and planning to install Oxygen 11 Beta. Any Beta users here? How smoothly it runs as compared to OT? Is there any problems in app support?
I've had no issues so far. Started when Dp3 was released and now on Dp4. Runs as well or better than my Pixel 2xl. Everyone's experience will vary depending on apps used, etc.
Been on DP4 since day one. It is my daily driver. Very stable.
Anyone using it on a T-Mobile Device?
I'm on T-Mobile device that has been converted.
Same here.
joe1gun said:
I'm on T-Mobile device that has been converted.
Click to expand...
Click to collapse
Can you update without rooting if your sim unlocked and can toggle the b/l unlock toggle in dev settings?
Edit-mine shows as an in2017
prozack1983 said:
Can you update without rooting if your sim unlocked and can toggle the b/l unlock toggle in dev settings?
Edit-mine shows as an in2017
Click to expand...
Click to collapse
You have to flash global firmware to run beta builds, there is a forum/guide on how to do that.
Awesome
I installed the beta a bit ago. I'm TMobile converted and I am very happy about the beta. It's very smooth .
Installed it yesterday. Someone mentioned netflix wasn't working but for me it's working fine.
Only thing I can't get setup yet is Google Pay.
I came from the latest official rom, just put the update file in the root directory and flash via the updater.
Does the open beta require a data wipe?
As I said in my first post the beta is awesome and I'm glad aod is back but I had to use the rollback package because 90fps is no longer an option on fortnite. So if your like me you need that 90fps gameplay:good:
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
Bastienhere said:
Does the open beta require a data wipe?
Click to expand...
Click to collapse
No it does not however if you wish to go back to android 10 you will have to use the rollback zip provided in the oxygen updater. Just so you know that the rollback package will indeed wipe data.
Zelete said:
Installed it yesterday. Someone mentioned netflix wasn't working but for me it's working fine.
Only thing I can't get setup yet is Google Pay.
I came from the latest official rom, just put the update file in the root directory and flash via the updater.
Click to expand...
Click to collapse
Google pay works fine if you root with magisk and update the device fingerprint to pass cts. I have it working.
How to root open beta please? Does it work normally?
danceeeee said:
How to root open beta please? Does it work normally?
Click to expand...
Click to collapse
Depends what is normal. Extract boot img from payload. Patch with magisk canary. Adb flashed.... Is working fine. [emoji106]
Ehm, Payload? Not sure what does it mean?
danceeeee said:
Ehm, Payload? Not sure what does it mean?
Click to expand...
Click to collapse
Do a search on rooting with magisk [emoji6]
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Sorry to be vague but if you don't understand what I said. I'm not sure I would be risking my phone.
I do understand, i have root on my phone. Just never heard of term Payload
AndyBury said:
Depends what is normal. Extract boot img from payload. Patch with magisk canary. Adb flashed.... Is working fine. [emoji106]
Click to expand...
Click to collapse
i tried flashing my patched boot.imgfrom the ob1 payload in fastboot and fastbootd but magisk manager still doesnt show magisk is installed
42o247 said:
i tried flashing my patched boot.imgfrom the ob1 payload in fastboot and fastbootd but magisk manager still doesnt show magisk is installed
Click to expand...
Click to collapse
Did it complete OK in the cmd windows?
I had to do it about 5 or 6 times till it completed OK.
It would see it in adb devices.... Then seem to lose connection....

Categories

Resources