Background info:
All Dell android devices use 'pkgs' as their method of doing rom updates.
The VP uses FFUs as it's a WP7 device, I believe that pkgs (which are unique to dell devices) are functionally very similar to FFUs (which are used by all WP7 devices(?) )
I am the master maintainer of Dell device pkgs and have the largest collection outside Dell itself. I am in the process of researching VP FFUs in the hopes of being able to mirror and provide guides on restoring back to stock roms.
Unfortunately the biggest difference is that FFUs appear to be internal-use only, as in they're ment for servicing tools used only by dell(?).
PKGs are intended for consumer use, and the OTA ones are available on dell's update-site: mobileupdate.dell.com
If this is true, then FFUs are much less common, and from what I've seen the only FFU available is for 104 (See Dell Venue Pro # Official Roms - XDA wiki for more information, and Dell Venue # Official Roms -XDA wiki for a comparison)
updatewp7.exe is similar to fastboot on android, it allows you to directly upload images to the device's respective partitions(?)
Also: the words 'rom' 'firmware' 'drivers' will be used interchangably here, they all mean the same thing.
Information:
The updates available to you are the same as on dell android OTAs, it depends on your currently installed rom.
Currently the track is:
00 EU/US (unlocked) devices get updates first
31/33 (at&t and tmobile USA respectively) get updates afterwards, which is consistant with the way dell manages their ota updates.
Bar the fact that Dell is contractually obligated to release them in a 'timely' manner, 31/33 devices are usually last to get them as they're carrier branded devices.
When the VP was released the primary region was 33 though so it was by default the target region.
As the VP is available unlocked the 00 region has taken over as the one to recieve them first.
Externally (visible to all users though system:about) there are two major version numbers:
OS version: which is the installed version of WP7
Firmware version: which is the part we're interested in
Internally, it's somewhat different (checkable though EM:phone information)
SW version:
OS version from before
Actual oem version
current lock status (?)
SW build date & time:
Example:
My current rom is OS 7720/FW 219, which would look like:
Externally:
OS version: 7.10.7720.68
Firmware version: 2250.1800.7720.219
Internally:
2250.1800.7720.219
GLEOS2A421933_s
TMO-US
Build date: 20110822 18:33:15
Translated: WP7 7720
Firmware version: 219
Hardware version: 2A4
Region: 33 (TMO-US)
Build date: Aug 22, 2011
General rom update process:
When an update is available, zune downloads the following files:
If available, a delta from <your installed version> to <the current version>
VP driver cab
The first set is an oversimplication, but essentially it is a dozen cabs that comprise the full update.
These are not device specific and are the same for all devices that are eligible to update(?)
The last file is device and carrier specific. These are what sets each individial device and carrier apart from eachother.
What I need from you:
Internal version numbers from EM app
Charastics of your device
Relative age (launch, near launch, very recent, etc)
Side of preinstalled sd card
Original lock condition and current lock condition
How to find internal version numbers:
Turn on device and open up dialer
Dial "##634#" (without the quotation marks)
Select "Phone Information"
Finished
What I hope to come out of this:
More complete list of VP roms (firmware)
Information on the hardware submodel numbers
Possibly a guide for flashing the VP
Currently confirmed submodels and regions:
Submodels:
1A4
2A4
Regions:
00EU - Unlocked EU Retail
00US- Unlocked US Retail
31 - At&t
33 - T-Mobile (USA)
Current OS version:
00EU - 8107
00US - 8107
31 - (?)
33 - 7720
my dvp too has the same specs as you have mentioned
2250.1800.7720.219
GLEOS2A421933_s
TMO-US
Build date: 20110822 18:33:15
Further hardware build is 2.1.2.0.0
EM is 1.12
Still have not got the 8107 update nor the 7740 update. Force updates too dont work. Seems all users with this specific model are not getting the new updates.
Yea, yours looks pretty much identical to mine. Is yours an 8gb one?
TheManii said:
Yea, yours looks pretty much identical to mine. Is yours an 8gb one?
Click to expand...
Click to collapse
Yes 8GB.
Also one thing I have noted is that I m not facing the disappearing keyboard issue most users are complaining. not sure if i m missing anything in terms of understanding the problem. but the keyboard both software one and the hardware one work fine without any issue
my dvp too has the same specs as you have mentioned
2250.1800.7720.219
GLEOS2A421933_s
TMO-US
Build date: 20110822 18:33:15
Further hardware build is 2.1.2.0.0
EM is 1.12
Still have not got the 8107 update nor the 7740 update. Force updates too dont work. Seems all users with this specific model are not getting the new updates.
my phone 16gb
Once I get a couple version numbers from non tmo branded devices I can draw a conclusion.
But my current thinking is that 219-33 ones that came with it preinstalled are intentionally not being given updates (or the converse, they forgot to add 219-33 to the update whitelist)
On the S5 and V, several pre-installed roms have no upgrade paths and must be manually upgraded for this very reason. These specific roms are ONLY available pre-installed and other devices of the same grouping can update because they have a common rom.
Example:
An S5 with 347 preinstalled cannot OTA to 351, but an S5 with 318 can OTA to 351. 347 can be easily manually upgraded to 351.
All 3 mentioned roms are intended for generic/retail S5's which is now the majority of the remaining S5's available.
Mine Europe Factory unlocked 8Gb with Mango update installed. Buyed new early summer 2011.
From EM:
SW version
2250.1800.7720.219
GLEOS2A421900EU_S
000-88
HW version
2.1.2.0.0
SW build date & time
20110822 17:12:49
From Settings/About:
OS version 7.10.8107.79
Firmware revision number: 2250.1800.7720.219
Hardware revision number: 112.576.2.0
Partition Layout FFU file - example:
information table --> HashTable.blob
amss.mbn
appsboot.mbn
apps.mbn
dbl.mbn
dsp1.mbn
fsbl.mbn
osbl.mbn
+
OS Section
-->User Part etc...
-->BLDR
-->SLDR
-->NK
-->IMGFS
-->Users Sector etc....
Igoran said:
Mine Europe Factory unlocked 8Gb with Mango update installed. Buyed new early summer 2011.
From EM:
SW version
2250.1800.7720.219
GLEOS2A421900EU_S
000-88
HW version
2.1.2.0.0
SW build date & time
20110822 17:12:49
From Settings/About:
OS version 7.10.8107.79
Firmware revision number: 2250.1800.7720.219
Hardware revision number: 112.576.2.0
Click to expand...
Click to collapse
Ah finally an AWS user that isnt tmo (hardware wise it's an AWS model still) Like I thought EU would be 00 or something, I'll update the OP.
00EU is a funny way to do it, then again the way they did it on the S7 isnt any better
They could have done 00 = Unlocked EU, 30 = Unlocked US
Perhaps 219-00xx is given updates and 219-33 isnt. So far that fits the pattern
Nokser said:
Partition Layout FFU file - example:
information table --> HashTable.blob
amss.mbn
appsboot.mbn
apps.mbn
dbl.mbn
dsp1.mbn
fsbl.mbn
osbl.mbn
+
OS Section
-->User Part etc...
-->BLDR
-->SLDR
-->NK
-->IMGFS
-->Users Sector etc....
Click to expand...
Click to collapse
Is there a DT.img? Besides that and the android-specific boot/recovery/system.imgs it's virtually identical to the contents of a pkg (which makes sense, they fulfill the same role)
Edit: Managed to extract the NK and imgfs parts, havnt figured out how to extract the others
Igoran said:
Mine Europe Factory unlocked 8Gb with Mango update installed. Buyed new early summer 2011.
From EM:
SW version
2250.1800.7720.219
GLEOS2A421900EU_S
000-88
HW version
2.1.2.0.0
SW build date & time
20110822 17:12:49
From Settings/About:
OS version 7.10.8107.79
Firmware revision number: 2250.1800.7720.219
Hardware revision number: 112.576.2.0
Click to expand...
Click to collapse
Mine is the same as above.
Can anyone get and upload ffu file of 219.33?
http://mobileupdate.dell.com/?version=GLEOS2A421933 -doesnt work.
multiupload.com with VenuePro_flash_GLEOS2A_US_TMO_SIGNED_SWV0105_LP003 0_RV001_RETAIL.zip doesnt work either.
It doesnt work with the VP as dell doesnt host them themselves (because it runs WP7), it's all done though windowsupdate.com
The FFU's, even though they are similar to PKGs are not intended for general release. It would be closer to QDL tool as those are not ment for general release, but have the capability of restoring a bricked device.
What do you mean- Flashing of VenuePro_flash_GLEOS2A...ffu via zune updatewp.exe will lead to brick?
QDL tool, as we seen on service manual. I bet update rom is stored on sd-card too. Yes another questions who can get this tool and how to read unknown formatted sd-card?
I need any PDA retail or TM ffu for this device to try to flash and modify if it works..
heineken78 said:
What do you mean- Flashing of VenuePro_flash_GLEOS2A...ffu via zune updatewp.exe will lead to brick?
QDL tool, as we seen on service manual. I bet update rom is stored on sd-card too. Yes another questions who can get this tool and how to read unknown formatted sd-card?
I need any PDA retail or TM ffu for this device to try to flash and modify if it works..
Click to expand...
Click to collapse
Not sure what you're talking about,
but with regards to the sdcard, WP7 devices 'lock' them so they're difficult to reformat for use as a normal sd card.
Updated op with more info, will eventually move it all over to the wiki once there's enough to warrent it's own page/section on a page
Still missing info from a at&t VP, and any other carrier ones that i'm unaware of
Can I install roms of Venue Pro to my Dell Venue, which runs android
mikecore said:
Can I install roms of Venue Pro to my Dell Venue, which runs android
Click to expand...
Click to collapse
If the files get rewritten to the specs of it yes. Otherwise that would just cause it to either brick or bootloop.
Related
Hi
I seem to remember a post about firmware versions,
what the current generic firmware version is and what the carrier versions are...
Can anyone help me find it ?
Thanks
Found it !!
Originally Posted by rhedgehog
of course not, don't be silly. you just don't understand how the ROM names work. They don't work like software version numbers usually do.
the rom codes have a specific code layout - X.XX.YYY.Z
X.XX (in this case 1.15) is the ROM version. Higher means newer. All these roms are 1.15 so they are all the same ROM.
YYY (405, 110, 60 etc) is the Region/Network code. Higher does NOT mean newer. this number tells you Who, and Where the ROM is intended for:
405 means it is a European HTC ROM
110 means it is a T-Mobile Europe ROM
60 means it is an Orange ROM
61 is Vodafone i believe
Asian devices have codes in the 700 range
Z is the revision number, and only denotes a minor change. Each ROM will have a different revision number as each network customises differently. This is only really relevant when comparing to the same brand code. so if you have 1.15.405.4 and then 1.15.405.20 comes out, then you need to update.
so, all the ROMs are version, 1.15. They are all the same, they are just different brands.
Click to expand...
Click to collapse
So what should I be looking for as the generic firmware ?
1.15.405.4
Generic ROM is 1.15.405.4
**SNAP**
"Samsing Update for Windows Phone"
Seems like Samsung is on the go again. Currently got this update (when eagerly coding code, switching windows back and forth).
So what is this (new) update?
- Anyone heard any news what it is (or even got it)?
I took a screenshot before updating, to compare with the new one if there is a difference (result when update finished).
Attachment for eye visuals
edit:
Seems like its two rounds of update's
edit 2:
"What changed"
- Free'd space on the device? (200 MB for me)
- Updated Firmware (2424.11.9.2), Radio (242.11.9.1) and Bootloader (5.9.0.6)
//fiinix
fiinix said:
"Samsing Update for Windows Phone"
Seems like Samsung is on the go again. Currently got this update (when eagerly coding code, switching windows back and forth).
So what is (new) this update?
- Anyone heard any news what it is (or even got it)?
I took a screenshot before updating, to compare with the new one if there is a difference (result when update finished).
Attachment for eye visuals
//fiinix
Click to expand...
Click to collapse
Is your device branded or unbranded ?
What´s your current firmware ?
I don´t get any update information....
I got it now, I've not heard about that. I didn't notice a thing for now. I hope we will get an explanation about this.
contable said:
Is your device branded or unbranded ?
What´s your current firmware ?
I don´t get any update information....
Click to expand...
Click to collapse
Mango Final
Samsung Omnia 7
Unbranded
Can't see much more right now; Currently _in_ the update progress.
fiinix said:
Mango Final
Samsung Omnia 7
Unbranded
Can't see much more right now; Currently _in_ the update progress.
Click to expand...
Click to collapse
Ok.
Final Mango has firmware 2424.11.8.5,
The latest SFR-France update has firmware 2424.11.9.3
and
The latest T-Mobile update 2424.11.9.4.
Just for you info...
I would say it´s the latest samsung update for unbranded devices.
---------- Post added at 09:35 PM ---------- Previous post was at 09:05 PM ----------
The carrier updates have the same radio version: 2424.11.9.1.
As mentioned before what you got is the latest update for unbranded devices.
Anyway good to know that it´s available...
When you get a chance, dump the update logs and see what changed.
I have an unbranded handset, changes are the same as first post:
Before:
OS : 7.10.7720.68
Firmware revision : 2424.11.8.5
Hardware revision : 3.15.0.4
Radio software : 2424.11.7.2
Radio hardware : 0.0.0.800
Bootloader : 5.8.1.9
Chip SOC : 0.36.2.0
After Update
OS : 7.10.7720.68
Firmware revision : 2424.11.9.2
Hardware revision : 3.15.0.4
Radio software : 2424.11.9.1
Radio hardware : 0.0.0.800
Bootloader : 5.9.0.6
Chip SOC : 0.36.2.0
** No internet tethering **
Some people have gotten Internet Sharing from FW 11.9.4
I'm using the unbranded generic UK FW and only gotten 11.9.2. With no internet sharing. Others?
I'm hoping this fixes the data issues when enabling/disabling. So I don't have to restart 50% of the time.
Does it break the jailbreak
When updating this new update, does it break the jailbreak.
It is approx. 14 days back, I received a Zune update for my Omnia7 (T-Mobile CZ).
After update:
Firmware: 2424.11.9.4
Radio soft.: 2424.11.9.1
Bootloader : 5.9.3.0
+ Internet Sharing
rastascan said:
I have an unbranded handset, changes are the same as first post:
Before:
OS : 7.10.7720.68
Firmware revision : 2424.11.8.5
Hardware revision : 3.15.0.4
Radio software : 2424.11.7.2
Radio hardware : 0.0.0.800
Bootloader : 5.8.1.9
Chip SOC : 0.36.2.0
After Update
OS : 7.10.7720.68
Firmware revision : 2424.11.9.2
Hardware revision : 3.15.0.4
Radio software : 2424.11.9.1
Radio hardware : 0.0.0.800
Bootloader : 5.9.0.6
Chip SOC : 0.36.2.0
** No internet tethering **
Click to expand...
Click to collapse
I had the same update, didn't noticed any change in performances or features...
just got the 2 updates also.
my device was a t-mobile uk which I forced nodo on previously and most recently mango, no not the carrier updates.
my stats:
os: 7.10.7720.68
fw: 2424.11.9.2
hw: 3.15.0.4
rs: 2424.11.9.1
rhw: 0.0.0.800
bl: 5.9.0.6
soc: 0.36.2.0
confirmed no tethering option
please don't make me have to downgrade and use the official t-mobile bloated software to get thethering
Tethering on Omnia 7
I succeeded in getting tethering on my Omnia 7, as follows:
1. Make sure you have the update talked about here.
2. Your phone must be unlocked - I have the Chevron unlock.
3. Get the following xap file: http://forum.xda-developers.com/attachment.php?attachmentid=772980&stc=1&d=1320528530 and use the Application Deployment tool to send it to your phone.
4. Install the Diagnosis app (if you haven't got it already) by typing ##634#.
5. In the Diagnosis app type *#9908#, select "System Tweaks". Press Save, then Close, then restart the phone.
6. You now have "Internet sharing" in your system setup menu.
7. If you now lost your cellular data connection (I did and almost panicked ) restore it by using Samsung's Network Profile app - worked for me.
8. Everything working perfectly for me now!
Reference: http://www.mobiletechworld.com/2011...msung-omnia-7-and-samsung-focus-in-one-click/
Guys. What's new in this update?
Unbranded handset on Orange RO here, got the 2 updates today, didn't notice anything new besides the extra megs, no internet sharing.
hujer said:
It is approx. 14 days back, I received a Zune update for my Omnia7 (T-Mobile CZ).
After update:
Firmware: 2424.11.9.4
Radio soft.: 2424.11.9.1
Bootloader : 5.9.3.0
+ Internet Sharing
Click to expand...
Click to collapse
I also received it 14 days ago. Samsung Omnia 7 (16GB) here with T-Mobile Germany branding.
OS: Mango (7720.68)
Firmware: 2424.11.9.4
Radio: 2424.11.9.1
Bootloader: 5.9.3.0 (yeah I got the new bootloader )
I received Internet sharing on the first day with Mango.
Guess this is only a little refresh for unbranded devices to clean up some junk and add internet sharing.
Recieved the update just now.
Samsung Omnia 7
OS: 7.10.7720.68
FW: 2424.11.9.2
HW Rev: 3.15.0.4
Radio SW: 2424.11.9.1
Radio HW: 0.0.0.800
Bootloader: 5.9.0.6
Got Internet Sharing added under Settings, haven't looked thoroughly for any other changes.
update in progress, Omnia 7 on Orange UK.....
EDIT
I see 2nd update being applied.
so people can only get tethering if you are either
a) chevron unlocked (which means downgrading etc etc)?
or
b) on the official carrier OS?
what about unbranded devices? are we not to get it because our OS is not carrier branded?
Not all of us are chevron unlocked (just in case people on here forget!)
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
did you have the unbranded mango rom? or is this carrier mango?
Boblebad said:
Recieved the update just now.
Samsung Omnia 7
OS: 7.10.7720.68
FW: 2424.11.9.2
HW Rev: 3.15.0.4
Radio SW: 2424.11.9.1
Radio HW: 0.0.0.800
Bootloader: 5.9.0.6
Got Internet Sharing added under Settings, haven't looked thoroughly for any other changes.
Click to expand...
Click to collapse
Samsung Omnia 7
- Stock, clean, SIM free, not branded device. (Not debranded.)
- Curently on T-mo, Macedonia.
- No internet sharing after the update.
Almost everyone on branded devices got the IS.
Apparently MS or manufacturer enabled only those devices that have a clear permission from the carrier on carrier devices only. Hope I'm wrong.
Disappointment is obvious, lessons learned.
KraFT
OS: 7.10.7720.68
FW: 2424.11.9.2
HW Rev: 3.15.0.4
Radio SW: 2424.11.9.1
Radio HW: 0.0.0.800
Bootloader: 5.9.0.6
Goodnight community,
there is a new update for the Samsung Omnia 7 avaible. It was released 6 minutes ago. My phone is the 16 GB version with Telekom Germany branding.
As most of you know, 7.10.7720 was the newest Mango, but now I have 7.10.7740.16.
Click the link below for a screenshot of the update message.
http://img213.imageshack.us/img213/918/newupdate.png
I am the first who updated my device to this version according to this site:
http://www.lynxinteractive.com/WP7DeviceStats/
Also according to that site, only the Nokia Lumia, the HTC Titan and the HTC HD7 were running this version of Mango.
A dump of the Settings -> Info page:
OS: 7.10.7740.16
Firmware: 2424.11.9.4
HW: 3.15.0.4
Radio: 0.0.0.800
Bootloader: 5.9.3.0
SOC: 0.36.2.0
Translated changelog:
- Fixed an E-Mail bug with Microsoft Exchange Server 2003.
When replying or redirecting a mail, it will contain the text of the previous mail.
- Fixed a bug with the Mailboxnotifications.
-mSc
Did you lose your jailbreak?
StefanBN said:
Did you lose your jailbreak?
Click to expand...
Click to collapse
I did not.
Custom accent colors, Zune SmartDJ modifications, ..., even the Interop Unlock is still present.
My father has the same phone as I do, unlocked the same way and also running most of the modifications I have on my own phone.
There is no update avaible for him.
Thanks. I just hope that this update fixes color banding on my Omnia..
What a nice birthday gift!
No update for me though... unbranded UK CSC...
nothing for H3G
Guys, i own an unbranded omnia 7 and my firmware is still 2424.11.8.2, i wonder if i should try to push the firmware manually or it's just as it should be ..
StefanBN said:
Thanks. I just hope that this update fixes color banding on my Omnia..
Click to expand...
Click to collapse
I looked into it in WP Bench, the issue is still present.
If you have got a developer unlocked device, you can fix the issue yourself within 2 minutes.
To the rest: No update message for my second Omnia 7. I'll try to answer all questions and will let you know whenever I see an update popup.
Yes, I've Interpop unlocked my phone, but it is on Mango. There is no fix, as I know for Mango, only for NoDo.
Weird......
Ive got a Mozart and Titan.
Mozart is branded UK Orange, The Titan is unbranded.
Both have had an update through Zune in tha last 20 minutes or so.......
The Mozart is 7740.16, My Titan is still 7720.68
No internet sharing on Mozart.....
My Samsung Omnia 7 Device got an Update too. But i dont have any information about the Changelog - in Zune there is no such Updateinformation.
Strange...
no update for LG c-900b
in fact still waiting for tethering drivers update...
I wonder if this update also fixes the disappearing keyboard issue.
Zunes starts updating, phone reboots, aaaaaannnnnd:
Error
Code:
================================================
START OF UPDATEVALIDATOR ERROR MESSAGES
================================================
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: IUCORE cannot find a path to highest expected version of: 7.10.7740.16
ERROR: UpdateOrderFromFileList: ULDR Update: ULDR Update Failed with HRESULT : 0x80180048
=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================
UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE 1 : iucore.7.10.7720.68-7.10.7740.16.cab.pku ERROR CODE: 0x80180048
Total number of Bad Packages: 1
Process Failed with code 0x80180048
UpdateValidator finished at 05:47:36 04/21/1980
Samsung Omnia 7, Orange UK, fw 0222.11.8.5, bl 5.8.1.9, not unlocked.
Has anyone else experienced a similar error?
same here, orange aswell.. but Im living in Brazil..
dunno if it's related but i've used the samsung firmware updater =[
Few minutes ago installed same update to LG Optimus 7 via Zune.
here in austria, my devices have no updates. omnia 7 and optimus 7. both unbranded ...
Country: England, Network: T-Mobile, Device: Samsung Omnia7
Unbranded 000-88 -> No Zune Update
Samsung Omnia7 T-Mobile UK TMO-GB (via Regedit) -> Zune update for 7.10.7740.16
BUT update fails, as I had used WP7 cab sender to force SFR-FR KI3 firmware.
I think flashing cabs halts the Zune update path.
I think I'll flash a preNoDo branded TMU Rom very shortly and update all the way via Zune. Damn branded is the way to go :-/
just to add a little piece of information: no updates for htc mazaa available
HI
now been updated
http://forum.xda-developers.com/showpost.php?p=19430778&postcount=53
ya, I think the samsung SFR-FR KI3 thing f*ked up our updates u.u
- update the firmware using SFR-FR KI3
- connected to macintosh wp7 utility - no updates
- connect to zune (via bootcamp) - new update = FAILED
- phone reset
- macintosh utility wp7 - no updates again
- zune - no updates
Tried to use the Windows Support Tool, by setting my device into recovery mode, but the freakin tool didnt recognize
same thing with my friend's omnia, which is basically the same: Orange uk, SFR-FR KI3, 7720
and they say android is fragmented ._.
Hi, im L900 indonesian (no carrier sim lock) newbie user..
why i cant find any phone update for my phone?
is it because i have up-to-date version (i dont think so)?
Info:
OS ver : 7.10.8773.98
Firmware rev : 2175.2101.8779.12201
Radio software ver : 2.1.75.20
Bootloader ver: 7.17.2.0
Arc's Soul said:
Hi, im L900 indonesian (no carrier sim lock) newbie user..
why i cant find any phone update for my phone?
is it because i have up-to-date version (i dont think so)?
Info:
OS ver : 7.10.8773.98
Firmware rev : 2175.2101.8779.12201
Radio software ver : 2.1.75.20
Bootloader ver: 7.17.2.0
Click to expand...
Click to collapse
Looks like your OS, FW and Radio are all 1 version behind. Bootloader didn't change.
Current:
OS: 7.10.8779.8
FW: 2175.2301.8779.12223
Radio: 2.1.75.22
I have seen word of a slightly newer firmware, but that's not verified.
Have you plugged your phone into a PC running Zune software?
Sent from my Lumia 900 using Board Express Pro
jimski said:
Looks like your OS, FW and Radio are all 1 version behind. Bootloader didn't change.
Current:
OS: 7.10.8779.8
FW: 2175.2301.8779.12223
Radio: 2.1.75.22
I have seen word of a slightly newer firmware, but that's not verified.
Have you plugged your phone into a PC running Zune software?
Sent from my Lumia 900 using Board Express Pro
Click to expand...
Click to collapse
i always conenct it to zune everyday to check for update and turn on phone update setting , but it always up-to-date.
where i can get newest update? is it because the region problem?
Arc's Soul said:
Hi, im L900 indonesian (no carrier sim lock) newbie user..
why i cant find any phone update for my phone?
is it because i have up-to-date version (i dont think so)?
Info:
OS ver : 7.10.8773.98
Firmware rev : 2175.2101.8779.12201
Radio software ver : 2.1.75.20
Bootloader ver: 7.17.2.0
Click to expand...
Click to collapse
i sent my Lumia 900 for repair, as it was having some hang issues as i droped it. nokia changed my screen and microphone and also updated OS to 7.10.8779.8
so, can i just send my lumia to nokia and ask them to update OS for me? or i can update it my self? i try to installing nokia care suite and it said my software is not upgradeable.. and for the new software is 2175.1601.8773.12141
you can see it at here <s10.postimage.org/bmdg8coop/downgrade.jpg>
Arc's Soul said:
so, can i just send my lumia to nokia and ask them to update OS for me? or i can update it my self? i try to installing nokia care suite and it said my software is not upgradeable.. and for the new software is 2175.1601.8773.12141
you can see it at here <s14.postimage.org/xrsd8zt9d/downgrade.jpg>
Click to expand...
Click to collapse
According to the image you posted, you have a newer version installed on your phone than the Nokia Suite is showing. It appears you are ahead.
PS: When posting a photo like that, you should probably try to black out the IMEI number. I don't know if it's still being done, but in the past, people would use your IMEI number to clone another device. Would not hurt to black out the MAC also.
I just noticed that your OS and Firmware are out of sync. They should both be 8773 or 8779. How did that happen? Your 8779 Firmware may be indicating that the 8779 OS is already there. Hence, your phone may think it's up to date.
Sent from my Lumia 900 using Board Express Pro
SuperSport said:
According to the image you posted, you have a newer version installed on your phone than the Nokia Suite is showing. It appears you are ahead.
PS: When posting a photo like that, you should probably try to black out the IMEI number. I don't know if it's still being done, but in the past, people would use your IMEI number to clone another device. Would not hurt to black out the MAC also.
Click to expand...
Click to collapse
oh, thanks i never know about that
jimski said:
I just noticed that your OS and Firmware are out of sync. They should both be 8773 or 8779. How did that happen? Your 8779 Firmware may be indicating that the 8779 OS is already there. Hence, your phone may think it's up to date.
Sent from my Lumia 900 using Board Express Pro
Click to expand...
Click to collapse
for the first time,the seller tell me its better to create new email account according to use registered account, i created new one.. but after that i reset the phone from about setting.. and i use the account that i already created... and i get phone update from zune without update info..
how i fix this? how if i update/downgrade it from nokia suite and then update it from zune?
anyone can help me through this??
My Lumia shows
OS version 7.10.8779.8
Firmware revision number 2175.2503.8779.12301
Radio software version 2.1.75.25
Bootloader version 7.17.2.0
Sent from my Lumia 900 using Tapatalk 2
I just got an update changing firmware to *.12301 as well...
zune shows me i already have the lastest update.. and nokia pc suite shows me previous version..
OK,
I've got what I believe is the full update of the 7.8 push for the ATT version of the Lumia 900 These are the version numbers I'm seeing. Anyone seeing different? (i.e. newer)
OS version: 7.10.8858.136
Firmware revision number: 2175.2307.8858.12480
Hardware revision number: 112.1914.2.0
Radio software version: 2.1.75.22
Radio hardware version: 8055
Bootloader version: 7.17.2.0
Chip SOC version: 0.85.2.1
(I would expect that some of the hardware revs might be different as this was a relatively early production phone)
- Michael
Not that anyone expected differently, but this is exactly what I have from doing the NCS flash via Navifirm last week.
eknutson said:
Not that anyone expected differently, but this is exactly what I have from doing the NCS flash via Navifirm last week.
Click to expand...
Click to collapse
Thanks for confirm though. I hadn't seen any full version list yet from the MS-Update method so I though I'd stick it up here.
Update process went pretty smoothly for me. 1st two updates were O/S (with the 2nd being the 7.8 build) with the 3rd being the Nokia-specific hardware update. The Nokia update choked the 1st time, but after I freed up 2GB of storage it ran fine.
Another NCS flash here. This was helpful, thanks!
MKohlman said:
Thanks for confirm though. I hadn't seen any full version list yet from the MS-Update method so I though I'd stick it up here.
Update process went pretty smoothly for me. 1st two updates were O/S (with the 2nd being the 7.8 build) with the 3rd being the Nokia-specific hardware update. The Nokia update choked the 1st time, but after I freed up 2GB of storage it ran fine.
Click to expand...
Click to collapse
My pleasure - thanks for posting this! I re-read what I posted, and meant that it isn't a surprise that what I flashed last week isn't newer. It was a relief to see that they were the same though, heh.