Database Users

WM5storage and the trinity

Hi,
Since I use Linux on all my primary workstations, I wanted to use WM5orage to export my sdcard in the trinity as an external disk. The program starts fine and the computer also recognizes it. There does however seem to be a problem because the computer starts complaining about I/O error and never succeeds in accessing the drive.
for the interested, this is what my log shows:
Dec 23 17:34:49 laptopia kernel: scsi6 : SCSI emulation for USB Mass Storage devices
Dec 23 17:34:54 laptopia kernel: Vendor: WM5torag Model: TRIN100 Rev: 1.60
Dec 23 17:34:54 laptopia kernel: Type: Direct-Access ANSI SCSI revision: 00
Dec 23 17:34:54 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:54 laptopia kernel: SCSI device sdb: 3970048 512-byte hdwr sectors (2033 MB)
Dec 23 17:34:55 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:55 laptopia last message repeated 5 times
Dec 23 17:34:55 laptopia kernel: sdb: Write Protect is off
Dec 23 17:34:55 laptopia kernel: sdb: assuming drive cache: write through
Dec 23 17:34:55 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:56 laptopia kernel: SCSI device sdb: 3970048 512-byte hdwr sectors (2033 MB)
Dec 23 17:34:56 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:56 laptopia last message repeated 5 times
Dec 23 17:34:57 laptopia kernel: sdb: Write Protect is off
Dec 23 17:34:57 laptopia kernel: sdb: assuming drive cache: write through
Dec 23 17:34:57 laptopia kernel: sdb: sdb1
Dec 23 17:34:57 laptopia kernel: sd 6:0:0:0: Attached scsi disk sdb
Dec 23 17:34:57 laptopia kernel: sd 6:0:0:0: Attached scsi generic sg0 type 0
Dec 23 17:34:57 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:34:59 laptopia last message repeated 12 times
Dec 23 17:34:59 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:34:59 laptopia kernel: end_request: I/O error, dev sdb, sector 8
Dec 23 17:34:59 laptopia kernel: printk: 5 messages suppressed.
Dec 23 17:34:59 laptopia kernel: Buffer I/O error on device sdb, logical block 1
Dec 23 17:34:59 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:00 laptopia last message repeated 5 times
Dec 23 17:35:00 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:35:00 laptopia kernel: end_request: I/O error, dev sdb, sector 16
Dec 23 17:35:00 laptopia kernel: Buffer I/O error on device sdb, logical block 2
Dec 23 17:35:00 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:01 laptopia last message repeated 6 times
Dec 23 17:35:01 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:35:01 laptopia kernel: end_request: I/O error, dev sdb, sector 40
Dec 23 17:35:01 laptopia kernel: Buffer I/O error on device sdb, logical block 5
Dec 23 17:35:01 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:02 laptopia last message repeated 5 times
Dec 23 17:35:02 laptopia kernel: sd 6:0:0:0: SCSI error: return code = 0x70000
Dec 23 17:35:02 laptopia kernel: end_request: I/O error, dev sdb, sector 48
Dec 23 17:35:02 laptopia kernel: usb 3-1: reset full speed USB device using uhci_hcd and address 2
Dec 23 17:35:03 laptopia last message repeated 5 times
etc..etc..etc...
anyone that has gotten this to work correctly ?

found solution
Just to reply to my own post, but I found the solution.
I just had to turn off the advanced USB network functionality off in the usb to pc connection settings. now it works perfectly

In Hermes you need to do this before using WM5Torage:
Settings --> Connections --> USB to PC and disable "advanced USB functions"
Try to see if it's the same on Trinity.

lol
posted at the same time!

pof said:
In Hermes you need to do this before using WM5Torage:
Settings --> Connections --> USB to PC and disable "advanced USB functions"
Try to see if it's the same on Trinity.
Click to expand...
Click to collapse
Nice Trick! It works!
BTW I had to change some settings in Pocket Controller (It made the sugestions itself) but everything is working now.
Gracias Pof.

Something is not right. I click Settings --> Connections --> USB to PC but then the screen flashes once but nothing happens. Any ideas?

