[Q] Dead SGS2 i9100 - Galaxy S II Q&A, Help & Troubleshooting

Hi
I was running SuperNexus 2 on my phone for a few months untill it just got stuck, i removed the battery and restarted, it got stuck on boot several times, so i entered in CWM, flashed the rom again and it stopped working at all. Doesn't enter in download mode or cwm and when charging the battery status doesn't appear (just gets a little hot). It also gets hot in the camera area when the battery is in.
Any help? Thanks

You can click the link in my signature, and go to the section 'No download mode?' and try the things listed there. Some members have managed to 'jump start' to download mode by using the methods listed there.
Unfortunately if there are no signs of life whatsoever after trying those things, and it gets hot around the camera whilst charging, then I'm afraid that's a hard brick = motherboard replacement. Sorry
Sent from a galaxy far, far away

magalhaes.resende said:
Hi
I was running SuperNexus 2 on my phone for a few months untill it just got stuck, i removed the battery and restarted, it got stuck on boot several times, so i entered in CWM, flashed the rom again and it stopped working at all. Doesn't enter in download mode or cwm and when charging the battery status doesn't appear (just gets a little hot). It also gets hot in the camera area when the battery is in.
Any help? Thanks
Click to expand...
Click to collapse
It is not easy to tell if the issue is a brick problem or a hardware issue. First investigate if it is a software problem.
If hardware, there are some sudden death cases known describing exactly what you have. It can occur on any ROM (even stock), usually after 1 year of usage.
http://forum.xda-developers.com/showthread.php?t=1876232
I had the same with mine (stock ICS ROM, after 18 months of usage). First it got stuck several times in heavy 3D games, and one day it suddenly didn't do anything else than getting warm in the camera area. It got fixed for free by Samsung (We have 2 years of warranty in Belgium)

Hopper8 said:
You can click the link in my signature, and go to the section 'No download mode?' and try the things listed there. Some members have managed to 'jump start' to download mode by using the methods listed there.
Unfortunately if there are no signs of life whatsoever after trying those things, and it gets hot around the camera whilst charging, then I'm afraid that's a hard brick = motherboard replacement. Sorry
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Made a Jig and tried everything in your guide... Nothing worked, still dead... Guess I'll have to take it to Samsung... Thanks...
spicyalan said:
It is not easy to tell if the issue is a brick problem or a hardware issue. First investigate if it is a software problem.
If hardware, there are some sudden death cases known describing exactly what you have. It can occur on any ROM (even stock), usually after 1 year of usage.
http://forum.xda-developers.com/showthread.php?t=1876232
I had the same with mine (stock ICS ROM, after 18 months of usage). First it got stuck several times in heavy 3D games, and one day it suddenly didn't do anything else than getting warm in the camera area. It got fixed for free by Samsung (We have 2 years of warranty in Belgium)
Click to expand...
Click to collapse
Yeah, looks like the same thing... We also have 2 years warranty, but mine ended october 5th..., 15 days ago... -_- Thanks for the answer

Related

Samsung Galaxy S II Random Shutdowns

Hi, I've had my SGS2 for around 3 weeks now, and in that period I have had 2 random shut downs.
The first time it happened I was using the original firmware out of the box. The second time it happened (yesterday) I was using the latest firmware via Kies.
The phone is unlocked and unbranded from buymobilephones.net (UK), and I'm on the T-Mobile UK network.
The phone is NOT rooted and I am not overclocking.
Is my phone faulty or is this a software problem? Baring in mind this has only happened twice in the past 3 weeks.
backup data and factory reset would be my first step.
Followed by a return to the store .
jje
JJEgan said:
backup data and factory reset would be my first step.
Followed by a return to the store .
jje
Click to expand...
Click to collapse
Cheers, just did a factory reset. Should I ring Samsung to fix the phone (comes with 12 month warranty) or return it to the online retailer? Not sure what to do.
Just send it off to sammy
Sent from my MB860 using XDA App
... 2 shut downs in 3 weeks?
It's not faulty.
Your contract is with the retailer not Samsung .
I would see if phone restarts again before returning it .
But would inform the retailer of the problem to be within 28 days .
jje
drm111 said:
... 2 shut downs in 3 weeks?
It's not faulty.
Click to expand...
Click to collapse
I've owned several phones over the past 15 years and I've never had such problems before, even with my previous Android the Orange San Francisco. Seriously, if I have a £500 phone I don't expect it to shut down randomly even it it's only twice in 3 weeks. I've missed some important calls and texts because my phone has shut down without me knowing.
JJEgan said:
Your contract is with the retailer not Samsung .
I would see if phone restarts again before returning it .
But would inform the retailer of the problem to be within 28 days .
jje
Click to expand...
Click to collapse
roharia said:
Just send it off to sammy
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Alright cheers, I'll ring buymobilephones.net and see what they say.
beggin said:
Hi, I've had my SGS2 for around 3 weeks now, and in that period I have had 2 random shut downs.
The first time it happened I was using the original firmware out of the box. The second time it happened (yesterday) I was using the latest firmware via Kies.
The phone is unlocked and unbranded from buymobilephones.net (UK), and I'm on the T-Mobile UK network.
The phone is NOT rooted and I am not overclocking.
Is my phone faulty or is this a software problem? Baring in mind this has only happened twice in the past 3 weeks.
Click to expand...
Click to collapse
I think you mean two weeks ago.....
If it continues, you may have a faulty one.
Well I have the same issue, it's in my pocket, next thing when I push the power button the screen just stays black.
Have to hold down the power button to drop it and then restart it.
Sooo, I had this happen once when it was on the table which took the phone in my pocket out the mix.
In the end I tried the battery fix with some geckostrip (that rubber easy removable strip you use on the back of phones to stop them sliding)
I put the strip on the underside (opposite of the connections) and wrapped it around the back (facing the cover).
This makes for a VERY tight snug fit in the unit.
It has now been 2 weeks without one single shutdown...so as much as I thought "this must be software or hardware related", it looks like it very well may be "hardware related" on the battery front.
For those who still have this issue try what I did and let us know your findings.
Cheers
Sheldon
Update: Okay never mind on the battery thing, phone lasted 2 weeks but just blacked out again.....
I had the same problem for many months but it stopped after I uninstallrd dolphin hd browser. No idea if coincidence or not but read a few others with sgs2 and dolphin installed had same problem. Do you by chance have it installed?
Sent from my GT-I9100 using XDA App
I've actually experienced problems similar to this twice now with my SII.
First time was straight out of the box. I charged it up and then took it travelling with me. I kept taking it out of my pocket to find out it had turned off. I thought it was my fault with the power button being in a bit of a silly place. But then it turned off whilst it was lying on my desk or in my hand whilst I was using it. Whenever it turned back on again the battery usage history showed a big sudden drop (10+%) in battery level and then it would increase slowly for a while after. Spoke to O2-UK and they got me to do a software reset and then a hardware reset when it reoccurred, which didn't fix the problem either. They then did a next day replacement.
After I got the most recent update to TW I started to experience times when I'd come to unlock my phone but the screen would stay black. It would, however, give haptic feedback when I pressed the power button but not respond to touch. I recently did a software reset of my phone due to another problem (it kept thinking it was docking this time - but stopped on the day I took it into the O2 Shop) and haven't experienced this since.
For so expensive device I expect only 2 "legal" reasons to shut down while running stock ROM with no additional software or changed hardware (i.e. battery):
1. Battery went completly empty (or as empty as power saving settings allow)
2. I forced it to shut down via power button
If it shuts down on its own under this conditions, first doubt is faulty hardware.
And then it should be quickly replaced by provider/shop/wherever it came from.
Everything else might raise doubt in faulty piece of additional software.
Have had similar issues. Uninstalled the go weather app / widget and nothing since. Might just be a coincidence though.
Sent from my GT-I9100 using Tapatalk
So I've read about this "sleep of death" that sounds like the same thing as what this is.
It appears to affect a wide margin of Samsung devices over time.
One post suggested it was because WIFI activates while the screen is off and the device is in sleep mode, thus blaming the like of apps such as Juice Defender and WIFI managment built into gingerbread.
I have uninstalled gingerbread, enabled watchdog to monitor utilization (out of curiosity) and set the WIFI sleep mode to NEVER.
One day down without a issue, I'll see what happens over the next few weeks.
-Sheldon
I heard that frequent shutdown/reboots happens with 2.3.6 release.
If you got it, better go back to 2.3.5 or earlier. Iit worked for me.
I have 2.3.4 and i get these problems once a month or so.
Wy OH has the same firmware but she gets a random shutdown once a week. We both have the 1900 Anker battery (not stock one) - weird. I am going to try a different ROm and see if it makes a difference.
same issue but after i have deleted à few apps the issue was gone...?
Sent from my GT-I9100 using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
guys im having the same issue too. its happened like 2 times in a month now. it previously happened when i was on 2.3.3 and stock ROM.
today it just happenned again even after being on superatmos 2.1, on 2.3.6.
whats going on?

[Q] Non-rooted I9300 lockups, followed by stuck at boot

First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months. I haven't installed any new apps in a few weeks, but my phone has been doing any regular updates. Today, my phone completely locked up about 5 separate times (about 2-3 hours apart for each). Each time, the only way to get my phone back was by pulling the battery (even the 10+ second press of the power button didn't work)... annoying, but manageable.
After the last lock up, my phone got stuck on the SAMSUNG logo (not the S-III logo). I let it sit there for about 45 minutes, and it was pulsing the entire time. Finally, I gave up and pulled the battery one more time. After putting it back in, the phone gets to the S-III logo, but the S is not pulsing. I've let it sit on that for over an hour - with no luck.
The failed root threads all suggest installing ODIN, rooting, wiping everything, then installing a stock firmware. I'm really hoping there is something else I can try, since wiping my phone would be extremely painful at the moment...
Anyone have any ideas?
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Sadly as this may be, mine derped out exactly like yours one week after I bought it. It would randomly reboot, lag a lot until the day I woke up to that brilliant Samsung boot screen and nothing more helped.
Had not done anything to it so I returned it for a replacement. Turns out I had a faulty unit.
Sorry bro, guessing it's the only thing that will get yours sorted again. While I know in every product there will always be faulty units, I'm seeing dead sgs3 threads very frequently, I'm guessing Samsung's build quality isn't that good...
Sent from my GT-I9300 using XDA Premium App
It might be worth remembering ...
shaunco said:
First off, I have read all of the other soft brick threads on both xdadev and other sites, but all of them seem to address issues that come about as a result of a failed root attempt. My phone is 100% stock, running 4.1.1, and has been working great for months.
...
Click to expand...
Click to collapse
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
JJEgan said:
Backup data factory reset and wipe >>> Or return phone to a service centre .
jje
Click to expand...
Click to collapse
I would love to backup my data, but since I had a stock bootloader (not CWM or one of the others) and the PIT seems gone, I'm SOL.
xclub_101 said:
It might be worth remembering that there ARE a certain percentage of faulty units - those are all covered by warranty
It is also worth pointing out that accuracy can be a ***** - there is no "normal" Galaxy S3 that 2 or more months ago was running 4.1.1 - so if you indeed have 4.1.1 that is as a result of some (probably OTA) upgrade at some point in that interval
Click to expand...
Click to collapse
Yeah, bad wording on my part. When I bought it (the first day Amazon sold the I9300), it had 4.0.4. It has had 4.1.1 since mid-October. My comment of it "working great" was in relation to the random lockups (and now the stuck at logo issue).
Lucky for me, the phone is a work phone, so I bought a new I9300 at Fry's this morning and at least got my service and all my apps back, along with the data for the apps that were nice enough to put it on the SD...
This means my focus has shifted from returning my old I9300 to a working state to simply getting data off of it. If the bootloader shows "no product", it seems that the partition table is shot. Loading a new partition table would destroy the underlying data... so, is there anything I can do (even things that are physically destructive to the phone) to get the data (even as a single binary blob) off the internal 16GB storage?
As I said, I'm happy to rip this thing to pieces, if there is a way.

Phone freezes randomly..every 5-10 mins..On different ROMS/safe mode.stock Rom..

