Related
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.
OK Guys. Problem Solved : Dead devices due to tmob 1.72 + Downgrade
Problem: New version changes Device ID, as well as ID format.
If you upgrade to tmob 1.72, you cannot downgrade back, as you cannot supply valid NBF files for the new device ID. If you try to play around, you end up with a very dull bootloader screen "Serial V.1.06", and nothing more can be done. SD card images cannot be flashed due to the same reason.
Untill our developers come up with a simple tool, the following 2 solutions can be used to get out of the disaster:
Solution 1:
(tested and 100% working for both dead devices stuck in bootloader and devices working but stuck with the tmob 1.72 version.)
You will need a working device (with old ROM before 1.72), besides your dead one.
1. Prepare your DEAD device in Bootloader mode. Don't connect it yet. (If it is still working but you want to downgrade, press Power+Action+Stylus, if it is already stuck in bootloader, just reset with stylus).
2. Connect your WORKING device, with OLD version via activesync.
3. Start the rom installation of your choice normally, with a version compatible with this WORKING device (Official or Modified NBF files via HymaUpgradeUT). If you don't know what I am talking about, just use your official file downloaded from your WORKING devices' provider).
4. Press NEXT, untill you are presented with the Current version and the one that will be installed. DO NOT click "UPGRADE" yet. (If you got an error so far, you are not using the correct version for your working device.)
5. When you get the dialog with the versions, disconnect the WORKING device from the craddle and connect your DEAD device, in bootloader mode.
6. Click "UPGRADE" and go get yourself a drink.
Et Voila.
Thanks to Victor for inspiring this solution.
Solution 2:
If you don't have another working device, and only have a dead one stuck in BootLoader, you can flash the attached image, through SD card. It will bring back your device to life with the BETA tmob 1.72 CE ROM.
Write the image to the card using "NTRW". Info on SD images and NTRW can be found in this forum.
Unfortunately, i don't have device even with working bootloader And it stuck in TMObile screen
I am sorry I have no solution for screwed Bootloaders, but if your device loads into the tmob screen, there must be something there still working. The only thing I can advise is to try to hard reset and not go into the extended ROM setup files (Soft Reset right after the Hard Reset and welcome procedure), but I guess you don't reach that far ....
What is about for XDA 1?
HI !
I have a Dead XDA. The bootloader is OK. How can I do with it ?
I need some advice for doing it, please !
Best reguard,
Carlo & Victor... You are GREAT!!
Okey.... I will try FIRST!!
please, where is the officiale t mobil rom ? we all have the beta (and thee pb you solve) but not the official one...
thanks
When i posted the T-mobile 172 rom i did not know how much greif it would cause people, sorry to everyone for this
As to the second solution using the SD card is it possible to use this method on a working XDA2.
Basically i have a UK XDA2 and of corse i getthe ID error if i run the upgrade, i dont understand very well how to change the ID part so could i just make the SD card with the rom on it and follow your instructions to recover a dead XDA2
Thanks
John
What should I do when I want to upgrade/downgrade...
I have the T-Mobile 1.72WWE rom installed.
Everything works ok for now, no problems.
But do I need to do when I want to upgrade/downgrade?
I don't have a second device so thats not an option
Please advise.
Thanks
To cairo31male!!
NOP!! Can't HELP!! Maybe the BOOTLOADER got the diffrent version? Mine is 1.03. Can u tell me how to upgrade the bootloader to 1.06?
And you mentioned about OLD version, what do you mean by that?
@hcnsoft:
The 2 solutions described above are for XDA 2's which have been screwed up by installing / uninstalling the latest beta version tmob 1.72. If this is your situation, and you have a working bootloader, both solutions should work for you.
@SEB152030:
The beta we have is 1.72, which caused all these problems. If you have another working device, as described in solution 1, you can revert back to the latest working official ROM (1.66), just follow the steps decribed above and use the official 1.66 upgrade program.
@applecom:
If your XDA 2 is dead, there is no harm in trying. But basically, this SD file will only work on devices that have already been upgraded to 1.72 and then died. If it is dead because of any other reason, I suggest you stick with older stable versions and don't try to mess up with 1.72 for now, until the developers come up with a simple tool to go back and forth between different roms. You can flash SD images that were made from other working devices that have your same model/language. You wouldn't get any errors that way.
@Panja:
Since your device is working, I suggest you wait a couple of days, before trying anything. The developers might come up with a simpler solution. If you absolutely have to downgrade, you can follow the solution 1 described above, but you will need another working device for a few minutes. Use the other working device which has the old ROM installed and start the OLD ROM installation software, then plug in your device with the 1.72 ROM AFTER you get the different versions dialog with the button "UPGRADE".
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
cairo31male said:
@hcnsoft:
@Ivan-R: which method are you tying? Solution 1 or 2? FOr the first solution, I guess it should work. For the SD flashing, I beleive you should have Bootloader 1.06. How to get that one, I don't know, but I strongly advise against it, untill all this matter is clear, as each new version of the bootloader implements stricter security, which will make it harder to customize in the future.
OLD version means any version before 1.72
Click to expand...
Click to collapse
I already try BOTH solution!! Solution 1, i try with ROM 1.03.11, which is thats the basic ROM. Solution 2, the RESULT is Not Allowed UpDate!!
So i guess this is the matter of BOOTLOADER!! Yours is 1.06 and me 1.03. THATS THE PROBLEMO NOW!! Now... How about upgrade the BOOTLOADER??
[email protected]#$!%G FREAK ROM!! :evil:
Mas Ivan,
Sebaiknya anda jangan menggunakan sd image yang di upload karena masih beta untuk menghindari kesalahan pada rom 1.72
thanks cairo for the info, my xda is working with the standard rom, Our only problem is me and the guy that got the rom in the first place would like to use it but we cant
anyway thanks for youe info
John
Solution 1
Solution 1 don't work for me because (I think) 2 version of bootloader 1.03 and 1.06.....
I found a solution : Here
Radio Stack Downgrade
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Re: Radio Stack Downgrade
watchdogsdg said:
I loaded the 1.72 Beta and would like to keep it, but the Radio Stack is horrible for me. I need to go back to the O2 launch version of the radio stack. I noticed in the O2launch Rom that the contents of the exe file included Radio.nb while the 1.72 exe contained Radio.nbf.
Is it safe for me to try and downgrade only the radio stack and if so should i use the launch version of himalaya upgrade or the 1.72 version of himalaya upgrade to install the launch radio.nb file?
Can anyone give me some advice here? My radio is barely functional. can't find networks where i know there is coverage. Thanks for any advice.
Click to expand...
Click to collapse
Go go go... Just downgrade it!! 8) Then you will join me in HERE!! Huahahahaha... You are STUCK for the REST OF YOUR LIFE!!
Didn't have any trouble downgrading
I just upgraded to 1.72 last week...hated it...gprs was WAY too slow. Today I downgraded and crossed my fingers back to Xda_II_Upgrade_v16050.exe (filename..not sure where i got it).
IT WORKS!! everything went fine and is fine.
I think my bootloader said it was something like version 1.01 (very hard to read that screen without the backlight) So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
This site is amazing. Thanks for everything.
Re: Didn't have any trouble downgrading
mkriemersma said:
So I'm guessing this downgrade problem may be specific to bootloader versions.
No expert, just letting you know what i did.
Click to expand...
Click to collapse
I AGREE WITH YOU!! BOOTLOADER thang'!! I am not EXPERT too, but I REALLY NEED SOME HELP HERE!!
Hi,
Thanks for all help!
I have a dead unit due to 1.72 ROm.
Itried to fool the himalya upgrade program with a soft reset as suggested in another thread, it works It gets trough the device id but stops when erasing rom, any suggestion?
Is there anyone out ther that can disassamble the himalyprogram and
make a small program without error checking?
I also have bootloader 1.06 and tried also "ntrw write ROM.nb1 H:"
It works writing the image but my bootloader don´t loads any rom.
Tried with 2 differnet SD cards, and soft reset, hardreset, and only pushing camera button, without succes, what is the right command?
Any more suggestions?
@nilron:
Press ARROW KEY (any direction on joystick) + POWER Button + SOFT RESET, all together, then wait a little. You should get instructions to press POWER to start flashing.
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
Hi all, I've purchased an HTC Mozart T-Mobile (German) branded, the firmware version number is 2250.09.12301.111, the phone is sim lock free but the only available languages are German and English UK; I live in Italy and i would have my own languages on my phone, so, which Rom I have to use to unbrand the phone and get italian language? Thx all
I second that.
Can someone post a detailed description as to how to unbrand Mozart phones for noobe?
For example I have those versions installed:
Firmware: 2250.09.12505.111 (--> 1.25.111.05)
Radio: 5.50.09.18_22.24.50.09U
How do I know my CID?
I can't find any guide to find CID please someone help us!
Firmware 2250.09.12301.111
Radio 5.50.09.18_22.24.50.09U
Bootloader 1.23.2250.1(110315)
I suppose that the "easiest" method here is to try every type of ROM and one that won't give "invalid vender id" error is designed for your CID as well. That's how I found that I have HTC_Asia branded version.
Isn't that method a little risky for the phone?
phoenixx666 said:
Isn't that method a little risky for the phone?
Click to expand...
Click to collapse
It is! That is how I killed my Orange-UK branded mozart.
Isn't possible to restore the phone whit the original firmware when bricked?
Yes, it should be fine IF you have the original ROM. But if you can, and you should be, use the gold card method to debrand your phone. It is actually quite easy if you follow the instructions.
The phone is already sim lock free, i would load a rom with italian language (i'm italian and the phone (T-mobile DE) have only german and english language), anyway a will give a shot today, later i let know you if my phone will be alive
Um.. I don't see how trying to flash ROM WITHOUT gold card can kill the device. It checks CID and if ROM isn't compatible with device, it won't flash at all. It is done BEFORE flashing. I tried flashing HTC_Europe this way - didn't start with this "invalid vender id" error. but it did work with HTC_Asia one and after flashing I got my device in the state I first ran it (with Australia settings)
Sorry, I'm a newbie
P.s. What's gold card?
nayato said:
Um.. I don't see how trying to flash ROM WITHOUT gold card can kill the device. It checks CID and if ROM isn't compatible with device, it won't flash at all. It is done BEFORE flashing. I tried flashing HTC_Europe this way - didn't start with this "invalid vender id" error. but it did work with HTC_Asia one and after flashing I got my device in the state I first ran it (with Australia settings)
Click to expand...
Click to collapse
Sorry to say it but you are wrong. This is exactly what I thought and I downloaded a ROM from Ansar. I thought it will give me an error if it is not compatible. But lo and behold, I received no error and the flashing process started. I was even happy and surprised. But the progress stopped at 11% and then told me my phone can not be flashed due to write error or something like that. Every time I put it on thereafter, it goes straight to the rainbow bootloader screen.
I had to go back to my HD2/7 until Ansar posted orange-uk rom which helped restored my phone. I have since debranded it using the gold card method and then received the update.
Summary, IF you have your correct factory ROM, you apparently can experiment, but if not you'd better stay off. Wrong ROM may give you an error, but like my case it may be only when your phone has been messed up.
abbas said:
Sorry to say it but you are wrong. This is exactly what I thought and I downloaded a ROM from Ansar. I thought it will give me an error if it is not compatible. But lo and behold, I received no error and the flashing process started. I was even happy and surprised. But the progress stopped at 11% and then told me my phone can not be flashed due to write error or something like that. Every time I put it on thereafter, it goes straight to the rainbow bootloader screen.
I had to go back to my HD2/7 until Ansar posted orange-uk rom which helped restored my phone. I have since debranded it using the gold card method and then received the update.
Summary, IF you have your correct factory ROM, you apparently can experiment, but if not you'd better stay off. Wrong ROM may give you an error, but like my case it may be only when your phone has been messed up.
Click to expand...
Click to collapse
You're totally right!
I had experienced the same: tried to flash an uncorrect ROM, had the same error, but - luckily - I immediately could re-flash the previuos and original one and everything went all right!
Well... Still I don't have italian language for the keyboard, but soon I'll experiment again!
This is a guide on how to flash a new ROM to your HTC 7 Mozart, without using Goldcard. This method can be used to update your ROM or to debrand your phone.
This method was outlined here by theintelligent. I've also used info from here by alalai. I take no credit for discovering this, but thought it deserved a pinned topic to help stop the multiple "how do I flash" topics and to make it easier for users to find the information.
Before you start
This WILL debrand your phone (remove network customisations) and it will enable you to receive updates as soon as Microsoft release them (rather than waiting for the operators).
It WILL NOT unlock your device (to allow you to use other network's SIMs). You will need to use a commercial service for this.
You WILL be able to update your phone to NoDo (and later leaked versions when they appear).
Preparation
I'm not sure why, I think it may be due to getting the right drivers installed, but you will need to install one of the following:
Windows XP users:
Install Microsoft ActiveSync .
Windows Vista/7 users:
Install Windows Mobile Device Center - make sure you install the right version 32/64bit depending upon your OS version.
Ensure that your phone's battery has at least 50% charge.
Download and flash your ROMs
Yes, I said ROMs - if you want to debrand your phone, you will need to download two sets of ROMs. If you're just updating and not debranding then you'll just need to download one ROM.
Download a ROM which is by the same network as you're on (for example if you're phone is currently locked to Orange UK then download RUU_Mozart_Orange_UK_1.22.061.10_Radio_5.50.09.18_ 22.24.50.09U, by ansar. - do not download 1.30!).
Open up ActiveSync/Mobile Device Center
Flash this ROM to your phone (you may not need to do this step, but most users will).
Turn your phone off.
Put your phone into Bootloader Mode - this can be done by pressing and holding the Volume Down Key & Power Button.
Plug your phone into your PC, hopefully a HTC USB driver will install.
Once the driver is installed your phone should display USB mode.
Extract the zip file and then run the exe file
Run through the update process
When your ROM is flashed, your phone will want you to customise it - just do the basic stuff.
Download the ROM you would like to flash (e.g. RUU_Mozart_HTC_Europe_1.30.401.01_5.54.09.21_22.33 b.50_RELEASE).
Extract the unbranded ROM zip file and then extract the exe file (WinZip will not do this - try 7zip or similar).
Copy the RUU_signed.nbh from the unbranded ROM
Extract the branded ROM exe
Paste the RUU_signed.nbh from the unbranded ROM to branded ROM
Plug your phone back into the PC in bootloader mode
Run RomUpdateUtility.exe file from the branded ROM (but with the unbranded RUU_signed.nbh file)
Follow the steps...
Et voila, you'll have (if all goes well) and unbranded ROM installed
Last step, plug your phone back into your PC and run Zune. Your phone should receive the latest cumulative update.
Let me know if anything isn't clear or needs updating. I am not going to list all ROMs, but there are a plethora of them available here.
Casey
thanks so much for this. i will try asap if my asia unbranded mozart will be flashed.
edit: question if i dont want to unbrand my mozart coz it already unbranded asia will i flash the htc_europe rom only? pls enlighten mo. ima little confused. =)
trixnix said:
edit: question if i dont want to unbrand my mozart coz it already unbranded asia will i flash the htc_europe rom only? pls enlighten mo. ima little confused. =)
Click to expand...
Click to collapse
Yes, if you're sure it's unbranded, then you can flash any ROM you like. Just make sure there's no difference between Asian and European models (I honestly don't know either way).
Casey
This is probably a stupid question but, after debranding can you still install operator specific apps (such as Orange UK's 'Your Orange' app) from the Marketplace?
Omega Point said:
This is probably a stupid question but, after debranding can you still install operator specific apps (such as Orange UK's 'Your Orange' app) from the Marketplace?
Click to expand...
Click to collapse
yes u can if u find it on the marketplace
they are apps like others
i am from algeria.
after a sucessfull flash, pin code requested.
is there a solution?
did you have the phone pin locked before you did the update? otherwise the default is usually 0000
i try to flash my asian version Mozart,
when i open the ROMUpdateUtility after it starts,
the Windows Mobile Device Center will automatically close, is that normal?
i flashed "RUU_Mozart_hTC_Asia_WWE_1.26.707.01_Radio_5.51.09.06_22.30.50.09U_by_ansar" first
And i paste the RUU_signed.nbh of "RUU_Mozart_HTC_Europe_1.30.401.01_5.54.09.21_22.33b.50_RELEASE" and flashed it.
the RUU always show invaild vender
thx u
alljerry04 said:
i flashed "RUU_Mozart_hTC_Asia_WWE_1.26.707.01_Radio_5.51.09.06_22.30.50.09U_by_ansar" first
And i paste the RUU_signed.nbh of "RUU_Mozart_HTC_Europe_1.30.401.01_5.54.09.21_22.33b.50_RELEASE" and flashed it.
the RUU always show invaild vender
Click to expand...
Click to collapse
I'm not sure if you can cross regions - I haven't tried it - someone else here may know. Maybe try another ROM.
Hi,
Great post.
If you going to flash via the bootloader then AS or WMDC do not need to be running.
Before attempting to flash a device ensure the battery has a charge of more than 50%
It is always good practise to perform another hard reset after flashing a ROM.
alljerry04 said:
i try to flash my asian version Mozart,
i flashed "RUU_Mozart_hTC_Asia_WWE_1.26.707.01_Radio_5.51.09.06_22.30.50.09U_by_ansar" first
And i paste the RUU_signed.nbh of "RUU_Mozart_HTC_Europe_1.30.401.01_5.54.09.21_22.33b.50_RELEASE" and flashed it.
the RUU always show invaild vender
thx u
Click to expand...
Click to collapse
Casey_boy said:
I'm not sure if you can cross regions - I haven't tried it - someone else here may know. Maybe try another ROM.
Click to expand...
Click to collapse
Hi,
I think you will need to create a goldcard and purchase a cable (new days) or even HARD-SPL or CID (old days) to unlock your device if you want to flash ROMS from different regions, when the option becomes available for the Mozart. (if ever).
Random Apps
I downloaded and installed the rom for the unbranded mozart for europe and HATE the fact you can't select the uk keyboard... So I installed the original orange one from ansaar but it has these silly apps that I can't uninstall... anyone know how to get rid?
As the ROM is branded then you cannot get rid of the carriers customisation, as for the keyboard, this is really no big deal, the £ key can still be used, and its not as if its a full qwerty anyway.
I have a UK Orange Mozart (Sim Locked) and unbranded to the Euro 1.28 using this method. When I connected to Zune it immediately wanted to upgrade the OS to the Pre-NoDo update but it refuses to see NoDo.
However there are reports of people flashing unbranded 7389 OS builds successfully getting the Official NoDo via Zune who are also in the UK so it's very unclear how MS are "Delivering" the updates. What do Microsoft really mean by "Open Market" ?
What isn't clear is if the unbranded phones were also sim unlocked.
Infuriated-Germ said:
I have a UK Orange Mozart (Sim Locked) and unbranded to the Euro 1.28 using this method. When I connected to Zune it immediately wanted to upgrade the OS to the Pre-NoDo update but it refuses to see NoDo.
However there are reports of people flashing unbranded 7389 OS builds successfully getting the Official NoDo via Zune who are also in the UK so it's very unclear how MS are "Delivering" the updates. What do Microsoft really mean by "Open Market" ?
What isn't clear is if the unbranded phones were also sim unlocked.
Click to expand...
Click to collapse
I wrote this guide after flashing my girlfriend's Mozart (which was OrangeUK branded) to Euro 1.30 which was OS v7389 and as soon as the 7390NoDo update was released she was asked to update.
So, yes, I'm unsure. Perhaps they are going by OS version. But if you want NoDo, then flash 7389 (which is essentially NoDo anyway) and then you'll get updated to 7390.
Casey
hd2leo_fusion said:
yes u can if u find it on the marketplace
they are apps like others
Click to expand...
Click to collapse
Do you have to reinstall all your applications??
Mogreen said:
Do you have to reinstall all your applications??
Click to expand...
Click to collapse
Yep. This completely reformats your phone - it's not the same as the update process. You'll lose everything - so backup your data with Zune.
That being said, you can just re-download your apps (even your paid apps).
Casey
Worked perfectly, thanks so much!
Casey_boy said:
[*]Download a ROM which is by the same network as you're on (for example if you're phone is currently locked to Orange UK then download RUU_Mozart_Orange_UK_1.22.061.10_Radio_5.50.09.18_ 22.24.50.09U, by ansar. - do not download 1.30!).
[*]Open up ActiveSync/Mobile Device Center
[*]Flash this ROM to your phone (you may not need to do this step, but most users will).
Turn your phone off.
Put your phone into Bootloader Mode - this can be done by pressing and holding the Volume Down Key + Power Button.
Plug your phone into your PC, hopefully a HTC USB driver will install.
Once the driver is installed your phone should display USB mode.
Extract the zip file and then run the exe file
Click to expand...
Click to collapse
Hopefully no-one minds me registering to ask for advice on de-branding. I have a question about the part of the procedure above where the branded ROM is first flashed. The version for my phone is here:
http://forum.xda-developers.com/showthread.php?t=1007277
But, when I unzip that, there's no complete .exe as it's already been extracted. The unbranded ROM is an .exe which I had to extract with 7zip, though. So, what .exe should I run for the initial flash with the branded ROM (e.g. RomUpdateUtility, EnterBootloader, something else etc.)? Thanks.
knirirr said:
But, when I unzip that, there's no complete .exe as it's already been extracted. The unbranded ROM is an .exe which I had to extract with 7zip, though. So, what .exe should I run for the initial flash with the branded ROM (e.g. RomUpdateUtility, EnterBootloader, something else etc.)? Thanks.
Click to expand...
Click to collapse
Run the ROMUpdateUtility executable
Casey