Database Develop

Bricked Mi3 - Showing QHUSUB Bulk in PC

I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.

Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Don't worry have you backup you data?
if you have, just install the driver for qhusb
then your phone should be able to recognises by MIflash then flash any fastboot rom, You phone should be good to go.

I had a similar issue but i tried to hold the power button for like 30 seconds and the phone booted. If it didn't work, you should follow this thread: en.miui.com/forum.php?mod=viewthread&tid=73348&highlight=Mi3%2Bunbrick&mobile=no

partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone

murattiy said:
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
Click to expand...
Click to collapse
Did you personally tried that? Because flash all bat do uses fastboot to flash, which can't be accessed.
I wonder whether the other one u poster doesn't use fastboot, cant check the file content atm

I have tried many times
last times tried 3 hours ago, for alpha 5.12.24
my video under explain
http://m.youtube.com/watch?v=fSl9xrR_J4g

@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol

you need to do İnstall spacial flash_all.batt change to in flash_all.batt "cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global"
dont use miFlash .. enough u clik speical flash_all.batt

If your device not boot into fastboot/recovery mode press power button for around 30-40 seconds .

and still not boot into fastboot/recovery mode
battery cable exist than try.. i tried many times))

Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!

From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?

Prince Chandela said:
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!

coolkillermax said:
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Click to expand...
Click to collapse
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?

回复: Bricked Mi3 - Showing QHUSUB Bulk in PC
Prince Chandela said:
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
Click to expand...
Click to collapse
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4

coolkillermax said:
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
Click to expand...
Click to collapse
flash miui fastboot rom then

Prince Chandela said:
flash miui fastboot rom then
Click to expand...
Click to collapse
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking

coolkillermax said:
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
Click to expand...
Click to collapse
can you boot in recovery now?

Prince Chandela said:
can you boot in recovery now?
Click to expand...
Click to collapse
No...
http://forum.xda-developers.com/xiaomi-mi-3/help/mi3w-lost-partition-userdata-img-t3293583

Me_Ashish_ said:
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
Click to expand...
Click to collapse
Really need your help..
Can you explain it further?
please..

[URGENT HELP] Pure stock Redmi 4A bricked (No Usb debugging or anything enabled)

