[HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs - Droid Eris Android Development

[SIZE=+3]Consolidated HTC RUU, Leak, and OTA Downloads[/SIZE]
[SIZE=+2]Here we have in one place links to (almost) every HTC Eris RUU Installer, OTA, and PB00IMG.ZIP downloads.[/SIZE] (You can also find some archaic stuff at shipped-roms.com)
The Eris is getting long in the tooth - grab copies for your personal archive. Mostly this stuff is useful only if you have needs for older components (bootloaders, radios, etc) or need to assist someone with a Cupcake (1.5) phone.
Note that the "rom.zip" (== PB00IMG.ZIP) files from MR1 and MR2 are made available for folks desiring easy access to Cupcake (1.5) components - e.g. the 1.47.0000 S-ON bootloader.
[SIZE=+1]Last Revised: 2011-03-04 (March 2011 OTA) [/SIZE]
[SIZE=+1]Eris HTC/VZW/Leak Historical Timeline:[/SIZE]
Code:
[B] # Date Remark Software #[/B]
01 2009-11-06 Eris Drop Day [B][COLOR=blue][ 1.12.605.1 ][/COLOR][/B]
02 2009-12-09 1st Eris [B][COLOR=green]OTA[/COLOR][/B] (equiv to MR1 [B][COLOR=orange]RUU[/COLOR][/B]) [B][COLOR=blue][ 1.16.605.1 ][/COLOR][/B]
03 2009-12-10 MR1 [B][COLOR=orange]RUU[/COLOR][/B] Available on PCD [B][COLOR=blue][ 1.16.605.1 ][/COLOR][/B]
04 2010-01-07 MR2 [B][COLOR=orange]RUU[/COLOR][/B] Available on PCD [B][COLOR=blue][ 1.17.605.1 ][/COLOR][/B]
05 2010-01-08 2nd Eris [B][COLOR=green]OTA[/COLOR][/B] (equiv to MR2 [B][COLOR=orange]RUU[/COLOR][/B]) [B][COLOR=blue][ 1.17.605.1 ][/COLOR][/B]
06 2010-03-03 HTC "Leak-V1" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.26.605.2 ][/COLOR][/B]
07 2010-03-14 HTC "Root" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.19.605.1 ][/COLOR][/B]*
08 2010-03-23 HTC "Leak-V2" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.26.605.4 ][/COLOR][/B]
09 2010-04-29 HTC "Leak-V3" [B][COLOR=red]PB00IMG.ZIP[/COLOR][/B] ROM leaked [B][COLOR=blue][ 2.36.605.1 ][/COLOR][/B]
10 2010-05-11 3rd Eris [B][COLOR=green]OTA[/COLOR][/B] (1.5 -> 2.1 upgrade) [B][COLOR=blue][ 2.36.605.1 ][/COLOR][/B]
11 2010-06-05 MR3 [B][COLOR=orange]RUU[/COLOR][/B] leaked [B][COLOR=blue][ 2.36.605.1 ][/COLOR][/B]
12 2010-07-15 4th Eris [B][COLOR=green]OTA[/COLOR][/B] [B][COLOR=blue][ 2.37.605.4 ][/COLOR][/B]
12b 2010-07-?? 4th Eris [B][COLOR=green]OTA[/COLOR][/B] (1.5 -> 2.1 upgrade) [B][COLOR=blue][ 2.37.605.4 ][/COLOR][/B]
13 2011-03-02 5th Eris [B][COLOR=green]OTA[/COLOR][/B] [B][COLOR=blue][ 2.41.605.6 ][/COLOR][/B]
* Note that even though the "Root ROM" was leaked chronologically later, it is a much older version of Android 2.1 than any of the "Leak" ROMs.
[SIZE=+1]2/13/2012 - NOTE: All file have been re-hosted to shipped-roms.com. <<==== Please use this link to find your download. Check the file name carefully, and verify the MD5 signature after you download.[/SIZE]
[SIZE=+3]Software Releases (by version) ==========================[/SIZE]
[ 1.16.605.1 ] a.k.a. "MR1" - (Cupcake/1.5)
RUU: RUU_Desire_C_Verizon_WWE_1.16.605.1.release_signed_with_driver.exe
119,334,520 bytes; MD5 signature: 3bafe8b5231e8a75f32256f2abaacda1
PB00IMG.ZIP: Eris_MR1_v1.16.605.1_PB00IMG.ZIP
102,346,348 bytes; MD5 signature: db04a87fb1084744a1c5d08148ecb631
OTA: not captured (to my knowledge)
[ 1.17.605.1 ] a.k.a. "MR2" - (Cupcake/1.5)
RUU: RUU_Desire_C_Verizon_WWE_1.17.605.1_release_signed_with_driver.exe
119,320,610 bytes; MD5 signature: 8b10da4a49f762584d806ac398368d39
PB00IMG.ZIP: Eris_MR2_v1.17.605.1_PB00IMG.ZIP
102,328,473 bytes; MD5 signature: 9e9ad31f01bbcb05157443287f4f38dd
OTA: see item #05 below in OTA section
[ 2.19.605.1 ] a.k.a. "Root ROM" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_RootROM_v2.19.605.1_PB00IMG.zip
107,427,740 bytes; MD5 signature: 63eacc5ede3b179f95dc22d8ef585f94
OTA: n/a
[ 2.26.605.2 ] a.k.a. "Leak-V1" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_LeakV1_v2.26.605.2_PB00IMG.ZIP
108,854,573 bytes; MD5 signature: bd6b08d32948022c865c79dcc61ae449
OTA: n/a
[ 2.26.605.4 ] a.k.a. "Leak-V2" - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: Eris_LeakV2_v2.26.605.4_PB00IMG.ZIP
108,819,939 bytes; MD5 signature: 6e3a2bb96432276b0af51ba6e7e1820c
OTA: n/a
[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU) - (Eclair/2.1)
RUU: RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
130,323,038 bytes; MD5 signature: 74035b1685b279b1aa4f17fafdbec78b
PB00IMG.ZIP: Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP
109,946,224 bytes; MD5 signature: 1c0b0182356242a9d673a661e7458587
OTA: see item #10 below in OTA section
[ 2.37.605.4 ] "4th OTA" - July 2010 - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: n/a
OTA: see items #12 and #12b below in OTA section
[ 2.41.605.6 ] "5th OTA" - March 2011 - (Eclair/2.1)
RUU: n/a
PB00IMG.ZIP: n/a
OTA: see item #13 below in OTA section
[SIZE=+3]OTAs =====================[/SIZE]
OTA files may be renamed to "update.zip", placed on the SD card root folder, and then applied to phones with older stock software using the recovery boot. Note that all Eris OTAs were NOT FULL UPGRADES, BUT RATHER PATCH UPGRADES - afaik, they will only work correctly when applied to a very specific HTC software version already on the phone; including the "stock" recovery boot** for that software version. They will not work correctly with Amon_RA or Clockwork recovery.
Note there was a period of time when Google's servers were hosting two separate "July 2010 (2.37.605.4)" OTA upgrades: one of them upgraded existing 2.1 handsets @ v2.36.605.1, and the other upgraded existing Cupcake 1.5 handsets @ 1.17.605.1. Please read carefully.
#02 [ Converts 1.??.???.? -> 1.16.605.1 ] - 1st Eris OTA
Not captured
#05 [ Converts 1.16.605.1 -> 1.17.605.1 ] - 2nd Eris OTA
desirec-ota-104882.7b1e5cca.zip
4,820,882 bytes; MD5 signature: f6bd240c726874e3922767979ecc6b32
#10 [ Converts 1.17.605.1 -> 2.36.605.1 ] - 3rd Eris OTA
OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip
81,504,835 bytes ; MD5 signature: 9a3a82e4b5afb4e885b41d28085b9adc
OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip[/URL]
#12 [ Converts 2.36.605.1 -> 2.37.605.4 ] - 4th Eris OTA
OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
13,437,426 bytes; MD5 signature: 6c509776a039149c392940025a13cff9
#12b [ Converts 1.17.605.1 -> 2.37.605.4 ] - (if you were stuck on 1.5, 3rd OTA)
06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip
79,318,831 bytes ; MD5 signature: d480a50f3fc450d7bc13cb277820c688
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
14,011,520 bytes ; MD5 signature: 503008da4ff106e95efb5700382bce49
** In the Cupcake (1.5) releases, you get past the stock recovery splash screen by pressing the Home (softkey) and End button simultaneously; in the Eclair (2.1) releases, get past the stock recovery boot splash screen by pressing Vol-Up and End simultaneously (a 2nd time if you powered up a 1.49.xxxx bootloader phone with the same sequence).
I performed MD5 checksums against all of these, and cross-checked prior references to insure everything is correct; if you find any reproducible discrepancies or MD5 mismatches when downloading please notify me via this thread.
bftb0
Revision History:
2011-01-13 added detail about key sequences for stock recovery menu access
2011-03-04 added March 2011 OTA
2012-02-13 re-hosted all files to shipped-roms.com

reserved for later use (i hope not, though).

This is great, thanks.

Thanks for taking the time to document all of this!

Awesome. I have a friend with a rooted Eris, upgrading to the Moto Droid. I have a HTC Incredible. If the process is similar I should be able to flash "Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP" by renaming it to "PB00IMG.ZIP" through the bootloader right? And then be able to apply the other ota's by naming them "Update.zip" through the stock recovery?
First the "OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip" and then "ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip".
Hopefully I'm on the right track.
I've run RUU's on my Incredible via PB31IMG.zip through hboot, and I assume the process is the same on the Eris.

BrettApple said:
Awesome. I have a friend with a rooted Eris, upgrading to the Moto Droid. I have a HTC Incredible. If the process is similar I should be able to flash "Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP" by renaming it to "PB00IMG.ZIP" through the bootloader right? And then be able to apply the other ota's by naming them "Update.zip" through the stock recovery?
First the "OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip" and then "ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip".
Hopefully I'm on the right track.
I've run RUU's on my Incredible via PB31IMG.zip through hboot, and I assume the process is the same on the Eris.
Click to expand...
Click to collapse
I infer that you are intending to return an Eris to stock condition. If so, the process you describe will work. Also, you could use the FlashBack21_v2 ROM to achieve the same thing in one pass. The primary difference between the two methods is that the former flashes the bootloader, whereas the latter leaves it unmolested.
cheers

Hopefully someone can help - In the wake of MultiUpload's voluntary shutdown, I cannot seem to find the OTA files listed above ANYWHERE. My wife recently bought a used Eris and set it up just the way she likes it, AND THEN we saw that it was still running Android 1.5. I want to get her upgraded without losing her existing configuration so I'm hoping to apply each of the OTAs in order to migrate her to 2.1.
Does anybody know of another location for these OTA downloads, or would be willing to share with me directly? Google, ISOHunt and Usenet have failed me miserably. Thanks.

If its not too late, tied to multiuploads were deposifiles.com , wupload.com and others. Now its shutdown here in the U.S but not intl, so when I went to my multiupload account all these mirrors were showing at the bottom listed. All I did was redirect from original host(MPLD) to depositfls.com, links are different but files are the same.
To do this only the account holder would be able too, I did it for my channel and 100's of files that I had but had to be done 1 after another.
Today I can't even open multiupload from chrome, good thing got it out when we did.
Sent from my PC36100 using xda premium

Yeah, I tried using a non-US VPN tunnel to circumvent any blocks and searched via various non-US search engines, and still no luck.

http://shipped-roms.com/index.php?category=android&model=Desire
Have fun

Those are the RUUs, which would wipe out my wife's configurations. I need the OTAs. Thanks though.

dtrammell said:
Those are the RUUs, which would wipe out my wife's configurations. I need the OTAs. Thanks though.
Click to expand...
Click to collapse
Saw this just now. It's late, and I haven't been keeping up with the whole mega/multi-upload drama.
Who wants to host the files? I'm not too interested in saving a single phone from a wipe and reconfiguration ... but if I thought the files would have a more stable home for a while (something open to the public), that's a different matter.
(Or, suggest an alternative to multiupload/depositfiles/ etc)
Let me know (here) if you can't send a PM.
bftb0

bftb0 said:
Who wants to host the files? I'm not too interested in saving a single phone from a wipe and reconfiguration ... but if I thought the files would have a more stable home for a while (something open to the public), that's a different matter.
Click to expand...
Click to collapse
How big are the files? If less than a gig I'd be willing to host them in my dropbox public folder and provide the direct links here.

dtrammell said:
How big are the files? If less than a gig I'd be willing to host them in my dropbox public folder and provide the direct links here.
Click to expand...
Click to collapse
Just the files listed in the OP are about 1.1 GB.
I have to find something similar for the FlashBack ROMs and a few utilities, so I'm poking around and PM'ing to see if I can find someone willing to host 2 GB of files. (I'd like to put all this re-hosting stuff to bed in one go.) Also, I'm trying submissions to shipped-roms.com - we'll see if that works.
Send me a PM with an e-mail address that can accept 100+ MB files. Also, please state which cupcake version the phone is on - 1.17.605.1? 1.16.605.1? Earlier?
bftb0

@dtrammell
update - have a look again in
http://www.shipped-roms.com/index.php?category=android&model=Desire
IF you are on the 1.17.605.1 release of Cupcake, your upgrade to the last factory release is
first
06cb731fe7f3.OTA_Desire_C_Verizon_WWE_2.37.605.4_1.17.605.1_release.zip
and second
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
(If you are on 1.16.605.1, you need to do this three times, starting first with "desirec-ota-104882.7b1e5cca.zip").
The way this is done is to rename each (in turn) to "update.zip" on the root folder of your SD card**, boot the phone into the factory recovery <2e> menu, and choose the "update.zip" menu item. Note that the key sequences for getting past the (factory) recovery splash screen differ depending on the which version of the recovery is on the phone - read the details in the OP, as you will find this key sequence to change between the first and second application of this method.
** as always, please verify MD5 signatures of the file after it has been transferred to your SD card. scary alien's "AFV" (Android File Verifier) app may be used for this if you like.
bftb0
DISCLAIMER: For anybody else who is reading this, using the stock recovery boot to perform upgrades via the OTA files only works for exact, specific versions of HTC FACTORY ROMs. Do not attempt with custom dev ROMs, or even the wrong initial version of HTC factory ROMs. The OTAs are PATCH KITS which only work on specific factory HTC ROMs - they are not "full ROM" upgrades.

Get a minus.com account. You'll get 50gb free. When you make your account add me and we both get 10gb free.
Sent from my Sabotaged Droid Incredible 2.

bftb0 said:
@dtrammell
update - have a look again in
http://www.shipped-roms.com/index.php?category=android&model=Desire
Click to expand...
Click to collapse
That's awesome, thanks a ton! I'll get downloading right now.

Related

[REF]Google Glass Stock OTA URLs

Introduction:
This is the information thread for all known OTA's for Google Glass
Click to expand...
Click to collapse
File List:
Latest:
XRW85 → XRX13B
See Google Glass # Official ROMs - XDA Wiki for a list of files
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a stock AND unmodified rom
Can I flash this if I'm rooted?
Only if you have not modified any files
Click to expand...
Click to collapse
Credits:
Kroo: XRR02 → XRR35 update
Ytwytw:
XRR02/XRR35 → XRR64B
XRR64B → XRR88
XRR88 → XRS36
aeroevan
XRV15C → XRV16
XRV16 → XRV22
XRV27 → XRV34
XRV39 → XRV49
XRV67 → XRV70D
winner00:
XRV22 → XRV27
XRV34 → XRV39
Psymin: XRV49 → XRV60B
jtxdriggers: XRV60B → XRV67
hedsick
XRV70D → XRV72
XRV72 → XRV87
XRV85B → XRW14B
XRW14B → XRW45C
XRW45C → XRW66
XRW66 → XRW85
XRW85 → XRX13B
Click to expand...
Click to collapse
Changelog:
Oct 24, 2014: Added XRW85 → XRX13B
Sep 29, 2014: Added XRW85
Sep 11, 2014: Added XRW45C → XRW66
Sep 11, 2014: Changed Page Layout to match my other pages
May 8, 2013: Initial Page
Click to expand...
Click to collapse
2char
Interested as well.
Sent from my XT907 using xda premium
Has anyone tested it or reviewed it??
Thanks to Kroo on #googleglass via freenode, we found the update delta for "XE5" (XRR35)
c17357b01ac6.signed-glass_1-665738-from-625737.c17357b0.zip
Going to remake op into list of currently available files officially from goog, in the meanwhile "XE6" is rolling out now/soon
------------------------------------------------------------------------------------------
Rewriting OP, quoting for history
TheManii said:
Though there is no public dump of XRR02 "XE4", XRR35 "XE5" is rolling out.
(Someone did dump and give a copy to android police to look at, but as of this post I'm not aware of anyone releasing one publicly)
If anyone that owns a glass and has time, could you do the following?
Dump XRR02
Find the update url for XRR35
While the former requires a device that hasnt updated, the latter should be able to be performed on any gGlass, regardless of current rom.
----------------------------------------------------------------------------------------------------------------------
I cant tell you how to do the former, if it was a standard android device you would (preferably) root and dump:
The kernel image
Bootloader
Baseband (if it was a phone/had a modem)
/system
1/2/3 need root, 4 does not.
----------------------------------------------------------------------------------------------------------------------
To do the latter:
If you have already updated
Root your device
Make a backup of build.prop
Open up build.prop
edit the following lines:
Code:
ro.build.date.utc=1364970747
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR02/625737:user/release-keys
Check for updates
post/send me your adb logcat
I do not have access to one (or even know anyone that does) so I cant be any more specific then that.
Click to expand...
Click to collapse
"XE7" is rolling out now
"XE8" is rolling out now, need someone with a glass unit to assist in finding the update urls
TheManii said:
"XE8" is rolling out now, need someone with a glass unit to assist in finding the update urls
Click to expand...
Click to collapse
I've got glass and haven't updated to XE8 yet - how can I find the update URL?
Sent from Frost⁴ using XDA Premium
aSquard said:
I've got glass and haven't updated to XE8 yet - how can I find the update URL?
Click to expand...
Click to collapse
It actually doesnt matter what rom you're on specifically.
You'll need to be rooted for the following steps, I would advise caution if you're not rooted and havn't rooted your glass previously.
I don't have a glass and I can't be responsible if it breaks during the rooting process.
If you're on "XE7" already:
If you did not already download the ota (which is hard to estimate since it will download automatically):
run a logcat
wait until it appears in the logcat
---------------------------------------------------------------------------
A more reliable method:
wait for the prompt to update to "XE8"
check /cache, there will be a file, it should be obvious to spot
---------------------------------------------------------------------------
If you're on XE4-6 (or want to also assist in getting the update urls for those)
Make a backup of build.prop if needed
open build.prop
edit the following 2 lines: (the values to change them to is at the end of this post)
ro.build.date.utc=
ro.build.fingerprint=
Reboot
wait for prompt
check /cache for filename
"XE4"
Code:
ro.build.date.utc=1364970747
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR02/625737:user/release-keys
"XE5"
Code:
ro.build.date.utc=1367809146
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR35/665738:user/release-keys
"XE6"
Code:
ro.build.date.utc=1370295186
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR64B/696124:user/release-keys
"XE7"
Code:
ro.build.date.utc=1372372324
ro.build.fingerprint=Google/glass_1/glass-1:4.0.4/XRR88/726688:user/release-keys
XE9 is out now, still would like a volunteer to help find the rest of the glass OTAs
XE10 is out now
TheManii said:
XE10 is out now
Click to expand...
Click to collapse
i tried updating with the X10 image thru the fastboot flash = boot, recovery , system, (and now i get boot loop on the GLASS screen )
Any help of a ADB expert
XE11 is out now
XE12.1 and XE16 are rolling out now,
reminder: still looking for a volunteer with a glass to find the ota urls.
Requirements:
Be on a stock rom
Rooted
Edit: found the urls for XE12 -> 12.1 -> 16, but still many more missing
Mine tried to update but failed at clockwork. I managed to pull the 12.1.zip from cache but it looks like you got that already... can I go from EX12 to 16? or do i have to apply 12.1 first (which I cant seem to install)?
Since there's no direct ota available for 12 -> 16, you'll need to go through 12 -> 12.1 -> 16
I'm not sure how to get it to install. Clockwork gives me a status 7 failure
Did you modify files in /system?
If you did and cant undo the changes, flashing the factory image should make it so you can ota.
Disclaimer: I do not own a glass, but the steps shouldnt be any different from a nexus device.
I did but I also tried flashing the stock images (boot, system, userdata and recovery) but couldn't figure out how to flash it with the stock recovery.
I have my Glass rooted, but I do not know what to use to flash the zip files. Also, if 12.1 isn't rooted yet, how do you install the XE16 update? Thank you.

[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]

[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
NOTE: This thread is the only official source of XperiFirm!
Websites like xperifirm.com and xperifirmtool.com were not authorized to redistribute my software!
XperiFirm...
Allows you to download the current firmware for all Sony Xperia-line smartphones, tablets and accessories released since 2013 (excluding Xperia R1/R1 Plus).
[03/06/2023]: All 2013-2014 devices, as well as Xperia E4g (2015) were officially removed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INSTRUCTIONS & REQUIREMENTS:
Microsoft Windows:
At least .NET Framework 4.6 must be installed due to Sony server's TLS 1.2 security protocol requirement.
Which means:
Windows XP (all)/Vista (incl. SP1): Not supported
Windows Vista SP2: .NET Framework 4.6
Windows 7/8/8.1: .NET Framework 4.8
Windows 10+: Pre-installed
Click to expand...
Click to collapse
Linux:
Prepare Linux for Mono installation:
http://www.mono-project.com/docs/getting-started/install/linux/
Enter the following lines once per computer:
$ sudo apt-get install mono-complete
$ sudo cert-sync /etc/ssl/certs/ca-certificates.crt
$ sudo certmgr -ssl -m https://igoreisberg.com
$ sudo certmgr -ssl -m https://software.sonymobile.com
(Enter Y whenever asked)
Enter the following line to launch XperiFirm:
$ mono XperiFirm-x64.exe
Click to expand...
Click to collapse
Apple OS X (x86_64/amd64 only):
Install Mono for OS X:
http://www.mono-project.com/download/
Enter the following in Terminal:
$ mono XperiFirm-x64.exe
Click to expand...
Click to collapse
FREQUENTLY ASKED QUESTIONS:
Why can't I see the downloaded firmware when I use "Tools -> Bundles -> FILESET Decrypt" in Flashtool?
"FILESET Decrypt" is obsolete because XperiFirm decrypted the firmware for you already. Use "Tools -> Bundles -> Create" instead.
How do I add/remove a device to/from favorites?
Right-click on the device's model name in the devices tree view.
Can I download firmware for devices released before 2013?
Sony Mobile deleted older devices when they migrated to their new API. Moreover, they keep deleting old devices from time to time. There's nothing I can do about it.
Can I download older firmware? / Why there's only one firmware version in the list, while there were multiple before?
I have no control over which firmware show per CDA. Sony Mobile deletes older firmware, and there is no way to download them after that. Try finding your FTF on http://www.xperiablog.net/forum/resources/.
Why is the CDA written on my product's box not included in XperiFirm?
CDA (aka CID and Customization ID) is never written on the box. The number on the box starts with "SI", which stands for "Sales Item" which is the combined identification of the device's model + color + country of origin + stock software customization, while CDA is only the customization ID.
To find out your CDA, open the stock "Phone" app and write *#*#SERVICE#*#* (*#*#7378423#*#*). This will open the Service menu.
Go to "Service info" -> "Software info" -> your CDA is under "Active Customization".
What is R1A/R3B/R3C/etc? Which one is better?
This is the operator-specific revision (officially "CDF Version") of the stock software (officially "Software Version") provided by Sony to the different regions and operators.
You can't compare revisions, each operator makes its own revisions. They are basically the same, just with different operator-specific apps.
How do I create an FTF file? / How do I flash a firmware?
This is outside the scope of this thread. There are a whole bunch of tutorials on the internet and on this forum.
CHANGELOG:
v5.6.5 [December 21, 2021]:
- FIX: Fixed connection error when trying to request a customizations list from Sony's server due to API change.
- MINOR: Model tags (like "dual" and "Wi-Fi") will no longer be included in the full device name, as it's no longer used in official device naming.
- MINOR: The "Wi-Fi" tag is now colored dark-red ("dual" tag is still colored blue). Implementation has been added for additional tags that may appear in the future, with different colors, without having to update the application.
NOTES:
* Due to this API change on Sony's side, XperiFirm 5.6.2 is no longer able to fetch firmware from Sony and is not supported.
v5.6.2 [September 29, 2021]:
- FIX: Fixed inability to download new firmware (i.e. 61.0.A.14.3 for Xperia 1 III) due to missing MD5 checksum information for the firmware files.
NOTES:
* Since the MD5 checksum is missing for these new firmware, integrity verification for them is impossible. However, if any of the files happens to be corrupted, unpacking will most likely fail. This should not be a problem if you're downloading firmware using XperiFirm directly (not manually).
v5.6.1 [April 5, 2021]:
- Sony's server has discontinued support for obsolete security protocols (SSL, TLS 1.0/1.1) and requires TLS 1.2+ support. However, .NET Framework 4.0 only supports SSL and TLS 1.0, thus XperiFirm is now targeting .NET Framework 4.6, which means Windows XP and Vista (incl. SP1) can no longer be supported, and a minimum of Windows Vista SP2 is now required, and .NET Framework 4.6 (or newer) must be installed.
NOTES:
* Due to this change, XperiFirm 5.6.0 may no longer be able to fetch firmware from Sony and is not supported.
v5.6.0 [March 20, 2021]:
- Downloading OTA updates was useless as there is no way to manually flash or extract them, thus the feature was removed.
NOTES:
* Due to domain migration, older versions of XperiFirm are no longer usable or supported.
* Due to removal of OTA updates listing, the "Check All" button is no longer needed and was removed.
v5.5.0 [October 11, 2020]:
- NEW: Code refactored to adapt to new API that doesn't use CDAs and firmware revisions (i.e. R1A), which is used for Xperia 5 II.
- NEW: Available firmware versions are loaded along with the customizations (formerly CDFs) list.
NOTES:
* Due to heavy code optimization, older versions of XperiFirm are no longer usable or supported.
* The "Check All" button is now only used for batch OTA updates listing, whenever "Enable OTA updates" is enabled in Settings.
* Loading OTA updates is not yet supported for devices that use the new API.
v5.4.0 [June 25, 2019]:
- FIX: Fixed unpacking while using Mono for Linux.
v5.3.8 [January 11, 2019]:
- FIX: Fixed "firmware is not available" error for certain firmware that are now hosted on a new Sony server.
v5.3.7 [July 28, 2018]:
- FIX: Workaround for broken version naming for certain Xperia XZ2 firmware.
v5.3.6 [March 2, 2018]:
- FIX: Fixed a reported cosmetic bug.
v5.3.5 [March 1, 2018]:
- FIX: Unpacking is matching that of Flashtool: the "partition.zip" is being extracted and a "partition_delivery.xml" is being properly created.
v5.3.1-v5.3.3 [March 1, 2018]:
- FIX: Bug and regression fixes for 5.3.0.
v5.3.0 [March 1, 2018]:
- NEW: Supports downloading official OTA packages (*.pkg). This can be enabled/disabled through "Settings". Those are single-file packages, thus Resuming is not supported, but you can still download them manually if you have to.
- FIX: A bunch of internal tweaks.
- MINOR: Larger device images.
- MINOR: Instructions for Manual downloading slightly changed: Folders should be named "FILE_<fileid>" instead of just "<fileid>".
v5.2.0 [October 21, 2017]:
- NEW: Manual mode is back, completely reworked for Sony's new API. Just click "Manual" and follow the instructions. No file renaming is required.
v5.1.0 [October 16, 2017]:
- NEW: CDF lists are now loaded directly from Sony servers. Manual updating is no longer needed, except for adding new devices, which is a rare case anyway.
- MINOR: Fixed support for Windows XP, but may be unstable as it uses a normal HTTP connection rather than a secure one.
- MINOR: Settings: "Unpack firmware automatically" checkbox - due to the demand.
v5.0.0 [May 16, 2016]:
- NEW: Download management, including a download queue that's saved on your computer and loaded on launch.
- NEW: Resuming feature, including checksum verification and automatic re-download of incomplete/corrupted chunks. Just click "Start" and the download will attempt to resume (for large firmware, the resuming might take a while).
- MINOR: Better error handling and prevention.
- MINOR: Settings: "Play a sound when a download completes"
- NOTE: "Manual" button and "Unpack automatically" are both obsolete, thus were removed in this version. Firmware will always be unpacked.
v4.9.1 [May 4, 2016]:
- NEW: Added support for Accessories (currently, just SmartWatch 3).
- FIX: Solved the lag cause by the image loading of each device.
- FIX: Some additional internal changes had to be made as part of the incremental transition of Sony's firmware database from the old servers to the new one. Many of the "grayed out" firmware will no longer appear on XperiFirm, as they are no longer available on Sony servers.
- MINOR: Added a "Available Releases" label for those who don't get the hint that they have to select a release version.
v4.9.0 [April 20, 2016]:
- NEW: You can now set a default download folder in XperiFirm's Settings panel.
- FIX: Some internal changes had to be made to support changes made by Sony for old devices: They deleted many of the images, thus I remade all of the device icons manually and stored them on XperiFirm's server. Moreover, resources (icons) are no longer preloaded from Sony servers (nothing left to preload there), thus launching XperiFirm is now faster.
- MINOR: Many old firmware are now being grayed out, which means that they are located on the old (no longer maintained) Sony server. Many of these firmware will warn for missing files as well. There's nothing that can be done about that.
v4.8.2 [January 13, 2016]:
- MINOR: Sony has added Xperia M to the new API. The problem is that Xperia M (C19XX) and Xperia M dual (C20XX) have different IDs, for reasons that aren't relevant to newer devices. However, some minor internal changes had to be made to support that specific case. Same issue applies to Xperia E and Xperia tipo. (Version 4.8.1 will still work normally, except for Xperia M, Xperia E and Xperia tipo which won't get firmware from the new API.)
v4.8.1 [September 29, 2015]:
- FIX: This should solve the occasional "Failed to connect to the server." error appearing randomly when opening XperiFirm.
v4.8.0 [September 26, 2015]:
- ATTENTION: Installation instructions for machines running Linux were updated!
- NEW: Adaptations were made to support another server Sony uses to provide firmware, in order to support new firmware released for several devices (like Xperia Z2, Z3, Z3 Compact, Z3+, Z3v, Z2 Tablet, Z3 Tablet Compact and Z4 Tablet) and support for new devices introduced on this other server exclusively: Xperia Z5, Xperia Z5 Compact, Xperia C5 Ultra and Xperia M5.
Firmware are loaded from both servers whenever it's possible.
To unpack a firmware that was manually downloaded from the new server, see FAQ section above.
Special Thanks: @OtaruM, @russel5 and @Androxyde who provided information using their devices!
v4.7.4 [August 28, 2015]:
- ATTENTION: XperiFirm now targets .NET Framework 4.0! You MUST delete the "XperiFirm.exe.config" file (or else XperiFirm would crash on launch)!
- NEW: Sony has a few corrupted firmware. Now XperiFirm will prevent you from downloading them.
v4.7.3 [June 22, 2015]:
- FIX: Fixed a minor but highly annoying bug that appeared when selecting a device (it selected another device instead). The device list is now focused on program launch again.
v4.7.2 [June 1, 2015]:
- FIX: Finishing touches: UI on Mono was basically fixed, the text is now presented correctly.
- FIX: Fixed an issue with the new code design related to devices which share the same model (C6916). Note: You might need to set some of your Favorites again.
v4.7.1 [May 31, 2015]:
- MINOR: Annoying visual bug fixed. Re-releasing because couldn't find any other problems.
v4.7.0 [May 31, 2015]:
- NEW: XperiFirm has a new look, made especially to be beautiful on Windows 10.
- NEW: "Favorites" were added! Right-click on a model in the devices tree to add to favorites, and right-click on a model in the favorites tree to remove from favorites! [Requested feature]
- FIX: XperiFirm was internally redesigned to fix some issues and add these features. Please report if anything goes wrong with the new code.
- MINOR: XperiFirm is now more specific if the unpacking fails due to long file paths.
v4.6.0 [May 25, 2015]:
- NEW: An image for every device is now displayed below the release list. [Requested feature]
Disclaimer: These images are retrieved directly from Sony Mobile's server and are not stored by me.
- NEW: The CDA lists are cached when loaded, so if you select another variant or device, you can go back to the previous list without having to reload it, thus the latest release versions are saved until you close XperiFirm. [Requested feature]
v4.5.3 [May 8, 2015]:
- NEW: One more step towards Flashtool integration: When the download/unpacking finishes, XperiFirm will create a file named "fwinfo.xml" inside the firmware's folder which has information about that firmware. In the near future, Flashtool will use this file to create an FTF bundle for you without having to press anything.
v4.5.2 [May 6, 2015]:
- NEW: A requested feature: When the whole CDA list has been checked for Latest Release, clicking "Check All" again will clear all "Latest Release" fields and re-check the list.
- FIX: An unexpected and rather embarrassing bug that caused a crash when selecting a CDA and then deselecting it by clicking an empty area, and then clicking a release version while no CDA is selected. Now the Release list will be cleared to prevent this.
v4.5.1 [April 29, 2015]:
- ATTENTION: This release is a preparation for better integration with Flashtool, done in co-op with Androxyde.
- MINOR: The CDA sorting by Latest Release behavior was changed: Secondary sorting is by Market instead of CDA. Also, the revision version is ignored in the sorting algorithm because they are not comparable to each other (i.e. R11A in firmware X isn't necessarily newer than R2A in firmware Y).
v4.5.0 [April 12, 2015] RE-RELEASE:
- ATTENTION: You must update to this version, else the device list might not load.
- ATTENTION: This update is the re-release of 4.5 with various critical fixes! XperiFirm moves to X.X.X version format ([Generation].[Major Update].[Minor Update]).
- FIX: The bug that caused "Invalid resource file received!" on some computers was fixed.
- FIX: Several other bug fixes and code improvements.
v4.5 [April 11, 2015]:
- NEW: Proxy settings added! Click the new gear icon next to the "Check All" button.
- NEW: All country flags in the device list are now being loaded from XperiFirm's server, which means if new flags are needed, you won't need to download another version of XperiFirm, it's all being covered server-side!
- NEW: The panels aren't being locked anymore when using the "Check All" button. You can scroll the lists, click on the CDAs as they are being checked and resort the list. This will not interrupt the checking process.
- FIX: Some visual bugs were fixed for even smoother experience!
v4.4 [April 10, 2015]:
- FIX: Fixed a weird bug that caused a delay when opening XperiFirm and "Checking for updates...".
- MINOR: Added a few icons for devices marked as for Brazil. Some of them are both for Brazil & Argentina or Brazil & Chile.
v4.3 [April 8, 2015]:
- NEW: Added support for CDMA devices with no IMEI (but MEID instead). Specifically, Xperia PLAY (R800x) for Verizon which was missing because of that issue.
v4.2 [April 6, 2015]:
- FIX: On some computers, lists might get cached and unable to refresh. In this version, caching is disabled entirely.
v4.1 [April 3, 2015]:
- ATTENTION: XperiFirm's database now uses compression. Any XperiFirm version prior to 4.1 will not be able to load any of the lists!
v4.0 [April 2, 2015]:
- NEW: Java is no longer needed for XperiFirm; Release list loading is now .NET-native. Which also allowed me to implement these features:
* File size was decreased from almost 300KB to just 267KB.
* You can run XperiFirm from any location, from any OS that has .NET Framework 3.5 or higher (Windows), or Mono (Linux/OS X). No more obscure Java errors that prevent XperiFirm from launching or working properly.
* Since there is no JAR file extraction involved anymore, hopefully anti-viruses stop complaining for a false-positive.
* Release list loading is MUCH faster, almost instant, since no more external Java calls are being made.
* When you select a CDA, the loaded release list is saved in memory until you select another device, which saves time and internet traffic if it's re-selected later.
* When you use "Check All", the "Latest Release" versions are being retrieved by the new method (instead of the Sony PC Companion-ish inaccurate method), which is accurate and is exactly the same as the topmost release you get when you select a CDA normally. (No more release versions mismatches and inaccurate versions)
* When you use "Check All", the operation also saves the release list to memory, which will then be re-used if the CDA is being re-selected, instead of loading the release list again and again.
v3.7 [March 25, 2015]:
- NEW: Firmware are being checked for availability on Sony Mobile's server when XperiFirm Downloader window opens. "Download" option will be disabled automatically for unavailable or incomplete firmware.
v3.6a [March 17, 2015]:
- FIX: Fixed a tiny bug that prevented XperiFirm from finding the Java Runtime bundled with Flashtool.
v3.6 [March 12, 2015]:
- ATTENTION: As of this release, "XperiFirm.jar" is being extracted to "%APPDATA%/XperiFirm/XperiFirm.jar" and will not appear alongside "XperiFirm.exe".
- NEW: Mono support for Linux and OS X: Platform-specific methods were replaced with custom methods to support most platforms that have Mono installed.
- NEW: UI Changes: CDA list panel column headers changed (for Mono support), and a new busy/idle status icon.
- FIX: Under-the-hood bug fixes, code improvements and better error handling.
v3.5 [March 5, 2015]:
- ATTENTION: I've decided to drop the alias "IaguCool" and use my name, Igor Eisberg, as the developer from now on.
- NEW: Manual unpacking for download manager support! Supports unpacking FILE_* or *.bin files manually, as long as the firmware is available for download. Includes file checksum verification. Supported formats for "Manual" unpacking (like any other CPU intensive processes - this one also works much faster on an SSD).
- NEW: Error handling was improved! If you don't have Java or if it's corrupted - XperiFirm won't run and an error will be shown.
- MINOR: Minor UI tweaking to look beautiful on Windows 8+, as a preparation for Windows 10.
- MINOR: A few under-the-hood bug fixes.
v3.1 [November 8, 2014]:
- CRITICAL: Fixed a critical bug that caused high CPU usage. Performance now improved drastically.
v3.0b [November 7, 2014]:
- MINOR: Fixed some annoying visual glitches.
v3.0a [November 7, 2014]:
- FIX: Fixed a crash caused by some missing files on Sony servers that messed up with column ordering by Latest Release. (this happens when Sony just begins to roll an update, it's a big mess of missing files, you'll just need to wait patiently until Sony finishes uploading their updates).
v3.0 [November 7, 2014]:
- ATTENTION: XperiFirm now targets .NET Framework 3.5 or later to enable some of the newer features!
- NEW: Total UI re-make. More information about each device (like project/code name). Easier to navigate than ever before.
- NEW: XperiFirm.jar is being self-extracted when you launch XperiFirm.exe. It is being always validated to be the correct file and recreated if it was modified or damaged.
- NEW: Smart downloading: Dummy files are not downloaded. Each file gets a name by analyzing data received from Sony.
- NEW: Smart auto-decryption ability, that uses online data to correctly unpack the firmware and prepare it for FTF creating in Flashtool.
- NEW: Smart sorting for both "Market" and "Operator", for finding your firmware easily.
- NEW: Smart release version checking: Only empty "Latest Release" fields will be checked when using "Check All".
- NEW: Smarter error handling.
- NEW: Added support for multiple simultaneous downloads.
- NEW: Added the ability to copy the raw download links of a firmware to the clipboard. Use however you want and at your own risk!
- NEW: Each and every device is being recognized exactly as marketed by Sony all around the UI, including devices that are merely variants of the same device.
- NEW: The download folder will always have a unique name (adding "(#)" instead of overwriting).
- NEW: The date of the latest update to the device list or any of the CDF lists will be displayed below the device list.
- NEW: A cool sound will notify you when a firmware finishes downloading and/or unpacking.
- FIX: Fixed a bug that broke the scrollbars of the CDF list when minimizing the window.
- DONATE: A nice looking donation button was added, please use it to support me!
v2.5 [August 16, 2014]:
- FIX: Fixed a critical bug which prevented getting releases of old phone models (caused by inconsistencies of Sony Mobile's data)
- FIX: A fixed "XperiFirm.exe.config" included, thanks to aphanic.
- NEW: A new info was added to XperiFirm Downloader - the "Network" name. Useless for most users, but provides general idea about the intended networks the firmware supports.
v2.4 [August 12, 2014]:
- FIX: Fixed the support for firmware of the same version but different revisions.
v2.3a [August 11, 2014]:
- MINOR: Added the firmware revision to the firmware's folder created by XperiFirm when starting a download.
v2.3 [August 11, 2014]:
- NEW: Automatic check for the latest XperiFirm version. If it finds a new version, it offers you to open this thread.
- NEW: Firmware revision was added to the release version (Screenshots updated)
- MINOR: When you sort the CDAs by "Latest Release", after running "Check All", the CDAs are automatically resorted.
v2.2c [August 10, 2014]:
- FIXED: The transfer speed indicator was fixed.
v2.2b [August 10, 2014]:
- FIXED: The transfer speed indicator update rate was changed from extremely fast to once per second, in order to lighten up on CPU and RAM usage, especially on older computers.
- MINOR: "XperiFirm.exe.config" is now packed with XperiFirm, you can chose not to extract it with the JAR and EXE if you don't use Windows 8.
v2.2a [August 9, 2014]:
- FIXED: A minor bug was fixed, that made XperiFirm crash when Downloader is closed while downloading a firmware.
v2.2 [August 9, 2014]:
- NEW: The XF Downloader's code was rewritten to increase speed + Transfer rate indicator added & estimated remaining time.
- MINOR: XperiFirm window is now resizeable/maximizable, by users' request.
v2.1 [August 5, 2014]:
- MINOR: Just a tiny cosmetic fix of the panels, just because I'm such a perfectionist.
v2.0 [August 3, 2014]:
- FIXED: XperiFirm will now use Java 64-bit in Windows 64-bit.
- NEW: Quickly check the latest firmware versions available for all CDAs of a specific device by pressing "Check All".
- NEW: You can use the Java Runtime Environment bundled with Flashtool, by copying XperiFirm.exe & XperiFirm.jar to Flashtool's folder.
v1.0 [July 31, 2014]:
- Download firmware for all Sony/Sony-Ericsson Android-based devices.
EVOLUTION OF XPERIFIRM:
Congratulations. This could be very nice indeed.
FTF File
Download FTF file?
Nice work can certainly be very useful...
Nice...very nice.
I would really like tp see something like that for Android but this is awesome...
Sent from my D6503 using Tapatalk
Great work:good:
hussein1 said:
Download FTF file?
Click to expand...
Click to collapse
Nope, it downloads the official FILE_* files that Flashtool can decrypt and bundle to FTF. It's a better alternative to using PC Companion since you can choose which firmware you want without the need to change build.prop.
How can we use this FILE' formats?
Mazellat said:
How can we use this FILE' formats?
Click to expand...
Click to collapse
Easy ;
open flash tool
go to tools>bundles>FILESET decrypt
choose to open the folder with the downloaded files and just follow the instructions to create your ftf
Very nice, but you need 32 bit Java even if you have 64bit Windows.
Working fine in Windows 8. Thanks :good::good:
Very nice application.. Waiting for this type of app from long time.. I was using the same kind of app in nokia phones.. This is the first for Android..
Really appreciate this..
Sent from my C5502 using XDA Free mobile app
hey bro ..
I am getting error as " Root Element is missing " when clicked on any Firmware Version .
Can you help me to solve this.
soorajskn said:
hey bro ..
I am getting error as " Root Element is missing " when clicked on any Firmware Version .
Can you help me to solve this.
Click to expand...
Click to collapse
Read the requirements.
You need Java Runtime Environment. Install both 32-bit and 64-bit (if you have Windows 64-bit).
Very good App! congratulations!
Thanks to all of you, I'm glad you find it useful
Thanks!! DOWNLOADING NEW FRIMWARE XSP 12.1.A.1.207 France for testing
crazy man!! u did a wonderful work!!
@IaguCool, thanks for your hard work, your program works like a charm, but i have a question
In some model phone we are can download a last firmware and older firmware. For my Z1C i can download only last firmware.. Can we donwload a older for Z1C?
Thanks
russel5 said:
@IaguCool, thanks for your hard work, your program works like a charm, but i have a question
In some model phone we are can download a last firmware and older firmware. For my Z1C i can download only last firmware.. Can we donwload a older for Z1C?
Thanks
Click to expand...
Click to collapse
This was actually possible until not long ago, but recently Sony Mobile deleted all old firmware files, so even if I add the download data, the files are not there anymore. We'll have to manage with what Sony provides and always keep a backup of our favorite firmwares each update. If there is an older version in the list, that means Sony Mobile still keeps the firmware files, but they will be deleted eventually too. XperiFirm shows you only what there is on Sony Mobile servers.

OTA XT1064 US AWS 22.21.25.en.us

I am on the latest 4.4.4 firmware, Blur_Version.22.11.6.titan_retuaws.retuaws.en.US., and would like to download the OTA to post here. I'm rooted, and looked in my cache folder and I do not see any downloaded files.
Am i doing this correctly? I know I need to return to stock to flash, but would like to post the OTA here first.
Please advise!
I am set up to pull logcats through ADB. I assume to pull the OTA link I can restore to stock, start a logcat, and then start the upgrade process. This will give me the URL for the OTA I think. Let me know.
I received this logcat from the device.
Code:
I/OtaApp ( 5598): [info] > DownloadActivity, handling (Blur_Version.22.21.25.titan_retuaws.retuaws.en.US) from ( upgrade)
D/Checkin ( 5598): publish the event [tag = MOT_OTA event name = LOG]
D/OtaApp ( 5598): [debug] > cancelling the previous pending intent set for download later
I/OtaApp ( 5598): [info] > next automatic download prompt (serverAnnoy) is scheduled in : 240 mins.
Disregard, OTA successfully captured. Will post in DEV section.
Thanks.
Do you have a screen shot of your android build number I think you labeled it wrong in the dev section. This looks like the long awaited 21.11.23 lollipop ota
Here is OP's thread with the download link: http://forum.xda-developers.com/mot...a-blurversion-21-11-23-titanretuaws-t2982339/
I have successfully applied this update. :good:

[ROM] Droid Mini/Maxx/Ultra L!te FW 4-21 ML

All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name ROM Droid Mini/Maxx/Ultra L!te FW 4-21 ML
Tagline Faster Lighter Economical
SYSTEM Firmware SU4-21 Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- tzdata 2015e
- icudt51l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps VZW & MOTO
- replaced by sound WirelessChargingStarted
- old gapps for long work phone
- uppdate apps Chrome, LatinIME, Skip, TouchLess, MotCamera, MotGallery, Migrate
- tetering work
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/Droid
for Loked Device
Install for QDLoad9008
Root, Xposed, BusyBox is PreInstalled
- Root SuperSU v2.46
- XPosed 2.6.1
- BusyBox v30
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_4_4_4_VZW_SU6-7_BL_V30.BA_Stock.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_Part1.bat. Parts XX of system.
*** You can also run a file if you are sure that your phone can work 4-5 hours with the screen RUN_Rus_VZW_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_Part**.bat. Parts XX of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
installed application Xposed 2.6.1
Xposed launched clicked install, reboot your phone
I see that the application is launched is set app_process 58 (pre-installed in the system) and XPosedBridge.jar 54 version (made with the application)
then uploaded GravityBox [KK], a check mark, the next reboot, and everything works
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Droid/4.4.4 SU4-21
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Droid Mini/Maxx/Ultra L!te FW 4-21 ML, ROM for the Motorola Droid Ultra
Contributors
CrashXXL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Android 4.4.4 SU6-7 (Flash on RSDLite)
Version Information
Status: Stable
Current Stable Version: 1.02
Stable Release Date: 2015-09-01
Current Beta Version: 0.01
Beta Release Date: 2015-08-15
Created 2015-10-08
Last Updated 2015-10-08
Reserved
Reserved
Update Available
Log
- Launcher with a mesh 4 * 5 with no search string
- Smart Action Moto return ... The assistant working all options
for blocked Patch_SmartAction_Launcher.4x5.NoBar.rar https://yadi.sk/d/kxbxpTnziSg35/Droid
for unlocked MotLauncher.4x5.NoBar.zip https://yadi.sk/d/jp8ykQqFindY8/Droid and SmartActions.zip https://yadi.sk/d/jp8ykQqFindY8/SmartActions
Reserved
I'm a bit confused here. A few months ago I used your set of steps to upgrade to SU6-7 with permanent root (even though I still have locked bootloader). Does this new set of steps allow downgrading to SU4-21 and then the ability to use Sunshine to unlock bootloader? Thanks!
Can I do Write Protection with this ROM?
OscarBrito16 said:
Can I do Write Protection with this ROM?
Click to expand...
Click to collapse
Write protection is still enabled so the root is limited as far as what you can do with it.
classic757 said:
Write protection is still enabled so the root is limited as far as what you can do with it.
Click to expand...
Click to collapse
I mean to install a custom recovery or flash a custom rom!
No, you would not be able to install a custom recovery with method. Unless you have su4-21 or lower your bootloader is locked and at this time there isn't a method to unlock it.
Also you can't downgrade to an older su version, once you have su5-24 or above the qfuse is blown.
As said above you can achieve root, but since the system is still write protected root access is limited. The other option is to perm root your device, and try safestrap, I hope I'm allowed to post that in the thread, sorry if I'm not.
Sent from my XT1080 using XDA mobile app
OscarBrito16 said:
I mean to install a custom recovery or flash a custom rom!
Click to expand...
Click to collapse
Without write protection disabled you cannot install custom recovery or flash custom roms.
Also, if you are on 4.4.4 there is no full root available at this time.
any chance to implement/add Czech language on this ROM?
dcoaster said:
I'm a bit confused here. A few months ago I used your set of steps to upgrade to SU6-7 with permanent root (even though I still have locked bootloader). Does this new set of steps allow downgrading to SU4-21 and then the ability to use Sunshine to unlock bootloader? Thanks!
Click to expand...
Click to collapse
I have the same concerns. Are we supposed to downgrade to the SU4-21???Will this grant us the ability to use Sunshine and unlock our bootloaders?? I thought it wasn't possible to downgrade??? Please I'm lost here I want to do this but I'm am unsure of the outcome?
You can add any language, but it takes a lot of time.
can you tell me how to do it?
- unpack apk
- transtale xml value-en to value-cz
- pack
- install on update from twrp
- check work
@CrashXXL
how can I add the gesture of jedi to my phone? what files do I need to take from your rom?
I do not want to take the whole rom, would be great if i could only take a few files and push the diff to my phone
Can i use this to flash it right over my rooted SU6-7 (rooted with your method months ago, Crash) or do i need to re-flash original stock (without root)?
will my phone be still rooted if i factory reset it..?
I guess this contains only Russian and/or English language, am i right?
Einheit-101 said:
I guess this contains only Russian and/or English language, am i right?
Click to expand...
Click to collapse
no, localization saved and added 2 more Russian and Ukrainian
Yeah, so no German

[ROM] Moto X L!te FW 4.4.4 KXA21.12-L1.26.EU.ML

All developments are carried out thanks to donations on Purchase of these or other devices
thank
Please do not copy files to other file shares
the project is under constant development and refinement
Project name ROM Moto X L!te FW KXA21.12-L1.26.EU.ML
Tagline Faster Lighter Economical
SYSTEM Firmware KXA21.12-L1.26.EU.ML Multilingual
- firmware Deodex - allowing resources using modifiers such GravityBox apply all when firmware odex, it sometimes limited customization or going awry
- tzdata 2015f
- icudt51l last
- return "the gesture of the Jedi" (after installing the firmware of the old sensor /*** it does not threaten the phone)
- delete more apps MotoServices, Google Drive & Docs, Permissions and etc
- replaced by sound WirelessChargingStarted
- old gapps for long work phone
- uppdate apps Chrome, LatinIME, Skip, TouchLess, MotCamera, MotGallery, Migrate
- tetering work
- removed a lot of the background services collect and send data on the type of phone DropBox, MotoCare, MotoConntect, Drive, FaceLock ... etc.
- added Russian, Ukrainian language
for Unloked Device
Install for Custom Recovery
Root not PreInstalled
Download there https://yadi.sk/d/jp8ykQqFindY8/MotoX/4.4.4
for Loked Device
Install for QDLoad9008
Root, Xposed, BusyBox is PreInstalled
- Root SuperSU v2.46
- XPosed 2.6.1
- BusyBox v30
DISCLAIMER
Author is not responsible for totally bricked devices, broken arms, legs, plane crashes and your wife's cheating.
All actions taken is your own risk.
Instructions to install
You:
- shouldn't be afraid of Qualcomm HS-USB QDLoader 9008;
- do not change any files, pathes;
- can install drivers manually;
- need to install python-2.7.9 and pyserial-2.7.win32;
- unzipp _Rus_4_4_4_KXA21_12-L1_26_BL_V30.B7.rar to Cython27;
Method is dangerous, however gives results.
you must have firmware SU6-7 receiving is not in the form of an update (OTA) and stitched through the RSD Lite.
00 Flash *******_4.4.4-KXA21.12-L1.26_CFC_1FF.xml firmware
01 Unzipp everything to Cython27.
02 Run BLBROKE.bat.
03 After you got Qualcomm HS-USB QDLoader 9008, install drivers manually
04 Run RUN_Rus_***_Part**.bat. Parts XX of system.
*** You can also run a file if you are sure that your phone can work 4-5 hours with the screen RUN_Rus_***_Full.bat
then repeat this step X times (the number of times equal to 6)
while (found next part) do
***
>> fastboot to hold 10 minutes that would have been charged a little phone
>> Run BLBROKE.bat.
>> Run RUN_Rus_***_Part**.bat. Parts XX of system.
***
end
99 Turn device on. Now you have SU DEODEX PreRooted
installed application Xposed 2.6.1
Xposed launched clicked install, reboot your phone
I see that the application is launched is set app_process 58 (pre-installed in the system) and XPosedBridge.jar 54 version (made with the application)
then uploaded GravityBox [KK], a check mark, the next reboot, and everything works
Drivers, Soft there -> https://yadi.sk/d/p458Cy0XineRC
Scripts, ROM there -> https://yadi.sk/d/kxbxpTnziSg35/Moto X/4.4.4
Please do not copy files to other file shares
the project is under constant development and refinement
XDA:DevDB Information
[ROM] Moto X L!te FW KXA21.12-L1.26.EU.ML, ROM for the Moto X
Contributors
CrashXXL
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Android 4.4.4 KXA21.12-L1.26
Version Information
Status: Stable
Current Stable Version: 1.00
Stable Release Date: 2015-10-14
Current Beta Version: 0.01
Beta Release Date: 2015-10-04
Created 2015-10-10
Last Updated 2015-10-15
Hi, im on 4.4.3.... I have root and bootloader unlocked. What i need to install?
Just download and install by twrp? Or i need do something before?
Hi, I'm on Moto X ATT 5.1 with locked bootloader. Can I downgrade to this rom?
which file should i download KXA21.12-L1.26.EU.ML-Post-Release.zip or KXA21.12-L1.26.EU.ML.zip ???

Categories

Resources