Kindle Touch can not flash, seems readonly

scottzhao · 09-18-2014, 10:41 AM

My Kindle Touch got bricked a few days ago due to low battery. After I charged whole day, it could boot up, looked OK, but book list was empty. Then I found WIFI not work, device info show "MAC unavailable". I reset and rebooted several times, no use, WIFI still dead. It was strange, when I connected to PC, I could see all books in documents folder, but Kindle could not list them at all. I formatted USB drive, it looked empty and no errors. After rebooting, everything came back again, all books under documents show again,

Then I tried to flash it with Kubrick 3.6 DVD. At beginning, in fastboot, diags flashed very fast, only took 2-3 seconds. but KT rebooted into main mode instead of diags. I manually rebooted it into diags with KindleSelectBoot on another PC and went back to Kubrick to continue with USBNet enabled. Kubrick recognized KT and went on, until flashing Jailbreak and format internal drive, it popped up "failed". Then I rebooted KT, it could enter main mode, nothing changed, all books were still there and WIFI still not work.

Then I manually do fastboot on PC and flash diag-ssh. fastboot response OK, then I went into daigs, USBnet enabled, I used Putty to ssh 192.168.15.244, it popped "connection refused". I waited long time and tried many times, still no connection.

Then I doubted maybe the whole file system is in Read Only mode, so Diags-ssh was not flashed successfully at all.

I checked old threads and found one met same problem, but no specific solution mentioned.

I don't know what goes wrong with my KT, I debricked several K4 with Kubrick or manually before, all successfully. No similar issue met.

Anyone can help?

does it mean hardware failure , flash chip damaged?

Thanks.

knc1 · 09-18-2014, 10:55 AM

Quote:

Originally Posted by scottzhao

- - - -
Does it mean hardware failure , flash chip damaged?

Thanks.

Sounds like it to me.
Info: https://www.mobileread.com/forums/sho...49&postcount=3

The K5 is usually quite easy for Kubrick to recover, but those device's batteries are all getting a bit old.

scottzhao · 09-20-2014, 10:55 AM

I got serial port adapter today and soldered 3 wires according to old posts, but SecureCRT got no message at all.
Anything wrong ?
My adapter is 1.8V .

If KT face down, the serial port plug on bottom should be RX, TX, GRD from left to right?
Wires should connect to TTL adapter's TX, RX, GRD, is it right?

Any suggestion?

knc1 · 09-20-2014, 11:11 AM

Quote:

Originally Posted by scottzhao

I got serial port adapter today and soldered 3 wires according to old posts, but SecureCRT got no message at all.
Anything wrong ?
My adapter is 1.8V .

If KT face down, the serial port plug on bottom should be RX, TX, GRD from left to right?
Wires should connect to TTL adapter's TX, RX, GRD, is it right?

Any suggestion?

Is this a Kindle Touch (K5) or a Kindle Non-Touch (K4) ?
Use this table and the first four characters of your serial number to determine our naming system:
https://wiki.mobileread.com/wiki/Kindle_Serial_Numbers

Then, in the Wiki Index:
(K4) https://wiki.mobileread.com/wiki/K4_Index#Serial_Port
(K5) https://wiki.mobileread.com/wiki/K5_Index#Serial_Port

scottzhao · 09-22-2014, 10:44 AM

Today I made serial adapter working, I modified adapter and added a AA battery for 1.8V VCC, serial port finally working.

Thanks for friend above, my Kindle is Kindle Touch ( K5), SN:B011 XXXX XXXX XXXX. Firmware Ver. 5.3.7(2004410010).

I tried to format disk to fix readonly problem, but not working.

SecureCRT output as follows:

Spoiler:

It seems drive as errors, how to fix?

I don't know password for root.

Any suggestion?

Thanks.

scottzhao · 09-22-2014, 10:47 AM

further to above post, in "Recovery Menu", I select "O" or "I", seems not working.
I copied firmware "update_kindle_5.3.7.2.bin" into it and manually update on KT, still nothing improve. All old books are still there, and all filesystem ReadOnly.

knc1 · 09-22-2014, 10:58 AM

That should be /var/local partition -
The Kindle will not start properly with errors on that partition.

Also, putting it in "diags mode" to fix it will not work, since /var/local is the same partition in both "diags mode" and "main mode".

