PKW stuck at boot progress bar(95%)

kenxl · 03-18-2016, 11:37 PM

My KPW stuck at boot progress bar (95%).
Reboot, no help.

Connect USB-TTL cable, can update firmware from recovery menu. I tried some versions I can found: 5.3.0, 5.4.4, 5.6.1.1. Update all successful, but still stuck at same place.

Anything I can do to save my KPW?

kenxl · 03-18-2016, 11:37 PM

here is the boot log:

Please use spoiler tags for such a long post - MODERATOR]

Spoiler:

knc1 · 03-19-2016, 12:31 AM

Quote:

Originally Posted by kenxl

My KPW stuck at boot progress bar (95%).
Reboot, no help.

Connect USB-TTL cable, can update firmware from recovery menu. I tried some versions I can found: 5.3.0, 5.4.4, 5.6.1.1. Update all successful, but still stuck at same place.

Anything I can do to save my KPW?

Which paperwhite?
Give us the first 6 characters of your serial number please.
And you can lookup our nickname for it here:
https://wiki.mobileread.com/wiki/Kindle_Serial_Numbers

What do you mean: "version I found" ??
Why don't you just download the correct (or desired) update package from Amazon?
A worked example:
https://www.mobileread.com/forums/sho...postcount=1301

On your second post -
Use the 'advanced editor' and wrap the output in code tags.
If long, like your second post, wrap with spoiler tags.
OR
Cut&Paste to a text file and make it an attachment to your post.
You will need to find the 'advanced editor' and scroll past the text entry box to the 'manage attachments' section.

Please do not turn this into a game of "20 questions" -
See this post:
https://www.mobileread.com/forums/sho...d.php?t=272087
and read the page that is linked to in that post, please.

kenxl · 03-19-2016, 01:03 AM

Quote:

Originally Posted by knc1

Which paperwhite?
Give us the first 6 characters of your serial number please.
And you can lookup our nickname for it here:
https://wiki.mobileread.com/wiki/Kindle_Serial_Numbers

What do you mean: "version I found" ??
Why don't you just download the correct (or desired) update package from Amazon?
A worked example:
https://www.mobileread.com/forums/sho...postcount=1301

On your second post -
Use the 'advanced editor' and wrap the output in code tags.
If long, like your second post, wrap with spoiler tags.
OR
Cut&Paste to a text file and make it an attachment to your post.
You will need to find the 'advanced editor' and scroll past the text entry box to the 'manage attachments' section.

Please do not turn this into a game of "20 questions" -
See this post:
https://www.mobileread.com/forums/sho...d.php?t=272087
and read the page that is linked to in that post, please.

Sorry, I am new here. Here is the first 6 characters
S/N: B02415

"version I found" mean for my KPW1, I tried some versions available now.

knc1 · 03-19-2016, 01:22 AM

Quote:

Originally Posted by kenxl

Sorry, I am new here. Here is the first 6 characters
S/N: B02415

That is a PW-1.
Since you have serial port access, you can jailbreak any version you install.
So don't use "versions I found" - -
There is no telling where or what you might have found.
Use the current firmware for the device from Amazon (5.6.1.1 - for the "5th generation" paperwhite - do not get 5.6.1.1 for any other model).

= = = = =

Please do not make me play 20 questions with you.
Give us context and details - not big text globs.

Nobody here can see over your shoulder and all of our crystal balls are off-line for seasonal maintenance.
YOU must be the one to help us solve your problem.

So start at the start -
Are you the original owner of this device?
Has it ever worked correctly?
What is the background on how it became "broke" ?
How many books and documents did it have on it then, how many now, what types?
What other things have you done to it, before and after trying to use the recovery menu?

You must be willing and able to cooperate with us in finding the answer to your problem.
If you can't do that, then take it to a local repair shop.

kenxl · 03-19-2016, 01:24 AM

This is the screen my KPW1 stucks

kenxl · 03-19-2016, 01:40 AM

Quote:

Originally Posted by knc1

That is a PW-1.
Since you have serial port access, you can jailbreak any version you install.
So don't use "versions I found" - -
There is no telling where or what you might have found.
Use the current firmware for the device from Amazon (5.6.1.1 - for the "5th generation" paperwhite - do not get 5.6.1.1 for any other model).

= = = = =

Please do not make me play 20 questions with you.
Give us context and details - not big text globs.

Nobody here can see over your shoulder and all of our crystal balls are off-line for seasonal maintenance.
YOU must be the one to help us solve your problem.

