Hi,
I'm currently on an Xperia Arc running FXP231 (CM10), which comes with SuperUser. I'm trying to switch to SuperSU, but so far no luck.
I've tried:
Downloading the flashable zip that is on SuperSU thread, and flashing it from CWM. The result is that SuperUser is removed, like it should, but SuperSU is not installed. It's not anywhere to be found. If I install it manually afterwards or beforehand, it will say that there is no super user application installed (i.e.: I've lost root).
Installing it from the Play Store. It installs fine, but as soon as I open it, it asks me to update the binary. It gives me two options: from CWM or "normal".
If I choose normal, it gives me "installation failed" no matter what, and then it closes.
If I try the CWM option, SuperUser is removed, but if I open SuperSU afterwards it will tell me that there is no super user application installed, which is rather frustrating.
Does anybody have any idea what might be going on and what to do about it?
Thanks.
Related
I was running stock rom, rooted with bloat removed. I flashed the update through Odin, flashed CWM, and reinstalled Superuser through CWM, and when I went to update the binary in Superuser, I noticed that it said that Busybox was not found. So I installed Busybox Installer and tried to run, but got an error saying that there are problems with some core utilities necessary to load Busybox.
I then reflashed the update, CWM and Superuser, hoping that would fix the problem, but it hasn't.
My question is if there is anyway to load Busybox internally through CWM? Even if it is an older version of Busybox, once the core utilities are there, I can always update through the Busybox Installer.
Worst case scenario, I just back up through Titanium, flash back to complete stock, update, and then load CWM...but I always hate starting from the beginning if I don't have to.
The only apps I use that require root are SetCPU, and Titanium Backup. Would I even notice anything without Busybox working? I know Titanium used to be able to update Busybox right through the app, but then they updated and don't anymore...but I'm not sure if Titanium still requires Busybox to properly work.
I posted screen shots of the error messages I see in both Busybox Installer and when updating the binaries through Superuser. Any help would be greatly appreciated. Thanks!
Nevermind, I fixed it. For some reason, the Busybox app from Stephen (Stericson) was the one that kept giving me the error. So I downloaded the Busybox Installer app from JRummy16, and it worked flawlessly the first time. I went back in to Superuser to see if it recognizes it, and it does. So all seems to be good.
Moderator, please feel free to delete the thread. Thanks!
You solved my problem thanks man!!
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
Just flashed Pons 10.2 ROM. Welcome back and thanks for the new rom. Seems to run pretty smooth. But when I run apps with superuser access I get a warning about using an old su binary 13. Any one want to help me get a new version on my phone? Is it as easy as installing SuperSU from the play store?
First problem I've heard of this. Have you tried to have Superuser update the binary? Also, you could just either install SuperSU from the Play Store, or flash the flashable zip of SuperSU (my recommendation if su isn't working; more pain-free and fool proof), provided by Chainfire. Or do the same with Superuser by Koush off the Play Store, but the only downside to that one is, it's older than the one available in the ROM. Koush doesn't update the Play Store religiously.
It only really shows up with Titanium Backup. Happened with Evolv 3.3 as well. As soon as I tried anything with Android 4.3 I get that warning. Loving your new ROM. Seems faster than 10.1. Going to try that SuperSU.zip now.
Open the su app and go to its settings menu. There will be an option in there to update the binary.
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.
I have been trying to Google this but am a little confused on all the steps I need to (and don't need to) take at this point, especially since I am a little behind. So I wanted to ask for help on forums, if anyone is willing to give some advice on this.
First of all, I have a Sprint version of the HTC 10. I don't know if that matters or not (I recall back when I was trying to figure out the original Magisk, someone mentioned that a Sprint model HTC 10 could be an issue, but I am not sure why).
Also, so far all I have done in terms of rooting it is:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Ummm, anyone?
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Its all there in the op of the magisk thread.
I read that thread, as I said, I still don't understand some parts.
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Have you tried posting in the dedicated Magisk thread?
Try installing leedroid nightly latest it has magisk available when you install rom
i did not try it, till now. I read something a few weeks ago.
But in the magisk thread the op said something that SuperSu is not the supported SU method? only phh superuser?!
I would ask the question in magisk thread.
Firstly: You ask a lot of semi-related questions, a lot of these are already answered, out there, in the appropriate threads.
Let me systematically try to answer your questions
What you have done:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
Click to expand...
Click to collapse
When you install the TWRP recovery, you actually install it to the recovery partition of your device.
the option the "not modify system" has nothing to do with installing TWRP, but with installing other mods/roms
It's there so you can make a backup without modifying the system partition, that way you can go back to a working isntall if you do happen to mess something up.
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
Click to expand...
Click to collapse
SuperSu *should* break safetney and thus should break android pay, as Chainfire says in the following thread: http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
"In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU."
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Click to expand...
Click to collapse
Installing SuperSu trough TWRP installs the dependencies (the actual root) and the application (which just manages the root access), the magisk guide tells you to first flash the preferred root (SuperSu or SuperUser phh's) trough recovery and then install the correct manager app trough the playstore.
This is probably so John doesn't have to keep on updating his zips everytime the makers of the manager apps update their apps, users can just download the latest version.
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
Click to expand...
Click to collapse
Resetting to stock is important for 2 reasons:
1. it cleans out all "old" root apps and methods
2. it cleans up a patched boot.img (kernel)
Then again, if you haven't flashed any other mods, you would probably be safe to install magisk on your rom.
One important thing everyone will always tell you: make a backup! (make a nandroid)
To do this, boot to TWRP and choose "backup" make sure to select: Boot, System and Data
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Click to expand...
Click to collapse
The proper steps would be:
0. Make a nandroid backup in TWRP!!
1. Open SuperSU and choose to completly unroot (somewhere near the bottom of the settings menu)
2. Boot to TWRP and flash Magisk
3. Flash the phhh superuser zip file (from the magisk thread)
4. boot android and install the superuser app from the playstore
5. boot twrp and install AutoMagisk
That's it!
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Click to expand...
Click to collapse
Radio shouldn't be broken unless you flash very old zips, don't worry about it
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Click to expand...
Click to collapse
I allmost enver use official OTA's so I can't say for certain buttttt as you used SuperSU, the root should be systemless so it should accept OTA updates..
What I would do:
1. make a nandroid
2. install OTA
3. See if everything works as expected
4. restore backup if something doesnt work properly =D
I would install the OTA before trying Magisk
Thank you, that was very helpful. I did try Googling all this, but couldn't find clear answers, which is why I am asking here.
And yes, I am definitely going to make a backup before messing with it. Is there any reason to make a Titanium backup too, or will the nandroid one be enough?
As for removing SuperSU, what would that system/boot stock reset delete? Would it delete any installed applications or application settings? Or undo updates to pre-installed system apps? Or reinstall apps that came with the phone that I uninstalled?
Got it working, thanks. (Though, AutoMagisk seems to only be available as an APK, not as a zip that can be installed from TWRP).
Seems like a few configuration settings got wiped due to the system partition being reset, but other than that most of my data seems perfectly intact.