I Rooted a buddies DINC (SLCD) over the weekend using Unrevoked 3.1. The device is rooted (verified in ADB), and applications such as Root Explorer, and Drocap 2 work.
Here enters the problem. When I opened up Titanium backup it said "Could not find root". My next step was to hit the Problems button. As soon as Busybox updates there is an endless stream of root permission requests. Once you click allow about 20 times, they will stop. After you re open Titanium and click menu>Batch>Backup, again with the endless Superuser permission. I clicked allow at least 30 times by the time the backup reached 3 percent completion.
I figured maybe a quick fix permissions via ROM Manager might help. This time rom manager continued to error out.
NEXT, I figured I would install Busybox via the Busybox app on the market. I downloaded the stable version, Incredible rebooted, and once booted, I tried Ti Backup again......failed.
Next solution was to ADB push Busybox to the DINC in recovery. I got it to install, and even verified its existence with root explorer. I placed it in /System/xbin.
This fixed ROM manager, and I was able to fix permissions HOWEVER Titanium backup still CONSTANTLY asks for superuser permissions.
Also the last thing I can even think of adding to this is that I noticed that some of the root apps seem to ask for permission a little more than I am used to on my DINC. The logs are quite large.
Really have no idea why his is such a pain compared to mine. Again, like I said, he has a 2.2 stock rooted SLCD Incredible.
Any help would be appreciated.
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Deltaechoe said:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Click to expand...
Click to collapse
Only thing I havnt tried is wiping Dalvik. He wants to try flashing his first ROM without loosing all of his apps. But that may have to happen.
Deltaechoe said:
Look at the permissions that you have set in the superuser app, if that's alright try updating or reinstalling superuser. If that doesn't work, try reinstalling titanium. If that doesn't work try cleearing your Dalvik Cache in clockwork. And if that doesn't work reinstall your rom i guess.
Click to expand...
Click to collapse
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
Sent from my ADR6300 using XDA App
PonsAsinorem said:
Also, I know it's generally obvious, but make sure Remember or Always Allow is checked. And reinstalling Superuser fixes most of these problems.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Wish it was all that easy. I have tried all of this lol. Titanium does not find busybix, so I doubt it is an SU issue. All the other root apps I have come across work. Like I said, I pushed Busybox, and it is now in system/xbin, but Ti still does not find it.
Similar issue
Hi, I have similar problem on Desire. I tried all as you and also no luck. I am going back to previous version where it worked.
Related
I searched the forums for a solution to this problem - I found that using Titanium Backup to download a new version of busybox would correct this issue, but it's still failing when I try to fix permissions from ROM Manager Premium.
When I used TiB to install busybox, it installed to /system/xbin/busybox...I put the phone in recovery mode, and from adb I pulled busybox down, and pushed it back to /system/bin
Still no luck....
From ROM Manager, I'm not able to fix permissions. This is happening after I applied someone's patch (I forgot which one) that replaces superuser with version 2.1 that's supposed to be more compatible with this 2.2 leaked build (3.16.605.0 CL203589 release-keys)
Any ideas how I can correct this issue?
I tried clearing superuser permissions 2.1's data, and when I try to fix permissions, I clicked allow, and remember. Still no luck.
Has anyone seen this issue, and been able to correct it? Perhaps I'm not using the right version of superuser permissions? If not, where can I find the correct version?
Well, I guess I've resolved the issue by reverting to an earlier backup from Monday.
Lesson learned - always make backups!
jp43 said:
Well, I guess I've resolved the issue by reverting to an earlier backup from Monday.
Lesson learned - always make backups!
Click to expand...
Click to collapse
Glad the backup solved the issue. The su 2.1 works fine btw, I don't know why someone would have a patch? Its just a zip that you flash through recovery....anyway glad you got everything worked out.
Sent from my Incredible using XDA App
So today after flashing a new rom and then going back to my nandroid backup of my previous rom SetCpu said I do not have root. I'm extremely worried. My phone is/was rooted of course seeing I could flash roms and SetCpu would work just about 25 minutes ago. Would anyone know what to do, rooting my phone previously was such a pain in the a**. Do I have a basta*d Desire HD? Someone be my savior!!
Check other apps that need root, like titanium backup. Still no root message? What ROM are you running? Did you do a full while when you flashed?
I always wipe data before restoring a NAND backup. You could try clearing data for superuser.
Superuser
Do you have the Superuser application?
The superuser app is still there just not working i guess and no app that uses root is working I don't know what to do. Will I have to re-root my device
Did you do what I suggested and do a full wipe then reinstall the backup? Did you try clearing your data for the superuser app?
MeNaCe2s0cieTy said:
So today after flashing a new rom and then going back to my nandroid backup of my previous rom SetCpu said I do not have root. I'm extremely worried. My phone is/was rooted of course seeing I could flash roms and SetCpu would work just about 25 minutes ago. Would anyone know what to do, rooting my phone previously was such a pain in the a**. Do I have a basta*d Desire HD? Someone be my savior!!
Click to expand...
Click to collapse
It happened to me today after I had done what you did. I dont have setcpu. Titanium on my Unity said it doesnt have root. tried everything the guys mentioned here, apart from clearing the data of superuser.
Anyway I did a full wipe, with system format as well, and reflashed Virtuous Unity. All seems fine now.
I had the same problem. Fortunately I had a flashable superuser zip that worked every time. I always keep it on the root of my SD card now just in case. Let me know if you want it and I'll upload it tomorrow from my laptop.
Sent from my Desire HD using xda premium
michael_duvalle said:
I had the same problem. Fortunately I had a flashable superuser zip that worked every time. I always keep it on the root of my SD card now just in case. Let me know if you want it and I'll upload it tomorrow from my laptop.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I'd sure love to have it...you never know when you get hit by another no-root issue.
Try clearing Superuser data if you have access to Settings Menu (i was suggest but if you did or not )
<Menu>, <Settings>, <Applications>, <Manage Applications>, select the <ALL> tab, wait for everything to load, scroll down and select Superuser, <Clear Data>
I don't know what is wrong with Superuser app, but it keeps locking new apps from root automatically without asking.
are you sure that the new ROM is rooted ? try rooting it by visionary+
There you go mate. This always worked for me. Flash in recovery.
mak3040 said:
Try clearing Superuser data if you have access to Settings Menu (i was suggest but if you did or not )
<Menu>, <Settings>, <Applications>, <Manage Applications>, select the <ALL> tab, wait for everything to load, scroll down and select Superuser, <Clear Data>
I don't know what is wrong with Superuser app, but it keeps locking new apps from root automatically without asking.
are you sure that the new ROM is rooted ? try rooting it by visionary+
Click to expand...
Click to collapse
Did not work for me. I lost root again when I restored a different rom.
michael_duvalle said:
There you go mate. This always worked for me. Flash in recovery.
Click to expand...
Click to collapse
Worked like magic.
michael_duvalle said:
There you go mate. This always worked for me. Flash in recovery.
Click to expand...
Click to collapse
i have a similar issue. i rooted my sensation using revolutionary
towards the end it kept restarting the phone and going into the boot screen, and then restarting it again. it did this about 3 times, and then it said it failed. i restarted my phone to the boot menu, and it shows s-off. i tried running the revolutionary program again to make sure, and it confirmed this.
i then got the leedroid mod and flashed that to my phone. the leedroid mod works well, just whenever i try to access superuser it crashes. i tried accessing titanium backup and adfree and when these request for permissions, i get an android notification that superuser has crashed and the request times out.
i tried using this fix, but this errors as well...
any assistance in resolving this will be greatly appreciated
thanks
hi
i had the same problem with trying some new roms and restoring nandroid.
i fixed this problem with: Rom Manager -> correct permissions -> reboot
best regards
OK, since search is down, I'm going to be a noob and ask something I know has been asked before...
I installed and ran V6 Supercharger yesterday, but wasn't completely sure if it worked properly, so I decided to start again. So I went back to tutorial and started again, first trying to re-install Busybox 1.18.2, as directed. I got message "unable to load busybox onto /sys/xbin". Odd.
So I backed out and opened Busybox installer again, this time got error message "No Root Access!". Tried that a few times, but same message. So I opened Titanium, No Root, MyBackUpRoot...NO ROOT!! 4Ext is also reporting errors, although it does accept SU Permissions...
Ummm...help??
E: Build.prop Editor, ROM manager, RAM Manager Pro, Root Explorer, ES Explorer all granted SU Permissions...
I think I know what may have happened, although don't know how or exactly why... Thinking busybox.apk has been deleted from /system somehow.
I am able to boot to recovery and doing nandroid now, so I obviously still have root. Going to wipe Dalvic and reflash ROM.
Fingers crossed.
Nope.
Did fresh download of Runnymede 6041 and reflashed.
Still same problem. Titanium does not see root, neither does busybox or MbR.
Really not happy now.
Edit: If anyone reading this has experience, where would I find the Busybox.apk, to verify if it was missing and how would I replace??
Have you try to clear superuser data in settings-applications-manage applications ?
I had this problem when I restore data for superuser using mybackup root.
Also check how much free system space that you have before downloading a new busybox. Maybe the free space is not enough for the new busybox.
Download program called visionary and install it. Open it then press (temproot) then keep going on what u doing. Make sure that u having 2.2 android or custom ROM. I did that and update worked as it should with no problem
Sent from my HTC Desire using XDA
Thanks for replies guys.
@mahmoud, want to point out I am root and s-off with custom ROM etc. Not sure if temproot will help me. I'm pretty sure the original Busybox file that is installed during unrEVOked has gone missing. Is that what happened for you too??
As I say, I can still boot to recovery and most SU apps are working...just not those that need Busybox.
@ckp, I will try that this evening. Cheers.
777ace said:
Thanks for replies guys.
@mahmoud, want to point out I am root and s-off with custom ROM etc. Not sure if temproot will help me. I'm pretty sure the original Busybox file that is installed during unrEVOked has gone missing. Is that what happened for you too??
As I say, I can still boot to recovery and most SU apps are working...just not those that need Busybox.
@ckp, I will try that this evening. Cheers.
Click to expand...
Click to collapse
Aaaaaahhhhh ok. Sorry I misunderstood u. What happened to me is that I wanted to root my phone and I couldn't use unrEVOked
Coz it always show me CID MISSING so I downloaded 3 apps and rooted my phone without computer. Visionary, superuser and ROM manager. I had to update busybox in superuser app. But it didn't update until I did temproot using visionary app. I don't know if that will help u or no. But nothing will happen if u downloaded visionary and temproot then try busybox.. let me know if u had any thing. Goodluck
Sent from my HTC Desire using XDA
777ace said:
OK, since search is down, I'm going to be a noob and ask something I know has been asked before...
I installed and ran V6 Supercharger yesterday, but wasn't completely sure if it worked properly, so I decided to start again. So I went back to tutorial and started again, first trying to re-install Busybox 1.18.2, as directed. I got message "unable to load busybox onto /sys/xbin". Odd.
So I backed out and opened Busybox installer again, this time got error message "No Root Access!". Tried that a few times, but same message. So I opened Titanium, No Root, MyBackUpRoot...NO ROOT!! 4Ext is also reporting errors, although it does accept SU Permissions...
Ummm...help??
E: Build.prop Editor, ROM manager, RAM Manager Pro, Root Explorer, ES Explorer all granted SU Permissions...
Click to expand...
Click to collapse
AFAIK, Titanium uses its own Busybox, so I would suggest uninstalling Titanium, reflashing Busybox (I don't know if it's possible), then reflashing Titanium. I hope this will help.
Thanks Coempi, but I did that already... Somehow, whatever tells Busybox or Titanium that I have root, is not doing that.
Dunno wtf just happened, but I uninstalled Titanium again, rebooted (again) and installed Busybox straight up... Everything back to normal, but nfi what I did.
I guess sometimes its the simple things, yeah...??
Thanks for help all.
777ace said:
Dunno wtf just happened, but I uninstalled Titanium again, rebooted (again) and installed Busybox straight up... Everything back to normal, but nfi what I did.
I guess sometimes its the simple things, yeah...??
Thanks for help all.
Click to expand...
Click to collapse
I'm glad it worked out finally.
Sent from my HTC Desire using Tapatalk
So I used odin to flash the official stock jelllybean rom then I used the Samsung toolkit to flash clockwork mod recovery and root. To root it said to flash a superuser zip in recovery. I did.after I reboot everything is working fine. Apps gain root access the promp pops up but after a few minutes it didn't anymore and I cant open busybox or setcpu because it cant gain access but the apps I already granted can. I updated su binary and it fails on gaining root access.
This happens with both super su and superuser. I also tried starting again by oding rom and rooting again. No luck. Please help
Sent from my SGH-T999 using xda premium
Sent from my SGH-T999 using xda premium
Ok, you can try a few things.
First since you have Root Explorer already granted, go into /system/xbin and make sure that there is a file named su. If not, then go into /system/bin and see if it is there. Follow this: If it is in /system/bin, copy it and put it in /system/xbin, check permissions and reboot. Then try an un-granted app and see if that works. Pay attention to the bin and xbin parts here ok.!?
^^^Edit: While you are in /system/xbin make sure that busybox is there also. Just to be sure it installed properly.
Second. If the above didn't work, the go to the market and ChainsDD used to have an app called SuperUser Updated Fixer or something like that. I remember a long time ago, I was having some trouble updating the binaries (as were tons of other people) and he came out with that handy little app. I have been using it since (whenever I have a ROM that uses SuperUser.apk).
Third: I literally just read over in mrRobinson's thread that ICS likes SuperUser, while JB likes SuperSU. Might be something to look into. Maybe swapping out the two apps, might alleviate the issue.
I tried swapping out to super su but was having the same problem. Instead of trying the root explorer method you posted I thought I would go ahead and clean install yet another time. I just wanted the update and root access to work no errors. So here's what I did to fix it and it worked however there's another problem now.
I factory reset, wiped caches
flashed jb stock firmware (instead of the stock fw i now flashed mr.robinsons prerooted firmware)
rebooted checked and saw super su was working fine with my apps.
flashed clockwork mod recovery
made a nandroid backup
flashed wildchilds stock deodexed jb rom (i needed a deodexed rom thats why i flashed this otherwise i would of just kept stock)
booted up and in the play store theres an update for Super Su however i cant update it, it gives me an error.
error retrieving information from server. cant download.tried wifi on off, mobile data on off, clearing google play data and cache. no luck. restored nandroid and there was no update so i clicked reinstall from playstore in su and when i went to go download it, it gave the same error.
So my previous problem is fixed and i dont seem to be losing root anymore but now I cant update SU anymore.
Never mind I seemed to have linked the two issues just because 1 happened before the other, but that might not be the case.
The Google play error is now happening with other apps that i try to update as well.
Is this happening to you guys too?
sometimes when i power off my phone it doesnt boot anymore it gets stuck on boot loop. for example all i did was fix permissions in cwm and it got stuck on boot loop.
Did you Odin root66?
Yeah I odined the root 66 fw by Robinson. That has fixed losing root. Super user is working fine. The only remaining problem is that I get into a boot loop sometimes when I restart for some reason like when I fix permissions.
Sent from my SGH-T999 using xda premium
Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Edit: Sorry, earlier it was in the dev section.
connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.
Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available