My goal is to remove all unused applications from the ROM. I use surface kitchen (couldnt find anything else). I put Rom files into the Base ROM folder in the kitchen and used option 1. All finished ok. However when i start !COOK.cmd I cant see any packages (i can see them in the OEM folder) to select. In the readme file I found this:
3. Open !COOK.cmd and Buildos will open.
-Check/Uncheck the packages you want to add in the rom(if there are no things to check, add the option.xml file to each of the oem packs)
However I couldnt find any option.xml file. I checjked Wicki but there is only Kiser kitchen. I would love to use it for Diamond but I'm not sure if I can. So I'm stuck for now. If anyone could help me it will be great.
Here's my kitchen, you may find it easier to use.
http://www.mediafire.com/?rx2twayzkn1
Just tried it. It works ok. Just a quick question. How do I remove unwanted packages. Should I just remove them from the casserole folder?
lolek74,
What do you mean by "My goal is to remove all unused applications from the ROM". Is that unused by yourself or do you mean to create a stripped down ROM removing as many apps as possible.
The later is what a few of us have been looking for and it would be great if you could create a ROM like that.
lolek: r u Polish?
^.^
Anyways, after the "concat" part, you will have an OEM folder and a SYS folder in casserole.
Each package (nearly) is prefixed with package_diamond_xxx
Some of them have accompanying language/mui folders
You can delete any pair you don't like.
Be careful while removing SYS packages though, or OEM_prefixed packages.
I'm not but my friend's wife is Polish and theirs children always watch bolek i lolek movie. Hence my nickname. I'll give a shot and report back tomorrow. Thank you.
i have a problem with extracting core files, file not found on the end
xip_e must be in casserole. but i can`t find it
This usually happens if you're trying to extract a "protected" ROM like bepe's, DP, Swift or Dutty's.
ok, i try another rom thank you
i tryed several roms but have the same problem also from htc NLD
how can i get the right rom
I have managed to remove some application. However After 1st boot I get message that Opera cant be find. Also how do I:
remove empty folder (games)
Update to Framework 3.5
update to latest OS.
Help highly apreciated.
I will make short tutorial for anyone who wants to try make their own rom.
lolek74 said:
I have managed to remove some application. However After 1st boot I get message that Opera cant be find. Also how do I:
remove empty folder (games)
Update to Framework 3.5
update to latest OS.
Help highly apreciated.
I will make short tutorial for anyone who wants to try make their own rom.
Click to expand...
Click to collapse
That tutorial would be very, very cool ! Good luck with you ROM making. Hope that you can finish it and share your steps with us wannabe cookers. Thanks in advance !
when i`m extracting system files
i get this message in the logfile
Error: ..\source\Part02.raw is not a valid IMGFS file. Exiting.
what does i do wrong.
I need help. How can I update OS and Framework. It will be great if someone could help me please.
skippydvd said:
when i`m extracting system files
i get this message in the logfile
Error: ..\source\Part02.raw is not a valid IMGFS file. Exiting.
what does i do wrong.
Click to expand...
Click to collapse
Skippy:
the menu on the right is for rebuilding a dumped ROM (*.raw) whereas the left hand side options are for cooking a prebuilt .nbh
I guess you are trying to use the right hand side options for an nbh? This is why you get this error. OR, you didn't place Part01 and Part02.raw in the "source" folder.
Related
I have made s script which installs all files in my Install-Directory of my SD-Card. The script is based on nscriptm and invoked automatically after HardReset.
It installs silently all CAB-Files, Reg-Settings in REG-Files, a TSK-File.
It copys all wanted files automatically from the SD-Card to the PocketPC (e.g. for the Windows-Folder, etc).
It deletes wanted files from the Pocketpc.
It copies Shortcuts.
So a complete new Install lasts only a few minutes. Great for testing.
Now I am searching an unzip/unrar/uncompress/... - Tool which can be invoked from the command-line with additional parameters to uncompress all Install-Files on the SD-Card.
Anyone knows ?
Sounds like an excellent idea. Can you share your script? Sorry I do not know of a zip utility. All installs on cab files are already compressed though.
Doed Pocket WinRar will do the job?
I also would love to try it...
Very good idea
This sounds like a great idea.
No, Winrar is only with GUI. No Commandline. Have searched for days.
CAB-Files are not Compressed I think. Only the EXE-Files containig the CAB-Files for Install on PC are compressed.
Please HELP !
I have made an extended ROM which runs my script now automatically.
If you want it send me PM.
I have also been searching the net for a compresion tool that runs from the command line, but with no luck.
I have made an extended ROM which runs my script now automatically.
If you want it send me PM.
Click to expand...
Click to collapse
axbl,
would love a copy of your script. For everyone's benefit, can you attach it to this thread?
thanks in advance.
axbl said:
No, Winrar is only with GUI. No Commandline. Have searched for days.
CAB-Files are not Compressed I think. Only the EXE-Files containig the CAB-Files for Install on PC are compressed.
Please HELP !
I have made an extended ROM which runs my script now automatically.
If you want it send me PM.
Click to expand...
Click to collapse
Hi axbl, would be happy to test your script, email is [email protected]
Hi axbl,
Could you please also post me a copy of your ROM / Script ?
Many Thanks,
Justin
[email protected]
Has anyone heard from axbl? While waiting in vain, I decided to give this a shot and see how far I go along scripting my installs. I find the nscriptm tool to be very capable but still I am stuck in a few areas which axbl seems to have excelled based on the initial post.
How can one trigger a cab file install and make it a silent install? I am using the Shellwait("") command to trigger the cab file installs one after the other but those that require input are causing an issue.
Next I have tried automating the response to those user input prompts (i.e YES / NO etc) but I am having trouble catching the window handle of the prompts and then using the Sendkey command.
Thanks in advance for all the help. Regards
I use the software call Autoconfig.exe which is included in O2 Asia ROM.
The Autoconfig.exe will read Autoconfig.txt file and execute according to the command line in the file.
The command line is exactly the same as Config.txt
[.......] <---- Section to be selected
CPY1: <---- copy from
CPY2: <---- copy to
EXEC: <---- Execute Program
CAB: <---- Install .cab file
RST: Reset <---- Soft Reset
I can do what I need about 80%. I say 80% is because after this process ended. I still need to put in name/pasword to all of those s/w or else it will still be trial version.
no more?
so any update in this topic??
....pls
little_frog said:
I use the software call Autoconfig.exe which is included in O2 Asia ROM.
The Autoconfig.exe will read Autoconfig.txt file and execute according to the command line in the file.
The command line is exactly the same as Config.txt
[.......] <---- Section to be selected
CPY1: <---- copy from
CPY2: <---- copy to
EXEC: <---- Execute Program
CAB: <---- Install .cab file
RST: Reset <---- Soft Reset
I can do what I need about 80%. I say 80% is because after this process ended. I still need to put in name/pasword to all of those s/w or else it will still be trial version.
Click to expand...
Click to collapse
hi, if you create an xml file or a cab (need winCE cab manager) you can add all the registry details you need to register your program...but you have to search your registry to find those details.
Yes, I can do it while ago.
The post I did was a year ago. At that time, I didn't know how to do it.
Thanks anyway.
axbl said:
I have made s script which installs all files in my Install-Directory of my SD-Card. The script is based on nscriptm and invoked automatically after HardReset.
It installs silently all CAB-Files, Reg-Settings in REG-Files, a TSK-File.
It copys all wanted files automatically from the SD-Card to the PocketPC (e.g. for the Windows-Folder, etc).
It deletes wanted files from the Pocketpc.
It copies Shortcuts.
So a complete new Install lasts only a few minutes. Great for testing.
Now I am searching an unzip/unrar/uncompress/... - Tool which can be invoked from the command-line with additional parameters to uncompress all Install-Files on the SD-Card.
Anyone knows ?
Click to expand...
Click to collapse
Pls can u share the script with us it would be a great help for all of us.
thx in advance
jeet
You don't have to ask that guy. He'd never come back.
It's not that difficult to do. You need to know how to build CAB file by using WinCE CAB Manager. Then, put those REG, TSK, EXE, File, etc. into your built CAB file. By using (Autorun and Config.txt) or (Autoconfig.exe and Autoconfig.txt) or (Autorun and ExtROM via \2577 folder), You can install any CAB files into the system after Hard Reset.
ok
could you pls post the files to do it?
(Autorun and Config.txt) or (Autoconfig.exe and Autoconfig.txt)
if possible?
Matt released a Kitchen with his WM6.1 Naked 9b1 release and it looks inclusive and concise but I am unsure where I should go to find out how to use it.
Lately, I have been reading a lot (WIKI and various threads) on how to cook a ROM and unfortunately, I got lost in all the reading. There seems to be a lot of info out there and I cannot find an updated clear/ concise set of instructions that would apply.
Through my reading, I have tried things like Hypercore (always having problems on the rebuild stage) but then I see this Kitchen released that has everything Apparently I didn't need to spend all that time learning how to extract a ROM and now I am just more confused.
I was wondering if someone could point out a relevant thread or set of instructions that would help me build a ROM from the WM6.1 Naked 9b1 Kitchen. It sounds easy from the way some people talk about it but I had less trouble learning how to pull the motor out of my car from the manual Sorry for my ignorance on this; I am not stupid just inexperienced and in need of direction. I am hoping someone can help and save me hours of reading and learning the hard way. Thanks for your patience and any help.
copied from matt's post:
The Kitchen should reside in a folder on your PC. In that folder you need to have the following:
+++++++++++++++
OEM (collection of folders containing package options, as well as OEMDrivers/OEMApps/OEMMisc/OEMVersion/OEM_Lang_0409 folders and OEM.cer file)
ROM (OS.bn file and the XIP folder)
SYS (collection of operating system folders and an option.xml file)
TOOLS (utilities to build your phone image)
BuildOS.exe (tool to create package dump, preparing for compilation)
CreateROM.bat (script to automate compiling your image)
pkgcommon.dll (module for BuildOS tool)
Readme.txt (readme for kitchen)
temp (dump location after first build with BuildOS)
+++++++++++++++
If you've downloaded the latest kitchen parts and have this, you should be ready to go.
1. Run BuildOS.exe
2. Select the packages you want to install.
3. Click the green arrow in the upper left corner.
4. Once it completes without error, it will say "done" in the lower left corner.
5. Close BuildOS.exe
6. Connect your Phone to the USB cable
*NOTE* Back up your phone, and ensure it has more than 50% battery!!
7. Run CreateROM.bat
8. Follow the prompts.
9. Do a hard reset after it finishes.
10. Enjoy!
Whoops double reply sorry!
Thanks so much! I just caught that link now in Matt's Sig. I wasn't sure if WM6.1 instructions would be the same as WM6 so I guess I never bothered to follow that link.
I didn't see a "Readme.txt" file in the Naked 9B1 Kitchen though; I even downloaded both of the 9B1 Naked Kitchens (w/MSS & w/o) and still no Readme (unless it is hidden good). I went through all the folders and it seems that everything else is there. Now I'll read ahead a bit more and give it a whirl. It does sound too easy though considering all the other info out there on this subject. Thanks a million Venelar!
Thanks Matt also; if your reading this.
yea, i got it just by tinkering...sometimes i get an error when i put too many oem files in there, i think its duplicates, but i'm not sure. I can find out the duplicate when buildos is running, because it tells me the last file processed, and i can do a search of the folder. what gets me is when it errors out before the buildos even starts. the command window comes up then just errors out... this usually happens when i put two complete oem archives in the oem folder.... so i've found just keep it simple with the oems programs and you should have no problems... oh yea when you think its doing nothing, and stuck.... nope its just processing, so don't close the command prompt. so relax and just let it do its thing.
To create themes, or to edit themes to your liking, you will need a working knowledge of android, adb, how to resign apk's, knowledge of your own O/S.
Before you start be aware that you will may end up wiping your phone once, if not more. So lets go over the things that you will need.
You will need JF's RC30, RC8, or ADP1 V1.3, depending on what version you intend to create for.
Here is the link to these: http://forum.xda-developers.com/showthread.php?t=466174
You will also want to get the dev bootloader installed on your phone and to HIGHLY suggest everyone trying your theme to install it as well.
Link to dev bootloader: http://forum.xda-developers.com/showthread.php?t=455860
You will also need to resign all the apks located in /system/app and framework-res.apk located in /system/framework. When you push all of these to your phone.
JesusFreke was kind enough to build a custom signing tool for me that would allow me to right click on an apk and resign it from there. I am posting it here for others to use as well. Note that this is a courtesy of JF, so thank him for it. I cannot stress how much time this has saved me and will save you.
Here is the link: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
I will assume that you have the sdk downloaded and extracted somewhere(if not, do that now), extract both files to the tools directory of your sdk.
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.(This is for XP, Vista coming soon)
To do this, right click on My Computer click properties, then choose the tab that says advanced. Click the button that says environmental variables. Go to system variables find the one that says CLASSPATH, double click it, go to the end of variable value. There should be a semicolon ; at the end. type in the path to the testsign.jar located in the tools directory of your SDK, for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar If CLASSPATH is not in your system variables then create it. Secondly, Find the system variable called PATH and add to the end of it, the full path to your sdk directory. For example, mine was c:\sdk\android-sdk-windows-1.0_r2\tools
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? That's how you will resign your .apks and .zips.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
You will also need a version of linux installed or running vmware with linux, if you want to create, or edit, an update script, which will install the theme onto the users phone.
You will need to be specific in addressing what version your theme is for, RC8, RC30, or ADP1. Make sure every file gets signed. Make sure you test the update.zip before you release it.
Every .apk contains the images relating to itself. However, every apk has the ability to use the images in framework-res.apk. The images for every apk is located inside of itself. To find these images open up the apk, you can rename it to .zip or open it with an archiver of your choice, winrar, winace, etc. Then after opening the apk open the folder called res and inside of that there are folders that are named Drawable, drawable-land, drawable-port, etc. This is where the images are stored.
Ther are some things you cannot edit unless you rebuild the entire apk from source, which we will not go into here.(another tutorial, another time) Just know that at this time you SHOULD NOT edit, or even open images with the extension .9.png. If you do you will have problems...Trust me. These are special images called ninepatch images and android resizes these images to fit wherever android, or any other apk, needs it to. if you do open them or edit them they will no longer render correctly when resized. I believe that in order to edit these you must do so and then put them into the source and rebuild the entire apk.
Before getting started you must also realize that you cannot simply resign one or two apk's and stick them in your phone and expect them to work. You must resign every apk inside of /system/app and framework-res.apk and put them on your phone at the same time.
To simplify this process for you though, I have provided an empty update.zip which you can place all of your resigned apps into and use to update your phone to your custom theme. You can also download someonelses theme and use there files, since they are resigned already. It may also be easier to see what files do what and go where since they have already been edited and are easy to point out.
Now, your ready to start changing things up.
You will now need to open the apk, which you can do by adding .zip after .apk, effectively changing it to a zip. Note that if you are using windows you will need to unhide known file extension types. you can also use your favorite archiver such as winrar, winzip, etc.
See here to unhide known file extension types for Xp: http://www.mediacollege.com/microsoft/windows/extension-change.html
See here to unhide file extension types for Vista: http://maximumpcguides.com/windows-vista/how-to-change-a-file-extension/
After opening the apk go to res and copy the folders that have drawable in their name. Go to your desktop, or wherever, create a new folder called Images, or whatever. Open the folder, paste the drawable folders in there. Now you can see what the files look like without opening them. Btw, you may also want to add -frame, or -launcher, to the end of the folders you cope over to keep them separated from others.
Finally, you've edited the images put them all in the apk renamed it back to an apk and resigned it. Now it's time to push it to your phone and see the changes you've made.
Important! : Whenever pushing files to the phone NEVER do it while the phone is running. Do this in recovery mode! If you do this while the phone is running normally you will begin to lose space in /system.
So, boot into recovery plug your phone in and open a cmd prompt. From the cmd prompt type adb shell mount /system then type the following: adb push c:\whereveryourfileis\whateveryourpushing.apk /system/app (system/framework if your pushing framework-res.apk)
Now reboot your phone. If it doesn't boot, try doing a wipe, if that doesn't work reinstall an update and try again. There are alot of things people can do wrong, I can't explain them all here. If you get real stuck, you can ask for help here or contact me on Gtalk [email protected].
So now your theme is done and your ready to make an update.zip for others to install your theme.
I have created a template for you to make your own update.zip. Just download, add the system apps to app, and framework to framework. Zip it up, SIGN IT, TEST IT YOURSELF, and then distribute it!
Empty update.zip template: Http://www.FightForthePits.com/Androidstuff/update_empty.zip
If anyone has any questions please try asking for help in this thread before emailing me for help Usually I will respond to questions in this forum.
I hope this Tutorial has been helpful. I will add on to it as needed.
Stericson
Links of interest:
Downloading SDK: http://code.google.com/android/intro/installing.html
Using ADB: http://code.google.com/android/reference/adb.html
Working with ninepatch should be straightforward if you use the draw9patch tool included in the SDK. Documentation on usage here:
http://code.google.com/android/reference/draw9patch.html
JF could also save theme users a wipe by resigning /system/app/* and /system/framework/framework-res.apk in his builds with the test keys. Nice tutorial, btw.
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Stericson
Stericson said:
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
Click to expand...
Click to collapse
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Click to expand...
Click to collapse
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
thx stericson this will help big time how long before I can get resigned rc30 last night when you said all the apk. need to be resigned I was like this is going to be a long night but I see jf hooked you up save some big time with his resigning tool
jashsu said:
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
Click to expand...
Click to collapse
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Stericson said:
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Click to expand...
Click to collapse
The resigned apps have been released, each update file will resign all of apps in /system/app and framework-res.apk. However, these updates make no changes to them whatsoever...Meaning your phone will look just like a brand new phone without any modifications.
rc30 works thx Stericson made it easy for use
Issues with using the update.zip above
Hi all,
I just wanted to point out that after I applied the update.zip above and rebooted applications kept force closing randomly and constantly even through the initial setup (where you have to click the green android to start).
Prior to this, I had JF's RC30 1.3, and the engineering bootloader V2 no sigcheck.
First I did just a alt+s then a alt-w and alt+s. And still nothing.
I'm new to all this so I'm not even sure where to begin troubleshooting. Should I be using the HardSPL?
Thanks in advance and I appologize if this isn't the right place for this post.
Update:
After reflashing with JF's 1.3 RC30 and the problem persisted I noticed that there was a new release 1.31 and this has fixed the problem. I hope this helps anyone else who runs into the same problem.
I still don't know what went wrong though, can anyone shed some light on this? thanks.
Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson
Alright, I am a little confused........
So I downloaded testsign.zip and extracted it to the tools folder. Then I went into environmental variables and added CLASSPATH with the value D:\Android\tools\testsign.jar and now I am not sure what to do next. Can someone give me some clarification. And btw I am on XP but I can get on linux at home if I need it, but I am a total noob to all this stuff so be gentle.
I'm using http://www.fightforthepits.com/Androidstuff/update_Rc30.zip and have been encountering issues when the phone boots up. As soon as the initial phone setup comes up I get process force close errors, I extracted launcher.apk, edited the files I wanted, repacked it, signed it and then resigned the update.zip. Any ideas what I'm doing wrong? I'm already running JF's RC30 1.31
Did you repack it in linux? Did you resign Launcher.apk? Also, that update file was never meant to be used as a template for an update since it kind of wipes your phone. You should be using update_empy, to push your own theme.
If you want to do only one file at a time, flash that update(update_rc30) then adb push your file into system/app. There are lots of things that you can mess up, most of them are hard to catch too. At any rate, everyone who has made a theme can tell you it's not just a straight forward process, expect errors. I've had more than I count I know....
Trial and error is your best teacher
Stericson
Stericson said:
Did you repack it in linux? Did you resign Launcher.apk? Also, that update file was never meant to be used as a template for an update since it kind of wipes your phone. You should be using update_empy, to push your own theme.
If you want to do only one file at a time, flash that update(update_rc30) then adb push your file into system/app. There are lots of things that you can mess up, most of them are hard to catch too. At any rate, everyone who has made a theme can tell you it's not just a straight forward process, expect errors. I've had more than I count I know....
Trial and error is your best teacher
Stericson
Click to expand...
Click to collapse
Must .apk's be signed if they're pushed over ADB? I'm not running Linux, I'm repacking/signing in windows.
I also had the issue with force close when installing the resigned update from the first post, apps that shouldn't even run on start up were force closing.
Also the IM application was gone, had to do a wipe and go back to jf 1.31 to correct it
I will take another look at the update I provided...
Stericson
did you ever figure out how to change the text on the status bar from black to white?
to do that you have to rebuiuld the entire apk from source and edit an xml document
Stericson
has anyone tried making the icons bigger? I noticed they are 48x48 if we go bigger will that affect anything? Also has anyone been able to remove the text below the icons on the home screen? Oh and where is the tab located that has been made invisible?
*edit
well I tried making the icons bigger and it doesn't really do anything, they don't show up bigger on the screen. Might have something to do with the text underneath, not sure.
Kyeld said:
Must .apk's be signed if they're pushed over ADB? I'm not running Linux, I'm repacking/signing in windows.
Click to expand...
Click to collapse
yes they must be signed.
Hi,
I searched around and yet I couldn't find much on ROM dumping
Do you need a different utility for a different device? I'm guessing there is one for Diamond but I couldn't find one yet
Also, what do you need to do before dumping a rom? (is unlocking required etc.)
butterdori said:
Hi,
I searched around and yet I couldn't find much on ROM dumping
Do you need a different utility for a different device? I'm guessing there is one for Diamond but I couldn't find one yet
Also, what do you need to do before dumping a rom? (is unlocking required etc.)
Click to expand...
Click to collapse
No unlocking won't change your ROM so unlock away!!
There is a utility that does the dumping for you and here it is..
Er... I don't quite understand how that works....
The instruction says..
Install EnableRapi.cab on the phone.
Run Partition Addresses.bat.
Read Partition.Addresses.bat to find the four addresses.
Edit Dump My Phone to include the four addresses in place of the words.
Run Dump My Phone.
Rar and Send!
-------------------------
Should I do this while the phone is connected by activesync?
Also, once I run Dump My Phone, it gives me an error that says that the device isn't ready.
You can try my dumping kitchen, it's very simple to use!
(sorry, it's german ^^)
Steps on how to dump an unprotected ROM:
- place your RUU_Signed.nbh inside the kitchen
- start "1a. Entpacken.bat" to unpack and dump the NBH file
- start "3. Packages erstellen.bat" to make packages inside the dump-folder
- pick out what you need from the dumped ROM
Good cooking!
you get two ways of "dumping rom".
both ways get an other result.
about your asking for first way, i think you are a beginner.
your problem will not the dumping of roms,
the problem would be getting the dumping-file back to your phone.
i think, you read many or some threads where you think to get easy answers.
but the answers would be allwasy the same "google/search for answer"
its not a good time for hardcore beginners ...
please try to explain with simple words, what you have done and what you want do.
(not only for your brain, take your fingers and make "tik tik tiktik.." on keyboard ...
i asking this to you becaue for cooking and flashing you dont really need the specified answer of dumping roms. some kitchens looks BOAH-NOTHING UNDERSTAND, but at most, you need only copy ruu_signed.nbh to BaseRom and klicki-klicki BEGIN or START. than you get the rom-folders with easy understanding names (at most). for not needed programs delete files or folders. for the games you can delete all entertaionment-folders. for delete welcome.exe you have to delete one folder welcome.exe and the file welcome.exe.
this example is easy and at the same time one of the difficults thing by cooking. delete entertainment makes no problems. but delete welcome ... you have to know, what you do before you do it. without welcome.exe you cant fix your display with display-coordinates. and you have not the correct time. for getting a solution you need to study forums ... the coordinates of display can find in registry - > if you checked the registry before you starts to cook/flash. to get automatic time you need registry again, but its hard to get them.
sorry for big answer ....
heartsurfer008 said:
Well I am desparetly trying to cook a NAND build for my HD2 but there is pretty much less info available for me [a big NOOB in cooking] to try out my luck at cooking..!!!
So I'll appreciate if someone would put some light on it..!!!
PS: - I would appreciate if somebody can provide a detailed info..!!!
Click to expand...
Click to collapse
Finally the tutorial
Make your own Android Build for the HD2 by domineus I have always lived by these words- if you give a man a fish, he can eat for a day; but if you teach a man to fish you can eat for a lifetime. Android on the HD2 has always been an interesting thing for me and I know a lot of people that want to create their own builds, but have no idea how. If you ask a build creator or maybe someone in the htc-linux-chat how to get started, there may not be an answer. In fact, some of the perplexing behavior has left me puzzled in several ways - as if how to get an android build is a vaulted secret of knowledge like the holy grail. To be honest, it's not. It's a bit of hard work, a few nods in the right direction, and ultimately it's a community involved project. Just like miui development is a community project spanning actual continents to get this thing on our device every single week! It has led to a lot of questions, in my inbox, of how to begin. For a long time, the answer to the question was not answered until Cass helped me out. I want to do the same and contribute how to get a build of miui (or any android build) to the HTC HD2.
Things you will need
In order to properly start android development, it would be a good idea to make sure you have the following (a lot of it is no duh when you think about it)
A computer running linux
I can't stress that enough. While there is a lot of things you can do in windows, you will need some sort of linux distro in order to get android properly running on your HD2. There are a lot of linux distros you can use; with many using ubuntu as it is the most user friendly. I use Fedora and I am quite happy with the results. It's simple and effective. It gets the job done. Get a distro that you feel can get the job done.
Android SDK - either windows or linux
Android SDK is something that can be freely accessed and downloaded from the following location:
http://developer.android.com/sdk/index.html
It is a developer environment, but probably the most important thing you can use here (for the time being) is logcat. Logcat provides you to visually see the libraries and files working together to get android to work as well as if you run into an issue, it is the first thing you should resort to. For instance, boot reloop? Take a look at your logcat and try again.
A kernel
There are quite a few kernels available for android previously and they are divided into evo kernel or nexus one kernel. Many builders have transitioned to an evo kernel for PPP and a few other nice details but it is totally up to you. I highly recommend hastarin's kernel. For most of the time, it works well. But as you have noted, on MIUI, it hasn't been working as fantastic on other builds.
Donor Files
This is a bit difficult to find because it appears that the files that work best are nexus one builds without CM6.1 modification. So far, only one chef has that and it is tytung's nexus one build. Regardless of whose files you're using (e.g. tytung or darkstone's system which is the preferred choice) you will need a well working android build. You will be pulling several files in order to port.
MIUI itself (well any build honestly just miui is a good example)
This is a given. However, if you download from miui.com you will probably have an untranslated rom with odex files. That's bad. And in Chinese! It would be a good idea to browse the English forum for a deodexed rom with appropriate english translation (apps and frameworks)
-If pulling files from windows, you will need this
system extractor
http://uranus.chrysocome.net/linux/explore2fs-old.htm
I use that if I download in windows. It's relatively straight forward and it allows you to pull the files you need from the system.ext2 you're using and copying them to folders necessary.
build.prop
This you will need. You can find one here:
http://www.multiupload.com/B59IU3S6XY
Patience
Probably the most important thing. One thing I have noticed is you need patience to make it through. Sometimes, your build works, sometimes it doesn't. And it is difficult to still keep going. But gotta pull it all in and keep trying...it does pay off.
Okay so you have your files, a nice linux distribution, your build you want to port (MIUI preferrably) and you're ready to go. Now it's time to begin the process!
Step One - The Setup
I usually grab my files in windows before transitioning to my linux distro to finish the process. If you using windows 7 and you are using explore2fs, you will definitely have to right click on the exe and make it compatible by selecting compatible with windows vista. The file should also need to be run by administrator. If you don't know how to do that you can google compatibility in windows 7.
First thing is first. Create a new folder, you can call it donor_files if you want because name is arbitrary. The most important thing is to just name it. Within that folder, create a new folder called system. Enter the system directory and create a new folder called etc. Within etc, select Once that is done, create a new folder within etc called firmware. Once completed, return back to the system folder, create the folder called lib. In the lib folder, create a new folder called hw. So your folder should look like this:
Folder Name
-system
--etc
---firmware
--lib
---hw
So far so good? Excellent. Now, if you're in windows you will need to do a few things. Extract the system.ext2 of your donor build and place it somewhere you will remember (like your desktop). Now open up explore2fs, select file, and open image file. Under files of type (drop down), select all files and navigate to your system.ext2 file. You should now see the ext loaded on the left side of the program's workspace. Located is a very small + that allows you to view all directories in your ext2 file. Click that.
You will see several system folders on the left and files on the root. Since you haven't selected a specific folder, in the right hand view, you should see the file build.prop. If you did select a folder (like app) you will see some files. And that's okay too. Get a feel of the program.
Now you will do a test file pull. On the left hand side, select the folder etc. On the right window, you will see several files. We want AudioBTID.csv. Once you see the file, right click on AudioBTID.csv and select export file. Navigate to the donor file folder (or whatever you named it) and place the file in system/etc of that folder. Congratulations you just pulled your first file! But you will need a lot more files. Within the same directory, pull gps.conf, hosts, media_profiles.xml and the ppp folder. Now, navigate to firmware and pull the following files:
BCM4329B1_002.002.023.0360.0362.hcd default_france.acdb htcleo.acdb
BCM4329B1_002.002.023.0436.0439.hcd default_nel.acdb yamato_pfp.fw
bcm4329.hcd fw_bcm4329_apsta.bin yamato_pm4.fw
default.acdb fw_bcm4329.bin
Ideally you should not be able to find htcleo.acdb. You can find it here
http://gitorious.org/xdandroid_leo/q...eo/htcleo.acdb
Now in explore2fs, go to the lib directory and pull these files and place them in your lib directory:
libcamera.so
libcamera_client.so
libcameraservice.so
libhtc_ril_wrapper.so
libmm-omxcore.so
liboemcamera.so
libomx_aacdec_sharedlibrary.so
libomx_amrdec_sharedlibrary.so
libomx_amrenc_sharedlibrary.so
libomx_avcdec_sharedlibrary.so
libomx_m4vdec_sharedlibrary.so
libomx_mp3dec_sharedlibrary.so
libomx_sharedlibrary.so
libomx_wmadec_sharedlibrary.so
libomx_wmvdec_sharedlibrary.so
libOmxCore.so
libOmxVdec.so
libOmxVidEnc.so
libqcomm_omx.so
libstagefright_omx.so
Once those files are pulled, navigate to the hw folder of the system and pull the following files:
sensors.htcleo.so
lights.htcleo.so
Once those files are pulled, you can save your donor files to a flash drive and then boot into your linux distro. Login to superuser in terminal. For fedora, the proper method involves typing in su --login and entering your password you set up. Minimize your terminal window.
Extract the miui (or any other build) to your desktop (the focus is the system folder). Ensure the rom is deodexed and in your own language (if its miui, you will have to apply the proper language translations). Now copy the files you pulled from your donor build and apply it to the appropriate folders (usually a copy and a paste-literally). In this instance there will be duplicate files, overwrite them. That's the point! Do not forget the build.prop file I linked to earlier. You should add that to system folder.
So the files are copied, the next step is to restore the minimized terminal window (the one that is logged in as root). cd to where your system is located (not to the system folder itself). Now you will have to enter the following commands in terminal
chmod -R 777 system/etc
chmod 755 system/bin/*
chmod 755 system/xbin/*
rm system/etc/firmware/default*acdb (if you have sound in call issues)
touch system/etc/ppp/active (If you have latest wrapper and need ppp)
chown root:2000 system/bin/pppd
chmod 4755 system/bin/pppd
chown root:root system/xbin/su
chmod 4755 system/xbin/su
chown root:root system/xbin/hci*
chmod 4755 system/xbin/hci*
dd if=/dev/zero of=system.ext2 bs=1048576 count=256
mke2fs -F system.ext2
sudo mount -o loop system.ext2 /mnt2
cp -rp system/* /mnt2
sudo umount /mnt2
A few words on this that I must bold. the /mnt2 directory may not exist. If not, try mnt, that usually works
Once this is done, you will have a nice system.ext2. The only thing you'd need now is a rootfs, a kernel, clrcad.exe and a startup.txt file. Once that is done, you can test your build out.
Any questions
Special thanks to Cass and the htc-linux-chat for the few pointers they gave me.
The guide is by "domineus - http://www.miui-dev.com/" & I take no credit what so ever
Thanks to "white-energy" for giving us the link..!!!
Hope to have many more Chief's for our HD2, so that we [especially me] can satisfy our hunger to try different builds/ROM's..!!!
Happy Cooking..!!!
PLEASE PRESS THANKS IF YOU FOUND THIS THREAD USEFUL..!!!
+ 1... nobody wants to share information?
I don't know if this help but you can try
http://forum.xda-developers.com/showthread.php?t=897940
These kind of thread pop up once in awhile, but it's going no where, I've never seen well known chef show up in this kind of thread.
knowledge is power, maybe they dont want to share the power
Can anybody out there give us a step by step guide for cooking a NAND ROM for HD2..???
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
white-energy said:
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
Click to expand...
Click to collapse
Thank you, please check post 1..!!!
I've been looking for something like this. I want to create my own build for the recovery flasher. I guess the only thing needed would be how to convert from regular nand to recovery.
Thanks bro.
velayo said:
I've been looking for something like this. I want to create my own build for the recovery flasher. I guess the only thing needed would be how to convert from regular nand to recovery.
Thanks bro.
Click to expand...
Click to collapse
I was lookin for the same & credit goes to domineus & white-energy
& "white-energy" comes up with a NAND ROM..!!!
Congrats..!!!
white-energy said:
http://www.miui-dev.com/forums/showthread.php?481-Howto-Make-your-own-Android-Build-for-the-HD2
Instead of making a ext image, you should make a yaffs image.. so it can work on Nand
Click to expand...
Click to collapse
Are you sure its the only difference? Are the nand drivers stored only in the bootimg/initrd and not somewhere in the system.img?
yes or no will do for me thx
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
i am confused
Which explore 2fs do I download? There are 3 different ones one for binary one for code and optional update source code. I am a noob and tired of not having roms I am happy with. I have windows 7 and xp. I realize this will take time and I am good with it everything thats worth anything takes time.
deckoff said:
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
Click to expand...
Click to collapse
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
deckoff said:
Is there a way to edit system.bin files, that comes with the NAND builds. I suppose that is where the ROM is. I want to unpack, edit the included apps and repack. How it is done? How the bin file is done. Google does not give any satisfiable links, did a quick search, though...
Click to expand...
Click to collapse
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
anyone know how to edit or anything about initrd.gz?
hnamanh said:
anyone know how to edit or anything about initrd.gz?
Click to expand...
Click to collapse
It's an archive that can be decompressed and edited thru linux.
White-Energy use system.bin in his rom
Regarding initr and zimage, there is a guide that you can point me on ?
Thank you
KillaHurtz said:
I think you mean system.img not system.bin
You can extract them with the unyaffs.exe or with the unyaffs command under linux. I have written a guide with attatched utilities here
Additionally birksoffsjunk (seasoned WM guru & chef of ChuckyDroid, ChuckyROM, & Dexter) has made a batch program to make this process easier. It's a work in progress & somethings are still buggy so follow the thread
Between the utility birkoffsjunk made & the tutorial I wrote you should be able to successfully edit & run your own build. Hope this helps.
Click to expand...
Click to collapse
I have only green HTC
Hello
I would like to use Android on my HD2. I was searching and testing many ROMS but I didn´t find any rom which is usable for me. I would like to have a ROM that is without Sense, has Multilanguage support and is on Android 2.2 version.
So I decided that I would make my own.
0) I was reading
HTML:
http://forum.xda-developers.com/showpost.php?p=10291851&postcount=1
and made this procedure.
1)downloaded some ROM from here
2)unpacked this rom in linux with :
Code:
unyaffs system.img
then I got this directories:
Code:
app bin build.prop etc fonts framework lib media usr xbin
3)I downloaded update-cm-6.1.1-N1-signed.zip from CyanogenMod Forum > Downloads > Stable Mod > Nexus One and unpacked. I got : META-INF system boot.img.
4)I copied everything what was described step 0 from directories from step 2 to directory system from step 3
5)I downloaded and copied build.prop from step 0 to system
6) I updated permition like it is described in step 0
7) I created system.img with command : mkyaffs2image . ../system.img
Then I copied this system.img from linux to my windows and put this file in directory in which was different NAND rom. (replaced system.img). After that I flashed my phone and it did not work. Screen was frozen after booting and only green HTC was on display.
Can somebody please help me and give me some advice or some small howto. Does anybody know what can be wrong?
Thank you
Michal Fichtner
I appreciate the guide but damn that is hard to read. It really needs some sort of structure to it, titling proper paragraphs etc.
Hi,
it is possible to combi the dropdown energy widget froom miui and the gingerbread lockscreen into Desire HD Build?
Thats was awesome !
Sorry for my bad english