So start at the start -
Are you the original owner of this device?
Has it ever worked correctly?
What is the background on how it became "broke" ?
How many books and documents did it have on it then, how many now, what types?
What other things have you done to it, before and after trying to use the recovery menu?

You must be willing and able to cooperate with us in finding the answer to your problem.
If you can't do that, then take it to a local repair shop.

Thanks for the prompt reply.
My wife is the original owner of this PW1
Yes, it worked fine 1 week ago.
She installed a 3rd party application named "duokan" on this PW1 , which make PW1 dual bootable. The issue was caused by her switching back from "duokan" boot to original kindle boot. Then PW1 always stuck at almost the end of booting.
For number of books on kindle, I am not sure. But now there is no book on kindle. My wife said there might be about 100+ books, 3-4M for every book.
I tried these items in recovery menu:
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

I also tried "3. Load MMC0 over USB storage", but response is "unknown option"

thanks again!

knc1 · 03-19-2016, 05:57 AM

Quote:

Originally Posted by kenxl

Thanks for the prompt reply.
My wife is the original owner of this PW1
Yes, it worked fine 1 week ago.
She installed a 3rd party application named "duokan" on this PW1 , which make PW1 dual bootable. The issue was caused by her switching back from "duokan" boot to original kindle boot. Then PW1 always stuck at almost the end of booting.
For number of books on kindle, I am not sure. But now there is no book on kindle. My wife said there might be about 100+ books, 3-4M for every book.
I tried these items in recovery menu:
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

I also tried "3. Load MMC0 over USB storage", but response is "unknown option"

thanks again!

Not our project, not our problem, ask them for support on their support forum.

= = = = =

Did you notice that with every firmware you tried to install with the Recovery Menu - none of the problem changed?

Translation: You can't fix it with the Recovery Menu.

Did you notice the offset of the kernel u-boot reports as booting?
That is not the kernel being installed using the Recovery Menu and the PW-1, 5.6.1.1 Amazon firmware package.

Translation: You never boot the kernel installed from the Amazon package.

You have three choices -

Restore the Kindle from the 'other' operating system, 'diags'.
Although Doukan has been known to botch that up also, so don't be surprised if that attempt fails.
See:
https://www.mobileread.com/forums/sho...d.php?t=272132
Just use the correct, current, PW-1, 5.6.1.1, firmware posted by Amazon.

OR

Restore the Kindle by assuming only u-boot is working and everything else is trashed (same as if it had been erased).
See:
https://www.mobileread.com/forums/sho...d.php?t=269099
Once again:
Use the correct, current, PW-1, 5.6.1.1, firmware posted by Amazon.
There are many log files attached to the posts of that thread, read them and compare them with the log files you capture as you follow the directions, step-by-step.

You never mentioned what type of computer you have to work with nor what OS it runs.
So I must assume you are certain you can read the directions for whatever PC/OS they are written for and translate them to the PC/OS you are using.

OR

Take it to a local repair shop.

When, if, you get it fixed, install KOreader.
That you can get supported at Mobileread.

If you want support on Doukan, use their support forum:
http://www.miui.com/forum-490-1.html
As you read through their forum, notice just how many things they are using are taken from this site and used without credit to the author or this site they took it from.
That should give you a hint why we don't provide technical support for Doukan here.

Translation:
If the Duokan Project wants to use our stuff without credit where credit is due, they can also use it without our support.

The idea that a free support site, staffed by volunteers, should be expected to support a commercial, for profit, software project is just so wrong that I can't think of words to describe it in public.

kenxl · 03-19-2016, 09:25 AM

Thanks knc1 for all the information you provided. They are very helpful to me.

I am very sorry for Duokan's stealing stuff from here. Since I found many useful information by google, I came here for some help.

Thank you again!

knc1 · 03-19-2016, 09:33 AM

Quote:

Originally Posted by kenxl

Thanks knc1 for all the information you provided. They are very helpful to me.

I am very sorry for Duokan's stealing stuff from here. Since I found many useful information by google, I came here for some help.

Thank you again!

One of those threads should enable you to recover your Kindle.

There is a third thread here that you might need - which I didn't look up (it is fairly recent).
It is about adding a larger eMMC flash chip but contains information on rebuilding u-boot.
If Doukan has altered the Amazon u-boot, you might need that information.

Otherwise, either trade in the Kindle or trade in the wife.

kenxl · 03-20-2016, 02:21 AM

after much work, finally I got my PW1 back to life!

I follow the steps from:
https://gist.github.com/TobiasWooldr...ca75190b9a473f

but after reboot, it still stuck at same place.

the last thing I done is touch a DO_FACTORY_RESTORE file into the USB drive, and reboot. It works!!!
here is where I found it https://www.mobileread.com/forums/sho...d.php?t=223067

Thanks Knc1 for providing me so much useful information!

knc1 · 03-20-2016, 08:32 AM

Quote:

Originally Posted by kenxl

after much work, finally I got my PW1 back to life!

I follow the steps from:
https://gist.github.com/TobiasWooldr...ca75190b9a473f

but after reboot, it still stuck at same place.

the last thing I done is touch a DO_FACTORY_RESTORE file into the USB drive, and reboot. It works!!!
here is where I found it https://www.mobileread.com/forums/sho...d.php?t=223067

Thanks Knc1 for providing me so much useful information!

Yup - that one is an edited re-print of some of the information found here (by **I think** one of our members using a different screen name).

And of course, the archives of ixtab is the same ixtab you find here (along with links to his archives).

03-18-2016, 11:37 PM	#1
kenxl Junior Member Posts: 7 Karma: 10 Join Date: Mar 2016 Device: Kindle Paperwhite	PKW stuck at boot progress bar(95%) My KPW stuck at boot progress bar (95%). Reboot, no help. Connect USB-TTL cable, can update firmware from recovery menu. I tried some versions I can found: 5.3.0, 5.4.4, 5.6.1.1. Update all successful, but still stuck at same place. Anything I can do to save my KPW?

03-18-2016, 11:37 PM	#2
kenxl Junior Member Posts: 7 Karma: 10 Join Date: Mar 2016 Device: Kindle Paperwhite	here is the boot log: Please use spoiler tags for such a long post - MODERATOR] Spoiler: - U-Boot 2009.08-lab126 (Nov 29 2012 - 23:18:55) CPU: Freescale i.MX50 family 1.1V at 800 MHz mx50 pll1: 800MHz mx50 pll2: 400MHz mx50 pll3: 216MHz ipg clock : 66666666Hz ipg per clock : 66666666Hz uart clock : 24000000Hz ahb clock : 133333333Hz 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: Celeste WFO (256 MB) Boot Reason: [POR] Boot Device: MMC Board Id: ---------------------- S/N: ------------------------ DRAM: 256 MB Using default environment In: serial Out: logbuff Err: logbuff Quick Memory Test 0x70000000, 0xfffc000 POST done in 17 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: 4748160 Bytes = 4.5 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 Jun 23 04:29:16 PDT 2015 armv7l Press [ENTER] for recovery menu... 0 //dev/mmcblk0p4: CHS=4/16/43712 size=1432354816 bytes flag type first last lba first lba size Partition p1: 0x00 0x0b 16 <large> 16 2797552 CHS: 0/1/1 - <large> Partition p2: Partition p3: Partition p4: BOOTING DEFAULT. argc == 12 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]: "user_debug=0x1" argv[11]: "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 sytem:mounted_proc:: info system:mounted_sys:: info system:mounted_dev:: info milestone:5.80:49.1: info milestone:5.86:49.2: info milestone:5.89:49.3: info milestone:5.94:49.4: info milestone:5.99:49.5: info sytem:mounted_tmpfs:: info milestone:6.07:sy50: info system:start:time=6100: info hardware:no_wan::WiFi only device. No WAN found info system:configlatform=yoshime3,board=celeste,rev= 21,proto=Y,wifi=Y,wan=N: info milestone:6.31:sy51: lipc-send-event[550]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) lipc-send-event[550]: C def:dbusi::Failed to init dbus lipc-send-event[550]: E defpen::Failed to open LIPC lipc-send-event[550]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed lipc-send-event[555]: E lipc:con::Connection error(Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) lipc-send-event[555]: C def:dbusi::Failed to init dbus lipc-send-event[555]: E defpen::Failed to open LIPC lipc-send-event[555]: E def:fail:source=com.lab126.hal, event=usbPlugIn:Sending event failed info milestone:7.06:sy99: info system:done:time=7090: crond[586]: crond: crond (busybox 1.17.1) started, log level 8 init.exe: sshd main process (584) terminated with status 2 init.exe: sshd main process ended, respawning init.exe: recevent pre-start process (589) terminated with status 1 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: debug sytem:event_emitted:mounted_cramfs_loopbacks: info milestone:8.11:fs75: info system:emiting_event:loaded_modules_dependencies: debug sytem:event_emitted:loaded_modules_dependencies: info modules:modprobe:loading module g_file_storage: Welcome to Kindle! kindle login: 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:8.62:fs00: debug sytem:event_emitted:loaded_ppp_async: info system:emiting_event:loaded_fakekey: debug sytem:event_emitted:loaded_fakekey: info milestone:10.36:fs23: info system:emiting_event:mounted_varLocal: debug sytem:event_emitted:mounted_varLocal: info milestone:10.45:fs25: info milestone:10.53:vi00: info prereg:PRAGMA_QUICK_CHECK_PASSED::sts=0 info milestone:11.01:vi99: info display:started:time=11030: info system:emiting_event:display_ready: debug sytem:event_emitted:display_ready: info userstore:run:time=11260,action=start: info battery:charged:cap=100,mV=4193,mAH=1393: info userstore:start:found_bootup_flag:Found BOOTUP flag file info system:emiting_event:battery_ready: debug sytem:event_emitted:battery_ready: info system:emiting_event:loaded_touch: debug sytem:event_emitted:loaded_touch: info system:emiting_event:mounted_userstore: debug sytem:event_emitted:mounted_userstore: info milestone:12.46:fs50: info milestone:12.50:fs90: info milestone:12.54:fs99: info milestone:12.58: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:15.12:xx00: info X:load:time=15250: 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:17.51:xx50: info X:starting:time=17560: info milestone:22.51:xx99: info X:started:time=22560: info system:emiting_event:x_setup_ready: debug sytem:event_emitted:x_setup_ready: info locale:read:lang=en_US.UTF-8,lc_all=en_US.UTF-8:Retrieved Language info system:emiting_event:langpicker_ready: debug sytem:event_emitted:langpicker_ready: info blanket_f:module already loaded:splash: info milestone:25.09i00: info milestone:25.39i99: info hardware:no_wan::WiFi only device. No WAN found info board_data_file :/opt/ar6k/target/AR6003/hw2.1.1/bin/yoshime3/celeste/wfo/AR6003_wfo_calfile.bin:: info wifim:enablediv:enabling antenna diversity for wifi...: MAC from kernel xx:xx:xx:xx:xx:EA boot: I def:rbt:reset=user_reboot,version=268989: info system:emiting_event:contentpack_font_ready: debug sytem:event_emitted:contentpack_font_ready: info milestone:31.10:fr00: info milestone:31.23:fr50: info milestone:31.39:fr51: info framework:starting:time=34240: Last edited by Dr. Drib; 03-19-2016 at 07:32 AM.

