Related
/system/addon.d/ is a folder in CM roms where the user (and sometimes apps) can put scripts that will be run when you flash a new version of the rom.
Tipically those scripts are used to backup system apps, and their files, so that they can survive a format and reflash.
For example, this is how you would keep SuperSU (root), Avast Agent,...
I made the script below so that @rovo89's Xposed for Lollipop will survive (that is keep it installed) when I flash a new CM12 nightly.
Tested on my phone (32bits), just flashed latest CM12 nightly, wiped cache and dalvik-cache and the phone rebooted fine (and Xposed was still working). Tested on TWRP 2.8.5.1, might not work with other recovery.
Warning: It's for Xposed for Lollipop only. It work as of today. It might not work later with new future versions of Xposed. Also not sure it would work for 64bits.
Download script only:
If you use SuperSu:
81-Xposed.sh
Or flashable zip, see post attachment below:
If you don't use SuperSu, see and flash this other version by DualJoe, see http://forum.xda-developers.com/showthread.php?p=59199445.
So to clarify, this works when you dirty flash? But if you clean flash you need to set everything up again?
click here for my device info:
~~~~~~~~~~~~~~~~~~
DEVICE: SM-N900W8
ROM: Temasek's CM12 v7.7
BASEBAND: N900W8VLUCNI1
KERNEL: 3.4.106-f2fs-temasek-cm12-hlte-v0.66+
RECOVERY: TWRP 2.8.5.0 hlte
XPOSED? YEAH BABY!
vanisleguy1976 said:
So to clarify, this works when you dirty flash? But if you clean flash you need to set everything up again?
click here for my device info:
~~~~~~~~~~~~~~~~~~
DEVICE: SM-N900W8
ROM: Temasek's CM12 v7.7
BASEBAND: N900W8VLUCNI1
KERNEL: 3.4.106-f2fs-temasek-cm12-hlte-v0.66+
RECOVERY: TWRP 2.8.5.0 hlte
XPOSED? YEAH BABY!
Click to expand...
Click to collapse
That's indeed a very good question ?.
Yes, I use it when dirty flashing, primarily to save time and streamline the process, that is, I avoid having to flash the Xposed zip over again.
If you do a clean flash (ie. with a wipe data) I think it should keep all the stuff in place (all the stuff installed by the Xposed zip). In that case thought, you'll need to reinstall the Xposed Installer, as well as all the modules you add. In that case you wouldn't really save much time I believe.
Sent from my OnePlus One using Tapatalk
And if real clean flash as like wipe system, it won't survive..
But for dirty it's great, going into recovery as writing it, thanks you..
reemar said:
And if real clean flash as like wipe system, it won't survive..
But for dirty it's great, going into recovery as writing it, thanks you..
Click to expand...
Click to collapse
Yeah, true, if you wipe system you remove that whole addon.d folder, which is good (might be needed).
Yes, it's basically for those who flash Nightlies every now and then (which don't require wiping more than cache and dalvik).
Sent from my OnePlus One using Tapatalk
adlx.xda said:
That's indeed a very good question ?.
Yes, I use it when dirty flashing, primarily to save time and streamline the process, that is, I avoid having to flash the Xposed zip over again.
If you do a clean flash (ie. with a wipe data) I think it should keep all the stuff in place (all the stuff installed by the Xposed zip). In that case thought, you'll need to reinstall the Xposed Installer, as well as all the modules you add. In that case you wouldn't really save much time I believe.
Sent from my OnePlus One using Tapatalk
Click to expand...
Click to collapse
I'll have to wait till Temasek comes back from holidays before I can test this
adlx.xda said:
/system/addon.d/ is a folder in CM roms where the user (and sometimes apps) can put scripts that will be run when you flash a new version of the rom.
Tipically those scripts are used to backup system apps, and their files, so that they can survive a format and reflash.
For example, this is how you would keep SuperSU (root), Avast Agent,...
I made the script below so that @rovo89's Xposed for Lollipop will survive (that is keep it installed) when I flash a new CM12 nightly.
Tested on my phone (32bits), just flashed latest CM12 nightly, wiped cache and dalvik-cache and the phone rebooted fine (and Xposed was still working). Tested on TWRP 2.8.5.1, might not work with other recovery.
Warning: It's for Xposed for Lollipop only. It work as of today. It might not work later with new future versions of Xposed. Also not sure it would work for 64bits.
Download script only: 81-Xposed.sh
Or flashable zip, see post attachment below:
Click to expand...
Click to collapse
I have some questions, please forgive my lack of knowledge.
How do you get the script into the addon folder in the CM nightly?
Also, do you know if it can be used in conjunction with Cyandelta updater?
Thnx, Alex
alexdpaul said:
I have some questions, please forgive my lack of knowledge.
How do you get the script into the addon folder in the CM nightly?
Also, do you know if it can be used in conjunction with Cyandelta updater?
Thnx, Alex
Click to expand...
Click to collapse
Just flash the zip in the fist post. This will install the script in the right place in your phone. After that you can flash Nightlies like you always do, manually or with Cyandelta (I use Cyandelta myself too).
You just have to flash the script once, it will also survive future flashes.
Sent from my OnePlus One using Tapatalk
adlx.xda said:
Just flash the zip in the fist post. This will install the script in the right place in your phone. After that you can flash Nightlies like you always do, manually or with Cyandelta (I use Cyandelta myself too).
You just have to flash the script once, it will also survive future flashes.
Sent from my OnePlus One using Tapatalk
Click to expand...
Click to collapse
Thanks, flashed the zip, just need to wait for the next nightly to see if it works for me.
Thanks for your quick reply!
You're missing at least one file (app_process32):
Code:
localhost bin # ls -l |grep app_
lrwxr-xr-x 1 root shell 13 Feb 23 20:53 app_process -> app_process32
lrwxrwxrwx 1 root root 32 Feb 24 17:36 app_process32 -> /system/bin/app_process32_xposed
-rwxr-xr-x 1 root shell 13664 Feb 23 20:53 app_process32_original
-rwxr-xr-x 1 root shell 72757 Feb 24 17:36 app_process32_xposed
DualJoe said:
You're missing at least one file (app_process32):
Code:
localhost bin # ls -l |grep app_
lrwxr-xr-x 1 root shell 13 Feb 23 20:53 app_process -> app_process32
lrwxrwxrwx 1 root root 32 Feb 24 17:36 app_process32 -> /system/bin/app_process32_xposed
-rwxr-xr-x 1 root shell 13664 Feb 23 20:53 app_process32_original
-rwxr-xr-x 1 root shell 72757 Feb 24 17:36 app_process32_xposed
Click to expand...
Click to collapse
I've been flashing various nightly and Xposed has survived all of them, so it works for me, no file missing as far as I can tell.
On my phone app_process32 is modified by SuperSu, and flash survival is handled by SuperSu script in addon.d (99-supersu.sh).
Sent from my OnePlus One using Tapatalk
adlx.xda said:
/system/addon.d/ is a folder in CM roms where the user (and sometimes apps) can put scripts that will be run when you flash a new version of the rom.
Tipically those scripts are used to backup system apps, and their files, so that they can survive a format and reflash.
For example, this is how you would keep SuperSU (root), Avast Agent,...
I made the script below so that @rovo89's Xposed for Lollipop will survive (that is keep it installed) when I flash a new CM12 nightly.
Tested on my phone (32bits), just flashed latest CM12 nightly, wiped cache and dalvik-cache and the phone rebooted fine (and Xposed was still working). Tested on TWRP 2.8.5.1, might not work with other recovery.
Warning: It's for Xposed for Lollipop only. It work as of today. It might not work later with new future versions of Xposed. Also not sure it would work for 64bits.
Download script only: 81-Xposed.sh
Or flashable zip, see post attachment below:
Click to expand...
Click to collapse
Work for me cm12(32bit) thx
Nice, it's work on my Xperia Z1 with CM12.
Not working for me on Oneplus One CM12, the XposedBridge.jar survives but not app_process, the OnePlus One has an ARM v7, so what do I need to modify in the config file?
card13 said:
Not working for me on Oneplus One CM12, the XposedBridge.jar survives but not app_process, the OnePlus One has an ARM v7, so what do I need to modify in the config file?
Click to expand...
Click to collapse
I also have a Oneplus One.
Do you have SuperSu? Go in SuperSu settings and check if you have installed the script to survive flashes.
Sent from my OnePlus One using Tapatalk
I don't have SuperSu, haven't used that since the nightlies became official and builtin su was working properly.
card13 said:
I don't have SuperSu, haven't used that since the nightlies became official and builtin su was working properly.
Click to expand...
Click to collapse
Ok, that's the reason why it fails for you then... I'll have to work that our then.
Sent from my OnePlus One using Tapatalk
How unistall this?
Rygiel98 said:
How unistall this?
Click to expand...
Click to collapse
Uninstall? Remove the file /system/addon.d/81-xposed.sh from your system.
Sent from my OnePlus One using Tapatalk
card13 said:
Not working for me on Oneplus One CM12, the XposedBridge.jar survives but not app_process, the OnePlus One has an ARM v7, so what do I need to modify in the config file?
Click to expand...
Click to collapse
Here is a fixed version.
Added entry:
[...]
list_files() {
cat <<EOF
bin/app_process32
bin/app_process32_xposed
bin/dex2oat
bin/oatdump
[...]
Click to expand...
Click to collapse
Special thanks to @funkyboy1281, @lentm, @macboy3000 for helping getting this work. As far as I can tell, this is the easiest and most straight forward instruction set for getting Android Pay to work on the latest version of Pure Nexus, Chroma, or OMNI Rom
Clean Flashing
Download the appropriate Rom.
Pure Nexus DiscussionChroma DiscussionOMNI (no link available, sorry)
Download Pure Nexus Dynamic Gapps 2-3-16 (Very important, you cannot use 15-3-16 or later). Yes, even if you use Chroma or OMNI, these Gapps should work for you. Link
Download the unSU script for completely unrooting before installing systemless root. Link
Download SuperSU 2.68 (or higher) Link || Discussion
Advance wipe in recovery all but internal storage
Install the ROM, gapps, and unSU
Optional: Install custom kernel
In TWRP, under advanced, go to terminal and type the following:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Note: You may also do this using ADB in recovery (adb shell, and then enter the same commands. This is much easier in my opinion, and is the method I used.
Flash 2.68 beta in TWRP
Fully reboot, go through initial device setup
Verify in SuperSU that you cannot install SU to the system. This will verify that we are using the systemless root option
Download SafetyNet Helper and make sure it passes
Install Android Pay and profit!
Dirty Flashing
Verify that SafetyNet still passes in Android.
Verify in Android that /data/.supersu is still present and contains the appropriate options (see clean flashing). You may also verify in recovery by going to terminal commands and entering in:
Code:
cat /data/.supersu
Install the updated ROM (do not reinstall gapps unless your ROM builder specifically tells you to do so. Pure nexus does not require a reflash)
Optional: Install unSU. This was not necessary on PureNexus, but I cannot be sure for other roms. It shouldn't hurt anything to flash.
Optional: Install custom kernel
Install SuperSu 2.68 (or higher)
Check SafetyNet Helper and make sure it still passes
FAQ
Q. Can I still install and use AdAway?
A. Yes. You must first install something in recovery before installing AdAway. See the discussion Thread. You should be installing v3.1 of the app after you install the recovery zip.
Q. Can I still use V4A?
A. Yes. I do not use this however, but it has been reported that nothing special needs to be done.
Q. Can I change the screen density?
A. We have not found a way to do this without tripping Safety Net
..
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
MrBrady said:
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
Click to expand...
Click to collapse
Noted, thank you! Still hoping some of the lucky folks that have it working can help us out here.
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
MrBrady said:
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
Click to expand...
Click to collapse
You (should) be able to change the density through adb using
Code:
adb shell wm density DPI
with dpi being what you want, or if you have root you can do that from a terminal emulator, just remove the adb shell part.
I tried the 2nd method without formating data in different combos to no avail, still hesitant to wipe my internal sdcard, it shouldn't be that hard man, will follow this thread
anyone know other aosp ROMs that have AP working outside of pure nexus?
Sent from my Nexus 6 using Tapatalk
Following the steps in the top most instructions in the OP...
1) Pure Nexus 3/8 does not have root out of the box, so the Unroot step was not needed.
2) TWRP did not show any files/folders in the /su directory, so the Terminal command didn't work. I booted up the device and did it through the Terminal there instead and then rebooted.
After that, loaded up Android Pay and it says "Android Pay can't be used".
Running SafetyNet reports....
SafteyNet request: success
Response validation: success
CTS profile match: false
Tried different methods, not working for me.
1. Download Pure Nexus 1/03/16 or newer (Layers), the latest PN GApps, UnSU, the latest SuperSU.
2. Backup any important data.
3. Boot into TWRP and wipe everything including internal storage
4. Format data.
5. reboot TWRP with USB-OTG that has fines necessary.
6. Flash Pure Nexus.
7. Flash GApps.
8. Flash UnSU.
9. In terminal I saw I still had a folder /supersu so I deleted that.
reboot. Setup phone with google account. Did not have it restore apps, but did have it restore basic setup from google.
Install Safetynet helper
Still fail CTS Profile Match
Don't know what the people are doing different, but not working for me.
Are you using the PN-Gapps or others?
The updated-unsu is what date?
Thanks!
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
macboy3000 said:
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
Click to expand...
Click to collapse
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I formatted everything except internal storage before installing.
macboy3000 said:
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
Click to expand...
Click to collapse
Well I tried this and still no luck
I even tried flashing the modified ROM, gapps, and never flashing SuperSU at all (so my rom wasn't rooted at all), and SafetyNet still gives me a red screen. I really wish I knew what was triggering this for some and how others can make it work.
I tried again using 2.57 SuperSU and Elemental X and still fails. Would someone that got it working be able to post a more detailed log of exactly what steps you're using and exactly what files you're flashing.
MrBrady said:
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
Click to expand...
Click to collapse
This has been my experience as well !
jcrompton said:
This has been my experience as well !
Click to expand...
Click to collapse
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
lentm said:
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
Click to expand...
Click to collapse
Not that I have found, unfortunately. Even via just ADB commands.
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Link_of_Hyrule said:
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Click to expand...
Click to collapse
Ummm...
That makes no sense...
The magisk.img is in data... Survives dirty flash... The magical part of magisk... Is injected into the boot.img... Which, afaik, isn't possible via addon.d
Link_of_Hyrule said:
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Click to expand...
Click to collapse
That makes no sense like the other guy said & only works with ROMs that have implemented that function (generally update-script that calls a script in root of the zip in CyanogenMods). If you install any ROM that have not that function, then nothing is backed up & /system is replaced as regular.
Addon.d is simply a folder with .sh scripts that are run when flashing a new rom update. Obviously, this won't work with stock roms but it should work for Lineage OS and similar roms I think. Sadly I don't know how to write .sh scripts.
Link_of_Hyrule said:
Addon.d is simply a folder with .sh scripts that are run when flashing a new rom update. Obviously, this won't work with stock roms but it should work for Lineage OS and similar roms I think. Sadly I don't know how to write .sh scripts.
Click to expand...
Click to collapse
Learn Bash, is easy to do like check how works other .sh scripts or if you are lazy search tutorials in Google xD...
Old thread, but I just discovered this "Flash After Update" script (actually @osm0sis pointed it out to me) which will flash any zip in a designated folder after flashing rom update.
osm0sis said:
99-flashafterupdate.sh addon.d script (many devices) - attached
For ROMs that don't have "Flash After Update" support built into their delta/update process. During an upgrade, this script will flash zips from a sdcard directory after all other addon.d backup/restore actions have completed. This can be used to flash SuperSU and then an AnyKernel2 kernel on CyanogenMod, for example. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
Click to expand...
Click to collapse
Especially handy if you keep your device unrooted, and can't use a tool such as this:
https://play.google.com/store/apps/details?id=se.davison.autoflasher
Link_of_Hyrule said:
Is there anyway someone can make an addon.d script for both magisk and the phh root? There's a similar script that you can find here that does this for xposed. Also, the Gapps use it. This would be very helpful so we don't have to reflash the scripts everytime.
Click to expand...
Click to collapse
Have a look at this:
https://github.com/topjohnwu/Magisk/issues/175
So is he integration the feature directly into Magisk?
Why don't you submit the changes as a pull request?
Edit: Tested the script. I can use the official Lineage OS updater now! No need for a third party app to auto flash Magisk want update.
Sent from my Nexus 7 using Tapatalk
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2 + John Miller . The Lineage part is @XePeleato and the Aosp of @haky86.
Too much for you?
More novice users should not be scared because the installation and configuration is incremental and that is why I say that it fits any user profile.
User Profiles:
Depending on the concerns that are most suited to your profile you should take the installation to the point that best meets your needs.
As a user I want ...
1- I want a stock experience with some extras but without Root.
You must install the rom file by TWRP and dot. The rom is the same as the cerberus V2 but comes with no root.
It incorporates among others ..., gyroscope, call recording, multiwindow ...
REQUIRED REQUIREMENTS:
-Bootloader Unlocked.
-TWRP
- Android 6 - C432B594 Stock - Recommended.
2- I want you to have root access too.
After installing the rom you must enter the store and download the application magisk manager and ready. You already have root access and get the most out of the rom, but not only that, but root access can be hidden to play PoGo or use payment applications and pass the SafetyNet test.
3- I want to activate extra functions and transform and customize the rom butt.
Well what you have to do is install this file from TWRP point.
We will achieve the following:
- Activate Multiuser
- Enable Local Update
- You can choose whether to install the Huawei magnifier or not
- Busybox, Viper4Android and SLC disappear
- You can choose to install the busybox and the viper in a systemless way and in this way the SLC is no longer necessary
- Advanced Reset
- New lock screen 100% customizable.
- The screen automatically turns on and off when opening and closing the mobile phone case
- Incorporates system apps uninstaller
- Total Commander
- Greenify
- Etc...
4- I want to be able to choose which rom to start the smartphone.
For that it is necessary to have followed steps 1, 2 and 3 and it is necessary to configure magisk to have default access to all requests per adb and applications and install the multiboot option.
To install Dualboot you must go to the file EXTRAS.ZIP that you will find inside the system folder of the rom. Uncompress your content in the external memory and install the DualBoot app and keep the files in memory because we will need them for later.
Then we start the dualboot application to be granted superuser permissions automatically. Then with SimpleReboot we restart a recovery and make a backup of boot.img in case something goes wrong, since it will be the only thing we will need to repair a possible failure or error.
VERY IMPORTANT: We need to have 3Gb of available space in the External SD for each additional rom we want to install, that is, if we are going to install Lineage and Aosp we will need 6Gb of available space.
4.1- I want AOSP.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.1- I want LineageOS.
We must download these files and install them at the same time and in order from TWRP
- Rom
- Aniboot
- Gaaps
- Magisk
4.3 I want the 3 Roms at a time.
Then follow steps 4.1 and 4.2
Restarting the system will take us directly to the last ROM installed. Once started and configured we installed the dualboot app that we had left on hand in the external SD. Repeat the operation on each of the additional roms installed. Once installed dualboot in all you can remove the app from the sd and of course all the corresponding installation files.
To change rom you have to enter the dualboot app and choose which one to start the system and restart.
MENTAL NOTE 01:
The 3 roms will have the same bugs as the originals. I am not yet qualified to fix them or even try, but I think that to be my first job is more than enough.
MENTAL NOTE 02:
The DualBoot application also installs an app called Leaks that controls possible bugs to send them to the original DualBoot developer.
I do not want to forget to give credits and thanks for:
@topjohnwu for creating magisk
@chenxiaolong for creating DualBoot and @BrainNotFound for portarlo
+ John Miller to create CerberusV2
@haky86 for creating Aosp and CWMR
@XePeleato for creating LineageOs and TWRP and Kernel
Greetings from Barcelona (Catalonia)
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Please delete, XDA app crashed while writing
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
Multi-rom Tripl3t is the first rom for pecholite that adapts to all types of users and allows to start the smartphone with Emui 4.0, LineageOS 14.1 or AOSP 7.1.1 (Nougat).
I present my first custom rom based on fellow cerberus v2
Click to expand...
Click to collapse
Link please :laugh::laugh::good::good:
kilroystyx said:
Link please :laugh::laugh::good::good:
Click to expand...
Click to collapse
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Fedroid said:
MULTI-ROM TRIPL3T B594 ODEX
http://pecholite.blogspot.com.es/2017/03/multi-rom-tripl3t-b594-odex.html?m=1
Click to expand...
Click to collapse
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
hi6120sft ale-l21 said:
Why in the screenshots there is a ss with a lockscreen asking for a fingerprint to unlock? I know that no P8Lite has a fingerprint sensor
Click to expand...
Click to collapse
Because it is cool, no more reasons sorry
I stucked on a first logo
blewko said:
I stucked on a first logo
Click to expand...
Click to collapse
Try a factory reset with stock recovery and flash again.
It helps in most cases
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
he should work... i have magisk and xposed but on C432B596 ROM
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
xander33 said:
he should work... i have magisk and xposed but on C432B596 ROM
Click to expand...
Click to collapse
Are you passing Safety net?
arviit said:
Does Xposed from Magisk work on our device?
I tried, but it stucks at boot logo.
Click to expand...
Click to collapse
It works. Flash Xposed and don't forget to wipe cache.
Phone will start in about 30 minutes.
It works. Use SDK 23 for this rom
Vinnipinni said:
It worked for me once but I think I reflashed something or so and then it didn't. After flashing it wait at least 1 hour before stopping the boot. After that, it doesn't seem to work.
Are you passing Safety net?
Click to expand...
Click to collapse
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
xander33 said:
No with the B596 ROM (i think its related to the new security patch)
With the B588 instead you have to disable xposed reboot the phone and safety net will be ok
Click to expand...
Click to collapse
I can confirm Xposed works. Not the Magisk one though.
Use the one from the mega root thread https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994.
I also know the xposed torch works. Like to recommend xEmui module.
I made small changes based v2
Suitable with OOS OB13 with Project Treble.
No need to mount any specific partitions (in recovery) manuly such as /vendor
Click to expand...
Click to collapse
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Download Link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
daxiaamu said:
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Click to expand...
Click to collapse
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Awesome. Thank you very much @daxiaamu!
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
Same thing here. Thanks for the heads up.
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
a63548 said:
Awesome. Thank you very much @daxiaamu!
Same thing here. Thanks for the heads up.
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
Need new link please
Aballamis said:
Need new link please
Click to expand...
Click to collapse
You can also use the one from xXx https://forum.xda-developers.com/on...1-1-speed-ram-optimized-t3627121/post72802213
Aballamis said:
Need new link please
Click to expand...
Click to collapse
Here's a mirror: http://www.mediafire.com/file/1psz6...ForceEncrypt_2.0_%28OP5-5T-Treble%29.zip/file
Recommendation
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Mohitash said:
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Click to expand...
Click to collapse
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
amitporedi007 said:
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
Click to expand...
Click to collapse
Magisk must be flashed after dm...zip. But if you have already installed magisk then no worries. Flash DM Verity n force encrypr disabler and then again flash magisk. No need to format data in this case. Format data only needed when you are doing pure clean install of stock (based) rom. Check my signature, i am on OOS 9.0.2 that is android pie 9.0 and magisk v18. Decrypted (using that dm verity and force encrypr disabler).