Database Develop

Device stuck in TWRP

Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
hey does your device have an working os ?

mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported

Benjamin0702 said:
hey does your device have an working os ?
Click to expand...
Click to collapse
Benjamin0702 said:
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported
Click to expand...
Click to collapse
Like I said, I am stuck in TWRP. I can't boot anything and I guess I don't have any os anymore.

Are you frozen in a black screen?

Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.

mrtr33 said:
Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.
Click to expand...
Click to collapse
You need to erase the "misc" partition.

VD171 said:
You need to erase the "misc" partition.
Click to expand...
Click to collapse
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext

mrtr33 said:
View attachment 5264227
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext
Click to expand...
Click to collapse
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/

VD171 said:
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Click to expand...
Click to collapse
Now I get the following error when trying to install the xiaomi.eu ROM form SD Card:
Code:
E: unable to update logical partition: /system_ext
E: unable to decrypt FBE device
After installating and rebooting I am back at TWRP again.

Trying to boot my Huawei P9 inot TWRP, stock rom always overwrites even if I boot into recovery correctly

As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23

Catnip202X said:
As the title suggests, I decided to flash Lineage OS onto my old Huawei P9 phone. I unlocked the bootloader, which was a mess but I did indeed achieve that goal.
However, things screeched into a halt as I found out that my specific model of P9 does not support SU or rooting. So the only way I can install TWRP is by running the
Code:
adb reboot bootloader
flashboot flash recovery_ramdisk twrp.img
Things got kinda weird when I tried to boot into recovery mode. I've tried all the ways, from using all kinds of key combinations to googling software solutions, sadly all my efforts were in vain. However, I can now boot into recovery mode consistently with the classic "volume + and power button" key combo. The problem I run into is that everytime I boot into it, I get the error screenView attachment 5281583
What can I do? all the other solutions on Google say that I need to root to use the software solutions so I'm stuck in this weird circular logic loop. So any suggestions?
Running EMUI 8.0.0.552(C01)
Model EVA-TL00
Cpu: Hisilicon Kirin 955
Kernel version 4.4.23
Click to expand...
Click to collapse
TWRP must be flashed with the command:
fastboot flash recovery_ramdisk ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help

zgfg said:
TWRP must be flashed with the command:
fastboot flash recovery ...
After flashing, first thing must be rebooting to TWRP by key conbo - it's always that same trick for Huawei phones
And btw, better ask inside the P9 LOS thread, to get attention and help
Click to expand...
Click to collapse
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.

Catnip202X said:
I've tried
Code:
fastboot flash recovery twrp.img
This doesn't work as I've learned that the correct partition name is recovery_ramdisk. Flashing the recovery gives the error.
Click to expand...
Click to collapse
Yes, sorry, you are right, typo.
But I wanted to point that you must use fastboot flash command (not FLASHBOOT or whatever you used in your post #1)
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
But also READ the P9 LOS thread - it clearly describes that LOS must bi flashed from fastboot, not from TWRP and it actually asks users not to use TWRP
See here and better ask there to get the answers directly from developer:
[ROM][Treble][microG]LineageOS 16.0 for HUAWEI P9
This thread is dedicated to provide Lineage-OS 16.0 builds with microG included for the HUAWEI P9 with current security patches. It is a treble build, therefore it could also work on other devices, but I haven't tested. And yes, the camera...
forum.xda-developers.com

zgfg said:
And that you MUST reboot to TWRP as the first thing after flashing it - otherwise (as you claimed), stock recovery will overwrite the TWRP you flashed
Hence, prepare you fingers for the key-combo, type fastboot reboot, disconnect USB and make sure you properly keep pressing Vol+ until it boots to TWRP. Then you can safely reboot to the system
Click to expand...
Click to collapse
I have indeed tried this route, but as I have stated before, trying to boot into recovery mode right after flashing TWRP and pressing key combo still boots me into the error screen where it says that I need to update something. On the bottom of the screen will also show errors such as Function11 not found and error 2 no image etc. I’ll try to replicate it and send you a picture of the error screen when I get home from work tonight.

Stuck On Fastboot (SOLVED)

I tried to uninstall magisk via twrp flashing boot.img but only appeared the fastboot screen, so tried to restore stock rom but still on fastboot
Tried MiFlash, XiaoMI tool v2, MiFlash Pro with so many fastboot roms, flashed custom roms (included the aosp derivates and the latest miui eu) and still no luck, at least twrp and custom recoveries works fine
Please help, I already spent to many days trying to fix it
Edit: Tried to flash vbmeta again and now it works

uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)

