Jump to content

Issues with USB connectivity etc. and root / A2SD


Guest PaulOBrien

Recommended Posts

Guest eViL D:
I don't think there are any USB altering codes for the desire :rolleyes: (that I know of)

Something else to try here:

sudo nano /etc/usb_modeswitch.d/05c6\:9002
Paste the following into the nano text editor
########################################################

# Qualcomm device?


DefaultVendor= 0x05c6

DefaultProduct=0x9002


TargetVendor=  0x0bb4

TargetProduct= 0x0c87


CheckSuccess=20


MessageContent="5553424360293389fc00000080000a2300000000000000fc00000000000000"
press CTRL+X, then Y then return to save the file. then run
sudo usb_modeswitch -c /etc/usb_modeswitch.d/05c6\:9002

The MessageContent was sniffed in windows using SniffUSB 2.0.

It's for the switch to the standard HTC composite USB device though, so it might not work, and somebody with a bricked device might need to sniff their phone instead.

When trying to save "Error writing /etc/usb_modeswitch.d/05c6:9002: No such file or directory "

Link to comment
Share on other sites

Guest Normola
When trying to save "Error writing /etc/usb_modeswitch.d/05c6:9002: No such file or directory "

You can save it anywhere, as long as you alter -c /etc/usb_modeswitch.d/05c6\:9002 to point to the correct place.

eg.

save to ~/Desktop/blahfile

sudo usb_modeswitch -c ~/Desktop/blahfile

Link to comment
Share on other sites

sudo usb_modeswitch -c /home/usb_modeswitch.d/05c6\:9002

Looking for target devices ...

No devices in target mode or class found

Looking for default devices ...

Found default devices (1)

Accessing device 004 on bus 001 ...

Using endpoints 0x01 (out) and 0x81 (in)

Not a storage device, skipping SCSI inquiry

Error: could not get description string "manufacturer"

Error: could not get description string "product"

USB description data (for identification)

-------------------------

Manufacturer:

Product:

Serial No.: not provided

-------------------------

Looking for active driver ...

No driver found. Either detached before or never attached

Setting up communication with interface 0 ...

Trying to send the message to endpoint 0x01 ...

OK, message successfully sent

Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...

Original device is gone already, not checking

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

No new devices in target mode or class found

Mode switch has failed. Bye.

Link to comment
Share on other sites

Guest Normola
Setting up communication with interface 0 ...

Trying to send the message to endpoint 0x01 ...

OK, message successfully sent

Device is gone, skipping any further commands

This is interesting. Were there any messages show in dmesg when this happened?

Link to comment
Share on other sites

Guest xTc is loVe
sudo usb_modeswitch -c /home/usb_modeswitch.d/05c6\:9002

Looking for target devices ...

No devices in target mode or class found

Looking for default devices ...

Found default devices (1)

Accessing device 004 on bus 001 ...

Using endpoints 0x01 (out) and 0x81 (in)

Not a storage device, skipping SCSI inquiry

Error: could not get description string "manufacturer"

Error: could not get description string "product"

USB description data (for identification)

-------------------------

Manufacturer:

Product:

Serial No.: not provided

-------------------------

Looking for active driver ...

No driver found. Either detached before or never attached

Setting up communication with interface 0 ...

Trying to send the message to endpoint 0x01 ...

OK, message successfully sent

Device is gone, skipping any further commands

Checking for mode switch (max. 20 times, once per second) ...

Original device is gone already, not checking

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

Searching for target devices ...

No new devices in target mode or class found

Mode switch has failed. Bye.

U mean we stay bricked?

Link to comment
Share on other sites

not that i saw

can we try it under fastboot ?

then it apears:

Bus 001 Device 005: ID 0bb4:0fff High Tech Computer Corp.

ah... tried it - wont find the device

sudo usb_modeswitch -c /home/usb_modeswitch.d/0bb4\:0fff

Looking for target devices ...

No devices in target mode or class found

Looking for default devices ...

