Database Develop

xiaomi mi3 hard brick cold dead?

Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Try mi flash tool

Main problem is that I have tried all 3 miflash I could found 2.11.6 20131108 20140509 and none of them recognizes device and I can't even initiate flashing process ;/

it sounds like a driver issue. just download all the drivers you can find for your phone.

Shamoth said:
Lately I was flashing mi3 trough fastboot on w7ulti64bit when something went wrong and now its cold dead.
I have been looking for solution everywhere and as usual xda is my last resort for help with phones, usually I found here what I was looking for but this time it is first time when I have to post new threat.
So basically I found that battery controller had some cold soldier on chip, whole module gives 0v while cell itself 2,8v so I think I fixed it since now whole battery module shows 3.3v and cell itself 3.8v after charging.
But im unable to wake up phone in to fastboot or any other way to reflash it.
When connected to 2000mAh charger there is solid red light, when connected to PC it lit for a second then goes off and PC recognizes mi3 as USB input device and HID compliant device.
I have tried to update drivers for those devises so miflash would recognize it and allow to flash it but without any success.
Any idea what else I could do with it, or how to force flash to flash at least boot sector?
Click to expand...
Click to collapse
Same problem here, waiting for someone give the solution

if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,

ZenR2 said:
if the device is not getting detected in any of the mi flash tools,i feel its a clear sign of driver issues ,
Click to expand...
Click to collapse
r u following correct procedure for using MI flash tool ?
is ur Phone able to boot to FLash mode ( turn phone off > Press volume + Key then Press Power on - it will show flash mode )
Now Open MI Flash tool > Press Refesh > it will show phone now ( a number will b shown instead of name Xiamo Mi3)
Now Extract Fastboot rom to C Drive ( it should look like this C:\ROM (Location should not cointain space)
Now click Browse > advance > select C:\ROM\Folder\ select bat file

Its not drivers issue since its get detected as QUALCOMM HS-USB QDLoader 9008 or QUALCOMM HS-USB Diagnostic 9006 depending of its state.
In QDLoader it is recognized by miflash as COM20 device and I can upload by miflash or qpst boot image, then it switches to diagnostic that is recognized by some sort of string and I can upload/proceed with rest of rom flashing that includes creating partitions and writing data to them.
Main problem is that when its successfully flashed it is still cold dark, while PC can see it and all partitions like 28 of them...
And I think its related to the fact that qpst reports phone as in download mode.
Any idea how to exit that mode, like in Mi2 that was forced to enter "service" by shortening some pins to put it download mode to flash cold dead ones?

agdag said:
magdag from en.miui.com forum seems to be able to hekp ..or try [email protected] , jason provide paid service
Click to expand...
Click to collapse
You were already looking at it
Kinda wasted a lot of Mine and Yours time and some of my money
If You got any other ideas since that time how to resurrect it just let me know.

Any solution?
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?

androidy88 said:
Is there any solution to this problem? My phone has been cold brick for 3 days now. Doesnt boot up or charge up. Detected on connecting to PC with a sound, but Shows as Com 10 or 20 on Miflash and thus cannot be flashed.
Cannot boot into fastboot as well.
Anyone anything?
Click to expand...
Click to collapse
You can check the steps I took for recovering from a similar problem here: http://en.miui.com/forum.php?mod=viewthread&tid=22811
If you have any other questions, tag me on your reply and i'll try my best to help.

After Nougat 4.0 - onePlus 3t dead

Hi there,
perhaps you guys can help me
I use a onePlus 3T 128GB and directly after delivery I update the OS, install twrp, make a clean backup and then personalized the phone.
Runs quite good but yesterday I wanted to update the system to 4.0 Nougat...
So I downloaded the full installer, backuped the full current system via twrp and then flash and install the 4.0 version.
Yeah... doesn't work really good...
After the Pin and the code for the sim card, the OS ask for a third pin code but none of both works. And I never have another pin code since years...
Then I wipe the cache and system with twrp and restore the last backup. Doesn't work. It only boots to the onePlus Logo and then nothing happens.
Same for the first clean backup without any personalisation...
For now I have an great smartphone that doesn't work... yayy...
Anyone of you has an idea how can I get my running phone back – with all my data and apps?
Edit1: adb sideload doesn't work
Edit2: Full Installer installed >> reboot >> no OS installed
Thanks for all guys.
Oliver

https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

You said you wiped your system..
what did you expect?

use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

raj7749 said:
use this guide to unbrick. This will definitely work
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
No, it doesn't work
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.

Jo_Jo_2000 said:
You said you wiped your system..
what did you expect?
Click to expand...
Click to collapse
When wiping system before installing a full roms zip (not only an incremental update), I would expect a working, os containing partition - like on the oneplus one (did that many times on bacon). But I can confirm, it's not working on opt3; at least not with oos4. In this case I need to restore working systemmpartition (from twrp-3.0.3-0), and flash then the rom zip.

current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:

GammarursPulex said:
current status:
twrp 3.0.2
I wipe the system and the cache again.
Restore my backup from sunday before I start this odyssey.
Try to boot the restored system >> stacks during oneplus logo on screen
Flash and install the 4.0 Update Rom
Boot >> enter Pin >> enter Sim Code >> see my customize lockscreen and a pop-uped telegram message
Want to unlock >> ask for another Pin that isn't my Pin or Sim Code (use these two for years from phone to phone)
Also have a full installed onePlus3T (perhaps with Nougat 4.0) that I can't unlock because of an unknown pin.
:good:
Click to expand...
Click to collapse
Would you try the following: From twrp restore your very first backup (firmware, system and boot), don't leave twrp and wipe (reformat with f2fs) data (I'm talking of the entire userdata partition, not only "wiping data without wiping media"); flash the full oos4 zip (the one with 1.4GB); don't leave twrp, go to Advanced->copy logfile. Try to boot system.
If the system stiil refuses to boot up completly, get the logfile with adb via twrp and show us.
DO NOT try this, without usb-c otg cable and usb stick, because you are reformating your data partition. That's the reason I have not tried this: need to get an usb-c otg cable (BTW: recommendations on usb-c otg cables welcome, but OT: so PM).

GammarursPulex said:
No, it doesn't work
The friend who gave me twrp recommend this to me.
But unfortunetly the full image here is just a update, too... so of course didn't work.
But at this moment I can't transfer any stuff to the internal storage because I have no possibility.
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me

mcdachpappe said:
the unbrick tool works 100 percent - i had to use it myself too.
if you see "Android Bootloader Interface" in your device manager you did something wrong.
in the thread for the unbrick tool it says "hold volume up button while connecting your op3t to your computer". unless you dont to it this way you will always see the Android Bootloader Interface instead of the unkown device - trust me.
turn off the phone, wait a few seconds, hold volume up key and plug it in. it will work at least it did for me
Click to expand...
Click to collapse
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.

GammarursPulex said:
Only success is that the device manager lists the oneplus as "Android Bootloader Interface". But nothing for transfer works.
Click to expand...
Click to collapse
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.

rms4067 said:
Look for my comment in that thread, I had numerous issues with the driver. I don't know exactly how I got it to work, but try my steps to get the driver to show up as Qualcomm 9008.
Click to expand...
Click to collapse
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience

GammarursPulex said:
Girlfriend here: Whoever said that having a break and eat something before going back to some PC problem was right xD
Ok, what i did now:
First i deactivated the automatic Windows-Update (not sure if there was the problem, but i had some problems with this automatically-Winstupid-Stuff... doesn't matter..).
Then i connected the op3t with the volume-up-trick to the computer and i got the "RELINK HS-USB QDLOADER 9008" back in the DeviceManager. Now i deinstalled the DeviceSoftware and like you said (maybe i was blind before...) there was a checkbox unlocked. I locked it (said something like "deleting DeviceSoftware from PC" or something like that) and clicked on "OK" to deinstall the DeviceSoftware.
I interrupted the "automatical installing drivers" in the Popup what shows at the right side of the task-line (i only got ~3-5 seconds until it was finished, so i had to do this step 2 times until i was fast enough^^). Windows said now that there was no success in downloading/installing the DeviceSoftware. Finally!
Next step (now i had enough time, because Windows didn't download/install anything) was right-click on the "QHUSB_BULK" and finally could install the downloaded drivers. DeviceManager now shows a "Qualcomm HS-USB QDLoader 9008 (COM3)" at "Connections (COM & LPT)".
I started the MsmDownloadTool aaaaand got Sahara-Error
Tryed another run with changed properties (compatibility mode (Win XP, SP3) and gave AdminRights). Now it shows me "Start Download Firehose Binary" and then returns to the "Sahara Communication Failed"-msg. Glad i found lyall29's post at page 6. Needed to make the whole thing 4 times until this error was gone >_<
When the download started, the op3t got a.. not sure, yellow? maybe lightgreen? LED-signal during the download is now running.
Until i wait:
Maybe the first mistake i also had was:
When pressing the power-button for 40 seconds, the op3t has to be turned off at the end. Then wait some seconds. Then push the volume-up for 10 seconds and then while still pushing the volume-button, connect the op3t with the computer to get the msg at DeviceManager.
Nvm, after the download finished, i got another popup sais "unknown device" and that Windows couldn't install the DeviceSoftware.
I did "Step 9: Disconnect phone from PC and boot into system." aaaaaaaaaaand.... it worked. Q,Q
Now all i need to do is trying to get the backup back until my boyfriend is home
But one question is still open:
When we tryed to load the backup, then the op3t said, that the backup is encrypted. But.. i'm pretty sure we didn't encrypt the phone-data. We also thing, that the problem why the backup didn't work correctly was, that the data was encrypted and so we couldn't gain access to it. We tryed this with his Win7-PC and my Linux-Laptop. Even with different USB-Ports (2.0 and 3.0).
I'm going to do a new backup now from the op3t, but what if the problem shows up again?
Someone got an idea if the MD5-Backup-Stuff should be encrypted or decrypted?
Besides that:
Thank you very much for the help!! I guess i wasnt that qualified with fixing phone-issues and i might did some very nooby failures... so really thank you for your patience
Click to expand...
Click to collapse
When you say load the backup, you mean a backup that you made in TWRP recovery, prior to bricking your phone?
My experience with the unbricking guide was that it in essence did a full wipe and reset (including the recovery partition). That would eliminate TWRP from your phone as well as any stored backups you had.
When I unbricked, I opted to just leave it stock as nougat was around the corner.
I also re-read your original post. I wouldn't have considered your phone "bricked" at that point.
I would bet that you could have booted the phone into TWRP.
You'll want to keep these things in mind too for future TWRP encryption issues (it's a known issue that most likely won't be fixed).
1) before you make a twrp backup, remove any figerprints/pins/passwords from your device, sometimes prevents issues for me
2)if you existing pins/passwords don't work try "default_password" that may work
3)if all else fails, boot into twrp, navigate to /data/system/ and down the list will be a few files to delete
- password.key
pattern.key
locksettings.db-wal
locksettings.db-shm
locksettings.db
4) the last step is always the first step for me, too many issues with twrp and encryption

GammarursPulex said:
I gave my phone to my girlfriend, because I had to head to work. She wrote to me:
"Tryed it a couple of times now and then there was something like "QHUSB_BULK" showed up. But only for around 3 seconds, then i got the message "RELINK HS-USB QDLOADER 9008 (COM4) installed". Now the device-manager has this "RELINK..."-thing, but not at "unknown devices" but at "Connections (COM & LPT)". I tryed to go to point "Update Device Software", but all I get is "its already installed". When i go to details, it sais something about "\system32\DRIVERS\cmnxusber.sys".
After this i tryed to get the QHUSB_BULK back on the screen, but it seems like Windows7 is installing this DeviceSoftware every time when i reconnect the phone with "volume button while connecting the phone to the computer". I even tryed to deactivate/deinstall the DeviceSoftware, but its the same game every time i try it from the beginning.
Then i tryed the MsmDownloadTool, but hey.. no response. Guess i need to update the software first."
Shes now sitting in front of my PC and trying the steps. I'm out of ideas at the moment, do you have an idea what she is doing wrong or where the problem is now? (At least we are a step further now, haha!)
@nvertigo67
I can look up for this sort of cable when I'm back home. But i hope this unbrick tool will succeed.
Click to expand...
Click to collapse
u r doing something wrong.. please follow guide correctly
It works 100℅

Just out of curiosity, did you unlock the bootloader before you did everything? Also did you go into settings -->developer mode and turn on OEM unlock and USB debugging?
From my experience, try wiping everything through twrp --> install the firmware/backup --> and then try doing another wipe and reboot. Now I understand you might lose your root/SU after wiping, but perhaps this will at least boot into the system for you.
If all else fails, try using ODIN and flash your stock firmware http://downloads.oneplus.net/devices/oneplus-3t/
EDIT:
If you're having driver issues try this.
1. Go into device manager (as admin)
2. Double click the device that you're having trouble with
3. Click on "Details" tab
4. Under "Property" dropdown, choose "Hardware Ids"
5. When you select that you should see a bunch of values under there. Right click the first one and copy it.
Ex:\ I have an S7 phone so mine looks like "USB\VID_04E8&PID_6860&REV_0400&ADB"
6. Now the value you copied, try searching it in google. Or paste it on here for us to help you find drivers compatible with it. Usually you can find compatible drivers in google. Once you find them and download them, if you go back to that device and click "Update Driver" you can manually point to the extracted drivers. It will find the compatible *.inf file and install it for that device.
Hope this helps!

https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
this works for me, every time i kill my 3T.
you must be doing something wrong.
Follow everyline

Hard Bricked 4x

Hi,
I have a following problem with my Redmi 4X. I tried to flash new rom and reboot my phone on twrp. When the phone shut down nothing happens anymore just black screen. No fastboot or recovery mode. When I contact the phone to Windows pc it shows in device manager: Qualcomm HS-USB Diagnostics 900E (COM20). I have tried to flash new rom with QFIL and Miflash (tried to change the driver to Qualcomm HS-USB QDLoader 9008).
With QFIL the error is: Download Fail: Switch to EDL FailFailed to switch to Emergency Download mode.
With Miflash the error is: Cannot receive hello packet. MiFlash is trying to reset status!
Any suggestions?

https://www.youtube.com/watch?v=uxrhJkSZc6E

Already tried that. Doesn't seem to change a thing.

Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
C:\Windows\system32>

k4rpp4 said:
Shouldn't it turn the driver to "Qualcomm HS-USB QDLoader 9008" after test point method?
This is what shows in command prompt:
C:\Windows\system32>adb reboot edl
error: device '(null)' not found
C:\Windows\system32>adb devices
List of devices attached
Click to expand...
Click to collapse
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!

The test points seems to change nothing. I think that after the " adb devices" command I should see my device listed but that is not the case and therefore impossible to flash rom. Somehow I should be able to change the "900E mode" to "9008 mode" without changing the driver manually and I think the test point method should do just that.

Here is video of what I have tried to do. If someone could point out what to do differently to get the flash work I would be very grateful.
https://drive.google.com/open?id=1aOkb3FCBzanMUW3WSdyuxyQO-33rdsBv

Windows 10 will not accept the 9008 driver because the driversignature ist not signed from Microsoft.
If you will unbrick it with Windows 10 64bit look here: https://www.youtube.com/watch?v=2d8KEruHWPg
and here: https://www.maketecheasier.com/install-unsigned-drivers-windows10/

Had allready done that also. Gave it another try without success

