KPW2 - 5.6.1.0.6 - Rooting/Jailbreaking

[knc1]

Originally Posted by fctools

Yeah, as matter of fact I changed the serial # back to the one I posted before because the number changed and I was afraid of having someone else's.

1) The things you installed, where not installed where the serial number is stored - those actions did not change the serial number.

2) Any change to the serial number, must have been done by the "erase all" command.
I.E: It may have been wrong before (specially if you bought this unit used) and then was corrected by "erase all" - but now reset to the wrong one again by your own actions.

You should learn what the situation is, once you try to register the device with Amazon.

[fctools]

Originally Posted by knc1

2) Any change to the serial number, must have been done by the "erase all" command.
I.E: It may have been wrong before (specially if you bought this unit used) and then was corrected by "erase all" - but now reset to the wrong one again by your own actions.

I did buy it used on ebay w/5.6.0.1 on but it wasn't JB or or anything could it have the wrong ser from the factory? Should I erase it again & and reflash?

[fctools]

After I erased it, the ser # it had was the one I posted and the one I changed it back to after flashing. As far as I know the ser number did change after flashing. At least the hash of it did. I don't know what's going on.

[knc1]

Originally Posted by fctools

I did buy it used on ebay w/5.6.0.1 on but it wasn't JB or or anything could it have the wrong ser from the factory? Should I erase it again & and reflash?

The factory does not sell on e-bay.

You most likely got a re-furbished device.
And probably a black-listed one at that (the erase all command **should** have generated the correct serial number).

[fctools]

My version says now 5.4.0 and I don't intend to let it go higher therefore no syncing till I'm sure. The jailbreak is acting weird. I hit update and it updates and restarts the way any update would. I understand the way it's supposed to work the update screen doesn't even show it only says jailbreak.If I run jb.sh manually it says jailbreak but kual still doesn't work. Any suggestions?

[knc1]

The jailbreak for the Kindles **ONLY** affects the ability to install our update_*.bin packages.
It has **NOTHING** to do with the execution of applications.

- - - -

NOTE: I wrote of the jailbreak above.
The most recent versions of the jailbreak for series 5.x firmwares bundles **OTHER** things that do affect the execution of applications.

- - - -

Please tell us what error message (or unusual behavior) given when trying to run KUAL.
"Doesn't work" isn't very much to go on.

[fctools]

Originally Posted by knc1

Please tell us what error message (or unusual behavior) given when trying to run KUAL.
"Doesn't work" isn't very much to go on.

The selected application could not be started. Please try again.
Both 1 & 2 do this.

[NiLuJe]

If it's a 4GB PW2, it needs FW whats-its-face for Kindlets to work. Can't remember the version right now, it's in the KUAL FAQ.

[knc1]

Right!
So in that case, the answer now to the next question that will be posted:
https://www.mobileread.com/forums/sho...postcount=1301
(I just got my crystal ball to re-boot.)
Duh...
I just read my own reference - that example is the firmware version you need to make active documents work on a PW2. AFAIR.

[fctools]

Presto! your crystal ball was right, worked perfectly! Finally after many hoops and jumps I have a jailbroken kindle. I locked the back door and synced with amazon and re-downloaded my books everything seems to work. Many thanks guys, I couldn't have done it without you!

[knc1]

One of the few people who ever recovered from "erase all" - - -
Which means something has changed about its having been broken for years.

- - - -

Now if someone has a sacrificial PW2, we could probably investigate the details.
Hmm...
The "erase all" command should (well, was) part of the Amazon released u-boot sources, maybe a bit of code reading is called for before burning a PW2 to the gods of knowledge.

Hmm(2)...
If so, it probably got fixed when the USB downloader mode disappeared from the PW1 - - -
because with it fixed, they wouldn't need a 'magic key' sequence to enter USB downloader mode, they could just use u-boot (which is the way the firmware was intended to be used).

[hontehai]

Originally Posted by raz572

Update 5

Here's what I did after logging in:

mount /dev/mmcblk0p1 /mnt/mmc
cd /mnt/mmc

echo 'raz572::0:0:raz572:/tmp/root:/bin/sh' >>etc/passwd
echo 'raz572:*:15826:0:99999:7:::' >>etc/shadow
echo 'raz572:*:15826:0:99999:7:::' >>etc/shadow-

cat etc/passwd
cat etc/shadow
cat etc/shadow-

Then, I restarted (power button on the bottom). Once booting finished, I did a whoami. It shows me as root. I did an 'exit' and logged in as raz572. I'm root again, in standard mode.

Success! It looks like I'm root in standard mode, so I think we're good to go for jailbreaking.

Could you explain detail ?
Ex: user hontehai and new password hontehai1

[fctools]

I didn't quite get it either whether this step is actually essential but I was able to skip it. Maybe I missed something but once you log in as root in diags mode you can do as you please, wounded feet notwithstanding

[eschwartz]

It does not matter what username you are logged in as, what matters is being able to run the jailbreak scripts with root permissions.

[NiLuJe]

I'd go so far as to add that renaming the root account is a terrible idea on principle .