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.

Flash OOs Oreo Stable release

Folks,
Seeing alot of comments about bootloops, etc after trying to install the new stable OOS Oreo release.
I went through the same issue myself and found the following method to work best.
PLEASE NOTE: I'm not responsible if this does Any type of damage or issues to your device.
Be sure to backup all you need to back up to your PC.
1. Complete wipe of phone.
2. Flash the stock recovery that was used for reverting from Oreo Beta to Nougat. http://oxygenos.oneplus.net.s3.amazonaws.com/OP5_recovery.img
3. Wipe everything again.
4. Sideload new Oreo release. (Credit @HatRiGt, https://drive.google.com/open?id=1NW5zyUOL6bWgUWozFGLiutzud203npKp)
5. Reboot to bootloader and flash the Chinese TWRP. https://drive.google.com/open?id=1AKbC4HB0h4rEldQUowWGdyM4iYBVV--7
6. Reboot to recovery and flash Magisk. I flashed the 14.6 version and haven't found any issues yet. (https://forum.xda-developers.com/attachment.php?attachmentid=4366826&d=1513897917)
7. Boot phone.
I cannot promise this will work for you, but it has done the job for me.
Running Oreo Stable with Magisk 14.6 and restored all apps from Titanium Backup that I saved on my PC.

I highly suggest blu_spark TWRP instead of chinese one, and i think this method is ONE of the other working way

Couldn't get mine to work with blu spark, hence why I had to use chinese

Link for Chinese twrp please

Thank you very much, work for me

Make a video of it please

New Magisk v.15.
Thanks to topjohnwu.

joecaesar said:
Link for Chinese twrp please
Click to expand...
Click to collapse
Added to OP.

All is well. And with google Drive almost all data is back.

Nice & easy workaround..
Step 5 has to be : install TWRP on fastboot mode...

@hallo dare
Any chance you can make a very detailed video about this process?

cultofluna said:
Nice & easy workaround..
Step 5 has to be : install TWRP on fastboot mode...
Click to expand...
Click to collapse
Yes, sorry. Amended text now.

lvints said:
@hallo dare
Any chance you can make a very detailed video about this process?
Click to expand...
Click to collapse
No real need for a video mate, just follow the post step by step and you're golden!

I can not sideload Oreo zip, it says can not read

Lvsitano said:
I can not sideload Oreo zip, it says can not read
Click to expand...
Click to collapse
You should try changing the TWRP

If you have problems with adb sideload:
Boot into fastboot and install stock .
Unlock/Lock your Phone and unlock it again. Locking will wipe the whole phone.
After this you can make a clean installation.
Reboot to bootloader and flash the Chinese TWRP and boot to Recovery.
Install the oreo.zip file.
Reboot to System.
Make your Setup: WLAN, GMail Account aso.....
After all boot to Recovery and install Magisk

Very easy, put oreo zip file in the root folder, backup all data, flash stock recovery, boot with stock recovery, wipe cache, upgrade internal..., Select oreo zip file and flash it, then back and select wipe, select erase every thing and reboot. Done.

Thank you so much! I finally got it working. I needed to do a factory wipe and skip the magisk installation but it worked!
Cheers!

nikoeuren said:
Thank you so much! I finally got it working. I needed to do a factory wipe and skip the magisk installation but it worked!
Cheers!
Click to expand...
Click to collapse
Magisk won't flash on stock recovery, if that's the reason you had to skip installing it.

hallo dare said:
Magisk won't flash on stock recovery, if that's the reason you had to skip installing it.
Click to expand...
Click to collapse
No I installed the TWRP and flashed magisk. It refused to boot so I factory swiped it and all was good. Now I have to figure out how to install magisk without getting into bootloop.
Sent from my ONEPLUS A5000 using Tapatalk

TWRP gets replaced by stock recovery

So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks

Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?

Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks

pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).

gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.

pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.

gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.

How to update without losing TWRP and root?

Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance

MagikGab said:
Hello, I have a Mi 9T Pro with 10.3.3, TWRP and Magisk. I received the update to 10.4.0. As stated in the title, how could I update the system without losing the TWRP and root through Magisk? Thank you in advance
Click to expand...
Click to collapse
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.

Robbo.5000 said:
You can't. The best way to update is to download the 10.4.0 recovery ROM, then flash that in TWRP. This will still overwrite Magisk, so you will need to install that again straight after installing the update. If you don't install Magisk immediately, then booting into system would also restore stock recovery, so it needs to be done before you reboot to system.
Click to expand...
Click to collapse
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?

i have the same question too..

MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.

