Hello,
I have a Samsung Galaxy S6 Edge SM-G925W8 and had SuperSU root access and XPosed Framework installed. I am now attempting to remove all of it so that I can pass Google's safetynet helper test. I have tried numerous things, but the safetynet result is always:
SafetyNet Request: Success
Response Validation: Success
CTS Profile Match: False
I first attempted to remove Root by clicking "Completely remove root" within SuperSU. After doing this, Response Validation was false, which, after doing some research, I learned was caused by XPosed Framework. I then boot into TWRP recovery and flash the Xposed uninstaller. This causes my phone to boot loop, forcing me to restore a NAND backup to before I removed anything. I then try to flash the XPosed Uninstaller BEFORE removing root access and it runs successfully. After this, I use SuperSU to completely remove all root, which also runs successfully then give the phone a reboot removing the app entirely. This is when I receive the SafetyNet Helper response above stating CTS Profile match is false. I'm not sure how to fix this error.
Any suggestions would be very appreciated! Thank you
Edit: I have no idea why this thread appeared twice...sorry I can't seem to delete one of them
Er.. Any ideas?
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Is this to play PokemonGo? If so there's a mod with instructions. Unless that's what you're trying to do...you might need to flash factory images if Xposed is stuck. Backup your pictures and stuff and go back to stock then use that mod. It works well but no Xposed which is a good thing IMO!
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
vgplayer54 said:
Hi, thanks so much for replying! Yes..it is for pokemon go. Is the mod you're talking about the Magisk one? If so, that is what I originally wanted to do, but flashing Magisk caused my phone to be stuck in a bootloop and forced me to flash a NAND Backup. This was after first flashing the xposed uninstaller and uninstalling SuperSU. So I gave up on root...truth be told I don't use the root apps too much anyway so it isnt a big loss for me. I'm also already on Stock firmware so I'm not sure why I can't pass the SafetyNet Test. Do I have any other options than wiping my phone clean?
Click to expand...
Click to collapse
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
djdarkknight96 said:
Well only data will be gone you need a full system wipe....
Or go delete the su files...use file manager to find them but just delete in recovery using TWRP with the location you searched..I don't think you can search in recovery without the terminal but you can do it all in recovery.
or if you completely flash factory image you can just not root
Hope this helps!
#GottaCatchThemAll
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Hello, I attempted to use ES File Explorer to search both the system/bin directory and the system/xbin directories. system/bin does not have the "busybox" or "su" files in them, so I assume they were removed when I uninstalled SuperSU. /system/xbin however does have these two files, but I am unable to delete them. I get the error "Cannot delete file". I'm guessing this is because I've already unrooted?
I then opened the terminal in my TWRP Recovery, however when changing directories into the system folder, the terminal shows that it is empty. when using ls -la, only two files are there, both called root and neither can be opened. rm -r /system/xbin/busybox does nothing either, it claims there's no such directory. Any suggestions? or just wipe?
Related
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Hitman3984 said:
So, when I rooted I installed SuperSU and uninstalled Superuser.
Went through the steps to from the mod to get all apps into the multi view window. During the move odex services I got stuck in bootloop and had to re-odin the root image file.
Now that everything is set superuser is obviously the file back in charge of handling SU prompts from apps but for some reason it's not accepting/hearing them so anything I install that requires root is crashing.
Attempted clearing the SU data but it didn't help.
Is there anyway to fix this short of flashing back to stock then back to root?
Would mounting the system as writable, deleting SU and then re-flashing the root image fix the problem?
Basically I'm trying to avoid resetting my phone up to get this done.
Click to expand...
Click to collapse
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
EDIT: Nevermind I see that there are 2 different root methods and one uses SuperSU. Sorry
shojus said:
I thought for sure that SuperSU is what was used in that file but I guess there must be a couple out there? The method I used never installed Superuser...?
Click to expand...
Click to collapse
I used the file from imnuts, which used superuser and not supersu.
I went ahead and deleted superuser, xbin/su and am reflashing. hope this fixes the problem.
which worked until the phone randomly rebooted and got stuck in loop..
and it was either sdpeed increase or lbe privacy guard causing it.
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
Ive even removed superuser and installed supersu and doing the all apps mod was causing this issue.
I have a feeling it could be because I was renaming the services.odex file before replacing it.
Trying a direct overwrite was causing a non stop bootloop I couldn't get out of 4 seperate occassions.
droidstyle said:
jellybean works better with supersu...try the file mrRobinson created...ie the original root image.
Click to expand...
Click to collapse
100% agree! I have not used Superuser for ages... Far superior imo...
shojus said:
100% agree! I have not used Superuser for ages... Far superior imo...
Click to expand...
Click to collapse
after rooting I feel like the touch screen has lost some sensitivity. not sure if it's just me and the day or I'm just loco.
and what I mean specifically is when flipping through my home screens they like to snap back now and then.
Not sure why, but I'd like to share with the community that I have Android Pay working on my Nexus 6p, running stock Android version 6.01, build MHC19Q, with beta 2.71 of SuperSU by Chainfire.
I flashed the Factory image using fastboot, flashed TWRP 3.01 via fastboot, and then flashed SuperSU within TWRP recovery using the Beta 2.71 ZIP file from Chainfire
During the setup of Android, I added my Google Account, but skipped the passcode and nexus imprint setup. Before completing the setup process, I restarted back into recovery, and wiped the internal storage. Once I did that, I copied the SuperSU zip back on the device storage via my USB, and installed it again once more. I restarted my Nexus, followed the entire setup and created a PIN only, NOT the nexus imprint. Once I was into the Google Now Launcher, I opened Android Pay...added my payment cards without any error messages at all. I confirmed root access is available, and then set up my Nexus imprint. I then confirmed at POS terminal that Android Pay does in fact work.
Not sure if this matters, but I have not yet enable DEV settings access within Android as of this writing. Also, I have not encrypted the device, and did not elect to use a pin when starting the phone.
Can anyone else confirm this works for them?
Have u tried buying anything with it yet?
Sent from my Nexus 6P using Tapatalk
---------- Post added at 07:47 PM ---------- Previous post was at 07:38 PM ----------
And u right it lets u setup now while rooted!
Sent from my Nexus 6P using Tapatalk
systemless root I'm guessing? have you tried with modded system?
Systemless mode.
Haven't tried any other mod. Yes, I used the tap & pay at the local bodega.
Can you check your supersu settings and look towards the bottom it should tell you if it's a system app or if it's running systemless
Sent from my Nexus 6P using Tapatalk
pretty sure it's systemless. I mean, no system level root has made it to Android pay. but I'm just speculating
screenshot
I'll post a screenshot asap, but I did check and SU is installed system-less mode.
Also....
I use the app Secure Settings, and it does report that Root is not available (WITHIN the Secure Settings application) however, other apps, such as Adaway, can request, and are able to be granted, root access, with no apparent issues.
Here....
Ahh so it was systemless no surprise there but good to know.
Sent from my Nexus 6P using Tapatalk
You can do this by chmod-ing the correct folder. See https://www.reddit.com/r/Nexus6P/comments/4coc1e/easiest_way_to_systemless_root_while_keeping/
speedinfreaky84 said:
Not sure why, but I'd like to share with the community that I have Android Pay working on my Nexus 6p, running stock Android version 6.01, build MHC19Q, with beta 2.71 of SuperSU by Chainfire.
I flashed the Factory image using fastboot, flashed TWRP 3.01 via fastboot, and then flashed SuperSU within TWRP recovery using the Beta 2.71 ZIP file from Chainfire
During the setup of Android, I added my Google Account, but skipped the passcode and nexus imprint setup. Before completing the setup process, I restarted back into recovery, and wiped the internal storage. Once I did that, I copied the SuperSU zip back on the device storage via my USB, and installed it again once more. I restarted my Nexus, followed the entire setup and created a PIN only, NOT the nexus imprint. Once I was into the Google Now Launcher, I opened Android Pay...added my payment cards without any error messages at all. I confirmed root access is available, and then set up my Nexus imprint. I then confirmed at POS terminal that Android Pay does in fact work.
Not sure if this matters, but I have not yet enable DEV settings access within Android as of this writing. Also, I have not encrypted the device, and did not elect to use a pin when starting the phone.
Can anyone else confirm this works for them?
Click to expand...
Click to collapse
Why the extra steps, why not just flash TWRP, Flash SU as Systemless, then reboot and use Android Pay? That's how I was able to do it. And I didn't need the extra steps of deleting xbin_bind or chmoding the folder /su/bin (I am guessing SU did that for me.)
Way too many steps.
CFAutoRoot updated to 3.71 beta. 3.71 won't install xbin_bind. su/bin already chmodded to 751 in 3.71.
Don't even need TWRP. CFAutoRoot on factory stock and you're good to go with Android Pay.
You're probably right, I know a lot less about the process than you, so I wanted to make sure I provided as much information about what I did during setup that could replicate my success....since I wasn't really trying to get it to work since it didn't work up until now on a rooted device.
But cool man I'm glad it can be done so much easier.
zeezz said:
You can do this by chmod-ing the correct folder. See https://www.reddit.com/r/Nexus6P/comments/4coc1e/easiest_way_to_systemless_root_while_keeping/
Click to expand...
Click to collapse
No need to do that anymore. The supersu setup script has been doing that for the last 4 versions (starting at v2.68).
Google Wallet?
Didn't Google Wallet work on any rooted or ROM system? Android Pay is really annoying when it comes to this regard.
how do you get the 2.71 to install as systemless?
i downloaded the 2.71 from this Beta thread
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
and it wont install as system less. is there something that has to be done or another 2.71 zip that is converted to systemless?
TimesNeverWasted said:
Didn't Google Wallet work on any rooted or ROM system? Android Pay is really annoying when it comes to this regard.
Click to expand...
Click to collapse
Google Wallet did work, but is being phased out and replaced with Android Pay.
nextelbuddy said:
how do you get the 2.71 to install as systemless?
i downloaded the 2.71 from this Beta thread
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
and it wont install as system less. is there something that has to be done or another 2.71 zip that is converted to systemless?
Click to expand...
Click to collapse
It should install in systemless mode by default, are you 100% stock? With not modifed boot.img?
Sent from my Nexus 6P using Tapatalk
MrKaon said:
It should install in systemless mode by default, are you 100% stock? With not modifed boot.img?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
i was able to get it to work with help from another thread.
if have never been rooted before with systemless, then people that install 2.71 will get installed as SYSTEM by default unless you came from one of the original systemless ZIp files such as 2.56 which sets some parameters first that the new ones do not do by default.
I had to:
boot into TWRP and go into TERMINAL and then type
echo SYSTEMLESS=true>>/data/.supersu
Then
echo BINDSYSTEMXBIN=false>>/data/.supersu
Once that is complete then flash latest BETA SuperSU such as 2.71
that worked for me.
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.
Hi guys, today I updated via OTA to MIUI 10 9.2.21, after that I reinstalled magisk and adaway but when I try to apply it says there's not enough space in the partition, so I tried to relocate the host file to DE /data/data folder as told by the app but it doesn't work, the link doesn't create . So I read that the solution could be un install system apps, so I downloaded Titanium Backup but it doesn't seem to un install any app, tried an app remover root from play store and CCleaner and that didn't work either, tried to remove some things in the /system folder but the delete process always fails. Don't know what to do to get adaway working again, it was working fine before the update.
Thank you in advance
Happened to me too if you try to install using magisk manager inside of android it won't work.
You have to install magisk initially in twrp for it to work.
No, I always install magisk first. Then I install an adaway downloaded apk. It always worked except for this time with the not enough space on partition issue
Already deleted 2 system apps (Bugreport and notes) with the adb and command method
Srill, adways says not enough space in the partition
Don't know what else to do, if it needs more space or what
This solution works on Mi8:
1. In Magisk manager tap "settings/systemless hosts". It should install systemless hosts module. Go check it in modules to confirm it is installed.
2. Reboot device
3. Install Adaway and apply ad-blocking. It should work now.
zvonimirovich said:
This solution works on Mi8:
1. In Magisk manager tap "settings/systemless hosts". It should install systemless hosts module. Go check it in modules to confirm it is installed.
2. Reboot device
3. Install Adaway and apply ad-blocking. It should work now.
Click to expand...
Click to collapse
Yeah! It worked!
Thabk you so much!
zvonimirovich said:
This solution works on Mi8:
1. In Magisk manager tap "settings/systemless hosts". It should install systemless hosts module. Go check it in modules to confirm it is installed.
2. Reboot device
3. Install Adaway and apply ad-blocking. It should work now.
Click to expand...
Click to collapse
Was about to say the same good one mate