fonzacus said:
uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)
Click to expand...
Click to collapse
Basically i tried everything in the guide and other xiaomi guides (Except flashing via EDL), in the gui tools always show as "Success" and via fastboot all seems to be flashed correctly but still got the fastboot screen
Edit: Trying one more time with another vbmeta and instaled dotOS, Now it works

just a side note, miui >12.5.x were built to be more picky with everything in general. you mightve been blocked by miuis avb (custom vbmetas workaround this) when you were sent to fastb
hence why twrp 3.6.x includes an advanced installer option (workaround this and other brands)
as for trying to fully uninstall magisk, lots of others (including me) failed lots in the past on 23 and canary (and other forks), reinstalling again seems to fix it
thankfully you got it up and running, tho id recd something other than dot, i and others found it battery heavy for some strange reason ;P

good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

xXchizaXx said:
good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.View attachment 5650943
Click to expand...
Click to collapse
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?

fonzacus said:
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?
Click to expand...
Click to collapse
Fortunately, you can install the Miui through the flash ROM, but unfortunately the Miui 11 version blocked me from starting up again, so I can't put any more ROMs in it.

Want to back to stock from CalyxOs On Xiaomi A2

Hello,
it's been about two years since I installed CalyxOs on my A2 and I don't want to do anything stupid.
I would like to ask you for your advice to go back to the original AndroidOne ROM and then test other ROMs like /e/ OS or GrapheneOS for example.
I'm on linux, a Manjaro, and no worries with the terminal unless you have an application at hand.
Knowing that the current ROM is a CalyxOs under Android 11, I share with you the data in my possession.
Thanks in advance
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well, if you are running with locked bootloader, you have to unlock it again through fastboot.
Toggle oem unlock in the developer options and then fastboot oem unlock.
Then you can boot twrp or Lineage recovery, fastboot flash boot <recovery_filename>.img to wipe your device for each slot.
I personally moved away from CalyxOS too and went back to LineageOS 18.1.
I also updated the firmware to the latest release firmware_jasmine_sprout_V11.0.28.0 cause that version of CalyxOS uses a old firmware that allowed to lock the bootloader, use twrp to flash the update package firmware and then move back to the recovery you want.
About the OS I see you like /e/ is available, for Graphene they support only pixels so you are out of luck I guess.

Hello,
So according to you, being on android 11 I can reinstall directly from a recovery such as lineage-18.1-20220507-nightly-jasmine_sprout-signed.zip
Apart from the firmware, no other manipulations or downgrade is necessary?

Hi @Reynald0,
I haven't been back for a while and I'm still using my xiaomi A2 under CalyxOs.
I have a problem, my A2 is no longer recognized in USB, whether under Linux, Windows, having tried many different cables. Reset, etc...
The A2 loads 4 seconds then disconnects, but it is not discovered by the PC.
So I am with an A2 under CalyxOs, without TWRP installed, without possibility to connect it to a PC.
Will one of you be able to help me to put it back to its original stock state?

