Background: Very familiar with the Eris, rooted it, flash ROMs frequently, never had an issue.
So I bought the phone on eBay, only issue was the phone was a bit beat up and the screen had been replaced. No big deal. Turned it on everything was fine, worked for about a day, then I decided to flash another ROM. Flashed the ROM and the phone would reboot every time I got to the lock screen UNLESS I had signal, then it would work. This issue happens to EVERY ROM I flash. I wiped cache,dvlik-orwhatever, full wipe, everything each time I would flash a ROM, and none of them have been stable. After flashing the first ROM I also ran into the turn off and vibrate 5 times with a flashing green light problem. I have gotten out of this twice with the USB pull method. I have researched these issues, I have tried flashing quite a few ROMs, and nothing seems to work flawlessly. Is the DI just a terrible phone or do I just have a bad unit? The main issue seems to be with signal, such as if I go from airplane mode on to off it will reboot and then get stuck in a boot cycle and the issue with flashing the phone and having to have signal before I can unlock the phone.
I am currently about to flash the PB31IMG to see if it will resolve the issues and then attempt to re-root. Any advice would be greatly appreciated as nothing has seemed to work so far. I would key you into what I have tried but I don't remember. Basically all the things to fix the 5 vibrate issue and general flashing woes.
Update:
Still no good. Flashed the PB31IMG via vol. down and power and it still did a reboot. Unlocked, got to the white HTC screen, and restarted. Booted the second time, got to the lockscreen, and rebooted before I could even slide down the unlock. Third reboot, got to activation this time, then it rebooted. Fourth reboot, go to activation, then rebooted. Fifth reboot, got to lockscreen, then rebooted before I could slide down.
So yeah. basically you can see what I am dealing with. And it is not fun. I have tried SD card in, SD card out. Just did its 6th reboot, didnt even get to the unlock screen before rebooting.
UPDATE 5/3:
Link to the video of whats happening. Nothing special and I recorded it with my Eris, but you'll at least see the timing of the reboots and what not. And ignore the breathing. lol. Just turn off the sound. Right after the video ended it did a 5 vibe. Pulled the battery and now it's just doing bootloops.
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
As for the flashing green light and 5 vibrates, I have so insight on this. It can happen if you press power and Vol+. I think it puts it in a safety mode and the only way to get out of it is a battery pull. So if you ever get stuck in a situation like this wait 10 minutes and try to turn it back on normally. If this doesn't work try booting into hboot (power + vol down) if this doesn't work power + vol up has worked for some people too.
There are cases however, where battery pulls don't help either. And no matter what the person tries the phone won't turn back on. This is a hardware problem and the only way to fix this is getting a new phone.
Dhessler5 said:
I have never had the random reboots before, at least not at the rate and consistency you have been. To me it sounds like something went wrong in the rooting process and I would recommend unrooting and rerooting.
snipped.
Click to expand...
Click to collapse
Would flashing the PB13IMG in Hboot unroot it or would I need to follow the guide? Just curious as I have never unrooted before, but I do know there is a guide for it.
The 5 vibrate thing is under control, it just has happened so I wanted to make it known.
And thanks for the info.
I would follow the guide for it, it would be the easiest and safest way and if you run into any problems they would be able to help you out and know exactly what to tell you. I have yet to unroot too so I don't want to tell you something without being 100% sure so I recommend the guide.
Alright, so it turns out flashing the image I flashed via Hboot is a way to unroot. :/ And that is when I got all the reboots in the beginning (the ones specifically posted, its not the first time). I am going to flash again once more to see if I can get a flawless start.
Still no good, flashed it again via Hboot and it restarted again. This timeat the white HTC screen after unlocking but before activation. :? Hm. Better than nothing, after the first reboot it fully loaded and everything is fine so far. Lets just home it doesn't slowly begin to degrade like last time.
A while ago while running the peanut stock ROM, every time my phone would reboot some apps would loose information (such as log in) and I was eventually unable to access the EPST settings.
If you rerooted your phone you could try to go into hboot and then recovery and "fix permissions." I am not sure if this will do any good but it couldn't hurt.
Also if it is unrooted you could try to bring it in to Verizon and see if they will give you a new phone or a restored one.
Make sure you have the stock Rom if you bring it back to Verizon also
sent from my dinc
sorry to hear this happened on an ebay phone... I've had it happen to 3 of mine... warranty took care of it since I'm still within my date. but after one year what do I do? luckily I bought my bros early upgrade meaning the Inc2 will suffice until april 2012
ohh yea my point sorry: I had an Eris before the Inc. //////had many problems after 5 they gave me the Inc if I agreed to drop my current one year contract and get a new two year paying the two year price PLUS got credited $199 for the Eris, and got to keep it, so I thought I made out until I realized this phone isn't gunna last two years. ANYWAY. I bought the Eris off Ebay, they gave me warranty after warranty no problem, best of luck
I have had my Inc for a year and have not had any issues. I would say you bought a bad model from someone on eBay. The 5vibration green light is indicative of a hardware failure and I have not seen anyone have a fix for it.
Sorry to say but I have seen no one, NO ONE recovery from the 5 vibs of death. From what I have gathered it is some sort of qualcomm download mode and I know of no way out. I have a feeling it is caused by pressing the vol + and vol - and power while trying to get into hboot.
This is just an uneducated guess. If your willing to part with the device I would love to get my hands on a 5 vibs phone.
Since it happens when the phone loses the signal, I'm wondering if it might be a radio issue. Which radio version is installed? It could be incompatible for your area/ROM/whatever.
Another thought: you said the screen was changed out. It is very possible that the kernal installed won't work for an lcd screen.
Anyway, more things to check and to test. Good luck!
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
ACD168 said:
mine always happened when i accidently pushed the vol + instead of vol -
twice it happened
Click to expand...
Click to collapse
That should be 3 vibs, not the 5.
they both won't work after wards thought as far as my testing.. had to get warranty replacements
I remember reading Chingy fixed 5 vib. It's not the end. I've seen other people fix it with ruu.
I couldnt fix mine when I got the 5 vibrations and I tried everything. My theory is that it has something to do with a messed up kernel flash since the baseband and kernel are apparently linked and I saw somewhere that flashing the same baseband 2x will cause this. It happened to me when I tried to flash a kernel twice (the first time it failed), some people could be getting this when flashing roms since they install new kernels also.
You can flash radios and kernals twice. There was one leaked radio in the past that caused problems from being flashed twice, but it isn't typical
Edit: I think chingy said something about trying a hundred different things, but eventually he got it to work by connecting to PC with battery removed. I could be wrong though because I read that post months ago. I know he got it working again by wiping system and starting fresh
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Trifurcated said:
I had the 5 vibs on mine a few weeks ago. It was an unfortunate event. I had the phone for almost a year, bought it new too. I had probably flashed at least a hundred times (thank you nighties for feeding my ROM flashing addiction) but I digress.
I was at work when it happened. If I remember right I believe I was re-installing a pandora apk when my phone did the vibs and led. As an fyi it is the same apk I am using now and it works fine. I initially thought oh well I'll fix it when I get home, surely someone has the answer...sadly not. I spent quite a while searching threads and google to no avail.
I was able to get it unrooted through hboot tho. I was also able to get it to boot when usb was connected to my PC, but as soon as I unplugged it would do the vibs again.
I don't like to admit defeat, but I had clearly lost. I called and got a replacement device sent (and an extended battery because the guy thought it could have been a battery issue, lucky me)
All I can do now is hope it doesn't happen again, but if it does hello warranty man. If someone does find a fix I would love to know about it for future reference.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think the 3, vibrate and 5 vibrate are connected because both times I had the 3 vib I had the same problems, would turn on when connected to usb then 3 vib and green flashing light... weird.
I woke up yesterday and the Galaxy Nexus (GSM) was not responding well. The touch input was lagging and it appeared to be under load. The phone was not hot. I took the battery out and put it back in. The phone however did not come back on. I have left the battery out over night and then put the battery back in when i woke up. Nothing. I have left it pluggeed into the computer for 3 hours unplugged then put then battery in. nothing. I have done numerous battery pulls and nothing.
I have read every possible post I can find about this but haven't recovered my phone. It was running AOKP milestone 3 and kernal build 162 (can't remember name sorry). CPU was not changed from stock settings (governor i believe). It will plug into computer with nop battery in and give me the OMAP4440 device listing for a brief second so I know its not dead.
Any help would be appreciate.
smee1216 said:
I woke up yesterday and the Galaxy Nexus (GSM) was not responding well. The touch input was lagging and it appeared to be under load. The phone was not hot. I took the battery out and put it back in. The phone however did not come back on. I have left the battery out over night and then put the battery back in when i woke up. Nothing. I have left it pluggeed into the computer for 3 hours unplugged then put then battery in. nothing. I have done numerous battery pulls and nothing.
I have read every possible post I can find about this but haven't recovered my phone. It was running AOKP milestone 3 and kernal build 162 (can't remember name sorry). CPU was not changed from stock settings (governor i believe). It will plug into computer with nop battery in and give me the OMAP4440 device listing for a brief second so I know its not dead.
Any help would be appreciate.
Click to expand...
Click to collapse
can you boot into fastboot?
Holding volume up+down and power?
no. no fast boot response. ONLY thing that tells me phone is seudo alive is the USB recognition for 1.5 seconds when plugged into computer without battery. This happened to me once before and leaving the battery out overnight got it back. No luck this time. Bought phone May 4th. First incident may 5th. Didnt want to bother with return because I love the phone. Now out of 14 day return policy. Can't send to Samsung due to root/etc
smee1216 said:
no. no fast boot response. ONLY thing that tells me phone is seudo alive is the USB recognition for 1.5 seconds when plugged into computer without battery. This happened to me once before and leaving the battery out overnight got it back. No luck this time. Bought phone May 4th. First incident may 5th. Didnt want to bother with return because I love the phone. Now out of 14 day return policy. Can't send to Samsung due to root/etc
Click to expand...
Click to collapse
hmm..
Try letting it sit another night and try again ,
wish i could help more sorry..
Did you pull the sim card as well? If not try that along with the battery and try again
Sent from my Transformer Prime TF201
yeah i tried that as well. i just said screw it today. called samsung got a shipping label. the warranty process could turn out bad/interesting. if it does i'll just let em keep the phone. been more problems since the day i got than any phone ive had. not flaming this gnex forum by any means so dont launch into a war on me. I miss my Galaxy S2. I work at an AT&T COR store maybe i'll poke around for when our GS3 is coming. I'll keep yall posted on what sammy says. If anyone reads this that has had a success story with recovering their phone from this problem let me know though please.
Sounds to me that your battery is flat and it doesn't charge. Do you have a spare one you can try (friend or work)?
Sent from my Galaxy Nexus using Tapatalk 2
Yeah I tried my friends Verizon nexus. Nada there too lol
Me too
smee1216 said:
yeah i tried that as well. i just said screw it today. called samsung got a shipping label. the warranty process could turn out bad/interesting. if it does i'll just let em keep the phone. been more problems since the day i got than any phone ive had. not flaming this gnex forum by any means so dont launch into a war on me. I miss my Galaxy S2. I work at an AT&T COR store maybe i'll poke around for when our GS3 is coming. I'll keep yall posted on what sammy says. If anyone reads this that has had a success story with recovering their phone from this problem let me know though please.
Click to expand...
Click to collapse
My Gnex happen excetly same after I updated CMW touch zip by rom manager! No response on power button. Power + volume +- button! Garrrrrrr!
That 1.5 second you've mentioned when you connected to the computer... did it say? OMAP or something like that? If so, you have a good chance of "reviving" the phone. Search up for OMAP flash.
This excactly the thread you need
Good luck buddy
http://forum.xda-developers.com/showthread.php?p=28486488
Sent from my Galaxy Nexus using Tapatalk 2
Helpful
This post helped. My GSM GN suddenly went black in the middle of an installation. Tried the tip with battery . No go
Saw the same problem at iFixit forums.
The tip was same. The trick was to use the charger instead of the USB port.
Worked well and my GN is back again.
Okay before i get bashed yes I have searched the threds and yes I found the issue but the solution did not apply to my case, So I do appoligize if this for any reason is not the right place and will be happy with any mod that feels necessary to move my thread
That being said, I came across a t-mobile galaxy S3 t-999 the phone is not rooted, has not had any physical damage and does not have water damage and no update was attempted, the occurrence was random with nothing being done, just shut off and wouldn't turn back on. The battery has been swapped with another S3 to confirm there is no battery issue. The cord has also been swapped.
Now the problem
The phone turns off after a couple seconds and does not boot
My initial thought was to first try a factory reset and if that didn't work to re-flash stock with odin.
Well recovery also turns on for 2 seconds and shuts right off.
Download mode? Yupp you got it same thing
cant reflash with odin because it won't stay in download mode
The only thing i seemed to find thats remotely close to this is a stuck power button and the solution seems to be slamming the phone on the table
However this is NOT the problem in my case
The slam method has been attempted as well as the remvoval of the power button, Plus after each time it shuts off It will NOT turn back on until I remove the battery which is when i get that glorious 2 seconds followed by it turning right off. Thats why i made a new post rather then posting this question there, but if I shouldn't have Im sorry The mod can remove it and i will be happy to repost it there.
If anyone can help me please do, because at this point my face looks like thank you.
majicmazo said:
Okay before i get bashed yes I have searched the threds and yes I found the issue but the solution did not apply to my case, So I do appoligize if this for any reason is not the right place and will be happy with any mod that feels necessary to move my thread
That being said, I came across a t-mobile galaxy S3 t-999 the phone is not rooted, has not had any physical damage and does not have water damage and no update was attempted, the occurrence was random with nothing being done, just shut off and wouldn't turn back on. The battery has been swapped with another S3 to confirm there is no battery issue. The cord has also been swapped.
Now the problem
The phone turns off after a couple seconds and does not boot
My initial thought was to first try a factory reset and if that didn't work to re-flash stock with odin.
Well recovery also turns on for 2 seconds and shuts right off.
Download mode? Yupp you got it same thing
cant reflash with odin because it won't stay in download mode
The only thing i seemed to find thats remotely close to this is a stuck power button and the solution seems to be slamming the phone on the table
However this is NOT the problem in my case
The slam method has been attempted as well as the remvoval of the power button, Plus after each time it shuts off It will NOT turn back on until I remove the battery which is when i get that glorious 2 seconds followed by it turning right off. Thats why i made a new post rather then posting this question there, but if I shouldn't have Im sorry The mod can remove it and i will be happy to repost it there.
If anyone can help me please do, because at this point my face looks like thank you.
Click to expand...
Click to collapse
I think you already know the answer. Seems to me that you've done everything possible. Were you on 4.1.2?
Can you call T-Mo or Samsung and Check Warranty Coverage on the IMEI ? They may ask for Serial Number instead.
Not actually my device
Aerowinder said:
I think you already know the answer. Seems to me that you've done everything possible. Were you on 4.1.2?
Click to expand...
Click to collapse
Perseus71 said:
Can you call T-Mo or Samsung and Check Warranty Coverage on the IMEI ? They may ask for Serial Number instead.
Click to expand...
Click to collapse
Yea thats what i was afraid of, I actually don't know the version it was on prior, to be honest this isn't my device I actually run a small time craigslist base business generally rooting peoples phones and installing roms and fixing softbricks, someone asked me if I can help them and i thought it would be a simple softbrick issue until I actually got a hold of the phone and saw this issue now i think its hardware problem but i thought id ask my good friends at xda before completely giving up
[
So my Tmobile S2 will go to logo loading screen then just cutboff and viberate every 2-3 seconds. Every few times it will fully load and go to the android guy making the phone turning on noise but then it will make a "errrr" noice and cut off. Sometimes it will actually cut all the way on but then cut of after maybe 1-3 minutes. i have gotten it to stay on long enough to factory reset it from the settings and it restarted just as it should and stayed on maybe 2 more minutes then what do you know?, cut off and viberated. i can not get it into recovery or download mode and when it does turn on it will hook up to kies and to my laptop but if it cuts off it disconnects. i have two batteries for it so thats not it right? i also had the screen and the lcd and the camera replaced about three weeks before this. i had the power button replaced yesterday. they guy that done it said he deleted my ROM and downloaded a new one and it didnt work, but when i got it on all my downloaded apps was on there still and in the same place on my home page! plus my password was still on there and the guy did not know it!! so he lied about deleting it right? it does charge when plugged up though it wont come on and it viberates still. i did leave it on charge all night and when i turned it on this morning it fully loaded three times in a role. also i havr not downloaded or updated anything on it, its all stock. and i have not unlocked, jailbroken it. and yes i have tried the volume up+power+home, volume down+power+home, volume up+ power, and volume down + power. nothing! what do i do now?????? Please help me!!!!!!!!! thank you!
Hi, this is not the forum for the Samsung galaxy s2. This is the forum for the htc wildfire, two very different phones pal. You should post this thread to the Samsung galaxy s2 device forum where people who have the device can help you. If you user the report function in the top right hand corner of your post ( its a ! ) and report the thread, saying you posted in the worng forum and can it be moved please. Good luck pal and I hope the S2 guys and girls can help
Sent from my HTC Sensation using Tapatalk
Can someone *please* help me fix this Note 4??
A while back I flashed Emotion Kernel to gain root and the phone worked fine for a few months then just died on me completely.
It doesn't turn on at all, I can not get into safe mode, bootloader, etc. I pulled the battery & held the power button, re-inserted battery and got nothing...Tried different Samsung stock/fast chargers-nothing....I tried everything I could find with no results.
If anybody has had this problem and fixed the phone please let me know. Thanks.
Bad battery, maybe
broad_st_bully said:
Can someone *please* help me fix this Note 4??
A while back I flashed Emotion Kernel to gain root and the phone worked fine for a few months then just died on me completely.
It doesn't turn on at all, I can not get into safe mode, bootloader, etc. I pulled the battery & held the power button, re-inserted battery and got nothing...Tried different Samsung stock/fast chargers-nothing....I tried everything I could find with no results.
If anybody has had this problem and fixed the phone please let me know. Thanks.
Click to expand...
Click to collapse
Could be bad battery or hard bricked.
Try new battery or if that didn't help then have a look at link below to fix hard bricked note 4.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Note 4 batteries are dying for lots of people anywhere from 18 months to just over 2 years, and the symptom is often fail to boot, boot loops, etc. As piggynuts said in another thread, it's not logical, but it's true.
It happened to me, and when I replaced the battery, everything was fine. I've read comments on other sites where it has happened to multiple people, and they solved it by replacing the battery.