Fix Root in CWM? - Verizon HTC One (M8)

Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?

jimbub said:
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
Click to expand...
Click to collapse
I always selected yes, jsut in case. But I made the jump to official TWRP and no longer get that nag. Maybe check that out. To me its better, esp since its 100% working now.

jimbub said:
Does anybody else get asked if they would like to "Fix root" every time they reboot their phone in clockwork? I've clicked it a few times and it doesn't seem to do anything. I'm not sure if anything is actually wrong as I can run root apps and have s-off.
Any suggestions?
Click to expand...
Click to collapse
I've been getting the same issue since rooting. Root seems to work just fine regardless (can write to /system and everything.)
From what I can tell, it's an issue with the permissions on the su binary. The permissions are rwx-r-x-r-x where as they should be rws-r-x-r-x (setuid bit set.) The easiest way to check this on your device is through the rootchecker app. You can try and manually change the permissions but they don't stick, and I haven't found anybody else with the problem or a solution.

I used to get this on twrp on my s4 and with cwm on this device as well. Always selected no and everything was fine.
Sent from my HTC6525LVW using Tapatalk

Related

[Q] Problems with Oneclick root?!

Hi,
I tried doing the Oneclick root with my Epic that is running 2.1 Eclair. When I installed Titanium and busybox it said phone is rooted. BUT when I start the phone in Manual mode to install update it only has 4 options:
Reboot
Install update
Wipe data
Wipe Cache
When I scroll down and select Install update it starts the process and then says e.signature verification failed update aborted. Is there something I am not doing right? I tried to unroot and reroot the phone but still get the same thing.
When I try the Root process with Oneclick Software for Samsung Galaxy One Click root it says the phone will restart and to select reinstall packages but I do not have that option. It still has the options shown above.
I know when I did my Hero and Evo I could get root and install Roms with no problems.
Can someone help please.
From reading you just need to install clockwork and then install roms and stuff. The kernels include a root, so install clockwork and install the rom I have in my signature. It already includes a kernel so that helps by one less thing you have to do. The one in my signature I have had no issues at all.
I installed rom manager (which is clockwork, right?) and tried to install a rom that way but when it reboots it goes to the same screen and gives the same message.
KateC1 said:
I installed rom manager (which is clockwork, right?) and tried to install a rom that way but when it reboots it goes to the same screen and gives the same message.
Click to expand...
Click to collapse
How are you rebooting into recovery? It sounds like you're hitting the stock recovery. Shut the phone down entirely and hold Vol -, Camera, and power. Keep holding until after the Samsung logo goes away.
Does this bring you more options?
If you still get nothing, try this instead
http://forum.xda-developers.com/showthread.php?t=808103
Nope.... Same options. I will read the link you provided.
Also, Busybox says that my phone is rooted then I click install and it says I do not have nand unlocked. Maybe this is the problem?
KateC1 said:
Nope.... Same options. I will read the link you provided.
Also, Busybox says that my phone is rooted then I click install and it says I do not have nand unlocked. Maybe this is the problem?
Click to expand...
Click to collapse
I might be wrong here, but I'm pretty sure getting nand-unlocked is a part of the rooting process. Perhaps the root didn't work entirely for you, I had a lot of problems using the 1 click root with my first epic because of timing, I had to open the batch file and replace the ping 127etc (the delays) with a pause command because the phone took too long to respond and the second half of the rooting process would fail. Try the link I posted, it worked out well on my first phone.
Thanks....So far I have removed the Oneclick root from it and now it says the phone is not rooted. My next step is to root again... Hope it works.
Worked great! Thank you!!!
KateC1 said:
Worked great! Thank you!!!
Click to expand...
Click to collapse
Awesome, Glad to hear you're up and running, Now you get to do the fun stuff (roms!!!!)
Yup.... Already got my Rom of choice installed and happy... Did not take long at all.

[Q] Unable to root phone

Rooted my phone a few days ago using the toms-world.org "one stop-shop" guide...
Then after having an issue installing a new ROM I restored it to to a point just before I rooted it. Used the same exact procedure as above, and it seems like everything is working like it should, up until I try to do anything that requires permission. It appears my phone isn't rooted, no matter how many times I try. It can't find the su dir. Any ideas?
Have you tried reflashing the su zip? Maybe you missed something? Honestly you should be getting some kind of error unless you're just missing a step I would think.
JoeVsFox said:
Rooted my phone a few days ago using the toms-world.org "one stop-shop" guide...
Click to expand...
Click to collapse
Just followed this procedure for the first time today and it is working for me.
RevTorA said:
Have you tried reflashing the su zip? Maybe you missed something? Honestly you should be getting some kind of error unless you're just missing a step I would think.
Click to expand...
Click to collapse
I have, several times. I've gone into cwm and reflashed it, and it will say "installed successfully" but will leave me with an unrooted phone when I boot it. I'm trying to avoid the pain of trying a clean wipe of the phone...
JoeVsFox said:
I have, several times. I've gone into cwm and reflashed it, and it will say "installed successfully" but will leave me with an unrooted phone when I boot it. I'm trying to avoid the pain of trying a clean wipe of the phone...
Click to expand...
Click to collapse
Mount /system in CWM under "mounts and storage" before you flash su.
Download super user from market kill all proccess aka task manager run a root program should then request root access hope this helps if not sorry ...
Sent from my SCH-I510 using Tapatalk

EDIT: Brick Fixed! Now, why did it happen?

All I've done to it was root it a few days ago. Today I started getting FC's on Instagram, so I rebooted it. Now it is stuck on the GT7+ boot screen, will not go past. I can reboot it, but nogo. Recovery loads, but then it reboots. I CAN get into download mode though.
After searches here, I'm downloading Kies and Odin3-v1.85.zip.
What else do I need? Do I need a file from here: http://www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
??? If so, which one? It's the U.S. T-Mobile 4g GT7+...
Thanks for any help!!! I'm hoping to fix it in the next hour or so before I go to work...
I *can* get to the Power + Volume Down update screen. I am DL'ing the firmware now. What do I do once I get it, how, exactly, do I update/recover it?
Also,
When I try to go into recovery, it loads what looks like it will be recovery, then says:
# Manual Mode #
-- Updating Application...
Then a minute or so later it reboots right back to the GT7+ splash screen and stays there...
:crying:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
VisualOddity said:
Fixed! It took a lot of work, but I got it. So, here is the question...
I rooted the other day, no custom ROM at all. Could this have been due to that root? That's all I can think of that might have caused this issue. I want to root again, but not sure if I should.
Thoughts?
(and before it's said, yes, it did recover, but I don't want to have to recover it again)
Click to expand...
Click to collapse
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
kzoodroid said:
Rooting in itself will not cause this as all root is is adding the su binary file to the system bin folder. It doesn't do anything except give you permission to access system folders. Did you also install a custom recovery too? A bad install of a custom recovery could possibly cause it to hang at reboot.
Click to expand...
Click to collapse
Nope. All I installed root related were Busy Box and Super User so I could use Titanium Backup...
Did you use titanium to remove anything?
Enviado de meu MB525 usando o Tapatalk 2
There was a thread in here about some people having problems with busybox though I have never experienced any problems with it. With so many different versions of this device it possible it could cause problems for some of them.

[Q] rooted? kinda? i dont know?

I used to be rooted at one point (not unlocked, i do not want to unlock my tablet), but after updating to jellybean i am not, ive looked at some of the guides for this, but dont think my situation is quite like theirs. I downloaded voodoo ota rootkeeper before hand and backuped my su, but i could never make it restore. The only checkboxes i have checked under Voodoo OTA rootkeeper are 'superuser app installed', 'system supports root protection' and 'protected su copy available'. I click 'restore root' and it says 'root su restored' but this does not seem to actually do anything.
The other 2 checkboxes 'device rooted' and 'root permission granted' remain unchecked seemingly no matter what i do :/. Is there a tutorial i missed that applies to my problem that does not require unlocking? or is there just nothing i can do to restore it?
Aquifel said:
I used to be rooted at one point (not unlocked, i do not want to unlock my tablet), but after updating to jellybean i am not, ive looked at some of the guides for this, but dont think my situation is quite like theirs. I downloaded voodoo ota rootkeeper before hand and backuped my su, but i could never make it restore. The only checkboxes i have checked under Voodoo OTA rootkeeper are 'superuser app installed', 'system supports root protection' and 'protected su copy available'. I click 'restore root' and it says 'root su restored' but this does not seem to actually do anything.
The other 2 checkboxes 'device rooted' and 'root permission granted' remain unchecked seemingly no matter what i do :/. Is there a tutorial i missed that applies to my problem that does not require unlocking? or is there just nothing i can do to restore it?
Click to expand...
Click to collapse
Im really interested to know how you root without "unlocking" your bootloader, cause when I wanted to root, i need to unlock my bootloader.
Tamaskan said:
Im really interested to know how you root without "unlocking" your bootloader, cause when I wanted to root, i need to unlock my bootloader.
Click to expand...
Click to collapse
There are a lot of methods to do so pre-jellybean, none that i know of post-jellybean, but im by no means an expert.
Aquifel said:
There are a lot of methods to do so pre-jellybean, none that i know of post-jellybean, but im by no means an expert.
Click to expand...
Click to collapse
The hard part is getting su on your device and you already have that if voodoo does its job. Run superuser or if you have supersu run that ( if you are asked to update then do so ). Rerun voodoo and try to restore root. Still no love install supersu from play store and then run it, try voodoo again, no love reboot and try voodoo again.
Much easier to do than type.:good:
tobdaryl said:
The hard part is getting su on your device and you already have that if voodoo does its job. Run superuser or if you have supersu run that ( if you are asked to update then do so ). Rerun voodoo and try to restore root. Still no love install supersu from play store and then run it, try voodoo again, no love reboot and try voodoo again.
Much easier to do than type.:good:
Click to expand...
Click to collapse
I tried that several times unfortunately :/, but! i did find the solution, i found a guy in these forums with a screenshot of my exact problem ( if only we could search screenshots ) here: http://forum.xda-developers.com/showthread.php?t=1893044 which directed me to this post: http://forum.xda-developers.com/showpost.php?p=30522201&postcount=118 and that combination of commands allowed me to finally restore my root . So far im getting superuser prompts again and things seem to be functioning normally, so i think my problem is solved!
Aquifel said:
I tried that several times unfortunately :/, but! i did find the solution, i found a guy in these forums with a screenshot of my exact problem ( if only we could search screenshots ) here: http://forum.xda-developers.com/showthread.php?t=1893044 which directed me to this post: http://forum.xda-developers.com/showpost.php?p=30522201&postcount=118 and that combination of commands allowed me to finally restore my root . So far im getting superuser prompts again and things seem to be functioning normally, so i think my problem is solved!
Click to expand...
Click to collapse
Good! I'm glad you have everything sorted.:good:

[Q] Weaksauce2 Failing to Root

