Database Info

[Q] A way to root but stay stock so can keep getting OTA s?

(noob) Question: Is there a way to root my OnePlus and keep stock recovery (for now at least) so I can just get the OTA updates? I want to have root so I can use Xposed and LMT but still stay stock. Thanks

scott62185 said:
(noob) Question: Is there a way to root my OnePlus and keep stock recovery (for now at least) so I can just get the OTA updates? I want to have root so I can use Xposed and LMT but still stay stock. Thanks
Click to expand...
Click to collapse
yep, just install the drivers, unlock the bootloader, install a recovery (i used twrp), then flash supersu. go over to the android development folder and there are toolkits there. im running stock rooted right now.

you dont have to unlock the bootloader or flash a recovery to root. just run "fastboot boot recovery.img" itll boot the alternative recovery, and you can flash the super user zip from there. it will only boot twrp or cwm but not flash it to the device and will not replace the stock recovery.
unlocking the bootloader just allows you to write to the boot partition and boot different recoveries and kernels from the device. it does set off a tamper flag which could void your warranty. but unlocking is not required for modifying the system partition which is what you are doing when you root.

scott62185 said:
(noob) Question: Is there a way to root my OnePlus and keep stock recovery (for now at least) so I can just get the OTA updates? I want to have root so I can use Xposed and LMT but still stay stock. Thanks
Click to expand...
Click to collapse
You can install OTA updates even with a TWRP installed. You just have to untick the CM Recory option from Settings -> Developer Settings -> CM Recovery
What that does it tells the OTA update not to update your recovery when the option is unticked. If you leave the tick on, then every OTA will relock your bootloader and install CM recovery.
But all in all, OTAs work fine with root + twrp

inffy said:
You can install OTA updates even with a TWRP installed. You just have to untick the CM Recory option from Settings -> Developer Settings -> CM Recovery
What that does it tells the OTA update not to update your recovery when the option is unticked. If you leave the tick on, then every OTA will relock your bootloader and install CM recovery.
But all in all, OTAs work fine with root + twrp
Click to expand...
Click to collapse
Oh wow, I didn't know that. Great! Thanks

inffy said:
You can install OTA updates even with a TWRP installed. You just have to untick the CM Recory option from Settings -> Developer Settings -> CM Recovery
What that does it tells the OTA update not to update your recovery when the option is unticked. If you leave the tick on, then every OTA will relock your bootloader and install CM recovery.
But all in all, OTAs work fine with root + twrp
Click to expand...
Click to collapse
That won't let you keep root, though it's easy to flash SuperSU from TWRP after every OTA.
A solution to OP's problem could be SuperSU Pro which lets you keep root even after OTA updates. I haven't tested it yet but the option is there.

CrashTestDroid said:
That won't let you keep root, though it's easy to flash SuperSU from TWRP after every OTA.
A solution to OP's problem could be SuperSU Pro which lets you keep root even after OTA updates. I haven't tested it yet but the option is there.
Click to expand...
Click to collapse
I unlocked my device, then booted into twrp via adb, then flashed supersu but i have no root. the app is installed but i cannot grand titanium backup for example root rights. so the root process did not worked but why? tried it severall times and downloaded everything from scratch sever times. no chance. help me pls..

blax123 said:
I unlocked my device, then booted into twrp via adb, then flashed supersu but i have no root. the app is installed but i cannot grand titanium backup for example root rights. so the root process did not worked but why? tried it severall times and downloaded everything from scratch sever times. no chance. help me pls..
Click to expand...
Click to collapse
open the SuperSU app, see if it complains about missing busybox or anything

CrashTestDroid said:
open the SuperSU app, see if it complains about missing busybox or anything
Click to expand...
Click to collapse
How do I install busybox?
Sent from my GT-N8010 using Tapatalk

Nevermind, I found the solution. I had to disable a Option in SuperSU settings because the CM comes not rooted from out of the box
Sent from my Carbonized Nexus 4

inffy said:
You can install OTA updates even with a TWRP installed. You just have to untick the CM Recory option from Settings -> Developer Settings -> CM Recovery
What that does it tells the OTA update not to update your recovery when the option is unticked. If you leave the tick on, then every OTA will relock your bootloader and install CM recovery.
But all in all, OTAs work fine with root + twrp
Click to expand...
Click to collapse
If I do this, will I lose root upon OTA?

sharp2G said:
If I do this, will I lose root upon OTA?
Click to expand...
Click to collapse
No if you have supersu pro installed and have selected the setting to keep root after ota

Will towelroot work on this?

Quinnaay said:
Will towelroot work on this?
Click to expand...
Click to collapse
im not sure people have really tried. youre welcome to give it a shot as it says its possibly compatible with everything. but theres already a root method that doesnt require bootloader unlocking and installs supersu which is most peoples favorite root manager.

Towelroot is incredibly simple I get a little nervous otherwise.. Is there a tutorial on the easy alternative, I only want titanium backup to restore my apps from s4 (considering I can do that)

inffy said:
No if you have supersu pro installed and have selected the setting to keep root after ota
Click to expand...
Click to collapse
Where is the option to "keep root after OTA" in SU?

I managed to boot the twrp recovery on 4.4.2..but updated to 4.4.4 33R and now it says SU binaries not installed...also cant boot recovery on fastboot as it says need to unlock the bootloader?
Why did update prevent this now?

tofuboi01 said:
I managed to boot the twrp recovery on 4.4.2..but updated to 4.4.4 33R and now it says SU binaries not installed...also cant boot recovery on fastboot as it says need to unlock the bootloader?
Why did update prevent this now?
Click to expand...
Click to collapse
Did you untick the option to update CM recovery during your update?

I didnt untick it no, but i never flashed the custom recovery in the first place as i just booted it up from fastboot on 25R, on 33R however its been disabled and requires unlocked bootloader.

inffy said:
You can install OTA updates even with a TWRP installed. You just have to untick the CM Recory option from Settings -> Developer Settings -> CM Recovery
What that does it tells the OTA update not to update your recovery when the option is unticked. If you leave the tick on, then every OTA will relock your bootloader and install CM recovery.
But all in all, OTAs work fine with root + twrp
Click to expand...
Click to collapse
@inffy,
Hi,
I unlocked bootloader before installing 22R and updated 25, 30, 33 & 38R with OTA from 'System updates' menu. After 38R i flashed TWRP recovery and rooted my phone without unlocking the phone again & its working fine. Perhaps, the we don't need to unlock bootloader again once it unlocked. Can anyone confirm it??

[Q] Problems rooting. Have s off and unlocked on lollipop.

Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.

DWDahlinger said:
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
Click to expand...
Click to collapse
Since you have TWRP installed do a android backup and install one of the rooted ROMs. Most will install SuperSu and BusyBox in the installation process.

DWDahlinger said:
Ok so I'm having this issue.... I do have s off and I'm unlocked from previously on KitKat. I flashed TWRP and tried flashing the latest SuperSU but it failed on multiple attempts. WinDroid says I'm already rooted when I try to do it but SuperSU gives me this message when I open it, "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Then it tells me to visit the forums for this problem so here I am.
SIDE NOTE:
I remember when I originally unlocked and rooted the phone I did a temp root because I was having an issue rooting. All this makes me assume that there's some type of root files, probably out of date, that is showing WinDroid that I'm rooted and preventing me from using SuperSU. I would try to locate them but for some reason (I assume Lollipop) I can't access my system files anymore. My ES File Explorer just shuts down when I try. I know one of you guys has got an answer for me.
Click to expand...
Click to collapse
You need to flash the latest version of supersu. My hunch tells me you aren't using the latest version. Also, when you post for help once please don't continue making similar posts and threads. It makes it very hard for you to get the help you are looking for. You never responded to the last post I made to you last night about to unlock your bootloader either.
Es file explorer is crashing because of the webview for Android update. Uninstall that update and it will work again.

dottat said:
You need to flash the latest version of supersu. My hunch tells me you aren't using the latest version. Also, when you post for help once please don't continue making similar posts and threads. It makes it very hard for you to get the help you are looking for. You never responded to the last post I made to you last night about to unlock your bootloader either.
Es file explorer is crashing because of the webview for Android update. Uninstall that update and it will work again.
Click to expand...
Click to collapse
Sorry I didn't see your response to my post. I only saw the others. Been trying to figure this stuff out since.
I think I flashed the latest version (2.46)? I used windroid. Pushed the file to the phone and installed it from the internal memory. Not sure of what the webview in Android update is or how to uninstall it. I will try the method you gave me in the other post. Thanks!
Update: Disabled webview for Android. Working now. Thanks!

Upgrade from 32.2.A.0.305 to 32.2.A.5.11

Hi!
Did anybody managed to upgrade from unlocked an rooted 32.2.A.0.305 to 32.2.A.5.11?!
I tried it at least five times and I failed.
Everything seems to work, except unlocking the bootloader and gaining root access.
1) Flashed the new firmware with Flashtool (without TA partitions!).
2) Tried to unlock the bootloader but this is not working as expected.
The service menu tells me that I can unlock my bootloader.
But when I try to unlock it via fastboot I am getting a message, that my device is already rooted/unlocked.
FAILED (remote: Device is already rooted)
So I locked it again using the "Sony Mobile Flasher". After a reboot the "fastboot -i 0x0fce oem unlock 0x....." command gives me an OKAY and after the next reboot my device is automatically wiped.
But the service menu still tells me that my bootloader is unlockable and not that is unlocked!
Installing the patched kernel and TWRP seems to work because fastboot returns an "OKAY".
But neither I can access the TWRP recovery (LED won't get amber) nor the device is rooted.
Okay.... does anybody can give me a hint, how to root the current FW version?!

Ok, I downgraded to 32.2.A.0.305 and everything is working fine again!
I have root access and I can boot into recovery!
What is wrong with 32.2.A.5.11?

im on .I 1 , bootloader unlocked , rooted
got same error as u
device already rooted
so i just didnt check what services menu say and rooted my z5

mohalazio said:
so i just didnt check what services menu say and rooted my z5
Click to expand...
Click to collapse
How did you do this?
I flashed a modifyed kernel (dm-verity: off, RIC: off, TWRP: no, DRM fix: yes, busybox: no) with
fastboot flash boot boot.img
But I cannot install SuperSU from PlayStore.
It sais that the su binary is missing and that it cannot be installed.
So, next I tried to install TWRP with
fastboot install recovery twrp-3.0.2-0-E6653-20160504.img
But on a reboot the LED is not getting amber and I cannot enter recovery.
It seems that neither the patched kernel nor the recovery has been installed. Even though fastboot returned with an OKAY for both install commands!
First I thought that something went wrong patching the kernel with rootkernel5.0. So I downloaded and flashed an already patched one for 32.2.A.5.11. But I have still no root access!
From loud despair I flashed the SLIMX REBORN ROM (1.17BEATMODE). Now I have full root access again, but on 32.2.A.0.305 with my old problems: a) The SU binary cannot be updated from within SuperSU app and b) SONY annoys me to update to the new version every day.
I can't believe that it is not possible to root the new version or that it just doesn't work for my device.

u missed 1 small detail
first : download flashable supersu ( supersu. zip )
then put it in rootkernel folder
build the kernel
u will get extra question asking u to install supersu ( the answer is yes )
flash ur boot. img
thats it

Hi!
I know that I can integrate SuperSU into the kernel image.
But I cannot upgrade a su binary installed that way by using the SuperSU app from playstore.
The PlayStore / TWRP method for SuperSU works like a charm on 32.2.A.0.305.
But I will give it a seventh try with "AndroPlusKernel Permissive v42" instead of the patched stock kernel.
mohalazio said:
u missed 1 small detail
first : download flashable supersu ( supersu. zip )
then put it in rootkernel folder
Click to expand...
Click to collapse

Okay, I am giving up for now!
Buying a SONY phone was one of my worst decisions in 2016.
After a Samsung Galaxy Nexus and a HTC One M8 the SONY Z5 drives me crazy.
After installing 32.2.A.5.11, SuperSU 2.79 and AndroPlus kernel v42 I still have a phone that is unrooted!
And TWRP is reporting the unknown partition "/keymaster"....

so u have supersu installed and working ?
if thats the case i also have binary update problem when updating it from playstore
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
i would suggest one way
first u have 2 IMEI
try unlocking the bootloader with the the other IMEI
UNLOCK using flashtool
then root kernel
---------- Post added at 10:58 PM ---------- Previous post was at 10:53 PM ----------
if things didnt work out
use this rom on .305
http://forum.xda-developers.com/xpe...m-32-2-0-305-e6653-e6683-1-0-0-t3498626/page1

mohalazio said:
so u have supersu installed and working ?
Click to expand...
Click to collapse
I managed to install it via TWRP but as you can see "Root Check" says that my device is not rooted and that the SU binary cannot be found! The same error with the SuperSU app itself. The message means that the su binary cannot be found and SuperSU is not able to install it!
mohalazio said:
i would suggest one way
first u have 2 IMEI
try unlocking the bootloader with the the other IMEI
UNLOCK using flashtool
then root kernel
Click to expand...
Click to collapse
Two IMEI?! My Z5 is the single SIM model.

what supersu version u used?

mohalazio said:
what supersu version u used?
Click to expand...
Click to collapse
SuperSU-v2.79-201612051815

try 2.78

Still not working!
Damn, why I am the only person on this planet that fails to root its XPeria Z5?!

good news for u
new rom based on .11
http://forum.xda-developers.com/xpe...m-32-2-0-305-e6653-e6683-1-0-0-t3498626/page1

Thank you!!
I'll give it a try!

NHG47K Root?

So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks

pstgh said:
So my unlocked Google Pixel was rooted until I recently received the NHG47K OTA update and now it is not....
SuperSU is showing installed, but when I open it up, I get a message saying that "There is no SuperSU binary installed and SuperSU cannot install it."
I didn't expect to lose root as I don't believe I ever actually authorized the OTA update to get installed... just woke up one day to find that my phone is no longer rooted.
Can someone please recommend the most efficient method to regaining root from here?
Thanks
Click to expand...
Click to collapse
Boot to twrp and reflash the SU binary.

With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?

pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Questions go in the "Google Pixel Questions & Answers" section.
Always use the latest of both unless you read otherwise - for example, if you read the TWRP thread, you'll see a lot of people have trouble with RC2, so just stick with RC1.

pstgh said:
With the new OTA build, do I need an updated TWRP.img file and/or a newer SU binary?
Click to expand...
Click to collapse
Boot to TWRP RC1, then install SU RC3. Assuming you don't want TWRP permanently installed.

Received Nougat update while having TWRP and Super SU Root

Hey, I'm curious how I received the Nougat update if I have TWRP and Super SU root. I've never been able to receive a phone update if I had this setup. Doesn't super su modify the system? If I try installing the update will I brick the phone?
Edit - Sorry, I meant to post in the questions thread. You guys can lock, move our delete this post.

I accidentally updated my phone while having TWRP and SuperSU installed. It does not brick your device, but you lose root access. I'm currently trying to re-root my phone but I'm having some issues. My phone seems to have remained unlocked.

I did the same thing...got worried at first, but everything looked okay so I went ahead and flashed Magisk...seems fine.

Hello!
I have B342 and want to update to B360. My phone is rooted and TWRP works.
When i use the normal way to update, the phone boots to TWRP and an Error message comes during update
How do I do it?
Thanks!