Database Users

Towelroot work??

I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk

Used it installed safestrap and when it reboots get the unlock symbol on the boot screen
Sent from my SM-N900V using XDA Premium 4 mobile app

Works fine on my device. For the unlock symbol, download latest SU and updated binaries. That will go away.
Sent from my SM-N900V using Tapatalk

Definitely works for getting root. Rooted, installed SuperSU, Xposed, SafeStrap all successfully. Now struggling to get a rom to work (tried Eclipse & Hyperdrive). Both say they install successfully via SafeStrap and then hangs on boot up. I've seen one other post on the Eclipse thread for the same problem, so it might be something to keep an eye on.

i can verify that this method works. i just installed superuser and it works flawlessly. the only thing is make sure to download the superuser app from here so you have the updated binaries: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip

re
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??

lazygregg said:
i have root access verified w/root checker
downloaded v1.99r4.zip and installed it
when i open it it asks for me to update binary and it fails installation
any ideas or workarounds??
Click to expand...
Click to collapse
Rerun towelroot

re
drewcam888 said:
Rerun towelroot
Click to expand...
Click to collapse
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails

lazygregg said:
i've done that multiple times...
reran towelroot, it reboots phone..open supersu the version that i downloaded earlier from the website and try to download supersu binary and it fails
Click to expand...
Click to collapse
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.

exaltedgod said:
I seem to be in the same boat as well. Things I have tried and it still does not work:
Installed Play Store Edition
Installed 1.99r4
Installed 1.99r5
All of them are saying I need to update binaries. While I am technically rooted and can grant permissions to apps, I need to get into SuperSU so I can modify some settings.
There are several others have issues on Reddit as well, so its not a couple of people.
Click to expand...
Click to collapse
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Sent from my SM-N900V using XDA Premium HD app

Dc4479 said:
Try this. Install safestrap 3.7x. Open it, give su permission, install recovery, hit the home button. Open supersu, update binary thru cwm/twrp. Don't click to reboot phone into recovery from supersu. Hold down home and bring safestrap back up. Reboot to recovery from there and it should update the binary. Hope this helps.
Click to expand...
Click to collapse
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:

exaltedgod said:
This is being very peculiar. After I installed Safe Strap, SuperSU went fine, able to get in and do what I needed to get done. I reboot into recovery. Made a backup, and rebooted system. Went right to SuperSU again. And the same issue occurs, constantly asking for updated binaries. I am trying everyone once more to make it all work. If not, then I will just stick with what I have and hopefully it doesn't cause any other issues.
Thank you for the help thus far. :good:
Click to expand...
Click to collapse
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.

pmt223 said:
Yeah I just did all this last night...I installed SafeStrap and installed Recovery, then went into SuperSU and clicked Normal when asking for updating Binaries and it hasnt asked again thankfully. All of this of course was after installing BusyBox from the Play Store.
Note though: Safestrap isnt working for flashing roms just yet, just like someone else said here, and someone else said this in the Jasmine Rom forum. I just tried it myself and everything looks fine when installing, but then when you boot up, screen goes black and unresponsive after the SS splash screen on a reboot. Hopefully we have an update to SS soon. Fair warning - make sure you create a backup of your System/Data, etc in SS before messing around...it makes it so much easier to restore in case something screws up.
Click to expand...
Click to collapse
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!

emtownsend said:
So, can someone enlighten me on what this "root" does? I've been running SafeStrap 3.72 with HyperROM 8 and just yesterday, successfully installed Towelroot on my Verizon Note 3. I downloaded the new SU to my SDcard before running Towelroot and was able to run it immediately after root and all looks good. But... what did I actually gain? Can I now install Cyanogen or others? I am a bit fuzzy on the difference, if any, on a rooted phone vs. an unlocked bootloader. Those of us on the Verizon retail Note 3 still don't have unlocked bootloaders do we? I miss the ease of playing with my old S3! LOL. Thanks!
Click to expand...
Click to collapse
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.

pmt223 said:
No, you dont gain an unlocked bootlader. At this point, only the Almighty will make that happen lol. For us with Verizon Notes (and some others), this helps the folks who either a) dont want to use Kingo or the other web methods, and b) folks who were on stock 4.4.2 NC4, like from an OTA (like me). This now gave me root, where when the OTA came out people were fearing there would never be a root for it (thanks to everyone else who put monies towards a bounty). Many people as well as myself cannot use SafeStrap successfully to fully flash a rom yet (you'll see this remarked in a lot of places), so Im sure there is an update forthcoming. In the meantime, I can use TB and freeze/uninstall a lot of the bloatware crap, and use Xposed for whatever else, which is fine by me. But no, we are still a no-go on full rooting and unlocked bootladers like on some other phones, which means no CyanogenMod, etc.
Click to expand...
Click to collapse
Ah. Got it. Thanks!
* I successfully used SafeStrap to install HyperROM 8 on slot 1 only, so I had to lose my stock ROM, but I'm OK with that.

cnotes2019 said:
I know outside of Att note 3 it hasn't been confirmed to work but wondering if anyone tried it on other note devices? Thanks.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
i rooted today with towelroot. i have a verizon note 3 on 4.4.2

Magisk

Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.

tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
Was wondering about this too. Not entirely confident about what things to reflash in case things go wrong otherwise wouldve tried this.

So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?

reddrago said:
So just took a risk and tried it and the phh's SuperUser didn't provide root. Might have to do something with how the latest SuperSU doesn't work either?
Click to expand...
Click to collapse
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...

tdgillihan said:
Has anyone tried Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382) on the A7 yet? I'd love to be able to root and still have ability to use Android Pay.
Click to expand...
Click to collapse
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.

piskr said:
I've tried it on my Moto X Play. Magisk and Xposed have no influence on Android Pay. But rooting (Phh's SU with Magisk) caused SafetyNet test turned red. It looks like Google suceeded to eliminate any coexistence between root and AP.
Click to expand...
Click to collapse
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?

tdgillihan said:
Did you try using AP or check with SafetyNet after flipping the switch in Magisk to show it as unrooted?
Click to expand...
Click to collapse
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.

ultramag69 said:
Chinese A2017 it worked... But I used the super user app as suggested by Tenfar on his rooting guide...
Click to expand...
Click to collapse
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.

piskr said:
Just ran SafetyNet and reverted to unrooted after. As far as I know failing with SafetyNet means that AP won't work.
Click to expand...
Click to collapse
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.

tdgillihan said:
The whole point of this is that you flip the switch and you're temp unrooted for whatever duration you chose. 5min is default I think. If you didn't try that then you never really checked to see if it would work before dumping it.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.

piskr said:
Ok, thanks, I'll find the time to try it again. But temporally unroot with Chainfire superSU didn't help. I used superSU without Magisk though, it was systemless and it worked with AP in the beginning. Seems that AP checked only system changes then. It worked till recently when Google obviously cut off AP from rooted phones.
Click to expand...
Click to collapse
If you're running a custom ROM it may or may not work. Some are saying it does and others not. But if we're talking about the A7 here that'll be stock for now.
Always thank those who are helpful...and just ignore those who aren't.

tdgillihan said:
Really? Hmmm, that's weird. Have you confirmed root and have you tried AP?
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...

ultramag69 said:
I'm using apps that require root, have the sd card fix done so EVERYTHING can use the sd card, file managers can't usually move or delete files on unrooted device, use clocksync so I have accurate time and have titanium backup installed. Haven't played with titanium backup but everything else works brilliantly...
Used Root Checker by joeykrim and it confirmed root...
It is phh's SuperUser app on playstore. Seems to work fine...
Click to expand...
Click to collapse
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.

tdgillihan said:
Wait, are you saying that the su in tenfars locked bl root is phh's? I didn't know that. That's good, then when he gets it working for the 2017u this should work on it as well.
Always thank those who are helpful...and just ignore those who aren't.
Click to expand...
Click to collapse
Don't know , I just downloaded the root manager Tenfars recommended from play store...
It works fine...

Are there any new reports on this subject? I have been able to successfully install Magisk and PHH SU on a Nexus 6P , but using the identical procedure on my Axon 7 (U) does not work. I am puzzled.

Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.

lokissmile said:
Magisk installs fine (busybox is detected) on A2017U but root + Magisk does not work. Going to keep testing some options and methods and I'll let you know.
SuperSU fails during install after extract.
phh-superuser install completes but no root.
Click to expand...
Click to collapse
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?

lokissmile said:
No luck so far, my gut thinks it's an issue with the kernel / boot.img patch. Sorry guys I'm going to keep banging on this one but it might take me a bit as I don't have a linux box up right now. Can someone that has a Chinese model get me a copy of the patched boot.img?
Click to expand...
Click to collapse
that's my thought too, since magisk seems not to create a log in /cache as it should and doesn't reaveal itself via logcat it looks like it doesn't realy get executed.
The guys in the common magisk were not realy able to help, guess we have to dig more into the init.rc script / boot.img patch. But might be that it get's fixed with v7 anyway, hope @topjohnwu is able to get it done quickly (or maybe has some ideas he how to debug it more, i didn't get an answer from him in the common, probably way too crowded magisk thread - goddamn pokemongo!)

Subscribing. Would like to get this working as well.

Edit: I've gone ahead and opened up a thread so it is easy to find: http://forum.xda-developers.com/axon-7/how-to/guide-installing-magisk-systemless-phhs-t3524270
We're up to Magisk V9 now and it still doesn't work. I'm almost certain it has to do with the execution of the patched boot.img, due to the write-protected /system partition. I finally got it working by using the the method in the guide I posted.

Delete

Delete

Craz Basics said:
I just rooted my galaxy s7 edge on 6.0.1, and it downloaded the nougat update (OTA). I havn't installed it yet, but I was wondering if I use flashfire, will I still have root and xposed? I'm highly doubting xposed but what about root?
Thanks,
Gavin
Click to expand...
Click to collapse
You wont have root or xposed.

Ah, figures. Thanks a ton for the reply though, I thought nobody was going to.

Craz Basics said:
Ah, figures. Thanks a ton for the reply though, I thought nobody was going to.
Click to expand...
Click to collapse
Yea, sadly xposed is not released for nougat yet, so nobody has that.

Ummmm you can root on 7.0 dude. Just update it to 7.0 and then just follow the directions in this thread https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
I can confirm that it is safe to use and works having done it myself, however as for xposed I don't think it's out yet for 7.0 bt I could be misinformed.

TheSproker said:
Yea, sadly xposed is not released for nougat yet, so nobody has that.
Click to expand...
Click to collapse
Do you think it will come out soon?

This is the last I heard on it in January
https://www.google.com/amp/s/www.xd...he-situation-regarding-xposed-for-nougat/amp/

