Database Info

[Q] Can you get root without custom recovery so that you can update with OTAs?

I followed this guide to get root on 5.0.1, but I didn't realize it makes updating a pain. I saw that this user's signature says he's running stock root, but I haven't been able to find a guide for doing so on Lollipop, only using towelroot on KitKat. The only thing I use the recovery for is getting root, so I don't care about keeping CWM if there's another way. Is there some way I can keep root and also use OTA updates?

If you are rooted and have a custom recovery, don't download the OTA within the tablet. Follow this thread, download desired FULL OTA Zip (WiFi or LTE) and latest SuperSu.zip. Flash OTA (≈700MB ) and then SuperSu. Won't loose custom recovery or root.
http://forum.xda-developers.com/showthread.php?t=3033730
---------- Post added at 07:11 AM ---------- Previous post was at 07:06 AM ----------
Ohhh and before that I used Flashify app from market to flash this TWRP recovery: http://forum.xda-developers.com/showthread.php?p=58864006

albertorodast2007 said:
If you are rooted and have a custom recovery, don't download the OTA within the tablet. Follow this thread, download desired FULL OTA Zip (WiFi or LTE) and latest SuperSu.zip. Flash OTA (≈700MB ) and then SuperSu. Won't loose custom recovery or root.
http://forum.xda-developers.com/showthread.php?t=3033730
---------- Post added at 07:11 AM ---------- Previous post was at 07:06 AM ----------
Ohhh and before that I used Flashify app from market to flash this TWRP recovery: http://forum.xda-developers.com/showthread.php?p=58864006
Click to expand...
Click to collapse
Yup! That's how I plan to do it for this update, but that's exactly what I'm trying to avoid doing in the future.

Quoting this post: http://forum.xda-developers.com/showpost.php?p=58922383&postcount=17
An Droid said:
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
From that, I understand that even if you have stock recovery, by being rooted, OTA wont work on you.
Just for the fact of being rooted.

Just unboxed a 920i 128GB. 5.1.1 wants tp install. Should I? Need to have root

Again this is an SM-G920i.
Some things that I wold like to do with this phone, and it looks like I can with th 5.02.
Root
TWRP
Custon ROMS
Should I just ignore this update 5.1.1 update and work with the 5.02? I know that I can root using ping pong on the 5.02 as well as flash ROMS using FlashFire. I did this with no issues with my AT&T 920a.

diamonddaveb said:
Again this is an SM-G920i.
Some things that I wold like to do with this phone, and it looks like I can with th 5.02.
Root
TWRP
Custon ROMS
Should I just ignore this update 5.1.1 update and work with the 5.02? I know that I can root using ping pong on the 5.02 as well as flash ROMS using FlashFire. I did this with no issues with my AT&T 920a.
Click to expand...
Click to collapse
If you want root just root then freeze the SDM using titanium backup. If you don't care about root take the update. It you want root then later want to unroot, first root, then, when you no longer want root, use Odin to install the latest stock firmware

Snowby123 said:
If you want root just root then freeze the SDM using titanium backup. If you don't care about root take the update. It you want root then later want to unroot, first root, then, when you no longer want root, use Odin to install the latest stock firmware
Click to expand...
Click to collapse
I understand all of that completely. I tried to root via pingpong, but I was not able to install the apk. Message said App not Installed. I'll fuss some more about why the pingpong apk won't install.
---------- Post added at 08:05 PM ---------- Previous post was at 07:43 PM ----------
I rooted the phone via PingPong.

Dbeayon said:
I understand all of that completely. I tried to root via pingpong, but I was not able to install the apk. Message said App not Installed. I'll fuss some more about why the pingpong apk won't install.
---------- Post added at 08:05 PM ---------- Previous post was at 07:43 PM ----------
I rooted the phone via PingPong.
Click to expand...
Click to collapse
Since you got root, Freeze or uninstall the SDM (System Updater).
That way you will no longer receive notifications to update!

Unable to root my oneplus 1

Hi guys, any idea why im being unable to root my device??
Ive tried with a normal process and also with kingo root
Its a one+ 1 with os 5.1.1 and CM 12.1 but the CM its also not properly installed, I downloaded the root checker app abd it says my device is not rooted.
Please help!!

Only there are 3 steps for rooting
1) unlock bootloader,
2) flash latest twrp recovery
3) then root with supersu .
After lollipop the apk roots are not working, but they show fake adds, don't believe them.

In Settings- Developpers options - remove Update Cyanogen recovery
And in SuperSU - remove Respect CM root settings

I rooted mine half an hour ago with king root. Had the January patch on
---------- Post added at 07:34 PM ---------- Previous post was at 07:31 PM ----------
drmuruga said:
Only there are 3 steps for rooting
1) unlock bootloader,
2) flash latest twrp recovery
3) then root with supersu .
After lollipop the apk roots are not working, but they show fake adds, don't believe them.
Click to expand...
Click to collapse
King root works. I have full SU and BB . Adaway, etc working,reason for doing it. I spend a fortune on paid apps and I'm sick of the intrusive ads on ones that won't charge

