HOW TO COOK ROMS USING SPOCKY'S KITCHEN
1. Download the kitchen and unzip it.
2. Download the eXpo or IQ base rom and place it in the folder BaseRom\GW820 (the file will have a dz extention)
3. Launch Start.bat and enter 7 and press enter. This will allow the kitchen to know you are building a rom for the for the eXpo/IQ.
4. Press a then enter. This will extract the files you need to build a rom from the .dz file.
5. Press b then enter. This will extract the files from the flash.bin file. It will also create a xip.bin file in
TOOLS\XIPPORT. If you are not porting a new build don't worry about the xip.bin file. If you are porting
a new build we will get to that soon.
6. Press c then enter. This will extract the sys files and the oem files into the temp\dump folder.
7. Now you are going to arrange your files that are in temp\dump into two separate folders OEM\GW820
and SYS\YourBuildVersion (eg. SYS\23563). Here is what you will put in each folder:
*Note: If you are porting a new build (such as a 6.5.5 build) you will be downloading the files that
match your build and will not find them in the temp\dump folder.
a. You will see a folder named OEM. Take the contents of that folder and put it into OEM\GW820.
b. Now you will create 3 folders within SYS\YourBuildNumber. DPI_192, dpi_192_resh_480_resv_800,
and SHARED.
c. Now within each of those folders you will create two folders; 0409 and COMMON.
d. Now go back to temp\dump (I recommend having two windows open. One for temp\dump and the
the other for SYS\YourBuildNumber.) Go into the temp\dump\SYS\0409 folder. Now copy every folder
ending in Lang_0409_DPI_192 into your DPI_192\0409 folder.
e. Next copy all files ending in DPI_192 from temp\dump\SYS\COMMON folder to your
DPI_192\COMMON.
f. After that copy Base_Lang_0409_DPI_192_RESH_480_RESV_800 and
Themes_Lang_0409_DPI_192_RESH_480_RESV_800 from temp\dump\0409 folder to
your dpi_192_resh_480_resv_800\0409.
g. Next copy base_dpi_192_resh_480_resv_800, MediaOS_dpi_192_resh_480_resv_800,
MediaOS_dpi_192_resh_480_resv_800, and Redist_dpi_192_resh_480_resv_800 from
temp\dump\SYS\COMMON to dpi_192_resh_480_resv_800\COMMON.
h. After that copy all files ending in Lang_0409 from temp\dump\SYS\0409 to SHARED\0409.
i. Finally copy all the rest of the files from temp\dump\SYS\COMMON to SHARED\COMMON.
*Note: If you are porting a build then do all of step 8. If you are rebuilding the stock rom do steps 8,
8d, 8e, 8m, 8n, and 8o. For some reason the kitchen won't build the rom properly if you don't.
8. Go back to the windows launched by start.bat. Press 9 and enter. This will bring up the options you will
use to port.
a. You will need a xip.bin that matches your build. It should come with the build files you downloaded.
b. Go to tools\xipport and rename the xip.bin that is in the folder. (eg. xip.GW820.bin) You will need this
file later.
c. Copy the xip.bin file you downloaded to tools\xipport. (Make sure it is named xip.bin)
d. On the start.bat windows press j and enter to launch xipport.
e. Click dump xip.bin
f. Click "make pkgs".
g. Now, you've got a "out" folder with files and modules separated in different subfolders.
Rename the out folder into something else. (eg. OUT.235xx).
h. Delete the downloaded xip.bin (or rename it if you want to save it) and rename the original
xip.bin back to xip.bin.
i. Repeat steps 8d-8f.
j. Now, you've got a out folder with files and modules separated in different subfolders from eXpo/IQ
base ROM.
k. Now replace modules\msxipkernel and files\msxipkernel with the ones from the newer xip.
(folder OUT.235xx)
l. Click "undo" to flatten out folder again.
m. Bring up the start.bat windows agin. Press k and enter. When a message tells you so, click "realloc
p", "write maps", "build xip_out.bin (ignore error messages in reallocp part). And finally, hit a key on
the dos prompt to finish this step (DO NOT HIT A KEY BEFORE BUILDING XIP WITH XIPPORT ELSE IT
WON'T WORK).
n. Bring up the start.bat windows and press "l" and enter to use the new xip in the kitchen
(xip_out.bin).
o. In the start.bat window press 9 and enter to go back to the normal options. (Now you have
everything you need to port. Proceed to step 9)
9. Bring up the start.bat windows and press d and enter. This will dump your xip.bin file.
10. Go to the ROM\GW820 folder. You will see a XIP folder. Go into that folder and then go into the
WinCENLS_WWE folder and copy the wince.nls file. Now go into the OEMXIPKERNEL and paste wince.nls in
there. After that copy the OEMXIPKERNEL folder. Next create a folder in ROM\GW820 and name it your
build # (eg. 23563). Now paste OEMXIPKERNEL into that folder. After that copy MSXIPKernel from
ROM\GW820\XIP. Go to ROM\SHARED and create a folder and name it your build # (eg. 23563). Paste
MSXIPKernel into that folder. It is important both folders are named the same.
*Note for those that are porting:
If you are porting a new build you need to go to TOOLS\XIPPORT\OUT.235xx\FILE\MSXIPKernel
and copy 723fb954-d931-4348-b672-82a188e587b5.dsm
After that paste the file in ROM\SHARED\YourBuildNumber\MSXIPKernel. This will allow the correct build
number to show in the about screen on your device
11. Bring up the start.bat window again. Press e and enter to launch the ervius visual platformrebuilder.
(Note: If building with vista or windows 7 you will need to right click on erviuskitchen, select
properties,choose the compatibility tab, check Run this program as an administrator, and click ok).
Once it is launched you will need to set a few options on the top bar of the kitchen. First select
GW820 as your device. Then select your rom res. Choose dpi_192_resh_480_resv_800. After that
select your XIP and SYS Builds. Finally you can select to leave out certain SYS files from your rom, but
do be warned that leaving out some SYS files can result in a rom that won't boot. Once you have
made all your selections click create rom. The kitchen will now build your rom. When it is done it will
launch a flashing program just exit it and the visual kitchen. Go back to the start.bat prompt.
12. Press f and enter. This will build the new imgfs.bin.
13. Press g and enter. This will build the new flash.bin.
There is an additional step for IQ owners. Download this ADD-ON FILE and place it in Baserom\GW820. Without it
you won't be able to repack the rom into a dz file.
14. Press h and enter. Then enter a name for your new rom (no spaces) and press enter. It will then create
a new dz file for you. You can find it in BuiltRom\GW820. It will be called rom.dz. This is the file you will
use to flash your phone.
Your rom is now built. Good luck and I can't wait to see what you guys cook up.
Here is the link to Spocky's Kitchen:
Spocky's LG Multidevice Kitchen 2.2
eXpo Add-on Package:
eXpo Add-on Part 1
expo Add-on Part 2
IQ Add-on Package:
IQ Add-on Part 1
IQ Add-on Part 2
Note 1: To use an add-on download all parts to the same folder and extract Part 1. Part 2 will extract automatically. Once they are extracted move the folders to your kitchen, overriding the existing folders.
Note 2: IQ users - If you are using the add-on package; remove fwua.mbn from Baserom\GW820 and place it back in there when after step 13.
Note 3: If you use the add-on only do steps 1-3, 5, 8, 8d, 8e, 8m, 8n, 8o, 9, and 11-14. If you are porting arrange your folders like in step 7 and also do all of step 8 and step 10.
Note 4: Step 9 needs to be done because there is a process in step 9 other than dumping the xip.bin that allows the ervius visual platformrebuilder to build a rom correctly.
Reserved for future use.
Awesome Tutorial Dark, thanks.
I hope questions are OK in this thread (being a sticky and all)
In the process of cooking my own ROM, I figured I would start by dumping and building a stock Telus IQ ROM.
I was able to get it to build and flash, but for some reason none of my mxip*.provxml files were processed. I don't mean user created mxip*.provxml files, I haven't changed anything in the ROM yet.
This is immediately apparent because if mxipupdate_metabase_001.provxml is not processed, themes do not work.
As a test, I renamed it to mxipupdate_metabase_001.xml and loaded it with FdcSoft Taskmanager and themes started working again.
They are all there in \Windows, they just didn't get processed.
Any ideas?
Note that I used Platformrebuilder to process my packages, not Visual Kitchen.
trueg said:
I hope questions are OK in this thread (being a sticky and all)
In the process of cooking my own ROM, I figured I would start by dumping and building a stock Telus IQ ROM.
I was able to get it to build and flash, but for some reason none of my mxip*.provxml files were processed. I don't mean user created mxip*.provxml files, I haven't changed anything in the ROM yet.
This is immediately apparent because if mxipupdate_metabase_001.provxml is not processed, themes do not work.
As a test, I renamed it to mxipupdate_metabase_001.xml and loaded it with FdcSoft Taskmanager and themes started working again.
They are all there in \Windows, they just didn't get processed.
Any ideas?
Note that I used Platformrebuilder to process my packages, not Visual Kitchen.
Click to expand...
Click to collapse
Use the visual kitchen. LG roms are weird. They are built differently than those from HTC.
But isn't Visual Kitchen just a front end for Platformrebuilder? I would prefer not to use Visual Kitchen if at all possible.
Hmm, I'm having the same problem when I use Visual Kitchen.
trueg said:
Hmm, I'm having the same problem when I use Visual Kitchen.
Click to expand...
Click to collapse
Idk if its the same issue, but im having problem with kitchen handling modules :\
I used WinDiff to compare the dump folder created by Visual Kitchen and the one created by just using Platformrebuilder and they were nearly identical. The Visual Kitchen dump had an empty folder called \build, a file called config.old and somehow a thumbs.db snuck in there. None of these would have made a difference, which explains why the resulting ROM behaves the same.
So, I'm not sure what to look at next.
It is something to do with the XIP.
Initially, I wasn't doing anything with the XIP. I just wanted to build a stock ROM, so I dumped the OEM & SYS and then built it back up with the original xip.bin. This mostly worked except for the mxip files not running.
Then I tried using the xip.bin created by Platformrebuilder (found in \temp), but that would cause my IQ to keep rebooting.
Finally, I did all of the steps involved in porting a new XIP, even though I wasn't actually porting any new code, and that worked.
Just wanted to post an update..
The issue with my provxmls not running was due to redundant DSM pointers. When Platformrebuilder creates the dump folder, it mergers all of the DSM files from the XIP & IMGFS into a single file in IMGFS. When I then used the stock xip.bin, it created redundant pointers since the same files were being referenced by the XIP and IMGFS. To correct the issue, I had to dump the XIP, delete the DSM files and then build a new xip.bin. Now all is well.
trueg said:
Just wanted to post an update..
The issue with my provxmls not running was due to redundant DSM pointers. When Platformrebuilder creates the dump folder, it mergers all of the DSM files from the XIP & IMGFS into a single file in IMGFS. When I then used the stock xip.bin, it created redundant pointers since the same files were being referenced by the XIP and IMGFS. To correct the issue, I had to dump the XIP, delete the DSM files and then build a new xip.bin. Now all is well.
Click to expand...
Click to collapse
Awesome, glad you got it worked out. Now u need to help me get Sense2.5 work on our expos xD.
This Device have only one Cookers??
And You do not want more?
Cheers
Nokser said:
This Device have only one Cookers??
And You do not want more?
Cheers
Click to expand...
Click to collapse
Dark's ROMs don't leave much to be desired.
I have a private build running (I know, I should share, but I cooked in stuff I "shouldn't" have .. another one will be forthcoming) and there's definitely other people over on lg-expo.com cooking.
I'd expect we'll see more in the coming weeks. Most of the (vocal) community is fairly new to cooking; and because of a number of factors, fairly small compared to others (lg-expo.com only has about 525 registered members at the time of this posting)
Understand.... thanks
I have been working on my own ROM since a day or two after I received my GW825. It's working very well, but it will probably be a little while before I post anything.
trueg said:
I have been working on my own ROM since a day or two after I received my GW825. It's working very well, but it will probably be a little while before I post anything.
Click to expand...
Click to collapse
same here, ive been working on getting sense to work on my expo...its being a b%$# lol.
At one point I started porting pretty much all of the HD2 code over to my IQ. Most of it worked fine. I got bored and switched back to just LG code before I made it to SenseUI. What problems are you having?
HTC stuff not linking liking my expo lol. s2.5 can get up and working minus 2 things active desktop(pictures, weather animations work) and my locations, both things i can live without. BUT its causing my internet to not be able to connect. Ital work on first boot then after that it wont. Then if i plug my phone into my computer and it establishes a async connection after that it can connect to internet fine....
very odd lol.
xdapants said:
Dark's ROMs don't leave much to be desired.
Click to expand...
Click to collapse
I would just like to clear up something about this statement. My roms are bare bones. I leave practically nothing in them so people can customize them the way they want. Some people don't like that. Apparently xdapants is one of them. Also those that want to use HTC software such as their UI, I have found that there is a lot of HTC stuff that isn't friendly with LG. There are cabs out there for those that want HTC's UI, but not all features may work. Finally, I posted the files for everything I removed so people can make cabs for any of the removed software.
Related
Does anyone know how to make custom roms for devices like the Excalibur or other Smartphones. I want to remove a lot of the clutter and add some applications of my own.
JAmerican
Not there yet AFAIK.
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
momentarylapseofreason said:
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
Click to expand...
Click to collapse
Bug fixes! Even if you build a custom rom, you would want to start with the latest available OS to get in on whatever bug fixes have been added. Then you would rip it apart and add/remove whatever you wanted. Sometimes the new OS would also have added/improved features, but the bug fixes is the main one.
mar11974 said:
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
Click to expand...
Click to collapse
Thanks for the insight. I reached as for as extracting the .NBH into .NB files with OS, GSM etc. How do you extract these. The PKG Tool didn't work for me and the Hypercore tools aren't working right either.
JAmerican
Hey all,
I was able to downgrade to WM5 and I am starting to understand a few things regarding ROM building but I still don't know how to edit the Windows.nb or OS.nb file. Can anyone offer suggestions. I am trying to optimize it so that there is less clutter.
JAmerican
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
da_mayhem said:
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
Click to expand...
Click to collapse
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
JAmerican said:
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
Click to expand...
Click to collapse
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
da_mayhem said:
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
Click to expand...
Click to collapse
Thanks for sharing! I was finally able to dump it. Now to see if I can mess around and get it to build! Wish me luck .
JAmerican
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
da_mayhem said:
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
Click to expand...
Click to collapse
I deleted some files from the ROM and rebuilt it but it was in .NBA format. I don't remember exactly what I did but I think I renamed the file to .NB and made a .NBH file out of it. Then Flashed my device. I got as far as the WM screen and was stuck there. I reflashed with the Standard WM6 ROM from T-Mobile. .
I'll try some more messing around. I really want to get some cooked roms for Smartphone edition.
JAmerican
Your right about files missing. I was able to extract the ROM and its packages and get two folders (ROM and SYS) along with other packages. The program I used (Package Tool) states that I am missing the following files:
[Missing Files]
SYS\MSXIPKernel
MODULE: busenum.dll
MODULE: cachefilt.dll
MODULE: certmod.dll
MODULE: coredll.dll
MODULE: device.exe
MODULE: devmgr.dll
MODULE: diskcache.dll
MODULE: encfilt.dll
MODULE: fatfsd.dll
MODULE: fatutil.dll
MODULE: filesys.exe
MODULE: fsdmgr.dll
MODULE: fsreplxfilt.dll
MODULE: hd.dll
MODULE: imgfs.dll
MODULE: mspart.dll
MODULE: osaxst0.dll
MODULE: pm.dll
MODULE: regenum.dll
SYS\WinCENLS_WWE
File: wince.nls
OEM\LangDB
File: initflashfiles.dat
File: mxip_lang.vol
OEM\OEMXIPKERNEL
File: boot.hv
File: boot.rgu
MODULE: cecompr.dll
MODULE: ceddk.dll
MODULE: HtcFsdspy.dll
File: mxip_initdb.vol
MODULE: nk.exe
MODULE: ONDisk.dll
and these files are in the Windows folder as well as other locations on my device. The only problem is that the device denies me access to these files. Is there a way to access these DLLs with a powerful file manager. I tried Resco and Total Commander to no avail. Anyway to trick the device into allowing me to copy these files?
Thanks.
JAmerican
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Ok so I was able to extract the T-Mobile WM6 ROM, I was able to use the Package Tool to get it seperated into a SYS and OEM folder. I deleted things like Live Messenger and Windows Live. I put the updated version of Live Search in ROM. I only added one other application, CeleTask. I didn't want to put too much work into tweaking this thing and find it not working. I am downloading the CreateOS.exe and CreateROM.bat files and will try to compile this thing. Wish me luck.
JAmerican
jockyw2001 said:
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Click to expand...
Click to collapse
Hey friend. I know this is not appropriate place to post this, but since you know my situation on the wifi of my phone. Would it be possible to put a working reverse flash of a tmobile dash onto mine and fix the wifi. I have tried everything. And you have been very helpful and it is much appreciated.
keep up the progress guys, i can't wait to try some of the cooked roms from users on this site
Good luck, i can't wait either....
Hey guys,
I used a tool to try and convert my unpacked ROM back to a packed (one folder ROM) and it deleted all my progress. Go figure. So I have to basically start all over again. This time though, instead of making all the changes. I am just going to remove like myFaves, update LiveSearch and add one of my own applications as well as one of my favorite applications and see if I can flash my Dash with it.
Somewhat but its my fault for not backing up.
JAmerican
THIS IS MY WM6.1 ROM KITCHEN
≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈≈
{REMEMBER IM NOT RESPONSIBLE IF YOU BRAKE YOUR PHONE}
{REMEMBER IM NOT RESPONSIBLE IF YOU BRAKE YOUR PHONE}
{REMEMBER IM NOT RESPONSIBLE IF YOU BRAKE YOUR PHONE}
{STEP 1}
EXTRACT ExcaliburKitchen.ZIP TO C:\
{STEP 2}
DOWNLOAD MY ROM FROM HERE:- http://forum.xda-developers.com/showthread.php?t=387355
IF YOU DONT WHAT TO DOWNLOAD MY ROM THEN DOWNLOAD KAVANAS FROM HERE:- http://forum.xda-developers.com/showthread.php?t=374890
{STEP 3}
EXTRACT THE ROM FROM THE .ZIP OR .EXE
{STEP 4}
PUT RUU_signed.nbh IN TO C:\ExcaliburKitchen\SOURCE
{STEP 5}
NOW CLICK ON (1) DumpOS.bat
{STEP 6}
NOW GOTO WORK FOLDER AND YOU'LL SEE A FOLDER CALLED DUMP GO INTO IT
{STEP 7}
NOW IN THIS FOLDER YOU CAN ADD WHAT YOU WHAT AND YOU CAN TAKE THINGS OUT OF THE ROM
{STEP 8}
IN THE DUMP FOLDER YOU'LL FIND A FILE CALLED InitCmd.ccs IN THIS FILE IS WERE YOU PUT THE START MENU LINK AND THE REGISTRY SETTING FOR YOUR SOFTWARE
IF YOU OPEN IT WITH NOTEPAD IT WILL LOOK LIKE THIS FOR THE LINKS:-
------------------------------------------------------------------
LINK %M\Messaging.lnk,:MSINBOX,,:mailapp
LINK %M\Settings.lnk,:MSSettings,,:settings
LINK %M\Contacts.lnk,:MSCONTACTS,,:contactsapp
LINK %M\Calendar.lnk,:MSCALENDAR,,:calendarapp
LINK %M\Internet Explorer.lnk,:MSPIE,,eapp
LINK %M\Windows Media.lnk,wmplayer.exe,,:mediaplayerapp
LINK %M\Pictures & Videos.lnk,:MSPIMG,,imgapp
LINK %M\File Explorer.lnk,:MSFEXPLORE,,:fexplore
LINK %M\Speed Dial.lnk,:MSScut,,:scutapp
LINK %M\Call History.lnk,:MSClog,,:clogapp
LINK %M\Voice Notes.lnk,:MSTVNOTES,,:notesapp
LINK %M\Tasks.lnk,:MSTASKS,,:tasksapp
LINK %M\ActiveSync.lnk,:MSSYNCAPP,,:syncapp
LINK %M\Camera.lnk,Camera.exe,/i,:cameraapp
LINK %M\Video Recorder.lnk,Camera.exe,/v,:videoapp
LINK %M\Welcome Center.lnk,:MSWelcomeCenter,,:welcomecenterapp
LINK %M\Windows Live.lnk,WLMLauncher.exe,,:WLMLauncher
LINK %M\Messenger.lnk,WLMMessenger.exe,,:WLMMessenger
LINK %M\Text Notes.lnk,TextNotes.exe,,:textnotesapp
LINK %M\Java VM.lnk,jbed.exe
TO ADD YOUR LINK TO YOUR START MENU ADD YOUR LINK TO THE BOTTOM OF THE LINKS EG:-
LINK %M\Video Recorder.lnk,Camera.exe,/v,:videoapp
LINK %M\Welcome Center.lnk,:MSWelcomeCenter,,:welcomecenterapp
LINK %M\Windows Live.lnk,WLMLauncher.exe,,:WLMLauncher
LINK %M\Messenger.lnk,WLMMessenger.exe,,:WLMMessenger
LINK %M\Text Notes.lnk,TextNotes.exe,,:textnotesapp
LINK %M\Java VM.lnk,jbed.exe
LINK %M\XXXX XXX.lnk,XXXXXX.EXE
AND FOR THE REGISTRY IT WILL LOOK LIKE THIS:-
-----------------------------------------------
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Ime File"="et9ime.dll"
"Layout Text"="eT9 IME"
"Keyboard Layout"="00000409"
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9]
"AvailableLanguages"="0109,0105,0113,011B,011F,0108,0115,0116,0118,010E"
"DefaultLanguage"=dword:00000109
"InstallFolder"="\\Windows"
"ShowExactKeyStrokeThreshold"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME]
TO ADD YOUR SOFTWARE REGISTRY ADD IT TO THE REGISTRY PART AT THE BOTTOM EG:-
[HKEY_LOCAL_MACHINE\Security\CHome\DefaultSettings\Settings\Launch]
"GUID"="{4B998C14-3801-4a8e-9B20-5DFE58B19C39}"
"PLUGINICONNAME"="CHomeGeneric_Settings_PluginIcon.png"
"PICTURES"="\\windows\\CHome_settings_launch.png"
"SK2URL"=":MSSettings;home_setup.cpl.xml"
"TITLETEXT"="Settings"
"TEXT1"="CHome Settings"
"TEXT2"=""
[HKEY_LOCAL_MACHINE\Security\CHome\DefaultSettings\Settings\XXXXX]
"GUID"="{4B998C14-3801-4a8e-9B20-5DFE58B19C39}"
"PLUGINICONNAME"="XXXXXXXXXXXXXXX"
"PICTURES"="\\windows\\XXXXXXXXXX"
"SK2URL"=":MSSettings;XXXXXXXXX"
"TITLETEXT"="XXXXXXXX"
"TEXT1"="XXXXXXXXXXX"
"TEXT2"="XXXXX"
THEN SAVE IT
{STEP 9}
CLICK ON BUILDOS.DAT WAIT TO ITS FINSHED THEN IT WILL OPEN htcrt WHICH CONVERTS THE NB TO NBH
1 CLICK BUILD
2 CLICK DEVICE
3 PICK Excalibur
4 CLICK OS THEN FIND 02_OS.nb IN C:\ExcaliburKitchen\Work AND CLICK ON IT
5 CLICK SPLASH FIND 00_MainSplash.nb IN C:\ExcaliburKitchen\Work AND CLICK ON IT
6 CLICK ON RADIO THEN FIND 01_GSM.nb C:\ExcaliburKitchen\Work AND CLICK ON IT
7 ENTER ANY VERSION NUMBER YOU LIKE THEN CLICK BUILD A WINDOW WILL OPEN GO TO C:\ExcaliburKitchen\FLASH ROM\ AND SAVE AS RUU_signed.nbh
THEN FLASH YOUR PHONE WITH YOUR NEW ROM
REMEMBER IM NOT RESPONSIBLE IF YOU BRAKE YOUR PHONE
By RickWyatt @ xda developers
heres the link :- http://rapidshare.com/files/119437757/ExcaliburKitchen.zip
What if there is no InitCmd.ccs file? Trying to use TMO WM6 ROM. This is the same problem I had trying to use the other kitchens (I thought it was me).
Boo Boo looks almost like a clean ROM:
Tried anyways only removing the handango in hand links (two files) from the rom and built RUU_signed.nbh with os only. Flashed fine with no issues, but most T-Mobile specific apps/settings did not load and do not show in the startmenu. TMO homescreens, ringtones, favorites, etc did not get placed/installed correctly. MyFaves (HTC App) seems to have installed correctly although it tries to load TMO homescreen which is now in the Windows directory, TMO Internet Settings loaded, but the startmenu is laid out differently. Most TMO Customizations just got installed in Windows directory where they will not install (homescreens, ringtones, etc. don't work under Windows directory). The files are there, but the phone runs as if they are missing (almost like running the Brightpoint ROM). The only TMO customizations Visible are the Startup and Shutdown screens, and winwap. Somehow the TMO customizations did not get loaded, but everything seems to work fine.
Recommend the following changes to make the kitchen more universal.
added command to DumpOS.bat
ren *os.nb os.nb
changed filename in BuildOS.bat to os.nb
Just an idea since not all ROM's have the same XX_os.nb filename.
ROM Cooking Hints?
Hi Ricky, and thanks a lot for such a good work, and sharing your knowledge !!!
A couple of questions around ROM cooking ...
- How does ROM size affect WM? I mean, adding files, apps, etc. to the rom makes WM having less memory to run programs or store files, or run slower, for example?
- I guess adding more and more files might create a ROM that does not fit in the Excalibur and might break it if flashed. How can we know when to stop adding stuff?
Thanks!!
EarthQ said:
Hi Ricky, and thanks a lot for such a good work, and sharing your knowledge !!!
A couple of questions around ROM cooking ...
- How does ROM size affect WM? I mean, adding files, apps, etc. to the rom makes WM having less memory to run programs or store files, or run slower, for example?
- I guess adding more and more files might create a ROM that does not fit in the Excalibur and might break it if flashed. How can we know when to stop adding stuff?
Thanks!!
Click to expand...
Click to collapse
if you add stuff to the rom it will slow down the rom but not to much & if you take things out of the rom it will get faster
and if you add to much software then the kitchen will crash
How do you remove programs? What all do you need to delete to safely remove it from your phone?
Did my first attempt at cooking. IT was successful, and I am using it know, but some changes, such as files I added to the InitCmd.tgz worked, and were extracted fine. Other tweaks, such as changing a CPanel's contents and adding media to the windows folder did not work, and came out as if I hadn't changed anything at all.
Do I need to make Cpanel changes in two places (Initcmd and somewhere else?) Is there another step to making files "stick"?
you also have to edit user.hv and default.hv
rickwyatt said:
you also have to edit user.hv and default.hv
Click to expand...
Click to collapse
Thank you!
rickwyatt said:
you also have to edit user.hv and default.hv
Click to expand...
Click to collapse
Ok, I don't get it. Rick, or anyone, can you explain the work flow a little more? I can't find a user.hv, or a default.hv in the dump contents, nor do I know what to do when I do find them. I see there is a assembler/disassembler toolset in the kitchen, but it fails to find any .hv's either. Is there anything missing in the steps above?
Profezza said:
Ok, I don't get it. Rick, or anyone, can you explain the work flow a little more? I can't find a user.hv, or a default.hv in the dump contents, nor do I know what to do when I do find them. I see there is a assembler/disassembler toolset in the kitchen, but it fails to find any .hv's either. Is there anything missing in the steps above?
Click to expand...
Click to collapse
you have to unhide system files what you have to do is move user.hv and default.hv to to edit user.hv&default.hv folder press disassemble.dat it the make to more files called HKCU.reg and HKLM.reg now download emediter freeware and save HKCU.reg and HKLM.reg UTF-16LE Now move HKCU.reg to notepad2.exe edit it then press save do the same for HKLM.reg then what you do is make a dump folder then press Reassemble.dat if there is no errors in the hv files then you will find user.hv and default.hv in the dump folder that you just made if the is an error it command prompt will tell you were the error is once dont move the hv files back to you dump folder
I think I got all that! Thanks a bunch.
Rickwyatt,
When I run Disassemble.bat it tells me it can't find the default.hv and user.hv file and then it tells me that there is no regedit4.txt file in the Resources directory.
I checked the locations of the files, and there isn't a regedit4.txt file but the default.hv and user.hv files are right where they are supposed to be. Any ideas?
[edit]
Nevermind... unchecked the "hidden" box on the two files... it still doesn't find the regedit4.txt that it's claiming is missing
Ok, so I successfully was able to use this to mod the 1.6 Rose ROM, but I noticed that the InitCmd.ccs looks far different. How do I edit the menu items in this ROM?
Specifically I am wanting to remove a bunch of stuff I don't use from the ROM:
- Orneta Calculator
- OMAP Clock
- Getting Started
- SMS Tool Pack
- Light Config
- Messenger
- Streaming Media
- Windows Live
- Resco Explorer
- CHome
Also if anyone can post the list of files that I would need to delete out of the exploded ROM for the above, that would be great... especially CHome.
I do want to give this ROM serious props. I love it! I just want to pare down the things I personally have no interest in using, but I don't want to delete the wrong files, and/or not remove the menu items in the ROM for them.
Rickwyatt,
The Disassemble.bat file keeps crashing. It tells me that regedit4.txt not found in the Resources directory. It creates a hkcu.txt and an hklm.txt file though.
open hkcu.txt hklm.txt then add REGEDIT4 to the top line then save rename hkcu.txt hklm.txt to hkcu.reg hklm.reg
New HTCRT.exe version 1.1.4
windows media player playing not smooth.
One bug in my own rom (base on your kitchen): Windows media player playing not smooth. How can i fix it, what reg can i edit?
travis.garrison said:
Ok, so I successfully was able to use this to mod the 1.6 Rose ROM, but I noticed that the InitCmd.ccs looks far different. How do I edit the menu items in this ROM?
Specifically I am wanting to remove a bunch of stuff I don't use from the ROM:
- Orneta Calculator
- OMAP Clock
- Getting Started
- SMS Tool Pack
- Light Config
- Messenger
- Streaming Media
- Windows Live
- Resco Explorer
- CHome
Also if anyone can post the list of files that I would need to delete out of the exploded ROM for the above, that would be great... especially CHome.
I do want to give this ROM serious props. I love it! I just want to pare down the things I personally have no interest in using, but I don't want to delete the wrong files, and/or not remove the menu items in the ROM for them.
Click to expand...
Click to collapse
Looking to dump a lot of the same things. If I remove them from the "dump" folder, is that the end of it or do registry settings need to be removed as well. First time doing something like this, thanks for the help and patience.
Instead of going through this tedious process.. why not start with a very light version of the ROM and just add what you need ?
Hi guys,
I decided to open a blog which explains how to cook roms for the i780. There are very few chefs, and cooking is a really hard science to learn without help! So, I decided that I take the time and write posts so that everyone could learn the process in a methodical manner and cook roms in the future!
I'd slowly write posts explaining each step of the process in detail, so that we can have more people learning how to cook and make the i780 community more happening
Head over to this URL to check out the first few posts -
http://i780romdev.blogspot.com
Update:
Attached core kitchen tools that you'll need to use! Enjoy!
cheers
San
I never was a fan of this forum, not sure why, maybe because I use a ASUS P527 and there are not proper instructions on how to create a custom ROM, I appreciate your taking the initiative
I think its good fun to try and figure out things on your own
Non-HTC devices do have a very small fan base unfortunately....and ironically, HTC makes the crappiest devices imo (highly crash prone, buggy, lousy drivers, useless qualcomm processor)!
You can apply the same tools and techniques even to cook asus roms....its not all that different
cheers
wooooooow thanks a lot buddy finally we have it also !!!
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
benveq said:
when will u release part 3? and also can u give the links of programs? like pkgtools_? coz i tried to download it from somewhere else and it had virus
Click to expand...
Click to collapse
hi m8!
i'll try and upload the set of tools shortly. You can get it in any of the kitchens posted for the i780 here. I'll however consolidate them and add it in this post as an attachment!
Part 3 - very soon
cheers!
You guy thanks for sharing your experience at cook ROMS,I whink I need this for my SmartPhone.
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
kitchen tools attached in the first post.
enjoy
dreamtheater39 said:
Hey guys, just dropped the next part of the series on the blog. Check out http://i780romdev.blogspot.com
Of course, the same theory, tools and understanding goes to cook for any other device too
cheers
Click to expand...
Click to collapse
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
benveq said:
yeah, now i am reading part 3 and u really teach very well! i think i will cook my own room soon with ur help i wanna ask a question if i dont want ms office and internet explorer in my rom which folders should i delete? i wanna add different office program
Click to expand...
Click to collapse
To remove a package, you can get rid of the corresponding folders in your SYS folder. But its not recommended that you knock off office/ie as they might be referenced within other apps. You can always take it off, build a rom and see if everything works fine
For example, to remove IE, just delete your Browsing, Browsing_DPI_xx and Browsing_Lang_XXXX, BROWSINGCORE, browsingie, browsingie_LANG_XXXX folders. That should get rid of IE for you! Then you need to recreate your bin!
cheers
thanks a lot for kitchen tools and ur explanations! i read ur blog all the time great work!!
The next post is up
cheers
dreamtheater39 said:
The next post is up
cheers
Click to expand...
Click to collapse
yes i read it, and u r teaching with examples it is great
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
benveq said:
i have two problems while i am using ervius pkgtools
1. when i open dumo folder it shows
[Missing Manifests]
(Maybe):\ROM\XIP\45116509-e364-4775-9098-c25f0b1fbac2.dsm
(Maybe):\ROM\XIP\d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
(Maybe):\ROM\XIP\723fb954-d931-4348-b672-82a188e587b5.dsm
(Maybe):\ROM\XIP\1a22bb67-d4c4-7bb4-c5d2-75cb3a85c45b.dsm
(Maybe):\ROM\XIP\449da4ef-e9c1-5cb4-2ec5-fb9b4c27a865.dsm
are these important dsm files?
Click to expand...
Click to collapse
This is not important....ignore them, its normal
benveq said:
2. when i press build packages it gives this error:
not found: select .os file to extract XIP
and i extract xip file using osbntool as xip.bin
any solutions for both of these?
Click to expand...
Click to collapse
When you start, it asks if you would like to run build xip.bat.....just hit NO for that....
trojan reported in the attachment
Win32/TrojanDownloader.Zlob.NBP
false alarm?
well last night i finished my own wm6.1 build 20270 128dpi pdxib1 according to your guide i wanna tell what i did to complete it ;
1.i exctracted my rom using i780 kitchen and i got dump folder and i also added some extra tools like ervius buildos,osnbtool etc...then i used pkgbuildos to seperate folders into oem and sys
2. i used oem part from krizky82's kitchen and i add some extra packages using ervius package creator 2.7 and add them with oem_blahblah to oem folder.
3. i deleted windows live and msn messenger from sys folder and copied netcf 3.5 and flashlite v3.1 from krizky82 kitchen. i also used his initflash and rgu file coz i had same structure almost(oem totally same and sys programs also)
4.i looked at both efn's kitchen and krizky82 kitchen and i saw that they have this structure oem,sys and rom and in rom there is xip folder. when i looked at inside xip folder i saw that there is only coredll.dll folder and others are dsm rgu and boot files so my next step
5. i used osbn tool to exract xip.bin and after i got that xipkitchen_beta6 and i choosed the same donor and original and after extracting i got original xip files and i ordered in same structure like efn's kitchen
6.then i used pgkbuildos and let the process starti had some dsm duplicate errors and i delete duplicated ones and later i didnt start xip extract bat and flashable bin bat so after process again i had temp/dump folder
7. during buildos there wasnt any error and i was happy about it
8. using inputTXTFileMaker ( thanks to u dreamtheather93) i got input text and after that using these commands;
mgfsfromdump imgfs_raw_data.bin new_imgfs.bin
del imgfs_raw_data.bin
ren new_imgfs.bin imgfs_raw_data.bin
make_imgfs i780.nb0.payload.body -nosplit
merge i780.nb0.payload.header i780.nb0.payload.body i780.nb0.payload
nbmerge -data 2048 -extra 8 i780.nb0 -conservative
and conv3 input.txt > conv3_output.txt
ren i780.nb0.b000ff !!i780_flashable_bin.bin
i got my flashable bin file yupiiiii i controlled the size of flashable bin and it is 86.2 mb and the size of dump folder almost 125 mb i hope it is ok
now i will flash my phone but is there any possibility that my phone can be bricked ?
thanks a lot for ur guide again!!!
note: i already used i780.bin as 12mb page pool size i did it before kitchen using osbn tool
good job m8
You cant really brick your i780 because of this I've done way crazier stuff....like trying out omnia's xip, drivers of omnia on i780....and nothing's given way
However, i'm hoping you've ported your XIP accurately, and i'm unsure how've you've built your SYS folder.
but, go ahead and flash and see if it boots nothing to be paranoid if it doesnt boot/hangs at startup/throws an error and fails etc. etc. If any of this happens, then we could troubleshoot it together
cheers & good luck
Great job!
Nice start San!
Not even some days left from your first successful cooking and you already best gid on it!
Keep on do it. And we wait for new mods for our best touchphone!
I think now anyone is able to break Eagles wings =P
First of all I want to thank EFN for old style kitchen that I have been using for long, but time goes on and we need more optimization and kitchen thats also easy to use.
Big thank to Mr Barin, who made brilliant kitchen to make this not easy process fully automatic.
I780 kitchen v3 "matic". (WM6.1 /WM6.5)*
*includes latest 128dpi 6.5 build packages with "test" epix drivers and mouse fix. So if you just start and simply press "play" button it will create new rom
1. Download and install latest OSbuilder and !manual! from http://www.mobileunderground.info/showthread.php?t=12348
2. Unpack >Kitchen< to anyfolder.
3. When you ready to make bin run 1.Start_OSBuilder.osb config file. Settings are optimized and working. So any changes in Osbuilder settings can make new rom nonworking. If you want to play with settings safe files 1.Start_OSBuilder.osb and osbuilder.osb for future.
4. Press button "Play" to start cooking.
5. When Mirage pops up choise i780.new.bin for flashing.
Small guide: When you porting SYS folder, VM ,ROM and METADATA folders should remain original in SYS!Also keep folders FWUPDATE and SQM, those folders contains dummy files of windows update and bug reports.
ROM folder has our device xip (modified and lighted by me with WWE support) and rom template, do not change anything in this folder . For CHS ROMS replace xip.bin with xip that has appropriate WinCENLS.
DONOR folder-place there donor device xip (or packages from xip).
OEM folder actually does same as SYS but it contains additional software and device specific applications and drivers. SYS used for osporting, OEM normally remains same.
You will find "moduled" files in SYS folder, they looks like folder with file name.
While cooking in osbuilder you see modules relock process with green line process, be sure that free memory in slot 0 isnt going under 20 mb (ideal is 24-25 mb)! If its so stop kitchen and recmod some modules (convert them to files). This is because slot 0 is used for process memory and must be free for current operations. Nk(native kernel) of wm 6.5 has support of more memory for modules(it has extra new slot for modules )than in 6.1.Thats only main differ of 6.5 and 6.1. Our device is using nk 6.1. So when other slots becaming overfilled with modules then reloc is going to fill rest of modules to slot 0, that can make : some applications non working, battery will drain faster, may not boot. Only some modules must be in this slot (as desired in dsm of packeges with flag "L")
U can see slots map by opening "Map" after module reloc process during rom building, modules in top section are in slot 0.
So you need to reloc some modules to files to keep slot 0 not garbaged. Dissadvantage: making files from modules of course making their work slower. !Some modules, such shell32.exe, some drivers, after reloc to files !may not work!, so reloc modules that are not system related folders such as WinodwsLive, Widgets,BROWSING etc. Relocking of mui, dpi and other small modules doesnt make sense, so those you can leave them in modules.
During cooking, popup with PagePool size wil be up. I set it to 10 mb by default. But u can easy change this value to desired.
Pls read Osbuilder manual for cooking related questions.
Enjoy cooking!
Added recmod tool that converts whole folders with modules to folders with files and viseversa (thx to dreamtheater39)
Extra for kitchen!
SYS and OEM packages of 28205Hybrid 96dpi ROM http://www.mediafire.com/file/yynemmzngzm/ENGLISH28205hybrid.rar use with Donor xip http://www.mediafire.com/file/ndns2eq4n1uce22/xip.BIN
Good Effort buddy.. will test it.. do u have any plans like ervius visual kitchen for i780 ?..
Tested 1. Dump Bin
I am getting below error message in an indefinite loop
ERROR: Could not find pointer for ofs 802****
ironeagle said:
Tested 1. Dump Bin
I am getting below error message in an indefinite loop
ERROR: Could not find pointer for ofs 802****
Click to expand...
Click to collapse
you are dumping offical ROM or yours?
heineken78 said:
you are dumping offical ROM or yours?
Click to expand...
Click to collapse
my own rom
Dude, I dont know the way your kicthen is working and your bin's, anyway my old BIN's doesnt give errors on it.
But if you can pls try it with official BIN and to complete.
Thx.
posted new kitchen
I'm not sure if I will give it a wirl or not. I have so much other work to do and learning another kitchen is not really on my menu right now.
And Yes as Always big thanks to EFN, and IronEagle also who shared his kitchen in the past. I might just try one of your ROMS for a while. I have my hands full already.
Thanks for posting the kitchen.
bobsbbq said:
I'm not sure if I will give it a wirl or not. I have so much other work to do and learning another kitchen is not really on my menu right now.
And Yes as Always big thanks to EFN, and IronEagle also who shared his kitchen in the past. I might just try one of your ROMS for a while. I have my hands full already.
Thanks for posting the kitchen.
Click to expand...
Click to collapse
Old kitchen belongs to EFN, no progress was made after Krizsky. IE had posted his kitchen (same as EFN) when he stepped to new one to avoid concurrence Me used osnbtool for long time.
Now we have OsBuilder that does everything with .NB files for any WinMo device, only what you need is rom template or nb image of device. Sure you can use it also without to compete only imgfs. Btw is recommended for HTC devices.
hi, my friend, i modify your command: 2.Build bin from nb.bat, maybe it's show better now:
@echo off
path %path%;%cd%\tools\osnbtool;%cd%\tools\XIPport;%cd% \tools
echo ------------------------------------
echo Converting nb0 to nb
echo ------------------------------------
osnbtool -extra ROM.nb0
echo ------------------------------------
echo Making bin file from nb
echo ------------------------------------
osnbtool -2bin ROM.nb0.EXA 0x000C0C00 -cutheader
echo ------------------------------------
echo Merging header +bin to working flashable bin
echo ------------------------------------
copy /b/y i780.bin.Header+ROM.nb0.EXA.bin i780.new.bin
echo ------------------------------------
echo delete temp files
echo ------------------------------------
rd /s/q temp
del ROM.nb0
del ROM.nb0.EXA
del ROM.nb0.EXA.BIN
echo ------------------------------------
echo Press anykey to close this window
echo ------------------------------------
pause
Where is the ROM.nb0 file?
I have message:
ERROR - Can not open the source file.
Upd:
Never mind, it works fine
i'll try it , maybe i'll make a good rom !
Hello everyone,
here's the wm6.5 rom for asus p835.
last updated: 10-12-09
http://cid-cf1603cd2858a369.skydrive.live.com/browse.aspx/PUBLIC
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
btw, as usual, you use this rom at your own risk as you should understand there's always risk when flashing rom to your mobile... blah blah blah..
------------------------------------------------------------------------------------------------------------------------------------
[14-12-09]
I guess most of us p835 users have to use our own effort to build the rom for this phone.
Here i will give you some guide how I did building the ROM. Hopefully we can gather more intelligence to make a nicer ROM for this phone.
first off, I will explain how to properly extract xip/sys from the original ROM. With these only you can modify it's system.
Tools needed: p835abisplit2.exe, osnbtool.exe
1. rename the original ROM you downloaded from asus site. Rename to G5.exe. run command: "p835abisplit2 g5.exe". You will now get a file FLASH.BIN.
2. Now we need to work with FLASH.BIN. Using OSNBTOOL, put in command "osnbtool -sp flash.bin", you will get something just like below:
OS ROM Partition Tool V1.59 By Weisun :> PDAclan.com
Sector size : 0x00000800
Extra data bytes : 0x00000008
OS IMAGE found.
Partitions infomation:
**************************************
Part-0 type: BOOT SECTION image
Part-1 type: XIP RAM Image
Part-2 type: IMGFS file system
Part-3 type: legit DOS partition
**************************************
Found BIN_FILE structure in source file.
Records: 0x0000036D RecordsSize: 0x06E10328
StartAddr: 0x01030200 ---------------->we need this address when we repack flash.bin. Check if yours is the same with this?
flash.bin.Header written.
3. command: "osnbtool -sp flash.bin.BIN.NB0"
4. command: "osnbtool -d flash.bin.BIN.NB0.OS.NB 2 imgfs.bin" --> you'll get imgfs.bin
5. command: "osnbtool -d flash.bin.BIN.NB0.OS.NB 1 xip.bin" --> you'll get xip.bin
6. command: "imgfstodump imgfs.bin" --> with this, you'll get a "imgfs" folder. You'll need to make it into a easy to use package. rename the folder to dump.
7. command: "packagebuilder dump" --> you will see inside dump folder, you have all files packed into different folders. You wont be able to see a single file in dump folder. if you do, probably packagebuilder unable to recognize them or something wrong with the files(i'm not sure what to do then). The most important thing in dump folder are the folders with letters starting with OEMxxxx and .ROM, .VM. These few folders should be retained in the new system. Others are all replaced with new system.
assume you are able to modify everything without question, you are now in the situation where you want to repack a ROM. We will need these files in the same folder: FLASH.BIN.HEADER, flash.bin.BIN.NB0.OS.NB, IMGFS.BIN.
1. You will need to repack imgfs first. using "imgfsfromdump imgfs.bin imgfs-new.bin", you get the new imgfs-new.bin.
2. assuming you already modified xip.bin, it should be in name xip-new.bin. Using "osnbtool -c flash.bin.BIN.NB0.OS.NB 1 xip-new.bin"
3. "osnbtool -c flash.bin.BIN.NB0.OS.NB.NEW 2 imgfs-new.bin", repacking imgfs
4. "osnbtool -extra flash.bin.BIN.NB0.OS.NB.NEW.NEW"
5. "osnbtool -2bin flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA 0x01030200 -cutheader", remember when we first unpack FLASH.BIN? There's a starting address which we must use here.
6. "copy/b/y flash.bin.Header+flash.bin.BIN.NB0.OS.NB.NEW.NEW.EXA.BIN os-new.nb0"
7. "p835abisplit2 /B G5.EXE" ---> you must have the original ROM G5.exe. Output is a file named "out.exe". This is a USB flash file. For me, I'd prefer a card flashing ABI file. Which I felt safer. For generating ABI file, you will need to download a flashable ABI file, rename to G5.abi and run this command "p835abisplit2 /B G5.ABI". You will get "OUT.ABI". Rename to G5_ALL_WWE.ABI to flash with an SD card.
Btw, all these are not my original works, credits to DA_G for his ROMs and guides, BEPE and others for their great tools, zhaochengw: most of the guides above is from him.
--------------------------------------------------------------------------------------------------
[16-12-09]
SYS modification:
to upgrade a sys, all you need from original ROM is .ROM, .VM and all OEMxxxxx folders. (that's all i know of). All other folders are to be deleted and replaced with folders from new builds. After you work out a complete SYS, use G'reloc to relocate address. I've tried using WMreloc, but everytime i tried doesnt boot. I'm not sure what caused the problem but at least G'reloc worked. There might be some hiccups when using G'reloc, you'll have to google abit on that. If you encountered a problem saying that there's not enough memory on slot0, try remove some of the removable directories such as office or onenote.
Once you successfully relocated, you will have to use BuildOS to pack it back. You might encounter problems like duplicated files, just delete the one not from OEM folders. after you're done, copy the DUMP folder from TEMP directory and use imgfsfromdump(step1 from second part above).
--------------------------------------------------------------------------------------------------
[19-12-09]
I'm not going to cover xip.bin porting, but i'll mention here that you will need to use xipport to manually port xip for this rom. I've tried some kitchen tools but none working. It's the same for sys porting too, you have to manually replace the files and/or change REG. After which you'll use BUILDOS to build it. Other than that, you'll need an OEM sys/xip. I'ved used D_GA's 28002 and found that his package works pretty well. You can find it here.
http://forum.xda-developers.com/showthread.php?t=544445
I'll upload some related tools together so you'll wont have to look everywhere. You can find the upload together with the ROM downloads area.
regards.
blue.
Nice working!
Thx for blue's hard working on this poor handset.
wish ASUS can fix bugs on drivers and also hope guys like u can countinue Cooking better roms!
Thanks Guy! You're the best!
Call Key,Trackball and Volume Key cannot use
blue00mountain said:
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
Click to expand...
Click to collapse
I had this issue too. Make sure you recmod all the browsing folders, incl Browsing, Browsingie & Lang folders
Sorry, How to Flash the Rom Use ABI File?
Blade0rz said:
I had this issue too. Make sure you recmod all the browsing folders, incl Browsing, Browsingie & Lang folders
Click to expand...
Click to collapse
i'm a beginner chef, so please tell me what's the purpose of recmod? For my understanding, it is only to make files become module? what else does it do?
blue00mountain said:
i'm a beginner chef, so please tell me what's the purpose of recmod? For my understanding, it is only to make files become module? what else does it do?
Click to expand...
Click to collapse
As I understand it, not only does it make a module into a file, it makes that file use the memory available in SLOT 0 in the ROM. Modules use SLOT 1 memory be default, so I think the browsing folders have issues accessing memory across the two slots
Have a read at Da_G's thread & the Native Kernel post - he explains it a lot better than I do
Good job on the ROM!
Blade0rz said:
As I understand it, not only does it make a module into a file, it makes that file use the memory available in SLOT 0 in the ROM. Modules use SLOT 1 memory be default, so I think the browsing folders have issues accessing memory across the two slots
Have a read at Da_G's thread & the Native Kernel post - he explains it a lot better than I do
Good job on the ROM!
Click to expand...
Click to collapse
ok, now the browser problem and garmin problem solved. although not really sure what i did that made it worked. Now i'm facing another problem, asus utilities, i.e. autorotate can only work once, and then it stoped working the next time ie starts. Autocleaner does not work at all. Any ideas?
Is there anyone testing my rom anyway?
regards,
B
I have test your ROM.It is very good.Sometimes any programs can be down.
Hi Blue00mountain
Thanks for your hard work, downloading.... hunger for P835 rom,
Read form other thread and noted that WM6.5.3 build 28002 was not as stable and fast as 28003 or later, would you consider to move on to newer version, thanks so much in advance.
blue00mountain said:
Hello everyone,
here's the wm6.5 rom for asus p835.
last updated: 10-12-09
http://cid-cf1603cd2858a369.skydrive.live.com/browse.aspx/PUBLIC
So far tested everything ok except Garmin XT not working anymore. Cant even start the application. Please let me know if you find otherwise.
btw, as usual, you use this rom at your own risk as you should understand there's always risk when flashing rom to your mobile... blah blah blah..
regards.
blue.
Click to expand...
Click to collapse
Thanks, that's great. BTW, I am start reading about porting XIP, would you mind telling me how to port XIP and how to test the ROM before hardware flashing the ROM?
leofong2022 said:
Thanks, that's great. BTW, I am start reading about porting XIP, would you mind telling me how to port XIP and how to test the ROM before hardware flashing the ROM?
Click to expand...
Click to collapse
There's quite some information on the web regarding xip porting. I felt that XIP is quite straight forward, not much problem. The problem I felt so far lies in SYS porting, and a chance to get a good OEM unmodified rom.
And there isnt any emulator to test rom. YOU WILL NEED TO FLASH INTO PHONE TO TRY IT OUT. However, this phone has a nice bootloader, which it checks for rom integrity before flashing. if you rom is incorrect, it doesnt allow to flash at all. Basically it is quite safe unless you messed something other than xip sys itself.
Thx blue!
anyway,the solution of unpack and repack P835 ROM may have another way:
follow steps are from hdubli,and hope can help everyone to Cooking ROMs!
---------------------------------------------
@ECHO off
ECHO Preparation
del flash.bin
del os-new.nb0
del flash.bin.bin.nb0.bin
del G5_ALL_WWE.abi
pause
TOOLS\p835abisplit2 g5.abi
ren os.nb0 flash.bin
TOOLS\osnbtool -sp flash.bin
TOOLS\nbsplit -data 2048 -extra 8 flash.bin.bin.nb0
copy flash.bin.bin.nb0.payload ROM\flash.bin.bin.nb0.payload
pause
ECHO Building OS
pause
TOOLS\BuildOS.exe
ECHO Realocating Modules
pause
TOOLS\WMReloc -gtemp\dump -llog.txt
ECHO Next: Build the rom...
pause
copy imgfs.bin temp\imgfs.bin
cd temp
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
cd..
copy temp\imgfs-new.bin
pause
TOOLS\insert -i imgfs-new.bin -o flash.bin.bin.nb0.payload -d 0x00460000 -s 0x5fdfff0
pause
TOOLS\insert -i 21812.bin -o flash.bin.bin.nb0.payload -d 0x00180000
pause
TOOLS\nbmerge -data 2048 -extra 8 flash.bin.bin.nb0 -conservative
pause
TOOLS\osnbtool -2bin flash.bin.bin.nb0 0x1030200 -cutheader
pause
copy /b/y flash.bin.header+flash.bin.bin.nb0.bin os-new.nb0
pause
TOOLS\cvrtbin os-new.nb0
ECHO Check the Out Put
pause
TOOLS\p835abisplit2 /b g5.abi
ren out.abi G5_ALL_WWE.abi
pause
del flash.bin.bin.nb0
del flash.bin.bin.nb0.payload
del flash.bin.header
del flash.bin.bin.nb0.extra
del imgfs-new.bin
pause
---------------------------------
Hi Blue,
Thanks for your details cooking step, I've done all the way to the dump folder, and after repack the dump folder using packagebuilder, I got a "info.txt" file and a "sys" folder, I leave everything untouch and try to repack imgfs, however I always get error as below after runing the command imgfsfromdump:
>imgfsfromdump imgfs.bin imgfs-new.bin
ImgfsFromDump 2.1rc2
Using compression type 'XPR'!
Sector size is 0x800
Processing "info.txt" as file
Processing "SYS" as module
then error message pop up "ImgfsFromDump.exe has stopped working"
Have you ever got this error? Did I missing something here, please help, thanks.
lizard999 said:
Hi Blue,
Thanks for your details cooking step, I've done all the way to the dump folder, and after repack the dump folder using packagebuilder, I got a "info.txt" file and a "sys" folder, I leave everything untouch and try to repack imgfs, however I always get error as below after runing the command imgfsfromdump:
>imgfsfromdump imgfs.bin imgfs-new.bin
ImgfsFromDump 2.1rc2
Using compression type 'XPR'!
Sector size is 0x800
Processing "info.txt" as file
Processing "SYS" as module
then error message pop up "ImgfsFromDump.exe has stopped working"
Have you ever got this error? Did I missing something here, please help, thanks.
Click to expand...
Click to collapse
i found there's some problems when u use the imgfsfromdump tool to make imgfs-new.bin
imgfsfromdump can't proceed the SYS folder,it can only deal with original "DUMP" folder
that means,when u dumped out the "DUMP" folder and use pkgtool(or packagebuilder) proceed it into models(SYS、OEM...ETC),u have to use BuildOS.exe rebuild all the files in SYS OEM.the result of BuildOS's rebuild just like the original "DUMP" folder.then u can use imgfsfromdump to make a imgfs-new.bin
Sorry about my poor English...
well,i still try to show u the way i repack imgfs.bin wihtout change anything.
1st, get the imgfs.bin
2nd,use imgfstodump and get the "dump" folder
3rd,use imgfsfromdmp directly,i get the imgfs-new.bin
blue00mountain said:
There's quite some information on the web regarding xip porting. I felt that XIP is quite straight forward, not much problem. The problem I felt so far lies in SYS porting, and a chance to get a good OEM unmodified rom.
And there isnt any emulator to test rom. YOU WILL NEED TO FLASH INTO PHONE TO TRY IT OUT. However, this phone has a nice bootloader, which it checks for rom integrity before flashing. if you rom is incorrect, it doesnt allow to flash at all. Basically it is quite safe unless you messed something other than xip sys itself.
Click to expand...
Click to collapse
ic, but i find that the xip size should be ~3200kb, is it just omit it during compling the xip?
In addition, do you mean it is just simply that just using Da_G's build with Da_G's MSXIPKernel + initflashfiles.dat and original P835 OEMXIPKERNEL is ok?
Sorry for my question because I know less on the OS complie, thanks
leofong2022 said:
ic, but i find that the xip size should be ~3200kb, is it just omit it during compling the xip?
In addition, do you mean it is just simply that just using Da_G's build with Da_G's MSXIPKernel + initflashfiles.dat and original P835 OEMXIPKERNEL is ok?
Sorry for my question because I know less on the OS complie, thanks
Click to expand...
Click to collapse
i don't think the XIP size should be 3200kb,anyway,in the Traditional Chinese version Rom,the size of XIP is more than 4200kb.
based on my experience, you dont need to have an exact same size for xip.bin. not sure if it will cause any problem but It will start anyway.
regarding your repacking dump question, the proper sequence i think is:
imgfstodump-->packagebuilder-->greloc-->buildos-->imgfsfromdump = imgfs-new.bin
blue00mountain said:
based on my experience, you dont need to have an exact same size for xip.bin. not sure if it will cause any problem but It will start anyway.
regarding your repacking dump question, the proper sequence i think is:
imgfstodump-->packagebuilder-->greloc-->buildos-->imgfsfromdump = imgfs-new.bin
Click to expand...
Click to collapse
Since I saw the p835abisplit2 creator starkwong said that (若要修改 XIP，請確保重新嵌入 nb0 前的 XIP 大小是跟原來的相同，否則刷機後會開機失敗)
-> if modifying XIP, please ensure the re-embedding nb0 XIP size is same as original XIP size, otherwise it may cause turn-on (mobile) failure after flashing.
If it is ok, that's great