Database Users

S-off, Superuser denying root like crazy

Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.

Odin is for Samsung Phones and if u lost root redownload the rom or Google super user and download the binaries and just flash them.
Sent from my Dark Unicorn Resurrected v.2.5 using Tapatalk 2

I tried all that, anyway im in the middle of a stock restore right now and trying to reroot but stuck at the damn visionary step >.<

I am now stuck with S-on and back in a stock rom, downgraded, and visionary still doesnt work, i give up

Try gfree method
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium

You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.

Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
I believe you got two troubleshootings steps backwards.
After you have searched and exhausted every troubleshooting step you found (which obviously wasn't thorough), you should have posted in the MIUI thread about the problem. They might have scolded you a little before answering, but you would have gotten your answer.
Flashing back to stock is ALWAYS your last resort. It should only be done after scouring the web for answers, then asking for the answer, and when there is no other alternative - FroYo PD15IMG.zip.
Jack is blunt, but as he's as right as always.

I'm not one to deny mistakes, that sure was stupid of me not to look, i guess i just thought there were deeper problems than just the rom having it turned off, anyway i'm doing the downgrade now and it should work, thank you for the help its appreciated

Jack_R1 said:
You're very likely doing so much wrong..
MIUI has an option in settings - "allow superuser privileges". You didn't turn it on, and it's off by default. That's it. And from there you went to a whole new level of going the wrong way.
No amount of restoring to stock and re-rooting can help you. Root privileges aren't phone-specific, they're ROM-specific, and relevant only for the ROM currently on the phone. Reflash the ROM with something else - and existence or inexistence of root will depend on this "something else". Thus I fail to understand, what were you looking for when restoring to stock. It was as irrelevant as could possibly be.
Click to expand...
Click to collapse
Could you point me to this "allow superuser privileges"? I have restored with recovery and have yet to find such a setting.

If you are referring to the permission guard, it allows everything, and there is no setting to simply turn it on

No, not this one. It's been some time since I sold my Nexus One, which was running MIUI back at the time, but I understand that in the newer MIUI there is an app or setting, called LBC guard, which controls both Superuser access and app permissions. Try looking it up.
P.S. I remember CM team member post, saying that the newer CM9 also come with root privileges turned off by default, because they decided it's a safer way.

Right, and the Permission Guard is run by LBC guard, there is no way to set anything different from what i have, i believe its a problem with the busybox binaries and superuser binaries, i'm trying to use this SuperSU instead of superuser to see if that will work. If i remember correctly before all this happened i may have hit uninstall busybox by accident and that may be why its not working, could be that ive never had busybox working and haven't been able to install it due to the SU problem
EDIT: Yes i have solved it now, SuperSU actually makes the prompts for superuser come up now, im using it instead of superuser entirely, must be deeper problems with original superuser

If you had SuperSU installed on the system and additionally installed the regular Superuser, or the other way around - these two are incompatible on binaries AFAIK, and mixing the applications without cleaning up the build and using the correct binary could cause what you were experiencing.

Yes your probably correct only i had two separate versions of superuser that didnt overwrite and that must be where the binaries got messed up

The 1st thing I usually do when I install a new rom, is install SuperSU, update the binaries then I use Titanium to uninstall Superuser.
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium

Drakona.cookie said:
Currently Running Miui 2.7.1.3 i believe the numbers are, whichever the latest version of the rom is. It installed no problem, was merely updating to try to fix theme issues from 2.6, and here is where the problem begins:
So i was browsing my phone and realised that i didn't have superuser on there, wondering why because usually every rom i ever ran had it automatically on there, installed it off of another site, the elite version, and from there everything got screwed up, i don't know what happened or why it started but, i could no longer run busybox, TBU, setcpu, nothing that requires root, due to the fact that superuser was denying root. I had no clue why, i've been reading threads for hours similar to "Superuser denying root" and such, and to no avail, the problem is still there, i have set superuser to both prompt and allow when asking for root, and neither worked, so i figured a clean fresh reflash of MIUI would help, however even after wiping and a clean install, root does not work, ive read some articles describing to just unroot and root again however it's been so long since ive rooted a phone, can anyone direct me to the best way to do this without having to do an ODIN and set up my phone allover again, keep in mind that it is still S-Off. What am i doing wrong?
I also have tried to clear data for superuser, as well as install multiple versions, neither have worked.
Any help is greatly appreciated!
ROBLEM SOLVED:
To those with similar problems to this who have ruled out other reasons, described in this thread, abandon Superuser and download SuperSU instead, it fixed my problem.
Click to expand...
Click to collapse
Anyone else with this problem go in the permissions app and enable root as miui uses its own root for security reasons.
Sent from my T-Mobile MyTouch 4g using xda premium

MIUI uses a customized superuser app. Use it and follow the instructions. Cnote ports the ROM. He knows what he's talking about.

Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks

Droid-2 said:
Hello, I am a newbie and looking for a miracle. I am going to apologize for the length of this message in advance. Couple days ago I perm rooted the HTC Glacier Mytouch 4g using the instructions at //wiki.cyanogenmod.org/w/Install_CM_for_glacier . As instructed, I downgraded the software to 1.17.531.2 and then perm rooted with S-Off on the device. Then, I installed the cyanogenMod 7.2.0-glacier (stable version) with the google apps. Everything worked great and was happy.
Right after I installed AdFree from Googleplay, I had issues but problem may not be caused by this app. Googleplay gave me a message of an “error no connection”. I got a message that the “ADWLauncher failed to launch” over and over again which prevented me from doing anything else. I was able to reboot the phone in between the notifications of the ADWLauncher failure. When I was back up and running, I got the same message of Googleplay “error no connection” and ADW failure very quick after start up. I pulled the battery and did a hard power up (volume down plus power button at same time). This is when things got worse. The Hboot starts up and wants to update, which I did but then I could not choose recovery mode to install a backup. If I choose not to update Hboot, then I only have the option to restart the phone. I can see on top of the screen “Glacier PVT SHIP S-OFF” .
Wait – things get worse. I am no longer running the cyanogenmod ROM but am back to the downgraded ROM 1.17.531.2. I still can’t download from googleplay because I get the message “Error no connection”, even though I am running on the old ROM. I can’t download apps from the phone, but I can push apps to phone from my googleplay account. I did push the ROM Manager app to the phone. When I start the ROM Manager, I get the message “You must root phone for ROM to function. Superuser was not found at “/system/bin/su” or “/system/xbin/su”.
I tried to start the recovery through adb using “adb reboot recovery”, but I get a power off symbol (a red circle) and phone freezes. I need to pull the battery to reboot.
Again sorry for the length. I am hoping for a miracle. Since I can’t do anything in the hard power up mode, I need to find a way to fix through adb or fastboot. Does anyone know how to get the Superuser installed through adb or fastboot? Is there a way to flash another custom ROM that has a superuser installed through adb or fastboot?
BTW. Gmail works fine.
thanks
Click to expand...
Click to collapse
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.

estallings15 said:
I would download a recovery image and use fastboot to install it. Maybe something is wrong with your recovery.
fastboot flash recovery recoveryname.img
Then wipe system, do a factory reset, and wipe dalvik-cache before flashing a ROM. Also, re-download your ROM.
Click to expand...
Click to collapse
Thanks - I will need to try this later

[Q] Nexus 7 wifi

Im new to Android world, so please help me.
Now, my Nexus 7 Wifi is now unlocked and rooted by your tutorial, and
flashed Xenon HD Custom Rom.
I was in Jelly Bean 4.2.2 before. And i found some site that says
XenonHD is updated to 4.2.2 version, so i try to get it, and installed it to
my device. But after evrything done, i checked my device's version and it
says 4.2.1, but im sure i downloaded the right one, dated April 2013, as
far as i know. So, my device was downgraded to 4.2.1
Question:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
e) And what more can i do to my device to achieve it AWESOMENESS
Thanks in advance..

a) Yes, on many android devices it's that easy to downgrade. You don't need to jump through all the hoops like iOS requires you to.
b) Sounds like something may have gone wrong during the install process. Perhaps you could post a picture of what it looks like.
c) not sure, never used it.
d) Guess that's up to you. If it's an upgrade then it could fix the screen issue you're having. You'd flash it the same way you flashed the 4.2.1 version.

I'm sorry for spoonfeeding.
zeneleven said:
a) Is it just that easy for downgrading an Android device? Because on
iOS, there are lots of concerns first before you can actually do
downgrading..
Click to expand...
Click to collapse
Yes. XenonHD says it's 4.2.2 though, so I'm pretty sure you flashed an old build or the dev forgot to edit some text to make it say 4.2.2.
zeneleven said:
b) After installing apps, i made a backup with Nexus Root Toolkit, and
after the backup process, it reboots, and i notice that something is
wrong, the X animation logo goes somewhere at the lower right, and
when it goes to lockscreen, since im locked on landscape orientation,
half right side shows first then the half left side, youll really say that, it is
not okay. I tried rebooting by XenonHD settings, i tried to turn off and turn
it on again, same thing happens, what should i do?
Click to expand...
Click to collapse
Flash a different ROM or reflash your current one. Backups shouldn't have any effect on the ROM; if the backup app you're using negatively impacts your experience, switch it (I use titanium backup). TWRP recovery also supports nandroid backups.
zeneleven said:
c) About XenonHD, is it just one theme available? or i can download more
themes elsewhere? can somebody point me to where can i do that?
Click to expand...
Click to collapse
From the ROM thread, it says it supports CM10.1 themes (theme chooser). Search "CM10 themes" on Google Play to find them, then go to your settings to apply.
zeneleven said:
d) should i be re-flashing for XenonHD 4.2.2? How would i do that?
Click to expand...
Click to collapse
First, download the ROM to your device (if you haven't already), and google apps.
Make a backup of your data (nandroid or Titanium backup or some other backup app).
Then hold the power button, and select either "reboot"/"restart" or "recovery".
If you select "reboot" and no option for "recovery" comes up, hold down the volume down key while the device is restarting, then navigate using the volume buttons once the bootloader pops up, to the "recovery" tab.
Verify that the recovery installed is indeed TWRP (TeamWin recovery). If it isn't stop, and get TWRP before continuing.
Once your recovery pops up, select "factory reset", and swipe.
Then, select "install" from the menu that pops up, navigate to the folder labeled "downloads" and select the ROM file, and then select "add more zips", then select the gapps (google apps) file.
After that, swipe the little bar to start flashing, then after it's finished, select "reboot system".
Once the thing has properly booted into the setup screen, set it up, and restore your data.
zeneleven said:
e) And what more can i do to my device to achieve it AWESOMENESS
Click to expand...
Click to collapse
Install M-Kernel and Trickster Mod (app).
Install Nova launcher.
Install fdroid (for freedoms).
Install MX Player.

Ive already re-flashed with XenonHD's latest update i think, and yeah its on 4.2.2. and still, got the lockscreen problem which i solved by changing the lockscreen orientation, locking it to portrait.. and got more error like "Apollo" and its launcher "has stopped" something.. and the voice dictation, exits when being used, wherever im in..
Now, im planning to switch to Cyanogenmod for 4.2.2, since it has few themes available.
About Kernel? Can someone help me how to do that? a great guide will be greatly appreciated, done searching and cant find it, i swear.
Thank you so much in advance

Why is my phone unable to run ROMs based off lineage is.

I have the H918 T-Mobile model and have tried resurrection, lineage, and aokp and all have booted to black screen and if i wait a while it finally allows me to start signing in. I get a ton of lag while doing this and then my phone crashed and goes to black screen until I pull battery and reboot. Also after each new Rom flash and setup when i go into twrp I get this. I'm not sure what I need to do to get lineage roms to work and boot properly without lag or black screen.

I'm not sure I can provide the needed advice, but when you see that screen are you choosing to keep system read only, or are your swiping to allow modifications?
Sent from my LG-US996 using XDA-Developers Legacy app

DOBBY0 said:
I have the H918 T-Mobile model and have tried resurrection, lineage, and aokp and all have booted to black screen and if i wait a while it finally allows me to start signing in. I get a ton of lag while doing this and then my phone crashed and goes to black screen until I pull battery and reboot. Also after each new Rom flash and setup when i go into twrp I get this. I'm not sure what I need to do to get lineage roms to work and boot properly without lag or black screen.
Click to expand...
Click to collapse
Before installing lineageos or resurrection remix or aokp, go into recovery, allow modifications. Then earse cache, dalvik, data, internal storage, and system (erase them twice). After that go inro the reboot option and press reboot to recovery once again. Then, install the desired rom and reboot.

DOBBY0 said:
I have the H918 T-Mobile model and have tried resurrection, lineage, and aokp and all have booted to black screen and if i wait a while it finally allows me to start signing in. I get a ton of lag while doing this and then my phone crashed and goes to black screen until I pull battery and reboot. Also after each new Rom flash and setup when i go into twrp I get this. I'm not sure what I need to do to get lineage roms to work and boot properly without lag or black screen.
Click to expand...
Click to collapse
Did you wipe data, doing so will unencrypt it. So allow modifications to system and format Data (doing so will wipe it completely dry so have a computer nearby), then add back the ROMs and Gapps then flash!

OneDon said:
Did you wipe data, doing so will unencrypt it. So allow modifications to system and format Data (doing so will wipe it completely dry so have a computer nearby), then add back the ROMs and Gapps then flash!
Click to expand...
Click to collapse
Okay so I got it to boot and was going through the setup and it froze. Went black screen and now I cannot turn on my display. Have to pull battery

