View Single Post
Old 11-23-2017, 12:20 PM   #23
coplate
Guru
coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.
 
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
Quote:
Originally Posted by coplate View Post
I assume thet have command line access, since they can remove that file.

Have him try this:
Code:
mntroot rw
echo "Bundle: FB02" > /etc/bundle_type.txt
touch /PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC
mntroot ro
And then try it again.

I don;t know if it will work, but it is the last thing I can think of.

I just took the time to try this, and it did not work for me, but I will need to try one more time, because you have to reboot for PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC to take effect.

It still did not work, so it looks like they have closed this loophole completely.

I forked kindletool again in order to add the SP01 header to the new Kindle Oasis 2017, but it didnt work either. The 'full image' recovery system must not be allowed to use our jailbreak security key, even though regular patches can. Or something more confusing.

Last edited by coplate; 11-23-2017 at 12:50 PM.
coplate is offline   Reply With Quote