kindle paperwhite 2 not included

[knc1]

Originally Posted by VariH2O

I am still at the stage of selection of the password. Password that generated kindletool not suitable.

If is more exact I am here

*** Take note of the Serial Number (S / N) shown during boot. You may need to increase the amount of scrollback or history in PuTTY as this is near the top. Enter the Serial Number into the tool below to compute a list of the possible root passwords for your Kindle. ***

Today I will continue to try to pass the password and login.

Thanks.

Now complete all of the following section, labeled:

Step 2
Boot into Diagnostics Mode

Post here at the end of that, where you should be looking at the diagnostics login, rather than the main login. (the password is not expected to work for the main login, only for the diagnostics login - Kindles are 'dual system boot' machines - two (2) OS installed).

[VariH2O]

Originally Posted by knc1

Thanks.

Now complete all of the following section, labeled:



Post here at the end of that, where you should be looking at the diagnostics login, rather than the main login. (the password is not expected to work for the main login, only for the diagnostics login - Kindles are 'dual system boot' machines - two (2) OS installed).

To be honest I do not fully understand you (I have a little problem with English) ...

As I understood, it is possible to enter the diagnostic mode, without superuser.

As I understand it, I can write:

kindle login: Boot into Diagnostics Mode
Password: //my password + Enter//(I have two passwords: Root PW, Recowery PW, Which should be used?)
Login incorrect

Did I understand you correctly? Login *Root* is not necessary to use?

[knc1]

All lower case for the username: root
do not enter it as: Root
You might not need a password, try just pressing enter.

[VariH2O]

Originally Posted by knc1

All lower case for the username: root
do not enter it as: Root
You might not need a password, try just pressing enter.

It does not work

[knc1]

Originally Posted by VariH2O

It does not work

Enable 'capture' in putty, then follow the entire sequence until you get stuck.

zip the capture log, attach to your next post, that way we can read it.

[VariH2O]

Originally Posted by knc1

Enable 'capture' in putty, then follow the entire sequence until you get stuck.

zip the capture log, attach to your next post, that way we can read it.

I copied my logs completely. The serial number has changed a couple of characters. Can you give it if needed. I copied logs through СTRL + C. I can write the log by putti if that is not enough.

Maybe I give you my serial number? You try to generate a password, maybe I do something wrong ...

[HarryT]

Do not make your entire serial number public. It's not at all a good idea: people could make malicious use of it.

[knc1]

Originally Posted by VariH2O

I copied my logs completely. The serial number has changed a couple of characters. Can you give it if needed. I copied logs through СTRL + C. I can write the log by putti if that is not enough.

Maybe I give you my serial number? You try to generate a password, maybe I do something wrong ...

Now follow the directions.

Hit any key to stop autoboot: 0
## Booting kernel from Legacy Image at 80800000 ...

See where it says:
"Hit any key to stop autoboot:"
Well, do it.
I fact, you can begin pressing keys before you see that message.

**IF** you press the key in time, you will not see the:
"## Booting kernel from Legacy Image at 80800000 ..."
message.
Instead, you will see the u-boot prompt as shown in the pictures at the link you posted.

If you see the "## Booting ..." message, start over, try again.
NOTE: You must have flow control (both hardware and software) disabled in Putty.

At my age, I don't have enough years left to help this person, somebody else do it.
http://uncyclopedia.wikia.com/wiki/Any_Key
https://en.wikipedia.org/wiki/Any_key

[VariH2O]

Originally Posted by knc1

Now follow the directions.

See where it says:
"Hit any key to stop autoboot:"
Well, do it.
I fact, you can begin pressing keys before you see that message.

**IF** you press the key in time, you will not see the:
"## Booting kernel from Legacy Image at 80800000 ..."
message.
Instead, you will see the u-boot prompt as shown in the pictures at the link you posted.

If you see the "## Booting ..." message, start over, try again.
NOTE: You must have flow control (both hardware and software) disabled in Putty.

At my age, I don't have enough years left to help this person, somebody else do it.
http://uncyclopedia.wikia.com/wiki/Any_Key
https://en.wikipedia.org/wiki/Any_key

My God, I was such a fool ... I apologize. I went to the diagnostic menu, the firmware copied to the memory Kindle, went to the upgrade process but in the course of renovation in putty I see the following:

update-payload.dat:EOF

