Yesterday my battery died half way through playing a game (not entirely unexpected, I'd been playing on my phone quite a bit that day and it still lasted 22-23 hours), I connected the charger that came with the phone and left it to charge while I got on with some uni work.
The phone vibrated to tell me the charge was complete so I disconnected the charger and turned the phone on as usual. After the samsung galaxy S2 splash screen, the screen lock appears and when I move it there are several error messages saying that various applications have had to stop (the main one seems to be TwLauncher but when I force close it, many others also force close). This continues for several seconds until the phone decides to restart itself and repeats the process ad infinitum until I can shut down the phone (I can manage this by not trying to get rid of the screen lock and just holding the power button until the menu appears).
I've had this phone a week (one of those days being today where it did not work at all) so it's still well within the return period but I was wondering if there is an obvious fix that I'm missing.
If not, I'll be ringing Samsung on Monday (I have coursework due for friday so I'll be devoting my samsung office hours time to that) and if they can't give me an easy fix I'll be ringing the place I bought it from and asking for an exchange.
So, has anyone else had similar issues and managed a simple fix?
Bump, I take it everyone else's phone is working then?
Giving this another bump in the hopes there's someone with a simple solution.
I don't want to have send my phone off and wait for the place to get stock.
there have been 2 firmware releases from samsung in the last couple of days, i assume you are running the latest firmware?
I can't even get the phone to stay on long enough for Kies to recognise it. It keeps restarting. Even when it was working I couldn't get Kies to work with it properly (I couldn't copy the contacts from the phone to the computer).
It's running the firmware it came with, but I can't check which version it is.
I was going to try flashing the new firmware via ODIN but I've been busy with coursework. Is this likely to solve the issue or will I just be giving the retailers ammo to reject my return?
go into recovery and do a factory reset
psp888 said:
go into recovery and do a factory reset
Click to expand...
Click to collapse
this is what I was looking for.
after googling, this sorted it out.
I just assumed download mode was the only other non-normal mode.
Thanks
Basic FAQs on the SGS1 forum mostly apply to SGS2 .Worth a look there before Google .
jje
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 everyone,
I have a stock Verizon Galaxy S4 that is having some issues and wont stay on and sometimes gets caught in a bootloop. I have been able to get into recovery and wipe cache / do a factory reset, but the phone keeps doing the same thing; reboot, sometimes start but then reboots again. I have had it for almost 2 years and thought it was the battery, so I bought another one and the phone still does the same thing. If I boot into safe mode, it lasts a little longer that way, but will eventually turn off and get caught into the bootloop again.
Any ideas on what the cause is and possibly how to fix it? The is completely stock and has never been rooted, unlocked, or anything like that. I looked in the forums, but it looks like they all have to do with flashed roms and non-stock options, which is why I am posting a new thread.
All help is appreciated. Thank you.
It sounds like your power button may be on its way out. I had the same issue with my phone. Couldn't get it to boot past the splash screen. If your is intermittent it may or may not be this issue. However if the problem gets worse, its more then likely the cause. After a lot of use the insulation inside the power button can wear away causing a short. If you google it there are several articles describing symptoms to help figure out if that is indeed the problem. If you run in to a boot loop, pull the battery and reinsert it. If the phone powers on without pressing the power button, that is your problem.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Eclipse ROM fatness!
MyColorScreen
I know it has been a few weeks but I wanted to provide an update. I have a friend who runs a cell phone repair shop. I took it to him and they did all sorts of tests and such, so we replaced the power button. After replacing the button, the phone still did the same thing.
I would pull the battery, but the phone would not turn on by itself. I would power on the phone like normal and would make it to the splash screen in which the phone would then power off. At that point, it would not try to restart, but rather would act like it was on and the phone / battery would get really hot. I would pull the battery and start again, with the same result.
Any other ideas? My friend, the co-owner of the business, and myself are all out of ideas.
Thanks!
Edit: Also I called Verizon and Samsung to see if I could work out a warranty through either of them. Since the phone is almost 2 years old, we all know the answer to that. Sammy wanted $70 just to look at it, let alone additional charges to fix it if the problem wasnt what they thought it was.
poda13 said:
I know it has been a few weeks but I wanted to provide an update. I have a friend who runs a cell phone repair shop. I took it to him and they did all sorts of tests and such, so we replaced the power button. After replacing the button, the phone still did the same thing.
I would pull the battery, but the phone would not turn on by itself. I would power on the phone like normal and would make it to the splash screen in which the phone would then power off. At that point, it would not try to restart, but rather would act like it was on and the phone / battery would get really hot. I would pull the battery and start again, with the same result.
Any other ideas? My friend, the co-owner of the business, and myself are all out of ideas.
Thanks!
Edit: Also I called Verizon and Samsung to see if I could work out a warranty through either of them. Since the phone is almost 2 years old, we all know the answer to that. Sammy wanted $70 just to look at it, let alone additional charges to fix it if the problem wasnt what they thought it was.
Click to expand...
Click to collapse
I have to say I'm shocked its not the power button. My only other suggestion would be to flash the stock firmware to the device using Odin. It could be a software problem. Your guess is as good as mine. However flashing the stock image is definitely cheaper then hassling with Sammy or big red. Not that voiding your warranty would matter at this point but make sure you flash whatever firmware your on right now. If you go backwards you may run into a problem since your phone has the Knox boot loader. Check out the i545 android development section here at XDA for tutorials on how to do so. There are a few of them out there. I'm not completely familiar with that process since I'm still on MDK firmware. But there are plenty of knowledgeable guys that can help you on those threads if need be. Good luck!
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
149ThemedGoogleKeyboards!!!!!!
Eclipse ROM fatness!
MyColorScreen
Well, I ended up selling it for $130 to some one for parts. I made full disclosure of what the phone was doing and even showed the buyer exactly what it was.
My father had an older Droid X2 that we are using for the time being. Our contract ends in less than 30 days in which we will be moving to T-mobile anyways. I get literally zero signal where I work and my wife gets very limited service where she works. However, the T-mobile service is excellent in both our respective buildings and in the Phoenix metro area where we live.
I appreciate your thoughts on trying to resolve this. One of the many reasons why I love XDA and the community.
Hi everybody i am asking for advice on trying to repair a phone for a family member the phone is a galaxy alpha F variant UK stock rom, factory unlocked and unrooted the problem started after finishing a call the handset was left un attended and when it was later picked up the screen was black but does not appear broken aywhere and does not appear to respond to touch
i have tried un successfully to get it into recovery or download modes the handset turns on and the blue lights come on and you can hear the start up tone but see nothing on screen, it also charges and i have tried a new battery, odin does recognise a device but as i cant get it into download i cant flash a stock rom which i have already downloaded.
So my question is, is there any software that i can download to diagnose whether or not the screen is dead or whether it is a f/w issue or is there a way around this where i can use a different tool to get into the handset and flash a new stock rom in case the current f/w is corrupted
Thanks in advance for any useful help and advice
Please understand that i am a newb to this so if i have made some mistakes or my questions have been answered elsewhere previously i do apologise
I think it seems pretty obvious that the problem is the display itself
Hi BigHands,
I faced a problem having the exact same symptoms as yours twice in the last few month: screen was staying black but phone reacted to some "external" actions (ON/OFF), blue light.
Not sure what happened exactly, but removing the battery and trying to restart the phone finally brought the device back to life after trying more than than 10 times!!!
So in my case, the display was probably not the (only) root cause.
Really weird however that I needed to reboot the phone >10times to make it work: usually when software is screwed either one single power cycle will bring the device back to life or it will never power up again!
Anyways, a FW issue is still a possibility considering the number of bug this phone has (for the price it was sold, that phone is definitely the worse gadget I ever owned!)... But it seems there is a bunch of FW updates on going on this model accross the world, so there is still a little hope things might improve... Samsumg may have woken up; who knows...
JF
So this is an old problem, and I'm kind've just hoping someone knows what's wrong with the phone even though it doesn't really matter anymore, because I'm genuinely curious. So a few years ago, I was running an unofficial CM12 build on my Sprint Galaxy S4, and I'd been using the ROM for about two months, give or take a few weeks. One day I just took a picture, and it turned off. But I couldn't turn it back on. And I still can't.
I've tried charging it, it's charged but it wont boot the main ROM, it wont recovery, it wont boot download mode/bootloader, it wont boot into safe mode. My laptop doesnt register it when i connect it through USB either (of course) so can't do anything with the laptop. It just shows "Samsung, galaxy S4" and just turns back off. If I want to make another attempt at powering it on in any way, I have to take out the battery and try again.
If anyone has any idea how to fix it, or AT LEAST what's wrong with it (again, I have a fully functional Note 5, I don't NEED the S4 to work) I would really appreciate the help. Thanks in advance.