Disable Setting Suggestions - Android Q&A, Help & Troubleshooting

Disable Setting Suggestions - Android Q&A, Help & Troubleshooting

I've found some information on this topic but the solutions I've found either don't really work or involve concepts that I don't understand. The closest thing I found to something I could use is to disable Setting Suggestions (which requires ADB) but that also disables the settings search function which is not acceptable to me.
My standard solution would be to enable Setting Suggestions when I need to use the search function and disable it when I'm done but since I can only disable Setting Suggestions by connecting to a computer with ADB installed this makes it too much of a pain to be practical.
Is there a way to use ADB to setup Setting Suggestions so that it can be disabled from within Settings?
Or is any other way to do this that can be explained to someone that barely knows how hook up a usb cable and run adb?

What are you referring to by "Settings Suggestions"?
Screenshots please?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AFAIK It's a system package that controls the display of suggestions within the Settings package as well as the settings search function.

If you have a custom rom, such as crdroid, you can disable it from the crdroid settings.
Otherwise, you can try rooting and uninstalling the package to see if that works.

PhotonIce said:
If you have a custom rom, such as crdroid, you can disable it from the crdroid settings.
Otherwise, you can try rooting and uninstalling the package to see if that works.
Click to expand...
Click to collapse
I was afraid that this would be the answer.
So this brings up another more basic question. I'm very new to all of this and so far all I'm able able to do is to use ADB to disable or uninstall user 0 apps that I otherwise could not modify from within the Settings app on my Walmart tablets. So what is the next thing I need to understand so I can have more control over how my devices function?
Which is simpler and less drastic, rooting a device or somehow getting a new rom? Is there any other option besides these?
I've seen some reference to backing up your device before trying these types of steps. Can you point me to any documentation that explains how I can backup and (more importantly) restore my tablet if something bad happens. This seems like a prerequisite to anything beyond ADB disable/uninstall.
I actually have a fair amount of experience of getting back to my current state from a factory reset so there's always that, but a reliable backup/restore could certainly save me hours of tedious configuration.
The bottom line is that I really don't know enough to even ask the right question. Any guidance you can provide is appreciated.

Rooting is probably the safer option. You can try using KingoRoot, it's a one-click root tool and is super easy to use. Try it a couple of times, if it keeps failing, you'll have to install a twrp image for your device and root via magisk. Since you're on a wallmart tablet though, I don't think you'll be able to get twrp for your model. You'll have to use fastboot to extract the boot.img, then patch it via magisk and flash it again to obtain root. Magisk is your best option for root.
Installing custom roms probably isn't possible for your device if its a generic wallmart tablet. If it has a brand name, please mention it. It will most likely be a random generic chinese tablet, so a custom rom for those is out of question.
Nandroid backups are used to backup your entire device. You can also take a TWRP backup if twrp is installed. If you mess up the rom using root (such as uninstalling a system module, or if the system bootloops or has any issues after deleting the module, a factory reset will not fix it, you will have to reflash the rom, most likely using sp flash tool if you have a mediatek soc in your device.
Considering that it may be a generic chinese tablet, it's probably better not to take the risks of rooting. I recommend that you try the KingoRoot app, and KingoRoot with your PC. If that doesn't work and you still want root, you're going to have to look into manually patching your boot.img. KingoRoot doesn't have any risks as far as I know, so do give that a try.
Please mention the tablet brand, if it is somewhat popular (and isn't a mediatek powered tablet), it may have twrp available for it unofficially, but don't get your hopes up.

Mumblefratz said:
I've found some information on this topic but the solutions I've found either don't really work or involve concepts that I don't understand. The closest thing I found to something I could use is to disable Setting Suggestions (which requires ADB) but that also disables the settings search function which is not acceptable to me.
My standard solution would be to enable Setting Suggestions when I need to use the search function and disable it when I'm done but since I can only disable Setting Suggestions by connecting to a computer with ADB installed this makes it too much of a pain to be practical.
Is there a way to use ADB to setup Setting Suggestions so that it can be disabled from within Settings?
Or is any other way to do this that can be explained to someone that barely knows how hook up a usb cable and run adb?
Click to expand...
Click to collapse
That's not how it works.
First, why do you want to disable it ?
Second, that package is responsible for search in settings app so disabling it disables search.
Thirdly, there's no way to disable/delete a system app without adb via PC, or with ROOT.

Mumblefratz said:
View attachment 5571037
AFAIK It's a system package that controls the display of suggestions within the Settings package as well as the settings search function.
Click to expand...
Click to collapse
You can turn off suggestions if that's what you need

I have it removed, along with a lot of other bloatware preloaded in my samsung phone. You can take a look
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com

Hamid Chikh said:
I have it removed, along with a lot of other bloatware preloaded in my samsung phone. You can take a look
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried adb removing stock bloat on my j510f, didnt work. Tried root and it did, so naturally i recommended it. Ofcourse, adb is the best option. OP even mentioned in his first post that he saw something related to using adb to remove bloat.

PhotonIce said:
Rooting is probably the safer option. You can try using KingoRoot, it's a one-click root tool and is super easy to use. Try it a couple of times, if it keeps failing, you'll have to install a twrp image for your device and root via magisk. Since you're on a wallmart tablet though, I don't think you'll be able to get twrp for your model. You'll have to use fastboot to extract the boot.img, then patch it via magisk and flash it again to obtain root. Magisk is your best option for root.
Installing custom roms probably isn't possible for your device if its a generic wallmart tablet. If it has a brand name, please mention it. It will most likely be a random generic chinese tablet, so a custom rom for those is out of question.
Nandroid backups are used to backup your entire device. You can also take a TWRP backup if twrp is installed. If you mess up the rom using root (such as uninstalling a system module, or if the system bootloops or has any issues after deleting the module, a factory reset will not fix it, you will have to reflash the rom, most likely using sp flash tool if you have a mediatek soc in your device.
Considering that it may be a generic chinese tablet, it's probably better not to take the risks of rooting. I recommend that you try the KingoRoot app, and KingoRoot with your PC. If that doesn't work and you still want root, you're going to have to look into manually patching your boot.img. KingoRoot doesn't have any risks as far as I know, so do give that a try.
Please mention the tablet brand, if it is somewhat popular (and isn't a mediatek powered tablet), it may have twrp available for it unofficially, but don't get your hopes up.
Click to expand...
Click to collapse
The tablet brand is Onn. I couldn't find out much about it other than it seems to be pretty much exclusive to Walmart.
However your response has pretty much convinced me that dealing with the specific question I posted in the OP is probably beyond my abilities at this time. I do have a vague idea of what you're talking about but that's about it.
I do understand that factory reset only restores the rom which is why factory reset can't unwind an update nor fix a screwup in the rom regardless of how it got there.
Ultimately what I am trying to accomplish is to gain whatever understanding and ability I can so as to have more control over the multitude of android devices I have in my life.
So far the limit of my bag of tricks is adb disable/uninstall. Yesterday I did a search of adb commands and found there's a lot more to adb than just disable/uninstall. I found a number of sources ranging from the offical seeming Android Debug Bridge (ADB) Commands Manual and Android Debug Bridge (adb) to adb cheat sheets and command lists put out by random folks and found them to be more than a bit intimidating.
However, the thing that caught my eye as having the most potential use to me are the following:
adb backup -apk -all -f backup.adb (backup settings and apps)
adb backup -apk -shared -all -f backup.adb (backup settings, apps and shared storage)
adb backup -apk -nosystem -all -f backup.adb (backup only non-system apps)
adb restore backup.adb (restore a previous backup)
These commands are simple on the face of it but there's still a lot that's not obvious. For example I assume that you can't use backup and restore fix a totally bricked device. On the other hand I would guess that if you haven't messed with the rom you can always do a factory restore first and then use the backup to save you the trouble of reinstalling and configuring all your 3rd party apps as well as restoring all the system disable/uninstalls save in the backup. Are my assumptions anywhere near corredt?
It's clear that I'm not a devloper, I'm not even a software engineer. I'm a retired digital hardware design engineer that would prefer not to get involved in all these details but can't help myself from trying to get things to work the way I want them to.
The essence of my question boils down to what next baby step can I take that extends what little control I have over my devices. Can you point me in ther right direction?

Hamid Chikh said:
That's not how it works.
First, why do you want to disable it ?
Second, that package is responsible for search in settings app so disabling it disables search.
Thirdly, there's no way to disable/delete a system app without adb via PC, or with ROOT.
Click to expand...
Click to collapse
I want to disable it because it annoys me.
I know disabling that package disables search which is why I said the followings in the OP first paragraph.
Mumblefratz said:
disable Setting Suggestions (which requires ADB) but that also disables the settings search function which is not acceptable to me.
Click to expand...
Click to collapse
I did not ask if you can disable/delete a system app without adb via PC (or root). I asked if I could use adb to change a system package so that it can be disabled from within the System Settings app.
Hamid Chikh said:
You can turn off suggestions if that's what you need
Click to expand...
Click to collapse
AFAIK I have disabled all suggestions, but that didn't stop suggestions made within the Settings app.
I did go through your link, [NO-ROOT] Samsung OneUI Optimization Guide - Settings, Fixes, Debloat, and ADB Features but didn't see anything related to suggestions please let me know if I'm missing something.
The biggest problem as I see it is the extreme variation from one brand of phone to another or one tablet to another tablet and even more so if comparing a tablet to a phone. I probably don't have even half of the stuff you list in your guide on my tablet.

Related

Resolved: conflict between gapps and the stock launcher after root my HDX Apollo

EDIT: Problem is resolved. After I learn very much:
I made a video, cause there is no helpful video with Safestrap 4. Only with Version 3 and this way is wrong now!
I also write a blog about that helpful storry and links that will help other's.
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.

Gatam77 said:
Hello,
i started to root my Apollo 8.9/LTE with Tutorials from here and a translation in german. I live in germany.
http://www.android-hilfe.de/thema/r...r-kindle-hdx-8-9-apollo-fire-os-4-5-2.693547/
http://forum.xda-developers.com/kindle-fire-hdx/general/tut-disable-ota-4-5-2-install-gapps-t3043550
Root Tool
Thats what i do
Rollback to OS 3.2.8 was great
Update to 4.5.2 was also ok
I rootet my Apollo, it works - i tested it
After that i renamed the DeviceSoftwareOTA.apk from Kindle in the priv-app
Now i copied all needed GAPPS files to the system Folder except the descripited
After that i restart my Apollo and now the Problems start
After restart
Google Folder with Images
The Google Assistent start immediately after restart
I have to choise a Language but there was no german
Also i had no WIFI Connection, so the Assistent start the Option to connect with WIFI
This work, but at the wifi there is a X and in the Assistent i habe no Internet connection
I use my SIM Card to get a internet connection (This work) but the Assistent need a WIFI
Also i lost my root and get Denied when i try to copy/change with a older version befor April 15 or delete the GAPPS Files in the system Folders
I can start/install Apps with apk, at the apollo i only can use the settings. I have no menu or keys
Thats what i tried
I can use adb and install ES Datei Explorer or SuperSu
I used KingRoot, it dosn't work
I copied the mod Rollback to 3.2.8 bin File in the root folder, but Apollo dont use this file, maybe cause i renamed the OTA Systemfile
I made a reset of the Apollo, but the google Assistent is in the systemfiles and start even after a reset
My Apollo
Has Fire OS 4.5.2
The DeviceSoftwareOTA.apk is renamed
I only can Read NOT Write in the system folders
I can use adb and connect to the Apollo
I tried so much the last 2 days so i hope you got a hint for me.
Click to expand...
Click to collapse
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher. That is probably why you are not seeing soft buttons, keyboard, etc. The only known solution is to temporarily use a different launcher to regain control of your device long enough to reroot. Problem is your device will revert back to the stock launcher on a number of different events including pressing the home key which frequently doubles as 'back' on FireOS. You then have to reinstall the non-stock launcher or find some way to make FireOS treat it as primary.
General overview:
- grab a copy of Nova or Apex (other launchers will probably work too)
- install via 'adb install' (research if unfamiliar)
- if all goes well you should regain temporary use of soft buttons and keyboard
- stay away from home key if possible as it will immediately restore the compromised stock launcher
- attempt to reroot your device with Kingroot. This should be safe given OTA is blocked. You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic; hopefully it will pick that up via your sim card
- you can also try rooting with CVE-2014-4322 exploit.
Once you are rooted there are several paths that can be pursued. Since you have a LTE device installing Safestrap and a different ROM probably isn't the best option. Nor is reinstalling gapps on FireOS as you will face an ongoing series of battles (conflicts) between Amazon and Google frameworks. You may need to roll back and upgrade again to fully resolve the launcher conflict.
Discussion for a different post. See if you can get rooted first.

Davey126 said:
You made some serious mistakes (come back to that later)
Click to expand...
Click to collapse
maybe you mean in a later post. Or do you mean, that i crash some Fire OS Framework with the GAPPS framework
Davey126 said:
Apex
Click to expand...
Click to collapse
I take Apex, i am familar with it.
Davey126 said:
You many need to install Kingroot via adb. Once launched Kingroot needs an internet connection to do its magic
Click to expand...
Click to collapse
i install kingroot 4.1 allready on the Apollo and also the software in my pc. Then i start the windows software but root didn't work. - Maybe because i dont have a internet connection on the Apollo??
Davey126 said:
you can also try rooting with CVE-2014-4322 exploit.
Click to expand...
Click to collapse
I used the cve20147911.apk from here (it work one time, bevor the GAPPS), but i try this one.
Davey126 said:
You may need to roll back and upgrade again to fully resolve the launcher conflict.
Click to expand...
Click to collapse
I couldn't rollback now. Is the reason that i dont have root?

Gatam77 said:
I couldn't rollback now. Is the reason that i dont have root?
Click to expand...
Click to collapse
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.

Davey126 said:
You can't change FireOS versions because you previously blocked OTA by renaming DeviceSoftwareOTA.apk. This file is required to perform rollbacks/upgrades. You will need to obtain root permissions to restore the original filename.
Click to expand...
Click to collapse
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?

Gatam77 said:
OK. With this file the update Start. But befor the Update load from amazon Website this takes first a look on the SDCard. Wright?
Click to expand...
Click to collapse
After enabling OTA put your device in airplane/flight mode to prevent updates from downloading. Make sure your device is stable (starts/functions normally) before attempting a rollback/update. I also advise allowing your device to upgrade to 4.5.5 (you will loose root) and then restart the rollback procedure from there.

Davey126 said:
Nice post; well documented.
You made some serious mistakes (come back to that later) and have a challenge ahead recovering your device. Based on others experiences there is some type of conflict between gapps and the stock launcher.
Click to expand...
Click to collapse
Thx for your words.
I installed a launcher and restart but also had no buttons. But a other way was it.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.

Gatam77 said:
Thx for your words.
I GOT IT!!
I dont have permission on system folder with ES Datei Explorer, but now i use adb.
I found a post here how to change permission with adb
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
chmod 755 /system/app
Now i rename the file with mv MYNAMEOFOTA to DeviceSoftwareOTA.apk
After i used the gifroot Files But i got a message that it wouldnt work with this kernel.
So i dont know exactly which way was it.
But now to my serious mistakes. Can you tell me please what you mean? Cause I love this amazon hardware but I hate the amazon Fire OS and i love GMail, sheets, Maps, and other good apps from Google. So i need root.
All works bevor i push the GApps. So what is the better way. I know I have to read much more bevor i start again. Cause the Apollo is tricky.
I wait for a answer of you bevor i rollback to 3.2.8. I can wait.
Click to expand...
Click to collapse
Congratulations! Glad you were able to make some progress. Unfortunately, you are not out of trouble yet. Do not change permissions on any other files as FireOS is very sensitive and sometimes will not start if permissions are not as expected. Especially on 'system' files and folders.
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together. While some have got it to work acceptably there are almost always problems, some quite serious.
A better approach is to use a twrp (recovery) emulator called Safestrap. Once installed you can install a limited selection of high quality ROMs that offer full access to the Google Play store. You may be familiar with the names: Nexus and CM11. They essentially turn your Kindle into a generic android tablet. You can even use native Amazon apps like Kindle reader.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
There are many posts on XDA detailing the rollback/upgrade/root/blockOTA/Safestrap/rom process. Start here and spend some time reading. I did not pick this thread because it was the 'best'; just one I happen to remember contributing to in recent days. But it will lead you to other helpful posts that lead to even more posts ...
As always:
- ask questions if unsure; never assume or guess
- keep WiFi off (airplane/flight mode engaged) to prevent OTAs when upgrading or rolling back. Consequences are large: an OTA can (and likely will) permanently brick your device.
- make sure you fully understand the procedures, expected outcomes and recovery options if things go wrong
- only use files posted on XDA (links ok too)
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.

Davey126 said:
Two concerns with the approach you took:
- using an outdated mod guide not published on XDA. Some of the techniques are old or no longer recommended
- attempting to install GApps on FireOS. Amazon and Google frameworks do not play nice together.
The downside is LTE is not well supported by these roms. If you use your tablet off WiFi and need LTE then you have a tough decision to make:
1) Forgo LTE in favor of a rom with full Google Play access
2) Retain LTE and FireOS with limited access to Google services and apps
As always:
- ask questions if unsure; never assume or guess
- a fresh mind helps; take a break when tired. Your device will wait.
Good luck.
Click to expand...
Click to collapse
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.

Gatam77 said:
The again a lot.
I need my Mobile Internet. Not really LTE but at least 3G! But LTE get better here in Germany so it would be nice.
I like CM. I already flashed my Samsung S3, my wife S3 Mini, and my 2 Amazon's Tate.
That's why I bought the Apollo and hope after 1 year or so there will be a custom ROM with LTE working. So if someone interested I will flash a Custom Rom, life a time without Mobile Internet and help the developer with sending log files, or other needed things.
No I started reading! But I will post again here that other can read and learn from my mistakes.
Click to expand...
Click to collapse
FYI - you can find the Safestrap compatible CM11 rom thread here. As I recall some aspects of LTE/3G work ok. Skim through the posts for more detail. Might be a non-issue for your needs.

Davey126 said:
You don't have to make that decision now. First step is to rollback to 3.2.8, upgrade to 4.5.2, obtain root and block OTA. In a previous post I suggested upgrading to 4.5.5 first. I am stepping away from that suggestion to streamline the process. However, there is additional risk going from 4.5.2->3.2.8 because if anything goes wrong you could end up bricking your device. Going from 4.5.2->4.5.5 is less risky but adds another step.
Click to expand...
Click to collapse
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?

Gatam77 said:
After i was short befor to brick my Apollo, maybe I would first Going from 4.5.2 > 4.5.5 and then 3.2.8 > 4.5.2.
But i dont read a hint with a link to 4.5.5. Can I download ist from here Davey?
Also i take a look in my router and he block some IPs when I used Kingroot on my PC yesterday.
14.17.41.155
202.77.59.49
163.177.71.157
120.198.203.149
103.7.29.30
They come from Hongkong and Bejiing. Is it possible that that was the reason Kingroot couldn't root my Apollo?
Click to expand...
Click to collapse
I can't speak to what IPs Kingroot uses. There have been various reports of it being slow or temporarily not working. Perhaps due to network congestion. Usually clears up after a few hours.
If you have restored DeviceSoftwareOTA.apk you can simply enable WiFi (disable airplane/flight mode) and allow the device to receive an OTA and self-update to 4.5.5. This is actually a good test OTA functionality is working which is also required for manual rollbacks/upgrades.
There is another option that does not involve rollbacks/upgrades: If you can obtain root you can then attempt to install Safestrap v4 followed by CM11 or Nexus v4 (you can also 'repair' FireOS using this method). Both Kingroot and Safestrap require interactive access. You don't need to type anything (so keyboard doesn't need to display), just tap an on-screen button or two. You would need to install apks via adb and then have enough control over your device to launch the app. Not easy or intuitive.
I will caution there is risk with either path (upgrading FireOS or installing Safestrap on a dysfunctional device). You have to weight the risks and take the course the feels most comfortable. There are no guarantees.
Reminder: do not do a 'factory reset' from the native recovery menu unless recommended by an experienced contributor, especially after rooting or installing Safestrap.

Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?

Gatam77 said:
Now all is ok again. I am so joyful.
First Download Safestrap from here
Downloaded and Follow the instructions here
Now i can start with a new and clean Android on a good Amazon Hardware
Installed Safestrap on my damaged Fire OS 4.5.2
Than install a recovery in the Safestrap APP
After that i made a slot with 1200 System/1500 Data/1000 Cache
Active the slot
go into Wipe Menu and Swipe to perform a factory reset
Go in the Install Menue and install CM11, GAPPS and SuperSu
Now i started in CM11
Again thx to Davey126.
My stock ROM is still the damaged where I mixed amazaon and google framework. What can i do?
Active the Stock slot, start into my damaged Fire OS
Push with adb a Fire OS 4.5.5 to the sdcard
Or make a OTA over the WLAN from amazon?
Or (in the video says: NEVER touch the stock at Safestrap) Install a Fire OS bin in Safestrap to witch slot?
Click to expand...
Click to collapse
Excellent - glad to hear the progress!! However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
The use of secondary slots is not recommended in Safestrap v4:
WiFi only works with CM11; Nexus v4 and Stock FireOS will fail to make a connection
Only 2 of 4 CPU cores are utilized resulting in poor performance under load
CPU runs at maximum speed at all times (no throttling) resulting in high battery use when idle
GPU does not throttle
Device never enters 'deep sleep'; radios remain active at all times
Backups can not be migrated between slots; flashing a secondary slot backup to the stock slot will brick device
Slot storage must be allocated in advance and can not be adjusted (must delete/recreate/reflash rom)
Recommended path:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
This means your device will be running CM11 with no access to FireOS. However, if needed you can replace CM11 with FireOS 4.5.2 from this thread. Note the images are customized for Safestrap; flashing a unmodified stock image will brick your device.
Miscellaneous:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Make a backup of the stock slot from within Safestrap (it will be large); move to a host PC for safe keeping
Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.

questioning asking
This is so interesting. So sorry for my allways following questions. You said I should ask, but maybe also other can have a answer for me. This also cost your time.
So if you can't answer its ok. Or if there are only some hint words that will be a help for me to find out more. Whatever.
I am more than thankfull for that help to find out more about Android.
Davey126 said:
However, there are some important changes needed that will greatly improve your CM11 experience (battery life, performance, stability). Some of this contradicts information in the video and recommendations from other versions of Safestrap.
Click to expand...
Click to collapse
Ok, a next thing that i can search for.
I see some of my Apps close very often. Special Play Store
Davey126 said:
Delete secondary slot (this will destroy your CM11 installation)
Flash CM11, GApps, SuperSu in stocki slot; this will overwrite FireOS in stock slot
Click to expand...
Click to collapse
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1. Or are they more reasons for that step?
Davey126 said:
NEVER perform a 'factory reset' from the native recovery menu; your device will brick
Click to expand...
Click to collapse
Whats do you mean special with "native recovery"?
That i start with the StockRom into my FireOS and after that i make a factory reset?
Davey126 said:
[*] Always keep a flashable copy of CM11 image on the device (in the root of sdcard) for emergency recovery. Safestrap v4 can not communicate via wifi, bluetooth or tether. If CM11 fails to boot your only option is to reflash an OS (CM11, Nexus or FireOS) from within Safestrap recovery. If a Safestrap compatible/flashable image is not already on the device you can not recover from this type of failure.
[/LIST]
Click to expand...
Click to collapse
I will do this! But...
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download.
Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Like
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Davey126 said:
[*] Safestrap may appear to be a full blown recovery but it is actually a TWRP emulator that runs within the system partition and has dependencies on other Amazon components (bootloader, native recovery, etc) that remain on your device from the previous FireOS 4.5.2 installation. Be careful with advanced tools that run at a low level. It is possible to 'damage' your device to an extent that it can not be recovered. Ask first if uncertain.
[/LIST]
Click to expand...
Click to collapse
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
When ends the Low Level and start the Deep System?

Gatam77 said:
With secondary slot you mean the ROM Slot 1, cause the Stock will be the first slot maybe?
Click to expand...
Click to collapse
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Gatam77 said:
I don't will go back to the Fire OS cause i have a Fire TV Stick and a Raspberry for that. If i still think so in some months i also can flash the Stock Rom with a CM Image? But its not necessary cause i have my CM11 or maybe in the future CM13 in the ROM Slot 1.
Click to expand...
Click to collapse
You do not want to maintain multiple slots (ROM images) in Safestrap v4. When you switch ROMs you overwrite the existing ROM in the Stock slot. You can overwrite CMxx with FireOS. At present CM12 and CM13 are not compatible with Safestrap v4. Do not attempt to flash any ROM image other than those specifically listed as "Safestrap Compatible".
Gatam77 said:
Whats do you mean special with "native recovery"?
Click to expand...
Click to collapse
"Native recovery" is the one supplied by Amazon accessible via <power> + <vol-up> from a cold start. NEVER use the 'factory reset' function from this menu when Safestrap v4 is installed; your device will brick.
Gatam77 said:
I dont know, at this time, so much from safestrap. But i take look in it, and i can use ADB Sideload, Mount a USB Storage. Maybe also to reboot into the Download. Is a push from adb or a Backup on a USB not also a way to restore a damaged Custom ROM.
Click to expand...
Click to collapse
None of these features work with Safestrap. Think of Safestrap as a virtual machine with ROMs running inside (technically inaccurate but conceptually convenient). You can only make full use ADB after portions of the ROM are up and running. If the ROM is damaged/unbootable you must do all repairs from within Safestrap. At present Safestrap v4 can not communicate with the outside world; all repair tools/images must be 'on board' (preloaded).
Gatam77 said:
Start into Safestrap
Wipe my Slot with the CM11 or delete ist and create it again
Push with adb a new file of CM11, GApps, SuperSu into my data permission
And after that flash it to the Data Partition
Click to expand...
Click to collapse
Probably repetitive but you do not want to recreate ROM Slot 1. Delete it and then flash CM11 (or Nexus v4 or FireOS) to the Stock slot.
Gatam77 said:
How i can find out what Low Level tools are?
I think a recovery like TWRP is one.
I also use Tasker or BusyBox. They can make also deep things on my system. Also Low Level?
Click to expand...
Click to collapse
- You can not use 'native' TWRP on your system as the bootloader is locked and can not be unlocked. Safestrap emulates TWRP.
- Tasker and BusyBox are fine
- Be careful with Xposed modules or other 'tweaks' that might cause your device to become unbootable.
Bottom line: enjoy CM11 and the apps that can be installed from the Play Store. Resist the temptation to customize further. If your device freezes or becomes unbootable you may not be able to recover.

Davey126 said:
Yes - delete all ROM slots (1-n) that you created. Bottom line: you only want to use the Stock slot.
Click to expand...
Click to collapse
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom

Gatam77 said:
Short Post
Oh my god. Again I trust a old Video. More later
So i install again.
First i make a backup (over WLAN) from my Stock Rom. I didn't get connection over USB at my PC neither connect a USB Stick to the Micro USB Slot. That's may what you mean that Sfestrap works like a virtual mashine.
So i CHECK if all files are at my root folder in the stock
After that i Wipe the Stock Rom
After that Flash all needed files and install like the last time but this time into the Stock Rom
Click to expand...
Click to collapse
Good! Please confirm that you are now running CM11 in the Stock slot.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
- avoid potential confusion while in Safestrap recovery which could possibly lead to a bricked device
Once everything is stable boot into CM11 and move the large backup files to a host via tether (fastest), WiFi or Bluetooth. You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
You can not attach a flash/thumb drive or any other USB device (including keyboards/mice) to the micro-USB port as HDX devices lack OTG support at the hardware level. An unfortunate design choice by Amazon and can not be fixed via software or special cables.
Keep in mind the HDX is a sensitive device. After flashing a ROM there rarely a need to return to the Safestrap recovery environment. Exceptions:
- flash a newer version of ROM (release release notes carefully)
- make periodic backups of your existing system and data partitions

Davey126 said:
Good! Please confirm that you are now running CM11 in the Stock slot.
Click to expand...
Click to collapse
I will do. At the moment it is still in Slot 1 and i recharge battery to 100%.
Maybe tomorrow . Because there is no video with this, i try to make a movie while making all this steps.
Assuming 'yes' you can (and should) remove all other slots if still present. Benefits:
- recover 3-4 Gb of permanent storage on your device and return it to the stock slot
Click to expand...
Click to collapse
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
You do not need to keep backups on your device for recovery purposes; only the smaller ROM image.
Click to expand...
Click to collapse
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.

Gatam77 said:
So i Flash my CM11 to the Stock Rom. And AFTER That i remove the other Slots.
After that I can recover storage back to the Stock ROM?
Click to expand...
Click to collapse
Correct. Although the goal is to delete all secondary (non-stock) slots there is no benefit to removing the slot that is currently hosting CM11 until you have confirmed the reflash of CM11 to the stock slot. This leaves you with a working ROM should something go wrong.
An 'idle' secondary slot does not present a problem just being there. However, it consumes considerable space and increases the possibility of making a fatal mistake while working in Safestrap recovery. Ultimately the decision is yours whether to keep or discard secondary slots. However, you want your primary slot to be stock. Hope this makes sense.
Gatam77 said:
After all works with the Custom Rom on the Stock Rom, i leave the ZIP file on my device after the flash. All other like GAPPS i also can thether later, if i need this again.
Click to expand...
Click to collapse
Correct.

Grand Prime SM-G530R4 || Root & Xposed Framework || Quick Guide

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pictures are .PNG screenshots of JRummys' Root Check - verifies Root & Xposed Modules **(XPrivacy) installed. -- side note, don't use xprivacy on Lollipop yet. Its' high on a short list for causing a memory leak I'd dealt with.
Samsung GRAND Prime - SM-G530R4 - LMY47X.G530R4TYU1AOL2
Root (SuperSU v2.65) // XPOSED Framework (v80.0 Lollipop) // FlashFire (v0.27 BETA)
More than willing to write up a full guide, however all of the instructions can be found right here on XDA, and I was just so thrilled to find a way to install Xposed, let alone a working (albeit beta) Zip flash utility.
Will void warranty.
Root Device w. CF-Auto-Root - http://forum.xda-developers.com/showthread.php?t=1980683
Find listing for: LMY47X.G530R4TYU1AOF5 - this is the only G530R4 listing.
Samsung | SM-G530R4 | gprimelteusc | MSM8916 | LMY47X.G530R4TYU1AOF5 | 5.1.1
Click to expand...
Click to collapse
-Follow the XDA forum link above, then onward again to Chainfires' CF-Auto-Root Repository @ https :// autoroot.chainfire.eu
-This is the only firmware listed for the G530R4 device, it WILL work with any available Lollipop 5.1.1 firmware for the G530R4, use Odin tool included with CF-Auto-Root to flash.
-For me, this method did NOT restore stock recovery.img -- although I *think* it was because of KNOX / SELinux; either way it is a non-issue after FlashFire is installed next.
Click to expand...
Click to collapse
Install XPOSED Framework w. - *Must* be done manually via custom recovery (not available for G530R4 to my knowledge) OR by using FlashFire v0.27 BETA
FlashFire v0.27 BETA *Required*- http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
- Do not proceed without this application.
-This tool is required to replace the function otherwise filled by a custom recovery capable of flashing .ZIP files directly to the device, from the device.
-MUST- Sign up for beta testing, to install the FlashFire beta APK this worked for me on the first try
- Note: FlashFire action queue will have a warning about Samsung write protection possibly causing issues if the Stock ROM is custom modified (i.e. such as after Rooting with CF-Auto-Root; this did NOT give me any problems; also, I did not change ANY default settings within FlashFire.
- Note: AFTER YOU FLASH THE XPOSED .ZIP the first boot will take much longer than usual, entire flash & boot took ~15 minutes for me.
Click to expand...
Click to collapse
Xposed Installer APK http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
-Download either from PC or device; and install the APK on device
Click to expand...
Click to collapse
[UNOFFICIAL][5.1.1/6][v80.0][11 Feb]Xposed for Samsung Lollipop/Marshmallow - http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
XPOSED v80.0 SDK22 ARMv7 -
-The .ZIP file you want is "xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip" listed at the bottom of OP.
-Download .ZIP file and place it on the SD card of your device. Use FlashFire to flash the ZIP (I did not change ANY setting from default within FlashFire, follow all directions as specified for XPOSED installer, several appropriately timed reboots are required.
Click to expand...
Click to collapse
-- Afterwards, be sure to download all of Chainfires' apps (they're all awesome) and donate.
-- The developer who ported Xposed v80.0 to Lollipop 5.1.1, wanam also has several Xposed Modules & apps worth checking out
-- And of course thanks to rovo89 for Xposed in the first place

Thanks a lot for this tutorial! Flashed Xposed on my SM-G530AZ with no problems at all

THANKS!
I appreciate this post a lot, because I guess nobody has a G530R except us and a few others. I find this strange, because you can get USCellular from WalMart with this phone for a little over 100$ and it is only 45$/month for a decent amount of data (and is unlimited after). Anyway, just wanted to thank you for this and ask a few questions.
I was wondering if you have any suggestions or any tips for backing up, to prevent data loss. I used ADB to create a backup that way, but don't know what way is best. I don't care about time and am used to command line, so that isn't an issue. I just don't know Android OS well enough or the backup systems to know what is going to create a complete backup. I was trying Flashify, but am confused about what it is exactly saving and what is needed to restore. I want to make several backups. 1 complete (all apps included) and 1 just the OS. I don't know what is necessary for just the OS and want to make sure that I don't softbrick my phone. I was thinking the backup I made with ADB would be sufficient, but don't know if that covers the AOS. I also want to keep an OS backup on my phone and want to make it as small as necessary, to save space and keep in on my sd card. I don't know which is the better route to go and how restoring works with Flashify, since TWRP and CWD don't work. Do I always need to use Odin or ADB? What is the difference between those? Any help would be greatly appreciated... ESPECIALLY, since, like I said earlier, nobody has this phone. Also, I don't know if I should use the newer versions of Xposed or not. I have heard that they need supporting software and want to keep it simple. Do you know any good rooted-apps? What Antivirus do you recommend after rooting? I have it narrowed down to Bitdefender, avast, 360, CM Security, Kaspersky, or Norton. I believe I am going with Bitdefender, due to the free version being comparable to paid versions of the others. I am great with computers, but want to learn all I can before moving forward. I thank you for helping me with rooting the phone! I have other OS Copies and don't know how to tell if they are good or not... Is there a way? Will flashing them possibly softbrick or even hardbrick my phone if they are wrong? It is just so complicated with a Samsung and having a USCellular phone, since I am also worried about losing my prepaid service and having to buy a new one (if I accidentally clear their info). Finally, are there any apps you recommend for improving performance? I pride myself in boosting Windows this way, but have no clue when it comes to phones. All of this is an attempt to get the virtual gyroscope module to work, so I can play some decent VR games (since they require gyroscope and the ones that don't have crappy graphics). Please let me know if there are any knowledge base resources specific to this phone or any apps, rooting kits, rom apps, or custom recovery programs that are out there that you use. I would greatly appreciate it! ... sorry for droneing, but I am just so excited to find someone else using this phone! TYVM for what you already have done!

Hi guy great looking post I've been searching for a guy like this but Google always points me to g530h or some other model do u have a working custom recovery as well I can't find one and can't port one to save my life I'm at work but I'll try this as soon as I'm home

nick.squatta.reynolds said:
I appreciate this post a lot, because I guess nobody has a G530R except us and a few others. I find this strange, because you can get USCellular from WalMart with this phone for a little over 100$ and it is only 45$/month for a decent amount of data (and is unlimited after). Anyway, just wanted to thank you for this and ask a few questions.
I was wondering if you have any suggestions or any tips for backing up, to prevent data loss. I used ADB to create a backup that way, but don't know what way is best. I don't care about time and am used to command line, so that isn't an issue. I just don't know Android OS well enough or the backup systems to know what is going to create a complete backup. I was trying Flashify, but am confused about what it is exactly saving and what is needed to restore. I want to make several backups. 1 complete (all apps included) and 1 just the OS. I don't know what is necessary for just the OS and want to make sure that I don't softbrick my phone. I was thinking the backup I made with ADB would be sufficient, but don't know if that covers the AOS. I also want to keep an OS backup on my phone and want to make it as small as necessary, to save space and keep in on my sd card. I don't know which is the better route to go and how restoring works with Flashify, since TWRP and CWD don't work. Do I always need to use Odin or ADB? What is the difference between those? Any help would be greatly appreciated... ESPECIALLY, since, like I said earlier, nobody has this phone. Also, I don't know if I should use the newer versions of Xposed or not. I have heard that they need supporting software and want to keep it simple. Do you know any good rooted-apps? What Antivirus do you recommend after rooting? I have it narrowed down to Bitdefender, avast, 360, CM Security, Kaspersky, or Norton. I believe I am going with Bitdefender, due to the free version being comparable to paid versions of the others. I am great with computers, but want to learn all I can before moving forward. I thank you for helping me with rooting the phone! I have other OS Copies and don't know how to tell if they are good or not... Is there a way? Will flashing them possibly softbrick or even hardbrick my phone if they are wrong? It is just so complicated with a Samsung and having a USCellular phone, since I am also worried about losing my prepaid service and having to buy a new one (if I accidentally clear their info). Finally, are there any apps you recommend for improving performance? I pride myself in boosting Windows this way, but have no clue when it comes to phones. All of this is an attempt to get the virtual gyroscope module to work, so I can play some decent VR games (since they require gyroscope and the ones that don't have crappy graphics). Please let me know if there are any knowledge base resources specific to this phone or any apps, rooting kits, rom apps, or custom recovery programs that are out there that you use. I would greatly appreciate it! ... sorry for droneing, but I am just so excited to find someone else using this phone! TYVM for what you already have done!
Click to expand...
Click to collapse
I know I'm probably a couple years to late to answer your question I just couldn't help myself... First of all since you would be familiar with flashfire to complete this guide that is what you Should use to take your back-ups since it will take everyone of the backups you listed plus it will let you choose the format whether it be .img. zip .tar etc
Second antivirus I honestly don't run one and don't know many people who do on their modded phones.
Third since you followed the guide of The OP and run Xposed greenify and amplify are musts for battery performance I also personally love luckypatcher and if you play Google Play games you will too...
Also if you know computers as well as you say you do their are many guides how to create a TWRP or CWM recovery here on XDA so you could always just make one for this phone.... The only reason there isn't one is most likely because a developer hasn't got sold of this phone seeing as how u.s. cellular is such a small company... Sorry if this was for nothing I just felt like I wanted to put in my two cents

A lost beginner looking for privacy and control

Hello,
I recently acquired a Sony Z5C, planning on switching to LineageOS sooner or later, but the android tweking world is way more complex than I initially imagined. I am mostly concerned about privacy and control but there is so much to go through I am completely lost. I thought it was all about running either Sony's rom or the lineageos rom but there seems to be a lot more to take into account.
What I am looking for:
getting rid of Sony's annoying bloatware
getting rid of Google Play Services
automatic or semi automatic security updates
fine tuning of application permissions (including ability to deny specific apps access to, say, my location, contact list, camera, internet, sms, without the apps noticing they have been denied access in the first place)
ads and trackers blocking (for instance global or per-application blacklisting of known "evil" domains)
being able to restore everything as it was when I purchased the phone
f-droid begin able to download and install updates without manual intervention
as little side effects as possible resulting from the deletion of the Google Play Services
Icing on the cake:
no loss in camera quality (I read somewhere it is sometimes possible to use image-enhancing algorithms despite having deleted the required DRM keys)
no loss in gps accuracy
same battery life (or better)
encompassing all data traffic of specific apps through tor or another technology preserving distant services from identifying me and my mobile network operator from knowing I access said services
Questions:
What is the difference between opengapps and microg? How does it relate with lineage? At which point in the installation process is it involved?
What are the consequences of rooting the device?
What is the purpose of so called "Magisk"? I read it "changes everything" but I have no idea what "everythin" was. As far as I understand, it is useful to fake a genuine configuration that have not been tempered with in order to use Google Pay or some games. I do not seem to care about that: should I? Is there more to know?
Most important question: in your opinion, considering the above points, the phone I have, current trends and hindsight, and your experience, what would be the best way to go? Should I follow the installation steps on the official lineageos page for the Z5C or do you think another option would suit me better?
To illustrate my technical knowledge: I have been a gnu/linux user for almost a decade but I am completely ignorant of the Android world and feel lost. In particular the concept of "root" and how user and system data is organized on the filesystem(s) (especially on Sony devices) seem different. I am willing to learn and get technical, but there is too much information and I do not know where to start with zero experience.
Thank you very much for your help.

I am in same situation. Did things like that for Moto and Samsung already, but I am new to Sony.
Key is to install TWRP. This is some kind of recovery where you can
- make a backup
- install LOS
- recall backups.
Once this is done:
- install root/su
- tingle the framework (to get microG running)
- install microG
- install afwall (firewall)
- install adaware
only than plugin a SIM and/or enable Wifi.
So: first thing is to install TWRP
unlock Bootloader:
To be able to unlock your Xperia Z5 Compact, prepare it by following these steps:
Go into Settings > About phone and tap seven times on Build number to enable developer options.
From Settings, go into Developer options and enable OEM unlocking.
Warning: Device protection features will not work on this device while this setting is turned on.Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialer and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
TWRP
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
A few words to your queston:
opengapps are not open source, they just add normal google apps to Custom Roms. With all pros and cons.
MicroG is offering some kind of api, so that most features can be used (notification, google maps, access to playstore).
They are installed after the custom rom. Some people don't install any of them, use FDroid as a store.
root gives you the chance to change settings, for a few advanced configurations it is required (or makes it easier): firewall, ad remove ...
No experience with magisk. It is another way of "rooting" it, gives more features (hide the root status) which is required for some games. Not needed it til now.

What seems to be missing from previous post is to backup your DRM keys since unlocking your bootloader means losing them FOREVER.
Regards,
Aeny

Aeny said:
What seems to be missing from previous post is to backup your DRM keys since unlocking your bootloader means losing them FOREVER.
Regards,
Aeny
Click to expand...
Click to collapse
Right, but didn't you need TWRP to make a backup. And that is on my list, first point. Or is it a special step to do?

Thank you for your help and valuable information which now raises even more questions
If I get things right TWRP is low level stuff that would allow me to backup and restore the system whenever I need to. Say for instance I just installed LOS and configured it as desired so I use TWRP to get a backup and if I later mess things up I can restore this backup without having to go through the whole installation and configuration process? How does the official LineageOS installation guide fit in all this, sould I follow it? Do I need to follow a completely different procedure? I am not planning to tinker anympre once everything has been set up, is TWRP only recommended for people who often experiment and change things or is it recommended for everyone?
The DRM keys are removed when unlocking the bootloader but since TWRP requires an unlocked bootloader they have to be backed up beforehand, am I right? Does it mean I can restore them afterwards once the bootloader has been unlocked without locking it up again? How can I back them up in the first place?
I cannot seem to picture how all the pieces fit together, which is low level stuff, which is high level. When you say "install microg", "install afwall", "install adaware", what are microg, afwall, adaware? Are they regular applications? Regular applications with root access? Low level modules? How is root managed in comparison with a gnu/linux system where I can either directly log as root, change user to root with "su", or get temporary privileges with "sudo"? When you say "install root/su", are we simply talking about installing the equivalent of "su" or "sudo" on a linux distribution? Is there a root password I shall input each time it is required or provide some applications root privileges through a configuration app? Is such an application to be installed separately?
Thank you for the clarification about opengapps/microg. I am interested in microg although I can give a try without in the beginning as long as it is still possible to install microg later.

fetchaspade said:
WRP only recommended for people who often experiment and change things or is it recommended for everyone?
Click to expand...
Click to collapse
Yes, highly recommended if not even required. All my LOS setups run via TWRP.
fetchaspade said:
The DRM keys are removed when unlocking the bootloader but since TWRP requires an unlocked bootloader they have to be backed up beforehand, am I right? Does it mean I can restore them afterwards once the bootloader has been unlocked without locking it up again? How can I back them up in the first place?
Click to expand...
Click to collapse
Good point. Don't know where do I need this DRM keys for, as I did't faced off this with other mobiles.
I think you have to make a backup of the TA partition:
https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597/
fetchaspade said:
I cannot seem to picture how all the pieces fit together, which is low level stuff, which is high level. When you say "install microg", "install afwall", "install adaware", what are microg, afwall, adaware? Are they regular applications? Regular applications with root access? Low level modules? How is root managed in comparison with a gnu/linux system where I can either directly log as root, change user to root with "su", or get temporary privileges with "sudo"? When you say "install root/su", are we simply talking about installing the equivalent of "su" or "sudo" on a linux distribution? Is there a root password I shall input each time it is required or provide some applications root privileges through a configuration app? Is such an application to be installed separately?
Click to expand...
Click to collapse
addsu is to flash via TWRP in same manner like LOS itself - as a zip. Others are regualar applications (installed like that) but required root privileges to work. No root password required. Once an app needs it it will ask you, and if you like it remembers you allowed it (so it will ask just once usually). Recommend to try this. You can't do much wrong if you create a backup
fetchaspade said:
Thank you for the clarification about opengapps/microg. I am interested in microg although I can give a try without in the beginning as long as it is still possible to install microg later.
Click to expand...
Click to collapse
MicroG is a bit more fiddling to install than gapps and seems to has limitations. There are separate threads for just this.
Just start, you will get a feeling for that all.
Edit: But
there is already a lineagos with microG built-in:
https://download.lineage.microg.org/suzuran/

