I had cyanogenmod 14.1 installed and I accidentally flashed SuperSU from it, and now all the root is lost. I used root checker and it says no root, however I can still boot into TWRP and have successfully flashed LineageOS 14.1. Is there any way I can regain the root?
Thanks for the non-existant help...
BrianSamsungTab said:
I had cyanogenmod 14.1 installed and I accidentally flashed SuperSU from it, and now all the root is lost. I used root checker and it says no root, however I can still boot into TWRP and have successfully flashed LineageOS 14.1. Is there any way I can regain the root?
Click to expand...
Click to collapse
LineageOS has a su addon zip for 14.1 that you should flash from their site. Look in their downloads portal under "extras" to find it.
The zip just gives me Error 4 in TWRP. Google yields nothing for this error at all.
BrianSamsungTab said:
The zip just gives me Error 4 in TWRP. Google yields nothing for this error at all.
Click to expand...
Click to collapse
I did some googling about a week ago and found this unresolved issue on LineageOS's Jira/issue tracker. Could you try the arm zip attached to that post and see if it works?
Didn't work. It says in TWRP that it succeeded (code 1) but when I boot back into Lineage or reflash it there is still no root.
Related
Hey Guys!
I'm having a little bit of trouble finding info on this out. I
I running android 6.0, have s-off and have installed TWRP 3.0.2-0 and had supersu installed.
Decided to enable encryption which only worked when i did full unroot via supersu app but now when I try to go into TWRP and enter my password to decrypt, it fails. I'm trying to re-install supersu but would also like to have TWRP work correctly.
Any one have any tips?
Thanks!!:good:
g33gz said:
Hey Guys!
I'm having a little bit of trouble finding info on this out. I
I running android 6.0, have s-off and have installed TWRP 3.0.2-0 and had supersu installed.
Decided to enable encryption which only worked when i did full unroot via supersu app but now when I try to go into TWRP and enter my password to decrypt, it fails. I'm trying to re-install supersu but would also like to have TWRP work correctly.
Any one have any tips?
Thanks!!:good:
Click to expand...
Click to collapse
ok I figured it [email protected]
I added my supersu.zip file to my external memory card (not encrypted).
Booted into TWRP
made sure my memory card was mounted and installed from the memory card.
Worked just fine!
NOTE: when i rebooted the phone, it did ask me for my password twice which scared my at first but it all worked out fine!
I have the v500 on Lineage OS version 14.1-20170505-nightly-v500. I'm trying to update and noticed I lost root at some point. I have TWRP 2.8.6; and when I try to do anything in recovery, TWRP freezes, and I have to reboot. It's not bricked and I can boot fine, but it appears I lost root and cannot figure out when. I've flashed several versions of Lineage OS and this is the first time I'm having issues. Any help would be appreciated. Thanks!
I would try flashing the add on SU zip, but I don't know how you'd do it if TWRP doesn't work.
I tried to install the add on su zip using sideload and when I try to start sideload using adb in TWRP, the device disconnects from adb. I saw where people lost root when they first installed LineageOS, but got it back with the next update. TWRP cannot backup, install, wipe, or sideload (via advanced). It's an interesting predicament. I've unbricked devices easier than trying to fix this.
Pixel XL running 8.0.0 OPR3.170623.007, developer options and USB Debugging are both on.
I was rooted for a while now, then I tried using one of my root-only apps and it told me it can't get root access.
I looked for SuperSU, which was missing.
I unrooted and rerooted using Skipsoft Unified Android Toolkit.
It flashed SuperSU 2.82 and flashed TWRP 3.1.1.1. The TWRP flashed just fine, but no matter how many times I flash SuperSU, it doesn't show up in my app drawer and the phone is still not rooted. I tried SuperSU 2.82 and the SR5 stable beta, neither worked. I also tried installing it through the Play Store after flashing it, it goes through the install process then just give me the option to install again, never fixes my issue.
Any idea on what I can do next?
edit: I updated to 3.2.0.0 and was able to root. Flashing the most recent beta and non-beta Magisk versions did not work, neither did installing the SuperSU APK. Once I updated to 3.2.0.0 I was able to root with Magisk just fine.
Flash the stock boot.img to both slots and reroot. Use SR5.
I would also advise to start by flashing the stock boot image. I would then boot twrp, flash twrp, then flash latest su.
If that doesn't work I would try going with the latest magisk zip (14.5)
I should have mentioned this, Unified Tool Kit flashed the factory boot image before releasing the latest TWRP and then flashing the most recent SuperSU. I did try flashing SR5 with negative results.
I'll give Magisk a try.
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
I followed 1,2,3,4,8, zero issues on 8.1.
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
DeviceManagent said:
I had a problem rooting with SuperSU. When i TWRP flashed it, it wouldnt show up in my apps, but my device was still rooted. For some reason the app just wasnt showing up so im using Magisk 14.5 instead...
Click to expand...
Click to collapse
Common issue. You can grab the app apk from inside the zip and install it.
I tried flashing both beta and non-beta Magisk versions and installing the SuperSU APK, nothing worked.
I saw that a new TWRP got released, 3.2.0.0. I flashed that and was able to successfully root. Thanks for your help, guys.
Yesterday I updated to the latest Cosmic-OS Oreo ROM and lost my magisk root. So went to TWRP and tried flashing Magisk but it failed with a "cannot mount /vendor" error. I've already tried all the different rooting guides on XDA specific to Oreo and also tried patching the boot image from the magisk app but the result is my phone gets stuck in a bootloop and never boots. Using ls in twrp terminal to find the vendor boot device in /dev shows it doesn't exist. Not sure what to do next any input appreciated! :crying:
Using Alberto's 8.1 AOSP.
I found recently that if I try to flash 16.4 it gives me a lot of red stuff, so I went back to 16.0
I then flash the universal fix version of magisk.
I forget whether I had to boot in between there and if I had to let it load magisk mgr in there somewhere.
I use root for things like TBPro.
Works fine for me in Alberto's AOSP 8.1 which is my daily.
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Very strange, but it just worked, after the 20th time of doing the same thing. Who knows why
Hey, my issue with Magisk is a bit different. I've upgraded my Pixel 2 XL every month and flashed Magisk afterwords. What I keep running into for the past couple of months is that after I'm all done, I will get a notification that there's an update to Magisk, but it's the same version I already have. I've tried different versions from 16.7 to the beta 17.3 and I would always seem to lose root after a while and be prompted to download the update to Magisk. Any help is greatly appreciated! Thanks in advance.
I am having the same issue with magisk after updating to nov update. Did the flashall then booted twrp and flash magisk Not sure why
Cowbell_Guy said:
Hey all, I have always updated each month using the simple methods posted here, just doing a fresh install of each factory image.
I have got the november update installed, TWRP installed. However, I cannot for the life of me get the magisk install to "take".
I have installed various versions, 16.7 17.1 and 17.3 in TWRP, have rebooted to system each time, and yet no magisk zip. Have even tried doing fresh install wiping system, magisk uninstall, etc. Anything you can think I am doing wrong?
I just checked and its nothing wrong with the TWRP method... I was just able to install sultan zip from it. Any other way I can get magisk manager/Magisk zips? I have always just flashed the zip from TWRP. please help, thanks
Click to expand...
Click to collapse
Run the Magisk uninstaller first
run 17.1 or the uninstaller. i've had better luck with 17.1
I guess the issue is linked to the Active Edge Module!
Download "uninmod_magisk", install it via TWRP, execute it via Terminal in TWRP, delete the Active Edge Module.
Now you can boot and reinstall that module.