Related
"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
Hello, I would like to update my Trophy to the last update, Ihad 7720 but I couldn't update to 7740 as I undersatnd from the UM2 threadit maybe because I have bootloader 4.6 . I reverted back to 7403 restore point but I still cannot flash an official Europe ROM, in order to downgrade the bootloader and SPL.
I recieve a Vender ID error when I try to flash another official Spark ROM.
I tried almost all the ROMS from the wiki download list.
I presume my phone is branded but I dont know on to which network, I recieved the phone as a gift and it had no operator menus.
Can you please help, by telling me which ROM should I install? or how can I find out if and to wich operator the phone is branded.
My info :
OS ver: 7.0.7403.0
FW: 2250.09.11004.401
HW: 003
Radio sw: 5.69.09.05a_22.50.50.21u
Radio hw: A.102.0.d4
Bootloader: 4.6.2250.0(129185)
Chip: 2.2.5.0
Thanks in advance
A) Wrong forum. Either post in the Q&A section or a device-specific forum.
B) The CAB-sender tool will show you your device branding string.
C) A registry browser can read the device branding string out of the DeviceTargetingInfo key (use search to find exact path).
D) If you want to downgrade the SPL, no need to flash the entire ROM; the SPL is a separate part of the image and can be flashed alone (without even wiping the phone).
viperthevenom said:
I presume my phone is branded but I dont know on to which network [...] or how can I find out if and to wich operator the phone is branded.
[...]
FW: 2250.09.11004.401
Click to expand...
Click to collapse
This is HTC Europe, also known as "unbranded". Read about characteristics value et. al..
Thread Closed
Not development!
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.
Hello I had bad experience in flashing random ROMs so now I need your help. Months ago I wanted official ROM and flashed without nowing what and brick my phone, motherboard changed so ...
Now I used the software called seveneighter that update to 7.8 using cabs, but I stuck on as you see 8783 in my About version, now when I try to update using zune it shows error 80180048 that's why I need the stock official ROM for my phone and start the updates all over again, please give me which is the right ROM for my phone I want to stock official. If you can tell me how to resolve this error I will be grateful too if I am able then to install 7.8 using zune, I have developer account so I can install xaps if that is needed.
OS version:7.10.8783.12
Firmware revision number: 2250.21.51303.401
Hardware revision number: 0004
Radio software version: 5.71.09.02a_22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 5.13.2250.3(135167)
Chip SOC version: 2.2.5.0
Thank you very much in advance
Hello I made a lot of threats and we discussed that the only way for returning to 7.5 without backup is installing the original ROM but I do not understand why when I tell what is my device information just everybody stops talking, this happened in 3-4 threats is there something that people are afraid or please tell me which original ROM should I install on this device, from here http://forum.xda-developers.com/showthread.php?t=2112687 or another place I do not know.
Firmware revision number: 2250.21.51303.401
Hardware revision number: 0004
Radio software version: 5.71.09.02a_22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 5.13.2250.3(135167)
Chip SOC version: 2.2.5.0
liduray said:
Hello I made a lot of threats and we discussed that the only way for returning to 7.5 without backup is installing the original ROM but I do not understand why when I tell what is my device information just everybody stops talking, this happened in 3-4 threats is there something that people are afraid or please tell me which original ROM should I install on this device, from here http://forum.xda-developers.com/showthread.php?t=2112687 or another place I do not know.
Firmware revision number: 2250.21.51303.401
Hardware revision number: 0004
Radio software version: 5.71.09.02a_22.51.50.21U
Radio hardware version: A.102.0.D4
Bootloader version: 5.13.2250.3(135167)
Chip SOC version: 2.2.5.0
Click to expand...
Click to collapse
Your device is from Europe (2250.21.51303.401 .. the 401 means Europe)
From the above thread you need this Rom
RUU_Mozart_HTC_Europe_1.28.401.04_5.52.09.16_22.33 a.50_RELEASE
http://ul.to/q5w5kyb9
thank you, so flashing this I won't break my phone like the last time flashing random ROMS and change the motherboard after that ?