Database Info

[Q] Phone stuck in boot loop.. Plz Help!!

Phone is A3LSGH-T959V.. Will power on and start to boot into recovery mode, but will shut down and start that process over again.. What do I need to do to fix this phone??

tlrichardson said:
Phone is A3LSGH-T959V.. Will power on and start to boot into recovery mode, but will shut down and start that process over again.. What do I need to do to fix this phone??
Click to expand...
Click to collapse
Confirm the model of phone you have. If it is indeed a SGH T959V, use the guide in the second link of my signature.

It is confirmed that the phone is in fact the SGH-T959V.. I'm using a Windows 7 PC, and the phone won't stay powered on long enough for the system to load the drivers for it.. Any other suggestions or advice is greatly appreciated...

tlrichardson said:
It is confirmed that the phone is in fact the SGH-T959V.. I'm using a Windows 7 PC, and the phone won't stay powered on long enough for the system to load the drivers for it.. Any other suggestions or advice is greatly appreciated...
Click to expand...
Click to collapse
Could you provide more info on how the phone got stuck, were you trying to flash a new ROM. Lumins guide is excellent( it has gotten me out of multiple self induced boot loops) but after installing one click, windows will not show you, on the pull down, a samsung composite device. you will have to look through the different drives that are shown to determine which drive your phone is on.
If you can get into the recovery mode, have you simply tried reflasing

tlrichardson said:
It is confirmed that the phone is in fact the SGH-T959V.. I'm using a Windows 7 PC, and the phone won't stay powered on long enough for the system to load the drivers for it.. Any other suggestions or advice is greatly appreciated...
Click to expand...
Click to collapse
If when you say shut down you mean bootloop, you need to read the guide as it says to put the phone in download mode. If your battery is dead, I'm sure you can figure out what you need to do to charge your battery on your own.

tlrichardson said:
Phone is A3LSGH-T959V.. Will power on and start to boot into recovery mode, but will shut down and start that process over again.. What do I need to do to fix this phone??
Click to expand...
Click to collapse
First make sure the battery is charged as Lumin suggested. If the battery is charged then my bet would be that you have a stuck power button. Try this. Pull the battery and put it back in. If the phone powers on by itself then your power button is stuck.

hechoen said:
First make sure the battery is charged as Lumin suggested. If the battery is charged then my bet would be that you have a stuck power button. Try this. Pull the battery and put it back in. If the phone powers on by itself then your power button is stuck.
Click to expand...
Click to collapse
Put in a brand new battery.. Phone is powering on by itself, but the power button doesn't feel like it's stuck.. Not saying it isn't stuck IJS.. It goes into recovery mode for a split second and resets.. Drivers won't load because the phone won't stay on long enough.. UGH!!

Definitely stuck

TwitchyEye said:
Definitely stuck
Click to expand...
Click to collapse
Without a doubt. Take the phone apart and clean the power button.

hechoen said:
Without a doubt. Take the phone apart and clean the power button.
Click to expand...
Click to collapse
I did, and seems to be working fine.. EXCEPT when I try to charge it or plug it into the pc.. It goes back into the boot loop.. Thinking the charger port may be the culprit here..

[Q] Stuck with bootloop no bootloader access :/

Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:

First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita

timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.

if you are SOFF u can go for RUU?

Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:

sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!

Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.

Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita

timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.

I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita

timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really

Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita

Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL

You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita

timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help

If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app

exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.

sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone

[Q] soft brick vibration issue

So while trying to put on a new ROM (I've rommed and done custom recoveries and radios on this phone before) I had TWRP recovery on it and the ROM I was going to wanted CWM on it, so I flashed that and on battery it will show Samsung logo then go into a 2 second vibrate boot loop.
None of the button combos work. I ordered a jig on ebay and it flashes download mode for about a second before it flashes again and goes into the 2 second vibrate mode again. I tried to go from jig to Odin and it saw it for a split second, but disconnected/failed as soon as it started looping.
I read about the power button issue and the behavior matches, but I know I was the one that messed this thing up.
Is the JTag repair service my only option at this point?
I got an S4 so I'm just trying to get this revived to get rid of it so too expensive and I'll just sell it for parts.
thanks in advance for the help!
Jeffro

jeffro7172 said:
I read about the power button issue and the behavior matches
Click to expand...
Click to collapse
Focus on that.

theesotericone said:
Focus on that.
Click to expand...
Click to collapse
The reason I dismissed that was because I actually did it twice.the first time I was able to get into odin.
So of course the next time I did it, I told it to reboot into recovery and that was the last command I gave it. Since recovery is hosed I think that's why it's just looping.
I guess it could be the power button but I think because I hosed recovery, it's just not booting.

This phone has a separate recovery partition. So even if you hosed the recovery it would still boot. Theory here, like I said I've never seen anyone report a recovery bootloop. I think it's just a timing issue. Power button happened to get stuck when you where flashing something. The fact that it won't hold DL mode further leads to the simple solution.
You got a stuck power button.

Isn't the sop for this problem a battery pull? If you take the battery out and put it back in and the phone tries to turn on by itself(lights or vibration) then it's a faulty power button.

jondroid2 said:
Isn't the sop for this problem a battery pull? If you take the battery out and put it back in and the phone tries to turn on by itself(lights or vibration) then it's a faulty power button.
Click to expand...
Click to collapse
makes sense guys, that's what it does. Guess it just so happened to crap out right when I was messing with it. Thank you all, I'll head that route and see if I can get it revived.

It indeed revived with a take apart and some power button fiddling. Thank you all very much!

Bricked Phone?

I went out partying last night, woke up to a crack on my nexus 5 and wouldnt turn on but the led would flash red. I figured it lost its charge. Charge the phone for few hours, phone would turn on and off right away as if it still were not charged. It would than shut off but restart to a screen that said Firmware Update- Please wait while it installs- B100. Nothing would install, it would stay at 0%. So I held the power button and now, it only turns on to the google sign and keeps looping from there. I tried to turn it on in recovery mode but that doesnt work either. My phone was never rooted, bootloader never unlocked and I never put it in debugging. I dont know what to do!

so the ol' 3-button combo doesn't get you to the bootloader?

Yes, it does. Forgot to mention that.

tonytouch311 said:
Yes, it does. Forgot to mention that.
Click to expand...
Click to collapse
I don't know what you did, but your phone is not bricked. Hope you have a recent backup. If you can get into the bootloader I'd try a factory reset in recovery. If that doesn't work then you're going to have to unlock the bootloader and try to flash the factory image. None of this may work as idk what you did to your phone, but this is what I'd do.

Is flashing a factory image/unlocking bootloader possible even tho I can't get into the settings menu to turn on debugging option?

tonytouch311 said:
Is flashing a factory image/unlocking bootloader possible even tho I can't get into the settings menu to turn on debugging option?
Click to expand...
Click to collapse
Yes, adb and fastboot are not related.
Sent from my Nexus 10 using Tapatalk 4

Are there any guides you all might suggest that are easy to understand?

Ask your friends what happened last night. Sounds like a good party
==**Team Nexus 5 sucks.**==
-Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build

tonytouch311 said:
Are there any guides you all might suggest that are easy to understand?
Click to expand...
Click to collapse
Alright, here. The catch-all solution: flash the factory image as in this thread http://forum.xda-developers.com/showthread.php?t=2513701.
Just remember to cd to your adb directory, I made that mistake and almost fainted because I thought my device was totally broken when fastboot devices listed nothing.
dicecuber said:
Ask your friends what happened last night. Sounds like a good party
==**Team Nexus 5 sucks.**==
-Underpowered battery for a 5inch 1080p screen that is non-removable. Weak generic antenna that drops signal. Worst speaker of any device on the market. Cheap plastic build
Click to expand...
Click to collapse
Really?? Is this your sig or just something totally irrelevant that you decided to insert into your reply? Do you even own one?

droid_<3er said:
Really?? Is this your sig or just something totally irrelevant that you decided to insert into your reply? Do you even own one?
Click to expand...
Click to collapse
It's his sig. Just ignore him.

I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.

tonytouch311 said:
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
Click to expand...
Click to collapse
If that's the case it sounds like you may have knocked something loose internally when whatever happened that caused the damage to your screen. Possibly a solder point or a cable coming loose.

Opened up the back cover, looks like condensation.....ill leave it alone for a few days and try again.

Reset
tonytouch311 said:
I was able to flash everything and it seemed successful. But, I can only get as far as GOOGLE and than it keeps rebooting.
Click to expand...
Click to collapse
Did u do another factory reset after last flash as this may need doing on some phones from what I've watched on good old YouTube...Good luck..

^Why would he factory reset when the phone is wet? You'll short circuit it that way..

The only method of a factory reset I've read about was turning on in Recovery, waiting for the little android, and holding Vol + and Power. Thing is my phone would never get to the little android, just loop on the GOOGLE introduction. Is there another method to factory reset?

tonytouch311 said:
The only method of a factory reset I've read about was turning on in Recovery, waiting for the little android, and holding Vol + and Power. Thing is my phone would never get to the little android, just loop on the GOOGLE introduction. Is there another method to factory reset?
Click to expand...
Click to collapse
Turn your phone off. Then hold power + vol down. It should boot into the boot loader. You'll see a "start" Then use the vol rocker to toggle to recovery. Once there push the power button. You should be in recovery. Then use the vol rocker to toggle to factory reset. Then use power to select it.

jd1639 said:
Turn your phone off. Then hold power + vol down. It should boot into the boot loader. You'll see a "start" Then use the vol rocker to toggle to recovery. Once there push the power button. You should be in recovery. Then use the vol rocker to toggle to factory reset. Then use power to select it.
Click to expand...
Click to collapse
Thats the method I'm unable to use...I was hoping there might be a string of code I could type into a command prompt being that I can only turn on the phone into the boot loader.

tonytouch311 said:
Thats the method I'm unable to use...I was hoping there might be a string of code I could type into a command prompt being that I can only turn on the phone into the boot loader.
Click to expand...
Click to collapse
Try
fastboot reboot recovery
Edit, sorry that's not going to work. Find the stock recovery image. Then try
fastboot boot recovery.img

So I was able to boot in recovery and factory reset, although the problem still persists. I will try and flash all images tomorrow. Thanks for all the help! Happy holidays!

[Q] HTC one m8 hardbricked can't access any thing

I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.

Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know

DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go

piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.

M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset

piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.

Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please

rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.

It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.

rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?

Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..