iPhone bricked? - No reason.

[mrkgoo]

I received a text message (I felt the vibration), and when I pulled it out to take a look - it was completely non-responsive. Home button, sleep wake button. Nothing.

SO I plugged it into iTunes, and nothing....for a few seconds then it jumped to life, making a buzz, a beep, and some other weird sounds. Then synced up.

Odd.

Then it died a few moments later - completely unresponsive again.

I plugged it into iTunes again, and it had an error 'reading the device'. Un plugged and replugged, and it synced, but nothing was showing on the display.

I held both buttons down to hard reset, and then it booted up. It seems ok. What could be wrong?

 

[Gamecockfan1214]

Thats sucks man. Have you tried putting in DFU mode and just completley restore it. Go on youtube and type in DFU mode and it will show you how. Make sure you follow the steps exactly.

 

[mrkgoo]

Thats sucks man. Have you tried putting in DFU mode and just completley restore it. Go on youtube and type in DFU mode and it will show you how. Make sure you follow the steps exactly.

Thanks for the advice - hopefully I never have to use the DFU, but as mentioned in my previous post, I got it going just by a double-button reset.

My curiosity was wondering what happened. I'm familiar with iPhone crashes requiring a reset, but this looked like the screen was dead, and all controls were dead. Is it possible a software issue locking out everything? Like a memory not being cleared? I know it can crash the phone, but didn't think it would completely kill it (temporarily).

Still, the reset worked so maybe I should cross my fingers.

 

[Vandam500]

Well If I were you I would do a DFU restore just in case. What if it happens again and is irreversible? Just my 2 Cents

 

[DPA]

Wirelessly posted (David's Black 16GB iPhone 3G: Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5G77 Safari/525.20)

I would do a DFU Mode restore just to be safe. I think what happened is that the incoming text message was the final straw for crashing the iPhone. So once memory was required for receiving and downloading that text message there wasn't enough of it to complete the task. Since the phone crashed, there was no way for it to complete those tasks so it wouldn't boot up. That's my guess.

David

 

[fuzion11]

Wirelessly posted (David's Black 16GB iPhone 3G: Mozilla/5.0 (iPhone; U; CPU iPhone OS 2_2 like Mac OS X; en-us) AppleWebKit/525.18.1 (KHTML, like Gecko) Version/3.1.1 Mobile/5G77 Safari/525.20)

I would do a DFU Mode restore just to be safe. I think what happened is that the incoming text message was the final straw for crashing the iPhone. So once memory was required for receiving and downloading that text message there wasn't enough of it to complete the task. Since the phone crashed, there was no way for it to complete those tasks so it wouldn't boot up. That's my guess.

David

WOW that's quite insightful David.

But for a iphone to not have any more memory...how could that be possible?

Would it mean previous applications he had opened and shut, weren't really shut and were still running in the back ground? I thought I heard the iphone would automatically ask those apps to shut down due to lack of memory.

I'm wondering if the thread poster had "Backgrounder" running with a few apps?

Anyhow, I hope you figure out the problem and get back to a good iphone experience.

 

[bytethese]

I received a text message (I felt the vibration), and when I pulled it out to take a look - it was completely non-responsive. Home button, sleep wake button. Nothing.

SO I plugged it into iTunes, and nothing....for a few seconds then it jumped to life, making a buzz, a beep, and some other weird sounds. Then synced up.

Odd.

Then it died a few moments later - completely unresponsive again.

I plugged it into iTunes again, and it had an error 'reading the device'. Un plugged and replugged, and it synced, but nothing was showing on the display.

I held both buttons down to hard reset, and then it booted up. It seems ok. What could be wrong?

It's a computer, sometimes it crashes. No DFU mode needed as you said yourself, resetting it worked.

 

[mrkgoo]

WOW that's quite insightful David.

But for a iphone to not have any more memory...how could that be possible?

Would it mean previous applications he had opened and shut, weren't really shut and were still running in the back ground? I thought I heard the iphone would automatically ask those apps to shut down due to lack of memory.

I'm wondering if the thread poster had "Backgrounder" running with a few apps?

Anyhow, I hope you figure out the problem and get back to a good iphone experience.

My phone has never been jailbroken, unofficially unlocked, or otherwise. The closes thing to a hack is to have run an approved app from the store that has given me emoji.

This DID occur to me, however - I was wondering if there was a memory leak or something.

I'm not sure how necessary a DFU restore at this point would be. It seems to be totally working fine now. If it happens again, I might try it, though. I think I will try and turn my phone off and on a bit more often.

Bytethese - I do realise it crashes, but I've never had a crash make the entire unit unresponsive with the screen off - normally it's when I was atually doing something - but I guess it's not impossible. haha, I just noticed in my fury of trying to make things work, I must've taken a screenshot, as I found a shot of my screen in the photo library when all this happened! Obviously all my commands had queued up and they all happened at once.

 

[DPA]

WOW that's quite insightful David.

But for a iphone to not have any more memory...how could that be possible?

Would it mean previous applications he had opened and shut, weren't really shut and were still running in the back ground? I thought I heard the iphone would automatically ask those apps to shut down due to lack of memory.

I'm wondering if the thread poster had "Backgrounder" running with a few apps?

Anyhow, I hope you figure out the problem and get back to a good iphone experience.

Well, there are 3 core applications that run in the background on the iPhone. Safari being one of them. App Store apps aren't allowed to run in the background. Safari only quits if you have no webpages open (only one Untitled page) when you quit or if you hold the home button for 10 seconds while exiting the app. It has been said before, it's a computer, computers crash from lack of memory. Usually they will put tasks off to the hard drive, taking the random out of Random Access Memory (RAM). I am not sure if the iPhone outs tasks off to the hard drive but I would assume it does. It still can run out of memory, though.

David