Is the 14.04v measured with the key off not running?
Post a pic of what is under the tank.
Tell me you performed all of suggested step 2 in post #3. Bad battery connections are the number-one reason for clock-resetting.
What is your bike's WARM IDLE RPM? Spec is 850~950rpm. The oil pump and magneto are gear driven. If warm idle is too low then oil flow and battery charge are reduced.
What battery charger are you using? Let's be certain its lithium friendly. Candidly hopefully it's the Shorai charger as it charges all cells independently. Low battery power or a weak cell is the number-two reason for clock-resetting and one reason for hard starting.
I'm going to point you to the Documentation forum to actually verify all three air pressure sensors are connected correctly. Yes jug means cylinder. Jug#1 is the rear one. Jug#2 is the front one. Check wire colors and hose connections and be certain the ambient one has no hose. Look at the two appropriate attachments here and compare carefully to your bike's conditions:
This area is a storehouse for Beginner's Modification help screens. 1. This Table of Contents. 2. Problems After VBAK/BAK or Ignition Coil Relocation. 3. Selecting and Installing Aftermarket Fuel Dry Breaks. 4. Turn Signal Fast-Flash and Click of Death (COD) Solutions. 5. AIS Bracket...
www.rswarrior.com
Also please snack on every post in the following:
Now that the major things on my Warrior are sorted out, I figure that it's now time to put some more effort into this small but annoying issue: the clock and trip meters reset every time I turn on the bike! The battery is a brand new Shorai, and I've cleaned/sprayed/reconnected every connector...
www.rswarrior.com
Whether or not you have already fixed the problems above, you still need to learn wassup with the Code 25 displaying. Dig through all of Chapter 6. Start with a solid read-through. Then brush-up on when a Code is accompanied by check engine light (CEL) illuminating. Then pdf-search for criteria '25' and discover all the things that can actually generate Code 25. Also perform a deletion step to delete all codes in history. Compare your observations to Chapter 6.
Finally, no matter the outcome of everything thus far, go to Documentation forum Table of Contents find Setting up the Warrior for Tuning and download the help file. Use that to write your own process procedure to establish tune baseline. Then tune your Warrior.
History tells me that what's been suggested here will 99% lead you to the fix, even if it's just getting you to a spot where you stumble across it. I'm here less and less, demands elsewhere, if you post descriptively enough to document your work and observations then others will jump-in. Luck to ya brother. The trouble associated with this is 99% of the time so minor it's brushed-by in the agony of trouble shooting

.