Hi all,
There is a tool to unpack the original Sony System Software Update Packages (Sony .pkg firmware file) to the separate files? I want to try to build a new custom ROM. This TV is build in 2015 and for some time, like all big companies, are stopping supporting old devices.
I also had a problem with the original motherboard where the flash memory has a damaged file system and after OS is booting after 20-30 seconds it reboots. I brough a new motherboard from eBay, but I'm interesed to try to reflash the old MB flash memory. Also there is a risk that flash memory could be damage, but at least I can change the chip and give a try with a new pre-installed firmware.
But to flash the new firmware I need an image which is unpacket and unencrypted, if is the case.
Thanks.
Related
Hello, friends,
I use the custom rom 23566 with driver version 3.003c, can I flash back to the official rom 21883 with driver version 2.003?
I am worrying whether I will brick my S200...
Please give me some advice, and I will appreciate your help very much!
you should be ok. (i have not try to downgrade my rom, so flash at your own risk!)
make sure you have over 50% battery before you flash.
netnerd said:
you should be ok. (i have not try to downgrade my rom, so flash at your own risk!)
make sure you have over 50% battery before you flash.
Click to expand...
Click to collapse
Thnk you for answering.
I want know whether someone had tried it.
I feel that the new roms exhaust battery very fast, I would like to try some old roms and old drivers. My rom language is simple Chinese, there is no official roms with 3.003c for simple Chinese. I did not think the drivers work well...
no u cant. once you upgrade to official latest ROM. old official ROM can not be revert back. because the official ROM can detect version. once it found your ROM is the latest. it does not allow you to flash back to previous official version.
u can flash it to other cooked ROM and then only flash back to the previous Official ROM.
i tried it.
fulat said:
no u cant. once you upgrade to official latest ROM. old official ROM can not be revert back. because the official ROM can detect version. once it found your ROM is the latest. it does not allow you to flash back to previous official version.
u can flash it to other cooked ROM and then only flash back to the previous Official ROM.
i tried it.
Click to expand...
Click to collapse
That is wrong! Download Acer Original Firmware version 2.0, extract it with ToolsByANPER to get flash.bin and extrom.bin.
Download one of Custom ROMs, i doesn´t matter which one (my Modular ROM or Arto´s Clean ROM). Extract the zip file.
Now copy in the original Acer flash.bin and extrom.bin into the extracted Custom ROM folder and overwrite the existing files.
Start the flash procedure with ACER_EUU.exe and follow the instructions.
Why do people state something and not search little bit more?
brainmaster said:
That is wrong! Download Acer Original Firmware version 2.0, extract it with ToolsByANPER to get flash.bin and extrom.bin.
Download one of Custom ROMs, i doesn´t matter which one (my Modular ROM or Arto´s Clean ROM). Extract the zip file.
Now copy in the original Acer flash.bin and extrom.bin into the extracted Custom ROM folder and overwrite the existing files.
Start the flash procedure with ACER_EUU.exe and follow the instructions.
Why do people state something and not search little bit more?
Click to expand...
Click to collapse
Thank you very much, guy. I think I have got answer from you. I think you mean that the driver information on the first screen is included in the flash.bin, do you?
As I know, the .amf file can be extracted to about 8 files, including .mbn and .bin files. And we can only flash any of them at one time( but the partition.mbn always must be flashed at the same time), a Chinese friend had tried and got these conclusion. I wrongly thought that the driver information on the first screen is included in one of the .mbn file. So I just thought that these "bios" files(.mbn files) are different in different rom version. I will check that whether they are the same.
sinocreate said:
Thank you very much, guy. I think I have got answer from you. I think you mean that the driver information on the first screen is included in the flash.bin, do you?
As I know, the .amf file can be extracted to about 8 files, including .mbn and .bin files. And we can only flash any of them at one time( but the partition.mbn always must be flashed at the same time), a Chinese friend had tried and got these conclusion. I wrongly thought that the driver information on the first screen is included in one of the .mbn file. So I just thought that these "bios" files(.mbn files) are different in different rom version. I will check that whether they are the same.
Click to expand...
Click to collapse
You can also just extract the original acer 2.0 ROM and put the cracked ACER_EUU.exe from Custom ROM folder into original Acer 2.0 ROM folder and start the flash procedure.
That is gonna give you also the 2.0 Radio and bootloader.
If you do as i first said - then you will get 2.0 firmware but with 3.0 Radio and bootloader - (3.0 Radio is better because Acer thit some fixes on the GPS, anyway newest Radio is always better).
EDIT: The information on the bootscreen is about Radio and Bootloader, not about drivers - drivers are integrated into flash.bin.
I have checked that, for official 3.003b/c, the only one file different is appsboot.mbn .
Of cause, image.bin and extrom.bin are different between different languages. It's obvious.
The "partial update method" seems valuable for other system part (such as RADIO) keep the same.
Moreover, for the recent patch, Patch_Acer_1.0_WM65_GPS signal , the major change is amss.mbn .
For ENPRG8650.hex and NPRG8650.hex, these two files could be checking mbn files are correct.
RUU stands for ROM Update Utility. This is a utility that is run via a .exe file that is used to flash a stock ROM, stock radio, stock splash screen, stock recovery, and stock firmware of a device. The utility performs a cleaning of the NAND memory of the device before flashing the included stock software. So a RUU is often suggested as a way fix common problems and to unroot a device. The utility also runs a set of checks on a the
a device before flashing such as CID (Carrier Identification), battery level check, and firmware version check.
A custom RUU is does the same as a RUU but it has been modified to not run the CID check and sometimes other security checks. You can flash custom ROMs, different radio versions, splash screens, and firmwares. You can even use a custom RUU to flash each of these individually
A .apk file, or Application Package File, is the type of file used to distribute and install Android applications files in the Android OS. These files are in zip file format and contain all needed files, scripts, resources, and etc. that the application needs to function.
If your XT1068 is the later version (came from factory with 5.0.2 -it has toshiba front cam) Kitkat will work BUT you will LOSE use of front cam as kitkat has no drivers for this
4.4.4 KITKAT XT1068 Easy Installer
Simple quick Installer of firmware via fastboot
the 4.4.4 Retaildsdsall (GLOBAL) firmware
YES IT CONVERTS UK (GB) PHONES
this is STOCK firmware with no mods,
So Will receive ALL Future OTA updates
and installs over ANY version of 4.4.4 /5.0.x / Custom Rom
(does not check - just flashes regardless of version)
by Auto Restore Script
Requires Windows 7/8/10 to run script
WARNING READ THIS!
MAKE A FULL BACKUP OF PHONE
via play and TWRP or your favorite method. DO NOT SAVE TO PHONE save to pc and a flash drive
(2 copies - cover yourself)
Try to have Battery over 70% charged - 50% OK under 30% DANGER
This flashes back STOCK UNTOUCHED files inc, GPT, modem, boot, recovery, bootloader, system etc etc (basically only your external SD card is left alone!!)
CLEAN FLASH ONLY, so do a
Full factory Reset / wipe required before installation
from phone backup & reset in settings
YOU can HANG / KILL your phone if IGNORED
-- USE @ OWN RISK --
DOWNLOAD
Kitkat 4.4.4
.14 .23 .27 versions (global) + UK (GB) .23 + DE (German) .14
stock firmware + installer AIO
+ INSTRUCTIONS
Download and save to PC / laptop / desktop - DO NOT save the Download to phone or SD Card
A) Firmware KXB21.85.14 (earliest version) https://mega.co.nz/#!mo8wnRJI!APkjY2f_bk-HB2JFBCoWh5rmPvltqCzgTQjQf1t-MHQ
B) Firmware KXB21.85.23 (DSDS ALL) https://mega.co.nz/#!Kkc31L4A!JLtksSioP_xnOZ6m3CR570o9Dxm7LbPgEF2gnkDF_TI
C) Firmware KXB21.85.27 (latest version) https://mega.co.nz/#!CltVzboY!etSjBHqKdMrQTYsh1LcsdMj9S3McG7gkfXRMI7WYPJQ
D) Firmware KXB21.85.23 - GB Region (UK) https://mega.nz/#!yotQhYjK!w0FcxKw1s6w4Ro125mwAvxcoPywnVso8Fa5BihW2Z3k
E) Firmware KXB21.85.14 - DE Region (Germany) https://mega.co.nz/#!T10zkTrR!yBTSeScMh2FLbi9GXjf34VRIBHtBsZoKv_XYqdBj9yU
.
.
V 1.0 Retired
V2.0
Simplified Install method, zip now includes instructions, drivers and all required ADB files
no longer needs USB debugging as done via AP Fastboot flash mode
FAQ's
Q1): What exactly is this?
STOCK motorola firmware files, with a added auto restore script, Adb and fastboot, to allow a easy installation.
Q2): What model phone does this work for?
XT1068 , Various Retaildsds firmware, confirmed working on UK (GB), Indian and EU phones NOT for Brazilian XT1068
Q3): What version is this ?
4.4.4 KITKAT version .14 .23 .27 and UK (GB) .23
Q4): Why Must I factory reset /wipe phone?
Simply because your phone will Hang if downgrading, be sluggish and other problems..... if you can flash firmware - you can make back up 1st and reload all you apps and data - Do it right 1st time
thanks for this.....i'll try your tools later, now i'm not able to use pc!!!
Will this restore the Indian Version to stock as well?
If so can I use the all earliest firmware that you have provided or should I download one specific to my region?
arjunpaliath said:
Will this restore the Indian Version to stock as well?
If so can I use the all earliest firmware that you have provided or should I download one specific to my region?
Click to expand...
Click to collapse
A and B should work on ANY XT1068 as it's a Retail for ALL Dual sim, (it may or may not have certain languages) but if you can find your original firmware it's a easy job to add the automated script
My fone came with KXB21.85-23 installed. Noticed big battery drain. Should switch to ART instead of Dalvik?
reefuge said:
A and B should work on ANY XT1068 as it's a Retail for ALL Dual sim, (it may or may not have certain languages) but if you can find your original firmware it's a easy job to add the automated script
Click to expand...
Click to collapse
Thank you. Was able to find my original firmware and restore to stock.
Rexton270 said:
My fone came with KXB21.85-23 installed. Noticed big battery drain. Should switch to ART instead of Dalvik?
Click to expand...
Click to collapse
I'm just leaving mine as is till lollipop comes out as OTA for XT1068
Wait, wouldn't the boot loader message modified prevent this roms from getting otas since it's a change to a file system?
Nagass said:
Wait, wouldn't the boot loader message modified prevent this roms from getting otas since it's a change to a file system?
Click to expand...
Click to collapse
I dont think so as you can still download OTA with modified Roms, but you need Stock recovery to install - but if it worries you edit the .bat script to remove the line with logo2.bin in it near end of script.
if we cant OTA install, but have a OTA zip of Lollipop we can modify it and just flash it via mfastboot method anyway
reefuge said:
I dont think so as you can still download OTA with modified Roms, but you need Stock recovery to install - but if it worries you edit the .bat script to remove the line with logo2.bin in it near end of script.
if we cant OTA install, but have a OTA zip of Lollipop we can modify it and just flash it via mfastboot method anyway
Click to expand...
Click to collapse
I don't know, I'm quite new to Motorola phones but I read in this forum more than once that for OTA updates (atleast for the lollipop one) you must have a completely stock rom, even a frozen system app would make the update fail to install.
Nagass said:
I don't know, I'm quite new to Motorola phones but I read in this forum more than once that for OTA updates (atleast for the lollipop one) you must have a completely stock rom, even a frozen system app would make the update fail to install.
Click to expand...
Click to collapse
I have run 4.4.4 versions .14 .23 and .27 on my xt1068 as well as modded xt1064 5.0 and modded xt1069 5.0.1 , so worst case is All I will be able to run is modded roms, but i'm 99.99% sure that if you have the correct OTA for you Android version on phone there will be a way to upgrade.
reefuge said:
I have run 4.4.4 versions .14 .23 and .27 on my xt1068 as well as modded xt1064 5.0 and modded xt1069 5.0.1 , so worst case is All I will be able to run is modded roms, but i'm 99.99% sure that if you have the correct OTA for you Android version on phone there will be a way to upgrade.
Click to expand...
Click to collapse
Well anyway I just saved all of your packages just in case I'll ever need to restore my UK XT1068 back to stock.
I still have bootloader locked and everything as it came out of the box waiting for 5.0 OTA (of course I'll try to get the link and post it on XDA )
Nagass said:
Well anyway I just saved all of your packages just in case I'll ever need to restore my UK XT1068 back to stock.
I still have bootloader locked and everything as it came out of the box waiting for 5.0 OTA (of course I'll try to get the link and post it on XDA )
Click to expand...
Click to collapse
Lol sometimes wished I had waited for OTA 5.0
hi ,
when I tried to return to stock through bat file , when was the time to writing partition , it says <bootloader>Preflash validation failed .
Has anyone idea why?
nitsos said:
hi ,
when I tried to return to stock through bat file , when was the time to writing partition , it says <bootloader>Preflash validation failed .
Has anyone idea why?
Click to expand...
Click to collapse
is your bootloader unlocked? this method requires UNLOCKED bootloader
Yes,I have bootloader already locked
as of 14/01/2015 firmware B is Accepting OTA zip update (copy to internal memory AND SDCARD ) to Lollipop 5.0.2 from india
bro can you please upload Firmware KXB21.85.23 (DSDS ALL) to google drive as some people are not able to access mediafire??!!
I found this guide on how to flash .mbn files on Qualcomm devices like X800,X900 etc... http://mytabletguru.com/how-to-flash-qualcomm-cpu/
The exact cause of hard bricking after flashing a chinese ROM is still unknown but i can assure you they're related to the one or more .mbn files included in those ROMs, unfortunately just taking them out won't make it possible to install the updates.
You'd still need to modify the kernel and boot.img in order to make it boot and still most things wouldn't work(current state of my cm13 rom), we would need to reverse engineer those incompatible files to get everything working or wait for the official update(which will never come). But i'll make a thread about reverse engineering .mbn files later.
Now, consider you have a bricked phone;
Basically here, you'd need an extracted image of the official update for X800 US(like the one included here) which include a lot of .mbn files and modem binaries.
Flash them all with the method above.
Then you should be able to boot into fastboot, after that you can flash recovery and either restore a backup or wipe data/cache to flash a new rom. This way you can keep your external storage(virtual sdcard) which wouldn't be the case with previous methods.
Theoretically it should work, if any of you have a bricked phone, wanna try it out but isn't sure how to do it, just post your question below and i'll try to help as soon as possible
My tablet is lenovo yoga tab 3 plus, YT-X703F.
I rooted my tablet, but I want to install an update. I have downloaded the OTA package, can I update by simply replace files? If it's possible, how to deal with those .p files?
Thank you.
zkn1021 said:
My tablet is lenovo yoga tab 3 plus, YT-X703F.
I rooted my tablet, but I want to install an update. I have downloaded the OTA package, can I update by simply replace files? If it's possible, how to deal with those .p files?
Thank you.
Click to expand...
Click to collapse
No as I told you before, you cannot replace the partition images since the update does not contain full images but only patch files (.p files which contain only differences) and a special update format for the system image. Since you have a modified system image (and boot image) it is likely that when you manually apply the patch you will brick your device!!
But to give you some background, the .p files are applied using the apply_patch recovery function (source code is here), whereas the system image patch is applied using the updater recovery function (source is here)
However, as I said fiddling with this is highly risky and I can only repeat myself that the easiest solution is to approach other Chinese users and ask them to boot TWRP and make backups of system and boot partitions of the version you are running and send them to you so that you can flash them via fastboot or TWRP.
matshias said:
No as I told you before, you cannot replace the partition images since the update does not contain full images but only patch files (.p files which contain only differences) and a special update format for the system image. Since you have a modified system image (and boot image) it is likely that when you manually apply the patch you will brick your device!!
But to give you some background, the .p files are applied using the apply_patch recovery function (source code is here), whereas the system image patch is applied using the updater recovery function (source is here)
However, as I said fiddling with this is highly risky and I can only repeat myself that the easiest solution is to approach other Chinese users and ask them to boot TWRP and make backups of system and boot partitions of the version you are running and send them to you so that you can flash them via fastboot or TWRP.
Click to expand...
Click to collapse
Alright, thank you