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????

Lenovo a850 china hard bricked, need help.

Hi..
A phone shop bricked my phone. Now it is not powered on if the battery inside. It also not power on without battery, but atleast when i connect it to USB http://telewizor.eu/displaylink.html , the red light at the phone (near camera) turn on. The pc also not detecting the phone.
Is there any way to fix it or flash it since it is not detected?
TQ

Will someone help?

kuszmania9999 said:
Will someone help?
Click to expand...
Click to collapse
maybe you have flashed wrong ROM. be careful not to confuse with ROW or CN rom. try press VOLUME UP + VOLUME DOWN and connect usb cable to your PC. works with mine.

sahniana said:
maybe you have flashed wrong ROM. be careful not to confuse with ROW or CN rom. try press VOLUME UP + VOLUME DOWN and connect usb cable to your PC. works with mine.
Click to expand...
Click to collapse
Wow....finally a reply, nevermind, i already managed to solved it by myself.

Hello,
I also having this issue and just fixed it.
See thread here :
http://forum.xda-developers.com/lenovo-a850/help/lenovo-a850-wont-power-flashing-rom-t3322646
Good Luck!

Got fully bricked oneplus one. Is it possible to flash fastboot through UART pins ?

Hello, guys I am noob af so when I was flashing Ubuntu Touch I disconnected my phone and now its don't even show up as USB it just dead no lights no anything but battery is full I checked with multimeter. So I was wondering if its possible to use UART pins to flash kernel so it can boot. Thank You all so much and if it possible just point right direction were i can find more info on serial connections.

mark1320 said:
Hello, guys I am noob af so when I was flashing Ubuntu Touch I disconnected my phone and now its don't even show up as USB it just dead no lights no anything but battery is full I checked with multimeter. So I was wondering if its possible to use UART pins to flash kernel so it can boot. Thank You all so much and if it possible just point right direction were i can find more info on serial connections.
Click to expand...
Click to collapse
There are other ways to start your device from hard-brick state; I once hard-bricked my opo and used ColorOS (Can't remember exactly) with some chinese tool and it then showed fastboot mode from there you can pick it up.

anaskhan27 said:
There are other ways to start your device from hard-brick state; I once hard-bricked my opo and used ColorOS (Can't remember exactly) with some chinese tool and it then showed fastboot mode from there you can pick it up.
Click to expand...
Click to collapse
Yes but it requires to show up as some weird usb in device manager but my don't even show when i plug it in

Charge your phone for 5 to 6 hours, this is what I did then my phone showed up in that device manager. Also follow each step on the unbrick guide on xda

thank you for help
Rex2688 said:
Charge your phone for 5 to 6 hours, this is what I did then my phone showed up in that device manager. Also follow each step on the unbrick guide on xda
Click to expand...
Click to collapse
Its now connecting but stuck in 8974_msimage_mbn loop it just trying to flash 8974_msimage_mbn and resets. Please Help.

Suggestion:
Connect with USB to Linux PC.
Big chance that yr PC sees memory card of OPO.
Copy Rom to the card.
Install with TWRP, if available, or with other similar.
That worked for my OPO brick.
Arvie

Color OS method worked for me. Just install the correct drivers and your good to go.

T-Mobile OnePlus -- Hard (HARD) Brick

Sorry for lack of details, but I'm not sure it will help anyway. Feeling pretty bad right now.
T-Mobile Oneplus 7 Pro. 256GB version.
I wanted to go to stock OxygenOS after buying the branded version two weeks ago.
I successfully got T-Mobile to unlock my SIM, and got OnePlus to send me unlock code for my bootloader after a week.
Successfully unlocked via fastboot. Tried several times to flash TWRP and no success using fastboot.
Tried MSM-Downloader from guacamole_21_O.07_190512_repack and successfully held volume both buttons to connect to the PC. MSM-Downloader said it was successfully connected.
I cannot find the exact error message I got from MSM-Downloader, but it said it didn't match plus another error message. At that point, my heart sank.
USB Device Not Recognized keeps popping up on windows again and again, while the connect sound plays. Doesn't matter if I hold down the volume buttons or not.
Can't get into qualcomm EDL mode. My guess is I hosed my boot and now it restarts endlessly when connected to anything at all.
Is this the end of my journey? I did tons of research on the best phone and the best deals available to save money, but looks like I played myself here with lack of caution.

I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.

bmg1001 said:
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
Click to expand...
Click to collapse
I cannot get into EDL. Regardless of what buttons I press (I am holding both volume buttons down in excess of 5 seconds) when connecting USB to the phone, Windows makes the "connect" sound endlessly and the driver isn't recognized.
If I can get into EDL, I will definitely try the above.

Do you have the proper drivers installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.

bmg1001 said:
Do you have the proper URL installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
Click to expand...
Click to collapse
Ok. I may be making progress thanks to your help but do have some hurdles I can see.
I do see the device when I hook it up to another computer. It shows up as Unknown USB Device (Device Descriptor Request Failed).
When I go to device manager to manually update the driver, and browse to the location I extracted the CAB file into, I see lots of devices to choose from, but the Qualcomm driver cab file list does not show "Qualcomm HS-USB QDLoader 9008" as an option. I see many Qualcomm USB Composite Devices in the list but none I have chosen seem to work (install fails).

Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?

bmg1001 said:
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
Click to expand...
Click to collapse
Yes, that is correct. Same cable i used to get into fastboot, etc... The original PC I caused the problems with recognized the device differently (showed up as a Qualcomm device) when I got into EDL with it before.
Edit: First event when plugging it into this second PC under device properties:
Device USB\VID_0000&PID_0002\5&3c8d678&0&2 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0000&PID_0000\5&1AE39384&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF000
Present: false
Status: 0xC0000719

I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.

bmg1001 said:
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
Click to expand...
Click to collapse
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?

unluckyoneplus7pro said:
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
Click to expand...
Click to collapse
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
I'll try there next. Can't seem to get any of my windows machines to recognize the thing.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.

unluckyoneplus7pro said:
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
Click to expand...
Click to collapse
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.

razorshiv said:
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
Click to expand...
Click to collapse
That's pretty cool. Makes the whole process much less stressful.
Got it up and running with international version. Now to see if I can get LOS installed. My sincere thanks to all and apologies for crapping up the board with my panic. I thought I had really screwed up, but it appears it was just stuck in EDL mode and needed a hard (HARD) reset.

Hey man, thanks for the donation. Glad you were able to get your phone up and running!

Holy Sh*t man. I know 5 bucks ain't much but I wanted to thank you so much. I thought I was fukd

Oneplus 8T HARD BRICKED ! HELP !!!

Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.

alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk

LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up

alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up

alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation

LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.

just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!🤭
forum.xda-developers.com

alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.

So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.

alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.

BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot

Thanks for sharing that - much appreciated.

alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate

LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.

alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!

alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!

NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps