Related
The Rom Koch at the moment does not support .nb files that have been created with tadzio's ImgFsTools as of now.
I've been wondering if we can perform the following steps to rebuild the .nb file using mamaich's old ImgFsTools.
If we can repack the dump into a rom that still has the 8Mb space in it, it should be possible for Rom Koch to open the file without problems. We can, after modifying that rom, repack it with the new ImgFsTools to shrink the files again.
I have been trying a couple of ways to do this, but run into some problems along the way. I've been digging in the forums to find out what I'm missing here, but can't seem to figure it out. I might be doing something totally obsolete here, but I've seem numerous posts of people trying to customize one of the precooked rom's with the Rom Koch, and didn't get anywhere.
First Try: Just unpack the .nb and repack.
Using the old ImgFsTools, I immediately get errors that there are invalid headers in the file doing the prepare command.
Second Try: First use NbSplit, then unpack and repack the payload.
This one neatly packs the payload again using the old toolkit, but after NbMerge on the files, the file is still small. So apparently it's not just the image file that has lost some size, because that is packed using the old tools, and should include the 8Mb free space. Seems like I'm mixing things up here, so have to try this another way.
Third Try: Same as above, but when repacking, use a different template.
I follow the steps that give me a smaller .nb file from the second try, but when repacking, I provide a both the old and new toolkit a template file of a fixed size rom. This packs the smaller rom data in a 67 Mb .nb file, so looks promising. Rom Koch still throws a DivideByZeroException though, so while I got (my test rom) the Black V2.0 rom in a 67Mb .nb file, that's not the problem.
Am I trying something remotely possible here, or should we just wait for an updated version of the Rom Koch to customize the precooked roms? Obviously, the new ImgFsTools do a lot more than just creating a smaller .bin file.
wait for koch v2.
It can be done and I've done it before using Jasjamming method.
Steps:
1. Prepare a good untouched version of any WM6 rom version ( No free space tweak by Tadzio's Toolchain) - Will be used as shell rom
2. Dump the WM Black 2.0 rom using Tadzio's toolchain only ---> Dump folder will be created: Do not delete
3. Use aWaiter and make imgfs_raw from the rom taken from no. 1 : Do not delete
4. Use normal imgfs tools to compile the dump directory using the imgfs_raw from no. 3 (Shell)
5. Make a new .nb file with the size of 67.7 MB.
actually guys... it's simple.
take an NB, split it into the dev data and the payload.
take the payload, and dump it... play with it, whatever, but remember to re-merge after you're done.
Olipro said:
actually guys... it's simple.
take an NB, split it into the dev data and the payload.
take the payload, and dump it... play with it, whatever, but remember to re-merge after you're done.
Click to expand...
Click to collapse
Sounds great, but I am waiting for Koch 2 that is even easier
Thanks guys, I guess I've been thinking too hard on this one.
Just wanted to try this to conveniently experiment with the precooked roms, but I guess convenient is when Rom Koch is upgraded...
I'll give the above suggestions a shot.
Hi everybody,
I would like to cook Artermis rom for my own Dopod P800W. How can I do this and what about the tools for rom modification? Please suggest me and put the link for download.
Thank you very much.
Everything you need is here:
http://forum.xda-developers.com/showthread.php?t=310076
The steps that I am using
1. Select the ROM that you want that has nbh extenstion
2. use nbhtool to extract the .nbh rom to nb files. Remane the os.nb to RUU_signed.nb
3. use the above link to get the tool to extract the RUU_signed.nb. This tool will extract all files in the rom and put them in folders--->There is a word doc in there that tells you what to do. It is a bit cumbersome but just follow it you will be fine.
4. in Sys folder, remove or add the folder you want--becareful here because there are folder interdpendent to each other so make sure you know what to add or delete.
5. use the Core tool again to build the new os.nb file. Make sure you follow the procedure in the work doc...
6. To build the nbh rom to load back to your device you will need htcrt tools. Copy the new os.nb and other nb files to the htcrt folder--this is what I do. Then run the htcrt program to build the new nbh romfile.
I hope the above will help you. I am building my own rom currently by using some component from B&Bv3.7 and the official wm6 v3.7 as the touchflow ROM. I have been playing with the above tools for sometimes now but still do not know what exactly what is required in each folder yet. Hard but fun...hihi.
attached...nbhtools and htcrt...just to save you sometimes. The core kitchen is in the above link. All programs run in DOS mode, BTW.
Thank you very much, I will try to use it for my rom cooking.
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
I made a tool p835abisplit2 previously for ROM rebuilding, however that tool only fully works for P565 and earlier devices, which has many limitations for P835 and newer devices. So now I rewrite it to have full functions!
Applicable Devices:
- Asus P835
- Garmin Asus M20, M10
Usage:
- Decompiling ROM
1. p835abisplit3 <abi/exe file>
2. If input is an exe file, then a decrypted abi file will be extracted, which can be used with the Asus internal flash tool (Not available here)
3. 13 files are extracted, content on each file is explained in their file names
3.1 txt file is the partition definition, you can customize the abi by editing this file
3.2 OS file is in B000FF format. Use osnbtool -sp twice to get a correct nb file
3.3 EXTROM is a standard FAT Image, you can open and modify directly with WinImage
- Rebuilding ROM
1. Modify txt file as you need (Optional)
2. Rename updated file to their original names
2.1 For building OS file, use osnbtool -extra os.nb 0x8 and osnbtool -2bin -CutHeader
3. p835abisplit3 /b <abi/exe file>
4. out.abi is created, which can be used with the Asus internal flash tool (Not available here)
5. If input file is an exe file, out.enc (Encrypted abi) and out.exe (Flash utility with updated ROM and region patch)
- Warning
1. This tool now is too powerful that you can easily brick your device if you modify the txt file incorrectly, so take care! (However it is proved to work by hdubli)
2. This tool is checked to create identical abi file if you rebuild without touching anything. If this is not the case with your base ROM, don't continue cooking and let me know!
** Please note that if you modify the partition layout, the length of text must be < 24 bytes **
If this post is left too long without updates, you can check new versions at http://www.studiokuma.com/tools/?section=misc-e
Great job, man!
If you can update the tool for extracting the Acer ROMs that can be used for extracting NeoTouch S200's ROMs of version 3.xxx, that'll be excellent!!!
aa125690 said:
Great job, man!
If you can update the tool for extracting the Acer ROMs that can be used for extracting NeoTouch S200's ROMs of version 3.xxx, that'll be excellent!!!
Click to expand...
Click to collapse
See here:
http://forum.xda-developers.com/showthread.php?t=631207
EXTROM from P835
Great tool, but there is still one backlog. As tool still cant directly extract extrom resp.ASUS_ROM from P835 (its working pretty well with M10,M20,P565). Even at the end is extrom located in os.nb0. After such impementation it will be perfect tool
No, don't trust the tools reports the FATFS at last partition of os.nb0. It is a dummy partition in all new ROMs from any vendor.
As I can tell from the G5 abi, there is no extrom in it.
EXTROM from P835
You are partially right as HKEY_LOCAL_MACHINE\System\StorageManager\Profiles doesnt contains any usual ext partition.
But how you explain that standard EXTROM files are parts of OS.NB0 ?
Isnt so usual that those EXT files are part of main image. These are typical extrom file, see what I extracted :
P835 is bit specific, as not contains just dummy file for extrom package.
And one more question regarding P835, as you probably know there is problem with relatively small ROM space.
Even I removed lot of crap files, ROM image is still showing same size. Pdocread is showing total 200MB on DSK1.
But available is only 97.18MB.
Anyone cooking for the M10?
Works on M20 Rom Thai version.
Also, where can I find Asus internal flash tool?
efe
asus m20 cook rom
Thanks for your good tool, I am now cooking a rom of asus m20 and I have been successed to work out a file called "flash.bin" final, would you please tell me how to do to make it change to say "m20.exe". Or do you have any suggestion eg. use bootloader. Thank you very much. I really need your help.
Firstly, your ROM needs to be extracted by a exe file instead of abi file first.
When you need to build exe file, use the /b switch.
Extract: p835abisplit3 xyz.exe
Build: p835abisplit3 /b xyz.exe
Then out.exe will be the new flash utility with your changes and region lock patched.
starkwong said:
Firstly, your ROM needs to be extracted by a exe file instead of abi file first.
When you need to build exe file, use the /b switch.
Extract: p835abisplit3 xyz.exe
Build: p835abisplit3 /b xyz.exe
Then out.exe will be the new flash utility with your changes and region lock patched.
Click to expand...
Click to collapse
Thanks for your answer, I still meet problem even I use your method, so let me give more detail as follow:
1. I have split the xyz.exe with your tool and a xyz.abi and 13 more files extracted.
2. And I also use some kitchen to make a new rom file called flash.bin.
3. I rename "flash.bin" to "Os.bin" (one of the 13 files)
4. Lastly, I follow your instruction to build ie. p835abispilt3 /b xyz.exe, a out.abi will come out
So, how should I do to change this "flash.bin" to become the xyz.exe for flashing. Your help should be most appreiate. Thanks
my asus m20 device is bricked, any idea? Please help
Jtag
Does anyone have experience with jtag on P835 ?
Or is there any other way how to recover dead bootloader on MSM Asus devices ?
i can't open p835abisplit3.exe
how can i open
M930
Hi Stark Wong,
please could you modify p835abisplit3.exe in order to correctly work with M930 ?
See error message :
I have updated the tool to support longer string, that should fix your issue.
Download it in first post.
To others: You must have the original EXE to form output exe. Just pass the EXE when building, it will read the new ABI and generate a new EXE file. You can't generate EXE when you only get the ABI file.
Thanks
Thanks a lot for fix.
Note that even you will incorretly use this tool, nearly always is way how to recover.
See : http://forum.xda-developers.com/showthread.php?t=722951
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.