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!

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.

/system writable with unionfs

Hi,
I've followed the instructions on how to build froyo on Ubuntu 10.04 32Bit,
I had to disable gdb in /buildroot/local/g8_arm/g8_arm.config
or shot make -i world
make menuconfig breaks everything
....so edit configs by hand.....
then it builds fine.....
thanks to his patch:
www android-hilfe de /android-os-entwicklung-customize/4801-kernel-module-kompilieren-erster-versuch.html
it runs (else unionfs complains about missing symbols..)
Code:
adb push unionfs.ko /data/local/tmp
adb push ntfs.ko /data/local/tmp
I've created a second 2GB ext3 partition on my sdhc class6
Code:
insmod /data/local/tmp/unionfs.ko
mount /dev/block/vold/179:18 /data/newroot
mount -t unionfs -o dirs="/data/newroot/rootfs=rw:/system=ro" unionfs /system
and now i've things like a writeble host file .....
it runs since yesterday here - and is fine.
jens

jensbln said:
Hi,
I've followed the instructions on how to build froyo on Ubuntu 10.04 32Bit,
I had to disable gdb in /buildroot/local/g8_arm/g8_arm.config
or shot make -i world
make menuconfig breaks everything
....so edit configs by hand.....
then it builds fine.....
thanks to his patch:
www android-hilfe de /android-os-entwicklung-customize/4801-kernel-module-kompilieren-erster-versuch.html
it runs (else unionfs complains about missing symbols..)
Code:
adb push unionfs.ko /data/local/tmp
adb push ntfs.ko /data/local/tmp
I've created a second 2GB ext3 partition on my sdhc class6
Code:
insmod /data/local/tmp/unionfs.ko
mount /dev/block/vold/179:18 /data/newroot
mount -t unionfs -o dirs="/data/newroot/rootfs=rw:/system=ro" unionfs /system
and now i've things like a writeble host file .....
it runs since yesterday here - and is fine.
jens
Click to expand...
Click to collapse
For morons like me what does that mean....root access??
Sorry if that is a dumb question

@mothy
so far, temporary root with writable /system directory

So just to be clear. Do you replace the kernel at all?
And do you have to mount the sd partition every time you boot up?

