Update:
Fixed kaiser and polaris version info for NBH
Fixed issue where if a source code pull failed, any later attempts would fail as well
Fixed issue with updating bootenv
It's my first meaningful contribution! I put together a couple of scripts and some other stuff to make it really easy for me to create a flashable NBH from the latest kaiser kernel sources.
Many thanks to dzo, JeckyllHavok, quitlahok, rzk333, -Arturo-, kallt_kaffe, the folks at www.codesourcery.com, poliva at the htc-flasher project on googlecode, and all the people who contribute to developing, testing, etc Android on HTC devices.
Note that none of the files these scripts download are mine. They were not created by me. They all belong to other people who have contributed much to the community.
The only things that I've made are:
- crnbh (which uses commands from scripts in the htc-flasher project)
- update-workspace
- everything under the patches and signatures directories
(just the patches, not the things they patch)
This requires an active internet connection to use. I don't plan on maintaining this but I thought I'd put it out there in the hopes that it could be put to good use or something.
Download the attached file
Extract to your home folder (important)
Read the README
If you want to change it, make it better, please do! Just mention me in the credits. Also please PM me so that I know it was helpful. Thanks!
Good luck!
May I ask what this does differently than my NBHCreator?
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
LoveMyPhone said:
First off, sorry for stepping on your toes I didn't notice yours until I was halfway through making it, and I only posted it because I figured it might be something to look at for ideas or something... I don't know how to describe what's different so I'll just post what it does...
update-workspace:
Gets the latest kernel source code
Gets the latest tinboot source code
Patches tinboot.S so that it uses the zImage and initrd.gz that are built later
Gets the latest bootenv source code
Patches buildInitrd so that it is a little bit safer (maybe)
Gets Yang from the htc-flasher project on googlecode
Patches the htc-flasher makefiles so that they only build Yang and HTCFlasher and then install them locally (to avoid cluttering the user's system)
Gets the arm toolchain from codesourcery.com and extracts it to the android-ezb directory
Builds and installs Yang (to the android-ezb directory)
then crnbh:
Builds the kernel source code
Builds initrd
Builds tinboot
Uses nbhmerge to create the output.nb file
Uses Yang to create the NBH file for the device
Click to expand...
Click to collapse
NO...NO...NO...
Don't be sorry...
I don't care if you make your own and post it...
I was only wondering because your OP was lacking in information as to what this did.
Actually the same thing happened to me just before I released my nbhcreator, loserskater released his nbh editor.
Your creator does some things mine doesn't (YET)
like actually pulling tinboot etc...
things like that I was putting off as an option for a later release.
other than that I am building the output very similar.
Now that I am in this deep I wish I would have gone without the GUI.
Seems to be creating cross-platform issues.
Well, please feel free to integrate any of it into yours. The two files are just shell-scripts written for bash... nothing more
Related
SuperJustKitchen v0.7 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
For more information on the kitchen, please read: http://forum.xda-developers.com/showthread.php?p=4288668
Word of warning:
None of the new EXT's have been tested and fixed for the Herald, Opal, Hermes AND Artemis. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here.)
howdy,
i just gave it a shot, downloaded all files and wanted to look into it but it seems i have to look somewhat deeper to just set the kitchen up...it doesnt work following your walkthrough guide...
so for now the impression left behind is:
nice homepage
frustrating setup..for a time pressed person
greetz
Sorry, that's because the setup has changed a lot since I first started the kitchen for the Herald.
It's pretty simple.
Create a folder in your C drive and name it Kitchens.
Within that folder create a folder called SuperJustKitchen.
Dump the contents of the the main files into this.
Go into the Working_Directory and dump the contents of the other 7z files.
I'll probably be making an auto install pretty soon.
Dharam's Kernel Development Tutorials
Since many of the S2 Kernel Developers have moved on or will be moving on to the Galaxy S3, I feel we need more developers for the S2. No offence to those who have moved on, even I would have done the same if I could afford one
Anyways, there will be many people who will have the knowledge of coding and stuff, just wont know how to build kernel's and all...
So here I present the Kernel Development Tutorials for the Galaxy S2. It will be similar for many other devices and so you can refer the same also if you are developing for any other device
The thread will be similar to my previous tutorials for the Galaxy 3, but based on MOD's for the S2.
I do not present myself as an expert of things, there are many great developers for the device including codeworkx, chainfire, gokhanmoral, simone201 and many many others which I am just skipping for the time being. Credits for their work will be provided as and when refered to.
I am also learning stuff myself, and so I maybe wrong at many places. I would request other developer's to keep a look on this thread and help out me and others whenever required. You guys have better knowledge, and it is a great thing to share the knowledge.
I will explain everything Step by Step.
If you got time to learn/develop join in.
If you get some step working and a fellow developer cant get it, please help each other by answering everyone's doubts.I cant reply to each and every query always.
Most of the code is to be run in the terminal. So I wont be mentioning to Open terminal every time.
I would like to thank marcellusbe who was the first one to make a proper custom Kernel for Galaxy 3, who taught me how to build a kernel, and also lot of other help
Note:
Please do not post useless messages.
If you dont know coding, please learn that first.
Do not flood my inbox with PM's. I will not respond to PM's regarding Kernel Development. Please post in the thread, so that everyone can learn.
[*]I AM NOT RESPONSIBLE IF YOU HARDBRICK YOUR PHONE, DOING ANY OF THE FOLLOWING STEPS
A request to all the people, please do not vote down this thread directly. It will take some time to build the tutorials step by step. If you have any doubts, then this thread will be similar to http://forum.xda-developers.com/showthread.php?t=1186409
I have got many requests to do a similar series for the S2, and so I am doing it.
This series will also be posted at www.androidnova.org - Checkout the website for latest Android News, Reviews and other cool stuff
Step 1: Setting Up The Build Environment
Installing Ubuntu.
1. Download Ubuntu x64 from http://www.ubuntu.com/download/desktop
2. Install Ubuntu directly or as a Virtual Machine ( I prefer direct installation)
3. If setup is Virtual Machine, Please dedicate enough RAM and processor for the Kernel to build fast, else it will take ages
Logging In As Root
1. When Ubuntu first boots, login with the username and password you mentioned while installing.
2. Open Terminal
3. Use following command.(Always the code after $/# is the one to be used. The one before that just specifies [email protected]:~)
## Anything after ## is a comment by me.
Code:
[email protected]:~$ sudo passwd
[sudo] password for dharammaniar: ## Enter password which you used to login.
Enter new UNIX password: ## Enter Password for root(it can be same as your prev password)
Retype new UNIX password: ## Re-Enter Password for root
passwd: password updated successfully
[email protected]:~$ su
Password: ## Enter the root password
[email protected]:/home/dharammaniar#
4. Once you get the last line as above means you now have root access.
5. Now logout from this user and login with username as root
6. On starting Terminal now, you should get
Code:
[email protected]:~#
Setting Up Build Environment
1. You should always be running as root.
2. Go To System->Administration->Synaptic Package Manager
3. Search for ncurses-devel
4. Install libncurses5-dev.
5. Download the toolchain. You can find it in the AOSP Source. I will also upload it soon enough.
Downloading Source
Downloading The Source
1. Download the Update4 Source from http://opensource.samsung.com/ or https://github.com/CheckROM/DK_S2_ICS_KERNEL/tree/5ec9752c34cedf3e8df9e887ecad6db9337de927
2. Download the initramfs from https://github.com/CheckROM/DK_S2_ICS_INITRAMFS/tree/d85b2201b79588e70387d3df0ffd2f83d741c4ac or maybe request some developer to post how to extract initramfs from stock samsung kernel. Even I am trying to figure that out...
(If any developer is reading this, and can help out, We would be grateful)
3. Create a folder named S2.
4. Inside that have 2 folders, 1) Kernel 2) initramfs
5. Kernel folder should have the source e.g. arch, drivers and all
6. initramfs folder should have the files init.rc and stuff
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Last Reserved... I will make use of these posts as and when required, so request the MOD's not to delete any of the above posts
Sure thing i got all the time i need. I was waiting for someone explain this xD
Nice to see this post. .Sir,I have send you PM if you don't mind please see it .
Really nice iniciative
Good luck !
Setting Up The Build Environment is done...
Checkout first page...
Awesome mate that is what i was looking for!
I really appreciate this
this will be the hugest tutorial in know.
but very helpfull for some peoples.
rly nice
Can I follow this tutorial (codes and everything) with mint 13?
Cristiano Matos said:
Can I follow this tutorial (codes and everything) with mint 13?
Click to expand...
Click to collapse
I think it should work, but cant guarantee...Try it and let me know
Dude, it's really nice. But one question. After that, are we going to have a brick wave? I think that unexperienced people like me will have some trouble when trying to build. Your tutorial will be brick safe if we follow all steps? If yes, I will try to do something.
Ics opensource update 4. is believed to be safe,so people will be "brick-safe".
This thread will be handy for disscussions when we get ICs successor,and samsung presents us a new "virgin" kernel source.
Also,u can find 6 toolchains in this repository- https://github.com/sakindia123/Android_Toolchains
I have posted this in a couple of threads as a little utility I wrote to find the latest RDF's its written in C# so you will need a C# compiler to run it. Once of the easiest and simplest onces is snippet compiler. Took me about 20 minutes to write so please no code reviews I assure you my production code is much better. Anyways if you want to check for the latest RDF's for either boost or sprint builds then here you go. Updated to latest build FH13 so as of right now it will find anything after that build which gets posted.
Instructions:
Download snipper compiler here:
http://www.sliver.com/dotnet/SnippetCompiler/
Copy/paste script into editor window and click run. Edit as needed. Enjoy.
UPDATE:
Modified version that includes a range and the ability to save matches to text file:
http://snipt.org/vzW7
Greetings all,
I would like to know something that seems to be so simple it hasn't been documented here anywhere.
My question is: How do I build the source provided by Google for my Desire HD?
Yes, there are tutorials, don't point me to them. They either provide you with the AOKP way or the CM way.
I want to build my stuff from scratch.
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I know about the vendor files, these are created by a third party. How do I know what vendor files I need to create? How do I know how to name them?
Don't get me wrong, I've used C, C++ and C# for YEARS (I think about 8 now) and I know how to code. I just don't know how to compile android!
It doesn't seem that hard though, I've seen threads where people provide ROMs for the Desire HD without even having the device!
Also, how would I test this and debug it? I don't think it's safe to just flash my rom once I get it compiled to my actual device and possibly brick it.. Can I use an emulator?
I hope you will read this post before answering something alike "Plenty tutorials" or "This can be found everywhere", because it can not. I can only find AOKP or CM ways, I want neither.
Greetings Ultimate-Tester
The only time I know of that this has been achieved for this device is aospX, an ICS ROM on the Inspire 4G forums. It is much harder than you would think. Google does not support this hardware, HTC does. So there was never AOSP source for this device.
Yes, I can imagine how hard it is. As I said I have programming experience, it's just that I don't have it with Android ROMS.
I have built mainly for Windows, also on Ring0 level (which is the lowest level you can get) so I think making drivers is a task I can handle. I am definitely not underestimating it.
Could anyone give me an answer to this line:
Code:
Is there a generator that will create the necessary file structures for me (in the devices folder)?
Is there a complete list that my rom needs to include in order to make it run on my device (preferably a list of folders I need)?
I am very interested in how other people knew what folders to create and what files to put in them. How would the Google Source (envsetup) know which device files to use and what not? Again, can I generate the file structure somehow?
Greetings,,
My suggestion is to use device trees from AOSP-based ROMs that already exist for this device. For example, look in the cfX manifest.xml for Ace-specific stuff (kernel, device, etc.). I personally haven't seriously tried this before, so that's all I can offer.
Okidoki, will do. Then for the last item: Testing.
What will be a safe way to test out my brew?
What will actually happen if I flash a ROM with missing files? I hope there's an underlying catcher that will send something I can see in logcat and fix it that way.. Is this the case, or will I immediately brick my phone once I do something wrong? Do I need to make sure something is 100% there in order to reach my recovery again?
Greetz,,
I'm nor aware of any safety nets. If you're developing, you probably have to be willing to take the risks.
Hey guys!
I just got my serranoltexx and am fairly happy. However, I really would like to try and get AOKP running. Could any devs point me in the direction of where to start, you know, just bootstrap me with some reading? I have a background in Linux and UNIX, have developed some networking stack API projects on windows and have written a ****load of bash, perl etc. scripts in the past. I've also worked on the Matroska container format. Compiling etc. pose no challanges for me. However, I have never fumbled around with Android and I have no idea what drivers and other components might be needed. And how to start finding out what's missing...
I do know how to bootstrap my source repository and sync it... and in theory also how to compile AOKP - for supported devices, that is. What I don't know is: how do I start resolving unmet dependencies, and, you know, generally port a rom to a new device?
Please don't post if you haven't even compiled your own ROM yet. More likely than not, you'd be wasting your time.
I've posted on xda-dev as well, not sure which is the more suitable forum, possibly this one... Link to the other thread:
http://forum.xda-developers.com/showthread.php?t=2501539
And please don't post me to this guide right here as it is only of limited help. As I said, I know how to do it in general... You know, this guide:
http://aokp.co/learn/so-you-want-to-build-aokp-jb-ubuntu-1204
I tried to build it, but many things are missing once i flashed the *.zip.
Maybe i messed up with sources and patches.
Tell us if you have success! :good: