Database Develop

Question Redmi Note 10 5G Bricked no fastboot/recovery

Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated!
{
"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"
}

assistance... you have lost warranty. anyway you can try this metod (work with my old mia3 but have a qualcomm chipset)
first: CLOSE YOUR PHONE!
install mi pro flash tool https://www.androidfilehost.com/?fid=14943124697586360238
PRESS power+ vol up+vold -
connet to pc via USB
OPEN MIflash tool pro
if your phone will be recognized you can flash stock firmware
with miflash pro you can install all drivers you need (but i'm not sure, test by yourself)
good luck.
if this procedure don't work go to an assistance point. you have damaged the bootloader
before mod devices with a/b partitions is very important read guides with attention. if you don't want trash a new device
you can also try sp flash tool, specific for mtk devices
How-to flash or install Stock ROM (Firmware) using SP Flash Tool
Step-by-Step guidelines to flash or install Stock ROM (Scatter Firmware) on Mediatek devices using the SP Flash Tool.
androidmtk.com

tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
did you even open it? tannedcan in every single post where there are instructions how to root/unlock/change rom
there is a DISCLAIMER for a reason.
that msg remark that you can brick your device if you dont know what you are doing or if you have doubts!
most of times things can be recovered but NEVER open a device in warranty.

simika said:
did you even open it? tannedcan in every single post where there are instructions how to root/unlock/change rom
there is a DISCLAIMER for a reason.
that msg remark that you can brick your device if you dont know what you are doing or if you have doubts!
most of times things can be recovered but NEVER open a device in warranty.
Click to expand...
Click to collapse
yes, i'm 100% agree with you

tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
I was exactly in same trouble, use This guide that solve the issue.
How to flash an MTK secure boot device without a custom DA​This is a step by step guide showing how to flash a Mediatek (MTK) secure boot device without using a custom download agent (DA). A little history Secure Boot M
forum.hovatek.com
Press mobile three buttons and connect cable to pc (use USB 2.0) to enter BROM mode (are like ERL mode in Snapdragon models). Because mtk models don't have test point. So don't need to disarm mobile.

Did you find the solution?

please any solution? i am into same problem. need stock rom for
Redmi Note 10 5G choppin​

Zaiserr2 said:
I was exactly in same trouble, use This guide that solve the issue.
How to flash an MTK secure boot device without a custom DA​This is a step by step guide showing how to flash a Mediatek (MTK) secure boot device without using a custom download agent (DA). A little history Secure Boot M
forum.hovatek.com
Press mobile three buttons and connect cable to pc (use USB 2.0) to enter BROM mode (are like ERL mode in Snapdragon models). Because mtk models don't have test point. So don't need to disarm mobile.
Click to expand...
Click to collapse
this really helped, thanks but only with usb 3.0

tannedcan said:
Hi all, dumbass me was so excited to get a new phone, I went around Redmi Note 10 ROMs on my Note 10 5G and bricked it... It won't boot into fastboot or recovery. When I boot it up holding the up/power buttons, the screen lights up and phone gets briefly recognized by my computer before rebooting. I've done some digging around and tried to find edl point? of this phone but couldn't get far. Any help would be appreciated! View attachment 5431881
Click to expand...
Click to collapse
same issue sir my device show handshake failed during flashing

wetito said:
assistance... you have lost warranty. anyway you can try this metod (work with my old mia3 but have a qualcomm chipset)
first: CLOSE YOUR PHONE!
install mi pro flash tool https://www.androidfilehost.com/?fid=14943124697586360238
PRESS power+ vol up+vold -
connet to pc via USB
OPEN MIflash tool pro
if your phone will be recognized you can flash stock firmware
with miflash pro you can install all drivers you need (but i'm not sure, test by yourself)
good luck.
if this procedure don't work go to an assistance point. you have damaged the bootloader
before mod devices with a/b partitions is very important read guides with attention. if you don't want trash a new device
you can also try sp flash tool, specific for mtk devices
How-to flash or install Stock ROM (Firmware) using SP Flash Tool
Step-by-Step guidelines to flash or install Stock ROM (Scatter Firmware) on Mediatek devices using the SP Flash Tool.
androidmtk.com
Click to expand...
Click to collapse
is it okey or I'm the only one whose phone just keeps getting recognized and unrecognized by the PC every 5-10 sec ????
even though i have tried same with diffrent PCs and diffrent cables
PLEEEEEEEEEEEEASE HELP because this is by far the biggest obstacle I had in this precedure

It is not OK, you are the only one
Start from BROM mode and proceed from there.

viktak said:
It is not OK, you are the only one
Start from BROM mode and proceed from there.
Click to expand...
Click to collapse
I appreciate your response but
i did it all
i already have python the last version
i downloaded the MTK driver
i pressed the whole 3 buttons in the phone connected to PC (the phone didn't give any output at all)
i did set it up (which does appear and dissapear in every 5secs so I had to be quick)
then for the main.py file didn't capture the phone (obviously because I constantly hear the devices get recognized and unrecognized and nor the cable nor the PC are the cause
the theeere I am, stuck in the very 1st step.
please I would be so thankful if you could diagnose the problem just for me to know what to do.
personally I don't think it's a phone hardware problem because back in the days lol i unlocked bootloader and installed recovery, all was very functional and everything responded smoothly
if you wanted to know any other detail i would be so pleasured to tell you

I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.

viktak said:
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
Click to expand...
Click to collapse
alright, appreciate it
thank you
pardon my abbreviations knowledge but I really don't know what a PM is

Did anyone found the way to back the phone to life???
If anyone can respond me quickly I will apreciate it.

Yes, it's quite easy. Just follow my guide on my blog. DM for details.

viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
Ok, I will see

viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
I have a problem, I can't make it work, not even the fastboot or MTK tools

viktak said:
Yes, it's quite easy. Just follow my guide on my blog. DM for details.
Click to expand...
Click to collapse
post a link to your blog

viktak said:
I don't have the time now. Earliest I can help you is on Monday. Send me a PM to arrange for it.
Click to expand...
Click to collapse
i need help on this very issue pls help meee

Question How to setup spflash for the soft bricked phone

Hi, my wife gifted me that Chopin phone form China, after a wrong "flash and lock" global firmware now my phone is stuck on bootloader.
According to this thread:
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
I have all the files needed to setup sp flash and try to put again the Rom in the phone, which is now not unlocked and no usb debugging on.
Can someone please give me a tutorial on how to use those files? My phone still not recognised in sp flash com port, I don't know how to do.
If anyone will help me it will be so appreciated, thanks!

If you need to disable authorisation, did you run the MTK Auth Bypass tool and get the message "Protection disabled"? That's what I had to do before SP Flash Tool would flash the phone (without disconnecting it or rebooting), and I also had to set the baud rate to 921600, although that was all under Linux, and the phone was still unlocked.

it's complicated. with phone locked fastboot commands don't work. with my hold mi a3 fastboot flashing unlock command work. but with miui and mtk chipset probably it's useless. but u can try. if u boot into bootloader with mediatek driver the pc should recognize your phone also if it's blocked

1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
{
"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"
}
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.

Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.

Bonscia said:
Thanks for the help, the problem I'm facing it's Auth tool cont recognise the phone, when I open the shell keep saying waiting for the device.
Driver are mtk with Libus installed, dunno.
When I restart the phone immediately have the logo then, if volume up I can log mi assistant or with volume down the bootloader screen.
Click to expand...
Click to collapse
1. Check your device driver for USB, suggest you re-install the MTK usb driver.
2. First run the program, select the Auth by pass then press start.
3. Make sure phone is in "power off" state, press Vol+, Vol- and power (all three at the same time), and don't release it, plug in USB cable and wait.... Don't release these three buttons until it is Auth by pass OK.
During this process, take a look at device manager, there must be one item like portable device - USB ( Com 3). keep flashing.

sure u add reinstall mtk driver

Tried many drivers, always same result:
Driver says the device can't start. Tried to install lisbus too but no changes.

Bonscia said:
Tried many drivers, always same result:
View attachment 5499127
View attachment 5499129
Driver says the device can't start. Tried to install lisbus too but no changes.
Click to expand...
Click to collapse
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.

kirinin said:
you "must" remove (uninstall) the driver first then re-install the MTK usb driver again.
Click to expand...
Click to collapse
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.

Bonscia said:
I did that many times, with win 10 no drivers signed mode, with many different mtk drivers but nothing was working. I'll try clean my windows and then start again with the drivers.
Click to expand...
Click to collapse
is a win10 problem that i also haved. hard to solve. u can try windows 7 via virtualbox (solved a lot of my problems in the past) or format and install a modded version of win10 (but i dont suggest this)

Virtual box looks no longer available, I'll install a fresh copy of win 7 in another partition, never give up lol

virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere

wetito said:
virtualbox is available for all system. i have a win7 virtualized under my linux pc, and miflash works fine. no bugs. if my tips makes you happy dont try. is not my problem, i didnt bricked my phone. i dont make things without know what i'm doing. good look. u can buy a new phone if u prefere
Click to expand...
Click to collapse
? I've just told you I've tried to download virtual box for win 10 but it's not avaible now or server was temporarily down for the download, so my only way it's to set up a fresh copy on win 7 on my pc, I can't understand your hanger answer.

kirinin said:
1: Unzip this attached file into a folder. run it.
2: select the unlock bootloader and start, then connect you phone via usb with all three buttons pressed. (Phone must be off before connect, )
View attachment 5498521
3: Your bootloader will be unlocked.
4: Close the program and re-start again, this time, select auth bypass and start, then repeat the phone connection. after at the bottom line, it show bypass ok.
View attachment 5498523
from here you may flash again rom via Miflash or SPflash.
P.S: I think the file size is too big, I can not attach it here. Sorry! P.M me if you wish.
Click to expand...
Click to collapse
Hi, can you share this Zip file with link drive or mega?
Thanks in advance

Which zip file? I have only this one
https://forum.xda-developers.com/attachments/mtk_bypass_final-rar.5444529/I
finally flashed the Rom with so flash but now the phone reboot in assistance mode sayings "NV data corrupted" I'm about to cry

Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.

Link with files is this, I've seen other link don't work
Redmi Note 10 Pro 5G brick
Redmi Note 10 Pro 5G Chinese version with fastboot unlocked. After unsuccessful firmware. At startup, it goes into fastboot, you can load it into recovery. Wipe doesn't help. When trying to flash through fastboot MiFlashPro "FAILED (remote: 'not...
forum.xda-developers.com
Download MTK Universal Tool V5 | MediaTek All in One Tool Latest Free
MTK Universal V5 Tool is a small MediaTek All in One Tool designed to disable user locks, bypass FRP, Auth Bypass, Format Data (user data format),
www.gadgetsdr.com

Bonscia said:
Hi, I've followed your instructions, I've finally flashed the Rom into the phone, but now phone bootloop into recovery, it says "nvdata is corrupted", I've took the scatter file from the Rom folder, how to fix that problem now? Thanks.
Click to expand...
Click to collapse
try wipe data. also u can control the active slot. try change it and reboot

Hi, finally I can install the Recovery V12.5.16.0.RKPCNXM rom and the engineering rom but have no baseband and no IMEI. Tried many times to put my IMEI codes with no luck, looks I need the mt6893 modem file to use sn writer but no way to find them on net, can someone share those files please? Thanks

How To Guide [GUIDE] [RUI3] Unlock bootloader on RealmeUI 3 with deep testing.

It is now possible to unlock bootloader using the in-depth deep testing app, however it will only work on Thailand firmware, so we are going to flash the Thailand firmware and use the in-depth app on it.
Links:
MTKClient: https://drive.google.com/file/d/13KohUUeuzVoGKxVWIuLDZx11PV8EeMBj/view?usp=sharing
SP Flash Tool: https://drive.google.com/file/d/1McZ11On8XbxGgE-hMA_nZqErHI_QwjQT/view?usp=sharing
MTK Drivers: https://drive.google.com/file/d/1UExJQxI1DmBGeDoYPul5YTXitOnsU6zx/view?usp=sharing
Thailand Firmware: https://drive.google.com/file/d/192KboBbW1eXzb6DWVlGAkGE-PEcgnHBJ/view?usp=sharing
Deep Testing APK: https://drive.google.com/file/d/1pESMmJef6Gm9YlJAE7OA_DDNnhFn3Jpz/view?usp=sharing
Libusb port filter: https://sourceforge.net/projects/li...ibusb-win32-devel-filter-1.2.6.0.exe/download
Flashing Thailand firmware:​We are going to flash this in SP flash tool, first, let's setup MTK authorization bypass (if you have already setup python and drivers then skip this)
Install python from https://www.python.org/downloads/ and make sure it's configured
Go to the Driver folder, right click cdc.acm.inf and install it.
{
"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"
}
Install libusb port filter, afterwards click Next and hold volume up and down button, then choose MediaTek USB Port.
Now click install, next install UsbDK from here: https://github.com/daynix/UsbDk/releases/
Once you have done that, open a CMD/Powershell in the directory of MTKClient, write pip3 install -r requirements.txt and python mtk payload, hold the volume up and down button and plug the device in
If everything went well, you should be seeing this:
Now open SP Flash tool, go to Options > Option
Now go to Connection and select UART, set the baud rate to 921600
Now, open the scatter file (MT6785_Android_scatter.txt) from the directory of the firmware, it should load the firmware
Unselect opporeserve2 and click the Download button, it should start flashing
Once it is done flashing, you should see this:
Don't forget to reboot the device into recovery mode (volume down + power) and format data.
Updating to RealmeUI 3:​Since it is not possible to use the deep testing app on RealmeUI 2, you must update to RealmeUI 3, simply update it from the update app in settings, if you do not get the update, we can't do anything about it.
No need, replaced firmware link with RealmeUI 3 Thailand firmware, just flash that and use the in-depth app in the guide!
Using the deep testing app and unlocking the bootloader:​Download and install the deep testing app, tap "Apply Now" and accept the agreement, you should be seeing this now:
Wait 3 to 5 minutes, close the app and reopen again, tap "Query verification status" and you should see this:
This means your device now has unlocked fastboot access, tap "Start deep testing" and the device will reboot to fastboot mode
If you see this, the device is now in fastboot mode, to unlock the bootloader plug the device into a PC and write fastboot flashing unlock in Fastboot/ADB directory, you should see this:
Press the volume up button, the bootloader is now unlocked, congratulations!
NOTE: you can return to any EEA/Indian firmware you were on before and still have the bootloader unlocked.
Credits:
@bkerler for MTKClient

I tried this method on my primary Realme 8 device (Bangladeshi varaint) and it did worked.

Nice tutorial!

Also a pro tip for recovery mode can't be accessed after changing firmware and device keep rebooting after every 5 mins while stuck in realme bootanimation
download latest platform tools from google's official developer website, go to fastboot mode, enter command "fastboot reboot recovery"
you will be in recovery mode
then format data
your device will boot to OS after that

Does it work on realme UI 3.0 C.09 (bootloader locked)?

AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Thank You

AJ⁰⁰⁷ said:
Does it work on realme UI 3.0 C.09 (bootloader locked)?
Click to expand...
Click to collapse
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.

ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Indian 8/128 variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Ohhz that's bad @plarfman

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
I think you misunderstood it. I was asking that can I flash it over my Indian C.09 firmware?

plarfman said:
It shouldn't matter which firmware you are on right now, as for updating to TH RUI3 firmware it dosen't matter which C.0x it is as long as it's RealmeUI 3.
Click to expand...
Click to collapse
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.

ShahriarX1 said:
Was the Thailand firmware you attached in the post official??
Cause I got an error while flashing it. It says the firmware is not official.
Click to expand...
Click to collapse
Show a screenshot.

ShahriarX1 said:
No. It's not working on RUI3 c.09 version. I've tried on my Bangladeshi 8/128 GB variant. And it got bricked after flashing the Thailand firmware.
Click to expand...
Click to collapse
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.

I don't know why after unlocking, entering recovery mode gets difficult. I wish that can be accessed while pressing buttons.
It's like recovery combo turns into fastboot combo
Also Oppo/Realme stock recovery has a problem when magisk is installed. It will bootloop forever when reboot to recovery from magisk and it's pretty hard to get into fastboot mode that moment.
The real fix for that problem is restore stock boot and dm-verity image

plarfman said:
Show a screenshot.
Click to expand...
Click to collapse

AE_Fahim said:
Stuck on recovery mode text? Then you should erase userdata, metadata and md_udc using mtkclient
And yes, mine is also Bangladeshi 8/128 varaint.
Click to expand...
Click to collapse
Flash is not completing bro. Have a check on the Screenshot and suggest.

ShahriarX1 said:
Flash is not completing bro. Have a check on the Screenshot and suggest.
Click to expand...
Click to collapse
Looks like your file got somehow corrupted. You can try downloading ofp file, manually decrypting it and merging multiple super.img using simg2img (super 2 must be Thailand) and setting super download is true from scatter file.

all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!

Yadhevdev66 said:
all set! I went to fastboot mode using deeptest tool. But i don't know what to do after that to unlock the bootloder device. Kindly help me!
Click to expand...
Click to collapse
in fastboot mode enter
Code:
fastboot flashing unlock

can you send the fastboot drivers?

How To Guide [GUIDE] UNBRICK YOUR HARD-BRICKED MTK

MIFLASHPRO PROCEDURE​
The MiFlashPro procedure is easier (and the easiest to recover your hard-bricked device), as you do not require the installation of any other external program (like python used in MTK Client for example (expect, of course, the drivers)
MTK Client is a more complicated installation as it requires the installation of Python and Git, which can be harder to use commands for people that don't or never used Python and Git, but gives you access to lock and unlock your bootloader with no 168 HOURS wait
In general, newer MTK chips are really easy to unbrick, even from a hard-brick, as it does not requires to open your phone and test-point it (especially this forum MTK 6833), compared to Snapdragon chips, which is the opposite and even costs 25€ to have a "Authorized Mi EDL Account". Keeping that out of the way, lets get to it
FIRST OF ALL​Install the MTK Preload/BROM VCOM drivers for your computer to recognise your phone in BROM state and follow the instructions given in the installation. Attached at the end of the thread
And download any MIUI ROM version from any trusted website (my favorite is mifirm.net, it downloads faster)
INSTALL MIFLASHPRO Attached at the end of the thread​There's two different Mi Flash(es). Mi Flash and Mi Flash Pro.
Mi Flash is only used to flash MIUI in your device, nothing special, probably everyone knows about it.
Then theres Mi Flash Pro (MFP for short). It's an All-In-One (AIO) tool, as shown below.
{
"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"
}
We got the some tabs, but let's focus on the "Recovery" and "SP Flash" tabs, as we do not need the other ones.
Recovery - Recovery flashing. If your device is only booting to Recovery (which can be possible, since someone here has got a case that couldn't boot to fastboot neither system, only to recovery), by writing both your device IMEI's on the spaces, then clicking "Refurbish" leads to a more advanced factory reset than just wiping your data normally. This can get you out of recovery and go back to MIUI however. If it's not your problem, then follow on.
SP Flash - The famous SP Tool. SP Tool is a easy tool to use, may be confusing at first, but then first time a charm and you can get used to it, easily, or after some times. SP Tool is famous for recovering many MTK devices from hard bricks, and thats what we will use to recover your device.
OPEN SP FLASH UP​
Here you are, greeted by a nice interface. There's nothing, but I will explain you to it.
There's 3 blank spaces, called Download-agent (DA for short), Scatter-loading file & Authentication file.
DA is to have access to the devices internal storage to be able to do the flashing;
Scatter-loading shows you the mapping of the partitions it will flash on the MTK;
Authentication is just the MTK protection for newer mtk devices that you need to be able to flash (*its also used to successfully flash, but you still need to bypass it somehow, as you require a Mi Account able to do BROM flashing, see below as you follow the thread)
Now, fill the blanks up:
To find the DA, it is always in the MiFlashPro installation location, so ...\MiFlashPro\. Access that folder, open up "\SP_Flash_Tool_V5" folder, and you will find a file named "MTK_AllInOne_DA.bin", use it as the DA.
To find the authentication file, its located in the same path of the DA, so ...\MiFlashPro\SP_Flash_Tool_V5\, and you will find a file named "auth_sv5.auth", use it as the authentication file.
Finally, to find the scatter-loading file, it is in the ROM folder you extracted, so ...\camellian_xx_xxxx_images_VXX.X.X.X.xxxxx_XXXXXXXX.XXXX.XX_XX.X_xxxxxl\ (the X's represent your MIUI version you downloaded). The scatter-loading file is always located in the folder "images", so \camellian...\images\, and you will find a text file named "MT6833_Android_scatter.txt", use it as the scatter-loading file.
Done?
Don't flash it yet, as we need to fix a issue with "combo_partisize_check".
Open up the scatter-loading file with Notepad or any text editor, so the text file named "MT6833_Android_scatter.txt".
Now, use the locate function to locate the following:
combo_partsize_check: true
After finding the first one, replace the "true" to "false", and the following one, and so on, till every line of them is set to "false" and isn't able to locate any set as "true".
We are done and finished setting up SP Tool!​*Now, we need to bypass the Authentication of our device. Why? Just as the Snapdragon chips, Xiaomi has also implemented a security layer where you need to log in with a "Authorized Mi Flashing Account", which costs money (generally only on Snapdragon devices, I am not sure if we can find any paying service for it), which is really easy to bypass due to BROM.
Download the file "mtkauthbypass.zip" attached in the thread below.
Extract it, open it up, and it looks like this:
Now, press the "Disable Auth" button, you will have 60 seconds to get ready, get your hands on the phone and press at the same time the VOL+, VOL- & POWER button, till you see prompt appearing in the blank space. Should be similiar as this:
(thanks to chopwell20 for image)
After that, immediately open up SP Tool, and press "Download" as fast as possible.
Let it flash, from 5 to 15 minutes.
After it finishes, a blue window with a checkmark appears, disconnect your phone, and just press down the POWER button to boot it up.
And thats it! You have recovered your phone!​If you have any issues or it didn't work out, please reply so someone can help you out
(Simplified image to understand better without explanation)
ISSUES​CONNECTIONS ISSUE is completely normal!
It is when you try to connect your phone in BROM mode to your computer, but it always shows the error symbol over it.
From what it seems, this should be a issue from the phone and not your computer or the drivers itself
It doesn't mean that it makes you unable to unbrick it, but a lot of patience, as with this issue you will require to keep trying over and over again to bypass it.
So, if you can't bypass the Auth, this is probably it. Just keep trying and trying over again till you get it. There's (probably) no workaround rather than having patience to do it
(This also happens to me every time, so I consider it normal, and with some users such as bg0169 having this same issue, I just considered this was important to address it out, but if you think its not this issue, then reply, better safe than sorry)
I made this thread due to some users bricking their devices, and for every new user that hard-bricks their device to hopefully make this to help them

Amazing guide.
Thanks. and missing screenshot where Authbypass gives you prompt.

SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?

Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly

1lopes said:
yes, it is bypassable.
you just go to the mapping, and disable the checks on those partitions. it will still boot normally, afterwards, if you want (which is not necessary), you can reflash your phone via fastboot and miflash for those partitions to be flashed correctly
View attachment 5895435
Click to expand...
Click to collapse
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.

Reelin said:
Thanks for your reply.
Unfortunately, my phone won't boot when i exclude those images. No vibration, no black screen and no fastboot/recovery.
The another bypass method which requires using readback also doesn't work. I think it's probably because mt6833 is a newer chipset compared to the ones used in tutorials.
Any other advices please? I really don't want to pay money just to use MIUI again.
Click to expand...
Click to collapse
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool

1lopes said:
Could you give me more details about the another bypass? I dont understand what do you mean.
If that did not work, then I suppose your bootloader is locked
Please download the engineering ROM > https://mifirm.net/model/camellian.ttt#files;
and flash it via SP Tool like you did to MIUI, then boot to fastboot and flash an EEA image > https://mifirm.net/model/camellian.ttt#eea (if i am correct, EEA images are allowed to be flashed even with locked bootloader.)
If you do get the same verified boot error, disable those partitions to flash once again
If these methods didnt work, you need to install MTK Client to unlock your bootloader and try to reflash via fastboot or SP Tool
Click to expand...
Click to collapse
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?

Reelin said:
My father took my phone and paid to repair it. Well, i guess thats a way to fix things...
Anyway, the other method i was talking about was the one using PGPT image and using Hex editor blah blah blah.
By the way, now my phone works but it seems NVRAM was deleted. My IMEI doesn't show up. Can i recover it without using temporary methods?
Click to expand...
Click to collapse
I dont know how to recover IMEIs since I always back my NVRAM and write it via MTK Client.
You can try this guide:
Thread '[QUICK GUIDE][HOW TO] Unbrick Camellia/Camellian and restore IMEI' https://forum.xda-developers.com/t/quick-guide-how-to-unbrick-camellia-camellian-and-restore-imei.4502077/
Alternatively, which I am not sure, try looking up a IMEI writer program somewhere in the web for MTK

---------- full quote removed ----------
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking

TheZian said:
Bro i need help
I followed the process as is, everything went well, I marked the blue box with the checkmark, when I turned on my device it was still the same, what do you recommend I do?
sorry for my bad english, i am using a translator because i am spanish speaking
Click to expand...
Click to collapse
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?

1lopes said:
That is weird, are you able to boot into recovery or fastboot?
Did you get any verified boot error?
Did you use the right firmware? If so, what version (MIUI version (Indonesia/EEA/MI, etc.), Android version and Codename)? If you used the latest one (MIUI 14 Android 13) please try MIUI 13 Android 12 or lower
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Esto no debería pasar.
¿Eres capaz de reiniciar en fastboot o recovery?
¿Obtuviste algún error de arranque verificado (verified boot)?
usaste el firmware correcto? si si, cual version (version de la MIUI (Indonesia/EEA/MI...) version de la Android y codename)?
Click to expand...
Click to collapse
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.

TheZian said:
I use MIUI 12 global version, and can't access fastboot or recovery mode, it didn't give me any error either, and I think I use the correct firmware version.
Click to expand...
Click to collapse
Try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?

Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
I get the same error, anybody know how to fix?

And there is a "MediaTek Preloader USB VCOM" displayed in the Windows Device Manager.

Reelin said:
SP Flash Tool gives error on "gz.img, rescue.img and cust.img" because verified boot is enabled.
Is it possible to bypass it? or how do i disable verified boot without fastboot access? is my device completely dead?
Click to expand...
Click to collapse
I did have an issue but did not really go through all these stress...I also unbricked it using Brom and my original stock ROM files

Addendum_expired said:
I am unable to use MTK Auth Bypass Tool on my device. It shows an error message 'MTK Auth Disable (SLA/DAA) error!' Can you please help me?
Click to expand...
Click to collapse
Shilze said:
I get the same error, anybody know how to fix?
Click to expand...
Click to collapse
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451

1lopes said:
Please try this:
Post in thread '[SOLVED] RN10 5G Hard-bricked after installing GSI' https://forum.xda-developers.com/t/solved-rn10-5g-hard-bricked-after-installing-gsi.4563191/post-88302451
Click to expand...
Click to collapse
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.

Shilze said:
It doesn't work, I think the problem is that the boot mode is bootloader instead of bootrom.
Click to expand...
Click to collapse
if your phone is displaying the 3 boot modes in the edge, then yes you are in bootloader*
you should restart to any mode, then right as it reboots you shall boot into BROM immediately and redo the same process

I think that when I press the volume up (+), volume down (-), and power buttons on my phone simultaneously, it doesn't seem to recognize any device. However, when I only press the volume up (+) and volume down (-) buttons, it recognizes a MTK Preloader USB VCOM port, and during the process, it seems to attempt to connect twice when "Disable Auth" is enabled. In addition, the BootMode displays as BootLoader

Question Redmi Note 10 Pro stuck on recovery mode & ADB unable to recognise device after system wipe

I was able to install ADB and fastboot on my Redmi Note 10 Pro (sweet). After I flashed the recovery and factory reset the device, I am unable to run the adb command to flash the zip file to the device. adb is working perfectly fine on my windows machine, but is not able to recognise my device. I am confused about how I should proceed to install the Pixel Experience 13 Plus edition of the ROM, and how I can configure my phone so that my PC recognises it since I have already factory reset the device so cannot boot back into MIUI.
Any help would be really appreciated, since it is my first time installing a custom rom. Apologies if I missed something, or if my query is not well versed.

Do you have TWRP recovery installed?
If yes click on the following buttons and swipe:
{
"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"
}
Then type the following in the terminal of your PC during your phone is connected to your PC via USB cable:
adb sideload <path on your PC to ROM.zip>
And if you want to flash Magisk before booting click on the same buttons as shown above again and type:
adb sideload <path on your PC to Magisk.zip>
That's it.
Now your phone should boot the ROM (e. g. PixelExperience) you have flashed.

Since I was installing Pixel Experience Plus 13, and they have officially recommended their custom recovery, I was using the Pixel Experience Recovery instead of TWRP

erehymnt said:
Since I was installing Pixel Experience Plus 13, and they have officially recommended their custom recovery, I was using the Pixel Experience Recovery instead of TWRP
Click to expand...
Click to collapse
I have never used the Pixel Experience Recovery and do not know if that one has "ADB sideload" feature as TWRP has.
Well, Pixel Experience Recovery is not needed to flash Pixel Experience ROM.
With TWRP you can flash any ROM.
Therefore I recommend you to download TWRP ...
Xiaomi Redmi Note 10 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
... and install it by booting into fastboot mode (hold "volume down" button + Power button) and typing following command in the terminal:
fastboot flash recovery <path on your PC to TWRP.img>
Afterwards hold "volume up" button + power button until it boots into TWRP recovery and do what I wrote you above.

minax007 said:
Do you have TWRP recovery installed?
If yes click on the following buttons and swipe:
Then type the following in the terminal of your PC during your phone is connected to your PC via USB cable:
adb sideload <Link to ROM.zip>
And if you want to flash Magisk before booting click on the same buttons as shown above again and type:
adb sideload <Link to Magisk.zip>
That's it.
Now your phone should boot the ROM (e. g. PixelExperience) you have flashed.
Click to expand...
Click to collapse
Unfortunately, the problem I'm facing is that adb is not able to recognise my device, so any adb commands I'm entering on my terminal are not being executed since the device isn't connected. Any way to fix this in particular?

minax007 said:
I have never used the Pixel Experience Recovery and do not know if that one has "ADB sideload" feature as TWRP has.
Well, Pixel Experience Recovery is not needed to flash Pixel Experience ROM.
With TWRP you can flash any ROM.
Therefore I recommend you to download TWRP ...
Xiaomi Redmi Note 10 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
... and install it by booting into fastboot mode (hold "volume down" button + Power button) and typing following command in the terminal:
fastboot flash recovery <path on your PC to TWRP.img>
Afterwards hold "volume up" button + power button until it boots into TWRP recovery and do what I wrote you above.
Click to expand...
Click to collapse
Okay I will try using TWRP once, thank you!

erehymnt said:
Unfortunately, the problem I'm facing is that adb is not able to recognise my device, so any adb commands I'm entering on my terminal are not being executed since the device isn't connected. Any way to fix this in particular?
Click to expand...
Click to collapse
Did you already install TWRP?
Does fastboot work in fastboot mode?

erehymnt said:
Okay I will try using TWRP once, thank you!
Click to expand...
Click to collapse
You are welcome!
Just write me if you run into issues, so that I can help you.
And don't worry if I respond with a delay (it is prayer time right now).
I don't see a problem with your device ... I have had similar issues and could resolve all of these.

minax007 said:
You are welcome!
Just write me if you run into issues, so that I can help you.
And don't worry if I respond with a delay (it is prayer time right now).
I don't see a problem with your device ... I have had similar issues and could resolve all of these.
Click to expand...
Click to collapse
I installed TWRP, it said the ROM flash was successful, but when I reboot my device, it still boots back to TWRP (i.e, the system doesn't boot the PixelExperience ROM).
Fastboot works in fastboot mode, only adb is disfunctional.

@minax007 I ended up wiping the system again, and after rebooting it fixed my issue. I have booted into the custom ROM now, thank you for your help!

erehymnt said:
@minax007 I ended up wiping the system again, and after rebooting it fixed my issue. I have booted into the custom ROM now, thank you for your help!
Click to expand...
Click to collapse
Wiping system is with this phone never needed. Why you've tried this?

erehymnt said:
@minax007 I ended up wiping the system again, and after rebooting it fixed my issue. I have booted into the custom ROM now, thank you for your help!
Click to expand...
Click to collapse
You are welcome.
In case you experience a problem again just post your questions in this great forum.
I know XDA developers since my first smart mobile, which was an XDA.
And I have always found a solution to the problems which you run into by time

Laptapper said:
Wiping system is with this phone never needed. Why you've tried this?
Click to expand...
Click to collapse
I don't know what the issue was earlier, I had mistakenly flashed a boot image earlier using fastboot (which was completely unnecessary and just me desperately finding a solution), and the phone would always reboot into the custom recovery since then.
Anyway, it's solved now, I'm glad I could figure out a solution to this, was scared that I had bricked my device!

minax007 said:
You are welcome.
In case you experience a problem again just post your questions in this great forum.
I know XDA developers since my first smart mobile, which was an XDA.
And I have always found a solution to the problems which you run into by time
Click to expand...
Click to collapse
Makes sense, I'll learn the process with time. Just a bit intimidating the first time since it poses the risk of bricking the device or causing some unintended damage.

erehymnt said:
I was able to install ADB and fastboot on my Redmi Note 10 Pro (sweet). After I flashed the recovery and factory reset the device, I am unable to run the adb command to flash the zip file to the device. adb is working perfectly fine on my windows machine, but is not able to recognise my device. I am confused about how I should proceed to install the Pixel Experience 13 Plus edition of the ROM, and how I can configure my phone so that my PC recognises it since I have already factory reset the device so cannot boot back into MIUI.
Any help would be really appreciated, since it is my first time installing a custom rom. Apologies if I missed something, or if my query is not well versed.
Click to expand...
Click to collapse
Hi
Device USB controller stuck in EDB mode that's why charging & ADB are not available
Fix
Remove the back cover
Disconnect the battery ribbon cable
Reconnect the battery
Thanks

erehymnt said:
Makes sense, I'll learn the process with time. Just a bit intimidating the first time since it poses the risk of bricking the device or causing some unintended damage.
Click to expand...
Click to collapse
Don't worry ... the devices of today (at least since appr. 10 years) are almost unbrickable ... in case you install the recovery correctly and just flash zip files.
And in case you still mess up things this is the forum to ask for help

lepusang said:
Hi
Device USB controller stuck in EDB mode that's why charging & ADB are not available
Fix
Remove the back cover
Disconnect the battery ribbon cable
Reconnect the battery
Thanks
Click to expand...
Click to collapse
Thanks for sharing your thoughts.
But he did not state that charing is not availble.