Thank you starbright_
To recap, I am to unlock the bootloader, install TWRP, flash addsu via TWRP, flash lineage enhanced with microg, and I'm good to go.
I'm still stuck on the very first step: backing up the TA partition. If I'm not mistaken I need the TA backup tool which requires root access. Root access requires an unlocked bootloader (which would remove the TA partition and the DRM keys) or is achieved for a limited amount of time thanks to exploits. According to both https://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597/ and https://forum.xda-developers.com/z5-compact/general/guide-how-to-root-z5c-painful-using-t3549388, it won't work on recent versions (7.1.1) so I need to downgrade. How can I do that? I imagine I need a tool to flash an old official rom: where am I to find an old official rom? How can I flash it without having an unlocked bootloader?
Backing up the TA partition really seems cumbersome. Is the loss of quality really noticeable on photos and videos? I find photos quite disappointing already and I fear it would get even worse.
On an unrelated topic, do you now of any way to backup SMS conversations as a simple file to import later on the same or different device? All I can find are applications that back up messages on a GMail account (no thanks) or any IMAP server (in what world is it simpler than an xml or simple text file ?).

Maybe you can translate this:
https://reraise.eu/2016/09/05/xperia-z5c-so-sicherst-du-die-ta-partition-teil-1

On an unrelated topic, do you now of any way to backup SMS conversations as a simple file to import later on the same or different device? All I can find are applications that back up messages on a GMail account (no thanks) or any IMAP server (in what world is it simpler than an xml or simple text file ?).
Click to expand...
Click to collapse
I'm using titanium backup for that.
(menu / backup data to xml)

@fetchaspade
Did you start your project? I would appreciate to take notes of your step. That's not only helping others, but also yourself once you have to do the steps again once.

LOS17.1 + recovery: how to create a full backup without root and without TWRP?

LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?

dvdram said:
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
Click to expand...
Click to collapse
Making a complete system backup requires root and/or custom recovery, period.
That is he way it is, you can't change that. There are no alternatives.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Making a complete system backup requires root and/or custom recovery, period.
Click to expand...
Click to collapse
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.

dvdram said:
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
Click to expand...
Click to collapse
Your reaction is a very butt-hurt reaction for a question that has been asked AND has been answered many times on this website and could have easily been found by you if you had searched.
Unless, of course, you did search and you did read where it has been answered before and, for whatever reason, you mistakenly thought that you would get a different answer just because you needed it to.
My point was, there is no way to access system partition or data partition without root. This forum is full of posts from other users asking the same thing, they all got the same answer, it can't be done without root or TWRP. Android just does not work that way, it has a linux kernel, which means, everything requires specific permissions and it is not in the best interests of OEM/carriers to allow access to /system and /data that easily and there is no way to give you "limited" access that only allows you to backup the /system and /data. There is only full permissions or none and they will not allow full permissions to the user.
That is entirely the whole point of people like us that find ways of rooting devices and installing custom recovery in the first place, because it is the ONLY way we can access /system and /data to make backups or modifications.
As for your thoughts of whether there will be a "new" way of making backups if adb and TWRP are no longer viable options....
Who knows? None of us will know until that time comes. We will all just have to wait and see if any takes the time to develop a new method.
Sent from my SM-S767VL using Tapatalk

dvdram said:
...
Last year Google announced that adb is very likely to be removed soon.
...
Click to expand...
Click to collapse
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.

jwoegerbauer said:
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
Click to expand...
Click to collapse
Yeah, I can't see Google completely removing adb, it is too valuable of a tool for development even for the stuff the carriers and their developers do on their end. Removing it would be like building cars and engines but completely disallowing the production or use of tools to assemble/disassemble the cars or engines.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
My point was, there is no way to access system partition or data partition without root.
Click to expand...
Click to collapse
I know that and I understand that. I've been using Linux on my private and on my working machines for at least 30 years now, and I know about permissions. And I also understand that there are good reasons for not rooting an Android device.
But that is not the point here.
I am and I always was talking about the recovery here, not the running LOS system, that you run every day to make any use of your phone at all. From my point of view, as a Linux user, booting into recovery is like taking a secondary boot device, eg a USB memory, and starting another Linux system that is completely independent of the one that my PC is running in normal cases. Using this secondary Linux I can do anything to the system and the hard drive that I want, regardless of permissions. I can re-install the boot manager, I can copy or delete files, I can repair the file system, and, most important: I can create images and snapshots of the system that will serve as an lifeline, a certain point in time that I can return to if it should become necessary.
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
Again: I am not talking (and I never was) about making root available in LOS.

@dvdram
...
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
....
Click to expand...
Click to collapse
Wondering why you don't ask this question to the developers of LineageOS?

jwoegerbauer said:
@dvdram
Wondering why you don't ask this question to the developers of LineageOS?
Click to expand...
Click to collapse
Silly me! I actually believed there would be developers reading this forum. How could I mistaken this statement on the starting page:
"XDA Developers was founded by developers, for developers."
I guess the word "developers" must have another meaning than I have always believed. Thank you for showing me my wrong!

[Magisk ROM][RMX2001][90HZ][Debloat]PpPmod[v1.1]

PpPmod for Realme UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About PpPmod
PpPmod is a port of the excellent xXx NoLimits magisk ROM for Oxygen OS. It's a systemless modification to the default Realme UI that allows the user to get much more out of his device than the default configuration allows.
But why a magisk ROM?
For two reasons:
1. Realme devices offer good price to performance ratio, but in many cases they lack a developer community around them to build those ROMs the users want.
2. Realme UI is not that bad honestly. It offers good performance, it's not too crazy aesthetically and its bloatware isn't baked deep into the system.
It's also a much safer way to modify Mediatek devices. As long as you've managed to root your phone, you are good to go. If something goes wrong, just wipe data and no harm, no foul.
Supported devices
While in theory, any Realme device with Realme UI v1, Android 10 and a full HD screen resolution should be compatible, the only two devices this has been tested on are a Realme 6 and a Realme 6 Pro. For the curious, i own the later.
Ok, but what does it do?
- Port of xXx NoLimits for Oxygen OS
- Fully systemless Realme UI ROM mod for magisk
- Designed to work with all phones that run RealmeUI v1, Android 10 on full HD screens, including MTK ones
- Fully configurable installation, every component is optional
- Includes comprehensive debloating options
- Optional build.prop tweaks
- Many kernel tweaks that can be adjusted and combined, in order to target different degrees of performance and battery life
- 90hz/120hz for ALL apps when the display is set to its high refresh rate
- GMS Doze included
- Ability to disable analytics
- Ability to disable wakelocks
- Can enable full screen gestures (swipe up) for 3rd party launchers
- Ability to set custom bootanimations from a built in list, or as a user selected bootanimation.zip
- Includes extra launchers, sounds and icons from popular device brands like Pixel and OnePlus
- Gcams for both Qualcomm and Mediatek devices are included (by Urnyx and onFire)
- Youtube Vanced, detached from the playstore so no pesky updates can override it
- Google Dialer and Contacts, both old and new versions
- Custom density modes
- Ability to systemize apps
In order to set your own bootanimation, place a bootanimation.zip inside /sdcard/PpPmod. You can also place a shutdown/restart animation named rbootanimation.zip there. Make sure that your bootanimations are 1080 pixels in width, or they won't work as you'd expect. If you set option CustomBootAnimation to 1 in PpP.profile, your animations will be used during start up and/or reboot, instead of the default ones. For more information about the PpPmod folder and the PpP.profile file go to Installation Instructions.
If you want to systemize an app for whatever reason, just place the apk inside /sdcard/PpPmod/apps., before flashing.
Concerning debloating there is a master switch you should toggle if you want your individual options to work. Set IndividualDebloatSelection to 1.
Installation Instructions
You will find detailed installation instructions along with download links on post #3
Screenshots
For screenshots, press here
Thanks to:
xXx
ahmed_radaideh
dustintinsley
gloeyisk
k1ks
andip71
linuxct
Mostafa Wael
mrRobinson
osm0sis
rufus.wilson
snowwolf725
topjohnwu
Zackptg5
ZaneZam
Kevin Saiza
Tytydraco
XDA:DevDB Information
PpPmod, ROM for the Realme 6
Contributors
FatherJony
ROM OS Version: Android 10
ROM Firmware Required: RealmeUI
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-09-14
Created 2020-09-03
Last Updated 2020-09-14

