anyone have any idea how to install incremental updates manually? i have an ota incremental package, have even dumped the contents and have the .img files inside but not sure what to do with them as they are not full partition images just the increments(i guess just the parts that need to be changed of the actual partitions) is there any way to merge them or how else should they be used? i tried to use payload dumper with --diff but that just keeps giving me an error that boot image type isnt supported so i can get all the other files and no boot image with it. if anyone has any ideas i would greatly appreciate it. i downloaded the oneplus software updater to try the local upgrade/update and it just keeps telling to put it in the root directory and i have put the zip and the extracted contents in every directory i can think of to no avail. oxygen updater also doesnt support this device (yet)
nvm i found the answer thanks to someone on tg..
encrypt the incremental with ofpflasher and update
Related
Does anyone know any way of opening the dell provided .pkg files , not ways how to install them on mobile , but to open them and extract the files included in it , in Windows , Linux or MacOSX?
tnx
I think TheManii knows the exact way but it involves flashing the pkg to your streak and pulling the battery out at the proper time. The extracted files will be in your LOST.DIR directory on your sim card. A pkg is encrypted and it takes flashing the file to decrypt it.
At least it goes something like that anyway.
lordmorphous said:
I think TheManii knows the exact way but it involves flashing the pkg to your streak and pulling the battery out at the proper time. The extracted files will be in your LOST.DIR directory on your sim card. A pkg is encrypted and it takes flashing the file to decrypt it.
At least it goes something like that anyway.
Click to expand...
Click to collapse
Thank you, interesting indeed this encryption , do you have more info about this process ?
http://mirror2.streakdroid.com/manii/<rom version>/update.zip are the decrypted pkgs
The pkgs can only be decrypted by the stock recoveries, noone's bothered reversing them to find the encryption algo.
TheManii said:
http://mirror2.streakdroid.com/manii/<rom version>/update.zip are the decrypted pkgs
The pkgs can only be decrypted by the stock recoveries, noone's bothered reversing them to find the encryption algo.
Click to expand...
Click to collapse
Thank you, are those ALL the files included in the corresponding .pkg?
Which is the right procedure to extract them, during installation or post ?
Any info about the process is very much appreciated as i am willing to try to decipher and recreate a working .pkg
tnx
The update.zips are completely unmodified, only thing that's been done is run though the stock rec to decrypt.
The safe way to decrypt them on your own is to load the wrong stock rec so it will fail at the first step in the update script. (It checks to see that your rec is the right region so it doesnt install a different region rom)
Afterwards a file will be dumped into <sdcard>\lost.dir, it's the decrypted pkg + garbage from the end of the last memory block. The zips themselves are the same size as the pkg.
There's no real point to making your own pkgs as the only thing it'd do is allow you to install it on a stock rec, but knowing how the encryption works is still useful.
This is even more true on the s10 as it uses pkgs, but they're encrypted differently and these steps dont work on it. I've yet to get a dump from those. All I can do is make nvflash dumps immediately after installing.
Hi guys!
I was hoping one of you could help me.
Yesterday i modified a build.prop file on my NextBook EBM8000ND (Next800T) tablet, causing it to get stuck in a bootloop every time it's turned on. I've been searching the Internet all day long but it's hard to find support when you have a device which no one in the world uses . It was rooted but I did a factory reset hoping that it would fix it. It didn't and now it's also unrooted. I tried to make a custom update.zip with the backup of the original build.prop file but the stock recovery simply refuses to load any update file. It always stops at verification. I used 7zip with store option. I tried signing the zip, I even edited the updater script to only print some text on the screen but the recovery still wouldn't load it. I tried to find a way to install CWM using sdcard but with no luck. When i tried to use ADB in recovery the device says: "failed to open driver control: No such file or directory". It might be worth mentioning that I found my device's ROM online with boot.img and recovery.img files and a .tar file which contains the original system folder.
Is there any way to make the stock recovery (since installing CWM or TWRP seems impossible) read my update file? Or is there another way to fix this? I only need to replace that single file.
Hoping to get help soon.
Cheers!
Hi everybody
I own an Xperia Pro MK16i. The phone is still on stock ROM (4.0.2.A.0.58 GB 2.3.4) and the bootloader is still locked. The only thing I did recently is root the phone successfully with eRoot.
Now, the phone still gets the OTA updates, right now it does notify me that the "new" update 4.0.2.A.0.62 (the latest GB release available for my phone) is ready to download. I would like to install this update in order to try it and only after eventually switch for ICS 4.0.4 (4.1.B.0.587 is the latest).
I was wondering myself:
1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?
2) Is there any chance for me to get somewhere the 4.0.2.A.0.62 stock rom with the proper customization number? My phone is unbranded and purchased in Italy where I live, customization version is: 1249-7782_R12D
3) What does this customization mean? Is it about language? About preinstalled apps? Or what? Someone could clear me the whole thing please?
Many thanks
goriath said:
1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?
Click to expand...
Click to collapse
OK, I digged around about this point and just for reference I share what I found.
The main problem with OTA updates is these packages are binary DELTA packages; they are not the full ROM/FW release, but they contain only the differences between the source ROM (the firmware installed in the phone) and the target ROM (the updated firmware you want to install in the phone).
I took a look inside the BIN file with an HEX editor and what I found confirm the dependance between the update and the stock ROM:
<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata version="3.2">
<product>
<manufacturer>SonyEricsson</manufacturer>
<model>MK16i</model>
<hwplatform>MSM7x30/8x55</hwplatform>
</product>
<update>
<generation>
<version>2.0.0.24</version>
<date>2012-02-01T11:01:38+01:00</date>
<rb_version>6.2.29.19</rb_version>
<rb_ua_version>6.2.29.19</rb_ua_version>
</generation>
<source>
<software>
<revision>4.0.2.A.0.58</revision>
</software>
<customization>
<variant>1249-7782</variant>
<revision>R12D</revision>
</customization>
</source>
<target>
<software>
<revision>4.0.2.A.0.62</revision>
</software>
<customization>
<variant>1249-7782</variant>
<revision>R12D</revision>
</customization>
</target>
</update>
</metadata>
This explains why my download_package.bin is large only 7.55MB; it does update (add/replace files to) the actual ROM. And this is the reason why updates through OTA are sequentials; I cannot install latest GB OTA update w/o go through every previous update first.
So this binary package alone is not useful to create a full ROM of any sort, cannot be flashed as is and cannot be extracted/unpacked/decrypted unless to be a developer and doing reverse engineering.
Hi,
I´m getting software install failed! on my Huawei wile doing an OTA ROM update.
It is an intermediate update so update.app does not have system.img, but rather the update.zip has folders with a patch for the /System.
As of that, I wanted to know what's wrong, so, is there any log file created from the update procedure?
G Play Mini - CHC-U01 Update to V100R001C434B120
OTA URL:
http://update.hicloud.com/TDS/data/files/p3/s15/G854/g104/v29161/f1/full/update.zip
Inside update.zip is update.app (and the folders to patch the /system) which in turn compacts another update.app inside.
So, either "open inside" update.app or extract update.app from update.zip, rename that update.app to update.zip and open the last update.zip to get the update.app that can be opened with HuaweiUpdateExtractor to get the *.img files (exept system.img).
Since I can´t adb in recovery I can´t do a logcat.
Can anyone help me debug the OTA update?
Build Number
This is getting more like a diary...
I found the log file in ./splash2/recovery.log
Now, where is the system getting the information of the build number other than from build.prop, because the info on the "about" menu is different form what is in ro.build.display.id or any other variable on the file.
I'll appreciate any help!
I found that the variable is stored in ./cust/hw/eu/prop/local.prop (on my case the path "eu" is because my CustCVersion is European, on Russian should be .../ru/prop/local.prop").
Unfortunately I didn´t know that CWM doesn´t include cust.img on nandroid backups, so i don´t have the original ./cust structure to replace the original settings.
i have update fail with chc-u01 firmware 6.0.
how cani do?
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk