I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?
yo
hi darren.hoo, i faced the same problem as yours and i realised that we should actually boot our tab to the downloading mode before we launch Odin3,pda.Turn on the usb debugging too(i dont know if this is necessary or not).Anyway happy flashing!
*Odin can only read .tar / .md5 extension ,you dont have to extract everything.
Kruel
Hi Darren.hoo,
To read the image files - It depends.
boot.img and recovery.img requires potentially a script to seperate the ramdisk and also the kernel. There are many good article on many wikis that explains which hex point is the seperator between the two.
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
bootloader.bin - you'll need a hexeditor of some sort. This is as is a bin file (data file)
Not sure about the others. (cache - i'd assume you can recreate anyway and the modem i guess is another binary that requires a hexeditor.)
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Hope this helps.
Really great tips!
frankus0512 said:
system.img - I haven't really played with this too much as I don't usually create ROMS or anything - have you tried to mount it normally on a linux system? as if the system.img is just a ISO? (e.g. mount -o loop system.img /mnt). To rebuild this to become "flashable" is a different story (i believe you need the unayffs2 tools).
Click to expand...
Click to collapse
no luck with this:
debian:/home/darren/gtab/rom/EUR/P7500XWKG9# mount -oloop system.img /mnt
mount: you must specify the filesystem type
But from what I've got from searching xda a lot, maybe it's RFS filesystem?
frankus0512 said:
In terms of flashing the IMG - you need to tar up the *.img files, then do something like md5sum -t #name of tar# >> #name of tar#. Basically, it just appends the hash in md5 format to the tar. rename the file to something like *.tar.md5, and use that to flash as PDA.
Click to expand...
Click to collapse
this tip just really solved my problem.
I've got a tar.md5 file with three files in it: boot.img, system.img, recovery.img, but I don't
want to flash recovery.img coz I've already flashed CWM, yesterday I tried delete recovery.img from the tar ball and then flash it, then ODIN tells me that the files is invalid by
md5sum. I didn't know earlier that it records md5 checksum at the end of the tarball file.
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
span_01 said:
It seems the OP got his answer but I'm having problems figuring out what to do.
I also have a system.img that i unzipped from a tar.md5 package by first editing the file extension to only say tar and then untarring it. When I try to mount the system.img with:
sudo mount -o loop system.img /media/systemimg
I get the filesystem type error:
mount: you must specify the filesystem type
Could someone who knows this please comment on how to mount the system.img to gain access to the files so I can explore system, that would be awesome.
Click to expand...
Click to collapse
samsung firmwares should have -t rfs but you have to have a linux kernel on your dev machine that has a rfs modules
http://forum.xda-developers.com/showthread.php?t=1081239
darren.hoo said:
I downloaded roms from samfirmware, after I unrar it, these are the file list
boot.img bootloader.bin cache.img hidden.img modem.bin recovery.img system.img
So How can I extract some files from system.img? I've tried unyaffs, but it segfaulted.
another stupid question is , how I can flash these files using odin? just select *.img in
pda and start?[/QUOTE,
........................................
hello,
you can extract system.img by android kitchen but it is long process to setup kitchen.
you make it .tar file to flash as pda in odin.
if you want to extract system.img, contact me by email, [email protected]
I will tell you .
Click to expand...
Click to collapse
Hi all, I have made been using these tools to modify and customize livesuit images to suit my needs, now I have packed all of them for u to get ur workstations to get ur hands dirty with some ROM editing/making. before u jump right in I must say though allwinner devices are not brickable, but still u may get ur warrenty void,get ur data wiped or miss a trip with ur mama or gf, and for all those reasons Ill not be held liable.
Now, my toolset includes the following - A ROM backup utility that backs up ur BOOT,BOOTLOADER,SYSTEM n RECOVERY, this will be ur starting point if u dont have any stock image.
A blank livesuit image with fake bootloader,boot,system n recovery fex files. which u will have to fill in with ur own stock roms, after u take backup. (if u dont have a stock ROM already.)
Linux tools to help u edit script.bin files and image tools to split boot images, pack or unpack system.fex etc.
The image packing/unpacking program.
#### GUIDE ####
Now we have our tools, get started....
To make stock image :
1. Get ur fimware dumped using the backup tool.
2. On a linux pc use the tools in the tools.tar.gz archive to make the dumped system file into a system.fex file by doing the follwing :
Make a directory called system.
Unpack the whole system.tgz file which u got from the dump tool inside it.
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>] u will get a system.fex file as output.
3. Now copy the boot.img bootloader.img recovery.img (rename the .img extension to .fex) and the system.fex u made inside the blank livesuit image and replace the nessecary files. And also replace files in the _iso folders. here ull hav to add .iso at the for filename. its pretty simple, just see how the blank files are kept.
4. Now u can pack the whole directory using the image_repacker program. Fire up runner.bat and put the directory make_stock.img.dump in it. It will generate a stock image of ur tablet. back it up as it will save u from many blunders in future.
Now if u want to modify any other livesuit image what will u do:
Just unpack the tool using the image_repacker program. run the runner.bat file, put the .img file on it(drag n drop) and use the /skip parameter in the options and let it do its work. u will get lots of files. now in a linux machine u can use the simg2img binary to make the system.fex file to a mountable image by using [simg2img <system.fex system.img>]
now mount it...make a directory called system, type these commands in the shell , [sudo mount -o loop system.img system ] this will mount the system.img inside the folder. now to make life simpler type [sudo nautilus] (on ubuntu) n start the file manager with super user access. n navigate to the system folder. now u can change files,delete unwanted stuff etc. after ur done with it pack the system directory using the make_ext4fs binary,type [ make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex> ] u will get ur system.fex file which u can pack in a livesuit image and flash.
Allwinner tools2.rar
http://www.4shared.com/rar/S3cbf46k/Allwinner_tools2.html
Editing bootloader scripts
Well, we have the freedom to try images of diffrent vendors to see what works and what doesnt, but some times the display resolution makes a problem, and theres alot of associated problems too. heres how u can edit the bootloader scripts.
I personally would say u download magicISO, and open the bootloader.fex with it, n copy the script.bin n script0.bin from ur backed up stock bootloader n then flash.
but otherwise u can do this via adb too.
run adb shell
type mkdir sdcard/bootloader
type mount -t vfat dev/block/nanda mnt/sdcard/bootloader
then goto sdcard/bootloader to see if it has actually mounted or not.
then with adb push script0.bin n script.bin to mnt/sdcard/bootloader.
then in adb shell type umount bootloader n then reboot.
If u want to mannually edit the bin files use the tools inside sunxi-tools-static.tar.bz2. the bin2fex will decode the bin n make a readable fex file which u can edit, and then use the fex2bin to make it back to bin. commands are [ bin2fex script.bin script.fex] and same goes for [ fex2bin script.fex script.bin]
SDcard Problems...
U must backup ur sdcard data... and after u flash a custom image if u dont see ur internal sd mounting the use following commands...
[ busybox mkfs.vfat dev/block/nand(x) ] here the x refers to the last nand partition that u can check by typing [cd dev/block] and then type [ls]
then type [vold] and u will see ur internal sd.
p.s I had uploaded the toolset but i dont seem to understand the upload system of xda, each time i close the window of attachments,my file is gone. so Im uploading it in 4shared. wait...ill link it.
I have no credits except that I collected and archived these tools. All these tools are made by their original programmers who have given us enough freedom to ruin our devices. So the credit goes to them.
Happy Hacking!!!!
cybermate123 said:
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>]
Click to expand...
Click to collapse
Shouldn't it be [make_ext4fs -s -l 500M -a system <filename.fex> {location of the system directory}]?
alright, following all instructions, I got a img made for my current setup, I flashed with LiveSuit to test if the img worked to get back to original...now im stuck at the android loading screen...any ideas?
EDIT: I'll just post details on my thread... http://forum.xda-developers.com/showthread.php?p=42373627
OMG!!! Why??? Im running my stock,its working...
EarthBoundX5 said:
alright, following all instructions, I got a img made for my current setup, I flashed with LiveSuit to test if the img worked to get back to original...now im stuck at the android loading screen...any ideas?
Click to expand...
Click to collapse
hey,did u unpack the system.tgz in linux or in windows? Aftr getting the rom backup copy the system.tgz file to linux. Unpack it there. Else ull broke symlinks as windows FAT n NTFS file system can contain symbolic links. U pls calm dwn n do the following, extract the system.tgz,make the system.fex n use the blank image i gave. Use ur own boot n bootloader. Replace files in ISO folder too n pack. N flash it.. It will work. I hav tested alot of roms. If u keep the whole system.tgz intact and dnt change anything ull get a working image. Im using mine. Still u try with a cool head n know each tool well 1st. Thn try again. If u hav a backup dnt wrry,u will b able to build ur image. Tell me if it works or not.ok.
Oops!!! Ya I made a typo on the make_ext4fs part.
EarthBoundX5 said:
Shouldn't it be [make_ext4fs -s -l 500M -a system <filename.fex> {location of the system directory}]?
Click to expand...
Click to collapse
Ya I made a typo on the make_ext4fs part. Yup file name should come first. Then directory containing system files. If all else fails u can upload ur backup (boot,bootloader,system) n ill hav a go at it.
cybermate123 said:
hey,did u unpack the system.tgz in linux or in windows? Aftr getting the rom backup copy the system.tgz file to linux. Unpack it there. Else ull broke symlinks as windows FAT n NTFS file system can contain symbolic links. U pls calm dwn n do the following, extract the system.tgz,make the system.fex n use the blank image i gave. Use ur own boot n bootloader. Replace files in ISO folder too n pack. N flash it.. It will work. I hav tested alot of roms. If u keep the whole system.tgz intact and dnt change anything ull get a working image. Im using mine. Still u try with a cool head n know each tool well 1st. Thn try again. If u hav a backup dnt wrry,u will b able to build ur image. Tell me if it works or not.ok.
Click to expand...
Click to collapse
99% sure I extracted in windows! Didn't even cross my mind about symlinks! I'll make a new img then, but just for archival purposes at this point...
EDIT: Again, I'm gonna continue a bit more, but at my thread, as I don't want yours to get garbaged up with my specific posts that are not 100% on topic to your thread...
EDIT 2: and nvm, I've been up late, and looking at my linux machine...I definitely extracted my system in linux, not windows...but again, doesn't really matter moving forward...
Thanks for providing very nice tool suite. I've just started to find decompile/compile tool for fex file. Fortunately soon your tool was found in XDA and I could start modding bootloader in order to solve hsync area problem on my device!!
Sent from my ATB701A using xda app-developers app
There must be something wrong going on, Ive tested my tools again...
EarthBoundX5 said:
99% sure I extracted in windows! Didn't even cross my mind about symlinks! I'll make a new img then, but just for archival purposes at this point...
EDIT: Again, I'm gonna continue a bit more, but at my thread, as I don't want yours to get garbaged up with my specific posts that are not 100% on topic to your thread...
EDIT 2: and nvm, I've been up late, and looking at my linux machine...I definitely extracted my system in linux, not windows...but again, doesn't really matter moving forward...
Click to expand...
Click to collapse
Im nt able to understand what might have gone wrong. As I hav unpacked ROMs of LY-F1,Eken T01,My stock ROM,an Sanei A90 ROM,Digma ID7 etc. I only got bootloop while making a livesuit image out of a Cyanogen mod build. But that was all about symlinks. I hav a doubt though I tested everything still I say u take a look at the blank livesuit image I provided, If its the problem( mines 7inch tab n that blank img is my base) u dwnload a img file which nearly matches urs n rip it apart,change n push ur things in n pack. Dnt wrry ur tabs nt bricked. And u can post here, it will nt trash my thread. Giv a logcat if u can. Ok.
cybermate123 said:
Im nt able to understand what might have gone wrong. As I hav unpacked ROMs of LY-F1,Eken T01,My stock ROM,an Sanei A90 ROM,Digma ID7 etc. I only got bootloop while making a livesuit image out of a Cyanogen mod build. But that was all about symlinks. I hav a doubt though I tested everything still I say u take a look at the blank livesuit image I provided, If its the problem( mines 7inch tab n that blank img is my base) u dwnload a img file which nearly matches urs n rip it apart,change n push ur things in n pack. Dnt wrry ur tabs nt bricked. And u can post here, it will nt trash my thread. Giv a logcat if u can. Ok.
Click to expand...
Click to collapse
I have already been flashing other images, and I am not concerned about bricking it anymore (now that I understand FEL and LiveSuit). I've already moved passed getting this working and am not working on getting CM10 working with compatibility packs...as I have no idea which to use for my tablet.
EDIT: I mean, should I just make my own compatibility pack? If so, I wouldn't know where to begin with what files out of my old system partition I'd need are...or even if they were jb compatible (coming from ics)
EDIT 2: Its a BRONCHO A710 according to the build.prop if that will help
EDIT 3: Which I've found is a clone of LY-F1, so I'll try messing with installing CM10 with that compatibility pack...although it appears many have had issues with it...which apparently I am having too, as its hanging on booting CM...
EDIT 4: I updated my thread with my absolute current situation and made 3 posts in other threads...
Also, to clarify, I'm not getting booting problems after I flash my created image, I'm getting Android loading problems...it passes the boot screen and enters the 2nd loading screen just fine, but it sits at the 2nd loading screen (3rd different screen visible during boot) forever.
Size of the system partition should never be set as fixed 500 mb, it should be taken from sys_partition.fex or sysconfig.fex (depends of AW chip) * blocksize. Setting wrong size can cause image corruption and partition will be always mounted as read only.
Yup. Sysconfig file should also be set properly.
EarthBoundX5 said:
I have already been flashing other images, and I am not concerned about bricking it anymore (now that I understand FEL and LiveSuit). I've already moved passed getting this working and am not working on getting CM10 working with compatibility packs...as I have no idea which to use for my tablet.
EDIT: I mean, should I just make my own compatibility pack? If so, I wouldn't know where to begin with what files out of my old system partition I'd need are...or even if they were jb compatible (coming from ics)
EDIT 2: Its a BRONCHO A710 according to the build.prop if that will help
EDIT 3: Which I've found is a clone of LY-F1, so I'll try messing with installing CM10 with that compatibility pack...although it appears many have had issues with it...which apparently I am having too, as its hanging on booting CM...
EDIT 4: I updated my thread with my absolute current situation and made 3 posts in other threads...
Also, to clarify, I'm not getting booting problems after I flash my created image, I'm getting Android loading problems...it passes the boot screen and enters the 2nd loading screen just fine, but it sits at the 2nd loading screen (3rd different screen visible during boot) forever.
Click to expand...
Click to collapse
yup sysconfig files should be set properly n u should see logcat. If ur file system is read only it will nt let u run anything n say sh permission denied. If thats the prob thn its error wit livsuit or system img making. As Ive seen sum roms use a bootloader script o make some symlinks n set permissions. I think ur bootloader is also doing same but as ur using the ROM frm ur tablet the flag fr da script is already present so its nt making the changes. Thus in someplace its stuck. A logcat would hav really given clr indications.
why its hard for me to this?
this is the files i get at first satge aka dumping :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's an Allwiner A20 tablet and I just want to have a backup img nothing more.
is there an easier way to do this?
I can install lnux inside vbox and go for step two but
what about " putting .iso files in _iso folder? where are they? I don't have any .iso files in dump folder.
sr i hope u can help please
hi bro i have my dump rom but i need make a .img file to take my own stock rom cause my divice es too strange and i have no way to take my stock rom. my tab is now in some rom but dint work anythink just boot and thats it.
can use my dump to make me a img file to flash with live suit? i realy dont know linux i use windows.
cybermate123 said:
Hi all, I have made been using these tools to modify and customize livesuit images to suit my needs, now I have packed all of them for u to get ur workstations to get ur hands dirty with some ROM editing/making. before u jump right in I must say though allwinner devices are not brickable, but still u may get ur warrenty void,get ur data wiped or miss a trip with ur mama or gf, and for all those reasons Ill not be held liable.
Now, my toolset includes the following - A ROM backup utility that backs up ur BOOT,BOOTLOADER,SYSTEM n RECOVERY, this will be ur starting point if u dont have any stock image.
A blank livesuit image with fake bootloader,boot,system n recovery fex files. which u will have to fill in with ur own stock roms, after u take backup. (if u dont have a stock ROM already.)
Linux tools to help u edit script.bin files and image tools to split boot images, pack or unpack system.fex etc.
The image packing/unpacking program.
#### GUIDE ####
Now we have our tools, get started....
To make stock image :
1. Get ur fimware dumped using the backup tool.
2. On a linux pc use the tools in the tools.tar.gz archive to make the dumped system file into a system.fex file by doing the follwing :
Make a directory called system.
Unpack the whole system.tgz file which u got from the dump tool inside it.
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>] u will get a system.fex file as output.
3. Now copy the boot.img bootloader.img recovery.img (rename the .img extension to .fex) and the system.fex u made inside the blank livesuit image and replace the nessecary files. And also replace files in the _iso folders. here ull hav to add .iso at the for filename. its pretty simple, just see how the blank files are kept.
4. Now u can pack the whole directory using the image_repacker program. Fire up runner.bat and put the directory make_stock.img.dump in it. It will generate a stock image of ur tablet. back it up as it will save u from many blunders in future.
Now if u want to modify any other livesuit image what will u do:
Just unpack the tool using the image_repacker program. run the runner.bat file, put the .img file on it(drag n drop) and use the /skip parameter in the options and let it do its work. u will get lots of files. now in a linux machine u can use the simg2img binary to make the system.fex file to a mountable image by using [simg2img <system.fex system.img>]
now mount it...make a directory called system, type these commands in the shell , [sudo mount -o loop system.img system ] this will mount the system.img inside the folder. now to make life simpler type [sudo nautilus] (on ubuntu) n start the file manager with super user access. n navigate to the system folder. now u can change files,delete unwanted stuff etc. after ur done with it pack the system directory using the make_ext4fs binary,type [ make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex> ] u will get ur system.fex file which u can pack in a livesuit image and flash.
Allwinner tools2.rar
http://www.4shared.com/rar/S3cbf46k/Allwinner_tools2.html
Click to expand...
Click to collapse
ok but can i use it in win7 it very helpfull and i wnna it so
need livesuit image file for ice x treme tab
Hi Bro,
Please share me link of any working JB livesuit Roms for ice extreme tablet ,
my tablet specs here : http://www.icexelectronics.com/shop/ice-xtreme/
Bro , if u have the same tablet with u , plz plz help me by making a livesuit image of yours...
currently , my tablet hangs around the boot logo .... cant get in to recovery either...
Please do help me...
Thanks
Hari
cybermate123 said:
Hi all, I have made been using these tools to modify and customize livesuit images to suit my needs, now I have packed all of them for u to get ur workstations to get ur hands dirty with some ROM editing/making. before u jump right in I must say though allwinner devices are not brickable, but still u may get ur warrenty void,get ur data wiped or miss a trip with ur mama or gf, and for all those reasons Ill not be held liable.
Now, my toolset includes the following - A ROM backup utility that backs up ur BOOT,BOOTLOADER,SYSTEM n RECOVERY, this will be ur starting point if u dont have any stock image.
A blank livesuit image with fake bootloader,boot,system n recovery fex files. which u will have to fill in with ur own stock roms, after u take backup. (if u dont have a stock ROM already.)
Linux tools to help u edit script.bin files and image tools to split boot images, pack or unpack system.fex etc.
The image packing/unpacking program.
#### GUIDE ####
Now we have our tools, get started....
To make stock image :
1. Get ur fimware dumped using the backup tool.
2. On a linux pc use the tools in the tools.tar.gz archive to make the dumped system file into a system.fex file by doing the follwing :
Make a directory called system.
Unpack the whole system.tgz file which u got from the dump tool inside it.
run a shell, inside the shell run the make_ext4fs binary and give these arguments [make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex>] u will get a system.fex file as output.
3. Now copy the boot.img bootloader.img recovery.img (rename the .img extension to .fex) and the system.fex u made inside the blank livesuit image and replace the nessecary files. And also replace files in the _iso folders. here ull hav to add .iso at the for filename. its pretty simple, just see how the blank files are kept.
4. Now u can pack the whole directory using the image_repacker program. Fire up runner.bat and put the directory make_stock.img.dump in it. It will generate a stock image of ur tablet. back it up as it will save u from many blunders in future.
Now if u want to modify any other livesuit image what will u do:
Just unpack the tool using the image_repacker program. run the runner.bat file, put the .img file on it(drag n drop) and use the /skip parameter in the options and let it do its work. u will get lots of files. now in a linux machine u can use the simg2img binary to make the system.fex file to a mountable image by using [simg2img <system.fex system.img>]
now mount it...make a directory called system, type these commands in the shell , [sudo mount -o loop system.img system ] this will mount the system.img inside the folder. now to make life simpler type [sudo nautilus] (on ubuntu) n start the file manager with super user access. n navigate to the system folder. now u can change files,delete unwanted stuff etc. after ur done with it pack the system directory using the make_ext4fs binary,type [ make_ext4fs -s -l 500M -a system {location of the system directory} <filename.fex> ] u will get ur system.fex file which u can pack in a livesuit image and flash.
Allwinner tools2.rar
http://www.4shared.com/rar/S3cbf46k/Allwinner_tools2.html
Click to expand...
Click to collapse
Help wit custom ROM AMPE A96
I have an original ROM for my tablet (download here w-w-w.szampe.com/en/support_down.asp?id=1205 or here w-w-w.szampe.com/UploadFile/file/2011-08/0317.rar
Can you help me creating a custom ROM with CMW recovery and a current android OS?
a31 ?
Does this tool also work for allwinner a31?
Thanks in advance.
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
looking for the same
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
me too looking for the same thing ..how to extract from or decompile .backup file which we get thru recovery.
hi loverboyritesh :: i and you are in same position.. but some advaaanced users are here that we are telling rumors and lies.. dont worry bro.. even i'm trying to get solution.. will tel you after geeing one.. Still no one can tell me hoe to extract .BACKUP file..
same
i am looking for how to reinstall .backup myself so i can have my original rom install.
but i have notice my .backup is 700+mb while custom rom is 200+mb
do you know how to?
reena0307 said:
I Backup-ed my Acer tab b1-A71 using android system recovery - Just like CWM.
The file name ends with .Backup, and i wanted to extract some files from it..
How to Extract data from .Backup file ? - Created with android system recovery
Click to expand...
Click to collapse
same here. dunno how to open and extract the files from a .backup file. hoping you know already
siiingkeeet said:
same here. dunno how to open and extract the files from a .backup file. hoping you know already
Click to expand...
Click to collapse
Nope.. Still i'm having that file but no one knew
reena0307 said:
Nope.. Still i'm having that file but no one knew
Click to expand...
Click to collapse
been searching for 5 days now :<
not a single answer found on google and forums
cant even post a new thread yet. just joined
hope someone will drop by this thread
still no solution?
got same problem here
Got a bootloop issue with an ASUS MeMo Pad 7 HD and I've booted in recovery <3e> to make a backup.
I've got a userdata_YYYYMMDD_HHMMSS.backup. I tried opening it with a bunch of tools like unyaffs, abe (Android backup extractor), going live on the file using linux tools (open as 7zip, zip, rar, tar, tar.gz, gz, bz2 , mount as iso, ext4 and so on....)
Still no luck :-/
Only clue is that the file seems compressed. During the backup under recovery, it told me 3600MB to backup and the file userdata_xxxxxxxx_xxxxxx.backup show only 2.61GB
I did this backup 3 time to ensure there were no corruption during the write process from the pad and did again the same "tests" to open the file...Not better.
If any dev' have any clue of the file format, I'd be glad to help
It doesn't seem to be a valid unix img file. Tried mounting it to no avail. When it's restored by the recovery it also extracts the individual files because i fails on one in my case and stops the entire restore... I tried unzipping it, changed extension to ,jar, .tar, .zip, etc., none of them are recognised...amazing for a standard android feature to find so little info about it
Any solution?
I called Alcatel's technical service today and they told me that you can use the backup file only from the phone. Mine gives me the following error when I try to restore it: Error Magic header
If anyone knows how to unpack the backup file I would be more than grateful.
It's a 512 byte header in front of a "tar.gz"
hexdump -C userdata_xxxxxxxx_yyyyyy.backup | lessshowed the magical zip header "1f8b0800 00000000" at offset 0x200
So, skipping 512 bytes, the rest can be gunzip | tar
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
Sir ektoric what d u mean on ur post?
Sorry cant understand it..
Can u please d a step by step procedure? Please...pls...plss
Thanks in advance...
Steps?
@ektoric sir im a noob in this... Can u show a step by step procedure?
@killen00 sorry, I assume you have a linux machine (or have access to one). The command is actually all there is to it.
Code:
dd if=userdata_xxxxxxxx_yyyyyy.backup bs=512 skip=1 | gunzip -c | tar xv
If you don't have a linux machine available, might I suggest one of the many distros of your choice, most of which have LiveCDs which you can run without installing.
script for gunzip method
maybe on xda it is common sense, but for me it was necessary to know, that these stock android recovery extracted files can be restored with nandroid custom recovery, if you simply repack them into tar archive.
i put this two command lines in a dirty shell script (extract + repack as tar).
thanks to ektoric figuring out his gunzip method!
edit: notamamasboy's mount method added (but not tested yet). if script not works come back few days later, download again and check version, maybe it has changed meanwhile.
with this you're able to transfer data of non-rooted phone to (rooted) similar one.
this is useful in case touchscreen is broken, you haven't custom recovery installed, usb-debugging is disabled and connecting usb-otg-mouse doesn't work.
tested on my Archos 50 b Oxygen (Mediatek MT6582).
it works for me, feel free to improve, port to busybox and publish. no support. use at own risk.
edit: bckp2cwm.sh is deprecated it is FOR JELLY BEAN ONLY (no selinux support)
a newer (selinux) version bckp2win.sh for TWRP you can find here:
http://forum.xda-developers.com/showthread.php?t=3775129
How did you go about determining the magic number found at 0x200? My hexdump output does not have that magic number (1f 8b) in any instance. Leads me to believe my backup is not a tar file. Any suggestions then?
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
ektoric said:
@notamamasboy, you are unfortunately correct.
Someone else also mentioned that their
Code:
userdata_xxxxxxxx_yyyyyy.backup
file was not of the same format I tried some "known magic headers", and could not find anything tell-tale. In which case, without some clues, you are back at square one.
Click to expand...
Click to collapse
Even more peculiarly, two backups were created a .backup and a .backup2, I wonder if combining with cat I can get somewhere...