gurnsey101 said:
Ummmm you can root on 7.0 dude. Just update it to 7.0 and then just follow the directions in this thread https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
I can confirm that it is safe to use and works having done it myself, however as for xposed I don't think it's out yet for 7.0 bt I could be misinformed.
Click to expand...
Click to collapse
I am aware, thanks for the reply. I am rooted as well on 7.0 now. How do you deal with the lag? I have the kernel Aduitor app (Sorry, I don't know how to spell it lmao) and both my governors are set to performance. This kills my battery but any other one is a bit too laggy for me. I do have greenify to help me out on standby which is what killed my battery before root.

gurnsey101 said:
This is the last I heard on it in January
https://www.google.com/amp/s/www.xd...he-situation-regarding-xposed-for-nougat/amp/
Click to expand...
Click to collapse
Will check out, thanks!

All good theres a reason i didnt take part in spelling bees haha and Well I set mine to conservative for the kernal aduitor app and make surr you hit the "apply on boot" option on the top and restart your phone (I didn't notice it at first) and it seemed to fix most of the lag as for the battery I flashed debloat script https://forum.xda-developers.com/galaxy-s7/themes/mod-extreme-debloater-s7-root-req-t3335703
either that or try this custom rom that I can confirm works as well and has no lag just follow the instructions carefully
://forum.xda-developers.com/verizon-s7-edge/development/rom-t3603231

gurnsey101 said:
All good theres a reason i didnt take part in spelling bees haha and Well I set mine to conservative for the kernal aduitor app and make surr you hit the "apply on boot" option on the top and restart your phone (I didn't notice it at first) and it seemed to fix most of the lag as for the battery I flashed debloat script https://forum.xda-developers.com/galaxy-s7/themes/mod-extreme-debloater-s7-root-req-t3335703
either that or try this custom rom that I can confirm works as well and has no lag just follow the instructions carefully
://forum.xda-developers.com/verizon-s7-edge/development/rom-t3603231
Click to expand...
Click to collapse
Conservative? That will be hella laggy lol. I have had the "apply on boot" option selected. And the debloat script, would just disabling the bloat work? Because that's what I have done. And I have a qualcomm s7 edge :/
so I don't have a custom recovery and no unlocked bootloader. So I don't think I can flash any ROMs. I did find a T-mobile ROM, but no AT&T (mine).
Edit: I did put it on conservative. Seems okay, just had to get passed startup

Yeah conservative is what I am on and no lag haha and no the debloat script removes things entirely from the system and yes you can flash the rom i linked even on locked bootloader that one is safe to flash just use flashfire and follow the instructions I use a Verizon s7 edge so it's all good you can flash it just make sure you follow the directions to the letter and dont panic if the reboot takes like 10 mins or so it will take a few for it to reboot after flashing

gurnsey101 said:
Yeah conservative is what I am on and no lag haha and no the debloat script removes things entirely from the system and yes you can flash the rom i linked even on locked bootloader that one is safe to flash just use flashfire and follow the instructions I use a Verizon s7 edge so it's all good
Click to expand...
Click to collapse
Is debloat safe?
Also, do I just download the zip and flash in flashfire? As well what version do I download, there are two files

Yes debloating is completely safe as long as you don't unstall key components (the one I linked is safe) all it does is pretty much run an adb command to unstall useless apps like all the google and Samsung apps that we never use that tend to take up space and ram

gurnsey101 said:
Yes debloating is completely safe as long as you don't unstall key components (the one I linked is safe) all it does is pretty much run an adb command to unstall useless apps like all the google and Samsung apps that we never use that tend to take up space and ram
Click to expand...
Click to collapse
Okay, which one do I use? I won't have Wi-Fi soon so I downloaded both, so I can just pick one.

Yes use flashfire. Flashfire is your love flashfire is your life haha and bt first go into super su and go into settings click on "enable su during boot" then use the flash zip OTA option and the make sure you chose the mount/system option and I use the Clean_S7_160319_Ultra one however I will advise you to look through the script first to see what is uninstalled first just to make sure so you can make backups bc I am not sure what exactly you use

I need you help asap! I ran a script (I found one that wasn't on the link you sent me, stupid me) and now it keeps saying "IMS Service has stopped" laterally every 2 seconds. Any help please?

Did you use the S7Edge DeepDebloatV2? Or something like that?? Haha yeah don't use that uninstall ims for now or reflash with Odin

gurnsey101 said:
Did you use the S7Edge DeepDebloatV2? Or something like that?? Haha yeah don't use that uninstall ims for now or reflash with Odin
Click to expand...
Click to collapse
Ahh. Yeah I refreshed in odin. Then I did your debloat, and worked like a charm, Thanks! I forgot to sign into Snapchat before rerooting Smh, this is not my day lol. Would you happen to know any way to get on with root?

Hmmmm ic well you could try hiding the root with rootcloak in the playstore bt if I had to guess it searches for super su and the su folder soooo my guess would be to maybe go into super su and uninstall the root and super su (or reflash everything with odin to make sure all root is wiped) and then log in then root it after

Android Pay can't be used with an unlocked bootloader?

I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?

dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.

dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...

Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.

dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.

EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs

U need to flash latest magisk and pass the safetynet to make Androidpay to work.

this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?

gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...

HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!

I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated

oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...

yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.

dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.

Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.

Can I Install A Recovery Besides TWRP?

I am running the latest Android Q, which I really like. Super smooth, fast, and all that. I'd like to sit with it for a while before switching to a CustomROM, but I'd still like to root it, which is where TWRP would come in handy. However, TWRP, last I installed it, had completely encrypted my phone, even with the January patch flashed, with no actual decryption password, thus softbricking it, because I could no longer start into Android. I've restored it, and it works just as well as it used to, but I'd like to root my phone. So, here's my question: Is there any recovery, besides TWRP, that works on the Essential? I've seen Orangefox, which supports treble phones, but I can't seem to find any threads that are about the compatability on other devices. A response will be greatly appreciated. Thank you for reading.

TipTopHiatus said:
I'd like to root my phone. So, here's my question: Is there any recovery, besides TWRP, that works on the Essential?
Click to expand...
Click to collapse
Hey, you don't need a custom recovery to root your phone. I mean, people have good reasons for using it, but you can still have root without it, if that's enough for you. I never installed TWRP on my PH-1, but still have it rooted since I bought it.
Just use Magisk to patch the boot.img, and you are done. I listed all the steps responding to another thread, so you can check it here.

kt-Froggy said:
Hey, you don't need a custom recovery to root your phone. I mean, people have good reasons for using it, but you can still have root without it, if that's enough for you. I never installed TWRP on my PH-1, but still have it rooted since I bought it.
Just use Magisk to patch the boot.img, and you are done. I listed all the steps responding to another thread, so you can check it here.
Click to expand...
Click to collapse
Thanks for the help, but I'd like to flash when I'm away from my PC, so a recovery is quite important to me. Nevertheless, thank you for the help.

TipTopHiatus said:
Thanks for the help, but I'd like to flash when I'm away from my PC, so a recovery is quite important to me. Nevertheless, thank you for the help.
Click to expand...
Click to collapse
OK, fair enough. ? BTW, I just responded to you in another thread about downgrading to Jan 2020...