PW4 w/jailbreak: restart takes 3 minutes

makue · 12-23-2018, 09:55 AM

Since upgrading to 5.10.1.2 (and maybe a fake registration) it takes my kindle up to 3 minutes to restart.
Even holding the power button for >40 seconds does not speed up the restart or breaks the time-out period.

Device Kindle PW4: G000 T6 (european, 32GB, WIFI-only, w/ special offers)

Initial fimrware was 5.10.0.1 then it was successfully jb'ed.
Recent firmware 5.10.1.2

hotfix: JailBreak-1.15.N-FW-5.x-hotfix
KUAL version: KUAL-v2.7.14-g174c43f-20181209
Python: kindle-python-0.15.N-r15585.tar
ScreenSaver: kindle-linkss-0.25.N-r15585
USBNet: kindle-usbnet-0.22.N-r15585.tar
LibrarianSync: librariansync-1.10.tar.gz + FIX LibrarianSync.zip

The device was fake-registered first, now it is registered with Amazon

I'm not sure for 100% but it seem to me, the slow restart began after creating a fake registration
(writing a file /var/local/java/prefs/reginfo) after the update to 5.10.1.2.
Therefore I decided to register it the normal way with Amazon, but this does not reduce the restart time.

Libriansync, screensaver and USBNet are working so far.

It's more an observation than a problem to me on the other hand I'm curious to know whats happening there.

knc1 · 12-23-2018, 10:05 AM

Check the quality of your WiFi connection to Amazon.
Compare the content of what you used as the fake registration file and what content 5.10.1.2 wrote.
Report your findings here.

How many books?
How many collections?
Do they show in the "Manage Content and Devices" page of your Amazon account?

makue · 12-23-2018, 10:59 AM

The quality of the WIFI connection is 90%

The 1st fake reginfo was:
#Wed Nov 22 01:01:01 CET 2017
givenName=M.
userId=amzn1.account.xxxxxxxGFJM7T4xxxxxxxxxxxxxxx
deviceName=M.'s KOA2
userName=M. K.
deviceEmailAddress=m._e7xxxx@kindle.com

now it is:
#Sat Dec 22 01:01:01 GMT+00:58 2018
givenName=M.
userId=amzn1.account.xxxxxxxGFJM7T4xxxxxxxxxxxxxxx
deviceName=M.'s PW4
userName=M. K.
deviceEmailAddress=m._6exxxx@kindle.com

I changed some items for anonymity but in fact I simply copied the reginfo from my already registered KOA2 to the PW4. The registration only changed the email address for the PW4, the userId stayed exactly the same.

There are 220 books and 1 collection and they show up in the amazon account.

Normally I use my kindles just offline and then the number including side-loaded books and collections are in total 633 books and 10 collections.

Does the process of re-indexing the books after a firmware change affect the restart time too? This would be a good explanation.

NiLuJe · 12-23-2018, 12:43 PM

When, exactly, in the boot process does it stall?

Note that you'll probably never cold-boot even an empty Kindle below 1 minute (or so), but, still, three times that seems strange.

Are you booting with the USB cord plugged into something? How is USBNet setup?

knc1 · 12-23-2018, 01:27 PM

Quote:

Originally Posted by makue

- - - -

I changed some items for anonymity but in fact I simply copied the reginfo from my already registered KOA2 to the PW4. The registration only changed the email address for the PW4, the userId stayed exactly the same.

- - - - -

Where both devices running the same firmware version when you did that?
(What you are changing is more firmware specific than hardware specific.)

Are both devices running the same firmware version now?

Do you have (exactly) the same books on both devices now?

makue · 12-23-2018, 02:11 PM

The PW4 stalls at the screen with a german text meaning "Please wait a moment while your kindle starts up" with the boy sitting under the tree.

The KOA2 where I took the reginfo from is on firmware 5.10.1.1 and the PW4 where I placed it is on 5.10.1.2

Both contained exactly the same books and collections synchronized by calibre and were offline.

I booted w/o any USB connction.
USB networking is disabled and it is disabled at boot time.

Btw. it takes 3 minutes to start booting at all not finishing

NiLuJe · 12-23-2018, 02:20 PM

So, before the progress bar even shows up, right? (And possibly before the frontlight lits up, too? Although that behavior may be device-dependent).

You may get a bit more info by checking the system logs (showlog)?

knc1 · 12-23-2018, 02:59 PM

Bad font/locale handling???

Switch it to English and see if the problem goes away.

makue · 12-23-2018, 03:11 PM

Yes, the kindle hangs way before the progress bar and w/o frontlights.

After issuing the ";dm" command I have some log files now but I lack the knowledge to find something helpful in them. Shall I post some/all of them here?

NiLuJe · 12-23-2018, 04:05 PM

Only the "system" one should be relevant, provided it didn't get truncated at a key moment by the log rotation feature

.

makue · 12-24-2018, 06:47 AM

Ok, here is a snippet from the log. I've issued the restart at 12:16:00

The hang is visible between
121615:"Found BOOTUP flag file" and
112215 "syslog-ng version 1.16.12 starting"

This time taking 6 minutes (the time zone is changed later)

Unfortunately this gives me no clue what's happening...

181224:121614 syslog-ng[417]: SIGHUP received, restarting syslog-ng
181224:121614 [ 875.901653] userstore ( 7228): drop_caches: 3
181224:121614 system: I userstore: filesystem sync done::
181224:121615 system: I userstore: stop:found_bootup_flag:Found BOOTUP flag file
181224:112215 syslog-ng[419]: syslog-ng version 1.6.12 starting
181224:112215 [ 0.000000] Booting Linux on physical CPU 0x0
181224:112215 [ 0.000000] Linux version 4.1.15-lab126 (jenkins-official@sjc10-jbuild08) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Tue Oct 16 15:54:38 PDT 2018
181224:112215 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
181224:112215 [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
181224:112215 [ 0.000000] Machine model: Lab126 i.MX6SLL Board
181224:112215 [ 0.000000] dt: falcon bios 0x9ffd0000(0x30000)
181224:112215 [ 0.000000] dt: storage bios

knc1 · 12-24-2018, 09:14 AM

Quote:

Originally Posted by makue

Ok, here is a snippet from the log. I've issued the restart at 12:16:00

The hang is visible between
121615:"Found BOOTUP flag file" and
112215 "syslog-ng version 1.16.12 starting"

This time taking 6 minutes (the time zone is changed later)

Unfortunately this gives me no clue what's happening...

181224:121614 syslog-ng[417]: SIGHUP received, restarting syslog-ng
181224:121614 [ 875.901653] userstore ( 7228): drop_caches: 3
181224:121614 system: I userstore: filesystem sync done::
181224:121615 system: I userstore: stop:found_bootup_flag:Found BOOTUP flag file
181224:112215 syslog-ng[419]: syslog-ng version 1.6.12 starting
181224:112215 [ 0.000000] Booting Linux on physical CPU 0x0
181224:112215 [ 0.000000] Linux version 4.1.15-lab126 (jenkins-official@sjc10-jbuild08) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Tue Oct 16 15:54:38 PDT 2018
181224:112215 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
181224:112215 [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
181224:112215 [ 0.000000] Machine model: Lab126 i.MX6SLL Board
181224:112215 [ 0.000000] dt: falcon bios 0x9ffd0000(0x30000)
181224:112215 [ 0.000000] dt: storage bios

Correcting (or trying to) file system errors.
Six minutes is nothing in this case, error correction can sometimes take days.

This is a PW4, so it is still in warranty, return it as broke (which it is) and get a different one in return.

makue · 12-24-2018, 12:19 PM

Hmm, ok thank you, youre explanation makes unfortunately sense.

I'm a bit reluctant to send the kindle back as I fear to receive a (refurbished) device w/ a recent firmware and hence w/o chance to jailbreak.

Is there a system command to look up how much is already damaged at the moment (# of bad blocks)?

knc1 · 12-24-2018, 12:33 PM

Quote:

Originally Posted by makue

Hmm, ok thank you, youre explanation makes unfortunately sense.

I'm a bit reluctant to send the kindle back as I fear to receive a (refurbished) device w/ a recent firmware and hence w/o chance to jailbreak.

Is there a system command to look up how much is already damaged at the moment (# of bad blocks)?

The eMMC should be a new enough model to respond to SMART commands.
If not, then somewhere here I posted the utility to get similar information from eMMC devices that do not support SMART commands.
It will be an attachment to one of my posts, probably a thread starter. But that is all I can tell you. Too many years, too many posts.

NiLuJe · 12-24-2018, 04:01 PM

@makue: I'd first take a look at a *full* log dumped via showlog and not ;dm, because Amazon's logging facilities sometime do funny things when coalescing logs...

(i.e., here, I'm only seeing the replay of dmesg's backlog done once the system logger boots up, which doesn't tell us much about when exactly it hung, besides "before syslog-ng appeared to have been brought up").

12-23-2018, 10:05 AM	#2
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Check the quality of your WiFi connection to Amazon. Compare the content of what you used as the fake registration file and what content 5.10.1.2 wrote. Report your findings here. How many books? How many collections? Do they show in the "Manage Content and Devices" page of your Amazon account? Last edited by knc1; 12-23-2018 at 10:07 AM.

12-23-2018, 12:43 PM	#4
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	When, exactly, in the boot process does it stall? Note that you'll probably never cold-boot even an empty Kindle below 1 minute (or so), but, still, three times that seems strange. Are you booting with the USB cord plugged into something? How is USBNet setup? Last edited by NiLuJe; 12-23-2018 at 12:46 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle PW4 - Collections from Folders without Jailbreak?	DarkWolf	Kindle Developer's Corner	3	11-20-2018 03:56 PM
Kobo Glo Freezing a Few Minutes after Restart	tnforpaul45	Kobo Reader	2	03-20-2016 05:09 PM
PRS-650 PRS-650 takes 6 minutes to open, 2 minutes to save a note	Eugenie	Sony Reader	15	06-07-2015 08:37 PM
Takes 8 minutes every time device is plugged in	Markqz	Devices	5	02-11-2015 06:49 PM
Library takes 5 minutes to open the reader!	accipiter	Sony Reader	1	02-02-2009 12:46 AM

12-23-2018, 09:55 AM	#1
makue Custom User Title Posts: 42 Karma: 10 Join Date: Aug 2017 Device: Kindle PW3	PW4 w/jailbreak: restart takes 3 minutes Since upgrading to 5.10.1.2 (and maybe a fake registration) it takes my kindle up to 3 minutes to restart. Even holding the power button for >40 seconds does not speed up the restart or breaks the time-out period. Device Kindle PW4: G000 T6 (european, 32GB, WIFI-only, w/ special offers) Initial fimrware was 5.10.0.1 then it was successfully jb'ed. Recent firmware 5.10.1.2 hotfix: JailBreak-1.15.N-FW-5.x-hotfix KUAL version: KUAL-v2.7.14-g174c43f-20181209 Python: kindle-python-0.15.N-r15585.tar ScreenSaver: kindle-linkss-0.25.N-r15585 USBNet: kindle-usbnet-0.22.N-r15585.tar LibrarianSync: librariansync-1.10.tar.gz + FIX LibrarianSync.zip The device was fake-registered first, now it is registered with Amazon I'm not sure for 100% but it seem to me, the slow restart began after creating a fake registration (writing a file /var/local/java/prefs/reginfo) after the update to 5.10.1.2. Therefore I decided to register it the normal way with Amazon, but this does not reduce the restart time. Libriansync, screensaver and USBNet are working so far. It's more an observation than a problem to me on the other hand I'm curious to know whats happening there.

12-23-2018, 10:59 AM	#3
makue Custom User Title Posts: 42 Karma: 10 Join Date: Aug 2017 Device: Kindle PW3	The quality of the WIFI connection is 90% The 1st fake reginfo was: #Wed Nov 22 01:01:01 CET 2017 givenName=M. userId=amzn1.account.xxxxxxxGFJM7T4xxxxxxxxxxxxxxx deviceName=M.'s KOA2 userName=M. K. deviceEmailAddress=m._e7xxxx@kindle.com now it is: #Sat Dec 22 01:01:01 GMT+00:58 2018 givenName=M. userId=amzn1.account.xxxxxxxGFJM7T4xxxxxxxxxxxxxxx deviceName=M.'s PW4 userName=M. K. deviceEmailAddress=m._6exxxx@kindle.com I changed some items for anonymity but in fact I simply copied the reginfo from my already registered KOA2 to the PW4. The registration only changed the email address for the PW4, the userId stayed exactly the same. There are 220 books and 1 collection and they show up in the amazon account. Normally I use my kindles just offline and then the number including side-loaded books and collections are in total 633 books and 10 collections. Does the process of re-indexing the books after a firmware change affect the restart time too? This would be a good explanation.

12-23-2018, 02:11 PM	#6
makue Custom User Title Posts: 42 Karma: 10 Join Date: Aug 2017 Device: Kindle PW3	The PW4 stalls at the screen with a german text meaning "Please wait a moment while your kindle starts up" with the boy sitting under the tree. The KOA2 where I took the reginfo from is on firmware 5.10.1.1 and the PW4 where I placed it is on 5.10.1.2 Both contained exactly the same books and collections synchronized by calibre and were offline. I booted w/o any USB connction. USB networking is disabled and it is disabled at boot time. Btw. it takes 3 minutes to start booting at all not finishing

12-23-2018, 02:20 PM	#7
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	So, before the progress bar even shows up, right? (And possibly before the frontlight lits up, too? Although that behavior may be device-dependent). You may get a bit more info by checking the system logs (showlog)?

12-23-2018, 02:59 PM	#8
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Bad font/locale handling??? Switch it to English and see if the problem goes away.

12-23-2018, 03:11 PM	#9
makue Custom User Title Posts: 42 Karma: 10 Join Date: Aug 2017 Device: Kindle PW3	Yes, the kindle hangs way before the progress bar and w/o frontlights. After issuing the ";dm" command I have some log files now but I lack the knowledge to find something helpful in them. Shall I post some/all of them here?

12-23-2018, 04:05 PM	#10
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Only the "system" one should be relevant, provided it didn't get truncated at a key moment by the log rotation feature .

12-24-2018, 06:47 AM	#11
makue Custom User Title Posts: 42 Karma: 10 Join Date: Aug 2017 Device: Kindle PW3	Ok, here is a snippet from the log. I've issued the restart at 12:16:00 The hang is visible between 121615:"Found BOOTUP flag file" and 112215 "syslog-ng version 1.16.12 starting" This time taking 6 minutes (the time zone is changed later) Unfortunately this gives me no clue what's happening... 181224:121614 syslog-ng[417]: SIGHUP received, restarting syslog-ng 181224:121614 [ 875.901653] userstore ( 7228): drop_caches: 3 181224:121614 system: I userstore: filesystem sync done:: 181224:121615 system: I userstore: stop:found_bootup_flag:Found BOOTUP flag file 181224:112215 syslog-ng[419]: syslog-ng version 1.6.12 starting 181224:112215 [ 0.000000] Booting Linux on physical CPU 0x0 181224:112215 [ 0.000000] Linux version 4.1.15-lab126 (jenkins-official@sjc10-jbuild08) (gcc version 4.9.1 (GCC) ) #1 SMP PREEMPT Tue Oct 16 15:54:38 PDT 2018 181224:112215 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d 181224:112215 [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache 181224:112215 [ 0.000000] Machine model: Lab126 i.MX6SLL Board 181224:112215 [ 0.000000] dt: falcon bios 0x9ffd0000(0x30000) 181224:112215 [ 0.000000] dt: storage bios

12-24-2018, 12:19 PM	#13
makue Custom User Title Posts: 42 Karma: 10 Join Date: Aug 2017 Device: Kindle PW3	Hmm, ok thank you, youre explanation makes unfortunately sense. I'm a bit reluctant to send the kindle back as I fear to receive a (refurbished) device w/ a recent firmware and hence w/o chance to jailbreak. Is there a system command to look up how much is already damaged at the moment (# of bad blocks)?

12-24-2018, 04:01 PM	#15
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@makue: I'd first take a look at a full log dumped via showlog and not ;dm, because Amazon's logging facilities sometime do funny things when coalescing logs... (i.e., here, I'm only seeing the replay of dmesg's backlog done once the system logger boots up, which doesn't tell us much about when exactly it hung, besides "before syslog-ng appeared to have been brought up").