Develop Bugs

Edit Build.Prop on Verizon Pixel without Root for wifi hotspot?

Will I be able to edit build.prop on a Verizon Pixel without root? Do I need to first flash TWRP recovery and then use adb shell to update build.prop? Afterwards, change file permission and flash the stock recovery? If this is correct, will this have any impact on safety net or future OTAs? Will my edits be overwritten by and OTAs?
Other than rooting, I'm assuming there's no (easier) way to accomplish the wifi tether check on this phone. I don't want to use the hack of using another app either (eg, flips the network then enable hotspot). I want to enjoy my pixel as stock without any further hacks. Otherwise, Verizon can keep their pixel.
Update:
Well, just remembered the Verizon Pixel boot loader is locked. I don't want to unlock it. Does this mean I can't flash recovery to accomplish the above? God, I'm so close to just saying f*ck it. I hate verizon.

My guess is once TWRP is released for pixel, you will need to flash a custom kernel to keep the build prop edit from reverting on boot. That is what I did for my N6 on 7.0. Just have to wait for TWRP to find out.

You do have to be rooted to edit your build.prop. You definitely will not receive OTAs once rooted, I believe it's been like this since Android 6.0. Even with stock recovery you can't get OTAs if you're rooted.
Edit...You still have to unlock the bootloader on a GS version in order to flash twrp.
Sent from my Pixel XL using XDA-Developers mobile app

Well, I found the Pixel XL at a local Verizon store----but, currently I have the Pixel (from Google). This hassle isn't worth it just for a bigger screen...plus, Verizon pixel only has 32 GB compared to my Google pixel with 128GB. This is the first android where I don't want to root----the phone and OS are that good now.
So, guess I'll cancel the Verizon pixel today. Was just hoping there'd be an easy way to "undo" the red devil's changes to Google's phone. Oh well.

How to root Google fi pixel 2 xl?

Is there a how to on rooting the pixel 2 xl for Google fi yet? Also a how to on enabling the built in call recording function? Thanks

This might depend on whether you bought from Google or Verizon (edit: just noticed you said Project Fi 2 XL). I've heard Verizon locks down the bootloader.
But even if your bootloader is unlockable, I think it still takes some time. The most important part is to have a recovery image that you can install on your phone to allow you to install anything from the menu. The developers of TWRP (or your preferred recovery) have to build that for the phone. I'm not sure if it's the case, but they may need access to the required open source bits to build it (like kernel source), and usually that's released shortly after the phone is.
After that, I think you can just install your SU apk of choice, unless they need to customize that on a per-phone basis as well.

I remember reading a long time ago, there is a file you change from a 0 to 1 in google that turns on the native call recording feature. I've got my phone unlocked now. I can't remember if it requires root or not to enable that simple feature. Does anyone here know? If so, where is that file and variable I have to edit? Thanks

Right now we cannot root yet, because of 2 reasons. If either of these were not the case we'd be able to root
1) Google has not released factory images for these phones yet. When they do, we will be able to root our phones without a custom recovery using the newest version of Magisk.
2) There is no custom recovery for our phones yet. When this is available, we can flash either SuperSU or Magisk in recovery to root.
Both rooting options above would require an unlocked bootloader of course.
ElementalWindX said:
I remember reading a long time ago, there is a file you change from a 0 to 1 in google that turns on the native call recording feature. I've got my phone unlocked now. I can't remember if it requires root or not to enable that simple feature. Does anyone here know? If so, where is that file and variable I have to edit? Thanks
Click to expand...
Click to collapse
Maybe a build.prop feature? If so, yes, that would require root, or custom recovery (you could technically modify this file in recovery without rooting)

BUT, since rooting requires an unlocked boot loader AND unlocking wipes your device, might as well unlock as soon as you can.

The first thing I do when I get a new phone is unlocked bootloader, then it can Rock!

I thought the newer versions of SuperSU can be applied from factory recovery.
Sent from my Pixel XL using Tapatalk

Colchiro said:
BUT, since rooting requires an unlocked boot loader AND unlocking wipes your device, might as well unlock as soon as you can.
Click to expand...
Click to collapse
Since my first Android phone (Motorola Atrix 4G) back in 2011, the first thing I do when I receive the phone is to unlock the bootloader. Then I wait for the root to arrive.

abuttino said:
I thought the newer versions of SuperSU can be applied from factory recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It can but that wasn't built for the Pixel 2 and you might brick it..

Well, that sucks. I hope that ChainFire will update SuperSU one or two more more times before he actually leaves.
I believe he's still consulting for now but, I hope he takes the ropes of the last phones of 2017.
Sent from my Pixel XL using Tapatalk

