Database Develop

[Guide] Switch From Beta to Stable OOS/Fix Random Reboots in Custom Rom

So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.

i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Gesendet von meinem xXx_NoLimits_6.0 on ONEPLUS 6T mit Tapatalk

MarcoG: said:
i am on OpenBeta9,can i use the Twrp Method for a downgrade to the Stable 9.0.13?
Click to expand...
Click to collapse
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.

ultyrunner said:
Given the problems with rolling back security patches I wondered the same thing. However, assuming we wiped everything including system it should work. Having said that, when I previously tried rolling back to the latest stable from beta, when I fastboot flashed everything to both slots, I could never get it to boot and was able to flash beta and get it running again.
Click to expand...
Click to collapse
I'd like to see a resolution to this ^

This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want

Causical said:
I'd like to see a resolution to this ^
Click to expand...
Click to collapse
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.

se7ensde said:
This should not be this complicated any time I my base whether it beta or stable I never met to do all of this...
It's super simple to go back to whatever oos version you want without the need of msm tool and all this extra stuff.... I've went from beta to stable and back to beta several times no issues... And you are going to have to format data no matter what if you are changing oos versions and don't want to run into an encryption problem.
You can just back everything up
Boot to fastboot
Fastboot format userdata
Fastboot boot twrp. img
Transfer needed files. (oos, twrp)
Flash oos + twrp
Reboot recovery (make sure the slot changed)
Flash oos + twrp
Reboot system make sure it boots up right
Now you can go flash the rom you want
Click to expand...
Click to collapse
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
ultyrunner said:
I can verify the TWRP steps outlined above (in the OP, not the comment with Fastboot) worked perfectly for me. Did everything in exactly the same order. Was on beta 8 and went to 9.0.13 without a hitch.
Click to expand...
Click to collapse
Awesome, you sir are THEE man. Please get a job with XDA or something

Causical said:
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Um ... OK ... ?

Causical said:
what about directy through TWRP? can I just replace fastboot with TWRP in your instructions or does Formatting userdata erase internal files (ie: TWRP, Magisk, etc... I'm only asking because I've only ever updated to the latest OOS and I'm just curious for future possible future tinkering)
---------- Post added at 12:38 AM ---------- Previous post was at 12:34 AM ----------
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
Yeah sure you can mix up the steps or skip whatever you want..

se7ensde said:
Yeah sure you can mix up the steps or skip whatever you want..
Click to expand...
Click to collapse
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.

ultyrunner said:
LOL, yeah. I was kind of surprised with the smart-ass comment, but then again lots of people on here don't follow instructions, do things out of order and then wonder what went wrong or why they suddenly have a $700 paper weight. Given how much chatter there's been about the MSM tool (not an option on Mac) or needing to fastboot flash individual images (which didn't work for me), I was surprised how easy moving back to stable completely via TWRP is. I'm used flashing Nexus and older Samsung devices, which used to be dead-simple.
Click to expand...
Click to collapse
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.

Causical said:
You were probably surprised with the smart ass comment because it wasn't a smart ass comment Sgt. Dillweed (that was a little smart ass)...I don't generally give a thanks to someone to be a smart ass, but nice to know where your head's at.
Click to expand...
Click to collapse
Nope. I was surprised because ...
Awesome, you sir are THEE man. Please get a job with XDA or something
Click to expand...
Click to collapse
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.

ultyrunner said:
Nope. I was surprised because ...
... is definitely smart-ass, and seems odd after receiving a like. If you don't see that in the tone, I'm afraid I can't help you.
I think THAT may be more indicative of where your head's at. But ... carry on and you keep on doing you, bud.
Click to expand...
Click to collapse
Cool I'm glad you can explain the "tone" and characteristics of my own words to me. I'll remember to try and not be so nice towards you next time, at least if I really be a **** it won't be mistaken.
I WAS originally thrilled by your simple and to the point response, but since you decided to twist my words and make yourself look like a jack ass... well nicely done, is all I have to say ?
Words of a Wise Guy: "hmmm seems odd after receiving a like..."
Huh, just think about that one for a second.

Causical said:
Cool I'm glad you can explain the "tone" and characteristics of my own words to me.
Click to expand...
Click to collapse
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.

ultyrunner said:
Clearly someone has to, because you can't understand that everyone isn't inside your head to hear the little voices that define 'polite' for you. Anyway, you're on the ignore list now.
Click to expand...
Click to collapse
Oooo scary...I guess I'll take my "like" or thanks back whatever you call it.

the.emilio said:
So as I go over the custom roms available in the development section I cannot help but notice how many users state that the rom is causing random reboots. It is usually due to said user flashing the custom rom over a beta OOS version instead of the latest stable build as the OP instructions usually indicate. The reboots are hardly caused by the rom itself. I am putting together this guide to help users go from beta back to stable. This will allow a clean install of the custom rom and usability as it is intended.
This can also be used to just go back to stable from beta if you want to run the stable OOS.
There are 2 ways to do this. One is via TWRP if that is what you prefer or you can also use the MSM tool to flash back to the latest stable. Both ways will wipe and format your internal data. This is due to the mismatch in security patches between beta and stable. So be sure to make a backup of your internal storage if there is stuff there that you need. You have been warned.
NOTE: Highly recommended to use a computer to make things easier. If you do not have a computer available, use the TWRP method listed below to get back to stable OOS. Once OOS boots, you can download your custom rom of choice using your phone and install it.
Here are the links for the latest MSM tool and latest stable zip if you want to use the TWRP method:
Latest MSM Tool
Latest stable OOS to flash in TWRP
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here.
If you want to run a custom rom, reboot to TWRP, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. If no PC is available, download your rom and needed files like twrp, magisk etc. using OOS stable first. Then you can reboot to recovery and follow the installation steps provided by your rom developer on their page.
Steps for MSM:
Download the latest MSM tool with link from above. Boot phone to EDL either by powering off the phone then holding Vol + and - with Power or my preferred way via adb by typing adb reboot edl. Plug in phone once in EDL and let MSM do its thing. If you are not sure how to use MSM, the link for the MSM tool outlines the steps. Your phone will reboot to OOS. If you want to run OOS stable you are done. Just set up your phone as normal from here. Note, your bootloader is locked. You will need to do an oem unlock to install twrp and magisk if you want root or to install a custom kernel.
If you want to run a custom rom or root your phone, get to the settings screen.. you can skip setting up your phone so just hit skip on all the prompts for set up. Go to settings, enable developer options. Make sure OEM unlock is selected and USB debugging is selected. Once you do that, do adb reboot bootloader. Then do the following:
fastboot oem unlock
It will reboot the phone. Skip through the set up again and go back to settings. Enable developer options and enabled USB debugging. Then run adb reboot bootloader. In the bootloader, do the following:
fastboot boot <twrp.img> (replace this with the actual file name)
From there, you can transfer your custom rom, gapps, magisk, kernel and twrp installer using a PC. Follow the installation steps provided by your rom developer on their page.
Click to expand...
Click to collapse
Thank you it works[emoji16]
Gesendet von meinem ONEPLUS A6013 mit Tapatalk

se7ensde said:
Fastboot format userdata
Click to expand...
Click to collapse
What is formatted? The complete internal sdcard?

TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible

Ryano89 said:
TWRP Steps:
Download latest OOS stable from link above
Flash OOS stable build
Flash TWRP installer
Reboot to TWRP
Factory Reset
Format Data type 'yes' when prompted
Reboot to System
Will this work if I'm on beta14 with July security patch, and I want to flash back to stable . 15 with June security patch? I'm using TWRP 3.3.1-6. I ask because I would like to flash back to stable but will not have access to my laptop for a week or two, so I'd like to do it right through twrp if at all possible
Click to expand...
Click to collapse
Yes.

Mannan Qamar said:
Yes.
Click to expand...
Click to collapse
Thanks, I only ask because I see a lot of disagreement about it on different threads. Some say you can do it, other's say you can't do it if you are flashing back to an older security patch. It's not urgent for me so I might just wait until I have access to my laptop again, but I was hoping to do it now. Won't format completely erase the device?

How to reset firmware

so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help

Um, i think ur in the wrong category

thejacer87 said:
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps ...
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is?
Click to expand...
Click to collapse
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)

Fatal_Scythe said:
The misc.bin file is basically just a script that tells the Device to directly boot into TWRP, because Xiaomi Devices / MIUI are configured to overwrite TWRP after a reboot. If you still feel uncomfortable having to flash the misc file, try "fastboot *BOOT* TWRP.img" instead of "fastboot *FLASH* TWRP.img".
If you wish to keep MIUI installed instead of an Custom ROM make sure to flash Magisk, as it patches the DM-Verity stuff that causes the Device to either get stuck in a Bootloop or replace TWRP with the Stock Recovery.
If you're planning to run an Custom ROM like LineageOS, AOSiP etc. you don't have to flash Magisk as long as your Device isn't encrypted. Rebooting from TWRP to System without flashing Magisk on an encrypted Device will encrypt your Data Partition and you'll have to format Data to be able to access the Internal Storage again. (Flashing Magisk in that case will prevent your Device from encrypting all your Data again after an ROM Flash.)
Click to expand...
Click to collapse
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions

thejacer87 said:
so i've tried a few roms, and couldn't get gpay working. im going to try a few things mentioned in other threads, but before i start that. i want to properly/fully reset my phone to the stock, to hopefully make sure i don't mess anything up in the future.
my first issue was installing twrp, i tried to `fastboot flash` the recovery, but nothing worked until i followed these steps: https://www.getdroidtips.com/download-and-install-twrp-recovery-for-redmi-k20-pro-latest/
im worried about what might be in the misc.bin in that zip. cuz i couldn't reboot into twrp recovery until i flashed that. does anyone know what that is? i think i just want to flash/reset? everything on my phone back to miui, make sure i update to the latest firmware etc. but, tbh, i find navigating xda difficult and can't seem to find the official firmware anywhere, or steps on how to reset the phone...
thanks for any help
Click to expand...
Click to collapse
If you're planning to go back to stock MIUI and locked bootloader, I highly recommend using Mi Flash and flashing the original fastboot MIUI ROM which can be found here https://www.xda-developers.com/download-miui-11-xiaomi-redmi-note-7-pro-poco-f1/amp/. All you gotta to do is extract the ROM file which is .tgz to any folder, and in Mi Flash select that folder click on "clean all and lock" in the bottom right corner, and click flash. This should theoretically make your device "out of the box".
Keep in mind that this method requires a PC with all ADB and fastboot drivers, they can be downloaded from here https://forum.xda-developers.com/showthread.php?t=2588979 .

thejacer87 said:
k thanks for the info. what's the difference b/w the boot v flash for twrp?
is the misc.bin from that link i posted safe then? where did it come from? is there a thread here where files like that are posted/talked about?
i definitely plan to stick with either lineage or Pixel experience. i just want to get google pay going. so i think my next attempt will be to relflash magisk and look into that sql fix everyone mentions
Click to expand...
Click to collapse
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too

Fatal_Scythe said:
BOOT will just let the Device temporarily boot into the Recovery (without making changes to the Recovery Partition) FLASH will write the Recovery Image to the Recovery Partition so you can boot to it whenever you want / need to.
I don't know if there's any kind of threads where certain files are talked about sorry, but I could be wrong though.
I don't know much about G Pay, I was gonna try it too but my Bank doesn't support it. I've seen quite a few people reporting success in getting it to work / making payments with it in local stores with the mentioned SQL Fix so if you're lucky it'll work for you too
Click to expand...
Click to collapse
just got gpay to work with the sql fix. thanks for the help

How To Guide [TWRP] MI 11 (Pro/Ultra) (mars/star)

[TWRP] MI 11 (Pro/Ultra) (mars/star)​
WARNING : I do not know who made this TWRP and I am NOT taking credit for it. It was posted on eu site and I'm just sharing since there was no thread for twrp here on xda.
INSTRUCTIONS
1. Before starting the process, the bootloader must be unlocked.
2. Install Xiaomi USB drivers.
3. Enable Usb debugging from Settings - Additional settings - developer options.
4. Download TWRP for Mi 11 (Pro/Ultra) , and put it in your fastboot folder.
5. Put your phone into fastboot mode.
6. Rename downloaded file to "twrp.img".
7. Do the following command. It will automatically boot into TWRP.
Code:
fastboot boot twrp.img
8. If you get a screen asking for a pin, press 2nd option
and change language to English then enter phone pin.
9. Change language to English (press the 6th option).
10. Go to "Advanced" and select "Onekey inject TWRP".
11. Swipe to inject the TWRP. It might take a few minutes, so don't worry.
Note
1) Don't change the boot slot, currently (Slot A) for most or your device will not boot at all.
2) For user experiencing decrypt issue, you can try one of the methods below to enable decryption:
a. Remove all your security eg. fingerprint, face unlock, pattern and leave ONLY pin. Reboot to twrp and try again.
b. Reflash twrp.
c. LAST RESORT! Format data and factory reset your device then reflash twrp.
3. For user experiencing decrypt issue but just want to flash latest build:
a. Boot to twrp > mount > mount usb storage then transfer your rom.zip to data/media/0
b. Now go to install and look for rom.zip under data/media/0. Profit!
4. The decrypt issue was a bug on the Chinese twrp, no update since may so don't ask for an ETA.
CHANGELOGS
07/18/21
1) Additional instruction from scratch.
2) Additional note for people having decrypt issue.
CTTO: xiaomi.eu, hoangsang

Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D

