It seems that my phone has gone into a fully bricked state. Doesn't respond to the power button. If I plug the usb cable in tho I do get:
usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
and it shows up in lsusb.
Is there anything I can do in this state to unbrick my phone? Or shall I send it to somewhere that can jtag it for me?
Thanks
Julia
quixoticgeek said:
It seems that my phone has gone into a fully bricked state. Doesn't respond to the power button. If I plug the usb cable in tho I do get:
usb 1-1: Qualcomm USB modem converter now attached to ttyUSB0
and it shows up in lsusb.
Is there anything I can do in this state to unbrick my phone? Or shall I send it to somewhere that can jtag it for me?
Thanks
Julia
Click to expand...
Click to collapse
Could you tell us what happen just before that. Maybe it could help...
Related
Help me!
I'm have XDA, with wrong flashed bootloader. In this time no bootloader picture, no other in display. When use the hard reset button, only two led's up. When i'm put the charger, phone chargigng it.
Please help me how to repair this XDA?
I'm build nullmodem cable for clean communication.
Thanks,
B.R. Thira
http://wiki.xda-developers.com/wiki/XDAtools
well this page have a picture which mention broken bootloader
maybe you should look into that
I'm read this, but i'm don't look, what cable use for upload bootloader. The software called pnewbootloader.exe don't have any option, or other switch. (com port USB port, speed) With usb cable and with Serial Link cable have no communication.
Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot
bcuraman said:
Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version.
http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25
The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made.
Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty?
I can't reach recovery,fastboot or anything
Any help would be much appreciated. Thank's a lot
Click to expand...
Click to collapse
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.
suraj.das said:
Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006
Let me know if it shows that.
(go to device manager on pc to check that)
If it doesnt show, try taking the battery out and putting it back and then connecting to pc.
Click to expand...
Click to collapse
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
bcuraman said:
yeah: This is the result of the command line:
" 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3)
[50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2)
[50149.664014] wlan0: associated
[51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci
[51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008
[51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[51146.928969] usb 1-4: Product: QHSUSB__BULK
[51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM
[51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.
suraj.das said:
Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
Extract it. Connect your phone and then click on the msm 8974download.exe..
Wait till it turns green and then reboot your phone
Thanks to Addel from oppoforums.
Click to expand...
Click to collapse
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?
bcuraman said:
Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?
Click to expand...
Click to collapse
I have no idea. Sorry. Maybe use your friend's pc? OR VM?
Hi there. I too am having issues with my Find 7 as well. I just bought it today. The previous owner apparently went to flash cm11 and he soft bricked it. The phone will power on to the start screen the the screen stays black and goes on and off. I can get to fastboot but not recovery. I have read in the oppo forums that I need to push the stock recovery too it but am unfamiliar with fastboot. I am willing to pay someone to get this phone working. Any input would be greatly appreciated.
MsmDownloader works great from inside an Windows XP VMWare virtual machine.
Hello,my nokia x
Old phone
Now,my phone stuck logo,no recovery,usb port is modified not usb port original,only can charge. Volum down is die. I dont connect to pc to fix this problem. Every body can help me fix?. Thank for reply
Without working USB port and recovery it's rather impossible to fix it
BluRaf said:
Without working USB port and recovery it's rather impossible to fix it
Click to expand...
Click to collapse
How to buy USB port?
thinhx2 said:
Hello,my nokia x
Old phone
Now,my phone stuck logo,no recovery,usb port is modified not usb port original,only can charge. Volum down is die. I dont connect to pc to fix this problem. Every body can help me fix?. Thank for reply
Click to expand...
Click to collapse
if usb port is charging but not connecting to pc...then u should try and use new usb cable (I had the same problem of usb cable-only charging) and for volume down, remove back panel amd try to press it with your nails...maybe it could help
ani00 said:
if usb port is charging but not connecting to pc...then u should try and use new usb cable (I had the same problem of usb cable-only charging) and for volume down, remove back panel amd try to press it with your nails...maybe it could help
Click to expand...
Click to collapse
usb cable is working normal with xiaomi mi3, lg me p350
thinhx2 said:
How to buy USB port?
Click to expand...
Click to collapse
Just ask your local phone service or find phone parts wholesaler and somebody with "hot air" operating skills.
Hi, recently I've fixed my k012's usb port. It was ripped from circuit, fell down while charging. Now i can charge the device alright but my pc is unable to detect the device. No ADB, no Fastboot, no MTP at all. Is my usb port busted? or do i need driver or anything. Is there any way to check if my pc can detect a device? Thank you.
Hello XDA community,
I am facing an issue with my device after flashing the wrong ROM. The device entered EDL mode, and when I connected it to my computer, it initially showed up under Ports in Device Manager as COM 10. However, now it is showing up under USB Controllers as an Unknown USB Device (Device Descriptor Request Failed).
I have tried the following solutions without any success:
Reinstalling the device driver by uninstalling and letting Windows reinstall it automatically after a restart.
Manually updating the driver through Device Manager.
Performing a hard reset and attempting to enter bootloader/recovery mode.
Trying different USB ports and cables.
Installing the Qualcomm QDLoader driver.
Unfortunately, none of these solutions have worked for me. I would greatly appreciate any advice or suggestions on how I can resolve this issue. Thank you in advance for your help!
"Device descriptor failed" is the most basic USB error possible in Windows.
It means that the device has asserted pullup on the D+ but is not responding to anything.
As proof of concept I just did that with a resistor and a cable.
This means that the USB interface is enabled but it is totally dead.
Not ADB, not fastboot, not EDL, nothing.
Renate said:
"Device descriptor failed" is the most basic USB error possible in Windows.
It means that the device has asserted pullup on the D+ but is not responding to anything.
As proof of concept I just did that with a resistor and a cable.
This means that the USB interface is enabled but it is totally dead.
Not ADB, not fastboot, not EDL, nothing.
Click to expand...
Click to collapse
Not everytime. It may be due to faulty usb cable and sudden power surge on the usb port.
mvikrant97 said:
Not everytime. It may be due to faulty usb cable and sudden power surge on the usb port.
Click to expand...
Click to collapse
Well, ok. Cut the white wire on a cable and you'll get this all the time.
In any case, it means, "I can sense something is plugged in, but I can't get to "Square One".
Renate said:
"Device descriptor failed" is the most basic USB error possible in Windows.
It means that the device has asserted pullup on the D+ but is not responding to anything.
As proof of concept I just did that with a resistor and a cable.
This means that the USB interface is enabled but it is totally dead.
Not ADB, not fastboot, not EDL, nothing.
Click to expand...
Click to collapse
what is the solution?
You've apparently bricked your device.
You need to flash everything using EDL mode.
You probably need to use EDL test points to get there.
It's bypassing EDL mode on boot because it thinks things are ok.
But as it gets further along it discovers that it's a train wreck and just stops.
If you had killed it more it would have gone directly to EDL mode.
Renate said:
You've apparently bricked your device.
You need to flash everything using EDL mode.
You probably need to use EDL test points to get there.
It's bypassing EDL mode on boot because it thinks things are ok.
But as it gets further along it discovers that it's a train wreck and just stops.
If you had killed it more it would have gone directly to EDL mode.
Click to expand...
Click to collapse
I don't have any issues myself, but do you think one of these "DeepFlash" Cables (e.g. on eBay) work? They are able to trigger EDL Mode apparently.
I've also read that you can just DIY such cable.
Long time ago, my phone had also gotten hardbricked due to an aborted Fastboot Flash.
I don't remember if Device Manager said "Device Descriptor Failed", but it wasn't in EDL Mode and I had to remove the backglass and trigger the EDL Test-points. All good though now.
I've never resolved exactly where the code for detecting a grounded D+ line in the USB is.
It could be in the PBL (in ROM), the xbl or the abl.
I'm not sure if all devices have it.
I'm quite sure that I've never gotten it to work.
That may be because of the devices I've tried or my lack of coordination.
OTOH, I have half a dozen devices that I can hit the EDL test points.
YMMV