Database Users

Problems using USB mass storage on an HTC Magic

Hi!
Just got an HTC Magic that was locked on Vodafone Spain. The phone is great, but I seem to have a problem, I can use it as a USB mass storage device.
When I plug it to the computer using the USB cable that came with the phone, the USB notification doesn't shows up, so I can't use the mass storage...
The microSD card has 8GB of capacity and it seems to be ok, at least I can take pictures and saved to the card...
I have tried on Linux(Ubuntu 9.04) and I got the following errors on syslog:
Code:
Sep 25 00:24:20 hotice kernel: [ 441.792088] usb 3-1: new full speed USB device using uhci_hcd and address 6
Sep 25 00:24:20 hotice kernel: [ 441.912044] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:20 hotice kernel: [ 442.136044] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:21 hotice kernel: [ 442.352116] usb 3-1: new full speed USB device using uhci_hcd and address 7
Sep 25 00:24:21 hotice kernel: [ 442.472079] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:21 hotice kernel: [ 442.696080] usb 3-1: device descriptor read/64, error -71
Sep 25 00:24:21 hotice kernel: [ 442.912091] usb 3-1: new full speed USB device using uhci_hcd and address 8
Sep 25 00:24:21 hotice kernel: [ 443.320083] usb 3-1: device not accepting address 8, error -71
Sep 25 00:24:22 hotice kernel: [ 443.432084] usb 3-1: new full speed USB device using uhci_hcd and address 9
Sep 25 00:24:22 hotice kernel: [ 443.840091] usb 3-1: device not accepting address 9, error -71
Sep 25 00:24:22 hotice kernel: [ 443.840117] hub 3-0:1.0: unable to enumerate USB device on port 1
I tried to connect it to Windows XP, it appears an error installing the hardware, then tried to install the USB driver that comes with the Android SDK but with no luck
I have already made a reset to defaults on the phone, but I still get the same problem.
Does anyone knows what could be happening and how can I solve it?
Thank you all.

I don't know if its important, but here is some more info on the phone:
SAPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0007 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I

Have you create the needed udev configuration for your HTC?
In order to mount correctly a HTC Magic you have to the following udev configuration file.
Code:
sudo gedit /etc/udev/rules.d/50-android.rules
And paste the two following lines. Do not forget to change USERNAME with your Ubuntu username
Code:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",ATTR{idProduct}=="0c02",SYMLINK+="android_adb",MODE="0666",OWNER="USERNAME"
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",ATTR{idProduct}=="0c01",SYMLINK+="android_fastboot",MODE="0666",OWNER="USERNAME"
After that you have to either reload the udev configuration or restart udev. To be sure restart udev.
Code:
sudo /etc/init.d/udev restart
I hope this will help youto resolve your case

Thank you for the reply, but I have already done that...
Also, I have pluged in another HTC Magic(a 32A version) to the same laptop and it worked ok
I cant understand what is happening ... can anyone else help me?

If I put the phone in Fastboot Mode, connect it to the laptop, and run the command
Code:
fastboot devices
I can see the phone... but using it as a usb mass storage, nothing happens

its probably hardware then. get them to replace the phone for you.

Humm, thats bad news
The phone is in second hand and I don't have the receipt of the purchase. I will ask the seller if he has it, if not, I guess I will not have a chance to put it to repair under warranty
Also, I have already installed the Cyanogen recovery image, so I guess that would void the warranty, right?

Pushing this topic to the top, has anyone else had this problem?

I had the problem on mine once but it was just related to one pc.
Removed all the drivers off the PC and it worked when I reconnected

@skhell
I don't know where you would find it for a 32A, but assuming you did not change your SPL you can use Fastboot to completely flash a stock config (system, recovery, boot, data, etc)
For instance, Cyanogen's instructions have you fastboot a SAPPIMG.nbh for 32B devices, I am assuming such an image exists for 32a devices as well...
If you can completely re-flash the entire system your warranty claim should be fine.

Yeah, I can restore the phone right as it was originally, the problem is that I don't have a proof of purchase to put it into repair under warranty...

[Q] USB Ethernet Network Adapter on ICS

Is it possible to get this working on the Acer A500 with the ICS leak? I've been able to use it on all 3.2 ROMs and Thors ICS, but when moving to the leak it will not execute "usb_ethernet", it recognizes it as a command but no output is shown. system is set to RW but it still doesn't load.
Just curious.
Thanks everyone!

On the ICS roms, usb1 is not showing up as a network interface

When I look at my dmesg, it shows "USB Ethernet Ver .2" but never loads the ASISX driver.
On Thors ICS it registers "asix 1-1.0: eth0: register "asix" at usb-tegra-ehci.2-1, ASIX AX8877 USB 2.0 Ethernet"
Perhaps its due to the leaked builds using the stock kernel?

