Develop Bugs

How can I unroot my Pixel XL?

A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.

Open SuperSu, cgo to settings, click on Unroot, reboot. Done

Why does Snapchat not like root? Been reading it a lot on other posts but not why.

FFutstuFF said:
A summary of my situation:
- Got Pixel XL
-Downloaded snapchat
-Logged into snapchat
-Rooted phone
-Accidentally logged out of snapchat
-Snapchat checks for root before it lets you log in
-I cannot log in until I first unroot
I have tried searching the Pixel XL reddit as well as the XDA Pixel XL forums, but I could not find a guide/program for unrooting the phone. If anyone knows how I could go about this, please let me know. Thank you.
Click to expand...
Click to collapse
you cant youre stuck forever
*sarcasm*

ZeroHart said:
Open SuperSu, cgo to settings, click on Unroot, reboot. Done
Click to expand...
Click to collapse
This doesn't work. Uninstall fails.

I mean, ultimately you can choose to flash the factory image or sideload the full OTA update which will reset you back to stock. (Be careful with the flashall bat file in the factory image...edit it and remove the -w from the fastboot update command if you don't want to wipe data). That is a cannon, yes.

FFutstuFF said:
This doesn't work. Uninstall fails.
Click to expand...
Click to collapse
Just flash a kernel and you should lose root

jjayzx said:
Why does Snapchat not like root? Been reading it a lot on other posts but not why.
Click to expand...
Click to collapse
Makes it easier to get around notifications that you have watched a post or the notification that you have performed a screen shot.
Instead of going after the exploits individually they go after the "root" of the cause. Pun so intended.

cwalker0906 said:
Just flash a kernel and you should lose root
Click to expand...
Click to collapse
Oh that's right, Chainfire fixed it so it's a boot img only patch now. Yea, do this and you're good to go.

Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.

Anthony825 said:
Say I needed to remove root and relock the bootloader to return this phone in exchange for the 128gb model. Is that possible? I've read that relocking will instantly brick my phone. I'm nervous about doing anything to this phone now haha.
Click to expand...
Click to collapse
Relocking if you have modified it MAY soft brick it. If you changed anything just go ahead and restore using a stock image and then relock.

The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?

Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Any luck with un-rooting it?

Haven't attempted it yet. Going to call around at all the Verizon in my area to see if any of them have the 128gb in either size pixel on my break at work today first. If they do, then I'll attempt unroot this evening and let you guys know what happens.

Anthony825 said:
The only thing I did after unlocking it is root it. Nothing custom. I downloaded titanium backup, granted it root access and that's it....didn't do anything else with it. Theoretically I should be able to remove root and relock the bootloader correct?
Click to expand...
Click to collapse
Why not just download the factory image flash back to stock. Longer process because you have to download that file but ultimately you probably want the stock image laying around just in case anyway..
https://developers.google.com/android/images

I have it downloaded as of last night. That's what I'll end up doing if I find a store with the 128gb in stock.

Turns out there are no stores around in my whole state that have the 128gb in stock. So no point in removing root for me unless I want my bluetooth connectivity with my car back.

Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.

spaceman860 said:
Just flash the stock boot.img from the version you're currently on. Then uninstall the SU app.
Click to expand...
Click to collapse
I can confirm that this works
I downloaded the factory image: marlin-nde63v-factory-a66866ba.zip
Found boot.img inside and extracted it and then flashed by
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Snapchat now opens then i rerooted via chainfires steps here
https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F?sfc=true

I had rooted with with boot to root. I use fastboot to flash stock boot.img to boot_a and boot_b. When my phone rebooted it wiped it self. Was I supposed to get boot.img from the OTA image> Ws there something that I could have done to avoid the wipe? I'm very sad to have lost lots of data.
Thanks.
~Josh

SafetyNet FAILED after stock rom and relocked bootloader? (Cant use Google Pay)

I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?

ntelas said:
I have a LG G4 since almost the release of it. I had it rooted and with an unlocked bootloader since now. I decided to use it as my daily though to pay with it using Google Pay. So I re-flashed the stock v29a zip provided by LG and did the "fastboot oem lock" command. The bootloader locked, the rom is fully stock now without any modification. Why Google pay still says that the phone is altered and after checking Safetynet with an app on play store, fails? Also On Play Store the phone appears Uncertified... What is the problem?
Click to expand...
Click to collapse
Just an idea, take a look at your build.prop and see if anything looks off. Maybe you need to format some partitions before flashing the stock zip?
Cheers!

Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?

ntelas said:
Thanks for the reply. I think the zip is flashing all the partitions.I checked for TWRP and did a factory reset after the flash to make sure it's as stock as it can get. Now for the build.prop I also think that it needs root to check and edit it right? If not what sould I look for?
Click to expand...
Click to collapse
I think that certain partitions need to be formatted you might want to search about that. I think TWRP can access the build.prop but not sure. I suggested checking build.prop because it will show different models, builds and basically would be an easy way to see if you are truly back to stock.
Good luck!

Thanks! I would have to install TWRP again maybe ?

ntelas said:
Thanks! I would have to install TWRP again maybe
Click to expand...
Click to collapse
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.

uweork said:
Didi you Unroot before Flashing Stock?
Maybe some remants in Some Partitions are causing you trouble.
Click to expand...
Click to collapse
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive

ntelas said:
I flashed stock coming from a RR rom with Magisk. Believe me if I had locked bootloader with a rooted rom now I wouldn't have my phone alive
Click to expand...
Click to collapse
Then You didn´t read Properly.
I didn´t mean Root itself more Remnant parts of Root, that cause ur Saftynet fail.
on Samsung S2 once i thought so too, but banking app said no no no...
Only an Option

a user from this forum said that you need to take the line "ro.build.firgenprint=..." of the any MM/LP build.prop and insert it into the N build.prop (including reboot btw) and try again if google pay works for you...
I don't know if it works, I don't tried it, but you say us.

Newbie question about OTA and root

So I decided to root my Pixel 3 XL. I've read a lot of tutorial and I'll root it later today. One thing I don't like is the fact I can't update OTA. Is there a easy way to update when the December update is out without losing data? Can I use the flash-all script?

open flash-all and remove "-w" (implies wipe) and you should be ok.
make backups as necessary etc

Chippelchen said:
So I decided to root my Pixel 3 XL. I've read a lot of tutorial and I'll root it later today. One thing I don't like is the fact I can't update OTA. Is there a easy way to update when the December update is out without losing data? Can I use the flash-all script?
Click to expand...
Click to collapse
Yes, but delete the -w from the flash-all batch file (and save/close the file before running flash-all). Also, be sure you have the latest SDK Platform-Tools. Here is the link. https://developer.android.com/studio/releases/platform-tools

Note after running flash-all.bat to return to stock (with -w flag removed if you want to preserve data), you will need to reroot. And then you'll need to do this every time an update comes out (monthly).
If you don't want to root again you could lock the bootloader AFTER you run flash-all.bat to return to stock. Relocking the bootloader will restore things like Google Pay and other apps that check Safety Net.

Thanks that worked. Could you guys also provide a guide how to go to stock firmware image again? I didn't find a guide.

Chippelchen said:
Thanks that worked. Could you guys also provide a guide how to go to stock firmware image again? I didn't find a guide.
Click to expand...
Click to collapse
The flash-all.bat is the stock firmware..

fury683 said:
The flash-all.bat is the stock firmware..
Click to expand...
Click to collapse
Thanks but somehow that didn't work on macOS. Is it also okay to open the .sh file and run the commands yourself?

Chippelchen said:
Thanks but somehow that didn't work on macOS. Is it also okay to open the .sh file and run the commands yourself?
Click to expand...
Click to collapse
Yes

Is not being able to flash an OTA update a TWRP issue, or is it the device itself?
And will this always be the case?

Gordietm said:
Is not being able to flash an OTA update a TWRP issue, or is it the device itself?
And will this always be the case?
Click to expand...
Click to collapse
It's a twrp issue right now. I'd either sideload the ota in the stock recovery or edit the flash-all.bat by removing the -w in it. Make sure you save the edited version before you run it.
Sent from my [device_name] using XDA-Developers Legacy app

Does root remain after updating to PIE?

I am currently on oreo with magisk and gcam, if i update the software will anything happen? etc lost of data or loss of root? Thanks!

Heimex said:
I am currently on oreo with magisk and gcam, if i update the software will anything happen? etc lost of data or loss of root? Thanks!
Click to expand...
Click to collapse
If you have magisk and directly try to install OTA, even if you succeed you'll end up in bootloop. Be careful, you may lose all your data and read the guides in the forum carefully before doing anything.

marstonpear said:
If you have magisk and directly try to install OTA, even if you succeed you'll end up in bootloop. Be careful, you may lose all your data and read the guides in the forum carefully before doing anything.
Click to expand...
Click to collapse
Hi what are my options here?
I have done this guide https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 to enable the camera but i have not locked the bootloader. I would like to keep it root. So give my current condition, i cant update OTA beacuse it is asking me to update. Thanks!

Heimex said:
Hi what are my options here?
I have done this guide https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-enable-camera2-api-t3851414 to enable the camera but i have not locked the bootloader. I would like to keep it root. So give my current condition, i cant update OTA beacuse it is asking me to update. Thanks!
Click to expand...
Click to collapse
Since your bootloader is still unlocked you just need to remove magisk and flash the stock boot.img for your current version (flash it in both slots) and try to update, if the update fails you will need to also flash the system.img for your current version. After everything is done you will be able to easily root again by using a patched boot.img for 10.0.2.0.

Hakkinan said:
Since your bootloader is still unlocked you just need to remove magisk and flash the stock boot.img for your current version (flash it in both slots) and try to update, if the update fails you will need to also flash the system.img for your current version. After everything is done you will be able to easily root again by using a patched boot.img for 10.0.2.0.
Click to expand...
Click to collapse
alternatively, is it possible to lock my bootloader according to that guide above and uninstall magisk? and then update it OTA. Will this method work?

Heimex said:
alternatively, is it possible to lock my bootloader according to that guide above and uninstall magisk? and then update it OTA. Will this method work?
Click to expand...
Click to collapse
You can only lock your bootloader after restoring the tampered partitions (e.g. boot and system partitions), if you lock your bootloader without flashing those partitions you will get the famous "system has been destroyed" message.

Hakkinan said:
You can only lock your bootloader after restoring the tampered partitions (e.g. boot and system partitions), if you lock your bootloader without flashing those partitions you will get the famous "system has been destroyed" message.
Click to expand...
Click to collapse
oh, sorry i am very new to this. Is there a guide available for the method that you have mentioned?

You can use this guide to download, extract and flash only the exact partitions that i've said.

Hakkinan said:
You can use this guide to download, extract and flash only the exact partitions that i've said.
Click to expand...
Click to collapse
Hi, so these are from my understanding (please correct me if i m wrong)
1) V9.6.11.0.ODLMIFF OTA link: https://android.googleapis.com/packa...73ab1909e7.zip (i am going to assume this is my original boot img that i am supposed to flash in the 2 partitions)
2) Run commands via ADB shell : fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (Do i have to keep my volume button pressed down throughout till reboot?) - to prevent data loss
3) Will my data be lost if i do this?
4) and finally update to PIE as normal?

