Tutorial LanguageBreak - Software Jailbreak for (probably) any Kindle <=

[QBit99]

Originally Posted by mergen3107

No, not yet. The linked PR that NiLuJe gave you hasn’t been merged yet (it’s color on GitHub will turn purple). And only then we need to wait more until new nightly is rolled out.

Nightly will have at least 10-3 in the name.

Okaay. Thx 4 the info

[mergen3107]

@jospalau
I think you should extract contents of LanguageBreak folder only, not the whole tarball.

[Mike Li]

Originally Posted by QBit99

Has anybody tried the one-click method?

Yes I have. At first, I got stuck in step seven and didn't restart. After multiple attempts, I got stuck in step five. It is still possible to load the store page.

[Yellow22]

Originally Posted by reminon

On 5.16.1 with my scribe. Initially ran the jailbreak. after following all of the steps and installing the hotfix, it left me in a pseudo demo mode, where it looked like normal mode but still in chinese, had me setup my device as thats all i could do. After setting up my device it left me with wifi connected, but unable to disable wifi or enable airplane mode. I had to keep fighting with it downloading updates ever couple of minutes. Eventually I saw your update the the jailbreak. I entered demo mode again and followed the jailbreak instructions a second time. This left me at an english setup screen . After setting up my device again, everything looks normal and enabled airplane mode.

When I boot my kindle it shows bridge+ while booting, but when I enter ;log mrpi "I have the files for mrpi and kual coplate copied over" nothing happens it just searches for the term instead of loading mrpi and installing kual. I fell I am missing something. any ideas?

Hi.

I have a kindle Scribe on 5.16.2, with serial ---23M---.

All the steps instructed by Marek can be performed successfully, except that just before installing hotfix, it appears a "Collecting Debug Info" window. Even though, hotfix can be installed and there is a "mkk" folder in kindle.

However, I fail to install MR installer and KUAL, and ";log mrpi" cannot be executed.

Would you please give me some advice?
Thanks.

[mergen3107]

Try multiples restarts after JB and after hotfix. Make sure Wi-Fi is off to avoid FW update.

[jospalau]

Originally Posted by mergen3107

@jospalau
I think you should extract contents of LanguageBreak folder only, not the whole tarball.

Little detail

Many thanks!

[Yellow22]

Originally Posted by mergen3107

Try multiples restarts after JB and after hotfix. Make sure Wi-Fi is off to avoid FW update.

Thanks very much for your response.

I have tried three restarts, and every time there was "BRIDGE+" in the boot screen. And ;log runme failed to execute.

So, it seems that the problem lies in the "BRIDGE+" issue. Would you please give me some advice on how to solve it? Thanks!

[Yellow22]

Originally Posted by Marek

If you are already registered do ;enter_demo reboot setup demo without wifi like normal go to ;demo menu and resell device

Hi, Marek. Sorry to bother you.

I have a kindle Scribe on 5.16.2, with serial ---23M---.

I performed your instructions successfully, except that just before installing update_hotfix_languagebreak, it appeared a "Collecting Debug Info" window. Even though, update_hotfix_languagebreak was installed successfully and there is a "mkk" folder in kindle.

But every time there is "BRIDGE+" in the boot screen. And ;log runme produced nothing. The reason may be that, when I jailbeaked my Scribe first time, I copied the old LanguangeBreak file(version 1.0.1).

Would you please tell me how to solve the "BRIDGE+" issue?

Many thanks.

[Marek]

Originally Posted by Yellow22

Hi, Marek. Sorry to bother you.

I have a kindle Scribe on 5.16.2, with serial ---23M---.

I performed your instructions successfully, except that just before installing update_hotfix_languagebreak, it appeared a "Collecting Debug Info" window. Even though, update_hotfix_languagebreak was installed successfully and there is a "mkk" folder in kindle.

But every time there is "BRIDGE+" in the boot screen. And ;log runme produced nothing. The reason may be that, when I jailbeaked my Scribe first time, I copied the old LanguangeBreak file(version 1.0.1).

Would you please tell me how to solve the "BRIDGE+" issue?

Many thanks.

Install the hotfix from niluje's snapshot thread

[Yellow22]

Originally Posted by Marek

Install the hotfix from niluje's snapshot thread

It works. My Scribe is finally jailbreaked.

Your help is greatly appreciated, Marek.

Enjoy 10 cups of coffee

[Alessio]

Originally Posted by Marek

try the latest hotfix in Niluje's snapshot thread

I've just tried it (the "Update_jailbreak_hotfix_1.16.N_install.bin") and my Kindle shows an Update Failed message. Then, it restarts, and shows the BRIDGE message again.

Is this not working because Amazon has updated my Kindle to 5.16.3.1?

[NiLuJe]

@Alessio: Depending on when exactly it updated, possibly.

Try the emergency approach described in #200.

----

EDIT: More importantly, stuff is probably broken on >= 5.16.3 regardless, so, err, don't bother for now, maybe?

[jospalau]

I factory reset the device setting an empty DO_FACTORY_RESTORE file because it was managed and no more JAILBREAK message starting. Is any way to fix it?

I ran ;log runme after renaming jb to RUNME.sh but I get UPDATE ERROR 12

After a few tries, it seems to run properly reading the log languagebreak_log but no message and ;log mrpi doesn't seem to install anything I copy in the foldr mrpackages

Sent from my 22081212UG using Tapatalk

[CitizenStile]

This is probably not the right place to ask, but as someone who successfully jailbroke their PW5SE on 5.16.2.1 what is the best way to verify that the "Rename OTA binaries" and "PREVENT OTA Updates" are functioning correctly while I'm on wifi? when I check /mnt/base-us I see that there is a folder called update.bin.tmp.partial and that it is empty... I'm assuming the fact that it has not been deleted and re-created as a file means that things are good?

[mergen3107]

RenameOTAbins you can check in /usr/bin. Look if the renaming has actually happened, as detailed in the .sh script in the /mnt/us/extensions/renameotabins/bin.

The second one I am not sure it still works effectively, I think people still do it as a habit