Database Users

/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

USB Host mode on Defy

Has anyone tried Defy's USB Host mode?
Would like to attach USB devices onto Defy:
- USB keyboard / mouse
- USB disk drives
- Other types of USB 3G modems (like CDMA1x/EVDO)
- Arduino IO board
...
I haven't bought Defy yet, but want to do some pre-research before the purchase.
Could someone do me a favor to post the outputs of "dmesg" on Defy?
(Run dmesg command under the Linux console).
I expect to see something like:
Code:
...
OMAP3630 ES1.1
...
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Sangoma WANPIPE r outer v1.1 (c) 1995-2000 Sangoma Technologies Inc.
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
...
I got above dmesg by Web searching for an OMAP3630 test board, not a Defy.
Just want to make sure Defy is equipped with USB OTG controller.

This function not supported in the kernel, so kernel we can not replace, because bootloader is locked.

_ReBoot_ said:
This function not supported in the kernel, so kernel we can not replace, because bootloader is locked.
Click to expand...
Click to collapse
Understood the bootloader is locked by Moto, and a kernel must be signed.
Instead of replacing kernel itself, can we just load new driver modules (*.ko via insmod command)?
Does Moto also prevent from loading customized driver modules?

Can someone help to get the outputs of "cat /proc/driver/musb_hdrc" ?
Something like:
Code:
#cat /proc/driver/musb_hdrc
Status: MHDRC, Mode=Peripheral (Power=60, DevCtl=80)
OTG state: b_idle; inactive
Options: musb-dma, otg (peripheral+host), debug=3 [eps=16]
Peripheral address: 30
Root port status: 00000000
Gadget driver: (none)

http://copytaste.com/e272

unrafa said:
http://copytaste.com/e272
Click to expand...
Click to collapse
unrafa, thanks a lot for your info.
One correction to my previous command line for current USB mode:
"cat /sys/devices/platform/musb_hdrc/mode"
Following dmesg of Defy shows the internal USB modem is attached to the USB Host for modem init. But later reset as b_peripheral:
Code:
<6>[ 8.118133] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<4>[ 8.118347] IRQ 78/usbtll: IRQF_DISABLED is not guaranteed on shared IRQs
<6>[ 8.119018] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
<6>[ 8.119323] ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
<6>[ 8.119842] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
<6>[ 8.134368] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
<6>[ 8.135192] usb usb1: configuration #1 chosen from 1 choice
<6>[ 8.135650] hub 1-0:1.0: USB hub found
<6>[ 8.135833] hub 1-0:1.0: 3 ports detected
<6>[ 8.136688] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
<6>[ 8.137451] usbcore: registered new interface driver cdc_acm
<6>[ 8.137573] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
<6>[ 8.138244] usbcore: registered new interface driver usbserial
<6>[ 8.138366] usbserial: USB Serial Driver core
<6>[ 8.138641] USB Serial support registered for moto-modem
<6>[ 8.138946] usbcore: registered new interface driver moto-modem
<6>[ 8.139312] USB Serial support registered for QSC 6085 Modem Driver
<6>[ 8.139617] usbcore: registered new interface driver cdma-modem
...
<6>[ 80.229614] MUSB BUS RESET as b_peripheral
How about to use:
"echo b_host > /sys/devices/platform/musb_hdrc/mode"
to enable the Host mode again?
May run command "modinfo musb_hdrc" to get actual parameters we can use to enable the Host mode.
Something like "modprobe musb_hdrc mode_default=1".

$ cat /sys/devices/platform/musb_hdrc/mode
b_peripheral
# echo b_host > /sys/devices/platform/musb_hdrc/mode
# echo b_host > /sys/devices/platform/musb_hdrc/mode
# cat /sys/devices/platform/musb_hdrc/mode
b_peripheral
# ls
uevent
modalias
subsystem
power
driver
gadget
mode
vbus
srp
# cat power
power: invalid length
# ls
uevent
modalias
subsystem
power
driver
gadget
mode
vbus
srp
# cat mode
b_peripheral
# cat vbus
Vbus off, timeout 0 msec
# cat srp
srp: invalid length
# cat uevent
DRIVER=musb_hdrc
MODALIAS=platform:musb_hdrc
# cat modalias
platform:musb_hdrc
# cat subsystem
subsystem: invalid length
# modinfo musb_hdrc
modinfo: can't open '/lib/modules/2.6.32.9-ga649a2e/modules.dep': No such file or directory
# modprobe musb_hdrc
modprobe: chdir(/lib/modules): No such file or directory
by the way /lib/modules doesnt exist, there are 20 modules in /system/lib/modules
and no musb_hdrc module there
Inside android's menu if i change "motorola Phone portal" to "USB mass storage" dmesg got this
<3>[12344.262695] do_cmd_proc_msg: Acquisition cycle length overflow
<6>[12345.158843] musb_pullup - Disabling USB Pullups
<6>[12345.159606] usbnet_disable
<7>[12345.159881] mtp_function_disable(): disabled
<6>[12345.161651] adb_release
<6>[12345.163146] adb_open
<6>[12345.165618] Sending USBLAN disabled uevent
<6>[12345.279876] musb_pullup - Enabling USB Pullups
<6>[12345.389068] device_mode_change_write - Successfully enabled function - msc_adb
<6>[12345.594573] MUSB BUS RESET as b_peripheral
<6>[12345.674407] MUSB BUS RESET as b_peripheral
<6>[12345.705291] android_usb gadget: high speed config #1: android
<4>[12349.139770] mmc0: Starting deferred resume
<4>[12349.511322] mmc0: Deferred resume completed
/sys/module/musb_hdrc/parameters/debug exists. no more than that file
Would it be possible to connect an external hard disk to this phone?

MAPGPS said:
Does Moto also prevent from loading customized driver modules?
Click to expand...
Click to collapse
No, we really can load own driver modules....
sent from my moto defy with taptalk

It would be very great if this will work.
Is there any progress?

yeah, be nice to connect 2 usb hosts so i can copy my slr pictures from a 32gb sd card over to a 320gb hdd.
I have usb y cables so i can power the hosts with an external usb charger.

Any news on this?

It will be nice to see an USB host patch/mod on Defy

hi
I've seen that some phones will enable host mode if you boot them with the data pins shorted, done with a "dongle". anyone tried this on the defy? I'll make one and try it if no one has.
Sent from my MB525 using Tapatalk

hmm.. is that safe? I dont want to burn my usb port..

I doubt it will damage anything. they won't be able to source enough current.
I've checked and the omap3610 supports usb otg. I will try to test this weekend.
Sent from my MB525 using Tapatalk

http://www.tombom.co.uk/blog/?p=124
that page shows the 'dongle' I mean.
Sent from my MB525 using Tapatalk

drmouse81 said:
hi
I've seen that some phones will enable host mode if you boot them with the data pins shorted, done with a "dongle". anyone tried this on the defy? I'll make one and try it if no one has.
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
Scratch that, it is not the data pins, you connect the "extra" pin (pin 4) to ground.

Maybe 2nd ini make this able...

Guys, i saw something on Blog.Makezine.
http://androidcommunity.com/ioio-fo...mples-from-usb-breakout-board-video-20110408/
http://ytai-mer.blogspot.com/2011/04/meet-ioio-io-for-android.html
Maybe this could help, would love to be able to play video files from a external HDD. Watching movies on the backseat while we drive to our vacation!

maybe we need another kernel,i think

Flashed a kernel? Now your xoom is on fire...

I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.

upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?

MitchRapp said:
upgrading from Tiaman 1.1.6 to 1.3.1 just overwrites them ... you mean changing kernels completely right?
Click to expand...
Click to collapse
No i mean the files on your computer, not the xoom. People are extracting the files into the SDK directory. Then leaving them there to mix with the new files. The xoom will overwrite what it needs to.

bwcorvus said:
I think the most common problem we are seeing is people not clearing the old files. Before you download a new kernel and extract it, delete the old files from your SDK directory on your computer. Everyone that has had a problem so far, either screwed up a step or flashed a combo of new files and old files (ie the wifi not working after). So again BEFORE you extract the new kernel, REMOVE all old kernel files from the SDK directory on your computer.
List of files:
boot.img
/system/lib/modules/bcm4329.ko
/system/lib/modules/tun.ko
/system/lib/modules/scsi_wait_scan.ko
/system/lib/modules/cifs.ko
/system/etc/vold.fstab
You may ask why i didn't post this in the development forum, cause i'm not developing anything.
Click to expand...
Click to collapse
This is why I always copy my files into a temp directory as shown in this post

Or just use a different folder for each version, and cd to the directory before you flash.
Also, you can do adb push system /system, and it'll put them in the right folders if you have it mirrored in your PC's folders.

Mine doesn't power up after following the procedure, it stays in the Motorola Dual Core logo..
I guess no XOOM for me until tomorrow
dmesg output:
Code:
<4>[ 18.182391] Primary GPT is invalid, using alternate GPT.
<6>[ 18.182577] mmcblk1: p1 (ebb) p2 (pdsb) p3 (misc) p4 (logo.bin) p5 (kpanic) p6 (recovery) p7 (boot) p8 (system) p9 (cache) p10 (userdata)
<6>[ 18.567134] android_usb gadget: high speed config #1: android
<6>[ 18.572291] EXT4-fs (mmcblk1p8): INFO: recovery required on readonly filesystem
<6>[ 18.572602] EXT4-fs (mmcblk1p8): write access will be enabled during recovery
<6>[ 18.603790] EXT4-fs (mmcblk1p8): recovery complete
<6>[ 18.606421] EXT4-fs (mmcblk1p8): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.682391] EXT4-fs (mmcblk1p10): recovery complete
<6>[ 18.683460] EXT4-fs (mmcblk1p10): mounted filesystem with ordered data mode. Opts: (null)
<6>[ 18.701587] EXT4-fs (mmcblk1p9): recovery complete
<6>[ 18.702643] EXT4-fs (mmcblk1p9): mounted filesystem with ordered data mode. Opts: (null)
<4>[ 18.740397] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
<3>[ 18.745288] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
<6>[ 18.844887] enabling adb
<6>[ 18.861463] adb_open
<6>[ 18.924122] warning: `rild' uses 32-bit capabilities (legacy support in use)
<6>[ 18.928677] gps_brcm4750_ioctl: Setting gps gpio reset pin: 0
<6>[ 18.928769] stingray_gps_reset_gpio: setting GPS Reset GPIO to 0
<6>[ 18.928937] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 18.929026] stingray_gps_standby_gpio: setting GPS standby GPIO to 0
<6>[ 18.930479] gps_brcm4750_ioctl: Setting gps gpio reset pin: 1
<6>[ 18.930572] stingray_gps_reset_gpio: setting GPS Reset GPIO to 1
<6>[ 19.003124] adb_release
<6>[ 19.003397] adb_open
<6>[ 19.028708] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 1
<6>[ 19.029017] stingray_gps_standby_gpio: setting GPS standby GPIO to 1
<6>[ 19.261164] android_usb gadget: high speed config #1: android
<6>[ 19.577060] tear_down_dma
<6>[ 19.577183] setup_dma
<6>[ 37.780346] gps_brcm4750_ioctl: Setting gps gpio standby pin to: 0
<6>[ 37.780512] stingray_gps_standby_gpio: setting GPS standby GPIO to 0

Connecting Android to a serial device using USB-Serial Converter

I am attempting to connect to a serial device from a Android tablet, via
USB-Serial Converter. In order to interface with this particular serial
device, a linux library must be used as an interface.
This library takes an integer as an argument, and tries to connect to the
device at the following location : /dev/ttySx, where x is the arguement. If
2 is provided to the library, it will look for the device at /dev/ttyS2.
Very simple.
When I connect the device to Ubuntu, there's is one simple extra step for
this device to work with the USB-Serial convert. The converter is exposed
at the location /dev/ttyUSB1. I just need to create a simple soft-link with
the serial port pattern (etc "ln -s /dev/ttyUSV1 /dev/ttyS99"). It works
perfectly.
Now the problem arises for Android. The converter is seen at
/dev/bus/usb/01/01. I never seen this convention in other project. The
question is how can I direct the I/O from /dev/ttySX to /dev/bus/usb/01/01

ehpaul said:
I am attempting to connect to a serial device from a Android tablet, via
USB-Serial Converter. In order to interface with this particular serial
device, a linux library must be used as an interface.
This library takes an integer as an argument, and tries to connect to the
device at the following location : /dev/ttySx, where x is the arguement. If
2 is provided to the library, it will look for the device at /dev/ttyS2.
Very simple.
When I connect the device to Ubuntu, there's is one simple extra step for
this device to work with the USB-Serial convert. The converter is exposed
at the location /dev/ttyUSB1. I just need to create a simple soft-link with
the serial port pattern (etc "ln -s /dev/ttyUSV1 /dev/ttyS99"). It works
perfectly.
Now the problem arises for Android. The converter is seen at
/dev/bus/usb/01/01. I never seen this convention in other project. The
question is how can I direct the I/O from /dev/ttySX to /dev/bus/usb/01/01
Click to expand...
Click to collapse
Which android device are you using and with which kernel and android build? In my case I am using kernel 3.0.+ with CM9 on a Kindle Fire and I do see the /dev/ttyUSBx getting created along with the /dev/bus/01/01. It has been a month since I tried it but I was able to see the problem you see and here is what I remember. When you plug the serial convertor both /dev get created but since the Android USB support only uses /dev/bus/usb/01/01, the kernel in order to save power "unmounts" the unused /dev/ttyUSBx after a certain time period. You can try using dmesg to see if that is happening in your case also. There is a kernel build flag that tells the kernel not to "unmount" it but I dont remember it off-hand. Best would be to use the Android USB support to talk to your device instead of the linux library if you can.
--------Update after testing it out again and checking dmesg etc---------------------------
When I plug the FTDI cable this is what shows up in dmesg:
<6>usb 1-1: new full speed USB device number 8 using musb-hdrc
<3>usb 1-1: device v0403 p6001 is not supported
<6>ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
<6>usb 1-1: Detected FT232RL
<6>usb 1-1: Number of endpoints 2
<6>usb 1-1: Endpoint 1 MaxPacketSize 64
<6>usb 1-1: Endpoint 2 MaxPacketSize 64
<6>usb 1-1: Setting MaxPacketSize 64
<6>usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
At this point if I check the filesystem I see both /dev/ttyUSB0 and /dev/bus/usb/001/0xx [ xx being the current device number ]
I can work with /dev/ttyUSB0 and all is well. Now as soon as I invoke any app that uses Android USB Host Mode API to connect
to USB (for enumeration, connection or whatever) the /dev/ttyUSB0 gets disconnected with following message from dmesg:
<6>ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
<6>ftdi_sio 1-1:1.0: device disconnected
At this point /dev/bus/usb/001/0xx is still alive and if I enumerate the USB devices using android API I see the same as the adaptor
name. So looks like till the Android USB API takes over the FTDI is available as /dev/ttyUSB0 but not afterwards.
------------------------Update ends--------------------------------

(a) If you see a /dev/ttyUSB1 device node created, then you can try the following in an Android terminal:
Code:
stty -F /dev/ttyUSB1 raw
cat /dev/ttyUSB1
If this shows data from your device, then you can use directly the device node to read()/write(), POSIX-style, without needing any library.
(b) If you cannot see a /dev/ttyUSB1 in your Android device, this means that you need to load the ftdi_sio kernel module (check android.serverbox.ch/?p=285 for instructions).

Let me link that for you:
"How to enable FTDI Support for your USB Host featuring Honeycomb Tablet (including sample native application)"
Also have a look at FTDI's Android Paper:
"White Paper: Connecting Peripherals to an Android Platform"
and this relevant blog, from this XDA thread.

pankaj013 said:
Which android device are you using and with which kernel and android build? In my case I am using kernel 3.0.+ with CM9 on a Kindle Fire and I do see the /dev/ttyUSBx getting created along with the /dev/bus/01/01. It has been a month since I tried it but I was able to see the problem you see and here is what I remember. When you plug the serial convertor both /dev get created but since the Android USB support only uses /dev/bus/usb/01/01, the kernel in order to save power "unmounts" the unused /dev/ttyUSBx after a certain time period. You can try using dmesg to see if that is happening in your case also. There is a kernel build flag that tells the kernel not to "unmount" it but I dont remember it off-hand. Best would be to use the Android USB support to talk to your device instead of the linux library if you can.
--------Update after testing it out again and checking dmesg etc---------------------------
When I plug the FTDI cable this is what shows up in dmesg:
<6>usb 1-1: new full speed USB device number 8 using musb-hdrc
<3>usb 1-1: device v0403 p6001 is not supported
<6>ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
<6>usb 1-1: Detected FT232RL
<6>usb 1-1: Number of endpoints 2
<6>usb 1-1: Endpoint 1 MaxPacketSize 64
<6>usb 1-1: Endpoint 2 MaxPacketSize 64
<6>usb 1-1: Setting MaxPacketSize 64
<6>usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0
At this point if I check the filesystem I see both /dev/ttyUSB0 and /dev/bus/usb/001/0xx [ xx being the current device number ]
I can work with /dev/ttyUSB0 and all is well. Now as soon as I invoke any app that uses Android USB Host Mode API to connect
to USB (for enumeration, connection or whatever) the /dev/ttyUSB0 gets disconnected with following message from dmesg:
<6>ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
<6>ftdi_sio 1-1:1.0: device disconnected
At this point /dev/bus/usb/001/0xx is still alive and if I enumerate the USB devices using android API I see the same as the adaptor
name. So looks like till the Android USB API takes over the FTDI is available as /dev/ttyUSB0 but not afterwards.
------------------------Update ends--------------------------------
Click to expand...
Click to collapse
are you using ftdi's code to modify it?

change /system/etc/permissions
this is from a question on stackoverflow titled "Android USB host and hidden devices" (sorry, i can't add external URLs yet). it worked like a charm on a micromax A120 canvas 2 phone (kitkat 4.4.2). now i can control my Arduino! i used busybox tools to do all the command line work (otherwise chmod wouldn't work). my steps (perhaps some were not required):
(0) install PDAnet drivers on my Windows 8 computer.
(1) root the phone using Vroot (now called iRoot). Very simple, only catch is that the su grant/deny page is partly in chinese, no big deal.
(2) install busybox and jackpal's Android-Terminal-Emulator available on github and the google play store (free).
(3) open a terminal window and become the superuser:
# su
(4) the file system may be read-only, so you might have to remount it:
# mount -o rw,remount -t yaffs2 /
or
# mount -o rw,remount -t rootfs /
or
# mount -o rw,remount -t rootfs rootfs /system
(5) make default.prop read/write:
chmod 666 /default.prop
(6) edit /default.prop, make the following changes:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
... And this is the real meat of it:
(7) To enable USB host API support you should add a file named
android.hardware.usb.host.xml and containing the following lines:
<permissions>
<feature name="android.hardware.usb.host"/>
</permissions>
into folder
/system/etc/permissions
in that folder find file named
handheld_core_hardware.xml or tablet_core_hardware.xml
and add
<feature name="android.hardware.usb.host" />
into <permissions> section.
(8) Reboot your device. Usb host api should work.

Is my Nexus 7 dead?

Okay, I have fastboot and ADB, the only way to get into recovery is through wugs toolkit. I have pushed a ROM to my phone but is says FAILED when I try to flash.
it says TWRP v 2.4.1.0 errors saying
Error flashing zip
Updating partition details...
E:Unable to mount ' /system'
E:Unable to mount ' /cache'
If I use fastboot to try and install recovery, boot, bootloads, or anything it fails as well.
C:\Program Files (x86)\WugFresh Development\data>fastboot devices
xxxxxxxxxxxxxxxxxxxx fastboot
C:\Program Files (x86)\WugFresh Development\data>fastboot erase boot
erasing 'boot'...
OKAY [ 2.531s]
finished. total time: 2.533s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Program Files (x86)\WugFresh Development\data>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.021s
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootl
oader-grouper-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
C:\Program Files (x86)\WugFresh Development\data>fastboot -w update image-nakasi
-jop40d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: xxxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.585s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 0.760s
C:\Program Files (x86)\WugFresh Development\data>
C:\Program Files (x86)\WugFresh Development\data>
(and I get the same for every file I try.
Any help is much appreciated.
Now this is my 4 year olds tablet and we woke up the other morning and it just wouldnt boot anymore. I did unlock it just for fun when we got it a couple months ago but I dont know why it would just not boot into the OS after two months.

In the situation you are in, you should NEVER use fastboot to attempt overflashing of the bootloader. All else, OK.
Try soft-booting (not flashing) a more recent recovery, e.g. TWRP 2.3.x.x or 2.4.x.x
pull it down to your computer & verify it's MD5 sig, then
fastboot boot recovery-image-name.img
If that works, via "adb shell" (once the recovery starts, ADB should work), see if you can do a
# mount /system
# mount /data
if these succeed, that means that each filesystem is OK. (Already mounted counts as a success) If it doesn't you will have to use the mke*fs tools located in the /system/bin or /sbin folder of the TWRP boot to re-initialize the /system, /data partitions as necessary.
My guess though is that if the device failed before all this happened, things might not be fixable.
If you can't even soft-boot a recovery - let us know what error message occurs.

bftb0 said:
In the situation you are in, you should NEVER use fastboot to attempt overflashing of the bootloader. All else, OK.
Try soft-booting (not flashing) a more recent recovery, e.g. TWRP 2.3.x.x or 2.4.x.x
pull it down to your computer & verify it's MD5 sig, then
fastboot boot recovery-image-name.img
If that works, via "adb shell" (once the recovery starts, ADB should work), see if you can do a
# mount /system
# mount /data
if these succeed, that means that each filesystem is OK. (Already mounted counts as a success) If it doesn't you will have to use the mke*fs tools on the /system/bin or /sbin folder of the TWRP boot to re-initialize those filesystems.
My guess though is that if the device failed before all this happened, things might not be fixable.
If you can't even soft-boot a recovery - let us know what error message occurs.
Click to expand...
Click to collapse
I went into fastboot
opened cmd
fastboot boot recovery.img
Recovery booted up
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # mount /system
mount /system
mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/APP on /system failed:
No such file or directory
~ # mount /data
mount /data
mount: mounting /dev/block/platform/sdhci-tegra.3/by-name/UDA on /data failed: N
o such file or directory
~ # # mount /system
# mount /system
~ # # mount /data
# mount /data
~ #
I tried to mount system and data in recovery and it didnt work...i tried cwm 6.0.2.3 and twrp 2.4.1.0
I see files in /sbin folder in recovery, how do I use those files?

well, if you are using the touch version of TWRP the "format data" command rebuilds the filesystem (after nuking it first) with mke2fs.
The command line for mke*fs can have lots of arguments, and off the top of my head I don't know which device plumbed into the kernel is the correct device.
Gimme a minute, I just did a factory reset on my tablet.
But yeah, if you are doing stuff manually from the command line with adb, you will be using the executables in the recovery's /sbin or /system/bin or /system/sbin (e.g. the mke2fs command).
Hang on, gotta check something.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
with your recovery running, type the command
mke2fs --help
you should see something like this:
Code:
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
I believe the commands you will want to use are something like
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
for /data and /system respectively. Give that a roll, power off the device, reboot into the bootloader, and then soft boot into your recovery again and see if /data and /system can be mounted

bftb0 said:
well, if you are using the touch version of TWRP the "format data" command rebuilds the filesystem (after nuking it first) with mke2fs.
The command line for mke*fs can have lots of arguments, and off the top of my head I don't know which device plumbed into the kernel is the correct device.
Gimme a minute, I just did a factory reset on my tablet.
But yeah, if you are doing stuff manually from the command line with adb, you will be using the executables in the recovery's /sbin or /system/bin or /system/sbin (e.g. the mke2fs command).
Hang on, gotta check something.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
with your recovery running, type the command
mke2fs --help
you should see something like this:
Code:
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
I believe the commands you will want to use are something like
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
for /data and /system respectively. Give that a roll, power off the device, reboot into the bootloader, and then soft boot into your recovery again and see if /data and /system can be mounted
Click to expand...
Click to collapse
I get
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
how so I apply the lines
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
I know that sounds dumb but I havent used adb, getting this far this fast feels pretty good. I appreciate your help!!

Skyler2Dope said:
I get
/sbin/mke2fs --help
unknown option -- -
Usage: mke2fs [-c|-l filename] [-b block-size] [-f fragment-size]
[-i bytes-per-inode] [-I inode-size] [-J journal-options]
[-G meta group size] [-N number-of-inodes]
[-m reserved-blocks-percentage] [-o creator-os]
[-g blocks-per-group] [-L volume-label] [-M last-mounted-directory]
[-O feature[,...]] [-r fs-revision] [-E extended-option[,...]]
[-T fs-type] [-U UUID] [-jnqvFKSV] device [blocks-count]
how so I apply the lines
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
I know that sounds dumb but I havent used adb, getting this far this fast feels pretty good. I appreciate your help!!
Click to expand...
Click to collapse
just type them in and hit the return key.
report any errors or successes, pls.

NRT v1.6.2 flash this stock rom instead
https://developers.google.com/android/nexus/images#nakasi
i have gotten errors on the flash that the program downloads for you before..
this saved my n7

bradman117 said:
NRT v1.6.2 flash this stock rom instead
https://developers.google.com/android/nexus/images#nakasi
i have gotten errors on the flash that the program downloads for you before..
this saved my n7
Click to expand...
Click to collapse
My partition is shot, I can't do anything with the toolkit. But I'll give it another go
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (2096 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.198s
rebooting into bootloader...
OKAY [ 7.302s]
finished. total time: 7.303s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
< waiting for device >

should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found

Skyler2Dope said:
should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found
Click to expand...
Click to collapse
add me on gtalk, [email protected]

did you try re-creating those filesystems?
probably you should add /cache in there for good measure
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p4
It is possible that when you are in fastboot mode (bootloader), the bootloader does not rely on having intact filesystems and performs a wipe and re-creation of each filesystem before it unpacks those (sparse) ext4 image files onto the targets.
But what I am suggesting above will give you more visibility into what is going on than using fastboot.
Given that you don't know where the trouble is, as I said before you should not be doing ANYTHING at this time which overflashes the bootloader - including installing full factory images.
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
Skyler2Dope said:
should it look like this
C:\Program Files (x86)\WugFresh Development\data>adb shell /sbin/mke2fs/mke2fs -
T ext4 -m 0 /dev/block/mmcblk0p9
/sbin/sh: /sbin/mke2fs/mke2fs: not found
Click to expand...
Click to collapse
NO. just type
C:\blahblah> adb shell
you will get a different prompt - which means you are using the command line on the phone at that time
and then the commands as shown previously

bftb0 said:
did you try re-creating those filesystems?
probably you should add /cache in there for good measure
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p4
It is possible that when you are in fastboot mode (bootloader), the bootloader does not rely on having intact filesystems and performs a wipe and re-creation of each filesystem before it unpacks those (sparse) ext4 image files onto the targets.
But what I am suggesting above will give you more visibility into what is going on than using fastboot.
Given that you don't know where the trouble is, as I said before you should not be doing ANYTHING at this time which overflashes the bootloader - including installing full factory images.
---------- Post added at 06:59 PM ---------- Previous post was at 06:58 PM ----------
NO. just type
C:\blahblah> adb shell
you will get a different prompt - which means you are using the command line on the phone at that time
and then the commands as shown previously
Click to expand...
Click to collapse
C:\adt-bundle-windows-x86_64\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
~ # ←[6n
does that look right?

Skyler2Dope said:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p9
mke2fs 1.41.12 (17-May-2010)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
~ # ←[6n
does that look right?
Click to expand...
Click to collapse
It looks right for the stock kernel, but stuff gets plumbed into the device tree differently depending on kernel.
Which recovery are you using?
you could try the "by name" devices:
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
(UDA -> /data, APP -> /system, CAC -> /cache)
BTW - if you haven't figured it out by now - you get "out of" the remote shell by typing the command "exit". You'll see the prompt change back to the Windows command prompt "C:\blahblahblah>"
Hmmm - those "by-name" entries are symlinks back to the same device names I gave you originally. Well, on the stock kernel anyway.
what does the command "ls -ld /dev/block/*" get you (on the adb shell) ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Send me a link to the place you downloaded your recovery image from, I can soft boot it and take a look.
either that or do a "cat /proc/partitions" and let me know what the output is.

bftb0 said:
It looks right for the stock kernel, but stuff gets plumbed into the device tree differently depending on kernel.
Which recovery are you using?
you could try the "by name" devices:
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP
mke2fs -T ext4 -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC
(UDA -> /data, APP -> /system, CAC -> /cache)
BTW - if you haven't figured it out by now - you get "out of" the remote shell by typing the command "exit". You'll see the prompt change back to the Windows command prompt "C:\blahblahblah>"
Hmmm - those "by-name" entries are symlinks back to the same device names I gave you originally. Well, on the stock kernel anyway.
what does the command "ls -ld /dev/block/*" get you (on the adb shell) ?
---------- Post added at 08:12 PM ---------- Previous post was at 08:07 PM ----------
Send me a link to the place you downloaded your recovery image from, I can soft boot it and take a look.
either that or do a "cat /proc/partitions" and let me know what the output is.
Click to expand...
Click to collapse
I am using TWRP 2.4.1.0
ls -ld /dev/block/* gets me
C:\Program Files (x86)\WugFresh Development\data>adb shell ls -ld /dev/block/*
brw------- 1 root root 7, 0 Jan 2 05:41 /dev/block/loop0
brw------- 1 root root 7, 1 Jan 2 05:41 /dev/block/loop1
brw------- 1 root root 7, 2 Jan 2 05:41 /dev/block/loop2
brw------- 1 root root 7, 3 Jan 2 05:41 /dev/block/loop3
brw------- 1 root root 7, 4 Jan 2 05:41 /dev/block/loop4
brw------- 1 root root 7, 5 Jan 2 05:41 /dev/block/loop5
brw------- 1 root root 7, 6 Jan 2 05:41 /dev/block/loop6
brw------- 1 root root 7, 7 Jan 2 05:41 /dev/block/loop7
C:\Program Files (x86)\WugFresh Development\data>adb shell cat /proc/partitions
major minor #blocks name

.
.
.
.
.
Skyler - we may well have stumbled onto the problem. I booted a couple of different recoveries, and they mostly plumb devices into the same device nodes in /dev/block.
What that suggests is that your partition table got mangled.
If it turns out that this is the case, your question "Is my Nexus 7 dead"? can probably be answered in the affirmative - until someone clever reverse-engineers the Nexus 7's APX mode.
There is a way that you can check this - with the "dmesg" output from your soft-booted recovery.
From the windows prompt, do this:
- soft boot the recovery (so it has been fairly recently booted), and once the ADB link comes up, do this:
C:\ugh> adb shell dmesg > dmesg_out.txt
this (the file "dmesg_out.txt") will have the kernel boot log in it. In an orderly boot, you would see something like this:
Code:
<6>[ 3.629591] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name
MMC32G BOOT_MULTI 0x10
<6>[ 3.631511] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.631716] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.632078] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.632304] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.632587] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 3.634589] Primary GPT is invalid, using alternate GPT.
<6>[ 3.634765] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
<6>[ 3.636710] mmcblk0boot1: unknown partition table
<6>[ 3.637896] mmcblk0boot0: unknown partition table
<6>[ 3.638149] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
note that it detects 9 partitions
and further, the command
C:\ugh> adb shell cat /proc/partitions
should display something like this:
Code:
major minor #blocks name
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
If you are missing a bunch of partitions, you have a problem with the eMMC Flash memory chip that is not currently correctable with tools in the wild.
Is that what you see - errors in the dmesg log, or a lack of partitions in /proc/partitions?

bftb0 said:
.
.
.
.
.
Skyler - we may well have stumbled onto the problem. I booted a couple of different recoveries, and they mostly plumb devices into the same device nodes in /dev/block.
What that suggests is that your partition table got mangled.
If it turns out that this is the case, your question "Is my Nexus 7 dead"? can probably be answered in the affirmative - until someone clever reverse-engineers the Nexus 7's APX mode.
There is a way that you can check this - with the "dmesg" output from your soft-booted recovery.
From the windows prompt, do this:
- soft boot the recovery (so it has been fairly recently booted), and once the ADB link comes up, do this:
C:\ugh> adb shell dmesg > dmesg_out.txt
this (the file "dmesg_out.txt") will have the kernel boot log in it. In an orderly boot, you would see something like this:
Code:
<6>[ 3.629591] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x3b78000 prod_name
MMC32G BOOT_MULTI 0x10
<6>[ 3.631511] mmc0: new high speed DDR MMC card at address 0001
<6>[ 3.631716] mmcblk mmc0:0001: Card claimed for testing.
<6>[ 3.632078] mmcblk0: mmc0:0001 MMC32G 29.7 GiB
<6>[ 3.632304] mmcblk0boot0: mmc0:0001 MMC32G partition 1 2.00 MiB
<6>[ 3.632587] mmcblk0boot1: mmc0:0001 MMC32G partition 2 2.00 MiB
<4>[ 3.634589] Primary GPT is invalid, using alternate GPT.
<6>[ 3.634765] mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8 p9
<6>[ 3.636710] mmcblk0boot1: unknown partition table
<6>[ 3.637896] mmcblk0boot0: unknown partition table
<6>[ 3.638149] [mmc]:mmc_rescan_try_freq:1907 mmc0: eMMC completed
note that it detects 9 partitions
and further, the command
C:\ugh> adb shell cat /proc/partitions
should display something like this:
Code:
major minor #blocks name
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
If you are missing a bunch of partitions, you have a problem with the eMMC Flash memory chip that is not currently correctable with tools in the wild.
Is that what you see - errors in the dmesg log, or a lack of partitions in /proc/partitions?
Click to expand...
Click to collapse
<4>[ 2.271075] GTCO usb driver version: 2.00.0006
<6>[ 2.271234] usbcore: registered new interface driver hanwang
<6>[ 2.271401] usbcore: registered new interface driver kbtab
<6>[ 2.271531] kbtab: v0.0.2:USB KB Gear JamStudio Tablet driver
<6>[ 2.271638] usbcore: registered new interface driver wacom
<6>[ 2.271769] wacom: v1.52:USB Wacom tablet driver
<4>[ 2.271841] [ektf3k]:[elan] elan_ktf3k_ts_init
<4>[ 2.272001] [ektf3k]:[ELAN] Start HW reset!
<4>[ 2.529906] [ektf3k]:The boot code is new!
<4>[ 2.709905] INOK=L
<5>[ 2.710168] smb347_charger: [cable_type_detect] Reg3F : 0x93
<5>[ 2.710486] smb347_charger: [cable_type_detect] Reg3E : 0x09
<4>[ 2.710561] Cable: CDP
<4>[ 2.710632] ========================================================
<4>[ 2.710765] battery_callback usb_cable_state = 3
<4>[ 2.710837] ========================================================
<4>[ 2.710978] inok_isr_work_function -
<6>[ 3.259898] cable_detection_work_handler(): vbus_active = 0 and is_active
= 1
<6>[ 3.260032] The USB cable is connected
<4>[ 3.310055] [ektf3k]:[elan] __hello_packet_handler: hello packet 55:55:55:
55
<4>[ 3.310189] [ektf3k]:[elan] hello packet's rc = 0
<4>[ 3.521744] [ektf3k]:[elan] __fw_packet_handler: firmware version: 0xb018
<4>[ 3.523705] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x0078
<4>[ 3.525607] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00c6
<4>[ 3.546763] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3021
<4>[ 3.546901] [ektf3k]:[Elan] Max X=2111, Max Y=1279
<6>[ 3.547105] input: elan-touchscreen as /devices/virtual/input/input0
<4>[ 3.547345] [ektf3k]:The firmware was version 0xB018 and id:0x3021
<4>[ 3.547444] [ektf3k]: /proc/ektf_dbg created
<4>[ 3.547690] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrup
t mode
<4>[ 3.547877] [ektf3k]:[ELAN]misc_register finished!!
<6>[ 3.548014] elan-ktf3k 1-0010: Update power source to 1
<6>[ 3.548383] in function ____rmi_bus_init____
<6>[ 3.548495] rmi_bus_init: successfully registered RMI bus.
<6>[ 3.548667] rmi_spi_init: registering synaptics spi driver (ref=124)
<6>[ 3.548742] driver.owner = 0x0
<6>[ 3.548872] driver.name = rmi_spi
<6>[ 3.548944] id_table[0].name = rmi
<6>[ 3.549073] id_table[1].name = rmi_spi
<6>[ 3.549145] probe function ptr = 0xc064f2b8
<6>[ 3.549297] in function ____rmi_register_driver____
<6>[ 3.549389] in function ____rmi_get_function_handler____
<6>[ 3.549523] in function ____rmi_get_function_handler____
<6>[ 3.549596] in function ____rmi_get_function_handler____
<6>[ 3.549727] in function ____rmi_get_function_handler____
<6>[ 3.549798] in function ____rmi_get_function_handler____
<6>[ 3.549947] in function ____rmi_get_function_handler____
<6>[ 3.550242] lid_init+ #####
<5>[ 3.550316] hall_sensor: [lid_init] start LID init.....
<6>[ 3.550672] input: lid_input as /devices/virtual/input/input1
<6>[ 3.550875] Wake28 for irq=374
<6>[ 3.551041] Wake28 for irq=374
<6>[ 3.551114] Enabling wake28
<6>[ 3.581073] using rtc device, max77663-rtc, for alarms
<6>[ 3.581222] max77663-rtc max77663-rtc.0: rtc core: registered max77663-rtc
as rtc0
<6>[ 3.581783] i2c /dev entries driver
<6>[ 3.582240] Linux video capture interface: v2.00
<6>[ 3.582387] usbcore: registered new interface driver uvcvideo
<6>[ 3.582461] USB Video Class driver (1.1.1)
<6>[ 3.582652] trpc_sema_init: registered misc dev 10:45
<6>[ 3.582782] trpc_node_register: Adding 'local' to node list
<6>[ 3.583912] nvavp nvavp: allocated IOVM at ff00000 for AVP os
<6>[ 3.584248] tegra_camera tegra_camera: tegra_camera_probe
<6>[ 3.584603] sensor_init+ #####
<6>[ 3.584706] mi1040 sensor_probe
<6>[ 3.584912] sensor_init- #####
<6>[ 3.585084] al3010_init+ #####
<4>[ 3.585157] light sensor info : al3010 init
<4>[ 3.585991] light sensor info : al3010 probe successed
<6>[ 3.586127] al3010 2-001c: driver version 1.0 enabled
<4>[ 3.586355] i2c-core: driver [al3010] using legacy suspend method
<4>[ 3.586491] i2c-core: driver [al3010] using legacy resume method
<6>[ 3.586572] al3010_init- #####
<6>[ 3.586918] device-mapper: uevent: version 1.0.3
<6>[ 3.587154] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: d
[email protected]
<6>[ 3.587314] Bluetooth: HCI UART driver ver 2.2
<6>[ 3.587388] Bluetooth: HCI H4 protocol initialized
<6>[ 3.587461] Bluetooth: HCILL protocol initialized
<6>[ 3.587592] Bluetooth: BlueSleep Mode Driver Ver 1.1
<6>[ 3.587714] Wake7 for irq=390
<6>[ 3.588340] cpuidle: using governor ladder
<6>[ 3.588764] cpuidle: using governor menu
<6>[ 3.588884] sdhci: Secure Digital Host Controller Interface driver
<6>[ 3.589016] sdhci: Copyright(c) Pierre Ossman
<6>[ 3.589088] sdhci-pltfm: SDHCI platform and OF driver helper
<6>[ 3.589220] sdhci_tegra_init+ #####
<6>[ 3.589391] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported
for sdhci-tegra.3
<4>[ 3.590545] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.591751] Registered led device: mmc0::
<6>[ 3.595172] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using
ADMA
<6>[ 3.595304] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported
for sdhci-tegra.2
<4>[ 3.596453] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.597656] Registered led device: mmc1::
<6>[ 3.599941] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using
ADMA
<6>[ 3.600056] sdhci_tegra_init- #####
<7>[ 3.600422] Registered led device: statled
<6>[ 3.601595] tegra-se tegra-se: tegra_se_probe: complete
<6>[ 3.603034] usbcore: registered new interface driver usbhid
<6>[ 3.603175] usbhid: USB HID core driver
<6>[ 3.603501] logger: created 256K log 'log_main'
<6>[ 3.603696] logger: created 256K log 'log_events'
<6>[ 3.603823] logger: created 256K log 'log_radio'
<6>[ 3.604008] logger: created 256K log 'log_system'
<6>[ 4.150710] inv_mpu_probe: Probe name mpu6050
<6>[ 4.150789] i2c i2c-2: MPU6050 is ready to go!
<4>[ 4.151024] i2c-core: driver [LTR_558ALS] using legacy suspend method
<4>[ 4.151100] i2c-core: driver [LTR_558ALS] using legacy resume method
<6>[ 4.152010] inv_ami306_probe: Probe name ami306
<6>[ 4.649906] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
<4>[ 4.690540] rt5640_modinit
<4>[ 4.690642] rt5640_i2c_probe
<4>[ 4.690753] i2c-core: driver [rt5640] using legacy suspend method
<4>[ 4.690885] i2c-core: driver [rt5640] using legacy resume method
<5>[ 4.710594] bq27541_get_psp status: Full ret= 0x0201
<5>[ 4.711314] bq27541_get_psp voltage_now= 4157000 uV
<5>[ 4.711963] bq27541_get_psp current_now= -172000 uA
<5>[ 4.712664] bq27541_get_capacity = 100% ret= 100
<5>[ 4.713310] bq27541_get_psp temperature= 289 (0.1óXC)
<6>[ 4.921173] DSP version code = 0x501a
<4>[ 4.921407] ************************realtek_ce_init_hwdep*****************
********************
<4>[ 4.921545] do_rt5640_dsp_set_mode mode=0
<6>[ 4.921628] rt5640 4-001c: w->name=SDI1 TX Mux
<6>[ 4.921701] rt5640 4-001c: path->name=IF2 path->connect=0
<6>[ 4.921833] rt5640 4-001c: path->name=IF1 path->connect=1
<6>[ 4.921978] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.922113] rt5640 4-001c: path->name=DAC L1 Switch connect=1
<6>[ 4.922241] rt5640 4-001c: w->name=Stereo DAC MIXL
<6>[ 4.922375] rt5640 4-001c: path->name=DAC L2 Switch connect=0
<6>[ 4.922655] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.922791] rt5640 4-001c: path->name=DAC R1 Switch connect=1
<6>[ 4.922918] rt5640 4-001c: w->name=Stereo DAC MIXR
<6>[ 4.923054] rt5640 4-001c: path->name=DAC R2 Switch connect=0
<6>[ 4.923333] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.923410] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.923538] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.923613] rt5640 4-001c: path->name=ADC1 Switch connect=1
<6>[ 4.923797] rt5640 4-001c: w->name=Stereo ADC MIXL
<6>[ 4.923873] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.924055] rt5640 4-001c: w->name=Stereo ADC MIXR
<6>[ 4.924130] rt5640 4-001c: path->name=ADC2 Switch connect=1
<6>[ 4.924311] rt5640 4-001c: w->name=Mono ADC MIXL
<6>[ 4.924386] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.924569] rt5640 4-001c: w->name=Mono ADC MIXR
<6>[ 4.924643] rt5640 4-001c: path->name=ADC2 Switch connect=0
<6>[ 4.931835] asoc: rt5640-aif1 <-> tegra30-i2s.1 mapping ok
<6>[ 4.934256] asoc: dit-hifi <-> tegra30-spdif mapping ok
<6>[ 4.938087] asoc: dit-hifi <-> tegra30-i2s.3 mapping ok
<6>[ 4.938881] headset_init+ #####
<4>[ 4.938954] HEADSET: Headset detection init
<4>[ 4.939240] HEADSET: Headset detection mode
<4>[ 4.939315] HEADSET: Config Headset Button detection gpio
<7>[ 4.939389] gpio_request: gpio-186 (btn_INT) status -16
<4>[ 4.939521] HEADSET: Config uart<->headphone gpio
<4>[ 4.939592] HEADSET: Config Jack-in detection gpio
<4>[ 4.939722] HEADSET: Turn on micbias power
<6>[ 4.939800] Wake12 for irq=402
<6>[ 4.939942] Wake12 for irq=402
<6>[ 4.940073] Enabling wake12
<6>[ 4.940145] gpio bank wake found: wake12 for irq=119
<6>[ 4.940217] Enabling wake12
<4>[ 4.959895] HEADSET: Turn off micbias power
<4>[ 4.959977] HEADSET: Config LineOut detection gpio
<7>[ 4.960051] gpio_request: gpio-179 (lineout_int) status -16
<6>[ 4.960182] headset_init- #####
<6>[ 4.960253] ALSA device list:
<6>[ 4.960324] #0: HDA NVIDIA Tegra at 0x70038000 irq 113
<6>[ 4.960453] #1: tegra-rt5640
<6>[ 4.960734] oprofile: using arm/armv7-ca9
<6>[ 4.960914] GACT probability NOT on
<6>[ 4.961050] Mirror/redirect action on
<6>[ 4.961123] u32 classifier
<6>[ 4.961193] Actions configured
<6>[ 4.961325] Netfilter messages via NETLINK v0.30.
<6>[ 4.961462] nf_conntrack version 0.5.0 (15580 buckets, 62320 max)
<6>[ 4.961848] ctnetlink v0.93: registering with nfnetlink.
<6>[ 4.961958] NF_TPROXY: Transparent proxy support initialized, version 4.1.
0
<6>[ 4.962091] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>[ 4.962439] xt_time: kernel timezone is -0000
<6>[ 4.962722] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.962960] arp_tables: (C) 2002 David S. Miller
<6>[ 4.963069] TCP cubic registered
<6>[ 4.963314] NET: Registered protocol family 10
<6>[ 4.964057] Mobile IPv6
<6>[ 4.964153] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 4.964423] IPv6 over IPv4 tunneling driver
<6>[ 4.965272] NET: Registered protocol family 17
<6>[ 4.965424] NET: Registered protocol family 15
<6>[ 4.965602] Bluetooth: RFCOMM TTY layer initialized
<6>[ 4.965687] Bluetooth: RFCOMM socket layer initialized
<6>[ 4.965818] Bluetooth: RFCOMM ver 1.11
<6>[ 4.965891] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>[ 4.966024] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>[ 4.966249] NET: Registered protocol family 37
<6>[ 4.966326] VFP support v0.3: implementor 41 architecture 3 part 30 varian
t 9 rev 4
<5>[ 4.966494] Registering SWP/SWPB emulation handler
<4>[ 4.974201] Do not disable PWM clock when kernel inits
<4>[ 4.974289] Disabling clocks left on by bootloader:
<4>[ 4.974361] fuse_burn
<4>[ 4.974498] cclk_lp
<4>[ 4.974570] pll_x_out0
<4>[ 4.974642] pll_d2_out0
<4>[ 4.974712] pll_d_out0
<4>[ 4.974842] pll_p_out2
<4>[ 4.974918] pll_c_out1
<4>[ 4.974992] pll_m_out1
<6>[ 4.975161] CPU rate: 1000 MHz
<3>[ 4.975332] tegra_fuse_program_init: no vdd_fuse. fuse write disabled
<4>[ 4.975836] tegra3_dvfs: minimum cap.cbus rate 228000000 requires 1000 mV
<6>[ 4.976034] tegra dvfs: tegra sysfs cap interface is initialized
<6>[ 4.976374] tegra_actmon.emc: Completed initialization (0)
<6>[ 4.976649] tegra_actmon.avp: Completed initialization (0)
<4>[ 4.977660] regulator_init_complete: fixed_reg_cdc_en: incomplete constrai
nts, leaving on
<4>[ 4.977806] regulator_init_complete: max77663_ldo8: incomplete constraints
, leaving on
<4>[ 4.977945] regulator_init_complete: max77663_ldo4: incomplete constraints
, leaving on
<4>[ 4.978188] ## wifi_probe
<4>[ 4.978323] wifi_set_power = 1
<3>[ 4.978395] Powering on wifi
<4>[ 5.278776] wifi_set_carddetect = 1
<4>[ 5.278986]
<4>[ 5.278989] Dongle Host Driver, version 5.90.195.75
<4>[ 5.278993] Compiled in drivers/net/wireless/bcmdhd on Oct 14 2012 at 16:3
1:58
<3>[ 5.649903] mmc0: error -110 whilst initialising MMC card
<3>[ 7.709905] mmc0: error -110 whilst initialising MMC card
<3>[ 9.769905] mmc0: error -110 whilst initialising MMC card
<3>[ 11.839906] mmc0: error -110 whilst initialising MMC card
<6>[ 11.894505] mmc1: new high speed SDIO card at address 0001
<4>[ 11.895367] F1 signature read @0x18000000=0x16044330
<4>[ 11.899466] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 11.900153] wl_create_event_handler thr:69 started
<4>[ 11.900863] p2p0: P2P Interface Registered
<4>[ 11.901081] dhd_attach thr:6a started
<4>[ 11.901224] dhd_attach thr:6b started
<4>[ 11.901371] dhd_attach thr:6c started
<4>[ 11.901653] wifi_get_mac_addr
<4>[ 11.902142] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 0
0:90:4c:11:22:33
<4>[ 11.902293] wifi_set_power = 0
<3>[ 11.902366] Powering off wifi
<6>[ 11.909977] [mmc]:mmc_rescan_try_freq:1903 mmc1: sdio completed
<4>[ 12.202737] =========== WLAN placed in RESET ========
<6>[ 12.202902] Wake24 for irq=392
<6>[ 12.203228] input: gpio-keys as /devices/platform/gpio-keys.0/input/input2
<6>[ 12.203445] gpio_keys: Released KEY_POWER
<6>[ 12.203523] gpio_keys: Released KEY_VOLUMEUP
<6>[ 12.203654] gpio_keys: Released KEY_VOLUMEDOWN
<6>[ 12.218332] max77663-rtc max77663-rtc.0: setting system clock to 2000-01-0
2 05:54:49 UTC (946792489)
<4>[ 12.218590] Warning: unable to open an initial console.
<6>[ 12.218875] Freeing init memory: 272K
<5>[ 12.225884] bq27541_get_psp status: Full ret= 0x0201
<5>[ 12.226540] bq27541_get_psp voltage_now= 4168000 uV
<5>[ 12.227244] bq27541_get_psp current_now= -10000 uA
<5>[ 12.227888] bq27541_get_capacity = 100% ret= 100
<5>[ 12.228534] bq27541_get_psp temperature= 289 (0.1óXC)
<3>[ 12.283042] init: Unable to open persistent property directory /data/prope
rty errno: 2
<3>[ 12.284820] android_usb: already disabled
<3>[ 12.285298] android_usb: already disabled
<6>[ 12.287073] adb_open
<6>[ 12.287178] adb_open(adbd)
<6>[ 12.287329] adb_bind_config
<6>[ 12.453844] android_work: did not send uevent (0 0 (null))
<5>[ 12.635110] bq27541_get_capacity = 100% ret= 100
<5>[ 12.635916] bq27541_get_psp status: Full ret= 0x0201
<6>[ 12.692380] android_work: sent uevent USB_STATE=CONNECTED
<6>[ 12.719994] set_config : usb set config wake lock ++
<6>[ 12.720088] android_usb gadget: high speed config #1: android
<6>[ 12.720350] android_work: sent uevent USB_STATE=CONFIGURED
<6>[ 13.279938] cable_detection_work_handler(): vbus_active = 0 and is_active
= 1
<6>[ 13.280080] The USB cable is connected
<6>[ 13.280157] elan-ktf3k 1-0010: Update power source to 1
<4>[ 46.107840] adbd (118): /proc/118/oom_adj is deprecated, please use /proc/
118/oom_score_adj instead.
<5>[ 64.800603] bq27541_get_psp status: Full ret= 0x0200
<5>[ 64.801328] bq27541_get_psp voltage_now= 4173000 uV
<5>[ 64.801977] bq27541_get_psp current_now= 73000 uA
<5>[ 64.802680] bq27541_get_capacity = 100% ret= 100
<5>[ 64.803329] bq27541_get_psp temperature= 288 (0.1óXC)
<5>[ 72.747283] bq27541_get_capacity = 100% ret= 100
<5>[ 72.748015] bq27541_get_psp status: Full ret= 0x0200
C:\Program Files (x86)\WugFresh Development\data>
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
YEAH EMPTY lol

Skyler2Dope said:
<4>[ 2.271075]
<6>[ 3.589220] sdhci_tegra_init+ #####
<6>[ 3.589391] sdhci-tegra sdhci-tegra.3: Error: tegra3 io dpd not supported
for sdhci-tegra.3
<4>[ 3.590545] mmc0: Invalid maximum block size, assuming 512 bytes
<7>[ 3.591751] Registered led device: mmc0::
<6>[ 3.595172] mmc0: SDHCI controller on sdhci-tegra.3 [sdhci-tegra.3] using
ADMA
<6>[ 3.595304] sdhci-tegra sdhci-tegra.2: Error: tegra3 io dpd not supported
for sdhci-tegra.2
<4>[ 3.596453] mmc1: Invalid maximum block size, assuming 512 bytes
<7>[ 3.597656] Registered led device: mmc1::
<6>[ 3.599941] mmc1: SDHCI controller on sdhci-tegra.2 [sdhci-tegra.2] using
ADMA
...
<3>[ 5.649903] mmc0: error -110 whilst initialising MMC card
<3>[ 7.709905] mmc0: error -110 whilst initialising MMC card
<3>[ 9.769905] mmc0: error -110 whilst initialising MMC card
<3>[ 11.839906] mmc0: error -110 whilst initialising MMC card
<6>[ 11.894505] mmc1: new high speed SDIO card at address 0001
<4>[ 11.895367] F1 signature read @0x18000000=0x16044330
Click to expand...
Click to collapse
ouch.
Skyler2Dope said:
C:\Program Files (x86)\WugFresh Development\data>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
YEAH EMPTY lol
Click to expand...
Click to collapse
Well, that explains that. Some bootloaders (usually S-OFF engineering bootloaders, not public release bootloaders) allow re-partitioning if the device gets completely stuffed up, but generally the public release bootloaders do not - which explains why flashing the factory roms from fastboot mode was failing - it too needs to read the partition table(s).
The Tegra 3 has this mode called "APX" which is similar to the "download mode" on Samsung phones where the PC application "Kies" can be used for manipulating Samsung phones at a very low level, including things like repartitioning the basic flash filesystems. It's what makes those Galaxy phones nearly impossible to brick, short of hardware failure.
Until we have tools for working in APX mode though, situations like yours are a dead end even for rooters.
RMA time? I don't think it was anything you or the 4-year old did by the way - I would engage with Asus/Google with a completely clear conscience.

bftb0 said:
ouch.
Well, that explains that. Some bootloaders (usually S-OFF engineering bootloaders, not public release bootloaders) allow re-partitioning if the device gets completely stuffed up, but generally the public release bootloaders do not - which explains why flashing the factory roms from fastboot mode was failing - it too needs to read the partition table(s).
The Tegra 3 has this mode called "APX" which is similar to the "download mode" on Samsung phones where the PC application "Kies" can be used for manipulating Samsung phones at a very low level, including things like repartitioning the basic flash filesystems. It's what makes those Galaxy phones nearly impossible to brick, short of hardware failure.
Until we have tools for working in APX mode though, situations like yours are a dead end even for rooters.
RMA time? I don't think it was anything you or the 4-year old did by the way - I would engage with Asus/Google with a completely clear conscience.
Click to expand...
Click to collapse
I called and I am doing an RMA, Ill be shipping it off tomorrow or the next day. I will post back if they actually send me another one. Google was amazing by the way, a real pleasure to deal with. I appreciate all the time you and bradman put in tonight to help me figure this out. I REALLY REALLY REALLY appreciate your time and efforts! This has by far been the best experience I have had on any forum! You guys are awesome!

Well they received my device. Waiting to see if I get charged or get a new one.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

bftb0
You deserve a lot more 'thanks' in your posts for doing so much to help the OP.
Sent from my Nexus 7 using xda premium