Hey Guys,
One of my younger brother some how managed to brick a stock 4A, and when starting it up, its stuck at the MI logo, however I am able to go in the Fastboot and stock recovery via the side volume and power buttons and the phone is charging while powered off.
I have tried factory resting via the stock recovery, but no use, still stuck at the logo.
Is there any app or software like odin (for Samsung), where I can flash a stock Rom in fastboot via my pc? If so can you please share the link to the thread or step by step instructions to do so?
i want to share again, its stock with no Xiaomi account or any USB debugging enabled from the developer options as it is pure stock. I have also attached the pictures of the phone with this message (I know it won't help, but just in case).
I want to thank every one for giving me their time in assisting me in resolving this issue.
Have a great day.

This guide might help you
http://www.99mediasector.com/flash-xiaomi-device-without-unlock-bootloader/
For procedure you can refer
Sorry not able to help u fully because of my time issues
According to me u can still flash miui ROM via fast boot (even when locked)
Use mi flash tool for that (link
https://xiaomiflashtool.com/ )
U need to only use fast boot roms to flash
Link http://en.miui.com/a-234.html <---- select redmi 4a global rom from it
See the YouTube vid for process

rseragon said:
This guide might help you
http://www.99mediasector.com/flash-xiaomi-device-without-unlock-bootloader/
For procedure you can refer
Sorry not able to help u fully because of my time issues
According to me u can still flash miui ROM via fast boot (even when locked)
Use mi flash tool for that (link
https://xiaomiflashtool.com/ )
U need to only use fast boot roms to flash
Link http://en.miui.com/a-234.html <---- select redmi 4a global rom from it
See the YouTube vid for process
Click to expand...
Click to collapse
Thank you bro, I tried, it, firstly it said Error: Flash Tz error" on flashing the rom via Mi flash. I did extracted it two times as stated and also tried extracting it once and I also tried placing the folder in C:/ drive (root), but the problem persists.
Also, I tried changing the drivers in device manager, but no use. I also downloaded ADB drivers, which gave me Xiaomi adb boot loader drivers but same issue.
Regarding the EDL, double clicking on edl.cmd, just reboots the phone to "MI" logo again and no black screens or red led light to show that its in the EDL mode, and I did tried flashing on the MI logo but the same results.
Please help.

Hassan Aftab said:
Thank you bro, I tried, it, firstly it said Error: Flash Tz error" on flashing the rom via Mi flash. I did extracted it two times as stated and also tried extracting it once and I also tried placing the folder in C:/ drive (root), but the problem persists.
Also, I tried changing the drivers in device manager, but no use. I also downloaded ADB drivers, which gave me Xiaomi adb boot loader drivers but same issue.
Regarding the EDL, double clicking on edl.cmd, just reboots the phone to "MI" logo again and no black screens or red led light to show that its in the EDL mode, and I did tried flashing on the MI logo but the same results.
Please help.
Click to expand...
Click to collapse
Wow wait were u trying edl or fastboot
The method I provided is for fastboot not for edl(though most of it same except u need to remove the back cover and do something)
If u think u can really do edl mode flashing the see this vid
Link :-
I think edl is the only method to fix this problem
I reccomend you to give ur phone to a shopkeeper to do it
If u think u can DL the thing that guy did in that vid u r free to go ahead

Xiaomi Mi 9 stuck in a bootloop, now with no OS. Help needed

Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.

Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.

divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.

crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?

mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.

I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.

mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode

How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )

No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!

Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk

sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom

Phone in Hard Brick mode

I was trying to install Arrow OS custom ROM to Motorola one power using TWRP. It got flashed, when I flashed the Gpps Rom with it, it didn't flashed and I rebooted the phone right there. The phone is now in a hard brick mode and is not responding to anything, is there anything I can do to fix it? Could you please guide me with the complete procedure?

You must use a blankflash to boot bootloader.BlankFlash available for
Moto One Power (Chef) https://mirrors.lolinet.com/firmware/moto/chef[/
.1 install Motorola drivers,2 install quallcom drivers for Motorola procesor(gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows) .3 use flashbat in blankflash directory,4 press volume down and power on phone.5 connect phone with pc and proces will be starting.if your phone starting in bootloader mode ,you can flash stock room

Thank you for your help and response. I followed the steps as you mentioned. On step 3 when I run the Flashbat file, It gives the below error, and the phone never started
[112.478] ReadFile() failed, GetLastError()=0
[125.434] ReadFile() failed, GetLastError()=0

when blankflash starting you can release the wolume and power.try differrent usb port in pc.I have the same problem with custom roms,You see port com in device manager on pc?

It worked, but how did you know all this? Just spot on :good:

I tried this method but not working on my phone, xt1942-1. This is the Chinese version p30 note I got from AliExpress. I see the device in device manager as port 9008
Any help would be appreciated!

Hi,you are try change a port USB in PC?this method works,my phone is the same like your,Moto p30 note from aliexpress

Thanks, I tried all usb ports on my pc but same problem. Should we press power and volume down buttons after connecting to pc? Please help I just got this phone today and bricked right away ...
Also there are two blankfash versions on the link you provided which one to use?

Hello again.you can reinstall drivers,change partition with blankflash folder.last time when I'm bricked my phone ( trying flash customrom )I waste half day to recover my moto.im change drivers,folders,USB port,try the same on laptop and nothing.But when I'm wakeup morning and try one more time it's works!I don't no why,maybe I'm stupid,but I think is a problem with drivers or something.You must try more and more,and do not give up!I'm use blankflash from Android 9

dadm said:
Hello again.you can reinstall drivers,change partition with blankflash folder.last time when I'm bricked my phone ( trying flash customrom )I waste half day to recover my moto.im change drivers,folders,USB port,try the same on laptop and nothing.But when I'm wakeup morning and try one more time it's works!I don't no why,maybe I'm stupid,but I think is a problem with drivers or something.You must try more and more,and do not give up!I'm use blankflash from Android 9
Click to expand...
Click to collapse
I tried again today and Voila its working! Blankflash literally tests your patience. Thanks @dadm for your suggestions and now I have a working moto one power as my daily driver!

htcmusic said:
I tried again today and Voila its working! Blankflash literally tests your patience. Thanks @dadm for your suggestions and now I have a working moto one power as my daily driver!
Click to expand...
Click to collapse
Hi @dadm I could not get my SIM card detected in RR rom and tried to flash stock again. Now I am in a bootloop whatever I do. Which stock did you use to revert back? And is your SIM card detected?

I have a few questions if anyone could answer. I am looking to get hands on this phone but making sure everything goes as I expect.
1.Does any member have knowledge which of this Device variants (XT1942-1, XT1942-2, XT-942-3) qualify for "Unlocking Boot-loader" and which variant does not support unlocking. I am lookig for 4/64gb Chef.
2. Is there Any Custom Pie Rom with Solid stability + Efficient & Effective Kernel?
3. Does stock Motorola Camera app works 100% in a custom flashed Rom as it does in Stock Rom or we have to use Google Pixel Camera apps as an alternative?
4. Is there anyway to get back to stock image from Custom rom.
5. How to recover the device from a Hard Brick.
6. Not but least. How well this device performs while playing PUBG.

Phone flashing locked and stuck at fastboot mode
I have done a stupid thing after flashing stock ROM I have flashed twrp and my stock ROM was stuck at loop after that I have locked the device and it showing it device is corrupted and will not boot
Could any body help me plss.??
I tried this blankflash.bat but it showing <waiting for device> my phn is already connected to pc

Ravi2730 said:
I have done a stupid thing after flashing stock ROM I have flashed twrp and my stock ROM was stuck at loop after that I have locked the device and it showing it device is corrupted and will not boot
Could any body help me plss.??
I tried this blankflash.bat but it showing <waiting for device> my phn is already connected to pc
Click to expand...
Click to collapse
Phone must be in EDM to flash blankflash
Sent from my ali using XDA Labs

Thanks for reply
sd_shadow said:
Phone must be in EDM to flash blankflash
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Actually how to enter EDM mode could you pls explain in steps my phone just start into fastboot,no recovery, no boot. Pls help me bro.

Problem solved
Ravi2730 said:
Actually how to enter EDM mode could you pls explain in steps my phone just start into fastboot,no recovery, no boot. Pls help me bro.
Click to expand...
Click to collapse
Anyone stuck in fastboot when it shows your phone is corrupt and will not boot just flash the command
fastboot boot boot.img file in stock room phn will automatically start everything working it work as a flash...?

Redmi Note 9 merlin 4/128 NFC - Hard Brick

A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?

Already tried power and minus option.when you connect to a desktop what does it say ?

Dokrak99 said:
Already tried power and minus option.when you connect to a desktop what does it say ?
Click to expand...
Click to collapse
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.

That's bad.
Hold the power +/- longer then 15 seconds try both.
Second
Charge for about 10 minutes and try the same again.
Last drain it when down keep pushing the power button to flat it.hook it up on desktop and install miflashtools.or try power +/- again

Dokrak99 said:
Hold the power +/- longer then 15 seconds try both.
Click to expand...
Click to collapse
Same as:
LordRedstone05 said:
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
Click to expand...
Click to collapse
Dokrak99 said:
Charge for about 10 minutes and try the same again.
Click to expand...
Click to collapse
When I try to charge it it goes in the bootloop again until I disconnect it and the battery runs out.
Dokrak99 said:
Last drain it when down keep pushing the power button to flat it.
Click to expand...
Click to collapse
It goes on, shows this battery icon, that it's empty and goes off. This repeats until I release the button.
Dokrak99 said:
hook it up on desktop and install miflashtools.or try power +/- again
Click to expand...
Click to collapse
The miflashtool does nothing when I click on Flash with the images and scripts loaded. Power +/- does the same as before.

Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot

Dokrak99 said:
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Click to expand...
Click to collapse
Thanks in advance

What should I do in this tool? The tool doesn't recognize my phone. It brings nothing since I cannot access Fastboot.

Well basically there is only one real option left . contact mi service center because mi don't support or they closed there download,edl support on there phones to prevent rom swapping .there is a edl cable with mtk support around but that's a long shot.because I never had a messed up phone like this.at least not one with mtk.without recognise you're desktop I don't see a fix in this to get in fastboot or flash it.

Download platform tools drop it on c:/ so c:/platform tools .install abd drivers package if you didn't have it.go in platform tools the top line and tick Cmd hit enter.try command : fastboot devices .try a few times if a number pops up you can try .fastboot reboot fastboot

LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
TWRP bricked my redmi Note 9 too, but i had ADB Connection in the black Screen so i rebooted to Fastboot over ADB and reflashed the Stock rom

LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
Did you find solution on this? Please answer bro i need your help

Jayson Galang said:
Did you find solution on this? Please answer bro i need your help
Click to expand...
Click to collapse
Unfortunately i haven't found a solution. I had to send it to a service center 2 Days ago. Sorry, that i couldn't help.

the right driver is mtk this is not adb nothing happens the this you could fixs is
go to the nearest techniciann beacause they need special tools to fix properly

Is your phone still bricked, If yes, I can provide link for the factory firmware recently released for Merlin, You could give flashing that in SP Flash a try, does not need auth account.

If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

Communos said:
Is your phone still bricked, If yes, I can provide link for the factory firmware recently leaked for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
Click to expand...
Click to collapse
yow is that legit? Had my redmi note 9 bricked for a week now.

CruisaderX said:
yow is that legit? Had my redmi note 9 bricked for a week now.
Click to expand...
Click to collapse
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If it keeps restarting, you've made any wrong modification. You need to follow your steps back and try to unmake your modification.
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
If you are using V12.0.5.0 or higher, TWRP will not work.
If you want to use sp flash tool, you need to flash the stock rom preloader using V12.0.4.0 (or lower). (It will works perfectly with lower preloader binary version).
With an older preloader version, your phone will can receive DA files and accept flashing with NO auth.
Everything you need to do is plug your phone in usb (without press any key, if you press any key it will enter in EDL mode and requests authenticaion).
Here, are PRELOADER binaries for flashing: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221081/
Here, are DA files for flashing using flash tool: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209767/
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/

VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
[/QUOTE
Click to expand...
Click to collapse
I tried actually before after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting), I will call this state 1 brick. In state 1 brick you can still access fastboot mode normally. Then i tried to flash twrp hoping to just flash a rom to fix it leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot bootloader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi devices. Now I am stucked with a hard bricked note 9 with no way of fixing.

CruisaderX said:
i tried before actually after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting, I will call this state 1 brick. In state 1 brick you can still access fastboot mode. Then i tried to flash twrp hoping to just flash a rom leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot boot loader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi device. Now I am stucked with a hard bricked note 9 with no way of fixing.
Click to expand...
Click to collapse
You need to read every line and every word careful and follow only specific guide for your specific problem.
If you try to do anything you see, obviously you will cause more damages to your device.
Please, read my post again: https://forum.xda-developers.com/t/redmi-note-9-merlin-4-128-nfc-hard-brick.4201717/post-84379823
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/