It's for the original Archos Kernel 2.6.29-omap1
Code:
# lsmod
ntfs 213028 0 - Live 0xbf276000
unionfs 74364 1 - Live 0xbf211000
this means you have to
temproot+"re"mount
the writable places, maybe soft-reboot (i use LCDDensity, it's soft-rebooting) and all your're changes are magicly there
instead of using sd, you can just create /data/newroot and let the things go there
Code:
# df -h
/dev/block/mmcblk0p4 299.4M 205.1M 78.9M 72% /data
i don't see any new rom's soon, unless we get a new bootloader, Archos uses mmcblk0 (an SD-Card device) and not mtd, so i think we can forget all that fastboot, flash_unlock mtd stuff.
this is very annoying, maybe i'm wrong,
but it looks like they don't want us to reflash the device :-(
unionfs usually need a own kernel, but the "ugly patches" make it run with the archos gen8 kernel
So i use temproot, gscript, LCDDensity after each reboot - and have all my settings back, apps like adsfree runs...
jens

forgive my lack of knowledge but you keep mentioning ntfs in the code fragments but you havent actually said that this is giving you ntfs support. does your kernal changes allow for reading ntfs volumes?

yes, i hope so, but i havn't tested it until now, minimum is that you can mount ntfs volumes by hand - but maybe it's automounting....
i want test a HD movie from sd, but mine doesnt fit in 4Gig (fat)
jens

i've connected same ntfs disk and:
Code:
usb 2-1:1.0: uevent
usb-storage 2-1:1.0: usb_probe_interface
usb-storage 2-1:1.0: usb_probe_interface - got id
devdb: devpath usb-musb_hdrc-1 not found
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
/mnt/flash/releases/G8A/v2.0.53-r80341/arcbuild/linux/drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
scsi 0:0:0:0: Direct-Access SAMSUNG HM160HI PQ: 0 ANSI: 2
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
usb-storage: device scan complete
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sda1.
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 2
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
same things more need to be done, a trick could be having a small fat partition, so the system has it's sda1 as fas as expecting .....
jens

U8800 not detected by pc

Hello,
I have an issue with my U8800.
It is not detected by my PC (Windows 7 x64). When I say it is not detected, I mean nothing happens. Tried all USB ports. In fact, I have tried the phone on 6 diferent PCs (4 with windows 7 x64, 1 with windows 7 x86 and one with Vista x86). The best I could get was usb not recognized (but very quickly) in one of them (x64) but not replicated. It doesn't matter if you go to Pink Screen, with battery, without battery, with sd card or without, etc. Have tried forcing all kinds of drivers, without success. Android SDK is fully installed, etc.
I also tried using 2 diferent Linux live OS's. On one of them, I was able to mount the "CD - the one with the drivers", but again, only once.
I was using Aurora with latest update when this issue started. Never partitioned. I have downgraded to Rom 136. Tried B517 and B528. I'm only able to root the device using Z4root with froyo.
Tried 3 different cables and all of them work without any issues with a Galaxy S3 and a ZTE Racer.
The funny thing is that the U8800 is detected by my car audio system (it uses windows CE 5.0) and plays media files fine. Even the USB Debugging shows up. On another car, with a "usb radio" it also works.
The device itself charges fine in every usb port i have tried
Any help would be appreciated.
Thank you

Hi guys, just an update.
I forgot to mention that the device itself does nothing while connected to the pc. No USB mount or USB Debugging icons. Just the charging message and the lightning icon.
I have tried the device on 5 more PCs and 3 more cables. Not much luck. I did get a few odd behaviours.
This is what I have found out:
Windows 7
With the phone OFF:
If I just plug in the usb cable, it will turn on and after a few seconds, the battery image will appear. While doing that, by using UsbDview, I can see USB Mass Storage Device with the idVendor=12d1, idProduct=1037.
Windows displays "Unrecognized usb device" and a pop up says that windows was unable to find/install drivers for the "unkown device" (error 45 - device is not connected).
Phone turned ON:
If I turn the phone on, no error is displayed and no attempts to install drivers are made. Nothing happens.
Ubuntu (12.0x) - Using the same method with the phone turned OFF:
Dmesg displays:
usb 5-1: new full-speed USB device number 5 using uhci_hcd
hub 5-0:1.0: unable to enumerate USB device on port 5
If I insist, by removing the usb cable, a few times, I get this:
"usb 5-1: new full-speed USB device number 2 using uhci_hcd
[ 2463.956220] usb 5-1: device descriptor read/64, error -71
[ 2464.180120] usb 5-1: device descriptor read/64, error -71
[ 2464.396215] usb 5-1: new full-speed USB device number 3 using uhci_hcd
[ 2464.516211] usb 5-1: device descriptor read/64, error -71
[ 2464.740204] usb 5-1: device descriptor read/64, error -71
[ 2464.956203] usb 5-1: new full-speed USB device number 4 using uhci_hcd
[ 2465.372073] usb 5-1: device not accepting address 4, error -71
[ 2465.484242] usb 5-1: new full-speed USB device number 5 using uhci_hcd
[ 2465.900220] usb 5-1: device not accepting address 5, error -71
[ 2465.900263] hub 5-0:1.0: unable to enumerate USB device on port 1
[ 2467.624209] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 2467.876222] usb 5-1: new full-speed USB device number 6 using uhci_hcd
[ 2468.019363] usb 5-1: not running at top speed; connect to a high speed hub
[ 2468.038249] usb 5-1: New USB device found, idVendor=12d1, idProduct=1037
[ 2468.038262] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2468.038270] usb 5-1: Product: Android Adapter
[ 2468.038276] usb 5-1: Manufacturer: Huawei Incorporated
[ 2468.038283] usb 5-1: SerialNumber: 20XXXXXXXXXX
[ 2468.130459] Initializing USB Mass Storage driver...
[ 2468.130622] scsi5 : usb-storage 5-1:1.0
[ 2468.130718] usbcore: registered new interface driver usb-storage
[ 2468.130720] USB Mass Storage support registered.
[ 2469.133463] scsi 5:0:0:0: Direct-Access Android Adapter 0100 PQ: 0 ANSI: 2
[ 2469.136395] scsi 5:0:0:1: CD-ROM Android Adapter 0100 PQ: 0 ANSI: 2
[ 2469.139317] scsi 5:0:0:2: Direct-Access Android Adapter 0100 PQ: 0 ANSI: 2
[ 2469.141053] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 2469.170237] sr1: scsi3-mmc drive: 0x/0x caddy
[ 2469.170496] sr 5:0:0:1: Attached scsi CD-ROM sr1
[ 2469.170578] sr 5:0:0:1: Attached scsi generic sg3 type 5
[ 2469.170762] sd 5:0:0:2: Attached scsi generic sg4 type 0
[ 2469.372234] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[ 2469.421238] sd 5:0:0:2: [sdc] Attached SCSI removable disk"
Phone turned ON:
Only when this information is displayed, If I turn the phone on, it will connect to linux. Usb debugging will come up and I'm able to mount the SD card.
This is very weird. Can anyone help me with this issue?

Hello again,
Over 100 views and not a single idea???
One thing, when I connect the phone to Ubuntu (not in pink screen, as it doesn't work), the internal memory is seen as unallocated. Is this normal? It say 2.0GIG but no file system. I have access to the internal memory on the phone itself. Could this be a clue (The external SD card is visible and accessable).
When i type adb devices, no device is present or if I use adb shell, error: device not found.
lsusb and dmesg show the device.
Bus 006 Device 028: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
ls -l /dev/bus/usb/006/028
crw-rw-rw-+ 1 root gabriel 189, 667 Sep 3 09:41 /dev/bus/usb/006/028
A have, at this moment, B517 installed (tried 136, 138, 518, 526, 528 with the same results).
Come on guys, I don't believe this to be a hardware issue. Please help!!!!!!!!!
P.S. I still have IMEI, serial, etc.

jcpbs said:
Hello again,
Over 100 views and not a single idea???
One thing, when I connect the phone to Ubuntu (not in pink screen, as it doesn't work), the internal memory is seen as unallocated. Is this normal? It say 2.0GIG but no file system. I have access to the internal memory on the phone itself. Could this be a clue (The external SD card is visible and accessable).
When i type adb devices, no device is present or if I use adb shell, error: device not found.
lsusb and dmesg show the device.
Bus 006 Device 028: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
ls -l /dev/bus/usb/006/028
crw-rw-rw-+ 1 root gabriel 189, 667 Sep 3 09:41 /dev/bus/usb/006/028
A have, at this moment, B517 installed (tried 136, 138, 518, 526, 528 with the same results).
Come on guys, I don't believe this to be a hardware issue. Please help!!!!!!!!!
P.S. I still have IMEI, serial, etc.
Click to expand...
Click to collapse
It is a strange behaviour. The only thing I could recommend you is dial *#*#2846579#*#* and see the usb port setting. On stock ROMs you should be able to change it to something like "normal" or "google".

Blefish said:
It is a strange behaviour. The only thing I could recommend you is dial *#*#2846579#*#* and see the usb port setting. On stock ROMs you should be able to change it to something like "normal" or "google".
Click to expand...
Click to collapse
Belfish, thank you for the reply. I have already tried that. Same result. Someone has suggested if the vold.fstab file has been moddified. I have never touched it so I don't know what I'm looking for. This is what's inside the file:
# Copyright (c) 2010, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# < DTS2010071700153 genghua 20100717 begin
# we modified this command according to our platform to support SD card recognization in user space
# dev_mount sdcard /mnt/sdcard auto /devices/platform/msm_sdcc.1/mmc_host/mmc0
## /* <DTS2010081001800 duangan 20100814 begin */
dev_mount sdcard2 /mnt/sdcard auto /devices/platform/msm_sdcc.4/mmc_host
dev_mount sdcard1 /mnt/sdcard 14 /devices/platform/msm_sdcc.2/mmc_host
## /* DTS2010081001800 duangan 20100814 end> */
# DTS2010071700153 genghua 20100717 end >
Is it supposed to be like that?
Thanks.

The vold.fstab shouldn't matter much. If it is wrong, then it would not let you mount sd card in android too.
I don't really know how to help you. I know there are some NV items that could alter the USB interface, but it's mostly in the kernel side. Maybe you can check your "dmesg" log on your phone. Using a Terminal Emulator, first write su for superuser and then dmesg. It gives you the kernel log messages in Android side (the phone).

Blefish said:
The vold.fstab shouldn't matter much. If it is wrong, then it would not let you mount sd card in android too.
I don't really know how to help you. I know there are some NV items that could alter the USB interface, but it's mostly in the kernel side. Maybe you can check your "dmesg" log on your phone. Using a Terminal Emulator, first write su for superuser and then dmesg. It gives you the kernel log messages in Android side (the phone).
Click to expand...
Click to collapse
Ok, I will do that. I just need to go back to 2.2 so I can root it. Once I have the Logs, I will post it. I really hope to solve this so I can try your new rom. Thank you Blefish
P.S. Is there anything I should be looking for?

[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.