Never mind... got it. WisBar Advance was interfering with it and as soon as I shut WisBar down then I could get into the setting.

sorry I'm a bit slow,
On my i-Mate Jam, i used the Card Export (which allows you to let your pc see your ppc as a usb-stick)
But can i do this with the trinity without Card Export?
(cuz it doesn't matter if i enable of disable the setting above it still starts up Active Sync)

Azamat said:
sorry I'm a bit slow,
On my i-Mate Jam, i used the Card Export (which allows you to let your pc see your ppc as a usb-stick)
But can i do this with the trinity without Card Export?
(cuz it doesn't matter if i enable of disable the setting above it still starts up Active Sync)
Click to expand...
Click to collapse
Yes, WM5Storage will work on the trinity if you follow the steps above. I was having problem until I did the same. Now it works flawlessly and best of all WM5Storage is free!

card export works too with this trick.

Card export II
hmm I'm having a problem with card export and wm5storage.
Changing the advanced USB functions doesnt help. With wm5storage I was getting an f1 error..sorry cant remember the exact error message.
Card export II ver 2.20 wasnt working either
Just now I tried the latest release of Card export ver 3.00 and im getting error cant connect to driver interface.
You guys actually got either wm5storage or Card Export to work on ya trinity's? cause im having no end of trouble with it and really miss the feature since upgrading from my Magician, because we can't install active sync on my University computers.
Device
Dopod D810
ROM 1.23.707.6 DOPODASIA WWE GPS
Radio 1.35.00.11
OS 5.1.461
CPU Samsung SC32442A-400MHz

Thanks guys! got my trinity this week and I was very disappointed when WM5torage wouldn't work, its one of my most used programs!

thanks perfectly working fine!
i thought schaps rom with wm5torage is useless!
up for you bro!

wm5torage for my p3600i (and previously p3600) doesn't work
pof said:
In Hermes you need to do this before using WM5Torage:
Settings --> Connections --> USB to PC and disable "advanced USB functions"
Try to see if it's the same on Trinity.
Click to expand...
Click to collapse
Hello,
my p3600i (and previously had a p3600) doesn't work using wm5torage. I'm running tnyynt's wm6.1 rom, when i go to "Settings --> Connections --> USB to PC", i see "Enable advanced network functionality". is this the same thing you guys are referring to? i unchecked this but no luck.
wm5torage version i'm trying to use is 1.8, i also tried 1.7 before but that doesn't work either. my laptop just don't see my card. I used a 8gb microsd with a mini-sd adaptor and also a 4 gb mini-sd, both didn't work.
hopefully someone can help me out.
thanks!

Android SDK on Linux and Vibrant

I installed Android SDK for linux on my laptop, I have my vibrant connected via USB and USB Debugging is checked, when I try to see if adb detected the phone I get
~/android/android-sdk-linux_86/tools$./adb devices
List of devices attached
???????????? no permissions
~/android/android-sdk-linux_86/tools$
Any ideas?
In my logs I see it's been detected
Jul 21 11:33:08 host kernel: [343023.204148] usb 2-2: new high speed USB device using ehci_hcd and address 8
Jul 21 11:33:08 host kernel: [343023.337973] usb 2-2: configuration #3 chosen from 1 choice
Jul 21 11:33:08 host kernel: [343023.339926] cdc_acm 2-2:3.0: ttyACM0: USB ACM device
Jul 21 11:33:08 host kernel: [343023.343833] scsi11 : SCSI emulation for USB Mass Storage devices
Jul 21 11:33:13 host kernel: [343028.346328] scsi 11:0:0:0: Direct-Access SAMSUNG SGH-T959 Card 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.346887] scsi 11:0:0:1: Direct-Access SAMSUNG SGH-T959 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.353861] sd 11:0:0:0: Attached scsi generic sg2 type 0
Jul 21 11:33:13 host kernel: [343028.355185] sd 11:0:0:1: Attached scsi generic sg3 type 0
Jul 21 11:33:13 host kernel: [343028.358528] sd 11:0:0:0: [sdb] Attached SCSI removable disk
Jul 21 11:33:13 host kernel: [343028.360075] sd 11:0:0:1: [sdc] Attached SCSI removable disk

