I just tried running the one click method. I had USB debugging enabled, upgraded to the latest drivers, and ran the exe. Everything said it was successful, I rebooted again, and installed Titanium Backup, and it's telling me it was unable to access root. What gives?
Do you see Superuser on your phone? Doesn't sound like the one click was successful, did you use a Mac? The one click was broken earlier for Macs, seems to work now though.
militant said:
I just tried running the one click method. I had USB debugging enabled, upgraded to the latest drivers, and ran the exe. Everything said it was successful, I rebooted again, and installed Titanium Backup, and it's telling me it was unable to access root. What gives?
Click to expand...
Click to collapse
I would manually type the root method into adb, then use the one click app to automatically push su and stuff to the phone. That seemed to work really well for me.
Sent from my DROID3 using XDA App
Thanks for both of your suggestions. For whatever reason, doing a second reboot on the phone seemed to work. I noticed SU was indeed installed, but TB wasn't finding root. After the 2nd reboot poof TB found root and all is well. Admin can close/lock this thread or I guess keep it open if others happen to have issues with One-Click to consolidate some threads. From what I've been reading one click is damn near bulletproof though.
Related
Before I get into it, I'm not sure if this is the best section for this. I posted here because it's a Samsung Captivate I am using and this is a question.
Anyway, I used a video to root my Captivate. I downloaded SuperOneClick, the USB Drivers for Captivate and .NET Framework. Everything went well and it said my phone was rooted successfully. Well, I used Root Check and Term Emulator and both said my phone was, infact, not rooted.
I also have the SuperUser app on my phone. I then proceeded to try again, where I got the error that my Captivate was already rooted. I used psneuter exploit to root. Now, I'm attempted to unroot my phone, where SuperOneClick seems to be frozen at "Waiting for device.."
After I unroot, what should I change or try?
Did you enable USB debugging from your phone? Give me more details on your rom and other stuff.
Also if your on gingerbread the one click root doesn't work on some gingy builds
Sent from my SPH-D700 using XDA App
Download any app from the market that requires root. Try to use it. If it works, your rooted, if not something is wrong.
Hello everyone. I know I'm a noob, but am hoping I can get some help anyway. Tried searching and not too many people are having the same problem, so I started a new thread.
Anyway, I used the one click root found in this thread:
http://forum.xda-developers.com/showthread.php?t=1348557
( I tried to post in that thread, but can't since I don't have 10 posts )
I'm new to hacking and I'll be honest. I only wanted to root my phone so I could use wireless tether, and then use Titanium Backup to freeze a lot of the bloatware on the phone. I have no desire to install a different ROM. I'm happy with the one it has, and happy to take the updates Verizon pushes. Everything was good until the latest update came through. When it downloaded, and rebooted, instead of updating, it booted in clockwork mod recovery. No matter what I tried, I couldn't get the update to go through.
So I settled on never updating again and froze the updater to prevent my phone from trying to update and going to CMR at random times. About 4 days later, my bluetooth quit working. Couldn't figure out why. Thought I was going to have to send it in for warranty work, so I tried to undo all the mods. I unfroze everything, and then hit the one click unroot button. It said it worked. Problem is, superuser is still installed with no way to uninstall.
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Next I tried to go ahead and get the update since the unrooting process was supposed to have reinstalled stock recovery. Well, it didn't. I still ended up booting up into CMR again. STILL can't update even after unrooting. Double checked, and wireless tether and Titanium backup both say "no root". On a whim, I try the blue tooth and guess what. It worked. May not need to send the phone off for warranty work after all.
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
I know this is a lot of question and I'm a noob, but I'm a noob willing to learn. If this problem has been encountered before, I apologize in advnace for not finding the appropriate thread. I tried.
updater app
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
NewDroidXUser said:
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Click to expand...
Click to collapse
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
NewDroidXUser said:
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Click to expand...
Click to collapse
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
NewDroidXUser said:
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
Click to expand...
Click to collapse
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
brad6360 said:
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
Click to expand...
Click to collapse
Ah, thanks. I'll post again to update how that went. Though, I'd like to keep the stock recovery. I'll try to do it without CWM.
latenighter49 said:
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
Click to expand...
Click to collapse
How did you change permissions in Gemini? I turned off all the autorun features and was able to get Bluetooth working but I didn't see anything about permissions in the settings. I could have missed it though being at work and all. Will turning off all the autorun features of the Software Update app stop it from trying to download the update in the middle of the night when I'm not looking like it sounds like it should?
In gemeni select block app. It's the same as freezing in titanium backup.
Sent from my VS910 4G using XDA
So i recently got my replacement phone and i decided to root it just like my old phone. Ive had a Galaxy s 4 before and i was able to root it with CF auto root in the past. When i try now odin says pass but i get the binary error. Ive tried reflashing, wiping data and cache, TWRP method and i even got another phone but no prevail. I have checked the files and they are all recent and updated and i have also updated my drivers. Please tell me what im missing or if y9u have any idea why this is happening. Thank you for your time! Cheers!
Jman9607 said:
So i recently got my replacement phone and i decided to root it just like my old phone. Ive had a Galaxy s 4 before and i was able to root it with CF auto root in the past. When i try now odin says pass but i get the binary error. Ive tried reflashing, wiping data and cache, TWRP method and i even got another phone but no prevail. I have checked the files and they are all recent and updated and i have also updated my drivers. Please tell me what im missing or if y9u have any idea why this is happening. Thank you for your time! Cheers!
Click to expand...
Click to collapse
Did you try re downloading cfauto root? When do you get the binary error ?
spirodave said:
Did you try re downloading cfauto root? When do you get the binary error ?
Click to expand...
Click to collapse
Yes I did and I'm sure I downloaded the right one. I'm getting the error when I open up the SU application.
re: root issue
Jman9607 said:
Yes I did and I'm sure I downloaded the right one. I'm getting the error when I open up the SU application.
Click to expand...
Click to collapse
re-download supersu from the play store and let
it install, reboot the phone and all should be good.
Jman9607 said:
Yes I did and I'm sure I downloaded the right one. I'm getting the error when I open up the SU application.
Click to expand...
Click to collapse
What Mister Junky said ... That is always a given in most cases
Misterjunky said:
re-download supersu from the play store and let
it install, reboot the phone and all should be good.
Click to expand...
Click to collapse
I just tried that and no success
Jman9607 said:
So i recently got my replacement phone and i decided to root it just like my old phone. Ive had a Galaxy s 4 before and i was able to root it with CF auto root in the past. When i try now odin says pass but i get the binary error. Ive tried reflashing, wiping data and cache, TWRP method and i even got another phone but no prevail. I have checked the files and they are all recent and updated and i have also updated my drivers. Please tell me what im missing or if y9u have any idea why this is happening. Thank you for your time! Cheers!
Click to expand...
Click to collapse
What I have done in the past is used root explorer and gone in and deleted the apk myself and rebooted. No uninstall from play store or things like that. That is if root explorer works since you root might be messed up. If that don't do it. Odin back to stock and fresh download every file. Check md5. Start all over. Sorry man
NOTE 4
re: usb debugging
Jman9607 said:
I just tried that and no success
Click to expand...
Click to collapse
Okay in that case you forgot to enable usb debugging in the phone.
Go to settings and navigate to "about" then scroll down until you see
"build number" once you find that click on it many times until it tells
you that developers option enabled and then go into developers options.
Then check the box which says: "usb debugging" to enable it.
Once that's done odin flash cf-autoroot again and that should
fix your supersu / root issue.
Good luck!
I didnt forget usb debugging. I will try flashing stock i guess
Jman9607 said:
I didnt forget usb debugging. I will try flashing stock i guess
Click to expand...
Click to collapse
Odin back to stock not flash. Start all over
NOTE 4
I unrooted to stock and deleted all the files i was using. I redownloaded everything and ran the process over again. This time it worked and i didnt get the error messages. Thanks to all that replied!!
I successfully installed Android M, and things were mostly okay. Titanium Backup won't load. It force closes, and having a problem with Dolphin Browser flashing a handful of times and then erroring out...unable to use. Other than that, everything seemed to be working perfectly. However, I needed to be able to restore my app settings, and I know Titanium Backup needs root. So, I thought maybe that's why it was force closing. So, I decided the easiest way to root would probably be using the Nexus Toolkit. I used that, which seemed to go normally, but the phone won't boot now. It just goes black. ADB seems to be able to communicate with it in this black screen state (via Nexus Toolkit, for example), but I can't get anywhere. I tried re-flashing the boot and bootloader, but it didn't help. I am seeking the wisdom of the elders.
YOu are going to have to start all over. SO factory reset. to clear out everything and get a fresh M load.
The toolkit is for Android L. So it overwrote things that Android M needed.
Once you have a fresh install. Go here http://www.androidauthority.com/android-m-root-613760/ and root.
all you need to do os flash a m kernel(despair kernel) and the latest SuperSU, and youll have root. flashing the latest supersu with a m kernel will not work.
Thank you for the feedback. I am mostly in business. I can't get BusyBox to install, though. The app runs fine, but actually installing it from within the app does not work...says it was not successful. I have tried the other location, which didn't work also. Any thoughts? Thanks much; greatly appreciate the assist.
mystik1 said:
Thank you for the feedback. I am mostly in business. I can't get BusyBox to install, though. The app runs fine, but actually installing it from within the app does not work...says it was not successful. I have tried the other location, which didn't work also. Any thoughts? Thanks much; greatly appreciate the assist.
Click to expand...
Click to collapse
I'll do some more research and get back to you on this one. Not exactly sure how busybox is running on the new file structure.
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