Related
Upgrading Extended ROM from Imate to TMobile Extended ROM, Easy As 123 Please follow the Steps
1. Get hexeditor
2. Download TMobile 1.60 and extract it to get ms_.nbf
3. Download I-Mate Ruu15283WWE and extract to get ms_.nbf
4. Open Both Files in hexeditor, please remember both files so you will get confused.
5. if you are having T-mobile and want to upgrade to I-mate Extended ROM you have to do the following in reverse.
6. Copy "2d 43 44 4c 00 00 00 00 " (-CDL....) and paste it to T-Mobile ms_.nbf, location "2d 54 4d 4f 42 49 4c 45" (-TMOBILE) , This is the Version.
7. Copy "62 34 34 39 38 64 31 34" (b4498d14) and paste it to T-Mobile ms_.nbf, location "65 38 34 31 37 61 63" (e8417acd), this is the CountryID
8. Save the T-mobile File to c:\New folder\ms_.nbf
9. Include in the New Folder "HimaClearJumpCode.exe","HimaGetDeviceData.exe", and "HimaUpgradeUt.exe".
10. Start to run the "HimaUpgradeUt.exe" and it will start updating your mobile.
Have fun and enjoy your new extended rom.
8)
ROM Version : 1.52.00WWE
ROM Date: 10/23/03
Radio version: 1.06.01
Protocol version : 1337.16
ExtROM version : 1.60.06
Next i will try to update my I-mate 1.52 nk.nbf to T-mobile nk.nbf but not the radio because radio will not work with my area.
Thanks!!!!
Let me try it!
the 8 hex digit number is not the country code, it is the sum of crc's of 256k blocks of data of the file.
see http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html
for a tool to calculate it.
soon an adaptrom version will follow.
a warning though: if an upgrade fails, you may be left with an unbootable device. you can use xda2dmp to fix this in most cases. ( I hope )
also DO NOT consider trying out 'HimaClearJumpCode.exe', it will make your device unbootable. and you will have to figure out how to use xda2dmp to fix it.
Update I-MATE ROM to T-MOBILE or backward ?
Hello,
I have an I-MATE and sometime ago updated to T-MOBILE ROM 1.6
Later on I-MATE released their own ROM update and when I tried to install it, even knowing that it is "lower" version - I got message that "Country Code ID is incorrect" (I am sure it is already known issue for XDA II community )
1. Is it make since to go waist a time and try go back in lower I-MATE ROM?
2. and if 1 is YES, how to change Country Code ID so installation of I-MATE will proceed further?
I would really appreciate reply from XDS developers.
Thank you
Paul
I did test it.
This method not only allow to install the extended rom it self , but allow the machine to flash the full set of rom!
Moreover, after flash the new rom, it will keep the country id of the new rom, not the old rom.
I found the bug, the problem is that the language of the device is reported as 'WWE'
maybe you can change one of the language identifiers in the binary of HimeUpgradeUt.exe.
or as I just noticed. the update tool in the Update.rar attachement in this thread http://forum.xda-developers.com/viewtopic.php?t=4785 has a updated version of the upgrade tool, which does know 'WWE'.
More interesting things :
1.All rom files (extended / radio / ce rom) has countryid inside the files. However if the ms_.nbf passed the countryid check, the rest of the rom will be allowed to flash, even the country id is wrong.
2.If you just want to upgrade a radio that not belongs to that countryid, just rename the company name of the radio rom by hexeditor to the machine's countryid (it is in the first few lines of the radio.nbf),
3. I can't find the country id inside the nk.nbf but it seems himaupgradeut.exe may not regonize a nb.nbf from different upgrade set.
For safe , use the himaupgradeut.exe comes with nk.nbf to upgrade the cerom
4. If you want to upgrade the CE ROM will different countryid, you must upgrade the extended with modified countryid too.
For example, I want to upgrade the CEROM to T-Mobile 1.60 CE ROM, but I want to keep the O2 1.52 extended rom, I have to
a. mod the T-Mobile extended rom's country ID / CRC to O2 countryid /CRC
b. upgrade the moded t-mobile extended rom with himaupgradeut.exe
c. Your device is now recognized a a t-mobile device. Use T-Mobile's himaupgradeut.exe to upgrade the CE rom to T-Mobile 1.60.
d. mode the o2 extneded rom's country ID / CRC to T-Mobile's countryid /CRC
e. upgrade the moded o2 extended rom with himaupgradeut.exe
It looks like very stupid, so we need want a new adapt rom and we love XDA-developers 8) .
1: also the checksums is only verified for the nk.nbf
3: nk.nbf is encrypted, decrypt it with xda2nbftool. then you can see the countryid.
4: I saw that the extended rom, is where HimaGetDeviceData gets the language/country id from.
"XDA developer Itsme" the 8 hex digit number is not the country code, it is the sum of crc's of 256k blocks of data of the file.
Click to expand...
Click to collapse
ahhh ic.. :?
killercheung said:
It looks like very stupid, so we need want a new adapt rom and we love XDA-developers 8) .
Click to expand...
Click to collapse
I agree with this :wink:
I try to search difference between nk.nbf and the other version nk.nbf, the Qtek2020 ver 1.60 nk.nbf is almost the same as I-Mate 1.52 nk.nbf, but with T-Mobile, it is totally different.
I will still try untill my unit becomes a paper weight, just to get that countryID error. it should be flexible like the old one.
XDA developer Itsme said:
I found the bug, the problem is that the language of the device is reported as 'WWE'
maybe you can change one of the language identifiers in the binary of HimeUpgradeUt.exe.
or as I just noticed. the update tool in the Update.rar attachement in this thread http://forum.xda-developers.com/viewtopic.php?t=4785 has a updated version of the upgrade tool, which does know 'WWE'.
Click to expand...
Click to collapse
i get the update.rar from the files of I-mate 1.52.. I think the version is WWE. :roll:
XDA developer Itsme said:
1: also the checksums is only verified for the nk.nbf
3: nk.nbf is encrypted, decrypt it with xda2nbftool. then you can see the countryid.
4: I saw that the extended rom, is where HimaGetDeviceData gets the language/country id from.
Click to expand...
Click to collapse
Where can I possibly get this file "xda2nbftool"
Suceed!!!!!.. because I update Already my I-mate 1.52WWE Extended ROM to T-mobile 1.60 Extended ROM, I successfully update all the upgrade within T-mobile 1.60 (nk.nbf, ms_.nbf, radio_.nbf), The CountryID error didn't appear anymore, the upgrade that I done with Extended ROM change my Country ID to what ever Extended ROM I update my device, the countryID is in extended rom(ms_.nbf) , now everybody can change thier unit to whatever update they want.
Thanks for the Help of XDA-Developer Team. More power 8)
another thing I noticed is that the password used for the nk.nbf encryption is different for each upgrade tool version:
v0500 uses password 'HTC'
v0600 uses password '921211'
so, yet another update to my xda2nbftool
now also has an option to change the crcsum in the file.
Thanks for XDA developer Itsme again
Finally I can change countryid of a TMOBILE rom to flash on an O2 Device.
However I found that himaupgradeut.exe v0500 come with the TMOBILE can't flash the rom (It reported MODEL ID error), but v0600 is OK.
I got an XDA2 , it will report country ID error when use TMobile's upgrade utility, but I want to upgrade the CE ROM to TMOBILE 1.60 WWE version.
Here is what I did :
1. decrypt the T-Mobile 1.60 CE image
run "xda2nbftool -d nk.nbf nk.nba HTC"
Because T-Mobile 160 upgrade rom is come with himaupgradeut v0500, therefore the decrypt code is "HTC"
2. Use HEX Editor change the nk.nba countryid from T-MOBILE to O2 (It is in the first line of the rom)
3. update the crc checksum of the nk.nba
run "xda2nbftool -c nk.nba -u"
4. encrypt the T-Mobile 1.60 CE image. Because I cannot use himaupgradeut v0500 to update, I have to use v0600 and the encrypt code is 921211
run "xda2nbftool -e nk.nba nk.nbf 921211"
5. Run the himaugradeut.exe v0600 to upgrade your rom!
I got one more question.
Is that the rom content inside the decrypted nk.nba identical to the rom dump by xda2dump ?
Because I tried to copy a xda2dump version of XDA2 Chinese 1.52 rom and copy the content from address 0x1000h ( Something like D300A0E300F0 in HEX code) to the end, and overwrite the 0x411150h - the end of a TMOBILE 1.60 nk.nba with the chinese rom content , and fill the end of the file to 0x1f80030h with 00 . I can flash the rom to the device without any problem, but it stop in the 1st boot screen.
The chinese is working with the bootloader SD card upgrade method.
What's wrong with me?
Thanks.
XDA developer Itsme said:
another thing I noticed is that the password used for the nk.nbf encryption is different for each upgrade tool version:
v0500 uses password 'HTC'
v0600 uses password '921211'
so, yet another update to my xda2nbftool
now also has an option to change the crcsum in the file.
Click to expand...
Click to collapse
Hello XDA developer Itsme, can you send me this file/site "xda2nbftool", because i can not access it here, i think the site is forbiden here, thanks in advance
here are the tools attached
XDA developer Itsme said:
here are the tools attached
Click to expand...
Click to collapse
Thanks... :lol:
killercheung: it is almost the same. the decypted file has a 64 byte header, followed by the rom found with xda2dump at offset 0x80040000.
I don't think you can mix roms like you describe.
Anyone know how to translate this ROM 2.20Chinese to English...
so we can have wmp10 in our XDA, and other features that is better than 2.06 and 2.02 ROM....
mamaich : can you teach us how to translate the english langguage, or you can upload this rom 2.20 that have been translate to english in this forum... big hope
Or the original rom of 2.20 CHS because when i try to download through the link you provided.... I always cannot completed the download and that file was not on your website (when i try to visit the page directly).
thx in advance
I also have mailed some days ago to Mamaich asking for some info about Win2k3se and Wmp10 translation..
Now we all waiting..
The test version of English ROM made from chinese 2.20 is uploaded to http://mamaich.kasone.com/imate/en.rar
archive contains nk.nba file that should be processe d with xda2nbftool and flashed.
I've uploaded mkrom toolkit used to create this ROM to: http://mamaich.kasone.com/imate/mkrom_220chs.rar (18.5 mb)
Original toolkit is taken from http://wiki.xda-developers.com/wiki/mkrom
To use it you'll need Linux or CygWin enviroment (I use cygwin), Perl, hex editor (I use HIEW). You should place new files to files1...files5 directories. Here is the maximal size these directories can be:
Files1: 655360 bytes
Files2: 1245184 bytes
Files3: 262144 bytes
Files4: 524288 bytes
Files5: 1114112 bytes
Toolkit would not warn you if this size is exceeded and would produce dead ROMs.
Files1 folder should contain mxip_MYXIP_100.rgu file which is a modified registry. CreateEngLinks.exe is a program that runs after hardreset and creates english folders and links. I was unable to patch the initobj.dat and default.fdf files in ROM, so I had to create this program.
cfg\os.nb1 is a "base" ROM image with some files renamed. You should not touch default.fdf, initobj.dat and kernel.rgu
When you run ./a.sh file it would produce a new ROM named nk.nb1. Use any hex editor to place this file to offset 0x40040 of NK.NBA I've posted in the prev. message and modify it's CRC and encrypt:
xda2nbftool.exe -c -u NK.nba
xda2nbftool -x NK.nba NK.nbf 0x20040304
Use this toolkit at your own risk. Addresses in ./a.sh are taken from 2.20.07 chinese simplified ROM and should be modified to be used with other ROMs. You may completely destroy your device if this toolkit is used incorrectly.
Hey mamaich,
that's perfect! THANX
Let me try it now...
buzz
Hi Mamaich... can you tell me what is the difference about this two files or links.
1. http://mamaich.kasone.com/imate/chineese_se.rar
2. http://mamaich.kasone.com/imate/en.rar
Is the number 1 totally 100% Chinnese? and the number 2 is 80% English, 20% Chinnese?
Thank You...
double_ofour said:
Hi Mamaich... can you tell me what is the difference about this two files or links.
Click to expand...
Click to collapse
hey double_ofour, it's written in mamaich's post above...
The test version of English ROM made from chinese 2.20 is uploaded to http://mamaich.kasone.com/imate/en.rar
I've uploaded mkrom toolkit used to create this ROM to: http://mamaich.kasone.com/imate/mkrom_220chs.rar (18.5 mb)
Click to expand...
Click to collapse
XDA2 WM2003 SE 2.20.07 WWE
Hi,
for your convenience I just created regular upgrade package out of mamaich's nk.nba file.
PERFECT WORK mamaich... )))
It is Country ID and Operator ID INDEPENDENT, however it will change your device to Qtek + WWE after upgrade.
If you don't like that, just edit .nbf files yourself.
OS version 2.20.07
Radio version: 1.18.00
Extended ROM is NOT included, because I believe, that anyone can build his own Ext ROM to suit his personal taste...
Get it here:
ftp://xda:[email protected]/Himalaya_SE/Himalaya_WM2003SE_2.20.07_Upgrade.zip
Unpack and run HimaUpgradeUT.exe
buzz
Hi.. is that 100% english or youve just rip it to mamaich room? still 80% English? sorry for this stupid question...
RE
Hi!
What are the major differences between the WM2003se Chinese-to-English ROM vs the available other 3 English ROMs
I suppose it can read/write chinese sms without the use of 3rd-party program?
How's the bluetooth performance? Still has the vanishiing Headset icon on the Today screen?
Thanks
i upgraded with the 2.20 file, anything runs fine, except, i can't turn on my qtek2020 with any button, neither the power button, nor the application buttons. only way to turn it on is doing a soft-reset or getting an incoming call..
what went wrong with the update??
regards epo
Great work mamaich and buzz_lightyear!!! Unbelievable work the both of you!!!
I have not yet tried and will do so in due time, but I am fairly certain that it is yet another accomplishment to be highly commended...
- Cheers and thanks again for the excellent work
Hey Epo.... is it full english? ot still like the same with mamaich rom?
it seems to be fully english.. anything works fine, except i can't turn it on with the buttons..
ok, now it works, seems to be a problem of my extended rom..
i reflashed it without executing the extended rom and now it works!
great work mamaich!!!!
Hi all, few questions ...
1. Does this ROM still have the hide&seek effect with the BT profile plug-in ?
2. The other 2 versions have only 3 alarms for the clock, and I really miss the 4th one in 1.72
3. It took me some time to localize the 2.06 one on my I-mate, did any one try this ROM with the arabic language ?
The MOST stable rom from among SEs
Hi,
Thanks Guys!
This is the most stable one from all SEs.
To make it more stable, turn off your radio when doing soft-resets and don't install or edit any language registry values! And don't use software that works with them, such as LENG and other.
Does anyone know how to enable russian language input mode now?
Rom: 2.20CHS
Radio: 1.18
Ext: 1.72-IMATE
Some Anomalies?
Hi!
When I open Programs -> File Explorer -> My Documents, I see some folders with square boxes as folder names. Any purpose for these folders? They are empty. Can I delete them?
One thing I found is that when my phone is off my O2 II will soft reset if I tap the GPRS icon on the Today screen top bar. Is this normal or am I getting a new soft reset button?
Thanks
:roll:
More square boxes
Again, when I go to Programs -> File Explorer -> Program Files I see a square box folder. Another thing is that there're two WMP folders. One of them is Windows Media PlayerCS which on opening display square boxes
Next, is if I go to Windows I see a square box folder right on the first line. If you tap on it it'll open with more square box folders and the icons - Help, Calendar, Phone, Contacts and Messaging come with square box names.
I presume all these square boxes are in chinese not properly translated yet.
Hope to see an updated version soon
Thanks
Hi,
I see square boxes in the "Connections" settings panel too.
Good work!
Thanks,
@ngel
Hi there,
i have a problem, my hermes did a hard reset (after playing with Sktools) ,and the bad thing is that i took all the cabs out of the extrom to free space and install other( prog not cab).
Now, after using V3a unlocker and the cab mountAllExtom, i see the ext rom
and can erase progs in it but the memory remains in use . i only have 0.84 M free .
can someone help me to recover all that precious space
Thank you
Thierry
Belgium
mth said:
Hi there,
i have a problem, my hermes did a hard reset (after playing with Sktools) ,and the bad thing is that i took all the cabs out of the extrom to free space and install other( prog not cab).
Now, after using V3a unlocker and the cab mountAllExtom, i see the ext rom
and can erase progs in it but the memory remains in use . i only have 0.84 M free .
can someone help me to recover all that precious space
Thank you
Thierry
Belgium
Click to expand...
Click to collapse
I'm not sure if this is the best way, but try to upgrade to lastest LVSW that includes Extended ROM, so after the upgrade, you can unlock in the same way you do in the past and use the 10Mb extra space.
Of course, if you are not planning to upgrade to WM6, don't follow me
REgards.
thank you jcespi2005
but i prefer to stay with a french and stabel rom. Are they any french patche for this rom.
Th
flash a NBH containing only an extrom using HardSPL, this will fix your issue.
Thanks Pof,
but i am a beginner.
Where can i find it or how can i do it ?
TH
wiki and forum, search for: nbhextract, nbhgen, hardspl and customRUU.
1) Flash HardSPL (latest version) on your phone
2) Extract ExtROM.nb from any shipped NBH (it doesn't matter which one) using nbhextract
3) Convert ExtROM.nb to NBH using nbhgen
4) Flash your newly created NBH file containing only ExtROM into your device using CustomRUU, make sure to start the upgrade in bootloader mode with activesync disabled.
super
muchas gracias Pof
I'll let you know if i succed
Thierry
Use the same guide here but change the technique to Ext.ROM only and don't select the OS.nb. In other words it's exactly the same steps exept for one.
filehttp://www.mrvanx.myzen.co.uk/hermes_guide/Downgrade/
ok sniper251
this means i only have to "click" on the extrom button and disregard the others ?
Yes and don't forget step #4 in Pof post assuming you have Hard Spl 1.40olipro.
Also you can check wether the .nb file is good or not before conversion using the file attached.
It worked fine to extarct the extrom.nb but which command do i need to execute the NBHgen ?
BTW i could not download the koch generator
Thanks for help
Thierry
i succeed in doing all the works and....it works
Thank you so much for ur help Guys
Th
mth said:
i succeed in doing all the works and....it works
Thank you so much for ur help Guys
Th
Click to expand...
Click to collapse
congratulations
Wellcome to the game.....
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
Hello guys i have just moved from HTC Wizard Thread because i have sold my old Wizard and have bought my brand new T-Mobile MDA Vario IV. Flashing, Dumping, etc on Wizard was really simple. But in Touch Pro i cant get through the all things. Maybe it is my not very good technical english or something. All i do is just reading and reading and cant get through. So I have still my stock ROM for Vario IV wich is even slower than Wizard custom ROMs, so its annoying a lot and it is still slow after i made all the registry tweaks! I would like to flash new faster ROM but i do not want to do it until i am sure i could reconstruct my stock ROM in case of some warranty isues. First thing i want to say is that i use Windows Vista Bussines x64 so maybe all my problems are in the case of 64bit drivers, but i did not find any compatibility information about all the utils.
1. I went to the thread how to dump and reconstruct Touch Pro ROM. I made all the necesary things but i cant even extract any raw file still get ITReadDisk error which i find in the thread but i did not get any solution.
2. I have downloaded T-Mobile ROM from czech T-Mobile official pages extracted the file RUU_signed.nbh, but i do not know how can i extract it. ROM kitchen did not help, or even if i can use it to reconstruct :-(
3. I tried NBHextract file but i think it is not usable for Touch PRO. I got few files SPL, 2x MainSplash and OS image, all *.nb, but i am not sure if i can use it to reconstruct original ROM.
Point of this, why i want ot do it is: I want to load HardSPL but i want to have backup of my stock SPL if i need to revert my warranty. Any help would be appreciated
I use Calkulin's Kitchen, which makes it easy to extract the RUU_signed.nbh and rebuild it. See the thread here or download the kitchen.
What program did you use to extract the ROM from your device? I used pdocread which worked great. Not sure if that works on Vista x64.
rsw686 said:
I use Calkulin's Kitchen, which makes it easy to extract the RUU_signed.nbh and rebuild it. See the thread here or download the kitchen.
What program did you use to extract the ROM from your device? I used pdocread which worked great. Not sure if that works on Vista x64.
Click to expand...
Click to collapse
I used pdocread.exe file but anytime i tried to dump rom i got the ITReadDisk Error, and any RAW file was not made just the first one with 0B size. Also i have downloaded the Raphael kitchen from http://forum.xda-developers.com/showthread.php?t=411915 and my Symantec endpoint security reported Trojan Horse in RaphaelCustomRUU.exe in Tools directory.
Sounds like it is not 64bit compatible. Any reason your running 64bit Vista? Unless you have a need for it your not going to see much performance difference on a desktop, just a hassle of compatibility problems with hardware that doesn't have 64bit drivers.
If you use Calkulin's Kitchen you will need the imgfstools from the Raphael kitchen you downloaded. They have been patched to allow ROMs to be larger than 128MB.
reason i run 64bit vista is that i have 8GB of RAM because i need to run multiple os in vmware. Will try it from win xp in vmware...
Anyway. Can i flash original ROM with all its parts shipped from T-Mobile to a device which has HardSPL applied? If i did that on HardSPLed HTC Wizard, i would have brick it...that is why i am asking.