Database Info

Google Play Sore Error (-505) -- Lollipop

After updating to Lollipop on my Nexus 5, it restored all of my apps except for about 10. One of them is a widget that I use everyday called Simple Calendar Widget by MYCOLORSCREEN. When trying to download the app, it gives me the message "Unknown error code during application install: -505". It seems to download fine, but the message pops up during the install process. Anybody know about this issue or experiencing the same thing if you try to download this application? I also tried downloading the apk file online but that also fails to install. I can't find any info regarding this issue. Thanks.

I had this issue on certain apps as well. The dev of those apps needed to change something for it to work on Lollipop.

RoomTenONine said:
I had this issue on certain apps as well. The dev of those apps needed to change something for it to work on Lollipop.
Click to expand...
Click to collapse
I've had this problem. Did a search with Google and it seems others are having this issue. Hopefully Google will have an update to fix.

Do a search in this forum. I replied with the cause and solutions. Was posted last week.
Sent from my Nexus 5 using Tapatalk

nikon120 said:
Do a search in this forum. I replied with the cause and solutions. Was posted last week.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Code 505 is a permissions code. This typically means that the APK file already exists in your /data/app folder. You'll need to locate the APK files in question in the /data/app folder and remove them. You will need root to perform this action.
You came across this problem because you didn't do a wipe of your userdata partition when you jumped from Kitkat to Lollipop. I encountered the same issue because of that reason. I just ended up wiping and starting fresh as my phone hadn't been wiped since I got the device last November.
Click to expand...
Click to collapse
Are you sure? I flashed the factory image of Lollipop on my phone and it wiped everything. Afterwards, I had to also do a factory reset of my phone from the settings due to a storage issue. Why would that get left behind?
Edit: I checked (phone is rooted) and the app isn't in the /data/app folder

PMamba said:
Are you sure? I flashed the factory image of Lollipop on my phone and it wiped everything. Afterwards, I had to also do a factory reset of my phone from the settings due to a storage issue. Why would that get left behind?
Edit: I checked (phone is rooted) and the app isn't in the /data/app folder
Click to expand...
Click to collapse
I spent an hour combing through Google group threads trying to get a real answer to this outstanding question. I was perplexed that only two applications of mine refused to install due to this error. The consensus was that the APK file was still there, or some remnants of data related to the application remained on the device that the Play Store service didn't like.
I ended up wiping my device twice:
Once by flashing both the userdata.img and cache.img files, which ended up giving me the storage issue bug on Lollipop. (Showing 16GB instead of 32GB)
Second by performing a factory reset from within the booted OS, which resolved the storage issue.
After that, everything was good to go. Have yet to encounter this error code again.

PMamba said:
After updating to Lollipop on my Nexus 5, it restored all of my apps except for about 10. One of them is a widget that I use everyday called Simple Calendar Widget by MYCOLORSCREEN. When trying to download the app, it gives me the message "Unknown error code during application install: -505". It seems to download fine, but the message pops up during the install process. Anybody know about this issue or experiencing the same thing if you try to download this application? I also tried downloading the apk file online but that also fails to install. I can't find any info regarding this issue. Thanks.
Click to expand...
Click to collapse
I just had to click install again after the error and it worked for me. It was a PITA.

sigh, I've had this issue with terminal emulator
C:\>adb install Term.apk
3966 KB/s (515876 bytes in 0.127s)
pkg: /data/local/tmp/Term.apk
Failure [INSTALL_FAILED_DUPLICATE_PERMISSION perm=jackpal.androidterm.permission
.PREPEND_TO_PATH pkg=com.jrummy.liberty.toolbox]
Click to expand...
Click to collapse
So yeah...duplicate permissions, in this case i had ROM Toolbox Lite installed which had the same permission sooooo it's one or the other at the moment

bleets said:
sigh, I've had this issue with terminal emulator
So yeah...duplicate permissions, in this case i had ROM Toolbox Lite installed which had the same permission sooooo it's one or the other at the moment
Click to expand...
Click to collapse
Hm alright. Where does the apk file need to be in order to use the adb install command? I want to see which app is conflicting with.

PMamba said:
Hm alright. Where does the apk file need to be in order to use the adb install command? I want to see which app is conflicting with.
Click to expand...
Click to collapse
as long as you have adb working it can be anywhere as long as you know the path
so adb install c:\path\to\file.apk
as it happens with terminal emulator i could download the apk seperately, with other apps i'd probably download on my tablet and pull it off that

