• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM10 Development (moved to upp)

i know the feeling lol. i havent gotten anything worth building as of yet, im doing some poking around though. might come up with something, i know ive come up with some basic ideas of how to get joe stones ril files to work with cdma, and ive got a solid handle on what a few of the proprietary files are that need to be pulled from the stock rom, but i havent gotten very far past all that
 
I have been searching desperately for a tutorial on "how to create a device tree for an unsupported device". I thought I would just start from scratch and do it, but I have come up short on the instructions. It's almost like everyone wants to keep it a secret.
 
i synced the google nexus 10 files(manta) so i could pick em apart and take a peek at what makes that distribution tick, i figure if we can take a couple different official builds and replace everything in them with info and files from our phone we should have something. that was my original plan all along, to take a known working build of cyanogen and go through all the files that you can text edit line by line, replace all the info to match our phones, then take all the prebuilt stuff it requires and put it where it goes, make sure the stuff from the vendor folder ends up pulled like it should be and all that. its a daunting task but it should technically work
 
basically all you can really do is use other device trees as reference, go through every thing line by line and adjust it all to match our phone, use things like the cm7 config for the warp to see what it required to go from stock to cm without changing android versions since thats our closest match of a phone, maybe take a peek at the officially supported ztes, like the blade, take a look at other phones that arent matches but are set up for a cm10 build, and then basically take all the info you have and mash it all together into something that looks like one of the cm10 builds format wise
 
i know how to do it, its the same way i was tinkering around in cwm, use a bunch of things as reference for what the code should look like, then adjust for our hardware, its just a huge pain in the ass and it gives me a headache trying to pick all that code apart
 
I guess I was hoping for a generic how-to for unofficial devices. It seems like something that cm should have on a forum, but not that I can find.
 
nope, just a few tiny sample devices. they expect anyone undertaking the task to pretty well know what they are doing already. and i mean its pretty self explainitory its just a huge undertaking. a working device tree for any device has all the code and stuff necessary to build a working distribution, adapt it to our device and there you go. change names, use our prebuilts instead of theirs, if you wanna go through every single file on a known working cm10 build checking it line by line to adjust all settings to our phones be my guest, i might do it i might not, to be honest i cant even focus on a screen full of text like that long enough to make it through one file at this point
 
i mean we know what processor and architecture we are running, we know what modems it uses for wifi and cdma and bluetooth, we pretty much know all the information we need to its just going through all those files and adjusting every little thing that is the hard part, not because its a difficult task, because its easy to miss something
 
I would consider doing this, but maybe if we delegate it would be less daunting?
 
that it would, we just have to make sure we all have the proper info. we have to syncronize our efforts in order to make it work right, if one person is pulling info from one source and another is pulling from a different source they will conflict. we have to decide on what base to use, a phone that doesnt have to be similar at all but has to be working fully on cm10. then we need to settle on sources of information, my vote for that category goes to a combination of hoarks cm9 source, the cm7 source(due to the fact that hoark put alot of extra crap we may not need in cm9), and the n861 two n860 kernel source for hardware info comparison
 
and we have to make sure that if someone runs into an issue where one source says one thing and the other says another we have to agree on what we are going with and all stick to it
 
oh yea, and i dont recommend using a samsung product as the base, that includes google nexus devices, they use a different method of doing things than most so id go with something a little more generic
 
I would recommend going through other zte devices and looking for similarities in the coding to see if you could find commonalities between them to better understand how ZTE codes their products.
 
exactly, thats why i suggested pulling from multiple zte sources, the warp 1 is nearly identical actually so anything that works on there would need very little modification but unfortunately cm9 device trees are formatted for cm9, cm7 for cm7, we can use the info as reference for what to change settings to but we cant just use the configs outright it wont work because cm7 may call something by a different name or have a [ where cm10 has a ( or a { its like differences between formats of anything, an mp3 player cant play ogg files because they are written differently, all the info is the same, its the same song, taken from the same cd, its just written differently. if i told you to read a book, and handed you a version of it written in chinese chances are youd be screwed, same basic principle
 
mind you, if we want cm9 it should be a simple task, cm9 works on the warp one, go through, change some names, replace their prebuilt files with ones we pull from our phone, done deal
 
ist just unfortunate you cant take a cm9 or cm7 device tree, plug it into cm10, and have it work
if we could do that itd be a breeze
 
junkie2100 said:
mind you, if we want cm9 it should be a simple task, cm9 works on the warp one, go through, change some names, replace their prebuilt files with ones we pull from our phone, done deal
Click to expand...

I am down with cm9 to start off. If you put something together I will grab the source and build it :)
 
honestly, it might be really good to start off with cm9. If we get it working well, it would seem an easier task to modify a working cm9 tree for our phone on cm10.
 
very true, ill see what i can do but the problem with me doing it is the whole connection thing, itll take me most of a day just to get the tree to you. but i will put it together if you like, the only problem i see is the kernel... not sure how a stock one will react to cyanogenmod
 
I am pretty sure I already know a couple of the proprietary files are incorrect. I am going to try to fix up my device tree with all the correct boardconfig and recovery.fstab info... and edit extract-files.sh to grab the correct files from the phone. Other than that I will need your guidance :)
 
junkie2100 said:
very true, ill see what i can do but the problem with me doing it is the whole connection thing, itll take me most of a day just to get the tree to you. but i will put it together if you like, the only problem i see is the kernel... not sure how a stock one will react to cyanogenmod
Click to expand...

Don't you have a 2.5gb/mo limit before being throttled to death? How are you even able to use this forum after downloading all those roms?
 
regarding getting the device tree to me, can't I add you as a contributor on github or something. I thought I read that was a possibility. If so, you can edit files right on github and commit them. I could then setup my environment to pull from that project and build all your most current changes. Just a thought.
 
You must log in or register to reply here.
Back
Top Bottom