Time to see if the serial number to password generated by the Python snippet in "Serial jail breaking" still generates the correct fiona password.
Code:
diag>?
get_input_from_stdin Received [?]
diag> MUSCAT_WFO - System Diags - 74
~~~~ 1.1.30.291999 ~~~~
pcbId:0670309164410CQB
(DS INFO)-Device Setting
(TOUCH PLATE)-Touch Plate Test
(OTS)-Operator test suite
(o)-Misc individual diagnostics
(WIFI NART)-nART factory test
(USB EXPORT)-USB device mode
(o)-Reboot or Disable Diags
(POWER SUSPEND)-Lock screen
(X)-Exit
exit login
get_input_from_stdin Received [EXIT LOGIN]
diag>ls: /var/local/log/messages_*.gz: No such file or directory
EXIT LOGIN: RESULT <PASS>
sock_close Sock close
Waiting to stop
Closing /dev/input/event0
Closing /dev/input/event1
Closing server_socket
Stopped
Exit to login prompt: 1
/etc/init.d/rcS: line 121: boot_milestone: not found
starting pid 2086, tty '': '/bin/sh /etc/getty-diags'
Welcome to Kindle!
[192_168_15_244] login:
Meanwhile, what did that command do to our USB networking setup?
Code:
mszick:PW3-Serial> ping -c 3 192.168.15.244
PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data.
64 bytes from 192.168.15.244: icmp_seq=1 ttl=64 time=0.410 ms
64 bytes from 192.168.15.244: icmp_seq=2 ttl=64 time=0.280 ms
64 bytes from 192.168.15.244: icmp_seq=3 ttl=64 time=0.403 ms
--- 192.168.15.244 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2026ms
rtt min/avg/max/mdev = 0.280/0.364/0.410/0.061 ms
mszick:PW3-Serial> ping -c 3 192.168.15.244
PING 192.168.15.244 (192.168.15.244) 56(84) bytes of data.
64 bytes from 192.168.15.244: icmp_seq=1 ttl=64 time=6.88 ms
64 bytes from 192.168.15.244: icmp_seq=2 ttl=64 time=0.301 ms
64 bytes from 192.168.15.244: icmp_seq=3 ttl=64 time=0.409 ms
--- 192.168.15.244 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2017ms
rtt min/avg/max/mdev = 0.301/2.533/6.889/3.080 ms
Answer: Nothing, it is still up and running.
And trying the password output by the Python snippet in "Serial jail breaking":
**Edit**
There have been some changes to that in the past, let me take a break and see what password the current KindleTool generates.
Code:
knc1:PW3-Serial> kindletool info G090G1.....
Device uses the new device ID scheme
Platform is Wario or newer
Root PW fionaed4
Recovery PW fionaed48
Hmm...
That is different than the output from that Python snippet.
I either typo'd something last night, made an error in transcription, or that Python snippet in "Serial jail breaking" is out of date.
I typo'd something last night, the output of the Python snippet in "Serial jail breaking" is correct.
Code:
[192_168_15_244] login: root
Password:
[root@[192_168_15_244] root]#
The first password output by the current KindleTool is correct, just like it should be.
Our networking?
Code:
[root@[192_168_15_244] root]# ping -c3 192.168.15.201
PING 192.168.15.201 (192.168.15.201): 56 data bytes
64 bytes from 192.168.15.201: seq=0 ttl=64 time=10.933 ms
64 bytes from 192.168.15.201: seq=1 ttl=64 time=1.151 ms
64 bytes from 192.168.15.201: seq=2 ttl=64 time=1.201 ms
--- 192.168.15.201 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 1.151/4.428/10.933 ms
I can't, at the moment, connect to the Internet.
But that is only because the PC I have the USB cable plugged into has packet forwarding disabled.
What is needed at the PC end of the cable is shown in /etc/hosts:
Code:
127.0.0.1 localhost.localdomain localhost kindle
192.168.15.200 usbnet-host-gw
I.E: The PC's address is *.201, the gateway address should be *.200
With that local-to-my-setup thing fixed, we do have a network connection from the 'diags' system while logged into the Kindle as the administrator: root.
That might be useful for serial jailbreaking, I will be giving that one some thought.