Error 122 in my own cooked ExtROM file - Upgrading, Modifying and Unlocking

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?

Related

"this is not a valid ce app".

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

Universal upgrading to Jasjar ROM (sorry for wrong crosspost

Hi!
Trying to figure out how to upgrade but I am missing something.
I downloaded the file JASJAR_WWE_11353_137_10301.EXE.
When I run it it gives me a country ID Error 120
Following other posts I downloaded the file MaUpgradeUt_noID.exe which gives me the error missing run.dll.
In another post it says to put the MaUpgradeUt_noID.exe in the same directory of the JASJAR_WWE_11353_137_10301.EXE.
BUT THE JASJAR_WWE_11353_137_10301.EXE DOES NOT CREATE ANY FILE NOR DIRECTORY.
WHERE THE HELL ARE THOSE EXTRACTED FILES???
P.S. What a nightmare.
Re: Universal upgrading to Jasjar ROM (sorry for wrong cross
claudioita said:
Hi!
Trying to figure out how to upgrade but I am missing something.
I downloaded the file JASJAR_WWE_11353_137_10301.EXE.
When I run it it gives me a country ID Error 120
Following other posts I downloaded the file MaUpgradeUt_noID.exe which gives me the error missing run.dll.
In another post it says to put the MaUpgradeUt_noID.exe in the same directory of the JASJAR_WWE_11353_137_10301.EXE.
BUT THE JASJAR_WWE_11353_137_10301.EXE DOES NOT CREATE ANY FILE NOR DIRECTORY.
WHERE THE HELL ARE THOSE EXTRACTED FILES???
P.S. What a nightmare.
Click to expand...
Click to collapse
You can use winzip to unpack the .exe..... and stop swearing.

ERROR in new orange ROm

I have downloaded at least 6 copies of lates rom from orange site but whenever I try to upgrade my imate it shows error
upon extraction of ROM (nk.nbf is extracted only 15.2MB Vs actual 63MB)and shows integrity error
Upon direct run give error on (self integrity check) and says it is a corrupt version of exe file.
Can anybody help me to resolve the issue
Are you running the whole .exe file as it is downloaded?
Have you tried extracting the .exe file first to see if the file sizes are correct?
If there is still a problem try downloading from xda-developers ftp I think some one has uploaded it to there.
Yes i did the same thing after getting error and then ultimately downloaded xda ftp version and observed
this is the correct version

Official WM6 Invalid vender ID...

I tried to install the 838Pro_HK_ENG_WM6_Upgrade_20070712.zip and got
an Error...
ERROR [294] : INVALID VENDER ID
Any help?
hi, would u mind sharing your file with all of us?
by mirroring, or BT?
thanks in advance.
Got it from the rapidesharelink.
Update worked with the RUUWrapper.exe from Schaps (extractet from the exe with winrar)
1: extract the official exe with winrar
2: extract the RUU_Inside.exe
3: copy the nbh file in the directory of your choice
4: extract the RUUWrapper.exe from schaps
5: put the RUUWrapper.exe in the same directory as the nbh file
6: start and enjoy
Ah... I saw it.
To your question:
Which variant of Hermes are you using?
Do you have SPL v2.10?
See my previous post.
My Update ist in progress.
21%

Weird OS.NB extracted?

Hello, I've tried extracting imgfs.bin from LG WM 6.5 firmware, and it results in some weird way.
The points I'm curious at are:
1. Unpacking .KDZ results in *.wdb, not .DZ.
2. Unpacking *.wdb results in weird binary file, not in .tot
3. Resulted binary file seems to be in Qualcomm .MBN format, but there seems to be almost no details within it. Are there any docs about this format?
4. I've tried using osnbtool (with -sp option), then it failed with this message: Can not find OS image! So I've searched it for a bit, then found that I have to rip off all the LG-specific regions to work. So I ripped those off (with custom unyaffsmbn), tried osnbtool again then it worked.
LU210927_00.bin.new.PRE written.
LU210927_00.bin.new.OS.NB written.
Now I get these two, so I tried nbImageTool on OS.NB generated. It extracted imgfs.bin, but seems like it is corrupted... Did I miss something?
Here is the link to the extracted OS.NB: https://drive.google.com/file/d/1vPHWbiHproO_bs09WASc8YreWNaJVrZr/view?usp=sharing
And here is the link to the original firmware (kdz): https://drive.google.com/file/d/1YknA0mg27YfaGEHr10XJ1k8ztgw_V3fA/view?usp=sharing
Thanks a lot!

Categories

Resources