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

Root CyanogenMod 10 Pre-alpha (985hPaKicK kang)

Here you go :

https://www.dropbox.com/s/nzi0hdqjshib5se/cmgetwifi2.zip

This version I was solely working on getting wireless working today. It has our drivers and both wireless scripts (and one or two others) running fine on boot. I'll probably mess with it again tommorow however im interested in building from source for my first time so I may just start with that since I setup my ubuntu and most of the environment today ;-)
 
omgbossis21 said:
Here you go :

https://www.dropbox.com/s/nzi0hdqjshib5se/cmgetwifi2.zip

This version I was solely working on getting wireless working today. It has our drivers and both wireless scripts (and one or two others) running fine on boot. I'll probably mess with it again tommorow however im interested in building from source for my first time so I may just start with that since I setup my ubuntu and most of the environment today ;-)
Click to expand...


hace esta revisi
 
No the wireless still doesn't work its not communicating outside of the system folder (needs much furthur device access). I just label the builds so I know which is which.
 
My other build has all our system files in it though it won't boot BC it doesn't see the rest of the file system. That's the one that bootloops and continued to after I fixed the unit d issue. It bootloops BC the scripts/system aren't syncing with the rest of the system. I started this wifi build working one script or file in At a time and marking sure it boots. Best way for you to see what is goin on and how I have been fixing things is boot the rom open root manager goto system/etc and try booting our factory scripts after setting permissions if necessary. You will see the script run if it errors to give you an idea how to fix it. You will see which scripts and file systems I have fixed in the updater script by this method.
 
omgbossis21 said:
My other build has all our system files in it though it won't boot BC it doesn't see the rest of the file system. That's the one that bootloops and continued to after I fixed the unit d issue. It bootloops BC the scripts/system aren't syncing with the rest of the system. I started this wifi build working one script or file in At a time and marking sure it boots. Best way for you to see what is goin on and how I have been fixing things is boot the rom open root manager goto system/etc and try booting our factory scripts after setting permissions if necessary. You will see the script run if it errors to give you an idea how to fix it. You will see which scripts and file systems I have fixed in the updater script by this method.
Click to expand...

All right, just finished downloading, flashing it now, then I will take a look.

EDIT: Even adb doesn't work?
 
Root browser isn't letting me execute, even after changing permissions. Was root manager not a typo?
 
I haven't tried adb though my PC recognizes it fine. I used whatever root browser or what not that is included in the rom. Shoot me a pm and we can talk via chat somehow.
 
It is working very well and very fast at that.
 

Attachments

  • Screenshot_2013-01-06-01-30-50.png
    Screenshot_2013-01-06-01-30-50.png
    67.7 KB · Views: 167
i dont want anyone to take it the wrong way. but hroark is banned, wouldnt that mean by all rights his work being posted here is banned? if thats the case i would imagine you guys would have to go to that forum to discuss this not here. im going to report my post to hopefully get a mod to chime in and clear up some confusion.

I am absolutely positive ANY of the mods can attest to my dislike towards ABC. however they are banned and so isnt their work so it would be quite a double standard to have it any other way...
 
Shabbypenguin said:
i dont want anyone to take it the wrong way. but hroark is banned, wouldnt that mean by all rights his work being posted here is banned? if thats the case i would imagine you guys would have to go to that forum to discuss this not here. im going to report my post to hopefully get a mod to chime in and clear up some confusion.

I am absolutely positive ANY of the mods can attest to my dislike towards ABC. however they are banned and so isnt their work so it would be quite a double standard to have it any other way...
Click to expand...

I was thinking the same thing. Though, we aren't really pushing his work here. It was only something he (or they) found, we are simply trying to work on it with or without their help... If anything, the linked rom can help us get ours moving towards functioning properly. Come on, lighten up.

Also, I'm sure no one is confused. Read the rules and a few threads and you realize what happens. I know these accounts should be banned, but removing a link to a rom that is really helpful seems counter productive. Nevertheless, I'm sure you know that these roms will just appear again; not linked to other sites, but rather hosted by those on this site. The roms will be changed and edited by those who compile them into something new, but containing the same beginning. By removing a link to the rom, you aren't stopping the spread, you aren't stopping production, you are only delaying it. So what is the point?
 
make no mistake i want development to continue, it would be awesome for you guys to get a fully functional rom. you are right that it stops no one as the link has already been found and shared for a good bit so people already know where to go and look if it is removed. hroark is one of my buddies from the prevail and is an amazing dev, i hope he manages to get a fully working rom.

my point is merely equality, regardless of my feelings for abc mini rom was removed and not allowed to be talked about due to whom made it, wouldnt you say that slows development in its own way?
 
Rules are Rules. I guess things are subject to Reports and being randomly noticed. That being said, not everything will seem fair.

Anyways, I am glad we are moving forward.
 
You must log in or register to reply here.
Back
Top Bottom