Hi, I've been recomended by a friend to use this kitchen instead, and I admint, it does seem alot simpler, or atleast a little more user friendy.
But the only guids I find are on EVK, can anyone point me in the right direction please?
thanks
Here is the only one I know but this thread is also useful
http://forum.xda-developers.com/showthread.php?t=628948
bobsbbq said:
Here is the only one I know but this thread is also useful
http://forum.xda-developers.com/showthread.php?t=628948
Click to expand...
Click to collapse
Yeah Ive already seen that, I was looking for something more on the level of tutoring you have given me
A little bump
Hi all,
After seeing all the great work and many different ideas people had for their themes and roms, I figure instead of asking for a bunch of signed files, I'd try to figure this out and learn how to do it myself.
I'm looking, for example, how to use RegawMOD's matrix bootscreen or Godson's else's taskbar etc.. on Damageless or Fresh's ROM. I figure I'd start with just the looks and themes before learning how to do anything that I could really screw up. Or how to make my own clear lock screen...
Anyway I'd appreciate any help or even a point in the right direction!
Aloha
808
Right direction...
http://wiki.xda-developers.com/index.php?pagename=CDMA Hero Guides
808rides said:
Hi all,
After seeing all the great work and many different ideas people had for their themes and roms, I figure instead of asking for a bunch of signed files, I'd try to figure this out and learn how to do it myself.
I'm looking, for example, how to use RegawMOD's matrix bootscreen or Godson's else's taskbar etc.. on Damageless or Fresh's ROM. I figure I'd start with just the looks and themes before learning how to do anything that I could really screw up. Or how to make my own clear lock screen...
Anyway I'd appreciate any help or even a point in the right direction!
Aloha
808
Click to expand...
Click to collapse
Start with the files in system/framework framework.apk or framework-res.apk. Then in system/app rosie.apk
beezy420 said:
Start with the files in system/framework framework.apk or framework-res.apk. Then in system/app rosie.apk
Click to expand...
Click to collapse
If I find the files I'm looking for can I just push them from one ROM to the phone through ADB? As for the apk, is it just a zip i can rezip? And then jsut push? Thanks again!
obannvi said:
Right direction...
http://wiki.xda-developers.com/index.php?pagename=CDMA Hero Guides
Click to expand...
Click to collapse
Thanks! Didn't realize the wiki had that stuff, just remember seeing how to root in there before. I'll check it more often!
Hey, I think the whole community would appreciate it if you searched on this, as I already wrote a guide for it.
http://forum.xda-developers.com/showthread.php?t=551711
bikcmp said:
Hey, I think the whole community would appreciate it if you searched on this, as I already wrote a guide for it.
http://forum.xda-developers.com/showthread.php?t=551711
Click to expand...
Click to collapse
Yep, bikcmp is the one who got me cooking.
atoz350 said:
Yep, bikcmp is the one who got me cooking.
Click to expand...
Click to collapse
which unyaffs did you get cuz there are three on there unyaffs, unyaffs.c and unyaffs.h? I am very new to this
Guys, I wanted to learn how to make one. I know the basics, but wanted to know what language it's written in and what are all the functions it supports and their syntax.
Where can I find this information? I tried searching but did not find anything.
edit: found a very helpful thread, http://forum.xda-developers.com/showthread.php?t=641223
making an update.zip isn't that hard, the only part that actually requires a bit of learning or familiarity is the update-script. just look at examples from themes and ROMs, and you'll likely get the hang of it really quickly. lastly, use a signing utility(i use autosign).
justinisyoung said:
making an update.zip isn't that hard, the only part that actually requires a bit of learning or familiarity is the update-script. just look at examples from themes and ROMs, and you'll likely get the hang of it really quickly. lastly, use a signing utility(i use autosign).
Click to expand...
Click to collapse
Thanks. Someone else had mentioned that. I did start looking the script and the update.zip file. But I wanted to figure out additional commands. What other functions are available for our disposal.
You searched it good alright. Let's see what 'make update.zip' comes up with on google. Oh my gosh, HOW TO MAKE UPDATE.ZIP FOR ANDROID PHONES.
http://lmgtfy.com/?q=make+update.zip
bikcmp said:
You searched it good alright. Let's see what 'make update.zip' comes up with on google. Oh my gosh, HOW TO MAKE UPDATE.ZIP FOR ANDROID PHONES.
http://lmgtfy.com/?q=make+update.zip
Click to expand...
Click to collapse
Thanks hot shot.
Why dont you follow that link and see what it says for yourself. None of the links give me what i want. I already know that I can backwards engineer a update.zip. That's trivial.
I want to know other commands that are available. Someone has to know. Unless even the devs started to just modify old zips and go from there. That I can do too.
I swear there are people like you just searching threads to post such remarks instead of real technical or meaningfull posts.
okay I found some syntax for update script. Check out this thread.
http://forum.xda-developers.com/showthread.php?t=641223
jackal424 said:
okay I found some syntax for update script. Check out this thread.
http://forum.xda-developers.com/showthread.php?t=641223
Click to expand...
Click to collapse
Excellent find OP.
jackal424 said:
Thanks hot shot.
Why dont you follow that link and see what it says for yourself. None of the links give me what i want. I already know that I can backwards engineer a update.zip. That's trivial.
I want to know other commands that are available. Someone has to know. Unless even the devs started to just modify old zips and go from there. That I can do too.
I swear there are people like you just searching threads to post such remarks instead of real technical or meaningfull posts.
Click to expand...
Click to collapse
word.....not exactly helpful.
I know that I found something similiar to what you're looking for....now I just need to remember where...
I know a lot of the files are going up on here....
http://android.git.kernel.org/?o=age
But how far are we away from having the entire source code? What is/are the magical file(s) that we need? I see that the most recent launcher is a few weeks old...
Anyone? I know there must be a way to find this info so if you could even just guide me to where I need to look.....?
AFAIK, everything to build a basic ROM is out there in AOSP... what is missing is device specific copyrighted drivers and libraries and Google Apps.
Can someone (Mod/OP) rename this thread to something that give us half a clue as to WTF it's all about?
attn1 said:
Can someone (Mod/OP) rename this thread to something that give us half a clue as to WTF it's all about?
Click to expand...
Click to collapse
Why don't you go find another thread to post in if you have nothing to offer?
Thanks Craig, that is basically what I was looking for.
Ok, folks... Some very industrious devs have worked out a more complete vendor tree for the Eris at http://github.com/punk-kaos/vendor_htc_desirec. I've synced it into -
$AOSPsource/froyo/vendor/htc/desirec <-- this is the level that all of the files are at (i.e. everything under vendor_htc_desirec/ from the repo)
I'm a little lost as to where to go from there. I've looked at multiple vendor trees, and everyone seems to do things a little differently each time.
Can any of you point me in the right direction?
Thanks!
Kudos to Kaos, jamezelle, conap, vinylfreak89, & darchstar! You really rock.
Ok, so I copied it all under
$AOSPsource/froyo/device/htc/
Since that's where the dream, passion, etc. stuff is.
Now, I do a - 'source build/envsetup.sh' and it seems to find the desirec stuff.
including device/htc/desirec/vendorsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh
I'm stuck at what to do a 'lunch' on now. In the vendorsetup.sh, there's a 'cyanogen_desirec-eng'.
When I 'lunch cyanogen_desirec-eng', I get -
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/htc/desirec/froyo_desirec.mk]]: "vendor/htc/desirec/device_desirec-vendor-blobs.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?
Getting closer!
Applause
I read you posts and see the questions you ask(that never seemed to get answered)and you will post some stuff you have learned all to help someone else who might want to get started dinking around with a pretty cool open source operating system. I applaud you for asking questions and when no one replies you answer it again yourself. You are the true definition of open source!
Im fairly new to this whole scene so excuse the "dumb" question but what exactly is a vendor tree?
You are stellar. I am going to try and port a froyo rom and then start to build something from the ground up. The questions you ask and the information you provide is invaluable. Want to put a rom project together?
Sent from my FroyoEris
good progress
paperweight said:
I read you posts and see the questions you ask(that never seemed to get answered)and you will post some stuff you have learned all to help someone else who might want to get started dinking around with a pretty cool open source operating system. I applaud you for asking questions and when no one replies you answer it again yourself. You are the true definition of open source!
Click to expand...
Click to collapse
Thank you. Many devs have helped me to learn all that I have learned. They are busy people just like most of us. Some of them probably don't pay attention to the forum that often. Some just have their own projects. Some hang out in IRC instead of looking in here. Actually, I've learned a lot in IRC, even when I just kick back and lurk. I really do want to get all of the info that I learn out here in the forum where 'noobs' are lurking. I've found that there is a certain level of detail that is available fairly easily with the search box. There's a point where it takes some real digging to figure things out. My hope is that it won't always be that way.
I tried manually taking all of the files and settings from the vendor tree and inserting them into SgtShultz. It didn't fix things. So, I'm thinking that either it really does have to be compiled in or this tree and AOSP Froyo don't quite mesh. Since there is some source code in the tree, that is most likely the issue.
I never could get the lunch command to work. That file is not there, and I'm still not sure what it should contain if I were to create it. Getting this to work would really help both of my other current projects...
MacShannon said:
Im fairly new to this whole scene so excuse the "dumb" question but what exactly is a vendor tree?
Click to expand...
Click to collapse
When you compile AOSP and/or variants from source, there is generally no device specific code - like drivers for instance. The vendor tree just sets everything up to add those proprietary files and settings into the mix, so that the resulting ROM will actually be usable. That's the idea anyway!
thanks for all the work you've been doing recently! i've followed the other thread as well... and am happy to say that i use (and appreciate) your work!
gnarlyc said:
When you compile AOSP and/or variants from source, there is generally no device specific code - like drivers for instance. The vendor tree just sets everything up to add those proprietary files and settings into the mix, so that the resulting ROM will actually be usable. That's the idea anyway!
Click to expand...
Click to collapse
I also have a "dumb" question.
If this is for the Eris, then why are the files under the "desire" name? I thought the eris was based on the hero platform or am I missing something obvious here?
gnarlyc said:
I'm a little lost as to where to go from there. I've looked at multiple vendor trees, and everyone seems to do things a little differently each time.
Can any of you point me in the right direction?
Click to expand...
Click to collapse
Have you tried the steps from this thread?
I am currently working through them, but had to stop because it's time for me to get ready for work.
I have gotten through the step where you copy the vendor files to the htc folder
sbarne3 said:
I also have a "dumb" question.
If this is for the Eris, then why are the files under the "desire" name? I thought the eris was based on the hero platform or am I missing something obvious here?
Click to expand...
Click to collapse
Great question! HTC's 'internal' name for the Eris is 'desirec' apparently. (Note that it's 'desirec' not 'desire'.) It was somewhat confusing when they came out with the Desire...
sbarne3 said:
Have you tried the steps from this thread?
I am currently working through them, but had to stop because it's time for me to get ready for work.
I have gotten through the step where you copy the vendor files to the htc folder
Click to expand...
Click to collapse
Looking at it now. Thanks!
gnarlyc said:
Ok, so I copied it all under
$AOSPsource/froyo/device/htc/
Since that's where the dream, passion, etc. stuff is.
Now, I do a - 'source build/envsetup.sh' and it seems to find the desirec stuff.
including device/htc/desirec/vendorsetup.sh
including device/htc/dream/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/sapphire/vendorsetup.sh
I'm stuck at what to do a 'lunch' on now. In the vendorsetup.sh, there's a 'cyanogen_desirec-eng'.
When I 'lunch cyanogen_desirec-eng', I get -
build/core/product_config.mk:190: *** _nic.PRODUCTS.[[device/htc/desirec/froyo_desirec.mk]]: "vendor/htc/desirec/device_desirec-vendor-blobs.mk" does not exist. Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?
Getting closer!
Click to expand...
Click to collapse
Did you run extract-files.sh? Iirc, the vendor_blob file is created when you run it.
Sent from my FroyoEris using XDA App
Resun said:
Did you run extract-files.sh? Iirc, the vendor_blob file is created when you run it.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Holy cow! I did not run it because I already have all of those files in place. It didn't occur to me to check and see if 'extract-files.sh' does something more than just pull the files.
Thank you.
Np, been working on my own, I've done the same thing about 10 times in the past week.
Sent from my Froyo Eris using XDA App
So, I commented out all of the 'adb pull' statements in the 'extract-files.sh' script, since the files are already there. Now I see that extract-files was creating the ...blobs.mk file under vendor/htc/desirec instead of device/htc/desirec. So, I changed that and ran it all again...
cd $AOSPsource/froyo
device/htc/desirec/extract-files.sh
source build/envsetup.sh
lunch cyanogen_desirec-eng
And this gives me -
build/core/product_config.mk:192: *** vendor/htc/desirec/froyo_desirec.mk: PRODUCT_NAME must be unique; "desirec" already used by device/htc/desirec/froyo_desirec.mk vendor/htc/desirec/froyo_desirec.mk . Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?
Here I go again! Thanks for all of the help. I really want to get this working, so that it can be scripted.
gnarlyc said:
So, I commented out all of the 'adb pull' statements in the 'extract-files.sh' script, since the files are already there. Now I see that extract-files was creating the ...blobs.mk file under vendor/htc/desirec instead of device/htc/desirec. So, I changed that and ran it all again...
cd $AOSPsource/froyo
device/htc/desirec/extract-files.sh
source build/envsetup.sh
lunch cyanogen_desirec-eng
And this gives me -
build/core/product_config.mk:192: *** vendor/htc/desirec/froyo_desirec.mk: PRODUCT_NAME must be unique; "desirec" already used by device/htc/desirec/froyo_desirec.mk vendor/htc/desirec/froyo_desirec.mk . Stop.
** Don't have a product spec for: 'cyanogen_desirec'
** Do you have the right repo manifest?
Here I go again! Thanks for all of the help. I really want to get this working, so that it can be scripted.
Click to expand...
Click to collapse
Shouldn't have it in both, should only be in the device subfolder.
Resun said:
Shouldn't have it in both, should only be in the device subfolder.
Click to expand...
Click to collapse
Thanks again! I know better than to do a drive by like that. I spent two minutes testing, posted the results, and then left to run errands for most of the day.
I'll try again when i get home.
so ive patched up the vendor on my computer (some files were pointing to devices/htc/desirec) and when i finally got it to behave i ran into something worse..
Code:
build/core/combo/TARGET_linux-arm.mk:39: *** Unknown ARM architecture version: armv6. Stop.
i ended up changing the lunch to desirec-eng because it wouldnt resolve the product name... im not a dev but i sure have a nose for this sort of thing, and help or an armv6.mk file would be appreciated