Related
how to dump the newest 19839 ROM？
i found i can't dump it。can anybody tell me？
thanks
search my friend and it will do you wonders....
http://forum.xda-developers.com/showthread.php?t=379559
in this thread it should show you what you need...
no,this is not the way which can dump the 19839 rom your friend UDk made,and besides they just keep it as a secret and ignore every PM which were sent by the person who would be happy to know the truth.and someone just criticize that the other cookers who just start a "Cooker War" and on the other hand he just make some undumpable Rom as the prove of his selfishness.What a ridiculous phenomena....
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
NikMel said:
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
Click to expand...
Click to collapse
thanks,but the rom is only removes dsm and rgu.if u dump it ,u will find the rom is do something by the owner.
so i want to know it.
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
swtos said:
All roms can be dumped.
Click to expand...
Click to collapse
really do you think what wrote???
ervius said:
really do you think what wrote???
Click to expand...
Click to collapse
what do you mean ?
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
swtos said:
what do you mean ?
Click to expand...
Click to collapse
nothing.... dump it and rebuild.
dcd1182 said:
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
Click to expand...
Click to collapse
rgus and sdms are allways the same from build 19716, same!!!
ervius said:
rgus and sdms are allways the same from build 19716, same!!!
Click to expand...
Click to collapse
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
dcd1182 said:
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
Click to expand...
Click to collapse
yes, dsm contains version, but you solve with my dsm patcher...
and rgu, maybe only 19716 are differents, for me no differences from 19199 and last posted...
I think that microsoft provides us with TRUE SYS 19202 (Mar 24 - April 5 - 2008)....
So, there's no reason to patch dsms... to match a non existing version .....
swtos said:
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
Click to expand...
Click to collapse
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
GPRS said:
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
Click to expand...
Click to collapse
no, he cannot, only who protects roms can.....
@ervius
please can you post dsm's & rgu's that worked with your build ??
thanks.
how protected?and how dump?
anbody tell me?help!
yes, I agree with u. swtos's ROM can be dump but can't be rebuilt. I want to know what's the problem of the ROM.
GPRS said:
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
Click to expand...
Click to collapse
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
hi all..
we all have suffered from one common things while making a rom..
after all your hard work and spending so much time and reading on and on for improvements u encounter this
stuck at smart mobility
so i request all people who faced such problems and have solved them,,plz write here about it..
what u have done..??
what is the cause??
this will easier for lots of people to understand why they have non booting rom..
so afterall i got this solution..
1.Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
byDOTCOMPT
2.if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system.
byTWOPUMPCHUMP
3.recmod ALL modules in your EXT folder
recmod these three folder in sys...browsing, browsingcore, and browsingie
BYTWOPUMPCHUMP
4.ALSO SEE THE ATCHED TXT FILES BY KOKOTAS FOR WHICH FILE TO RECMOD ON PAGE 3
This could be caused by many things.
I suggest you check all last changes you did, which packages/edits etc...
Before I edit my kitchen I always make sure I have a backup incase stuff like this happens so I can refert back.
I recommend editing step by step and not edit to many things at once.
Grtz Leo
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
kokotas said:
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
Click to expand...
Click to collapse
almost done..
ok i made a rom 23544..works like a charmm..
but i just upgrade new build like 23548,49,52
all have non booting issue..
no changes have been made from 23544 build not even new application added..
but no luckk.
checked wince..found xip is ok..
also done recmod but no luck..
so now???
i tell u what i just change build 23544,,i got bootable rom..then just chang build ..48..49
non bootable rom
Try XIP 23544, SYS 23548,49,52.
Maybe a bad XIP source?!
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Laurentius26 said:
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Click to expand...
Click to collapse
but without recmod the kitchen even not building a rom
That's weird, the kitchen should run without recmodding modules.
Maybe you have a conflict in your kitchen where a file is overwriting a module?
saurabh88 said:
but without recmod the kitchen even not building a rom
Click to expand...
Click to collapse
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
twopumpchump said:
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
Click to expand...
Click to collapse
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
Could you post your Build_log.txt here.
-
saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
twopumpchump said:
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
Click to expand...
Click to collapse
yes screen does not dim..
so what is your suggestion??
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
saurabh88 said:
yes screen does not dim..
so what is your suggestion??
Click to expand...
Click to collapse
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
kokotas said:
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
Click to expand...
Click to collapse
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
twopumpchump said:
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
Click to expand...
Click to collapse
ok i will compare them and see.l
saurabh88 said:
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
Click to expand...
Click to collapse
Have you tried the 23554 that I posted (It is in my Rollups folder, link can be found in NRGZ sticky in this forum)
build log of 23554
still stuck at smart mobility,,,here i attached file plz someone look at it and help me...
i have just sorted them through dump sorter..
Saurabh: see also this post by twopumpchump: http://forum.xda-developers.com/showpost.php?p=6032341&postcount=14
Hey everybody,
I'm cooking a WM6.5.x ROM for HTC Touch Pro / Fuze / Raphael (you call it how you like it). I'm using WM build 23699. Everything is fine, that's no problem But I have a question related to the kernel. I have not updated the kernel, so I only have slot 0 and 1. But are there much advances on updating my kernel to the 'native' one? And where can I find it? And how should I do it?
Thanks in advance!
MadMatt
The advantage to have a native 6.5 Kernel is that you will have a more smooth rom because you will not need to recmode any module thrn the standard for having a booting rom (Ntconfig.dll).
I dont know if it does exist for your phone but you must search for it in its thread,you need to search for Nk.exe.Once you will find it just replace it with the old one in OEMXIPKernel.
af974 said:
The advantage to have a native 6.5 Kernel is that you will have a more smooth rom because you will not need to recmode any module thrn the standard for having a booting rom (Ntconfig.dll).
I dont know if it does exist for your phone but you must search for it in its thread,you need to search for Nk.exe.Once you will find it just replace it with the old one in OEMXIPKernel.
Click to expand...
Click to collapse
The NK.exe is the only thing you need? And is it possible that it is the same as the one from the HTC Diamond? (as the only difference between those two is the keyboard)
Yes ,only nk.exe you need and i doubt that Nk.exe from another device should works.
_Madmatt said:
The NK.exe is the only thing you need? And is it possible that it is the same as the one from the HTC Diamond? (as the only difference between those two is the keyboard)
Click to expand...
Click to collapse
af974 said:
Yes ,only nk.exe you need and i doubt that Nk.exe from another device should works.
Click to expand...
Click to collapse
Okay, I'll search for the NK.exe. And OsKitchen will automatically detect that it is a newer kernel than?
If you will replace the old kernel then OsKitchen will does all the process automatically.
_Madmatt said:
Okay, I'll search for the NK.exe. And OsKitchen will automatically detect that it is a newer kernel than?
Click to expand...
Click to collapse
Good lord, update the kernel!!! There's one posted in the native kernel thread.
Here's the one I've been using. I think it's the latest. Just swap it into your xip folder and you'll be good to go. And quit recmodding!!!
Farmer Ted said:
Good lord, update the kernel!!! There's one posted in the native kernel thread.
Here's the one I've been using. I think it's the latest. Just swap it into your xip folder and you'll be good to go. And quit recmodding!!!
Click to expand...
Click to collapse
Thanks, will I need to update OEMDrivers too? Because I read that sometimes that is needed too And will I be able to un-RecMod everything after updating the kernel?
Look for one of Da_G's kitchens (23016 was the last full one). It has the oem. But the drivers are all the same. I use drivers from the Orange/20779 final raphael rom. Convert all the drivers to modules.
Farmer Ted said:
Look for one of Da_G's kitchens (23016 was the last full one). It has the oem. But the drivers are all the same. I use drivers from the Orange/20779 final raphael rom. Convert all the drivers to modules.
Click to expand...
Click to collapse
Didn't understand what you are saying here So I need all the OEM packages execpt the OEMDrivers? The OEM packages I have right now are those from the RUU_Raphael_HTC_WWE_5.05.405.1_R_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship.exe
Are that good ones too? Convert all drivers to modules? What do you mean by this? Convert the OEMDrivers in the OEM tab to EXT packages? (Using osKitchen)
Sorry, all you need is the 20779 or 20771 oem. But if you don't want to dump it yourself, get Da_G's kitchen, which is cleaned up a bit. The drivers aren't 6.5-specific. You should convert them all to modules, though.
Farmer Ted said:
Sorry, all you need is the 20779 or 20771 oem. But if you don't want to dump it yourself, get Da_G's kitchen, which is cleaned up a bit. The drivers aren't 6.5-specific. You should convert them all to modules, though.
Click to expand...
Click to collapse
Allright, if the drivers aren't 6.5 specific, then I can just convert my drivers I have now to EXT-packages?
_Madmatt said:
Allright, if the drivers aren't 6.5 specific, then I can just convert my drivers I have now to EXT-packages?
Click to expand...
Click to collapse
Why convert them to EXT's? Just leave them in your OEM Drivers folder. And convert them to modules.
Farmer Ted said:
Why convert them to EXT's? Just leave them in your OEM Drivers folder. And convert them to modules.
Click to expand...
Click to collapse
Okay. and how do I do that in osKitchen? This is my first kernel update
I don't use that kitchen, but if it doesn't have module creation built-in, get reversemod.exe and manually do the conversion by dragging and dropping the files onto the exe. You should do all the oem driver dll's (they get loaded at startup, anyway, and this will save some virtual memory).
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