Hi guys, my galaxy s3 international i9300 just bricked today. I've been running phenomenal 4.0 extreme with ARHD 11.0 for a couple of weeks.
Phenomenal Extreme:
cpu arm : -125mv to all freq
cpu internal: -50mv to all freq
bus: -100mv to all freq
gpu: -100mv to all freq
It turned off all of a sudden and I can't turn it back on. Can't enter download mode or recovery either. The screen simply does not turn on. LED indicators don't turn on either.
Tried a USB Jig (that works on my old galaxy S1) and it doesn't work either. Phone remains dead. What can I do?
I intend to claim for warranty if all else fails, but it's already been flashed on a custom rom and I can't reset the flash counter.
If the screen doesn't turn on at all, you can try a new battery
The battery was at 90+% when the phone died. Happened this morning an hour after I unplugged it...
Unfortunately I don't have a spare battery with me. Now I'm back home again and I plugged it in. It seems to be charging (the battery has heated up). Will try the jig again after an hour of charging.
I wish I could help you buddy, does your PC recognise your device?? If so try booting into download via adb. If not then the service centre is your only option. It shouldn't matter whether its been modified or not because if its not turning on Samsung will just wipe and flash it, they only tend to check the status of the device if hardware is messing up. Or you could try taking the battery out and leaving it out for a few mins then put it back in
Sent from my GT-I9300 using xda premium
speedyjay said:
I wish I could help you buddy, does your PC recognise your device?? If so try booting into download via adb. If not then the service centre is your only option. It shouldn't matter whether its been modified or not because if its not turning on Samsung will just wipe and flash it, they only tend to check the status of the device if hardware is messing up. Or you could try taking the battery out and leaving it out for a few mins then put it back in
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Just tried - PC does not detect the phone. Well, seems like I need to head to the service centre then. In this case though, isn't my phone hardware messing up? I can't even turn it on.
I must admit I never knew undervolting could screw up the phone.
viscy said:
Just tried - PC does not detect the phone. Well, seems like I need to head to the service centre then. In this case though, isn't my phone hardware messing up? I can't even turn it on.
I must admit I never knew undervolting could screw up the phone.
Click to expand...
Click to collapse
The phone doesn't need anything like that in my opinion, I only go as far as rooting and flashing....no CPU overclocking or GPU undervolting. By phone hardware I meant the screen, battery, volume buttons, modem etc, it seems you have messed up internals I.e processor or gpu . Head to the service centre buddy. Sorry I can't be more help.
Sent from my GT-I9300 using xda premium
Sry for you mate, but have you underclocked - overclocked after flashing kernel or died ur phone with changing anything to this kernel?
Sent from my GT-I9300 using xda premium
josefmawas said:
Sry for you mate, but have you underclocked - overclocked after flashing kernel or died ur phone with changing anything to this kernel?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Hey. I installed the kernel without doing any other modifications.
galaxy s3 turn to zombie mode
i flash my galaxy s3 with phenomenal kernel after one day working and overclocking gpu at first the sound of GS3 runs with glitching and badly noise turn off s3 and turn it on again but when gs3 goes boot up no sound at all after 4th or 5th resets at bootup my cell shows vertical lines and pink background and freeze
and the cell compeltly dead and no respond to power or downloading or recovery mod or power charging amaing things at this situation when i warming may cell , phones power on with sound and overclocked to 1704mhz and 6890 quadrant score and when cell going to cold back to freezing sound glitching and back completly to dead iam so confused with this galaxy s3
flashed with stock with pit file and without pitfile
flashing with bootloader but no success
Hey, don't think your situation is the same as mine. I did not overclock or in any way modify the kernel settings after installing phenomenal 4.0. My phone is currently with the service centre and I will report back when I find out if the warranty claim is successful.
The service center personnel outright told me that rooting will void the warranty and I still have no idea if it is possible for them to check if I indeed had flashed my S3. I did not reset the flash counter before it completely went unresponsive on me.
Fingers crossed that the warranty claim will be successful...
ill sent my cell to warraty but reject me becuase my phone was rooted and told me we can replace your damaged board with new board but u must pay 500$ :0
at the end of this story i boaught another GS3
last week i gift new galaxy s3 to my wife and bought galaxy note2 ang galaxy note 10.1
but damaged galaxy s3 stay with me some days warmed and tunred on automatically and i hear bootup sound
I got the exact situation as yours. But i installed Wanam.
My phone bricked just 30 minutes after flash.
I was clueless. But after i did some googling & reading forums, now i know.
It was my mistake.
I checked the md5, and it clearly stated as "Unmatched", yet i flashed it anyway.
The ROM booted fine. Installed TiBu, and proceed to restore apps.
So, 30 mins after flashing, my phone died.
Now my phone's at Samsung Service Centre. Expected to finish repair in 2 days.
Sent from my Transformer Prime TF201 using Tapatalk 2
Related
Hello,
I think I have hard bricked my galaxy s2 GT-I9100 (France)
It was working well with the official Kies ICS update.
I installed Sygic Navigation Trial app from Play Store.
Then I started Sygic. It asked me to select maps to download.
I selected some and started download.
When download reached 1800M over 2400M my phone suddenly stopped working. The screen was freezed.
There was no response either from the home key neither the power button.
I removed the battery.
Now the phone doesn't start anymore. There is nothing on the screen. No samsung logo, no battery indicator. No sound. No vibration.
Could someone please help?
I suggest you send it to samsung service center
Sent from my GT-I9100 using xda premium
You tried charging it first for 10 mins atleast?
Sent from My Samsung Galaxy S2 running Paranoidandroid Rom.What else if not?=P
Did you tried download mode, or recovery?
Sent from my GT-I9100 using xda premium
sqbaannyy said:
Did you tried download mode, or recovery?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes I have tried all key combinations.
The phone had just been charged all night before.
...
So many SIIs dying due to weird reasons recently, dafuq? Mine died twice already! First time was fixed with a free new battery from sammy but now its dead again...... same reason i think. I let the battery run from 100% to 0% and now its dead Battery dont wanna charge no boot no screens no vibrations... Something is wrong in there...
I still cannot power on my sgs2.
What I have noticed is that when I let the battery in the phone, 10 min after I can feel some heat like if the CPU is working at 800mhz.
I think that the phone is endlessly trying to boot, but resets even before reaching the first samsung logo.
My fear is that the mmc chip is corrupted. I heard there was bugs in the emmc firmware with the wear leveling.
...
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
So I got my phone yesterday. It was running on 4.1.1 iirc(not sure, it was a version of JB though), device told me it needed an update but I didn't have the time to update.
Now today, as I'm returning home I'm playing a game when the phone gets really hot. Now I don't mean normal warm, almost unbearable to touch the bottom third of the phone for longer than a couple of seconds.
I closed all the apps and let the phone rest to cool down. Couple minutes later I want to turn the screen on to check the time and it just doesn't respond. I remove the battery, try turning it back on, no response.
I tried charging it, thinking the battery might have suddenly died(even though it was at 20%) but the red charging light doesn't even show up. I'm not sure whether it's the sudden death issue or something else.
Will I be able to fix this by myself, or will I have to get the phone to a service center? I just got it so naturally I don't want to lose it, but I've read that even a usb jib won't get a device like this in download mode.
Thanks in advance!
Edit: Phone is normal international version, I didn't root, using stock rom. Basically I didn't do anything except install apps and set up some accounts. The phone doesn't react to the vol down+menu+power combination, no matter in which order I hold the buttons.
Sudden death, Samsung will change the motherboard for free
Thanks. Any idea on how long it might take to get the phone back? Will I have to bring it to the store where I got it(not a Samsung service center) or send it to Samsung?
Take it to store. The repair should last a few weeks or so.
Sent from my GT-I9300 using xda premium
UrbanDrawer said:
Take it to store. The repair should last a few weeks or so.
Click to expand...
Click to collapse
Oh dear god.
Biglia05 said:
Oh dear god.
Click to expand...
Click to collapse
If you only got it yesterday demand a replacement.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
corrsea said:
If you only got it yesterday demand a replacement.
Sent from my SGS3 using Tapatalk
ROM Sotmax Ultimate V14
Kernel Yank555.lu-V3.1c
Click to expand...
Click to collapse
Cheers, will do that tomorrow.
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 ]
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: