Related
Phone vibrates 5 times and has a green LED light that stays on. I was running Dark Unicorn v2 before this. It was on Safe Mode. I rebooted into recovery, and now the phone vibrates 5 times and a green light appears. VOL DOWN + POWER does not do anything besides that green-light five-vibration thingy.
Any ideas?
From what I read before, it's not dead. It put itself on some kind of mode. I don't remember where I read about this but let me do a quick search. In the mean time, have you tried adb?
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
siloner said:
From what I read before, it's not dead. It put itself on some kind of mode. I don't remember where I read about this but let me do a quick search. In the mean time, have you tried adb?
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Click to expand...
Click to collapse
I've been reading a lot about it. There was something called safe mode. From what I've read, it seems to be a problem with my volume button (perhaps the phone believe the volume up button is being pressed).
I cannot use ADB as the computer does not detect the phone/SD.
Does your volume up button feel like it's going out? Also try a battery pull then Vol down + power
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
siloner said:
Does your volume up button feel like it's going out? Also try a battery pull then Vol down + power
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Click to expand...
Click to collapse
I'm not exactly sure what you mean by "going out", but from the outside there doesn't seem to be anything physically wrong with it. I also never had any problems with it while I was using the phone normally.
The battery pull and VOL DOWN + POWER gives me five vibrations, and then a permanent green LED. I can't get the phone exchanged because I'm in India, and my warranty has already expired.
Well sorry but I'm out of ideas man. I'll keep searching for an answer and if I find something I'll let you know. Hopefully someone else sees this and has a solution
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
Your emmc chip has died this happened to me a while back that's all it has nothing to do with the buttons. I had mine for only a month and it happened to me so you will need another phone its nothing you can do with that device now
Sent from my SGH-T959V using xda app-developers app
tvotony said:
Your emmc chip has died this happened to me a while back that's all it has nothing to do with the buttons. I had mine for only a month and it happened to me so you will need another phone its nothing you can do with that device now
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Thank you for the information. Guess there's really nothing I can do to save my phone then...
Well, at least I will be out of the T-Mobile contract in February. Then I can get a new phone, and use a temporary crappy one until then.
DKMikey said:
Thank you for the information. Guess there's really nothing I can do to save my phone then...
Well, at least I will be out of the T-Mobile contract in February. Then I can get a new phone, and use a temporary crappy one until then.
Click to expand...
Click to collapse
If you have insurance they will replace it I used to have this phone back when I was a tester for team royal back in the glory day of this device
Sent from my SGH-T959V using xda app-developers app
This happened to me and I kept trying to boot into clockworkmod recovery. No matter what I did, it wanted to either do as you stated above or it would immediately try to load off the sd card my pd15img. I simply turned off the phone, pulled the sd card out, and when the phone went to the hboot screen with a volume up and power, or volume down, I then put the sd card back in and selected recovery. I don't know if this is what's wrong with yours, but I definitely had that 5 vibration flashing light issue.
V/R
Tony
Sent from my MyTouch 4G using xda premium
tony6083 said:
This happened to me and I kept trying to boot into clockworkmod recovery. No matter what I did, it wanted to either do as you stated above or it would immediately try to load off the sd card my pd15img. I simply turned off the phone, pulled the sd card out, and when the phone went to the hboot screen with a volume up and power, or volume down, I then put the sd card back in and selected recovery. I don't know if this is what's wrong with yours, but I definitely had that 5 vibration flashing light issue.
V/R
Tony
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
If you can get to the hboot screen you should load the pd15img. It would hopefully start you over un rooted
Sent from my SGH-T959V using xda app-developers app
What does the phone do when its plugged in? I only ask because mine was doing this same thing and it turns out it was a problem with my battery. I got a new one from Ebay for about 5 bucks but I also convinced T-Mobile that it was my phone and got it replaced. I had Insurance on it of course.
DKMikey said:
Phone vibrates 5 times and has a green LED light that stays on. I was running Dark Unicorn v2 before this. It was on Safe Mode. I rebooted into recovery, and now the phone vibrates 5 times and a green light appears. VOL DOWN + POWER does not do anything besides that green-light five-vibration thingy.
Any ideas?
Click to expand...
Click to collapse
I had that happen once also, I did the following and it booted up.
1) take battery out for at least 15min, (I don't know why, but it worked)
2) then do the volume-down+ power it should come right back up.
3) If I remember right, the battery that was in the unit giving me problems, was less than 20%, that very well could have been the real issue. Find a way to charge the battery then pull it.
TheAxman said:
I had that happen once also, I did the following and it booted up.
1) take battery out for at least 15min, (I don't know why, but it worked)
2) then do the volume-down+ power it should come right back up.
3) If I remember right, the battery that was in the unit giving me problems, was less than 20%, that very well could have been the real issue. Find a way to charge the battery then pull it.
Click to expand...
Click to collapse
1 + 2 tried, but didn't work.
Maybe I will try it with a new battery. Thanks for the information guys!
Edit: I do not have insurance (1 year is done)
The PD15IMG I had on my card was the original stock Ginger bread I think and I would had to have re-rooted.
Sent from my MyTouch 4G using xda premium
fried eMMC on MyTouch 4G
I'm also having this issue, got confirmed that my MT4G is dead, but I got it revived using this method here, it is not intended for MT4G, but i got it working...I temporarily using it, while waiting for fix (if there is any) and finding mainboard for my device.
chleoj said:
I'm also having this issue, got confirmed that my MT4G is dead, but I got it revived using this method here, it is not intended for MT4G, but i got it working...I temporarily using it, while waiting for fix (if there is any) and finding mainboard for my device.
Click to expand...
Click to collapse
Problem is, my phone doesn't even go into recovery...or hboot.
Any solutions yet? I've been reading this and have done everything here.
I've bought myself a new replacement battery off eBay. Charged it over night and still nothing. Powering up the phone, it vibrates. After powering up the phone and left it on for 5 min, I waited to see if it'll recognize my phone through the computer so I can check if it's the phone or the lcd, but still nothing. Any suggestion will be really grateful! And I have no insurance. Bought it used over Craigslist.
Sorry, I'm not trying to jack anyone's thread. Just didn't want to start a new one with almost the same problem.
I think your volume button is stuck was reading somewhere that someone fixed it by taking his volume button apart and it was stuck pressing up I think and that's y it was doing that not sure if this would help u at all but you might wanna try that
Sent from my HTC Glacier using xda premium
http://forum.xda-developers.com/showthread.php?p=29650107
Read that post it shows that the volume up button is stuck. The vibrations happens to me to if I power my phone down and then hold the up button and try and power on so I think that's the cause of all this
Sent from my HTC Glacier using xda premium
Hello everyone,
Curious if anyone is having the same issue as me? I have tried multiple roms, stock, with and without kernels.
I am having some touch issues. Either I have to press harder then normal at times or multiple times for my press to register. Its getting quite annoying. Not sure if this is a defect or if i can modify something within the system files to make the screen more sensitive or if there is even a way to re-calibrate my sensors/screen?
Thank you in advance,
DFL
Did you figure out what was wrong? ... It just started to do the same with me... Even to right this was a pain in the a$$...
Sent from my Nexus 7 using Tapatalk 2
ancostel said:
Did you figure out what was wrong? ... It just started to do the same with me... Even to right this was a pain in the a$$...
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
No, im still fishing around for a solution.
Any input would be appreciated.
Cheers
DFL
Well, I've rebooted in recovery mode, wiped the cache and it's back to normal now... I know it's just a temp solution, but you might wanna give it a try
Sent from my Nexus 7 using Tapatalk 2
ancostel said:
Well, I've rebooted in recovery mode, wiped the cache and it's back to normal now... I know it's just a temp solution, but you might wanna give it a try
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
hmmm... wiping cache fixed? i bet systemcleanup active would help then. I will take your advice and try out that app systemcleanup on my tab. I use on my phone Nexus S just didnt think the N7 would need it due to its specs.
Thanks mate, ill give it a go.
DFL
I had the same problem. So annoying. Take it back dude its detective.
Sent from my Nexus 7 using Tapatalk 2
I have the same issue but sparingly, turning my screen off and on fixes it for me tho.
Sent from my Nexus 7 using XDA Premium HD app
Fufu_the_Great said:
I have the same issue but sparingly, turning my screen off and on fixes it for me tho.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Has anyone decided if this is a hardware or software problem? I've started having the same issue. Turning off the screen sometimes fixes it for me but not always. A reboot always fixes it.
Like just now... I was playing Zenonia 2 and in the middle of a battle I suddenly couldn't get the touchscreen to respond. I hit power to lock the device and immediately tried to turn it back on with power again... but I couldn't even get the unlock screen to work. I set it down for about 30 seconds and when I tried again it was fine. I pulled the game back to the top and it worked fine.
When this happens the "soft" buttons (back, home, etc) always seem to work just fine, so I'm inclined to say it's really a software problem.
Running stock + root.
My thought is that it has to be a hardware issue, or if everyone with the issues is rooted than it could be from the root. My device has fantastic response however I am not rooted.
Sent from my Nexus 7 using xda app-developers app
Uh60m Pilot said:
My thought is that it has to be a hardware issue, or if everyone with the issues is rooted than it could be from the root. My device has fantastic response however I am not rooted.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would think hardware as well, but the home and back buttons always work and they use the same touch surface...
I got the same thing here and rebooting appears to fix it. Sometimes it is so bad that I cannot move icons from one screen to another.
Did you guys try flashing stock 4.1.1 using fastboot or the toolkit? If that does fix it then its probably hardware problem.
skinfreak said:
I got the same thing here and rebooting appears to fix it. Sometimes it is so bad that I cannot move icons from one screen to another.
Click to expand...
Click to collapse
I had the same problem ! solved by turning off the screen and turn on it
I have the same issue and mine isn't rooted yet so I don't think it is an issue with that. A wipe of the device doesn't help but a reboot usually does. This is my second N7 as the first was a warranty replacement for the headphone jack issue. The first never had the issue so I think it is an issue that should be addressed. I am outside my 14 days so I might have to go through Asus now.
---------- Post added at 01:23 PM ---------- Previous post was at 12:50 PM ----------
For what it is worth, I just called Google and they are going to send me a new one. The lady that assisted me stated that she has had a few complaints with this issue and that they just replace it. N7 #3 should be on the way in a couple days. For some reason she said that the device wasn't set up properly in my profile so it will add a couple days to the process because of the long weekend.
Not a big deal. I have lived with it for a while now. At least they appear to be taking care of it and I wasn't transferred to Asus. At least yet.
OK guys, woke up the other day to find the Nexus 4 with a solid (not flashing) red light and couldn't get it to boot or fastboot or anything, whether plugged into PC or not. Phoned google (they didn't ask about root or bootloader or anything) and they have sent a replacement. I will be sending my broken one back to them soon, but is there any chance I'll be able to relock it first? Does anyone have experience of this kind of situation before?
dannycorker said:
OK guys, woke up the other day to find the Nexus 4 with a solid (not flashing) red light and couldn't get it to boot or fastboot or anything, whether plugged into PC or not. Phoned google (they didn't ask about root or bootloader or anything) and they have sent a replacement. I will be sending my broken one back to them soon, but is there any chance I'll be able to relock it first? Does anyone have experience of this kind of situation before?
Click to expand...
Click to collapse
Don`t think they will be able to see or take the trouble to check if the phone`s unlocked. No, you cannot flash a image to a dead phone, if you could do that it wouldn`t be bricked
gee2012 said:
Don`t think they will be able to see or take the trouble to check if the phone`s unlocked. No, you cannot flash a image to a dead phone, if you could do that it wouldn`t be bricked
Click to expand...
Click to collapse
Well I hope you're right - would be frustrating to be punished for what is clearly a hardware issue!
And of course you can't flash a dead phone, I was wondering if there was some magical key combination that might reach fastboot that I haven't already tried or something like that :laugh:long shot I know...
dannycorker said:
Well I hope you're right - would be frustrating to be punished for what is clearly a hardware issue!
And of course you can't flash a dead phone, I was wondering if there was some magical key combination that might reach fastboot that I haven't already tried or something like that :laugh:long shot I know...
Click to expand...
Click to collapse
Volume down while inserting USB cable.
Does it for anything?
Sent from my Nexus 4 using xda premium
mariosraptor said:
Volume down while inserting USB cable.
Does it for anything?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Absolutely nothing, although I'd not heard that one before so thanks - with any luck it will just be checked for powering up and then wiped at Google once they can't get it on. I'm sure people must have sent phones to them in this condition before?
Usually by opening the phone and disconnecting the battery you can fix your red light issue, google it, it's pretty common.
yes but that also voids the warranty.
m4r0v3r said:
yes but that also voids the warranty.
Click to expand...
Click to collapse
Not if you do it right
Sent from my Nexus 4
dannycorker said:
Absolutely nothing, although I'd not heard that one before so thanks - with any luck it will just be checked for powering up and then wiped at Google once they can't get it on. I'm sure people must have sent phones to them in this condition before?
Click to expand...
Click to collapse
Follow iFixit guide or one similar. You won't void your warranty by taking off the back cover and unscrewing the screws that holding the battery connector.
Then remove and replace battery connector and undo all previous steps.
Sent from my Nexus 4 using xda premium
Volume up and power for 30 sec then power again does nothing?
Sent from my Nexus 4 using xda premium
jonapunk said:
Volume up and power for 30 sec then power again does nothing?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
No, no response at all from it whatever I do - might leave it a couple of days to see if the battery fully discharges, seen that in a couple of places as potentially helping. Wouldn't be too keen on taking it apart, seems like tempting fate regarding the warranty to be honest.
No just RMA it
Sent from my Nexus 4 using xda premium
Device : Nexus 7
Running : Android 4.1.2 Rooted
Problem : I was trying to unroot it and flash a 4.2.2 ROM to the device and i ended up bricking it somehow. I looked around a lot on here and youtube. I found one solution i had not tried which was to get into recovery mod. But the device was stuck on the boot loaded. So i hard shut it down, and pressed the key combination to load the boot loader. And, the screen wasn't loading. I heard the little chimes my computer makes when ever a USB device is active, so i heard the thing load into the boot loader. But its not showing on the screen!
Please help i really shouldn't have done this. But i am literally about to cry.
I tried using Wugfresh's Nexus toolkit to flash the ROM, and it would stop on sending system.
I dont know if i did something wrong, if the kernel was messed up, if the kit wasnt right, please as the video said there is 4 million members here. someone has to know what to do...
-Sean
That is not the bootloader. You need to have your device disconnected from your pc. Then go to your bootloader.
Sent from my SPH-D710 using xda premium
graydiggy said:
That is not the bootloader. You need to have your device disconnected from your pc. Then go to your bootloader.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Okay. I disconnected it and started the tree button combination.
Annnnd Nothing is happening.
Should i try plugging it into the wall outlet?
Volume up and power. Its not a 3 button combo.
Sent from my SPH-D710 using xda premium
graydiggy said:
Volume up and power. Its not a 3 button combo.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I feel kind of stupid.
Nope. Not working. And its not the battery. its plugged into the wall.
Just a noob guess, Is it possible the device isnt even using the display? Like its so messed up that its per say not even realizing it has a screen?
Try volume down and power. It is possible that the screens flex cable came loose. Pop the back off and check. You should be getting some visual queue. If all else fails hold the power button for awhile. Like around 15 to 20 seconds. I have had to do that a few times. That should fix it.
Sent from my SPH-D710 using xda premium
graydiggy said:
Try volume down and power. It is possible that the screens flex cable came loose. Pop the back off and check. You should be getting some visual queue. If all else fails hold the power button for awhile. Like around 15 to 20 seconds. I have had to do that a few times. That should fix it.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
OKay. Whats the best tool i should use to get it open?
Also thank you so much for your help.
You can use a fingernail really. The best thing is a plastic spuger. A guitar pic works nicely. Just start at the bottom and work your way around.
Sent from my SPH-D710 using xda premium
---------- Post added at 11:56 PM ---------- Previous post was at 11:53 PM ----------
Have you dropped the device at all or sat on it? If you are getting no visual queues, either you have a loos flex cable, or the lcd is cracked or just non functional all together. The best way to check that is to shine a flashlight at an angle into your screen. Look for any odd lines that have a slight or significant curve to them.
Sent from my SPH-D710 using xda premium
graydiggy said:
You can use a fingernail really. The best thing is a plastic spuger. A guitar pic works nicely. Just start at the bottom and work your way around.
Sent from my SPH-D710 using xda premium
---------- Post added at 11:56 PM ---------- Previous post was at 11:53 PM ----------
Have you dropped the device at all or sat on it? If you are getting no visual queues, either you have a loos flex cable, or the lcd is cracked. The best way to check that is to shine a flashlight at an angle into your screen. Look for any odd lines that have a slight or significant curve to them.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Assuming i found the right cable which was under a copper shielding that was running up from the metal frame under the battery. It was yellow.
It was tucked all the way in.
I didnt see any cracks or lines. I did sit on my pillow was under it.
That could possibly break the device. I just recently broke mine the other day in similar circumstances. The cable is right by the battery on the right. Should be almost centered by the batt.
Sent from my SPH-D710 using xda premium
graydiggy said:
That could possibly break the device. I just recently broke mine the other day in similar circumstances. The cable is right by the battery on the right. Should be almost centered by the batt.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Oh. But it was working the other day. Does it just do that?
and Yes i got the right cable. So what can i do now? It was rooted so i cant send it back, Is there anything i could do?
You technically could send it back... They can't confirm it is rooted unless you unlock the bootloader and the little lock thing shows up on the splash screen. And since your screen doesn't work, they can't see it unless they test the device after replacing the screen assuming they don't replace the whole unit. But I don't know their procedures. Most companies just replace the whole thing. The screen shouldn't just go out. Not saying it doesn't happen, but it shouldn't.
Sent from my SPH-D710 using xda premium
graydiggy said:
You technically could send it back... They can't confirm it is rooted unless you unlock the bootloader and the little lock thing shows up on the splash screen. And since your screen doesn't work, they can't see it unless they test the device after replacing the screen assuming they don't replace the whole unit. But I don't know their procedures. Most companies just replace the whole thing. The screen shouldn't just go out. Not saying it doesn't happen, but it shouldn't.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Alright. Ill call Google in the morning. I actually was following a guide i saw on a google forums thing where it said to flash the ROM if its not updating as it should. Which is what was happening.
Seanwoodfin99 said:
Alright. Ill call Google in the morning. I actually was following a guide i saw on a google forums thing where it said to flash the ROM if its not updating as it should. Which is what was happening.
Click to expand...
Click to collapse
Well good luck. Never thought one could fully brick a Nexus 7. From my understanding, it is damn near impossible. Tell them that you were updating to 4.2.2 and it won't boot up at all now. That should avoid them replacing the screen and checking everything ultimately getting you a whole new device. I know you said it's not the battery, but try charging it overnight and the try to boot it up. I have seen so many people think they bricked, but discovered later on down the line 'up to 6 months later' that their battery was just dead.
Sent from my SPH-D710 using xda premium
graydiggy said:
Well good luck. Never thought one could fully brick a Nexus 7. From my understanding, it is damn near impossible. Tell them that you were updating to 4.2.2 and it won't boot up at all now. That should avoid them replacing the screen and checking everything ultimately getting you a whole new device. I know you said it's not the battery, but try charging it overnight and the try to boot it up. I have seen so many people think they bricked, but discovered later on down the line 'up to 6 months later' that their battery was just dead.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yep its charging now.
Ill call in the AM if its not going. I got a case number and everything and i have Asus's number.
But seriously thanks for all the help youve given me.
I have a problem with my nexus 4
I am using stock 4.4 latest one and I am rooted and using closed fw
The problem is when I wake up I found that the alarm doesn't wake me up and th e phone is like shutting down I think it's freezing on the black screen and I cannot open it from the power button and I have to long press the power button to shutdown it and press it again to power it on and I found a missed alarm I don't know if that from the KitKat or from the root or what actually I didn't had this experience on JB
So if I can solve this just let me know Guy's
thanks
What happen when you plug in charger in it , can u see anything on screen , try charging your battery externally with a external charger , it's always good idea to start with simple steps
Sent from my HTC One using xda app-developers app
same
It happens on charging or not and if I put charger nothing happened
Can u go to download mode or have u tried factory reset already ??
Sent from my HTC One using xda app-developers app
Any luck buddy ??
Sent from my HTC One using xda app-developers app
no luck
Brownpanda said:
Any luck buddy ??
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
no luck man and i already did i don't know what to do and i put a custom rom based on stock img and kernel and i got the same issue and now i am using cm11 and i didn't get this problem till now i don't know if the problem on the phone or beacuse of the stock rom but i didn't get this on android 4.3 it's from kitkat 4.4.1 and up
anyone experience this like me ?
Have u tried replacing proximity sensor , I have seen this problem before with some of my clients , just a guess could be different issue
Sent from my HTC One using xda app-developers app
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
I nexus 4 proximity sensor is attached with headphone jack
Sent from my HTC One using xda app-developers app
Brownpanda said:
Have u tried replacing proximity sensor , I have seen this problem before with some of my clients , just a guess could be different issue
Sent from my HTC One using xda app-developers app
---------- Post added at 02:16 PM ---------- Previous post was at 02:15 PM ----------
I nexus 4 proximity sensor is attached with headphone jack
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What about a broken power button? I've replaced a bunch of them on sgh-t989, so what if it happened to the n4? I've been using mine ever since it was released in 2012 and there's no issues, but you never know... Just my first thought...
Also, the proximity sensor/headphone jack ribbon cable can be disconnected without affecting the usability of the phone, so i guess he could try doing that, if you say that it might need replacement of it.
Have u got chance to check proximity sensor , as other member suggested just remove sensor n check , it will even work without sensor but u may find your problem
Sent from my HTC One using Tapatalk
4.4 will not boot with proximity sensor/headphone jack cable disconnected - n4 will not boot past boot logo ...
Rolf2 , is it a new question ? U should start your own thread
Sent from my HTC One using Tapatalk
no, this is answer about proximity sensor , do you see question mark ?
no
Power button is OK because I can power it off and on again from it and prox I think it's OK I don't know