Database Info

[Q] Can't uninstall system apps with Titanium Backup in CM11

Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.

Cloonix said:
Hello,
i finally got my Nexus 5 today and first thing I did was unlocking the bootloader, installed TWRP custom recovery, flashed CM11-nightly and Franco Kernel (r31).
Next thing I usually do is to uninstall some apps with Titanium Backup (Pro). But I can't uninstall any system apps (e. g. Browser.apk). Titanium says "successful" but after refreshing the application list, the app is still there.
Does anyone have an idea what is going wrong here? Is it a problem with CM11's superuser or with Titanium Backup?
Thanks.
Click to expand...
Click to collapse
What happens if you delete the file with a file manager and reboot?

Aerowinder said:
What happens if you delete the file with a file manager and reboot?
Click to expand...
Click to collapse
I used Solid Explorer as a file manager and tried to delete /system/app/Browser.apk. The root-confirmation (CM11 superuser) pops up, asks for superuser (i grant) and Solid Explorer deletes the file without error. But the file is still there (without reboot).
Issue with superuser?
Edit: Stop... I noticed /system is mounted as read-only.

I tried to analyze the problem... and the only conclusion is, that my superuser is not working. Also Super SU ist not working. I also flashed Omni ROM instead of CM11 with no success. I used an older version of TWRP without success. Does anybody has an idea?
Edit: Before with Stock ROM and Super SU it was working.

I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?

Me to, cm11 for a850L build on crdroid nexus4

Cloonix said:
I don't know why I'm the only person with this issue... But I solved it with the following steps:
1. Flash CM11 (nightly)
2. Start the OS
3. Reboot to recovery and wipe cache/dalvik
4. Install "Super SU"
5. Start the OS
Titanium Backup is asking for root rights. Other apps also didn't get root in CM11. Whenever I install a new CM11 nightly root rights for TB are gone and I have to do the same steps again.
But why no one else has this problem? I googled like crazy. Is it CM11 or me?
Click to expand...
Click to collapse
Did you leave out Franco kernel this time?

This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456

es0tericcha0s said:
This is the fix for your issue:
http://forum.xda-developers.com/showthread.php?t=2592456
Click to expand...
Click to collapse
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
Aerowinder said:
Did you leave out Franco kernel this time?
Click to expand...
Click to collapse
No I flashed Franco after CM.

Cloonix said:
Thanks a lot!
Changing selinux to "permissive" did solve all my problems. I also had issues with other applications.
How can I change the selinux mode directly in the CM11-Zip? Under Redhat/CentOS is a configuration file unter /etc/selinux. In CM11 I can't find something similar.
And how it comes that this issue is not well-known? I think there are more 4.4 KK / CM11 users with problems.
No I flashed Franco after CM.
Click to expand...
Click to collapse
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?

es0tericcha0s said:
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.

Cloonix said:
Even without Franco (which was my first guess) CM11 (my root) behaves that way.
I will look for a method to set selinux to permissive directly in the ZIP of CM11 and will update this post.
Click to expand...
Click to collapse
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.

es0tericcha0s said:
I'd imagine adding something like this in: http://forum.xda-developers.com/showpost.php?p=48006307&postcount=65 would do the trick, though I have not had that issue in awhile. I switch roms often.
Click to expand...
Click to collapse
I tried this. And it was successfully changing selinux to permissive with every reboot. But doing this I noticed that even permissive doesn't solve the problem. CM11 built-in superuser just don't work for me. Only "Super SU" by Chainfire works well. And permissive solves a few other problems besides TiBa.

Personally I've always eventually had issues with Superuser unmounting the system as rw causing issues with apps like Titanium. Had it happen many many times on my old phone as well as the Nexus 5 across multiple ROMs. I just stick with SuperSU now.

Haven't had too many issues with that part it seems, but glad you narrowed down the problems.

I find this issue sometimes on varous flashes of CM 11 on different devices.
I use ROM toolbox fo manage apps, and sometimes it just wont delete. The solution is strange: I install adaway - somehow, that "unlocks" something that lets you delete apps. You can uninstall adaway once you have run it!

Galaxy Nexus
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!

es0tericcha0s said:
No problem. I know that problem was starting to annoy me. Got the idea from playing with a new Note 3. The newer Samsung 4.3 roms are like that too. If you don't change to Permissive then Xposed and other mods won't work either.
I guess it's possible that it's just something strange with certain CM11 and Franco kernel combos?
Click to expand...
Click to collapse
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel

daniu said:
Hi,
unfortunately the SElinuxModeChanger seems not to work for me (Samsung Galaxy S2, CM 11 m6) and I do not really get how I should install Supersu (the first described solution). I guess I should not just install it from the play store - right? But were do I get an installable zip-file to install it from the CWM?
Or is there anything else that might be wrong in my system - so that I do not need to install supersu at all?
regards
Daniel
Click to expand...
Click to collapse
If you are already using CM11, then yes, you can install SuperSu from the Play Store. Once you do and open the app, it will prompt you to update the SuperUser binary. You should be able to do the "normal" method, and then once that updates, reboot, then try the SELinux app again and then everything should start to work like you would expect. If the normal method doesn't work, then you can let it download the newest zip for you if you choose the CWM/TWRP method, and then boot to recovery and install the zip it downloads for you.

SeEsAw12 said:
I'm replying just to help out anyone who has this issue, but doesn't have a Nexus 5. I was trying to find a fix for me and my Galaxy Nexus running the latest Paranoid Android beta 4.4.2 because I kept having this same problem.. It wouldn't uninstall... and I would only keep getting directed to this specific post. So....
I tried the 'selinux' fix first, and that alone would not do a thing...
I then tried installing the 'Wanam Xposed' app and it worked perfectly.
Just change selinux to permissive and make sure both selinux and Wanam have SU access and then try to uninstall via Titanium... or whatever method you usually use.
Hope it's okay for me to post here. Thanks for the help, everyone!
Click to expand...
Click to collapse
No clue why, but this worked for me. Permissive didn't do it (was already permissive using CM 11 for tf201) and AdAway didn't do it. Didn't matter that Wanam Xposed is for Samsung devices, once given root to this app, Titanium got its head out of its rump.
UPD: So, if i uninstall Wanam Xposed then TB sticks its head back up its rump. Whatever giving root to that app does, its fixing usage issues with TB.

Xposed on 5.0.1

Has anyone had success installing xposed framework on the m8 running a stock rooted lollipop rom? I have tried multiple times following the guide in the xposed thread here http://forum.xda-developers.com/showthread.php?t=3034811 with no success.

It worked for me on adrenaline 2.1 but not on a couple of other roms I tried.

jas88 said:
It worked for me on adrenaline 2.1 but not on a couple of other roms I tried.
Click to expand...
Click to collapse
What were the steps you took to install it?

I opened xsposed installer >framework > reboot. I only downloaded a couple of modules but they work.

nmarietta said:
What were the steps you took to install it?
Click to expand...
Click to collapse
what steps are you using to install xposed? I have it working on Fluent 7.1 just fine.

BladeRunner said:
what steps are you using to install xposed? I have it working on Fluent 7.1 just fine.
Click to expand...
Click to collapse
I downloaded the files from the link I posted above..
Install the xposed installer .apk
Reboot from within the installer and grant root privileges.
Flash the framework via TWRP
I have also tried to flash the framework first, install the .apk, and reboot from within the installer to grant root.
Neither way has worked for me.

nmarietta said:
I downloaded the files from the link I posted above..
Install the xposed installer .apk
Reboot from within the installer and grant root privileges.
Flash the framework via TWRP
I have also tried to flash the framework first, install the .apk, and reboot from within the installer to grant root.
Neither way has worked for me.
Click to expand...
Click to collapse
I have it running on stock rooted, here are the steps I took.
Flashed the xposed arm zip file in TWRP
Installed the 3.0 alpha2 apk
Once installed I went into "framework" and hit soft reboot.
Once the phone was done I installed a module/made it active and soft reboot again.
I don't think you have to take these exact same steps but this is just what I did following a YT video. In "framework" it always says "Installation is only possible maunally via recovery for now." in red letters. That confused me into thinking it was not installed properly but all the modules I'm using are working fine.

The Stig 04 said:
I have it running on stock rooted, here are the steps I took.
Flashed the xposed arm zip file in TWRP
Installed the 3.0 alpha2 apk
Once installed I went into "framework" and hit soft reboot.
Once the phone was done I installed a module/made it active and soft reboot again.
I don't think you have to take these exact same steps but this is just what I did following a YT video. In "framework" it always says "Installation is only possible maunally via recovery for now." in red letters. That confused me into thinking it was not installed properly but all the modules I'm using are working fine.
Click to expand...
Click to collapse
I have tried to install this exact same way. After flashing the framework and installing the alpha .apk, I activated greenify and rebooted.
Upon launching greenify, I saw a yellow dialogue box that said auto hibernation service has stopped (auto hibernation worked fine before trying to use xposed) I attempted to enable the xposed features and a screen popped up telling me to install the xposed framework.
I have since restored my nand backup I made before flashing xposed, and greenify is back to auto hibernating, just cant use the xposed features.

nmarietta said:
I have tried to install this exact same way. After flashing the framework and installing the alpha .apk, I activated greenify and rebooted.
Upon launching greenify, I saw a yellow dialogue box that said auto hibernation service has stopped (auto hibernation worked fine before trying to use xposed) I attempted to enable the xposed features and a screen popped up telling me to install the xposed framework.
I have since restored my nand backup I made before flashing xposed, and greenify is back to auto hibernating, just cant use the xposed features.
Click to expand...
Click to collapse
Have you tried installing other modules? Looking around the greenify sections here on XDA seems it wasn't ready for 5.0, but there is a beta thread that you may want to take a look at.
http://forum.xda-developers.com/apps/greenify

The Stig 04 said:
Have you tried installing other modules? Looking around the greenify sections here on XDA seems it wasn't ready for 5.0, but there is a beta thread that you may want to take a look at.
http://forum.xda-developers.com/apps/greenify
Click to expand...
Click to collapse
I just found that beta thread, and I am now trying to install xposed again.
I also tried Xsense, and did not have any luck.
What modules are you using? I will activate them and test.

