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)
Related
Hello Guys,
I started to have problems with my wing and end up in three-color bootloader screen. I can tell you that I am not playing around with my phone. I do not even install any software not to risk its basic phone functionality since I am using this phone as a business phone. So, no crazy rom flash or etc has been done prior to this problem.
My phone started to have problems with answering calls last week. When it was ringing, it was keep ringing and I was not able to take the call even though I was pressing every possible buttons on the phone. It was locking.
I noticed that phone was locking the buttons too. So, I selected "do not lock buttons when the device is off". But, this does not have any effect. Phone was keep locking my buttons.
Last night, I noticed that my phone was unresponsive once again as usual, I soft reset the device, and it booted to the three color screen (I think you guys call this bootloader screen?) where it says "IPL 4.26.0002" and "SPL 4.26.0000". Tried to soft reset probably another 10 more times. same thing...
I took out the battery, went to sleep. Put back the battery in the morning, it booted to the OS and phone is running. But none of the hard buttons were working. It also hangs up the incoming call after first ring. I soft reset the device once again and it went back to the three-color screen.
I went to the Tmobile website, and found that there is an upgrade ROM. I downloaded and ran that program. It said that it installed it to the device successfully, and then the device rebooted itself. Guess what, back to the three-color screen.
I have been reading your forum since morning, and read a lot about brick phones etc. I tried couple of the techniques for recovering brick phones, but nothing helped. Hopefully, someone here can tell me what is going on, even though if the answer is to throw the device to the trash.
Additional Observations
It looks like nobody is interested
I have other observations.
- When "do not lock buttons" is checked, phone starts acting even more weirder. it generates keystrokes by itself. Camera starts taking photos.
- If the battery of the phone is out at least an hour (I don't know why), phones boots fine. If you soft reset at the moment, it will always goes back to the three color bootloader.
Can this be a virus?
I hope someone can help me, I have a Sprint Touch Pro2. Last night it randomly started rebooting itsself, i was not loading a new rom, i was not installed any software, i wasn't doing anything other that texting and IMing people. After i removed the SD Card, there were a few times i got it to load to the unlock screen, but once i got passed that it would say "starting device activation..." or something like that. Then i got it loaded but Touch Flo 3D would not automatically start. So i removed the battery and restarted it again and i went to bed and left it charging, and it kept restart itself again, when i woke up it the phone was dead, and will not turn on. The charging light is on but it will not turn on.
This happenned to me, i ended up having to exchange the phone.
have u tried a hard reset. U can do this by holding power button and call and end keys.
Phone must be off and it will completely erase your data
this sounds like what my phone is doing. is there a fix? i think im sol because i didnt buy it though sprint.
Not Hopeless
This happened to my Sprint TP2 I soft and hard-reset it but it still went back to the reboot loop.
I put it in the tri-boot screen and re-reflashed the stock ROM and all was well.
Same here
The same thing is happening for me right now. Soft-resets aren't helping. It's sporadic, however, sometimes saying it successfully activated and needs to reboot (then going into activation right away), sometimes saying it failed, and sometimes not coming up at all (but I'm pretty sure it's running in the background, even if I hit cancel, because the phone is very warm and the battery drains very quickly).
I took it to Sprint and they confirmed it was already activated. They tried manually activating it, succeeded, and it still kept doing it. However, both them and I were able to place a phone call, text, and visit a website... so basically it was working. But, like I said, this constant nagging of activation was running in the background sucking juice and killing performance. Their diagnosis was "it's acting weird". The main home screen clock has also been stuck at 0:00 ever since this started (though the lock screen clock and clocks in the World Clock screen are correct).
They said I could go to their service shop and do a diagnostic and backup/wipe/restore or they'd replace it under warranty if it still didn't work.
I figured I'd just try the hard reset myself tonight. Will post how that goes. I'm not sure what this "tri-boot" screen is, but I'll do some searching and check that out too.
I was using my phone this morning and I opened up chrome. As soon as I did that my phone restarted. I did a soft reset and it took me to an AT&T app page. I think it was something like Ready 2 Go(Not entirely sure of the name), and it said to press continue which showed me a Google setting page telling me I had turned off location tracking. I turned it on and went back to chrome (probably a mistake). It started restarting again, and it would take a few restarts before I got the screen, but then it went back to looping after 30 seconds, and I haven't seen the screen since. I already factory reset, and I tried recovery mode which showed me a red triangle ! icon. I have a Mac, and someone told me to plug my phone into the computer, but I want to make sure I know where to go from before I do that. Can anyone help?
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
Ever since yesterday my Google Pixel has been stuck in a seemingly endless bootloop. It all started when I was using the phone as normal, then it suddenly froze. I tried turning it back on, but that's when it started happening. Every time it resets there is always either a blue line in a random location or a blue smear on the bottom of the screen. I can't access recovery, but fortunately the bootloader is unlocked (as it says in the title). But even that doesn't seem to help as every time I flash a factory image, it does the same thing.
I have searched for any situations similar to mine, but I either encounter vague/unhelpful solutions from Google on the Google forums, or threads that aren't specific enough. I am making sure to be as specific as I possibly can so I don't try the wrong solution and mess my phone up even further.
I was successful at one point a little while ago. Throughout the day I let it do its thing to drain the battery, until it finally died. I noticed that when I turned it on, it had the "No command" message with the dead Android robot instead. I reflashed the stock image one more time, and it was successful. However, I was an idiot and took my phone off the charger, and with what minuscule battery life was left, it quickly died, strangely setting me back to the bootlooping I had originally.
I'm new to this website (and pretty much forums in general), and I had just signed up for this specific reason, so apologies if I come off as a bit clueless.
(Edit: It still seems like a chance-based thing, but the no command message may pop up after letting the phone die and turning it on.)
I'm having this same issue as of today. Have you had any luck resolving it?
Same here. I updated the most recent "security update" (~44MB) and the phone started to repetitively reboot cycle. First, it last for 3-4 hours of normal use, then quickly down to 10 min. And then it couldn't even pass the animation to complete the reboot. Called/emailed Google service. Tried to wipe/factory reset in recovery mode. No help. Or even worse. It's now stuck at the"Google" screen for a minute, and reboot. Any thought?