Database Develop

Problem tethering to Ubuntu with galaxy s (2.3.3 XXJVK)

hi all guys.
i got some problems with tethering after flashing my galaxy i9000 with XXJVK ROM. i have ubuntu 10.10 and i could use the usb tethering with the XXJPK but now my pc don't recognize any hardware, how can i fix this? please help me
(sorry 4 my bad english)

this is not a common problem, right?

nxz said:
hi all guys.
i got some problems with tethering after flashing my galaxy i9000 with XXJVK ROM. i have ubuntu 10.10 and i could use the usb tethering with the XXJPK but now my pc don't recognize any hardware, how can i fix this? please help me
(sorry 4 my bad english)
Click to expand...
Click to collapse
Hi,
Try that:
Menu -> Settings -> Applications -> Development and enable USB Debugging.
GL.

i tried to turn on the usb debugging but nothing happened.
what's wrong?
Sent from my GT-I9000 using XDA App

anyone who can solve my problem please?
Sent from my GT-I9000 using XDA App

some help please
Sent from my GT-I9000 using XDA App

bump :/
Sent from my GT-I9000 using XDA App

any solution?
Sent from my GT-I9000 using XDA App

ttf said:
Hi,
Try that:
Menu -> Settings -> Applications -> Development and enable USB Debugging.
GL.
Click to expand...
Click to collapse
I've got the same problem. Please help
Ubuntu 10.10
dmesg:
[ 5434.221792] usb 2-2: USB disconnect, address 9
[ 5434.516279] usb 2-2: new high speed USB device using ehci_hcd and address 12
[ 5434.656675] usb 2-2: bad CDC descriptors
[ 5434.656724] usb 2-2: bad CDC descriptors
[ 5442.977365] usb 2-2: USB disconnect, address 12
[ 5443.280027] usb 2-2: new high speed USB device using ehci_hcd and address 13
[ 5443.420988] cdc_acm 2-2:1.0: This device cannot do calls on its own. It is not a modem.
[ 5443.421107] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
[ 5443.427284] scsi19 : usb-storage 2-2:1.2
[ 5444.424718] scsi 19:0:0:0: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
[ 5444.425080] scsi 19:0:0:1: Direct-Access Android UMS Composite 0001 PQ: 0 ANSI: 2
[ 5444.425567] sd 19:0:0:0: Attached scsi generic sg1 type 0
[ 5444.425816] sd 19:0:0:1: Attached scsi generic sg2 type 0
[ 5444.431057] sd 19:0:0:0: [sdb] Attached SCSI removable disk
[ 5444.431802] sd 19:0:0:1: [sdc] Attached SCSI removable disk
[ 5453.498774] usb 2-2: USB disconnect, address 13
[ 5453.788031] usb 2-2: new high speed USB device using ehci_hcd and address 14
[ 5453.928931] usb 2-2: bad CDC descriptors
[ 5453.929002] usb 2-2: bad CDC descriptors

