Develop Bugs

5 vibration diagnostic code

So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App

I have it too. Can you boot your phone up like normal after a little while? Everyone else on this forum who gets this can't do jack with their phone. I can boot up fine afterwards, it's just extremely annoying.
It's a code for some kind of hardware failure and they all had to get a new phone. I've been told a RUU may fix everything, but that's a semi-long process for someone as ADD as me to go through. You could try it though. And if you do, shoot me a PM with the results.

Yeah that's exactly what mine does, It'll boot right away and I usually only run into the issue when I'm playing a game for more than five minutes or using my phone in a warm environment. It seems to hit 100° F and then stops itself from overheating.
I was really hoping to not have to Ruu, because its such a process and I don't want to lose the gingerbread keyboard. Maybe someone else will chime in with another idea.
Sent from my ADR6300 using XDA Premium App

So far you and I are the only 2 I know about in the internet who can still boot up like normal afterwards.
I wiped dalvik last night and I haven't had the issue today, you might give that a try. It can't hurt.
-CM7 ADR6300

Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App

This just in, rebooted while playing star wars podracing on n64oid.
I think it is a heat issue, cuz my phone is always pretty warm when it happens.
-CM7 ADR6300

I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App

Also had it on OMFGB, though not as frequently.
Also, today I've noticed my haptic feedback has been... varied in vibration intensity.
-CM7 ADR6300

thisisshep said:
Ill try that today. I initially thought it was the battery overheating but it did it with the stock 1300 and its doing it with the evo battery I'm using now. Ill finish setting up adb and try the ruu next week when I get time.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I have an Ruu that you just place on the root of your SD and flash through hboot no adb needed if you want it pm me..... and ill give you the file and instructions
Sent from my Incredible using XDA App

Well I broke down tried the RUU and that went through fine but I cant seem to replicate the error with stock. I tried gaming for about 20 minutes and it didnt do it yet, normally it does it after like 5

Good to know.
Have you gone back to CM7 and seen if it helps out there?
-CM7 ADR6300

No I havent tried rerooting yet and reinstalling cm7 It keeps doing it only now it gets stuck in a boot loop instead of doing the five vibration thing then it boot loops about 3-5 times till it cools itself down then restarts normally like nothing ever happened
I already talked to verizon and the new ones in the mail so theres really no sense messing with it anymore now i just need to decide if i want to root the next phone or not

That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App

thisisshep said:
So lately I've been getting the 5 vibration code and I've been searching around here and on other forums and no one seems to know what causes it. Has anyone else that's been experiencing this noticed that it seems to go away after a battery pull and then letting the phone cool down? I'm rooted with unrevoked running cm7 rc2 with Chad's newest kernel right now and tried running cm7 with the included kernel and experienced the same issue.
My main concern is whether to ruu and whether thats going to fix it or if it's simply a hardware issue
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
What version of ClockWorkMod are you running? I read some problems with flashing CM7 caused by CWM 3.0.0.8 that was fixed by going to 3.0.0.7

dpwhitty11 said:
That's what's happening to mine now, too... I also couldn't root it? Unrevoked kept failing. Oh well. I'm selling it and migrating to a Thunderbolt.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App

pete_kowalski83 said:
Nice, I hope the person who buys it informed.....id be f ing pissed
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Yeah, you've got that right !!!!

When it happened to me I couldn't do a damn thing except get into clockwork Mod, which didn't help because I couldn't access the sdcard. I called up verizon and got a new one. For the two of you that actually have a working phone after this is your phone S-ON or S-OFF?
thisisshep said:
It seems to hit 100° F and then stops itself from overheating.
Click to expand...
Click to collapse
100F is nothing for these processors. Think about it, your body is 98F and a processor is meant to handle a lot more heat than your body. I know the TI OMAP in the original droid had a failure point of 220F.
silverxbv2 said:
I've read about this in a lot of forums lately. But it seems like it only comes up with cm7. You guys sure its not rom related?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Nope, not rom related since it happened to me when I was using Incredibly Re-Engineered v2.3 and flashing a custom kernel when it happened.

Mine remained rooted ans s-off throughout the issue.
I unrooted and applied s-on and reverted to the November RUU and it fixed everything.
Rerooted and reapplied s-off a few hours ago and flashed Virtuous. No more CM7 for me. That's when I started having issues.

Mine does the same thing. Vibrates once, turns off, vibrates 5 times and the LED blinks green. I think mine is related to an overheating issue. Mine reboots almost always when im plugged into the car charger, talking on the phone over bluetooth on my way to work. About a 35-45 minute commute. Even when plugged in at home, and while messing with the settings as well. The only thing that is almost always the same is the screen brightness. Thats when it gets super warm and then turns off. I'll try it out with the screen brightness settings to lower then usual. But when I let it cool off, like I do in the car in front of the A/C vent for about 30 seconds,, with the battery out of the device, it comes right back on no problems.

Mine was rooted and s off. I believe I installed cm7 using clockwork 3.0.0.7 then upgraded to 8 and still had the issue. I know 100°f is nothing for a processor but it seemed to have issues as soon as it got around 110 then if you let it sit it works again so that's what led me to thinking it was a heat issue even though it doesn't make much sense
Sent from my ADR6300 using XDA Premium App

EF02 and overheating.....

I am using [Odin]Stock EF02 with CWM 3.1.0.1/Root/Busybox 1.18.4 and also tried EF02Plus as well. I seem to have an issue only with EF02 with overheating. I remember it was an issue with the orginial leak of GB but now my phone will say it refuses to charge when it gets too hot. I did a check and my temp reading is at 107F. Now it is about low 90's outside today and we dont have AC as we do not want to kill the planet. Is anyone else having over heating issues? I have also tried both modems ef02 and ef10... I wounder is modem ec03 may solve this... whats your thoughts?

htc_joe said:
I am using [Odin]Stock EF02 with CWM 3.1.0.1/Root/Busybox 1.18.4 and also tried EF02Plus as well. I seem to have an issue only with EF02 with overheating. I remember it was an issue with the orginial leak of GB but now my phone will say it refuses to charge when it gets too hot. I did a check and my temp reading is at 107F. Now it is about low 90's outside today and we dont have AC as we do not want to kill the planet. Is anyone else having over heating issues? I have also tried both modems ef02 and ef10... I wounder is modem ec03 may solve this... whats your thoughts?
Click to expand...
Click to collapse
I used to have that problem too... it seems to be better now... im running marcusiants acs unnamed rom rc10 with the ee03 modem... it has seemed to fix my heating problems... hope I helped you
Edit: also im using maddogins lockscreen mod... just incase that would effect it.
Sent from my SPH-D700 using XDA App

Yes, EE03 runs much cooler. I tried them all.
Sent from my SPH-D700 using XDA App

Lol im getting super overheating problems with stock efo2+eflo modem
Im think of going back to srf once 1.3 comes out
Sent from my SPH-D700 using XDA Premium App

gtuansdiamm said:
Lol im getting super overheating problems with stock efo2+eflo modem
Im think of going back to srf once 1.3 comes out
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Try marcusiants rom on the acs site and try the ee03 modem.. that should help.
Sent from my SPH-D700 using XDA App

I saw this problem go away when I switched from EF02Plus and went to decadence EF02 deodexed version.

I have had this problem on every ROM I have tried since the release of froyo.. On froyo it would shut down because of the temps and cause all sorts of corruption problems. At least on gingerbread, I am not seeing the corruption, but the overheat lockup is still there and requires a battery pull... I have posted in every thread about this issue and have not seen a real fix to the solution. And I am not sure if it is just certain phones or what as it is not a huge widespread thing, but people do have it... I may try one of the other two roms listed later this week to see if I can sort out the problem...

lilmexx said:
I have had this problem on every ROM I have tried since the release of froyo.. On froyo it would shut down because of the temps and cause all sorts of corruption problems. At least on gingerbread, I am not seeing the corruption, but the overheat lockup is still there and requires a battery pull... I have posted in every thread about this issue and have not seen a real fix to the solution. And I am not sure if it is just certain phones or what as it is not a huge widespread thing, but people do have it... I may try one of the other two roms listed later this week to see if I can sort out the problem...
Click to expand...
Click to collapse
That sounds like a hardware issue if you have it on froyo too...
Sent from my SPH-D700 using XDA App

I think if I charge via usb it stays cooler since lower amp of 500mha
Sent from my SPH-D700 using XDA Premium App

Ran in the big sprint store that has the tech center in it, just to see what they said about the problem.. They ran some tests and an hour later, they came back and said the battery was def on the bad side of things and gave me a new one. So far my battery life has been crazy good and no heat shut downs.. I havent really tested it fully yet, but hopefully my issues were purely battery..

Sent from my SPH-D700 using XDA App

I'm running on ef02 stocked with root and I also use a extended battery with 3500mah capacity ,, been using all this ever since samfirmware released it but so far not one over heat problem that I have seen
Sent from my SPH-D700 using XDA App

lilmexx said:
Ran in the big sprint store that has the tech center in it, just to see what they said about the problem.. They ran some tests and an hour later, they came back and said the battery was def on the bad side of things and gave me a new one. So far my battery life has been crazy good and no heat shut downs.. I havent really tested it fully yet, but hopefully my issues were purely battery..
Click to expand...
Click to collapse
Good to hear you didn't hae t get your whole phone replaced.
Now you should try rc10... batteries great after calibration with ee03 modem... right now I'm at 94% and my phones been off the charger for 3.5 hours and the screens been on 30 minutes... I got 3.5 hours with screen on yesterday, and that as urin the calibration process, so today it I'll probly be better .
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Yes, EE03 runs much cooler. I tried them all.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I agree. I use the EE03 modem on the EF02 rom and it work better in my opinion.

Replaced battery did not change anything... On the drive home, talking, same thing happened.. Granted is was like 100 degrees out and I have no ac in my truck... But yeah still shut down!! I guess I am gonna try unnamed and ee03. I guess I have to odin to ee03 correct??

lilmexx said:
Replaced battery did not change anything... On the drive home, talking, same thing happened.. Granted is was like 100 degrees out and I have no ac in my truck... But yeah still shut down!! I guess I am gonna try unnamed and ee03. I guess I have to odin to ee03 correct??
Click to expand...
Click to collapse
That sucks... and yeah print it it take about like a minute to set everything up.
Sent from my SPH-D700 using XDA App

lilmexx said:
Replaced battery did not change anything... On the drive home, talking, same thing happened.. Granted is was like 100 degrees out and I have no ac in my truck... But yeah still shut down!! I guess I am gonna try unnamed and ee03. I guess I have to odin to ee03 correct??
Click to expand...
Click to collapse
Everything is in my sig plus newest version should fix any issues you have

[Q] Screen Unresponsive

I have had my phone sense Nov last year and just updated to the OTA 2.3 Android a few months ago. Sense the update (and to a lesser degree ever sense i got my phone) the screen has becoming more and more unresponsive. It started as just the Lock Screen would do nothing for the first few seconds and then everything would be fine. I would have it think i was long pressing spots sometimes and apps like Facebook and Tweetcaster would super scroll and speed up or down for a long time. Over the past couple weeks it has become so bad that my phone would stop responding to the touch screen within a couple seconds of awakening it. I have resorted to using the arrow keys like its an old Sidekick. Which works, just not really well. I am planning on calling sprint and getting it insurance-replaced because i think it might be a hardware problem. But before doing that I have put it back to stock ROM using the program that Samsung put out as their replacement to Odin (which i have used many times sense after about a month i started rooting my phone and screwing around with it.) The recent Apps i have been using which i think could be responsible are Mr. Number as it blocks calls and Cloudskipper Media Player sense it overrides the lock screen and maybe one of those two is messing with something.
Has anyone else had this problem or something similar, any ideas on how to fix it if it comes up again?

Ok, u said that u have ur phone rooted since u updated it to gb? Or what? Trying to clarify first before we contine.
Sent from my SPH-D700 using xda premium

Sorry, no it is currently not rooted. It was, but i had to restore it to factory because while it was rooted Clockwork wasnt liking the OTA update. Actually Clockwork wasnt seeing my SD card at all at that point. So I used the Odin replacement to reset, then the update took. Sense then i havent re-rooted it.

