A few days ago I rooted my Bionic with psouza4 one click root and it worked perfect the first time I tried it. After I rooted I started noticing a few issues (Every time i opened an app requiring SuperUser permissions, it would constantly tell me it was being granted SuperUser permissions, could not boot into recovery either with the bootstrap app or from ROM Manager)
Figuring it might've been because of a bad root, I unrooted and tried rooting again. Now every time I try to root again, it gets to the third step and I get an error saying "we have root but could not push su. Try unrooting first, then running root."
I've unrooted and tried rooting 4 times now and it keeps failing and giving me this error.
I was only rooted for a few days so I was stock rooted with all bloat and nothing frozen so I never deleted or modified anything except for gaining root the first time.
Thank you in advance for your help
Dhacker's one-click restore. In development.
Sent from my DROID BIONIC using xda premium
Thanks, gonna go give it a shot.
Related
So I rooted my new Captivate (Rogers, I896) using this method
http://forum.xda-developers.com/showthread.php?t=827544
Everything worked perfectly, and the Superuser Access icon appeared in the app drawer. Unfortunately, no programs can gain superuser access. ROM Manager keeps giving me an error when I try to do anything (flash recovery, fix permissions etc) and doesn't show up on the list of 'Superuser' programs. I haven't gotten any prompts to allow access, either, so I don't know what's wrong. Any ideas, XDA?
It's quite possible that your root is incomplete, that happens sometimes with some rooting methods. You should try re-rooting. That thread lists at least three rooting methods, which one did you use?
Sent from my SAMSUNG-SGH-I896 using XDA App
I rooted using the method from the link in my first post. You were right, though - it was incomplete. I re-rooted with z4 and it worked perfectly -- enjoying AXURA and the lack of TouchWiz =D
Hey guys, I'm definitely a novice in these matters, but this is the first time I've had a problem so I'd appreciate some help.
While my Droid was on FRG83D I rooted with SuperOneClick using rageagainstthecage. I had to install PdaNet to get it to work, but it did work for me. This morning I got the OTA update for FRG83G and downloaded and installed it just a few minutes ago.
I didn't unroot my phone before I did this.
Afterwards the two apps I use that require su won't work (Barnacle and ROM Manager for backups, I don't have a custom ROM flashed to my phone yet) so I ran SuperOneClick again, ran root using psneuter. Still didn't work so I unrooted using psneuter. Then I realized that I should probably unroot using rageagainstthecage and did so. So at this point (theoretically) my phone was unrooted. Then I ran root with rageagainstthecage again and my two apps still won't work.
Every time I rooted or unrooted using either method SuperOneClick worked seemingly perfectly.
So here's my question: What did I do wrong? And just as importantly, how do I fix it so I can have root access on my phone again?
*Edit* Well this is pretty embarrassing. I just rebooted my phone and tried Barnacle again, and the su acceptance box came up like it's supposed to. I suppose I'm back to being rooted. I think I'll leave this here, and if anyone has any constructive criticism of my (lack of) process or comments about why things acted the way they did and why it works now I'd like to hear it. I'm all about learning more about all of this.
Okay guys my friend updated and he still has super-user, but it does not work.
I ran superoneclick newest version, it said it was rooted. I rebooted manually and his phone was stuck at the Droid anamation screen,
I finally figured out our to factory restore Power+x, then at the ! Trianlge with phone; hit power up and camera.
I restored it, rebooted and he still has super-user. So i tested it with root check and titanium back-up, did not work. I unroot with superoneclick and it does nothing.
So I came here and started reading I found out that 1.7 is needed to root. My question is will it still root even though super-user is already installed, but not working?
Verizon Droid A855
2.2.3
Buildnumber is : frk76
Baseband is c_01.43.01p
Thanks for any help.
No one has done this or has knowledge?
sent from my ice cream sandwhich MT4GS
I have had the same problem. Even superuser was denied superuser permission. Go figure. I am eager to hear if anyone knows how to get back to root.
keeganob1 said:
I have had the same problem. Even superuser was denied superuser permission. Go figure. I am eager to hear if anyone knows how to get back to root.
Click to expand...
Click to collapse
Have you tried superoneclick 1.7 rageinthecage exploit? I read it will root the firmware. What I have not read is people who had root lost it and re-rooted. I know someone here has to know, this I would think It would be a common issue with the og droids.
For some reason I can't find anything on it.
sent from my ice cream sandwhich MT4GS
A while back I had a update and when I updated it removed my root, but I still had superuser. I did a system restore and rerooted fine. Recently the Milestone X got a gingerbread update and I wasn't updating because I was hearing that a lot of people were having problems with their rooting and wireless tether afterwards. A couple nights ago I accidentally hit the update button and now system restore doesn't bring it back to the original OS. Looking into this currently. I will post again if I find a way to get this working.
There is a simple, one-click re-root app from the market that lets you quickly re-root after the OTA update. Of course, you have to be rooted first.
Before doing your OTA, download the free app "ota rootkeeper" from the market. Run this BEFORE the OTA, and it'll stash away a copy of all your root stuff. Then, after the OTA, go back to the app, and with one click, re-rooted! Lots of phones it won't work on, but it DOES work on the Droid 3!
Worked perfectly for me, re-rooting after the OTA. Neall
Just wanted to confirm for other users that if you updated to frk76 firmware. On 2.2..3 and were rooted. Supeoneclick. 1.7 will. Re root even if superuser is showing up.
Download 1.7 superoneclick
Run rageagaintsthecage exploit.
If it locks up, turn usb debugging off then back on. ( ie have the window open). I had to do it.
Re boot and good to go.
Sent from my ICS Splashed using Tapatalk
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
furlessxp said:
So I just rooted my Motorola Droid since my contract expired with Verizon. I'm using this phone as practice so I'm not afraid to brick it. After using the superoneclick method to root the phone, it installs superuser fine, and I can access the app. I installed ROM manager for obvious reasons and every time I try to flash a recovery, it freezes at the point where the app is supposed to ask me for superuser permissions. I tried using titanium backup and it is not asking for permissions either. I then go into the superuser app and did the "Tap to check for updates" under the Su binary v3.0.3 label. The update fails every time on the "Gaining root access..." step. I tried unrooting and rerooting and everything. I went into the superuser settings and set the automatic response to "allow" and am still getting nothing. I have also force closed superuser, and then cleared all the data before restarting.
Am I just missing something important? Or am I just unlucky to the point where nothing I ever try in regards to rooting works the way it is supposed to?
Click to expand...
Click to collapse
Have you tried updating the superuser app itself? not only the su binary
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app