Boot loop - what's wrong?

[geekmaster]

Originally Posted by abarthch

@geekmaster
Where can I find a sample text for the RUNME.sh?

I have MANY scripts on my hard drives called RUNME.sh, but none of them on my currently mounted drives contain a boot counter reset. Here is an example RUNME.sh that you may modify as you wish:

PHP Code:

#!/bin/sh
#only run if no RUNME.done file
test -f /mnt/us/RUNME.done && exit

# reset "needs repair" boot counter:
echo 0 > /var/local/upstart/lab126_gui.restarts

# prevent running until RUNME.done deleted
touch /mnt/us/RUNME.done 


I just typed this now. I did not test it...

[abarthch]

Thanks, but I wasn't successful.

However... something happened and now the boot loop is gone. But as soon as I touch the screen to enter the settings menu or try to open book it reboots again. Also the USB mode still doesn't work.

Is there a command I can send over in this state, e.g. to reset the device? I tried to send over the 'cat' line to at least reset the boot counter, but it asked for a password.

[geekmaster]

Originally Posted by abarthch

Thanks, but I wasn't successful.

However... something happened and now the boot loop is gone. But as soon as I touch the screen to enter the settings menu or try to open book it reboots again. Also the USB mode still doesn't work.

Is there a command I can send over in this state, e.g. to reset the device? I tried to send over the 'cat' line to at least reset the boot counter, but it asked for a password.

Asking for a password is good. You can compute the password from the serial number (if you recorded it). Rebooting as you described could be low battery, or full /var/local, or a hardware problem. You could try swapping batteries with another device. I do not yet have a PW3 so I cannot easily figure other methods to get past such a problem. The serial number should also be in the log files on the user store partition (i.e. kindle USB drive), if you have momentary access to it during the boot process (but you may need a looping host script to grab it quickly), and you many be much more successful running linux on the host because windows always writes a readyboost temp file on a drive to ask you if you want to use it for readyboost (if it is fast enough), even before you have a chance to access the drive (which sucks if you plan to do data recovery on the device).

[geekmaster]

Now the PW3 described in this thread is in my hands. I guess the first step will be the serial port. Perhaps I need to remove the battery and charge it with a standalone lithium battery charger. I will post results.

Serial capture mentioned previously:

Spoiler:

PHP Code:

U-Boot 2009.08-lab126 (Apr 15 2015 - 07:37:55)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   29 C, calibration data 0x5574df5f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Muscat WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 0670************
S/N: G090G1**********
I2C:   ready
DRAM:  512 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0x1fff0000
POST done in 112 ms
Battery voltage: 4000 mV

