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.
Related
Is there any way to use Android Pay on rooted device?
OOS 4.0.2
franco Kernel (I have red that it baypass unlocked bootloader for Android Pay?)
TWRP
Root (SuperSU)
I tried to turn off root in SuperSU but it still detects root or unlocked bootloader
extra2 said:
Is there any way to use Android Pay on rooted device?
OOS 4.0.2
franco Kernel (I have red that it baypass unlocked bootloader for Android Pay?)
TWRP
Root (SuperSU)
I tried to turn off root in SuperSU but it still detects root or unlocked bootloader
Click to expand...
Click to collapse
Remove SuperSU, download magisk 11 - flash it (contains its own root solution). Franco kernel is all good., When your back in your phone, install magisk manager from the play store, open it, go to settings, enable magisk hide and reboot and you should pass the safetynet test (look on play store for safetynet its the first app with a green square icon). If you pass that, your all good!
just only tipp (i don't use Android Pay) - SuperSu also has a hide similar functionality - Options >> Enable Superuser []
... i'd first try it, instead of uninstall/replace
Hmmmm.... I tried to unroot in SuperSU, now my device stay stuck at the splash screen and won't boot. I'm on FreedomOS, I guess it's incompatible; just a heads up to those users.
EDIT: Nevermind, flashed the zip and all is well!
manor7777 said:
Remove SuperSU, download magisk 11 - flash it (contains its own root solution). Franco kernel is all good., When your back in your phone, install magisk manager from the play store, open it, go to settings, enable magisk hide and reboot and you should pass the safetynet test (look on play store for safetynet its the first app with a green square icon). If you pass that, your all good!
Click to expand...
Click to collapse
I hope I don't need to wipe all data?
EDIT:
And one more thing: would Android Pay work on FreedomOS?
extra2 said:
I hope I don't need to wipe all data?
EDIT:
And one more thing: would Android Pay work on FreedomOS?
Click to expand...
Click to collapse
I'm using it right now! Latest FreedomOS, and Magisk 11 to root. I didn't wipe all data, i just didn't install SuperSU when i installed FreedomOS and instead installed Magisk as it has its own SU solution. Easiest way do it and i use android pay more than once a day!
manor7777 said:
I'm using it right now! Latest FreedomOS, and Magisk 11 to root. I didn't wipe all data, i just didn't install SuperSU when i installed FreedomOS and instead installed Magisk as it has its own SU solution. Easiest way do it and i use android pay more than once a day!
Click to expand...
Click to collapse
Thanks, I'm gonna flash FreedomOS and do as you said. It's just you know I'm on the stock OOS and it'll be first custom ROM for this phone (yes it's again oos but anyway). I'll let you know if it (android pay) works for me
[EDIT]
Yeah dude, works great. Thanks
Hey everybody I rooted my device this morning, and I was setting everything up again since it gets wiped during the process. So finally I come and try to login in to Snapchat and it says something similar to "log in has failed please try again later" anybody have this problem or a way to fix it? Thanks in advance!
Snapchat checks for root and purposely prevents you from logging in if it find it. If you rooted with SuperSU, try installing Chainfire's SUHide. Otherwise, if you rooted with Magisk, enable MagiskHide in Magisk Manager.
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
martinsavvy said:
I usually unroot with SU and login while unrooted, then flash whatever SU zip used to root again. It should work and you'll stay logged in.
Click to expand...
Click to collapse
so i just do the full unroot option, sign in, then just flash the SU again?
sakumaxp said:
so i just do the full unroot option, sign in, then just flash the SU again?
Click to expand...
Click to collapse
Yeah that's what works for me.
martinsavvy said:
Yeah that's what works for me.
Click to expand...
Click to collapse
OMG thank you so much that was so easy!!!!
magisk is better though because you can still use android pay and mobile banking applications.
If I throw on a custom ROM after wiping will I need to do this process again?
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
Anova's Origin said:
Yes. Unless the custom ROM has built-in root, you will have to flash SuperSU or Magisk every time you flash a ROM (including updating the same ROM to a newer version). Flashing a ROM replaces the files required for root in the /system or /boot partition.
Click to expand...
Click to collapse
I shouldnt brick if i have to loose root and reflash super SU when I'm running a rom right? Sorry for all the questions
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
Anova's Origin said:
Suddenly losing root without a reasonable explanation would be a cause for concern and should merit further investigation.
However, simply flashing SuperSU after flashing a ROM (dirty or clean flash) shouldn't cause any issues.
Click to expand...
Click to collapse
Yeah cos I would need to flash the ROM, then sign in to Snapchat, then go back to TWRP and flash super SU
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you dirty flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. ROMs like OOS will either replace TWRP with stock recovery or trigger dm-verity if you don't root immediately after clean flashing.
Anova's Origin said:
Honestly, I would just recommend you to use Magisk to root. You can have it hide both root and itself from apps like Snapchat. Better yet, since Magisk Manager is not a system app, it will survive updates through dirty flashes. This means that after the initial set up, any time you flash a ROM and then Magisk immediately afterwards, root is already set up and hidden from Snapchat the first time you boot up.
Also, be careful with flashing a ROM without rooting immediately. You might trigger dm-verity if you clean flash a ROM like OOS without rooting before booting.
Click to expand...
Click to collapse
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
sakumaxp said:
So I just have to download magisk manager and it should re-do everything for me if I understand correctly right?
Click to expand...
Click to collapse
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
Anova's Origin said:
You will have to remove all traces of SuperSU before flashing Magisk. If Magisk detects systemless SuperSU already present on your phone, it won't root it with its own method (and therefore cannot hide root from other apps). The easiest way to install Magisk over SuperSU is just to dirty flash your current ROM and then immediately flash Magisk v11.1 (don't forget to wipe cache/dalvik). After you boot, you will have to install the Magisk Manager app from the playstore if the Magisk.zip didn't already do so automatically. Then enable Magisk Hide and reboot your phone. Root should be hidden now. You will have to regrant root permissions for all of your root apps.
Click to expand...
Click to collapse
I'm on stock ROM, so I guess I can go into super su and loose root then download magisk and get it that way
Thanks mate, it took forever to find this solution, it worked!
I use SU and it was simple to "unroot" from within the SU# app
1. settings scroll down to the "cleanup" section, select full unroot, accept all the warning messages, the phone will reboot into recovery and then reboot the phone after it finishes. Your phone may cycle through the reboot process a couple of times
2. log back into your phone, then you can log into the Snapchat app.
3. now you can re-root your phone, if you want to.
Cheers.
im on OOS 4.1.0
so i unlock bootloader, then which twrp should i flash?
after this what should i flash? just the latest zip off this thread, or the dm verity thing aswell?: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
how will android pay work then? and also will snapchat work with this
If you want Android pay to work you need to root with Magisk and enable Magisk Hide.
Don't flash the verity zip or modify your system partition!
chandyy said:
im on OOS 4.1.0
so i unlock bootloader, then which twrp should i flash?
after this what should i flash? just the latest zip off this thread, or the dm verity thing aswell?: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
how will android pay work then? and also will snapchat work with this
Click to expand...
Click to collapse
You will need to install a kernel which bypasses dm verity check. Version of twrp does not really matter here, but as always its recommended to be on the latest version.
This is what I do:
1. Install Stock OOS. Don't reboot.
2. Install TWRP using image file as you may have lost that.
3. Reboot now and setup your stuff(minimal or as much as you want, doesn't matter)
4. Reboot to TWRP
5. Flash Magisk (easiest systemless root option)
6. Reboot
7. Install Magisk Manager and hide it.
8. Reboot
9. Install franco kernel and reboot.
10. Check SafetyNet in Magisk Manager.
You are good to go.
chandyy said:
im on OOS 4.1.0
so i unlock bootloader, then which twrp should i flash?
after this what should i flash? just the latest zip off this thread, or the dm verity thing aswell?: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
how will android pay work then? and also will snapchat work with this
Click to expand...
Click to collapse
I am rooted and I use Android Pay all the time. In general, I:
-Flashed TWRP 3.0.4-1 (3.1.0-1 also works fine)
-Flashed the Freedom OS ROM 2.6.1-1which includes a Root app called Magisk. Read the Freedom OS ROM Thread Original Post (OP) to understand it.
-You will have to go into the Magisk app once you are back up and running and use the settings to "Hide Magisk". You will also have to go in to Magisk setting s and tick a box next to each app you want to "hide" root from. (Android Pay, SnapChat". The Magisk app also has a mechanism to ensure that the device will pass SafetyNet checks. It is not necessary to flash any additional root apps like SuperSu (which, BTW, is NOT open source).
The Freedom ROM 2.6.1-1comes with a very nice installer called Aroma. It is very polished and is basically a nicely customized (but not overdone variant) of the original Oxygen OS. I was all about CyanogenMod and Lineage before, but this OS and its install and its Magisk integration works great and I am not having to deal with firmware mismatches, nightly build bugs, etc.
The Freedom OS includes all of the Google Apps (gapps) so that you can select from among them without having to separately flash a GAPPS package. MAKE SURE YOU SELECT GOOGLE CHROME during install and save yourself some trouble.
Enjoy. My experience with it has been smooth and I never thought I would move off of Lineage OS, but Freedom OS is very well done and I can use Android Pay
jasleen_ss said:
You will need to install a kernel which bypasses dm verity check. Version of twrp does not really matter here, but as always its recommended to be on the latest version.
This is what I do:
1. Install Stock OOS. Don't reboot.
2. Install TWRP using image file as you may have lost that.
3. Reboot now and setup your stuff(minimal or as much as you want, doesn't matter)
4. Reboot to TWRP
5. Flash Magisk (easiest systemless root option)
6. Reboot
7. Install Magisk Manager and hide it.
8. Reboot
9. Install franco kernel and reboot.
10. Check SafetyNet in Magisk Manager.
You are good to go.
Click to expand...
Click to collapse
thanks
this worked a treat for anyone wondering aswell
Hey everyone. I just got my new OnePlus 3T a week back. I was loving it till today but I wanted to mess with my phone and I guess I did just that. Long story short, I was on 7.1.1 and unlocked OEM and installed TWRP. Phone booted up and i went into recovery and installed Super SU and the dm verity. After this step, my phone is stuck on the boot animation. I'm able to access TWRP as well as Fastoot ADB. I want to sideload the stock OxygenOS ROM into my phone through ADB, but i'm unsure which file to flash and the exact process. Could someone please help me out? :crying:
That's why you always make a nandroid back up
I figured out why the adb sideload wasn't working. I tried to do the sideload directly from the ADB cmd while my phone was in fastboot mode. So, I tried an alternate method by going into TWRP and doing the sideloading from the advanced menu. It worked and I'm setting up my OP 3T now Guess I jumped the gun by posting here without thinking.
On a side note, my device doesn't have root access now. Maybe it never got installed properly before getting bricked. I think it had to with the fact that I had updated to 7.1.1 by using a VPN. I'm pretty good at following instructions so i couldn't have gone wrong. Can anyone tell me if i can go ahead and root my device now that I'm back on stock OS?
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
kunal1540 said:
You dont flash supersu and dm verity files at the same time
No wonder you end up in bootloop
Multiple threads are already there about the same issue.
For root just flash supersu
Click to expand...
Click to collapse
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Rahulsingh9367 said:
Damn, I didn't know that. I only searched for the bootloop issue and didn't really find something that seemed simple enough for me. Almost all the guides I read had similar instructions so I flashed the Dm-verity first and then the Super SU immediately after that. What does dm verity do if it doesnt need to be flashed? And just so that I'm clear - flashing Super SU is enough and no need to bother with the dm verity?
Click to expand...
Click to collapse
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
fluster84 said:
There's a much much simpler solution, you just use magisk. There's no need to flash supersu or dm-verity fix, just flash the latest magisk zip file in TWRP -> reboot -> install Magisk manager from playstore and you have perfectly working rooted phone.
Click to expand...
Click to collapse
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Azar_98 said:
Try the latest version of magisk, v11.6.
http://tiny.cc/latestmagisk
Click to expand...
Click to collapse
Worked perfectly and no hassle at all. Thank you so much!
Rahulsingh9367 said:
Tried flashing the Magisk v9 zip and checked the option that goes something like "verify after flashing" and it failed. Should I uncheck both those options before flashing or flash the phh super user zip too?
Click to expand...
Click to collapse
Always flash the latest magisk, and you don't need to flash phh or anything else. Magisk now comes with magisksu that works great with OOS 4.1.1.
Check the link below for latest magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless
If you don't mind losing your data, you can try this 100% clean but slightly painful install. It might be overkill for most but you can start from a clean slate. Backup your stuff to the PC before you do this.
1. Flash compatible stock recovery (stock recovery for android N) in fastboot
2. Now choose to wipe everything (even music, photos) from stock recovery. You will lose everything on your phone.
3. Sideload OOS 4.1.1 rom
4. Reboot and complete phone setup
You are now completely stock except with a unlocked bootloader. In order to gain root, continue further -
5. Enable developer options in Settings and then enable Advanced Reboot and USB debugging
6. Reboot to fastboot and flash twrp 3.0.4.-1
7. Reboot to twrp and flash Magisk v11. 1 zip
8. Reboot and install Magisk Manager from playstore.
Congratulations, you have a stock 4.1.1 with working root and it will even pass safety net check (enable magisk hide in magisk manager)
Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.
swangjang said:
Hi all,
TLDR QUESTION: do I have to "fastboot flash boot magisk_patched_boot.img" every time after "adb sideload ota_file.zip" ?
-------------------------------------------------------------------------------------------------------------------------------------------------
I'm coming over from only using samsung galaxy series to Pixel 5.
I've always used custom roms with root and whenever there was an update available, the usual process was:
1. Flash updated rom.zip
2. Flash magisk.zip
Done.
I assume it's a similar process for pixel phones and I intend to stay on stock rom with root.
I need to pass safetynet for google pay so I have to change the device fingerprint to Pixel 3a to bypass hardware attestation (as written on this forum guides).
1. Does changing the fingerprint to 3a break the on-device OTA updates?
2. Does changing the fingerprint to 3a break updates for Pixel 5 apps?
3. After an OTA update, (either by on-device or sideload), do I have to re-flash the magisk patched boot.img to retain root?
4. Also, if I decide to un-root, does bootloader re-locking also require a device wipe?
Thank you.
Click to expand...
Click to collapse
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.
dirtyreturn said:
This may help. https://forum.xda-developers.com/pixel-5/how-to/tutorial-unlock-bootloader-root-valid-t4178673/page1
For bootloader, I'm pretty sure that relocking would wipe the device. I think unlocking it wipes the device.
Though, it's not entirely necessary, I think, to relock the bootloader after unrooting. I think, for preference of complete security over device. I believe it disallows device modification.
Click to expand...
Click to collapse
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.
swangjang said:
Hi, thanks for your response however I have already read that guide but it does not answer any of my questions.
Click to expand...
Click to collapse
Oh, sorry.
1) I think it changes a build.prop entry for device manufacturer or model.
2) Pixel 5 apps? Do you mean specifically designed for this device? I have a 3xl also, and I think and it seems, that stock apps are the same. Ah, for example, the Google stock camera app - I am not sure if a Pixel 5 specific feature would disappear or not work or something.
3) I THINK you will need to. Like, at least with elementalx and kirisakura kernel the (?)script(?) looks to see if Magisk is installed and retains it. I am assuming the Google stock kernel does not .
4) unlocking the bootloader wipes the device, I believe. I would assume relocking the bootloader would. Personally, I've never relocked the bootloader on any device after unrooting . If you do relock, back up your internal storage as an incase , failsafe, or general rule or something.
Hopefully, there will be someone to chime in in case I am wrong.
Hi, i don't use OTA but full image for update but no, it don't break change props on pixel 5 but yes you need to flash magisk again.
Good update. No issues for november update
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.
cescman said:
As the december system/security update is coming, may I confirm the correct way to update:
1. disable all magisk modules, unhide magisk manager
2. Flash newest factory image, or flash OTA zip
3. reboot, and you get an updated but unrooted device
4. root the device as usual with magisk
5. Reapply all the magisk modules you use
Click to expand...
Click to collapse
With the Pixel 2 my process was
1. fastboot flash stock boot and dtbo images for your current build version. (Not sure if dtbo is really needed)
2. Apply OTA via ADB
3. Allow phone to boot and finish update
4. Use magisk to patch the boot image from the new build version
5. fastboot flash patched boot image.
I have used this method for three years with the Pixel 2 and only had one issue. I used smalipatcher to make mock GPS look like real GPS and apparently the magisk module needs to be re-created for each build.
j0nnyd said:
That's typically the way I've always do it except you do not unhide MM. I also modify the batch file named ‘flash-all.bat’ and remove the ‘-w' so it doesn't wipe my device.
Click to expand...
Click to collapse
I do this as well, but couldn't get the boot image patched through magisk for some reason. Anyone have a patched boot image they can share?
I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.
*deleted*
TonyApuzzo said:
I hope to get a more streamlined solution eventually, but this is what I did to upgrade my Unlocked Pixel 5:
Download factory image
Unzip
Edit "flash-all.bat" to remove the "-w", save as "flash-nowipe.bat"
plug in phone and enable debugging
adb reboot bootloader
flash-nowipe.bat
unzip "image-redfin*" into a temp folder
cd into the temp folder
adb push boot.img /sdcard/Download/boot.img
on phone run Magisk Manager and patch /sdcard/Download/boot.img
adb pull /sdcard/Download/magisk_patched.img
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
I didn't need to uninstall / reinstall any modules, they were all there after the final reboot. I did have to uninstall / reinstall vanced using vanced manager to get it working.
Next time I will try patching the boot image and repacking so I need fewer reboots.
Click to expand...
Click to collapse
1. What's your build.prop before upgrade?
2. Did you uninstall Magisk (restore/complete) before upgrade?
3. If #2 is 'NO', did your 'Restore Magisk Manager' and disable 'MagiskHide' before upgrade?
Thank you very much!