Thanks! Hmm,
So it is not possible to flash custom ROM/kernels on the Google Pixel Device ending up with enabled dm-verity? Or is that for all Android Devices? Is it possible to flash custom rom/kernels without disabling dm-verity? On Tuesday, 2 April 2019 23:23:04 UTC+2, Alessio Balsini wrote: > > > Thank you! > > This seemed to work :) > > Had to run the adb disable-verity command before remounting. > > That's strange, `adb remount` with -R should also disable verity. > Anyway, cool that it worked. > > > I tried enabling dm-verity after pushing the .ko modules > > > > It has resulted in "Your device is corrupt. It can't be trusted and may > not work properly. > > Visit this link on another device: g.co/ABH" > > > > Pressing the power button to continue takes me into the bootloader for a > few seconds, I see the Google logo for about 1sec. And Im back into the > Fastboot Mode. I guess I can flash Pixel factory image. But how do I get > pass the dm-verity check? > > That is an expected behavior, enforced for security reasons. > Unfortunately, being able to pass the verity checks would require to > update vendor.img, as well as the keys for all the verity checks, that > is not possible... > > Regards, > Alessio > -- -- 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.
