Database Develop

OTA update with root and TWRP?

hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!

RotesMeerJogger said:
hi! my OP3T is rooted and have a custom recovery (TWRP). now i get an ota update. i have read somewhere in this case its necessary to flash the ota manually in TWRP because i will lost root after this and if i flash it in TWRP i can after ota update flash superSU and will have no problems after reboot the phone.
i have tried this but get "Error 7" in TWRP while flashing ota update. isn't it possible at this way? what is my mistake?
thanks a lot for help and pardon for my bad english!
Click to expand...
Click to collapse
I have a detailed thread already running on how to update here
http://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
I shall keep it up to date with further releases
Sent from Funk Tuned 3T

okay, i have searched in the wrong category thanks a lot for the link!
this thread can be closed.

how can i receive the updates when i root my phone?
and is there anyway to change the emoji without root?

a7mad-911 said:
how can i receive the updates when i root my phone?
Click to expand...
Click to collapse
You should still receive OTA notifications with root. And it should detect you have root, and will download the full update zip, and it will install with TWRP.
Otherwise, you can manually download the full zip update from Funk WIzard's thread which he linked in Post #2 above (which also has detailed instructions on how to update when rooted and TWRP installed).

Works like a charm with magisk 13.6

I just did it with my OP3t and was super easy.
1) download update.
2) go to hidden folder .Ota
3) move zip file to another folder
4) put Magisk in the folder, too
5) reboot to recovery, flash ROM, then Magisk
6) wipe dalvik/cache and reboot
Edit: updated following testing of redpoint73's correct advice

LeighR said:
4) put twrp and Magisk in the folder, too
5) reboot to recovery, flash ROM, then twrp, then Magisk
Click to expand...
Click to collapse
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.

redpoint73 said:
As long as you already have TWRP installed (which is the situation we are talking about) you just need to flash the OTA update zip, then flash Magisk.
Magisk prevents TWRP from being over-written (replaced) with stock recovery. In other words, you don't need to flash TWRP, since TWRP is already there.
Click to expand...
Click to collapse
This means I will keep all apps/settings/files?
Thank you.

JayDz said:
This means I will keep all apps/settings/files?
Click to expand...
Click to collapse
Yes.
Although I will caveat that with my rule of thumb: "hope for the best, prepare for the worst". In that a "dirty" flash of an update is often possible (saving your a lot of work setting up the device again). But you should still be prepared to wipe and do a "clean" install if you run into any problems. So back up your data, by your method of choice, before you try to update.
In particular, for a major update (such as OOS 4.x to 5.x) a clean install (default wipe in TWRP - data, cache and Dalvik) is typically advised.

Shall?? You used the word 'shall' properly in context? Kudos to the school system (I here assume India's) you attended, and to you for paying attention, using the 'King's English' in it's most proper form.

Is it possible for me to have this root combo?

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.

Relock bootloader (with magisk) on the Oneplus 5?

Hello everyone, I've tried to search on the web about this issue since the OTA for Android O is finally out for the Oneplus 5 and couldn't get a satisfying solution. I rooted my OP5 a while ago with Magisk and now that this update is out and tried to install it, It just wouldn´t let me, searching I found that my locked swich to relock the bootloader was because I had to enable it on Magisk, so I opened magisk and couldn´t find that option, and now that I searched on how to enable the "Lock bootloader option" in the Magisk app and found nothing, I'm just out of ideas, so guys, could you help a (noob) brother out with this?
Ps.: If you could attach some screenshots about where to click or what to do, I'll apreciate it a lot (yeah, I'm that stupid when I freak out and don't find how to undo mi mess)

No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the full OTA zip, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.

Didgeridoohan said:
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the update, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Click to expand...
Click to collapse
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?

Fosko Stock said:
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Click to expand...
Click to collapse
Yes.

Help ! Problems with Magisk, root and OTA.

Hi guys I'm a beginner so sorry if i did so many stupid mistakes.
I succesfully rooted my Xiaomi Mi A1 with Magisk about 3 months ago and tried to ignore OTA updates until today
I tried to follow a guide in github which i can't link because i'm new in this foru.
Since i rooted with Magisk i followed the first method
I "restored images" then tried to update but still doesn't work
Then i decided to reboot and then tried to update but it doesn't work
So then i tried to uninstall Magisk by dragging it from the home Just like any other app but didn't work
Then proceded to delete all Magisk folders from my downloads but the update still doesn't work
Then desperately tried to reinstall Magisk but it isn't the v16 version so i tried to install it(i don't know which file i need to select so i tried selcting any image files) says it worked but it didn't so i rebooted and tried over and now i'm stuck with incomplete rooting, non-working Magisk and no OTA update.
I'd like to update OTA and bring back Magisk and root.

