Database Info

Basic Root Question

I very recently purchased (as in less than a week ago) a Google Pixel (5") from the Google Play store. I would like to root it, but have a few questions that I could only seem to find vague answers to online. Firstly, does the Google Play purchased version of this phone come automatically with an unlocked bootloader? I saw several posts online that this was the case, but the posts are all pretty old (10/2016, about 9 months ago) and nothing really since then. Is there a way to verify/check if the bootloader is unlocked?
Secondly, the phone I got has Android 7.1.2 (build NKG47L). These - posts look to be the most recent info on rooting this phone, but they mention a different build number. Does anyone know if this is still an accurate process?

Unlock bootloader in developer options by toggling, then use OEM unlock in fastboot, Install TWRP, and flash latest superSU in TWRP. Done.......
Sent from my Pixel using Tapatalk

Are you the same alienjon as on FB, with the Light Whip?
Bootloader is probably locked - it was on mine when new from Google Play - Aus and about 6 months ago, but locked bootloader is part of Google policy so it probably still is. Unlock like this:
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
be aware that unlocking the bootloader will wipe your phone (would keep your data secure it someone had stolen it and was unlocking it to hack it), so do that early.
I root as per Chainfire's instructions, there's no easy way to update and keep root at the moment (Flashfire is supposed to work but it doesns't for me) so I reroot after each update, worked for the June update.
There are a few things to be aware of; TWRP is up to 302rc2 but some people have had trouble with that, I still use twrp 302 rc1 which works reliably (just boot it, to flash SU then reboot I haven't installed it). SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
https://plus.google.com/+Chainfire
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.

@maulich That's perfect. Took me about an hour and a half to root, but most of that was reading and re-reading instructions to make sure I didn't mess anything up. I did notice that there is now some device protection feature that gets disabled when you unlock the bootloader. I checked online and it seems that this basically is a feature that factory resets the device in case someone tried to force themselves into a stolen device. I'll look around, but any suggestions for security features to implement for a rooted device?
@Clancy_s Sorry to disappoint, but no relation to an alienjon on FB. You are correct that it was locked, but I really love how easy it is to unlock. I'm used to phones purchased from Verizon that are beastly to unlock. My last phone (Galaxy S5) never got a workaround for the bootloader from what I recall (though after the Towel Root process stopped working it was almost a year and a half before a new rooting procedure was discovered - kudos to the devs that figured that problem out!)
In any event, thanks for the input on unlocking and rooting. I looked at a few different websites, but the procedure appears to be the same for unlocking that you found. This is the rooting procedure I used and worked fine, though the directions weren't as straightforward as you'd think; ie: the latest TWRP has a .zip but no .img to download on their website and I didn't trust anything else I found online that claimed to be the correct .img file. I used the next most recent version (RC1 - I saw several warnings against the alpha builds) and didn't have any problems. I also used the latest SuperSU (2.82, I believe). A few posts mentioned sticking with 2.79 because of bugs with the newer version, but those were from several months ago and elsewhere it stated that this issue was fixed. It seems to be working great for me
Clancy_s said:
SU is currently 2.82 and as of the May update Pixel needs the boot image signed, which borked SU. Chainfire released a fix, a .zip which you need to flash after the SU zip as per this thread:
https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
(apparently you can do without it for the June version of Pixel update, haven't checked that myself). Future versions of SU will include signing as part of the main install. I fine it useful to keep an eye on Chainfire's Google+ account which has links to the latest versions and any other significant changes:
Click to expand...
Click to collapse
Unfortunately I didn't see your post until after I rooted. I can verify, though, that flashing the SuperSU zip worked fine without any additional steps. (ie: boot into TWRP image, flash TWRP and SuperSU zips, which I did together).
Clancy_s said:
Finally, did you mean to post your question twice? I think you can probably delete the second instance if you want to, save having replies scattered around.
Click to expand...
Click to collapse
I did not. When I tried to submit my initial post I got a server error. It didn't look like anything had gone through so I went back and resubmitted, which worked. I later realized that the first post did, in fact, go through but I couldn't figure out how to delete it. My apologies for the dupe.

alienjon said:
I couldn't figure out how to delete it. My apologies for the dupe.
Click to expand...
Click to collapse
In a web browser either on the PC or on the phone, click the exclamation point in the triangle /!\ in the lower left corner of the post you want to report, report it to a moderator and ask them to please delete it, or move it, if you ever post something in the wrong section.

Thanks. I'll remember that in case it comes up again.

How do I remove the error on boot, and take the update my phone cannot install?

I have unlocked, rooted and installed magisk and busybox.
It has been awhile since I have done this stuff to my android devices. I seem to have done it successfully except now I just don't want to update and screw it up
I also read the "internal error" message can be made to go away.
I have a Pixel 2 and I am on 8.1.0 (OPM1.171019.011) and I think I want to be on OPM~19.013
How do I get to that version and install Magisk and/or busybox to the right location because I think that had a weird issue too where it didn't install to the right location (binx?)
Please help me figure out what I am doing. I know I should not be messing with things that might just mess up my phone for the sake of fiddling with it, but I need root for some things and I enjoy tinkering
Thank you

ImIntoStuff said:
I have unlocked, rooted and installed magisk and busybox.
It has been awhile since I have done this stuff to my android devices. I seem to have done it successfully except now I just don't want to update and screw it up
I also read the "internal error" message can be made to go away.
I have a Pixel 2 and I am on 8.1.0 (OPM1.171019.011) and I think I want to be on OPM~19.013
How do I get to that version and install Magisk and/or busybox to the right location because I think that had a weird issue too where it didn't install to the right location (binx?)
Please help me figure out what I am doing. I know I should not be messing with things that might just mess up my phone for the sake of fiddling with it, but I need root for some things and I enjoy tinkering
Thank you
Click to expand...
Click to collapse
we need some more information. Verizon or Google version? TWRP installed?
the error, to my knowledge as of now is with the dtbo file that magisk patches. it does absolutely nothing but be annoying. magisk is aware and I'm sure we'll see a fix with an update from them soon.
to update. yes. you need the Jan update which is just mainly a security update. to do this it depends on which version you have. download the factory image (not OTA), extract. and you'll have to use adb and fastboot to flash some things. there is an entire guide dedicated to this... in the guide section.... I lay out how I did it toward the end of the thread.
https://forum.xda-developers.com/showthread.php?t=3729313
after you update just flash TWRP, kernel, magisk again. then go in to magisk and download the busy box module. easiest way and it will install it to the correct place.
Sent from my Pixel 2 using Tapatalk

OTA Process Question (Android 10/Rooted/Magisk)

When I rooted on Pie, I just didn't bother with OTAs after that. Unless it's a new Android version or has new features, I don't care. Security patches are overhyped drivel. Never had an issue, never will.
When I updated to 10, I Googled like mad and followed some step by step instructions. Easy peasy. But I'd really like to just KNOW what to do and how to do it. So could someone knowledgeable on this walk me through the correct way to deal with OTAs when stock rooted with Magisk. The only root stuff I even really use is a few substratum themes here and there, which of course I know to disable/uninstall before an update.
Unless I'm mistaken (or just remembering it wrong), there's a nifty A/B method for doing OTAs and keeping Magisk/root.
Anyway, could someone just give me a play by play of what exactly I need to do and how to do it? I was hoping I could learn before the November update drops in (presumably) a few days or so. Help would be greatly appreciated.

it's pretty simple, restore images then perform OTA (don't restart) and install magisk to inactive slot.
for details check official Magisk Documentation (can't post link)

updating if rooted

My rooted moto G7 is still on stock android 9, security level 1 October 2019, build PPOS29.114-134-4. My wife has the identical Moto G7 phone, but unrooted, and I know she has received several OTA system updates since then.
My rooted phone is so far behind in updates because every non-OTA update method I've read about results in losing root. I know that regaining root is a simple thing to the experts but every time *I* attempt to root this (or any other phone) I end up getting into trouble. I don't even remember how rooting was originally done on this phone and obviously I am not doing things correctly.
Could a kind expert please give me step by step instructions suitable for a newbie on how to update the system on this rooted phone and then simply regain root?
My phone has twrp installed and I do have recent nandroid backups. If my memory is correct, I originally used twrp to root this phone but my memory may or may not be correct.
Thank you.
(To explain, the only reason I root this phone is
1) to use Titanium Backup which I've used many times to restore apps
2) for easy nandroid backups in case I mess something up
3) to hopefully install a Google free rom one day. I used lineageos on another phone but understand it still has problems on this phone)

maybeme2 said:
My rooted phone is so far behind in updates because every non-OTA update method I've read about results in losing root.
Click to expand...
Click to collapse
EVERY update of your firmware requires a new installation of Magisk.
New firmware = new boot.img => Magisk will be deinstalled

Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?

maybeme2 said:
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
Click to expand...
Click to collapse
You have to manually flash the firmware via fastboot. There're a lot of tutorials here in this forum for that.

Do It manually
https://forum.xda-developers.com/moto-g7/how-to/manually-update-g7-using-fastboot-t3917381
Just pay attention to not erase user data and it won't wipe anything

maybeme2 said:
Thank you
Actually I cannot get any updates unless I unrooted first. When I tell the phone to look for updates it does and tells me I'm up-to-date. Which I'm obviously not.
So it seems something is preventing update. I assumed it's because I'm rooted. What do I need to do to receive ota updates and after updates how do I regain root?
Click to expand...
Click to collapse
Theres a magisk module called Safety Net something-another and if you install hat module, reboot, go back to magislk-settings and towards the mid to bottom check the box that says Hide Magisk to protect from various forms of detection
Then you can reboot again or just wait awhile and you should be able to update BUT, as stated above, you'll have to reinstall magisk every update.

Thanks. It is hard to know what to believe anymore. In my searches I also read that accepting ota updates on a rooted Moto G7 will brick the phone.

maybeme2 said:
Thanks. It is hard to know what to believe anymore. In my searches I also read that accepting ota updates on a rooted Moto G7 will brick the phone.
Click to expand...
Click to collapse
Because some people also tell a lot of nonsense!
An ota.zip is a block based update process. You MUST verify the partitions before doing any changes! Otherwise it could lead to a fully damaged device.
"Hide the manager..." Thanks a lot!!
@maybeme2 flash the correct firmware to update your device.

WoKoschekk said:
Because some people also tell a lot of nonsense!
Click to expand...
Click to collapse
Very true. But .....it takes knowledge (which I am slowly acquiring) to tell the difference. And, if the person asking already had enough 'knowledge' to know it is nonsense, they would not need to search for information. A classic Catch-22 dilemma for a newbie. That's why searching for help is so dangerous.
QUOTE=WoKoschekk;82901585]An ota.zip is a block based update process. You MUST verify the partitions before doing any changes! Otherwise it could lead to a fully damaged device.[/QUOTE]
What do you mean by "a block based update process". I think I know, but it is dangerous to guess. If you have the time, could you explain?
Also, what do you mean by "verify the partitions before doing any changes!"? Verify for what? And after verifying the partitions, do what with that knowledge?
These are summary statements. Similar to "you must do the correct thing". It does not tell me what the correct thing is.
What people asking for help need is
1. Click on. ....
2. Copy. .. to. ... because. ..
etc.
3. Be sure to. ....
HTA123's answer was helpful that way.
"There are plenty of tutorials" is not helpful because some of these tutorials are incorrect and will brick your phone.
QUOTE=WoKoschekk;82901585]"Hide the manager..." Thanks a lot!!.[/QUOTE]
What do you mean by ""Hide the manager..."?

maybeme2 said:
What do you mean by "a block based update process". I think I know, but it is dangerous to guess. If you have the time, could you explain?
Also, what do you mean by "verify the partitions before doing any changes!"? Verify for what?
Click to expand...
Click to collapse
Android uses a ext4 filesystem that allocates storage space in units of "blocks". Your system partition is read only and Android will not change anything on it. So Motorola's developers know the block address of each file. Instead of replacing a updated file they replace an updated block.
But on a modified partition the block addresses may have changed for each file. While an update replaces a block with the correct address, this block could stored incorrect files/data.
block based OTA
To avoid such problems an OTA verifies your whole system. The easiest way to verify a partition is to build hashes/checksums.
Hide Magisk Manager
This option is helpful to hide root for some apps that check your device for root. But it's not for a device update/OTA.

WoKoschekk, that is very informative. Thank you so much! I've learned a lot and it explains a lot of things about ota's, and other things.
Excellent. I will copy and keep in my notes.
Thank you again.

maybeme2 said:
WoKoschekk, that is very informative. Thank you so much! I've learned a lot and it explains a lot of things about ota's, and other things.
Excellent. I will copy and keep in my notes.
Thank you again.
Click to expand...
Click to collapse
Attached you find a system log of a failed OTA update process grabbed from my Moto G6 plus. I know there are more interesting things in life than that. But it shows you what I have explained in my post before.
After trying to verify the partitions it fails due to a mismatched hash and the update process exits with a error (time: 04:34:25, somewhere in the middle of the log).