I had the same problem on my computer. Here is how I fixed it.
cd /android sdk/tools/
sudo ./adb kill-server
sudo ./adb start-server
sudo ./adb devices
That should fix it.
Sent from my SAMSUNG-SGH-I897 using XDA App

You have to put the sdk in the C: drive and use the command
cd C:\android-sdk-windows-2.xx_rx\android-sdk-windows-2.xx_rx\tools
http://forum.xda-developers.com/showthread.php?t=502010
http://forum.xda-developers.com/showthread.php?t=517874

alexmullins posted the quick fix - run the adb daemon as root. Or you can modify udev so your the vibrant is mounted with the correct permissions:
Create or edit the file
Code:
/etc/udev/rules.d/51-android.rules
and add the following line:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
Which states something like: "when a usb filesystem with vendor id of 04e8 (Samsung Vibrant) is mounted, apply the 0666 file permissions."
Double check that your vendor id matches "04e8" by running lsusb. Look for your vibrant in that list.
Hope this helps.

@bbwharris
I did not know about your fix. Thanks for that
Sent from my SAMSUNG-SGH-I897 using XDA App

guys,
Thanks a ton!!!
I am going to tinkle with in a bit.
And whoever pointed me to the "C" drive, I hope you like your BSOD's LOL
[EDIT]
List of devices attached
T959c9e2869c device
YES!!!!!!!!!!
[/EDIT]

lqaddict said:
I installed Android SDK for linux on my laptop, I have my vibrant connected via USB and USB Debugging is checked, when I try to see if adb detected the phone I get
~/android/android-sdk-linux_86/tools$./adb devices
List of devices attached
???????????? no permissions
~/android/android-sdk-linux_86/tools$
Any ideas?
In my logs I see it's been detected
Jul 21 11:33:08 host kernel: [343023.204148] usb 2-2: new high speed USB device using ehci_hcd and address 8
Jul 21 11:33:08 host kernel: [343023.337973] usb 2-2: configuration #3 chosen from 1 choice
Jul 21 11:33:08 host kernel: [343023.339926] cdc_acm 2-2:3.0: ttyACM0: USB ACM device
Jul 21 11:33:08 host kernel: [343023.343833] scsi11 : SCSI emulation for USB Mass Storage devices
Jul 21 11:33:13 host kernel: [343028.346328] scsi 11:0:0:0: Direct-Access SAMSUNG SGH-T959 Card 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.346887] scsi 11:0:0:1: Direct-Access SAMSUNG SGH-T959 0000 PQ: 0 ANSI: 2
Jul 21 11:33:13 host kernel: [343028.353861] sd 11:0:0:0: Attached scsi generic sg2 type 0
Jul 21 11:33:13 host kernel: [343028.355185] sd 11:0:0:1: Attached scsi generic sg3 type 0
Jul 21 11:33:13 host kernel: [343028.358528] sd 11:0:0:0: [sdb] Attached SCSI removable disk
Jul 21 11:33:13 host kernel: [343028.360075] sd 11:0:0:1: [sdc] Attached SCSI removable disk
Click to expand...
Click to collapse
ADB has to be run with root access. sudo ./adb

bbwharris said:
alexmullins posted the quick fix - run the adb daemon as root. Or you can modify udev so your the vibrant is mounted with the correct permissions:
Create or edit the file
Code:
/etc/udev/rules.d/51-android.rules
and add the following line:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
Which states something like: "when a usb filesystem with vendor id of 04e8 (Samsung Vibrant) is mounted, apply the 0666 file permissions."
Double check that your vendor id matches "04e8" by running lsusb. Look for your vibrant in that list.
Hope this helps.
Click to expand...
Click to collapse
I implemented this work around, and no need for root to run it anymore
Credit goes to bbwharris!!!

HAHAHAHA
BUMPity bump bump BIA......

