5.6.5 Jailbreak (closed-kindle) -- released! - Page 69

Belenos · 05-14-2016, 05:20 PM

Quote:

Originally Posted by Branch Delay

jailbreak was originally developed on a PW2. Worked fine for lots of people. the method of executing it has drastically changed from what I developed, hence, there could be bugs. Run my original instructions if things aren't working (i.e. the menu text never changes)

Oh well, the JailBreak-1.14.N-FW-5.x-hotfix worked for me

geekmaster · 05-14-2016, 05:30 PM

I will try the original method. A downgrade requires really old firmware (which I do not have).

I cannot find (at the moment) my big box-o-devkits (with bus pirates and serial adapters and such) -- a side effect of spring cleaning, I am afraid (where stuff not used recently gets "put away"). I hope the original method works so I do not need to keep hunting for missing hardware tools.

Though I suppose I could do a little proxy app to make a kindle into a usb serial adapter SSH into the kindle, then run another terminal app that talks to its serial port which is wired to the target kindle serial port. A lot of us have more than one kindle, or would likely wouldn't be here in this forum, eh?

But I prefer the USB-only methods when available.

Belenos · 05-14-2016, 05:38 PM

Quote:

Originally Posted by geekmaster

I will try the original method. A downgrade requires really old firmware (which I do not have).
.

Check these two links
https://www.mobileread.com/forums/sho...&postcount=994

geekmaster · 05-14-2016, 06:31 PM

Crap! is the F-word appropriate here? The ORIGINAL instructions say to go to a website after copying the jb files to the kindle, so I turned off airplane mode and I had just connected my PW2 to my wi-fi network, when I got a phone call. When I got off the phone call, my PW2 said "Your Kindle has been Updated!". It is no longer on FW 5.6.5. It is on FW 5.7.4.

What now? Grr... F-F-F!

EDIT: I tried copying the 5.4.2 firmware from ixtab's website onto my PW2 userstore, and with USB cable still attached I did a hard reset. It looked promising, firmware installing, but it ended up failing with "UPDATE ERROR: 12", which I suppose means it prevented a "firmware downgrade attack", eh?

doctorfrog · 05-14-2016, 06:50 PM

To start with this post, I want to first say thanks to those who volunteer their time to helping dopes like me who get things tangled up. I have a fairly thick skin and will not be upset overmuch if I don't get a whole heck of a lot of help with this. But please update the OP with the warning "DO NOT EVER FACTORY RESET YOUR DEVICE."

I have a Kindle Touch purchased from Amazon in December. Model is MP63GW, which I think you guys here call a KV? Up until recently I had it in Airplane mode at all times, having first de-registered it. I recently Jailbroke it, because I can't resist tinkering with things, and registered it.

And I realized how much I hate ads. So much. I realize such a sentiment is scoffed at here (partly out of a deference to Amazon that is in some ways understandable), but I wanted to be rid of them immediately. So I deregistered.

And I got an unsettling message next time I rebooted, something about this Kindle not being a test device any more? Confusing. And I was still getting ads. So I factory reset it. Yeah, not bright. I realize now that wasn't the thing to do.

So I'm pretty lucky that my Kindle still works for the basic reading tasks I only ever wanted it to do in the first place. (I sideload with Calibre.)

Except for one thing. Books that are loaded as MOBI don't work properly. I can view them and all that, but if I switch from one MOBI book to another, I lose my place in the previous book. If I load the book, it skips all the way to the beginning of the book, reading as "1%" in the lower right. If I swipe forward, then back, I can usually get my place back, but otherwise end up at the cover.

This behavior does not happen with AZW books or when switching between AZW and MOBI files.

I reapplied the Jailbreak and Hotfix, and appear to have done so successfully, but this behavior persists.

If it's possible to help me restore the original functionality, that'd be great, but otherwise, I guess my idiotic mistakes can be held up as some sort of warning to others. In the meantime, I'll be converting books to AZW and hope that nothing else breaks.

NiLuJe · 05-14-2016, 07:26 PM

@doctorfrog: First, properly ID your device via the Wiki.

And checking what actual FW version it's running might be helpful, too.

(Because a Touch doesn't run FW 5.6.5, so, you'd be in the wrong thread).

EDIT: As for your actual issue, barring FW >= 5.6.x shenanigans, make sure the date/time is properly set on your device. We eithe have a KUAL button for that somewhere, or there's a searchbar command to do it (the details should pop up with a quick search).

doctorfrog · 05-14-2016, 09:13 PM

