Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 11-21-2019, 10:13 AM   #1
Benjamin Li
Junior Member
Benjamin Li began at the beginning.
 
Posts: 5
Karma: 10
Join Date: Nov 2019
Location: China
Device: Kindle Paperwhite 2
Can't get into diags menu when doing serial jailbreaking

Hi friends,

I had a kpw2 whose touch screen was normal and I would like to do serial jailbreaking referring Serial Jailbreaking your fw >= 5.6.x Kindle for Dummies.

Unforunately the device's touch screen was suddenly unresponsive, and I couldn't locate the cause. I replaced a mother board and the touchscreen became normal, and I continue serial jailbreaking.

But I encounter a new issue that the device can't get into diags menu.After I
excute bootm 0xE41000 the device doesn't get into diags menu. The screen turns blank and is finally stuck on the scene of the tree and the child.And the logs shows the errror as below:

IP-Config: no devices to configure
kinit: Unable to mount root fs on device dev(179,2)
kinit: init not found!

I have read Kindle PW after I. Initialize Partition Table (fdisk) and format FAT whose situation could be similiar to mine. But I am also in a state of confusion.

Can anyone help me or give me some advice? Thanks a lot.

Below are my device's situations:
FW:5.12.1
Registered(Y/N):Y

Here is the complete logs:
Code:
[    0.000000]   Normal zone: 448 pages used for memmap
[    0.000000]   Normal zone: 56896 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: rootwait log_pos_goal=0x8fffc000 console=ttymxc0,115200 root=/dev/mmcblk0p2 ro ip=off debug video=mxcepdcfb:E60,bpp=8,x_mem=3M
[    0.000000] Prink buffer will be relocated to physical address: 8fff2000
[    0.000000] log_buf_len: 32768
[    0.000000] early log buf free: 31293(95%)
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 254652k/254652k available, 7492k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xfde00000 - 0xffe00000   (  32 MB)
[    0.000000]     vmalloc : 0xd0800000 - 0xf2000000   ( 536 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .init : 0xc0008000 - 0xc010b000   (1036 kB)
[    0.000000]       .text : 0xc010b000 - 0xc04aa000   (3708 kB)
[    0.000000]       .data : 0xc04aa000 - 0xc04dd7c0   ( 206 kB)
[    0.000000]        .bss : 0xc04dd7e4 - 0xc0504540   ( 156 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:624
[    0.000000] MXC GPIO hardware
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] arm_max_freq=1GHz
[    0.000000] MXC_Early serial console at MMIO 0x2020000 (options '115200')
[    0.000000] bootconsole [ttymxc0] enabled
[    0.000000] Console: colour dummy device 80x30
[    0.263047] Calibrating delay loop... 1987.37 BogoMIPS (lpj=9936896)
[    0.321368] pid_max: default: 32768 minimum: 301
[    0.326248] Mount-cache hash table entries: 512
[    0.331161] CPU: Testing write buffer coherency: ok
[    0.336187] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.351121] print_constraints: dummy: 
[    0.355070] NET: Registered protocol family 16
[    0.363310] print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal 
[    0.370888] print_constraints: vddcore: 725 <--> 1300 mV at 1475 mV fast normal 
[    0.378585] print_constraints: vddsoc: 725 <--> 1300 mV at 1475 mV fast normal 
[    0.386252] print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal 
[    0.393984] print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal 
[    0.401660] print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal 
[    0.410557] LAB126 Board id - 02722011341508PI
[    0.419101] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.425943] hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.
[    0.433277] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.439149] L310 cache controller enabled
[    0.443172] l2x0: 16 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x02030000, Cache size: 262144 B
[    0.459452] bio: create slab <bio-0> at 0
[    0.467087] max77696> regulator init
[    0.471559] spi_imx imx6q-ecspi.0: probed
[    0.476149] usbcore: registered new interface driver usbfs
[    0.481759] usbcore: registered new interface driver hub
[    0.487265] usbcore: registered new device driver usb
[    0.494401] Reboot Reason - Standard Reporting
[    0.498876] kernel: I max77696-irq:evtrcrd: evt=SFT_PRSTRT: Software Partial Restart
[    0.506639] Reboot Reason - Metric Framework Reporting
[    0.511798] kernel: kernel_metric_generic,counter,event_recorder,ercflags,SFT_PRSTRT,1,
[    0.519821] Reboot Reason - Legacy Metric Reporting
[    0.524713] 
[    0.527807] MAX77696 TOPSYS 1.0.0 Installed
[    0.534637] max77696-gpio max77696-gpio.0: gpio#0 -- -- func-0 in 
[    0.542154] max77696-gpio max77696-gpio.0: gpio#1 -- -- func--1 in 
[    0.549895] max77696-gpio max77696-gpio.0: gpio#3 -- -- func-0 in 
[    0.557947] MAX77696 GPIO Driver 1.0.0 Installed
[    0.563631] buck mode: 4
[    0.566944] buck mode: 4
[    0.570418] print_constraints: max77696_buck1: 900 <--> 1300 mV at 1250 mV fast normal idle standby
[    0.580024] buck mode: 4
[    0.583499] print_constraints: max77696_buck1dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby
[    0.593305] buck mode: 4
[    0.596572] buck mode: 4
[    0.600042] print_constraints: max77696_buck2: 900 <--> 1300 mV at 1200 mV fast normal idle standby
[    0.609646] buck mode: 4
[    0.613123] print_constraints: max77696_buck2dvs: 600 <--> 1300 mV at 900 mV fast normal idle standby
[    0.622908] print_constraints: max77696_buck3: 600 <--> 3387 mV at 1300 mV fast normal idle standby
[    0.632691] buck mode: 4
[    0.635961] buck mode: 4
[    0.639227] print_constraints: max77696_buck4: 1200 mV fast normal idle standby
[    0.647076] buck mode: 4
[    0.650551] print_constraints: max77696_buck5: 600 <--> 3387 mV at 1800 mV fast normal idle standby
[    0.660169] buck mode: 4
[    0.663646] print_constraints: max77696_buck6: 600 <--> 3387 mV at 3200 mV fast normal idle standby
[    0.672755] MAX77696 Buck Regulators Driver 1.0.1 Installed
[    0.679118] print_constraints: max77696_ldo1: 800 <--> 3950 mV at 3300 mV normal idle standby
[    0.688249] print_constraints: max77696_ldo2: 800 <--> 3950 mV at 3000 mV normal idle standby
[    0.697329] print_constraints: max77696_ldo3: 800 <--> 3950 mV at 2500 mV normal idle standby
[    0.706443] print_constraints: max77696_ldo4: 800 <--> 2375 mV at 1800 mV normal idle standby
[    0.715510] print_constraints: max77696_ldo5: 800 <--> 2375 mV at 1800 mV normal idle standby
[    0.724628] print_constraints: max77696_ldo6: 800 <--> 3950 mV at 3200 mV normal idle standby
[    0.733711] print_constraints: max77696_ldo7: 800 <--> 3950 mV at 3200 mV normal idle standby
[    0.742824] print_constraints: max77696_ldo8: 800 <--> 2375 mV at 1100 mV normal idle standby
[    0.751892] print_constraints: max77696_ldo9: 800 <--> 2375 mV at 1100 mV normal idle standby
[    0.761025] print_constraints: max77696_ldo10: 2400 <--> 5550 mV at 5200 mV normal idle standby
[    0.770522] MAX77696 Linear Regulators Driver 1.0.2 Installed
[    0.776877] print_constraints: max77696_lsw1: 
[    0.781690] print_constraints: max77696_lsw2: 
[    0.786444] print_constraints: max77696_lsw3: 
[    0.791178] print_constraints: max77696_lsw4: 
[    0.795686] MAX77696 Load Switches Driver 1.0.0 Installed
[    0.802305] print_constraints: max77696-display: 
[    0.807777] print_constraints: max77696-vcom: 
[    0.812549] print_constraints: max77696-vee: 
[    0.817275] print_constraints: max77696-vneg: 
[    0.822054] print_constraints: max77696-vpos: 
[    0.826808] print_constraints: max77696-vddh: 
[    0.832285] 
[    0.832288] EPD vreg probe complete!
[    0.837934] print_constraints: max77696_vddq: 240 <--> 984 mV at 600 mV 
[    0.844713] MAX77696 LPDDR2 Termination Supply Driver 1.0.1 Installed
[    0.852448] MAX77696 I2C Driver 1.0.0 Installed
[    0.859522] i2c-core: driver [max17135] using legacy suspend method
[    0.865810] i2c-core: driver [max17135] using legacy resume method
[    0.872054] Switching to clocksource mxc_timer1
[    0.887125] NET: Registered protocol family 2
[    0.891583] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.898682] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.905855] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.912389] TCP: Hash tables configured (established 8192 bind 8192)
[    0.918765] TCP reno registered
[    0.921918] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.927782] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.934401] NET: Registered protocol family 1
[    0.939123] RPC: Registered named UNIX socket transport module.
[    0.945061] RPC: Registered udp transport module.
[    0.949798] RPC: Registered tcp transport module.
[    0.954514] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.965196] etb: probe of etb failed with error -2
[    0.970245] etm: probe of etm.0 failed with error -2
[    0.975481] Static Power Management for Freescale i.MX6
[    0.980745] wait mode is enabled for i.MX6
[    0.985023] cpaddr = d0820000 suspend_iram_base=d081c000
[    0.990413] PM driver module loaded
[    0.994171] IMX usb wakeup probe
[    0.997443] the wakeup pdata is 0xce1387c0
[    1.001887] IMX usb wakeup probe
[    1.005135] the wakeup pdata is 0xce1388c0
[    1.009442] cpu regulator mode:ldo_bypass
[    1.013665] _regulator_get: get() with no identifier
[    1.018658] mx6_cpu_regulator_init: failed to get pu regulator
[    1.024702] i.MXC CPU frequency driver
[    1.041580] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.048624] msgmni has been set to 497
[    1.052739] io scheduler noop registered
[    1.056777] io scheduler cfq registered (default)
[    1.061987] MAX77696 Backlight Driver 1.0.0 Installed
[    1.067835] imx-sdma imx-sdma: loaded firmware 1.1
[    1.077211] imx-sdma imx-sdma: initialized
[    1.251468] Serial: IMX driver
[    1.383612] console [ttymxc0] enabled, bootconsole disabled
[    1.383612] console [ttymxc0] enabled, bootconsole disabled
[    1.399131] loop: module loaded
[    1.402339] MAX77696 32kHz Oscillator Driver 1.0.0 Installed
[    1.408659] input: max77696-onkey as /devices/platform/imx-i2c.0/i2c-0/0-003c/max77696-onkey.0/input/input0
[    1.421857] MAX77696 ONKEY Driver 1.0.0 Installed
[    1.448000] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.0 as rtc0
[    1.467961] max77696-rtc max77696-rtc.0: rtc core: registered max77696-rtc.1 as rtc1
[    1.497271] MAX77696 RTC Driver 1.0.2 Installed
[    1.502681] snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc2
[    1.509415] i2c /dev entries driver
[    1.517270] max77696-battery max77696-battery.0: Voltage alert     3400mV ... 4260mV
[    1.525420] max77696-battery max77696-battery.0: SOC alert         (disabled)
[    1.533462] MAX77696 Fuel Gauge Driver 1.0.0 Installed
[    1.540336] MAX77696 USB Interface Circuit Driver 1.0.0 Installed
[    1.548144] max77696-adc max77696-adc.0: ADC average rate: 32 sample(s)
[    1.554765] max77696-adc max77696-adc.0: ADC delay: 0 nsec
[    1.560268] max77696-adc max77696-adc.0: ADC cur src: 50 uA
[    1.565846] MAX77696 ADC Driver 1.0.1 Installed
[    1.571060] imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
[    1.579480] sdhci: Secure Digital Host Controller Interface driver
[    1.585666] sdhci: Copyright(c) Pierre Ossman
[    1.590149] mmc0: no vmmc regulator found
[    1.595468] mmc0: SDHCI controller on platform [sdhci-esdhc-imx.1] using DMA
[    1.603606] mmc1: no vmmc regulator found
[    1.610010] mmc1: SDHCI controller on platform [sdhci-esdhc-imx.2] using DMA
[    1.617772] Registered led device: max77696-leds.0
[    1.622571] MAX77696 LED Driver #0 1.0.0 Installed
[    1.631659] Registered led device: max77696-leds.1
[    1.636458] MAX77696 LED Driver #1 1.0.0 Installed
[    1.641787] nf_conntrack version 0.5.0 (3978 buckets, 15912 max)
[    1.650506] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.655879] TCP cubic registered
[    1.659137] NET: Registered protocol family 17
[    1.663597] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    1.671402] LPDDR2 MfgId: 0x1 [Samsung]
[    1.675543] Bus freq driver module loaded
[    1.681592] Bus freq driver Enabled
[    1.686075] mxc_dvfs_core_probe
[    1.693665] DVFS driver module loaded
[    1.716791] regulator_init_complete: max77696_ldo10: incomplete constraints, leaving on
[    1.732036] regulator_init_complete: max77696_ldo7: incomplete constraints, leaving on
[    1.749393] regulator_init_complete: max77696_ldo6: incomplete constraints, leaving on
[    1.764602] regulator_init_complete: max77696_buck6: incomplete constraints, leaving on
[    1.772830] regulator_init_complete: max77696_buck5: incomplete constraints, leaving on
[    1.781544] regulator_init_complete: max77696_buck2dvs: incomplete constraints, leaving on
[    1.790248] regulator_init_complete: max77696_buck1dvs: incomplete constraints, leaving on
[    1.799474] emmc: I def:mmcpartinfo:vendor=sandisk, host=mmc0:
[    1.817290] max77696-rtc max77696-rtc.0: setting system clock to 2019-11-21 13:09:01 UTC (1574341741)
[    1.846805] mmc0: new high speed DDR MMC card at address 0001
[    1.852956] mmcblk0: mmc0:0001 SEM04G 3.68 GiB 
[    1.857705] mmcblk0boot0: mmc0:0001 SEM04G partition 1 2.00 MiB
[    1.863760] mmcblk0boot1: mmc0:0001 SEM04G partition 2 2.00 MiB
[    1.870728]  mmcblk0: p1 p2 p3 p4
[    1.876943]  mmcblk0boot1: unknown partition table
[    1.883901]  mmcblk0boot0: unknown partition table
[    1.897685] MAX77696 Main Charger Driver 1.0.0 Installed
[    1.906202] MAX77696 Energy Harvester Driver 1.0.0 Installed
[    1.916849] Freeing init memory: 1036K
3.0.35-lab126 #1 Tue Sep 3 03:12:16 PDT 2013 armv7l
[    1.926120] INFO:Loaded module /lib/modules/mxc_epdc_eink.ko  (10304 bytes)
[    2.386630] add wake up source irq 104
[    3.526652] KERNEL: I pmic:fg battery id check::wario_battery_valid=1
[    5.342222] INFO:Loaded module /lib/modules/mxc_epdc_fb.ko  (83340 bytes)
[    5.736488] INFO:eink initialized... (786432 bytes)
Press [ENTER] for recovery menu...       0 /[    6.749142] INFO:!!! Checking MBR /dev/mmcblk0 !!!!  
[    6.759113] INFO:partition 2, start sector is 782336
[    6.764161] INFO:partition 3, start sector is 913408
[    6.769243] INFO:partition 4, start sector is 1044480
[    6.774362] INFO:maximizing partition 6688768 sectors
[    6.779474] INFO:*** Partition table verified for /dev/mmcblk0 ***
/dev/mmcblk0p4:[    6.791609] INFO:Setup loop device /dev/loop0 for /dev/mmcblk0p4 + 8192

CHS=4/16/104512 size=3424649216 bytes
flag type      first    [    6.802268] INFO:Checking for updates... (auto-pilot mode)
   last  lba first   lba size
Pa[    6.810454] INFO:No update*.bin found; no update needed.
rtition p1:
0x00 0x0b         16 <large>            16    6688752
    CHS: 0/1/1 - <large>
Partition p2:
Partition p3:
Parti[    6.827034] INFO:no updates found.
tion p4:
BOOTING DEFAULT.
IP-Config: no devices to configure
kinit: Unable to mount root fs on device dev(179,2)
kinit: init not found!
Thank you again sincerely.
Benjamin Li is offline   Reply With Quote
Old 11-21-2019, 03:57 PM   #2
knc1
99.44/100% On Holiday
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,062
Karma: 18200595
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Benjamin Li View Post
. . . .
FW: 5.12.1

Here is the complete logs:
That "complete log" is from the kernel's start-up.
Show us the Kindle's power-on start up please.

You do that by using the terminal emulator that you have attached to the serial port to capture to a file, then re-boot the Kindle, save the capture file, compress it (zip is ok), and attach to your next post.
knc1 is offline   Reply With Quote
Old 11-22-2019, 02:33 AM   #3
Benjamin Li
Junior Member
Benjamin Li began at the beginning.
 
