I installed cm 10.2 ROM on my RAZR and a few days later installed jellywiz rls7. Now that I have jellywiz it seems like supersu doe not have any root permissions, no root apps work, and when I try to update the super binary it says installation failed, when I install update through recovery it gives me an error saying status 6. Can someone help me out correcting this problem? I've been googling this for hours, nothing works.
Thanks in advance.
I've never used Jellywiz, but is Superuser built in under your settings, or is it a standalone program? I've had poor luck with SuperSU, but superuser is built in to CM10 and AOKP roms, and has never missed a beat. Have you tried uninstalling, boot to recovery, wiping cache/dalvik, rebooting, and reinstalling?
EDIT
Did you follow the installation instructions on the forum to the T? It seems to be pretty particular as to the installation process, unlike others I have used.
You may need to turn on root from "developer options" in settings. I think most 4.3 roms require this. If you don't have that option in settings, I would re-read the install instructions or maybe ask in that thread.
Sent from my Optimus G using Xparent Red Tapatalk 2
LuckiestNut419 said:
I've never used Jellywiz, but is Superuser built in under your settings, or is it a standalone program? I've had poor luck with SuperSU, but superuser is built in to CM10 and AOKP roms, and has never missed a beat. Have you tried uninstalling, boot to recovery, wiping cache/dalvik, rebooting, and reinstalling?
EDIT
Did you follow the installation instructions on the forum to the T? It seems to be pretty particular as to the installation process, unlike others I have used.
Click to expand...
Click to collapse
Yeah I followed every instruction except the last 2, I could not find how to do it. Supersu is built in the ROM and when I try to uninstall it says uninstallation failed. When I update it through play store it still gives me the same errors and the pop up installation failed or uninstallation failed when I try to update or uninstall.
helioXverse said:
You may need to turn on root from "developer options" in settings. I think most 4.3 roms require this. If you don't have that option in settings, I would re-read the install instructions or maybe ask in that thread.
Sent from my Optimus G using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I am on 4.1.2 not 4.3 anymore.
I fixed it, I just rerooted and everything is fine now. I dlled a root checker in playstore and it said i wasnt rooted so i rerooted and it replaced supersu with superuser, everything is working fine. Thanks for the help anyways
Related
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.
Hi, I have a small problem.
Perhaps someone of you can help me. I asked this in the exploit thread as well as in the SuperSU thread but most I think just oversaw it.
I had CF-root on ICS stock before upgrading to JB. Sow since I got JB (4.1.1.), I'm on stock without root.
I tried the new exploit to root my phone.
I used the method to root and it worked but my SuperSU can't get updated or removed. I can just hit deinstall in the play store but it stays installed (like one of Samsungs own apps) and only option I have is to update it.
I did press on update but when I enter the app it still says binary needs to get updated. When I click yes to update it, it says install error. When I click to remove SuperSU in the app itself nothing happens.
SuperSU is at v0.99
What should I do? I assume I have to get rid of CMW and SuperSU from the old ICS root, but how without reflashing everything?
EDIT: I can't enable the exploit fixes either, when I click one of the checkboxes the SuperSU pop-up just flashes for a split second and is gone again, leaving the checkboxes unchecked.
Thanks in advance!
I have an SCH-i545 MDK build.
I am trying to upgrade from 4.2.2 to 4.3 and get root working.
On a 4.2.2 ROM, the motochopper exploit works perfectly. However, if I load a 4.3 ROM and follow the same method, when I flash the kernel to the pre-release kernel, the phone hangs and never boots. I've tried it several times with the same result, clearing cache before the process starts also seems to have no effect.
So what's the deal? Why is this happening? I know I have the right build. I went back to stock 4.2 and re-rooted using these files to make sure it would work at all. It worked perfectly. WTF? I flashed back to the stock kernel before installing the 4.3 ROM and trying again. Same deal, no booting after flashing the pre-release kernel.
Is there an updated root exploit for 4.3 that I missed?
I am following this guide: http://forum.xda-developers.com/showthread.php?t=2290798
This is my desired 4.3 ROM: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/582-jfltevzw
forkbomb said:
I have an SCH-i545 MDK build.
I am trying to upgrade from 4.2.2 to 4.3 and get root working.
On a 4.2.2 ROM, the motochopper exploit works perfectly. However, if I load a 4.3 ROM and follow the same method, when I flash the kernel to the pre-release kernel, the phone hangs and never boots. I've tried it several times with the same result, clearing cache before the process starts also seems to have no effect.
So what's the deal? Why is this happening? I know I have the right build. I went back to stock 4.2 and re-rooted using these files to make sure it would work at all. It worked perfectly. WTF? I flashed back to the stock kernel before installing the 4.3 ROM and trying again. Same deal, no booting after flashing the pre-release kernel.
Is there an updated root exploit for 4.3 that I missed?
I am following this guide: http://forum.xda-developers.com/showthread.php?t=2290798
This is my desired 4.3 ROM: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/582-jfltevzw
Click to expand...
Click to collapse
I've never seen a custom ROM that didn't come rooted. I suspect that your 4.3 ROM doesn't need to be exploited to be rooted.
k1mu said:
I've never seen a custom ROM that didn't come rooted. I suspect that your 4.3 ROM doesn't need to be exploited to be rooted.
Click to expand...
Click to collapse
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
forkbomb said:
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
Click to expand...
Click to collapse
I'd ask the developer of that ROM what's up.
forkbomb said:
Ok with the 4.3 ROM installed, it has SuperSU installed but it says my device is not rooted. SuperSU says it needs to update it's binaries.
I click install normal, it says failed. I click CWM, it never reboots. Rebooting into recovery doesn't continue the process.
Is this the ROM's fault? Should I just pick another 4.3 ROM?
Click to expand...
Click to collapse
You must go to setting, about phone, tap the build number repeatedly until developer options are granted.
Now go to settings, developer options, look for Root. Select it and choose "ADB & Apps"
dynospectrum said:
You must go to setting, about phone, tap the build number repeatedly until developer options are granted.
Now go to settings, developer options, look for Root. Select it and choose "ADB & Apps"
Click to expand...
Click to collapse
Oh wow, that was simple. Thank you.
Phone has been fine, rooted with cwm5.5. This is wifey phone so I keep messing with it at a minimum. At some point I noticed it no longer has root. It runs stock 4.1.2. With a couple of root apps - such as AdAway-which is no longer working and has error message "Either subinary could not be found or you did not allow root permissions for AdAway"
Superuser app has this error "There are currently no superuser app policies." then "Superuser binary must be updated" attempting to update results to error "There was an error installing superuser. "
I rooted the phone again with the same CWM ver. file. attempted to flash superuser but it errored and aborted installation. I rebooted and installed rom manager so that I could update CWM. That errored out as well. Root verifier confirms there's no root on the phone. I have installed busy box but it has the same error message no root access.
I thought to root with CWM ver 6.0.4.6 but installation aborted. I tried TWRP but it aborted as well. Only CWM 5.5 works which my normal routed is then to flash superuser, install rom manager and then have it update to CWM to ver 6.xx. But his time none of these is working. How do I regain root?
jayinc11 said:
Phone has been fine, rooted with cwm5.5. This is wifey phone so I keep messing with it at a minimum. At some point I noticed it no longer has root. It runs stock 4.1.2. With a couple of root apps - such as AdAway-which is no longer working and has error message "Either subinary could not be found or you did not allow root permissions for AdAway"
Superuser app has this error "There are currently no superuser app policies." then "Superuser binary must be updated" attempting to update results to error "There was an error installing superuser. "
I rooted the phone again with the same CWM ver. file. attempted to flash superuser but it errored and aborted installation. I rebooted and installed rom manager so that I could update CWM. That errored out as well. Root verifier confirms there's no root on the phone. I have installed busy box but it has the same error message no root access.
I thought to root with CWM ver 6.0.4.6 but installation aborted. I tried TWRP but it aborted as well. Only CWM 5.5 works which my normal routed is then to flash superuser, install rom manager and then have it update to CWM to ver 6.xx. But his time none of these is working. How do I regain root?
Click to expand...
Click to collapse
have you tried flashing another ROM? rumor has it that custom roms contain and are pre rooted.
captemo said:
have you tried flashing another ROM? rumor has it that custom roms contain and are pre rooted.
Click to expand...
Click to collapse
Initially I had actually, but camcorder issues, modems with sporty service ... we a deal breaker. Si I just restored it to stock with kies to avoid more lip. Only thing I did was root the stock so I could install a few apps such as AdAway. I don't plan to do stock on this unless I can get get rooted stock rom.
jayinc11 said:
Initially I had actually, but camcorder issues, modems with sporty service ... we a deal breaker. Si I just restored it to stock with kies to avoid more lip. Only thing I did was root the stock so I could install a few apps such as AdAway. I don't plan to do stock on this unless I can get get rooted stock rom.
Click to expand...
Click to collapse
When I rooted my phone I was wary of using methods that would have me going through either download mode or having to install a custom recovery (which eventually became pointless since I had to do both to flash roms anways lol) but at the beginning I was trying to use something simple.. while googling I stumbled upon this http://www.kingoapp.com/ and rooted from there.. it's like a one-click root kind of thing and seems to keep the root working regardless.. maybe you wanna check it out and see if it helps, in case you loose your root again. If you wanna run your phone stock but rooted, at least after doing the restoration via keys you'll keep the stock samsung recovery.
Hope it helps!
wavv.drama said:
When I rooted my phone I was wary of using methods that would have me going through either download mode or having to install a custom recovery (which eventually became pointless since I had to do both to flash roms anways lol) but at the beginning I was trying to use something simple.. while googling I stumbled upon this http://www.kingoapp.com/ and rooted from there.. it's like a one-click root kind of thing and seems to keep the root working regardless.. maybe you wanna check it out and see if it helps, in case you loose your root again. If you wanna run your phone stock but rooted, at least after doing the restoration via keys you'll keep the stock samsung recovery.
Hope it helps!
Click to expand...
Click to collapse
Thanx for that link/suggestion. I didn't see Note i717 listed under supported devices. Did you if this app supports rooting the i717?
jayinc11 said:
Thanx for that link/suggestion. I didn't see Note i717 listed under supported devices. Did you if this app supports rooting the i717?
Click to expand...
Click to collapse
I know, it doesn't show our device, but I kind of went with the home page "root all devices" statement they had and it worked perfectly fine. I did the same with my sister's Note 2 t0ltetmo which is in fact a canadian Videotron phone I gave her and worked fine too. I do not believe that that Note 2 is in the list either, but it still worked
wavv.drama said:
I know, it doesn't show our device, but I kind of went with the home page "root all devices" statement they had and it worked perfectly fine. I did the same with my sister's Note 2 t0ltetmo which is in fact a canadian Videotron phone I gave her and worked fine too. I do not believe that that Note 2 is in the list either, but it still worked
Click to expand...
Click to collapse
Hey it worked some - I decided to test it on my old Captivate. The only thing is it doesn't install CWM/TWRP or similar. So I cannot install a custom ROM. Is it not supposed to install a custom recovery? If not how do I do that having rooted with Kingoapp?
Thanx again for suggesting this app.
jayinc11 said:
Hey it worked some - I decided to test it on my old Captivate. The only thing is it doesn't install CWM/TWRP or similar. So I cannot install a custom ROM. Is it not supposed to install a custom recovery? If not how do I do that having rooted with Kingoapp?
Thanx again for suggesting this app.
Click to expand...
Click to collapse
My pleasure, and glad to hear it worked! And no, lol, sorry. The app only roots your phone, but it does not install a recovery. The good thing about it is that at least you can run stock and use any rooted apps, like I do with my Asus HD7 (for which, unfortunately I haven't found either a custom recovery or a custom ROM to flash, so I run it stock but mess around with root apps)
However..
I looked into this Galaxy Captive thread: http://forum.xda-developers.com/showthread.php?t=2547997 and didn't find a recovery itself that could be downloadble.
So while googling I stumbled upon this: http://true-android.blogspot.ca/2013/10/how-to-install-custom-recovery-in-most.html.
I my english is good enough to understand, it would seem as if the goomanager app allows u to install recoveries directly from your phone, so you could maybe try if you wish.. If u do, please let us know how it worked, as I'm sure others also would benefit from this.
If you want a CWM recovery for either the Note i717, the Note2 T889 or the S2 T989 let me know and I'll upload them, as those are the only ones I have ATM.
Cheers!
Hey all, about a month ago I flashed Hyperdrive. I messed up not clearing cache/things and it left a few odd bugs that i just dealt with.
Since then I've decided to fix it all up and flash a new rom but now my Safestrap is saying i'm not rooted and SU is saying I don't have the binaries. I'd like to just get off this rom and into something fresh and without bugs but first I need to re-root it looks like. Any help on where to go from here?
-Verizon S4, 4.4.2, NC5
Search google for towel root, super easy apk install root method
joshm.1219 said:
Search google for towel root, super easy apk install root method
Click to expand...
Click to collapse
Thanks a million, it worked like a charm
joshm.1219 said:
Search google for towel root, super easy apk install root method
Click to expand...
Click to collapse
The only problem is now I'm getting stuck flashing the roms. It seems like stock slot one won't mount system and if i try a different slot it just doesn't work.
Binary Manifest Download Fails!?
joshm.1219 said:
Search google for towel root, super easy apk install root method
Click to expand...
Click to collapse
Hey Josh,
Thought I'd jump im here because the post seemed relevant to the problem I'm having. I have a Samsung Galaxy S4, build NC5 with Verizon. I rooted phone with Towel Root and verified with Root Checker and Busy Box. I am using SuperUser Elite and the binary shows as outdated (in red) but when I tap to update it says downloading manifest.... fail. I then hit try again and it says superuser has stopped working. I have uninstalled and reinstalled several times to no avail. I also installed Titanium Backup. I've read about downloading a zip and saving to sd card and then flashing rom and/or starting up in recovery mode and I am not familiar with doing any of that. Any help would be appreciated as I've about had it with the root thing. Thanks ahead of time.