Kindle Touch Won't Enter Diags...? - Page 2

TBennettcc · 04-09-2014, 08:34 PM

Okay guys, it still seems that I'm stuck. I'm going to post some more serial logs here, and I'd appreciate it if you could take a look and see what's wrong. Everything I've tried to follow in the "Simple De-bricking" thread, silver18's "noob guide", and Kubrick, have all failed. I cannot copy any files to the USB drive when it is connected to Windows, Mac OS X, or Ubuntu.

As a side note, I have now been able to reliably boot into diags mode by viewing a serial console while booting, and hitting enter as soon as I see the following lines:

Spoiler:

Here is the serial console output of all the commands I've run. Please let me know if you'd like to see the output of any other commands:

Spoiler:

Boot to diags, then try to enable USBNet (note all the files not found towards the end (/cust and /tmp))... (can anybody tell me why this doesn't work? Am I missing this file --> /mnt/base-us/USBnet.xml ? Is it something else?):

Spoiler:

Code:

U-Boot 2009.08-lab126 (Nov 10 2011 - 00:14:40)

CPU:   Freescale i.MX50 family 1.1V at 800 MHz
mx50 pll1: 800MHz
mx50 pll2: 400MHz
mx50 pll3: 216MHz
ipg clock     : 50000000Hz
ipg per clock : 50000000Hz
uart clock    : 24000000Hz
ahb clock     : 100000000Hz
axi_a clock   : 400000000Hz
axi_b clock   : 200000000Hz
weim_clock    : 100000000Hz
ddr clock     : 800000000Hz
esdhc1 clock  : 80000000Hz
esdhc2 clock  : 80000000Hz
esdhc3 clock  : 80000000Hz
esdhc4 clock  : 80000000Hz
MMC:  FSL_ESDHC: 0, FSL_ESDHC: 1
Board: Whitney WFO
Boot Reason: [POR]
Boot Device: MMC
Board Id: 00614011147515QA
S/N: B011140714750V3Q
DRAM:  256 MB
Using default environment

In:    serial
Out:   logbuff
Err:   logbuff
Quick Memory Test 0x70000000, 0xfffe000
POST done in 13 ms
BOOTMODE OVERRIDE: DIAGS
Hit any key to stop autoboot:  1  0 
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5122560 Bytes =  4.9 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...

mxc_spi mxc_spi.0: can't setup spi1.0, status -22
mxc_spi mxc_spi.2: chipselect 0 already in use
2.6.31-rt11-lab126 #1 Wed Nov 9 15:20:18 PST 2011 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (35504 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (43336 bytes)
INFO:eink initialized... (486400 bytes)
INFO:DIAGS MODE
Press [ENTER] for recovery menu...       0 /
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Loaded module /lib/modules/arcotg_udc.ko  (50332 bytes)
INFO:Loaded module /lib/modules/g_file_storage.ko recovery_mode=1 (34988 bytes)
Charge: 96% [#########################################################:]
INFO:Charger limit of 65% reached, charging disabled


Menu
====
3. Load MMC0 over USB storage
4. Erase MMC0
I. Initialize Partition Table (fdisk) and format FAT
O. Format and overwrite FAT partition
E. Export FAT partition
U. Update using update*.bin file on FAT partition
M. Update using update*.bin file on FAT partition of second MMC port
D. dmesg / kernel printk ring buffer.
Q. quit
Choose:  10 /  9 -  8 \  7 |  6 /  5 -  4 \  3 |  2 /  1 -
Menu timeout
BOOTING DEFAULT.
  argc == 11
  argv[0]: "kinit"
  argv[1]: "consoleblank=0"
  argv[2]: "rootwait"
  argv[3]: "ro"
  argv[4]: "ip=off"
  argv[5]: "root=/dev/mmcblk0p2"
  argv[6]: "quiet"
  argv[7]: "user_debug=31"
  argv[8]: "eink=fslepdc"
  argv[9]: "video=mxcepdcfb:E60,bpp=8"
  argv[10]: "console=ttymxc0,115200"
  argc == 4
  argv[0]: "IP-Config"
  argv[1]: "-i"
  argv[2]: "Linux kinit"
  argv[3]: "ip=off"
IP-Config: no devices to configure
kinit: do_mounts
kinit: name_to_dev_t(/dev/mmcblk0p2) = dev(179,2)
kinit: root_dev = dev(179,2)
kinit: /dev/root appears to be a ext3 filesystem
kinit: trying to mount /dev/root on /root with type ext3
kinit: Mounted root (ext3 filesystem) readonly.

init started: BusyBox v1.17.1 (2011-11-09 15:05:40 PST)

starting pid 478, tty '': '/etc/init.d/rcS'
/etc/init.d/rcS: line 85: boot_milestone: not found
system: I rcS:def:starting /etc/rcS.d/S50diags
USER=root
prevlevel=N
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
READ_AHEAD=4
USER=root
prevlevel=N
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
IO_SCHED=anticipatory
USER=root
prevlevel=N
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/
VERBOSE=no
TMP_SIZE=32M
info firsttime:mount_rw:time=13400:Mounting root RW for first boot
info firsttime:mtab:Linking /var/tmp:
info firsttime:mtab:Linking Kindle Registry:
info firsttime:xorgconf:Linking xorg.conf:
info firsttime:guid:Generating guid:
ln: /usr/share/fonts/X11/misc/cursor.pcf: No such file or directory
info firsttime:mount_ro:time=13640:Mounting root RO
elevator: type  not found

info system:start:time=13710:
/etc/rcS.d/S50diags: line 462: f_proto: not found
info system:config:platform=yoshi,board=whitney,rev=20,proto=N,wifi=Y,wan=N:
info system:done:time=14020:
info zforce:start:version=2.0b0r12:
/etc/rcS.d/S50diags: line 462: iptables-restore: not found
/opt/ar6k/include/dbglog.h.save: No such file or directory
info userstore:run:time=14900,action=start:
info userstore:found_bootup_flag::Found BOOTUP flag file
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
      8192 bytes per cluster
        32 reserved sectors
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
   1687040 bytes per FAT (= 3295 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 3390464 (sector 6622)
    421729 data clusters (3454803968 bytes)
32 sectors/track, 64 heads
         0 hidden sectors
   6754288 sectors total
FATs differ but appear to be intact. Using first FAT.
/update-2004410010-fwo.bin
  Contains a free cluster (10240). Assuming EOF.
/update-2004410010-fwo.bin
  File size is 119752543 bytes, cluster chain length is 655360 bytes.
  Truncating file to 655360 bytes.
/system/userannotlog
  Contains a free cluster (123597). Assuming EOF.
/system/userannotlog
  File size is 1329 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
Orphaned long file name part "a5cb7b071daf4030db8d"
  Auto-deleting.
Long filename fragment "y921d706224ad" found outside a LFN sequence.
  (Maybe the start bit is missing on the last fragment)
  Not auto-correcting this.
Checksum in long filename part wrong (7f vs. expected b1).
  Not auto-correcting this.
/system/Search Indexes/Index.db
  Contains a free cluster (220921). Assuming EOF.
/system/Search Indexes/Index.db
  File size is 2195456 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/Index.lg
  Contains a free cluster (227350). Assuming EOF.
/system/Search Indexes/Index.lg
  File size is 1560613 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/Y921D7~1
  Contains a free cluster (146045). Assuming EOF.
/system/Search Indexes/Y921D7~1
  File size is 245 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/yd1c082247831804c263b7e13d41924f4
  Contains a free cluster (146643). Assuming EOF.
/system/Search Indexes/yd1c082247831804c263b7e13d41924f4
  File size is 253 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/ya63dba0456b53c707bd4b55bc25a40b2
  Contains a free cluster (146201). Assuming EOF.
/system/Search Indexes/ya63dba0456b53c707bd4b55bc25a40b2
  File size is 60823 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/y5f103dc898dff919a9ca951a65f9e6d1
  Contains a free cluster (146656). Assuming EOF.
/system/Search Indexes/y5f103dc898dff919a9ca951a65f9e6d1
  File size is 253 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/yaa77f2e99d57b14d93a637b94db306f4
  Contains a free cluster (146699). Assuming EOF.
/system/Search Indexes/yaa77f2e99d57b14d93a637b94db306f4
  File size is 134287 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/yd49068a5934d704efc74ea4a2e749771
  Contains a free cluster (148535). Assuming EOF.
/system/Search Indexes/yd49068a5934d704efc74ea4a2e749771
  File size is 247 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/y27d0e7b0910f70a6a203c855f0dff212
  Contains a free cluster (148549). Assuming EOF.
/system/Search Indexes/y27d0e7b0910f70a6a203c855f0dff212
  File size is 247 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/Search Indexes/y4cfacd60f67bbdd656c6d8194ed68c3a
  Contains a free cluster (148574). Assuming EOF.
/system/Search Indexes/y4cfacd60f67bbdd656c6d8194ed68c3a
  File size is 60103 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/acw/stock-xray-20120814010316.acx
  Contains a free cluster (188580). Assuming EOF.
/system/acw/stock-xray-20120814010316.acx
  File size is 22899 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/acw/stock-endactions-20120814010316.acx
  Contains a free cluster (188583). Assuming EOF.
/system/acw/stock-endactions-20120814010316.acx
  File size is 23516 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/acw/stock-corrections-20120405030052.acx
  Contains a free cluster (188586). Assuming EOF.
/system/acw/stock-corrections-20120405030052.acx
  File size is 18301 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/acw/stock-gotoui-20120405030052.acx
  Contains a free cluster (188589). Assuming EOF.
/system/acw/stock-gotoui-20120405030052.acx
  File size is 12232 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/acw/stock-translator-20120405030052.acx
  Contains a free cluster (188591). Assuming EOF.
/system/acw/stock-translator-20120405030052.acx
  File size is 20735 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/acw/stock-wikipedia-20120405030052.acx
  Contains a free cluster (188594). Assuming EOF.
/system/acw/stock-wikipedia-20120405030052.acx
  File size is 19019 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_29965.jpg
  Contains a free cluster (137633). Assuming EOF.
/system/thumbnails/thumbnail_29965.jpg
  File size is 10241 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_29847.jpg
  Contains a free cluster (123596). Assuming EOF.
/system/thumbnails/thumbnail_29847.jpg
  File size is 5290 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_11186.jpg
  Contains a free cluster (152177). Assuming EOF.
/system/thumbnails/thumbnail_11186.jpg
  File size is 4338 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_29986.jpg
  Contains a free cluster (140355). Assuming EOF.
/system/thumbnails/thumbnail_29986.jpg
  File size is 4522 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B002RKRSKG_EBOK_portrait.jpg
  Contains a free cluster (221084). Assuming EOF.
/system/thumbnails/thumbnail_B002RKRSKG_EBOK_portrait.jpg
  File size is 9442 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B006WLYSSQ_EBOK_portrait.jpg
  Contains a free cluster (221109). Assuming EOF.
/system/thumbnails/thumbnail_B006WLYSSQ_EBOK_portrait.jpg
  File size is 12127 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B0050C47RA_EBOK_portrait.jpg
  Contains a free cluster (220814). Assuming EOF.
/system/thumbnails/thumbnail_B0050C47RA_EBOK_portrait.jpg
  File size is 9738 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B0050BXW8Q_EBOK_portrait.jpg
  Contains a free cluster (220816). Assuming EOF.
/system/thumbnails/thumbnail_B0050BXW8Q_EBOK_portrait.jpg
  File size is 9853 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B0058H20RQ_EBOK_portrait.jpg
  Contains a free cluster (220818). Assuming EOF.
/system/thumbnails/thumbnail_B0058H20RQ_EBOK_portrait.jpg
  File size is 21050 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B005064LTK_EBOK_portrait.jpg
  Contains a free cluster (220822). Assuming EOF.
/system/thumbnails/thumbnail_B005064LTK_EBOK_portrait.jpg
  File size is 9067 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B006OG53X8_EBOK_portrait.jpg
  Contains a free cluster (220812). Assuming EOF.
/system/thumbnails/thumbnail_B006OG53X8_EBOK_portrait.jpg
  File size is 13591 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B005306NQM_EBOK_portrait.jpg
  Contains a free cluster (220821). Assuming EOF.
/system/thumbnails/thumbnail_B005306NQM_EBOK_portrait.jpg
  File size is 4369 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/system/thumbnails/thumbnail_B0050BXW7W_EBOK_portrait.jpg
  Contains a free cluster (220824). Assuming EOF.
/system/thumbnails/thumbnail_B0050BXW7W_EBOK_portrait.jpg
  File size is 8079 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/My Clippings.txt
  Contains a free cluster (26474). Assuming EOF.
/documents/My Clippings.txt
  File size is 136 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/GLORIO~1.AZW
  Contains a free cluster (2960). Assuming EOF.
/documents/GLORIO~1.AZW
  File size is 802084 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/dictionaries/Oxford_Dictionary_of_English.azw
  Contains a free cluster (84975). Assuming EOF.
/documents/dictionaries/Oxford_Dictionary_of_English.azw
  File size is 21220553 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/dictionaries/Oxford_Dictionary_of_English.sdr
  Contains a free cluster (123576). Assuming EOF.
/documents/dictionaries/The_New_Oxford_American_Dictionary.sdr/The_New_Oxford_American_Dictionary.mbs
  Contains a free cluster (211455). Assuming EOF.
/documents/dictionaries/The_New_Oxford_American_Dictionary.sdr/The_New_Oxford_American_Dictionary.mbs
  File size is 195 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/dictionaries/The_New_Oxford_American_Dictionary.sdr/The_New_Oxford_American_Dictionary.mbp1
  Contains a free cluster (211454). Assuming EOF.
/documents/dictionaries/The_New_Oxford_American_Dictionary.sdr/The_New_Oxford_American_Dictionary.mbp1
  File size is 215 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/dictionaries/The_New_Oxford_American_Dictionary.sdr/EndActions.data.B0053VMNY2.asc
  Contains a free cluster (207365). Assuming EOF.
/documents/dictionaries/The_New_Oxford_American_Dictionary.sdr/EndActions.data.B0053VMNY2.asc
  File size is 217 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Great Expectations (Modern Library Classics)_B002RKSUBC.sdr/Great Expectations (Modern Library Classics)_B002RKSUBC.apnx
  Contains a free cluster (157112). Assuming EOF.
/documents/Great Expectations (Modern Library Classics)_B002RKSUBC.sdr/Great Expectations (Modern Library Classics)_B002RKSUBC.apnx
  File size is 1711 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/The Holy Bible, English Standard Version_B001EOCFU4.phl
  Contains a free cluster (152292). Assuming EOF.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/The Holy Bible, English Standard Version_B001EOCFU4.phl
  File size is 366 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/The Holy Bible, English Standard Version_B001EOCFU4.mbs
  Contains a free cluster (152321). Assuming EOF.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/The Holy Bible, English Standard Version_B001EOCFU4.mbs
  File size is 215 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/The Holy Bible, English Standard Version_B001EOCFU4.mbp1
  Contains a free cluster (152320). Assuming EOF.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/The Holy Bible, English Standard Version_B001EOCFU4.mbp1
  File size is 5035 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/EndActions.data.B001EOCFU4.asc
  Contains a free cluster (152291). Assuming EOF.
/documents/The Holy Bible, English Standard Version_B001EOCFU4.sdr/EndActions.data.B001EOCFU4.asc
  File size is 449 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/My Clippings.sdr/My Clippings.mbp1
  Contains a free cluster (130203). Assuming EOF.
/documents/My Clippings.sdr/My Clippings.mbp1
  File size is 86 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/My Clippings.sdr/My Clippings.mbs
  Contains a free cluster (130204). Assuming EOF.
/documents/My Clippings.sdr/My Clippings.mbs
  File size is 176 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Kindle User's Guide_B0058H1LW6.sdr/Kindle User's Guide_B0058H1LW6.phl
  Contains a free cluster (137721). Assuming EOF.
/documents/Kindle User's Guide_B0058H1LW6.sdr/Kindle User's Guide_B0058H1LW6.phl
  File size is 266 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Kindle User's Guide_B0058H1LW6.sdr/Kindle User's Guide_B0058H1LW6.mbs
  Contains a free cluster (137729). Assuming EOF.
/documents/Kindle User's Guide_B0058H1LW6.sdr/Kindle User's Guide_B0058H1LW6.mbs
  File size is 306 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Kindle User's Guide_B0058H1LW6.sdr/Kindle User's Guide_B0058H1LW6.mbp1
  Contains a free cluster (137728). Assuming EOF.
/documents/Kindle User's Guide_B0058H1LW6.sdr/Kindle User's Guide_B0058H1LW6.mbp1
  File size is 211 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Kindle User's Guide_B0058H1LW6.sdr/EndActions.data.B0058H1LW6.asc
  Contains a free cluster (137723). Assuming EOF.
/documents/Kindle User's Guide_B0058H1LW6.sdr/EndActions.data.B0058H1LW6.asc
  File size is 163 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.sdr/EndActions.data.B006ZKJGLI.asc
  Contains a free cluster (137554). Assuming EOF.
/documents/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.sdr/EndActions.data.B006ZKJGLI.asc
  File size is 194 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.sdr/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.mbs
  Contains a free cluster (138829). Assuming EOF.
/documents/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.sdr/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.mbs
  File size is 299 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.sdr/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.mbp1
  Contains a free cluster (138828). Assuming EOF.
/documents/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.sdr/This Week in the Civil War - Jan. 19th - 25th, 1862_B006ZKJGLI.mbp1
  File size is 212 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Andersonville - Volume 1 A Story of Rebel Military Prisons_B000JQUK9G.sdr/Andersonville - Volume 1 A Story of Rebel Military Prisons_B000JQUK9G.phl
  Contains a free cluster (139508). Assuming EOF.
/documents/Andersonville - Volume 1 A Story of Rebel Military Prisons_B000JQUK9G.sdr/Andersonville - Volume 1 A Story of Rebel Military Prisons_B000JQUK9G.phl
  File size is 341 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Andersonville - Volume 1 A Story of Rebel Military Prisons_B000JQUK9G.sdr/EndActions.data.B000JQUK9G.asc
  Contains a free cluster (139510). Assuming EOF.
/documents/Andersonville - Volume 1 A Story of Rebel Military Prisons_B000JQUK9G.sdr/EndActions.data.B000JQUK9G.asc
  File size is 190 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.phl
  Contains a free cluster (191204). Assuming EOF.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.phl
  File size is 365 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.mbs
  Contains a free cluster (193469). Assuming EOF.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.mbs
  File size is 215 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.mbp1
  Contains a free cluster (193468). Assuming EOF.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.mbp1
  File size is 1079 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/EndActions.data.B004UKEX7C.asc
  Contains a free cluster (193473). Assuming EOF.
/documents/The Trial and Death of Jesus Christ A Devotional History of our Lord's Passion_B004UKEX7C.sdr/EndActions.data.B004UKEX7C.asc
  File size is 968 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Abraham Lincoln_B000JQV2MK.sdr/Abraham Lincoln_B000JQV2MK.phl
  Contains a free cluster (143459). Assuming EOF.
/documents/Abraham Lincoln_B000JQV2MK.sdr/Abraham Lincoln_B000JQV2MK.phl
  File size is 174 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Abraham Lincoln_B000JQV2MK.sdr/Abraham Lincoln_B000JQV2MK.mbp
  Contains a free cluster (140350). Assuming EOF.
/documents/Abraham Lincoln_B000JQV2MK.sdr/Abraham Lincoln_B000JQV2MK.mbp
  File size is 256 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Abraham Lincoln_B000JQV2MK.sdr/EndActions.data.B000JQV2MK.asc
  Contains a free cluster (143462). Assuming EOF.
/documents/Abraham Lincoln_B000JQV2MK.sdr/EndActions.data.B000JQV2MK.asc
  File size is 190 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Secret Holocaust Diaries_B001Y35J5S.sdr/The Secret Holocaust Diaries_B001Y35J5S.phl
  Contains a free cluster (140577). Assuming EOF.
/documents/The Secret Holocaust Diaries_B001Y35J5S.sdr/The Secret Holocaust Diaries_B001Y35J5S.phl
  File size is 356 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Secret Holocaust Diaries_B001Y35J5S.sdr/The Secret Holocaust Diaries_B001Y35J5S.apnx
  Contains a free cluster (140524). Assuming EOF.
/documents/The Secret Holocaust Diaries_B001Y35J5S.sdr/The Secret Holocaust Diaries_B001Y35J5S.apnx
  File size is 1458 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Secret Holocaust Diaries_B001Y35J5S.sdr/EndActions.data.B001Y35J5S.asc
  Contains a free cluster (140590). Assuming EOF.
/documents/The Secret Holocaust Diaries_B001Y35J5S.sdr/EndActions.data.B001Y35J5S.asc
  File size is 802 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Incidents in the Life of a Slave Girl Written by Herself_B000JML1RA.sdr/Incidents in the Life of a Slave Girl Written by Herself_B000JML1RA.apnx
  Contains a free cluster (140571). Assuming EOF.
/documents/Incidents in the Life of a Slave Girl Written by Herself_B000JML1RA.sdr/Incidents in the Life of a Slave Girl Written by Herself_B000JML1RA.apnx
  File size is 1199 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Army of the Cumberland_B004TOYWK2.sdr/The Army of the Cumberland_B004TOYWK2.apnx
  Contains a free cluster (169820). Assuming EOF.
/documents/The Army of the Cumberland_B004TOYWK2.sdr/The Army of the Cumberland_B004TOYWK2.apnx
  File size is 97 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/A Christmas Carol_B000JQUKKU.sdr/A Christmas Carol_B000JQUKKU.apnx
  Contains a free cluster (146044). Assuming EOF.
/documents/A Christmas Carol_B000JQUKKU.sdr/A Christmas Carol_B000JQUKKU.apnx
  File size is 486 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.phl
  Contains a free cluster (152176). Assuming EOF.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.phl
  File size is 332 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.mbs
  Contains a free cluster (150654). Assuming EOF.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.mbs
  File size is 5731 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.mbp1
  Contains a free cluster (150653). Assuming EOF.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.mbp1
  File size is 213 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/EndActions.data.B0032UYGE6.asc
  Contains a free cluster (149155). Assuming EOF.
/documents/The Bible - The Holy Bible Formatted for Your eReader_B0032UYGE6.sdr/EndActions.data.B0032UYGE6.asc
  File size is 1020 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Selected Sermons of Jonathan Edwards_B004UJAE3U.sdr/Selected Sermons of Jonathan Edwards_B004UJAE3U.apnx
  Contains a free cluster (158223). Assuming EOF.
/documents/Selected Sermons of Jonathan Edwards_B004UJAE3U.sdr/Selected Sermons of Jonathan Edwards_B004UJAE3U.apnx
  File size is 1095 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Pursuit of God_B004TQ8GP2.sdr/The Pursuit of God_B004TQ8GP2.phl
  Contains a free cluster (156737). Assuming EOF.
/documents/The Pursuit of God_B004TQ8GP2.sdr/The Pursuit of God_B004TQ8GP2.phl
  File size is 269 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Pursuit of God_B004TQ8GP2.sdr/The Pursuit of God_B004TQ8GP2.apnx
  Contains a free cluster (156564). Assuming EOF.
/documents/The Pursuit of God_B004TQ8GP2.sdr/The Pursuit of God_B004TQ8GP2.apnx
  File size is 503 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Pursuit of God_B004TQ8GP2.sdr/XRAY.entities.B004TQ8GP2.asc
  Contains a free cluster (156742). Assuming EOF.
/documents/The Pursuit of God_B004TQ8GP2.sdr/XRAY.entities.B004TQ8GP2.asc
  File size is 17450 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Pursuit of God_B004TQ8GP2.sdr/EndActions.data.B004TQ8GP2.asc
  Contains a free cluster (156740). Assuming EOF.
/documents/The Pursuit of God_B004TQ8GP2.sdr/EndActions.data.B004TQ8GP2.asc
  File size is 181 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.phl
  Contains a free cluster (161210). Assuming EOF.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.phl
  File size is 248 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.mbs
  Contains a free cluster (161207). Assuming EOF.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.mbs
  File size is 219 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.mbp1
  Contains a free cluster (161205). Assuming EOF.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.mbp1
  File size is 212 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/EndActions.data.B004TPH9R4.asc
  Contains a free cluster (161212). Assuming EOF.
/documents/Within Prison Walls being a narrative during a week of voluntary confinement in the state prison at Auburn, New York_B004TPH9R4.sdr/EndActions.data.B004TPH9R4.asc
  File size is 366 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/The Adventures of Sherlock Holmes_B000JQU1VS.phl
  Contains a free cluster (162237). Assuming EOF.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/The Adventures of Sherlock Holmes_B000JQU1VS.phl
  File size is 361 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/The Adventures of Sherlock Holmes_B000JQU1VS.apnx
  Contains a free cluster (169280). Assuming EOF.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/The Adventures of Sherlock Holmes_B000JQU1VS.apnx
  File size is 641 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/XRAY.entities.B000JQU1VS.asc
  Contains a free cluster (162251). Assuming EOF.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/XRAY.entities.B000JQU1VS.asc
  File size is 56260 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/EndActions.data.B000JQU1VS.asc
  Contains a free cluster (162250). Assuming EOF.
/documents/The Adventures of Sherlock Holmes_B000JQU1VS.sdr/EndActions.data.B000JQU1VS.asc
  File size is 190 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Grimm's Fairy Stories_B000JML1QG.sdr/Grimm's Fairy Stories_B000JML1QG.apnx
  Contains a free cluster (162397). Assuming EOF.
/documents/Grimm's Fairy Stories_B000JML1QG.sdr/Grimm's Fairy Stories_B000JML1QG.apnx
  File size is 734 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Grimm's Fairy Stories_B000JML1QG.sdr/XRAY.entities.B000JML1QG.asc
  Contains a free cluster (164667). Assuming EOF.
/documents/Grimm's Fairy Stories_B000JML1QG.sdr/XRAY.entities.B000JML1QG.asc
  File size is 17048 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/documents/Grimm's Fairy Stories_B000JML1QG.sdr/EndActions.data.B000JML1QG.asc
  Contains a free cluster (164670). Assuming EOF.
/documents/Grimm's Fairy Stories_B000JML1QG.sdr/EndActions.data.B000JML1QG.asc
  File size is 190 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/tts/data/high-quality/synth_tom_full_155mrf22_270_06.dat
  File size is 23960576 bytes, cluster chain length is > 23961600 bytes.
  Truncating file to 23960576 bytes.
/.active-content-data/8a10d02f34c153ec0135373a3040000a/work/GameStats.ser
  Contains a free cluster (170083). Assuming EOF.
/.active-content-data/8a10d02f34c153ec0135373a3040000a/work/GameStats.ser
  File size is 623 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/.active-content-data/8a10d02f34c153ec0135373a3040000a/metadata/thumbnail_8a10d02f34c153ec0135373a3040000a-5.jpg
  Contains a free cluster (169099). Assuming EOF.
/.active-content-data/8a10d02f34c153ec0135373a3040000a/metadata/thumbnail_8a10d02f34c153ec0135373a3040000a-5.jpg
  File size is 4513 bytes, cluster chain length is 0 bytes.
  Truncating file to 0 bytes.
/.active_content_sandbox/com.amazon.kindle.ns.widgets.EndActions
  Contains a free cluster (235655). Assuming EOF.
/.active_content_sandbox/com.amazon.kindle.ns.widgets.Goto
  Contains a free cluster (235659). Assuming EOF.
/.active_content_sandbox/com.amazon.kindle.ns.widgets.AuthorProfile
  Contains a free cluster (220864). Assuming EOF.
boot: I def:rbt:reset=user_reboot,version=000000:

Checking for unused clusters.
Reclaimed 22502 unused clusters (184336384 bytes).
Checking free cluster summary.
Free cluster summary wrong (365032 vs. really 411217)
  Auto-correcting.
Performing changes.
/dev/loop/0: 314 files, 10512/421729 clusters
/etc/rcS.d/S50diags: line 13: /usr/local/sbin/dropbear: not found
mounting waveform filesystem
umounting waveform filesystem
info display:started:time=43660:
/etc/upstart/battery-diags: line 91: f_proto: not found
info battery:charged:cap=96,mV=4192,mAH=1413:
USER=root
prevlevel=N
OLDPWD=/
HOME=/
runlevel=S
eink=fslepdc
TERM=vt102
PATH=/sbin:/bin:/usr/sbin:/usr/bin
SHELL=/bin/sh
PWD=/dev
VERBOSE=no
LD_LIBRARY_PATH=/usr/lib/tts/speech/components/common/:/usr/lib/tts
No state is present for card imxyoshi
Unknown hardware: "WM8962" "" "" "" ""
Hardware is initialized using a guess method
/etc/rcS.d/S50diags: line 13: audioServer: not found
/etc/rcS.d/S50diags: line 13: kb: not found
diags : /opt/factory/rootfs_md5_list not found.
Sending: mkdir -p /mnt/base-us/diagnostic_logs/
PostMode len = 10 of 16
Diag cmds =  m x d c
GlobalHalImpl: found DeviceType: 19
found: zforce
Sending cmd: modprobe mx50_yoshi_mma8453  
input: mma8453 as /devices/virtual/i2c-adapter/i2c-0/0-001c/input/input5

check mma8453 chip ID

mma8453 0-001c: build time Nov  9 2011 15:18:29

add mma8453 i2c driver

Sending cmd: modprobe mx50_proximity  
FATAL: Module mx50_proximity not found.
found: whitney_button
Input driver version is 1.0.0
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "WM8962 Beep Generator"
Supported events:
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "imx-yoshi Headset"
Supported events:
Input driver version is 1.0.0
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "whitney-button"
Supported events:
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "zforce"
Supported events:
Input driver version is 1.0.0
Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
Input device name: "mxckpd"
Supported events:
Input driver version is 1.0.0
Input device ID: bus 0x18 vendor 0x0 product 0x0 version 0x0
Input device name: "mma8453"
Supported events:
 failed to open /dev/input/event6
 failed to open /dev/input/event7
[Found] name: KEY_MENU, symbol: MENU, value: 139
[Found] name: KEY_X, symbol: X, value: 45
[Found] name: KEY_D, symbol: D, value: 32
[Found] name: KEY_C, symbol: C, value: 46
[Found] name: KEY_Q, symbol: Q, value: 16
Devmode enabled
Reading vars from temp storage...
...None found, Copying vars from /proc
Setting postmode to normal
Writing new vars to temp area
You must reboot before new values will take effect
1000
1000
system_diags[MainTest] 1 INFO : Start test
   WHITNEY_WFO - System Diags
   ~~~~~~  1.0.6.217  ~~~ -1094849656 ~~~~~~~~~~~~
~ S ~ Device Setting  
O) Operator test suite     
R) Run in Test     
G) Gas Gauge     
E) 511     
T) Power Test     
B) Audio Test     
H) Adjust battery     
M) MoviNand     
N) Misc individual diagnostics     
Y) ART 11g factory test     
U) USB device mode     
D) Exit, Reboot or Disable Diags     
K) Lock to HOME button     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

Cmd: M
system_diags[MoviNandTest] 1 INFO : Start test
   WHITNEY_WFO - MoviNand
   ~~~~~~  1.0.6.217  ~~~ 333976 ~~~~~~~~~~~~
   Enter MOVINAND Test.
   It might take few minutes
   to finish the test
   Be patient

	Parsing : [RunInMode=0 Mount_Cust_Flag=/cust/etc/version.txt]
	RunInMode = 0
	Mount_Cust_Flag = /cust/etc/version.txt
MD5 file list : /opt/factory/diagrootfs_md5_list
system: I mntroot:def:Making root filesystem writeable
EXT3 FS on mmcblk0p2, internal journal

umount: /cust: not found
kjournald starting.  Commit interval 5 seconds

EXT3-fs: mounted filesystem with writeback data mode.

system: I mntroot:def:Making root filesystem read-only
MD5 file list : /cust/opt/factory/rootfs_md5_list
File not found: /cust/opt/ar6k/include/dbglog.h.save
md5 sum test failed
File not found: /cust/opt/ar6k/include/dbglog_id.h.save
md5 sum test failed
File not found: /cust/opt/ar6k/host/eeprom
md5 sum test failed
File not found: /cust/opt/ar6k/host/recEvent
md5 sum test failed
File not found: /cust/opt/ar6k/host/support/RFtest.sh
md5 sum test failed
File not found: /cust/opt/ar6k/host/support/loadtestcmd.sh
md5 sum test failed
File not found: /cust/opt/ar6k/host/support/loadAR6000.sh
md5 sum test failed
File not found: /cust/opt/ar6k/host/support/platformscripts/plat_YOSHI_NATIVEMMC-SDIO.sh
md5 sum test failed
File not found: /cust/opt/ar6k/host/athtestcmd
md5 sum test failed
File not found: /cust/opt/ar6k/host/bmiloader
md5 sum test failed
check md5 list /cust/opt/amazon/ebook/lib/lucene-core-2.4.1.jar not in md5
Adding /cust/opt/amazon/ebook/lib/lucene-core-2.4.1.jar to failed md5sum list
check md5 list /cust/opt/amazon/ebook/lib/ReaderSDK-impl-it_IT.jar not in md5
Adding /cust/opt/amazon/ebook/lib/ReaderSDK-impl-it_IT.jar to failed md5sum list
check md5 list /cust/lib/libc-2.12.1.so not in md5
Adding /cust/lib/libc-2.12.1.so to failed md5sum list
File not found: /cust/usr/sbin/rpinit
md5 sum test failed
File not found: /cust/usr/share/xsessions/awesome.desktop
md5 sum test failed
File not found: /cust/etc/sysconfig/ALLOW_CVM_RESET
md5 sum test failed
check md5 list /cust/etc/shadow not in md5
Adding /cust/etc/shadow to failed md5sum list
File not found : /cust/opt/ar6k/include/dbglog.h.save
File not found : /cust/opt/ar6k/include/dbglog_id.h.save
File not found : /cust/opt/ar6k/host/eeprom
File not found : /cust/opt/ar6k/host/recEvent
File not found : /cust/opt/ar6k/host/support/RFtest.sh
File not found : /cust/opt/ar6k/host/support/loadtestcmd.sh
File not found : /cust/opt/ar6k/host/support/loadAR6000.sh
File not found : /cust/opt/ar6k/host/support/platformscripts/plat_YOSHI_NATIVEMMC-SDIO.sh
File not found : /cust/opt/ar6k/host/athtestcmd
File not found : /cust/opt/ar6k/host/bmiloader
File not found : /cust/usr/sbin/rpinit
File not found : /cust/usr/share/xsessions/awesome.desktop
File not found : /cust/etc/sysconfig/ALLOW_CVM_RESET

Failed md5sum: [/cust/opt/amazon/ebook/lib/lucene-core-2.4.1.jar]
From file         : [50373bca7c7436d4b9741a3a8e972a3a]
From md5sum result: [a96c4738f837c2b4affa7f1e3d0ec7c0]

Failed md5sum: [/cust/opt/amazon/ebook/lib/ReaderSDK-impl-it_IT.jar]
From file         : [9a1205bba7c4e0c3a10529cec30f4c2f]
From md5sum result: [0c55937adaf748a19ee1c6bc8bb16c29]

Failed md5sum: [/cust/lib/libc-2.12.1.so]
From file         : [2f90835ebac53e1525818dee2929c443]
From md5sum result: [d18a726707e3c28cd2de80707cdca26b]

Failed md5sum: [/cust/etc/shadow]
From file         : [6cea7485deb63b98bb5e8d68699d5565]
From md5sum result: [0f5f858b6a2b9e2f548fd967b9a323ec]
md5sum [4009] files in [0] min, [32] secs
   WHITNEY_WFO - MoviNand
   ~~~~~~  1.0.6.217  ~~~ 333976 ~~~~~~~~~~~~
 
   FAIL
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ X ~ Exit
  

Cmd: X
run: Status: WAIT_FOR_STATUS_EXIT
system_diags[MoviNandTest] 1 FAIL : 58  
File not found : /cust/opt/ar6k/include/dbglog.h.save
File not found : /cust/opt/ar6k/include/dbglog_id.h.save
File not found : /cust/opt/ar6k/host/eeprom
File not found : /cust/opt/ar6k/host/recEvent
File not found : /cust/opt/ar6k/host/support/RFtest.sh
File not found : /cust/opt/ar6k/host/support/loadtestcmd.sh
File not found : /cust/opt/ar6k/host/support/loadAR6000.sh
File not found : /cust/opt/ar6k/host/support/platformscripts/plat_YOSHI_NATIVEMMC-SDIO.sh
File not found : /cust/opt/ar6k/host/athtestcmd
File not found : /cust/opt/ar6k/host/bmiloader
File not found : /cust/usr/sbin/rpinit
File not found : /cust/usr/share/xsessions/awesome.desktop
File not found : /cust/etc/sysconfig/ALLOW_CVM_RESET