Quote:

Originally Posted by NiLuJe

@doctorfrog: First, properly ID your device via the Wiki.

And checking what actual FW version it's running might be helpful, too.

(Because a Touch doesn't run FW 5.6.5, so, you'd be in the wrong thread).

EDIT: As for your actual issue, barring FW >= 5.6.x shenanigans, make sure the date/time is properly set on your device. We eithe have a KUAL button for that somewhere, or there's a searchbar command to do it (the details should pop up with a quick search).

Thanks. I actually didn't have the device jailbroken for long before I started futzing with it, so I haven't install KUAL yet. I guess that's what I get for being impatient. I'll make that my next step.

Per the Wiki and Device Info, this is a Kindle Basic 2014 running 5.6.5.

NiLuJe · 05-14-2016, 09:50 PM

@doctorfrog: Okay, then first and foremost, re-install the JB hotfix to make sure everything is back in order after your factory reset.

Then, yeah, double-check the date/time, because my other "fix" for those kind of weird issues was "do a factory reset", but you've already done that

.

knc1 · 05-14-2016, 09:55 PM

Quote:

Originally Posted by doctorfrog

Thanks. I actually didn't have the device jailbroken for long before I started futzing with it, so I haven't install KUAL yet. I guess that's what I get for being impatient. I'll make that my next step.

Per the Wiki and Device Info, this is a Kindle Basic 2014 running 5.6.5.

Not possible.
The 2014 runs series 4.x firmware.

But if you skipped a year due to lack of interest, actually meant 2015 (its 2016 now), then you mean a KT-2
my bad, that is what the wiki table says.
and my initial thread on the KT-2 is dated Nov. 2014
(I couldn't have written about it, if I didn't have it then

)

geekmaster · 05-14-2016, 10:15 PM

On my PW2 with FW 5.7.4, I just tried the JB in the first post. It display a web page with a bunch of smileys, and then after about a 7 second delay (just as with FW 5.6.5) it gave a popup saying "application error" just as before.

It seems that there could still be a vulnerability in there, if it could be expoited...

knc1 · 05-14-2016, 10:20 PM

Does:
;fc-cache
work on that firmware version?

geekmaster · 05-14-2016, 10:42 PM

Quote:

Originally Posted by knc1

Does:
;fc-cache
work on that firmware version?

It did not act like it did anything. I did not do a factory reset before the JB, so maybe that made it not work. Trying the JB again on the newest firmware -- it acts like it is TRYING to execute some code... Perhaps that heap spray needs a different value (address?)...

Doing a factory reset now. Will try it again (on FW 5.7.4). It "feels" like there could still be a vulnerability hiding in this method...

EDIT: No, it still kicks up an application error "The selected application could not be started. Please try again."

NiLuJe · 05-14-2016, 10:52 PM

They killed ;fc-cache, as I recall. (Like the last time, they took the easy workaround).

geekmaster · 05-14-2016, 10:56 PM

https://cansecwest.com/slides/2015/L...ecWest2015.pdf

Branch Delay · 05-14-2016, 10:57 PM

I assume they fixed the actual crash on 5.7.x. What you're seeing is probably the OOM killer taking down the browser after too much memory is allocated. Easy to check via dmesg.

;fc-cache was just a trick for mntroot. easy to work around, probably could find something else in a few hours. not critical

05-14-2016, 05:30 PM	#1022
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	I will try the original method. A downgrade requires really old firmware (which I do not have). I cannot find (at the moment) my big box-o-devkits (with bus pirates and serial adapters and such) -- a side effect of spring cleaning, I am afraid (where stuff not used recently gets "put away"). I hope the original method works so I do not need to keep hunting for missing hardware tools. Though I suppose I could do a little proxy app to make a kindle into a usb serial adapter SSH into the kindle, then run another terminal app that talks to its serial port which is wired to the target kindle serial port. A lot of us have more than one kindle, or would likely wouldn't be here in this forum, eh? But I prefer the USB-only methods when available. Last edited by geekmaster; 05-14-2016 at 05:33 PM.