nmarietta said:
I just found that beta thread, and I am now trying to install xposed again.
I also tried Xsense, and did not have any luck.
What modules are you using? I will activate them and test.
Click to expand...
Click to collapse
Currently I'm using
Sense 6 lockscreen mods (LP)
Sense 6 Toolbox beta (to find the beta you have to change your settings, open the module in xposed/scroll all the way right to settings/change to "beta")
YouTube AdAway
YouTube Background Playback

The Stig 04 said:
Currently I'm using
Sense 6 lockscreen mods (LP)
Sense 6 Toolbox beta (to find the beta you have to change your settings, open the module in xposed/scroll all the way right to settings/change to "beta")
YouTube AdAway
YouTube Background Playback
Click to expand...
Click to collapse
I reinstalled xposed, and updated greenify to beta 11. I also installed Sense 6 Toolbox beta. Everything seems to be working just fine.
My problem was using modules that were not updated to work with lollipop. Thanks for all your help!

Android Pay Working (Tested on TruPure 2.6)

Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:

Just so you're aware the link you included is broken and depending on which version of SU is installed Step 2 might not be necessary as version 2.62-3 automatically installs systemless.

Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.

Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk

Fixed the broken link, and clarified that this is only tested on the latest supersu.

SR3TLAW said:
Well this is big news.. The newest SuperSU is systemless by default? If im reading this correctly, the Google Play update will make this option usable/.
Click to expand...
Click to collapse
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.

drewksparks said:
The newest SuperSU isn't systemless by default, step 2 is where we change the string to request the systemless. No need to download a special SuperSU package.
Click to expand...
Click to collapse
Spasticdroid said:
Xposed will definitely break Pay for obvious reasons.
Installing Google Dialer will break Pay too if the required framework JAR and permissions XML are also installed. You can install the dialer without those files, but I doubt CID and lookup will function as it should.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Sounds like regardless there is no still no way with Exposed or Google Dialer

SR3TLAW said:
Sounds like regardless there is no still no way with Exposed or Google Dialer
Click to expand...
Click to collapse
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.

drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
Whats all the fuss about Google Dialer, does it make dreams come true?

drewksparks said:
There definitely isn't a way with google dialer, but Xposed may work if you use the RootCloak module. I personally havn't tested it.
Click to expand...
Click to collapse
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk

Spasticdroid said:
RootCloak has never worked with Android Pay.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
My mistake. I thought I remembered something about it working. So, at the moment, there seems to be no way to make Android Pay work with Xposed or Google Dialer. I personally get by very well without both.

Has anyone tried it with multirom and have the second rom without any root or xposed? I'm gonna give it a go and see how it pans out.
Sent from my XT1575 using Tapatalk

Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...

bsilver2988 said:
Hi All. Can't seem to get this working. I'm on my 5th attempt at installing. I entered the install commands in TWRP 3.0 exactly as described using TruPure 2.6. Installed OpenGApps Stock. Confirmed I achieved systemless root and changed the permission in the su/bin folder using Root Explorer. I don't have ad-away or any other modification and I installed TruPure as this thread suggests. Each time, SafetyNet check fails. Any other thoughts on what might be causing this?
On a possibly related note, root doesn't seem to survive a reboot after changing the folder permissions...
Click to expand...
Click to collapse
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
/system/app
Android System WebView (WebViewGoogle)
Chrome Browser - Google (Chrome)
Clock (DeskClockGoogle)
Cloud Print (CloudPrint2)
Exchange Services (Exchange3Google)
Gmail (Gmail2)
Google Calendar (CalendarGoogle)
Google Docs (EditorsDocs)
Google Drive (Drive)
Google Keyboard (LatinImeGoogle)
Google Now Launcher (GoogleHome)
Google Photos (Photos)
Google Play Movies & TV (Videos)
Google Play Music (Music2)
Google Sheets (EditorsSheets)
Google Slides (EditorsSlides)
Google Talkback (talkback)
Google Text-to-Speech (GoogleTTS)
Google Translate (Translate)
Hangouts (Hangouts)
Maps (Maps)
YouTube (YouTube)
/system/priv-app
Google Play Services (GmsCore)
Google Play Store (Phonesky)
Google App (Velvet)
Click to expand...
Click to collapse

Spasticdroid said:
Android Pay is going to fail if there's more GApps installed to system other than what was shipped by default on the Pure. You can however, install updated versions of the default shipped apps, or even debloat the ROM of the default shipped apps (which TPMM does), and still have Android Pay working.
Looking at the list of stock Open GApps, Google+, Google Calculator, Google Camera, Google Contacts, Google Fit are a few that never was installed as system apps on stock ROM.
EDIT: Stock apps on the Moto X Pure Edition
Click to expand...
Click to collapse
Thanks for this! It makes perfect sense. Unfortunately I'm still getting a Fail when I run the test. Any other thoughts?
EDIT: Figured it out! I guess OpenGapps itself was incompatible with this setup. Installing TruPure without it solved the problem. Thanks for the help!

Thanks @drewksparks, followed your detailed instructions and confirmed by buying me a beer with my phone running True Pure 2.6.2. Now to decide if it's worth giving up Xposed, Gravity Box, Amplify, etc. Hmmm I want it all.

