Develop Bugs

[EOL][ROM][7.0] RevivorOS v2.0

REVIVING THE LOVE FOR STOCK ROM. OPTIMISED STOCK ROM on the base of NPJS25.93-14-4 for MOTO G4/PLUS.
{
"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"
}
NOTE: This thread is best viewed on a desktop browser like Microsoft Edge/ Google Chrome/etc.
FEATURES:
1. FULLY DE-ODEXED by smali-2.2.0 and baksmali-2.2.0 .
2. FULLY DE-BLOATED
3. ZIP-ALIGNED ALL SYSTEM AND FRAMEWORK APPS
4. March 1 Security patch & Android Nougat 7.0
ALLEGED PERFORMANCE IMPROVEMENTS THAN STOCK NPJ25.93-14:
1. Faster in general UI performance.
2. Apps will use less storage and memory because the ROM is deodexed, debloated and zipaligned.
3. More battery efficiency as claimed by the update npjs25.93-14-4 + point 2.
4. A bit less of heating than stock owing to debloat.
DOWNLOADS:
1. TWRP 3.1 by @oadam11: Post 2 of Ground Zero ROMs thread for athene
2. ROM: Android File Host Link
3. SuperSU v2.79 SR3: [BETA]SuperSU v2.79 SR3 thread
4. Magisk v12 : Magisk Release Thread
5. Magisk Terminal Debloater v4 module/script: Download manually here from this Thread or from the Download section under Magisk Manager App.
6. ElementalX Kernel v1.04 for Stock N ROM: ElementalX Kernel thread for athene
7. Vegito Kernel v6.5 for Stock N ROM: Vegito Kernel Thread
INSTALLATION PROCEDURE:
1. Make appropriate backups in TWRP.
2. Wipe System, Data, Cache and ART Cache.
3. Install the ROM. (No need for GApps)
4. Reboot.
5. Update Google Play Store via tapping on version in Play store settings and after that update the Google Play services.
6. Update all the apps and reboot once.
NON-ROOTED. Why?
Simply because some people want MagiskSU and some want SuperSU. Moreover rooting would require changing the kernel to ElementalX or Vegito as there was no root exploit in stock N kernel.
BUGS:
1. Settings app MAY crash if you open the Apps section. If you want to configure the default apps tap the gear icon immediately.
Getting it to work is pure LUCK. Sorry I have no fix for it. Happens only to me idk why. No one else reported this.
ROOTING PROCEDURE:
WARNING: IF YOU DIRECTLY FLASH SOME SU MANAGER YOUR DEVICE WON'T BOOT.
1. Take appropriate backups in twrp (Boot partition recommended).
2. Flash ElementalX kernel v1.04 for Stock ROM or Vegito Kernel v6.5.
3. Reboot (Optional).
4. Flash your desired su manager (Magisk v12 or SuperSU v2.79 SR3).
5. Reboot (Incase of SuperSU boot process will loop once).
6. Update the Magisk Manager/ SuperSU from PlayStore(If needed).
IMPORTANT NOTES:
DON'T TRY INSTALLING ANY FUTURE OFFICIAL OTA FROM MOTOROLA ON THIS ROM. FLASH STOCK NOUGAT FROM HERE IF NEED BE. I have already removed the '3c_ota' app using the magisk terminal debloater script, although, if you get any update via the OTA app, don't try installing it.
SUBSTRATUM/OMS Support won't be possible on this ROM as it is based on prebuilt system images instead of some raw source code. Legacy mode may work with root. Do not report bugs for the same. I'm not responsible for the consequences of themeing.
This ROM will NOT upgrade your BOOTLOADER and PARTITION TABLE. They'll remain the same as NPJ25.93-14 (Dec 1 Patch) unless you had flashed the March 1 patch in stock recovery.
Hello moto sound and boot animation works fine
Credits/Thanks:
1. @kosmasgr for the TWRP backup.
2. @Swapney Raul for testing the ROM.
3. @oadam11 for TWRP 3.1.0
4. @Chainfire for SuperSU.
5. @topjohnwu for Magisk.
6. @veez21 for Magisk Terminal Debloater.
7. @flar2 for ElementalX kernel.
8. @Dreamstar for Vegito kernel
9. XDA for the amazing dev portal.
10. Motorola for the device. (Ik many of you hate Lenovo)
11. Google ofc for Android and the open source community.
12. Android File Host for hosting the downloads.
If I missed anyone..do PM for the same. :good:
Do check out the bootlogos/splash screens I have made for athene.
ADDITIONAL SUPPORT:
1. Custom ROM help thread.
2. For further assistance, you can message at Telegram: Personal or Community.
HIT THANKS IF YOU LIKED IT. :good:
XDA:DevDB Information
RevivorOS, ROM for the Moto G4 Plus
Contributors
tywinlannister7
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock N 93-14-4
Based On: Stock ROM
Version Information
Status: Stable
Created 2017-05-18
Last Updated 2019-11-22

Reserved :good:

Thanks ? and files manager works fine if u update the app.

Hi! Can I flash without wiping data if I'm already on stock NPJS25.93-14? Thanks!

A BIG NO
pblasi said:
Hi! Can I flash without wiping data if I'm already on stock NPJS25.93-14? Thanks!
Click to expand...
Click to collapse
No I would not recommend this. Since the apps are deodexed and zipaligned with many of them being removed. So this will create a problem on a dirty flash. Instead use Titanium Backup for apps and their respective data.

