First off, this is my friend's Droid 2 Global, and he asked me to post this question up.
Most of the time when I (on att) call him (verizon), his screen lights up black and the phone vibrates, but he can't answer the call. He can't do anything while I'm still ringing him, and when it's all over, the phone comes back to life; however, it doesn't recognize that it had any missed calls.
Any ideas of what's going on?
Do a factory data reset, it happened to me and this fixed it.
Sent from my DROID2 GLOBAL using Tapatalk
Related
I've noticed a problem that has happened twice with my new Nexus 5 so far - it will vibrate and then turn off. I don't know if it is going through its full shutdown sequence or not as what has happened is that the phone has not been in use, in my pocket once and I don't remember what the other time, and all of a sudden it vibrates once out of the blue, I go to check the phone and it is off. I can turn it back on again but find it weird that it seems to be crashing and then not even restarting - but being off. It is not rooted but the bootloader is unlocked so I can root in the future, if needed.
Is anyone else experiencing this?
rajax said:
I've noticed a problem that has happened twice with my new Nexus 5 so far - it will vibrate and then turn off. I don't know if it is going through its full shutdown sequence or not as what has happened is that the phone has not been in use, in my pocket once and I don't remember what the other time, and all of a sudden it vibrates once out of the blue, I go to check the phone and it is off. I can turn it back on again but find it weird that it seems to be crashing and then not even restarting - but being off. It is not rooted but the bootloader is unlocked so I can root in the future, if needed.
Is anyone else experiencing this?
Click to expand...
Click to collapse
Hi,
I have the same problem but i don't use the vibrator. My nexus works very good in all aspects but turns off randomly some days....
It's really disgusting and I don't know what I have to do for solve this neither...
Maybe use a manual one over a vibrator
Sent from my Nexus 5 using xda app-developers app
Hello--I've been having a minor but strange problem lately: my phone doesn't vibrate when it shuts down.
I've tested this on different sound (vibrate/silent/normal) settings and no matter what my phone does not vibrate when it powers off.
I'm not sure when this started, i.e. if you're going to ask me whether this stared after an OTA or something
I remember some time in the distinct past it used to vibrate, and the nexus 4 and galaxy nexus I had before most certainly did that as well.
My phone still vibrates on all other occasions.
I am fully stock (4.4.3 KTU84M), rooted
My phone doesn't vibrate on shutdown either. Nothing to worry about..
Sent from my Nexus 5 using Tapatalk
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
ZMaissi said:
Hi..
It's just a guess, but I don't think they waste any time trying to figure out what happened, specially since they already gave you a new unit. I would say, Don't bother
Enviado desde mi XT1080 mediante Tapatalk
Click to expand...
Click to collapse
Thanks, that is sort of what I was thinking. I suspect the boot partition is corrupt. But, wasn't sure being a new customer with Verizon.
Hey can you link me something about how you downgraded your droid ultra from SU6-7.2 to SU6-7
LOL, just flash SU6-7 (CFC-obakem_verizon-user-4.4.4-SU6-7-release-keys.xml) with RSD-Lite. That's the easiest way.
rfunderburk39 said:
Background, I have a Droid Maxx that I purchased/leased from Verizon, that arrived with 6-7.2. I downgraded to 6-7 and rooted. From the time of purchase the phone would reboot a few times a week. After rooting it began to reboot usually daily or many times a day. A week ago on Saturday it rebooted and began to loop from splash screen and back off. After many restarts it went into the factory recovery and no options would work and the screen forever went black. It has been charged for days, no button combinations work, except when plugged into the computer while holding the down vol it will load the hsusb drivers will sometimes load, and occasionally when connected to the computer or wall charger the green led will light. So I took the phone into verzion and they see the same results and attempted to charge it with both a cable and wireless, same results. So they shipped a new unit to me and before shipping this old one back to them I have a few questions for ones of you that may know the answer:
Anything I can do to restore it to stock? I assume no from my research
Will they discover its rooted?
If so what will be the resulting action?
Thanks for taking the time to read this.
Click to expand...
Click to collapse
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Mangu said:
Possible input hopefully it helps with your issue. Something similar has happened to me, but it was not software related. I am BootLoader Unlocked, but the only mod is for tether.
My phone would continuously reboot, but all I ever see is a black screen. sometimes when it stops rebooting the phone was actually powered on and responds to my voice commands, rings from calls, and notifications sounds work, but black screen.
My issue was actually due to the screen/LCD connection getting a little loose . Tech took phone apart disconnected and reconnected my screen, and problem solved. No more boot loops nor black screen.
It happened to me again a few months later, but I had dropped the phone a couple of times, which probably caused the loose screen connection a second time. After getting fixed again, I have had no issues, but then again, my Maxx also hasn't had any bad falls.
Click to expand...
Click to collapse
In the case of my phone, you could hold the power button in for a long period of time and then release and still nothing, not a flicker. I did not try voice commands, not a bad idea, but I did not want to open the phone due to the fact it was being replaced (further risking a decline on replacement).
On a similar note, the new unit seems to reboot at least once daily.
Hey, I have an unrooted and stock idol 3 that I was just playing a game on when suddenly the screen turned bright blue and then off. I tried to turn it on and it showed the Alcatel screen and then went blue again and this time turned off for good. I tried to go in to the recovery but that doesn't work either. I held down the power and volume for lots of time and in many different combinations also to no avail. The only thing the phone does is that the notification light turns on when the charger or usb to the computer is plugged in. Has anyone come across something like this and has any ideas how I can fix it? Any and all help will be appreciated, thank you.
Same here. Yesterday I was opening the camera app and the screen went blue. I've press the power and up button but the phone doesn't turn on.
What can I do?
I called Alcatel's customer service and they told me to send it in, luckily I didn't root my phone or anything, that's what I'm going to do. If you need to call them, the phone number is 855-368-0829
wow, that totally sucks. G/l with the repair/fix.
it looks it died simply. Can happen, nobody is perfect. Hope you get lucky with replacement.
@Cheeseball14 same thing happened to me. how did you proceed after calling the costumer service number? Were you asked to ship in the phone?
same issue as your post and others , i did call the alcatel warranty number , sent it to the Texas repair center , got my phone back , and still the same issues for the phone turned on and off , then screen turned blue , and didn't want to turn back on , then i called again, sent it again , they send me a pre paid shipping la label , hoping this time they will fix the problem, the web calls this blue screen of death
Fix Idol 3 won't turn on.
cheeseball4 said:
Hey, I have an unrooted and stock idol 3 that I was just playing a game on when suddenly the screen turned bright blue and then off. I tried to turn it on and it showed the Alcatel screen and then went blue again and this time turned off for good. I tried to go in to the recovery but that doesn't work either. I held down the power and volume for lots of time and in many different combinations also to no avail. The only thing the phone does is that the notification light turns on when the charger or usb to the computer is plugged in. Has anyone come across something like this and has any ideas how I can fix it? Any and all help will be appreciated, thank you.
Click to expand...
Click to collapse
I took mine back to seller (Bell). There they reset it to particular factory settings. Need to be careful otherwise to not erase the full system. Just a factory reset by Bell or your supplier.
Did your phone turn on? How could bell reset if it doesn't turn on like op's phone?
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
You're just in a bootloop. Try holding down power and home.
Sent from my Samsung SM-G930T using XDA Labs
That happened to me like clockwork until I found these fixes here. "Everything has stopped" and then wouldn't not from a restart.
http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
I refreshed probably 4 times thinking something was wrong with my phone until I flashed those fix zips in that thread. Solid ever since.