Related
Hi. All of a sudden titanium backup is saying it cannot acquire root privileges, ROM manager will not boot into recovery and when I downloaded SU Update Fixer for Superuser it is also saying it failed to gain root access and says try downloading and flashing an update.zip???
Everytime I try to use an app that requires Superuser rights, it says it has stopped unexpectedly and needs to force close, but the app still works!
I am S-OFF, rooted and currently running Virtuous Unity V2.39.0?
Any ideas......
did u try clearing your su log?
VaderXI said:
Hi. All of a sudden titanium backup is saying it cannot acquire root privileges, ROM manager will not boot into recovery and when I downloaded SU Update Fixer for Superuser it is also saying it failed to gain root access and says try downloading and flashing an update.zip???
Everytime I try to use an app that requires Superuser rights, it says it has stopped unexpectedly and needs to force close, but the app still works!
I am S-OFF, rooted and currently running Virtuous Unity V2.39.0?
Any ideas......
Click to expand...
Click to collapse
Have you downloaded the SU updates that have been in the Market lately? After downloading I then rebooted and SU was working again.
syc7090 said:
did u try clearing your su log?
Click to expand...
Click to collapse
Tried, but the app force closes before I get the chance.
Sent from my HTC Incredible S using XDA App
tpbklake said:
Have you downloaded the SU updates that have been in the Market lately? After downloading I then rebooted and SU was working again.
Click to expand...
Click to collapse
The only SU updates I can find is the update fixer, which is telling me I need to download and flash an update.zip, but don't know where to get that from! I recently updated the binary code to SU, or something like that, but have rebooted a number of times since then and still no joy.
Should I just try uninstalling and reinstalling again? All very annoying.....
Sent from my HTC Incredible S using XDA App
VaderXI said:
The only SU updates I can find is the update fixer, which is telling me I need to download and flash an update.zip, but don't know where to get that from! I recently updated the binary code to SU, or something like that, but have rebooted a number of times since then and still no joy.
Should I just try uninstalling and reinstalling again? All very annoying.....
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
then you must have installed the updates from market. uninstall the updates, then everything will be fine once more
shiningarmor said:
then you must have installed the updates from market. uninstall the updates, then everything will be fine once more
Click to expand...
Click to collapse
If you're really messed up with the latest superuser and su binary, you can try flashing this which I created with the stable superuser and su binary from VU2.39. Of course, remember to turn off auto upgrade of superuser in market afterwards.
http://www.multiupload.com/3EKXQ4OFAE
itandy said:
If you're really messed up with the latest superuser and su binary, you can try flashing this which I created with the stable superuser and su binary from VU2.39. Of course, remember to turn off auto upgrade of superuser in market afterwards.
http://www.multiupload.com/3EKXQ4OFAE
Click to expand...
Click to collapse
Thanks itandy, but this is how I got over it in the end. If anyone else is having the same problem, follow these steps to get you back up and running again:
o go to Settings > Manage applications > Superuser
o Hit clear Data
o Force SU update fixer, from the market
o go back to Superuser and in preferences:
o disable logging
o Set automatic response to Allow
o Reboot device
Can finish pulling my hair out now!
VaderXI said:
Thanks itandy, but this is how I got over it in the end. If anyone else is having the same problem, follow these steps to get you back up and running again:
o go to Settings > Manage applications > Superuser
o Hit clear Data
o Force SU update fixer, from the market
o go back to Superuser and in preferences:
o disable logging
o Set automatic response to Allow
o Reboot device
Can finish pulling my hair out now!
Click to expand...
Click to collapse
I could email you a beer I would
I hit this snag tonight trying to get a new rom on my Sensation and I too was pulling out my hair. Thanks a ton for this.
VaderXI said:
Thanks itandy, but this is how I got over it in the end. If anyone else is having the same problem, follow these steps to get you back up and running again:
o go to Settings > Manage applications > Superuser
o Hit clear Data
o Force SU update fixer, from the market
o go back to Superuser and in preferences:
o disable logging
o Set automatic response to Allow
o Reboot device
Can finish pulling my hair out now!
Click to expand...
Click to collapse
Thanks! Confirm - this solves problem with su force close
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.
So I have a Moto X and I have recently rooted it with the method shown here:
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059
Everything works fine and I can grant everything SU as normal but I can't actually get into my SuperSU app and use it properly due to the failure to update the SU binary. When I open SuperSU it shows "The SU binary needs to be updated. Continue?" and then when I click continue, it acts like it's going to install and after a minute or so it gives me an error that reads "Installation failed! Please reboot and try again." and I have rebooted and followed what it said many times and I just can't get it to work correctly. Could it possibly be because I only have a temp root? PLEASE HELP!
Also, keep in mind I am new to root and I am new to this forum so please don't be too harsh on me if I did anything wrong, such as post on the wrong thread or something. Please just leave me a note or something and I will gladly comply if I need to move this to another thread or anything of the sort. Thank you.
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.
I recently acquired a 2013 Moto X 1058 (AT&T Variant) and I've unlocked the bootloader with Sunshine, I've flashed Lineage OS 13 and Open Gapps but certain apps (facebook, snapchat, facebook messenger, google chrome) among apps will not download, instead immedietly throw the error "cannot install Facebook, try again later if the problem persists get troubleshooting help error code:0" and it does it for most apps. Few apps install, like Firefox, Kik, Android Messages but I cannot get this fixed, I've tried multiple gapps, redownloaded gapps, flashed different roms and i can't get it working.
EDIT: the unofficial TWRP 3 is poorly built and doesnt set permissions correctly, I had to use the terminal and do this
chown -R media_rw:media_rw /data/media/
find /data/media/ -type d -exec chmod 775 {} ';'
find /data/media/ -type f -exec chmod 664 {} ';'
Just download it from TWRP themselves.
go seting -->goole play store --> give all permission
I was not able to put in those commands into terminator emulator, kept saying access denied. Any ideas on how to get access or whatever?
I am suffering the same exact problem. I've tried clearing app cache, removing account, wiping cache in TWRP and so on. Nothing is working. I'm not even able to restore the apps via TiBu. Unfortunately it doesn't appear many ppl suffer from error code: 0
weaver11b said:
I was not able to put in those commands into terminator emulator, kept saying access denied. Any ideas on how to get access or whatever?
I am suffering the same exact problem. I've tried clearing app cache, removing account, wiping cache in TWRP and so on. Nothing is working. I'm not even able to restore the apps via TiBu. Unfortunately it doesn't appear many ppl suffer from error code: 0
Click to expand...
Click to collapse
Try that commands with root
Type in terminal su after flash the root
YedanyXD said:
Try that commands with root
Type in terminal su after flash the root
Click to expand...
Click to collapse
hi, after trying your method, I still cant DL using playstore, tried via adb and twrp terminal
I have error code 0 too
I have a Huawei MediaPad 7 youth and some days ago I noticed Google Play Store was uninstalled. I have my tablet rooted, and prior to this everything was fine. I reinstalled Google Play via an APK file on Lucky Patcher's official page (there's the modded Play Store and the original Play Store APKs, I installed the original cause the modded one couldn't install), and I tried to use Lucky Patcher to make it a system app again, but it said it couldn't cause there was few space on /system/app (I have no idea where this folder is, I looked everywhere with my native Android file manager but I can't find it) and told me to free some space on there. So I decided to let Google Play as an user app, but be careful not to uninstall again. Today I opened Play Store for first time since reinstallation, and tried to install two different VPNs, but they both gave me error code 0. Please help me!
It worked on my HTC One M7 Sense 7 Viper 9.0.0 ROM after getting code 0 for multiple apps! Never had this issue before.
Thank you, OP.
I repeat, OP is not telling you to put in random Linux commands. This method actually works! (for me)
Poororo said:
hi, after trying your method, I still cant DL using playstore, tried via adb and twrp terminal
Click to expand...
Click to collapse
You can install terminal apps and from there give root access and execute above cmd.
Yalp Store FTW
Having the same issue I found, downloaded and installed Yalp Store From F-Droid. It finally let me donwload and install/update apps without needing to access play store directly.
I know some might've solved their issues already, but for those who are on CM/LineageOS and need to gain root access, remember that you can enable root in the developer settings... For Lineage 14.1 I'd google, as there are a few steps before that I think.
Hope it helps someone
Can any one help me with bootloader unlocking
I broke my head over this, but it worked!! Thanks!
smitharro said:
I broke my head over this, but it worked!! Thanks!
Click to expand...
Click to collapse
How did you do that please ?
futchy4u said:
How did you do that please ?
Click to expand...
Click to collapse
Simple: I followed the instructions in the OP.
smitharro said:
Simple: I followed the instructions in the OP.
Click to expand...
Click to collapse
Thanks, I already did that but it didn't fix it.
I got it fixed by swapping internal SD with the ExternalSD
Thanx bro, it's working...
Need your help, bro
RedDeadDorito said:
It worked on my HTC One M7 Sense 7 Viper 9.0.0 ROM after getting code 0 for multiple apps! Never had this issue before.
Thank you, OP.
I repeat, OP is not telling you to put in random Linux commands. This method actually works! (for me)
Click to expand...
Click to collapse
I have the same error on my One M7 with Viper 9.0.0 ROM. And I can't fix it. Please help me. Explain how you fixed it. Thanks, bro.
I'm getting the same error.. Ive tried flashing other versions of TWRP and Roms. No clean flash will correct it. What is the deal with this?
Me too. By the way, what's "OP"? where is it?
RunAway15 said:
I'm getting the same error.. Ive tried flashing other versions of TWRP and Roms. No clean flash will correct it. What is the deal with this?
Click to expand...
Click to collapse
I fixed this error. Follow this instruction: android-fix.com/google-play-problems/51-error-code-0.html
I do "Set permissions with Android Debug Bridge". And everything 's ok now.