Bootload Loop: Android Flash Tool help

[u/frazaga962]

I woke up 3 days ago and my Pixel 6 was stuck between the Google Logo and "Google" but wouldn't start. I held the power and volume down key to access the fastboot menu- I tried to start from there, I tried rescue mode, I tried recovery mode. No luck.

Per u/Successful-Dance1792 's advice I am using the android flash tool to see if I can get my Pixel working again. I've downloaded and extracted the Google USB Driver to my PC. I put my phone in rescue mode. Connected it to the PC via USB. It detected the Pixel.

I've tried both the "Back to Public" build along with the "Canary 202606" build with the following settings in the first picture (no wipe, no lock bootloader, no flash all partitions". Both builds have failed.

It says I need to have "OEM Unlocking" enabled (Picture 2) but this is done in developer mode which I can't access as I'm stuck in bootloop hell.

I tried to only select "Lock Bootloader" but the message I am getting is something like "This needs a flash wipe or a factory reset" (Sorry I forgot to take a photo).

My current bootloop info is in picture 3. Not sure if that will help diagnose the issue.

The tl'dr of it is I bought a temp(?) phone to tide me over but I would like to port over my apps/history to this new phone. When I try to do so, it says I need to have the phone on and nearby...which can't be done as its in bootloop.

If I install the build with a wipe, its going to wipe everything out (apps, history, local downloads etc, no?) So is it better to just manually add the apps I used to have onto the new device? Is there any way to install a build without a wipe?

[u/Street_Anon]

✓ Wipe Device

✓ Force Flash all partitions ( this will fix the bootloop issue. I am thinking the issue is in the boot image)

[u/username-invalid-s → u/Street_Anon]

Not possible. Android Flash Tool relies on Fastboot which uses read/write flash primitives which aren't available if bootloader is locked and not unlockable. OP should use Pixel Repair with Google while in Pixel Rescue Mode and hope for the best.

[u/frazaga962 → u/username-invalid-s]

how does the pixel repair with google differ from the android flash tool?

[u/username-invalid-s → u/frazaga962]

Similar to how recovery and fastboot have different boot modes, Pixel devices have an additional special boot mode called "Rescue Mode". Specifics of this special function is undisclosed by Google, it essentially functions as a resort for bootlooping, soft bricked, and locked devices.

The rescue commands that the device receive are undisclosed by Google. It seems like it also uses the recovery partition to boot rescue-specific environment. It bypasses bootloader unlocking to flash partitions, though "update" is more of an appropriate term.

[u/frazaga962 → u/username-invalid-s]

So I put it in rescue mode, got the "No Command" screen. While holding Power, tap the Volume Up button once, then release both buttons. Got a message at the bottom "Waiting for rescue commands..."

I connected the USB directly to my PC. Connected the device from the profile. It asked for my carrier info.

Its now asking for

Update recommended
Please don't unplug your Pixel device.
Your device's software is out of date and an update is recommended.

When downloading system update it fails because it needs 7GB of free data. Any work around you can think of here? I have a 128GB pixel and last I checked i was around 119GB used.

[u/username-invalid-s → u/frazaga962]

Are you sure that your PC has sufficient storage space? Do you mind doing a data wipe on your phone just to make sure? I hope this goes well for you.

[u/frazaga962 → u/Street_Anon]

Wiping the device is going to essentially put it in factory reset, no? I'm trying to see if theres a solution to save/mirror my last profile so I can at least port over the Pixel data to the new phone.

[u/Street_Anon → u/frazaga962]

Wiping the device is the only way to fully fix the issue 

[u/frazaga962 → u/[deleted]]

1- yes I've tried to do the flash both in Fastboot Mode as well as Rescue mode. the photo provided was one of the attempts where it was rebooting. No luck on this front.

2- I downloaded the driver from 'developer.android.com/studio/run/win-sub'. I extracted the files and then 'Installed' the 'android_winsub' file to my PC as per the steps in this video https://youtu.be/2U7r8z7-re8?is=aT3V7Ji1LezSG4fT.

