Develop Bugs

[ROM][11/24/2011] UNOFFICIAL CM7 G2/Vision Kang's Built from Source

This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.

Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6

Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z

I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.

Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App

smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.

Is your link supposed to point to recovery.img?

bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.

Camcorder still borked?

rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery

Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.

Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!

Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0

Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App

do you know if usb issue was addressed in this build

Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App

is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.

having problem flashing the img help

I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .

cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick

[ROM] CyanogenMod 7 for the Samsung Galaxy S :: V7.1.0-RC1 (26 June 2011)

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
This version is a release candidate, but you will find it stable for everyday use.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Galaxy S, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official posthttp://forum.cyanogenmod.com/topic/...r-the-samsung-galaxy-s-v710-rc1-26-june-2011/​CyanogenMod:
Latest Version: update-cm-7.1.0-RC1-GalaxyS-signed.zip
Download: Link
Mirror: Link
MD5sum: c7e812d4c94de40176d463de7f720ffd​Google Apps addon:
Version: gapps-gb-20110613
Mirror: Link
Mirror: Link​The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

cool. just released

thank you all devs

We know. There is the oficial thread posted by codeworks. So why did you post this?
Sent from my GT-I9000 using XDA Premium App

sefuleo said:
We know. There is the oficial thread posted by codeworks. So why did you post this?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
This is the official thread for the RC (and future RC's)... codeworkx's thread is for nightlies. the difference being is that the build flashed from this thread is allowed to report bugs to the issue tracker.

RC is too in codeworkx thread. But anyway.... Thanks for posting.
Sent from my GT-I9000 using XDA Premium App

sefuleo said:
RC is too in codeworkx thread. But anyway.... Thanks for posting.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
there is no information about the RC('s) in codeworkx's thread. his thread clearly says nightly at the top and is for nightlies and nightlies only. the "latest version" link does not count because following that no matter what will show you *all* options. this is the standard CM way of doing things. a thread for nightlies and a thread for stable(ish) version. feel free to check any other CM-supported device's section and you will see both as well.

so is RC1 > Nightly

tb5... said:
so is RC1 > Nightly
Click to expand...
Click to collapse
RC1 = stable(ish)
nightly = bleeding edge
RC will only be updated a few times over the next few weeks until the final build is released. nightlies will continue to be pumped out every night. benefit of RC is you can post issues to the issue tracker and actually contribute back to the community.

So whats the deal?
Used to run CM on my HTC Magic.
Have heard that there are issues with battery life etc. on SGS.
What are the cons of SGS CM71. Cant seem to find list of good/bad issues.
Also, the nightly "must be on froyo" is not listed on the CM7 webpage (and this thread). I can flash from sammy gingerbread now?

BatGnat said:
Used to run CM on my HTC Magic.
Have heard that there are issues with battery life etc. on SGS.
What are the cons of SGS CM71. Cant seem to find list of good/bad issues.
Also, the nightly "must be on froyo" is not listed on the CM7 webpage (and this thread). I can flash from sammy gingerbread now?
Click to expand...
Click to collapse
all the wiki instructions clearly say to flash from Froyo, and those are the instructions to follow.

Kaik541 said:
all the wiki instructions clearly say to flash from Froyo, and those are the instructions to follow.
Click to expand...
Click to collapse
Yes, but you had best add it to the install instructions here too, or the 15 questions you get about bootloaders a day will become 150 or more. No fun at all.
Also, it notes in the instructions on the OP that if you are updating a previous CM7 install, you do not need to flash Gapps again. This has not been true for around 15 nightlies now...has whatever issue that required reflashing Gapps along with a nightly been fixed?

Downloading it..
Finally a RC release ..good work Cyano's Team ..
I use Cyanogen 7 on my Galaxy S and also on my Htc Magic 32b
Cyanogen 7= The best rom of ever
Cheers

Perfectly and thx

rschenck said:
Yes, but you had best add it to the install instructions here too, or the 15 questions you get about bootloaders a day will become 150 or more. No fun at all.
Also, it notes in the instructions on the OP that if you are updating a previous CM7 install, you do not need to flash Gapps again. This has not been true for around 15 nightlies now...has whatever issue that required reflashing Gapps along with a nightly been fixed?
Click to expand...
Click to collapse
the ROM threads for RC releases are cookie-cutter, only replaced with proper links/md5sums. as for the gapps thing, I've been flashing updates every few days and have literally never once had to reinstall gapps =/
also, rschenck, please don't leave me to moderate this thread alone, you make the i9000 threads worth reading

And ANOTHER question....
If I opt not to install the RC1 release itself, but wait and install the next Nightly, which would be 40 for the i9000. Will that automatically update me to RC1?
Plus I am always ready to lend a hand and/or a stinging bon mot, you just seem more up on the RC1 situation than I so I defer to your wisdom.
Lastly, regarding reflashing Gapps, it has been advised as a precaution for ages now to avoid potential trouble. I see no harm in continuing to do it.

Kaik, thanks for the thread. Downloading the RC now (I've been running nightlies for months, if this is good enough I might have my dad run it!) Just wondering, are you a member of the CMSGS team? And if so, do you have any insight to headphone controls being fixed?

A little suggestion..
PLEASE CYANO'S TEAM READ THIS:
See at SuperAosp 8.6 camera..is similiar at Cyanogen camera but it is best in graphics..background black ..photo button better..see it please

rschenck said:
And ANOTHER question....
If I opt not to install the RC1 release itself, but wait and install the next Nightly, which would be 40 for the i9000. Will that automatically update me to RC1?
Plus I am always ready to lend a hand and/or a stinging bon mot, you just seem more up on the RC1 situation than I so I defer to your wisdom.
Lastly, regarding reflashing Gapps, it has been advised as a precaution for ages now to avoid potential trouble. I see no harm in continuing to do it.
Click to expand...
Click to collapse
personally, I always run under the assumption that each and every flash will horribly destroy my phone and make backups of apps with TiBu and nandroid every time while praying I never have to open heimdall again. I then keep the gapps zip and at least one earlier nightly on my SD card. RC1 is basically just a "nightly considered stable for the purpose of bug reports" for official means. nightlies will always surpass stable builds (and will always come with the risk that they are far more likely to break)
chambo622 said:
Kaik, thanks for the thread. Downloading the RC now (I've been running nightlies for months, if this is good enough I might have my dad run it!) Just wondering, are you a member of the CMSGS team? And if so, do you have any insight to headphone controls being fixed?
Click to expand...
Click to collapse
I'm an honorary member of teamhacksung as it were. I've been out of the i9000 group because coolya and codeworkx mostly have it under control and rschenck provides the right amount of help while being entertaining in a way that I couldn't possibly hope to be. as for headphone controls, atinm is aware of the issue and it's on the list of things to be fixed (including TV out at some point).

I didn't follow that much the Nighlies thread in the past month because i didn't have time to flash and reflash continously.
I'm wondering, on this RC1, if everything works, including all that didn't work perfectly in nightlies builds.
And what about battery life? I switched from JVH to JVP and i noticed a small reduction of battery life. Is CM7 RC1 overall better or worst than the aforementioned releases?
ANyway, thumbs up for the passage from nightlies to RC, i was looking forward for CM7 on my SGS since when i bought it in January. Coming from an HTC phone i really missed the speed and functions of CM.

[wip][rom][aosp] ns2

Change of plans, hopefully with the help of anyone who is willing I'd like to compile an aosp build for the Sprint GS2 from source instead of trying to hack a port together, as suggested in this thread and other places, it just feels like it will be a lot more of a fruitful experience for all involved and have a better end result.
(a big thank you to everyone who so far have been super encouraging and friendly with noob questions, it's much appreciated!, I hope that if you wanted to help with the port you'll help with this build as well!)
This is a WIP. Starting out with Samsung's open source platform and kernel instructions on how to build from aosp and I'll take it from there.
I've setup some repos to get this all started in one place:
Samsung SPH-D710 platform source - https://github.com/thefredelement/sph-d710_platform_source
Samsung SPH-D710 kernel source - https://github.com/thefredelement/sph-d710_kernel_source
Team Hacksburg kernel source - https://github.com/thefredelement/android_kernel_samsung_c1spr
Stock kernel initramfs (thanks buddy323!) - https://github.com/thefredelement/stock-initramfs-eg30-epic-4g-touch
https://github.com/thefredelement/Samsung-Galaxy-S2-Sprint-Epic-4G-Touch-AOSP-Build - will be where the build will live after I push over Samsung's platform make and upload it!
--- old stuff that will make your head spin ---
If anyone wants to continue working on this, feel free.
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: you don't want this...

Reserved for changelog, when hopefully it gets that far

Awesome to see a project like this, good luck in the port!
Sent from my SPH-D710 using XDA App

O_OMG <3 :-!
Sent from my SPH-D710 using xda premium

Good luck! Looking forward to this.

What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App

deano0714 said:
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This boots using the stock Sprint/Samsung kernel.

xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
What kernel are you using?

thefredelement said:
What kernel are you using?
Click to expand...
Click to collapse
im using stock

xploPR said:
im using stock
Click to expand...
Click to collapse
Did you wipe all of your user data before installation?
Do you get to the boot animation?

Constructive criticism would be for me to point out you must not have read the OP because it clearly said nothing works because we don't have a aosp kernel yet but you are just rude.
Sent from my SPH-D710 using xda premium

xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
ehusidic said:
The title clearly states its not ready or stable so chill out while the devs do what they do
Click to expand...
Click to collapse
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.

I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.

jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic ore infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
Sorry for the horrid insults I aimed at the complaining member. Too uncouth.
Sent from my SPH-D710 using xda premium

Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. I agree this is a much better idea.

jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
i like that mandatory vacations with paid vacations to hawaiii, can xda hook it up or what?

thefredelement , good luck. glad to see new devs... i hope to be there one day but i'm way off...
Thanks!

thefredelement said:
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: http://www.multiupload.com/OF1HXSSOCJ
Click to expand...
Click to collapse
hit me up i can get ur rom working with wifi/3g/4g/whatever. zedomax at gmail dot com

Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
I recall rumor about samsung sending a GS2 to Cyanogen so that he could "get to work". Guess that never materialized - or they gave him something else to do once they hired him...
Sent from my SPH-D710 using xda premium

it was one of the cyanogen devs that got a galaxy2 & they have nightlies for the gs2 now.... It should not be hard to get it ported over
....
One of the devs on teamhacksung was asking for people with the phone to help with it ..he ask on twitter like the 16th so they are probably working on it....
Sent from my SPH-D710 using xda premium

[ROM] Unofficial CyanogenMod 9.0.0 Testing builds for Epic 4G Touch

Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** If one of this builds bricks your phone, kills your cat or causes
** a thermonuclear war, don't point at us. We'll laugh at you.
** You decided to make this modifications to your Phone.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on experimental builds is the leading
** cause of male impotence.
Hey all, you may remember me from back on the cdma hero. Well, I decided to pick up dev'ing again, and have been pushing source up to my github for working code for ice cream sandwich on our Epic 4G touches. It's my pleasure to say it's mostly functional, with just a few bugs remaining, of which i'll post at the end of my thread here. If I didn't list some functionality you're looking for in the bugs list, either it already works, or i forgot about it. Chances are high that it already works, though . Once I get nightlies to run, i'll make another thread for that.
Follow me on twitter for updates, and testing builds Please, follow the instructions listed below for flashing, to prevent any damage to your phone
Or, for the lazy, click HERE which is also mirrored for a download, which will also be mirrored HERE. note that my laziness will probably hinder me from updating the OP frequently to keep up with my updates i post on twitter.
Don't forget to flash GAPPS if you're coming from a non-CM-based ROM
Kernel: FC07
Recovery: CWM
What works
- GPS
- Camera
- SMS/MMS
- YouTube
- External SD mounted to /emmc
- Pretty much everything else
Bugs
- apps2sd doesn't work for EXTERNAL SD
- Video recording doesn't decode the files properly to mp4, so the output is unusable
- Music occasionally FCs. Feel free to post some logcats (pastebin'd only) if this happens to you
Installation Instructions
*WARNING* There have been a number of people over the past 6 weeks experiencing HARD BRICKS of their E4GT when flashing ICS from ROGUE 1.2.1 on FB15 AND NEWER KERNELS. Please see THIS THREAD for more information. As such, I am STRONGLY recommending that ALL FLASHING of this ROM be done ONLY from the STOCK CWM EL26 RECOVERY (download) EDIT: As an update to this, we're fairly certain this issue is sporadically occurring whenever a partition is being formatted by the recovery. this led us to believe that the problem lies in the kernel samsung has been putting out in the leaks. Please, for your sake, use, a recovery with a gingerbread kernel when flashing this rom, or doing nandroids, or even doing data wipes.
First install of CM9
BACKUP your existing ROM
Did you backup your existing ROM? No? BACK IT UP, GENIUS
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED (*note* backup/restore seems okay, it's only the actual zip/kernel flash that risks bricking. See THIS THREAD for more information.)
Reboot to recovery (power+vol-up)
WIPE DATA
Flash CM9
Flash GAPPS
Reboot to system
After rebooting, if you go BACK to recovery, you'll be on Rogue 1.2.2
Upgrading CM9
This build will upgrade from any CyanogenMod rom just fine. Just, be sure you're using the EL26-CWM recovery when flashing this rom. read my Edit up above for further details.
Reboot to DOWNLOAD mode (power+vol-down)
Using ODIN (link) flash to StockCWM EL26. Flashing CM9 from another recovery, such as Rogue, MAY BRICK YOUR PHONE. YOU HAVE BEEN WARNED (*note* backup/restore seems okay, it's only the actual zip/kernel flash that risks bricking. See THIS THREAD for more information.)
Reboot to recovery (power+vol-up)
Flash CM9
The newest update changes the way backuptools work for the install script. it reads custom user scripts in /system/add.d. Since the first rom i put out didn't have that, you'll need to reflash google apps after flashing cyanogenmod. after flashing this latest update, subsequent updates won't need you to reflash Google Apps
Wipe cache
Reboot to system
Enjoy!
EDIT: I updated the OP with the link to the rom. This is using some better coding for mms and sms receiving, and the LOS bug was fixed by the epiccm group, and pushed to mainstream cyanogenmod, so we we're benefiting from this. also, added in were sprint visual voicemail and sprint updates. There's surely other stuff i'm missing to add to what's working and what's not . Note that Cyanogenmod doesn't normally use stock kernel, rather it uses cm-kernel. the issue is that we don't have source for the kernel in ics, so we can't merge our board-files, etc into it just yet. But this isn't an issue, as far as functionality. It's just not the full CyanogenMod experience .
EDIT2: I had jerdog change the thread title to unofficial, because we aren't really in CM just yet. It's more because of my discrepancy, with not wanting the device tree to be pulled, because i'm still doing work on it.
EDIT3: Guys, don't be flashing any themes over this rom, reason being because i changed the framework files a bit in my source, and it hasn't been pulled into mainstream cyanogenmod yet.

Wow, I ran your stuff on my hero. So nice to have you here.

Sick great to have you here

Wow thank you so much I've heard great things about your work!
Sent from my SPH-D710 using xda premium

Woot woot I remember the old hero days...
Sent from my GSII.

Wow dude, my hero memories are rushing back to me! Great to see you here!
Sent from my SPH-D710 using xda premium

Nice, glad to have you here!

Man your about to be a real "hero", darchstar to the rescue, glad to have you here man. Ill be installing this since it comes with recovery, very small chance of a brick now,,, THANKS again.
Sent from a phone with kNOw CIQ ...

Good stuff buddy!
Sent from my SPH-D710 using xda premium

damn epic touch scene getting better and better with all these ics

**** yea glad to see you again
Sent from my SPH-D710 using xda premium

A quick note:
As with all CM9 ROMs, we have been seeing some RARE bricks (hard brick, unbootable, no download mode, blue LED of death) when flashing from FB?? and newer Rogue kernels. These are RARE but they DO happen. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1525495
I would recommend doing ALL of your flashing from EL26 StockCWM (if you can still find it).
You have been warned.

darchstar said:
Bugs
- Sporadic instances where 3g doesn't pick up coverage again, after coming out of low signal areas.
Click to expand...
Click to collapse
Have to keep waiting.

neatchee said:
A quick note:
As with all CM9 ROMs, we have been seeing some RARE bricks (hard brick, unbootable, no download mode, blue LED of death) when flashing from FB?? and newer Rogue kernels. These are RARE but they DO happen. See this thread for more info: http://forum.xda-developers.com/showthread.php?t=1525495
I would recommend doing ALL of your flashing from EL26 StockCWM (if you can still find it).
You have been warned.
Click to expand...
Click to collapse
thats some excellent advice

Oh man, darchstar's in? sh*t just got real. I wish I could just jump forward a few weeks.. Good to see you here!
EDIT: Darchstar, let me know if you want me to take this down, but I'm gonna put a link here to make it a bit easier: http://t.co/bn3AW0bD
EDIT 2: I evidently didn't make it big enough...LINK IS IN THIS POST [and Darchstar's twitter]UNTIL FURTHER NOTICE
I just put it here to save from the "where's the link" posts..
P.S. Downloading and I'm tweaking cause I'm so excited to flash this.

just flashed from fb27 with no issues but dont do it if your scurrrrrrred

Where's the link.
Sent from my SPH-D710 using Tapatalk

Will of fire said:
Where's the link.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
post 15 has the link

both links from your twitter and the one provided Above are not working.
Sent from my SPH-D710 using xda premium

Mms is sending but not able to download. Charging light works. Woohoo. Thanks for the release.
Sent from my SPH-D710 using Tapatalk

PAC ROM [Nexus5] Basketbuild bugs

After flashing the latest b.b., my radio was completely fried. Not that I'm too upset, files were easy to find. However, for someone new to root/custom ROMs, this issue may prove to be quite difficult. I received no calls, texts, or emails for 9 hours. When I fixed the errors an obscene amount of missed calls and texts and my emails poured in. If anyone using N5 experiences this, easy fix. Flash new radio and make sure a clean wipe is done prior to reflashing. Voila!

https://developers.google.com/android/nexus/images
After downloading the zip:
Wipe data
Wipe Dalvik
Wipe Cache
Flash .img

Any other bugs I'm willing to post fixes if requested.

I can say with complete confidence that PAC ROM is definitely my favorite ROM. However, I create threads in regards to bugs and so on for intel purposes only. I do not post in these threads to complain, put down, or belittle any developers hard work. I have PAC ROM installed on 2 of my devices and love nightlys. This being said, I'm fully aware of potential risks, risks I voluntarily involve myself in. I simply take the initiative to open thread communication to assist in maximizing feedback, thus making it easier for developers and testers to make any necessary improvements. If anyone has for any reason been offended in ANY way, please let me know. And I do apologize if so.

We appreciate your eagerness in sharing bug reports with us. However, these would be more useful if a logcat of the issue is provided so that we can also diagnose the issue. Furthermore, it is highly recommended that these device specific bugs be reported in the pac rom thread for your device, so that the maintainer for your device is notified of the issue and other users can report if they are having the same issue.

iurnait said:
We appreciate your eagerness in sharing bug reports with us. However, these would be more useful if a logcat of the issue is provided so that we can also diagnose the issue. Furthermore, it is highly recommended that these device specific bugs be reported in the pac rom thread for your device, so that the maintainer for your device is notified of the issue and other users can report if they are having the same issue.
Click to expand...
Click to collapse
I made that attempt. I have no access any longer to the site.

D.D.P. said:
I made that attempt. I have no access any longer to the site.
Click to expand...
Click to collapse
Nexus 5 PAC-rom thread:
http://forum.xda-developers.com/google-nexus-5/development/rom-pac-version-t2670238

Also, I have submitted many bug reports and follow up. I seem to be shifted to the back burner. Which is unfortunately why I am not making further efforts to regain access to PAC ROM forums. I have devoted a lot of time to making sure, as a user, I contributed as much as possible toward advancements in PAC. I have went as far as using banners in multiple forums, used avatars supporting the ROM. Im not looking for praise, just enjoy reciprocating what I hope to receive when I release my ROM.