MagikGab said:
Many thanks! In this way I could at least save the TWRP! Should I have to take some other precautions? Like deactivate all Magisk modules, perform a backup of apps ecc?
Click to expand...
Click to collapse
P12AV33N said:
No, you can simply flash the ROM and right after that, flash Magisk. This way you won't loose twrp or Magisk.
Click to expand...
Click to collapse
I would just add to this that, although this is all that is required, I would still backup things, just in case.
It's always good practice when flashing things to backup what you can, even when it's not needed should things go smoothly. It only takes an absent minded moment of stupidity in TWRP to do some serious damage. As many people, myself included, can vouch for.

Thank you everyone!

I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15

macanovic88 said:
I've read a lot about this, some say it's better with fastboot rom and Miflash, but twrp method with recovery seems to be easier method.
Can anybody confirm is it necessary to remove compatibility.zip file from flashable zip file before flashing?
Clean flash or dirty should work for 10.3.4.0 update?
I'm using 9T Pro (EU), rooted, stock 10.3.3.0, TWRP 3.3.1-15
Click to expand...
Click to collapse
Flashing a minor update is fine to do as a dirty flash in TWRP.
Doing a major update is 50/50 (going from 10.3.x to 10.4.x as it's s change from Android 9 to 10, or going from 10.x.x to 11.x.x). You may be fine, you may have issues. It might be a better option to try using the 'save data' option in the Mi Flash Tool, which is the same as a dirty flash, but will still update vendor and firmware files, should they have changed between the versions.
You might be guided by what the OTA would do. Occasionally when an OTA provides a major version change, it will perform a clean flash and give you big warnings that this will happen first. If an OTA tells you this will happen, then I would definitely use the Mi Flash Tool and use the 'clean all' option.
As for the compatibility zip, it depends on the TWRP you are using. Just try as is first and if your get an error about the wrong device, then remove it and try again.

Thanks a lot, your answers are very helpful in this thread! ?

I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.

cgdams said:
I got the OTA update to 10.3.4.0 on my Mi 9T Pro, too, but it wouldn't install via TWRP (mauronofrios version 3.3.1-15). I also tried to flash the full 10.3.4.0 ROM (https://bigota.d.miui.com/V10.3.4.0...EAGlobal_V10.3.4.0.PFKEUXM_964826982c_9.0.zip) with TWRP, but that didn't work either, not even after removing compatibility.zip.
I then changed my TWRP to OrangeFox Recovery 10.0_7 stable (via fastboot) and dirty flashed the full ROM via OrangeFox. That worked flawlessly, it even seems that it will be able to install future OTA updates, but that remains to be seen when the next OTA update arrives.
Click to expand...
Click to collapse
You need to confirm if orangefox is actually ready for OTA by checking in its settings.
Sent from my Redmi K20 Pro using Tapatalk

Can i Install Magisk using temporary twrp ?

Can i install magisk through temporary twrp (using fastboot boot recovery xxx.img) in my poco f 1 ?

The answer to that would be a definite maybe.
Joke aside, that should work fine as long as TWRP is otherwise working as it should. There's no difference in functionality between flashing or just booting TWRP.

Why not flash it directly? That is, if there is a twrp for your phone.
As to Magisk, ask XDA
Sent from my SM-A605FN using Tapatalk

pr1jker said:
Why not flash it directly? That is, if there is a twrp for your phone.
As to Magisk, ask XDA
Click to expand...
Click to collapse
But i want to flash OTA
And before flashing OTA i will uninstall magisk

Didgeridoohan said:
The answer to that would be a definite maybe.
Joke aside, that should work fine as long as TWRP is otherwise working as it should. There's no difference in functionality between flashing or just booting TWRP.
Click to expand...
Click to collapse
If i flash temporary twrp , i can flash my OTAs too
I seen some of the people following this,
Flashing temporary twrp and flashing magisk and whenever OTA receives they are simply uninstalling magisk and flashing OTA.
Here my question if i go with this magisk will work perfectly or not ?

@Nicky Cheer There should be no issues with that setup. If you haven't already, I'd advice you to also take a look at @topjohnwu's OTA instructions.

Didgeridoohan said:
@Nicky Cheer There should be no issues with that setup. If you haven't already, I'd advice you to also take a look at @topjohnwu's OTA instructions.
Click to expand...
Click to collapse
Tq @Didgeridoohan and @topjohnwu for clarifying
But one more doubt what is the difference between restore image and complete uninstall under magisk manager ?

Nicky Cheer said:
Tq @Didgeridoohan and @topjohnwu for clarifying
But one more doubt what is the difference between restore image and complete uninstall under magisk manager ?
Click to expand...
Click to collapse
Restore image - only restore the stock boot image and leave all Magisk internals intact.
Complete uninstall - remove everything Magisk related from your device.
First option is preferred, since you then won't have to set everything up again afterwards.