drewksparks said:
Hey everyone, I got Android Pay working with the latest version of TruPure (2.6)
This should also work on other stock moto ROM's, as it isn't much different.
I saw this thread (http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659) and made a few changes.
Step 0:
I do not think that this will work with Xposed or Google Dialer/Contacts installed, but I have not tested to confirm. I also uninstalled and reinstalled Android Pay before starting the process, and did not set it up. No need to wipe google play services data as other ways of implementing Pay have done (this causes problems with Android Wear, which I have) This works with the latest version of supersu, 2.67.
Step 1:
Reboot into TWRP recovery, wipe system, cache, and dalvik (art). Data wipe is not needed, at least on my phone.
Step 2:
go to the terminal (in twrp, under the advanced tab) and enter the following two commands.
Code:
echo SYSTEMLESS=true>>/data/.supersu
Code:
echo BINDSYSTEMXBIN=false>>/data/.supersu
this will make TruPure use systemless root on the next install.
Step 3:
Flash TruPure 2.6, and do not select Google Dialer in the installer. Make sure in the log that SuperSu is installed systemless, if not, you did step 2 wrong.
Step 3v2: if you don't want to install TruPure (honestly why not it's great) flash your room of choice in this step. If the ROM comes with xposed or other tweaks, this will not work.
For a stock ROM, flash here, then flash SuperSU 2.67, then continue.
Step 4: Reboot system, wait for apps to optimize.
Step 5: start up your favorite terminal app, run
Code:
su
accept the prompt
Code:
chmod 751 /su/bin
Step 6: Launch and set up Android Pay, no reboot required
Hope this helps! Your milage may vary!
:good: say thanks if I helped! :good:
Click to expand...
Click to collapse
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.

cerobles1 said:
To all the smart puppies outthere, would like to know is it is possible to get this to work on CM13 or AOSP based Custom ROMs. Android Pay is the only thing keeping me runnign TruePureMM. Not that it's a bad ROM but the customization you get from the CM13 ROMs like Bliss is crazy awesome. I'd be a ginnie pig and try it out if someone comes up with something like this for CM13 or AOSP ROMs. Thanks guys.
Click to expand...
Click to collapse
Won't work unfortunately. Too many files and apps and such are needed in CM and CM-based ROMs (example: Bliss) for them to work properly, and in turn breaks Android Pay.
If we can ever get an AOSP-based ROM, which is bare (meaning not built with AOSP apps included) working on this device, we may have a chance, just like how some ROMs on Nexus devices, such as Chroma and PureNexus, works with Android Pay.
The last thing needed would be a proper GApps package containing only the default GApps found in a stock Pure/Style ROM to install (can be updated versions of those apps too.)
Sent from my XT1575 using Tapatalk

[Q&A][FAQ][TW][N][7.0][SM-G930F/FD/K/L/S/W8] SuperMan/SuperStock-Rom

