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
Related
i am using resurrection remix 3.0.6 with siyah kernal 4.1.5. i believe rr 3.0.6 is still not stable due to sudden lag spike. it happen so suddenly, my screen just freeze. so i make the option to pull out the battery and re-insert the battery to reboot the phone.
then it happen, it doesn't seems to be able to boot up my primary rom which is the RR 3.0.6, i try to boot up secondary rom, which happen to be the same RR 3.0.6, but nothing, the phone auto shut down. i still can go into recovery mode using 3 button combo, then i try to wipe cache, but still the same, not able to boot up RR 3.0.6.
i am very frustrated already, i choose to reinstall the ROM by doing a factory wipe/data wipe, but the data wipe thing just stay there for very long... the worst thing happen. i pull out my battery again. this is when all hell break lose... i can't on my phone, can't do 3 button combo, usb jig no use. simply nothing, like a dead fish.
however, i realise my phone started to heat up around the camera area with the battery in it... that mean a sign of life? anyone face this problem and manage to revive the phone without sending to jtag?...
This is why i am afraid of rooting GS2. GS1 was soo easy...
its not the rooting process that break my phone, its the ROM. rooting doesn't give me trouble, just 2 min using zergrush.
my phone can do nothing but heat up when the battery is put in...
Aha.. zergrush? You suggest me to not flash this rom?
Somebody know how to help this guy?
Answer
Well same kind a thing happen for me little different but yeahhh almost the same. Apparently I burn up my motherboard, that might be the warm up around your camera. Anyway still to early to say something but my suggestion is before you do anything take it to the Samsung customer service, if they can bring your phone alive then you can do it as well, but if they come up with no then you have no choice but to order new motherboard.
Hope it helps..
thanks for your suggestion... sounds like doom day... how much is the motherboard cost?
Well I just received mine today. I find a guy on ebay and you sell your bricked motherboard for 50$ bucks and you can get yours for 130$ bucks.
I install it today and works perfectly fine. But again just check with the Samsung Service then do what you need to do.
---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------
Well I just received mine today. I find a guy on ebay and you sell your bricked motherboard for 50$ bucks and you can get yours for 130$ bucks.
I install it today and works perfectly fine. But again just check with the Samsung Service then do what you need to do.
same here.
installed resurrection remix rom and when install rebooted phone it would not turn on. dead. So I sendt my phone inn to my provider (only had it for under a year), and from the service log they have changed the mainboard.
I have the same problem guys...
Last night my phone gone dead..
It is still in warranty..
Is there any chance from the service to deny the warranty?
(maybe they can see if it was rooted etc..?)
I'm so so sad.....
alexisgt said:
I have the same problem guys...
Last night my phone gone dead..
It is still in warranty..
Is there any chance from the service to deny the warranty?
(maybe they can see if it was rooted etc..?)
I'm so so sad.....
Click to expand...
Click to collapse
There is no way can know that. Try your luck. they will most likely accept it
Jokesy said:
There is no way can know that. Try your luck. they will most likely accept it
Click to expand...
Click to collapse
I hope so..
Thanks for your reply! It gave me hopes! :good:
Hi People of the world! As you can see im new to here so yeah i just might be in the wrong section...
So, I just got my shiny android a week ago, and know it sits on my desk, lifeless, like a brick. Like literally its dead! I don't know if I can fix it or the BIOS (if theres one in Samsung Galaxies) is fried, or maybe the motherboard is fried, or the battery overcharged, etc. But I just cant do anything! I'm totally out of ideas!
Heres the problem, I first rooted my android successfully, and played around with my android a while. But as you expect I just coudn't wait for the jelly bean update! So, I desided I would give a try to take the Russian firmware instead. That was already a bad idea, but I read on some threads that it would work fine, so I downloaded one from Sammobile.com. The real mistake? I downloaded the wrong phone. I own a Samsung Galaxy S Advance NFC Version;GT-I9070P The one I downloaded was UnNFC version; GT-I9070. Well, I didn't realize that, and proceeded with entering download mode and eventually flashing the PDA file from Sammobile with ODIN. So I pressed start. It started the process, and after 5 min it said in blue: RESET. I saw the phone rebooting. Now, another big mistake: I started touching the power button, which I shouldn't have done. Then, instead of waiting, as soon as seeing the thing wasnt booting, I took out the battery and unplugged the USB cable. Then after a while the PASS appeared in green. So it went successfully? NONONO Now it wont boot! More specifically, it wont TURN ON! like it wont whow any sign of life. As if it had no battery or USB.
Today I discovered, If I hold Vol UP+Power+Home when its connected to my PC, it makes the beep, shows that it failed to install the driver for "U8500 USB ROM" What the (*^&(&%*(&^&* is that??? Also, in 5 seconds, the device disappears, meaning that I must hold the button combo for another 20 seconds.
So, I've got no connectivity to ODIN, nor Kies, and I cant go into download mode, nor recovery mode.
Any Help?
Pleeaase if you can help youre a super god of androids!
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
MikeSome1 said:
ok, so if I understand correctly, You can't even turn on a phone - no samsung logo, no yellow triangle, nothing, right?
Click to expand...
Click to collapse
Exactly. Nothing at all.
The only evidence that its not fried is that the computer detects it as U8500 USB ROM for 5 seconds whenever i hold the power button or any combination. Nothing on the phone though.
Hey
Hey man got the same problem... I have put mine to a service center i will see what the'll do
pafiking said:
Hey man got the same problem... I have put mine to a service center i will see what the'll do
Click to expand...
Click to collapse
Yeah i think I should take it to service too, but I want to try at least first:cyclops:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Lynnfield4000 said:
I've just repeated exactly the same steps as the OP on my GT-9070P and have "successfully" bricked my two-week-old phone. If someone happens to find a solution, please share. :crying:
Click to expand...
Click to collapse
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
Please help! I also bricked my Samsung S Advance I9070P after downgrading from JB to GB, since JB was updated for India I9070...but the phone bricked after downgrade. Everything was successful and it had auto-rebooted after the downgrade and stuck with Start up screen. When I removed battery and tried again..it bricked! No recovery mode, No download mode, no power on.
Surge411 said:
Ikr its really bad to break your phone as soon as i get it. Worse, for me its a few of days to my birthday! Worse thing that could happen. I will PM you if i happen to find a good solution. Also, to make it really the worst thing, the GT-I9070 is one of the less popular phones (not like the s3). The NFC version? Even rarer! So not only are there not many developers working for that phone, not many people have really encountered problems with the phone at all.
Surge
Click to expand...
Click to collapse
So you find any solution? I have a similar problem right now.
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.
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 ]
Rom- s5 sensations version 7
I was using my phone for the past two weeks with no problem, all of a sudden today it would not unlock, I held down the power button then a screen with all these different colours came up
It eventually went away and the screen went black again
Now nothing works it ill not power on and LED wont come on when charging
Can the phone have been hard bricked after 2 weeks of installing the custom rom? :/
Thanks in advance
XDA Visitor said:
Rom- s5 sensations version 7
I was using my phone for the past two weeks with no problem, all of a sudden today it would not unlock, I held down the power button then a screen with all these different colours came up
It eventually went away and the screen went black again
Now nothing works it ill not power on and LED wont come on when charging
Can the phone have been hard bricked after 2 weeks of installing the custom rom? :/
Thanks in advance
Click to expand...
Click to collapse
Hi! This herna from XDA Assist.
Well, normally if you did not touch any deeper thing in your ROM you should have no problem if you have been using it for as much time. Anyway this question should be done in the above thread, so I will move it there so you can get a better reply from people using the same device or even the same ROM than you.
http://forum.xda-developers.com/galaxy-s3/help
I will move it to the original place where it should be, and wish you to get the answer you are waiting for.
Try usb jig to force download mode, if that doesn't work then it sounds like a brick -sorry.
boomboomer said:
Try usb jig to force download mode, if that doesn't work then it sounds like a brick -sorry.
Click to expand...
Click to collapse
I just dont understand how it could be bricked after being perfectly fine for 2 weeks and i had been using it like 5 minutes before no problem :/
Blame the emmc chip, it is very fragile and can go pop at any moment.
Try reading the dead boot recovery thread in general forum.