I'm using Flexreaper R10 and here is what I get
I flashed the zip provided HERE
I insert the USB adapter and dmesg shows
Code:
<6>[ 146.691880] usb 1-1.3: new high speed USB device number 5 using tegra-ehci
<6>[ 146.763606] usb 1-1.3: New USB device found, idVendor=13b1, idProduct=0018
<6>[ 146.691880] usb 1-1.3: new high speed USB device number 5 using tegra-ehci
<6>[ 146.763606] usb 1-1.3: New USB device found, idVendor=13b1, idProduct=0018
<6>[ 146.764309] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 146.764980] usb 1-1.3: Product: USB 2.0 Network Adapter ver.2
<6>[ 146.765345] usb 1-1.3: Manufacturer:
<6>[ 146.765721] usb 1-1.3: SerialNumber: 01E821 device strings: Mfr=1, Product=2, SerialNumber=3
<6>[ 146.764980] usb 1-1.3: Product: USB 2.0 Network Adapter ver.2
<6>[ 146.765345] usb 1-1.3: Manufacturer:
<6>[ 146.765721] usb 1-1.3: SerialNumber: 01E821
I try to manually load the module I need, "asix410.ko" and I get
Code:
<3>[ 463.740506] asix410: version magic '2.6.36.3 SMP preempt mod_unload ARMv7 ' should be '2.6.39.4+ SMP preempt mod_unload ARMv7 '
Any ideas?
I see that it says that the kernel is not the proper version, but I was under the impression that as log as the kernel is 2.6.39.x, this driver should work.
Thanks!

Try using a hex editor to change the version info in the .ko file to match what the system is expecting and give it a try. I've done that successfully before with a cifs.ko module.

saeba said:
Try using a hex editor to change the version info in the .ko file to match what the system is expecting and give it a try. I've done that successfully before with a cifs.ko module.
Click to expand...
Click to collapse
I did that, having seen you do that with cifs, but the kernel is was made for has like 6 characters whereas this one has 7, so because of that the kernel finds that there is a mismatch and STILL won't load the module.

[Q] ubuntu 12.04, not detecting TF101

Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?

viewlessguru said:
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
Click to expand...
Click to collapse
If your using USB 3.0 ports to connect the tablet try switching to a usb 2.0 port. usb3 has been known to cause add issues sometimes.

Try each of your USB ports. I have issues with my tablet not being seen on all but one port on my PC. Even though stuff works in the other ports It still was not seen.
Sent from my Transformer TF101 using xda premium

What do you see on "$lsusb"?
Can you see an Nvidia Device?

[Q] unable to root nexus 7

hi, i have a 2012 nexus 7 (4.4.2). the only windows-pc i have is my work laptop which i dont have the admin password for stuff like installing drivers and mounting usb drives. so i am booting it using fedora live-usb.
usb debugging is checked in developer options and usb computer connection is set to mtp. this is what i see when it is connected to the pc while on the home screen:
Code:
[[email protected] nexus]$ uname -a -m -p
Linux schneidz 3.9.5-301.fc19.x86_64 #1 SMP Tue Jun 11 19:39:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[[email protected] nexus]$ adb devices
List of devices attached
015d30e1223xxxxx device
[[email protected] ~]$ sudo tail -f /var/log/messages
...
Mar 16 15:59:57 schneidz systemd[1]: Started Hostname Service.
Mar 16 16:00:45 schneidz kernel: [12741.755058] usb 3-1: new high-speed USB device number 24 using xhci_hcd
Mar 16 16:00:45 schneidz kernel: [12741.783549] usb 3-1: New USB device found, idVendor=18d1, idProduct=4e42
Mar 16 16:00:45 schneidz kernel: [12741.783558] usb 3-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[COLOR="Purple"]Mar 16 16:00:45 schneidz kernel: [12741.783560] usb 3-1: Product: Nexus 7
Mar 16 16:00:45 schneidz kernel: [12741.783562] usb 3-1: Manufacturer: asus
Mar 16 16:00:45 schneidz kernel: [12741.783563] usb 3-1: SerialNumber: 015d30e1223xxxxx[/COLOR]
Mar 16 16:00:45 schneidz colord: Device added: sysfs-asus-Nexus_7
but when i reboot the tablet into fastboot mode this is what i see on the pc:
Code:
[[email protected] nexus]$ adb reboot bootloader
[[email protected] ~]$ sudo tail -f /var/log/messages
Mar 16 16:11:57 schneidz kernel: [13414.076731] usb 3-1: USB disconnect, device number 24
Mar 16 16:11:57 schneidz colord: device removed: sysfs-asus-Nexus_7
Mar 16 16:11:57 schneidz dbus[657]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 16 16:11:57 schneidz dbus[657]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 16 16:11:57 schneidz dbus-daemon[657]: dbus[657]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 16 16:11:57 schneidz dbus-daemon[657]: dbus[657]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 16 16:11:57 schneidz systemd[1]: Starting Hostname Service...
Mar 16 16:11:57 schneidz systemd[1]: Started Hostname Service.
Mar 16 16:11:59 schneidz kernel: [13416.496065] usb 3-1: new high-speed USB device number 25 using xhci_hcd
Mar 16 16:11:59 schneidz kernel: [13416.510152] usb 3-1: New USB device found, idVendor=18d1, idProduct=4e40
Mar 16 16:11:59 schneidz kernel: [13416.510163] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[COLOR="Purple"]Mar 16 16:11:59 schneidz kernel: [13416.510169] usb 3-1: Product: Android
Mar 16 16:11:59 schneidz kernel: [13416.510183] usb 3-1: Manufacturer: Google, Inc
Mar 16 16:11:59 schneidz kernel: [13416.510186] usb 3-1: SerialNumber: 015d30e1223xxxxx[/COLOR]
Mar 16 16:11:59 schneidz mtp-probe: checking bus 3, device 25: "/sys/devices/pci0000:00/0000:00:1c.7/0000:25:00.0/usb3/3-1"
Mar 16 16:11:59 schneidz mtp-probe: bus: 3, device: 25 was not an MTP device
...
[[email protected] nexus]$ adb devices
List of devices attached
[[email protected] nexus]$ fastboot oem unlock
< waiting for device >
and it hangs forever. whats weird is that it lists a different product and manufacturer (eventhough the serial numbers match what is on the tablet screen in the fastboot menu -- although product name says grouper). am i doing the wrong method to root this thing (i always thought that nexus devices were the easiest to root) ?

the problem was that i needed to be logged in as root in fedora.

Bricked Jiayu S3A (flashed native ROM with replaced recovery)

1001st problem with bricked device. I tried to flash one of native ROM (jiayus3-5.1_20160121-212346_PC) to almost new phone (ok, almost just received). I replaced file "recovery.img" with TWRP one, checked all checkboxes in SP Flash Tool (as I understand it was fatal mistake), chosem "firmware upgrade" option and clicked "Download". After reboot I even unable to turn it on: LED does not works, looks like it does not charging, all buttons combination (power + volume up or power + volume down or just long power press, etc) does nothing.
On linux (I am using Ubuntu clone, latest Mint) it does not detected without battery. With battery installed in logs I see:
Code:
Aug 2 10:13:44 mobby kernel: [14104.033379] usb 3-6: USB disconnect, device number 40
Aug 2 10:13:46 mobby kernel: [14105.139306] usb 3-6: new full-speed USB device number 41 using xhci_hcd
Aug 2 10:13:46 mobby kernel: [14105.267790] usb 3-6: New USB device found, idVendor=0e8d, idProduct=0003
Aug 2 10:13:46 mobby kernel: [14105.267793] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 2 10:13:46 mobby kernel: [14105.268802] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
Aug 2 10:13:46 mobby mtp-probe: checking bus 3, device 41: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
Aug 2 10:13:46 mobby mtp-probe: bus: 3, device: 41 was not an MTP device
Aug 2 10:13:48 mobby kernel: [14107.582861] usb 3-6: USB disconnect, device number 41
Aug 2 10:14:12 mobby kernel: [14131.531452] usb 3-6: new full-speed USB device number 42 using xhci_hcd
Aug 2 10:14:12 mobby kernel: [14131.659849] usb 3-6: New USB device found, idVendor=0e8d, idProduct=0003
Aug 2 10:14:12 mobby kernel: [14131.659854] usb 3-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 2 10:14:12 mobby kernel: [14131.660664] cdc_acm 3-6:1.0: ttyACM0: USB ACM device
Aug 2 10:14:12 mobby mtp-probe: checking bus 3, device 42: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-6"
Aug 2 10:14:12 mobby mtp-probe: bus: 3, device: 42 was not an MTP device
....... and so on until USB detached .....
I tried to connect it to windows host, installed drivers from autoinstaller then connected phone. I hear sound "device connected", see "drives installation" popup then in 2 seconds sound "device disconnected" and everything repeated infinitely.
So SP Flash Tool unable to connect to my device (without battery it is invisible for the system, nothing in logs) to flash another firmware back. Could you recommend something?
UPD: After researching I found that my Linux still can detect it:
Code:
$ lsusb
...............
Bus 003 Device 091: ID 0e8d:0003 MediaTek Inc. MT6227 phone
...............
Nevertheless I still cannot do anything with SP Flashtool

Well, connection coming up for 2 seconds, than disappearing again ... looks like the preloaded is still working and your phone lives. Did you install the VCOM driver (for Windows)? You should be able to flash your phone with SP flashtool.

Blackcrown said:
Well, connection coming up for 2 seconds, than disappearing again ... looks like the preloaded is still working and your phone lives. Did you install the VCOM driver (for Windows)? You should be able to flash your phone with SP flashtool.
Click to expand...
Click to collapse
Thank you for reply. Actually I fixed it already. Problem was in wrong firmware. I tried to flash unsupported firmware or something like this. Then I downloaded FW from Deutch site and it flashed like a charm.