skylerfly16 said:
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
Click to expand...
Click to collapse
Yes, They just did the new stable in TWRP Format.

The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile

speedtripler said:
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
Click to expand...
Click to collapse
Why did you install the Chinese exe?

skylerfly16 said:
Why did you install the Chinese exe?
Click to expand...
Click to collapse
The official one hadn't been released yet and I like a challenge sometimes

Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/

deleted post

I keep getting a " no such partician " fail msg , what am I doing wrong here?

speedtripler said:
I keep getting a " no such partician " fail msg , what am I doing wrong here?
Click to expand...
Click to collapse
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?

heinhuiz said:
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
Thx It's ok,I got it after a few attempts
The language on twrp still opens on Chinese and it needs changed to English each time but apart from that it seems to work fine!

SanHelios said:
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
Click to expand...
Click to collapse
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers

innocence07 said:
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
Click to expand...
Click to collapse
Is banking and payment apps still working?
Can you still pass safetynet check?

speedtripler said:
Is banking and payment apps still working?
Can you still pass safetynet check?
Click to expand...
Click to collapse
Yes and yes

Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future

sabrewulf said:
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
Click to expand...
Click to collapse
The recovery is fully functional as far as I can tell...
I did a complete backup successfully but I haven't tried to restore it yet

You click on everything ?

Hi,
after a long day of learning the hard way (got stuck in Fastboot Loop) I am now on stable EU 12.5.7 (MI11 Ultra, EU phone). So far so good, but I was wondering, how can I make TWRP stuck to the phone, meaning, when I push the power button to have an option like: Boot into TWRP. Is that possible or is there a "click this button with this... trick"?
ATM, I can only get TWRP to work, when I enable it via PC, which is not good.
I am asking, because I have an old Oneplus 6, which has this option. TWRP is installed and I can boot directly to it, if I want to.
Can you please help me out? Is there a trick or am I doing something wrong?
Greetings from Germany
Placebo

I believe you are on custom EU rom right? Just reboot into recovery, custom eu rom injects twrp as standard recovery

Hi, yes I am and I did that also. But still can't boot into TWRP from within the phone. Is there a trick after the injection?

Question [Solved] Help with fixing my phone back to Normal after playing with Roms & Twrp

Got the bootloader unlocked..should've read more & implemented over a proper guide.
long story short:
stared with magisk apk..when phone was fine.. then got into bootloop;
quickly downloaded & flashed the global (lime) MIUI V12.0.5.0.QJQMIXM;
installed twrp; should've done this before.
wasn't able to copy anything into internal storage.
Used Twrp to wipe phone.. & flashed the stock_global_miui_(lime)12.0.5 boot.img in fastboot
because twrp was saying "unable to decrypt fbe device" on internal storage
formatted using twrp.
booted properly but setup says device is locked because associated with existing mi account can't open wifi but was able to activate device upon entering password on mobile data setup completes but device restarts frequently & still unable to access wifi
I think it has something to do with "unable to decrypt fbe device"..
should I try flashing custom rom boot img?
please don't ban me..tell if I did something wrong, I'll correct that..
..
Edit:
MiFlash-tool Worked
Flashing other compaitable custom Rom also worked
..
Had twrp wipe the whole phone and the format the partions
& then flashed in fastboot & everything was normal.
..
FBE device encryption is basically storage encryption that prevents dirty flashing miui rom via fastboot.
this can be avoided by implementing proper procedure of magisk & use of lazypatcher.
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction.. godbless
[solved]
Currently I'm running Miui just like a new device.
I will make another guide thread on rooting systemlessly & flashing other custom rooms... if I succeed I will link it here..

Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.

