I've had this happen twice since Saturday, so I'm thinking it may be a recurring issue that I may have to get looked into, but wanted to see if anyone had any advice or input on the matter....
I'm using 2.0.2 and had restored my iPhone 3G a while back because backups took 3 hours or more and every time I synced, the MDCrashReportTool would crash. The restore seemed to fix my issues for a week or so until Saturday night when I was syncing my phone. When it got near the end of its backup, the phone rebooted itself and got hung up on the Apple logo boot screen. I let it sit for 6 or 7 minutes and it never fully booted. I held down both buttons to shut it off and restarted, and it still never fully booted up. I eventually put it into recovery mode and restored it and it was going fine until this morning when it was backing up again and did the exact same thing.
Both times I restored, I tried to restore from my last backup after it was done, but after churning for a while it said it couldn't restore due to a corrupt backup or it being incompatible with my iPhone. I wonder if this somehow messed something up with the firmware that eventually craps out? I'm not going to attempt using the backup this time, and instead am letting it do its thing and will put everything back on there...
Has anyone else had this issue be recurring? If this does not work, I'll just take it to the genius bar and see if they'll replace it. I got the phone on launch day and have had no other issues, aside from the long backups and the MDCrashReportTool thing I mentioned above. A friend of mine mentioned that if they replace it, I'll get a refurb... is this true? My phone is pretty much in pristine condition, and getting a refurb (probably with scratches all over it) would be unacceptable to me. I also don't know how they'll handle it since it's not something I could necessarily reproduce unless I dragged my Mac Pro into the store and made it backup dozens of times until it happened (it will backup perfectly fine a number of times and then all of a sudden one time it will do this). If I bring it in restored, they'll see it functioning and probably say it's working now so all is well... and if I let it continue sitting at the boot screen, they'll restore it just like I have and claim it's fixed....
I'm using 2.0.2 and had restored my iPhone 3G a while back because backups took 3 hours or more and every time I synced, the MDCrashReportTool would crash. The restore seemed to fix my issues for a week or so until Saturday night when I was syncing my phone. When it got near the end of its backup, the phone rebooted itself and got hung up on the Apple logo boot screen. I let it sit for 6 or 7 minutes and it never fully booted. I held down both buttons to shut it off and restarted, and it still never fully booted up. I eventually put it into recovery mode and restored it and it was going fine until this morning when it was backing up again and did the exact same thing.
Both times I restored, I tried to restore from my last backup after it was done, but after churning for a while it said it couldn't restore due to a corrupt backup or it being incompatible with my iPhone. I wonder if this somehow messed something up with the firmware that eventually craps out? I'm not going to attempt using the backup this time, and instead am letting it do its thing and will put everything back on there...
Has anyone else had this issue be recurring? If this does not work, I'll just take it to the genius bar and see if they'll replace it. I got the phone on launch day and have had no other issues, aside from the long backups and the MDCrashReportTool thing I mentioned above. A friend of mine mentioned that if they replace it, I'll get a refurb... is this true? My phone is pretty much in pristine condition, and getting a refurb (probably with scratches all over it) would be unacceptable to me. I also don't know how they'll handle it since it's not something I could necessarily reproduce unless I dragged my Mac Pro into the store and made it backup dozens of times until it happened (it will backup perfectly fine a number of times and then all of a sudden one time it will do this). If I bring it in restored, they'll see it functioning and probably say it's working now so all is well... and if I let it continue sitting at the boot screen, they'll restore it just like I have and claim it's fixed....