Thats not a work around; thats following the install instructions from google
http://developer.android.com/guide/developing/device.html#setting-up

SGS 9000 dead - black screen

Dear all,
I recenetly added Voodoo and LauncherPro to my SGS. All was well. However, today after mounting the discs are USB devices, I ran into some problems after I started using it again:
1) The external SD is marked as corrupted.
2) With USB debugging enabled, the SGS does not show up in the list of devices (lsusb does not show the Samsung devices). adb devices does not list anything.
Next, I rebooted the 'phone. The device can back, the media scanner ran, and the option to unlock the SIM card was displayed, and then it went black, and this was it. Nothing happens when I press any keys.
I plugged into the USB cable and got this from the messages logs on the host computer:
Code:
Nov 23 14:15:11 AMS-L0769L kernel: [ 5351.652593] usb 2-3: new high speed USB device using ehci_hcd and address 10
Nov 23 14:15:11 AMS-L0769L kernel: [ 5351.947495] usb 2-3: configuration #3 chosen from 1 choice
Nov 23 14:15:11 AMS-L0769L kernel: [ 5352.003925] cdc_acm 2-3:3.0: ttyACM0: USB ACM device
Nov 23 14:15:12 AMS-L0769L kernel: [ 5352.127067] scsi6 : SCSI emulation for USB Mass Storage devices
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.131940] scsi 6:0:0:0: Direct-Access SAMSUNG GT-I9000 Card 0000 PQ: 0 ANSI: 2
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.139922] scsi 6:0:0:1: Direct-Access SAMSUNG GT-I9000 0000 PQ: 0 ANSI: 2
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.150786] sd 6:0:0:0: Attached scsi generic sg2 type 0
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.152738] sd 6:0:0:1: Attached scsi generic sg3 type 0
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.159490] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Nov 23 14:15:17 AMS-L0769L kernel: [ 5357.162228] sd 6:0:0:1: [sdc] Attached SCSI removable disk
I can get in via "adb shell" and su to root.
The sd cards are mounted and fine, but the screen is still black:
Code:
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I have removed the external SD and rebooted, but have the same symptons.
Any idea on how to resurrect the device? I can post the output of dmesg if required.

Problems solved by removing the SD card and SIM card, and with several reboots.

Problems with PC connection. connection resets(The pc is running ubuntu)

Most of the times when i'm connection the device to my laptop (With ubuntu 12.10 on), the phone is connection and disconnection on a loop,
even if the device is on charge only mode. so i can't even charge the device from my laptop
The ubuntu syslog:
Oct 15 18:25:25 bnaya kernel: [260911.917518] usb 3-2: new high-speed USB device number 67 using xhci_hcd
Oct 15 18:25:25 bnaya kernel: [260911.934094] usb 3-2: New USB device found, idVendor=1004, idProduct=6300
Oct 15 18:25:25 bnaya kernel: [260911.934103] usb 3-2: New USB device strings: Mfr=2, Product=5, SerialNumber=0
Oct 15 18:25:25 bnaya kernel: [260911.934109] usb 3-2: Product: USB Charge Only Interface
Oct 15 18:25:25 bnaya kernel: [260911.934113] usb 3-2: Manufacturer: LG Electronics Inc.
Oct 15 18:25:25 bnaya kernel: [260911.936666] usbhid 3-2:1.0: couldn't find an input interrupt endpoint
Oct 15 18:25:25 bnaya mtp-probe: checking bus 3, device 67: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2"
Oct 15 18:25:25 bnaya mtp-probe: bus: 3, device: 67 was not an MTP device
Oct 15 18:25:27 bnaya kernel: [260913.907563] usb 3-2: USB disconnect, device number 67
Click to expand...
Click to collapse
And its repeating itself until i disconnect the cable.
Also i discovered only after i bought the device that its not have a mass storage decide connection mode.
I'm working on making the MTP to work, maybe it will solve the problem.
Thanks!

I'm seeing something similar when charging via usb in the car. If I'm listening to something via BT it will pause.
Sent from my VS980 4G using Tapatalk

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.