I tethered on Windows 7 64-bit just to make sure tethering is working in JVK (Darky's v10 RC3).
But like you, I cannot seem to tether using Ubuntu 10.
I remember Ubuntu could automatically detect the connection in FroYo (Darky's v9.x)
Now I is telling me to setup Mobile Broadband Connection. Doesn't work when I use default values.
Maybe it can't find drivers for Samsung's Gingerbread? After all, it's not official.
Try Mobile AP for now?
Or go back to FroYo if you must have tethering.

Working on Windows 7.. right
but it's bug-reporting and should be worked on till next release
Of course i can go back to Froyo.. i can buy a umts-stick too or pay a DSL für Cable! THATS NO SOLUTION for this problem. Thanks anyways

nxz said:
any solution?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Having the same issues. No solution as yet.

Same problem here with stock 2.3.3. The problem is present running Ubuntu 11.04, Debian Stable, OpenSUSE 11.4 and I'm sure several others as well.

Having the same issue with Darky v10 RC6
Wifi-tethering works (also while plugged) so not that big a deal
Tried it on ubuntu 10.04 and 11.04.

It is a big deal, since WiFi tethering munches the battery. So, bumping.

Was anyone able to resolve this - usb tether or storage connect gb version to ubuntu since Froyo worked fine
Sent from my GT-I9000 using XDA App

Same problem here.
Upgraded from stock Samsung to Darky's ROM 10.1 today, and my Fedora 14 installation says the same thing. Using WiFi-tethering as of now, but that's not the solution.

Bump; same problem. Ubuntu 11.04. Any temporary fix or anything?
Running 2.3.4 (JVQ) on AT&T Captivate. USB tethering works fine with Windows.

Just upgraded from 2.2 to stock 2.3 (XXJVO) using kies only to find that usb tethering is not working with archlinux. I wouldn't complain as much if I had my home broadband working, but i9000 was my only gateway to the www for the last couple of weeks and now it's gone. I'm yet to find any solution but in the meantime all we can do is complain to samsung and/or downgrade.

I am writing this usb tethered jJVQ 2.3.4 on Ubuntu 11.04
I got the solution here:
http://technomagus.wordpress.com/mobile/tethering/samsung-galaxy-s-i9000-as-3g-modem/
It uses wvdial and after setup is simple enough to get going
However, after some thinking and testing, I found out the solution which will get a working Internet connection. When you connect USB cable, Ubuntu recognizes Galaxy S as modem (dev/ttyACM0) and everything is okay. If you now activate USB tethering on Galaxy S, then USB connection is screwed. So, if you do not activate USB tethering from the menus, then you can use wvdial to connect to Net.
Install wvdial
> sudo apt-get install wvdial
and then connect Galaxy S with USB cable. Use wvdialconf to autodetect Galaxy S modem.
> wvdialconf
This generates configuration file /etc/wvdial.conf. You have to edit it a little, and certain things depend on your ISP, so I cannot give a file which works for everyone. This is just an example for Saunalahti.
[Dialer Defaults]
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Init4 = AT+CSQ
Init5 = AT+CGDCONT=1,"IP","internet.saunalahti"
Phone = *99#
Modem Type = USB Modem
Stupid Mode = 1
New PPPD = yes
Dial Command = ATDT
Modem = /dev/ttyACM0
ISDN = 0
Password =internet
Username =internet

[Q] can someone tell me how to connect my phone to linux.. Kubuntu 12.04

since i updated to JB i seem to have lost the USB connection..
i dont see a way to hook my phone to the computer and see the files as a drive?
anyone?

aarons6 said:
since i updated to JB i seem to have lost the USB connection..
i dont see a way to hook my phone to the computer and see the files as a drive?
anyone?
Click to expand...
Click to collapse
On mine, set the phone as a camera and it worked. (12.04)

its not working no matter how i connect it.. with mtp i see a device but it has only the motoroladevicemanagersetup.exe in it

aarons6 said:
its not working no matter how i connect it.. with mtp i see a device but it has only the motoroladevicemanagersetup.exe in it
Click to expand...
Click to collapse
Ubuntu 12.04 here
phone is on, I connect the usb wire
- it connect as a media device (MTP)
- open the upper status bar to see the usb notification
- you touch the notification to open it.
- you chose Camera (PTP)
- and there, you have both "drive" mounted in file manager.
you're welcome.

yeah but its not working. it mounts the phone as camera: and there is 2 folders..
mass storage camera and usb ptp class camera
both empty
trying to connect it with mtp-tools i get this
libmtp version: 1.1.3
Listing raw device(s)
Device 0 (VID=22b8 and PID=2e33) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
22b8:2e33 @ bus 1, dev 56
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
usb_open(): No such device
LIBMTP PANIC: Could not init USB on second attempt
Unable to open raw device 0
OK.

aarons6 said:
yeah but its not working. it mounts the phone as camera: and there is 2 folders..
mass storage camera and usb ptp class camera
Click to expand...
Click to collapse
well, on my stock ubuntu 12.04 LTS and my Atrix HD rooted on ICS then updated to JB (and not rerooted),
when I switch to camera, I get 2 mounted drives, one with the external SD and one with the internal memory.
Using the stock file manager under ubuntu.

[Q] Kindle fire HD 7" not recognised as an MTP device anymore

I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.
Feb 13 15:01:05 kernel: [ 161.419037] usb 1-5: new high speed USB device using ehci_hcd and address 5
Feb 13 15:01:05 kernel: [ 161.533760] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:05 kernel: [ 161.533767] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:05 kernel: [ 161.533772] usb 1-5: Product: OMAP4440
Feb 13 15:01:05 kernel: [ 161.533775] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:05 mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:05 mtp-probe: bus: 1, device: 5 was not an MTP device
Feb 13 15:01:08 kernel: [ 164.534204] usb 1-5: USB disconnect, address 5
Feb 13 15:01:08 kernel: [ 165.305041] usb 1-5: new high speed USB device using ehci_hcd and address 6
Feb 13 15:01:09 kernel: [ 165.419856] usb 1-5: New USB device found, idVendor=0451, idProduct=d010
Feb 13 15:01:09 kernel: [ 165.419863] usb 1-5: New USB device strings: Mfr=33, Product=37, SerialNumber=0
Feb 13 15:01:09 kernel: [ 165.419868] usb 1-5: Product: OMAP4440
Feb 13 15:01:09 kernel: [ 165.419871] usb 1-5: Manufacturer: Texas Instruments
Feb 13 15:01:09 mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5"
Feb 13 15:01:09 mtp-probe: bus: 1, device: 6 was not an MTP device
Feb 13 15:01:12 kernel: [ 168.420300] usb 1-5: USB disconnect, address 6`
Click to expand...
Click to collapse
This repeats ad infinitum, well at least 30 times I unplugged it after that.
My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??
Any help would be much appreciated.

JBDegriz said:
I have a Kinde fire HD 7" that I rooted for a neighbours son which he managed to brick within 20 Mins of getting it back, I think the battery died on him when he was installing something. Now when I plug the Kindle into my system which runs Linux I get the following in the logs.
This repeats ad infinitum, well at least 30 times I unplugged it after that.
My question is this, will I be able to to restore the Kindle using the Factory cable from SkOrPn or is this a case where I need to send it back to Amazon ??
Any help would be much appreciated.
Click to expand...
Click to collapse
Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..

lacoursiere18 said:
Is the device still able to comunicate with ADB? If it can then you do not need a fastboot cable. If it does not then yes you will need one to restore it..
Click to expand...
Click to collapse
No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.
So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.
Thanks

JBDegriz said:
No ADB never sees the device any more as the USB just keeps reconnecting and disconnecting. The same thing happens in windows where I keep getting the sound when you connect a usb device over and over again and windows looks for a device driver for an OMAP4440, which I believe is the CPU in the Kindle.
So I need to know that in a situation like this that the Factory cable would actually help, I'm sure I read somewhere that fastboot mode needs a working bootloader and I'm not sure that this kindles bootloader is still there.
Thanks
Click to expand...
Click to collapse
Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..

Hi, I have the same problem, did you manage to cure it with the skorn cable, I am asking because I have made a factory cable myself but its giving the same problem.
lacoursiere18 said:
Yea it doesn't sound like it's in working order, so yes, a fastboot cable would be need to get the device back in action..
Click to expand...
Click to collapse

devilxmax said:
Hi, I have the same problem, did you manage to cure it with the skorn cable, I am asking because I have made a factory cable myself but its giving the same problem.
Click to expand...
Click to collapse
No I'm afraid not. If your device is being recognised as an OMAP4440 then your out of luck as there are no drivers for this yet. I had to send my device back to Amazon who replaced it no questions asked.
A good thread to check is http://forum.xda-developers.com/showthread.php?t=2096888 post a few details of your problem on that thread and you will get a helpful response.
Good luck

[Q] Broken HTC First - Any way to fix it?

Hello,
right next to me I have an HTC First which seems broken. It's my father's phone, and he is terrible at really telling what happened, so I will spare you the details, except that he was - the last time the device actually worked - maybe downloading some navigation app from a website (http://www.viamichelin.de/).
The First doesn't turn on any more, when you connect a charging or a usb cable, all that happens is that the home + the menu button shortly light up. The screen is most likely not cracked, it seems all in all perfectly fine.
Linux tells me the following about the HTC First as an USB device:
Code:
$ lsusb
Bus 004 Device 009: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
$ dmesg
[ 4099.008909] usb 4-1.4: new high-speed USB device number 7 using ehci-pci
[ 4099.094091] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected
[ 4099.094249] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0
[ 4372.398567] usb 4-1.4: USB disconnect, device number 7
[ 4372.398780] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 4372.398804] qcserial 4-1.4:1.0: device disconnected
[ 4375.398363] usb 4-1.4: new high-speed USB device number 8 using ehci-pci
[ 4375.521723] hid-generic 0003:05C6:F006.0009: hiddev0,hidraw6: USB HID v1.11 Device [HID 05c6:f006] on usb-0000:00:1d.0-1.4/input0
[ 4379.820165] usb 4-1.4: USB disconnect, device number 8
[ 4380.006727] usb 4-1.4: new high-speed USB device number 9 using ehci-pci
[ 4380.091837] qcserial 4-1.4:1.0: Qualcomm USB modem converter detected
[ 4380.091977] usb 4-1.4: Qualcomm USB modem converter now attached to ttyUSB0
So what do you think? Any suggestions on how I could probably fix this device?
Thank you very much in advance,
Peter

maybe try to flash it back to stock rom via RUU

hlp me friends
same problem ...please tell me how to flash my htc first....plz hlep me

restoring to stock
first of all you must know that this will wipe everything from your phone,so make a backup of personal data... you will need to download the RUU package which has the original stock firmware from this link:
http://www.androidruu.com/?developer=Myst
download this one because this can be s-off: RUU_MYST_UL_Cingular_US_1.08.502.1_Radio_1.15.40.0 0.13_2_10.64.40.33AL_release_316579_signed_2.exe
do you have installed the drivers and is your bootloader unlocked from htc dev?
of course it must be unlocked
1-reboot into bootloader
2-open cmd and type: fastboot oem lock
this will relock your bootloader so you can proceed to install the RUU (if you dont know fastboot comands ask me to send you the files and give you further instructions)
3-now its time to grab the rom.zip from RUU. run the file which you downloaded and i will tell you 2 ways to get the rom.zip
*the first one is to find it to temporary files,pres the windows key + R and type %temp% and there are to many folders,but in one of them you will find it
*the second one is from task manager,open RUU.exe and open taske manager (ctrl+shift+esc),go to applications,right click on ruu ,click on go to process,it will direct you to sth highlighted and again right click on it,click on open file location and here you are at the folder where is located rom.zip . copy it at the folder where you have fastboot.exe and close the RUU application
4-now is time to install the rom.zip,type in cmd:
fastboot oem rebootRUU
(the screen must show htc logo and a dark background)
5- the final step is flashing zip,type again in cmd:
fastboot flash zip rom.zip
(the cmd will show some automated scripts and after a couple of minutes your phone will be completly reverted to stock)
6-if you want to s-off and install a custom rom,first head up to htcdev.com to unlock your bootloader,download moonshine s-off for htc first and it will s-off your htc and root it,install a custom recovery and choose your favorite rom)
Sorry for my bad english,but im trying to do my best !
For any problem contact me !
If i helped you,press the thanks button

wifi problem
Dear,
I have htc first & im face wifi problem after connecting data connecting from sim.
Please resolved if possible.
Thanx & regrds
Kamran siddiqui

I'm pretty sure I bricked my phone bad...

I was trying to reflash the system ROM, and accidentally canceled the ./flash_all script... Now, when I connect my phone, dmesg -w running on my host (Arch Linux) returns this:
HTML:
[22650.389556] usb 3-1.3: new high-speed USB device number 73 using xhci_hcd
[22650.485540] usb 3-1.3: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[22650.485542] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[22650.485543] usb 3-1.3: Product: QUSB_BULK_CID:0402_SN:301E7E84
[22650.485544] usb 3-1.3: Manufacturer: Qualcomm CDMA Technologies MSM
[22650.492441] qcserial 3-1.3:1.0: Qualcomm USB modem converter detected
[22650.492528] usb 3-1.3: Qualcomm USB modem converter now attached to ttyUSB0

Update: So I've discovered now that my phone is apparently in Qualcomm's QDL, or Emergency Download mode... I found a tool here that apparently allows you to flash an image to a device running in this mode...

Were you able to unbrick your phone?

peneoark said:
Were you able to unbrick your phone?
Click to expand...
Click to collapse
Not yet...

same problem here, i tried install new update and now my phone don't turn on, only appears Qualcomm HS-USB 9008 when connecting usb

So apparently I never updated this thread... I ended up just RMAing my phone, but this is the bug that bricked my phone: https://bugs.archlinux.org/task/63370