Database Info

SuperSU needs to update binary

Just updated my Nexus 5 using the OTA thread that went through fine,
I then proceeded to update SuperSU using the following link: http://download.chainfire.eu/supersu which was the update v1.99r3.
Using TWRP I flashed this and root is working for most apps i have tested: titanium, adblock, root explorer. So root is back.
However whenever I load up SuperSU I keep getting the following message: "The SU binary needs to be updated. Continue?"
So of course I have done this and let it use TWRP to flash. Let the phone boot up and upgrade the app as it needed. However on next load up of the app it asks to do the same yet again.
I feel as though I'm forgetting something as it's been a while since I've done this. ( use to live on flashing when i had my SII)
My Nexus is Stock ROM. CF-Auto Rooted. TWRP Recovery. Nothing else is modified.
Help would be appreciated, even though I don't go into supersu all that often anyways.
Cheers all.

What if you upgrade it using the "normal" method?

If I do a normal install i get the following:
Installation failed!
Please reboot and try again.

brichardson1991 said:
If I do a normal install i get the following:
Installation failed!
Please reboot and try again.
Click to expand...
Click to collapse
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?

rootSU said:
That message is usually indicative of not having root in the first place. What if you flash it via TWRP then do it normally? Could TWRP be removing it with its "Fix root" option?
What about other recoveries? Do they allow root to stay?
Click to expand...
Click to collapse
How odd like I said my apps are all receiving their root permissions...
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
I don't have any other recoveries on my phone, so I wouldn't know about that last option.

brichardson1991 said:
How odd like I said my apps are all receiving their root permissions...
Click to expand...
Click to collapse
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Have you tried other binary download?
brichardson1991 said:
What file would we be talking about flashing? The Temp one SuperSU makes to flash when you click install via TWPR?
Click to expand...
Click to collapse
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
brichardson1991 said:
I don't have any other recoveries on my phone, so I wouldn't know about that last option.
Click to expand...
Click to collapse
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.

rootSU said:
Are they though? SuperSU grants permissions but if the binary is not present, its irrelevant. Can you actually do root things with the root apps that have the permissions?
Click to expand...
Click to collapse
It does seem that way Titanium has backed up an app just now, adblock has updated and Nova is hiding the time on the first screen.
rootSU said:
Have you tried other binary download?
Click to expand...
Click to collapse
No, I shall give a older one a try.. Tried 1.97 as well and to no luck.....
rootSU said:
In SuperSU, do the TWRP flash install of the binary and reboot, then try the "normal" install immediately after
Click to expand...
Click to collapse
This failed to do anything just got the install failed again.
rootSU said:
Theres a link in my signature to Philz recovery. In the settings is a root option, so the recovery itself can root without flashing any zips. Maybe try that if downloading an older flashable zip or the above hasnt worked.
Click to expand...
Click to collapse
I assume this would override TWRP recovery?

brichardson1991 said:
I assume this would override TWRP recovery?
Click to expand...
Click to collapse
Yes it would. You can always flash back to twrp afterwards

rootSU said:
Yes it would. You can always flash back to twrp afterwards
Click to expand...
Click to collapse
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app

brichardson1991 said:
Well considering that worked and I now can get into SuperSU I think I will stick with Philz. Even if I paid for the TWRP app
Click to expand...
Click to collapse
Good news. The latest version of Philz, s it is CWM based - uses the latest Cyanogen sources to build. I update the CM sources everytime I build Philz so hopefully there should be fewer issues when new stuff comes out.

Any way to root without installing TWRP

Hi everyone
I've just received my Honor 8 and I would like to root it without installing TWRP (or any other recovery than stock one) to receive further OTAs.
Is there any way? I tried Kingroot but did not work.
Thanks

I haven't tried this, but you should be able to do a systemless install of TWRP, root the phone, then re-install the stock recovery.

Hi, thank you for your answer.
I tried this. I reinstalled stock recovery (found in a UPDATE.APP file). But now, my device fails to do OTAs.

