Help! I have been unable to find any posts on this topic here or elsewhere.
I have a rooted Samsung Galaxy S3 AT&T running CyanogenMod 10.1 rc 2. This release has been running well. In the course of trying to update, when I rebooted into recovery (I have used both TWRP 2.5 and ClockworkMod 6) the phone powered down and would not reboot. Pressing and holding the power button (with or without volume up/down or home) for an extended period of time did absolutely nothing. Nor did pulling the battery, which had 80%+ charge.
All threads I have seen describe situations where powering-on starts the boot process but the boot process won't finish. In this case, pressing and holding power does absolutely nothing.
The last thing I did was run EZ-Unlock-11.apk, which first reported that the bootloader lock status was undetermined, but then reported it as being unlocked after I pressed unlock. This probably wasn't necessary as I would imagine the bootloader had to have been unlocked for me to have flashed CyanogenMod 10.1 in the first place.
Connecting the phone to a computer via USB doesn't do anything either. The computer does not see the phone (naturally), though this too worked fine before this happened.
Any ideas?
P.S. Additional information: with the phone plugged into a charger, the LED's do not light.
Looks like you just experienced the sudden death syndrome, unfortunately. Probably the EMMC failed and the device is bricked. If you are under warranty, see if you can get a replacement.
http://forum.xda-developers.com/showthread.php?t=2058560
Sent from my SGH-T999 using Tapatalk 2
klin1344 said:
Looks like you just experienced the sudden death syndrome, unfortunately. Probably the EMMC failed and the device is bricked. If you are under warranty, see if you can get a replacement.
http://forum.xda-developers.com/showthread.php?t=2058560
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks... I checked the linked articles and (1) this syndrome is reported only in the non-U.S. device; and (2) it's reported to have been fixed with a Samsung firmware update and there's a patch that requires stock. Can this happen with CyanogenMod running?
wheindl said:
Thanks... I checked the linked articles and (1) this syndrome is reported only in the non-U.S. device; and (2) it's reported to have been fixed with a Samsung firmware update and there's a patch that requires stock. Can this happen with CyanogenMod running?
Click to expand...
Click to collapse
So you're running the AT&T variant...It looks like the EZ-Unlock apk you mentioned is for the Verizon version. Running that and having it unlock a bootloader that didn't need it might have bricked it.
FIESTY2 said:
So you're running the AT&T variant...It looks like the EZ-Unlock apk you mentioned is for the Verizon version. Running that and having it unlock a bootloader that didn't need it might have bricked it.
Click to expand...
Click to collapse
+1 this is the reason its bricked.
ATT S3 doesn't come with a locked bootloader and has a different partition to bootloader/recovery then Verizons S3.
After you ran that app you applied something where it wasn't supposed to go and completely bricked your device.
This is why its recommended to read and research before rooting/modding and installing custom apps/firmware.
I'm sorry to say but your phone is a paperweight.
Sent from my SGH-I747 using xda app-developers app
Related
Heres one for you all. Just got my GS3. Rooted it..bla bla..bla. Was running on stock rom of course and decided to try out one of the cm10 nightlies. Did my back up..bla bla bla and new rom would not flash. tried another and got the same thing. I was reading around and came across someone asking another guy if he had unlocked his bootloader because the same thing was happening to him.. The guy provided the .apk to unlock bootloader so I figured Id try it. Unlocked fine. Went to Rom Manager and booted into recovery.
Thats the last time my phone has been on. I cant get to anything. I can plug it into computer and hold power, vol, home buttons down for download mode and recovery but nothing. The computer will beep like its acknowledging it but still doesn't do anything. PLEASE HELP. This is my first Samsung and Ive always been able to get to recovery or bootloader to fastboot but this has me completely shut out. Im desperate. Thanks.
EDIT: remember, I never got to flash a new rom. All I did was use that unlocker.apk(not sure of the name) to unlock then booted into recovery from rom manager. Using that unlocker i believe is what did it. Like I said, im new to samsung, besides rooting some s2's for people at work and never had to unlock bootloader on their S2's
Unlocker.apk? Maybe it's a good thing I don't know what that is? But I would guess that may be part of your issue .
How did you get root?
Did you use this http://forum.xda-developers.com/showthread.php?p=28019751 ???
Sent from my SAMSUNG-SGH-I747 using xda premium
Unlocker.Apk? Never heard of that and the at&t gs3 doesn't even have a locked bootloader. What user gave you that? If you can get into download mode.. (power off phone ..hold volume down + power button + home button) then flash back to stock.
I see that you CAN get into recovery? Since you made a backup ...why not just use it?
Sent from my SAMSUNG-SGH-I747 using xda premium
Assuming you're running the AT&T version, your bootloader was never locked. So, running an app to unlock your bootloader (which would be for a different phone), seems like a sure-fire ticket to brick town.
Seeing as how you can't boot into recovery or download mode at the moment, I would imagine your only recourse would be to try a USB jig to get into download mode to try to flash back to stock. Else, if the jig doesn't get you into download mode you'll either have to seek out JTAG service, try to get a replacement via warranty (make up some story), or enjoy your new paperweight and buy a new phone.
Good luck.
defnow said:
Unlocker.Apk? Never heard of that and the at&t gs3 doesn't even have a locked bootloader. What user gave you that? If you can get into download mode.. (power off phone ..hold volume down + power button + home button) then flash back to stock.
I see that you CAN get into recovery? Since you made a backup ...why not just use it?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I too have never heard of this apk. It sounds malicious. He should return to stock. One time after rebooting my phone the Rom would never boot; the screen was black. I even tried restoring a backup but that yielded the same results. Get into Odin and flash a stock package from the dev thread.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
If you need JTAG this guy who posted this thread evidently had good luck. Check it out.
http://forum.xda-developers.com/showthread.php?p=30942252
Sent from my SAMSUNG-SGH-I747 using xda premium
Have you tried...
There really aren't enough details in your initial post to properly speculate on what is happening or happened with your phone, but...
I found that the easiest way to enter Recovery and Download mode is when the phone is not connected via USB.
Have you tried entering Download mode while the phone is not plugged in via USB?
Unlocker.apk meant for the Verizon s3?
Yeah..
Congratulations on your shiny new paperweight!
JTag is your only hope.
Goodluck!
it seems that my friend has bricked his phone by installing a verizon boot loader in a at&t gs3 i tried going into recovery and download but nothing the phone wont boot or anything seems to be dead.
question is is there any way to fix it I tried many methods but all failed ):
Why would he install a verizon bootloader? He might have to get a jtag service to fix it. Bummer
Sent from my SGH-I747M using xda premium
undecided323 said:
it seems that my friend has bricked his phone by installing a verizon boot loader in a at&t gs3 i tried going into recovery and download but nothing the phone wont boot or anything seems to be dead.
question is is there any way to fix it I tried many methods but all failed ):
Click to expand...
Click to collapse
Jtag once i was having same issue with my brothers phone tried tiresly but no go
Sent from my SGH-I747M using xda premium
1) Charge battery & phone for an hour.
2) Pull battery for five minutes
3) Put battery back in
4) Press and hold VolumeDown+Power+Home
If that doesn't get you ANY display at all, not even a splash screen, then it's a "hard brick" and he'll need to send his phone out for "JTAG" repair. They are available on eBay for ~$50.
If you do get display, then come back and let us know for the next step (odin).
Some people think the phone is bootloader Locked. When they see that verizon version has bootloader unlock, they flash that.
I almost made that mistake, but I read and re-read everything for a week before even downloading stuff to try
Sent from my SGH-I747M using xda app-developers app
Is it possible for a usb jig to fix my problem?
undecided323 said:
Is it possible for a usb jig to fix my problem?
Click to expand...
Click to collapse
HIGHLY doubtful at the moment. Have you tried the above listed options?
Deoxlar said:
Some people think the phone is bootloader Locked. When they see that verizon version has bootloader unlock, they flash that.
I almost made that mistake, but I read and re-read everything for a week before even downloading stuff to try
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Deoxlea...... WHAT.... HOW DARE YOU..... You mean you READ stickies? What are you trying to do. Set a good example?
My only option for the phone to start working is a jtag or a usb jig. I I ordered a usb jig and will report back if it fixes my phone
I have a jig from my old captivate that has worked both times I've tried to get into download.
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
chylos said:
Hi
I saw update notification tonight. Tried to update my stock nexus 7 over the air. Device sad it will reboot to update but it powered down. Now it's not opening and not charging. It's bricked
I searched google and nothing came up.
What can I do pls help guys
Click to expand...
Click to collapse
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
It seems the the bootloader was corrupted, but from what I can tell, even if the upgrade modifies the bootloader it should have happened during the upgrade which runs in recovery, not before the upgrade even began.
Click to expand...
Click to collapse
yepp exactly the same.
In short, don't update
Sent from my Nexus 7 using XDA Premium 4 mobile app
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Sent from my Nexus 7
datallboy said:
Use the Kit Kat factory image to restore your device to an "unbricked" state. I updated to KST16S OTA and had no problems. Unlocked, rooted, stock ROM, stock recovery.
Click to expand...
Click to collapse
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
I wish it were that easy. It is the bootloader itself that is corrupted. I doesn't start far enough to use fastboot. It doesn't matter the button combination, the screen stays totally blank.
Click to expand...
Click to collapse
Damn that sounds awful, and I was nagging for not getting the update, that's way worse. So you can't access bootloader mode at all? Did you try to use fastboot commands or adb when plugged to the pc?
Worth a shot if not already tried:
http://forum.xda-developers.com/showthread.php?t=2404297
DarthBOFH said:
I'm in the same boat. Updated to KRT16O a week ago and it worked fine. Yesterday morning I had a notification that an update was available. I touched the update button, watched it count down from 10, the screen went blank and that was it. If I plug it into my computer, it is detected as a QHSUSB_DLOAD device, which according to searches is bad news. I've got an RMA with ASUS and will be dropping it at the post office tomorrow.
Click to expand...
Click to collapse
I've actually gotten the QHSUSB_DLOAD before when trying to get into bootloader but pressing the wrong buttons.
I was eventually able to get out of it going through various button sequences.
I believe holding down the power for a long time worked in the end, but I forget now.
nope nothing helped me. it's still bricked. i tried every button combination up to 3 minutes. No sign of power.İt was 32 gb. i think google ****ed up this time.
So i bricked my Samsung Galaxy S3. I believe it is hard bricked because there is absolutely no response from the phone. Can't boot into recover, download, or regular boot. The phone has at least 40% battery when I last saw it work.
I was attempting to roll back my android OS to see if I could extend my battery life but every time i tried using odin my download mode would give me "sv rev check fail" so i attempted to unlock the boot loader. I couldnt odin it so I flashed a custom rom to check if I could flash roms on my phone. The slimkat custom rom worked but when I tried to flash back to stock I would get the sv error. I saw that EZ-Unlock app would work so i tried it out. The app said it unlocked but when I restarted the phone to get into download mode, the phone seems to be bricked.
I have a usb jig but it doesnt seem to force my phone in to download mode and I am waiting on a micro SD card to try to un brick it. How can I use the micro card to un brick the Tmobile version of SG3?
Samsung Galaxy S3 SGH-T999
First of all the bootloader is NOT locked, so whatever that app does it was not mean for this device.. You should never attempt to downgrade firmware, it has been stated many times that there is high risk to hard brick when you try to bypass this restriction. The unbrick might work
Follow instructions in the debrick thread and hopefully it'll work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
NomNomMOn said:
I saw that EZ-Unlock app would work so i tried it out. The app said it unlocked but when I restarted the phone to get into download mode, the phone seems to be bricked
Click to expand...
Click to collapse
thats what i used on my first S3. bricked it like a............brick.lmfao.
gave it to some guy and i here now that he was able to revive it by some magical hoo-doo crap. well thats what i deserve for not reading reading and reading some more.
well , good for him is all i can say.! at least its gettin used ! :sly:
err on the side of kindness
Lol! I couldn't remember for sure if that's how it had happened on this thing, so I didn't want to say for certain that it was fixable. (Should a just asked you, but in my own defense, what's left of my mind these last few weeks is pretty much a scrambled mess!)
Anyway, I can 100% confirm that this type of brick is fixable. Using it as we speak/type!
And thanks to mrrocketdog for saving my a$$ with this thing! I may not have been around at all the last little while if not for him! (Might be back using my sad little MyTouch 3G Slide!)
Sent from my SGH-T999 using Tapatalk
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
shadows006 said:
I don't know why, but for some reason my nexus 5x is stuck in a bootloop. I was rooted running 6.0.1 (MTC19T) when it shutoff and was not trying to update to N as others were.
I can access the bootloader, but not recovery (just reboots). I have flashed other stock 6.01 OTA's which hasn't changed anything. Flashing TWRP again does nothing. Was trying to follow THIS thread, but PC does not recognize phone in download mode. Also, the phone will only stay download mode for about 15 seconds before rebooting. Any advice?
LGH970 32GB
Bootloader: BHZ10m
Baseband: M8994F-2.6.32.1.13
Secure boot: enabled
Device state: unlocked
Click to expand...
Click to collapse
Well If u can access bootloader you can flash any firmware using fastboot commands.
Totally weird, but my 5x just did the same thing. I opened the Yahoo Sports app, and it froze. An attempted reboot, and it's now stuck in a boot loop. If I try to enter recovery, it reboots. Unfortunately, my desktop is at work, so I can't troubleshoot right now.
I'm starting to wonder if I'll be reading several of these posts today. Hmmm...
enzo_cz said:
Well If u can access bootloader you can flash any firmware using fastboot commands.
Click to expand...
Click to collapse
Yes, but I've tried flashing multiple different stock images from the google repository by unzipping them and flashing the components to no avail. Is there another way to flash it? Should I be flashing something else?
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
shadows006 said:
UPDATE: tried everything. Getting a replacement from google. Only a month or two from the year warranty. Week without a phone. Thanks Obama...
Click to expand...
Click to collapse
That is exactly the route I took with customer service this afternoon.
Mine is @ LG as I haven't bought from Google... Let's see...
talkEDtv said:
That is exactly the route I took with customer service this afternoon.
Click to expand...
Click to collapse
Same here, when I went back from 7 to 6.0.1 bootloop. I unfortunately did not get to try the TOT file method as I had already RMA it out and just this morning caught this.
Out of all the Android devices it amazes my how easily this device bricked. I had numerous HTC devices and despite being carrier locked and using a java card to unlock the bootloader i never once had this issue with with any of them, they are very forgiving and will be seriously considering the 2016 HTC nexus as this one is only 4 months old. Im nowhere near n noob to rooting and flashing but disappointed how unforgiving the device is. Granted there are some things I really like about it, but bricked in 4 months is a bad sign of quality IMO.
Nexus are impossible to brick, unless you flash stock factory image...
I have had this same problem.
http://forum.xda-developers.com/nexus-5x/help/5x-bootloops-recovery-t3391459
Eventually after disassembly, I called Google Play and LG, to have it replaced.
I also had a cracked camera glass and screen, got a new Nexus 5x , and havent been charged since it seems the phone was due for failure no matter what.
The problem SEEMS to be the button or signal of of the power button always being pressed. When it's off it will even turn on by itself, and maybe if your lucky itll stay on for a while.
Call in, request RMA
---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------
gpvecchi said:
Nexus are impossible to brick, unless you flash stock factory image...
Click to expand...
Click to collapse
This is not true, unless in context TO BRICK, as they seem to be BRICKING themselves sometimes. Hardware defects exist in all electronics, even the good ol'nexus