Database Users

[ROM]RUU_Mozart_TMO_DE_1.28.111.03_5.52.09.16_22.33a.50 _RELEASE

Here new ROM for Mozart
http://www.filefactory.com/file/b48..._1.28.111.03_5.52.09.16_22.33a.50_RELEASE.exe
DO NOT TRY TO FLASH THIS ROM FOR ANY OTHER DEVICE EXCEPT MOZART!
Enjoy!

THNX a LOT!
Hopefully it fixes my problems with sending text messages.

Will I lose my data (mainly my SMSes) if I install this update?
//EDIT -> according to several forums, I will lose my data...
and I haven't found any solution to backup my SMSes - yeah -.-
Is there anything I should regard or be aware of before updating?
//EDIT -> I just tried updating my phone and don't know how. It boots in the bootloader (RGB-test with some data on the device, SPL, the SD card, ...) just fine but the RUU doesn't find it.
I'm trying to flash it from a Windows XP machine - is there anything I have to take care of before I can flash it?
Or is there a real step-by-step manual for total dummies (I've flashed my HTC Diamond several times before without problems and have got no clue, why the PC won't find my Mozart).
The update process cancels with a CONNECTION ERROR [260].

will the hspa work on it from the tmobile usa after flashing this rom???

Invalid vender id
I have
INVALID VENDER ID
T-Mobile
Is there already a solution?
THX
nice greetings

Do you have the German T-Mobile version?
Mine flashed without any problems (after solving the driver problem...).

I have T-Mobile Austria.
but that this should be the same, right?
Greetings

Well, I'm not exactly sure.
However, if you think about the update failing with a wrong VENDOR ID - I guess it makes a difference.

FrozenLord said:
Do you have the German T-Mobile version?
Mine flashed without any problems (after solving the driver problem...).
Click to expand...
Click to collapse
are there any big noticable changes after flashing the new rom?
or is it just a minor security/stability update?

Be careful when uninstalling TMO apps
ROM is working very good, more fluent than stock version 1.25 - no problems found yet.
Still noticed the same problems with the stock ROM after uninstalling TMO shipped apps. When I uninstall Navigon the BING Map "Search" and "get directions" is gone/does not work anymore. When I remove "mediencenter" and plug in the headphones the phone is neither accepting nor able of making calls. However reflashing solves the problem - but you can't get rid of those TMO apps without losing functionality.

cmxqu said:
ROM is working very good, more fluent than stock version 1.25 - no problems found yet.
Still noticed the same problems with the stock ROM after uninstalling TMO shipped apps. When I uninstall Navigon the BING Map "Search" and "get directions" is gone/does not work anymore. When I remove "mediencenter" and plug in the headphones the phone is neither accepting nor able of making calls. However reflashing solves the problem - but you can't get rid of those TMO apps without losing functionality.
Click to expand...
Click to collapse
Strange, i deleted all the default T-mobile stuff and everything works just fine..
I also have the german T-mobile Mozart 16GB because it isn't released in the netherlands yet. I uninstalled all the programs Tmo ships. directions work just fine, very strange

hi
hi bro.. i have a question, first.
1- How to flash this ROM in my HTC 7 MOZART?
2- What news have this ROM? it is possible that my phone is blocked trying to flash this rom?
3- What fix this ROM in my cellphone?
thanks bro...

fabrifox said:
hi bro.. i have a question, first.
1- How to flash this ROM in my HTC 7 MOZART?
2- What news have this ROM? it is possible that my phone is blocked trying to flash this rom?
3- What fix this ROM in my cellphone?
thanks bro...
Click to expand...
Click to collapse
According to some other sites (just google the version number), this rom ships out with new devices. So no, it should not get you blocked, as it's a legit update.
Flashing is fairly easy: Backup everything you can, start you Mozart in Bootloader mode (pressing volume down while powering it on), plug it into your PC via USB, install the drivers if needed (done by installing Active Sync in XP, Windows Vista and newer should automatically find the needed drivers), start the updater and follow the instructions.
There is no official changelog, but several people think that the animations are smoother, the touchscreen reacts faster, ...
Seeing that there is no official changelog and the only thing we can do is assume what could have changed, I think there's no sense in discussing this. Especially since you can find several threads in other forums that discuss the changes in various lengths...
I haven't noticed any new problems after the update, so I guess it's at least as good as the previous version.
But this are just my thoughts

