Appears your stock recovery partition is borked and probably has been for some time. You would not necessarily notice unless trying to access stock recovery (rare) or perform a rollback/upgrade which requires a working recovery. Normally I would lean towards repairing recovery but given the presence of Safestrap and now a soft bootloop I think moving to a stable rom takes priority. I'm assuming to can still boot into Safestrap recovery.
The bootloop may be due to the presence of the 13.1.0 update file and/or an OTA update that came down from Amazon if you left wifi enabled and airplane mode was not active. You might be able to remove the update .bin using the File Manager built into Safestrap (under Advanced). You should find the update file in the root of sdcard. Navigate carefully as you can do irrevocable damage deleting things from the wrong folder. If that doesn't help stronger measures are needed.
Things to consider:
- your device is obviously unstable and at risk of becoming an unrecoverable brick; immediate goal is to minimize the risk of this occurring
- data preservation is now secondary; if you can get into Safestrap recovery you should be able to make a backup of your data partition for future restoration
- next step involves flashing Nexus 2.0.5 to the STOCK slot replacing FireOS. Normally this is not recommended but is now needed as FireOS is unstable. Either FireOS or Nexus must be in the stock slot to recover a 'native' version of FireOS which is needed for subsequent rollbacks/upgrades/unlocks. I have been advised by @ggow not to flash the SS version of FireOS 3.1.0. That leave Nexus as the only alternative.
- we are in uncharted water. I am taking a best (reasonably educated) guess on the safest path. It may not work with unfavorable outcomes. You are welcome to seek assistance from another party. That's not sarcasm. I'm willing to continue but may make a miscalculation that could leave you with a brick.
Give it some thought and let me know how you want to proceed. Sorry this has happened.
okay this may be the same nexus i had before i did a factory reset. this must be were the problem developed because i was still rooted and ota were disabled still.
anyways how do i get nexus if ss is installed it specifically ays to not install if ss is active. Thank you this is not your fault it is solely mine
do you think it would be a better choice to jsut restore my previous back up of 3.2.4 ?
---------- Post added at 03:23 AM ---------- Previous post was at 03:10 AM ----------
restored to my back up of 3.2.4 and it is working correctly what route would be best to go from here. My initial endgame was cm12.1 and unlocked bootloader so i didnt have to lug around fire Os anymore but i seems that it will be quiet a bit of work since my last rom is still somewhat intact