Hello everybody,
please my question is very simple.
Can I use CDC device (USB-SPI converter by Microchip) with GT7500?
The device uses CDC ACM drviers. When I plug in to my computer I see ttyACM0 is created in /dev/ folder.
If I connect device to GT7500 throw USB Adapter dmesg inform me about Device not supported (dmesg short report in bellow). But if I look to .config i see is CDC ACM driver is inculded.
If plug device to my second tabled WM8650 everything is OK. /dev/ttyACM0 is created and accessed from app.
Thanks for any answer.
Tulak
Sorry my english.
DMESG from GT7500:
<6>[ 51.517019] tegra-ehci tegra-ehci.0: Tegra EHCI Host Controller
<6>[ 51.517185] tegra-ehci tegra-ehci.0: new USB bus registered, assigned bus number 2
<6>[ 51.524200] [ CONNECTOR_DRIVER (acc_notified,387) ] ACCESSORY=OTG : STATE=online
<6>[ 51.544106] tegra-ehci tegra-ehci.0: irq 52, io mem 0xc5000000
<6>[ 51.563811] tegra-ehci tegra-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 51.563983] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 51.564019] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 51.564048] usb usb2: Product: Tegra EHCI Host Controller
<6>[ 51.564072] usb usb2: Manufacturer: Linux 2.6.36.3 ehci_hcd
<6>[ 51.564096] usb usb2: SerialNumber: tegra-ehci.0
<6>[ 51.568457] hub 2-0:1.0: USB hub found
<6>[ 51.568519] hub 2-0:1.0: 1 port detected
<6>[ 51.570408] tegra-otg tegra-otg: tegra_start_host-
<6>[ 51.570441] host_notify: ndev name=usb_otg: from state=0 -> to state=1
<6>[ 52.173954] usb 2-1: new full speed USB device using tegra-ehci and address 2
<3>[ 52.431969] usb 2-1: device v04d8 p000a is not supported
DMESG from WM8650:
usb 2-1: New USB device found, idVendor=04d8, idProduct=000a
usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
usb 2-1: Product: USB Device - CDC Mode
usb 2-1: Manufacturer: Microchip.
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
cdc_acm 2-1:1.0: usb_probe_interface
cdc_acm 2-1:1.0: usb_probe_interface - got id
cdc_acm 2-1:1.0: This device cannot do calls on its own. It is not a modem.
cdc_acm 2-1:1.0: ttyACM0: USB ACM device
usb 2-1: adding 2-1:1.1 (config #1, interface 1)
usb 2-1:1.1: uevent
Sorry for needless information in dmesg.
To time 51.568519 is pluging USB adapter.
Tulak said:
Sorry for needless information in dmesg.
To time 51.568519 is pluging USB adapter.
Click to expand...
Click to collapse
Hi,
I also have similar problem of a cdc-acm device working on one tablet and not on the other.
On the tablet on which it doesnt work, the ROM doesnt come with the cdc-acm.ko so it was "insmod" ed
Any help on this? Anyone?
I have the same problem with Samsung devices, any one?
Anyone using fastboot with linux?
I only get adb running using debian squeeze and this udev rule:
Code:
#Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="0fce", MODE="0660", OWNER="root", GROUP="androiddev", SYMLINK+="android%n"
So I have to boot windows to flash boot images
Greetz,
scheich
no one???
*push*
Should be in latest sdk?
Compile can be a ***** so grab this
http://www.multiupload.com/91QOOXZHPY
Wow, seems, that my fastboot binary was too old.
Thank You a lot!
dmesg
Code:
[ 843.649189] usb 3-4: new high speed USB device using ehci_hcd and address 7
[ 843.795440] usb 3-4: New USB device found, idVendor=0fce, idProduct=adde
[ 843.795449] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 843.795456] usb 3-4: Product: S1Boot Download
[ 843.795461] usb 3-4: Manufacturer: Sony Ericsson Mobile Communications AB
[ 843.795680] usb 3-4: configuration #1 chosen from 1 choice
[ 884.106276] usb 3-4: USB disconnect, address 7
[ 922.884299] usb 3-4: new high speed USB device using ehci_hcd and address 8
[ 923.029670] usb 3-4: New USB device found, idVendor=0fce, idProduct=0dde
[ 923.029679] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 923.029686] usb 3-4: Product: S1Boot Fastboot
[ 923.029691] usb 3-4: Manufacturer: Sony Ericsson Mobile Communications AB
[ 923.029697] usb 3-4: SerialNumber: BX852J5PT5&ZLI
[ 923.029925] usb 3-4: configuration #1 chosen from 1 choice
fastboot-linux devices
Code:
BX852J5PT5&ZLI fastboot
Okay, so I finally managed to solder a working factory cable, and the ot a response from my Kindle Fire HDX 7" (as far as usb is concerned);
Here is the state my HDX is in: If i hold power for 16 seconds, it will start to boot, show the all grey "kindle fire" logo, then the screen turns off.
If I turn it on with the Volume+ button pressed, I get to stock recovery. No amount of factory reset and rebooting will do any good here.
In both cases above, I will get nothing at all on USB when plugged to a computer. No message about it even being plugged in on dmesg.
When I plug in the factory cable, I get a reponse, but a lot of "new high-speed USB device, device descriptor read/64, error -110".
Now here is the interesting part, when I hold power with the factory cable plugged, the device is recognized! Logs will be at the end.
The problem here is I can't get fastboot to show devices. I tried the following:
fastboot devices
fastboot -i 0x1949 devices
fastboot -i 0x05c6 devices
fastboot -s 0 devices
fastboot -s ttyUSB0 devices
fastboot -s /dev/ttyUSB0 devices
And get nothing. I think I am on the right track to getting it to work again, but I'm at a loss about what to do next.
I'm willing to try anything as long as it doesn't involve screwdrivers and/or snakes!
Here is the log from dmesg:
Code:
[Ter Dez 3 07:47:10 2013] usb 2-1.2: >new high-speed USB device number 39 using ehci_hcd
[Ter Dez 3 07:47:25 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:47:40 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:47:40 2013] usb 2-1.2: >new high-speed USB device number 40 using ehci_hcd
[Ter Dez 3 07:47:55 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:48:10 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:48:11 2013] usb 2-1.2: >new high-speed USB device number 41 using ehci_hcd
[Ter Dez 3 07:48:21 2013] usb 2-1.2: >device not accepting address 41, error -110
[Ter Dez 3 07:48:21 2013] usb 2-1.2: >new high-speed USB device number 42 using ehci_hcd
[Ter Dez 3 07:48:31 2013] usb 2-1.2: >device not accepting address 42, error -110
[Ter Dez 3 07:48:31 2013] hub 2-1:1.0: >unable to enumerate USB device on port 2
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >new high-speed USB device number 43 using ehci_hcd
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >New USB device found, idVendor=05c6, idProduct=9008
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >Product: QHSUSB__BULK
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >Manufacturer: Qualcomm CDMA Technologies MSM
[Ter Dez 3 07:48:42 2013] usbcore: registered new interface driver usbserial
[Ter Dez 3 07:48:42 2013] usbcore: registered new interface driver usbserial_generic
[Ter Dez 3 07:48:42 2013] USB Serial support registered for generic
[Ter Dez 3 07:48:42 2013] usbserial: USB Serial Driver core
[Ter Dez 3 07:48:42 2013] usbcore: registered new interface driver qcserial
[Ter Dez 3 07:48:42 2013] USB Serial support registered for Qualcomm USB modem
[Ter Dez 3 07:48:42 2013] qcserial 2-1.2:1.0: >Qualcomm USB modem converter detected
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >Qualcomm USB modem converter now attached to ttyUSB0
Here is usb-devices and lsusb output, in case it's needed:
Code:
T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 43 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=05c6 ProdID=9008 Rev=00.00
S: Manufacturer=Qualcomm CDMA Technologies MSM
S: Product=QHSUSB__BULK
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial
Code:
Bus 002 Device 051: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9008 Gobi Wireless Modem (QDL mode)
bcdDevice 0.00
iManufacturer 1 Qualcomm CDMA Technologies MSM
iProduct 2 QHSUSB__BULK
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
Thanks!
Moronig said:
Okay, so I finally managed to solder a working factory cable, and the ot a response from my Kindle Fire HDX 7" (as far as usb is concerned);
Here is the state my HDX is in: If i hold power for 16 seconds, it will start to boot, show the all grey "kindle fire" logo, then the screen turns off.
If I turn it on with the Volume+ button pressed, I get to stock recovery. No amount of factory reset and rebooting will do any good here.
In both cases above, I will get nothing at all on USB when plugged to a computer. No message about it even being plugged in on dmesg.
When I plug in the factory cable, I get a reponse, but a lot of "new high-speed USB device, device descriptor read/64, error -110".
Now here is the interesting part, when I hold power with the factory cable plugged, the device is recognized! Logs will be at the end.
The problem here is I can't get fastboot to show devices. I tried the following:
fastboot devices
fastboot -i 0x1949 devices
fastboot -i 0x05c6 devices
fastboot -s 0 devices
fastboot -s ttyUSB0 devices
fastboot -s /dev/ttyUSB0 devices
And get nothing. I think I am on the right track to getting it to work again, but I'm at a loss about what to do next.
I'm willing to try anything as long as it doesn't involve screwdrivers and/or snakes!
Here is the log from dmesg:
Code:
[Ter Dez 3 07:47:10 2013] usb 2-1.2: >new high-speed USB device number 39 using ehci_hcd
[Ter Dez 3 07:47:25 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:47:40 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:47:40 2013] usb 2-1.2: >new high-speed USB device number 40 using ehci_hcd
[Ter Dez 3 07:47:55 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:48:10 2013] usb 2-1.2: >device descriptor read/64, error -110
[Ter Dez 3 07:48:11 2013] usb 2-1.2: >new high-speed USB device number 41 using ehci_hcd
[Ter Dez 3 07:48:21 2013] usb 2-1.2: >device not accepting address 41, error -110
[Ter Dez 3 07:48:21 2013] usb 2-1.2: >new high-speed USB device number 42 using ehci_hcd
[Ter Dez 3 07:48:31 2013] usb 2-1.2: >device not accepting address 42, error -110
[Ter Dez 3 07:48:31 2013] hub 2-1:1.0: >unable to enumerate USB device on port 2
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >new high-speed USB device number 43 using ehci_hcd
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >New USB device found, idVendor=05c6, idProduct=9008
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >Product: QHSUSB__BULK
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >Manufacturer: Qualcomm CDMA Technologies MSM
[Ter Dez 3 07:48:42 2013] usbcore: registered new interface driver usbserial
[Ter Dez 3 07:48:42 2013] usbcore: registered new interface driver usbserial_generic
[Ter Dez 3 07:48:42 2013] USB Serial support registered for generic
[Ter Dez 3 07:48:42 2013] usbserial: USB Serial Driver core
[Ter Dez 3 07:48:42 2013] usbcore: registered new interface driver qcserial
[Ter Dez 3 07:48:42 2013] USB Serial support registered for Qualcomm USB modem
[Ter Dez 3 07:48:42 2013] qcserial 2-1.2:1.0: >Qualcomm USB modem converter detected
[Ter Dez 3 07:48:42 2013] usb 2-1.2: >Qualcomm USB modem converter now attached to ttyUSB0
Here is usb-devices and lsusb output, in case it's needed:
Code:
T: Bus=02 Lev=02 Prnt=02 Port=01 Cnt=02 Dev#= 43 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=05c6 ProdID=9008 Rev=00.00
S: Manufacturer=Qualcomm CDMA Technologies MSM
S: Product=QHSUSB__BULK
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=2mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=qcserial
Code:
Bus 002 Device 051: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9008 Gobi Wireless Modem (QDL mode)
bcdDevice 0.00
iManufacturer 1 Qualcomm CDMA Technologies MSM
iProduct 2 QHSUSB__BULK
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
Thanks!
Click to expand...
Click to collapse
How about adb devices. Is that working. If so that could help. My brick Kindle went totally dead on me. Won't power on at all even plugged in. Not even the grey Kindle shows up.
Sent from my Nexus 5 using Tapatalk
Android Cowboy said:
How about adb devices. Is that working. If so that could help. My brick Kindle went totally dead on me. Won't power on at all even plugged in. Not even the grey Kindle shows up.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Nope, nothing on adb devices either. And my Kindle stopped responding completely. I'm afraid the factory cable burned something, but if yours is dead as well, that could be the battery going dead. Maybe the bootloader won't boot far enought to let the battery charge. Did your stop showing the grey kindle by itself?
Moronig said:
Nope, nothing on adb devices either. And my Kindle stopped responding completely. I'm afraid the factory cable burned something, but if yours is dead as well, that could be the battery going dead. Maybe the bootloader won't boot far enought to let the battery charge. Did your stop showing the grey kindle by itself?
Click to expand...
Click to collapse
Plugged it for 30min and it's turning on again. Being recognized by pc now with fastboot cable.. Testing at the moment.
Sent from my Nexus 5 using Tapatalk
Android Cowboy said:
Plugged it for 30min and it's turning on again. Being recognized by pc now with fastboot cable.. Testing at the moment.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Good news AC!
Keep us posted!
I'm able to get adb recognized but not fastboot. Been searching for fastboot drivers with no luck.
Mine acts like it wants to boot up but then I get fooled and try to unlock it real quick with no luck.
It's teasing me.
Sent from my LG-D800 using XDA Premium 4 mobile app
Android Cowboy said:
Plugged it for 30min and it's turning on again. Being recognized by pc now with fastboot cable.. Testing at the moment.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hi, can you share with us the result of your factory cable rescuse actuions? I've my HDX 8.9 turned brick and is waiting for the cable to come.
doggyxxx said:
Hi, can you share with us the result of your factory cable rescuse actuions? I've my HDX 8.9 turned brick and is waiting for the cable to come.
Click to expand...
Click to collapse
I was not able to recover. But there is another thread in the forum that does show how to get the device to be properly recognized and possible recovery.
Android Cowboy said:
I was not able to recover. But there is another thread in the forum that does show how to get the device to be properly recognized and possible recovery.
Click to expand...
Click to collapse
Do you have idea of what make your kindle become un-recoverable? I've done factory reset after my kindle is bricked. Do you think this would make the recover hopeless?
doggyxxx said:
Do you have idea of what make your kindle become un-recoverable? I've done factory reset after my kindle is bricked. Do you think this would make the recover hopeless?
Click to expand...
Click to collapse
Factory reset was the last thing to do but follow the info on this thread that should help you recover. http://forum.xda-developers.com/showthread.php?t=2575712
Android Cowboy said:
Factory reset was the last thing to do but follow the info on this thread that should help you recover. http://forum.xda-developers.com/showthread.php?t=2575712
Click to expand...
Click to collapse
Thanks. I'll give it a try. Hope it works.
Android Cowboy said:
I was not able to recover. But there is another thread in the forum that does show how to get the device to be properly recognized and possible recovery.
Click to expand...
Click to collapse
Hello
I have been following android cowboy for a long time, got root, custom rom and etc on kindle fire hdx, but now its bricked, can you Please give a link to that thread,
Thanks a LOT.
ferrouskid said:
Hello
I have been following android cowboy for a long time, got root, custom rom and etc on kindle fire hdx, but now its bricked, can you Please give a link to that thread,
Thanks a LOT.
Click to expand...
Click to collapse
Forum.xda-developers.com/showthread.php?t=2588608
Sent from my Nexus 5 using Tapatalk
Android Cowboy said:
Forum.xda-developers.com/showthread.php?t=2588608
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks so much man.
Android Cowboy said:
Plugged it for 30min and it's turning on again. Being recognized by pc now with fastboot cable.. Testing at the moment.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Where did you get the fastboot cable for the kindle fire hdx? I'm having trouble finding one......
Hi,
the display of my galaxy s2 is dead and now I'm trying to recover all my data. If I connect the phone via usb to my pc Windows recognizes it as an usb media but I gain no access. Under Linux it gives me the following error
Code:
Unable to mount Android
Unable to open MTP device '[usb:002,003]'
Dmesg shows the following output
Code:
[ 135.856487] usb 2-1.2: Product: Android
[ 135.856492] usb 2-1.2: Manufacturer: Android
[ 135.856497] usb 2-1.2: SerialNumber: 0019adcd587f8e
[ 136.660306] usb 2-1.2: usbfs: process 2538 (pool) did not claim interface 0 before use
[ 136.730533] usb 2-1.2: reset high-speed USB device number 10 using ehci-pci
[ 136.823484] usb 2-1.2: usbfs: process 2538 (pool) did not claim interface 0 before use
[ 136.839730] usb 2-1.2: USB disconnect, device number 10
[ 137.038544] usb 2-1.2: new high-speed USB device number 11 using ehci-pci
[ 137.139993] usb 2-1.2: New USB device found, idVendor=04e8, idProduct=6860
[ 137.140004] usb 2-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 137.140010] usb 2-1.2: Product: Android
[ 137.140015] usb 2-1.2: Manufacturer: Android
[ 137.140020] usb 2-1.2: SerialNumber: 0019adcd587f8e
lsusb also shows the galaxy s2:
Code:
Bus 002 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]
but the problem is that adb devices -l says it's still offline, so I can't connect..
Code:
List of devices attached
0019adcd587f8e offline usb:2-1.2
Maybe the problem is that my device boots until the PIN screen and I can't unlock it .. but I think it could be even a hardware issue.. Also I have a custom rom + custom kernel installed (it's called ressurection remix)
So is there a chance to connect my device?
EDIT: now, after a few times of trying sometimes the devices connects correctly (Windows says it's an GT9100 and also Kies tries to connect) but I can't access it 'cause I cannot type in my PIN. Also adb now says I have an unauthorized device connected. So if I can change the last point with adb I think I'll gain access to my data.
EDIT2: I've figured out that I can boot into CWM and now adb says the device is connected as recovery. So I can use pull/push commands but the problem is that i cannot see all files.. trying to find a solution now for this one..
EDIT 3 : I'm recovering my data via the help I got here: techglen.
com/2014/01/29/
how-to-recover-data-using-adb-recovery-on-android/
(I'm not allowed to send links..)
SO I think the thread can be closed
SP Flash tool crashed after the first step (red bar, 100%).
Now when I connect it, it appears in Device manager as DA USB VCOM Port (COM5), but SP Flash never detects it (I am on 64-bit Win7), and I can't upgrade or upload firmware.
So how can I get this device alive again ? Screen keeps staying black. Before it showed battery status.
I tried to connect in while running VMWare, connecting all USB to Linux, and all I see is like below. It goes directly to the DA USB Port (Product 2001). So no preloader. So how can I salvage it ?
[ 52.150514] [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
[ 460.866849] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 461.214431] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2001
[ 461.214435] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 461.282544] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
[ 461.285440] usbcore: registered new interface driver cdc_acm
[ 461.285441] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
I recovered my bricked G708
I had the same issue after trying to flash the 1.04 firmware. After a few seconds my SP-flashtool became unresponsive and left me with a bricked (black screen all the way) G708. Tried al kinds of tricks, drivers and tools but neither the flash-tool not the MTK droid tools recognized the thing upon connecting. Ultimately:
1. I pried the thing open (remove the 3 tiny screws near the SIM and TF card slot).
2. Disconnected the battery (on my device it is not soldered on the logic board).
3. Reconnected the battery.
4. Coonected the USB cable with SP-flash running in download mode......success!
I am a happy camper again, hope it will solve your problem.
Beste regards,
EP
I have one that shows colorfly logo and 100% battery when connected to the pc (win7 x86).
What to do now?