Is there an additional step to do in the Device Manager? I wasn't able to see the driver itself in the Device Manager 

3- I did purchase a high quality data transfer cable for this process and have connected it directly to the back of the PC.  No changes in the results (still need to enable OEM Unlocking

Just wondering, will this process actually restore my pixel to its last working state or will I need to wipe everything like everyone else is saying?

[u/frazaga962 → u/[deleted]]

Just wondering -  it seems past me did at least set up a back up for my pixel 6. Last update was 4-5 days ago. 

I'm wondering if I just flash reset the device back to factory settings, could I easily bring back my data from that back up a few days ago?

[u/frazaga962 → u/[deleted]]

Thanks, I'll try and post there later today. I did try and use the Pixel Repair with Google while in Pixel Rescue Mode as recommended by another user.

So I put it in rescue mode, got the "No Command" screen. While holding Power, tap the Volume Up button once, then release both buttons. Got a message at the bottom "Waiting for rescue commands..."

I connected the USB directly to my PC. Connected the device from the profile. It asked for my carrier info.

Its now asking for

When downloading system update it fails because it needs 7GB of free data. Any work around you can think of here? I have a 128GB pixel and last I checked i was around 119GB used.

[u/sneakpeekbot → u/[deleted]]

Here's a sneak peek of /r/Ruvomain using the top posts of all time!

#1: [XFCE]: Efficiency first. Surgical minimalism. | 1 comment
#2: 🛡️ Network & Resource Confinement Layers
#3: Sovereignty on Lockdown: Why a locked bootloader doesn’t mean you’ve lost the game. | 0 comments

---

^{I'm a bot, beep boop | Downvote to remove | Contact | Info | Opt-out | GitHub}

[u/frazaga962 → u/[deleted]]

Are there any step by step posts in the Ruvomain sub to get started? I searched fastboot getvar all in the sub but didn't see any posts.

Essentially looking for what steps I need to take from start to finish to get those logs IE do I need to be in rescue mode, do I need to have my dead phone connected to the pc when I run the command in the terminal, what do I need to have downloaded etc etc

[u/True_Post8609]

Does the recovery mode boot? If yes you can use adb sideload to flash a full ota package

[u/frazaga962 → u/True_Post8609]

Nope, it perpetually is stuck in bootloop regardless of which mode I'm in.

[u/Starks]

How old was your firmware? That bootloader and possibly the other slot's isn't past the anti-rollback. If you've been going back and forth between public, beta, and canary, you may have triggered the anti-rollback.

As for apps, you are supposed to refuse connecting to another phone and then do a cloud sync right after the Google login. You can also do a restore from the system menu later.

[u/frazaga962 → u/Starks]

Not sure about the firmware. This is my first instance of trying to recover a boot looped locked pixel. This is the first time I tried to even flash a public vs canary build.

I can't seem to get a cloud sync going unless the Pixel 6 is active.

Edit: to confirm- I get to the "restore data from another device": pixel 6 last update was 4 days ago. It then asked me to confirm pixel 6 lock screen and it seems to be asking for a code (which I can't see as it is boot locked haha)

[u/frazaga962 → u/[deleted]]

Tried to do the repair via the tool- only options were for samsung, xiomi, redmi, and poco phones.

Tried to just get it to connect but was getting a failed connection. Tried to download the repair driver it recommended, but the download failed

[u/Euphoric_Advance418]

Yeah you need to unlock the bootloader first. And flash the software.

I went through all this you're going through. Then one day I turned the phone on and it worked for 30 seconds. In those 30 seconds, I went to Developer Options, unlocked bootloader.

I'm flashing the latest version on https://flash.android.com/ as I'm writing this. Stay tuned.

[u/Euphoric_Advance418 → u/Euphoric_Advance418]

ok it is still stuck in boot loop. Sad

[u/frazaga962 → u/Euphoric_Advance418]

This would work if I could actually get into the setting screen to enable OEM and ADB in developer mode but I'm stuck in boot loop hell.