Motherboard replacement procedure - Galaxy S III Q&A, Help & Troubleshooting

I have a 16GB Galaxy SIII GT-I9300 international.
A few days ago it started repeatedly rebooting. The reboot frequency increased until it would not reboot at at all.
I tried a number of fix suggestions. None worked.
None of the software/firmware fixes will work because the phone simply won't switch on.
I believe the problem is with the motherboard memory. The phone is a month out of warranty so I don't think Samsung will fix it for free. Besides, I opened the case.
I'd like to know exactly how I can can make sure I order the right replacement board and and what other steps I need to take to get phone working. Fortunately I have a full SD card backup

TEXT to large cannot read it .
jje

Related

HELP! No Call Audio & Call Disconnects

Symptoms:
- On making a call, starting from today (really yesterday), I get no audio going in or out. However both speakers are work fine, because the earpiece makes a beep sound to let me know call forwarding is active. The rear one works for everything.
- Headphones in call don't work either
- Sometimes I get sound for one call until I hang up, or it's very crackly and
useless.
- While ringing when dialing out (or rather, when you WOULD be hearing ringing if it was working), sometimes it'll cut the call and say "OUT OF SERVICE AREA", and then I'll get the circle with the line through it where signal is supposed to be. Signal is back seconds later.
- Data and texting work fine.
Things I've tried:
- I was on Omega ROM 13.1 with Siyah 1.5.3, although I've read online people have this issue bone stock, unrooted.
- Flashed stock insecure kernel
- Flashed several different modems
- ODIN'd back to the ROM that came with the phone (was originally a real-SIM-unlocked, Vodafone Germany i9300).
- Wiped everything possible
I'm willing to donate via Paypal to whoever has a definitive fix for this problem. It's really driving me insane that I don't have a working phone for calls. Worst case I'll call Samsung, but I expect they'll charge me an arm and a leg, if they even accept it considering it's from Germany originally (bought it off Amazon in June). This seems like a software issue, not a hardware issue consider both speakers still physically work fine. The issue is, what the hell is causing it if it came about completely randomly, and is happening across all ROMs, kernels, and modems that I flash?
Before you ask, no the Accessibility Setting for turning off all sounds is not on.
Thanks in advance for anyone that replies.
I use omega rom and I've had this a lot, I found that restoring the apn using titanium backup caused the problem, so I now use a apn backup app. Sometimes flashing the modem twice, clear cache, fix permissions helps. I always got call audio if I flashed back the base Rom. On ics, I could flash modems Willy nilly and 90% would work, not so on jelly bean. However, on omega v25 I can flash any modem and it works. Lh4 is about the best modem for me,
After flashing Rom (with full wipe), check call audio, make 1 change at a time so you know what removes sound. You may have to clear cache/fix permissions after certain changes.
Sent via TCP/IP
gsw5700 said:
I use omega rom and I've had this a lot, I found that restoring the apn using titanium backup caused the problem, so I now use a apn backup app. Sometimes flashing the modem twice, clear cache, fix permissions helps. I always got call audio if I flashed back the base Rom. On ics, I could flash modems Willy nilly and 90% would work, not so on jelly bean. However, on omega v25 I can flash any modem and it works. Lh4 is about the best modem for me,
After flashing Rom (with full wipe), check call audio, make 1 change at a time so you know what removes sound. You may have to clear cache/fix permissions after certain changes.
Sent via TCP/IP
Click to expand...
Click to collapse
It just happened totally randomly (as in it began totally randomly). Flashing the ROM again helped for one or two calls. Then back to square one. Tried everything possible including wiping and restoring the EFS. I'm not sure what kind of issue this is because the speaker itself works and so do data and texting, but not calls.
Sent from my GT-I9300 using xda premium
Well try downloading your region modem as I have experienced that problem when I was on xxxxDl12. try "15". If it doesn't help, then your region modem for your device should do the trick
Sent from my GT-I9300 using xda app-developers app
nasdiemx said:
Well try downloading your region modem as I have experienced that problem when I was on xxxxDl12. try "15". If it doesn't help, then your region modem for your device should do the trick
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I'm in the US so there's no regional modem. But I've tried every modem and none have solved the issue. And this issue came up after 4 months of no issues. I'm hoping there's no hardware issues.
Sent from my GT-P7510 using XDA Premium HD app
Product F(RED) said:
I'm in the US so there's no regional modem. But I've tried every modem and none have solved the issue. And this issue came up after 4 months of no issues. I'm hoping there's no hardware issues.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
Product F(RED), did you get a solution to this issue? i'm having the /exact/ same thing with my i9300 in the US. I'd also be willing to donate to whom ever documents a solution for this issue. I'll supply any information or do any action (short of bricking the phone) to fix it..
I had to ship it to the sellers on Amazon (who are in Germany, where the phone came from originally), and they shipped it to Samsung for repair, and then back to me. Samsung in any EU-member country (including the UK) will repair a Galaxy S3 from any other EU country, and my S3 has a 2 year warranty instead of 1. It was a hardware component failure (not sure which) which required a new motherboard.
Guess what. It's happening again. I don't know what to do. I don't have the time or money to keep shipping this thing abroad to get it fixed. -_-
Ok, is anybody still monitoring this situation? I have had this exact same problem which has plagued me now for about 2 months. The story is bizarre:
My phone was a blue i9300 which I bought factory unlocked at my local **** Smith retailer in July 2012. It worked just fine for months, then this audio problem surfaced, precisely as described here. I googled for solutions and tried various "fixes" which apparently worked for other people but had no effect for me. These escalated in invasiveness until I had flashed CWM and several ROMs with several versions of modem. None had any effect whatever. By this time, I decided it must be a hardware issue, so I spent the next week of my spare time trying to erase what I'd done so I could do a warranty claim. Finally I got TriangleAway to work and flashed it with I9300XXEMB1_I9300OXAEMB1_BTU stock UK system. To outward appearances, the phone looked original. Everything was fine, except for the original audio problem.
Meanwhile, I found a white S3 on ebay with a broken screen and I bought it for the motherboard, which I thought would fix the problem with the blue one and remove the need for warranty claim, as I still wasn't sure I'd covered my tracks well enough. The broken handset arrived and I carefully swapped the motherboard over, put the SIM in and made a call. I was horrified to find the exact same problem. Everything worked fine, except no audio on calls.
Now what was I going to do with this broken handset I just bought? It was worth nothing as it was, so I began looking on ebay for a new screen for it. Found one and ordered it. I had already decided that the fault must be on the screen half of the phone rather than the motherboard. While I was waiting for the screen to arrive, I took the original blue phone to **** Smith, explained the problem to them and asked them to send it to Samsung for me for warranty. This they happily did. I put my SIM in my Bauhn 3G tablet and have been using it as a phone (better than nothing) in the meanwhile.
The screen for the white one arrived yesterday and I sat down and carefully installed it. Put in the SIM and rang my landline. You guessed it, no audio. Exact same problem. WTF? This can't be happening. But it is. What do I do now? What are the chances of these two handsets having exactly the same fault? The white one has its original firmware XXBLH3. I haven't messed with it at all other than changing the screen. It can't be the SIM card as it works ok in the tablet. I am lost. HELP!
Edit: Just did an OTA upgrade, it is now 4.1.1 XXDLK1 Audio problem remains the same.
slurpy1 said:
Ok, is anybody still monitoring this situation? I have had this exact same problem which has plagued me now for about 2 months. The story is bizarre:
My phone was a blue i9300 which I bought factory unlocked at my local **** Smith retailer in July 2012. It worked just fine for months, then this audio problem surfaced, precisely as described here. I googled for solutions and tried various "fixes" which apparently worked for other people but had no effect for me. These escalated in invasiveness until I had flashed CWM and several ROMs with several versions of modem. None had any effect whatever. By this time, I decided it must be a hardware issue, so I spent the next week of my spare time trying to erase what I'd done so I could do a warranty claim. Finally I got TriangleAway to work and flashed it with I9300XXEMB1_I9300OXAEMB1_BTU stock UK system. To outward appearances, the phone looked original. Everything was fine, except for the original audio problem.
Meanwhile, I found a white S3 on ebay with a broken screen and I bought it for the motherboard, which I thought would fix the problem with the blue one and remove the need for warranty claim, as I still wasn't sure I'd covered my tracks well enough. The broken handset arrived and I carefully swapped the motherboard over, put the SIM in and made a call. I was horrified to find the exact same problem. Everything worked fine, except no audio on calls.
Now what was I going to do with this broken handset I just bought? It was worth nothing as it was, so I began looking on ebay for a new screen for it. Found one and ordered it. I had already decided that the fault must be on the screen half of the phone rather than the motherboard. While I was waiting for the screen to arrive, I took the original blue phone to **** Smith, explained the problem to them and asked them to send it to Samsung for me for warranty. This they happily did. I put my SIM in my Bauhn 3G tablet and have been using it as a phone (better than nothing) in the meanwhile.
The screen for the white one arrived yesterday and I sat down and carefully installed it. Put in the SIM and rang my landline. You guessed it, no audio. Exact same problem. WTF? This can't be happening. But it is. What do I do now? What are the chances of these two handsets having exactly the same fault? The white one has its original firmware XXBLH3. I haven't messed with it at all other than changing the screen. It can't be the SIM card as it works ok in the tablet. I am lost. HELP!
Edit: Just did an OTA upgrade, it is now 4.1.1 XXDLK1 Audio problem remains the same.
Click to expand...
Click to collapse
OK that's the most insane thing ever. I can't frigging believe it.
I've had this issue for a month and a bit and it's driving me insane. Worst of all it goes and comes back without any apparent reason. Today it started again. I've done all the exact things you did, changed modem firmware, installed cyanogenmod, everything in the phone works fine except I get no audio in calls and suddenly call drops and signal goes out of service for a few seconds.
After hearing about your case I don't know what to do. I have an insurance with the phone company that covers theft, I am thinking about it.....
well same thing happened to me , i was in a different country for one month and when i went back this started. i have no idea whats going on.
It's a hardware issue. You need to send it to Samsung for motherboard replacement.
Product F(RED) said:
It's a hardware issue. You need to send it to Samsung for motherboard replacement.
Click to expand...
Click to collapse
sorry, was logged on with my friend's account.
so i bought my phone on august 20th last year, from amazon, do i even have a warranty? how am i supposed to replace it?
thanks! how much would that cost?
thanks alot
holydire said:
sorry, was logged on with my friend's account.
so i bought my phone on august 20th last year, from amazon, do i even have a warranty? how am i supposed to replace it?
thanks! how much would that cost?
thanks alot
Click to expand...
Click to collapse
You have to message the seller. I bought mine from amazon too and it came from Germany. I had to pay $80 and wait like 3 weeks to ship it there and get it back.
Sent from my SGH-I337
holydire said:
sorry, was logged on with my friend's account.
so i bought my phone on august 20th last year, from amazon, do i even have a warranty? how am i supposed to replace it?
thanks! how much would that cost?
thanks alot
Click to expand...
Click to collapse
Vendor for warranty or Samsung give an additional 24 month warranty that is limited as per .

Low/No connectivity from repaired S3

Hi All,
I had to get my S3 repaired by Carphone warehouse recently, they replaced the entire LCD screen.
So before I had it repaired the phone would connect to my home wifi while I was in my room, but since having my phone repaired I can't connect from my room anymore. When I'm near the wifi, 5-6m away the phone will connect fine.
Could they have done something during the repair which has stopped it working? Or could it be something else?
Ah also on the rare occasion that my phone picks up my home wifi when I try to connect I get an authentication error...
Thanks for any help
Deep
Could be several things, you didn't say why the screen was replaced -dropped? Aerial module damaged or not properly connected, software updated.
You'd probably be best to take it back and describe the problem.
First delete and remake your wifi settings to the router .
Fails then restore your Nandroid or factory reset fails return the phone .
boomboomer said:
Could be several things, you didn't say why the screen was replaced -dropped? Aerial module damaged or not properly connected, software updated.
You'd probably be best to take it back and describe the problem.
Click to expand...
Click to collapse
The sensitive buttons on the bottom of the phone had stopped working. That was the only issue with the old phone
JJEgan said:
First delete and remake your wifi settings to the router .
Fails then restore your Nandroid or factory reset fails return the phone .
Click to expand...
Click to collapse
Done that
Looks like it'll be another trip to CPW tomorrow.
Bit annoying as this is my second S3. Bought one in May last year and early this year the phone kept restarting, CPW 'fixed' it but the issues remained to they gave me a new one in April time.
Sent the brand new one off for repair just last week for the problem with the touch screen buttons.
Both phones were in excellent condition, no marks or drops! This has really put me off buying another Samsung phone unfortunately
Haven't with worked on the s3 but on many of the other galaxy phones the WiFi reception is extremely poor with the back removed... Seems the actual antenna is mounted in the back and contacts the main board when the back is installed. It's possible that those contacts got bent or something when the back was off.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[Q] Samsung S3 mini cannot read simcard after suspected virus download