Installing a Kindle update package will not fix the problem, they don't touch /var/local.

Kubrick **should** have a menu entry that will clear (and force a re-format) of /var/local (and of the user storage partition).
Give that option a try (it is normally disabled).

scottzhao · 09-22-2014, 12:13 PM

I tried with Kubrick several times.

At beginning, when in fastboot mode, it seems flashed diags successfully, when rebooting, it goes into main instead of diags.This might mean the diags not flashed correctly. I used another PC to boot it into diags with SelectBoot, then went back to Kubrick, followed the instructions to enable USBnet, it went on, flashed main quickly ( quicker than normal, only 3-4 seconds, it should be 30 seconds or longer I think), then I ticked "install jailbreak" and "format internal storage", now Kubrick stopped and popped up "failed".
It seems Kubrick can not clear internal storage at all. I think "/var/local" not changed either.

"Kubrick **should** have a menu entry that will clear (and force a re-format) of /var/local (and of the user storage partition).Give that option a try (it is normally disabled)"

Would you please tell me where this option in Kubrick? I checked around and could not find this option. I tried almost all options in Kubrick already.

Is there anyway to force a re-format) of /var/local (and of the user storage partition) via serial port?

Thanks.

knc1 · 09-22-2014, 01:53 PM

Quote:

Originally Posted by scottzhao

- - - - -

Is there anyway to force a re-format) of /var/local (and of the user storage partition) via serial port?

Thanks.

Yes.
But since mmcblk0p3 (/var/local) is mounted in both "diags mode" and "main mode" you have to catch the boot sequence while the Kernel is still running in its ram-resident, initramfs.

There is a u-boot prompt - -
Then a bit later, another ("hit any key") prompt -
That is the one from the initramfs start-up that you want.

I do not recall what all tools (commands) you have available at that point.

None of the eMMC partitions should be mounted at that point.

The thing you want to do, is make /dev/mmcblk0p3 and /dev/mmcblk0p4 appear to be unformatted.
The usual thing is to write 4, 4096 byte blocks to the start of the partition you want to force a format of.

If the 'dd' command is available in initramfs -
dd if=/dev/zero of=/dev/mmcblk0p3 bs=4096 count=4
(*p3 is /var/local, *p4 is /mnt/usr (user storage) )

web search engines can find you the manual page on dd (and any other *nix command), as in:
http://linux.die.net/man/1/dd

scottzhao · 09-23-2014, 09:51 AM

I can stop at Uboot and input bist, result is as follows, is there any thing I can do in with bist command?

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

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
cspi clock : 54000000Hz
ahb clock : 100000000Hz
axi_a clock : 400000000Hz
axi_b clock : 200000000Hz
weim_clock : 100000000Hz
ddr clock : 200000000Hz
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: 00614011144508VG
S/N: B011140714740V0J
I2C: ready
DRAM: 256 MB
Using default environment

In: serial
Out: serial
Err: serial
POST done in 2 ms
Battery voltage: 4096 mV

bist > ?
? - alias for 'help'
autoscr - DEPRECATED - use "source" command instead
base - print or set address offset
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
check - perform MMC CRC32 check
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
diag - perform board diagnostics
echo - echo args to console
fail - fail blink fail pattern on LED
fastboot- Fastboot
fstor - File Storage
go - start application at address 'addr'
halt - halt board
help - print online help
i2c - I2C sub-system
idme - idme - Set nv ram variables

iminfo - print header information for application image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
loopw - infinite write loop on address range
md - memory display
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - mmcinfo <dev num>-- display MMC info
mtest - simple RAM read/write test
mw - memory write (fill)
nm - memory modify (constant address)
ocotp - OCOTP sub system
panic - panic halt
pass - pass blink pass pattern on LED
pmic - pmic - PMIC utility commands

printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
sleep - delay execution for some time
source - run script from memory
sspi - SPI utility commands
version - print monitor version
bist >

knc1 · 09-23-2014, 10:03 AM

Quote:

Originally Posted by scottzhao

I can stop at Uboot and input bist, result is as follows, is there any thing I can do in with bist command?
- - - -
bist >

The "bist command" is just a full build of u-boot.

If you mean: "Anything I can do to fix the device partition errors"
Answer: No.
(at least not without the Kindle's address map while in bist)

- - - - -

You could change the kernel command line to make it stay in its ram-resident initramfs mode and not continue to boot one of the on-flash systems.

But you don't need to do that, just don't interrupt the boot sequence until you see the kernel's first prompt (issued from initramfs mode, to stop the kernel's boot sequence at that point).

scottzhao · 09-23-2014, 10:14 AM

I tried to stop after Uboot, it shows as follows:

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: 00614011144508VG
S/N: B011140714740V0J
DRAM: 256 MB
Using default environment

In: serial
Out: logbuff
Err: logbuff
Quick Memory Test 0x70000000, 0xfffe000
POST done in 13 ms
Hit any key to stop autoboot: 0
uboot > ?
? - alias for 'help'
bist - start Built In Self Test
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
go - start application at address 'addr'
help - print online help
idme - idme - Set nv ram variables

log - manipulate logbuffer
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
setenv - set environment variables
version - print monitor version
uboot > dd if=/dev/zero of=/dev/mmcblk0p3 bs=4096 count=4
Unknown command 'dd' - try 'help'
uboot > <INTERRUPT>
uboot >

It seems enter uboot menu, DD command not available here.
Anything I can do?

Thanks

knc1 · 09-23-2014, 10:21 AM

Too soon. That was the u-boot prompt, wait for the kernel boot prompt.

scottzhao · 09-23-2014, 10:36 AM

"interrupt the boot sequence until you see the kernel's first prompt (issued from initramfs mode, to stop the kernel's boot sequence at that point)."

How to interrupt the boot sequence ?

I hit ENTER, then it stopped at Uboot. If I don't hit key, it continued, I could not stop booting.

Another problem is I tried in recovery menu to select "O" or "E", it seems no use, after 10 seconds, booting continued.

Thanks.

knc1 · 09-23-2014, 11:20 AM

From u-boot prompt -
**without** running any other command or doing any changes to anything -
enter: bootd
With finger ready to hit any other key after kernel starts to output text.

You have a one or two second window to get it right.
(And if your running a terminal emulator under windows, the opportunity will probably be long gone before windows prints anything.)

09-18-2014, 10:41 AM	#1
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	Kindle Touch can not flash, seems readonly My Kindle Touch got bricked a few days ago due to low battery. After I charged whole day, it could boot up, looked OK, but book list was empty. Then I found WIFI not work, device info show "MAC unavailable". I reset and rebooted several times, no use, WIFI still dead. It was strange, when I connected to PC, I could see all books in documents folder, but Kindle could not list them at all. I formatted USB drive, it looked empty and no errors. After rebooting, everything came back again, all books under documents show again, Then I tried to flash it with Kubrick 3.6 DVD. At beginning, in fastboot, diags flashed very fast, only took 2-3 seconds. but KT rebooted into main mode instead of diags. I manually rebooted it into diags with KindleSelectBoot on another PC and went back to Kubrick to continue with USBNet enabled. Kubrick recognized KT and went on, until flashing Jailbreak and format internal drive, it popped up "failed". Then I rebooted KT, it could enter main mode, nothing changed, all books were still there and WIFI still not work. Then I manually do fastboot on PC and flash diag-ssh. fastboot response OK, then I went into daigs, USBnet enabled, I used Putty to ssh 192.168.15.244, it popped "connection refused". I waited long time and tried many times, still no connection. Then I doubted maybe the whole file system is in Read Only mode, so Diags-ssh was not flashed successfully at all. I checked old threads and found one met same problem, but no specific solution mentioned. I don't know what goes wrong with my KT, I debricked several K4 with Kubrick or manually before, all successfully. No similar issue met. Anyone can help? does it mean hardware failure , flash chip damaged? Thanks. Last edited by scottzhao; 10-04-2014 at 10:26 PM.

