Related
Hello Guys,
I have a Oneplus 3 with Oxygen OS 4.0.1 with locked Bootloader atm because when I try to use Android Pay with Root and Freedom OS it doesn't work
I figured out that this Safetynet fails when I unlock my Bootloader but
I would like to get the EmojiOne Emojis back in Whatsapp and Android Keyboard is this Possible ?
Is there a Way to bypass Safetynet that I can use Root and V4A again ?
(I already tried Magisk)
Greetings
Magisk has an emoji one module, root, etc while passing safety net
Sent from my du_oneplus3 using Tapatalk
slothdabski said:
Magisk has an emoji one module, root, etc while passing safety net
Sent from my du_oneplus3 using Tapatalk
Click to expand...
Click to collapse
Okay and how can I hide my unlocked Bootloader ?
Just try it, working like a charm. Really, worth.
mucha.k1994 said:
Just try it, working like a charm. Really, worth.
Click to expand...
Click to collapse
It doesn't work on Oneplus 3 because it's nearly Stock and the Safety Thing checks for unlocked Bootloader......
I managed it by installing a custom Whatsapp Mod and maybe a custom Keyboard soon.....
Luro02 said:
It doesn't work on Oneplus 3 because it's nearly Stock and the Safety Thing checks for unlocked Bootloader......
I managed it by installing a custom Whatsapp Mod and maybe a custom Keyboard soon.....
Click to expand...
Click to collapse
In fact, Magisk patch the bootloader dm-verity (which is used by SafetyNet to check if your device is unlocked), so juste flash a completly stock system, check SafetyNet, and Install latest Magisk with the modules you want, reboot and you're good to go !
Arno500 said:
In fact, Magisk patch the bootloader dm-verity (which is used by SafetyNet to check if your device is unlocked), so juste flash a completly stock system, check SafetyNet, and Install latest Magisk with the modules you want, reboot and you're good to go !
Click to expand...
Click to collapse
Dude did you tried it on the Oneplus 3 ???
IT'S NOT WORKING WITH UNLOCKED BOOTLOADER !!!!!!!!!
Luro02 said:
Dude did you tried it on the Oneplus 3 ???
IT'S NOT WORKING WITH UNLOCKED BOOTLOADER !!!!!!!!!
Click to expand...
Click to collapse
Working perfectly with the normal way of unlocking, installing TWRP and flashing Magisk
What can you do with root before it breaks ? (Xposed,Substratum,Adblocker or V4A working ?)
What were your Steps to get it working ?
Do you still have the DM-Veriy Warning on Boot ?
Luro02 said:
What can you do with root before it breaks ? (Xposed,Substratum,Adblocker or V4A working ?)
What were your Steps to get it working ?
Do you still have the DM-Veriy Warning on Boot ?
Click to expand...
Click to collapse
I'm running Open Beta 13 with an unlocked bootloader and Magisk with Substratum. I would recommend unlocking your bootloader, flashing stock, then rooting with just Magisk, not SuperSU. I followed these steps and I have it working, SafetyNet passed.
Luro02 said:
Dude did you tried it on the Oneplus 3 ???
IT'S NOT WORKING WITH UNLOCKED BOOTLOADER !!!!!!!!!
Click to expand...
Click to collapse
Its working perfectly on op3 with magisk. So relax.
You must check magisk hide in magisk settings ofc.
Running latest freedomOS CE and all good. Magisk, safetynet, V4A, abblock, substratum. All working.
So stop saying it doesnt work with unlocked bootloader, thats just bull****.
Update to latest version of Freedom OS.
I think you should try updating your ROM to latest version of Freedom OS. Has everything you need.
Thanks Guys
It works
Rooted (super su) and ElementalX kernel, nougat 7.1.2. I want to use viper4android and having problems (driver installs but it doesn't work). I read that installing magisk su might work better but I get an error every time I try. Super su is systemless and guides are saying it should work just to flash the zip of magisk but it isn't working. Is there anything I need to do? I also have poweramp installed which may be messing with viper4android but I'm a bit lost. Any help would be great.
Are you trying to install Magisk on top of SuperSu or in place of it? Also, you are using the version of Magisk that was modified for the Pixel, not the official version, correct?
jhs39 said:
Are you trying to install Magisk on top of SuperSu or in place of it? Also, you are using the version of Magisk that was modified for the Pixel, not the official version, correct?
Click to expand...
Click to collapse
I'm going in place of SuperSU, I think you've nailed my issue though....I didn't know there was a modified version
Kevinj17 said:
I'm going in place of SuperSU, I think you've nailed my issue though....I didn't know there was a modified version
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B1xZ4VKT4JKZUFhVUlk0enhBVFk/view
I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?
jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that
sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.
It worked, I'm officially rooted .Thanks for the help!
jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.
Hello guys, I'm using the stock version of rom 7.1.1, I made the update via OTA today. I would like to know if there is any way to use safetynet in this rom, Magisk was installed without any problems and seems to work very well (with the exception of safetynet).
Can someone help me?
larilieb1793 said:
Hello guys, I'm using the stock version of rom 7.1.1, I made the update via OTA today. I would like to know if there is any way to use safetynet in this rom, Magisk was installed without any problems and seems to work very well (with the exception of safetynet).
Can someone help me?
Click to expand...
Click to collapse
We need the kernel source so we can modify it, until then magisks safetynet won't pass.
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
larilieb1793 said:
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
Click to expand...
Click to collapse
There's a Netflix app that by pass the root check,I found it on apk mirror.
larilieb1793 said:
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
Click to expand...
Click to collapse
I have 7,1,1 stock and magisk with safety net pass, follow this steps:
1. Unistall magiks with the Unistaller Zip via twrp
2. Install magiks 12.0 vía twrp
3. Boot your phone, install magisk manager and check the correct install of magisk
4. install the module universal safety net fix (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431) via twrp
5. DO THIS!! >>> https://forum.xda-developers.com/moto-z-play/how-to/magiks-moto-z-play-t3545473 .
6. Install magisk 13.3 via twrp and the Latest magisk manager
7. Check that the module are actived and run the safety net test
Good luck sorry for my english
larilieb1793 said:
Thanks for your answer, so the only way is to wait for the kernel ... I'm less distressed because I'm with the stock rom without root and twrp, and the only application that the play store will not let me download was Netflix, because my bootloader is unlocked... So it's ok, thank you!
Click to expand...
Click to collapse
EDIT: Nevermind, saw in other thread you've already sideloaded Netflix apk.
folken2003 said:
I have 7,1,1 stock and magisk with safety net pass, follow this steps:
1. Unistall magiks with the Unistaller Zip via twrp
2. Install magiks 12.0 vía twrp
3. Boot your phone, install magisk manager and check the correct install of magisk
4. install the module universal safety net fix (https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431) via twrp
5. DO THIS!! >>> https://forum.xda-developers.com/moto-z-play/how-to/magiks-moto-z-play-t3545473 .
6. Install magisk 13.3 via twrp and the Latest magisk manager
7. Check that the module are actived and run the safety net test
Good luck sorry for my english
Click to expand...
Click to collapse
Wow! Thank you so much, it worked very well here :good:
Thanks for the help guys!
larilieb1793 said:
Wow! Thank you so much, it worked very well here :good:
Thanks for the help guys!
Click to expand...
Click to collapse
Be careful, magisk and magisk hide drain a lot of battery (SO Android) if you don't need safetynet pass dont active the module and magisk hide
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
-=ApA=- said:
Hello!
Device: Mi 10T Pro
Current ROM: miui_APOLLOEEAGlobal_V12.1.2.0.RJDEUXM_cff0da241e_11.0 (Stable)
Android version: 11 RKQ1.200826.002
Bootloader: Currently 15hrs left to unlock
If one wants to root, stick with the stock ROM and possibly get OTA updates (looking forward to MIUI 12.5), what is the best method/option for rooting?
A) Patch boot.img with Magisk and flash it to device using fastboot
B) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to BOOT and install Magisk using TWRP
C) Install TWRP for Mi 10T/10T Pro by Whyle (TWRP_apollo_3.5.0_10-beta_1_whyle) by flashing it to RECOVERY and install Magisk using TWRP
Thank you.
Click to expand...
Click to collapse
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Aldenar said:
I just rooted my Mi 10T Pro and yes, A is the way to go. That way, you preserve your stock recovery while still letting yourself root the phone. Everything works, only after an OTA upgrade to Android 11 came, my phone got stuck in a bootloop, recoverable only by wiping doing a factory reset.
Click to expand...
Click to collapse
You didn't have to factory reset - just have to return to stock before ota - that's required because boot partition is changed by rooting and ota fails... So basically fastest method is flashing stock boot image before ota, making new one with magisk after ota and returning with full root
calinorg said:
A) is the only choice, and you'll have to UNROOT before ota by flashing stock boot partition. C wouldn't work as we do not yet have complete working twrp.
And never flash recovery to boot partition, you'll brick your device, so B) is out of the question. And fastboot boot recovery.img is not the same as fastboot flash option, so take good care...
Click to expand...
Click to collapse
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
-=ApA=- said:
Yes, i understand. Thank you calinorg and Aldenar.
Just so you know, after rooting (even after just unlocking bootloader), your SafetyNet (CTS profile) will fail. Yes, even if you rename your Magisk app, use MagiskHide and MagiskHide Props Config module. Personally it doesn't impact me much, cause even my banking apps are working without issues and my bank does not support NFC payments anyway. Only few apps, including infamous McDonalds app complain and do not run. I guess fast food is alot more sensitive industry than banking then . IMHO there is no point in detecting root in apps anyway. If all of your data is in your servers (with tamper checks), manipulating it on device level (like memory manipulation with games) would be pointless. More and more apps and games nowadays are using the same method. I guess McDonalds and all others alike should just fix their apps instead of blocking out rooted users.
More info on SafetyNet CTS profile failure and possible workaround here. Universal SafetyNet Fix Magisk module.
Since i don't have TWRP installed, im not eager to test SafetyNet fix yet, cause several users are reporting bootloops and problems with banking app security mechanisms. I'm guessing that (problematic) Magisk modules can be uninstalled by other means than just TWRP but still, i will wait for the more stable solution.
Click to expand...
Click to collapse
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Aldenar said:
I am using that exact Magisk module and it works like a charm - The SafetyNet check got downgraded back to Basic that and together with Magisk Hide, works like a charm!
Click to expand...
Click to collapse
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
-=ApA=- said:
Nice, thanks! I'll give it a try. What version of the module are you using? Latest release is v1.1.1 on GitHub.
Click to expand...
Click to collapse
Latest, so 1.1.1. As proof, see screenshots
Aldenar said:
Latest, so 1.1.1. As proof, see screenshots
Click to expand...
Click to collapse
Awesome, thanks!
EDIT: Also working for me just fine.
Any luck on 12.1.5.x or even 12.5 beta?
Illuvitar said:
Any luck on 12.1.5.x or even 12.5 beta?
Click to expand...
Click to collapse
12.5.1.0 was fine, now trying with 12.5.5.0
12.5.5.0 needs Universal SafetyNet Fix module update (i'm using 2.1.1), otherwise SafetyNet check will fail! With 12.5.1.0 it's still working fine with Universal Safetynet Fix 1.1.1 tho.
You will also need to install Riru to use Universal SafetyNet fix 2.1.1
Update:
12.5.12.0 still working. Had to rename magisk.db tho and reinstall Magisk 23.0.
Make sure not to update Magisk beyond version 23!