PW PW USBNET your kindle neeeds repair

[bmsleight]

Hi,

I broke it go I get to keep both parts! Fail of the day. Never code whilst tired.

On a PW1, as part of an unusual software I am developing. I was automating adding keys to /mnt/us/usbnet/etc/authorized_keys

		cat /tmp/sshid >> /mnt/us/usbnet/etc/authorized_keys
		sleep 2
		reboot

In error I ended up with a blank line in /mnt/us/usbnet/etc/authorized_keys

Example not exact keys..

ssh-rsa AAAAB3Nza....
ssh-rsa AAAAB3N..

ssh-rsa ABAA...

The kindle was in a reboot cycle. So being careless. Issh in using the newly added key ABAA.... I then did

vi /mnt/us/usbnet/etc/authorized_keys

Removed the blank line. Kindle reboots. The goes to dreaded "your kindle neeeds repair".

The kindle will not connect as USB storage. Boots quiet quickly to the "your kindle neeeds repair". Any suggestions (please not the soldering iron!).

Time to find another 2nd hand paperwhite ?
Is 3G an issue ?

Regards,
Brendan


USBNetwork - 2020-10-11 13:05 NiLuJe
Serial Number Kindle: B029 (Unconfirmed - sticker not checked on machine)
Kindle: Kindle PaperWhite 3G + WiFi

[NiLuJe]

If you don't have the Rescue Pack + CRP installed, yep, that's a trip to a boot interrupt via serial to go to diags and reset the fail counter from there (it's in two places in /var/local, if memory serves, one for X, one for the framework, and/or one for failures-per-boot, and one for full-failures-after-reboot).

[bmsleight]

Originally Posted by NiLuJe

If you don't have the Rescue Pack + CRP installed.

Time to install that on my three other PW before I do anything next!

Originally Posted by NiLuJe

yep, that's a trip to a to go to diags

I have hands that are not nimble Ok what fun....

Thanks for the quick reply. I am off to swear at myself some more.

Regards,
Brendan

[bmsleight]

HI

The definition of insanity is doing the same thing over and over again and expecting a different result.

Another Kindle PW1. The good news is the I have the Coward's Rescue Pack.

Code that caused trouble:-

		cp /mnt/us/usbnet/etc/authorized_keys /tmp/authorized_keys
		cat /tmp/sshid >> /tmp/authorized_keys
		# Remove any blank lines 
		grep -v -e '^$' /tmp/authorized_keys > /mnt/us/usbnet/etc/authorized_keys
		sleep 2
		reboot

The ssh update worked, I was able to login. But it continually rebooted. Until I get the your kindle needs repair screen.

The kindle was on a wifi network that does nto have access to the internet (touch /mnt/us/WIFI_NO_NET_PROBE)

I have the USB Networking log.
https://pastebin.pl/view/4618e68d


With the diagnostics mode available, via Coward's Rescue Pack - is there a way to restore ?
I tried USB networking

$ ssh root@192.168.15.244
ssh: connect to host 192.168.15.244 port 22: Connection refused
$ telnet 192.168.15.244
Trying 192.168.15.244...
telnet: Unable to connect to remote host: Connection refused
# nmap -sS 192.168.15.244
Starting Nmap 7.80 ( https://nmap.org ) at 2020-12-19 20:54 GMT
Nmap scan report for 192.168.15.244
Host is up (0.0024s latency).
All 1000 scanned ports on 192.168.15.244 are closed
MAC Address: EE:59:00:00:00:15 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 5.89 seconds
# nmap -Pn 192.168.15.244
Starting Nmap 7.80 ( https://nmap.org ) at 2020-12-19 20:54 GMT
Nmap scan report for 192.168.15.244
Host is up (0.0024s latency).
All 1000 scanned ports on 192.168.15.244 are closed
MAC Address: EE:59:00:00:00:15 (Unknown)

Nmap done: 1 IP address (1 host up) scanned in 5.88 seconds

Do I put https://s3.amazonaws.com/G7G_Firmwar...ndle_5.3.3.bin as update.bin in root of a mounted kinlde ?
[https://gist.github.com/ramast/58633...ecc96965d48ed]


Or

Do /DO_FACTORY_RESTORE in mount ?

Worried I can not do

 echo 0 > /var/local/upstart/lab126_gui.restarts

[https://www.mobileread.com/forums/sh....php?t=264752]

Any help would be great.

Lockdown fun!. Both locked out of Kindle and Locked in at home!

Regards,
Brendan

[NiLuJe]

You have to *enable* USBNet in the diags menu first (I don't recall the PW1 layout OTOH, but it's fairly self-evident. The K4 JB instructions on the wiki might help, since they essentially *require* doing that).

IIRC, the exact procedure is detailed in the RP's README, though.

(You also need the Rescue Pack installed before the CRP, or the sshd in diags goes bye-bye. In short: RP makes sure the sshd is there, working, and won't get killed; CRP allows you to boot to diags automatically when plugged in. Which means CRP alone is useless, and RP alone requires USBMS access to boot to diags).

----

A full update won't reset the fail counter.

A factory reset *might* but I don't know if it trips before or after the KNR check (and/or whether that check actually works at all on that FW/device).

There *might* be a way to do that from diags directly, though, assuming you don't fat-finger an "erase mmc" along the way p).

[bmsleight]

You have to *enable* USBNet in the diags menu first

I did enable the USBNet
N) Misc individual diagnostics -> U) Utilities -> Z) Enable USBNet

RP alone requires USBMS access to boot to diags

No Rescue Pack Installed! Guess who feels silly now!

[bmsleight]

Long shot - I tried renaming update_kindle_5.3.3.bin to update.bin and placing it in the root of mounted kindle - but file gets deleted on reboot - is there a way to enable this installation ?

[bmsleight]

DO_FACTORY_RESTORE worked

[bmsleight]

TLDR: Kindle will go into reboot loop and then "your kindle needs repair" if wifi not set-up correctly when using WIFI_NO_NET_PROBE

Longer:-
Well I found the bug. The openWRT access point, was incorrectly configured by me.

I had set WIFI_NO_NET_PROBE

touch /mnt/us/WIFI_NO_NET_PROBE

I had:-

Kindle <---wifi --> OpenWRT AP [192.168.2.x] <-- ethernet --> Home router [192.168.1.x] <-- Internet -->

The Kindle was fine with ethernet disconnected

Kindle <---wifi --> OpenWRT AP [192.168.2.x]

But when I connect with my laptop [192.168.1.x] to debug, I was going wifi (other) ->home router -> Ethernet. However the wifi access point was set-up wrong. Such that, from any device connected to the wifi, (such as the Kindle), could ping internet but not receive response.

I have now corrected the Routed AP documentation:-
https://openwrt.org/docs/guide-user/...ype=sidebyside

Thanks for all the help. I can carry on tweaking my app prior to release (with Coward's Rescue Pack and Rescue Pack installed - to help bail me out).