Related
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.
i run china k20 pro on indian miui 11.01.0
i installed twrp -21 version
installing magisk 20 provides root access however magisk manager asks to something which results in bootloop to recovery
ignoring that request, the module i wanted to install [energized ] asks for updating to magisk 20.1 which also leads to bootloop to recovery.
is there anything to do ? or just wait for magisk 20.2 to be released and then try it
p.s installing magisk was the only way to prevent redmi recovery from overwriting twrp, i don't know if this has any importance
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
yeah i used magisk uninstaller to make the phone work normally
Glad it worked . Are u able to install magisk again ?
eLcTrOn said:
i'm in kinda similar situation ,
installed magisk v20.1 and everything went fine , but when trying to install viper4android it asked me do install busybox , i did it within magisk now it only boots to fastboot , to fix it and make it boot agian i used magisk_uninstaller.zip
boots fine now but can't install magisk again if i do that it will stuck on fastboot screen .
so for your case i suggest using magisk uninstaller.zip
but hope that some one help to install magisk agian
Click to expand...
Click to collapse
Dont install Viper4android via magisk. Just download the package and install in via TWRP. Use this guide
I have this exact problem right now but even with other versions of magisk, I encounter the same issue. Any suggestions?
Same problem here with magisk I guess it is a compatibly issue with MIUI 11
Yep, it's a MIUI11 issue and the reason I haven't shifted over to it. I suspect whatever release of magisk is in the pipeline will fix it provided it's been reported.
In the meanwhile I've read 19.4 works; you could try the canary builds if that seems to old for your liking... just be careful.
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
winesh said:
Had the same problem, its because of data encryption.
You guys need to format data before installing magisk.
Click to expand...
Click to collapse
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
AvgZing said:
Even with data formatting 20.1 causes issues: In fact, it seems latest Magisk build seems to be causing issues on all (or, many) builds of MIUI 11.
For k20 pro, 19.3/.4 seems smartest to install and then update via magisk manager
I believe other phones (mi 9?) need even older versions like 17.2, so I wouldn't be surprised if future updates continue to push the installation build back.
Click to expand...
Click to collapse
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
droident said:
I'm hoping the Magisk situation gets fixed. I checked the Magisk support thread and only saw one post about a bootloop with a Mi9T Pro (again, likely data encryption) so I'm given the impression MIUI might be off the radar for Magisk bug fixes.
I've had a couple of issues with Magisk 20.1 on MIUI10 - nothing critical but a couple times Magisk Manager has frozen (i.e. kill the process, relaunch and it works) and a couple hangs when root apps have been launched for the first time (again, kill + relaunch, a few times if necessary). Smooth sailing otherwise but gives me the impression that Magisk isn't without flaws on MIUI. One response was to dump MIUI altogether but I'd rather have a stable hardware experience for now. I tested a lot of custom ROMs on my last device and based on that, I'd like to stick to MIUI for a while.
Out of curiousity what are the other bugs with MIUI11 aside from it not working with encryption?
Click to expand...
Click to collapse
Other than standard app compatibility issues, I haven't heard of any major MIUI11 bugs, which is fantastic to hear.
I have tried all sorts. MI9T MIUI 11.0.1.0 and magisk just causes recovery bootloop . Gonna try magisk 19.4 if thats a thing mentioned in a previous reply
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
I got the same problem on my k20 pro (with MIUI EU).I try driffent ways provided by magisk official but no one works.I have to flash the system. It's not a good idea for intalling V4A on this phone
XedosMD said:
I use Miui 11.0.3 together with Magisk. I used the following procedure:
1. Copy Magisk 20.1 (for twrp) to your internal storage (e.g. downloads)
2. Install Magisk via TWRP
3. Don't reboot (it will cause bootloop).
4. Do factory reset (it will remove your Data). Your bootloader will remain patched.
5. Reboot your phone, do initial config.
6. Install Magisk Manager and run it so you will see that Magisk is installed.
7. DON'T install additional files suggested by Magisk Manager (or you will end up in bootloop again)
8. Enjoy your rooted K20Pro!
Click to expand...
Click to collapse
Does your phone remain encrypted after you do these steps? I doubt...
For some reasons, I wanna keep my phone encrypted.
Hi, I'm having k20 pro with miui 12.0.3 android 10. Safetynet fix was success before 13th January 2021. But after that google updated something and safetynet start failing.
Now, I'm dilemma which safetynet fix version should i flash? v1.0.2 or v1.1.1?
JimzFreebies said:
Hi, I'm having k20 pro with miui 12.0.3 android 10. Safetynet fix was success before 13th January 2021. But after that google updated something and safetynet start failing.
Now, I'm dilemma which safetynet fix version should i flash? v1.0.2 or v1.1.1?
Click to expand...
Click to collapse
Try one and then another (uninstall first, install second) - what does it cost (five minures)
zgfg said:
Try one and then another (uninstall first, install second) - what does it cost (five minures)
Click to expand...
Click to collapse
But if my phone goes in bootloop after flashing it, then how to fix it? I don't want to lose my data.
JimzFreebies said:
But if my phone goes in bootloop after flashing it, then how to fix it? I don't want to lose my data.
Click to expand...
Click to collapse
It should not go to bootloop.
Even if it goes, there are couple of ways how to repair bootloop bcs of an errant module, without factory reset - from Magisk go to Github, scroll, open and read Magisk Wiki.
Easist, if you have TWRP, put a "disable" or "remove" (without quotes) empty file to /data/adb/modules/safetynet and reboot - Magisk will disable or uninstall that module.
Or, by booting to Android Safe mode and then rebooting to Android normal mode - all modules will be disabled.
There is also adb command to uninstall all Magisk modules while booting.
All documented in Wiki
It fully applies to the systemless modules (those that use Magisk systemless dynamic mounting instead of hard changing the system partitions) - that modules, when disabled or uninstalled (and rebooted), leave no changes on the system.
SafetyNet-fix is a proper systemless module
Hi, currently my 9t pro has version 12.0.5 (Android 10).
I have root with magisk 25.2 and the twrp version is 3.5.2.9.0 (I point out that, every time I enter recovery, it asks me for the screen unlock pin, without which I cannot access).
I would like to upgrade to version 12.5.2.0 (Android 11).
Do I just boot into twrp, insert the lock screen pin, install the above update, wipe cache and dalvik, install the magisk zip and reboot?
Or am I obliged to update twrp when changing the Android version? The latest version of twrp released for my device seems to me to be 3.6.2.9.0
A thousand thanks
bricca said:
Hi, currently my 9t pro has version 12.0.5 (Android 10).
I have root with magisk 25.2 and the twrp version is 3.5.2.9.0 (I point out that, every time I enter recovery, it asks me for the screen unlock pin, without which I cannot access).
I would like to upgrade to version 12.5.2.0 (Android 11).
Do I just boot into twrp, insert the lock screen pin, install the above update, wipe cache and dalvik, install the magisk zip and reboot?
Or am I obliged to update twrp when changing the Android version? The latest version of twrp released for my device seems to me to be 3.6.2.9.0
A thousand thanks
Click to expand...
Click to collapse
TWRP v3.6.2 should be ok with A10.
On the other side, A11 (AFAIK) will not work with v3.5.2.
Hence better update TWRP
The rest should work the way you descried, just make sure that you upgrade from Global to Global (or EEA to EEA, etc) - ie, not from Global to EEA or so (that would require flashing the Fastboot ROM)
You can also wipe from TWRP:
/data/system/package_cache
PS:
Disable/uninstall Smali Patcher or similar Magisk modules that were specific for the old ROM - to avoid bootloop upon upgrading the ROM and flashing Magisk (if you do not uninstall Magisk, all modules and everything will be back upon your upgrade)
zgfg said:
TWRP v3.6.2 should be ok with A10.
On the other side, A11 (AFAIK) will not work with v3.5.2.
Hence better update TWRP
The rest should work the way you descried, just make sure that you upgrade from Global to Global (or EEA to EEA, etc) - ie, not from Global to EEA or so (that would require flashing the Fastboot ROM)
You can also wipe from TWRP:
/data/system/package_cache
PS:
Disable/uninstall Smali Patcher or similar Magisk modules that were specific for the old ROM - to avoid bootloop upon upgrading the ROM and flashing Magisk (if you do not uninstall Magisk, all modules and everything will be back upon your upgrade)
Click to expand...
Click to collapse
Would you please explain to me how I can upgrade twrp from 3.5.2 to 3.6.2? I also have the official twrp app.
As for the magisk modules these are the ones I currently have installed. Do you think it is better to uninstall magisk directly before entering twrp and flash the new rom and magisk zip?
bricca said:
Would you please explain to me how I can upgrade twrp from 3.5.2 to 3.6.2? I also have the official twrp app.
As for the magisk modules these are the ones I currently have installed. Do you think it is better to uninstall magisk directly before entering twrp and flash the new rom and magisk zip?
Click to expand...
Click to collapse
As usual - TWRP.me, download, find your device, download img and flash to Recovery (you can do from current TWRP or from Fastboot)
Maybe you better disable that liboencrypto module
Or you can try with but study Magisk GitHub Wiki, how to fix the bootloop caused by incompatible modules
zgfg said:
As usual - TWRP.me, download, find your device, download img and flash to Recovery (you can do from current TWRP or from Fastboot)
Maybe you better disable that liboencrypto module
Or you can try with but study Magisk GitHub Wiki, how to fix the bootloop caused by incompatible modules
Click to expand...
Click to collapse
The twrp update flash so I can do it directly from the application?
Instead, to avoid a possible bootloop just uninstall that module? Do all the others give problems?
Thank you.
bricca said:
The twrp update flash so I can do it directly from the application?
Instead, to avoid a possible bootloop just uninstall that module? Do all the others give problems?
Thank you.
Click to expand...
Click to collapse
I never use the TWRP app. Read instructions from TWRP.me
You can uninstall modules. But, plz read and LEARN (it's more useful for the future how to dožisable modules from TWRP - docs I pointed you in the previous post)
I have a Redmi Note 10 pro (Sweetin) Indian Variant and I have rooted it using magisk. Can I get update my device or will face things like loosing root or bootloop?
Device Name: Redmi Note 10 pro
Region: India
Code name: Sweetin
Magisk Version: 26.0
Recovery / Fastboot: Fastboot
OS: MIUI 13
For recovery update/upgrade, not really. You will lose your root yes but that's because boot.img will be replaced by stock ROM, in this case, you'll just have to reflash magisk after. Also, I advise to temporarily disable all modules before updating to avoid bootloops. If bootloop ever happened and magisk modules might be the culprit, just head to /data/adb/ and delete the modules folder.
For fastboot update, yes, root will be lost too.
BigChungus321 said:
For recovery update/upgrade, not really. You will lose your root yes but that's because boot.img will be replaced by stock ROM, in this case, you'll just have to reflash magisk after. Also, I advise to temporarily disable all modules before updating to avoid bootloops. If bootloop ever happened and magisk modules might be the culprit, just head to /data/adb/ and delete the modules folder.
For fastboot update, yes, root will be lost too.
Click to expand...
Click to collapse
If bootloop happens in fastboot update what should I do? I won't be able to go into the /data/adb right?
Hehe_boi said:
If bootloop happens in fastboot update what should I do? I won't be able to go into the /data/adb right?
Click to expand...
Click to collapse
Well yes, but it rarely happens. I recommend upgrading through recovery methods anyways. I've only ever use fastboot when downgrading. Upgrading through recovery ensures that you'd still have access to your data after upgrade.