yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Quick question: Can I build a kernel using the tut that I placed in the OP without borking my current CM10 build files? I have been leery of building anything else, because I have had no trouble building in the last 2 months and after all the trouble I had getting started, I don't want to have to begin from zero just to do something different. I also want to try out building slimbean but the same concerns apply. To me, it seems as though it shouldn't be a big deal, just accessing a different set of files depending on what I am building. But, I'm at least smart enough to say when I don't know and personally, I've had a bellyful of learning by trail and error. Anybody throw me a bone on this? Thanks .....:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Sure. Copy your current build directory to a new one, change your repo source for the kernel, run a sync and then build.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] incarnation95:
Thanks guys for all the help and i have with the help of this guide and active helpers in this thread been abl to build PA, SLIM BEAN AND CNA for my device!

AND I LL BE ACTIVE HERE TO HELP OTHERS FROM WHATEVER I KNOW:)

And now was trying to build someone's rom for sgs1 galaxysmtd... the compiling was going good untill it started making the kernel... this is the error that i get!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Building a PACman ROM with some interesting additions. Hope to have it ready this time tomorrow.... gonna add it to the OP, although its essentially the same as cm or slim. Just sync a different repo:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
OK it looks like something is not setup correctly in your environment either permissions or wrong ownership of files its hard to say. I think part of your problem is you are using several tuts you need to stick to one until you get a successful build.

I would try these links below and stop jumping from tut to tut;)

Building Kernels From Source:

http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source

HOWTO: Unpack, Edit, and Re-Pack Boot Images

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Good Luck

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] whassupmyninja:
So if i want to follow that tut to build the kernel since i had no luck with the tut in the op and while doing that i should move the files out of my cm10 folder and copy them elsewhere and also take out the repo file in the bin folder to ensure i do not mess with my build of my rom? I want to make the kernel but i dont want to start all over again (i already had to twice!) I want to learn to do this stuff effectively, i just need a jumpstart lol
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Do you have that 'galaxysmtd_initramfs.list' file in the '/kernel/samsung/aries/usr' folder?

https://github.com/CyanogenMod/andr.../blob/jellybean/usr/galaxysmtd_initramfs.list

This was the error you received (line #187-217):

https://github.com/CyanogenMod/andr.../jellybean/scripts/gen_initramfs_list.sh#L187

[I][COLOR="Gray"]# if only one file is specified and it is .cpio file then use it direct as fs
# if a directory is specified then add all files in given direcotry to fs
# if a regular file is specified assume it is in gen_initramfs format[/COLOR][/I]
input_file() {
source="$1"
if [ -f "$1" ]; then
${dep_list}header "$1"
is_cpio="$(echo "$1" | sed 's/^.*\.cpio\(\..*\)\?/cpio/')"
if [ $2 -eq 0 -a ${is_cpio} = "cpio" ]; then
cpio_file=$1
echo "$1" | grep -q '^.*\.cpio\..*' && is_cpio_compressed="compressed"
[ ! -z ${dep_list} ] && echo "$1"
return 0
fi
if [ -z ${dep_list} ]; then
print_mtime "$1" >> ${output}
cat "$1" >> ${output}
else
echo "$1 \\"
cat "$1" | while read type dir file perm ; do
if [ "$type" = "file" ]; then
echo "$file \\";
fi
done
fi
elif [ -d "$1" ]; then
dir_filelist "$1"
else
echo " ${prog}: Cannot open '$1'" >&2
exit 1
fi

You have the proprietary vendor blobs for that device? (Like the proprietary_vendor_samsung repo from TeamChopsticks or TheMuppets repo for our phone)

A brief search for that error seems to be related to not having those proprietary vendor blobs.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Sounds right. Thing is, yes I do have 1 "Franke-build" where I have tried to adapt different tuts. However I have maybe 6-7 builds going, 1 for each tut.

This one might have some promise. I saw one like it but was outdated. This seems newer, I will try.

It also adopts whatwas my initial thoughts! lol Pull the kernel from the cm10 rom folder instead of creating everything new. So it will have all the manifests and failover stuff.

Building Kernels From Source:

http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source

===============================================

This one I have used. But all of the resource links are dead. So I can't use it properly.

HOWTO: Unpack, Edit, and Re-Pack Boot Images

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images

Thank you roger, I will push on..... :-/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] incarnation95:
Thanks for the error! I downloaded the kernel source again and it solved the error:)

I had the vendor folder established well!

Anyway thank you :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Holy crap ... and totally off topic ...

Have any of you guys seen how insanely complicated it is to flash a rom on an HTC One X? My goodness, that is not a straight forward process. :crying: :eek: :silly:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] UZ7:
Haha I think that's a given with any HTC devices :P
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yeah that's definitely one part of HTC ownership that I don't miss. Anybody remember the wire trick for the rezound? That turned out to be a snap but the horror stories made me nervous as hell
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Hey, I was just wondering what kind of errors you/anybody is getting with the kernel tut. I'm really beginning to wonder if mine have to do with my setup....:-/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Still in the middle of a successful pacman build that failed at boot. Sounds like an oxymoron right? A successful failure? Like jumbo shrimp or a braille keypad on the drive up ATM. Never had a build that finished successfully and didn't work before. You've tried all the tuts and none of them work for you? Have you pm ed Sean or mohan? Have Rogers tips helped at all?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Check your Pm. :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Really, really close. Maybe 2-3 steps from the end. On one of them, all I have to do is get mkbootimg to work, then zip it up. I did notice that in InstigatorX, he left the mkbootimg to happen, once flashed, on first boot. Interesting. I still don't really know how I would effect the OP tut tho. I've collected, perhaps 12 of the as .txt with the hopes that I can put together the right combo for skyrocket. Regrouping at the moment.

I would love to approach mohen about this. There isn't any better Android guy as far as I have seen. Funny thing with him tho. He will not touch anything "Unofficial". No cm and only a few cherrypicks ICS/aokp (well, cm9-aokp?). Like some rom manager stuff that he liked and boot sound! He does have a kernel build thread but it is not really exploited last time I checked. Only partially done OP. I would have to find a few hours to read it before I posted there. He does give total and complete answers to well asked questions tho. You can tell that he proves everything before posting and follows with troubleshooting steps.

Packman sounds cool. Maybe I will do a "SpaceInvaders" one?! I'd have to find my old coleco and hack it. Probably an emulator out there someplace.

The problem with links to other tuts is that pretty much all of the aren't for skyrocket. So the end of them is all wrong. Going from zImage to bootimg, then zip.

Anyway, still plugging away. ;-/
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'm talking with DAGr8 about possible solutions to your build issues. I know you have probably listed your various issues a million times but could you PM me with a rundown of whats holding you back at this point? It might save some time.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
@wantowan2:

If you really just want to build a kernel this is the simplest way to build a CM10 kernel.

1. cd to your CM10 build directory.

2. Type ". build/envsetup.sh" minus the quotes.

3. Type "lunch" and select the device you're building for.

3. Type "mka bootimage"

4. Change directory to "out/target/product/your_device/

5. Make a flashable zip with the "boot.img" and "system" folder that is located in the directory above.

This takes about 2 - 3 minutes you will have to google how to modify config files to modify the kernel. The kernel file created will be about 7 MB not 230 lol;)

EDIT: I usually make clobber first just to clean up the "out" directory.

That's it enjoy and I hope this helps.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
Pft! hahahahahahahahahaha Are you serious? lol If that works, for ME I mean, you have no idea of the implications.

Thank you dude. I will report back!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
I usually make clobber first just to clean up the "out" directory.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Wait, you didn't know this? I thought this whole time you were trying to build it separately from the cm10 build tree on purpose. I thought it was understood that you can build just the kernel from within the build tree.

You really should go back and read the commands and definitions in the /build directory.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wantowan2:
It was never about me. It has always been about producing a skyrocket kernel tut for the OP. BMP7777 polled the thread and I'm the only one that said yes. It's ok tho. Been a heck of a ride so far and I have learned plenty along the way.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Ahh, I see. Well, good job then. :)

In other news, it seems as though after one of topprospect's commits was merged yesterday, the OP needs to be updated. Need to add another repo to the local_manifest.xml

http://review.cyanogenmod.org/#/c/24631/

<project name="CyanogenMod/android_device_samsung_celox-common" path="device/samsung/celox-common" remote="github" revision="jellybean" />
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
When you repo sync the celox project it's automatically added to the local manifest.

Roger
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
Yep - I can confirm that, just kicked off a build to update Nibbles and it was there after a sync.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'll take care of it. Do you think that could be an issue for the PAC build failing due to mk. file problems? I saw celox in my manifest last night and didn't know what to make of it...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
BMP What error are you seeing when building pacman?

Roger
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
This is what I get:

[CODE/bin/bash: vendor/pac/tools/getvendorprops.py: No such file or directory

build/core/product_config.mk:199: *** vendor/pac/products/pac_skyrocket.mk: malformed COPY_FILE "\". Stop.

** Don't have a product spec for: 'pac_skyrocket'

** Do you have the right repo manifest?][/CODE]

And this is the response that gs2 gave me at the time:

the first error i got aswell, in the source they changed something in the file getvendorprops.py but it will still build.

second error means the file in vendor/pac/products/pac_skyrocket.mk has and invalid path here or the file its looking for is not there, (check and see if the file is there, also check to see if i may have mispelled something):

# PAC boot logo
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/common/bootlogo/pac_logo_480x800.rle:root/logo.rle

I told him that his text looked good and he responded that he thought it may have had something to do with some commits being pulled from git.

https://github.com/PAC-man/android_vendor_pac/commit/1e99fe1be822a2ca3aa3c616b503676ad909a874

I've been doing my homework trying to hack this out, so to speak. As I told him, my product_config.mk is too big to post, but line #199 shows this:

$(check-all-products)

Honestly, I can't make heads or tails of it. He told me that you were successful, so I guess were back to 3 months ago with you holding my hand through a damn build:(. Seriously, brother, any help would be appreciated.

Took a step back and looked again and I saw what the real problem was, I think:

build/core/product_config.mk:199: *** vendor/pac/products/pac_skyrocket.mk: malformed COPY_FILE "\". Stop.

Looking at the pac_skyrocket.mk I see this:

# Check for target product
ifeq (pac_skyrocket,$(TARGET_PRODUCT))

# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_hdpi

# AOKP device overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/pac/overlay/aokp/device/skyrocket

# PAC device overlay
$(shell cp -f vendor/pac/overlay/pac/samsung/hdpi/frameworks/base/core/res/assets/images/android-logo-mask.png frameworks/base/core/res/assets/images/android-logo-mask.png)

# PAC boot logo
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/common/bootlogo/pac_logo_480x800.rle:root/logo.rle

# include ParanoidAndroid common configuration
include vendor/pac/config/pac_common.mk

# Inherit CM device configuration
$(call inherit-product, device/samsung/skyrocket/cm.mk)

PRODUCT_NAME := pac_skyrocket

GET_VENDOR_PROPS := $(shell vendor/pac/tools/getvendorprops.py $(PRODUCT_NAME))

endif

I see there's only one backslash....is that the problem? How should it look? This seems to be the way it's always been, but then again it took me this long to see the ACTUAL problem.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
When did you sync last? Looks like that getvendorprops.py file was removed from /vendor/pac/tools along with a few other files.

https://github.com/PAC-man/android_vendor_pac/commit/7eb9a388ae9be3ab162f27fdcd8bbe50d2dbea26

Your pac_skyrocket.mk is trying to reference that getvendorprops.py file which no longer exists.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Think a make clobber and fresh sync will do it?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Try adding the new celox common product to your local manifest, I think that's gonna do it, since that change was made yesterday and the day before my build compiled just fine with my tutorial, I'll keep digging in the repo files on github see if I can see anything else.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Was able to sync up using my tether(network at work won't let me sync or build) but have to wait till I get home to see if it will build. I'll let you know. Thanks:D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Well I'm guessing that you made the pac_skyrocket.mk file yourself? I didn't see the skyrocket in the PAC repos. I'm guessing you need to delete this line:

GET_VENDOR_PROPS := $(shell vendor/pac/tools/getvendorprops.py $(PRODUCT_NAME))
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Yes, I had to create one. gs2usr has made me a tut and this is one of the steps. As soon as I am successful, it will posted in the OP. He's been helping me get it together, and I don't want to post the tut until I am up and running. i don't want him to have to field a bunch of requests for assistance, he's probably tired of messing with me as it is. I'll be building as soon as I get home(around 7 EST) and will post his steps then if everything goes well.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
I haven't done a rrpo sync since my last build, so I'm just gonna cherry pick the changes so the sync doesn't Bork my build environment. :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
This is what I get after syncing:

Starting compilation
including vendor/cm/vendorsetup.sh
/bin/bash: vendor/pac/tools/getvendorprops.py: No such file or directory
build/core/product_config.mk:199: *** vendor/pac/products/pac_skyrocket.mk: malformed COPY_FILE "vendor/pa/prebuilt/pa_hdpi". Stop.
Device skyrocket not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 56, in <module>
result = json.loads(urllib2.urlopen(githubreq).read())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 406, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 519, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 444, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 378, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 527, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
/bin/bash: vendor/pac/tools/getvendorprops.py: No such file or directory
build/core/product_config.mk:199: *** vendor/pac/products/pac_skyrocket.mk: malformed COPY_FILE "vendor/pa/prebuilt/pa_hdpi". Stop.

** Don't have a product spec for: 'pac_skyrocket'
** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

:mad: Do I need to dump my vendor file and resync it?

Edit: rebuilt the entire build and vendor files and started from scratch. Same result. Hmph
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
I modified the “pac_skyrocket.mk” to what I have below and its compiling lets see if it completes and the ROM boots. I have a suspicion I may not have a boot logo but this is what I had to do to get it to compile.

Modified “pac_skyrocket.mk”

# Check for target product
ifeq (pac_skyrocket,$(TARGET_PRODUCT))

# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_hdpi

# AOKP device overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/pac/overlay/aokp/device/skyrocket

# PAC device overlay
$(shell cp -f vendor/pac/overlay/pac/samsung/hdpi/frameworks/base/core/res/assets/images/android-logo-mask.png frameworks/base/core/res/assets/images/android-logo-mask.png)

# include ParanoidAndroid common configuration
include vendor/pac/config/pac_common.mk

# Inherit CM device configuration
$(call inherit-product, device/samsung/skyrocket/cm.mk)

PRODUCT_NAME := pac_skyrocket

endif

Fingers Crossed Roger
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
You still have a reference to getvendorprops.py that you have not deleted yet.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
Success!!! PACMAN v16.1.0

Success!!! PACMAN v16.1.0

The my modified “pac_skyrocket.mk” did the trick I'm up and running PACMAN v16.1.0.

Package complete: /home/roger/pacman/system/out/target/product/skyrocket/skyrocket_PAC_jb-alpha-v16.1.0.zip
ba6d769c303cccbb87fbcef698d958a6 skyrocket_PAC_jb-alpha-v16.1.0.zip

Total time elapsed: 25 minutes (1506.900939030 seconds)
roger@roger-desktop:~/pacman/system$

Download Link: http://d-h.st/vNm

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I can't delete it because I don't have it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
Good going. Now throw me a bone and share the secret:confused:

This is mine:

# Check for target product
ifeq (pac_skyrocket,$(TARGET_PRODUCT))

# OVERLAY_TARGET adds overlay asset source
OVERLAY_TARGET := pa_hdpi

# AOKP device overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/pac/overlay/aokp/device/skyrocket

# PAC device overlay
$(shell cp -f vendor/pac/overlay/pac/samsung/hdpi/frameworks/base/core/res/assets/images/android-logo-mask.png frameworks/base/core/res/assets/images/android-logo-mask.png)

# PAC boot logo
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/common/bootlogo/pac_logo_480x800.rle:root/logo.rle

# include ParanoidAndroid common configuration
include vendor/pac/config/pac_common.mk

# Inherit CM device configuration
$(call inherit-product, device/samsung/skyrocket/cm.mk)

PRODUCT_NAME := pac_skyrocket

GET_VENDOR_PROPS := $(shell vendor/pac/tools/getvendorprops.py $(PRODUCT_NAME))

endif
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
I already gave you the bone before you asked for it scroll up or click here http://xdaforums.com/showpost.php?p=33869879&postcount=2494 :p

EDIT: Let me know if it worked for you.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I just PMed you, closer but still not quite there.....i sent you the code. Does that make sense? I don't know why it's different than yours. Sounds like a few months ago all over again.:crying:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Gotta say your finish time is pretty impressive, I have a quad core and 8g ram and ccache enabled and can't break under an hour, always between 60-68 minutes.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
I replied.

Roger

---------- Post added at 09:06 PM ---------- Previous post was at 08:54 PM ----------

Ha ha thanks keep in mind that was my first build now my ccache has PACMAN stuff in it my next build from a make clobber will under 20 minutes and a dirty build probably under 10.;)

Roger
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Geeezzz, my first one before ccache was 100 minutes.. :(
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] BMP7777:
I'm building! I only have a dual core so mine will be 3 hours or so. Gonna get it right and if it goes well maybe I'll be ready tomorrow night. Thanks to both of you! gs2, are still up for hosting?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] gs2usr:
Yesss Sirrr!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
All credit goes to gs2usr I just had to figure out the tweaks needed for the "pac_skyrocket.mk" file after the Pacman updates broke the Skyrocket build.

Roger:cool:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] m4570d0n:
Haha, I think we had a lost in translation moment here. What I've been trying to explain was that you needed to delete the line at the end of your pac_skyrocket.mk file that referenced getvendorprops.py. It was the next to last line right above the "endif". roger took that line out in his pac_skyrocket.mk, that's why his works. :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roger_n:
This is what I actually removed we were getting multiple errors.

# PAC boot logo
PRODUCT_COPY_FILES += \
vendor/pac/prebuilt/common/bootlogo/pac_logo_480x800.rle:root/logo.rle

GET_VENDOR_PROPS := $(shell vendor/pac/tools/getvendorprops.py $(PRODUCT_NAME))

Roger