Hello guys, I open a Question and Answer Thread for all SuperMan Rom users, so even users under 10 posts can ask their questions here.
Below I added some basic Q&A stuff which can also be found at the main thread, if you have any question, read through them before posting, thanks!
In case you search for the changelog have a look: Changelog post
If you want to see my post with all useful links such as TWRP, magisk, xposed and more visit: useful post​
Basic Questions:
Q: How to get into Download Mode?
A: Power off your phone, than hold: home + volume down + power on button until you see the download mode.
Q: How to get into Recovery Mode?
A: Power off your phone, than hold: home + volume up + power on button until you see the recovery mode.
Q: My Phone is stuck at boot and doesn't start, what to do??
A: Update your bootloader and modem. Also make sure you have made a fresh install of the rom. Bootloader and Modem can be found in the OP. Another problem can be that you are didn't decrypt your phone. To fix this read below how to disable encryption.
Q: Do I need to update bootloader and modem after every update?
A: It's recommend to update your bootloader and modem everytime there is a new base yes. The developer will tell you if necessary on every rom changelog.
Q: I get verification failed at start up!?!? My phone is broken now?
A: Yes, you have to buy a new phone now. Just kidding You did not disable force encryption in TWRP (how to do so you will find below in how to decrypt your phone).
Q: I get verification FRP LOCK? WHYYYYYY???
A: Very simple answer, you did not enable OEM Unlock in developer options. Now you need to flash full rom with odin again and start from scratch. But don't forget to enable OEM Unlock this time!
Q: Which devices are supported at the moment?
A: Current supported devices are: SM-G930F/FD/K/L/S/W8. Snapdragons are NOT supported
Q: Is this rom working on Snapdragon 820 variants?
A: No, sadly not.
Q: I want to change something in my rom setup, how can I do that?
A: Simply reflash the same rom version without any wipe and than choose the correct things you want.
Q: Some features are not present in this rom, but they are on stock rom, so where are they?
A: In aroma installer you have the option to select bloat you want to install or not, you probably didn't select all package, this is why it's missing now.
Q: After a clean install my phone is overblated with many custom settings. What to do?
A: Open my romcontrol, grant it root permissions and then my default settings will be applied.
Q: Will you add X or Y feature?
A: You can kindly ask in the thread for that, if I like your suggestion I will think about adding it to the rom.
Q: You said you fixed SD card RW but Titanium Backup can't write to external SD card, why???
A: This is because of googles changes concerning SD card, to fix this open Titanium Backup, Menu, Preferences, Backup Folder Location, Storage provider and than hit DocumentProvider Storage and select your SD card. Problem solved
Q: I can't find X and Y mod. Please help
A: I've added many links and useful stuff to this post here. Hope that's what you have been looking for!
Q: I want to have my external storage like an internal as well. Google introduced it with android Marshmallow, but I can't see this option?
A: Just follow this Guide here and you can setup your SD card as normal storage
Q: I got a new strange icon appearing after nougat update. What's that?
A: This is a new advanced calling feature introduced in android nougat. Should make your call quality better or something like this. To hide it please visit following forum: Get rid of RCS icon
Questions concerning rom updates:
Q: Do I have to do a full wipe for the new version?
A: It is always the best option to make a clean install, otherwise please don't come and report bugs!
Q: But I don't want to make a full wipe when only small stuff changed!
A: For updates using the same bases you can install the rom with a dirty flash. BUT with a new base a clean install is highly recommend!
Q: What steps should I do to update to a new version with a full wipe but keep all data?
A: There are some different ways. One way is to make a backup with Titanium Backup, you can backup all Apps and Preferences there. Make sure to store this backup on external SD card (if you have one). Second way would be to save your data onto a google account or samsung cloud and restore it after a clean install.
Q: I miss an apk after rom update, how can I get it back?
A: Simply reflash rom and select "dirty flash" in aroma + select the app this time in aroma.
Q: My battery life is so bad and performance is very poor after an update!?!?
A: This comes actually not form the rom itself, dirty flash can cause problems even if only some small things have been changed. So simply install it clean again and it will solve your problem.
Q: Performance and battery is very poor even after clean install. What should I do now?
A: I assume you installed Xposed than, some modules can cause batterydrain and performance problems. So try to make a clean install of the rom WITHOUT xposed installed.
Questions about log and logcats:
Q: I got FC's and other Problems with the rom, what to do?
A: Take a logcat for me, developers use to say: without a log, it never happened . A logcat can be grabed with a PC and ADB installed, simply type: adb logcat > log.txt while your phone is connected and the error is happening. Same can be done if you have a terminal installed on your phone. Simply type adb logcat > log.txt and you will have the same output as on the PC.
Q: What kind of logs can I provide to help you?
A: Logcat: This one is for general infos about FC's
DMESG: this is for kernel related things
Last_Kmsg: this can be used after a random reboot
Q: How to get logs?
A: 1. Connect your phone to your pc
2. Make sure you got usb debugging enabled
3. Install Minimal ADB tool
4. After install open it and type: adb logcat > logcat.txt, adb shell dmesg > dmesg.log, adb shell cat proc/last_kmsg kmsg.log
5. Send me the file you got
You can also send me a log created by your phones terminal with the exact same commands!
Questions about RomControl:
Q: None of my romcontrol changes do anything, why are you such a bad dev!?!?
A: The problem is not on my end, you installed stock systemUI (which is STOCK and does not support one single mod). Use another one in aroma instead. The same thing can happen with good lock!
Q: Romcontrol gives FC's to me. HELP!
A: Very simple answer here: wipe data and cache from superman control application. Also make sure storage permissions are given to the romcontrol.
Q: Romcontrol still FC after cleaning data and cache!
A: Make sure you allow storage permission in main settings.
Q: I try to backup my current RomControl setup, but it won't work?
A: It works. Just make sure to enable storage permission in main samsung applicatoin settings. You will find it in internal sdcard under RomControl folder.
Q: I can't restore SuperMan control settings after a clean base update, why?
A: Backup for SuperMan control only works as long as you use the same version of the app, I mostly change very much things in new releases that's why it won't work there.
Q: SystemUI reboot doesn't work in SuperMan settings app, why?
A: Since Nougat update, you need to install busybox in order to get this button working. Without busybox the button will just do nothing.
Q: I enabled weather on lockscreen but I can't see anything...
A: You probably didn't setup or even installed samsungs weather widget. Without it weather on lockscreen won't work too. So reflash the rom with the widget installed this time and set it up.
How to go back to stock:
Q: I like to go back to stock rom, how is this possible?
A: I can provide you here all steps which are needed to go back to a full stock rom.
0. Make a backup and than wipe all partitions in TWRP
1. Go to Sammobile and choose your country
2. Download the file and the attached Odin on sammobile
3. After downloading, put your phone into download mode
4. Make sure drivers are installed and your pc can detect your phone in odin
5. If the box in odin turns blue, add the AP file to AP tab, BL file to BL tab, CP file to CP tab and CSC_HOME to CSC tab
6. Hit start and wait until it is finished.
7. Reboot and you have a stock rom again
Questions about Encryption:
Q: On TWRP there is an error about /data mount, what to do?
A: Your device is encrypted, follow the steps below to get rid of your encryption.
Q: Help, I never had a code and now after installing the rom my phone asks for a password??
A: Your device is still encrypted, on step 0 of my rom instructions it tells you to be sure you're not. So, what do you need to to in case you are still encrypted.
A: HOW TO DISABLE ENCRYPTION:
1. Boot into TWRP
2. Select Wipe
3. Select format data
4. Then you manually need to type "yes" with the keyboard
5. Confirm the wipe (this will remove the encryption)
6. Reboot your recovery
Q: Is there a way to get rid of encryption which is simpler?
A: Not really, you could also wipe data with stock recovery but this is quite a big hassle so above method works better.
Q: And if I want to use this rom with encryption?
A: Normally we can use the stock kernel to encrypt our device, but since the Android 7.0 Nougat update samsung makes a check kernel sides to block deodexed roms from booting. This means that even the stock kernel is build by me to disable knox and tima. So encryption won't work there and you have to encrypt your device after you set up your phone. After that go to settings, security, encrypt device. It may need some additional steps to work...
Questions about CSC/Signal:
Q: Where has the CSC selection gone?
A: To include all csc files, the rom get way to big, so it got it's own thread now, take a look here: CSC installer
Q: I have a weak cellular signal, what can I do against it?
A: Two things: first, install your providers CSC using CSC installer and flash in TWRP or flashing stock CSC with Odin. Second Thing: You can install the modem from your provider, also find your modem on Sammobile and install it with Odin in CP tab.
Q: I don't have all sHealth features, how come?
A: Not all CSCs include this feature. I recommend to use AUT or DBT as it has the best compatibility!
Q: Can I flash MM CSC on N and vis a verse?
A: No, this is clearly not recommend! You can and will face call fc's!
Questions about Xposed:
Q: Does Xposed work yet on Android N 7.0?
A: No it does not! You will end up in a bootloop when you flash it on android N
Q: I selected xposed but now I don't see an app for it?
A: Maybe there went something wrong with installing the app to /data/app from my installer script. But xposed is actually installed only the app is missing, so head over to the download page of xposed app: Material Xposed Thread
Q: I selected xposed but the app shows not active or something else with xposed is not working.
A: This can have 2 reasons:
1. You have installed latest xposed version without installing magisk, magisk is required for most recent xposed version!
2. You used 86.2 xposed (which does not need magisk) but you did not install supersu. Since 86.2 does not use magisk to be systemless it uses supersu instead!
Questions about Magisk:
Q: How can I pass safetynet?
A: 1. Make sure to fully uninstall SuperSU by chainfire
2. Flash most recent 2.4.3 SuperStock Kernel
3. Flash Magisk V12
4. install latest Magisk Manager from playstore
5. Open Magiks Manager, go to settings
6. Enable MagiskHide, systemless hosts and systemless busybox
7. Reboot the phone and check safetynet!
Q: I got out of date binary issue?
A: Since Magisk V11.1 there is no need for phh root anymore. Everything is handled inside the MagiskManager apk!
Q: Where can I configure the root settings in Magisk?
A: Since Magisk V11.1 Magisk uses MagiskSU, you can find it in latest Magisk Manager V4.1
Questions about Snapchat:
Q: Even when I did not use xposed during my setup in rom I can't login to snapchat anymore!
A: Snapchat got updated and now detects even root access on your phone!
Q: What to do to login to snapchat then?
A: Clean install the rom without root and xposed and login to your snapchat, save the app with titanium backup, flash back xposed and root. For the next update of the rom just restore snapchat backup in TB.
Q: Any other possibility?
A: You could enable MagiskHide and check Snapchat inside it so root will be hidden from Snapchat. You will be able to perfectly login without any issues.
Q: I want to discuss this problem a bit deeper. Should I do so?
A: Do that, but this has nothing to do with this rom, so please go ahead and post your experience here on this Snapchat Thread.
Questions about Kernels:
Q: I want to switch kernel, how?
A: Since we have systemless xposed and systemless supersu, we have patches in ramdisk of boot.img. This means you have to reflash Magisk and supersu (or any other zip that changes some stuff in ramdisk partition) after every change of kernel!
Q: Synapse shows no UCI support!
A: Most comon issue is that no busybox is installed. Download the one from here: Latest busybox and flash it in recovery.
Q: I got random reboots, heeelp!
A: This is most likely from a custom kernel, if you face random reboots please check if you have the latest kernel installed or switch back to the stock kernel included in the rom.
Q: My screen is kind of yellow/orange and the touchscreen doesn't work at all!
A: You have chosen the wrong kernel in aroma selection. Reflash the rom without any wipe selecting the right kernel version.
Questions about Root:
Q: I lost root after installing this rom. What to do?
A: All mods (like supersu, phh's root, xposed and magisk) are stored in ramdisk of kernel boot.img. So if you flash this rom, and after this another kernel, simply reflash your preferred root method and it will work again!
Q: I selected phh root but my phone tells me I am not rooted!!
A: There are two possibilities:
1. You have mixed supersu/phh with magisk.
2. You did not install phhs root app from playstore.
Q: I get a warning about binary out of date. Help!
A: That happens on latest Magisk V11.1. Reason: Root has fully moved into Magisk Manager, no additional app required. Uninstall phh or supersu apps and only use magisk!
Q: I want to use su hide on my phone, how to do so?
A: Both below variants are outdated, I recommend to use Magisk with its build in MagiskHide. Check the thread: Magisk Thread
Link to phh's hidesu: Phh's thread
Link to chainfires suhide: Chainfires thread

Hi,
I have a bit of a silly question. I have enabled the torch to be turned on by the volume button but now want to turn that function off and can't remember where i enabled it from. I have looked everywhere but can't find it. Are you able to point me in the right direction.
Many thanks.

reeves72 said:
Hi,
I have a bit of a silly question. I have enabled the torch to be turned on by the volume button but now want to turn that function off and can't remember where i enabled it from. I have looked everywhere but can't find it. Are you able to point me in the right direction.
Many thanks.
Click to expand...
Click to collapse
Hello
Settings, display, torchlight
Sent from my SuperMan powered SM-G930F

Tkkg1994 said:
Hello
Settings, display, torchlight
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Thanks that was driving me crazy.

downloadable files verification
Can some one verify that all of the downloadable files on the OP are the correct ones?
Can't seem to get it working, the steps I follow, are as following.
-> flash to stock rom from sammobile
-> OEM unlock
-> flash latest TWRP
-> in TWRP, format data
->install latest BL and CP from OP
-> flash rom -> Clean install
result is a non booting superman rom.. What can I do? I have been trying for DAYS now...

grave-diggers said:
Can some one verify that all of the downloadable files on the OP are the correct ones?
Can't seem to get it working, the steps I follow, are as following.
-> flash to stock rom from sammobile
-> OEM unlock
-> flash latest TWRP
-> in TWRP, format data
->install latest BL and CP from OP
-> flash rom -> Clean install
result is a non booting superman rom.. What can I do? I have been trying for DAYS now...
Click to expand...
Click to collapse
There are several reasons:
1. Encryption is still enabled
2. BL/CP was not successfull
3. You mixed your settings about G930F or G935F model

I noticed a few things in aroma log when it was installing
failure to boot.img extracting ramdisk failure, aborting, is this something that's causing the problem?
I am still not getting it right..

grave-diggers said:
I noticed a few things in aroma log when it was installing
failure to boot.img extracting ramdisk failure, aborting, is this something that's causing the problem?
I am still not getting it right..
Click to expand...
Click to collapse
Thats not really good lol. Redownload the rom. Maybe you got a corrupt zip file
Sent from my SuperMan powered SM-G930F

Holy crap I got it to work.. 4 days of trying to get this to work made me get alot of knowledge about this stuff, the file was corrupt, redownloading the file worked.

grave-diggers said:
Holy crap I got it to work.. 4 days of trying to get this to work made me get alot of knowledge about this stuff, the file was corrupt, redownloading the file worked.
Click to expand...
Click to collapse
Finally!
Sent from my SuperMan powered SM-G930F

Right at this point I am wondering why snapchat doesn't want to log me in. There's no xposed or snapprefs on my phone, exposed uninstaller was flashed. Does this come familliar? There has to be a workaround without having to use bluestacks right?

grave-diggers said:
Right at this point I am wondering why snapchat doesn't want to log me in. There's no xposed or snapprefs on my phone, exposed uninstaller was flashed. Does this come familliar? There has to be a workaround without having to use bluestacks right?
Click to expand...
Click to collapse
Someone said that it even checks for root now

Okay, here's the solution. If you find yourself having trouble logging in in to snapchat on a rooted device without xposed framework installed. Make sure to search for xposed using root explorer, delete all system files manually.. For some reason xposed uninstaller did not completely remove every xposed file in my phone.

SM-G930L
Does this ROM works on Korean variant? SM-G930L is the model. Thanks in advance

genorazer said:
Does this ROM works on Korean variant? SM-G930L is the model. Thanks in advance
Click to expand...
Click to collapse
Make a full backup and try
Sent from my SuperMan powered SM-G930F

Im on fully stocked g930fd
Can u confirmed is this the correct sequence
Root
Install twrp
Make a back up
Make a clean flash
Install superman rom

tatuboy said:
Im on fully stocked g930fd
Can u confirmed is this the correct sequence
Root
Install twrp
Make a back up
Make a clean flash
Install superman rom
Click to expand...
Click to collapse
No need to flash root. Flash twrp, flash bl and cp? backup, wipe (remove encryption) flash rom.
Sent from my SuperMan powered SM-G930F

Tkkg1994 said:
No need to flash root. Flash twrp, flash bl and cp? backup, wipe (remove encryption) flash rom.
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
Can u link to me the needed files?
If it have video tutorial much better..
Im from oneplus3 users before.
So i dont have much knowlege in s7.
I need to know
First how to flash TWRP?
2ND What is bl? U mean boot loader?
Cp? What does it mean for?
Then after i back up. And wipe.
How to remove encryption?

tatuboy said:
Can u link to me the needed files?
If it have video tutorial much better..
Im from oneplus3 users before.
So i dont have much knowlege in s7.
I need to know
First how to flash TWRP?
2ND What is bl? U mean boot loader?
Cp? What does it mean for?
Then after i back up. And wipe.
How to remove encryption?
Click to expand...
Click to collapse
Okay you want to install this rom. So go to my main page and follow all android beginner steps. Very detailed guide there
Sent from my SuperMan powered SM-G930F

Tkkg1994 said:
Make a full backup and try
Sent from my SuperMan powered SM-G930F
Click to expand...
Click to collapse
is there a chance it could brick the phone?

Ordered Pixel 2- awaiting delivery... Advice welcome!

OK, I’ve ordered and am awaiting arrival of my unlocked Pixel 2 from Google. I am on Verizon GFUDP and I plan on unlocking, rooting with Magisk and installing the tethering module. Then I plan on enjoying the phone and pretty much don’t plan on fussing around much with it.
I plan on unlocking before I do anything, including installing my Verizon sim. But do I have to allow the phone to do any upgrading prior to the rooting process? Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Any "must have" apps to take advantage of Pixel 2?
Any help or advice is much appreciated!
Thanks in advance!

I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices

amajamar said:
Do I have to allow the phone to do any upgrading prior to the rooting process?
Click to expand...
Click to collapse
You should.
amajamar said:
Also, can I (should I)hold off installing my sim until everything is rooted and up and running?
Click to expand...
Click to collapse
Doesn't make a difference.
amajamar said:
I was also thinking of using the Skipsoft toolset, but not sure if it is necessary. What are your thoughts on that?
Click to expand...
Click to collapse
I'd do it manually via the command line with fastboot and adb - knowing how to use these tools is very important in case something ever goes wrong.
amajamar said:
Also, regarding lockscreen security on the phone, is fingerprint or password required? Can you use one or the other? I never use a passcode in general so wondering how it works.
Click to expand...
Click to collapse
You can use both.

Diesel_Jeremiah said:
I purchased two Pixel 2 phones, and did the same thing you're planning on doing. I also have Verizon.
1) Unlocking the bootloader will wipe the device; Do this first. If you set up the phone prior to OEM unlocking, you will lose everything you set up.
2) Installing the SIM at anytime won't affect anything. When you install the Verizon SIM, some verizon apps will download. You can delete them if you want.
3) I did not use skipsoft. If you have a basic knowledge of ADB/Fastboot you will be fine without it.
4) The finger print reader is crazy fast. Also, setting up the phone it asks for a pin. Try it with the security of both to start. If you dislike it you can disable it in the future.
5) Apps I like/use: Tasker, Magisk, Titanium Backup, Custom Navigation Bar, Hide "using battery" notification, AdAway, Nova Launcher, Swipepad (where I put the "reboot" shortcuts), Reboot (Material Design) [ I made shortcuts to enter recovery, bootloader, etc], 1weather, Digilux (screen brightness control from the fingerprint reader), and Naptime (Have seen some battery length increase, though slows down notifications)
6) Not really apps, though @Tulsadiver made mods via Aroma from here: Various Mods for 8.1 December Update (Added Screen shots to show black notifications, battery icon removal, and clock w/day & ampm)
7) I like the Snoke kernel found here: [KERNEL]Snoke Kernel by @DespairFactor
There is a guide here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) by @nathanchance
I laid out steps in this post here: [GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye) - Post 127
Here are links because sometimes they can be tiresome to find:
SDK Platform Tools
(Follow the steps in the linked Post 127 to make cmd and SDK tools easier)
Factory Images for Nexus and Pixel Devices
Full OTA Images for Nexus and Pixel Devices
Click to expand...
Click to collapse
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.

