I have some good & bad news for commando development.
I have made and tested a perfectly working recovery for commando. It was a pita too as I had to alter the framebuffer driver to even get the recovery UI to display properly. The bad news is due to hopefully an unintentional engineering flaw in commando I don't feel comfortable releasing it currently.
NEC of course has fastboot blocked on the device and its a Code Aurora Foundation source device using "little kernel bootloader". The fault lies in the bootloader as it seems there is NO hardware key combo to boot recovery from a powered-off state (I also tried every key combo on it and verified from an inside source that there is no alternate hard-reset method). This bootloader is not capable of being updated via OTA so they can't easily "fix" it. The only way to boot into recovery is to call recovery from inside the OS via adb reboot recovery, a reboot binary, or to send the boot recovery intent like an ota update does. What this means is if you use this custom recovery and tinker/flash something to your phone that makes it unable to boot into android you will be software bricked and unable to recover. This also means that if you get pin/gmail account locked out of your stock phone and thus can't get into the settings menu you will also have no way to recover. To deepen this "security" NEC has also disabled the select/enter key in stock recovery meaning if a gmail locked stock phone user could issue "adb reboot recovery" they would be unable to even select the wipe data/factory reset option.
You know the more I think of it I'm nearly 100% certain this was no accident and is the most unusual "security" I've ever seen a company use on an android. Kudos to NEC for really thinking out of the box on this one!!
I'm hoping some of you users might find a hardware key way to boot recovery. In this current state I think it may be too dangerous to unlock for the masses the ability to flash custom roms & kernels.
Anyone who just wants to root the phone psneuter works flawlessly on it.
I have made and tested a perfectly working recovery for commando. It was a pita too as I had to alter the framebuffer driver to even get the recovery UI to display properly. The bad news is due to hopefully an unintentional engineering flaw in commando I don't feel comfortable releasing it currently.
NEC of course has fastboot blocked on the device and its a Code Aurora Foundation source device using "little kernel bootloader". The fault lies in the bootloader as it seems there is NO hardware key combo to boot recovery from a powered-off state (I also tried every key combo on it and verified from an inside source that there is no alternate hard-reset method). This bootloader is not capable of being updated via OTA so they can't easily "fix" it. The only way to boot into recovery is to call recovery from inside the OS via adb reboot recovery, a reboot binary, or to send the boot recovery intent like an ota update does. What this means is if you use this custom recovery and tinker/flash something to your phone that makes it unable to boot into android you will be software bricked and unable to recover. This also means that if you get pin/gmail account locked out of your stock phone and thus can't get into the settings menu you will also have no way to recover. To deepen this "security" NEC has also disabled the select/enter key in stock recovery meaning if a gmail locked stock phone user could issue "adb reboot recovery" they would be unable to even select the wipe data/factory reset option.
You know the more I think of it I'm nearly 100% certain this was no accident and is the most unusual "security" I've ever seen a company use on an android. Kudos to NEC for really thinking out of the box on this one!!
I'm hoping some of you users might find a hardware key way to boot recovery. In this current state I think it may be too dangerous to unlock for the masses the ability to flash custom roms & kernels.
Anyone who just wants to root the phone psneuter works flawlessly on it.