I'm brand new to android so excuse my lack of knowledge but I recently attempted to install Weaksauce2 and Supersu. I tried checking if it was installed properly with Root Checker but it says it was not. I don't understand because when I open Weaksauce2 and click "I Agree", I get a notification that says "Root Activated".
I'm sorry if this is a very simple issue but I don't want to destroy my new phone and couldn't find anything about this on the forums. Thank you in advance.
m.sa said:
I'm brand new to android so excuse my lack of knowledge but I recently attempted to install Weaksauce2 and Supersu. I tried checking if it was installed properly with Root Checker but it says it was not. I don't understand because when I open Weaksauce2 and click "I Agree", I get a notification that says "Root Activated".
I'm sorry if this is a very simple issue but I don't want to destroy my new phone and couldn't find anything about this on the forums. Thank you in advance.
Click to expand...
Click to collapse
Are you still on 4.4.4 or did you accept the update?
jcsugrue said:
Are you still on 4.4.4 or did you accept the update?
Click to expand...
Click to collapse
Still on 4.4.4. I installed Weaksauce2 after transferring it from my computer and then installed Superdu afterwards. I thought the root was successful but then I got Root Checker and it said it was not installed properly.
Is it safe to uninstall Weaksauce and try installing it again?
m.sa said:
Still on 4.4.4. I installed Weaksauce2 after transferring it from my computer and then installed Superdu afterwards. I thought the root was successful but then I got Root Checker and it said it was not installed properly.
Is it safe to uninstall Weaksauce and try installing it again?
Click to expand...
Click to collapse
Yes. You're not going to hurt anything by reinstalling. It took me a couple tries. Just make sure that you don't attempt to update the su bin when you install supersu. The update will fail, but the installed version will work.
m.sa said:
Still on 4.4.4. I installed Weaksauce2 after transferring it from my computer and then installed Superdu afterwards. I thought the root was successful but then I got Root Checker and it said it was not installed properly.
Is it safe to uninstall Weaksauce and try installing it again?
Click to expand...
Click to collapse
You should check if sunshine will work on your device by running it. If you are able to use it.. your root will be permanent.
jcsugrue said:
Yes. You're not going to hurt anything by reinstalling. It took me a couple tries. Just make sure that you don't attempt to update the su bin when you install supersu. The update will fail, but the installed version will work.
Click to expand...
Click to collapse
I tried it a couple of more times and it worked, so I thank you for the information. I wasn't sure if there was some steps I needed to take before uninstalling it.
As for Sunshine, I'd like to ease into rooting and feel around a bit before I pull the trigger on purchasing it. I'm sure I'll find some ROMs I'd like to install, so I'll probably grab it soon.
You can't install ROMs without it right? I don't think you can get a recovery tool without being in S-off, although I'm not sure.
Also, as a follow up question, if I install a third party app, will anything bad happen if the device shuts off? I know Weaksauce is temporary so I'm not sure what would happen if the device shuts off while an app that requires root is installed.
Again, thank you for all the help.
Hmm, it seems the issue actually hasn't been solved. When I used Root Check, it said it was successfully rooted, but Root Checker said it was not. When I tried to run Titanium Backup, an error message appeared saying it could not acquire root privileges. Busybox also says it could not get permission from SuperSU, even though SuperSU asked me to grant permission for it and I said yes.
I'm really not sure what's going on.
m.sa said:
Hmm, it seems the issue actually hasn't been solved. When I used Root Check, it said it was successfully rooted, but Root Checker said it was not. When I tried to run Titanium Backup, an error message appeared saying it could not acquire root privileges. Busybox also says it could not get permission from SuperSU, even though SuperSU asked me to grant permission for it and I said yes.
I'm really not sure what's going on.
Click to expand...
Click to collapse
You cannot install busybox because unless you are s-off your system partition is write protected.
dottat said:
You cannot install busybox because unless you are s-off your system partition is write protected.
Click to expand...
Click to collapse
Okay. I can still use Titanium Backup though right? Regardless, I can't achieve root access so I can't use it anyway. I was looking for a guide on how to use WeakSauce but it really does seem as simple as installing it, running it, and then installing SuperSU. Again, this is my first day on Android so if there's something obvious that I could be missing, feel free to let me know. Sorry for all the trouble.
dottat said:
You cannot install busybox because unless you are s-off your system partition is write protected.
Click to expand...
Click to collapse
I'm VZW M8 4.4.4, Sunshine fails but I am TempRooted with WS2. Pounding away since getting the phone I had ChainfireSU installed but it could not update binaries. I also installed BusyBox. I uninstalled both thinking they were screwing up SS. It appears I still have the SS SU Helper APK installed. RootChecker shows me rooted with SU in /system/xbin/su and BusyBox installed in /system/xbin/busybox. Either WS2 or SS 2.8.4 re-roots me at each boot. I think WS is included in SS and will give TempRoot too. I do have redo any changes I've made such as renaming the HTC update files as they get replaced by HTC. Things like TiBU and ES File Explorer root requiring options work. Things like Xposed don't.
Don't know how I got here as I tried all sorts of combos until it sunk in that SS 2.8.4 just was not going to work on my phone.

Categories

Resources