amajamar said:
Nice! Thanks! No need for TWRP? I was going to install it.
Was there a "thing" regarding which version of Magisk to install? I thought I read something somewhere about issues with the newest version.
Click to expand...
Click to collapse
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.

Diesel_Jeremiah said:
I have TWRP installed as well. I didn't comment on it since you didn't ask about it.
NOTE: You have to boot TWRP img, then install TWRP ZIP. Search threads, you'll find the info.
NOTE 2: You cannot install TWRP, Magisk and Kernel at the same time. Best way is to install everything is: TWRP ZIP, reboot. Flash Kernel, reboot. Flash Magisk, reboot.
As for Magisk, I'm on v5.5.3 and V15.2 without issues.
I've been upgrading through Magisk direct install without issues.
NOTE: You will get a pop up that your system has an issue and contact the manufacturer after Magisk. Do not panic, it'd because Magisk is modifying the DTBO img. It does not harm anything.
I also installed Viper4Android from Magisk.
Version 2.5.0.4 = works normal and processes correctly.
Click to expand...
Click to collapse
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.

amajamar said:
Awesome! What features does the Snoke kernel give? Any issues with it? Do you need to flash the factory kernel to take an OTA?
I never used Viper4Android before. What does it do?
Thanks.
Click to expand...
Click to collapse
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.

Diesel_Jeremiah said:
Custom Kernel: Android Basics 101: Understanding Kernels – XDA Developer TV
I feel a bit snappier response and better battery life. There is Snoke, Flash, and ElementalX to name a few.
If you've loaded TWRP at all or mounted system rw; OTAs will not work. You'll have to use the factory images.
I've had no issues with the Snoke kernel. Just ensure you use the proper one for 8.0 or 8.1.
Viper4Android: Get the Sound you Deserve with ViPER4Android -- Android App Review
Viper4Android and Pizel 2 front facing speakers work very well together.
Click to expand...
Click to collapse
Excellent information! Thanks!