Database Develop

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.

Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this

Wow and so it begins, great work thanks!

Thanks
Sent from my Pixel using XDA-Developers mobile app

has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well

Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:

Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.

GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...

zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.

Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.

Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.

zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.

rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....

Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?

ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk

Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.

fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off

ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????

BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

[ROM] TMO Z2 Force 27.1.3 FlashAll (October 2018 Version)

UPDATE 11-9-18: I have updated the FlashAll with the October edition of version 27.1.3. Yes, they updated the ROM but kept the same version number lol.
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from https://mirrors.lolinet.com (thank you!), unzipped it, used root junky's script to convert it (thank you!) and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Updated October Flashall https://drive.google.com/open?id=1PczvmaVv19c91iOGhpNmhmfKyvDkz-ob (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall into a folder called "TMO Moto z2 force 27.1.3 flashall" Open a command prompt in the folder it created. Connect your phone to your computer via ADB.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit. This does not wipe user data.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above (if you use recovery).
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
Not Rooted and want to wipe everything?
Run flashall_erase.bat. It will boot into fastboot mode, update the partitions, and wipe everything.
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.

texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south.
Downloads
1. Flashall https://drive.google.com/open?id=1HK2zssCGlPTD5m2A_SAD-RjrQDfmZMTR (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance,
Click to expand...
Click to collapse
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.

kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
Sorry! It was late and I linked to the wrong thing. ? Try it now please.

texasaggie1 said:
This is a TMO Z2 Force 27.1.3 FlashAll. It does not wipe user data. I created it because the OTA update wouldn't complete, I think because I am rooted. Anyway I took the OTA from @xiyl (thank you!), unzipped it and made a batch file to flash the partitions. The flashall includes ADB and Fastboot also. The Flashall is for windows. Your bootloader needs to be unlocked. You need to be on an OREO rom already.
Disclaimer: Flash at your own risk. Not responsible for damages if this stuff goes south. If you don't know what a flashall is, or twrp, or fastboot, you may not be ready for this.
Downloads
1. Flashall https://drive.google.com/file/d/1JKu5S7xvy8xvyCodLEt7olr8czP_8FUm/view?usp=drivesdk (download to your computer)
2. TWRP Installer (if you are rooted, download this to your phone) https://dl.twrp.me/nash/
3. Magisk (if you are rooted, download this to your phone) https://forum.xda-developers.com/apps/magisk
How To:
Unzip the Flashall. It will create a folder called "NASH_TMO_27.1.3" Open a command prompt in the folder it created.
Not Rooted?
If you are NOT rooted, just run flashall.bat. It will automatically boot into fastboot mode, update the partitions, reboot, and profit.
Rooted
If you are rooted:
1) run flashall_then_recovery.bat. It will automatically boot into fastboot mode, update the partitions, then automatically reboot into a temp twrp recovery.
2) In TWRP install the twrp installer you downloaded above
3) Reboot recovery
4) Install magisk that you downloaded above.
5) Reboot
If this helps you please hit the "Thanks" button. Reply to this post if you have questions or need any assistance.
Click to expand...
Click to collapse
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .

kendallgreen said:
the "flashal link" contains only TWRP3.1.zip with boot.img and META-INF folder. it doesn't contain a flashall_then_recovery.bat nor NASH_TMO_27.1.3.
Click to expand...
Click to collapse
kendallgreen said:
I downloaded and unzipped the new NASH_TMO_27.1..3. I added the AdbWinApi.dll and AdbWinUsbApi.dll and got the flashall_then_recovery.bat to run. I didn't install the TWRP installer or Magisk but rebooted to recovery and then system. After several restarts due to unlocked bootloader warning, it came back to build number OCXS27.1.2 kernel [email protected]#1 Fri Apr 20 09:21:27 CDT 2018. Android security level May 1, 2018. Android version 8.0.0 However, all of my apps were retained except Messaging .
Click to expand...
Click to collapse
So try it again but this time just do the regular flashall.bat. it should work this time.
It sounds like you are installing this to slot a but your phone is running in slot b. If doing it this way doesn't fix it just look on here for the command to switch your phone from one slot to another.

success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.

kendallgreen said:
success. I tried the flashall.bat and got the system updated to 27.1.3. I noticed that when I fastboot --set-active=_a, I had 27.1.2 and with --set-active=_b, I had to restart the phone because it was stuck at the unlocked bootloader warning. thanks.
Click to expand...
Click to collapse
awesome! The whole a/b partition thing can be quite annoying

great job man glad someone did this i was about to try thanks

worked great but i reflashed remove encryption oreo also i didnt know if it was a necessary was being safe you made it easy no fastboot lol great work

