After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
did not have a problem with ryans one touch lag fix that also takes care of root
I'm having the same problem. Also new to this so I'm sure it's going to be something simple. But it's dricing me crazy. I'm sooo close. Anyone with advice it would be much appreciated.
sorry I forgot to say that I have the Epic 4g
aaconteh said:
After I installed the firmware update, via Odin, i can't seem to re-root my phone. I re-installed the update, renamed the zip, flashed it and no smoke. I'm kind of new with all of this so what do i do to access root at this point?
Also, I re-downloaded the superuser app from the market and it stated that there was a new version available. The app states" an error occurred and su was not updated. A zip(su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary. " I tried to flash this recieved an error message saying that the zip was "(bad)". What do I do?
Click to expand...
Click to collapse
The Superuser app from the market isn't going to give you superuser privileges without the phone being rooted. That's why you are rooting the phone in the first place.
As I've made a habit of experimenting with every ROM known to man I've gotten this down to a routine when it comes to flashing and re-rooting. And a big part of my routine is using TGA_Gunnman's handy One Click ROOT Windows application (also a mac version available in the same thread)...
http://forum.xda-developers.com/showthread.php?t=739300
Just use it and follow the instruction. Biggest thing is to make sure the phone has USB Debugging enabled and that the internal and external SD's are NOT MOUNTED. Just click the ROOT ME button, look in the shell window to see that the update.zip has been pushed successfully, use the vol rocker keys to select REINSTALL PACKAGES, and reboot.
It's never failed for me so far, and I've re-rooted dozens of times now.
Best of luck!
DemDonkies said:
sorry I forgot to say that I have the Epic 4g
Click to expand...
Click to collapse
The root method for the Epic4g is a tad different...and located in another forum...
http://forum.xda-developers.com/showthread.php?t=770388
Im experiancing this problem for a long time now... I have a galaxy s phone with darky's ROM v10.0 RC final. evidently it is rooted but some apps don't recognized it as a rooted phone. first, when i ran the superuser it fails and said com.noshufou.android.su is failed to work...and then theres a notificaTION that su binary is outdated but i tried to update it a million times but always failing, tried this su update fixer but still negative results. downloaded busybox installers the first one also failed to install busybox saying the directory where i want to put it has a problem, tried to put it to other option directory but still negative. the other busybox installer says that my phone is not rooted. how come this happens when titanium backup recognized my rooted phone. im running out of bright ideas here (if what Ive done can be classified as a bright ones hahaha) please someone help me...
Jayfunk said:
Im experiancing this problem for a long time now... I have a galaxy s phone with darky's ROM v10.0 RC final. evidently it is rooted but some apps don't recognized it as a rooted phone. first, when i ran the superuser it fails and said com.noshufou.android.su is failed to work...and then theres a notificaTION that su binary is outdated but i tried to update it a million times but always failing, tried this su update fixer but still negative results. downloaded busybox installers the first one also failed to install busybox saying the directory where i want to put it has a problem, tried to put it to other option directory but still negative. the other busybox installer says that my phone is not rooted. how come this happens when titanium backup recognized my rooted phone. im running out of bright ideas here (if what Ive done can be classified as a bright ones hahaha) please someone help me...
Click to expand...
Click to collapse
Try to update your busybox...
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
twomoses said:
So, after learning that Motorola was not going to give us a software update for the Atrix 4G, I decided to take a chance and unlock the bootloader and flash a custom rom. I flashed CyanogenMod 7 Olympus (cm-7-20120923-NIGHTLY-olympus) and I love it! I made a backup of the stock rom and then a backup of CM7 after I had it set up the way I like it for the most part.
My only problem: I lose root access randomly... without rebooting... without doing anything! SU is there, and the superuser apk is there, and they come up as granting superuser permission, but the apps say they don't have access. Even trying to update the binary says "failed" when gaining root access.
I've been scouring forums and the net looking for similar problems. Rebooting doesn't fix it. I've tried downloading and flashing SU 3.1.3 from recovery (wipe cache & dalvik cache, then install from zip), and that didn't work. I then tried the same for 3.2-RC3, and no luck there. I've ran Fix Permissions just to try, and that did not work either. Somewhere, someone posted to reflash the ROM. Instead, I just restored a backup, and it comes back for a few days... then it stops working again.
Any suggestions on how to fix this or what could cause it? I don't mind restoring the backup again, but I'd like to keep it from happening if at all possible.
Click to expand...
Click to collapse
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
upndwn4par said:
Try going in to Manage Applications and clear su data. If that doesn't work go to the Play Store and Install Superuser Update Fixer.
Click to expand...
Click to collapse
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
twomoses said:
Thanks for the quick reply. I cleared the cache for Superuser (couldn't believe I didn't think to do that in the first place), and now it will not prompt to grant or deny. I try to update the binary, and it stops at "Gaining root access..." and doesn't show okay or failed. I tried to run the Superuser Update Fixer, and it says that the signatures are okay. When I try to force it, it does the exact same thing as Superuser: it hangs at "Gaining root access..."
It may be worth noting that I have to force-close Superuser the first time I open it after clearing cache. After that, it opens but only does the above mentioned.
Click to expand...
Click to collapse
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
upndwn4par said:
Open a terminal emulator and type su and hit enter. If you don't see #, you are not properly rooted.
Click to expand...
Click to collapse
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
twomoses said:
Nothing happens in terminal emulator.
Now my question is, (and forgive my n00bness) since CM7 came rooted, do I follow the normal steps to re-root the phone through adb? I've never seen how to root a custom rom, but that may be because the process is exactly the same.
Click to expand...
Click to collapse
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
I don't know the answer to your question since most users root, unlock, then flash a ROM. If it were me, I would try to root as if it were GB 236.
upndwn4par said:
Nothing happens? No error ("not found" or "permission denied" or something like that)?
Go to the Play Store and download Root Checker, and check for root with that also.
Click to expand...
Click to collapse
That is correct. I ended up having to kill the terminal emulator too. It just sits there with nothing displaying.
I ran root checker, and all I get is the loading circle in the middle that says "Please wait for Root Check to complete. System appears to be running very slow." Nothing else was running slow, so I rebooted my phone again.
I don't know what changed, but now I have root again! Many thanks upndwn4par!
My guess is clearing data in Manage Applications did the trick. Anyway, glad it is working!
Another method for checking if you are rooted properly.
EDIT: nevermind, now I see it's been discussed already. :stupid:
Off topic: I seriously want to borrow your signatures tho!
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
USB Debugging stays on usually because I don't connect my phone to a computer I don't know.
When this started, I was still getting the toast messages saying access granted, but it wasn't actually working. Somewhere along the line of steps it started working again tho.
twomoses said:
Off topic: I seriously want to borrow your signatures tho!
Click to expand...
Click to collapse
Absolutely!
upndwn4par said:
Absolutely!
Click to expand...
Click to collapse
Done!
Solved: This fixed my problem!
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
So, props to you Sabbelknoken! I suddenly lost root again the same way I had before. I came back through this thread to revisit my steps, and I found that my USB Debugging was off. (I think I turned it off so one of my computers would stop asking me for the drivers. Not important.) I turned it on and it immediately began working!
Just wanted to concur...
Thanks to Sabbelknoken!! I had this same problem with my Droid Charge running Tweaked 3.0. Nothing was getting root and everything was hanging on "Gaining root access..." I tried SuperSU, re-installing Titanium Backup, Superuser, SuperSU, Superuser Update Fixer, Root checker, I cleared data, rebooted several times...over and over.
Then sure enough, my dang "USB Debugging" was not checked. Checked it, and now I'm happily rooting again. *whew* Thought I was going to have to re-Odin my ROM. Ick.
Thank again everyone!
su losing root usb debug etc
I too get su issues from time to time. mostly with stock roms when i flash a fruitcake or gingerbread. and recently one of the leak roms. just type d su in terminal emulator an got $ instead of #. I hope that means im properly rooted . I have a couple of one click root apps on my computers just incase i need to reroot. one is superoneclick 2.33 shortfuse and the other is motofail. then i make sure to install busybox and upate the binary. i also have su update fixer, superuser elite, and supersu. as well as rootchecker.
two thing I did not know were that 1. usb debugging is not just for transferring files or connecting to the computer. I used to turn it off sometimes and then wonder why superuser had problems. 2. how to see you are rooted by typing su in terminal.
From what i understand the one click methods are not ideal as they do not always work. but I usually try them first . If they are outated and dont work i end up rooting by command prompt. some times it woul take me cloose to an hour trying different things. never knew it was usb debugging turned off that causes most root failures. Did some reading and realized that if i allow su permission for terminal emulator, then type su again i get#. good to know.
activate USB debugging
Sabbelknoken said:
have you disabled debugging in developement settings? if you do so, SU does not work any more, or the be more precisely: You won't be able to see the "Allow"-dialog...
Click to expand...
Click to collapse
Thanks for that simple tip. I was having the same problem, the "Allow" dialog didn't appear for any application request and Root Checker was only saying: "Device seems to be running really slow"
I was 2 or 3 days looking for the solution to this problem, because it is my first time rooting and I can't believe something as simple as activating USB debugging is not really explained in the rooting guide I used.
I hope that now Titanium and ROM Toolbox Pro work properly.
Hey guys so I ran into anther problem.A while ago I posted on what next for my p769, I have a rooted v10g ICS locked bootloader.I cant do the OTA update because Ive modified system apps and rom settings. I followed the method of flashing a JB Backup with CWM from this link that was provided: http://forum.xda-developers.com/showthread.php?p=37666447
So then I didnt have CWM installed so I proceeded to install cwm for my phone using this link http://forum.xda-developers.com/showthread.php?p=36620368
As for that my results were a little troubling The flashing led lights when I turn on my phone dont blink anymore and when SU grants permissions it has started to loop it continuously grants permissions to apps that SU just gave permissions to.And on top of that the CWM installation was supposedly installed but I cant even boot to CWM
Hope I can get some help on this one .
Andrusio said:
Hey guys so I ran into anther problem.A while ago I posted on what next for my p769, I have a rooted v10g ICS locked bootloader.I cant do the OTA update because Ive modified system apps and rom settings. I followed the method of flashing a JB Backup with CWM from this link that was provided: http://forum.xda-developers.com/showthread.php?p=37666447
So then I didnt have CWM installed so I proceeded to install cwm for my phone using this link http://forum.xda-developers.com/showthread.php?p=36620368
As for that my results were a little troubling The flashing led lights when I turn on my phone dont blink anymore and when SU grants permissions it has started to loop it continuously grants permissions to apps that SU just gave permissions to.And on top of that the CWM installation was supposedly installed but I cant even boot to CWM
Hope I can get some help on this one .
Click to expand...
Click to collapse
So a little add on to that I think I jacked up my phone because now it wont connect to wi fi networks and it seems SU gives access to apps but doesn't really give them root access ....-_- I think the worst part about this is I cant restore to an old back up because I was trying to install CWM so I could make backups .
Andrusio said:
So a little add on to that I think I jacked up my phone because now it wont connect to wi fi networks and it seems SU gives access to apps but doesn't really give them root access ....-_- I think the worst part about this is I cant restore to an old back up because I was trying to install CWM so I could make backups .
Click to expand...
Click to collapse
Please make sure that busybox is properly installed on your phone.
artit said:
Please make sure that busybox is properly installed on your phone.
Click to expand...
Click to collapse
I have heard it has to be a specific busybox ..the robert one I assume ? What is the way to properly install busy box ,I installed it prior to CWM installation.Now my phone is messed up it wont even connect to WI-Fi
Andrusio said:
I have heard it has to be a specific busybox ..the robert one I assume ? What is the way to properly install busy box ,I installed it prior to CWM installation.Now my phone is messed up it wont even connect to WI-Fi
Click to expand...
Click to collapse
I have used both Stephen and Robert version. Just install the one your prefer. For wifi issue, it work before you mess up your phone? Try to make CWM work and restore a good CWM backup.
artit said:
I have used both Stephen and Robert version. Just install the one your prefer. For wifi issue, it work before you mess up your phone? Try to make CWM work and restore a good CWM backup.
Click to expand...
Click to collapse
So for the Wi-Fi it did indeed work before The CWM issue ..in fact it worked perfectly I dont know what CWM did to my phone
You have to do a hard reset to fix the problem. Then start over
LG-P769 rooted, debloated, over clocked, under volted, and linked2sd. 'Tis the season to give thanks so hit the button already!
(I cant post to the original thread, but im hoping someone here can help me please?)
Ive rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.
But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.
Can anyone suggest what is the easiest way to get round this, or even why it's happening? And why is the later version of SuperSU disappearing on reboot?
non persistent SU after rooting Android 4.3 - solved
OK, so Im still unsure how I ended up successfully rooted ,but then reverting back to a non-working or incompatible SU version on reboot (presumably the version installed via cf-root?). It's news to me that an app installed via standard means can be overridden for any reason on reboot. One day someone might explain that or tell me the appropriate phrase to use for my friend google so he can explain it to me.
So what I was then trying to do was install a custom recovery so I could flash the latest SU, as per OP. Try as I might I cant. Even removing the battery once TWRP has been transferred using Odin the standard recovery still prevails. So that one is still unresolved.
But in the meantime, as with most well written apps, the answer is within SU itself. Going into Options in the Su installed via the standard app installer, I selected the option to install that SU as a binary. And it worked, so now SU persists across reboots.
Just in case someone else has the same issue, although judging by all the replies I suspect not (or maybe everyone else is able to post to the original thread, although I dont see this exact problem or solutio there).
If it didnt help anyone, sorry for wasting your time!
Hi,
I have the same problem : my root is lost after each reboot.
I must uninstall SuperSU, then update SuperSU end reboot to have the root again.
Could you give me your solution with simple words because I don't understand what you posted befort. Sorry for my bad english ...
Thanks.