k4rpp4 said:
Had allready done that also. Gave it another try without success
Click to expand...
Click to collapse
Is the Qualcomm 9008 driver now installed?
Did you start the mi-flash tool with administrator privileges?

I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.

k4rpp4 said:
I installed the Qualcomm drivers but device manager still shows 900E driver unless I manually change it to 9008.
edit:
I finally succeeded with test point method. Now flashing. Im so grateful to you ConradB.
Click to expand...
Click to collapse
Perfect :good:

Bro please help my device in bricked

k23m said:
After the test point method you will see a new "9008" device in the Device Manager.
Then all of the above commands will be completely irrelevant and useless.
In the 9008 mode use MiFlash, not QFIL/QPST, to reflash your phone.
Cheers!
Click to expand...
Click to collapse
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..

sayan990 said:
Thank you buddy .. Your 4 years old post help me to turn on my hard brick redmi 4x.
I don't know the actual reason of hard brick but The situation was my phone was in condition like
1. Possible to go in fastboot mode
2. When turning on there is only mi logo for fraction of second.
I tried test point method as described . It turned on in one attempt..I just want to add something. I face some issues after test point flashing . So I just flash miui again . Then It's working perfectly fine. After Test point flash check your battery. Maybe fully drained. Just charge it and turn it on..
I am posting this just for Information..
Click to expand...
Click to collapse
I do had same issue with my mobile but even when I tried to flash MIUI I got "ACK count don't match" attached img

My friend accidentally installed an A2 Lite ROM to his A2. Is there something to do?

Hello all,
A friend of mine said he was careless and installed an A2 Lite ROM to his A2. All I know is he can't fix the phone no matter what he tried.
Can we do something about this? Or is the phone permanently bricked?

lelele5 said:
Hello all,
A friend of mine said he was careless and installed an A2 Lite ROM to his A2. All I know is he can't fix the phone no matter what he tried.
Can we do something about this? Or is the phone permanently bricked?
Click to expand...
Click to collapse
try flashing stock rom

Thank you for the reply. Will get back to you as soon as I get an answer from him.

Okay, I got some more info: From what my friend said:
He installed the ROM but after selecting "restart device" it didn't boot up.
Pressing button combinations has no effect either.
When the device is connected to PC Windows recognizes it as "Qualcomm HS-USB QDLoader 9008(COM3)".
He also tried different versions of MiFlash but he is getting "The Write timed out" and "cannot read hello packets" (???) errors.
Since the device isn't reacting to button presses he can't activate fastboot.
This was translated from another language. Hope I didn't make any mistakes.
EDIT: He tried edl before, it didn't work.
Now he is getting "Error loading type library/DLL".

Your friend need to do Flash Point

Ask him to google "How to flash a qualcomm soc with qpst via com port". I'm sure he'd find a lot of videos on youtube guiding through the entire process. Also tell him to keep the stock fastboot rom downloaded, coz he'll be needing that.
Flashing a wrong rom destroyed the partition table of his device. If he cant fix it himself, tell him to visit a nearby service centre. He'll get the device back in a few days or so.

lelele5 said:
Okay, I got some more info: From what my friend said:
He installed the ROM but after selecting "restart device" it didn't boot up.
Pressing button combinations has no effect either.
When the device is connected to PC Windows recognizes it as "Qualcomm HS-USB QDLoader 9008(COM3)".
He also tried different versions of MiFlash but he is getting "The Write timed out" and "cannot read hello packets" (???) errors.
Since the device isn't reacting to button presses he can't activate fastboot.
This was translated from another language. Hope I didn't make any mistakes.
EDIT: He tried edl before, it didn't work.
Now he is getting "Error loading type library/DLL".
Click to expand...
Click to collapse
all is fine ...
he can flash it in miflash in edl mode
if computer can see the 9008 com port he is already in edl
the error with hello packets is because he waits too long to start flashing ..he needs to unplug phone then when he plugs it in he must have everything prepared then press flash quickly
he can wait for battery to run out of charge ...then prepare miflash ...then plug in phome ...the EXACt moment it wakes press flash
then it will work

Thanks a lot for your time and help everyone. He got frustrated and sent it to a service center. I couldn't convince him. It works fine now, though.

[Fix] [Guide] Device not showing in Fastboot or MSM Tool (Windows)

I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot

FireRattus said:
I recently had these issues with Windows not having the correct drivers even after installing the oneplus drivers
Since I could not easily find these solutions I thought I should share them here so that it may be easier to find for anyone who needs it
The first problem is OnePlus 6T not showing in MSM Tool and showing in device manager as QUSB_BULK_CID:xxxx_SN:xxxxxxxx
The solution I found here https://forum.xda-developers.com/t/guide-unlock-verizon-oneplus-8-5g-uw-in2019-bootloader.4409377/
is this :
Enter EDL mode with adb reboot edl or by powering the phone off and holding both volume up and down while connecting it to a PC
Next Open device manager and if you see "QUSB_BULK_CID:xxxx_SN:xxxxxxxx"
try to update the driver, it will not find one but choose the option to search Windows Update
It should open your settings to the Windows update page
You can open this manually and you should see the option to View Optional Updates
select “Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2” and install it.
This should install the correct driver, replacing “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” with "Qualcomm HS-USB QDLoader 9008" in device manager
After this I thought I had solved my problems but then the OP6T was not showing in fastboot
I eventually found my solution here https://forum.xda-developers.com/t/...ng-up-in-fastboot-mode-windows-10-11.4194491/
The issue is because of OnePlus having unsigned drivers and windows refusing to use them unless you disable driver signature enforcement
I recommend following the linked guide for this problem as the solution is identical for the 6T as well as the 8T, I couldn't write it any better and I wouldn't want to just copy their guide
But it essentially is as simple as disable driver signature enforcement and install the correct drivers with device manager so your device will show in fastboot
Click to expand...
Click to collapse
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail. It's obviously not my daily driver (based on release dates, etc.) so it's not a big deal but at the same time, I don't want to root my daily driver as it has enough trouble on stock OS as it is (Google Pixel 6 Pro). I don't need to go rooting it and introducing a whole new world of hurt, thus, the desire to root my recently resuscitated OnePlus One (I got it stuck in a boot loop one or maybe even two years ago but it wasn't my daily driver then, either and just kind of a tinker device, one of a couple at that. So rather than put in the minimal amount of effort to fix it, I just tossed in a drawer until a future need demanded that I give it the time and attention necessary, which happened to occur the other night. All went super smoothly until I hit this particular roadblock alluded to above while trying to gain root using Bacon Root Toolkit. Admittedly, I haven't tried going the old-fashioned route of gaining root but mostly because I couldn't get my computer to recognize that the device was connected to it, so that was no more an option than was going the easy route with BRT.)
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...

QneEyedJack said:
Per chance, would you know if this would also apply to the OnePlus One on Linux? I recently tried to gain root access but no matter what I did, I could not get the device to show up in fastboot or as an ADB device, for that matter. I tried both USB 2.0 ports and 3.0 ports, to no avail.
Click to expand...
Click to collapse
I am not exactly sure about this but I recommend you try what is suggested here if you haven't https://technastic.com/oneplus-usb-drivers-windows-mac-linux/
sudo apt-get install android-tools-adb android-tools-fastboot
QneEyedJack said:
Edited to mention that I successfully got it out of the boot loop by flashing cm12 and that booted up no problem. I also have TWRP installed, which actually may need updating as it was the version originally installed however many years ago prior to getting it stuck in the boot loop and subsequently getting the junk drawer treatment for 1-2 years but to my knowledge that would not cause the device to not be recognized as a fastboot/ADB device...
Click to expand...
Click to collapse
to my knowledge the recovery you have installed should not effect your device being recognized in fastboot mode
You should probably update your recovery to the latest official twrp imo