Database Develop

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.

Global Stable 10.0.3.0 and TWRP Encryption

Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.

I am also interested about update with Magisk

GeorgeKatsi said:
Hello guys. Yesterday ( October 30th) I had a notification about upgrading from 10.0.2.0 to 10.0.3.0. I was rooted with Magisk, and after the update the root privileges were gone. I tried to boot to TWRP again, but it stays encrypted without asking for password as usual, so I am unable to flash the zip and root again. Is it ok if I use the boot.img in order to install via patched_boot?As for now there isn't 10.0.3.0 firmware available for download in order to extract it. Thank you for your time.
Click to expand...
Click to collapse
You can flash patched_boot to get the TEMP magisk working before the new twrp available for 10.0.3.0
Code:
fastboot boot patched_boot.img
The boot image can be patched via magisk by yourself or you can use mine from 20181104_mi8_10.0.3.0_patched_boot.img
Remember this TEMP solution fails after rebooting. Or you fastboot boot patched_boot.img every rebooting.

Hello ich have the Same Problem, can U Tell step by step how to do that?
Ich want to flash custom Rom

same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data

mikefallen said:
same issue im on miui.eu 10.0.8.0 with encryption enabled.
Booting into recovery TWRP does not ask for passcode to decrypt data
Click to expand...
Click to collapse
I flashed the patched_boot made by magisk, but I am still unable to decrypt twrp. I hope they support 10.0.3.0 soon so I can use twrp again.

TWRP install and magisk root xz3

So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update

Jharrisonkerr said:
So over the last day or 2 I've tried flashing the twrp recovery image. It flashes fine and reboots and loads the twrp recovery. However nothing works after that like it hangs and the touch screen is inop. How do I get past this? I have flashed the latest twrp for 52.0.A. 8.131 and phone is on the stock firmware also.
Just trying to get to the stage of installing the magisk root software. I've heard also people having issues with certain versions of magisk on Sony phones to? Is this fixed in the latest version?
Is there anything else I should be doing? Is the xz3 able to be rooted on the latest software released by Sony as of August update
Click to expand...
Click to collapse
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.

MartinX3 said:
I didn't got bug reports to fix something in this direction.
Touch doesn't work in the android system?
And it hangs?
Or what hangs where?
Yes, you either need to use magisk 18.1 or the newest canary should work too.
Click to expand...
Click to collapse
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.

Jharrisonkerr said:
Hi Martin, touch doesn't work when in the main twrp screen after using fastboot to move the twrp. img file over to the device so I can install the magisk program to allow root access.
Click to expand...
Click to collapse
Hi Jharrison,
You did say it hangs
At twrp boot logo?

MartinX3 said:
Hi Jharrison,
You did say it hangs
At twrp boot logo?
Click to expand...
Click to collapse
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.

Jharrisonkerr said:
Well it's like it hangs as it loads the Sony logo and then boots into twrp but nothing happens when touching the touch screen or using the side volume buttons apart from showing the twrp boot logo.
What's the full process of flashing twrp to the device? Maybe I'm doing something wrong? I did see some people have had to connect a mouse to there phone to operate twrp?
Sorry for the confusion. I'm not sure if it's the way I'm doing it or if there is a issue with twrp on the xz3 on the latest Sony firmware. I've done a few roots before as I have a tablet install in my car as well as rooting a previous xperia phone but the latest android 9 seems harder to crack.
Click to expand...
Click to collapse
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?

MartinX3 said:
So you see just the twrp logo, no buttons?
That indicates a failing decryption
Did you downloaded the reuploaded twrp?
And twrp and firmware having the same version?
Click to expand...
Click to collapse
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?

Jharrisonkerr said:
Yeah that's it, just the main twrp boot screen/logo no buttons to install the magisk.
I haven't as of yet. When was this uploaded? Recent? Yeah the version for twrp was for the same firmware version not custom rom just stock version
Is there any specific way to flash it in fastboot?
Click to expand...
Click to collapse
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log

MartinX3 said:
I did reupload the twrp with new omnirom code changes to fix this problem in the past
Please redownload the twrp
I hope it is fixed now
If not, I would like to see a dmesg and a /tmp/recovery.log
Click to expand...
Click to collapse
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?

