Database Users

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

[Q] Super Su Fix

hello guys ... i want the super SU fix because it doesn't have the Binary installed and it doesn't want to install help needed plz

here is it http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip

mohamedrashad said:
here is it http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
Thanks ... is it a flashable .zip ??
Sent from my GT-S5360 using XDA Free mobile app

Omar El- Hussien said:
Thanks ... is it a flashable .zip ??
Sent from my GT-S5360 using XDA Free mobile app
Click to expand...
Click to collapse
no
thats a zip from chainfire
extract zip
pull su inside arm folder
n superuser it self
create a folder
system/app/superuser apk
/xbin/su
zip ur folder
sign with zipsigner.apk
then extract that zip again
under meta-inf u can found
com/google/android/update binary
under binary u must make a updater-script file
open it and follow this code
Code:
show_progress(0.1, 0);
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
show_progress(0.500000, 0);
ui_print("");
run_program("/tmp/busybox", "mount", "/system");
ui_print("");
ui_print("");
ui_print("Initializing");
ui_print("");
ui_print("Please Wait");
ui_print("");
ui_print("");
delete("/system/app/Superuser.apk");
delete("/system/xbin/su");
package_extract_dir("system", "/system");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
ui_print("Setting Permissions");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su","/system/bin/su");
show_progress(0.100000, 0);
ui_print("Finish");
ui_print("");
ui_print("");
unmount("/system");
ZIP again n sign using zipsigner apk
flash under cwm
or u can google it if u bored

or you could just flash my zip in cwm with system mounted
uninstall any superuser/supersu you have first
http://d-h.st/kFt

Minions_Army said:
no
thats a zip from chainfire
extract zip
pull su inside arm folder
n superuser it self
create a folder
system/app/superuser apk
/xbin/su
zip ur folder
sign with zipsigner.apk
then extract that zip again
under meta-inf u can found
com/google/android/update binary
under binary u must make a updater-script file
open it and follow this code
Code:
show_progress(0.1, 0);
mount("rfs", "EMMC", "/dev/block/stl9", "/system");
show_progress(0.500000, 0);
ui_print("");
run_program("/tmp/busybox", "mount", "/system");
ui_print("");
ui_print("");
ui_print("Initializing");
ui_print("");
ui_print("Please Wait");
ui_print("");
ui_print("");
delete("/system/app/Superuser.apk");
delete("/system/xbin/su");
package_extract_dir("system", "/system");
show_progress(0.200000, 0);
show_progress(0.200000, 10);
ui_print("Setting Permissions");
set_perm_recursive(0, 0, 0755, 0644, "/system/app");
set_perm(0, 0, 06755, "/system/xbin/su");
symlink("/system/xbin/su","/system/bin/su");
show_progress(0.100000, 0);
ui_print("Finish");
ui_print("");
ui_print("");
unmount("/system");
ZIP again n sign using zipsigner apk
flash under cwm
or u can google it if u bored
Click to expand...
Click to collapse
Hey this is universal I flashed it numerous times successfully
Sent from my GT-S5360 using Tapatalk 2

why not use the newest versions?

marcussmith2626 said:
or you could just flash my zip in cwm with system mounted
uninstall any superuser/supersu you have first
http://d-h.st/kFt
Click to expand...
Click to collapse
the only problem with your flashable .zip file is that you must un-install any other APK super user or super su ... and here comes the problem ... you cant delete it by system \ app \...etc Root explorer doesnt have root permission ... also same problem with the Link2Sd .... so i think you must add an un-installer on your zip file

-CALIBAN666- said:
why not use the newest versions?
Click to expand...
Click to collapse
its not related to an update i tried that alot ....

Omar El- Hussien said:
the only problem with your flashable .zip file is that you must un-install any other APK super user or super su ... and here comes the problem ... you cant delete it by system \ app \...etc Root explorer doesnt have root permission ... also same problem with the Link2Sd .... so i think you must add an un-installer on your zip file
Click to expand...
Click to collapse
You can just flash it and remove duplicate apps after if you want - shouldn't be a problem
Or add a line to delete the name of the superuser/supersu app in the updater script

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

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

[GAPPS][4.4.x][5.x][arm][arm64][All DPI] Fermion GApps [08-11-2015]

{
"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"
}
Thanks to @-Favstylez- for the banner!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices,
* dead SD cards, thermonuclear war, or you
* getting fired because the alarm app failed.
* Please do some research if you have any
* concerns about features included in this
* GApps before flashing them! If you point
* the finger at me for messing up your device,
* I will laugh at you.
*/
About the project
The Fermion GApps is a project made from my own hand. I started the scripts from scratch and have been improving them alone.
Ill make weekly updates, will be released mostly in the weekend.
This work is open source.
Created: 01-April-2015
Last update: 08-November-2015
Follow me in pushbullet to get new updates notifications!​
Features
Support for both KitKat (4.4.x) and Lollipop (5.x)
Support for both 32 and 64 bits processor architecture
Google Play Services and Google Play Games comes DPI optimised
Use of scripts to automatically compile the zips, using extra-compression to make'em smaller
The packages are foolproof, the scripts check you are installing the right version corresponding to your processor architecture and android version
Debloating script add-on to free some space and allow you to use a bigger package
Backup function, you don't have to reinstall the GApps after a ROM update, not even the Add-Ons or the Black Hole, most ROMs support this
DOWNLOADS & PACKAGE COMPARISION
Install or Update​1. Download and copy file to SD card.
2. Reboot into recovery
3. ONLY IN FIRST INSTALL: Do a full wipe (data, system and cache), flash your ROM and then the GApps.
4. Flash the selected zips (Packages and then Add-Ons)
5. Wipe cache and dalvik
6. Reboot the device
Add-Ons​
Black Hole Debloating Script v1.6, it removes:
-AudioFX
-Basic Dreams Wallpaper
-Cell Broadcast Receiver
-CM Wallpapers
-Exchange Services
-Galaxy Wallpaper
-Holo Spiral Wallpaper
-Live Wallpapers
-Live Wallpapers Picker
-Noise Field
-Phase Beam
-Photo Phase
-Photo Table
-Pico Tts
-Visualization Wallpapers
-Stock alarms, ringtones and notifications sounds
Chrome Beta
Chrome Dev
Google Office Suite, wich installs:
-Google Drive
-Google Docs
-Google Sheets
-Google Slides
Google Basic Framework, wich installs (replacing stock/AOSP):
-Google Calendar
-Google Camera
-Google Hangouts
-Google Keyboard
-Google Now Launcher
Outstanding Changelog
(See the folder in downloads link for full apps version)​
08/November/2015
The regular updates corresponding to each package
01/November/2015
Now with GmsCore and PlayGames DPI optimised, for: 160, 240, 320, 480, and unknown or different DPI devices
The regular updates corresponding to each package
18/October/2015
GmsCore removed from NIS package to make a real change between it and TIS, and make the more minimalist GApps package
The regular updates corresponding to each package
11/October/2015
The regular updates corresponding to each package
04/October/2015
The regular updates corresponding to each package
Fixed the script with arm64 zips
27/September/2015
The up-to-date Google Inc. updates to the corresponding packages
New structure, now with six available packages (check out the table for more details), with a new super basic package: NIS (Nought-Integer-Spin), and the previous packages changed; previous QIS is new EIS with some changes, previous EIS is new SIS, and previous SIS is new TIS
Deleted the Fit Add-On
Docs Suite renamed to Office Suite, and System Base renamed to Basic Framework and removed Keep from it
New date format in all the updater-scripts , previous dd-mm-yyyy, new is dd-month-yyyy
Removed Wallet, and added Bookmarks Sync Adapter and Face Unlock with its libraries
Moved from compiling in Linux to compiling in Windows due to more complex but fast compiling
19/September/2015
The up-to-date Google Inc. updates to the corresponding packages
13/September/2015
Now the Lollipop version is functional in both 5.0.2 and 5.1.1 versions, all the corresponding packages renamed from "5.1.x" to "5.x"
Now you can find info about the package you´ve installed in the F-Gapps.prop file located in /system
The up-to-date Google Inc. updates to the corresponding packages
Re-organized scripts and the way they check out the device before install
06/September/2015
Various Google Inc apps updated, including Google App, Maps, and Street View with new Google logo, and for arm devices updated Play Services to 8.1.05
Fixed a librarie with Drive that makes FC when open a PDF
30/August/2015
Up-to-date Google Inc apps updates, this time there were a lot of updates
Updated all the packages and add-ons except for the Black Hole
09/August/2015
Up-to-date Google Inc apps updates
Updated all the packages, Chrome Dev, Docs Suite, System Base, and Chrome Beta for 4.4 and 5.1(arm)
02/August/2015
Re-added the backup function
Google System Web View added to QIS and HIS packages
F.A.Q.​
Im facing FCs in x app
First try doing a full wipe (system, data & cache), flash your ROM, then the GApps, if problem still persist, then wait till next update to see if is fixed, or mail me
Im getting error while flashing
See if it show an error like "This package is for androird KitKat/Lollipop or 32/64 bits, and look for the right version, if dont but it says error 6, mail me, probably a syntax error in the updater-script

Ar-Dinthalion said:
Hi, I get to work and compiled a recov-*snip*
Click to expand...
Click to collapse
Hey! Nice job with this. Would you like me to add your work to The Gapps Central? If you do, can you give me a little more information about it so I can put it in the right section? Like if they have the same PA Gapps script? Or does it use @jajb's script? Or are the scripts entirely different?

TheXGX said:
Hey! Nice job with this. Would you like me to add your work to The Gapps Central? If you do, can you give me a little more information about it so I can put it in the right section? Like if they have the same PA Gapps script? Or does it use @jajb's script? Or are the scripts entirely different?
Click to expand...
Click to collapse
Sure! I PM you

Can we use this with Android 5.1 \ CM12.1 ROM's?

mundano said:
Can we use this with Android 5.1 \ CM12.1 ROM's?
Click to expand...
Click to collapse
Yes, I personally use CM 12.1

Hangouts and Google Messenger seem to be incompatible to some dual-SIM phones like the Moto G. So it would be best not to remove the included Messenger o those ROM's because there is no other way of getting SMS's to work.

mundano said:
Hangouts and Google Messenger seem to be incompatible to some dual-SIM phones like the Moto G. So it would be best not to remove the included Messenger o those ROM's because there is no other way of getting SMS's to work.
Click to expand...
Click to collapse
Yes, its known that those Gapps aren't compatible with Dual-Sim services, so please don't use them for devices like Moto G, if you have the problem PM and I'll send you an AOSP messenger apk, I'm trying to create a acript that avoid uninstall of specified apps by the user, like the PA Gapps did, but it will take me some more days

Ar-Dinthalion said:
Yes, its known that those Gapps aren't compatible with Dual-Sim services, so please don't use them for devices like Moto G, if you have the problem PM and I'll send you an AOSP messenger apk, I'm trying to create a acript that avoid uninstall of specified apps by the user, like the PA Gapps did, but it will take me some more days
Click to expand...
Click to collapse
Nexus4
Flashed latest Euphoria ROM and your latest built GApps and stuck on black screen forever.
#HIS_(Full)_F-Gapps_5.1.x_150415.zip

Subhojit said:
Nexus4
Flashed latest Euphoria ROM and your latest built GApps and stuck on black screen forever.
#HIS_(Full)_F-Gapps_5.1.x_150415.zip
Click to expand...
Click to collapse
Check out your ROM, the GApps don't have the meanings to kill a phone, try out clean install in your ROM, I test the GApps myself in three devices (own, girlfriend, brother), everyone different and all working perfectly

The only thing which attracted me to this thread was the usage of particle physics terms. LOL

parasthakur37 said:
The only thing which attracted me to this thread was the usage of particle physics terms. LOL
Click to expand...
Click to collapse
Thanks , I know physics are cool xD

My new favorite gapps !!

Ar-Dinthalion said:
Thanks , I know physics are cool xD
Click to expand...
Click to collapse
Quark quark

drive2droad said:
My new favorite gapps !!
Click to expand...
Click to collapse
parasthakur37 said:
Quark quark
Click to expand...
Click to collapse
Hey! Thanks! It's good to have nice feedback, I feel charmed xD

Ar-Dinthalion said:
Hey! Thanks! It's good to have nice feedback, I feel charmed xD
Click to expand...
Click to collapse
Hahaha right

Hi
installed with pleasure on galaxy tab pro 10.1 & rom 5.1 cyano
can these gapps be updated on google play
thanx
regards

@Ar-Dinthalion hi, I have a moto g 2014 and tried to edit the updater-script removing some apps from being deleted but i can't flash my edited version of black hole debloat. I get the following error: Error executing updater binary.
things iv'e tried:
1. signing zip
2. using my rom (CM12.1 official) binary
3. using another rom binary
pd. the unedited version of black hole work's. :good:
this is what i have in the updater-script
Code:
ui_print("");
ui_print("Fermion Gapps for Android 5.1.x");
ui_print("");
ui_print("Package: Debloating Script");
ui_print("Updated: 12-04-2015");
show_progress(1, 15);
ui_print("-Unmounting system partition");
run_program("/sbin/busybox", "umount", "/system");
ui_print("-Mounting system partition");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
ui_print("-Sending bloatware to a blackhole");
delete_recursive(
"/system/app/BasicDreams",
"/system/app/Browser",
"/system/app/Camera2",
"/system/app/Calendar",
"/system/app/Calculator",
"/system/app/CMWallpapers",
"/system/app/DownloadProviderUi",
"/system/app/Eleven",
"/system/app/Email",
"/system/app/Exchange2",
"/system/app/FM2",
"/system/app/FMRecord",
"/system/app/Galaxy4",
"/system/app/Gallery2",
"/system/app/HoloSpiralWallpaper",
"/system/app/HTMLViewer",
"/system/app/LatinIME",
"/system/app/LiveWallpapers",
"/system/app/LiveWallpapersPicker",
"/system/app/NoiseField",
"/system/app/PhaseBeam",
"/system/app/PhotoPhase",
"/system/app/PhotoTable",
"/system/app/PicoTts",
"/system/app/SoundRecorder",
"/system/app/STK",
"/system/app/VisualizationWallpapers"
);
delete_recursive(
"/system/priv-app/AudioFX",
"/system/priv-app/CalendarProvider",
"/system/priv-app/CellBroadcastReceiver",
);
show_progress(1, 15);
set_metadata_recursive("/system/addon.d", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/app", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/etc/permissions", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/etc/preferred-apps", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/framework", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/priv-app", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
ui_print("-Unmounting system partition");
run_program("/sbin/busybox", "umount", "/system");
ui_print("");
ui_print("Done debloating your ROM!");
any help is greatly appreciated, thank's

Ar-Dinthalion said:
Yes, its known that those Gapps aren't compatible with Dual-Sim services, so please don't use them for devices like Moto G, if you have the problem PM and I'll send you an AOSP messenger apk, I'm trying to create a acript that avoid uninstall of specified apps by the user, like the PA Gapps did, but it will take me some more days
Click to expand...
Click to collapse
With the last CM12.1 updates Google Messenger become compatible with dual Sim phones... At least with Moto G 2014, that is true...

validatus said:
Hi
installed with pleasure on galaxy tab pro 10.1 & rom 5.1 cyano
can these gapps be updated on google play
thanx
regards
Click to expand...
Click to collapse
Thanks!, Sure! But there is a problem that when the data/app is moved to system/app the OS don't recognise it, you can do it, but before installing the updated zip uninstall them directly from Play Site and it should work
blind_rodro said:
@Ar-Dinthalion hi, I have a moto g 2014 and tried to edit the updater-script removing some apps from being deleted but i can't flash my edited version of black hole debloat. I get the following error: Error executing updater binary.
things iv'e tried:
1. signing zip
2. using my rom (CM12.1 official) binary
3. using another rom binary
pd. the unedited version of black hole work's. :good:
this is what i have in the updater-script
Code:
ui_print("");
ui_print("Fermion Gapps for Android 5.1.x");
ui_print("");
ui_print("Package: Debloating Script");
ui_print("Updated: 12-04-2015");
show_progress(1, 15);
ui_print("-Unmounting system partition");
run_program("/sbin/busybox", "umount", "/system");
ui_print("-Mounting system partition");
run_program("/sbin/busybox", "mount", "/system");
show_progress(1, 15);
ui_print("-Sending bloatware to a blackhole");
delete_recursive(
"/system/app/BasicDreams",
"/system/app/Browser",
"/system/app/Camera2",
"/system/app/Calendar",
"/system/app/Calculator",
"/system/app/CMWallpapers",
"/system/app/DownloadProviderUi",
"/system/app/Eleven",
"/system/app/Email",
"/system/app/Exchange2",
"/system/app/FM2",
"/system/app/FMRecord",
"/system/app/Galaxy4",
"/system/app/Gallery2",
"/system/app/HoloSpiralWallpaper",
"/system/app/HTMLViewer",
"/system/app/LatinIME",
"/system/app/LiveWallpapers",
"/system/app/LiveWallpapersPicker",
"/system/app/NoiseField",
"/system/app/PhaseBeam",
"/system/app/PhotoPhase",
"/system/app/PhotoTable",
"/system/app/PicoTts",
"/system/app/SoundRecorder",
"/system/app/STK",
"/system/app/VisualizationWallpapers"
);
delete_recursive(
"/system/priv-app/AudioFX",
"/system/priv-app/CalendarProvider",
"/system/priv-app/CellBroadcastReceiver",
);
show_progress(1, 15);
set_metadata_recursive("/system/addon.d", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/app", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/etc/permissions", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/etc/preferred-apps", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/framework", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
set_metadata_recursive("/system/priv-app", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644, "capabilities", 0x0, "selabel", "u:object_r:system_file:s0");
ui_print("-Unmounting system partition");
run_program("/sbin/busybox", "umount", "/system");
ui_print("");
ui_print("Done debloating your ROM!");
any help is greatly appreciated, thank's
Click to expand...
Click to collapse
Hi, please PM me and I help you
mundano said:
With the last CM12.1 updates Google Messenger become compatible with dual Sim phones... At least with Moto G 2014, that is true...
Click to expand...
Click to collapse
Great, good to hear that news! Thanks!

thanks for the gapps package update !! would there be a separate package for 5.1.1 or it will be the same as 5.1 ?

Clean android ROMs?

Hey
thinking about buying that phone
but I hate MIUI
is there clean android roms for that phone?
how about updates to the roms over time?

Right now we have LineageOS and Paranoid Android, both in Beta stage.
Development is slow.
I'm using Havoc OS (built for the Redmi K20 Pro, I made it work in this device tho).

Schnedi said:
Right now we have LineageOS and Paranoid Android, both in Beta stage.
Development is slow.
I'm using Havoc OS (built for the Redmi K20 Pro, I made it work in this device tho).
Click to expand...
Click to collapse
Hello,
Can you tell how you managed to port rom on MI 9T? Because I used your guide but TWRP still tells me it's a rom for Raphael device

isman77 said:
Hello,
Can you tell how you managed to port rom on MI 9T? Because I used your guide but TWRP still tells me it's a rom for Raphael device
Click to expand...
Click to collapse
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
{
"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"
}
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system

Schnedi said:
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system
Click to expand...
Click to collapse
I can do this with EVERY rom from the Pro variant ?

FroZine said:
I can do this with EVERY rom from the Pro variant ?
Click to expand...
Click to collapse
Yes, I've tried Havoc, Evolution, Pixel Experience and AOSIP.
Unfortunately, if the kernel has an extra feature (DT2W for example) we won't have it.
Kernel is inside the boot.img and if we flash it, the phone will go into a bootloop.

Schnedi said:
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system
Click to expand...
Click to collapse
can you post a link with you'r zip of the rom? for a noob like me in this materie. thxs
Verstuurd vanaf mijn Mi 9T met Tapatalk
---------- Post added at 11:06 AM ---------- Previous post was at 10:55 AM ----------
lets try it by myzelf[emoji3577]
Verstuurd vanaf mijn Mi 9T met Tapatalk

Is it really necessary to format data ?

do i deleted al this lines that yoy show in you file?
Verstuurd vanaf mijn Mi 9T met Tapatalk

beaverhead said:
do i deleted al this lines that yoy show in you file?
Verstuurd vanaf mijn Mi 9T met Tapatalk
Click to expand...
Click to collapse
delete these:
assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");
(The first 2 lines)

Schnedi said:
Hi.
It's very easy to do.
• Download the ROM
• Uncompress it to get this
• Delete the 2 files hightlighted red
• Open the one highlighted green
• Delete the first 2 lines
Code:
[COLOR="DarkRed"]assert(getprop("ro.product.device") == "raphael" || getprop("ro.build.product") == "raphael" || abort("E3004: This package is for device: raphael; this device is " + getprop("ro.product.device") + "."););
ui_print("Target: Xiaomi/raphael/raphael:9/PKQ1.181121.001/V10.3.16.0.PFKCNXM:user/release-keys");[/COLOR]
ifelse(is_mounted("/system_root"), unmount("/system_root"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
.......................................
.....................
.........
• Save
• Compress all the files and folders
Installation
• Boot to TWRP
• Format data (after this, move the files to your phone or use an USB OTG)
• Restart TWRP
• Install the ROM
• Factory reset
• Restart TWRP
• Install GApps
• Install Magisk
• Reboot to system
Click to expand...
Click to collapse
Thanks for the great tip, I really appreciate Havoc. I immediately tried the installation, but unfortunately I ended up in a bootloop (at the start of Havoc). My old installation was Global Stable 10.3.11, I used the Russian TWRP. The reinstallation of the Global Stable worked without any problems.
What else could I do to install the Havoc?

limuc said:
Thanks for the great tip, I really appreciate Havoc. I immediately tried the installation, but unfortunately I ended up in a bootloop (at the start of Havoc). My old installation was Global Stable 10.3.11, I used the Russian TWRP. The reinstallation of the Global Stable worked without any problems.
What else could I do to install the Havoc?
Click to expand...
Click to collapse
You flashed 10.3.11 zip rom from twrp after flashig havoc?

limuc said:
Thanks for the great tip, I really appreciate Havoc. I immediately tried the installation, but unfortunately I ended up in a bootloop (at the start of Havoc). My old installation was Global Stable 10.3.11, I used the Russian TWRP. The reinstallation of the Global Stable worked without any problems.
What else could I do to install the Havoc?
Click to expand...
Click to collapse
I think could be caused by SeLinux, try flashing thos file https://androidfilehost.com/?fid=6006931924117886495 after flashing everything else.

epicblue8 said:
You flashed 10.3.11 zip rom from twrp after flashig havoc?
Click to expand...
Click to collapse
Yes, exactly! With wipe and format data, after install, I reboot to recovery, then magisk, then reboot to recovery, then start system.

Schnedi said:
I think could be caused by SeLinux, try flashing thos file https://androidfilehost.com/?fid=6006931924117886495 after flashing everything else.
Click to expand...
Click to collapse
Thanks, that was a great idea! The installation worked fine, but Magisk reports 'cts profile false'. Gpay can't be set up with Paypal either (it worked with the old 'Stable').
When restarting, Havoc reports that the vendor does not match the system, but still starts.
And the BEST: I now have a K20 pro....

Schnedi said:
Right now we have LineageOS and Paranoid Android, both in Beta stage.
Development is slow.
I'm using Havoc OS (built for the Redmi K20 Pro, I made it work in this device tho).
Click to expand...
Click to collapse
And does everything work? the camera and Fingerprint reader?