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

[NiLuJe]

Of note for the new 4GB PW2 owners: 5.4.5 is out. Haven't had time to look at it yet, it may be terribly evil, or not. Stay tuned.

[afterbox]

@eschwartz

No, no Kterm here. KUAL isn't compatible with my device yet (thanks to Amazon's less than comprehensive firmware...) so I am using SSH. The thought of a subshell had indeed crossed my mind, I just couldn't think of a way around it. Will try to source it now...

[afterbox]

Originally Posted by NiLuJe

Of note for the new 4GB PW2 owners: 5.4.5 is out. Haven't had time to look at it yet, it may be terribly evil, or not. Stay tuned.

Oooo! A firmware update! Should I poke it with a stick and upgrade? Or should I wait for you? What's the worst that could happen...

Will.

[knc1]

Originally Posted by williamrochira

exec /mnt/us/esys/bin/busybox ash
# # # # <- never reached by **prior** shell and not passed to new.
But echo $PATH returns:

/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin:/usr/local/python/bin

So the export PATH=/mnt/us/esys/bin:/mnt/us/esys/usr/bin:$PATH didn't work...

The exec shell function does not pass the current command file and the current point of execution in it.

Ah, well, at least the Busybox version 1.17 (or whatever) ash that Amazon uses doesn't.

Hmm...
Maybe passing the new version of ash some argument(s) or option(s) might work.
As in:
exec /mnt/us/esys/bin/busybox ash -l
(-l, "ell" for "login shell" ? - - maybe)

- - - -

Thanks everyone for the help here.

[NiLuJe]

I need to check if it's JB friendly or not .

----

@knc1: env PATH=... exec blah ?

(Yeah, I like env ;D).

[knc1]

Originally Posted by NiLuJe

I need to check if it's JB friendly or not .

----

@knc1: env PATH=... exec blah ?

(Yeah, I like env ;D ).

Maybe - at least it would in Bash.

This function **should** be (and is in some OSs) named "chain".
It should just be replacing the current code and data sections of the program executing with that of the program executed.
I.E: Same environment, same open file descriptors (the current command file should be open on fd #3 or on fd #5), same-same everything else.

But this is an old version of Busybox ash -
All we can do is mess with it until we figure out how it **actually** works.

[afterbox]

Okay, I've gotten it to work.

In my .profile, I have:

source path.sh
cd /mnt/us
exec esys/bin/busybox ash

An in '/tmp/root/path.sh':

export PATH="/mnt/us/esys/bin:/mnt/us/esys/usr/bin:$PATH"

Works for me :-)

[eschwartz]

You might want to move HOME to [userstore] or something.... or it will magically delete itself from tmp every time your Kindle reboots!

[afterbox]

Originally Posted by eschwartz

You might want to move HOME to [userstore] or something.... or it will magically delete itself from tmp every time your Kindle reboots!

Already done ;-)

[NiLuJe]

Haven't checked if the JB still applies on vanilla 5.4.5, but did confirm that it should survive an update, so you're free to check if it helps, @williamrochira .

[afterbox]

[deleted]

[afterbox]

Updated, but ';un' still sends it into USB Drive Mode, so I think it killed the jailbreak. :-(

Edit: "Update Your Kindle" isn't greyed out when I copy over the JB files. Should I re-jailbreak?

[NiLuJe]

@williamrochira: Note that the usual caveats apply (namely, it kills everything that had a foothold in the rootfs, except the JB itself).

So, just reinstall the hacks (MKK, USBnet, ...). That said, I'd be glad to know if you can indeed reinstall the JB itself, even if that shouldn't be needed.

[afterbox]

@NiLuJe

Installing jailbreak now. Happy to be your guinea pig ;-)

[NiLuJe]

FWIW, the update package itself has hopeful hints of awareness of new models (which is new, for a recovery PW2 update, BTW).