How to Dump PDAViet ROMs. I dumped the ROm, but PackageTool does not work on it?
What is the Reason?
How to solve it?
SheikhAatif said:
How to Dump PDAViet ROMs. I dumped the ROm, but PackageTool does not work on it?
What is the Reason?
How to solve it?
Click to expand...
Click to collapse
PDAVIET ROM??? There are 2 reason.
1. The cooker is encrypt it so it undumpable.
2. The cooker remove all .rgu and .dsm file, rgu is the registry file, and dsm is contain location and group of file, PackageTool can't work without dsm & rgu file.
All PDAVIET ROM like that, so...search another ROM.
Imho , it may possible because encrypted file may we desrypted back, and diskimg.nb0 file (flash file) is still saving information about stucture original file (need may learn about it). Other way is to rearrange the files and directories result by dumper not rebuilt completely yet by BuildOS
Related
I was wondering if someone would share some information about low level modification of the rom kitchens. I have been working with Dog Guys kitchen and an original rom image and i have done some extensive modifications. Unfortunately, it is really just a cluged mess. The problem is that I don't know how to modify the underlying registry keys.
NOTE: I am not talking about *.rgu files in OEM packages and I am not talking about boot.rgu.
I am talking about the registry keys associated with the version of the compact framework built into the rom. Or the registry entries that define what applications are initially set on the program menu. Or the keys with the various application that are installed in the rom by default.
I have done a great deal of searching and I clearly don't know what the key words are to find this information. It must exist because both DCD and No2chem were able to either find it or derive it. I am just hoping someone will point me in a direction where I might be able to learn the next stage of rom customization beyond simply adding different OEM packages.
Thanks
most of the programs have their own folders. In each folder there is .rgu file. that file contains registery entries for that program.
in oem folder there are folders oemapps and operator. those folders contain more than one programs in one folder. all the registry entries that are related to all those programs are in one single rgu file in those folder. There are some registry entries in .provxml files as well.
when one file contains registry entries for more than one program, most of the entries that belong to a single program will be next to each other ( not always true )
a1jatt said:
most of the programs have their own folders. In each folder there is .rgu file. that file contains registery entries for that program.
in oem folder there are folders oemapps and operator. those folders contain more than one programs in one folder. all the registry entries that are related to all those programs are in one single rgu file in those folder. There are some registry entries in .provxml files as well.
when one file contains registry entries for more than one program, most of the entries that belong to a single program will be next to each other ( not always true )
Click to expand...
Click to collapse
Could you tell me where the registry information is for the contents of the SYS directory. for example where are the registry entries for SYS/NET. there isn't a corresponding .rgu file.
thanks.
sys folder has lots of other subfolders .. they have their rgu files.
There are some programs in bin format. they are already encoded i think.
You can put registry entries in a cab and put it in extened rom .. and run it after hardreset .. that way it will overwrite the original keys.
atomclock, I found this old thread concerning a solution and troubles with cooking .net CF 3.5 into a ROM:
http://forum.xda-developers.com/showthread.php?t=350279
Keystone said:
atomclock, I found this old thread concerning a solution and troubles with cooking .net CF 3.5 into a ROM:
http://forum.xda-developers.com/showthread.php?t=350279
Click to expand...
Click to collapse
Thats funny... That is the oem package I'm using in my rom.
There seems to be three possible avenues to work this issue.
1. Build oem's and hope that the registry keys in the oem's .rgu file COMPLETELY overwrite the original entries. (Oemizer is a good tool for this http://tiermann.net/index.php?optio...d=3:personal-oemizer&catid=1:Desktop&Itemid=3 )
2. Review the registry after a rom is written and create an xml file that will overwrite and delete all unnecessary registry keys (here is a link for anyone interested http://forum.xda-developers.com/showthread.php?t=366337&highlight=kitchen )
3. Get the inside information as to where the registry keys are actually located and make changes at the source instead of trying to patch it after the fact. (If someone has a link for this information please provide)
Why is it so impossible to get the necessary information to proceed with option 3.
I want to port the drivers from the current official rom to an old wm5 kitchen. I really need to get access to the underlying workings.
NOTE: I already know how to proceed with options 1 and 2. I need the information for number 3.
If you can answer the following question then you have the information I want.
Where are the registry entries for the BUILT IN .net framework (/SYS/NET)?
Thanks
Hi everybody ,
Well I upgraded my titan (htc p4000) with the last dcd kitchen. I want to know what I do wrong or something like that. I want to add prgram and utilitie by the keiser kitchen. I took package and utiliti, the base rom of dcd kitchen and I cook a rom with keiser kitchen: after few minute that say it done, but i d'ont see where the cooked rom are or the utiliti to instal the rom. Thanks and sory for my english if it is bad ...
If you used DCD's kitchen, the output file should be in a folder named RUU wherever you unzipped the kitchen. The file will be named RUU_signed.nbh
If you used ppckitcen's buildos, the output file will be found in your documents folder in a subfolder called Buildos RUU. The file will also be called RUU_signed.nbh.
You can always search for files with an .nbh extension.
The program used to flash the rom will be Rom Update Utility, hence the heavy use of the term RUU.
Flashing via memory card or SD card method is generally better. Read the wiki for more info.
While I was cooking my own rom, I dumped the Stock Rom 1.90.485.3 which came preloaded on my TP which I bouaght in egypt.
I noticed a new cab file which was not included with any other rom I dumped to use in the kithcen.
This file is PT_DDI.CAB which is located in the OperatorPkg_PT folder in the OEM Folder and when extracted includes a New DDI.dll file.
I have searched for the DDI.dll file in all the stock roms and never found it, Only found a DDI.dll folder under Temp\Dump_XIP folder and it does not contain the DLL file only and which gets deleted when we start cooking the rom.
This rasis several questions
-Does this mean that the DDI.dll file is missing?
-Do we cook the rom without the DDI.dll file?
All experts please investigate the cab file included, this may lead to improved graphics quality for Raphael.
I have attached other drivers cab files also included in the rom
Thanks and best regards
As you've said, the ddi.dll is located in XIP, which is another storage area in the ROM that typical ROM kitchens don't modify without extra steps.
So the ddi.dll isn't missing, but yes you sort of cook without it (the XIP stays as-is in most kitchens without modification)
However this .dll may be different, let's take a look
Da_G said:
As you've said, the ddi.dll is located in XIP, which is another storage area in the ROM that typical ROM kitchens don't modify without extra steps.
So the ddi.dll isn't missing, but yes you sort of cook without it (the XIP stays as-is in most kitchens without modification)
However this .dll may be different, let's take a look
Click to expand...
Click to collapse
No, The DDI.dll Folder does not have a DDI.dll, I have attached the Folder for you to look at.
Best regard
Correct, that is a module. This is a format sometimes used to store files in ROM, it is quicker for the device to access these modules than it would be if the .dll was stored as a file. So yes, this folder does not have a ddi.dll, but, the device 'sees' this folder as ddi.dll and it functions as such.
Da_G said:
Correct, that is a module. This is a format sometimes used to store files in ROM, it is quicker for the device to access these modules than it would be if the .dll was stored as a file. So yes, this folder does not have a ddi.dll, but, the device 'sees' this folder as ddi.dll and it functions as such.
Click to expand...
Click to collapse
Now when you start cooking the BuildOS.ex deltes the temp folder and accrodengly also deletes the Dump_XIP folder which was in the temp folder.
Now if you do a search for the DDI.dll, It does not exist anymore.!!
What happend to DDI.dll module?
Regards
It is stored in the XIP, a seperate area of storage outside of the IMGFS, which is the area you are looking in when cooking. If you open the .nb or .nbh file in a hex editor, you can see the XIP area in the first section of the file.
For instance, using a hex editor, search for the string "ddi.dll" in the .nbh, you will locate it in the XIP section. Again this section is not normally modified during cooking, so when you see it disappear from the temp folder it has not been deleted from the ROM, only from the temporary copy extracted for use in the cooking process.
Furthermore, according to version info, the ddi.dll found in my Fuze XIP is ver. 1.95, as is the ddi.dll in the module you provided from your ROM. (open file S005 in notepad), while the ddi.dll provided in the .cab is 1.90. This doesn't mean it is better or worse, only different, have not looked into the differences.
shafez said:
Now when you start cooking the BuildOS.ex deltes the temp folder and accrodengly also deletes the Dump_XIP folder which was in the temp folder.
Now if you do a search for the DDI.dll, It does not exist anymore.!!
What happend to DDI.dll module?
Regards
Click to expand...
Click to collapse
Da_G are right, DDI.dll is part of XIP, and kitchen is not maked to modify the XIP, only use the XIP from the Shipped NBH file you put in BaseROM.
Anyway, seems your ROM have a CAB to update the DDI.dll file in the customizations, so perhaps a new version...
If you want modify/port the XIP start here http://forum.xda-developers.com/showthread.php?t=438676
Cheers
jcespi2005 said:
Da_G are right, DDI.dll is part of XIP, and kitchen is not maked to modify the XIP, only use the XIP from the Shipped NBH file you put in BaseROM.
Anyway, seems your ROM have a CAB to update the DDI.dll file in the customizations, so perhaps a new version...
If you want modify/port the XIP start here http://forum.xda-developers.com/showthread.php?t=438676
Cheers
Click to expand...
Click to collapse
All clear now,Thank you very much.
Best Regards
Thank you
Da_G said:
It is stored in the XIP, a seperate area of storage outside of the IMGFS, which is the area you are looking in when cooking. If you open the .nb or .nbh file in a hex editor, you can see the XIP area in the first section of the file.
For instance, using a hex editor, search for the string "ddi.dll" in the .nbh, you will locate it in the XIP section. Again this section is not normally modified during cooking, so when you see it disappear from the temp folder it has not been deleted from the ROM, only from the temporary copy extracted for use in the cooking process.
Furthermore, according to version info, the ddi.dll found in my Fuze XIP is ver. 1.95, as is the ddi.dll in the module you provided from your ROM. (open file S005 in notepad), while the ddi.dll provided in the .cab is 1.90. This doesn't mean it is better or worse, only different, have not looked into the differences.
Click to expand...
Click to collapse
Da_G
Forget to say thank you,please forgive me.
Thank you very much
Best Regards
Hey no worries, you got the answer and that's the important part No problemo.
Hello all ,
I'm a happy user of Shep's 6.5 rom.
But i would like to cook rt (remote tracker a antitheft aplication) into the rom.
the rom is protected , so extracting it with a kitchen en recooking doesn't work.
Also tried flashing-> dumping into part0x.raw -> extracting , but also no luck.
so cooks i ask you, is there a way to do this??
thanks , arnold
Hi, yes, far easier would be to ask for a kitchen and use that, but barring that;
You can dump the rom, but do not split it into packages (you will need to manually dump as the kitchen will try to split into packages automatically)
Once dumped you'll have all the files in a single \dump folder.
Now add your files to it, then open default.hv in program CeRegEditor
manually add your registry entries or import them into the registry hive, and save it
now cook the rom (again can't use the kitchen, have to do it manually, since your source is already a single \dump folder)
this will give you the source rom + whatever you added To look at the manual steps you will need to do, look at the .cmd and .bat files in the kitchen.
ok will try that ,
but strange that automatic extracting by the kitchen hangs on "protected rom" and manual it works.....
But hey...your the kitchen master
thanks
Protected roms don't dump correctly in the kitchen because the scripts are designed to work around .dsm files.. and the .dsm files are stripped on a protected rom
You can however still manually dump and get a \dump folder, flat folder with all files (as it is stored in the ROM)
Still possible to work with this folder, however the kitchen(s) are not designed to. As it is more difficult.
okey , got it......
even made myself a little kitchen to dump and rebuild the roms
(will post it later if it works, have to flash my phone to test it)
All files in the dump dir seems to be in the phone's \windows dir...
is there a way to place files in other dir's , or do i have to do this by adding cabs to the config.txt file?
Anyway , thans for the help.
works like a charm..
posted it here : http://forum.xda-developers.com/showthread.php?p=3612337
I have been working on rom development for LG Quantum. I have managed to extract the rom parts and from that, I have a "flash.bin" file which has (contains??) the OS.nb file. The only problem with it is that the flash.bin file has a "RA000F" header in it. HTC Rom Editor opens flash.bin if I rename flash.bin to OS.nb, but crashes when I try to get at files within it. I have tried finding the D000F header within the flash.bin file and extracted OS.nb from there. HTC Rom Editor allows me to extract imgfs.bin from the OS.nb that came from the flash.bin file. If I use the OS.nb taken from flash.bin, I can modify and rebuild the OS.nb with any changes I make, but then I can't reintegrate the changed OS.nb back into flash.bin.
Are there any tools which allow me to work with files with the RA000F header in them? Also, is there any real information (documentation) available on the RA000F rom format? I can't seem to find any real documentation on it.
Can anyone help me?
Please send me link for your rom , i try dump it
WojtasXda said:
Please send me link for your rom , i try dump it
Click to expand...
Click to collapse
Dump with what?
anaheiim said:
Dump with what?
Click to expand...
Click to collapse
Flash.bin from first post