I tried Ghetto Root, it claims that it was successful, but SuperSU never gets installed, the only effect is Knox starts force closing at bootup.
I tried ChainFire AutoRoot, I get "FAIL!" After "Nand Write Start".
I'm running stock 4.4.2 on Verizon Note 2. Please help! This is so frustrating. Thank you
UPDATE!*
After working on this all day, I was able to successfully root by using the all in one package posted by NetworkingPro on the 3rd page of the GhettoRoot thread ( http://forum.xda-developers.com/not...ghettoroot-v0-1-towelroot-port-t2864125/page3 )
SuperSU does NOT show up under installed apps, you have to install it manually and update binaries (through the app).
Hope this helps someone!
Related
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!
A couple of weeks ago I successfully rooted my Galaxy S3 using the toolkit - everything including superSU worked fine and dandy.
Because of problems with the device freezing I downloaded the latest update to 4.1.2 using KIES - this of course took away root access.
I uninstalled all the various root apps I had installed and used the phone for a few days to make sure the problem was solved
Today I re-rooted using the toolkit in the same way - all went fine and the phone was rooted and I reinstalled rooted apps like ROM Toolbox Pro that I had already paid for.
When I loaded root apps I got the superSU prompts to allow them which all worked ok. However when I went into SuperSU itself it tried to update the binary and failed each time. Chainfire let me have the latest update which I installed with Mobile ODIN - after that it still worked but the problem of failing to update binary still occured.
I then tried installing the same zip file in recovery using TWRP seemed to work ok BUT now I have the "No SU Binary installed and cant install - this is a problem". I tried again after a fresh install of the latest UPDATE SuperSU v1.10 from here - but still the same and now no rooted apps will run. Super User cant be uninstalled as Play reports that it is installed!I
can fathom a few possible options:-
1) Can I just install SuperUser (chains DD) from the Play store - will this work in place of SuperSU or is it just going to make it worse
2) Can I just re-run the Root Option in the toolkit again in the hopes that it will at least give me superuser rights even if I can actually updated SuperSU (as I had before) or do I need to unroot before rooting again
3) If I could find the download I could use CF-Root via desktop ODIN but I do want TWRP installed for ROM Toolbox to work at its best
Suggestions on these or other solutions welcomed - the phone is still working fine just no root access!
Try flashing cf auto root with Odin.
Sent from my Nexus 7 using Tapatalk HD
Cant update SuperSu v1.10
Im having the same problem! I tried using Superuser to update the binary and it did it successfully but when i try to open the app the problem's still there(I attatched a screenshot)! I was running the free v1.04 of this app and I liked it so much that a few days ago I decided to buy the Pro Version 1.05 through Google Play! Everything was working great than the next day I got a notice saying there was an update to this app (v1.10), so I install it and now it tells me to update the binary but when I choose to update, it gives me an error and restarts my phone ! I attached a screenshot of the error right before it crashes!!! I'm running a rooted HTC one S, with stock ROM (Jelly Bean 4.1.1) and custom recovery (ClockWorkMod), I have enough memory in my entire system!! I hope they fix this soon, I email the developer . If i get an answer i will post back the results here!!
CF Root
Theshawty said:
Try flashing cf auto root with Odin.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks
I just installed CF-Root using ODIN and my rooted apps can now access again BUT when I open SuperSU I am still getting the message to update the binary and the update then fails. The first time it failed it left SuperSU open and apparently functioning, not sure it registered the fact that I have paid for the pro version, though Google Play reports the pro update is installed and wont let me uninstall/re-install. If I cancel the option to update the binary the app just closes now. (odd that it didn't the first time)
So I am still where I started in that it will not update the binary and I am certainly not going to flash the update.superSU V1.10.zip file again because the first time I did that it made no difference and the second time it lost the binary file altogether. I imagine more S3 owners are going to come across this so I will sit tight with what I have and hope that Chainfire can get it working again
I downloaded the md5 file for TWRP and installed that with Mobile Odin so now I have TWRP back as well - still cant open supers but it is doing its job in the background which is the main thing for now
It doesn't seem to be a GS3 related problem. I have a HTC One S, yesterday I updated SuperSU to v1.10 and the app also asked me to update the binaries (as with any update). As you can imagine binaries installation failed.
I have tried to uninstall updates (via app manager) but it doesn't help because su has been deleted. I will have to root again and wait until SuperSU is fixed before updating.
http://forum.xda-developers.com/showthread.php?t=1538053
It has a thread .
jje
Updated SuperSu with CWM through desktop!!
I got an email from developer with a link to download the zip file! After downloading it to my desktop, I plugged in my HTC one S to move the zip file to my root folder the I booted the phone into HBoot and installed it in CWM recovery. Rebooted an done, I double checked by clicking on the SuperSu app and now no more binary update warning and in the settings it says SuperSu Pro v1.10!!! Awesome, here's the link to the download :
download.chainfire.eu/312/SuperSU/UPDATE-SuperSU-v1.10.zip
---------- Post added at 08:38 PM ---------- Previous post was at 07:42 PM ----------
gbswales said:
A couple of weeks ago I successfully rooted my Galaxy S3 using the toolkit - everything including superSU worked fine and dandy.
Because of problems with the device freezing I downloaded the latest update to 4.1.2 using KIES - this of course took away root access.
I uninstalled all the various root apps I had installed and used the phone for a few days to make sure the problem was solved
Today I re-rooted using the toolkit in the same way - all went fine and the phone was rooted and I reinstalled rooted apps like ROM Toolbox Pro that I had already paid for.
When I loaded root apps I got the superSU prompts to allow them which all worked ok. However when I went into SuperSU itself it tried to update the binary and failed each time. Chainfire let me have the latest update which I installed with Mobile ODIN - after that it still worked but the problem of failing to update binary still occured.
I then tried installing the same zip file in recovery using TWRP seemed to work ok BUT now I have the "No SU Binary installed and cant install - this is a problem". I tried again after a fresh install of the latest UPDATE SuperSU v1.10 from here - but still the same and now no rooted apps will run. Super User cant be uninstalled as Play reports that it is installed!I
can fathom a few possible options:-
1) Can I just install SuperUser (chains DD) from the Play store - will this work in place of SuperSU or is it just going to make it worse
2) Can I just re-run the Root Option in the toolkit again in the hopes that it will at least give me superuser rights even if I can actually updated SuperSU (as I had before) or do I need to unroot before rooting again
3) If I could find the download I could use CF-Root via desktop ODIN but I do want TWRP installed for ROM Toolbox to work at its best
Suggestions on these or other solutions welcomed - the phone is still working fine just no root access!
Click to expand...
Click to collapse
I got an email from developer with a link to download the zip file! After downloading it to my desktop, I plugged in my HTC one S to move the zip file to my root folder the I booted the phone into HBoot and installed it in CWM recovery. Rebooted an done, I double checked by clicking on the SuperSu app and now no more binary update warning and in the settings it says SuperSu Pro v1.10!!! Awesome, here's the link to the download. Just copy and paste the link in your browsers address bar!! Hope this helps, good luck!!
download.chainfire.eu/312/SuperSU/UPDATE-SuperSU-v1.10.zip
(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.
As the title states, I'm trying to root my phone using towelroot, yet everytime that it runs all it does is reboot my phone which according to the splash screen for towelroot, says that it's unsuccessful. How do I go about correcting this?
breakneat said:
As the title states, I'm trying to root my phone using towelroot, yet everytime that it runs all it does is reboot my phone which according to the splash screen for towelroot, says that it's unsuccessful. How do I go about correcting this?
Click to expand...
Click to collapse
Have you downloaded SuperSU yet? I had the same issue until I did. I think I remember that was the solution.
Here are the complete instructions for rooting with Towelroot, not much to it.
http://forum.xda-developers.com/showthread.php?t=2784138
breakneat said:
As the title states, I'm trying to root my phone using towelroot, yet everytime that it runs all it does is reboot my phone which according to the splash screen for towelroot, says that it's unsuccessful. How do I go about correcting this?
Click to expand...
Click to collapse
Install SuperSU and busybox onto your phone before you try towel root, these will install but not set up. make sure you have usb debugging turned on, then try it again. SuperSu will bond with towel root and then ask to turn off knox...knox is trying to block it. You need SuperSu and then busybox running. if you get it rooted you'll be able to update SuperSu and set up busy box...maybe rom tool box, lucky patcher blackmart alpha, and rom manager after you get rooted too.
I had an instance where towel root said it worked and apps were saying I still needed full root access, so I used kingo android root to finish over it.
you can also try kingo android root (your decision and you own risk) it worked for me most times without any crap installed. even the chinese version rooted my phone but it puts its own program and SU, but if you already have SuperSU and busybox installed, the SuoerSu will uninstall those other SU apps and still have root. (your decision and you own risk).
Idk what those programs are that the post above me refer to, but all I did is download selinux mode changer and set to permissive, then use towelroot. See if that helps any
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
@ryant35: Thanks for the insight, I had it downloaded, and I was following that guide - it didn't mention installing SuperSU until the device is rooted ( and SafeStrap installed )
@Neontc: SELinux Mode changer depends upon the device already being rooted from what I read on the download page. I'll give it a shot though.
If anyone knows how to fool TowelRoot into thinking that it's online, I'd be very happy to hear that news. I'm going to be out to sea without internet for my phone for about a month, and I'm still actively trying to root my phone...
Thanks again for the quick responses, and I'll try to update when I can as far as what's happened and how I fixxed it!
Maybe I am wrong more than likely I am but I was under the impression that busybox was included somehow with the towel root install. I went with the towel root first then came back with the su after the root was installed after I checked to make sure the root took using root checker from the play store. Jesse
Sent from my SCH-I545 using XDA Free mobile app
http://forum.xda-developers.com/galaxy-s5/general/sm-g900f-root-android-5-0-t2963451
Soon...
Are you saying we can't root?
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
I just got the phone, it was updated to Lollypop, I would rather put a rom on it anyways, do I need to revert back or something? some help would be nice, I am new to this Tmobile phone.
joachim123 said:
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
Click to expand...
Click to collapse
That's what I thought. I usually just flash a recovery and flash super su.
I rooted my device just fine after updating to 5.0 with the cf auto root for kitkat... worked like a charm on lollipop 5.0
So does any twrp recovery .
Sent from my Tmobile S5 on Lollipop 5.0
SuperSU installed but no SU
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
---------- Post added at 02:30 PM ---------- Previous post was at 02:19 PM ----------
gilbnx said:
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
Click to expand...
Click to collapse
Sorry guys! My mistake, I didn't use cf-autoroot. I just ODIN'ed the autoroot and now all is well!
Please anyone who's taken the update (via OTA or by flashing the full DOB1 tar) and then rooted and installed custom recovery: if you've since installed custom Roms, please head over to this thread and let us know how you did it, what steps you took, etc.
http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034
Thanks much!