Posts: 5
Karma: 10
Join Date: Nov 2019
Location: China
Device: Kindle Paperwhite 2
Smile

Quote:
Originally Posted by knc1 View Post
That "complete log" is from the kernel's start-up.
Show us the Kindle's power-on start up please.

You do that by using the terminal emulator that you have attached to the serial port to capture to a file, then re-boot the Kindle, save the capture file, compress it (zip is ok), and attach to your next post.
Thank knc1 for your quick response. I have rebooted the device from the homepage of the device, and wait the device to return to the homepage again. The attachment is the logs. Thanks
Attached Files
File Type: txt New logs after reboot.txt (14.5 KB, 15 views)
Benjamin Li is offline   Reply With Quote
Old 11-22-2019, 07:27 AM   #4
Jacervi
Junior Member
Jacervi began at the beginning.
 
Posts: 8
Karma: 10
Join Date: Nov 2019
Device: Kindle keyboard, Kindle pw3
Quote:
Originally Posted by Benjamin Li View Post
Thank knc1 for your quick response. I have rebooted the device from the homepage of the device, and wait the device to return to the homepage again. The attachment is the logs. Thanks
Hi, I have had similar problem and by now I can do the the procedures that follow in serial jailbreaking.
Firs I have got data between Putty and PW3.The problem was that the blue wire that indicates the procedure is NOT necessary. Without this cable communication is fluid and the touch screen began to response.
Second, to get the uboot command line I press the ket Return immediatly just when the system start. Then I can see the command line.
Finaly I continue with the procedure press options in the kindle touch screen.