Ibra2800 said:
Hi guys I'm a beginner so sorry if i did so many stupid mistakes.
I succesfully rooted my Xiaomi Mi A1 with Magisk about 3 months ago and tried to ignore OTA updates until today
I tried to follow a guide in github which i can't link because i'm new in this foru.
Since i rooted with Magisk i followed the first method
I "restored images" then tried to update but still doesn't work
Then i decided to reboot and then tried to update but it doesn't work
So then i tried to uninstall Magisk by dragging it from the home Just like any other app but didn't work
Then proceded to delete all Magisk folders from my downloads but the update still doesn't work
Then desperately tried to reinstall Magisk but it isn't the v16 version so i tried to install it(i don't know which file i need to select so i tried selcting any image files) says it worked but it didn't so i rebooted and tried over and now i'm stuck with incomplete rooting, non-working Magisk and no OTA update.
I'd like to update OTA and bring back Magisk and root.
Click to expand...
Click to collapse
Why you didn just flash Magisk uninstaller. Zip file?
Poslato sa VTR-L29 uz pomoć Tapatoka

urbanboymne said:
Why you didn just flash Magisk uninstaller. Zip file?
Poslato sa VTR-L29 uz pomoć Tapatoka
Click to expand...
Click to collapse
Sorry, i thought that i could still keep Magisk and root intact if i didn't use the uninstaller.

Ibra2800 said:
Sorry, i thought that i could still keep Magisk and root intact if i didn't use the uninstaller.
Click to expand...
Click to collapse
No you cant. You are lucky you didnt brick your phone. Flash uninstaller and than try OTA update. Download TWRP for your phone/new rom and flash working Magisk again and root phone. Is simple. Of course, if you are on TWTP you will be unable to OTA update your phone. You need stock recovery or wait for ZIP flash file of newes rom
Poslato sa VTR-L29 uz pomoć Tapatoka

@Ibra2800 There's no need to uninstall Magisk to update with an OTA. There are however a few prerequisites that need to be fulfilled:
You need to have the stock boot image installed. That can be done by using the restore images option in the Manager or manually flashing the boot.img file with fastboot or equivalent.
You need to have the stock recovery installed. This means the OTA will fail if you have TWRP or another custom recovery installed. Either keep the stock recovery installed and only boot the TWRP image when necessary (the fastboot boot command), or you make sure you restore the stock recovery image when you need to update.
You also need to have a few important partitions on your device untouched. Those include (but may not be limited to) /system and /vendor. If you've so much as mounted these as rw, the OTA will fail. This one can be tricky, because if an app has root access it can easily do this without you noticing.
If you manage to fulfill the above, you should be able to update your device. If the A/B method from @topjohnwu's OTA tips didn't work, use the general case instructions instead.
Right now, it sounds like you need to start from scratch though...
If you can get a hold of a full firmware file for your device, you might be better of flashing that instead. Or, wait for a flashable update, as stated above. And if you want to reinstall Magisk you might have to first uninstall it, to start clean. Use this uninstaller.

Thanks for trying to help me
Sorry to ask but i just can't wrap my head around it, how am i supposed to use the uninstaller, what are the steps ? Also i only user Magisk so i think i don't have any custom recovery and don't know what's TWRP purpose.

Ibra2800 said:
Sorry to ask but i just can't wrap my head around it, how am i supposed to use the uninstaller, what are the steps ? Also i only user Magisk so i think i don't have any custom recovery and don't know what's TWRP purpose.
Click to expand...
Click to collapse
The uninstaller is a zip that you flash in a custom recovery (i.e. TWRP) to uninstall Magisk completely. You should also be able to use the "Complete uninstall" option in the Magisk Manager.
TWRP is a custom recovery that you can use to make backups of your device partitions (so you don't loose any data if anything goes wrong, it's highly recommended to make regular backups in some way) and install custom ROMs and other modifications to your device. You can either install it permanently or just boot it whenever you need it (there are likely gonna be guides about this in your device's forum).
Since you seem to be quite new at this, I would suggest that you take some time to browse through your device's forum and familarise yourself with things like ADB, fastboot, custom recoveries, custom kernels, ROMs, etc. And if you have more questions like this, it's often best to ask them in the device forum, since there sometimes are device specific things that need to be done for everything to work right.

Rooting Moto G6 with PPS29-118-15-11. What versions of noverity, twrp, magisk to use?

Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.

Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.

pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.

SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!