Develop Bugs

A way to open 'tadzio' roms in Rom Koch?

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.

Custom Smartphone ROMS

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

Samsung i780 kitchen - release 0.2 BETA (New Version!)

PLEASE NOTICE THAT THIS KITCHEN IS A VERY EARLY BETA AS IT HAS NOT BEEN DEEPLY TESTED
*** USE IT AT YOUR OWN RISK! I ASSUME NO RESPONSIBILITY! ***
Hi guys,
after many days of testing I'm releasing my kitchen for i780.
It is very basic: no gui, only batch Windows scripts.
What you can do with this kitchen:
A) Convert your Part02.raw dumped rom to bin flashable PDA rom
B) Create a dump folder to cook your own rom and recreate a bin flashable PDA file.
Please notice that there's no tool included to edit, add or delete modules and files from rom dump.
You must use one of the tools available here in forum to do this or do this by hand.
Donwload the zip file and extract everything.
READ CAREFULLY THE README FILE IN THE ZIP ARCHIVE
This file explains how the procedures work and what you need.
PLEASE TEST THIS KITCHEN AND REPORT YOUR RESULTS
I thank chaimd for his bintonb0 tool, tadzio for his tools and Juggler for conv3 sourcecode.
I also thank Topogigi for his original procedure.
I modified conv3 tool to make it work with i780 rom files and made split and merge tools.
If you want to try this kitchen, I thank you!
[FONT=&quot]If any guru in the forum wants to make a gui for this kitchen or insert tools for module, file and registry editing (like the ones you can find in other kitchens), it would be appreciated.[/FONT]
Issue 1: it seems there's a problem with Part02.raw conversion. It screws up connection settings. Problem is being investigated.
[Partial solution]: it seems that this problem is due to both size and language: I used an English rom to convert an Italian Part02.raw.
Using an Italian rom seems to solve the problem. But you must check the new rom size: if it's too big it gets cut down and it doesn't work.
Version 0.2: this version contains a new conv3 release. This release it's a little bit more complicated than the previous one but it supports a wider variety of rom images and guarantees correct conversions. Previous release could lead to incorrect roms so you should consider it as deprecated.
For Issue 1, limitations are still the same: you should use a rom of the same language of the dump and mind the result size

this is just great

great job
great effort for the great device.
I will try for sure, thanks a lot

Recreate???
At first thanks for the kitchen!!!
But I got one question... How can I rebuild the dump folder and what files are needed in the kitchen directory to recreate???
Do I just have to start RecreateBin.bat and it uses the files from the dump-directory???
THANKS!!

mievalt said:
At first thanks for the kitchen!!!
But I got one question... How can I rebuild the dump folder and what files are needed in the kitchen directory to recreate???
Do I just have to start RecreateBin.bat and it uses the files from the dump-directory???
THANKS!!
Click to expand...
Click to collapse
You must read the PDF file in the kitchen directory. Some parameters may change according to the ROME used

Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze

vibranze said:
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
Click to expand...
Click to collapse
you need flashable pda part file for convert,
like XHD1 pda file (you can find in this forum).

vibranze said:
Hi Famusc,
Great Kitchen!
I have some questions before I can try your kitchen.
In the PDF you mentioned, an existing bin PDA ROM, what do you mean by that and how to get it? I have E1 ROM .raw files with me but not the .bin file.
Cheers,
Vibranze
Click to expand...
Click to collapse
Hi,
Existing bin file will be used as a model ton convert your raw file. Famusc said that the bin file must be the largest possible. So far, we use the D1 bin file. The probleme is E1 raw file part is larger than D1 bin file.
There may also have concerns related to the language of ROM file. I try to cook a French raw file with an UK D1 rom, and the result is a broken ROM

Hi Eunjea & Webise,
Thanks for the explanation.
My current stock ROM is D1 and how to convert it to .bin format if I want to use mine?
Actually I always use English ROM and replace the wince.nls and add some fonts to support Chinese reading
Btw, how do I know what is the value for first jump, footer start and footer checksum address? In the PDF, the first jump address is on 444400 and in my bintonb0.txt I also have 444400, can I follow the same address?
Cheers,
Vibranze
webise said:
Hi,
Existing bin file will be used as a model ton convert your raw file. Famusc said that the bin file must be the largest possible. So far, we use the D1 bin file. The probleme is E1 raw file part is larger than D1 bin file.
There may also have concerns related to the language of ROM file. I try to cook a French raw file with an UK D1 rom, and the result is a broken ROM
Click to expand...
Click to collapse

I just want to backup my ROM which is built by my operator so that if I have problems with the upgrade I can always go back to my original ROM.
How can I create the bin files for te part 1 and 3?

Can anyone advise, as there is no bin file for the Omnia this kitchen will not be compatible, right? Or is there a way to create one?

I managed to dump an Dutch rom, version E1.. Could you explain how I can make a flashable image for the complete rom and/or how to make a radio rom from the three parts I dumped?
Furthermore, i have had some issues when I dumped the rom with the instructions that were in the readme.pdf.
There are some connection problems, that the originally phone doesnt have..when I flashed my rom, there werent any connection settings visible. e.g. settings > connections > connections > advanced > select networks, here was nothing visible.
It seems a bit like the same problem that people had with the english dumped E1 rom. Is there a chance that certain files from the raw files werent correctly put in the i780_flashable.bin (final product) ?

Is this the latest version of famusc's kitchen?

[PRJ]Start Kit. Kitchen. Based at official stable release (479.3WWE). UC Ready.

Just start kit. For further cooking.
Based at official release (and stable, I hope,- don't like to be beta-tester for HTC "in the dark").
It's new way for me (just began to use WinMob by Diamond), so don't bite me too much
Don't forget about Hard-SPL!
Few cosmetic changes & a little tweaked. UC ready.
In OEM left TouchFlo only.
In SYS out: OneNote, PowerPoint, WindowsLive, Help & other rubbish.
In "Install" folder - example only. You can change it to your own provider (look to OEM\CONNECTIONSETUPDB - password I found at XDA) or just use ConnectionSetup.
The most tweaks - in OEM\xxxconfig
Be careful to finish.xml - it's important file!
(return to "Internal Storage". Manila start including in this file too. You can customise it up to you. Same as *.rgu in this folder)
To find the bugs&errors better together, I think
Ideas&remarks - welcome!
It's OPEN PROJECT.
Kitchen: http://rapidshare.com/files/143594363/WWE_1.93.479.3_kitchen.zip
Example ROM (with pass for provision.zip):
http://rapidshare.com/files/143600258/1.93.19965.Light.rar
For make the same - just press !COOK.CMD in the kitchen.
Lighted packages:
http://rapidshare.com/files/144298572/PACKAGE_Diamond_PhoneCanvas.RAR
http://rapidshare.com/files/144138802/PACKAGE_Diamond_QuickGPS.RAR
The trick - in change heavy bmp files to compressed/indexed png.
And patched dll/exe, for use another files.
Not sure about using system resources in this way - up to you. Try.
Changes: http://rapidshare.com/files/144298443/changes_to_kitchen.rar
(Corrected ROM container: 19965 now. Was 20273 - just mistake. And help engine)

can I just install your rom on my Diamond?
Would like to try it, but dont want to fool around with the Kichen stuff

Been reading much on cooking the last days. This looks like a good start!
Thanks for sharing. Hope I can create my own Diamond ROM from here. If it's good enough for some of my friends I will share it on XDA as well

teddyen66 said:
can I just install your rom on my Diamond?
Click to expand...
Click to collapse
Not see the reason - only base functions.

You are right, but it's the fastest ROM I've ever tried
But like you said, it's very basic. Camera is not working, so you need to add all these yourself.
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
update: You might even remove the Office part from the light ROM??

mccune said:
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
Click to expand...
Click to collapse
Hm. "Top" level - zip. Inside - rar. Going to try download back. May be corrupted...
No, everything OK to archive.
I use rar v.3.71
mccune said:
You might even remove the Office part from the light ROM??
Click to expand...
Click to collapse
Word & Excel till alive

mccune said:
You are right, but it's the fastest ROM I've ever tried
Now watching the kitchen files.. .."WinRAR gives the following message: Invalid or corrupt authenticity information"
It does seem to extract just normal. Is the RAR file save?
Click to expand...
Click to collapse
Its 7-Zip i think extracts ok

I will give this a try, other kitchens didn't work out for me very well.
Thanks man ...

Help system
I think idea to remove the help system absolutely is not the best.
Sometimes apps need it for normal work. May keep help engine alive?
Any opinions?

Please tell me one usefull hint that's provided to you because of the Help function?
For me it's wasted space on every device I've owned. If I encounter any problem they go beyond the help files

Looks pretty complicated with no real guide, will look into other kitchens!

I talk about engine (hwhelp) only. The most help files - "dead cargo", of course.
After try to push "help" button at some apps - error, could make system unstable.
P.S. made two "light" packages. ( see in the first post).
It use a little less memory, I hope.

Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!

sev7en said:
Congratulations for this new project! If you need any help about a multilanguage (Italian) version... I'm ready!
Click to expand...
Click to collapse
Thanks for support
I think, change the locale - it's only change the *.mui & may be other files in folders *_0409. Change to Italian locale - _0***, don't know exactly.
Could you try it?

Found the mistake - "alien" rom container (from 20273) in the kitchen.
Just accident.
May be it's nothing, but...
- in the first post + hwhelp.exe: changes_to_kitchen.rar

Tricks
Stop unused services (functional don't loose) - will start on demand:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BthAsPlugin]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\BTHIDSVC]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\OBEX]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\QuickGPS]
"Flags"=dword:00000004
[HKEY_LOCAL_MACHINE\Services\WirelessService]
"Flags"=dword:00000004
It's THE SAMPLE. (but I use it)
May stop any more? Biotouch, for example?
------------------------------------------------------------------------
Start HTCVolumeControl.dll without taskmanager, or if you use another TM:
[-HKEY_CURRENT_USER\Software\HTC\BootLauncher\Services\HTCVOLUME]
[HKEY_LOCAL_MACHINE\Services\HTCVOLUME]
"Dll"="HTCVolumeControl.dll"
"Order"=dword:0000000c
"Index"=dword:00000000
"Info"=dword:00000000
"Prefix"="VOL"
Tested on Raphael VolumeControl
------------------------------------------------------------------------

Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!

GriFolle said:
Somebody can explain how to (EXACTLY! step by step) change OS, XIP, SYS in this kitchen? I've read a lot of tutorial but I didn't understand how...
In example, I've got:
1) this kitchen and this "base" rom
Click to expand...
Click to collapse
You don't neet "base" rom (or what you mean?) it's example only.
If you talk about rom\os.nb in the kitchen - it's just container for rom, which is empty.
GriFolle said:
2) another diamond rom with 20748 xip build.
If I would to update OS, XIP and SYS to newer, what I have to do?!
Click to expand...
Click to collapse
Just delete oem, rom, sys & make you own "tree"

Thanks for your very QUICK reply Modilv!
So, I have just to take the parts of (maybe more) diamond romS that I need (including OS.nb??) and put theme in your kitchen..?
So simple?!
PS: no "porting" xip or something like that?
TIA

It't not "my" kitchen (just add bepe's utility to final step)
I made the "tree" only.
You can do the same.

New Asus/Garmin Asus abi ROM tool for full ROM customization!

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