Related
Ok, I'm loving Gingerbread, but m-deejay has been including Cyanogenmod in his recent builds, which I don't want.
I'm REALLY keen to work on my own Gingerbread build...but need pointers on the steps I need to take.
I want to use a clean custom Nexus One Gingerbread build, such as http://forum.xda-developers.com/showthread.php?t=885784
Then I'll have to replace the Nexus drivers and stuff with the HD2 ones...this is where the problem starts...how do I know which files are needed for HD2 specifically?
And then I need to add/remove apps etc to customise it?
I don't want anyone to hold my hand, just to at least point me in the right direction, as finding this information seems to be very difficult, unlike Windows Mobile cooking, which has lots of good tutorials...even though I'd expect that to be the other way around
I taught myself WM cooking & dev, but this is a whole new ballgame to me....
Appreciate any help I can get...
I'll happily donate a few $ to anyone who can help me get a stock build going...
No one able to shed ANY light? Give me ANY pointers?
Like I said, I'm willing to donate $ if I get help to get a ROM built...
Good pointers!!!
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
NemanjaLO said:
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
Click to expand...
Click to collapse
Yea I saw that, thanks...only problem is that it's an old build, and it's miui.
Where do I find the latest drivers etc? And how is a NAND build different? How do I package up a NAND ROM?
I was thinking the very same thing but when I started looking into it I got put off by the complexity and the time it would take.
Have you thought about just modding MDj's ROM, stripping it back to bare ginger and replacing the bits we dont want, this might be easier that building one from scratch.
Yea, it's a possibility...but I won't learn as much doing it that way...and I'd rather try to create my own than use someone else's hard work as a base, if you know what I mean.
I have time, and am willing to learn as much as I need to...I just need some pointers...there are plenty Android HD2 chefs now, surely one of them is willing to help out
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
I'd love to see this too!
SamanthaMarquez said:
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
Click to expand...
Click to collapse
Hey,
yes I've VERY interested...I'm hoping to get a stock-ish one together with my own little touches...maybe release one if I learn enough about it.
Any help you can give would be much appreciated...
Even to start with, a list of the basics...ie get ROM dump, extract xyz, do this...anything at all...
I just got back from a swim at the beach to relax, intending to come back and try to figure it out on my own with what help I can get from that page linked above...but if you have managed to get one together, thats even better
This might be of some use for windows users (I've successfully tried extracting MDJ's Gingerbread system.img with it).
http://android.modaco.com/content/z...-boot-recovery-system-userdata-kitchen-ready/
yea extracting is easy...but I would prefer to use a clean build to start from, rather than m-deejays...trying it using the guide in the link above with the Nexus S dump...having to use some donor files from m-deejays build though...still trying to get my head around it all
Well I gave it a quick try using the above guide, and it gives "NAND Kernel Open Fail".
I used m-deejays kernel, and put all the relevant files into the correct directories before making the system.img, and i put initrd.gz and zimage into boot.img, so I dont know what I did wrong...?
You don't use system.img on nand. You need to create a yaffs.img. Which I've never done before. I've only made builds the sd way, not nand. Maybe all you have to do is rename the .img after you create it. You should jump on irc, room #htc-linux-chat. You would get your answer in like 5 secs;p
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
g.lewarne said:
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Click to expand...
Click to collapse
Yea, something like that would be handy...but even to start with, I'd just love to know the basic processes needed to get a basic Android build running on the HD2, without having to rely on someone elses current build.
I tried the link above, and it did sort of help understand a little of whats going on...but this stupid kernel error is preventing me from knowing how my test build works/or doesnt work...
I mean I had too use m-deejays gingerbread dump to get some of the driver files etc from...but where does he get them from? Thats the stuff I dont know...
It's obviously not overly difficult as there are so many devs pumping out HD2 ROMs...would just love one of them to share the secrets
Cash - not sure ... depends on how much help I get, but I'm willing to donate along the lines of US$20 or so...
mattfmartin said:
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
Click to expand...
Click to collapse
hehe...
What server is that chat room on?
the_scotsman said:
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
Click to expand...
Click to collapse
Is it possible that the img files need to be created as ext4 rather than yaffs? I know gingerbread runs on the ext4 system (where froyo ran on yaffs2) but I'm not sure how this relates to building the rom.
Nah, don't think so...not accroding to: http://forum.xda-developers.com/showthread.php?t=897940
Ive tried a few more times but am still getting the kernel error...so I cant even test if my build works or not as it wont even boot...so very frustrating...
Lets break it down........
1st
Here's a brief intro I did a few days ago read it..
http://forum.xda-developers.com/showthread.php?t=897940&page=2
The above goes for any .img used with DAF, they are yaffs2 images.
2nd
The sensible option for a clean build would be an existing stock gingerbread rom on a sister device. AdamG just happens to make the cleanest Desire roms around. I've had my eyes on this build for a minute, check it out and see if this what your looking for. Oxygen v2.0-RC6
3rd
I've been able to unyaffs disect, reassemble and get some 'customized' roms running. They flash, boot, & work great.....but I lose root permissions. lol
I was acutally doing this with the 1.6 NAND rom of MDJ that came as a single.img
That particular file was just system.img & boot.img yaffs2'd together. After I disected it I was able to unyaffs the 2 images and edit/modify change kernels, etc. etc. The only problem I have run into is the root issue.
Conclusion:
----------------------------------------------------------------------------
I'd be glad to help out any way I can in porting a ROM worthy of our devce
Any serious inquries can be directed to my inbox for private discussion on gtalk .
I'm no dev and am in no way claiming to be. I do have some findings and that's why I'm offering my help. Cheers
I guess this thread can be a simple way for us to ask one of the devs the difficulty of a specific task that they may want completed... Not really demanding it or anything, but just seeing if it is possible/probable
So, may i ask just how hard it would be to port the "ClockworkMod Recovery (3/30/11 Bugfix)" from the fascinate to the continuum? i am just curious, because i spend a decent amount of time in ClockWork just backing up and such, and that looks niceee
Also, kinda going along with the other request, is there a way to get the kernel that had CWM built into it working without the video problems when entering CWM?
Lastly, the Reboot Options... I hope that we can get that working too
Thank you again Devs for looking at our phones And we appreciate all you do for us
trailblazer101 said:
I guess this thread can be a simple way for us to ask one of the devs the difficulty of a specific task that they may want completed... Not really demanding it or anything, but just seeing if it is possible/probable
So, may i ask just how hard it would be to port the "ClockworkMod Recovery (3/30/11 Bugfix)" from the fascinate to the continuum? i am just curious, because i spend a decent amount of time in ClockWork just backing up and such, and that looks niceee
Also, kinda going along with the other request, is there a way to get the kernel that had CWM built into it working without the video problems when entering CWM?
Lastly, the Reboot Options... I hope that we can get that working too
Thank you again Devs for looking at our phones And we appreciate all you do for us
Click to expand...
Click to collapse
i know imnuts is working on reboot options for ya....as for the rest...hopefully
rooting
Also if ive tried all unroot / root Fashions available does this mean my phone is unrootable? and how do you know if you have root i know on my hero it changed a version number on my continuum it didnt change anything but insisted on saying i had root access when i know i did not. because i did not have access when i tried to install the clockwork recovery posted by adryn
nitsuj17 said:
i know imnuts is working on reboot options for ya....as for the rest...hopefully
Click to expand...
Click to collapse
I need to find a time one of you themers are online in IRC to try and get that fixed. All of my attempts have resulted in them not working so far. I think the issue is in android.policy.jar as that is what I've been able to capture as the issue with logcat.
Also, I'm working on fixing recovery for you guys and just posted a topic so you can pick the color you want it to be.
Can't wait until all of this comes into motion
Thanks again man!
What else do we need to start getting some custom roms like CM7 and others like XxVirusxX. What is need to take an AOSP and build it for our Elocity? I recently got and Evo 4g rooted is same day, now running CM7 rom, tiamat kernel, viper undervolt Is it possible to get these to work on this elocity?
its possible to port components and features of other roms, or to compile other roms for the a7. i compiled a clockworkmod recovery that i have posted on my twitter and elsewhere than you can use to conveniently backup/switch/restore roms and data with, which will aid in additional roms being made accessible, as loading them (and recovering from them) will be more convenient.
also gotta good /device setup for the naz10 going for use in rom compiling. mebbe i'll post it up for others when i have it near complete.
How did you get the clockwork mod to flash? Also I'm assuming you finished the key mapping that hadn't been done?
bestialbub said:
its possible to port components and features of other roms, or to compile other roms for the a7. i compiled a clockworkmod recovery that i have posted on my twitter and elsewhere than you can use to conveniently backup/switch/restore roms and data with, which will aid in additional roms being made accessible, as loading them (and recovering from them) will be more convenient.
also gotta good /device setup for the naz10 going for use in rom compiling. mebbe i'll post it up for others when i have it near complete.
Click to expand...
Click to collapse
Is that why it has been so quiet in here haha
Sent from my Mynized EVo 4G
smal you can't say it wouldn't be awesome to have half the stuff you have for evo for the elocity
rombold said:
smal you can't say it wouldn't be awesome to have half the stuff you have for evo for the elocity
Click to expand...
Click to collapse
Oo of course, with out a doubt, Im just sitting back waiting for one of these great devs. Hopefully they got something good from the kernel Source
Sent from my Mynized EVo 4G
i might throw my sifted kernel source up for dev types to browse thru. just the added and modified source from elocity, not the whole package, so one can see what elocity did. pretty sure i spotted changed accelerometer settings in the kernel source that could aid in correcting that issue on a kernel level possibly.
i'm still moving slow without adb access. either have some service or kernel reconfiguration to do for that one. too many fun things to do, not enough personal time to get em all done swiftly.
Sent from my X10i using Tapatalk
Time will only tell and I got plenty of it
ayup, got the key mapping working with the latest clockworkmod recovery.
http://twitter.com/#!/bestialbub
it was confusing because it seems the newest version has a secondary back button. had to scratch my head a couple seconds until i figured to map it to the volume key and forget the key combinations for toggling display on and off.. tho power+search might toggle it (not really a useful feature of any concern).
oh, if you look at the devices existing keylayout, the volume or 'media_key' has the value of 213.
i left out instructions for flashing with apx on purpose. if you don't know how, you probably shouldn't, because i don't have a fix today for you if you break your device some how. i'll see about posting some complete apx backup scripts, along w/ a nvflash pack that doesn't have the added rom bloat + stock and my cwm recovery image. but that might be like in a week. i got that adb to work out, file permissions to finishing documenting for fun, and repacking the factory rom for cwm for fun.
nothing to exciting towards new features regular users will enjoy today, but something romheads/chefs/modders/themers will like to make software work and testing easier.
I Gotta get another male/male USB Wire, and I'll Be Watching out for Updated on This and Following you on Twitter no Also, Im Willing to try just as long as the directions are clear. Right Now im waiting on some HTC Sense 3.0 for the EVO. So im on XDA all Day haha
ROMBOLD: Check Your PM
bestialbub said:
i'll see about posting some complete apx backup scripts, along w/ a nvflash pack that doesn't have the added rom bloat + stock and my cwm recovery image. but that might be like in a week.
Click to expand...
Click to collapse
Awesome... <3
Either one would be awesome Amon ra or CWM recovery Wonder how much the tiamat kernels require to work for us?
cwm recovery is done and available for use. questions; leave at the link you download 'em from.
http://twitter.com/#!/bestialbub
i also have the factory rom repacked and install script made for use w/ cwm (and maybe factory) recovery. this should step up the ability for folks to mod and theme the existing roms. will post tomorrow, then mebbe post an nvflash/apx pack for backup/restore/recovery flashing before i get started on themeing to follow.
Hey been looking around through xda for a bit but couldnt find anything.
Im after a guide on how to start making my own ROM.
If anyone could post a link to a guide or let me know the important steps on how to start.
Had a U8800 for a bit and love it and want to make it perfect
Cheers
first you have to understand some programming language , specifically c or java, but most high level languages are similar
then I am told that you need to have a deep understanding of linux file system, which I don't... so I am not qualified to give you anymore advice...
For me I started out trying to port clockwork recovery to u8800. There's a guide by koush that gives the most basic steps on how to do this. Following that and doing a lot of reading I was able to get it pretty good and obviously Geno has since taken over to basically perfect it.
I think the recovery is a good place to start since it's similar to the normal android os but just really cut down. Try building it from source and work out how to get it on the phone and booted.
As well as Stockwell's very useful suggestion (do you have a link to the specific koush guide that you found useful, Stockwell?), you might want to go to XDA's Chef Central, and cyanogen's advice at :-
http://forum.xda-developers.com/showthread.php?t=667298
below are the links to "further reading" that I've extracted from that post.
Android Developer Guides: http://d.android.com
Working with AOSP source: http://source.android.com
Platform Developer Guide: http://pdk.android.com
Android Gitweb: http://android.git.kernel.org
Git Ready (Git tips and tricks): http://www.gitready.com/
Building CyanogenMod: http://wiki.cyanogenmod.com/index.ph...ng_from_source
How Dexopt works and what are those odex files: http://android.git.kernel.org/?p=pla...5936;hb=master
stockwell said:
For me I started out trying to port clockwork recovery to u8800. There's a guide by koush that gives the most basic steps on how to do this. Following that and doing a lot of reading I was able to get it pretty good and obviously Geno has since taken over to basically perfect it.
I think the recovery is a good place to start since it's similar to the normal android os but just really cut down. Try building it from source and work out how to get it on the phone and booted.
Click to expand...
Click to collapse
Would you please give the link to koush's guide?
Here's the guide by koush:
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
I think it's missing some stuff though. At the very least it looks like you would need to do
. build/envsetup.sh before running lunch. I think there was another problem but I can't remember what it was now.
Thanks everyone for the info.
I am studying IT at the moment and am about to learn java so sort of wanted something to have a go at while learning
As the title says, what would it take to get rom manager working on the a500.
I ask this because of the appextractor that would be great to have working while switching between roms and I also feel like having rom manager support shouldn't be that hard. We have CMW ported and yet rom manager doesn't see it as having it, and that is all that is needed. so what would it take?
We have CWM because it's a custom port by Thor, and he's seen fit to keep his modifications to himself rather than submit them back to CWM.
We do thank him for his work, but his current attitude is stifling futher development.
Oh, I see thanks for the info FloatingFatMan, I didn't know that. I am new to the tablet stuff, but I have been in to the phone side of android for about a year and a half. I just assumed that it was something else. Didn't know Thor kept his mods to himself, but i assumed so you know what they say lol