HTC 816w MT6582 "USB DEVICE NOT RECOGINZED" error after flashing, - Desire 816 Q&A, Help & Troubleshooting

Hi all,
Phone was showing "force closing" messages, I flash it with sp tool, now phone is dead which was due to flashing wrong PreLoader, Now phone showing only USB Device Not Recognized when trying to flash while press and holding down volume down button, I tried to short clo point with gnd but luck, Any good expert help to troubleshoot the problem to recover phone,
thanks
regards

Related

HTC One X doesn´t start anymore

Hello guys,
I am new here and thats my first post, please tell me when I do something wrong. But I think this is the best forum to ask :
I had a well-functioning HTC One X. But at once it doesn´t start and stuck in the HTC bootlogo. I googled it and after many days I try to unlock the bootloader. The bootloader starts only after many trys and then shows a red field "battery level is too low to flash"(connected to PC). The red led doesn´t lights up. I leave it in the bootloader and after many hours it starts normally (bootloader still locked). I set the phone back to factory settings (not in the bootloader). I used it like every day, but after hours when I switch to the normal menü it was stucked for 5 seconds and then the screen become black and it wont restart. I buy accumulator for the phone and exchange it (I have a little bit "hardware skills"). I connected it with loading cable to the socket (not the PC!). The red LED flashes for a second and then happens nothing. After many trys the bootloader shows up (connected to my PC) and I googled for almost hours to find a solution. "I have to install a custom ROM". I unlocked the bootloader with the programm "One X All-In-One Kit v2.3". I don´t know why but I shut the phone down. I try to start the phone or the bootloader but it doesn´t work. I try it now for weeks but it is dead (but I´m very sure the problem that it doesn´t starts is not due to the unlocked bootloader, because it is the same problem with the "not starting" like the time before I unlocked it). But the strange thing is... and now comes the important part... when I connect the phone with my PC the PC make the "USB connected"-sound and says that there is a unrecognized device connected. And when I try to start the bootloader the PC makes the "USB disconnected"-sound and a second later the "device-driver software not installed"-sound (I hope you know what I mean) and when I keep trying to start the bootloader it happens again and again the same. I tried almost everything, I use a loading.bat file but it can´t detect the phone (you know "unrecognized device"). Is it the accumulator ? Is the hardware dead ? Or what is the problem ?
I hope you understand this text (I´m sixteen and from germany). If you don´t please ask me every question you have. I really hope you can help me with my really long-term problem.
Thanks for every question, reply, solution or improvement proposal for me
XilentMe
So, what i have deduced is that
1. You are stuck on fastboot with low battery.
2. Your PC does not recognize your device.
For this purpose, first download and install the htc usb drivers. These should work: http://forum.xda-developers.com/showthread.php?t=2211791
Then visit this thread: http://forum.xda-developers.com/showthread.php?t=1658084
follow the instructions, once your phone is charged enough, unlock the bootloader, flash a custom recovery, boot into recovery and let it charge for a while, then flash a new rom.
Dont forget to press the Thanks button if i helped
Okay thanks for your proposal, but the problem is now that I can´t boot into bootloader, the phone does nothing. No reaction, no charging LED, no normal boot, no bootloader...absolutely nothing. Only when I connect the HTC to the PC the PC make the "USB-device connected" sound, as if you connect a USB-stick to your PC, but nothing else happens.
Any ideas or similar problems ?
XilentMe
So try to charge via pc. Leave for some time connected to pc and try to power up.
Hey,
I tried it, but it didn´t work. Nothing happens, only the "plug off-sound" when I want to start the bootloader via volume down+power button, while it is connected to the PC. I have no idea what to do.
XilentMe

[Q] Unable boot to "Download mode"

Hi every one
i got my E988 OTA update , but it fail to boot up and Show "secure booting error cause boot certification verify"
i tried many method on this forum , but it not enter "Download Mode" and detect by the PC. Please advise anything i can try?
Thank you everyone :crying:
Make sure your drivers are installed.. Take battery out and hold both volume buttons and plug in usb
2SHAYNEZ
It took me a while as well to figure out the whole 'Download Mode' thing but it became easier once I got the technique down. This is my anecdotal evidence but I dont think you need to surely have drivers installed since I plugged it into my Linux machine and it still entered download mode.
This is the method I used.
1) Turn the device completely off.
2) With one hand, Hold down both Volume arrows on the device for about 3 seconds
3) Using your other hand, plug your device into your computer. (As in, already have it plugged into USB and plug the Micro-USB port into your phone)
4) And it should show 'Download Mode' on your phone.
Hope that helps!
Thank you all bro~
 @shayneflashindaily thank you ~I have install/reinstall every Driver,and also got same..
 @GreatCaesar: i tried your method , it got same result , still show "secure booting error":crying:
maybe its a bad cable.......

Device bricked - white LED only flashing when connected to USB cable, no EDL possible

Hi
I need really some good ideas.
My Mi Mix 2 bricked first when I was flashing the global rom via TWRP.
Installation worked out, I choose restart system in TWRP and then the screen got black and nothing happened any more.
At that time device was in EDL mode and was detected by MiFlash.
After some days I solved the "cannot receive hello package" issue and MiFlash started to flash the system (I choose China stable as first recovery).
Unfortunately MiFlash was not successful, I got the "Not enough storage is available to process this command.(0x80070008; Max buffer sector is 256)" failure message and since that the device is more or less fully dead:
no reaction at all on any hard button combinations
no EDL detected
no fastboot
The only reaction I see is the white LED light flashing when connected to a USB cable, but the PC does not recognize the device at all anymore.
Any idea how I can bring back the device to life?
Thnx
no one any idea to support?
How did you solve it man
why don't you try to use deep flashing cable to get edl mode

Vibe P1A42 stuck at Lenovo logo bootloop

Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
After a lot of trials I could solve the problem, but I dont know what I did different.
I did everything the same.
Anyway thanks to everybody who read.
Regards.
hagiwatt said:
Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
hagiwatt said:
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
Click to expand...
Click to collapse
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
pavanpilot94 said:
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
Click to expand...
Click to collapse
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
hagiwatt said:
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
Click to expand...
Click to collapse
Hi Everybody!
I have just recieved the phone from service center. They fixed the vibration problem under warranity.
So binary counter did not affect the warranity status.
I dont know if they checked the counter or not.
For information to anyone who has the same issue.
Regards.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
and if the pc did not detecte the phone and i cant see any thing new in device manager ,plz help me

Water damaged OP3 only shows Tux at boot for 3 seconds (hard brick?)

Hello,
I've got a water damaged OP3 (it was in a pool for about 1min). Now after a few days having it in a pot of rice and cleaning the logic board with 100% isopropanol it finally woke up when pressing power button.
My problem now: It just shows up with a Linux Logo (a small Tux in the middle of the screen) and then turns off after 3 seconds. If I connect it with a charger, the screen persists for the moment.
When pressing + holding volume up button, windows recognizes it as "unknown usb device" and screen stays black.
I only need to access the flash to rescue some of my recent (of course not backed up) data.
What do you suggest? Could I try the unbrick the phone or do these symptons point to a irreversible hardware damage?
Is there a way to read the flash without flashing (or with flashing a minimum set of) stock image?
best regards and thanks in advance!
Contact a software technician
juuz said:
hello,
i've got a water damaged op3 (it was in a pool for about 1min). Now after a few days having it in a pot of rice and cleaning the logic board with 100% isopropanol it finally woke up when pressing power button.
My problem now: It just shows up with a linux logo (a small tux in the middle of the screen) and then turns off after 3 seconds. If i connect it with a charger, the screen persists for the moment.
When pressing + holding volume up button, windows recognizes it as "unknown usb device" and screen stays black.
I only need to access the flash to rescue some of my recent (of course not backed up) data.
What do you suggest? Could i try the unbrick the phone or do these symptons point to a irreversible hardware damage?
Is there a way to read the flash without flashing (or with flashing a minimum set of) stock image?
Best regards and thanks in advance!
Click to expand...
Click to collapse
you better avoid doing experiments on op3. Symptoms you have mentioned in your thread, tells that your has been flashed (don't have usb drivers,no os,no firmware). I have faced same problem with my letv le 1s. It is a software problem. Your phone is totally empty. So do contact with any software technician, he uses sp flash tool to wake up the device. Download sp flash tool and follow procedure. If sp flash tool is detecting your device then it means your device hardware is fine.
juuz said:
Hello,
I've got a water damaged OP3 (it was in a pool for about 1min). Now after a few days having it in a pot of rice and cleaning the logic board with 100% isopropanol it finally woke up when pressing power button.
My problem now: It just shows up with a Linux Logo (a small Tux in the middle of the screen) and then turns off after 3 seconds. If I connect it with a charger, the screen persists for the moment.
When pressing + holding volume up button, windows recognizes it as "unknown usb device" and screen stays black.
I only need to access the flash to rescue some of my recent (of course not backed up) data.
What do you suggest? Could I try the unbrick the phone or do these symptons point to a irreversible hardware damage?
Is there a way to read the flash without flashing (or with flashing a minimum set of) stock image?
best regards and thanks in advance!
Click to expand...
Click to collapse
Have you installed the necessary drivers in Windows for the phone to show up as Qualcom HS-USB..........Loader9008? Otherwise your phone will not be recognised when you do volume press for 10 seconds and connect. Even if it is recognised in this "service" mode, you may be able to unbrick/restore your phone but in the process, the entire phone would be wiped clean. (I know since I have done it).
tnsmani said:
Have you installed the necessary drivers in Windows for the phone to show up as Qualcom HS-USB..........Loader9008? Otherwise your phone will not be recognised when you do volume press for 10 seconds and connect. Even if it is recognised in this "service" mode, you may be able to unbrick/restore your phone but in the process, the entire phone would be wiped clean. (I know since I have done it).
Click to expand...
Click to collapse
I've tried to get the phone into EDL Mode (Qualcomm chip), but had no success, phone vibrates and windows recognizes an "unknown usb device" (pressed Volume Up and connected to USB, phone was definitely turned off). But I am not able to get the device recognized as "QHSUSB_BULK" which - afaik - is the prerequisite to install the Qualcomm USB Driver und go on with the unbrick procedure..
I hope anyone got some idea how to get the phone back to life..
juuz said:
I've tried to get the phone into EDL Mode (Qualcomm chip), but had no success, phone vibrates and windows recognizes an "unknown usb device" (pressed Volume Up and connected to USB, phone was definitely turned off). But I am not able to get the device recognized as "QHSUSB_BULK" which - afaik - is the prerequisite to install the Qualcomm USB Driver und go on with the unbrick procedure..
I hope anyone got some idea how to get the phone back to life..
Click to expand...
Click to collapse
Your understanding of the unbrick steps is not correct. Initially the phone will not show up at all or may show up as unknown or something else. It is only when you install the EDL mode drivers and then hold the power button down for 40 seconds and the hold down the volume up button for 10 seconds and connect to PC, will it show up in the EDL mode. Ofcourse you will have to disable the driver signature verification before installing the drivers.
Read the Unbrick Guide again and install the drivers before trying to connect.
tnsmani said:
Your understanding of the unbrick steps is not correct. Initially the phone will not show up at all or may show up as unknown or something else. It is only when you install the EDL mode drivers and then hold the power button down for 40 seconds and the hold down the volume up button for 10 seconds and connect to PC, will it show up in the EDL mode. Ofcourse you will have to disable the driver signature verification before installing the drivers.
Read the Unbrick Guide again and install the drivers before trying to connect.
Click to expand...
Click to collapse
Thanks so far, but being a software developer myself I am not a totally beginner. I followed the guide, also read it twice etc.. Also tried another USB cable including the original Oneplus cable.
When plugging it in while pressing Volume Up my Linux laptop reports this:
Code:
[40474.458362] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426231] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426354] usb usb3-port2: attempt power cycle
[40476.710061] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.677934] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.678051] usb usb3-port2: unable to enumerate USB device
On my windows machine the device manager reports "Windows has stopped the device because it has reported problems. (Code 43)".
Any suggestions? It seems that the device has lost all firmware etc. and there is no EDL left on the device.
EDIT:
With holding Vol(-) and Power I could get rid of the Tux Penguin and enter fastboot and recovery of the phone.. NAND seems to be okay, can decrypt my internal storage.. The USB port doesn't work in recovery (same error like I had with the EDL mode, unknown device)..
I hope I can now charge the battery a bit and recovery my data...
Thanks so far guys..
juuz said:
Thanks so far, but being a software developer myself I am not a totally beginner. I followed the guide, also read it twice etc.. Also tried another USB cable including the original Oneplus cable.
When plugging it in while pressing Volume Up my Linux laptop reports this:
Code:
[40474.458362] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426231] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40475.426354] usb usb3-port2: attempt power cycle
[40476.710061] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.677934] usb usb3-port2: Cannot enable. Maybe the USB cable is bad?
[40477.678051] usb usb3-port2: unable to enumerate USB device
On my windows machine the device manager reports "Windows has stopped the device because it has reported problems. (Code 43)".
Any suggestions? It seems that the device has lost all firmware etc. and there is no EDL left on the device.
EDIT:
With holding Vol(-) and Power I could get rid of the Tux Penguin and enter fastboot and recovery of the phone.. NAND seems to be okay, can decrypt my internal storage.. The USB port doesn't work in recovery (same error like I had with the EDL mode, unknown device)..
I hope I can now charge the battery a bit and recovery my data...
Thanks so far guys..
Click to expand...
Click to collapse
Sorry if I had sounded condescending, but I had no way of knowing your level of expertise.
Best of luck for restoring your phone or for saving the data.
tnsmani said:
Sorry if I had sounded condescending, but I had no way of knowing your level of expertise.
Best of luck for restoring your phone or for saving the data.
Click to expand...
Click to collapse
No need to worry.. Of course, you couldn't know and there are a lot of people asking dump questions..
My phone is back a life, I guess the data transfer via USB is not working anymore, charging works although I needed to take my Oneplus One's battery (identical connector, just need to take care of the pin layout [+/-]) because my OP3 battery is pretty low and I don't know if I can reactivate it.. It has about 3,4V at the moment and charges very slow..
Finally, if anyone else faces this issue and can't boot his phone:
Try different button combinations and keep holding the buttons several seconds/minutes..

Categories

Resources