Related
Hello,
If an application doesn't have an uninstall button is there a way to remove it?
I'm specifically wanting to remove the market app. I think I screwed it up when I installed it and it's completely useless. This isn't a "market fix" situation, it won't open for me at all. I tap, get a quick screen flash and it goes right back to home screen.
I was wondering if I could uninstall, then try to re-apply properly and hopefully get a better result.
Thanks.
Neudle said:
Hello,
If an application doesn't have an uninstall button is there a way to remove it?
I'm specifically wanting to remove the market app. I think I screwed it up when I installed it and it's completely useless. This isn't a "market fix" situation, it won't open for me at all. I tap, get a quick screen flash and it goes right back to home screen.
I was wondering if I could uninstall, then try to re-apply properly and hopefully get a better result.
Thanks.
Click to expand...
Click to collapse
Guessing here... depending on the version you're running.
Settings | Applications | Manage Applications | Running | select Market | force-stop | uninstall
I'm running the stock 3389 firmware.
Market shows up under system applications, no uninstall button. I can do force stop but that's it.
**
Maybe I don't need to bother trying to uninstall or remove the market. I'm reading through the enhancement thread now, I haven't installed that yet. Could be what I need to get the market working.
using Root Explorer, if you don't have it, get it otherwise you'll have to do this using adb shell or terminal, /system/app, mount r/w, rename Vending.apk to Vending.apk.bak that will uninstall vending. I would do a data/cache wipe using TI first on Market. Then reboot and rename back to Vending.apk, I've had to reinstall it before due to issues.
chad
HKChad said:
I would do a data/cache wipe using TI first on Market. Then reboot and rename back to Vending.apk, I've had to reinstall it before due to issues.
chad
Click to expand...
Click to collapse
Sorry, I don't know what TI is for doing the data/cache wipe...
Neudle
Neudle said:
I'm running the stock 3389 firmware.
Market shows up under system applications, no uninstall button. I can do force stop but that's it.
**
Maybe I don't need to bother trying to uninstall or remove the market. I'm reading through the enhancement thread now, I haven't installed that yet. Could be what I need to get the market working.
Click to expand...
Click to collapse
I was using stock 3389 and of course w/o the market. After I installed the enhancement package and did the market fix according to the instructions I now have the market and it works fine as does the gtab itself. I have a feeling if you did the same it may fix your problem. If not, at least you'll have the updated tegra drivers. Good luck!
I hope that this is in the correct forum and if not I apologize.
The latest update of BusyBox hosed my phone and when I reflashed the Classic Rom, by tommytomatoe, I of course got a notification to update BusyBox and bunch of other apps. I did a manual update for all of the apps except BusyBox and have been repeating at every update.
Is there a way to put BusyBox on "hold" so that if I press Update All it will not update with the rest of the apps. This would also be useful for other apps too to prevent them from updating.
Any suggestions would be appreciated.
Doc
I think ti backup can freeze them...
razr maxx - stock rom - rooted
use titanium backup.. bt ul need pro version in order to use the freeze option
Sent from my HTC One V using xda premium
I have the pro version of Titanium but if I freeze the app won't it prevent it from running when it is needed by other apps? I just want to freeze the update part.
Doc
I think the "remove market link " in TB should accomplish that
Sent from my M886 using Tapatalk 2
This is very easy.... First click update all then mannualy stop that app you dont want to update.... Click on cross sign on app...
docesq said:
i hope that this is in the correct forum and if not i apologize.
The latest update of busybox hosed my phone and when i reflashed the classic rom, by tommytomatoe, i of course got a notification to update busybox and bunch of other apps. I did a manual update for all of the apps except busybox and have been repeating at every update.
Is there a way to put busybox on "hold" so that if i press update all it will not update with the rest of the apps. This would also be useful for other apps too to prevent them from updating.
Any suggestions would be appreciated.
Doc
Click to expand...
Click to collapse
Hi, first post
I flashed my TMOBILE US [SGH-T999] SIII with root66 and all went well. verified with rootkeeper I'm indeed rooted. Problem is when I first configured superSU i checked hide from apps list (figured id still be able to get it in /system) So although it asks for permission and still fully functional I cannot open the app to change the configuration. There was some codes *#*#1234#*#* amongst others I thought would bring up the app, but because the sim is no longer registered to a network it just gives a network error.
This has been going on for a week and would really appreciate a solution. Going to google play doesn't show any options. just a picture. If i disable in manage apps i can then deactivate on google play, but it didn't help. Also re flashed rom and nothing changed.
Should be able to open the app somewhere on the phone right? use file explorer to delete some config file that will reset to default?
irvington said:
Hi, first post
I flashed my TMOBILE US [SGH-T999] SIII with root66 and all went well. verified with rootkeeper I'm indeed rooted. Problem is when I first configured superSU i checked hide from apps list (figured id still be able to get it in /system) So although it asks for permission and still fully functional I cannot open the app to change the configuration. There was some codes *#*#1234#*#* amongst others I thought would bring up the app, but because the sim is no longer registered to a network it just gives a network error.
This has been going on for a week and would really appreciate a solution. Going to google play doesn't show any options. just a picture. If i disable in manage apps i can then deactivate on google play, but it didn't help. Also re flashed rom and nothing changed.
Should be able to open the app somewhere on the phone right? use file explorer to delete some config file that will reset to default?
Click to expand...
Click to collapse
Hi, to open supersu through the dialpad, please enter the following:
*#*#1234#*#*
or
*#*#7873778#*#* which spells(*#*#SUPERSU#*#*)
If that didn't work, check if supersu is still installed by going to manage applications.
Sent from my Droid Incredible 2 using Tapatalk.
antoniodz95 said:
Hi, to open supersu through the dialpad, please enter the following:
*#*#1234#*#*
or
*#*#7873778#*#* which spells(*#*#SUPERSU#*#*)
If that didn't work, check if supersu is still installed by going to manage applications.
Sent from my Droid Incredible 2 using Tapatalk.
Click to expand...
Click to collapse
Yeah mentioned the codes in my post. my girlfriend has a deathgrip on the phone right now but i'm pretty sure the exact error was: Not registered on network. I also mentioned that superSU is indeed installed cause I can clear su's data, etc from the manage apps area. I use groove IP for phone calls and I've been putting the code in the phone settings not the groove voip app if that matters.
bumped after a few days of waiting patiently.
Hi i was having similar issues, did you try
*#234#* instead of *#*#234#*#* that worked for me before although my issue now is different.
i was getting an error and work around it by installing
System app remover (root) from play store
then went to apkmanger and click on reinstal Supersu, that bring back the icon
that did not solve my problem of the dialing code not working anymore, but it got me to super su app
hope it helps
Ajabis said:
Hi i was having similar issues, did you try
Click to expand...
Click to collapse
you just woke up a sleeping thread. its one year old, so I am sure it has been resolved.
Check this out! Links to useful Guides and " Banned " Documentaries
My Google account was being wiped out in front of my eyes almost every other time i rebooted. After some thread reading and trial and error I finally figured it out. Its been about 18 hours and over 15 reboots (EDIT: Few days now ) either via reboot menu, wanamXposed module and adb, I have not lost my account so far.
This is still being tested, so affected users please test and comment how it worked for you.
There are hundreds of posts out there that tell you the fix is to be on Google play Store version 4.4.21 and many of them have reported that it works. Unfortunately many including me, were on the very same version and yet Google account was being wiped no matter what. Thats when i realized, it is not just being on 4.4.21, but having that version as a system app, instead of having the version installed as an update. The difference is, when you have version 3.x.x installed as a system app, which updates itself to 4.4.21, it does not update the original app, but instead installs updates in the /data partition. So seeing version 4.4.21 in the Playstore app 'About' settings does not mean anything.
Verify if you are on an affected release.
Go to Setting >> more >> Application Manager >> Downloaded. If you see 'Google Play Store' you may be affected.
Now go to the application managers "All" Section (swiping leftward from 'Downloads' section) and navigate to 'Google Play Store'
You will see the version number of your app. Next to it, you will see two buttons, One of them may be "uninstall updates" If you see this option, your version number means nothing. Don't be fooled by it, you have may 4.4.21 installed, but in your /data/app directory.
If the above was true, you have an older version of playstore installed as a system app, and have the latest version installed as an update over the old version in the /data partition.
Instructions
Flash GoogleWipeFix_Flash_CWM.zip from Clockworkmod.
PS: This really only removes your existing Google Play Store, flashes v 4.4.21 and clears data. You may as well flash it, nothing to loose.
Click Show content for Manual Instructions (Not needed if you chose to flash instead).
You do not need this if you flash using my zip. This is for Manual Testing only.
If you are not already on PlayStore version 4.4.21 then download version 4.4.21 and place in in your SDCard as /sdcard/Phonesky.apk
DOWNLOAD
Google Play Store 4.4.21
Instructions for shell users :
Code:
su
mount -o remount, rw /system
cp /system/app/Phonesky.apk /system/app/Phonesky.apk.bkp
mv /data/app/com.android.vending-1.apk /data/app/com.android.vending-1.apk.bkp
cp /sdcard/Phonesky.apk /system/app/Phonesky.apk
chmod 644 /system/app/Phonesky.apk
reboot
Instructions for Root explorer users
Re-mount /system as read-write
Backup /system/app/Phonesky.apk
Backup and Delete /data/app/com.android.vending-1.apk (TIP: you may see warnings that PlayStore Stopped, Thats ok!)
Copy /sdcard/Phonesky.apk and overwrite /system/app/Phonesky.apk
Give the new apk appropriate read permissions to all. rw-r--r--
reboot
Click to expand...
Click to collapse
Troubleshooting help
If it does not work for you, it would be of great help if you could post below details.
What rom are you on?
Please check the following:
Go to application manager >> Google Play Store and tel me if you see the button "Uninstall updates" next to "Force Stop"
If you have "Uninstall updates" you need to click it, and then repeat the whole procedure again.
Do you have access to adb or terminal emulator app? if yes, please give me the output of the following.
Code:
su
ls -l /data/app/com.android.ven* /system/app/Phonesky.*
Click to expand...
Click to collapse
I added a CWM flashable zip. Try that if it didn't work earlier.
XDA:DevDB Information
GoogleWipeFix, a Tool/Utility for the Samsung Galaxy Note II
Contributors
kkoolpatz
Version Information
Status: Testing
Created 2013-11-02
Last Updated 2013-11-05
I use my own cooked rom which is posted in the forums as well.. I have hardly had any gapps issues.. Had them once in the beginning but flashing the latest gapps solved everything..!
Thanks for sharing
kkoolpatz said:
Verify if you are on an affected release.
Go to Setting >> more >> Application Manager >> Downloaded. If you see 'Google Play Store' you may be affected.
Now go to the application managers "All" Section (swiping leftward from 'Downloads' section) and navigate to 'Google Play Store'
You will see the version number of your app. Next to it, you will see you buttons, One of them may be "uninstall updates" If you see this option, your version number means nothing don't e fooled by it. you have may 4.4.21 installed, but in your /data/app directory.
Click to expand...
Click to collapse
I am using Tigra v.3 ROM, which has the 4.4.21 version as system app and still I had the Google account wiped yesterday after a reboot from Wanam Xposed.
So maybe your fix solves some problems, but in my case...
Thanks anyway!
My ROM users are already on 4.4.2.1 by default (removed everything related to old versions) and they still have account lost.
The problem is only in XXUEMI6, XXUEMJ2/5 don't have this problem.
Thanks for sharing
tried this on my n7105T
no i no longer get the force close / crash message
just no connection (like i was getting prior to trying a million other fixes)
including factory reset
I haven't been on the forums much lately but can't see anything about this - what is the bug exactly? All your google data being deleted on just the account being removed from the phone? Or something else entirely?
dhuewes said:
I am using Tigra v.3 ROM, which has the 4.4.21 version as system app and still I had the Google account wiped yesterday after a reboot from Wanam Xposed.
So maybe your fix solves some problems, but in my case...
Thanks anyway!
Click to expand...
Click to collapse
Its just been one day, so i'm hoping this fix stays permanent. Are you sure you do not have /data/app/com.android.vending-1.apk installed?
fliptechnologies said:
tried this on my n7105T
no i no longer get the force close / crash message
just no connection (like i was getting prior to trying a million other fixes)
including factory reset
Click to expand...
Click to collapse
What do you mean by no connection? I am not sure if this will apply to your device since this caters specifically to Note 2 leaked roms.
Tamen said:
I haven't been on the forums much lately but can't see anything about this - what is the bug exactly? All your google data being deleted on just the account being removed from the phone? Or something else entirely?
Click to expand...
Click to collapse
If you are on one of the affected roms, after you reboot Google account is totally removed. As if it was never added. Its known to happen on Note 2 android 4.3 leaked MI6 rom
I've tested your possible Fix.... Had 3 reboots in total now... so far so good... No G account yet....
Sent from my GT-N7100 using XDA Premium 4 mobile app
I just did try.
I didnt have vending-1.apk in my data folder so didnt do anything with that.
Also when we copy phonesky.apk , do we need to set permission to rw.r.r ???
I actually did it. And now trying.
Sent from my GT-N7100 using xda app-developers app
I just moved the updated version to /system/app and removed Phonesky.apk.
I'm gonna check out if it does anything, smart tip btw, never thought of this.
I've given it a try, thanks.
Thanx man
Sent from my GT-N7100 using XDA Premium 4 mobile app
Yes,the fix works...rebooted nearly ten times today,no google account loss.
Just remember to set permission as rw-r-r for phonesky.apk after replacing the old one.
akp.ajinkya said:
Yes,the fix works...rebooted nearly ten times today,no google account loss.
Just remember to set permission as rw-r-r for phonesky.apk after replacing the old one.
Click to expand...
Click to collapse
Thanks, I'll add the permissions part to OP
I followed your full procedure, the problem persists, wanam v4.0 (mi6).
hi
I have noticed that whenever i fiddle with xposed, my account gets wiped. Otherwise no loss on reboot. Just what i have observed.
kkoolpatz said:
Thanks, I'll add the permissions part to OP
Click to expand...
Click to collapse
Worked for me on Hurricane v5, note3 apps and Superwolf theme 10.5 -- Thanks
Alipk52 said:
I followed your full procedure, the problem persists, wanam v4.0 (mi6).
Click to expand...
Click to collapse
Thanks for reporting. I wonder if you need to remove .odex file since wanam is an odex rom
Please check the following for me.
Go to application manager >> Google Play Store and tel me if you see the buttons "Uninstall updates" and "clear data"
If you have "Uninstall updates" something went wrong in your procedure.
Do you have access to adb or terminal emulator app? if yes, please give me the output of the following.
Code:
su
ls -l /data/app/com.android.ven* /system/app/Phonesky.*
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.