Hi guys
Hope someone can help! After ignoring advice from the Antivirus I picked up it appears a virus, my Samsung S3 mini does not read simcards anymore. The Antivirus told me my IMSI number has been changed, giving me the new and old ones. A motherboard replacement and a firmware upgrade did not solve the problem. I hope my phone is still fixable! Thanking you in advance for your help....
Certainly did not get a virus. Especially one that would persist across a motherboard swap. Which, I am a bit confused on... So you did a motherboard swap and have the same exact issue? That could only happen if they swapped the SIM card reader from the old board to the new and that is the faulty part. Other than that, check to see if your IMEI is correct or still there. If the EFS partition gets messed up, it can cause issues like this...but not across motherboard swaps either.
So either someone told you they swapped motherboards and lied to you, or they swapped a bad part over along with it.
thank you
es0tericcha0s said:
Certainly did not get a virus. Especially one that would persist across a motherboard swap. Which, I am a bit confused on... So you did a motherboard swap and have the same exact issue? That could only happen if they swapped the SIM card reader from the old board to the new and that is the faulty part. Other than that, check to see if your IMEI is correct or still there. If the EFS partition gets messed up, it can cause issues like this...but not across motherboard swaps either.
So either someone told you they swapped motherboards and lied to you, or they swapped a bad part over along with it.
Click to expand...
Click to collapse
The repairshop said they changed the motherboard, so i don't suspect them of lying....and i did the firmware upgrade....
charles101 said:
The repairshop said they changed the motherboard, so i don't suspect them of lying....and i did the firmware upgrade....
Click to expand...
Click to collapse
Well check the IMEI from behind the battery and in the phone, see if they match. You didn't answer whether or not the IMEI was still there either. And if they actually did change the motherboard, that would be why you would have gotten the message the 2nd time around, if the app had saved your info from before and you restored it. Why are we trusting this anti-virus app anyway? They are known to point out stuff that isn't there or relevant. If they don't report anything, people think there's no reason to install them...
Also, did the repair shop charge you for the motherboard swap and gave you back the phone not working still with the same issue? Something just seems really off about this. I do repairs for a living and couldn't imagine that going down in that manner at my shop.
hi
es0tericcha0s said:
Well check the IMEI from behind the battery and in the phone, see if they match. You didn't answer whether or not the IMEI was still there either. And if they actually did change the motherboard, that would be why you would have gotten the message the 2nd time around, if the app had saved your info from before and you restored it. Why are we trusting this anti-virus app anyway? They are known to point out stuff that isn't there or relevant. If they don't report anything, people think there's no reason to install them...
Also, did the repair shop charge you for the motherboard swap and gave you back the phone not working still with the same issue? Something just seems really off about this. I do repairs for a living and couldn't imagine that going down in that manner at my shop.
Click to expand...
Click to collapse
Hi Es0
I did not enquire too much at the repair shop, they just told me that a motherboard swop did not fix the fault and i accepted it at the time. The IMEI number matches except the slashes in the number at the back of the battery don't appear in the IMEI number displayed on the screen. The repairshop charged me not a cent and the phone came back same as i took it in...
charles101 said:
Hi Es0
I did not enquire too much at the repair shop, they just told me that a motherboard swop did not fix the fault and i accepted it at the time. The IMEI number matches except the slashes in the number at the back of the battery don't appear in the IMEI number displayed on the screen. The repairshop charged me not a cent and the phone came back same as i took it in...
Click to expand...
Click to collapse
Ah ok. They just swapped yours back in afterwards it would seems. But there's no way that the other motherboard would do the same thing unless it was broken in the same way and/or they were using the same SIM card reader, which of course, wouldn't make any sense and would defeat half the purpose of swapping it in the first place. I think you need a second opinion from another shop.
You've tested it with other cards as well?
Put your card in another phone to make sure that is still functioning properly?
When you look in the Settings / About Phone / Status - Does it show the phone # and ICCID #?
Do you get a 0 with a / through it at the top for the signal?
Hi Es0
es0tericcha0s said:
Ah ok. They just swapped yours back in afterwards it would seems. But there's no way that the other motherboard would do the same thing unless it was broken in the same way and/or they were using the same SIM card reader, which of course, wouldn't make any sense and would defeat half the purpose of swapping it in the first place. I think you need a second opinion from another shop.
You've tested it with other cards as well?
Put your card in another phone to make sure that is still functioning properly?
When you look in the Settings / About Phone / Status - Does it show the phone # and ICCID #?
Do you get a 0 with a / through it at the top for the signal?
Click to expand...
Click to collapse
The card works fine in a Samsung Pocket at the moment. By # do you mean number ( sorry i am not up with the jargon...) ? Card in the Pocket now and by "my phone number" says "unknown". I don't see any reference to ICCID on either phone! And am not sure where to look for the 0 with a / through it !! Sorry if i am trying your patience here....
charles101 said:
The card works fine in a Samsung Pocket at the moment. By # do you mean number ( sorry i am not up with the jargon...) ? Card in the Pocket now and by "my phone number" says "unknown". I don't see any reference to ICCID on either phone! And am not sure where to look for the 0 with a / through it !! Sorry if i am trying your patience here....
Click to expand...
Click to collapse
I mean your telephone number. If the card reader was not working at all, it would not be able to pick up your # off the card to display in the Settings / About Phone / Status part. But it is weird that the card in your other phone reads unknown. Have you tried another SIM in the phone in question? It could just be that the SIM card is being weird. I've seen them work on some phones and not others. The 0 with / would be in the Status Bar for the signal bars - next to the battery icon, etc.
Have you modded the phone at all?
Hi Es0
es0tericcha0s said:
I mean your telephone number. If the card reader was not working at all, it would not be able to pick up your # off the card to display in the Settings / About Phone / Status part. But it is weird that the card in your other phone reads unknown. Have you tried another SIM in the phone in question? It could just be that the SIM card is being weird. I've seen them work on some phones and not others. The 0 with / would be in the Status Bar for the signal bars - next to the battery icon, etc.
Have you modded the phone at all?
Click to expand...
Click to collapse
Ok here goes....at first i tried different simcards with the same network operator with no success, this morning (South Africa time) I rethought your advice about trying other simcards, this time from other network operators....VOILA!! All it was is that the phone got locked to the other network again!! Probably by the Anti-virus app.... well i never!!!! So there you have it ...!!
If you can advise me about unlocking my Samsung S3 mini (on Cell C in South Africa) I would be very grateful!
Thank you again for your excellent advice...! Very much appreciated
Regards
Charles
Glad you're on the right track. As far as unlocking, you can try the instructions here:
http://forum.xda-developers.com/showthread.php?t=2082626
Seems like with most Samsung unlocks like these, it is very dependent on the build version of the software and the cellular company. If you are on 4.1.2, and it is not working, see if you can find a 4.1.1 modem and try again. That works in many of the phones I have unlocked with this kind of method. If that doesn't work, you're going to need an unlock code. If you aren't sure where to get that, check out my site and send me a message.
hello again Es0
es0tericcha0s said:
Glad you're on the right track. As far as unlocking, you can try the instructions here:
http://forum.xda-developers.com/showthread.php?t=2082626
Seems like with most Samsung unlocks like these, it is very dependent on the build version of the software and the cellular company. If you are on 4.1.2, and it is not working, see if you can find a 4.1.1 modem and try again. That works in many of the phones I have unlocked with this kind of method. If that doesn't work, you're going to need an unlock code. If you aren't sure where to get that, check out my site and send me a message.
Click to expand...
Click to collapse
hmmmm I put the other network simcard in, made a test phone call... worked fine! so I thought its sorted now...now the fault is sort of on again. At ABOUT DEVICE and STATUS it shows the right network, but in the dropdown menu it says selected network unavailable.... can't make phonecalls but have access to internet via 3G...!! Can you still give me an opinion?
Charles

[Q] A bit cautious about installing a ROM again..

Well I have a GT-9300, I used to have custom ROMs on it. Until it received a SDS(In total the phone was 4 times in Warranty repair), they "fixed" it the first time.
After a while I got tired of the Stock ROM and it being Sluggish, wanted to install Cyanogen Mod. I did but the phone turned into a PDA, when I checked in Status(Settings>>About>>Status) the "Network" block said "Unknown"(IMEI & Serial Number were intact!). The phone is SIM free!
I sent the phone a second time to Warranty repair, they "fixed" it again.
Now after it returned, after a while I wanted to Update via Samsung Keis to 4.3, after I did same result that happened after first repair!(IMEI & Serial Intact but Network Unknown)
I sent the phone off to a 3rd time to Warranty, this time they replaced the entire Motherboard of the phone thus changing IMEI & Serial Number.
When it came back, when I went to pick it up at the store where I sent it off. I noticed that the SIM card slot is broken, sent the phone to warranty repair once a gain and got it back after a week with fixed SIM slot.
Now my concern is that even after the Motherboard has been replaced, if I will try to install a custom Cyanogen Mod I will hit the same error (IMEI & Serial Intact & Network: Unknown).
Has anyone had this kind of issue of SDS and Network:Unknown? After a new motherboard replacement did it solve it?
I really want to get rid of the TouchWiz, it's heavy and makes the phone sluggish!!

