I have been trying to use the new 3.03 ROM to customize one that I like. I have used BuildOS several times before with no problems but today I keep getting two errors.
error 1: has something to do with .dll is in use or is write protected.
error 2: "Kitchen\Vogue6.1_GPS_3.03
Guid should contain 32 digits with 4 dashes (xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx)
What do these errors mean and how can I get passed that?
Related
I tried to dump a certain rom image (nk.nb0) to files for reusing. However, almost all the exe and dll seem to be malfunctioning saying "this is not a valid ce app".
Only a clue I can get is the error messeage called
ERROR: could not find pointer for ofs 00000000
The rom image is probably made by CE4.1 but when I put -4 option the more error messages are coming up. so I can't help but omit -4.
:shock:
[Full messages..]
img 00000000 : hdr=8599c46c base=84000000 commandlineoffset=84000000
ERROR: could not find pointer for ofs 00000000
84000000 - 84000000 L00000000 rom_00 start
84000000 - 84000004 L00000004 romsection id=ea000ea7
84000004 - 84000040 L0000003c NUL
84000040 - 84000048 L00000008 'ECEC' -> 8599c46c
84000048 - 84001000 L00000fb8 NUL
84001000 - 8403e0c8 L0003d0c8 o32 region_0 rva=00001000 vsize=0003d0c8 real=84001000 psize=0003d200 f=60000020 for nk.exe
....
..
.
Hi,
you CANNOT use dumped .dll or .exe files since relocation information was stripped out at ROM generation process. And since the executable code is loaded by loader into RAM (different position than in ROM) you will never be able to use it.
All you can do with dumped .exe .dll is some disassembly.
John
JohnSmith said:
Hi,
you CANNOT use dumped .dll or .exe files since relocation information was stripped out at ROM generation process. And since the executable code is loaded by loader into RAM (different position than in ROM) you will never be able to use it.
All you can do with dumped .exe .dll is some disassembly.
John
Click to expand...
Click to collapse
ummm... I have used .exe's and .dll's from one device's ROM and used them successfully on another after extracting with dumprom.
I would think the issue has to do with the compression. If you have a WinCE 4.1 ROM and use -3, the files will be corrupt. Try loading the .wav's, .bmp's and .htm's in your Windows/Linux applications and see if they run. If not, then you need to use -4 (which means you may need to hack at the offsets).
LD
I am trying to cook my own ExtROM file.
I opened (using ER2003edit) the current 1.72.800, remove some files, add other files, and saved everything.
When I am trying to flash that file I am getting (running HimaUpgradeUt.exe) error 122 - Extended image file checksum error.
How can I fix this error?
I really don't understand what is wrong. All the roms that I create now cannot be created properly. The preconfig wont run, themes wont even apply, and when I try to reflash it with other roms, RUU says unknown version...I had to boot into bootloader to flash it. (without forcing sspl in ruu)
What the heck is happening? I'm cooking the same way i've been cooking (build OS + dutty's nbhtool) I'm getting very frustrated
Which kitchen or base ROM are you using? Need more info of exactly what you are doing!! Does this happen when you flash to official ROMs too?
I've used pandora, hypercore (they are both the same thing really). Both used to work fine, now they no longer work and both gave me the same errors "after" I flashed the rom I made. Here's the outline of the problem:
1) assuming current rom is schaps's 4.01
2) Runs RUU, auto detect fine
3) flash with the rom I made, flash completed, reboot
4) rom doesnt work properly, preconfig doesnt launch at all, tsk doesnt apply properly, and etc
5) run RUU, cant auto detect, "error, rom........."
6) boot to oli 2.10 BL, flash with "any" premade rom
7) repeats #1
The Roms I made were based on ATT's official rom, I've also used vp3g's coz most craps have already been removed.
1) run nbhextract to extract RUU
2) run nbsplit, imgfsfromnb, imgfstonb
3) toss os.nb into hypercore XIP extract, extract XIP
4) put everything into pandora's kitchen (root/ OEM folder, SYS folder, ROM [Os.nb, XIP folder]
5) remove/add stuff, rebuild .dsm if needed
6) run buildOS
7) run createbat
8) run NBtools (left "version as it is", chose hermes100, SuperCID, no ext rom/radio/spl)
9) rom created, then flashed.
I just made a basic rom with pandora. No editing done besides using the oem packages included to make it. Can someone try the rom out and tell me if you are facing the same problem? (Just a bare OS rom)
i.e. after flashing the rom, with active sync connected, RUU gives Error 244 and the only way to reflash it is get into bootloader mode. OR can RUU still work in windows after flashing it?
I need to know if there's something wrong with my bootloader (whether i need to reflash it) or somehow somewhere the kitchen tools that I've been using suddenly just screwed up any help is greatly appreciated
*I only have problems with the roms that I recently created, again, they used to work fine, I have no problems flashing other people's roms*
http://www.sendspace.com/file/3ycn37
I'd delete your HyperCore and Pandora folders and re-extract them from the original downloads to be honest. Whilst I can't think of what might cause the Error 244, I've found myself that after mixing this and that between HyperCore, Pandora and any of the zillions of 'working' folders I've got kicking about I do eventualy end up overwriting something somewhere that needs to be consistent between builds and knacker myself.
I have managed to solve the problem after redumping everything via the original tools. However, I'm still using hypercore kitchen to extract XIP. I no longer use dutty's NBHtool to create the image, I'm not sure if it contributes to the problem, but I'm having great results with nbhgen.
When I'm done cooking my rom, I'll document down everything I know and create my own kitchen.
Matt released a Kitchen with his WM6.1 Naked 9b1 release and it looks inclusive and concise but I am unsure where I should go to find out how to use it.
Lately, I have been reading a lot (WIKI and various threads) on how to cook a ROM and unfortunately, I got lost in all the reading. There seems to be a lot of info out there and I cannot find an updated clear/ concise set of instructions that would apply.
Through my reading, I have tried things like Hypercore (always having problems on the rebuild stage) but then I see this Kitchen released that has everything Apparently I didn't need to spend all that time learning how to extract a ROM and now I am just more confused.
I was wondering if someone could point out a relevant thread or set of instructions that would help me build a ROM from the WM6.1 Naked 9b1 Kitchen. It sounds easy from the way some people talk about it but I had less trouble learning how to pull the motor out of my car from the manual Sorry for my ignorance on this; I am not stupid just inexperienced and in need of direction. I am hoping someone can help and save me hours of reading and learning the hard way. Thanks for your patience and any help.
copied from matt's post:
The Kitchen should reside in a folder on your PC. In that folder you need to have the following:
+++++++++++++++
OEM (collection of folders containing package options, as well as OEMDrivers/OEMApps/OEMMisc/OEMVersion/OEM_Lang_0409 folders and OEM.cer file)
ROM (OS.bn file and the XIP folder)
SYS (collection of operating system folders and an option.xml file)
TOOLS (utilities to build your phone image)
BuildOS.exe (tool to create package dump, preparing for compilation)
CreateROM.bat (script to automate compiling your image)
pkgcommon.dll (module for BuildOS tool)
Readme.txt (readme for kitchen)
temp (dump location after first build with BuildOS)
+++++++++++++++
If you've downloaded the latest kitchen parts and have this, you should be ready to go.
1. Run BuildOS.exe
2. Select the packages you want to install.
3. Click the green arrow in the upper left corner.
4. Once it completes without error, it will say "done" in the lower left corner.
5. Close BuildOS.exe
6. Connect your Phone to the USB cable
*NOTE* Back up your phone, and ensure it has more than 50% battery!!
7. Run CreateROM.bat
8. Follow the prompts.
9. Do a hard reset after it finishes.
10. Enjoy!
Whoops double reply sorry!
Thanks so much! I just caught that link now in Matt's Sig. I wasn't sure if WM6.1 instructions would be the same as WM6 so I guess I never bothered to follow that link.
I didn't see a "Readme.txt" file in the Naked 9B1 Kitchen though; I even downloaded both of the 9B1 Naked Kitchens (w/MSS & w/o) and still no Readme (unless it is hidden good). I went through all the folders and it seems that everything else is there. Now I'll read ahead a bit more and give it a whirl. It does sound too easy though considering all the other info out there on this subject. Thanks a million Venelar!
Thanks Matt also; if your reading this.
yea, i got it just by tinkering...sometimes i get an error when i put too many oem files in there, i think its duplicates, but i'm not sure. I can find out the duplicate when buildos is running, because it tells me the last file processed, and i can do a search of the folder. what gets me is when it errors out before the buildos even starts. the command window comes up then just errors out... this usually happens when i put two complete oem archives in the oem folder.... so i've found just keep it simple with the oems programs and you should have no problems... oh yea when you think its doing nothing, and stuck.... nope its just processing, so don't close the command prompt. so relax and just let it do its thing.
Alright I have post several times else where regarding this issue and nobody wants or can help me with an answer.
I am trying to start how to create,modify roms with Kitchen Version 0.87 in my Linux not in Virtual Box Though I've tried both still dont work.
Ok first I have done everything accordingly including Installing Java in the Terminal to Run Kitchen.
Here are my Errors Reports;
Note: (This Happens On any Rom I put in my Update Folder)
Make sure the ROM is under the original_update folder. The format
may be one of the following:
– A ZIP file for a cooked ROM (e.g. update.zip)
– A ZIP file containing *.img (e.g. rom.zip from shipped ROM)
– boot.img + system.img (e.g. from shipped ROM or Nandroid)
Press Enter to continue
[: 75: 0: unexpected operator
[: 34: DamageControl-3.5-final.zip: unexpected operator
scripts/choose_rom: 73: file_array[1]=DamageControl-3.5-final.zip: not found
[: 73: DamageControl-3.5-final.zip: unexpected operator
Available ROMs:
(1) DamageControl-3.5-final.zip
Enter file number (0 = cancel)[/COLOR]:
Nvm. Missed that line.
fr4nk1yn said:
Nvm. Missed that line.
Click to expand...
Click to collapse
So you don't know either?
Wrong forum.
have you tried a different rom zip, that one could be corrupted or just not work well in the kitchen. I would first try a completely different rom. If it works try to download DC again.
Also look at the scripts folder. The scripts are pretty easy to follow. Try doing the steps out by hand and you will probably get better error messages.
Sent from my PC36100 using Tapatalk
laydros said:
have you tried a different rom zip, that one could be corrupted or just not work well in the kitchen. I would first try a completely different rom. If it works try to download DC again.
Also look at the scripts folder. The scripts are pretty easy to follow. Try doing the steps out by hand and you will probably get better error messages.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Like I said in paragraph I've tried every rom I have witch is about 21 rom's
Post the question here... http://forum.xda-developers.com/showthread.php?t=633246