I opened up ES File Explorer and found something quite interesting. When I went to look for the firmware updates for my Fire TV device, I noticed two .bin files which are named ROMv2_patch_1_0_hdr.bin and ROMv2_patch_1_1_hdr.bin. I changed these files' .bin to .zip and when I attempted to flash them via recovery, I get a corrupted zip file format after its been flashed. I will provide a link to these two files and hopefully I can investigate the format in the /firmware folder on how rbox makes prerooted Fire TV roms. I'm trying to see how Amazon puts their OTA updates in the /system folder since it's located in that directory. Thank you guys for making these forums as precise as possible! I will get back to you as soon as possible if you guys are interested in seeing how Amazon runs their operating systems!
Related
Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!
Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001
Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?
asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse
I've been scouring the interweb looking for a way to take a stock tar file and convert it to a zip file that will flash with twrp. I know it can be done, but thus far I'm not happy with the processes I've found... how do you guys do it?
The stock TAR files contain partitions in IMG format - an all in one file system, and in this case using EXT4 formatting.
In order to create a ZIP, you need to access the files on the partition, which means finding a way to mount those IMG partitions to copy their contents, or find a piece of software to extract from them w/o mounting. Since they are EXT4, you can probably assume a Windows solution isn't available (EXT4 is Linux). Some utilities may exist to handle EXT4 on Windows, but finding one that knows EXT4 and can extract/mount an IMG file is pretty specific.
EDIT : found a utility for you - http://forum.xda-developers.com/showthread.php?t=2285831
If you can somehow get the files out of the archive, you'll need to find a tutorial on the structure of a flashable ZIP. Generally, its just folders and files but there is also a META-INF folder, scripts to install and set permissions, etc. There are likely threads here on XDA that can detail these steps.
Spitzaf, thanks so much! I was hoping for just such a tool
Hi all,
The usual DISCLAIMER: I am in no way responsible for any and all damage the following does to your phone.
I'm new to this whole flashing ROM business, having started by flashing stock Lollipop upgrade to my LG G3 as I was using it on Ultra Mobile and therefore wasn't getting OTA updates. I've now done the same with my brand new Moto Maxx (US) xt1250, which has the exact same phone as the xt1254 (as I'm sure all of you know but it bears repeating just in case).
I found the easiest way to install all of the upgrades to Lollipop from stock Kitkat was just to download these files:
http://rootjunkysdl.com/files/?dir=Droid Turbo/Firmware
I then extracted them into ADB + Fastboot folder one at a time, going in this order:
VRZ_XT1254_KDF21.128-15_15_CFC.xml.zip
VRZ_XT1254_SU2-12_12_CFC.xml.zip
VRZ_XT1254_SU3TL-38_38_CFC.xml.zip
VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
After copying the first group of files into the ADB/fastboot folder and starting up my phone in bootloader, I'd simply click on the batch file for that group (for example the VRZ_XT1254_KDF21.128-15_15_CFC.bat file) to install the first Rom. Then I'd unzip the files for the second lot xml files, allow it to replace the files that had the same name, and then click on the batch file for that Rom.
However, all this was a bit tedious, and I imagine that some people might like to be able to just go direct to the latest 5.1 OTA of stock verizon without all this copying and pasting. So I renamed the files for the first xml batch with a "1" in front, the second with a "2" and so on, and renamed all the commands in the batch xml files to include these modifications. I then put all of the batch file commands together, but also removed some of the unnecessary commands (like "pause", "%fastboot% oem fb_mode_set" and "%fastboot% oem fb_mode_clear") to give you one single batch file.
IN SUMMARY:
I have at your disposal all of the images with modified names, and a single batch command that'll install the upgrades sequentially, which you can do by simply copying all of these files into adb/fastboot folder and clicking on "VRZallupgrades".
I tested this on my droid, and it works great!
My question is this: Would anyone find this helpful? I'm currently uploading all 8GB of files to mega.nz on ****ty hotel internet, but it should be done by tomorrow morning.
Rhuagh3 said:
Hi all,
The usual DISCLAIMER: I am in no way responsible for any and all damage the following does to your phone.
I'm new to this whole flashing ROM business, having started by flashing stock Lollipop upgrade to my LG G3 as I was using it on Ultra Mobile and therefore wasn't getting OTA updates. I've now done the same with my brand new Moto Maxx (US) xt1250, which has the exact same phone as the xt1254 (as I'm sure all of you know but it bears repeating just in case).
I found the easiest way to install all of the upgrades to Lollipop from stock Kitkat was just to download these files:
http://rootjunkysdl.com/files/?dir=Droid Turbo/Firmware
I then extracted them into ADB + Fastboot folder one at a time, going in this order:
VRZ_XT1254_KDF21.128-15_15_CFC.xml.zip
VRZ_XT1254_SU2-12_12_CFC.xml.zip
VRZ_XT1254_SU3TL-38_38_CFC.xml.zip
VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
After copying the first group of files into the ADB/fastboot folder and starting up my phone in bootloader, I'd simply click on the batch file for that group (for example the VRZ_XT1254_KDF21.128-15_15_CFC.bat file) to install the first Rom. Then I'd unzip the files for the second lot xml files, allow it to replace the files that had the same name, and then click on the batch file for that Rom.
However, all this was a bit tedious, and I imagine that some people might like to be able to just go direct to the latest 5.1 OTA of stock verizon without all this copying and pasting. So I renamed the files for the first xml batch with a "1" in front, the second with a "2" and so on, and renamed all the commands in the batch xml files to include these modifications. I then put all of the batch file commands together, but also removed some of the unnecessary commands (like "pause", "%fastboot% oem fb_mode_set" and "%fastboot% oem fb_mode_clear") to give you one single batch file.
IN SUMMARY:
I have at your disposal all of the images with modified names, and a single batch command that'll install the upgrades sequentially, which you can do by simply copying all of these files into adb/fastboot folder and clicking on "VRZallupgrades".
I tested this on my droid, and it works great!
My question is this: Would anyone find this helpful? I'm currently uploading all 8GB of files to mega.nz on ****ty hotel internet, but it should be done by tomorrow morning.
Click to expand...
Click to collapse
It is not necessary to flash anything other than VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. This file contains the full firmware package and does not need previous updates to build upon.
TheSt33v said:
It is not necessary to flash anything other than VRZ_XT1254_SU4TL-44_44_CFC.xml.zip. This file contains the full firmware package and does not need previous updates to build upon.
Click to expand...
Click to collapse
seriously? Wow. major noob moment. With my Lg G3 it definitely wasn't possible to flash straight to 5.1
Thanks for the heads up
Kinda makes this noob sick. I just got a new Moto G4 X1625 (not Amazon). Next came the steps to unlock the bootloader with Motorola and to install TWRP. Everything had gone so easily by following some how-to steps I jumped to the next step of installing SuperSU without doing a backup – thinking it was simply adding an app. Big mistake! Reboot and now always stuck on the logo boot animation.
Okay, so I found and tried use TWRP to install ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip in an attempt to get back to stock. No luck there since install always aborts with a "Could not find 'META-INF/com/google/android/update-binary' in the zip file."
I checked a couple of other ROMs and that META-INF directory doesn't seem to be included in them either.
What do I need to do just to get back to normal eliminating the effects of that SuperSU install? Help greatly appreciated.
That file you downloaded is not a flashable file.
Instead, read this linky
Thanks for the helpful clue @t0mm13b. I followed the approach at <http://www.stechguide.com/download-stock-firmware-of-moto-g4-and-g4-plus/> and executed the listed commands from my MacOS Terminal. They did the job resulting in a fresh install after bootup.
2-1/2 questions…
1. Are flashable ROM files readily available? The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
2. Is TWRP not useful for these stock ROMs?
The ones I found all seemed missing the META-INF directory. Will they be .img files and not .zip?
Click to expand...
Click to collapse
As a general rule of thumb, read the accompanying text to the link of the download, on a web page where you find one. It will tell you if it's flashable or not.
Factory images, just like what you had to carry out previously, never have, and do not have the `META-INF` directory. They usually contain img files that requires `fastboot flash`.
On the other hand, OTAs and flashable zips will have that in their respective zip file.
Thanks again @t0mm13b for the clarification. I often didn't see info about whether a ROM is flashable in link or web page text, but it may have just been assumed based on being aware of what the zip contains.
First of all, you need to navigate to Total Commander, whichever file explorer that has root functionality and go to the root folder /data/ota_package to get the official stock rom. You also need root permissions to transfer this update file to the download folder so please refer to an Magisk installation page to properly flash in recovery. Push this .bin of the update after it downloads, cut and paste it to the downloads folder, rename the .bin of the .bin update file to .zip (Don't install the update in settings) then reboot into TWRP and flash it. I will provide the stock update image shortly for the latest version which is 6.2.7.1 on the Fire TV Stick 4K. This works on any Fire TV that's unable to update through the main ota page in settings. If you'd rather wait for a prerooted rom, go to @rbox for the latest updates. Thank you, let me know if there's any problems!