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.
Related
a few days ago i mentioned that i kept getting a force close in the martket and i couldnt install any app from it
i did several wipes and noticed as soon as i apply the dark facebook or transparent facebook widget, i get the force close on the market.
so i think that is the problem.
anyone else facing this?
can someone check if the same thing happens with them?
however this issue is resolved when i uninstall updates from market using application manager. but i have to do that everytime i want to install an app from the market.
what morph are u using
all of these cause the same problem for me:
http://forum.xda-developers.com/showthread.php?t=652661
http://forum.xda-developers.com/showthread.php?p=6325029#post6325029
Did you apply any morph that modified framework-res.apk ?
I've noticed that sometimes it screws up the UIDs and the Market app loses the PACKAGE_INSTALL permission.
Only way out I've found is to restore your most recent nandroid backup.
I'm sure theres a manual way to fix this (if this is even your issue), but havent found instructions yet.
Its likely not this facebook morph as it includes only images and xml, and cannot affect any other part of the system.
Post your logcat around the time the market force closes.
britoso said:
Did you apply any morph that modified framework-res.apk ?
I've noticed that sometimes it screws up the UIDs and the Market app loses the PACKAGE_INSTALL permission.
Only way out I've found is to restore your most recent nandroid backup.
I'm sure theres a manual way to fix this (if this is even your issue), but havent found instructions yet.
Its likely not this facebook morph as it includes only images and xml, and cannot affect any other part of the system.
Post your logcat around the time the market force closes.
Click to expand...
Click to collapse
yes i did apply themes that modify framework-res
how can i post a log of this as you mentioned?
can you tell me how to get the log from my phone?
1. open a command shell. Start-run-cmd
2. Type in: adb logcat
3. On your phone, wait til you get the error, click close
4. On the command shell press control-c to stop.
5. Select the part that contains the error. You may have to use the top right window button to choose edit-mark and then edit-copy
6. Paste the log here or better still on www.pastebin.com
try this
http://forum.xda-developers.com/showthread.php?t=673870
This works but I have to do it everytime I want to install an application
britoso said:
1. open a command shell. Start-run-cmd
2. Type in: adb logcat
3. On your phone, wait til you get the error, click close
4. On the command shell press control-c to stop.
5. Select the part that contains the error. You may have to use the top right window button to choose edit-mark and then edit-copy
6. Paste the log here or better still on www.pastebin.com
Click to expand...
Click to collapse
thanks for this
now since i've uninstalled updates, i didnt get any force closes
i'll keep checking, if i do get one, i'll post the logcat here
thanks for your help!!
[Rom Add-On] Clean & Stable Add-On For All Stock Firmware V4[21/07/11][New Market]
Please Do Not post this elsewhere
This will not work on newbie5 modded stock rom
Hi All.
I have made this rom add-on to try to keep the device as clean and stable as possible. I could add custom boot screens, launcher (like launcher pro) and much more, but I have only added the essentials. As i think everyone has different tastes and the extras are easily installed. I have chosen to use the software tool which is part of the stock firmware, this insures easy installation on any os. No usb recovery drivers or clockwork mod needed!
V4 Rom Add-On includes:
Market (New)
Google Talk
SuperUser
3D Gallery
Google Calendar
Visionary
YouTube App
(removed titanium backup due to size restraint, can be installed through market)
V4 can be installed over the top of V3, titanium backup will remain
V3 Rom Add-On includes:
Market (Old)[Full]
SuperUser
3D Gallery
Google Calendar
Visionary
Titanium BackUp
YouTube App
If you cannot sync contacts or calendar. Please use this fix http://forum.xda-developers.com/showpost.php?p=12385012&postcount=131
I have updated the rom add-on now so if you use the version with -1 at the end, it contains the fix.
Optional .ZIP's
Small Taskbar (For Advent v1.09 and v1.10 firmware only)
Gmail
Contacts
Google Maps can be downloaded from the market
I highly recommend launcher pro, its available from the market. It is a lot better than the stock launcher, and the payed for version has some great widgets.
Button savior, also available from the market. Is also for me a must for the vega, it adds the missing buttons as on-screen buttons.
This V3 update is more of a clean up. There was a lot of confusion over the multiple .rar parts and some compatibility issues with v1.10 POV firmware. I have now removed the small taskbar and added it as a update, so now my rom add-on is fully compatible with the pov firmwares and does not require multiple .rars. Advent firmware users who want the small taskbar, simply flash the Small_Taskbar.zip. If you have already installed my v2 version there is no need to update, as i said its more of a clean up. There are a few added apps, but they are easily installed.
Install Instructions:
1 - Download the .zip you wish to flash. Copy the .zip to "software update" on your SDcard.
2 - Navigate to settings/software tool/software update on vega, and touch the .zip
3 - Device will reboot and a "out of a box" android will appear and install the parts.
You will not lose any of your apps/data from this process.
Please make sure you have sufficient power to apply Add-On, i would recommend 50%
Root Instructions:
Root is required for some apps. Eg Button savior requires this for it to function fully.
1 - Open visionary
2 - Touch "Temproot now" the screen will go blank for a few seconds and return to the visionary page. Then click it again. (i have no idea why it is required to do this twice, but in my experience it is necessary)
3 - Touch "Attempt Permroot now" After a few seconds a super user prompt will appear, allow the prompt. Then device will reboot and it should be rooted.
If Flash does not work, navigate to /etc/shuttle_data and run the flash.apk. That will reinstall the included flash version.
If all apps are not showing in the market please follow ice-mn tip. Many thanks to him for this.
ice-mn said:
Since there are several post discussing this I have opened this thread instead answering the same on all of them.
To get all apps (at least all I have looked for ) you only have to follow the steps described.
1. Go to Manage Applications (in settings/applications)
2. Press the running tab and select market (if market is not running execute it)
3. Select Market from running apps. And:
Press Clear Cache
Press Force Stop
4. Go back and Select Google Services Framework. And:
Press Clear Data (answer ok on the message warning)
Press Force Stop
5. Try to run Market. You will get an error message.
6. Reboot the device and run market twice (the first one you will get the error message again).
Click to expand...
Click to collapse
Thanks to skyball2 and alphaola for supplying stock POV frameworks
Thanks to demonknight9 for posting the original market_update.zip
Check out my custom boot animation Here: http://forum.xda-developers.com/showthread.php?t=950304
Hi mate just got my vega so this is very welcome,thank you very much
shaddy666 said:
Hi mate just got my vega so this is very welcome,thank you very much
Click to expand...
Click to collapse
Welcome to xda dev. I see this is your first post
Glad you find it useful. i hope to update it soon with a complete package (Flash etc), i just need some where to host it.
original_ganjaman said:
Hi All.
I have been playing with the market enabler (thanks to demonknight9). I have added the small taskbar framework to the update. so now you can have the market and small taskbar on a stock v1.08 vega. More gmail apps can be downloaded from the market. As demonknight9 says its very easy to install. No need for CWM.
1 - Download market_update0.zip file and put on storage card.
2 - Navigate to settings/software tool/software update, and navigate to location of market_update0.zip.
3 - Run the market_update0.zip
4 - Device will reboot and install the parts.
You will not lose any of your apps/data from this process.
It looks like flashing things to are vegas is easy, can be done from the software update. The zip is unsigned. More things can be added but i thought i would keep it simple to start with.
Hope its useful
I have made one with flash,spare parts and superuser as well, but it is larger than i can upload to xda dev. if anybody has somewhere i can upload i would be gratefull.
EDIT:I have added the flash.apk to enable flash, visionary to fully root the device and spare parts to disable compatibility mode for games to the attachments.
Click to expand...
Click to collapse
Good idea to add the bits. Why don't you upload it to fileape? Easy peasy to open an account. Just chose a username and a pass, no email, no confirmation just a plane doddle. go here; www.fileape.com
Upload it to mediafire, you dont even need to register an account to use it
How long does the market updater take, my vega been hanging for about 10 minutes, is this normal?
Walesraider said:
How long does the market updater take, my vega been hanging for about 10 minutes, is this normal?
Click to expand...
Click to collapse
Which part is it hanging on, once run the device should reboot, then a picture of a box with a arrow appears, and the progress bar bellow turns orange. I have flashed this and different versions with no problems.
demonknight9 said:
Good idea to add the bits. Why don't you upload it to fileape? Easy peasy to open an account. Just chose a username and a pass, no email, no confirmation just a plane doddle. go here; www.fileape.com
Click to expand...
Click to collapse
I will take a look at that, thanks. Hopefully i will add a updated one over the weekend.
Once i selected the update zip the screen dimmed but didnt reboot - no picture of the green box. would you suggest i power off and retry?
Walesraider said:
Once i selected the update zip the screen dimmed but didnt reboot - no picture of the green box. would you suggest i power off and retry?
Click to expand...
Click to collapse
sounds like nothing has been flashed, yeah try powering the device back on and trying again.
Ok i've restarted the vega but iv've come back to the dimmed screen..any ideas?
Any ideas why I can't see most of my apps in the marketPlace
LauncherPro etc are not found when I search for them
Jezwick said:
Any ideas why I can't see most of my apps in the marketPlace
LauncherPro etc are not found when I search for them
Click to expand...
Click to collapse
I am looking at that now. It only looks like a few apps are not showing. Not to sure why, i have tried changing the market files but no go.
Walesraider said:
Ok i've restarted the vega but iv've come back to the dimmed screen..any ideas?
Click to expand...
Click to collapse
Thats very odd. I have re-flashed 4 different versions in the last 10 mins with no problems. Try to hold the power button down for six seconds to totally shut down. Plug the device into the power. Then try a reboot. If that does not work then you are going to have to go into recovery and re-flash the stock rom. Sounds like the flash got interrupted for some reason.
original_ganjaman said:
Thats very odd. I have re-flashed 4 different versions in the last 10 mins with no problems. Try to hold the power button down for six seconds to totally shut down. Plug the device into the power. Then try a reboot. If that does not work then you are going to have to go into recovery and re-flash the stock rom. Sounds like the flash got interrupted for some reason.
Click to expand...
Click to collapse
Many thanks, I re-installed the stock rom after putting it into recovery. I tried the market updater again and it worked no problem. Thinking about it now I was on low battery so that why it might not have worked 1st time round..
Walesraider said:
Many thanks, I re-installed the stock rom after putting it into recovery. I tried the market updater again and it worked no problem. Thinking about it now I was on low battery so that why it might not have worked 1st time round..
Click to expand...
Click to collapse
I never thought to put a warning on low battery. I will add it to the first post. Glad you got it sorted
Is there any way to revert back to large notification bar? It does look good but It's a little too small for me.
original_ganjaman said:
I am looking at that now. It only looks like a few apps are not showing. Not to sure why, i have tried changing the market files but no go.
Click to expand...
Click to collapse
Try "Market Enabler" -> http://code.google.com/p/market-enabler/
WaPeR32 said:
Try "Market Enabler" -> http://code.google.com/p/market-enabler/
Click to expand...
Click to collapse
I tried it and it work it. I set up to US T-mobile.
inberno said:
I tried it and it work it. I set up to US T-mobile.
Click to expand...
Click to collapse
I'm glad!
Me alegro!
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.*
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.
Hello Guys,
I come in need of a help,
I'm writing from my computer now,
Yesterday my phone was working fine,
Today morning, I updated the apps on my phone; amongst the updates was android system webview.
After a reboot, my phone is unresponsive, it won't open any of the apps from that point.
I reboot again, since keyboard doesn't work, I used the OTG cable to use the physical keyboard to enter the password and get in. Tried entering setting to uninstall that crap app, settings is unresponsive.
No SIM services, no keyboard, no fingerprint, no settings etc.. basically nothing works and everything says "unresponsive and asks to either wait or close".
The only thing I have now is TWRP Recovery, and I'm inside it now.
I've wiped Cache + Dalvik / ART Cache : Result still same, nothing works.
I mailed [email protected] (which is provided in the app's "Developer" section) about this and got a reply that the mail is no longer being monitored.
Can someone please let me know how I can remove android system webview by using TWRP ? So that I can enter the phone back again as normal..
Device Details:
Lenovo K8 Note
Android 7.1.1 Nougat, (Never updated the OS)
Device has been rooted and has recovery options.
I think you can find WebView module in Magisk respiratory so I suggest you give that a try. Flash it and I think it will be fine as long as you have Magisk installed, of course.
dedq said:
I think you can find WebView module in Magisk respiratory so I suggest you give that a try. Flash it and I think it will be fine as long as you have Magisk installed, of course.
Click to expand...
Click to collapse
Thanks, I couldn't quite understand that..
I've never read/seen a need for Magisk so far.. so may I know what is the procedure to be done here...?
I do read Magisk is a systemless Root, (I already have SuperSu, is that the same functionality? (though I can't open anything that is))
Find the Magisk zip on Google and flash it over TWRP.
Head over to the Magisk module site and you will be able to find an alternate WebView module you can flash. It will be in zip format so I guess you will need USB to transfer those files to your phone since you cannot use it to download modules.
dedq said:
Find the Magisk zip on Google and flash it over TWRP.
Head over to the Magisk module site and you will be able to find an alternate WebView module you can flash. It will be in zip format so I guess you will need USB to transfer those files to your phone since you cannot use it to download modules.
Click to expand...
Click to collapse
Understood, thanks..
Will try this out.
KillerBeeSama said:
Understood, thanks..
Will try this out.
Click to expand...
Click to collapse
Give it a try and come to tell if you have sorted it out.
If not, you will probably need to flash your ROM again hoping the application won't stay updated but to back to stock version.
dedq said:
Find the Magisk zip on Google and flash it over TWRP.
Head over to the Magisk module site and you will be able to find an alternate WebView module you can flash. It will be in zip format so I guess you will need USB to transfer those files to your phone since you cannot use it to download modules.
Click to expand...
Click to collapse
Oh, one more thing,
Does this procedure mean, I'll lose TWRP and SuperSu?
Can I not just downgrade the android system webview manually itself?
KillerBeeSama said:
Oh, one more thing,
Does this procedure mean, I'll lose TWRP and SuperSu?
Can I not just downgrade the android system webview manually itself?
Click to expand...
Click to collapse
You won't lose TWRP but I am not sure about SuperSu since it's very old and people don't use it from the time Magisk appeared. I don't think you will be able to have both TWRP and SuperSu.
It would be good for you to just uninstall the updates of WebView if you can use your phone at all. That would solve the problem.
TWRP basically is a menu what allows you to select and apply ADB and/or Fastboot commands.
SuperSU is a Superuser access management tool: it requires SU binary got installed on Android.
Both mentioned sofwares are completely different things, don't depend on each other.
BTW:
I always root Android without the need to make use of Magisk or SuperSU.
So, I went through these
[MAGISK] [MODULE] Webview Manager
Welcome to the XDA home of Webview Manager by Androidacy Read about it on our blog: https://www.androidacy.com/tag/webview-manager/ What is this? This magisk module allows to install several webviews and browsers, replacing the stock one with...
forum.xda-developers.com
Android system Webview installed but not used by apps
I downloaded and installed the latest version of android system WebView from the app store on my android tablet (running 5.0.2). But apps still go on using the old webview version (39.0.0.0). Ho...
android.stackexchange.com
SystemWebView releases
SystemWebView releases
www.bromite.org
Installing SystemWebView
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser! - bromite/bromite
github.com
I got is, .. the adb and appt command says "not found". so.. confusion. and I also see that Bromite System Webview might or might not work on some apps..
So,
Is there a way to downgrade an app through recovery mode
or delete that app's data and start from scratch for that alone?
or is there a way to flash an old Android System Web View through TWRP?
Please help, I have spent the whole day trying to fix this.
I already have SuperSu and it seems if I need to goto Magisk (which is just for that other webview application, I have to do a lot of rolling back and applications going away, ) I don't want that..
Let's keep the Magisk idea as last resort and please let me know if there is any other way to delete the entire Android Webview related stuff and start from beginning.
<bump>
Attached the attack of errors. (these are just few of the ANR popups, there are lots more.. at the last screen you can see even settings won't respond)
My recommendation: Reflash phone's Stock ROM to get rid off of all modifications you applied so far, then restart modding from the scratch.
jwoegerbauer said:
My recommendation: Reflash phone's Stock ROM to get rid off of all modifications you applied so far, then restart modding from the scratch.
Click to expand...
Click to collapse
Just because of one application?
I just want that android webview gone/replaced with a stable one, is that not possible without destroying everything?
Thanks everyone.
we have a solution,
In my case, uninstalling the Xposed framework fixed it for me..
So, while working on this issue I had made a flow map and a log of what is done and its results, may be someone else can benefit from it in the future..
Spoiler: Tries and results
Even starting the entering phone itself is a big issue, because the keyboard applications don't come up; fingerprint doesn't work on first boot as a security measure as well; connected physical keyboard to OTG to phone to enter password... then greeted with lots of errors of all the applications.
Asking people blowed over 'to buy a new phone'
Posted to Reddit, no replies
Posted to Google support, got crappy bot_ish answers; who even hires these people!
Posted to XDA, have some ideas worth trying
Unpacking the system web view.apk on computer gives crap details as it is almost completely encrypted.
Going rabbit hunting through the rabbit hole, checking each folders on "/"
found something similar /system/app/WebViewGoogle/WebViewGoogle.apk
Quick google search confirms that I’m on the right path to finding it...
May be data or XML is somewhere too?
Deleted(copied and deleted) /system/app/WebViewGoogle/WebViewGoogle.apk
Result, Same
Then Reverted
PS: Original Copy at ext_sdcard
Replaced the existing one (92.0.4515.115 with 90.0.4430.210)
Result, no changes.
Then reverted with the crappy original
May be adb will install properly?
Tried adb commands on phone on TWRP, doesn't work
Tried adb from computer to phone, unable to connect to phone.
Was doing it wrong, while in TWRP, I need to initiate "ADB Sideload" and then connect from PC (with Firewall allowed)
then "adb devices", shows connected device with serial number
after the above, the adb push keeps saying "error: connect failed: closed"
turning phone ON and connecting for additional settings (USB debugging) pops "mtp host failed" as soon as I wire..
Started the phone, switched over to Guest account, (oddly seems stuff there are kind of better with lesser error messages), tried launching playstore and wifi, both need password which I don't have, entering settings, hangs for a while, quickly go to apps and uninstall updates for android system web view.. web view becomes 0.0.1
results, fail
Created a temporary user account on phone whilst booting, (because of the observable lesser apps running if I switch over from main..)
added my gaccount on it,
launched playstore to update the android system web view..
the update is stuck at 60%~70 %each time and is unable to complete..
took the v90 application that is on pendrive, connected otg.. and started to install application manually from there..
it said, no space.. even though there is around 4 GB free... continued to disable other applications, such as chrome, youtube, drive etc..
still unable to install the v90 application
even installing other apps (sudoku example) have the same issue,
and then I see a popup that package manager has stopped working (aha! so that itself doesn't work, then can't install),
Went to see if I can change something on developer options, developer option wont come up even after 7+ taps.. hmm strange, may be only main account can have dev options.
While at it, swapped out the Gboard with older AOSP keyboard (retaining Fleksy though).
Rebooted and tried again.. no fix yet..
Atleast I don't have to switch to physical keyboard now for every reboot, since the inner older keyboard comes for first boot.
By TWRP, removed existing app and replaced with v87; doesn't seem to be any different, same errors...
Was about to install the Magisk but it seems to have lots and lots of catches to it, and things to-do before I can go to that...
Continuing investigation on how to downgrade and get back to older state
Through TWRP, deleted the app folder from /system/app/WebViewGoogle/WebViewGoogle.apk
researched to see if there is something else to delete, couldn't find much... proceeding from what we know...
Removed ATSystem.apk (3C's helper) from /system/priv-app just in cast (copy placed at ext_sdcard)
result no change..
Started at around 31-Jul-21 13:00 and went on till 01-Aug-21 01-26 pausing to for the day to rest...
Restored App Folder back to /system/app/WebViewGoogle/WebViewGoogle.apk
WebViewGoogle.apk is v90 again.. (the original seems to be missing, meh, not like it's going to fix)
reboot, result, no changes.
Starting step to install magisk
Removing xposed now..
wiped dalvik cache
rebooting
Kind of stable!!!
Everything seems to work?!?!
Firewalled all app except playstore and mail,
mail seems to work, but can't open the mails (just the headers are received), clicking on the mail says "unable to inflate webview"
aha, I forgot that I have v87 still, if I update that again, will it work (if it doesn't we know how to revert now)
proceeds to update v87 to latest
reboots,
I guess issue resolved by uninstalling xposed, next step to enter phone and move data to safe zone and think about next step.
Are you using xprivacylua?
VD171 said:
Are you using xprivacylua?
Click to expand...
Click to collapse
No, I do remember hearing about it.
GUys, i have installes a system webview on my Samsung J2 core, after restarting my phone stuck on int boot animation, then i do the hard reset combination keys and keeps from restarting. what should i do.
TUPANGPUTi23 said:
GUys, i have installes a system webview on my Samsung J2 core, after restarting my phone stuck on int boot animation, then i do the hard reset combination keys and keeps from restarting. what should i do.
Click to expand...
Click to collapse
Oh... sorry to hear that.
I don't know the solution to that, because mine is rooted I was able to get into the custom recovery and fix things.. not sure what can be done here for your case, (I do know that the old samsung's default recovery is kinda unreadable for English speakers)
So, I think it's best for you to start a new thread in the forum, because if you make a new thread there's a higher chance of reply than this thread which is already marked solved.
(plus. please do attach any photos even crude it may be, still will help people see and suggest actions)