Nexus 6P freezes up the reload during adb sideload - Nexus 6P Q&A, Help & Troubleshooting

A couple of months ago I flashed the June 4, 2019 Pixel Experience ROM using TWRP v3.2.3-1 on my Nexus 6P and worked very well using a Win10 PC and Android SDK for Windows.
When the September 6, 2019 update was available so I decided to flash it on my Nexus 6P. That's when things went wrong. Now my Nexus 6P boots back and forth between the initial bootloader and the Google logo about 2-3 times then goes into TWRP. Once in TWRP I'm able to wipe the cache and format the data. Then I try to do the adb sideload, when it reaches anywhere from 3% to 15% then my Nexus 6P freezes up for about a few seconds, then reboots eventually going back to TWRP. I have used TWRP v3.3.1-0 and v3.2.3-1 but same results. I've tried flashing the Aug 26 Pixel Exp ROM and even tried to restore the June 4 Pixel Exp ROM I had working on it, but no luck.
Update: I applied the BLOD workaround and flashed the TWRP FBE version on the my Nexus 6p. The adb sideload successfully completes now, but the Nexus 6p still boots back and forth between the initial bootloader warning screen and the white Google logo.
Update: I flashed the June 4, 2019 Pixel ROM, THEN I applied the BLOD patch and it worked! My Nexus 6P is now running great with the Pixel Experience ROM from June 2019. However I when I try to install the updates it goes into TWRP prompts me for a password. I enter the password in TWRP but it says the password is invalid. So I can't apply any updates to the Pixel ROM. I tried flashing newer versions then applying the BLOD patch but no luck. It seems like I'm stuck with the June 2019 Pixel ROM and can't upgrade beyond that version.
Has anyone ran into this issue?

Related

