So I have everything required to install SuperSU, i even got the Config just in case
and when i flash the zip file using TWRP it says that the installation was completed with no errors
when i reboot i find out that my devices isn't rooted.
So i tried again with flashing the config, same issue
Then I installed the SuperSU app from google play, then tried flashing the zip file and when i reboot, the app was deleted and same thing. No Root
Need help
Related
Hi I'm trying to install above since viper4android wont work with the stock su, but no luck.
I've tried installing from the market per this:
1. Install SuperSU from Play Store.
2. Open SuperSU and grant it SuperUser permissions (important; if you delete SuperUser before you grant rights to SuperSU you lose your root and need to either reflash the ROM or flash the zip I linked above).
3. gone into supersu settings and told it to grant su on boot, and grant to anything in the system folder as well
and I've also tried installing the zip version in recovery. I've also tried using the file manager in recovery to rename the current su binary in system//xbin and put the new one from the zip file in the directory.
Any way I try installing it freezes on boot up and I have to restore a nand to get my TP working again.
Overall loving flintmans new evervolv, it's really smooth, but the sound on the TP is pretty low and crappy sounding without viper4android so it's a pretty big issue for me.
Can anyone help please?
PS I cant find the apk for the current su, maybe thats part of my issue as well. Also Supersu works with 3.4 kernel version of cyanogenmod so its not a kernel issue.
I am a proud owner of OP One and SuperSu Pro. Currently i am using http://forum.xda-developers.com/oneplus-one/development/daily-stock-unofficial-cm12-builds-t2948099 ROM (as of today 15-12 build).
I installed SuperSU through TWRP 2.8 and used to work fine, untill i updated to a new CM12 build. Then i was promted to grand permissions to an app, but i could not press "grant", later opened the SuperSU app and got a message that there is no binary installed, so i tried to reflash the zip noumerous times, but it seems that TWRP is unable to flash the zip.I can flash other zips like new versions of the ROM, GAPPS etc.
It seems like TWRP is not able to flash the SuperSu zip, even though i get a "succesful" message while flashing. I tried cleaning Cache and Dalvik. Also i can't find the log created by TWRP which is suposedly created in data/media/0 so i can't post detailed info about it.
Super Su
There is no Su binary installed and SuperSu cannot install it. This is a problem.
...
Click to expand...
Click to collapse
This is my installation process [last post summary]
https://forum.xda-developers.com/gal...ageos-t3576865
Downloaded lineage-14.1-20170322-nightly-klte-signed.zip
flashed this ROM with TWRP
rooted with CF-Auto-Root - same problem
downloaded again addonsu-ARM-signed_14.1
flashed this ROM again with TWRP
cleaning Dalvik and cache [kind of never done it before here]
rooted with addonsu-ARM-signed_14.1
all works
PS after flashing 20170322 ROM, on the first run I almost sh*at myself as SD card was not recognized. Restarted and was OK.
CATLOG screenshot
https://dl.xda-developers.com/4/1/0....jpg?key=J9F9olpmOpltDNbjtBwaxQ&ts=1491479200
If I try to update binaries in TWRP, it stops, restarts and stops during Lineage loading screen forever. [nothing in TWRP logs about SU I can see]
So I flash ROM again, and addonsu-ARM-signed_14.1 from TWRP to fix it.
I was reading that after flashing addonsu-ARM-signed_14.1 - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
Is there a way to have it done?
Is it sometimes necessary to set permissions in Terminal for some SU files/folders before updating binary? I think ages ago I was doing something like this...?
Is it possible that
1. flash ROM
2. root fith CF root
3. dirty flashROM
4. use correct root addonsu-ARM
can have anything to do?
SM-G900F
lineage-14.1-20170329-nightly-klte-signed.zip
lineage-14.1-20170405-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
The link for your install process, gives an XDA 404 page loading error.
One question though with SuperSU settings. Do you have it set to allow SU to run during boot? Maybe that's why it seems to take forever to load after updating binaries through TWRP?
Sent from my SM-G930P using Tapatalk
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
newuxtreme said:
@dr.ketan
I was finally able to install your rom. However I have not been able to figure out how root works on this exactly as of yet.
I tried to install a normal Supersu from google play but it says I don't have Root on my Rom yet.
Can someone help me out with this please?
Click to expand...
Click to collapse
I thought Dr. Ketan's N10 ROM was pre-rooted with either Magisk or SuperSU. Did you not have this option in the AROMA Installer? If not, here is some help..
I personally recommend Magisk for root. It's just as easy to use Magisk over SuperSU. Each root solution has its own dedicated app as well. To root with Magisk you will need the latest root zip which is V14.0 along with the latest Magisk Manager apk.
You can download the latest Magisk Manager apk and the latest Magisk V14.0 root zip from the link below...
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Here you can read and learn all about Magisk too. Once you download both the root zip and the apk, transfer both to your internal storage.
Next, download the no_verity_opt_encrypt_5.1 zip from here...and transfer it to your internal storage.
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
(Its the second link from the bottom in the list)
Easy steps to root your device with Magisk..
Boot to TWRP Recovery
Select Backup and put a check in each box. That way if anything goes wrong you can restore the backup and have a working device.
Next, select WIPE - Advanced WIPE - Check both caches
Swipe to wipe both caches
Next, select INSTALL
Navigate to where you saved the root zip and select the zip.
Swipe to flash the zip
Click on the box to wipe the caches
Now, just in case, flash the no_verity_opt_encrypt_5.1 zip that you downloaded earlier.
Reboot your device. Once booted up, install the Magisk Manager apk. It will install as a normal app. Make sure you have enabled "unknown sources" in Settings - Lock Screen and Security so you can install apps outside of the Play Store.
Open the Magisk Manager app and set it up to your preference. It's very easy to use.
If you run into any issues don't hesitate to ask questions.
Good luck and happy flashing!
Sent from my Samsung SM-G955U using XDA Labs
I've flashed recently CSC file and lost the root. I updated MAgisk app up to 25.1 version (not a zip file just apk) but still no root. I have flashed Magisk 25.1.zip file in TWRP recovery. Now the phone is rooted, but I unable to start Magisk app. It just stuck on the start (The Mask). I tried to uninstall Magisk app via Application manager, and reinstall it following by reboot. Still Magisk unable to start. I don't remember whether MAgisk was unhidden before the update and zip installation. What should I do next?
Should I rename the Magisk.apk to uninstall.zip and run this file in TWRP. Then install Magisk apk and install zip file from within Magisk App? If so, what the best way to install MAgisk App; via TWRP or File Manager?
Samsung Galaxy S5
Marshmallow 6.0.1