Hi ​@Erickeee , you can use the “Export Original” function from the Strava website, that is the uncut version. If you open your activity in the webbrowser, you will find it here: 

After downloading the file you can delete the activity and then upload the file on the Strava website: 

Thank you for the reply. I tried it and it worked. Thank you so much. 
 

Hello ​@Erickeee and everyone else - our team has confirmed that there is a bug related to the activity cropping tool on mobile. We will update this thread as soon as we have any more updates. In the meantime, please refer to the workaround posted by ​@Jan_Mantau in this thread  

Any updates? The same thing just happened to me with activity 15648075323.

Plus another question: Would it be possible to make the crop tool non-destructive? If the original file is still there (and can be exported), why not always use this as the base for the crop tool (even if the activity already has been cropped before)?

This just happened to me. Considering it’s possible to export the original activity, can support please recover the original activity? I just ran my first major marathon and after cropping 2 seconds ended up with a 33km run instead (activity 15642748469), losing not only all the data, but also the PB in my achievements.
I’m absolutely gutted. Deleting and re-uploading is not a fix but a fairly rubbish workaround - I do not want to lose all my kudos and comments on my run. 

I’m not aware the support is able to restore the activity with retaining the comments and kudos but you could try asking them anyway, contacting the support is explained in https://support.strava.com/hc/en-us/articles/216917777-How-Do-I-Contact-Strava-Support

In general you could consider to change the default visibility of your activities to private if not already done so. That would give you the time to make cropping, naming, adding pictures, restoring the activity and so on without someone seeing the activity meanwhile. After the editing you can change the activity to be visible to everyone.

Probably not support themselves, but the dev team can always update the database with correct data. I’m a dev and we’ve had an issue like this in our product and had to manually update the database to recover customers’ data. It’s a pain and not fast, but it is possible. 
Having to delete the activity and re-uploading should be a temporary workaround while they work on a fix and recover people’s data - The original data is not lost since you can export it in the first place and most people would have the original data from Garmin too.  

Have twice tried to crop a ride this afternoon and both times the crop has been far too severe - losing much of the ride.

The work around does work (thanks ​@Jan_Mantau !) but the bug is quite frustrating!

What’s the status on the bug fix & data recovery? ​@Lola