My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.

if you need baseband its easy to fix i had the same issues i was testing kernel its eas fix if you need i can help fix ive bricked and tried everything works easy check last post put on this https://forum.xda-developers.com/z2-force/development/pantheon-kernel-alpha-t3805977

My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.

dismembered3po said:
My Tmo box is rooted, presently running the original 27.1 release.. I've been getting the OTA update notifications for 27.1.2.
Do we know if I can skip 27.1.2 and jump straight to the 27.1.3 release? I'd love to be able to do this flash-all and put the update notifications to bed for a while.
Click to expand...
Click to collapse
It should be fine to skip revisions.

StonedYoda said:
My Fellow Texan.....
THANK YOU.
My phone has been in a weird limbo for months. I was on AOSIP ROM but it wasn't rooted, I couldn't use any moto mods and I couldn't install anything because TWRP wasn't installed and it wouldn't let me install it, either. I now have TWRP, but it's showing no baseband. So I'm gonna attempt to fix that but I'm already in a better place than I was. Thanks again, brother.
Click to expand...
Click to collapse
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.

mookiexl said:
If you are on tmobile, flashing the firmware flashall from the aosip thread to get baseband back.
Click to expand...
Click to collapse
If that doesn't work let me know. It should though. You may have to re-root after his suggestion

I'd been avoiding updates because I just didn't want to deal with rooting again and restoring data, etc. This was great!

(bootloader) slot: not found this is what I get with every fastboot command.

I was having the same issue... I was on 27.1.2 and kept getting notified to update, but it kept failing. I'm rooting with Magisk (16.0 initially but then up to 17.1) and it wouldn't update. Thanks to this thread, I ran the flashall_then_recovery.bat and it worked a treat!!! Thank you TexasAggie!

TWRP Installer link is down
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.

climbhigh77 said:
The link to the TWRP installer is timing out when loading and comes up with an error message. Is it possible to install the 27.3 update using adb and then flash magisk in the temp twrp? Thanks for your work bro!
UPDATE:
I tried and now I'm stuck in bootloop. I can still get to twrp using adb and did a wipe but it's still stuck in loop land. Do I need to be rebooting in TWRP from slot A or B? This is my first phone that has dual partitions and I am a bit confused by it. Any suggestions? THANK YOU!!
UPDATE:
Tried your flashall update a second time and it worked with no bootloop issue, was able to flash magisk and obtain root again too.
Click to expand...
Click to collapse
Glad to hear that!

So has anyone figured out how to root the phone?

I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)

TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?

greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.

TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader

TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.

I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck

I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root

Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper

My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.

mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!

greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.

mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'

greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot

mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?

mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot

fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later

mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)

fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.

mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success

mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?

No touch screen after March factory image update

Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.

tatico28 said:
Anyone else having this issue after fastboot the March factory image, I was rooted with Magisk on the January firmware.
Click to expand...
Click to collapse
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?

Homeboy76 said:
Did you uninstall Magisk or disable the magisk modules before you flashed the March 2020 factory image?
Click to expand...
Click to collapse
No, I did not, is there a workaround?

tatico28 said:
No, I did not, is there a workaround?
Click to expand...
Click to collapse
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.

Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.

tatico28 said:
Thanks for your response, updating the Tools module made the difference, since I`ve tried to fastboot flash the factory image twice with the old tools version, I did not know that the March update came with this bag of treats lol.
Click to expand...
Click to collapse
Hi, what do you mean updating the tools module? tnks

davidvd102dvd said:
Hi, what do you mean updating the tools module? tnks
Click to expand...
Click to collapse
I think he's referring to SDK platform-tools.

Homeboy76 said:
I think he's referring to SDK platform-tools.
Click to expand...
Click to collapse
i though the same but tried without success

davidvd102dvd said:
i though the same but tried without success
Click to expand...
Click to collapse
Ok, then this must be what he is talking about: https://pixelrepair.withgoogle.com/carrier_selection

Yes the SDK Platform- tools, also I had to fastboot flash the boot.img to both a,b slots.

Homeboy76 said:
No it is not a workaround, strange things happen when you don't at least disable all magisk modules before you flash a Factory update. Why some modules must be updated to work with the March Factory image. Use this Guide: Do #4 'keep data' then do #9 to root.
Click to expand...
Click to collapse
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28

alwynjoshy said:
bro just disable the modules is enough or do we have to flash the stock boot too? @tatico28
Click to expand...
Click to collapse
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'

Homeboy76 said:
If you are going to do #4 and you are rooted, do this first:
- Open Magisk Manager
- Tap modules uncheck all the modules that have a checkmark (tap the ✓).
- Reboot to deactivate the modules
- Open Magisk Manager
- Tap Uninstall
- Tap Restore images (unroots your phone by restoring/flashing stock boot images).
- Do #4 'keep data'
Click to expand...
Click to collapse
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive

alwynjoshy said:
Restore images failed says no image found. So i disabled all modules and rebooted then flashed stock image booted up. The i went bootloader and flashed march OTA. Booted up But still touch is not responsive
Click to expand...
Click to collapse
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?

Badger50 said:
A factory reset may be your only option then. Have you tried switching your slots and then fastboot the factory image without the -w so as not to loose data?
Click to expand...
Click to collapse
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED

alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.

tatico28 said:
Update the SDK Platform Tools, flash March factory img. without -w if you don`t want to erase your data, extract boot.img from image.zip, fastboot flash boot.img to both slots and you should be ok.
Click to expand...
Click to collapse
I tried the way you said but same result. The only thing i didn't do is i flashed only slot A only. But my active slot is A so i think that is not the issue

