Develop Bugs

[Q] Reboots, not able to boot, 5 vibrates.

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.

Can I still return this?

I just got my E4GT a couple weeks ago...all of a sudden, it started going to hell. The touchscreen stopped working pretty much completely, it won't charge and won't acknowledge the USB cable at all, so I can't connect to Odin or flash a stock firmware, or use a usb jig. The screen flashes transparent red/blue, i cant use the touchscreen while charging...
It's a hardware issue, I know but can I still take it in? What are the chances they'll say I can't return it because I rooted it? All of the employees at my sprint store seem pretty clueless...is it worth a try just to see if they can fix/replace it?
I really don't want to pay 100 bucks for a new phone just because I rooted it -__-
Also, my parents are REALLY, REALLY pissed.
Thanks, for the love of god, help me.
I have to go on a trip in 3 days and I NEED my phone.

br//0k3/n said:
I just got my E4GT a couple weeks ago...all of a sudden, it started going to hell. The touchscreen stopped working pretty much completely, it won't charge and won't acknowledge the USB cable at all, so I can't connect to Odin or flash a stock firmware, or use a usb jig. The screen flashes transparent red/blue, i cant use the touchscreen while charging...
It's a hardware issue, I know but can I still take it in? What are the chances they'll say I can't return it because I rooted it? All of the employees at my sprint store seem pretty clueless...is it worth a try just to see if they can fix/replace it?
I really don't want to pay 100 bucks for a new phone just because I rooted it -__-
Also, my parents are REALLY, REALLY pissed.
Thanks, for the love of god, help me.
I have to go on a trip in 3 days and I NEED my phone.
Click to expand...
Click to collapse
Most employees wont know it's been rooted. Especially if they can't get into it like you're saying. If you can get into it, go into settings>Privacy>Factory Reset. This will erase mostly everything on the phone.
You should tell them it just stopped working and ask for an exchange. To me, it sounds like a hardware problem though.

Well...what I'm worried about is that they'll put a different battery in, see that it still turns on, see the custom boot screen/yellow triangle of doom, and tell me to get the **** out. >____<
Should I flash a broken ZIP onto it just to be sure? I have a half-downloaded starburst ROM on my sd card.
If it matters by the wy, I'm running calkulin's rom 1.5, but this started happening on starburst 1.9.8r. I flashed calkulin's to see if it fixed the problem, but nope. :/
Is there a stock ROM I could flash through CWM and not Odin?

br//0k3/n said:
Well...what I'm worried about is that they'll put a different battery in, see that it still turns on, see the custom boot screen/yellow triangle of doom, and tell me to get the **** out. >____<
Should I flash a broken ZIP onto it just to be sure? I have a half-downloaded starburst ROM on my sd card.
If it matters by the wy, I'm running calkulin's rom 1.5, but this started happening on starburst 1.9.8r. I flashed calkulin's to see if it fixed the problem, but nope. :/
Is there a stock ROM I could flash through CWM and not Odin?
Click to expand...
Click to collapse
Sprint Repair M&P states that rooted devices are to be triaged by normal process. Part of that triage process is to unroot the device if the problem is suspected to be caused by root.
Worst comes to worst, they unroot the device and you get an exchange.

I also got the red transparent screen once a few days ago. I am experiencing weird other problems now
Sent from my SPH-D710 using XDA App

http://www.forums.acsyndicate.net/s...-15-11-Closer-to-Real-Stock?p=12393#post12393
Sent from my SPH-D710 using xda premium

Have you tried using different usb cables? Just throwing it out there you would be surprised what a bad cable can do. Same with the power block you plug in the wall

They won't care about root. Just play dumb if they call you out on it (in other words say you didn't know root is bad - but only if they ask). As far as battery, put the oem battery back in, never use a non oem battery no matter what anyone tells you, I am an engineer who designs these things for a living, correct power supplies are crucial. Finally, they will probably ship you a refurb if you are out of your return period, not in time for your trip. It is just the way it is.
Sent from my SPH-D710 using Tapatalk

My phone works fine. But I did get a transparent blue screen once. Any idea what that means?
Sent from my SPH-D710 using Tapatalk

[Q] How to full brick my phone or repair it

Hey guys,
I kind of messed up when i tried to flash a new rom earlier today. Now i can't access CMW and if I try to go to download mode it just shut down after 3-5 seconds of being there, Just before it shuts down a blue screen flashes. The problem is i thought of sending it back for the warranty but i had the Koodo rom so after the "Samsung galaxy ...t989d" the koodo screen appears an then it shuts down.
So I really don't think there is a way to fix this, as I've tried with ODIN but the download mode isn't staying. So is there a way I can get rid of the Koodo screen??

oscarito619 said:
Hey guys,
I kind of messed up when i tried to flash a new rom earlier today. Now i can't access CMW and if I try to go to download mode it just shut down after 3-5 seconds of being there, Just before it shuts down a blue screen flashes. The problem is i thought of sending it back for the warranty but i had the Koodo rom so after the "Samsung galaxy ...t989d" the koodo screen appears an then it shuts down.
So I really don't think there is a way to fix this, as I've tried with ODIN but the download mode isn't staying. So is there a way I can get rid of the Koodo screen??
Click to expand...
Click to collapse
Learn and live? You understood the risks when doing this. Don't force your mistakes on everyone else by sending in a unit YOU broke. (By forcing mistakes, I mean T-mo, Samsung will have to eat the cost of you messing up your phone and they just pass that along to everyone else.
Try pulling the battery wait a minute, then put it back and boot to download mode with the USB cable connected to the PC with ODIN already up and running. Try to be quick and get ODIN start before the phone cuts off.
I've had a few instances where a flash was bad and it took some crack timing to get everything to work right and save my butt.

