Please help. My Xiaomi Mi 3 TD (Tegra Version) is completely bricked and only shows up as APX mode. I was able to get it to communicate with NVFLASH but I can't do anything with it because it keeps telling me "unknown device found".
Is there anyway to recover from this?
Related
Hallo Everybody,
I'm new to flashing/rooting/etc. on mobile android devices, but since my Motorola RAZR I is stuck at the red Motorola logo, it is time to gather some experiance.
As said, the phone stucks at the Motorola logo, propably a bootloop. Fastboot access is possible, it is also possible to get into the recovery menu. But when I try to connect adb via the recovery menu option "apply update via usb" my PC (Win7) gets an "Unknown Device" in the Device Manager under USB-Controller.
I used adb before for playing a little bit around, so all Motorola drivers for the normal debug mode work, but I don't find a driver for the "Unknown Device" (recovery mode adb).
I already tried different USB cables and restarted my PC serveral times, but still no driver for the "Unknown Device". I also tried the Intel Driver update for android devices and forced to install the Motorola drivers for this "Unknown Device" but nothing helps.
I wanted to try to download/backup some files from the internal storage. Afterwards, I want to flash a lineageOS.
I also searched a day in the internet and in this forum but I didn't find a solution. Sorry if I didn't find the Solution-Thread.
Has somebody an Idea?
Many Thanks in advance.
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
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.
last night i got and update on my k20 pro 8gb 256 with QFKEUXM rom when i restart the phone it got hardbricked
My device is hard bricked, can't turn it on, access Fastboot or Recovery. It's also not charging, no LED and the power brick isn't getting warm. Bootloader-Unlocked , USB-Debugging disabled.
when i connected it to windows (but i didn't open it)
Windows is showing: Qualcomm HS-USB QDLoader 9008 (COM10)
I downloaded the latest Fastboot ROM for my device and region: raphael_eea_global_images_V12.0.5.0.QFKEUXM_
then tried to flash it via mi flash
MiFlash is recognizing as com10 the device and when i try to flash:
- start flash
- acessing the ROM (I think)
- ping target via firehose
then after 30 second says can't write time out device disconnected
i don't know what should i do i even payed 20$ for mi account auth via teamviewer i still got same error didn't get to auth part
the guy said your phone is dead impossible to fix it and told me even if you opened it and did testpoint it wouldn't help you (it's a hardware issue)
how can fix this issue sorry english is not my first language
Hi i got an ASUS ROG 3 I003DD ZS661KS - 6A017CN TENCENT edition bricked while updating any solution? I tried everything from computer but not opening at all, screen total black and no recovery mode starts,
Any help is appreciated
what is the device showing identified as under device manager when plugged in from the side port?
Nothing black screen, i tried up down button and power but nothing, few days ago recovery mode worked now nothing.. i tried to look some programm for force boot the phone through pc but all websites link are empty, I don’t know what to do.. i was updating the phone then this happened..
Get the device in EDL mode with working Qualcom drivers and a good connection to your pc. Then follow below guide, all needed looks to be there. You can get the device in EDL mode with a flash cable that you can buy cheap or make one yourself from a USB cable - there are guides online for doing that too.
[UNBRICK/RAW] Revive your bricked ASUS ROG Phone 3 [23-NOV-2021]
Unbrick your ASUS ROG Phone 3 for free!! Don't pay for this stuff anywhere, it's your device and you deserve the right to fix it yourself. I noticed some people in the community charging upto 50$ for the firmware which should've been free from...
forum.xda-developers.com
I connected the phone with EDL cable the computer recognize as Qualcom device etc.. but
i tried to flash the raw stock firmware trough pc and EDL cable but nothing says Sahara error mode while the process