Related
Nexus 5, 4.4.4, dalvik runtime. Currently on cyanogenmod 11, but this problem started prior.
I rooted my phone, initially to run xposed framework. I actually got it installed and opened, but I noticed I couldn't install any modules. Uninstalled, tried to reinstall, found I couldn't sideload any apks. Cancel button works fine, but install button does not respond to touch in any way.
Everything I have tried:
Rebooting
Unrooting/reflashing stock
Rerooting
Using various apk installers/file managers. They all still bring me to the install screen where I can't push install, so they're unless
Clearing caches (dalvik, package installer)
Making sure all screen filter apps are off
Making sure all security options are correct (do not verify app, allow unknown sources)
Flashing a new Rom entirely (cyanogenmod)
I'm at a loss. Are there any options left to try that may fix this?
First, root has nothing to do with your issues. When you say install button doesn't work, what install button are you taking about? And how are you trying to side load an apk? Are you using an app, recovery, or what?
Sent from my Nexus 5 using XDA Free mobile app
Do you have echo lock screen notification installed?
#stayparanoid
Unfortunately I can't post an image of the install screen because I'm still a new poster. I usually just try to install apps by navigating to them in my file manager and clicking on them. Nothing special. The install screen is the default holo one that pops up.
Welp, turns out it was Echo Lockscreen. That's a massive bummer...loved that app! Thanks Pirateghost.
Yet again, all thanks go to @jrkruse for this one. I have modified his zip to work on the Verizon S7 flat. The ROM is silky smooth since it uses the factory kernel. The instructions have been tweaked to work for the Flat. I can confirm that SafetyNet passes using this method.
A MASSIVE thanks goes to @hunteditor for this. I haven't been around XDA much these past few weeks and haven't made a new thread for the U-ROM. It has been long overdue. He took on the annoyance of modifying the instructions and download links to work.
hunteditor said:
People ask if they can root this Rom. The answer is yes, but why would you want to? You get all the benefits of rooting and still have official status. Plus, you get the outstanding battery life of a non-rooted S7.
Click to expand...
Click to collapse
jrkruse said:
An Explanation of what this is. I have found a way to manipulate system files on a stock rom and not loose system official status. This Allows Samsung Pay and all safetynet checking apps to function. This Rom is not rooted just modified.
Features
Features:
Aroma Installer
Choose From Total Stock Rom
Choose From Debloted Rom 70 Apps Removed
Choose From BS Free Over 120 Apps Removed
Choose PlayStore Rom Over 120 Apps Removed Plus All Samsung Apps Replaced With Google Apps
Wifi Calling
Video Calling
Volte
Hd Voice
Visual Voice Mail
Working Hotspot For Unlimited Data Customers
Samsung Pay Working
Samsung Cloud Storage
Native Call Recording With Automatic Call Recording Feature
Multi Users
Device Maintenance Enabled
International Settings Layout
Build.prop Tweeks
Ad Host Blocking
Outdoor Mode
KeyLight Duration Settings
LockScreen Torchlight
Phone Testing Menu For System Selection Control
Stock Kernel So No Lag
MODS-(NoNaMeRomControl)
3minitbattery
Speed meter
Status bar mods
Center clock
Wifi/signal bar mods
Color change icon mod
Custom backgrounds
Notification drop-down
Incallui background
Gif in notification drop-down
Change/remove carrier names
And much more...
Click to expand...
Click to collapse
LATEST ROM UPDATE IS POSTED HERE
Downloads:
G930UUEU4BQD2_G930UOYM4BQD2_VZW.zip
UFirm_Multi_Carrier_Hybrid_NoNaMe_PlayStore_BS_Fre e_V14_VZWS7FLAT.zip
Latest Odin
Latest FlashFire APK
Nougat_S7_Root_2_81_All_Carriers_V2.zip – thanks jrkruse
S7 Nougat root kernel
Install Instructions From Any Build:
Warning: This will wipe your device. Some of these instructions are redundant, but they will ensure that everything goes as planned. If you don’t follow them to the T, don’t complain.
1) Unzip G930UUEU4BQD2_G930UOYM4BQD2_VZW.zip. Boot the phone into download mode (volume down, home, and power) then flash all four files (BL, AP, CP, and HOME_CSC) with ODIN. The phone will reboot into recovery and throw an error. Reboot into download mode and reflash HOME_CSC again. – Thanks @thefirst__noel
2) Don’t bother logging into any accounts, as the phone will get wiped again. Copy the FlashFire.apk, AP_G930UUEU4BQD2_CL10860000_QB13198947_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5, and UFirm_Multi_Carrier_Hybrid_NoNaMe_PlayStore_BS_Free_V14_VZWS7FLAT.zip to Internal Storage. – Thanks @appye
3) Make sure secure boot is turned off!!! Shut off the phone and boot into download mode (volume down, home, and power). Flash the S7 Nougat root kernel in the AP slot in Odin.
4) When the phone reboots, unlock developer options and enable USB debugging. Unzip the S7_SU_2_79_Root_Unroot_WO_Tweaks.zip and run root.bat from your PC. May need to right-click and run as administrator.
5) Now install FlashFire. In FlashFire, select add Flash Firmware Package and choose AP_G930UUEU4BQD2_CL10860000_QB13198947_REV02_user_ low_ship_MULTI_CERT_meta.tar.md5 and make sure all partitions are checked.
Then add Flash Zip or OTA and choose UFirm_Multi_Carrier_Hybrid_NoNaMe_PlayStore_BS_Fre e_V14_VZWS7FLAT.zip and tap mount system when FlashFire asks.
VERY IMPORTANT NOTE: MAKE SURE TO UNCHECK INJECT ROOT AFTER ADDING THE ZIP! – Thanks @dclutter1
Click Add Wipe and choose Wipe Dalvik Cache and Cache and choose Format Cache Also select wipe SuperSU image. Make sure wipe is at end of flash sequence. The sequence should be AP file first then Zip second and Wipe cache last.
6) The phone will restart and FlashFire will flash the firmware first, then the Aroma Installer will start.
7) In Aroma, select wipe ALL data (DO NOT KEEP SU) – See notes below.
8) The phone will say custom status on first boot, but it goes away after setup and reboot.
The phone may take up to 20 minutes to boot the first time, so be patient.
If you reflash the ROM, you must flash the AP file in FlashFire at the same time.
Notes:
* Do not use Package Disabler Pro if you choose NoNaMe mods in Aroma.
* If you are installing the S8 apps, you may run into force closes. Your best bet is to pull down on the notification panel, click the settings button, and go into applications and clear data for everything that is force closing. If you keep data, you may run into issues with Advanced Calling and other features. Keep data at your own risk. If you don’t wipe data, then please don’t post issues in the thread.
* I was able to keep my settings and data by choosing keep data in Aroma and still passed SafetyNet. I can’t guarantee that this will work for everyone, but you can try if you want. This probably will not work if you are coming from MM. If you decide to take this route and have issues, do a full wipe and reinstall before posting any problems.
* If you get constant application errors saying "IMS service has stopped" and "com.sec.epdg has stopped", boot into recovery using the Power+VolUp+Home combination. You will likely get a "No command" error screen. Let it on that screen (30-60 seconds) and it will eventually go into the recovery menu. Wipe data and cache in recovery. – thanks paul.miner
jrkruse said:
THANKS AND CREDITS
@jds3118 for testing and providing files and bootlooping his phone countless times for me
Gharrington for his awesome 3minitbattery mod...
NoNaMe rom development team for their incredible mods and rom control app...
@malbert16442 for his black themes
Xda for all the great guides to accomplish this...
Click to expand...
Click to collapse
Kernel source
RomControl Source
jrkruse said:
Install And Uninstall Ad Blocking Via ADB Without Rooting
ADB_AdBlocking_Host_Stock_Host.zip
AP_G930UUEU4BQD2_Boot_Recovery_Image.tar.md5
Nougat_S7_Flat_EngBoot.tar.md5
Download these three
Unzip ADB_AdBlocking_Host_Stock_Host.zip
Reboot phone to download mode
In Odin Flash Nougat_S7_Flat_EngBoot.tar.md5 In AP Slot
When phone reboots and reconnects run adblocking.bat for ad blocking or run no_adblocking.bat to remove ad blocking
Phone will reboot back to download mode
In odin flash AP_G930UUEU4BQD2_Boot_Recovery_Image.tar.md5 In AP Slot
Your back to normal
Click to expand...
Click to collapse
***This post has been modified to include the Flat files only.***
Thanks @DJ XtAzY for the Boot_Recovery image.
Does this ROM come with Google Pixel Dialer, Google Camera etc Google stuff in Aroma to choose from ?
I didn't install those options, but I believe they are there, along with some S8 app options as well. I've been running this for a week. It's silky smooth with great battery life. Every time I pick up my phone now I can't help thinking this is how our phones should be. I'm loving this ROM.
Here's the boot recovery file I created that should be added to the first post:
AP_G930UUEU4BQD2_Boot_Recovery_Image.tar.md5
Those that want to remove or update ad blocking host file will need to follow jrkruse post, with one modification:
https://forum.xda-developers.com/showpost.php?p=71331817&postcount=2
jrkruse said:
Install And Uninstall Ad Blocking Via ADB Without Rooting
ADB_AdBlocking_Host_Stock_Host.zip
Unzip ADB_AdBlocking_Host_Stock_Host.zip
Reboot phone to download mode
In Odin Flash Nougat_S7_Edge_EngBoot.tar.md5 In AP Slot
When phone reboots and reconnects run adblocking.bat for ad blocking or run no_adblocking.bat to remove ad blocking
Phone will reboot back to download mode
In odin flash AP_G930UUEU4BQD2_Boot_Recovery_Image.tar.md5 in AP Slot
Your back to normal
Click to expand...
Click to collapse
I also modified the updater_script so that the BS Free section of the script will remove more of Google Apps, such as Photos, Hangout, but I kept the Camera plugins and the Gallery's photo editor and video playback, etc. I also sorted that section of the script by alphabetical, it was a pain to see what the script removes and keep when everything is out of order when going through the list. If anyone's interested of that updater_script, let me know.
DJ XtAzY said:
Here's the boot recovery file I created that should be added on the first post:
AP_G930UUEU4BQD2_Boot_Recovery_Image.tar.md5
Those that want to remove or update ad blocking host file will need to follow this modified post:
https://forum.xda-developers.com/showpost.php?p=71331817&postcount=2
I also modified the updater_script so that the BS Free section of the script will remove more of Google Apps, such as Photos, Hangout, but I kept the Camera plugins and the Gallery's photo editor and video playback, etc. I also sorted that section of the script by alphabetical, it was a pain to see what the script removes and keep when everything is out of order when going through the list. If anyone's interested of that updater_script, let me know.
Click to expand...
Click to collapse
I added this to the second post. Thanks!
As for the updater_script, I planned to redo it to fix the gallery and video issues on the next version. I didn't want to upload an update with these fixes, then release one right after when the latest ROM is available with the new firmware, because that usually ends up being the case lol. I'd definitely be interested in looking at your script.
I feel like I'm going crazy here, any help would be appreciated. I downloaded everything and flashed all four files (BL, AP, CP, and HOME_CSC) with ODIN. The phone reboots into recovery and throws an error. I reboot into download mode and reflash HOME_CSC again. Then, it just gets stuck on the SAMSUNG screen. I've tried reflashing multiple times, and even let the phone sit for over an hour in case it was just taking a long time to boot. But I can't ever get it past the SAMSUNG screen. Any ideas?
@CVertigo1
I was able to install this ROM.
I noticed a very weird thing. In the attached screenshot, there is a small white tab at top of the screen in scroll area.
Why does it exist ? Can we hide it ?
njKeever said:
I feel like I'm going crazy here, any help would be appreciated. I downloaded everything and flashed all four files (BL, AP, CP, and HOME_CSC) with ODIN. The phone reboots into recovery and throws an error. I reboot into download mode and reflash HOME_CSC again. Then, it just gets stuck on the SAMSUNG screen. I've tried reflashing multiple times, and even let the phone sit for over an hour in case it was just taking a long time to boot. But I can't ever get it past the SAMSUNG screen. Any ideas?
Click to expand...
Click to collapse
Reboot into recovery and wipe data.
electrosam said:
@CVertigo1
I was able to install this ROM.
I noticed a very weird thing. In the attached screenshot, there is a small white tab at top of the screen in scroll area.
Why does it exist ? Can we hide it ?
Click to expand...
Click to collapse
It's called the battery bar. Disable it in the ROM control app.
CVertigo1 said:
Reboot into recovery and wipe data.
It's called the battery bar. Disable it in the ROM control app.
Click to expand...
Click to collapse
Thanks a lot. I was able to hide it.
Another weird thing is, in the ROM control app, the button size is enlarged. Not sure why (attached).
I was using other ROM of yours earlier and in it the size was correct. Any thoughts?
Also, a word of caution during installation-
When I flashed everything from ODIN first and booted, the phone downloaded an update(OTA)
I accidentally said Update. It went ahead and installed it.
Booted back fine, was able to root, flashfire, aroma. After aroma however, it got stuck in boot animation. Rebooted it, got stuck and would not go ahead.
Needed to factory reset from recovery and start over.
Some of the cursors are a little awkward with the modded systemUI. You'll notice it everywhere, especially Google.
CVertigo1 said:
Reboot into recovery and wipe data..
Click to expand...
Click to collapse
That did the trick, thank you so much!
CVertigo1 said:
Some of the cursors are a little awkward with the modded systemUI. You'll notice it everywhere, especially Google.
Click to expand...
Click to collapse
Thanks.
One more doubt-
How can we control settings of open source ad blocking ?
I think it is blocking 'Here Maps' App and I'd like to exclude this from blocking.
Thanks.
electrosam said:
@CVertigo1
I was able to install this ROM.
I noticed a very weird thing. In the attached screenshot, there is a small white tab at top of the screen in scroll area.
Why does it exist ? Can we hide it ?
Click to expand...
Click to collapse
thats the battery bar you can remove it in the rom control app
CVertigo1 said:
Some of the cursors are a little awkward with the modded systemUI. You'll notice it everywhere, especially Google.
Click to expand...
Click to collapse
Is there a plan to fix this ?
Is this more visible if we choose Google Play ROM version as opposed to debloat/verizon rom ?
I was using Verizon_TMO_Hybrid_Nougat_Rom and in this I think this cursor/gui awkwardness did not exist.
Thanks
electrosam said:
Thanks.
One more doubt-
How can we control settings of open source ad blocking ?
I think it is blocking 'Here Maps' App and I'd like to exclude this from blocking.
Click to expand...
Click to collapse
I use Adguard, so I don't use the ad blocking in the ROM. I don't know how to help on that. Did you see post #2 about ad blocking? If I remember correctly, you can edit the file and use adb to push it, but I'm not certain.
electrosam said:
Is there a plan to fix this ?
Is this more visible if we choose Google Play ROM version as opposed to debloat/verizon rom ?
Click to expand...
Click to collapse
That is really up to jrkruse if he fixes it in a later update. Switching ROM versions won't fix it. If it's a huge bother to you, then re-flash the ROM and don't choose the modded systemUI.
I am currently running Stang5litre Edition 5.0 s7 v3 MM ROM on an AT&T S7 Flat and I believe the ROM is based on the S7 Edge . I am trying to flash this ROM using the OP instructions and keep getting this error in Odin on Step 1. The phone never reboots, it just stays in recovery. Any suggestions?
ezwalker63 said:
I am currently running Stang5litre Edition 5.0 s7 v3 MM ROM on an AT&T S7 Flat and I believe the ROM is based on the S7 Edge . I am trying to flash this ROM using the OP instructions and keep getting this error in Odin on Step 1. The phone never reboots, it just stays in recovery. Any suggestions?
Click to expand...
Click to collapse
Its cause this ROM is nougat based and for a strange reason you can't flash nougat roms directly on top of MM ones. The usual fix is to flash the stock firmware for your phone, try to get the OTA update for nougat, then follow the steps. Also just giving a fair warning you can't downgrade back down to MM after the nougat update so you wont be able to go back to Stang5litre until he updates that to nougat.
---------- Post added at 02:00 PM ---------- Previous post was at 01:45 PM ----------
@CVertigo1
Hey I have a bit of a bug report. Was messing around with the settings in NNRomControl and finally got things the way I like it. I went to go restart the phone and when it booted back up System UI either Stopped or Crashed and didn't restart itself. Did a little testing and found that it was the System UI Tuner Mod. After enabling any of the settings and restarting the phone System UI would immediately crash on startup.
Deleted
Hey @CVertigo1 im using the current urom. And dome of my pictures arent loading. Anyidea? Refer to my picture in the other thread
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.
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)
HI with the previous ROMS ive used i am able to remove bloatware like bluetooth , basic daydreams,print spooler ,sim tool kit ,fused location ,mobile broadcasts, carrierdefault app etc using a frdroid debloat application running as root.
it works perfect with AOSP ROMS, and havoc os etc , YET when i try to do the exact same thing with a exact same phone running LineageOS 18.1 (android 11) it causes the system to bootloop and reboots to recovery after the LineageOS logo just flashes for ages.. anyone know why this is or how i can work around it ?
you probably removed some software that's needed from the ROM to work correctly, if android needs an app to perform basic functions this might happen, you can still debloat it, just try to understand which app removal is causing the bootloop and remove all the apps but that one
tdjj said:
you probably removed some software that's needed from the ROM to work correctly, if android needs an app to perform basic functions this might happen, you can still debloat it, just try to understand which app removal is causing the bootloop and remove all the apps but that one
Click to expand...
Click to collapse
yes i tried this ! i tried removing one by one and they all cause bootloops(having to reflash the rom in twrp each time) .. what i cant understand it why only Linageos causes a bootloop with other roms i can remove the exact same PKGS without this happening...
i was thinking perhaps it might have to do with the android version the other roms i can do this on are all runnning on android 9 // when i have tried this on roms using android 10/11 it doesnt work. i think there has been a change to the system wide config of some sort that checks the hiarchy on boot /
By default a phone's bootloader at the begining loads vbmeta.img what holds the hard-coded hashcodes of Android's ( critical ) partitions like /system and then checks whether these partitions got tampered or not.
So in case you make any changes to /system partition ( e.g. remove system apps ) a successfully booting into Android OS must fail.