Hi guys,
a new version of ER2003Edit is available from the wiki page:
http://wiki.xda-developers.com/wiki/ER2003Edit
New features and improvements:
- provides support for the new upgrade tool version (0.9.1.0) used by the latest T-Mobile and O2 updates
- supports editing of the header information (DeviceID, Operator and Language) in order to circumvent the country code error
- some other fixes and improvements
Best regards,
softworkz
Thnx dude! At last we got a program to modify the header. I guess this makes a lot of XDA owners very happy.
Great work!
Late...
Thanks Softworkz, great work again. It really looks like an even more powerful tool, but there seems to be a little bug (or I am doing something wrong):
After upgrading ER2003Edit to the new version, I cannot open the ms_.nbf anymore. When I try to open the file, ER2003Edit always crashes, although I left the file unbmodified.
Downgraded to the old version again and there it works, although I have to decode and encode the files by myself.
Any suggestions?
No problems opening the ms_.nbf here after doing the upgrade. Running Win XP sp1.
Try uninstalling the old one completely then install the new one...
Works great!
Late...
is it a misunderstanding between header-information and encryping ???
I think Er2003edit does not do the encryption/decryption so far.
Hey Softworkz...
this would be a great improvement as I guess all coming
extended roms will be encrypted.
Alex
Tried uninstalling and re-install but that didn't help. As far as I remember, Softworkz tool is not able to edit encrypted ms_.nbf.
But on my machine (Win XP pro 2002 SP1) the program always crashes when opening an non-encrypted ms_.nbf...
I will use the old one as a workaround, I don't need to change the header so this should be fine.
some programming tips:
It should not be very difficult to implement the xor decryption, just xor each DWORD in the file with 0x25863614 after loading it in memory, and before saving it back to the file.
also, if you verify the header checksum after loading the file, you should be able to detect that the file you are loading is actually a decrypted nbf file.
and another check to see if at offset 0x70040 there is a valid bootsector, with
the 'MSWIN4.1' and 'FAT16' strings should prevent it from crashing on invalid files.
Ouch, I just found out that the wrong version of xda2tools.dll was included with the setup. I have made available a new version (1.2.20) to fix this. (see wiki page)
Some details about ER2003Edit:
You do not need to uninstall old versions before installing newer ER2003Edit versions.
The new version (1.2.x) is able to perform XOR-De-/Encryption. When opening an extended ROM file ER2003Edit first checks if it is encrypted by looking for the presence of the dashes in the header.
If those are present in the right places ER2003Edit opens the file as usual. If the dashes are absent ER2003Edit tries to decrypt with all of the three XOR-Passwords (). If none of those passwords produces a file with a correct header a prompt is shown which lets you enter your own password.
The decrypted (or a copy of the unencrypted) ROM file is saved to the temp folder. When saving with ER2003Edit the file is encrypted again (in case the original file was encrypted) and is saved to the original location overwriting the initial file.
Itsme: The "dash-check" was used because the CRC-check in your code was always true (didn't look into it further).
The new version supports auto-detection of the ROM type in order to edit the header of the other 2 ROM files (NK and Radio_), too. The "error accessing image files" message is now suppressed for these files.
Nevertheless modifying the header of those files is useless and I didn't figure out how to access the file structure in those files (doesn't look like a FAT image).
Best regards,
softworks
Okay, that explains the problems I experienced. As soon as I am back home I will give it a try. If it works it will be a nice & powerful tool...
==> seems to work perfectly. So there are no more obstacles. Next stage will be an Upgrade to 1.66.xx... :shock:
ok, now it works.
currently, a non-matching crc value only results in a printed warning, maybe I/you could add an extra parameter to the file processing functions, which get the result of the crc-check.
or maybe even better, raise an exception, for the warnings.
ER2003 crashes opening new O2 extended ROM Files
Hi softworkz,
first off all thanks for your great work!
Using the new version of er2003 i cant open the ms_.nbf file of the latest O2 upgrade (1.60.52). It crashes every time. Opening and editing my self created ext. ROM based on T-Mobile Update 1.60.07 works great.
Whats wrong with my installation? If you wish i can send u my Win XP error report.
Escargotet
Sorry for posting, was 2 stupid to read forum first!
Sorry for posting, was 2 stupid to read forum first!
Hi all
Please help to clarify as there are some inconsistances...
(or I am wrong, but will run into this problem)
Er2003edit will try to modify the header information in the NK and Radio_mbf but this will not be successfull and I still will get the Country ID error, is that right ???
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
So there is a missing link...
Alex
itsme said:
ok, now it works.
currently, a non-matching crc value only results in a printed warning, maybe I/you could add an extra parameter to the file processing functions, which get the result of the crc-check.
or maybe even better, raise an exception, for the warnings.
Click to expand...
Click to collapse
The CRC check does not work in your code. XORing with a wrong password results in the following message:
WARNING: this does not look like a nbf header, possible you provided the wrong password
But this gets printed as a result of the "dash-check". If the crc-check would fail, a different message would be printed:
WARNING: checksum is not ok, possibly you provided the wrong password
But this message never gets printed because (filecrc != crcsum) never occurs (for whatever reason).
Xant said:
Hi all
Er2003edit will try to modify the header information in the NK and Radio_mbf but this will not be successfull and I still will get the Country ID error, is that right ???
Click to expand...
Click to collapse
No. Er2003Edit can open NK and radio ROM files and edit the header. Er2003Edit automatically re-encrypts the newer ROM files (XOR-Method).
Er2003Edit decrypts older ROM files (DES-Encrpytion), lets you edit the header and save the file but it does not re-encrypt these ones (use xda2nbftool). A message is displayed in this case to remind you to encrypt the file.
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
softworkz said:
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
Click to expand...
Click to collapse
I confirm what bobopopo claims, i tried only flashing the ms_.nbf, and it totally messed up my machine (stuck in bootloader), i had to reflash all three to get it to work again
nargalzius said:
softworkz said:
Xant said:
As far as bobopopo expierenced the new upgrade utility will not run parts of the upgrade but rather leave the machine useless.
Click to expand...
Click to collapse
AFAIK the upgrade tool will only look at the extended ROM's operator field. Anyone please correct me if I'm wrong about that.
Click to expand...
Click to collapse
I confirm what bobopopo claims, i tried only flashing the ms_.nbf, and it totally messed up my machine (stuck in bootloader), i had to reflash all three to get it to work again
Click to expand...
Click to collapse
I knew about this. I was just stating that the header of NK and Radio is irrelevant for the upgrade tool and is not responsible for the country code error.
SPV M1000
Does it work with SPV M1000 version
loade ER2003 started it and stay on the ROM info screen :?
Related
I have the T-Mobile ROM 1.60 currently installed on my I-Mate. Now I am trying to install the latest I-Mate update, I keep getting Country ID Error 120. Anyone know a solution? It seems we need some kind of AdaptROM...
The same for me yesterday ERROR 120, I try anyway but no results
I think that new ROM only for I- mate Device with special IMEI Number :evil:
Any ideas? :?:
I upgrade to i-mate update and I try to upgrade to T-Mobile I get the same error!!
anyone can help?
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
tomerbn said:
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
Click to expand...
Click to collapse
It seems not possible by writing just writing the nbf to SD card and flash to the XDA 2 anymore.
Because the bootloader will check the first 412 bytes (i believe it is the code on the last line of the 412 bytes, somthing like HTCSA00400000XXXXXXXX.............) of the rom on the SD card match with your machine or not. Therefore without any modification, only the ROM dump from the Machine itself can be flashed.
Moreover, nbf is encoded, you can't just edit it by HEX editor, you have to get the rom in nb1 format.
I think XDA developers have to develop new tools to
1. Get the first 412 byte of the rom from your machine in an easier way. Now we have to use Multiport / USB TTY get into bootloader console, dump the rom to SD card , and use ntrw read the SD Raw data to the computer to get this 412 byte. You need a HEX Editor to do so. (Please correct me if I said something wrong).
We can
a) develop an APP to get the 412bytes from SD to harddisk without using a HEX editor
b) directly read this 412 bytes from the XDA2 if possible.
2. A Rom tools that can add your machine's own first 412bytes (or the code) , combine it with a .nb1 or .nbf and write it to a SD card.
By the way , I think a new adoptrom support XDA2 will be the best solution 8)
note added by itsme: this will very likely break your devie!! - better look at sdtool
same problem
i'm having the same problem, installed imate update, now i cant install the t-mobile update.
nobody seems to know how to fix this
HEEEEEEEEEEEEELLLLLLLLPPPPPP
try this
Hi,
another idea... :idea:
try to unzip (using winrar i.e.) the file ruu15283wwe_cdl.exe,
and run the HimaUpgradeUt.exe
It might work!
I got error, the device is not connected, or something like that, while trying to use the original file, but with the HimaUpgradeUt it works!
Tomer
Check this out http://forum.xda-developers.com/viewtopic.php?t=4785
First it was a Phone, then it became a computer phone, now it is camera computer phone... what will be the next?
Click to expand...
Click to collapse
A camera computer phone with a stable, reliable OS? Oh well, we can dream....
Hi,
just a tip for opening the latest ROM files with ER2003Edit:
ER2003Edit has a file type selector in the file open box which is by default set to autodetect.
in autodetect mode ER2003Edit tries all encryption passwords it knows for any type of ROM (NK,Radio,ms_)
when using autodetect mode and your ROM does not get detected and you enter the correct password manually, you will receive an "Error accessing image files" message
To prevent this message choose the correct type of ROM (ms_.nbf) from the file type selector of the file open dialog and enter the password
ER2003Edit can open and edit all types of ROM files now in order to let you change the language and device type settings (to prevent country code error)
Tip: Opening ROM files is always faster when you do not use autodetect mode!
BTW here are the passwords for the ITA-Rom:
ms_.nbf: 0x20040305
nk.nbf: 0x20040304
radio_.nbf 0x20040306
A new version of ER2003Edit will have these passwords built in, but I currently do have no time for a new release just to include the passwords.
Enjoy!
fantastic
thank you very much
Works
Thanks
Softworks, are the the old passwords hardcoded into the app?
I reckon on your next update, maybe you could just make the app read an XML (or text, whatever) file with the passwords. So you can easily just add passwords in the future onto the text without having to recompile a newer version.
Also, since when talking about XDAII files, we're only talking about 3 filenames which never change. Maybe you could make a load process to simply check the filename which has been opened and use the corresponding "file process" to open it. Sort of like instead of autodetect when you open files. Have a simple check that checks wether one clicked either of the 3 files, then have a script that mimmicks selecting manually the filetype instead of "autodetect." That should eliminate the "nuances" of opening files (especially helpful for us n00bs hehe)
Cheers,
Carlo
Sorry, Iwould like to ask how / where to find the password of the images?
Thanks!
Hi All,
I have images which can't open by ER2003edit V1.2.20, it say the password is incorrect. Anyone can help or teach?
The rom image is from O2, the rom version is 1.60 or higher.
Thanks!
Can someone help me out too, it won n't seem to work with me.
d.zee said:
Can someone help me out too, it won n't seem to work with me.
Click to expand...
Click to collapse
Cant find them either.... Please help
See here:
http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
Here is a patched version of ER2003Edit.exe that has the new 3 passwords. Auto detection now works. :lol:
Just unzip then copy it over installed ER2003Edit.exe usually found in
C:\Program Files\softworkz\ER2003Edit\ER2003Edit.exe
RE
Hi!
Thanks. It works.
:lol:
PDA: O2 XDA II
ROM Version: 2.06.00WWE
Radio Version: 1.18.00
ExtROM Version: 1.12.924WWE (from IIs)
OS: Windows Mobile 2003 Second Edition
OS Version: 4.21.1088 (Build 14132)
Any reason I am getting shcksum errors?
I chenaged the content of ms_.nbf save it, and tried to flash it, but I gor error 122 - checksum error?
Any known reason for that?
Looks like I am out of my depth but its worth a try
I have a blueangle and have worked out that there are more tools on in Himalaya than for us.
I have further worked out that the upgrade works in the same way.
So I would think that this tool does, Well I am either wrong or just dumb.
Is my undersatnding correct that this application would only have the paswords for the at that time Known rom realeases.
Is my understanding that even with a password out of a xda3nbtool this toll will not work if you add it in the dialog.
Thus I seem to find that if I fill in the device name, op and lang as well as pasword I fail, same is true if leave them blank.
Please help me out or point me in the correct direction
Thanks
Hi,
does anyone know a program or a howto for editing Asus MyPal ROM Updates? In fact I only have to add a single file.
Thanks for any response
Martin
Dear Fellas,
Where can I get a step by step ROM upgrade instruction to upgrade/flash my XDA II into WM2003SE? I have been through the forum, but still can not find a basic guide to do the upgrade.
I have downloaded "Customized_WM2003SE_Asian_Edition_Version2.zip" from ZeroXtreme. What can I do with this file? How can I start it?
Anyone can help me pleaseeee.......Thanks a lot.
Rgds,
Fendie
Ahoy there matey!
this is what you do:
1. decide on what version you want to use.
2. get them roms. (E.g. read through DCS's post on the ORIGINAL WMSE)
currently there are three versions of the WMSE namely 2.02,2.06, and 2.20.
3. check your device data for language and operator:
use getdevicedata.exe from the upgrade files, copy it to your device's windows directory, then tap on it.... it will produce a log file, copy the log file to your desktop pc, then use notepad.exe to view it.
look for the language setting e.g. WWE, CHT... etc.
look for operator settings e.g. O2, Qtek... etc.
now check your downloaded NK.nbf, MS.nbf and radio.nbf to see if they have the same settings as your device..... you can use ER2003edit.exe which can be downloaded from wiki.xda-developers.com.
if the files have the same settings, thats good... if not... change it so that they would be the same as your device.... better yet use DCS's batch file for easier conversion... (note, DCS's 2.02 rom is set to WWE,O2)
now... assuming you had made all the preparations... (language, operator settings, and that you have a complete set of roms e.g. NK.nbf, MS.nbf and radio.nbf)
put them all in one directory along with the other files that came with the upgrade package.
make sure you have a full battery before proceeding with the upgrade.
plug the charger to tha cradle and the cradle to the comnputer.
click on himalaya upgrade program.... then the program will run, put the device in the cradle and watch the screen for further instructions
goodluck...
be sure to read on DCS's post regarding upgrades for a more detailed info.
assuming everything goes well; during the upgrade do NOT take out the unit from the cradle; go watch tv or something...if you receive an error message; don't fret. the forum hosts a lot of topics on how to revive your unit...
and if your xda dies during the upgrade; make sure your tray tables are in their upright position, put your head between your legs and kiss your arse goodbye
what do guys suggest the ROM i use?
which one is the most stable?
mate, i noticed that you're from the philippines. i'm based in thailand i used the rom posted by zeroextreme; it's the wm2003 se asian rom. pretty stable that one; after upgrading my unit's power consumption improved noticeably. although as expected some apps may not display well when using landscape mode (those're the apps not designed for wm2003 use). but overall the rom upgrade was well worth it. stable and no hick ups; been using it for more than 2 weeks now i think.
others may have useful tips on the other roms they used for upgrading; not to mention experiences.
cheers
acid.... try 2.02.t1 they say its more stable than 2.06.
thanks mga kababayan!
Z-man said:
Ahoy there matey!
this is what you do:
1. decide on what version you want to use.
2. get them roms. (E.g. read through DCS's post on the ORIGINAL WMSE)
currently there are three versions of the WMSE namely 2.02,2.06, and 2.20.
3. check your device data for language and operator:
use getdevicedata.exe from the upgrade files, copy it to your device's windows directory, then tap on it.... it will produce a log file, copy the log file to your desktop pc, then use notepad.exe to view it.
look for the language setting e.g. WWE, CHT... etc.
look for operator settings e.g. O2, Qtek... etc.
now check your downloaded NK.nbf, MS.nbf and radio.nbf to see if they have the same settings as your device..... you can use ER2003edit.exe which can be downloaded from wiki.xda-developers.com.
if the files have the same settings, thats good... if not... change it so that they would be the same as your device.... better yet use DCS's batch file for easier conversion... (note, DCS's 2.02 rom is set to WWE,O2)
now... assuming you had made all the preparations... (language, operator settings, and that you have a complete set of roms e.g. NK.nbf, MS.nbf and radio.nbf)
put them all in one directory along with the other files that came with the upgrade package.
make sure you have a full battery before proceeding with the upgrade.
plug the charger to tha cradle and the cradle to the comnputer.
click on himalaya upgrade program.... then the program will run, put the device in the cradle and watch the screen for further instructions
goodluck...
be sure to read on DCS's post regarding upgrades for a more detailed info.
Click to expand...
Click to collapse
Hi Z-Man,
Thanks for your response. But still do not understand in some areas
I just got MS.nbf and some *.CAB files from the extended ROM of ZeroXtreme. There are no NK.nbf and Radio.nbf. Is it because it's an Extended ROM? Where can I get the "non-extended" ROM?
And I don't really understand on DCS's post.
Sorry, I am really really newbie.....
Many thanks.
Rgds,
Fendie
ms.nbf is the extended ROM, you still need to get the radio.nbf and nk.nbf
download the file here:
HIMALAYA_WM2003SE.zip and Operator update.zip:
http://forum.xda-developers.com/viewtopic.php?t=13588
extract all files to one directory... and add the ms.nbf that you have
you didnt mention the operator and languange settings of your device... check your device info....
then use DCS's batch file to convert the settings.... by default, DCS uses WWE and O2.
make sure all the nbf's are set to the same settings...
then begin upgrade
Himalya Romkitchen is still valid for SE
Hi to everyone.
Before this HTC device I had others and also had a Motorola Mpx220 (WM2003 SE).
I was used to move the files within "\Windows\Start Menu" (mostly .lnk files to installed programs) into newly created subfolders, to be able to use and/or access the function I needed in a faster way.
I've tried doing the same on this WM5 device, but everytime I try I get an error message reporting it is not possible (File Explorer has greyed out options to cut and/or copy, while TotalCommander just reports it's not possible to "overwrite" ???).
Does anyone have an idea of how this can be done (registry ???) ?
Thank you.
Ciao
Here is the solution...
Hi Mix, it's Mix answering (yes, I'm the same person...)...
First of all I would like to thank you ALL the people which knew the solution and were fighting to answer to my doubt...
You were so many, I wonder why the message has been read times and so many answers arrived: 0 (yes, ZERO).
Anyway, I came across the solution myself, by chance...
The problems seems being the smartphone versions of WM5 being protected against file modifications. This protection extends also to some files execution and to certificate installations (hence some problems may arise when connecting to an Exchange Server for syncronization).
Some tools are needed to remove this protection, and some experience of registry modification is required too (I will not help anyone beside what is in this message and I take no responsability for any mistakes and/or troubles you may produce or face).
First of all you need a special version of RegEdit (the tool from PHM): you should find an HTC digitally signed copy of it called RegEditSTG.exe.
Look around for it: there are many forums around which do hold a copy of it.
Place it in your phone's memory, not on the MicroSD card...
With this tool you should change the following values:
HKLM\Security\Policies\Policies\00001001 = 2 => 1 (RAPI)
HKLM\Security\Policies\Policies\00001005 = 16 => 40 (Cert)
HKLM\Security\Policies\Policies\00001017 = 128 => 144 (?)
The first is the value you will find, the second is the value you should enter. The third line has a question mark because someone says it should be made, someone not... It's up to you. I made it.
Then you should find another tool (with the same above method) called SDA_ApplicationUnlock.exe which has to be run on your desktop PC with the phone already connected with USB (and possibly with ActiveSync not in the middle of a sync...).
Once you run this, you will get a message that the unlock took place (if not, it may be the first operations did not complete well).
Disconnect your phone from the USB cable and power cycle it (switch it off and then on again).
Opla'... the phone is not APPLICATION UNLOCKED and you will be able to move file around the directories as I was looking to when I first posted my message.
Now I have a very quick Start Menu, as I wanted.
Please, be aware that this operation hacks the security policies of WM5 and then any other application which may be dangerous can now run on your phone.
If you wish to stay on the safe side, it could be useful to restore the registry settings to their original values, but I do not know if this could cause other problems, since I didn't on my phone.
I actually double check every single file by myself before launching it and I do not run anything which I'm not sure it is safe.
So, pay attention... (you have been warned...).
Hope this helps someone else out there.
Ciao
Thanks for the tips mate! I was searching around for the same problem.
Can a hard reset put all the files back as in the old WM2003? I'm asking that 'cause if you look at the windows directory, many exe and dll files are repeated, with a different code. I guessed they are for the many different languages the phone support and the code is the country code. Maybe when you switch from one language to another those files are renamed so you have the correct exe and dll for the language you need...
If I can erase all the files I don't need (I will never change the language or maybe have only italian and english) I can save lot of space.
Am I wrong? Was that ever tried before?
vbi said:
Thanks for the tips mate! I was searching around for the same problem.
Click to expand...
Click to collapse
;-) I knew...
Can a hard reset put all the files back as in the old WM2003? I'm asking that 'cause if you look at the windows directory, many exe and dll files are repeated, with a different code. I guessed they are for the many different languages the phone support and the code is the country code. Maybe when you switch from one language to another those files are renamed so you have the correct exe and dll for the language you need...
If I can erase all the files I don't need (I will never change the language or maybe have only italian and english) I can save lot of space.
Am I wrong? Was that ever tried before?
Click to expand...
Click to collapse
In order:
- Yes, I suppose a hard reset of the device completely restores the original factory settings, hence, the device will appear as "brand new".
- You're right: all the localized files present there are just to be able to swithc to other languages (maybe following user's settings and maybe also following user's SIM settings too...).
- Erasing the unused files may appear as a "space saving" job. It is not. First of all you will not be able to remove ROM resident files, but provided you could be able to do this, you will not be able to use ROM space as you intend...
Finally then, it's completely unuseful to try to remove them, just a waste of time trying...
Ciao
Thanks Michele.
Are you sure the windows directory is in ROM?
I always tought ROM was only to store the "disk" image when you hard reset the device. I was so for the Qtek S100.
vbi said:
Are you sure the windows directory is in ROM?
Click to expand...
Click to collapse
Yes it is. On the fact that it is then copied into RAM, well, this is a tecnique which was used up to WM2003 SE devices.
Starting from WM5 devices MS somewhat changed the behaviour of the whole system, hence I'm not then so sure.
Indeed, I have never been sure of anything, beside death, so you can imagine...
I'm not really so "expert".
Having used an MPx220 for over one year (with all its limitations, but exploiting it very much), using a WM5 device now is a much more relaxed experience (faster, more realiable and less troubly in terms of memory).
Just MHO
Thanks Mix - i followed your directions and it worked.
Got my QTEK (running i-Mate ROM) Application Unlocked
I seem to have successfully dumped my Cingular 8525 ROM, and placed it on the FTP area ftp://xdaupload:[email protected]/Hermes/Dumped_ROMs/ (directly as ftp://xdaupload:[email protected]/HTC_TyTn_Cingular8525_CWS_1_34_502_1_WWE.zip) but when I try to extract the imgfs I get lots of decomp errors and it seems that compressed files do NOT get uncompressed....
Is there something different in these newer ROMs or am I just being stupid or ????
TIA,
Richard
Moved the dump to safe heaven.
I haven't download your files to see if I can extract them, but if you not succeed with itsme rdmsflsh.pl you can also use mamaich rom editing tools, viewimgfs.exe with "part_02.raw". See if it makes any difference
pof said:
Moved the dump to safe heaven.
I haven't download your files to see if I can extract them, but if you not succeed with itsme rdmsflsh.pl you can also use mamaich rom editing tools, viewimgfs.exe with "part_02.raw". See if it makes any difference
Click to expand...
Click to collapse
It worked a little better, or at least differently.... I forgot to mention I tried that as well. Much harder to deal with the files being each in subdirectories The filesizes extracted still didn't match those reported on the device itself though, so I'm not convinced I'm getting a good extraction.
Results are on my work machine, I'll have to login there and see if I can post some specifics....
Richard
User error
rsolomon said:
Results are on my work machine, I'll have to login there and see if I can post some specifics....
Click to expand...
Click to collapse
DOH! User error.... Remote Desktop to my work machine slowed things down enough that I could see errors about not being able to load dlls.... seems the ActiveState Perl 5.8 install insists on installing to "site" vs "perl" but doesn't add "site" to the path, so Windoze couldn't load the necessary dlls.
I just copied them into my working directory for now and am re-running the extraction....looks much better already!
Richard
ok, can you add a warning to the wiki with this info ? thanks
pof said:
Moved the dump to safe heaven.
Click to expand...
Click to collapse
Should I add it to the wiki or will you do that?
Richard
pof said:
ok, can you add a warning to the wiki with this info ? thanks
Click to expand...
Click to collapse
Yep, I already noted one needs v5.8, I should really clean this up and find the right fix, but I'll note the path problem at least and maybe someone else will do it "right" later
Richard
do it yourself please, i have no time now... leaving to France in a few hours.
pof said:
do it yourself please, i have no time now... leaving to France in a few hours.
Click to expand...
Click to collapse
Both wikis updated, thanks for the help!
Richard
rsolomon said:
The filesizes extracted still didn't match those reported on the device itself though, so I'm not convinced I'm getting a good extraction.
Click to expand...
Click to collapse
Ok, pretty confused here. One example:
bthasplugin.dll
Exploring the device via ActiveSync shows a filesize of 17560 but the size shown on my PC of the extracted version is 18944. Spot checking a few other files show similar size disparities.... is this normal? Why?
Richard
Not sure, but probably the difference is because file size (byte count) is different than size on disk (amount of clusters the file takes).