hi
FrozenLord said:
According to some other sites (just google the version number), this rom ships out with new devices. So no, it should not get you blocked, as it's a legit update.
Flashing is fairly easy: Backup everything you can, start you Mozart in Bootloader mode (pressing volume down while powering it on), plug it into your PC via USB, install the drivers if needed (done by installing Active Sync in XP, Windows Vista and newer should automatically find the needed drivers), start the updater and follow the instructions.
There is no official changelog, but several people think that the animations are smoother, the touchscreen reacts faster, ...
Seeing that there is no official changelog and the only thing we can do is assume what could have changed, I think there's no sense in discussing this. Especially since you can find several threads in other forums that discuss the changes in various lengths...
I haven't noticed any new problems after the update, so I guess it's at least as good as the previous version.
But this are just my thoughts
Click to expand...
Click to collapse
Thank you so much!!! Ure a bad man =) i try to flash and later i said ok....

if i have a german t-mobile device, do I have to flash my mozart at first? Or can _I just install the new firmware without doing anything before??
edit: and is this version newer or this one: [ROM]RUU_Mozart_HTC_Europe_1.28.401.04_5.52.09.16_22.33 a.50_RELEASE
am I able to install both on my german tmobile mozart?

WinUser009 said:
if i have a german t-mobile device, do I have to flash my mozart at first? Or can _I just install the new firmware without doing anything before??
edit: and is this version newer or this one: [ROM]RUU_Mozart_HTC_Europe_1.28.401.04_5.52.09.16_22.33 a.50_RELEASE
am I able to install both on my german tmobile mozart?
Click to expand...
Click to collapse
No you can't flash the HTC_Europe version, only the TMO_DE version.
TMO_DE stands for T-mobile Germany
HTC_Europe is the generic software for the non branded devices.
Doesn't make any difference except the useless apps you get from t-mobile.
But after you delete them everything is the same.
And for the record, You don't have to flash your phone at first... Installing new firmware IS flashing. so you just run the RUU and make sure zune is running and phone is running, not in stand-by.
And be sure to backup everything you want to keep, haven't flashed my mozart, but i think you lose all data when you flash it.
Sure someone else knows that.

Aerox912 said:
No you can't flash the HTC_Europe version, only the TMO_DE version.
TMO_DE stands for T-mobile Germany
HTC_Europe is the generic software for the non branded devices.
Doesn't make any difference except the useless apps you get from t-mobile.
But after you delete them everything is the same.
And for the record, You don't have to flash your phone at first... Installing new firmware IS flashing. so you just run the RUU and make sure zune is running and phone is running, not in stand-by.
And be sure to backup everything you want to keep, haven't flashed my mozart, but i think you lose all data when you flash it.
Sure someone else knows that.
Click to expand...
Click to collapse
Thanks for the answer!
I thought that I have to set the mozart in the bootloader mode, in order to flash. When I was telling it "flashing" I meant something like hspl like we had to do on the HD2, befor we could flash custom roms or htc roms on it.
edit: and is there any possibility to go back to: 1.25.2250.5 firmware (now installed on my phone)?
and last question this 1.28 version will not breake my warranty, right? It'S a normal t-mobile rom, isn't it?

Guys, I'm not sure I fully understand everything so far.
I basically have a Telstra (Australian) HTC 7 Mozart. From what I gather, I cannot flash this on my device until it is unbranded, is that correct?

hello to everyone.
I have a htc t-mobile mozart Germany but I live in Venezuela and I can assure you and proven DepNet.com for both 1.25 and 1.28
posted on this page to a friend Football and run to perfection
and also I can tell you that my phone came with 1.25 and the 1.28 istale him but then return to 1.25 and all is well.
and the echo for several times trying to place the Spanish language and if anyone can help I'd appreciate it forever

@ WinUser009:
HSPL was needed because we used to flash cooked (and therefore custom-made) ROMs, which were not signed by HTC or any other company able to sign them. These ROMs are unmodified and signed, which is why you can flash them without flashing any unlocked HSPL first.
Bootloader-mode is just a different mode to boot in - it does not need any changes to your phone!
I don't think that there is a possibility to go back to 1.25.xxx - but honestly why would you want to? But I have to admit that I have not yet tried it...
As to the warranty: that's a complicated matter...
This firmware is not official and my new Mozart (I got a new one after sending it in) still had the 1.25 firmware installed (someone posted that newer phones should ship with the 1.28). So there might be a person detecting that you flashed it yourself, if they keep sending out new phones with 1.25 preinstalled.
However, the phone I turned in had 1.28 flashed and I have not received any complaints when I sent it in for a replacement. So I guess it is up to your shop but it should not pose any problems!
@ameel
You can flash as soon as one of these things happen:
- custom roms are released that don't check for the carrier information
- you unlock your phone (somehow)
- Telstra releases an update
But as of now you can't flash these T-Mobile roms on your Mozart.
@minino405
Sorry, but I didn't understand your post. What did you try to tell / ask us?
I hope I could help you with some of your questions

[Q] Updating after flashing a rom.

Hey Guys,
I have recently purchased a T-mob UK Omnia 7 and am willing to flash it with a non-branded rom. I am confident enough in how to do it. Are the roms available from samifirmware unbranded?
The thing I wanted to ask was, after flashing the rom, am I going to receive notifications for updates? Is the phone going to update? The reason I am asking is that I noticed some people are facing problems when updating the post-nodo update.
thanks

Hey,
I just did the same that you want to do. Flashed the Omnia 7 with the
Firmware Version I8700XXJK1 and "de-branded" my phone with that.
After flashing I got a message that the pre-nodo update is available.
After updating the Omnia 7 to 7008 I thought I will get the NoDo Update but nothing came yet....
Hope that this won't take too long

Mordanius said:
Hey,
I just did the same that you want to do. Flashed the Omnia 7 with the
Firmware Version I8700XXJK1 and "de-branded" my phone with that.
After flashing I got a message that the pre-nodo update is available.
After updating the Omnia 7 to 7008 I thought I will get the NoDo Update but nothing came yet....
Hope that this won't take too long
Click to expand...
Click to collapse
Hopefully. I just hope that we will be able to get the following updates as well as nodo. Any thoughts anyone?
I am coming from Android and still getting used to the differences.

No wonder those ROMS are branded, but are they truly?
Roms posted on samfirmware, are all branded but some does not have a splash screen for operator logo, there seem to be some 000-88 carrier code to deal with. I had my Omnia 7 on Orange, I flashed it with DBTJK1 from samfirmware, it picked up the pre-nodo update right away. NoDo, however was not available as of yesterday.
Having checked on Microsoft's website, I learnt that Orange was delivering all available updates. So, I tweaked back my registry to ORG-GB (Originally noted from my official ROM before replacing it), the restarted my phone and NoDo was available.
So just hack your registry for the carrier or any unbranded code and you shall get the update right away.

xdamir said:
No wonder those ROMS are branded, but are they truly?
Roms posted on samfirmware, are all branded but some does not have a splash screen for operator logo, there seem to be some 000-88 carrier code to deal with. I had my Omnia 7 on Orange, I flashed it with DBTJK1 from samfirmware, it picked up the pre-nodo update right away. NoDo, however was not available as of yesterday.
Having checked on Microsoft's website, I learnt that Orange was delivering all available updates. So, I tweaked back my registry to ORG-GB (Originally noted from my official ROM before replacing it), the restarted my phone and NoDo was available.
So just hack your registry for the carrier or any unbranded code and you shall get the update right away.
Click to expand...
Click to collapse
Can you please help me finding a guide how to tweak the carrier version? Ive been looking for it whole day with no luck.

