Update Paperwhite to 5.3.0 WITHOUT locking yourself out! - Page 6

knc1 · 11-10-2012, 10:37 AM

Quote:

Originally Posted by NiLuJe

@all: Since he mentioned being able to boot into diags via serial, I'm assuming the jailbreak actually installed from diags, which makes sense

.

If the jailbreak is being put on mmcblk0p3, then it is being put into both main and diags.
Since mmcblk0p3 is common to both systems and mounted at the same place in the file system tree.

(Which, I thought from following the conversation, is what was intended.)

h1uke · 11-10-2012, 10:38 AM

@knc1: I'll be able to provide requested information in 4-5 hours.

knc1 · 11-10-2012, 10:40 AM

Quote:

Originally Posted by h1uke

@knc1: I'll be able to provide requested information in 4-5 hours.

Thanks!

I have to ask these "more info" questions because I don't own the machine but I assure you, they are not idle requests.

h1uke · 11-10-2012, 10:42 AM

Quote:

Originally Posted by NiLuJe

@all: Since he mentioned being able to boot into diags via serial, I'm assuming the jailbreak actually installed from diags, which makes sense

.

the 'diag' mode can be entered from u-boot prompt by running the bootm_diags
environment variable which just boots from a non-standard address.
I remember that I tried the diag mode when data.tar.gz from v1_6 was sitting
in a root folder. Can this be the cause?

NiLuJe · 11-10-2012, 10:54 AM

@h1uke: Yep, that's what I meant. It's at its core the same payload as the K4 JB, so it still supports being run from diags.

I don't remember exactly which file diags expect on the PW (.tar.gz or .stgz), but if the right one was there, yep, that would do it

.

And to answer knc1: Yeah, the bridge possibly works from diags, if somethings runs it, which I'm not actually sure of, but, theoretically, it would work

.

knc1 · 11-10-2012, 10:58 AM

Quote:

Originally Posted by eureka

Oh, BTW:

Code:

$ cat 530/etc/shadow 
root:!:10933:0:99999:7:::
daemon:*:10933:0:99999:7:::
bin:*:10933:0:99999:7:::
sys:*:10933:0:99999:7:::
sync:*:10933:0:99999:7:::
operator:*:10933:0:99999:7:::
sshd:*:10933:0:99999:7:::
messagebus:*:10933:0:99999:7:::
nobody:*:10933:0:99999:7:::
default:!:10933:0:99999:7:::
framework:!:14033:0:99999:7:::

Yep, root can't login.

That is another pain-in-the-ass change.

The USBnet hack will have to start shipping a public key-pair so that people can ssh into the machine without a password.

knc1 · 11-10-2012, 11:02 AM

Quote:

Originally Posted by NiLuJe

And to answer knc1: Yeah, the bridge possibly works from diags, if somethings runs it, which I'm not actually sure of, but, theoretically, it would work

.

There are other places where "our" data and applications could be stored, but then we would be into an "arms race" with Amazon.

Our only advantage there, is that it costs Amazon a whole lot more time and money to undo what we have done.

NiLuJe · 11-10-2012, 11:03 AM

@knc1: It already bypasses this, when connecting over USB only (ENABLE_WIFI=false, the default settings): telnet doesn't check auth at all, and dropbear doesn't check the password, just hit enter and you're in.

knc1 · 11-10-2012, 11:28 AM

Quote:

Originally Posted by NiLuJe

@knc1: It already bypasses this, when connecting over USB only (ENABLE_WIFI=false, the default settings): telnet doesn't check auth at all, and dropbear doesn't check the password, just hit enter and you're in.

That should do it.

Although my personal preference is to replace the updater with a sym-link to /bin/true and go "full manual" with these updates.

I realize that isn't much help to the general population of Kindle owners.

NiLuJe · 11-10-2012, 11:38 AM

@knc1: On the other hand, it does make OpenSSH grumpy...

Code:

