yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] g.lewarne:
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
[HD2 Android Q&A, Help & Troubleshooting and Genera] mattfmartin:
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.
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
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 :p

Cash - not sure ... depends on how much help I get, but I'm willing to donate along the lines of US$20 or so...

hehe...

What server is that chat room on?
[HD2 Android Q&A, Help & Troubleshooting and Genera] dave_t321:
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.
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Nah, don't think so...not accroding to: http://xdaforums.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...:mad:
[HD2 Android Q&A, Help & Troubleshooting and Genera] KillaHurtz:
Lets break it down........

1st

Here's a brief intro I did a few days ago read it..

http://xdaforums.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
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
1- Yep, thanks...I actually used your info to create my system.img and boot.img files, which seemed to work fine.

2- I had contemplated this, but tried using the /system dump from a source thread here on xda somewhere. Maybe using an existing stock ROM would be better? Only thing with that means that if I were to eventually release a ROM here, I would have to get his permission...not always a big deal I guess...

I wonder why I have this kernel issue with my current test? basically I looked at the structure of m-deejays latest NAND build and copied it.

So I put initrd.gz and zImage into boot.img...but magldr gives me the kernel error on boot.

Also, I used m-deejays 9.4 kernel pulled from his current builds. I put the module files into lib/modules before creating the system.img.

Would really love more help.

If I was to use a donor ROM such as the one you mentioned, I would extract it. But then I'm a little unsure exactly which files need to be changed that are specific to the HD2...this is the sort of thing Im struggling with.

And then there's build.prop...what needs changed in there?

Appreciate your input! :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] KillaHurtz:
As I wrote that tytung was posting his Nexus One Gingerbread V.2

http://xdaforums.com/showthread.php?t=905060
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Hmmm...worth a look...but I still want to learn how to do it myself...porting from another devices build..
[HD2 Android Q&A, Help & Troubleshooting and Genera] KillaHurtz:
I got you dude, thats how I feel. I was blown away by gingerbread & wanna play with porting other builds aswell. I'm a bit overwhelmed trying to find all this info myself. It's nice to see someone else that doesn't know everything, but wants to lean:)
[HD2 Android Q&A, Help & Troubleshooting and Genera] atoore:
You really don't need to make a boot.img because you can just place the initrd.gz and the kernel inside /system. AFAIK,your build won't boot if you used wrong init.rc inside the initrd.gz. I suggest you to unpack the initrd.gz and put the init.rc from your ported Rom which you will find inside boot.img after you unyaff it. Make sure to set the permissions on the initrd.gz before you repack it because it will lose the permissions and you might face some issues. The correct permission is chmod 4755. So you just bassicly fallow the guide for miui exept when you building the ex2, but instead, make it yaffs image. Good luck and check out HTC-Linux-chat if you want further assistant.
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Thanks for your help!

I just did it that way with boot.img to follow the other NAND ROMs here in the NAND forum.

I had a look inside the initrd.gz from m-deejays gingerbread build, but it only has initrd in it...there's no init.rc as you say...is that the same thing?

I'll have another try again tomorrow, this time using another custom ROM as the source.

As I said though, I'm still not sure exactly which files need to be replaced that are specific to the HD2...I guess that MIUI tutorial is still pretty much the way it will be now for other builds?

Thanks again...I'll probably pop into the irc channel tomorrow for help :P

What server is that channel on btw?
[HD2 Android Q&A, Help & Troubleshooting and Genera] atoore:
You will need Linux machine to unpack the initrd.gz. I can't remember the commands from top of my head to unpack it. The Chanel server is on freenode.net.
[HD2 Android Q&A, Help & Troubleshooting and Genera] velayo:
I'm trying to make my own build from scratch also. Regarding what needs to be changed, as far as I have gone now, its basically the drivers. I might be wrong. But, I remember a while back when this started, that if you went to cotulla's kernel tree there were a bunch of different files, which in essence were pretty much the drivers. I gather that much from my experience whith linux. My idea would be that only the drivers have to be replaced or added to a stock rom to make it work with hd2. *Remember the tun.ko files?

I could be totally wrong. BUt I will keep reading this thread and help out as I learn. Thanks for starting it bro.

One more question, I've been trying to extract boot.img from an mdj build unsuccesfuly. I tried unyaffs, explor2fs and many other things and I'm still stuck.
[HD2 Android Q&A, Help & Troubleshooting and Genera] mattfmartin:
Just load that build up and adb pull the files out of the system
[HD2 Android Q&A, Help & Troubleshooting and Genera] KillaHurtz:
unyaffs works on that image, I know because I did it. Make sure you are doing it in linux with the command unyaffs. For this only works if I cd where the .img is

Ex: killahurtz@root# cd /home/killahurtz/Desktop/target folder/ <enter>

Then when your in the right directory, run the unyaffs commmand "unyaffs system.img"

Works everytime for me, but I had trouble until I did it exactly like that. Hope that helps bro :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Ok fixed the kernel issue, but now it gets stuck on the htc boot screen.

Here's the log: http://pastebin.com/npGbZjQF

It's stuck in a loop while doing something, but I dont know what? :mad:
[HD2 Android Q&A, Help & Troubleshooting and Genera] pongster:
Hey David! Great to see you got the kernel thing fixed...

When you say HTC bootscreen, you're in the screen just before the android lockscreen is supposed to be? and it won't proceed?

Try checking your framework-res.apk... or anything in the /system/framework you may have modified... that used to cause bootloops in my builds :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Hey S :)

Yea, the HTC bootscreen. having talked in the htc-linux irtc channel, it seems the init files might need to be modified...though Im still clueless as to what all that is...

I didnt change any framework...im trying to get this stock build to boot first, then play with stuff and see how it all works...

So very frustrating....:mad:
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Ok, I'm guessing my problems are with initrd and it's contents...at the moment im cheating, using tytungs one from his gingerbread build, but it's probably causing the problem.

So I'm trying to find what would need changed in here...init.rc?
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Hello,

I was on the same boat but finally got ROM kernel replaced and booted fine.

I used DFT LEO Stock Desire as base and extracted the img files, replace zimage in boot.img to MDJ_S9.5.OC, initrd.gz was side by but haven't touched it. Repacked the boot.img. Extracted system.img, placed and replace ko files in system/lib/modules, Then repacked the system.img.

Flashed the ROM using DFT flashing tools and got it working. Though it was my first attempt got success.

But I'm just learning and so far I have learnt how to change kernel, splash screen (Not how to edit since I cannot find info how to but just replaced logo.rle in initrd.gz/initrd/ from another custom ROM to get clean HTC then DFT), adding apks and few things about modifying graphical things like bootanimation.

Now I'm trying to find how to understand other things like:

What are symlinks?

What are odex and why we need to convert them to deodex?

How to replace the Android OS. i.e my ROM has Android v2.2 and how to downgrade to 2.1 or upgrade to 2.3. Which are the files to be replaced?

What is busybox?

And few other things...

But I feel android cooking is x50 times harder then WM. :o

BTW; the_scotsman, are you the same guy asking help about initrd in IRC? ;)

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Hey :)

Yep, same one in IRC :p

I remember seeing you around in the WM cooking threads...Android cooking is a whole different ball game...WM was easier, even without kitchens, but this is taking a lot more learning.

I didn't get time today, but thats what I was thinking of doing. Grabbing the stock DFT ROM, and swapping the module files and try to get that one working...then I know I'm doing everything right up to that point.

I guess Gingerbread requires some extra changes? Possibly in init.rc as darkstone said, but I wouldn't have a clue what.

Once I get a ROM to boot, I'll sit and study all the files a bit more, try to learn what they do etc...

I'm also trying to get my head around symlinks, busybox etc...WM seemed to have a lot more helpful reference stuff floating around, but all the android dev resources are full of geek talk that assume you understand what it all means lol...

Thanks for your post, I'll give it another try tomorrow :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
You're welcome.

Just now I tried to upgrade my ROM (Leo Stock Desire) to custom Nexus One Gingerbread by following "[Howto] Make your own Android Build for the HD2 " guide but end up sucking on splash screen (DFT). :(

Here is the logcat :

I don't know whether the guide is for upgrading or downgrading OS build. Some one if let us know how to change/upgrade/downgrade OS build, would be greatly appreciated but I'm not so good in finance to donate some $$. :o

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] Stephen:
I have been using this rom http://xdaforums.com/showthread.php?t=905060 since yesterday and I think it is excatly what you are looking for. Only two minor bugs. Usb doesn't work but I get arround it by using droid explorer and the keypad lights flicker but that is also easy to fix.

Awsome rom best yet, fast, stable, completly stock nexus one rom!
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Thanks but we aren't trying to make ROMs just because there aren't any or like copying the other ROM from other devices and porting it for our device.

We are studying how to update the ROM to different OS build. Not just Gingerbread but all the OS builds out there.

Not matter what the thread title says, we are trying to become developer and not users. ;)

Hope I haven't said loud. :p

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] noellenchris:
Hey scotsman and cracing, i've attached a txt file that I made to help me figure out what files NOT to use from builds since they were not compatible with HD2. It's actually for cyanogen mod, but it should help. I was also searching for a list of what drivers/files I needed for hd2. Well hope this helps you along, and I'll be watching your thread cause it could end up as a great guide to cooking android roms.

Chris

EDIT: HEY PONGSTER! Long time no see...
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Thanks mate, should be a big help!

Finish work in an hour, can't wait to get home and start playing with the builds again...;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] pongster:
hey buddy! sneaking in during some downtime... :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
I've been looking over init.rc files within the initrd.gz and comparing ones from different builds.

A lot of it is over my head...I understand some of it, but there are so many differences between different builds...it's really put me off...I'm beggining to think I might not bother.. :( :mad:
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Thanks a lot buddy. I hope it will help us more. :)

Just got 1TB hdd. So will come up with this after installing Windows and Linux in VM.

Keep going scotsman, wish you best of luck. :D

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] KrewsialNL:
I had the exact same issue when getting into the 'ROM cooking'. Though I really dont' have time for all the work and next to that, I think you're more of an advanced user then I am, I can only say hang in there and you will be able to do it :)

Good luck!
[HD2 Android Q&A, Help & Troubleshooting and Genera] noellenchris:
the initrd.gz has really evolved in the past 2 months. Cedesmith and a few others started changing the init file and more inside. They removed the rootfs and changed the way the system mounts partitions. This brought speed increases and some also caused file corruption.

Anyhow, I would try to stick with NAND only initrd.gz files to compare otherwise it will be confusing. Maybe you already are and I'm behind now....:)

I do know that I'm falling behind since I don't really have the Linux skills. I try but I'm slow....:P

Chris
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Yea, I have been comparing all different NAND ones, and they are still so very different, I have no idea what needs changed to get a build working...

Pity there's no "default" one, or is cedesmiths the best one to find and base from?

And then does Gingerbread require different settings?
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Ok I have compared DFT LEO Stock Desire ROM with original Desire Stock ROM of same version (2.29.405.5).

And found that almost all of the files are identical except 21 files which looks like Leo drivers, fixes, and changes. I have listed below:

.\build.prop	different
.\app\htccamera.apk	different (As said, the camera app has replaced to EVO ones)
.\app\htccamera.odex	only in Original Desire Stock ROM
.\app\superuser.apk	only in DFT LEO Desire Stock ROM
.\bin\su	only in DFT LEO Desire Stock ROM
.\etc\firmware\htcleo.acdb	only in DFT LEO Desire Stock ROM
.\lib\libgps.so	different
.\lib\libhtc_ril_wrapper.so	only in DFT LEO Desire Stock ROM
.\lib\libomxvidenc.so	different
.\lib\egl\libegl_adreno200.so	different
.\lib\egl\libglesv1_cm_adreno200.so	different
.\lib\egl\libglesv2_adreno200.so	different
.\lib\egl\libq3dtools_adreno200.so	different
.\lib\hw\copybit.qsd8k.so	different
.\lib\hw\gralloc.qsd8k.so	different
.\lib\hw\lights.htcleo.so	only in Original Desire Stock ROM
.\lib\hw\sensors.bravo.so	only in Original Desire Stock ROM
.\lib\hw\sensors.qsd8k.so	only in DFT LEO Desire Stock ROM
.\lib\modules\bcm4329.ko	different
.\xbin\busybox	only in DFT LEO Desire Stock ROM
.\xbin\su	only in DFT LEO Desire Stock ROM

-- 21 files listed

So if we replace these files in any of original Stock ROMs built for any other HTC devices, we should get it working on our HTC Leo. :)

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Ok guys, Finally cooked a working ROM taking everything from Bravo_Froyo_Vodafone_UK_2.33.161.2. :D

As I said above, you see what files are related to leo to get it working. There aren't so many files.

Note, do not replace everything I listed above. The file name can clearly mention what they are and whether you need to replace them.

But note, I had loop issue at htc animation and solved it after many flashes. It was due to files and folders permissions.

chmod -R 777 system/etc
chmod 755 system/bin/*
chmod 755 system/xbin/*
chown root:2000 system/bin/pppd
chmod 4755 system/bin/pppd
chown root:root system/xbin/su
chmod 4755 system/xbin/su

Did these and got the device booted perfectly. :D

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Thanks for the updates! You still using cotullas boot.img? More specifically the initrd.gs files?

I'lll have aplay on the weekend. You got Froyo working...now try to get Gingerbread working and I'll be happy! :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Nope, yes initrd.gs is from cotulla but zimage aka kernal is MDJ_S10.OC :)

But in which stock ROM Gingerbread is present? any idea?

However, i hope it get Gingerbread working using custom Gingerbread ROM also. :rolleyes:
[HD2 Android Q&A, Help & Troubleshooting and Genera] tdizzle404:
is this thread stil lactive?
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
I've personally put Android on hold while I play with WP7...bt might end up coming back and having another go :)
[HD2 Android Q&A, Help & Troubleshooting and Genera] tdizzle404:
Yea everybody's kinda went to wp7. "lol" welli hope to see ya release a gingerbread build.Thanks Man
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
I have already stopped android and will never think back about android cooking. Coz WP7 is almost same as WM cooking. Waiting for its tools and kitchen. :)

Android cooking was so hard and understanding its functions was 50% harder then WM for me. :o
[HD2 Android Q&A, Help & Troubleshooting and Genera] fabiere:
hey ;) have you do this in root (sudo su) or simple user in your linux?
[HD2 Android Q&A, Help & Troubleshooting and Genera] CRACING:
Doesn't matter I guess but yes as root. Not sudo su but I have created new login for root (sudo passwd). :)

Thanks...

Best Regards
[HD2 Android Q&A, Help & Troubleshooting and Genera] fabiere:
I have created a ROM. It boot but i have no data :s

Kernels: cotulla dft and mdj10.3
[HD2 Android Q&A, Help & Troubleshooting and Genera] the_scotsman:
Did you add the correct ril wrapper?
[HD2 Android Q&A, Help & Troubleshooting and Genera] fabiere:
The libhtc_ril_wrapper.so from dft nand
[HD2 Android Q&A, Help & Troubleshooting and Genera] fabiere:
Can you help me ?
[Captivate Q&A, Help & Troubleshooting] goo200:
Hi,

After doing the official froyo update for the rogers i896 captivate, I am no longer able to transfer programs to my internal SD card. I'm running W7 x64, and I haven't rooted my system yet. Any help would be appreciated, either an explanation or better yet a work around. Thanks in advance.

:mad: damn you rogers...
[Captivate Q&A, Help & Troubleshooting] goo200:
I meant cannot transfer apks
[Droid 2 General] NightGriffin420:
Good evening,

I am stuck and don't know what I should do next. I've tried reading through the topics on here, and also talking with people in IRC but no one can give me product specific help on the Droid 2. I was rooted, but hadn't updated to 2.3.20 yet, and was getting bugged daily about it. So I decided to try to flash my phone back to stock, so that I could do the OTA and update. Well, I did all of that (I think), and then did the OTA and rooted, and installing roms didn't work. So I then flashed with the most recent stock .SBF 2.3.20. I think it worked, my System Ver is "Version.2.3.20.A955.Verizon.en.US". I installed Rom Manager, and installed ClockworkMod. I have the ROM .zip file on my SD, but when I go to recovery mode, and click apply sd:update.zip. I get verification errors. I have version <e3> recovery. I was told I need <e2> recovery, so that it wouldn't verify and I would get pass that part.

I am honestly stuck. I don't know what to do. I don't know if I have the wrong version on my phone, or what?

Could someone please point me in the right direction?
[Droid 2 General] juliend:
What rom are you trying to install? And what clockworkmod app are you using? You want d2 bootstrap. You will not use the "install update.zip" option to install your rom. You select "select zip from sd card" and browse to find your rom file. All this info is in here, mostly in the stickies. There are probably good directions in the thread for the rom you are trying to install as well.
[Droid 2 General] NightGriffin420:
Thanks for the reply man, I am sitting here pulling my hair out.

I'd like to install GummyJAR. I am using Rom Manager app to install ClockwordMod Recovery. When I select the option "Install Rom from SD Card" in Rom Manager app, it just reboots the phone, and nothing happens. I have looked through the stickies, and looked in the thread of the Rom and still have troubles. I don't know what I am doing wrong, lol.
[Droid 2 General] newk8600:
You need to run koush's bootstrap in order for clockwork to actually work. Right now your clockwork doesn't have the workaround needed on the D2.
[Droid 2 General] NightGriffin420:
Thanks newk8600. I figured it out finally, that was my main problem. But Koush booted me in the right Recovery Mode and I was able to install the ROM successfully.

Thanks again!