Database Users

SYSVersion 1.2 - Check the actual version of your SYS build.

Hey all, just fired an app together to quickly check the version of your SYS build. Easily check to see if the SYS version which is advertised is legit or not.
pop the exe into the root of your kitchen and run it. Or drag and drop the SYS folder onto the program.
Pass the folder path also if needed: SYSversion.exe <path_to_sys>.
If run with no arguments it will check for the presence of SYS and check the version.
The results will be in "Report.txt" inside the SYS folder being checked.
Enjoy!
http://www.mrvanx.org/files/mvApps/SYSVersion12.7z
ChangeLog:
Code:
1.0: First Release
1.1: Added capability to drag & drop the sys folder onto the program
1.2: Results now show the major/minor versions (ie 5.2.19971, instead of just 19971)

Where exactly does this have to go? Or can it be anywhere in the kitchen?

Good one I guess it checks the dsm values since I found a lot of old builds, but thats just since I used the old dsms to rebuild the dumped 20924

this is my sys\ report.....

ervius said:
this is my sys\ report.....
Click to expand...
Click to collapse
Cool Did you build the version yourself?

evirus, your DSM tool works , but it was not needed to patch .net dsm too
@l3v5y the tool must be in the same folder of the kitchen where the SYS folder is

Hopefully you guys have found this useful, had to dust off the coding cap for this

Beautiful work man!!!

xplode said:
evirus, your DSM tool works , but it was not needed to patch .net dsm too
@l3v5y the tool must be in the same folder of the kitchen where the SYS folder is
Click to expand...
Click to collapse
Thanks for that!

mrvanx said:
Hey all, just fired an app together to quickly check the version of your SYS build. Easily check to see if the SYS version which is advertised is legit or not.
pop the exe into the root of your kitchen and run it. See Report.txt for the results.
Enjoy!
http://www.mrvanx.org/files/mvApps/SYSVersion10.7z
Work to do: Code in the capability of dragging a folder onto the program to check. Hope you find this useful.
Click to expand...
Click to collapse
thanks for that handy tool
will make it much more easy for us to see if port is complete

xplode said:
evirus, your DSM tool works , but it was not needed to patch .net dsm too
@l3v5y the tool must be in the same folder of the kitchen where the SYS folder is
Click to expand...
Click to collapse
yes, you are right, maybe I have to update my tool!!!!! hehehehe!!!!
for mrvanix, maybe you have to extend the analisys, also to "5.2", and to \OEM and .payload too (for xip section!!!), for a complete tool, bwt, great util
bye!!!

awesome tool my friend
thanks for this

Superb tool dear. It reveals lots of hidden informaation..
My falicitations to you bro!

mrvanx said:
Hey all, just fired an app together to quickly check the version of your SYS build. Easily check to see if the SYS version which is advertised is legit or not.
pop the exe into the root of your kitchen and run it. See Report.txt for the results.
Enjoy!
http://www.mrvanx.org/files/mvApps/SYSVersion10.7z
Work to do: Code in the capability of dragging a folder onto the program to check. Hope you find this useful.
Click to expand...
Click to collapse
good tool ,thx

It is a good tool, thank you

Hmm, it seems like I've got to update my kitchen
So thank you for this very convenient tool.
Keep it up, M

Tool updated to 1.1.
Enjoy.

again updated to 1.2

Awesome Job Dude!!

hey bro! in terms of convinience I prefer the way 1.0 works. It leaves the report.txt outside the \SYS which is convinient.. (Again it is my view....)

ervius ROM_Deprotector.....

Hi all, I post this little apps that maybe can help you if you want dump a protected rom (not all, obviously.....) but in some cases it can help.....
how it works:
put a .payload or a .nb file in the same folder of the app, open a command prompt and write:
rom_deprotector os.nb
or
rom_deprotector os.nb.payload
where os.nb / os.nb.payload is the name of your target file.....
wait and finger cross that the target file was protected in a way known by my apps, if my apps "deprotect" the target file, you can dump it then
good lock.....
version 2 a bug on output string solved!

There are a couple different ways to protect a rom. Which method does this one unprotect? imgfs signature mod? file/module header swap?

chavonbravo said:
There are a couple different ways to protect a rom. Which method does this one unprotect? imgfs signature mod? file/module header swap?
Click to expand...
Click to collapse
there are other ways to protect roms, not only theese 2, bwt... it deprotects the 1st one that you told......
so, maybe an old wise will be able to build another "new???" rom.....

haha very nice tool, i am yet to test this out, but it looks very nice. I am going to go out an guess that you and UDK are about 4 steps ahead, and have already been using new ways to protect your roms.
very nice work though once again. you never stop amzing everyone with the work you do.

conflipper said:
haha very nice tool, i am yet to test this out, but it looks very nice. I am going to go out an guess that you and UDK are about 4 steps ahead, and have already been using new ways to protect your roms.
very nice work though once again. you never stop amzing everyone with the work you do.
Click to expand...
Click to collapse
what about???
did it work well???

Maybe I'm doing something wrong, but it doesn't seem to work for me.
I have extracted the nb file out of a nbh file (using NBHextract). Now I try to execute "ROM_Deprotector.exe os.nb" (whereas "os.nb" is the name of my nb file).
But nothing is happening, the command is executed (that means I can type in a new command), but the file stays untouched, and the computer isn't working at all.
What am I doing wrong?

@ervius
Amazing achievement,,,
How can I tell the type of protection added on the rom? Is there a way to find out which rom is capable to be deprotected by your method?
And if you don't mind, I think your tool can be useful as relatively handy to my thread here

johnpatcher said:
Maybe I'm doing something wrong, but it doesn't seem to work for me.
I have extracted the nb file out of a nbh file (using NBHextract). Now I try to execute "ROM_Deprotector.exe os.nb" (whereas "os.nb" is the name of my nb file).
But nothing is happening, the command is executed (that means I can type in a new command), but the file stays untouched, and the computer isn't working at all.
What am I doing wrong?
Click to expand...
Click to collapse
I tested couple of roms and same results keep happening to me.
@ervius,,, would you mind share the details of handling one sample rom as a tutorial to understand this method better?
if my apps "deprotect" the target file, you can dump it then
Click to expand...
Click to collapse
How can i tell if the file got deprotected successfully, and can you explain how you dump it after all?

NOBELOVE said:
I tested couple of roms and same results keep happening to me.
@ervius,,, would you mind share the details of handling one sample rom as a tutorial to understand this method better?
How can i tell if the file got deprotected successfully, and can you explain how you dump it after all?
Click to expand...
Click to collapse
try version 2 attacked to the 1st post!!!!!
to see if it works, try to dump, for example a DIB rom (os.nb), then use deprotector and try to redump it..... to see if rom_deprotector works...
bye!

ervius said:
try version 2 attacked to the 1st post!!!!!
to see if it works, try to dump, for example a DIB rom (os.nb), then use deprotector and try to redump it..... to see if rom_deprotector works...
bye!
Click to expand...
Click to collapse
This rom deprotector doesnt work on my ROMs My ROMs are cooked in your visual kitchen Any ideas ervius?

So am I. The initiative is so great. I had tested with most ROMs out there but didn't have luck at all. Does not matter you use nb or payload.
Hope you find a real way to break it!
hugs
Ameet said:
This rom deprotector doesnt work on my ROMs My ROMs are cooked in your visual kitchen Any ideas ervius?
Click to expand...
Click to collapse

If i rememember right Bepe new kitchen, what ervius is based off, it takes the apps.reg and inserts that into the hives, and so you can not decompile it.
also i think this tool just reconstructs the imgfs start address if a chef decided to mess up the imfgs address.

conflipper said:
If i rememember right Bepe new kitchen, what ervius is based off, it takes the apps.reg and inserts that into the hives, and so you can not decompile it.
also i think this tool just reconstructs the imgfs start address if a chef decided to mess up the imfgs address.
Click to expand...
Click to collapse
yes, you are right!
bepe kitchen produces a dumpable rom, but unusuable to rebuild new roms!
bye!

ervius said:
yes, you are right!
bepe kitchen produces a dumpable rom, but unusuable to rebuild new roms!
bye!
Click to expand...
Click to collapse
Oh ok. Now I get it. So the tool only reverses the protection which is done on the ROM IMGFS header to make it really undumpable. Right? You right about Bepe's kitchen producing dumpable ROMs but due to lack of dumped DSMs & RGUs the ROM is not re-packagable Cool.. Now I get the drift
Mind sharing how to protect the ROM so can be documented in the tutorials?