Question How to OTA update while preserving root?

Hi,
I've been a bit away from this forum since the initial rooting of the phone. I'm currently on TD1A.220804.031 and was wondering how does one OTA update this phone while preserving root?
Is it as simple as taking the OTA and then installing magisk again onto the other partition?

flash full factory image and then init_boot patched with magisk

Annie the Eagle said:
Hi,
I've been a bit away from this forum since the initial rooting of the phone. I'm currently on TD1A.220804.031 and was wondering how does one OTA update this phone while preserving root?
Is it as simple as taking the OTA and then installing magisk again onto the other partition?
Click to expand...
Click to collapse
Not possible to pass by ota to update.
You have to disable your Magisk Module, flash factory image with adb and flash your patched magisk_init_boot to keep root.

Annie the Eagle said:
Hi,
I've been a bit away from this forum since the initial rooting of the phone. I'm currently on TD1A.220804.031 and was wondering how does one OTA update this phone while preserving root?
Is it as simple as taking the OTA and then installing magisk again onto the other partition?
Click to expand...
Click to collapse
The only way to update using OTA and preserve root is the Magisk's option to "Install to inactive slot (after OTA)". But it doesn't really work for Pixel 7's... Therefore, any current method to update the Pixel 7's does not "retain" root... it'll always need to be re-rooted
I like the very informative post that Lughnasadh posted...
Lughnasadh said:
The "Install to Inactive Slot" upgrade method in Magisk is very hit or miss, mostly miss. Some have been successful, but for the most part most have been not. However, here are 2 reports of it actually being successful when updating to the December Security build on the Pixel 7 (I've seen a few successful reports in other months as well):
Still probably best to use another method to update...
Updating after root
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm...
forum.xda-developers.com
Updating after root
I have my pixel 7 rooted and I cannot get automatic updates. What would be the best way for me to get updates on my system? Going by the name I'd guess the pixelflasher is used, but I honestly just don't want to brick my Christmas gift so I'm...
forum.xda-developers.com
Click to expand...
Click to collapse

Annie the Eagle said:
Hi,
I've been a bit away from this forum since the initial rooting of the phone. I'm currently on TD1A.220804.031 and was wondering how does one OTA update this phone while preserving root?
Is it as simple as taking the OTA and then installing magisk again onto the other partition?
Click to expand...
Click to collapse
If you want to update and preserve root, the easiest way is to use Pixel Flasher, unless you want to take a chance on using the "Install to Inactive Slot" method, but as stated earlier it is really hit or miss, mostly miss. I would recommend Pixel Flasher if you would rather not re-root after updating.

Follow the steps on this video, i think is the faster and easy way to update.