Database Develop

[Root] Replacing Superuser app with Super SU by CF

Super SU by CF
SuperSU is the Superuser access management tool of the future
Features include:
- Superuser access prompt
- Superuser access logging
- Superuser access notifications
- Per-app notification configuration
- Temporary unroot
- Deep process detection (no more unknowns)
- Works in recovery (no more segfaulting)
- Works when Android isn't properly booted
- Works with non-standard shell locations
- Trusts ADB connection
- Always runs in ghost mode
- Wake on prompt
The Pro version additionally offers:
- OTA survival mode (no guarantees)
- Full color-coded command content logging (input/output/error)
- Per-app logging configuration
- Per-app user override
- PIN protection
Who, What Why ? - said by CF
As you may know, I make a lot of apps that use or require root. I also release rooted kernels. I run into a lot of issues with existing Superuser tools. More importantly, a lot of my users run into these issues as well and then email me about it. So I decided to do something about this. Doesn't mean these were problems you have ever seen, or will ever see.
And thus, I have written - pretty much from scratch - SuperSU. I have taken the su binary command line parameter parsing from Superuser, to make sure that is compatible. Aside from that, it is completely rewritten, because how I wanted to do a number of things was incompatible with the existing codebase.
This is not a stab at ChainsDD, or his skills. He has done great work and will no doubt continue to do so, however, I felt the need for some of these changes, and thus made them. This is an early release, so I expect there will be some unforseen issues somewhere.
From now on, all CF-Root and Mobile ODIN Pro (EverRoot) releases will be built around SuperSU.
Please note that SuperSU is not hardened-security-tested or reviewed, and may be exploitable (... as may other solutions ...).
Install :
Flashable Zip v0.93
Market :
Lite
Pro
Note : Pro is key only, you need to install lite version first.
If you install from market, you will have two superuser, remove older one with system appl remover, or any other application can perform same job.
Remember, if you remove older first without installing newer one, you will lose Root n newer won't run.
One more thing market version will be regular application, so hard reset can delete it. So better install with flashable zip, to make it system application.
Source : http://forum.xda-developers.com/showthread.php?t=1538053

Thanks a lot doc. Gonna give it a try.
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Sorry to say but this belongs to General Section.

Nice one, Dr.Ketan.
Perhaps your fine installation instruction could also include this:
"Superuser (the old one) is a system app and should be removed from /system/app/ folder using Root Explorer, ES Eplorer with root permissions, or similar explorer app. Titanium Backup does not show Superuser in its app list, and therefore cannot remove it."
Otherwise you'll be swamped with Titanium questions.

This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..

dr.ketan said:
This is modding
any thing android Mod, should be better place under development.
thogh let's leave it upon moderator..
Click to expand...
Click to collapse
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...

grgsiocl said:
i think it doesnt work if USB debugging is enabled and if it is disabled then it works fine...
Click to expand...
Click to collapse
CF says he has fixed that bug in v0.74, and that's the one posted here.

I have no issue with USB debugging ON

Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA

kopitalk said:
Confirmed working fine! Recommended to install via CWM. It will replace the other automatically so you don't have to manually remove it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Newbie question here, (sorry) so you don't just download from the market/play store..... open and it will install on it's own?
Sent From my Two Tin Cans & String Device on The Wookie Network

It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market

dr.ketan said:
It will install, but not as system application. So it is recommended to flash with CWM. as well you have to remove old manually, if you install from market
Click to expand...
Click to collapse
Another newbie question... Is there enough of a difference between superuser & supersu for a newbie to risk mucking up their phone?
Thanks!
EDIT : are there instructions as to how to flash with CWM? SORRY!!
Sent From my Two Tin Cans & String Device on The Wookie Network

Superuser v0.75 has been released.
Changelog:
10.03.2012 - v0.75
- Adjustment to OTA survival (better!)
- Slight speedup in Settings
- Fixed native settings update after temp-re-root
- Clear data no longer clears PIN code
- Layout: Prompt: Grant and Deny switch positions (ICS style)
- Layout: AppDetail: Save and Cancel switched positions (ICS style)
- Layout: Added xlarge PIN layout
http://forum.xda-developers.com/attachment.php?attachmentid=940641&d=1331395344
P.S. Dr.Ketan, when I try to download CWM flashable zip from your 1st post I get a 404.