Hi
I was running on Omega v38 past few days, and my phone was running great.
Few days back my phone got totally stuck once, but a reboot fixed it.
Today I upgraded to Omega 40, and my phone started to freeze every few mins.
So I megawiped, and reinstalled it.
My phone got frozen in the set up screen itself.
Megawiped and installed Foxhound.it ran great for few minutes and gets frozen every 5-10 mins.
So I mega wiped and reinstalled Omega 38.
Same problem. Even during searching for Titanium backup, the phone got frozen.
By frozen, I mean the screen won't respond or turn off.
Only a reset would solve the issue.
I've also noticed that the phone is getting too hot during it.
Any fix?
Could it be an indication to SDN issue?
that's really strange have you wiped system during the "megawipe")) ?
i guess the only solution is to return to stock via odin and than flash again
Triangled Away
Flashed Stock Rom
Still the problem persists.
Even in Safe Mode.
eggman89 said:
Triangled Away
Flashed Stock Rom
Still the problem persists.
Even in Safe Mode.
Click to expand...
Click to collapse
Having the same problem over here, tried numerous roms (OMEGA v37-v40, CM10.1, Resurrection) no luck at all. Phone keeps randomly freezing. So I decided to go back to stock and unroot (for warranty reasons). Without any problems I unrooted my device, and installed a stock JB rom from my country (Netherlands). Traingle away, worked like a charm, but still, when installing apps and settings, I got random freezes, even on stock (official rom). As you said as well, screen would not respond, no hardware keys either. So decided to return it for warranty, and get a new phone/repaired hardware. Woke up, phone still running (very surprised), used it throughout the day, only a random reboot in the late evening and a single freeze. I really don't get how this bug/hardware problem works... Going to see what happens next couple of days, before returning for warranty... I also tried other tricks, such as in this thread: http://forum.xda-developers.com/showthread.php?p=37432509 not sure if it helped, but it sure looks that way. I also check if my EMMC was insane (http://forum.xda-developers.com/showthread.php?t=1993044&page=388) And it is, not sure however if this is related, because the sudden death problems mention not booting at all.
Good luck, keep us posted on your progress.
CrashyNL said:
Having the same problem over here, tried numerous roms (OMEGA v37-v40, CM10.1, Resurrection) no luck at all. Phone keeps randomly freezing. So I decided to go back to stock and unroot (for warranty reasons). Without any problems I unrooted my device, and installed a stock JB rom from my country (Netherlands). Traingle away, worked like a charm, but still, when installing apps and settings, I got random freezes, even on stock (official rom). As you said as well, screen would not respond, no hardware keys either. So decided to return it for warranty, and get a new phone/repaired hardware. Woke up, phone still running (very surprised), used it throughout the day, only a random reboot in the late evening and a single freeze. I really don't get how this bug/hardware problem works... Going to see what happens next couple of days, before returning for warranty... I also tried other tricks, such as in this thread: http://forum.xda-developers.com/showthread.php?p=37432509 not sure if it helped, but it sure looks that way. I also check if my EMMC was insane (http://forum.xda-developers.com/showthread.php?t=1993044&page=388) And it is, not sure however if this is related, because the sudden death problems mention not booting at all.
Good luck, keep us posted on your progress.
Click to expand...
Click to collapse
My phone has finally died (SDS) after few days of random freezing.
Gave it to service center. They replaced it with a new Motherboard which is of 32 gb . :victory::victory:
eggman89 said:
My phone has finally died (SDS) after few days of random freezing.
Gave it to service center. They replaced it with a new Motherboard which is of 32 gb . :victory::victory:
Click to expand...
Click to collapse
eggman, can you let me know which service centre in bangalore. I got my mobo replaced for an audio issue. They gave me a new Mobo with 16GB and the bad eMMC chip. Having lots of freezing issue.
cheers,
Vince

SGS2 bricked while booting up.

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 ]

[Q] Frustrated with desire x

