It is advisable to format partitions userdata, system, cache.
If you are logged in droidboot is only possible from the system, or recovery, better to do it by making sure that the collected works recovery.
fastboot erase system
fastboot erase userdata
fastboot erase cache
I do not know whether to create droidboot file system or just demolishing the old one, but it would be better to boot into recovery and perform
make_ext4fs / dev / block / platform / [Platform] / [by-name or by-label] / [name] [section size]
cd out / target / product / [name devaysa]
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot boot recovery.img
the device will boot in rekaveri
Then can come out any small mistakes, such as I, sections userdata and system are not mounted in the recovery mode itself, so I was doing a ramdisk and fstab file, as a result, had to mount them manually
croot && bzr branch lp: project-rootstock-ng
cd project-rootstock-ng /
wget -c "http://ftp.heanet.ie/mirrors/ubuntu-cdimage/ubuntu-touch/vivid/daily-preinstalled/current/vivid-preinstalled-touch-[архитектура: armhf or i386] .tar.gz"
./rootstock-touch-install vivid-preinstalled-touch- [architecture: armhf or i386] .tar.gz out / target / product / [name devaysa] /system.img
machine reboots itself (possibly 2 times)
If the device reboots rekaveri, most likely, not enough room in
/ dataor / recovery (to get thrown off the downloaded file, it is better to change the path in the / storage / sdcard0).