Database Develop

[HOWTO] get root back after ota update!

this is how i did it anyways. i had to flash the boot.img and update via stock recovery to get the ota to flash. but then no root!
so heres how i got it back:
download the superboot/paulobrien method (http://forum.xda-developers.com/showthread.php?t=882333).
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!

I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
The method I used was:
1. Boot into fastboot.
2.
Code:
fastboot flash recovery recovery-clockwork-3.0.0.0-crespo.img
3. Reboot from fastboot directly into recovery (not doing so will cause android to replace CWR).
4. Mount USB, copy su-2.3.6.1-ef-signed.zip to the /sdcard via windows/linux
5. Mount /system
6. Install update from zip (browse to were you put su-2.3.6.1-ef-signed.zip).
7. Install it, and reboot.
8. open root explorer, and rename /etc/install-recovery.sh to install-recovery.sh.old
9. open ROM Manager, reflash CWR.
now you are all done, rooted, w/ CWR

I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).

Luxferro said:
I've got root back, but not by that method. I think it might be a mistake to flash that boot.img, as the 2.3.1 update patched boot.img... so replacing it with one from 2.3 might not be the best idea. But I guess no one really know what the changes might be.
I guess time will tell
Click to expand...
Click to collapse
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
im using stock recovery.

I'm rooted on 2.3.1 but I lose clockwork recovery when I reboot an gota reflash it using rom manager. Anyone having this problem