09-22-2014, 10:44 AM	#5
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	Today I made serial adapter working, I modified adapter and added a AA battery for 1.8V VCC, serial port finally working. Thanks for friend above, my Kindle is Kindle Touch ( K5), SN:B011 XXXX XXXX XXXX. Firmware Ver. 5.3.7(2004410010). I tried to format disk to fix readonly problem, but not working. SecureCRT output as follows: Spoiler: 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: 00614011144508VG S/N: B011140714740V0J DRAM: 256 MB Using default environment In: serial Out: logbuff Err: logbuff Quick Memory Test 0x70000000, 0xfffe000 POST done in 13 ms Hit any key to stop autoboot: 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: 5189664 Bytes = 4.9 MB Load Address: 70008000 Entry Point: 70008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... 2.6.31-rt11-lab126 #1 Fri Jul 12 02:22:50 PDT 2013 armv7l INFO:Loaded module /lib/modules/eink_fb_waveform.ko (39524 bytes) INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_update_mode=1 (50808 bytes) INFO:eink initialized... (486400 bytes) INFO:Using default keypad setting. (not passing "kb_rev" to module) INFO:Loaded module /lib/modules/whitney_button.ko (9268 bytes) Press [ENTER] for recovery menu... 0 / INFO:!!! Checking MBR /dev/mmcblk0 !!!! INFOartition 2, start sector is 782336 INFOartition 3, start sector is 913408 INFOartition 4, start sector is 978944 INFO:maximizing partition 6754304 sectors INFO:* Partition table verified for /dev/mmcblk0 * INFO:Loaded module /lib/modules/arcotg_udc.ko (46872 bytes) INFO:Loaded module /lib/modules/g_file_storage.ko recovery_mode=1 (36196 bytes) Charge: 98% [################################################## ########] 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: 1 - Menu timeout fsl-usb2-udc fsl-usb2-udc: dma_pool_destroy udc_td, fa416000 busy INFO:Couldn't find localized image at /mnt/wfm/images/splash.raw.gz BOOTING DEFAULT. argc == 10 argv[0]: "kinit" argv[1]: "consoleblank=0" argv[2]: "rootwait" argv[3]: "ro" argv[4]: "ip=off" argv[5]: "root=/dev/mmcblk0p1" argv[6]: "quiet" argv[7]: "eink=fslepdc" argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=2M" argv[9]: "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/mmcblk0p1) = dev(179,1) kinit: root_dev = dev(179,1) 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. info system:emiting_event:mounted_proc: info system:emiting_event:mounted_sys: info firsttime:mount_rw:time=15900:Mounting root RW for first boot info firsttime:lostfound:Removing lost+found: info firsttime:mtab:Linking /var/tmp: info firsttime:mtab:Linking Kindle Registry: info firsttime:xorgconf:Linking xorg.conf: info firsttime:cursor:Linking Xorg cursor: info firsttime:guid:Generating guid: info firsttime:mount_ro:time=17300:Mounting root RO info system:emiting_event:mounted_dev: info system:emiting_event:mounted_tmpfs: info milestone:17.46:sy50: init.exe: recevent pre-start process (561) terminated with status 1 info system:start:time=17520: info hardware:no_wan::WiFi only device. No WAN found info system:configlatform=yoshi,board=whitney,rev=20, proto=N,wifi=Y,wan=N: info milestone:17.74:sy51: info milestone:18.44:sy99: info system:done:time=18470: info system_cramfs_loopbacks:mountingcramfs:Mounting compressed directories filesystem images: info system_cramfs_loopbacks:mounted:Image /lib/firmware/cyttsp.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/share/X11/xkb.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/java/lib/fonts.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /etc/kdb.src.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/lib/locale.cramfs.img mounted: info system_cramfs_loopbacks:mounted:Image /usr/share/keyboard.cramfs.img mounted: info system:emiting_event:mounted_cramfs_loopbacks: info milestone:19.04:fs75: info system:emiting_event:loaded_modules_dependencies: info modules:modprobe:loading module g_file_storage: info system:emiting_event:loaded_g_file_storage: info modules:modprobe:loading module fuse: info system:emiting_event:loaded_fuse: info hardware:no_wan::WiFi only device. No WAN found info system:emiting_event:loaded_ppp_async: info milestone:19.47:fs00: info modules:modprobe:loading module whitney_button: Welcome to Kindle! kindle login: info system:emiting_event:loaded_whitney_button: info system:emiting_event:mounted_varLocal: info milestone:19.67:fs25: info milestone:19.69:vi00: info zforce:start:version=2.0b0r12: info system:emiting_event:loaded_touch: info milestone:20.03:vi99: info display:started:time=20040: info system:emiting_event:display_ready: info battery:charged:cap=98,mV=4154,mAH=1159: info userstore:run:time=20290,action=start: info system:emiting_event:battery_ready: info userstore:found_bootup_flag::Found BOOTUP flag file boot: I def:rbt:reset=user_reboot,version=200441: info mntus:fs_error_recover::File system errors recovered info system:emiting_event:mounted_userstore: info milestone:76.40:fs50: info milestone:76.42:fs90: info milestone:76.44:fs99: info milestone:76.47:sys99: info system:emiting_event:dbus_ready: info dbus:check-update:status=2:dbus_ready sent info hardware:no_wan::WiFi only device. No WAN found info milestone:77.66:xx00: info X:load:time=77780: info X:xorg.conf:Generating xorg.conf: warn ttsd:upstart_ttsd_exited:: info X:makexconfig:Whitney Input device detection status: info X:makexconfig:Keypad: OK: info X:makexconfig:Touch device: OK: info X:makexconfig:Accelerometer device: N/A !!: info X:xorg.conf:xorg.conf generated: info milestone:79.24:xx50: info X:starting:time=79320: info milestone:86.10:xx99: info X:started:time=86120: info system:emiting_event:x_setup_ready: info locale:read:lang=en_US.utf8,lc_all=en_US.utf8:Retr ieved Language info system:emiting_event:langpicker_ready: info blanket_f:module already loaded:splash: info milestone:87.40i00: info milestone:87.40:fr00: info milestone:87.79i99: info milestone:87.80:fr50: info milestone:87.83:fr51: info framework:starting:time=88010: info hardware:no_wan::WiFi only device. No WAN found EXT3-fs error (device mmcblk0p3): htree_dirblock_to_tree: bad entry in directory #2426: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 EXT3-fs error (device mmcblk0p3): htree_dirblock_to_tree: bad entry in directory #2424: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 ..................... It seems drive as errors, how to fix? I don't know password for root. Any suggestion? Thanks. Last edited by Dr. Drib; 09-22-2014 at 12:35 PM. Reason: S/N redacted ;) -- NiLuJe

