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.
Related
Hi - I'm using a Galaxy S3 right now and it's not powering on at all. Battery is guaranteed not empty as it has been on charge all morning. It's rooted and running SuperNexus - I9300 - BUILD 4.
I can't even get into download mode - tried powering on with volume keys held up and/or down along with home key and power key but no luck
I've called Samsung and they will take it away for warranty repair but my worry is if they know it's rooted - will they refuse to fix it?
I'm clutching at straws but has anyone got any other suggestions I could try?
I imagine you already tried this, but when it happened to me last, I simply took the battery out for a few and put it back in, then it fired up. Has only happened to me once though.
NMonster69 said:
I imagine you already tried this, but when it happened to me last, I simply took the battery out for a few and put it back in, then it fired up. Has only happened to me once though.
Click to expand...
Click to collapse
yeh it's been out for a few minutes. Maybe i should try it for a little while longer.
One thing I forgot to mention is that sometimes I would pick up the phone to look at something and the screen would be blank but the soft keys would be lit up. The only way to get the screen back was to keep the power button pressed down for 10 seconds or so so that it switched off and then back on.
This is what happened this time - but only this time it's refusing to come back on
5aq1b said:
yeh it's been out for a few minutes. Maybe i should try it for a little while longer.
One thing I forgot to mention is that sometimes I would pick up the phone to look at something and the screen would be blank but the soft keys would be lit up. The only way to get the screen back was to keep the power button pressed down for 10 seconds or so so that it switched off and then back on.
This is what happened this time - but only this time it's refusing to come back on
Click to expand...
Click to collapse
There's a known issue with some devices having problems with this in here:
http://forum.xda-developers.com/showthread.php?t=1993044
But if your device was starting to have problems before... maybe it wasn't related to motherboard but something else, maybe even software related... But still, if the device is not powering at ALL you should be good with samsung, as they will just replace the motherboard and thats all (at least some ppl had it repaired even rooted and with CM installed on the thread I linked above.
Good luck and share your adventure with the SAT (if you finally send it there) on the other post
If your in the eu then rooting your phone won't affect the warranty. It's been confirmed a few times in the thread posted above. It sounds to me like another mother board failure.
Sent from my GT-I9300 using Tapatalk 2
MuertoKo said:
There's a known issue with some devices having problems with this in here:
http://forum.xda-developers.com/showthread.php?t=1993044
But if your device was starting to have problems before... maybe it wasn't related to motherboard but something else, maybe even software related... But still, if the device is not powering at ALL you should be good with samsung, as they will just replace the motherboard and thats all (at least some ppl had it repaired even rooted and with CM installed on the thread I linked above.
Good luck and share your adventure with the SAT (if you finally send it there) on the other post
Click to expand...
Click to collapse
thanks mate! Pardon my ignorance, but what's 'SAT' ?
I think i'll be sending it off to http://www.freesamsungrepairs.com/ because of their turn around time!
Raverlee said:
If your in the eu then rooting your phone won't affect the warranty. It's been confirmed a few times in the thread posted above. It sounds to me like another mother board failure.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
thanks - just a pain in the arse, especially this time of year. Gutted that i'll have lost a few pictures as i didnt change the settings to store pictures on external storage And i've lost all my notes!
did a backup with titanium backup though!
Does anyone know how to restore it so that your folders and layout are preserved?
5aq1b said:
thanks mate! Pardon my ignorance, but what's 'SAT' ?
I think i'll be sending it off to http://www.freesamsungrepairs.com/ because of their turn around time!
Click to expand...
Click to collapse
Technical service
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 ]
So I was charging my phone, and it restarted itself and now it's stuck in a bootloop!
I can't access download mode or recovery, it keeps restarting before I have the opportunity to press any buttons (hardware or on screen) and removing the battery does nothing either, as soon as I put the battery back in, the phone resets without me even pushing the power button
I'm using Temasek CM11 v8 with the "201113-1248-cm11-i9300-r3p2-linux30101-BOEFFLA-temasek" kernel
Is it recoverable?
I've managed to get it into both Recover and Download mode briefly, but both times the phone restarted within a few seconds back to the bootloop
Sounds like the power button is shorted out, fairly cheap repair if so.
Sent from my GT-I9300 using Tapatalk
Thanks for the reply. What makes you think that it's the power button shorting?
Holding power button for 5 seconds acts as a hard reset, everywhere.
That's a good starting point actually. There's no reason for download mode to reboot automatically. If it loaded then it waits for the events. Either it works until you do anything with a PC, or doesn't work at all.
hi
try using a universal battery charger and then try again
JustArchi said:
Holding power button for 5 seconds acts as a hard reset, everywhere.
That's a good starting point actually. There's no reason for download mode to reboot automatically. If it loaded then it waits for the events. Either it works until you do anything with a PC, or doesn't work at all.
Click to expand...
Click to collapse
Ah Well I suppose that makes it pretty conclusive. 2 hours later and it's still bootlooping... I'd take it apart but I don't really know what i'm looking for and I suspect if it's shorting, something will need replacing or soldering etc. Thanks very much
eltonpestana said:
try using a universal battery charger and then try again
Click to expand...
Click to collapse
I don't think I have one, I shall check though. Thanks very much
The issue of having it shortly resetting once reinstalled the battery sounds to me like a hardware failure, most probably hard resetting all the time.
A hardware repair should help fix this.
tweetatoo said:
The issue of having it shortly resetting once reinstalled the battery sounds to me like a hardware failure, most probably hard resetting all the time.
A hardware repair should help fix this.
Click to expand...
Click to collapse
It's funny you say that, after hours and hours of trying to get my phone to work, somehow through more luck than judgement I managed to get it into recovery and flash WanamLite 7.2 (I figured it was the next best thing to stock, as I couldn't access download mode) and well... since then, touch wood my phone hasn't restarted itself even once... now granted in that time i've only touched the power button once, to turn on the device, but it seems like progress to me
So my question is, is it possible that I could of had a bad flash or something? It seems too coincidental to me, and I don't actually think the different ROMs have anything to do with the problem (that is still lingering beneath I suspect), but the optimist in me REALLY wants it to be fixed haha
EDIT: Oh and thank you tweetatoo for your reply
So my question is, is it possible that I could of had a bad flash or something? It seems too coincidental to me, and I don't actually think the different ROMs have anything to do with the problem
Possible its the well known multipleromflashed problem .
JJEgan said:
So my question is, is it possible that I could of had a bad flash or something? It seems too coincidental to me, and I don't actually think the different ROMs have anything to do with the problem
Possible its the well known multipleromflashed problem .
Click to expand...
Click to collapse
Interesting, thanks. It's just a bit confusing, it seems plausible because I flashed the ROM earlier in the day but at the same time, im not sure how much control the new ROM would have over the phone entering Download Mode... Mind boggling.
I'll keep an eye on it for a bit... and im still too scared to use the power button haha
Thanks very much
Download mode is entirely separate to the rom, I still think your power button shorted out (stuck down) as it's been reported many times before. If you have warranty then now would be the time to triangle away and return to stock for a while, just in case.
Sent from my GT-I9300 using Tapatalk
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk
Hi there! Long time reader, first time poster (TL;DR below...but it should be a quick read anyways )
So I've been using this S2 of mine for almost 4 years now, haven't had any trouble (other than a couple of battery swaps). For the past 6 months or so I've been using CM 12.1 nightlies without issue.
The events:
- The other day, my phone froze (I wasn't using it when it froze, it was when I went to use it that I noticed...it was on the wifi selection screen if it matters), so I held the power button to shut it down, and when I powered it back up, it just froze at the Samsung boot screen (with the usual yellow triangle).
- At this point, I was able to reboot into download mode at will, but any attempt to boot to recovery just led to the freeze at the Samsung boot screen. Also, the phone would automatically reboot itself at this point any time I inserted the battery (I was of course putting the battery in and out trying everything I could).
- I would have reflashed from Odin at this point, but since I was away for a few days I just kept trying to reboot into recovery, to no avail. On one of these attempts (power+vol up+ home) it showed the Samsung boot screen, and then immediately shut down and I haven't been able to get anything onto the screen since
I'm now home, and I can't seem to fix it. If I plug the phone into a charger, the top half or so of the phone gets warm, and it also seems to get warm if it isn't plugged in and I try to power it up. I was thinking maybe the phone was maybe doing the same thing as before and just not showing anything on screen, but I blindly do the steps to get it into download mode, and Odin doesn't recognize anything (drivers are definitely installed). I have also tried other batteries, no luck.
Any ideas of what I might try? I'm willing to do anything. For the record nothing happened to the phone at all when this all happened (no dropping or water damage or anything, just my attempts at booting into recovery). Maybe I should try a jig? I'm also open to opening the phone if there's something I can do, though I don't have experience with this.
Thanks so much for any suggestions!
TL;DR: phone froze (running CM 12.1 nightly), held power to shut it down, and then consistently froze at the boot screen on any attempts to power it on. After a few attempts at booting into recovery (the phone would only freeze or enter download mode) the screen suddenly shut off and I haven't seen anything on it since no matter what I try. I can't think of anything that happened to the phone I'm open to any and all suggestions! Thanks
One sentence amongst your description stands out like a 'sore thumb'.....
That the device heats up towards the top when you attempt to charge it.......
Until you try a jig I can't be certain, but that heating coupled with a dead/unresponsive screen along with a lack of recovery and/or download modes (download mode is 'hardwired' into the device, and NOTHING should be able to corrupt it) are the primary symptoms of a failed motherboard.......
That is my opinion based on my experience in these forums and personal experience with a (now dead) S2 (one of two that I own).........
Get the jig just to be sure, but I'd be surprised if it had any effect.....sorry to be typing something you don't want to read, but you said it yourself, the device is 4 years old....it's been in service roughly twice as long as most smartphones, and they don't last forever....
http://i.imgur.com/rVnFwJM.jpg
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
smacsmac said:
Thanks dude! It's nice to have some idea of what happened. I am indeed very happy my phone has lasted me this long, and my friend is gonna give me an extra S2 she has anyways it seems so it's all good!
I'll try the jig and update here with the result (I ordered one online...will arrive in January sometime)...just in case anyone is curious.
Click to expand...
Click to collapse
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Yeah....be good to know the results.....If only to confirm or refute what I've suggested.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sorry it took me a while...the jig was in the post haha. It didn't do anything at all (no response when I plugged it in) so I think it's safe to say you were bang-on and the motherboard failed! Happily using a new S2 (with CM13.0 now ) on behalf of my friend though.
Thanks again.
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Elaias said:
Sounds familiar. Happened to me also due to failed cyanogenmod update (CM13). Only thing that works is download mode, so i'm not given up hope yet.
I can't post a link but google ''Apply Update Failure samsung galaxy s II'' there's a thread about this on the cyanogenmod forum.
Click to expand...
Click to collapse
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Its hard to tell you and hard to accept. You can almost give up the hope, your NAND Chip is just what we call " wear-out ". In the most cases no write is possible anymore, the funny part is -> sometimes read is still fine. If that is the case: The system is booting and working, but saving just nothing. The NAND is frozen to its state before it broke.
At our local store, customers come to us with issues like " Factory Reset impossible ", "Can't delete my Files" "Can't create files". All these Devices have inaccessible NAND's and inaccessible Recovery. Only Bootloader is working, but as the NAND is broken, flashing doesn't change anything.
smacsmac said:
oh mine was just straight up dead...no download mode or anything visible on the screen (and nothing to do with CM13 either)
hope you get yours sorted out! have you tried reflashing anything via Odin while in download mode?
Click to expand...
Click to collapse
yeah, flashing with odin did the trick. now running cm13 and everything works fine. sorry to hear that your phone turned to brick.