Changelog
Version 1.1
Fixed a bug where enabling HighRefreshRate had no effect on the first boot after installation.
Updated Google Dialer to the latest version.
Updated sqlite to the latest version.
Reworked kernel tweaks, with some inspiration from Ktweak by tytydraco.
New ReadAhead option added. This allows the user to disable, or set the readahead cache to a percentage of the device's memory. Default is 1 (cache disabled).
New CPUGovernorTweaks option added. When this is enabled, schedutil and interactive governor tunables are tweaked in order to increase performance. The default governor will also switch to schedutil or interactive depending on availability. Default is 1 (enabled).
Reworked CPUInputBoost option to make it more granular. You can now select from small, medium, high and max presets. For more info about them read the profile description.
Reworked CPUStuneBoost option to make it more granular. You can now select from small, medium, high and extreme presets. For more info about them read the profile description.

Installation
PpPmod allows for a fully customizable installation. The way this works is via a configuration file called PpP.profile. You will always be able to find the latest version of this file on this post. Make sure you edit this file on Notepad++ if you are opening it on Windows in order to preserve the Unix EOL format.
Requirements:
Realme UI v1 on Android 10 and display width of 1080 pixels
A working Magisk installation of v20.4 or higher
PpPmod should only be flashed via Magisk Manager
First time installation:
Place PpP.profile in /sdcard/PpPmod/ and edit it to personalize the installation to your liking
Flash the PpPmod zip via Magisk Manager
Reboot. Wait for at least a minute to let all installation options take effect.
Done
The first time you install, chances are that the PpPmod folder will not be in /sdcard, so you have to create it yourself. If you don't place PpP.profile there, the mod will be installed with the default options when you flash it and place the default PpP.profile inside /sdcard/PpPmod/.
Update to a newer version:
Open Magisk Manager and uninstall the previous version
Reboot
Wait for a couple of minutes after reboot as the uninstallation process can take some time
Install the newer version via Magisk Manager. Don't worry about changes to PpP.profile, they will be merged to your older version profile
Reboot. Wait for at least a minute to let all installation options take effect
Done
Uninstallation:
Press the waste bin icon next to the mod's name on the Magisk Manager
Reboot. Wait for a couple of minutes after reboot as the uninstallation process can take some time
Done
Downloads:
PpPmod v1.1
PpP.profile v2
PpPmod v1.0
PpP.profile v1

FAQ
Q: I just installed PpPmod and my phone has heated up and stutters, is this normal?
A: Yes, the installation process is fairly intense, and during the first boot following the installation, a lot of stuff happens in the background. Just let your phone settle for 10 minutes and it should be fine.
Q: I did all that and my phone still heats up, you liar!
A: Well, check your settings. PpPmod offers many options for tweaking, but not every one of them is suitable for all phones, or all usage patterns. In general, the higher performance settings may be fine for general usage and offer you a flagship like experience along with a high refresh rate, but will cause excessive heat and throttling during gaming.
For example, maybe a 12nm chipset shouldn't be pushed aggressively by enabling CPU boost options, especially if you game alot. You may gain a brief performance boost that will sooner or later be the cause of intense overheating, which will cause throttling, which will cause stutters. In short, try to be reasonable with your settings and expectations, PpPmod will not magically turn your mid range chipset into an SD865.
PpPmod is also not designed to work along with other magisk mods that adjust performance by altering kernel behavior. If you want to use such mods with it, try disabling every PpPmod performance setting, like:
KernelTweaks
LMK_RAM_Management
ReadAhead
DisablePeWq
DisableHotplugging
IncreaseMinGPUFreq
CPUGovernorTweaks
CPUStuneBoost
CPUInputBoost
The result may still not be ideal, but this is your best bet.
Q: My debloating options aren't working!
A: You forgot to set option IndividualDebloatSelection to 1.
Q: I think i found a bug, what is the best way to report it?
A: You should always include a detailed description of what triggers the bug, its effects, your specific phone model (including hardware characteristics like RAM and storage), firmware version, your PpP.profile and preferably a logcat from when the bug occurred.
Q: Can i be a beta tester? I swear i am awesome!
A: As long as you meet certain conditions, sure! The conditions are:
First and foremost, you must understand that beta testing doesn't mean early access. Most of the time you will have to do things that may be inconvenience you, or lead to loss of time and data (factory resets)
You should know at the very least how to setup and use adb
You should have A realme device with Android 10 and Realme UI v1
Q: Can i ask for a feature?
A: Sure, but keep in mind that PpPmod isn't primarily geared towards a specific device. So while device specific features are not out of the question, priority will be given to features that affect a range of devices.
Q: My phone isn't listed in supported devices, but it's a Realme device with Realme UI v1, Android 10 and a full HD resolution, should i give this a try?
A: Yes, as long as you don't mind resetting your data if something goes wrong, you should. That's exactly what i am trying to achieve with this mod. Normally, a new phone like for example the Realme X7 Pro would not have any options for customization on release, and may never get much due to the Mediatek soc. But PpPmod should work immediately, at least in theory. Even if there are some device specific issues i will do my best to fix them, and in the worst case scenario the phone is still safe from any permanent harm. Just reboot to recovery and reset data.
Q: PpPmod sucks and i wanna uninstall it. Must i also remove magisk?
A: NO, you don't have to and in fact you shouldn't if you don't have a reason unrelated to PpPmod, as magisk resides in your boot partition and thus unlike PpPmod, can mess with your device if you aren't careful.
Q: What does PpP mean?
A: No one knows fo sure. Some thik that it means Pro Plus Prime. Some other, less charitable persons claim it means PapaPowah instead. We may never know the truth.
Q: What do you plan for your next project?
A: Rewriting Android in Objective Cobol
Q: Is it true that you are actually a boomer?
A: Ok, that's enough. You guys have crossed the line and now i am forced to conclude this QA session.

FatherJony said:
Reserve
Click to expand...
Click to collapse
Good job dude

Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.

PapaSid26.12 said:
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
Click to expand...
Click to collapse
Yes, it works. But the whole point of a systemless mod is that you CAN'T brick your phone. Worst case you will just have to wipe data via recovery.

great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..

marvinvvh said:
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
Click to expand...
Click to collapse
I am sorry to hear that about the EU version. I thought that this would have been resolved by now. Unfortunately this is a magisk mod, thus it doesn't work without magisk.

Even after making changes in PpP.profile I'm getting default settings

Shanpatil said:
Even after making changes in PpP.profile I'm getting default settings
Click to expand...
Click to collapse
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.

FatherJony said:
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
Click to expand...
Click to collapse
Can u give some SS??

I bricked my phone...
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)

fraillesgeon said:
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
Click to expand...
Click to collapse
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.

FatherJony said:
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
Click to expand...
Click to collapse
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.

fraillesgeon said:
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
Click to expand...
Click to collapse
I did the same mistak. Howevre here is a solution.
If you have sd card, download latest ozip file from realme wessbite and place in root of sd card. Then insert it into your realme 6 and boot into recovery using power and vol down. After that install zip from total storage and install from sd card. Hopefullt it will be back.
On an another note there shall be some key combo for booting into fastboot mode

Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.

I'm back!
FatherJony said:
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
Click to expand...
Click to collapse
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!

Can you do the step by step process on how to flash it using magisk?

fraillesgeon said:
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Click to expand...
Click to collapse
Great news! I am really glad you were able to save your phone. As a rule, only use internal storage (/sdcard) for important operations.
I am looking forward to your impressions!

Better Mobile App

welcome