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.
Related
Can we flash rom using PC ?? Its not that big a deal but sounds cool to me.. i cudnt find any such option in nandroid-mobile.sh.. I mean after i reboot into recovery i dont want to press any buttons on my phone..Juts hook up the phone to pc and flash the new rom using say adb
It should be possible. When flashing zips, the recovery checks the update-script file found in the META-INF folder. Mimicking the steps there and inputting the correct adb commands and copying the files on the appropriate folders and partitions on your phone should yield the same results.
But as you may have guessed, this isn't practical.
so u mean to say that i unzip the contents of the zip archive and just execute the script from terminal ???That shud be it??? I know its impractical but wat the hell i love doing things from my debian terminal
Update: that script is just a set of messages to be shown during actual update process..it isnt the script ..
instead the script apparently "update-binary" is a binary executable and not a shell script..DO you think that unzip and calling this binary might work??
I'm not entirely sure. I think adb has it's limitations. Check other's replies xD
Hai all i am working on a working ics rom for the Veolo player and clones.
Now i downloaded a rom from Himedia Q5 and wanted to extract the system.img logo.img and boot.img files to see whats inside
I tried all tools available on this forum (Unjaffs2 etc.) but no luck so far
The firmware is available here https://mega.co.nz/#!KMkHVTCR!XSLG0gNa-z20jDqYNQbNMy89qQZC1WIQpy5SmUGAcbk
Can some one try to extract this img files for me and explain to me how they did it ?
I can,t run it n the veolo beause the veolo has 512mb system memory and the himedia q5 1gb.So i can't make a system dump.
I want to modify the rom to be used on a veolo thats the idea.
I thing these files are packed some how ???
Hope you can help me guys thnx
system.img is an yaffs2 file system: 4K 24bits/1K and contains root filesystem as well.
boot.img is NOT an Android boot image, but an uImage kernel.
bootargs.img contains kernel boot arguments in text.
Quite not-the-way-we-do-it-in-Android, but manageable.
yeah i know the bootimg contains the kernel etc and the system.img is a yaffs2 file system i also know
Buit still the problem is that i can't extract the root file system etc in it all tools i could find gave a error ?
Any idea how i can extract it ? since the common tools seems not to work ?
Thx for the info btw
Anyone who can help me unpack the system.img and the userdata.img ???????????????????
Unpack system.img Q5 and MMB-422 or Veolo aka Godbox
kraakie256 said:
Anyone who can help me unpack the system.img and the userdata.img ???????????????????
Click to expand...
Click to collapse
Yeah, no problem. I own a MMB-422, a Veolo look-a-like. I have an ICS firmware for it, so it should also work on your Veolo. The problem is that you need an RS232 <-> UART or USB <-> UART converter to modify the systems partition and upload the new ICS firmware. I build one myself. I posted the howto on meteorit.wikia.com/wiki/MMB-422.HDTV/Software-Updates
I managed to decompile the system.img and userdata.img from the Q5 with yaffs2utils. I believe I used the following command ./unyaffs2 -p 4096 -s 200
To unpack the MMB-422 firmware (8K chunks and 366B spare) I also use unyaffs2 but with -p 8094 and -s 366
But then......I can pack the system dir again to an system.img with mkyaffs2img but it generates an image with a complete different layout and it cannot be used with our "Godbox".
Maybe we can coöperate? Do you live in The Netherlands? I do......Do you have C++ skills?
bobbes said:
Yeah, no problem. I own a MMB-422, a Veolo look-a-like. I have an ICS firmware for it, so it should also work on your Veolo. The problem is that you need an RS232 <-> UART or USB <-> UART converter to modify the systems partition and upload the new ICS firmware. I build one myself. I posted the howto on meteorit.wikia.com/wiki/MMB-422.HDTV/Software-Updates
I managed to decompile the system.img and userdata.img from the Q5 with yaffs2utils. I believe I used the following command ./unyaffs2 -p 4096 -s 200
To unpack the MMB-422 firmware (8K chunks and 366B spare) I also use unyaffs2 but with -p 8094 and -s 366
But then......I can pack the system dir again to an system.img with mkyaffs2img but it generates an image with a complete different layout and it cannot be used with our "Godbox".
Maybe we can coöperate? Do you live in The Netherlands? I do......Do you have C++ skills?
Click to expand...
Click to collapse
Well i managed to unpack it etc but my Veolo died Flash mem full of bad blocks grrrr
I amw aiting for a replacement
Btw The firmwares MMB-422 choose -p8192 -s368
And for the Himedia -p4096 -s200 and you can repack it with -p8192 -s368 but it seems that somehow the fw crashes when you flaash it
I think it's a library in the lib folder who causes the crash
Can't continue at the moment since my veolo died
And no i dont have C++ Skills i understand it a bit
Btw The firmwares MMB-422 choose -p8192 -s368
Click to expand...
Click to collapse
That's true. I made an mistake.
And for the Himedia -p4096 -s200 and you can repack it with -p8192 -s368 but it seems that somehow the fw crashes when you flaash it
Click to expand...
Click to collapse
The (re)compiled image has a complete different structure so the mkyaffs2img program has to be rewritten to suite our needs. It wont flash it in bootloader (u_boot aka fastboot) mode.
To bad that your Veolo's NAND has died! Are you sure? Did you try a complete erase of the whole NAND and then repartition the NAND again? Do you use UART?
bobbes said:
That's true. I made an mistake.
The (re)compiled image has a complete different structure so the mkyaffs2img program has to be rewritten to suite our needs. It wont flash it in bootloader (u_boot aka fastboot) mode.
To bad that your Veolo's NAND has died! Are you sure? Did you try a complete erase of the whole NAND and then repartition the NAND again? Do you use UART?
Click to expand...
Click to collapse
yeah it's dead i used a uart\
When you recomplile remove the first part of the header with a hexeditor
Look for Yffsv10 or something like that
And remove all crap before that. other wise fastboot won't regonize it as a yaffs2 image
Hi all, some of us allwinner device users find us having a clone n no firmware to download in case a custom ROM fails. Here how to save urself. Download any clones stock rom. If ur on ics dwnload ICS. Nw install n setup adb n pull ur whole tablets internals out. By using commands like adb pull system system. It will make a dir called system n pull ur system partion in. Nw fr da bootloader n boot we use cat to read nand partitions nandc n nanda. Su -c "cat dev/block/nandc > sdcard/boot.img" n sameway read nandc to a file bootloader.img.
Now wit any rom un/packing utility (i use image repacker) unpack the clone image. Replace the boot n bootloader files inside the unpacked livesuit img n chnge extension to .fex (if ur packing program has iso folder change there as well) no repack n flash. If it works on whole its cool. Else use adb to push modules from ur system folder to the rom ur running. Also push the etc folder to system/etc n push the hw folder in lib/hw to system/lib/hw. Nw reboot. It will work.
Nw fr a permanent solution. Use sunxi tools in ubuntu or any linux to 1st make the system.fex of the clone ROM to a system.fex file using SIMG2IMG. Nw mount it by using sudo mount -o loop system.img <system> nw in ubuntu u should type sudo nautilus n open the gui file browser in su mode. It makes changing files a bit easy. Nw frm ur backed up system folder copy the contents of vendor/modules lib/hw n etc to the mounted dir. Aftr ur done use MAKE_EXTFS to make a sparse fex file. Use make_ext4fs -s -l 500M -a system system newsystem.fex . It will make u newsystem.fex. Copy it back to ur unpacked rom. Replace it. Pack. Flash. U got ur stock rom running. (not actually,as u havent changed apps,do it if u want).
If u want u can make the ext4fs directly frm ur backed up system folder. Now copy the new fex file back.repack.flash. It will bring u ur true stock rom back. N on some livesuit images it corrupts the diskfs so da internal sd doesnt mount. (in eken T01A's ROM) the do the following. Open adb shell cd to dev/block the last nand partition is ur sdcard. Format it by using busybox mkfs.vat dev/block/nand(the last letter u saw in dev/block i.e. nandj). Then type vold. Ull get it mounted. Now u can hav peace of mind while flashing custom ROMs. Enjoy.
U will need things- tablet running stock ROM. U can get it frm a frnd also . Sunxi tools from github by amery. A linux box. A windows pc fr un/repacking the image. N common sense. I didnt goto very details abt da commands. U will need it there. N one thing to note u dnt even need a linux box if u hav a working tablet. In the system/bin folder u hav ur simg2img n make_ext4fs binaries. So u can do that part on a tablet. I leave this part fr u to figure out own ur own. N while ur at it,change ur stock bootanimation wit sumthing cool if u want. Copy it in system/media. If a file is already there then back it up.set permission to rw-r-r. Enjoy. Hope ull hit the thanks button.
where i can find stock rom??
i messed it up.
flash custom rom nuclear_pfdq88c-eng 4.0.4 IMM76D 20120821 test-keys and wifi not working.
AND THE TABLET IS NOT MINE!!! LOL!!!
Custom ROM for Ampe 96
I have an original ROM for my tablet (download here w_w.szampe.com/en/support_down.asp?id=1205
Can you help me creating a custom ROM with CMW recovery and some current android OS?
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...
Hi, I have new Prestigio tablet PMT5777_3G and I want to modify it's default ROM. I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=1801690. I successfully extracted system folder, but I have no idea how to create updater-script for this specific ROM. If I understand correctly I need to get updater-script from original ROM.
I've got something that resembles original ROM, but it's folder structure is completely different from what I would expect.
I would expect:
META-INF
system
boot.img
I've got:
APDB_MT6582_S01_MAIN2.1_W10.24
boot-sign.img
BPLGUInfoCustomAppSrcP_MT6582_S00_MOLY_WR8_W1315_MD_WG_MP_V12_P4_1_wg_n
cache-sign.img
Checksum.ini
EBR1-sign
lk-sign.bin
logo-sign.bin
MBR-sign
MT6582_Android_scatter.txt
preloader_htt82_tb_jb5.bin
recovery-sign.img
secro-sign.img
system-sign.img
sro-lock-sign.img
sro-unlock-sign.img
userdata-sign.img
I'm an android developer, but have no experience with custom ROM's and now am in a situation, where I want to get that custom ROM up and running, but am unable, because I can't figure out how to create updater-script or extract it from files that I currently have. It would be great if someone could point me to the right direction of what to do next.
Thanks
P. S. It seems it's against the rules to ask questions here, but I can't seem to find where else to ask this on xda
Dantenas said:
Hi, I have new Prestigio tablet PMT5777_3G and I want to modify it's default ROM. I followed this tutorial: http://forum.xda-developers.com/showthread.php?t=1801690. I successfully extracted system folder, but I have no idea how to create updater-script for this specific ROM. If I understand correctly I need to get updater-script from original ROM.
I've got something that resembles original ROM, but it's folder structure is completely different from what I would expect.
I would expect:
META-INF
system
boot.img
I've got:
APDB_MT6582_S01_MAIN2.1_W10.24
boot-sign.img
BPLGUInfoCustomAppSrcP_MT6582_S00_MOLY_WR8_W1315_MD_WG_MP_V12_P4_1_wg_n
cache-sign.img
Checksum.ini
EBR1-sign
lk-sign.bin
logo-sign.bin
MBR-sign
MT6582_Android_scatter.txt
preloader_htt82_tb_jb5.bin
recovery-sign.img
secro-sign.img
system-sign.img
sro-lock-sign.img
sro-unlock-sign.img
userdata-sign.img
I'm an android developer, but have no experience with custom ROM's and now am in a situation, where I want to get that custom ROM up and running, but am unable, because I can't figure out how to create updater-script or extract it from files that I currently have. It would be great if someone could point me to the right direction of what to do next.
Thanks
P. S. It seems it's against the rules to ask questions here, but I can't seem to find where else to ask this on xda
Click to expand...
Click to collapse
Since you are a beginner to ROM development, I would recommend the use of dsixda's Android kitchen, which you probably have downloaded already. If not use this link
http://forum.xda-developers.com/showthread.php?t=633246
Follow these steps to obtain the file structure and Meta-Inf folder for your custom rom.
1. Open the folder where you have placed the kitchen.
2. You will find a folder called original_update.
3. Open that folder and copy your boot.img and system.img files into it. ( In your case it is boot-sign.img and system-sign.img. Rename those files into boot.img and system.img and place them in the folder )
4. Now open the kitchen. ( Refer the above link to know how to do it )
5. You will find " 1. Set up working folder from ROM " option under Main Menu.
6. Type 1 and you will be directed to another menu. Click Enter.
7. Select your boot.img and system.img from the menu.
8. Now follow the instructions that appear on the screen.
9. When you successfully complete the steps, you will have the required Working folder, with boot.img, system folder and Meta-Inf folder, which will contain the updater-script (It will be automatically generated)
All the best. :good:
Hit Thanks if this helped you... PM me if you need further help or search the forum for detailed instructions.
Thanks, this helped me, but I still can't create ROM.
I encountered a problem with kitchen:
Code:
Available ROMs:
(1) system.img and boot.img
Enter selection number (default=1, cancel=0, r=refresh):
Found original_update/system.img
Found original_update/boot.img
The new working folder will be named WORKING_061614_070841
Change the name (y/n)? (default: n):
Creating working folder WORKING_061614_070841 ...
Copying boot.img ...
Copying system.img ...
Adding an update-script ...
NON-YAFFS/NON-TAR FILE FORMAT DETECTED IN ROM
Mounting system.img to loopback device and then extracting files ...
Error: Unable to mount system.img
Error: No /system/framework folder found!
Press Enter to continue
This creates my missing update-script and boot.img, but system folder is empty.
Would it be a good idea to extract all system files from device and attempt to create ROM with them, and this update-script, or is there something I could do with system.img to make it extract?
Try this
Don't worry. There's always an alternative. Try this simple method.
1. Boot into CWM (Clockwork Mod) Recovery. (I'm pretty sure you know how to do it, if not, you can feel free to search the forum)
2. Choose Backup and Restore.
3. Make a backup in your external sdcard.
4. Now boot normally, open your external sdcard. You will find a folder called clockworkmod. Copy that folder to your PC.
5. Inside that folder, you will find the backup.
6. Now, copy boot.img and system.ext4.tar.a to your original_update folder of the kitchen.
7. Warning! Do not copy system.ext4.tar, only copy system.ext4.tar.a
8. Once you have copied these two files, rename system.ext4.tar.a into system.ext4.tar
9. Now, open android kitchen and follow the exact same steps as you did before.
10. When you choose the available rom, you will find the screen as below.
Code:
Available Roms:
(1) system.ext4.tar and boot.img
11. Choose it and follow the instructions. You will have your required working folder.
Try this and let me know if you still face any issues. :good:
I was unable to load CWM recovery, because it is not supported by my device. I tried TWRP too, which also doesn't support my device. Is it possible to do without CWM?
Dantenas said:
I was unable to load CWM recovery, because it is not supported by my device. I tried TWRP too, which also doesn't support my device. Is it possible to do without CWM?
Click to expand...
Click to collapse
I'm sorry my friend, even if you create your own ROM, you require either one of them to flash the ROM to your device. Seeing you so keen on developing the rom, try to use any yaffs tool to create your system.img from extracted system folder. You may refer this thread.
http://forum.xda-developers.com/showthread.php?t=1645412