Awesome, keep up the good work .......cj_000 wrote:We have yet to release the root process - currently looking for another way in that we can share, so when it's patched, we can have another way in.
No, a bootloader exploit would have been awesome, but like its predecessors the kernel is encrypted, with the crypto being handled in hardware. Our best bet for unsigned kernels is yet again kexec but it can be quite the pain getting that to run on ARM devies.wizziwig wrote:I would hold off on releasing the root until the firmware is much more stable and bug free. No sense letting them patch the exploit before we have a firmware we're ready to live with for a while (in case we can't get more updates without losing root). At the very least they need to fix 5.1 audio playback of local files - the last firmware only fixed netflix and cable-box passthrough.
I'm curious if your exploit allows full bootloader control so we could remove android entirely and boot up a regular Linux distro to install XBMC, etc.? Assuming drivers were properly ported, etc. If not a full Linux, maybe at least allow NDK apps in Android? From what I can see, the old NDK work-around in the Wiki only applied to the x86 Revue and not these newer Arm units.
Is it not possible to statically link the required Arm libraries similar to what was done with the x86 libs to get NDK on the Revue? I know there are a few devices out there based on Marvell Armada 1000 that run regular Android. Products like these:cj_000 wrote: We have been playing with getting arm based android apps running on the Sony (vizio applies here, it's the same SOC) but most of the boxes libraries would need to be changed, which makes Google TV not work anymore. I suppose if we had some way to selectively control which libraries are used on the fly it'd be great, but actually going about that is another story.
Users browsing this forum: Bing [Bot] and 3 guests