Database Develop

Fix dec 2016/jan 2017: Snapchat on rooted android device running xposed.

POST IS UPDATED REGULARLY.
LINK 1 - Parallel Space: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl&hl=en[/URL][/URL]
LINK 2 - Parallel Space 64-Bit Support: https://play.google.com/store/apps/details?id=com.lbe.parallel.intl.arm64&hl=en[/URL][/URL]
Salutations. (That means 'Hello').
NOTE: For those who are interested, I will include background information about how I came to the solution. All that other jazz too. First and foremost however; the fix!
SOLUTION:
Right at the top of the post, you will find two links. This being a new account and all (don't ask), until I create 10 posts I cannot include any outside links. So once I've done so, I will update the post.
STEP **: So at the top of the post, there are clearly two links. 64-Bit Android devices are becoming increasingly common. This architecture may pose a few problems. give the application framework. Should you own a 64-Bit device, I recommend installing this application too (LINK 2). This will theoretically prevent any obstacles.
Pre-requisite(s): Make sure you have the 'Snapchat' application installed. It is recommended to have installed the latest update from the Google Play Store.
STEP ONE: Download the application appended to LINK 1. This is called Parallel Space. You might recognize the name (its creators are the same who allow you to seamlessly virtualize Windows OS on Mac OS).
STEP TWO: Launch the application.
STEP THREE: You should be prompted with a grid-like interface. Here you will be greeted with a range of familiar icons. In the top right corner of each icon, you will notice a blue check-mark. Make sure that there is one next to the 'Snapchat' icon. This will ensure that the app is 'cloned'.
STEP FOUR: In the 'Parallel Space' app, tap on the 'Snapchat' icon. This will launch the application.
STEP FIVE: From here it is pretty self-explanatory. You are greeted by the standard 'Snapchat' interface. Tap on 'Log In'. Then proceed to do so.
STEP SIX: 'Snapchat' should be functioning as normal.
STEP SEVEN (BONUS): During testing, this worked on and off. --
Remain logged-in to the 'cloned' 'Snapchat' application within the 'Parallel Space' application.
Then proceed to launch the stock 'Snapchat' application.
Next attempt to 'Log-In'.
Should this operation be successful, you are then free to uninstall 'Parallel Space' and any related assets from your device.
HOWEVER, I personally do not recommend this. When logging out or updating the 'Snapchat' application, errors may be re-encountered.
Instead, I recommend that if possible, do use the stock application, but leave 'Parallel Space' installed. Using the stock app will improve efficiency and reduce the load on system resources. But keeping the 'Parallel Space' application on the device, well; you get the point.
Enjoy the fix! If it does not work, please let me know [Device Name and Model No.]. I've tested on various devices, succeeded every-time. Do keep in mind that this is a loop-hole, so may be patched in future or not work at all for some devices.
Background (Because I know someone will ask): The idea came to mind while using a LG G5 as a daily driver. I had tested every custom ROM available for the device. The problem was that with custom ROM's, there was always an issue, Malfunctioning sensors, camera's not working persistently, etc , etc.
The G5's stock ROM left me wanting more. The overbearing interface made it a living hell. Plus, the device just being rooted (NO XPOSED) meant that 'Snapchat' did not work. I looked for fixes for a time, but could not find any.
Development of ROM's for the device is on-going, and I am an active member. But I just couldn't handle not being able to use the camera (one of the device's best features) and no accelerator, screen-rotation, etc. So I went back to stock again. Do keep in mind that I was alternating/dual-booting between custom and stock ROM's just because of the camera; mainly.
This most recent time. instead of flashing stock MM, I flashed stock N for the G5. For 850, it has been officially released in some countries, and a manual flash via TWRP was a peice of cake.
This update is a lot better. I am running Nova Launcher again. So it makes it look a little better. Themes have also been improved. I am using an in-built dark one which makes the device look a lot better aesthetically. Additionally, I'm rocking a white carbon-fibre skin on the exterior; improving grip and overall security. The only issue was again, no 'Snapchat'.
After a few days, I had the idea to attempt this. I tested my theory and it worked! That's it.
Please do keep in mind that I will update this post as often as possible.
P.S This was tested just after updating to the latest version of 'Snapchat' which was a significant update. It included Shazam, Groups, etc. So you know, pretty cool that it worked.

Did not work on Google Nexus 5 running Android 7.1.1. Still gives error message saying that I can't connect to the server.

Same here, not working on freshly reinstalled and rooted 7.1.1 Nexus 5x. No Xposed, no nothing. I get the infuriating "temporarily failed" message in both cloned and regular modes.

It didn't worked. S7 edge exynos (6.0.1)

Holyphe said:
It didn't worked. S7 edge exynos (6.0.1)
Click to expand...
Click to collapse
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.

hot_potato said:
I'm pretty sure if you get Xposed framework, there's a module that allows you to hide root from apps. Problem is that there is no Xposed framework for Android 7 yet. Hope this helps.
Click to expand...
Click to collapse
Whats the name of it?

Holyphe said:
Whats the name of it?
Click to expand...
Click to collapse
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.

AndroidFL said:
I personally tried the module on cm13 but it doesnt work for me. I think that somehow snapchat knows when you use xposed too.
The thing is that on aosp roms with root already build in sometimes snapchat do not catch it but if you have xposed, no way you can get in. For that freaky snapchat app here is what i did: install any rom, if if had root build in i then install su uninstaller zip with twrp then log in into snapchat and after that, rooting with super su zip again. The catch is that once you log out of the app and attempt to log in again, you cant get in and you have to repeat the proccess. It's annoying as hell!!! They need to disable the security check, if people want to cheat che system somehow they will, so whats the point. Also there are much more tweaks for jailbroken iphones and they have no problem with it .
Sorry for the rant here buqt im super frustrated.
Click to expand...
Click to collapse
That's the only solution I've seen working so far. unroot and reroot. Root cloak doesn't work, parallel doesn't work. I should've logged in before rooting and I hate to do it again.

Any work arounds yet? I've seen ppl do it using titanium backup but I'm not sure if that works. Can anybody help?

Samsung s5 G900v Not working
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.

Dukeboyty said:
I have been searching and searching and still haven't found a way to sign into snapcat. It took me about 6 months to be able to find out how to root my phone.
Click to expand...
Click to collapse
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.

Okay. I will try this on monday and will let youknow how it goes. Right now I decided to unroot to use snapchat, so I didn't loose my streaks. Thanks in advane will let you know how it goes.

immorality said:
Well todays your lucky day.
Step one turn off xposed.
Step two reboot
Step three sign into snapchat
Step four turn xposed back on
Step five reboot
You should be able to snap now.
Click to expand...
Click to collapse
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!

Dukeboyty said:
Now that i think of it, when i uninstalled xposed it didn't work still. but after i "fully unrooted" through Super su and tried to sign in it worked. so it has to do with root or maybe both but the xposed didnt work for me. Thanks even though it didn't/wouldn't have worked for me!
Click to expand...
Click to collapse
Snapchat detects xposed framework.
Though at a time they did do root they since moved to blocking xposed due to the security concerns with money and also privacy of the user.
Though with certain phones and ect that could be the case I am using a s5 and have no issues.

just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)

ahmedsasker said:
just install magisk and systemless xposed and turn on magisk hide in magisk manager now snapchat won't detect root
then when u wanna log in just turn off xposed in xposed installer and reboot "it won't take time booting optimizing app when reactivated now" so reboot is easy
and u can have multiple accounts by backing up snapchat with titanium backup and don't ever log out just wibe its data and when u want to relog just restore the backup
and if u want to have multiple accounts access just patch the titanium backup with luckypatcher and have multiple backups (accounts)
Click to expand...
Click to collapse
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?

Fnn.09 said:
Can u make a instructions how to do it step by step? How can i turn off xposed in xposed installer? It also works when SuperSu is installed or i have to unistall it first?
Click to expand...
Click to collapse
make a nandroid backup if u want
1- full unroot by opening supersu and going to settings and press Full unroot and wait till it finishes and restart
2- download xposed uninstaller if u have xposed framework installed and flash it
3- install magisk manager from playstore
4- download and flash last magisk which is (12v) now from : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
5- flash magisk v12.0 which you downloaded now your phone will have systemless root
6- go into magisk manager app and go to settings and toggle "Magisk Hide" (ON) and restart now your root is hidden
7- remove your current xposed app and install this one : https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
8- flash systemless xposed : https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
9- reboot and go to the xposed installer app and toggle the xposed off or on as you want when u restart it won't take time optimizing apps like before so fast now
your root is hidden now but xposed is not but you can disable it and enable it easily

Instead of using Parallel Space (which I believe to be insecure) use Island to clone your apps. It's a little more advanced to setup, but it's a lot more secure. It works for rooted and non-rooted devices. On the 1st page of the thread, it explains how Parallel Space and others repack the apk file locally, which is dangerous. https://forum.xda-developers.com/android/apps-games/closed-beta-test-incoming-companion-app-t3366295
Island never repack apk file locally, which is inherently insecure for users, since all your app data (including password input) are technically in the hand of MoboClean. (The same applies to other similar tools, e.g. LBE Parallel Space)
Instead, Island takes advantage of the underlying mechanism used by "Android for Work". This ensures that all your apps run natively in Android system and their data are securely stored in internal location of Android which is never accessible by Island. It has the same level of security as "Android for Work".
Click to expand...
Click to collapse
Be sure to read the disclaimer!!! The app is still only available in closed beta at the time of writing this, and could possibly cause you're device to bootloop or even possibly brick it, but root, xposed, or other modifications {in my opinion) has a higher chance of bootloops or bricking your device.
You follow the same steps in island to clone snapchat as you would in Parallel Space to login to snapchat. It might be possible to use the play store inside island to download snapchat inside island and login that way. I can't remember exactly how it works. I believe that island is a good way to test apps in a "sandbox environment" to keep the data excluded, safe and secure from the regular apps that you have installed outside of island.
I use Magisk now which bypasses SafetyNet which is what snapchat uses to "block access" to modified/rooted devices.
Probably the easiest method is to download Casper which is an alternative snapchat client that allows you to save snaps, and many other features that the official snapchat client can't do. Find Casper at www.casper.io
FYI Netflix has started to change how they do things as well by hiding the app's play store page from devices that have been modified or rooted, but it's still possible to simply sideload Netflix for now.

Magisk keeps uninstalling

Hi.
I have a HTC 10 running LineageOS 14.1. In the past 4 days I have had to re install Magisk 16.3 at least 4 times daily as it keeps uninstalling itself. I have always had this issue with Magisk but it appears to have gotten worse instead of being solved.
Any suggestions as to what I can do to improve the situation?

It's likely not uninstalling itself, but something is killing the daemon. If you figure out what (aggressive battery saving might be a culprit), it would be good...

Magisk manager tells me that "Magisk is not installed" and that version 16.3 is available to install. However when I reboot it's there again so looks like you're right. Guess I'll have to have a look for what's causing it.. Thanks.

This is happening to me on OOS open beta 6. It's not really uninstalled because all my modules are present, but root does not work and the Magisk app is gone from my apps in settings and app drawer. I have to go into recovery and reflash it. This is happening on reboots at random.

it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.

manan001 said:
it seems after the april update on stock orea 8.0 MIA1 Xiaomi this issues has become frequant.
Click to expand...
Click to collapse
Some users are experiencing this, and I suspect it's a MagiskHide thing. You could help investigating by doing two things:
Install a beta release (use v16.3 because of the 64-bit issue with v16.4), and provide the magisk_debug.log after Magisk "uninstalls itself". You might have to grab it from recovery, since you're loosing root.
Disable MagiskHide and let it be disabled for a while to see if the issue still occurs (to confirm if it's MagiskHide or not).

Can be caused by Greenify?

I have the same problem magisk uninstalled after installing sdw hide root & sdw mock location through xposed installer

same issue but xposed included.

LG G6 Rootet Oreo Stock debloatet Magisk 17.2. same problem. deinstalling itself

kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
I installed greenify and this happened......probably it is the cause

m1l4droid said:
@Didgeridoohan adding Magisk as an exception in the MIUI battery saver didn't work. Not sure what to do.
Click to expand...
Click to collapse
Me neither...
There's a relatively active GitHub issue open about this issue, but there's been nothing definitive found about it yet.
The reports about this issue are so scattered, lacking in details and undefined that it's hard to say anything either way. Some users have success if disabling MagiskHide, some not so much, etc.
Someone that is experiencing the issue need to figure out what it's about. Until then there's not much to do...

It causes because of Busybox... uninstall busybox module fixed the problem for me

Didgeridoohan said:
... but something is killing the daemon. If you figure out...
Click to expand...
Click to collapse
Definition for daemon: https://www.linux.org/threads/android-services-and-daemons.10847/
How can one figure out?

kerpert said:
Can be caused by Greenify?
Click to expand...
Click to collapse
Nope. I've uninstalled greenify and magisk stopped anyway. So it's not related to greenify.

dan60 said:
How can one figure out?
Click to expand...
Click to collapse
Possibly by saving logs at the moment the daemon is killed off. Can be tricky...
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.

Didgeridoohan said:
If you don't want to, or don't have the skill to figure that out, you could try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.

Geofferey said:
I should probably state that the module was made using a 17 template so min magisk ver. 17. There's really no telling what's killing the daemon. Also I note in the thread if magiskd is killed manually my module doesn't work. Don't know what all that is about... I've been playing around trying to kill it off manually and restart with no success using SSH as my root access. I don't expect this to work for everyone because I don't know how their daemon is dying. For some odd reason the module works for me when my daemon dies randomly so I'm happy with that. BTW I included logging which prints time and date script detects magisk not running and if it successfully restarted. The logs located in /data/local/tmp/magiskd-helper.log. I also have .pid in /data/local/run. Create dir if non-existent and . pid should be there.
Click to expand...
Click to collapse
You could let the script also dump the current logcat buffer to a file (or cyclically save logcat to a file set to a certain size) when it detects the Magisk daemon not running. Might show why it dies...

Didgeridoohan said:
... try this meanwhile:
https://forum.xda-developers.com/apps/magisk/magisk-installed-workaround-t3908748
Would be interesting to know if it works for everyone.
Click to expand...
Click to collapse
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.

dan60 said:
Great initiative. I installed it yesterday, but sadly my oreo moto z play got unrooted again (same as if no Magiskd-helper had been flashed). But thanks for trying to help.
Click to expand...
Click to collapse
When you reboot does magisk come back? Could you post output of /data/local/magiskd-helper.log? I would like to see if it even attempted.

N960U1 and could not update software. Need help.

Hi everyone,
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945

NahteT said:
So straight into the problem: I got my phone around the end of November 2018, which was when the Security Patch for that month came out. After that last update, I checked manually every month to see if there was another one. But after 12/14/2018, which was the last time I was able to check for updates, the phone would keep saying that it failed to download update, and a network or server error has occurred. I desperately need help.
View attachment 4685945
Click to expand...
Click to collapse
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch

KOLIOSIS said:
Boot into recovery & wipe the cache partition,reboot to system & then try again.
If that doesn't help,try using Samsung Smart Switch on your PC to update.
https://www.samsung.com/us/support/owners/app/smart-switch
Click to expand...
Click to collapse
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?

NahteT said:
Sadly, none of the two options worked for me. I have also tried booting into Safe mode, but the same problem would occur again. What else can I do, other than a factory reset?
Click to expand...
Click to collapse
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.

KOLIOSIS said:
The only thing I can think of ATM is find the system apps responsible for system updates (two,I believe) wipe the cache & data ,if possible,from both,& try again.
If you are running an unadulterated version of the firmware that shipped with the phone,I'm stumped as to why you cannot update.
If you have any disabled apps perhaps enable them to rule out anything that might be causing this.
Click to expand...
Click to collapse
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.

NahteT said:
Do you have to rely on ADB to wipe the cache and data? I found the two system apps that are used for Software Update (com.sec.android.soagent , com.wssyncmldm), but I can't seem to find the command code to do that.
Click to expand...
Click to collapse
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.

KOLIOSIS said:
No,just navigate to Settings > Apps & tap on the 3-dot menu in the corner,select to view all/system apps & wipe each software update app.
If the buttons are greyed-out,then of course that can't be done.
Click to expand...
Click to collapse
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.

NahteT said:
I have just tried wiping the cache and data for the system apps, and also wipe the cache partition of the phone, yet nothing changes. I think what happened was that I accidentally disabled the two system packages for Software Update through ADB before this problem occurs, and now re-enabling them would have no effect.
Click to expand...
Click to collapse
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.

KOLIOSIS said:
You can't re-enable apps that have been disabled by ADB w/o a factory reset.
In the future, you may want to consider using one of the Package Disabling apps that are available to avoid situations like this.
Click to expand...
Click to collapse
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?

NahteT said:
If that's the case, then it wouldn't make sense that I were able to re-enable quite a lot of apps disabled by ADB. Or is this a special case where the crucial system apps that when disabled, they can't be re-enabled again?
Click to expand...
Click to collapse
That would be my guess, otherwise, you should be able to update.

KOLIOSIS said:
That would be my guess, otherwise, you should be able to update.
Click to expand...
Click to collapse
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.

NahteT said:
Okay, I'll do a factory reset to see if this would solve the problem. Thanks for your help.
Click to expand...
Click to collapse
Please keep us posted on your outcome.

KOLIOSIS said:
Please keep us posted on your outcome.
Click to expand...
Click to collapse
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.

NahteT said:
So problem is solved: I did a factory reset, and the software update works just fine. I guess that the assumption about disabling crucial system apps caused them to not become re-enabled again must be right. Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware. Thank you once again, I appreciate your help a lot.
Click to expand...
Click to collapse
No problem, glad to be of help.
As for the ADB Removal & re-install of apps, I 1st heard about it from this XDA article/how-to:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/amp/
As it mentions the inability to re-install/re-enable apks, I just took their word for it & never uninstalled anything that I might need at some point.
That's why I like using package disablers, it's easily reversible without a reset.
Regardless, a factory reset isn't the end of the world, just a PITA at most.
Glad you got things going again.

Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.

NahteT said:
Well I learned my lesson now - not to abuse ADB too much when it comes to bloatware..
Click to expand...
Click to collapse
Glad the problem was solved. My view is that concern with bloatware is a vestige of the past. On present-day phones, I'd guess that less than 0.1% of storage, memory, processor time, or battery charge are tied up with bloatware apps. So trying to identify and disable them won't have any noticeable benefit, and may well break things.

NahteT said:
Sorry to bother you again, but now I have problems with package disablers. I'm currently using a package disabler app, and it requires Device Owner App permission in order to disable bloatware apps, which can easily be done through ADB.
adb shell dpm set-device-owner com.pdp.deviceowner/.receivers.AdminReceiver
However, upon doing this, the lock screen of the phone will now show "This device is managed by your organization" at the bottom of the screen, and I don't feel comfortable about it. I have tried to uninstall the package disabler after done removing bloatware, but it wouldn't let me because the app is now a device administrator. I kind of screwed up myself after using the uninstall option inside the app, without knowing that it has completely uninstalled all the bloatware I disabled (instead of uninstalling the app itself), and caused my phone to stuck in boot loop, but I managed to fix that by another factory reset.
What kind of ADB command do I need so I can remove Device Owner App from the package disabler after I'm done disabling the bloatware?? (this is so ironic: disable a package disabler). Very sorry to disturb you again.
Click to expand...
Click to collapse
The message is just a generic one (as used when you grant admin rights for work e-mail,for example).
What it comes down to is if you trust the package disabler app & its developer,as I don't think there is any way to revoke the permission as long as you are using it to disable any apps at all.
I may be wrong on that,but,it seems like that's what's going on here.
If this still bothers you,then the next best solution is to continue using the disabling app long enough to determine which apps you are 100% certain are not needed/wanted.
Make a list & then switch to the ADB method.
That way,you get the admin rights to the disabler app off of your phone,but,you do give up the flexibility of the app as well.
The only way I see around your predicament is gaining root access & using the disabler app w/o admin rights,or,another app such as SD Maid Pro or Titanium Backup Pro.

Debloated stock -without Google apps- for best performance/privacy

One word ahead: I am a huge fan of Custom Rom (LOS). Nevertheless some feature will be missed (volte) and performance might be not perfect (camera, dolby) due to proprietary firmware.
On the other hand I like to keep away from data collecting companies as google.
Isn't than a rooted and debloated stock image with microG instead of Gapps the best possible option? I did this once for an older Samsung and results was fine. But there is one thing I don't know: How it will act on updates. I don't want to miss security updates.
Any ideas? Or is it a bad idea at all? Curious to your feedback
I will extend this posts. Not only writing a step by step howto, but also explain the ideas behind. Maybe also some steps aside, mistakes I did.
So for the first steps look https://forum.xda-developers.com/t/...est-performance-privacy.4240057/post-84573619
EDIT Mai 1st 2021:
I get for some time a second phone and did some experiments. From what I see new - there is no real need to go the long, long way to root it. Even on a stock RAM you get get back control over your data!
The gapps are less important than I ever thought. If you get curious, just switch over here to get more information:
https://forum.xda-developers.com/t/...est-performance-privacy.4240057/post-84909643
(To avoid misunderstandings: I will not provide a ROM. There are some steps to go with existing stock ROM - as only this gives you full features.)

Isn't than a rooted and debloated stock image with microG instead of Gapps the best possible option?
Click to expand...
Click to collapse
I will assume you are comparing it with the latest LOS available.
Privacy-wise? Not really. Even if you remove GApps from the stock rom, Samsung will still collect data. You can limit that by:
1. Not using Samsung Account/Pay/Pass (as on why, read privacy policy)
2. Removing "com.hiya.star", which collects your location, tho it will break the "Places" feature in the Phone app.
3. Replacing Samsung Keyboard with an open-source alternative or disabling the autocorrect feature as it sends corrected texts to Samsung.
4. Not using Samsung Weather app/widget (as on why, read privacy policy)
After that and using some F-Droid apps I would say you have a pretty decent privacy.
Performace-wise? Absolutely. The battery life is a lot better compared to AOSP ROMs and thats not even taking into account that OneUI has the Ultra Power Saving Mode. The camera is miles ahead too and of course, VoLTE actually works.
How it will act on updates. I don't want to miss security updates.
Click to expand...
Click to collapse
I have tested that. If its just a security update, then it will install flawlessly. If its a feature update, some bloatware and Gapps may reinstall. I haven't experienced any update failing, but that may change in the future.
Any ideas? Or is it a bad idea at all? Curious to your feedback
Click to expand...
Click to collapse
If you really care about privacy, but dont want to miss out on features, then go ahead with debloating and degoogling the stock rom. Just note that some problems with compatibility and some rare random crashes may occur.

Retrecd said:
...
1. Not using Samsung Account/Pay/Pass (as on why, read privacy policy)
2. Removing "com.hiya.star", which collects your location, tho it will break the "Places" feature in the Phone app.
3. Replacing Samsung Keyboard with an open-source alternative or disabling the autocorrect feature as it sends corrected texts to Samsung.
4. Not using Samsung Weather app/widget (as on why, read privacy policy)
After that and using some F-Droid apps I would say you have a pretty decent privacy.
Click to expand...
Click to collapse
Sure, that was the ideas to remove as much of Google/Samsung stuff as possible and also use AFWall to limit data transfer. I am using FDroid already, there are good tools, respecting privacy.
So you went already same approach? There is already a thread about debloating, but I think what I want to do is even behind that. If you like, you can share more details. I would like create some kind of a howto ...

starbright_ said:
Sure, that was the ideas to remove as much of Google/Samsung stuff as possible and also use AFWall to limit data transfer. I am using FDroid already, there are good tools, respecting privacy.
So you went already same approach? There is already a thread about debloating, but I think what I want to do is even behind that. If you like, you can share more details. I would like create some kind of a howto ...
Click to expand...
Click to collapse
Here is an article on using ADB to remove bloatware: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Now here is a list of bloatware on the S10, remove it the way showcased in the article: https://forum.xda-developers.com/t/galaxy-s10-s10-debloat-bloatware-removal-list.3912073/
The list is a bit older, but most of the bloatware is still present in the latest version.
The same way you removed the bloatware, you remove the Gapps. Remove the following core Google packages:
Code:
com.google.android.gsf
com.android.vending
com.google.android.gms
If you want to remove more packages that aren't listen in the article install the "App Inspector" from Google Play or any APK site and find out the names of the packages.

Please read and share your ideas. I am sure that we only together can create the best possible solution. Maybe you know othere ways/apps to solve a problem. As of now I share my point of view.
My hope is, that at the end of this to have an "howto" covering as many aspects as required for this.
First thing nevertheless is install TWRP/Magisk, which seems to be more tricky than usual.
While you can debloat your ROM without root, there are imho 3 reasons for doing that:
microG needs be installed as a system-app to have working location service (get your location by GPS or by offline database)
you will have problems to install a firewall and adblocker. There are solution with don't need root (Netguard and Blockada), but both base on a "virtual" VPN connection and you can have only one at a time. So you do have either a Firewall or an AdBlocker, but not both.
The way of create and restore backups are much better with root. I can recommend TWRP itself for a general backup and migrate for apps/settings.
For those like me, coming from unrooted stock fw the recommendation is to
root with Magisk - details here
flash the TWRP - details here
spoofing the signature for usage of microG instead of playservices
install microG and "friends"
debloat stock ROM
migrate data from old to new device

starbright_ said:
First thing nevertheless is install TWRP/Magisk, which seems to be more tricky than usual.
Click to expand...
Click to collapse
Tricky indeed and even more tricky is installing updates. Once you know the procedure it's ok, but it is still a major hassle compared to a stock OTA update.

here
jelbo said:
Tricky indeed and even more tricky is installing updates. Once you know the procedure it's ok, but it is still a major hassle compared to a stock OTA update.
Click to expand...
Click to collapse
Sure, I am aware of that. I just read about it. But there is no other way except you are happy with stock. First time is always a nightmare, but I hope once get used to it.

Retrecd said:
Here is an article on using ADB to remove bloatware: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
Now here is a list of bloatware on the S10, remove it the way showcased in the article: https://forum.xda-developers.com/t/galaxy-s10-s10-debloat-bloatware-removal-list.3912073/
The list is a bit older, but most of the bloatware is still present in the latest version.
The same way you removed the bloatware, you remove the Gapps. Remove the following core Google packages:
Code:
com.google.android.gsf
com.android.vending
com.google.android.gms
If you want to remove more packages that aren't listen in the article install the "App Inspector" from Google Play or any APK site and find out the names of the packages.
Click to expand...
Click to collapse
How did you managed that switch from Gapps to microG? I assume if you delete Gapps without MicroG installed you will get lot of problems.
How did you manage to spoof Stock Rom? Are you on 11?

Hi all. Very interesting conversation. Has someone successfully used microG on stock rom on a daily usage? In my past experience, using microG without signature spoofing is making a lot of apps not working properly...

lp35 said:
Hi all. Very interesting conversation. Has someone successfully used microG on stock rom on a daily usage? In my past experience, using microG without signature spoofing is making a lot of apps not working properly...
Click to expand...
Click to collapse
I think spoofing is a must have. I just evaluate how this can be done.
With Android 11 it is more difficult. I found that one (but not sure whether signature spoofing works):
https://forum.xda-developers.com/t/module-smali-patcher-7-3.3680053
this one:
https://forum.xda-developers.com/t/signature-spoofing-on-unsuported-android-11-r-roms.4214143/
or via NanoDroidPatcher
https://forum.xda-developers.com/t/...7-microg-pseudo-debloat-f-droid-apps.3584928/
It says:
11.0 / SDK 30 (R)
Patcher does not work from TWRP
Patcher works from Magisk if your ROM's services.jar already contains classes.dex
I checked that and /service/framework/service.jar contains that classes.dex
So I give this a try, downloaded the patcher and started it out of Magisk. Log looks ok so far. It requires reboot.
The problem with enabling Magisk is - you have to boot with "recovery" mode - and not sure, it fails several time (although USB is plugged) or phone reboots again and than Magisk is disabled - while booting into TWRP still works.
So my guess is: This causes some problem.

Step 3) - Spoofing
Have been successful:
I followed that thread:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
But I just created a spoof_AVDapi30.zip. My thinking just flashing that one for spoofing seems to be wrong. Also flashing both: spoof and microG_AVD....
So what I did was flashing out of Magsik (Module install out of memory) NanoDroid-microG-23.1.2.20210117.zip and followed by spoof_AVDapi30.zip.
Power off. And take care you boot with Power + Vol+ + Bixby + USB Cable pressed until you see the splash-screen.

I really hope stock + MicroG takes off!

It is already. I started debloating - that is another step. See this thread:
Debloating S10e
I am still in testing phase and I would like to see once an FW-update via OTA will happen. Curious what will happen with my system.

starbright_ said:
It is already. I started debloating - that is another step. See this thread:
Debloating S10e
I am still in testing phase and I would like to see once an FW-update via OTA will happen. Curious what will happen with my system.
Click to expand...
Click to collapse
Amazing! Keep us posted!

Debloating is done.
Final step is takeover of my previous installation. I do that with the tool/app migrate. That works rather fine.
I am not using the special sections to export contacts, SMS ...
Contacts will be exported from the app itself and than imported in new device.

Is this dead? Hehe

No it is working. Have you tried that?
I couldn't deinstall com.samsung.android.kgclient and blocking its UID (with awfall) causes some battery drain. Maybe I have to live with not blocking this.
Anyhow, I am wondering whether debloating is required at all. Cutting the connection to Ethernet (to not talk "home") might be enough.
I don't not have enough understanding of what will be better: remove or just block.
A removed app might not spend time on connecting servers again and again, while a missed service can cause trouble if you don't expect that.
Probably it is best to uninstall apps you are really sure there are no dependencies to others and block the others-

starbright_ said:
Step 3) - Spoofing
Have been successful:
I followed that thread:
Signature Spoofing on unsuported Android 11 (R) Roms
How to get Signature Spoofing working on Android 11 (R) Roms that have no support for Signature Spoofing? In my Case here I use a Samsung Galaxy S8 with an unofficial LineageOS 18.1 (Android 11) by stricted I use TWRP recovery but this should...
forum.xda-developers.com
But I just created a spoof_AVDapi30.zip. My thinking just flashing that one for spoofing seems to be wrong. Also flashing both: spoof and microG_AVD....
So what I did was flashing out of Magsik (Module install out of memory) NanoDroid-microG-23.1.2.20210117.zip and followed by spoof_AVDapi30.zip.
Power off. And take care you boot with Power + Vol+ + Bixby + USB Cable pressed until you see the splash-screen.
Click to expand...
Click to collapse
So just install those inside of magisk and reboot? I'll give it a shot.

Dead thread, I see.

steventorres said:
Dead thread, I see.
Click to expand...
Click to collapse
What are you continuously posting about dead thread? Any question or any feedback? Strange. It is is all set and done. What do you expect?
@VenfefulRat:
This wasn't a real question, right. It was stated to do it out of magsik. It would be great to have some feedback.
@All: A forum lives from reading (to gain knowlegde ) and posting (sharing experience, ask questions, give feedback). If someone ask and he gets answer I would expect a feedback or at least a like (as a sign it has been read). Otherwise people stop posting and the only left here are those who ask or feed the troll.

G9+ & Adaway: Ads show up

I have two G9+ phones, both rooted with Adaway installed. One has the stock ROM (Android 10) & the other has LineageOS 18.1.
On the phone with Lineage there are no ads when running a particular game. The same version of the game on Moto Android 10 has ads.
There is some app I don't understand called Moto GameTime that appeared when I started the game but I have disabled it. (I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Still, Google ads appear with the stock ROM despite having Adaway.
Everything looked ok in Adaway. It tells me its three sources are up to date. When I try to reload & reinstall hosts from those sources I get an error: "Unable to copy hosts file to /system partition. Please check Magisk systemless module is enabled the reboot." (Magisk Manager shows Magisk 23.0 is installed.)
Something is causing problems that seem to involve lack of access to the /system partition. I don't know if that is related to the appearance of ads on the stock ROM, but any thoughts? How can I fix this?

