hey guys.. i been looking around everywhere to try and get a good explanation of the files inside the rom.zip... like what the files are in the META-INF? and what are all the files inside the system folder? how do i know what to change and what not to change.. lol sorry but if anyone could possibly give me a more in depth explanation i would appreciate it greatly!!!
i dont have answer but i would also like to know this... since im just trying to learn how be a dev...
lol seems no one can help us... but this did help a little... http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
Hi
The files in META-INF are just that, meta files they contain information about the files that are part of the rom.. specifically CERT.* and MANIFEST.MF contain the SHA1 hash of each file in the rom when you flash the rom your recovery environment hashes each file and checks it against the manifest. These files are created during the signing process.
META-INF/com/google/android/updater-script tells the recovery environment what to actually do. such as format /system then extract system to /system on the phone, set permissions for each file and the correct kernel to your boot.img then reflash it
the files in /system are the actual operating system and are in a UNIX-ish layout
executable's in bin & xbin, system apks in app, configuration files in etc, libraries in lib, ringtones and bootanim in media
rattking said:
Hi
The files in META-INF are just that, meta files they contain information about the files that are part of the rom.. specifically CERT.* and MANIFEST.MF contain the SHA1 hash of each file in the rom when you flash the rom your recovery environment hashes each file and checks it against the manifest. These files are created during the signing process.
META-INF/com/google/android/updater-script tells the recovery environment what to actually do. such as format /system then extract system to /system on the phone, set permissions for each file and the correct kernel to your boot.img then reflash it
the files in /system are the actual operating system and are in a UNIX-ish layout
executable's in bin & xbin, system apks in app, configuration files in etc, libraries in lib, ringtones and bootanim in media
Click to expand...
Click to collapse
wow rattking thank you very much!! that was the best description anyone has ever given me!!! lol that was very helpful!! is there a place where you learn this from? or did you just figure it out as you went..?
Related
So I guess my question is, "Can anyone help me?"
I used custom ringtones, and I don't like using them from the SD card, it creates lag, takes longer to load the ringtone, etc, so I keep them on my /system/media folder. Normally to accomplish this, when I install a new ROM update, I edit it and resign it, with my media folder, rather than the ROM's.
My predicament however, is that I don't know how to change the file structure for the update, I know there are files in the update that say, this and this folder exist, where this goes, etc. This is what I don't know how to do.
All I need the update to do is contain the media (/system/media) folder, so I can just add all my ringtones and notifications to this update, and flash it after I flash whatever update/rom, etc, instead of always having to be at my computer to create a custom version of every rom I use.
Could anyone please care to help? I'd be ever grateful.
You can use the attached file.
Just edit the files in the ROM
zip it
put the zipped ROM in the same folder as the attached files
run sign.bat
FLASH
ID# said:
You can use the attached file.
Just edit the files in the ROM
zip it
put the zipped ROM in the same folder as the attached files
run sign.bat
FLASH
Click to expand...
Click to collapse
is this just to be used for signing? i already know how to sign files. i need someone to edit w/e files are inside the rom that tell its structure (this folder exists, and gets flashed here, this folder goes here, etc). i cant just take a cm rom and delete everything i dont need then flash it. it will get errors in recovery.
Make a folder called media in the root of your update, and create the proper descending folders in media (i.e. audio/ringtones, etc). Place your notifications/ringtones/alarms etc in the proper folders. (I am sure you understand this already)
Open your update-script file for the update and add the line
Code:
copy_dir PACKAGE:media SYSTEM:media
That should do it.
Note that if in the update-script you already have an entire system folder being copied over via
Code:
copy_dir PACKAGE:system SYSTEM:
then you need only add the folder media to the folder /system in the update.
cloverdale said:
Make a folder called media in the root of your update, and create the proper descending folders in media (i.e. audio/ringtones, etc). Place your notifications/ringtones/alarms etc in the proper folders. (I am sure you understand this already)
Open your update-script file for the update and add the line
Code:
copy_dir PACKAGE:media SYSTEM:media
That should do it.
Note that if in the update-script you already have an entire system folder being copied over via
Code:
copy_dir PACKAGE:system SYSTEM:
then you need only add the folder media to the folder /system in the update.
Click to expand...
Click to collapse
Thanks man, but my buddy actually just helped me out with this, but yeah thats exactly what I needed to know. Thanks a ton mate
Hi...
I want to create my own update.zip from a original and clean RUU.exe I already know how to extract the exe file and all the other stuff that has to be done. But in the system.img arnt the necessary META-INF files.
I know its made with Android SignApk, but all Guides that I found show only how to sign one single apk. But it seems I need to sign all the stuff at once.
My question at the devs: How do you do this? And can I use my own key?
Don't know if can help you, but check dsixda's kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
Cheers
8ut8f8rder said:
Hi...
I want to create my own update.zip from a original and clean RUU.exe I already know how to extract the exe file and all the other stuff that has to be done. But in the system.img arnt the necessary META-INF files.
I know its made with Android SignApk, but all Guides that I found show only how to sign one single apk. But it seems I need to sign all the stuff at once.
My question at the devs: How do you do this? And can I use my own key?
Click to expand...
Click to collapse
Dude, that's simple:
Pack all your stuff into an update.zip and then let run Signapk with the zip file as filename and it will sign it for you correctly by creating a META-INF folder and calculating all SHA1 checksums...
Thanks, finally I got a selfmade working rom. dsixda has some usefull templates for the update-script in his kitchen.
@TheSSJ
I will try that, but I guess the zip-file has to contain a proper update-script.
TheSSJ said:
Dude, that's simple:
Pack all your stuff into an update.zip and then let run Signapk with the zip file as filename and it will sign it for you correctly by creating a META-INF folder and calculating all SHA1 checksums...
Click to expand...
Click to collapse
Can you detail it sir? im kinda new here Thanks in advance
I want to deodex stock firmware (2.36 - XWKTH) and i made the zip file with system folder include 'app' and 'framework' folders.
I can't create update-script for this.
any bady can make me a list of commands For the following? (of course with mount system and what is needed for this)
Code:
deleting .odex files forom app and framework.
copying system folder (in the zip file) to /system
Many thanks!
If someone can teach me how convert the rom.... I really appreciate it.
Use this method..
rizal2105 said:
If someone can teach me how convert the rom.... I really appreciate it.
Click to expand...
Click to collapse
Download a valid update.zip to
use as a template - for example,
my CyanogenMod 0.7.
Extract the zip to a new folder and
rename it - let's call the folder
updatezip .
Inside the updatezip folder, delete
the system folder and boot.img
file (as these are the
CyanogenMod files that you don't
want).
For the ROM you want to convert,
extract the contents of its
system.rfs image to a new folder
called system.
Copy this new system folder to the
updatezip folder.
Copy the boot.img file from your
ROM to the updatezip folder.
Re-zip the contents of the
updatezip folder (but not the
updatezip folder itself). If you see
warnings about symlinks not
being added, don't worry - we
don't want to add them anyway.
You need to have some Linux shell
experience in order to do this. You
can't do it from Windows.
rizal2105 said:
If someone can teach me how convert the rom.... I really appreciate it.
Click to expand...
Click to collapse
Use dsxida kitchen
Search about it.
Sent from my Nexus 5 using Tapatalk 2
Thanks for to all of your concerns. I really appreciated.
@sangalgojoe
Thanks Dude???
thanks for this i was seraching for this
Hi!
i don't know how to make a module so i want replace file in system/etc (file i want replace fonts.xml)
so can anyone help?!?
All the instructions you need are right here:
https://topjohnwu.github.io/Magisk/guides.html
Hi Sorry i try to read it (and look half internet) to understand how to simply replace a file with magisk. Maybe it has changed with version 24? Please link some source where it's easly explained how this task could be achieved.
Isn't this what you are looking for? https://topjohnwu.github.io/Magisk/guides.html#the-system-folder
The system folder
All files you want to replace/inject should be placed in this folder. This folder will be recursively merged into the real /system; that is: existing files in the real /system will be replaced by the one in the module’s system, and new files in the module’s system will be added to the real /system.
Click to expand...
Click to collapse