You can check what version you are running in settings, since that's the latest image for Oreo i would assume that this is the correct one for you.
Those are the right commands and you don't need to hold any key, this is only required while unlocking your bootloader.
You won't lose any data and if the update fail you will also need to run: "fastboot flash system_a system.img" and "fastboot flash system_b system.img".

Hakkinan said:
You can check what version you are running in settings, since that's the latest image for Oreo i would assume that this is the correct one for you.
Those are the right commands and you don't need to hold any key, this is only required while unlocking your bootloader.
You won't lose any data and if the update fail you will also need to run: "fastboot flash system_a system.img" and "fastboot flash system_b system.img".
Click to expand...
Click to collapse
Ok noted, i cant seem to extract the payload.bin despite following the guide. It is quite hard to understand.. escpecially with python? I have installed python and everytime i run the commands on the guide it just doesnt work..
edit 1: i am able to do it. Will try it now.

i have followed your instructions to flashing the boot img for A and B. as shown https://imgur.com/L7lw3qW
however the bootloader remains unlocked, do i still update OTA to pie?

Yes, it doesn't manter if tour bootloader is unlocked ir not, the only factor is if your partitions are tampered with or not.

Question Easiest way to go back to unrooted P6 Pro from Magisk?

Hi,
I have rooted my P6 Pro to test a few things and now want to go back to stock rom with locked bootloader from Magisk.
I have the bootloader currently unlocked and security and verity disabled.
I have looked at android flash .com as it was suggested was the easiest way but I cannot even find the roms to flash none of the build numbers match my device which is currently oriole-sd1a.210817.036-factory-297ee25a.zip
This is the rom I want to flash back and re lock everything back to stock.
Thanks in advance.

