Develop Bugs

Stuck on Samsung's Galaxy Note Logo

Hello, I'm having trouble trying to install a custom rom into this device. The thing is that I had the stock 4.4.2 rom, then I managed to root it, and then I also installed TWPR so I could install the custom rom afterwards, well it turns out that I ran into trouble when I realized that after flashing the custom rom I couldn't get it to boot, and then I thought that it might be related to the bootloader. Isn't this tablet's bootloader locked? I know the bootloader gets updated when I update the stock rom, and I suppose it was and I'm on kk bootloader since I'm on 4.4.2 stock. Well it could be that the bootloader is locked and needs to be unlocked? I remember this was true for an HTC I used to have and for my current LG. But I don't know what to do, I mananaged to revert it back to stock after flashing the custom rom since I couldn't get it to work, I'm using odin for everything and following the instructions to the letter, being very careful and all, always wiping data partition and cache before. When following instructions didn't help I decided to try a few things on my own. I first flashed the root, then TWPR then the custom rom, then I tried TWPR, custom rom and then root, then root and custom rom. I've tried like all possible combinations to no avail it gets stuck on Samsung Galaxy Note 10.1 2014 edition logo and the custom rom doesn't boot. I'm so desperate since this is the first android device I haven't been able to install a custom rom on. Now I'm back to stock and lost everything, have to start from scratch now since I didn't back up, I had nothing important on my tablet, but still... I really need someone to help me out. My tablet is working fine now but with stock, no luck with custom rom (Hyperdrive) I don't wanna try other rom because I'm still thinking it has to do with the bootloader, but I don't know if it's locked or what.

sure, boot was ended ? If I remenber well, you need to be patient for first boot of hyperdrive rom, about ten minutes.
if you have have trouble with flashing, may I suggest you to update your tab step by step.
1) reinstall stock rom (seems you have already done that)
2) flash twrp 2.6.X (reboot, and keep time to manage a backup, use your tab, ...)
3) flash a custom rom with twrp (you will be able to restore some data from your backup if needed)
a good way is also to use your stock rooted rom with xposed modules. So you will be able to customize your tab like a custom rom do.

Xcoders said:
Hello, I'm having trouble trying to install a custom rom into this device. The thing is that I had the stock 4.4.2 rom, then I managed to root it, and then I also installed TWPR so I could install the custom rom afterwards, well it turns out that I ran into trouble when I realized that after flashing the custom rom I couldn't get it to boot, and then I thought that it might be related to the bootloader. Isn't this tablet's bootloader locked? I know the bootloader gets updated when I update the stock rom, and I suppose it was and I'm on kk bootloader since I'm on 4.4.2 stock. Well it could be that the bootloader is locked and needs to be unlocked? I remember this was true for an HTC I used to have and for my current LG. But I don't know what to do, I mananaged to revert it back to stock after flashing the custom rom since I couldn't get it to work, I'm using odin for everything and following the instructions to the letter, being very careful and all, always wiping data partition and cache before. When following instructions didn't help I decided to try a few things on my own. I first flashed the root, then TWPR then the custom rom, then I tried TWPR, custom rom and then root, then root and custom rom. I've tried like all possible combinations to no avail it gets stuck on Samsung Galaxy Note 10.1 2014 edition logo and the custom rom doesn't boot. I'm so desperate since this is the first android device I haven't been able to install a custom rom on. Now I'm back to stock and lost everything, have to start from scratch now since I didn't back up, I had nothing important on my tablet, but still... I really need someone to help me out. My tablet is working fine now but with stock, no luck with custom rom (Hyperdrive) I don't wanna try other rom because I'm still thinking it has to do with the bootloader, but I don't know if it's locked or what.
Click to expand...
Click to collapse
Are you on P605 or P600? The Hyperdrive rom is not for all variants.

11737
lightman33 said:
sure, boot was ended ? If I remenber well, you need to be patient for first boot of hyperdrive rom, about ten minutes.
if you have have trouble with flashing, may I suggest you to update your tab step by step.
1) reinstall stock rom (seems you have already done that)
2) flash twrp 2.6.X (reboot, and keep time to manage a backup, use your tab, ...)
3) flash a custom rom with twrp (you will be able to restore some data from your backup if needed)
a good way is also to use your stock rooted rom with xposed modules. So you will be able to customize your tab like a custom rom do.
Click to expand...
Click to collapse
Thank you, I've done all those steps, I've reinstalled the stock rom several times and, then I've flashed twpr 2.6.X and I've also tried with 2.7.X just in case, and I've had to root before or after installing the stock rom because if I don't I can't boot from stock either Ohh yes, I was very patiend the fist time it booted, I waited 15 minutes

shayind4 said:
Are you on P605 or P600? The Hyperdrive rom is not for all variants.
Click to expand...
Click to collapse
I'm on P600 and the Hyperdrive version I picked was made for P600 too, I'm sure of that

Seeking a better understanding

Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all

Shoruk3n said:
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Click to expand...
Click to collapse
1. If you switch roms, always do a clean install (wipe all partitions) . If you want to get rid off all the mods wipe system and flash the same rom + gapps + root. You won't loose data since you are only modifying the system partition.
2. Stock recovery by Oneplus is as if says stock, you littery can't do anything with it apart from upgrading your OOS, wiping cache partitions and doing a factory reset. I do recommend the TWRP provided by Bluspark since that seems to be the only one I tried without any issues whatsoever.
3. Magisk is the new root method in my opinion, it supports Magisk modules which simply are mods that can be installed and removed with a single click (reboot required tho). You can compare it to xposed but very limited when compared.
4. Boot.img is your kernel, never flash standalone img files apart from TWRP since the kernel modifies more the only the boot img. Always flash the full zip.

TWRP - Permanent Installation or Temp?

Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks

myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
If you only want to use TWRP when you have a fastboot-ready PC available, there is no need to install it. The reason why that is there is because since TWRP is embedded in the kernel (not flashed to a recovery partition like older devices), it will be overwritten whenever you flash a custom rom that includes a kernel, and I'm fairly certain they all do.
Returning the stock recovery menu is as easy as flashing the stock boot.img. There are no downsides that I know of of having TWRP on your device. And yes, returning to the stock rom and recovery is as easy as fastboot flashing the factory image.

myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
I dont install it anymore.
I run rooted stock and have no need really for a nand backup.
When I need it I just fastboot it and honestly I cant recall the last time I needed to do that.
On other deivces I have it installed for ease of updates for LineageOS.

My Pixel XL 2 swings both ways! I use TWRP on board and Fastboot!

I run stock rooted with flash kernel. I use my Nexus 6p terminal to fastboot boot TWRP on my Pixel when flash kernel pushes an update. I don't really see any reason to run a custom rom on this device as it runs great as is and there is an app for pretty much any custom rom feature you'd want.

Rooting went fine Flashing rom almost bricked me due to directions??

I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly

Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app

I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?

nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done

Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?

nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good:

**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