Hi Brian, I have the exact same problem.
Trying to build a pixel-c with prebuilt libraries in vendor.img, but build is failing with: Check module type: out/target/product/dragon/obj_arm/SHARED_LIBRARIES/libzrp_intermediates/link_type FAILED: out/target/product/dragon/obj_arm/SHARED_LIBRARIES/libzrp_intermediates/link_type I am guessing it is to do with libraries linking to other libs in system partition can not be packed in vendor partition. Were you able to generate custom vendor.img and make it work after flashing? Appreciate any help! Thanks! On Friday, February 5, 2016 at 9:01:01 AM UTC-8, Brian Yee wrote: > > Thanks for the reply. > > I mis-spoked a bit in my original post. What I see happening is locking > the bootloader after I put my new software on works fine. The bootloader > is locked but now I see a screen that says "OS on your tablet is damaged. > Needs recovering." It is a black screen an in the upper left I have > options, using the had keys to navigate, to "Restart Device", "Switch to > fast boot mode.","Reboot into Android Recovery.", "Turn Off Device" and > "Switch to USB Recover" > > So I think I did something wrong that doesn't allow me to boot up back to > the home screen successfully. Even when I built stock AOSP and loaded it I > still got the same start-up error I talk about above. > > I followed the instructions found at: > http://rootzwiki.com/topic/15145-build-overrides-on-pure-aosp-builds/ > thinking that if I just fake out the build.prop everything will just verify > fine. This did get rid of the error when the framework starts up fine, but > this didn't resolve my current issue when I lock the boot loader. > > I noticed flags in fstab.dragon that said to verify system and vendor. I > removed them, but again it didn't seem to do anything extra for me at boot > time. I'm sure I'm doing something wrong, lol > > Basically my goal is to take a Pixel C and be able to flash it with custom > software. Then the company I work for wants to distribute them out to > customers. Warnings about the OS being unverified or the boot loader is > unlocked is scary to no technical people so we don't want to show it even > though we know it's ok. It's about customer experience, right? > > I assumed locking the boot loader would remove the wait for 30 seconds > screen, but this is not be the case as you said. So a lot of this effort > could be for nothing. I will have to try your original solution of editing > ActivityManagerService > and maybe this will fix my boot up issue when locking the boot loader. > > Thanks, > -Brian > > > > > On Thursday, February 4, 2016 at 7:42:15 PM UTC-5, Hamilton Turner wrote: >> >> Short answer: AFAIK, you cannot remove the warning at boot time unless >> you are working directly with an OEM or are an OEM. That comes from the >> bootloader, which is not an open component and you cannot readily modify. >> More details at >> https://source.android.com/security/verifiedboot/verified-boot.html and >> https://lwn.net/Articles/459420/ . The little dialog that shows when the >> framework first turns on is easily removable, but the actual warning on >> boot is not. >> >> I'm surprised to hear you can't boot if you re-lock the bootloader. In my >> experience this is not true - relocking just means you cannot flash more >> partitions without first unlocking again (which wipes the userdata >> partition). It doesn't remove the warning screen at bootup, which is what >> you're after, but it should not tank the bootup. According to the flowchart >> on dm-verity, all paths lead to "finish boot" >> >> Best, >> Hamilton >> >> On Wednesday, February 3, 2016 at 10:10:00 AM UTC-5, Brian Yee wrote: >>> >>> >>>> Prior emailer was mostly correct - this is caused by the build >>>> fingerprint stored in vendor.img not matching the one stored in >>>> system.img. >>>> See ActivityManagerService for the code that pops up this dialog (search >>>> for SHOW_FINGERPRINT_ERROR_MSG). This specifically relies on a call to >>>> Build.isFingerprintConsistent(), which itself just returns if the system >>>> properties ro.build.fingerprint == ro.vendor.build.fingerprint (the latter >>>> being set when vendor.img is compiled). Use "adb shell getprop" to check >>>> your own values. You cannot create a build fingerprint that matches the >>>> one >>>> inside the vendor bits unless you're working with the OEM, so aftermarket >>>> ROMs will always either show that dialog or choose to remove the code that >>>> displays it. >>>> >>> >>> I'm trying to build the AOSP for the Pixel C and while I am getting this >>> error I also get an error when I try to lock the boot loader again. I feel >>> like these errors are related. The error I get when locking the boot >>> loader is "OS on your tablet is damaged. Needs Recovery". I assume >>> because it is doing an OS verification check that I am failing. >>> >>> The in app error is easy to fix as you say you just remove the check, >>> but how do I lock the boot loader again? It seems like the unlocked boot >>> loader causes a screen to display on every boot that says "your boot loader >>> is unlock and the OS Verification check is disabled. Will boot in 30 >>> seconds" >>> >>> I don't want to see this screen and to wait 30 seconds, so I lock the >>> boot loader, but now I can't boot up. Any ideas on what I would need to >>> change and how to go about it? >>> >>> If there is a way to edit the vendor.img to have the correct build.prop >>> that would be awesome. This needs to get done, so if i have to get down >>> and dirty in kernel code or the boot loader so be it. Instructions would >>> be helpful though! >>> >>> Thanks, >>> -Brian >>> >>> >>> >>> >>> >>> -- -- 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]. For more options, visit https://groups.google.com/d/optout.