Ok. Well there is an updated version of cwm, and there are a few steps that u need to do to reroot with gb
Sent from my SPH-D700 using xda premium

androidmaster1 said:
Ok. Well there is an updated version of cwm, and there are a few steps that u need to do to reroot with gb
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I was having problems updating TO gb while rooted. But thats not the problem.

teccan9nja said:
I was having problems updating TO gb while rooted. But thats not the problem.
Click to expand...
Click to collapse
Yeah you can't do the official gb update while rooted... if you need help rooting now there is a sticky in the developement section on it...
Sent from my SPH-D700 using Tapatalk

teccan9nja said:
I was having problems updating TO gb while rooted. But thats not the problem.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=kwFRzzIqouE
complete steps on how to root epic on gb

androidmaster1 said:
http://www.youtube.com/watch?v=kwFRzzIqouE
complete steps on how to root epic on gb
Click to expand...
Click to collapse
Or you can be lazy and let me do it for you in like 5 minutes
Sent From My Cyan Samurai

Speaker not working cm9 with shadow 5 kernel

My phone all of a sudden stopped ringing when I got calls, text, etc.... noticed it while trying to watch a video...no sound. Then one day it rang for an IM. So I knw now the speaker isn't busted like I originally thought. Its worked fine until now. Anybody have any input? Feel free 2 pm me
Sent from my SPH-D700 using XDA

Must be something in the water. Had same thing. Try plugging in a wired headset while watching a youtube, then unplug. This worked for me for 2 hours then nada. Reflashed rom and even reformated to mtd but no difference. Something is hosed in nvram. Replaced unit under tep as I also had cracked screen so didn't get too much into.
Sent from my CleanGB/MTD Epic

I believe I still have the cm9 file on my sd. Wouldn't I need to reflash my kernel? To my knowledge handles the sound etc.
Sent from my SPH-D700 using XDA

Or maybe flash shadow 4 again.
Sent from my SPH-D700 using XDA

None of that worked for me. If you figure it out, please post a solution cause there are quite a few threads on the issue.
Sent from my CleanGB/MTD Epic

Odin back to stock EL30 and see if you still have issue. If you do it is a hardware issue. that is what happened to my wife. The repair center fixed it for free because I have the insurance.
Edit:
all files can be found here:
http://forum.xda-developers.com/showthread.php?t=1052813

What all will that do? I assume I will loose root and cm9?
Sent from my SPH-D700 using XDA

It assures that you do not have corrupted data. Yes you will have to root and then flash CM9. Do not restore anything. See if your issue is gone, then load apps and set up your phone.
Sent from my PantechP4100 using xda premium

My phone was rooted remotely. I used to have odin on an sd card. I know I would understand it if I seen it done. Originally I just wanted root on stock rom and kernel but he asked me if I wanted gb or ics so naturally I wanted 2 try out ics. He set it up with shadow 4 kernel then I flashed shadow 5 on my own. I dnt understand y it would work fine for like a month or 2 then nothing.
Sent from my SPH-D700 using XDA

debage39 said:
My phone was rooted remotely. I used to have odin on an sd card. I know I would understand it if I seen it done. Originally I just wanted root on stock rom and kernel but he asked me if I wanted gb or ics so naturally I wanted 2 try out ics. He set it up with shadow 4 kernel then I flashed shadow 5 on my own. I dnt understand y it would work fine for like a month or 2 then nothing.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
Lulz =] I'm sorry.. you should have asked me to help ya out... add me on gtalk [email protected] if you ever need anything. Or PM me.
THE most ironic thing is someone else I rooted I suggested the shadow kernel for has had this same issue.... he even flashed back wiping data but to no avail tomorrow ill have to odin y'all back to stock and re root ya and give you the proper cm9's and kernels and you should be good to go if of course the speaker isn't out. =]
Sent from my SPH-D700 using xda premium

speaker still not working
I tried reflashing cm9 and shadow 5, then tried cm9 and included stock kernel alone with gapps, then tried shadow 6. no sound on all. but doesnt explain it working for a bit then going back out. idk

Mine works and I have always used shadow. Shadow has no speaker mods other than voodoo. Have you blown it with volume+?
Sent from my SPH-D700 using Tapatalk

You will have to Odin to get it working then reinstall everything without restoring data.
Sent from my PantechP4100 using xda premium

No I've never messed with the audio settings.
Sent from my SPH-D700 using XDA

Marcusant and kenny, is there a way of accessing any of the nvram settings for audio, like telling it to use speaker vs audio jack so these can be reset somehow? I recently went through similar situation. Plugged wired headset in and out while watching youtube. This made my speakers come alive again for short time so they weren't blown. I factory reset, flashed stock, all ota's, rooted and went mtd cleangb. None of this brought back speakers. Something was telling them not to come on. Got new device so moot point 4 me now...
Epic powered by CleanGB/MTD 1.1.2

Sounds more like it was the hardware jack itself that was bad and getting stuck on. Might have been junk in the jack.
Sent from my SPH-D700 using xda premium

Hey goron, ill b home all day if wanna try 2 tackle this problem with the speaker. I have faith. Lol let me knw if ur free anytime 2day. I would say email me. Ill probly get it faster. Thanx for all ur help!
Sent from my SPH-D700 using XDA

Big Goron said:
Lulz =] I'm sorry.. you should have asked me to help ya out... add me on gtalk [email protected] if you ever need anything. Or PM me.
THE most ironic thing is someone else I rooted I suggested the shadow kernel for has had this same issue.... he even flashed back wiping data but to no avail tomorrow ill have to odin y'all back to stock and re root ya and give you the proper cm9's and kernels and you should be good to go if of course the speaker isn't out. =]
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Odin him back to stock to see if he still has the problem I suspect he will. My wife had this issue when on cm no custom kernel it was a hardware issue. I am not saying CM caused it **** happens and her hardware failed.
One way to tell if it is hardware is does it vibrate? If it doesn't vibrate then it is hardware if it does then it might be a setup issue.

Yea it vibrates. Phone sitting on the table with vibrate.....kinda like a ringtone right? Sad but true lol
Sent from my SPH-D700 using XDA

debage39 said:
Yea it vibrates. Phone sitting on the table with vibrate.....kinda like a ringtone right? Sad but true lol
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
Then it might not be hardware. When my wife's speaker stopped working it wouldn't even vibrate. When I spoke with the person at Sprint that fixed it he said it is the same unit. Of course I am not sure if it did vibrate at first because the wife didn't tell me for like 3 weeks that it was happening.

Screen is black but phone works?

i was out getting some pretty damn good ice cream tonight phone was working fine.. go to check time and black screen... lights for back and menu came up but screen is black... also after batt pull found that its still black but phone boots up and you can unlock it.. i think its just a bad phone but could anyone help me find out whats going on?
[ROM][UCALH1]Triune II[AllianceRom][81512]
is what i'm using... but yeah kinda sucks. the only thing great about working for AT&t is i can get a new one fast but was hoping it was a rom problem.. any idea what i can do?

Could be some loose connection with your digitizer call phone support or repair place.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

tacotino said:
[ROM][UCALH1]Triune II[AllianceRom][81512]
is what i'm using... but yeah kinda sucks. the only thing great about working for AT&t is i can get a new one fast but was hoping it was a rom problem.. any idea what i can do?
Click to expand...
Click to collapse
I didn't have this problem after I installed Triune II, but if you suspect the ROM is related, do a backup and install a different ROM to see if that resolves the problem..... just a thought and takes less than 5-10 min.

What does the screen look like in download mode or in CWM?
Sent from my SGH-I747 using xda premium

OK Found out that the screen is defective, no problem! Ferrying new phone Tuesday
Sent from my MB886 using xda premium

RiPpeR_dUdE said:
I didn't have this problem after I installed Triune II, but if you suspect the ROM is related, do a backup and install a different ROM to see if that resolves the problem..... just a thought and takes less than 5-10 min.
Click to expand...
Click to collapse
How can he back up what he cant see?
Sent from my SAMSUNG-SGH-I747 using xda premium

So i need help, I'm sending in my phone for warranty.. Do you think they'll fix the screen then see i have a custom ROM or wipe it the fix the screen... Or how do i put it to stock and reset the counter?
Sent from my MB886 using xda premium