Good luck.
Jacervi is offline   Reply With Quote
Old 11-22-2019, 08:37 AM   #5
Benjamin Li
Junior Member
Benjamin Li began at the beginning.
 
Posts: 5
Karma: 10
Join Date: Nov 2019
Location: China
Device: Kindle Paperwhite 2
Quote:
Originally Posted by Jacervi View Post
Hi, I have had similar problem and by now I can do the the procedures that follow in serial jailbreaking.
Firs I have got data between Putty and PW3.The problem was that the blue wire that indicates the procedure is NOT necessary. Without this cable communication is fluid and the touch screen began to response.
Second, to get the uboot command line I press the ket Return immediatly just when the system start. Then I can see the command line.
Finaly I continue with the procedure press options in the kindle touch screen.

Good luck.
Thanks for your kind advice, but I use a different usb to serial converter board and I don't need to use the blue wire. I also can arrive uboot command line normally.

Hope anyone else can give me more advice.
Benjamin Li is offline   Reply With Quote
Old 11-22-2019, 01:08 PM   #6
knc1
99.44/100% On Holiday
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,062
Karma: 18200595
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Benjamin Li View Post
Thanks for your kind advice, but I use a different usb to serial converter board and I don't need to use the blue wire. I also can arrive uboot command line normally.