bleets said:
as long as you have adb working it can be anywhere as long as you know the path
so adb install c:\path\to\file.apk
as it happens with terminal emulator i could download the apk seperately, with other apps i'd probably download on my tablet and pull it off that
Click to expand...
Click to collapse
Wow it looks like GTasks is conflicting. Without GTasks this app is useless. :crying:
Thanks though.

PMamba said:
Wow it looks like GTasks is conflicting. Without GTasks this app is useless. :crying:
Thanks though.
Click to expand...
Click to collapse
https://code.google.com/p/android-developer-preview/issues/detail?id=1668
hopefully it'll get sorted...
You'd have thought people testing would have installed enough apps to come across it and if google knew about it in october why not fix it

I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.

How I solved it
In bootloader mode I flash from the factory image userdata and cache, then I wipe Dalvik, data and cache in TWRP after the first boot I skip the setup just too full factory data reset, in the second boot, I set up everything normal, but instead of restoring from previous devices I set it up as a new device, then I manually download the app that was giving the error, it installed without a problem.
I know is a little too much for an app, but it works for me.

onetraakmind said:
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
Click to expand...
Click to collapse
Exactly.
Thank you very much for the tip.

onetraakmind said:
I had this issue trying to install Rom Toolbox. I uninstalled Terminal Emulator and the issue went away, probably because Terminal Emulator is included in Rom Toolbox.
Click to expand...
Click to collapse
I'm currently having the issue everyone mentions, except I already have ROM Toolbox Pro and was trying to install Terminal Emulator. Terminal Emulator in ROM Toolbox currently FC's on Stock (rooted) 5.0.1. But I use other features, like the Rebooter that I don't wanna sacrifice for just Terminal Emulator haha. Wish they'd fix this issue permanently

Jleeblanch said:
I'm currently having the issue everyone mentions, except I already have ROM Toolbox Pro and was trying to install Terminal Emulator. Terminal Emulator in ROM Toolbox currently FC's on Stock (rooted) 5.0.1. But I use other features, like the Rebooter that I don't wanna sacrifice for just Terminal Emulator haha. Wish they'd fix this issue permanently
Click to expand...
Click to collapse
Uninstall ROM toolbox, install terminal emulator, install ROM toolbox... Someone said that worked.

rootSU said:
Uninstall ROM toolbox, install terminal emulator, install ROM toolbox... Someone said that worked.
Click to expand...
Click to collapse
You really should look in the rom toolbox pro app a little better. There is an emulator built in
Sent from my One M8 using Tapatalk

mattie_49 said:
You really should look in the rom toolbox pro app a little better. There is an emulator built in
Sent from my One M8 using Tapatalk
Click to expand...
Click to collapse
I know, that's why you can't install jackpal terminal emulator if you have ROM toolbox installed as it uses the same permissions.
Although you should read up yourself because if you did, you'd know the terminal emulator in rom toolbox force closes on lollipop on the nexus 5.

I understand this is a old thread but I fixed it a way that wasn't mentioned in this thread. Just thought I'd share for anyone googling this issue and finding this. What I did was go into the guest account and uninstall the app that was causing the issue such as snapchat. The way I caused it in the first place was installing snapchat on aptoide which installed it on both my account and the guest account and I decided I didn't want snapchat anymore so I uninstalled it but it was still there on the guest account which caused the error 505 whenever I tried to reinstall snapchat.

[Completed] The Sky Go app and Sky Movies apps will not play on my device because of root check

