Database Users

[Q] NoDo update for LG E900

Hi guys
Does anybody know when will be nodo update for our phone?

Sometime between today and the end of March...

cant wait for it ...

I need copy&paste so much And I like to have a phone with a newest soft. :-D

I just recived NoDo. I have flashed the Open Europe ROM a few weeks ago!

I can't flash OE ROM cause my phone dosn't work properly after flashing (Camera dosn't work and many apps crashed system)

I just got an update request for the February 2011 update. I am on telus.

nVd90 said:
I just got an update request for the February 2011 update. I am on telus.
Click to expand...
Click to collapse
Same here. However, there is now a support page up that explains how to update to nodo, so maybe next week we shall see it :|
http://www.telusmobility.com/en/ON/lg_optimus_7_support/trouble30.shtml
edit : found this shortly after posting: a week at least, maybe four
the landing page for support for the phone
http://www.telusmobility.com/en/ON/lg_optimus_7_support/index.shtml
has
The earliest date that a TELUS customer can receive the Windows Phone 7 software update is Tuesday March 29th, 2011. Microsoft is releasing the software update in a phased approach and it may take up to four weeks for all TELUS .....
Click to expand...
Click to collapse

Gahgah said:
I just recived NoDo. I have flashed the Open Europe ROM a few weeks ago!
Click to expand...
Click to collapse
I flashed that ROM, too, but no update so far.

I'm still waiting ....

up date is availabel
Up date NoDo is out.
Successfully installed.

If you're not already dev unlocked the official way, would you mind terribly just verifying whether the DeveloperUnlockState and MaxUnsignedApp registry values still have the same effect as before? Ie. if we can still unlock to a degree in a Chevron-ridden world.

Vodafone Spain still not giving me NoDo

Still nothing here on Europe Open.

:[ How long can we wait for it?????? :[

__ow said:
If you're not already dev unlocked the official way, would you mind terribly just verifying whether the DeveloperUnlockState and MaxUnsignedApp registry values still have the same effect as before? Ie. if we can still unlock to a degree in a Chevron-ridden world.
Click to expand...
Click to collapse
I'd like to know this as well!

No NoDo here (Vodafone UK)...

Still nothing in Poland F.ck

How is checked if new version is available? Is it globally universal URL? Or is it stored inside device and zune after conecting is using this URL? Or is it somehow else made?

I think it is a same way as a "normal windows" update.

[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.

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.

Unbranded 16GB Omnia 7 and no Mango till now

I have samsung omnia 7 16GB unbranded i bought it from expansys
and till now i didn't get Mango update
any one could help
Regards

Lies and a different battery cover?
I dunno the whole system seems buggered - I have an 8GB "3" branded Omnia 7, and I received the updates the day it came out

Its getting rolled slowly, it can take up to 24 days to reach everyone. Google force update trick to get it to install faster
Sent from my OMNIA7 using XDA Windows Phone 7 App

Try the Unofficial Way
You probably won't get the update until a few weeks because it's still in the distribution phase which could, or could not, take forever.
There is a trick that everyone's been doing though:
1. Connect your phone to your PC and launch Zune.
2. Go to your phone's settings from there, and click the 'Update' tab.
3. Then click on any other tab, and once again click on the Update tab.
4. This is the tricky part...right after you click the 'Update' tab for the second time, wait exactly from 2 to 3 seconds and then disconnect your PC from internet. You must do that before you get the 'No Updates Found' screen.
If you suceed, you should wait for about 20 seconds and then you will find an available update.
5. Reconnect to the internet, start your update, and voila.

thx for help
i try this unofficial way and it work with me and install the first update 7.0.4
but while installing 7.10 it give me error and the phone restart and stuck with samsung omnia 7 logo
i made hard reset for the phone it restore again to old software
but form this time every time i restart the phone it stuck with omnia 7 logo and i have to remove the battery and insert it again to load the os
any idea about this

Spookidoodles said:
Lies and a different battery cover?
I dunno the whole system seems buggered - I have an 8GB "3" branded Omnia 7, and I received the updates the day it came out
Click to expand...
Click to collapse
strange, i have the same as you and are on three....no update for me???

egyfox85 said:
I have samsung omnia 7 16GB unbranded i bought it from expansys
and till now i didn't get Mango update
any one could help
Regards
Click to expand...
Click to collapse
I have 16GB unlocked and unbranded version as well and i have no mango yet either. I read elsewhere here that if you do the "trick" download using Zune you don't get the proper update for the Omnai because there is a Samsung firmware update as well that is missing. I will wait for a few weeks max to see if I can get via Zune. Will let you know when I get it.

@egyfox85:
Try to flash your device with a RTM ROM (or Nodo rom, but you cant use then the Chevron Jailbreak), because your Omnia 7 firmware is damaged.
Then try update to Mango..
Greetings.

17-apg said:
I have 16GB unlocked and unbranded version as well and i have no mango yet either. I read elsewhere here that if you do the "trick" download using Zune you don't get the proper update for the Omnai because there is a Samsung firmware update as well that is missing. I will wait for a few weeks max to see if I can get via Zune. Will let you know when I get it.
Click to expand...
Click to collapse
I'm in a similar position as you where I have a 16gb Omnia 7. I actually forced my device but restored it back to NoDo soon after realising my firmware version was incorrect. I just hope me forcing it doesn't hinder my chance of getting Mango - does anyone know whether this could be an issue or not?

I have an unbranded omnia 7 16gb from tmobile germany (no carrier branding shown when turned on the phone). I forced update to mango but received an error 80180048 and now I want to reflash it back to its original rom to re-do updates to nodo and just wait for offical release. Does anyone know what the original rom is?

I was in the same situation. I made dozens of attempts to update, but only succeeded by reverting to a pre nodo rom, and allowing updates as far as Zune would go. After this, the phone updated all the way through to Mango using the network pull trick without issue. So if you are willing to wipe the phone completely, this might be the way.
I started at Samsung Omnia 7 Firmware XXJL3 Retail UK.

I've been using Mango since the day it first rolled out on my 16GB Omnia 7 from expansys UK.
Used the forced update, got the lastet OEM updated firmware with it too

now my phone stuck at start up Omnia 7 logo and i reflash it with firmware I8700XXKC1 after i finish it updated to 7.392 but also no mango
this should be UK rom
any idea about this too

Kash511 said:
I'm in a similar position as you where I have a 16gb Omnia 7. I actually forced my device but restored it back to NoDo soon after realising my firmware version was incorrect. I just hope me forcing it doesn't hinder my chance of getting Mango - does anyone know whether this could be an issue or not?
Click to expand...
Click to collapse
I put mine back to Nodo a few days ago and just got the official Mango via Zune today. Now, my details are:
OS 7.10.7720.68
FW 2424.11.3.1
HW 3.15.0.4
Radio SW 2424.11.7.2
Radio HW 0.0.0.800
Bootloader 5.8.1.0
Chip SOC 0.36.2.0

17-apg said:
I put mine back to Nodo a few days ago and just got the official Mango via Zune today. Now, my details are:
OS 7.10.7720.68
FW 2424.11.3.1
HW 3.15.0.4
Radio SW 2424.11.7.2
Radio HW 0.0.0.800
Bootloader 5.8.1.0
Chip SOC 0.36.2.0
Click to expand...
Click to collapse
Nice one mate and congratulations (I'm jealous lol) - I'm checking mine everyday but have had no luck so far, guess I'll just have to be patient. Just for info, is your phone a German model, (mine is but its still unlocked/unbranded). I ordered mine from eBay assuming it was a UK model but it wasn't - it updated to NoDo fine a while back...

Kash511 said:
Nice one mate and congratulations (I'm jealous lol) - I'm checking mine everyday but have had no luck so far, guess I'll just have to be patient. Just for info, is your phone a German model, (mine is but its still unlocked/unbranded). I ordered mine from eBay assuming it was a UK model but it wasn't - it updated to NoDo fine a while back...
Click to expand...
Click to collapse
yip, mine is a German model with 16GB (that's why I bought from there). But hey, horror stories.... I couldn't update NOW so I deleted it thinking that the old version was stopping the new version from downloading. Then I couldnt get it at all so I tried to go back to NODO and couldnt restore. Phone hung on the update connection . Reinstalled KC1 using WP7 installer and got back to NODO and did a force install (trick) to get back to Mango. And still I cannot update NOW; must be a Sammy problem. You should try the "force Zune trick" to get the Mango update pal..

Running 16 GB unbranded Omnia 7 purchased from ebay.de on Swisscom in CH and tried Zune update for 1/2 hour ago .... & got the regular update to Mango (not forced). Will post later if everything went well.... Regz from CH

17-apg said:
yip, mine is a German model with 16GB (that's why I bought from there). But hey, horror stories.... I couldn't update NOW so I deleted it thinking that the old version was stopping the new version from downloading. Then I couldnt get it at all so I tried to go back to NODO and couldnt restore. Phone hung on the update connection . Reinstalled KC1 using WP7 installer and got back to NODO and did a force install (trick) to get back to Mango. And still I cannot update NOW; must be a Sammy problem. You should try the "force Zune trick" to get the Mango update pal..
Click to expand...
Click to collapse
Aaah,nah I already forced it and wasn't happy as the firmware was completely wrong, the reason I reverted back to NoDo was because of that issue. On a positive note, I sent a tweet to windowsphonehelp (or whatever they're called) and they responded back saying if you've forced it and go back to NoDo it shouldn't cause an issue - so, when Mango does officially come out for these handsets, I should get it with no issues. Here's hoping that happens sometime soon as I'm getting quite fed up - all my mates and even my brother are fully mango'd
---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------
Congratulations to you Drado, I'm extremely jealous. Here's hoping your update is the start of many updates to these handsets, especially mine lol

17-apg said:
I put mine back to Nodo a few days ago and just got the official Mango via Zune today. Now, my details are:
OS 7.10.7720.68
FW 2424.11.3.1
HW 3.15.0.4
Radio SW 2424.11.7.2
Radio HW 0.0.0.800
Bootloader 5.8.1.0
Chip SOC 0.36.2.0
Click to expand...
Click to collapse
I'm on Mango final... no tricks at all just prompeted by my carrier.
OS 7.10.7720.68
FW 0222.11.8.5
HW 3.15.0.4
Radio SW 2424.11.7.2
Radio HW 0.0.0.800
Bootloader 5.8.1.9
Chip SOC 0.36.2.0
I've been having loads of issues with it. I had no problems whatsoever on NoDo.
Slooooow boot ups. (sometimes fast sometimes takes a couple of mins)
Sometimes if i switch it off and on it locks up and just displays the battery indicator. No home screen. (need to pull the battery)
Problems with the data connection dying requiring a soft reset of the phone to re-enable. (this is a MAJOR issue)
Started having bluetooth issues - it wont discover anything sometimes. (seems to work if i switch on WiFi as well. wtf?)
Info slow to appear on lock screen.
Keyboard closes itself randomly (known issue i see)
Really un-impressed with Mango. I've just hard reset my device so will see if that helps at all.

Kash511 said:
Aaah,nah I already forced it and wasn't happy as the firmware was completely wrong, the reason I reverted back to NoDo was because of that issue. On a positive note, I sent a tweet to windowsphonehelp (or whatever they're called) and they responded back saying if you've forced it and go back to NoDo it shouldn't cause an issue - so, when Mango does officially come out for these handsets, I should get it with no issues. Here's hoping that happens sometime soon as I'm getting quite fed up - all my mates and even my brother are fully mango'd
---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------
Congratulations to you Drado, I'm extremely jealous. Here's hoping your update is the start of many updates to these handsets, especially mine lol
Click to expand...
Click to collapse
For your info after the Zune tric install here are my stats!!
FW 2424.11.8.5
HW3.15.0.4
Radio SW 2424.11.7.2
Radio HW 0.0.0.800
Bootloader 5.8.1.9
So my specs are close to most others on here so I dont think I will force back to NODO to wait for official Mango. My phone is working 100% on every level right now so i will leave well enough alone for now!!
Let me know when you get the official release and your stats when installed.

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