Hit any key to stop autoboot:  1  0 
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.0.35-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2634464 Bytes =  2.5 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.098505] No Legacy reboot reason code to print
[    0.292290] LPDDR2 MfgId: 0x5 [Nanya]
[    0.295978] 
[    0.295981] just text: vaddr c0150d44, va 0xc0150200 pa 0x801000c3 attr 0x6
[    0.308585] 
[    0.308589] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.317505] 
[    0.317508] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.325799] 
[    0.325801] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.334585] 
[    0.334588] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.344919] 
[    0.344922] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.358055] 
[    0.358058] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.368448] 
[    0.368451] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.381338] 
[    0.381341] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 PREEMPT Wed Apr 15 08:08:43 PDT 2015 armv7l
Press [ENTER] for recovery menu...       0 //dev/mmcblk0p4:
CHS=4/16/99776 size=3269459968 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6385648
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Mounted root (ext3 filesystem) readonly.
info sytem:mounted_proc::
info system:mounted_sys::
info system:mounted_dev::
info milestone:6.93:49.1:
info milestone:6.98:49.2:
info milestone:7.00:49.3:
info milestone:7.04:49.4:
info milestone:7.07:49.5:
info sytem:mounted_tmpfs::
info milestone:7.14:sy50:
info system:start:time=7170:
info hardware:no_wan::WiFi only device. No WAN found
info system:config:platform=wario,board=muscat,rev=2,proto=Y,wifi=Y,wan=N:
info milestone:7.31:sy51:
lipc-send-event[809]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[808]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[809]: C def:dbusi::Failed to init dbus
lipc-send-event[809]: E def:open::Failed to open LIPC
lipc-send-event[809]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
lipc-send-event[808]: C def:dbusi::Failed to init dbus
lipc-send-event[808]: E def:open::Failed to open LIPC
lipc-send-event[808]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
info milestone:8.20:sy99:
info system:done:time=8230:
crond[825]: crond: crond (busybox 1.17.1) started, log level 8
iniü.exe: sshd main process (823)init.exe: sshd main process ended, respawning
info system_cramfs_loopbacks:mountingcramfs:Mounting compressed directories filesystem images:
init.exe: recevent pre-start process (828) terminated with status 1
warn system_cramfs_loopbacks:mountpointmissing:Image /lib/firmware/cyttsp.cramfs.img not mounted, non existing mounting point:
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:
debug sytem:event_emitted:mounted_cramfs_loopbacks:
info milestone:8.89:fs75:
info system:emiting_event:loaded_modules_dependencies:
debug sytem:event_emitted:loaded_modules_dependencies:
info modules:modprobe:loading module g_file_storage:
info system:emiting_event:loaded_g_file_storage:
debug sytem:event_emitted:loaded_g_file_storage:
info modules:modprobe:loading module fuse:
info system:emiting_event:loaded_fuse:
debug sytem:event_emitted:loaded_fuse:
info hardware:no_wan::WiFi only device. No WAN found
info system:emiting_event:loaded_ppp_async:
info milestone:9.12:fs00:
debug sytem:event_emitted:loaded_ppp_async:
info system:emiting_event:loaded_fakekey:
debug sytem:event_emitted:loaded_fakekey:
info milestone:9.22:fs23:
info system:emiting_event:mounted_varLocal:
debug sytem:event_emitted:mounted_varLocal:
info milestone:9.27:fs25:
info milestone:9.30:vi00:



Welcome to Kindle!

kindle login: info prereg:PRAGMA_QUICK_CHECK_PASSED::sts=0
info display:update:Checking '/opt/eink/images/R046_ED060KD1C1' for overrides:
info cyttsp4:update:cyttsp4 fw ver=000E file version=000E:
info system:emiting_event:loaded_touch:
debug sytem:event_emitted:loaded_touch:
info milestone:11.48:vi99:
info display:started:time=11500:
info system:emiting_event:display_ready:
debug sytem:event_emitted:display_ready:
info userstore:run:time=11690,action=start:
info userstore:start:found_bootup_flag:Found BOOTUP flag file
info battery:charged:cap=77,mV=4001,mAH=1140:
info system:emiting_event:battery_ready:
debug sytem:event_emitted:battery_ready:
info system:emiting_event:mounted_userstore:
debug sytem:event_emitted:mounted_userstore:
info milestone:13.09:fs50:
info milestone:13.12:fs90:
info milestone:13.16:fs99:
info milestone:13.20:sys99:
info system:emiting_event:devcap_ready:
debug sytem:event_emitted:devcap_ready:
info system:emiting_event:dbus_ready:
debug sytem:event_emitted:dbus_ready:
info dbus:check-update:status=2:dbus_ready sent
info hardware:no_wan::WiFi only device. No WAN found
info milestone:14.57:xx00:
info X:load:time=14670:
info X:xorg.conf:Generating xorg.conf:
info X:xorg.conf:xorg.conf generated:
info milestone:16.01:xx50:
info X:starting:time=16070:
info milestone:18.88:xx99:
info X:started:time=18920:
info system:emiting_event:x_setup_ready:
debug sytem:event_emitted:x_setup_ready:
info locale:read:lang=en_GB.utf8,lc_all=en_GB.utf8:Retrieved Language
info system:emiting_event:langpicker_ready:
debug sytem:event_emitted:langpicker_ready:
info blanket_f:module already loaded:splash:
info milestone:19.66:pi00:
info milestone:19.87:pi99:
info system:emiting_event:contentpack_font_ready:
debug sytem:event_emitted:contentpack_font_ready:
info milestone:23.39:fr00:
info milestone:23.50:fr50:
info milestone:23.53:fr51:
info framework:starting:time=25070:
info hardware:no_wan::WiFi only device. No WAN found
info board_data_file :/opt/ar6k/target/AR6003/hw2.1.1/bin/wario/muscat/wfo/AR6003_wfo_calfile.bin::
[   29.946374] ath6kl: ath6kl_fetch_board_file: Board calibration file fetched: /opt/ar6k/target/AR6003/hw2.1.1/bin/wario/muscat/wfo/AR6003_wfo_calfile.bin
[   30.050607] ath6kl: MAC from kernel xx:xx:xx:xx:xx:E9
[   30.486337] ath6kl: host only supports scatter of :1 entries, need: 16


