Database Info

Help. Stuck on Bootloop on Pixel

I'm stuck in a bootloop on Pixel (sailfish). I've rooted with SuperSU and installed TWRP previously. I've never had an issue applying the new updates until today.
Here's the steps I followed:
I downloaded the 7.1.2 (N2G47O, May 2017) update from the google site and verified the SHA 256 hash
I removed the -w from the "fastboot -w update" in flash-all. Then ran flash-all.bat. It completed successfully. The phone rebooted.
Next I powered down the phone and booted to fastboot.
I then tried to install TWRP by running "fastboot boot twrp-3.0.2-RC1-fastboot.sailfish.img"
It installed fine and booted to TWRP.
I opened TWRP and tried to install TWRP. It ran fine. Rebooted and here's where I went into the problem
The phone boots up and gives me the message about "Your Device software can't be checked for corruption. Please lock the bootloader". I've seen this before, so no issues.
Then the Google screen shows up with a black line through it.
Then it comes back to the previous message about the unlocked boot loader.
If I tried to hold POWER down, I get a message "[RAMDUMP] Writing to EXt 4 file" and back to the message about the unlocked boot loader.
How do I fix this ?
UPDATE: After much trying, i finally caught it when it was powered off and managed to get to boot to fastboot where I reflashed the most recent update. But.. is this still the best way to install TWRP ? Or should I do something else?

The problem is the bootloader in the N2G47O. A temporary fix is to download the N2G47E image and extract the `bootloader-sailfish-8996-012001-1702151126.img` file and then boot your phone into fastboot and run `fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126.img`. Then you can boot into TWRP and install whatever you need

Abolfazl said:
The problem is the bootloader in the N2G47O.
Click to expand...
Click to collapse
Thank you very much! I've followed the temp fix and now have both TWRP and SuperSU installed.
I appreciate the quick response and help

Wow this just happened to me too. Thanks for the fish. I guess a better upgrade path is to not skip the April update ( I was coming from March to May)
Also follow the hardware process of booting to fastboot if this is happening, no need to wait for an oppurtunity. Just press Power + Vol - + etc and release to boot to fastboot.
.

THANK YOU!
Abolfazl said:
The problem is the bootloader in the N2G47O. A temporary fix is to download the N2G47E image and extract the `bootloader-sailfish-8996-012001-1702151126.img` file and then boot your phone into fastboot and run `fastboot flash bootloader bootloader-sailfish-8996-012001-1702151126.img`. Then you can boot into TWRP and install whatever you need
Click to expand...
Click to collapse
Saved my life here! I thought I was going to have to deal with Ads until the next time they updated TWRP! This worked beautifully!

Flashing new TWRP 3.1.1 lead me to no recovery

Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.

My firmware is latest Nougat (BLN-L21C432B360).
I tried to flash TRWP 3.1.1. Before this try, I had version 3.0.2-1 as written above. I flashed twrp when I still had Android 6 with EMUI 4.
Regarding the way to enter TWRP, yes, I know the method and I do it.
The problem is my phone don't enter twrp but remain stuck at logo.
It seems that the recovery is not present or has problems.
I've tried even to reflash the old recovery, just in case. Nothing.

Try this-
flash stock recovery for your model.
boot normally.
flash TWRP latest.

Now I try and post later.
What a mess. I should leave the old 3.0.2 which was working good...

I was already on nougat and the 3.0.2 was still working perfectly. I had flashed that twrp when I was still on 6.0 and after the update with firmware finder it was still working.
Moreover I used the official TWRP app to update and it failed miserably even if it said flash successful at the end of operation....

Then I used the classic way with ADB and still nothing.
I can see on the Windows shell "failed: command not allowed"

Rommco05 said:
Frp in fastboot is unlocked?
Click to expand...
Click to collapse
AFAIK, Factory Reset Protection is linked to account protection in case someone steals the phone. In this way it should be more difficult to wipe completely the phone and use it.
Anyway, just checked in fastboot and no, FRP is locked. I just had a look in developer options and I noticed that "Enable OEM unlocked" is greyed out. But it should not have nothing to do with flashing the recovery.
Or not?

Let's see

Diamantes said:
Hi guys.
My issue: I had TWRP 3.0.2.1 on my honor and decided to update to latest version. Big error.
I have the TWRP app installed and I followed the procedure to flash recovery with that app. It seemed everything was fine, because it said ""recovery flashed".
Now when I try to enter recovery, my phone gets stuck at logo "your device is booting now".
I have to reboot in EMUI recovery to go out from that stuck page and to load normally the phone.
So I decided to flash recovery in the old ADB fashioned way: now when I get to "fastboot flash recovery twrp.img", the phone tells me "FAILED (remote: Command not allowed)"
Practically now I have no TWRP and I do not know how to proceed.
Some good Samaritan out there?
Thanks.
Click to expand...
Click to collapse
Unlock your boot loader

Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see

Diamantes said:
Bootloader is unlocked.
For some reason, my "OEM unlocked" option turned greyed out, and FRP is locked again.
I will try this eve to lock bootloader again and restart the unlocking operation from scratch.
Will see
Click to expand...
Click to collapse
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x

you mean that even if I can't access TWRP, this should be still there and I cannot lock bootloader?
And you advice to do a factory reset first.
If this doesn't work? Then?

shashank1320 said:
In emui 5 OEM unlock option is not there and can only be found in MM or Emui 4.x
Click to expand...
Click to collapse
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out

Diamantes said:
You mean that I couldn't even see the option?
I have nougat and emui 5, the option is present but greyed out
Click to expand...
Click to collapse
Yeah exactly. See SS
This was there till emui 4

So how can I solve the problem?
Someone told me the only way is to lock bootloader in order to have again this option available to be turned on... And so start the process again.
At the moment I cannot access TWRP nor flash it through ADB. Practically even if bootloader is unlocked, I have a rooted phone with no possibility to do anything else... Regarding flashing of course.

Thank you for your replies.
Anyway I really know now that I cannot buy honor for flashing.
I just tried a factory reset from advanced options.
After all the pin request etc, the phone rebooted and get stuck on the initial window (your phone has been unlocked and cannot be trusted-your phone is booting now...).
So I had to press usual buttons to enter in emui recovery, the only way I can get the rebooting option from this state.
Of course the phone is not reset.
I give up. This crappy phone is taking too much time of my life.
I will keep it like this. And I'm not sure at all I will get future OTA update.
I never EVER had these issues with Samsung phones or HTC, and believe me that I was flashaholic... I flashed tens and tens of ROMs, I rooted and unlocked all my previous phones with no glitches or whatever..,
This time I tried honor for the price.
Never again for flashing or playing around.
Just for normal, classic phone use, hoping it will last some other month before I purchase another brand.
Thank you all.

Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment

Diamantes said:
Of course my thoughts about this ****ty phone were all right.
I received the ota update for version b365, downloaded and OF COURSE STUCK at boot logo after automatic restart...
I will never be able to install anything else because the recovery is corrupted.
I am condemned to stay with b360 until this cursed phone will die for natural causes...
No comment
Click to expand...
Click to collapse
But recovery can be changed mate. Try twrp with new thread in my signature and follow steps, it won't be a trouble. Try once in free time as i know you already are frustrated with trying all ways.

The TWRP on official TWRP site sadly won't work for our berlin devices, i neither know why it is still there sincerely. Personally i can't recommend the usage of TWRP official app for our phone as it downloads a wrong version... you have to get the OpenKirin edition from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash that via adb fastboot. Be sure to have "USB debug" on by developer options menu, and to have installed HiSuite (just to have all the functional drivers)

I thank you all for your patience and replies.
But as Shashank said, I'm really frustrated because I tried everything in the past.
Now I'm rooted (luckily) but with FRP locked. It seems the reason why I cannot flash nothing.
In any case I will try again the suggestion of redskull. The last hope!
Thanks.

[Help] Bootloop after re-locking Bootloader!

After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?

Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here https://developers.google.com/android/ota and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.

Arju said:
Man, when you lock the bootloader you need to make sure you're 100% back on stock without any modifications flashed. Seems to me you tried locking while having magisk flashed.
Try to see if you're able to get into recovery. Get into bootloader menu by pressing power button+volume down and the press volume upp until you get to recovery and then press power button. If you're able to get into recovery then download the full ota image for Google pixel sailfish from here removed-link and then while you're in there should be an option to update using adb. You need to adb sideload the update from your computer to your phone. I know this should work on a non Verizon phone but I hope and assume that is what's needed this time. If you're not able to get into recovery and your bootloader is still locked then you pretty much have a bricked device.
Click to expand...
Click to collapse
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?

have you tried fastboot boot twrp.img? does it bootloop aswell? if so, you might have hard bricked your pixel... last solution is to try flash stock image and then try again with stock recovery / twrp img.

Mr Ian said:
At the minute I've taken it to a Phone shop hoping they will be able to figure a way to get to the recovery menu - baring in mind I had TWRP flashed.
Yeah, It will go to the Bootloader menu but when trying to go into recovery it will just repeat the same process as before where by it will flash the Google splash-screen then restart. Any notes on how to go about hard flashing the image?
Click to expand...
Click to collapse
If you can't access stock recovery and your bootloader is locked then your device is pretty much hard bricked unfortunately. Don't think the phone shop would figure it out, they might change the motherboard as a solution if they don't have the right tools to reflash on a deeper level. Hope they figure it out. Please let us know if they managed to fix it. If not then someone else might have some suggestions. I'll try to think of something else.
Try either of these commands to see if you can unlock the bootloader again:
fastboot oem unlock
or
Code:
fastboot flashing unlock
And then try what the post above me suggests.

Hey, did you ever figure out a solution to this? I did the same thing to myself today...

any solution??
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Mr Ian said:
After reading the news that a new method had been found for Verizon/EE-UK Google Pixel (Sailfish) Phones to unlock the Bootloader - I decided to do so and then proceed to flash Magisk for root and other benefits however as there was recently a new update which was showing as 'Failed to Install'.
Of cause I wanted to update the device so I attempted to re-lock the Bootloader using 'fastboot flashing lock' and proceeding to select Yes from the prompt. Which seemed to be acceptable and worked to lock the Bootloader.
Now my phone is stuck in a crazy boot-loop where by the phone will turn on - flash the Google logo on the white background for a split second then shut itself down and repeat.
Does anybody have any tips for me to recover the phone from this awful state?
Click to expand...
Click to collapse
Did you managed to unlock it???

You can unlock the bootloader with htc-fastboot if you have a bricked android 7-8.
They patched it on Android 9.
On android 9 your only chance is to reflash it in edl mode. Anyone here who can help me to enter edl mode with my pixel?

Question Booting fine but showing "Your Device Is Corrupt" screen if bootloader is unlocked

I got a 6a today, with the intent of learning about rooting. I've never rooted before, but was pretty involved with iOS jailbreaking so kinda a similar vein.
I wanted to get to Android 13 to get a fresh start (as opposed to rooting on A12 and upgrading), so i downloaded the factory image. I used the flash-all.sh script, but it got stuck on "Rebooting into fastboot." It then booted into the "Your Device Is Corrupt" screen, and would get stuck on the Google logo when it was booting. I finally got the A13 factory image to boot, but the "Your Device Is Corrupt" screen still showed every time i boot *as long as the bootloader is unlocked*. When I lock the bootloader it seems to be fine. After talking to a couple friends that have been rooting for a while, they somewhat think that I've done something to the NAND and should send back the device for a replacement. I'm not sure what to do now. Any suggestions?

You're fine...all androids have a warning screen after being unlocked.

Zaxx32 said:
You're fine...all androids have a warning screen after being unlocked.
Click to expand...
Click to collapse
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked

CobreDev said:
I hear you, but this is a prompt that showed before the typical bootloader warning. It says "Your device is corrupt. It can't be trusted and may not work properly. Visit this link on another device: https://g.co/ABH"
If I click the power button it continues on the the regular bootloader warning
My friends who have been rooting for years say that this is irregular and shouldn't happen aside from the first boot. It happens every single boot as long as the bootloader is unlocked
Click to expand...
Click to collapse
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.

Lughnasadh said:
That specific "corrupt" message you are getting when your bootloader is unlocked sounds more ominous than it really is. If you peruse through the Pixel 6 and 6 Pro forums you'll see that many people have encountered this message without any negative side effects and there are a few ways to get rid of it. In the simplest terms it's basically just a hash mismatch.
One method that seems to work well is to sideload the OTA during the next update. Even just updating via the "normal" OTA may get rid of the corrupt message.
Click to expand...
Click to collapse
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?

CobreDev said:
Ah interesting, so probably not corrupted NAND then. One friend told me to go ahead and sideloaded the Android 13 OTA (I’m on Android 13 currently), but i noticed in the root guide it specifically said *don’t* sideloaded the ota before rooting. If i sideloaded the A13 OTA now will i mess up anything for rooting, or should i just live with the error until the next update?
Click to expand...
Click to collapse
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.

Lughnasadh said:
Nah you NAND is fine.
The very first thing you should do before doing anything is make sure you have flashed the A13 bootloader to both slots to avoid having problems with the new ARB and bricking your device, if you haven't already.
Not sure what root guide you are referring to and in what context they are saying that, but sideloading an OTA shouldn't mess anything up relating to being able to root. It's really up to you what you do. You can live with that message for another couple of weeks (Sept. 6 is when the next stable update should be released), sideload the OTA or even dirty flash the factory image again (that might get rid of the message).
But whatever you decide to do, don't forget to flash the A13 bootloader to both slots before anything!!! I've seen a handful of people already brick their phone because they did not do this.
Click to expand...
Click to collapse
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!

CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
No problem and yep, that's correct. Just make sure you don't boot into the slot which still has A12 on it. Good luck!

CobreDev said:
Alright, i’ll try sideloading the OTA. I’ve tried flashing the factory image several times and it hasn’t fixed it.
To flash the bootloader to both slots, i follow the instructions on the Factory Image download page where it says:
# If your active slot is ‘a’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active b
fastboot reboot bootloader
fastboot set_active a
fastboot reboot bootloader
fastboot reboot
# If your active slot is ‘b’
fastboot --slot=other flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot set_active a
fastboot reboot bootloader
fastboot set_active b
fastboot reboot bootloader
fastboot reboot
Is that correct? Thanks for your help!
Click to expand...
Click to collapse
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.

Lughnasadh said:
Slight correction in case you haven't done it already. They instruct you to go use "adb reboot fastboot" at the beginning. That is wrong because that will put you in fastbootd and you can't flash the bootloader from fastbootd. Instead, at the beginning use "adb reboot bootloader". This is if you use Option 2 in their directions.
Click to expand...
Click to collapse
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!

CobreDev said:
Figured that out, thanks. Unfortunately sideloading the OTA didn't fix it, so i'll wait for the september update to see if that fixes it. Thanks everyone for the help!
Click to expand...
Click to collapse
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!

dannyzamora said:
Did you manage to solve the problem? If you still have not got it I will tell you that the same thing happened to me and I tried to flash in all ways and in both slots without getting it and in the end I managed to solve it by flashing the latest rom with the pixel flasher, checking the option to flash in both slots and checking the two boxes "disable verity and disable (anotherone)", at the end of the flashing I did not get back what was corrupt, I hope it helps you, greetings and good luck!
Click to expand...
Click to collapse
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!

CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
I’ll keep that in mind, thanks for the tip!
Click to expand...
Click to collapse
Try with the last update

CobreDev said:
i haven’t fixed it yet, because the September update hasn’t come out for Pixel 6a.
Click to expand...
Click to collapse
??? It came out earlier this week. https://developers.google.com/android/images#bluejay

Ah, must've missed that thanks

CobreDev said:
Ah, must've missed that thanks
Click to expand...
Click to collapse
Did you manage to solve it?

dannyzamora said:
Did you manage to solve it?
Click to expand...
Click to collapse
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now

CobreDev said:
I did, though fixed it by accidentally wiping it out. Oh well, it’s fixed now
Click to expand...
Click to collapse
Good news! Congratulations

Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty

jackfrost909 said:
Just got, just rooted, now on A13 Oct. and looking to "fix" this screen shouting to anyone who sees my phone boot, "come and get lunch".
Is this still the way?
ty
Click to expand...
Click to collapse
Unless there's an FBI agent out to get you, nobody will care. Most people won't even know what an unlocked bootloader is. If you're scared of hackers so much, reflash stock and relock

Question Why i cant updated latest QPR A13 for my pixel 6a

after download and reboot apprear this error..refer photo..

Try shutting it down, entering fastboot mode and flashing it from here.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
ok thanks..no need unlockboot loader rite?

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
You can't flash anything with a locked bootloader

ctfrommn said:
You can't flash anything with a locked bootloader
Click to expand...
Click to collapse
ok thanks..hmmm..

Boi. said:
ok thanks..no need unlockboot loader rite?
Click to expand...
Click to collapse
For Android Flash Tool you need to have OEM unlocking enabled in developer options, but don't need to actually have the bootloader unlocked beforehand. The tool will unlock your bootloader during the process (assuming you are able to unlock the bootloader, e.g. not a Verizon model). It will also lock it afterwards if you choose to do so.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
already try..still not work

Boi. said:
already try..still not work
Click to expand...
Click to collapse
You probably need to be more specific. What exactly happened after using Android Flash Tool? How did you initially try to install QPR1B1? Are you using the latest Platform Tools? Do you have the latest USB drivers installed? Have you tried using an A to C cable using a USB 2.0 port?
If you're flashing environment is set up correctly, you can also try sideloading the OTA image.

bfsr83 said:
Try shutting it down, entering fastboot mode and flashing it from here.
Click to expand...
Click to collapse
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...

Pakabidu said:
Thank you!
For the last 4 years I was updating my Pixels by downloading full official image and flashing without -w option, then patching boot.img via magisk and this process worked flawlessy every time. Tried same method with my new Pixel 6a on bluejay-tp1a.220624.021.a1 and every time I'd flash September's update bluejay-tp1a.220905.004.a2 my phone wouldn't boot and I would get "Your device is corrupt. It can't be trusted" error followed by google boot image and then boot loop. OK I thought, I'll wait until I've got time for a clean flash and that will solve it. To my surprise, it did not... Flashed clean image with full wipe and still same issue So now I did it via Android Flash Tool and it worked! For curiosity, then flashed the same image I had issues with via ADB and it also works now So what was the cause of the problem remains a mistery to me...
Click to expand...
Click to collapse
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...

Pakabidu said:
Update:
I think I was able to flash that image with ADB after doing with Android Flash Tool first is because it was the same image. Later tried flashing next month's update via ADB and had same issue again. So today decided to sideload November's update via ADB instead of flashing full image and that worked.
Just wonder what did I mess up for me not to be able to flash with ADB...
Click to expand...
Click to collapse
That is really weird behaviour for a Pixel device. I update using the stock rom method for all my pixels and never had issues. I have the Pixel 6 and the only instance I got the device is corrupt when I tried to roll back the November update to the October update causing a bootloop.
I wonder if there is something wrong with the 6A and some people having issues with the oem unlocking being greyed-out. Hopefully, Google will fix the issue with a future patch or monthly update.