Develop Bugs

Root + twrp + bootloader unlock + twrp flashable stock rom - marhsmallow

If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.

Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?

Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.

Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.

I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!

slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....

Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.

I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?

Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's

Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?

famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's

Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.

famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.

Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?

famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.

Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".

famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )

Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.

Pixel 2 Bricked??! (Solved!)

I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
---Solution---
Chilipepprflea said:
I know this is probably too late for you guys, but maybe it will help someone else. Fastboot commands would result in "waiting on any device" and my Pixel 2 wouldn't boot out of the bootloader. I thought it was done for good based on this thread and others I've read...until I came across this Reddit https://www.reddit.com/r/GooglePixel/comments/b25nso/error_slot_unbootable_load_error/
I did what this guy did and held the power button (ended up being for a couple minutes in my case) and it vibrated and all is good again! adb recognized my phone and I was able to flash again.
Click to expand...
Click to collapse

You'll have to go back into bootloader and do a stock flash follow the steps on googles site. go back to 8.0 or whatever you were on before, make sure that boots up fine. You must not have had updated your sdk before trying to update to 9.0

I was going to just reflash everything but when I do fastboot devices its just blank as if the phone does not exist. Also the computer doesnt do its chime when I plug the USB in while its in bootloader. When the phone is off and I plug it in it shows the charging icon for a split second then boots into bootloader saying ERROR: Slot Unbootable: Load Error. If I try to do any commands in fastboot it just says "waiting for any device"

I was already on 9.0 and was just pushing the January security patch when it stopped near the end of the update. Now I can not get fastboot to even see the device.

Try removing all drivers and fastboot files on your pc. Sounds like you just flashed the wrong file. Were you rooted with magisk? or just on a stock rom. re download the full image and try and re flash. https://developers.google.com/android/images
Because of the slots (a and b) alot of people seem to have trouble flashing things. I have even messed things up as well. On the Pixel devices I havent been able to not go back into stock setups. Even if it took removing all files and starting over.
---------- Post added at 04:19 AM ---------- Previous post was at 04:18 AM ----------
I will keep checking back over here to see if you have any issues.

So I just tried what you had said. Deleted all the SDK files and uninstalled the drivers, rebooted computer and phone redownloaded everything and still can not find the phone via fastboot... magisk was installed but I was doing the full image install without the -w so it would not wipe. it was almost done with it and never actually booted into android it just stayed on the bootloader which I found strange. That is when I noticed that the phone could no longer be found via fastboot devices. I have tried different cords different ports and even a different computer and still have the same result. It did update the bootloader and radio portions of the update. I feel like if I can get fastboot to start working I can save this thing.

I got caught up with friends that came over. You have tried everything I would have tried. Which is good cause you seem to know what you are doing, but not good that it hasnt been resolved. Have you looked at this guide? https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Coolpente said:
I started updating the phone to the Jan 2019 update from the Dec 2018 update (I just like having the latest updates) It rebooted into bootloader via ADB just fine. I then ran the flash all.bat without the -w so it wouldnt wipe the phone out completely. It started updating and rebooting just like normal after the bootloader and radio parts. It made it close to the end of the system update and did not reboot the phone. It went back to the bootloader which I thought was odd. Fastboot can no longer see the phone in Fastboot devices. When starting the phone it reboots back into bootloader saying load failed. It also will not boot into recovery (which I expected from the update and not getting to flash twrp back in yet) I have rebooted the phone and my computer as well. I tried my other phone to check the cable and it found it in ADB and Fastboot just fine. I do have the latest SDK installed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Are you *sure* it will not boot to recovery? If you're not used to the stock recovery it can fool you. Many ppl see the dead android and stop there. If you can get into the stock recovery you can try sideloading an OTA via adb (which only works in recovery). I would also be trying different computers and cables. If you cannot use fastboot -and- you have no working recovery you might be dead in the water.

OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])! And those who have seen me around this forum the last year know that I am very knowledgeable and don't make the simple and "noob" mistakes! I've literally have helped and recovered people in this/our position -- so it is doubtful there was a amateur or novice mistake made in the updating process or "stone un-turned" in the recovery process!
So here is what happened to me, particularly, and my observations on it...
- When "crap hit the fan", it was very peculiar that fastboot would identify the phone's serial number as "??????????" (when running the command "fastboot devices"). Only after rebooting and disconnecting/reconnecting the usb cable did it (fastboot) simply just stop detecting. To make sure that my computer, usb port, cable, and fastboot is working correctly and able to process properly, I would make sure the fastboot process/server was not running, then I would actually run the command "fastboot getvar all", and as it would "would for device", I would plug in the phone, nothing would happen, then plug in my phone [taimen] (not my gf's walleye), and it would detect it and display all the pertinent information and device details, I would then unplug it from my phone, run the same getvar command, and lastly replug it into the phone (broken gf's walleye) with no detection or success.
- What's also interesting and of note is that when loading straight into the bootloader (via button combination), it displays no error in the list of device details. But when booting into the recovery (note: I, like the OP, had the TWRP custom recovery already flashed and installed) and also the system and/or from a power-off state, it states in red colored font and yellow background, "ERROR: Slot Unbootable: Load Error". Even more than that is when attempting to boot into Download mode, it states a different error (but in the same font style), "ERROR: Operation Denied"!
- I also attempted to manually change the slot in attempts to address the "slot unbootable..." "...load[ing] error", but -- due to either fastboot not detecting or the device not connecting properly I imagine -- without fastboot properly detecting, the commands wouldn't work and execute properly anyway. I've even taken steps further and attempted to format and custom "re-size" partitions. But, for the aforementioned reasons (presumably), it and attempts at commands like it wouldn't likely work and execute, again as previously reasoned. Also, in attempt to tackle the "slot" aspect of the issue, I tried Deuce's script; but as Deuce's script is, simply put, based off of the flash-all.bat that ends up being an advanced batch (pun intended) of commands that manually and individually flashes the stock images/partitions to the partitions of the device -- so, in essence, uses fastboot and since fastboot can't work.... I even found and attempted to use the (hardly heard of; at least to me) tool Skipsoft Android Toolkit (which looks genuinely super dooper awesome btw...)... all for naught :crying: ...
You know, after a year with the Pixel 2 (XL), and after coming back from messing my phone up (15+ times), and actually purely bricking it once (had to get it replaced), I always thought that, as long as one could access the device via the bootloader, one would always have hope (at least in the Pixel's case). So, it's curious but agonizingly ironic being able to access the bootloader (which was not the case in my one and only instance of bricking my device and having a completely "lost cause") just for me not to be able to do anything about it and/or fastboot to not be able to properly connect and send commands to it...
But to me and Coolpente (and anyone else who this may have happened to) I ultimately can't think of anything else that can be done at this point. To re-iterate, I/we had the most up-to-date platform-tools (r28.0.1), it has been proven that the usb cord, port, computer, and drivers are all working as I was able to get the "getvar all" command to work on another pixel mere seconds before attempting the same on this (broken) device, and even attempted all tools available...
Unfortunately, @Coolpente, it does look as if our phones are irrevocably "bricked" and it's all rather doomed and attempting to get it repaired/replaced by the manufacturer ("The Big G") is the only recourse we may have :crying::crying::crying:
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...

simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
-- SNIP---
I wrote this (very long) post in hopes of giving as much information and details as possible in the desperate hopes that any other solutions might be brought up...
Click to expand...
Click to collapse
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.

Coolpente said:
I am so glad I am not the only one that his has happened to! I have rooted several phones as well as almost bricking the one that ultimately bricked... (not up to date sdk tools) You have word for word the exact same thing that is happening to me. no recovery no booting and no download mode just the bootloader which is not found by fastboot. I thought at first it may have been the usb port in the phone disconnecting somehow but when plugging it in from a completely off state it does show the charging battery screen for a split second then boots into bootloader saying it can not load that slot. I am not very fluent in the disassembly of phones like this or I would check to see if the data parts of the USB port are not connected to the board.. It kills me that the phone is not even a year old and something like this would happen.. I have since gotten a replacement phone but I am very interested in seeing if there is a way to fix it in the near future outside of sending it in.
Click to expand...
Click to collapse
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....

simplepinoi177 said:
OMG @Coolpente!!!! THIS....HAPPENED...TO....ME!!!!
Holy crap! I can't believe this happened to someone else! I thought it was just me and my bad luck!
I literally was doing the same thing (only difference was on my gf's pixel 2 [walleye])!
Click to expand...
Click to collapse
Find a new girlfriend, your problem will be easily solved.

simplepinoi177 said:
I know it is highly unlikely, but I'm hanging in there hoping for the same thing as well...
Yeah, it's troubling that this is can be happening coming from very "seasoned" users!
I was considering the same that it feels more like a hardware issue since everything seems to work on the computer end as well as everything working on another pixel device, BUT I can't see how a failed "fastboot" command and process can effect any kind of hardware or physical connections ("data parts")?!
If anything, I believe it has to do with the sequence of events of how things crapped out... I believe that, in some random manner, the bootloader -- which gets flashed and updated first; referencing the script in the flash-all.bat -- gets replaced, but isn't installed/initialized/"placed" properly -- but curiously enough, is installed "properly" enough that it can be re-entered after turning the device off -- that most everything works BUT the all important fastboot connection/interface/detection! That's why I attempted to manually flash the bootloader image ("fastboot flash bootloader bootloader.img"), but, "head-bangingly" poetic in its irony of course, fastboot is required to accomplish this ("this" being fixing freaking "fastboot"! :crying: )
I'm terrified to update my own Pixel at this point.
Unfortunately, this seems to have only been documented in our two cases (so far)...I wonder if it's even worth creating a Google support ticket in attempts to bring it up to them in hopes that they fix whatever might be causing this -- hopefully assisting and saving others from this disaster -- and/or even pull the update until it is stable (although, like I stated, it seems not a prevalent enough issue that many either have successfully updated via this image and process or most haven't brought it up anywhere) and/or keep it from happening in the next update.
In any case, here's hoping ("pray for the best, expect the worst" kind of scenario is most likely appropriate) any kind of solution materializes, or, at the very least, can be shown as a "word of warning" and caution about the (this, specifically) update....
Click to expand...
Click to collapse
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...

Coolpente said:
I have considered going to a custom rom and avoiding the stock rom completely... Which would avoid ever needing to use fastboot to update in the future.. but its to late for one phone but not to late for the other. I havent even looked into roms since CM broke down...
Click to expand...
Click to collapse
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**

simplepinoi177 said:
Yeah....but, if you think of it, I've been updating by way of Full Factory images via fastboot for over a year (14 months to be exact), so the last 13 times and 13 out of 14 times it worked perfectly....so, pure statistics, I wonder if swearing off fastboot forever is truly pertinent just yet...
Well, at least the pixel 2's been out for....14 months, apparently...so there seems to be a lot of good, stable custom ROMs that have been long in development to choose from, if anything... **~shrugs~**
Click to expand...
Click to collapse
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.

Coolpente said:
As far as statistics are concerned yea I have been updating 2 pixels by full factory images for the last year and one has survived all 12 months while the other made it through 11 of 12. but in fear of bricking another pixel device knowing this could potentially happen again... it feels as if going to custom roms would for sure be the safest method and still keep root. Of course losing root and going pure stock would be 100% the best... I love having root and dont want to lose it.
Click to expand...
Click to collapse
Yeah, I see what you're saying and in the exact same boat (2 pixels, gf's is a walleye, mine's a taimen, both have been updated monthly with no issues or def bricking issues, so 14 of 14 and 13 of 14...)...
But I guess that's definitely one of the "safest" methods, just that support for ROMs come and go (hell, even one of the original custom kernels [Flash] is EOL)...but Pixel 2 is only a year "in" and Google will continue to support it for the foreseeable future so it may look like regular support for walleye/taimen-related mods will continue to get regular updates and support as well...
But still, as I enjoy our conversations, it also serves to "bump" this thread as well...
Anyone have any idea on how to reinstall bootloaders, switch slots, enter custom recovery, flash anything all without -- and this is key -- fastboot (because fastboot will not detect and connect with the device)?!?!

I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?

James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.

simplepinoi177 said:
Awww crap! Super sorry to hear that! As you can see, not a lot of ideas or thoughts were submitted, and haven't been in a long while, so there doesn't seem to be much/anything that can be done it seems...
If you truly have the exact same thing, then that means that the USB connection is not working, so, you're not able to get into the recovery nor able to run any commands, so the only recourse it seems me and @Coolpente is to contact Google and attempt at a RMA...
But, as this is a third instance -- there may be more; I'm convinced there are, they just have not spoken up here specifically -- I wonder if this is something to be brought up to Google Support (https://productforums.google.com/forum/#!forum/phone-by-google) and their support forums? I mean, although this might not be a widespread widely known issue, this issue does make the device completely unusable and able to be rescued! For me, that's a serious matter -- as most other issues you can learn to live with it (while still being able to use the device for the most part) and/or it's something that can be worked on, repaired, debugged, etc. -- that needs to be attended to, dealt with, or at the very least brought to their attention.
Click to expand...
Click to collapse
I just contacted Google for an RMA. Hope it doesn't occur on the phone that will be shipped to me. Now I am without a phone for a couple weeks...

James1258 said:
I just tried to update to Feb from Jan and this happened to me....
Anything I can do about it?
Click to expand...
Click to collapse
Did you also ran the flash all without - w?
Sent from my Pixel 2 XL using Tapatalk

Corrupted Deviced, Unlocked Bootloader Vendor Parsing Failed, can get in TWRP.

Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!

You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.

hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.

If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL

I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.

Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?

Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools

Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.

Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.

Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.

It's because you were using r28.0.1 before, download r28.0.2

Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/

Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.

At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!

Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.

XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?

XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!

hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?

Cannot flash factory firmware after a failed root attempt

Thanks in advance if anyone can help me with this.
I tried to root my phone via Magisk using a tutorial on YouTube. I noticed after Magisk had patched the boot.img it reduced in size from around 65MB to 30MB, which seemed odd. Flashed it, and phone became stuck in a boot loop. I tried to use fastboot to put the original boot.img back, and ended up being told the system was corrupted.
Thought I would just flash the factory firmware back on to the phone - however, that is failing partway through, when it tries to flash vendor.img, with an error "write to device failed in SendBuffer()"
I've tried multiple different versions of ADB and Fastboot, from HighOnAndroid and Google, tried flashing from a different laptop, but it fails at the same point regardless. The only thing I haven't been able to try is a different cable, but it would seem odd if that was the cause?
My device was originally on Bonito 10.0.0 (QQ1A.191205.011, Dec 2019) - I've tried to flash that back, and also tried 10.0.0 (QQ1A.200105.002, Jan 2020), neither of them working.
I'm using ADB and Fastboot from the Platform Tools at https://developer.android.com/studio/releases/platform-tools - a lot of posts I've read talk about "installing ADB and Fastboot", but they're just executables that run fine without any installation, unless I'm missing something.
Does anyone have any ideas of what I could try please?

Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.

smimon said:
Same old story - different cable, different port, worked.
I also suspect that the platform tools were not compatible with QQ1A.200105.002, Jan 2020, since the one I successfully managed to flash in the end was the December version.
Since I changed both cable and version at the same time, I can't say which one it was.
Hope this helps someone else.
Click to expand...
Click to collapse
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.

clayndwoods said:
I wonder if this is why Magisk Installer doesn't like my boot image, consequently failing to patch it.
Click to expand...
Click to collapse
Known issue with Cannery Channel. Try latest Stable. Also checkout Magisk thread.

Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
I don't want to hose this phone, has I just got it as a replacement from Google. I tried sideloading the Android 10 update using TWRP (my original phone had TWRP and Magisk installed) and bricked the phone. Well, not exactly bricked. It was stuck in recovery, the only thing that would work was the bar code display.
You never know what you like so much about the pixel until you have to use a Samsung while waiting for your replacement Pixel to arrive. I can't survive without call screening LOL!

clayndwoods said:
Android
I figured it out. I was trying to patch the wrong file, apparently.
I'm a bit concerned, though, as the patched file is 29.6Mb and the orignal boot.img is around 60Mb.
Click to expand...
Click to collapse
The patched file is normally smaller than the stock boot.img. That's OK and expected.

Question Android 13 bootloop

Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?

Delete the cache in recovery if all else fails it should fix whatever the conflict is

Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13

Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.

Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?

Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.

Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?

Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.

Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.

Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.

Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...

I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.

fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes

Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot

fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times

Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android

fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware

I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update

apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.