Hi,
Sprint Note 5 here. Basically I'm just trying to get my phone to be unrooted to pass SafetyNet (Android Pay, Pokemon Go, and others) but have some system modications (adaway and removed boot sounds mainly).
What I did do is flash stock odin firmware, then twrp, supersu, and make my changes. Then if I just unroot with supersu it still fails SafetyNet. If I unroot and tell SuperSU to restore boot.img then I get a bootloop. Probably due to TWRP still being there and not stock Recovery? So I thought maybe from there I can just flash boot and recovery via odin but that didn't seem to work either. Is it possible to take the stock firmware and flash whatever I need except system? Or not possible to alter system and go back to stock boot/recovery?
Edit: I took stock firmware, extracted it, removed system.img, and repacked it up (sboot.bin, modem.bin, recovery.img, cm.bin, boot.img, cache.img) and flashed it . It works but then brings me to some "system update" screen and then stock recovery with a verity failed error. Reboot to device just bootloops. Maybe I need to just remove more than just system?
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Ulti2x said:
Could I have dm-verify disabled, Magisk root with AP working, bootloader unlocked, and twrp all on OOS 4.0.3? What would be the best process for doing this on a brand new 3t with stock OOS 3.5.4?
What I was thinking was first disabling dm-verify on 3.5.4 with fastboot commands, then flash 4.0.3 as it is less than 1 GB, unlock the bootloader, and install magisk and twrp w/ fastboot. Am I missing anything?
Click to expand...
Click to collapse
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Sent from my ONEPLUS A3000 using Tapatalk
uudruid74 said:
Just install FreedomOS, and judging by the performance and battery of 4.0.3 vs the new beta, get the CE version based on the beta. Im downloading it now. Some people are passing SafteyNet
Click to expand...
Click to collapse
What's CE?
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
To simplify this question, could I disable dm-verify and unlock the bootloader on OOS 3.5.4 and boot back into a wiped phone without any problems? After unlocking the bootloader and disabling dm verify, will I able to just update to 4.0.3 using the OTAs in settings?
Or does booting into the phone with an unlocked bootloader and no dm verify cause me to get stuck at boot? Thanks in advance.
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
Click to expand...
Click to collapse
Thanks so much. I don't need to wipe cache after I flash Magisk right? And what's the big deal if the play store detects my device as uncertified?
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Just a small note but you should be able to root without modifying system. They modify boot image now and don't touch system.
Sent from my ONEPLUS A3000 using Tapatalk
Anova's Origin said:
Might as well wipe cache afterwards for good measure.
At the moment, Play Store certification does not seem to affect anything, though you never know when Google is going to start blocking uncertified devices from certain apps.
Click to expand...
Click to collapse
Can I use fastboot commands just by opening command prompt right?
EDIT: This link okay? https://forum.xda-developers.com/showthread.php?t=2588979
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Anova's Origin said:
That tool should work fine.
Be sure to install the correct drivers for the OP3T as well.
Click to expand...
Click to collapse
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Ulti2x said:
With this tool, I should be set for drivers right? https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Click to expand...
Click to collapse
Yep
uudruid74 said:
Not entirely sure what it stands for, but its based on the 7.1.1 beta. Running it now. Not passing safetynet, but it has a checker telling me why. Working on it..
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Ulti2x said:
What's CE?
Click to expand...
Click to collapse
CE stands for community edition
Anova's Origin said:
Unlocking the bootloader does not trigger dm-verity or prevent you from installing via automatic OTA installs. Dm-verity is triggered if you flash TWRP and swipe to allow system modifications, which you will have to do if you intend to to root later.
You can use Oxygen OS's built-in OTA installer to update your phone as long as you have not rooted and have not installed TWRP yet. If you have either rooted or installed TWRP, it would be safer to flash the full ROM through TWRP for upgrades.
That said, everything you listed above can be accomplished. I would advise you take the following steps:
1) Use the phone's built-in OTA updater to upgrade to OOS 4.0.3*
*You can upgrade at a later step, though this way is more convenient as OOS will download and flash the patch automatically
2) Unlock bootloader (this will wipe everything)
3) Either move the Magisk.zip file to your internal storage at this point, or place it on a flash drive which you can access on your phone through USB OTG
4) Flash TWRP 3.0.4-1 through fastboot
5) Reboot to TWRP, swipe to enable system modifications (do not reboot until after you root)
6) Flash Magisk v11.1
7) Reboot into system, download Magisk Manager from the app store if the zip you flashed did not install the app automatically
8) Enable Magisk Hide in Magisk Manager, also hide Magisk from the play store app (prevents it from detecting root and labeling your device as uncertified).
9) Reboot phone for Magisk Hide to take effect.
Safetynet should be able to pass at this point. If you get a dm-verity message during boot, but everything else works perfectly, you can remove the message following this guide. I'm not sure if the stock kernel for OOS hides bootloader status, if you have problems with safetynet, you could try using a custom kernel.
At the moment, I am on OOS 4.0.3 with Franco's kernel and rooted with Magisk v11.1. My bootloader is unlocked and I have TWRP 3.0.4-1 as the recovery. Safetynet passes and my device is listed as certified in the Play Store. I can't test Android Pay as it hasn't been released here yet, though apps that checks safetynet like Pokemon GO work.
Click to expand...
Click to collapse
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Ulti2x said:
My Play Store says uncertified after I did the whole process, and hid Magisk from it. Anyway to fix it?
Click to expand...
Click to collapse
Go into settings, find Play Store and wipe cache. Then reboot.
Anova's Origin said:
Go into settings, find Play Store and wipe cache. Then reboot.
Click to expand...
Click to collapse
Still says it. Maybe I need to wait?
Forgot, I actually had to delete Play Store's app data last time before rebooting. Then it worked.
Thanks a lot everybody! I have never used fast boot before (have only flash w/ sammy phones) and now I know. Thanks again all for helping me.
Guys I'm looking for someway to clean flash 4.1.1 OOS and then get root with magisk and all the safetynet related stuff. Oh, also I should disable the dm-verity warning.
Only I can't find any guide to show me that, anyone who can explain in detail?
Thanks in advance
ruggyboss said:
Guys I'm looking for someway to clean flash 4.1.1 OOS and then get root with magisk and all the safetynet related stuff. Oh, also I should disable the dm-verity warning.
Only I can't find any guide to show me that, anyone who can explain in detail?
Thanks in advance
Click to expand...
Click to collapse
You'll need TWRP installed, so if you haven't got that already, unlock the bootloader and fastboot flash TWRP.
Code:
fastboot oem unlock
fastboot flash recovery <filename>.img
There's plenty of guides around on how to set up fastboot.
After that it's just a matter of flashing the full OTA in TWRP and after that the Magisk zip. Magisk will disable dm-verity.
Install the Magisk Manager, enable Magisk Hide and you're done.
Didgeridoohan said:
You'll need TWRP installed, so if you haven't got that already, unlock the bootloader and fastboot flash TWRP.
There's plenty of guides around on how to set up fastboot.
After that it's just a matter of flashing the full OTA in TWRP and after that the Magisk zip. Magisk will disable dm-verity.
Install the Magisk Manager, enable Magisk Hide and you're done.
Click to expand...
Click to collapse
So I rooted with magisk, no problem but one: I still get the dm-verity warning on boot.
Tried flashing no-verity-opt-encrypt 5.1 but nothing (actuality I don't even know how that works). Help for this? Thanks guys
ruggyboss said:
So I rooted with magisk, no problem but one: I still get the dm-verity warning on boot.
Tried flashing no-verity-opt-encrypt 5.1 but nothing (actuality I don't even know how that works). Help for this? Thanks guys
Click to expand...
Click to collapse
Is it dm-verity or unlocked bootloader warning? They're different...
Didgeridoohan said:
Is it dm-verity or unlocked bootloader warning? They're different...
Click to expand...
Click to collapse
The one that goes "the dm-verity is (or is not?) started in enforcing mode and may not work properly", and then there's red text...
here you go:
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
You can also flash a custom kernel that has dm-verity disabled.
Ok then
Done with that too
Thanks a lot! <3
Hello There,
I know that when I'm writing this, decryption isn't fully working yet and our TWRP still on Alpha Stage.l
(There's Modified vendor to decrypt internal storage on OF recovery thread, but unfortunately my device is Indonesian variant which i didn't see on the download list)
However, changing rom is still possible but i decided to wait until decryption is completely working. I'm going to stick on global rom with unlocked bootloader and magisk installed. Booting device to temporary custom recovery via Adb and flash magisk afterwards
Question :
Is it possible/won't cause any issue to do and OTA update if the situation :
- Unlocked bootloader
- Magisk Installed
- Stock Recovery Installed
Thanks in advance!
galileogarin said:
Hello There,
I know that when I'm writing this, decryption isn't fully working yet and our TWRP still on Alpha Stage.l
(There's Modified vendor to decrypt internal storage on OF recovery thread, but unfortunately my device is Indonesian variant which i didn't see on the download list)
However, changing rom is still possible but i decided to wait until decryption is completely working. I'm going to stick on global rom with unlocked bootloader and magisk installed. Booting device to temporary custom recovery via Adb and flash magisk afterwards
Question :
Is it possible/won't cause any issue to do and OTA update if the situation :
- Unlocked bootloader
- Magisk Installed
- Stock Recovery Installed
Thanks in advance!
Click to expand...
Click to collapse
When an ota arrives
In magisk do the following
- Uninstall Magisk
- Restore Images
Then install OTA . Should be working fine .
To get root again just flash Magisk in a custom recovery like you did before keeping stock recovery.
mak626 said:
When an ota arrives
In magisk do the following
- Uninstall Magisk
- Restore Images
Then install OTA . Should be working fine .
To get root again just flash Magisk in a custom recovery like you did before keeping stock recovery.
Click to expand...
Click to collapse
Ah got it, thanks!
Does safety net gets passed with this method?
Any problems with banking apps and play protect?
crazyguyrohan said:
Does safety net gets passed with this method?
Any problems with banking apps and play protect?
Click to expand...
Click to collapse
I think sweet is using hardware evaluation so the moment we unlock bootloader the safety net becomes invalid .
I am using this module to fix safety net.
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com