Originally Posted by geekmaster
I do not think diags uses upstart, or at least it did not on 5.0.x firmware.
You are probably right, though /etc/upstart/userstore is called from /etc/upstart/diags, which in turn is symlinked from /etc/rcS.d/S50diags...
I found by now also the reason for the missing files in /usr/local - it reminded me of the line "# TODO - make sure production loses /usr/local/bin to disable this
" seems that's not a "TODO" any more, but rather a "DONE".
strings system_diags |grep usr/local
mkdir -p /usr/local/sbin
rm -rf /usr/local/*
I don't know, why dropbear is explicitly named within the system_diags binary - I wonder, if it might actually be contained as a binary ressource or something, so that dropbear can be created "on the fly"... Whatever the reason, when "disabling diagnostics", the last line is executed any byebye dropbear. Maybe I'll try to install it in /usr/bin or something, and see if I can get a start-script to run it...
Another (pssibly) interesting thing that "strings system_diags" showed is that there are somewhere a few parameters for "idme", which suggest it might be possible to get into fastboot directly from diags:
strings system_diags |grep idme
idme -d --bootmode fastboot
idme -d --postmode diag-nuspo
idme -d --postmode normal
idme -d --postmode diag-nm
idme -d --bootmode main
Lastly I need to correct one thing that I wrote in my first post here: your RUNME.sh *is* executed also when booting into Diags mode, once the "mntus.params" is installed when booting to Main mode...