Database Develop

OTA update with TWRP

Hi,
I have done root using TWRP and set TWRP as permanent recovery.
Now, yesterday new EUI 5.8.x OTA is downloaded but not able to flash it.
kindly guide how to update using TWRP.

acharya.tejas said:
Hi,
I have done root using TWRP and set TWRP as permanent recovery.
Now, yesterday new EUI 5.8.x OTA is downloaded but not able to flash it.
kindly guide how to update using TWRP.
Click to expand...
Click to collapse
For OTA updates you need stock recovery

Or download the full rom and flash thorthrough twrp

Yes i agree. You need one of the above mentions. Either you should have a stock rom or flash the whole firmware update version.
Sent from my Le X526 using Tapatalk

Can not upgrade to B390 (C432)

Hi,
I'm on C432, unlock bootloader. (It's a debranded phone).
I can't update. to B390.
I did a clean install of B386 using TWRP (flash the 2 zip file, clean cache). B386 works fine.
Update from phone did upload the B390 update, it rebooted into Huawei recovery and it failed at 12%. "Software installed failed".
So I've tried with TWRP (I have downloaded the B390 from Firmware finder) and it fails on update.zip with an error 7.
I've tried various versions of B390 (from Firmware finder) and they all fail when trying to install update.zip from TWRP.
Flashing back B386 with TWRP works (no errors when flashing update.zip).
It seems the update.zip from B390 tries to look for something missing in my phone....
Any ideas ?
Thanks !

XavierP56 said:
Any ideas ?
Thanks !
Click to expand...
Click to collapse
Stay on B386 unless you're really keen for the latest security update.
Peace.

I can' t even go back to B182, B383. Only B386 I can install (hopefully). This tells me that something is corrupted in my phone.
I have the following error with TWRP:
assert_failed: block_image_verify("/dev/block/platform/hi_mci.0/by-name/system", "package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
ERROR 7
With other update.zip, I also have
assert(update_huawei_pkg_from_ota_zip("UPDATE.APP"));
What's wrong in my phone ?

https://forum.xda-developers.com/p9/how-to/update-method-problems-to-version-t3660717

albelushi7 the problem is that update.zip fails with TWRP because of the assert.
I guess the problem is because my VENDOR, PRODUCT, VERSION are probably corrupted (or may be other partitions).
I can't flash them using fastboot.
I looking for a TWRP backup of these partitions for a L09C432 model. Can someone share a backup of these partitions ?
(Even a full backup with B390 installed for a L09C432 would be great !)
Thanks !

I'm going crazy with this. Tried to rollback to MM everything time I try to flash, it fails.
Either by
- TWRP : Update.zip fails with ERROR 7
- Huawei updater + HiSuite
- 3 Button methold and dload folder.
I can only flash B386. It works fairly OK but with some random crashes.
I don't understand what's wrong with my phone. It was an Orange phone, debranded to C432. I had several updates without any issues and problem came since B383.
Could not update with Phone updater to B386. Did with TWRP. But now, I can't install anything. Only B386 can be installed !!!

XavierP56 said:
I'm going crazy with this. Tried to rollback to MM everything time I try to flash, it fails.
Either by
- TWRP : Update.zip fails with ERROR 7
- Huawei updater + HiSuite
- 3 Button methold and dload folder.
I can only flash B386. It works fairly OK but with some random crashes.
I don't understand what's wrong with my phone. It was an Orange phone, debranded to C432. I had several updates without any issues and problem came since B383.
Could not update with Phone updater to B386. Did with TWRP. But now, I can't install anything. Only B386 can be installed !!!
Click to expand...
Click to collapse
same thing happen with my phone. now, i use c185 with b390. you should try the same.

So you flashed the OemCust for C185 and it worked ? Good to know !
You were on C432 before ?
Did you try revert back to your original OemCust ?
Thanks !

Hi! I had the same problem. I solved it in this way:
Backup app+data with titanium
Revert to MM with the official procedure, upgrade via updater to nougat and install, always via updater the updtes until B390. Works everything.
The I reunlocked bootlader via adb, install twrp, rooted and restore apps with titanium.
Long procedure, but it worked

rikiki81 said:
Hi! I had the same problem. I solved it in this way:
Backup app+data with titanium
Revert to MM with the official procedure, upgrade via updater to nougat and install, always via updater the updtes until B390. Works everything.
The I reunlocked bootlader via adb, install twrp, rooted and restore apps with titanium.
Long procedure, but it worked
Click to expand...
Click to collapse
How lucky ! I did install MM Rollback and then MM (C432B136). I was on stock recovery and bootloader locked.
Update B136 -> B160 : Ok
Update B160 -> B182 : Failed
Now I can barely install anything (B386 anymore, it used, now it doesn't). Only TWRP...

XavierP56 said:
How lucky ! I did install MM Rollback and then MM (C432B136). I was on stock recovery and bootloader locked.
Update B136 -> B160 : Ok
Update B160 -> B182 : Failed
Now I can barely install anything (B386 anymore, it used, now it doesn't). Only TWRP...
Click to expand...
Click to collapse
When I downgraded to MM I was already on b182. I immediately had the nougat update available.
B182-->B380-->B386-->B390
I used ths: http://consumer.huawei.com/it/support/phones/p9/

Magisk patching, recovery, and OTA questions.

I've just ordered the Mi Max 2 on Cyber Monday for $189.99 USD on GB, I've already applied and gotten approved for Xiaomi bootloader unlock.
While waiting for my phone to arrive I've been trying to do the necessary preperations for flashing Magisk.
I've never used Magisk before as my current Zenfone 5 uses SuperSU.
According to the release thread for Magisk the new Magisk Manager can patch the boot.img directly.
My question is, will the below steps work?
-unlock the bootloader
-install magisk manager
-download the full rom for the mi max 2 and patch it with the magisk manager
-flash the patched rom?
Would this work and would I be able to receive OTA updates using this method?
I'm asking because using TWRP means no OTA updates and that's a pain.
I want Magisk just for root, adblock, and camera api module to use google camera HDR+
I can't find any answers to my questions anywhere as all guides and threads talk about using the TWRP method and all say TWRP can't recieve OTA.

Chisame said:
I've just ordered the Mi Max 2 on Cyber Monday for $189.99 USD on GB, I've already applied and gotten approved for Xiaomi bootloader unlock.
While waiting for my phone to arrive I've been trying to do the necessary preperations for flashing Magisk.
I've never used Magisk before as my current Zenfone 5 uses SuperSU.
According to the release thread for Magisk the new Magisk Manager can patch the boot.img directly.
My question is, will the below steps work?
-unlock the bootloader
-install magisk manager
-download the full rom for the mi max 2 and patch it with the magisk manager
-flash the patched rom?
Would this work and would I be able to receive OTA updates using this method?
I'm asking because using TWRP means no OTA updates and that's a pain.
I want Magisk just for root, adblock, and camera api module to use google camera HDR+
I can't find any answers to my questions anywhere as all guides and threads talk about using the TWRP method and all say TWRP can't recieve OTA.
Click to expand...
Click to collapse
if you rooted forget about OTA updates.
u need to download recovery flashable update zip files against small size OTA's
this is a little hack for OTA updates.(if you have a stock recovery.img) ive not tried though
flash existing flashable rom. this removes (magisk / supersu / all system modification )
flash stock recovery
flash ota update via stock recovery
again u can flash magisk to get root.
u need to repeat the whole process whenever a ota is available (i would prefer to download the recovery flashable zip and flash it in TWRP)
Chisame said:
My question is, will the below steps work?
-unlock the bootloader
-install magisk manager
-download the full rom for the mi max 2 and patch it with the magisk manager
-flash the patched rom?
Click to expand...
Click to collapse
no need to patch rom/ boot.img just flash magisk.zip in twrp it patches automatically.
manual patching is required only for certain specific devices.

reversegear said:
if you rooted forget about OTA updates.
u need to download recovery flashable update zip files against small size OTA's
this is a little hack for OTA updates.(if you have a stock recovery.img) ive not tried though
flash existing flashable rom. this removes (magisk / supersu / all system modification )
flash stock recovery
flash ota update via stock recovery
again u can flash magisk to get root.
u need to repeat the whole process whenever a ota is available (i would prefer to download the recovery flashable zip and flash it in TWRP)
no need to patch rom/ boot.img just flash magisk.zip in twrp it patches automatically.
manual patching is required only for certain specific devices.
Click to expand...
Click to collapse
So, worst case scenario I'll still need to TWRP and install that way. Is the current TWRP compatible with MIUI 9 on the mi max 2?
MIUI 9 has been rolled out the the Max 2 locally.

Chisame said:
So, worst case scenario I'll still need to TWRP and install that way. Is the current TWRP compatible with MIUI 9 on the mi max 2?
MIUI 9 has been rolled out the the Max 2 locally.
Click to expand...
Click to collapse
Yes twrp is supported irrespective of miui version

TWRP 3.2.0.0

Has any of you guys tried the newest TWRP 3.2.0.0 for OnePlus 3T? Did you find a bug?
Thanks.
Info: http://www.androidpolice.com/2017/1...g-better-support-oreo-roms-pixel-2-bug-fixes/
Download TWRPfor OP3T from the official site: https://dl.twrp.me/oneplus3t/

I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...

jojlse said:
I wonder if it triggers dmverity and how to avoid it if we just want to upgrade twrp...
Click to expand...
Click to collapse
I assume you flash the updated Recovery followed by the patched firmware, which i assume you already have? I don't even know if the firmware is necessary but whenever i flash anything i also re-flash the patched firmware while I'm at it. No reason not to.

Alright, DM-Verity will be cleared if you flash the newest Magisk beta, and TWRP 3.2.X.X is working fine. I don't think Teamwin would release an official version of TWRP without making sure it's completely free of bugs. It flashes Oreo ROMs (Cardinal Xtended, N2Os) and also flashed OOS 5.0 very well. Add-ons such as Magisk and Magisk Modules flashed flawlessly.

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