The current state of your system is quite unclear, so it's hard to say what the best way to proceed is, except to run additional diagnostics. The Boot Info Script will provide at least some of the relevant information -- but given the number of things you've tried, there will still be some uncertainty about what that script returns. If you run this script and need advice, edit your post to include a link to the
RESULTS.txt file that the Boot Info Script returns, and add a comment to this reply to alert me to the new information.
If Windows is booting right now, then there is at least one thing you could try that stands a good chance of working: Install my rEFInd boot manager in Windows. Be sure to install the ext4fs driver (or the driver for whatever filesystem you used for Ubuntu). Depending on your configuration, that may enable you to boot Linux directly by using a rEFInd icon that refers to the Linux kernel (a file with a name that includes the string
vmlinuz). If Windows is not booting, you could try rEFInd from a CD-R or USB flash drive. (The rEFInd downloads page includes links to images for both these media.) That might get Windows and/or Linux booting, but I can't make any promises of that.
Another comment: The Boot Configuration Data (BCD) is a Windows-specific boot loader construct. Thus, the fact that you got messages about BCD when attempting to boot Linux is a clear indication that you were not booting Linux. Furthermore, the last I heard EasyBCD was pretty much useless for assisting in dual-boot configurations on EFI systems. Thus, you shouldn't bother with that software. Instead, use the firmware's own boot manager, GRUB, rEFInd, or another boot manager to select which OS to boot.
Right now, the easiest way to deal with Secure Boot is to disable it. If you must boot with Secure Boot enabled, though, it can be done. Theoretically, Ubuntu supports Secure Boot, but I've seen enough problem reports that it's clear that this support is far from perfect. If you use a third-party tool like rEFInd, you'll need to take extra steps to get it working with Secure Boot. The rEFInd documentation includes a page on Secure Boot, so consult it if you want to use rEFInd with Secure Boot. For other boot loaders, I've written a more general page on Secure Boot.