Unable to root 5.1.1 - Nexus 5 Q&A, Help & Troubleshooting

Hi
I was running 5.1 stock and rooted with supersu.
I've manually flashed 5.1.1 and that seems to have gone well..the phone is up and working.
I downloaded SuperSU 2.46 and flashed it via TWRP, phone rebooted and I had a superSU icon.
When I click on it I got an error saying no binaries are installed.
So I booted to TWRP and flashed it again, then when exiting TWRP I was asked if I want to install SuperSU so I said yes.
Phone rebooted and now I have a superSU installer icon. I've run that and selected TWRP.
It downloaded a file, rebooted to recovery, flashed and restarted the phone.
The phone is backup but not rooted. I still have a superSU installer icon..
How do I root this phone ?
Thanks

Related

[Q] Lost ROOT after manually updating last OTA via TWRP

As title says... I had unlocked bootloader and flashed TWRP then SuperSU and ROOT was working fine.
- Last OTA I got which was yesterday (as only just got the phone) was XNPH33R.
- I used TWRP to install the update which went fine except I lost ROOT access.
- Went back to TWRP and reinstalled SuperSU which shows as installed on my phone - however no apps that require ROOT can get ROOT access and RootChecker shows that the phone is not rooted.
- Rebooted to System / Tried to Fix Permissions / Tried to reinstall newest SuperSU - nothing works
Does anyone have any suggestions as to how I can regain ROOT or is not possible on XNPH33R?
Further issues I have now got no ADB access in Fastboot no matter what drivers I install... don't know if this is all linked!!!
Jesus christ
Any help appreciated.
Thanks in advance
Too much work if you do a full wipe and re rooted ?
Also try to put zip file with airdroid and flash it in download mode
So I've found out that although adb was telling me that it couldn't recognise any devices in fastboot mode - all the actual commands from the OnePlus One toolbox were actually getting through as I relocked my Bootloader to see what would happen and then tried to Flash Recovery and it told me Bootloader was locked - so that confirmed adb commands were working.
To solve my ROOT problem I did the following:
1) Flashed CM XNPH22R
2) Installed all OTA updates
3) Unlocked Bootloader
4) Installed TWRP - then chose REBOOT TO SYSTEM (this told me I wasn't rooted and then followed prompts)
5) I chose to install SuperSU from Play Store
6) Opened SuperSU and updated binaries
7) Turned off Update CM Recovery in Developer Options
8) Rebooted and installed and ran Root Checker....
9) Success!
Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.
Cholerabob said:
Remove the respect CM root settings from the SU settings menu and your root will come back i had the same problem until i found this out.
Click to expand...
Click to collapse
Thanks - wish you told me that earlier!!
I assumed it should be on because it's CM right!!! Doh!
Oh well - this might help someone else...

Moto Xt1068 soft brick( no is installed and no root access)

I accidentally wiped system using twrp and now it says no is installed. I had rooted before and when I tried to install a custom ROM using twrp. It failed. Whenever I reboot, it shows device not rooted swipe to install supersu . I swiped with no use. Also installed SuperSU 2.5x beta. Install succeeded. But still shows device not rooted. Please help
If you can access recovery, try any custom rom (CyanogenMod is recommended) and then flash Chainfire's systemless root.
I flashed official ROM and it worked.

Installed Oct 2017 Image and TWRP, Can't Install SuperSU from TWRP

I successfully updated from the August Oreo image to the October Oreo image today and installed the latest TWRP recovery image. Then I tried to install SuperSU (SR5) through TWRP, which seemed to go well, but the app wasn't added to in the app drawer, and none of my apps had root access. I rebooted into TWRP and reinstalled SuperSU (SR5), and still, the app wasn't listed in the app drawer. Then I rebooted into TWRP and installed SuperSU (SR3), the last version I'd installed before the October update that worked, and that didn't get added to the app drawer either. Rebooted, reinstalled SuperSU (SR3) in TWRP, and still, not listed. I then uninstalled SuperSU from Oreo, where it surprisingly was listed, and installed SuperSU from the Play Store. Then I opened SuperSU and it needed to update the binary, which I let it do normally (not via TWRP). Now My phone has been booting with the G logo for the past 10+ minutes. What should I do?
After 20 minutes, I rebooted via ADB and now I'm back at the G loading screen with the colorful G with a moving status bar underneath (not the dots).
After another 10 minutes with the colorful G with a moving status bar underneath (not the dots), I tried to reboot into recovery so I could try manually installing SuperSU via TWRP again. I found that there was no recovery partition installed.
Ended up reflashing the October Oreo update (OPR3), which worked on the first try, then reflashed TWRP, SuperSU, and suhide, one at a time. All of that worked, and now everything seems to be working.... Not sure what went wrong, but glad everything is back to normal and no data was lost!
Why do people still use SuperSU? Magisk is a much better alternative and I don't trust it now it's in the hands of some Chinese company.
I didn't know about Magisk... Wiping and installing now...

7 Pro reboots into TWRP after Update

So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Maybe you have some Magisk module causing this. There is an option to disable Magisk modules through command line.
memocatcher said:
So I was rooted and had TWRP, I installed the OTA via the OnePlus Updater. Then I proceeded to flash TWRP in fastboot again, flashed twrp installer afterwards and finally flashed magisk 19.3. Then I rebooted into system, but whenever I 'm at the pin field the device shuts down and reboots to TWRP.
I uninstalled magisk via the zip file and succesfully rebooted into my system. Why is this happening and how can I get back Magisk?
Click to expand...
Click to collapse
If you used magisk uninstaller and the reboots are gone then just flash magisk again. Also it's best to use 19.4 magisk

I wiped the system using Twrp and i dont know how to restore my phone

Hi, i have Samsung J7 Prime it was rooted by Magisk Manager and when i updated the Magisk Manager to V.18 the root stoped in my phone i tried to restore it so i installed the SuperSU and it did not help me so i installed the pro version and it also did not help me so i uninstalled the Magisk Manager V18 and installed an older version and it said that it is not installed and downloawded a file and after start his code it said "Reboot" and i chose "OK" and the phone restarted and the root also restored so i didnt uninstalled the SuperSU but i opened it and it said that it will install its flash so i approved and the phone stil for long time at the starting so i opened the recovery mode (Twrp) and i wiped the system by advanced wipe and i dont know how to restore my phone plz help me.

Categories

Resources