09-23-2014, 11:20 AM	#15
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	From u-boot prompt - without running any other command or doing any changes to anything - enter: bootd With finger ready to hit any other key after kernel starts to output text. You have a one or two second window to get it right. (And if your running a terminal emulator under windows, the opportunity will probably be long gone before windows prints anything.) Last edited by knc1; 09-23-2014 at 11:23 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
GNU Gnash – Flash player for Kindle Touch	baf	Kindle Developer's Corner	35	09-30-2014 08:50 AM
Touch Bricked Kobo Touch - no internal SD card (flash memory chip instead)	bher	Kobo Reader	6	07-30-2014 06:22 PM
Kindle Touch: Bricked and readonly filesystem	pmugabi	Kindle Developer's Corner	6	09-17-2012 01:50 AM
flash my Kindle Touch using windows, how?	ldai	Kindle Developer's Corner	1	03-23-2012 04:08 PM
Readonly Database	seanbw	Calibre	6	03-17-2010 06:30 PM

09-20-2014, 10:55 AM	#3
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	I got serial port adapter today and soldered 3 wires according to old posts, but SecureCRT got no message at all. Anything wrong ? My adapter is 1.8V . If KT face down, the serial port plug on bottom should be RX, TX, GRD from left to right? Wires should connect to TTL adapter's TX, RX, GRD, is it right? Any suggestion?

09-22-2014, 10:47 AM	#6
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	further to above post, in "Recovery Menu", I select "O" or "I", seems not working. I copied firmware "update_kindle_5.3.7.2.bin" into it and manually update on KT, still nothing improve. All old books are still there, and all filesystem ReadOnly.

09-22-2014, 10:58 AM	#7
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	That should be /var/local partition - The Kindle will not start properly with errors on that partition. Also, putting it in "diags mode" to fix it will not work, since /var/local is the same partition in both "diags mode" and "main mode". Installing a Kindle update package will not fix the problem, they don't touch /var/local. Kubrick should have a menu entry that will clear (and force a re-format) of /var/local (and of the user storage partition). Give that option a try (it is normally disabled).

