[GUIDE][Noobs]How to Create your own stock based XPERIA ROM

[GUIDE][Noobs]How to Create your own stock based XPERIA ROM - Android Software Development

Hey Guys,
My name is Braa, I’am just a new developer here in the XDA and today I’am going to show you a complete guide on how to make your own “XPERIA” Stock Based ROM.
First of all you have to get the Stock XPERIA Firmware of your device
Let’s get started to build our ROM:
First Step: (Getting the STOCK FTF File of your Device)
1) Get the latest stock FTF Firmware of your device
{
"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"
}
2) Open it using 7-ZIP
3) Now we will be focusing on the most important file “system.sin” Just Extract it to your desktop
4)Now go to the XPERIA Flashtool  Tools  Sin Editor   Choose the system.sin file you have just extracted to your desktop Extract Data
5)Now you will have a file called “system.ext4”
6)Get a tool called “EXT4 Unpacker” then select that file  Extract all the files into a folder
Congrlatiouns you have got your stock device firmware but not in the form of “FTF” instead in the form of “ZIP”
But this was not everything we will now move into more advanced part but don’t panic everything will be explained easily with screenshots so, Let’s GO !
Understanding the System folder you have just extracted
System Folder Contains the Majority of ROM Files, now we have to explain the SYSTEM Folder structure
1. app : contain all the system's app and the odex file of system app
2. bin : contain the command and bin files for the rom
3. vendor: specified vendor system. you have your specific vendor's app, libs, and config files here also contains the Themes (XPERIA 2011-2012 Devices)
4. etc : additional setting and files for the ROM.
5. font : It’s Clear it contains the fonts
6. framework : system's framework files and the odex file for framework
7. lib : drivers, modules, kernel related files for the rom
8. media: media files-ringtones, notification, bootanimation.
10. usr : files needed for keyboard, bluetooth, etc.
11. xbin : additional command and bin files (busybox is usually installed here)
12. build.prop file : Contains your Device default properties
Q)DEODEX VS ODEX
A)Most of custom rom available is deodexed rom while our stock rom is half deodexed rom. I'll try to explain it in most simple way. First of all, we should understand that mostly every app in android consist of three part, *apk files, *dex/odex files, and lib files.
ODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in same folder with the apk files (/system/app). the positive side, it consume less internal memory and a execute faster. the negative side, it makes the app uncostumizable (cannot apply custom themes) and need more space in system partition.
DEODEXED rom means that *dex file needed to run the app is extracted from the apk file and placed in /data/dalvik-cache. the positive side, the app can be themed (full customizable) and consume less system partition. we could put more app in /system/app in deodexed rom. the negative side, it consume a lot of internal memory. please be cautious with the internal memory space if you use deodexed rom. (NOTE: if you start from stock rom, you may use Kitchen to convert odexed to deodexed rom).
Now if you want a really looking good Ui ROM u will stick into DeOdexing your ROM
Note: What was explained above in the part of ODEX VS DEODEX doesn’t mean that DeOdexing ROM will decrease it’s Performance
Q)How to DeOdex My ROM ?
A)Bro, This could be done using many tools like (Universal DeOdexer or DsiXda Kitchen)
Now I will explain the Dsixda kitchen method
Tools Needed:
Cygwin
JDK
Android Kitchen
Steps:
1)Extract Cygwin.zip  Run Setup.exe  Next  Install from local directory  Set the root directory as it  Set the local package directory as cygwin_packages  Select that reload icon and install all
2)Now Click on Cygwin icon on desktop you will see that commands appear automaticly
3)Now Extract the kitchen Android-Kitchen-0.224.zip then rename it to “kitchen” (without the quotations)
4)Then copy that folder into c:/Cygwin  home  your username folder
5)Open the cygwin and write these commnds
6)Cd kitchen  ./menu
7) Just compress the system folder we have just extracted from the ext4 unpacker into ZIP File
8)Now copy that file to C:\cygwin\home\Your username\kitchen\original_update
9)Open the cygwin  then write the kitchen commands I’ve mentioned above
10)Select “Set up working folder of your ROM”  Press Enter  Select the zip you compressed  It will ask you to add a null boot.img agree to this
11)Select the “Advanced Options”  Select De-Odex files in your ROM  Select “b” DeOdex both folders (Recommended) wait till the process finishes
Updater Script ! (Nightmare to a lot of noobs)
Sorry Guys I can’t help you with this part  even my updater-script in my ROM I forgot how I did it here is it you can base your updater-script on it
Just download it !
WE’VE Done this part !
Modifying your ROM
1)Adding Tweaks
1.1)Adding init.d Support
Adding init.d support means that you can run your favorite scripts and tweaks on your Stock Based ROM
Download the file “enable_init.d.zip” and put all its files inside system folder into your ROM System Folder
1.2)Modifying Build.Prop for more stability
Here’s a lot of Build.prop Tweaks
1. Force launcher into memory
ro.HOME_APP_ADJ=1
2. Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
3. VM Heapsize; higher RAM, higher hp can be
dalvik.vm.heapsize=48m
4. Render UI with GPU
debug.sf.hw=1
5. Decrease dialing out delay
ro.telephony.call_ring.delay=0
6. Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
7. Save battery
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
8. Disable debugging notify icon on statusbar
persist.adb.notify=0
9. Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
10. Raise photo and video recording quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
11. Signal (3G) tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
12. Net speed tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
13. Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
14. Fix some application issues
ro.kernel.android.checkjni=0
15. Phone will not wake up from hitting volume rocker
ro.config.hwfeature_wakeupkey=0
16. Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
17. Disable boot animation for faster boot
debug.sf.nobootanimation=1
18. Miscellaneous flags
ro.config.hw_menu_unlockscreen=false
persist.sys.use_di ring=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
Q)How can I add these lines to my build.prop
A)I will tell you
Download a tool called “Notepad++”
Extract the build.prop file from your ROM then right click on it then edit with notepad++
Go to Last line:
Then add
# Tweak Name
Tweak Properties
#
Done
Here’s my build.prop I used in my ROM: its just a sample copy what you want from it
2)Bravia Engine 2 with X-Reality
Download the file of BE-2 then paste it in your ROM then add these lines to build.prop
# X-Reality Engine
ro.service.swiqi2.supported = true
persist.service.swiqi2.enable = 1
#
ro.service.swiqi3.supported = true
persist.service.swiqi3.enable = 1
#
3) Modifying the wallpapers of the ROM
Go to etc\customization\content\com\sonyericsson\wallpaperpicker\wallpapers
Then Add your Wallpapers
4) Modifying the Themes
system\vendor\overlay\framework
Themes are found here
In newer XPERIA Devices Themes are found in /app
5) Adding Supercharger intiries
Just add these lines to your build.prop
# V6 SuperCharger, OOM Grouping & Priority Fixes created by zeppelinrox.
# DO NOT DELETE COMMENTS. DELETING COMMENTS WILL BREAK UNINSTALL ROUTINE!
# BEGIN OOM_MEM_Settings
ro.FOREGROUND_APP_MEM=1536
ro.VISIBLE_APP_MEM=3072
ro.PERCEPTIBLE_APP_MEM=4096
ro.HEAVY_WEIGHT_APP_MEM=20480
ro.SECONDARY_SERVER_MEM=8192
ro.BACKUP_APP_MEM=14080
ro.HOME_APP_MEM=1024
ro.HIDDEN_APP_MEM=10240
ro.EMPTY_APP_MEM=15360
# END OOM_MEM_Settings
# BEGIN OOM_ADJ_Settings
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=3
ro.PERCEPTIBLE_APP_ADJ=3
ro.HEAVY_WEIGHT_APP_ADJ=5
ro.SECONDARY_SERVER_ADJ=7
ro.BACKUP_APP_ADJ=6
ro.HOME_APP_ADJ=1
ro.HIDDEN_APP_MIN_ADJ=12
ro.EMPTY_APP_ADJ=15
# END OOM_ADJ_Settings
# End of V6 SuperCharged Entries
6) Making your Apptray Transparent
Just Replace the apptray_pane_bg.9.png I provided to your Home.apk in store mode
7) Changing the bootanimation (HDPI)
XPERIA Z1
XPERIA Z2
8) Media not scanned or No pictures found here’s the solution
Download Rescan media root and put it in data folder of your ROM
If you are on 4.1.2 and HDPI Device (Maybe works on XHDPI or MDPI)
So my ROM “Doomsday” is open source for you, it contains full XPERIA Z2 Ui just take the download link from my signature then download it and take what you need from it but don’t forget to give me the proper credits and press thanks for me
Thread will be updated soon :laugh:

Downloads
My Personal ROM Updater-script
My Build.prop
[URL="http://d-h.st/j59"]Doomsday ROM[/URL]
EXT4 Unpacker
X-Reality and BE-2
apptray_pane_bg.9
XPERIA Z1 Bootanimation (HDPI)
XPERIA Z2 Bootanimation (HDPI)
Init.d Support

Why it says, Installation aborted.. I tried 3,4 times to make installation from custom rom. file... but unable to flash by using that rom the ROM.
Error shows this image in background.. (Can not make ScreenShot)

@Eliminator79 ho did you made a working custom rom from the above tutorial?
I have created 15-20 custom rom in different ways from different tutorials from xda, mostly it stops installation with an error. 4-5 times it started phone just for showing start animation ...
I quit....
Right now Installed stock rom back. after wasting 2 days..

Might be an updater-script
aatifaneeq said:
@Eliminator79 ho did you made a working custom rom from the above tutorial?
I have created 15-20 custom rom in different ways from different tutorials from xda, mostly it stops installation with an error. 4-5 times it started phone just for showing start animation ...
I quit....
Right now Installed stock rom back. after wasting 2 days..
Click to expand...
Click to collapse
Might be an updater-script problem
What's the error that comes during installation ?
Status 7 or Status 6 :good:

no status..
it just says
installation abort..

this time is says , aborted status (0)
View attachment 2893076
Here is the updater script code
Code:
show_progress(0.1, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("debuggerd", "/system/bin/csview");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/chcon");
symlink("toolbox", "/system/bin/setenforce");
symlink("toolbox", "/system/bin/grep");
symlink("toolbox", "/system/bin/runcon");
symlink("toolbox", "/system/bin/touchinput");
symlink("toolbox", "/system/bin/getsebool");
symlink("toolbox", "/system/bin/setsebool");
symlink("toolbox", "/system/bin/restorecon");
symlink("toolbox", "/system/bin/getenforce");
symlink("toolbox", "/system/bin/load_policy");
symlink("toolbox", "/system/bin/cp");
symlink("toolbox", "/system/bin/playback");
symlink("toolbox", "/system/bin/du");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm(0, 2000, 0755, "/system/vendor/lib/hw");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
show_progress(0.1, 10);
show_progress(0.2, 0);
show_progress(0.2, 10);
unmount("/system");

Also replaced, updater script with yours 1, stil same error..

aatifaneeq said:
this time is says , aborted status (0)
View attachment 2893076
Here is the updater script code
Code:
show_progress(0.1, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("debuggerd", "/system/bin/csview");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/chcon");
symlink("toolbox", "/system/bin/setenforce");
symlink("toolbox", "/system/bin/grep");
symlink("toolbox", "/system/bin/runcon");
symlink("toolbox", "/system/bin/touchinput");
symlink("toolbox", "/system/bin/getsebool");
symlink("toolbox", "/system/bin/setsebool");
symlink("toolbox", "/system/bin/restorecon");
symlink("toolbox", "/system/bin/getenforce");
symlink("toolbox", "/system/bin/load_policy");
symlink("toolbox", "/system/bin/cp");
symlink("toolbox", "/system/bin/playback");
symlink("toolbox", "/system/bin/du");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm(0, 2000, 0755, "/system/vendor/lib/hw");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
show_progress(0.1, 10);
show_progress(0.2, 0);
show_progress(0.2, 10);
unmount("/system");
Click to expand...
Click to collapse
you should set correct code partition in your update script
i mean this lines:
format("MTD", "system");
mount("MTD", "system", "/system");
you can find this lines in another custom roms which correct work on your phone.
just find this lines in that custom rom ( in meta inf folder in that custom rom ) then copy that lines and replace that in your update script
if your custom rom has a kernel , you should find the partition of kernel at the end of update script and replace in end of your update script
finally replace the update binary in that custom rom which correct work on your rom with your update binary.
do this work at the end of your work.means make your rom first then do this work with your rom.zip file
hope can help you

I have also used the working update script downloaded from Eliminator79's 2nd post... but still displaying same error..

Maybe works
aatifaneeq said:
I have also used the working update script downloaded from Eliminator79's 2nd post... but still displaying same error..
Click to expand...
Click to collapse
Replace the whole META-INF folder of your ROM with mine
Strongly will work :good:

Also did this too..also replaced with few other Xperia J roms, not worked. even replaced only apps folder. but in vain..

aatifaneeq said:
I have also used the working update script downloaded from Eliminator79's 2nd post... but still displaying same error..
Click to expand...
Click to collapse
NO bro
just used update binary from another rom which work correct on your phone
but about update script just edit 2 lines that i told you before
find it in update script for another custom rom for your phone and replace with your update script ( just 2 lines )
of course when you build your rom then do this

Thanks for the reply.
I already did this too. but it only shows boot animation , i have waited 10-12 minutes but nothing changed... same story all the time

aatifaneeq said:
Thanks for the reply.
I already did this too. but it only shows boot animation , i have waited 10-12 minutes but nothing changed... same story all the time
Click to expand...
Click to collapse
Give me the META-INF from your custom rom ( which you made it ) and META-INF from other custom roms which correct work on your phone

hamidreza2010 said:
Give me the META-INF from your custom rom ( which you made it ) and META-INF from other custom roms which correct work on your phone
Click to expand...
Click to collapse
Bro, thanks for the reply..
Here are both META-INF folders, both are not working when i replace (delete and paste all new files) system folder.
P.S. Installation only works when i modify app files from Doomsday ROM Jlo v5 ROM, But i also want to change all other system folders, not only app folder.

aatifaneeq said:
Bro, thanks for the reply..
Here are both META-INF folders, both are not working when i replace (delete and paste all new files) system folder.
P.S. Installation only works when i modify app files from Doomsday ROM Jlo v5 ROM, But i also want to change all other system folders, not only app folder.
Click to expand...
Click to collapse
ok just 2 thing:
1- Your roms has custom kernel ?
2- Give me META-INF folders from another normal custom rom not aroma

hamidreza2010 said:
ok just 2 thing:
1- Your roms has custom kernel ?
2- Give me META-INF folders from another normal custom rom not aroma
Click to expand...
Click to collapse
i do not have any other meta inf :|
Well, i found a rom, and using it as base, where i have replaced app, framework folder and installation worked and Phone is working fine.. But when i replace complete system directory, it stopped on boot screen..
about kernal, i am using stock kernal.sin
here is the meta inf that worked only with app/framework folder

thanks dude
Great TUT :highfive: :good: :victory:
Now I get my ROM installed ok
But BIGGEST PROBLEM I FACE! On Rebooting it stucks on splash screen and then it reboots! :'(
Check my updater script!
Help me someone please :'( Been working a lot but this sh*t doesn't resolves!
I use Xperia SP and this is my whole META-INF Folder
Thanks in advance. Anyone who can help me
Meta INF download below :

Tech N You said:
thanks dude
Great TUT :highfive: :good: :victory:
Now I get my ROM installed ok
But BIGGEST PROBLEM I FACE! On Rebooting it stucks on splash screen and then it reboots! :'(
Check my updater script!
Help me someone please :'( Been working a lot but this sh*t doesn't resolves!
I use Xperia SP and this is my whole META-INF Folder
Thanks in advance. Anyone who can help me
Meta INF download below :
Click to expand...
Click to collapse
Probably one of these
1)Framework issue (Both .jar & -res.apk)
2)Modified Wrongly Build.prop
3)Permissions are set wrongly
4)/lib problems
Just check and let me know

Related

[HOWTO] Build your own rom for GT-I8190(golden) with dsixda's Android Kitchen

...here is my "HOWTO" build your own stocked based rom for GT-I8190(golden) - "all versions" ...
...this Guide is written with the following basic set up: "Microsoft Windows 8 pro 64bit - cygwin 2.774"
preparation & requirements:
- patience ....
- a working and updated dsixda's Android Kitchen version http://forum.xda-developers.com/showthread.php?t=633246
+ this tools.zip (unzip it and copy it into your /kitchen/tools folder)
- a original Samsung firmware (golden) .tar.md5
example: HOME_I8190XXAMD3_I8190OXAAMD3_1154865_REV00_user_low_ship.tar
- 7-zip 9.20
1. unpack the "firmware.tar.md5" with 7.zip
2. inside extracted folder you find boot.img, cache.img, hidden.img, modem.bin, STE_boot1.img, STE_boot2.img and system.img
3. now select boot.img & system.img and pack a new .zip file with 7.zip
4. copy the new .zip file into your /kitchen/original_update folder
5. now start dsixda's Android Kitchen...."MAIN MENU"
5.1 extract sec_csc.zip - go to "0 - ADVANCED OPTIONS" ---> "18 - Plugin scripts" ---> "(3) Extract_SGS2_CSC_from_cache.img"
5.2 after extracting "sec_csc.zip" unpack it with 7.zip ...
6. now go back to "MAIN MENU" & "Set up working folder from ROM"
7. after extracting system.img copy the "system" folder from "sec_csc.zip" into your "workingXXXXX/system" folder .
8. now go back to "MAIN MENU" & go to "8 - Show working folder information"
it schould look like this:
Code:
Android OS version : 4.1.2
Device : golden
Model : GT-I8190
ROM Name : JZO54K.I8190XXAMD3
CSC version : I8190OXAAMD3
Rooted (Superuser app + su) : No
Rooted (unsecured boot.img) : No
BusyBox installed : No
BusyBox run-parts support : No
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : No
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
9. now you can make your changes like "root" "busybox" etc...
10. ... when you have done all your changes go back to "MAIN-MENU" and follow this:
"99 - Build ROM from working folder"
Code:
Select a build option:
1 = Interactive Mode - recommended for most users
(Guide me through the build)
2 = Lazy Mode - trust the kitchen to do everything without asking
(Zipalign, Edify, sign ROM, auto-name ZIP)
3 = Express Mode - for advanced users
(Zipalign, Edify, don't sign ROM, auto-name ZIP)
4 = Extreme Mode - for advanced users
(No zipalign, no script conversion, don't sign ROM, auto-name ZIP)
5 = Cancel - Don't build now
==========================================================================
[COLOR="Red"]Number (default: 1): 1[/COLOR]
Would you like to optimize the APK files by zipaligning them (y/n)? (default: y):[COLOR="Red"] n[/COLOR]
NOTE: This device (golden) requires an updater-script
--------------------------------------------------------------------------
Converting to updater-script, please wait ...
- Initial formatting ...
- copy_dir ...
- set_perm_recursive ...
- set_perm ...
- run_program ...
- package_extract_file ...
- show_progress ...
- set_progress ...
- sleep ...
- delete/delete_recursive ...
- symlink ...
- write_raw_image ...
- format and mount ...
- unmount ...
- Final formatting ...
Device name in kitchen, or variant of: golden
Please ensure these device mount statements are correct:
--------------------------------------------------------------------------
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
--------------------------------------------------------------------------
Copying update-binary ...
„../../../../../tools/update_files/emmc-update-binary“ -> „update-binary“
--------------------------------------------------------------------------
An updater-script has been created under META-INF/com/google/android of
your working folder. Please review it and make any necessary changes. An
update-binary has also been added.
DO NOT delete any of the files under META-INF/com/google/android.
Proceed with the change (y/n)?
y = Proceed; updater-script and update-binary will be used in the ZIP
file; update-script will remain in working folder.
n = Cancel; updater-script and update-binary will be deleted and not
used.
? [COLOR="Red"](default: y): y[/COLOR]
Making update.zip ...
update.zip created
It is recommended that you sign your ROM.
Sign it (y/n)? (default: y): y
Signing update.zip ...
The new ROM will be named golden_signed_050613_162708.zip
Change the name (y/n)?[COLOR="Red"] (default: n): n[/COLOR]
Found OUTPUT_ZIP folder
==========================================================================
Congratulations ...
...copy it to your sdcard and flash it with cwm recovery

....updater-script examble:
Code:
show_progress(0.1, 0);
format("ext4", "EMMC", "/dev/block/mmcblk0p22");
mount("ext4", "EMMC", "/dev/block/mmcblk0p22", "/system");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("debuggerd", "/system/bin/csview");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/touch");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
show_progress(0.1, 10);
show_progress(0.2, 0);
package_extract_file("boot.img", "/dev/block/mmcblk0p20");
show_progress(0.2, 10);
unmount("/system");
modem.bin (baseband) update .zip:
updater-script:
Code:
show_progress(0.100000, 0);
ui_print("GT-I8190 modem.bin update");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
show_progress(0.100000, 50);
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p16"),
delete("/tmp/modem.bin"));
show_progress(0.100000, 100);
ui_print("Done");
example .zip (XXAMD3):
View attachment GT-I8190_modem.bin-update.zip

thank you for this
it is a huge huge help

Thanks alot. I got it working with your previous instructions from earlier help in the other thread, but how do we flash "modem.bin" for baseband updates?
Any idea if it can be done with kitchen or do we still have to do it with odin?

tys0n said:
Thanks alot. I got it working with your previous instructions from earlier help in the other thread, but how do we flash "modem.bin" for baseband updates?
Any idea if it can be done with kitchen or do we still have to do it with odin?
Click to expand...
Click to collapse
added @ 2nd post

Thanks enox, this is great!

Hi! Thanks for this tutorial :good: But I have one big problem :/ Everything goes good, but after flash it kill my phone Luckily I brink back it for live.
I have one question. I set option "ROM will wipe all data" and I think that this bricks my phone. Is sufficient remove "format("ext4", "EMMC", "/dev/block/mmcblk0p25");" from "updater-script" or will be better build whole ROM again without option for wipe data?
Btw, I think that I am not first one who had this problem and maybe it will be good to write in first post that wiping ROM will brick your phone
I found how to fix it here. After flash stock recovery and stock fw i had to go to stock recovery and wipe data and cache.

Hi enox, any chance of a re-up of the tools.zip? link seems to be down atm, thanks.
[EDIT] Must have been something wrong with the site, the link works again now, cheers.

xenex1 said:
Hi enox, any chance of a re-up of the tools.zip? link seems to be down atm, thanks.
Click to expand...
Click to collapse
the download link works .... just try it again...

enox.co said:
the download link works .... just try it again...
Click to expand...
Click to collapse
It does indeed, just downloaded it thanks. :good:

nice
two questions:
how can i root a original firmware with this tutorial ... i mean that the created custom firmware is a rooted firmware? bt: is my root is lost when I flash the created rom?

hurricane2012 said:
two questions:
how can i root a original firmware with this tutorial ... i mean that the created custom firmware is a rooted firmware? bt: is my root is lost when I flash the created rom?
Click to expand...
Click to collapse
this tutorial is on to build your own rom using kitchen
concerning the how to root your custom rom
refer to other tutorials on dsizda's Anrdoid kitchen found on XDA forums
if you have gotten Kitchen running you will see option 2 is "Add root permissions"
this will add root to your custom ROM

Thanks

hurricane2012 said:
Thanks
Click to expand...
Click to collapse
no problem
just be sure to check your updater-script when prompted to do so
you may need to make corrections to it

The created rom works ... but i have no phone signal and wifi ... why? i use HOME_I8190XXAMD3_I8190OXAAMD3_1154865_REV00_user_low_ship.tar following all steps from post #1 - set root and busy box ... no more! after flashing all thinks work - but no phone signal and no wifi

hurricane2012 said:
The created rom works ... but i have no phone signal and wifi ... why? i use HOME_I8190XXAMD3_I8190OXAAMD3_1154865_REV00_user_low_ship.tar following all steps from post #1 - set root and busy box ... no more! after flashing all thinks work - but no phone signal and no wifi
Click to expand...
Click to collapse
you should flash from post #2
example .zip (XXAMD3):
GT-I8190_modem.bin-update.zip

Doesnt work for me Baseband unknown ... Wifi cant connect

hurricane2012 said:
Doesnt work for me Baseband unknown ... Wifi cant connect
Click to expand...
Click to collapse
... if you have done all steps .... it should work ....

enox.co said:
... if you have done all steps .... it should work ....
Click to expand...
Click to collapse
no ... doesnt work ... i have do all steps ... but after flash my own rom phone and wifi dont work ... i have no idea why ... which original rom do you use exactly? where do I get this rom?

hurricane2012 said:
no ... doent work ... i have do all steps ... but after flash my own rom phone and wifi dont work ... i havy no idea why ... which original rom do you use exactly? where do I get this rom?
Click to expand...
Click to collapse
http://hotfile.com/dl/211675727/04f...-GT-I8190-DBT-I8190XXAMD3-1366526389.zip.html
...

Updater-script problems

hello all ive been working on my rom but i cant get it working in recovery it says the binary couldnt be read correctly, attached is my working folder zip from kitchen please help look into it i cant figure it out

Rename update-binary.orig to update-binary. That might be the issue mate!

Could you help me to check this problem? Thank you very much!
http://forum.xda-developers.com/showthread.php?t=2390510
Rahulrulez said:
Rename update-binary.orig to update-binary. That might be the issue mate!
Click to expand...
Click to collapse

Hi, I know this has nothing to do with what the OP asked on the thread, but it's related to Updater-Script so here goes:
I've notice a lot of people have been using delete_recursive instead of format command to wipe system.
Why is that? Is it safer to use delete_recursive? Because I'm using Android Kitchen and it creates an Updater-Script with format command.
It's the first time I'm using Android Kitchen though so I'm afraid of testing the zip I made before I'm sure it's safe to use format. Can somebody help me?
PS.: I didn't want to create another thread to ask this so I apologize in advance.

MaKTaiL said:
Hi, I know this has nothing to do with what the OP asked on the thread, but it's related to Updater-Script so here goes:
I've notice a lot of people have been using delete_recursive instead of format command to wipe system.
Why is that? Is it safer to use delete_recursive? Because I'm using Android Kitchen and it creates an Updater-Script with format command.
It's the first time I'm using Android Kitchen though so I'm afraid of testing the zip I made before I'm sure it's safe to use format. Can somebody help me?
PS.: I didn't want to create another thread to ask this so I apologize in advance.
Click to expand...
Click to collapse
It all started with mmc bug that has been presented by ICS source for GS2.
format() command was triggering hard brick.
You can find very good and full explanation of the bug in GS2 section of the forum but here is very short and simple explanation of the bug.
The MMC_CAP_ERASE command (part of format) was writing bunch of zeros in MMC killing the phone.
After kernel source was released we were able to disable that command and it became safer but some devs still use delete_recursive instead of format.
Both command do same and have pretty much same affect but delete_recursive might be few milliseconds slower than format()
Format command is formatting the partition where delete_recursive is deleting everything from partition (folders, subfolders, files etc) and then goes over the partition again to make sure nothing left behind (thus "recursive").
For new install format() command is cleaner, I think.
But if dev has modified his script at some point it will just keep using it till new modification is required. So there may be no need for delete_recursive any more but since it's in script and script is working no one is really looking into it.
Hope this make sense.

agat63 said:
It all started with mmc bug that has been presented by ICS source for GS2.
format() command was triggering hard brick.
You can find very good and full explanation of the bug in GS2 section of the forum but here is very short and simple explanation of the bug.
The MMC_CAP_ERASE command (part of format) was writing bunch of zeros in MMC killing the phone.
After kernel source was released we were able to disable that command and it became safer but some devs still use delete_recursive instead of format.
Both command do same and have pretty much same affect but delete_recursive might be few milliseconds slower than format()
Format command is formatting the partition where delete_recursive is deleting everything from partition (folders, subfolders, files etc) and then goes over the partition again to make sure nothing left behind (thus "recursive").
For new install format() command is cleaner, I think.
But if dev has modified his script at some point it will just keep using it till new modification is required. So there may be no need for delete_recursive any more but since it's in script and script is working no one is really looking into it.
Hope this make sense.
Click to expand...
Click to collapse
Thanks for reserving your time to answer me. Really appreciate it.
I came from a Galaxy S2 before the S4 and I'm aware of the MMC_CAP_ERASE problems.
I just didn't know it was caused by the format command. Thanks for explaining it to me.
I'll keep using delete_recursive from now on.

Here's my log...
Installing '/sdcard/GEM4.3_By:Joeyxc.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/GEM4.3_By:Joeyxc.zip.md5
Skipping MD5 check: no MD5 file found.
line 4 col 17: syntax error, unexpected STRING, expecting $end
line 5 col 19: syntax error, unexpected STRING, expecting ',' or ')'
2 parse errors
E:Error executing updater binary in zip '/sdcard/GEM4.3_By:Joeyxc.zip'
Error flashing zip '/sdcard/GEM4.3_By:Joeyxc.zip'
Updating partition details...
Please help
Sent from my SGH-I337 using Tapatalk 2

Joeyxc said:
hello all ive been working on my rom but i cant get it working in recovery it says the binary couldnt be read correctly, attached is my working folder zip from kitchen please help look into it i cant figure it out
Click to expand...
Click to collapse
The issue is the format the text is in. Also in addition to renaming update-binary.orig to update-binary, rename update-script to updater-script. Open the updater-script.orig with a text editor and look at the format and compare it to the text you have in 'update-script'. Change the format of the text in 'update-script' to match the format of 'updater-script.orig'. You should be able to notice right away that you will need to add parenthesis', semi-colons, and apostrophes as you are missing all of them. If you need more help let me know, I can look over/help you edit it.
Edit: Come to think about it, you just needed to convert update script to updater-script using kitchen.

Can I ask an updater-script related problem here please.
I write a few CWM utils (see my thread)
Some of these scripts perform a factory reset (wipe /data essentially)
On the GS2, this used to work great, but on the GS4, doing this also wipes the entire internal SD card!
I think this happening because there is a link to sd card in /data/media/0 perhaps.
My question is, how can I perform such a wipe of /data in the updater-script and keep internal SD Card in tact?
I've tried delete_recursive and format
But always, the script ends up wiping the entire SD card along with /data
example of commands I've been using in the updater-script are:
format("ext4", "EMMC", "/dev/block/mmcblk0p29", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p29", "/data");
delete_recursive("/data");
I've also tried unmounting /sdcard before attempting one of the above commands:
unmount("/sdcard");
run_program("/sbin/umount", "/sdcard");
(also tried both of these with /data/media/0)
both actually unmounted /sdcard (as I could no longer access it in recovery) but both the format and the delete_recursive command still managed to wipe the entire internal SD card.
If unmounted, I am then unable to get recovery to see the sdcard until the device is rebooted.
I've tried to remount the sdcard to get it back online for the current recovery session in the updater-script using:
mount("vfat", "EMMC", "/dev/block/mmcblk0p1", "/sdcard");
but this doesn't seem to work.
Any pointers or advice would be greatly appreciated as this has been driving me nuts! :silly:
:good:

FWIW, I had issues with data too, I was unable to restore shealth2 since it is preinstalled in /data/app and I would soft-brick everytime I tried flashing it until I finally used the script below with success.
unmount("/system");
mount("ext4", "EMMC", "/dev/block/mmcblk0p29", "/data");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");
package_extract_dir("system", "/system");
set_perm_recursive(0, 0, 0755, 0644, "/system");
run_program("adb", "install", "-r", "added_files/system/app/HealthContentProvider.apk");
run_program("adb", "install", "-r", "added_files/system/app/SensorService.apk");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
run_program("adb", "install", "-r", "added_files/data/app/SHealth2.apk");
unmount("/system");
unmount("/data");
Sent from my TouchPad using xda app-developers app

Data wiping on S4:
Recent CWM versions have seemed to handle this without issue.
I'm still using my alpha CWM and it handles this case without a problem.
Are you using current recovery repos from CM as well as device repos?
Removed 3 posts as they are not development related.
Please - If you're just downloading/flashing a ROM, not developing or creating it - try that ROM's specific thread.
If one isn't there consider asking in the Q&A for that specific device.

hey guys i know it's been some time no one has replied to this thread, i hope someone can help though... Here is my issue, i am building my own rom from stock SGH-M919V (Galaxy S4..carrier Video Tron) rom using latest android kitchen, i have removed lots of bloatware, removed knox, deodexed the apps..etc.etc. I am ready to build the rom so i do that, then comes the time to flash the new rom created by android-kitchen i am using Philz Touch recovery latest, this is the error i get in recovery:
Code:
Installing update...
format() expects 5 args, got 4
E:Error in /storage/sdcard1/stock.zip
(Status 7)
Installation aborted.
some times i get...format() expects 3 args, got 4...if i try a different setting in recovery.
I know a lot of ppl had this issue before, i just cant find the solution for my phone, model, rom specifically.
Android Kitchen says it needs to convert the update-script to updater-script...so i do what it suggest...ive learn this was the issue i am having...can someone point to the right direction to fix this and to successfully flash my rom?
BTW this is the very first rom i try to bake so i am farely new to this. I would also like to remove the format() command and use delete_recursive() ..how do i implement it ? do i just rename the command ?.
THANKS ! :fingers-crossed:

I am making a rom in cwm but I always get the error status of 0 , help me fill in the updater script correctly?
This is the updater script made from cygwin:
Code:
show_progress(0.1, 0);
format("MTD", "system");
mount("MTD", "system", "/system");
format("MTD", "userdata");
package_extract_dir("system", "/system");
symlink("dumpstate", "/system/bin/dumpcrash");
symlink("debuggerd", "/system/bin/csview");
symlink("mksh", "/system/bin/sh");
symlink("toolbox", "/system/bin/touchinput");
symlink("toolbox", "/system/bin/playback");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");
set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");
set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/firmware");
set_perm(0, 2000, 0755, "/system/vendor/lib");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
show_progress(0.1, 10);
show_progress(0.2, 0);
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
show_progress(0.2, 10);
unmount("/system");
The rom is for s3 mini

help updater script

hello sir
u have been helping me a lot
i am uploading my update script from my working folder
please tell me if there are any errors as well as will this work while flasing from cwm recovery

First of all,Change the thread title all of us are here to help you
And second,specify what help you want from him,without telling us what help you need he can't help you...
Take this as a suggestion
-Regards

you wont know till you flash it - what works on one device might not work on another even if symantically correct
best thing to do is do what I do - test your own work

marcussmith2626 said:
you wont know till you flash it - what works on one device might not work on another even if symantically correct
best thing to do is do what I do - test your own work
Click to expand...
Click to collapse
hello
ok i changed the mount points but still got status 0 error
here is the coding of updater script
Code:
show_progress(0.1, 0);
ui_print("WELCOME");
ui_print("PANDORA ROM");
mount("rfs", "EMMC", "/dev/block/stl19", "/system");
mount("rfs", "rfs16", "/dev/block/stl11", "/data");
package_extract_file("check_data_app", "/tmp/check_data_app");
set_perm(0, 0, 0777, "/tmp/check_data_app");
run_program("/tmp/check_data_app");
package_extract_dir("data", "/data");
set_perm_recursive(1000, 1000, 0771, 0644, "/data/app");
package_extract_dir("system", "/system");
symlink("toolbox", "/system/bin/cat");
symlink("toolbox", "/system/bin/chmod");
symlink("toolbox", "/system/bin/chown");
symlink("toolbox", "/system/bin/cmp");
symlink("toolbox", "/system/bin/date");
symlink("toolbox", "/system/bin/dd");
symlink("toolbox", "/system/bin/df");
symlink("toolbox", "/system/bin/dmesg");
symlink("toolbox", "/system/bin/getevent");
symlink("toolbox", "/system/bin/getprop");
symlink("toolbox", "/system/bin/hd");
symlink("toolbox", "/system/bin/id");
symlink("toolbox", "/system/bin/ifconfig");
symlink("toolbox", "/system/bin/iftop");
symlink("toolbox", "/system/bin/insmod");
symlink("toolbox", "/system/bin/ioctl");
symlink("toolbox", "/system/bin/ionice");
symlink("toolbox", "/system/bin/kill");
symlink("toolbox", "/system/bin/ln");
symlink("toolbox", "/system/bin/log");
symlink("toolbox", "/system/bin/ls");
symlink("toolbox", "/system/bin/lsmod");
symlink("toolbox", "/system/bin/lsof");
symlink("toolbox", "/system/bin/mkdir");
symlink("toolbox", "/system/bin/mount");
symlink("toolbox", "/system/bin/mv");
symlink("toolbox", "/system/bin/nandread");
symlink("toolbox", "/system/bin/netstat");
symlink("toolbox", "/system/bin/newfs_msdos");
symlink("toolbox", "/system/bin/notify");
symlink("toolbox", "/system/bin/printenv");
symlink("toolbox", "/system/bin/ps");
symlink("toolbox", "/system/bin/reboot");
symlink("toolbox", "/system/bin/renice");
symlink("toolbox", "/system/bin/rm");
symlink("toolbox", "/system/bin/rmdir");
symlink("toolbox", "/system/bin/rmmod");
symlink("toolbox", "/system/bin/route");
symlink("toolbox", "/system/bin/schedtop");
symlink("toolbox", "/system/bin/sendevent");
symlink("toolbox", "/system/bin/setconsole");
symlink("toolbox", "/system/bin/setprop");
symlink("toolbox", "/system/bin/sleep");
symlink("toolbox", "/system/bin/smd");
symlink("toolbox", "/system/bin/start");
symlink("toolbox", "/system/bin/stop");
symlink("toolbox", "/system/bin/sync");
symlink("toolbox", "/system/bin/top");
symlink("toolbox", "/system/bin/umount");
symlink("toolbox", "/system/bin/uptime");
symlink("toolbox", "/system/bin/vmstat");
symlink("toolbox", "/system/bin/watchprops");
symlink("toolbox", "/system/bin/wipe");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");
set_perm(0, 3003, 06755, "/system/bin/ip");
set_perm(0, 3003, 02750, "/system/bin/netcfg");
set_perm(0, 3004, 02755, "/system/bin/ping");
set_perm(0, 2000, 06750, "/system/bin/run-as");
set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");
set_perm(0, 0, 0755, "/system/etc/bluetooth");
set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");
set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");
set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");
set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");
set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");
set_perm(0, 0, 0777, "/system/bin/a2sd");
set_perm(0, 0, 0777, "/system/etc/init.d/00banner");
set_perm(0, 0, 0777, "/system/etc/init.d/01sysctl");
set_perm(0, 0, 0777, "/system/etc/init.d/02firstboot");
set_perm(0, 0, 0777, "/system/etc/init.d/04apps2sd");
set_perm(0, 0, 0777, "/system/etc/init.d/99complete");
set_perm(0, 0, 0777, "/system/bin/launcha2sd");
set_perm(0, 0, 0777, "/system/bin/starta2sd");
set_perm(0, 0, 0777, "/system/bin/jita2sd");
set_perm(0, 0, 0777, "/system/bin/chka2sd");
set_perm(0, 0, 0777, "/system/bin/zipalign");
set_perm(0, 0, 0777, "/system/bin/sysinit");
set_perm(0, 0, 0777, "/system/bin/busybox.a2sd");
set_perm(0, 0, 0644, "/system/bin/apps2sd.hlp");
set_perm(0, 0, 0777, "/system/xbin/a2sd");
set_perm(0, 0, 0777, "/system/bin/dtinstall");
set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");
set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");
set_perm(0, 0, 04755, "/system/xbin/bash");
symlink("/system/xbin/bash", "/system/bin/sh");
set_perm(0, 0, 04755, "/system/xbin/nano");
set_perm(0, 0, 04755, "/system/xbin/sysrw");
set_perm(0, 0, 04755, "/system/xbin/sysro");
set_perm(0, 1000, 0755, "/system/xbin/busybox");
symlink("/system/xbin/busybox", "/system/bin/busybox");
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su", "/system/bin/su");
show_progress(0.1, 10);
show_progress(0.2, 0);
run_program("/data/dtinstall.launch");
delete("/system/bin/dtinstall");
delete("/data/dtinstall.launch");
show_progress(0.2, 10);
unmount("/system");
unmount("/data");
please help

abhishekr700 said:
hello
ok i changed the mount points but still got status 0 error
here is the coding of updater script
please help
Click to expand...
Click to collapse
script looks fine - you probably havent changed the update binary to the one I gave you earlier
here it is again in attachment - unzip and replace the one in your rom zip with it
dont put it in the kitchen working folder - build the rom and then use winrar to open the zip and delete the scripts and then drag the new scripts into the zip folder

marcussmith2626 said:
script looks fine - you probably havent changed the update binary to the one I gave you earlier
here it is again in attachment - unzip and replace the one in your rom zip with it
dont put it in the kitchen working folder - build the rom and then use winrar to open the zip and delete the scripts and then drag the new scripts into the zip folder
Click to expand...
Click to collapse
hurray i replaced the update binary and now i successfully flashed my rom
but my phone got into a bootloop
why??

abhishekr700 said:
hurray i replaced the update binary and now i successfully flashed my rom
but my phone got into a bootloop
why??
Click to expand...
Click to collapse
how long is a bit of string?
logcat it with adb - some file you modded is wrong - probably a jar file but who knows - could be anything

marcussmith2626 said:
how long is a bit of string?
logcat it with adb - some file you modded is wrong - probably a jar file but who knows - could be anything
Click to expand...
Click to collapse
hey logcat gave me this
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse

abhishekr700 said:
hey logcat gave me this
Click to expand...
Click to collapse
sounds like you didnt wipe system data and cache and mount system data and cache before you flashed the zip
edit sorry - I assmue that error was on the adb command and not in the logcat it produced as previously thought
thats because you havent installed adb drivers and your phone is not set to usb debugging mode - you will have to add it to the build prop I think - there is a guide somewhere for using adb on a device which cant boot and doesnt have usb debugging turned on
you can always flash stock rom then turn on usb debugging then flash your rom and then take a logcat

marcussmith2626 said:
sounds like you didnt wipe system data and cache and mount system data and cache before you flashed the zip
edit sorry - I assmue that error was on the adb command and not in the logcat it produced as previously thought
thats because you havent installed adb drivers and your phone is not set to usb debugging mode - you will have to add it to the build prop I think - there is a guide somewhere for using adb on a device which cant boot and doesnt have usb debugging turned on
you can always flash stock rom then turn on usb debugging then flash your rom and then take a logcat
Click to expand...
Click to collapse
i wiped
system
cache
dalvik cache
using cmw
i used this command for logcat
adb logcat -v long > logcat.txt
i tested rhis command firsy on my present rom
i had installed my phone drivers earlier
but i dont know how to enable usb debugging on my newly built custom rom
can u detail me abut that build.prop u r talking about

abhishekr700 said:
i wiped
system
cache
dalvik cache
using cmw
i used this command for logcat
adb logcat -v long > logcat.txt
i tested rhis command firsy on my present rom
i had installed my phone drivers earlier
but i dont know how to enable usb debugging on my newly built custom rom
can u detail me abut that build.prop u r talking about
Click to expand...
Click to collapse
add this to the build.prop and default.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
or from adb console you can type (with phone in recovery mode)
Code:
adb shell
su
mount -o remount,rw /system
cd /
echo "persist.service.adb.enable=1" >> default.prop
echo "persist.service.debuggable=1" >> default.prop
echo "persist.sys.usb.config=mtp,adb" >> default.prop
echo "persist.service.adb.enable=1" >> /system/build.prop
echo "persist.service.debuggable=1" >> /system/build.prop
echo "persist.sys.usb.config=mtp,adb" >> /system/build.prop
restart phone and adb should work
its also a good idea when you are building a rom to mod one file at a time and then flash it - otherwise its like trying to find a needle in a haystack if you have no idea which file has the error

marcussmith2626 said:
add this to the build.prop and default.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
its also a good idea when you are building a rom to mod one file at a time and then flash it - otherwise its like trying to find a needle in a haystack if you have no idea which file has the error
Click to expand...
Click to collapse
one thing i noticed after the logcat response that
in/system/bin/ there is a file sh0 and not sh
why is it and do i need to rename it to sh to work
because logcat said that it couldnt fild such file
can that be a erroe and renaming the file fix it

abhishekr700 said:
one thing i noticed after the logcat response that
in/system/bin/ there is a file sh0 and not sh
why is it and do i need to rename it to sh to work
because logcat said that it couldnt fild such file
can that be a erroe and renaming the file fix it
Click to expand...
Click to collapse
here is that file if you need it (unzip the file in attachement and place in system/bin)
I have no sh0 in my folder so im guessing its an incorrectly named file

marcussmith2626 said:
here is that file if you need it (unzip the file in attachement and place in system/bin)
I have no sh0 in my folder so im guessing its an incorrectly named file
Click to expand...
Click to collapse
is sh0 in place of sh can produce error

abhishekr700 said:
is sh0 in place of sh can produce error
Click to expand...
Click to collapse
well if its looking for a filename it cant find thats going to cause an error
unzip the file I gave in my last post and put in bin folder and reflash the rom and see if it boots or you can use adb commands (if usb debugging is enabled)

marcussmith2626 said:
well if its looking for a filename it cant find thats going to cause an error
unzip the file I gave in my last post and put in bin folder and reflash the rom and see if it boots or you can use adb commands (if usb debugging is enabled)
Click to expand...
Click to collapse
can this also cause bootloop

abhishekr700 said:
can this also cause bootloop
Click to expand...
Click to collapse
If a file is missing then yes
why dont you just try it?

abhishekr700 said:
i wiped
system
cache
dalvik cache
using cmw
i used this command for logcat
adb logcat -v long > logcat.txt
i tested rhis command firsy on my present rom
i had installed my phone drivers earlier
but i dont know how to enable usb debugging on my newly built custom rom
can u detail me abut that build.prop u r talking about
Click to expand...
Click to collapse
Never wipe dalvik cache while installing ROM. Only wipe data, cache. Don't wipe Dalvik Cache. Whenever I wipe dalvik cache while installing any STOCK based ROM, I get a bootloop and stuck at Samsung Galaxy y screen.
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands

marcussmith2626 said:
If a file is missing then yes
why dont you just try it?
Click to expand...
Click to collapse
ok placed sh file in system bin
still bootloop
in updater script found this
set_perm(0, 0, 04755, "/system/xbin/bash");
symlink("/system/xbin/bash", "/system/bin/sh");
Click to expand...
Click to collapse

abhishekr700 said:
ok placed sh file in system bin
still bootloop
in updater script found this
Click to expand...
Click to collapse
as long as kitchen created your update script and all you did was edit the top part above the sym links to set the correct mount points it should all work fine
like I said if you are getting bootloops logcat it - its impossible for me to say why it doing it really - could be anything - any little change you have done which is why I said when build building a rom make one change at a time and test

[MT6582]Most Epic Rom Ever [MERE] [MICROMAX] [A120]

MERE ROM FOR MICROMAX A120
FEATURES:
*KitKat Based
*Aosp Icons
*Sound Settings
*Better Ram Management
*Network Monitor
*Listview Animation
*Volume Rocker Wake switch
*Shutdown Animation switch
*Performance Control
*Proximity Gestures
*Multiuser Support
*App Privacy
*Advanced Reboot Menu
*Updated and Fixed Gapps
*Ios Fonts
Screenshots:
{
"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"
}
INSTRUCTION TO FLASH MERE ROM ON FOTA MMX
1. You must be on stock mmx jellybean or fota mmx kitkat.
2. Boot into recovery. I personally prefer PHILZ.
3. If you are on philz, select clean to install a new rom. If you are not using philz simply wipe/data, wipe/system in any other recovery.
4. Browse to the merefota.zip location in your sd card and install it.
5. Reboot. We are done!
DOWNLOAD LINK : MERE FOTA
Credits :
* Team EPIC for developing MERE
* @umangleekha & @Siddhesh.K15 .
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x (STOCK)
Version Information
Status: FINAL
Current Beta Version: 1.51
Final Release Date: 2015-01-12
Created 2015-01-08
Last Updated 2015-01-12

Mere rom for STOCK micromax
INSTRUCTION TO FLASH MERE ROM ON MMX STOCK
1. You must be on Stock Kitkat mmx_06. You can download it from here.
2. Download CTR recovery from here and flash it with sp flash tool.
3. Boot into recovery and go to Wipe Menu and click on Wipe Data-Factory Reset.
4. Now select Install zip and browse to the location where you have MERE ROM zip and install it.
5. Reboot your device & enjoy full aosp experience with MERE rom.
Download Link: MERE ROM
Hit thanks if you want me to bring more such roms for our device

Mere rom for wiko rainbow
INSTRUCTION TO FLASH MERE ROM ON WIKO RAINBOW
1. You must be on wiko rainbow kitkat before flashing this ROM.
2. Boot into recovery and wipe/data & /system.
3. Browse your sd card for mere rom zip and install it.
4. Reboot & enjoy!
Note: Do not flash DOLBY mod, DSP manager is inbuilt in the latest version.
DOWNLOAD LINK: Go here

DOLBY MOD FOR MERE
1. Download from here.
2. Boot into recovery and simply flash it, then reboot.
3. Enjoy Dolby sound on your device.
Note: FOR MERE ROM ONLY
Credits: @umangleekha for this mod.
Hit thanks if you want me to bring more such roms for our device

my device is myphone agua rio (s5501) version with 4gb of storage and running Edmhar's Kitkat Deodexed. can i flash this directly to my device? Thanks.

cheeze.keyk said:
my device is myphone agua rio (s5501) version with 4gb of storage and running Edmhar's Kitkat Deodexed. can i flash this directly to my device? Thanks.
Click to expand...
Click to collapse
No, its for different base.

or i need to flash the mmx fota before flashing your rom?

cheeze.keyk said:
or i need to flash the mmx fota before flashing your rom?
Click to expand...
Click to collapse
First, its not my rom. It's Team Mere's creation. So full credits to them for developing such a beautiful rom. I simply ported it.
Second, i am not sure whether micromax fota works on rio or not. Better consult senior devs of your rio group.

Good work, but found a bug.
Wifi internet connection lost when switching between wifi ap (2 routers, same SSID, same security and password, different channel.)
This works well in any other ROM. Never happened to me.
Another thing. Because you used wiko rainbow DarkL zip?
You need to modify the script !!
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");
delete_recursive("/system/app");
delete_recursive("/system/priv-app");
delete_recursive("/system/framework");
delete_recursive("/system/media");
package_extract_dir("system", "/system");
[COLOR="Red"]set_perm_recursive(0, 0, 0666, 0666, "/data/data/de.robv.android.xposed.installer/conf/modules.list");[/COLOR]
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 0, 0777, 0777, "/system/xbin/busybox");
run_program("/sbin/umount", "/system");
[COLOR="Red"]run_program("/sbin/mount", "/data");
package_extract_dir("data", "/data");[/COLOR]
delete_recursive("/data/dalvik-cache");
[COLOR="Red"]run_program("/sbin/umount", "/data");[/COLOR]
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
show_progress(0.1, 10);
ui_print("[*] Flashing partition: BOOT");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));
assert(package_extract_file("logo.bin", "/tmp/logo.bin"),
write_raw_image("/tmp/logo.bin", "logo"),
delete("/tmp/logo.bin"));
show_progress(0.2, 10);
unmount("/system");
The red lines can be deleted

moonrotation said:
Good work, but found a bug.
Wifi internet connection lost when switching between wifi ap (2 routers, same SSID, same security and password, different channel.)
This works well in any other ROM. Never happened to me.
Another thing. Because you used wiko rainbow DarkL zip?
You need to modify the script !!
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");
delete_recursive("/system/app");
delete_recursive("/system/priv-app");
delete_recursive("/system/framework");
delete_recursive("/system/media");
package_extract_dir("system", "/system");
[COLOR="Red"]set_perm_recursive(0, 0, 0666, 0666, "/data/data/de.robv.android.xposed.installer/conf/modules.list");[/COLOR]
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 0, 0777, 0777, "/system/xbin/busybox");
run_program("/sbin/umount", "/system");
[COLOR="Red"]run_program("/sbin/mount", "/data");
package_extract_dir("data", "/data");[/COLOR]
delete_recursive("/data/dalvik-cache");
[COLOR="Red"]run_program("/sbin/umount", "/data");[/COLOR]
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
show_progress(0.1, 10);
ui_print("[*] Flashing partition: BOOT");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));
assert(package_extract_file("logo.bin", "/tmp/logo.bin"),
write_raw_image("/tmp/logo.bin", "logo"),
delete("/tmp/logo.bin"));
show_progress(0.2, 10);
unmount("/system");
The red lines can be deleted
Click to expand...
Click to collapse
i will look into that wifi problem soon. & Yes, i used wiko rainbow dark l script. I was too lazy to edit it. I will fix it soon.
users like you always motivate me. Thanks for pointing out mistakes. :good:

moonrotation said:
Good work, but found a bug.
Wifi internet connection lost when switching between wifi ap (2 routers, same SSID, same security and password, different channel.)
This works well in any other ROM. Never happened to me.
Another thing. Because you used wiko rainbow DarkL zip?
You need to modify the script !!
Code:
mount("ext4", "EMMC", "/dev/block/mmcblk0p5", "/system");
delete_recursive("/system/app");
delete_recursive("/system/priv-app");
delete_recursive("/system/framework");
delete_recursive("/system/media");
package_extract_dir("system", "/system");
[COLOR="Red"]set_perm_recursive(0, 0, 0666, 0666, "/data/data/de.robv.android.xposed.installer/conf/modules.list");[/COLOR]
set_perm_recursive(0, 0, 0777, 0777, "/system/etc/init.d");
set_perm_recursive(0, 0, 0777, 0777, "/system/xbin/busybox");
run_program("/sbin/umount", "/system");
[COLOR="Red"]run_program("/sbin/mount", "/data");
package_extract_dir("data", "/data");[/COLOR]
delete_recursive("/data/dalvik-cache");
[COLOR="Red"]run_program("/sbin/umount", "/data");[/COLOR]
run_program("/system/xbin/busybox", "--install", "-s", "/system/xbin");
show_progress(0.1, 10);
ui_print("[*] Flashing partition: BOOT");
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "bootimg"),
delete("/tmp/boot.img"));
assert(package_extract_file("logo.bin", "/tmp/logo.bin"),
write_raw_image("/tmp/logo.bin", "logo"),
delete("/tmp/logo.bin"));
show_progress(0.2, 10);
unmount("/system");
The red lines can be deleted
Click to expand...
Click to collapse
Actually he used my rom's updater script, the xposed config file permission line should be removed also the data extract line can be removed but data mount and unmount line is requied because i'm wiping dalvik-cache in updater script.

umangleekha said:
Actually he used my rom's updater script, the xposed config file permission line should be removed also the data extract line can be removed but data mount and unmount line is requied because i'm wiping dalvik-cache in updater script.
Click to expand...
Click to collapse
You're right, I did not see well.
mr-illusionist said:
i will look into that wifi problem soon. & Yes, i used wiko rainbow dark l script. I was too lazy to edit it. I will fix it soon.
users like you always motivate me. Thanks for pointing out mistakes. :good:
Click to expand...
Click to collapse
Here a test of your rom with Xpro kernel v2, and same kernel DarkL rom.
You can see 0,00 B. I use Greenify. I have no idea if it may be the culprit.

This ROM seems interesting, I will surely try this one.
Can someone confirm, if this ROM is pre-rooted?

kool_sandy said:
This ROM seems interesting, I will surely try this one.
Can someone confirm, if this ROM is pre-rooted?
Click to expand...
Click to collapse
Not pre rooted

So, how to root it? I rooted it using kingoroot.
Sent from my Oneplus One

kool_sandy said:
So, how to root it? I rooted it using kingoroot.
Sent from my Oneplus One
Click to expand...
Click to collapse
Well, flash root zip from the attached blog. It can be flashed over any kitkat based rom (mediatek) http://www.androiddevs.net/mediatek-rooting-issue-fix-kitkat-roms/

Thx bro, well try this soon!
Sent from my Oneplus One

umangleekha said:
Actually he used my rom's updater script, the xposed config file permission line should be removed also the data extract line can be removed but data mount and unmount line is requied because i'm wiping dalvik-cache in updater script.
Click to expand...
Click to collapse
I have share this ROM to so many friends BEC i lov this ROM

Hi,
I ported for myself this rom (Gionee P3/Walton Primo GF) but i have a bug: PlayStore refuse to connect. I also port MERE 1.51 flareS from the original developers site and i have the same problem. Do you have any ideea how to solve this bug?

Latest Mere (V1.51) will be updated for wiko base today. Stay tuned!
Full ROM this time.

[One UI][A70] - Creator ROM ZIP

Creator ROM Galaxy A70:
This is a small project, ¡create a basic rom based on one ui for your A70 device!
this project is based on Dynamic Installer and SuperR custom zip, I am not responsible for damaged phones, install at your own risk.
FEATURES:
Spoiler: Features
Debloat
Custom CSC Features
Floating Features
Build.prop TWEAKS
Add apps or files to the system, vendor and product
Multidisabler
DFE
Fix bluetooth pairings loss
and more
Downloads:
Download: AndroidFileHost
ROM made with Creator ROM: Universal ROM A70q
ACTIONS:
use file: ROM ZIP/META-INF/com/google/android/updater-script:
ui print: This is what will be displayed on installation
Code:
ui_print(" ");
#Example
ui_print("Creator ROM ");
Files bin: Files to make the zip work (Creator ROM/ROM ZIP/install/bin/)
Code:
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
run_program("/tmp/install/bin/busybox", "sh", "/tmp/install/bin/configure.sh");
Mount:
Code:
#system
ifelse(is_mounted("/system"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "system"), "/system"));
#vendor
ifelse(is_mounted("/vendor"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "vendor"), "/vendor"));
#product
ifelse(is_mounted("/product"), "", mount("ext4", "EMMC", file_getprop("/tmp/config", "product"), "/product")
Unmount:
Code:
#system files
ifelse(is_mounted("/system"), unmount("/system"));
#vendor files
ifelse(is_mounted("/vendor"), unmount("/vendor"));
#product files
ifelse(is_mounted("/product"), unmount("/product"));
Extract files:
Code:
#system
package_extract_dir("system", "/system");
#vendor
package_extract_dir("vendor", "/vendor");
#product
package_extract_dir("product", "/product");
Permissions apps:
Code:
#app
set_metadata_recursive("/system/system/app", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
#priv-app
set_metadata_recursive("/system/system/priv-app", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
Change build number: DOO/META-INF/com/google/android/updater-script
Code:
#Find
update_file_string "ro.build.display.id=(ROM NAME) "
#Example
update_file_string "ro.build.display.id=A70 ROM v3 "
Debloat:
these files have effect on product (app and priv-app), system (app, priv-app and system_ext)
Find DOO/META-INF/addons/blacklist.txt:
There you write the name of the apk you want to delete or simply leave it empty, when it is empty all those that are not in whitelist.txt will be deleted like Chrome (Without .apk)
Find DOO/META-INF/addons/blacklist_packages.txt:
Here you write the name of the package of the app you want to delete example: com.android.chrome
Find DOO/META-INF/addons/whitelist.txt:
Here you write the name of all the apk that you do not want to delete like SystemUI (Without .apk)
Find DOO/META-INF/addons/whitelist_packages.txt:
In this file you write the name of all the application packages that you do not want to delete
Floating Features:
Find DOO/META-INF/addons/floating.txt
Add the new lines you want to add for the floating features
Prop TWEAKS:
system/build.prop
Find DOO/META-INF/addons/newprop.txt
I will write the new tweaks that you want to add to your build.prop
vendor/build.prop
Find DOO/META-INF/addons/newvprop.txt
I will write the new tweaks that you want to add to your build.prop
CSC Features:
Find DOO/omc/cscfeature.xml
I do not recommend editing this file but you can add your features here
Extract files:
In the following folders you can add the files that you want the zip to move when it is installed
ROM ZIP/product/
ROM ZIP/system/
ROM ZIP/vendor/
ZIP: Zip all DOO folders into one DOO.zip file (META-INF and omc) And move the DOO.zip file to ROM ZIP/DOO/
Notes:
All lines added to newprop.txt, floating.txt, etc, will be added to their respective files, if the line already exists it will be replaced
lines can be added as ro.config.tima=0 and it will be replaced by ro.config.tima=1
BTC: bc1qqtg3pgxkhm7egmh35qnsq8xmnjjte6zeyz8s30
Paypal: Paypal.me...
if you want to support the project
XDA: DevDB Information
Creator, ROM MOD ZIP for the Samsung Galaxy A70
Based On: ONE UI
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2021-07-18

Nice!

Database Users

welcome