Hi there
I bought one of these sticks hoping to get a Linux distro onto it and try it as a plain PC, but am stymied at step 1. I plain cannot get my PC to enumerate the USB connection!
The actual thing I bought seems to run Android OK.
The PCB is blue/green and has CYX_809III on it with v5_0 20140510 under that. Now when I try a USB connection to my PC I get
Code:
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device not accepting address 17, error -62
usb 4-2: device not accepting address 18, error -62
hub 4-0:1.0: unable to enumerate USB device on port 2
And of course lsusb shows nothing new.
I have enabled developer options/USB debugging, I have tried 3 different power supplies, I have tried all 3 USB ports on the stick, I have even tried it into my Raspberry Pi (to sanity check my PC which sees my LG phone fine) and am at a complete loss.
Similarly when I hold the "factory reset" button and plug in a USB cable the stick does a factory image reload (Android picture with rotating thing at stomach) for 3 minutes then reboots - it does not offer any kind of recovery menu.
The only bits from Dr Google I have not tried are shorting pins 8-9 of the NAND (as I cannot find a clear description of what this actually achieves and whether it is relevant to this version) and another post (which I can no longer find, thought it was on XDA but ...) that seemed to have instructions for forcing the USB Vendor and Product IDs somehow ?via modprobe? but apart from the fact I can't find the post I have no idea what the IDs should be.
Any suggestions welcome - TIA
Me and another guy are having the same problem with this device (or actually a CX-919 with the same PCB inside).. We're still looking for a solution.. PM me and I'll send you a link to the thread on another forum.
dukla2000 said:
Hi there
I bought one of these sticks hoping to get a Linux distro onto it and try it as a plain PC, but am stymied at step 1. I plain cannot get my PC to enumerate the USB connection!
The PCB is blue/green and has CYX_809III on it with v5_0 20140510 under that. Now when I try a USB connection to my PC I get
Code:
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device descriptor read/64, error -62
usb 4-2: device not accepting address 17, error -62
usb 4-2: device not accepting address 18, error -62
hub 4-0:1.0: unable to enumerate USB device on port 2
And of course lsusb shows nothing new.
I have enabled developer options/USB debugging, I have tried 3 different power supplies, I have tried all 3 USB ports on the stick, I have even tried it into my Raspberry Pi (to sanity check my PC which sees my LG phone fine) and am at a complete loss.
Similarly when I hold the "factory reset" button and plug in a USB cable the stick does a factory image reload (Android picture with rotating thing at stomach) for 3 minutes then reboots - it does not offer any kind of recovery menu.
The only bits from Dr Google I have not tried are shorting pins 8-9 of the NAND (as I cannot find a clear description of what this actually achieves and whether it is relevant to this version) and another post (which I can no longer find, thought it was on XDA but ...) that seemed to have instructions for forcing the USB Vendor and Product IDs somehow ?via modprobe? but apart from the fact I can't find the post I have no idea what the IDs should be.
Any suggestions welcome - TIA
Click to expand...
Click to collapse
same problems here
Cooler_King said:
Me and another guy are having the same problem with this device (or actually a CX-919 with the same PCB inside).. We're still looking for a solution.. PM me and I'll send you a link to the thread on another forum.
Click to expand...
Click to collapse
same thing here i was just got from ebay member paq999
this is the title i have got
CX919 RK3188 Quad Core Android 4.2 TV BOX 5-in-1 Wireless Control Fly Air Mouse
guess not
Related
I cant use my usb ? Device not recognize when plugged in via usb i have all the necessary drivers installed and they work when i use other htc phones with adb . i have search for days now and all i can find is htc desire "bravo" usb brick fix . which is to push misc version file and flash an image file of some sort . but i cant push anything because i cant use the usb to connect with adb i have managed to find and install a wireless adb but how do i find the misc version for the desire s "saga" and flash_image file to push and flash ? any help with this would be great... thanks in advance...
scaffman said:
I cant use my usb ? Device not recognize when plugged in via usb i have all the necessary drivers installed and they work when i use other htc phones with adb . i have search for days now and all i can find is htc desire "bravo" usb brick fix . which is to push misc version file and flash an image file of some sort . but i cant push anything because i cant use the usb to connect with adb i have managed to find and install a wireless adb but how do i find the misc version for the desire s "saga" and flash_image file to push and flash ? any help with this would be great... thanks in advance...
Click to expand...
Click to collapse
Does you USB work when in fastboot mode?
Also, it would really help if you could boot into Linux on your computer (using e.g. a Fedora live CD) and post a dmesg after plugging in your phone.
no got nothing in fastboot mode .. downloading Fedora live CD now . i don't know how to use linux much . if you could me help with any commands i would need that would be magic . i'm a bit of a noob but smarter than average noob , i can follow instructions lol
R ya s-on or s-off? Do u have recovery? 4ext recovery has a built in usb unbrick option
jmcclue said:
R ya s-on or s-off? Do u have recovery? 4ext recovery has a built in usb unbrick option
Click to expand...
Click to collapse
Hi , my device is S-on with no recovery its stock running 2.3.5 on 2.10.401.8 build . i have been trying to push root files over wireless adb to install recovery but i'm not having much luck atm.
scaffman said:
no got nothing in fastboot mode .. downloading Fedora live CD now . i don't know how to use linux much . if you could me help with any commands i would need that would be magic . i'm a bit of a noob but smarter than average noob , i can follow instructions lol
Click to expand...
Click to collapse
All you need to do is:
plug in your phone when it's booted into Android
open a terminal
type the following: dmesg>logfile
then open up the file manager (or just type: nautilus&) and you'll find a text file named 'logfile' in your home folder, attach that here
Aquous said:
All you need to do is:
plug in your phone when it's booted into Android
open a terminal
type the following: dmesg>logfile
then open up the file manager (or just type: nautilus&) and you'll find a text file named 'logfile' in your home folder, attach that here
Click to expand...
Click to collapse
Hi , i just tried that but terminal gives error message "can't create logfile: read only file system"...
even tho my sd is in the phone ? i've tried changing home folder to /sdcard/data/data/jackpal.androidterm/app_HOME
but i think i've got the sd path name wrong lol this is right pathive found /mnt/sdcard/jackpal.androidterm/app_HOME/ but still get the same error "can't create logfile: read only file system"...
i have installed Anjedi which has lolcat in tools and when i plug in usb i get a log says (1267): Ignoring unknown switch 'usb_mass_storage' in warnings tab and some others sorry i'm tring to find a way to copy this logcat info to show.
scaffman said:
Hi , i just tried that but terminal gives error message "can't create logfile: read only file system"...
even tho my sd is in the phone ? i've tried changing home folder to /sdcard/data/data/jackpal.androidterm/app_HOME
but i think i've got the sd path name wrong lol this is right pathive found /mnt/sdcard/jackpal.androidterm/app_HOME/ but still get the same error "can't create logfile: read only file system"...
i have installed Anjedi which has lolcat in tools and when i plug in usb i get a log says (1267): Ignoring unknown switch 'usb_mass_storage' in warnings tab and some others sorry i'm tring to find a way to copy this logcat info to show.
Click to expand...
Click to collapse
I'm asking for the dmesg from your computer when it's booted into Linux, not for a dmesg from your phone.
Aquous said:
I'm asking for the dmesg from your computer when it's booted into Linux, not for a dmesg from your phone.
Click to expand...
Click to collapse
Hi , sorry lol . yes i got it now . attached . thanks
scaffman said:
Hi , sorry lol . yes i got it now . attached . thanks
Click to expand...
Click to collapse
Yep, that's what I was looking for.
[ 522.472578] usb 3-2: new full-speed USB device number 6 using uhci_hcd
[ 522.596060] usb 3-2: device descriptor read/64, error -71
[ 522.811129] usb 3-2: device descriptor read/64, error -71
[ 523.014066] usb 3-2: new full-speed USB device number 7 using uhci_hcd
[ 523.128032] usb 3-2: device descriptor read/64, error -71
[ 523.342051] usb 3-2: device descriptor read/64, error -71
[ 523.548273] usb 3-2: new full-speed USB device number 8 using uhci_hcd
[ 523.958045] usb 3-2: device not accepting address 8, error -71
[ 524.060049] usb 3-2: new full-speed USB device number 9 using uhci_hcd
[ 524.470046] usb 3-2: device not accepting address 9, error -71
[ 524.470076] hub 3-0:1.0: unable to enumerate USB device on port 2
Click to expand...
Click to collapse
I've had this problem too, and it's a problem with the USB port on your phone. You can try plugging in the cable while holding the phone differently, or pushing the connector slightly up after it's been plugged in, and you can try rebooting your phone, but ultimately this is a hardware problem caused by old age.
Aquous said:
Yep, that's what I was looking for.
I've had this problem too, and it's a problem with the USB port on your phone. You can try plugging in the cable while holding the phone differently, or pushing the connector slightly up after it's been plugged in, and you can try rebooting your phone, but ultimately this is a hardware problem caused by old age.
Click to expand...
Click to collapse
Thanks for your help !!! knowing that the hardware failed i have now installed a new usb flex cable and it works like a charm ive s-offed and about to flash custom roms now so happy days
I am trying Carbon Rom on my Galaxy S2 (version from here. I notice that my USB doesnt seem to work. If i connect to my Linux box, I get
[38662.932040] usb 5-2: new full-speed USB device number 89 using uhci_hcd
[38663.056328] usb 5-2: device descriptor read/64, error -71
[38663.488499] usb 5-2: device descriptor read/64, error -71
[38663.704033] usb 5-2: new full-speed USB device number 90 using uhci_hcd
[38664.112027] usb 5-2: device not accepting address 90, error -71
Continuously. Does anyone know if it is possible to fix? Other than this and some occasional to often reboots, am loving this rom!
p.s. This is the reaction with MTP/Usb storage, Debug On/off
Works now - weird
Its working now.. not sure what happened there.. perhaps the phone was rebooted at some point..
i have a usb to Ethernet adapter 10/100 which cabe with its CD. I hooked it up with my device but no luck. :crying:
could not see eth0 in terminal using netcfg .
after reading some posts about usb to Ethernet on xda , I rooted the phone, ran the makefile provided in the CD. still no luck.
So finally after reading for 2 days, I have options to
Install Ethernet drivers (don't know how)
Install kernel with Ethernet drivers (will change my phone config completely, maybe need to recalibrate later)
Flash a new ROM with Ethernet drivers (will need to reinstall everything)
Don't know the best option. Kinda stuck.
I don't want to loose the current config of cpu speed, etc. provided in the current Android
FYI: The device is detected on the device using usb host controller. Usb to Ethernet Model "Terabyte USB To Lan Card Ethernet Adapter Speed 10/100" found on Amazon. Manufacturer CH9100 Make CH9200. drivers provided has a "ch9x00.c" dunno what to do with it. (I mean after cross compiling).
attached the .c file for refrence.
I have an htc Desire 526G (MT 6582), the phone was working bad, so I found a thread here on XDA about flashing the phone via Fastboot.
I use only Linux, Ubuntu, and I installed ADB and Fastboot. The procedure was OK, but the result was bad, now the phone is bricked.
So, in the same thread, I found a ROM scattered to use with SP Flash Tool and I downloaded Sp Flash Tool for LInux (SP_Flash_Tool_v5.1628_Linux) and Installed the MTK drivers. I suppose that the MTK driver is working because the pc can recognize another identical phone as "MTKXXX device".
Unfortunately the SP Tool is not able to access my phone, this is the output
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1479500736.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
comboTimeout index(3) saved.
To make the "Download" I make a click on the "download" button, the tool start waiting for the connection, so I insert the usb in the phone (in power off), I tried with battery and without battery.
It's strange that I tried the connection hundreds of times, using different USB ports, cables, Full/High speed, with and w/o battery, auto detect mode, different agents and so on, and once (only once) SP tool could connect to the phone, but it said thet PMT was chamged, so I found on the net that I should format the phone, but there were no more successes in connecting.
Could someone help me in fixing this problem?
XDA Visitor said:
I have an htc Desire 526G (MT 6582), the phone was working bad, so I found a thread here on XDA about flashing the phone via Fastboot.
I use only Linux, Ubuntu, and I installed ADB and Fastboot. The procedure was OK, but the result was bad, now the phone is bricked.
So, in the same thread, I found a ROM scattered to use with SP Flash Tool and I downloaded Sp Flash Tool for LInux (SP_Flash_Tool_v5.1628_Linux) and Installed the MTK drivers. I suppose that the MTK driver is working because the pc can recognize another identical phone as "MTKXXX device".
Unfortunately the SP Tool is not able to access my phone, this is the output
Code:
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1
[email protected]/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.1/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1479500736.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
BROM connected
Downloading & Connecting to DA...
connect DA end stage: 2, enable DRAM in 1st DA: 0
COM port is open. Trying to sync with the target...
Failed to Connect DA: S_BROM_DOWNLOAD_DA_FAIL
Disconnect!
BROM Exception! ( BROM ERROR : S_BROM_DOWNLOAD_DA_FAIL (2004)
[H/W] Fail to download DA to baseband chip's internal SRAM!
[HINT]:
1. There's an cable communication problem between FlashTool and BootROM.
2. Target might be shutdown unexpectedly or target lost power supply.
[ACTION]
1. Try again.
2. Proceed H/W checking in download cable and target side com port.
3. Monitor if power-drop occured in target side.)((ConnectDA,../../../flashtool/Conn/Connection.cpp,131))
comboTimeout index(3) saved.
To make the "Download" I make a click on the "download" button, the tool start waiting for the connection, so I insert the usb in the phone (in power off), I tried with battery and without battery.
It's strange that I tried the connection hundreds of times, using different USB ports, cables, Full/High speed, with and w/o battery, auto detect mode, different agents and so on, and once (only once) SP tool could connect to the phone, but it said thet PMT was chamged, so I found on the net that I should format the phone, but there were no more successes in connecting.
Could someone help me in fixing this problem?
Click to expand...
Click to collapse
Hello,
Please register for a XDA account to post and reply in the forum.
Also you might try posting your query here Android Q&A Forum with all relevant details, the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
Hey guys!
I have a rooted Samsung Galaxy S6 G920I.
The problem with this thing is that I had the debug mode disable and I forgot about that.
I started the phone in TWRP and wipe everything to install another OS.
Problem is...Now I can't connect my phone to install the new OS. Windows, Linux or MacOS does not detects the phone.
When I connect my phone to Linux or MacOS it's like I never connected anything. Windows detects the USB connection but says "The last USB device you connected to this computer malfunctioned and Windows does not recognise it.".
In Device Manager appears as "Unknown USB Device (Device Descriptor Request Failed)"
I tried with Samsung USB Drivers, Android SDK, 4 USB different cables, OTG, and nothing.
I see a Terminal in TWRP, so I was wondering if it's possible to enable Debug mode or whatever I need to connect the phone and transfer a new OS.
Thanks in advance!