U-Boot 2009.08-lab126 (Apr 15 2015 - 07:37:55)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   36 C, calibration data 0x5574df5f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Muscat WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 0670************
S/N: G090G1**********
I2C:   ready
DRAM:  512 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0x1fff0000
POST done in 111 ms
Battery voltage: 4002 mV

Hit any key to stop autoboot:  1  0 
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.0.35-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2634464 Bytes =  2.5 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.098504] boot: C def:rst:reset=hard
[    0.102291] boot: C def:rst:reset=hard
[    0.291527] LPDDR2 MfgId: 0x5 [Nanya]
[    0.295218] 
[    0.295221] just text: vaddr c0150d44, va 0xc0150200 pa 0x801000c3 attr 0x6
[    0.307757] 
[    0.307760] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.316637] 
[    0.316640] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.324988] 
[    0.324991] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.335764] 
[    0.335767] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.349164] 
[    0.349167] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.359128] 
[    0.359130] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.371538] 
[    0.371541] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.381391] 
[    0.381395] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 PREEMPT Wed Apr 15 08:08:43 PDT 2015 armv7l
Press [ENTER] for recovery menu...       0 //dev/mmcblk0p4:
CHS=4/16/99776 size=3269459968 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6385648
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Mounted root (ext3 filesystem) readonly.
info sytem:mounted_proc::
info system:mounted_sys::
info system:mounted_dev::
info milestone:6.93:49.1:
info milestone:6.99:49.2:
info milestone:7.03:49.3:
info milestone:7.07:49.4:
info milestone:7.10:49.5:
info sytem:mounted_tmpfs::
info milestone:7.19:sy50:
info system:start:time=7220:
info hardware:no_wan::WiFi only device. No WAN found
info system:config:platform=wario,board=muscat,rev=2,proto=Y,wifi=Y,wan=N:
info milestone:7.44:sy51:
lipc-send-event[809]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[808]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory)
lipc-send-event[809]: C def:dbusi::Failed to init dbus
lipc-send-event[809]: E def:open::Failed to open LIPC
lipc-send-event[809]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
lipc-send-event[808]: C def:dbusi::Failed to init dbus
lipc-send-event[808]: E def:open::Failed to open LIPC
lipc-send-event[808]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed
info milestone:8.33:sy99:
info system:done:time=8370:
crond[822]: crond: crond (busybox 1.17.1) started, log level 8
iniü.exe: sshd main process (820)init.exe: sshd main process ended, respawning
info system_cramfs_loopbacks:mountingcramfs:Mounting compressed directories filesystem images:
init.exe: recevent pre-start process (825) terminated with status 1
warn system_cramfs_loopbacks:mountpointmissing:Image /lib/firmware/cyttsp.cramfs.img not mounted, non existing mounting point:
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:
debug sytem:event_emitted:mounted_cramfs_loopbacks:
info milestone:9.03:fs75:
info system:emiting_event:loaded_modules_dependencies:
debug sytem:event_emitted:loaded_modules_dependencies:
info modules:modprobe:loading module g_file_storage:
info system:emiting_event:loaded_g_file_storage:
debug sytem:event_emitted:loaded_g_file_storage:
info modules:modprobe:loading module fuse:
info system:emiting_event:loaded_fuse:
debug sytem:event_emitted:loaded_fuse:
info hardware:no_wan::WiFi only device. No WAN found
info system:emiting_event:loaded_ppp_async:
info milestone:9.26:fs00:
debug sytem:event_emitted:loaded_ppp_async:
info system:emiting_event:loaded_fakekey:
debug sytem:event_emitted:loaded_fakekey:
info milestone:9.46:fs23:
info system:emiting_event:mounted_varLocal:
debug sytem:event_emitted:mounted_varLocal:
info milestone:9.51:fs25:
info milestone:9.54:vi00:



Welcome to Kindle!

kindle login: info prereg:PRAGMA_QUICK_CHECK_PASSED::sts=0
info display:update:Checking '/opt/eink/images/R046_ED060KD1C1' for overrides:
info cyttsp4:update:cyttsp4 fw ver=000E file version=000E:
info system:emiting_event:loaded_touch:
debug sytem:event_emitted:loaded_touch:
info milestone:11.73:vi99:
info display:started:time=11750:
info system:emiting_event:display_ready:
debug sytem:event_emitted:display_ready:
info userstore:run:time=11940,action=start:
info userstore:start:found_bootup_flag:Found BOOTUP flag file
info battery:charged:cap=77,mV=4001,mAH=1154:
info system:emiting_event:battery_ready:
debug sytem:event_emitted:battery_ready:
info system:emiting_event:mounted_userstore:
debug sytem:event_emitted:mounted_userstore:
info milestone:13.38:fs50:
info milestone:13.41:fs90:
info milestone:13.45:fs99:
info milestone:13.50:sys99:
info system:emiting_event:devcap_ready:
debug sytem:event_emitted:devcap_ready:
info system:emiting_event:dbus_ready:
debug sytem:event_emitted:dbus_ready:
info dbus:check-update:status=2:dbus_ready sent
info hardware:no_wan::WiFi only device. No WAN found
info milestone:14.55:xx00:
info X:load:time=14710:
info X:xorg.conf:Generating xorg.conf:
info X:xorg.conf:xorg.conf generated:
info milestone:16.45:xx50:
info X:starting:time=16500:
info milestone:20.21:xx99:
info X:started:time=20250:
info system:emiting_event:x_setup_ready:
debug sytem:event_emitted:x_setup_ready:
info locale:read:lang=en_GB.utf8,lc_all=en_GB.utf8:Retrieved Language
info system:emiting_event:langpicker_ready:
debug sytem:event_emitted:langpicker_ready:
info blanket_f:module already loaded:splash:
info milestone:20.99:pi00:
info milestone:21.21:pi99:
info system:emiting_event:contentpack_font_ready:
debug sytem:event_emitted:contentpack_font_ready:
info milestone:24.70:fr00:
info milestone:24.79:fr50:
info milestone:24.82:fr51:
info framework:starting:time=26400:
info hardware:no_wan::WiFi only device. No WAN found
info board_data_file :/opt/ar6k/target/AR6003/hw2.1.1/bin/wario/muscat/wfo/AR6003_wfo_calfile.bin::
[   30.013477] ath6kl: ath6kl_fetch_board_file: Board calibration file fetched: /opt/ar6k/target/AR6003/hw2.1.1/bin/wario/muscat/wfo/AR6003_wfo_calfile.bin
[   30.116391] ath6kl: MAC from kernel xx:xx:xx:xx:xx:E9
[   30.549610] ath6kl: host only supports scatter of :1 entries, need: 16
info milestone:52.06:fr99:
info framework:started:time=52090,delta=27280:
info blanket_f:loading blanket module:usb:
info blanket_f:unloading blanket module:splash:
info system:emiting_event:framework_ready:
debug sytem:event_emitted:framework_ready:
info stored:started::
info stored:read_in_counters:REBOOTS=0, REBOOT_LIMIT=1, RESTARTS=0, RESTART_LIMIT=5:
info monitor:writing_file:file=/var/run/upstart/stored.restarts:
Retrieved 314 keys for system/daemon/pmond/


U-Boot 2009.08-lab126 (Apr 15 2015 - 07:37:55)

CPU: Freescale i.MX6 family TO0.0 at 996 MHz
Temperature:   36 C, calibration data 0x5574df5f
mx6sl pll1: 996MHz
mx6sl pll2: 528MHz
mx6sl pll3: 480MHz
mx6sl pll8: 50MHz
ipg clock     : 66000000Hz
ipg per clock : 66000000Hz
uart clock    : 80000000Hz
cspi clock    : 60000000Hz
ahb clock     : 132000000Hz
axi clock   : 198000000Hz
emi_slow clock: 22000000Hz
ddr clock     : 396000000Hz
usdhc1 clock  : 198000000Hz
usdhc2 clock  : 198000000Hz
usdhc3 clock  : 198000000Hz
usdhc4 clock  : 198000000Hz
MMC:  FSL_ESDHC: 0,FSL_ESDHC: 1,FSL_ESDHC: 2
Board: Muscat WFO
Boot Reason: [ POR ]
Boot Device: NAND
Board Id: 0670************
S/N: G090G1**********
I2C:   ready
DRAM:  512 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Quick Memory Test 0x80000000, 0x1fff0000
POST done in 111 ms
Battery voltage: 4005 mV

Hit any key to stop autoboot:  1  0 
## Booting kernel from Legacy Image at 80800000 ...
   Image Name:   Linux-3.0.35-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2634464 Bytes =  2.5 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.098522] boot: C def:rst:reset=hard
[    0.102311] boot: C def:rst:reset=hard
[    0.291358] LPDDR2 MfgId: 0x5 [Nanya]
[    0.295047] 
[    0.295050] just text: vaddr c0150d44, va 0xc0150200 pa 0x801000c3 attr 0x6
[    0.307590] 
[    0.307594] nmx6sl_wfi_iram: vaddr e084e000, va 0xe084e200 pa 0x904043 attr 0x2
[    0.316470] 
[    0.316474] mx6sl_ddr: vaddr e0856000, va 0xe0856200 pa 0x905043 attr 0x2
[    0.324820] 
[    0.324823] mx6sl_iomux: vaddr f40e0000, va 0xf40e0200 pa 0x20110c3 attr 0x149
[    0.335593] 
[    0.335596] ANATOP: vaddr f40c8000, va 0xf40c8200 pa 0x20110c3 attr 0x149
[    0.348991] 
[    0.348994] CCM: vaddr f40c4000, va 0xf40c4200 pa 0x20110c3 attr 0x149
[    0.358954] 
[    0.358957] MMDC_P0: vaddr f41b0000, va 0xf41b0200 pa 0x21110c3 attr 0x149
[    0.371369] 
[    0.371372] L2: vaddr f2a02000, va 0xf2a02200 pa 0xa02043 attr 0x149
[    0.381221] 
[    0.381225] arm perif: vaddr f2a00000, va 0xf2a00200 pa 0xa00043 attr 0x149
3.0.35-lab126 #1 PREEMPT Wed Apr 15 08:08:43 PDT 2015 armv7l
^[Press [ENTER] for recovery menu...       0 //dev/mmcblk0p4:
CHS=4/16/99776 size=3269459968 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    6385648
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4: 


[knc1]

If you can get even momentary access to USB storage -
Put an empty file, no file extension, all uppercase:
DO_FACTORY_RESTORE
at the visible root of USB storage, reboot.

Ref: https://www.mobileread.com/forums/sho...78&postcount=1
(Yes, it works with the newer devices also.)

[geekmaster]

Originally Posted by knc1

If you can get even momentary access to USB storage -
Put an empty file, no file extension, all uppercase:
DO_FACTORY_RESTORE
at the visible root of USB storage, reboot.

Ref: https://www.mobileread.com/forums/sho...78&postcount=1
(Yes, it works with the newer devices also.)

It stopped the boot loop. Stuck at the kindle tree. When plugged into computer, it cycles into "USB charger" mode (with backlight on), as detected by virtualbox usb settings. Then less than a second later it disappears (no USB device, backlight off), and repeats after a few seconds (or not). Inconsistent behavior. Earlier I got it to display various screens like ;611, and setings/device info. It rebooted on power adapter and got to 30% progress, but stalled when plugged into computer.

Different behavior depending on USB connection. The log provided by the OP looks like it reboots with no warning or error message. Serial port time, I think...

And when it did allow some settings menu access, plugging in USB cable did immediate reboot. But then just letting it sit awhile on the charger reboots eventually too...

And when I did get a screensaver up (by tapping the power button), it was ugly black and white, so there must be an eink waveform issue as well (though the eink wavefile analysis in the serial capture does not report an error). I wonder if the screen had been replaced at some point...

[knc1]

Originally Posted by geekmaster

It stopped the boot loop. Stuck at the kindle tree. When plugged into computer, it cycles into "USB charger" mode (with backlight on), as detected by virtualbox usb settings. Then less than a second later it disappears (no USB device, backlight off), and repeats after a few seconds (or not). Inconsistent behavior. Earlier I got it to display various screens like ;611, and setings/device info. It rebooted on power adapter and got to 30% progress, but stalled when plugged into computer.

Different behavior depending on USB connection. The log provided by the OP looks like it reboots with no warning or error message. Serial port time, I think...

And when it did allow some settings menu access, plugging in USB cable did immediate reboot. But then just letting it sit awhile on the charger reboots eventually too...

When you peel off the cover -
Look for things like a poor solder job on the Hall Effect sensor.

We had a case of a 'loose' Hall Effect sensor fairly recently.
Which resulted in some very strange behavior.

= = = =

Sorry, I just remember that you replied to that problem with an example of keeping the hot air off of nearby parts with metal foil.
Ah, well, I'll leave this post here anyway.

[geekmaster]

Unplugging and replugging USB cable from PC seems to have repeatable behavior. Cable out, immediate amber LED off. Cable in, ~200msec delay, LED on, USB Charger detected, ~500msec delay, backlight on, ~600 msec delay, USB not detected, 600msec delay, backlight off, ~400msec delay, LED off, 500msec to 2sec delay, repeat about 4 times, then stall with LED on... It acts like software trying to find or do something that fails, but I need a serial port connection to see what what this "USB Charger" mode cycling loop is all about...

[geekmaster]

Originally Posted by knc1

When you peel off the cover -
Look for things like a poor solder job on the Hall Effect sensor.

We had a case of a 'loose' Hall Effect sensor fairly recently.
Which resulted in some very strange behavior.

= = = =

Sorry, I just remember that you replied to that problem with an example of keeping the hot air off of nearby parts with metal foil.
Ah, well, I'll leave this post here anyway.

Reminders are helpful anyway, if only to remind me of something that *I* said and then completely forgot (and perhaps cannot be convinced that I ever said it). Senior moments are becoming unwanted companions. I wish I was young again, but with my lifetime of knowledge and experience completely intact (including the memories that may no longer be accessible)...

Originally Posted by Study Fuels Hope for Memory Recovery Among Alzheimer’s Patients

Alzheimer’s patients may be able to recover lost memories, according to a new study. ... Using a technique called optogenetics, the researchers were able to coax those memories back. The researchers say optogenetics is still not approved for use on humans. The important point is, this a proof of concept. That is, even if a memory seems to be gone, it is still there. It’s a matter of how to retrieve it. ... However, using flashes of blue light to stimulate the brain’s hippocampus region, the mice with Alzheimer’s appeared to remember ... this study builds on previous research that has shown that Alzheimer’s destroys synapses, but not necessarily memories. As long as the neurons are still alive, the memory will still be there, which means you may be able to recover some of the lost memories ...

Yeah, I will look for a loose sensor...

[geekmaster]

I just did a ;dm search command, and a bunch of "system logs" documents showed up in my documents. Trying to view one loaded an apparently empty document (full screen all white except for small "100%" at the bottom). No menu, no drag down menu. After half a minute it rebooted, and only a "Set Up Your Kindle" document now... I wonder where those logs in my documents folder went...

[geekmaster]

Hmm, I just connected USB to computer again while PW3 desktop working. It popped into an out of "USB Charger" mode detected on PC, touchscreen not responding, reboot half a minute later. I think I see a pattern here -- perhaps it is reformatting /mnt/us (and copying the "welcome" document there). That may indicate data corruption on the userstore partition (or a glitch from bad firmware or bad rootfs), or a power problem that affects flash or SD-RAM reliability... Or a bad connection somewhere (like that hall-effect sensor -- but should that corrupt userstore?)... That could also be why it switches to "Charger" mode (which is "0MB flash drive" mode on earlier kindles) when it tries to switch to USBMS mode.

EDIT: It is still in airplane mode though, even after losing the system log documents, so apparently /var/local is NOT getting reformatted... I just deleted "Set Up Your Kindle" -- to see if it comes back after reformatting (if that is indeed what is happening). [Nope, that is not it. After moving USB from PC to power supply, it reboots again. Empty documents folder... Still, it seems intuitively related to loading the mass storage kernel module...

EDIT2: That "Lab126, Inc. USB Charger" mode is USB VID/PID 1949:DEAD, which probably means "dead battery" (the "charger" mode that virtualbox calls it). Less scary than a dead device...

[geekmaster]

I just did a factory reset from the settings menu. Usually it reboots while in settings, so I was quick.

Woohoo! My grayscales are back. A faint "kindle" just showed up on the kindle tree screen, then a redraw with a darker gray "kindle", then a "choose your language" screen. If eink got fixed, perhaps other stuff too?

[geekmaster]

It still reboots... And it wants to FORCE me to register before I can get to settings... All I can do is register, or read one of two books (Set Up Your Kindle, and Kindle Paperwhite User's Guide -- a new book)... No menu button or home button. And now the screen locked up -- perhaps another reboot soon... ;-(

At least the corrupt eink waveform file got fixed, now to stop that pesky boot loop...

[geekmaster]

I took it apart. I did not find board layout or teardown pics in master index, or google. :O

I see that this PW3 is well labelled on the PCB silkscreen. It has pads to install button switches, labelled "USB BOOT", "ON/OFF", and "RESET", and a set of pads labelled "SERIAL DEBUG" (which have had wires soldered to them in the past).

One of the testpoints is labelled "JTAG", but JTAG needs more than one pin, so some of those other testpoints scattered around the board must also be JTAG, or it may re-use pads for other functions...

Anyway, the "USB BOOT" switch looks a lot like the "magic key" we have been searching for, so we can probably update kubrick to support this device as well. Even easier now that amazon gives us full firmware images in the update files.

I will take photos and upload them to a new PW3 teardown thread, but I have outdoor chores to do first. The joys of home ownership, eh?

EDIT: I am thankful at this point that I have a very powerful magnet (harvested from a hard drive) mounted on a handle. The PW3 screw on the floor jumped several inches up to the magnet, allowing for fairly large sweeps to find it. This tool has not been used to swap hard drive head stacks in quite some time, so it is good to find a new use for it...

[geekmaster]

I tried various combinations of power, battery removal, and whatnot while jumpering across the "USB BOOT" switch contacts. No luck -- it behaves as before. Online docs say to connect USB to imx_usbdownloader on a linux PC, then apply power while pressing the USB BOOT switch, but I have not had success. No 15a2 VID I am looking for (only 1949:dead from lab126, or nothing). I wonder if those ON/OFF pads disconnect power, which may be easier than futzing with the battery AND USB cable (which also may supply power) while holding a jumper across "USB BOOT". Better still would be to find and install some push buttons. I have a bag full of dozens of those tiny push buttons I got off ebay, if only I can find them...