Related
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 :?
i have a O2 XDA II . it came loaded with 1.66WWE. i wanted to put 1.60. i downloaded it from sourceo2.com
then double clicked the installable. it started the downgrade . it said it will take 30mins & started deleted the rom image.. i then went for lunch & came back in 15mins.. the phones now totally dead.
If i dock it , the screen says USB V1.06
if i remove it the screen says Serial V1.06. I cant hard rest it nor can i soft reset it. i huess cause there no rom image in it.
What do i do.. please help with as many links software as one can..
Please...
ive got 1.72, but when i try that. it says country error.??
can that be resolved.. i dont mind loading 1.72.
the good news is that it seems you still have the boot loader working ... use ER2003 tool to modify the country code of the 1.72 ROM file ... or you can use the xda2nbftool.exe if you like the command line mode
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
hyper said:
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
Click to expand...
Click to collapse
Unpack the .exe file with winrar/winzip. And you're good to go.
Edit this file: ms_.nbf
managed to unpack it... now when i try to load 1.60 it says model id error & if i try to load 1.72 it says country id error.
what do i change in the ms_.nbf file ????
do i only change this file fields or all three??
i even removed the battery & checked the model ID. on my phone it says PH10B
i changed all the three files to PH10B ..
Now i get Connection Error.....
Now what???
now the error is ERROR 101... connection error.
(i'm loading 1.60)
also is it possible for me to do it via my emory card (i have a MMC32MB & 128MB)
if so, what file do i need to copy & then whats the procedure??
i got 1.03.00 rom on mine. my xda 2 is 2 days old now dunno wht rom to load it up with now. whts the best & safe rom now. i have no apps or nething to back up so its oki. the phone was bought from u.k. and was locked on O2 network. now its unlocked and being used in India. plz advise wht ROM to d/n and use. if possible the d/n link as well. thx
Question?
Why do you want to downgrade your phone? :shock:
For upgrade to 1.72:
1. Download i-mate 1.72 update and xda2nbftool
2. unpack that update to any directory on your harddrive
3. download script from this post to created directory (unpack it too)
4. copy xda2nbftool.exe to that directory
5. run provided script
6. insert XDA2 to cradle and then HimaUpgradeUt.exe
You will i-mate splash screen from i-mate though, but working device.
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
i wonder... most O2 XDA II come with 1.6 rom version. mine came with 1.66. could that mean its not O2 even though its written O2 on my phone? could it mean its T-Mobile or something??
can someone post a link or software that i need to put onto my MMC card & then use that to install the rom from the card inserted in the phone??
hyper said:
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
Click to expand...
Click to collapse
So, what's that problem? Can you run it?
Try to run it in command prompt... And if it writes any error, post it here...
Can you access the file system of your XDA2 from ActiveSync -> Explore?
now i managed to get the problem of Country error out of the way , but now im getting the ERROR 101 - Connection Error.
no i cannot browse any files & my active sync does not show connected.
what files do i need to copy paste onto my MMC card so that i can flash it by executing the files with the camera button & the MMC Card inserted??
im dowloading the NTRW & 1.72 NK.nb1 file. do i just copy & paste it on the mmc card & then instert the card into the phone & then press the camera button.. should this do the trick??
this is all that i have tried so far... yet no luck.
my phones originally from malaysia , its an O2 XDA II
i have the following rom with me. my bootloader is V1.06
1. RUU172800WWE_CDL_SKU1
2. XDA_IIupgrade_v16050
3. RUU172104wwe-t-mobile-uk
1. i removed the battery , dcoked the phone, connected the charger to the docking bay at the back...the red light on the phone lights up.... the bootloader screen shows up ina slightly distorted manner.
i then ran all the three roms as it is..without editing anthing. The error i get in all the three times is ERROR 101. CONNECTION ERROR. it tells me to check is usb is connected, charger is connected usb port is conencted & the phone is on. .......... everythings connected but obviously phone can only be in bootloader mode.
2. i put the battery back in dock the phone, the charger is yet connected to the back of the docking bay. .. i try all three installations withour extracting or editing as they are exe files..... now, all the three times i get COUNTRY ID ERROR OR MODEL ID ERROR.
3. when i edit the ones that give me model id error then i get CONNECTION ERROR AGAIN. (this is again with the battery in & charger plugged in)
i downloaded the NTRW & 1.72 NK.nb1 file. but the one that is available on this forum is corrupted. so i cannot extract it.
NTRW ive downloaded seperately. i need the nb1 file now. can someone post a working, no-corrupted image rom image file?
once i get the correct Rom.nb1 file... all i have to do it copy & paste the correct rom.nb1 & ntrw.exe file onto my MMC card & keep the battery in the phone & insert the MMC card & press the Camera button .... is that correct? i'm guessing that this will run the ntrw exe file & load (dump) the Rom.nb1 file onto the phone. is that correct?
please do let me know what else i can try & dowload a newer RUU or something. i think the best way is to SD flash the phone.
i dont even mind flashing it to a PPC2002 version & then upgrading it from there. if thats possible.
As far as the connection between the USB Docking Bay is concerned,...everytim i connect or disconnect the phone, i hear the familiar XP "TING" which shows that some USB thing is connected, but my active sync does not show that the phones connected, i guess that cause it got no rom in it.
Also when i edit the ms_ / NK / Rom files er2003 i get an error everytime i start the software, but i just press IGNORE & continue. i always get ROM successfully written & then the error pops up again but i keep pressing ignore. this works... but whats up with the CONNECTION ERROR. IF ITS NOT CONNECTING TO THE PHONE, HOW DOES IT KNOW THAT THE MODEL ID OR COUNTRY ID WRONG ???
Ok.
If any ROM update can detect your device (as we can see error messages COUNTRY ID ERROR or MODEL ID ERROR), there is hope, you can update your device.
If it's 1.72 ROM (that writes COUNTRY ID ERROR or MODEL ID ERROR), use the solution I send you few posts ago (unpacking, running batch script etc.)
When you updating, keep battery in your device and charger of device connected to cradle! Don't remove anything.
BTW: Don't use RUU172800WWE_CDL_SKU1 update, it just update only part of your device (ExtROM)!
BTW2: Read this: http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
thanks againa beecher. the problem is that once i use the patch & then run it. it does not show me the country id or model id error (for which i thank you) but then it says error connecting.
i have a USB to serial connector. should i try serial connection?? or maybe try it on another computer.
can anyone please tell me how do to a SD flash step by step with the Rom.nb1 file attachment of link.
Hi guys,
I have to compliment Stefan for personally e-mailing me back about a problem I was having and pointing me here. Hopefully I can become a little less clueless through the forums.
When using kitchen, I get the ROM.EXE update. I understand I run this on my PC. My phone is a Wallaby, with WM2003 first edition. I've written down my t-mobile settings and I'm ready to flash it. However, when attempting to run the ROM.EXE program, I getting the following error:
Code:
ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR
Cannot execute the remote communication progra,
Please make sure that the USB/Serial cable is properly connected.
The phone is connected to the PC directly over USB through it's cradle and I have ActivSync 3.7.1 running. Any ideas what my problem could be?[/code]
http://forum.xda-developers.com/vie...+remote+communication+program+programme+error
http://forum.xda-developers.com/vie...+remote+communication+program+programme+error
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Stefan
Alrighty, after reading those, I figured I had to write the WM2k3SE ROM to a SD card. After extracing the NK.NBF from the ROM.EXE I have to a directory, I fire up the XDA OS IMAGE TOOL and select it in the SOURCE. I choose "SD CARD" for my destination and produce the following error:
Code:
NK.NBF: Incorrect Filesize(33554464), file size should be exactally 32505888 bytes. Error opening input file.
A quick search of the forums didn't show anything that might apply. According to these wiki instructions this looks like the correct thing to do. Is it possible that I have a bad kitchen rom?
Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM....
OK, but is the procedure I'm following correct? Download a WM2003FE ROM.EXE at version 3.17.03 and then extract the NK.NKF from the executable and flash with that? This will allow me to use the ROM.EXE of my WM2003SE kitchen image instead of using the OSI tool? (If this works, I'm going to go add to the wiki).
Hello,
please, please I need help
for flash Alpine´s ROM. I tryied 4 different ROMs for flash my device and always detects "Error 120: Country ID Error".
Flashing by way of xda2nbftools with XOR codes of Alpines ROMs not worked - control checksum errors.
Regards
You should use an executable that does not check country ID. MaUpgradeUt_noID.exe is the file you are looking for. Run your ROM upgrade program. At the point when you face the country ID error under a directory (sth like this: C:\Documents and Settings\Your Name\Local Settings\Temp\A funny named directory) you will find 6 files. Before cancelling the upgrade copy them to another safe directory (after cancelling all will be deleted automatically) and cancel the upgrade. Replace HimUpgrade.exe with the file I attached in that safe directory. Put the alpine in bootloader mode and cradle it. Then run this file (MaUpgradeUt_noID.exe). First it will fail then in the second time it should work.
Thank you very well,
your method is correct.
Now i have:
Radio: 1.03.00
Ext.ROM: 1.11.144 WWE
ROM: 1.11.00 WWE
Protokol: 1337.42
HRomek, is this firmware from I-mate PDA?
voln, no it is firmware from i-mate PDA2 (ALPINE).
that really works. thanks a lot
As I couldn't find a MiniSD (less than 2Gbytes, impossible where I live) I worked on re-flashing my Comet back to the German ROM using USB.
1. Downloaded the Comet ROM + Extended Rom files that Scorpio had placed in rapidshare
2. Executed the DSUU for Atom Life (WWE 20070914) and cut the 12 header bytes from both "FLASH.dio" and "ExRom.img" and pasted those 12 bytes in the German Comet AL1.dio and ExRom.img, and renamed AL1.dio to FLASH.dio
3. Placed the patched German files in the DSUU temp directory, replacing the original WWE files (c:\windows\temp)
4. Instructed DSUU to proceed as normal
5. The deviced cold-booted after finishing and worked.
So, flashing vía USB can be achieved by means of re-using the 12 bytes of both headers (it might be needed depending on the original ROM, to either edit Pass.32 or to hold down the "arrow key" of the PC at the initial stages of DSUU to skip the CID check).
Of course, this has not cured my "Radio ROM" problem, as my XDA Comet still has the WWE Atom Life Radio Rom, which does not work on Comet devices.
I will now work in finding a way (shall it exist) to dump the Radio Rom (I have already got itsutils and executed pdocread a couple of times).
Best regards
Hi
Maybe you can dump the radiorom with haret.
Unfortunetly I have not the knowledge to help you in these job.
You flashed the complete update with replaced files ?
Or did you flash OS and ExtROM only ?
I flashed the complete upgrade.
I did so because I had already flashed the complete WWE Atom Life upgrade, so in my case it made no difference, to put all these extra files back into the device, as they were already there!!!
But if we manage to find out which files affect the GSM/Radio part (and we also find out how to dump radio roms), it might be that we end up with a clear process to update Comet/Life with different ROMs using USB.
P.D.
I did my best into getting a 512 Mbytes MiniSD, but MediaMarkt, Saturn and smaller shops did not have anything so small. They were basically focusing on SD or MicroSD. I think MiniSD may end up as a dead technology.
pepelu456 said:
P.D.
I did my best into getting a 512 Mbytes MiniSD, but MediaMarkt, Saturn and smaller shops did not have anything so small. They were basically focusing on SD or MicroSD. I think MiniSD may end up as a dead technology.
Click to expand...
Click to collapse
You can try a bigger card. If it will be recognized, you can flash with this one.
I don't think, that the device will be damaged.
But I haven't test it.
PS:
I played with pdocread and the following command dumps a part, contained the bootloader.
As I said I don't know how to use pdocread to dump a specified part, but maybe this is a small hint, how you can use this tool.
pdocread.exe -n 0 0x00000000 0xFFFFFFFF -b 0x100000 File_out.bin
Click to expand...
Click to collapse
I belive, if you can dump the bootloader, you can also dump the radiorom.
I hope you have success to lokate the Radiorom.
If I can help to dump the radio, PM me.
I'm not sure, but if you choose in BL:
(5) Burn MOT/BL via UART
and insert a MiniSD, it appered the messages "couldn't find parti.mbn , amsshd.mbn and amss.mbn.
amss.mbn must be the RadioROM.
Your pdocread command works in my mixed WWE-GER device too and dumps te bootloader.
Trying to access binary partition 1 delivers the following error:
"Invalid controler"
Trying to access binary partition 2 delivers the following:
-- Once again the same dump of the bootloader.
--------------------
I also think that it should be possible to dump the Radio ROM, as DSUU is able to report the "date" of the Radio ROM file, whereas WM6 is unable to communicate with the Radio Stack.
Of course, the obvious (not necessarily true) reasoning is that WM6 is trying to use standard API calls that are failing whereas DSUU is accesing the ROM files before going into bootloader mode (when the user decides to execute the upgrade)
HARET fails to dump anything over 4Kbytes with a "short write to disk detected" (it will sometimes not write a single byte down)
Both behaviours may be caused by lack of adaptation to this specific hardware platform.
Regards
P.D.
I really find it unbelievable that the Atom Life has had so little hacking, taking into account that it has been sold by O2 Asia for quite a while, but even looking at Chinese forums (no, I can't speak chinese), they don't seem to be any more advanced than we are.
pepelu456 said:
As I couldn't find a MiniSD (less than 2Gbytes, impossible where I live) I worked on re-flashing my Comet back to the German ROM using USB.
1. Downloaded the Comet ROM + Extended Rom files that Scorpio had placed in rapidshare
Click to expand...
Click to collapse
Pls help, where you can have that comet ROM and Extended Rom.
Thank you.
Dear pepelu456,
I got your same situation. Now, so sad cannot repair.
pepelu456 said:
As I couldn't find a MiniSD (less than 2Gbytes, impossible where I live) I worked on re-flashing my Comet back to the German ROM using USB.
1. Downloaded the Comet ROM + Extended Rom files that Scorpio had placed in rapidshare
2. Executed the DSUU for Atom Life (WWE 20070914) and cut the 12 header bytes from both "FLASH.dio" and "ExRom.img" and pasted those 12 bytes in the German Comet AL1.dio and ExRom.img, and renamed AL1.dio to FLASH.dio
3. Placed the patched German files in the DSUU temp directory, replacing the original WWE files (c:\windows\temp)
4. Instructed DSUU to proceed as normal
5. The deviced cold-booted after finishing and worked.
So, flashing vía USB can be achieved by means of re-using the 12 bytes of both headers (it might be needed depending on the original ROM, to either edit Pass.32 or to hold down the "arrow key" of the PC at the initial stages of DSUU to skip the CID check).
Of course, this has not cured my "Radio ROM" problem, as my XDA Comet still has the WWE Atom Life Radio Rom, which does not work on Comet devices.
I will now work in finding a way (shall it exist) to dump the Radio Rom (I have already got itsutils and executed pdocread a couple of times).
Best regards
Click to expand...
Click to collapse
hi,
u said that we can flash via usb i have atom life purchased from middle east it have wm5 pre-installed , i entered www.seeo2.com and saw that there is an upgrade to wm6 so i downloaded the file an started the update process when detecting device it says ID ERROR, is threr a solution for this problem , and something else i flashed the wm6 rom via SD i took from temp folder in windows and removed the 12 headers , it flashed nice , but i want from the usb so that i can flash the radio files , ext rom , boot loader ...etc.
thnx
Yoou can find sth here for yr upgrade http://forum.xda-developers.com/showthread.php?t=378616
it didnt work for me changed the pass.32 no use i think i cant upgrade via usb
Try this http://www.myxda.com/xda-atom-life_wm6_oct2007ara.aspx
hi i need hel.. plese
i have a o2 comet and mi radio is gone after rom update mwg... plese scorpio could u help me with the original o2 comet files to restore gsm module, i'll be forever in your dept... i sherched everywhere even on ur blog, rapidshare, google, tryed everi original atom life rom, bu evrithig works with other rosms exept radio gsm, plese help me with the files ... i try upgrading rom becouse batery life was lousy. plese help...
the same problem
ion_plugged said:
i have a o2 comet and mi radio is gone after rom update mwg...
Click to expand...
Click to collapse
I have exactly the same problem. Even already try to receive update from service centre... answer was: "we need you device to test and... for repair app cost 100eur and more"
If some one can help us... please help!!!
count me in this list i have the same issue lost radio and imei and i don't have O2 in my country