Related
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
frol_swe said:
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
Click to expand...
Click to collapse
Have the same problem here
frol_swe said:
Last night I updated my Nexus 7 (2013) to 4.4.3, using the normal OTA notification. Everything was working fine, and the phone rebooted into 4.4.3 and I was happy. This morning however, the screen is all black and I cannot wake it in any way.
When I plug it into my computer it shows up in QHSUSB_DLOAD mode:
usb 2-1.5: new high-speed USB device number 19 using ehci-pci
usb 2-1.5: New USB device found, idVendor=05c6, idProduct=9008
usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1.5: Product: QHSUSB_DLOAD
usb 2-1.5: Manufacturer: Qualcomm CDMA Technologies MSM
qcserial 2-1.5:1.0: Qualcomm USB modem converter detected
usb 2-1.5: Qualcomm USB modem converter now attached to ttyUSB0
By holding the power button I can get it to disconnect and reconnect, but always with this result.
The device was running rooted stock firmware, and was S-unlocked.
What can I do to fix this? Hopefully there is something to do other than return it..
Click to expand...
Click to collapse
Try the nexus 7 toolkit. There are options for recovering bricks. Good luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance
DarkerTimes said:
Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance
Click to expand...
Click to collapse
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?
_keesj said:
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?
Click to expand...
Click to collapse
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk
DarkerTimes said:
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
Thank you very much, I will try
Gesendet von meinem GT-I9505 mit Tapatalk
Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.
DarkerTimes said:
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.
Click to expand...
Click to collapse
Congratulation for your first GNU/linux use !:highfive:
Yeah dmesg is super huge, it contains record of all that happened on your system since your started it up. (it s a bit more complicated in fact).
I dont know any option to make it shorter, but there are ways
- to only get the bottom of it,
- to save its output in a file
Code:
dmesg > ~/Desktop/dmesg-output.txt
- or to increase the amount of message your terminal can display (right click, profile, profile preferences, scrolling, unlimited).
However here you only need to look at what happened recently (i.e when you connected your phone)
If you connecte your phone and then run the dmesg command the end of the output should show the device detection in the last 50 lines.
I cant acces your attachement, is this only me ?
With a working phone on a non VM ubuntu you should see something like this.
(It may be different on your system, as long as you can read som usb lines, further more containing MT65xx or Mediateck, you are good to go !
....
...
[ 237.437926] usb 2-1.6: new high-speed USB device number 5 using ehci-pci
[ 237.530804] usb 2-1.6: New USB device found, idVendor=0e8d, idProduct=2000
[ 237.530809] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 237.530812] usb 2-1.6: Product: MT65xx Preloader
[ 237.530814] usb 2-1.6: Manufacturer: MediaTek
[ 237.637040] cdc_acm 2-1.6:1.1: ttyACM0: USB ACM device
[ 237.692248] usbcore: registered new interface driver cdc_acm
[ 237.692250] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapter
....
That would means that your OS detected that a new device was connected to USB and that it recognise a mediateck phone.
I hope it's also the case with your phone !
BTW I don't know vmware so well, but sometimes virtual machine prevent virtualised operating system to acces usb port. Maybe someone can confirm that this issue wont appear here ? Or you can check it out by plugging some working usb device and look if some lines get added to dmesg
MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
Nope, apparently the attachment wasn't uploaded correctly.
MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
hope it works now
View attachment 2927858
here is the output from dmesg:
first run:
[ 5.270990] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.271001] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.271010] usb usb1: Product: EHCI Host Controller
[ 5.271019] usb usb1: Manufacturer: Linux 3.13.0-35-generic ehci_hcd
[ 5.271027] usb usb1: SerialNumber: 0000:02:03.0
[ 5.272005] hub 1-0:1.0: USB hub found
[ 5.272231] hub 1-0:1.0: 6 ports detected
[ 5.273333] ehci-platform: EHCI generic platform driver
[ 5.273386] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.273404] ohci-pci: OHCI PCI platform driver
[ 5.273465] ohci-platform: OHCI generic platform driver
[ 5.273494] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.273813] uhci_hcd 0000:02:00.0: UHCI Host Controller
[ 5.273822] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 5.274010] uhci_hcd 0000:02:00.0: irq 18, io base 0x000020c0
[ 5.274349] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.274351] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.274352] usb usb2: Product: UHCI Host Controller
[ 5.274353] usb usb2: Manufacturer: Linux 3.13.0-35-generic uhci_hcd
[ 5.274355] usb usb2: SerialNumber: 0000:02:00.0
[ 5.274492] hub 2-0:1.0: USB hub found
[ 5.274546] hub 2-0:1.0: 2 ports detected
second run
[ 201.982468] usb 2-2.1: new full-speed USB device number 4 using uhci_hcd
[ 202.310781] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 202.310840] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 202.448421] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
[ 202.456529] usbcore: registered new interface driver cdc_acm
[ 202.456544] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 202.471104] usbcore: registered new interface driver usbserial
[ 202.471210] usbcore: registered new interface driver usbserial_generic
[ 202.471344] usbserial: USB Serial support registered for generic
[ 202.481866] usbcore: registered new interface driver option
[ 202.482531] usbserial: USB Serial support registered for GSM modem (1-port)
[ 241.102849] usb 2-2.1: USB disconnect, device number 4
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
btw, every 50-60 seconds i got the pluggin and unplugg sound from my windows system
Edit:
i have a second Fairphone now and tried to turn on the first one with tha accu of the second one and the second phone with the accu of the first one. both doesn´t start. only the second one with the second accu is working.
DarkerTimes said:
second run
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
Click to expand...
Click to collapse
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.
My Solution
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards
_tmp said:
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.
Click to expand...
Click to collapse
shooter_92 said:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards
Click to expand...
Click to collapse
Hey guys,
sry that I've been away for this long period of time.
The problem is that i can't enter recovery mode, so the only way to try it would be with the SP flash tool but I decided to contact the fairphone support and sent it back for repairing it.
But thanks all for your help!!
Edit: I got my phone back now. The issues were caused by damaged mainboard, they change it completely.
Sent from my Galaxy S4 using Tapatalk
I have the same problem
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?
hewitje240 said:
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?
Click to expand...
Click to collapse
Hi, did fall under warranty
Sent from my GT-I9505 using XDA Free mobile app
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.
My Fire TV bricked and none of the described un-bricking method works.
When connecting through USB I can see "Marshall London HS-USB Diagnostics 9006 (COM21)" port in Device Manager. I also observed that MiFlash tool recognize it as "\\?\usbstor#disk$ven_qualcomm&prod_mmc_storage&rev_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}"
I have unbricked my Mi Phone using this tool and it requires a ROM containing boot, kernel, system etc. images and other flashing scripts. Do we have similar kind of ROM available for Fire TV?
I am in the same boat.
Did you try this
{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Looks like I goofed up big time. Now I only see QHUSB_DLOAD and I am not able to see any drive on OSX or Linux. I am suspecting the Mi Flash tool that I was using to check it did something. Instead of showing "\usbstor#disk$ven_qualcomm&prod_mmc_storage&re v_1.00#7&5313ab4&0&1234567890abcdef&0#{53f6307-b6bf-11d0-94f2-00a0c91efb8b}" it is now showing COM20.
On linux I tried this command
Code:
dmesg | tail
and it shows following output
usb 1-2: new ISB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2: Product: QHSUSB_DLOAD
usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered for Qualcomm USB modem
qcserial: 1-2:1.0: Qualcomm USB mode converter detected
usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
Any help in this regard is appreciated.
{ParanoiA} said:
Did you try this
Click to expand...
Click to collapse
Ok.. I have a Linux VM (ubuntu 16.x) booted up, and the FireTV is recognized as a /dev/sdb device. I have downloaded the .bin file from amazon. How do I decompress the BIN file to get the images folder to dd over to the firetv partitions?
I am a linux newbie, so missing that key step
NEVERMIND - Figured it out
Thanks Rbox & {ParanoiA} for hte unbricking guide. I successfully recovered my FireTV and am back up and running.
Rbox/{ParanoiA} any way to recover my fire TV from the state it is currently in.
One more observation. Now it is showing the connection as "Marshall London HS-USB Diagnostic 9008"
After googling a bit I zeroed in that it should be recoverable. I a following this link
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
However I need following files (MPRG8064T.hex and 8064T_msimage.mbn) in addition to what mentioned in this. I am not able to find anything other than MPRG8064.hex and 8064_msimage.mbn anywhere. I am not sure whether I can use these files or not
MPRG8064.hex and 8064_msimage.mbn did not work
Can Anyone provide MPRG8064T.hex and 8064T_msimage.mbn file?
Just uploaded the requested - http://www.mediafire.com/download/jqfx835f5ompvf4/q.7z
the link contains the non T variant of the requested files
In an attempt to get the device from 9008 to 9006 mode, I attempted http://cellphonetrackers.org/qhsusb_dload-fix-qualcomm-soc.html without success
After two months of reading and testing every trick i've read on blogs, youtube, russian or chinese forums, and still at the exact same place. No matter what I do or try, I can't get out of the bloody 9008 state. Did any of you had any breakthrough on the problem? Thanks!
Hi! I would like to try to give a last shot to my almost dead LG G4 H811, after charging the battery with an external charger I tried to boot it and the screen never turns on.
After that I tried to see if my computer was able to see it, so I plugged it with the battery attached and without pressing any button I saw this in dmesg:
Code:
[ 493.380017] usb 1-12: new high-speed USB device number 10 using xhci_hcd
[ 493.522999] usb 1-12: New USB device found, idVendor=05c6, idProduct=9008
[ 493.523005] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 493.523009] usb 1-12: Product: QHSUSB__BULK
[ 493.523012] usb 1-12: Manufacturer: Qualcomm CDMA Technologies MSM
[ 493.524378] qcserial 1-12:1.0: Qualcomm USB modem converter detected
[ 493.524602] usb 1-12: Qualcomm USB modem converter now attached to ttyUSB0
Are those logs a good signal? I would really appreciate if it is possible to bring it back because we would like to use it for astrophotography on prime focus (it has a great camera)
Thanks in advance!
birry said:
Hi! I would like to try to give a last shot to my almost dead LG G4 H811, after charging the battery with an external charger I tried to boot it and the screen never turns on.
After that I tried to see if my computer was able to see it, so I plugged it with the battery attached and without pressing any button I saw this in dmesg:
Code:
[ 493.380017] usb 1-12: new high-speed USB device number 10 using xhci_hcd
[ 493.522999] usb 1-12: New USB device found, idVendor=05c6, idProduct=9008
[ 493.523005] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 493.523009] usb 1-12: Product: QHSUSB__BULK
[ 493.523012] usb 1-12: Manufacturer: Qualcomm CDMA Technologies MSM
[ 493.524378] qcserial 1-12:1.0: Qualcomm USB modem converter detected
[ 493.524602] usb 1-12: Qualcomm USB modem converter now attached to ttyUSB0
Are those logs a good signal? I would really appreciate if it is possible to bring it back because we would like to use it for astrophotography on prime focus (it has a great camera)
Thanks in advance!
Click to expand...
Click to collapse
Sounds like you may have a bricked device. You should probably give this thread a thorough read, and follow it to the T.