Hi
I am using miui v5 4.3.x
Since it still does not have a multirom supported kernel, I decided to install ubuntu touch by their official dual boot method. Everything went fine but it installed supersu. Since miui already has a btter superuser manager, I decided to remove it. So I went to settings in supersu app and then chose the option that removes supersu so that we can install some other superuser manager.
Now I removed supersu, but it seems like miui su app is no more in use. Even though I have enabled root in that app, apps still say no root.
Please tell me how to fix this and get back to default miui su manager.
have you tried re-rooting via the app?, its in the android market,there are usually conflicts if you have two root apps, disable/ remove one and clear the data and start from scratch.
or just restore to the backup you made before you installed ubuntu,
Related
Superuser not work
ROM Manager saying i need to root my phone. Please help completely lost.
Open superuser, hit menu, toggle permissions on, reboot.
And get rid of ROM Manager
Need More help didn't work
I don't use CM, but if it comes with the newest version of SuperUser (3.04 I believe), then that's likely the problem. Uninstall it and install an older version.
R&R SU with one in this link
http://forum.xda-developers.com/showthread.php?t=1297612
I too had thought I lost root access w/ latest SU (3.04 I believe).
Installed 3.0 in above link and everything back to normal now, i.e, root apps functioning normally.
Just be careful not to update app through Market to 3.04; I haven't found a way to stop it prompting me to update. Can't detach from Market via TB because SU doesn't appear in apps list.
i'm on 3.4 with no issues but ive lost root flashing other roms with 3.0. weird
Do what HipKat says.
I started testing this ROM (FIXED ICS Fusion Final with Aroma + Kernel Compact V1.2.6). And something strange has happened. The ROM is rooted put the app Lucky Patcher v2.7.5 does not install, start and end the process restarts the phone without completing the installation. Titanium Backup already installed successfully (it requires root to install) but Lucky Patcher v2.7.5 does not install. I tried other versions without success.
I tried to install other apps that require root and also had no success. It's strange because it is the message that the app root permission received, but before completing the installation simply restarts.
The Chainfire 3D, Link2SD and Lucky Patcher v2.7.5 installed and did not like said above (message displays permission for root and begins installation but before finishing restarts and does not install). But Titanium Backup, Root Explorer and Terminal Emulator installed without error.
To be sure I tried all the possibilities through which I could do my little knowledge, I did upgrade to the latest ROM version (Version 1.6) and moved to its kernel (kernel is duos.tar end-devenloped for Hell_lock) and still keeps restarting the apps that quoted above.
I undid downloaded the package root and unroot the Millan.SIS through CWM and I ran the unroot, restarted, ran the root, rebooted, tried to install any of the applications I mentioned again and the system could not install before performing a reboot completion of installation.
I can not understand why some applications that require root and install other not. The worst is that just the Link2SD and more accurate than Lucky Patcher not install.
Flash again update.zip to get root access.U can down. it from here
http://www.galaxyyarchive.info/2012/11/installing-merruk-kernel25-onjbv303.html
pustinjak said:
Flash again update.zip to get root access.U can down. it from here
http://www.galaxyyarchive.info/2012/11/installing-merruk-kernel25-onjbv303.html
Click to expand...
Click to collapse
Thanks, tried but unsuccessfully, tried supersu, but also without success. I was enjoying the ROM, but I think I will have to try another.
I do need to wipe cache/data for re-installing a rom, and now all works fine.
I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..
Nexus 4 running CM10 nighty and faux123 kernel
fauxclock app has problem remembering settings when using superuser so previously I installed superSU then removed superuser using root explorer, all good and no problems.
recently I updated CM10 to latest nightly, and as superuser is bundled app it was installed too. so now I have 2 apps for permitting root access but here my problems begin.
Neither app would grant superuser status to apps that requested it
superuser would force close when opened
superSU would start, then try to install the superuser binary, which it could not do as it did not have root privlige
I uninstalled superSU and rebooted, now my launcher pages had all changed back to default (no widgets and stock wallpaper) but worse I had no notification bar and the softkeys where not available. Very hard to navigate the phone
Anyways after an hour I gave up trying to fix the mess I had gotten into and restored my backup from recovery.
So my question is, where did I go wrong? What is the correct procedure for updating the ROM - other than a clean install
Prehaps I should have reinstalled superuser and removed superSU prior to the update?
Any pointers would be appreciated.
Thanks
Rumple
EDIT:
Found some good info on this in the CM10 thread, maybe I should have started there instead of searching all the superSU threads on XDA
problem is now fixed
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??