am trying to run remote play but its not working as am getting error 88001003 due to my bootloader is unlocked
my phone is rooted with latest magisk and the remote play is checked in magisk hide
my phone is
mate 8 rebranded To AL-10 8.0.0839
Related
So I'm on stock aqh3 firmware but I am rooted with magisk and have notorious kernel installed. Even though I have magisk hide to hide Netflix I'm still getting that error 5.2, am I missing something here? On my s6 aslong as had magisk hide enabled it worked fine.
Magisk 14 here btw
Bump
Hey!
It's great we finally got our own lite forum
I had an update to version (WAS-LX1C432)B182 yesterday. Only way to install it on my device was by official update and full package. Of course i had to unlock bootloader, install twrp and root again afterwards.
Magisk is running fine so far. I can, however, not pass safetynet check. How about you guys, any experiences?
I tried disabling and enabling magiskhide, core mode only, new busybox installation and enabling log settings but haven't been lucky so far. Btw, is it normal that one always has to enable logging after every restart?
I recently updated to WAS-LX1C432B182 via official (full) update package. This was the only way i was able to update, which means I had to re-unlock bootloader, install TWRP (3.1.1.), root my phone with magisk and restore my phone. I am finally passing safetynet (For now! ). To make it work I have to enable logging (*#*#2836579#*#*) and restarte magiskhide (terminal!) after every reboot. Google also says I'm certified. The only thing RootBeer Sample detects is the magisk busybox binary module.
Chur to you, you I rooted my phone with TWRP first,and then installed Superuser, but I did it all with the command prompt administrator on the I've only really work with Samsung before and that was quiet might drawn out sort of different way to go about it. What's your opinion all this s***
Hello,
I have two apps that fail some security check and doesn't want to launch on a brand new OnePlus5
One banking app tells me I'm rooted
And a game says I have rooted or modified device.
I did not root my device. It's like out of the box.
I have turn off USB debugging and developers options.
I have been told to install Magisk to hide root but my phone is not rooted and it seems I have to root it in order to install Magisk. Which I don't want.
How is it that those app fail security check?
What can I can do to pass it?
Thank you guys
Lock the bootloader
KashCorp said:
Hello,
I have two apps that fail some security check and doesn't want to launch.
One banking app tells me I'm rooted
And a game says I have rooted or modified device.
I did not root my device. It's like out of the box.
I have turn off USB debugging and developers options.
I have been told to install Magisk to hide root but my phone is not rooted and it seems I have to root it in order to install Magisk. Which I don't want.
How is it that those app fail security check?
What can I can do to pass it?
Thank you guys
Click to expand...
Click to collapse
ROFL omg incomplete info if you're not aware.... IF you relock the bootloader make sure you do not have a custom recovery installed. you MUST have STOCK recovery BEFORE you relock the bootloader. If you lock the bootloader with custom recovery, you'll brick your phone.
With that said, you should be able to install Magisk and pass the safety check. If not, then the Magisk dev with apps are failing and he may fix that in an update.
had the same situation, because I used supersu for root before I switched to magisk.
I solved it this way:
1. run unsu-script (https://forum.xda-developers.com/showpost.php?p=63615067)
2. flash magisk
3. hide it for the banking app, playstore and google service framework
4. reboot
5. done
KashCorp said:
Hello,
I have two apps that fail some security check and doesn't want to launch on a brand new OnePlus5
One banking app tells me I'm rooted
And a game says I have rooted or modified device.
I did not root my device. It's like out of the box.
I have turn off USB debugging and developers options.
I have been told to install Magisk to hide root but my phone is not rooted and it seems I have to root it in order to install Magisk. Which I don't want.
How is it that those app fail security check?
What can I can do to pass it?
Thank you guys
Click to expand...
Click to collapse
If you unlocked the bootloader you will fail security check as other member said. If your bootloader is locked you might want to go into the Play Store settings and see if your device shows up as certified. If not go into settings / applications and clear all data for Play Store then reboot your phone. When you log back into the Play Store the status should change to certified.
Days ago, I had the wonderful idea of installing TWRP. I didn't want to install a custom ROM, I simply wanted TWRP + the current android. However, after I installed TWRP, the Android 8.0 was wiped out. I thought I would still keep the Android 8...
I tried to install many older versions (from April, June, July, August) of the stock ROM 8.0 via Odin, but all of them failed (as far as I learned, they failed because they had an older version than the Bootloader I had installed), then I successfully installed a stock ROM build from December.
Now, my phone doesn't pass the SafetyNet Test. It fails on "CTS profile match" (I read on the internet it is due to the unlocked Bootloader).
Interesting thing is: when I browse to "Developer Options -> OEM unlock", it says "Bootloader is already unlocked", even if the option is unset.
Now I have no TWRP (and I don't want to play with it anymore) and I have no root access.
Does anyone know how to "relock" the Bootloader or do anything that will allow me to pass the SafetyNet Test?
I used Magisk to do an OTA update to Oxygen OS 12, but it feels like my root is gone because TWRP disappeared, the bootloader was locked after the update, and I had to unlock it. But when I do root check, it still says I'm rooted. Most of my Root access requiring apps don't work properly either like battery limiter and Adaway. But I check root status in Momo, and it says the environment is abnormal. Upon restart it doesn't pop up with TWRP as recovery; it goes to default OP recovery. Also, the warning at startup where it says the warning about the bootloader being unlocked is also gone, even after reunlocking my bootloader after the OTA update.
Also, slightly unrelated, but my fingerprint sensor has also stopped functioning completely. I couldn't use it to unlock my phone so I removed all fingerprint data and I tried adding it back and it wouldn't even detect my finger when I tried to add it back.
What is a true test to check if I need to wipe and reroot and install TWRP again?
How did TWRP just disappear?
Did I do the OTA wrong?
Why would my phone allow me to grant root access to root checker if I wasn't still rooted?
Would a simple fix be just reinstalling Magisk?
edit: So it seems that Adaway works, but battery limiter does not(I assume doing a fresh install of the APK might help). And my fingerprint sensor also does not work.
I am indeed rooted, but I am still wondering why TWRP just disappeared? And why does my fingerprint sensor not work at all?
I have the Oneplus 8 Pro American version.
Take a step back and read this.
[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this! ANSWER - THE BOOTLOADER! Massive Update...
forum.xda-developers.com
A12 is not in a good state anyway and most people use OOS11 or a custom rom.
IDK if battery limiter is a12 compatible but that does not matter.
You should NOT use TWRP with A12 and you should NOT do an OTA with magisk to a12.
What i would do now:
1. Read the thread i posted above carefully.
2. Backup all you data to a pc.
3. Backup persist image.
4. Use MSM Tool ro rollback to a clean state of OOS11.(https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/)
5. Flash latest A12 as local upgrade within the system updater twice (to ensure its on both slots)
6. Extract boot img with payload dumper and patch it via magisk.
7. Unlock bootloader
8. fastboot BOOT patched_boot_image.img
9. Start magisk and install
Enjoy rooted A12.
Or better simply stay on A11 its better anyway.