I have posted before too on this issue of random reboots on desire x. It seems that i am the only one who have faced random reboot problem multiple times a day( varies between 1-10).
Now i would like to explain my issue in detail. These restarts DOES NOT occur when i am using the phone and running multitude of apps.
It only occurs when the phone is lying idle or when charging. Sometimes it reboots with white HTC screen while sometimes it gets stuck on a black screen( not switched off), in latter case i have to long press the power button to reboot it again. I can't even leave my phone alone while charging because it may crash which will result in missed calls and messages. The phone worked fine for first 4 months of purchase so may not be hardware related. I did upgrade my software twice from 1.18.401(factory) to 1.18.720 . the latest update was 1 week before the problem started.
I did not spent my $400(Indian price) on buying a buggy phone which bothers me and left me wondering why is it behaving so strangely.
The trouble shooting i performed in last month includes -
FACTORY RESETTING 5 TIMES
RUNNING PHONE WITHOUT SD CARD
RUNNING WITHOUT ANY APPS INSTALLED
PUTTING A WEDGE ALONG BATTERY TO ENSURE GOOD CONNECTION
SCRUBBING BATTERY AND PHONE CONTACTS
USING PHONE ON SEVERAL SIM CARDS
The problem may be network related, i don't know.
I am so disappointed in HTC. Is anybody here on software version 1.18.720 and not facing problem of reboots. If the update is faulty HTC should come up with another one.
I am on a sabbatical and 300 miles far from nearest service station for another month.It makes no sense to cover 300 miles and spend hell lotta money just to get this goddamned thing serviced. My last hopes are on Jelly Bean update to solve this problem which seems to take forever in coming to Asia. Is there any way to go back to 1.18.401 which came natively with my phone or some other way to resolve it.
Thank You
Get it replaced in Warranty. THE JB UPDATE WONT SOLVE THIS ISSUE. As it is specific to some users and not others, so its not a SOFTWARE issue. Its Hardware Fault. Get it replaced ASAP.
Regards
Yasir
neXus PRIME said:
Get it replaced in Warranty. THE JB UPDATE WONT SOLVE THIS ISSUE. As it is specific to some users and not others, so its not a SOFTWARE issue. Its Hardware Fault. Get it replaced ASAP.
Regards
Yasir
Click to expand...
Click to collapse
yea i still have 6 months of waranty left.. but the phone ran well for full 4 months before the update....so was wondering
rocky00001 said:
yea i still have 6 months of waranty left.. but the phone ran well for full 4 months before the update....so was wondering
Click to expand...
Click to collapse
Let the warranty guys wonder why the issue happened. Its a costly thing, and warranty is EXACTLY for these type of situations. USE it.
Just save yourself the hassle and get it replaced like nexus suggested if you dig into what the causes are it will take a while because i tried to with an older htc device
Jb wont solve it, if its kinda similar to my problem described in your previous thread, motherboard change is the only option
thanx everybody . so that means i will live with this faulty device for sometime more till i go back to my work place n have access to service station
rocky00001 said:
I have posted before too on this issue of random reboots on desire x. It seems that i am the only one who have faced random reboot problem multiple times a day( varies between 1-10).
Now i would like to explain my issue in detail. These restarts DOES NOT occur when i am using the phone and running multitude of apps.
It only occurs when the phone is lying idle or when charging. Sometimes it reboots with white HTC screen while sometimes it gets stuck on a black screen( not switched off), in latter case i have to long press the power button to reboot it again. I can't even leave my phone alone while charging because it may crash which will result in missed calls and messages. The phone worked fine for first 4 months of purchase so may not be hardware related. I did upgrade my software twice from 1.18.401(factory) to 1.18.720 . the latest update was 1 week before the problem started.
I did not spent my $400(Indian price) on buying a buggy phone which bothers me and left me wondering why is it behaving so strangely.
The trouble shooting i performed in last month includes -
FACTORY RESETTING 5 TIMES
RUNNING PHONE WITHOUT SD CARD
RUNNING WITHOUT ANY APPS INSTALLED
PUTTING A WEDGE ALONG BATTERY TO ENSURE GOOD CONNECTION
SCRUBBING BATTERY AND PHONE CONTACTS
USING PHONE ON SEVERAL SIM CARDS
The problem may be network related, i don't know.
I am so disappointed in HTC. Is anybody here on software version 1.18.720 and not facing problem of reboots. If the update is faulty HTC should come up with another one.
I am on a sabbatical and 300 miles far from nearest service station for another month.It makes no sense to cover 300 miles and spend hell lotta money just to get this goddamned thing serviced. My last hopes are on Jelly Bean update to solve this problem which seems to take forever in coming to Asia. Is there any way to go back to 1.18.401 which came natively with my phone or some other way to resolve it.
Thank You
Click to expand...
Click to collapse
i am on 1.18.720.3 and have faced no problems whatsoever yes sometimes i have random restarts but that is a very rare case like once in a month you should probably get it fixed via service centre :good:
djranbhir said:
i am on 1.18.720.3 and have faced no problems whatsoever yes sometimes i have random restarts but that is a very rare case like once in a month you should probably get it fixed via service centre :good:
Click to expand...
Click to collapse
maybe you too, I had very similar issue on desire, restarted firstly once in month, once in week, several times a day, ended up with totaly useless pocket clock, anything else caused restart
myusernamewastoken said:
maybe you too, I had very similar issue on desire, restarted firstly once in month, once in week, several times a day, ended up with totaly useless pocket clock, anything else caused restart
Click to expand...
Click to collapse
ditto.it started once in week types but now the frequency is pretty constant n not progressive.. might be that we are few of unlucky ones.
i called htc few days back they told me flashing rom should fix it
restarted again within 10 mins i used it as wifi hot spot..sick of this thing....
I do not have access to a service centre for next 1 month
rocky00001 said:
restarted again within 10 mins i used it as wifi hot spot..sick of this thing....
I do not have access to a service centre for next 1 month
Click to expand...
Click to collapse
Thats awfuly bad luck... cant you send it via mail to service centre? In czech republic, there is this posibility (and we are around monkeys level here in whole smartphone situation).
I also have 720.3 but don't have such problem.
That's absolutely a hardware problem,take it to service center asap n dont wait for jb update.
sent from my HTC DX
myusernamewastoken said:
Thats awfuly bad luck... cant you send it via mail to service centre? In czech republic, there is this posibility (and we are around monkeys level here in whole smartphone situation).
Click to expand...
Click to collapse
YEA may be i can but that will take forever in India to get a proper response from main htc office/SC that is 3500 miles away. I will be in bangalore in may/june so will directly go the main service centre myself. Additionally I don't think they will replace the phone immediately so sending over mail will be useless if i get the same phone back with some temprory tweaking from their side.
I have 6 months of warranty left till November so if it goes bad let it be, my case will get stronger.
Can i flash my phone back to 1.18.420 myself without voiding warranty.?
In future i will think twice before going for HTC
i read somewhere in forums that android phones also need to cool down for sometime and periodic reboots or what they probably meant is switching off the phone for few mins is essential for long life of the phone but may be its just me
djranbhir said:
i read somewhere in forums that android phones also need to cool down for sometime and periodic reboots or what they probably meant is switching off the phone for few mins is essential for long life of the phone but may be its just me
Click to expand...
Click to collapse
thats old desire trick called "put that brick into freezer", but it doesnt help in long term, youll have to cool it whole time youre using it
RANDOM REBOOTING devices with STOCK ROMs have FAULTY HARDWARE.
I phone shouldnt reboot on heat even with extreme use, and if it does, its faulty.
If you have custom roms or kernels, then it might be due to software issue, but on STOCK, its always HARDWARE.
rocky00001 said:
I have posted before too on this issue of random reboots on desire x. It seems that i am the only one who have faced random reboot problem multiple times a day( varies between 1-10).
Now i would like to explain my issue in detail. These restarts DOES NOT occur when i am using the phone and running multitude of apps.
It only occurs when the phone is lying idle or when charging. Sometimes it reboots with white HTC screen while sometimes it gets stuck on a black screen( not switched off), in latter case i have to long press the power button to reboot it again. I can't even leave my phone alone while charging because it may crash which will result in missed calls and messages. The phone worked fine for first 4 months of purchase so may not be hardware related. I did upgrade my software twice from 1.18.401(factory) to 1.18.720 . the latest update was 1 week before the problem started.
I did not spent my $400(Indian price) on buying a buggy phone which bothers me and left me wondering why is it behaving so strangely.
The trouble shooting i performed in last month includes -
FACTORY RESETTING 5 TIMES
RUNNING PHONE WITHOUT SD CARD
RUNNING WITHOUT ANY APPS INSTALLED
PUTTING A WEDGE ALONG BATTERY TO ENSURE GOOD CONNECTION
SCRUBBING BATTERY AND PHONE CONTACTS
USING PHONE ON SEVERAL SIM CARDS
The problem may be network related, i don't know.
I am so disappointed in HTC. Is anybody here on software version 1.18.720 and not facing problem of reboots. If the update is faulty HTC should come up with another one.
I am on a sabbatical and 300 miles far from nearest service station for another month.It makes no sense to cover 300 miles and spend hell lotta money just to get this goddamned thing serviced. My last hopes are on Jelly Bean update to solve this problem which seems to take forever in coming to Asia. Is there any way to go back to 1.18.401 which came natively with my phone or some other way to resolve it.
Thank You
Click to expand...
Click to collapse
You remember me about my old Mio A701 phone who started to behave strange for month or two... and after that the radio chip crashed...
Also it happend on my wife's LG phone that a little dirty (mettalic I think) on circuit inside right behind the power plug was able to freeze the phone and some times to restart.
So, if you tried all that things and the problem is not solved then it is a hardware problem! You have to disassemble the phone and repair it! Or go to service center (never I had).
its not a heat problem coz .i can use this device for prolonged sessions. only when the screen is off and network on it reboots
PS. when is jb coming to India
Try one more thing there is a app(don't know name) which can increase the minimum processor frequency
Try that out may be your CPU has very low min speed, don't sure about this but give it a try.
If that requires rooting then don't do it.
sent from my HTC DX

Categories

Resources