Ya b'coz link replaced by CF with new version
updated now

dr.ketan said:
Ya b'coz link replaced by CF with new version
updated now
Click to expand...
Click to collapse
even mobile Odin is updated with 2.25

Very Slow Boot Up Following Switch to SuperSU Pro
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz

krazman325 said:
My Note is running rooted stock ROM with Franco.kernel v6. After installing the SuperSU v.75.zip with CWM and installing the Pro key, and removing Superuser.apk my Note is VERY slow to boot up. It took less than 1 minute immediately prior to SuperSU and now takes 5-6 minutes. It runs wifi and mobile data and sync together EVERY time it boots. It never did this before. It also runs "Media Scanning 6-8 times before it finishes booting.
I'm not complaining, just informing. I realize that this is a new work in progress as posted in the OP post #1. Is anyone else having these issues? If not, any suggestions to correct these problems? I have tried clearing Dalvik and cache partition through CWM app.
Thank you for any help and/or advice.
kraz
Click to expand...
Click to collapse
what you said was true...it slows up booting...but what i did was, in supersu app, i selected grant as default and there is no need for prompt...after that, booting as speed up!

I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Sorry for wasting space in this thread!!! Hopefully, anyone else having similar trouble will see this.
kraz

Thanks Doc!flashing now

krazman325 said:
I actually found my own solution as you were posting! Thanks for your help, grgsiocl!!! I did leave default access set to PROMPT though as it will only show the first time until i grant permission.
MY SOLUTION: I unchecked the show Notification Toasts, rebooted and total boot up took 50 seconds!
Click to expand...
Click to collapse
Yeah, this is what CF has to say about it in his original thread:
Chainfire said:
PROTIP:
For extra performance, disable notifications. Logging does not impact performance much.
Click to expand...
Click to collapse

I think it would have been better to just link to chainfires thread rather than repost what he posted.

Recent Button, Home , notification & lock Screen not working - Xiaomi Mi3

I am using MIUI Global 7.5| Stable (7.5.1.0 MXDMIDE) ROM & suddenly the notification area and lock screen is not working. The recent button and home button on the device is also not working. I was researching the web regarding the bug is android which might be causing this issue?
See this link here >> Android Police link >>
How To Fix Missing Home And Recents Buttons, And Notification Shade That Refuses To Pull Down After Android Update
Second Link >> Google Plus Link of PaulOBrien >>See this also
Now both the above try to resolve by connecting the mobile to you desktop/lappy in order to execute the command. There is an alternate option available here which might also work >> S7 Edge not showing notifications in tray and "recent apps" button and settings button dnt work
It talk about doing it by following this steps
"And I followed what the user Mike Tompkins said: "Did this using nova launcher. Long press home screen choose shortcut, activities, setup wizard, setup wizard test activity. Creates shortcut, open follow directions. Not sure if it really helps. Didn't have issue."
Here's the fix, being broken down dummy style:
1) Download Nova Launcher & set it as default to replace TouchWiz.
2) Long press on the home screen.
3) Choose Widgets.
4) At the top, under Nova Launcher, scroll to the right & press & hold on Activities and place it somewhere empty on the home screen.
5) Scroll down to Setup Wizard. I saw 2 Setup Wizard options.
6) Under the first Setup Wizard option, I opened it & scrolled down to the 3rd choice which said ".SetupWizardTestActivity". It might be in a different spot for you, but look at the small writing, that's how I saw this one.
7) Select that to create the widget shortcut.
8) Open it. Apparently you're supposed to have a menu to go through and just click through "Next", but there wasn't one for me.
The screen just flashed and then next thing you know, everything works!
But I am unable to find the .".SetupWizardTestActivity"
Any suggestion?
Moreover whenever I am going to developer option I see this message "Developer option is not available for this user"
I am sure I don't have any other user added to this handset.
Help & suggestions?
I have been able to access the device using abd, after adding permission, and have downloaded the logcat files of the device which is attached herewith >> Unable to attach logcat as am a new user, let me know how I can add them.
Now when I am connecting the devices via adb, the devices are showing in adb devices.
When i am executing this command >> adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
I am getting this following message:
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardTestActivity }
Error type 3
Error: Activity class {com.google.android.setupwizard/com.google.android.setupwizard.SetupWizardTestActivity} does not exist.
I am not sure why this problem is appearing? any help to fix this issue of home button, recent button, notification issues fixed?

thing happened to you,seems like a system ui absence .. just reflash the rom ot try any other custom roms available.. or just a factory reset might help,,if not hepfull, i would insist you to try a custom rom..
btw are you rooted??

thilak devraj said:
thing happened to you,seems like a system ui absence .. just reflash the rom ot try any other custom roms available.. or just a factory reset might help,,if not hepfull, i would insist you to try a custom rom..
btw are you rooted??
Click to expand...
Click to collapse
Yes the problem seems to be System UI or something, I am not sure. I had rooted the device after the problem appeared, but it didn't able to resolve the issue. Today I had installed MIUI 8.0 on the device and all the problem disappeared, so it seemed like the problem, was with the bug in MIUI 7, or inherent bug when upgrading from KitKat to MM.

[ROOT] SM-T707A - Lollipop with SuperSu - Xposed & Debloated - Part II

Root SM-T707A on Lollipop with SuperSu - Xposed & Debloated - Part II
Where are we right now?
* Part I: Flash Stock Lollipop 5.0.2.
* Part II: Gain Root access for Lollipop with SuperSU. <---- YOU ARE HERE!
* Part III: Flash Xposed Framework thru Flashfire.
* Part IV: Debloat the tablet from both AT&T and most of Samsung stuff.
* Part V: Improve usability and aspect with Xposed Modules.
Once again, some words of our sponsors: NO, I'm NOT resposible for any consequence originated from the use of this guide, being that the death of your tablet, or your smart tv, the Panama Papers or Luis Suarez just playing rough with Filipe Luiz's foot. Whatever happens to your tablet, it's ON YOU.
Introduction (PLEASE READ!):
This guide works as a continuation of Part I, so we assume you flashed KitKat and applied Lollipop updates as described.
If you are already on Lollipop and have several weeks using it, of course you can try this guide, but I STRONGLY SUGGEST to start from zero, backup your files and use the guidelines on Part I of this guide.
Part II: Gain Root access for Lollipop with SuperSU
IMPORTANT - During the first boot on our brand new lollipop, don't try to connect to your WiFi and remove your SimCard if availble before even selecting any option. We don't want any internet at this time.
Our first move in Lollipop is to Reject all the AT&T offers..
Then accept terms of Samsung EULA (and hit No Thanks below)...unless you want to share information with Sammy.
Then you can put your name (I didn't), it' s up to you.
Disable the 3 checkboxes for location services (you can enable this later).
Then skip the Samsung Account creation and hit also Next on my "Find my mobile" screen without doing nothing.
Finally, you'll reach the Android Desktop.
Setting the stage for rooting with KingRoot
Still avoiding any conection to the internet, go to your apps and tap Settings.
Before doing nothin, I strongly suggest you change your language to english in case you use another.
If your first language is English, you're good.
If it's not, you can change it on General TAB, then "Language and Input".
After this, tap the Device tab, choosing then Display option on the left.
Choose Screen timeout and select 10 minutes.
Now select Lock screen on your left and Screen lock on your right. Tap "None".
Now go to "General" tab and tap "Security".
Enable the Unknown sources checkbox and press OK on the popup.
Press home button. Now you can connect to your Wifi.
The moment you got Internet, Samsung will start forcing some updates on your tablet.
At the same time, several Google popups will ask you to "regularly check device for security".
Decline them all the time!
There is a "Games" app that loves to open itself without asking
When that happens, it will introduce you to an agreement that you will REJECT.
If it doesn't show, better. But it will eventually.
Now enter the Play Store and Log in with your credentials.
Accept the playstore conditions when prompted. If you are kicked out of the app just enter again.
Still inside Playstore, now swipe from your left side border to gain access to the menu.
Tap "My Apps" and use the "Update All" button on the right.
Accept all APP Permisions (seven times in my case).
The update process will start. This will take some time so BE PATIENT and do nothing else.
When everything is updated, you'll notice some warning on your status bar.
Swipe down your status bar. It will ask several times to Update Google Play Services.
Tap any of update offers for Play Services. Playstore will open again offering the update.
Hit Update and Accept. When the update of Google Play Services is finished, hit the Open button.
You gain access to Google Settings. Tap Security.
Disable "Remote locate this device" - "Allow remote lock and erase".
Disable also "Scan device for security threats" and "Improve harmfull app detection" (unless is greyed out).
Hit the home button and go back to desktop.
Installing KingRoot
For the next step, you need to download these files on your PC:
* Kingroot V4.90
* RemoveKing
Copy them on your tablet's internal memory. Specifically on the root of your internal memory. If you copy them inside a folder, later commands will fail.
Back to your tablet's desktop, look for the folder icon on the bottom left corner. This will open the Samsung File Manager. Look for "Device Storage" on the left column. If you copied the files correctly, you'll find both on the right pane of the display. Extract the RemoveKing.zip file by tapping it and clicking "OK". A RemoveKing folder will appear on the root of your filesystem.
Now open the Kingroot V4.90 file. Hit Next and then Install.
If a google warning appears citing - "Installation blocked". Hit "Install anyway" (unsafe).
If it doesnt, just hit Open. A blue screen shows up with the legend "ROOT auth".
Swipe upwards twice (assuming you're holding your tablet in portrait).
Now hit the "Try it" button. The app will verify root status in a matter of seconds.
Now tap the "TRY THE ROOT" button at the bottom.
When the root is sucessful, you'll be asked to "Forbid Knox".
Tap Cancel and press the home button. Now you are rooted with Kingroot.
Installing and preparing Terminal Emulator
Now that we are rooted, enter the playstore and install the app "Terminal Emulator for Android". Open it. You'll notice some small font selected so, hit the 3 dots on the right upper corner and go to preferences. On Font Size choose 24 pt. Hit the back physical button of the tablet. Now the "white letters" become readable. And it shows something like:
Code:
klimtlteatt:/ $
Next type the following and hit enter:
Code:
su
A Kingroot popup will ask for root permission. Tap "Allow".
Now the $ symbol will change for #.
Next you hit the HOME button to exit the app briefly (don't close the app in any other way, just hit the HOME button).
Uninstalling KingRoot
After that, go to your apps and enter the KingRoot app.
Now tap the 3 dots on the upper right corner and select "General Setting". Disable "Smart Authorization", then disable "Enable Root Authorization". Finally choose below "Uninstall KingRoot". Hit Continue. Uncheck "Backup Root" when prompted and hit OK. When all is over, you're back to the desktop. Go back again to your apps and uninstall Purify.
Applying the Scripts
Open again Terminal Emulator app (thru the app Icon) . Now we need to hit a couple of scripts by moving first to our extracted folder by entering the following command on the terminal (plus enter):
Code:
cd /sdcard/RemoveKing/
To run the first script type (then press enter):
Code:
./step0.sh
It just takes 3 seconds, then type the following and press enter:
Code:
./step1.sh
This last script will ask for a confirmation during its process.
Type just an "y" and hit enter: (WARNING, the Y won't appear on your display after typing it)
Code:
y
You'll notice a bunch of errors, don't mind them.
Installing SuperSU
Now hit the home button and go to the play store.
Search and Install SuperSU (free version). Open it. Choose Expert.
The app will ask "The SU binary needs to be updated, continue?".
Hit Continue and then choose "Normal" when asked on the next popup.
You'll receive an "Installation Sucess!". Tap the Reboot option.
Congratulations! You are now rooted with SuperSU.
After rebooting, enter the Terminal app once more, and tap the X on the right upper corner and hit OK.
That will finish the current terminal session.
If you're interested in getting Xposed Framework, go to part 3 of this guide.
If you're just interested in debloating the SM-T707A and improve its performance, go to part 4 (Soon).
Part 5 is where I discuss the modules I'm using on Xposed and also some Playstore apps to improve functionality, and remove as much Touchwiz as possible, while also working on better battery life (Soon too).
Final Considerations (suggested reading - not mandatory)
While this guide may seem easy to carryout, it took me almost a month to get SuperSu to work on Lollipop.
I'm no coder (a soon to be Certified Public Accountant), and the real magic to pull this off was to try many combinations of different app versions, different situations with google services and several strategies with the script and superSU. In fact, most of KingRoot versions don't work on this tablet to get root, also tried SuperSume app from the playstore. The same could be said for KingoRoot (don't confuse it with KingRoot), it worked but I couldn't remove it without losing root.
Why I'm telling you this? Because using KingRoot and similar apps to root this tablet, your mileage may vary while doing it. In fact, even while applying my first two guides there's a respectable chance of KingRoot tool failing to root your tablet. If you followed this couple of guides to the last comma, your chances of success are very close to 100%. But I have noticed in similar Galaxy Tab S threads, that the use of KingRoot and KingoRoot to achieve root is just a matter of using the root tool many times until it works, and I wanted to avoid you guys going thru that. To take sucess rate as close as it gets to 100%, we took all of this steps. They were included to avoid many failures. I believe they're are 99% flawless to achieve root on Lollipop with SuperSU.
Also, the second script won't remove many KingRoot files, because it was thought for KingoRoot on KitKat.
I have to give myself more time to develop something that could really clean up the last traces of KingRoot.
Special Thanks
* @chixvicious - For showing how to achieve the same over KitKat and KingoRoot instead.
* @bakageta - For creating these scripts for the Alcatel smartphone over KingoRoot.
* @Kingxteam - For developing KingRoot to allow us to root our device.

Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.

bakageta said:
Oh wow, I had forgotten all about those scripts. Glad to see someone getting some use out of them.
Click to expand...
Click to collapse
They were life-savers, thanks a lot for them!!

Broken links?
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.

zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!

kainanmaki said:
Thanks for the heads up!!. I'll check them ASAP.
EDIT: All links are fixed!!
Click to expand...
Click to collapse
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again

ElCid43 said:
Man, can't thank you enough for this...So great for someone like me with little knowledge for all this magic. I am gonna do this when I get back from vacation. Can't wait for the rest of it!
Thanks again
Click to expand...
Click to collapse
I hope to get part IV and V in no more than 10 days...
I'm in the process of testing removing/freezing many services, just a sneak preview:
So far I was able to disable close to 180-190 apps/services from a total 250-260 (can't remember the exact number).
Of course there are some key services removed (for e.g multi windows, but that's just one service).
Still you can easily remove like 165 without losing any stock functionality. That's how much bloated the tablet is.
Removing useless stuff from samsung and 3rd party (eg. VPN, Policy Updates) or more evident like MultiWindow, the gallery app or even the file browser.
Or the weird ones like the phone app that is hidden and you can't use (you can disable it and still keep LTE Data).
More to come.

Need Help - Having Untimely Reboot Issues
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom

Where did you find the alternate method??
zopert said:
First and foremost, thank you for the thorough walkthrough.
I've come across an issue with the provided links to KingRoot and RemoveKing. When I click on either, I receive the following message:
"Invalid Attachment specified. This can happen for a variety of reasons-- most likely because the thread or post you are trying to view has been moved or deleted. Please return to the forum home and browse for another similiar post."
Do you have any alternate links available?
EDIT: I did find an alternate method that worked for proper replacement of KingRoot with SuperSU. All good, and glad for the compatible xposed framework.
Click to expand...
Click to collapse
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom

TomandJonna said:
Wow...Thanks SO MUCH for this guide! It gives me hope that I can actually enjoy using my T707A to the fullest!
Alas, I need some assistance PLEASE:crying:
I'm following your guide to the letter, and I've successfully achieved Part 1. Part 2, however, alludes me even after many, many tries. Here is what is going right and wrong:
a) Achieved root with KingRoot
b) installed and achieved SU with Terminal
c) ISSUE - KingRoot (or something) reboots the tablet during Uninstall, which kills SU access obtained with Terminal
d) ISSUE - after reboot, I no longer have permission to run the scripts to uninstall KingRoot
Is there another way for me to do this? As long as the tablet is rebooting during uninstall of KingRoot I have no SU access, so can't do anything but start over and experience the same thing time after time.
ANY assistance would be so very much appreciated...MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
I had that problem many times, the uninstall reboots the tablet before you can establish SuperSu.
The most reliable way I found of overcoming this is to follow the exactly in this order and without stopping to much because google wants to run updates behind scenes that mess with our process (that's why sometimes it works and sometime it doesn't). My recommendation is to start over from scracth again (I know it's boring). I'll probably do it again on my tablet just to validate and to try some other things related to the original services).

TomandJonna said:
Hi...I am VERY interested in your "alternate" method for replacement of KingRoot with SuperSU that actually worked. Would you be so kind as to share that with me? I'm having huge troubles (see my post) replacing KingRoot as it reboots thus killing my SU access necessary to run the uninstall scripts provided in OP. Any help would be GREATLY appreciated. MOST humbly & sincerely...Tom
Click to expand...
Click to collapse
Other thing I forgot to ask, did you started clean from the first part or just started with part 2 of the guide?

Will this method trip Knox?

i need * RemoveKing file now...

[MOD] Nougat_PlayStore_Rom_Addon_ADB_Install

Must Be on Nougat Rom!!!
I recommend Starting on freshly wiped rom but. This requires Package Disabler Pro Be Installed.
PlayStoreNougatMods.zip
Extract zip
Enable Usb Debugging
Disable Verify apps over USB
Enable all disabled apps
Plug phone into computer watch phone screen accept usb debugging key for computer
Run Install_PlayStore_Rom.bat
Follow Instruction On Cmd Screen
Once Install Is All Done
Select Pixel For Home Launcher
Open Settings/Application/Default Application under Calling Select Phone
Open Language and Input
Open Virtual Keyboards and click manage keyboards and turn on GBoard keyboard
Open Developer Options
Set Window Animation scale to .05x
Set Transition Animation scale to .05x
Set Animation Duration scale to .05x
Open settings goto accessibility
Enable all the servicesexcept talkback unless you want it
In settings open applications
Open applications manager
Goto menu select speciall access
In Phone Administrators enable all except android device manager unless you want that
Now click back button and open Draw over other apps and enable all
Click back button and open Modify system settings enable all
Click back button and open Notification access enable all
Open Rom Control and Everything Installed will be accessed there
Features
Pixel Dialer V8 With working Video Calling
Pixel Contacts
Google Camera
AOSP Browser
Google Messenger
Google Clock
Google Calculator
Call Recording Via BoldBeast
Rom Control Mods
DNS66 Ad Blocking
Status Bar Mod
Torchlight With Volume Buttons
Access To IMS Settings And Advanced Calling
Keylight Duration Settings
Battery Bar +
Status Bar Internet Speed
Recent Bar In Notification Panel
Button Remapping Via AIO Gestures
Volume Button Music Skip
Fingerprint Gesters
Led Control Via Light Flow App
Volume Panel Mod

View attachment 4048810View attachment 4048811View attachment 4048812View attachment 4048813View attachment 4048820View attachment 4048821

Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk

jonesj198 said:
Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Inquiring minds want to know

I guess you havent seen this thread https://forum.xda-developers.com/ve...din-stock-nougat-firmware-s7-edge-to-t3558313
It will work on stock beta 2 but I have the official tmobile nougat firmware working on our phones. Only thing that doesnt work is wifi calling and Visual Voice Mail but Volte and Video calling work. So you might want to look into that

Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Sent from my SM-G935V using Tapatalk

jonesj198 said:
Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Click to expand...
Click to collapse
Did you accept the adb key when prompted did it install anything

Here is the package disabler pro import script. You can also just istall all of the apks manually if you have to
View attachment PlayStore.zip

I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Sent from my SM-G935V using Tapatalk

jonesj198 said:
I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Click to expand...
Click to collapse
When you first start bat file does it show device as unauthorized

jrkruse said:
When you first start bat file does it show device as unauthorized
Click to expand...
Click to collapse
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Sent from my SM-G935V using Tapatalk

jonesj198 said:
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Here if you dont have those numbers before device its not recognized

Is usb debugging enabled and verify apps over usb disabled

Did you accept debugging key. If this never came up. In developer settings click revoke usb debugging the unplug and replug your phone into computet. If the below screen still doesnt come up start the bat file then it will pop up. Accept key close bat then reopen and start process

jonesj198 said:
Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Installing apps manually will work just fine. Then just copy the playstore.xml file from the zip of it I posted and import it with pacage disabler pro it should disable 126 packages

stud

Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.

CyanideHD said:
Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.
Click to expand...
Click to collapse
What build is your rom. Beta 2?

jrkruse said:
What build is your rom. Beta 2?
Click to expand...
Click to collapse
TMobile nougat.

CyanideHD said:
TMobile nougat.
Click to expand...
Click to collapse
If you have the rom control app open it under useful apps and open samsung info and tell me your csc version

[ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]

Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!

Some screenies:

Saved2

Saved3

Well nice job!

jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread

kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?

jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)

jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again

kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified

It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!

First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.

charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!

FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!

New version, see change log in OP for details.

Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.

jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his

Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek

Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.

Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!