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 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.
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).
ok right now i'm running the love rom on my g4 wizard. how do i reflash my original cingular rom? i know, it sounds like a nub question but here is the problem. it will flash then hang at 80% and the progress bar will turn red. it will then pick up again and continue to 95% then turn red, fail and say error 326 invalid command. i downloaded the updater directly from htc.
any ideas guys?
Yeah it doesnt work....Your now stuck with the Wizard Love Rom or you can upgrade to another rom but you cant go back to the original Cingular Rom.
internetadam4657 said:
ok right now i'm running the love rom on my g4 wizard. how do i reflash my original cingular rom? i know, it sounds like a nub question but here is the problem. it will flash then hang at 80% and the progress bar will turn red. it will then pick up again and continue to 95% then turn red, fail and say error 326 invalid command. i downloaded the updater directly from htc.
any ideas guys?
Click to expand...
Click to collapse
internetadam4657 said:
ok right now i'm running the love rom on my g4 wizard. how do i reflash my original cingular rom? i know, it sounds like a nub question but here is the problem. it will flash then hang at 80% and the progress bar will turn red. it will then pick up again and continue to 95% then turn red, fail and say error 326 invalid command. i downloaded the updater directly from htc.
any ideas guys?
Click to expand...
Click to collapse
That ROM is for a G3 Wizard, Check your PM's
ok i reflashed with your method and i'm back to my cingular rom. thanks a lot!
(big reason to go back was it was the only rom that my school's wifi app would work with, plus the love rom in combo with orwells wm6 wasn't cool. that splash was ugly IMO)
internetadam4657 said:
ok i reflashed with your method and i'm back to my cingular rom. thanks a lot!
(big reason to go back was it was the only rom that my school's wifi app would work with, plus the love rom in combo with orwells wm6 wasn't cool. that splash was ugly IMO)
Click to expand...
Click to collapse
If you were talkin' to me...glad I could help...one question though...
did your ext Rom install on its own?
no, i still had a blank ext rom as i had to setup all my internet settings, etc again. how can i fix that one?
internetadam4657 said:
no, i still had a blank ext rom as i had to setup all my internet settings, etc again. how can i fix that one?
Click to expand...
Click to collapse
All you have to do is download and install the Ext Rom cabs manually. This may still be available on the ftp. If not PM me.
It worked for me
Thanks a lot ercave1, the ROM flashed flawlessly, however the EXT ROM didn´t came up by itself. The features I´m missing are as follows:
1.- USB switch to select activesync mode to serial or RNDIS is missing, regardless this USB sync to PC (Activesync 4.5) is alive and working well.
2.- ClearVue pdf is missing, not a big loss and I really don´t care since there´s another alternatives to read and diisplay pdf documents.
3.- GetGood and in general all connection settings! I don´t give a s**t!!
4.- MIDlet Manager, big loss... I´m going to keep trying to download Risidoro_Intent_MIDlet_ Manager_V11 whenever the ftp be up and running again. So no worries.
5.- Voice Speed Dialing Settings icon in both the Program ans Setting screens are missing, however the software is running when I press the known VSD button.
6.- Cingular carrierlogo! I don´t care I have my own logo.
And I guess that´s it !
Regardless the comments above, I´d like to learn how to "extract" the correspondent EXT ROM cab files, if you guys have and advice on it would be great.
Thanks again ercave1 for the big help
internetadam4657 said:
no, i still had a blank ext rom as i had to setup all my internet settings, etc again. how can i fix that one?
Click to expand...
Click to collapse
luiggi said:
Thanks a lot ercave1, the ROM flashed flawlessly, however the EXT ROM didn´t came up by itself. The features I´m missing are as follows:
1.- USB switch to select activesync mode to serial or RNDIS is missing, regardless this USB sync to PC (Activesync 4.5) is alive and working well.
2.- ClearVue pdf is missing, not a big loss and I really don´t care since there´s another alternatives to read and diisplay pdf documents.
3.- GetGood and in general all connection settings! I don´t give a s**t!!
4.- MIDlet Manager, big loss... I´m going to keep trying to download Risidoro_Intent_MIDlet_ Manager_V11 whenever the ftp be up and running again. So no worries.
5.- Voice Speed Dialing Settings icon in both the Program ans Setting screens are missing, however the software is running when I press the known VSD button.
6.- Cingular carrierlogo! I don´t care I have my own logo.
And I guess that´s it !
Regardless the comments above, I´d like to learn how to "extract" the correspondent EXT ROM cab files, if you guys have and advice on it would be great.
Thanks again ercave1 for the big help
Click to expand...
Click to collapse
Yes, this is because the Ext Rom was wiped out by the G3 Rom having been flashed on your G4 devices. I don't remember reading about a fix for this, but you may want to search through the forum. The only solution I'm aware of is to install the Ext Rom manually.
I'm glad you guys got the device running again.
Regards,
ercave1
luiggi said:
Regardless the comments above, I´d like to learn how to "extract" the correspondent EXT ROM cab files, if you guys have and advice on it would be great.
Click to expand...
Click to collapse
What do you mean with 'extract'?
1-From the RUU exe file?
2-From nk.nba?
3-Phone disk dump?
4-WinCE disk reading?
Reflashing ExtROM CID Locked
Who knows Russian go to http://4pda.ru/forum/index.php?showtopic=32996 & read my post
And the one who does not know it?
thanks to: Murchelago
literal from the Russian to English
it is the first step. if someone can polish it (I do not speak English good).....
_________________________________________________________________________________________
Already many know that mun built Shell Of tool, which was capable of pouring axis into Wizard G4 with [lochennym] [Sidom], but to the enormous regret it does not know how to pour with [ekstrom].
Recently it decided to be played a little with the program of nb2nbf and to verify, is it possible by nevertheless any means to renew also Extended Of rom to CID-Locked apparatuses. And which there was my happiness, when I revealed after [pereproshivki] that he renewed.
It decided by the same method to try to flood Splash Of screen and HTC Of logo - everything proved to be very simply.
In view of the small quantity of information on the forum on [devaysu] Of wizard G4, it decided to build brief instruction on its [pereproshivke].
1. We stitch through apparatus by pure piercing - Wizard_Love_2.26.10.2_WWE_Novii+CF2.
http://rapidshare.com/files/8651097/Wizard...E_Novii_CF2.rar
2. By the program of typho5 we unpack nbf the file of piercing, which we desire to pour into the beast.
First we fill up into the folder with the program of nbf, and then start with the parameter of typho5.exe - x nk.nbf. After procedure we obtain several files, in number of which is contained OS itself, Extended Of rom, and also as a rule Splash Of screen and HTC Of logo.
([ZY]. For convenience in the use of program made [batnik]. Simply you will place nbf into the folder and will neglect typho.bat)
3. Now we gather our nbf file, each at will can include any desired components in it, naturally, except axis itself.
4. We go in very [progu] of nb2nbf and we make the following tuning:
- We establish Model ID: WIZARD
Language: it is empty
OEM: it is empty
Operator of version: it is empty
CID: it is empty ([ochen]_[vazhno]); remove the numbers, which are contained inside the field
- We establish [galochku] opposite “File of # 1”, we click on the button of survey (button with three points), we find the file Of extended Of rom' and (in the folder of typho5, the exemplary name of 9b000000-Extension.nb)
- In the field “Of start Of address” we enter 9b00000
- In the field “Of image Of name” we enter Extension Of rom (not Extended Of rom, you be attentive!!!)
- In the point “Of file of # 2” we find Splash Of screen, in the field of address we enter 92000000, in the field “of image of name” we write Splash Of screen.
- In the point “Of file of # 3” we find HTC Of logo, in the field of address we write 9d000000, in the field “of image of name” we write WITH HTC Of logo.
- We press button “Translate”
- Extended ROM is ready, it is possible to stitch through.
Unnecessary for you files it is possible simply not to include, but to insert, for example, only one by [ekstrom].
5. We place the obtained file of nbf into the folder [proshivalshchikom] and start. Procedure as with the usual piercing, lasts in all the pair of minutes.
6. We pour the axis Of shell Of tool' ohm from mun' of a.
Finale - valuable piercing
Don´t know
mestrini said:
What do you mean with 'extract'?
1-From the RUU exe file?
2-From nk.nba?
3-Phone disk dump?
4-WinCE disk reading?
Click to expand...
Click to collapse
I really don´t know from where and how mestrini, that´s the reason why I quoted the word extract and included the word learn
luiggi said:
I really don´t know from where and how mestrini, that´s the reason why I quoted the word extract and included the word learn
Click to expand...
Click to collapse
I enumerated the options since each have its own reason
1- Use Winrar to open RUU.exe and use typhoonnbfdecode.pl to extract the 10MB file (0xA00000 bytes) of the extended rom from nk.nbf
2- oops, same as 1 (and its nk.nbf- not nk.nba). hehe, my mistake
3- use pdocread.exe to read BDTL1 - or TRUEFFS_DOC1 (use my Wizard Service Tool as it can be done with a few clicks )
4- Unhide extended_rom and use Active Sync to copy the files to PC (or, once again use my tool to do the same )
cheers
Sounds great to me!
mestrini said:
I enumerated the options since each have its own reason
1- Use Winrar to open RUU.exe and use typhoonnbfdecode.pl to extract the 10MB file (0xA00000 bytes) of the extended rom from nk.nbf
2- oops, same as 1 (and its nk.nbf- not nk.nba). hehe, my mistake
3- use pdocread.exe to read BDTL1 - or TRUEFFS_DOC1 (use my Wizard Service Tool as it can be done with a few clicks )
4- Unhide extended_rom and use Active Sync to copy the files to PC (or, once again use my tool to do the same )
cheers
Click to expand...
Click to collapse
Thanks a lot mestrini, I appreciate your input and I´ll give it a try right away!