k0mpresd said:
its not flashing it. read the command. its only booting to that image to install su. then reboot will bring you back to stock 2.3.1 boot.img.
Click to expand...
Click to collapse
Sure it is. But on Android bootup, a script is running somewhere to replace it with stock recovery. They did this on Droid_1 after the first or second update (that's my only other android phone... so my android experience is limited).
edit: I just found the script. It's /etc/install-recovery.sh .... just renamed my to install-recovery.sh.old. gonna reflash CWR and test it now.
edit2: yep, works great now. CWR, and retained my 2.3.1 boot.img

So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone

chris6278 said:
So is this something that the devs of clockworkmod need to fix in order to not lose clockwork recovery when u reboot the phone
Click to expand...
Click to collapse
No, it's a safety mechanism so you can't lose recovery... It has nothing to do with clockworkmod. Someone can make a root script or app that disables it easily. Or people can just do it themselves manually.
edit: actually, all that needs to be done is add some code to the update script inside su-2.3.6.1-ef-signed.zip so when it installs the update, it renames install-recovery.sh

distortedloop said:
I reflashed CWM, then from CWM, remounted /system, then used adb to chmod 6775 su. That restored root pretty easily.
What Recovery image are you using? Are you able to get into it consistently? I can't from fastboot except for if I immediately hit it up after flashing CWM with fb, or from ROM Manager (flash from RM, then select reboot to recovery).
Click to expand...
Click to collapse
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks

If u dont mind can u please provide the instructions on how to do it manually. Id really appreciate it. Sorry im a noob lol

Where in root explorer do i need to rename

Where in root explorer do i rename it

plmiller0905 said:
I want to attempt to restore my root by using your method. But I'm lost at the part when you use adb chomd 6775 su,
When I go into adb, do i just type chomd 6775 su? Do I have to download something else to use this? Please explain, thanks
Click to expand...
Click to collapse
chmod needs to be done at a # prompt.

chris6278 said:
Where in root explorer do i rename it
Click to expand...
Click to collapse
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...

Is it just me or does adb remount no longer work?
If I use the old koush rootboot.img it works, but no wifi, if I use the stock boot.img, I get no wifi but am able to remount.

I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes

chris6278 said:
I can read an ive done all the steps u posted but my ? Is where in root explorer do i find /etc/install-recovery.sh so i can rename it? Im learning this as i go so excuse me if i sound stupid sometimes
Click to expand...
Click to collapse
do you have root explorer? if not, it's just a file explorer that has root access. by default when you open it you are at /
you need to scroll down to /etc
go in that folder and find the install-recovery.sh
look up top for the button to turn it from read-only to read-write, click it
go back to the file long press it, and then choose rename.

Luxferro said:
I'm trying not to be rude... but if you can post in this thread, you can read it to. Before you asked your question a couple different step by step posts outlined all you need to know.... and this thread is only 2 pages...
Click to expand...
Click to collapse
Thanks..I already rerooted but thanks anways

I got root explorer an followed ur directions an now everything works great. Thanx for ur help an sorry for being a pain lol

[Solved] Can't flash Clockwork Recovery.

I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
failed to copy recovery.img permission denied
Click to expand...
Click to collapse
Thanks for any help, I'm hoping it's just a small little step I missed.

mikeeey said:
I've read the guides, tried manual and the simple download from the Android Market. Here's what happens:
I've rooted my Thrill with SuperOneClick 2.1.1. It was a successful root from what I can tell, it added Superuser into my apps, and I was able to download Rom Manager from the Android Market.
If I try using Rom Manager and click "Flash ClockworkMod Recovery" It appears to install. But when I hit "Reboot into Recovery" it just reboots like normal.
If I try to manually get into recovery mode by holding volume down and the 3D button it just boots into the stock recovery mode.
When I try to manually install Clockwork and copy recovery.img to /data with cmd I get this:
Thanks for any help, I'm hoping it's just a small little step I missed.
Click to expand...
Click to collapse
This is covered in the cwm thread in development section you need to use a file explorer that has root access and change permissions to the /data folder. You can use es file explorer, its free. Open it go into settings then browse as root... not really sure exact steps but they are in the came thread.

O my such a small step I missed! Thank you! Ill try this later today.

Permissions of /data are set to R/W but I still get the same error..
I'm starting to wonder if the cause of this is because I tried using Rom Manager to flash clockwork, THEN tried the adb method. Maybe it already being there is causing the permission denied?
edit: so it looks like it was as simple as me looking over the permissions and thinking I saw everything was checked, but really the two checks from the left under "other" were grayed out lol, checking those fixed it.

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu

Nexus S & Galaxy Nexus one click root toolkit ! Unlock bootloader+CWM+Su(or)SuperSu
This tool will root you nexus s/Galaxy Nexus install su or super su and ClockWorkMod recovery!!
For Nexus S:4G,I9020T,I9023,I9020A.
Galaxy Nexus:GSM/Verizon/Sprint
Disclaimer!
Your warranty is now void.
I am not responsible for bricked or damaged devices
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
DOWNLOAD
Click to expand...
Click to collapse
Current Version (Nexus S + Galaxy Nexus) 3.5: http://d-h.st/qaL
MIRROR:http://www.mediafire.com/download.php?1if2rvgpcte2rcs
Old versions:
3.0: http://d-h.st/mhO
2.0: http://dev-host.org/gcZ (nexus s only)
1.0: http://dev-host.org/bEE (nexus s only)
HOW-TO
Click to expand...
Click to collapse
just unzip the content and run the tool ! drivers are included in case you need them.
incase you had any problems try rerunning the tool,and if you got superuser/supersu app but you are unable to use root apps,update superuser/supersu from the play store then update the binary from inside the app.
CHANGELOG
Click to expand...
Click to collapse
V3.5
-added support for jelly bean
-few script optimization
-updated superuser and supersu
V3.0
-added support to galaxy nexus and all it's variants.
-added support to install super su.
-moved from *.bat to *.exe
-new icon
-su/super su, will now automatically flash no need to touch "install zip"
-skip bootloader unlock if you are already unlocked.
-update drivers
V2.0
-Removed "sticky.bat"
-modified su flashing script.
-the recovery now will stick automatically no need to flash any file after rooting or running any script.
V1.0
-initial release
ALL DATA WILL BE WIPED FROM DEVICE(only if bootloader is locked)
credits
-Chainfire for super su
-ChainsDD for superuser
-Pdanet for drivers
-Clockworkmod team for recovery
-my friend for the icon​

am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?

raducux said:
am i going to loose everithing on USB storage ? or jjust sistem data ? i have to have a full rom right ?
Click to expand...
Click to collapse
if your bootloader is locked then yes you will loose everything on USB storage,if the bootloader is already unlocked you will not loose any data,you don't need to flash a rom after rooting the device as it will not wipe the system.

Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?

Sticky please
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.

Romaniac said:
Hi, I installed the drivers on my computer and am currently running the run.bat file. It's saying my device is not found. I have USB Debugging on, and USB storage is on. Any ideas?
Click to expand...
Click to collapse
Turn off the usb storage,you just need usb debugging enabled if you turned on usb storage it will not work
stewie-droid said:
Can i replace CWR with newest img version?
PLEASE STICKY THIS THREAD ON TOP.
Click to expand...
Click to collapse
The tool includes the latest cwm img,but if you want to replace it with another one you can do,just make sure you rename it to same name of the img in the root tool folder,but make sure that the recovery you will use is compatible with the nexus s

After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.

Ritwik7 said:
After I execute run.bat the phone is rooted. I reboot using ClockWorkMod Recovery. Then, when I run sticky.bat and follow the instructions I get the following:
[email protected]:/ $ su
su
[email protected]:/ # rm /etc/installrecovery.sh
rm /etc/installrecovery.sh
rm failed for /etc/installrecovery.sh, No such file or directory
What should I be doing? Please help.
Click to expand...
Click to collapse
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.

Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.

Ritwik7 said:
Thanks for your reply. I used a FixRecovery.zip file from another thread and flashed it after executing run.bat again. Now I am able to boot into ClockWorkMod.
Click to expand...
Click to collapse
My friend can you guide where i can find this .zip because i m facing the same problem.thank you in advance

Ok I got it to stick by using Root Explorer to mount it as read/write first then ran the sticky.bat. ICS is the rm /etc/install-recovery.sh command.

m.sabra said:
The phone should booted normally when running the sticky.bat (On the home screen),there is nothing to worry about just Complete the instructions normally one of the two scripts will fail since the name of the file differ in gingerbread and ics,try this rm /etc/install-recovery.sh and continue the instruction it should work and clockworkmod recovery would stick.
Click to expand...
Click to collapse
I tried this and when I want to do the sticky.bat, when I type the "rm /etc/install-recovery.sh" it sais rm failed for /etc/.., Read-only file system

I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966

karx23 said:
I had the same problem with sticky.bat.
Once you 're done with run.bat and it reboots in cwm just flash fix-recovery.zip
http://forum.xda-developers.com/showthread.php?p=20432966&highlight=fix-recovery#post20432966
Click to expand...
Click to collapse
thanks ! added the link to the OP in case anyone had problems like this.

Argh, I seem to have successfully unrooted my Nexus S 9020t and had it rebooted back in, but while it was booting up again I accidentally pressed a button and it told me "error: device not found" twice followed by "<waiting for device>".
Unfortunately my phone has already been rebooted, but it still seems to be waiting for my device. I'm not sure if I can disconnect this device from USB while this is going on, so uh, what do I do?
Edit: Disconnected and reconnected the USB cable on the phone to see what would happen, and it seems to be ok. I'm still stuck on "waiting for device" though. Should I consider restarting the process again?
Edit Edit: Decided to just try to redo the process all over again...seems to have worked!

Updated tool to version 2.0 ! check the changelog in OP, it should solve all sticky recovery related problems,as i removed sticky.bat and now the recovery will stick automatically without the need of running any commands or flashing any fixes.
thanks for reporting problems and feedbacks

thank you for this

Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?

Lelouche said:
Okay, I've tried to run this but it always fails at flashing the recovery.. Any help?
Click to expand...
Click to collapse
Ok first have you unlocked your bootloader when the tool asked you to use volume buttons to chose yes and unlock ? (If you did this you should see an unlocked lock under google logo when booting the phone) if you didn't just run the script again and unlock the bootloader.
Are the drivers installed properly ? When you connect the phone to the pc check device manager to see if the PC recognizes the phone (the drivers are included in the tool in case you need them .
And last check the root tool folder on your pc it should have a file called cwm.img if it doesn't then download the tool again.

SuperUser is not visible after the process
I am on stock ICS, I had previously unlocked the bootloader, then I did the whole process mentioned in this thread. It showed me the CWM menu but when I did the reboot, I couldn't find the superuser app. Then to test whether it is rooted or not, I installed titanium backup but it says the device isnt rooted. What to do now? I tried SuperOneClick but it doesn't seem to work.
Edit: Thanks guys, sorry. It was my mistake, I didnt do the whole process in a right way. It is working as expected.

Help for xolo a500s ips

Hi guys today I have rooted my xolo a500s IPS
using farmaroot but when I tried to mount system
r/w for pushing some apps and removing some on
system partition but it is not mounting because of
that i cant make changes on system please help
how can I mount system partition

TheRoHit18 said:
Hi guys today I have rooted my xolo a500s IPS
using farmaroot but when I tried to mount system
r/w for pushing some apps and removing some on
system partition but it is not mounting because of
that i cant make changes on system please help
how can I mount system partition
Click to expand...
Click to collapse
Can you mount in CWM? If yes, then try this workaround. Mount system and Flash Aroma File Manager. Now you have mounted System folder for pushing and deleting APKs. :thumbup:
Press thanks if helped. :thumbup: :thumbup: :thumbup:
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands

hnkotnis said:
Can you mount in CWM? If yes, then try this workaround. Mount system and Flash Aroma File Manager. Now you have mounted System folder for pushing and deleting APKs. :thumbup:
Press thanks if helped. :thumbup: :thumbup: :thumbup:
Sent from my GT-S5360 Gadget of Mass Destruction using xda-app
Using CWM........Busybox Commands........No I use my hands
Click to expand...
Click to collapse
I have not installed cwm yet

TheRoHit18 said:
I have not installed cwm yet
Click to expand...
Click to collapse
Which browser are you using ? And check again if your phone is rooted see if you have the SuperSU app.
I recommend you to use Root Browser.

PrimeNexes said:
Which browser are you using ? And check again if your phone is rooted see if you have the SuperSU app.
I recommend you to use Root Browser.
Click to expand...
Click to collapse
I used all apps like es file explorer , root browser, root explorer but system can't be mounted on rw I really what's the reason and my xolo is rooted

TheRoHit18 said:
I used all apps like es file explorer , root browser, root explorer but system can't be mounted on rw I really what's the reason and my xolo is rooted
Click to expand...
Click to collapse
Do you get a prompt form the SuperSU application for allowing the root access ? If you don't check the superSU settings you may have disabled the root access for any app.

PrimeNexes said:
Do you get a prompt form the SuperSU application for allowing the root access ? If you don't check the superSU settings you may have disabled the root access for any app.
Click to expand...
Click to collapse
yes I get prompt from supersu

I also tried installing busy box but it also not getting installed

TheRoHit18 said:
yes I get prompt from supersu
Click to expand...
Click to collapse
I recommend you to check the SuperSU setting as you problem does sound like root access is not available to the app.
Try installing terminal emulator and type "su" in the terminal and press enter if you get "[email protected]: / # " then the apps are getting the access.
then type "reboot" and if your phone reboots then the apps can interact with root file.Give it a try and post the result.

PrimeNexes said:
I recommend you to check the SuperSU setting as you problem does sound like root access is not available to the app.
Try installing terminal emulator and type "su" in the terminal and press enter if you get "[email protected]: / # " then the apps are getting the access.
then type "reboot" and if your phone reboots then the apps can interact with root file.Give it a try and post the result.
Click to expand...
Click to collapse
bro I tried this via adb the phone is rooted and I also tried mounting system via adb but it showing read only file system

TheRoHit18 said:
bro I tried this via adb the phone is rooted and I also tried mounting system via adb but it showing read only file system
Click to expand...
Click to collapse
Can you upload some pics like the settings page of superSU,the error you get while browsing the root files with Root Explorer ?
And tell me what thing you did for rooting.

PrimeNexes said:
Can you upload some pics like the settings page of superSU,the error you get while browsing the root files with Root Explorer ?
And tell me what thing you did for rooting.
Click to expand...
Click to collapse
here are the some ss...

TheRoHit18 said:
here are the some ss...
Click to expand...
Click to collapse
First of all upgrade the superSU or install the latest Frameroot from Here
And then try

PrimeNexes said:
First of all upgrade the superSU or install the latest Frameroot from Here
And then try
Click to expand...
Click to collapse
I have used it for rooting my xolo really m confused my phone is rooted but still I can't make changes in system also I tried installing busybox but failed to install

TheRoHit18 said:
I have used it for rooting my xolo really m confused my phone is rooted but still I can't make changes in system also I tried installing busybox but failed to install
Click to expand...
Click to collapse
I am not getting whats the problem so first you you install the CWM so that we can install a Custom ROM so if your files or Settings are messed up it will be cleared or just factory reset your phone or Super-wipe the phone.

PrimeNexes said:
I am not getting whats the problem so first you you install the CWM so that we can install a Custom ROM so if your files or Settings are messed up it will be cleared or just factory reset your phone or Super-wipe the phone.
Click to expand...
Click to collapse
I have installed cwm the problems is system is not mounting to r/w coz of that I can't remove or push apps to system

TheRoHit18 said:
I have installed cwm the problems is system is not mounting to r/w coz of that I can't remove or push apps to system
Click to expand...
Click to collapse
can you mount it in CWM ??? And did you installed a custom ROM ?

PrimeNexes said:
can you mount it in CWM ??? And did you installed a custom ROM ?
Click to expand...
Click to collapse
yes I can mount in cwm but when I flashed a s4 launcher successfully but nothing happend

TheRoHit18 said:
yes I can mount in cwm but when I flashed a s4 launcher successfully but nothing happend
Click to expand...
Click to collapse
Try to flash a Custom ROM for IPS I will try to make a zip that checks your R/W.But flash a CustomROM for a trial but first make a nandroid backup :good:

PrimeNexes said:
Try to flash a Custom ROM for IPS I will try to make a zip that checks your R/W.But flash a CustomROM for a trial but first make a nandroid backup :good:
Click to expand...
Click to collapse
can you pls suggest me a c ROM for my IPS

Cannot root... CWR: repeatedly attempted supersu and superuser

Hello,
I've unlocked the bootloader on my One, then proceeded to install supersu via zip through clockworkmod recovery.
I rebooted, attempted to gain root access, and was unable to.
I then rebooted into clockworkmod recovery and attempted to install superuser from this thread, rebooted and was unable to gain root. I then installed supersu from the same thread, and was unable to gain root.
Lastly, I attempted to wipe the cache partition and dalvik cache in effort, and still I am not able to gain root.
I'm unsure exactly what to do from here on out, as the process is truly very simple, but just not working.
Should I flash an official recovery and start over?
Thanks,
Matt

Have you opened the su app and updated the binaries?

I used twrp recovery a few days ago when I rooted. try to flash latest version of twrp through adb and wipe, clear cache,and retry.
If you still have trouble, check out wwjoshdew on youtube. I followed his instructions and rooted/unlocked with no hiccups.

BD619 said:
Have you opened the su app and updated the binaries?
Click to expand...
Click to collapse
Thanks for replying quickly.
The state I'm in now is:
- The SuperSu apk is gone.
- Superuser is installed.
- Root Checker, Helium, ES File Explorer's "root explorer" report no root
- Shark reports root (aka starts).
- superuser info reports `su` 3.2.18
- Used ES File Explorer to verify presence of `/system/bin/su`
Any idea on what could be wrong?
Thanks again,
Matt

How about another try on TWRP 2.6.3.0 recovery?

Sure, I will try this, Originally I tried TWRP, but couldn't access my internal storage (don't know why). Attempted sideload and failed, so I install clockwork and was able to install superuser.zip from /sdcard/.
Thanks!

Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)

branded said:
Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)
Click to expand...
Click to collapse
Get the latest version of SuperSU from here
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
I would suggest using it as it is updated more often then superuser as far as I know

Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt

Glad you got it enjoy

So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!

dtracycar said:
So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!
Click to expand...
Click to collapse
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...

Devilish_Angel said:
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...
Click to expand...
Click to collapse
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?

dtracycar said:
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?
Click to expand...
Click to collapse
... Does it show rest of the files ...

Devilish_Angel said:
... Does it show rest of the files ...
Click to expand...
Click to collapse
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.

dtracycar said:
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.
Click to expand...
Click to collapse
... you might want to install TWRP 2.6.3.0.
Get it from here http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
this is the .img file so you ought to flash it from fastboot ...

branded said:
Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt
Click to expand...
Click to collapse
4.3 was your problem. You needed to use a different SuperSU and this is the case with anyone else who wants to root 4.3 or 4.4. I believe I used SuperSU v1.65. Glad you got it working!

mHamers since
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse

dtracycar said:
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse
... might be a bad SU file. download from here and flash from recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip ...
Click to expand...
Click to collapse

Devilish_Angel said:
dtracycar said:
... might be a bad SU file. download from here and flash from recovery
Well, I finally got it to work! Thank you for all your help! Now if I could only get wifi hotspot or foxfi to work. Thats the whole reason I rooted in the first place!
Click to expand...
Click to collapse
Click to expand...
Click to collapse