Failed md5sum: [/cust/opt/amazon/ebook/lib/lucene-core-2.4.1.jar]
From file         : [50373bca7c7436d4b9741a3a8e972a3a]
From md5sum result: [a96c4738f837c2b4affa7f1e3d0ec7c0]

Failed md5sum: [/cust/opt/amazon/ebook/lib/ReaderSDK-impl-it_IT.jar]
From file         : [9a1205bba7c4e0c3a10529cec30f4c2f]
From md5sum result: [0c55937adaf748a19ee1c6bc8bb16c29]

Failed md5sum: [/cust/lib/libc-2.12.1.so]
From file         : [2f90835ebac53e1525818dee2929c443]
From md5sum result: [d18a726707e3c28cd2de80707cdca26b]

Failed md5sum: [/cust/etc/shadow]
From file         : [6cea7485deb63b98bb5e8d68699d5565]
From md5sum result: [0f5f858b6a2b9e2f548fd967b9a323ec]
md5sum [4009] files in [0] min, [32] secs
system_diags[MoviNandTest] 1 INFO : End test
exe: Status: WAIT_FOR_STATUS_EXECUTED
   WHITNEY_WFO - System Diags
   ~~~~~~  1.0.6.217  ~~~ -1094849656 ~~~~~~~~~~~~
S) Device Setting     
O) Operator test suite     
R) Run in Test     
G) Gas Gauge     
E) 511     
T) Power Test     
B) Audio Test     
H) Adjust battery     
~ M ~ MoviNand  
N) Misc individual diagnostics     
Y) ART 11g factory test     
U) USB device mode     
D) Exit, Reboot or Disable Diags     
K) Lock to HOME button     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

Cmd: D
system_diags[DisableDiags] 1 INFO : Start test
   WHITNEY_WFO - Exit, Reboot or Disable Diags
   ~~~~~~  1.0.6.217  ~~~ -1094849856 ~~~~~~~~~~~~
~ F ~ Fastboot Bundle Install  
U) USB Bundle Install     
C) Check Pass/Fail Status     
R) Reboot System     
D) Disable Diagnostics     
L) Exit to login prompt     
M) ReportToXml     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

Cmd: C
system_diags[PassFailTest] 1 INFO : Start test
	[testName=HAL_CMD_CHECK_DIAGS]~~~~~
	testName = HAL_CMD_CHECK_DIAGS
   WHITNEY_WFO - Check Pass/Fail Status
   ~~~~~~  1.0.6.217  ~~~ 479472 ~~~~~~~~~~~~
   Are you sure?
 
~ Q ~ To continue  
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

Cmd: Q
run: Status: WAIT_FOR_STATUS_DONE
	Getting parent: DisableDiags
	Getting parent: DisableDiags
system: I mntroot:def:Making root filesystem writeable
EXT3 FS on mmcblk0p2, internal journal

	Getting parent: DisableDiags
	Getting parent: DisableDiags
sh: can't create /tmp/tmp.txt: nonexistent directory
Manufacturing code is invalid
DeviceSettingObjectImpl: setUserVersion (NULL)
Waveform to use
BBB [08_07_00ad_3c_156e21_03_3c_000008da_85
]


WaveformVersion: 08_07_00ad_3c_156e21_03_3c_000008da_85
cp: can't stat '/tmp/xmlReport.xml': No such file or directory
	Get top level: MainTest
Cannot open file: /tmp/Report.txt
	BEGIN_REPORT : MoviNandTest
Cannot open file: /tmp/Report.txt
system_diags[MoviNandTest] 1 FAIL : 58  
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
Cannot open file: /tmp/Report.txt
	END_REPORT : MoviNandTest
Cannot open file: /tmp/Report.txt
	BEGIN_REPORT : DisableDiags
Cannot open file: /tmp/Report.txt
system_diags[DisableDiags] 1 PASS : 141  
Cannot open file: /tmp/Report.txt
	BEGIN_REPORT : PassFailTest
Cannot open file: /tmp/Report.txt
system_diags[PassFailTest] 1 PASS : 144  
Cannot open file: /tmp/Report.txt
	END_REPORT : PassFailTest
Cannot open file: /tmp/Report.txt
	END_REPORT : DisableDiags
Cannot open file: /tmp/Report.txt
cp: can't stat '/tmp/Report.txt': No such file or directory
cp: can't stat '/tmp/logFile.txt': No such file or directory
   DIAGS FAILED
   ~~~~~~  1.0.6.217  ~~~ 0 ~~~~~~~~~~~~
 
   SEND THIS UNIT TO REWORK
 
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ X ~ Exit
  

X
[Found] name: KEY_X, symbol: X, value: 45
Cmd: X
run: Status: WAIT_FOR_STATUS_EXIT
system_diags[PassFailTest] 1 PASS : 144  
system_diags[PassFailTest] 1 INFO : End test
exe: Status: WAIT_FOR_STATUS_EXECUTED
   WHITNEY_WFO - Exit, Reboot or Disable Diags
   ~~~~~~  1.0.6.217  ~~~ -1094849856 ~~~~~~~~~~~~
F) Fastboot Bundle Install     
U) USB Bundle Install     
~ C ~ Check Pass/Fail Status  
R) Reboot System     
D) Disable Diagnostics     
L) Exit to login prompt     
M) ReportToXml     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

X
[Found] name: KEY_X, symbol: X, value: 45
Cmd: X
run: Status: WAIT_FOR_STATUS_EXIT
	Parent: System Diags
system_diags[DisableDiags] 1 PASS : 141  
system_diags[DisableDiags] 1 INFO : End test
exe: Status: WAIT_FOR_STATUS_EXECUTED
   WHITNEY_WFO - System Diags
   ~~~~~~  1.0.6.217  ~~~ -1094849656 ~~~~~~~~~~~~
S) Device Setting     
O) Operator test suite     
R) Run in Test     
G) Gas Gauge     
E) 511     
T) Power Test     
B) Audio Test     
H) Adjust battery     
M) MoviNand     
N) Misc individual diagnostics     
Y) ART 11g factory test     
U) USB device mode     
~ D ~ Exit, Reboot or Disable Diags  
K) Lock to HOME button     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

N
[Found] name: KEY_N, symbol: N, value: 49
Cmd: N
system_diags[MiscIndividualDiagnostics] 1 INFO : Start test
   WHITNEY_WFO - Misc individual diagnostics
   ~~~~~~  1.0.6.217  ~~~ -1094849856 ~~~~~~~~~~~~
~ C ~ Certification Test Mode  
I) Wifi Test     
L) LED Test     
K) Key test     
V) Video Test     
M) Accelerometer     
P) Proximity Sensor     
T) Touch Sensor     
F) FCT Test     
A) Accessory Port     
U) Utilities     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

U
[Found] name: KEY_U, symbol: U, value: 22
Cmd: U
system_diags[Utilities] 1 INFO : Start test
   WHITNEY_WFO - Utilities
   ~~~~~~  1.0.6.217  ~~~ -1094850096 ~~~~~~~~~~~~
~ E ~ 511 with wan and device info  
Z) Enable USBnet     
M) Mount nfs     
S) Stress Tests     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

Z
[Found] name: KEY_Z, symbol: Z, value: 44
Cmd: Z
system_diags[USBnet] 1 INFO : Start test
	testName = USBnet
	Executing usb_net_test: /mnt/base-us/USBnet.xml
Cannot open xmlFile /mnt/base-us/USBnet.xml
NOT Found NFS path
   WHITNEY_WFO - Enable USBnet
   ~~~~~~  1.0.6.217  ~~~ 1 ~~~~~~~~~~~~
   ipAddress : 192.168.15.244
   netMask   : 255.255.255.0
   deviceAddr: EE5900000015
   hostAddr  : EE2900000015
   device_NFS: /mnt/gen3/factory
   host_NFS  : /scratchbox/nfs/factory/
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Press X to continue
 
   PASS
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~ X ~ Exit
  

X
[Found] name: KEY_X, symbol: X, value: 45
Cmd: X
run: Status: WAIT_FOR_STATUS_EXIT
USB_NetInfo: Exporting USB net info to /mnt/base-us/USBnet.xml
NOT Found NFS path
NOT Found NFS path
found: g_file_storage
FATAL: Could not load /lib/modules/2.6.31-rt11-lab126/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.31-rt11-lab126/modules.dep: No such file or directory
ifconfig: SIOCSIFADDR: No such device
system: I mntroot:def:Making root filesystem writeable
system_diags[USBnet] 1 PASS : 132  
system_diags[USBnet] 1 INFO : End test
exe: Status: WAIT_FOR_STATUS_EXECUTED
   WHITNEY_WFO - Utilities
   ~~~~~~  1.0.6.217  ~~~ -1094850096 ~~~~~~~~~~~~
E) 511 with wan and device info     
~ Z ~ Enable USBnet  
M) Mount nfs     
S) Stress Tests     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit

After enabling serial root login prompt, run "mntroot rw" to make the filesystem writable (yet can't make a directory)?:

Spoiler:

..running mount:

Spoiler:

...directory listing of /dev/mmcblk0p3 (/var/local) before writing /dev/zero:

Spoiler:

...continuing on, running "dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K" while the partition is mounted:

Spoiler:

...directory listing of /var/local after zeroing

Spoiler:

...unmounting /var/local

Spoiler:

...re-mounting /dev/mmcblk0p3 to /var/local and getting a directory listing (it looks like the partition is re-populated when it is mounted?):

Spoiler:

...re-zeroing /dev/mmcblk0p3 after unmounting:

Spoiler:

...console output after enabling USB Device Mode and trying to copy the main.img to the USB userstore. According to Mac OS X (the OS I'm trying to copy from), the file transfer fails after about 8.4 MB (of 367 MB) of data have been transferred:

Spoiler:

Code:

   WHITNEY_WFO - System Diags
   ~~~~~~  1.0.6.217  ~~~ -1096803448 ~~~~~~~~~~~~
S) Device Setting     
O) Operator test suite     
R) Run in Test     
G) Gas Gauge     
E) 511     
T) Power Test     
B) Audio Test     
H) Adjust battery     
M) MoviNand     
N) Misc individual diagnostics     
Y) ART 11g factory test     
~ U ~ USB device mode  
D) Exit, Reboot or Disable Diags     
K) Lock to HOME button     
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

U
[Found] name: KEY_U, symbol: U, value: 22
Cmd: U
system_diags[USB_DeviceModeTest] 4 INFO : Start test
	testName = USBexport
	export USB
	Check USB_cable
   WHITNEY_WFO - USB device mode
   ~~~~~~  1.0.6.217  ~~~ 333976 ~~~~~~~~~~~~
   Please connect the USB cable
   from PC to the device
 
 
~ Q ~ to continue  
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

	Waiting
Connected to a HIGH speed Host

	Exporting USB user store
found: g_file_storage
   WHITNEY_WFO - USB device mode
   ~~~~~~  1.0.6.217  ~~~ 333976 ~~~~~~~~~~~~
   USB device exported
    
   Once you are done
   Eject the USB device from the PC then
 
 
~ Q ~ to continue  
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
X) Exit
     

g_file_storage gadget: high speed config #1

charger: Stop charging as battery is full

mmcblk0: error -110 transferring data, sector 1425544 nr 8, cmd response 0x900 card status 0x80b00

mmcblk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 1425544 nr 8, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425544

mmcblk0: error -110 transferring data, sector 1425545 nr 7, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425545

mmcblk0: error -110 transferring data, sector 1425546 nr 6, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425546

mmcblk0: error -110 transferring data, sector 1425547 nr 5, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425547

mmcblk0: error -110 transferring data, sector 1425548 nr 4, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425548

mmcblk0: error -110 transferring data, sector 1425549 nr 3, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425549

mmcblk0: error -110 transferring data, sector 1425550 nr 2, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425550

mmcblk0: error -110 transferring data, sector 1425551 nr 1, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425551

mmcblk0: error -110 transferring data, sector 978960 nr 8, cmd response 0x80900 card status 0xc00

mmcblk0: error -110 transferring data, sector 1425544 nr 8, cmd response 0x900 card status 0x80b00

mmcblk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 1425544 nr 8, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425544

mmcblk0: error -110 transferring data, sector 1425545 nr 7, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425545

mmcblk0: error -110 transferring data, sector 1425546 nr 6, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425546

mmcblk0: error -110 transferring data, sector 1425547 nr 5, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425547

mmcblk0: error -110 transferring data, sector 1425548 nr 4, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425548

mmcblk0: error -110 transferring data, sector 1425549 nr 3, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425549

mmcblk0: error -110 transferring data, sector 1425550 nr 2, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425550

mmcblk0: error -110 transferring data, sector 1425551 nr 1, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425551

mmcblk0: error -110 transferring data, sector 979192 nr 32, cmd response 0x80900 card status 0xc00

mmcblk0: error -110 transferring data, sector 1425800 nr 8, cmd response 0x900 card status 0x80b00

mmcblk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 1425800 nr 8, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425800

mmcblk0: error -110 transferring data, sector 1425801 nr 7, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425801

mmcblk0: error -110 transferring data, sector 1425802 nr 6, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425802

mmcblk0: error -110 transferring data, sector 1425803 nr 5, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425803

mmcblk0: error -110 transferring data, sector 1425804 nr 4, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425804

mmcblk0: error -110 transferring data, sector 1425805 nr 3, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425805

mmcblk0: error -110 transferring data, sector 1425806 nr 2, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425806

mmcblk0: error -110 transferring data, sector 1425807 nr 1, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1425807

mmcblk0: error -110 transferring data, sector 982480 nr 40, cmd response 0x80900 card status 0xc00

mmcblk0: error -110 transferring data, sector 1426056 nr 8, cmd response 0x900 card status 0x80b00

mmcblk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 1426056 nr 8, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426056

mmcblk0: error -110 transferring data, sector 1426057 nr 7, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426057

mmcblk0: error -110 transferring data, sector 1426058 nr 6, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426058

mmcblk0: error -110 transferring data, sector 1426059 nr 5, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426059

mmcblk0: error -110 transferring data, sector 1426060 nr 4, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426060

mmcblk0: error -110 transferring data, sector 1426061 nr 3, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426061

mmcblk0: error -110 transferring data, sector 1426062 nr 2, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426062

mmcblk0: error -110 transferring data, sector 1426063 nr 1, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426063

mmcblk0: error -110 transferring data, sector 985576 nr 24, cmd response 0x80900 card status 0xc00

mmcblk0: error -110 transferring data, sector 1426312 nr 8, cmd response 0x900 card status 0x80b00

mmcblk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 1426312 nr 8, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426312

mmcblk0: error -110 transferring data, sector 1426313 nr 7, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426313

mmcblk0: error -110 transferring data, sector 1426314 nr 6, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426314

mmcblk0: error -110 transferring data, sector 1426315 nr 5, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426315

mmcblk0: error -110 transferring data, sector 1426316 nr 4, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426316

mmcblk0: error -110 transferring data, sector 1426317 nr 3, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426317

mmcblk0: error -110 transferring data, sector 1426318 nr 2, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426318

mmcblk0: error -110 transferring data, sector 1426319 nr 1, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426319

mmcblk0: error -110 transferring data, sector 1395688 nr 24, cmd response 0x80900 card status 0xc00

mmcblk0: error -110 transferring data, sector 1426568 nr 8, cmd response 0x900 card status 0x80b00

mmcblk0: retrying using single block read

mmcblk0: error -110 transferring data, sector 1426568 nr 8, cmd response 0x900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426568

mmcblk0: error -110 transferring data, sector 1426569 nr 7, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426569

mmcblk0: error -110 transferring data, sector 1426570 nr 6, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426570

mmcblk0: error -110 transferring data, sector 1426571 nr 5, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426571

mmcblk0: error -110 transferring data, sector 1426572 nr 4, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426572

mmcblk0: error -110 transferring data, sector 1426573 nr 3, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426573

mmcblk0: error -110 transferring data, sector 1426574 nr 2, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426574

mmcblk0: error -110 transferring data, sector 1426575 nr 1, cmd response 0x80900 card status 0x0

end_request: I/O error, dev mmcblk0, sector 1426575

...etc., etc., etc.

...what am I doing wrong?

Once again, thank you to all who reply. I am much awaiting your answers.

NiLuJe · 04-09-2014, 09:13 PM

Unmount it before zeroing it, since you're accessing it 'raw' via /dev

TBennettcc · 04-10-2014, 12:41 AM

I did that? Second-to-last "spoiler" fold...

Quote:

...re-zeroing /dev/mmcblk0p3 after unmounting:

Code:

[root@kindle /]# umount /var/local
[root@kindle /]# dd if=/dev/zero of=/dev/mmcblk0p3 bs=4K count=1K
1024+0 records in
1024+0 records out
4194304 bytes (4.0MB) copied, 0.367403 seconds, 10.9MB/s
[root@kindle /]#

...any ideas why USBnet won't work?

Why I can't create a directory when I supposedly have read and write access to the filesystem?

Is there any way to do an fsck on any of these partitions? When trying, I get an error:

Quote:

[root@kindle /]# fsck /var/local
fsck 1.41.10 (10-Feb-2009)
fsck: fsck.ext2: not found
fsck: Error 2 while executing fsck.ext2 for /var/local
[root@kindle /]#

NiLuJe · 04-10-2014, 07:23 AM

@TBennettcc: Whoops, my bad, 3AM strikes again ;p.

IIRC, there's one of the options in diags that creates the missing folder/file for USBNet on diags, check the manual unbricking threads and/or the wiki, that should be in there

.

As for fsck/mkfs, the needed binaries might not be there in diags (can't say, it's been a long time since I checked a diags part), try to pull them from main.

knc1 · 04-10-2014, 08:21 AM

Quote:

Originally Posted by TBennettcc

Why I can't create a directory when I supposedly have read and write access to the filesystem?

In the case of your spoiler:
I do not see where you reformatted /var/local after zeroing its meta-information.
Note: a cold start (full re-boot) will detect the zero'd partition and format it for you.

Several common possibilities:
1) on a Kindle, the mntroot script only changes the / partition, not any other partitions (here, /var/local is on another partition).

That script is a very early lab126 screw-up, never been fixed.

The author did not know you can "mount -o remount,rw" a file system that is already rw (or conversely, "mount -o remount,ro" a file system that is already ro) without harm.

In general:
2) The file system or backing store does not support write operations (why you can't write to a cramfs (or other ro) file system; why you can't write to write protected media (flash in the case of the Kindle, for instance the u-boot part of flash is write protected and hardware locked)).

3) The file system is not mounted read-write.
Note: if mounted errors=ro, then a file system command that errors will switch it to ro.

4) No write permission for the current user to the parent directory.

TBennettcc · 04-12-2014, 07:11 PM

Can I schedule a meeting with one of you on IRC?

I'm pretty much free 1930 - 0200 UTC weekdays, and just about all day on Saturdays.

knc1 · 04-13-2014, 08:05 AM

Quote:

Originally Posted by TBennettcc

I am assisting a friend with a Kindle Touch. When I first received it, it was in diags mode. I rebooted it from the diags menu.
- - - -
When selecting "main", the Kindle reboots, shows a message: "Software Update. Your Kindle software is updating. This can take a few minutes. DO NOT turn your kindle off during the update process. Your Kindle will automatically restart as soon as the update process is complete.", and then reboots to the above screen telling me "the update was not successful".
- - - -

This is an unusually long thread of problems - -
So an unusual question:

Is there any chance that either you or your friend turned off the kindle during the update process?

- - - -

Doing so **could** have corrupted the flash device (not just the file system(s) stored on it - the device internals).

TBennettcc · 04-13-2014, 10:17 PM

If that's the case, is the device really, truly, completely bricked, or is there still a way to restore it?

Other than running the standard unbricking procedures (flashing diags partition and kernel and main kernel, etc.), I have not tried to run any updates. The device is still acting the same as when I received it. I have never seen a screen on the device besides the diags partition, the "update failed" screen, the "boy under the tree" when booting (and the loading bar), and the "Your Kindle needs repair" screen (which, ironically enough, didn't need the boot count file reset to get rid of...). I have never seen any kind of main "desktop" menu or interface.

So far as I understand, my friend tried to turn on the device, and it showed the "empty battery-plug me in-recharge me" screen. Someone told him this meant he needed a new battery, so he bought one and put the new battery in.

As far as how it got to that point, I'm not sure. I don't know which screens, if any, he saw before the "plug-in-to-charge" screen. I don't know if it tried to do an update first, and failed, and showed the "failed update" screen before it showed the "plug-in-to-charge" screen.

Is it possible it was trying to do an update, and the battery died in the middle of the update? I don't have a Kindle of my own yet (I was planning on buying a PW2 in short order), so I don't have any experience with updates or the updating process. I don't know if the device needs to be plugged in to power before starting an update, etc. (If something like this can happen because of that, IMHO, they should make that a *requirement*!)

I can boot to fastboot (1949:d0d0). I can boot to diags. I can enter USB Recovery mode (15a2:0052). I can talk to the device through the serial console. I can flash the diags partition, diags kernel, and main kernel. All of which tells me *something* has to be working, right?

Is there *any* way to completely nuke everything and start over? Maybe erase MMC0? I've seen various threads on this site claim to be able to repair a Kindle that has had its MMC0 nuked, but they all seem to be predicated on getting the main partition image successfully copied over to the USB user partition, which seems to be a problem for me.

Thank you for your time.

knc1 · 04-14-2014, 06:45 AM

Quote:

Originally Posted by TBennettcc

- - - - -
So far as I understand, my friend tried to turn on the device, and it showed the "empty battery-plug me in-recharge me" screen. Someone told him this meant he needed a new battery, so he bought one and put the new battery in.

As far as how it got to that point, I'm not sure. I don't know which screens, if any, he saw before the "plug-in-to-charge" screen. I don't know if it tried to do an update first, and failed, and showed the "failed update" screen before it showed the "plug-in-to-charge" screen.

Is it possible it was trying to do an update, and the battery died in the middle of the update?
- - - -

The unfortunate answer is: **YES**

The design of the firmware protects the system from attempting an update in the case of a **SINGLE POINT** failure - -
Specifically, a low terminal voltage on the battery.
(Same measurement triggers the "need more juice" panel.)

The (faulty) assumption in the design is that the terminal voltage is an indication of the storage capacity (available).

Ah, but LiIon batteries do not age in that manner.

Terminal voltage measurement only indicates if the battery is **FULLY Charged** to its **current** capacity.
But what is FULL ?

In the case of a relatively new battery, about 1.5 amp/hours.
In the case of an old (and/or heavy used/cycled) battery, maybe less than that of a small hearing aid battery.

When **FULLY Charged** both case will show a *normal* full-charge terminal voltage.
But the stored energy will not be the same, in one case (new) it will be a lot, in the other case it will be not even worth mentioning.

Duh.

A **TWO POINT** failure -
1) Insufficient storage capacity to complete the high power consumption erase/re-program cycles needed to re-write the flash.
2) Only testing the terminal voltage, not testing the capacity.

Translation:
Its toast.
(or spare parts - except for the flash chip - that thing is destroyed)

- - - -

The only good news is:
Neither you nor your friend had anything to do with this failure.
And it probably happened **before** the battery was changed.

The conditions back then:
1) A battery with little storage capacity (due to use/age);
2) The presence of an update file.

The system tried to run an "auto install update" and ran out of power while the flash chip was getting one of its erase/re-program cycles organized (the battery has a tiny micro-computer in it).

Result: It self-destructed.

TBennettcc · 04-15-2014, 11:44 PM

Could you do your best to explain *why* the flash is toast? Perhaps it's only me and my rudimentary understanding of flash memory, but isn't flash memory just a bunch of flip-flops that saves state in non-volatile RAM? To me, then, it would seem that a "bad update" would do nothing more that load a corrupted image into the NVRAM... not necessarily hurt anything physically?

Let's say I still wanted to screw around with this thing, just for giggles and grins... What would be the downsides of erasing MMC0? Would that erase u-boot? How do I get the "special/hidden" files/data from the non-user areas before I nuke MMC0?

Theoretically, if I erase MMC0, I should be able to:

Code:

a. boot to u-boot
b. get into fastboot mode
c. flash diags, diags kernel, and main kernel
d. boot into diags
e. enable USB drive mode
f. copy main kernel to user area
g. reboot to diags
h. get to root serial console with login prompt
i. load main partition from user area?

Do you see anything wrong with the above? Am I underestimating the effects of erasing MMC0? (And even if the copy to the user area fails, at least I tried something else, even though it didn't work. All that means is that the flash really truly is toast, in which case it's only good for parts, or maybe a trade-in towards a new one with Amazon. As a friend of mine likes to say, "You can't broke broke! It's already broke! You can't broke it no more!")

Thank you very much for your time. You've been a great help, and your detailed explanations have been fabulous.

knc1 · 04-16-2014, 10:08 AM

Thanks, (I think -

).

The hard one first:

Yup, flash is just a bunch of flip-flops and logic gates.
So is the SoC on the main board and the SoC on the 3G board.

(SoC: System On a Chip)

About 2*10^9 * 8 of them or twice that on other Kindle models.
So there is also quite a bit of structure to the device and management requirements of that structure.

Some boring history (but might have keywords for web-searching):
In the case of the most distant relative of today's flash chips -
(Intel 1702 as I recall)
The entire device was erased at once, by intense UV light.
The device was programed in blocks by a high voltage programming circuit.
(eprom : erasable, programmable, read-only, memory)

The next step was to get rid of that "erase by intense UV light" and its quartz window on the chip carrier.
Enter the eeprom: electrically erasable, programmable, read-only, memory.
All of which was provided by external circuitry.

As storage capacities increased, the external circuitry became more complex and over time was moved onto the same chip.

That includes the management and control sequencing, which was moved into a (rom) programmed micro-controller.
A "special function" computer in its own right.
Also the erase and programming voltage generation was moved on-chip.

But as a crude summary,
the USB flash drive, these on-board flash chips, and even the SSD spinning rust replacements are just EEPROM devices on steroids (on triple steroids in the case of SSD devices).

Same limitations on all variteties over the years:
You can erase them, you can program them, you can read them BUT you CAN NOT write to them.
Sorry, just can't be done.

So the micro-controller has to "fake" the write operation.

The management of the storage is done in "erase blocks" sized parts of the internal structure. 4,096 bytes * 8 bits + ecc bits + vendor defined bits + price of tea in china.

It is interrupting the "life cycle" of an erase block by dropping the power at the wrong time which puts the device into a non-recoverable state.

I.E:
micro-controller's data says an erase block is erased and ready to be programmed (but the power failed before it could be erased completely).
OR:
micro-controller's data says an erase block has been re-programmed (but the programming power failed during the attempt).
OR:
other, less obvious, sequencing errors.

That micro-controller is fairly complex, and on SSD devices, nearly a full computer in itself.
But there are still limits to what it can detect and correct.

If its database says that block 1603456 has been programmed (or erased), and assigned a readable address (or a "ready" address) -
that is what it has to work with.

The easiest to visualize is an incompletely erased erase block (because of power failure to the erase voltage generator) on the "ready" address list.
So that is the next erase block it will try to program, but you can not program an un-erased, erase block.

The device has been rendered useless.

(the controller on an SSD is a lot "smarter" than that, but you still don't want to disconnect their power while they are sequencing)

Doing an "erase mmc" (a full device erase) may or may not allow the controller to re-cover some of the storage capacity.
Chances are: slim - to - none.

- - - - -

The easy one:

Device and owner specific information is stored on the device, outside of the partitioned areas.

You need to make a copy of that (and write it back) to make the Kindle "work" after a full device erase.

Geekmaster has posted scripts and directions -
probably in the older, manual, de-bricking threads.

The "erase mmc" command will also (after erasing the device) re-write the u-boot area with the copy of u-boot currently running in ram.

According to the comments in the Amazon source code, the failure to save and restore the "device and owner" data is an error in the diags programming, which I think has never been fixed.

TBennettcc · 01-04-2015, 12:17 PM

Recently received a PM requesting some information on my serial cable and setup. I thought I would post my response here so that others may benefit:

I made my purchase from Mouser:

Serial Cable:
895-TTL232RGVREG1V8W

Plastic Header:
538-78172-0003

Pins for header:
538-78172-0410-CT

From RadioShack:
278-502 - 30 AWG wrapping wire

I used the wrapping wire to make the connection between the small header pins and the serial cable output. Be aware, you will probably need a high-power magnifier, as these things are *small*. I think I ended up using the edge of a knife to fold the 'arms' of the connectors onto the stripped wrapping wire. They fit into the white connector nicely, and mated perfectly with the connector on the Kindle Touch.

These parts are accurate for the Kindle Touch. Some of the other Kindles also need the socket to be soldered on the board. I do not have that information.

Cable datasheet:
TTL-232RG Datasheet

Cable information and drivers (you want the VCP drivers):
FTDI USB-to-Serial Cable information / Drivers

That should get you started.

rohitpsk · 10-24-2015, 12:25 PM

Looks like I am having the same problem. Any way this can be resolved or has been resolved?

https://www.mobileread.com/forums/sho...d.php?t=266726

knc1 · 10-24-2015, 01:50 PM

Quote:

Originally Posted by rohitpsk

Looks like I am having the same problem. Any way this can be resolved or has been resolved?

https://www.mobileread.com/forums/sho...d.php?t=266726

Only the 5.6.x series of firmware has a new enough kernel to support the (e)MMC tools.
Those tools **might** in some cases, be a help to recovering the eMMC operation.

or at least, either fail or report what is wrong with the device.
Either of which means you now have a used screen to sell on e-bay.

rohitpsk · 10-24-2015, 03:20 PM

What about this...

http://www.powerbookmedic.com/Amazon...3-p-46083.html

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Kindle touch]help, debricking , can't enter diags mode	zklcy	Kindle Developer's Corner	26	10-24-2012 09:47 AM
Kindle Touch Frozen in System Diags	XXPetrosXX	Kindle Developer's Corner	4	07-14-2012 07:50 AM
Bricked Kindle Touch; Won't boot into diags/fastboot	kerotan	Kindle Developer's Corner	3	05-19-2012 10:58 AM
Kindle Touch stuck at Diags page	sayyeah	Kindle Developer's Corner	3	05-12-2012 11:38 PM
Kindle Touch Stuck at diags	sole	Kindle Developer's Corner	13	05-01-2012 08:47 AM

