Flashing AOSP on Pixel3/Blueline

[Doug Swalen]

I'm not entirely sure this is the right forum for this question but I don't see any other forum that is a better fit either...

So previously with Pixel/Sailfish when I would build and flash AOSP it was straightforward. I'd do the build and then flash four files copied from the out/target/product/sailfish directory...

fastboot flash boot boot.img

fastboot flash system system.img

fastboot flash userdata userdata.img

fastboot flash vendor vendor.img

This procedure would work on Pixel...as it had worked for my Nexus devices previously as well.

But with Pixel 3 the steps outlined above do not work. After flashing the aforementioned files, I do fastboot reboot and a splash screen appears for a second like the boot is going to go through but then I'm taken back to the bootloader.

I can still put the Factory back on but whenever I try to put AOSP on the way I'd been doing it, it doesn't work. I don't think this is a build issue because I'm doing an unmodified AOSP build with no code changes so the build should be good.

I went looking for instructions to see if there's been any change in flashing procedure or a listing of what needs to be flashed but the only document I found was located here...

https://source.android.com/setup/build/running

...and it's not current (doesn't mention either the Pixel 2 or 3 line of devices when doing builds)

I did notice that it recommended using fastboot flashall but it wasn't clear on what was to be flashed. Am I to just grab every .img file out of my out/target/product/blueline directory and run flashall? Or some subset of those files?

If anyone can clue me in on the best method for flashing AOSP on the Pixel 3, given that my old method is apparently no longer operative, I would be very grateful.

[Doug Swalen]

Add Crosshatch and Walleye to the list of Pixel devices I can't flash and boot AOSP on. 

So in summary, Sailfish I can build straight clean unmodified AOSP and flash and successfully boot to. But Walleye, Blueline, and Crosshatch all try to boot after flashing but then wind up back at the bootloader. I don't have Marlin or Taimen devices so I can't check them.

This is very frustrating. It sure seems like beginning with Walleye something has changed in the flashing procedures because what worked for Sailfish no longer works. But I have been unable to locate any information suggesting any change has taken place. 

So I don't get what's going on except that I can't make AOSP and successfully flash it to Walleye, Blueline, or Crosshatch.

[Colin Cross]

The documented way to flash a device is fastboot flashall.  I'd suggest trying that first, and it will tell you which images it's flashing.

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Doug Swalen]

I had tried fastboot flashall before but it didn't work. However when I tried it this time it did. Not sure what was wrong last time but at least now I know the correct method going forward for those non Sailfish devices. Thanks.

[jw wang]

Hi Doug Swalen

I came across the same issue of yours, do you at the end perform fastboot flashall in your /aosp/ANDROID_PRODUCT_OUT/ folder ?

were you flashing a userdebug build from aosp ?   is it possible to get every adb permission like adb remount, disable-verity, adb push..... ?

thanks