New Pixel 2 XL owner, questions concerning OTA updates, unlocked bootloader, etc.

Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
4) Any other recommendations or things I should be aware of?
Thanks guys

Only other thing I would read up on is how to work around the whole dual slots "feature" that these Pixel phones have. The last couple times I've tried to update to the latest security update, I get a "your device is corrupt and cannot be trusted" message and the phone won't boot. I end up have to scramble to flash stock boot.img to both slots A and B, flash the factory image to both slots, and hold my breath as to whether or not it's going to work. I wish there was an idiot's guide to updating firmware for this phone. Everyone that posts on this subject has a different opinion on how to do it properly. Going form any given security update rooted with Magisk, how does one update to the next month's firmware, without temporarily bricking the phone or wiping data? I've been unlocking phones and flashing custom roms since before Android was even invented. So I'm no stranger to this stuff, but it has become quite a production to keep up to date with this stuff.

Phazonclash said:
Hi guys, I finally decided to replace my good old Galaxy S7 edge and I came to the conclusion that I wanted, after using Samsung, OnePlus and Sony phones for years, the most streamlined Android experience possible without having to deal with OEM bloat, delayed updates, etc. anymore.
Result: I made the most obvious choice and I got an unlocked white 128GB Pixel 2 XL from the Google Store directly (I can't wait to receive it!).
I have a few questions though...
1) Will unlocking the bootloader alone (without actually rooting the phone) cause OTA updates to fail?
2) It's now possible to root your phone with Magisk without installing a custom Recovery (TWRP). Once installed, Magisk allows you to temporarily restore the stock, unrooted "boot.img". Is it enough for OTA updates to install properly or will they fail as soon as Magisk has been installed, even if the stock boot.img has been restored?
3) Does the Pixel 2 have an "e-fuse" that will get triggered once the bootloader is unlocked that will cause features to not work properly anymore, like on Samsung phones?
3) Any other recommendations or things I should be aware of?
Thanks guys
Click to expand...
Click to collapse
To answer your questions.....
1. No
2. Yes. But you'll have to unroot and completely uninstall magisk to take the OTA.
3. No
4. There are several guides to explain how to unlock the bootloader, install twrp, kernels, and root. Let me know if you'd like links, or you can search on your own if you'd like. Welcome to the P2XL. We hope you enjoy your stay ??

OTA updates. Question..

On my pixel, I installed forcedoze, custom navigation bar and button mapper. Now, in order for this app to work I have to run abd shell with the usb debugging enabled on the developer settings.
I'm pretty new to doing this type of things on my android phone and I'm just curious.
Is it safe to download a security update and android update without my settings being erased or my pixel 2 bricking? (My pixel 2 isn't rooted)

I'm using Custom Navigation Bar and my settings persist after an OTA automatic installation or when I manually flash an OTA update. No need to re-allow anything via ADB neither, the permissions I gave to the app so it can work properly (pm.allow blah blah blah)) survive the update, and no risk of bricking
For your 2 other apps, I'll let someone else give you a definitive answer, but I'm pretty sure the same applies.

SlySV17 said:
Is it safe to download a security update and android update without my settings being erased or my pixel 2 bricking? (My pixel 2 isn't rooted)
Click to expand...
Click to collapse
I'm not sure of the other stuff you've asked and inquired about, but if your phone isn't rooted and this app doesn't really require root to work, then it's far from likely any of what you've described would actually brick your pixel 2...
IMHO, bricking happens when flashing or changing permissions/root folders... at worst, updating would merely override what an app does versus any kind of app (without root permissions) could stop or get in the way of an OTA...

Does the latest TWRP not work with Android 10?

I've been away from the scene for about 8 months, so pardon my ignorance.
I know that both TWRP and Magisk had issues with the new Android 10 towards the end of 2019 with the Pixel 3XL.
Is this still a limitation, is twrp flashing not achievable on Pixel 3XL with Android 10 and is it the same with Magisk?
Essentially I'm looking for root on the Pixel 3XL with Android 10.
Thanks

still met the same issues as used to be, but luckily Magisk is still the only way to get Root on Android 10.

Yeah got it all sorted now, had to patch the boot.img with magisk and flash it, can't flash zip via TWRP like I used to with the Pixel 2XL.
Have AdBlocker and Gpay all setup now with root.
Happy that I have root again. Life is just not the same without it.
Shame that I can not flash LineageOS though.

No it does not work on Android 10. The developer claims that he's working on it and you can follow his project on GitHub where he posts the change logs. Apparently the TWRP thread doesn't get updated on XDA.
They released a statement last month saying that it works for any phone that does not ship with Android 10 but that is not true at all. So keep your fingers crossed and next time you buy a phone don't buy one made by Google and their dual partition crap.