121110:163645 sshd[1962]: User root not allowed because account is locked
121110:163645 sshd[1962]: input_userauth_request: invalid user root [preauth]
121110:163648 sshd[1962]: Failed none for invalid user root from 192.168.2.1 port 47877 ssh2
121110:163651 sshd[1962]: Failed password for invalid user root from 192.168.2.1 port 47877 ssh2
121110:163655 sshd[1962]: error: Could not get shadow information for NOUSER
121110:163655 sshd[1962]: Failed password for invalid user root from 192.168.2.1 port 47877 ssh2
121110:163655 sshd[1962]: Connection closed by 192.168.2.1 [preauth]

Wee, more patching to do!

EDIT: Fixed in USBNetwork v0.5.N

.

twobob · 11-10-2012, 02:21 PM

Quote:

Originally Posted by NiLuJe

@knc1: On the other hand, it does make OpenSSH grumpy...

Code:

121110:163645 sshd[1962]: User root not allowed because account is locked
121110:163645 sshd[1962]: input_userauth_request: invalid user root [preauth]
121110:163648 sshd[1962]: Failed none for invalid user root from 192.168.2.1 port 47877 ssh2
121110:163651 sshd[1962]: Failed password for invalid user root from 192.168.2.1 port 47877 ssh2
121110:163655 sshd[1962]: error: Could not get shadow information for NOUSER
121110:163655 sshd[1962]: Failed password for invalid user root from 192.168.2.1 port 47877 ssh2
121110:163655 sshd[1962]: Connection closed by 192.168.2.1 [preauth]

Wee, more patching to do!

EDIT: Fixed in USBNetwork v0.5.N

.

sublime

great work so far people!

h1uke · 11-10-2012, 05:07 PM

Quote:

Originally Posted by knc1

Please capture a listing of the u-boot commands and post the full listing.

Sorry, cannot provide information on JB_1.6 and JB_1.7 I used: I'm away and
from actual files don't have remote access to that location.

Below are

u-boot startup:

Spoiler:

u-boot environment and supported commands:

Spoiler:

normal boot:

Spoiler:

Code:

uboot > boot
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608640 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
MX50 LPDDR2 MfgID: 0x1 [Samsung]
2.6.31-rt11-lab126 #1 Tue Oct 30 18:48:14 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (39836 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_updat
e_mode=1 (51416 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!

INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2863104 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/44736 size=1465909248 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    2863088
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
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/mmcblk0p1"
  argv[6]: "quiet"
  argv[7]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  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/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 system:emiting_event:mounted_dev:
info system:emiting_event:mounted_tmpfs:
info milestone:6.35:sy50:
init.exe: recevent pre-start process (495) terminated with status 1
info system:start:time=6400:
info hardware:no_wan::WiFi only device. No WAN found
info system:config:platform=yoshime3,board=celeste,rev=21,proto=N,wifi=Y,wan=N:
info milestone:6.63:sy51:
info milestone:7.23:sy99:
info system:done:time=7260:
info system_cramfs_loopbacks:mountingcramfs:Mounting compressed directories filesyst
em 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:7.89: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:8.28:fs00:
info system:emiting_event:loaded_fakekey:



Welcome to Kindle!

kindle login: info system:emiting_event:mounted_varLocal:
info milestone:8.67:fs25:
info milestone:8.70:vi00:
info milestone:8.90:vi99:
info display:started:time=8910:
info system:emiting_event:display_ready:
info userstore:run:time=9180,action=start:
info battery:charged:cap=98,mV=4141,mAH=1382:
info userstore:found_shutdown_flag::Found SHUTDOWN flag file
info system:emiting_event:battery_ready:
info system:emiting_event:mounted_userstore:
info milestone:9.84:fs50:
info milestone:9.86:fs90:
info milestone:9.89:fs99:
info cyttsp:update:vendor=CANDO:
info system:emiting_event:loaded_touch:
info milestone:11.82: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 usbnet:start::usbnet is disabled
info milestone:13.24:xx00:
info X:load:time=13390:
info X:xorg.conf:Generating xorg.conf:
info X:makexconfig:Celeste Input device detection status:
info X:makexconfig:Touch device: OK:
info X:makexconfig:Accelerometer device: N/A !!:
info X:xorg.conf:xorg.conf generated:
info milestone:13.98:xx50:
info X:starting:time=14000:
info x_monitor:x_monitor starts::
info x_monitor:read_counters::REBOOTS=0, RESTART=0, REBOOT_LIMIT=1, RESTART_LIMIT=5
info monitor:writing_file:file=/var/run/upstart/x.restarts:
info x_monitor:inc_restart::RESTART=1, RESTART_LIMIT=5
info x_monitor:restart::job=x
info milestone:18.67:xx00:
info X:load:time=18680:
info X:xorg.conf:Generating xorg.conf:
info X:makexconfig:Celeste Input device detection status:
info X:makexconfig:Touch device: OK:
info X:makexconfig:Accelerometer device: N/A !!:
info X:xorg.conf:xorg.conf generated:
info milestone:18.83:xx50:
info X:starting:time=18840:
info milestone:23.07:xx99:
info X:started:time=23080:
info system:emiting_event:x_setup_ready:
info locale:read:lang=en_US.utf8,lc_all=en_US.utf8:Retrieved Language
info system:emiting_event:langpicker_ready:
info blanket_f:module already loaded:splash:
info milestone:23.96:pi00:
info milestone:23.98:fr00:
info milestone:24.43:pi99:
info milestone:24.43:fr50:
info milestone:24.46:fr51:
info framework:starting:time=24630:
info hardware:no_wan::WiFi only device. No WAN found
boot: I def:rbt:reset=user_reboot,version=177470:
info milestone:57.17:fr99:
info framework:started:time=57210,delta=32800:
info blanket_f:loading blanket module:usb:
info blanket_f:unloading blanket module:screensaver:
info blanket_f:module already unloaded:ad_screensaver:
info blanket_f:module already unloaded:ad_screensaver_active:
info blanket_f:loading blanket module:screensaver:
info blanket_f:unloading blanket module:splash:
info system:emiting_event:framework_ready:
Retrieved 171 keys for system/daemon/pmond/

dmesg -c:

Spoiler:

Code:

[root@kindle root]# dmesg -c
Linux version 2.6.31-rt11-lab126 (jenkins-official@jbuild02) (collect2: ld returned
1 exit status) #1 Tue Oct 30 18:48:14 PDT 2012
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Amazon.com MX50 YOSHIME Board
Board ID and Serial Number driver for Lab126 boards version 1.0
MX50 Board id - 00A15011241414IF
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c046c86c, node_mem_map c0496000
  DMA zone: 192 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 24384 pages, LIFO batch:3
  Normal zone: 320 pages used for memmap
  Normal zone: 40640 pages, LIFO batch:7
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Kernel command line: consoleblank=0 rootwait ro ip=off root=/dev/mmcblk0p1 quiet ein
k=fslepdc video=mxcepdcfb:E60,bpp=8,x_mem=4M mem=256M console=ttymxc0,115200
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 255012KB available (3296K code, 359K data, 1000K init, 0K highmem)
NR_IRQS:368
MXC IRQ initialized
cko2_set_rate, new divider=0
MXC_Early serial console at MMIO 0x53fbc000 (options '115200')
console [ttymxc0] enabled
Console: colour dummy device 80x30
Calibrating delay loop... 799.53 BogoMIPS (lpj=3997696)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
i.MX IRAM pool: 128 KB@0xd0840000
MX50 LPDDR2 MfgID: 0x1 [Samsung]
CPU is i.MX50 Revision 1.1
MXC GPIO hardware
Using SDMA I.API
MXC DMA API initialized
bio: create slab <bio-0> at 0
CSPI: mxc_spi-0 probed
CSPI: mxc_spi-1 probed
CSPI: mxc_spi-2 probed
MXC I2C driver
MXC I2C driver
MXC I2C driver
PMIC Light driver loading...
mc13892 Rev 2.4 FinVer a detected
Initializing regulators for mx50 yoshi.
regulator: SW1: 600 <--> 1375 mV
regulator: SW2: 900 <--> 1850 mV
regulator: SW3: 900 <--> 1850 mV
regulator: SW4: 1100 <--> 1850 mV
regulator: SWBST: 0 mV
regulator: VIOHI: 0 mV
regulator: VPLL: 1050 <--> 1800 mV
regulator: VDIG: 1200 mV
regulator: VSD: 1800 <--> 3150 mV
regulator: VUSB2: 2400 <--> 2775 mV
regulator: VVIDEO: 2775 mV
regulator: VAUDIO: 2300 <--> 3000 mV
regulator: VCAM: 2500 <--> 3000 mV fast normal
regulator: VGEN1: 3000 mV
regulator: VGEN2: 1200 <--> 3150 mV
regulator: VGEN3: 1800 mV
regulator: VUSB: 0 mV
regulator: GPO1: 0 mV
regulator: GPO2: 0 mV
regulator: GPO3: 0 mV
regulator: GPO4: 0 mV
PMIC ADC start probe
PMIC Light successfully loaded
Device spi3.0 probed
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
NET: Registered protocol family 1
LPMode driver module loaded
Static Power Management for Freescale i.MX5
PM driver module loaded
sdram autogating driver module loaded
Bus freq driver module loaded
mxc_dvfs_core_probe
DVFS driver module loaded
i.MXC CPU frequency driver
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering unionfs 2.5.10 (for 2.6.31.14)
msgmni has been set to 498
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
regulator: DISPLAY: 0 mV
regulator: GVDD: 20000 mV
regulator: GVEE: -22000 mV
regulator: VCOM: 0 <--> 2749 mV
regulator: VNEG: -15000 mV
regulator: VPOS: 15000 mV
regulator: TMST: 0 mV
papyrus 1-0068: PMIC PAPYRUS for eInk display
Amazon MX35 Yoshi Power Button Driver
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a Freescale MXC
console handover: boot [ttymxc0] -> real [ttymxc0]
mxcintuart.1: ttymxc1 at MMIO 0x53fc0000 (irq = 32) is a Freescale MXC
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale MXC
mxcintuart.3: ttymxc3 at MMIO 0x53ff0000 (irq = 13) is a Freescale MXC
loop: module loaded
mxc_rtc mxc_rtc.0: rtc core: registered mxc_rtc as rtc0
Probing mxc_rtc done
mc13892 rtc probe start
pmic_rtc pmic_rtc.1: rtc core: registered pmic_rtc as rtc1
mc13892 rtc probe succeed
i2c /dev entries driver
MXC WatchDog Driver 2.0
MXC Watchdog # 0 Timer: initial timeout 127 sec
MXC Watchdog: Started 10000 millisecond watchdog refresh
PMIC Character device: successfully loaded
pmic_battery: probe of pmic_battery.1 failed with error -1
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
mxsdhci: MXC Secure Digital Host Controller Interface driver
mxsdhci: MXC SDHCI Controller Driver.
mmc0: SDHCI detect irq 273 irq 2 INTERNAL DMA
mxsdhci: MXC SDHCI Controller Driver.
mmc1: SDHCI detect irq 0 irq 3 INTERNAL DMA
Registered led device: pmic_ledsr
Registered led device: pmic_ledsg
Registered led device: pmic_ledsb
nf_conntrack version 0.5.0 (4096 buckets, 16384 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
kernel: I perf:kernel:kernel_loaded=0.48 seconds:
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
regulator_init_complete: disabling TMST
regulator_init_complete: disabling VCOM
regulator_init_complete: disabling GPO4
regulator_init_complete: disabling GPO3
regulator_init_complete: disabling GPO2
regulator_init_complete: disabling GPO1
regulator_init_complete: disabling VGEN3
regulator_init_complete: disabling VGEN1
regulator_init_complete: disabling VCAM
regulator_init_complete: disabling VAUDIO
regulator_init_complete: disabling VVIDEO
regulator_init_complete: disabling VSD
regulator_init_complete: disabling SWBST
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 12:10:43 UTC (43843)
Freeing init memory: 1000K
mmc0: queuing CIS tuple 0x01 length 3
mmc0: queuing CIS tuple 0x1a length 5
mmc0: queuing CIS tuple 0x1b length 8
mmc0: queuing CIS tuple 0x14 length 0
mmc0: queuing CIS tuple 0x80 length 1
mmc0: queuing CIS tuple 0x81 length 1
mmc0: queuing CIS tuple 0x82 length 1
mmc0: new high speed SDIO card at address 0001
emmc: I def:mmcpartinfo:vendor=samsung, ddr=0, host=mmc1:
mmc1: new high speed MMC card at address 0001
mmcblk0: mmc1:0001 M2G1HF 1.86 GiB
 mmcblk0: p1 p2 p3 p4
mxc_epdc_fb_init_hw: 06_05_009f_3c_2b1b02_06_db_00000d20_85_12.wbf
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with writeback data mode.
ARC USB OTG/Gadget/Device Controller driver (26 Mar 2012)
kernel: I perf:usb:usb_gadget_loaded=8.27 seconds:
g_file_storage gadget: File-backed Storage Gadget, version: 7 August 2007
g_file_storage gadget: Number of LUNs=1
fsl-usb2-udc: bind to driver g_file_storage
fuse init (API version 7.12)
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mmcblk0p3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with writeback data mode.
cypress reset
cyttsp_bl_app_valid: App found; normal boot
cyttsp: I mfgcmd :cmd_cmpl::
cyttsp_set_sysinfo_mode: hst_mode:0x90, mfg_stat:0x44, mfg_cmd:0x0
cyttsp_set_sysinfo_mode:SI2:tts_ver=0x15D5 app_id=0x2054 app_ver=0x020A c_id=0x00001
1
cyttsp_set_operational_mode: hstmode:0x0 tt_mode:0x0 tt_stat:0x0
cyttsp_power_on: Power state is ACTIVE
input: cyttsp as /devices/platform/cyttsp.0/input/input0
cyttsp: I cyttsp_proc_write::command=unlock:
[root@kindle root]#

diag mode boot and most interesting menus:

Spoiler:

Code:

uboot > run bootcmd_diags
## Booting kernel from Legacy Image at 70800000 ...
   Image Name:   Linux-2.6.31-rt11-lab126
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4608576 Bytes =  4.4 MB
   Load Address: 70008000
   Entry Point:  70008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK
Starting kernel ...
2.6.31-rt11-lab126 #1 Fri Sep 7 15:17:38 PDT 2012 armv7l
INFO:Loaded module /lib/modules/eink_fb_waveform.ko  (36956 bytes)
INFO:Loaded module /lib/modules/mxc_epdc_fb.ko default_panel_hw_init=1 default_updat
e_mode=1 (51152 bytes)
INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /INFO:!!! Checking MBR /dev/mmcblk0 !!!!

INFO:partition 2, start sector is 782336
INFO:partition 3, start sector is 913408
INFO:partition 4, start sector is 1044480
INFO:maximizing partition 2863104 sectors
INFO:*** Partition table verified for /dev/mmcblk0 ***
INFO:Checking for updates... (auto-pilot mode)
/dev/mmcblk0p4:
CHS=4/16/44736 size=1465909248 bytes
flag type      first       last  lba first   lba size
Partition p1:
0x00 0x0b         16 <large>            16    2863088
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Partition p4:
INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192
INFO:No update*.bin found; no update needed.
INFO:no updates found.
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]: "eink=fslepdc"
  argv[8]: "video=mxcepdcfb:E60,bpp=8,x_mem=4M"
  argv[9]: "mem=256M"
  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 (2012-09-07 15:07:58 PDT)
starting pid 423, 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=5960:Mounting root RW for first boot
info firsttime:cursor:Linking Xorg cursor:
ln: /usr/share/fonts/X11/misc/cursor.pcf: No such file or directory
info firsttime:mount_ro:time=6000:Mounting root RO
elevator: type  not found
info system:start:time=6070:
/etc/rcS.d/S50diags: line 466: f_proto: not found
info hardware:no_wan::WiFi only device. No WAN found
info system:config:platform=yoshime3,board=celeste,rev=21,proto=N,wifi=Y,wan=N:
info system:done:time=6470:
info cyttsp:update:vendor=CANDO:
/etc/rcS.d/S50diags: line 466: iptables-restore: not found
/opt/ar6k/include/dbglog.h.save: No such file or directory
info userstore:run:time=7820,action=start:
info userstore:found_shutdown_flag::Found SHUTDOWN flag file
/etc/rcS.d/S50diags: line 13: /usr/local/sbin/dropbear: not found
mounting waveform filesystem
info display:update:Displaying splash screen:
umounting waveform filesystem
info display:started:time=8560:
/etc/upstart/battery-diags: line 91: f_proto: not found
info battery:charged:cap=97,mV=4133,mAH=1373:
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
/etc/rcS.d/S50diags: line 13: alsactl: not found
/etc/rcS.d/S50diags: line 13: audioServer: not found
FATAL: Module mxc_keyb not found.
/etc/rcS.d/S50diags: line 13: kb: not found
diags : /opt/factory/rootfs_md5_list not found.
Change list is: [173022]
Sending: mkdir -p /mnt/base-us/diagnostic_logs/
PostMode len = 6 of 16
Ignoring PostMode
GlobalHalImpl: found DeviceType: 23
found: cyttsp
HalWifi: name: /mnt/us/tools/atheros/art_rel/art/bin, artRootPath: /mnt/us/tools/ath
eros/art_rel/art/bin
        MainTest:exe
        MainTest:exeTest Set CPU to faster speed
system_diags[MainTest] 1 INFO : Start test
   CELESTE_WFO - System Diags
   ~~~~  1.9.385.173022  ~~~~
~ S ~ Device Setting
P) Touch Sensor Plate Test
O) Operator test suite
E) 511
N) Misc individual diagnostics
Y) nART factory test
U) USB device mode
D) Exit, Reboot or Disable Diags
L) Lock diags screen
X) Exit


EInkPanel:clear_display m_eink.size: [786432]
        MainTest:is_chargerConnected: charger is: disconnected
mxc_rtc: saved=0xaa18 boot=0xaaa2
boot: I def:rbt:reset=user_reboot,version=173022:
        MainTest:is_chargerConnected: charger is: disconnected



Cmd: N
        MiscIndividualDiagnostics:exe
system_diags[MiscIndividualDiagnostics] 1 INFO : Start test
   CELESTE_WFO - Misc individual diagnostics
   ~~~~  1.9.385.173022  ~~~~
~ C ~ Certification Test Mode
I) Wifi Test
G) Gas Gauge
L) LED Test
O) FrontLight test
S) HallSensor detect
V) Video Test
T) Touch Sensor Menu
F) VnI test
N) MoviNand
E) Power Test
H) Adjust battery
M) MoviNand/AdjBat/DisableDiags
U) Utilities
X) Exit

Cmd: U
        Utilities:exe
system_diags[Utilities] 1 INFO : Start test
   CELESTE_WFO - Utilities
   ~~~~  1.9.385.173022  ~~~~
~ O ~ Format user partitions
E) 511 with device info
D) WAN Desense Test
Z) Enable USBnet
M) Mount nfs
S) Stress Tests
R) Run in Test
X) Exit

