Hi, so I have encountered a rather big issue with my xiaomi redmi 3 pro.
I believe I have flashed wrong (corrupted ? ) ROM, now I have a really annoying situation.
So, I flashed " ido_xhdpi_images_V7.2.6.0.LHPCNDB_20160129.0000.14_5.1_cn " in MiFlash, took a bit long time (nearly 15 minutes), afterwards it was completed, I disconnected my phone, and *BOOM* since then, black.
Current situation is this: When I connect my phone via USB, my phone gets recognized in device manager as
"Qualcomm HS-USB QDLoader 9008 (COM#)", also it gets recognized in MiFlash, but can't get it to work in fastboot, and it is not recognized as adb device. So, throughout 3 days now, I tried nearly EVERYTHING I have found on forums. The only thing I have not done is to take the back cover off and disconnect battery ( as I have seen on forums), tried with deep flash cable, all possible combinations of buttons and all. If the phone is connected to PC, when I press whatever combination of buttons on phone I just get Windows sound for connecting an USB device.
So today, when I connected it, red LED light was blinking, I have no idea what that was, so I plugged it into the wall to charge for 10mins, and now when I connect it, it's gone again, all black, no response whatsoever.
So, when I connect it to MiFlash and try to flash any ROM, tried nearly everyone I found, I get the same message; "Unspecified error 0x80004005; End Transfer packet id0, status 9" if I refresh MiFlash without disconnecting, and press flash again I get "Reached the end of the file. (0x80070026; Receiving hello packet) "
Things maybe to mention: I am running a 64 bit Windows 10, and my bootlocker is locked.
So I am wondering, if there is any possible way to solve this or it's time for a new phone?
alchzor said:
Hi, so I have encountered a rather big issue with my xiaomi redmi 3 pro.
I believe I have flashed wrong (corrupted ? ) ROM, now I have a really annoying situation.
So, I flashed " ido_xhdpi_images_V7.2.6.0.LHPCNDB_20160129.0000.14_5.1_cn " in MiFlash, took a bit long time (nearly 15 minutes), afterwards it was completed, I disconnected my phone, and *BOOM* since then, black.
Current situation is this: When I connect my phone via USB, my phone gets recognized in device manager as
"Qualcomm HS-USB QDLoader 9008 (COM#)", also it gets recognized in MiFlash, but can't get it to work in fastboot, and it is not recognized as adb device. So, throughout 3 days now, I tried nearly EVERYTHING I have found on forums. The only thing I have not done is to take the back cover off and disconnect battery ( as I have seen on forums), tried with deep flash cable, all possible combinations of buttons and all. If the phone is connected to PC, when I press whatever combination of buttons on phone I just get Windows sound for connecting an USB device.
So today, when I connected it, red LED light was blinking, I have no idea what that was, so I plugged it into the wall to charge for 10mins, and now when I connect it, it's gone again, all black, no response whatsoever.
So, when I connect it to MiFlash and try to flash any ROM, tried nearly everyone I found, I get the same message; "Unspecified error 0x80004005; End Transfer packet id0, status 9" if I refresh MiFlash without disconnecting, and press flash again I get "Reached the end of the file. (0x80070026; Receiving hello packet) "
Things maybe to mention: I am running a 64 bit Windows 10, and my bootlocker is locked.
So I am wondering, if there is any possible way to solve this or it's time for a new phone?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section so that the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
Hi, sorry to hear that happened to you. I suggest you to post this on Xiaomi reddit page, so more people can help you. Here is the link:
https://www.reddit.com/r/Xiaomi/
Related
I made an error in the rooting process somewhere, though I don't know where. I was trying to use CWM Recovery to install Cyanogen
Somewhere along the line, while trying to unlock the bootloader and flash ROM, I made a grave mistake.
Now, my Motorola Photon 4G is bricked. It will show nothing on the screen.
When plugged into the computer via USB, the computer will see that a USB device is plugged in, but give the message "USB Device Not Recognized" - in "Device Manager" it shows up as a "USB Mass Storage Device" with a yellow triangle with exclamation.
When plugged in to USB, the LED light is white (which is a color I had never seen before when the phone was working). Then sometimes if I try to boot the phone with Power+VOLDOWN the phone will restart or something (indicated only by the Windows notification sounds of disconnecting device/ connecting device) and then the LED light is green, as it used to show when fully charged.
Every method of fixing a bricked Photon I've found seems to require that the computer can already recognize the phone in some way. I've tried RSD Lite and others.
I just seem to be very lost here, and maybe I'm missing something obvious. Is there anything that I can do to troubleshoot this issue further?
You may want to try to charge your battery using a different phone or some external charger.
Enviado desde mi MB855
mammolastan said:
I made an error in the rooting process somewhere, though I don't know where. I was trying to use CWM Recovery to install Cyanogen
Somewhere along the line, while trying to unlock the bootloader and flash ROM, I made a grave mistake.
Now, my Motorola Photon 4G is bricked. It will show nothing on the screen.
When plugged into the computer via USB, the computer will see that a USB device is plugged in, but give the message "USB Device Not Recognized" - in "Device Manager" it shows up as a "USB Mass Storage Device" with a yellow triangle with exclamation.
When plugged in to USB, the LED light is white (which is a color I had never seen before when the phone was working). Then sometimes if I try to boot the phone with Power+VOLDOWN the phone will restart or something (indicated only by the Windows notification sounds of disconnecting device/ connecting device) and then the LED light is green, as it used to show when fully charged.
Every method of fixing a bricked Photon I've found seems to require that the computer can already recognize the phone in some way. I've tried RSD Lite and others.
I just seem to be very lost here, and maybe I'm missing something obvious. Is there anything that I can do to troubleshoot this issue further?
Click to expand...
Click to collapse
not.a.troll is probably right...I'd try charging the battery with an external charger. It's a pain in the rear, but that's best shot, then try starting over. It seems to me that you may have started the process when you weren't fully charged.
No, not a troll, despite my poor typing.
Thank you for both of your suggestions about charging the battery in some other way.
I'll try that and see if it changes things.
sorry to bring old topic back, but can you tell me how`s your phone now? because i`m having the same problem here, My photon can`t boot, not even going to fastboot when i press power & vol+
really need some help here,.. anyone??
Thanks...
I have a (supposed) MT6589 iPhone i5s clone which I managed to brick. I tried to use the instructions here to use the SP Flash Tool to unbrick it, but the first problem I have is with getting my Windows 7 (32 bit) computer to recognize the phone. I installed the MediaTek MT65xx Preloader VCOM driver and it connects for a second. I can see the device connected as a COM device, but it only stays connected for a second and then disconnects. (This is independent of whether I am running the SP Flash Tool or not.)
Is this a symptom of a bad driver? The other problem with trying to follow the instructions is that it says to remove the battery, but this copy is a 1:1 of the iPhone so it is not intended to be opened up. I tried to discharge the battery completely, but when I plug the device in, there seems to be no response (ie, Windows doesn't do anything). At some point, there seems to be some charge in the battery because of constantly plugging in the USB cable, and at that point, is when the device is recognized but is quickly disconnected.
Anyone happen to know what I am doing wrong?
So in general, I am first interested in:
Why is the device connecting properly (I assume) being recognized as MediaTek Preloader VCOM, then disconnecting in about a second?
Is it related to not being able to disconnect the battery?
In theory, wouldn't a dead battery be the same as disconnecting the battery?
When battery is dead, nothing happens when I connect the phone to my PC. This seems odd since I am supposed to be able to connect to the PC without any battery... What is the difference?
Per instructions, I've been pressing the + volume button when connecting, but I seem to get similar results no matter if I press + or not.
Should I be loading any other drivers besides the MediaTek Preloader drivers?
Thanks.
PS. I've decided to open up the phone using a video found on YouTube, and found that the battery is soldered, so I am not so motivated in trying to disconnect the battery if possible.
Update: OK, the problem I likely had with the phone is that since the phone was in a type of "boot loop", I couldn't actually tell it was on or not... And plugging in the cable only worked if the phone is off. Once I made sure the phone was dead due to battery dying and made sure I did not turn the phone on, I could connect, let the battery charge long enough for the phone to respond to the PC, and then it was recognized by SP Flash Tool. However, seems I may have tried flashing something incompatible as the phone is not responding. I'll likely need to write another post once I can find the symptoms of what is going on.
Try hardware preloader MOD which means test point on the phone board; by soldering one to GND and another point on the board (connecting points are clear on the board), this will stop connecting and disconnecting phenomenon
Hi everyone, I have the unfortunate moment of having a failure during an update by LG PC Suite. Initially it was stuck with the picture "Downloading mode", but as the update keep failing at 4%, I read some online threats to press the volume up and power, and now I regretted it. I am stuck with the phone being detected as "hsq-usb dload", no way to go back to the "Downloading mode" picture, even though I tried pressing combinations like volume up+volume down..etc...
I did a search and found alot of people having the same problem, but unfortunately, I am unable to find a solution that fix mine. So far I have installed the Qualcomm hs-usb qdloader driver and it shows up under Device Manager as Port 8.
I have tried the following:
1) Using QPST, detected as phone in "Downloading mode", but I do not know how to proceed as the images and hex files online are not for my model. In addition, it requires the SPC code...so....
2) Using a trial version of CDMA workshop, it detects my phone as "Downloading Mode". I tried to use it to switch modes to Reset or Power Off, but it didnt work.
In addition, the trial mode does not allow me to "read" the SPC code. An earlier version of 2.7 is totally not able to "Read" my phone, showing all details as "Error:" when a read is attempted
3)Using Linux, Ubuntu (via VMPlayer). I was able to see it being detected under lsusb command, which shows as a qualcomm modem. I tried using scripts from various sources like brickdetect.sh, PblClear, lgL9FixBoot.sh ( I know these aren't for my phone, but I was desperate enough to try), and nope, it didnt result in any change in state of my phone.
I am not really a technical person (but willing to try), and I have spend 2 days trying and researching, and I am now out of ideas. As such, I am posting here hoping if anyone has any solutions? Thanks in advance!
Update as of 2 days of these trial: My phone has a solid amber light at home button when battery and usb (to computer) is connected, when pressing it, it goes from amber to red, to amber and vice versa again for around 1 minute, then it disappears. On my computer I see something disconnecting and connecting. In the end after 1 minute after the light disappears, the qualcomm hsqusb qdloader appears under Ports in device manage.
If I do not connect the battery and just connect via usb, the qualcomm hsq-usb qdloader appears under port without any flashing light on the phone.
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
You haven’t said much about as to what you had done with this phone prior to your issue, whether you have left your P9000 as standard with OTA updates or perhaps you have rooted, flashed a different Rom or changed its Kernel ?
It’s hard for anyone to give help easily without some background from you.
You're right, I bought it two weeks ago as a used part. To my knowledge it was left as standard (previous owner didn't seem to be skilled too much since some of his folders remained on the phone) and as far as I remember the installed ROM was 20160810, although I'm not 100% sure since I'm also new to android / not experienced with ROM versions and didn't write it down. At the end I believe the phone had never been rooted or changed kernel.
Maybe worth mentioning: The last two days before failure I noticed that the phone restarted one or two times per day.
@brager
There are two possibilities (or more)
1. It's hard bricked, so Google for a mtk hard unbrick guide
2. It's a battery related problem
Keep it two days plugged, or replace it
Keep in mind that the newest mtk software has to be installed on your computer
And try another cable first of all
1. It's hard bricked, so Google for a mtk hard unbrick guide
Click to expand...
Click to collapse
I've already performed all the steps in these mtk hard unbrick guides. I'm able to enter META mode but when I try to flash the preloader I get the error described above [BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)]
2. It's a battery related problem
Keep it two days plugged, or replace it
Click to expand...
Click to collapse
As far as I understand it flashing can/should be done without battery.
Keep in mind that the newest mtk software has to be installed on your computer
Click to expand...
Click to collapse
I was using SPFT 5.1524.00, now updated to SPFT 5.1628 and get nearly the same error: BROM ERROR: STATUS_DA_HASH_MISMATCH (0xC0070004)
And try another cable first of all
Click to expand...
Click to collapse
...didn't change anything.
I think the phone has a hardware problem and went to heaven.
Brom error: Status_da_hash_mismatch
brager said:
Lately during the morning after having my P9000 charged overnight it suddenly shut down and after that was completely unresponsive:
I tried powering it back on but it wouldn't (neither by pressing the power button nor in combination with volume+ or any other button).
I tried charging it again but the LED isn't lighting up so I'm guessing it's not actually charging either.
Then I tried to reanimate it with SPFT but realized that the phone wasn't recognized by the pc. When I pressed the volume+ button it was recognized as "MediaTek USB Port (COM3)" for some seconds but then disappeared again.
Despite of that I tried to flash the stock ROM 20160810 (as well as others - no difference). Every time I get the same error:
BROM ERROR: STATUS_DA_HASH_MISMATCH (-1073283068)
Also I tried to flash preloader only, without any difference.
Then I opened the cover, removed the battery and tried again - nothing changed: The pc recognizes my phone only when I'm pressing volume+ but throws the error above when trying to flash.
Next I shortened the GND point on the phone's mainboard to any test points, but couldn't bring the pc to recognize the phone.
Any ideas...? Does someone know what the error message means? I know that DA stands for "download agent".
Click to expand...
Click to collapse
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Help,I have the same problem
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
It has been 2 days that i try to fix this problem,because i thought it was a driver problem i formatted my windows 7 and reinstalled everything.
This issue still persists and my phone is brand new.
Hi,
I got my new phone a couple of days back, installed CM13 (officially unlocked, did that with TWRP + install ROM) probably incorrectly because i couldn't get the fingerprint sensor and other stuff to work at all.
Today my phone turned off by itself with around 70% of battery left and it's not responding anymore. Cannot go into Recovery mode, not even to Fastboot. Connected it to the charger and have the red light of the devil blinking... Tried to do everything i found online but i couldn't get into EDL mode (and then Flash through MiFlash), since fastboot is not working at all.
I really don't wanna have to open the back of the phone and. What can i do to save the phone? Is there any proven solution and a comprehensive guide to this (for a total idiot like me)?
Yes there is deep flash cable method search on xda/youtube it works like a charm,😉, this method saved me once
Try this (http://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055) works 100%
Try to disconnect and reconnect the battery.
This has kicked me into EDL mode once and after flashing it was fine
Both methods are sound, but if you decide to remove the back cover, remember to eject the SIM card tray first
Thanks for the replies, i was hoping i wouldn't have to have to open the back cover and disconnect the battery but it seems to be the only option at this point.
The deep flash cable doesn't seem that difficult tho, why don't you give it a shot? It seems like that's what they use at MI service centres after all.
So i have managed successfully to have the pc recognise the device as Qualcomm Hs USB Qdloader 9008, opened the MiFlash tool and recognised the device, but when i try to flash a stable MIUI rom i get an error: "Write timed out" as many times i tried to do it.
Does anybody have a suggestion?
My device was unlocked officially and i have no recovery no fastboot nothing at all.
alphax_ said:
So i have managed successfully to have the pc recognise the device as Qualcomm Hs USB Qdloader 9008, opened the MiFlash tool and recognised the device,
Click to expand...
Click to collapse
Which method you used - Deep Flash cable or Battery disconnect?
Yeah sorry i did not mention it, disconnected the battery.
i tried the battery removing method but the phone is not responding
now need to try cable method
Ryan Raghendh said:
i tried the battery removing method but the phone is not responding
now need to try cable method
Click to expand...
Click to collapse
Get into EDL