@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:
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.
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.
