I am using TWRP, Oreo Beta, Magisk, BusyBox, Selinux to permissive on boot, and Xposed.
Something odd randomly started happening out of the blue.
No apps are showing inside other apps.
What I mean is, for example, Xposed shows installed libraries, Aptoide shows installed apps for update etc. All empty.
{
"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"
}
I have about 10 xposed modules downloaded and of course I have apps installed on my device it would be impossible for there not to be.
What I have tried:
-Disable xposed
-Disable and uninstall Magisk
-Remove busybox
-Change Selinux to Enforced
Nothing works.
EDIT: Ive flashed a version of TWRP that will now decrypt my data partition. This did not solve anything however.
Any suggestions or insights would be appreciated.
In the Xposed log I do see this:
01-28 17:54:04.468 E/Xposed ( 690): Unable to open /vendor/framework/oat/arm64 to prepare apps for Xposed: Permission denied
That seems important
Thanks
Related
Still locked and stock right now, but used ADB commands to enable wakelock detector lite (no root needed), noticed the following wakelocks pretty consistently:
OnePlus Launcher
*job*/com.android.launcher3/.quickpage.weather.WeatherService
UID
bluedroid_timer
The first seems to be related to the OnePlus launcher shelf weather service, which I don't even have enabled nor use. Not sure what the second is.
Any idea how to mitigate these without root or xposed?
Same problem (OxygenOS 2.3.7)
{
"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"
}
I dont know how fix this with root and oos 3.2.7
wojtek5379 said:
I dont know how fix this with root and oos 3.2.7
Click to expand...
Click to collapse
Freeze the stock launcher or uninstall it and use some other launcher.
U can try 2 turn off the weather in shelf. For me the problem was fixed than (when i was using OOS 3.x.x).
About the bluedroid_timer wakelock, maybe the following thread will be useful:
http://forum.xda-developers.com/oneplus-3/help/deep-sleep-vs-awake-screen-off-t3494097/page1
I just want to share, for who know V4A and for anyone who not. Now the app works in Marshmallow
Quick guide (What I did to make it work)
-Need:
Busybox (Root)
SE Linux Mod Changer or Terminal Emulator. Is up to you, I used the Terminal
Viper4Android v2.5.0.5 - https://forum.xda-developers.com/showthread.php?t=2191223
-Install Busybox, enter into the app and Install.
- a_ SE LinuxModChanger: Install, in the app tap "Permissive"
b_ Terminal: Install and type
su
getenforce
setenforce 0
Click to expand...
Click to collapse
**Su: gain Root access//Getenforce: check the status//Setenforce: Change the Mode (0: Permissive\\1:Enforcing)
{
"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"
}
-Install V4A, I installed as a system app.
-Open and Install the driver, Reboot.
To see if it works check "Driver Status" in the app:
*(Processing show "Yes", only playing a song)
So I own a LeEco Le s3 x626 and I've been trying to flash Lineage OS 7.1.2.
The rom flashes fine but I want to use Magisk instead of SU. The rom flashes supersu by default and I let that happen. I've tried many methods of flashing original boot image and Magisk then using boot image verifier but it just never boots up and goes in a bootloop.
I am wondering if replacing the supersu zip with a Magisk zip will work since it flashes supersu on boot but if I do that it will instead flash Magisk. Will that work?
Screenshots:
{
"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"
}
That is the script in the Aroma installer folder
That is the location of the supersu file
Link to rom: please pm
Please ask if you don't understand my English
Umm... I don't understand what you're saying, are you trying to root your Android device using Magisk?
I make bloat magisk module for s20 port because bloat zip cant be flashed with small system partition. This module can allows you install all bloat as system but data storage consumed. Must be. you have large space of data storage and expect slight impact on your data partition. instead of expanding your system partition this is much better.
{
"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"
}
All files inside this module is from bloat.zip of Astrako i just compiled it as magisk module.
iNSTALLATION:
Just install in magisk as module.
You can also add or remove bloats by your own needs.
Here: root/data/adb/modules/samsung.bloat/system/you can see the app and priv-app here.
Download link:
S20Bloat_magisk1.0.zip
How to download it?
Please accept me to access download data
yulio ch said:
How to download it?
Please accept me to access download data
Click to expand...
Click to collapse
Sorry link updated.
Thanks for update the link
{
"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"
}
If you are running stock and don't want to root you device, this bash script will "uninstall" with the pm uninstall --user 0 trick all the bloatware from samsung that is never used.
By default removes the samsung store, all the knox related stuff and all the google bloatware minus the playstore and the google services.
Basically a "LineageOS with gapps nano" experience. It also purges all the user apps installed by default, so this is meant to be run after a factory reset.
TL;DR:
Do a factory reset, dont plug in your sim and dont enable wifi. Setup everything without a net connection and enable adb. Then run the script (needs adb installed). It should work on Linux and OSX, maybe Windows with WSL?
Proof:
(There are some apps that I usually use, i didnt make any screenshot after debloating)