No default device found. Is it connected? Bye.

This is interesting. Were there any messages show in dmesg when this happened?
Edited by r&a
Link to comment
Share on other sites

Guest Normola
not that i saw

can we try it under fastboot ?

then it apears:

Bus 001 Device 005: ID 0bb4:0fff High Tech Computer Corp.

As far as I can tell, this is the correct device id for fastboot usb anyway. Will fastboot.exe communicate with it?

Have you tried this (from an earlier post)

*****Ubuntu 9.10+ *****

sudo echo 'SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="0bb4", MODE="0660", GROUP="plugdev"' > /lib/udev/rules.d/11-android.rules

sudo echo 'SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="05c6", MODE="0660", GROUP="plugdev"' > /lib/udev/rules.d/11-android.rules

sudo echo 'SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="05c6", ATTR{idProduct}==""9002", SYMLINK+="android_adb"' > /lib/udev/rules.d/11-android.rules

suco echo 'SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", SYMLINK+="android_fastboot"' > /lib/udev/rules.d/11-android.rules

sudo echo 'SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c02", SYMLINK+="android_adb" ' > /lib/udev/rules.d/11-android.rules




***** Ubuntu 9.04 *****

sudo echo 'SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="0bb4", MODE="0660", GROUP="plugdev"' >  /etc/udev/rules.d/11-android.rules

sudo echo 'SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="05c6", MODE="0660", GROUP="plugdev"' > /etc/udev/rules.d/11-android.rules

sudo echo 'SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="05c6", ATTR{idProduct}==""9002", SYMLINK+="android_adb"' > /etc/udev/rules.d/11-android.rules

suco echo 'SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", SYMLINK+="android_fastboot"' > /etc/udev/rules.d/11-android.rules

sudo echo 'SUBSYSTEM=="usb|usb_device", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c02", SYMLINK+="android_adb" ' > /etc/udev/rules.d/11-android.rules
If you don't have a persistent linux installation, you can try to restart udev like this:
sudo /etc/init.d/udev stop

sudo /etc/init.d/udev start

Edited by Normola
Link to comment
Share on other sites

i have no 11-android.rules

and command responds: permission denied

As far as I can tell, this is the correct device id for fastboot usb anyway. Will fastboot.exe communicate with it?

Have you tried this (from an earlier post)

*****Ubuntu 9.10+ *****

sudo echo 'SUBSYSTEM=="usb|usb_device", SYSFS{idVendor}=="0bb4", MODE="0660", GROUP="plugdev"' > /lib/udev/rules.d/11-android.rules

sudo /etc/init.d/udev start

Link to comment
Share on other sites

Guest Normola
i have no 11-android.rules

and command responds: permission denied

Try creating it with nano first

For ubuntu 9.10+

sudo nano /lib/udev/rules.d/11-android.rules

CTRL+C then Y to save
If you boot into recovery mode (with the red triangle) and run modeswitch with the following file (using sudo usb_modeswitch -c /NEWFILELOCATION), do you get any effect (dmesg or adb/fastboot detection)?
########################################################

# Change to recovery device?


DefaultVendor= 0x05c6

DefaultProduct=0x9002


TargetVendor=  0x0bb4

TargetProduct= 0x0c87


CheckSuccess=20


MessageContent="55534243107c35062400000080000612000000240000000000000000000000"

Edited by Normola
Link to comment
Share on other sites

Guest Normola
No default vendor/product ID given. Aborting.

That doesn't sound right. Could you paste the command you used. Also check to make sure the config file was written correctly.

Link to comment
Share on other sites

missed filename but corrected and no go as i edited the answer

That doesn't sound right. Could you paste the command you used. Also check to make sure the config file was written correctly.
Link to comment
Share on other sites

Guest xTc is loVe
missed filename but corrected and no go as i edited the answer

Any brickes out there with the r5 Rooting Method and the new Recovery Console?

Link to comment
Share on other sites

Guest nicandris