Does it notify you they're available, but fail to install? Or is it not seeing any updates?
I haven't been able to do much experimentation because there's not TWRP backup for my L04 yet, and I don't want to leave myself in a bad state without a restore option. I'm probably going to hold off on any updates (I'm on b140 now) until I have a fully working TWRP.

I had a notification and, when it did reboot, it failed. Now, it doesn't see any update. I am on b101.

Finally, I downloaded frd-L09c432b120 from here.
I followed these instructions: (http://forum.xda-developers.com/showpost.php?p=68695798&postcount=2)
DigiGoon said:
Steps are below, follow them.
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
...
Click to expand...
Click to collapse
I stopped there!
Rebooted my phone (no wipe done) and got a notification for an update.
The update succeeded (I'm now on B120).
But now, bootloader is locked again. So, it will wipe my phone when I will root it (locking bootloader first). So, I'm really looking for a solution to get OTAs on a rooted phone. Even if I will have to root it again, but without loosing lock on bootloader.

Isn't it possible to disable the device encryption so that you can avoid having to wipe it every time?

evilpaul13 said:
Isn't it possible to disable the device encryption so that you can avoid having to wipe it every time?
Click to expand...
Click to collapse
How can I do this?

Florent06 said:
Finally, I downloaded frd-L09c432b120 from here.
I followed these instructions: (http://forum.xda-developers.com/showpost.php?p=68695798&postcount=2)
Flash all other extracted files similarly firing these commands.
...
I stopped there!
Rebooted my phone (no wipe done) and got a notification for an update.
The update succeeded (I'm now on B120).
But now, bootloader is locked again. So, it will wipe my phone when I will root it (locking bootloader first). So, I'm really looking for a solution to get OTAs on a rooted phone. Even if I will have to root it again, but without loosing lock on bootloader.
Click to expand...
Click to collapse
I suggest to not do any OTA's. For all we know, an OTA can make it harder to root.

The thing might not work with a new official release is the recovery. And looking to other devices that has not been the case.
Just don´t encrypt the phone as it makes much harder to update. Also might mess up the timed on/off function.

Rooting without TWRP must be really hard.
Sent from my honor 5X using XDA Labs

I know only one way of rooting without twrp and that is to use KingRoot or a similar app/software.
It messes up the phone pretty bad and makes it a headache to get OTA in the future.

muradulislam said:
I know only one way of rooting without twrp and that is to use KingRoot or a similar app/software.
It messes up the phone pretty bad and makes it a headache to get OTA in the future.
Click to expand...
Click to collapse
Well root itself will cripple OTA updates. Using Kingroot is really not recommended due to compatibility issues. So SuperSU is the best choice.
Sent from my honor 5X using XDA Labs

adriansticoid said:
Well root itself will cripple OTA updates. Using Kingroot is really not recommended due to compatibility issues. So SuperSU is the best choice.
Click to expand...
Click to collapse
I should have highlighted HEADACHE in the above post. With SuperSU or magisk, it's super easy to enable/get OTA again but not the same with KingRoot.
And the bootloader unlocked by KingRoot has to be unlocked again, using official method, to be able to flash desired images for a complete unroot.

muradulislam said:
I should have highlighted HEADACHE in the above post. With SuperSU or magisk, it's super easy to enable/get OTA again but not the same with KingRoot.
And the bootloader unlocked by KingRoot has to be unlocked again, using official method, to be able to flash desired images for a complete unroot.
Click to expand...
Click to collapse
I once rooted my father's Honor Holly with Kingroot. Damn. Never again. Haha.
Sent from my honor 5X using XDA Labs

adriansticoid said:
I once rooted my father's Honor Holly with Kingroot. Damn. Never again. Haha.
Click to expand...
Click to collapse
Messed up partitions didn't it?

Tmobilefan906 said:
Messed up partitions didn't it?
Click to expand...
Click to collapse
Yes! I rooted it with Kingroot and tried to flash a custom recovery through Flashify. The recovery partition got corrupted and I can't flash anything to it anymore.

adriansticoid said:
Yes! I rooted it with Kingroot and tried to flash a custom recovery through Flashify. The recovery partition got corrupted and I can't flash anything to it anymore.
Click to expand...
Click to collapse
You can fix it

I think i can help you
You should use FRAMAROOT
link to download this is given below :
https://framarootappdownload.net/;);)

Tmobilefan906 said:
You can fix it
Click to expand...
Click to collapse
How?
Sent from my honor 5X using XDA Labs
---------- Post added at 09:38 PM ---------- Previous post was at 09:36 PM ----------
kbhatia1 said:
You should use FRAMAROOT
link to download this is given below :
https://framarootappdownload.net/;);)
Click to expand...
Click to collapse
Framaroot isn't updated anymore.
Sent from my honor 5X using XDA Labs

[solved] June updates are out, but which one?

Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.

CatThief said:
[solved] Which June factory image is for the "everything else" devices... NHG47N or NHG47B?
Edit: Sorry, just figured it out, but it took info from another site other than Google's to find out that "N" is for Verizon and "B" is for everyone else.
Click to expand...
Click to collapse
There's actually 4 different builds.
See here for what's what

Yep, I did that. There is no description there for "N" but I found out "B" is the one I want.

I always get Failed to udate, try again when installing the ota via settings.

Juli112 said:
I always get Failed to udate, try again when installing the ota via settings.
Click to expand...
Click to collapse
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.

alluringreality said:
Have you unlocked the bootloader and modified the phone in any way? Personally I've rooted my phone with SuperSU, so I've been using FlashFire to install the OTA.
Click to expand...
Click to collapse
Did you update already. I read somewhere since the may update that if you have bootloader unlocked, rooted, and another kernel you get bootloops?
Is that true? I'm still on April security update and been using stock rom, just unlocked bootloader, rooted, and using elementalx kernel

I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435

I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.

alluringreality said:
I still have the May update on my phone, so I was just reading what people were saying about June before installing. According to posts like the first link, the current version of SuperSU does not sign the boot image. Signing the boot image as the last step is reportedly needed to avoid bootloops for the May or later bootloader. If someone is just using SuperSU, they can use the zip from the second link after SuperSU, which is what I did for May.
https://forum.xda-developers.com/showpost.php?p=72451572&postcount=1357
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't use ElementalX, but I've read a few posts indicating that it will also sign the boot image when installed last.
https://forum.xda-developers.com/showpost.php?p=72181714&postcount=1435
Click to expand...
Click to collapse
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!

Nope. twrp.img must be firstly boot into the phone, then via this temporary twrp,you can install twrp.zip from your phone.
kazemitsui said:
hey thanks i got everything up and running with the new June OTA. but what do you use to reflash TWRP?
flashify just freezes i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse

CatThief said:
I did a flash-all (with -w removed) of NHG47B, then booted TWRP where I installed SuperSU and also VerifiedBootSigner-v8.zip before rebooting and everything is working fine.
Click to expand...
Click to collapse
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?

TENN3R said:
Twrp rc1 or rc2?
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I used twrp-3.0.2-0-RC1-fastboot-sailfish.img because it was the only version that was stable for me from the start. When the January update came out I tried the current TWRP at that time (it was an RC3, can't remember the version) and while others had no problems I had an experience of my own that I'm not keen on repeating.
As for SuperSU, I installed SR5-SuperSU-v2.78-SR5-20161130091551.zip then updated to the latest 2.82 from Google Play.
I know​, newer releases may work now, but I was only going to try something newer if my "old" method failed. Like I said, I only boot to TWRP, I don't​ flash it. I just want root.

kazemitsui said:
i tried to use flashfire to install the twrp zip and that failed, im still on stock recovery. Is there a way to do this without having to plug the phone into my pc? thanks!
Click to expand...
Click to collapse
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
TENN3R said:
Supersu 2.82 or 2.79rc3?
Click to expand...
Click to collapse
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.

alluringreality said:
When you tried installing TWRP with FlashFire, did you put the boot signer after TWRP? The TWRP install has to be signed with the current bootloader. The FlashFire documents make it seem like it should be able to install TWRP, but I haven't tried installing TWRP and can't find any relevant posts, so I suppose it might not work.
https://flashfire.chainfire.eu/actions/zip/
Personally I've just been using the small OTAs that come to the phone the past few months, but the following post indicates that FlashFire can at least retain a previously-installed version of TWRP without issue.
https://forum.xda-developers.com/showpost.php?p=70929003&postcount=8
I had installed 2.79 RC3 with the May update, and then I had taken the play store update to 2.82. When I did the June update with FlashFire I'm guessing it must have went back to 2.79 RC3, because I got the update message again. I haven't seen anything to suggest either is likely an issue with the Pixel.
Click to expand...
Click to collapse
I just flashed TWRP through my computer I couldn't bother trying to figure out if FlashFire will flash TWRP or not haha

How to Root J7 Prime (G610F) on Nougat?!

Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.

vishnurmcf said:
Hello Guys,
Updated my J7 Prime to Nougat today. Is there anyway to Root this device on Nougat?! Please replay.
Thank You.
Click to expand...
Click to collapse
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.

anubhab723 said:
Not yet. Better wait for a couple of updates from Samsung & then try to root. I would recommend Magisk for rooting.
Click to expand...
Click to collapse
man i need a working root i... tried by twrp by install the root latest version so now i am flashing a stock firmware hhhhhh ....will magist work 100 percent ?? i need the full confidence answer thanks a lot

lI also just updated, I tried using CF Auto Root but that didn't work and made my phone bricked (verification failed). Will Magisk work certainly because I don't want to have to reset again.

Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Sent from my SM-G955U using XDA-Developers Legacy app

fast69mopar said:
Get your device back to a fully stock state and then start fresh by installing TWRP. Next, I would suggest making a backup of your stock ROM in TWRP just in case something goes wrong and you need to restore your boot image. Then, I would attempt to root your device with an older version of Magisk, like V12.0, and see what happens. If you have root, great, if not, restore your stock boot image and flash the next newest version of Magisk. That would be my starting point. Good luck and happy flashing!
Click to expand...
Click to collapse
Will try that. Thanks!

wsty said:
Will try that. Thanks!
Click to expand...
Click to collapse
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask

fast69mopar said:
Sounds good. Let us know how it works out if you run into any trouble no hesitate to ask
Click to expand...
Click to collapse
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?

wsty said:
I have some questions.
1. Do you need the specific Magisk file for your device or does Magisk work for all devices regardless of the variant?
2. Do you know where to get Magisk 12.0?
Click to expand...
Click to collapse
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Before you flash any root zip in TWRP, make a backup of your stock boot image. That was ifsomething goes wrong you can revert back and try again with a different version if Magisk.
Make sure you read the info that @topjonwu has made available for us for Magisk. The link below is full of information pertaining to Magisk.
There is one other thing that I forgot to put here. Magisk is a pretty universal root solution that patches the boot image just like Chainfire's SuperSU. There is not a device specific Magisk zip so you can flash any version if Magisk to attempt to gain root access in your device. Like I said before, I would start with flashing V12.0 and start from there. If V12.0 works and you have root, boot to TWRP and make a backup of your boot image to save it. That was if you flash, for instance, V13.0 and it doesn't work or fails to flash then you can boot back to recovery and restore your boot image and have working root.

fast69mopar said:
Magisk works on almost all variants. The will need to flash the Magisk zip and then install the Magisk Manager apk.
Here is the link to the Magisk main thread. If you scroll down the the bottom of the OP, you will see the download link for the Magisk zip files. Also the Magisk Manager apk's are available in this thread too. If you need any help just ask.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks!

wsty said:
Thanks!
Click to expand...
Click to collapse
No problem

Any working Twrp for this?

Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...

denizbay said:
Yes, I am having the same problem. I tried two different ROOT files, but it did not work.
What is Magisk? Someone can explain ...
Click to expand...
Click to collapse
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app

Looking this: https://forum.xda-developers.com/ga...ared-root-file-j7-prime-g610f-nougat-t3678253

inamie said:
Magisk can hide knox counter... using working twrp for Nougat... format data.. install magisk v14 & done. The only problem now, twrp cant read external storage, so cant flash anything thru sdcard, need to use OTG instead.
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app

inamie said:
Downloaded the TWRP from somewhere and follow the above step. Succesfully rooted my device..
Sent from my SM-A910F using XDA-Developers Legacy app
Click to expand...
Click to collapse
What Magisk version, Version 14 tripped the verification error on my 610M

Try Magisk v14.0
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-sys

FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.

vishnurmcf said:
FINALLY !! I've rooted my J7 Prime on Nougat. Will post a thread on it very soon.
Click to expand...
Click to collapse
Looking forward to your instructions. Please release soon! Thank you!

SOLVED: Flashed Magisk zip from TWRP but no root

Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
If starting fresh from November (.A1.) Update
Install November update
Download latest Magisk Beta (17.3) and move it to the internal storage of the device
Reboot to bootloader
Download the .img version of TWRP for "crosshatch"
In the location of downloaded TWRP .img, open cmd and enter
Code:
fastboot boot twrp-3.2.3-1-crosshatch.img
Allow twrp to boot (this will take a minute or two)
Then go to install and install the Magisk zip
Reboot and find magisk manager and make sure it says you're rooted
Until there is an update to the patched_boot.imgs, dont follow the how to beyond this point. In fact I am hiding it for the time being.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-root-pixel-3-xl-magisk-t3856712#login
Click to expand...
Click to collapse
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?

JJT211 said:
Sorry, its been quite a while since ive rooted and im new to Magisk. Im currently on November .a1 update. I followed the below tutorial
But I do not see the "MAGISKSU (topjohnwu)" at all. I feel like there's more to root than just installing Magisk from TWRP. I see an "Install" but am hesistant as I bricked my phone last time I tried this.
What am I missing?
Click to expand...
Click to collapse
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?

TonikJDK said:
It is just flash the zip from TWRP. And based on that screenshot it looks like you are done. What happens when you try and do something that requires root?
Click to expand...
Click to collapse
I usually verify root by downloading root checker app. App says that I'm not rooted.
EDIT: Nevermind, I tried it again and now it says I'm rooted. Thanks!