As I've stimulated no response here, I took the ugly step of wiping the phone, flashing the experimental LineageOS and restoring everything from backup (not a fully successful process because the data for certain apps was not backed up by Super Backup & Restore).
At least there are now no ads getting through onto the phone.

The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w. There is a workaround for it (currently in development stages). It's a flash able zip script that dumps the super partition "fixes" it and flashes it back. Your phone must have the bootloader unlocked and be rooted for it to work. It currently works for A only devices without any issues, but is throwing an lpmake error 73 for mysterious/unknown reasons, but a fix is in the works. I will post a link when I get home.

I assume the phone is rooted with Magisk which is a systemless root method. Even with older devices /system remains unmodified. All changes are only overlays/modules managed by the Magisk App.

doktorspin said:
(I tried to move GameTime out of system using system/app mover but I got an error: "Could not remount /system".)
Click to expand...
Click to collapse
This could also be done with a own module. See instructions here.

Keven11 said:
The issue you are having is related to stock Android 10. It does not allow you to make any changes to the system partition, as it won't allow you to mount it as r/w.
Click to expand...
Click to collapse
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)

doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse
I fixed the issue by ditching Android 10 for LOS 18.1. But thanks for the pointer.

doktorspin said:
Thanks. I decided to replace the stock ROM with LOS18.1. That problem solved. (Got a new one: can't use data over the phone connection.)
Click to expand...
Click to collapse

I'm glad you got it figured out. The data issue, along with many other bugs will be rectified any day now with the new release. The issue you are having with LOS 18.1 is because at the time of development the kernel for A11 hadn't been released by Moto yet. However, they did finally release it a little under 2 weeks ago. So the new version of it will be much much better. It will be linked to the same link I posted. It's just a matter of time now, and not much of it.

Telegram Odessa Devs and testers group: https://t.me/joinchat/SaZ2BX0M8bQmkioW