fr3d0x said:
Thanks and files manager works fine if u update the app.
Click to expand...
Click to collapse
Thanks for the heads-up :good:

Αwesome rom @tywinlannister7. Also i edited build prop , adding line ro.sf.lcd_density=410 before flashing and works excellent.
I have fc with file manager but there is no file manager ( strange ) and fc with appbox but also there is no this app
Wipe data and cache will solve the problem

tywinlannister7 said:
1. Moto File Manager and a few apps may give you Force Stops on first boot. If force stopping the app and then clearing its data and wiping cache (both)
FIX: Force Stop the apps>Clear Data>Update from Google Play>Wipe caches (both ) in twrp> Reboot
Click to expand...
Click to collapse
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?

kosmasgr said:
Αwesome rom @tywinlannister7. Also i edited build prop , adding line ro.sf.lcd_density=410 before flashing and works excellent.
I have fc with file manager but there is no file manager ( strange ) and fc with appbox but also there is no this app
Wipe data and cache will solve the problem
Click to expand...
Click to collapse
Deodexing and debloating might be a reason. These apps work in the background as system apps and create a bit of the force stop thing.

pblasi said:
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
Click to expand...
Click to collapse
What model do you have? I have tested this on the indian xt1643. Although the base of the ROM is from the European model (Shouldn't make any difference imo).
Can you try disabling or uninstalling it? (Proceed with backup). If no help, I'll need a logcat and try to find a fix. I'm still a beginner and this is my first ROM after Lineage. ?

pblasi said:
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
Click to expand...
Click to collapse
I got this error while setting up the device but after the setup it was gone haven't seen that error since then,do you get it often?

If i flash this from mm will my modem will change to nougat?

dedik46 said:
If i flash this from mm will my modem will change to nougat?
Click to expand...
Click to collapse
No

It would be nice if you could add substratum support

[email protected] said:
It would be nice if you could add substratum support
Click to expand...
Click to collapse
I think as this is a stock ROM we can't add Substratum commits in, though if I'm incorrect someone correct me!
Nice work by the way, tywinlannister7 good to see a TWRP flash of the latest security patch and OS!

Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???

diegomartinezlovey said:
is necessary flash official nougat before???
Click to expand...
Click to collapse
I think you should do so, ideally, so that your baseband and other firmware is at least on Nougat, before then wiping your device and then flashing this TWRP file as per the opening post.

diegomartinezlovey said:
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
Click to expand...
Click to collapse
You need to first flash the Dec 1 path update then this so that all things work.

echo92 said:
I think as this is a stock ROM we can't add Substratum commits in, though if I'm incorrect someone correct me!
Nice work by the way, tywinlannister7 good to see a TWRP flash of the latest security patch and OS!
Click to expand...
Click to collapse
As far as I know we can add using small editor but it's a hard job so no one does that.

diegomartinezlovey said:
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
Click to expand...
Click to collapse
I had used the system and boot dump from the reteu model owned by @kosmasgr . But the ROM should work fine as long as you have updated to Nougat NPJ25.93-14 or above.

[ROM][UNOFFICIAL][ResurrectionRemix-P-v7.0.2][dragon] -> 20190624 (DISCONTINUED)

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
​
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.​
​
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
XDA:DevDB Information
ResurrectionRemix, ROM for the Google Pixel C
Contributors
followmsi, apascual89, redukt
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: RR-P-v7.0.2-20190423
Stable Release Date: 2017-04-15
Created 2017-04-25
Last Updated 2019-06-24

Ok guys, this rom is ultimative for configuration nerds (like me) - tested it now since release and find no issues. Magisk root and hide is full integrated, OMS too. Did some tests with my new toy (Huawei Watch 2 4g) by playing with watchface tools on bluetooth connection - well... it´s stable!
Connected my B&W P5 wireless headphones and got no hickups!
Running this setup with an accelerator based wallpaper - the GUI is really fluid and smooth.
Some screens;

The blur & transparency options are realyl eyecatcher, check it out

New version arrived ..
RR-N-v5.8.3-20170503-dragon-Unofficial-followmsi.zip
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not needed if you upgrade from previous build)
3. Install RR-N-v5.8.3-20170503-dragon-Unofficial-followmsi.zip
4. install open_gapps-arm64-7.1-xxxx-20xxxxxx.zip (optional)
5. install SuperSU-v2.79-201612051815.zip (optional - the RR ROM installer does not include Magisk installation)
6. Reboot into system ..
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to systemless rooting - if you have installed supersu before you need to install SperSU.zip again !
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- If you have problems with SetupWizard from opengapps - pls install opengapps after first system boot.
- BeansGapps SetupWizard should have no problems at all !
The required (stock) vendor.img is part of the ROM installer now !
You may have a try and do a "dirty" flash too -> do not wipe your data partition.
If you face any problems pls fo a factory reset via TWRP first.
DOWNLOAD:
NEW: https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg
OLD: https://onedrive.live.com/redir?res...17&authkey=!ACPxBsf1QD-Fr0M&ithint=folder,zip
Enjoy

Guys, it seems that the manually Magisk root installation is recommended. SuperSu give some conflicts and settings force closes. Many thank to @followmsi for his hard work supporting our lovely device with this beast of rom
Btw - if you get in trouble with SuperSU get MagiskManager root privileges and let it download Magisk-v12.0.zip. Reboot your device in TWRP and install Rom / (Kernel) / /MagiskManager/Magisk-v12.0.zip again. Thats´s all Have Fun

