Related
Hi!
I was wondering if the WM5 Rom editing tools still work with a WM6 Rom, I was trying to add some dll's to the WM6 rom to make it work on my Prophet (Sound dll is wrong). I first umpacked the rom with prepare_imgfs.exe then viewimgfs.exe I replaced the files in the dump directory and then tried to repacked with buildimgfs.exe but it displays one line of junk on the commandline and that's it. So the questions are:
1. Can the Rom editing tools be used on a WM6 Rom
2. What orther options are there to change files in a not flashed .nba file?
Thanks,
Ramon
ok how did you get that to work, cus i was trying it and the folder Dump was not getting made!!! i tried it so many time!
I don't have any problems at all... Everything works just the way it did with wm5...
extract OS.nb from nk.nbf using: typho5.exe -x nk.nbf
prepare_imgfs.exe OS.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs.exe OS.nb -nosplit
-----------------------
replace OS.nb with the name of the OS part.
do not forget the -nosplit option in prepare_imgfs and in make_imgfs.
bye
Just to clarify, I'm using
Code:
typhoonnbfdecode to get 80040000-OS.nb
prepare_imgfs 80040000-OS.nb -nosplit
viewimgfs imgfs_raw_data.bin
make the changes without removing any of the files created in the dumping process then
Code:
buildimgfs
make_imgfs 80040000-OS.nb -nosplit
after that use nb2nbf_tornado to make a new nk.nbf
_Nomad_ said:
Just to clarify, I'm using
Code:
typhoonnbfdecode to get 80040000-OS.nb
prepare_imgfs 80040000-OS.nb -nosplit
viewimgfs imgfs_raw_data.bin
make the changes without removing any of the files created in the dumping process then
Code:
buildimgfs
make_imgfs 80040000-OS.nb -nosplit
after that use nb2nbf_tornado to make a new nk.nbf
Click to expand...
Click to collapse
I'm doing the exact same thing, but at this step:
make_imgfs 80040000-OS.nb -nosplit
It goes wrong it fails without an error message..
What exact file are you trying to integrate in the rom? is it a module?
btw. you never get an error message
_Nomad_ said:
What exact file are you trying to integrate in the rom? is it a module?
Click to expand...
Click to collapse
Well I don't think it matters, because I also tried a makeimgfs and changed nothing.. no files.. but the file I want to change is "wavedev.dll"
Solved it!
I though the last step:
make_imgfs.exe nk.nbf -nosplit
But it had to be make_imgfs.exe 80040000-OS.nb -nosplit
I thought it was just going to create a new file..
That's odd... before rebuilding you didn't remove any files did you? such as imgfs_raw_data.bin?
rvbcrs said:
Solved it!
I though the last step:
make_imgfs.exe nk.nbf -nosplit
But it had to be make_imgfs.exe 80040000-OS.nb -nosplit
I thought it was just going to create a new file..
Click to expand...
Click to collapse
Naa, no new file... the old one is used as a template...
Great to see you solved it
Good luck with the rest...
Just learning a bit of ROM-cooking atm. Got a little problem, hope someone can help me get further:
When I add files to the "dump" dir and try running "BuildImgfs.exe" it lists the files nicely, but "imgfs_raw_data.bin" doesn't change date or time, nor does it change size.
What am I doing wrong?
vippie said:
Just learning a bit of ROM-cooking atm. Got a little problem, hope someone can help me get further:
When I add files to the "dump" dir and try running "BuildImgfs.exe" it lists the files nicely, but "imgfs_raw_data.bin" doesn't change date or time, nor does it change size.
What am I doing wrong?
Click to expand...
Click to collapse
It's NORMAL, go on. I don't know why the date doesn't change, i was confused too the first time i cooked a rom, but i can say it's completely normal.
Thank you Risidoro for the fast response.
is it possible to cook wm6 rom for G4 locked devices? thanks
risidoro said:
extract OS.nb from nk.nbf using: typho5.exe -x nk.nbf
prepare_imgfs.exe OS.nb -nosplit
viewimgfs.exe imgfs_raw_data.bin
...modify "dump" directory as you need...
BuildImgfs.exe
make_imgfs.exe OS.nb -nosplit
-----------------------
replace OS.nb with the name of the OS part.
do not forget the -nosplit option in prepare_imgfs and in make_imgfs.
bye
Click to expand...
Click to collapse
Thank you you are a star, i have it working now!!! the auto thing that was made does not work!!!
funman said:
Thank you you are a star, i have it working now!!! the auto thing that was made does not work!!!
Click to expand...
Click to collapse
the autothing?!? Where is it? I've never heard of it!
BTW: i'm happy you succeeded in cooking your first(?) rom! Happy cooking!
bye
risidoro said:
the autothing?!? Where is it? I've never heard of it!
BTW: i'm happy you succeeded in cooking your first(?) rom! Happy cooking!
bye
Click to expand...
Click to collapse
I forgot to thank you too risidoro You really helped me out here! I suceded to cook my first rom hehehe.. nothing special some extra files.. but still hehe.. Now I like to know how I can change registry settings, do I have to change them from the extended_rom or is there a way to do it in the ROM?
Thanks again to all who helped out!
rvbcrs said:
I forgot to thank you too risidoro You really helped me out here! I suceded to cook my first rom hehehe.. nothing special some extra files.. but still hehe.. Now I like to know how I can change registry settings, do I have to change them from the extended_rom or is there a way to do it in the ROM?
Thanks again to all who helped out!
Click to expand...
Click to collapse
Now you need to learn how to create cabs and autorun them from ext_rom. That's what does all that AFAIK. Chefs -- is there any other way? Can you modify the seed hives directly?
I would like to know how to modify the hives too. I saw a tutorial somewhere, but I can't find it now.
Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
thank you.
thaihugo said:
Hi,
let's keep the rom development topic in here. Here is my romkitchen, from kaiserkitchen 0.3. There is no flash utility, but you can use customruu for that.
The included rom is a base for localisation, or customisation. Click on first step (prepare), make your changes, then click on step 2 (cook). You have a Signed_RUU ready for flashing.
In my experience, it is best to delete the RUU_Signed before creating a new one
Also, the custom ruu will not flash the new rom if you do not change the folder between each flashing on vista. I use a name identation (folder1 then folder2, etc...)
Happy cooking. Please use this to help finding stuff about drivers
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi
Thank you very much.
Ram
Thank you for your hard work and dedication we put it. Best regards
thaihugo said:
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
davidgreen said:
you mean that we have to extract sys folder from RUU_Signed.nbh file... then execute greloc and take note of the value... then copy files in the sys folder like OEMAPPS and OEMDrivers... and when we finish adding files in the sys folder... before we execute cook process and NBHutils we have to run the greloc again and reinsert the previous values... then click doit! in the greloc?
Click to expand...
Click to collapse
Make sure you keep your langugage specific folders intact.
Thanks
Ram
G'Reloc Situation
thaihugo said:
Hi,
Warning: you cannot add or remove from sys folder without doing a greloc. DO it before doing anything. Notge the value, then relaunch it when you added or removed something. Put back previous value then click on go!
http://rapidshare.com/files/142122071/shiftkitchen.rar.html
Click to expand...
Click to collapse
Hi thaihugo
My G'Reloc posts the same numbers always before and after, and strangely they are same for kaiser and SnapVUE. Am I doing anything wrong there?
Slot 0: 01F90000
Slot 1: 03DD0000
Size of ROM: 83400000
Unknown: 00000000
These are the numbers I have seen in ImageInfo.txt under .VM folder in SYS
Thanks
Ram
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
thaihugo said:
Most of the time, greloc sees the same numbers, but is needed for the few DLL's you have added. So even if you (as me) get the same number everytime, just run it to make sure everything is in place.
If you put say a full sys from another device, you will get slightly different numbers. You will have to put back the value you posted here in that case.
Morality: If you add any dll folder or exe folder in the SYS folder (not a simple dll or exe), do a preventive g'reloc before cooking.
Click to expand...
Click to collapse
oh. Thank you
Ram
Help needed...
After all...i decided to cook my own rom...
Read alot , did everything i have read...
"cab oem" ing
"initflashfiles.dat" modification
but when it came to the end , buildos gives an error such as
The target file "temp\dump\mstscax.dll is a directory not a file"
Mind do wake me up for what i am missing ?
Safak
Help #2 for the noob
I have found out the problem about the previous tab... It was about wrong configuration of Remote Desktop...
I have overcome it but came a new one which is
Buildos gives this error
"Error building default.hv and user.hv"
and now , what ?
Help this poor lamer :-(
eh...
I ignored the latest error and have my own rom...and i m now flashing it to my Shift...
Will let yo know whn done...to be honest i m a little nervous about the result...
Urgent Help
I m in deep trouble...
I messed everything and now i m dead...Winmo side does not even boot...tell me what to do...tell me if there is a way to go back ?!?
how about flashing working rom to it?
omg
Recovered....thanks alot for your patience...
Average Joe
Hi guys,
I recently bought a HTC shift which SnapVue came out to be in Chinese, i really need to change the language and liberate it ASAP. I 've read so many replies on many different threads that i'm just completely confused right now. I barely understand all the technical words used out here. I need help please. Thank you.
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
gullum said:
What is the max size the rom can be?
I'm getting my Shift this week and I'm prepering for it with a cooked rom
EDIT: I saw that UDK's rom was 64mb in size so I know I'm safe if I'm within that limit
Click to expand...
Click to collapse
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
thaihugo said:
Welcome Gullum.
64mb is the limit IMHO. Some NBH files over 50 mb have problems, and I have to reduce them.
Click to expand...
Click to collapse
ok first problem now ... I made my first atempt to flash a rom and now snap vue only gives a black screen what to do now?
edit maybe it should be added to first post that to recover from bad cooked flash then just flast the included rom
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
gullum said:
I now have a working own cooked rom on my shift just need to do some finetuning and I'll upload a rom for everyone to try... next step is to port a newer build.
i'm typing this on my snapvue side of my **** with opera mini
I have added some apps from blakstone and opal
google maps, rsshub, streaming media, calculator skined, thumbcal and some more
Click to expand...
Click to collapse
Hi
Can't wait. Could you check whether you are able to attach to audio to notes etc.
Thanks
Ram
Before i get flammed like crazy. I have searched for guides to cooking roms and used all different kinds of kitchens but none seem to work at all. Unless there is something written between the lines that i can't see i just don't think i'm doing anything wrong.
Anyway. When I try an build a rom and create the os-new.nb file imgfsfromdump just crashes and i can't create the file. Sometimes it works but once it fails it doesn't start working for a long time. I'm not sure what i'm doing. I try and dumb a stock rom and rebuild exactly the same but the same thing happens.
If anyone with some xip|sys porting could give me a hand to get past this step i'd appreciate it.
Thanks..
I'm starting to believe it might be a conflict with SP3. Can anyone confirm that they have these kitchens working with SP3?
replace your ImgfsFromDump with the attached version
itje said:
replace your ImgfsFromDump with the attached version
Click to expand...
Click to collapse
Thanks itje. I tried this but it still crashes everytime i try and compile the files. I'm not sure why. Is there something i could be doing wrong? Have you seen this before?
Did ImgfsFromDump ever work for you? (That is, did you try just extract and create the image without modify any content)
For me, I am not following the script in the kitchen completely to create the image. Here is what I execute on the temp directory (w/ dump as sub-directory) and work fine so far. (just make sure you did not remove the imgfs.bin and the payload in extracting the image)
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Strangly enough it did work a couple of times then i just started getting that error that says "imgfsfromdump needs to close" that basic windows error. I thought it might have been DEP but i made a exception for that program. I'm going to try this and see if i have the same problems.
I'M SUCH AND IDIOT!!! The reason it was crashing is cause i kept building the dump into packages. So i assume it was looking for files in the wrong place which just causes the process to fail. Thanks guys!!!
Can someone help me find this 21109 build to where i can actuallyt port it? I've tried to extract it from various roms and all it does is fail everytime and my phone is stuck at the sony screen.
*******EDIT******
I finally figured out how to get XIP ported but now i'm having a problem with the SYS folder. No matter what SYS folder i use and no matter how many different tutorials i go through i still get the same point. I flash and it sits at the sony ericisson symbol and does nothing. Is there some folders i shouldn't change in the SYS?
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
itje said:
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
Click to expand...
Click to collapse
When i run g reloc i get the same values as i did with the original build. Let me see if i understand the file hierarchy correctly.
1. I run G'reloc where i have my stock ROM's SYS folde. (note those values)
2. then i run G'reloc where my Donor SYS folder with the rest of the crap from the Donor ROM.
3.Then i copy the Donor SYS folder into the location i have my stock ROM SYS folder and overwrite. I run G'reloc again if the information is different from the first time i ran g'reloc i change it and hit do it.
Is this what i should be doing? I do this and i get the same result no matter which ROM i try and port from. I am porting from a touch pro ROM so is there anything i would need to change due to the vga to wvga switch?
swap from the modules marked with red to blue
base_dpi_192_resh_480_resv_640
to
base_dpi_192_resh_480_resv_800
since our device is WVGA you need to have the value set to 800 instead og 640.
So swap the folders with 640 from donor rom to the ones from either blackstone or x1
I can't get anything to work... If i extract the xip from this 21109 build that i have and try an use xipporterex to create the new xip and write it into the os.nb.payload and then merge the files. If i take that os.nb that is created i can build that and it will boot but if i try use the rom build procedure where it makes the os-new.nb file it will never boot. Even if i do nothing but just extract and rebuild the rom will not boot. From this i assume that i'm doing something wrong, 21109 build is corrupted or both. I'm not this inept. This shouldn't be giving me this much trouble with all these tutorials. Can someone please help me out with the exact procedure they use when building an X1 rom with porting over a new build?
I am currently trying to port the sys 21728 of a wm 6.5 rom to my Karmba kitchen. I used 2 diffrent wikis:
http://forum.xda-developers.com/showthread.php?t=389772
http://forum.xda-developers.com/showthread.php?t=437264
Boths ways do not work. After flashing the device does not boot and stops at the radio screen. The WinCENLS_WWE is in the xip folder.
- dnsapi.dll I deleted from the "OS" folder, cause it is also in the "OEMDriver" folder.
- taskmrg.exe I deleted from the "Shell" folder, cause it is also in the "OEM" folder.
The xip is ported to 21728 and seems to work...the device works with the old sys.
Any ideas?
really no idea?
Try the newer ervius kitchen posted here, already updated to 21812
http://forum.xda-developers.com/showthread.php?t=515824
Hello everybody,
I need some help with porting Blackstone Stock Rom Europe 1.56 to Leo Stock Rom 1.43.479.2.
I'm using Ervius Visual Kitchen 1.8.1. The problem appears when i'm trying to port the sys folder.
I did the following:
I made 2 kitchens donor and blackstone. I extracted .nbh files in both kitchen using "Dump NBH/NB/Payload" option.
I copyed folder 21864 from donor ext\LEO\21864 to blackstone kitchen in ext\BlackStone\21864 and selected in ervius kitchen this ext version. I build the rom and it boots up ok...
After this I moved the sys folder from donor kitchen sys\21864 to blackstone kitchen sys\21864.
I ported also xip.bin by copying xip.bin from donor kitchen ROM\xip.bin to blackstone Tools\xip.bin_new then i pressed "Xipporterex & ROM". I checked "Is an AKU 5..." unchecked "Execute Cert Patch", "Execute PP Patcher" and "Change PP to 16 Mb". I clicked on Port It, all went ok. Then i clicked "Find first..." then "Write it". No error. Then "Rom Tools" -> Write & Done.
Then i tried to create rom again selecting all system xip and ext vs 21864. All went Ok but the phone doesn't boot.
What i did wrong. Please help.
Hi fiftyz,
Use this "OEMXipKernel.zip" in attachment as replacement for yours, it's changed to handle 6.5.
If you don't use it, you must recmod several files/folders in the SYS folder.
Better you do some search and reading
sparkienl said:
Hi fiftyz,
Use this "OEMXipKernel.zip" in attachment as replacement for yours, it's changed to handle 6.5.
If you don't use it, you must recmod several files/folders in the SYS folder.
Better you do some search and reading
Click to expand...
Click to collapse
Thank you! I'll try this way.
I did a lot of research before posting here... Maybe i didn't see that part... Sorry and thank's again. I tought that option "Is AKU 5..." from ervius kitchen will solve that part because it creates that folder when porting xip.
I'll post if it is working.
Did you have success with the solution provided by sparkienl?
I tried to build a ROM the same way as you but with also with the same result -> no boot.
I tried also to build up a ROM with the fix from sparkienl, but I got an error in the ervius kitchen during the build phase.
Does anyone have other suggestions?
Did you check the option "real WM6.5 AKU" ?
Yes, I did.
At what point does the ROM stop booting?
maybe is Notification_Enhancement ,I change it with Notification_Enhancement 3_0_1919_3829
EpiphanyNL said:
At what point does the ROM stop booting?
Click to expand...
Click to collapse
it stops on the "smart mobility" screen, before the information (radio, rom, ...) in the right lower corner appears.
You didnt port you XIP correctly