E-TEN G500 ROM decode errors - Windows Mobile Development and Hacking General

Hello all.
I have trouble with decoding ROM from ETEN G500.
I grab ROM from device by OSImageTool.exe.
Then i try to decode it to files by "dumprom.exe -5 eten.nbf -d c:\!\! "
Decompress started (decompress some files) and then crashes with next
message:
8c0b8040 - 8c0b804c L0000000c 'ECEC' -> 80221b2c 001e1b2c
8c0b804c - 8df78000 unknown"
Anybody know how i can decompress all ROM ?
Next i try to use "HTC64 Extended ROM Tool" tool
and this tool cant when decodecompress ROM with next message
"Unable to decode ROM file"

Related

XDA tools nearly there but can't understand, any help plse

I have installed jeff summers version of xda tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using XDAtools OSImage but can only Can this only be NB1(windows CE(*.nb1) type files if I try to call this NBF I get the following error:
error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for reading. the system cannot find the file specified.
error opening source bootloader from C:\program files\xdatools\bootloader_v5_15.nb0ea. error opening target device.
Can I dump my device memory into a file called ‘xxxx.NBF’?
2: When I try to upgrade my ROM by:
Start OSImage tool and select source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via programmeA) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory (via programmeA) I always get the following message:
ProgrammeA not found - run with --register error opening target device.
I originally ran the programmeA with --register when first installed.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks John.
If you're trying to burn your original ROM back to the device that shouldn't be a problem. Use the [...] button to locate your .nb1 ROM for the source, and select Device Memory (via Programme A) as your destination.
Have you installed ProgrammeA.exe into the binaries folder of XDATools? That's the only thing I can think of.
Thanks I have tried this but believe the problem is the ProgrammeA file but it is definetly in the binaries folder. I am running win98SE but don't think this should be a problem. When you run jeffs tools it extracts itself out under program files and places all the required files in the right directories. Would appreciate it if any one out there can supply some help ?
Thanks John
I think I know what the problem is...
I have the same problem. If you look at the dos box that pops up you see that programmeA.exe looks in to the \\Binaries\English\ folder for a *.nbf file. It looks like you will have to provide it a *.nbf file in stead of a *.nb1

nbf file of ipaq upgrade

i got nbf file of ipaq upgrade and want to dump it to files.
tried to many way i knew, dumprom, rdmsflsh.pl, but they said
imgfs is not found.
HTC64 Extended rom tool also an error to decode,
do anyone have an idea to
@decode to fat file,
@dump it to files
Help please!

TPEnable.exe question..

I'm trying to cook the latest 1.11.171 Extended ROM from O2 by removing all the O2 stuff...
I can sucessfully update the ms_.nbf file by using the alpine_ext_rom_tool.
The updated ROM downloads ok to the XDA IIi but towards the end of setup I get the following error message 'The file \Extended_ROM\TPEnable.exe is not a valid Windows CE Setup File'.
Clicking on 'ok' the message goes away and the touchpad is enabled??
Any ideas on how to fix this error message?
The best bet is to delete TPDisable.exe and TPEnable.exe files from the ROM and references from the Config.txt file. This will leave more room for other, useful programs. They're not needed.

Problem with "Unable install"

Hey. i have problem
i have LEngsmart (russian languge for smartphone 2003)
i wanna replace file inside CAB file and this i doing without problems
but when i try install it to my smartphone win WM3, they said me "unable to install in this directory".
this CAB package have inside file like: *.mui, *.dat, *.reg and some else.
if i change only *.reg file, then they install propertly, but when i change *.mui file then he cant install this.
what i do wrong?
please help me
ps. i try to rebuild this package and do selfextraction with polish languge
Best greetings from Poland

[HOWTO] Completely restore your device to its original condition (warranty coverage)

FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!​
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Code:
00_GSM.nb
01_IPL.nb
02_SPL.nb
03_MainSplash.bmp
03_MainSplash.nb
04_OS.nb
Copy 02_SPL.nb and 03_MainSplash.nb to C:\HTCRomTool and 04_OS.nb to C:\XIPPORT
ok, now we have official SPL and MainSplash ready to use but we need the OS too
To obtain exactly the original OS we need to modify some registry keys inside "boot.hv" according to our language.
This file is located in the XIP section, so we should extract the xip files from 04_OS.nb, modify boot.hv and re-inject the xip in the os.
Don't worry, we have another solution because we already have the original xip obtained from dump process ([email protected]'s wiki)
The XIP section is Part01.raw
Copy Part01.raw to C:\XIPPORT and rename it to "xip_out.bin"
Run xipport.exe, change the offset to "00313800", the filename to "04_OS.nb" (see pic01 at the end of post for detail) and press "write xip_out.bin to:"
This tool write the xip section (xip_out.bin) in the OS (04_OS.nb) at the specified address (00313800).
Now we have 04_OS.nb with our original XIP
Rename 04_OS.nb to OS.nb and copy it to C:\tadzio
Copy imgfs_raw_data.bin obtained from dump process to C:\tadzio
Open a command prompt, go in C:\tadzio and type this command:
Code:
C:\tadzio>imgfstonb imgfs_raw_data.bin os.nb os-new.nb -bigstoragemove
This tool recostructs the OS (os-new.nb) from our dumped image (imgfs_raw_data.bin)
Now we need to patch the size of OS-new.nb, to do this type this command:
Code:
C:\tadzio>bPatch.exe -1 0xFF 0x632D000 OS-new.nb
The size of patched file must be 99.1 MB (103,993,344 bytes)
Ok, our OS is ready to use!
Copy OS-new.nb to C:\HTCRomTool and run "htcrt.exe"
This tool creates and signes a .nbh file from a .nb file. I suggest you to create 2 .nbh, one for OS and Spalsh (eg. OS.nbh)
and one for SPL (eg. SPL.nbh).
Select "ROM builder" tab and fill the fields like screenshots at the end of post:
OS.nbh (see pic02 for detail)
SPL.nbh (see pic03 for detail)
Press "Build!", type the filename without extension and press "Save"
Flash OS.nbh first so if something wrong in the image and the device don't boot you'll be able to flash any other ROM; while, if it boots ok, then flash the SPL.nbh.
Copy OS.nbh to C:\RomUpdate, rename it to ruu_signed.nbh, run "ROMUpdateUtility.exe" and follow the instructions
At this point we have flashed OS and Splash, if its all ok and the device boot right, then you can flash SPL
Delete ruu_signed.nbh, copy SPL.nbh to C:\RomUpdate, rename it to ruu_signed.nbh and run "ROMUpdateUtility.exe"
That's all!! Now you have completely restored your device to its original condition.
I've tested this procedure, worked fine for me and i hope for you too
.
.
.
bye all
.
.
.
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
avathar behemoth said:
isnt there some way to find out if we can enable wifi in the startup of the os? .. then we know if its in the Pharos or not. whadoyathinkhuh? seems in the Artemis wifi is enabled by the os....
Click to expand...
Click to collapse
i've tried to play around this few time ago with no succes
I've configured wifi interface card throw registry hack, it appears in the network adapter list, but when i turn on wifi nothing happens...
did you use the files i posted in the wifi thread? (posted the tnetw 1251 driver and a file from the extended rom of the artemis... wifinit.exe) but kudos to you for getting a device listed in the pharos (though i looked with task manager i think in a previous rom i flashed and i saw wifi.dll or something loaded at the list of pharos devices)
poldo964 said:
FIRST OF ALL I'M NOT RESPONSABLE OF ANY KIND OF DAMAGE OCCURRED DURING THIS PROCEDURE.
DO IT AT YOUR OWN RISK!​
Ok, go on now
This guide assumes that you have already dumped your original ROM.
For how to dump your ROM, follow [email protected]'s wiki until obtain imgfs_raw_data.bin
What we need:
Official Pharos WWE ROM
tadzio tool (by tadzio)
XIPPORT tool (by bepe)
bPatch (by suracha)
HTC rom tool (by Dark Simpson) with pharos settings added by me
ROM update utility
I suggest you to create a folder for each tool (eg. C:\tadzio C:\XIPPORT C:\HTCRomTool C:\RomUpdate)
and unzip the tools in the respective folders. bPatch.exe is inside tadzio tool.
Download the official rom, right clic on "RUU_Pharos_HTC_WWE-ME_1.11.456.1_4.1.13.59_03.15.90_BLUE_Ship.exe", select "Open with WinRar" and extract RUU_Signed.nbh in "C:\tadzio"
Open a command prompt, go in "C:\tadzio" and type this command:
Code:
C:\tadzio>nbhextract ruu_signed.nbh
this tool extract the content of the .nbh file, if its all ok you should have these files now:
Click to expand...
Click to collapse
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
wittanny said:
Failed to pass this step with this message " 'nbhextract' is not recognized as an internal or external command, operable program or batch file"
This command was not included in your attached tadzio tool.
Click to expand...
Click to collapse
oops! sorry
hi
i have not imgfs_raw_data.bin ????
when i run the romupdateutility i get error "invalid vendor id"
please help
lindows said:
when i run the romupdateutility i get error "invalid vendor id"
please help
Click to expand...
Click to collapse
you need HardSPL to flash a NON official ROM
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
fmulinacci said:
well, actually I went from a Pharos running Poldo v13 (HardSPL Mobiz) to a completely original english Pharos by simply installing Pharos Official English ROM Version 1.11.707.1 (http://forum.xda-developers.com/showthread.php?t=394721).
Now when I boot, everything is original, even the SPL is the original and not the Mobiz anymore.....
Lucky?
Click to expand...
Click to collapse
are you italian?
poldo964 said:
are you italian?
Click to expand...
Click to collapse
yes, why? do I write english so bad ?
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
fmulinacci said:
yes, why? do I write english so bad ?
Click to expand...
Click to collapse
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
by the way, I got a question for you: from your signature now you are using your latest rom and the new radio. I now a lot of people likes your new rom very much, but somebody complains about poor battery lasting. Does this new radio improves battery issue?
Cheers
Click to expand...
Click to collapse
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
poldo964 said:
no no... i mean that you have a WWE ROM now, not italian... When i've bought my pharos there was an ITA ROM inside and this thread explains "how to completely restore your device to its original condition (warranty coverage)" like the title says
cannot confirm this, i'm working with kaiser device now... but you can test by yourself, just flash the old radio and see what happens
cu
Click to expand...
Click to collapse
ok, I got it....however my Pharos was French (a great deal, about 150€ at FNAC in Geneva...I could not let it on the shelf), and I did not back it up before upgrading....let us hope in 1 year nothing bad will happen ;-)
Hi all,
I'm looking for the official french version. Could anyone share it or tell me where i could DL it?
Thanks all.

Categories

Resources