So i've rooted my phone using the unrevoked method... every time I reboot the phone I get a message about "operation failed, check super user something or other" yet when i look in super user permissions, unrevoked, and overclock widget are there... (these are the only apps i can think of that i've granted, or need super user permission) Is there any way to see which program/widget or whatever is throwing that error?
Pardon me if this is a newb question...
Thanks in advance for any help.
i only played with unrevoked briefly, but i believe that you have to open unrevoked and run it again each time you reboot. thats probably why you're getting the error. those apps can't get superuser permissions.
good luck!
SilverStone641 said:
i only played with unrevoked briefly, but i believe that you have to open unrevoked and run it again each time you reboot. thats probably why you're getting the error. those apps can't get superuser permissions.
good luck!
Click to expand...
Click to collapse
I used toast's rooting method first, then unrevoked and have no issues. Others have no issues with unrevoked without toast's method.
why would you use toasts AND unrevoked??? they both essentially do the same thing
hmmm. I seem to remember reading somewhere that they made the root stick on reboot. Maybe They were talking about the next version. Thanks for the tip.
SilverStone641 said:
why would you use toasts AND unrevoked??? they both essentially do the same thing
Click to expand...
Click to collapse
Well no actually they don't..You can't flash custom roms etc with unrevoked for example.
toast's and unrevoked DO NOT do the same thing. toast's gives you write permissions to /system while in recovery. unrevoked allows you to write a few things to /data while in android, but is otherwise useless. nothing currently writes to /system while in android. so, your problem is the overclock bit, because that probably messes with /system, to which nothing can write while in android. remove it, i bet you don't have the problem. unrevoked works well for installing things like wireless tether, not so much for other things.
and, unrevoked has been modified to reboot everytime you start the phone. you don't have to reapply it.
Basically, unrEVOked is useless if you already actually rooted with toast's method.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
timothydonohue said:
and, unrevoked has been modified to reboot everytime you start the phone. you don't have to reapply it.
Click to expand...
Click to collapse
so then is there any way i can figure out why I'm getting an error when i reboot about "operation failed, check super user"
Related
Anyone know how to get permanent root?What i mean by permanent is when i reboot the phone i still have it.
I usually update to D107 then root phone using one click root method,install magic aosp rom,go to SuperUser(which i placed in /system/app folder) it ask me to update to newest version,i click ok and it works,i get root access in Estrong File Manager and other root apps,i can delete and modify /system folder from Estrong file manager.
After reboot i go to Estrong file manager and it doesnt work any more,SuperUser looses its update and any root app i install after reeboot dont get SuperUser prompt for root access anymore.And if i try to update SuperUser it says that update was successful but at the bottom i don't see new version.I still get root if i adb shell su,but on android i don't get asked for su anymore and i dont think i have root on the phone.Can anyone post step by step instruction for getting "permanent root",Thanx in advance.
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
jokarak said:
I think you do have root, but the issue is that root has to be re-enabled after every reboot (it is done automatically and doesn't require user intervention). Don't ask me why, but that seems to be how root in the Epic currently works with the jk method. The superuser app will work only the after it is installed, and subsequent to a reboot, will loses its ability to control permissions, and any new apps that need (or want) to get superuser status will do so without a prompt from the superuser app, which could be bad depending on the app.
Check this thread where they found a work around: http://forum.xda-developers.com/showthread.php?t=788939
Click to expand...
Click to collapse
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
lviv73 said:
Thanx man,that definetly looked promising but dint fix the problem.I wondrer if its just certain phones that have this problem because I don't see many people complaining or is it just certain roms and kernels.
Click to expand...
Click to collapse
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
mykenyc said:
Hey bro, this is what i did because last night i installed the mix kernel and was getting to many dropped calls even in voicemail.
I re-flashed my epic to complete stock, i then ran the Andro/koush one-click method to get clockwork recovery. Then i flashed the Bub's AOSP Magic rom, now i tried to install Andro kernel to get superuser but this didn't work (couldn't gain root), so then i removed superuser.apk and install fluff kernel power saver one and have perm root.
http://forum.sdx-developers.com/epi...uffkernel-epic-4g-version-1-0-1-2-8-1-mflops/
If i remember correctly those was the steps i did.
Click to expand...
Click to collapse
Thanx man,that fixed my root,you saved me alot of trouble,i guess it was the kernel.Oh and the fluff kernel is probably the smoothest kernel i used so far,now my root is there all the time,thanx again.
Just a quick post to let anyone that is interested know that VISIONary appears to work (to some extent at least) on the HTC Wildfire.
I have only used the 'Temproot now' option but that works well enough to give me root and let me install and run Titanium backup to backup my apps. No lasting changes are made when using this option so the root is lost at reboot but you can simply run it again when you need root access again.
There is a Permroot and Temproot at boot option but I havn't been brave enough to try those yet. (anyone brave enough to test these options? ;P)
In case anyone is wondering why I have gone this route instead of using the unREVOKED tool... it is because using VISIONary allows me to get root access without the seriously annoying 'unable to charge phone when switched off' bug that happens with the Wildfire after using the current unREVOKED tool. If that bug gets fixed I would probably use unREVOKED again but until then this is a good second best for me.
Big props to paul @ MoDaCo for this sweet tool.
Thanks i may try this
Dude as far as I know (and I've been looking for this bug quite a long time) the problem does not have nothing to do with unrevoked, but with the recovery that is "pre-installed" with it, in this case with ClockwordMod.
ricardoft said:
Dude as far as I know (and I've been looking for this bug quite a long time) the problem does not have nothing to do with unrevoked, but with the recovery that is "pre-installed" with it, in this case with ClockwordMod.
Click to expand...
Click to collapse
Yes, I understand this but until unrevoked release a version with a different recovery version the problem stills exists. I believe that you can flash the htc recovery instead of the ClockworkMod recovery and not get this problem. But if I do that, I don't get ClockworkMod (and most importantly the ability to nandroid backup) so I might as well just use this temproot method.
As I said in my original post, if an updated unrevoked is released with a fixed "pre-installed" recovery I would use that method but until then this works for when I want root.
with unrevoked you can install custom recovery if exist for wildfire, unrevoked dont edit recovery, it is clockworkmod team work
Or you can charge while your phone is ON instead , I do, cause I don't like getting missed calls etc.
Sent from my HTC Wildfire using XDA App
rolks said:
with unrevoked you can install custom recovery if exist for wildfire, unrevoked dont edit recovery, it is clockworkmod team work
Click to expand...
Click to collapse
Hpez said:
I believe that you can flash the htc recovery instead of the ClockworkMod recovery and not get this problem.
Click to expand...
Click to collapse
As I said above, I know you can use the HTC recovery and the problem goes away but then so does ClockworkMod and the important ability to be able to be able to make nandroid backups. There is a thread here in the forums about this bug and in it someone contacted Koush (Clockworkmod author) and he said it was not a bug with ClockworkMod.
So I don't really know where the problem lies, only that VISONary gives us another option to use in situations when we really must have root, until this problem is resolved in someway.
kevin2516 said:
Or you can charge while your phone is ON instead , I do, cause I don't like getting missed calls etc.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
What happens in this situation; your battery goes low to the point your phone switches off (maybe a night out and you forgot to charge you phone etc) now because your battery is so low, your phone won't switch on. Now, if you can't switch your phone on because your battery is too low and you can't charge your phone when it is switched off....... how do you use your phone again?
Now I understand this situation will very probably not happen but it is an example of why this bug is annoying.
Hpez said:
What happens in this situation; your battery goes low to the point your phone switches off (maybe a night out and you forgot to charge you phone etc) now because your battery is so low, your phone won't switch on. Now, if you can't switch your phone on because your battery is too low and you can't charge your phone when it is switched off....... how do you use your phone again?
Now I understand this situation will very probably not happen but it is an example of why this bug is annoying.
Click to expand...
Click to collapse
Dude you probably don't have read the hole thread. If you had, you probably know that POWER + VOLUME DOWN + TRACKPAD will reboot your phone and you can use it without removing your battery ; ) And yes, this method works fine so now we have 2 methods to root our phones. Yeah! : )
ricardoft said:
Dude you probably don't have read the hole thread. If you had, you probably know that POWER + VOLUME DOWN + TRACKPAD will reboot your phone and you can use it without removing your battery ; ) And yes, this method works fine so now we have 2 methods to root our phones. Yeah! : )
Click to expand...
Click to collapse
Ok, so you can press POWER + VOLUME DOWN + TRACKPAD to reboot to save having to take the battery out (thats cool, I didnt know that, thanks for the info) to get the phone working again but will the phone charge when it is off? If not, then the situation is still the same.
I guess phone charge every time, connected or disconnected. The only problem is the orange light, that stays up no matter what you do (until you reboot or pull the battery out) xD
So if I root with underevoked I can't recharge phone when it's not turned on?
And what can u do with temproot? I mean can you flash roms and kernells? plz help
dud3me said:
So if I root with underevoked I can't recharge phone when it's not turned on?
And what can u do with temproot? I mean can you flash roms and kernells? plz help
Click to expand...
Click to collapse
There is a thread discussing this bug, you would be best to have a read of it as it explains the problem.
http://forum.xda-developers.com/showthread.php?t=769062
As for the temproot question; no you can't flash ROMS, you need Clockworkmod for that but the temproot allows you to use apps that need root access (e.g. Titanium backup).
Hpez said:
As for the temproot question; no you can't flash ROMS, you need Clockworkmod for that but the temproot allows you to use apps that need root access (e.g. Titanium backup).
Click to expand...
Click to collapse
Y would i want to use that
VISONary+ doesn't seem to work any more on the Wildfire after the latest 2.21 OTA update.
VISIONary Permroot
Hi everyone, after reading through this thread I wasn't sure if anyone had successfully tried permroot using VISIONary. (I wasn't having too much luck with the Unrevoked method).
Just tried it now, and as others have found the temproot works just fine. The permroot however just doesnt want to work! I mean it doesnt brick the phone thankfully but it just didnt work for me.
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Also, you need to flash CW at least twice for it to take.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
lucre said:
So, disgusted by the bloatware that came with my myTouch, I figured I'd try to get my ducks in a row and root the sucker.
I read that temproot using Visionary is pretty safe, so I did that. It was nice to be able to get into the familiar CLI and do "rm amazonmp3.apk", etc., but of course everything comes back on restart.
So, I thought, before I permroot, I should back up the ROM. I downloaded Rom Manager and clicked the Backup Current Rom button. It downloaded ClockworkMod and the screen went black, and now it shows no signs of life.
Have I killed it good and dead?
Is it possible to fix it at all? I haven't given the SDK a good look yet - is that likely to be my salvation?
Click to expand...
Click to collapse
First thing's first. Pull the battery for about a minute. Reinstall it then plug in the phone but don't try to boot. If the orange light comes on that's good. If not you might be in trouble but all hope is not lost yet.
krohnjw said:
Can you get into hboot? Hold vol down when you start up the phone.
If so grab this image here: http://www.filefactory.com/file/b4f....140e_26.03.02.26_M_release_155771_signed.zip
Rename it PD15IMG.zip, pop it on the SD card root and let hboot restore the stock image/recovery/bootloader
More info: http://forum.xda-developers.com/showthread.php?t=863899
Click to expand...
Click to collapse
This is your best bet. Re-image it completely and start over, this time READ THE ENTIRE TUTORIAL BEFORE TOUCHING IT!!
jjjackson56 said:
Sdk will probably help but this happened to me also the first time I backed up my first rom. Did you flash cw recovery? If so what I did was a battery pull then power back on holding volume down and pressing power. It then booted into recovery and did the backup properly and everything was fine.
But don't hold me to this could be a fluke.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
ADB probably won't be much help since he's not perm-rooted; it won't let him do anything. Just re-image the sucker.
CBConsultation said:
Also, you need to flash CW at least twice for it to take.
Click to expand...
Click to collapse
In order to perform a nandroid backup you need:
1. Perm root, NOT temp root, PERM ROOT.
2. S-OFF so you can successfully flash clockwork recovery.
Not trying to be harsh just want to be perfectly clear.
TeeJay3800 said:
Not necessarily, it only took once for me.
I think the reason he's having problems is because he flashed the recovery before perm rooting. You're not supposed to attempt a recovery flash while only temp rooted.
Click to expand...
Click to collapse
Yup.
I successfully used the gfree method and set s=off, updated my bootloader to .85.2007 using the great guide here:
http://forum.xda-developers.com/showthread.php?t=858996
The problem is getting permroot to work. Using visionary, I can temproot without any problems and su on a terminal, use rom manager, root-explorer. Everything. But when trying to use Visionary to permroot, it just acts like I am not doing anything. The button just clicks and sits there. It lets me click it again, but it never leaves the menu.
Its not the worst problem in the world, but it would be nice not to use visionary after every restart.
lockback said:
I successfully used the gfree method and set s=off, updated my bootloader to .85.2007 using the great guide here:
http://forum.xda-developers.com/showthread.php?t=858996
The problem is getting permroot to work. Using visionary, I can temproot without any problems and su on a terminal, use rom manager, root-explorer. Everything. But when trying to use Visionary to permroot, it just acts like I am not doing anything. The button just clicks and sits there. It lets me click it again, but it never leaves the menu.
Its not the worst problem in the world, but it would be nice not to use visionary after every restart.
Click to expand...
Click to collapse
if you have temp rooted w/ s=off you do not need to permaroot. The Security Protocol is going to remove any SU access. So you are good to go.
do this, turn off the phone. and pull the battery. put it back it and turn on the phone go to Term Emulator and type "su". do not even worry about the VISIONary program. if the $ changes to a # you are good to go.
Thanks for the response.
I have s=off (just confirmed), and when I do exactly as you said I get a "permission denied" message after running SU. I can't change mount in root explorer either. I would need to run visionary again and temp root to get root access again....
lockback said:
Thanks for the response.
I have s=off (just confirmed), and when I do exactly as you said I get a "permission denied" message after running SU. I can't change mount in root explorer either. I would need to run visionary again and temp root to get root access again....
Click to expand...
Click to collapse
Try this.
uninstall Visionary, reboot the phone to clear up any unwanted cache, and reboot into bootloader and clean the cache and the Dalvik cache then re download VISIONary direct from the site via a computer with a Landline connection, or strong wi-fi connection then push the visionary.apk via a USB cable and install it that way.
just to make sure you do not have a faulty visionary program.
I had the same problem, on three phones. I did get it to run one time after uninstalling, rebooting and installing again.
I didn't plan on staying stock though, so I didn't need to run permroot. I just ran temp root with r/w access to system then downloaded ROM manager from the market and used it to flash clockwork recovery. (it defaults to flashing 3.0, but if you want to use Iced Glacier ROM flash clockwork 2.5.1.2) After that I just rebooted into recovery and nandroid'ed my stock ROM then flashed a new one. Iced Glacier is practically stock, so try it first.
A good idea on clearing everything, sadly, same behavior. Temp root works fine, permroot just ignores the fact I hit the button, and reboot reroots me.....
Did something not go right on the original rooting process? Everything seemed to work with gfree so well.
marine668, I was hoping to run standard for a little while before loading a ROM. I'm *really* happy in the performance coming from a MT3G, so I wanted to wait until I had a good reason to load up a ROM.
So, not the end of the world if I can't permroot, just seems odd.....
lockback said:
A good idea on clearing everything, sadly, same behavior. Temp root works fine, permroot just ignores the fact I hit the button, and reboot reroots me.....
Did something not go right on the original rooting process? Everything seemed to work with gfree so well.
marine668, I was hoping to run standard for a little while before loading a ROM. I'm *really* happy in the performance coming from a MT3G, so I wanted to wait until I had a good reason to load up a ROM.
So, not the end of the world if I can't permroot, just seems odd.....
Click to expand...
Click to collapse
Iced glacier is practically stock, you can try that out. All they did on that ROM is remove the bloat and add a overclock kernel.
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
lockback said:
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
Click to expand...
Click to collapse
the only 2.3 ROM out for the MyTouchHD is CM7.
EVERYTHING else is 2.2 or 2.2.1.
lockback said:
Not to derail too much here, but is Iced Glacier 2.2 or Gingerbread? I was more tempted to jump to G if I do load a ROM.
Click to expand...
Click to collapse
Iced glacier is 2.2, cm7 and gingerbaked are the only 2.3 roms out that i know of
Sent from my HTC Glacier using XDA App
While the changes in gingerbread are nice, many are cosmetic and will be wasted in a sense ROM. Sure there are some optimizations and some new API's, but really the difference isn't so great that I would say its a must have update. If you like sense, waiting until we have an official 2.3 based ROM to customize is not a big deal. If you want sense, go for Iced Glacier for the time being.
I like it, though currently I am running CM7... I could take either or really.
I actually quite dislike sense. I swapped out the launcher in the first 30 minutes, and booting Sense is a pretty big plus for me.
I think I'll wait until CM7 gets a proper release and go with that.
Hey guys, noob here and am kind of hung up...
I d/l TB from the Market some time ago, I used it maybe 2 or 3 times to go through and delete a few unwanted apps. I went through a little tough period where I accidentally deleted 'Google Talk', I found the apk's and fixed that whole issue; however it seems ever since that incident TB will not fire up (correctly). It is telling me it cannot get root access (though I KNOW my phone is rooted). When I goto Problems>Get Busy Box it seems to d/l, but then I get an Error at the top of my device stating that it failed and to see the website for more trouble shooting. I have un-installed TB, re-installed and still noooo luck.
Does anyone have any idea whats going on? Thanks in advance!
Open superuser, tap on TB and "forget " su access. Reboot. Reopen TB and grant su access again.
Dalamar1320 said:
Open superuser, tap on TB and "forget " su access. Reboot. Reopen TB and grant su access again.
Click to expand...
Click to collapse
Oddly enough it doesn't show any Apps on the 'apps' tab in su?
Hmmmm... looks As if my phone may not be rooted any longer? I originally did it through z4root, and now that app isn't in the market.. am I missing something here?
Think it was that EA28 update that did all this. Trying to figure out how to manually root now.
Probably the easiest way to get back to a stock rooted image would be to download an odin image and install it that way. Or are you trying to just get root access back?
http://forum.xda-developers.com/showthread.php?t=867648 - DI01
http://forum.xda-developers.com/showthread.php?t=956289 - EB01
The EA28 does remove root access. I tested it on my wife's Fascinate.
nitroglycerine33 said:
Probably the easiest way to get back to a stock rooted image would be to download an odin image and install it that way. Or are you trying to just get root access back?
http://forum.xda-developers.com/showthread.php?t=867648 - DI01
http://forum.xda-developers.com/showthread.php?t=956289 - EB01
Click to expand...
Click to collapse
Seems weird man, I actually downloaded CWMRecovery_DJ05_DL09.tar.md5, flashed it via Odin....went to settings>>about phone>>and still shows I am running EA28...
Any idea what I may be doing wrong?
EDIT: Another thing I noticed is when i go into Boot Recovery (using vol down+up+power, wait till 2nd samsung logo, vol d...the text is blue, when I hit apply sd:update.zip it goes to red and says its VoodooLagFix at the top?? This was supposed to be an update.zip that got me rooted+busybox... I am getting alittle confused here lol
Awesome !! Got EB01, Froyo 2.2 with Super Clean 2.4... thanks a lot man. My first custom ROM ever haha
You will have to try out Super Clean 2.5! It is compiled of nearly 75% of EB16 source code. The 2.4 I have had some battery life issues. About 12-14 hours tops on a full charge. I am hoping that super clean 2.5 will help with the issue. It might be something to look into.
nitroglycerine33 said:
You will have to try out Super Clean 2.5! It is compiled of nearly 75% of EB16 source code. The 2.4 I have had some battery life issues. About 12-14 hours tops on a full charge. I am hoping that super clean 2.5 will help with the issue. It might be something to look into.
Click to expand...
Click to collapse
i will keep an eye out. Like stated this is all relatively new to me, but boy am I impressed with the speed opposed to my stock 2.1 eclair I was running just an hour ago! lol