I am not sure what was wrong with your case. If you have successfully upgraded bootloader, you should see bootloader version
b1c1-0.2-5672671 /home/wrk/q-10.0.0_r1$ fastboot flashall -------------------------------------------- Bootloader Version...: b1c1-0.2-5672671 Baseband Version.....: g845-00023-180815-B-4956438 Serial Number........: 89RY0ABZE -------------------------------------------- Checking 'product' OKAY [ 0.059s] Setting current slot to 'a' OKAY [ 0.074s] Sending 'boot_a' (65536 KB) OKAY [ 2.730s] Writing 'boot_a' OKAY [ 0.317s] Sending 'dtbo_a' (8192 KB) OKAY [ 0.430s] Writing 'dtbo_a' OKAY [ 0.095s] Sending 'vbmeta_a' (4 KB) OKAY [ 0.120s] Writing 'vbmeta_a' OKAY [ 0.063s] Rebooting into fastboot OKAY [ 0.060s] < waiting for any device > Sending 'system_a' (4 KB) OKAY [ 0.001s] Updating super partition OKAY [ 0.019s] Resizing 'product_a' OKAY [ 0.005s] Resizing 'system_a' OKAY [ 0.005s] Resizing 'vendor_a' OKAY [ 0.005s] Resizing 'product_a' OKAY [ 0.006s] Sending 'product_a' (317212 KB) OKAY [ 12.736s] Writing 'product_a' OKAY [ 1.828s] Resizing 'system_a' OKAY [ 0.006s] Sending sparse 'system_a' 1/2 (524284 KB) OKAY [ 21.396s] Writing 'system_a' OKAY [ 2.637s] Sending sparse 'system_a' 2/2 (287436 KB) OKAY [ 11.680s] Writing 'system_a' OKAY [ 1.600s] Sending 'system_b' (45756 KB) OKAY [ 1.863s] Writing 'system_b' OKAY [ 0.235s] Resizing 'vendor_a' OKAY [ 0.006s] Sending 'vendor_a' (453888 KB) OKAY [ 18.193s] Writing 'vendor_a' OKAY [ 2.280s] Rebooting OKAY [ 0.000s] Finished. Total time: 95.849s You can see the device rebooted once during flashing. In addition, you don't need to do " mkdir dist; make -j80 dist DIST_DIR=dist" since it fastboot should be able to locate out/target/product/crosshatch/ for new build image files. On Monday, September 16, 2019 at 7:38:34 AM UTC-7, subhani shaik wrote: > > Hi Chyifeng, > > I am facing the same problem like above. I even tried to flash both > partition using your steps and then flash the new build, hit the same > issue. Please check if my sequence of steps are incorrect. > > repo init -u https://android.googlesource.com/platform/manifest -b > android-10.0.0_r2 > > repo sync -j80 -c --no-clone-bundle --no-tags > > curl --output - > https://dl.google.com/dl/android/aosp/google_devices-crosshatch-qp1a.190711.020-861edfad.tgz > | > tar -xzvf - > > tail -n +315 extract-google_devices-crosshatch.sh | tar -zxvf - > > > curl --output - > https://dl.google.com/dl/android/aosp/qcom-crosshatch-qp1a.190711.020-f44a22d8.tgz > > | tar -xzvf - > > tail -n +315 extract-qcom-crosshatch.sh | tar -xzvf - > > > source build/envsetup.sh > > lunch 14 //crosshatch > > make -j80; mkdir dist; make -j80 dist DIST_DIR=dist > > copy and unzip aosp_crosshatch-img-eng.subani.zip > > fastboot -w flashall > > > Thank you for your help. > > On Saturday, September 14, 2019 at 9:35:07 AM UTC-7, Chyifeng Ding wrote: >> >> Yes, crosshatch for Pixel3XL works fine. Your Pixel3XL may have older >> version of bootloader. You need to upgrade bootloader first before flashing >> AOSP phone image. >> Download the production phone image >> https://dl.google.com/dl/android/aosp/crosshatch-qp1a.190711.019-factory-130c70be.zip >> >> unzip crosshatch-qp1a.190711.019-factory-130c70be.zip >> cd crosshatch-qp1a.190711.019 >> fastboot flash bootloader bootloader-crosshatch-b1c1-0.2-5672671.img >> fastboot reboot-bootloader >> >> You should be able to do "fastboot flashall -w" after that. >> >> On Friday, September 13, 2019 at 9:44:42 AM UTC-7, Surge Raval wrote: >>> >>> I've been trying to build android for the pixel 3 devices. Both sargo >>> and bonito build successfully and boot. However, crosshatch and blueline do >>> not. >>> >>> This is what I've tried and has worked on sargo/bonito. >>> >>> Pure aosp 10 r2 branch sync, lunch aosp_$(TARGET_PRODUCT)-userdebug. And >>> making dist and otapackage (otardppackage) >>> >>> the 3/3xl reboot from recovery, get to white Android splash and reboot >>> to fastboot immediately with the reasoning on the fastboot screen given as >>> "reboot to bootloader". >>> >>> Has anyone successfully built for crosshatch and/or blueline on Android >>> 10, and if so could you list your steps.. >>> >>> I should note, crosshatch will boot if I make an update zip with a >>> super_empty.img and manually fastboot in the order of boot, dtbo, vbmeta >>> (thehen reboot to fastbootd) flash super_empty over super (system_b) then >>> flash product, system, and vendor. >>> >>> This seems like it shouldn't be the only way. I'm looking for a way to >>> do this via sideload using update_engine as the facilitator rather than >>> fastboot. >>> >>> Thanks >> >> -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/07b8353f-ac3a-44c8-9e14-13ec0bc73b6f%40googlegroups.com.