Hello everyone
I am not a developer but would appreciate any helpful feedback, preferably in layman's language, that anyone might be able to offer to a problem that I am having with my android device, running version 4.2.2, a large Hannspree 13.3 tablet. I bought the tablet about six months ago and I am happy with the general performance. However, recently I downloaded a number of streaming media apps from Google Play Store including the Sky Go and Sky Movies apps and also the All4 Channel 4 on demand app. When I tried to run these apps, I got a message saying 'These apps are not supported on rooted devices'. I am led to believe that the Hannspree 13.3 is rooted by default at manufacture although I did not know this at the time of purchase and indeed, at that time I was totally ignorant about 'rooting'. For this reason, I have not yet opted to do a factory reset of my device because, if true, then this would not solve the issue. After researching comments on a number of internet forums, I came across several suggestions as to how to resolve the issue. I opted for downloading the SuperSU app, which then enabled me, via the app settings, to perform a 'full unroot', which I duly did. By downloading a root checker app, I was able to verify that my large Hannspree tablet is now unrooted. However, when I tried the Sky Go and Sky Movies apps after unrooting, I still got an error message 'Not supported on rooted devices'. I no longer get the 'rooted app' message when I play the All4 app, but the app doesn't play, it simply hangs. Therefore, and I have been in touch with the Sky Community forums, these streaming media apps all still perceive my device to be rooted but it is not, although someone from the Sky Community forum suggested that there still must be traces of the original rooting in the OS/firmware which the Sky apps and other streaming media apps are picking up on. I tried, on advice, a hide root app but when I tried this, I get a message saying 'Cannot find the su binaries'. When I tried to reinstall SuperSU I got a similar message 'Cannot locate the su binaries and SuperSU cannot install them. This is a problem'. It seems that the original unrooting has removed the su binaries and I cannot now try hide root apps. However, there must be some trace of root that the streaming media apps are still picking up on.
Would anyone know how to remove these traces of root. I did read somewhere, another suggestion from a forum, that it was possible to manually unroot a device by using a file manager app and deleting su binaries from system/bin and system/xbin directories and deleting superuser.apk from system/apps directory. However having browsed system directory with root browser in the ROM toolbox app, the su binaries are not present in the system/bin or system/xbin which, I suppose, is further verification that my device is now unrooted. But it can't be fully unrooted, otherwise surely the streaming media apps would play.
Should I do a factory reset to restore the device to its default (presumably rooted) state and then manually delete the su as described above?
The curious thing is that the streaming media apps work perfectly on my smaller Hannspree 10.1 device, which obviously is not rooted and not perceived as rooted.
Is it possible to install the operating system of my smaller Hannspree device onto my larger Hannspree device? I tried the 'check available updates' in the About tablet tab in Settings but I get an error message on my large Hannspree device to the effect of 'Error invalid ROM ID' so cannot do an update, or check for an update.
Can any of you techies out there help?
Thanks, in anticipation.

trivia chris said:
Hello everyone
I am not a developer but would appreciate any helpful feedback, preferably in layman's language, that anyone might be able to offer to a problem that I am having with my android device, running version 4.2.2, a large Hannspree 13.3 tablet. I bought the tablet about six months ago and I am happy with the general performance. However, recently I downloaded a number of streaming media apps from Google Play Store including the Sky Go and Sky Movies apps and also the All4 Channel 4 on demand app. When I tried to run these apps, I got a message saying 'These apps are not supported on rooted devices'. I am led to believe that the Hannspree 13.3 is rooted by default at manufacture although I did not know this at the time of purchase and indeed, at that time I was totally ignorant about 'rooting'. For this reason, I have not yet opted to do a factory reset of my device because, if true, then this would not solve the issue. After researching comments on a number of internet forums, I came across several suggestions as to how to resolve the issue. I opted for downloading the SuperSU app, which then enabled me, via the app settings, to perform a 'full unroot', which I duly did. By downloading a root checker app, I was able to verify that my large Hannspree tablet is now unrooted. However, when I tried the Sky Go and Sky Movies apps after unrooting, I still got an error message 'Not supported on rooted devices'. I no longer get the 'rooted app' message when I play the All4 app, but the app doesn't play, it simply hangs. Therefore, and I have been in touch with the Sky Community forums, these streaming media apps all still perceive my device to be rooted but it is not, although someone from the Sky Community forum suggested that there still must be traces of the original rooting in the OS/firmware which the Sky apps and other streaming media apps are picking up on. I tried, on advice, a hide root app but when I tried this, I get a message saying 'Cannot find the su binaries'. When I tried to reinstall SuperSU I got a similar message 'Cannot locate the su binaries and SuperSU cannot install them. This is a problem'. It seems that the original unrooting has removed the su binaries and I cannot now try hide root apps. However, there must be some trace of root that the streaming media apps are still picking up on.
Would anyone know how to remove these traces of root. I did read somewhere, another suggestion from a forum, that it was possible to manually unroot a device by using a file manager app and deleting su binaries from system/bin and system/xbin directories and deleting superuser.apk from system/apps directory. However having browsed system directory with root browser in the ROM toolbox app, the su binaries are not present in the system/bin or system/xbin which, I suppose, is further verification that my device is now unrooted. But it can't be fully unrooted, otherwise surely the streaming media apps would play.
Should I do a factory reset to restore the device to its default (presumably rooted) state and then manually delete the su as described above?
The curious thing is that the streaming media apps work perfectly on my smaller Hannspree 10.1 device, which obviously is not rooted and not perceived as rooted.
Is it possible to install the operating system of my smaller Hannspree device onto my larger Hannspree device? I tried the 'check available updates' in the About tablet tab in Settings but I get an error message on my large Hannspree device to the effect of 'Error invalid ROM ID' so cannot do an update, or check for an update.
Can any of you techies out there help?
Thanks, in anticipation.
Click to expand...
Click to collapse
Hi, thank you for using XDA assist.
There is a general forum for android here*http://forum.xda-developers.com/android/help*where you can get better help and support if you try to ask over there.*
Good luck.

Snapchat on rooted devices without Xposed (Nougat)

Hi, So i recently bought a nexus 6p and I rooted it as one of the first things. I then found out I was running Nougat, and Xposed wasn't out yet. Many apps blocks the use of the app if you are rooted fx. Snapchat. But I found a way around without using a Xposed mod fx. 'root cloak'.
All you have to do:
1. Download Root Browser, by JRummy Apps Inc. or any other app of the same kind
2. navigate to /vendor/lib/
3. Locate the file named "liboemcrypto.so"
4. Rename the file to "liboemcrypto.so.bak"
5. power off the device and boot it normally up, and then Snapchat should be working again:good:
If I posted this in the wrong thread, sorry it my first post
#EDIT 1
6. Login to Snapchat
7. Rename "liboemcrypto.so.bak" to "liboemcrypto.so" (original name)
8. power off the device and boot it normally up. Then Snapchat should still be working, and you will not get any errors in other apps
Check my comment for more details (comment 5)

It works! Thank you so much!
Sent from my Nexus 6 using Tapatalk

Thanks men

I'm getting a "operation failed" message every time I try to change this. I've tried root browser and amaze file manager, and got the same message both times. Each has superuser permissions. Is there a fix for this?

Thankssss! Love you!

Okay so yesterday I started getting errors, Spotify not playing any sound, Facebook videos not loading, Facebook messenger call not working. One week after I changed the name of the file, so I decided to change it back to see if it was the file that was causing the problems. After I renamed it back to original, and then I had no errors with the other apps and Snapchat is still logged in and working.
So I recommend to change the file to .bak, reboot, login in Snapchat. Change the file back, reboot and then there shouldn't be any problems:good:

TheGejr said:
Hi, So i recently bought a nexus 6p and I rooted it as one of the first things. I then found out I was running Nougat, and Xposed wasn't out yet. Many apps blocks the use of the app if you are rooted fx. Snapchat. But I found a way around without using a Xposed mod fx. 'root cloak'.
All you have to do:
1. Download Root Browser, by JRummy Apps Inc. or any other app of the same kind
2. navigate to /vendor/lib/
3. Locate the file named "liboemcrypto.so"
4. Rename the file to "liboemcrypto.so.bak"
5. power off the device and boot it normally up, and then Snapchat should be working again:good:
If I posted this in the wrong thread, sorry it my first post
#EDIT 1
6. Login to Snapchat
7. Rename "liboemcrypto.so.bak" to "liboemcrypto.so" (original name)
8. power off the device and boot it normally up. Then Snapchat should still be working, and you will not get any errors in other apps
Check my comment for more details (comment 5)
Click to expand...
Click to collapse
That file doesn't exist for me.

Wish this was posted before I unrooted and relocked the bootloader lol :cyclops:

TheGejr said:
Okay so yesterday I started getting errors, Spotify not playing any sound, Facebook videos not loading, Facebook messenger call not working. One week after I changed the name of the file, so I decided to change it back to see if it was the file that was causing the problems. After I renamed it back to original, and then I had no errors with the other apps and Snapchat is still logged in and working.
So I recommend to change the file to .bak, reboot, login in Snapchat. Change the file back, reboot and then there shouldn't be any problems:good:
Click to expand...
Click to collapse
Can't log in. Still the same issue. My phone was rooted, and I installed SnapChat. Do I need to unroot to install it?
EDIT: I uninstalled/installed SnapChat. No luck still.

X0LARIUM said:
Can't log in. Still the same issue. My phone was rooted, and I installed SnapChat. Do I need to unroot to install it?
EDIT: I uninstalled/installed SnapChat. No luck still.
Click to expand...
Click to collapse
It seems very random, for whom it's working for... i recently logged on snapchat on my Iphone, and now i can't login on my Nexus. So i don't really know it seems very random :/

TheGejr said:
It seems very random, for whom it's working for... i recently logged on snapchat on my Iphone, and now i can't login on my Nexus. So i don't really know it seems very random :/
Click to expand...
Click to collapse
log out of your iphone..
It can only be logged in on one device..like whatsapp..

X0LARIUM said:
log out of your iphone..
It can only be logged in on one device..like whatsapp..
Click to expand...
Click to collapse
Yea i have logged out, but it still don't work

TheGejr said:
Yea i have logged out, but it still don't work
Click to expand...
Click to collapse
Simplest way to use SnapChat on the rooted phone.
Step 1: Unroot (In SuperSU, click Full Unroot and restart)
Step 2: (After the reboot) Install Snapchat
Step 3: Log in
Step 4: Go to TWRP/CWM and flash SUPERSU
Step 5: Open Beer
You now have SNAPCHAT working on a rooted phone.

I have tried all of these methods, with or without Xposed. Impossible to get it to work on my htc one m7. Anyone have experience on the same device? and NO Casper is not an option!! Thanks

How do you guys login with the Magisk root? On s7 edge

this didn't work on my Galaxy S7, anyone know any other methods?

Hey crew, downloaded the exact same app as mentioned to my rooted Nexus 6P, found the file, clicked rename and operation failed. Any solution?

tmfvde said:
Hey crew, downloaded the exact same app as mentioned to my rooted Nexus 6P, found the file, clicked rename and operation failed. Any solution?
Click to expand...
Click to collapse
Hey make sure you have BusyBox installed from the app store. Also download the extra utilities once you first open root browser.

File not found
Hi, The file doesn't exist. I'm on a Nexus 5 CM 14.1 . Any suggestions?

File Not Fund, on OnePlus 3
mithunsrk9 said:
Hi, The file doesn't exist. I'm on a Nexus 5 CM 14.1 . Any suggestions?
Click to expand...
Click to collapse
can't find that file on my oneplus3 , what should I do ?

[GUIDE] Debloating and More (Fire HD 8)

This is for the Fire HD 8 8th generation rooted with xyz's exploit
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
I've seen a couple people run into problems with this so rather than have xyz's thread clogged I figured I'd
make a seperate thread just for this.
I've made an update to the debloat.zip so it can be flashed at any time rather than flashing after rooting
[seperate zip instead of a modifed finalize.zip ]
==Debloating==
DISCLAIMER : Per testing and input from other members, Amazon Apps will NOT be able to be reinstalled after flashing this. I've yet to figure out if this is a direct result of this script or due to the nature of xyz's exploit, either way
after rooting, do NOT expect to be able to use Amazon Apps (defeat's the purpose of this script anyways lol)
1. Download debloat.zip from here
2. Reboot to TWRP, and flash
3. Reboot to system and say goodbye to Amazon Bloatware
==Replacing FireLauncher==
1. Install a launcher of your choice (Tested with CPL and Nova Launcher)
2. Install Terminal Emulator
3. Run 'su' from terminal emulator and grant it root permissions, then type 'pm disable com.amazon.firelauncher'
4. Press the home button and your new launcher is ready to go !
Thanks to xyz for the amazing work :highfive:

delessio100 said:
This is for the Fire HD 8 8th generation rooted with xyz's exploit
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
I've seen a couple people run into problems with this so rather than have xyz's thread clogged I figured I'd
make a seperate thread just for this.
I've made an update to the debloat.zip so it can be flashed at any time rather than flashing after rooting
[seperate zip instead of a modifed finalize.zip ]
==Debloating==
1. Download debloat.zip from here
2. Reboot to TWRP, and flash
3. Reboot to system and say goodbye to Amazon Bloatware
==Replacing FireLauncher==
1. Install a launcher of your choice (Tested with CPL and Nova Launcher)
2. Install Terminal Emulator
3. Run 'su' from terminal emulator and grant it root permissions, then type 'pm disable com.amazon.firelauncher'
4. Press the home button and your new launcher is ready to go !
Thanks to xyz for the amazing work :highfive:
Click to expand...
Click to collapse
Thanks for this! Will flashing this debloat.zip allow me to install and use the Amazon Prime Video or the Alexa app from the Playstore later on or will it stop the app from working?

ryknow27 said:
Thanks for this! Will flashing this debloat.zip allow me to install and use the Amazon Prime Video or the Alexa app from the Playstore later on or will it stop the app from working?
Click to expand...
Click to collapse
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to

delessio100 said:
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
Click to expand...
Click to collapse
Awesome, thanks for the reply. I'll give it a shot.
---------- Post added at 09:49 AM ---------- Previous post was at 09:38 AM ----------
delessio100 said:
Per my testing, the Play Store version of Amazon Apps are working (I've tested Alexa, Prime Video, and the Kindle App so far), so yes you should be able to
Click to expand...
Click to collapse
Sorry, one more question. When you tested the Amazon apps, did you also previously install the finalize.zip?

ryknow27 said:
Awesome, thanks for the reply. I'll give it a shot.
---------- Post added at 09:49 AM ---------- Previous post was at 09:38 AM ----------
Sorry, one more question. When you tested the Amazon apps, did you also previously install the finalize.zip?
Click to expand...
Click to collapse
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit

delessio100 said:
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
Click to expand...
Click to collapse
Thank you

delessio100 said:
Yes, xyz's finalize.zip only removes system apps related to OTA updates, so it prevents accidental / forced OTA updates from overwriting things modified by the exploit
Click to expand...
Click to collapse
I followed the instructions for Tailborn form your post on xyz's thread except for installing Root Essentials and then followed the instructions from this thread and after installing several Amazon apps, they start to open and then force close. I could be wrong but I think it may be due to the finalize.zip because after the first time I successfully rooted with xyz's method it did the same thing. Since it works for you, do you know if you did anything different than what I did?

ryknow27 said:
I followed the instructions for Tailborn form your post on xyz's thread except for installing Root Essentials and then followed the instructions from this thread and after installing several Amazon apps, they start to open and then force close. I could be wrong but I think it may be due to the finalize.zip because after the first time I successfully rooted with xyz's method it did the same thing. Since it works for you, do you know if you did anything different than what I did?
Click to expand...
Click to collapse
What apps specifically aren't working ? I've only tested the Kindle App, Alexa, and Prime Video. Are these giving you errors? I haven't fully tested all Amazon apps as I don't really use them but if you can give me a list of the apps that aren't functional I can take a look when I get home. If you'd prefer I can modify my debloat script to not remove the Amazon apps you want to keep Also if you could provide a logcat from one of the apps that's crashing I can try to determine what's causing the crash. The instructions I provided for Tailborn were just to fix the error with his SD card

delessio100 said:
What apps specifically aren't working ? I've only tested the Kindle App, Alexa, and Prime Video. Are these giving you errors? I haven't fully tested all Amazon apps as I don't really use them but if you can give me a list of the apps that aren't functional I can take a look when I get home. If you'd prefer I can modify my debloat script to not remove the Amazon apps you want to keep Also if you could provide a logcat from one of the apps that's crashing I can try to determine what's causing the crash. The instructions I provided for Tailborn were just to fix the error with his SD card
Click to expand...
Click to collapse
Yes I did see that your instructions were to help him with his SD card issue. I was basically just using it as a guide to start over except for anything to do with the SD card since I didn't have that issue.
The main apps I'm wanting to work that I'm having an issue with is Alexa and Amazon prime video. It will be a little bit before I can attach a logcat. I've never created one before but it should not be that hard to figure out and I'm on my way to work right now.

ryknow27 said:
Yes I did see that your instructions were to help him with his SD card issue. I was basically just using it as a guide to start over except for anything to do with the SD card since I didn't have that issue.
The main apps I'm wanting to work that I'm having an issue with is Alexa and Amazon prime video. It will be a little bit before I can attach a logcat. I've never created one before but it should not be that hard to figure out and I'm on my way to work right now.
Click to expand...
Click to collapse
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Getting Logcat (assuming you're on windows and running command prompt on the desktop)
1. Connect the kindle to your computer, run adb logcat -c (clears logcat)
2. Run adb logcat | findstr "com.amazon.dee.app" > logcat.txt (This will store the logcat for the Alexa app to a text file on your desktop)
3. Go back to your kindle, open the Alexa App and wait for it to crash
4. After it crashes, hit CTRL + C in command prompt (stops logging)
5. Copy and paste logcat.txt and send it in your reply
This will help me figure out what's causing the crash and from here I'll be able to fix it

delessio100 said:
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Click to expand...
Click to collapse
Thanks

delessio100 said:
I'm on my way home from college (on the bus ) so I can guide you through it when I get home. Alexa worked without errors for me so I'm not sure why it wouldn't work for you but I'm sure we'll get it sorted it out soon
Getting Logcat (assuming you're on windows and running command prompt on the desktop)
1. Connect the kindle to your computer, run adb logcat -c (clears logcat)
2. Run adb logcat | findstr "com.amazon.dee.app" > logcat.txt (This will store the logcat for the Alexa app to a text file on your desktop)
3. Go back to your kindle, open the Alexa App and wait for it to crash
4. After it crashes, hit CTRL + C in command prompt (stops logging)
5. Copy and paste logcat.txt and send it in your reply
This will help me figure out what's causing the crash and from here I'll be able to fix it
Click to expand...
Click to collapse
Sorry, I've been really busy here at work this evening and unfortunately, the computers here will not let me retrieve a logcat through ADB. They have them locked down to where we can't use them for much except for work stuff.
I did get a logcat from an app called "aLogcat" from the Playstore but it is really long and I don't know if it will be good enough. I can attach it here or if it is best I can get one from adb later tonight after getting home. I'm in no rush

ryknow27 said:
Sorry, I've been really busy here at work this evening and unfortunately, the computers here will not let me retrieve a logcat through ADB. They have them locked down to where we can't use them for much except for work stuff.
I did get a logcat from an app called "aLogcat" from the Playstore but it is really long and I don't know if it will be good enough. I can attach it here or if it is best I can get one from adb later tonight after getting home. I'm in no rush
Click to expand...
Click to collapse
Id prefer you get one from adb as it'll make narrowing down the problem much easier :good: but I can just use grep on my PC to filter out the other things, so if you can send over what you have and attach the logcat from adb at your leisure when you get home, I'll take a look

delessio100 said:
Id prefer you get one from adb as it'll make narrowing down the problem much easier :good: but I can just use grep on my PC to filter out the other things, so if you can send over what you have and attach the logcat from adb at your leisure when you get home, I'll take a look
Click to expand...
Click to collapse
Hopefully I attach this right...lol.
I will get it from adb later tonight. Thanks again.

ryknow27 said:
Hopefully I attach this right...lol.
I will get it from adb later tonight. Thanks again.
Click to expand...
Click to collapse
I just skimmed through it and grepped for 'com.amazon.dee.app' but nothing crash related has come up. The only crash related thing I noticed in the logcat was related to Amazon's Device Metric's app which shouldn't be affecting the Alexa App ( as i have that app removed and Alexa functioned fine in previous tests). I think a regular adb logcat is gonna be our best bet to narrow the issue down. If you haven't done this already try these suggestions
1. Clear App Data & Cache from settings and try opening it
2. Clear App Data & Cache, then from Settings grant the app all requested permissions, then try opening it
3. Uninstall the app then repeat step 2 after installing (don't open the app before granting permissions)
I have a suspicion it's related to the removal of Amazon's Account Management App (if you go to settings -> My Account , settings crashes) yet only my debloat zip removes this app, and you said you experienced this before flashing it. I'm installing the Alexa app now and I'm going to see if i can reproduce the crashes. I won't be letting Amazon get the best of us
Edit : I was able to recreate the crash by uninstalling the app, reinstalling, and then i got it to crash after signing in, however, after opening the app again it went right to the main screen and hasn't crashed since
Edit 2 : Try uninstalling, installing, signing in, and after it crashes open the app (it will crash again) then open it again (it shouldn't crash this time and should bring you to the main screen)
It seems that there's permissions included in the app that are only allowed for system priv-apps (which might be causing the crash) so if after doing this you still aren't able to get into the main screen try moving the app to /system/priv-app

delessio100 said:
I just skimmed through it and grepped for 'com.amazon.dee.app' but nothing crash related has come up. The only crash related thing I noticed in the logcat was related to Amazon's Device Metric's app which shouldn't be affecting the Alexa App ( as i have that app removed and Alexa functioned fine in previous tests). I think a regular adb logcat is gonna be our best bet to narrow the issue down. If you haven't done this already try these suggestions
1. Clear App Data & Cache from settings and try opening it
2. Clear App Data & Cache, then from Settings grant the app all requested permissions, then try opening it
3. Uninstall the app then repeat step 2 after installing (don't open the app before granting permissions)
I have a suspicion it's related to the removal of Amazon's Account Management App (if you go to settings -> My Account , settings crashes) yet only my debloat zip removes this app, and you said you experienced this before flashing it. I'm installing the Alexa app now and I'm going to see if i can reproduce the crashes. I won't be letting Amazon get the best of us
Edit : I was able to recreate the crash by uninstalling the app, reinstalling, and then i got it to crash after signing in, however, after opening the app again it went right to the main screen and hasn't crashed since
Edit 2 : Try uninstalling, installing, signing in, and after it crashes open the app (it will crash again) then open it again (it shouldn't crash this time and should bring you to the main screen)
It seems that there's permissions included in the app that are only allowed for system priv-apps (which might be causing the crash) so if after doing this you still aren't able to get into the main screen try moving the app to /system/priv-app
Click to expand...
Click to collapse
Ok well, I tried everything you listed here and it still just closes right after opening. I do not get the chance to log in or anything. Also to clarify what I said originally because it may have been a little misleading, the first time I rooted it I did not actually install the Alexa app but I did try to log into the Amazon services within the Fire Launcher and it would crash. At that point, I re-did the root and did not install the finalize.zip and it would then let me log in to Amazon services but that leaves all of the OTA stuff in there. So I tried it all again and that's when I first messaged you about it.

ryknow27 said:
Ok well, I tried everything you listed here and it still just closes right after opening. I do not get the chance to log in or anything. Also to clarify what I said originally because it may have been a little misleading, the first time I rooted it I did not actually install the Alexa app but I did try to log into the Amazon services within the Fire Launcher and it would crash. At that point, I re-did the root and did not install the finalize.zip and it would then let me log in to Amazon services but that leaves all of the OTA stuff in there. So I tried it all again and that's when I first messaged you about it.
Click to expand...
Click to collapse
At this point I'd recommend talking to xyz as it doesn't seem to be an issue with my debloat script, he's going to have a much better understanding of the issue and is more knowledgeable. I'll look at your adb logcat when you get time to grab one but I've wiped my Kindle clean reflashed everything including finalize.zip and my debloat script and I'm still able to log in and use Amazon Apps

No problem and thanks for the assistance. I'll still get the adb logcat later tonight. [emoji3]
Sent from my HTC 10 using Tapatalk

ryknow27 said:
No problem and thanks for the assistance. I'll still get the adb logcat later tonight. [emoji3]
Click to expand...
Click to collapse
I'll take a look whenever you get time to send it :good:

delessio100 said:
I'll take a look whenever you get time to send it :good:
Click to expand...
Click to collapse
Sorry it took me a day to get back to you. I didn't get time to mess with it due to some stuff going on. I tried something different this time. I followed the directions from xyz's thread except I did not install the finalize.zip. I then did everything from this thread, then I used a root explorer and deleted all of the OTA stuff from system/priv-app. Now, the Alexa app will run just fine but the Prime Video app crashes. So, I tried doing what you said a couple of times using "com.amazon.avod.thirdpartyclient" but the .txt file would always be empty. So I just used adb logcat -v long > logcat.txt to catch the crash. Hopefully you can make sense of it...lol.

Question Install apk from local storage

Hey guy's, I hope somebody can help me out here. I can't find any explanation on internet. I want to install an apk from the local storage on my Rog phone 5 ( android 12,un rooted) .
In the old days it was pretty simple, just a slide to activate the "allow unknown sources", click on the apk file and it would install. Now on the rog phone 5 in the apps&notifications, special app-acces, install unknown apps it only shows a few apps that I can give permissions to install from unknown sources. Like Chrome, file manager, gmail, brave browser etc. ( see picture). So I give the file manager or brave the permission,restart the phone, go to the apk in the file manager but it won't install.
It will just show the contents of the apk. If I select the apk I can remove it, rename it, compress it, anything but install it.
I can choose open with brave but still nothing happens. I tried downloading an app in the playstore to install apk files but it won't even list the apk file. I have no clue why they made something that used to be so easy so complicated. So I hope somebody can enlighten me how to install an apk on this phone. Thanks in advance!

Have you enabled install unknown apps in developers options ? Special app access allows you to allow/not allow individual apps to install unknown apk files. I think you have to enable it in developer options for the native installer first. I may be wrong but it's worth checking.

I'll go check if the option is there and let you know. Tnx man.

The only thing I found was " force app allowance on external drive" and but it changed nothing.

Piriroekoe said:
The only thing I found was " force app allowance on external drive" and but it changed nothing.
Click to expand...
Click to collapse
you could try
Code:
adb shell settings put secure install_non_market_apps 1
adb shell settings put secure unknown_sources_default_reversed 1
that would be from terminal on pc or you could install settings database editor from play store and grant it permissions via adb and you will have gui to change system settings

Could you please walk me through how to do this? Tnx.

Piriroekoe said:
Could you please walk me through how to do this? Tnx.
Click to expand...
Click to collapse
Ok, first I guess I need to ask some questions. Have you tried a different file manager, installed thru play store ? How many .apk files have you tried to install ? If it is just the one app that you have in storage it may be corrupt. Have you tried a fresh copy of it ? Is it an old app and is it compatible with your Android version ?
I don't know what I was thinking, that isn't in developer options anyway, it's in security. It would seem odd for them to remove the ability to install personal apk.