5.3 Update for Paperwhite -- will it interfere with the jailbreak?

[qlob]

I signed up as well a year or two ago, and got nowhere.

[geekmaster]

Originally Posted by qlob

I signed up as well a year or two ago, and got nowhere.

I signed up too. No results. I only got involved in the UNOFFICIAL development BECAUSE they did not accept (or reject) my application to become an OFFICIAL developer.

By locking down their KDK to NOT include us, that very act encourages jailbreak development.

I have been an AUTHORIZED developer for many projects and companies. The ONLY applications that I applied for and did not get are Kindle and Skype. All others were approved.

In my opinion, it is the locked/restricted KDK that encourages jailbreak and sideloaded app development, more than anything else. If they provided an official path for our development efforts, we would not be in this dilemma.

[eureka]

KDK isn't an answer anyway. It's a sandbox. It's restrictive.

And jailbreak (or, more precisely, rooting) would be done even in case of freely accessible KDK and official way of KDK app sideloading. Just look at Android ecosystem (hint: Android SDK is freely accessible and any user can install .apk without problems).

Here is an official letter about rejecting of KDK request (and no, they don't apply mentioned strategy to firmware updates assembling):

Spoiler:

[qlob]

And I thought it was actually going to be a letter.......

[geekmaster]

Originally Posted by eureka

KDK isn't an answer anyway. It's a sandbox. It's restrictive. ...

If they won't let us play inside their sandbox according to their rules, then we will play outside it using the freedom to create our own rules and do things our own way, without all their silly restrictions. Personally, I think their KDK way is too far removed from the "bare metal" for my needs anyway...

[eureka]

Originally Posted by geekmaster

If they won't let us play inside their sandbox according to their rules, then we will play outside it using the freedome to create our own rules and do things our own way, without all their silly restrictions. Personally, I think their KDK way is too far removed from the "bare metal" for my needs anyway...

Wait, what? Successful applying for KDK doesn't take away a right (and urge) to "create our own rules ... without all their silly restrictions". You are contradicting yourself: even with your own [potential] official developer key and KDK, you're still wanting to do "bare metal" things... I guess, you'd still use jailbreak after receiving official KDK. It was my point.

[geekmaster]

Originally Posted by eureka

Wait, what? Successful applying for KDK doesn't take away a right (and urge) to "create our own rules ... without all their silly restrictions". You are contradicting yourself: even with your own [potential] official developer key and KDK, you're still wanting to do "bare metal" things... I guess, you'd still use jailbreak after receiving official KDK. It was my point.

No contradiction. I am saying that if they will not let us play by their restricted rules inside their KDK sandbox, then we will play by our unrestricted rules outside the sandbox, closer to the bare metal.

If I had a KDK, I may never have strayed outside it (toward the "bare metal"). My efforts would have gone into KDK development. I may never have bothered with a jailbreak, already having my own official developer key.

But NOT having a KDK, I was drawn toward "bare metal" (native mode) development, because it aligns more with my previous development experience and because being OUTSIDE the KDK, I can do it.

How is that a contradiction?

Anyway, arguing how things "would have been" is pointless, because amazon did not see fit to honor my KDK application.

[awh_tokyo]

Well, after my Kindle got updated to 5.3, I attached to the serial port and got into the boot loader.

I'm trying what I can find in the Debricking page, using a 5.3.0+JB firmware that I found. I'll let everyone know how it goes.

[awh_tokyo]

No dice :-( Flashed the 5.3.0 image with fastboot, and it boots, but it must rely on the JB already having been installed. Tried to downgrade to 5.2.0 but the system partition seems to be a damaged ext3 filesystem.

[dos1]

Originally Posted by awh_tokyo

No dice :-( Flashed the 5.3.0 image with fastboot, and it boots, but it must rely on the JB already having been installed. Tried to downgrade to 5.2.0 but the system partition seems to be a damaged ext3 filesystem.

If I were you I would just download official 5.3.0 image and unpack data.stgz from jailbreak manually, so there'll be less chance of flashing corrupted filesystem.

[qlob]

Originally Posted by awh_tokyo

No dice :-( Flashed the 5.3.0 image with fastboot, and it boots, but it must rely on the JB already having been installed. Tried to downgrade to 5.2.0 but the system partition seems to be a damaged ext3 filesystem.

I believe you can run the jailbreak from Diags, you just have to boot into diags with fastboot.

[knc1]

Originally Posted by awh_tokyo

No dice :-( Flashed the 5.3.0 image with fastboot, and it boots, but it must rely on the JB already having been installed. Tried to downgrade to 5.2.0 but the system partition seems to be a damaged ext3 filesystem.

Loop mount the file system image and fsck it before using it.
Tell us what fsck reports.
Also, what 5.2.0 image you are using.

[giorgio130]

Don't know about the paperwhite but with touch and k4 you can't flash the system partition using fastboot as it would get corrupted (flashed only partially). Maybe it's still the case...

[twobob]

Originally Posted by giorgio130

Don't know about the paperwhite but with touch and k4 you can't flash the system partition using fastboot as it would get corrupted (flashed only partially). Maybe it's still the case...

Ouch. that's an important and painful detail...

[qlob]

hmmmm. maybe flashing the KT's diags+ssh partition will work?