Related
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.
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
Hi guys, please direct me to the correct place if this is not it. I am currently running revolt and I want to flash a new ROM. I had a status 7 error, which I have had before and I fixed that by updating CWM. But here is where I get hung up. I get an error that I thought was related to ROM manager not having the correct permissions. I went to update my supersu and give it the correct permissions, but I decided I wanted to change to Superuser and uninstalled supersu. I have now having an error where I can not download anything from he play store because my memory is full. When I check my memory it does not add up. I have 12gb of space and a I am using roughly 4 gb of that. If anyone knows of a way that I can fix the issue so that I can update my CWM and flash a new ROM it will be greatly appreciated!
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Guynan said:
Did you have the same error before changing your root managing app? You went from superuser to supersu
Sent from my ST18i
Click to expand...
Click to collapse
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
eviltweak said:
I tried to change from supersu to superuser and I can't download superuser because it says my memory is full.
Click to expand...
Click to collapse
That is really confusing. When it says wrong permissions, it won't mean the root managing app has the wrong permissions, it means that the system has wrong permissions somewhere. This cannot be fixed through Supersu or Superuser. If you can still go into recovery, go into advanced, and then 'fix permissions' and that should fix issues if that is what it pertains to.
Because Android it is based off a Linux kernel, it is very picky with the permissions you give it. Too little and it doesn't work. Too much, and it doesn't work.
Let me know how you go.
I don't think I explained this very well in my first post. My issue lies when I try to flash the new version of cwm. I get this screen.
I went into recovery and advanced and I don't have an option that is fix permissions?
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Guynan said:
So you do have a current working recovery? Okay then advanced>Fix Permissions, at the bottom. If it isn't there, it might be the stock recovery included by Samsung. What is wrong with your current recovery? I can't seem to figure it out sorry.
Click to expand...
Click to collapse
I am running CMW 6.0.3.7. When I go to advanced all that I see is Reboot recovery, Reboot to bootloader, Power Off, Wipe Dalvik Cache, Report Error, Key Test, Show Log, *******Go back*******.
My recovery works, its just not up to date so when I go to flash a new ROM I get a status 7 error. I have had this issue before and I fixed it by updating my recovery. BUT this time when I go to flash an updated version of CWM I get the screen that I posted above.
the status seven error is usually to do with the updater-script. So make sure the ROM you want to flash is for your device, if it isn't (which may be why you have run into issues) don't flash it. But if you are sure it is, go into the ROM, META-INF>Android>Google>Updater-script (the android and google may be the other way round, it won't take you long to find it) And then open the updater script in a text editing program and remove the first few lines of stuff. It will have the words "assert" "getprop" and looks different to the rest, so just delete that section, and rezip if you have to, and try reflashing. But if that doesn't work and the issues are becoming intrusive, a full reset might be in order.
Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk
It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7
themsubtle said:
It also deleted everything an now I have to install everything again! So annoyed may not even go back to colouros, I'm am more than fed up with this phone this has happened to me twice, where the phone has decided to delete everything! Really starting to wish I didn't get the find 7
Click to expand...
Click to collapse
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk
rajitsingh said:
That is very strange. Did not delete anything for me, even the root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
My root is intact but everything else back to default factory settings and as titanium or the built in backup app don't work I now have to start again, i am really not happy would quite happily sell this phone now
Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!
themsubtle said:
Also there seems to be a bug with the new update where if you go into apps in the settings, it's force closes the settings app
Also since the update a lot of the system apps such as the backup and restore app force closes!
Click to expand...
Click to collapse
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:
blessingme said:
It cannot be the update fault!! Check very well whats goes wrong. The update ist very good and completely fixed the screen over-sensitivity issues.:good:
Click to expand...
Click to collapse
It must have been the update, because I have haven't changed anything else for it to happen, the update has fixed the screen sensitivity too which is good,but I am getting a lot of force closes, from settings app, backup and restore app, and few other system apps.
No issues
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.
jebulol said:
I had no issues with the update or any update. I still have root, settings are the same and all to data is there. Maybe your OTA packet got corrupted.
Click to expand...
Click to collapse
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs
No issues here.
Every OTA update has been fine and dandy. I still have root since 1.2.1.
you're not alone.
themsubtle said:
It may have done because I lost all of my settings, apps and data, root was fine but thinking of possibly going to custom rom soon but not which is the most stable with least bugs
Click to expand...
Click to collapse
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk
rajitsingh said:
I use the same modified recovery as I also used the same method for rooting on 1.2.4i. Even upgraded my supersu after rooting. It has to be something else.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
hmmm, then I'm not sure.
Her x9006 (Int-EU) is less than a week old and had nothing significant done except OTA (to 1.2.4i) then root before the 1.2.5i OTA was released.
scar200 said:
My girl's phone had something similar happen.
She updated to 1.2.5i OTA and lost everything - as if the phone went through a factory reset.
It even lost root. Irritated me to no end.
For reference, root was gained a couple of days prior on 1.2.4i through TWRP recovery and the supersu update 2.02.
The recovery was then flashed to the Find7 Mod recovery in the rooting thread on oppo forums.
I suspect that the OTA screw up may have been due to this Find7 mod recovery. I'm not sure.
How did you get root? and what recovery was on the phone when you did the OTA update?
Click to expand...
Click to collapse
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version
themsubtle said:
I had the same as you modded recovery, and I gained root at 1.2.4i (the same way too supersu update thru twrp, then flashed modded recovery) not sure what happened but am still getting force closes when I go into apps in settings and couple other system apps
Also I have the find 7 qhd version
Click to expand...
Click to collapse
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?
scar200 said:
Hmmm, when she gets back, I'll try to test if this modded recovery is indeed the issue.
I'm thinking of using the stock recovery provided by oppo on their forums.
Have you thought of doing full reflash to try and get rid of all the FCs?
Click to expand...
Click to collapse
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working
themsubtle said:
Yeh you'll have to let us know what you find out, Yeh I'm thinking that to, i have got twrp installed at the moment but that was only to do a backup.
Click to expand...
Click to collapse
Ok, I did multiple tests, and am listing the 2 important ones.
Test 1
1. I reflashed back to 1.2.1i then OTA-ed to 1.2.2i (the next OTA it detected was1.2.5i), flashed TWRP and Update SuperSU 2.02 (to get root) then flashed the x9077-official-recovery-mod.
2. Installed some apps, changed some settings then OTA-ed to 1.2.5i - everything was deleted and I lost root after the OTA - essentially I had to go through the new phone start up menu (language, area, wifi, etc.).
*Initial problem replicated*.
Test 2
I did the exact same procedure again as in Test 1 step 1, but instead of the mod recovery I flashed the Stock Recovery for Find 7/7a (from the thread of the same name in the oppo forums, I used version 0712).
Then I again installed the same apps, changed the same settings and OTA-ed to 1.2.5i.
All the apps and settings remained but the phone lost root.
*Only significant delta between the 2 cases was the recovery version.*
Conclusion
The problem in my girl's case was the x9077-official-recovery-mod.img recovery. OTA-ing using that recovery caused her phone to go through a factory reset. This problem isn't present if the stock recovery direct from Oppo was used. Lesson learnt.
Hope this helps someone. Cheers.
themsubtle said:
I have thought of doing full wipe and re-flash but I haven't got a way to restore everything because titanium backup or the built in backup app are not working
Click to expand...
Click to collapse
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.
scar200 said:
Quick update, I switched the SU app from SuperSU to CWM's Superuser and that appears to have solved Titanium Backup issues (based on a thread in oppoforums).
It also made FolderMount usable (I set it up to link some folders from the internal storage to the external SD card).
Hope this helps.
Click to expand...
Click to collapse
I can confirm that switching to CWM's Superuser works. When I updated to 1.2.5i I wasn't able to restore my data for ANY of my apps via Rom Toolbox. I decided to replace the Superuser app caused I remembered that worked for me once with a custom rom on the HTC Amaze, and sure enough now my apps' data has been restored. Success. :good:
rajitsingh said:
Just wanted to let everyone know that the 1.2.5i OTA that I received today has completely fixed the screen over-sensitivity issues for me.
I used to have a lot of issues with things like typing on the keyboard and scrolling through lists and the app drawer, but all those issues are completely gone now.
Also, the OTA did not mess with root. Root is intact.
Sent from my X9006 using Tapatalk
Click to expand...
Click to collapse
Hi, regarding the screen touch oversensitivity issue, just one question - are you using any sort of screen protector?
I have a tempered glass screen protector. I tried everything from 1.2.4i to 2.0.1i beta and the screen problem is there. Hearing good news about this 1.2.5i update and need somebody to confirm it works.