So, I've rooted my HD 8.9 and installed the Google Apps I'm interested in running i.e. Play store, gallery, voice search etc. I installed the framework and such in the system/app folder. I also replaced the calendarprovider.apk with the Google version, it will allow for my shared calendars in my Google account to sync propery in the native Kindle calendar app, mostly cause I hate the low res icons in the Google Apps (I've not been able to swap the Google Calendar icon and get the app to install). Anyway, today I attempted to install super box pro and accuwether from the Amazon app store and they failed. They will download, but once they start installation they fail and show a red exclamation point on the app icon. I've been able to install other apps, allrecipes, Documents to go, the dark Knight rises and a couple others. Any thoughts?
One thing, after installing the Google apps and necessary files, I unrooted and did a factory reset. I don't need a rundown of the reasons to leave it rooted. I'm content without having root. Plus, after rooting I loose my Amazon books. No point in having g the kindle if I can't use it for its original, intended purpose.
Thanks, in advance, for any productive suggestions.
Happy New Year,
Ray
Sent from my SCH-I535 using xda premium
One quick addition bit of info. The popup that I get says that "application storage space is running low". Does this make sense?
Sent from my KFJWI using XDA Premium HD app
After rooting, did you re-register you KFHD 8.9 with Amazon? Or after un-rooting, for that matter. If I remember correctly, I had to re-register with Amazon after rooting to sync with Amazon services.
Sure did. After posting I decided to factory reset again and, for the time being, I'm having no problems getting apps. I haven't installed any of my molded apps with 256 icons though. That shouldn't make a difference but seems the only variable I can think of.
Sent from my KFJWI using xda premium
Thread Moved
If you are asking questions, and have no development work to post, then the issue belongs in Q & A, and not development.
No Problem, as I'll move the thread.
MD
Thank you. It seemed to me, without a specific place for 8.9 questions the 8.9 development section was the most logical place to post. No biggie just seems that a place for 8.9 questions and such would be handy. I understand the two devices are similar but they do have differences from a root and development standpoint.
Thanks
Ray
Sent from my Kindle Fire HD 8.9 using xda premium
Moscow Desire said:
If you are asking questions, and have no development work to post, then the issue belongs in Q & A, and not development.
No Problem, as I'll move the thread.
MD
Click to expand...
Click to collapse
On that note -can we get a Q&A Thread for the KFHD 8.9" ? It gets rather confusing have 4 different devices all in the KFHD 7" Q&A Thread.
Reborn627 said:
So, I've rooted my HD 8.9 and installed the Google Apps I'm interested in running i.e. Play store, gallery, voice search etc. I installed the framework and such in the system/app folder. I also replaced the calendarprovider.apk with the Google version, it will allow for my shared calendars in my Google account to sync propery in the native Kindle calendar app, mostly cause I hate the low res icons in the Google Apps (I've not been able to swap the Google Calendar icon and get the app to install).
Click to expand...
Click to collapse
Have you updated to 8.3.1 yet? I just did so and the CalendarProvider.apk I was using previously no longer works.
Like you, I discovered I had to replace that file in order for the Kindle to save my synced calendar settings, otherwise they'd be lost once Calendar was removed from memory by the Android OS. The CalendarProvider.apk I was successfully using under 8.3.0 came from ICS AOKP ROM and it was one of the few I found that worked properly. But now, it's not. Instead, Calendar Storage isn't showing up in the list of Installed Applications and my Google Sync Settings shows "Sync com.android.calendar" instead of just "Sync Calendar" under Google Sync Settings, and throws an error when trying to sync.
For now, I've reverted back to the system default CalendarProvider until I can find another that works. I'm fairly certain I've done everything I did the last time, and am even running the same version of all the Google Apps I was using previously. So I can't figure out why it's not working like it used to.
Are you in the same boat? Or have you not upgraded yet?
CheriePie said:
Have you updated to 8.3.1 yet? I just did so and the CalendarProvider.apk I was using previously no longer works.
Like you, I discovered I had to replace that file in order for the Kindle to save my synced calendar settings, otherwise they'd be lost once Calendar was removed from memory by the Android OS. The CalendarProvider.apk I was successfully using under 8.3.0 came from ICS AOKP ROM and it was one of the few I found that worked properly. But now, it's not. Instead, Calendar Storage isn't showing up in the list of Installed Applications and my Google Sync Settings shows "Sync com.android.calendar" instead of just "Sync Calendar" under Google Sync Settings, and throws an error when trying to sync.
For now, I've reverted back to the system default CalendarProvider until I can find another that works. I'm fairly certain I've done everything I did the last time, and am even running the same version of all the Google Apps I was using previously. So I can't figure out why it's not working like it used to.
Are you in the same boat? Or have you not upgraded yet?
Click to expand...
Click to collapse
I actually have not run 8.3.1 at all. I ran 8.3.0 for about an hour just to make a backup. I've been running the sg17 CM ROM for a month or more now. I've lrarned to live without Amazon Instant Video for the time being. I've been quite pleased with CM on the kindle. In fact, with the latest Kindle app update, the book part of the tablet is virtually identical to the Amazon ROM app. Wish I could be more help to you.
Ray
This forum is meant for people who are getting locked out of their accounts due to "3rd Party Plugins or Applications"
We need to stop this from happening so share your experiences and thoughts on the matter.
I have 2 devices: a Nexus 6P running Pie (Pixel Experience) and a Pixel 3XL on the stock Pie rom. Both are rooted with Magisk Canary builds and both have Magisk Hide turned on. Snapchat never detects root on the Nexus but ALWAYS detects it on the Pixel. I've even repackaged Magisk on the Pixel but that doesn't help. I've read that it's easier for apps to detect root on A/B partition devices so maybe the newer, updated Snapchat apps have code to detect it. When I have time, I'll try an old version and see if it works...
Note that I don't believe Snapchat bans just by detecting root. It is detecting certain apps that are somehow triggering it. If you check the list of apps that you have given permission for superuser, it would be one of those. The app that I had that was triggering Snapchat was an app named app ops. I had downloaded it and just giving it permissions alone was getting me banned on Snapchat. I think this problem only affects users running Oreo or higher for whatever reason. I myself had an old phone running marshmallow with app ops and never experienced a ban. I don't think that any of the people reporting the problem had anything lower than Oreo. If you have somehow discovered the app causing your problems, uninstalling it may not fix your problem. I had to wipe my phone in order to fix it because I was still receiving bans despite uninstalling the app that was causing my problems
I've never installed app ops so that's not my problem.
As for A/B partitioning, I'm on a Samsung galaxy Note 8 and it didn't come out with this on my device so yeh ?
The main thing I found out that I had to do, was repackage the manager and I haven't been banned for the last 4 days
I am on the S8 plus and was locked out for 12 hours before. Snapchat continued to lock me out even when I fully uninstalled magisk. I decided to clean install a different Rom which seemed to do the trick. A month later I decided to go back to my original Rom and guess what? Can't even login coz of some mod I think.
So I would say it depends on what mods you have installed yourself or packaged with the custom ROM.
Snapchat ban
I have same problem. Yesterday they gave me ban but i was unbanned with their site. But today they give me one more ban but now is for 24h ... anyone know how to fix snap or maybe hide root? S7 9.0 blackdiamond v3
Downloaded an early January 2019 version of Snapchat and signed up for a new account on my Pixel 3XL. All was good at first then I closed the app. When I tried to sign back in, I got the "problem connecting to server" error which requires an update to the most current version. I updated and after just a few hours, I got the "12 hour account locked" message for "3rd party apps". I've had Magisk Manager repackaged but that obviously didn't help. BTW, I have not repackaged Magisk on my Nexus 6P and it's still works. I found a comment by a user of the Bitmoji app (which I use on my Pixel but not my Nexus) that reported his Snapchat was locked by this app so I uninstalled it. We'll see how it goes when my 12 hour ban is up...
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
newkydawg said:
Update: I uninstalled Bitmoji. I also added the systemless host module in Magisk and enabled systemless mode in Adaway. That is supposed to prevent Adaway from modifying the system partition but neither worked. I'm on a 24 lock now....
Click to expand...
Click to collapse
What apps have you given superuser? The app causing you problems is likely in that list
I had this happen before to me, i uninstalled edXposed and i was able to use snapchat even while on a 24 hour ban
iMystic said:
What apps have you given superuser? The app causing you problems is likely in that list
Click to expand...
Click to collapse
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
newkydawg said:
Nope. I have the same apps on my Nexus 6P and it doesn't get locked out. In fact, my wife's Nexus 6P has the same apps, is rooted with SuperSu and she doesn't get locked out so IDK...
Click to expand...
Click to collapse
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
iMystic said:
I don't know if this would affect you but an app that was causing the problems on my phone with Android 9.0 has no affect on an old phone running Android 6.0.1. I don't know why this happens but if you were running a new version of Android such as Android 9.0, an app that may not cause problems on your 6P may cause problems for you. And again, I have no idea why this happens but I can guarantee that was my problem and I haven't had a ban since
Click to expand...
Click to collapse
Both my Pixel 3XL and Nexus 6P are running Android 9 rooted with Magisk Canary (19005). Both have the same apps with superuser rights. All this to say that Snapchat was working fine on both for months and for about the last 6 weeks, my Pixel 3 XL's account gets locked and my Nexus 6P does not.
Thanks for trying to help and glad you figured your problem out.
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
There are all the reasons why i purely stopping to use Snapchat, and also due to the fact that the application is so badly optimized for Android (even since the complete redesign of the application), in the end considering my use so irregular, I just uninstalled it, so no problem.
The time of Snapprefs and Snaptools was fun and funny, and especially less vicious as a concept than the basic one.
The good old days, but all good things must come to an end.
Rom said:
snip
Click to expand...
Click to collapse
It's what happens when a company becomes complacent and puts more effort into blocking modifications instead improving their terrible app.
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
I have got a problem, I have a Nokia 7 Plus, stock fw no changes at all!
And I keep getting banned... Support is a joke, I just get automatic replies...
The only reason i may have for getting bans is if snap scans the sd card, where I have magisk and roms files from other devices...
Any tips ???
newkydawg said:
Update:
About 2 weeks ago, I flashed the May rom update for my Pixel 3 XL, installed Snapchat ver. 10.41.6.0, hid SC and all components of Google Play Services and Google Play Store in Magisk and I haven't been banned! I detach SC from the Play Store with TiBu but it somehow gets reattached. I just don't update it. Thanks @TevW !!!
Click to expand...
Click to collapse
I tried to follow the instructions but snapchat keeps saying there was a connection problem with the server.
TevW said:
I'm copying this from the SnapFreedom thread who's problems obviously mirror your own. I'll be editing parts out, but some of it should still apply if you guys are getting locked out.
XPrivacyLua
Install it from FDroid or Xposed Repo and check the boxes for "Determine activity" and "Get applications" in Snapchat's tab. You can also enable "Get location" to spoof your location and still use SnapMaps.
Magisk
A few points, these probably don't apply, but they're still worth doing.
Repackage it through Settings -> Hide Magisk
Make sure to block all components under "Google Play Services" and "Google Play Store". There's a few things that aren't blocked by default that might trigger SafetyNet.
Snapchat
Hoo boy...
Don't use anything higher than, and including, 10.41.6.0. It's pretty much a ban-fest. With SnapTools, we use 10.20.5.0 and 10.26.5.0. Those are probably your safest bets. Also, if you plan on downgrading, use any 10.39 app. Something in how logins work has changed in the later versions, so apps like Preferences Manager don't work.
Theming your app should be okay. I did it for months and never got a ban.
Only give it the bare minimum permissions. Storage, Camera, and Microphone. Location too, if you're into being tracked by your friends and Snapchat.
Do NOT use modified apps. At all. Ever. They're the easiest things to detect.
If you want to block ads reliably, you can use this Magisk Module. This WON'T stop bans.
Snapchat also logs your device ID. If you've received a temp-ban prior to this, make sure to change your Device ID. If you're on Oreo, you can use this app. If not, you can use Titanium Backup to change it. The latest version with this function is version 8.2.2. But honestly, the most reliable way is to reflash your ROM.
Click to expand...
Click to collapse
Does this mean that I can't use energized adblock magisk module? Do I have to use only the Snapchat adblock magisk module that you linked for any kind of adblocking on the device.
Thanks!
Hello all,
I'm new to using Pixel Experience on my Pixel 2 XL and am running into an issue with one banking app. I installed version 12 of Pixel Experience and the TD Bank app won't even show up in the Play Store. If I try and download it from the web, I get "Your device isn't compatible with this version". I went ahead and installed Magisk and enabled MagiskHide but that didn't seem to help much. Since I can't even get it installed, I can't specifically hide root for that app.
Any ideas or suggestions would be greatly appreciated.
Thanks,
Fred
In my prior experiences with a rooted device on which banking account didn't work it did with island. Maybe you can install the banking app to island and use it there, because within island there is no root
Bright.Light said:
In my prior experiences with a rooted device on which banking account didn't work it did with island. Maybe you can install the banking app to island and use it there, because within island there is no root
Click to expand...
Click to collapse
Thanks I will look into Island as I wasn't familiar with it. I did end up getting it working by exporting the app APK from another phone and installing it on this one.
Fred