Database Info

HELP! Recovering my bricked Mi4

Since Xiaomi and Micro$oft released a public ROM of Windows 10 Mobile for Mi4, the curiosity drives me to try it. But I felt so uncomfortable after successfully installed win10 on my mi4.
So I decided go back to Android roms. But sh*t happened - my mi4 got bricked during the flashing.
Phone won't boot with black screen and no boot options. Holding any buttons (including power button + volume down more than 2 minutes) won't work.
The pc can not recognize a USB device after it is plugged in (in both Windows XP and Windows 8.1).
Then I plug it into my Mac OS X with a VirtualBox of Windows 7 OS inside.
The USB devices shows a unknown device of id 05C6:F006.
I did a lot of googling of 05c6:f006 which seems to be 05c6:9008 and something Qualcomm related.
And the most important thing is to make my computer to recognize it.
So things I need to figure out:
Is my phone hardware damaged or software damaged (hard bricked or soft bricked)?
Do I need to disassemble it?
How can I make my pc to recognize it ?

Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue

darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
My phone was recognized as a USB input device, VID_05C6&PID_F006, seems to be Qualcomm_QHSUSB 9008 related

I have exacly the same probleme here, do you have find any solution ?

If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works

xiaomi mi4 lte not turn on
darkmaster566 said:
If it's getting recognised, we can try flashing another recovery or directly boot into recovery from command prompt by using command fastboot boot recovery.img
Try this and let me know if it works
Click to expand...
Click to collapse
Good evening. I have a problem with my Xiaomi 4 lte, after trying to return from 6 to android 4.4 android after this tutorial : ]Now the phone does not start, if you stick to connect to PC loaded or red LED flashes once and the computer sounds like something I plugged in but not afiseaja nimicc device. He is charged for 24 hours and not start and MIFLASH program is not found

Mi4w hard brick
darkmaster566 said:
Please add screenshot of your phone state. Maybe we can determine if its a hardware or software issue
Click to expand...
Click to collapse
Hey! I had bymistakely flashed wrong partition and tried flash in miii 6.3.3 ROM....
Now my device is bricked....Whenever i connect to charger the red light blinks....And when connected to pc....The red light comes.....But no drivers come on my pc...Means its to recognising.....Can you help me please????

Partially bricked Mi4c mi-globe 7.2.9

Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant

have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom

Fastboot don't work,as PC don't see the phone?

DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.

Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?

DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck

Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?

DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.

OnePlus 7 Pro not detected by PC at all (only in EDL/MSM mode)

Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez

This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse

Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.

MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.

amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck

Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.

Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.

It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.

Xiaomi Redmi 9A totally dead after PS Flash Tool

Hello there,
first of all excuse me if its wrong section to post such things.
My Redmi 9A won't turn on after i've flash it using PS Flash Tool , i've tried to charge it, button combinations and other things...
whenever i am connecting 9A to my PC it says "unrecognised USB device" and i am completely out of clue what can i do to bring it back to life.
any help will be appreciated

Got the same problem too i cant find a solution either, been searching for weeks

Same here after trying to unlock bootloader

Hi ! Same problem for me and I'm looking for a solution. I bricked my phone 2 months ago... there is 1 solution that I found but IMEI is lost (not a big problem, you can flash it) and mobile network connection is lost (this is my problem). So you can flash a custom recovery with SP Flash Tools and flash a custom ROM like Havoc OS through it and that's working excepted the mobile network connection...

I found the solution and fixed my friend's 9a. It seems that after doing stuff in brom mode, the phone gets stuck somehow and all hw buttons wouldn't work at all. What I did is I opened the phone and removed the battery cable and put it back to reset the phone state, then turned the phone on.

DummyCode said:
I found the solution and fixed my friend's 9a. It seems that after doing stuff in brom mode, the phone gets stuck somehow and all hw buttons wouldn't work at all. What I did is I opened the phone and removed the battery cable and put it back to reset the phone state, then turned the phone on.
Click to expand...
Click to collapse
Don't work for me

Rares656723 said:
Don't work for me
Click to expand...
Click to collapse
Try holding the volume and power buttons for more 2 seconds when connecting and bypassing

Resetting stock ROM without usb port?

So I need to send in my 8T for trade-in. However, I'm running a custom ROM with unlocked bootloader so I need to flash stock to avoid getting denied.
Here's the problem. My usb port is broken and only allows for charging. I cannot use the MSM tool with my PC since it won't be detected. Yes I've tried everything, including cleaning the port. It's not a driver issue since it happens on multiple computers and my new phone is detected just fine.
Back in the day i used to do this all the time with Samsung phones (by downloading a ROM and flashing it in recovery from internal storage). Is it possible at all with a OnePlus? I can access Android just fine, my phone is not bricked. And it's already rooted.
Otherwise my only solution would be to either replace the usb port, or send it in with a custom rom and hope for the best.
I'd be so grateful for any help

sebas156 said:
My usb port is broken and only allows for charging.
Click to expand...
Click to collapse
- Press F to pay respects.
Well I don't know if this will help you or not... My 8T's USB connection is not stable too. But by enable ADB through devoptions, something on 8T restarts and I got a PC-recognizable USB connection back. I'm running LineageOS 18.1 / 19.1 (aka Android 11 / 12) on KB2007 and this method works on both version.
But if your PC can't detect it under EDL 9008 mode... Good luck with contacting OnePlus service center and I'll have my [ F ] key pressed...

IAAxl said:
- Press F to pay respects.
Well I don't know if this will help you or not... My 8T's USB connection is not stable too. But by enable ADB through devoptions, something on 8T restarts and I got a PC-recognizable USB connection back. I'm running LineageOS 18.1 / 19.1 (aka Android 11 / 12) on KB2007 and this method works on both version.
But if your PC can't detect it under EDL 9008 mode... Good luck with contacting OnePlus service center and I'll have my [ F ] key pressed...
Click to expand...
Click to collapse
Thanks for your respects
LUCKILY I was able to flash stock in the end. How? By trying to press the cable in 100 times. When I was just about to give up, suddenly my PC made the USB connection sound. Never was so happy to hear that sound lol. Idk what happened, but it got detected again. Well, a bit.
It took like 2 hours to get the MSM tool to work, since my device kept disconnecting during install. I bricked it 10 times over, but it worked!

sebas156 said:
Thanks for your respects
LUCKILY I was able to flash stock in the end. How? By trying to press the cable in 100 times. When I was just about to give up, suddenly my PC made the USB connection sound. Never was so happy to hear that sound lol. Idk what happened, but it got detected again. Well, a bit.
It took like 2 hours to get the MSM tool to work, since my device kept disconnecting during install. I bricked it 10 times over, but it worked!
Click to expand...
Click to collapse
LMAO
Congrats