Google's Factory Image Flash Instructions Inadequate?

hawkswind1

Senior Member
Jun 11, 2012
474
210
73
I bought a Nexus 6p when it first came out and finally upgraded to the 2xl. What a difference. I didn't realize how far behind the times the 801 chip is.
Anyways, everything was working fine. Then......I installed twrp and magisk and some modules. A few days later installed flash kernel. Somewhere along the way my touch screen got wacky especially near the edges and scrolling got weird, and when I tried playing audio with the oem adapter and several headphones, audio would continue to play from speakers and a notification said a charging device is connected. I flashed the latest factory image using flash-all per instructions to see if it was a software issue but the problems persisted. I contacted Google that sent me a new usb adapter but it didn't fix the audio problem.

I did one more search before requesting a replacement device and came across Deuce's script that flashes the factory image to both slots and some other stuff. Somehow it fixed my touch screen issues and the audio adapter problem.
On the 6p if I used flash-all.bat and an issue wasn't fixed I could be sure it was a hardware problem. Doesn't seem so on the 2 xl unless I am missing something. Seems Google should be using Deuce's flash-all script in place of their own.

https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761