Hey guys,
I wanted to give you an update, I managed to root the device and inspect / reverse engineer the stuff that is going on there. I'm currently trying to port autosign for Linux, so that you can ship ROMs with your own update.zip on SD card, which eases up installation pretty much. The recovery mod seems to be a fork of TWRP, right? Is it open source? Are the OEM keys for ZTE available? I tried to reverse-engineer the update.zip files, but it seems as you guys are distributing your own MAR files which I have no idea of how to reverse-engineer them (with POST-dependent XML hashed APIs etc ... wtf). The keys are a blocker atm, the partitions of the recovery.img are pretty fucked up and in no way compliant to the usual Android magic. Really hard to reverse engineer what they do there. (Off Topic: I guess ZTE Open C was the worst name for the application of Google Fu as it always ignores the C, even with "Open C" as a keyword -.-, I would suggest renaming the next device with ZTE OpenThree or similar. Also they should consider not limiting downloads to 30kB/s as I had to try the download of the firmware 7 times before it didn't cancel. Their webserver has also no range-support... ) 1. The device is now rooted, everything you need to have is hosted here - also the self-packaged rooted Android 4.4.2 variant with the ZTE-OEM kernel, see the README.md on how to root it: (The flashing tool still needs Windows, which sucks hard - so I would prefer the update.zip method for initial rooting as I'm a Ubuntu dev/shadow) https://github.com/martensms/zte-openc-rootkit I'm still pushing the files, so it might take a while until the commits appear (1.8GB ...). 2. I have never built anything but gaia, as I can't get through the config.sh call. Gaia itself was built successfully and flashed after the rooting process. As the master variant depends on the new Gecko API, I guess I have to built everything from scratch (navigator.mozInputMethod.removeFocus() seems to be not existing in the OEM Gecko variant, so all select fields are broken :P). 3. I couldn't fix the xml file myself. How can I fix the repo url? The problem is - as I never built anything yet - I have no idea where the repository has to be cloned to. Should it land in external/tinyxml2 or platform/external/tinyxml2? It's superconfusing, I have really no idea how to overwrite it correctly as the platform/external/tinyxml2 is listed nowhere as a remote inside the base-caf-jb.xml. Please help. Cheers all, ~CM On Sat, Jun 7, 2014 at 5:56 PM, Julien Wajsberg <[email protected]> wrote: > Le 07/06/2014 15:36, Adrian Custer a écrit : > > >> The biggest challenge for me is that the Firefox OS free software >> *project* does not exist. Right now Mozilla has all its developers working >> in little teams each doing great work on their piece of the puzzle. >> However, there is no real, effective, communicating leadership to which the >> core issues can be brought and who could provide a plan to resolve all the >> technical debt. Critically for us outsiders, the insiders do not have it as >> part of their work to build the community and pull us in. Individually they >> are each willing to help and enthusiastic but structurally this has not >> been stated as part of their responsibilities so the project is not forming >> as an effective collaboration of outsiders and Mozilla. >> > > Yes, this is sadly true. Thanks for saying it in such a clear way :) > > That said, it should be easier to contribute in a specific application (as > opposed to the underlying system bits). > > Even if the documentation improved a lot (thanks to the huge work of Chris > Mills and people like you), we still need to make it easier to find the > first steps to do. Even for me, it's not always easy to know what to look > first on MDN. > > -- > Julien > > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g >
_______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
