ok, ima try to make this short and sweet. Im attempting to extract the contents of system.img from an official samsung firmware using unyaffs2
this is quite literallly the FIRST time using my android skills since setting up my linux laptop.
ive done the following so far
running ubuntu 10 something
android sdk, eclipse
downloaded two versions of yaffs neither work as i would have expected.
now, trying to extract the system.img from this file (samsung note 3 kitkat official firmware)
https://doc-04-5g-docs.googleusercontent.com/docs/securesc/ha0ro937gcuc7l7deffksulhg5h7mbp1/met8j7ju751f78fpes2risgambd0mblc/1390788000000/16903193897035115666/*/0B84fZ-6xuKyyMmRMTHhjMldINDA?h=16653014193614665626&e=download
im running into this error
image size is not a multiple of 2048 64
it continues to extract the files saying each one has failed and then into the folder i specified there are a couple of files, none of which look recognizable or usable.
what am i doing wrong here?
Related
Hi guys,
I'm at my wit's end with this one.
I have a 1.2GB data.img file created with Clockworkmod Recovery backup. I believe it was one of the older versions, in the 3.x.x.x range. When this was created I had plenty of space available on the SD and the MD5 was created successfully.
I have had no luck restoring this with any version of CWM. Restoring simply results in a system that won't boot; I am presented with either a black screen or a boot-loop. I have since learned that this is because my backup has too many files. Apparently CWM is hard-coded to restore a maximum of 10,000 files and will not restore anything past that point. I found a thread where someone had edited the source code to increase this limit to 50,000, compiled and flashed it, then successfully restored their backup. Aside from the initial editing, I would not know where to start to do this for my phone (SGS2)
Furthermore, I cannot extract the contents with unyaffs.exe for Windows. When I try to do this, it extracts a small portion of files (around 170MB), then exits with the following report :
Code:
read image file
: Bad file descriptor
read image file
: Bad file descriptor
I have since learnt that this is due to NTFS limitations with the length of pathnames. 'No problem' I think, and decide to install Ubuntu 11.10 so that I can use the linux version of unyaffs to extract the full thing without these limitations.
After a bit of messing around, I successfully compile the unyaffs source (I'm no expert in these matters). I then attempt to extract data.img and after a short while processing I get another error! :
Code:
Segmentation fault
Out of interest, I checked how much data had been extracted and got 9,544 items, totalling 204.2 MB. So I'm roughly 1 GB down.
Please help, you might not believe the hours I've spent to get to this stage and I still can't get all of my data back. I need my contacts (Google didn't back them up apparently), messages, app data and anything else I can get my hands on. If there's a better utility I can use for extracting, or perhaps a modified version of CWM I can flash onto my SGS2 so that I can restore the backup properly, I'm all ears.
Look forward to any responses and thanks in advance.
Just to update, I have now tried ext2explore on Windows 7, as well as yaffs2 explorer on Android. Both will open the .img file but display a blank window.
Ive done a backup on my phone and created a flashable zip (update.zip)
Now im playing around with dsixda's kitchen and trying to extract the system.tar, however it fails most likely due to fact the the system.tar is empty
the files in the archive are as follows
Meta-inf -- <folder>
boot.img -- <8192KB>
image-edify -- <1KB>
system.ext4.tar -- <0KB>
system.ext4.tar.a -- <976,563KB>
system.ext4.tar.b -- <68,151KB>
By the looks of things it has split the system.ext4.tar because its over a gig
How can i compile this into one file or one image so that the kitchen can read it, I'm on a windows 7 PC but i can run linux in a vbox if necessary.
Thanks
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
mikep99 said:
Try using the zip file in your input folder.
dsixda's kitchen should be able to extract from it
Click to expand...
Click to collapse
Already tried, it comes back saying its deleting the part a and part b files and then says the system.ext4.tar isnt a valid archive.
Is it a stock rom?
If so, download the firmware from sammobile and put the tar.md5 file into your input folder (after removing the .md5 suffix).
Thats worked for me in the past....
It is stock, but i have removed the bloatware, installed a few mods, i was hoping to use this particular one really as a base. Ive already played around with fully stock and i kind of broke the whole thing
I'm not too sure then unless theres some tool you can find to merge the 3 tar files into 1...
Never had to do it so I'm unable to suggest anything I'm afraid.
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
th3magpi3 said:
Hey guys,
I'm currently in the middle of developing my own ROM for an S802 based TV box (M8). I am close to releasing but I have a few issues, one very much in particular. I am trying to find a script that will extract a .tar file to the /sdcard/ directory on first boot of the ROM but I'm having a hell of a time. I am a reseller of these boxes and I'm trying to get my Kodi userdata to extract into the proper directory, /sdcard/Android/data/, on first boot but nothing I do seems to be working. Currently I'm using a script called installApk.sh. From what I've gathered it works fine for extracting .tar files to non-sdcard directories but when I attempt to point the extract path of the tar to the /sdcard/ directory it fails. I've also tried decompiling the kodi apk, injecting all of my userdata directly into the apk and re-signing but that causes all of the addons to fail. I'm wondering if any of you have run into a similar issue or know a solution to my problem. Any help is appreciated. Thanks.
Mag
Click to expand...
Click to collapse
see Introduction : How to build an Android ROM - XDA-University
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS] by lokeshsaini94
This thread will be moved to Android Q&A, Help & Troubleshooting
I have some problems extracting files from a system.img file in windows
after hours of different tutorials im still stuck at 0 and hope someone got a solution.
almost every post and video i find shows the easy use of sgs2toext4.jar and how it goes from here to the linux reader.
My main problem here is that sgs2toext4jar gives me a system.ext4.img that 0kb.
added a screenshot that show the problem here.
Do you know of a way that works? Im not a pro user, more of a newbie just so its said, but i can read and follow a tutorial if there is one.
this is what ive done so far:
**Ive downloaded a stock rom for my tablet
http://www.galaxyrom.com/2015/11/up...ytab-e9-6-wi-fi-sm-t560-to-android-4-4-4.html
**unpacked the file with 7-zip and from T560XXU0AOK1_T560XEU0AOH1_HOME.tar and have found myself with the the system.img
Installed programs after tutorials
7zip
ext4 unpacker
ex2explorer
linux reader
system.ext4
Cygwin64
Anyone been able to do this?
Been trying for days to extract the kernel from Nougat to use it within Marshmallow in order to downgrade with vibration working on nougats bootloader - but for the life of me i can NOT get windows to actually read these files properly. have all kinds of mounting programs, a java based converter that doesnt actually work (sgs2ext4) i end up with this loop of the same lines, and a 0kb converted file. I can mount the regular img file fine, but it will NOT open without some sort of error. the files themselves are just fine as they will properly flash and run when using odin (when compressed into tar.md5)
Tried wthin twrp hoping the file manager might just let me browse through it since the phone is already linux based and can actually see the information... but no dice there either. It doesnt go into further detail than just showing me that theres an img file present, with options to delete, chmod, etc.
what can i do to dig down to this zimage portion of boot.img that everyone insists the kernel is within? (i say insist cuz i havent actually seen it for myself!)
none of the tutorials ive come across address these specific opening errors - other than that the error is happening because windows cant read it
diskinternals wont work, osfmount will mount but i cant read it .... where on earth are these drivers or programs or whatever i need to actually allow me to browse and explore these files properly? and dare i say, recompress them once ive found what im looking for!
i did also try flashify, thinking run nougat, backup kernel, install marshmallow, restore nougat kernel, but it just leads to freezing on boot logo. I need to get within these img files to actually do what i want to successfully, switching out only that one specific zimage part of the file, leaving the rest intact.
very frustrated here, would very much love some help with this...
Try this, helped so much!
https://forum.xda-developers.com/general/xda-university/unpacking-editing-packing-roms-img-dat-t3350261
Also, If you want to try, here is a link for the tools:https://www.androidfilehost.com/?fid=24459283995310951