Hi all,
I'm working with the Android aosp for imx6q devices, version 7.1.2. We've managed to compile everything OK but when starting on recovery mode, the recovery.cpp application fails. It shows this message:
Could not mount /cache (No such file or directory).
But partitions in normal operation android detects and mounts OK all the partitions, including /cache, and it does not seem to be any differences in the fstab files between recovery and boot partitions.
Also, if I take a look at the serial console, seems that the SELinux is not giving permissions to the recovery service. This message appears everytime Android tries to execute the recovery service:
init: Starting service 'recovery'...
audit: type=1400 audit(243.990:6): avc: denied { read write } for pid=228 comm="recovery" name="card0" dev="tmpfs" ino=6663 scontext=u:r:recovery:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=0
init: Service 'recovery' (pid 228) killed by signal 11
I've tried to compare the recovery image with the default boot image and it only seems to differ in the init.rc file (and also, of course in /sbin/recovery). So, what's the problems? It's a SELinux permission problem or a parittion one?
Thanks in advance,
Solved! Go to Solution.
Hi Diego,
The problem is solved now. I've found that recovery.cpp needed the links to
the /dev/block/by-nam, but current android scripts did not create these
soft links
from dev/block/platform/soc0/soc/2100000.aips-bus/2198000.usdhc/by-name
I added this soft link into init.recovery.freescale.rc and now it's working
OK.
Thanks for your interest.
Carlos Fernández
Embedded software engineer
carlos.fernandez@idneo.com
IDNEO Technologies www.idneo.com
FICOSA Group www.ficosa.com
Polígon Industrial Can Mitjans, s/n
08232 Viladecavalls (Barcelona) - Spain
<http://www.linkedin.com/company/idneo>
<https://twitter.com/Idneo_Tech?s=02>
El mar., 19 mar. 2019 a las 0:12, diegoadrian (<admin@community.nxp.com>)
escribió:
NXP Community
<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>
Re: imx6q android recovery fails
reply from Diego Adrian Cuevas
<https://community.nxp.com/people/diegoadrian?et=watches.email.thread> in *i.MX
Processors* - View the full discussion
<https://community.nxp.com/message/1126434?commentID=1126434&et=watches.email.thread#comment-1126434>
Hello,
I apologize for the delay.
If you are still having a problem, have you tried disabling SELinux during u-boot, or with adb?
Best regards,
Diego.
Hi Diego,
The problem is solved now. I've found that recovery.cpp needed the links to
the /dev/block/by-nam, but current android scripts did not create these
soft links
from dev/block/platform/soc0/soc/2100000.aips-bus/2198000.usdhc/by-name
I added this soft link into init.recovery.freescale.rc and now it's working
OK.
Thanks for your interest.
Carlos Fernández
Embedded software engineer
carlos.fernandez@idneo.com
IDNEO Technologies www.idneo.com
FICOSA Group www.ficosa.com
Polígon Industrial Can Mitjans, s/n
08232 Viladecavalls (Barcelona) - Spain
<http://www.linkedin.com/company/idneo>
<https://twitter.com/Idneo_Tech?s=02>
El mar., 19 mar. 2019 a las 0:12, diegoadrian (<admin@community.nxp.com>)
escribió:
NXP Community
<https://community.freescale.com/resources/statics/1000/35400-NXP-Community-Email-banner-600x75.jpg>
Re: imx6q android recovery fails
reply from Diego Adrian Cuevas
<https://community.nxp.com/people/diegoadrian?et=watches.email.thread> in *i.MX
Processors* - View the full discussion
<https://community.nxp.com/message/1126434?commentID=1126434&et=watches.email.thread#comment-1126434>