ok wont buy a desire... :rolleyes:

ordering my N1 now from expansys!!

anyone that used em both has something to say about comparance?

Link to comment
Share on other sites

Guest SonicArt77

last night I got the drivers for the three qualcomm devices, and after installing them on a x86 windows machine, they're listed as:

Qualcomm HS-USB Modem 9002

Qualcomm HS-USB Diagnostics 9002 (COMx)

Qualcomm HS-USB NMEA 9002 (COMx) (assuming for GPS)

Seeing that the they're COM ports, we might have some hope...

Link to comment
Share on other sites

Guest NOFX

Guys,

This might be a really crazy idea, but it just struck me:

In this link: http://android.modaco.com/content/google-n...en-final-alpha/, the final alpha port of Desire ROM to N1, I just noticed under 'known bugs'.

Known Issues

* Bluetooth does not work reliably

* FM Radio finds stations but does not produce any sound

* Footprints camera view is rotated 90 degrees

* USB mount notification does not fire - use 'USB Mount' application from menu.

Is it just a coincidence that BT, FM and USB all have problems? And can this fact in some way be related (or maybe solved) in the Desire case as well?

Don't hang me if it's rediculous - it's worth a shot right :rolleyes:

Link to comment
Share on other sites

Guest jamlam
last night I got the drivers for the three qualcomm devices, and after installing them on a x86 windows machine, they're listed as:

Qualcomm HS-USB Modem 9002

Qualcomm HS-USB Diagnostics 9002 (COMx)

Qualcomm HS-USB NMEA 9002 (COMx) (assuming for GPS)

Seeing that the they're COM ports, we might have some hope...

Have you tried connecting to them with HyperTerminal? There may be a menu or something...

EDIT: Also found this link to a post about someone using this device for debugging https://brewmobileplatform.qualcomm.com/bmp...s/list/887.page

Edited by jamlam
Link to comment
Share on other sites

Guest adi90
Guys,

This might be a really crazy idea, but it just struck me:

In this link: http://android.modaco.com/content/google-n...en-final-alpha/, the final alpha port of Desire ROM to N1, I just noticed under 'known bugs'.

Known Issues

* Bluetooth does not work reliably

* FM Radio finds stations but does not produce any sound

* Footprints camera view is rotated 90 degrees

* USB mount notification does not fire - use 'USB Mount' application from menu.

Is it just a coincidence that BT, FM and USB all have problems? And can this fact in some way be related (or maybe solved) in the Desire case as well?

Don't hang me if it's rediculous - it's worth a shot right :rolleyes:

Like this idea ...

SonicArt77 , can you share those drivers please ?

Link to comment
Share on other sites

Guest kubino
last night I got the drivers for the three qualcomm devices, and after installing them on a x86 windows machine, they're listed as:

Qualcomm HS-USB Modem 9002

Qualcomm HS-USB Diagnostics 9002 (COMx)

Qualcomm HS-USB NMEA 9002 (COMx) (assuming for GPS)

Seeing that the they're COM ports, we might have some hope...

seems like you are locked in debug mode. the good think is you will propably be able to access device at low level. Has anybody tried to use QXDM / QPST ?

QPST (Qualcomm Product Support Tool) is an windows application developed by Qualcomm for cellular phones that feature Qualcomm chipsets. It features a file explorer, factory test tools, low level communication settings, RF calibration tools, roaming list editor, service programming tool, and more.

Link to comment
Share on other sites

Guest Biliskner
seems like you are locked in debug mode. the good think is you will propably be able to access device at low level. Has anybody tried to use QXDM / QPST ?

QPST (Qualcomm Product Support Tool) is an windows application developed by Qualcomm for cellular phones that feature Qualcomm chipsets. It features a file explorer, factory test tools, low level communication settings, RF calibration tools, roaming list editor, service programming tool, and more.

Yeh I've got those tools. But can't get it to connect to my phone on COM ports. Anyone want them - I can upload.... (if it's not against forum rules)

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.