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
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. ^^
Did everything correctly from start to finish, flashed the SuperSU and Busybox package, but still no root access.
Couldn't install binary on SuperSU so I tried superuser... begins to download the update but fails at request for root access.
Please HELP! TWRP installed fine, i've installed the 4.2 camera keyboard and clock through twrp and they all work fine...
Titaniumbackup says it has root, but I guess that isn't right.. lol
fastboot says *TAMPERED* and *UNLOCKED*.
I also apologize if this isn't the right place for this, I can't post in the development thread due to the fact that i have <10 posts
You sound rooted, if not you wouldn't have been able to install the 4.2 camera. download superuser and try that. if all is good. then try superSU.
Also reboot your phone and try to install superSU again. but you are rooted.
cmay227 said:
You sound rooted, if not you wouldn't have been able to install the 4.2 camera. download superuser and try that. if all is good. then try superSU.
Also reboot your phone and try to install superSU again. but you are rooted.
Click to expand...
Click to collapse
Sorry I meant to include that superuser failed to gain root access in the process of updating. SuperSU won't even update, just goes to installation failed.
theguitarhero94 said:
Sorry I meant to include that superuser failed to gain root access in the process of updating. SuperSU won't even update, just goes to installation failed.
Click to expand...
Click to collapse
are you trying to flash the binaries from the SU app? if so you can't do that with S-on you need to Download the Zip from the SU website and flash in recovery... watch one of the videos on root/ custom recovery they explain it in detail
DNA help
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
bbeatz88 said:
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
Click to expand...
Click to collapse
From what I understand if you are flashing the available custom ROM you must wipe system AND format data for it to install successfully. If you are able to get back into recovery just wipe those two and reflash the zip I believe you will be good to go after that.
two_cents said:
are you trying to flash the binaries from the SU app? if so you can't do that with S-on you need to Download the Zip from the SU website and flash in recovery... watch one of the videos on root/ custom recovery they explain it in detail
Click to expand...
Click to collapse
Finally got it to work. Fix was around xda. Had to install superuser and I then disable superuser in SuperSU and now the superuser updates correctly. Super su still asks me to update and fails but I guess I'll just use superuser... Weird also it reboots when the update fails sometimes
My problem is that I rooted the phone OK but randomly apps will say that they cannot get root. Like titanium backup will randomly do that, a reboot will usually fix it. Thoughts?
ilogik said:
My problem is that I rooted the phone OK but randomly apps will say that they cannot get root. Like titanium backup will randomly do that, a reboot will usually fix it. Thoughts?
Click to expand...
Click to collapse
I found that manually launching Superuser, then launching TiBu worked when TiBu wouldn't get root.
bbeatz88 said:
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
Click to expand...
Click to collapse
md5 mismatch is because the backup is unrooted...
theguitarhero94 said:
md5 mismatch is because the backup is unrooted...
Click to expand...
Click to collapse
no... md5 mismatch is because the backup probably failed and the device rebooted before it completed. this is a known issue with both twrp and cwm recoveries on HTC DNA
Deuces said:
no... md5 mismatch is because the backup probably failed and the device rebooted before it completed. this is a known issue with both twrp and cwm recoveries on HTC DNA
Click to expand...
Click to collapse
gotcha, he didn't say anything about it not finishing, and I had the same issue a while back on my incredible and the backups definitely were completed... so i'm not really sure
OP, go see my post in this sub-forum about not being able to update the su binary. It should solve your issues.
Sent from my rooted and debloated Droid DNA.
I'm having the same issue, but disabling root in SuperSU doesn't work, and when I update the SU binary in SuperSU or Superuser my phone reboots.
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
I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
Hello, I have Android 6 Pure IMUI ROM 2.2 and my SuperSU binaries aren't updating.
Whwn I open SuperSU, it displays the update window, I select TWRP and it reboots to recovery.
After a while of installing on recovery, it skips MD5 verification and boots normally, and when I open SuperSU it ask's again that I need to update the binary.
If this helps, Im having this issue on the first update prompt that SuperSU gave me, after installing Magisk app.
Does anyone have any idea?
Thank you!
joaomPT said:
Hello, I have Android 6 Pure IMUI ROM 2.2 and my SuperSU binaries aren't updating.
Whwn I open SuperSU, it displays the update window, I select TWRP and it reboots to recovery.
After a while of installing on recovery, it skips MD5 verification and boots normally, and when I open SuperSU it ask's again that I need to update the binary.
If this helps, Im having this issue on the first update prompt that SuperSU gave me, after installing Magisk app.
Does anyone have any idea?
Thank you!
Click to expand...
Click to collapse
clear super su app data and check it.
also try by uninstalling magisk module.
miststudent2011 said:
clear super su app data and check it.
also try by uninstalling magisk module.
Click to expand...
Click to collapse
Hey, thanks for your help.
I tried uninstalling magisk a week ago, which resulted on me losing root, I simoly restored a backup and its all fine now (totally forgot to reply about this here)
Thanks once again and have a nice day
joaomPT said:
Hey, thanks for your help.
I tried uninstalling magisk a week ago, which resulted on me losing root, I simoly restored a backup and its all fine now (totally forgot to reply about this here)
Thanks once again and have a nice day
Click to expand...
Click to collapse
Glad to hear that you solved your problem