• 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)

np, and one last thing make sure youve tried both versions of the lunch command i mentioned earlier if you havent yet
night
 
I set up a git repository with the existing device tree for cm10 here. Keep in mind I do not fully understand how git works, but I managed to get it setup at least :)
 
sweet. alright and as far as you saying lunch doesnt work. does lunching fail? or does lunching work and the build still fail?
 
git repository = win
you may proceed

edit: and dont feel bad, youre actually doing very well, youve surprised me on a number of occasions, this is just the kind of thing ive been doing for fun since i was a kid. hell ive been banned from the computer lab at parker road elementary school since i was 9 lmao
 
yea see as it turns out, the joe stone ril files were in there, which are part of the things built into the file that keeps giving the error. that would explain why the thing keeps failing, remove the joe stone files and we should be good to build
 
just gotta make sure we put the original cyanogenmod files back in their place. this may cause a radio malfunction yes, but at least we will have a build to be able to see if it does, and if it does im sure we can make some sort of cm/joe stone hybrid file that wont crash the build
 
wait... hmm, need different ones. those are zte specific they done replace anything... gotta find out where theyre linked to and change it kuz they dont replace anything
 
The joe stone ones will work. Which version do you have? Like what is the file name and was this the stuff from pg's github?
 
wait.... we need dtm
he knows which ril file works, it may just be that we need cm9 instead of 10 tho
and in case this helps here is a very similar phone talked about on the warp cm9 board that they were discussing pulling things from right before dtm said the ril is working
https://github.com/MTDEV-CM10
re encoding all of this is a daunting task tho and i am having trouble focusing on it at the moment, if it turns out to be necessary and i can manage it later i will but hopefully we can use the same method they did on the warp to get ril fixed
 
playful god didnt have the joe stone files, so not only are the joe stone files built for the warp1 though i dont know if that matters considering its radio commands and they have the same radio, but its also made for cm9 and we are attempting to build cm10
 
pgs source was very incomplete, it didnt even have enough to get cwm running let alone a full cyanogen so we had to pull a jurassic park move and fill in the missing pieces with hoark dna lol
 
like superr said tho if you got someone that can take a look its all there on github now. and that framework folder is obviously the issue, we know that, im just not sure how to fix it and my brain is fried after trying to work on like 20 projects at once yesterday

the device tree is fine as far as i can tell... its just the framework folder that was modified in the cm source itself thats the problem, thats why we are erroring on the build of a "common" component
 
thats the part that was so confusing. he said that it couldnt build something and output it to the common cm part of the build, not the device specific part, but apparently you had to add that common component to cyanogens source to get ril to work for the warp, and its conflicting with our build. possibly just because we have cm10 instead of 9
this is ALOT of code to go through and adjust though, i think i can see some differences between a cm10 file and this one but im not sure

this joe stone file is so much bigger and has so much more info than the files i have to compare it to that i cant tell what info is actually in the cm10 file to compare to and what isnt, i could very well end up removing something we need. my only thought is to find one we know will build in cm10 and rename it to replace the joe stone ones, then we can work that out later. the radio wont work unless we get really lucky but we can at least get it built and see what we are working with
 
Are you building off the cm repo or the mtdev stuff? Cm10 doesn't work for the triumph yet, well it has alot of issues, and if you are using their repo, you would also inherit alot of their issues. I know for them, they make a lot of changes in the source.
 
You must log in or register to reply here.
Back
Top Bottom