QUOTE(Leering @ Dec 28 2009, 10:17 PM)
Because it was a unique exploit? (IMG:
style_emoticons/default/blink.gif)
yeh, that's not really an answer.
either way, what it really comes down to:
1. Does the new dash prevent the exploit from running even when running on the old kernel? (this is probably why it doesnt work in it's current form)
if so- theres a reasonable chance that it would be a nearly impossible job to re-allow it by modifying the dash to do so.
or2. does XBR/Freeboot's own modifications to the dashboard prevent it
(doubt it.)
or3. does King Kong need to be changed in order for it to work again
(also doubt it.)
as you all should know, downgrading back to your original nand would allow you to run that KK exploit and boot xell from your dash, so this absolutely has to do with the dashboard you are running.
whether or not it is something that could be easily patched back in for support is what the question is, unless this is something that can be fixed through tweaking king kong itself, which again, is unlikely.
And I don't feel like editing this whole post over for this afterthought, but I just realized farmboynick said that he tried running it through the whole container situation off the hard drive, but has anyone tried running it off the disc as you originally had to? If it runs there, that would mean yes, it is possible.