I downloaded the Android 4.4.2 source code that turned out to be about 14GB with more than 4,00,000 files.
I want to back up the folder in some .tar or zip or similar archive so that I can start fresh if something goes wrong in the working copy. I tried making a .tar.gz archive but it gave file permission errors during extracting and won't extract anymore.
So, how do I go about this ??
pauldmps said:
I downloaded the Android 4.4.2 source code that turned out to be about 14GB with more than 4,00,000 files.
I want to back up the folder in some .tar or zip or similar archive so that I can start fresh if something goes wrong in the working copy. I tried making a .tar.gz archive but it gave file permission errors during extracting and won't extract anymore.
So, how do I go about this ??
Click to expand...
Click to collapse
This is what I did in my starting days
I copied all the folders from the source directory to another HDD which was just 80gb... I kept it permanently as my backup HDD...
But while copying don't copy everything at once... Copy in pieces... The 'external, framework n repo' folders are huge... So copy one by one... Or It'll take forever to copy....
But actually backups aren't required... You can always reset any changes you make to any file..!
But what's wrong with archiving ? I get multiple errors of "Cannot create symbolic link".
And how can reset the changes of the entire source code ??
Related
PS: I managed to extract the system.rfs file and the boot.img to the Working folder in the Kitchen.But i dont know about this,if i repack the room it wont boot and i think i know where is the problem but i need some expert point of view.When you tap: 1 and S in the kitchens menu it shows the format for each ROM.I didnt find system.rfs and boot.img as an allowed format so i decided to rename my system.rfs in system.img...when i done that the kitchen loaded my ROM.Then i made a backup copy of my system.rfs extract it with magic iso and clicked the next step on the kitchen extracting progress.Then i restarted the application and clicked the option 99 for repacking...i selected the 1 option then,i taped NO at zipaligning,i signed and renamed my ROM.The rom was created,then i copyed it on my SD.In CWD i selected install zip from SD,the process failed it gave me an error similar to : your updater script is...bla bla.I reentered the kitchen,i selected YES to convert my updated script the rest of the options were like above,copyed the ROM to my SD when i clicked yes to install id gave me an error about the boot.img.Now im thinking that by renameing my system.rfs into .img made a corruption on system folder tree and META-INF , because system.img is specific to HTC.your advice guys?what i did wrong?
Use Magic ISO to open and extract the files.
私のEVO 3Dから送信される。
dastin1015 said:
Use Magic ISO to open and extract the files.
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
magic ISO?...i tryed but it wont open
PS: i managed to extract the MD5 file ,now what i will do with all of them?
see first post again pls
Or power ISO.
Sent from my GT-S5570 using xda premium
Today I wanted to see what the JellyBean for SGS III is like so I made a nandroid backup of my current setup. After playing with JB for a while, I wanted to restore the backup, but I was greeted with an error message.
I've been messing with this the entire F****** day and so far I've isolated the file that is corrupted (it's /system/app/Keystring_factory.apk).
So I need to delete that file from within the archive. The problem is how do I do that? When I try to copy the file to my computer, it hangs on it and says "corrupted file" (tried windows explorer but also total commander). I am able to open the archive on my SGS III using something like ZArchiver, but it doesn't have the option to delete the file from within the archive.
Help?
Deusdies said:
Today I wanted to see what the JellyBean for SGS III is like so I made a nandroid backup of my current setup. After playing with JB for a while, I wanted to restore the backup, but I was greeted with an error message.
I've been messing with this the entire F****** day and so far I've isolated the file that is corrupted (it's /system/app/Keystring_factory.apk).
So I need to delete that file from within the archive. The problem is how do I do that? When I try to copy the file to my computer, it hangs on it and says "corrupted file" (tried windows explorer but also total commander). I am able to open the archive on my SGS III using something like ZArchiver, but it doesn't have the option to delete the file from within the archive.
Help?
Click to expand...
Click to collapse
U can extract cwm with titanium backup or use a file explorer to extract the backup and delete the file then zip it.
But I would flash a new Rom and extract cwm with TB and restore the parts u need with TB.then when all is good make a new backup.
I don't think it's a good idea to restore a corrupted file even if u find the errors
Btw. Fayaab has tweeted that he is going to release a JB for gs3 tomorrow and this should be working
Tried that too, Titanium got stuck at the file. 7-Zip got stuck even when "Testing Archive". I'll write the file off as corrupt. Interestingly enough, the data.ext4.tar is also corrupt. Does this mean it's a time for a new microSD card? Or is it CWM that's writing corrupt files somehow?
Access system files from recovery any use .
http://forum.xda-developers.com/showthread.php?t=1646108
Works on SGS3
jje
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.
The op says that after downloading the file, unzip the file then put it in the TWRP/BACKUPS folder.
After booting the Safestrap recovery, use restore to install the rom.
Either I don't understand or there's some problem with the file I've downloaded.
When I unzipped the file I got VZW-S4-SS-TWRPBACKUP-I545XXUEMK8MK2OMEGA18 folder and inside there were another folder called
rom-slot2-I545XXUEMK8OMEGA18 and in that folder there are 5 files
(data.ext4.win, data.ext4.win.md5, recovery.log, system.ext4.win000, system.ext4.win000.md5).
After putting VZW-S4-SS-TWRPBACKUP-I545XXUEMK8MK2OMEGA18 folder into TWRP/BACKUPS folder,
I rebooted the phone into SS recovery and click restore button, but I don't see the VZW-S4-SS-TWRPBACKUP-I545XXUEMK8MK2OMEGA18 in restore. I have re-downloaded the zip file 3 times and got the same files. What am I doing wrong?
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk