Hi and thanks for your assistance and your interest in my issues. I will keep an eye on that script BUT i do think that the root of all i described here with my VIM3L is a little bit more bad than just restoring stock LEDs behavior : by the way blue LED is controlled by the bootloader if i am not wrong, i must enter into it and then restore the blue LED on when powered off through KBI commands; red and white ones are controlled by the CPU and they are still working : red is off by default and white is always on by default when running OS AND it is easily customizable inside it AND different between OSes.
Thanks for your answser 
I do think that i will start another topic in the OOWOW section because this rescue software is very well designed and could be handy if it do what it supposed to do … AND i think that my issues have been triggered my an OOWOW script failure. I did a reset to factory default mode … it went well until blue LED blinking when powered off after the script end because i was supposed to eject SD and boot back into OS WITHOUT DCIN out and i tried everything : remote, key combinations, even ssh to power on my device again after that script was done : nothing worked, so i DCIN out and in again after 5s and OS boot up properly BUT, the is a big BUT : i loose : blue LED + KHADAS boot logo when booting from eMMC and my guess is that the OOWOW script mentioned above failed and that failure caused side effects … i do not not know if i should more concerned about those because my SBC is still working well.
OOWOW
→ working for me : wizard , uboot installation to SPI and almost all scripts …
→ not working for me : oowow installation to SPI in order to have it embedded, along with uboot into SPI and boot from SPI ! When i press ‘okay’ to flash it, oowow disable network each time before checking system updates AND then nothing can happen !!!, it could not be written to SPI through oowow BUT if i have the proper spi_update or spi_flash command maybe i could workaround this like @Electr1 told me for uboot installation to SPI … device info returns SERIAL NUMBER NOT SET and sometimes v12 or v14 for HW revision, it depends … SPI uboot info returns NOT RECOGNIZED, although it is in SPI …
→ command line should be helpful in my case but i need the assistance of KHADAS team, i do not know which command to run and i do not want to make the situation badly than it is ATM !
With that said @hyphop + KHADAS done a great job with OOWOW BUT there are inconsistencies from one board to another one i think ATM…
Anyway, i really like my VIM3L, it is very well designed and bricked resistant 
, and OOWOW is good but has issues with my board sadly 
It is a nice piece of work anyway .
Thanks for any further assistance,
Regards