Database Users

TWRP 3.1.1 on oxygenos2

Hi i was about to update my phone and setting it to factory in order to update it to Oxygenos last version since i still using oxygen2 (andoid 5) etc...
I was about to do a twrp backup however i do no thave enought space so i've read on internet that with twrp 3.1+ you can backup directly on pc. I've tryed to update twrp however its not working and not starting the recovery partition. I've read that : (3.0.2-1 and above for OxygenOS 3.x and above) (3.0.2-0 and below for OxygenOS 2.x and below) however i need the updated version to backup directly on pc what can i do? some advice? i've looked for a modified version of twrp 3.1 for oxygenos2 but i did not find it :S

Before you do this, update TWRP via these instructions
https://wiki.lineageos.org/devices/oneplus2/install
skip down to this line "Installing a custom recovery using fastboot" as you do not need to unlock the bootloader as it is already unlocked since you have TWRP already.
Do not make a TWRP backup, It will not be of any use once you move to OxygenOS 3.6.1 since the backup will be of Nouget (android 5). The best way to upgrade would be to follow the steps here http://downloads.oneplus.net/oneplus-2/oneplus_2_oxygenos_3.6.1/
Once you get to step 4, click the "View Instructions for TWRP Recovery" link then you can either dirty flash or clean flash the zip. I would recommend clean flashing, as in do the factory reset as mentioned in the second paragraph under step 4. However, do not directly flash the rom afterward, use the reboot option in TWRP to reboot into recovery then flash the zip.
NOTE: If you want to use Magisk to pass SafetyNet and have root, download the Magisk zip and flash after flashing the rom, or queue it to it flashes right after the OOS rom.
afterward let the phone boot up then do the setup. Once you have completed setup, enable developer settings and enable advanced reboot. use reboot into recovery to boot into TWRP
Now go ahead and make a TWRP Backup, This backup will be your Go-To backup if you want to go back to factory OOS 3.6.1 with the setup completed and Magisk already installed.

Not able to backup
The problem is that the last version of TWRP working on oxygenos2 is 3.0.2-1 and you can not make the backup directly on computer, i've traied toupdate twrp and it does not lounch however with that version of twrp (3.0.2) or before it works that was the point if there was any modified twrp for oxygenos2 and with twrp version 3.1 or higher.

TWRP v3.x.x doesn't work with oxygen 2.
There's no way to boot TWRP v3 without installing oxygen 3.
If you need to backup your files (pictures, videos, WhatsApp messages etc.) you don't need TWRP because it backups only your system and your apps.
So simply attach your phone to your PC and copy all your files.
If you need a copy of your system then you need to free some space on your phone and do a backup with TWRP v2

Bootloops after flashing Magisk OOS 5.0.2

I've been getting bootloops after installing Magisk on my OnePlus 5 unlocked bootloader , rooted before at 4.5.15.
I directly updated it to 5.0.2 which resulted in many errors in the end had to flash it completely and then clean install the ROM .
The ROM works perfectly with almost no trouble.
I then flashed almost all Magisk versions I could get hold of (14.5,15.2,15.3,15.4(beta))
But none of them could get past the boot animation.
I've also flashed the no Verity mod file both before and after the flashing of Magisk nothing worked.
But everytime after all this I flash the Magisk uninstaller and I get easily get back to using the device but without root.
Anyone help me rooting this ?
The ROM has been downloaded from official OnePlus website and the twrp I'm using is the codeworkx version.

First do this then tell me how it went.
1. Boot to fastboot and flash twrp-3.2.1-0-universal-codeworkx-cheeseburger.img via command window, make sure you have adb installed on pc.
2. Then boot DIRECTLY to twrp.
3. Dirty flash OOS 5.0.2 over your current rom in twrp and then wipe dalvik and cache.
4. Then boot into fastboot DIRECTLY again and flash twrp-3.2.1-0-universal-codeworkx-cheeseburger.img again.
5. Boot into twrp directly and flash Magisk 15.2.zip
6. Finally boot into the system.
7. Optional: then you can go ahead and update Magisk via it's own flash tool.

I'm already on 5.0.2 so do I dirty flash it again?

Help needed, ze552kl bootloop after flashing without uninstall magisk

Last working state :
1. Android O version WW-15.0410.1803.55
2. Bootloader unofficial unlocked
3. Rooted with magisk
Reason for flashing :
Update to latest Oreo then re-root but flashing failed due to magisk not being uninstalled first
Current state :
1. Able to enter fastboot
2. Twrp is intact
3. Magisk uninstalled using twrp
Actions already taken :
1. Uninstall magisk via TWRP
2. Re-flash WW-15.0410.1803.55 via TWRP
3. Wipe dalvik/cache
4. Factory reset via twrp swipe
Still stuck in bootloop
I'm thinking of flashing Oreo stock recovery prior to reflash Oreo firmware via Asus flash tool. Found Oreo stock recovery image from 15.04.10.1711.6. Is this usable? (Edit : found suitable version and bunch of other versions, big thanks to Iceboy91 on following thread : https://forum.xda-developers.com/zenfone-3/help/request-stock-recovery-boot-img-stock-t3763381 )
But before I do anything even more stupid, I need your advise on correct next moves, guys.

