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

well i can just do it to my dropbox, itll just take forever to upload, and im not sure about githubs compatability with my unstable internet may cause corruption. and sorry i was working. but to answer your questions... starting in reverse order, i dont get throttled because i bypassed their proxy servers, they cant throttle me anymore. i pull over a gb a day easy and they cant do shit about it lol. the whole guiding thing tho shouldnt be necessary, i think i got it all... other than the fw files i haven quite figure out where those are supposed to go yet but i think i can and even without them it might be bootable. youre going to want to run the environtment and vendor setup deal, whole tutorial thing ya kno, and then itll be called ZTE_warp2
so for lunch its
lunch ZTE_warp2
same for brunch and all that
make note of capitalization, i didnt think to change it sorry
you will need the ics distro, and i recommend putting it in a different folder than the jellybean one that way it doesnt get overwritten, if you sync in the same directory you will probably kick yourself down the line
and i dont even know whats going on anymore so if i screwed something up i apologize, btw the serenity kernel can be used but isnt being used currently, im using one of playfulgods kernels at the moment, we can try dtms later itll have to be extracted and i cant remember how to do that right now. plus im in the middle of uploading over 100mb right now over a 3g connection... so yea not gonna happen bud lol
anyway ill post the link when its done and you can play around with that, and make sure you use the included framework files they should be good for cm9 they just arent working with cm10 apparently
 
and if it fails due to an error made by me i apologize, ive been staring at code for over an hour and it hurts my brain lol
 
yea uploading is gonna take a couple hours... sorry github doesnt get along with my computer but there is little i can do about that. ill get it up as soon as i can, and im gonna try not to fall asleep on you but i cant make any promises
 
sounds good. I will check back in a while and try to get a build off tonight :) I corrected the boardconfig and fstab files in my github if you want them. Thanks for your hard work my friend :)
 
np at all. this benefits me as much as anyone else here. but yea i think i adjusted everything properly... umm, let me check, i may have to have you fix the boardconfig lol, i was losing focus at that point

nope i got it all im pretty sure. if it doesnt work out tho feel free to adjust whatever you like and tinker with it. not like you can break the original download so if you screw it up redownload and try again lol
and as far as testing goes it should be perfectly safe as long as you dont flash a recovery along with it, keep a backup, and if it doesnt work just restore, no harm no foul
i wont be around for the initial testing phase tho, plus even if i was awake for it 10 people will have tried it before i did lol, takes me FOREVER to download anything
 
oh yea, and if youd like to try dtms serenity kernel, you can look up how to unpack a .img file and pull the kernel itself from his boot.img, or even try flashing the boot.img itself after installing a test build that does have a possibility of working, id try this one first tho since its what got cwm working and it was designed to work with cm
and if you run into build issues again, remember vendor cm is generic stuff and the ril frameworks we input into there, vendor zte means there is an issue with the device tree, and like it gave you an error on android_framework_base, that means it was something in the framework directory, then inside the base directory, which obviously it was, deep in there but it narrows things down at least a tiny bit

i dunno if that made a whole lot of sense kuz im tired so ill put it this way too
android_framework_base = /framework/base/
and itll either say something about cm or zte as a vendor, cm points to the root of the whole ics source, zte points to the device tree
 
sounds good. I can start syncing cm9 in a while. I may not be able to get a build off tonight, but for sure tomorrow. I will still try tonight if possible :)
 
that works, let me know how it turns out. ya kno, if im a complete failure or just a bit of a screw up lol. give it about 20-30 more minutes and hopefully ill have a link for you
 
if the hoark source i got from github was good tho and he didnt use some special build method it should work tho
 
yep, almost every proprietary file was replaced except the ones i couldnt find in the system folder from my deodexing. they should still work tho considering the hardware is almost identical
 
ok well i dont see any references to the screen type itself, i did however find something else i forgot to change... it may still work mind you, it wont effect anything functionality wise but it may confuse the hell out of you, the screen is inverted lol. my bad, fixing that one now, still not done uploading tho so itll be a few minutes
 
I got bored and started on a device tree that is as close to the warp Cm9 source as i can possibly get. I still have a lot to edit and will check it against the ones you guys upload.

EDIT: Speaking with Playfulgod about the device tree to get his opinion.
 
syncing ics repo now...gonna be a while. I don't think I'm gonna be able to build it tonight. For sure tomorrow though :)
 
Playfulgod is going to make us a working device tree tomorrow, i will upload what i came up with in a minute. I didn't use any files from the warp1 these are all files pulled from the sequent.
 
I will try to build yours and playfulgods tomorrow as well. I am excited to see what we can come up with...Thanks shinru2004 :)
 
You must log in or register to reply here.
Back
Top Bottom