Unable to do it
Thanks guys I've tried all these options you are sharing, but had no success
By default my one+ should be rooted with cianogen right?
But the root checker app shows that it's not properly rooted
Tried with kingo root and didn't work.
Also from developer options unchecked the update cm option and flashes the recovery and erased it and nothing

SuperSU - There is no SU binary installed, and SuperSU cannot install it.

Hi
I use a Samsung Galaxy Note 4 (exynos) which I recently updated to Marshmallow (6.0.1). The update was a success through Odin and after that I was able to root and install TWRP 2.8.7 did a back up and later upgraded to TWRP 3.0.1-0 which at this point is only accessible through home, volume + and power button and not Quick boot as I was previously able to.
1. Somehow I lost root access and can't figure if out if I should revert back to TWRP 2.8.7 IS THAT THE PROBLEM?
2. Should I re-root manually (don't even know what this means as I can only assume using Odin)?
I've tried to uninstall SuperSU AND and reinstall as some forums had suggested to no avail.
I realized this problem when I didn't get prompts to grant access to certain apps and when I opened the actual SU app I got the message ,
'' There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 5.0, you need to manually re-root- consult the relevant forums for your device!"
I have researched and read all types of related solutions but none that talks abut this particular issue... Am I alone out there, please assist as I'm about to wipe the entire phone and stick to basic android, which will see me die of boredom.

I have same problem as well. Tried unintalling and reinstalling SuperSU but the problem still the same. I even flash the AutoCFroot, but still no luck.
Please help

Hi @rxk since I was impatient for responses I figured I had no option but to redo the process from scratch... so I wipe the cache and did a factory reset.
Reinstall the official marshmallow 6.0.1
Used CF-Auto-Root-tre3g-tre3gxx-smn910h for root access
Installed TWRP 2.8.7 instead of the I previously had 3.0.1
I just restored my backup everything was working fine for about 20 mins and we're back to square one. Depressed.

Download another super su version.zip and flash it through recovery.some su versions I used had this problem

Thanks I installed BETA-SuperSU-v2.72-20160510112018 and it worked perfectly for me.

Glad it worked for you

I also get the error above and need to update Super SU. When I go to recovery I have 3 options to install. Through ADB, External storage or Cashe.
How to proceed? The recovery is not TWRP but Android recovery. Thank you

The problem is with su version .pls try another version su version. Download another su version.zip and flash it through recovery

[email protected] solution worked for me... I tried a few other versions of the su and found one that worked well. I wonder what happend to his/her "thanks" button thou.

When I go to recovery I have 3 options to install. Through ADB, External storage or Cashe.
I don't know which option to follow.

I dont think that there is samsung stock 6.0 SU release... if you need root access then revert back to 5.0... or you can flash a custom ROM

I'm running an eRobot 6.0.1 custom rom, installed BETA-SuperSU-v2.72-20160510112018 and it worked perfectly for me.

Just start from square one .download a another version SuperSU.zip file and flash it in recovery
Just forget about the other 3 options
---------- Post added at 11:11 AM ---------- Previous post was at 11:11 AM ----------
@gizomot ikr lol

I'm sorry, I don't understand what to do.

Just download a super su.zip file say betasupersu2.52 .zip .now head on to recovery click install and install the 2.52.zip
https://drive.google.com/file/d/0B-CJc5WWY-robUtYQ0dscDJqS00/view?usp=drivesdk .
Is there a option install from zip in your android recovery then go ahead and install the above file if not try twrp or cwm

i have the same problem just like you.
i have a nexus 5 and lately l've flashed nougat Aosp 7.0
and it's running fine,afyer that i flashed supersu.zip and regained root access,then installed busybox which asked me to disble an option that has to do with scanning supersu.
i confirmed yes,my phone rebooted,and then i figured out that i lost root cuz Supersu says ''Su binaries aren't installed and supersu can't install them.
i tried reflashing several versions of supersu via recovery(twrp) including v2.76, v2.77 ,and v2.78
it says succesful.
but when i reboot,no supersu in app drawer,an eeven if i install it from play store,the pop-up window saying no su binary is installed is still there.
please heeeelp help Sos ? ?
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
i have the same problem just like you.
i have a nexus 5 and lately l've flashed nougat Aosp 7.0
and it's running fine,after that i flashed supersu.zip and regained root access,then installed busybox which asked me to disble an option that has to do with scanning supersu.
i confirmed yes,my phone rebooted,and then i figured out that i lost root cuz Supersu says ''Su binaries aren't installed and supersu can't install them.
i tried reflashing several versions of supersu via recovery(twrp) including v2.76, v2.77 ,and v2.78
it says succesful.
but when i reboot,no supersu in app drawer,an eeven if i install it from play store,the pop-up window saying no su binary is installed is still there.
please heeeelp help Sos 😁 😀

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!