Develop Bugs

HELP! Not quite bricked but similar!

So, I was having some FC issues using the 806 oc kernel on MyFroyo6. I switched to the 768 kernel and was fine. I tried another 806 kernel and had to go back, once again to 768. No big.
WELL, from out of nowhere, I was getting some unresponsive buttons (Home, back, etc...) they'd work eventually but were sluggish. I rebooted the phone and now it goes straight to the hboot screen. That'd be fine except my buttons do not work.
I just want to nandroid back to an earlier state but without the volume or power buttons working, that's impossible. The power button must work in some capacity otherwise it wouldn't turn on at all.
Any ideas?

I forgot to mention that it's going straight to fastboot without any help from me.

Does the trackball work? Is device visible in adb?

donkey72 said:
Does the trackball work? Is device visible in adb?
Click to expand...
Click to collapse
No and no.
It just sits in the fastboot menu. The volume buttons barely worked for a second and I managed to wipe but it's back to square one again. Stuck on the fastboot screen with no way to select the options.
I used roomie's phone to put ESPRNG.zip on the sdcard just to see if everything else is working and it is. From what I can tell, the phone is working but it's almost as though all the buttons are constantly going because it automatically went through the options I would have had to press "up" for. However, I can't control anything it's doing...

Water damage, mime did the same thing when I dropped it in the pool, give it time in a ziploc bag of white rice for about 2 Days that should do the trick
Sent from my T-Mobile myTouch 3G Slide using XDA App

Thanks! I think that might have been it. It's a moot point now seeing as how T-Mobile replaced the phone on the spot when I went in. I wasn't expecting that! I was going to ask them if they could shed some light on the problem and they just whipped out a new phone. Oh, well.

[Q] cant turn off, always turns back on in recovery!

can someone help me figure this out? i turn my g2 off, but right after its off it automatically boots into clockwork-mod recovery!! has anyone else had this issue?

rapidfire224 said:
can someone help me figure this out? i turn my g2 off, but right after its off it automatically boots into clockwork-mod recovery!! has anyone else had this issue?
Click to expand...
Click to collapse
Im having the same issue..weird!

Well known issue with CWR. Koush said its not high on his priorities. You could download the source and try to figure it out though.

hmmm, ok. im not an expert with doing things from source. somone else maybe, with more skills?

It's an issue when the charger is plugged in. It should shut down fine if you haven't got the charger connected.

there is nothing wrong with being in recovery while charging -- uses very very very little power and when your ready to turn on the phone, you just hit reboot and your done. Or maybe you want to clear cache before you boot? or maybe you want to backup before you boot or maybe you wanted to fix permissions before you boot? i mean -- its actually a blessing in disguise. I would be more annoyed if this was an issue with the G1 because it was so easy to get to recovery as it was (power and back button) whereas with the g2 if you wanted to get to recovery you'd have to either use adb or its PC counterparts, a reboot app in the rom, or by booting into fastboot and then 3 more steps after that to get to recovery.
its like living next door to the convenience store, bank, grocery store, and the massage parlor. one stop shoppin -- no hard trudging around to get places.
it is a benefit... yes its a bug...(a bug with benefits heh) but frankly i've put in a request that if koush updates recovery i want to be able to "keep" this bug.

androidcues said:
there is nothing wrong with being in recovery while charging -- uses very very very little power and when your ready to turn on the phone, you just hit reboot and your done. Or maybe you want to clear cache before you boot? or maybe you want to backup before you boot or maybe you wanted to fix permissions before you boot? i mean -- its actually a blessing in disguise. I would be more annoyed if this was an issue with the G1 because it was so easy to get to recovery as it was (power and back button) whereas with the g2 if you wanted to get to recovery you'd have to either use adb or its PC counterparts, a reboot app in the rom, or by booting into fastboot and then 3 more steps after that to get to recovery.
its like living next door to the convenience store, bank, grocery store, and the massage parlor. one stop shoppin -- no hard trudging around to get places.
it is a benefit... yes its a bug...(a bug with benefits heh) but frankly i've put in a request that if koush updates recovery i want to be able to "keep" this bug.
Click to expand...
Click to collapse
A convenience store that keeps its blinding storefront lights on all night even though the whole damn place is closed except for a soda machine outside.
Sent from my HTC Vision using XDA App

helloelan said:
A convenience store that keeps its blinding storefront lights on all night even though the whole damn place is closed except for a soda machine outside.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Talking about the screen?
Hold the back button. On my Pulse it turns the screen off. Or totally black, I can't remember.
Better yet, turn it upside down.
Or, leave it switched on.

DanWilson said:
Talking about the screen?
Hold the back button. On my Pulse it turns the screen off. Or totally black, I can't remember.
Better yet, turn it upside down.
Or, leave it switched on.
Click to expand...
Click to collapse
First time I discovered this bug I was about 9 hours late. I grabbed my hot ass phone n unplugged. I put it infront of the ac vent so it could cool down. After about ten minutes I powered up n the setcpu widget told me the phone was at 120 something degrees.
Needless to say my first g2 never ran right after words. Too many random reboots n odd graphical glitches.
I unrooted and cried bad hinges so tmobile would replace it.
Damn shame its not on his priorities list...

[Q] fml i think im bricked black vibrate errors

So let me start off with I've done research and not just posting up a new thread because I'm lazy. All of the threads that I have looked through all seem to be close but not the same as most people can boot into recovery.
Running Konis elite series III had it about a week with no issues Ive reboot plenty of times and havent had any problems once so ever. Now I think my problem happened yesterday when I needed to clear up some space and deleted the package I installed Konis rom from I figured since it was already installed the package wasnt needed anymore. I noticed later that day my number pad was no longer showing up didn't pay much mind to it figured i just needed a restart. Reboot the phone today at work and low and behold.
Phone gives me 3 vibrates no lights on regular power up.
Vol - power I get 5 vibrates green flashing led (gotta pull batt for it to turn off)
Vol + I get 3 vibrates no lights
The phone just stays black need to take out the battery in order to get the vibrate errors again.
All the threads I read regarding the 5 vibrates say its in diagnostic mode but everyone else is able to get into recovery. I think I am now the owner of an expensive paper weight. -_-
Would pulling the koni rom install file off the sd do this?
What does the vibrate error mean.. being in diagnostic mode is pretty broad how are you suppose to troubleshoot something like that :/

Are you able to get into the bootloader at all?

Are you absolutely 100% positive that you're holding volume down and power? That should take you to the bootloader. I saw someone with a similar problem, but they were just doing volume up instead.
What happens when you try to power the device normally?
And deleting the rom zip from your SD card shouldn't cause any problems. In fact, I can't think of a single way it could cause anything to go wrong. That is the only thing you deleted, right? You didn't delete anything from internal memory?
Sent from my PC36100 using Tapatalk

well i think that the 5 vibrates and green led's are indicative of safe mode. the other i'm not so sure about. if you're holding vol down and power and getting 5 vibrates then maybe there is a prob with your vol buttons. its acting as if your holding the vol up button without hitting it. maybe its stuck or something like that. just guessing though.

yo
Thanks for all the replys.
Nah doesn't let me do anything. I plug it in and it asks for broadcom drivers thats about it.
I made sure that the vol - is being pressed it gives me 5 vibrations and then the green led no recover menus/

A buddy of mine had the same problem after flashing the kingdom rom on his incredible. He sent it to the phone insurance company and they replaced the motherboard. So basically, your kind of screwed.
Well.....unless you can somehow fix it on the evo...... because I know we tried everything on his incredible, and it would just do the exact same thing every time, no matter what.

nvm same deal. it booted up intro recovery one time i erased cache and ran a saved backup on clockworks phone restarted after it finished and back to the same deal. yay.

unregimented said:
nvm same deal. it booted up intro recovery one time i erased cache and ran a saved backup on clockworks phone restarted after it finished and back to the same deal. yay.
Click to expand...
Click to collapse
What do you mean by back to the same deal?? Back to normal or back to the problem?

hardware related..
volume button keeps getting stuck some way some how and whenever the phone turns off its a pain to turn on. 30+ tries taking the batt in and out. When the phone would be turned on the volume would pop up randomly. Figured it was that so i bumped the phone on the desk with the buttons down and it cranked on did it again early today and it cranked up again after a few tries my phones toast. -_-

[Q] Phone shut off now stuck in permanent death loop

Hey all, I have a S3 i747 on rogers. I have had it for a couple years everything working fine and great, I rooted it after I bought it and it worked no problem. A week or two ago it suddenly shut itself off while I was using it. I didn't think much of it, then later that day again it turned itself off.
This time, it automatically tries to reboot but as soon as the logo appears it instantly turns itself back off again. It's not that it gets to a certain point, it's like there's a time limit on how far it can progress through the boot sequence, I estimate about 4-5 seconds. No matter what I try I cannot get it past this cut off time.
I have tried download mode, recovery mode, battery tricks (found on obscure sites), etc etc etc and still its stuck in this death loop. Im fine with buying a new phone, but I had not made a contact back-up for 6 months (no, I wasn't syncing with google) and have lost many, many new contacts as well as certain files and pictures that I wouldn't mind getting back.
Also, if I am very fast I can get the first page of recovery mode to pop up, but then the "time limit" hits and before any selections on the menu can be made it automatically reboots. If I leave the battery in, it will try every few minutes to boot repeatedly until the battery is completely zapped.

TeflonTeffy said:
Hey all, I have a S3 i747 on rogers. I have had it for a couple years everything working fine and great, I rooted it after I bought it and it worked no problem. A week or two ago it suddenly shut itself off while I was using it. I didn't think much of it, then later that day again it turned itself off.
This time, it automatically tries to reboot but as soon as the logo appears it instantly turns itself back off again. It's not that it gets to a certain point, it's like there's a time limit on how far it can progress through the boot sequence, I estimate about 4-5 seconds. No matter what I try I cannot get it past this cut off time.
I have tried download mode, recovery mode, battery tricks (found on obscure sites), etc etc etc and still its stuck in this death loop. Im fine with buying a new phone, but I had not made a contact back-up for 6 months (no, I wasn't syncing with google) and have lost many, many new contacts as well as certain files and pictures that I wouldn't mind getting back.
Also, if I am very fast I can get the first page of recovery mode to pop up, but then the "time limit" hits and before any selections on the menu can be made it automatically reboots. If I leave the battery in, it will try every few minutes to boot repeatedly until the battery is completely zapped.
Click to expand...
Click to collapse
Does it still keep rebooting even in download mode? If not then try reflashing your stock rom.
Or maybe try booting up without an sd and without a sim card.
Sent from my SGH-I747M using Tapatalk

Also make sure to not hold the volume and home keys too long when going into download mode, once the phone vibrates you should be able to let go. I made the same mistake on my phone and then noticed i had been pressing the volume and power keys while download mode was starting, causing it to select cancel. If not though you are probably looking at some sort of internal hardware issue that may be causing the reset to trip or causing the phone to believe it should be shutting itself off at that moment. This is all purely speculation, but hope it helps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Florad77 said:
Does it still keep rebooting even in download mode? If not then try reflashing your stock rom.
Or maybe try booting up without an sd and without a sim card.
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
zoomonkey90 said:
Also make sure to not hold the volume and home keys too long when going into download mode, once the phone vibrates you should be able to let go. I made the same mistake on my phone and then noticed i had been pressing the volume and power keys while download mode was starting, causing it to select cancel. If not though you are probably looking at some sort of internal hardware issue that may be causing the reset to trip or causing the phone to believe it should be shutting itself off at that moment. This is all purely speculation, but hope it helps.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I can't even make it into download mode, or recovery mode. Like I said, its as if the phone has a built in time-limit for how long it is going to load, the absolute farthest I can get is the first page of recovery mode and then boom it instantly resets before I can even make one selection, and I did this like 100 times in a row so I got very fast at getting into recovery mode. As per 2nd quote, yes I am releasing the buttons as I am supposed to to get into the appropriate mode, but the "time limit" hits and just reboots no matter what.
I've tried booting up without sim and sd card, but it still doesn't make it any further.

Dead boot look i747
Fix a fix for it? I have the same problem.
TeflonTeffy said:
I can't even make it into download mode, or recovery mode. Like I said, its as if the phone has a built in time-limit for how long it is going to load, the absolute farthest I can get is the first page of recovery mode and then boom it instantly resets before I can even make one selection, and I did this like 100 times in a row so I got very fast at getting into recovery mode. As per 2nd quote, yes I am releasing the buttons as I am supposed to to get into the appropriate mode, but the "time limit" hits and just reboots no matter what.
I've tried booting up without sim and sd card, but it still doesn't make it any further.
Click to expand...
Click to collapse

I would put my money on a bad power switch/button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yes, it acts like a stuck power button, a common problem with galaxy s phones.
If it auto starts when you insert the battery, that's a sure sign the power on circuit is active.
When my Captivate did this, I opened the back & carefully tapped it on a table edge to try dislodging any debris.
I then followed teardown instructions, inspected the switch assembly & blew it out with forced air.
The problem ended & never returned. I honestly don't think there was a physical defect in my phone's switch; more likely a residual charge on the mainboard.
Root causes vary as do solutions for the problem. Inexpensive switch replacement is a good one too.
Since then I have used a couple of apps to reduce the need for the gs3 power button.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[q] screen is glitchy after dropping!

Two days ago, my T-Mobile Samsung Galaxy S3 dropped out of my coat pocket as i was running for the bus. I picked it up and saw the screen was cracked along the top left and bottom left hand side. Everything was working for the past two days and i figured i'll just wait till Christmas to get a new phone. This morning i took my phone off the charger and turned it on. The Samsung logo flashed, and then the boot animation for Slimrom (the custom rom i'm currently running on) flashed for about a second but then the screen went black. I did a battery pull but the weird thing is whenever i put my battery back in, even without touching the power button, it boots up by itself but then the screen goes black again. I can access TWRP and download mode but they both go black after a few seconds as well. I was able to successfully turn on my phone and have it fully function for about 15 minutes after putting it back on the charger, but it quickly blacked out again. It also keeps randomly booting up by itself which is weird. Im guessing this is a problem with the screen itself, but could it be a software issue because the device keeps booting up by itself? If it is the screen, will i have to buy a new one or is it not worth it? I've also tried using a different battery and i have the same issue so it can't be that. Any help is appreciated!

Sounds like an issue with the power button, it probably got stuck somehow either when you dropped it, or after you dropped it. Do a simple search for power button and you will find ways to fix it!

Holy crap i didn't even think of that! It makes total sense since every time i even tap my power button, even for just a second, it turns on. I've read around that clearing the cache or a factory reset could work. Is this true?

Unlikely, unless it's a software issue but it's always a possibility. Slam the phone against something to try to get the power button back into place, or open it up and try to see if you can fix it yourself, or replace it

The problem seems to be gone. I haven't had any issues for two days now. All i did was press the power button really hard multiple times. Thanks for you help man!