Just download Chevron wp7 updater, updates your none branded splash rom to nodo, make sure you prevent lock it on prenodo, then you got a awesome hacked phone, mango not coming out till a longgg time so enjoy most of it, I am!
Sent from my OMNIA7 using XDA Windows Phone 7 App

PS. My phone was t mobile jk1 speeded my phone up 2x then nodo blew it away, now I got a phone with no tmobile splash as for thefuture.updates worrry about them when they come, have problems flashing? Buy a s9000i galaxy jig on eebay for 3 pounds, hope I helped, cheers
Sent from my OMNIA7 using XDA Windows Phone 7 App

If you want to keep your tmobile just chevronwp7 it and use the debrand.xap with toms cap tool see windows developer section for wp7 tools, also Omnis 7 developement
Sent from my OMNIA7 using XDA Windows Phone 7 App

stopmybeat said:
If you want to keep your tmobile just chevronwp7 it and use the debrand.xap with toms cap tool see windows developer section for wp7 tools, also Omnis 7 developement
Sent from my OMNIA7 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Please stop, you've said the same thing three times now.
I have tried flashing the DBTJK1 firmware today and I got the feburary update but not nodo. I even tried setting the carrier to ORG-GB and rebooting the phone with no luck. If anyone can give any advice, I'd greatly appreciate it.

I flahed my Omnia 7 with the "I8700 XEN I8700XENJK1" ROM, andthe day after I got the NoDo through Zune.
So no "blocking" of updates here in Denmark on "3"
UPDATE: Sorry, I've misread your ROM-version

So, what is the real difference between these firmware versions:
I8700XXJK1 - DBT
I8700XXJK1 - XEN
I8700XXJK1 - BSE
Coming from Germany I just flashed the DBT and got the pre-NoDo but
NO NODO

xdamir said:
So just hack your registry for the carrier or any unbranded code and you shall get the update right away.
Click to expand...
Click to collapse
Would you be so kind and let us know which unbranded code to use or how to get that?

Changing carrier code does *not* force the update down, been there and done that.
However if your gullible to try, unbranded code is 000-88

MrSkiba said:
Changing carrier code does *not* force the update down, been there and done that.
However if your gullible to try, unbranded code is 000-88
Click to expand...
Click to collapse
Thanks for that mate, and how can I fix this in the registry? I guess I have to unlock the device again.....but don't want to do this anymore.
I just want to receive the NoDo Update with my - now unbranded - WP7 !!!

Yep, you need to unlock the device and modify the registry settings, however if you've flashed with any of the unbranded ROMs on samfirmware, it'll already be sitting on 000-88.

MrSkiba said:
Yep, you need to unlock the device and modify the registry settings, however if you've flashed with any of the unbranded ROMs on samfirmware, it'll already be sitting on 000-88.
Click to expand...
Click to collapse
Thanks, didnt know that the roms available at samfirmware are set to that code. Good news for me.

Many thanks for these informations. I flashed my Omnia 7 with the I8700XXJK1 - DBT ROM and can confirm that the registry setting is set to 000-88.
But the Problem is that I still receive no NoDo and I am getting nervous.....
Updated it before with Chevron, then flashed it down to the Original Samsung I8700XXJK1 - DBT...7004
Now I am on 7008 hanging......
Anything went wrong?

The NoDo update seems to be selective, the way it selects is unknown, if you don't get it immediately, don't worry about it, it'll eventually come your way. Theres no method I've found in forcing the update down (even the zune timing trick seems a bit of a hoax to me).
I've contacted my Samsung Support Centre and I'm querying what unbranded UK firmware they have and whether its preloaded with NoDo. They will probably get back to me within the week.

read what I said, the 3 times are for your benefit, update via the way I said no Zune, cheers
Sent from my OMNIA7 using XDA Windows Phone 7 App

MrSkiba said:
The NoDo update seems to be selective, the way it selects is unknown, if you don't get it immediately, don't worry about it, it'll eventually come your way. Theres no method I've found in forcing the update down (even the zune timing trick seems a bit of a hoax to me).
I've contacted my Samsung Support Centre and I'm querying what unbranded UK firmware they have and whether its preloaded with NoDo. They will probably get back to me within the week.
Click to expand...
Click to collapse
This is the most useful thing anyone has ever said, I'll hold on for the moment. Please let us know what's going on with the UK unbranded firmware, thankyou.

Final Mango DZ File Name

For you DZ hunters out there, the official Quantum (AT&T) DZ name should be LG-C900AT-01-V11f-310-410-JUL-27-2011.
The internal rom name is: LG-C900-V11f_Final-JUL-27-2011-2250-7720.
Yes, you read those correctly, our final mango update that we've been waiting for comes from July!

fb401 said:
For you DZ hunters out there, the official Quantum (AT&T) DZ name should be LG-C900AT-01-V11f-310-410-JUL-27-2011.
The internal rom name is: LG-C900-V11f_Final-JUL-27-2011-2250-7720.
Yes, you read those correctly, our final mango update that we've been waiting for comes from July!
Click to expand...
Click to collapse
Any news on the Quantum Bell (C900B)? I have the leaked 7720 ROM, but I think that one is missing some drivers.

That info would have to come from a C900B user who's on Mango. They'd have to go into the MFG to get the info as I have for this.
Sent from my LG-C900 using XDA Windows Phone 7 App

master pda dude said:
So just to be clear... I could use this DZ with the LGDP2_V36_UMTS tool to upgrade to Mango without using Zune?
Click to expand...
Click to collapse
Yes, but you would lose all of your data.

master pda dude said:
Awesome. I can't update via Zune or Cab Sender because I depend on my Quantum for Internet, and my phone can't be on QC Composite and MS Composite simultaneously. I see there is no WiFi Tethering... that sucks.
Click to expand...
Click to collapse
Flash the Telstra ROM, it has WIFI tethering with the latest update. It works very well.

flashing help
I tried updating my Quantum a few weeks ago to software version 8107 using instructions found here. The backup failed, but since I didn't have any important info on the phone anyway, I proceeded with the update attempt. My phone lost connection during the upgrade process and was bricked.
I was able to hunt down the factory Quantum ROM for my AT&T Quantum. It took several attempts, but the flashing was finally successful. I went through the first 2 software updates successfully through the Zune software, but my phone lost connection during the Mango update and was bricked again. Whenever I try to flash the factory ROM now, my phone will reboot when the flashing is finished, but it will hang on the LG title screen and won't ever boot. Does anyone have any suggestions for what else I can try, or know where I can download the Mango ROM for AT&T's Quantum? The only link I've found online says the file has already been removed from the hosting site.

Officiall Mango Update Arrived

Just upgraded from mango rc and there is no skype, can't find how to make mp3 work as a ringtone, also cannot find function which lets me translate text using the camera.

What carrier are you on, and has your phone been debranded?
I still haven't recieved my mango update... I have a Telus phone that has been registry debranded. I'm running it on AT&T's network.

Try re-branding it.

riauba said:
Just upgraded from mango rc and there is no skype, can't find how to make mp3 work as a ringtone, also cannot find function which lets me translate text using the camera.
Click to expand...
Click to collapse
Skype hasn't been released yet AFAIK. There are guides on how to make MP3s that can be used on Mango as ringtones, for example: http://wintellect.com/CS/blogs/jgar...-custom-ringtones-in-windows-phone-mango.aspx
Text translation is done from Bing (the search button) and then you select "vision".

Arktronic said:
Try re-branding it.
Click to expand...
Click to collapse
That's my next step, but I wanted to see if anyone with a registry de-branded phone had received an update already. So has everyone here gotten their update but me?
EDIT: I forced the update via Ziko's post: http://forum.xda-developers.com/showthread.php?t=1279960 and the update is currently installing.

I flashed a different ROM, so my phone went back to 7389. It updated to 7392 and got stuck there. So I updated it to the Mango beta via the proper beta provisioning app, and from there it went to 7720 + LG drivers.

I am on Vodafone Spain with an AppHub developer account running build 7712 on my LG Optimus 7 and I have received the ISV 7720 update without forcing it. But it won't go beyond step 6 of the update process (restarting your phone) saying there are some missing drivers or something.

Missing drivers? Odd. Have you tried a different computer?

I'm on ATT as well.... didn't get the option to upgrade, but this worked
http://gizmodo.com/5844454/you-can-force-the-windows-phone-75-mango-update-right-now
It did take a couple of trys, there is a "sweet" spot to disconneccting the comptuer from the internet, and it says to wait 30 seconds, but it took more like 2 minutes. It did come up eventually thought, and I am running 7.5

sonus said:
What carrier are you on, and has your phone been debranded?
I still haven't recieved my mango update... I have a Telus phone that has been registry debranded. I'm running it on AT&T's network.
Click to expand...
Click to collapse
I'm on Vodafone uk and i unlocked my phone before.

MS rolling out 7.10.8107.79 update

hello all,
Yesterday Microsoft released the 7.10.8107.79 update for windows phone.
This is believed to fix the SMS bug and disappearing keyboard fix.
Currently only the Vodafone Italy customers are receiving it.
But you can get the update using manual cab sender method.
check the following post for details.
http://forum.xda-developers.com/showthread.php?p=21028452#post21028452
Meanwhile, if anyone on telstra or other ROM gets a official update , please let me know

Well I'll be waiting to get it from Sasktel here in Canada but I think I'd take the firmware update to get wireless tethering to be honest.
Just curious. Has anyone with a quantum experienced the disappearing keyboard?? I have never experienced it. Ever.
I'm on 7740 right now.

No, you just need use the registry editor on MFG menu and change the identification of your Quantum, In my case I have an AT&T carrier Quantum and I change their identification as Vodafone and Zune launch the update proces to 8107....easy.
The values to change to Vodafone are here:
http://forum.xda-developers.com/showthread.php?t=1359368

Reyk said:
No, you just need use the registry editor on MFG menu and change the identification of your Quantum, In my case I have an AT&T carrier Quantum and I change their identification as Vodafone and Zune launch the update proces to 8107....easy.
The values to change to Vodafone are here:
http://forum.xda-developers.com/showthread.php?t=1359368
Click to expand...
Click to collapse
Does changing the carrier also result in a change in the firmware for the phone as well? For example, would I also get an update that would change me over to the Vodafone firmware?

droodls said:
Well I'll be waiting to get it from Sasktel here in Canada but I think I'd take the firmware update to get wireless tethering to be honest.
Just curious. Has anyone with a quantum experienced the disappearing keyboard?? I have never experienced it. Ever.
I'm on 7740 right now.
Click to expand...
Click to collapse
Yes I had the keyboard disappear countless times on 7720 and 7740. Very frustrating. It wasn't only the on screen keybaord either, sometime while typing with the hardware keyboard, the text box would lose focus on its own. havent seen the issue since going to 8107.
droodls said:
Does changing the carrier also result in a change in the firmware for the phone as well? For example, would I also get an update that would change me over to the Vodafone firmware?
Click to expand...
Click to collapse
in my experience, there are built in safe guards in the update process that will prevent you from flashing the firmware of a different carrier/model of phone.

bobzero said:
in my experience, there are built in safe guards in the update process that will prevent you from flashing the firmware of a different carrier/model of phone.
Click to expand...
Click to collapse
Too bad. Was kinda hoping there would be an easy way to get the tethering update, but I suppose this is to be expected.

AT&T update
Is AT&T already released this update? Or something is wrong in my phone?
My phone is stucking at 7.10.7720.68

ATT not releasing 8107