Used your deprotect tool, it said deprotection done successfully.
But after dumping bepe's rom, all file names, sizes are correct.
Some files, e.g. .lnk files are correct too.
But all .dll and .sys files are all zero padded, and unusable.

if
we provide you with updated ways roms get protected are you up for updateing this sweet little tool?

joshkoss said:
we provide you with updated ways roms get protected are you up for updateing this sweet little tool?
Click to expand...
Click to collapse
sorry for late.....
no, becouse there are a lot of protection, and I don't know all of them... maybe.....
bye!

Dear Ervius
amd NOOB
will this tool will work with ur kitchen build roms. casue when I try to dump ur kitchen's build rom (which is CRACING's wm 6.5 23034 rom) through visual kitchen's build 1.8.1 .. its just build ur kitchen's structure but did nothing with sys, oem and ext folder.. its just resume language as 0000 and dpi as 00
please help me.. I tried ever rom in it. but didnt get result yet

[Q] How to decompile/recompile binary XML from .apk file?

I have an .apk file which containing the new HTC keyboard, and I tried to translate the Russian layout to Hebrew so I'll be able to use any ROM which use this keyboard (I can't find the original Android SK on the ROM).
There is no problem to find the Russian XML files, but it's all compiled to a strange binary XML.. can someone help me with it? is there any way to decompile it to a normal XML again and then recompile it so i'll be able to override the original on my system?
thanks in advance
Avi

You would have to use a hex editor. More helpful information may be found here:
http://forum.xda-developers.com/showthread.php?t=479019

AXMLPrinter2:
http://forum.xda-developers.com/showthread.php?t=514412
Stericson's hex editing tutorial:
http://forum.xda-developers.com/showthread.php?t=479019

Thanks you two
I wish we'll have an app in the future (maybe i'll write one ) that can easly decompile/recompile - just like we have for mode9 files etc.

A problem, I can only decode it to a normal txt file - but I can't recode it back to that binary xml format...
How can I do that?

avimak said:
A problem, I can only decode it to a normal txt file - but I can't recode it back to that binary xml format...
How can I do that?
Click to expand...
Click to collapse
There's a converter in the Android SDK.

jashsu said:
There's a converter in the Android SDK.
Click to expand...
Click to collapse
Which one? there's a lot of them there...

avimak said:
Which one? there's a lot of them there...
Click to expand...
Click to collapse
"aapt dump xmltree" will show the contents but not in actual xml.

cyanogen said:
"aapt dump xmltree" will show the contents but not in actual xml.
Click to expand...
Click to collapse
Hi man, I'm already using AXMLPrinter2.jar to decode the xml file, that's not the problem. I'm looking for a way to recode it back to binary - and jashsu says it's in the SDK, but we have there about 100 different tools so I asked him which one is to recode a simply xml to binary xml that's fits Android
do you know?

Hey Avi,
why don't you use the hebrew keyboard that already published in iandroid.co.il forums?

zrubi said:
Hey Avi,
why don't you use the hebrew keyboard that already published in iandroid.co.il forums?
Click to expand...
Click to collapse
Well, first of all I'm using it now and it's great.. but still the HTC official keyboard looks bigger and wider for me, plus there is a space there (in the Russian layout) for question mark etc...

[FYI] Metadata.cif & Metadata.sof PKGS info

AndrewSh said:
23668 AKU 5307 Windows CE: 5.2 Build 4585 (June 17 2010. 16:05:08)
23668_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409.7z (38.98 MB)
http://www.multiupload.com/BRBSUQU4QD
http://multi-up.com/299136
Re-uploaded by Alexx~
Click to expand...
Click to collapse
Wow! Tried it and seems sooooo faster respect to 23667. My I8000 has increased performances as never before. Now SPB MS carousel is really responsive!
I noticed a lot of changes between 23667 and 23668. Any idea?
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.

fubo73 said:
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
Click to expand...
Click to collapse
Metadata package is the all the registry entries, gathered together into one place.

utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
Are you saying it is built during cooking? If not, why I did not find it in packages so often?

utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.

AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
can you please tell us how to edit/adjust packages.cif/packages.sof?

HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)

AndrewSh said:
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
Click to expand...
Click to collapse
thanks alot. is there a english version of this tool available?

HD2Owner, English version is a part of Barin's OSBuilder (which I use as a rom kitchen)
The English discussion and public downloadable release is here

