One month ago my Desire S crashed on floor. At first all seems to be ok, only a very small scratch.
After a couple of weeks the first strange behaveour: it becomes to close applications (sense, browser, meteo, mail...). I restarted it and it begins to loop boot even after a factory reset. I keep trying to restart the phone since finally it restarted apparenty correctly.
It worked fine for a week, then it begins again to crash applications and now I can't start the phone any more over the HTC logo.
No RUU, no factory reset, no recovery mode... only the bootloader.
It is possible that the crash on floor brake somehow the hardware in souch manner?
What can I do now?
Related
For the record...
my Raphael started a reboot loop about 6 months ago. It would start up, load the splash, and get to loading TouchFlo and then restart it.
At first I thought it was a bad ROM or radio. So reflashed with lots, but no difference.
Turns outs that the problem was the hardware restart button at the bottom of the phone. I worked this out as at no stage during the phones startup was I able to do a soft reset.
So, I dissembled the phone and took out the plastic V shaped switch and it worked.
Hi all.
Yesterday I installed a cab file that required my phone to reboot. Once I started to do so, my phone froze on the 'at&t world phone' screen during power up. I've removed the battery several times and tried to restart it but it freezes the same way everytime. I've also used the reset button to no avail.
Is there any other way to get it working or is it done for good?
Just hard reset it; hopefully, you remembered to back everything up before you installed the cab. If you didn't, then consider it a lesson learned. The device isn't bricked, but the cab must've screwed up the startup process somehow so that now the device won't start up.
I have had this tab for a few weeks and noticed that when it is in sleep mode the screen tends to go on and off randomly. Am I missing a setting or is this an issue. It is rooted and I am running GO Launcher. Any clues?
Mine re-boot randomly. So, I always kill the sound because I don't want to wake up at midnight by booting sound.
Usually my GTP reboot every 1~2 days, and became soft brick every 3~4 days. I should hard reset to boot it again.
What I have done to my GTP? All vanila. Original rom from factory, didn't root, just install 10~14 apps.
Mine kept rebooting randomly, and became a brick one day (hard brick). I tried to so soft reset, hard reset, factory reset, Odin and re-write Original ROM and etc...
Nothing worked. So, sent to Samsung service center. My tab was only 3 month old.
After fixed, random re-boot keeps happening.
Hey,
yesterday i faced a problem i didn't knew of yet. As i mentioned sometimes, i came from an One M7 2 weeks ago as it didn't work the way it should - camera useless and awful battery life. I rooted the M7, had problems with it and so on - just how it is with a rooted phone + custom roms.
However, due to the DRM i didn't root my Z3 yet. Yesterday i took it out my pocket, thought it was a bit warm.. nevermind. It worked. 30 minutes later i pulled it out again, still warm, and screen wouldn't turn on. I reset it (power and vol+ for those who didn't know), tried to boot again.. well, it took several minutes and finally showed me the attached error message. The system performance was really, really low. Everything stuttered, i couldn't even enter my pin. A few forced reboots later i could finally enter my pin and get into my system only to notice that my data partition wasn't doing fine. I had to set language and so on in the initial setup process, apps kept force-closing in seconds. My own apps were still on the device, however when i tried to open WhatsApp there was no data there, i should have gone through the registration process. The phone froze after seconds each time. I tried to enter the fastboot menu (is it called that way?) while booting to just do a factory reset, didn't find the button combination. So finally, after i found home without navigation from no man's land (sure, why doesn't it happen at home anyway..), i managed to boot it, get through settings and initiate a factory reset. Of course, all the apps were deleted then and i could install all apps like LightFlow again. Had to re-enter all the settings i did in those kind of apps, it was kind of annoying.
So, my questions: Why the hell did this happen to my Z3? Not rooted, didn't even think of it. There wasn't a day on the One M7 without flashing anything and it never happened. It wouldn't have been as bad as it was on the Z3, as i HAD root, could have wiped data in TWRP in a matter of seconds and also had backups of my data, which i of course didn't have for my unrooted Z3.
Is it likely to happen again? Can any app do this on a non-rooted phone? I read a bit about the error, that it would be caused by some apps, but not in the extent as it happened on my phone. Most of the times it would just be an annoying error message.
I got a thing in always getting a defective unit, so i hope it isn't happening again on the Z3
Maybe the internal flash is corrupted/failing. I had a similar issue with my HTC One X I went to nap one day and half hour later it shut down, it restarted but boot looped. Eventually it showed no data partition as being mounted and completely died. They replaced the motherboard.
Better contact Sony, maybe you need a replacement.
Mh, actually that's the least thing i want to do.. I'd have to wait for at least 2 weeks to get it back and chances are that they won't do a thing or damage it (bad experiences with my former Razr i). It works just fine after the factory reset, no errors yet. If it should happen again, i'd of course send it in for repair but i think, until then i will use it normally, with more caution and backups of course.
Probably the cleanest solution HERE
Hi, I was sitting down with my nexus on my leg with about 40% battery left when it suddenly turned off and then flicked to the google startup page before going blank. After attempting to turn it on again (to no avail), I resorted to plugging it in, which resulted in the phone looping on the google page then vibrating before repeating. I tried to get it into the bootloader menu, but it appeared and then reverted to the google page after the phone vibrated.
I've tried looking up solutions, but the only plausible situation for me seems to be returning it so the warranty can take over. The only hitch with that being that the bootloader is unlocked (not rooted, just the bootloader). I really am stuck, and do not know what to do. Any help would be greatly appreciated.
I had this one. Factory reset /wiping data was the only thing that fixed it. I assume something went corrupt with my data
Sent from my Nexus 5 using Tapatalk
It seems I got lucky. The phone rebooted properly and went to optimise all the apps as it would after an OTA update. It started up and worked as normal, until I restarted it, after being on for about 3 minutes, it turned itself off again. It rebooted in the same manner again, so I've just taken this time to relock the bootloader (so I can use the warranty if I can find proof of purchase (well, the date more importantly)). Hopefully this was just a little glitch, but I will post again for more advice if it goes wrong again (and I'll try a full factory reset first)