I searched the forum but i cannot find the answer.
I would like to make an xrecovery zip file off the rom i use.
Is this possible and how.
Thanks.
You can create a nandroid backup instead using Backup and Restore in xRecovery
Titanium Backup for single files.
You can also grab the files that you need to push as an update via Titanium backup. It creates an update.zip with a few files inside that you can extract to another phone if you like...
Nandroid backups are made with xRecovery for the Xperia models. It will give you three files and a checksum file, these can be added to a zip file if you like and restored using xRecovery.
I've found a good article on XDA located here on the subject. It's not specific to the X10 or Xperia models but you might find it worth reading
benz0076 said:
I searched the forum but i cannot find the answer.
I would like to make an xrecovery zip file off the rom i use.
Is this possible and how.
Thanks.
Click to expand...
Click to collapse
I'm not a Dev but this is what I'd do if I wanted to make an update zip of the changes I've made to the Rom installed on my phone. Before you try it, just remember that I could be wrong on this and if your going to create your own package, try it on your own phone before releasing it for public use.
First thing to do would be to extract the files from any ROM update package, but preferably the one that your currently installed one is based on.
If you open the zip file there will be two or more folders. One will be system and the other META-INF. If you drill down through the META-INF folder to the bottom of the folder structure you'll find a file called "update-script" This is the script that XRecovery uses when it updates your phone and you can easily read what's being done.
Eg:
Code:
format DATA:
format CACHE:
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
And it would continue on with more after that.
The script is formating the Data, Cache, and system partitions on the phone in preparation for installing the new Firmware. It is then copying the contents of the System folder included in the package to the system partition on the phone. The rest after that is setting up symbolic links and setting directory permissions.
If you use ADB to pull the /system folder from you phone, that would be the equivalent of the system folder that is included in the update package.
Code:
md system
adb pull /system system
You could, if you wanted, just replace the system folder in the update package zip with the system folder that you just pulled from your phone and you would have a packaged ROM.
If you wanted to include apps in the package that are not in the /system/app folder you would need to pull the apps that you wanted to include from the /data/app
Code:
md data\app
adb pull /data/app data\app
You would then add the data folder to the rom package so that you would then have three folder instead of two.
data
META-INF
system
After that change the the beginning of the update-script file to look something like this
Code:
format DATA:
format CACHE:
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
After your all done use something like 7zip to zip everything back up using no compression "Store Only" and you should have a XRecovery installable ROM.
NOTE:
If you have paid apps and are making this ROM for anybody other than yourself to use, make damn sure that you remove them from the /data/app folder before zipping everything up into a package. Including paid apps in your ROM is Warez and won't be tolerated anywhere.
GreatBigDog said:
I'm not a Dev but this is what I'd do if I wanted to make an update zip of the changes I've made to the Rom installed on my phone. Before you try it, just remember that I could be wrong on this and if your going to create your own package, try it on your own phone before releasing it for public use.
First thing to do would be to extract the files from any ROM update package, but preferably the one that your currently installed one is based on.
If you open the zip file there will be two or more folders. One will be system and the other META-INF. If you drill down through the META-INF folder to the bottom of the folder structure you'll find a file called "update-script" This is the script that XRecovery uses when it updates your phone and you can easily read what's being done.
Eg:
Code:
format DATA:
format CACHE:
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
And it would continue on with more after that.
The script is formating the Data, Cache, and system partitions on the phone in preparation for installing the new Firmware. It is then copying the contents of the System folder included in the package to the system partition on the phone. The rest after that is setting up symbolic links and setting directory permissions.
If you use ADB to pull the /system folder from you phone, that would be the equivalent of the system folder that is included in the update package.
Code:
md system
adb pull /system system
You could, if you wanted, just replace the system folder in the update package zip with the system folder that you just pulled from your phone and you would have a packaged ROM.
If you wanted to include apps in the package that are not in the /system/app folder you would need to pull the apps that you wanted to include from the /data/app
Code:
md data\app
adb pull /data/app data\app
You would then add the data folder to the rom package so that you would then have three folder instead of two.
data
META-INF
system
After that change the the beginning of the update-script file to look something like this
Code:
format DATA:
format CACHE:
format SYSTEM:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
After your all done use something like 7zip to zip everything back up using no compression "Store Only" and you should have a XRecovery installable ROM.
NOTE:
If you have paid apps and are making this ROM for anybody other than yourself to use, make damn sure that you remove them from the /data/app folder before zipping everything up into a package. Including paid apps in your ROM is Warez and won't be tolerated anywhere.
Click to expand...
Click to collapse
Thanks i am going to try this and will let you know if it works..
Sent from my X10i using XDA App
Zip for xrecovery
I have some modified .png files for a theme and I need to make a zip for xrecovery, can someone explain IN DETAIL PLZ, on how to do this. this is what i think im supposed to do so far. change .apk to .zip, use 7zip edit files inside, change zip back to apk? thats about where i get lost
CAYCE_VII said:
I have some modified .png files for a theme and I need to make a zip for xrecovery, can someone explain IN DETAIL PLZ, on how to do this. this is what i think im supposed to do so far. change .apk to .zip, use 7zip edit files inside, change zip back to apk? thats about where i get lost
Click to expand...
Click to collapse
Follow this thread... http://forum.xda-developers.com/showthread.php?t=714288
Related
This is a tool I made for myself for backing up some of the custom files... Mostly as a result of wanting to expedite the process of backing up some configuration files in /system (such as inadyn.conf or bashrc on synergy rom). It reads a text file to determine what files you want, saves them in a tar on your sdcard (necessary to tar them to keep permissions the same when transferring to fat). Then you flash the restore zip to put them back.
It's set to not backup if there already is a backup (to prevent overwriting your custom files by clicking the wrong zip). The backup.tar is deleted on successful restore.
To use, create a text file in /sdcard/custBackups called custom_files.txt, and put the full pathname of each desired file in there, seperated by a single space (no newlines). While in recovery, run the backup zip to save your custom files, and run the restore zip to restore them after flashing.
An easy way to add the files while using adb shell (with busybox installed) is to cd and ls around to find your file, then while working in the same directory run this command
echo " `realpath myfilename`" >> /sdcard/custBackups/custom_files.txt
(those are backticks, not single quotes, which may be on hackers keyboard but isn't on most android keyboards, that's why I suggested adb shell)
looks long but is pretty quick with bash completion. But only needs to be done once for each file, the text file stays in place.
Thanks to Cyanogen's team and ginger yoshi, as I got the idea from them and learned the updater script reading their files.
A dev can put this in their own updater script so it's all in one (which I do when exporting the svn for synergy). If you can't figure out how to add it reading my script, let me know. And if any devs do use, just shoot me some credit.
If this is used on any other phone, the assert command and mount command in updater script needs to be changed to suit... the rest should be pretty universal.
Is this something like Titanium Backup.apk but in zip format?
No I made this just for synergy for backing up the special configuration files for some of the special tools i'm that ROM, like inadyn and dropbear. Also any special themed files, my fonts..
Basically, catching any system files that titanium and other apps don't get.
Sent from my PG86100 using XDA App
Hi, I've gathered some resources for creating my Touchwiz 4.0 rom but I need to know how to make a flashable zip from a nandroid backup of /system.
How would I do this?
Another question while I'm here.. I get this error when using kitchen: Imgur Link , any suggestions?
DamnTarget said:
Hi, I've gathered some resources for creating my Touchwiz 4.0 rom but I need to know how to make a flashable zip from a nandroid backup of /system.
How would I do this?
Another question while I'm here.. I get this error when using kitchen: Imgur Link , any suggestions?
Click to expand...
Click to collapse
You don't need nandroid backup
Just need /system partition
Connect your device to PC
Go to platform-tools folders where you have installed adb.
Make a folder system in this folder.
Open Command Prompt in that folder and type
Code:
adb pull /system system
It will take some time.
When it's completed. What you have to do is replace the system folder in any ROMs flashable zip and modify it's updater-script to suit your needs
Thanks for taking the time to answer my question!
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
Remember: Backup first! Be rooted! Have busybox installed! (We will create a recovery flashable zip which updater-script uses busybox commands)
To deodex your current device state follow the steps below:
Make sure you have adb and your device drivers installed on your computer (how to: installing and using adb).
Open command line and pull /system/app, /system/priv-app and /system/framework from phone via adb to your computer.
Code:
adb pull /system/app app
adb pull /system/priv-app priv-app
adb pull /system/framework framework
This will generate the folders "app", "priv-app" and "framework" containing the pulled files in the current directory.
Generate a list containing the folders with "arm"-folders which have to be deleted later in the phone (not the "lib/arm"-folders!!). Do this by opening terminal and navigate to the folder containing your previously pulled folders "app", "priv-app" and "framework" and type
Code:
dir /s /a:d /b arm | find /v "\lib\arm" > loglist.txt
There now should be a textfile containing all paths to the "arm"-folders. We'll need it later...but the textfile should look like:
Code:
<Directory you pulled your files to>\priv-app\3DTourViewer_HD_M2\arm
<Directory you pulled your files to>\priv-app\BackupRestoreConfirmation\arm
<Directory you pulled your files to>\priv-app\CloudAgent\arm
<Directory you pulled your files to>\priv-app\CSC\arm
....
Install Java (if you don't already have) and de-odex the pulled files with this tool.
Put the deodexed files into the folders /system/app, /system/priv-app and /system/framework in the attached zip.
Edit the zips' updater-script (META-INF\com\google\android\updater-script) according to the previously generated folder list. Take the textfile generated in 3. and replace
all \ with /
the path <Directory you pulled your files to> (see above example) in the textfile with "/system
It then should look like:
Code:
"/system/priv-app/3DTourViewer_HD_M2/arm
"/system/priv-app/BackupRestoreConfirmation/arm
"/system/priv-app/CloudAgent/arm
"/system/priv-app/CSC/arm
....
Then replace line end characters with ", (remember to remove the very last comma in the line or to insert a very last " in the line in case the last line doesn't contain line end character(s)) to get a comma-separated list of your folders:
Code:
"/system/priv-app/3DTourViewer_HD_M2/arm","...","/system/priv-app/BackupRestoreConfirmation/arm"
Modify the 'delete-recursive' entries in the updater-script according to your list and save it (do neither modify the encoding of the file nor the line end characters! Has to be "LF"! )
Boot into recovery.
Clear cache and dalvik-cache.
Flash zip.
Reboot (in my case it took some minutes).
I recommend using Notepad++ as editor because it's easy to use and much more powerful than standard windows editor.
reserved
SHA_NDY said:
Ok, I finally managed to do it.
If anyone is interested in how it worked I can try to provide my way to success ...
Remember: Backup first! Be rooted! Have busybox installed!
Make sure you have adb and device drivers installed on your computer.
Pull /system/app, /system/priv-app and /system/framework from phone via adb to your computer.
Code:
adb pull /system/app app
adb pull /system/priv-app priv-app
adb pull /system/framework framework
This will generate the folders "app", "priv-app" and "framework" containing the pulled files in the current directory.
Generate a list containing the folders with "arm"-folders which have to be deleted later in the phone. Do this by opening terminal and navigate to the folder containing your previously pulled folders "app", "priv-app" and "framework" and type
Code:
dir /s /a:d /b arm | find /v "\lib\arm" > loglist.txt
There now should be a textfile containing all paths to the "arm"-folders. We'll need it later...but the textfile should look like:
Code:
<Directory you pulled your files to>\priv-app\3DTourViewer_HD_M2\arm
<Directory you pulled your files to>\priv-app\BackupRestoreConfirmation\arm
<Directory you pulled your files to>\priv-app\CloudAgent\arm
<Directory you pulled your files to>\priv-app\CSC\arm
....
Install Java (if you don't already have) and de-odex the pulled files with this tool.
Put the deodexed files into the folders /system/app, /system/priv-app and /system/framework in the attached zip.
Edit the zips' updater-script (META-INF\com\google\android\updater-script) according to the previously generated folder list. Take the textfile generated in 3. and replace
all '\' with '/'
the path '<Directory you pulled your files to>' (see above example) in the textfile with '/system'
'/arm' with '/arm"'
Line end characters with ','
to get a comma-separated list of your folders. Modify the 'delete-recursive' entries according to your list and save the updater-script (do not modify the encoding of the file)
Boot into recovery.
Clear cache and dalvik-cache.
Flash zip.
Reboot.
Attached: the zip-file body which has to be edited as you need it...do not touch the permission settings in the updater-script...
Click to expand...
Click to collapse
One question , have you use twrp 2.8.1.1 ?
Inviato dal mio SM-G850F utilizzando Tapatalk
belthazor86 said:
One question , have you use twrp 2.8.1.1 ?
Click to expand...
Click to collapse
Yes, I used TWRP 2.8.1.1
I'm not sure but perhaps it will also work flashing with Flashify app.
Ok,now I can do it again. In this time i have modified the file updater-script with information of my textfile
Inviato dal mio SM-G850F utilizzando Tapatalk
Nothing,bootloop again..I give up. Nothing Xposed for me
Inviato dal mio SM-G850F utilizzando Tapatalk
The bootloop problem was a LF replaced by CRLF in the edited updater-script...
I followed your guide and everything went well. No bootloop.
But I got some popup notifications that google services and some google related stuff has stopped so I can not finish the initial setup.
Any clue what went wrong?
I assume your downloadable deodexed france 5.0.2 is for galaxy G850F ... Flashed it ... Bootloop ...
zalood said:
I followed your guide and everything went well. No bootloop.
But I got some popup notifications that google services and some google related stuff has stopped so I can not finish the initial setup.
Any clue what went wrong?
Click to expand...
Click to collapse
Hey zalood,
I only moved through all the steps described in the guide after initial setup was done. I'm not sure if there are files/libs/preferences missing before setup is complete.
zalood said:
I assume your downloadable deodexed france 5.0.2 is for galaxy G850F ... Flashed it ... Bootloop ...
Click to expand...
Click to collapse
This zip is for deodexing a stock state france 5.0.2 ROM, not the ROM itself. Same for russian zip...
I hope this was helpful.
SHA_NDY said:
Hey zalood,
I only moved through all the steps described in the guide after initial setup was done. I'm not sure if there are files/libs/preferences missing before setup is complete.
This zip is for deodexing a stock state france 5.0.2 ROM, not the ROM itself. Same for russian zip...
I hope this was helpful.
Click to expand...
Click to collapse
Thanks SHA_NDY.
Perhaps I was also wiping the data instead cache and dalvik only.
Will try again in the morning and revert back ...
Deodexing and flashing successful . . .
Thanks a lot for this Guide . .
first of all thank you, for this guide :good:
when I try to install it TWRP says "E: Error executing updater binary in zip ' /sdcard....", but i don´t touched the updater-binary file.
can someone give me an advice ?
albert-319 said:
first of all thank you, for this guide :good:
when I try to install it TWRP says "E: Error executing updater binary in zip ' /sdcard....", but i don´t touched the updater-binary file.
can someone give me an advice ?
Click to expand...
Click to collapse
Which TWRP version do you use? I use 2.8.1.1 and everything works perfect.
If you don't succeed in flashing with e.g. other TWRP version you can take a zip (something you already flashed) that you know to work with your TWRP version. Delete everything in the zip EXCEPT the updater-binary and place the files you deodexed into the zip (keep the folder structure according to the attached zip in this thread) and place your updater script.
Do you have busybox installed?
Hi, just flashed stock russian firmware, set up google account and etc, flashed twrp 2.8.1.1. then russian zip to deodex but stuck on android logo, do I have to update gapps after setting account and then flash deodex zip?
diego1810 said:
Hi, just flashed stock russian firmware, set up google account and etc, flashed twrp 2.8.1.1. then russian zip to deodex but stuck on android logo, do I have to update gapps after setting account and then flash deodex zip?
Click to expand...
Click to collapse
I'm not sure if I did so to get it working. I think I remove the zip files, everyone should do like described in the tuto, don't know what side-effects do occur...sorry
Dear SHA_NDY,
So I followed all the steps in your tutorial.
So what I did was unzipped the zip file that you had attached, and then updated the directories with the deodexed files and updated the updater script as well. I then zipped the file back up and tried to flash it but it wouldnt flash for me.
What am I doing wrong?
Thank you
harper86 said:
Dear SHA_NDY,
So I followed all the steps in your tutorial.
So what I did was unzipped the zip file that you had attached, and then updated the directories with the deodexed files and updated the updater script as well. I then zipped the file back up and tried to flash it but it wouldnt flash for me.
What am I doing wrong?
Thank you
Click to expand...
Click to collapse
Can you provide your zip for download? Thanks
SHA_NDY said:
Can you provide your zip for download? Thanks
Click to expand...
Click to collapse
Hi Shandy. Fixed it. What I did was just flashed arter97 deodex system image file via ODIN and works pretty well now. Just had to re root after that.
Thank you
Then replace line end characters with ", (remember to remove the very last comma in the line) to get a comma-separated list of your folders:
Code:
"/system/priv-app/3DTourViewer_HD_M2/arm","...","/system/priv-app/BackupRestoreConfirmation/arm"
Modify the 'delete-recursive' entries in the updater-script according to your list and save it (do neither modify the encoding of the file nor the line end characters! Has to be "LF"! )
Click to expand...
Click to collapse
Im trying so much but dont get this part.
At the monent i am here now
"/system/priv-app/3DTourViewer_HD_M2/arm
"/system/priv-app/BackupRestoreConfirmation/arm
"/system/priv-app/CloudAgent/arm
"/system/priv-app/CSC/arm
....
Click to expand...
Click to collapse
@SHA_NDY maybe you can explain it a little more?
maybe in german?
ManuFisch said:
Im trying so much but dont get this part.
At the monent i am here now
@SHA_NDY maybe you can explain it a little more?
maybe in german?
Click to expand...
Click to collapse
I'll give it a try but don't recall any German from childhood .
If you're using notepad++ or notetab pro, then you can do a replace using regular expressions, so put your cursor at the top of the doc and for the "find" field, use this [\r\n]+ and click on 'use regular expressions' if it's there, (which is carriage return line feed, which is at the end (invisible) of each line). In the replace field, put ", (exactly), and then replace-all. If the entire document is now a single line, then it's good. Probably you have to remove the last comma manually.
So now you've edited your .txt file that you created in the OP steps, so now open the updater-script file in the .zip. There are 3 "delete-recursive" sections like delete-recursive("... "), one for apps, one for priv-apps and one for framework, so copy the first batch of modified text from the .txt file that are "apps" (up till the framework one), and paste them over the entire innards of the ("...") clause of the delete-recursive. Same for framework (only one entry), and same for priv-apps.
I'm just writing from memory so maybe I mispelled something. ANyway, when you're completed, make sure to overwrite updater-script in the .zip and you should be ready to either mess up your phone (back it up!) or make it xposed compat.
cheers.
Hi,
I have a T-Mobile S5 and I'd like to get a link to the stock ROM with latest security upgrades so that I can debloat and mod it.
Can anyone point me to some resources on how to debloat and create a custom ROM.
Is it possible to use the international ROM and flash it on the T-Mobile S5?
Thanks
1) Download the ROM
Download from sammobile.com (look for G900T, latest should be ~April 2017)
You'll need to make an account (free), and it's pretty slow, but there isn't really an option.
You might be able to grab the international version, but I haven't tried. I heard it's not compatible with some of the US locked versions, but the T-Mobile and AT&T versions were supposed to be exactly the same so they shouldn't have a problem. Also, it probably won't come with Wifi Calling.
2) Extract zip with `unzip` and then, extract the .tar.md5 with `tar -xf`
3) Download sgs2ext4.zip (google it:
forum.xda-developers.com/attachment.php?attachmentid=645192) and extract it
4) Run `java -jar sgs2ext4.jar system.ext4.img system.img` (and then do the same for cache).
5) Mount both images (`mount -o loop system.img system/` and same for cache).
6) Get `sec_csc.zip` from the cache folder and extract it.
7) Make a copy of the system/ mounted folder, chown it to yourself so that you can easily modify it later on.
8) Merge system/ folder from extracted sec_csc.zip with the system/ folder you created.
9) Copy boot.img and system/ into a new folder, let's call it build/
10) Get a copy of META-INF (update-binary is the important one) and also place it in build/
11) Use the updater-script from here: https://forum.xda-developers.com/tm...pment/odexed-development-starter-kit-t3386186 and delete everything between "Symlinking and Setting Permissions" to show_progress (aka get rid of all of the set_metadatas).
12) Generate appropriate permissions (as described here: https://forum.xda-developers.com/tm...pment/odexed-development-starter-kit-t3386186) and place them right after "Symlinking and Setting Permissions".
13) At this point, you should be able to zip everything up and install on your phone. This is a fresh full ROM with no mods and all the bloat.
14) Delete and don't forget to also remove set_metadatas that correspond to whatever you deleted or else the updater will complain that something might have failed. My old post (again: https://forum.xda-developers.com/tm...pment/odexed-development-starter-kit-t3386186) also describes a couple of simple mods you're likely to make.
Note that if you disable selinux, you might not have to deal with permissions, but I think you have to modify boot.img for that, and I don't know how to do that. (Aside: Almost all ROMs posted not by me on this forum have selinux disabled. EG: if you install them, on every boot, it will say something about kernel not being selinux enforcing.) If you need more advanced modding, you'll need to deodex. I don't know how to do that and have never needed to. You'll have to look somewhere else for guides for that.