Mmmm interesting I heard itbefore an effectively from you Andrew lets make it important here cause neither me use it... Thanks a lot

Just to make it more understandable - screenshots from packages cif and sof editor from OSBuilder tool

Barin is now on vacation and I have no contact with it, but I hope he will forgive me.
I translated pSofCifBuilder to English.
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck

Alexx~ said:
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Click to expand...
Click to collapse
Yea I am starting to like that OSBuilder now...

AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.

!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.

!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
Farmer Ted said:
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
Click to expand...
Click to collapse
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.

cnzqy1 said:
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
Click to expand...
Click to collapse
as i said i never ever modified them, that means it doesnt even matter with Build OS. moreover, using "all packages to one" technique strips most of the info from these files without even affecting the ROM.

In this order, which is specified in packages.sof will be building registry. It is not related to PRB, or OSB, or any other kitchen.
Building registry does rgucomp (default.hv, user.hv and boot.hv) on the list of packages (dsm) from packages.sof
It has always been, regardless of whether old or new kitchen. So no other way.
Further deletion of files dsm ("all packages to one", etc.), nothing to do with the building registry.
P.S. There is a myth that OSB is important packages.sof, and at for other kitchens, it is not needed. This is nonsense. In OSB can view and edit packages.sof and packages.cif. That's all the difference.

well, my point is just that registry is added into the hives even if package has not been mentioned in packages.sof, so why bother editing it?

It is important that packets from the SYS and from OEM (which can be attributed to the group OEMDrivers) were formed in the order of packages.sof. The rest you can adjust with the names (dsm or package, depending on the kitchen).
If you think that the roster of SYS formed not so - you are mistaken.
As an example, you might see messages about the problem of "blank page" in IE.

trust me, i've never modified that file. i always use it without editing, from whichever source i get it. i'm not saying it is useless, but in most cases we don't need to edit this file

How to disable auto time synchororization in kitchen

hi every body
can someone please give me some advice .i want to disable auto time synchronization before cooking the leo rom.can you please tell me how can i do this.thanks.and i wish you all very happy new year.

Code:
;disable auto time sync
[HKEY_LOCAL_MACHINE\Software\HTC\TimeZoneAutoFix]
"CreatePDPAlways"=dword:00000002
"WarnAlways"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\Clock]
"HomeDST"=dword:00000000
"AutoDST"=dword:00000000
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"NITZEnable"=dword:00000000

HD2Owner said:
Code:
;disable auto time sync
[HKEY_LOCAL_MACHINE\Software\HTC\TimeZoneAutoFix]
"CreatePDPAlways"=dword:00000002
"WarnAlways"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\Clock]
"HomeDST"=dword:00000000
"AutoDST"=dword:00000000
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
"NITZEnable"=dword:00000000
Click to expand...
Click to collapse
thanks for reply .where is this in os kitchen please?

master92 said:
thanks for reply .where is this in os kitchen please?
Click to expand...
Click to collapse
Try opening all the reg files in your kitchen and look... You might learn a couple of new things as well if you do that!

ai6908 said:
Try opening all the reg files in your kitchen and look... You might learn a couple of new things as well if you do that!
Click to expand...
Click to collapse
Yup, that works. Also, just use Kheb 1.1 to find registry keys. It's faster and easier than either searching or starting a new thread.
The key is probably in the oem drivers rgu, and it may appear several times.

i swithed to osbuilder lately.
there is a option inside called registry preview.
if you expand the three and select the key you're searching for, it shows wich rgu-files are editing the selected key. very easy. best kitchen i ever used to cook roms.
i already solved some order problems this way. just to let you know.
the keys i wrote about should be simply added as last package after all xip/sys/oem (overwrite any other rgu values).

HD2Owner said:
i swithed to osbuilder lately.
there is a option inside called registry preview.
if you expand the three and select the key you're searching for, it shows wich rgu-files are editing the selected key. very easy. best kitchen i ever used to cook roms.
i already solved some order problems this way. just to let you know.
the keys i wrote about should be simply added as last package after all xip/sys/oem (overwrite any other rgu values).
Click to expand...
Click to collapse
hi thanks for reply can you please tell me where can i download this kitchen, and is it for leo.

master92 said:
hi thanks for reply can you please tell me where can i download this kitchen, and is it for leo.
Click to expand...
Click to collapse
You can make it work for leo.
http://www.mobileunderground.info/showthread.php?t=12348