Related
just like what the title said,i think if any one can teach us how to cook an android rom thats will be good,then we can make our own rom.i dont really like the rom that we has right now(i dont mean the roms are not good,im very want to thanks the Acookers,those rom just changed too much base on the offical roms,i want a rom that has almost the same as the official rom with sense..)
ok,i found the android kitchen for the hd2,the download link is here http://www.megaupload.com/?d=EK281AVK , the original thread is here http://forum.xda-developers.com/showthread.php?t=738770 big thanks to the author
+1 for that
yea me too
wish someone would make a complete tutorial showing how to do it and explain every concept for noobs
first you need a good knowledge with linux os if not .... no hope
lol this is such wishful thinking. i'm a noob like yall and would love to give back to the modding community that's provided so much for me. but unfortunately, making a tutorial of this would be near impossible. or really hard at least. you can't put into a tutorial, as someone mentioned, a firm understanding of linux os. that's just too much information to try to shove into a tutorial.
but if this does happen, i'll happily eat me words because i'd love to be able to cook up some roms.
Not sure how to cook roms really, there's Coffe Shop v1 but the system.ext2 always comes up with 195MB from a 119MB image, and wouldn't boot, and the developer disappeared and hasn't updated it in a while.
Sent from my HDROID2 using XDA App
tarekkkkk said:
first you need a good knowledge with linux os if not .... no hope
Click to expand...
Click to collapse
i dont think so,just like cooking a wm rom,you dont have to know very deeply of the ce or wm,all you need is replace things,its just easy if some on tell you how.....but maybe im wrong....
There are android kitchens available on the site here... just search for it as I don't have a link to it at the moment...
It's not as easy as cooking for WinMo and it won't always boot but you can sure cook
pongster said:
There are android kitchens available on the site here... just search for it as I don't have a link to it at the moment...
It's not as easy as cooking for WinMo and it won't always boot but you can sure cook
Click to expand...
Click to collapse
whats the key word?is it for hd2?thanks
weixiong said:
whats the key word?is it for hd2?thanks
Click to expand...
Click to collapse
search android kitchen.. no its for android not hd2... but you can use it to get results...
any news
+1
any news
look up coffee shop you could of searched first and found this without starting a new thread
you don't need to be an expert in linux, but at least have the basics. If you wana start, let me know, PM me or something. I'll try to help any way I can... I'm no expert as well, tho...
for some recent roms, they all use standdard ext2 image, it's better you work it on linux,
on linux you can mount the rootfs.img data.img, system.ext2 image to linux, then you can easily to copy & paste it.
and you'd know how android & linux boot up by adding & edition those boot config file.
and hd2 android is not standard rom like other cellphone's, hd2 rom don't need to pack into a single file, this is more easy for edition. and everyone can split the rom into several files.
few files information:
system.ex2 will be mount as /system, where android files located
data.img will be mount as /data, where user data located
initrd.gz, linux boot from here.
rootfs.img in some roms, the initrd.gz boot up will load this file, and mount this file as /, and main boot files are here. if you don't have this file, the main boot config files are in initrd.gz.
I am not guru, just tell what I know.
thanks.
Somebody should my a video of this
qingcai said:
for some recent roms, they all use standdard ext2 image, it's better you work it on linux,
on linux you can mount the rootfs.img data.img, system.ext2 image to linux, then you can easily to copy & paste it.
and you'd know how android & linux boot up by adding & edition those boot config file.
and hd2 android is not standard rom like other cellphone's, hd2 rom don't need to pack into a single file, this is more easy for edition. and everyone can split the rom into several files.
few files information:
system.ex2 will be mount as /system, where android files located
data.img will be mount as /data, where user data located
initrd.gz, linux boot from here.
rootfs.img in some roms, the initrd.gz boot up will load this file, and mount this file as /, and main boot files are here. if you don't have this file, the main boot config files are in initrd.gz.
I am not guru, just tell what I know.
thanks.
Click to expand...
Click to collapse
Thanks a lot!
Okay, as I am sure we all see there has been a HUGE break through for our HD2 freedom thanks to all the Dev's here with the release of ClockWork Mod Recovery. I can for see a downpour of one particlular question flooding the forums... "Can you make a ROM ZIP Please".
I would assume that it can't be that much of a task to take a NAND build and make it flashable (Maybe I am wrong) but it seems all the hard stuff of creation is done, it becomes a matter of "format" (Maybe Not the Right Word). Extract Boot and System.IMG's, Editing a script?
So... Maybe we can all take the burden off some of the Devs doing this to our favorite builds? Then they can focus on what they do best... making this stuff work.
What is involved in doing this?
Hell, maybe I am way off and we should leave it to the Pro's?
I'm Ready.
DroidTh3ory said:
Okay, as I am sure we all see there has been a HUGE break through for our HD2 freedom thanks to all the Dev's here with the release of ClockWork Mod Recovery. I can for see a downpour of one particlular question flooding the forums... "Can you make a ROM ZIP Please".
I would assume that it can't be that much of a task to take a NAND build and make it flashable (Maybe I am wrong) but it seems all the hard stuff of creation is done, it becomes a matter of "format" (Maybe Not the Right Word). Extract Boot and System.IMG's, Editing a script?
So... Maybe we can all take the burden off some of the Devs doing this to our favorite builds? Then they can focus on what they do best... making this stuff work.
What is involved in doing this?
Hell, maybe I am way off and we should leave it to the Pro's?
I'm Ready.
Click to expand...
Click to collapse
I would have to agree. I'm not much of a developer but I can follow directions pretty good. I would come on board and like DroidTh3ory said, take some of the burden off some of the Devs.
I would also like to a see a Nandroid (backup of nand to sd) type option so as if the new rom we flashed is not what we were hoping we can roll back the nandroid.
DroidTh3ory said:
Okay, as I am sure we all see there has been a HUGE break through for our HD2 freedom thanks to all the Dev's here with the release of ClockWork Mod Recovery. I can for see a downpour of one particlular question flooding the forums... "Can you make a ROM ZIP Please".
I would assume that it can't be that much of a task to take a NAND build and make it flashable (Maybe I am wrong) but it seems all the hard stuff of creation is done, it becomes a matter of "format" (Maybe Not the Right Word). Extract Boot and System.IMG's, Editing a script?
So... Maybe we can all take the burden off some of the Devs doing this to our favorite builds? Then they can focus on what they do best... making this stuff work.
What is involved in doing this?
Hell, maybe I am way off and we should leave it to the Pro's?
I'm Ready.
Click to expand...
Click to collapse
I am not a developer. I would be more than happy to help with doing the conversions if someone posts a way to do it.
The developers need to spend their time developing their builds to be the best that they can be. We, as a community, need to help the developers by taking the little tasks, such as file conversions, from the developers so they don't have to sweat the little stuff.
Linux BASH scripts are my friend.
Well, dsixda kitchen does allow import of nandroid backups, and anyway unyaffs already extracts imgs
Sent from my HTC Desire
droidzone said:
Well, dsixda kitchen does allow import of nandroid backups, and anyway unyaffs already extracts imgs
Sent from my HTC Desire
Click to expand...
Click to collapse
droidzone...I've used unyaffs to extract system.imgs before and the only problem is that it only extracts them in a read-only kind of form because I can't edit anything and I have to get an act of congress just to see a PNG. I'll give the dsixda kitchen a shot.....downloading right now.
Yes, flashing (actually recovering) a rom from SD is safe and simple. With recovery we could do these by ourselves.
dbshane said:
Yes, flashing (actually recovering) a rom from SD is safe and simple. With recovery we could do these by ourselves.
Click to expand...
Click to collapse
Ok, then try the kitchen. It allows import of nandroids and once imported, you can mod it whatever way you want.
Sent from my HTC Desire
Well, the first step is done.. We now have recovery. Now when just need something to use it with.
I was looking through the different builds NAND, RAM and SD. Besides everything being wrapped up in .img's, the NAND ROMS have the same files. Comparing to the ONLY Flashable [.ZIP] ROM I see no similarities.
Maybe RaiderX303 or another DEV can put us in the direction we would need to go. Software, Files, Steps, Etc
droidzone said:
Ok, then try the kitchen. It allows import of nandroids and once imported, you can mod it whatever way you want.
Sent from my HTC Desire
Click to expand...
Click to collapse
Okay so... When you are referring to Nandroids and you referring to backups? We have 3 build types at our disposal right now... NAND, RAM, and SD.
What would we compile out of the ROMS the DEVs have provided to use?
DroidTh3ory said:
Well, the first step is done.. We now have recovery. Now when just need something to use it with.
I was looking through the different builds NAND, RAM and SD. Besides everything being wrapped up in .img's, the NAND ROMS have the same files. Comparing to the ONLY Flashable [.ZIP] ROM I see no similarities.
Maybe RaiderX303 or another DEV can put us in the direction we would need to go. Software, Files, Steps, Etc
Click to expand...
Click to collapse
I think installing the dsixda kitchen is the first step in all of this. I'm installing it right now and I'm going to give it a shot using JDMS's NAND ROM.....we'll see what happens if I can get it to boot up in recovery or not.
mazdarider23 said:
I think installing the dsixda kitchen is the first step in all of this. I'm installing it right now and I'm going to give it a shot using JDMS's NAND ROM.....we'll see what happens if I can get it to boot up in recovery or not.
Click to expand...
Click to collapse
All right, I will do the same with the NEXUSHD 1.9 and see what happens.??? LOL
Raiderx uploaded a rom in zip format. Can't you guys just take that and compare it to another build to see the differences?
DroidTh3ory said:
Well, the first step is done.. We now have recovery. Now when just need something to use it with.
I was looking through the different builds NAND, RAM and SD. Besides everything being wrapped up in .img's, the NAND ROMS have the same files. Comparing to the ONLY Flashable [.ZIP] ROM I see no similarities.
Maybe RaiderX303 or another DEV can put us in the direction we would need to go. Software, Files, Steps, Etc
Click to expand...
Click to collapse
The big issue to converting a NAND to UPDATE.ZIP is not about the files (just unpack boot.img and system.img and put the contents in the relative folders) but making the updater scripts specially for symlinks that ZIP not support so is needed that symlink are deleted and recreated on-the.fly by the updater script
updater scripts are under META-INF folder in the zip
rafpigna said:
The big issue to converting a NAND to UPDATE.ZIP is not about the files (just unpack boot.img and system.img and put the contents in the relative folders) but making the updater scripts specially for symlinks that ZIP not support so is needed that symlink are deleted and recreated on-the.fly by the updater script
updater scripts are under META-INF folder in the zip
Click to expand...
Click to collapse
My head just exploded.. LMAO. but Seriously, I see what your saying. Any tips on updating the Scripts? Would starting from a SD or RAM build be a better way to start?
rafpigna said:
The big issue to converting a NAND to UPDATE.ZIP is not about the files (just unpack boot.img and system.img and put the contents in the relative folders) but making the updater scripts specially for symlinks that ZIP not support so is needed that symlink are deleted and recreated on-the.fly by the updater script
updater scripts are under META-INF folder in the zip
Click to expand...
Click to collapse
LOL...I have to agree once more with DroidTh3ory because my head just started to hurt when I started reading all of that.......I think this is the reason even more why we need a Developers hand in all of this. I know we are all looked at as little vampires that suck the very last drop out of what you guys have to offer but we would honestly would love to help instead of just coming on here to download stuff and complain about how this doesn't work and that doesn't work and just be a pain in the devs butt........So if any Developer is watching from up above....PLEASE, show us the way...LMAO
DroidTh3ory said:
My head just exploded.. LMAO. but Seriously, I see what your saying. Any tips on updating the Scripts? Would starting from a SD or RAM build be a better way to start?
Click to expand...
Click to collapse
I would say since raf explained the basics for converting nand to update.zip that nand would be a good place to start
Sent from my HTC HD2 using XDA App
DroidTh3ory said:
My head just exploded.. LMAO. but Seriously, I see what your saying. Any tips on updating the Scripts? Would starting from a SD or RAM build be a better way to start?
Click to expand...
Click to collapse
mazdarider23 said:
LOL...I have to agree once more with DroidTh3ory because my head just started to hurt when I started reading all of that.......I think this is the reason even more why we need a Developers hand in all of this. I know we are all looked at as little vampires that suck the very last drop out of what you guys have to offer but we would honestly would love to help instead of just coming on here to download stuff and complain about how this doesn't work and that doesn't work and just be a pain in the devs butt........So if any Developer is watching from up above....PLEASE, show us the way...LMAO
Click to expand...
Click to collapse
Sorry guys
to make the updater scripts you have to understand a little bit about symlinks and packing/unpacking stuff.. otherwise will be a lot difficult
basically you just need to unpack the .img files and put the contents in the folders. than you need to creat/modify the scripts for the META-INF folder, that basically are different for any build.
that's it.
its always nice to see members helping each other.after all the devs are done marvellous job in recent days.
rafpigna said:
Sorry guys
to make the updater scripts you have to understand a little bit about symlinks and packing/unpacking stuff.. otherwise will be a lot difficult
basically you just need to unpack the .img files and put the contents in the folders. than you need to creat/modify the scripts for the META-INF folder, that basically are different for any build.
that's it.
Click to expand...
Click to collapse
Ok Rafpigna....here's what I got in my update script that I put together the best I can using other update scripts from different ROMS and builds that I've collected in the last 3 months.
show_progress 0.1 10
run_program PACKAGE:remtool.sh
copy_dir PACKAGE:system SYSTEM:
show_progress 0.2 40
copy_dir PACKAGE:data DATA:
show_progress 0.3 80
copy_dir PACKAGE:sdcard SDCARD:
show_progress 0.4 100
If there anything I should include or take out or should I go and jump off a building now?...LMAO
Im trading my HD7 for a HD2 on monday and i was looking at roms, i was placed into an instant confusion. What does it me to put files into sdcard/andriod, do you have to make your own folder cause im pretty sure the sd card doesnt already have that folder and how do you go to haret.exe from the phone itself? the hd7 functions are not the same so maybe thats why i have no idea whats going on.
Please help
-Thank You
Here's a link to the procedure to add Android using SD builds. Once you do the required steps, Haret, etc. will be added and you will not need to manually add them yourself. If you do not need Windows, I would recommend the NAND ROMs using CWM. Using CWM, you will be able to quickly change ROMs. Also, I found that the NAND ROMs boot faster and use less battery in standby and actual use.
http://forum.xda-developers.com/showthread.php?t=881958
Basically what that means is to create a folder on the root of your SD card called "Android" and copy the ROM files to it then on your phone go to WinMo's built-in file manager and open the Android folder and run CLRCAD (audio file) then Haret.exe and you'll boot in to Android.
thank you for the replies, but would you mind giving me a step by step instruction for the NAND boot too then if thats more recommended since i wont be using windows anymore.
dxaznxk said:
thank you for the replies, but would you mind giving me a step by step instruction for the NAND boot too then if thats more recommended since i wont be using windows anymore.
Click to expand...
Click to collapse
Check the stickie roll up threads, or click the guide link in my sig I have to links to how to install Android at the top of my guide. Or one more suggestion.........
Use Search!
hallo guys I want to install 2 ROMS in SD card for my HD2 device.
a sense and a MIUI one ,,but I want to have both installed!
in order to run everytime which I want...
is this possible ? can you explain and help?
many thanks!!
Yes, it is.
In the folder with the files in (probably named 'Android') there is a file called startup.txt. Change the folder name to whatever you want (e.g. 'MIUI' or 'Sense') then within the folder open the startup.txt. There will be a line saying rel_path=Android (or whatever the name of the folder originally was). Change this to rel_path=your folder name and boot. I can't remember if the line is exactly like that, so keep the formatting the same (i.e. the same spaces, signs etc.) and only change the Android bit.
thank you! and after I boot into windows how I will choose which I want?
(MIUI or SENSE named?)
gesamgr said:
thank you! and after I boot into windows how I will choose which I want?
(MIUI or SENSE named?)
Click to expand...
Click to collapse
Well I guess you would have to uninstall any automatic loaders you have and manually browse through the files and choose the right CLRCAD and HARET from the desired folder
ok thank you !!!
Hi gesamgr,
follow the download link for the exceller autoloader in this thread:
http://forum.xda-developers.com/showthread.php?t=737001
On bootup sequence it shows you the opportunity to choose which OS you'd like to boot - multiple OS as SD version included! Remember to follow the instructions carefully.
best regards
Getrid
Use MAGLDR 1.13 for booting into WINDOWS or any ANDROID ROM.
Just use Boot AD SD for booting into Android.
Change the folder for booting different android ROMs using SERVICES....Boot Setting.....Android SD Folder.
I have 3 roms in SD
just point the way in Magldr
[Q] How to convert any "initrd.gz" of NAND/NativeSD ROM to "SD" Version?
I'm successfully convert many ICS NAND ROMs and others to SD version.
I used UBUNTU to create the .ext4 system/data files
I used the Updater-script to 'grep' the required actions for setting the symlinks and permissions.
With the Help of the NAND version of the Initrd.gz, I success for many ROMs to create updated Initrd.gz and it Boots fine.
With Others new ROM, it Hangs at booting process which needs much time and efforts to study the init.rc, initcleo.................... which i can't.
I have tried to convert the "Initrd.gz" of many ROMs to SD version but always failed.
The reason is the Technique for SD definitions in "init.rc", init.htcleo.rc, ......." which many of us don't know about.
There are some few ROMs has been converted by the cookers and they are working fine.
Most of the New ROMs specially "JB" are not easy to be converted.
Here I'm trying to find a guide or special instructions for those specific files mentioned above to step over a restricted way for conversion.
Please, if any of you has experience in this or did his experimental tries for the same to help us in here.
Hi,
is this thread what you need?
http://forum.xda-developers.com/showthread.php?p=14101216
Sent from my HTC HD2 using xda app-developers app
Nooooooooooooooooooooo
o82239 said:
Hi,
is this thread what you need?
http://forum.xda-developers.com/showthread.php?p=14101216
Sent from my HTC HD2 using xda app-developers app
Click to expand...
Click to collapse
This is actually a great thread and it helped me much but it doesn't support JB as i stated in the first post.
Hi,
why don't you use NativSD?
Sent from my HTC HD2 using xda app-developers app
Why No NativeSD
Because i like to try many ROMs without intervention.
When i use the normal SD versions for ROM then i need to test another rom, all what i need to do is:
1- Remove the old files for that ROM from the folder and copy the other.
2- Keep both ROMs and play with them.
3- In case i need to do Backup, simply copy all directory files to any storage (So simple).
But with Native SD, it requires many procedures like (Prepare the SD, create parti., .........) which i don't like that way.
I always prefer the SD method and i love to convert NAND ROMs or NativeSD to SD.
Anyhow, thanks for your question but i didn't yet got a reply.