imx60_wario/uImage 2752512 [######################################]



rootfs.img.gz 206792663 [######################################]



imx60_wario/uImage 2752512 [######################################]
rootfs.img.gz 126480630 [########################::::::::::::::][ 240.162666] INFO: task init:1 blocked for more than 12 0 seconds.
[ 240.168693] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
^C^C
[ 360.182670] INFO: task init:1 blocked for more than 120 seconds.
[ 360.188697] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 360.203987] INFO: task loop0:620 blocked for more than 120 seconds.
[ 360.210269] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 480.222652] INFO: task init:1 blocked for more than 120 seconds.
[ 480.228677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 480.243972] INFO: task loop0:620 blocked for more than 120 seconds.

Launched firmware several times. Constantly brakes on this block 126480630.

[knc1]

Enable the capture file (Session Logging) in Putty.


Re-boot the Kindle.

This way we can see everything that happens on the serial port.

What (if anything) you enter using the screen -
Anything you do on another computer -
Keep notes.

When you hit a point that you can not go futher -
Disable the capture file -
Open the log file in a text editor, annotate the log at the proper points with your notes.

When you use a file (or anything else) that you got somewhere else, include a link and a name.

Compress the capture file (log file).
Please do not use RAR (it still has not gone fully Open Source) -
Use 7Zip instead (which you need for opening NiLuJe's snapshots anyway) -
http://www.7-zip.org/download.html

Attach the compressed capture file (log file) to your next post.
You will have to select the 'Advanced Editor' and scroll down past the text entry box to see the 'Manage Attachments' section.

**Remember when Posting**

• We can not see over your shoulder.
• We can not directly channel into your mind.

You must write up everything you do.
Use your native language if you must, somebody here can translate it.
The site has over 1/4 million members, so unless you are the Last of the Monhicans, somebody can read it.

This post might help:
http://www.garynorth.com/public/1896.cfm

[VariH2O]

Originally Posted by knc1

Enable the capture file (Session Logging) in Putty.


Re-boot the Kindle.

This way we can see everything that happens on the serial port.

What (if anything) you enter using the screen -
Anything you do on another computer -
Keep notes.

When you hit a point that you can not go futher -
Disable the capture file -
Open the log file in a text editor, annotate the log at the proper points with your notes.

When you use a file (or anything else) that you got somewhere else, include a link and a name.

Compress the capture file (log file).
Please do not use RAR (it still has not gone fully Open Source) -
Use 7Zip instead (which you need for opening NiLuJe's snapshots anyway) -
http://www.7-zip.org/download.html

Attach the compressed capture file (log file) to your next post.
You will have to select the 'Advanced Editor' and scroll down past the text entry box to see the 'Manage Attachments' section.

**Remember when Posting**

• We can not see over your shoulder.
• We can not directly channel into your mind.

You must write up everything you do.
Use your native language if you must, somebody here can translate it.
The site has over 1/4 million members, so unless you are the Last of the Monhicans, somebody can read it.

This post might help:
http://www.garynorth.com/public/1896.cfm

Thank you for instruction and for your advice, I I will consider.

Recorded logs.

The sequence of my actions:

1) Run the cherubs indicates speed, choose a serial port, I press "Open" and includes books.

2) Waiting for label and stop autoboot.

3) Run in diagnostic mode.

4) In the diagnostic menu, choose "U - Enter USB mode", copy the firmware to the memory, reboot Kindle.

Then begins flashing, but stops at a particular block. Unusual and should be seen in the logs.




Спасибо за инструкцию и за ваши советы, я учту.

Записал логи.

Последовательность моих действий:

1) Запускаем Putty, указываю скорость, выбираю серийный порт, жму "Open" и включаю книгу.

2) Жду надпись и останавливаю autoboot.

3) Запускаюсь в диагностическом режиме.

4)В диагностическом меню выбираю "U - Enter USB mode" , копирую в память прошивку, перезагружаю Kindle.

Далее начинается прошивка, но останавливается на определённом блоке. Должно быть видно в логах.

[knc1]

The 'main' firmware is flashed.

It is only the **second** time that it tries to re-flash the same firmware that the system enters a loop.
We will try to deal with that **only** if it shows to be significant.

1. Reboot the system.
2. Enter Diags.
3. Export USB.
4. Connect to PC.
5. Remove (delete) any file update_*.bin.
6. Safely remove USB cable.
7. Disable Diags.
8. Exit and Re-boot (without the usb-pc cable connected).
9. It should "just work".
   It may take awhile to re-start, it has to recover the journal on the 'main' file system.
   Just keep it connected to a wall charger until it recovers.

[VariH2O]

I try now.

[knc1]

Originally Posted by VariH2O

Unfortunately, I think not so successful. With further startup I get the console:



And yet. Then nothing is written. Not reaching to entering password (login Kindle / Kindle password),
This can be a problem in the firmware?



К сожалению, мне кажется так не увенчается успехом. При дальнейшем запуске я получаю в консоли:


И всё. Дальше ничего не пишется. Не доходит до ввода пароля (Киндл логин/ киндл password) ,

Это может быть проблема в прошивке?

There is no need to login in.
Forget about that, that is long past, the device has had the new image re-loaded.

Just leave it on the wall charger, give it time to recover.
(You can expect to be looking at the boy under the tree for at least a day or two.)

If it does not recover on its own, then it is a bad flash device (bad hardware).
Only replacing the flash chip will fix it.

= = = =

You have not yet given the full image update filename nor the link where you got it from.
This would be much easier if you would follow directions.

I don't ask you to do things, just to use up my time with the asking.

You have a 4Gbyte PW-2, the firmware for the earlier 2Gbyte PW-2 devices **will not** work!
And without the name and link, I have no idea what you are trying to load (the 'diags' on the PW-2 may not be checking the model correctly).

It makes absolutely no sense to ask for directions and then fail to follow them.
It is only a waste of your time to ask and a waste of my time to answer.

[VariH2O]

Originally Posted by knc1

The 'main' firmware is flashed.

It is only the **second** time that it tries to re-flash the same firmware that the system enters a loop.
We will try to deal with that **only** if it shows to be significant.

1. Reboot the system.
2. Enter Diags.
3. Export USB.
4. Connect to PC.
5. Remove (delete) any file update_*.bin.
6. Safely remove USB cable.
7. Disable Diags.
8. Exit and Re-boot (without the usb-pc cable connected).
9. It should "just work".
   It may take awhile to re-start, it has to recover the journal on the 'main' file system.
   Just keep it connected to a wall charger until it recovers.

The work came out the same error as here: https://www.mobileread.com/forums/arc.../t-263045.html . You have already explained that the man should be doing in this situation, try these instructions.