[Q] Help Soft brick fixed replacement on it's way already.

So I somehow soft bricked my SGS4, think I unistalled something I shouldn't have with Titanuim backup. Contacted T-mobile and am receiving a new phone under my warranty for just the 5 dollar processing fee. Knowing I was getting another phone I figured I'd try to fix the one I had. Went into download mode and fixed it. What do I do now ? I don't want to be billed for the whole phone price. Also a known issue before the soft brick was my sd card wasn't being recognized. So even though my old phone is technically fixed from the issue I reported to get the replacement, the sd card still isn't functioning so it's still broke essentially.
arbyn said:
So I somehow soft bricked my SGS4, think I unistalled something I shouldn't have with Titanuim backup. Contacted T-mobile and am receiving a new phone under my warranty for just the 5 dollar processing fee. Knowing I was getting another phone I figured I'd try to fix the one I had. Went into download mode and fixed it. What do I do now ? I don't want to be billed for the whole phone price. Also a known issue before the soft brick was my sd card wasn't being recognized. So even though my old phone is technically fixed from the issue I reported to get the replacement, the sd card still isn't functioning so it's still broke essentially.
Click to expand...
Click to collapse
I'm having trouble seeing the issue here...? The SD card wasn't being read, you soft bricked it messing around, ordered a new phone, fixed the 1st phone's soft brick and the SD card still isn't being read. So if that is right, then what is the problem with returning the first phone since it was not working properly?

Categories

Resources