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 :?
Firstly, forgive me if this has been covered - I tried searching for this but didn't find an answer...
I'm trying to upgrade my Orange M1000 to WM5 and am worried that I'll totally destroy my machine, so I'm treading as carefully as possible.
I've been following the instructions from xda2jojo but came across something very quickly:
The instructions say to search for nb.nbf. I guessed this might be a typo (?) so I downloaded nk.nbf instead.
I went to patch it but I get an error: "Sorry, this file cannot be patched!"
Also, when in the ROM editor, there is no option for Orange - which should I use instead?
Am I being really dumb or is this a real problem?
Thanks
MkS
The Same Problem in TSM500
I also have the same problem
I tried to patch NK.nbf but it fails, showing the message "Sorry, this file cannot be patched"
I also tried to update my TSM500 without editing this file, but it doesn't seem to connect. And when it connects, it shows a message saying that tuere is a language error.
I used HimaGetDeviceData to get the language configuration, but un file "Devicedata.txt" there is only a "U" and nothing else. There isn´t language nor version number, nothing...
copy the file Devicedata.txt to your pc and open it there.
Use this Himaupgrade file that bypases country and telco identity
ftp://xda:[email protected]/Himalaya_SEs/HimaFiles/himaupgradeut_197.exe
I hope that this help...
Does that also get around the fact that the patch1.exe program claims that nk.nbf cannot be patched?
What this patch for ?
Sorry for question . What this patch for ?
I have no idea, but the instructions for upgrading to WM5 say you've got to patch nk.nbf.
I had the same problem
:arrow: I had the same problem ... so I did upgrade without patching .
By the way Sprite Back Up is not working .
Pocket Informant impossible to install .
Hi - get the same problem with the patch. Am treading carefully too to ensure i don't have an expensive paperweight.
Anyone know if the patch is mandatory or is the file linked via the wiki for w2k05 ROM already patched and ready to go and therefore need to skip this step according to the FAQ
Thanks
Finally updated
Finally I got my xdaII updated. I didn't patch nk.nbf, I only uploaded the file.
The xda started correctly, and after an hour since I updated it, I only saw that the buttons "camera" and "recording" (left side of tha xda) doesn't seem to work.
I think that the memory is too low. Maybe I chose a wrong version of WM2005.
Storage
Total: 14.57 MB
In use: 1.74 MB
Free: 12.83 MB
Program
Total: 24.35 MB
In use: 14.94 MB
Free: 9.41 MB
Anybody else have the same memory problem?
Thx
(Pd: Voice recording key only works when display is off)
patch NK.nbf but it fails
hi guys
I also have the same problem
I tried to patch NK.nbf but it fails, showing the message "Sorry, this file cannot be patched"
Can any one help us
tKS
Upgrade successful
I had the same problem. I did not patch and performed the upgrade. Everything works fine except the record and camera buttons. Vito Button mapper does not help either, but it does allow you to make the contact & calendar buttons multi-functional so they can replace the for-now missing buttons.
Good luck.
Who else to ask ?
I did PM to xda2jojo and I have no answer ? probably he is busy .
sorry to edit this....give me time to edit the procedure---xda2jojo
if you received the "Sorry, this file cannot be patched" error message ..
there are only two reason .. maybe you downloaded a corrupted nk.nbf ..
exact size of nk.nbf
1.50f.00WWE
is 33,554,496 bytes(32,769kb)
1.50f.blWWE (BuzzMobile 2005)
is also 33,554,496 bytes(32,769kb)
but if you think you downloaded it right and still receive this error ..
it only means that you downloaded a already patched ROM and no need to patch it anymore ..
just skip the procedures about patching the rom
and go directly to upgrading
now if you receive a country id Error .. just use modified Himaupgradeut.exe
read the wiki
http://wiki.xda-developers.com/index.php?pagename=Himalaya_2005
to know where you can get the file
Thanks
Thanks
That's cool - thanks!
Bugger - I had to go back down to 2003SE.
No MMS, no Messenger, and no working Activesync. It looked so great too. It was the MMS and Activesync issues that were key for me though. Will wait till a definitive fix is found and try again.
Thanks for your help, though, guys. If I hadn't tried, I'd never know.
Messenger works OK on mine. Activesync works OK on my laptop, but not my Desktop. MMS doesn't work though, yet.
same problem
hey ppl i 2 have the sameproblem my file size of nk.nbf is 32,769 kb is that ok i also do not ahve active sync 4 installe dnither do i have service pack 2 isntalled is it sensible 2 insatall or will it screw up myprecious xda2?plz let me kno asap
thanx
This is how i did it, works to the T 4 me (I Have A Zipped NK.NBF)
Step 1
Unzip From First Part, (It Should Automatically Unzip Second Part)
(Ignore this if you already have unzipped NK.NBF)
Step 2
Using WM2005patch1.exe Patch The NK.NBF File
Step 3
Using ER2003Edit Change The Country Code 2, O2 WWE
Step 4
Run HimaUpgradeUt.exe
Step 5
Once All Installed Reboot Fone And Run ExtROM_WM2005.cab,
ExtROMUnlocker(for_WM2005Only).cab And BuzzWM2005RAMDisk-Full.cab
2 unlock hidden memory!
(Shows 124mb Ramdisk & 15mb Storage formaly known as ExtRom)
Not sure if there is updated ramdisk or not...
My activesync 4 works flawlessy With Win XP Service Pack 2,
MMS Doesn't Work For Me Either,
I have downgraded back 2 wm2003se for this reason...
Well just untill Someone gets it running again...
Good Luck, & Ave Fun! The general layout onWM2005 is great.
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 have a new TyTn now, (lost old one), I changed the boot screen too a CIA one i found.
I cant remember how i did it...
I have search put can only find THIS THREAD but that is for a different
model.
Can some one point me to a thread that allows me to change the TyTn boot screen???
Please.
Depends on which boot screen you want to change. There are three of them. First one when you switch on , second when it initiates the gsm and third is windows boot screen. First two you need to create and flash to your device the third is simply called welcomehead.96.png and resides in the windows directory overwrite that file with one of your own thats 240x320 and it will show on startup
is this the image you are referring to
http://forum.xda-developers.com/showpost.php?p=3078867&postcount=14
If thats what you want to have on your hermes
unzip the first attachment then run the ruu_wrapper copy the welcomehead.96 file over to the windows directory if you want to change the windows mobile loading screen too.
If you fancy creating your own use the splashscreenmaker attached, although its for the artemise it works fine on the hermes and wizard too, not sure about other devices. Just make sure the images are 240x320 and no more than 256 colours(well thats what i have found works)
Oh before anyone asks , as i am sure they will, this will not wipe your phone all it does is upgrade the boot screens
Thanks very much
if i had known that the artemise worked i would of used that.....
no problem steve, was that the screen you wanted
sure was buddy
thanks again
Hi,
I've been trying to locate the "boot photo" on an Amlogic S912 TV box that I have in order to change it. It is the first image that you see when you power the unit on, followed by the boot video which I have already changed and is located in the "etc" folder of the unit. I cannot find the location of the initial photo though. If anyone can tell me what folder it is located in I would certainly appreciate it! I believe it is either in bmp format or png format. The unit is running android 6 and these are the folders that are in the unit. (If this question is in the wrong section I apologize in advance!)
Thanks for any help anyone can offer.
It's not gonna be there. That image is stored in one of 2 places in every device I have had. It was either on the boot partition or bundled with the kernel. Either way you would have to flash the device to change it.
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
fxbill said:
I just discovered that it is in the "logo.partition" which shows up in temp/ level 1 with the Amlogic Customization Tool, but I'd like to find out how to modify that with my own photo and then repack the firmware. Any ideas?
Click to expand...
Click to collapse
You would need to extract that partition and find the file that it is placing in temp. Change the file and refresh the partition. Mind you this is dangerous and doesn't always work. But as long as you ha e an unlocked bootloader you should be able to recover.
The "logo.partition" is a single file in the level 1 temp file directory. It is actually a single file type, but I don't know how to disassemble the file or what program would open it. I can get a hex editor to open it, but that doesn't help me much since it is a 6 megabyte file and the hex, of course, is unreadable...at least to me. There are about 20 files in the level one temp folder of which this is just one. The program works just fine with Amlogic devices that are running Android 5 and below and does almost everything with Android 6, but this is one of the things that it won't do in Android 6 and the Customization program has not been updated for a couple of years. I'm hope that eventually it will be but at this point I need another way or program that will allow me to do it!
Found it..... It's in the Level 2 folder. Easy to put into the firmware once you know where it is!