WARNING!!!
I updated the RC firmware and battery update this AM. I flew this afternoon in an area that I have a minimum of 100 flights. It's my battery stretch area to keep them conditioned. I always fly at 100 feet and above to remain clear of all obstacles i.e. Tree's. I took off climbed to 124 feet and started to fly my normal race track pattern. I should back up for second and explain I had to reset all my pre-sets as they had been defaulted back to factory settings. After doing this and a normal pre flight and making sure I had minimum satellites I launched. As I started my first turn in the race track I noticed the trees looked closer than usual but as i started to react (throttle off climb on) it was too late. I heard the impact and the screen went blank. The I1 suffered significant damage. Would like to hear if others have noticed erroneous altitude readings since update. I will be calling DJI first thing Monday morning. Below is the final moments before the crash. Defiantly went into frisbee mode after impact. Unfortunately I wasn't shooting video.
Ouch... Bummer...

I watch my altitude readout a lot as my baro sensor gets a bit flaky sometimes... starts drifting over time just after takeoff...
DJI agreed and said send it back, but I am waiting for snow to fly (season over) before doing so...
In the meantime...I figured out what seems to work with mine to get by...
First flight of the day... I always go straight up and let it hover at say 30 ft and leave it for several minutes...
If the baro sensor going to drift today... readout will stay at 30ft but the bird will sink or climb slowly...
If it drifts... I have found I can keep nudging it back till it stops changing and hangs steady...
The readout will be all wrong by this point... I then land it and power cycle the battery...
Repeat and it will be fine... will work the rest of the day fine also... I have found on mine...
Does not mean other birds will do the same...Just saying what mine will do sometimes...
In summary...
I added "Baro Check" to my post takeoff checklist and check for drift before flying away...
30 seconds or so of no drift hover before I commit to flying away... all flights...
3 mins on first flight of the day... rock steady hover before I leave from the home point...
I also added "Readout Check" to my prelanding checklist...
I stop the landing at about 3ft AGL and glance at the readout to confirm it did not drift much during flight...
That said... mine started doing this way back in the early summer... big baro drifts of up to 70ft off...
Has not drifted as much lately... couple feet first flight... then steady rest of day...
No change really when I did last FW update on Friday...
Drifted maybe 2ft first flight today... about the same as before the last update...
My opinion... you may have had a baro issue... it was not a FW caused issue today...