(EDIT: Sorry for giving the impression that you didn't need the i2 registered first - if you can't get it registered, give support at Diablosport a holler on the phone. Be patient, please...)
I've not had much luck with the Ignitor software, seems unstable - at least on my computers (Windows 7 64-bit, Windows 10 64-bit and Fedora 25 Linux 64-bit using the Java app under the Updater/Linux folder of the i2 drive). It seems like it updates some files, but removes other non-updated files at the same time. I've found an easier way to do the updates to the i2. This works for the initial update out of the box ONCE IT IS REGISTERED, and any normal updates afterwards. I've actually removed the Ignitor software from my computer.
0. Register your i2 - I originally had issues with the wireless password entry - the Enter key at the bottom of the wireless password screen didn't work for me - all the other keys did. I updated the updater module by downloading it from the DOWNLOADS section and putting it the root of the i2 drive. Once I did that, the Enter key on the wireless password screen worked for me (and it probably had nothing to do with that...but it worked for me.) I tried the initial update via wireless - sort of worked, some things got updated, others didn't. I think that while it was doing the update, the i2 was registered - at least the size of the info.xml file increased. I tried updating via wireless again, but it would tell me that it was up to date - but doing steps 9 and 11 weren't showing any modules or databases installed. I knew from previous experience with a DCX-1000 that something wasn't updating properly.
1. Go to https://www.diablosport.com/downloads/ and download all the files in the i2000 section of that page.
2. Plug in the i2 device into your computer and wait until the i2 drive appears. If Ignitor starts, exit out of it.
3. Copy all of the above files into the root of the i2 drive (where info.xml is located) I select all the files in Windows and drag them all to the i2 drive at the same time.
4. Wait for the i2 device to recognize that there are update files present and starts processing them.
5. Follow the directions on the i2 screen if any are presented (like clicking OK or NEXT or restarting, etc.)
6. Wait for the i2 to tell you it is completely updated (all the files you copied to the drive should have disappeared) and that you can reboot/disconnect the i2
7. Unplug the i2, wait 10 seconds, plug it back in to your computer and wait until it completely starts.
8 On the i2 device, wait until you get the agreement screen, then click "YES", then click on the "?" button on the extreme right top of the i2 screen.
9. Select the APPLICATION INFORMATION button, you should see the following:
- Vehicle (and a version number)
GUI (and a version number)
Installer (and a version number)
Updater (and a version number)
Logger (and a version number)
10. Click on the upper left arrow at the top of the i2 screen. It shoud take you back to the previous screen
11. Click on the DATABASE INFORMATION button
12. You should see the following:
- DCX_TUNES (and a version number)
DCX_PID (and a version number)
DTC_CODES (and a version number)
FORD_PID (and a version number)
DTC_CODES (and a version number)
GM_PID (and a version number)
DTC_CODES (and a version number)
GUI (and a version number)
13. If all these versions match their respective versions on the DOWNLOADS page, you are good to go!
14. After you have successfully installed your tune, reconnect the i2 to your computer and copy (not move) your INFO.XML file and the TUNES folder to your PC. Do this copy every time you load/change a tune to your car. The INFO.XML file contains your i2 serial number, and your encrypted license number among other things - these are important if your i2 gets lost/stolen. The TUNES folder contains another folder (which will be your VIN of your car) and inside that folder will be your original OEM tune and your current loaded tune (and any 3rd party tunes) and is also very important - as long as you have those, the people here at Diablosport can always get you working.
15. If you live in a state that requires emissions testing (like Pennsylvania does), then remember to either swap out your ECU (if you have a 2015+ Dodge/Chrysler/Jeep/RAM, basically a Fiat Corporation of America - FCA) back to the original ECU, or if not a 2015+ FCA automobile, load your original, backed up OEM tune, far enough ahead of time to get at least 100 miles on the car - otherwise, you will fail the emissions test because there is not enough data for it to evaluate, and will have to return to the inspection station and get re-tested (and maybe re-pay!) for the test. This also applies if you are going to take your car to the dealer for work or a recall. If you have an unlocked ECU (2015+ Dodge/Chrysler/Jeep/RAM), and they do an ECU update...you're encrypted again and the ECU is locked! Diablosport can fix that....for a fee! (and don't moan about it, it was YOUR fault!)
NOTE:
Although this method works under Linux, for some reason the i2 hangs between running the update files. If that happens to you, load the downloaded files to a USB stick, take your i2 and i2 USB cable to a friend that has Windows, plug in the i2 and your USB stick, and load the files from your USB stick to the i2. As long as the i2 shows up as a drive, you do not have to load anything on their computer. I'm not sure why Linux is hanging, one of these days I'll monitor the USB connection under Linux and Windows and see if there are any differences in what is happening. In theory, doing the updates this way, at the actual point of updating, the USB should only be supplying power to the device. Again, in theory, once those files are loaded on the i2, you could be powering it from an external USB power bank! The computer on the i2 is handling everything at that point. And, as a last insult...the i2 operating system is based on Debian Linux!!!