05-14-2016, 06:31 PM	#1024
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	Crap! is the F-word appropriate here? The ORIGINAL instructions say to go to a website after copying the jb files to the kindle, so I turned off airplane mode and I had just connected my PW2 to my wi-fi network, when I got a phone call. When I got off the phone call, my PW2 said "Your Kindle has been Updated!". It is no longer on FW 5.6.5. It is on FW 5.7.4. What now? Grr... F-F-F! EDIT: I tried copying the 5.4.2 firmware from ixtab's website onto my PW2 userstore, and with USB cable still attached I did a hard reset. It looked promising, firmware installing, but it ended up failing with "UPDATE ERROR: 12", which I suppose means it prevented a "firmware downgrade attack", eh? Last edited by geekmaster; 05-14-2016 at 07:15 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
KINDLE DEAL: Released: A Story of God’s Power Released in Pro Baseball ($	gospelebooks	Deals and Resources (No Self-Promotion or Affiliate Links)	0	07-14-2011 09:12 PM
iPad iPad jailbreak released	scottjl	Apple Devices	25	05-08-2010 02:20 PM

05-14-2016, 06:50 PM	#1025
doctorfrog Junior Member Posts: 7 Karma: 10 Join Date: Jan 2013 Device: Kindle Basic 2014	To start with this post, I want to first say thanks to those who volunteer their time to helping dopes like me who get things tangled up. I have a fairly thick skin and will not be upset overmuch if I don't get a whole heck of a lot of help with this. But please update the OP with the warning "DO NOT EVER FACTORY RESET YOUR DEVICE." I have a Kindle Touch purchased from Amazon in December. Model is MP63GW, which I think you guys here call a KV? Up until recently I had it in Airplane mode at all times, having first de-registered it. I recently Jailbroke it, because I can't resist tinkering with things, and registered it. And I realized how much I hate ads. So much. I realize such a sentiment is scoffed at here (partly out of a deference to Amazon that is in some ways understandable), but I wanted to be rid of them immediately. So I deregistered. And I got an unsettling message next time I rebooted, something about this Kindle not being a test device any more? Confusing. And I was still getting ads. So I factory reset it. Yeah, not bright. I realize now that wasn't the thing to do. So I'm pretty lucky that my Kindle still works for the basic reading tasks I only ever wanted it to do in the first place. (I sideload with Calibre.) Except for one thing. Books that are loaded as MOBI don't work properly. I can view them and all that, but if I switch from one MOBI book to another, I lose my place in the previous book. If I load the book, it skips all the way to the beginning of the book, reading as "1%" in the lower right. If I swipe forward, then back, I can usually get my place back, but otherwise end up at the cover. This behavior does not happen with AZW books or when switching between AZW and MOBI files. I reapplied the Jailbreak and Hotfix, and appear to have done so successfully, but this behavior persists. If it's possible to help me restore the original functionality, that'd be great, but otherwise, I guess my idiotic mistakes can be held up as some sort of warning to others. In the meantime, I'll be converting books to AZW and hope that nothing else breaks.

05-14-2016, 07:26 PM	#1026
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@doctorfrog: First, properly ID your device via the Wiki. And checking what actual FW version it's running might be helpful, too. (Because a Touch doesn't run FW 5.6.5, so, you'd be in the wrong thread). EDIT: As for your actual issue, barring FW >= 5.6.x shenanigans, make sure the date/time is properly set on your device. We eithe have a KUAL button for that somewhere, or there's a searchbar command to do it (the details should pop up with a quick search).

05-14-2016, 09:50 PM	#1028
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@doctorfrog: Okay, then first and foremost, re-install the JB hotfix to make sure everything is back in order after your factory reset. Then, yeah, double-check the date/time, because my other "fix" for those kind of weird issues was "do a factory reset", but you've already done that .

05-14-2016, 10:15 PM	#1030
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	On my PW2 with FW 5.7.4, I just tried the JB in the first post. It display a web page with a bunch of smileys, and then after about a 7 second delay (just as with FW 5.6.5) it gave a popup saying "application error" just as before. It seems that there could still be a vulnerability in there, if it could be expoited...

05-14-2016, 10:20 PM	#1031
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	Does: ;fc-cache work on that firmware version?

05-14-2016, 10:52 PM	#1033
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	They killed ;fc-cache, as I recall. (Like the last time, they took the easy workaround).

05-14-2016, 10:56 PM	#1034
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	https://cansecwest.com/slides/2015/L...ecWest2015.pdf

05-14-2016, 10:57 PM	#1035
Branch Delay Connoisseur Posts: 95 Karma: 1699999 Join Date: Aug 2015 Device: Voyage	I assume they fixed the actual crash on 5.7.x. What you're seeing is probably the OOM killer taking down the browser after too much memory is allocated. Easy to check via dmesg. ;fc-cache was just a trick for mntroot. easy to work around, probably could find something else in a few hours. not critical