Hi Dev's!
after finding out how to create my own rom I will explain the progress for everyone.
[1st step - rebuild nbh with parts from different original roms]
At first of all make sure you have RSPL/HSPL installed before you try to create/flash your rom
Download a original rom for your device to start-up
Extract the contens of the *.exe and copy the RUU_signed.nbh to a directory you like (working direktory were you can collect all tools, data during our costumation process)
use nbhTool to extract the *.nb parts from the RUU_singed.nbh
e.g.
Code:
nbhtool.exe -split RUU_signed.nbh Schubert.txt
A textfile file for nbhTool is generated modify it forthe contens you like to rebuild afterwards (e.g radio or os) ==> see attachment for a demo txt file)
rebuild a RUU_unsigned.nbh with nbhTool
e.g.
Code:
nbhtool.exe Schubert.txt
and flash it with an RUU (maybe use a costum RUU for task 29 or 00)
finish
[2nd step modify registry ==> DeveloperUnlock]
Tested official Schubert rom's Nodo & Mango (Europe & Asia)
open htcrie_0.7.0.35 and open os.nb (Version includet in WP7 Costum Rom Manual Kitchen)
do not use other versions of htcRIE (e.g. htcRIE_0.7.0.46) cause there is a huge difference when inserting IMGFS into os.nb
click on IMGFS on the left side and click Image => Save Files...
IMGFS.bin should be saved at the location of your choice
use XiDump to extract the contens of IMGFS.bin
Code:
xidump.exe imgfs.bin
The contens should be extracted in the folder IMGFS
go into this folder and copy default.hv to a save place for modifications (thats a hidden file!!)
Drag&Drop default.hv over HVEdit.exe
now a new file is created called default.hvm
delete the default.vh to prevent convusion
edit default.hvm with a text editor
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg]
"PortalUrlProd"=""
"PortalUrlInt"=""
create Key wich doesn't exists at the moment
Code:
[HKEY_LOCAL_MACHINE\Comm\Security\LVMod]
"DeveloperUnlockState"=dword:1
you can also check/add the key for maximum unsigned apps
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\DeviceReg\Install]
"MaxUnsignedApp"=dword:7fffffff
save the file and drag&drop defaul.hvm over HVEdit.exe
a new default.hv is created wich contains you modifications
copy default.hv into the IMGFS folder wich was created before
In addition to that you can copy the CustClear.provxml into the root of the IMGFS folder
make sure it is hidden & write protected
the CustClear will be directly in the Windows folder after flashing
so no need to copy CustClear from Ringtones to Windows to unlock the phone after an update via Zune
Click to expand...
Click to collapse
rename IMGFS folder to "dump"
now rebuild imgfs with ImgFromDump
Code:
ImgfsFromDump.exe IMGFS.bin IMGFS-rebuild.bin
copy IMGFS-rebuild.bin to a save folder & rename it to IMGFS.bin
go to htcRIE-0.7.0.35) and implant IMGFS with following shell comando
Code:
htcrie.exe replace /I imgfs.bin os.nb
next open os.nb with a hex editor and search for following HEX-String
Code:
C7 14 02 80 01 04 00
rewrite the next 4 HEX-Numbers with
Code:
5D D6
save the file
finished
For information the hex code wich is generated from htcRIE compared with the original os.nb hex code.
If you search for differences in this two bin files this was the first one of 14 differences.
Don't know why the others are different but work
for NoDo
Code:
| htcRIE_0.7.0.35 | Original
012C72E8 | C7 14 02 80 01 04 00 8B | 012C72E8 | C7 14 02 80 01 04 00 5D |
012C72F0 | FE FF FF C0 20 00 00 FF | 012C72F0 | D6 FF FF C0 20 00 00 FF |
for Mango
Code:
| htcRIE_0.7.0.35 | Original
01106830 | C7 14 02 80 01 04 00 8B | 01106830 | C7 14 02 80 01 04 00 5D |
01106838 | FE FF FF C0 20 00 00 FF | 01106838 | D6 FF FF C0 20 00 00 FF |
[3rd step get ready for cab updates/customation]
Use DefaultCerts.dat & MSDefaultCerts.dat (from XBmod-Yuki's HD2 Rom) in your IMGFS to be ready for costum cab updates
[4th step adding OEM apps]
simply copy & overright the files from IMGFS Partition with the *.xap's, *.xml's,...
thanks to itje for mentioned that
thx to itje for the instruction how to dump IMGFS-Contens from OMEGA/ETERNITY roms
itje said:
dump ruu:
Code:
nbhTool -split ruu_signed.nbh Schubert.txt
dump os.nb:
Code:
xidump -b os.nb
Click to expand...
Click to collapse
[5th step adding additional languages]
thx to itje for extracting/preparing language packs from ETERNITY rom
Just copy & replace in IMGFS
Languages-Files
[6th step change wallpaper]
thx to -WP7User- to explain the necesarry steps for changing the wallpaper
Copy the pictures you like to have in your rom into IMGFS
add or modify values in default.hv
don't forget the comma if there is more than one wallpaper!!
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\WallpaperSets]
for changing the defauft lookscreen wallpaper look into user.hv and change
Code:
[HKEY_CURRENT_USER\Software\Microsoft\Photos\LockScreen]
XSPL
XSPL posted by Cotulla
Tools
nbhTool posted by ted973
Htcrie posted by Heathcliff74
NbhImageTool posted by DaG
XiDump posted by bepe
ImgfsfromDump posted by airextreme (v2.4.0 won't work for me)
HvEdit posted by ceesheim
Kitchen
WP7 Costum Rom Manual Kitchen posted by xda2_haseeb (instruction for IMGFS editing)
WP7build posted by tslany (only for information)
Registry Keys
Cab Updater
Omega OEM apps
FYI
The attached text file contains all nb entries to rebuild the whole rom expect the spl
You only need the line for radio.nb or os.nb, the rest could be deleted if you do not need them
flash devices only if you know what you are doing, i take no responsible for any damage
thx to itje for creating a nbhMerge textfile for HTC Trophy
where are all the rom coockers?
Are Ansar & DFT the only one who knows how to make a flashable rom?
Maybe we can use this thead to collect our testing progress
- what do we have tested (also to see wait leads in an corrupt *.nbh)
I think you meant "cookers" lol. I don't think there are any "publicly" available tools atm.
@sandman01: where did you get the unofficial untouched european HTC HD7 firmware?
I would also love to look inside the rom cooking process. AFAIK there are only a few tools here on XDA, that allow rom manipulation up to a certain degree. And the custom roms need the RSPL or HSPL boot loader to flash the unofficial roms, because the official roms are signed.
However, I did not ever see any of the original roms, which brings me to my first question: where can I get them?
Hi rudelm!
with RSPL/HSPL you can flash every official HD7 rom.
Look in the HD7 Rom development section for roms you like to analyse
My only requirement is the german language is included in the rom.
@drkfngthdragnlrd
thanks for correcting my mistake I've edited my post
Are these WP7 Rom Tools not what you're looking for?
thesecondsfade said:
Are these WP7 Rom Tools not what you're looking for?
Click to expand...
Click to collapse
Not really,
HTCrie is a good Tool but it isn't able to modify nbh files
If you want rom modifications you have to extract the contens and do you work.
e.g. extract os.nb or gsm.nb open it again with HTCrie and modify it
you can include other IMGFS, aso. when opend os.nb with the tool
Howerver you can't combine the *.nb files to a *.nbh when the work is done
For that operation you need something like the NbhImageTool from DaG, but with modifications (mayby the right certificat) to combine the *.nb files to an signed/correct flashabel *.nbh
see first post updated with the tools I already use
sandman01 said:
Hi rudelm!
with RSPL/HSPL you can flash every official HD7 rom.
Look in the HD7 Rom development section for roms you like to analyse
My only requirement is the german language is included in the rom.
@drkfngthdragnlrd
thanks for correcting my mistake I've edited my post
Click to expand...
Click to collapse
about the RSPL/HSPL stuff: I know, OSPL is the one that flashes only the official firmware files. I'm currently flooded with all these new links to more and more roms, it's so damn confusing
Maybe these tools are the right way to look for cooking roms? http://forum.xda-developers.com/showthread.php?t=1240455
rudelm said:
Maybe these tools are the right way to look for cooking roms? http://forum.xda-developers.com/showthread.php?t=1240455
Click to expand...
Click to collapse
You are right it's a little bit confusing.
The link you mentioned needs a Costum rom with two modified certificates to work for us.
(DefaultCerts.dat & MsDefaultCerts.dat)
So you wil need a costum rom to be able to make your own update packages. :-(
custom roms build process solved
see post 1 for tools
Guide
re-wrote my initial post to a guide for everyone!!
Just a quick question....
Could this be used on.... Say one of the HTC leaked mango roms to put in a reg key or 2, so when you flash it's pre-unlocked ?
For the moment I have only extract radios and os files and flash it for my purpose
tomorrow I will try to modify default.hv (regestry) to get an unlocked NoDo rom and if all seems good I will also try to flash mango from the official RUU on my HD7 (os only)
At the moment I don't know why it shouldn't work.
the issues with bricked bootloader in Cotullas XSPL thread comes from flashing the 4.x SPL which I do not include. So I think Mango isn't a problem only the new SPL 4.x
But if you were faster than me, try to flash an unmodifierd Mango os.nb and tell me if there could be built/flashed properly.
If you like to modify the regestry dump the imgfs from the os.bin andd edit the default.hv with HVEdit (see the links in the first post)
rebuild IMGFS & os.nb and than merge it together wit nbhMerge to get a flashable *.nbh
Hope that works
For now I will go to sleep
good night from austria
FYI:
yesturday I had troubles flashing a os only rom cause I use ansars costum NoDo rom wich leads in an error after flashing, don't know why.
The original RUU os.nb's worked today without issues.
At the moment I flashed the latest 1.69 NoDo rom with the 5.69 radio from the Mango rom ==> works great
Thanks, with my US HTC Trophy, there is no backup (NoDO) rom available.
I tried the leaked HTC mango rom and I liked the firmware updates/radio update. The problem is I can't unlock it. So, it would be a dream if I could take the mango rom and pre-unlock it so when it's flashed, it's already to go
Thanks for looking into this, can't wait to see if you have any luck here. Could make unlocking phones for people really easy.
[How to] for registry modification on the first post
Tested it with official Mango rom & implanted Developer Unlock & prevent from relocking
Also the trick with CustClear in /Windows
Work in the same way lik NoDo, only the hex offset were the differences are in os.nb is different
Have u been able to change the boot logo on the 4.05 mango rom?
Good guide, I missed a few parts with the hex editing to complete my rom, so thx mate
itje said:
Have u been able to change the boot logo on the 4.05 mango rom?
Good guide, I missed a few parts with the hex editing to complete my rom, so thx mate
Click to expand...
Click to collapse
Havn't tried it jet.
I will test to change the boot logo when I'm back from work
Did you mean the HTC boot logo or the Windows Phone Animation at the beginning?
I tested the boot logo, but I can't access the setting needed in htcrie to add new. I have not tested this on NoDo rom, so I am not sure if its something in my setup or if its "locked" in Mango
Have not looked for the animated one, but I imagine I will try change that too
itje said:
I tested the boot logo, but I can't access the setting needed in htcrie to add new. I have not tested this on NoDo rom, so I am not sure if its something in my setup or if its "locked" in Mango
Click to expand...
Click to collapse
Yesturday I tried to change the boot logo but failed also.
Extracting Logo.bin & the spash screens itself it not a problem, however reinserting with the right compression is.
imgfsFromDump says that the compressin DLL doesn's support the right compression methode.
(tried the v5 &v7 dll)
BTW. the Logo.bin is strange, because its very small compared to the 2 big pictures which it should contain.
And its mostly filld with 00 & FF (viewed in hex editor)
Maybe the pictures are stored on an other place as well
Related
Hey there,
i decoded the newest o2 ROM and found out (using a hex editor on the decoded .fat-file) that at about 74% till about 99% it's all empty (just FF FF FF). NOW THAT'S A WASTE OF ROM! :evil:
Regards,
NiTeSHiFT
Sound good news to me.
A) Room for more code.
B) Room for bug fixes.
C) Perhaps efficient programming.
Better than a full rom with no room for fixes and extentions.
Then again you could argue that entended code with lots of goodies should be there already.
John
NiTeSHiFT said:
...I decoded the newest o2 ROM and found out (using a hex editor on the decoded .fat-file) that at about 74% till about 99% it's all empty (just 00 00 00)....
Click to expand...
Click to collapse
Does that mean that 25% of the previous ROM was that flabby o2 interface
Perhaps o2 were forced to get rid of their interface to make way for the forthcoming AKU2.
astage said:
Does that mean that 25% of the previous ROM was that flabby o2 interface
Click to expand...
Click to collapse
OK, I try to look it up in the shipping ROM as I go on vacancies for a week now... But that has to be done before ;-)
...
OK, same in the original ROM: from 02f0c250 it starts with FF FF FF FF till 3effffff where it ends with the FF FF FF FF. Seems to me as unused space.
Why didn't they add the new .Net CF 2.0 in that space for example?
NiTeSHiFT said:
astage said:
Does that mean that 25% of the previous ROM was that flabby o2 interface
Click to expand...
Click to collapse
OK, I try to look it up in the shipping ROM as I go on vacancies for a week now... But that has to be done before ;-)
...
OK, same in the original ROM: from 02f0c250 it starts with FF FF FF FF till 3effffff where it ends with the FF FF FF FF. Seems to me as unused space.
Why didn't they add the new .Net CF 2.0 in that space for example?
Click to expand...
Click to collapse
i injested my own files into that ROM.
nearly to 20MB of files in totaly can be injected and flashable to boot.
Nice to me!!
Asukal said:
i injested my own files into that ROM.
nearly to 20MB of files in totaly can be injected and flashable to boot.
Nice to me!!
Click to expand...
Click to collapse
Well, good for you ;-) Now I need any information how ->I<- can do that ;-)
Which Program can I use to inject files to the ROM? Would love to inject the .Net CF 2.0 and some other things I use often, like the never Changing Adobe Reader and such stuff ;-)
Regards,
NiTeSHiFT
NiTeSHiFT said:
Asukal said:
i injested my own files into that ROM.
nearly to 20MB of files in totaly can be injected and flashable to boot.
Nice to me!!
Click to expand...
Click to collapse
Well, good for you ;-) Now I need any information how ->I<- can do that ;-)
Which Program can I use to inject files to the ROM? Would love to inject the .Net CF 2.0 and some other things I use often, like the never Changing Adobe Reader and such stuff ;-)
Regards,
NiTeSHiFT
Click to expand...
Click to collapse
Hi! just inject files into windows filder, not any othe folders now.
*if you want to inject some programs, you must make Shortcut manually
after boot the new your ROM.(i made cab file to create short from Extrom,when you make hard reset)
* .Net CF 2.0 and Adobe, i think also work.....
*also delete the files you dont want.
For me, i injected wince.nls(national language support file) and japanese and Chinese fonts, and ClearVue PDF viewer,Japanese Input systems like them....
following is the stpes to you rown ROM
But pls do it carefully, if your steps were wrong, the new rom cant
boot.
But Sirial/USB mode never die even you failed flash ROM,
you can re-flash another one agai.
pls do this your own risk.
-----the way to MY_ROM----------
PLS use the HTC64-Extended rom-tool to encode/decode nbf-nb(fat) by
graphical interface by mr,ball666.
http://forum.xda-developers.com/viewtopic.php?p=191164#191164
Use this Decode to nbf to nb (default is xxxx.fat)
U can use both of fat / nb with mamaich ROm Editor.
U must save the Project file (xxx.prj) when decode.
this prj file need when you encode back nb(fat) to nbf.
1; decode nk.nbf to nk.nb(or nk.fat) with this tool.
then ROM editor by Mr,mamaich
http://forum.xda-developers.com/viewtopic.php?t=34171&highlight=
2; prepapearr_image.exe nk.nb(or nk.fat) -nosplit
*imgfs_raw_data.bin and imgfs_removed_data.bin were created(0KB)
add or delete files of imgfs_raw_data.bin (edit this)
3;(ex delfile.exe <filename>----u can delete files with this
4;(ex addfile.exe <filename>--u can add files with this
5:make_imgfs.exe nk.nb(or nk.fat) -nosplit ---imgfs_raw_data.bin will be remake to nk.nb(or nk.fat)
6; use HTC64 Extron tool again to encord the nk.nb(or nk.fat) to nk.nbf
again(if you have nk.nbf in same directry, it will be over write)
@the buildimgfs.exe from dumped&edited files with view_imgfs.exe is not work yet.
Good luck!
Hi Asukal,
I am really tempted to what you have done....
However, I understand that the time required is huge.
If possible, can you use the new O2 rom as a base and input the windows folder following:
1. wince.nls (chinese)
2. adobe reader ppc version 2
3. latest skype 1.20.89
4. .Net CF version 2
Merry Christmas and happy new year!!!
Cheers,
chris_khho said:
Hi Asukal,
I am really tempted to what you have done....
However, I understand that the time required is huge.
If possible, can you use the new O2 rom as a base and input the windows folder following:
1. wince.nls (chinese)
2. adobe reader ppc version 2
3. latest skype 1.20.89
4. .Net CF version 2
Merry Christmas and happy new year!!!
Cheers,
Click to expand...
Click to collapse
Merry Xmas to you!
i will try but can you wait for a while,
i must fly to Dalian in nothern china tommorow morning and
back to here shenzhe on 26th,
i will finish after my trip!
Good luck!
Of course no problem.
Good luck to your trip.
I will have another hardreset soon I think.
Cheers,
Package Tool is an extension to Mamaich's imgfs tools
- Main function of this tool is to build packages for a new Rom Kitchen I'm working on
- Using this tool you can also extract the following information after creating a dump folder using viewimgfs.exe:
Core OS
Value: "Windows Mobile-based Pocket PC" or "Windows Mobile-based Smartphone"
Versions
Shows the version of the packages
SYS
This is the OS version
The example shows Crossbow, CE 5.2 Build:15341 AKU 0
NET
This is the .NET Compact Framework version
OEM
This is the version of the OEM packages
The example shows only one,
but I've also seen ROMs with different versions for each OEM package.
In that case there would be multiple OEM entries
Language
The LANGID and the language of the ROM
DPI
The DPI (dots per inch) of the resources
this also depends on the resolution of the device
Value: 96 or 128 or 131 or 192
Certificates
List of all certificates used for the packages.
The OS is signed my Microsoft and the OEM packages are using a certificate from the OEM
Missing Manifests
This is a list of all packages that are missing inside the dump folder.
It is normal that there are missing packages, because the packages from the boot section (XIP) are missing... don’t worry about them
Missing Files
This lists all missing files.
Someone edited the ROM or removed files from the dump folder!
Example:
Code:
[Selected Path]
C:\dump
[Core OS]
Windows Mobile-based Pocket PCs
[Versions]
SYS: 5.2.15341.0
OEM: 2.18.0.0
NET: 2.0.6129.0
[Language]
0409 - English (United States)
[DPI]
96
[Certificates]
CN=Microsoft Windows Mobile PCA, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
CN=OEM Sign 2005
[Missing Manifests]
d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
723fb954-d931-4348-b672-82a188e587b5.dsm
13cb07c1-20b6-567f-dfcc-39d58b95e374.dsm
This tool is very useful for analyzing an unknown ROM, especially to extract the OS version and it will be much more useful after the release of the new ROM Kitchen.
It is also possible to execute the tool using the command line
Usage: PKGTool.exe <path to the dumped ROM>
This would just create packages, without any output
Because of this usage, you can just drag & drop the dump folder onto the tool
About the package names
The names of the packages can be extracted from the dump folders for WM6, but WM5 contains GUIDs instead of names.
To provide the ease of WM6 "Package Names" for previous (i.e. WM5) ROMs, the tool collects all package names inside map.txt and replaces the GUIDs with the actual Package Names.
You must let the tool read a WM6 dump to collect the Package Names before it can replace WM5 GUIDs.
e.g.
- Building packages from a WM5 dump creates: 1bc57b2f-c0f3-46c6-8c2a-257952317eac
- Building packages from a WM6 dump creates: OEM_Lang_0409
- Building packages from a WM5 after it was used for a WM6 ROM also creates: OEM_Lang_0409
Extending the map.txt can be disabled by: Menu - Tools - Expand Map
Download: View attachment package_tool_v1.01.zip
ROM dump converted to packages...
It is exactly the tool I'm looking for.
But... doeas it require any additional dll's? VB runtime or whatever? I have had exactly the same problem with your XIPPort. There are two version published here. One works fine (exe file 2007-01-21), second one (published with sources) produces:
message translated from polish into english:
Application can not be executed, because configuration is not valid. Problem can be resolved reinstalling application.
I've got the same message running PKGTool.exe
Sorry...yes, someone else told me the same...
I think it is cos I installed:
Microsoft Visual Studio 2005 Professional Edition - DEU Service Pack 1 (KB926606)
I will try to get that working... just give me some time
bepe said:
Sorry...yes, someone else told me the same...
I think it is cos I installed:
Microsoft Visual Studio 2005 Professional Edition - DEU Service Pack 1 (KB926606)
Click to expand...
Click to collapse
I have VS too.
Please wait - I'm downloading ENG SP1 now. I'll check if it is the reason.
I will try to get that working... just give me some time
Click to expand...
Click to collapse
Sure ))
yes, it is the reason... see:
http://community.macrovision.com/showthread.php?p=375127
bepe said:
yes, it is the reason... see:
http://community.macrovision.com/showthread.php?p=375127
Click to expand...
Click to collapse
ok. you are right
Ok, I completely removed visual studio and installed it without SP1...
After that I recreated the tool, it should be working now
I've had no problem running the tool (then again i'm running win2k ) but what i'd like to know for now is how to get the OS version/build values
tx
ok, sorry I forgot... the information about the OS might only exists in newer roms
did you have anything after
[Versions]
...
?
bepe said:
ok, sorry I forgot... the information about the OS only exists in newer roms
did you have anything after
[Versions]
...
?
Click to expand...
Click to collapse
The program worked flawlessly m8; I'm asking this to know how to get it myself , that is if you don't mind sharing it
the OS version is written into the dsm files...
open this dsm file using a hex editor:
d0b41563-b345-4444-aa15-986e7c7fff99.dsm
after 0x003C you will see something like:
05 00 01 00 D0 07 FF 39
that’s the OS version and build
Yes. It works after installing VS SP1.
Many thanks.
A Great And Very Useful Tool Bepe.
I Cannot Wait To See Your Finished Kitchen.
Cheers
Congrats Bepe!
Package Tool rules
Very nice
Thanks Bepe
I used to coock by ur previous kitchen
It was easy (even 4 beginer like me) and worked very nice
I hope this one will be more usable
1-Would u pls give us the steps?
2-Do we need to have WM6?
3- Is it for all devices, I have Himalaya?
4- Can we use it now or wait for the finished kitchen?
Sorry for to much ques.
Regards
v1.01 - Fixed a small bug in map handling
@The_hesham:
this is only the first part of the new kitchen…
I only released the tool cos it can also be used to analyze roms
to use this for a kitchen you have to wait for the new version
bepe said:
@The_hesham:
this is only the first part of the new kitchen…
I only released the tool cos it can also be used to analyze roms
to use this for a kitchen you have to wait for the new version
Click to expand...
Click to collapse
Bepe
As I understand I should have ROM already have the following
1- All *.rgu & dsm files are not deleted during cooking. But we delete *.rgu file in order to save space
2- We alraedy have ROM built by ur way mention some time ago (and I succed to cook with it)
Or I misunderstand somthing
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="]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?
Here is the updated version of my Lg multidevice kitchen. It now supports :
- ks20
- ct810
- gm730
- gm735
- gm750
- gw820
- vs750
::These tools have been made thanks to: MisterJp, CopsFrance, Teoami, Bepe, Ervius, No2Chem, Da_G, Cmonex, Jayautros
This kitchen is now built around ervius visual kitchen for bepe's platform rebuilder. I don't really like write a lot, so I won't explain every option in details, nor will I write a "how to cook roms for dummies", it's already been done in the past, if you know how to search, you'll find very interesting threads on it on this forum.
Kitchen options (use "*" to switch between standard and advanced options)
SELECT DEVICE
::1-KS20 2-Incite ...
Needed for every operation below, don't forget to set it.
DUMP FUNCTIONS
::a- Extract DZ File
Extracts baserom\rom.dz file into baserom folder
::t- Extract BIN ROM File
Extracts baserom\rom.bin file into baserom folder (for vs750)
::b- Extract Flash.bin
Extracts baserom\flash.bin into builtrom\temp, creating directories if they don't exist.
::c- Dump imgfs.bin
Extracts content of builtrom\temp\part_2_imgfs.bin file to temp\dump, allowing you to edit windows files.
::d- Dump bin.bin
Extracts content of builtrom\temp\part_1_rawfs.bin to ROM\XIP
::e- Launch ErviusKitchen
Launches ErviusKitchen, allowing you to modify and generate a new rom
BUILD FUNCTIONS
::f- Build imgfs.bin
Creates new imgfs from temp\dump folder to builtrom\temp\imgfs.bin
::g- Build flash.bin
Generates a new flash.bin into builtrom folder based on builtrom\temp directory and new imgfs.bin
::h- Build rom.dz
Generates a new rom.dz into builtrom folder based on baserom mbns and new flash.bin
::u- Build rom.bin
Generates a new rom.bin into builtrom folder based on baserom mbns and new flash.bin (vs750)
::i- Build flasher
Generates a new rom.exe into builtrom folder based on rom.dz (only available for Incite)
XIP PORT
::j- Launch XipPort
Launches XipPort, allowing you to modify and generate a new xip
::k- Reloc Xip
Relocates xip after you've changed it using XipPort
::l- Use New Xip in Build functions
Allows you to use the Xip built with XipPort when building flash.bin (either from the kitchen or directly from ErviusKitchen)
::m- Restore original Xip in Build Functions
Allows you to use the original Xip when building flash.bin (either from the kitchen or directly from PkgToolsBuildOs)
Kitchen use:
Select the device you want to cook for (1=ks20, 2=incite...)
Take a dz file, and put it into baserom\(your device name) (KS20, incite, gm750...).
run start.bat
execute a, b, c, kitchen options
now copy temp\dump\sys into \sys\(your sys version), and arrange the files so that it looks like the \sys\20755 folder. Do the same with OEM folder (copy it to \OEM\(your device name).
execute d, and arrange xip folders : copy the content of your oemxipkernel into rom\(your device name)\(your ip version) and everything else into rom\shared\(your xip version)
go into tools\xipport. Launch xipport. Click "dump xip.bin"
OPTIONAL : If you want to port xip to another version click "make pkgs". Now replace modules\msxipkernel* and files\msxipkernel* with the ones from the newer xip. Click "undo".
execute Kitchen "k" and when a message tells you so, click "realloc p", "write maps", "build xip_out.bin". 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).
execute Kitchen "l" to use this xip.
execute "e" to launch ervius kitchen. Then select your device, language, ext, rom dpi, rom res, xip build and sys build. Choose the packages you want to include (for your convenience, I included a few packages tweaks and fixes in EXT\(your device name). Eventually click the "create" button.
Optional for Ks20, required for Incite : execute step h to produce a rom.dz file.
Now enjoy your new creation in builtrom\(your device name).
If you want to make a 1st rom easily, or if something went wrong and you want to verify you've done everything correctly, I'm also providing 2 packages (1 for KS20, 1 for Incite) with almost every step already done. They're very similar to the roms I made (xCite2b, KisS20.4). Download the package you want, extract it into your kitchen folder, then :
- Execute step "B" to generate a few files
- Execute step "E" to launch Ervius kitchen
- Optionnaly, try to rebuild xip part with step "K" and "L" (1st rename xipport\out.INCITE.21046 to xipport\out) (I'd suggest doing this only after building a 1st working rom)
- Click Load and select the preset for your device (INCITE_0409_20755 or KS20_409_20755).
- Click create (and for incite users, execute step "H" of the kitchen to produce a rom.dz).
That's it.
If every step was successful, you should have a flash.bin file in builtrom\(your device name) folder and optionnaly a rom.dz.
KS20 : Then just flash with lgmdp your baserom directory and just change flash.bin path from baserom\flash.bin to builtrom\flash.bin.
Incite : either use the usual way (rom.dz replacement) to flash your device or execute step "i" to produce a rom.exe with teoami tools.
Congratulations, you've just flashed your first LG <insert the name of your device here> cooked rom
Before you ask :
- I chose 20755 build because it's proven to be bugfree for Ks20 and Incite (and build is smaller too), if you understood the process, you should be able to build a rom for any wm build.
- Ks20/Incite Packages contain latest available oem parts (spanish 10e unbranded for the Ks20, 10x for the incite). (Incite is the clean version, if you want the full stock oem, just dump imgfs.bin)
- Base kitchen Ext folder contains everything to build a bugfree 20755 rom.
- If you want to make the same thing for wm6.5, just download a wm6.5 build.xip somewhere and replace the files in the kitchen.
- 20755 folder is not in the basic kitchen anymore, but I've made another archive that you can download if you need it.
- as for vs750 roms, you need to use bin (decrypted) files (not wdb). Don't forget to replace step "a" with "t" and step "h" with "u" in the tutorial above. You will need the decrypted roms available in the bottom of this post.
I'm just asking you 1 thing : if you make changes to this kitchen to improve it, please, share what you've done (and of course, if you're using it, you can also buy me a beer)
Kitchen history:
v2.3 [2011-10-13] - Added (partial: can't decrypt roms for now) support for VS750 roms.
v2.2a [2010-05-10] - Added support for GM735 WM6.5 roms, corrected a bug in GM730 rom creation.
v2.2 [2010-04-22] - Added support for many devices, updated almost every tool to latest version, build process is faster than before
v2.0 [2009-07-09] - Changed to ervius visual kitchen for bepe's platform rebuilder, multidevice support (ks20, Incite). New tools, rewrote almost everything.
v1.1 [2008-08-25] - Added Xip Port and Tools sections
v1.0 [2008-07-15] - Initial revision
Download Links:
Vogica v2.3, the LG multidevice Kitchen
Incite addon / Ks20 addon
Sys 20755
VS750 v5 decrypted rom
VS750 v7 decrypted rom
Old releases :
Vogica v2.2a, the LG multidevice Kitchen
Vogica v2.0, the LG multidevice Kitchen
Vogica v1.1, the KS20 Kitchen
Useful Links:
LG KS20 custom rom KisS20 (UC, WM6.1)
LG Incite custom rom xCite (UC, WM6.1/6.5)
Thank you MisterJP and you. You made some very good work for the coocking of the KS20.
Thanks to both.
nice tool !
but
Code:
cls
set choice=
cd BuiltROM\temp
..\..\TOOLS\LGFlashMuncher.exe -c ..\flash.bin -e Header.bin -0 part_0_BOOT.bin -1 part_1_RAWFS.bin -2 imgfs.bin ..\..\BaseROM\flash.bin
cd ..
pause
GOTO :start
:9
cls
set choice=
cd BuiltROM\temp
..\..\TOOLS\LGFlashMuncher.exe -c ..\flash.bin -e Header.bin -0 part_0_BOOT.bin -1 part_1_RAWFS.bin -2 imgfs.bin ..\..\BaseROM\flash.bin
:8
the new xip.bin don't Insert !!!
it shoud be
..\..\TOOLS\LGFlashMuncher.exe -c ..\flash.bin -e Header.bin -0 part_0_BOOT.bin -1 xip.bin -2 imgfs.bin ..\..\BaseROM\flash.bin in :9 ?
good....a nice start........and thanks
Thanks for your great job! Hoping that KS20 will have its Cook Rom & WM6.1 at last!
waiting for wm6.1 on my lovely ks20
is this the most actual thread to the ROM cooking stuff
Would like to use french 1f ROM but cook German language into it
Greet`s Erich
I have made a flash.bin with language in german for the ROM HKG 10a, which is in normally in english. So, the HKG 10a is newer than the French 10f. Why to use an older ROM? Find the flash.bin here:
http://rapidshare.com/files/131832687/flash.zip.html
Thank you itapower
many thanx!
Is there something I have to take care of?
Or can I flash it like I flashed the ROM from 10b to 10e?
Did you just change the language or also other stuff?
Is this ROM running without troubles?
Is it locked or branded?
I have unlocked KS20 with vodafone branding right now,...
Greet`s erich
changing language of ROM
don`t know why nobody from the pros is responding
Most of my questions I figured out yesterday - but I am very curious how to change the language of a ROM be myselfe
This I couldn`t figure out
Hope someone can tell me which of the 10 .mbn Files I have to change or is the language in the .bin
Greet`s Erich
Basically, you need to extract the flash.bin, replace *.409* folders with *.407* versions (407 is for germany) that you may find in another rom. That's not a trivial operation, although the kitchen helps a lot. There are tutorials here that explain this with more details (search for "translate" ou "localize" rom).
more questions
Hello spocky12!
I got really interested in cooking ROMS while playing around with the kitchen
But I don`t get the difference between "flash.bin" and "imgfs.bin"
What is included in which .bin
When the *.409* folders are replaced with *.407* and the ROM is cooked
is it enough to flash the "flash.bin" to the KS20 without the "imgfs.bin"
Another question is the Registry tweaking - which I wanna do.
You have a folder in the kitchen "Packages\OEM_Registry Tweaks Pack" there are 3 files.
Is the name random or how is the convention?
The .dsm file is Hex - what is it for?
Is it enough to edit the .rgu file?
When cooking the ROM does it include the changes I perform in the .rgu file?
Hope you help me understanding this a bit better
Greet`s Erich
@eriche : follow step by step the kitchen tutorial, you should see clearer.
- Imgfs.bin is a file contained inside flash.bin (as xip.bin and a few other).
- The files you need to modify are inside imgfs.bin
So what you need to do is:
1- extract dz to obtain *.mbn and flash.bin
2- extract flash.bin to obtain imgfs.bin, xip.bin...
3- extract imgfs.bin to obtain WM files
4- change files
5- rebuild imgfs.bin
6- rebuilt flash.bin
7- flash new flash.bin + original mbn files.
For Registry tweaks, you can directly change rgu file in OEM_Registry Tweaks Pack. When you rebuild you imgfs, it will be automatically added to system registry so you dont need to create a new package.
7- flash new flash.bin + original mbn files.
Click to expand...
Click to collapse
Isn`t it possible to flash only the .bin file
With original .mbn files you mean the one from the Base Image where I change the language or the Image where the Language is included
Greet`s Erich
You should be able to flash only flash.bin but I can assure that you won't crash your phone.
To flash, you only need partition.mbn and flash.bin but if partition.mbn differs from your actual ks20 partition (that is, if your actual rom mbn don't come from the same dz than your cooked rom), there's a chance that flash.bin overlaps something else on you phone. So it's secure only if you've already flashed the same mbn and the same partition.mbn before. If not, I can't say, maybe it is, but not for sure.
So as I wrote on first post, to flash, select baserom as rom folder. Each mbn line will automatically populate and the just change the path to flash.bin to your newly built flash.bin (which is in builtrom if you use the kitchen).
language cooking not easy - but I don`t wanna give up!
oh god - it`s not that easy
I don`t know in which step I have to replace the Language folders
With HK-ROM (newer ROM) I did step a-e = 1-8
With GER-ROM (language ROM) I also did a-e = 1-8
but then I have 77 ".0407" and 59 ".409" folders
so why is this? Different languages have different folder amount?
Or should I change the language after step "d" ??
looking forward to bring light inside
EDIT:
I used "PKGToolsBuildOS" (step e) to change the language.
But this tool brings following message
Not copied: OEMBT_Lang_0407! No \SYS\ folder corrisponding...
Not copied: OEMVVS_Lang_0407! No \SYS\ folder corrisponding...
Click to expand...
Click to collapse
Don`t know if this is critically?
I prefere to do things by my own - because I don`t trust tools that crash that often *gg*
GreeT`s
I've never succeded in using PKGToolsBuildOS to change rom language. I do it manually.
It seems that you're counting also subdirectories in your 040x folder count (ie, there's a Base_Lang_0409 folder and inside lies a commctrl.dll.0409.mui. Of course, you don't need to count it as changing Base_Lang_0409 folder will also replace its subdirectories.). Sys folder should contain approximately 30 040x first level folders. Between roms, it there may be 1 or 2 folders less or more (depending on the availability of windows_live and things like that.)
The only thing important is that in the end, every folder that was 0409 is now replaced by 0407 folder.
I did it
Jea - today I did it
I flashed HongKong 10a ROM with German language to my KS20.
I have now
ROM: v10a
Bootloader: v10a
Modem Firmware: V10e
ROM date: 2008-04-29
I don`t understand why the Modem Version is still the "old" one
How can I get the newest modem Firmware from the HongKong ROM?
ROM-Date seems also the "German 10e" date.
Who can bring light inside :I)
Greet`s erich
Informations about version are stored in registry (in HKEY_LOCAL_MACHINE\Software\LGE\VersionInfo).
As for modem version, it's in mbn files and not in flash.bin.
So does it mean I have the "modem Version" from the HongKong ROM but only it shows the "old" one
Or do I have to change a .mbn file to change Modem Version?
Whitch .mbn file is the one holding the Modem crap?
I know from my friend who owns a HTC Diamond that a new modem version can save battery and bring faster or more stable access,...
Greet`s erich
I made a kitchen for the Herald that creates ROMs in both XPR and LZX compressions and I was wondering if you guys wanted it ported to your phones?
If you want it, I need a few things. This ROM is compatible with Bepe's Extended ROM kitchen. It won't come with OEM, ROM or XIP folders as you can get those yourselves.
The way the kitchen work is:
Run "RunMe.bat"
Choose compression algorithm. (XPR or LZX)
Follow the normal Bepe's kitchen process.
Wait as the kitchen creates the ROM (like Bepe's kitchen, but with whatever compression you chose.)
The kitchen will automatically open up the imgfs.bin in a hex editor and automatically adjust it for the wanted compression before it builds the ROM.
It automatically inserts the proper XIP drivers.
It will automatically set the Pagepool to 4MB but give you the option to change it to something else as it does.
It then automatically creates the NBH and then finally launches whatever flasher (CustomerRUU, FlashCenter, or whatever your devices use) to flash the ROM.
For those who don't know what LZX compression is:
It's a compression algorithm that, although slower (by 1-4% in real life use) gives a good amount of free storage space. In some case (like in the Herald) it makes the ROM so small that it has to be flashed through an SD card due to the Herald's flashing size requirements. On an average 50mb ROM, it takes off about 10mb. The actual cooking itself does take a LOT more CPU and RAM to do in your PC, though. Especially the RAM. (It's because the tools that actually do the compression weren't really optimized for the job.)
Anyhow, let me know if you want it.
I would like to view it
thanks
Oh yeah I would really love to try it!
Oh great , i would really like and need it to cook WM 6.5 rom , please tell us what you need .
I need to know the following:
What RUU/FlashCenter/Whatever you guys use and a link to it.
What the name of your NBH has to be when flashing through SD card (just an added bonus, not really needed.)
I need to understand what the hex editing is for in this thread.
I need a cook to volunteer a working ROM's kitchen files.
Lastely, I need two beta testers to test said ROM built in my kitchen. They'll be testing both the algorithms by testing two ROMs and reporting back to me.
EDIT: A few minutes later and I've modified the kitchen. I just need the info that I asked for above to finish it.
ivanmmj said:
I need to know the following:
What RUU/FlashCenter/Whatever you guys use and a link to it.
Click to expand...
Click to collapse
ROMUpdateUtility.exe, in the forum you can find it. I will search for it, but if you download any radio for trinity (in the wiki) you will have all needed files.
I said radio because of the size (smaller download)
What the name of your NBH has to be when flashing through SD card (just an added bonus, not really needed.)
Click to expand...
Click to collapse
TRINIMG.NBH (I think)
I need to understand what the hex editing is for in this thread.
Click to expand...
Click to collapse
It is for changing the id of the os partition. In the trinity standard is 0x400 (the same in most htc devices), for P3600i the id is 0x401. You will have to make in the bat a choice, and modify the line of inserting os.nb whith nbhutils
I need a cook to volunteer a working ROM's kitchen files.
Lastely, I need two beta testers to test said ROM built in my kitchen. They'll be testing both the algorithms by testing two ROMs and reporting back to me.
Click to expand...
Click to collapse
Sorry but the trinity is my work phone, and I can't flash it frequently
mac_es said:
ROMUpdateUtility.exe, in the forum you can find it. I will search for it, but if you download any radio for trinity (in the wiki) you will have all needed files.
I said radio because of the size (smaller download)
Click to expand...
Click to collapse
Awesome.
mac_es said:
TRINIMG.NBH (I think)
Click to expand...
Click to collapse
Thank you.
mac_es said:
It is for changing the id of the os partition. In the trinity standard is 0x400 (the same in most htc devices), for P3600i the id is 0x401. You will have to make in the bat a choice, and modify the line of inserting os.nb whith nbhutils
Click to expand...
Click to collapse
If this is not already a feature of your kitchen, I can EASILY make it so that if you choose trinity standard you get 0x400 and if you choose P3600i you get 0x401. So I guess this kitchen will have a dual purpose. Out of curiousity, what's the difference between the two devices? And this is done to an NBH file? Wouldn't it be easier to just create the NBH with the proper OS partition address in the first place?
mac_es said:
Sorry but the trinity is my work phone, and I can't flash it frequently
Click to expand...
Click to collapse
That's quite alright. ^_^ I appreciate the knowledge you have volunteered already.
If this is not already a feature of your kitchen, I can EASILY make it so that if you choose trinity standard you get 0x400 and if you choose P3600i you get 0x401.
Click to expand...
Click to collapse
Thanks, I cook for me so I don't need it.
So I guess this kitchen will have a dual purpose. Out of curiousity, what's the difference between the two devices? And this is done to an NBH file? Wouldn't it be easier to just create the NBH with the proper OS partition address in the first place?
Click to expand...
Click to collapse
The diffs are a more powerfull CPU (500 MHz) and more ram. Most cookers build for P3600 so the hex edit is for trying a rom cooked for P3600. Yeah, it is more clean to generate a new nbh but you will have to convince the cookers.
FYI, you should make a separate device in the xip section, in the OEMXIPKernel. The nk.exe for P3600i should be at least rev3, and most of cookers of P3600 use nk.exe rev0
Kitchen finished but before I upload it, I think I'm going to add a script to allow both P3600 and P3600i creation. If you can get me nk.exe rev3 and it works on all trinity's, I can go ahead and make it so that it automatically updates the nk.exe on all ROMs cooked in the kitchen. Make sure it's in module form.
If you can get me nk.exe rev3 and it works on all trinity's, I can go ahead and make it so that it automatically updates the nk.exe on all ROMs cooked in the kitchen
Click to expand...
Click to collapse
nk.exe rev3 works on all trinitys but it has an issue whith saving DPAPI keys in the file system. As result, after some resets you have lost all the passwords stored in the device.
To avoid this you should add a key in boot.rgu. (Take a look to the thread of P3600i or to chanvi's wm6.5 rom) Chanvi stated that even whith that key there are some issues (though it is working fine for me).
Also I prefer nk.exe rev0 to rev3. The device is better in response time (at least for me).
Also it has been appeared a "new" nk.exe, which chanvi use in his rom that should work in any trinity. I don't know if it is better or not than rev0...
Hmm... I now have to decide if it's worth the time, seeing as I'm making kitchens for EACH device and working on two Herald ROMs (while working full time). I've got two options, make it so that the right rev and registry keys go with the right device automatically, or let people do it themselves. Does anyone by any chance have both files already ready along with the registry keys? It would help a lot (since I'm already downloading kitchens and ROMs from EVERY device, it's a lot more work to research and download even more kitchens.
Here is info (ONLY FOR COOKS), how to make LZX compression work on our kitchen. This method is tested by myself and everything works fine.
Short step by step instruction:
1. Download fixed version of cecompr_nt.dll from HERE
2. Replace cecompr_nt.dll from kitchen to downloaded file.
3. Download from attachement cecompr.dll and replace it in your XIP section.
4. Open os.nb.payload in HEXeditor and find beginning of imgfs. Here is how it looks in my case (ULDR removed):
Code:
00280000 F8 AC 2C 9D E3 D4 2B 4D BD 30 91 6E D8 4F 31 DC ř¬,ťăÔ+M˝0‘nŘO1Ü
00280010 01 00 00 00 01 00 00 00 01 00 00 00 34 00 00 00 ............4...
00280020 08 00 00 00 00 02 00 00 00 10 00 00 58 50 52 00 ............XPR.
5. Replace XPR to LZX, and save this file.
6. Now you can cook with LZX compression = about 9-10 MB more free space on storage
Hi Tomme45i
Don't boot for me , what mean (ULDR removed) , i have he same HEWEditor that you but my os.nb.payload is a "reducer" , may be it's the error ?
chanvi93 said:
what mean (ULDR removed)
Click to expand...
Click to collapse
Hi chanvi93
You can read something more about ULDR HERE. Removing ULDR partition gives you about 3 MB more free space on internal storage. You can edit it by yourself manually, or you can use XipporterEx by Ervius & udK (it is implemented in visual kitchen by ervius). Ervius kitchen have also payload_reducer, so after removing ULDR and reducing size, my os.nb.payload have size 2.6 MB You must remember to change start insert address for XIP section, otherwise your device will hang on the second splashscreen.
tomme45i said:
Hi chanvi93
You can read something more about ULDR HERE. Removing ULDR partition gives you about 3 MB more free space on internal storage. You can edit it by yourself manually, or you can use XipporterEx by Ervius & udK (it is implemented in visual kitchen by ervius). Ervius kitchen have also payload_reducer, so after removing ULDR and reducing size, my os.nb.payload have size 2.6 MB You must remember to change start insert address for XIP section, otherwise your device will hang on the second splashscreenie.
Click to expand...
Click to collapse
finally some great news..
i will try that on my kitchen - thx ivan thx tommi
Thanks Tommi45i ,
Finaly , i use visual Ervius-Bepe kitchen and shared it with all .
Yea, sorry, I got somewhat swamped with xda "work."
I worked with Ervius to add LZX compression to his visual kitchen, so anyone using it can now enjoy LZX compression.
Hi ivanmmj,
I have a strange result trying to add LZX to my kitchen :
It seems to be partly working as building is much much slower while adding file but the resulting os.nb is 10Mo bigger than with XPR compression and storage at first boot falls from 20Mo.
Any idea on why it's not working as expected ?