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?
Related
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.
{
"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 Update1. 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 ?
Hello everyone!
After finally figuring out how to boot into TWRP on the norwegian version of this device, I was crazy with exitement about flashing blisspoprom, but I get this error message:
This package supports bootloader (s) T530XXU1B0D8, T530NUUEU1B0E5; this device has bootloader T530XXU1B0G2
I have flashed a lot of devices, but I haven't really looked into bootloaders., as I've never encountered this problem before.
Is it possible to replace the bootloader on my device at all? Or are there version of the ROM out there that supports my bootloader?
N00b questions, indeed, but it's proven quite hard to find information on google searches on this subject, and everything I've found seems to be device specific. I tried to flash stock with bootloader update checked in Odin, but that didnæt change the bootloader number...
Open the rom file in 7zip or WinRar, go to META-INF/com/Google/Android and open the updater-script with notepad++. Delete the first line of the updater-script (it should have the word "assert" in it ". Save it and now try flashing the rom
thisisapoorusernamechoice said:
Open the rom file in 7zip or WinRar, go to META-INF/com/Google/Android and open the updater-script with notepad++. Delete the first line of the updater-script (it should have the word "assert" in it ". Save it and now try flashing the rom
Click to expand...
Click to collapse
Thank you sir! Much appreciated.
I got the file open in Notepad, would it be awfully blunt of me to ask you how much of this I need to delete? There's two lines starting with "assert" so I thought It would be safest to ask.
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
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);
....
MadBigMadBoatMan said:
Thank you sir! Much appreciated.
I got the file open in Notepad, would it be awfully blunt of me to ask you how much of this I need to delete? There's two lines starting with "assert" so I thought It would be safest to ask.
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
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);
....
Click to expand...
Click to collapse
Delete the following:
"assert(getprop("ro.product.device") == "matissewifi" || getprop("ro.build.product") == "matissewifi" || abort("This package is for device: matissewifi; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "T530XXU1BOD8" || getprop("ro.bootloader") == "T530NUUEU1BOE5" || abort("This package supports bootloader(s): T530XXU1BOD8, T530NUUEU1BOE5; this device has bootloader " + getprop("ro.bootloader") + ".");
Click to expand...
Click to collapse
Leave everything beginning with package_extract_dir("install", '/tmp/install");
Also just making sure, you are using the latest version of BlissPop, correct? Located here, you want the one named BlissPop-v4.0.1-matissewifi-UNOFFICIAL-20150917-1958.zip (note you want the one dated 20150917, not the one dated 20150912).
Also I'd recommend using notepad++ rather than regular notepad, idk if that's absolutely necessary, just a recommendation
thisisapoorusernamechoice said:
Delete the following:
Leave everything beginning with package_extract_dir("install", '/tmp/install");
Also just making sure, you are using the latest version of BlissPop, correct? Located here, you want the one named BlissPop-v4.0.1-matissewifi-UNOFFICIAL-20150917-1958.zip (note you want the one dated 20150917, not the one dated 20150912).
Also I'd recommend using notepad++ rather than regular notepad, idk if that's absolutely necessary, just a recommendation
Click to expand...
Click to collapse
Flashing!
4.0 for now, didn't want to wait for another download. I'll try 4.0.1 if there's any hithches. And, regular notepad seems to have done the trick, I hadn't heard of ++ before but I'll check it out.
I make it short. Actually are Xperia Devices unable to run AOSP without using fastboot to flash the OEM Images from SONY. I wanted to create a empty ZIP containing a Updater Script who flashes the OEM Images after placing them into the ZIP. The Problem is that i was unable to find the OEM Partition. Is anyone aware of it? I'm searching for the "/dev/block/platform/*/by-name/" to use a command like this "package_extract_file("boot.img", file_getprop("/tmp/config", "boot"));"
And for the People who are wondering why the ZIP has to be empty. There are two Reasons. First, all Devices need own Images, besides that they are getting updated from Time to Time.
The second thing is the Legal Stuff. SONY added a Agreement before You can download the Images. Every User has to accept that, otherwise would we get trouble with them.
Just to clear that out already. Hope we can quickly make the flashing more handy for the Future!
And Dear Moderators, pls don't move this Thread. It will be edited and extended after creating the ZIP to share it right here!
Why not just add /oem flash image to ota-zip (or twrp?)?
Miustone said:
I make it short. Actually are Xperia Devices unable to run AOSP without using fastboot to flash the OEM Images from SONY....
And Dear Moderators, pls don't move this Thread. It will be edited and extended after creating the ZIP to share it right here!
Click to expand...
Click to collapse
{make otapackage} works 100% on xz1 Xperiadev natural aosp; it even comes with an odd aosp/recovery embedded : thus better to FIRST make clean +make bootimage and save it to avoid final embedded recovery. The /vendor img is also included in the ota zip.
If you want to add addon.d support check my Los15 "extracted" https://forum.xda-developers.com/an...zip-custom-t3173316/post76455910#post76455910
Than just repack the final ota zip package with them (including Los15 update-binary).
If you want WidevineDRM L3 (check XZ1 attached txt) you need to add specifics drm/vendors in /vendor prior to build; alternatively for Magisk users, you can instead repack them in final ota zip, but they will only be active after Magisk install. Source https://github.com/DirtyUnicorns/an...3d1555c#diff-daceb2a2ce86bd2430773e29f2b3db5e
To avoid Firebase analytics in Webview , I also suggest using Lineage15 pre-pack 66 version (arm64) https://github.com/LineageOS/android_external_chromium-webview/tree/lineage-15.1/prebuilt
Don't forget MicroG patches https://forum.xda-developers.com/showpost.php?p=75320072&postcount=4319 ...
Code:
[SIZE="1"][I]'bolded is added'[/I]
getprop("ro.product.device") == "poplar" || abort("E3004: This package is for \"poplar\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Sony/aosp_g8341/poplar:8.1.0/OPM2.171019.029/nn04300157:userdebug/dev-keys");
[B]ifelse(is_mounted("/system"), unmount("/system"));
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);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
[/B]show_progress(0.650000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
[B]mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
[/B]
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
[B]mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/vendor", "/vendor", "");
package_extract_dir("vendor", "/vendor");
unmount("/vendor");
[/B]show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
[/SIZE]
EDIT @Miustone , aosp xperiadev mostly use /odm instead of /oem for /dev/block/bootdevice/by-name/oem (sda63 on xz1), but fastboot always -> oem
(1000Thx @jerpelea )
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!