Hi,
Did anybody tried to overwrite the vendor modules by using Magisk
remounting ?
Thanks,
Luca
Il giorno venerdì 9 agosto 2019 alle 18:39:37 UTC+2 bal...@google.com ha
scritto:
> This explains the signature issue:
>
>
> https://groups.google.com/forum/?utm_medium=email_source=footer#!msg/android-building/pypiLF_tkxU/Yn9DKg3vEAAJ
>
> Cheers,
> Alessio
>
>
> On Monday, June 3, 2019 at 12:08:00 PM UTC-7, Raymond Wanyoike wrote:
>
>> I don't know; dmesg shows a bunch of errors in early boot:
>>
>> # dmesg|grep PKCS#7
>> [1.846059] PKCS#7 signature not signed with a trusted key
>> [1.855653] PKCS#7 signature not signed with a trusted key
>> [1.864403] PKCS#7 signature not signed with a trusted key
>> [1.871683] PKCS#7 signature not signed with a trusted key
>> [1.881490] PKCS#7 signature not signed with a trusted key
>> [1.897577] PKCS#7 signature not signed with a trusted key
>> [1.908881] PKCS#7 signature not signed with a trusted key
>> [1.921134] PKCS#7 signature not signed with a trusted key
>> [1.937646] PKCS#7 signature not signed with a trusted key
>> [1.957838] PKCS#7 signature not signed with a trusted key
>>
>> I tracked down the touchscreen module to /vendor/lib/modules/ftm5.ko
>>
>> # insmod /vendor/lib/modules/ftm5.ko
>> insmod: failed to load /vendor/lib/modules/ftm5.ko: Required key not
>> available
>>
>> I'll keep digging...
>>
>> On Mon, Jun 3, 2019 at 7:38 PM 'Alessio Balsini' via Android Building <
>> android-...@googlegroups.com> wrote:
>>
> Wasn't that module already loaded by init?
>>>
>>> -Alessio
>>>
>>> On Mon, Jun 3, 2019 at 4:59 PM Raymond Wanyoike
>>> wrote:
>>>
>> OK; more troubleshooting. Compiled the blueline kernel; patched it
with root (su); and booted it it up:
...
$ adb shell
$ su
# insmod /vendor/lib/modules/snd-soc-sdm845.ko
insmod: failed to load /vendor/lib/modules/snd-soc-sdm845.ko: Required
key not available
# dmesg | tail -n3
[ 507.155988] PMI: smblib_get_prop_dc_online: POWER_PATH_STATUS = 0x95
[ 507.156461] healthd: battery l=88 v=4314 t=27.6 h=2 st=2 c=-494
fc=2956000 cc=65 chg=u
[ 519.116179] PKCS#7 signature not signed with a trusted key
* **signature not signed with a trusted key*
On Mon, Jun 3, 2019 at 5:31 PM 'Alessio Balsini' via Android Building <
android-...@googlegroups.com> wrote:
>>> Not so easy... :) Drivers built for a given kernel may not be
> compatible with a different kernel build due to ABI breakages.
> As a result, in most of the cases (is ABI changed), old drivers must
> be substituted with new ones to work.
>
> Cheers,
> Alessio
>
> On Mon, Jun 3, 2019 at 2:50 PM Michael Burrows
> wrote:
> >
> > Thank you for helping me out a while back Alessio! I am now about to
> build the kernel again. Is there a way to implement the touchdriver(and
> maybe other drivers missing aswell) before building? To avoid having to
> do
> the steps you have provided me with? I know there are drivers I have to
> download before building AOSP. But I cannot seem to find any information
> about downloading drivers for the kernel.
> >
> > Thank you once again
> >
> >
> > tirsdag 2. april 2019 23.23.04 UTC+2 skrev Alessio Balsini følgende:
> >>
> >> > 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 android-...@googlegroups.com
> > To unsubscribe from this group, send email to
>
> android-...@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
