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.
The UK T-Mobile Vivacity is updated, latest official UK T-Mobile Vivacity terminal software online upgrade tool is released on April 18, log in ZTE UK website(zteuk.co.uk), click Devices, choose T-Mobile Vivacity,click Product support, then download the Vivacity terminal software online upgrade tool to update the mobile phone.
Be sure to back up personal data before update.
In a desperate move to root my mobile, I messed with it and bricked. I wanted to remove preloaded junk apps to spare some internal memory. Though its good mobile but lacks space on internal memory. Now I need Stock Rom for my mobile of following specification.
Model - Callbar A1 (Manufactured by WingTech)
Android - 2.3.5
Kernal Version – 2.6.35.7
Software version – 2.3.001.P1.12065
Hardware version – P1
CPU – SC6820 (1 Ghz.)
Screen – 3.5” HVGA
RAM 256 MB
Internal Memory 220 MB
Any help would be appreciable. I am ready to explore and experiment because handset is already not working. Images of handset are given below.
Official Stock ROMs of Callbar Mobiles
UPDATE
Original Stock ROM of CallBar Mobiles is available on following official link.
Millions of Thanks to Company's Sales Head Officer in my country to whom I talked on Mobile. He was kind enough to spare his precious time and guided me to download StockRom and flash it properly. Without naming him on this public portal, I would like to tell that he is Great Person.
There are 3 Stock ROMs for Models CallBar A1, CallBar A2 and CallBar Tab7 available under the Modem Driver Download Section. The Rar File includes all tools and software required for flashing.
Here is the link
Thread closed at Op's Request.
Thanks
SacredDeviL666.
ZTE V790 upgrade
good afternoon, I have a mobile phone zte v790 I bought unlocked in the uk and it came with android 4.0.
I know that this mobile phone can upgrade to the version 4.1 but the problem is that the file has the update zte has on site site, which has to be done through the sd card is corrupted!! and honestly no longer know where to find it.a zte Portugal doesnt provides assistance to tels purchased outside portugal which is stupid.thus decided to get your help.I hope you can.best regards,azoreangirl
azoreangirl said:
ZTE V790 upgrade
good afternoon, I have a mobile phone zte v790 I bought unlocked in the uk and it came with android 4.0.
I know that this mobile phone can upgrade to the version 4.1 but the problem is that the file has the update zte has on site site, which has to be done through the sd card is corrupted!! and honestly no longer know where to find it.a zte Portugal doesnt provides assistance to tels purchased outside portugal which is stupid.thus decided to get your help.I hope you can.best regards,azoreangirl
Click to expand...
Click to collapse
I'm also looking for a solution to update my V790. Did you have any luck? I couldn't even find a newer ROM for it.
Hey guys,
I'm on:
Viper10 5.3.0 - Android 7
Magisk 11.1
Magisk Manager 4.1
FW 2.41.617.3
S-OFF
BL: LOCKED
and wanted to use Android Pay with my Austrian debitcard (Bank Austria & EasyBank) and VISA Card.
Go to:
Settings
Google
Android Pay
Add credit-/debitkard
-------
Credit card VISA
Fill in my VISA card no.
"Cannot use card with Android pay"
-------
Depitcard BankAustria &/or EasyBank
Fill in my card no.
"Card type not allowed"
I don't know what's the problem.
Hopefully someone knows what to do.
Hi buddy, I have a question about my HTC 10 which from Aus too ^^ Does your device have an update to Android 7.0? My device still in Android 6.0 now and I dont know how long to have an update to 7.0
Hey,
well I'm on Android 7. But I flashed a custom rom that is based on Android 7. I flashed the Rom: "Viper10 5.3" from here
http://venomroms.com/viper10-downloads/?refresh=xmas
And here is the forum link for further questions
https://forum.xda-developers.com/htc-10/development/rom-21-02-viper10-1-0-0-tweaks-hub-t3379151
Greez