Develop Bugs

Twrp and flashing a Rom

So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565

wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.

noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!

if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.

**MANY** questions regarding flashing

Disclaimer: I come from the LG D802 world so I have no idea what antirb, dm-verity, authorization code or other strange protections are. Back then, any soft/hard brick could have been simply fixed by putting the phone in download mode and flashing the original software. So here I'm a bit scared to mess with the phone. I googled up all these questions, but mostly got contradictory answers so I decided to make a thread here trying to address everything.
For all the following scenarios, we'll consider that we're running the latest global MIUI with antirb = 4 (MIUI v10.0.1 OEIMIFH)
SCENARIO 1:
Let's say I want to gain root access with the original ROM (in my case: MIUI v10.0.1 OEIMIFH with antirb = 4). I understand that I have to:
1. fastboot into some custom recovery (let's say orangefox)
2. reflash redwolf from recovery
3. flash magisk
4. reboot into system
Now I should have root access, right? What about if I want to make changes to the /system partition now? From what I understand, there is a dm-verity check that detects changes to the /system partition and bootloops the phone if found. So, am I safe or not to make changes? (eg: flash youtube vanced, edit hosts, remove system apps, edit configuration files, etc)
SCENARIO 2:
I read somewhere that in order to disable all /system integrity checks, I'll have to reflash MIUI through orangefox and it will auto-patch out those checks. So, for instance, I want to flash the latest weekly xiaomi.eu ROM. (which AFAIK is China developer based and might interfere with the antirb check). The steps should be:
1. download the ROM
2. look into the .zip file and remove the firmware update script (is this necessary or orangefox will take care of it ???)
3. copy to sd
4. wipe cache, dalvik and /data (without /system and /persist)
5. flash through orangefox
6. flash magisk
7. reboot to system. done???
Now I should be able to make all sorts of changes to the phone (/system partition) without bootlooping or whatever?
SCENARIO 3:
Let's say I want to flash RR (or any other custom ROM). The instructions say that I need to have a NON-ARB firmware. What does it mean? How do I flash a NON-ARB FW if I'm on ARB 4 without bricking my phone?
SCENARIO 4:
Let's say that somehow I managed to flash a custom ROM. How can I go back to the original MIUI without bricking/losing the unlocked bootloader? Is miflash enough?
Unrelated questions:
1. How to make the custom recovery permanent? (is booting into recovery + twrp reflash enough ???)
2. Will OTA's brick my phone? (the phone being twrp'ed + magisk'ed)
3. Will OTA's remove my custom recovery?
4. What is lazyflasher and when does it have to be flashed? (or is it still required?)
5. Is it possible that the bootloader will get relocked by mistake?
6. What are the advantages of redwolf/orangefox compared to vanilla twrp?
I'd appreciate if somebody could take time to explain the steps and answer my questions (especially those from scenario 3) because I'm pretty sure there are many other users as confused as me regarding all this xiaomi flashing policy.

Scenario 3 : No you don't have to flash any firmware as you are already in latest miui version
Non ARB is for those people who is using anti3 ROM and don't want to upgrade to anti4 ROM
Just flash RR ROM without flashing any firmware file
Scenario 4 : yes using MiFlash just flash fastboot ROM or else just flash recovery ROM from custom recovery
There won't be any chances of bricking if you use MiFlash software because MiFlash checks bootloader index before flashing fastboot ROM, to be safer side always flash latest available MIUI ROM
xiaomi.eu is not a official ROM you can get official ROM from en.miui.com
To make custom recovery permanent just flash lazy flasher
No OTA will not brick your device
Yes if you flash full recovery ROM then custom ROM will be replaced by mi recovery but you can avoid this by flashing lazy flasher
No there is no chances of bootloader lock with OTA update, to lock bootloader you have to flash fastboot ROM using MiFlash software and you have to select clean all and lock option

Thank you, I finally start to understand how this phone works.
Now I have 1 more question: what about that dm verity thing? I don't feel yet ready to go to a full custom rom so I'd like to try out xiaomi.eu rom first because I understand that it is based on the chinese version of miui which comes with extra features. Will messing around with /system partion bootloop my phone? (due to the dm verity thing)

csm1n said:
Thank you, I finally start to understand how this phone works.
Now I have 1 more question: what about that dm verity thing? I don't feel yet ready to go to a full custom rom so I'd like to try out xiaomi.eu rom first because I understand that it is based on the chinese version of miui which comes with extra features. Will messing around with /system partion bootloop my phone? (due to the dm verity thing)
Click to expand...
Click to collapse
All the edited options will be over written by newly flashed ROM.
I don't know much about Dm Verity but you can flash lazy flasher to avoid dm Verity
Hopefully you will find your answer here https://forum.xda-developers.com/an...zip-lazyflasher-tool-flashing-custom-t3549210

csm1n said:
Thank you, I finally start to understand how this phone works.
Now I have 1 more question: what about that dm verity thing? I don't feel yet ready to go to a full custom rom so I'd like to try out xiaomi.eu rom first because I understand that it is based on the chinese version of miui which comes with extra features. Will messing around with /system partion bootloop my phone? (due to the dm verity thing)
Click to expand...
Click to collapse
had a G2 long time.
dm verity you can flash after installing TWRP flash file called lazyflasher or use orange fox recovery and no need to do anything. just flash and forget.
also try masik rom

I'm a newbie myself. Can I ask a few questions too?
1. If I want to root (miui 10) and install some mods, what's the best way to backup my current rom before rooting?
2. If I change my ROM to a custom ROM, how can I flash back my current ROM with OTA?
Thanks

Remig83 said:
I'm a newbie myself. Can I ask a few questions too?
1. If I want to root (miui 10) and install some mods, what's the best way to backup my current rom before rooting?
2. If I change my ROM to a custom ROM, how can I flash back my current ROM with OTA?
Thanks
Click to expand...
Click to collapse
1. TWRP Backup or ADB backup
2. You can return to stock MIUI ROM by flashing fastboot ROM using MiFlash (Recommended) or by flashing MIUI Recovery ROM

How to update OTA updated on rooted Phone

My phone is rooted with magisk and i have twrp recovery..
I am getting latest miui OTA update i want to update my phone but I don't wanna lose my all data is there any way to update miui without losing data on rooted phone ....
What i have?
1. Rooted
2.TWRP RECOVERY
What i don't want to lose?
1. My current Data
2. Magisk root...
Thanks...

Create backup, flash FULL OTA (not incremental) and flash magisk, wipe caches (recommended) and reboot.
If you'd like OTA support you can switch to supporting recovery like redwolf. Read the forums.

If i do what you have mentioned above , so there is no issue of a data loss ?? Or i have to use another recovery?

Hi,
firstly I am sorry for reviving an old thread, but I could not find any answer to this question. Also I am a new member and this is my first post (sorry, if I make any mistakes).
So how do I update my MIUI in the correct way and easily without any dataloss? A step-by-step guide would be very nice.
I have MIUI Global 10.3.2.0 Stable and want to update to MIUI Global 11.0.3.0 Stable.
"Normally" (before my device was rooted) I would directly update via system-update, but I am kind of scared since my phone is rooted now. It is the first time I have rooted my device, so I am new to this topic. I have used Redwolf to root my RN5P, but without flashing it as my recovery (just "fastboot boot redwolf.img", the normal TWRP did not work, since it always asked for password), also I have Magisk 20.1 (Stable) and cam2api installed.
Hope someone can help me. Thanks ahead.

yasin0005 said:
If i do what you have mentioned above , so there is no issue of a data loss ?? Or i have to use another recovery?
Click to expand...
Click to collapse
No data loss happen for me.. Like as you mine was rooted and twrp.. Just flash full recovery rom zip flash with latest version twrp( Not ota)
---------- Post added at 05:22 PM ---------- Previous post was at 05:18 PM ----------
mitu725 said:
No data loss happen for me.. Like as you mine was rooted and twrp.. Just flash full recovery rom zip flash with latest version twrp( Not ota)
Click to expand...
Click to collapse
Yes you lost magisk root... Just flash after, like as you did before

I am waiting since two weeks. Please someone answer/help me. Thanks.

- Get the recovery ROM from https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
- fastboot into custom recovery, if not already permanently installed
- flash the ROM
- re-install Magisk through recovery
- re-install camera2api
Other possibility, since you have only rooted your device, but haven't installed any custom recovery
- use the builtin update from MIUI
- fastboot any custom recovery
- re-install Magisk
- re-install camera2api
Neither way any data will be lost, nor will any app be de-installed

Tischbein said:
- Get the recovery ROM from https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
- fastboot into custom recovery, if not already permanently installed
- flash the ROM
- re-install Magisk through recovery
- re-install camera2api
Other possibility, since you have only rooted your device, but haven't installed any custom recovery
- use the builtin update from MIUI
- fastboot any custom recovery
- re-install Magisk
- re-install camera2api
Neither way any data will be lost, nor will any app be de-installed
Click to expand...
Click to collapse
Thank you for your reply. But in both ways I have to install custom recovery. That is not what I want (else I would have done it earlier in the frist place when I have rooted my phone). I want to keep the original MIUI recovery and "everything original/stock as possible" (that's the reason I stick to MIUI and do not use any custom rom).

Mura1 said:
Thank you for your reply. But in both ways I have to install custom recovery. That is not what I want (else I would have done it earlier in the frist place when I have rooted my phone). I want to keep the original MIUI recovery and "everything original/stock as possible" (that's the reason I stick to MIUI and do not use any custom rom).
Click to expand...
Click to collapse
Read it properly.. In the second method its written that we should fastboot any recovery not flash(install) it.. I hope your problem is solved now:good:
My question is i have orange fox recovery installed. How do I install ota ? Is just flashing the full rom zip enough? I want to preserve data.

@Mura1 you should only fastboot into any custom recovery. This you must have done in the past to root your device. It's the same way.
@Anymeofyou yes this should work. It's the same way I upgrade the device. Afterwards I flash the custom recovery and magisk as well, but that may be only a precausion. In the past I had to fastboot TWRP and flash TWRP once again within TWRP to have it installed. OrangeFox should keep the custom cevoery after an update, but since its only a few seconds to flash OF once again, it doesn't hurt me.
Till now no loss of data recognized.

Ah, thank you @Anymeofyou, know I got it and big thanks to @Tischbein in the first place . Sorry, for having to reading it multiple times (my bad).
I have updated now successfully. Have a nice day.

Tischbein said:
@Mura1 you should only fastboot into any custom recovery. This you must have done in the past to root your device. It's the same way.
@Anymeofyou yes this should work. It's the same way I upgrade the device. Afterwards I flash the custom recovery and magisk as well, but that may be only a precausion. In the past I had to fastboot TWRP and flash TWRP once again within TWRP to have it installed. OrangeFox should keep the custom cevoery after an update, but since its only a few seconds to flash OF once again, it doesn't hurt me.
Till now no loss of data recognized.
Click to expand...
Click to collapse
Thanks @Tischbein

Custom ROM Installed, Custom Recovery Dies

This is my first thread, I apologize for any mistakes or core aspects left out.
Intro/Formatting Key​Before I start, I want to give a quick thanks to those contributing to these forums/threads, as it got me through my first custom ROM install ever! Knowing too much information is better than too little, and my want to not waste anyone's time, I'm going to share most of my experience installing the custom recovery and ROM. I will explain what I mean by custom recovery dying at The Dead Recovery. Italics will be used as commands entered in SDK tools. Bold will be used as outputs from cmd.
Phone Specs​Phone: Oneplus 7T HD1905 running Android 11 OOS
Custom Recovery: Chinese TWRP from this youtube video
Custom ROM: Derpfest R for hotdogb found here
My Install Process​Besides needing to turning off driver signature reinforcement, the bootloader unlock was a normal process. Issues started occurring when I wanted to flash the custom recovery. fastboot reboot fastboot would not give me any feedback on the cmd prompt as it would say <waiting for devices> even though my phone was in fastbootd mode. After reading another thread, I hail married the flash using fastboot flash recovery twrp_best.img. All was great! My phone booted into TWRP, wiped the old stuff, flashed Derpfest, and rebooted. Derpfest works pretty well! (a little buggy but what do you expect from a beta build?).
The Dead Recovery​I notice the safety net with this ROM was broken, so I wanted to install Magisk to fix that issue (I wanted to use Gpay). I download the apk, do my renames for .zip and unintall.zip, and attempt to boot to recovery, but I just get a black screen! Using PWR+VOLUP allows me to reboot into the ROM just fine at least, so I didn't brick my phone. From here, I don't know what I should do to mitigate this issue. Here are my main concerns/questions.
Questions/Concerns​1. Will flashing a new recovery allow me to still boot into my phone?
2. Should I use a different image?
3. Should I maybe use flashboot flash recovery_a twrp_best.img flashboot flash recovery_b twrp_best.img to flash the recovery?
Thank you in advance!​

Question TWRP flashing method

Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !

I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.

twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)

best way is the magisk install

ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13

TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.