Database Info

[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!

I have a Verizon pixel unrooted lock but on NDE63V. How do I get npf26j?

my verizon some how has the playstore rom NDE63V and not the X like most verizon models. How do I apply the newest update OTA?

Download the OTA and sideload it through the stock recovery with a computer. Reboot. Done.

There are a ton of guides online showing you how to sideload an OTA. It's fairly easy, the hardest part is usually just making sure you have your adb drivers installed.
I used the AndroidCentral guide here: https://www.google.com/amp/amp.androidcentral.com/how-manually-upgrade-your-nexus

If I already have TWRP (bootloader unlocked through depixel8) and am rooted, will flashing the zip through TWRP simply apply an update and let me keep TWRP and my previous data?
Edit: Read up a bit more. Seems like you'll need to be on 63V and then sideload the update (not through TWRP).

ota updates with root and a linux host?

Ok,
I have fastboot and adb working on my linux mint host. Can someone explain to me how to install ota updates on a rooted pixel phone? I tried installing it via the zip using twrp and that didn't work. It just unrooted my phone so I had to reroot it. I tried using Flashfire and downloading the ota update and then using flashfire to detect the ota update and flash it and everytime it doesn't work... errors and then unroots my phone.

I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.

bush911 said:
I never succeeded in OTA on my rooted pixel. I always download the full image then do upgrading via fastboot or flashfire.
Click to expand...
Click to collapse
Ok, I downloaded the ota update via Google's webiste. Flashed it with flashfire. It asked if I would like to overwrite the boot and recovery. (said it would most likely fail if I didn't.) I told it ok. It flashed for a while. Rerooted automatically. It booted back up. It didn't update. Still prompting me to update ota.

I just tried the second method in this article
https://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.

Which version of SuperSU are you trying to use? Both of the following links discuss verified boot, which is one possible item you could be running into with the latest Pixel updates.
SuperSU v2.82-SR1 is the latest version, and it added boot signing.
https://plus.google.com/+Chainfire/posts/XikxTkhHpiG
If you are using an older version of SuperSU, then you will need to sign the boot image. I installed the latest Pixel update before v2.82-SR1 was available, so I just had FlashFire install the OTA, and then I added the following zip to the list of FlashFire actions immediately after it was set to root the phone again. FlashFire worked without issue to update to the latest release for June by adding the following before rebooting when using a version before SuperSU v2.82-SR1.
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606

I am attempting to flash 2.79. but immediately after, I flash the verifiedbootsignerv3.zip

How to root my phone"
Sent from my itel it1408 using XDA Free mobile app

yared1212 said:
How to root my phone"
Sent from my itel it1408 using XDA Free mobile app
Click to expand...
Click to collapse
Not sure what you mean here...

dorlow said:
sailfish-n2g47e-factory-00a46e7e.zip
Then used flashfire to flash it like the article states. No error but my phone is still prompting and trying to update via Ota.
Click to expand...
Click to collapse
That looks like an April update, and there are newer versions, so I'm not surprised the phone would try to update.
https://developers.google.com/android/ota
Three months ago was the first time I tried FlashFire, and I couldn't get it to use the OTA to the phone at that time. Some of the FlashFire instructions made me think I might need to use the backup option to get the OTA to work, but I was actually able to take the May and June OTAs using FlashFire without the backup option. I'm not sure why FlashFire didn't work for an OTA in April, while it did work with an OTA on the phone the past couple months. I think I may have ended up using a download from the Google site with FlashFire in April, so my only guess was that either using the Google download or a newer version of FlashFire is why I was later able to use the phone OTA with FlashFire for May and June.
SuperSU v2.79 SR3 with either the VerifiedBootSigner v3 or v8 has worked for me in May and June, and then I've taken the Play Store SuperSU update to v2.82. I don't have TWRP installed, and I get the impression there could be some extra steps for FlashFire when TWRP is installed, so I don't have to deal with that. Of course the only reason I switched to using FlashFire is because it seems like the quickest method to just take an OTA and update with SuperSU. If FlashFire didn't work so easily, I'd just go back to sideloading, or using one of the other update methods.

T-Mobile IN2017 Root Method?

All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.

SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.

You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.

stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!

BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.

SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.

stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?

There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3

cannot root S10e

Hi all,
I used to have my S10e rooted, at some point root was lost, I've never figured out why. So today I tried to obtain root again.
My bootloader is (still) unlocked, (greyed out, says already unlocked). I've tried 4 or 5 different methods or guides. I've tried downloading the latest Q firmware, installing it, copying the AP to device, patching that with Magisk, then install the patched AP.
I've tried several guides of installing TWRP first, from crDroid and lineage, but nothing works.
Whenever I try to install either TWRP or an rom with root, Odin either stops without any message, or just says "failed". I've seen "only official released binaries are allowed to be flashed" on my phone in download mode screen while trying to install patched ROMs. I've been able to install something, but then got "invalid kernel length" while booting.
I've been really strict with following the guides. but none of them gave me rooted phone.
Is there anyone who can give me a pointer into the right direction? I'd like to install crDroid, but I'm not able to get TWRP running, which is one of the first steps.
Thanks in advance!

which TWRP version did you try