[Q] Hard bricked or hardware failure? - Galaxy S III Q&A, Help & Troubleshooting

Hello All
Have been sulking for a couple of days as I have rooted many devices and decided to root my beloved S3 I9300 international from XELLA.
Used one click option and installed and updated to latest CWM and made a full nandroid back-up.
Then followed to the letter install of AOSPA:Android 4.2.2 JDQ39][28MAR] PARANOIDANDROID 3.15 - The Pure Experience! which after a couple of days found was a very good rom but not for me so wanted to go back to stock.
Now this is where I might have made a mistake, being a noob I am not too sure. I went back to recovery factory reset Wipe data and Dalvik then tried to restore full nandroid. It went through all the MD5 checksum bit and after 25-30 mins had re-installed XELLA re-booted and everything seemed fine.
Then going through and checking my data,etc my S3 just went dead!
No backlight, no 3 button download, no power, no LED, no absolutely nothing.
I have tried battery pull for over 2 mins malarky. USB jig, different battery, different USB cable, connecting to computer by USB normally and via KIES in which the device does not even register.
I have gone through every Q & A on here but to no avail.
Basically is the Apple of my eye hard bricked (So service centre bound.) or has someone got any new ideas I could try please.
Many thanks in advance.:crying:

Edit...just noticed you tried another battery
---------- Post added at 07:57 AM ---------- Previous post was at 07:55 AM ----------
Sounds and looks like a hard brick to me

Does your phone allow you into Download mode?
AndroidPlant
An everyday user.

If it won't boot into download mode then it sounds like total failure, motherboard or cpu etc blown.
Restoring your nandroid didn't cause it, particularly as it booted normally afterward. Send it to service for repair.

Totally dead!
I cannot get into download mode or anything totally dead.
The phone wasn't running hot or anything and it was about 20mins after returning to stock and all seemed fine.
I was just about to connect to PC for ODIN to root but nothing. Like I said tried download mode,another battery,USB jig,everything.
I did even look at the various JTAG threads for hard bricked phones so it does seem like a service centre job.
However as I had just switched from custom ROM and back to stock surely my counter will be showing as I could not 'triangle away'?
But if it is hardware failure, they repair and they boot it straight back into stock would they even check?
It seems warranty would be honoured as it is hardware failure not bricking via firmware. Not really sure on this one?
Many thanks in advance.

I very much doubt the service centre's approach to 'repair' would match your idea, they will only try to boot and then start replacing major parts e.g motherboard, screen etc. until it passes testing.
As long as there is no evidence of water or physical damage you should be fine, if the bootloader splash screen isn't appearing I don't see how they would even know you'd flashed a custom ROM.

try opening the phone and heat the motherboard with a heat gun or hair dryer for about 30 seconds abkout 10cm away from motherboard, it will re-solder any hardware that isnt soldered properly, if that doesnt work the solution will cost you money!

I tried the hot hair dryer trick to no avail. Spoke again to tmobile who are saying it is under warranty. So will stick it in the pre paid package they are sending and see how I get on.
10 working days minimum. Then another 5 before I hopefully get it back.
I shall post results asap for everybodys reference at that time.
Many thanks.
Sent from my Sony Tablet S using xda app-developers app

Phone coming back from repair.
I finally am having my machine sent back to me.
This is the report that was sent to myself.
FAULT DESCRIPTION
Power - Turn on/off - Turn on/off - Does not switch on
and this is what they have done.
REPAIR DESCRIPTION
Software update -
Screening -
Calibration -
Replacement - IC/PA/FILTER
The part in the photo had this on it SAMSUNG 222. (KMVTU000LM-B503) (HHDK579S). and was a chip which they said they had replaced.
I shall let you know when it arrives back.
Regards.

Solved. New board.
Now got the phone back and they have replaced the whole board in the machine with latest stock firmware (soon to be rooted.) and now hopefully SDS proof.
Hope this a pointer for someone in the future.:good:

Related

Boot problem. Would appreciate any advice

I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.

[Q] Not sure if bricked Vibrant or something else

Hello all -
My "bricked" situation appears to be unique as I've searched all over and have only found others with at least a phone that has a display.
Scenario:
Had SimplyHoney 4.0 installed (I believe Voodoo Lagfix was enabled). Decided it was time to go back to stock. ODIN'd back to stock (doesn't that wipe any VooDoo?). Re-rooted phone and connected to Kies for giggles to see if it would actually work this time for an "Official" update. (Last time I connected the phone it would not recognize the phone as the appropriate phone for an update) This time it saw it as a Vibrant and proceeded to do the Froyo update. Once it was completed, the Vibrant's screen never turned on.
It feels warm to the touch when you turn on the phone after a few minutes like it typically does, but I can't see anything on the screen.
Did this update do an extreme brick to my phone that it is now a lost cause?
I appreicate any advice you have.
BTW, tried the download button combos that are out here and none of those worked.
When I last had my phone open to fix the GPS contact, I see there is a small battery. Would popping that help reset anything?
It's the same scenario in this video on YouTube - "Video of hard bricked vibrant" by htcpro1212
Sorry can't post links yet.
I had a similar situation with a friends Vibrant this is what I did...pull out battery, plug phone to computer with usb, do the three button combo (volume up down &power) while holding replace battery and that should put phone in recovery mode... hope this helps good luck!
Sent from my Nexus One using XDA Premium App
no point rooting if you're going to update with kies, it wipes root
you could have just used whitehawkx stock 2.2 rom, kies has a history of hard bricks after you've been on a few custom roms
keep trying button combo's (vol + and power with the GB bootloades) but chances are its hard bricked, if it doesnt work phone samsung or t-mobile and say you tried updating with kies and it doesnt do anything now
Pm sent I can fix this for you...
You should always try ODIN back to stock. Its such an Relief.
I'm not sure if this will work in this case or not. When I thought I had bricked my Vibrant, I had a picture looking like a phone-triangle-computer on the screen, so it wasn't blacked out.
I got a "jig" (search the forums or google it.) They cost less than $10 and have saved me several times when I've messed up to get me to download mode so I can use odin.

I9100t HARD BRICKED... SUDDENTLY

That is what happed this morning:
Woke up, whatsapp for a bit, suddenly, reboot itself, stuck in siya logo.
waited for 30mins, no luck, hard turn off (long press power button)..
after that, no more reboot, no download mode, no CWM, try the three button trick no luck, remove battery and three button trick no luck......
Here is what I have done with my phone before, It runs perfectly for like months:
Resurrection Remix Rom 2.2
Siyah Kernal (latest S2 version)
BLN
Overclock (200-1300) but stable with siyah
Apex launcher...
I sincerely beg for all genius developers to give me a hand...........
Try a download jig and see if that makes it respond.
St0rmzx said:
Try a download jig and see if that makes it respond.
Click to expand...
Click to collapse
ordered.... still waiting for that..
any other solution yet to be discovered?
bump
as i didn't "flash" dead my phone, I think there might be some solution.....
...
you are damn right, I can't live without it...
my phone is out of warranty plus flashed count.......
plus still looking for a shop that do jtag in sydney...
...
Call wireless provider tell them a crazy story about an accident you had and your phone is crushed and bloody and if they provide upgrade then ask for an early upgrade due to no warranty that is what I did for my $3
Sent from my SGH-I747 using xda premium
i just hardbricked my galaxy2
no download screen, no recovery screen no boot...
its only a week old! in virgin warranty...
have you had any luck with finding a shop to to jtag in sydney????
only option is to claim on insurance...
duleim said:
i just hardbricked my galaxy2
no download screen, no recovery screen no boot...
its only a week old! in virgin warranty...
have you had any luck with finding a shop to to jtag in sydney????
only option is to claim on insurance...
Click to expand...
Click to collapse
If there is jo Jtag shop in Syndey, you can send it overseas for Jtag repair. But I suppose it costs a lot of money.
Alternatively, you can send it to Samsung, play stupid (phone didnt turn on this morning) and keep your fingers crossed.
Wish you luck mate.
Sent from my Galaxy S2 GT i9100
Could anyone shed some light on all these bricked phones that were bricked out of the blue - without users fault? I mean, there are so many threads about bricking phones while doing nothing - the phone was just normally used, or even with the screen off, and it just turned off by itself/rebooted itself/froze and there was no way to recover it... Similar thing happened to me month ago - I was on a safe stock 4.0.3 ROM with safe kernel (mmc_cap_erase disabled), I have just started a game that I play regularly, the screen froze, I have waited for some time, then tried to do a hard reboot, got stuck at booot logo, and that was it. Recovery was erased - no way to enter it, download mode was still alive but it was stuck while trying to flash anything - there was an error while trying to write rom, kernel etc. I had to sent it to repair centre...
Thos was just an example, one of many. So, the question is - is this bad Samsung hardware in action, or software bugs that are causing hardware malfunctions or something else? I mean, I had few HTC Android phones before, and I have never saw anything like SGS2 Q&A forum - every second thread is about bricked phone...
Any thoughts?
I think people jump in with both feet without doing much research.I don't blame them,as I just flashed RR3 and I didn't fancy reading 62,000 posts.
Plus its a very popular phone,so maybe its only a tiny %age that are faulty.
Sent from my GT-I9100 using xda app-developers app

Phone won't turn on after "system crash"

Hi, I have a galaxy s2 in what i believe is hard brick mode. A little backstory, i was watching some stuff online when i noticed the battery bellow 35%. So i pluged it to the usb charger. I left it there for like 20 minutes. When i came back, i unlocked the phone only to see tons of "error" messages and the force close window. Apperently it had to force close /system?... I was puzzled so i just pulled the battery off and on and tried turning it in. Stuck at the welcome screen. I tried ro acces recovery mode. The android icon was "dead" and some error messeges appeared in red, unable to mount /system, invalid argument. I turned it off, but the welcoming screen poped up without me touching anything. I left it for a few minutes. Then i pulled the battery off for a few minutes too. When i tried to turn it on again, the phone was dead. Nothing works, i tried:
Pressing the power button for a minute
Download mode
Recovery mode
Leaving the battery out for hours
Leaving it charging for hours
Nothing. Im stunned, mainly because i never rooted it or touched anything. Im desesperated at this point, any help will be great. I abused google and made tons of search, but everything related to my problem has to do with flashing and rooting failures. Which i never did with my phone.
If you've never messed with it, and assuming it hasn't expired time-wise, send it in for warranty service. If you don't have warranty, try another battery just in case, then try a jig. Then start looking for JTAG repairers (assuming it can be JTAG'd), and if it can't, take it to local mobile repair shops & have them take a look at it. If they can't/won't fix it, then send it to Samsung/authorised repairer.
I think i voided the guarranty by updating the phone to ICS a few months back... Im trying the battery swap now.
demian93 said:
I think i voided the guarranty by updating the phone to ICS a few months back... Im trying the battery swap now.
Click to expand...
Click to collapse
That wouldnt void the warranty.
{go back to your iphone since you are an android noob}
theunderling said:
That wouldnt void the warranty.
{go back to your iphone since you are an android noob}
Click to expand...
Click to collapse
It depends on how he upgraded to ics, if he did from an official update then is ok, but if he flashed a leaked or a custom rom based on ics then no more warranty if he can't flash the original samsung rom
Already tried changing batteries, didnt work...
You know what to do next then.
I still dont understand the cause of the brick, my phone is dead and it wont even charge. This is bogling my mind. And yeah im an adroid noob, this my first smartphone.

SGS2 bricked while booting up.

Well, first of all, I should start by greeting the community, as this is my first post. So, yeah, hey everybody, been reading the forum for quite a while now, and it's been of a great help
Now, to the problem - this morning I noticed that my sgs2 had turned itself off. I didn't suspect the phone to be bricked or something as this happens from time to time when using custom roms. I tried turning it back on, it booted up, showed my kernels logo (DorimanX, not sure for the version though), so I put my phone in my pocket. After half an hour or so, I wanted to make a call, but I noticed that my sgs2 still hadn't booted up. So I tried restarting my phone using the power button, but instead of restarting it just turned off and I hadn't been able to turn it on since - it's bricked
I've heard of phones getting bricked while flashing a new rom or kernel, but never had I thought it could happen on simply booting up...
I did some research on bricked SGS2 and here's what I have done so far:
I've tried booting up in recovery/download modes, but that doesnt work.
I've tried soft/hard resetting my phone - still no luck.
I've also tried making an USB Jig, didn't work though. I'm not quite sure if my self-made jig works in the first place, as I did mess up the micro usb connector pretty bad while soldering resistors to pins. I'll try that one again with a different jack later and will keep you updated on weather it worked or not.
So, my question is, if my second try at making a USB Jig fails, is JTagging my only chance on reviving the phone? I guess that a MOBO change would probably help.
Another question is, if JTagging is my only chance, wouldn't it be easyer to just replace the bricked NAND chip? Then again, even though I have all kinds of soldering equipment accessible and also have the skills to do it, I have no idea where it's located on the mobo... Some info on that would also be much appreciated.
I havent flashed a new rom for quite a while now, last time I did it was when the latest version of Resurrection Remix was released.
My CPU wasn't overclocked - it was underclocked to 1GHz.
I was using DorimanX kernel.
Thanks in advance
jankanolv said:
Well, first of all, I should start by greeting the community, as this is my first post. So, yeah, hey everybody, been reading the forum for quite a while now, and it's been of a great help
Now, to the problem - this morning I noticed that my sgs2 had turned itself off. I didn't suspect the phone to be bricked or something as this happens from time to time when using custom roms. I tried turning it back on, it booted up, showed my kernels logo (DorimanX, not sure for the version though), so I put my phone in my pocket. After half an hour or so, I wanted to make a call, but I noticed that my sgs2 still hadn't booted up. So I tried restarting my phone using the power button, but instead of restarting it just turned off and I hadn't been able to turn it on since - it's bricked
I've heard of phones getting bricked while flashing a new rom or kernel, but never had I thought it could happen on simply booting up...
I did some research on bricked SGS2 and here's what I have done so far:
I've tried booting up in recovery/download modes, but that doesnt work.
I've tried soft/hard resetting my phone - still no luck.
I've also tried making an USB Jig, didn't work though. I'm not quite sure if my self-made jig works in the first place, as I did mess up the micro usb connector pretty bad while soldering resistors to pins. I'll try that one again with a different jack later and will keep you updated on weather it worked or not.
So, my question is, if my second try at making a USB Jig fails, is JTagging my only chance on reviving the phone? I guess that a MOBO change would probably help.
Another question is, if JTagging is my only chance, wouldn't it be easyer to just replace the bricked NAND chip? Then again, even though I have all kinds of soldering equipment accessible and also have the skills to do it, I have no idea where it's located on the mobo... Some info on that would also be much appreciated.
I havent flashed a new rom for quite a while now, last time I did it was when the latest version of Resurrection Remix was released.
My CPU wasn't overclocked - it was underclocked to 1GHz.
I was using DorimanX kernel.
Thanks in advance
Click to expand...
Click to collapse
What happens when you plug the charger. Does it charge?
pasanjay said:
What happens when you plug the charger. Does it charge?
Click to expand...
Click to collapse
I guess the battery is charging, as it heats up, but I don't see the charging animation. Also my PC won't see that a USB divice of any kind is connected.
jankanolv said:
I guess the battery is charging, as it heats up, but I don't see the charging animation. Also my PC won't see that a USB divice of any kind is connected.
Click to expand...
Click to collapse
order an usb jig and try. If it does not work send it to a repair center
Very similar happened to me a couple of days ago. Sgs2 crashed and wouldn't boot. I was also running dorimanx kernel, under clocked at 1ghz.
Originally I managed to get to download mode (not recovery mode). Kernels wouldn't flash via odin. I also tried using samsung kies to flash stock without success.
I tried the solution for nand bricked phones in this forum, however, this appears to have hard bricked the phone, since it failed to flash and now the phone does nothing (other than get hot when it is plugged in.) Nothing shows on screen. The PC does not recognise the device.
None of the threads I've read seem to offer a solution to this - any ideas? I guess I need to try a service centre, but thought I'd mention since I had same configuration as jankanolv, which of course may just be a coincidence...
birdr said:
Very similar happened to me a couple of days ago. Sgs2 crashed and wouldn't boot. I was also running dorimanx kernel, under clocked at 1ghz.
Originally I managed to get to download mode (not recovery mode). Kernels wouldn't flash via odin. I also tried using samsung kies to flash stock without success.
I tried the solution for nand bricked phones in this forum, however, this appears to have hard bricked the phone, since it failed to flash and now the phone does nothing (other than get hot when it is plugged in.) Nothing shows on screen. The PC does not recognise the device.
None of the threads I've read seem to offer a solution to this - any ideas? I guess I need to try a service centre, but thought I'd mention since I had same configuration as jankanolv, which of course may just be a coincidence...
Click to expand...
Click to collapse
Sounds familliar, lol. Anyways, did you use USB Jig to get to download mode? Or you just managed to boot it up on it's own?
I am really confused right now, because I'm pretty sure this can't be a hard brick as nothing has went wrong while flashing something on the device - it just bricked itself...
I've just get in the forum a few minutes ago only to find somoene with this symptoms, and i wasn't in here for too long and voilá...
Since yesterday my SGII, with no problems to this date, went in reboot mode for a few times.
I have no clue what is going on, but im sure something is.
i'll wait to see if theres anyone else complaining about it.
cheers
Hmm... Looks like a lot of people are getting this "brick" lately.
Maybe we all used some kind of app that bricked the phone on bootup?
Well, I tried to make another Jig, didn't work... This time though, I screwed my resitors up...
Another thing - is it really relevant to have exactly 301kOhm resistance between pins 4 and 5? As far as I know, it just kind of short circuits some pins on MOBO, which tells the phone to boot up in download mode. But I might be wrong...
Btw, sorry for the double post.
Same Problem
Hi,
I just face the same problem today,
now my S2 not working and just heat up.
this only happened after the original update done to my S2 - Android 4.1.2 - 2 days ago.
any help please
heat up....near the rear camera heat up?
Sent from the little guy
Mine gets hot near the camera. Nothing shows on screen.
In answer to jankanolv's questions:
- originally I could get to download mode via pressing home/power/volume down. (Not any more following failed flash). I've not tried a USB jig.
- my crash which started the situation occurred while I was listening to tune in radio pro app.
Well guys....near camera heating + no boot/dl/recovery = claim warranty saying that you factory reset the phone, 4.0.4 was laggy.
Sent from the little guy
was going to post a thread asking for help for what appears to be a similar problem
mine got stuck in a bootloop after pulling the battery, tried flashing new software in recovery then tried through odin but kept failing, now its bricked.
does nothing, wont go into either download or recovery mode so looks like its off to the service centre with it.
ahmadmetwally said:
Hi,
I just face the same problem today,
now my S2 not working and just heat up.
this only happened after the original update done to my S2 - Android 4.1.2 - 2 days ago.
any help please
Click to expand...
Click to collapse
Yessss! good to know I'm not the only one facing this issue.
I posted a thread about this yesterday but it is all the way down in page 3 already:
http://forum.xda-developers.com/showthread.php?t=2192996
I tapped on the "sync" toggle on the notification shade and my phone just turned itself off.
Recovery and download mode were accessible though.
Thanks for the help.
I went to Samsung to get them to fix based on the factory reset while on stock 4.04 premise, but they were having none of it, and wanted to charge me to investigate the problem. Once out of warranty period, it seems it doesn't matter if their software can brick your phone!
I found a local phone fixing service in Hong Kong which investigated, diagnosed as a motherboard failure (which I suspect my problem genuinely was given how firmware flashes were failing), and replaced + fitted for 700hkd, (approx 90usd). The guy did it in front of me within 10 mins. "Andy Telecom" in Mongkok, on +852 9237 9237 in case someone else has the same issue locally.
Well, outta warranty...that's another story. You only get 1-2 years to brick your device
Glad you had it fixed for 90 bucks, some service centers charge around 150.
Sent from the little guy
Well, I finally managed to make a working USB Jig, tried it on Galaxy Ace, worked like a charm.
What confuses me right now, is that my sgs2 has drained all the battery, even though it was switched off for about 2 days. I'm charging the device right now, and I will keep you updated on weather my jig works..
Sorry for double-posting again on an old thread, just wanted to let you guys know - I took the phone to warranty service and they changed the mobo. I didn't have to pay anything and everything is working normally. Of course all data on sd card is now lost for good, lol.
So if you hard brick your device so badly it even won't respond to usb jig and you still have your warranty active, don't bother trying to revive your phone - just take it to warranty service
I guess they couldn't see the odin download count so they cant void my warranty, he he he ]

Categories

Resources