yashsingh1/xdaforums huggingface dataset:
[SuperSU] ldeveraux:
Uninstall Xposed?

What exactly do I need to do to uninstall Xposed? I'm on CM13 with systemless SuperSU as well as systemless xposed with Magisk framework. I need to get SUhide installed, so I uninstalled the xposed framework temporarily. I'm a bit confused, since after doing that in TWRP, I still get the "/system/bin/app_process32_xposed found". Do I also need to uninstall the Magisk framework? Or the Xposed app itself? I thought disabling the framework was sufficient.
[SuperSU] Portgas D. Ace:
Best way is to flash the uninstaller.zip. Otherwise wipe system, cache and dalvik and re-flash your ROM.
[SuperSU] ldeveraux:
Flash the xposed uninstaller? I did that in TWRP but still get the error message. That's why I thought I might need to go a step further? I'm not wiping my system, but I could reflash the ROM. Not sure if that would solve the problem though.
[SuperSU] Portgas D. Ace:
The strange thing is that there is a file in the system patition. I thought that the system partition isn't touched by the systemless Xposed, but maybe this is some kind of link. Try to manually deleting the "/system/bin/app_process32_xposed" file via recovery and try again.
[SuperSU] matmo10:
I was in the same exact position. grep_i's instructions fixed it for me. Did you ever end up getting any version of suhide to work with PureNexus 7.1.1? I'm trying to get Android Pay to work again, thats why I tried to install suhide v0.55.

I have PureNexus 7.1.1, and am rooted via Nexus Root Toolkit. I currently have SuperSU v2.79 . Any ideas, anyone?

Thanks grep_i, you saved me.
[SuperSU] tsuttie99:
Not yet unfortunately. I was still recovering from the trauma of thinking I had to reinstall haha. I copped out and drove across town to get a type c cable. Copped and ran uninstall zip.

As for AP on pn 7.1.1... I have heard the magisk route might work. But I have also heard safety net was updated and that it will not work now. It checks for unlocked bootloader now. Some kernels hide this from SN but since the update it will still fail if rooted.

My reason for su hide was similar. My banking app has NFC payments but it's not Android pay. I was kind of hoping that the app was just doing some basic root checks and not using safety net for verification.
[SuperSU] shubham399:
I am using superSuv2.79

With rootswitch

Still unable to Authenticate in Pokemon Go

Cm14.1 Rom
[SuperSU] EViollet:
suhide doesn't work on CM14.

And without suhide, you won't be able to hide SuperSU. So, Pogo, no go...

Switch back to CM13, or use Magisk and phh superuser. I've read that that combo works.

Regards
[SuperSU] Fenny:
With CM14/AOSP, revert the commit I posted earlier in this thread. After successful build without it suhide works fine.
[SuperSU] EViollet:
Of course, that is another solution. But, unfortunately, rebuilding a ROM isn't easy for everyone.

Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk
[SuperSU] pkelly517:
Then maybe that request shouldn't be in a development experimental unsupported thread?
[SuperSU] Bryanx86:
Hey, i recognize your name from the ABCrom thread, have you been able to get suhide working on ABCrom? And if so, how? Thanks
[SuperSU] zzzhead:
Does anyone know where should I go to I order to edit the mount parameters during boot time, to mount su.img as rw.?

I can remount it using terminal, says that /dev/block/loop1 is mounted read only
[SuperSU] jcmm11:
/su is mounted rw by default. Checked script and see image attached.

If it's read only you remounted it that way.
[SuperSU] zzzhead:
Mine is mounted as ro. Where can I go to edit the mount script?
[SuperSU] jcmm11:
/sbin/launch_daemonsu.sh

And if yours is read only you did it. The script mounts it rw.
[SuperSU] zzzhead:
Upon future investigation, su.img is mounted as rw. However, upon any operations to any file in the mount directory /su, example modify suhide.uid, the mount will change to ro, and changes are not saved.

I'm guessing this could possible be due to me restoring a ext4 nandroid on a f2fs partition, do you have any thoughts on this?
[SuperSU] magnum73:
A quick question...

Can I safely update supersu app from the google play, if I have it systemless installed, together suhide ? I have a oneplus 3.
[SuperSU] Chainfire:
Perhaps it is corrupt? It should self heal every boot, but you can try running e2fsck manually. If that also fails, try removing it entirely, and re-rooting.
[SuperSU] zzzhead:
Thnx for the suggestion. Re-rooting makes me lose root a few seconds after boot, but I can't really point it to magisk or systemless supersu.

Could you elaborate more on the e2fsck command that you mentioned, I would give that a shot!
[SuperSU] tdurdenn:
I wish I could use this with PHH Superuser, so I could keep root enable and xposed.
[SuperSU] mariopo3:
Which version of Oxygen OS you have?

Becouse I have Oxygen OS 3.2.8 with November security patch and when I flash Suhide 55.0 the phone don't turn on, I waited 2 hours and nothing so I uninstalled Suhide and my phone works fine, if you can write the steps too install the zip fine
[SuperSU] pkelly517:
I stopped trying to get it to work a few months ago. See post #2.

I still follow this thread just in case Chainfire figures out a Google proof way to hide root. I'm not hopeful.
[SuperSU] Rhoban:
There won't be any sure method to hide root from SafetyNet.

Google wants it to be very secure, so they will patch everything our devs may come up with.
[SuperSU] Fenny:
En garde.
[SuperSU] buttie:
Just a PSA: suhide causes bootloop on latest supersu (v2.79 SR1).
[SuperSU] EViollet:
Erm... No.

I'm running suhide AND SuperSU 2.79 with absolutely no issues.

Your problem, most probably, comes from your ROM. As stated at least once a day, suhide is NOT compatible with current ROMs that include the latest security patches (starting from November). And that is valid for Marshmallow AND Nougat.

Regards

EnvoyÃ© de mon ONEPLUS A3003 en utilisant Tapatalk
[SuperSU] buttie:
You mean 2.79 or 2.79 SR1?

That's not entirely true, I'm running suhide 0.55 on HTC One m9 with latest security patch (December 1st) and SuperSu 2.79 (stable not SR1) without any issue.
[SuperSU] pkelly517:
Yup.

And for the 'honor' of using Android Pay, the cat /mouse game isn't worth it. I can pull out a credit card just as easy, and I have more confidence that it will work.
[SuperSU] ldeveraux:
I think I got it installed by reflashing the ROM, uninstalling SuperSU, installing SuperSU systemless, flashing SUhide. Then I rebooted and reinstalled xposed. Seems to work!
[SuperSU] magnum73:
I have an older version of oxyGen installed, version 3.2.1. And also suhide 54.0 I think...
[SuperSU] EViollet:
Actually, I misread, and was talking about 2.79, NOT SR1. Haven't tried that version. Sorry about the confusion.

However, as for suhide with the security patches, I don't see how that's possible. From what I understand, you have to remove at least some of the patches from the ROM in order to get out of the bootloop.

Regards
[SuperSU] buttie:
I'm pretty sure HTC did something in this manner, Stagefright Detector shows zero vulnerabilities though, so there is that at least.
[SuperSU] Damfino2000:
I also had a boot problem - this was my first attempt installing suhide. I have a Nexus 6 the latest PureNexus w/December patches (12/15/2016), latest TWRP (3.0.3.0), latest SuperSU (2.79SR1) installed systemless, and installing the latest (0.55) version of suhide caused it to be stuck on the booting animation indefinitely.

Installing the suhide-rm zip got my phone booting again. So there appears to be something going on with that combination. I don't have any other odd things like Magisk, Xposed, etc.
[SuperSU] Alkalyte:
I can't seem to get xposed installed and suhide doesn't seem to be working after flashing. No bootloop or anything it just doesn't work.
[SuperSU] fw85:
Well since [MENTION=631273]Chainfire[/MENTION] seems to be completely uninterested in patching this tool for no apparent reason, is there perhaps any experienced developer out there who'd be able and willing to quickly fix suhide for the latest security patch?

I'm by no means an expert, so please excuse my ignorance, but how difficult do you reckon it might be to fix this? I guess even if there was someone, they'd probably have to get Chainfire's permission first, assuming he's not just going to ignore them.

Surely, some of you would already like to reply with the argument that "it's a losing game" etc etc, yet I believe it's worth looking into if you got the time and the skill. The same methods have been working for almost 3 months now, which makes me think that Google has stepped down a little in their effort to combat all this. 3 months ago, they'd update SafetyNet pretty much every week, but not anymore.
[SuperSU] Ch3vr0n:
Then you need to look a bit closer. I think he said a few posts ago that it's NOT a case of disinterest but LACK OF TIME! Right now he's focusing on pushing a new FlashFire update.

Sent from my Nexus 6P with Tapatalk.
[SuperSU] Neffy27:
Exactly what happened to me just now. Same phone, recovery, rom except running Stable 2.79.
[SuperSU] Alxoom33:
I don't think your post is correct or appropriate on [MENTION=631273]Chainfire[/MENTION]'s thread.
[SuperSU] Rhoban:
So if the last methods are still working, why exactly do you need an update for this?
[SuperSU] apophis9283:
As developers they have that right. The right to not do it when you snap your fingers. He has other projects a life, you know being human. You have XDA twisted. It doesn't work like that
[SuperSU] vandyman:
Very rude!

Quit playing with your Pokemon.
[SuperSU] fw85:
Sure, don't get me wrong, I'm not trying to force Chainfire to do anything here, I'm in no position to do that. Also, it's not like I'm ungrateful for his work either, I even bought SuperSU Pro to support him.

I was just confused as to why he would abandon this project, when it's so useful to so many people. And if he doesn't want to continue, why not allow some other experienced developer to quickly patch this (assuming there would be someone willing to do that)? Like Fenny for example, who already figured out what causes the bootloop.

Because I'd like to update my system and any new update is going to break suhide. I also prefer this method to Magisk, since it easily lets me use and hide xposed alongside root as well. I'm sure I'm not the only one who'd greatly appreciate if someone took a little bit of time to patch this tool.
[SuperSU] Rhoban:
SuperSU and Rootswitch works fine for me. I'm not sure it can actually hide Xposed successfully. But I'm using a 7.1.1 ROM with the December security patch and can play PokÃ©mon.

Not sure about Android Pay.

Maybe he will plan updating it at some point. Otherwise he probably would have labeled it as EOL or something.
[SuperSU] noobhero:
Cant expect much haha.

There are always pple who are full of self entitlement
[SuperSU] vandyman:
I understand .

I want a million dollars so can someone please work for it than give it to me?

Quit playing with your Pokemon.
[SuperSU] Mikulec:
Whixh SuperSU? Looks like you are the only one so far.
[SuperSU] Rhoban:
I believe it is 2.78 SR5.

And I'm not the only one, there are several other people who use it. But the method to make it work has been buried between other discussions.

This approach requires some patches. I can't attach the patches myself because the mobile site version is an ass.

But you can find the patches, and the procedure, at post #5055.
[SuperSU] Alkalyte:
Okay so this just is not working for me and i tried to just uninstall suhide and xposed by topjohnwu and clear art/dalvik then reflash my old xposed by wanam and now my xposed installer says xposed v85.1 by wanam installed but not active check logs for details and it seems to me that both topjohnwu and wanams xposed are installed somehow. How do i rid of myself of xposed entirely so that i can reinstall fresh? Thanks for any help.
[SuperSU] Rhoban:
If you really want to start fresh then I'd suggest a clean flash of your ROM too.
[SuperSU] zeratos:
Does suhide still makes phones laggy as hell? I recently switched from the motto g first gen to the p8 lite and want to try it but after searching through the thread I found purple still complaining about it.
[SuperSU] grep_i:
If you had everything SYSTEMLESS than it would be as easy as removing folder

/su/xposed

Or reinstall Supersu.

Clearing cache and dalvik are not necessary in these cases as there is none due to suhide, removing suhide will automatically trigger the rebuild of the caches which results in optimization apps at startup.

If I'm not mistaken SuperSU also clears dalvik after flashing but this I'm not absolutely sure of as I mostly flash multiple flashable zip files in one go.
[SuperSU] Rhoban:
I think "laggy as hell" is an exaggeration.

I've used suhide on my Samsung Galaxy S4 and did not see any performance degradation.
[SuperSU] jrk190:
Weird issue.

I added my card to Android pay, yet I still get unsupported device when I try to pay, even when it passes green.

Any clues?
[SuperSU] mobileman88:
What device, rom, kernel and root are you using?
[SuperSU] jrk190:
Nexus 5X, elementalx, Pixel ROM with rootswitch and the root method in post 5005 (I think it's that post...)
[SuperSU] mobileman88:
Suhide does not work with any of the roms after November as it is not compatible. I am not familiar with pixel Rom. Is it a custom 3rd party rom?
[SuperSU] osm0sis:
If people direct link or download the attachment directly without reading that's their own fault. The post it is attached to pretty clearly, and always, explained what it was for.
[SuperSU] rhiome:
Thank you so much for this post. I was using version .16 so I followed your advise and uninstalled it. Then I flashed .50 and SuperSu 2.78 and my whole phone was lagging out and not responding. I waited for a long time until the not responding errors came pooing in. Super su would not go past a black screen. So I guess there is more waiting for me. Thanks again. If anyone has additional suggestions I would appreciate them.
[SuperSU] voland66:
[MENTION=1073033]rhiome[/MENTION] Just checking: Your are saying supersu 2.78; it should be 2.78SR1 (service release one)
[SuperSU] wilflare:
Nexus 6P with Android 7.0 (Nougat)

SuperSU 2.79SR1

latest suhide 0.50

- working Pokemon GO

- working Android Pay (yet to test but adding cards work)
[SuperSU] Flippiej:
It's not working on my rooted stock rom of my OnePlus 3.

Flashed SR1 SuperSU a day before suhide, then yesterday flashed suhide with the SR1 SuperSU after it.

Got Pokemon Go working, but afterwards found out that root is actually not working anymore at all and SuperSU wants to update its binaries. (which attempts fail)
[SuperSU] nefescalanadam:
It's not working on my Cm13 with Nexus 4..

Flashed first SR1 then suhide other then SR1 again.

Pokemon Go isnt work, root is actually not working anymore at all and SuperSU wants to update its binaries. (but cant)
[SuperSU] Super-Veloce:
How?

I flashed Note 7 rom for my Note 3.

Went into SuperSU app and uninstalled superSU

I could play Pokemon Go

Now I'm trying to flash latest supersu (SR1-SuperSU-v2.78-SR1-20160915123031) and after that I tried to flash suhide and got "fatal error su can not be mounted" ...
[SuperSU] dev_freak:
How do I flash it?
[SuperSU] ianmacd:
There's no need to reflash SuperSU 2.78 SR1 after flashing suhide.
[SuperSU] Opticuhl:
Thanks for the tip, I'll give it a try.
[SuperSU] dratsablive:
You need to reflash SU after flashing SUHide, otherwise you will end up with a boot loop per [MENTION=631273]Chainfire[/MENTION] instructions.
[SuperSU] blue4you:
I try suhide 0.50 with my Xperia Z5 Compact with stock rom and patched kernel with rootkernel V5.0 (without root and without busybox)

I used SuperSu 2.78SR1. Flash first superSu 2.78 SR1 zip -> restart -> flash suhide050.zip und superSU2.78 SR1 zip again.

Root is working , su-hide also but Titanium Backup didn't get root and Root Explorer starts only with a with screen.

I know that root is available because Script Manager get root access.

Android Pay also works!

But my bankig app - VR-SecureGo crashes.
[SuperSU] osm0sis:
No, [MENTION=7187684]ianmacd[/MENTION] is correct. Now that suhide uses su.d instead of custom_ramdisk_patch.sh you don't need to reflash SuperSU after. Chainfire was just in a hurry and hasn't had the chance to update the OP for v0.50 yet.
[SuperSU] desztan:
Is there an app to find out the UID of the packagename. I'm not good at programming.
[SuperSU] racing_md:
I used Package Name Viewer 2.0 by csing. Does what it needs to do with a clean ui. I also wanted to echo that it does not seem necessary to flash SR1 after flashing su .5. Originally I flashed SR1 su .5 then SR1. I had root but android pay didn't work. I went back and flashed su .5 again and everything is right in the world. Stock 6p 6.0.1.
[SuperSU] bobby janow:
I think you can see it under /data/system/packages.list but I'm not entirely sure. Confirmation would be needed.
[SuperSU] desztan:
I could see the packagename but not the UID...
[SuperSU] racing_md:
My appologies. I didn't read your post closely enough, I missed the part about the UID. I do not know of an app that also gives the UID. I had to do it through a adb shell on the computer. Have you used adb before?
[SuperSU] desztan:
Yes. I use terminal emulator...
[SuperSU] tepar:
You can try apktool by polartouch.se, just search it on playstore. :good:
[SuperSU] adrman:
I'm seeing the same result on stock 7.1.1, Franco kernel with root switch. Safetynet passes, able to add card, but failed transaction. AP is tripping on something else. At this point, it's just much easier and more reliable to take a card out of my wallet.
[SuperSU] jrk190:
It's basically the pixel system ported to the Nexus 5x.

---------- Post added at 06:00 PM ---------- Previous post was at 06:00 PM ----------

Yeah, it's weird that everything else passes. I'm tempted to go back to stock but I don't think I will yet.
[SuperSU] grep_i:
It's working with my ROM and December patch, device Nexus 5
[SuperSU] zeratos:
Well, it did made my moto g "laggy as hell", opening xda labs or pokealert made the phone run out of memory when I had suhide installed, opening pokemon go made the phone restart sometimes, without it the phone runs fine. ._.
[SuperSU] Hannibal226:
U wanna say that u use an own modified Rom or it should generally work with correct steps?

I only red something about the script which should help, but also read not on hammerhead...

Can u tell something more please?

Thanks & CHEERS!
[SuperSU] grep_i:
It's working as is, without modifications,

just december stock rom,

supersu 2.79,

ElementalX 6.27,

Xposed 86.1 romracer systemless,

suhide 0.55 & root switch 1.3.3.2
[SuperSU] zerosource:
is it nougat 7.0 or 7.1.1?
[SuperSU] grep_i:
Stock rom nexus 5 is 6.0.1 dude, I'm not messing with custom roms as I do not find them good enough compared to my stock rom.
[SuperSU] -Deco-:
Oh right so you assume that your assumptions on exploitations are correct and that it's simply a "quick fix". I'll tell you what, since you seem to think it's so easy to bypass a security update why don't you do it instead of heading onto XDA and asking others to do it for you. Just because you think something is happening doesn't mean it is happening, I can certainly assure you that Google are not letting their guard down and won't be anytime soon; too many corporations and apps now depend on it's security. Stop making assumptions about what you think is happening and learn to respect other individuals; [MENTION=631273]Chainfire[/MENTION] was not forced into making this and is neither forced to update it either, just because you want it updated doesn't mean he's going to, you are neither familiar with his current situations and/or future plans/situations so it does not give you the authority to make assumptions that he has abandoned this project. What he provides is what you get, not what you want.
[SuperSU] Rhoban:
That's a pretty old phone and that's probably why.
[SuperSU] fw85:
Wow take a chill pill. You should've probably read my previous comment before writing all this. I wasn't forcing him to do anything, I was just disappointed to see this project become abandoned, which it clearly has been, for the time being.

Why don't I do it myself? I would, but as I mentioned, I don't have enough experience in android development yet. And even if I could, I'd probably need his permission first. And I'll let you be the judge of how easy/hard it is to fix for everyone, since [MENTION=522448]Fenny[/MENTION] already figured out a patch for Pixel devices.
[SuperSU] -Deco-:
Abandoned? Oh, so I assume he has abandoned other projects such as CF-Autoroot as it hasn't been updated in a while, doesn't seem like it. Chainfire operates many projects; you can't expect them all to be updated on a regular basis. I was stating that you should do it yourself due to your ignorance in that this project has been scrapped/abandoned let's ask someone else to do it.
[SuperSU] zamula:
Have you tried opening Android Pay, clicking on the option to add a credit card, and then while it's still on that screen, use AP for the transaction? If I don't do that first the transaction fails, but using the above steps it works fine. My environment is a 6.01 based ROM with root switch, Xposed, and suhide.
[SuperSU] adrman:
No, I haven't. Perhaps I'll give it another go after the January security update drops. Thanks.
[SuperSU] Hannibal226:
So I fully unroot my phone and tested again.

Same problem as before.

BUT u r running nougat, too? I guess it's still MM right, because for now I don't know a way to get xposed working on Nougat (even it's planned)

CHEERS
[SuperSU] Nomelas:
Getting a continuous loading at boot after flashing this and supersu 2.79 and even SR1.

This is after updating my rom to the latest CM Snapshot with December security patches.

Phone: OnePlus One

Rom: SultanXDA's custom cm13

I've removed everything else such as magisk and xposed but no help
[SuperSU] grep_i:
I think you missed my post #5390 2 posts after yours where I explain that stock rom Nexus 5 is 6.0.1 MarshMallow.

Don't know anything about Nougat.

I wish you the best with figuring it out.
[SuperSU] Hannibal226:
Sorry, yeah I missed that u answered it afterwards, my fold.

CHEERS
[SuperSU] DIXES:
Excuse me, an SELinux is always Permissive kernel still works now? Thanks.
[SuperSU] Rhoban:
Probably. I'm using Rootswitch now, and this sets selinux to enforcing when root is off.

---------- Post added at 06:37 AM ---------- Previous post was at 06:35 AM ----------

It has been said many times that suhide will bootloop on ROMs with November, and later, security patches.
[SuperSU] BlackDragon381:
I use suhide 0.55 and RootSwitch 1.2.4, but pokemon go 0.51 still see root, what i do wrong?
[SuperSU] grep_i:
Maybe if you update your version of root switch, I believe the most recent version is 1.3.3.2
[SuperSU] BlackDragon381:
I don't know that there is a newer version of rootswitch, pokemon now works, many thanks!
[SuperSU] tsiftsism:
So, if we are stuck into bootloop the only way for our device to boot is to full wipe and boot the system as it's the 1st time?

Or is there a way to delete the suhide from within TWRP?

I flashed the suhide-rm but it didn't help.
[SuperSU] Rhoban:
You can try flashing a different kernel and see if it helps. Otherwise, doing a clean install may be the only option.

But I don't know much about suhide, so maybe someone with more knowledge can correct me.
[SuperSU] buttie:
Try [MENTION=6312707]Pwnycorn[/MENTION] tip and if it won't help you, try to re-flash few versions of SuperSU: 2.79 SR1, 2.79 and 2.65.

BTW: Wipe also cache and dalvik/art cache partitions in recovery - it's almost never a culprit in case of bootloader loop but won't hurt.
[SuperSU] grep_i:
No that's not the only option you have when stuck in bootloop, but by far the easiest if you don't really know what your doing or what to do.

Look at this post

Maybe it can help you too with your problem of not getting suhide removed.