I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Teracotta said:
I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Click to expand...
Click to collapse
It depends on the image, boot, recovery, system etc and what you want to do with it?
ashyx said:
It depends on the image, boot, recovery, system etc and what you want to do with it?
Click to expand...
Click to collapse
I figured out the issue.
The earlier firmwares list the files as .img, but they are in fact .img.ext4 files. I renamed them, then converted them to proper .imgs and it worked.
Thanks you for giving a response.
Related
I've compiled and installed a modded kernel. I'm trying to figure out how to load AOSP compiled binaries. I've tried using adb flash_image system /sdcard/system.img, but I get "failed with error: 6." Does anyone know what this means or how to load system.img on a Galaxy Tab from VZW? I'm working on reactivating the phone dialer...
the galaxy tab has nothing like fastboot, so its pretty hard to flash it! but u can try to overwrite a stock factory.rfs with the files from ur system.img and flash via odin!
That sounds like a great idea. However, I'm trying to figure out how to put the vendor specific drivers in the system.img, which is mountable and editable. If I could get my hands on an original stock system.img, that'd be awesome.
Sent from my SCH-I800 using XDA App
As far as I know, the Tab doesn't use mtd file system, so I don't think it uses .img extensions.
Not positive though. Somebody correct me if I'm wrong.
I know for a fact that img files are created as the output of an Android system build. This img can be broken apart with standard Linux tools. I've already done this. I've also mounted factoryfs.rfs to a local directory, which allows me to move apps to and from the file system.
Sent from my SCH-I800 using XDA App
If you have a md5 of it too, you should be able to flash it via an advanced restore in CWM recovery. That is if it is only the data that is flashed to /system. otherwise I would suggest converting it to a .fs or .tar and flash via heimdall or Odin (respectively).
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
Landroid said:
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
Click to expand...
Click to collapse
thanks! this was very easy to use
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
This is the latest firmware (T700XXU1ANF7) as of June 29, 2014 for the Galaxy Tab S 8.4 (Wifi) model (SM-T700).
"No-Wipe" means your app data and storage will all stay 100% in tact. Only system mods, custom kernels, and root will be removed as you are flashing stock firmware.
Please feel free to use as you see fit.
Download: http://www.androidfilehost.com/?fid=23501681358556680
open1your1eyes0 said:
This is the latest firmware (T700XXU1ANF7) as of June 29, 2014 for the Galaxy Tab S 8.4 (Wifi) model.
"No-Wipe" means your app data and storage will all stay 100% in tact. Only system mods, custom kernels, and root will be removed as you are flashing stock firmware.
Please feel free to use as you see fit.
Download: http://www.androidfilehost.com/?fid=23501681358554636
Click to expand...
Click to collapse
No 10.5 love?
mitchellvii said:
No 10.5 love?
Click to expand...
Click to collapse
+1, can't forget us 10.5 owners
mitchellvii said:
No 10.5 love?
Click to expand...
Click to collapse
Stock Firmware SM-T800 (Wi-FI)
Stock Firmware SM-T805 (LTE)
Now all I need is a rom to screw my rig up with so I'll need this
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
u did it on Windows or Linux? cause I want the system file extracted. can u send it to me please?
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
Maybe you could repack it with root files to get root. There is a how to video on you tube. I would do it, but my linux machine is down.
suzook said:
Maybe you could repack it with root files to get root. There is a how to video on you tube. I would do it, but my linux machine is down.
Click to expand...
Click to collapse
Please don't coming from the one that said root is okay from the note 10.1 2014 edition. Root and profit. Sound familiar. You mean root and brick.
mitchellvii said:
No 10.5 love?
Click to expand...
Click to collapse
ewells38 said:
+1, can't forget us 10.5 owners
Click to expand...
Click to collapse
Apologies for the delay folks. It's now uploaded.
http://forum.xda-developers.com/showthread.php?t=2800372
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
well, we need some step by step instruction here
anyone able to extract system files??
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
Chainfire needs recovery.img to make cf autoroot for us. Are u able to extract the recovery.img for the q0.5 as well as 8.4 so I can post it in the cf auto root thread so we can get root?
FYI for those of you who have PMed me I have fixed the corrupt download and updated the OP link.
Zip
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
Can you please zip extracted and provide a link!!
Thanks
No
jazzespresso said:
well, we need some step by step instruction here
anyone able to extract system files??
Click to expand...
Click to collapse
No I am unable to extract and have done many in the past. It appears no one here has been successful either!!!
EMSpilot said:
No I am unable to extract and have done many in the past. It appears no one here has been successful either!!!
Click to expand...
Click to collapse
bare with me on that one since I tried too many different options, following worked for me - required files attached here (I ziped, so hopefully XDA did not blocked it)
This is for Windows PC:
1. Download sgs4ext4fs.exe, and download firmware, unzip firmware up until you see system.img.
2. Open command prompt (on windows, click start, type cmd) where system.img, and type
sgs4ext4fs --trim system.img systemt.img
........ > you will see bunch of ............., but wait until it finishes.
3. Once it finishes it creates systemt.img, get sgs2toext4.jar (save it to the same folder), and open sgs2toext4.jar, and drag and drop newly created systemt.img to the window (sgs2toext4.jar's window), wait until it finishes, when it finishes it will create systemt.ext4.img
4. Now last step, download ext2explore.exe, and open it, and go to file --> open image and pick systemt.ext4.img, it will show the img file there (on both side of window), on the left side, select the systemt.ext4.img (should be showing full path), right click your mouse, and select save to your desktop or any other folder location you pick.
Obviously, next step will be odexing everything:laugh:
Yorgo1982 said:
u did it on Windows or Linux? cause I want the system file extracted. can u send it to me please?
Click to expand...
Click to collapse
Here you go:
System img from Galaxy Tab 10.5
How about a custom recovery .the build your own recovery with stock recovery.IMG leads to a http// 404 error online after it builds it.any of you smarter than me individuals know how to build a custom CWM/TWRP img ?
Nexus 5 via Tapatalk
open1your1eyes0 said:
This is the latest firmware (T700XXU1ANF7) as of June 29, 2014 for the Galaxy Tab S 8.4 (Wifi) model (SM-T700).
"No-Wipe" means your app data and storage will all stay 100% in tact. Only system mods, custom kernels, and root will be removed as you are flashing stock firmware.
Please feel free to use as you see fit.
Download: http://www.androidfilehost.com/?fid=23501681358556680
Click to expand...
Click to collapse
I actually needed this this morning and feel indebted to you cause the online so called Stock Firmwares lead to mad amount of bloat to my computer.
Thank you
restore
jball said:
I actually needed this this morning and feel indebted to you cause the online so called Stock Firmwares lead to mad amount of bloat to my computer.
Thank you
Click to expand...
Click to collapse
Thanks this worked like a charm!!! Great work!!!
I wanted to download the firmware and remove all the bloat stuff from my N9108v.
Downloaded the firmware and it is a zip file. NO worries - unzipped and I don't see any ".tar.md5" files. Just various other files that include "mbn img ext4 bin" files. MNone of these look like working in ODIN. Is there anything I'm doing wrong?
Thanks in advance.
Cheers.
s327374 said:
I wanted to download the firmware and remove all the bloat stuff from my N9108v.
Downloaded the firmware and it is a zip file. NO worries - unzipped and I don't see any ".tar.md5" files. Just various other files that include "mbn img ext4 bin" files. MNone of these look like working in ODIN. Is there anything I'm doing wrong?
Thanks in advance.
Cheers.
Click to expand...
Click to collapse
HI OP - please remove thread - I just used a different extractor - less vigorous I guess. Did the trick and just extracted to the first layer. Ok - didn't remove the bloatware either...
Thanks.
Hey all, long story short I need to find to the Nougat vendor.img. The link to it from the debloated ROM page appears to be down, so if anyone else has a link to the .IMG file that would be helpful. In the WETA ROM thread, the dev said you go extract it from the .zip but I have no idea where it is/how to flash it in fastboot if it's not a .IMG file. Thanks.
Sent from my Nexus 6P using XDA-Developers mobile app
If the file icon looks like a page with a cd/dvd on it, that is an .img file. Or just right click and look at the properties.
Eric214 said:
If the file icon looks like a page with a cd/dvd on it, that is an .img file. Or just right click and look at the properties.
Click to expand...
Click to collapse
In the zip, the vendor file has a .new.dat extension. Would I change that to .img and flash it in fastboot? Or would that be a mistake?
if the dev says the vendor.img file is included it should be in there, your have to dig through the compressed folder to find it, its usually named vendor.img you might have extensions hidden, or if you have a known .img file elsewhere it will likely have the same icon next to it in the file tree.
you can just extract it and rename the file with a straight ".IMG" prefix and flash that from your ADB folder or using your chosen tool
hutzdani said:
if the dev says the vendor.img file is included it should be in there, your have to dig through the compressed folder to find it, its usually named vendor.img you might have extensions hidden, or if you have a known .img file elsewhere it will likely have the same icon next to it in the file tree.
you can just extract it and rename the file with a straight ".IMG" prefix and flash that from your ADB folder or using your chosen tool
Click to expand...
Click to collapse
So that didn't work (phone wouldn't boot past splash screen) but I did flash this .img file https://www.androidfilehost.com/?fid=24651430732236715 and it worked
RollTribe said:
So that didn't work (phone wouldn't boot past splash screen) but I did flash this .img file https://www.androidfilehost.com/?fid=24651430732236715 and it worked
Click to expand...
Click to collapse
What issue were you having that you needed the vendor image, if you mind me asking?
Was your phone stuck in the splash screen loop?
defcondev said:
What issue were you having that you needed the vendor image, if you mind me asking?
Was your phone stuck in the splash screen loop?
Click to expand...
Click to collapse
I had an old version of TWRP (wasn't aware that there was one that worked with Nougat) and needed to flash an old vendor to get it to work, then a newer one to get my phone to boot. I flash the DP5 vendor and the phone booted just fine, but there was a warning message and I figured it would be better to get the updated vendor.