I know nothing much of ROM Development but I do have the basic foundation knowledge and I wish to commence in releasing a modded ROM soon as a start...
As a start can anyone give a pointer of the following :
1. Boot image » what is required to extract / modify ?
Note : Please do not re-quote as I will be making changes as we go along
So let us discuss and explore so that we can learn together....
Sent from my GT-I8150 using xda premium
I was thinking of doing the same andy. Asked cow to see if he would like to point me in the right direction.
I had to abandon my idea as new house i moved into i dont have any internet to work off so had to put my plans on hold. But here is what i was told what is basically needed for cooking roms.
1) Download Kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
2) Download your stock ROM
3) Extract system.img.ext4, cache.img.ext4 and boot.img from stock ROM, put into Kitchen's original_rom folder
4) Do this for SGW: http://forum.xda-developers.com/show...8&postcount=12
- No need to upse KezzaPlane's updater script anymore
5) Run ./menu in kitchen and follow the instructions
On part 3. If you want to use a different kernal( Oc one or simply Cow's oc kernal) please make sure to ask for the use of the kernal first and then use that boot.img and replace it into the rom that you are going to cook.
hi, thank you very much for the information, so far i have downloaded eclipse ee, and the android sdk but had zero idea where to start lol
i was so motivated when arco started and released his ics rom that i wanted to do my share as well, i have experience in coding in java but also wanted to know what else to do, then i bumped on this post, thanks a lot man!
snwman said:
4) Do this for SGW: http://forum.xda-developers.com/show...8&postcount=12
Click to expand...
Click to collapse
um unfortunately that link doesn't seem to work, may i ask for the full link?
this is awesome, i will support this thread. pls someone provide clear informations on how and what needed
Related
____________________________________
2BOrange
____________________________________
Hi everybody,
I have made a free application to install any kernel on your SGS very easily.
The idea is that there is a website where kernel are uploaded with a script and an application to:
- search
- download
- install it on your phone.
The application and the website are not limited to install kernell but I think it is a good way to try it.It can execute any script in the android shell.
So I have made some script for some kernel, there are so much that I have not the time to make one for each of them.
To make a script is very easy, I have attached an example of one I have uploaded on the website. If you need to attach a file, put it in a zip and upload both (the script and the zip) through the upload form on the website,
The address of the website is:
http://www.2borange.com/
A general thread on XDA (not dedicated to kernel on SGS) about the application:
http://forum.xda-developers.com/showthread.php?p=14875954#post14875954
You need to create an account to upload but it is not mandatory to just search, download and install a kernel.
Please keep me informed if everything work or not. I have only test it on my phone.
For the author of the kernels: I am sorry to have not yet informed you of the sharing of your great work, I will do it for sure when I will have done enough test to offer you an interesting way to share your work.
For the user: if you have time, don't hesitate to upload some scripts, it is free and easy to do...
Thank you for everything,
Michael
LIST OF KERNEL AVAILABLE AS OF JUNE, 27:
- Galaxian
- Infusion Kernel Faster Fusion Reaction
- Semaphore Kernel JVH - JVP
- SpeedMod Gingerbread
- TalonDEV
- TEGRAK lagfix- Voodoo kernel installer
- Voodoo kernel JVP
Don't hesitate to upload some new firmware. A model of script is provided below as attachment
niceee something to look foreward to
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
This allows you to actually find a kernel, download it and flash it as well. The Kernel Flasher is just for kernels already on your sd card.
O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
Thank you for your message.
I did not know about this application. I have read the description and I can tell you the purpose of mine is totally different.
I have understood that Nedar application is to install a Kernel that you have already downloaded and copy on your SDCARD.
The purpose of my application is to download automatically a script and a zip file, and execute the script.
So there are 2 main differences between these two applications:
- my application get files you need directly from the cloud (Internet), so it is like a deposit of files
- my application is not limited to kernel installation, it is just a usefull example to show people how it works, but it can do more, really lot more tasks.
However, because the application of Nedar is dedicated to one particular task, it has option I have not yet implemented in mine. By example, I have not yet construct a script to backup the kernel in an update.zip file, which could be very usefull.
So they are really very different. I hope I will be able to construct more script, but may be the biggest difference with any dedicated application is that anyone can participate to my project without any knowledge in Java programation.
You just have to know a little bit about shell to be able to share your work with others.
THAT IS THE REAL PURPOSE OF THIS APPLICATION : SHARING!
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
Thank you for your interest.
The thing I need now is not money, donation,etc... but report of test and ideas of improvment.
By the way, I only have a samsung phone, and I am wondering if there are possibilities to install kernel in other phone only by using the shell, have you an idea ?
Second question: have you an idea how to proceed to install an entire ROM through the shell ? I suppose the phone has to be rebooted before installation begin and lauche in a recovery mode, but how to make it automatic like in ROM Manager?
Thank you for your help!
omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
What is the way it should take for you?
I need ideas
lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
I have already included a kind of filter based on brand, model of phone and firmware version plus sdk version, do you think it could be more precise?
Fixed script on server, should work on every phone now
Hey snoopy33, why do you have not yet updated this page?
Ok, so after having a million questions I thought I'd write up a quick little 'how to' with regards to porting.
And now the warning
Read and learn first, doing this could cause serious issues with your tab or even brick it. The tab is really tough, and hard to brick if you do everthing right but it could still happen. I'm not responsible if it does.
Where to start
Get good at reading, google searching and searching XDA. Lots of porting discussion regarding other phones can apply to the tab.
Learn to use Heimdell
Have a linux distro available, either by virtual box, or natively.
Technomancer where it all began
I've said it before and I'll say it again, without techs work miui wouldn't have been possible.
Reference technomancers thread here: http://forum.xda-developers.com/showthread.php?t=931857 on how to download the cm7 + sgt source, you're also going to want to follow the kernel making part, cause most likely you'll need to make adjustments to the init.rc which is inside the initramfs and requires building the kernel again.
porting x build
Get X build onto your computer and extract the update.zip for it.
Copy the boot.img into your linux environment and extract it using splitbootimg.pl script (note: Google it, plus this doesn't work with samsung builds). Compare the init.rc to your init.rc (from the sgt cm7 kernel source root folder). Specifically the most important part here is the PATH, LD_LIBRARY_PATH statement and BOOTCLASSPATH lines.
Build your kernel with the updated init.rc and flash with heimdell, it should still boot your cm7/miui build (if you were running it before) albeit with errors.
The system
Now following the awesome list of proprietary files (either from your source folder or technomancers github link) check the galaxytab-common-vendor-blobs.mk for the GT-P1000. It lists every file you need that's propreitary to the tab and where to put it.
Also you'll probably need the debuggerd from /system/bin on the cm7 build.
Compare the /system/build.prop of the cm7 build to your port, make sure the ril info is the same as well as the ro; model, brand, device, board, and platform lines.
Create an update.zip (or whatever you want to call it.zip) and try it.
It's not booting
Logcat is great, but I really suggest using the ddms from the android sdk tools. It's color coded, and gives a much nicer view of what's happening.
Using winmerge in windows or a linux file compare program start checking what other bin files may be missing that you require. Special notice to the xbin folder.
It works! I want to post it!
Ok, first up, make sure you have permission if this is someone elses custom build you've ported. Most people/groups are really good about it assuming you ask first and give them credit in your post.
Also credit everyone who helped, answered a question or sent you in the right direction. (it's just polite)
Second your going to want to make sure your update.zip flashes the kernel, read the update_script from the cm7 build to understand how it works.
So that's it for a start. roll up your sleves, gather your courage and get to it!
Please if you have other tips, add them to the thread, what's better 1 or 2 'developers/porters' or 100?
Thanks. This is very useful for me.
Thanks,
Following this method, with slight alterations to adjust, I was able to port an i9000 phone build to the tab in about 10 minutes, it's really not terribly that difficult once you have the right steps.
The first couple times are usually frustrating but after that you get the hang of it
Hi mssmison Thank you for your guide,it will be very useful in the future! I have only one request,how can I contact you? I have a proposal for you about a dev team (regarding an old think tank)
Thanks for the guide...
Is there any ROM left to port by the way?
Sent from my GT-P1000 using XDA Premium App
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
Whiles there's currently an excellent port from the 7100 MIUI build it has a couple of flaws which I'm not totally sure can be resolved. It's been a long time since I looked at developing anything but figured I'd have a look at the current patchrom implimentation to see if we could get a proper 317 build going.
Here's some details about patchrom, and what I've done so far.
First up. https://github.com/MiCode/patchrom already has a note2 tree, so we can use that as a base for changes for the 317.
Have all the same pre-recs installed as you would to compile cm.
In linux you'll need to make a patchrom folder
1.mkdir patchrom
micode doesn't yet have all the repo setup for jellybean, so I just downloaded the following zip tardballs and extracted them into their respective folders;
https://github.com/MiCode/patchrom_miui/tree/jellybean -> patchrom/miui
https://github.com/MiCode/patchrom_tools/tree/jellybean -> patchrom/tools
https://github.com/MiCode/patchrom_build/tree/jellybean ->patchrom/build
https://github.com/MiCode/patchrom_note2 ->patchrom/note2
https://github.com/MiCode/patchrom_android/tree/jellybean ->patchrom/android
Once that's complete you can pretty much follow the developer guide here;
https://github.com/MiCode/patchrom/blob/ics/Patchrom Developer Guide.pdf
I highly suggest installing this as your source rom, (http://forum.xda-developers.com/showthread.php?t=2016575&highlight=stock) installing it as a stock build first (no themes tweaks etc)
Create a folder patchrom/317 and start following the guide to create your stockrom.zip
Copy the following from the note2 folder into your new folder
makefile
miuihome
miuisystemui
originalsettings
mms
overlay
phone
settings
thememanager
customize_framework.sh
customize_miuiapp.sh
phoneapps.mk
Camera maybe?
Edit the makefile to update the directory references to your new build folder.
Run the make workspace to unzip and decompile the frameworks that are going to be modded.
By following the guide, with what you've done we're now at the firstpatch phase. That's what I'm currently working on as well.
The directions are a little convoluted so hopefully this helps.
When you run make firstpatch what it tries to do is automatically patch the miui smali bits into the framework/services smali files. Whenever it can't it'll create a *.rej file for you.
What you need to do is edit the associated file and manually put in the diffs from the rej files. Where we have this super great advantage is there's already the 7100 framework with the patched in rej in the note2 folder you downloaded earlier. So really you just need to compare that smali file against yours and apply the changes noted in the rej file. (tip. you edit the original files created during make workspace, nothing in the temp directory, just in the framework.jar.out folder etc)
Here's a really great post detailing an example; http://forum.xda-developers.com/showpost.php?p=25713236&postcount=171
Boy.. that doesn't sound easy.. but believe me it's easy once you start looking at it.
Ok I've dealt with the *.rej files now what?
Holy congrats! Your a step ahead of me at this point Next up you just need to run make fullota. It *should* at this point build an ota you can flash from recovery.
copy to sdcard, reboot recovery flash and.. it should boot. Really I expect there should be little or no issues thanks to the 7100 work we've already borrowed.
Assuming it works, let's get it on github and shared with the miui team. That'll go a long way to making it a weekly build.
Good luck and have fun!
If you get somewhere, let us know.
An additional source is the changelog for patchrom on the note2 (7100). Here's the manual commit details. This is also a pretty good map for what we need to do.
https://github.com/MiCode/patchrom_note2/commits/jellybean?page=2
Brother, are you now doing this job？I want to do but is too difficult for me...
I have been using MIUI 3.1.25 from the T-Mobi Galaxy Note 2 thread. I really like this ROM. But there are issues since it is not optimized for the i317 note 2 phones. Example: I can't access my 64GB SD card on MIUI v5. I reverted to the previous version (MIUI 3.1.25) and my SD card forks fine. Have anyone followed the instructions in the original post above and was able to port MIUI to the i317 note 2 phone? I would really like to know how to port this ROM. I am looking into how to get started.
Thanks for sharing this! Idk if anyone has improved on miui from this? Im willing to look into it, would you be willing to help me out with fixing some issues once i get it flowing? If so i appreciate it, just toss me a pm at your convenience.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
dirtydroidx said:
Thanks for sharing this! Idk if anyone has improved on miui from this? Im willing to look into it, would you be willing to help me out with fixing some issues once i get it flowing? If so i appreciate it, just toss me a pm at your convenience.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks for the post but belive me fixing rejects is not that easy job. You will get hundreds of rejects while patching the smali code by MIUI patchrom.
If anyone got success with this, I would love to get in touch with you.
Guys please help with Patchrom Tool for Note 2
I'm seeking help in knowledge to make a ROM and kernal for all distributions. A basic stripped down no hardware except CPU.
We will start with the kernal first. Extracted and repack for download and modifications.
I need to get a kernal for every version. I will provide download locations etc..
Next will come the basic stripped down version anyone can build onto. Using a kitchen etc..
You need to be able to know how to do a flash backup by yourself for the boot.img development aka kernal development.
My starting location is at
ixrom.wordpress.com
The basic guidelines will be there to get started.
Any coding help and all ideas are welcome.
I want to provide a extremely simple way to have someone download the coded or modified examples. To get up and running with a boot.img and then make it the same thing for the ROM. This way we can skip the manufacturing security and strange audits. I will make a good basis for all to work from.
If you know of good working already to go boot.img in this manner? the better. I will host the versions and the CPU compatibility as well. This way any ROM development can be built straight for any phone no matter what. I have already tested working models and yes this is possible. If you would like to participate and help me develop this?
Drop by the blog and or email me at
[email protected]
You can also sometimes get me on facebook... Do a search for [email protected]
Yes I have a hobby and business making soap
I will make this possible for all of us.
Thank you XDA for making this possible.