Re: [android-building] AOSP flashing Pixel 3 XL with fastboot
Glad it helped! Good Luck, Vitaliy Freidovich CEO1-Family 972 - 54 - 6465548 On Thu, Jan 3, 2019 at 6:34 PM Peder Møller wrote: > OK, thanks again Vitaliy Freidovich. Looking at the offcial build guide... > > https://source.android.com/setup/build/building > ...it is pretty obvious, that I was missing the proprietary binaries. For > some reason I could build and run on Pixel XL without these binaries but > for Pixel 3 XL, they were needed. > > > mandag den 24. december 2018 kl. 20.10.41 UTC+1 skrev Peder Møller: >> >> No I haven't. >> The AOSP building guides I have been reading so far haven't mentioned >> proprietary binaries. >> For the Pixel XL, it was not necessary to configure proprietary binaries, >> but maybe it's different for the Pixel 3 XL >> Thank you for the tip. I will certainly try to investigate this. >> >> søndag den 23. december 2018 kl. 17.18.39 UTC+1 skrev Vitaliy Freidovich: >>> >>> Hi Moeller, >>> >>> Have you configured proprietary binaries? >>> >>> Good luck, >>> >>> On Fri 21 Dec 2018, 5:59 p.m. Peder Møller, wrote: >>> >>>> I am trying to flash my Google Pixel 3 XL with my locally built AOSP. >>>> >>>> The build and flash seem to go smoothly, but the phone does not start >>>> up. >>>> At startup, the Google logo is seen shortly and then the phone boots >>>> again. >>>> I do not think there is anything wrong with the phone. >>>> When the phone is flashed with a factory image >>>> (crosshatch-pq1a.181205.006-factory-96b23504), everything works fine >>>> >>>> The AOSP repository has been retrieved with >>>> >>>> repo init -u https://android.googlesource.com/platform/manifest -b >>>> android-9.0.0_r21 --depth=1 >>>> >>>> compilation seems to work fine, flashing with >>>> >>>> fastboot -w flashall >>>> >>>> also completes without problems, but the phone doesn't start up. >>>> The interesting thing is that I have previously built an AOSP for a >>>> Pixel XL and that went fine, so it looks like some strange difference >>>> between Pixel and Pixel 3. >>>> >>>> I realize that there is a previous thread on something similar >>>> >>>> https://groups.google.com/forum/#!topic/android-building/lmCUWEgoaKQ >>>> >>>> but it was not clear what could be done to solve the problem. >>>> >>>> Any feedback would be highly appreciated. >>>> >>>> -- >>>> -- >>>> 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. >>>> >>> -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@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-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@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-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] AOSP flashing Pixel 3 XL with fastboot
Hi Moeller, Have you configured proprietary binaries? Good luck, On Fri 21 Dec 2018, 5:59 p.m. Peder Møller, wrote: > I am trying to flash my Google Pixel 3 XL with my locally built AOSP. > > The build and flash seem to go smoothly, but the phone does not start up. > At startup, the Google logo is seen shortly and then the phone boots again. > I do not think there is anything wrong with the phone. > When the phone is flashed with a factory image > (crosshatch-pq1a.181205.006-factory-96b23504), everything works fine > > The AOSP repository has been retrieved with > > repo init -u https://android.googlesource.com/platform/manifest -b > android-9.0.0_r21 --depth=1 > > compilation seems to work fine, flashing with > > fastboot -w flashall > > also completes without problems, but the phone doesn't start up. > The interesting thing is that I have previously built an AOSP for a Pixel > XL and that went fine, so it looks like some strange difference between > Pixel and Pixel 3. > > I realize that there is a previous thread on something similar > > https://groups.google.com/forum/#!topic/android-building/lmCUWEgoaKQ > > but it was not clear what could be done to solve the problem. > > Any feedback would be highly appreciated. > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@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-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@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-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [android-building] How to maintain android binaries checksum intact. after rebuild of AOSP.
Hello, I would kindly disagree, as your environment might change from build to build, and the resulting images could theoretically, and perhapps practically, behave differently. Thus it's a correct bahaviour in my opinion that the checksum changes. Good luck, On Fri 21 Dec 2018, 5:58 p.m. , wrote: > Hi Android Experts, > > > >We need some help / information that, Is there any way > to keep android images (system.img, boot.img etc ) checksum [md5sum/crc32] > same even after fresh build or recompilation??. Even though without > changing a single bit in the AOSP Source code if we rebuild it, Android > binaries checksum keeps changing. As I can understand that the > compilers/linkers adds the date and time-stamp to the images/binaries after > each build which causes the change in the checksum. So my question, Is > there any way to avoid this change in image checksum after every rebuild. > it should change only when we change any source code. kindly update. > > -- > -- > You received this message because you are subscribed to the "Android > Building" mailing list. > To post to this group, send email to android-building@googlegroups.com > To unsubscribe from this group, send email to > android-building+unsubscr...@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-building+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@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-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