Flash raw oreo via Asus flash tool and all will be fine.

[email protected] said:
Flash raw oreo via Asus flash tool and all will be fine.
Click to expand...
Click to collapse
Will Asus FT run properly on TWRP i/o stock recovery? Last time I did it booted to TWRP and I can't proceed. Kindly confirm if it's possible and I'll give it another try. I am left with another option which is flashing corresponding stock recovery and boot image.

To save your time from trial and error recovering from similar problem, here's what I do.
Issues :
1. Flashing raw on stock with TWRP stuck on eternal 'unzip image'
2. Flashing raw on stock ROM with stock recovery and wipe data OFF was successfull but could not enter system (stuck on Asus logo with circling progress).
Also unable to enter stock recovery at this point.
Steps taken to recover from bootloop :
1. Flash corresponding recovery and boot image to replace TWRP (BE CAREFUL WITH SOFTWARE VERSION)
2. Firstly, flash basic Oreo RAW firmware which can only boot to fastboot found on this post : https://forum.xda-developers.com/zenfone-3/how-to/updated-unlock-relock-bootloader-t3749456
3. Flash full RAW Oreo firmware found on the very same post mentioned on #2, but with WIPE DATA SELECTED.
Note : Step 2 might be skippable, up to you to try

Hey ,
If you wanna upgrade to latest Oreo update, just follow these steps (most of the users did not report any kind of bootloop)
1) Flash stock recovery
2) Sideload the latest firmware .zip
3) Reboot and flash TWRP & Magisk
Link for stock recovery/boot images by @shakalaca :
https://mega.nz/#F!lw02CLpA!hpetR2-Sec1F__gHPNRE9Q!E09B3BbA
If anything happens, RAW firmware is there for you
Note: Do not remove/uninstall Magisk via TWRP. Flashing latest update will remove Magisk automatically.

Thanks for the tip, my problem has been solved, but better solution is certainly welcomed. Will do when caught in the same situation.

Here is what I do:
Skip automatic update and do it manually through TWRP.
First flash update then reinstall latest magisk in order within TWRP.
Reboot.

sanctitude888 said:
Will Asus FT run properly on TWRP i/o stock recovery? Last time I did it booted to TWRP and I can't proceed. Kindly confirm if it's possible and I'll give it another try. I am left with another option which is flashing corresponding stock recovery and boot image.
Click to expand...
Click to collapse
AFT just needs working fastboot.
Flashing raw via aft will restore all stuff to stock state.
Twrp will be replaced by stock recovery too.
I wouldn't recommend flashing stock zip via twrp.
Another way to get back to. Stock is to replace twrp by stock recovery (after wiping data, cache, system). Then flash boot.img and finally use update via SD card option from the newly installed stock recovery.
Also you can take twrp backup of stock rom (system, data, boot) and restore whenever you want to go to stock (after wiping system, data and cache).
All methods tried and tested.

Problems with MIUI v11.0.4 and TWRP/Magisk

Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder

coder111 said:
Hello,
I have MI 9T. I unlocked it and tried to get TWRP and Magisk installed and ran into issues.
I tried TWRP 3.3.1-0-davinci and Magisk v20.4, both official.
If I flash v11.0.4.0 ROM (I tried both global or EU versions, QFJMIXM and QFJEUXM), and then install TWRP and Magisk, phone goes into bootloop and then back to TWRP. After that I am not able to boot system at all, and end up going into fastboot and reflashing official ROM.
I tried flashing v10.3.15.0 PFJEUXM (EU) version. TWRP and Magisk work perfectly fine on that one.
Then I tried upgrading to v11.0.3 version (I think the hash was PFJEUXM but I'm not certain) from system settings, it works perfectly fine with TWRP and Magisk too.
If I then try upgrading to v11.0.4.0 it all goes wrong. TWRP/Magisk get wiped (that's usual), but if I reinstall them- bootloop again and unable to boot system.
I'll keep using v11.0.3 for now, but it would be nice if TWRP/Magisk get fixed to support v11.0.4. Until that happens I think it would be wise to avoid upgrading to v11.0.4 if you have TWRP and Magisk.
P.S. I never set any passwords or authentication anywhere.
--Coder
Click to expand...
Click to collapse
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both

Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
zgfg said:
There are two other threads about installing Magisk (without using TWRP).
However, TWRP (official or OrangeFox) can be also installed (independently of Magisk, e.g. I did once I already had Magisk).
And everything works perfect for QFJEUXM 11.0.4.0 - responding from my Mi 9T with both
Click to expand...
Click to collapse

coder111 said:
Can you enumerate exactly which steps you took and which options you selected?
For me it was:
* Boot into Fastboot.
* Fastboot flash original MIUI ROM
* (Boot the system). I tried skipping this step, didn't make a difference.
* Reboot into Fastboot
* Fastboot flash TWRP.
* Reboot into TWRP.
* Reboot into TWRP again. TWRP asks to install itself before reboot. Allow TWRP to install itself.
* Copy Magisk to mobile USING MTP while in TWRP recovery.
* Install Magisk.zip. Wipe cache and dalvik.
* Reboot into system.
* FAIL.
Maybe I had to set a password somewhere or decrypt/mount something in one of the steps or something? Or did you install something extra like dm-verity disabler or something? I tried installing dm-verity disabler after TWRP but that just sent my phone into bootloop immediately.
Click to expand...
Click to collapse
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP: https://mega.nz/#F!hllnSIpA!amAG8moMYW_tG8r731Tzgg

Thanks for your help.
I tried the thing with Magisk Manager & boot image file, and it worked. I can live with stock recovery for now. I just needed root.
You saved me quite a bit of hassle. Thanks again.
zgfg said:
I didn't need to install 11.0.4.0 - I had it by OTA
Install Magisk as described in the threads you can find here on XDA (Easiest way to install Magisk without TWRP, title was something like that), basically:
- start from stock QFJEUXM 11.0.4.0
- extract boot image from recovery/zip package QFJEUXM 11.0.40 and copy to phone
- install Magisk Manager app and patch the extracted image (DM Verity and Enforce encryption must be On, Recovery option Off)
- copy the patched image to PC and flash by Fastboot to boot partition
- reboot to system and you are rooted, enjoy Magisk
Flash the official TWRP, boot to, enter your Android unlock pin/pass but
do not format Data or anything - enjoy TWRP.
From TWRP you can flash OrangeFox recovery if you like it (you can always flash back TWRP if you wish) - it also supports Android pin/pass for the read/write access to Internal memory
You don't need to extract and patch yourself the boot image, you can find the patched boot image on my Mega (and the corresponding Magisk Manager Canary apk), as well as TWRP:
Click to expand...
Click to collapse

Mi9T stucks on kali boot logo after flashing nethunter

I do have orangefox recovery flashed into my phone. Wiped data, system, cache... and format data
First of all, I installed MIUI (the latest version from mi website "miui_DAVINCIGlobal_V12.1.4.0.RFJMIXM_e0ac13ed89_11.0.zip"). If I reboot into the system, it works fine.
Then flash magisk(v24.3) and 'disable DM-Verity_ForceEncrypt', and reboot into recovery
When I flash nethunter (nethunter-2022.2-davinci-miui-ten-kalifs-full.zip), which I downloaded from offensive security webpage., it does install well (at least it doesn't show any error messages).
After flashing nethunter, I rebooted into system. When nethunter logo did pop up, it got stuck into that fire animation. I can still access fastboot and recovery menu.
Any idea of what's happening? Why doesn't it boot?

Xylonity said:
I do have orangefox recovery flashed into my phone. Wiped data, system, cache... and format data
First of all, I installed MIUI (the latest version from mi website "miui_DAVINCIGlobal_V12.1.4.0.RFJMIXM_e0ac13ed89_11.0.zip"). If I reboot into the system, it works fine.
Then flash magisk(v24.3) and 'disable DM-Verity_ForceEncrypt', and reboot into recovery
When I flash nethunter (nethunter-2022.2-davinci-miui-ten-kalifs-full.zip), which I downloaded from offensive security webpage., it does install well (at least it doesn't show any error messages).
After flashing nethunter, I rebooted into system. When nethunter logo did pop up, it got stuck into that fire animation. I can still access fastboot and recovery menu.
Any idea of what's happening? Why doesn't it boot?
Click to expand...
Click to collapse
For Magisk you ABSOLUTELY don't need Verity and so
Simply, extract boot.img from the firmware zip and by using Magisk APP take install, Select and Patch to patch your extracted boot.img
Do not enable Recovery option while patching
Then flash from Fastboot the patched boot img to Boot
That's it - the proper way to install Magisk to your Xiaomi ( I used and still use on my Mi 9T from MIUI 10 till now with MIUI 12.5)
For Nethunter I cannot help you. It's been more than two years since I used Kali and at that time it installed flawlessly.
However, then I had MIUI 11 and Kali required MIUI 11 - don't know how is it now...
And btw, I always use the latest TWRP.me version - currently 3.6.1_9-0

zgfg said:
For Magisk you ABSOLUTELY don't need Verity and so
Simply, extract boot.img from the firmware zip and by using Magisk APP take install, Select and Patch to patch your extracted boot.img
Do not enable Recovery option while patching
Then flash from Fastboot the patched boot img to Boot
That's it - the proper way to install Magisk to your Xiaomi ( I used and still use on my Mi 9T from MIUI 10 till now with MIUI 12.5)
For Nethunter I cannot help you. It's been more than two years since I used Kali and at that time it installed flawlessly.
However, then I had MIUI 11 and Kali required MIUI 11 - don't know how is it now...
And btw, I always use the latest TWRP.me version - currently 3.6.1_9-0
Click to expand...
Click to collapse
Thanks for replying