zoel.fahmi said:
Try to reboot bootloader
then flash twrp
wipe everything and format the data partition
reboot to twrp again
then flash custom rom
If you're flashing miui again, your phone bootloader will be lock again and you need something like lazy2flasher if you wanna keep miui with twrp and magisk etc.
Click to expand...
Click to collapse
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..

xhykari said:
first of all thank you for taking out the time to read & respond..
I found an article with lazy 2 flasher earlier, I'll look into it..
is there any where I should look to find a suited custom rom for my phone..
Click to expand...
Click to collapse
you can use custom rom from Poco M3 since it's used the same SoC (662)
here : https://forum.xda-developers.com/f/poco-m3-roms-kernels-recoveries-other-develop.11969/
check the thread name Poco M3 / Redmi 9T or unified or codename like citrus and lime

whats the difference between Lime, Citrus, & Juice..
Mine is Lime
Juice is Lime & Citrus I think..
So will Juice work on a device which previously ran Lime?
..
basically can I install PixelPlusUi_Juice
or should I first try the lazy2flasher.. & @zoel.fahmi
where do I get lazy2flasher

If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable

Cursader said:
If anything goes for me (RedmiNote9Pro) i just use miflash to flash original miui and start all over from there, might not be the quickest method but is easy and reliable
Click to expand...
Click to collapse
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
..

xhykari said:
THERE IS AN MI FLASH TOOL too.. :O
whydoinotknowofthis.. What the heck..
can it bypass dm verity as well? like does it apply flash without lazypatcher?
do we need to provide it rom or can it fetch itself?
would you be please share some links for me?
Click to expand...
Click to collapse
If the bootloader unlocked and you can go into fastboot you can flash stock rom and It's just like it came from the store! Here you have link for your convinience: https://c.mi.com/oc/miuidownload/detail?guide=2

MiFlash-tool Worked..
(its the best tool for bringing mi devices from rom mess back to scratch new)
Flashing other Rom also worked..(pixelui)
juice = lime + citrus (works for both)
Thank you so much.. @Cursader & @zoel.fahmi for pointing me in the right direction..

I think I messed up royally

Long story short: I tried to install a GSI so I installed TWRP and flashed some necessary zips (vbmeta, mutidisabler, ...) from different sources and the GSI, but maybe it was a bad idea to follow multiple sources, because the phone was bootlooping when I tried to reboot into system. I then wiped everything and reflashed everything but that didn't fix it. After meddlilng around for a while, I was able to get into the download mode, so I thought of flashing the factory firmware with Heimdall. I used samloader and downloaded the supposedlly correct firmware (M215FXXU2BUH6/M215FODM2BUI1/M215FDDU2BUH1/M215FXXU2BUH6, region is BKD). When I was adding the files, I found out that I was missing the following files:
md5.img (MD5HDR)
efs.img (EFS)
sec_efs.img (SEC_EFS)
nad_fw.bin (NAD_FW)
param.bin (PARAM)
steady.bin (STEADY)
uhuh.bin (UHCFG)
blcmd.bin (BLCMD)
spu.img (SPU)
ul_key.bin (UL_KEYS)
nad_refer.bin (NAD_REFER)
dqmdbg.img (DQMDBG)
There were other partitions, but no files were listed for them, so I think they are not supposed to be flashed. There were also two different "fota.zip" files, but I didn't know what to do with them. Anyway, I flashed the other files, but the phone started bootlooping with the bootloader unlocked warning screen. I locked the bootloader from the download mode and tried again but no luck. I tried reflashing everything again, but the flashing stopped halfway with the message "super.img blocked by OEM" or something like that. I performed a force reboot with volume down + power and it rebooted into the "Emergency Recovery Function" screen. I reflashed everything again, but this time, without super.img, and it flashed fine, but the same bootloop problem remained. Looking up on the internet, it seems that efs.img has something to do with the IMEIs. I don't have any backup of it. I also don't know how to get the rest of the files (if all of them are even necessary), or what they even do/mean.
Basically, I'm trying to get it back to the factory software, or salvage it in any other way. Does somebody have any idea how to fix it?

Naah... Stuff like this happens to me all the time.
Download this ODIN first: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then download this firmware: https://samfw.com/firmware/SM-M215F/BKD/M215FXXU2BUG2
Now first a few things:
1. You probably downloaded a engineer firmware that isnt allowed as of now.
2. Heimdall is mostly dead, last I checked. It isnt very wise to use it.
3. LOCKING THE BOOTLOADER IN A UNSTABLE STATE IS FOOLISHNESS. I do not mean to offend anyone, but pls dont do this.
4. I think you are using ErfanGSI/ some other port. These will NOT work. Only phhusson's GSI's have worked for me so far.
So coming back to the topic, Just open up the ODIN and connect up your phone. It will get recognized. If it is not in emergency/ download modes, just hold vol down + power, then press both vol buttons and connect to pc immediately - it will boot into dl mode.
Select the BL, AP, CP and HOME_CSC. Flash these.
It should reboot right back up into stock.
Also, are you using my vbmeta zip from ItsMeKande's thread?
Chill
GuruPrasadAH

Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
GuruPrasadAH said:
Also, are you using my vbmeta zip from ItsMeKande's thread?
Click to expand...
Click to collapse
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?

newt23 said:
Thanks for the fast response. I followed your instructions and was able to recover the device. It was actually bootlooping after flashing the firmware. I had to lock the bootloader to be able to successfully boot into the system. I was kind of worried, because I was running Odin in VirtualBox since Odin is Windows-exclusive and I don't use Windows. I'm glad everything worked out well in the end. I used to be into Android modding years ago, but my last Android device was Android 5 based and I stopped modding it once it got to my "perfect state". I haven't kept up with the modding scene since then. Things seems to have gotten a lot more complicated with newer Android versions.
Yes.
Since you seem to know about this stuff, can you recommend a GSI that's customizable, lightweight, and doesn't have GApps or microG?
Click to expand...
Click to collapse
My to-go answer is always crdroid. Its lightweight, customizable, and comes in variants with gapps, foss and vanilla. The one you're looking for is vanilla. Here's the post where u can find the link
Any official or unofficial lineage OS for Samsung galaxy M21
Hello everyone so I have a Samsung galaxy M21 with One UI 3.1 core. Are there any lineage OS official or unofficial builds for Android 11? If you know please reply to this, thank you in advance!!! 🙏🏾🙏🏾🙏🏾
forum.xda-developers.com

Hmm, it didn't work. I get bootloops...

Did you follow all the instructions given in that thread?
Only if you flash vbmeta, Multidisabler it will boot.
Then too magisk is recommended. The zips are in that thread.
Follow the instructions and let me know. On guy OldNoobOne also successfully flashed and booted a gsi
Let me know if it works
Chill
GuruPrasadAH

For Multidisabler just do a google search one for samsung devices will appear

Here's what I did (stock firmware, unlocked bootloader):
1. Boot into dl mode
2. Flash TWRP and boot into it
3. Wipe > Format data > "yes"
4. Reboot > Recovery
5. Advanced > Terminal
6. "cd external_sd/flash"
7. "super mount system"
8. "super flash system crdrom-v313-210921-arm64-bvZ-lite.img"
9. Install > vbmeta.zip, multidisabler-samsung-3.1.zip"
10. Reboot into system
And I get bootloops. Multidisabler detects Android 10, doesn't find the stock recovery and fails to mount /system. Maybe that's the problem? I'm using this one.

Also try flashing magisk... I dont really understand what is happening to you.
Maybe you set the system as read only? Really not sure.
Also, a ROM might be coming soon
Chill
GuruPrasadAH

Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!

newt23 said:
Yes, that did the trick! I'm able to boot into crDroid now. I was wondering if I needed to flash something to fix the corners, but seems like a simple reboot fixed it.
Anyway, thanks a lot for your help!
Click to expand...
Click to collapse
Use Overlay-Fix by dev Yillie. It had worked for me on crd too. You will find Yillie on telegram 'Galaxy M21 Updates' group, download from there.