alwynjoshy said:
I only use a slot only, didn't try swift slots but i try to go recovery mode to sideload the zip. A error state "NO COMMAND FOUND" AND SHOWS A DEAD ANDROID WITH STOMACH OPENED
Click to expand...
Click to collapse
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:

Badger50 said:
Thats just the stock recovery screen. Hold the power button down, and then tap the volume up button once. Then you'll be stock recovery :good:
Click to expand...
Click to collapse
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA

alwynjoshy said:
Is both sideload and run flash-all.bat give the same functionality to flash or it will be different way to flash the OTA
Click to expand...
Click to collapse
It's a matter of choice really. Many, like myself, like to fastboot the factory images every month to update. Others like the OTA. Functionality is pretty much the same as far as I've seen. However, you can't fastboot an OTA, likewise you can't side load a factory image, and of course, you have to be bootloader unlocked to fastboot the factory images, so keep that in mind as well. I also like using fastboot because you can switch slots to sometimes get rid of errors that occasionally pop up. Good luck with finding your solution whichever way you choose to go. :good:

Rooted 4a 5G still on January version, how do I update?

I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?

WhiteAsIce said:
I have a rooted 4a 5G that's still on the January 5, 2021 version. Whenever I go to the phone's settings to check for updates, it keeps saying that the device is up to date. I went to https://developers.google.com/android/images#bramble but I am unsure how to update my device. Am I supposed to use Factory Image, or Full OTA Image?
Click to expand...
Click to collapse
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh

Edit: See below.

Tulsadiver said:
I always use factory images. Just remember to remove the -w from the flash all .bat or .sh
Click to expand...
Click to collapse
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?

WhiteAsIce said:
So I removed the -w lines from the flash-all files, flashed the June OTA, then flashed the Magisk patched boot img. My phone cannot boot past the fastboot screen, meaning I don't have a phone until I fix this. Any help?
Click to expand...
Click to collapse
Did you leave any modules on your phone?

Tulsadiver said:
Did you leave any modules on your phone?
Click to expand...
Click to collapse
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.

WhiteAsIce said:
What are modules?
Anyway, it's too late, I ran the flash-all file with the -w lines to try to recover my phone, but it ended up WIPING my entire phone. Everything is gone, downloads and pictures and all.
Click to expand...
Click to collapse
You are rooted with magisk but don't know what magisk modules are?

Tulsadiver said:
You are rooted with magisk but don't know what magisk modules are?
Click to expand...
Click to collapse
The only one I had was a mod to allow safetynet to pass.

My phone is rooted with magisk, so I need to do the monthly updates manually. In order to do this, I download both the OTA and the factory image. I update the phone using the OTA. I extract the boot.img file from the factory image, put it on the pixel after updating and patch it with magisk. Then I copy it to my computer and flash it to the active boot slot as described below.
Too late to help now, but the issue was probably that the pixel has two boot slots, boot_a and boot_b, and it was booting from the wrong one. The -w you used finally is the wipe option and it's done by default unless you remove it, so that's why the phone was wiped.
In my case, I used the following commands to make sure that I flashed to the correct slot and/or booted from the correct slot that had the magisk patched kernel:
fastboot getvar current-slot
fastboot flash boot_a magisk_patched.img
If it's ever necessary, you can manually change the active boot slot: fastboot --set-active=a
If you flash the correct magisk-patched kernel to either slot and set the phone to boot from that slot, your phone will boot up. I learned about this the hard way and now, every month, I just make sure that I flash to the currently active slot and have not had a problem since. One of the nicest things about having a pixel is that they are just about impossible to brick - it's just a matter of redoing things properly.