09-22-2014, 12:13 PM	#8
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	I tried with Kubrick several times. At beginning, when in fastboot mode, it seems flashed diags successfully, when rebooting, it goes into main instead of diags.This might mean the diags not flashed correctly. I used another PC to boot it into diags with SelectBoot, then went back to Kubrick, followed the instructions to enable USBnet, it went on, flashed main quickly ( quicker than normal, only 3-4 seconds, it should be 30 seconds or longer I think), then I ticked "install jailbreak" and "format internal storage", now Kubrick stopped and popped up "failed". It seems Kubrick can not clear internal storage at all. I think "/var/local" not changed either. "Kubrick should have a menu entry that will clear (and force a re-format) of /var/local (and of the user storage partition).Give that option a try (it is normally disabled)" Would you please tell me where this option in Kubrick? I checked around and could not find this option. I tried almost all options in Kubrick already. Is there anyway to force a re-format) of /var/local (and of the user storage partition) via serial port? Thanks.

09-23-2014, 09:51 AM	#10
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	I can stop at Uboot and input bist, result is as follows, is there any thing I can do in with bist command? U-Boot 2009.08-lab126 (Nov 10 2011 - 00:14:55) 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 cspi clock : 54000000Hz ahb clock : 100000000Hz axi_a clock : 400000000Hz axi_b clock : 200000000Hz weim_clock : 100000000Hz ddr clock : 200000000Hz 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: 00614011144508VG S/N: B011140714740V0J I2C: ready DRAM: 256 MB Using default environment In: serial Out: serial Err: serial POST done in 2 ms Battery voltage: 4096 mV bist > ? ? - alias for 'help' autoscr - DEPRECATED - use "source" command instead base - print or set address offset boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory check - perform MMC CRC32 check cmp - memory compare coninfo - print console devices and information cp - memory copy crc32 - checksum calculation diag - perform board diagnostics echo - echo args to console fail - fail blink fail pattern on LED fastboot- Fastboot fstor - File Storage go - start application at address 'addr' halt - halt board help - print online help i2c - I2C sub-system idme - idme - Set nv ram variables iminfo - print header information for application image itest - return true/false on integer compare loadb - load binary file over serial line (kermit mode) loads - load S-Record file over serial line loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range loopw - infinite write loop on address range md - memory display mm - memory modify (auto-incrementing address) mmc - MMC sub system mmcinfo - mmcinfo <dev num>-- display MMC info mtest - simple RAM read/write test mw - memory write (fill) nm - memory modify (constant address) ocotp - OCOTP sub system panic - panic halt pass - pass blink pass pattern on LED pmic - pmic - PMIC utility commands printenv- print environment variables reset - Perform RESET of the CPU run - run commands in an environment variable setenv - set environment variables sleep - delay execution for some time source - run script from memory sspi - SPI utility commands version - print monitor version bist >

09-23-2014, 10:14 AM	#12
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	I tried to stop after Uboot, it shows as follows: 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: 00614011144508VG S/N: B011140714740V0J DRAM: 256 MB Using default environment In: serial Out: logbuff Err: logbuff Quick Memory Test 0x70000000, 0xfffe000 POST done in 13 ms Hit any key to stop autoboot: 0 uboot > ? ? - alias for 'help' bist - start Built In Self Test boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory go - start application at address 'addr' help - print online help idme - idme - Set nv ram variables log - manipulate logbuffer printenv- print environment variables reset - Perform RESET of the CPU run - run commands in an environment variable setenv - set environment variables version - print monitor version uboot > dd if=/dev/zero of=/dev/mmcblk0p3 bs=4096 count=4 Unknown command 'dd' - try 'help' uboot > <INTERRUPT> uboot > It seems enter uboot menu, DD command not available here. Anything I can do? Thanks

09-23-2014, 10:21 AM	#13
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Too soon. That was the u-boot prompt, wait for the kernel boot prompt.

09-23-2014, 10:36 AM	#14
scottzhao Member Posts: 11 Karma: 10 Join Date: Sep 2014 Device: Kindle Touch	"interrupt the boot sequence until you see the kernel's first prompt (issued from initramfs mode, to stop the kernel's boot sequence at that point)." How to interrupt the boot sequence ? I hit ENTER, then it stopped at Uboot. If I don't hit key, it continued, I could not stop booting. Another problem is I tried in recovery menu to select "O" or "E", it seems no use, after 10 seconds, booting continued. Thanks.

Advert

Advert