View Single Post
Old 08-10-2017, 10:57 PM   #5
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by coplate View Post
but yeah, I realized you probably don't want to drop into linux... oh, will the diags kernal skip the first boot stuff, maybe. I lost my train of thought there, It doesnt make a lot of sense
It is a dual boot system, the mmcblk0p1 partition that is the home of the 'main' system isn't even mounted when running the 'diags' system.

/var/local (mmcblk0p3) is common to both systems.
/mnt/us (mmcblk0p4) is common to both systems.
But as a general rule, neither of those hold executable code.
(Both are 'user data' - /var/local is 'user action, generated data').

Dropping to a command line shell is a key step in the serial jail breaking thread.
So your way needs to work on all diags versions that do not have the old menu entry that is quoted in the current serial jail breaking thread.
OR
find an alternative.
mounting the 'main' system and dropping a tar bomb on it would fixup everything in a single step.
knc1 is offline   Reply With Quote