If you rooted your Pixel 6 pro using Magisk, unrooting it will be easy. There is an official Uninstall Magisk button in the app just tap on it, and select Complete to uninstall. The application will work on the uninstall process and automatically restart. Then you'll be back to normal.

randylahey786 said:
If you rooted your Pixel 6 pro using Magisk, unrooting it will be easy. There is an official Uninstall Magisk button in the app just tap on it, and select Complete to uninstall. The application will work on the uninstall process and automatically restart. Then you'll be back to normal.
Click to expand...
Click to collapse
Cheers thanks I did eventually figure out why Android flash . Com wasn't finding my particular build I had installed (November) had to type more of the filename in and it flashed it perfectly back to stock and locked the bootloader all seems good cheers.

randylahey786 said:
If you rooted your Pixel 6 pro using Magisk, unrooting it will be easy. There is an official Uninstall Magisk button in the app just tap on it, and select Complete to uninstall. The application will work on the uninstall process and automatically restart. Then you'll be back to normal.
Click to expand...
Click to collapse
presumably you then need to flash the original unpatched boot.img? then lock the bootloader?

whatsisnametake2 said:
presumably you then need to flash the original unpatched boot.img? then lock the bootloader?
Click to expand...
Click to collapse
Didn't need to re patch the boot .IMG Android flash .com must have done it automatically because everything is as was and it's now locked.

Ady1976 said:
Cheers thanks I did eventually figure out why Android flash . Com wasn't finding my particular build I had installed (November) had to type more of the filename in and it flashed it perfectly back to stock and locked the bootloader all seems good cheers.
Click to expand...
Click to collapse
Happy to help, it's a good thing to know that you found it useful bro!

randylahey786 said:
Happy to help, it's a good thing to know that you found it useful bro!
Click to expand...
Click to collapse
Certainly I never knew how easy Android flash tool is to use thanks.