romhtk said:
Hi @Reynald0,
I haven't been back for a while and I'm still using my xiaomi A2 under CalyxOs.
I have a problem, my A2 is no longer recognized in USB, whether under Linux, Windows, having tried many different cables. Reset, etc...
The A2 loads 4 seconds then disconnects, but it is not discovered by the PC.
So I am with an A2 under CalyxOs, without TWRP installed, without possibility to connect it to a PC.
Will one of you be able to help me to put it back to its original stock state?
Click to expand...
Click to collapse
Well, you need fastboot to perform a lot of operations.
Those 4 seconds make me think of Magisk, or in general that indicates a boot problem, red color indicator.
You can forget TWRP from now on with LineageOS 18.1 and LineageOS 20 we use Lineage recovery.
If you are sure your device isn't detected using fastboot devices when you are into fastboot mode then there is not much we can do, if you used Magisk you will have to deal with changing slots and temporary flash the recovery as a boot image.
I don't recall exactly, but the first thing is to unlock the bootloader again, then upgrade the firmware cause CalyxOS used an old one, and then you should be good.
If you plan to use Magisk and Lineage recovery the most important things you will have to deal are:
Switching between slots,
fastboot --set-active=a , set the a slot as active
fastboot --set-active=b , set the b slot as active
fastboot flash boot boot.img && fastboot reboot , where boot.img is the Lineage recovery

Reynald0 said:
Well, you need fastboot to perform a lot of operations.
Those 4 seconds make me think of Magisk, or in general that indicates a boot problem, red color indicator.
You can forget TWRP from now on with LineageOS 18.1 and LineageOS 20 we use Lineage recovery.
If you are sure your device isn't detected using fastboot devices when you are into fastboot mode then there is not much we can do, if you used Magisk you will have to deal with changing slots and temporary flash the recovery as a boot image.
I don't recall exactly, but the first thing is to unlock the bootloader again, then upgrade the firmware cause CalyxOS used an old one, and then you should be good.
If you plan to use Magisk and Lineage recovery the most important things you will have to deal are:
Switching between slots,
fastboot --set-active=a , set the a slot as active
fastboot --set-active=b , set the b slot as active
fastboot flash boot boot.img && fastboot reboot , where boot.img is the Lineage recovery
Click to expand...
Click to collapse
Thank you very much for your answer.
I think I misspoke, if I understood your message correctly. The phone starts up correctly, CalyxOs works perfectly well, but I can't charge it, nor access the files by connecting it to a pc. Magisk is not installed

I just rebooted in fastboot mode and with an I just rebooted in fastboot mode and with an
Code:
adb devices
, the tel is not detected.
Can you tell me what is DSU?

romhtk said:
I just rebooted in fastboot mode and with an I just rebooted in fastboot mode and with an
Code:
adb devices
, the tel is not detected.
Can you tell me what is DSU?
Click to expand...
Click to collapse
Sorry, I have no experience with GSIs, so I can't help you with them right now.
I will try them in the future if there are no alternatives ^o^

I went to a computer specialist, tested new cables, etc... nothing to do.
adb/fastboot via wifi ?
How complicated is it?
Reynald0 said:
Sorry, I have no experience with GSIs, so I can't help you with them right now.
I will try them in the future if there are no alternatives ^o^
Click to expand...
Click to collapse

Question Reflashing stock ROM on bootlooping device

Hi.
Bought this phone 4 months ago and it went into a boot loop, where it would only show the battery empty icon. Yesterday, I tried turning it on again and noticed, that it's stuck at the Redmi - Powered by Android" screen. From this screen, I can enter fastboot. See this video:
VID_20230417_194410.mp4
drive.google.com
I've read that there are a couple of options for reflashing this device:
- aks someone with the authorized Xiaomi account to reflash stock rom using the MiFlash tool (no bootloader unlock needed)
- put the device somehow into ETL mode and reflash stock rom using the MiFlash tool (no bootloader unlock needed)
I've tried contacting someone, who for #1, but they aren't willing to help, for some reason (I'm wiling to pay). For #2, I'd have to open up the device, which I'd like to avoid doing.
Would anybody know of any other options for fixing this?
Thank you in advance!

okay, which version of MIUI are you running?
first get the fastboot rom of the version your phone supports , i recommend the global version fastboot rom , because it works and its stable and u get your updates
download this fastboot rom first
Temporary file download page
miuirom.org
and I will give you the MI flash tool working version at like 6 hours after, Ill post the remaining steps after you download this , btw, you will get a .tgz file , when u download the Rom, thats the one you need

RunoTheDog said:
Hi.
Bought this phone 4 months ago and it went into a boot loop, where it would only show the battery empty icon. Yesterday, I tried turning it on again and noticed, that it's stuck at the Redmi - Powered by Android" screen. From this screen, I can enter fastboot. See this video:
VID_20230417_194410.mp4
drive.google.com
I've read that there are a couple of options for reflashing this device:
- aks someone with the authorized Xiaomi account to reflash stock rom using the MiFlash tool (no bootloader unlock needed)
- put the device somehow into ETL mode and reflash stock rom using the MiFlash tool (no bootloader unlock needed)
I've tried contacting someone, who for #1, but they aren't willing to help, for some reason (I'm wiling to pay). For #2, I'd have to open up the device, which I'd like to avoid doing.
Would anybody know of any other options for fixing this?
Thank you in advance!
Click to expand...
Click to collapse
If you can boot into fastboot, then it is already enough.
Now, I suppose your bootloader is still locked
You need to download a MIUI ROM from "EEA", from any trusted website, and remember to download the "Fastboot" ROM to flash it (my favorite is mifirm.net, it downloads faster)
Install MiFlashPro - attached at the end of the thread
Open it up, and you will be greeted with this.
Click on the "Mi Flash" tab, as it is the only one we need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will be greeted with this window now:
After you have done downloading your ROM, extract it to any place.
If MiFlash does not recognise the directory you have extracted in, move it to C:\. Not any external drive, your main one
Now click on the "select" button box, go to your ROM directory, and simply select its folder
Boot your device into fastboot (PWR + VOL-), click on "refresh" button box and your device serial number should appear on the first line.
Now simply click "flash" and let it do its job for 10 to 15 minutes. It will reboot automatically.
If you dont succeed, please read this thread:
Thread '[GUIDE] UNBRICK YOUR HARD-BRICKED MTK' https://forum.xda-developers.com/t/guide-unbrick-your-hard-bricked-mtk.4564029/
You will require BROM and to bypass and to flash via SP Tool.
RunoTheDog said:
For #2, I'd have to open up the device, which I'd like to avoid doing.
Click to expand...
Click to collapse
You have either got confused, or being scammed
Newer MTK devices do not require the opening of the device. I suppose you have been probably confused with a Qualcomm Snapdragon based service, that does require the opening, so you can access EDL mode and flash your phone into life, or someone just put up the Redmi Note 10 5G and is a scam, also, on MTK, you do not need to pay for a authorized Mi account. On MTK, it is easily bypassable due to BROM

Thank you both.
I put ran MiFlashPro, pointed it towards the downloaded eea stock rom file and attempted to flash it, but got this error message:
So I presume this is due to locked bootloader? I'll try to follow the second link.

I actually managed to enter recovery mode and do a factory reset. Currently setting it up and plan on updating it.

RunoTheDog said:
I actually managed to enter recovery mode and do a factory reset. Currently setting it up and plan on updating it.
Click to expand...
Click to collapse
Good to hear you got sorted. I basically bricked my phone last week (only 3 weeks old ) after trying to switch from MIUI 13 Global to EEA. I managed to get it into BROM mode and used MTK Auth Bypass which allowed me to use Chimera Tools to flash the phone again as nothing else seems to work with a locked bootloader. Currently running MIUI 14 with root and magisk optimisations (blur/high end tweaks, MIUI monet etc) and loving it! Just need a way to bypass Play Integrity API for Google Wallet