Hi,
I lost root after updating to JWR66Y, and when I open up SuperSU, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
So I turned off my phone, pressed volume down+power button to go into TWRP and re-flash SuperSU.zip, but the screen only shows broken android with exclamation mark on it.
So, my question is, what do I do? I want to flash TWRP via adb and then flash SuperSU.zip via TWRP. Is that the correct procedure? I'm afraid if something goes wrong I won't have a way to restore my nandroid backup or something.
Thanks.
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
simms22 said:
you always lose root if you take an ota update or flash the factory img. when you flash stock, its just that, stock. its been that way since the beginings of android.
you want to fastboot(not adb) a custom recovery, then flash the latest su binaries via your custom recovery.
Click to expand...
Click to collapse
To add on what simms22 said,
SuperSU 1.60 flashable zip: http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip
Related
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Nope. Cant with custom recovery..
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery?
Thanks
Click to expand...
Click to collapse
Your phone will boot loop if you don't go back to stock recovery first. I tried just to see what would happen and that's what happened. People who tried to flash it with Flashify reported no success.
SkyGO said:
Good morning, I wanted to know if I can upgrade to Android 7.1.2 beta with root and custom recovery installed. Do I have to remove them before upgrading or the upgrade will remove them automatically ? Will my device even boot if I update with root and custom recovery. Thanks
Click to expand...
Click to collapse
Stock ROM? Important information you omitted. From a guy who always runs the latest stock ROM rooted and custom recovery here's how you do it: You do not have to remove them first, and although they (SU & kernel) will be overwritten with the new boot.img, it is very easy and straightforward. You need the TWRP flashable (beta) OTA zip file, in the OP here. Put the latest SU and your custom kernel on the device root, or wherever. (should already be there) and then reboot to TWRP recovery. Select "Install" and then select the OTA you downloaded above, and tap "Add more zips". Next you want to add the latest SU zip (2.79 SR3) and last add your kernel. Mine is EX. Once you have queued all 3 zips, in less than a minute you will be back up and running 7.1.2 , rooted and with kernel. Even if you flash each file individually you will still be ok. (OTA, SU, Kernel). See the same thread further down... Credit for the TWRP flashable OTA goes to @Displax.
I'm about to provision my One Plus 5 for use I will be running it with TWRP a unencrypted data partition (makes restores easier) and root via Magisk day one.
I'm curious if I'm running it in this configuration when an OTA comes down the pipe will it do any of the following?
re apply fastboot oem lock?
flash the recovery to stock recovery?
remove magisk?
re-enable dm-verity?
Curious if the process after an OTA apply is to re-flash TWRP potentially re-apply magisk? Does applying ota mess with your data partition if you already decrypted it?
Also was thinking about leaving the data partition decrypted so I can push things to it via ADB or manipulate it when it's in a non-functional state can anyone here comment on if that's still possible while encrypted? And if so what dis-advantages of leaving it encrypted I hear one is you have to remove the lock screen password before you create a backup since the keys are not backed up and you might be locked out after a restore.
With some more research I've answered my own question I'll put them here in case anyone wants to refer to them in the future.
TWRP users will lose TWRP after a flash of the OTA.
Root will be lost regardless if you flash using TWRP or stock.
Data is not touched during flash so it should stay as is.
DM-verity requirement is unknown.
For rooted users it's better to do a full flash with TWRP OTA through TWRP will cause a problem.
Actually, you won't get the small incremental OTA, you will download the complete 1.5 - 2gb rom... This happens when you have root whether you have got TWRP or stock recovery.
Root will always be lost, yes but if you flash with TWRP you can flash magisk oe SuperSU immediately afterwards to gain root again. Not having TWRP you will need to either boot TWRP or install it to install root again.
DM-Verity, I have never had any problems with this after flashing and then rooting...
I dirty flash the 4.5.10 and i had to reflash the ROM + no_verity_op5.zip. My first and only issue was a sort of bootlop to the recovery.
So wait. If I flash the OTA, then flash Magisk, I will have root and lose TWRP, right?
Then could I use some app like Flashify or the TWRP app to install the recovery?
I don't own a PC right now and want to know if it's possible.
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Filip013 said:
I've flashed Magisk, but because I can't get Xposed to work, I'd like to remove Magisk and install SuperSU, but I don't know how. I tried to flash the uninstaller via TWRP and it says everything is fine, but after rebooting it just stays installed. If I try to flash SuperSU anyway I get stuck on boot. I have to flash stock boot.img via TWRP and then Magisk magically reappears. I tried using MiFlash but it refuses to do anything. It says no permission.
One possible solution, I guess, would be to flash stock ROM via TWRP. Can this be done? Any other ideas? Or am I just stuck with Magisk until a new version is available?
Click to expand...
Click to collapse
Magisk is pretty much "useless" for now. Because it is based on system-less root, and cannot be updated (because still in testing phase! Newer Xposed module from Magisk requires latest Magisk root binary, which is pretty out of option atm as we can't update to the latest binary). The only solution if you want to have proper root access is:
1. Head over to Xiaomi MIUI website and download the full stock ROM again, and then flash it via fastboot (choose flash_all_except_storage.bat if you want to preserve your data).
2. Once flashed, reboot back to bootloader and unlock it.
3. While still in bootloader flash the correct CF-Auto root boot image for your ROM (contains SuperSU 2.82 binary, https://desktop.firmware.mobi/device:1748)
4. Wait patiently and it will automatically reboot. Install SuperSU from Play Store if you want root management app.
5. If you need Xposed, download the Xposed apk from XDA and then install it normally (not via recovery).
6. ??? Profit
*DO NOT INSTALL permanent TWRP as it will cause your phone stuck in boot loop.
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Filip013 said:
@soralz
Thanks for your help, but no luck. I understand what I'm supposed to do, but I can't get MiFlash to work. When I try to flash stock image I get a "Permission Denied" error. (I have unlocked my bootloader successfully). I tried flashing modified stock image from here But then I couldn't boot. My only solution is to flash stock boot.img via TWRP and I can boot, but I stay stuck with Magisk.
So far, the only options I can think of is to wait for a recovery-flashable ROM, a new software update or a new version of Magisk.
Click to expand...
Click to collapse
You couldn't boot, are you using permanent TWRP?
Have you tried download the Full ROM from here and run this (as attachment)?
http://en.miui.com/download-333.html
Btw, place the folder under 1 directory only eg: as attachment. (I tried in multiple directory eg: "D:\Phones\ROM\Stock ROM", it just wouldn't flash)
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Filip013 said:
@soralz
OMG!!! I can't believe it. MiFlash refused to let me flash because I tried to do that from the wrong location. Weird??!!
Good. I’ve managed to follow your instructions and success!! Just a minor note, I couldn't flash the modified boot.img directly via fastboot, it still won't let me. But I just booted TWRP (without flashing) and then flashed it from there. Again, THANK YOU!
BTW, yes, I had flashed permanent TWRP and then unsuccessfully tried to remove it.
Click to expand...
Click to collapse
Oh you manage to fix that? Good for you then. And yes you cannot have permanent TWRP and SuperSU at the same time. The CF-auto root for me I just click root.bat and done. btw side note, you will lose root after each update, besure to check out the new patched boot image. I m sure in the future we will have automated process, don't need to re-root manually after each update
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.
fireop958 said:
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.
Click to expand...
Click to collapse
SuperSU should have a uninstall file, try flashing that in twrp
Sent from my validus_athene using Tapatalk
fireop958 said:
I was trying to root my phone and I installed Supersu but than my phone refused to boot. It would open fastboot but nothing after that. I tried to revert to the stock image and i think i made it past that but, that did not fix anything i can still only boot into fastboot. Please help me I want to save my phone.[/Q
Flash a temporary rom and then install a stock recovery, and then boot back into stock rom by flashing stock image on pc
through fastboot mode
Click to expand...
Click to collapse
@fireop958
Installing SuperSU or any root app needs custom kernel installed, if you flash it on stock kernel then its anti-root mechanism will get activated and it will refuse to boot;
now first flash the stock rom via fast boot from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
then after its booted successfully, then flash the TWRP from fastboot and flash the ElimentalX kernel from TWRP, reboot and check the kernel info in about phone in settings; after then
simply flash SuperSU or magisk from TWRP to get root access
siddhesh9146 said:
@fireop958
Installing SuperSU or any root app needs custom kernel installed, if you flash it on stock kernel then its anti-root mechanism will get activated and it will refuse to boot;
now first flash the stock rom via fast boot from here : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
then after its booted successfully, then flash the TWRP from fastboot and flash the ElimentalX kernel from TWRP, reboot and check the kernel info in about phone in settings; after then
simply flash SuperSU or magisk from TWRP to get root access
Click to expand...
Click to collapse
Thank you so much. You saved my life right there.