Related
I have hard bricked my phone. The only thing that even shows activity is the blue LED at the top. I can get over the fact that I did this by flashing a bad ROM (a GSM ROM named incorrectly but still as always, my fault for not being careful). The device does NOT respond to the USB Jig, all it does is turn on that blue LED once again. So now that I am here, I know there is one option which is a JTAG repair by one of the fabulous members here. My question is whether I can just play dumb (I am dumb so it shouldn't be THAT hard) at a Sprint store and claim Kies was updating my phone and my computer did a hard reset.
First, would that be sufficient in bricking an ordinary phone? Second, after applying the Jig, the ODIN counter should be back at 0, is there any way for them to prove that I did it? I'm sure they'll know what I did, but it ain't what'cha know, it's what you can prove. So is this a viable option?
Thanks a million, you guys are the light in my galaxy
Take it into the store, tell em you woke up this morning, pulled it off the charger and this is what it does. Its really that simple.
Would it be over-the-top to do what I described? Simpler is better when it comes to these things?
Edit----
I have to go back to the store that I got the phone from. I just got it last week, signed a new contract. Should I go for the woman that sold me the phone with the aforementioned story, or should I go for a random at the service and support?
I would just say like mentioned earlier that you woke up and this is how your phone was. It won't turn on or anything.
Thanks, I will do that when I go there this morning.
its not hard bricked u just need a jig
drksilenc said:
its not hard bricked u just need a jig
Click to expand...
Click to collapse
Read the OP..he has and attempted to use the jig.
........
Have you tried going into odin mode?
Sent from my SPH-D710
Any update on this? C'mon OP don't leave us hanging!
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight
U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all
Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.
So I want to start off saying my device is not bricked. Just have have a question about knowing If a phone is bricked or if a hardware issue. I know the difference between a soft brick and hard brick but can a hard brick only happen after flashing some zip. Or can it still happen randomly without flashing or even entering the recovery in over a week.
I ask this cause it has happened to me before. Where one day my A100 wouldnt turn on. Not even the boot screen. The only sign of life was the light by power button while charging.
SO is it possible still to hard brick if nothing was flashed in over a week or most likely a hardware issue?
I thought the same thing happened to my note 2 yesterday. But all it was, was this damn new update draining my battery so fast. I thought somehow it was bricked lol
ANy answer to my question will be thanked
Yes, a device can get hard bricked without flashing or messing around with the recovery. That will most likely be a hardware failure issue.
But as you found out with your GN2, that the problem can be something else. That is where the art of troubleshooting becomes important.
That's not called hard brick. That's call device failure because of age or defect.
Sent from my SGH-T889 using Tapatalk 2
whatsitsnamenow said:
That's not called hard brick. That's call device failure because of age or defect.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Hard brick is the effect. Device failure (hardware failure) can be a cause of a hard brick. Not always, but can be a cause.
Hard brick is a non-recoverable bricked device (no matter how the device became non-recoverable bricked).
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
is it possible that the LCD went bad?? when you plug it into charge does it react (lcd or vibrate?) I would also suggest trying out a known battery. could be that if it is the original battery that it is so dead that I got "spikey" and finaly just died.
hope it is that simple
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
If she wasn't trying to flash anything, doesn't sound like a brick which, to my understanding, results from software failures. The procedure posted in the thread applies when you are trying to recover from a brick caused by firmware failure from attempting to flash the wrong bootloader so I'd be doubtful if it would help you here. This could be a specific hardware failure which is not unheard of with equipment like this. Also sounds like it gave warning of the gradual failure. When you plug it into a charging outlet, does it show any sign of life - a light or vibration? If it's an LCD failure, it probably wouldn't affect charging or recognition by your PC. If there is no sign of life at all even with different batteries, you may want to try a professional repair service as I presume exercising the warranty is not an option in view of the firmware history.
Hi,
Thanks for the replies.
I did try different batteries. The phone does not vibrate or react at all even when plugged in which does not suggest an LCD failure.
I guess you are right,it must be a hardware failure. I'm quite suprised,I thought these phones were well buit and resistant.Oh well.
She's getting a Nexus 5 now.
Thanks for the help !
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.
dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem
If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.
Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.