Jharrisonkerr said:
OK, I will try this later.
Just to confirm what is the correct way to flash the twrp. Img file using fastboot? Fastboot flash recovery twrp.img?
Click to expand...
Click to collapse
The correct way is in the first post of the first page in the main twrp thread.

Managed to get it working, however once all installed it asks to update the magisk app to 19.3 which I have done however it is now stuck in a bootloop where it loads Sony and powered by android and then reboots every time.
What's the fix for this?

So far I've fixed it by reinstalling the previous version through twrp. Is there issues with magisk 19.3?
Alos now in the magisk manager I have the manager showing up to date(7.3.2) but magisk is showing not installed only able to install magisk 19.3?

Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]

MartinX3 said:
Please either use magisk 18.1 or the newest canary
Or switch to a custom ROM. [emoji14]
Click to expand...
Click to collapse
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?

Jharrisonkerr said:
For some reason I can't seem to get magisk 18.1 back on now after the update. I'm guessing I'll have to do a clean install again. The magisk manager is fine but magisk doesn't shown as installed. Is there a fix for this or will a clean stock flash work? Or is there a way to flash a new boot.img?
Is this also a known issue when updating magisk?
Click to expand...
Click to collapse
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.

MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Tried the magisk uninstaller but every time I do it comes up with error 1 and then never installs.
The flash boot.sin sounds a easy fix, I will try that and see. If not looks like a full firmware reinstall is on the cards. I'll stick with 18.1 when I do as that seemed to work until I updated. I'll wait till a stable release of 19.4 is released.
Many thanks for your help so far Martin.

MartinX3 said:
You can flash the magisk uninstaller first
Or the firmware
Or the boot.sin from the firmware folder
It's a known issue for the xperias from sony
The developer said that a working magisk before was an accident and since he used an official way it wasn't working anymore correctly
And then it seems in 19.4/canary fixed er the xperia specific issue.
Click to expand...
Click to collapse
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?

Jharrisonkerr said:
Managed to reflash the beta 19.3 zip for magisk then restart, flashed the uninstaller which worked and then reinstalled magisk which is now working again.
Is it safe to update the manager app from 7.0.0 to 7.3. 2 and leave the magisk version at 18.1?
Click to expand...
Click to collapse
The app is fine

MartinX3 said:
The app is fine
Click to expand...
Click to collapse
Awesome I'll update the app to latest then and leave magisk at 18.1 as root is working fine so far.
Many thanks for your help with all this Martin. :good:

MartinX3 said:
The correct way is in the first post of the first page in the main twrp thread.
Click to expand...
Click to collapse
Can you share the link please? I visited your profile but did not found the that thread how to flash my sony xz3 using TWRP.

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

Working TWRP for Mi9T Pro on Android 10 (QFKEUXM) **SOLVED**

Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
**UPDATE**
I flashed the latest TWRP from this thread and all went smoothly. Also managed to get Viper4android working which was my biggest concern coming from Android 9. Happy days :victory:

_ray_ said:
Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
Click to expand...
Click to collapse
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.

Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Good luck and please do post back the results :good:

Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Sent from my Redmi K20 Pro using Tapatalk

I'm also interested in this. I want to keep TWRP and magisk post-upgrade to Android 10

I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system

_ray_ said:
Good luck and please do post back the results :good:
Click to expand...
Click to collapse
ishaqtkr said:
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Click to expand...
Click to collapse
Okay so, coming from 10.3.4.0 Stable, OFox Recovery and encrypted, the update ran through fine without any problems. Since I'm encrypted I had to enter my password first but after that it started installing the Update. as far as I remember, I've seen that Orangefox's script that prevents Orangefox from being overwritten after every update (it's called OTA.bak I think) already handles both DM-Verity and Force-Encrypt on it's own, at least I didn't had to take any further steps regarding Encryption and such stuff and after updating it booted into MIUI 11 just fine (which ofc since it's an Major Update took a little longer than usual but at least it eventually did)

desiresiscool said:
I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system
Click to expand...
Click to collapse
So what do you do when you're on 10.3.4 pfkeuxm Rom and running with twrp and magisk installed?
Can't I install the miui 11 rom via twrp and then immediately flash magisk again?

Following the advice here, I've got the update installed with twrp and magisk working fine. The only problem I have is that I can't read/write the system partition so titanium backup isn't working. Any ideas how I could fix it?