Help I need 6.0.1 (MMB29P nexus 6p modified boot image.

I just updated to 6.0.1 (MMB29P on my nexus 6p and tried to root. I installed twrp via fastboot adb whatever and I get dead android guy. Twrp just will not install. I need to update for cm 13 so i stop getting internal error message at boot which drives me crazy. I do not want to downgrade so i can keep the January security updates but i might have to at this point.

Device restart problem after 8.1.1 feb update

i have flashed the FireHound-v4.1.1 [Angler] rom and gapps and i was on 8.1.0 (OPM5.171019.015, Feb 2018) so i didn't flash vandor image in first time and got error in firstboot lockscreen that i have to flash the opm 3.17 . By using twrp image flash option i flash opm 3.17 vandor then again after advance wipe FireHound rom flashed. Now device not booting up after lock screen of firehound it goes back to twrp after 2 hrs of waiting to device to bootup i flash stock 8.1.0 (OPM5.171019.015, Feb 2018) again.Now my device is keep on restarting it not even going to recovery i can go to bootloader only. I have unlocked bootloader and fastboot flash method enabled. Please help me as its my beloved device. i have already made my backup of all data.
Got any solution ?? I have the same problem.
I had a similar issue but it was on nougat 7.1.2 . Anyway i flashed the factory image and the first time it bootlooped but on reflashing the same factory image around 3rd time the phone booted up. So try that and see if you can fix it.

Pixel XL March Factory Images Available

Just saw this on the developers website
https://developers.google.com/android/images
Have any Magisk users has success removing images, downloading the ota, and reflashing Magisk to the other slot before rebooting? The download always fails for me.
GroovinChip said:
Have any Magisk users has success removing images, downloading the ota, and reflashing Magisk to the other slot before rebooting? The download always fails for me.
Click to expand...
Click to collapse
Yeah - I've never been able to get that to work and seems more complicated than just flashing factory (with -w removed) or sideloading OTA and then just reinstalling MAGISK....
I was curious if the current version of MAGISK worked on top of March 2018 security updates. I haven't seen any posts saying otherwise, but would be interested to see some confirmation that some have tried it successfully (regardless of actual upgrade method)....assume we will again have to remove all password/pin prior to upgrading to get passed the TWRP decryption issues that emerged with the Feb 2018 updates. I haven't seen any new versions of TWRP released to resolve that issue yet.
sb1893 said:
Yeah - I've never been able to get that to work and seems more complicated than just flashing factory (with -w removed) or sideloading OTA and then just reinstalling MAGISK....
I was curious if the current version of MAGISK worked on top of March 2018 security updates. I haven't seen any posts saying otherwise, but would be interested to see some confirmation that some have tried it successfully (regardless of actual upgrade method)....assume we will again have to remove all password/pin prior to upgrading to get passed the TWRP decryption issues that emerged with the Feb 2018 updates. I haven't seen any new versions of TWRP released to resolve that issue yet.
Click to expand...
Click to collapse
I just flashed update and magisk and so far no problems.
Great to hear! Really appreciate you sharing your success. I'll be taking the plunge this evening or tomorrow. Will share anything relevant that comes up.
Anybody have any luck flashing the OTA in TWRP? I keep getting error 7
For anyone that has problems: follow this guide
Works on every update, also I did it yesterday.
Now running march update + magisk + custom kernel flawlessly.
sb1893 said:
Great to hear! Really appreciate you sharing your success. I'll be taking the plunge this evening or tomorrow. Will share anything relevant that comes up.
Click to expand...
Click to collapse
I just upgraded to March Security patches...and I can confirm that it went smoothly. I flashed factory (removed -w). Then fastbooted twrp (after removing security pattern). Flashed MAGISK v16. Confirmed root and MAGISK Hide working as expected. Confirmed SafetyNet passing. Re-setup security and fingerprints (probably took the largest portion of time). Up and running - all looks good. Total process probably took less than 30 minutes.
no problems for me either. i flashed the march full factory image and rooted with magisk v16. i didn't permanently install twrp. i just fastboot booted it. i did confirm that twrp wasn't able to decrypt my phone, so i set screen lock security to none and then twrp was able to boot.
TENN3R said:
For anyone that has problems: follow this guide
Works on every update, also I did it yesterday.
Now running march update + magisk + custom kernel flawlessly.
Click to expand...
Click to collapse
can i ask which kernel are you using? i am currently running stock+ magisk and was wondering if i could further extend the battery life beyond 5.5hrs sot
Android P dev preview 1 was released today.
Sent from my Pixel XL using XDA Labs
samad.ansari said:
can i ask which kernel are you using? i am currently running stock+ magisk and was wondering if i could further extend the battery life beyond 5.5hrs sot
Click to expand...
Click to collapse
I used elementalx for a very long time, awesome kernel, but recently I switched to linux stable kernel, which is pure stock but updated to latest linux stable available (more security patches at kernel level).
And since pure android phones are always the best with stock files, I'm very happy with this kernel.
TWRP was updated to 3.2.1-1 yesterday and is now able to decrypt the data partition!!
https://dl.twrp.me/marlin/
themastermonk said:
TWRP was updated to 3.2.1-1 yesterday and is now able to decrypt the data partition!!
https://dl.twrp.me/marlin/
Click to expand...
Click to collapse
Confirmed. I was able to successfully fastboot boot TWRP-3.2.1-1 on my Pixel XL running March Security update. And I used my pattern to unlock and it successfully decrypted. Good news. Removing / restoring security/fingerprints was the most time consuming part of applying updates. Great work and many thanks @Dees_Troy!!!

Problems with updating to August Update

Hi! I wanted to switch from Pixel Experience back to stock, I flashed V10.0.11.0 using the official fastboot image (I used flash_all.bat). However, when I try to install the August update using OTA, it always fails for no reason. I had TWRP and Magisk installed with Pixel Experience, but reflashing everything should have deleted those. Also, I didn't flash Magisk or TWRP. I didn't even boot temporary TWRP - everything should be completely stock, but the OTA still fails. What am I doing wrong?
Edit: Curiously, Google Play shows that my device is not certified. How the hell is my phone still not considered stock? I tried reflashing multiple times, and even locking the bootloader, but the OTA still fails, and the phone is still not certified!

Nexus 6P first brick ??? Help

Hi guys,
I have a Nexus 6P here that was working normal on Android 8.1 stock already had unlocked bootloader, stock recovery. But I tried to install Twrp but already started the problems he did not want to start after some attempts including with the Toolkit he started Android. Soon after I tried to install Pixel Experience Pie, but then I never finished the installation and then restarted or opened TWRP again. Today I managed to get him to open TWRP which was developed for those with the BLOD Problem. Does anyone have any idea how to make it work?

Categories

Resources