Is there a way to get a G1 into a diagnostic mode so the Qualcomm modem will show up over USB to a PC. I've tried various USB HTC drivers, including ones which include COM port over USB drivers (namely sync/diagnostic stuff for the Hero) but haven't had any luck getting anything but ADB composite device to show up.
I'm sure I'm getting the drivers to install, as the composite device changes its name depending on where the USB/ADB driver came.
Is there something I am missing here?
Thanks
I'm not steady handed enough to try your ribbon cable approach, though I think for a total investment of about $12 with shipping I can have a full homebrew cable. Much cheaper than the suggested component parts are by themselves.
I will update if the following work, I'm going off of supposition here:
This should be sufficient for getting the ExtUSB connector. Great part in my opinion is it already has wires going to a break out box.
www_amazon_com/HTC-Multifunction-Adapter-T-Mobile-Shadow/dp/B001QD3MQE/ref=lh_ni_t_
For the 3.3v CMOS compliant serial cable, I'm going to try this:
www_amazon_com/Data-Cable-Nokia-3585-CA-42/dp/B000BI4HQY/ref=pd_cp_cps_1
(replace _ in www_amazon_com with .)
Thanks for getting me started down the right road Xsite_01.
I know serial interfacing with most HTC phones isn't a top priority with ADB/ActiveSync (and JTAG for the hardcore), but someone should get Xsite's links added to the Wiki.
Xsite_01 said:
Diagnostic mode is entered from blue led mode using htc extusb to serial cable.
Qualcomm modem will show but with serial cable not regular usb. Here is the link on how to build one. If you need info on how to build it from home parts click here to view my tutorial, or contact me.
You acces serial port using serial cable and putty. Also you can acces the phone using PSAS/QMAT, Link 1, Link 2 for how to do it. But be wery careful accesing this, some command might damage the phone. I suggest that you read more about it before atempting anything.
You should not atempt this with regular usb cable becouse you can send the phone in some boot mode that can only be accessed using serial cable and you will be stuck(until you build serial cable).
Click to expand...
Click to collapse
I would like to communicate with the HTC Dream (G1) using the (qualcomm) diagnostic mode. By this, I mean the one that the QPST/QXDM softwares are using to talk to the baseband (radio). As I understand, it is possible to build the serial to USB cable (using the ExtUSB adapter needed for the G1) to do so. I would really appreciate if someone could confirm that he tested that for this purpose. I tried to build one by myself (using your instructables tutorial, great by the way, thanks Xsite_01 !) but did not managed to use it in diagnostic mode (neither in other mode actually, I may have broken some part of the chips so I would need to double check what I did and/or rebuy components to try again. The procedure is not difficult by itself, it is just the soldering pins that are really small...).
What I tried is to go to fastboot mode (default bootloader mode for the G1), issue the "fastboot oem rtask c" command (using the HTC standard USB cable). The command never returns so I disconnected it and plugged the serial cable (the one I made) but I did not see any diagnostic mode.
To compare, I managed to use the diagnostic mode on the HTC Desire Z using the following procedure:
* issue the "fastboot oem rtask c". The command returns an error but it is ok, it is because it gave the handling of the USB content to AT interpreter of the baseband
* issue the AT$QCDMG command to the AT interpreter of the baseband. You now get the diagnostic mode.
If someone has some hints, don't hesitate. I will come back as soon as it is working...
Related
Hi,
I'm trying to run an app on the Kaiser phone, but unfortunately it does not recognize phones unless they are configured as serial devices. Is there a way to configure the USB port on the Kaiser as a serial communication port? I tried punching in ##3424# but was unsuccessful. I also could not find a flag in the registry that allowed use of USB as a serial bus. Does any of you have the drivers that allows mapping the USB as a serial port in my computer?
Thank you,
SJ
Last time i checked
USB!=Serial
If you are trying to use the phone as a serial modem, then there are existing drivers for the HTC Modem.
Got it to connect as a serial modem
Hi,
I made some progress in this front. I got my Vista computer to recognize my phone as a HTC USB modem.
But when I start the wModem using Menu > Start and then on Vista goto Start > Connect to > HTC USB Modem it drops the WModem connection on the Kaiser. The Wmodem application closes and reappears after Vista has determined it is unable to connect to the modem.
Has anyone else seen this problem.
Thanks,
Shree
format C: and install XP should do the trick
usb cant emulate old serial == rs232 that few new pc's even have anymore
a usb to rs232 adaptor is required but those require the device using them
being able to be usb host and only flame and Athena support that
I was wondering if anyone has had luck compiling the kernel to support. I was thinking about doing this so so I could connect some serial devices to my phone, but I just wanted to see if anyone all ready has yet.
drock3260 said:
I was wondering if anyone has had luck compiling the kernel to support. I was thinking about doing this so so I could connect some serial devices to my phone, but I just wanted to see if anyone all ready has yet.
Click to expand...
Click to collapse
are you talking about usb host mode or something else? this is chipset support but no drivers for usb host.
most htc devices actually can run a serial mode where the data +- for the usb can be run as txd/rxd. You have to recompile the kernel with usb disabled and serial support enabled, but then you can connect serial devices that run at 3.3volts. I downloaded the serial app and it shows a hardware port on the vogue so I just assumed it supported this, but I could be wrong.
drock3260 said:
most htc devices actually can run a serial mode where the data +- for the usb can be run as txd/rxd. You have to recompile the kernel with usb disabled and serial support enabled, but then you can connect serial devices that run at 3.3volts. I downloaded the serial app and it shows a hardware port on the vogue so I just assumed it supported this, but I could be wrong.
Click to expand...
Click to collapse
i guess that figures - when you go into bootloader it starts in serial mode... haven't really looked into this. Have you looked at the kernel git?
http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
no I have not, but that seems like a good place to start. Thanks
edit: looks like most things are for bluetooth serial connections
edit2: looks like the kernel was built the way it should have been, but it only shows ttymsm0 which i think is for the bluetooth
So for 3 days now i have been reading thread after thread on xda. i cant seem to connect my phone to my computer. Every time i come across a new link to drivers i try it but still no dice.
What happens:
Install Drivers
Phone set to mass storage
plug usb in
mount sd
windows thinks...
USB Device not recognized
Phone: Captivate, stock everything (with ota update)
OS: Windows 7 64 bit
What am i doing or not doing?
I apologize in advance if i have not stumble across thread where this has already been answered.
hacklerg said:
So for 3 days now i have been reading thread after thread on xda. i cant seem to connect my phone to my computer. Every time i come across a new link to drivers i try it but still no dice.
What happens:
Install Drivers
Phone set to mass storage
plug usb in
mount sd
windows thinks...
USB Device not recognized
Phone: Captivate, stock everything (with ota update)
OS: Windows 7 64 bit
What am i doing or not doing?
I apologize in advance if i have not stumble across thread where this has already been answered.
Click to expand...
Click to collapse
Try uninstalling all the drivers and try one again using x64 (I know you probably did it already, but just confirming).
Maybe try doing a factory reset?
So i uninstalled the drivers using the uninstaller application that came with the download then i deleted the files off the computer.
went to the captivate wiki on xda, downloaded the 64 bit drivers from that link (look exactly the same as the other links), then ran the installer application from that download.
what happened was at the end of the install wizard it said that: "mss install wizard was not completed... install wizard was not succesfully installed samsung usb driver for mobile phones.".
I did however notice that at one point in the wizad it called the driver x86 instea of x64.
i would be lieing if i didnt say i hated samsung right now. o yea and i think at&t too. ha ha
Thanks for the help! : )
so in addition to hours spent on other days, im about 5 hours into trying to make the phone connect today.
it seems worse now, it only sometimes sees a device it cant recognize.
i tried more batches of driver uninstall/installs and i even downloaded the full kies.
nothing seems to make it go. im about to lob this thing across the room. any other suggestions or people with a similar problem?
any help would be much appreciated.
1) Scrub your system again of all Samsung drivers.
2) Go to Samsung Software & Firmware Downloads and get the Mini Kies program.
3) Install Mini Kies, this will install drivers.
4) Set USB settings on phone to ask on connection, Settings>Applications>USB Settings>Ask on Connection
5) Connect phone to computer
6) Select Mass Storage when the phone asks
7) Mount phone to computer, depends on which ROM you are running
8) Report back,
I'm running Windows 7 x64 Home Premium and have no troubles connecting. Hope this helps.
ok thanks for the tips.
Here's what i did:
Download mini kies from the link (i noticed that there were driver there to but i did not download that link)
Set phone to ask on connection
plug phone into computer
set to mass storage.
mount sd card
computer says "usb device not recognzed"
Mini Kies still says "please connect mobile phone"
i scream!
what do you suggest i do from here?
hacklerg said:
ok thanks for the tips.
Here's what i did:
Download mini kies from the link (i noticed that there were driver there to but i did not download that link)
Set phone to ask on connection
plug phone into computer
set to mass storage.
mount sd card
computer says "usb device not recognzed"
Mini Kies still says "please connect mobile phone"
i scream!
what do you suggest i do from here?
Click to expand...
Click to collapse
Have you tried a rear USB port instead of a front? I don't know why but many have claimed this was the trick. It should not work, but for some reason it does for some.
alphadog00 said:
Have you tried a rear USB port instead of a front? I don't know why but many have claimed this was the trick. It should not work, but for some reason it does for some.
Click to expand...
Click to collapse
The usb ports on the back of the computer are usually connected directly to the motherboard. The usb ports located other places on the computer are usually connected to the mother board via a secondary card of some type - this adds another level of hardware and software drivers required to make those ports work. Also it is not unusual for some usb to operate at different power levels - often referred to as powered and non powered ports.
So not all ports are the same which is why some people have different results on different ports on their computer.
One other option that sometimes works: turn on usb debugging in settings/applications/development. Then connect the usb. Pull down the notification window and select the button that says something like "select to copy files...". This brings up a dialogue box asking to mount the phone, and you select that.
Sent from my SAMSUNG-SGH-I897 using XDA App
alright i tried
every single usb port (it a laptop btw sorry should of said that earlier)
and also with and without debugging
computer still says usb device not recognized.
is there any more info that anyone needs? Tried hooking the phone up to a mac also (snow leopard osx laptop) no luck still.
dayv said:
The usb ports on the back of the computer are usually connected directly to the motherboard. The usb ports located other places on the computer are usually connected to the mother board via a secondary card of some type - this adds another level of hardware and software drivers required to make those ports work. Also it is not unusual for some usb to operate at different power levels - often referred to as powered and non powered ports.
So not all ports are the same which is why some people have different results on different ports on their computer.
Click to expand...
Click to collapse
I have built many machines and never had a device work on one USB port and not on another.
All my USB devices that require power, require an actual AC adapter -As for unpowered ports - never heard of that. Powered and unpowered hubs yes - but not unpowered ports.
alphadog00 said:
I have built many machines and never had a device work on one USB port and not on another.
All my USB devices that require power, require an actual AC adapter -As for unpowered ports - never heard of that. Powered and unpowered hubs yes - but not unpowered ports.
Click to expand...
Click to collapse
First, just to make this clear all usb ports are powered, and so long as they are in compliance with the usb standard they are powered to 5v.
Second, what you referring to with powered/non powered usb hubs is a usb hub that has a secondary power source (ie includes ac power cable maybe) vs a usb hub that is only powered by the usb serial bus via the usb connecter to the computer.
What was referring to in powered/non powered usb port is a technology included in some ports that allows that port to use the power of two usb ports in one port - not sure but I believe it is an ibm technology - which is some times referred to slangly and inaccurately as powered usb
Now the point of my post was to point out even though there is a universal standard for usb - depending on how these ports are actually connected to the serial bus on the mother board will affect they way they perform - ie usb on the back of the computer that is mounted directly to the mother board serial bus vs one connected via a pci card.
And even though you have never experienced differing performance in your usb ports does not mean that it doesn't happen - it is actually quite common particularly with devices that both connect via usb as well as charge its battery via usb.
I currently have a computer with 7 usb ports all of which will connect and work with my wife's ipod - but I have found two of these ports that will not charge her ipod. most likely this failure to charge her ipod is due to the hardware (or the software driver for the said hardware) in between these two ports and the mother board.
In all of the computers you have built have you built any that had usb ports mounted directly on the mother board serial bus that you also connected a usb pci card to allow for more usb ports? I guarantee you if you do this often enough you wil eventually build a computer that has usb ports with differing performance.
while the info on usb is nice : ) i would very much appreciate any help on gettingmy phone connected. thanks!
hacklerg said:
while the info on usb is nice : ) i would very much appreciate any help on gettingmy phone connected. thanks!
Click to expand...
Click to collapse
I'm guessing by now you have tried all your ports, lol. have you tested your phone on other computers and/or with other usb cables?
One thing to try is check and see if there are any driver updates for the usb hardware in your computer. You can usually find these updates with the computer vendor and/or mother board manufacturer support.
Sorry I missed your post earlier about connecting to a mac - when you connected to the mac was your phone in debugging mode?
I don't know if it is necessary to connect to a mac, but to get some linux distros to mount the drives in cappi it has to be in debugging mode and while linux and NEXTstep are different they are in the same family, have the same ancestor. maybe if someone with a mac read s this they can let us know if it is needed.
If you keep connecting to different computer with no luck, try a different usb cable.
Actually its connecting to a pc. I just tried to connect to a mac wouldn't work there either.
But I've tried all the different combos of debugging and mass storage options it just says it doesn't recognize the usb device.
I have tried a bunch of different drivers and using both kies and mini kies.
Windows 7 64 bit
Laptop
Captivate (stock everything)
Sent from my SAMSUNG-SGH-I897 using XDA App
hacklerg said:
Actually its connecting to a pc. I just tried to connect to a mac wouldn't work there either.
But I've tried all the different combos of debugging and mass storage options it just says it doesn't recognize the usb device.
I have tried a bunch of different drivers and using both kies and mini kies.
Windows 7 64 bit
Laptop
Captivate (stock everything)
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
getting unrecognized usb device is almost certainly a driver issue - what ever kept it from working with the mac is something else.
have you downloaded and installed the drivers dg has linked in his odin 3 one click thread?
Second have you had a chance to check if your computer had any usb driver updates? One of my machines would not properly identify my phone that I tried reinstalling drivers on and I found there was and update for the mother board usb controller - after updating it instantly recognized it.
I am having the same issue with an added twist, which is that some USB ports will rapidly disconnection/reconnect the device to windows even though I havent unplugged it.
I have/had adb working on both my old laptop, and desktop. And like the OP I have spent many hours trying to get this to work. Very frustrating.
Current Scenario:
Phone is stuck at AT&T screen. Can get to download mode. XP cannot installing drivers.
Questions:
Has anyone encountered anything like this? I know some people report issue with some data cables not being able to connect. But I am surprised I can get to download mode with it so am questioning if the cable could be the issue. Could it be a bad port? Since my original cable has gone bad could it have messed up my port? I saw a posts about this but no follow up.
Notes:
Cognition 2.3b6
USB Drivers from (http://forum.xda-developers.com/showthread.php?t=731989) I've obviously have been able to connect prior to these issues to upgrade my ROM.
Kies and Kies Mini were previously installed. I since deleted since having these issues.
Uninstalled iTunes as suggested in other posts.
History:
My phone is stuck at the AT&T boot screen. Using my original Samsung cable I could not get my phone into download mode. So I went out and made the jig to get it into download mode. This worked but win XP won't recognize the phone once I put my original cable in. I realized that my original cable might be internally frayed, so I went out and bought a generic USB cable. Now I can get my phone into download mode (without using the jig) which shows that my original cable has been damaged at some point. This would also explain that when my phone is off and I plugged it in using the old cable the phone would turn on.
Anyway, using this new generic cable, XP/ODIN won't recognize my phone. When trying to put it in download mode (two button/insert cable/no SIM/no SD), I see XP popup: Found New Hardware, USB device, Samsung USB Composite Device, USB device, Samsung USB Composite Device, then get the Found New Hardware Wizard with message Cannot Install the Hardware, problem installing this hardware: USB Device.
Thanks in advance.
Oh and not sure if it matters but I cannot get into recover mode either. Cannot get past AT&T boot screen.
Um... make sure you remove all traces of the Kies stuff.
Re-install USB drivers over the top of the existing ones.
I might suggest buying a "sumsung" cable from an AT&T dealer.
AND - make sure your using the USB port that is on your mobo - apparently it makes a difference.
I had my phone in a "bricked" state and had to re-install drivers on my Win7 box. it found the phone and recognized it enough for ODIN to start up.
Also.... to find out if the phone is being recognized - I would recommend d/l'ing the Android SDK and doing the ADB command - adb devices and see what pops up.
Heh - last thing.. please say you had the phone in "USB Debugging" mode before things went south?
Here's a link to a thread containing another variant of the Captivate USB Drivers:
http://androidforums.com/captivate-.../123644-captivate-usb-drivers-links-here.html
I can't remember which I used, but if the above suggestions don't work for you, it won't hurt to try these!
And for what it's worth, I don't believe the problem to be within the USB cable. I use everything EXCEPT the Samsung USB cable. Anything from Monoprice.com cables, to my old Blackberry cable... A MicroUSB cable is just that...generic or not. As long as it's a 5 pin cable, you should be good.
@avgjoegeek
avgjoegeek said:
Um... make sure you remove all traces of the Kies stuff.
Click to expand...
Click to collapse
Uninstalled and deleted program files/samsung/kies*. Would I need to look through registry as well?
Re-install USB drivers over the top of the existing ones.
Click to expand...
Click to collapse
Done. Multiple times. Even tried drivers from Samsung support site. Currently I'm using the ones from the Stock ODIN thread. (Uninstalled all. Rebooted. Installed drivers from ODIN thread. Rebooted.)
I might suggest buying a "sumsung" cable from an AT&T dealer
Click to expand...
Click to collapse
Called AT&T said they didn't carry any data/sync USB cables. Which I found was odd. Have one coming from Amazon soon that looks-like and is listed to be OEM.
AND - make sure your using the USB port that is on your mobo - apparently it makes a difference.
Click to expand...
Click to collapse
Tried all of them.
I had my phone in a "bricked" state and had to re-install drivers on my Win7 box. it found the phone and recognized it enough for ODIN to start up.
Also.... to find out if the phone is being recognized - I would recommend d/l'ing the Android SDK and doing the ADB command - adb devices and see what pops up.
Click to expand...
Click to collapse
Returns: List of devices attached (nothing else)
Heh - last thing.. please say you had the phone in "USB Debugging" mode before things went south?
Click to expand...
Click to collapse
Upgraded to Cog v2.3b6 before things went south. I normally keep USB Debugging mode as defaulted. Wondering if the update would have caused it to be unchecked. I think I checked that once and rarely make changes. Either way, are you suggesting that if that option is not set that I am pretty much hosed?
@norcal einstein: I will have to try your suggestion from a new machine. My work just locked (McAfee) our machines due to virus going around.
Hi there ... I've run into this similar problem before.. The link you posted's instructions:
"plug usb then open odin"
NO!!!!
#1 odin oneclick must be open before you connect your phone. (and i didnt see in previous posts that you did this?)
Here's the rest....
From a soft-bricked state the Samsung I897 displays a "gadget" screen involving
icons of a phone + exclamation + computer. It is still possible to boot into download mode from this point (which is before the att logo) there your phone can.
Apparently you've been able to get into download mode .
When my phone was soft-bricked and I finally figured out how to put it in download mode I got the "gadget serial device driver not found" bs. I had already opened odin-oneclick and it said "added". So I tried and it worked.
There is no better source for drivers than the manufacturer. So i suggest using those drivers instead. Also the usb port on a captivate IS a generic usb plug.... it's just offset to the side a little bit to add STYLE.
Thanks to everyone that replied. I just want to provide a my resolution for others that might be search for similar issues.
My Captivate is now back up and running. Loaded with Cog2.3b6.
The generic cable proved not to be the issue. I know some people reported having issues with cables but I believe as long as the cable is labeled to be a sync or data cable you should be fine. Avoid the charger cables as it will be just that - a charger cable only.
The jig worked like a charm to get to download mode. Just connect the two leads (4 and 5; closest to the center of the phone) using 301k resistors worked. I used 3x100k and 1x1k. Although, I later learned that my OEM cable went bad on me and just getting a new cable I can get into download mode fine. If some of you are having issues might want to consider keeping a extra cable just to rule out cable issues before trying out the jig. The jig IS very easy to do but finding a micro-b USB plug or adapter that gives easy access to the 4 and 5 leads might be hard.
Out of ideas what was wrong (being stuck at AT&T boot screen, being able to get to download mode, my laptop not being able to detect my phone) I borrowed a laptop running Vista. This worked! Vista and ODIN detected my phone and I was able to get back to stock.
So still not sure what's wrong with MY laptop. Hoping to get it resolved by the time they get the AT&T Froyo update out. But I am very much guessing our tech department tightening up McAfee restrictions (like being able to download exe(cutables) might be the culprit. I will have them remove the restrictions so I can re-install the USB drivers and see if that works.
If you are looking for instructions for how to get download / ODIN working, all the instructions from all the many threads work. I will not repeat those instructions here. But a couple notes: I didn't find any difference with leaving SIM card in or out. Might be best to just leave it out. I've tried both inserting cable last and inserting battery last. Both ways works. So if you can't get one way working chances are you probably won't be able to get it working the other way either. I personally use the battery first, both volume buttons then cable. Once I had to wait 10 mins before getting it to work. That was probably once in about 10 times I've done download mode.
And BIKERBOY8989 is correct, if you can get to the AT&T boot screen chances are you SHOULD be able to get into download mode. Might want to check cables and/or try on another machine. As I mentioned already.
Good luck!!!
Hello,
few days ago I've got my USB OTG cable. So, when I connected this OTG cable to my USB HUB through USB cable with 2 sides of type A port (pic here : http://www.cyfronika.com.pl/art93/kab120aa-l.jpg) to get power on HUB from USB port charger but nothing happened on phone with flash storage, any notifications or something. Then, when I wanted to transfer some files from my computer to sdcard. I've connected USB cable but Windows 7(32-bit) says that my device can be damaged or something (code 43). I've searched about this and found this http://pcsupport.about.com/od/errorc/a/code-43-error.htm . I've used http://forum.xda-developers.com/showthread.php?p=21503469 for setting up the OTG and for kernel too.
Well, I've followed this tutorial but the error still appears. Tried on 3 computers with different cables and different USB ports.
So just tell me if it's software problem or I must do something with this.
LOGCAT : http://pastebin.com/gbqqDxay
LOGCAT_radio : http://pastebin.com/H4dU9JWX
dmesg : http://pastebin.com/tkicx7xb
Logs has been taken after USB cable connecting.
Thanks
(bump) can anyone help me?
(bump again)
(bumpin' like a crazy) Please, anyone have solution for this problem?
So the general idea is, you're trying to let your phone connect to other hardware while the phone is the host, right?
Now you're trying to connect your computer to your phone again normally and it's not working? (normal usb cable)
For one, there are a bunch of errors in the log you posted, thinks like
Code:
W/PackageManager( 353): Unknown permission android.permission.ACCESS_SUPERUSER in package hu.sztupy.android.usbhostcontroller
That might be a problem, I don't know. Perhaps you're better off asking the dev of this mod about these errors. Maybe there's something you forgot or wasn't mentioned in your guide that causes these?
Have you also considered the possibility your phone is now *always* trying to be the host (which is not going to be something a pc likes)? You're saying you can't properly connect with your pc any more, but can you connect with another device (usb stick for example)?
Marshian said:
So the general idea is, you're trying to let your phone connect to other hardware while the phone is the host, right?
Click to expand...
Click to collapse
Yes, It was the general idea when I've bought OTG cable.
Marshian said:
Now you're trying to connect your computer to your phone again normally and it's not working? (normal usb cable)
Click to expand...
Click to collapse
Yes, tried with 2 Nokia cables and one stock from Samsung. Windows is always showing code 43 ;/
Marshian said:
That might be a problem, I don't know. Perhaps you're better off asking the dev of this mod about these errors. Maybe there's something you forgot or wasn't mentioned in your guide that causes these?
Click to expand...
Click to collapse
Well, I'll try to contact with @sztupy (http://forum.xda-developers.com/showthread.php?t=1468531). Anyways I think I haven't forgotten what I wanted to write.
Mashian said:
Have you also considered the possibility your phone is now *always* trying to be the host (which is not going to be something a pc likes)? You're saying you can't properly connect with your pc any more, but can you connect with another device (usb stick for example)?
Click to expand...
Click to collapse
I've set default settings for USB Host Controller app. But no, I can't connect another device. I'm in half way to download Linux, maybe on it everything will be working properly.
Anyway thanks for your reply, let's see if it will be working on Linux ;f
//EDIT : Same problem on Linux. Device is not recognized.
(bump) Any ideas?
(bump)
ADDED MORE LOGS.