Database Develop

[INFO][HELP][FIXES][HOW TO] Collection of Help - Info postings for the Nook Color - x

HELP
I've got a problem with my Nook Color (BNRV200)​
Tired of searching for a thread that tells you what to do when you need to install, fix a problem, need a recovery, etc. I have compiled a number of links to various threads by developers and others that answer questions that get asked a lot. This post is intended to give a site that will make finding these answers easier than a regular search. It will have a list of threads and posts with various helps, have a topical list of problems and sites which address those topics, links to common sites and app needed to get what both Noob and seasoned members need to work with and on Nook Colors.
You choose to make changes, flash ROMs, etc. it is your choice. You assume all responsibility for what ever happens. I list these links because I know they have helped and work for me as well as many others. If you need help with a particular problem addressed in these links, ask on those threads.
If you use information in any of these links make sure to click on the thanks button both here and in those links. If you want to write a thank you note also, that to is fine, but does not add to the "Thanks" counter. These people have worked hard for free that we can have greater enjoyment and fun with our tablets. Most get nothing for their time and effort so "thanking them" is their greatest return and the least the rest of us can do in appreciation. Credit and kudos are given by Authors Names in Post #2
By Topic​(A)
Add Network speed to Status Bar. Post#3
Android.process.media force close or crash Click here Also make sure all Google apps are updated, defrost frozen ones, update in play, refreeze (Mine was Gmail) (Thanks bowguy)
(B)
Boot Loop Problems (2)
Bootable CWM Recovery SD (v5.5.0.4 and now v6.0.1.2) (1)
(C)
Change "Status Bar" or "Navigation bar" colors or heights (for two rows of status info). Post#3
Change perceived DPI, rotation behavior, fullscreen, permissions on a per app basis Post#3
(D)
Dual Boot Nook (12)
(F)
Faster bootup
To get faster bootup you can disable the boot animation and save about 30 seconds from boot up time by adding "debug.sf.nobootanimation=1" to the build property file in the /system folder. This is a pain though if you keep up with the nightlies regularly like I do. I got tired of editing the file for every update or reversion if there was a problem with the newer nightly. So I created a script that goes into the Userinit.d folder that checks build.prop on every boot and adds the line if needed without any further intervention. The first boot after installing a new nightly will have the boot animation but no more till the next install when the process will repeat all automatically. Download the AutoNoBootAnimationScript.zip in attached files below, unzip, follow the included instructions and enjoy.
Faster SD card access. Instructions bottom of Post#4
Freeze/Disable applications (1)
(G)
Google Play says, "This app is not available for your device"
Get Xposed Framework in Post#3, download "PlayStore Fixes", set Fake density 240, Check No Restrictions Patch. Clear Google Play Store data, reboot enjoy.
(H)
Home button / icon stopped working, defrost / enable android Keyguard
How can I make my ROM run smoother, have more free memory or have longer battery life. Post#4
How to play flash video on Android 4.4 Kitkat in Dolphin Browser (14)
How to do a Logcat (13)
(I)
I wiped, erased, formated my /ROM (#2) partition (2)
Installing CM11 and get Status error 7 or other problems - Must use CWM 6.0.4.7+ or TWRP 2.6.3.0 (Download below)
Installing new CM11 and latest Gapps and no Google Play. Problem /system is too small.
The Prefered way to fresh install latest nightlies: If you do a conventional (no repartition) install using the smaller 01/05 Gapps and install the other Goople apps through Google play. They install into the /data directory instead of the /system. You can do this also with Gmail, Sound search (ears), Google TTS and Hangouts.
Alternate experimental adventurous way. There are two .zips available that will repartition your Nook and give you more /system space and /Data space.
Dweatons mod of Leapinlarswork, Repart.zip, is here and will yield 1.1Gb /System, 2Gb /Data, and 3.6Gb /Media.
Mine is here and will yield 1.1Gb /System, 4.5Gb /Data, and 1Gb /Media. You must get and use a reformat 5,6,7,8.zip after the running the repartition.zip for dweatons get Leapinlar's here. For mine get it here. the difference is for his you must install with CWM before 6.0.3.6, mine works with 6.0.4.8. Reverts to B&N Stock /system are available here.
Installing CM on EMMC CM11 (8), CM10.2 (9), CM7 or CM10 (6)
Installing CM on SD (3)
(M)
Make Play Store show All apps in listings Post#3
Modifying partition sizes original (5) Modified for CM11 and CWM 6.0.4.8 (15)
More SD card storage Use a 64 Gig SD Micro. Instructions bottom of Post#4
(N)
Nook won't boot (7)
(P)
Put Play Store link in App info window Post#3
(R)
Recovery boot loops (1)
Repairing partitions, blank screens and cannot flash new roms (2)
Restore Nook Color to Stock, (4)
Running Netflix app in CM 10 and 11 (11)
(S)
Screen touch sensitivity a little off. Try Nook Screen Recalibrate in Google Play
SD Card install tips Leapinlar's Tips post #2
Stock Nook Color Roms Leapinlars (1.4.3), Dizzy Dens (1.4.1)
(V)
Video Flicker in CM11 Crackle, Hulu and other video sites and apps, update to CM11 nightly 4/22+ or (10)
Volume / Sound to low. Try Speaker Boost in Google Play. Caution:
Mine works great @ 50% boost. Be very careful above 40%, go slowly and safely. If you want to rename the DSPmanager goto post #6. If you have CM 10.2+ (4.2.1) you must do the renaming since the DSP version since then throttles back the sound levels.
(Y)
YouTube updated and asked for update for Google Play Services but Google play has no update. Get Version 4.2.43 here: (11) (At bottom of attached files) Latest (4/20/2015) New update on Youtube and / or Google Play problems. Solution here: http://forum.xda-developers.com/showpost.php?p=60241045&postcount=54
(W)
Where can I get:Gapps http://wiki.cyanogenmod.org/w/Gapps
Latest Nightlies http://download.cyanogenmod.org/?device=encore&type=nightly
Recoveries (download in attached files below)
Stable versions http://download.cyanogenmod.org/?device=encore&type=stable
Older releases of CM 10 or CM11 http://techerrata.com/browse/cm/encore/nightly​ List of Authors of Post
To whom credits and thanks are due!
See Post (#2)​
If you know of other Help, Info, etc sites post a reply I'll check it out and include it in the lists above. Even if the post are not on Nook Color forum, If it worked for you on your Nook, post a reply with your Rom version and I will check it out and consider adding it to this list.
Recoveries​ The recoveries I have are listed below and can be downloaded in the attached files box. The MD5 sum files are in the MD5 sums for recoveries zip. Download it, un-zip it, and check with the approriate recovery. These are for the Nook Color (BNRV200)
CWM Recoveries3.2.0.1 - Good for CM7 Eyeballer or nemith
5.5.0.4 - Good for CM7 thru CM10.2 Racks
6.0.1.2 - Good for CM7 thru CM10.2 - LeapinLar
6.0.5.0 - Must have for CM11 5-16+ Nightlies eMMC & SDCard installs - polymath257
6.0.5.1 - Latest Available - rjwil1086​TWRP Recoveries2.3.1.0 - From TWRP Site
2.4.1.0 - Eyeballer
2.6.3.0 - Must have for CM11 thru 5-15 nightly (use 2.4.1.0 for pre CM11) - Eyeballer
2.8.3.0 - Must have for CM11 for 5-16+ nightlies - rjwil1086​(nba#+5)

[INFO][HELP][FIXES][HOW TO] Collection of Help - Pt2
By Author of Post​
Dean Gibson
Repartitioning the NC to 1-5 Gb, 2-4Gb and 5-1 Gb: (5) http://forum.xda-developers.com/showthread.php?t=1094371
Eyeballers
Install CM7 or CM10 + Recovery to EMMC: (6) http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color
Leapinar
Tips: (1) http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
EMMC Repair: (2) http://forum.xda-developers.com/showthread.php?p=28457126#post28457126
Nook Color Installation Guide for CM7/CM9/CM10/CM10.1/CM10.2/CM11 on SD: (3) http://forum.xda-developers.com/showthread.php?p=32921666#post32921666
nismopc
Running current Crackle TV 4.0.3 on CM11 Nightlies: (10) http://forum.xda-developers.com/showthread.php?t=2634964
Nootered
Restore to Stock: (4) http://forum.xda-developers.com/showthread.php?t=931720&highlight=fix+boot
pastordl
Running current Netflix app in CM 10 and 11: (11) http://forum.xda-developers.com/showthread.php?p=44626173#post44626173
Repartion and reformating zips for CM11 and CWM 6.0.4.8: (15) http://forum.xda-developers.com/showpost.php?p=54401912&postcount=4177 (From Dean Gibson's work, also Leapinlars and Dweaton)
paxChristos
[Tutorial] How To Logcat (13) http://forum.xda-developers.com/showthread.php?t=1726238
RileyGrant
Dummies Guide to Fixing 'My Nook Won't Boot' (7) http://forum.xda-developers.com/showthread.php?t=949699&highlight=boot+zip
Steven676
CyanogenMod 11 Nightly Builds for Nook Color: [Read first three posts]: (8) [FONT=&quot]http://forum.xda-developers.com/showthread.php?t=2629337[/FONT]
surviveland
[Guide][Flash]How to play flash video on Android 4.4 Kitkat - xda-developers (14) http://forum.xda-developers.com/showthread.php?t=2548001
Tausaur
Dual Boot (12) http://forum.xda-developers.com/showthread.php?t=1275859
Tdm
CWM 6.0.4.7 Touch Recovery Ramdisk (http://forum.xda-developers.com/showpost.php?p=51446977&postcount=19015) http://forum.xda-developers.com/showpost.php?p=51446977&postcount=190

Customize Rom or Apps without being a developer - Xposed Framework
Customize Rom or Apps without being a developer - Xposed Framework
From Rovo89's thread
In this thread, I'm presenting a framework which gives you the possibility to modify your ROM - without modifying any APK (developers) or flashing (users)!
Click to expand...
Click to collapse
Get Xposed Framework and install instructions Click on "click to show content" box
For the framework:
Download the Xposed Installer APK and install it
Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"
Reboot
Done!l
You can verify this by starting the Xposed Installer again. If app_process jumped back to an older version (or none at all), you probably have a ROM with S-On or similar, which reverts any changes to /system after a reboot. Then you can try to flash this file: http://forum.xda-developers.com/show...postcount=2308
For any modules you want to install:
Download <module>.apk and install it
Launch the Xposed Installer and go to the "Modules" section (you will also get there if you click on the notification warning you that the module is not enabled yet)
Enable the module by checking the checkbox
Reboot
Done!
For information & help with Xposed Framework go to Rovo89's thread.
Once you have installed the Xposed Framework you can get many of the modules under the Download tab in the framework app.
There are also a large number of modules at this thread made for module developers to list their work. If the Modules indicate they are made for a specific phone or tablet they may not work on others. If you try and it does not do what it says it will do, contact the module maker, not rovo89, unless it is his module, ie: "Make Play store show all apps" or just un-install the module. No guarantees they will help. Some only have one tablet and only develop for what they have.
A Short list of some of the things you can do using Xposed Framework and modules.
These do all work with CM11 current nightlies and CM 10.2 last nightly, 1/19/14
For more info on Modules listed install Xposed Framework and click on Download tab​
Change color of status bar / notification bar. Xposed Framework - X Blast tools. Plus lot more. By femblack.
Network Speed Indicator - by fatminmin. With 123 below the up down speed can be shown in two readable rows. ** This will not work with CM10.2 Stable with the 3.0.8 Kernel or the updated hack fix kernel
Play Store link in app info - by qwerty12 - Does what the title says
App settings - by Tungstwenty & Rovo89 - What it is: This is an Xposed module that allows changing generic settings on a per-app basis. "Generic settings" means settings that are global to all applications, such as: perceived DPI, rotation behavior, fullscreen, etc..
Play Store Fixes - Rovo89 - Make play store show all apps
Enable SwiftKey predictions in more places - by qwerty12 - Email address website and filter list fields.
123 Dimension Editor. - by Hamzahrmalik - Change various UI dimensions: Status bar height, Navigation bar height and others. I doubled the height of my status bar and shrunk my navigation bar.
Cool Tool: - by Deviant Studio Software - Monitor various system info in floating window or in Status Bar. I have time, day, date, Free Memory and Battery Temp in two rows of my status bar.
Status bar volume. - by Niko001 - Move the volume bar over the status bar.
I do like things my way. That is what Android is noted for.​
This Module "Workaround for Netflix on CM10/CM10.1" works on most any CM10 thru 10.2 Rom.
From Kaepernick's post.
"Well, thanks to Entropy512's help, I was able to modify his Xposed hack to work on CM10 (based on Android 4.1) and CM10.1 (based on Android 4.2) for the Incredible. Using the newest Netflix app and it's working well without issue.
Click to expand...
Click to collapse
Get it here.
*** Make the Xposed Framework persist through a CM ROM update with script "90-xposedpersist.sh" (in the 90-xposedpersist.zip), put the ".sh" file in the /system/addon.d/ folder. Available here See Post #4 there for specifics here***
Image 1. Cyan status bar & navigation bar, network speed indicator & X blast options.
Image 2. Play Store button in app info.
Image 3. App Settings screen.
Image 4. Home screen with dual line expanded status bar, Cool tool info and Net work speed.

Run CM10 & 11 smoother and get more free memory
Tips to help CM10 and CM11 run smoother, less laggy, etc.,
and have more free memory on your Nook Color
and maybe even a little longer battery life.
These are a collection of tips that have been collected from various post in XDA, personal sharing with others, and as a result of my own desire to try to improve things where I can. I have tried everything listed here and each adds a little to smoothness(s), free memory(f) or battery(b) life. My CM11 flashed Nook runs quite smoothly, with free memory at desktop running from 110 to 160 Mb and six to eight hours of battery life depending on type of constant use. This is on a nearly three year old tablet. I have partitions set to 5Gb data and 1Gb media. All apps are in the tablet. I also have a 32Gb Sdcard. I also have over 220 apps including system apps. I use my tablet from 6-8 hours or more a day.​
Unless noted all apps mentioned are available through Google Play. I recommend the apps, etc., because they work for me. I get nothing out of it except the joy of helping others. Like everything try at your own risk. This includes app I have on my Nooks. If you have other programs you can try adjusting them as I have and see how it helps, or not. Trying and finding out what does and doesn't work is half the fun.
Free and simple​
On all CM10 and CM11: (s) Try lowering your maximum clock speed to 1000, or even 800mhz in System, Performance Processor, Maximum CPU frequency. Many have reported improved smoothness at slower speeds. Faster can run ahead of itself and actually make things jittery. Make sure to check Set on boot to retain settings.
CM11: Use 5/17+ nightly.
On all: System Settings ( some may only apply to CM10 or 11 List:
Wifi, advanced,Uncheck Network Notification (b)
Keep Wifi on during Sleep, only when plugged in (b)
Scanning always available, uncheck (b)
Wifi Optimization, checked (b)​Sound,Set quiet hours (your sleep time)(b)
Touch sounds, screen lock sound, volume adjustment sound and Charging Sounds, Enable, all unchecked (b)​DisplaySleep (set time for max time you want screen to stay on before going to sleep, shorter time saves more battery)(b)​Developer Options,Kill app back button, checked, (Allows you to kill kill app by long pressing back button)(b)​Performance,CPU governor, (Lower on list will give faster response but use more battery, Default is "ondemand". Try the others and stick with what suits you the best.) Make sure to check Set on boot to retain settings.​If you haven't activated the "Developer Options list":In "About Tablet, Build Number, tap ten times till it states "Developer Options turn on."​
AdFree: (b) Available on Slideme.com Stops adds in browsers and most all App with add banners. Saves time by not downloading the adds.
On All: ((f,b) Freeze / Disable unused (unusable) apps in System.(b,s,f)
Don't delete them since any ROM update you install will replace them, freezing / disabling them will last through an update. The stock App manager allows you to disable most of these. Titanium Backup and Rom Toolbox Pro can freeze more but do cost, though I think they are well worth the price for what they deliver. There are some free "App freezer" programs available. I've only tried Chef's App Freezer, check the ratings and comments.Android Keyboard (ASOP) - I use Swiftkey (lite is available)
Camera - (No camera in Nook, no need of file)
Com.android.smspush. No phone text.
Gmail and / or Email and Email Services (if you use another E-mail client, ie:K9)
File Manager ( if you uses another ie Root Exporer (Speedsoft) or Root Browser (Jrummy))
Google search - Definately slo-o-ows things down
Key Chain - if you don't use lock screen
Mobile Data and Mobile Network Configuration - No phone, no need
One time Init - only used on first install once
Picasa uploader - If you don't use Picasa
Print Spooler - If you don't use it.
Sound Recorder - No Microphone, no need
Sound Search for Google Play - If you don't use it
Talk back - If you don't use or need it.
Trebuchet - If you use another Launcher.
Voice+ - No Microphone or phone, no need.
If you use a different clock than stock, calendar etc you can freeze / disable the stock version. Example: I use Dejaoffice to link with Outlook on my PC so I freeze Calendar storage, calendar, and calendar sync.​
Change app permissions: (f,b) (for apps that run at startup and then stay in memory even when you not running them.)
I use App settings, it requires Xposed Framework to run but once set up does it's thing in startup, changes permissions, and closes. To get the Xposed Framework go here.
The most common causes of this problem are the following permissions: receive boot completed, vibrate, and wake lock. Not all apps can have these turned of. App settings has the ability to launch the program from is menu. Try turning off a permission, save, menu (launch). If it works great, if not go back and turn that permission back on.
The following is a list of Apps I changed permissions on and which permissions I disabled to keep them from persisting / sticking in memory:Advanced Task Manager: receive boot completed, and wake lock.
Alarm Clock Extreme: read phone state, receive boot completed, vibrate, and wake lock.
BusyBox Installer: receive boot completed, and wake lock.
CPU Master Pro: receive boot completed.
Crackle: receive boot completed, vibrate.
DejaOffice: vibrate.
Elixer: vibrate, and wake lock.
Evernote: receive boot completed, and wake lock.
Google Play Services: receive boot completed, and wake lock.
Kyo-Tux Aeon HD: vibrate.
News and Weather: receive boot completed, and wake lock.
Nook: receive boot completed, vibrate, and wake lock.
Pandora: receive boot completed.
RoboForm: receive boot completed
ROM Manager: receive boot completed, and wake lock.
The Weather Channel: receive boot completed, vibrate.
Titanium Backup: receive boot completed, vibrate.
Winamp: vibrate.
YouTube: receive boot completed, vibrate.​​
Advanced Task Manager: (b,f,s) Put the widget in dock, set your ignore list in app. One press and all unwanted apps go bye-bye.
My Ignore List:
Adfree, Elixer Widget, Alarm Clock Extreme, K-9 mail, Nova Launcher, Swiftkey, Speaker Boost, Pie Pro, Earthquakes, AFWall+, Clipper+, DejaOffice, Tasker, 360 Security.
Not so Simple but worth the time, still free​
Replace DSPManager with Speaker Boost: (f,b) Get more volume and save EMMC memory.(DSPManager 18Mg - Speaker Boost 1.7 Mg=16.3Mg saved) Get more info here.
Replace Trebuchet with Nova Launcher: (s) does more, has more adjustments. (Does take more memory but pays back in smoothness)
LagFix (fstrim) Free. (s) Use two to three times a week. (s,b)
Use Elixer widget to replace other widgets: (f,b) and save Memory 45 meg (for Battery widget, Wifi state and stats widget, free memory and CPU stats) - 12 Meg for Elixer = 33 Emmc memory saved.
Rom toolbox lite: Settings: (f,b,s) (some of these may need Pro)
Under performance.Settings, Main Preferences, Boot Delay, 40 seconds.
Task Manager, Tap on Task Manager on top left of screen.You can change the Minfree memory settings, with CM10 I found strict to work the best. So far with CM 11 custom settings of 30 FA, 40 VA, 65 SS, 75 HA, 90 CP, and 100 EA setting works well.) I set them then save them into custom settings). Make sure to update to 5/17 nightly.
Start up killer, add Elixer, Google play services, The Weather Channel, and YouTube. (keep them out of active (service) memory or minimize there active size.)
Ignore List. 360 security (or your antivirus app), AdFree, AFWall+, Android system, Clipper+, Earthquakes, Elixer Widget, K-9 Mail, Mobile Data, Nova Launcher, Pie Pro, Rom Toolbox Pro, Speaker Boost, System UI, Tasker.​SD Boost. You can change the size of the cache to both internal and external SDcard. I find with my class 4 Sandisk SDcard a setting of 4096KB works best. A benchmark is available to test your settings. If you have a faster card ie: Class 10 you can try larger cache sizes and save as custom. ​
Not Free but worth it (IMHO)​
Upgrade to Nova launcher Prime:
In Nova Settings: (s)
Look and Feel, Scroll and Animation speeds (faster than light) (s)
New Apps - check Auto Add Short cuts, (make sure to turn off auto add in Google Play.)
Labs - Check the following, Big Grid size options, Widget Image Async List, Widget Image Cache, Restore Widgets Faster. (s) ​
Upgrade to Rom Toolbox Pro, LagFix (fstrim) Premium (scheduling trims): Get more bells and whistles and help support the developers.
Upgrade to 32 or 64Gb Class 10 SD card - Buy a 32Gb Class 10 SD card, about $20.00 + ship, prepare as usual and you'll cut your access time to the SD card buy about half. I can do a 2Gb recovery backup in about 5 and 1/2 min. With my Class 4 it takes just shy of 11 minutes.
More Memory Buy a Sandisk 64 Gb Class 10 Micro SD card, about 40.00 + ship, and partition the whole card as one Primary partition, format as FAT32, Sectors/ cluster 32 (16384 bytes) using "MiniTool Partition Wizard Home Edition" available for free here. I have donated to MiniTool since I use it for all kinds of partitioning,(resizing, moving, copy, etc.), on PC's and all kinds of flash memory. I started with the partition set to 30,451.33, copied my data from my 32G sdcard. It worked great and with SD boost set to 4096 all SD access was noticeably faster. So I used Partition Wizard to resize the card to the full capacity, the program changed the size and copied all the files in about 20 minutes. Plugged it into the Nook Color and went from 17 GB free to 47 Gb Free. It is a bit slower than the 32Gb & and the bootloader doesn't list CWM or TWRP recovery kernel or ram on the SD, but oh the storage. I can put over 40, 2 hr AVI or MPEG movies on the card and still have better than 20Gb free.
If you have other Apps, tricks, tweaks that you have tried and found to help. Please reply and I will try them out and list them if they do add to the smoother, longer, freer Nook.​

Netflix on CM11 on SD
Good source of info. Thanks! Confirming that latest Netflix is working on SD. See that thread

If you use Speaker Boost try this to save memory.
Ever since CM7 and Nook Color Tweaks, in has been necessary to find a way to boost the sound output of our little wonder tablet. I tried several an ended up using Speaker Boost. I have found that I no longer need to use DSPmanager. The problem is that freezing or disabling the app doesn't keep it from installing in memory and using 18meg of precious RAM. Renaming the file with.bak extension or deleting it works after a reboot but, if you like to keep up with the nightlies like I do it is re-installed with every update. It gets to be a pain using a file manager to do this every day. So let your Nook do the repetitive work.
So I have worked up three quick and easy ways to rename the file.The best and easiest is the last.
1. Is a Tasker task. This was the first one I used and I setup a widget so I. Can rename with one tap. The.xml file can be imported as a task into Tasker.
2. Is an apk made from the Tasker task. It works the same way just doesn't need Tasker to work.
3. A script file that can run at every boot, check if DSPManager.apk exists, and rename it. This eliminates having to rename it and reboot after every ROM update as it is renamed before the app is loaded. It is only 279 bytes and is the only file that has to remain to work. In the 90RnamDSP scripts.zip below are three files. One that goes into userinit.d folder, an instruction.txt file and an installation script that sets everything in place just by running it.
I want to thank LeapinLar for the help he gave debugging the rename script. This was my first script and had to get everything in proper order and get the syntax correct. What I learned help me build and debug the installation script in a few hours.
Download, unzip, import, install, etc, and enjoy.

Thanks, nice job
Might check the links for the 6.x recovery threads

webyrd said:
Thanks, nice job
Might check the links for the 6.x recovery threads
Click to expand...
Click to collapse
Checked and corrected, Thanks.

pastordl... check pm about a couple of link issues

DizzyDen said:
pastordl... check pm about a couple of link issues
Click to expand...
Click to collapse
Thanks, guess we know where the missing link is.

problem with latest YouTube and Google Play apps not working
For problem with latest YouTube and Google Play apps not working, Go here:
http://forum.xda-developers.com/showpost.php?p=60241045&postcount=54

[ROM] CM 12.x (Android 5.x) for moto_msm8960 A-family KKBL/JBBL

Thread created by hbenz2008 but now maintained by me CWGSM3VO:
Requirements:
- Unlocked JBBL/KKBL bootloader. Builds are bootloader specific.
- Updated KKBL recovery, can find one here: https://twitter.com/dhacker29/status/583847256589213696
- Updated JBBL recovery, can find one here: http://downloads.blissroms.com/Recovery/Recovery/moto_msm8960_jbbl/
Builds can be downloaded from:
- CMxlog: http://www.cmxlog.com/12.1 and choose your device.
- CyanogenMod: http://download.cyanogenmod.org/ and choose your device.
GApps:
- DHacker gapps:
4-25-2015: https://www.androidfilehost.com/?fid=96042739161893996
6-07-2015: https://www.androidfilehost.com/?fid=24052804347756927
- Delta gapps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
What works:
- Phone
- WiFi
- GPS
- SMS/MMS
- Mobile Data
- Camera/Camcorder
- HDMI
- Bluetooth
- Call Recording
- Tethering (WiFi: Yes / USB: Yes / BT: Yes)
- USB storage
- F2FS for /data, /data/media and /cache (recovery/kernel dependant)
Known issues:
- The "calc bug". This affects some users. This is due to the GPU crashing. A fix may be hard to nail down. Workaround is to disable H/W layers + force GPU rendering via devopts.
- HDMI. Depends on TV. Works 100% on some, not others (in my testing) -- statusbar/navbar is visible and small scaling issue (statusbar cut off somewhat). Reported not working on AHD.
- Bluetooth; some reported issues with different car makes/models. For me personally, it's worked with a variety of headsets and devices (decks, etc). Tethering appears to work for me, some reports of issues. Issues reported with wearables being paired and WiFi not working or requiring BT to be activated after WiFi connected.
- MMS; most issues can be tracked to incorrect APN settings, please verify with your provider (or try searching this or CM11 threads)
- WiFi; some users have reported issues connecting to certain brands of APs and/or band-mode; most reports isolated to security protocol being used (WPA vs WPA2)
- Clock resets to 1970. Thanks to @MaicolS for using this solution successfully: http://forums.androidcentral.com/an...-update-can-t-connect-google.html#post4323256
- Snapchat crashes sending video. @VlitalityX found this solution: Developer Options->Drawing->Turn on "Force RTL layout direction" then turn it off.
- Alarms not firing or repeating. Disable Automatic Network Date & Time in Settings->Date & Time. Appears to be an issue with RTC writes and/or QCom time_daemon.
- Some reports of GPS not working, try this fix: http://forum.xda-developers.com/showpost.php?p=56659808&postcount=5264
Reporting issues:
- Please ensure your signature includes device, rom, etc to help if posting in the thread.
- Provide a logcat capture if possible, otherwise enable aplogd.
- Enable aplogd, see here: http://forum.xda-developers.com/showpost.php?p=59620294&postcount=2327 and provide logs. You can safely leave this enabled.
- Open a JIRA bug report, see here: https://jira.cyanogenmod.org and provide logs.
Notes:
- There are unofficial builds provided in this thread and should not be used when filing reports with JIRA.
- When coming from another ROM (non-CM) a clean-wipe is recommended (backup your data + internal sdcard data)
- Some users have had issues clean installing CM12.1 - one workaround known is to install CM11 first then upgrade to CM12.1
- The Xposed framework is not supported. Please uninstall/remove it and any modules before reporting issues.
Tips:
- I use TWRP
- I use DHacker's GApps package and let Google via my account update everything as need be.
- For me, a "clean wipe" is formatting the following: /system, /cache, /data and /data/media. Backup anything of value from /data and /data/media before doing this. Flash ROM, flash GApps, reboot. Authorize your PC USB connection on the phone after enabling Developer Options and test adb from the Android SDK.
- When performing a "dirty flash" (upgrade) I manually wipe /cache and dalvik-cache before rebooting to UI.
- For KKBL to JBBL issues with downgrading, see this: http://forum.xda-developers.com/showpost.php?p=63091712&postcount=4465 and this: http://forum.xda-developers.com/showpost.php?p=56963255&postcount=702
- Drained to 1% battery and boot-looping? Try this: http://forum.xda-developers.com/showpost.php?p=61728073&postcount=3754
- If your CM build is 1+ month older than what you plan to flash/upgrade, it is recommended you do a clean flash.

So far, I had some issues with network, apparently it's losing WiFi connection randomly . The Play Store takes a long time to download or update apps or get "Retry" messages.

None of those issues here,however i had some unfortunately dialer stopped,it corrected itself after couple reboots.
Downloaded es file explorer as fx explorer couldn't get into System files.
GPS still hosed in my case

I forgot to mention: during the flashing, a mount error appear, but the ROM booted, normally. Happened to you to?

No but flashing was really quick I was surprised.under a min maybe then it took bout 5 min to reboot.but no errors

Hummmm, strange... What recovery are you using? I flashed dHacker's one, before flashing the ROM.
And something happened just now: I rebooted the phone and the DPI as changed! All the things are smaller now. Weird...

Most likely need to reflash.using twrp 7.1 and flashed dhacker gapps.
note: cant write to System file yet

I know this is for KKBL, but can this be built for JBBL? How is the overall feel of the build anyways?
Sent from my ATRIX HD using XDA Free mobile app

douglasvbarone said:
I forgot to mention: during the flashing, a mount error appear, but the ROM booted, normally. Happened to you to?
Click to expand...
Click to collapse
FYI he said SD card doesnt work yet

doesnt work in what capacity?

lngwca said:
FYI he said SD card doesnt work yet
Click to expand...
Click to collapse
Well, that kills it for me then. Will have to wait. I have all my music and photos on my SD card.

doing a nandroid backup now, but photos in SD can be seen .Once done, i will test music...
Anyone can post a gps.conf from a working gps whether it be jelly bean or kitkat.
... will be appreciated. Under System/etc
very smal file 2kb or so

both music and photos in SD can be manipulated just fine
iBolski said:
Well, that kills it for me then. Will have to wait. I have all my music and photos on my SD card.
Click to expand...
Click to collapse
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.

hbenz2008 said:
both music and photos in SD can be manipulated just fine
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
Click to expand...
Click to collapse
Ahh, gotcha. I thought there was NO access to the SD card. So, it's just write access. I know under Lollipop, they were supposed to make it work better than they did under KK. Supposedly, it's a setting where you can say give it all access or only to it's own directories. Supposedly though, many apps might have to be rewritten to get this, so if the app hasn't been updated to ask for the new permission, then it won't work.

lngwca said:
FYI he said SD card doesnt work yet
Click to expand...
Click to collapse
The tweet:
Everything except SD YouTube video seems to work on RAZR HD
Click to expand...
Click to collapse
Has nothing to do with SD card, it means SD YouTube videos (SD - Standard Definition, as opposed to HD - High Definition).

his tweet said "Everything except SD YouTube video seems to work on RAZR HD "
so sd as in resolution. i asked him if he could try viralpopup or tubemate. might try this on the weekend to see how this feels.
oh and can someone upload a mirror pls? page won't load 2 download.
ps it's a cm12 port not AOSP too from his threads on twitter

absolutely true, the challenge for now is to gain access to editing system file.
kabaldan said:
The tweet:
Has nothing to do with SD card, it means SD YouTube videos (SD - Standard Definition, as opposed to HD - High Definition).
Click to expand...
Click to collapse

hbenz2008 said:
both music and photos in SD can be manipulated just fine
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
Click to expand...
Click to collapse
try root explorer to edit system files
http://www.reddit.com/r/Android/comments/2m7fqo/i_wanted_to_keep_a_chart_going_of_apps_we_know/
check play store if you bought/have titanium backup
they pushed an update for support. now if only they updated their UI....

confirmed, works-root explorer-

my bad... just thought that he missed a comma. lol also every ones sd wasnt mounting

MIUI 9 systemless magisk, xposed possible?

Dear fellow mixers,
I try to achieve the combination of:
MIUI 9 Android 7.0 either from EpicROM or xiaomi.eu
Installing Magisk systemless root
Installing Xposed for magisk
3 Questions:
Anyone achieved this already? If yes, can you tell us which version/release of MIUI, which variant of Magisk & Exposed did you use?
If someone didn't do it, but knows which combination of MIUI, Magisk and Xposed (especially which versions and mods) should work in theory, can you say so?
To my understanding this should help to *not* trip safetynet and allow us to run Snapchat?
My research so far:
According to this post, Unofficial Xposed 88.1 for MIUI9 SDK24 should work
According to this post, 88.1 works and xmiui also has a magisk zip
Another guide that seems to be written before 88.1 was released with MIUI 9 compatibility. So I'm confused which guide to follow, which combination of systemless xposed/magisk will work?
Edit:
I'll use my experiences and document them here to later create another how-to for systemless magisk/xposed on miui9 and another guide how to properly backup second space apps.
Second space backup:
Using Titanium Backup installed and started in First Space will only backup first space apps. Installing Titanium Backup in Second space also didn't work properly for me for some apps like LINE messenger.
Actually there are two (somethimes three) places that need to be backed up:
1. App APK (the installation files itself)
/data/app/<appname>
for both spaces, because they use the same app installation, as no user data is saved here, so it's in a single location, no matter how many android user accounts or MIUI spaces you have.
2. App's user data (like LINE Messenger database etc. normally not visible to you but important):
First space: /data/user/0/<appname>
Second space: /data/user/10/<appname>
This is unique for every user account (or miui space), here individual data is being saved, like two different LINE messenger accounts, or FB accounts.
3. User's accessible app data (where your app stores things that you produce in your apps and are visible to you when connecting your phone to your PC or checking your sdcard/internal storage):
First Space: /storage/emulated/0/<folder>
Second Space: /storage/emulated/10/<folder>
the folder names can be a mess here, whatsapp names their user data folder simply Whatsapp. Here they store your chat history DB, your downloaded pictures, videos and audio. Other apps can basically name their folder however they want and sometimes it's difficult to find out what folder your app stores files in. The app "Magix Pro Screen Recorder" as a fictional example could store your screen recordings in /storage/emulated/0/Movies/recordings/
To properly backup whatsapp in second space:
copy /storage/emulated/10/whatsapp folder to your PC
in new rom/phone create second space, then copy the backup form your PC to the same location as above in your new rom/phone
install whatsapp from play store, open it and it should recognize the backup and ask you to directly restore it
To properly backup a more complex app that uses all three folder types described above I take Naver LINE Messenger as an example:
backup /data/user/10/jp.naver.line.android/ *
backup /data/app/jp.naver.line.android-1 *
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install terminal emulator and delete the previous LINE settings by using the following commands:
su
sqlite3
/data/user/10/jp.naver.line.android/databases/naver_line
delete from setting;
.quit
if you don't have the sqlite3 binary, you can try to find it online for android (arm64 binary), paste it to your /bin folder and try again, or open the file on your computer with an sqlite explorer
if available, delete the following xml:
/data/user/10/jp.naver.line.android/shared_prefs/jp.naver.line.android.settings.xml
open the Line app and it will ask you to enter your user and password
Alternative method:
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
use an sqlite editor on your phone or on your pc to empty the following database:
/data/user/10/jp.naver.line.android/databases/naver_line
start line
My preferred method:
on old phone, install device id changer pro in second space and open it
note down device ID
backup /data/user/10/jp.naver.line.android/
backup /data/app/jp.naver.line.android-1
in new rom/phone create second space, then copy the backups to the same locations as above
don't open line app yet
install device id changer pro in second space and open it
enter the previously noted down device ID and set it
start line
* creating proper backups of the two LINE folders is a whole procedure again, we need to use tar gz to preserve permissions when copying and pasting:
- enable developer mode and usb debugging
- connect to pc
- install minimal adb & fastboot on your PC
- start cmd, execute:
adb shell
- accept popup on device, then type into cmd:
su
- accept supersu on device
- type:
cd /data/user/10/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-10-jp.naver.line.android.tar.gz .
cd /data/user/0/jp.naver.line.android
tar -cvpzf /storage/emulated/0/user-0-jp.naver.line.android.tar.gz .
cd /data/app/jp.naver.line.android-1
tar -cvpzf /storage/emulated/0/app-jp.naver.line.android-1.tar.gz .
- copy the 3 backup tar.gz files into your first space internal storage, and type:
cd /storage/emulated/0/
tar xpvzf user-10-jp.naver.line.android.tar.gz /data/user/10/
tar xpvzf user-0-jp.naver.line.android.tar.gz /data/user/0/
tar xpvzf app-jp.naver.line.android-1.tar.gz /data/app/

Reported Psyman version seems work and sometimes... latest build officialy released by Rovo works... then u need made a backup and try to flash a magisk version, lastest will have more chance to work because include all report from git...
And a lot of xposed module need to be updated....
cheers

I wasn't unable to make xposed 88.0 or 88.1 to work with the latest N MIUI 9 Epic rom using magisk. the only version that worked for me was V87 xposed but somehow gravity box didn't seen to work well when enabling setting and applying theme, that is gravity older version not the newest the newest version require xposed 88 and newer which didn't activated on N MIUI 9 Epic newest rom, exMIUI did work though

Ok, some news...
Lastest stable from Xiaomi.eu (9.1 - 7.0 - SDK 24) works with magisk and xposed... only need good version and right apk...
Cheers

[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!

Magisk Module Systemless Debloater

Magisk Module Systemless Debloater
Download:
GitHub - zgfg/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
GitHub - Magisk-Modules-Alt-Repo/SystemlessDebloater: Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP
Select and systemlessly debloat preinstalled system apps. Supporting up to System As Root (SAR), Dynamic partitions and Android 13. Module must be installed through Magisk app, not TWRP - GitHub - ...
github.com
Wiki pages by @ipdev:
ConfigScript
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
with his examples of apps that can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
CommunityList
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
*** Yet another System(less) debloater, how and why?
- Systemless means that all changes made are active only when Magisk is loaded and module is enabled.
For OTA or anything, just disable the module (or boot without Magisk) and your system partitions are no more affected
- For Android up to 9 and/or 10 (depending on devices), system partitions were read-write, hence hard-debloating by use of eg TWRP, Titanium, etc (to delete the pre-installed system apps) was possible
This is no more possible for the phones released with Android 10 and higher.
System (System As Root, Dynamical partitions) becomes read-only on the file-system level and stock apps could be debloated (the same holds for any changes on the system partitions) only by the systemless approach - by use of Magisk to dynamically overlay the required changes at boot time
Hence, this module also uses the Magisk REPLACE mechanism and dynamical mounting through the module's service.sh script
- The module debloates only (stock) apps pre-installed to the system partitions, traditionally named as /system, /system-ext, /product, /vendor and /apex; plus additionally on A12 and A13 devices, variably named system partitions like /india, /my_bigball, etc
Hence sorry, to debloat user apps installed to /data, please use the other methods (first of all, just simply uninstall them or at least uninstall their updates)
- Originally I started development with Xiaomi Mi 9T (MIUI 10-12.5, Android 10-12) and later continued with Xiaomi 11 Lite 5G NE (MIUI 12-13, Android 11-12). However, the module relies on the common Magisk overlay mechanism and the list of apps to be 'debloated' is configurable hence there are many users who successfully use this module on the various other devices (like Pixel, Samsung, One Plus, etc.), with the stock or custom ROMs, and with up to Android 13
- Original, default list coming when the module is installed will be empty - user must define then himself which apps should be debloated, depending on his device, ROM and preferences
To (re)configure the list of apps for debloating, simply edit the (textual) /Download/SystemlessDebloater.cfg config file on Internal memory.
Module automatically installs the config file with instructions inside but with the empty list
(Re)configure your list of system apps you want to debloat, reinstall the module (always through the Magisk Manager, not TWRP) and reboot - to take your changes in effect
You only need to provide the proper names (not package names) for the preinstalled system apps, the module will find their exact System paths
- However, the user bears the risks and responsibility himself (device may no more boot when certain system apps are removed/debloated) but the Troubleshooting section below provides instructions how to recover, even from the bootloop cases
Nevertheless, whenever you want to 'debloat' some service or app you are not familiar with, please google first to find what that app is really about and is it generally safe to be debloated (on your but also on the other phones and even by other methods, it doesn't matter)
Don't be afraid of the module and debloating, but be cautious what are you going to debloat
*** Installation
- Download the latest module from GitHub - scroll down, open Assets and find the latest v1.5.3 zip:
https://github.com/zgfg/SystemlessDebloater/releases/tag/153
- In Magisk app (manage), open Modules tab and take Install from storage, navigate to the downloaded SystemlessDebloater.zip (as is, do not unzip)
Read what Magisk prints while installing and find the module's log in /Download/SystemlessDebloater.log file on Internal memory
To finish the installation (it applies to all Magisk modules), reboot the phone
- First time the module will not debloat anything - it will just create the input/config file /Download/SystemlessDebloater.cfg on Internal memory
Open that config file, read the instructions in the file and fill your own list of app names for debloating - look at the commented examples you will find in that config file
- Save the config file, reinstall the module and reboot.
Inspect the log and consult the Troubleshooting section below if needed
- To find what system apps you have on your phone and what are their exact names, scroll down through the SystemlessDebloater.log to the "System apps, not debloated" section
Find e.g. a line:
/system/app/Email (com.android.email)
Then copy/add just the Email name (supposed that you want to debloat the built-in Email app) into the SystemlessDebloater.cfg config file
Repeat for the other apps you want to debloat. Then reinstall the module (only on the reinstallation, module processes the config file) and reboot
Fine tune your list of apps for debloating but every time reinstall the module and reboot
- Last but not the least: Once debloated, apps can no more be found (until you reconfigure, disable or uninstall the debloater) under the Settings / Apps
Hence, if you want to delete their cache or data, do Clear cache/data before debloating the apps
Moreover, before trying to debloat any app, look first if you could simply Uninstall that app (ie, if it was a user and not the system app) from Settings / Apps
If Uninstall is not available for that app, try to Uninstall updates: updates are also installed to Data while SystemlessDebloater 'debloats' only from the System - hence the app's update on Data may still remain there
*** Troubleshooting
- What if I eg have configured the app EMail to debloat, but the app is still present?
Check if you have missed to perform Uninstall / Uninstall updates from Settings, Apps - perform, reboot and test again
Check if you have miss-spelled the application name - correct in the config file SystemlessDebloater.cfg, save, reinstall the module and reboot
App names are cases sensitive - eg, the correct name might be Email, not EMail
- To help yourself, use eg Package Manager app (from Playstore) where you can search for all the apps/services, find their exact names and installation paths (to see are them System or User apps)
- What if I change my mind and I want to un-debloat and use Email, but to debloat now eg, Chrome browser?
No problem, reconfigure the list in SystemlessDebloater.cfg, save, reinstall the module and reboot
- What if after a week or so, I realize that some functionalities on the phone were affected?
Sorry, you had decided to debloat the 'wrong' apps/services
Google about which app(s) are safe to debloat or not, reconfigure your list in the config file, reinstall the module and reboot
Or disable the module and reboot, to figure out was the problem really due to debloating
- Oops, what if I have a bootloop (phone does no more boot since the 'wrong' apps were debloated)?
If you have TWRP with the read/write access to Data, navigate to /data/adb/modules/SystemlessDebloater and by using Advanced / File explorer from TWRP, create a dummy file named disable (without extension) in that folder
Reboot and Magisk will boot but with the debloater disabled - hence, all the previously debloated apps will be un-debloated now (to see if debloating was really responsible for the bootloop)
Instead of dummy file named disable, put the remove dummy file to trigger Magisk to uninstall that module on the next reboot (all that applies to any module possibly causing your bootloops)
If the proper TWRP is not available for your device and ROM, boot to the Android Safe Mode - google for a key-combo to boot in, for my Xiaomi it takes (re)booting with Vol+ and Vol+ pressed simultaneously
Don't do anything in Android Safe mode but reboot then to 'normal' mode - Magisk will boot now with all the modules disabled (this method does not work for Magisk v20.4 or earlier)
You will have to re-enable MagiskHide/DenyList (don't worry, your list of apps to hide the Magisk from was not lost), re-enable the other modules, correct SystemlessDebloater.cfg, reinstall debloater and reboot
There is also a third method (adb wait-for-device shell magisk --remove-modules), but search yourself and read about from the Wiki Documentation on the Magisk GitHub page
*** Enough for the theory, install now and practice debloating

IMPORTANT
Since the version v1.5.1, SystemlessDebloater module supports a new SystemlessDebloater.cfg config file - thanks to @ipdev
Update will create the new config file and transfer your DebloatList
Please delete then your old SystemlessDebloaterList.sh input file and read and use the new config file instead
---
For more info about the SystemlessDebloater.cfg config file, please see: Wiki pages from @ipdev:
ConfigScript
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com
and his examples what apps can be debloated (Android, Google, Oppo, Samsung, Xiaomi, LineageOS):
CommunityList
Guide for the Systemless Debloater Module. Contribute to mModule/guide_sDebloater development by creating an account on GitHub.
github.com

On my Xiaomi Mi 9T, eea Stable QFJEUXM 12.0.2 I safely debloat the following apps:
Code:
DebloatList="
AnalyticsCore
AntHalService
BasicDreams
BookmarkProvider
CatchLog
Chrome
CneApp
EasterEgg
facebook-appmanager
facebook-installer
facebook-services
FileExplorer_old
GlobalFashiongallery
GlobalMinusScreen
Gmail2
GoogleFeedback
GooglePartnerSetup
HybridAccessory
HybridPlatform
IdMipay
InMipay
Joyose
MiBrowserGlobal
MiBrowserGlobalVendor
MiCreditInStub
MiDrop
MiLinkService2
MiPicks
MiPlayClient
MiRcs
MiRecycle
MiService
MiuiBrowserGlobal
MiuiBugReport
MiuiDaemon
MSA-Global
Netflix_activation
Notes
PartnerBookmarksProvider
PaymentService
PhotoTable
Stk
TouchAssistant
Traceur
Turbo
uceShimService
Velvet
VsimCore
wps_lite
YellowPage
Zman"
E.g., I debloat YouTube and install Vanced YT root.
Similarly, I debloat GMail, Wellbeing, Netflix, Facebook, Turbo, etc - inspect and exclude from the list those apps you want to keep
Also, DebloatList I used for Mi 9T but Xiaomi.eu weekly 20.9.17 (MIUI 12, Android 10):
Code:
DebloatList="
AndroidAutoStub
AntHalService
BookmarkProvider
Browser
BTProductionLineTool
Calculator
CatchLog
CneApp
EasterEgg
Email
GoogleFeedback
GooglePartnerSetup
Health
Joyose
Lens
MiMover
MiPlayClient
MiRecycle
MiService
MiuiBugReport
MiuiDaemon
Notes
PaymentService
Stk
TouchAssistant
Traceur
uceShimService
Velvet
VsimCore
WebViewGoogle
wps_lite"
and for Xiaomi.eu Stable 12.0.6:
Code:
DebloatList="
AndroidAutoStub
AntHalService
BookmarkProvider
Browser
BTProductionLineTool
Calculator
CatchLog
CneApp
EasterEgg
Email
GoogleFeedback
GooglePartnerSetup
Health
Joyose
Lens
MiMover
MiPlayClient
MiRecycle
MiService
MiuiBugReport
MiuiDaemon
Notes
PaymentService
Stk
TouchAssistant
Traceur
uceShimService
Velvet
VsimCore
WebViewGoogle
wps-lite"
You may exclude e.g., Calculator,Email, Health or Lens, if you want to use them.
You can expect most of these apps also on the other MIUI firmwares. Installation folders on System may vary, but module will find their paths
EDIT:
SystemDebloaterList.sh and DebloatList were used in the module versions v1.5.0 and earlier, since v1.5.1 the module uses SystemDebloater.cfg

Thanks a lot to @ipdev for discussing and sharing ideas, encouraging and for successful testing on Xiaomi Poco F2 (debloater found most of the same MIUI apps as above) and OnePlus 5T
Also, thanks for your successful test on Pixel 3aXL with Android 11:
ipdev said:
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse

Reserved

Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
.​

HippoMan said:
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
.​
Click to expand...
Click to collapse
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Quick edit.
Since the back-side move for xda is still going, there are some errors while in transition.
Since attachment is not working at the moment. GoogleDrive - Link

ipdev said:
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
OxygenOS isn't as bad, bloat-wise, as some other OS's, such as what comes with Samsung. But there are still things that I don't want, such as the OnePlus camera and a few other items.
I'll report back here after I try this.
.​

ipdev said:
It does not matter if it system-as-root or a slot device.
By time modules are run, system paths are set.
The active slot partition is running, and (if needed) switch root has happened.
Root directory is set to / and system directory is set to /system
curious about OxygenOS, do not run it very much so I am not sure what should/could be removed.
Cheers.
PS.
Works on Pixel 3aXL. (Stock Android 11. Magisk canary.)
Attached the SystemlessDebloater.log from 3aXL.
And the SystemlessDebloaterList.sh I use for testing. (remove the .txt)
Click to expand...
Click to collapse
Thank you for testing on A11.
Log cannot be downloaded, 404?

zgfg said:
Thank you for testing on A11.
Log cannot be downloaded, 404?
Click to expand...
Click to collapse
Looks like some more hiccups on xda back-side again.
Will be nice once the transition is complete, xda will be fast and stable again. :fingers-crossed:
Updated my prior post with a gDrive Link.
If you look at the log, you will notice chrome is not debloated.
The stub is debloated, Chrome (Think it is in product/app) is a gzip version of the Chrome apk.
Chrome is automatically installed into /data/app/HashStringOrSomething/com.android.chrome-HashStringOrSomething/Chome.apk
I have not taken time to look into that change.
Cheers.

ipdev said:
Looks like some more hiccups on xda back-side again.
Will be nice once the transition is complete, xda will be fast and stable again. :fingers-crossed:
Updated my prior post with a gDrive Link.
If you look at the log, you will notice chrome is not debloated.
The stub is debloated, Chrome (Think it is in product/app) is a gzip version of the Chrome apk.
Chrome is automatically installed into /data/app/HashStringOrSomething/com.android.chrome-HashStringOrSomething/Chome.apk
I have not taken time to look into that change.
Cheers.
Click to expand...
Click to collapse
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
One more thing. I've found some people claiming that Chrome breaks to run if Playstore shows Device is not certified.
But back in the spring when Google started to play with enforcing CTS Profile Hardware attest, and prior than @Displax invented ro.product.model spoofing (to force Basic attest and to pass CTS/SafetyNet, to get Device certified), my CTS was failing and Device was not Certified but I had no problems using Chrome on daily basis
---
Also, you have PrebuiltGmail and Music2, I had Gmail2 and FileExplorer_old (I had to use Package Manager to find that Gmail was installed as Gmail2/Gmail2.apk and similarly the Android FileExplore as FileExplorer_old.apk)
Btw all Mi* and Miui* stuff apply only for debloating Xiaomi
In your input list you have lite and wps (both are not found in the log), mine was wps_lite (WPS preinstalled to Vendor) - please check

zgfg said:
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
One more thing. I've found some people claiming that Chrome breaks to run if Playstore shows Device is not certified.
But back in the spring when Google started to play with enforcing CTS Profile Hardware attest, and prior than @Displax invented ro.product.model spoofing (to force Basic attest and to pass CTS/SafetyNet, to get Device certified), my CTS was failing and Device was not Certified but I had no problems using Chrome on daily basis.
Click to expand...
Click to collapse
PlayStore issues are weird at best.
Hit or miss, depends on the device and/or setup.
Certificataion does not seem to play a big part over all.
If it does then Google's has more issues than fixing SafetyNet to worry about.
Sometimes it is just a Google being Google.
I will look into Chrome tomorrow.
I normally use Chrome Dev PlayStore - Link.
More so now, Brave Browser PlayStore - Link.
zgfg said:
Also, you have PrebuiltGmail and Music2, I had Gmail2 and FileExplorer_old (I had to use Package Manager to find that Gmail was installed as Gmail2/Gmail2.apk and similarly the Android FileExplore as FileExplorer_old.apk)
Btw all Mi* and Miui* stuff apply only for debloating Xiaomi
In your input list you have lite and wps (both are not found in the log), mine was wps_lite (WPS preinstalled to Vendor) - please check
Click to expand...
Click to collapse
No harm checking for apps that do not exist on the device.
It may cause extra lines in the log file and one or two seconds of install time.
My bad.
Must have split wps_lite when I was adjusting the list. Then when sorting, it just put lite and wps in the correct order.
---
I re-flashed and/or reverted a few phones tonight and added them to the gDrive Link.
The files listed as _pfile.list (preinstalle files) are a list of files located in app and/or priv-app of system, product and vendor.
I use a shell scripts for this kind of stuff, [ because I am lazy ] primarily with adb shell.
I adjusted the one I use to make the pfile list.
list_pfiles.sh - Still needs to be run as root.
list_pfiles.sh needs to be located in a writable directory. (sdcard/Download | data/local/tmp | ...)
It still uses a static NAME= variable that you will want to change.
I added a few things to make it run from a root file manager like fx or mix.
With the addition (work from a file manager app/or called from a diferent directory), if you rename the script file, you will also have to adjust the SCRIPT= variable to match.
Cheers.
Edit:
2021.Aug.21
I updated the list_pfiles script.
To Use:
Copy this script to the device.
Recommended to use the /sdcard/Download/ directory.
Run from adb shell (or a terminal app) using the sh command.
sh list_pfiles.sh
Run from a file manager that is able to execute a script file.
Note: May or may not work depending on file manager..

ipdev said:
PlayStore issues are weird at best.
Hit or miss, depends on the device and/or setup.
Certificataion does not seem to play a big part over all.
If it does then Google's has more issues than fixing SafetyNet to worry about.
Sometimes it is just a Google being Google.
I will look into Chrome tomorrow.
I normally use Chrome Dev PlayStore - Link.
More so now, Brave Browser PlayStore - Link.
No harm checking for apps that do not exist on the device.
It may cause extra lines in the log file and one or two seconds of install time.
My bad.
Must have split wps_lite when I was adjusting the list. Then when sorting, it just put lite and wps in the correct order.
---
I re-flashed and/or reverted a few phones tonight and added them to the gDrive Link.
The files listed as _pfile.list (preinstalle files) are a list of files located in app and/or priv-app of system, product and vendor.
I use a shell scripts for this kind of stuff, [ because I am lazy ] primarily with adb shell.
I adjusted the one I use to make the pfile list.
list_pfiles.sh - Still needs to be run as root.
list_pfiles.sh needs to be located in a writable directory. (sdcard/Download | data/local/tmp | ...)
It still uses a static NAME= variable that you will want to change.
I added a few things to make it run from a root file manager like fx or mix.
With the addition (work from a file manager app/or called from a diferent directory), if you rename the script file, you will also have to adjust the SCRIPT= variable to match.
Cheers.
Click to expand...
Click to collapse
Pixel comes with only G stuff but interestingly, without Wellbeing
Velvet.apk, what is the package name (you should still be able to find the name on /data/data)?
When you have Velvet (Poco F1, F2 and One+ 5T), do they also have Google.apk = com.google.android.googlequicksearchbox?
Btw, if you use MiXPlorer and choose Tools, App Remnants, you can see /data/data folders for debloated apps (and you can remove them)

HippoMan said:
Over the weekend when I have time to fix any potential bricking or boot loops, I'm going to try this on my A/B device (One Plus 7Pro, GM1917, OOS 10.3.5) ... unless before then anyone indicates that this is not even likely to work on my phone.
If I end up doing this, I'll report my results.
Click to expand...
Click to collapse
I did it just now, and it worked wth no problems on my device! For my initial test, I used SystemlessDebloater to remove GooglePartnerSetup, and it was indeed removed. No bootloops, no problems.
Good work on this module!
zgfg said:
...
Btw, if you use MiXPlorer and choose Tools, App Remnants, you can see /data/data folders for debloated apps (and you can remove them)
Click to expand...
Click to collapse
Well, in my case, GooglePartnerSetup doesn't appear anywhere among MiXPlorer's "App Remnants", even though other /data/data items are indeed being displayed there. But this is not causing any kind of issue on my device, so I am not concerned.
.​

zgfg said:
Pixel comes with only G stuff but interestingly, without Wellbeing
Click to expand...
Click to collapse
Don't worry, Google would not forget to bundle it.
Digital wellbeing is named WellbeingPrebuilt.
package: name='com.google.android.apps.wellbeing'
I just did not add it to the debloat list.
zgfg said:
Velvet.apk, what is the package name (you should still be able to find the name on /data/data)?
When you have Velvet (Poco F1, F2 and One+ 5T), do they also have Google.apk = com.google.android.googlequicksearchbox?
Click to expand...
Click to collapse
Velvet is Google.
package: name='com.google.android.googlequicksearchbox'
As far as I know, Velvet is the bundled and/or GApps name used.
Cheers.

HippoMan said:
I did it just now, and it worked wth no problems on my device! For my initial test, I used SystemlessDebloater to remove GooglePartnerSetup, and it was indeed removed. No bootloops, no problems..​
Click to expand...
Click to collapse
Just a short question - you have A11 on your OnePlus 7Pro?

zgfg said:
Just a short question - you have A11 on your OnePlus 7Pro?
Click to expand...
Click to collapse
One Plus 7Pro, GM1917, OOS 10.3.5 ... as I mentioned above OOS 10.x is A10.
.​

zgfg said:
Interesting - what happens when you debloat Chrome-Stub from Product and leave Chrome on Data, does it still run?
Btw, I do use Chrome (because of the integrated translator, making me easy to sometimes read worldwide forums if needed) and I didn't want to debloat originally. However, my preinstalled version on Product was not the latest, and Google Play was offering me to update, but updating Chrome was always failing.
I downloaded the apk from ApkMirror but installation had also failed
Then I debloated (at that time, prior to this debloater I used to manually create my system folder given to Magisk to overlay, and with dummy apk instead of with .replace file) and only then I was able to install Chrome apk (ofc to Data) and since then, to regularly update it through Playstore
Click to expand...
Click to collapse
Still have to test some more.
So far only on my Pixel aOS 11.
This is a little tricky to explain my testing/findings.
- Long post, truncated it for now. -
Not logged into Google. (PlayStore)
With Chrome stub active, Chrome is treated as a system app.
Even though the full version is in data it can not be uninstalled only disabled.
PlayStore shows an available update for Chrome.
If stub is removed (debloated), Chrome is treated as a user app.
You have the option to uninstall.
PlayStore does NOT show an update for Chrome.
Did not matter if I cleared cache and/or data on PlayStore or re-scan with with PlayProtect.
This is odd, since Google should still want to update even if it is just a user app.
I'll have to dig though the user agreement again.
Might be automatic update only when Google apps are included (system app) when not logged in.
--
As soon as I logged in, Google immediately updated some back-end.
Chrome is now available for an update and it updated fine.
This is also where some oddities came in.
--
<TRUNCATE>
--
Still have to double check everything.
Seems to be an issue distinguishing between system and user apps.
Should have time this weekend to redo and verify every step I used for testing.
As of now, I would suggest the same as you did it.
Debloat Chrome (stub)
Uninstall Chrome (should be considered a user app after the debloate.)
Install from another source (if need be then update from PlayStore.) or just install from PlayStore.
Cheers.

Btw, released v1.3.5 through the OP post #1 - just to log to the logfile the Android version, is it SAR and is it A/B - would be nice if you can test does it log correctly when you have time and A/B device.
Unfortunately, still unable to resolve a miss-communication with the bot to successfully submit to Repo

Can somebody dhare his debloat app list? Or the best, .sh file? İt would be great