HI all, a few months i rooted my S3 phone then an update messed everything up, it stopped giving permissions to applications and they could not run, Im also trying to reset binary counter but triangle away is not working.
SuperSU is reporting that SU binary is not installed and it cannot install it.
None of the SuperSU functions do anything anymore and it does not function and i cannot uninstall it. I am trying to reset binary counter to see if it will fix the issues but triangle away keeps crashing on startup. Any advice please? Thank you
Other things that my phone does:
On startup it always says android is updating has dont for the past few months it is no longer downloading or installing other updates.
you need to root it again. The update will have removed it.
gzanothor said:
HI all, a few months i rooted my S3 phone then an update messed everything up, it stopped giving permissions to applications and they could not run, Im also trying to reset binary counter but triangle away is not working.
SuperSU is reporting that SU binary is not installed and it cannot install it.
None of the SuperSU functions do anything anymore and it does not function and i cannot uninstall it. I am trying to reset binary counter to see if it will fix the issues but triangle away keeps crashing on startup. Any advice please? Thank you
Other things that my phone does:
On startup it always says android is updating has dont for the past few months it is no longer downloading or installing other updates.
Click to expand...
Click to collapse
The update removed the SU binaries.
For the "Android is Updating..." thing; re-flash recovery (Via Odin and preferably a kernel after that) and wipe the dalvik cache, that should take care of the problem. Once you've installed the kernel, your root problems should go away as well
familyguy59 said:
The update removed the SU binaries.
For the "Android is Updating..." thing; re-flash recovery (Via Odin and preferably a kernel after that) and wipe the dalvik cache, that should take care of the problem. Once you've installed the kernel, your root problems should go away as well
Click to expand...
Click to collapse
Ok thanks i'l give it a try
familyguy59 said:
T" thing; re-flash recovery (Via Odin and preferably a kernel after that) and wipe the dalvik cache, that should take care of the problem.
Click to expand...
Click to collapse
ok i'v rerooted it and that fixed the SU problem, how do you go about re-flashing recovery with odin?
gzanothor said:
ok i'v rerooted it and that fixed the SU problem, how do you go about re-flashing recovery with odin?
Click to expand...
Click to collapse
Just follow the instructions for whatever recovery you choose .
Basic is file in PDA slot .
jje
Related
I have tried to Root my Vibrant on the UVKB5 update for a while now.
One Touch Root, says "no space on device", yet declares the phone rooted (su commands do not work).
Applications that require root, though, do work the su binary is always outdated and cannot be updated because "cannot find installed su binary".
This was found when I tried to boot into Clockwork Mod but only ended up in recovery mode - I downloaded the e3 fix that told me "the system cannot find the path specified. temp root failed! install cannot continue." All Try agains and Reboot and Try Agains result in the same answer.
I don't want to go back to JFD because I've done it before with a CyanogenMod with SGSII and everything crashed.
But if I did go to JFD, could I install CyanogenMod 7 the same? (the instructions assume I have the UVKB5 update)
Help.... please?!
Thanks!
i believe CM is like miui...as in the way of flashing it on the vibrant. u can either flash it from eclair 2.1 or froyo 2.2. as long as u can boot into recovery. but if u flash it from 2.1 u might have to pull out the battery then reflash from the new recovery since it bootloops...hope that helps.. i actually read how to install it..have u tried flashing project v which is a uvkb5?? then CM??that could be an easier way since project v is already rooted.
Sent from my Vibrant
I kinda wanna just install cyanogenmod...
all u have to do is this
1) root
2) install rom manager (free) from market
3) install cwm from rom manager
4) click reboot in recovery from rom manager(it will ask for root access)
5) reinstall package(u may have to repeat this step twice
6) put a custom rom of ur choice CM7 or miui
7) install it ....THAT'S IT....
deziguy420 said:
all u have to do is this
1) root
2) install rom manager (free) from market
3) install cwm from rom manager
4) click reboot in recovery from rom manager(it will ask for root access)
5) reinstall package(u may have to repeat this step twice
6) put a custom rom of ur choice CM7 or miui
7) install it ....THAT'S IT....
Click to expand...
Click to collapse
Did you even read my original post.
My phone is only half rooted. Clockwork won't open and the e3 fix can't find root.
I know what to do, I was reading the instructions.
Have you tried to update your Superuser app in the market? If you download it and install the update you might get a parse error or something that says it can't update the binaries. Scroll down in the market link for Superuser and there is an Update Fixer. Install and run that and then rerun/update the Superuser app.
Sounds like your binaries are out of date. This shoud fix it. Might also want to go to settings>manage apps>Superuser and clear cache/data. Once you update the SU, you'll have to re-grant permission anyways so clearing data shouldn't be an issue.
If that fails try to re-root is with Option A here http://forum.xda-developers.com/showthread.php?t=849028 There are two options here. Choose before you start.
A: Download this update.zip file to root your phone. You plan to install Rom Manager to flash CWR and a new ROM later.
Woodrube said:
Have you tried to update your Superuser app in the market? If you download it and install the update you might get a parse error or something that says it can't update the binaries. Scroll down in the market link for Superuser and there is an Update Fixer. Install and run that and then rerun/update the Superuser app.
Sounds like your binaries are out of date. This shoud fix it. Might also want to go to settings>manage apps>Superuser and clear cache/data. Once you update the SU, you'll have to re-grant permission anyways so clearing data shouldn't be an issue.
If that fails try to re-root is with Option A here http://forum.xda-developers.com/showthread.php?t=849028 There are two options here. Choose before you start.
A: Download this update.zip file to root your phone. You plan to install Rom Manager to flash CWR and a new ROM later.
Click to expand...
Click to collapse
That is not the problem. Installed Update Fixer. Signatures are "OK!". Force, just force closes the app.
A: I can't flash through CWR, as mentioned in my OP.
Looks like I'm going to have to start over again and just ODIN through this..
savbers said:
Applications that require root, though, do work the su binary is always outdated and cannot be updated because "cannot find installed su binary
Click to expand...
Click to collapse
I did read your OP and it says this. If you update your SU then the binaries will update too with the fixer. The you can download CWR from the market, reinstall it, grant SU permission and flash away. Try going into settings>manage apps>superuser and clear cache/data. If you are only half rooted as you say, then first thing to do us get full root back, eh? Good luck.
Woodrube said:
I did read your OP and it says this. If you update your SU then the binaries will update too with the fixer. The you can download CWR from the market, reinstall it, grant SU permission and flash away. Try going into settings>manage apps>superuser and clear cache/data. If you are only half rooted as you say, then first thing to do us get full root back, eh? Good luck.
Click to expand...
Click to collapse
Thanks for all the help, but in the end I did man up and went back to stock JFD and now Cyanogen mod runs amazingly. And the MMS that didn't use to work on my phone -does!
Google Apps didn't install properly and I had to re-install the rom 'cause i was impatient.
Love it now though... and google thinks I have a nexus s. ^^
Hi,
My phone quits during the update process to JB in recovery at around 32% and then once booted back into android displays a popup saying failed to update software, try again using kies or use a samsung service centre. It doesn't connect to kies (stays stuck at connecting) and pretty sure samsung will just wipe the phone which I'd rather not do.
I originally had the phone rooted with Siyah 1.5.3 but have since reflashed the stock i9300 3e android recovery, reset the flash counter to 0 and official binary with triangle away and fully removed root from within SuperSU. I have also wiped the cache, any ideas on why the update is still not applying? I would like to stick the stock rom and avoid wiping.
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Aladdin Sarsippius said:
Same here,
Stock Rooted S3 with CWM and busybox. Used Mark Skipper's toolbox for that, and also used that to unroot, flash stock recovery and uninstall busybox. JB update also gets an error at 32%. Do I have to uninstall SU too? Really don't want to do a complete reinstall since CMW didn't manage to backup my phone...
Click to expand...
Click to collapse
Haven't tried to update since I unrooted (ota is only available during a few hours in the afternoon here and hasn't become available yet) but it removed the SuperSU.apk when I unrooted. Stweaks app is still there but doesn't work due to the lack of root. The only other non-stock thing left is the kernel but I don't think that should matter seeing as I've used triangle away and reset the counter and binary to official. I'll post on whether it works next time around
Try removing cwm somehow, many people find that this is a problem, same happens with me, apparently cwm fixed it in newer updates.:good:
CWM is the culprit. I really don't know why people insist on using that. It is utterly useless.
Download the ROM you want from samsung-updates.com or through CheckFUSDownloader, extract the .MD5 file from the downloaded ZIP, copy the .md5 file to the device, and flash using MobileOdin.
Then, if you want, just flash SiyahKernel again using Odin.
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
this worked for me.
viva.fidel said:
I had already removed cwm recovery and replaced it with the stock i9300 3e recovery but still didn't work, I downloaded the ota update manually and found it be a small incremental update which still didn't flash in the stock recovery due to a mount error..
in the end I checked the latest update available from checkfus, downloaded it from samfirmware.com and flashed it using odin.. and now got jelly bean without wiping! Reflashed siyah & su binary and everything is good now. Only issue now is the OS sees the device being modified (even after triangle away reset) so a future ota updates is off the cards.
Click to expand...
Click to collapse
in triangle away there is a box that says something like modified workaround, tick that then run triangle away, when it restarts your status will be normal, then go to application manager and remove triangle away. after about 15 minutes go into superSU and unroot.
So, a couple days ago SuperSU gave me the update message. did it through PhilZ's recovery. then, SuperSU said there was no binary file.
Next I downloaded both superuser and superuser zips from root thread and have tried flashing both.
Now, I have SuperSU and it is working(with update messages).
Question, How do I go about updating the binary without losing it?
Appreciate any help...
masterjakeway said:
So, a couple days ago SuperSU gave me the update message. did it through PhilZ's recovery. then, SuperSU said there was no binary file.
Next I downloaded both superuser and superuser zips from root thread and have tried flashing both.
Now, I have SuperSU and it is working(with update messages).
Question, How do I go about updating the binary without losing it?
Appreciate any help...
Click to expand...
Click to collapse
turn off auto update and wait
Well, when i start superSU it comes right up to the upgrade or cancel. if i cancel, it closes.
Also, Titanium backup says something about it being an outdated binary and it "may" not work correct?
I have no clue where to find the correct binary to flash through recovery...
masterjakeway said:
Well, when i start superSU it comes right up to the upgrade or cancel. if i cancel, it closes.
Also, Titanium backup says something about it being an outdated binary and it "may" not work correct?
I have no clue where to find the correct binary to flash through recovery...
Click to expand...
Click to collapse
it's fixed now ... just choose update and then choose twrp/cwm option
I updated yesterday no problem
Hey guys,
I have an i9300, rooted with slimbeam installed. A few days ago I dropped my phone and the screen cracked and the display disappeared; so I got it replaced. When I turned my phone on again, it was stuck on the boot screen. So I fully wiped my phone and flashed slimbean again (as I already had the file on my external SD card). This got me passed the boot screen and my phone is working fine except it seems like I don't have proper root access. I downloaded a root checker and thats the message I got "Does not have proper root access" and when I run superSU it said "the su binary needs to be updated" so I click on update and I get a message saying " install failed. Reboot and try again" I reboot and tried again and same error
Anyone know what my best course of action would be?
EDIT: It also randomly keep rebooting.
Thanks a lot guys!
Cheers
bd101 said:
Hey guys,
I have an i9300, rooted with slimbeam installed. A few days ago I dropped my phone and the screen cracked and the display disappeared; so I got it replaced. When I turned my phone on again, it was stuck on the boot screen. So I fully wiped my phone and flashed slimbean again (as I already had the file on my external SD card). This got me passed the boot screen and my phone is working fine except it seems like I don't have proper root access. I downloaded a root checker and thats the message I got "Does not have proper root access" and when I run superSU it said "the su binary needs to be updated" so I click on update and I get a message saying " install failed. Reboot and try again" I reboot and tried again and same error
Anyone know what my best course of action would be?
EDIT: It also randomly keep rebooting.
Thanks a lot guys!
Cheers
Click to expand...
Click to collapse
If you have Phil's touch recovery then go in the settings and reroot your device and install supersu app from play store and update your binaries...
Sent from my GT-I9300
kunal1540 said:
If you have Phil's touch recovery then go in the settings and reroot your device and install supersu app from play store and update your binaries...
Sent from my GT-I9300
Click to expand...
Click to collapse
Would that be in recovery mode? Cause I couldn't find anything regarding root there. or should I follow this http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953
Thanks! I realy appreciate your help
bd101 said:
Would that be in recovery mode? Cause I couldn't find anything regarding root there. or should I follow this http://forum.xda-developers.com/galaxy-s3/orig-development/i93xx-philz-touch-t2002953
Thanks! I realy appreciate your help
Click to expand...
Click to collapse
yes in philz recoverey in philz settings i think...re root option and install supersu from play store..or
alternative is to flash supersu zip file from the respective thread..
Flash the latest supersu's .zip from a custom recovery.... Here's the thread
http://forum.xda-developers.com/showthread.php?t=1538053
kunal1540 said:
yes in philz recoverey in philz settings i think...re root option and install supersu from play store..or
alternative is to flash supersu zip file from the respective thread..
Click to expand...
Click to collapse
i did flash superuser from the respective thread. When I run the root checker app I still get the "Sorry! This device does not have proper root access". When I run SuperSU it says "There is no SU binary installed and SuperS cannot install it. This is a problem! "
What do I do now? I was hoping flashing SuperSU would solve the problem.. but i guess that didnt work
So I just successfully installed CM13 on my i9300. Everything works fine, but I just found out I lost root rights.
I went and downloaded the Super SU app from the PlayStore, launched it and that gave an error that there's no SU binary installed and I need to manually root again.
So I downloaded UPDATE-SuperSU-v2.65-20151226141550.zip, put it on the sdcard, rebooted into CWM Recovery, installed the zip and booted back into the system (when prompted to fix boot I selected no as recommended), but now I STILL HAVE NO ROOT RIGHTS and the Super SU app still gives the same error.
Is there a specific SuperSU.zip I should be installing in recovery to make it work?
Or is something wrong with the recovery and do I need to flash that through Odin? (I don't think this is the case though, as flashing CM13 and gapps went completely fine)
Thanks for any isnight and tips
There is already Root option in developer settings.Can you try it?
ArdaCsknn said:
There is already Root option in developer settings.Can you try it?
Click to expand...
Click to collapse
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
warriotox said:
In Developer Options I have set Root Access to Apps and ADB it didn't give any error, but doesn't seem to be doing anything either... In file manager I can't reach root, Root Checker app fails, Super SU gives than binary error, and another app that requires Root Access says I don't have it as well..
Click to expand...
Click to collapse
Flash rom again and dont flash SuperSu its better now without using SuperSU
I got the same problem. I tried to root with odin again but it didnt work...
Flash cm13, wipe data and cache and flash cm13 again. Cm13 should be pre rooted.
Sent from my HTC One M9 using Tapatalk
Hi Guys, I have the same problem too after CM13. Unfortunately rooting again with ODIN flashed stock recovery back and am stuck on CM13 now with no root and stock recovery. Can someone help please? Below is the detailed description of what happened.
----------------------------
1. My Samsung Galaxy SIII International (I9300) was rooted and I had CM11 stable/snapshot version there since last 2-3 weeks.
2. Yesterday, I tried upgrading the latest CM13 nightly for my device.
3. While doing so, and rebooting, it asked me the normal message "root possibly lost, fix, yes or no". I accidentally pressed no.
4. Then I noticed after CM13 was flashed, that I do not have root access anymore. Please note that at this point in time, I was not aware that it has to be explicitly enabled in developer options.
5. I came to know that I lost root when I tried to boot in to recovery (CWM) to install gapps.
6. Now, under the impression that I do not have root anymore, I tried to root again with Odin as I had been doing all these days.
- By doing that, ODIN removed my custom recovery (CWM) and flashed it with stock recovery.
- Though ODIN said PASS after reboot, I still do not have root access.
7. Removed cache, wipe data, and factory reset, multiple times but no help.
8. Enabled root for both apps and adb in Developer options, but no use.
9. I also tried KINGO root ( a very popular tool for SGS3 these days) but in vain.
10. Now, am stuck with CM13 and stock recovery and unable to do anything with ROM manager or anything else as I do not have root anymore.
11. Am able to install few apks for whatsapp and facebook for now and living with it, but it wouldn't let me install playstore apk too anymore.
Highly appreciate any quick feedback.
same here after rooting once cm13 by developer option, for some reason i had to use hide my root app, now unable to get root back
Its a problem with the s3, it forgets root. The most reliable is chainfire and sticking with a stock rom.
You must:
Wipe to factory,
flash an original rom via odin,
Boot straight to recovery and wipe to factory again,
Flash original rom again,
Boot straight to recovery and wipe to factory,
Allow the phone to boot.
You must flash at least twice and reset to factory at least twice, even tho I sad it thrice, to kill all remnants of the old rooted rom.
Then you can flash chainfire via odin and go from there.
Beamed in by telepathy.