Hope anyone else can give me more advice.
Which means it can not find anything valid to boot too and gives up with a command line entry only.
knc1 is offline   Reply With Quote
Old 11-22-2019, 03:01 PM   #7
Jacervi
Junior Member
Jacervi began at the beginning.
 
Posts: 8
Karma: 10
Join Date: Nov 2019
Device: Kindle keyboard, Kindle pw3
Quote:
Originally Posted by knc1 View Post
Which means it can not find anything valid to boot too and gives up with a command line entry only.
I can't see in the log the uboot line no either bootm 0xE41000 command.
Jacervi is offline   Reply With Quote
Old 11-22-2019, 08:42 PM   #8
knc1
99.44/100% On Holiday
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,062
Karma: 18200595
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by Jacervi View Post
I can't see in the log the uboot line no either bootm 0xE41000 command.
If u-boot can not find a kernel image to start ...
If you can not find a kernel image to start ...
Then there is no kernel image available (as I and u-boot both described above).
So write a kernel image to the proper location of the device.
knc1 is offline   Reply With Quote
Old 12-01-2019, 04:16 AM   #9
Benjamin Li
Junior Member
Benjamin Li began at the beginning.
 
Posts: 5
Karma: 10
Join Date: Nov 2019
Location: China
Device: Kindle Paperwhite 2
Quote:
Originally Posted by knc1 View Post
If u-boot can not find a kernel image to start ...
If you can not find a kernel image to start ...
Then there is no kernel image available (as I and u-boot both described above).
So write a kernel image to the proper location of the device.
Thanks for your guide.
I had changed another motherboard and I could jailbreak it successfully.
Benjamin Li is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Tools Serial Jailbreaking your fw >= 5.6.x Kindle for Dummies grant2 Kindle Developer's Corner 478 12-04-2019 06:07 AM
PW3 Serial jailbreaking help Gyiyg Kindle Developer's Corner 2 06-17-2019 08:05 AM
PW3 PW3,fw 5.10.3 serial jailbreaking help LivingOn Kindle Developer's Corner 9 05-14-2019 07:28 AM
Jailbreaking a PW4 with G001 serial number thechordmaster Kindle Developer's Corner 31 03-19-2019 01:31 AM
Serial Jailbreaking FW >= 5.6.1.1 knc1 Kindle Developer's Corner 6 08-14-2017 09:38 AM


All times are GMT -4. The time now is 06:16 PM.


MobileRead.com is a privately owned, operated and funded community.