• 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 cant build, thats why superr is doing that, but hes building off the repo stuff, the only thing changed is those two ril files

i cant sync the repo properly over my 3g connection
 
ok yea those are completely different. i think we have our answer, now as soon as superr gets the chance he can toss those in place of the framework files we have now and we should be up and running

edit: and they seem to match the format of the cm10s built in ril files as apposed to the ones we had, so this should be the answer to that problem
 
They work for the warp1's ril for cm10 so it should be exactly the same
 
kool, yea we definitely seem to have something here, if nothing else goes wrong we should have a build by the end of the day :D
 
Keep in mind we haven't gotten ril data to work. But maybe with the proprietary blobs from ics you might have better luck ;)
 
hopefully. right now tho i figure if we can get the rom running we can work out the kinks as we go, and it wont limit us to one problem to solve either, right now we are at a complete standstill because we only had one issue to work on
 
i guess i could start poking around the ril files see what i can come up with... maybe ill get lucky and stumble on something. and just to be clear, the ril data never worked on cm9 for the warp with hoarks source? and did it work on cm7? i may be able to compare and adjust things according to a working one even if its improperly formatted
 
Hey guys. Downthemachine sent me over to help you guys out. since iam also doing cm10 for the warp. shouldnt be too hard.

What is the current status?
do we have a working device tree, or do i need to make one ?
Ril? do we have Ril Files?
 
Dm47021 said:
Hey guys. Downthemachine sent me over to help you guys out. since iam also doing cm10 for the warp. shouldnt be too hard.

What is the current status?
do we have a working device tree, or do i need to make one ?
Ril? do we have Ril Files?
Click to expand...

sweet, thanks for comin to help, basically we dont know what we have as far as device tree. we know we had a working device tree to build cwm from, but we havent made it to cyanogen yet. the build kept crashing on a framework jar file that as it turns out contains things made from the joe stone source files that were put in the framework folder of hoarks cm9 configuration
we have been using hoarks cm9 as a base, and from there adjusting everything for our phone, replacing all the prebuilt stuff with files from our rom, editing the boardconfig and init and all that stuff, right now tho we have just figured out the reason we cant make a build has nothing to do with the device tree it has to do with something outside the device tree...
 
https://github.com/superr/warp2_device_tree
that is what we are working with
and the problem seems to be that the stuff in the framework folder was made for cm9 not cm10
so we are going to replace the bigger one with one of these
http://db.tt/rKl1OIaX
then we will see if we can at least get a build out of it

oh yea and in case it helps here is our cwm device tree without all the extra crap done to it
https://docs.google.com/uc?export=download&id=0B1pvmzqy_P8odTQ0dTl2RG1rZEU

to be quite honest i dont have any idea what im doing, im just kinda playing it by ear trying random things to see what they do or dont do

ya gotta figure if i keep chuckin rocks im bound to hit something eventually lol. thats how i got clockworkmod 6 working and that only took 2 days
 
untill superr comes back though im stuck, im incapable of acquiring and therefore compiling the cyanogenmod source myself, that is why im just kinda sitting here being useless at the moment
 
Hello, Thanks downthemachine and Dm47021 for coming to help us out, and of course junkie2100 for your continued support. Just downloaded the new ril files. Can't wait to build this sucker.
 
ok, so just replace the framework from the new joe stone zip with the framework from hroarks, right? Do I need to update anything in the files that may refer to the replaced files? They have different names. Or rename the new files to match the old?
 
just rename on of them to ZTEQualcommRIL.java
they are both that file just two different variations
if that doesnt work try the other, if that doesnt work we may need to get rid of the ZTEQualcommUiccRIL.java to make it work which may require finding a reference to it in the build files but im not sure deleting or renaming it might work

at least i think theyre just two different variations of the same thing, theyre both the same size which is much closer to the first one we have, the uicc one we have is tiny compared to any of them, you may want to try replacing that with 2 tho hold on let me look
 
I just did a full text search of our device tree for ZTEQualcommRIL.java, and there is not a reference to it in any of the files we are using.
 
yea id just go with my original plan, replace the bigger one with one of those, then try it without the uicc thing, then if that doesnt work we will go from there
 
ok, I renamed to ZTEQualcommRIL.java just in case, and removed the uicc file. Building now.....This will take at least 30 minutes, maybe more. I will update immediately if possible :)

I wish this error was closer to the beginning of the build, lol

it gets so close, I even end up with userdata.img, recovery.img, and some others.
 
also, you might have to do something about the public class references
old file says
public class ZTEQualcommRIL extends RIL implements
new file says
public class ZTERIL extends RIL implements CommandsInterface

it may look for the wrong thing if ZTEQualcommRIL is referenced and the built files name the public class ZTERIL instead
there are two of them in there from what i saw
 
junkie2100 said:
sweet. alright and as far as you saying lunch doesnt work. does lunching fail? or does lunching work and the build still fail?
Click to expand...
It fails immediately with no error. I get the first lines I always get when I use brunch, and then a command prompt. No info at all.
 
You must log in or register to reply here.
Back
Top Bottom