• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Google Pixel 3a Stuck In Fastboot

Z

Zach Everheart

Lurker
I tried installing magisk to root my phone and it worked, however when I tried to reboot my phone it kept rebooting into fastboot. I looked everywhere for a solution and came up empty handed. Any help would be great
 
So why do you say that it worked? This sounds like it failed to me.

Can you reboot into android at all? Can you get back into recovery? If the answer to both is "no", i,e. you can only boot into fastboot mode, then you'll have to reflash the phone (you could try just flashing the boot.img if you have a separate image, or the ROM, but a full firmware flash will be the simplest and most likely to work).
 
Hadron said:
So why do you say that it worked? This sounds like it failed to me.

Can you reboot into android at all? Can you get back into recovery? If the answer to both is "no", i,e. you can only boot into fastboot mode, then you'll have to reflash the phone (you could try just flashing the boot.img if you have a separate image, or the ROM, but a full firmware flash will be the simplest and most likely to work).
Click to expand...

No I cant get into recovery or the android os and I assumed it worked because it flashed the file without any errors, where can I find the boot.img for google pixel 3a?
 
Zach Everheart said:
No I cant get into recovery or the android os and I assumed it worked because it flashed the file without any errors, where can I find the boot.img for google pixel 3a?
Click to expand...
Unfortunately all that tells you is that the flashing worked, not that what you flashed was correct, compatible and worked correctly.

You can find factory images (full firmware) for the 3a here, and flashing instructions here.

I've not downloaded and examined one of these files, but I expect they contain a set of separate images for the different partitions. If so you should be able to find the boot image there and could try fastboot flashing just that, or that plus the system image (ROM). But be prepared to do the complete flash if it doesn't work. Don't try reflashing the booloader separately: if that goes wrong you have a real brick on your hands (despite the name the boot.img is not the bootloader, it's the kernel and ramdisk).
 
Hadron said:
Unfortunately all that tells you is that the flashing worked, not that what you flashed was correct, compatible and worked correctly.

You can find factory images (full firmware) for the 3a here, and flashing instructions here.

I've not downloaded and examined one of these files, but I expect they contain a set of separate images for the different partitions. If so you should be able to find the boot image there and could try fastboot flashing just that, or that plus the system image (ROM). But be prepared to do the complete flash if it doesn't work. Don't try reflashing the booloader separately: if that goes wrong you have a real brick on your hands (despite the name the boot.img is not the bootloader, it's the kernel and ramdisk).
Click to expand...

So I attempted to flash the boot.img file and got this error: FAILED (remote: Failed to write to partition Not Found)
And I tried the system.img file too and got a different error: FAILED (remote: Partition boot not found)
So finally I clicked the 'flash all' file and got this error: FAILED (remote: Failed to write to partition Not Found)
Not sure if its my pc or phone or what
 
Is your bootloader unlocked? I assume it was when you flashed magisk, just wanted to be sure you'd not relocked it afterwards.

Is your fastboot program up-to-date? You can get those errors with an older fastboot program (though the fact that you flashed previously suggests it should work).

Did you download the correct firmware? I linked to the 3a firmware because that's the forum we're in, but if you have a 3a XL you should download the firmware for that instead (people sometimes are inexact about the model number so I have to cover all of the possibilities here).
 
Hadron said:
Is your bootloader unlocked? I assume it was when you flashed magisk, just wanted to be sure you'd not relocked it afterwards.

Is your fastboot program up-to-date? You can get those errors with an older fastboot program (though the fact that you flashed previously suggests it should work).

Did you download the correct firmware? I linked to the 3a firmware because that's the forum we're in, but if you have a 3a XL you should download the firmware for that instead (people sometimes are inexact about the model number so I have to cover all of the possibilities here).
Click to expand...

So I installed the boot.img and system.img with a newer version of fastboot and adb and it worked. Thanks for the help man!
 
You must log in or register to reply here.
Back
Top Bottom