03-19-2016, 01:24 AM	#6
kenxl Junior Member Posts: 7 Karma: 10 Join Date: Mar 2016 Device: Kindle Paperwhite	This is the screen my KPW1 stucks Attached Thumbnails

03-20-2016, 02:21 AM	#11
kenxl Junior Member Posts: 7 Karma: 10 Join Date: Mar 2016 Device: Kindle Paperwhite	after much work, finally I got my PW1 back to life! I follow the steps from: https://gist.github.com/TobiasWooldr...ca75190b9a473f but after reboot, it still stuck at same place. the last thing I done is touch a DO_FACTORY_RESTORE file into the USB drive, and reboot. It works!!! here is where I found it https://www.mobileread.com/forums/sho...d.php?t=223067 Thanks Knc1 for providing me so much useful information! Last edited by eschwartz; 03-20-2016 at 04:47 PM. Reason: url --> link

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PDF progress bar	Bearded	Amazon Kindle	0	03-18-2016 07:03 AM
Progress bar?	frogette	Which one should I buy?	13	10-18-2014 04:01 AM
No Progress bar on the Touch...	grizedale	Amazon Kindle	13	09-29-2011 05:02 PM
Understanding the progress bar	wanderr	Amazon Kindle	3	03-12-2011 02:06 PM
Opus cannot boot, stuck on boot screen	baloma	Bookeen	35	11-13-2010 04:20 AM

03-19-2016, 09:25 AM	#9
kenxl Junior Member Posts: 7 Karma: 10 Join Date: Mar 2016 Device: Kindle Paperwhite	Thanks knc1 for all the information you provided. They are very helpful to me. I am very sorry for Duokan's stealing stuff from here. Since I found many useful information by google, I came here for some help. Thank you again!

Advert

Advert