[Q] SCH-S968C(GP) Hard Bricked - Verizon Samsung Galaxy S III

Greetings!
I recently rooted my Samsung Galaxy SCH-S968C(GP), and Installed CWM Recovery. I flashed cyanogenmod to my phone. It had issues so i decided to try another rom. I was attempting to flash GlamourS5 to my phone. I went through the process. When it finished, the phone shut down. It didn't restart like the installer said it would. So i pressed the power button- no avail. It is now thoroughly hard bricked. It does nothing when power button is pressed. When connected to Windows 8.1 via a Samsung Micro-USB cord, The status indicator light turns red, and windows indicates (beeps) that a new device is connected. Windows does not offer auto play options, nor does the device appear in the Devices and Drives directory. When I long press the power button, the status indicator light on the phone turns off, and windows indicates (beeps) that a device has disconnected. However, the phone does nothing else.
My question to you is: Have I ruined my phone permanently, or are there ways I can fix it?

Related

Just flashes on startup. Black Screen

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.

[Q] [HELP] -Garmin-Asus A10 -Requesting for technical support

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.

Phone unresponsive, even to volume up + power button combination

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.

[SM-G925F] Hard Bricked, not turning on.

Hello guys,
My Samsung Galaxy S6 Edge (SM-G925F) has been sitting in the corner for a while. I've flashing it so Custom ROM (don't remember to which) and it got bricked. I've tried all possible ways to turn it on (Volume DOWN + Home + Power), but nothing helps. I can't turn on the Recovery Mode and Download Mode. I connected it to my PC, it recognizes it but instantly disconnects from it. When I hold POWER button, computer it recognizes it, when releasing the POWER button, it disconnects. When I open Device Manager on computer, it recognizes it as a Exynos7240. I tried to install various drivers but no-one seems to be working. The phone can't be detected by Odin, Multidownloader, Smart Switch and other apps.
If anyone knows the solution how to fix it, that might be really helpful.
Computer is using Windows 10 (64-bit).

LTE 32GB bricked by himself

Hello
Yesterday while i was watching ads in some freemium game tablet just turned off. I plug it to original charger and tried to turn on, but screen do not light up. Then I tried to press Power Button with Volume Up or Volume Down for from couple to 30 seconds but without any luck. When i connected tablet to PC, it shows as "APX" and system can not find drivers for it. When it is connected to PC via USB cable and when i press Power Button and Volume Up or Volume Down for 10 seconds light change from orange to green and tablet dissappear from device list in windows device manager and when i do it again it comes back as APX (doesn't matter which combination) so it looks like i can not get into fastboot mode.
What happend? What can i do to bring it back to life which was stopped for no apparent reason?
Tablet was flashed and after updated couple of months ago to newest OTA via ADB and it is with B01 battery.
My PC is on Windows 7.

Categories

Resources