I recently had a problem with my XDA 1. It started running VERY VERY slowly (kind of like a computer that was infected with 10000 spyware programs). The battery was constantly showing that it was going to shutdown but yet seemed to still operate.
I tried doing a backup to SD Card while it was on the cradle, yet after about 4 minutes of usage it would automatically soft reset - interrupting the backup.
So i thought stuff it, i don't care about the data i will just do a hard reset. Now, after doing the hard reset i can't even get it to turn on. The O2 Screen comes up and the light flashes on and off every few seconds. It does this for about 45 seconds then switches off again.
Does it sound like the mainboard is gone? Could it just be the battery? Are there any home repairs ideas? I do have a second xda i can pull apart if i must to test what is wrong with this one.
Thanks.
Adrian
boot problem
if a desktop pc were to exhibit these sort of problems then i would definitely suspect a motherboard problem. if you are still under warranty then straight back to the store is the place for you. if not then scour the forums for solutions fixes or suggestions, there are some very experienced people on here - not me -
ian
since it's still under warrenty I strongly advice to replace it or at least to get it repaired by the center ... but if you tend to feel it's a challenge for you to fix it your self, then you may do the following to eleminate the possibility of S/W problem ...
1. Flash the ROM with a new OS image. This should solve any ROM problem.
2. Make sure you didn't turn on the "Calib/Debug" option in the GSM menu of the boot loader.
BTW, was the radio part OK while having this problem ?
actually its not under warranty, i bought it off a friend when he upgraded to his XDA II. Im not sure what the radio version was, i jsut put any details in there because i couldnt boot to find out what it was at.
Can you flash the rom without having to boot it up? Are there the instructions on how to do it on this site?
Thanks.
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.
Ok, so heres the deal. The s2 is my sisters phone, and she comes home and told me the phone wont turn on, that its stuck on the boot screen and it just keeps turning off and doing it again. So I started looking into it (Im an iPhone user, so I'm not too familiar with android devices. BUT I do know a bit about computers, cell phones and just technology in general). I ended up finding out that its stuck in a soft brick. So I started youtubing how to fix it. Found a great method using Odin3 and Samsung Kies. AND IT WORKED. I turned the phone back on, got past the lock screen and everything was all good.
After about 30 seconds, THE PHONE BRICKED AGAIN:crying:. And it went right back into the boot loop, I cant get it into download mode because it just keeps restarting after a couple of seconds. With that happening, I cant get the computer to recognize it so I can do a recovery fix with Samsung Kies. I legit cannot find any solution to it.
The thing that baffles me and is causing me a huge headache is the fact that THE PHONE IS NOT ROOTED. nothing has been done to it, its completely stock. So if there is no solution to it, can somebody at least tell me what might have been able to cause this?
Thanks to all,
Dariel
Well, you're in the wrong forum for the SGH-T989. That's probably your issue.
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 ]