SuperSu 2.67 missing icon in launcher - SuperSU

I installed SuperSu v2.67 on a Nexus 5 running stock Marshmallow 6.0.1, and SuperSu works great for me so far!
The only (minor) issue I've encountered thus far is that the SuperSu icon seems to be missing from the Google Now launcher home screen and app drawer.
I can still launch SuperSu by searching for it in the Google Play store and clicking "Open", and it still pops up when an unauthorized app is requesting root access.
I've tried to do a complete unroot + reinstall, change the SuperSu icon from the app's settings etc. - without success.
Has anyone else encountered this? Is there any way to get SuperSu icon to show up?
Thanks in advance.

Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.

Edit:
Correction! Found the icon. It was buried in the app drawer all along. What threw me off was that for some reason, when I write "SuperSu" or any prefix of the name in the search box at the top, it doesn't find SuperSu, like it does pretty much any other app. Weird.
Anyway, thanks for the help and sorry about the false alarm.

Chainfire said:
Try this with your computer:
adb uninstall eu.chainfire.supersu
Reboot back into Android, then reboot into recovery and reflash, or extract the APK from the zip and "adb install" it.
Click to expand...
Click to collapse
I'm having a similar problem as the OP except that 2.6.7 binaries don't install on a T-Mobile Note 4 (SM-910T3) in either Lollipop or Marshmallow using either the Normal or TWRP methods. 2.6.5 and 2.6.6 binaries install properly, however.
I tried the command in recovery and got the following error:

In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.

Chainfire said:
In other words, you have a completely different problem that isn't even vaguely related. Not enough info, wrong thread.
Also, adb uninstall doesn't work from recovery, only full Android.
Click to expand...
Click to collapse
You're right I didn't explain things right. My ROM comes preinstalled with SuperSU 2.6.6 and I have the same issue as the OP as the app doesn't appear in either app drawer and I can't launch it from the Play Store either. I'll try adb uninstall properly.
The 2.6.7 failed install is a separate issue. Do I start another thread here in the same forum? What info do you need?

Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok

thereassaad said:
Mate if adb shell not working then use this as i got same issues before anyway go to setting/application manger then roll down to find this
eu.chainfire.supersu
Then uninstall it & reboot then re install supersu app extracted from supersu zip it should work for u ok
Click to expand...
Click to collapse
Thanks. I got it to uninstall and was able to reinstall, but it still wouldn't show up in app drawer or open from the Play Store.

Related

[SUPPORT] Update failures

With all major changes to SuperSU, there are updates to both the GUI and binary. The GUI is the part you see on screen, the binary is what allows other apps to actually acquire root access. The first time you open SuperSU after such an update, it will attempt to update the binary to the latest version.
There are a lot of components to the binary and it needs to be set up just right for everything to work. This is a complex operation, and sometimes it fails. SuperSU is used by dozens of millions of users across hundreds of different devices, running even more different firmware revisions - any change always has the potential to break something somewhere.
SuperSU offers multiple ways of installation: in-app 'normal', in-app TWRP/CWM, and ZIP via TWRP/CWM. These all have their own strengths and weaknesses, so if one doesn't work, try the others if available.
If you are reporting an update failure, you should include at least the following information. Some information requires some skill with adb to retrieve.
- Exact device model
This includes the brand, the model, and the carrier variant (if applicable: mostly USA, Korea, China)
- Exact firmware version
Which exact firmware are you using? If you are using a custom firmware, please include a link to the download for this firmware. If on top of that, you are also using a custom kernel, please include a link to the download for that as well.
- Exact Android version
Android x.y
- Exact SuperSU version
Which version were you running, and to which version are you updating? If using Pro, do you have OTA survival mode enabled?
- Interfering apps
There are some apps that can interfere with SuperSU installation, primarily:
- other Superusery apps
- Xposed
- BusyBox (symlinked or non-symlinked)
Include in your report if you have one or more of these installed.
- Update methods tried
In-app 'normal', in-app via recovery, and ZIP via recovery. If you used one of the recovery options, please include exactly which version of which recovery you are using, and if it's not an official build (so a TWRP not from the TeamWin website, a CWM not from CWM's site, etc) a link to where you got it from.
Note that if you let TWRP or CWM "fix" root for you, or let them disable the firmware from flashing a new recovery (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.
- What kind of root are you left with?
After a failed binary update, multiple outcomes are possible:
- Root is lost. Apps cannot get root anymore, you cannot get root using "su" from an adb shell, etc
- Root seems to mostly still work. Most apps still work, and/or "su" still works from an adb shell
- Nothing seems to have changed at all, even the GUI still shows the old version number
Report what state your device is in now. Note that you can get the version of the main "su" binary by running "su -v" from a terminal emulator or adb shell.
- Logs from TWRP, when updating the binary using the TWRP/CWM button inside the SuperSU app
After pressing the TWRP/CWM button, the device should reboot into TWRP, do it's thing for a few seconds, then reboot into Android. If SuperSU still complains about the binary, please retrieve the TWRP log file. You can retrieve it via adb pull /cache/recovery/last_log, which should produce the last_log file in your current directory. You still need at least partial root from booted Android to retrieve this log. Sadly it is wiped and replaced with a new file when you boot into recovery a second time, so you cannot retrieve it that way. Note that this log will always contain a number of errors, as the installer tries several things in several ways, that work differently on different firmwares. Attach this log file.
- Logs from TWRP, when updating SuperSU completely via ZIP
If after you boot back into Android, SuperSU is not working right or still asks for updated binaries, reboot back into TWRP, install the ZIP again. After the ZIP is installed, you can retrieve the log file via adb pull /tmp/recovery.log, which should produce the recovery.log file in your current directory. Attach this log file.
- Logs from SuperSU (very important)
If SuperSU keeps asking you to update the binaries after trying any which way and failing, please post the detection log. After updating has failed, don't reboot, but produce detection information via adb logcat -d | find /i "installer" > logcat.txt (Windows, use 'grep -i' instead of 'find /i' on Linux or OSX), which should produce a logcat.txt file in your current directory with several lines mentioning SuperSU. Attach this log file.
- Various logs (very important)
Some additional handy information can be gotten by via some adb shell calls. If you that working, copy/pasting the following commands should produce a nice sulog.txt file in your current directory, which you should attach to your post:
(as always with copy/pasting, make sure you press enter a few times afterwards to make sure the last line was flushed)
Code:
adb shell getprop > sulog.txt
adb shell set >> sulog.txt
adb shell toolbox id >> sulog.txt
adb shell busybox >> sulog.txt
adb shell su -v >> sulog.txt
adb shell su -V >> sulog.txt
adb shell su -h >> sulog.txt
adb shell su --self-test >> sulog.txt
adb shell ls -l /system/xbin/*su* >> sulog.txt
adb shell ls -lZ /system/xbin/*su* >> sulog.txt
adb shell ls -lZ /system/bin/toolbox >> sulog.txt
adb shell ls -l /system/bin >> sulog.txt
adb shell ls -l /system/xbin >> sulog.txt
adb shell ls -laR /su >> sulog.txt
adb shell ps >> sulog.txt
In closing
All this information will help diagnose the problem, and potentially help fix the issue if there is something wrong with SuperSU itself (which is not unheard of). The more information you provide, the better you can be helped. Still, be aware that often it takes a while to get a problem sorted. Even when a lot of people are having the same problem (and many problems may look the same but deep down are separate issues), it is rare to find a user who actively wants to help fix the issue. Most users will only complain but then don't really assist in solving the issue. If you can be someone who can actively help, and by that I mean being responsive to questions, being available for a live debugging session, etc, you are a rare gem indeed, and your assistance will be greatly appreciated.
If you are writing multiple posts, it is always helpful if you keep linking back to your original post with the report. Saves me time.
Sorry for the inconvenience!
SGH-T999
4.3
2.06 can update to 2.14 but binary update never takes
BusyBox but dont know what kind
In-app 'normal', in-app via recovery, and ZIP via recovery after that binary update still fails normal and via TWRP v2.8.0.1
Still have root
Update has make my Galaxy S5 is unusable...
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
shadow322 said:
SGH-T999
4.3
2.06 can update to 2.14 but binary update never takes
BusyBox but dont know what kind
In-app 'normal', in-app via recovery, and ZIP via recovery after that binary update still fails normal and via TWRP v2.8.0.1
Still have root
Click to expand...
Click to collapse
As stated on IRC, I'm going to need the logs described above.
Emmie0702 said:
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
Click to expand...
Click to collapse
Sounds unlikely to be due to SuperSU. Either way, there's nothing you can really do about it now. Situations like these I advise a factory reset and a data restore.
Chainfire said:
Sounds unlikely to be due to SuperSU. Either way, there's nothing you can really do about it now. Situations like these I advise a factory reset and a data restore.
Click to expand...
Click to collapse
I've done a factory reset & stoll have the same problem. How would I restore data?
Emmie0702 said:
I've done a factory reset & stoll have the same problem. How would I restore data?
Click to expand...
Click to collapse
You would restore the data from a backup you've made before resetting ?
In SuperSU you can try 'full unroot' from Settings (twice if necessary) and unroot, see if that resolves the slowness/crashing.
The only backup I have is a titanium backup. I can't get anything to download from the play store. I never flashes recovery because it wasn't available when I rooted. I never went back to add it (which I could kick myself for right now). Would re rooting help? Supersu isn't on my phone anymore either. I'm not sure what happened to that.
Edit: could the platform.xml under /etc/permissions/platform.x ml have anything to do with it?
Knox
Emmie0702 said:
After update I am unable to open any Google based apps, Gmail, maps, YouTube, etc. I get an error that says "Unfortunately, [app] has stopped.". Im also getting the "Unfortunately, the process com.google.process.gapps has stopped" error. What do I need to do? I did a factory reset hoping thats would fix the problem but it hasn't. It seems as thought it's not reading my SD card as well. It's showing I don't have pic or that one is even installed. I can make calls but that's about it. No Internet, no connections, no apps. Can't even sign onto my gmail to be able to download any app from the play store. I am out of town & without a computer until later tonight. Would re rooting fix my problem? I do not have recovery flashed onto my phone. It wasn't available when I rooted & I never got around to doing it. Pleasant Help! I have a titanium back up of my 0hone but can't download the application to try that avenue.
Click to expand...
Click to collapse
@Emmie0702 I think it's a weird Knox Action -i mean, It MAY happen 'coz Knox
Chainfire said:
Note that if you let CWM "fix" root for you (sometimes you are asked this), you have broken root, and the only way to recover it is flashing the full ZIP through recovery.
Click to expand...
Click to collapse
CWM is asking for that. I have to answer Yes or No. So I should click No ?
sorry wrong thread
Samsung N7100 Hong Kong (rom is UK)
N7100XXUFND3
4.4.2
2.14 pro
Don't have OTA survival mode enabled.
Before updating the SU, I can use the SU as usual. But after updating the SU binary via normal, it says I didn't install the execute file ( something like that, since I'm using Chinese), which means i haven't root.
So, do i need to re-root, then update the SU binary?
p220fhf said:
Samsung N7100 Hong Kong (rom is UK)
N7100XXUFND3
4.4.2
2.14 pro
Don't have OTA survival mode enabled.
Before updating the SU, I can use the SU as usual. But after updating the SU binary via normal, it says I didn't install the execute file ( something like that, since I'm using Chinese), which means i haven't root.
So, do i need to re-root, then update the SU binary?
Click to expand...
Click to collapse
You can give it a shot, rerooting via the ZIP ( http://download.chainfire.eu/supersu ) with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
SuperSU Problem!
I've rooted my device (GT-1335 - Android 4.4) with Windershare Rooting Toolkit, After rooting I've installed Root checker basic from the market and run it. It says your device is rooted. But when i wanted to go to root using FX explorer, it says you need permission from Advance user. When i click SuperSU after that it says that "There is no Su binary installed, and SuperSu cannot install it. This is a problem!", After that i checked whether my device is rooted or not with Root checker basic, but now its says that my device isn't rooted!
Please Help, and replay soon!
Note: My device isn't original samsung model!
super su still loading
After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
I had problems with using Stock 4.4.4 on my i9305.
Was freezing/not opening, then when it did it wouldn't update.
So I went to the SuperSu site and downloaded the latest to instal via CWM.
Now working fine. Hope this helps someone.
Chainfire said:
You can give it a shot, rerooting via the ZIP with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
Click to expand...
Click to collapse
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.
So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.
My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game , but can't root again as it says "You didn't root")
Sorry for my bad English.
SuperSU 2.14 not working on s4 4.3
gokunjp said:
After update super su in playstore my s4 octacore in app tab on supersu still loading but nothing happened...
Click to expand...
Click to collapse
same problem here on my S4-quad-16G with samsung 4.3-stock, which was rooted mothns ago via AutoROOT+twrp2.7.01
p220fhf said:
I tried to reroot on my s4, but nothing changes, when updating the SU to 2.14.
So, I think, maybe, the main problem is SU 2.14 on 4.4.2 and 4.3.
My s4 was 4.3 rooted, before the SU update, everything was fine. But after updating, the SU app said I didn't root. Then I updated my FW to 4.4.2(I9505ZHUFNB3), and used CF-root to root. Still ok, but when the SU updated to 2.14, thing happened again. (Now my s4 is temp unroot for playing game , but can't root again as it says "You didn't root")
Sorry for my bad English.
Click to expand...
Click to collapse
same here update 2.14 from PlayStore f.cked-up the SuperSU app (i have waiting-donut on APPS and LOGS-tabs...)
Device stays rooted, and root-requests from other apps seems to work too, because there is a typical SuperSU-reuqest popup there....
So please fix the APP for Samsung 4.3 4.4 firmwares...
Versions 2.01+2.06 worked flawlessly.
what i have already tryed:
1) On the [Settings]-TAB: => UNINSTALL APP: Effect 'uninstalling...'-popup stays 4ever w/o effect
2) On the [Settings]-TAB: => UNINSTALL APP for a NEW SuperUserApp: Effect 'uninstalling...'-popup stays 4ever w/o effect
3) Booted into TWRP => INSTALL the SuperSU-2.14.ZIP, rebooting phone -> in SuperSU (the same waiting donuts on APPS/LOGS...)
Phone: i9505-OpenEUROPE quad-core/16G Samsung-stock-FW 4.3
Device I9505
Android Version: Stock 4.3 MKF
BusyBox v1.22.1
Wanam Xposed installed
Stock Recovery
Kingo Root
Google Play Update
Issue: After update from 2.13 to the latest 2.14 when supersu try to reinstall it stuck more than 5 minutes, I reboot my phone, reopen supersu but now in my "APPS" and "LOGS" I have some kind of neverending loop load, I can't manage to see my rooted apps there, and in my SETTINGS if I try to make some changes it stuck and need phone reboot, otherwise all my rooted apps work fine!
Chainfire said:
You can give it a shot, rerooting via the ZIP with TWRP. See if that helps, and let us know. If it doesn't fix the issue, I will find this firmware and flash it on my own N7100 (if possible) and see if I can replicate the issue.
Click to expand...
Click to collapse
I think i figure out the problem, is the SU bin update. My note 2 is rooted and is using SU 2.14 pro, but i don't update the bin. It works fine, but when opening the su app, it asks you to update the bin.

Uninstall as system app

The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
Sorry as I don't have a solution for your problem....
But still as far as I know Super user 2.46 is not fully compatible with android 5 & above.
On other hand I would suggest you to give a try to super user 2.49 beta which is the latest but still under development.
Hope you find this useful.
ayushbpl10
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If you want to make SuperSU a user app:
If SuperSU was "updated" by the Play Store (ie there's an eu.chainfire.supersu-*.apk in /data/app), then delete /system/app/SuperSU.apk and reboot. If it's flashed *and* the afore mentioned apk is *not* in /data/app, then move /system/app/SuperSU.apk to /data/app and reboot.
Sent from: SGS2 - JB 4.1.2 GB27 / SGS4 - JB 4.2.2 MF9
Sent from my Aqua i5 mini using xda-developers.com, powered by appyet.com
DeanGibson said:
The method I used for rooting my LG G3 (v5.0.1) installs SuperSU (2.46) as a system app. I would much prefer to have it be a regular app (as it has always been on my Android devices prior to v5.0). When I use SuperSU to clean up in preparation for "another" SU app, it removes itself and leaves behind a few files (including the su binary) in /system/xbin.
All well and good. However, after now installing SuperSU from the Google Play Store, SuperSU gives the message that there is no su binary installed, and of course refuses to work. I even tried copying su to "sux" and giving the latter 4755 privileges (while still rooted), but that didn't help.
Is this a bug in SuperSU, or is it a necessity of Android 5.x ???
ps: The XDA forum software will not let me post this as a question. Where do I post questions about SuperSU?
Click to expand...
Click to collapse
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
mmonaghan34 said:
If all you wanted to do was make it a user app, reroot, open supersu, go to cleanup and choose for reinstallation. After choosing that, if it says to reboot then press it again, do so, else reboot and install supersu from play. Done, supersu as a user app
Click to expand...
Click to collapse
That doesn't work (v2.46 on LG G3 running v5.0.1). It loops trying to uninstall. After a couple minutes, I forced a reboot. SuperSU was still there, and as a system app.
Edit: The same thing happens when I tell SuperSU to completely unroot the LG G3. Since I needed to unroot in order to apply an LG/Verizon OTA update, I used LG's Flash Tool to replace the system partition (THAT removed SuperSU!), and then the OTA update was successful.
Since LG now supplies an on-phone backup/restore tool for the G3 as part of the Settings menu, I no longer need to run Titanium Backup, which means I no longer need root. Given the nuisance issues with rooting/unrooting/system updating/etc, I've decided to remain unrooted on the LG G3 for the time being. Quite a change for me, since this is the first Android device in well over a dozen for which I've made this decision.

Cannot find Supersu tool in Settings menu

I cant find supersu in settings..im running on cm11s on OPO.
But im getting root access. When i search in settings, it shows a superuser tool. bt i cant access it through the settings.
plz give me your valuable points..screen shorts are attached below for ur clarification. please help me..
cjl bny said:
I cant find supersu in settings..im running on cm11s on OPO.
But im getting root access.....
Click to expand...
Click to collapse
Suggestion: uninstall su - reboot - reinstall su.
Go to the play store and select superSu. Hopefully you see the Uninstall button.
I tried to reinstall supersu many times. does not appear in the menu and does not have an open button in settings.
Yes I have verified I have root access. Using Android x86 7.1.2
How do I run this app?

Gear LIve TWRP, Rooted With Magisk - General/Questions 2019

So I just recently came across this watch and have been fiddling with it. I managed to twrp it, unpack the 5.1.1 boot img other day and patch it with magisk and flashed it successfully. There was a little error in magisk manager you could slide by when you first opened it but it showed installed could grant superuser permissions.
The newest updates (6.0.1) and above I guess are using this squashfs scheme for system so it's not mountable. I noticed on the lg watch there was a squashfs doryimg, does anyone have squashfs sprat compatible twrp already anywhere, or can create one quicker than me? Or lead me in the right direction to compile it myself? An update installed on me unrooted me and failed to install, ideas on easiest way to freeze them prefferably adb shell pm uninstall -0 type command? Managed to also magisk patch 6.0.1boot img and flash it successfully get superuser permissions but its not proper doesnt have system permission to change anything much because of squashfs.
Tried DPI Changer is nice. Google Keyboard is good but wish it had an enter button so I can fiully type in jackpal terminal spaces that require an enter key. Will maybe try hackers keyboard(tried swype, gboard, minuum on 5.1.1 no dice). Google Analog draw keyboard zip kind of nice but annoying to type with. Es File Explorer pro size render disallowed looking at others app menu beside users. Es File Explorer worked to uninstall on 6.0.1 but not 5.1.1 had to go to go to data/ app to uninstall on 5.1.1. Could not install apk from device. Have been having to use adb install and push commands to get most files on the watch. Chrome apk latest works. I'd like to stay at 5.1.1 to maintain proper magisk/ twrp solely because of lack of squashfs support. Anyway to update google play service (1.1 to android 1.3 or 1.5) without updating version or install real playstore? Tried remote desktop/ gmail but only thing stopping me was I am unable to login to a google account on device because there is no account section in settings. Tried several app versions, shortcuts, workarounds no luck but lmk if you were able to.
Used rootjunky restore tool v2 to restore stock 4.4 it works well. V3 wouldn't recognize my almost bricked device but V2 would. OTA back from 4.4 is super annoying tho adb doesnt work says unauthorized until 5.1.1 doesnt give key doesnt pop up. Adb sideload is friend. There is not another boot img until 6.0.1 so had to apply patch updates then unpack/ repack. Had issues with backups not restoring root somehow. https://forum.xda-developers.com/wiki/Samsung_Gear_Live couldnt find anything newer besides one reddit post. first 6.0.1 update is twrp flashable.
well thats about all for now when I reupgrade I'll try and upload 5.1.1 magisk root if nothing changes. Thank you kindly Feel free to chime in if you still have this device, what worked for you., any tips, :good:
Still looking??
Sorry, I can't help you....... The gear live support just keeps getting less..... Well, it IS five years old after all...
Anyhow, I still have mine an love it. I read you were able to get TWRP on it successfully.
I can flash TWRP to the Gear Live just fine, but as soon as I reboot normally, the stock software replaces TWRP with the original recovery.
Supposedly, TWRP has a patching feature built in, but I've not been able to make it work.
SO....... Do you have any ideas why mine would not be working??
Thanks
Boowho??

Question Okay, I'm stupid...

So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
install this apk should solve the problem
If worse comes to worse a factory reset will.
A lot of the bloatware is useful. I prefer to use a package disabler as I can easily toggle them on or off as needed real time.
rtd4 said:
install this apk should solve the problem
Click to expand...
Click to collapse
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Trying install via adb I get: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_DUPLICATE_PERMISSION: Package com.samsung.android.providers.contacts attempting to redeclare permission android.permission.SEND_CALL_LOG_CHANGE already owned by com.android.providers.contacts]"
Hmmm, perhaps I should remove Google Contacts first...
Okay, that helped, but now I'm getting: "
Performing Streamed Install
adb: failed to install /home/mhicks/Downloads/SamsungContactsProvider.apk: Failure [INSTALL_FAILED_VERSION_DOWNGRADE]"
I thought deleting the "com.samsung.android.providers.contacts" might solve the problem, but trying gave me: "
./adb -d uninstall com.samsung.android.providers.contacts
Failure [DELETE_FAILED_INTERNAL_ERROR]"
darkfrog26 said:
It sat for a minute trying to install and then came up with, "App not installed" and says that every time I retry.
Click to expand...
Click to collapse
try these commands on pc
adb shell cmd package install-existing com.samsung.android.providers.contacts
adb shell pm install -r --user 0 /system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk
The first command returns: "Package com.samsung.android.providers.contacts installed for user: 0", but the second command returns: "Failure [-3001: INSTALL_FAILED_REJECTED_BY_BUILDTYPE]"
If you have deleted the apk with root you just have to paste it again in the folder /system/priv-app/SamsungContactsProvider
@rtd4, unfortunately, this device isn't rooted.
darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
It is somewhat complicated to recover the device without wipe in the past I had these problems, it was solved with a higher version of the application
@rtd4, I suppose it's time for a wipe... Thanks for trying to help me.
If you had made a copy of all your apps including system apks with ApkExport you could now use that copy to restore it.
Now before you factory reset make a copy of your installed apps and any system updates then save it on the PC or SD card. After the reload you won't need Playstore. It speeds things up a lot...
APK Export (Backup & Share) - Apps on Google Play
Manage and extract your apps.
play.google.com
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
darkfrog26 said:
@blackhawk, thanks for the tip. Right now, I'm trying to set up a Telegram account so I can root my phone (US version) if I'm going to go through the trouble of wiping. Unfortunately, Telegram's SMS verification appears to be broken or at least doesn't like Mint Mobile... Fun day.
Click to expand...
Click to collapse
You're welcome.
You really don't need to root.
Consider the possible consequences carefully.
Package Disabler will easily block apks you don't want running.
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
darkfrog26 said:
Well, it would appear it's moot anyway since I'm at Baseband v4 and only v1 can be rooted apparently...
Click to expand...
Click to collapse
This is the one I use:
Home - Package Disabler
The only NON-root solution that let’s you disable any unwanted packages that come pre-installed / installed with your phone / tablet.
www.packagedisabler.com
It has an interactive widget that allows you to toggle selected entries on/off. It runs even in Safe mode so be careful what you disable. I've never had to do a factory reset because of it but the potential is there.
Unfortunately it no longer disables Google play Services but will disable all carrier bloatware including OTA updates.
darkfrog26 said:
@rtd4, unfortunately, this device isn't rooted.
Click to expand...
Click to collapse
Then how come you have removed apk from system?
In case you have used command like
pm disable packageName . Then try pm enable packageName
Or
If you have used
pm hide packageName then try
pm unhide packageName
darkfrog26 said:
So, I was going through and removing bloat from my phone and was trying to remove the Samsung Contacts app through `adb`, but apparently I removed the wrong thing and now the Phone, Messages, and Contacts app are crashing every time I try to open them. I removed "package:/system/priv-app/SamsungContactsProvider/SamsungContactsProvider.apk=com.samsung.android.providers.contacts" which is apparently a core service. I'm wondering if anyone might know how I could reinstall that APK?
Click to expand...
Click to collapse
Next time use this, so you don't make mistakes:
[TOOL] ADB AppControl 1.8.0 πŸš€ Ultimate App Manager & Debloat Tool + Tweaks
ADB AppControl πŸš€ Root is not required. Works with any Android device. Can do almost everything you dreamed about with applications. ADB AppControl - the desktop program, that will allow you to easily manage applications on your android device...
forum.xda-developers.com

Categories

Resources