IPhone 4, 4s, 5, and 5c Continuously Powercycling after adding iOS 7.0

Question

For the last two months since the release  of iOS 7.0, my iPhone has been in a continuous powercycling loop. I've  backup and restored so many times, you would think I could frequent  flyer miles from the person administrating the apple server. Even though  the iPhone 4 is not my main use device, it is a device that I first  purchased at full price. So it is truly my device, and it really upset  me that this crap was going on with it. So for the last several weeks me  and a few friends conducted several experiments with the device and a  few others that are having this problem to determine what is causing the  powercycling issue. What we've discovered that the issue is in the  power saving control of the iOS. On three devices, we attempted to  charge the devices. After several days, the devices charged to 100%. It  was extremely diffcult to do. When the device all reached 50% charged,  the powercycle issue presented itself. When we recharged the batteries  again on the devices, it took much longer do so. This time, we disabled  the items that were hgh battery user, like wifi, bluetooth, lower the  brightness, etc. It of course it took longer for the battery to drain,  but when it hit 50% charge. The issue reappeared. We did this with  several other devices. We used iPhone 4, 4s, 5, and a 5c. All had  the same issue, and had the same results. We conclude that it is a  software issue. It's occuring on number of devices, with the same iOS. I  can simply say to 4, and 4s owners to either upgrade to a new device or  hope the next update of 7.0 will have a fix. 5C oweners, hopefully the  next software update will correct the issue. I hope this helps, please  conduct your own experiments, and post your results.

Answer 1

If this was an iOS issue, then, in your words, all users would be experiencing this. We have 5 iPhones in the family. a 4, 4s, 5c and 2-5s. None are experiencing this issue, and all are on the latest iOS 7.0.4. If you continue to backup and restore to backup, you will probably continue to see this behavior. I would assume there is a corrupt file in the backup that is continually bringing the problem back. Try to restore the device as new, and before putting anything else on the device conduct your test. If it fails, then get the hardware checked.