redukt said:
Guys, it seems that the manually Magisk root installation is recommended. SuperSu give some conflicts and settings force closes. Many thank to @followmsi for his hard work supporting our lovely device with this beast of rom
Btw - if you get in trouble with SuperSU get MagiskManager root privileges and let it download Magisk-v12.0.zip. Reboot your device in TWRP and install Rom / (Kernel) / /MagiskManager/Magisk-v12.0.zip again. Thats´s all Have Fun
Click to expand...
Click to collapse
Did you install fresh boot.img before you installed Magisk ?
If you want to install both - magisk and supersu - you need to follow the instructions here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock (flash uninstaller if Magisk is previously installed)
Download the latest Magisk zip file
Reboot to a custom recovery
If you choose to use SuperSU (only support Android 6.0+), flash SuperSU in systemless mode now
Flash Magisk zip
Reboot. Update the stub Magisk Manager to the latest from Play Store
I don't have any problems ...
Installed Magisk only - works fine.
Installed SuperSU and Magisk - works fine. (SuperSU is the root tool then - Magisk Manger is used for modules only)
Magisk is quite nice - it does not need to double-boot after installation.
And it's open source too
If you install SuperSU and Magisk it still needs to double-boot because of SuperSu.
Maybe we should switch to Magisk in general .. for all ROMs
I did test this on LineageOS OMS CM14.1 now.
Will test again on RR version .. but it should be the same - the integrated Magisk Manager should not be related.
Cheers

Made a screen shot with LOS OMS version ..

Made same test on latest RR version now ... no problems at all.
Installed Magisk only - working fine.
Installed Magisk and SuperSU .. all is fine.
Same like in LOS OMS version .. root tool is SuperSU.
Magisk Manager has been granted access inside SuperSU tool.
Pls check your install procedure again ..
Removal of SuperSU or Magisk is done by just applying the fresh boot.img.
Magisk only install:
1. fresh boot.img (taken from zipped ROM package)
2. Install Magisk only-
3. Reboot system - no double-boot
or
Magisk and SuperSU install:
1. fresh boot.img (taken from zipped ROM package)
2. Install SuperSU first !!!
3. Install Magisk
4. Reboot system - still have the double-boot
SuperSu only installation has been already validated on last RR version.
I am really starting to like Magisk ... no double-boot anymore and full opensource

Here the same screen shot but inside RR ..
My conclusion .. no issues at all with magisk !
Seems to fully working with chromeos signed boot.img
Works with and without Supersu.
Does not need double-boot .. and is opensource.
Hmmmm .... I think I will switch
But the ROMs will be not changed !
If somebody wants to install SuperSU you don't need install a fresh boot.img before.
After ROM installation you decide what you want .. both tools or just one tool.
Topic magisk is closed now

followmsi said:
Here the same screen shot but inside RR ..
My conclusion .. no issues at all with magisk !
Seems to fully working with chromeos signed boot.img
Works with and without Supersu.
Does not need double-boot .. and is opensource.
Hmmmm .... I think I will switch
But the ROMs will be not changed !
If somebody wants to install SuperSU you don't need install a fresh boot.img before.
After ROM installation you decide what you want .. both tools or just one tool.
Topic magisk is closed now
Click to expand...
Click to collapse
Those screenshots have nicely answered a question for me if the Roms are laid out like stock nav bars or not lol

Made the same package for flo/deb and manta devices .
And now for dragon device too ..
It seems there are still issues with the opengapps SetupWizard on 7.1.2 ROMs.
The SetupWizard (only) package below seems to work fine - except for the "vision settings".
BeansGapps_SetupWizard_7.1.2_Dragon.zip
Installation:
1. As we want to see the SetupWizard we do a clean install .. wipe system, cache, dalvik, data .. everything except internal storage.
2. install the 7.1.2 ROM of your choice.
3. Install official opengapps package you like ..
4. install BeansGapps_SetupWizard_7.1.2_Manta.zip
5. Install Magisk and/or SuperSu.
6. Reboot into system and wait for the SetupWizard.
Cheers

followmsi said:
Made the same package for flo/deb and manta devices .
And now for dragon device too ..
It seems there are still issues with the opengapps SetupWizard on 7.1.2 ROMs.
The SetupWizard (only) package below seems to work fine - except for the "vision settings".
BeansGapps_SetupWizard_7.1.2_Dragon.zip
Installation:
1. As we want to see the SetupWizard we do a clean install .. wipe system, cache, dalvik, data .. everything except internal storage.
2. install the 7.1.2 ROM of your choice.
3. Install official opengapps package you like ..
4. install BeansGapps_SetupWizard_7.1.2_Manta.zip
5. Install Magisk and/or SuperSu.
6. Reboot into system and wait for the SetupWizard.
Cheers
Click to expand...
Click to collapse
Hello followmsi,
Thanks for port RR to our Pixel C I love RR and I use it on both of my OnePlus.
In my OP 3T with a 7.1.2 RR Rom I´m using BeansGAPPS Mini, so I should use the Beans package provided in your OneDrive folder?
Thanks in advance.

Istvan_86 said:
Hello followmsi,
Thanks for port RR to our Pixel C I love RR and I use it on both of my OnePlus.
In my OP 3T with a 7.1.2 RR Rom I´m using BeansGAPPS Mini, so I should use the Beans package provided in your OneDrive folder?
Thanks in advance.
Click to expand...
Click to collapse
If you read above .. it's just a replacement for the setupwizard.
If you install opengapps and the setupwizard is crashing reboot into TWRP again and install this package above - just to fix setupwizard only.
Of course you can install complete beans gapps too.
Cheers

followmsi said:
If you read above .. it's just a replacement for the setupwizard.
If you install opengapps and the setupwizard is crashing reboot into TWRP again and install this package above - just to fix setupwizard only.
Of course you can install complete beans gapps too.
Cheers
Click to expand...
Click to collapse
Ok, let´s give it a try and post results here.
Cheers!!

followmsi said:
If you read above .. it's just a replacement for the setupwizard.
If you install opengapps and the setupwizard is crashing reboot into TWRP again and install this package above - just to fix setupwizard only.
Of course you can install complete beans gapps too.
Cheers
Click to expand...
Click to collapse
Full wipe and ROM installed with latest Beans Gapps without any kind of problems. I love RR and it works like a charm for the moment. I was using the tablet for at least 4 hours I think with all my daily apps installed (arround 40 apps) Substratum and rooted with latest Magisk.
I have a question, the stock kernel can handle usb-otg? And what formats can handle, like NTFS, exFAT, etc? Sorry for dumb question but I forget all my USB at the office....
Really thanks for your work mate!!!

Istvan_86 said:
Full wipe and ROM installed with latest Beans Gapps without any kind of problems. I love RR and it works like a charm for the moment. I was using the tablet for at least 4 hours I think with all my daily apps installed (arround 40 apps) Substratum and rooted with latest Magisk.
I have a question, the stock kernel can handle usb-otg? And what formats can handle, like NTFS, exFAT, etc? Sorry for dumb question but I forget all my USB at the office....
Really thanks for your work mate!!!
Click to expand...
Click to collapse
The kernel supports NTFS and F2FS .. exFAT via fuse only.
Have a try to mount your drive via console.
Maybe tricky ..
To make it short ..
Pls use Paragon drivers or other tools for exFAT and NTFS.
Maybe use "stick mount" too.
These tools offer "real" Android integration .. that what you want !
Cheers
EDIT: Because of TWRP config, the ntfs-3g user space driver is also included in the RR ROM.
https://github.com/followmsi/androi...mmit/01918bd2e07ae491eaae9a37af4175d375c18c86
Type in terminal ..
mount.ntfs /dev/yourdevice
To mount via kernel driver you just type. ..
mount -t ntfs /dev/yourdevice
Have a try ..
But as said above .. to have it "comfortable" use proper Android tools

New version arrived ...
RR-N-v5.8.3-20170511-dragon-Unofficial-followmsi.zip
Changes:
- Latest RR changes
- Latest kernel changes
- Fix for "Wifi direct"
- Enabled Doze (Ambient light)
Enjoy ..

Due to several reasons I have removed the vendor.img from the ROM now !
I have changed the first page accordingly ...
The required (stock) vendor.img is not part of the ROM installer !
You will find a copy inside the download folder.
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install ROM ...
4. Install current stock vendor.img (flash via TWRP)
5. install opengapps or beansgapps (arm64) (optional)
6. install SuperSU.zip and/or Magisk.zip
7. Reboot into system ..
Thanks for your understanding ..

followmsi said:
Due to several reasons I have removed the vendor.img from the ROM now !
I have changed the first page accordingly ...
The required (stock) vendor.img is not part of the ROM installer !
You will find a copy inside the download folder.
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install ROM ...
4. Install current stock vendor.img (flash via TWRP)
5. install opengapps or beansgapps (arm64) (optional)
6. install SuperSU.zip and/or Magisk.zip
7. Reboot into system ..
Thanks for your understanding ..
Click to expand...
Click to collapse
Hello and thanks for updating the ROM,
So in order to flash the latest update after install the "vendor_N2G47O_2017-05.img" I must flash the "vendor_N2G47O_2017-05.img" right?
Cheers!!!

Istvan_86 said:
Hello and thanks for updating the ROM,
So in order to flash the latest update after install the "vendor_N2G47O_2017-05.img" I must flash the "vendor_N2G47O_2017-05.img" right?
Cheers!!!
Click to expand...
Click to collapse
No .. this is a copy of current stock vendor.img file.
And if you have current vendor.img now, you don't need to install again.
Sent from my AOSP on Manta using Tapatalk

[ZIP] ViPER4AndroidFX 2.5.0.5 (SafetyNet passed) [STOCK 7.0 - LOS 14.1]

After hundred of unsuccessful attempts of modify the ViPERFX installer to get it working on our stock rom (Marshmallow and Nougat), i found a way.
{
"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"
}
Available versions:
- ViPERFX 2.5.0.5 version, codename "Beautiful".
- ViPERFX 2.4.0.1 version, codename "Beautiful".
Changelog:
V4A v2.5.0.5 Update
February 12, 2017ViPER4Android (V4A)
ViPER4Android updated to v2.5.0.5
Changes:
0. Emergency fix v2504 – repair load file incompatibility issues.
1. New UI.
2.Add quad-ch convolver support (stereo convolver).
3.Add FET compressor.
4.Support change storage path.
5.Fix bugs.
------------------------------------------
V4A v2.4.0.1 Update
Changes:
1.Fix bugs.
2.New audio effect 'AnalogX'.
3.More optimization.
Pre-requisites:
1) Rooted device.
2) Your device MUST have BusyBox installed (recommended version HERE)
*Flash it from recovery, it's a minimal version.
Installation:
0) Take a backup of your complete System partition with TWRP (just in case).
1) Download and Install "The SELinux Toggler.ver.4.3.9.build.62.apk " (or the available newer at that moment), grant root permissions and disable the enforcement.
2) Download and Install your desired ViPER4Android version (see attachments) from TWRP and then boot to system.
3) Open your ViPERFX app, grant root permissions and install the driver (a dialog should ask you about it), the app may look freezed for 1 or 2 minutes (while doing it), let it work, it's normal.
4) Reboot your device.
5) Open the app and check the driver status, if it says "Normal" then you're done. Just activate V4A-FX from the app and enjoy.
Uninstall:
See post #8
Credits: The ViPER Team - http://vipersaudio.com/blog

Reserved.

Great work, I really had waiting for this a very long time. One question, if I uninstall the SELinux app it affects Viper?

champagne66601 said:
Great work, I really had waiting for this a very long time. One question, if I uninstall the SELinux app it affects Viper?
Click to expand...
Click to collapse
Thanks, yes it needs selinux enf. Deactivated in order to work. But you can also activate the developer mode in the Viper app (settings - dev mode), there is an option (that i didn't test) that change the selinux state. I think this change will persist and you will not have issues whether you delete the selinux toggler app.

Does it works with a custom ROM?

Johann0109 said:
Does it works with a custom ROM?
Click to expand...
Click to collapse
Yes, it works.

is there any way to uninstall it?

Dar Samir said:
is there any way to uninstall it?
Click to expand...
Click to collapse
Yes sure,
How to Uninstall:
- Tap the three lines button (settings) in the ViPER app.
- Select uninstall driver
- Remove the ViPER apk manually, located in "system/priv-app".
- Reboot your device, that's all.

ViPER FX (2.5.0.5) Materilized
I'm glad to share this little file that gives a fresh look to the ViPER4Android App, thanks to @pittvandewitt (the guy who makes the beutiful theme) and to @moonlightdrive (the sir who makes a port to stock 7.0).
It works on any ROM and of course, on stock.
Screenshots:
https://i.imgur.com/JVl1kiq.png
https://i.imgur.com/KQJ7ZzD.png

moonlightdrive said:
After hundred of unsuccessful attempts of modify the ViPERFX installer to get it working on our stock Nougat 7.0 rom, i found a way.
Available versions:
- ViPERFX 2.5.0.5 version, codename "Beautiful".
- ViPERFX 2.4.0.1 version, codename "Beautiful".
Changelog:
V4A v2.5.0.5 Update
February 12, 2017ViPER4Android (V4A)
ViPER4Android updated to v2.5.0.5
Changes:
0. Emergency fix v2504 – repair load file incompatibility issues.
1. New UI.
2.Add quad-ch convolver support (stereo convolver).
3.Add FET compressor.
4.Support change storage path.
5.Fix bugs.
------------------------------------------
V4A v2.4.0.1 Update
Changes:
1.Fix bugs.
2.New audio effect 'AnalogX'.
3.More optimization.
Pre-requisites:
1) Rooted device.
2) Your device MUST have BusyBox installed (recommended version HERE)
*Flash it from recovery, it's a minimal version.
Installation:
0)Take a backup of your complete System partition with TWRP (just in case).
1) Download and Install "The SELinux Toggler.ver.4.3.9.build.62.apk " (or the available newer at that moment), grant root permissions and disable the enforcement.
2) Download and Install your desired ViPER4Android version (see attachments)from TWRP and then boot to system.
3) Open your ViPERFX app, grant root permissions and install the driver (a dialog should ask you about it), the app may look freezed for 1 or 2 minutes (while doing it), let it work, it's normal.
4) Reboot your device.
5) Open the app and check the driver status, if it says "Normal" then you're done. Just activate V4A-FX from the app and enjoy.
Uninstall:
See post #8
Credits: The ViPER Team - http://vipersaudio.com/blog
Click to expand...
Click to collapse
champagne66601 said:
I'm glad to share this little file that gives a fresh look to the ViPER4Android App, thanks to @pittvandewitt (the guy who makes the beutiful theme) and to @moonlightdrive (the sir who makes a port to stock 7.0).
It works on any ROM and of course, on stock.
Screenshots:
https://i.imgur.com/JVl1kiq.png
https://i.imgur.com/KQJ7ZzD.png
Click to expand...
Click to collapse
Both of you: thanks a lot for this development. It works like a charm and installation is as smooth as butter!!
Just need one information: lockscreen visualization and pulse don't work after installing V4A (as musicFX and AudioFX are removed). Is is possible to get V4A with these two customizations or any of them? (Just asking the tweaks if available as like pulse and not intended any development enforcement.)
I'm on AEX ROM. Thanks in advance.

checksamir said:
Both of you: thanks a lot for this development. It works like a charm and installation is as smooth as butter!!
Just need one information: lockscreen visualization and pulse don't work after installing V4A (as musicFX and AudioFX are removed). Is is possible to get V4A with these two customizations or any of them? (Just asking the tweaks if available as like pulse and not intended any development enforcement.)
I'm on AEX ROM. Thanks in advance.
Click to expand...
Click to collapse
Sorry for the delay, wasn't at home.
Well in that case, if you're on AospExtended i pressume that you have Magisk Installed, and if you have it, you can install the ViPER4Android Magisk Module by ahrion.
I used to use this Module when i was using LineageOS (with pulse activated).
v4afx_v1.4.zip
Edit: i forgot to mention that you have to dirty flash your current AEX to get MusicFX/AudioFX again and to remove v4 scripts and files located into system.

moonlightdrive said:
Sorry for the delay, wasn't at home.
Well in that case, if you're on AospExtended i pressume that you have Magisk Installed, and if you have it, you can install the ViPER4Android Magisk Module by ahrion.
I used to use this Module when i was using LineageOS (with pulse activated).
v4afx_v1.4.zip
Edit: i forgot to mention that you have to dirty flash your current AEX to get MusicFX/AudioFX again and to remove v4 scripts and files located into system.
Click to expand...
Click to collapse
Hello Moonlight,
Thank you a ton for your swift response. I have dirty flashed the ROM and then flashed V4Afx module, however the issue remains the same. Probably a clean flashing of ROM would resolve. Will try it later this week and update you the status.
thanks again for the tip.
Rgds,
Samir

I'm on ViperOS LOS 7.1.2 with root and magisk.
Tried to install via Magisk module but nothing happened, phone reboot after install but the apk didn't show up.
---- UPDATE -----
I've installed the ZIP some post above and worked like a charm

thank you very much. After a lot of searching for the viper mod, the only one that worked for me was this one. Xt 1621 Nougat stock 7.0, busybox and SElinux toggler, elementary kernel 1.04. Thanks for a little I go back to M.M.

does it have Dolby >?

tnmsrkr said:
does it have Dolby >?
Click to expand...
Click to collapse
No, it's only original V4a driver.

I Tried 10 Options out on the Internet to try and install Viper on My Moto G4 running Lineage Os 14.1 with Android 7.1.2 version and still cannot install this Darn Viper. Any Help would be Greatly Appreciated....

Touchpad64gb said:
I Tried 10 Options out on the Internet to try and install Viper on My Moto G4 running Lineage Os 14.1 with Android 7.1.2 version and still cannot install this Darn Viper. Any Help would be Greatly Appreciated....
Click to expand...
Click to collapse
Did you follow all the descripted steps in this guide?
It's mandatory to install BusyBox (use the version that i uploaded in the OP) and the SElinux enforcement must be deactivated.
If you're still facing issues, read post #11.

moonlightdrive said:
Did you follow all the descripted steps in this guide?
It's mandatory to install BusyBox (use the version that i uploaded in the OP) and the SElinux enforcement must be deactivated.
If you're still facing issues, read post #11.
Click to expand...
Click to collapse
Yea, I tried all the steps in every Install Option out there. I have been Rooting and Flashing for Years but this has me stumped! I have a full version of the latest BusyBox installed, but I will try the version that OP suggest. As far as the SElinux enforcement...It won't let me deactivate it???

Touchpad64gb said:
Yea, I tried all the steps in every Install Option out there. I have been Rooting and Flashing for Years but this has me stumped! I have a full version of the latest BusyBox installed, but I will try the version that OP suggest. As far as the SElinux enforcement...It won't let me deactivate it???
Click to expand...
Click to collapse
SELinux enforcement must be turned off in order to work, otherwhise the v4a_fx driver will not be properly loaded. The app ("The SELinux toggler") keeps the enforcement disabled (and this should remain in that way, all the time).
I had issues using normal versions of BusyBox, so that's the reason why i recommend that specific flashable version posted in the op.

[TWRP]+[KERNEL]+[ROOT]-Xperia XA1 Plus with more features

I am not having XA1 Plus anymore. This kernel is development discontinued. Sorry for that.
Hello Xperia lovers , Today i am going to present you Xperia XA1 Plus Stock kernel with more usefull features . Since Xperia xa1 plus is not added into XDA yet, Project device is selected temporarily. Will move it later when form Moderators will add this device.
No need to tell about what is kernel and what it do . because almost everyone know these days about kernel and its working process.
So with this kernel you will get twrp 3.2.1 (Latest build) which i have moded to work with MTP devices.
More ever in some devices Data in encrypted automatically. Forcefully data encryption is disabled in this kernel.
{
"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"
}
Just simply turn on your device, wait for viberation and white led. then press Vol+ OR Vol- button to enter recovery mood Both will work.
This is intial release of this kernel, will update it with more features time by time.
wait for next release with more useful mods and features
To flash this kernel simply install Fastboot and ADB drivers and use flashtool in fastboot mood OR
install ADB and Fastboot drivers,
Then put boot.img in adb and fastboot home path and Or switch off your device and press Vol+ button and attach usb cable
Code:
Fastboot flash boot boot.img
Fastboot reboot
Warning :
Code:
This kernel needs unlocked bootloader
Your Warrenty is void.
i am not responsible if something goes wrong with flashing.
Attaching Stock Boot.img also in case if anyone want to move to stock kernel again.
Many Thanks to developers who inspired us and created tools to work smoothly.
XDA:DevDB Information
[TWRP]+KERNEL+ROOT-Xperia XA1 Plus with advanced features, Kernel for the Sony Xperia XA1
Contributors
Ab.Shaheen
Kernel Special Features: Added TWRP 3.2.1 (Go Through Vol+ OR Vol- on boot) , Disabled Force Encryption of data, Fully Supported Xperia XA1 Plus .117 Stock ROM. (Not Tested With Other ROMs), Disabled Force encryption of userdata,
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-01-04
Created 2018-01-04
Last Updated 2018-10-09

Reserved
version 1
~Initial Release
~Based on XA1 PLUS Nougat (.117)
~Disabled force encryption
~Added latest version of TWRP (3.1.2)
~Added SELINUX status in settings > about > SELinux Status
Version 2
~Based on XA1 PLUS Nougat (.131)
~Initrd support added
~Disabled DM Verity.
~Set selinux to permissive
Version 3
~Based on latest Oreo update (.116 & .129)
~Disabled Force encryption (New method)
~Disabled DM-Verity (New Method)
~Updates twrp recovery to new and stable version.
~Battery life is extremely good. using since last week.
~Added some other tweeks.
~init.d still under process. (But you can use magisk module for init.d)
Version 4
~All Points from Version 3
~And new added features.
~If your data is already encrypted, you can decrypt your data from settings,
~Reworked magisk installer. ( Patch boot.img from magisk App by keep selecting preserve "force encryption" and "DM Verity options" Otherwise it may stuck at boot animation. )
Version 5
~Based on Oxa1 plus OREO (.138)
~reworked selinux to permissive
~reworked init.d support
~more stable and working "adb authorization prompt" and "developer options"
just install latest magisk zip to get root access.
Version 6
Updated kernel for 101 firmware.

Download Links
To Download For Nougat and Oreo : Click Here To Download.

root
good joob!! i have xa1 plus. Can modify the CPU gobernor with this kernel?

It's for latest firmware only? .117 one?
Does it support MAGISK or only SuperSU?
What about DRM fix/patch?
Sorry for so many questions, but probably some other user would ask them anyway

ch3mn3y said:
It's for latest firmware only? .117 one?
Does it support MAGISK or only SuperSU?
What about DRM fix/patch?
Sorry for so many questions, but probably some other user would ask them anyway
Click to expand...
Click to collapse
Yes , it support systemless magisk and supersu. I did'not checked with the other versions, may be supporting them or may be not.
DRM patch will be also in next releases of this kernel..

Can anybody provide TA partition backup to look into DRM patch?

Can someone help me? Root XA1 + G3416, Android 7.0 .117

root for 3426 dual is possible? thanks everyone
i had unlocked bootloder successiful, after i had installed this
https://forum.xda-developers.com/devdb/project/dl/?id=27994
phone restart normal.... not in twrp...
how can i install twrp and then install superuser for root....
thanks you...

Alekim91 said:
root for 3426 dual is possible? thanks everyone
i had unlocked bootloder successiful, after i had installed this
https://forum.xda-developers.com/devdb/project/dl/?id=27994
phone restart normal.... not in twrp...
how can i install twrp and then install superuser for root....
thanks you...
Click to expand...
Click to collapse
I have not tested it on 3426. but it should work on that, just download Here It should work, but if not working then please provide kelnel.elf from stock ftf, i can compile it with twrp for you.

enrik98 said:
good joob!! i have xa1 plus. Can modify the CPU gobernor with this kernel?
Click to expand...
Click to collapse
thats not a big deal bro, now working on DRM patch, will update it later..

Ab.Shaheen said:
thats not a big deal bro, now working on DRM patch, will update it later..
Click to expand...
Click to collapse
Hi!
I tried to change the frequency of the cpu with the app "kernel audiutor" and many other apps, but none of them managed to change the frequency of the cpu. I think the problem may be SONY ric

Ab.Shaheen said:
I have not tested it on 3426. but it should work on that, just download Here It should work, but if not working then please provide kelnel.elf from stock ftf, i can compile it with twrp for you.
Click to expand...
Click to collapse
ok thanks you.... this twrp on my G3426 work very well, but i have try to instal superuser.zip.... just say fail....
how can i root my sony now? thanks you...

Alekim91 said:
ok thanks you.... this twrp on my G3426 work very well, but i have try to instal superuser.zip.... just say fail....
how can i root my sony now? thanks you...
Click to expand...
Click to collapse
Try to Flash magisk

TheOldMan said:
Try to Flash magisk
Click to expand...
Click to collapse
i ve installed magisk 15.1 and when i open supersu it say Su binary occupied
solved with flash of Magisk-v15.2(1520) and super user 2.79....
now we hope for a ROM Lineage OS.... any hope?

Alekim91 said:
ok thanks you.... this twrp on my G3426 work very well, but i have try to instal superuser.zip.... just say fail....
how can i root my sony now? thanks you...
Click to expand...
Click to collapse
SuperSu is also working very well on it, but if you will flash systemless zip from Here . System mode Supersu will cause bootloops or stuck at boot animation. And magisk works without any error, tested by me.

enrik98 said:
Hi!
I tried to change the frequency of the cpu with the app "kernel audiutor" and many other apps, but none of them managed to change the frequency of the cpu. I think the problem may be SONY ric
Click to expand...
Click to collapse
Still busy with DRM patch, ric is enabled therefore you are facing this problem, will update it now.

Ab.Shaheen said:
Still busy with DRM patch, ric is enabled therefore you are facing this problem, will update it now.
Click to expand...
Click to collapse
Thanks Bro!!

for xa1 plus there is android oreo? nothing of news? thanks you
is possible to activate double tap to wake? i miss this feature from my z4+...... help me pls

@Alekim91
X and X Compact should get Oreo before XA1 series. And they still didn't. Somewhere (don't remember site) I read that Xes will get it this month and XA1 series around MWC (february/march).

[MOD] FCS Xperia X OREO

{
"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"
}
Main advantages
- Best performance at all temperatures (50 ~ 70% faster than stock)
- Less heat (especially during moderate / intense use -5 ~ 10 ° C)
- Maintains very good performance for long periods of time
- Faster cooling
- Overheating has been deactivated
- Do not heat device while in sleep mode
- System improvements and Soc qualcomm
- Optimized CPU and gpu for Soc qualcomm control
- No overheating when used and device charged
- System and kernel functions were fixed
- Add support init.d stock
Requirements
- Xperia X F5121 & F5122
- Compilation 34.4.A.2.70
- Firmware 8.0
- Install busybox
- Twrp
- Magisk 16
- it is unknown if it works for SuperSU
Installation
Attention: it is not authorized under any circumstance to lodge the files of this mod in another cloud of storage, you can add this thread to your post
- Turn off your device
- Enter twrp
- Install - Xperia_X_Thermal_Oreo_Compilation_70.zip
- Before restarting, perform the following steps
- Twrp
- Wipe
- Slide to factory reset
- Advanced cleaning
- Option:
- Dalvik / ART Cache
- Cahe
- Data
- Slide to clean
- Reailize the installation of - initd_magisk.zip
- ready restart and configure your device
- Once the configuration is finished, turn off your device
- and restart the first few times when your device starts, leave it for 2 to 3 minutes and unlock it and go
Now to enjoy your device without worrying that hot :laugh:
credits: @korom42 or its magisk module although it is adapted for the Xperia X

Faq
- will work in another compilation
you can try but it is based on the compilation 34.4.A.2.70 that you probably bootloop
- It is necessary to perform the cleanup with twrp and reestablish my device
if it is necessary for the changes to be applied correctly
- I can upload it to my personal storage cloud
no, but you can place the thread on this topic without any problems
- Works for Android Nougat
Do not

Reserved

It doesn't need Magisk and some suspicious module, I think. Any app which can emulate init.d (like Kernel Adiutor) will work just fine.

How do I know it works?
I installed it in a clean rom, but the phone heats up normally as expected, as data: install the magisk file and I throw error, followed the steps to the letter

winsters said:
I installed it in a clean rom, but the phone heats up normally as expected, as data: install the magisk file and I throw error, followed the steps to the letter
Click to expand...
Click to collapse
the device does not heat up if you follow the steps as you re-check the installation and it will last for 2 weeks

Bootloop wheb used on xgen rom 1.07. . Did I do something wrong

Does this mod also work with Omni Rom Oreo?

Hmm, I found only the 1st thing I'm unable to install, I can install the main FCS thing but it's a no go on the initd magisk thing.. it doesn't install....

lilbrat said:
Hmm, I found only the 1st thing I'm unable to install, I can install the main FCS thing but it's a no go on the initd magisk thing.. it doesn't install....
Click to expand...
Click to collapse
The same here

PNIGGE said:
The same here
Click to expand...
Click to collapse
Copy to internal sd (crucial). Install the zip. Enable init.d using kernel adiutor. Restart phone. Profit.

I was having some weird issues with the mod where the init.d scripts wouldn't run neither with the module suggested in OP nor through Kernel Adiutor and was also tired of having to reflash the mod every time a new security update was released, so I went in and made a pure Magisk version of the mod (attached on this post).
This Magisk version is exactly the same as the OP, the only difference is that it's now a Magisk Module (so it applies systemlessly) and that you don't need busybox nor any kind of init.d support for it to work (the init.d scripts from the mod are executed directly through Magisk late_start hook instead). Download the ZIP, install through Magisk Manager, reboot and done.

mbc07 said:
I was having some weird issues with the mod where the init.d scripts wouldn't run neither with the module suggested in OP nor through Kernel Adiutor and was also tired of having to reflash the mod every time a new security update was released, so I went in and made a pure Magisk version of the mod (attached on this post).
This Magisk version is exactly the same as the OP, the only difference is that it's now a Magisk Module (so it applies systemlessly) and that you don't need busybox nor any kind of init.d support for it to work (the init.d scripts from the mod are executed directly through Magisk late_start hook instead). Download the ZIP, install through Magisk Manager, reboot and done.
Click to expand...
Click to collapse
How would the installation process differ from OPs instructions with this Magisk module?

CntrlAltDel45 said:
How would the installation process differ from OPs instructions with this Magisk module?
Click to expand...
Click to collapse
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.

mbc07 said:
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.
Click to expand...
Click to collapse
Thank you. I used the second method you mentioned. Everything went by seamlessly.

mbc07 said:
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.
Click to expand...
Click to collapse
Used the 2nd method, but there's a problem: after 2 minutes in stand by from the restart of the phone, it restarted by itself...
What's the problem? Need a dalvik/cache wipe after the installation with Magisk? Is it incompatible with Xposed framework (installed on my phone)? Or maybe the compilation base (I'm on fw .118) is different and cause bootloop...
Thanks in advance.
Edit: I used the first method, I had an installation without restart, but it doesn't work!

will it work with .118 rom?

AlexUnder2010 said:
will it work with .118 rom?
Click to expand...
Click to collapse
No! But you can get the right file at this link: https://mega.nz/#F!DZAGDY6B!d6CeWtv-tqD0RHtsOHS02w
When you open the folder, find and download fcs thermal v. 1.3. Then install through twrp.
I've installed on stock rom .118 and works great

Niquillo said:
No! But you can get the right file at this link: https://mega.nz/#F!DZAGDY6B!d6CeWtv-tqD0RHtsOHS02w
When you open the folder, find and download fcs thermal v. 1.3. Then install through twrp.
I've installed on stock rom .118 and works great
Click to expand...
Click to collapse
It's for Nougat only ??*