Hey guys,
I found some threads on here on how to work in Kitchen and extract Android ROMS. Everything is set up, kitchen is working, cygwin is :good: but when i try extracting factory ROM folder of NEXUS 6 i found it gives some errors.
In the zip that i try to export there is a folder and the folder looks like this ->
-bootloader-shamu ... .img
-flash-all
-flash-base
-image-shamu- .. .zip (in here are the recovery.img,system.img ..)
-radio-shamu- .. .zip
When i try extracting this it gives "No system folder found"
When i try extracting image-shamu .zip it gives "sys/mman.h" can't be found..
Any usefull suggestions on what I am doing wrong ?
Thanks!
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
So, my phone recently got soft bricked....
I had the tar file of the XXELK4 leaked firmware and i extracted it, unpacked system.img.
Mounted it as ext4 and extracted the contents.
I want to make a flashable zip file from the system.img contents.
I made a folder called system. In which all app, bin, etc and other folders are.
Then i copied over the boot.img from the tar file...
Now, i need the meta-inf. I tried using some meta-inf from other roms, and removing the aroma functions from them.
Then trying to flash..
I get only a bootloop.
So, could someone provide a clean Meta-inf consisting of only the updater-script and update-binary??
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.
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 ??
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