Database Info

[Successful] [UNBRICK] Redmi Note 5/Pro Bypass EDL Authorization

In this video I'll guide you to Unbrick Redmi Note 5/Pro without replacing Motherboard, for fastboot flash Xiaomi has introduced the security feature known as EDL Authorization, without Authorized ID you can't flash and unbrick you Redmi Note 5, here I'm representing the FASTBOOT ROM for Redmi Note 5 (Whyred) which'll bypass the MI EDL Authorization, yes there is no need of MI ID Authorization and also you don't have to try test point method.​
Links:
https://drive.google.com/drive/folders/16lQ-A175D_5DJU-YT4lbul5htgaNNw21
Procedure:
Just flash the Extracted ROM using "may 2018 miflash tool" (Unzip the files selected the folder where rom is extracted choose option of clean all and click on flash.​

Fixed url:
https://m.youtube.com/watch?v=Pf_pPCGkldI

Enough with same threads.. There are numerous guides already about same thing, we dont need a new one everyday.

Incogn said:
Enough with same threads.. There are numerous guides already about same thing, we dont need a new one everyday.
Click to expand...
Click to collapse
Well I'm aware of that, and this video is a prove it self

rashidmalyk said:
Well I'm aware of that, and this video is a prove it self
Click to expand...
Click to collapse
Sorry you dont make sense or i just cant understand you.. We dont need proof, its been reported as working, in atleast 4 different threads. Its not some kind of new magic method, its the same guide everybody is talking for a week already.

Incogn said:
Sorry you dont make sense ir i just cant understand you.. We dont need proof, its been reported as working, in atleast 4 different threads. Its not some kind of new magic method, its the same guide everybody is talking for a week already.
Click to expand...
Click to collapse
:silly: these guys are just here for karma and nothing new to add.

Incogn said:
Sorry you dont make sense or i just cant understand you.. We dont need proof, its been reported as working, in atleast 4 different threads. Its not some kind of new magic method, its the same guide everybody is talking for a week already.
Click to expand...
Click to collapse
I'll appreciate you if there is a single thread posted by you (of 4 threads). After getting the device hard bricked, why you people try test point method when the phone was already tucked in EDL Mode, there are many miserable users whom ruin there devices due to bloody incomplete and so-called magical guides by the developers kind of you.

deathbearer said:
:silly: these guys are just here for karma and nothing new to add.
Click to expand...
Click to collapse
Its much better than begging authorization from Russians, and soon there will be new things from me!

rashidmalyk said:
I'll appreciate you if there is a single thread posted by you (of 4 threads). After getting the device hard bricked, why you people try test point method when the phone was already tucked in EDL Mode, there are many miserable users whom ruin there devices due to bloody incomplete and so-called magical guides by the developers kind of you.
Click to expand...
Click to collapse
Lmao, im not looking for appreciation from you, where did you get this crazy idea.. All im saying is, THIS GUIDE BEEN ON FORUM FOR WEEKS, ITS ALREADY 4TH THREAD SHOWING SAME THING. This is not your work, nor is it some new method. Its the same method thats been posted on this forum before. Stop creating same threads over and over again. And what is even worse, is i dont see a single credit to anyone, even tho files and guide was taken from other people and miui forum. So shame on you.

rashidmalyk said:
Its much better than begging authorization from Russians, and soon there will be new things from me!
Click to expand...
Click to collapse
Without contributing anything new thats a tall claim to make. You would be begging too. If new way of unbrick information was not found.
First do something on your own rather than stealing someone else's work.

How to do it on my Xiaomi Mi8? Where can I get a compatible modded ROM?

I am getting the following message "write time out, maybe the device was disconnected"

Incogn said:
Lmao, im not looking for appreciation from you, where did you get this crazy idea.. All im saying is, THIS GUIDE BEEN ON FORUM FOR WEEKS, ITS ALREADY 4TH THREAD SHOWING SAME THING. This is not your work, nor is it some new method. Its the same method thats been posted on this forum before. Stop creating same threads over and over again. And what is even worse, is i dont see a single credit to anyone, even tho files and guide was taken from other people and miui forum. So shame on you.
Click to expand...
Click to collapse
Can you please show other thread that exist before for this same procedure because have searched and see non

VeerAmrit said:
I am getting the following message "write time out, maybe the device was disconnected"
Click to expand...
Click to collapse
Did you watch my other guide?

klingkling said:
Can you please show other thread that exist before for this same procedure because have searched and see non
Click to expand...
Click to collapse
True this has been re-posted a lot of times. I first posted it here with all the proper credits but mine was reported so I asked the mod to take it down permanently. After a few days I made a thread again because of a lot of pm's. Here it is::
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780

Need Help
Can you help me with bypass authorization on Redmi 3s Prime. is there any option for it, cant even install TWRP recovery without binding the phone. Any help will be appreciated.

Can i flash any of these roms on my fake rom note 5 with locked bl? and which one?

I have a MiPad4 which I can only get fastboot
I have tried to flash with the latest MiFlash and the 28 may 2018 Miflash
Miflash can see the device - it goes through the flash and everything seems to be doing fine until after 30 seconds it says
error:FAILED ( remote: Flashing is not allowed in Lock State )
I had this device unlocked before , but when I flashed TWRP originally I left the default selection of clean all and lock on MiFlash ( sad default )
any ideas ?

baldrick_turnip said:
I have a MiPad4 which I can only get fastboot
I have tried to flash with the latest MiFlash and the 28 may 2018 Miflash
Miflash can see the device - it goes through the flash and everything seems to be doing fine until after 30 seconds it says
error:FAILED ( remote: Flashing is not allowed in Lock State )
I had this device unlocked before , but when I flashed TWRP originally I left the default selection of clean all and lock on MiFlash ( sad default )
any ideas ?
Click to expand...
Click to collapse
You answered yourself. You left default selection "clean all and lock". It locked your bootloader again, because thats what you chose to do.

Further Updates??
Bro i just did as u shown in vid and with ur help i just unbricked my dead.
But now I want to ask u something will i get updates now or how can i Flash TWRP Or any other Recovery??

HELP, BRICKED! MSMTOOL does not solve

Hello friends, I need help!
My phone is totally bricked! No function exists anymore (no fastboot, no recovery) just QDloader, but here my headache begins:
Following https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109/ I downloaded all available versions, nothing worked, "Sha256 DOES NOT MATCH" found out I bought Chinese version of OP6, it is very rare to find MSMTOOL version for Chinese, and the only one I found didn't work "SHA256 DOES NOT MATCH"
I do not know what else to do ! I need your genius!
* Already tried to uncheck "SHA256 CHECK", and it works, the whole system is transferred to the phone but when it ends simply nothing happens, continues bricked
**all info: ONEPLUS A6000 - 6/64GB - B182-181006 (Need some more info?)
*** I found that it is Chinese due to the red "band" that comes with the box / charger. photo:
https://i.imgur.com/gfL9v8S.jpg sorry for link, using image tool i have bug

Here is the link to the latest hydrogen os for the op6,
http://download.h2os.com/OnePlus6/MP/OnePlus6Hydrogen_22_OTA_034_all_1909041314_0edfbb2dfaa34e94.zip
Got it from the official website (https://www.oneplus.com/cn/support/softwareupgrade/details?code=PM1574150497163)
Reading through other posts, people just flashed oxygen using the local upgrade option and it worked. Ofcourse the hardware differences between the model's cannot be overcome.
Try flashing hydrogen first, then use the local upgrade to move up to oos and see if that works.

cbarai said:
Here is the link to the latest hydrogen os for the op6,
http://download.h2os.com/OnePlus6/MP/OnePlus6Hydrogen_22_OTA_034_all_1909041314_0edfbb2dfaa34e94.zip
Got it from the official website (https://www.oneplus.com/cn/support/softwareupgrade/details?code=PM1574150497163)
Reading through other posts, people just flashed oxygen using the local upgrade option and it worked. Ofcourse the hardware differences between the model's cannot be overcome.
Try flashing hydrogen first, then use the local upgrade to move up to oos and see if that works.
Click to expand...
Click to collapse
Thanks for trying to help friend. Like I said, the device is without recovery, outside of QDLoader, nothing works

Perhaps you should give this thread a look. It saved my behind several times.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665

caitsith810 said:
Perhaps you should give this thread a look. It saved my behind several times.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Fastboot bricked man??

Try this and follow exactly! https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

@ brunoerthal1
Im wondering, u said ur OP6 can acutally get into EDL mode. but cannot flash using MSMtool right?!
this case is pretty same as my friend OP2...what is your perivous state before u do brick your OP6?
the OP2 from my friend have EXACT same situation! cannot pass the SHA256...MAYBE the internal SD is damage, hardware related!!!
Suggest u give it to chinese guy and send to china and fix...!

Your OP6 is international version, use this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892

Delete

??

Can anyone confirm this working before I go ruin my phone haha

Clank50AE said:
Can anyone confirm this working before I go ruin my phone haha
Click to expand...
Click to collapse
You won't. Enjoy the better software!

suzook said:
You won't. Enjoy the better software!
Click to expand...
Click to collapse
Thank you for the Swift reply! My RM3 is glitchy as albeit and I'd like more stability. I know it's just the OS but it's very annoying.

Looks great. There's a big red warning to your thread tho that don't use if you're phone is Red Magic 3 it will damage the motherboard. Hmm

Any one besides OP tried this ?

leipnacht said:
Looks great. There's a big red warning to your thread tho that don't use if you're phone is Red Magic 3 it will damage the motherboard. Hmm
Click to expand...
Click to collapse
Everything is the same, other than the CPU. Nothing will happen. If people want to stick with the buggy rm3 sw, than go ahead. Not sure why you would want to.

so if rm3s fw works with rm3, can we try to install it thro twrp???

hagouba said:
so if rm3s fw works with rm3, can we try to install it thro twrp???
Click to expand...
Click to collapse
TWRP states ERROR 7 when i tried this
LE: Avoid using this so called GUIDE, this is a bad joke... I tried using the Tool on RM3 and the cmd remains stuck with at Downloading firehouse program... then after some time "Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit:
I also swapped USB's, different cable and so on... COM 5 6 and 7 were used

@JerryYin I completely understand now why you were not sharing the tool ???

hagouba said:
so if rm3s fw works with rm3, can we try to install it thro twrp???
Click to expand...
Click to collapse
Absolutely not. Different sized partitions. You need to use the tool 1st.

Alex4455 said:
TWRP states ERROR 7 when i tried this
LE: Avoid using this so called GUIDE, this is a bad joke... I tried using the Tool on RM3 and the cmd remains stuck with at Downloading firehouse program... then after some time "Error]: Download programer FAIL.Please check phone status and reset into edl mode and try again.
Software download FAIL.Press any key exit:
I also swapped USB's, different cable and so on... COM 5 6 and 7 were used
Click to expand...
Click to collapse
Bad joke? Maybe you dont know what you are doing.
I did 3 phones. No issues. Its on your end.

suzook said:
Bad joke? Maybe you dont know what you are doing.
I did 3 phones. No issues. Its on your end.
Click to expand...
Click to collapse
You don't realize this is not a GUIDE, this is a statement and you are telling us to use the tool for something.... You did not provide steps, video, guide, pre-requirements, nothing
This is not my 1st time using this tool so i know how it works, i kept crashing my CN <-> EU roms and needed to use the tool
So, why don't you provide with these 3 x RM3's a video on how did you use the tool, on what hardware did you use it (PC hardware, maybe Ryzen is overkill for the app and does not know how to use the scripts), what drivers you have installed (because this tool does not provide drivers vs the RM3 tool that provides) and all that kind of stuff ?

Alex4455 said:
You don't realize this is not a GUIDE, this is a statement and you are telling us to use the tool for something.... You did not provide steps, video, guide, pre-requirements, nothing
This is not my 1st time using this tool so i know how it works, i kept crashing my CN <-> EU roms and needed to use the tool
So, why don't you provide with these 3 x RM3's a video on how did you use the tool, on what hardware did you use it (PC hardware, maybe Ryzen is overkill for the app and does not know how to use the scripts), what drivers you have installed (because this tool does not provide drivers vs the RM3 tool that provides) and all that kind of stuff ?
Click to expand...
Click to collapse
I'll delete the thread. I was trying to do people a favor. Didn't realize I needed to hold people's hands.

suzook said:
I'll delete the thread. I was trying to do people a favor. Didn't realize I needed to hold people's hands.
Click to expand...
Click to collapse
You shouldn't listen to aggressive people, they're the minority, thanks for whatever you were trying to do. I would like to give it a read if you still have the guide saved

If you speak the truth then please provide us with a picture or anything. First I don't know if rm3s fw is more stable than rm3 but if it is, I would definitely come back to stock rom as I missed the fan and triggers very much.

Sangyedorje said:
You shouldn't listen to aggressive people, they're the minority, thanks for whatever you were trying to do. I would like to give it a read if you still have the guide saved
Click to expand...
Click to collapse
Aggressive people ? Guide ?
The Guide was like this:
Use this tool from this thread (https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207) and enjoy the much more stable firmware of the RM3S "END"
And like i said in my previous posts, i asked him for a detailed explanation because what he said does not work, it always ends up with sahara_rx_data:237, i even tried on my laptop with with windows 7 fresh install
Then he suddenly reacts like a 12 years old and deletes everything

Alex4455 said:
Aggressive people ? Guide ?
The Guide was like this:
Use this tool from this thread (https://forum.xda-developers.com/red-magic-3/how-to/tool-nubia-red-magic-3s-unbirck-tool-t4025207) and enjoy the much more stable firmware of the RM3S "END"
And like i said in my previous posts, i asked him for a detailed explanation because what he said does not work, it always ends up with sahara_rx_data:237, i even tried on my laptop with with windows 7 fresh install
Then he suddenly reacts like a 12 years old and deletes everything
Click to expand...
Click to collapse
Well, you said his post was a bad joke that comes off as aggressive, even if the guide is dangerously unexplained he didn't wrote it with malicious intent so you shouldn't talk to a fellow forum member that way.
I think he is onto something, it seems reasonable that if RM3 and RM3S share so much hardware in common their firmwares won't differ that much either.

Sangyedorje said:
Well, you said his post was a bad joke that comes off as aggressive, even if the guide is dangerously unexplained he didn't wrote it with malicious intent so you shouldn't talk to a fellow forum member that way.
I think he is onto something, it seems reasonable that if RM3 and RM3S share so much hardware in common their firmwares won't differ that much either.
Click to expand...
Click to collapse
Bad Joke of a guide is considered aggressive these days ? Whoaw, the newer generation is way over sensitive
Besides the so called guide, i lost almost 4-5 hours investigating this so called guide with error fixing and so on, here is what worked for me
The below "what worked for me steps" resulted and complete WIPE of the device !
I have no responsibility over bricked devices, i simply shared what some one did not bother to "info"
Do this on your own RISK !
What worked for me as on flashing the RM3s firmware on my RM3 is that 1st of all you need Windows 8.1, i tried on different hardware AMD and Intel with the Unbrick Tool RM3S and does not work on Windows 10 no matter what (windows 7 did not worked on Ryzen and my Laptop)
1. Have Windows 8.1 X64 (i used my Intel Celeron Laptop)
2. Have the drivers for the QDLoader HS-USB Driver_64bit_Setup
3. Download the tool for the Unbrick RM3S
4. Install the QDLoader drivers on the newly installed windows 8.1 and choose to restart
5. Turn the phone off and leave it like that until the Unbrick tool is ready
6. Run the Tool's exe and let it extract (the RM3S Unbrick Tool)
7. Power on the Phone holding PWR and Vol Down
8. Connect to a USB 2.0 port directly in to the motherboard with a quality cable
9. Select EDL mode from the Bootloader menu of the phone
10. Search within Device manager the phone's COM port
11. When the tool is ready, input the COM Number and select continue and install
These steps worked for me and phone booted fine... Conclusion is: I went Back to CN V2.38 and restored backup via TWRP, no performance gain, the device is still seen as RM3 but running with RM3S firmware
GPU and CPU frequency is of a normal SD855
My personal opinion is: This is a waste of time after all the hype I've gotten in to believing it would run like a SD855+

Alex4455 said:
Bad Joke of a guide is considered aggressive these days ? Whoaw, the newer generation is way over sensitive
Besides the so called guide, i lost almost 4-5 hours investigating this so called guide with error fixing and so on, here is what worked for me
The below "what worked for me steps" resulted and complete WIPE of the device !
I have no responsibility over bricked devices, i simply shared what some one did not bother to "info"
Do this on your own RISK !
What worked for me as on flashing the RM3s firmware on my RM3 is that 1st of all you need Windows 8.1, i tried on different hardware AMD and Intel with the Unbrick Tool RM3S and does not work on Windows 10 no matter what (windows 7 did not worked on Ryzen and my Laptop)
1. Have Windows 8.1 X64 (i used my Intel Celeron Laptop)
2. Have the drivers for the QDLoader HS-USB Driver_64bit_Setup
3. Download the tool for the Unbrick RM3S
4. Install the QDLoader drivers on the newly installed windows 8.1 and choose to restart
5. Turn the phone off and leave it like that until the Unbrick tool is ready
6. Run the Tool's exe and let it extract (the RM3S Unbrick Tool)
7. Power on the Phone holding PWR and Vol Down
8. Connect to a USB 2.0 port directly in to the motherboard with a quality cable
9. Select EDL mode from the Bootloader menu of the phone
10. Search within Device manager the phone's COM port
11. When the tool is ready, input the COM Number and select continue and install
These steps worked for me and phone booted fine... Conclusion is: I went Back to CN V2.38 and restored backup via TWRP, no performance gain, the device is still seen as RM3 but running with RM3S firmware
GPU and CPU frequency is of a normal SD855
My personal opinion is: This is a waste of time after all the hype I've gotten in to believing it would run like a SD855+
Click to expand...
Click to collapse
Can you tell if it far more stable and less bug than our rm3 fw? As for the performance it depend on device prosessor.

[HELP] Redmi 9 Hard Bricked

Hello i've flashed a custom ROM for my Redmi 9 this morning but it failed.
Now my phone doing a big f* bootloop, the recovery (TWRP) is dead and the fastboot too.
I've found a tool named SP Tool to repair the phone but the problem is when i plug my phone to my computer the phone is charging (logic) and instead showing the animation of the battery it bootloop until it runs out of battery.
So someone can help me please
Thanks
Edit: Oh i forgot, now i've realised than when i flashed the rom i've wiped the entire phone (internal storage too)
My bad...

Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.

Hi, my phone has the codename Lancelot with a MTK Helio G80.
I will try, thanks

XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore

LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
Both SIM slots have no IMEI? I assume you wiped all and didn't backup?
You'll need Modem Meta and ENG ROM to fix that, you can get the ROM and the specific way to fix it from here.
If you're lost you'll find all the answers in the thread, but don't be afraid to ask there just don't ask an already asked question.
Here is a brief guide made by the same person to provide the ROM.
Goodluck.

LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
hey can i contract to you? i have a same problem too need some help
thank.

LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
can i contract to you? i have a same problem too need help

XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
I followed the guide in the video. But failing in the LibUSB Step. Mediathek device is not showing up. My Redmi 9 is hard bricked, just seeing a "redmi logo" bootloop. No matter if I try to boot normally, recovery or fastboot. Any Idea?

Kisle said:
I followed the guide in the video. But failing in the LibUSB Step. Mediathek device is not showing up. My Redmi 9 is hard bricked, just seeing a "redmi logo" bootloop. No matter if I try to boot normally, recovery or fastboot. Any Idea?
Click to expand...
Click to collapse
This tool installs the driver required to unbrick your device, if you can find your device specific driver to install on your PC then you can skip using this tool and install the driver manually.
If you can't find the driver, then try using a different cable when connecting the phone to the PC. Or a different port in the PC (Like the legacy 2.0 USB port in the motherboard).
The tool should first detect any device connected to install the driver it doesn't work the other way. If it still doesn't work then your only option is to find the driver manually. Or maybe you can find an updated version of the same tool or a similar tool.

XDHx86 said:
This tool installs the driver required to unbrick your device, if you can find your device specific driver to install on your PC then you can skip using this tool and install the driver manually.
If you can't find the driver, then try using a different cable when connecting the phone to the PC. Or a different port in the PC (Like the legacy 2.0 USB port in the motherboard).
The tool should first detect any device connected to install the driver it doesn't work the other way. If it still doesn't work then your only option is to find the driver manually. Or maybe you can find an updated version of the same tool or a similar tool.
Click to expand...
Click to collapse
Thanks for your help. Actually I got it working with a lot of try and error... not even sure which drivers worked at the end. Also I had to switch to a win 7 computer. On win 11 drivers just didnt work. But with MTK Bypass tool + SP flash Tool, I was able to flash the stock image and recover my briked phone!

Kisle said:
Thanks for your help. Actually I got it working with a lot of try and error... not even sure which drivers worked at the end. Also I had to switch to a win 7 computer. On win 11 drivers just didnt work. But with MTK Bypass tool + SP flash Tool, I was able to flash the stock image and recover my briked phone!
Click to expand...
Click to collapse
Glad it worked out in the end mate.
Might be a random guess but it could be because signature protection was enabled on the win 11 PC.
Don't brick your phone again!

LeCaptain said:
It worked! Thanks
But now i've got a little problem..
The phone don't have a IMEI anymore
Click to expand...
Click to collapse
Hi can I contact you I also have the same problem and it's my only mobile thank you

DISC0DEVIL said:
Hi can I contact you I also have the same problem and it's my only mobile thank you
Click to expand...
Click to collapse
Hey, i can help you by sending videos that helped me to fix my problem but i've lost them.
Do you have a bootloader locked or unlocked? (here to know how)
If it's the 1st option, relax, you can modify easily
If it's the 2nd a little bit less
NB: i don't use really use this phone, just for developpment and some things than it can break the OS because it had some problems with apps and updates.
Have a great day and i hope than you have found a solution before my answer.

XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
I just made an account to tell all of you amazing people in this forum how much i truly appreciate your support:
YOU ALL ARE AWESOME!!!! I was legit going to loose my job if i didn't unbrick this darn Redmi 9 coz it's my boss's daughter's device
e putting the blame on me being the spoiled lil brat she is :/ so it was either this phone gets working or i get thrown onto the streets.
I soared through so many websites and articles that i had almost given up XD... until i landed here.
I love ya'll! keep up the good work!

LeCaptain said:
Hello i've flashed a custom ROM for my Redmi 9 this morning but it failed.
Now my phone doing a big f* bootloop, the recovery (TWRP) is dead and the fastboot too.
I've found a tool named SP Tool to repair the phone but the problem is when i plug my phone to my computer the phone is charging (logic) and instead showing the animation of the battery it bootloop until it runs out of battery.
So someone can help me please
Thanks
Edit: Oh i forgot, now i've realised than when i flashed the rom i've wiped the entire phone (internal storage too)
My bad...
Click to expand...
Click to collapse
please tell me you didnt reflash preloader

XDHx86 said:
Is your device Merlin or Lancelot? If you're not sure, what processor do you have, Qualcomm or MTK?
If it is Qualcomm, try test-point method to access EDL mode, then use Mi Flash Tool to flash MIUI on your device. Read this FAQ to learn more.
If it is MTK, then follow this guide and download the tools used in the video from here. You can find your device ROM (Lancelot) here.
Just make sure you're flashing global version if your device is global or chinese if your device is chinese.
If you're not sure what you're doing, I highly recommend sending it to a professional.
Goodluck.
Click to expand...
Click to collapse
Bro in my device when i Connect my mobile.. libusb not recognized my phone.. What should i do

optsiam said:
Bro in my device when i Connect my mobile.. libusb not recognized my phone.. What should i do
Click to expand...
Click to collapse
Is it in EDL mode?

No but I am gonna try it Tomorrow

Someone help me please? Two days ago i bricked my redmi 9 eea after update via ota. He just died, no infinite loop or charge. After a tutorial from here was able to revive him with sp flash, phyton and other stuffs. Everyting went OK and my phone is alive again. Whatever now I've getting issues that weren't there before hard brick. My redmi doesnt recognize my Sim card. I enter my pin security and then don't get any sim card signal. Also can't log on play store with my Google account, i get this message "there was a problem communicating with Google servers, try again later." Tried to wipe Google play services data, also from play store, formated redmi from recovery but the problems remains. Maybe i need to reinstall rom again, im pretty sure it was the right rom i flashed because i download it from miui official website. Unfortunately after reviving my redmi with sp flash, my bootloader got locked again. Sense i cant log with Google account because phone doesn't recognize my chip to activate data sim card, i cant either unlock with mi unlock. Is there any solution for this? Thanks.
Perhaps flashing phone with another rom the problem gets fixed. I can still flash my phone with sp flash even with bootloader blocked right? My redmi comes with a European rom. To revive him i used rom last update, maybe should try a previous version?

LeCaptain said:
It worked! Thanks
Click to expand...
Click to collapse
Are all the steps performed with the phone turned off and connected to the computer?

Question Your device is corrupt. Oneplus 9

I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9

Flash by edl if you can't do it then pm I'll fix it by tv

Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck

applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day

SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above

rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.

I had this problem because I flashed a custom kernel on a custom rom today

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.