04-09-2014, 09:13 PM	#17
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Unmount it before zeroing it, since you're accessing it 'raw' via /dev

04-10-2014, 07:23 AM	#19
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@TBennettcc: Whoops, my bad, 3AM strikes again ;p. IIRC, there's one of the options in diags that creates the missing folder/file for USBNet on diags, check the manual unbricking threads and/or the wiki, that should be in there . As for fsck/mkfs, the needed binaries might not be there in diags (can't say, it's been a long time since I checked a diags part), try to pull them from main.

04-12-2014, 07:11 PM	#21
TBennettcc Member Posts: 15 Karma: 10 Join Date: Mar 2014 Device: Kindle Touch	Can I schedule a meeting with one of you on IRC? I'm pretty much free 1930 - 0200 UTC weekdays, and just about all day on Saturdays.

04-13-2014, 10:17 PM	#23
TBennettcc Member Posts: 15 Karma: 10 Join Date: Mar 2014 Device: Kindle Touch	If that's the case, is the device really, truly, completely bricked, or is there still a way to restore it? Other than running the standard unbricking procedures (flashing diags partition and kernel and main kernel, etc.), I have not tried to run any updates. The device is still acting the same as when I received it. I have never seen a screen on the device besides the diags partition, the "update failed" screen, the "boy under the tree" when booting (and the loading bar), and the "Your Kindle needs repair" screen (which, ironically enough, didn't need the boot count file reset to get rid of...). I have never seen any kind of main "desktop" menu or interface. So far as I understand, my friend tried to turn on the device, and it showed the "empty battery-plug me in-recharge me" screen. Someone told him this meant he needed a new battery, so he bought one and put the new battery in. As far as how it got to that point, I'm not sure. I don't know which screens, if any, he saw before the "plug-in-to-charge" screen. I don't know if it tried to do an update first, and failed, and showed the "failed update" screen before it showed the "plug-in-to-charge" screen. Is it possible it was trying to do an update, and the battery died in the middle of the update? I don't have a Kindle of my own yet (I was planning on buying a PW2 in short order), so I don't have any experience with updates or the updating process. I don't know if the device needs to be plugged in to power before starting an update, etc. (If something like this can happen because of that, IMHO, they should make that a requirement!) I can boot to fastboot (1949:d0d0). I can boot to diags. I can enter USB Recovery mode (15a2:0052). I can talk to the device through the serial console. I can flash the diags partition, diags kernel, and main kernel. All of which tells me something has to be working, right? Is there *any* way to completely nuke everything and start over? Maybe erase MMC0? I've seen various threads on this site claim to be able to repair a Kindle that has had its MMC0 nuked, but they all seem to be predicated on getting the main partition image successfully copied over to the USB user partition, which seems to be a problem for me. Thank you for your time.

04-15-2014, 11:44 PM	#25
TBennettcc Member Posts: 15 Karma: 10 Join Date: Mar 2014 Device: Kindle Touch	Could you do your best to explain why the flash is toast? Perhaps it's only me and my rudimentary understanding of flash memory, but isn't flash memory just a bunch of flip-flops that saves state in non-volatile RAM? To me, then, it would seem that a "bad update" would do nothing more that load a corrupted image into the NVRAM... not necessarily hurt anything physically? Let's say I still wanted to screw around with this thing, just for giggles and grins... What would be the downsides of erasing MMC0? Would that erase u-boot? How do I get the "special/hidden" files/data from the non-user areas before I nuke MMC0? Theoretically, if I erase MMC0, I should be able to: Code: a. boot to u-boot b. get into fastboot mode c. flash diags, diags kernel, and main kernel d. boot into diags e. enable USB drive mode f. copy main kernel to user area g. reboot to diags h. get to root serial console with login prompt i. load main partition from user area? Do you see anything wrong with the above? Am I underestimating the effects of erasing MMC0? (And even if the copy to the user area fails, at least I tried something else, even though it didn't work. All that means is that the flash really truly is toast, in which case it's only good for parts, or maybe a trade-in towards a new one with Amazon. As a friend of mine likes to say, "You can't broke broke! It's already broke! You can't broke it no more!") Thank you very much for your time. You've been a great help, and your detailed explanations have been fabulous.

04-16-2014, 10:08 AM	#26
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Thanks, (I think - ). The hard one first: Yup, flash is just a bunch of flip-flops and logic gates. So is the SoC on the main board and the SoC on the 3G board. (SoC: System On a Chip) About 210^9 8 of them or twice that on other Kindle models. So there is also quite a bit of structure to the device and management requirements of that structure. Some boring history (but might have keywords for web-searching): In the case of the most distant relative of today's flash chips - (Intel 1702 as I recall) The entire device was erased at once, by intense UV light. The device was programed in blocks by a high voltage programming circuit. (eprom : erasable, programmable, read-only, memory) The next step was to get rid of that "erase by intense UV light" and its quartz window on the chip carrier. Enter the eeprom: electrically erasable, programmable, read-only, memory. All of which was provided by external circuitry. As storage capacities increased, the external circuitry became more complex and over time was moved onto the same chip. That includes the management and control sequencing, which was moved into a (rom) programmed micro-controller. A "special function" computer in its own right. Also the erase and programming voltage generation was moved on-chip. But as a crude summary, the USB flash drive, these on-board flash chips, and even the SSD spinning rust replacements are just EEPROM devices on steroids (on triple steroids in the case of SSD devices). Same limitations on all variteties over the years: You can erase them, you can program them, you can read them BUT you CAN NOT write to them. Sorry, just can't be done. So the micro-controller has to "fake" the write operation. The management of the storage is done in "erase blocks" sized parts of the internal structure. 4,096 bytes * 8 bits + ecc bits + vendor defined bits + price of tea in china. It is interrupting the "life cycle" of an erase block by dropping the power at the wrong time which puts the device into a non-recoverable state. I.E: micro-controller's data says an erase block is erased and ready to be programmed (but the power failed before it could be erased completely). OR: micro-controller's data says an erase block has been re-programmed (but the programming power failed during the attempt). OR: other, less obvious, sequencing errors. That micro-controller is fairly complex, and on SSD devices, nearly a full computer in itself. But there are still limits to what it can detect and correct. If its database says that block 1603456 has been programmed (or erased), and assigned a readable address (or a "ready" address) - that is what it has to work with. The easiest to visualize is an incompletely erased erase block (because of power failure to the erase voltage generator) on the "ready" address list. So that is the next erase block it will try to program, but you can not program an un-erased, erase block. The device has been rendered useless. (the controller on an SSD is a lot "smarter" than that, but you still don't want to disconnect their power while they are sequencing) Doing an "erase mmc" (a full device erase) may or may not allow the controller to re-cover some of the storage capacity. Chances are: slim - to - none. - - - - - The easy one: Device and owner specific information is stored on the device, outside of the partitioned areas. You need to make a copy of that (and write it back) to make the Kindle "work" after a full device erase. Geekmaster has posted scripts and directions - probably in the older, manual, de-bricking threads. The "erase mmc" command will also (after erasing the device) re-write the u-boot area with the copy of u-boot currently running in ram. According to the comments in the Amazon source code, the failure to save and restore the "device and owner" data is an error in the diags programming, which I think has never been fixed.

01-04-2015, 12:17 PM	#27
TBennettcc Member Posts: 15 Karma: 10 Join Date: Mar 2014 Device: Kindle Touch	Recently received a PM requesting some information on my serial cable and setup. I thought I would post my response here so that others may benefit: I made my purchase from Mouser: Serial Cable: 895-TTL232RGVREG1V8W Plastic Header: 538-78172-0003 Pins for header: 538-78172-0410-CT From RadioShack: 278-502 - 30 AWG wrapping wire I used the wrapping wire to make the connection between the small header pins and the serial cable output. Be aware, you will probably need a high-power magnifier, as these things are small. I think I ended up using the edge of a knife to fold the 'arms' of the connectors onto the stripped wrapping wire. They fit into the white connector nicely, and mated perfectly with the connector on the Kindle Touch. These parts are accurate for the Kindle Touch. Some of the other Kindles also need the socket to be soldered on the board. I do not have that information. Cable datasheet: TTL-232RG Datasheet Cable information and drivers (you want the VCP drivers): FTDI USB-to-Serial Cable information / Drivers That should get you started.

10-24-2015, 12:25 PM	#28
rohitpsk Junior Member Posts: 9 Karma: 10 Join Date: Oct 2015 Location: Ludhiana Device: Kindle Paperwhite second generation	Looks like I am having the same problem. Any way this can be resolved or has been resolved? https://www.mobileread.com/forums/sho...d.php?t=266726

10-24-2015, 03:20 PM	#30
rohitpsk Junior Member Posts: 9 Karma: 10 Join Date: Oct 2015 Location: Ludhiana Device: Kindle Paperwhite second generation	What about this... http://www.powerbookmedic.com/Amazon...3-p-46083.html