Hope this helps. LMK if anything else is needed.

knc1 · 11-10-2012, 06:10 PM

OK, Thanks.
Some vital information there, but I can hold off on questions for awhile.

Ah, well, one question:
Do you have ssh (or telnet) setup over USBnet?
If so, then I may have a list of small questions for things in the kernel's dynamic part of the file system.

Observations at first glance:
* A very unusual start address for an embedded Linux kernel.
* U-boot is certainly stripped down
* Why would the init scripts be looking for our dropbear installation, unless it intended to do it harm? (which is a criminal offense in the USA).
* Others, not as trivial. Will need more study.

Special Request
Would someone run off the same outputs from 5.2.0 before up-grading please.
Note that the above requires the serial port connection.

NiLuJe · 11-10-2012, 06:12 PM

@knc1: That's been standard behavior for diags since the K4 (where, in fact, dropbear was still there on released devices for a good long while before they shipped an updated diags version).

(And on some main version, too). Check the factory md5 list, they have a *lot* of stuff in /usr/local on their dev images.

knc1 · 11-10-2012, 06:17 PM

@NiLuJe: My special request remains, that isn't the only thing I was looking for.

11-10-2012, 10:54 AM	#80
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@h1uke: Yep, that's what I meant. It's at its core the same payload as the K4 JB, so it still supports being run from diags. I don't remember exactly which file diags expect on the PW (.tar.gz or .stgz), but if the right one was there, yep, that would do it . And to answer knc1: Yeah, the bridge possibly works from diags, if somethings runs it, which I'm not actually sure of, but, theoretically, it would work . Last edited by NiLuJe; 11-10-2012 at 10:59 AM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle Paperwhite Update Version 5.3.0	JoHunt	Amazon Kindle	115	11-30-2012 04:32 PM
5.3 Update for Paperwhite -- will it interfere with the jailbreak?	sparrowlight	Kindle Developer's Corner	159	11-19-2012 09:11 AM
Paperwhite Update Coming One of These Days?	copyrite	Amazon Kindle	13	11-05-2012 02:56 PM
Paperwhite Shipping Update?	nobylspoon	Amazon Kindle	454	10-26-2012 10:56 AM

11-10-2012, 10:38 AM	#77
h1uke Zealot Posts: 121 Karma: 82565 Join Date: Aug 2010 Location: Maryland, USA Device: dxg, k3w,k4nt,kpw	@knc1: I'll be able to provide requested information in 4-5 hours.

11-10-2012, 11:03 AM	#83
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@knc1: It already bypasses this, when connecting over USB only (ENABLE_WIFI=false, the default settings): telnet doesn't check auth at all, and dropbear doesn't check the password, just hit enter and you're in.

11-10-2012, 06:10 PM	#88
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	OK, Thanks. Some vital information there, but I can hold off on questions for awhile. Ah, well, one question: Do you have ssh (or telnet) setup over USBnet? If so, then I may have a list of small questions for things in the kernel's dynamic part of the file system. Observations at first glance: * A very unusual start address for an embedded Linux kernel. * U-boot is certainly stripped down * Why would the init scripts be looking for our dropbear installation, unless it intended to do it harm? (which is a criminal offense in the USA). * Others, not as trivial. Will need more study. Special Request Would someone run off the same outputs from 5.2.0 before up-grading please. Note that the above requires the serial port connection.

11-10-2012, 06:12 PM	#89
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@knc1: That's been standard behavior for diags since the K4 (where, in fact, dropbear was still there on released devices for a good long while before they shipped an updated diags version). (And on some main version, too). Check the factory md5 list, they have a lot of stuff in /usr/local on their dev images.

11-10-2012, 06:17 PM	#90
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	@NiLuJe: My special request remains, that isn't the only thing I was looking for.

Advert

Advert