I'm currently running the stock SM-T310 4.4.2 build. I have my device rooted (verified by Root Checker Basic) and I have SuperSU installed via Play (SuperSU Free v2.4).
Yet every time I am in TWRP and attempt to flash a rom, the ROM install fails immediately and at Reboot, TWRP asks if I want to install/fix Root permissions. What is going on and why is there a discrepancy?
Related
I'm at a loss as to what is wrong. I flashed a prerooted stock version of KitKat and I think root was working. But now for some reason it doesn't work. I flashed the supersu zip (v1.80) via TWRP recovery but after rebooting, the SuperSU app doesn't even show up on my device. When I install manually from thr Play Store it's as if I'm not rooted. I've flashed the zip multiple times and I do not want to factory reset and delete all my data (especially since I really can't backup without root atm). Any ideas?
Edit: sorry about the post title typo. *flashing
Hi,
I have the Samsung Galaxy Tab Pro 10.1 (SM-T520) running on Android 4.4.2. Rooting did go well (had to reboot a few times before knox disabled). I tried root checker and its OK.
I then would install TWRP. I downloaded the latest version for my device (2.8.0.0) and tried to flash the IMG with Flashify.
It said complete and rebooted into Stock recovery! Something did go wrong.. I tried TWRP manager (app from app store) to install TWRP, but it wants BusyBox.
I tried to install Busy box but it said it had a problem with installation and said I could try another directory.
I did, and again the same error. I couldnt find the file busybox in system/bin nor system/xbin.
What might the problem be? Should I continue, or is my device unstable and might I brick it?
Edit: Or would Odin do the trick and flash TWRP properly?
This is common and someone should answer already!!
michael64142 said:
Hi,
I have the Samsung Galaxy Tab Pro 10.1 (SM-T520) running on Android 4.4.2. Rooting did go well (had to reboot a few times before knox disabled). I tried root checker and its OK.
I then would install TWRP. I downloaded the latest version for my device (2.8.0.0) and tried to flash the IMG with Flashify.
It said complete and rebooted into Stock recovery! Something did go wrong.. I tried TWRP manager (app from app store) to install TWRP, but it wants BusyBox.
I tried to install Busy box but it said it had a problem with installation and said I could try another directory.
I did, and again the same error. I couldnt find the file busybox in system/bin nor system/xbin.
What might the problem be? Should I continue, or is my device unstable and might I brick it?
Edit: Or would Odin do the trick and flash TWRP properly?
Click to expand...
Click to collapse
Seriously... Do I tell TWRP Manager Root to install Stericson busybox or not?
I have a galaxy s3 I747UCUFNJ2 that I tried rooting with CF-Auto-root, installed TWRP recovery and managed to get SuperSU updated but when i go to open SuperSU it won't open with message: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Device status shows custom instead of official. I dont want to have to totally wipe the phone just root with no custom rom.....
What am I forgetting??
Since you have TWRP, just flash supersu.zip from TWRP.
Try busybox from play store
Do you have Knox?
You might need to freeze it with TIBU or remove it.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
I upgraded my FireTV1 to the latest Pre-Rooted Rom. I now can't access Supersu. The chainfire app is still installed I see in Apps, but I can't access it. Where do I go from here? I assumed the pre-rooted rom that I flashed wouldn't have an issue like this.
I can still adb reboot recovery and it boots up to TWRP, I'm just not having any luck getting chainfire/supersu to request/grant root access to anything or even get Supersu to load.
I used adb to install the latest supersu apk which went fine. Since I can't access it in the Amazon launcher I loaded Kodi and tried accessing it from the Android apps and as soon as I click on it Kodi closes and Supersu doesn't open either.
I just decided to wipe the system and reinstall the pre-rooted rom from scratch. Working fine now.
Question: Magisk says "You are not forced to a single root solution for Magic Mount and other features. However, only two choices are provided: systemless SuperSU and MagiskSU. It will attempt to remove any other root, and install MagiskSU by default"
If my M8 is already rooted with S-ON, having SuperSU root access manager, what changed are required and are to be expected by going on with Magisk?
Not sure. But my thought would be make a TWRP backup of your current (rooted) setup (which you should always do before rooting) then try Magisk. If it doesn't work, restore your backup.
Or flash full stock (unrooted) ROM, then Magisk, if you want to be sure it installs without a hitch.