Hi,
I apologize if I use the wrong term in advance.
I rooted my HTC One a few month back following this link:
http://forum.xda-developers.com/showthread.php?t=2473644
It has been working fine, I found out all of the sudden the phone is unrooted, it says "There is no SU binary installed", also, it failed to install OTA 4.3.
NOTE: There was a minor OTA a few weeks ago, I did update it.
I was wondering if someone could give me some directions. thank you
Did you install a custom recovery? That will cause the 4.3 OTA to fail. It will also let you flash the SuperSU or koush's superuser zip which should then restore your root access.
I don't have the ability to post a link yet, but if you search for Chainfire's SuperSu, you should find a page on XDA for 1.86. Download the zip to your One, flash it in recovery, and you should have root back!
Thank you for the reply. "I think" I found the thread you are talking about.
A stupid question, how do I "flash it in recovery"? thank you
GimliLongBow said:
Did you install a custom recovery? That will cause the 4.3 OTA to fail. It will also let you flash the SuperSU or koush's superuser zip which should then restore your root access.
I don't have the ability to post a link yet, but if you search for Chainfire's SuperSu, you should find a page on XDA for 1.86. Download the zip to your One, flash it in recovery, and you should have root back!
Click to expand...
Click to collapse
baysidefish said:
Thank you for the reply. "I think" I found the thread you are talking about.
A stupid question, how do I "flash it in recovery"? thank you
Click to expand...
Click to collapse
Assuming you've installed a custom recovery, here's what you'll need to do. First, load up the bootloader, then use Vol+Down/Up to select Recovery. Hit the Power button to select it. Once that's loaded, you should see an option either for Install or Install Zip from sd card. Select that, browse to where you saved the zip file on your phone, and select it. And that should be it!
If you don't get some sort list of options when you select Recovery from the bootloader, you'll probably want to install either TWRP or ClockworkMod Touch. You can find those in the Original Android Development section of the forum here. Right now I'm running TWRP but I like them both.
Have fun!
Related
Here's some info:
GSM Galaxy Nexus - Retail (bought from amazon).
Version: 4.0.1 (says no further update available).
Build Number: ITL41F
Can't remember if I rooted, then updated to ITL41F or not.
Followed THESE instructions successfully:
Code:
- Got drivers for Galaxy Nexus installed.
- Used "fastboot-windows oem unlock" and unlocked bootloader.
- Used "install-superboot-windows.bat"
Does this mean I am rooted permanently or have I missed out something?
I do not have Clockwork MOD installed. I don't plan on putting a custom ROM on the phone, I just want root access on the stock ROM.
Superuser is installed.
RootExplorer is denied superuser permissions (never had a prompt or anything). I can navigate to system/app/ and see superuser is in there. RootExplorer does see all the folders and files, but cannot be mounted in R/W mode.
Superuser Update fixer app says (under "force):
Code:
Checking signatures... ok!
extracting tiny busybox... ok!
extracting superuser.apk... ok!
Gaining root access ... fail!
In laymans terms, what do I need to do now to gain root access to my phone?
Also, to clarify, if I run a OTA update to the stock ROM, will it un-root my phone?
Thanks
Easiest thing is to unlock your bootloader, flash CWM, and then apply a su.zip.
I rarely ever actually root a phone. Usually I will install CWM and then flash a stock root rom.
Look in this thread for the Clockworkmod boot method...should work like a charm.
http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html
fastboot-windows.exe boot boot.superboot.img
Should have just used this after you unlocked boot loader for route
Anyways , the above will get you sorted
Merry Christmas
40Glock said:
Easiest thing is to unlock your bootloader, flash CWM, and then apply a su.zip.
I rarely ever actually root a phone. Usually I will install CWM and then flash a stock root rom.
Look in this thread for the Clockworkmod boot method...should work like a charm.
http://androidforums.com/galaxy-nexus-all-things-root/452146-how-root-samsung-galaxy-nexus.html
Click to expand...
Click to collapse
Thanks. However:
1) I'm hoping my bootloader will still be unlocked. Therefore will flashing CWM reset the phone, IE delete all the apps?
2) What happens if I don't really want to install CWM? Can I not be rooted without it?
3) It doesn't really explain why I don't seem to be rooted :/
I should also add that Root Explorer does see all the files and folders, but it cannot be mounted in r/w mode.
But I'll take a look at the link, thanks.
I don't understand why you want to be rooted then...
Sent from my Galaxy Nexus using XDA App
you should move your question to the galaxy nexus q&a forum, you will get more help there, if not find someone who already had the same issue. Read ALL stickies at the top of the forums. This will help solve your problem. Posting here will most likely get you bad attitudes fyi
Sent from my Galaxy Nexus
anotherxdauser said:
Thanks. However:
1) I'm hoping my bootloader will still be unlocked. Therefore will flashing CWM reset the phone, IE delete all the apps?
2) What happens if I don't really want to install CWM? Can I not be rooted without it?
3) It doesn't really explain why I don't seem to be rooted :/
I should also add that Root Explorer does see all the files and folders, but it cannot be mounted in r/w mode.
But I'll take a look at the link, thanks.
Click to expand...
Click to collapse
1. Unlocking the bootloader wipes the device not CWM. Mine came unlocked from retail store.
2. According to Superboot thread you can root without CWM.
3. Did you install busybox like the instructions say?
Similar to the previous post...since you have a GSM phone post/look in GSM thread for proper help.
Sent from my Galaxy Nexus using xda premium
Ditto what alot of others have said. Post about GSM model in CDMA area, plus not dev related. Asked for post to be moved to help you out.
merry xmas and good luck
Thanks for not flaming guys!
Thread moved......
drpancake said:
I don't understand why you want to be rooted then...
Click to expand...
Click to collapse
I need to be rooted to allow various apps to run to their full potential.
Well, tried the rooting process again, now no matter what method I choose, they are all saying "waiting for device".
Any pointers on what to do next?
you can try below if you like.
first of all, make sure your boot loader is unlocked.
secondly,
download CWM recovery from below.
http://forum.xda-developers.com/showthread.php?t=1357642
then download below su binary package i have made
http://forum.xda-developers.com/showthread.php?t=1395155
place su_signed_signed.zip into your sdcard (copy into your phone internal storage)
then turn off you phone, boot into bootloader mode (hold vol+ and vol- and power button).
once you are in it,
type
"fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img".
then using vol+ switch to boot recovery option and press the power button.
once you are in Clockwork Mode Recovery,
choose option "install zip from sdcard"
then browse and select "su_signed_signed.zip"
once it has done, you have rooted your phone.
now all you need to do is, reboot your phone, go to android market,
and install https://market.android.com/details?id=com.noshufou.android.su
then run Superuser,
go to settings,
then select "Su binary v3.XXX, tap to check for updates".
after you tap on that, it should say that SU is out of date.
click on update su binary, then you will be prompted for Superuser request.
once you have permitted it, it will then download the latest su binary and install it.
then you are done.
^^ Except I DO NOT WANT CLOCKWORK MOD on my phone.
However, as closure, I did manage to re-root my phone. I dried different drivers for the Samsung and somehow it just accepted the deivce and rooted it for me.
I've seen and answered this question quite a few times so I thought I'd just write down the procedure once so everyone can find it.
So you want the latest OTA and want it rooted but you have no idea how to get there? I can help.
Prior to yesterday I was running rooted stock with TWRP recovery. The OTA failed of course.
In order to install it and root I did the following.
1) install rooted stock image via odin (found at http://forum.xda-developers.com/showthread.php?t=1739426) This re-nstalled stock recovery.
2) install and run voodoo ota root keeper from the play store to preserve root.
3) took OTA download and let it install
4) ran voodoo OTA rootkeeper to restore root again
5) Install goo manager from play store
6) install twrp via goo manager
7) made a rooted stock nandroid backup.
The above procedure didn't wipe any of my data or settings because I came from rooted stock to begin with. I just used odin to restore the recovery and missing bloatware..
Hope this helps
Do you have the clockworkmkd recovery file I need to flash through odin? Does this mean I don't have to use adb?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Mastermachetier said:
Do you have the clockworkmkd recovery file I need to flash through odin? Does this mean I don't have to use adb?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I didn't use ADB. I used twrp for my recovery, but you can install rom manager and cwm recovery with it instead of goo manager and twrp.
I lost my root when i did the update...
can you give step by step on how to root again after the update and install the google universal search?
thanks...
Flashed the rooted stock image via Odin, update failed at 27%. Any ideas?
No idea. Just reporting on what worked for me.
Tlo218 said:
Flashed the rooted stock image via Odin, update failed at 27%. Any ideas?
Click to expand...
Click to collapse
If you've disabled or uninstalled stock at&t and Sammy apps (like Flipboard, clocks, etc.) the update will fail. You need to enable/reinstall stock apps.
Hi, I used Voodoo Root Keeper to regain root. However, in my device status it is now saying modified instead of normal. How can I fix that?
You can't. Don't worry about it.
one028 said:
I lost my root when i did the update...
can you give step by step on how to root again after the update and install the google universal search?
thanks...
Click to expand...
Click to collapse
That's beyond the scope of my original post.
knarfl1 said:
If you've disabled or uninstalled stock at&t and Sammy apps (like Flipboard, clocks, etc.) the update will fail. You need to enable/reinstall stock apps.
Click to expand...
Click to collapse
It looked like reflashing the rooted stock rom did reinstall the bloat I removed.
gunnyman said:
I've seen and answered this question quite a few times so I thought I'd just write down the procedure once so everyone can find it.
So you want the latest OTA and want it rooted but you have no idea how to get there? I can help.
Prior to yesterday I was running rooted stock with TWRP recovery. The OTA failed of course.
In order to install it and root I did the following.
1) install rooted stock image via odin (found at http://forum.xda-developers.com/showthread.php?t=1739426) This re-nstalled stock recovery.
2) install and run voodoo ota root keeper from the play store to preserve root.
3) took OTA download and let it install
4) ran voodoo OTA rootkeeper to restore root again
5) Install goo manager from play store
6) install twrp via goo manager
7) made a rooted stock nandroid backup.
The above procedure didn't wipe any of my data or settings because I came from rooted stock to begin with. I just used odin to restore the recovery and missing bloatware..
Hope this helps
Click to expand...
Click to collapse
worked fine for me
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
Here's the original site I read about this method way back when...
http://www.theandroidsoul.com/easy-guide-root-att-galaxy-s3/
Gunny's method does work, just giving another option
OP guides worked for me. Thanks
I like the new keyboard, less errors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Thanks for the info just would rather have a CMW flashable with root
I just want to say thank you I really appreciate your help and the time you put in to provide this info it worked like a charm and I really appreciate the help
I didn't loose root
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
z45123 said:
I just want to say thank you I really appreciate your help and the time you put in to provide this info it worked like a charm and I really appreciate the help
Click to expand...
Click to collapse
You're welcome.
So does this work if I lost root during the process?
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
dahlem said:
So does this work if I lost root during the process?
There's a much easier method to get root back after the update.
Flash CWM/TWRP
Flash the file I attached below.
Install Busybox from market
Reboot
Done deal
It does work. I tested earlier today from G1 stock unrooted. Pulled and installed the update, flashed CWM. Flashed the attached file, busybox download and profit. Then used gooomanager to change to TWRP
Click to expand...
Click to collapse
Yes, it does work. Get a custom recovery back (CWM) and flash the file I attached in my earlier post. Saves the time from flashing a stock rooted ROM and going from there as a starting point.
So I was rooted and running cynogenmod 10. I decided to go to root66 and I love it, but I noticed I no longer am rooted. I have supersu listed as an app but when I click on it it says "there is no SU binary installed and SuperSU cannot install it. This is a problem!"
I tried to boot into clockwordmod recovery and reflash it, but I know have stock android recovery. So I tried to download clockwordmod recovery through odin and it said pass but when I go into recovery it is still android recovery.
I d/l the toolkit but get an error using it.
I want to root to run wifi tether, what is the easiest way to get back root?
jongordo8 said:
So I was rooted and running cynogenmod 10. I decided to go to root66 and I love it, but I noticed I no longer am rooted. I have supersu listed as an app but when I click on it it says "there is no SU binary installed and SuperSU cannot install it. This is a problem!"
I tried to boot into clockwordmod recovery and reflash it, but I know have stock android recovery. So I tried to download clockwordmod recovery through odin and it said pass but when I go into recovery it is still android recovery.
I d/l the toolkit but get an error using it.
I want to root to run wifi tether, what is the easiest way to get back root?
Click to expand...
Click to collapse
I'm pretty sure you shouldn't be posting here with this type of problem...I see your post count so I can kind of figure out why now...shoot me a PM and I'll help you out. In the meantime, a root66 should solve your problem...are you using Odin correctly?
re: Root
jongordo8 said:
So I was rooted and running cynogenmod 10. I decided to go to root66 and I love it, but I noticed I no longer am rooted. I have supersu listed as an app but when I click on it it says "there is no SU binary installed and SuperSU cannot install it. This is a problem!"
I tried to boot into clockwordmod recovery and reflash it, but I know have stock android recovery. So I tried to download clockwordmod recovery through odin and it said pass but when I go into recovery it is still android recovery.
I d/l the toolkit but get an error using it.
I want to root to run wifi tether, what is the easiest way to get back root?
Click to expand...
Click to collapse
Try this:
First install a fresh copy of Superuser from the google play store. (free download)
Then install "TWRP recovery.
To install TWRP you need to install "GooManager" first which is a free download from the google play store.
Once installed, simply click the menu softkey on your phone and select "Install OpenRecoveryScript"
It's that easy.
Most likely you have a corrupted CWM in your phone which is missing files or some of the files in it are corrupt..
If GooManager pops up asking for root access and you allow it then TWRP recovery will fix your root issue I am sure.
Good Luck!
Why didn't you post this in the root66 thread? Wanting more eyes on your question is no excuse. This will be moved before sunset.....
Sent from the phalanges of my hand to the facet of your cranium.
LoopDoGG79 said:
Why didn't you post this in the root66 thread? Wanting more eyes on your question is no excuse. This will be moved before sunset.....
Sent from the phalanges of my hand to the facet of your cranium.
Click to expand...
Click to collapse
Help me out here please,
I too post questions and hope to get answers to troubleshooting, as the OP did. Open the main page, and there is NO sub forum for root66 listed.
The OP needed an answer to his troubleshooting and thus posted it in Galaxy S III Q&A, Help & Troubleshooting...
What is wrong, with that? Why does it have to be moved ? Is it NOT a question? Does the OP not need Help? Does the OP not have a question?
How is this query so different from others that is must be posted elsewhere, and Why?
It truly makes one hesitant on posting something and later not be able to find it because some almighty god has moved it..
I just don't understand. I must be wrong in thinking this was a forum one could seek to find help in a common interest. Trust me,
I am just totally confused. err... I couldn't find a confused sub forum to post this in. Sorry.
1) I want to know what error you got from the toolkit.
2) root66 comes with root access. It's kind of the whole point.
I don't know what you did to end up with the mess you have now, but here is how you fix it. You need to back up your data, and wipe everything. Then Odin root66 if that is what you want. Then if you want CWM, download the one from my signature. If you leave auto reboot checked in Odin, you need to drop to recovery mode before the phone boots (when Odin reboots it), because there is a script that will overwrite custom recoveries when the phone boots. When you exit CWM, it will tell you to disable the stock recovery. Just choose yes and done.
re: Root66 Forum
bobolinko said:
Help me out here please,
I too post questions and hope to get answers to troubleshooting, as the OP did. Open the main page, and there is NO sub forum for root66 listed.
The OP needed an answer to his troubleshooting and thus posted it in Galaxy S III Q&A, Help & Troubleshooting...
What is wrong, with that? Why does it have to be moved ? Is it NOT a question? Does the OP not need Help? Does the OP not have a question?
How is this query so different from others that is must be posted elsewhere, and Why?
It truly makes one hesitant on posting something and later not be able to find it because some almighty god has moved it..
I just don't understand. I must be wrong in thinking this was a forum one could seek to find help in a common interest. Trust me,
I am just totally confused. err... I couldn't find a confused sub forum to post this in. Sorry.
Click to expand...
Click to collapse
Well for one thing there is a root66 forum here, check it out: [Firmware/OTAs] T999(V) Official, Leaked & Root66 FW & OTA Updates!
Good luck!
ok i was able to install recovery img with cmd
now i want to root my device and again i cant find how
i download supersu and flash it in recovery and it did nothing when i open the supersu it say su binarry missing???
plz your help
bubu23 said:
ok i was able to install recovery img with cmd
now i want to root my device and again i cant find how
i download supersu and flash it in recovery and it did nothing when i open the supersu it say su binarry missing???
plz your help
Click to expand...
Click to collapse
Since your intent is to flash a custom ROM (based on your other thread here), there is no need to root prior to flashing the ROM. Just flash the desired custom ROM, as they are already rooted.
Also, probably no need to start a new thread, as you've already caused confusion by doing so. I wasted my time responding to your other thread (how to install custom recovery) when you already figured it out (you didn't update the other thread).
bubu23 said:
ok i was able to install recovery img with cmd
now i want to root my device and again i cant find how
i download supersu and flash it in recovery and it did nothing when i open the supersu it say su binarry missing???
plz your help
Click to expand...
Click to collapse
Just look up "supersu binaries zip." and download the latest from chainfire's website. Flash it from recovery and the notification will be gone.
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
No, i downloaded normal su (SuperSU) and then flashed it through TWRP. I don't know which su you are using, but there are loads of us who have installed SuperSU without an issue.
nemexs said:
It seems there would be a problem in flashing normal downloaded SU and have to go through the long process of flashing systemless SU after which have to upgrade it.
Is it normal for you guys too?
How come 1+3 bricks after installing normal SU?
b.t.w. personal note: thanks to one of the oneplus rep that was in the euro tour in Rome the TWRP recovery fix worked (sorry forgot your name ). Really appreciate the chat and help out!
Click to expand...
Click to collapse
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
PS: regular supersu is both systemless and "normal" root it makes a decision during installation determining whether your device can support normal root and if not then it does a systemless boot.img patch.
StykerB said:
You may have the wrong flashable, flashing supersu on the OP3 for me is very quick and painless. Make sure you have the latest from chainfire's website v2.76 at the time of me posting this. : http://download.chainfire.eu/supersu-stable
Click to expand...
Click to collapse
You beat me to pointing him to it. If I can add, there's a dedicated SuperSU thread to seek help if SuperSU causes an issue:
http://forum.xda-developers.com/showthread.php?t=1538053
Highly unlikely but just in case. If you are not sure, there are sufficient number of toolkits out there that can simplify the job for you.
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
nemexs said:
@tropicanapure @StykerB
Have tried them the only way I can flash SU is downloading @ahmed_radaideh 's oneplus3 toolkit and then flashing his SU. Tried the normal version and the problem seems to be present (brick), yes chainfire's su. If I don't want to do full wipe I'd have wipe system and just reflash stock and then systemless su
Click to expand...
Click to collapse
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
tropicanapure said:
Then you may want to check the process y you are using for this.
If I can ask what exactly are you trying to fix? Do you already have SuperSU installed? And you are trying to move to systemless?
Or are you unable to install SuperSU itself? If yes, then you may want to post to the SuperSU thread too.
Click to expand...
Click to collapse
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
nemexs said:
I had no problem in installing it systemless, however just wanted to see if everyone else had to go through the same process. It seems not, now I'm trying to find out how come I can't install normally.
Click to expand...
Click to collapse
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
tropicanapure said:
You still haven't mentioned the process you use[emoji6]
The process most commonly used via TWRP is to download the zip from the link above and flash it. That's all there is to it.
Click to expand...
Click to collapse
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
nemexs said:
my bad, yes I use twrp method 3.0.2 the most recent one, flash stock rom and then flash su
Click to expand...
Click to collapse
Assuming your bootloader is already unlocked beforehand, the straight answer to your question is yes, that's how most of us do it.
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
otonieru said:
No problem with flashing SU whatsoever,
and i rather not to use any toolkit to flash either recovery or anything,
fastboot for recovery and recovery for anything else,
Simple, straight and safe
Click to expand...
Click to collapse
doesn't work for me.