gallaxxeess said:
Learn and live? You understood the risks when doing this. Don't force your mistakes on everyone else by sending in a unit YOU broke. (By forcing mistakes, I mean T-mo, Samsung will have to eat the cost of you messing up your phone and they just pass that along to everyone else.
Try pulling the battery wait a minute, then put it back and boot to download mode with the USB cable connected to the PC with ODIN already up and running. Try to be quick and get ODIN start before the phone cuts off.
I've had a few instances where a flash was bad and it took some crack timing to get everything to work right and save my butt.
Click to expand...
Click to collapse
Yeah well people here are advised to send their bricked device to Samsung all the time because Samsung won't know the difference... I don't see how that is any different from what this guy is proposing...
Sent from my SGH-T989 using xda premium

It sounds like you have a stuck or broken power button. Try doing what the guy above said to do and after you return it to stock, send it to Samsung for a replacement.

If you have insurance on your phone just tell them you lost it, but you would have to pay the copay
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

[Q] Bricked GS3, phone is powered off and unresponsive

Think I just borked by AT&T Galaxy S3, and yes it is completely my fault. This is probably a dead end, buy I figured I'd ask as a last resort.
I've got a lot of experience rooting and flashing ROMS and flashing custom recoveries and was rushing a proceedure when the problem occurred. I was trying to flash the CWM touch recovery using the instructions here: http://forum.xda-developers.com/showthread.php?t=1739426
I tried to do all this through my phone using Terminal Emulator and typed in the portion "mmcblk0p18" one letter off from what I should have (I think I typed in "mmcblk0p08" ... sick sinking feeling my stomach right now). The code went through as I started to power down the phone as I was looking at the code I wrote. Noticed the mispelled line of code right as the screen was powering off. Now my phone is completely unresponsive, after I rebooted. The phone does not power on, cannot boot into recovery mode, and worst of all seemingly will not boot into download mode. I've had boot loops before and am familiar with how to traditionally boot into Download mode via POWER + Vol Down + Home Button and used Odin to flash a fix.
Are there any other options, short of taking it to a repair shop, that I can try? I'm guessing it's completely bricked, but I just wanted to see if there were any options I was missing that are worth trying.
About to start calling repair shops to see if they can take a look at it as well.

Warranty replacement. Just say you don't know why it won't turn on. I did this after dropping my rooted phone and they asked no questions.

On the phone now, I'll let you know if they're able to assist with troubleshooting or otherwise.

I did the same thing.... I had insurance through att reported the phone lost... I repeat lost not stolen.. Got a replacement in 2 days brand new white and used that to pull the stock rom and flash it to my old phone. The then turned around and sold the replacement phone
Sent from my SGH-I747M using xda premium

That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

Mphill46 said:
That doesn't make sense why the phone won't even turn on, were you trying to flash on a low battery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I agree that it doesn't make sense. It's behaving almost as if the battery is just flat out dead. I have a spare battery, but when I tried that one it made no difference. I plugged the phone into a couple of different chargers while the AT&T rep was helping me troubleshoot and the charging light wouldn't turn on. The phone was not responding to anything at all, no matter what we tried.
They declared it hardware failure and are sending a replacement, as part of the original warranty. It did not have any physical damage, scratches, no water damage, etc.
Let this be a lesson to others: Be very very VERY careful with ADB and read your commands carefully. Those warnings about bricking your phone are real and shouldn't be taken lightly. I've rooted 6 devices and flashed what I'd estimate as over 60 ROMs over all my Android devices. I let my guard down and rushed things, and really my carelessness is all to blame at this point.

Trying to reset before warranty claim

Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.

xThaNaturalx said:
Hey guys,
Kind of an interesting question here. I've had my GS3 since summer and it's been running great. I was on a custom ROM with root (done without tripping binary), so it still says Samsung official and 0 flashes on the download screen, but it does say "custom" on the system status. Anyway, I hadn't done anything with flashing in several months. But the other day my phone just shut off and wouldn't turn back on. When I try, it vibrates, goes to the samsung splash screen, then shuts back down. Doesn't matter what I do, it won't get further than this. Can't boot into recovery or download mode with the button combos either. Won't read it on the computer or anything either. So I went out today and made a jig, thinking this would help. Well, it kind of did. It boots it into download for about five seconds, then shuts back off. So it's not enough time for me to get it to the computer and flash the stock ROM through Odin. I was thinking about trying to send it in to Samsung for warranty claim, because I had seen that people had luck with this when this was happening to a lot of GS3s in December. On several forums people said that Samsung was doing it no questions asked, regardless of root because they knew it was a hardware problem. So my question was just whether anyone here had any experience with it/Samsung? Or whether you guys thought I would be smarter to try and do it with AT&T? Anyway, thanks a lot for your time and input.
Click to expand...
Click to collapse
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.

aybarrap1 said:
Did you get a new battery? Worth a try. AT&T might get you one on the spot to try at a corporate store. Otherwise I doubt AT&T will be able to tell if you rooted if you can't boot up.
Click to expand...
Click to collapse
Absolutely true, but if its not the battery the atat rep will point you to an atat service center for assistance and its a safe bet that they have a few more tools at their disposal to troubleshoot the phone. If they somehow see any system modification, you are capital F****d. Do you have the wireless insurance with atat? I just dealt with this except I dropped the phone, shattered the screen and it would only power on for 10 mins at a time and then reboot. I paid my $$$ deductable and sent the broken phone to the insurance provider and yes the system still showed as being "modified" when I sent it to them.
Sent from my Atat S3 that now thinks its a Galaxy Nexus........

I would send your s3 to Samsung if it still under warranty. I sent over my bricked s3 and they fixed it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app