I tried everything for note 3 to get the SuperSU binaries update to date and I tried all version from the su website or play store. All I get is Installation failed. I am clean stock rooted.
Questions and Help issues belong in Q&A and Help section, thanks!
Thread moved
FNSM
What version of supersu do you have? 2.01?
yup I have the latest SU installed, the problem is that whenever the su app is updated the binaries fail to install, but if I do a factory reset and install the most current version then there are updated... Does the SU app require internet to update/download the binaries?
I was having a similar issue with SuperSU and any all other super user apps. They install, and attempt to update binaries. At this point it never completes the update or the phone crashes and reboots. Haven't quite figured out what the snag is myself.
My issue comes and goes. right now it also asks to update binaries but always fails
I had this issue when I first rooted on stock 4.4.2. So I'm guessing you're on stock? Here download this http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip and instead of installing it. I zip it and go to the common folder. Extract supersu apk and install it. Then run it from the app drawer. Tell me if that works!
That is the not the solution, I have formatted my phone multiple times. I have never been able to update binaries. There has to be a solution to this problem..
jrdnsingh89 said:
That is the not the solution, I have formatted my phone multiple times. I have never been able to update binaries. There has to be a solution to this problem..
Click to expand...
Click to collapse
Why would you format your phone?
I having this weird error when I uninstall an/any app, the android.acore app/service force closes. I tried to wipe clean many times. I just received it again. So whenever I reformat the phone, I can't update the binaries for some reason
Related
this may have been asked, but i'm new to the nexus 7. i rooted it right away, and put TWRP on. probably shouldn't have but i like doing nandroids. i was excited for the OTA and want to just install it since my tab got it, but it won't obviously since i've got a custom recovery (duh i should've thought of that..) and i don't want to go flashing roms yet (i like keeping everything stock right away, it's so smooth)
so my question is, is there a way to go back and flash the stock recovery somehow so i can OTA, then put TWRP back on? i can't find the stock file to fastboot flash or anything
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
kangy said:
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
Click to expand...
Click to collapse
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Alright try this.
Go to SuperSU settings and and click on Reinstall under Cleanup, it will give you a prompt and tell you it will self close and to re-install from the market. (Mine never fully uninstalled which I assume is due to it being flashed to ROM, I checked under the App manager and it only had a downgrade option so) Anywho. If it did uninstall go ahead and redownload it from the market, if it didn't check the market anyway, the Dev published and update for it to help with 4.2 multi users.
Once you get it reinstalled and/or updated from the market go back to the settings and Toggle off Enable Superuser, close the app, re-open and then re-enable superuser. You probably will want to give it a reboot at this point. (Ive restarted my device a hundred times since going to 4.2 from trying to work through the bugs. Once you restart test a root app. I used Adaway for the test. Important, if the app fails or gives an error about not having root, try again. After I went through all of those motions SuperSU was pretty slow for a while with giving root access, usually the second request from the app wakes it up. Since then though it is back to being snappy with zero lag.
Yes, the reason you can't flash TWRP through ROM Toolbox is that requires root. Once you get your SuperSU working try flashing the latest TWRP again, it should only take a few seconds to flash. Let me know how it goes, I'm subscribed to the thread. I may not be the smartest guy on XDA but you are in the same exact boat I was last night!
jayochs said:
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Click to expand...
Click to collapse
First, determine if you have root or not. Open TiBackup, if it opens correctly and you can see all your apps listed, you have root. Otherwise it will say "Failed to obtain root," and quit.
If you have root, then great. If not, you can flash the SuperSU zip in TWRP/CWM: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
I haven't tried flashing superSU, I've always flashed Superuser zip [google "superuser zip"], and then installed superSU from Play store.
Once you have root..
Go to Settings > Security and check allow installation from non-market apps, and uncheck the security feature that checks all apps for being malicious.
Then try it. If you still cannot restore apps, you might have to install them with adb.
I just updated someone's N7 to 4.2, and as usual I backed up everything in TiBackup.
Then I backed up the TitaniumBackup directory [because I had to do a full factory reset].
I then extracted all the .apk.gz files with gunzip. [in linux OR adb: $ gunzip *.apk.gz -- for windows, I suppose you would have to use 7-Zip].
Then I tried to install with pm:
Code:
for i in *.apk; do pm install $i; done
But every one was giving me an error, INSTALL_FAILED_INVALID_URI, I couldn't figure it out. Found a thread said to chmod 755 /data/local, but that did not fix it.
So what I had to do, was on my linux PC:
Code:
for i in *.apk;
do adb install "$i"
done
So I finally was able to batch install my apk files.
after that I restored all apps data.
Nandroid back ups not possible after 4.2 update
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Yordan5 said:
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Click to expand...
Click to collapse
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
mvmacd said:
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
Click to expand...
Click to collapse
NRTK 1.5.5 would not flash the 4.2 custom rom I fed it either. Just kept stalling out with errors that it could not find the zip file.
So I booted into TWRP and flashed it with no problem at all.
I also did backup in TWRP and checked everything but saw no mention that is was a Nandroid backup. How can I be sure?
i'm trying to nandroid back to a 4.1.2 nandroid i have, problem is, twrp has different directories for nandroids in 4.2 than 4.1.2...so it can't find the old nandroids and i can't find the 4.2 dir where twrp stores them now. ugh. such a damn headache for an update that it turns out i didn't want lol
Read my post below, I was having the same problem but got back on 4.1.2. You have to use the twrp explorer and relocate the twrp files since 4.2 moved them.
http://forum.xda-developers.com/showthread.php?t=1992552
Nandroid Downgrade from 4.2 to 4.1.2
Sent from my Nexus 7 using Tapatalk 2
I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..
I have Nexus 4 running rooted JB 4.3Stock (Build JWR66V). I have also installed xposed framework. Recover is TWRP. Last week I got a system update notification. Update size is about 1.8 MB. After rebooting for installing the update, TWRP shows a message that Root permission may have been broken and displays a button to fix the permission. Even i choose to ignore this and reboot, root permission is not affected in anyways after reboot. However, I noticed that system was not updated and the build number remain the same. After couple of days, i get the update notification again and once again the same thing repeats. Can anyone tell me why its not getting updated?
rjwarrier said:
I have Nexus 4 running rooted JB 4.3Stock (Build JWR66V). I have also installed xposed framework. Recover is TWRP. Last week I got a system update notification. Update size is about 1.8 MB. After rebooting for installing the update, TWRP shows a message that Root permission may have been broken and displays a button to fix the permission. Even i choose to ignore this and reboot, root permission is not affected in anyways after reboot. However, I noticed that system was not updated and the build number remain the same. After couple of days, i get the update notification again and once again the same thing repeats. Can anyone tell me why its not getting updated?
Click to expand...
Click to collapse
Its the JWR66Y update, have you looked here for info http://forum.xda-developers.com/showthread.php?t=2145848. Or just reflash the factory image and reroot and you`re done http://forum.xda-developers.com/showthread.php?t=2010312.
Re:
Hi Is the update failing because of Xposed Framework? any idea?
rjwarrier said:
Hi Is the update failing because of Xposed Framework? any idea?
Click to expand...
Click to collapse
Off course, and you have a custom recovery and possibly a custom kernel. Updates can only be installed on factory images, unless you flash them with a custom recovery like TWRP.
Re:
gee2012 said:
Off course, and you have a custom recovery and possibly a custom kernel. Updates can only be installed on factory images, unless you flash them with a custom recovery like TWRP.
Click to expand...
Click to collapse
Hi it worked! The android build is now JWR66Y. I uninstalled the xposed framework and then flashd the update file thru TWRP. Eventhough after flashin the update, i flashed the SU, it didnt work (TWRP was showing that the installation was success). When i rebooted, cudnt find SU in apps. So I just installed the app from Play Store and it worked! Now I have root access too.
Thanks mate!
I currently have the 4.4.2 Google Play edition rom by Danvdh installed. I was performing a backup to flash the new 4.4.3 through CWM.
After the backup, there was a message that root may be lost and if I should fix it. I selected 'Yes'.
After the reboot, I no longer have root access. I have tried to re-root with motochopper and it continues to fail.
Can I restore a backup to regain my root? Or is there another way to regain my root access?
I tried searching for similar issues but could not find one that addressed my problem specifically.
Thanks in advance.
FIXED!!!
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
tuffgong2k3 said:
Not sure how or why, but SuperSu got messed up. Then I tried to open it, I was receiving an error that no binaries were found. I tried re-installing the apk without success. I then flashed the SuperSu zip in CWM recovery mode. Once it restarted, I was then able to open SuperSu and my root was back.
Click to expand...
Click to collapse
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
sway8966 said:
If you are using old CWM you would get the message saying "you root may be lost "and asking you to fix it before reboot. Never said "yes" to that questions. That will mess up your super su. If you read through the general section you could see some post about this.
Click to expand...
Click to collapse
Ahhh, thanks sway. I obviously did not find that section. I thought I had the latest CWM, but I guess I didn't. Time to update.
S4 i9505 not rooting through any apps
Hi, I recently flashed cm12.1 on my S4 i9505 and its working fine.
I need a working GApps package, I tried flashing 2 PA GApps(mini and micro), updated version which is TK GApps(mini), and also cleared calvik cache before and after flashing them as some forums suggested, but none of them worked and all Google apps keep crashing as soon as I boot in CM even the keyboard.
The 2nd issue: My phone is not rooted anymore and I tried a couple of rooting android and windows apps but none seem to root my phone, fails everytime. The errors which I faced are below.
Framaroot: "Your device seems not vulnerable to exploit included in Framaroot"
iRoot (android): "GT- i9505 No Root Permission"
iRoot (windows): "Device is connecting
eRoot (windows): Stuff written in chinese and no root button available as mentioned in different forums"
KingoRoot: "Root Strategy unavailable, just try it"
TowelRoot: Stuck on make it ra1n and after a while "towelroot stopped responding"
Root Checker: "Root checker has stopped working"
3rd Issue: I tried installing playstore apk till I get my GApps working, but it crashes everytime I open it, any solutions?
Thanks
AAF1994 said:
Hi, I recently flashed cm12.1 on my S4 i9505 and its working fine.
I need a working GApps package, I tried flashing 2 PA GApps(mini and micro), updated version which is TK GApps(mini), and also cleared calvik cache before and after flashing them as some forums suggested, but none of them worked and all Google apps keep crashing as soon as I boot in CM even the keyboard.
The 2nd issue: My phone is not rooted anymore and I tried a couple of rooting android and windows apps but none seem to root my phone, fails everytime. The errors which I faced are below.
Framaroot: "Your device seems not vulnerable to exploit included in Framaroot"
iRoot (android): "GT- i9505 No Root Permission"
iRoot (windows): "Device is connecting
eRoot (windows): Stuff written in chinese and no root button available as mentioned in different forums"
KingoRoot: "Root Strategy unavailable, just try it"
TowelRoot: Stuck on make it ra1n and after a while "towelroot stopped responding"
Root Checker: "Root checker has stopped working"
3rd Issue: I tried installing playstore apk till I get my GApps working, but it crashes everytime I open it, any solutions?
Thanks
Click to expand...
Click to collapse
1. Gapps: http://opengapps.org/
2. You cannot loose root acces on CM. It's impossible. You just need to activate it in developer settings and after that flash Supersu (optional). All the apps etc you tried is completely obsolete.
3. See post number 1.
Lennyz1988 said:
1. Gapps: http://opengapps.org/
2. You cannot loose root acces on CM. It's impossible. You just need to activate it in developer settings and after that flash Supersu (optional). All the apps etc you tried is completely obsolete.
3. See post number 1.
Click to expand...
Click to collapse
I already have root access set to "apps and ADB" in developer options. is this what you're referring to?
AAF1994 said:
I already have root access set to "apps and ADB" in developer options. is this what you're referring to?
Click to expand...
Click to collapse
Yes.
I would suggest performing a full wipe then flash CM and then the Gapps.
or you can try to just flash Supersu and your root will probably be back.
http://forum.xda-developers.com/showthread.php?t=1538053
Lennyz1988 said:
Yes.
I would suggest performing a full wipe then flash CM and then the Gapps.
or you can try to just flash Supersu and your root will probably be back.
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
I tried your suggestion, did a full wipe and flashed CM successfully through TWRP, the flashed GApps successfully, and SuperSU also, but just before rebbot, TWRP asked for "fix root" and when i swiped for yes, the reboot brought me back to Samsung logo and never rebooted CM... waited for about 15 mins before pulling the battery out...
I tried to flash CM and a stock firmware through odin then and now it says "Firmware upgrade failed, try KIES...... " odin fails to flash anything and gives error "No PIT Partition", even if I try to flash PIT files (tries 4 different files for i9505), all failed....
now I can only access download mode and lost TWRP too...
help please!
Install a stock ROM through Download Mode. This will get you back to a working state. From there get TWRP and then install CM12.1. And this time around, follow instructions! At no point were you EVER told you had to fix root, and as you found out, fixing root removes root access.
Honestly mate I was on CM for a while with my i9505 intl before deciding to try something else. I recommend this rom http://forum.xda-developers.com/showthread.php?t=2557353 . either the latest 5.1 or previous 5.0.1 release, they are both rock solid and there's great support for it too. They've even packaged cm addons as optional flash files.
Sent from my GT-I9505G using Tapatalk
---------- Post added at 04:15 AM ---------- Previous post was at 04:11 AM ----------
Sorry forgot to mention it's a Google play edition so rest assured your gapps come included.
Sent from my GT-I9505G using Tapatalk