Kindle Touch/PW1/PW2 5.0.x - 5.4.4.2 JailBreak. Plus FW 5.x USBNetwork.

[jiacker]

Help!!!
My kindle paperwhite fireware is 5.3.1 and install:
kindle-jailbreak-1.14.N.zip-kindle-5.4-jailbreak.zip
Update_mkk-20141129-k5-ALL_install.bin
KUAL-v2.5
kual-helper-0.4.N
Update_usbnet_0.18.N_install_touch_pw.bin
update_combined-dev-certs-20121002_install.bin
when i want to install update_rescue_pack_20131220.bin, the update not success because it show "Unable to mount diags partition".
Does anybody told me how to install update_rescue_pack_20131220.bin ?

[NiLuJe]

That's... not good?

Unfortunately, probably hard to debug without checking things out manually over SSH.

Hopefully it's only a matter of the FS needing a fsck?

[NiLuJe]

That's... not good?

Unfortunately, probably hard to debug without checking things out manually over SSH.

Hopefully it's only a matter of the FS needing a fsck?

[knc1]

Hmm...
Does the device have a valid and working 'Diags' partition?

Let me put a strain on the old memory cells -
Ah, a PW - KTerm should work on that and perhaps be easier for the O.P. to use than ssh.

(although, with USBnet installed, ssh should be working)

[jiacker]

Did i open usbnet connect in ssh with wifi and update update_rescue_pack_20131220.bin to debug it?

Does the device have a valid and working 'Diags' partition?
how do i known this diags partition is working?

[knc1]

Originally Posted by jiacker

Did i open usbnet connect in ssh with wifi and update update_rescue_pack_20131220.bin to debug it?

NiLuJe will probably need to have you check a few things using the command line interface.

If you haven't setup ssh connection over the USB cable before, just using the kTerm application might be easier.

[jiacker]

Originally Posted by knc1

NiLuJe will probably need to have you check a few things using the command line interface.

how to check?
I connect ssh and come into
Welcome to Kindle!

#################################################
# N O T I C E * N O T I C E * N O T I C E #
#################################################
Rootfs is mounted read-only. Invoke mntroot rw to
switch back to a writable rootfs.
#################################################
[root@kindle /]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 348365 250010 80855 76% /
tmpfs 128096 60 128036 0% /dev
tmpfs 128096 0 128096 0% /dev/shm
tmpfs 32768 304 32464 1% /var
/dev/loop/2 216 216 0 100% /lib/firmware/cyttsp
/dev/loop/3 2536 2536 0 100% /usr/share/X11/xkb
/dev/loop/4 98612 98612 0 100% /usr/java/lib/fonts
/dev/loop/5 1280 1280 0 100% /etc/kdb.src
/dev/loop/6 8124 8124 0 100% /usr/lib/locale
/dev/loop/7 8936 8936 0 100% /usr/share/keyboard
/dev/mmcblk0p3 63461 14682 45503 24% /var/local
fsp 1392632 95536 1297096 7% /mnt/us
/dev/loop/0 1392632 95536 1297096 7% /mnt/base-us

-------------------------
My kindle brick a few days ago and I call other person to help me repaire it.I don't know how he debrick it.So i want to install update_rescue_pack_20131220.bin.May be i could repair it next time when it brick again.

[NiLuJe]

Maybe a fsck /dev/mmcblk0p2 would shed some more light on this?

Also check if /mnt/mmc exists while you're at it.

[jiacker]

Originally Posted by NiLuJe

Maybe a fsck /dev/mmcblk0p2 would shed some more light on this?

Also check if /mnt/mmc exists while you're at it.

[root@kindle /]# ls -al /mnt/mmc
drwxrwxr-x 2 root root 1024 Nov 30 2012 .
drwxrwxr-x 8 root root 1024 Nov 30 2012 ..
[root@kindle /]# fsck /dev/mmcblk0p2
fsck 1.41.10 (10-Feb-2009)
e2fsck 1.41.10 (10-Feb-2009)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p2

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

[root@kindle /]#

Is there something wrong with mmcblk0p2?

[knc1]

Originally Posted by jiacker

[root@kindle /]# ls -al /mnt/mmc
drwxrwxr-x 2 root root 1024 Nov 30 2012 .
drwxrwxr-x 8 root root 1024 Nov 30 2012 ..
[root@kindle /]# fsck /dev/mmcblk0p2
fsck 1.41.10 (10-Feb-2009)
e2fsck 1.41.10 (10-Feb-2009)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/mmcblk0p2

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

[root@kindle /]#

Is there something wrong with mmcblk0p2?

Impossible to say for certain.
The only thing that can be said is that the file system stored on it is unusable trash.

[jiacker]

And how can i fixed it, copy somebody‘s mmcblk0p2 to restore?

This is the first jailbreak kpw_jb_520-531.zip with 5.3.1 log before it bricked,is this affect the mmcblk0p2?

2013-01-24 15:30:00
This file contains the jailbreak log. You can safely delete this file.

23:29:11 PREPARING JAILBREAK
23:29:13 PREPARING JAILBREAK
23:29:13 Extracting files ...
23:29:14 OK
23:29:25 INSTALLING FILES
23:29:27 Mounting filesystem ...
23:29:30 OK
23:29:31 Installing updater certificate ...
23:29:33 OK
23:29:34 Installing Kindlet certificates ...
23:29:37 OK
23:29:38 Installing jailbreak bridge ...
23:29:41 OK
23:29:42 Installing rescue pack (main) ...
23:29:44 OK
23:29:45 Installing rescue pack (diags) ...
23:29:48 Backed up diags passwords to /etc/shadow.before_rescue_pack on diags partition
23:29:49 OK
23:29:51 CLEANING UP
23:29:53 Removing obsolete files ...
23:29:55 OK
23:29:56 JAILBREAK SUCCEEDED :-)

[knc1]

Originally Posted by jiacker

And how can i fixed it, copy somebody‘s mmcblk0p2 to restore?

- - - - -

Sort of.
You should be able to find recovery image's for the PW's Diags system among our debricking images.
See the "Where do I start?" sticky thread for leads/links to the old (pre-kubrick) recovery information.

- - - -

Nothing you did is likely to have trashed the file system itself -
Much more likely that you have failing hardware (the eMMC chip).
But the chip **might** be able to recover when you re-flash it.

[internal]

Right so im getting my Kindle PW2. Hopefully it will be on a fw <= 5.4.4.2.

Was wondering, if it is then can I manually upgrade to this said firmware then jailbreak?

If it isn't, then can I open up the device to JB or will I have to refund and hope for another?

Cheers
Inf

[knc1]

Originally Posted by internal

Right so im getting my Kindle PW2. Hopefully it will be on a fw <= 5.4.4.2.

Was wondering, if it is then can I manually upgrade to this said firmware then jailbreak?

If it isn't, then can I open up the device to JB or will I have to refund and hope for another?

Cheers
Inf

That "this said firmware" is a bit vague -
could you state which firmware by number please?

Also, this might help: https://www.mobileread.com/forums/sho...81&postcount=6

[internal]

Originally Posted by knc1

That "this said firmware" is a bit vague -
could you state which firmware by number please?

Also, this might help: https://www.mobileread.com/forums/sho...81&postcount=6

Its fine, i just got my new kindle, its on firmware 5.6.1.0.2. Ahh ow well.