I wonder why there are no guides or stickies for this kind of stuff. In the Samsung forums, there were, and I didn't see near the problems with people trying to Root or add a ROM as I do over here.
Makes me very reticent about modding the phone. Seems you need to find multiple threads to get it done right.
I am assuming that the process outlined earlier in this thread is not outlined in the instructions for Lineage.

https://forum.xda-developers.com/showpost.php?p=77177529&postcount=6
Phoenix591 said:
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
lineage-14.1-20180721-UNOFFICIAL-h918.zip.md5
When lineage 15.1 becomes official the h918 builds will be aimed at post10p. x86cpu is currently doing unofficial builds for both.
Click to expand...
Click to collapse

EFG5 said:
https://forum.xda-developers.com/showpost.php?p=77177529&postcount=6
Click to expand...
Click to collapse
Any reason why you're digging up posts from 2017?
Sent from my LG-H910 using XDA Labs

Bootloop after themed unrooted system with Andromeda/Substratum

Hi guys!
I'm looking for answer how to restore latest stock system on my dual sim version, unrooted with locked bootloader (no modification).
I've just updated my overlays with andromeda/substratum and unfortunately got a bootloop. Have no idea how to remove that overlays causing bootloop. Have no TWRP recovery so I can not flash the rescue zip. Is it possible to get in to the TWRP with locked bootloader?
Any advice or help will be appreciated.

kamyk70 said:
Hi guys!
I'm looking for answer how to restore latest stock system on my dual sim version, unrooted with locked bootloader (no modification).
I've just updated my overlays with andromeda/substratum and unfortunately got a bootloop. Have no idea how to remove that overlays causing bootloop. Have no TWRP recovery so I can not flash the rescue zip. Is it possible to get in to the TWRP with locked bootloader?
Any advice or help will be appreciated.
Click to expand...
Click to collapse
While it's booting, rebooting, hold volume down key till you feel a vibration..... It'll start in safe mode which will allow you to uninstall the faulty theme.... Also, for Substratum users here, which theme did what it did? I never had a problem with substratum .

Thanks for reply.
The unfortunate theme was //substweaks//.
I've put the phone in to the safe mode but it stuck on black screen with description Safe Mode.
Finally I've disabled that freaked overlay via ADB and now I'm good to go ?

kamyk70 said:
Thanks for reply.
The unfortunate theme was //substweaks//.
I've put the phone in to the safe mode but it stuck on black screen with description Safe Mode.
Finally I've disabled that freaked overlay via ADB and now I'm good to go ?
Click to expand...
Click to collapse
Subtweaks works just fine.... There's no problem with it. So weird. Might be something in conflict with that...
Sent from my XZ Premium using XDA Labs

Yup. Apparently there must be a conflict with Swift Dark. Was good till Swift applied and phone returned to life when Subtweaks disabled via ADB

Take a look at Swift Black. It's beautiful on this phone

Just checked that theme again. Mod for center clock and 4G switch to LTE causing problem. Anyone can confirm?

Substratum

Okay I have the T-Mobile version of the OnePlus 6t and the bootloader is unlocked and it's rooted running the stock ROM. I installed substratum but nothing works I put busy box in also just in case. Will substratum work with the stock ROM?

yep, works just fine, with no busy box needed

I noticed subs stopped working for me after I clean flashed stock OOS.
Haven't changed anything but only a handful of overlays show up after a reboot

you know you have to be rooted for Subs to work on this phone..

wase4711 said:
you know you have to be rooted for Subs to work on this phone..
Click to expand...
Click to collapse
My phone is rooted and none of the overlays work. Do I have to use an older version of substratum?

Flash1959 said:
My phone is rooted and none of the overlays work. Do I have to use an older version of substratum?
Click to expand...
Click to collapse
Oh and it's rooted with magisk 18.1

mine is too..
not every subs theme will work on this phone; try Valarie, I really like that one, and I know it works on this phone
remember, you first "build and enable" the things you want to theme, making sure you are using mods that work on 9.0.
then, after you build the theme, you reboot; once it boots, go back into subs app, and "enable" everything you just built; the changes should happen right then, and the theme should be installed and working.
More info in the Subs thread here on XDA, but that works for me every time..

Yap, follow the steps what @wase4711 says. Before that, make sure that you haven't installed any Magisk Doze Modules, this may affect is enabling the theme. If you have already Installed any Magisk modules, try by Uninstalling them and then apply the Theme, Once you have applied the theme, you can Install the Module's back. You can also use Pitch Black Theme, and It also works perfectly with OP6T.