Database Users

[Q] Unlocking vs rooting

Potential first time Nexus user coming over from Desire Z.
I intend to transfer my old data from my DZ to the nexus4 when I get it via Titanium Backup. My DZ is rooted with S-off, so it's all good.
I've stumbled over instructions on how to unlock the nexus4 via ABD, but if I'm not wrong, that's only to allow flashing of custom bootloaders and ROMs, right?
Which is to say, unlocking != rooting, and in order for Titanium Backup to work properly, the n4 will have to be rooted as well as SU, busybox etc installed.
Am I on the right track?
Cheers.

nexus come unlock.
unlock = to be use with any carrier
rooting = giving beyond standard permissions such as changing how android does things. EG overclocking, changing your sound "quailty" etc and you said. TB (titanium backup)

Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.

Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
Click to expand...
Click to collapse
Thanks Unlawful. Yes, I meant bootloader unlocking.
Unlawful said:
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.

endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I doubt it. Be cool if it did
Once you have it unlocked you enter the recovery mode and root it there. I'm probably guessing shortly after its release someone is going to make a program so it does it in few steps.
There won't be anything really out that really requires root, other than TB.

endlesstrail said:
Thanks Unlawful. Yes, I meant bootloader unlocking.
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
Nexus 4 does not come rooted. You have to root it.

NeverAlwaysEver said:
Nexus 4 does not come rooted. You have to root it.
Click to expand...
Click to collapse
Thanks guys. I guessed as much.
Yeah, I'll probably have to do without the backup of my apps for a few days until some kind soul manages to root it and posts instructions. Maybe it'll just be a day or a few hours even! :fingers-crossed:

You will be able to unlock the bootloader right away.
Root maybe not. In order to root it you will need either need a custom recovery for the device or a software exploit.
It won't take long but a custom recovery needs to be built and tested first.

It's easy to root a nexus
First you unlock the bootloader=fastboot oem unlock.
Then you use fastboot to flash a recovery. Once recovery is flashed you have to use adb to make it stick(delete the script that overwrite custom recovery with stock) then you flash su. Zip in recovery. Very simple to do
Sent from my SCH-I535 using xda premium

Unlawful said:
Unlock can also mean bootloader unlocking so you can flash/boot from custom recoveries, ROMs, kernels etc (the previous poster was referring to SIM unlocking).
It's just as easy to root, simply install/flash SuperSU via recovery though ChainsDD's Superuser works as well.
Click to expand...
Click to collapse
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.

USSENTERNCC1701E said:
Just want to clarify, I have not had a nexus device before, but my understanding is that, even on a Nexus, without unlocking the bootloader, one would still need to exploit and mount system as RW first to install SU.
Click to expand...
Click to collapse
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
endlesstrail said:
Do you mean to say that the nexus4 comes rooted? Because installing of any of the SU apps require the phone to already be rooted, which I assume is not the case even for Nexus devices.
Click to expand...
Click to collapse
I think Chainfire meant that in case you wanted to switch from Superuser to SuperSU or if you're just installing the APK (the application). If you do want to root, you should just flash the zip file found here in a custom recovery which does everything for you.

Unlawful said:
Without unlocking the bootloader, it's much more difficult to root and as you said, one would need to use an exploit and then do as you have said. However, Nexus devices do come with the luxury of unlockable bootloaders for a multitude of reasons .
Click to expand...
Click to collapse
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.

I just want to clear up some terminology to stop people getting confused...
Bootloader a.k.a HBoot - This is the piece of software that runs before anything else on the phone. It basically packages it all up, tells what to run in what order e.t.c Every computer device has a bootloader in some form or another, be it an Android Phone, iPhone, Windows PC, iMac e.t.c. The HBoot is accessible by switching your phone off, then holding down volume down as you turn it back on. The first line of the HBoot will tell you if you are S-OFF or S-ON.
Recovery - The recovery is the piece of software that allows us to write files to partitions while they aren't being used. It is the portal to allow us to flash custom ROM's and kernels. There are custom recoveries with more options than the stock such as ClockworkMod.
Superuser a.k.a su or Root - This is a user that is present on all linux distros that allows higher permissions than standard users have access to. Certain apps need superuser permissions to function, such as Titanium Backup.
A bootloader is traditionally locked. This means it stops you from writing to any partition on the device other than data. What is always true of Nexus devices, and now true of most consumer devices, there is an offical method for unlocking the bootloader. With HTC, you have to download some software, with Nexus devices, it is as simple as booting into fastboot mode, and typing the command "fastboot oem unlock" (assuming you have fastboot installed on your connected PC / mac).
Although this unlocks the bootloader (which by the way resets your device to factory settings), you still aren't rooted. You now have the ability to flash images to the previously locked partitions. Once you have access to write to partitions, the easiest method of rooting is installing a custom recovery (fastboot flash recovery recovery.img, and then using that to flash a superuser zip.
There are exploits for rooting, which either eman the recovery partition gets written to without the bootloader unlocking OR the su files get pushed to the system partition while the bootloader is locked. These exploits are more tricky and are getting harder to find, but allow you to gain root access without voiding your warranty.
To answer someone else's question, when you unlocked the bootloader on the Nexus One you got a watermark on the bootsplash, I don't know about any Nexus after that.
EDIT - Unlocked Phone: To throw some further clarification, when people talk about "unlocked phones" what they actually means is carrier. This term pre-dates smartphones, and a locked phone just meant that if you bought your phone through a carrier, you could only use it on their network, so no other SIM would work unless you bought a code off them to unlock it. This only applied to GSM phones (not CDMA) and s still practised today. The Nexus 4 will not be carrier locked wherever you buy it.

l0st.prophet said:
I just want to clear up some terminology to stop people getting confused...
Click to expand...
Click to collapse
Thanks for the excellent clarification. It's much clearer now.

USSENTERNCC1701E said:
Thanks. Bytheby, my only experience in the past with non-hack bootloader unlocking is with HTCunlock. Have past nexus devices had a permanent watermark even after relocking? I'm hoping that's not the case, cause extensive googling does not have anyone explicitly saying one way or the other, so maybe only HTC is that jacked.
Click to expand...
Click to collapse
Both the Galaxy Nexus and the Nexus 7 don't have anything changed when you unlock the bootloader (apart from an unlocked lock image on the boot screen beneath the Google logo and then it disappears after going to the boot animation). I would assume this was the same with the Nexus S . Also another good thing about Nexus devices is that you can relock the bootloader after unlocking it and it will be back to a stock configuration (assuming you're on the Google-built ROM).

PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
I beg to differ; DroidWall is the one utility I refuse to live without, and that requires root.
Other than that and TitaniumBackup though, you're quite right; the new stock features of JellyBean mean I likely won't even bother with any major third-party modifications. Indeed, I'm thinking this'll be the first 'phone in many a year which I won't be installing a custom ROM on for at least the first six months of use.

PlanBSTi said:
There won't be anything really out that really requires root, other than TB.
Click to expand...
Click to collapse
Lol, the irony is I really only use TB because I'm switching ROMs. I disagree though, I really like the extra customization that comes with a lot of custom ROM's. But I've run phones for a few months with OEM skins, while waiting on an exploit. I agree there won't be a pressing need for root.

I guess you guys like to actually see ads on your phones.

albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I actually don't find many apps to have very intrusive ads at all. I also feel better knowing I'm not ripping off the devs

albundy2010 said:
I guess you guys like to actually see ads on your phones.
Click to expand...
Click to collapse
I've never actually ended up with an air push app, and the rest of the ads really don't bother me, sometimes I'll go on a clicking spree to support devs. If it really bothers me I buy the full version or uninstall it.

[Q] Question about rooting

Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!

timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.

Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?

timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well

Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks

Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock

timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app

noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?

Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)

comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?

NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.

timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!

Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app

Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!

Can't take OEM updates after unlocking bootloader and installing TWRP

I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!

Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.

luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service

luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!

Huntereb said:
Dang! That's unfortunate! I might just install a custom rom for her or something, then. Thanks for the information!
Click to expand...
Click to collapse
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.

I haven't tested on modern phone but i know that if you want to install successfully an OTA update you need: 1) stock recovery (with TWRP it will fail) 2) an untouched system partition (you must install supersu in systemless mode).
Another way is via flashfire from the play store.
Hope this could help you

luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yeah, you're wrong
Enviado desde mi XT1681 mediante Tapatalk

Huntereb said:
I've unlocked the bootloader and installed TWRP on my girlfriend's Moto G5 Plus, but now whenever she tries to take OEM updates, the device reboots into the updating stage and then fails at an image of a dead Android. I'm at work currently without access to the device, but before I get home I was wondering if anyone else has had similar issues or has a resolution to this issue?
Thank you!
Click to expand...
Click to collapse
You can still take OEM updates even if you have unlocked your bootloader. Your phone needs to have stock rom and stock recovery. Since you installed TWRP, its failing to update. Flash stock recovery image and you'll be able to update just fine.

luizlee86 said:
I may be wrong.. but AFAIK custom roms don't have the one button navigation feature.
Click to expand...
Click to collapse
Yes it has but that feature no name like onekey navigation....you can set in fingerprint gesture menu whatever you want

I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?

welp11 said:
I have a general question about updates. On my G5 plus I'm still on the January 1st Android security level. I unlocked my bootloader but kept the recovery and rom stock.
Will I get OTA updates normally and just be able to install them through the OS? Or do I have to find the update online and install via fastboot?
Click to expand...
Click to collapse
You will get all updates via OTA:highfive:, the unlock of bootloader won't prevent you to get updates:laugh:
In extrema ratio flash via fastboot but you won't need that:good:

luizlee86 said:
You can't get those automatic updates if you have modified the phone system (e.g. unlock bootloader)... if this is what you mean.
I'm still not very used to moto devices but, from what I've read so far, you have to install updates via fastboot.
Click to expand...
Click to collapse
djroese33 said:
Yes, that's true stuff! Also, you'll keep getting the update notifications. To end that nightmare, you need to purchase the paid version of Titanium Backup and 'freeze' the Motorola Update Service
Click to expand...
Click to collapse
Wait, so if an ota rolls out, it'll fail. But you can manually flash with fastboot. But even after fastboot flashing, it'll still notify you that an update is waiting?? Even if you manually applied that update?
I'd rather not freeze the service as I do want to know when the next ota comes along that I'll want to flash.

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.

What to do about OTA update on rooted phone?

My phone keeps bugging me to install OTA update for krack vulnerability. I tried and it sent my phone to boot loop and now I have it restored. My phone has xposed installed. What is the best course of action? I would like to update but if that's not possible can I at least stop having the message show up each time I unlock my phone?

You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.

thorin0815 said:
You could try to disable/freeze the Motorola-Updateservices (/system/priv-app/3c_ota/3c_ota.apk) or flash a new full (not OTA) firmware for your device without boot.img, recovery.img and without wiping data.
Beware: After flashing a full firmware, all modifications to the system partition are lost and have to be redone.
I always disable all 3c moto services and never faced problems because of it.
Click to expand...
Click to collapse
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.

twoplustwo said:
Is that even safe not to apply the patch? I find it hard to believe just because you root your device you can't update it.
Click to expand...
Click to collapse
Is it a good idea to avoid security updates? No, it isn't. Is it clever to avoid updated drivers? No, it isn't (at least in most cases).
You should have informed yourself about the backdraws of rooting your phone before you did it. You need to be completely on stock firmware without any changes
to the system files to be able to use an OTA for updating your phone. This is needed to be safe the OTA update works the way it should.
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.

thorin0815 said:
The best way for updating a rooted phone is to install the full updated rom, which is easy to get for our device.
Click to expand...
Click to collapse
How can this be done? I don't know what to search for in these threads?

twoplustwo said:
How can this be done? I don't know what to search for in these threads?
Click to expand...
Click to collapse
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

thorin0815 said:
Check this for example: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.

twoplustwo said:
Some of my apps (like TI backup) need root. Is there a root for this version yet? I've tried searching but I find these forums very difficult to navigate.
Click to expand...
Click to collapse
Same procedure as on other stock rom versions): you need ElementalX kernel to be flashed and afterwards your desired root method(magisk is recommended).
Guides like this are valid https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918