Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

This morning I woke up to my Samsung Galaxy S3 which just “hung” during the start-up screen with the white text “Samsung Galaxy S3 GT-19300” on a black background. It never comes to the “Enter Pincode” screen.

It worked without a problem when I went to sleep last night. As far as I know it should not update the software on its own, similarly the apps shouldn't update themselves without my confirmation.

I have tried to restart it and to take the battery out and put it in again but the result is the same.

Any suggestion or advice on how to fix this would be so much appreciated.

share|improve this question
    
Have you seen this thread? –  Suraj Bajaj Dec 12 '12 at 9:09
    
I too am experiencing the same problem. All attempts to reset/hard reset, enter download mode/recovery mode have been unsuccessful. Any attempt just results in the phone turning off/on and remaining stuck on the back screen with white samsung text. The problem occured while I was actually using the phone browser, phone just suddenly reset and now I am having this issue. All help will be appreciated. –  user25164 Dec 18 '12 at 2:46
    
Are you using a custom ROM? What you're describing is typical when a modified kernel you are using is not suited for the ROM you've flashed. –  Harsha K Dec 18 '12 at 3:38
    
Same problem. Hard reset doesn't work (can't get into that screen via the volume up/home/power button route). Did you by any chance just install AppBrain Ad detector? I did, so it's just a thought. (sorry I can't add this as a comment, so I've added it as an answer which it probably isn't...) –  user25233 Dec 19 '12 at 10:19
    
Hi everyone and thanks for your comments. My phone was not rooted or using a custom ROM, everything was the same as when it left the factory. I eventually went down to the store and they take a look at it. Sadly it ended with the phone being repair because there had been some malfunction in the memory-reading hardware it only was the ROM which was booted, no the operating system itself (or something very like that, can't remember the exact words from the tech guy). Thanks for all your comments. –  Mestika Dec 20 '12 at 7:21

protected by Community Dec 19 '12 at 11:19

Thank you for your interest in this question. Because it has attracted low-quality answers, posting an answer now requires 10 reputation on this site.

Would you like to answer one of these unanswered questions instead?

Browse other questions tagged or ask your own question.