Database Users

[GUIDE] Download ANY firmware customization from Sony & create an FTF with Flashtool

[GUIDE] Download ANY firmware customization from Sony & create an FTF with Flashtool
Part A: changing your customization number to download a different firmware customization (optional)
Requirements:
Rooted Xperia smartphone with locked bootloader:
- For firmware versions 10.1.A.1.350 and 10.1.A.1.434, use goroh_kun root exploit
- For firmware versions 10.1.1.A.253, 10.1.1.A.307 and 10.3.A.0.423, use perf_event root exploit and remount-reboot fix
Build Prop Editor
The customization number of the firmware you want to download (see list, only customizations for the same phone model)
Start BuildProp Editor.
When a Superuser request pops up, tap 'Grant' or 'Allow'.
{
"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"
}
At the first start, a backup of 'build.prop' will be created automatically, which can be restored in case of any problems.
Scroll down to 'ro.semc.version.cust' and tap it.
Change the value to the customization number of the firmware you want to download.
When asked to reboot, tap 'No'.
Tap 'ro.semc.version.cus_revision' and change the value to 'R1A'.
When asked to reboot, tap 'Yes'.
Part B: downloading firmware with Sony PC Companion
Requirements:
Sony PC Companion
Xperia smartphone with locked bootloader
Delete this folder if it already exists:
- Windows XP: C:\Documents and Settings\All Users\Application Data\Sony Mobile\Update Engine\db
- Windows Vista/7/8: C:\ProgramData\Sony Mobile\Update Engine\db
Start Sony PC Companion.
Case A: new software version available
Click 'Update'.
Click 'Accept'.
If you only want to download the firmware without updating, disconnect your phone as soon as the "Downloading software..." screen appears.
If you disconnected your phone, this window will appear, which you may close. Otherwise your phone software will be updated.
Case B: no new software version available
Click 'Your Phone / Tablet is up to date'.
Click 'repair my phone / tablet'.
Click 'Next'.
Repairing your phone will delete your personal data and settings. If you don't want this, see step 6. Click 'Continue'.
Tick the checkbox and click 'Next'.
If you only want to download the firmware without repairing, disconnect your phone as soon as the "Downloading software..." screen appears.
If you disconnected your phone, this window will appear, which you may close. Otherwise your phone software will be repaired and your personal data will be lost.
Part C: creating an FTF file with Flashtool
Requirements:
Flashtool
Firmware files from Sony PC Companion or Sony Update Service (see part B).
Start Flashtool or Flashtool64 (for 64-bit Windows).
Click 'Tools' > 'SEUS Decrypt'.
Select the 'Source Folder' (copy-pasting this path will not work):
- Sony PC Companion (Windows XP): C:\Documents and Settings\All Users\Application Data\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony PC Companion (Windows Vista/7/8): C:\ProgramData\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony Update Service (32-bit Windows): C:\Program Files\Sony Mobile\Update Service\db\13740270\blob_fs
- Sony Update Service (64-bit Windows): C:\Program Files (x86)\Sony Mobile\Update Service\db\13740270\blob_fs
Move all 'Available files' to 'Files to convert' by selecting them and clicking the right arrow button.
Click 'Convert'.
Enter the following details:
- Device: your phone model, e.g. 'C6602', 'C6603', 'C6606' or 'C6616' for Xperia Z (see 'Settings' > 'About phone' > 'Model number').
- Branding: can be found in the first columns of these tables by looking up the customization number, e.g. 'Customized US'.
- Version: the build number of the firmware, e.g. '10.1.1.A.1.307'.
Move all files from 'folder list' to 'Firmware content' except *.ta files (e.g. simlock.ta, preset1.ta, cust-reset.ta, ...) by selecting them and clicking the right arrow button.
Click 'Create'.
When you see 'Bundle creation finished', your FTF will be in 'C:\Flashtool\firmwares'. If your combination of device/branding/build is not yet available on xda-developers forum, please be so kind to share it (see part D).
To save about 2 GB of disk space, delete this folder:
- Sony PC Companion (Windows XP): C:\Documents and Settings\All Users\Application Data\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony PC Companion (Windows Vista/7/8): C:\ProgramData\Sony Mobile\Update Engine\db\13740270\blob_fs
- Sony Update Service (32-bit Windows): C:\Program Files\Sony Mobile\Update Service\db\13740270\blob_fs
- Sony Update Service (64-bit Windows): C:\Program Files (x86)\Sony Mobile\Update Service\db\13740270\blob_fs
Part D: sharing your FTF on xda-developers forum
Upload your FTF to a file host. I use Dev-Host for this purpose, but it only supports files up to 512 MB, so I use WinRAR to pack my FTF with the following options: 'Compression method' = 'store' (since FTF is already compressed), 'Split to volumes, size' = '512 MB'. Of course you can use a different file host and archiver if required. Please note that Google Drive, Dropbox and Box all have bandwidth quotas, so your shared files may be disabled if they are downloaded too much.
Create a new thread on xda-developers forum in 'Xperia Z General' and include at least the following information:
- Device
- Build number
- Android version
- Customization version
- Region
- Branding
- Download links
Here is an example: [STOCK ROM][FTF] Xperia Z (C6603) 10.1.1.A.1.253 Generic BE (Unbranded/Belgium)
If this post was helpful, don't forget to click the 'Thanks' button.

Is a locked bootloader really necessary for step A?

Coirpre said:
Is a locked bootloader really necessary for step A?
Click to expand...
Click to collapse
Not really for part A, but it is required for part B (because Sony Update Service will only work with a locked bootloader) and part A is useless without part B
However, if your bootloader is unlocked, you can use "Flash tool for Xperia™ devices" (Sony Emma).

Apollo89 said:
Not really for part A, but it is required for part B (because Sony Update Service will only work with a locked bootloader) and part A is useless without part B
However, if your bootloader is unlocked, you can use "Flash tool for Xperia™ devices" (Sony Emma).
Click to expand...
Click to collapse
even after restoring a TA-Backup? sorry, I'm still new to the way sony handles this...

Coirpre said:
even after restoring a TA-Backup? sorry, I'm still new to the way sony handles this...
Click to expand...
Click to collapse
After restoring your TA-Backup (or doing a relock with Flashtool) and flashing a stock ROM, you can use Sony Update Service again.

Apollo89 said:
[*]If you just want to download the firmware without flashing it to your phone: watch the download progress very closely. When the end is near, start holding the USB connector. As soon as the download is completed (see screenshot), IMMEDIATELY DISCONNECT YOUR PHONE. Timing is crucial here. If you disconnect it before downloading is finished, the download will stop. If you disconnect it too late, you might lose data. I used this method several times without losing any data. My experience is that the download progress bar suddenly goes to 100%, before you would expect it, so be prepared!
Click to expand...
Click to collapse
Thank you for your guide.
I just want to add that with "PC companion", I disconnected my phone before the end of the downloading and it didn't stop. I make my own .253 FTF without problem.
Somebody could confirm ?

LedFanatic said:
Thank you for your guide.
I just want to add that with "PC companion", I disconnected my phone before the end of the downloading and it didn't stop. I make my own .253 FTF without problem.
Somebody could confirm ?
Click to expand...
Click to collapse
You're right!
When restoring with PC Companion, you can disconnect your phone during the download.
The downloaded files will be in 'C:\ProgramData\Sony Ericsson\Update Engine\db\13740270\blob_fs'.
The only thing I'm not sure of, is if PC Companion also downloads the full image when updating?
I will download my next update with PC Companion. If the files are the same as with Sony Update Service, then I will update this guide.

Apollo89 said:
You're right!
When restoring with PC Companion, you can disconnect your phone during the download.
The downloaded files will be in 'C:\ProgramData\Sony Ericsson\Update Engine\db\13740270\blob_fs'.
The only thing I'm not sure of, is if PC Companion also downloads the full image when updating?
I will download my next update with PC Companion. If the files are the same as with Sony Update Service, then I will update this guide.
Click to expand...
Click to collapse
What I can tell you is that I made my 253.ftf and 253.zip from an updating PC companion process between .434 to .253. But I didn't compare if the files are the same as with SUS. I use flashtool to flash the ftf and TWRP to recovery flash the zip and didn't have problem...
As soon as the .307 will be available here in France, I will try to reproduce the same process and let you know

Changing build.prop not worked for me
Sony update service downloads same customization version - before change file.(phone restarted after change)

relicks said:
Changing build.prop not worked for me
Sony update service downloads same customization version - before change file.(phone restarted after change)
Click to expand...
Click to collapse
Are you sure you changed the right value? There are multiple entries with your customization number in build.prop, but it's (only) this one you should change: 'ro.semc.version.cust='. After changing this value, save and close build.prop and open it again to check if it has been saved correctly. Also, did you delete the folder 'C:\Program Files (x86)\Sony Mobile\Update Service\db' before starting Sony Update Service?

Apollo89 said:
Are you sure you changed the right value? There are multiple entries with your customization number in build.prop, but it's (only) this one you should change: 'ro.semc.version.cust='. After changing this value, save and close build.prop and open it again to check if it has been saved correctly. Also, did you delete the folder 'C:\Program Files (x86)\Sony Mobile\Update Service\db' before starting Sony Update Service?
Click to expand...
Click to collapse
Yes i am sure. "ro.semc.version.cust" was 1270-7689 (generic UK), and i changed it to 1271-5145 (generic Turkey). And i duble check the value after save it, delete db folder.

relicks said:
Yes i am sure. "ro.semc.version.cust" was 1270-7689 (generic UK), and i changed it to 1271-5145 (generic Turkey). And i duble check the value after save it, delete db folder.
Click to expand...
Click to collapse
That's very strange. I successfully downloaded three other customizations by using this method. A guy who PM'd me was also able to change from 'Generic UK' to 'Vodafone UK' by following this guide. Are you sure SUS was downloading 'Generic UK' again?

Apollo89 said:
That's very strange. I successfully downloaded three other customizations by using this method. A guy who PM'd me was also able to change from 'Generic UK' to 'Vodafone UK' by following this guide. Are you sure SUS was downloading 'Generic UK' again?
Click to expand...
Click to collapse
I think you need to change also the id for ro.product.name=
And ro.semc.version.cus_revision=
That what i did to make it work.
Sent from my C6603 using xda premium

gm007 said:
I think you need to change also the id for ro.product.name=
And ro.semc.version.cus_revision=
That what i did to make it work.
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
I didn't have to change those values, but something just came to my mind: I had ro.semc.version.cus_revision=R3A and I downloaded firmwares with R4A, R6A and R11A (all higher).
The guy who changed from 'Generic UK' to 'Vodafone (UK)', changed from R14A to R16A (also higher), but he said he first tried to change to 'Generic ES', which is R5A (lower), and it didn't work.
When I check the latest firmware versions with the URL you can find here (see browser bookmark), I get an empty response if the 'cdfVer=' in the URL is higher than the one of that customization, so I always use cdfVer=R1A there.
This will probably also do the trick here!
@relicks, could you try to change your values to this (without changing anything else):
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R1A
and see if that works? I think it will

Apollo89 said:
I didn't have to change those values, but something just came to my mind: I had ro.semc.version.cus_revision=R3A and I downloaded firmwares with R4A, R6A and R11A (all higher).
The guy who changed from 'Generic UK' to 'Vodafone (UK)', changed from R14A to R16A (also higher), but he said he first tried to change to 'Generic ES', which is R5A (lower), and it didn't work.
When I check the latest firmware versions with the URL you can find here (see browser bookmark), I get an empty response if the 'cdfVer=' in the URL is higher than the one of that customization, so I always use cdfVer=R1A there.
This will probably also do the trick here!
@relicks, could you try to change your values to this (without changing anything else):
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R1A
and see if that works? I think it will
Click to expand...
Click to collapse
nope
It says Your phone has already latest firmware.

relicks said:
nope
It says Your phone has already latest firmware.
Click to expand...
Click to collapse
Does Sony Update Service still offer the option to do a factory reset? I have had this problem where factory reset wasn't even available anymore.
I had to restore the original build.prop from my backup, then I rebooted and SUS gave the factory reset option again.
After that, I modified build.prop again, rebooted and then it worked.
If that still doesn't work, you can try this:
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R7A
Don't forget to do a full reboot each time you change something in build.prop and delete the SUS db folder.

relicks said:
nope
It says Your phone has already latest firmware.
Click to expand...
Click to collapse
Close pc companion and use update service.
Sent from my C6603 using xda premium

Apollo89 said:
Does Sony Update Service still offer the option to do a factory reset? I have had this problem where factory reset wasn't even available anymore.
I had to restore the original build.prop from my backup, then I rebooted and SUS gave the factory reset option again.
After that, I modified build.prop again, rebooted and then it worked.
If that still doesn't work, you can try this:
ro.semc.version.cust=1271-5145
ro.semc.version.cus_revision=R7A
Don't forget to do a full reboot each time you change something in build.prop and delete the SUS db folder.
Click to expand...
Click to collapse
Thanks mate, it is now ok.:good:
But question, it was .434 before after do these things it downloads .253 and i loose root. Is it possible download .434 same customization number for rooting?

relicks said:
Thanks mate, it is now ok.:good:
But question, it was .434 before after do these things it downloads .253 and i loose root. Is it possible download .434 same customization number for rooting?
Click to expand...
Click to collapse
What did the trick? You just tried again with 'R1A'? Or did you use 'R7A'?
No, unfortunately it is not possible to download previous firmware versions from Sony. You can only downgrade if you can find the right FTF file online.

Nice share thanks
Xperia p LT2II
Engima v8.3
sliding xp kernel

[ROM] HUAWEI Ascend W1-U00 | v1.32 | Now available !!

Hi all
I would like to everyone present the first Custom Windows Phone 8 ROM for HUAWEI Ascend W1-U00.
{
"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"
}
Informations
Windows Phone 8.1 GDR1
Build 14219
Dev unlock
Interop unlock
All capabilities
Changed size partitions :
MainOS - 2,1 GB
Data - 1,5 GB
Additional
Can enable mass storage mode
Searching updates PfD
without dev account and app from market.
Available 51 Langs
ar-SA
az-Latn-AZ
be-BY
bg-BG
ca-ES
cs-CZ
da-DK
de-DE
el-GR
en-GB
en-US
es-ES
es-MX
et-EE
fa-IR
fi-FI
fil-PH
fr-CA
fr-FR
he-IL
hi-IN
hr-HR
hu-HU
id-ID
it-IT
ja-JP
kk-KZ
ko-KR
lt-LT
lv-LV
mk-MK
ms-MY
nb-NO
nl-NL
pl-PL
pt-BR
pt-PT
ro-RO
ru-RU
sk-SK
sl-SI
sq-AL
sr-Latn-CS
sv-SE
th-TH
tr-TR
uk-UA
uz-Latn-UZ
vi-VN
zh-CN
zh-TW
How to flash ?
So... The whole update process will proceed in two steps. The first step is flashing the ROM in which certain features are unlocked (required for flashing custo ROM). Performance of the system, its working, etc have not been changed. The second and last step concerns flashing Custom ROM.
! REMEMBER! Everything you do at your own risk.
Step 1 !
a) Download ROM and Flash tool
b) Run "HWDiagnosticApp (##2846579#) ", turn on "Diag settings" and reset phone.
c) Run Flash Tool , select ROM file / Config XML and click "Scan && Download".
d) Now your phone should reset and start in download mode.
If your phone does not want to start the download mode, use QPST​
e) When phone displays 100%, and the inscription OK. The process of flashing rom is complete. Now you need Reset the phone (press power button on 15 sec or remove battery). Flash tool displays information about the bad file FFU, just ignore it .
Step2 !
Before you begin the process of flashing Custom ROM, make sure that you have a ROM with ability to run the device in mass storage mode. If not, flash it. Also remember that after flashing Custom ROM you need perform the first start (until you see the start menu). If you already have ROM with the ability to run in mass storage mode, you can follow the below instructions.
a) Download latest ROM + WP8CRUU, link at the bottom of the page.
b) Run device in mass storage mode
c) Run WP8CRUU.exe and follow the instructions in the program.
!!Attention!!​​​​If you have Custom ROM , you only need start the phone in Mass Storage mode and flash new Custom ROM with WP8CRUU. You do not have flash everything from scratch !!
How to Enable Mass Storage Mode ?
This is very simply, when you start your phone, press "cam" + "vol -" .
Changelog :
v1.32
- Build 14219
- Corrected some regstry entries
- Rebuild firmware packages
- Solved problem with the updates
Now you can update to W10 !
How to do it? Instruction is given below
You need set this values :
[HKEY_LOCAL_MACHINE\SYSTEM\Platform\DeviceTargetingInfo]
"PhoneManufacturer"="NOKIA"
"PhoneManufacturerModelName"="RM-976_1115"
"PhoneFirmwareRevision"="01061.00066.14235.36003"
"PhoneHardwareVariant"="RM-976"
"PhoneMobileOperatorName"="000-GB"
You can use this REG editor (working without CustomWPSystem app)
Important! You need choose "sign in with different account" in Windows Insider otherwise the program will not search for updates !
v1.10
- Fixed a bug with memory card detection
- Fixed bug with incorrect reading of the battery status
Click here to download v1.32
Click here to download v1.10
Click here to download v1.00
Super Big thanks for donations :
€10,00 EUR
$15,00 USD
$16,00 USD
$33,00 USD
$66,00 USD
If you appreciate my work, click it ​

Good work!
May be you should hide langs under a spoiler.

Trying not to get jealous --- Lumia user here

Great work indeed! When you say "mass storage mode" do you literally mean USB mass storage mode (view the phone's storage as a block device)? That would be... very impressive. I'm guessing you need to reboot the phone to enter such a mode though. Alternatively, if you "just" mean Full FS Access via MTP, that's still very cool.
One thought: did you include the Samsung RPC server (so that tools written for interop-unlocked Samsung phones will work)? If not, it may be difficult to port some apps; not all the relevant parts of the registry are writable even with capability unlock (unless you modified the registry ACLs) and I can't find an arbitrary registry write function in the Huawel WINMDs (although there may be one I just didn't see; I did find a read function).

GoodDayToDie said:
Great work indeed! When you say "mess storage mode" do you literally mean USB mass storage mode (view the phone's storage as a block device)? That would be... very impressive. I'm guessing you need to reboot the phone to enter such a mode though. Alternatively, if you "just" mean Full FS Access via MTP, that's still very cool.
One thought: did you include the Samsung RPC server (so that tools written for interop-unlocked Samsung phones will work)? If not, it may be difficult to port some apps; not all the relevant parts of the registry are writable even with capability unlock (unless you modified the registry ACLs) and I can't find an arbitrary registry write function in the Huawel WINMDs (although there may be one I just didn't see; I did find a read function).
Click to expand...
Click to collapse
I saw read/write dword functions somewhere in Huawei apps.

Finally. This literally might be the only way to upgrade the Tracfone version since straight talk has no plans on releasing a update. Been flashing all the foreign GDR2 Huawei W1 ROMS and all work fine but don't allow me to use 3G. Really hope this project takes off and possibly a work around for users with the Tracfone branded version of the phone.

soft of reker work in your rom?
http://forum.xda-developers.com/showthread.php?t=2685826

reksden said:
soft of reker work in your rom?
http://forum.xda-developers.com/showthread.php?t=2685826
Click to expand...
Click to collapse
You can't talk about copyright.

-W_O_L_F- said:
You can't talk about copyright.
Click to expand...
Click to collapse
I'm writting:
reker written this xap and jailbreak. I don't change original files.

GoodDayToDie said:
When you say "mass storage mode" do you literally mean USB mass storage mode (view the phone's storage as a block device)?
Click to expand...
Click to collapse
Yes ... If you can enter to Mass storage mode you need reboot phone and press appropriate buttons
anonymous007 said:
don't allow me to use 3G
Click to expand...
Click to collapse
In my ROM 3G works fine !

WojtasXda said:
Yes ... If you can enter to Mass storage mode you need reboot phone and press appropriate buttons
In my ROM 3G works fine !
Click to expand...
Click to collapse
you should try to сopy reсovery(huawei w1) in htс 8x (rom)/ if you are familiar with the format nbh

reksden said:
you should try to сopy reсovery(huawei w1) in htс 8x (rom)/ if you are familiar with the format nbh
Click to expand...
Click to collapse
Hmmm , you should stop posting **** like that in threads it doesn't belong !!!!!
HARDWARE HARDWARE HARDWARE isn't the same !!!
read this and read it real carefully.
http://forum.xda-developers.com/showpost.php?p=51233276&postcount=5
and ps , nbh is a container , in that container are another few .nb containers , and they are signed !!!

reksden said:
you should try to сopy reсovery(huawei w1) in htс 8x (rom)/ if you are familiar with the format nbh
Click to expand...
Click to collapse
It didn't work without bricking your phone, because HTC has other hardware and other bootloader!
Please stop posting stuff in development thread if you don't know about development!
I'm sure WojtasXda will find a way to do this on all WP8 devices, BUT WAIT!

please can you give us the link off your rom ?

Update... Info in first post !

WojtasXda said:
Update... Info in first post !
Click to expand...
Click to collapse
This is great!!!
Bt is the a possibility to disable 3 collums?

athloni said:
This is great!!!
Bt is the a possibility to disable 3 collums?
Click to expand...
Click to collapse
Yes, you can disable 3 rows with WPH Tweaks by @jessenic: http://forum.xda-developers.com/showthread.php?t=2486387
Sent from my RM-915_nam_usa_228 using Tapatalk

Can I install WP8.1 with the Developer Preview program after using your ROM?

xdevilium said:
Can I install WP8.1 with the Developer Preview program after using your ROM?
Click to expand...
Click to collapse
Developer Preview only check some Registry Keys then apply a key I don't remember
When you have a Interop Unlocked devices you have Developer Unlock too . So there's no problem with using Dev Preview app.
I think next preview will release in 2nd of April , Yes?

ngame said:
Developer Preview only check some Registry Keys then apply a key I don't remember
When you have a Interop Unlocked devices you have Developer Unlock too . So there's no problem with using Dev Preview app.
I think next preview will release in 2nd of April , Yes?
Click to expand...
Click to collapse
yes
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Where can I find "HWDiagnosticApp"?
Also will this work on Windows 8?

DRM keys restored !!!

i have used many custom roms but atlast i came back to stock rom and when i flashed the stock rom, my DRM keys restored itself. i have to do nothing. happpy!!!!

How do you see your drm is restored?
Send with tapatalk pro

jindal_bharat said:
i have used many custom roms but atlast i came back to stock rom and when i flashed the stock rom, my DRM keys restored itself. i have to do nothing. happpy!!!!
Click to expand...
Click to collapse
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!

If you did not backup your ta partition when u first rooted the keys are gone forever.

androidfreak70 said:
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
Click to expand...
Click to collapse
daniel2728255 said:
If you did not backup your ta partition when u first rooted the keys are gone forever.
Click to expand...
Click to collapse
+2
Kinda useles to open a new thread about that in my case !
Send from my XZ With My Own Personal Modified MoonWalker SuperB !

androidfreak70 said:
No
Your DRM keys didn't restored. If bravia engine work so that's not mean the DRM keys are back
Flashtool just restore the TA partition not DRM keys
Tapatalk'ed from my Xperia™ Z (C6602) running Dirty Unicorns ROM!
Click to expand...
Click to collapse
then what r drm keys for ?
as my be2, xloud, trackid, ota updates everything is working .

Check the service menu: dial *#*#7378423#*#* (i.e. *#*#SERVICE#*#*) and choose 'Service tests' > 'Security'. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
DRM keys are unique for each device, so they are not contained in any firmware download. Once they are erased, there is no way to get them back, unless you made a backup of the Trim Area (TA) before unlocking your bootloader.

jindal_bharat said:
then what r drm keys for ?
as my be2, xloud, trackid, ota updates everything is working .
Click to expand...
Click to collapse
DRM keys for warranty only
Those days and other things work when the TA partition restored not DRM keys
Xperia™ Z (C6602) with Tapatalk!

Ok thanks man
Sent from my C6603 using XDA Free mobile app

DRM restored
Mine was also restored.
Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...
I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!
I'm also happy I have my DRM Keys back with the TA Partition working!
Good luck people

mandibox said:
Mine was also restored.
Tho the mess over here, on a Xperia Z2, was absolutely a little mistake that costed the phone's life: I changed dpi setting under /system/build.prop and couldnt get the phone to startup properly (bootloop). So to get it connected to the PC, the only exit was to unlock the bootloader and flash some 3rd party recovery mode. By doing so I knew I was gonna lose DRM keys, TA Partition was gonna be screwed... anyway, I had to do it. So I got into the OS partitions, I copied (too late) the TA Partition that was still there, and I could make a backup of not much things... the recovery did some backup, I'll check later its contents. Very complicated to explain details of what I did, but after it, to get the phone back working, I downloaded a brand new stock firmware, which also restored my TA Partition and my DRM keys somehow...
I made a test. I used a tool (Backup-TA-9.11) that downloaded from the phone the new TA Partition. And then I compared it to the old one (using same tool), and I saw that the old one was totally f***d up!
I'm also happy I have my DRM Keys back with the TA Partition working!
Good luck people
Click to expand...
Click to collapse
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.

xerwudjohn said:
HOW did you do that? are you sure about that? please check your service test/security if both first three lines are Ok.
Click to expand...
Click to collapse
Hello!
Sorry for the late response
I now figured out the DRM Keys are not really restored.
At the time I did not know about them, and lost them by mistake.
But I found another post that kinda helped me getting them back: http://forum.xda-developers.com/crossdevice-dev/sony/xperia-z1-z2-z3-series-devices-drm-t2930672

Apollo89 said:
Check the service menu: dial *#*#7378423#*#* (i.e. *#*#SERVICE#*#*) and choose 'Service tests' > 'Security'. If your DRM keys are okay, both MARLIN and WMLA will show up as [Key OK]. If they are erased, they would show up as [Unknown Error].
DRM keys are unique for each device, so they are not contained in any firmware download. Once they are erased, there is no way to get them back, unless you made a backup of the Trim Area (TA) before unlocking your bootloader.
Click to expand...
Click to collapse
Man I restored them twice and it still gives me the :/
Sent from my C6603 using XDA Free mobile app

One question, is it possible to have your DRM keys intact with a locked bootloader, and be able to access fastboot?
I know for a fact that in Flashtool, it stated that fastboot features were accessible.
So, this whole time I thought that I might have accidentally unlocked my bootloader until I came across this thread.
I remember when I first got the phone, I was unable to access Fastboot mode due to a locked bootloader, but now I am able to.
Code:
20/001/2015 19:01:57 - INFO - Device connected with USB debugging on
20/001/2015 19:01:57 - INFO - Connected device : Sony Xperia Z
20/001/2015 19:01:57 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
20/001/2015 19:01:57 - INFO - Android version : 4.4.2 / kernel version : 3.4.0-perf-g32ce454 / Build number : 10.5.A.0.230
20/001/2015 19:01:57 - INFO - Checking root access
20/001/2015 19:01:58 - INFO - Root Access Allowed
20/002/2015 19:02:27 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
20/002/2015 19:02:28 - INFO - Device will soon enter fastboot mode
20/002/2015 19:02:28 - INFO - Device disconnected
20/002/2015 19:02:41 - INFO - Device connected in fastboot mode
20/002/2015 19:02:45 - INFO - Device Status: FASTBOOT mode
20/002/2015 19:02:47 - INFO - Fetching fastboot version info from connected device
20/002/2015 19:02:47 - INFO - FASTBOOT version info: [ version: 0.5 ]
{
"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"
}
-NEVERMIND, just tried flashing XzKernel-26 by alnikki25k, and it didn't boot.

Personally, I can't understand how other people is possible to bring their DRM keys without having TA-Partition. It's all fictive information and I'm totally sure, that no one have restored DRM keys within new ROM installation. And I can bet 100% that it doesn't matter - is it STOCK or CUSTOM ROM. Your DRM Keys aren't going to be restored within new ROM. It's impossible. The only way to get your DRM keys back is to restore your own TA-Partition (flashing any other person's TA-Partition will definitely brick your device), where DRM keys are located at.
Locking your bootloader doesn't restore your DRM keys. All you can do for now is to temporarily get some functions working only with some MODS, which are located somewhere in XDA.

my drm keys are lost after re locking BL. now i want to unlock it again but it fails every time i enter the unlock code.. is this because of lost drm keys? any assistance please?

[ROOT] Rooting for SGP611 with giefroot (Bootloader Locked)

WARNING: This instruction may brick your device permanently. I am not
responsible for any your loss or damage.
The following is the instruction to get root for SGP611 with giefroot(http://forum.xda-developers.com/crossdevice-dev/sony/giefroot-rooting-tool-cve-2014-4322-t3011598)
Requirement:
Bootloader Locked Z3 Tablet Compact Wi-Fi 16GB (SGP611)
D6603(Generic GLOBAL 23.0.A.2.93) firmware (You can got it from XperiFirm)
Flashtool
Install driver included in Flashtool
Patched version of giefroot_v3 (View attachment giefroot_v3_sgp611_fix1.zip)
Download:
View attachment giefroot_v3_sgp611_fix1.zip
Small Instruction:
1.Backup
2.Flash SGP611 firmware (23.0.1.A.0.167) if other version is installed
3.Flash D6603 system partition (23.0.A.2.93)
4.Enable [USB Debug] and [mock locations] and [Unknown Source] , then run install.bat in (View attachment giefroot_v3_sgp611_fix1.zip)
5.You got root!
6.Backup TA, Back to SGP611 firmware
Instruction:
1. Backup all your data (including application data and internal storage)
2. Get SGP611(23.0.1.A.0.167) firmware
3. Get D6603 firmware(Generic GLOBAL 23.0.A.2.93 ftf) from somewhere
4. If firmware version of your device is not 23.0.1.A.0.167, then flash all
contents of ftf to back to 23.0.1.A.0.167
(Start Flashtool and click "flash device", then choose "Flashmode".
On "Firmware Selector" select SGP611 firmware.
Uncheck APPSLOG, CACHE, DATA in Wipe menu.
Check all checkbox in Exclude menu.
Unckeck KERNEL in Exclude menu.
Then click Flash button.
Shutdown your device and connect USB on holding volume down.
Wait 20minute or more to finish.
)
5. Flash only system partition of D6603 (23.0.A.2.93)
(Open "Firmware Selector" with same instruction above.
select D6603 firmware.
Uncheck APPSLOG, CACHE, DATA in Wipe menu.
Check all checkbox in Exclude menu.
Unckeck SYSTEM in Exclude menu.
Then click Flash button.
And flash with same instruction above.
)
6. Power on your device, then enable [USB Debugging] and [Allow mock
locations] in Developer options. And enable [Unknown sources] in Security
setting.
Added:
Disable [Verify apps over USB] in Developer options, and disable [Verify apps] in Security setting.
Thanks kvi!
7. Install usb driver included in Flashtool
8. Download giefroot_v3_sgp611.zip and extract zip
9. Run install.bat in extracted folder, then wait for about 1minute
10. You got root!
11. Backup TA
12. Restore stock firmware by following insruction of this thread http://forum.xda-developers.com/z3-...-to-rooted-stock-sgp621-firmware-drm-t3015494
(replace SGP621 to SGP611 in the instruction)
Thanks to zxz0O0 for giefroot and some other tools.
zxz0O0 spend so much time to make giefroot work on SGP611 kernel.
Thanks to lowtraxx for root instruction for SGP621.
(http://forum.xda-developers.com/z3-...t/root-root-locked-bootloader-sgp621-t3013534)
Thanks to CubicU07 for instruction to restore stock firmware.
The old version (giefroot_v3_sgp611.zip) does not work.
Please try new version (View attachment giefroot_v3_sgp611_fix1.zip).
I'm sorry.

For me its not working:
Got a Z3TC 16GB WIFI, installed the Z3TC ftf, then flashed the system from the Z3, then used the tool but always get a device not rooted error

moritz31 said:
For me its not working:
Got a Z3TC 16GB WIFI, installed the Z3TC ftf, then flashed the system from the Z3, then used the tool but always get a device not rooted error
Click to expand...
Click to collapse
It may not succeed in one time.
Plaese try again 3 or 4 or more times.
If you still fails, please let's me know results of commands below.
Code:
adb shell cat /data/local/tmp/giefrootlog
adb shell cat /data/getrootlog
adb shell ls -l /data/local/tmp/scsi_wait_scan.ko

rurie said:
It may not succeed in one time.
Plaese try again 3 or 4 or more times.
If you still fails, please let's me know results of commands below.
Code:
adb shell cat /data/local/tmp/giefrootlog
adb shell cat /data/getrootlog
adb shell ls -l /data/local/tmp/scsi_wait_scan.ko
Click to expand...
Click to collapse
hey, i got it the problem seems to be on one site windows10,
on my mac i had to unplug replug the device after reboot before pressing continue

I noticed a mistake.
I fixed and upload again. (giefroot_v3_sgp611_fix1.zip)
Please try new file.
This file fixes both exploit itself and install.sh(for Linux/OS X).

rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!

kvi said:
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
Click to expand...
Click to collapse
Thanks for confirming

kvi said:
rooted OK disabling all options for check/verify apps ! (1 option in security + 1 option in Developer options) , Backup TA OK
TA restored on rooted stock firmware , drm keys OK
Thx!
Click to expand...
Click to collapse
Thank you for reporting and information!
I added your information to the instruction.

FtF global z3 or z3 tablet?
edited:
I was asking if need to build de ftf firmw using z3 as device or z3 tablet, but It works with z3
Works for me, actually running stock android with root and TA partition restored.
THANKS A MIL!

I do not speak English, I use google translator
Do not know which section you mean, 5 or 12. If I did 5 you see in this picture
http: // oi59.tinypic.com / 2my85qc.jpg

Root with the bootloader intact, that is amazing! Will this also work on the WiFi 4G version? That's the one I have and I don't want to mess it up.

Angelusz said:
Root with the bootloader intact, that is amazing! Will this also work on the WiFi 4G version? That's the one I have and I don't want to mess it up.
Click to expand...
Click to collapse
Just scroll one line up in general forum you have the post for the SGP621 (LTE version) here
enjoy!

Oh, I missed that one, thanks!

Does it void warranty? As the DRM keys and still there and how to do you restore the DRM keys

Copy apps in SDcard.
If you already gained root access, can you copy all apps to SDcard? What apps you guys recommend? Thanks in advance.

Does this method erase all data in internal card?

Has anyone got this working with SGP612 yet? (32gb Wifi only version). I have't seen this mentioned anywhere, but it should be similar to SGP611?

I'm a bit confused at step 12 : first thing to do when following CubicU07 instructions is to follow ... lowtraxx instructions...
If we follow CubicU07 thread, we first have to back up TA, but that was step 11 of this current thread. sso I guess we should follow lowtraxx instructions, but this one specifies that it won't work for SGP611, and sends us to this thread. Back to square one, then.
My guess is that we have to follow CubicU07 thread, no matter what he says first (so, I won't follow lowtraxx instructions).
Could you please be more specific for step 12 ? Do we finally have to use Advanced stock kernel, PRFCreator, SonyRICDefeat, ... as described in CubicU07 thread (which also involves unlocking BL) ?
Thank you.

Where can I get the firmware from step 3?

It's written : install XperiFirm and download it with this software.

[Lava Pixel V1][How To]Flash Stock Firmware.

How To Flash Stock Firmware of Lava Pixel V1.
This Method uses Smart Phone Flash Tool (SP Flash Tool), under Download.
This Method is useful If SoftBricked OR May Be HardBricked.
This Method can also be Used to Restore Specific Partition(s).
Like Recovery, Boot, BootLoader, System, ... etc.
At This Post.
Can also be used to Flash Custom Recovery, Like TWRP.
At This Post.
Pros :
1. Does Not Need to be ROOTed.
2. Does Not Need to be Turned ON.
3. Does Not Need to have Battery.
4. Does Not Need to have Memory Card & SIM Cards.
5. Does Not Need to be Cooked in HCL Acid.
Cons :
1. Need to Turn Off & Remove Battery, Memory Card, SIM Cards.
2. You may BootLoop OR SoftBrick OR HardBrick if you did something else.
3. Need to At-Least Thank Me.
This Tutorial is NOOB a.k.a. New-Bee Friendly.
Any NewBee's, Mr. & Mrs. Noob & Alien can find this Tutorial very easy,
As it is in STEP by STEP Procedure with Image's for each STEP.
See Notes Here : (Link)
Note to All :
I (Dark❶) is NOT & will NOT be Responsible for anything happening by following the process in this Thread, IT is Your responsibility & what you DO with it.
If any S**T happens to your Phone & PC, Then I (Dark❶) & Anyone else is NOT Responsible, BUT you are.
.

Reasons for this Tutorial.
Why I Did this Tutorial?
I did this tutorial for New-Bee's like ME.
As I wanted to Restore Stock Firmware after Messing UP.
How I came across this Method?
I had messed up my System partition and then to fix it I had to use SP Flash Tool.
& then I found This Tutorial on AndroidMTK.
For Experts OR Advance Users, I know that you may already know this Methods.
But New-Bee's Like Me are New to this Kind of World & Need Some HELP.
And So, I made this Tutorial as Simple as Possible.
.

Requirements Before Flashing Firmware.
Pre-Request :
1. Need to Download Required Drives from here : (Mediatek_Driver_Auto_Installer_1.1352.00.zip )
Extract it to somewhere you can find it easily.
Run "Mediatek-Drivers-Install.bat" with Administration Rights.
When many Red Box comes while installing "Mediatek USB unsigned driver", Click Install, for all.
2. Need to Download SP Flash Tool from Here : (SP Flash Tool) Use Latest Version.
Extract it to somewhere you can find it & can execution easily.
You just need to execute "flash_tool.exe" to start SP Flash Tool.
3. Need to Download Firmware file.
Download this file :
Stock Marshmallow
for White Variant Here : (Lava_Pixel_V1_S031_20160122)
OR
for GOLD Variant Here : (Lava_Pixel_V1_S110_20160123)
Extract it somewhere you can find it easily.
4. Need to Remove Some Stuff from Phone.
i. First Turn Off the Phone.
ii. Then remove Phone's back cover.
iii. Then remove Phone's Battery.
iv. Then remove Memory Card & all SIM Cards.
v. Then Do Not Throw your Phone out the Window.
5. Connect the Phone to PC.
Use the USB cable to Connect the Phone to PC(DeskTop or LapTop).
.

Steps to Flash Stock Firmware Using SP Flash Tool.
STEP 1 :
Start "flash_tool.exe" to start SP Flash Tool.
{
"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"
}
STEP 2 :
Click on "Download" Tab.
STEP 3 :
Now, to select Scatter file, in "Download" Tab.
Click on "Scatter-loading" Button.
STEP 4 :
In "Open Scatter File", Selection Window, go to the extracted location of "MT6582_Android_scatter.txt".
Then Select "MT6582_Android_scatter.txt"{Marked as 1}.
And then Click on "Open"{Marked as 2}.
STEP 5 :
After Successful completion of "STEP 4", will see the changes marked within Blue Rectangle.
Check that ALL the Check Box are Ticked.
[ Ignore This IF Flashing Stock Firmware ]
For Restoring of Specific Partition(s), (See Note 3 Below)
Go to This Post
& Then Return HERE & Proceed.
STEP 6 :
Now, Select "Download Only" Mode {Marked as 1}. (See Note 4 Below, !!! U R Warned)
Click on "Download" Button {Marked as 2}.
As Soon As, Clicked on "Download" Button, Go To "STEP 7" Immediately.
STEP 7 :
After Successful completion of "STEP 6", Do the Following As Soon As Possible.
First Un-Plug the USB Cable & THEN Re-Plug it Only ONCE, as Shown in below Animation.
Wait for 10 Seconds , IF Nothing happens after 10 sec's, THEN Un-Plug & THEN Re-Plug it again & Wait for 10 Seconds again.
Still after the Second Attempt, Nothing Happens THEN Drives are Not Installed Properly.
STEP 8 :
After Successful completion of "STEP 7", Will See Some Rapid Changes in Progress Bar.
In Below Part of "Smart Phone Flash Tool" Window, will start after "Start" & end before "Stop".
For Animation Above, Read the "Note 2" below.
STEP 9 :
After Successful completion of "STEP 7", And Then "STEP 8".
When Flash Process is Complete, will see Below Success Window.
STEP 10 :
After the Above Success Window, Close All the Windows.
AND
Insert Battery, Along with Required Memory Card, SIM Cards.
And Ofcourse Back Cover.
AND Then
Yea! Sure, Turn On the Phone.
DoNe, EnJoY,
:good:
See Notes Below (Link).
.

Reserved Post 1.
Reserved 1 For Future Use.

Reserved Post 2.
Reserved 2 For Future Use.

How to Restore Specific Partition(s).
Restore 1 :
After "STEP 5" , UnTick all the Box's , Proceed to "Restore 2".
Note that you need to have previously backed up copy of That Partition,
How to Back UP See HERE.
OR If flashing Custom Recovery Need to have that Image of Recovery.
Example : TWRP
Need to Repeat "Restore 2" to "Restore 4" for Different Partition(s).
Below Example is for Restoring Recovery Partition using "StockRecovery.img".
Restore 2 :
After Successful completion of "Restore 1", Then Tick Only the required Partition Box.
Example is taken for "recovery"{Marked as 1}.
Now, Click Anywhere in the Blue Marked Rectangle to "Open File" Window{Marked as 2}.
Restore 3 :
After Successful completion of "Restore 2", Then "Open File" Window will be Displayed.
In "Open File" Window , go to stored Recovery Image.
And Then Select the Stock OR Backed UP Recovery Image File ending ".img"{Marked as 1}.
Then, Click on "Open" Button{Marked as 2}.
Restore 4 :
After Successful completion of "Restore 3", will see the changes marked within Blue Rectangle.
Restore 5 :
After Successful completion of "Restore 4" ,
If Needed, Repeat "Restore 2" to "Restore 4" for Other Partition(s),
Else go to "STEP 6".
.

Reserved Post 3.
Reserved 3 For Future Use

Reserved Post 4.
Reserved 4 For Future Use.

Credit's & Note's :
Credit's :
Thanks To ...
1. MediaTek Inc. for Smart Phone Flash Tool (SP Flash Tool).
2. AndroidMTK.com for providing SP Flash Tool & Mediatek_Driver_Auto_Installer for Download & This Tutorial.
3. FirmwareFile.com for providing Stock Marshmallow for White & GOLD Variant which can be Found Here : (Lava Pixel V1)
4. Person who created the ".gif" file which is used from HERE, Where Few of its Frames are Used & Edited by ME in "STEP 7".
5. All Tool's & Drivers & Other Stuff belong to respective Company & People including Copyrights & Trade Marks.
Note's :
1. I (Dark❶) is NOT & will NOT be Responsible for anything happening by following the process in this Thread, IT is Your responsibility & what you DO with it.
If any S**T happens to your Phone & PC, Then I (Dark❶) & Anyone else is NOT Responsible, BUT you are.
2. In "STEP 8" the ".gif" is Edited , For full Stock Firmware will take lot more time to complete, & Also I have Skiped Some Frames for ".gif" file size.
3. If flashing Stock Firmware then This Post is not Need, If Restoring Any Specific Partition then This Post is a MUST.
4. Select Only "Download Only" Mode If selected Any other mode Can be harmful, AS especially "Format All + Download" Mode ERASE Phone NVRAM which Contains Serial No, IMEI, MAC Address & many more details of Phone. U R Warned.
5. All Images in this Thread belong to me including "*.png" & "*.gif", But anyone can share it with condition that credits are given to ME and a link to this Thread.
.

Reserved Post 5.
Reserved 5 For Future Use.

Reserved Post 6.
Reserved 6 For Future Use.

Note Plz
Now This Thread Is Complete

download links are dead please update download links.

Here's a Candy Lollipop for Informing ME. EnJoY.
akskbn said:
download links are dead please update download links.
Click to expand...
Click to collapse
Turns out that the "firmwarefile.com" removed all the firmware files for this Device and Kept Only this :
http://www.mediafire.com/file/92o5xcu64gu7ta7/Lava_Pixel_V1_S111_20160224.zip
Do not know if it's for which variant , Kindly try and tell me.
I can't verify coz my White Variant latest Build No is : Lava_Pixel_V1_S045_20160106 : The update which came in FEB 17.
I am Guessing that this Might be for both variants with latest Updates. Remember, Do Not Blame Me IF Anything Bad Happens.
By the way , Thanks for notifying me. I appreciate that.
Best Wishes. :good:

frimeware link -- drive showing not found
kindly update link

deepan007 said:
frimeware link -- drive showing not found
kindly update link
Click to expand...
Click to collapse
See this :
Dark❶ said:
Turns out that the "firmwarefile.com" removed all the firmware files for this Device and Kept Only this :
http://www.mediafire.com/file/92o5xcu64gu7ta7/Lava_Pixel_V1_S111_20160224.zip
Do not know if it's for which variant , Kindly try and tell me.
I can't verify coz my White Variant latest Build No is : Lava_Pixel_V1_S045_20160106 : The update which came in FEB 17.
I am Guessing that this Might be for both variants with latest Updates. Remember, Do Not Blame Me IF Anything Bad Happens.
By the way , Thanks for notifying me. I appreciate that.
Best Wishes. :good:
Click to expand...
Click to collapse
the post above your's.

!!! Link's Updated !!!
I Searched the Net and found some Firmware file for this Device, Which I uploaded to my personal DropBox.
I have Updated the Link's in my Thread with my personal DropBox Link's.
Kindly Take the Note. :angel: