Hello folks,
* mistake in title: I mean volume down + power
I'm having some trouble with my Samsung Galaxy S6 not responding.
I can't remember which Android version it has; it's whatever it came with in 2015, so it's Marshmallow or earlier. The phone is not rooted, not modified. I think that USB debugging is enabled.
The phone is showing a slowly blinking blue notification light.
It does not respond to pressing any of the keys, does not respond to soft reset (volume down + power), does not respond to hard reset (volume up + power + home).
When plugged into a computer via USB cable the computer does not give the option to connect to the phone.
Running "adb devices" at the (Ubuntu) command line with phone connected returns blank list of devices.
What are my options? Is there some other reset option I haven't yet tried?
Did u figure it out? I am having the same problem, thinking of changing the motherboard.
Same problem here, I wake up and the phone was dead, without touching it
It has RR OS 6.2 Android 8.1, no notification light, just nothing... Dead
This is weird, it's happening to me too, the same days...
If you find something about or see other S6 users with the same problem comment here
It is stupid answer, but leave phone for discharging battery, charge for a 15%, maybe (for quick discharge, if phone gets stuck again), and try to turn on. If it's doesn't helps, you can go to recovery and do reset.
Related
Hey guys.
I have an interesting problem. My Fuze battery drained a few days ago. After I plugged it back in and booted the phone, there is no light on the screen, keyboard or the button and no charging like shows up on the center circle.
After plugging it into the wall and powering it up, i can hear the phone booting. Once booted i can call the phone from another phone, the phone ring and I can press the talk button and take the call/press end to end it.
I tried doing a (blinded since there is visual light) hard reset (stylus/power button/volume button down/up combo) but unfortunately I have one of the EnergyROMs where the volume button functionality was not working so i dont think .
I also tried plugging the phone into USB to see if i can flash another rom, but the computer does not even recognize a device has been plugged in (even if tried searching from it using device manager)
Searching the posts have not yielded any information. Should I consider this phone dead?
Ali
Do a search on the MTTY tool, this might be able to connect & hard reset the device. Keep playing with it, you may get lucky or get some better advice soon ! Good luck
I got an HTC One S from a friend who got it from another friend. I don't have any history on the device. He gave it to me to fix because I'm the only Android user he knows and his phone won't start.
If I keep the power button pressed, the capacitive buttons flash exactly 15 times and occasionally the phone vibrates. I don't have a One S so not sure if that indicates that phone was started or shutdown.
Neither fastboot devices not adb devices shows the device. But every once in a while when it vibrates, if the phone is connected to the PC with a USB cable, it beeps - like it's connected. I don't see Android Phone in Device Manager. But I see a MTP USB Device with a yellow exclamation mark. Uninstalling and reinstalling HTC Drivers didn't fix the problem.
I have tried Power+Volume Down key. Shining a torch on it (seemed to work for a few people), keeping it plugged into the mains for 3 days, kept it in the freezer for 2-3 minutes (also seemed to work for one person).
I think when I first got the phone and plugged it into the mains, I saw a red charging light. But I may be mistaken. In any case, there is no light anymore indicating charging. But I don't think that's the problem.
I have no idea whether the device is bricked or not. And if there is any way to fix it. Samsung has Odin which makes any Samsung phone practically unbrickable. I haven't used any HTCs since the G1 so have not been in touch too much with the HTC development. But from reading, it seems that messing around with Romming with S-ON can cause the phone to be bricked. And perhaps that's what my friend or his friend did. Does this sound like that's what could have happened?
Thanks for any pointers.
I dont think the device is bricked. its just a little harder to press the power and volume down when you see the buttons flashing.
just check and do these steps.
connect the mobile to charger and see if the orange light comes and stays on
if the orange light is there, press the power button and keep your finger ready near the volume down button
you should keep the power button pressed and as soon as the orange light disappears you should press the volume down button until you end up in boot loader screen
give this a few tries and see if the device boots up in bootloader
ayyu3m said:
I dont think the device is bricked. its just a little harder to press the power and volume down when you see the buttons flashing.
just check and do these steps.
connect the mobile to charger and see if the orange light comes and stays on
if the orange light is there, press the power button and keep your finger ready near the volume down button
you should keep the power button pressed and as soon as the orange light disappears you should press the volume down button until you end up in boot loader screen
give this a few tries and see if the device boots up in bootloader
Click to expand...
Click to collapse
The problem is that I no longer see any light at all when I connect the phone to a charger. It's probably fully charged. Would that show a green light? If so, that's not visible either. I have a feeling that the bootloader has got wiped out or something.
I read in one post that the phone may be stuck in the QHUSB-DLOAD mode.
So I followed the steps in http://unlimited.io/qhsusbdload.htm. But that didn't help. I don't remember the exact statement since I was running an Ubuntu Live CD. But the gist was that it couldn't connect to the phone so presumably it's not stuck in QHUSB-DLOAD mode. Although the site states that it will NOT fix QHSUSB_DLOAD issues encountered by flashing ROMs - which may well be what may have happened.
I understand that running an RUU for the HTC One S may set it back to factory state. But for that I need fastboot to work.
Suspected problem: Bootloop
It all started when I connect my phone (Garmin-Asus A10 (v5.0.82 (updated with GarminAsusPhoneUpdater_Telenor_v2.0.3.exe of denmark))) on laptop through USB cable, the USB slot looks slightly damaged already upon looking at it, after connecting the expected to be happen is that the back-light will turn on, but what happen is that the phone has no response from it, I try to press the power button still no response, I removed the battery and bring it back and try to turn on again the logo appears (without vibrate which is supposed to be present in turning on my phone) then disappear after 7-10 secs.
It's already stock on the logo as I turn it on, the moment I pressed the power button the logo appears for about 7-10 secs then it disappear, also when I removed the battery and put it back the logo appears without pressing anything and disappear again after 7-10 secs.
I try to wipe the data through Volume Up + Volume Down + Power Button the ** WIPE USERDATA ** appears but then after a few secs it disappear again which is supposed to last for about a minutes.
And also I still can go to the **USB POLLING MODE ** through Volume Up + Power Button but seems like there is nothing to do with that thing.
I know it will be easy to fix this with the use of Garmin-Asus phone updater but it requires the phone storage which is so impossible to access at this point.
Hope you guys can help me with this, I badly need that phone.
----
Updates:
I can already open the phone and go to the home screen and menus... etc., but only when I close/cover the 1st metal/copper of the battery (back view (- to +))., but then I get an error saying that "The installed battery is not compatible with this device"
Upon doing this the phone is keep on rebooting, even if I already turn it off it keeps on turning on by itself, also I can't use any network at this point.
I already formatted the phone using master clear & **WIPE USERDATE** (Volume up + power button) still got the same problem.
And also updated with 006-B1243-00.update (The last .update file I used to update my phone (V5.0.82 DN)), upon rebooting after verifying the .update file it just blink twice then the update stops already at that point.
Updates 2:
Physically there is nothing wrong with the phone, I can still use the phone but as I mention already "only when I close/cover the 1st metal/copper of the battery (back view (- to +))." everything works fine except for the error "The installed battery is not compatible with this device" the red with "X" battery (Screenshot-1434948958913)
Also I notice something from my storage the "System Volume Information" (Screenshot-1434949331146, Screenshot-1434949336619, & Screenshot-1434949345666), I'm pretty sure that I haven't seen yet that before, I deleted the folder still it comes back.
Also once I connected my garmin phone to my computer the USB connected thing (Screenshot-1434949876071) don't disappear just until I restarted the phone.
Thanks in Advance.
My Nexus 5 was drained off battery and was not taking charging suddenly. I entered the hard reset mode( power+volume down button) and accidently did a "restart bootloader". Since then my phone has been hard bricked! I cannot enter into recovery mode as well( power + volume down button). But I am sure that if I can get the bootloader running somehow, my phone will be back. I am sure it does not have any grave hardware issues as such. But the maintenance (service) center says , they will need to replace the motherboard, which is too costly for me.
Can anyone give me any pointers of how can I get my phone working again?
aman572 said:
My Nexus 5 was drained off battery and was not taking charging suddenly. I entered the hard reset mode( power+volume down button) and accidently did a "restart bootloader". Since then my phone has been hard bricked! I cannot enter into recovery mode as well( power + volume down button). But I am sure that if I can get the bootloader running somehow, my phone will be back. I am sure it does not have any grave hardware issues as such. But the maintenance (service) center says , they will need to replace the motherboard, which is too costly for me.
Can anyone give me any pointers of how can I get my phone working again?
Click to expand...
Click to collapse
Have you tried connecting it to a computer and seeing if it gets detected by the computer in device manager? If so, it should still be possible to bring it back.
What exactly happens when you try to power it on? Does the screen turn on at all? Does it vibrate once, as supposed to, when you press the power button? Or is it completely unresponsive? Also, when you plug it in to charge, does a red LED light up where the notification light normally is?
Also, try various combinations of powering up sequences. You want to try the following:
Hold power
Hold power + vol down (this should bring you into bootloader)
Hold power + vol up
Hold power + both volume buttons
Let me know what happens when you try this, and maybe I can help you out!
I have a Lg G Pro 2. Few days back it got bricked by its own( a crazy fact). That time it was showing QHSUSB_BULK. I figured it out as 9006. Took the phone to a local service shop. Today I got it back and found that nothing had happened to the phone, except worse. Now it is not detected by PC, only green light blinks for some time if tried to power on. And then everything is black and cold as death.
I think it have been flashed with wrong ROM. Anybody here can guide me with the test points of Lg G Pro 2 (D838 F350) ? So that I can force it to QHSUSB_BULK ? Or any step by step advice to get it up ?
I am in real need of assistance, and thanks in advance for any sort of help. Best Regards.
I would like to mention that the phone indicator blinks for sometime if I try to power it on, as it does on boot, but nothing else is there. No recognition by PC, no presence in Device Manager. Blinks for sometime, stops, again starts blinking... and this goes on at regular short intervals. The area around the camera gets warm after sometime. Everything loops till I pull off battery.
Now, am I missing something ? Is the problem not as deadly as I am thinking ? Is it soft bricked ?
Hi, I not sure how it got bricked I never brick LG device.
Normally if anything happen we try pull battery out and put it back in, try then to turn the phone on.
Have you try connect to to pc with USB cable, one end of USB connnect to pc and other end connect to the phone. Then try press Power + Volume Up or Power + Volume down, this is to try to get into phone download mode. If you can get into download mode you can flash the kdz file to make it useable again.
Or without the USB cable we want to get to factory reset mode by use hardware method try press:
- Power + Volume Up or Power + Volume down
- If you see LG logo come up release the buttons you press above 1-2 second
- Press again Power + Volume Up or Power + Volume down
- Until it show and ask to use volume up/down button to select choice, say yes
Caution factory reset will delete all data on the phone and reset it as when you bought it new.
- Again it will ask for factory reset, use Volume up/down to choose and select yes for factory reset
turn on the phone and when light is blink press volume up or down button for some time and see if it it is detected as usbhulq?