Yesterday I have not resisted and I moved from T-Mobile ROM to O2 ROM using the file tmobile_t2_16050.rar downloaded form mdkia FTP. The strange thing is that after the upgrade everything remained the same (same software installed, contacts, EVERYTHING, also the extROM version: 1.60.36...) except for the start screen that now shows O2 logo...
What has happened???
Now I'm looking for O2 ROM 1.66, how can I find it?? I looked around but didn't find....
Grazie....
GOT IT!!!!!!
I made a HARD reset and Now I have a Wonderful XDA2 with ROM 1.60.50!!!
First impression: TODAY screen is really wonderful, MUCH MORE THAN MDA2 T-Mobile!!!!!!!!!
Now what I need is 1.66 O2 ROM!!!!!!!! Can anybody help???
peppepep
I'm very interested in your posting. I do not, unfortunately, have an answer for your question, but if you would be so kind perhaps you can help me.
I have the MDA II and I was running the 1.60 ROM with little to no difficulty, except for GPRS not always on, but I fixed that with the tool that is available.
Somehow my device got corrupted and I decided to upgrade to T-Mobile 1.60.36. Well that was a mistake, because I have had a very buggy device for about 2 weeks now, lots of problems.
Are you pleased with the 1.60.50 ROM? How specifically do I do what you did, which is going to the XDA II ROM Upgrade from 1.60.36?
What about the Country ID error I hear about? Does this present a problem?
Please help, I have posted on other threads here to no avail.
Ed
PS: I tried the FTP link, but I could not get connected.
Download the file "ROM TMobile to O2 1.60.50" from mdkia FTP: http://maja.mine.nu:8000/Login
user: xda2
pssw: xda2
I used this file to move form Tmobile to O2. No Country ID error because it has been modifyed by mdkia himself.
Let me know how it goes! (For me OK 100%)
peppepep
Edited: I did find out how to work the RAR File.
Naturaly I'm a little nervous about this.
Please tell me how you like the O2 ROM, and if you had any problems using the T-Mobile to O2 FLASH?
Forgive me, but I'm not familiar with using this type of file (RAR File) to flash my device. I have only used ROM Upgrade Files that provide automatic loading.
Could you please help me in this regard?
Also how do you like the 1.60.50 ROM, from O2?
A rar file is similar to a zip file, it is compressed and needs unzipping before you can use it.
The extended rom/ rar files
I downloaded the rom upgrade and it is fine, but what are we to do with ext_rom_o2_16050.rar.But (1.) What does this extension do? and (2.) How do I load it in in?
I assume you are requesting help to upcak the RAR File? If so:
You need a unzip or unrar file software. I do not recall the name of the software. I did a search and see that there are a few utilities for thiis out there.
I have it at home and could send it to you later.
Ed
Rar file
I can unpack the rar, that's not the problem, just what to do with all those extra files? Those aren't the Rom Upgrade files, they what are they?
I misunderstood your post evidently, and I'm still not clear on what your original post requests. "How do I load it in in?" I have yet to try the ROM Upgrade, but I opened the largest file displayed and it took me to a ROM Upgrade setup. It appeared to me that this is how you load it in. I'm not sure what the other files do, but I bet the utility for the upgrade would take those if needed.
What device do you have?
I own the T-Mobile MDA II, and I have never gone outside the T-Mobile ROM Upgrades. I may, however, because I do not like the current 1.60.36 I'm using. It is not very stable.
I hope T-Mobile comes out with a 1.66 soon.
Related
y saw at www.pocketpartner there is a romupdate 1.72 for the qtec 2020
link:http://www.pocketpc-club.nl/content.php?id=3331.
hein
Thanks!!!
Has anyone tried to upgrade using this ROM? Any problems?
I've posted the last rom french & English one on the following link.
Read what the people says (The roms that I post are original from dangard)
http://forum.xda-developers.com/vie...tart=200&sid=f82d07fe82b956d754c6f2e9845c419f
Kind regards
Problem with the ROM 1.72.03
Hi,
I've install the ROM 1.72.02FRA (ExtROM 1.72.603)
And the MMS composer don't work...
When I launch it, they close immediatly
Can you help me ?
Didier
hein said:
y saw at www.pocketpartner there is a romupdate 1.72 for the qtec 2020
link:http://www.pocketpc-club.nl/content.php?id=3331.
hein
Click to expand...
Click to collapse
I have installed the rom update 1.72.00WWE on a Qtek 2020. It works fine. However I do have a view remarks. I dont see any changes. I thought windows 2003 second edition was installed. The external rom version is 172.125. If I start TomTom3 when the wired GPS is not connected, I get the message "Can not open COM1. Port does not exist". Fortunaly it works well when I connect it. Does anyone know why I do not see any changes in 1.72
Re: Problem with the ROM 1.72.03
Figmentbe said:
Hi,
I've install the ROM 1.72.02FRA (ExtROM 1.72.603)
And the MMS composer don't work...
When I launch it, they close immediatly
Can you help me ?
Didier
Click to expand...
Click to collapse
Hi,
I think that you have make a backup before to install the update & that you have tryed to reinstall your backup after the update.
You have to remain that if you make a backup, you are not able to restore your backup after.
If you do this, you will overwrite some programs (mms,...)
If not give me more details.
Kind regards,
Update from pocetpc-club works fine.
I updated my QTEK with the file as mentioned. It worked fine. Restoring an old backup is not a problem, but doesn't give a full backup, because you restore the old files. So you really have to install everything new.
As far as I can see, there are no problems with the update.
Regards, Luc
Does this ROM update the bootloader?
Hi,
Has any of you who have upgraded to this ROM checked if it also does upgrade your bootloader to 1.06?
Regards,
Mark
Hello,
Mine has upgraded the bootloader to v1.10.
Cheers
BootLoader
Raphael said:
Hello,
Mine has upgraded the bootloader to v1.10.
Cheers
Click to expand...
Click to collapse
Upped and running on i-mate + qtek 1.72 ROMs but still 1.01 here.
Sorry, my mistake , my bootloade is V1.14 with the Dangaard 1.72 ROM.
cheers
@Raphael
Are you sure you'are looking at the right place? Haven't heard yet of booloader newer than 1.06 yet. But that doesn't ofcourse mean that it doesn't exist.
Mark
hmm, it seems that someone is mixing up radio stack and bootloader. have never heard of bootloader newer than 1.06 but radio stack 1.10 1.14 and even 1.17 (in some german replacement devices with 1.72.01GER) is out so far.
greetings from black forrest
peter
Sorry, You're right, had a mix up:V.1.02
No w I start to be ashamed of this mix up.
Cheers
:lol:
Just did a soft reset on mine with ROM 1.72 and I can insure you that
Radio is 1.14
I don't know how to find the "bootloader version" ?
so long
there are two ways of finding bootloader version:
1. you hold power-, 4-way rocker switch and soft-reset and your device goes into bootloader mode (and by the way all of your data is lost, so backup your device before doing that)
2. browse around xda-developers forum and find a tool that is called safebootloader.exe or something like that. this file must be copied to your device. start it and it writes a file where informations about the bootloader is in. open that file with a hex-editor e.g. and you can see the version.
regards
peter
My friend just got the hermes running the crossbow os, would someone tell me how to dump the rom out? Need urgen reply cause he will leave hong kong tomorrow.
First try Buzz's rom dumper. It's available here
There are reports that it won't work which may be related to the Hermes microSD slot. I'd try the miniSD version of Buzz's pgm first.
There are various ways to dump the ROM from a live device, I don't know which one will be the most reliable or will be more helpful to reconstruct the ROM after the dump, so if possible dump the rom in all methods explained here:
1) itsutils pdocread, as explained in the WIKI:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoDumpRom
This is IMHO the most reliable method, first use 'pdocread -l' to list all partitions, then dump ALL them in "raw" files. Feel free to ask if you need help or are unsure in any of the steps.
2) As Sleuth255 suggested, you can also try grab_it! tool from buzz, but I don't know if it will work or not.
3) There is also mamaich's TestWM5.exe, which dumps files and modules to SD card, but I think the dump will not be useful for creating a valid imgfs after, anyway try this method too.
4) It will be also useful if you dump the bootloader on this device: Run gnuharet.exe on the device, then telnet to port 9999 and issue this command: 'pwf splfile 0x30000000 0x40000' in gnuharet.exe
This will dump the running SPL in a file called "splfile" in the folder where you run gnuharet from. It will probably be corrupted by wince usb host buffers, but anyway will be useful too.
Good luck and feel free to ask if you have problems
Suspense is killing me... did we get a dump?
Also please, put the Hermes in bootloader mode (side ok + power button + softreset with stylus) and tell us exactly the IPL and SPL version you see in the tri-color screen. Probably we can investigate how to dump rom parts from bootloader using 'rbmc' command in mtty.
tsuishui said:
My friend just got the hermes running the crossbow os, would someone tell me how to dump the rom out? Need urgen reply cause he will leave hong kong tomorrow.
Click to expand...
Click to collapse
Any progress? Im all tingles here, my wife thinks im crazy...lol cannot wait to get my hands on this one...(and i dont mean my wife)
This should be interesting if he actually gets it
It is as follows
HERM100
IPL-1.00
HERM100 MFG
SPL-1.02
Ok, i will wait a while and I will provide you the commands to dump the ROM from bootloader. Meanwhile download HHD Usb Monitor trial version, and install it.
pof said:
Ok, i will wait a while and I will provide you the commands to dump the ROM from bootloader. Meanwhile download HHD Usb Monitor trial version, and install it.
Click to expand...
Click to collapse
Any idea what the chances are to create a working rom out of this?
I am out of computer right now so i will try to dump the rom later today and my friend tells me that this device is come from microsoft. Also it is the rom from t-mobile.
great news today!
Now I really can't wait for this
http://msmobiles.com/news.php/5846.html
darkjedi said:
Now I really can't wait for this
http://msmobiles.com/news.php/5846.html
Click to expand...
Click to collapse
nice tease...guess i put it up for discussion in our Hermes meeting tomorrow..
Well lookey here! M$ also released a version that runs on the HTC Wizard. The Wizard was their preferred device at MEDC 2006.
I'm really wondering why they called it WM6.0 instead of SE or 5.5...
POF and other more intelligent people than me - if we do get this ROM I am more than happy to act as a guinea pig for this!! I have 2 days off work and a brand new Hermes to mess around with!
LOL I'm sure everyone will want to be a guinea pigs for this
darkjedi said:
I'm really wondering why they called it WM6.0 instead of SE or 5.5...
Click to expand...
Click to collapse
possibly marketing...
Getting the ROM dump is only the first (most important) part. Next the talented folks here at xda developers will need to convert it to a flashable image. The Hermes architecture presents unique challenges here. I'm sure having this dump on the FTP site will add even more incentive to this effort which will also result in our ability to cook our own ROMs....
Hi all,
Thus far has anyone managed to get any version of BB Connect running on WM6?
I have tried but with no joy
I also need help with this. The WM5 ROM had BB Connect pre-installed, but the WM6 one doesn't. Does anyone have the cab from the WM5 one?
ade0282 said:
Hi all,
Thus far has anyone managed to get any version of BB Connect running on WM6?
I have tried but with no joy
Click to expand...
Click to collapse
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)
Steps that I have done:
- Extracted the WM6 NBH (duttys tool)
- Hex-Edited the windows.nb
Original HEX string is:
4D3EA0E3063083E3452FA0E30510A0E302
New Hex string is:
1D3EA0E3013083E3452FA0E30510A0E301
This resulted in os version 5.1.465 (like the original WM5 for Athena)
- Used the Athena_upgrade package to flash this modified windows.nb to my device.
One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.
If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.
- Don't forget to change the AKU to .3.3.1
Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!
Cheers
c0rnholio said:
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)
Steps that I have done:
- Extracted the WM6 NBH (duttys tool)
- Hex-Edited the windows.nb
Original HEX string is:
4D3EA0E3063083E3452FA0E30510A0E302
New Hex string is:
1D3EA0E3013083E3452FA0E30510A0E301
This resulted in os version 5.1.465 (like the original WM5 for Athena)
- Used the Athena_upgrade package to flash this modified windows.nb to my device.
One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.
If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.
- Don't forget to change the AKU to .3.3.1
Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!
Cheers
Click to expand...
Click to collapse
Hi Cornholio: could you help me with more details on the process to charge into the pda this .nb file? I am not sure if needed to join in a full nbh all the diferent files with .nb after extract the rom or is needed only flash the os.nb
I tried unsucessfully the tools you mention and is not possible to charge the os. I think it is due my device is WM6 before..
beginner said:
Hi Cornholio: could you help me with more details on the process to charge into the pda this .nb file? I am not sure if needed to join in a full nbh all the diferent files with .nb after extract the rom or is needed only flash the os.nb
I tried unsucessfully the tools you mention and is not possible to charge the os. I think it is due my device is WM6 before..
Click to expand...
Click to collapse
Hi, you only need to flash the windows.nb file. It should also work if you already have WM6 on it. What has to be mentioned is that the itsutils in the Athena_Upgrade Package also did not work for me so I was unable to read out the handle and flash it, but I've downloaded the itsutils from here: http://nah6.com/~itsme/itsutilsbin-20070705.zip
and they worked without any problem.
c0rnholio said:
Hi, you only need to flash the windows.nb file. It should also work if you already have WM6 on it. What has to be mentioned is that the itsutils in the Athena_Upgrade Package also did not work for me so I was unable to read out the handle and flash it, but I've downloaded the itsutils from here: http://nah6.com/~itsme/itsutilsbin-20070705.zip
and they worked without any problem.
Click to expand...
Click to collapse
thanks a lot, you are great!!!
do you have some instructions on how to do it, please?
read and re-read and found it. Now working...
beginner said:
thanks a lot, you are great!!!
do you have some instructions on how to do it, please?
read and re-read and found it. Now working...
Click to expand...
Click to collapse
Glad to hear that you figured it out. Sorry for not replying, but I didn't had the time to write a step-by-step guide.
c0rnholio said:
Yes. Tonight I took the time to get things sorted. I now have WM6 and BBC 2.1.2.54 running. (Still no luck with BBC4)
Steps that I have done:
- Extracted the WM6 NBH (duttys tool)
- Hex-Edited the windows.nb
Original HEX string is:
4D3EA0E3063083E3452FA0E30510A0E302
New Hex string is:
1D3EA0E3013083E3452FA0E30510A0E301
This resulted in os version 5.1.465 (like the original WM5 for Athena)
- Used the Athena_upgrade package to flash this modified windows.nb to my device.
One word of warning when using this flash method: Be sure to read out the proper handle for the area where the .nb will be stored.
If you want the whole wm6 on your device do the full upgrade with one of the provided WM6-ROMs before flashing the above modified .nb.
- Don't forget to change the AKU to .3.3.1
Thanks to all involved people who provided the tools, wm6 and whatever. You have my greatest respect!
Cheers
Click to expand...
Click to collapse
i see that BB 4 works with Black, for 5.1.195. I tried some hacking for WM6 of Athena but BB 4 doesn't connect. I think it checks something more that the operative version.
beginner said:
i see that BB 4 works with Black, for 5.1.195. I tried some hacking for WM6 of Athena but BB 4 doesn't connect. I think it checks something more that the operative version.
Click to expand...
Click to collapse
BBC 4.* check the ModelID of the device also... hence wont work on an athena.... you have to wait for a version 4.0 for the Athena sorry...
walshieau said:
BBC 4.* check the ModelID of the device also... hence wont work on an athena.... you have to wait for a version 4.0 for the Athena sorry...
Click to expand...
Click to collapse
do you know where it checks it? i have the idea of replace the header of the rom file, that says what device is it, but non sure if i coul brick the device.
I am desperate, I red almost all posted instructions of how upgrade g4 (VODAFONE unlocked, my case) firmware and none works fine with me. I get the new firmware (Qtek_S200_220736_2207116_024721_SPA) for my Prophet I followed all steps and always tell me the same, ERROR[238] FILE READ.
I have tried hundreds times and nothing. Someone can help me?.
Thank you in advanced.
P.D.
This is what I do:
0)Begin installation from Qtek_S200_220736_2207116_024721_SPA.
1)Copy the files from the temporary folder to other location
2)Close the instalation program.
3)Paste into new created directory ROMUpdateUtility_NoID.exe and execute it. Until here, everithing is OK.
4)In the step that the process ask if I want to update my firmware, I click YES and pataboooommmmmm! EROR[238] FILE READ
Its unlocked?
Is The CID unlocked?, I had the same machinne and I was able to upgrade from last spanish ROM version to Touch Xb by Gullum just like a regular G3. Also update Radio, only the Vodafone stiker remains in the case.
Hello!
I' really new here and this is my first WinMo device.
First of all, I want to say that this forum is plenty of information but the problem is that it is too chaotic. So, I'm sorry if there are the answers to my future questions but afer hours and hours of searching I'm still confused/misty/obnubilated.
My problem:
I have an HTC Touch Dual, Orange Romania branded. It has a personalized WinMo 6 and there is not any upgrade facility from Orange to upgrade to WinMo 6.1. It has only English interface, so I think that is an WWE version.
I want to upgrade my phone to the official ROM (released in 9/10/2008) but ,first off all, I'll need to backup all my Orange-Ro ROM, to restore it in case of malfunction (sending to service) and...the most important for our community, to share this ROM to other members (especially Romanian ones) who need to restore their Orange-Ro ROM. There is not any of Orange-Ro ROM on the Internet (all the Internet!).
Well, as I said, I'm new and...noob.
I want an actualized tutorial of dumping and rebuilding ROM from those 4 files obtained. „Actualized” because of the fact that the most of the indications of dumping and rebuilding are obsolete/old.
My questions:
1. for dumping, do I need to Hard-SPL and CID-Unlock my locked device?
2. Will dumping a locked, branded ROM preserve all its state (settings, splash screen etc)?
3. Do I need to hard reset my device to return to its factory state before dumping (I want this rebuilded ROM to be „pure” withowt traces of my presence).
4. I've found this Guide for Dumping Niki . Is it still good?
5. Where can I find the „Reconstruct a Dumped ROM from Niki” Guide, to make it "flashable".
Here i found some indications from tom_codon
What we need to do now ?
1. Copy part02.raw u dumped from original rom to Tools folder and run step1.bat
2. Extract RUU_signed.nbh from Ship rom and put in ShipRom folder.
Link download :
http://www.asia.htc.com/download/RUU_Nike_HTCASIA_WWE_1.31.707.09_Radio_Nike_1.58.1 6.27_signed_Ship.zip
Or here :
http://www.asia.htc.com/download/RUU_Nike_SingTel_WWE_1.31.871.14_Radio_Nike_1.58.1 6.27_signed_Ship.zip
3. Run Reconstruct a dumped rom.cmd in my Tools and wait some times.When page DOS done it will exit .U go to Update_Rom folder already have new RUU_signed.nbh.This files reconstructed your original Rom with your languages.
Have funs..!
Click to expand...
Click to collapse
So what about part00.raw, part03.raw and raw04? For example I know that part00.raw IPL, SPL and Splashscreen. I'll need the Orange Splashscreen for this ROM (in fact, I need a perfect copy of this ROM). Can I put all the raws in the „Base ROM” folder?
Also, the "RUU_signed.nbh"file from Ship ROM...
I want to remember that the Orange ROM is a WinMo 6 one!
Thanks in advance. I'll be back for new questions.