I have tried rooting using both Magisk and Supersu. I've not had luck passing safety net checks. I've uninstalled Magisk. The specific problem I'm having is that I'm trying to remove all the supersu files. When I get into recover mode using twrp, I can see a /supersu folder. I delete it, or at least it acts like it deletes it but when I reboot into recovery, it's still there. When I use a root explorer app, the folder is nowhere to be found.
rwmappraisal said:
I have tried rooting using both Magisk and Supersu. I've not had luck passing safety net checks. I've uninstalled Magisk. The specific problem I'm having is that I'm trying to remove all the supersu files. When I get into recover mode using twrp, I can see a /supersu folder. I delete it, or at least it acts like it deletes it but when I reboot into recovery, it's still there. When I use a root explorer app, the folder is nowhere to be found.
Click to expand...
Click to collapse
Have you wiped cache after removing the supersu files? Any time you remove apps/files from /system, you have to wipe cache and/or Dalvik/ART cache or it thinks it's still there when it isn't.
Why didn't you just use SuperSU's app settings to unroot and uninstall SuperSU then use Magisk?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
use the unsu script and flash a unrooted boot.img from your rom
Try kingroot
Sent from my SHV-E210S using Tapatalk
Related
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
I know about this solution: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
And I know about Dr. Ketan's script to make SuperSU work with S6.
BUT, his script makes the phone restart on its own every so often. And when I try to unroot via the SuperSU app I get a bootloop. Wiping cache or Dalvik doesn't help.
So my question is: how to make S health work, while at the same time being able to get OTA updates?
AmarganthAmaranthine said:
I know about this solution: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
And I know about Dr. Ketan's script to make SuperSU work with S6.
BUT, his script makes the phone restart on its own every so often. And when I try to unroot via the SuperSU app I get a bootloop. Wiping cache or Dalvik doesn't help.
So my question is: how to make S health work, while at the same time being able to get OTA updates?
Click to expand...
Click to collapse
Use magisk, but you'll need to wipe and reinstall whatever rom you are using
Chrisaa63 said:
Use magisk, but you'll need to wipe and reinstall whatever rom you are using
Click to expand...
Click to collapse
Nope, Magisk doesn't work. I can't edit build.prop file with magisk, despite being successfully rooted and giving root browser and es file explorer root permissions.
The only solution I've found thus far is rooting with the Dr. Ketan script and then after editing the build.prop file reflash stock firmware without wiping data. This isn't a great solution but it works for now.
AmarganthAmaranthine said:
Nope, Magisk doesn't work. I can't edit build.prop file with magisk, despite being successfully rooted and giving root browser and es file explorer root permissions.
The only solution I've found thus far is rooting with the Dr. Ketan script and then after editing the build.prop file reflash stock firmware without wiping data. This isn't a great solution but it works for now.
Click to expand...
Click to collapse
There is one easy solution! If any Galaxy S6 user setup S health on their device and then they backup S Health application data via Samsung Smart switch on pc and then that person share his S health backup data file with us on this forum then we will be able to restore S Health data via smartswitch!
And after that we will be able to use S health though we have tripped knox!
Someone please help us!
AmarganthAmaranthine said:
Nope, Magisk doesn't work. I can't edit build.prop file with magisk, despite being successfully rooted and giving root browser and es file explorer root permissions.
The only solution I've found thus far is rooting with the Dr. Ketan script and then after editing the build.prop file reflash stock firmware without wiping data. This isn't a great solution but it works for now.
Click to expand...
Click to collapse
I have magisk installed and rooted through that. Also hidden magisk and S health works fine? I've just downloaded it..
I was able to get an backed up S6 version, installed the last 4.8.1.something from APKmirror, restored the backup to my S8+, and allowed S Health to update using the Play Store.
Made sure all Samsung Health related apps are blocked in MagiskHide. Works, although I cannot reset the userdata in-app (to remove the donor's personals and fitness results), or else it will complain about root again.
Thanks though!
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
bsd1101 said:
I want to switch from supersu to superuser, and having an interesting problem that supersu somehow covered up. I have a Nexus 5x running the stock rom. With every months upgrade I would flash using fastboot, go into twrp recovery before first full boot and remove a bunch of unneeded applications in /system/app. When I would boot up those applications would be gone. Somehow this isn't the case with superuser. I can still go into recovery and remove them, but when I boot up all the applications are still in /system/app. If I go back into twrp they are still shown as being missing. I've tried installing es file explorer, but it's unable to delete the applications once the system is up. remounting /system doesn't work either. Any help?
Unrooting supersu caused all the applications to come back; so does supersu not really delete them either, but somehow prevents them from showing up following the recovery scheme or something?
Click to expand...
Click to collapse
You aren't doing something right or you don't have something setup correctly. With root, you should be able to unintelligible them completely.
When you removed them, did you wipe cache and dalvik/ART cache before rebooting? If not then the system probably still thinks they are there because they still have data loaded into cache.
I recommend sticking with SuperSU, superuser doesn't work as well as SuperSU
Sent from my SM-S903VL using Tapatalk
I've been googling a bit more. As it turns out there are two system partitions for nougat; in nexus 5x and some other devices apparently. This became more apparent when the file recovery-from-boot.p; which I rename in order to prevent recovery from being overwritten is not renamed when booting the OS. Nougat apparently pulls the system files from somewhere else. So whatever Chainfire did makes it boot the same partition as visible in recovery. Fully unrooting brings all those apps/system partition back. Haven't been able to find a good post that tells me how to to circumvent this without SuperSU; or exactly how this works.
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
GphonePrince said:
I uninstalled Google Playstore using ES file explorer's root uninstaller and rebooted my phone. Then I reinstalled Google Playstore with an apk file (now shown as user app. The re-installation was success but the app keeps crashing after I tried to download an app with it.
I uninstalled Google Playstore in the first place because I encountered the "waiting for download" bug (apps stuck on that messages without downloading at all).
I cannot flash GApps in TWRP because it says /system partition not found.
I'm using Rooted Asus ROG phone, stock ROM 15.1630.1903.89, magisk
Please help
Click to expand...
Click to collapse
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Anytime you uninstall/remove system files and apps or anytime you reinstall/replace system files and apps, it is best to boot into recovery then wipe cache and dalvik cache then reboot. The reason why this must be done is because when you remove/add stuff from/to system, the OS is looking for stuff that is there when it shouldn't be or is not finding stuff that should be there but isnt.
Wiping cache and dalvik then rebooting allows the device to rebuild cache as it should be for what is currently in system.
The most effective fix with the least possible issues in your situation is to reflash your stock firmware then flash TWRP on the device again then root the device again using Magisk.
Next time, before you add/remove system files/apps, boot into TWRP and create a nandroid backup of your current ROM, then, if you encounter issues when you add/remove system files/apps, you can boot into TWRP and restore the backup and you'll be restored to exactly what you had before you added/removed the system files/apps.
The ability to create and restore backups via TWRP is the main purpose for using TWRP, the ability to flash ROMs and such is a minor secondary feature or purpose of TWRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
GphonePrince said:
Thanks for the detailed reply. I have re-flashed the stock ROM and re-rooted the phone now.
Now, I am just wondering why I am still encountering the "/system partition not mounted" error in TWRP for both (now and the previous time) rooting procedures? This prevents me from installing busybox and flash anything with TWRP.
PS: I am following the rooting guide here, since it is the most detailed one for newbies like myself. According the the screenshots shown in this guide, the OP also encountered the "/system partition not mounted" error in TWRP (system shown as 0MB, and before booting to system with TWRP, the message "no OS found" appeared). Hence I suspect his guide was not perfect despite getting root successfully. Mind having a look at the guide for me to see whether you could spot any missing/wrong steps please? (I know it is in Chinese but it does have loads of screenshots) I would really appreciate it. Thanks so much!
Click to expand...
Click to collapse
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Is your device an A/B partition device?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
GphonePrince said:
It's Asus ROG phone. seems like it is according to here: https://www.xda-developers.com/list-android-devices-seamless-updates/
Click to expand...
Click to collapse
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
That is the problem then, the process of rooting and flashing TWRP on A/B devices is very much different than how it is done on other non A/B devices.
Look for instructions on how to use TWRP on devices that have A/B partitions.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I will look into it thanks
Hi. I've installed and used magisk. then I've repacked magisk manager to hide it. then it has gotten removed. Now I've reinstalled magisk manager but it is not detecting magisk. Other root app are working.
lordkian2000 said:
Hi. I've installed and used magisk. then I've repacked magisk manager to hide it. then it has gotten removed. Now I've reinstalled magisk manager but it is not detecting magisk. Other root app are working.
Click to expand...
Click to collapse
It isn't as simple as reinstalling, you might have to reverse the process of whatever you did to hide it.
Or, you can try going to system settings>applications>magisk manager and wipe the app's data and cache then reboot the device.
Or, a step further would be to boot into recovery and wipe only the cache partition(s). Factory reset is not required, just wiping cache should work if the issue is due to conflicting cached system data.
By the way, anytime you add/remove/modify anything in/to/from the system partition or any app that is a system app, it is always best to boot into recovery and wipe the cache partition to remove any conflicting cached system data from before the addition/removal/modification.
Sent from my SM-S767VL using Tapatalk