So i've looked around and no one that i've seen has the same exact problem as i do. Here's my post in another forums about my problem.
Here's my story about my Galaxy s2 for T-mobile. My phone randomly turned off 2 days and whenever i tried to turn it on, it would restart and basically never get pass the blue loading bar screen. Second, i found out about this boot loop sequence and i was able to do a factory wipe.
After i factory wiped the data etc off the phone, i was able to use it until it ran out of battery, but then after i found out it ran out of battery, it wouldn't let me turn it back on, it wouldn't get pass the loading screen, once again. On the other hand, i am able to go to recovery mode or download mode, but the phone shuts off before i can even try and click on the options i want.
Today, i found out that if i kept pressing power button consecutively on the phone, I'd be able to go to my home screen and basically act as if nothing ever happened, it'd function as a new phone! I then had the nerves of turning off my phone just to make sure it finally works now, but my hopes were crushed and now the pressing the power trick does not even work anymore. It would probably work one out of 10-15 times, and in the end it'd still restart. I am using a gingerbread galaxy s2. My friend tried using the usb jib on my phone, and it worked but whenever he tried to plug in the usb, the phone would just restart. I am extremely frustrated with this, and if you can help, please do so because it's important that i fix this phone. If you have any questions, please feel free to ask!
Hi there, thank you for the welcoming me to the forums. No, my phone is not rooted, it has always been gingerbread etc i never tried rooting because i never knew how:/ I believe this started when i was just browsing around facebook, so i'm not entirely sure what happened... Uhmm i tried going to download mode through the volume keys and power button when it's connected to usb to the i think it's odin3? and it'd be in the download mode but as soon as the computer says it's connected, the phone would just turn off again and bam, it's like nothing ever happened. My phone does charge when it's plugged in, but it doesn't show it's being charged but i remember my battery was dead last night and i charged it till today and now it's got power. ANd no i don't have a warranty:/ i really hope you can help me
Sounds like a faulty power button. Check out Mobiletech video for thier power button repair service.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-t-mobile-power-button-repair/
Sent from my SGH-T989 using xda premium
Related
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. -_-
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
dubbz84 said:
I have a SPH L710 galaxy s3 (sprint). I recently flashed a Rom called hyperdrive 4.1.2 that was on it's RLS11. following the instructions (factory reset x2, wipe cache, wipe dalvik, wipe system), I then picked the features i wanted in the built in aroma installer and let the rom flash. When it was done I noticed i kept getting the message "the process com.android.phone has stopped". So i performed a clean install of my previous Rom which was Liquid Smooth.
A day or two later I noticed hyperdrive has released it's RLS 12, so i decided to give it another try. This time there was an option in the aroma installer for developer picks so i selected that, thinking my previous attempt i may have picked conflicting files in the aroma installer. The Rom worked fine for about a day. Then the next day while it was charging after the battery have completely died the night before. I noticed the phone had rebooted on its own, then it started going into a boot loop. I did a battery pull, and i noticed when i put it back in, before i could even hold the buttons to get it into recovery mode or download mode, the phone would vibrate and turn on by itself, without me pressing any buttons at all. After some trying i was able to have the buttons held so when i inserted the battery, i was already holding the buttons to try to get to recovery. When I did this it would say it was about to go into recovery, then the screen would go black. The same thing when I tried getting it into download mode, It would show the download mode screen, then go to a black screen. I Then did some research, after seeing no one else really having this problem, and noticing that since it was still seeing boot screens before the black screen, it shouldn't be a hard brick.
I decided to order a USB jig for my phone that came today. When inserted the battery with the usb jig the phone still turned on by itself, but it was able to go to download mode and it stayed at the screen. I used odin 3.07 to flash SPH-L710_MD4_1130792_Rooted_Nodata, which was a tar file you would use if you wanted to keep your user data. It took 10 minutes to flash but everything seemed to be a success, it rebooted my phone and everything seemed to be working fine. After about 20 minutes of my phone being plugged back into a charger and i was halfway through with downloading an app from the android market where out of nowhere my phone temporarily froze and then rebooted, to where it will show the samsung screen, then the samsung galaxy s3 screen, then just goes to a black screen. Now even with the USB jig, it will still power on by itself as soon as a place in the battery, go directly to download mode, but then go to a black screen within 3-4 seconds before i can do anything.
Has anyone ever encountered anything like this before? At first i thought it might be a stuck power button, but when I was able to flash through download mode with the USB jig that first time it makes me think it is bricked. Any help or insight would be GREATLY appreciated.
Click to expand...
Click to collapse
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
GiantJay said:
How long did you let it set on the black screen because it takes a while to boot up the first time after flashing a ROM.
Click to expand...
Click to collapse
Well i just placed the battery back in, it started on it's own without my pressing anything again, and i've been timing the last 5 minutes. but it seems like it will stay a black screen indefinitely. unless i remove the back of the phone, or snap it back into place, or any kind of micro impact movements it seems, when I do that it vibrates like it's first being turned on, and shows the samsung screen, then the samsung galaxy s3 screen, then it will go black again.
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
topherk said:
See if your adb on your computer can recognize the phone while it's stuck on the black screen. You might be able to push a Rom or recovery over using that.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Not picking it up on adb.
dante32278 said:
You may want to just start fresh and lose your data with a different stock file. That kinda happened to me before on the gs2 and I found better results with a 100% fresh start. The no data always left me with a hangup or two after getting the phone to boot.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
After the first odin flash i was thinking the same thing. But that's the thing, it won't stay on the download mode screen long enough for me to even try to flash anything else through odin. I'm also noticing when connected to the charger, if i make a slight impact against the phone with my palm, the screen will briefly show the battery icon as if the phone is charging when it is turned off, then the screen will go black again. When it is unplugged, is when it will show the samsung screen, then the samsung galaxy s3 screen, then go black again.
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
To me it sounds like maybe your power button is stuck "down"
If you didn't know, the power button has a fail safe reboot that happens after holding for about 10 seconds. So no matter what, if you phone is frozen or whatever, holding power more than 10s will cause it to reboot. That would also explain why its turning itself on as soon as you pop in the battery.
toolegit said:
That's weird...sounds like something is loose. Any kind of recent impact damage to the phone? Dropping it, throwing it at your cat, anything like that?
Click to expand...
Click to collapse
not recently, and if it was ever dropped, it would be in it's case... But i had noticed that while it was in it's power glove case, sometimes i would have to use more than normal pressure on the power button to get the phone to respond. I was wondering if something was stuck, just haven't read anything like that happening to anyone, and when I used the jig the first time the screen stayed on.
So I came home after being out for a bit and went to check my phone. When I hit the power button the screen didn't turn on. I then unplugged it and the charging LED stayed lit green once I unplugged it (it should have went off). I could not get the screen to turn on. I then plugged it into my PC to see if it'd recognize the device and nothing happened. Then, I had someone call my phone and it rang like it was on and went to voicemail, but the screen didn't do anything. I then reset it using POWER + VOL UP. It restarted and seems fine now... but I am not sure what that was. It is on stock 4.4.3 (I did the GPE conversion). Haven't had any issues with it until this. Hopefully it isn't a bad sign...
Zeebz said:
So I came home after being out for a bit and went to check my phone. When I hit the power button the screen didn't turn on. I then unplugged it and the charging LED stayed lit green once I unplugged it (it should have went off). I could not get the screen to turn on. I then plugged it into my PC to see if it'd recognize the device and nothing happened. Then, I had someone call my phone and it rang like it was on and went to voicemail, but the screen didn't do anything. I then reset it using POWER + VOL UP. It restarted and seems fine now... but I am not sure what that was. It is on stock 4.4.3 (I did the GPE conversion). Haven't had any issues with it until this. Hopefully it isn't a bad sign...
Click to expand...
Click to collapse
I don't think it's as a result of the device failing or something. I also had it happen to me only once and that was after I tried to install a program that requires root, it wanted to reboot but go stuck and didn't do anything. You could still hear the back ground notifications, ringing etc, same as yours, only difference being that I couldn't do a Volume up + power to reset, didn't work for me, lucky for me though it did pick up the device when plugged into PC.
I don't know if it's because of the rooting, or the rooting app or what the reason might be. Like I said it only did it once, haven't had a problem with it since(Been fine since the problem occurred sometime in April).
I mention the rooting app because it only occurred after I tried to grant access for root app, so... might be a coincidence, don't know.
Hope it's nothing serious for you as well :good:
BerndM14 said:
I don't think it's as a result of the device failing or something. I also had it happen to me only once and that was after I tried to install a program that requires root, it wanted to reboot but go stuck and didn't do anything. You could still hear the back ground notifications, ringing etc, same as yours, only difference being that I couldn't do a Volume up + power to reset, didn't work for me, lucky for me though it did pick up the device when plugged into PC.
I don't know if it's because of the rooting, or the rooting app or what the reason might be. Like I said it only did it once, haven't had a problem with it since(Been fine since the problem occurred sometime in April).
I mention the rooting app because it only occurred after I tried to grant access for root app, so... might be a coincidence, don't know.
Hope it's nothing serious for you as well :good:
Click to expand...
Click to collapse
Ahh, mine was a bit different. It was more like my phone froze and the screen couldn't power on. I actually couldn't hear notifications or anything or get them while it was like this. When the person called my phone it rang for them like they were connecting to my phone, then went to voicemail after like 5 rings (like if the phone was on). But my phone didn't ring nor did the screen turn on for the call, it was just frozen.
Once I hard reset the phone (POWER + VOL UP) when it came back on I got all the texts I'd missed since my phone messed up.
Happened to me once. The screen is on but black !
Required a hard reset
HTC M8
I have a Google Galaxy Nexus and was using it last night (8/11)--it was a bit slow, as it has been for a few weeks, so I shut it down and hope restarting may help. When I started it back up, it was stuck on the "Google" word for about an hour and then I suppose lost power. I was not near a computer to plug it in.
When I got home, I plugged it into my pc to charge, then read online to hold down Power + Up + Down, which I did. I got to the Recover console with the "start" and little Android guy and the white arrows. However, no matter what I press (power, up, down) nothing happens. I cannot get past this screen. Also, my pc was trying to find drivers for it and couldn't. What should I do? And is there a way to preserve anything on the phone? I have not modified the phone in any way (rooted or whatnot).
I think you cannot move between options because the bootloader is locked. Can't say 100% that's the cause of it though.
Thank you for replying. If that is the case, how do I fix that?
And after it ran out of power, I charged it again and tried starting it normally and it started. So I have no idea what is going on. However Im now afraid to restart it in fear it will be stuck on the logo again. It still runs a bit slow.
So I guess I have 2 questions:
1) If I have to load it into recovery again and no buttons work, how do I fix that?
2) Since it did start again, but runs slow, what could be going on? Any tests I can run?
Thanks!