KOA2 KOA2 jail break research

[coplate]

For everyone interested, here is another way to skip wifi setup.

When you get to the language screen, you can touch and hold "american english" ( probably the other languages too? ), for a bout 10 seconds, until the 'Next" button changes to "Next..." ( note the "..." part ).


I did not discover this, but I cannot re-find the page I learned it on, credit to whomever really found it.

[knc1]

There are now "Beta" (test grade) KOA2 packages of some of the basic things created.

I will post them sometime tonight (when the other stuff arrives to where I am uploading it).

Oh, Phooey!
I forgot to re-package kTerm.
Will have to get that one also, later, much later.

[knc1]

The KOA2 jail break instructions now being tested have also been converted from forum BBCode to MarkDown and copied to the "README.md" file of the repository.
Which makes them show on the landing page in an almost readable version (line break handling is messed up - but anyway ...).
https://github.com/knc1/KOA2_Jailbreak

Edit:
Just found the cause, my text editor is set to strip trailing spaces, and a markdown line break is two trailing spaces.
Will have that fixed up with the next version posted.

Those directions are changing multiple times per day.
github members can receive notification of when the files are changed by selecting to "watch" the repository.

github membership is free.
Just in case you want to join so that you can be notified of updates to the directions.

That is unlike this forum, which does not send notifications on edit changes to a post.

[j.p.s]

Originally Posted by knc1

Edit:
Just found the cause, my text editor is set to strip trailing spaces, and a markdown line break is two trailing spaces.

Have you tried asciidoc and decided markdown is better for you?

If not, you might want to give asciidoc a whirl.

[knc1]

Originally Posted by j.p.s

Have you tried asciidoc and decided markdown is better for you?

If not, you might want to give asciidoc a whirl.

GitHub uses markdown as the their "standard" markup language.
Get (no pun intended) them to change their "standard" markup language and then I can change what format the "README" document is written in.

After all, the overall intent was to get it to show on the landing page of the repository.

[j.p.s]

Originally Posted by knc1

GitHub uses markdown as the their "standard" markup language.
Get (no pun intended) them to change their "standard" markup language and then I can change what format the "README" document is written in.

After all, the overall intent was to get it to show on the landing page of the repository.

Have you seen this, from January 2013 ?

http://asciidoctor.org/news/2013/01/...rns-to-github/

[knc1]

Originally Posted by j.p.s

Have you seen this, from January 2013 ?

http://asciidoctor.org/news/2013/01/...rns-to-github/

You are still missing the point.

This forum generates markdown when it mails you a PM notification and github accepts markdown.
All I have to do is fixup the trailing spaces, not use pandoc to do a forum BBCode to asciidoc conversion.

We are developing a jail break here, not a new documentation work flow.

[j.p.s]

Originally Posted by knc1

You are still missing the point.

This forum generates markdown when it mails you a PM notification and github accepts markdown.
All I have to do is fixup the trailing spaces, not use pandoc to do a forum BBCode to asciidoc conversion.

We are developing a jail break here, not a new documentation work flow.

I was unable to read that between the lines. Sorry for the distraction.

[knc1]

Originally Posted by j.p.s

I was unable to read that between the lines. Sorry for the distraction.

Not a problem.
In fact, the exchange lead me to making a change in my documentation workflow.

The files in the public repository will be changing today as a result.

I will be using LyX as the documentation preparation tool. So the *.lyx file will be the actual, master, document.
In addition to its usual print formats, there will be a *.tex (LaTex) file version to use as an intermediary.

The *.tex intermediary plus pandoc will allow the generation of our mediawiki format (for our wiki), the specific flavor of markdown that github uses (for the github viewables), and as a special favor to j.p.s., asciidoc.

Support for a BBCode version (used in this forum) will not be supported.

All-in-all an actual simplification and time savings to support the unpublished documentation.
It will probably be easier for other sites to use also (subject to the included license).

[knc1]

After a ten hour editing session, the change has been made.
The best of the bunch is the *.pdf file version (you will have to download it - github's pdf viewer is not worth shit).

I haven't tested the medawiki format file on our wiki yet - it might or might not have to tweaked by hand.
(I had to tweak the markdown format file by hand a bit also.)

Comments please.

Originally Posted by knc1

Not a problem.
In fact, the exchange lead me to making a change in my documentation workflow.

The files in the public repository will be changing today as a result.

I will be using LyX as the documentation preparation tool. So the *.lyx file will be the actual, master, document.
In addition to its usual print formats, there will be a *.tex (LaTex) file version to use as an intermediary.

The *.tex intermediary plus pandoc will allow the generation of our mediawiki format (for our wiki), the specific flavor of markdown that github uses (for the github viewables), and as a special favor to j.p.s., asciidoc.

Support for a BBCode version (used in this forum) will not be supported.

All-in-all an actual simplification and time savings to support the unpublished documentation.
It will probably be easier for other sites to use also (subject to the included license).

[AcidWeb]

Point 4 of "Check current firmware". If JB was installed successfully it should point to "Install the Jailbreak Survial Code" not "Install Device Jail Break".

[knc1]

Originally Posted by AcidWeb

Point 4 of "Check current firmware". If JB was installed successfully it should point to "Install the Jailbreak Survial Code" not "Install Device Jail Break".

Thanks.

[knc1]

Originally Posted by AcidWeb

Point 4 of "Check current firmware". If JB was installed successfully it should point to "Install the Jailbreak Survial Code" not "Install Device Jail Break".

I edited the *.md document versions by hand this morning - while still awake.

Today I return to determining the new partition layout details.
We need that, since some of our add-ins make direct access to the partitioned filesystems.

[coplate]

Just notes,

for a variety of reasons I am positive that adb or fastboot is built into these devices, and we just need to figure out how to turn it on.

[Vamp12]

Hello. I have a KOA2 running a 5.9.2.0.1 FW it's a 32gb + 3g model. I had some battery problems, and amazon kindly sent me a replacement and they blacklisted the first one. From what I read, it isn't possible to jailbreak it yet. I was wondering if someone is working on that jailbreak and if I can be of any help?