So i am a little confused.
Back on Gingerbread i had my phone rooted and was just using adblock and Titanium backup on the stock rom. SU worked fine and everytime i booted up TB or Adblock it always showed up with the "application has been granted SU access" or whatever.
When i updated my phone to stock ICS through Kies, i couldnt use TiTbackup anymore so i re-rooted my phone using some program i saw on here (it was not ODIN).
After that my Titanium Backup worked fine again as well as Adblock.
Now i am trying to jump into CM10/AOKP but i cannot seem to flash TWRP and superuser wont update (its telling me i dont have root access).
What should i do? Just try to re-root via Odin and flash the newest version of Superuser? Or will that screw things up considering i have SU already installed.
Thanks for any help.
Did you restore using CWM?
idbl_fanatic said:
Did you restore using CWM?
Click to expand...
Click to collapse
Restore to what?
Khameleon said:
Restore to what?
Click to expand...
Click to collapse
Restore your ROM
idbl_fanatic said:
Restore your ROM
Click to expand...
Click to collapse
Why? Its the factory Rom on right now, i havent changed anything on it.
Just got Root Checker and now its saying i dont have root access.... le sigh.
I can still get into CWM, is there a way to flash something to give me root access?
Khameleon said:
Why? Its the factory Rom on right now, i havent changed anything on it.
Just got Root Checker and now its saying i dont have root access.... le sigh.
I can still get into CWM, is there a way to flash something to give me root access?
Click to expand...
Click to collapse
The reason I asked, was because CWM has issues with setting the correct access, and if you restore, you lose root.
idbl_fanatic said:
The reason I asked, was because CWM has issues with setting the correct access, and if you restore, you lose root.
Click to expand...
Click to collapse
Should i just try reflashing SU? Or would that brick or ruin my phone?
I think the reason Titanium backup and Adblock are still working are because that is what i was using before i went to ICS and it maintained SU permissions.
Think SU might have just gotten corrupted?
Related
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
sblantipodi said:
As title.
I always rooted my gnex using an unsecure boot image.
Now I can boot with an unsecure boot image, I can push/chmod su, superuser and daemonsu using adb but than what should I do?
What should I do to root the phone?
Thanks.
Click to expand...
Click to collapse
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
mwalt2 said:
You can either flash the SuperSU .zip by Chainfire in a custom recovery or you can take the .zip apart and do it manually. Push all of the files in the .zip to the corresponding locations on your phone and look at the updater-script to see if you need to do any other commands. Root in 4.3 is different and Chainfire's method basically uses a script to enable it at every boot. I have not read about any other superusers working for 4.3, though I could have missed it.
Click to expand...
Click to collapse
is there a way to undo this process once done?
sblantipodi said:
is there a way to undo this process once done?
Click to expand...
Click to collapse
Naturally, backtrack your steps.
beekay201 said:
Naturally, backtrack your steps.
Click to expand...
Click to collapse
Can I safely remove all the files copied from the zip ?
sblantipodi said:
Can I safely remove all the files copied from the zip ?
Click to expand...
Click to collapse
Yes.. Restoring whatever in the process..if you modified anything that was there already.
Galaxy Nexus 4.3 NO ROOT w/ SuperSU_1.51.zip
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
innerspace said:
Ok XDA - you're my only hope. I've completely lost root after flashing the last two PA releases. I just flashed the most recent (dirty), flashed GApps, rebooted, Flashed SuperSU_1.51/zip, Wiped Dalvik/cache in TWRP, rebooted, SuperSU says no binary installed, please manually root. Losing my mind here, need to get rooted again, could someone lend me some backup?
Click to expand...
Click to collapse
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
download the most current supersu.zip and flash it in recovery.
if you're using a toolkit (i bet you are) STOP IT.
Zepius said:
download the most current supersu.zip and flash it in recovery.
about 2 minutes prior to your reply, I updated the "Toolkit" along with all the other items (supersu, img, etc..)
And after that, my device is rooted again.
Although, the main reason I started all of this was to update my device's build further, but it seems the OTA update is now gone... I'll have to wait for it appear again and see how it goes...
Zepius said:
I'll keep that in mind...
if you're using a toolkit (i bet you are) STOP IT.
Click to expand...
Click to collapse
Thanks for the reply!
Much appreciated!
Click to expand...
Click to collapse
AMKhatri said:
Did you manage to solve this problem?
I've got the same problem now...(There is no SU Library installed... This is a problem!)
Previously I had root but SU Library wouldn't update, ChainFire told me to re-root which caused me to lose root completely, tried again to root, without any luck.
Stuck without Root
Click to expand...
Click to collapse
I did, though I'm fuzzy on how exactly, and no, no toolkits here. IIRC I ended up wiping, updating recovery, and then manually flashing, but I had to do it multiple times to get root to stick. Sorry I don't have any better info to provide, glad to hear a) I wasn't the only one who experienced this problem, and b) you got your root back.
I have recently rooted my phone i think gone through all the steps on galaxys4root.com. When I was done I tried to update su binary and it said installation failed.then tried to go on titanium backup and it said rom is not rooted .ok i got su app to update but it now saying there is no su binary installed and super su cannot install it . This is a problem But the phone says it is rooted so do I need to re root the phone
Thanks for any help
willdoe said:
I have recently rooted my phone i think gone through all the steps on galaxys4root.com. When I was done I tried to update su binary and it said installation failed.then tried to go on titanium backup and it said rom is not rooted .ok i got su app to update but it now saying there is no su binary installed and super su cannot install it . This is a problem But the phone says it is rooted so do I need to re root the phone
Thanks for any help
Click to expand...
Click to collapse
I think the steps on galaxys4root.com may be outdated or used properly on an older version of Android. Try CF Auto-Root: http://forum.xda-developers.com/showthread.php?t=2294005
Vigz said:
I think the steps on galaxys4root.com may be outdated or used properly on an older version of Android. Try CF Auto-Root: http://forum.xda-developers.com/showthread.php?t=2294005
Click to expand...
Click to collapse
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
willdoe said:
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
Click to expand...
Click to collapse
No. However, CF Auto-Root will flash stock recovery. If you want to install custom ROMs, simply re-flash CWM Recovery.
willdoe said:
do i have to unroot the phone first or anything i should do before cf auto root right now i have cwm recovery and super su down loaded on it
Click to expand...
Click to collapse
ok thanks a bunch one more question what steps should i follow to re-flash cwm recovery
willdoe said:
ok thanks a bunch one more question what steps should i follow to re-flash cwm recovery
Click to expand...
Click to collapse
I am guessing here but please correct me if i am wrong cf auto root gives me root then i should follow galaxy s4root.com instrutions on how to install cwm recovery
willdoe said:
I am guessing here but please correct me if i am wrong cf auto root gives me root then i should follow galaxy s4root.com instrutions on how to install cwm recovery
Click to expand...
Click to collapse
Once you are rooted you have to choose which recovery you want. Twrp is the most compatible with most Roms out there. To get cwm you need to install ROM manager from the market. The option to flash recovery will be inside. If you want twrp download goo manager and the option to flash will also be in the app. Good luck!
Sent from my SGH-M919 using xda app-developers app
mrzhadow said:
Once you are rooted you have to choose which recovery you want. Twrp is the most compatible with most Roms out there. To get cwm you need to install ROM manager from the market. The option to flash recovery will be inside. If you want twrp download goo manager and the option to flash will also be in the app. Good luck!
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can also get either TWRP or CWM as a Tar file that can be flashed in Odin.
You can also download the .img files and flash either with Flashify.
There are a lot of ways to flash recoveries. Each with specific advantages for specific situations.
Ok thanks a bunch to all of ya in my situation I am just trying to get root on my phone it is a t-mobile S4 its running 4.2.2 it seemed easy enough on galaxyS4root.com I think I guessed wrong so I will definitely try cf auto root though I am not done trying yet so again thanks for your time
willdoe said:
Ok thanks a bunch to all of ya in my situation I am just trying to get root on my phone it is a t-mobile S4 its running 4.2.2 it seemed easy enough on galaxyS4root.com I think I guessed wrong so I will definitely try cf auto root though I am not done trying yet so again thanks for your time
Click to expand...
Click to collapse
That website you tried seems to have borked you all up. Cut your losses with methods from there and start over with the CF Auto Root method. it will work perfectly in 30 seconds.
Ya I was pretty aggravated lastnight but got up this morning used cf autoroot and so far so good super su has binary installed titanum back has root its going good so far thanks again for yalls help
So all of sudden, my rooted S3 is not rooted anymore.
I wanted to use Titanium Backup and it says
"Sorry, I could not acquire root privileges. This application will *not* work! Pleasre verify that your ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command."
and then I tried my other root applications such as Greenify, App Ops and they are all saying my phone isn't rooted anymore.
I don't understand, I never upgraded my phone after I rooted and I never flashed a different rom and kept the Touchwiz Rom.
I used this guide to root my phone originally:
http://forum.xda-developers.com/showthread.php?t=1771687
My phone is running 4.3 Android (Same Version I used when Rooted in the first place)
Baseband Version: T999UVUEMJC
Please let me know what to do
check if supersu is working properly.
Cronoss said:
check if supersu is working properly.
Click to expand...
Click to collapse
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
magic132131 said:
It isn't.
The following message pops up:
"There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
Click to expand...
Click to collapse
My suggestion would be to back everything up and re flash root66.
Cronoss said:
My suggestion would be to back everything up and re flash root66.
Click to expand...
Click to collapse
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
magic132131 said:
Would I lose all my data?
In terms of re flash root66, that means simply using Odin and re-rooting my phone like I do the first time right? Would it be the same instructions too?
Click to expand...
Click to collapse
I'm not sure if you are going to lose your data.. so that's why I said to back everything up, just in case.
And yes.. same method as before from that post.
Befoe you flash again. Try uninstalling then installing supersu again
SoulEater- said:
Befoe you flash again. Try uninstalling then installing supersu again
Click to expand...
Click to collapse
I can't uninstall supersu as it gives me no option to do so. I can only uninstall all updates that were applied but not complete remove and then install it.
I had this happen on my Tmobile Galaxy S3.
I read somewhere else on XDA that you just had to install the latest SuperSU, in zip form, from recovery mode.
I havent posted enough here to be able to post a link, but you can find it on chainfires website.
Then reboot and it should work.
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
The Cheese Deity said:
I have searched the forums for my device, and other people's posts trying to find a way to root my device. Towelroot did not work for me. I read that i could install Philz touch recovery and root with that, but i cannot find the version of that for my phone. If somebody could point me in the direction of a method to root my phone, i would very much appreciate it
Click to expand...
Click to collapse
You could download GooManager (or Flashify) off the Play Store, install custom recovery (TWRP) and root. It will install the one for your phone automatically.
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
DocHoliday77 said:
You need root to use GooManager.
Im curious, what happened with Towelroot? I cant see any reason it wouldnt work. Can you tell me the steps you used?
Click to expand...
Click to collapse
I downloaded the towelroot apk, installed it and clicked "make it rain" and the app said i should have root. I downloaded root checker and it says i do not have root access.
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
DocHoliday77 said:
After running Towelroot You have to install SuperSU from the Play Store, then open the app and let it update the binary and disable Knox.
If SuperSU hangs, reboot and it'll work on the second try.
Click to expand...
Click to collapse
I had tried CF-Auto-Root before towelroot, and it seems to have either partially installed SuperSU, or SuperSU just doesn't like my phone. It shows up in my app list as "eu.chainfire.supersu.MainActi" and force closes when i try to open it. I cannot uninstall it. (i should have mentioned this in my OP maybe)
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
DocHoliday77 said:
Oh ok. That makes more sense to me for why Towelroot didn't work then. Probably the easiest fix would be to reflash the firmware with Odin, then try Towelroot first. Since you dont have root now, its going to make fixing the problem any other way near impossible.......actually, now that I said that, you could flash twrp recovery, then use its file manager to manually delete any traces of the failed root.
Still, I think the firmware flash is an easier and safer option. But its up to you how you want to proceed.
Click to expand...
Click to collapse
I successfully flashed TWRP, exactly what files should i delete?
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
DocHoliday77 said:
Check the cf autoroot thread to be sure, but probably the su binary, install-recovery.sh, daemonsu, etc.
Click to expand...
Click to collapse
The recovery file manager does not see a lot of the files on my phone. It does see the SuperSU folder, but even if i delete or rename it, it just fixes itself upon reboot. I'm thinking of flashing the 4.4.2 firmware through odin, is a factory reset absolutely necessary to do that?
I flashed the firmware, ran towelroot, installed SuperSU, installed the binary, disabled Knox, and i am now running a rooted device!
Thank you very much DocHoliday77 for all of your help, i greatly appreciate it.
Which firmware did you reflash? Stock 4.4.2??
I cannot find towelroot on the app store. Are there any suggestions on what to do without towelroot
I have the Fire TV 1 and had TWRP and Pre Rooted 5.2.4.1 FW installed. Yesterday during a restart the FTV started boot looping. I could see the option for TWRP recovery though.
I booted into TWRP recovery and reflashed the Pre Rooted 5..2.4.1. The FTV now booted but I have lost both TWRP and SuperSu as well. When I type su into an adb shell I got su not found?
Updated were blocked through the device as well.
Anyone else experience this? What can I do now to get TWRP installed and root established?
Help anyone?
Bump ^
Did you do any factory reset or something? I don't know how you could have lost SU and twrp when installing the prerooted roms. All apps say no root? i wonder if you did a factory reset if it would help or re-installed whatever version you were on when you rooted? I'm a novice so don't blame me for bricking! lol
Michajin said:
Did you do any factory reset or something? I don't know how you could have lost SU and twrp when installing the prerooted roms. All apps say no root? i wonder if you did a factory reset if it would help or re-installed whatever version you were on when you rooted? I'm a novice so don't blame me for bricking! lol
Click to expand...
Click to collapse
Thats why I am stumped! I did not do any factory resets or wipes. I simply selected rbox's rooted 5.2.4.1 ROM, installed and rebooted. Now I dont see the initial boot screen when the fire tv restarts. Just the regular animation.
is your bootloader unlocked? I don't have any rooted FTV1's. I think you could reflash the recovery if your unlocked....
Michajin said:
is your bootloader unlocked? I don't have any rooted FTV1's. I think you could reflash the recovery if your unlocked....
Click to expand...
Click to collapse
Unfortunately I don't think my bootloader is unlocked
pspTP said:
Unfortunately I don't think my bootloader is unlocked
Click to expand...
Click to collapse
all i can think of is try to root with a USB A to A cable, i think that was possible. From appstarter do you see anything non-stock?
Michajin said:
all i can think of is try to root with a USB A to A cable, i think that was possible. From appstarter do you see anything non-stock?
Click to expand...
Click to collapse
Since I had installed rBox's 5.2.4.1 rooted ROM when I had root, thats what I am on now except without root now. I had blocked updates on the device so thankfully that is still in place. And according to aftvnews, this version cannot be rooted.
I do have a bunch of non stock apps that I had installed that are still present on the device.
pspTP said:
Since I had installed rBox's 5.2.4.1 rooted ROM when I had root, thats what I am on now except without root now. I had blocked updates on the device so thankfully that is still in place. And according to aftvnews, this version cannot be rooted.
I do have a bunch of non stock apps that I had installed that are still present on the device.
Click to expand...
Click to collapse
you ever try to sideload SuperSU? Or run a root app that requests access and seen if it just says access denied? Just throwing out ideas to try, I didn't see anyone else trying to help. If you flashed pre-rooted version then i would think some of the exploits are still in your system.
Michajin said:
you ever try to sideload SuperSU? Or run a root app that requests access and seen if it just says access denied? Just throwing out ideas to try, I didn't see anyone else trying to help. If you flashed pre-rooted version then i would think some of the exploits are still in your system.
Click to expand...
Click to collapse
I downloaded the latest supersu and sideloaded it. When I run it there is simply a blank screen and back to where I was. Nothing happens.
Now in appstarter I can see two versions of su, one from before and the latest one. Running either does not do anything.
I had Adaway installed before as well. If I run it now, it just comes back with not a rooted device
Do you still have TWRP? You should be able to flash SuperSU that way.
Sizzlechest said:
Do you still have TWRP? You should be able to flash SuperSU that way.
Click to expand...
Click to collapse
No thats the kicker, I lost both TWRP and root.
It is a long shot, but you could try kingo root and king root, see if they can get root access. I know they dont work on a firetv stock for rooting, but something must have flashed wrong and maybe they can find a way into root.
Curious though, every time you have flashed the pre-rooted OS did you always disable the updates every time?
Michajin said:
It is a long shot, but you could try kingo root and king root, see if they can get root access. I know they dont work on a firetv stock for rooting, but something must have flashed wrong and maybe they can find a way into root.
Curious though, every time you have flashed the pre-rooted OS did you always disable the updates every time?
Click to expand...
Click to collapse
I believe the pre-rooted OS has that setting disabled in the first place.
pspTP said:
I believe the pre-rooted OS has that setting disabled in the first place.
Click to expand...
Click to collapse
AFTVnews always recommends disabling updates to be sure. It almost seems like you got updated. Try running Kingroot. Worst case it fails and you are still where you are at...