Help desperate situation. Note 9 audio dead - Samsung Galaxy Note 9 Questions & Answers

Note 9 Exynos Purchased in India.
But my audio has stopped working.
I spent days and nights trying to see if anybody else has faced a similar situation and could not find much info.
XDA gurus my last hope.
Samsung's support is bad. here. The less said the better.
I finally pulled the trigger and did a factory re-set. That too did not help.
Here is a funny thing.
I can shoot pictures but I can't shoot Video.
If I plug my headphones in nothing happens.
The only thing that works is blue tooth headset but not for calls.
If I can figure out what parts need changing I can order them. And try replacing them.
The only Part I could find is this.
https://shopee.com.my/Krcb-98512-Fo...CUD07XjfwNIQZ3inXJADNm-X84Ea9PHVLt7NMgOSL74Fo
Update:
I finally tracked the problem down to the latest update. Soon after the update. Phone started to get hot. And also charging took longer than normal. Audio slowly stoped working.

You can try the following diagnostic tools, if anything to confirm if you have a hardware issue:
1) Dial *#0*# on you dialler and you get Test Mode from where you can test various hardware, including audio
2) In Samsung Members app go to Phone Care and select Interactive Tests. There you can find another set of hardware diagnostics that you may find useful.
Good luck!
Sent from my SM-N960F using Tapatalk

Done sir.
Im pretty sure the Audio IC is blown.
Just need to confirm the part number to order.
kta said:
You can try the following diagnostic tools, if anything to confirm if you have a hardware issue:
1) Dial *#0*# on you dialler and you get Test Mode from where you can test various hardware, including audio
2) In Samsung Members app go to Phone Care and select Interactive Tests. There you can find another set of hardware diagnostics that you may find useful.
Good luck!
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse

Just in case somebody else has this problem I am sharing info as I find it.
It would seem the IC needed is MAX98512
And you can download the full Note 9 schematic from my google drive here.
https://drive.google.com/file/d/15MPFlmcnupHqU_4ZAkPOyWo5QeBj9XI-/view?usp=sharing

How do I figure out which IC to change. 98512 or 9896B
Could not find any info online. Other than 98512 is an audio amp and 9896B is audio IC.
Further reading & research seems to link this to the latest Android 10 update.
A lot of other people have faced similar problems on various phones. And 90% of the time the only solution is to have the mainboard replaced.
Just google android 10 updates broke my phone.
So far I have done 3 factory data re-sets. Each time trying something new like this time I did not update from backup. Still, my max98512 seems to be the problem.
I have placed an order for new chips from aliexpress.
Not being able to roll back really suck.

So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.

RonChinoy said:
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
Click to expand...
Click to collapse
Following here, my father Note 9 same problem and he think it very very bad work by Samsung to put out such devices to break after only 1.5 year of use, His old Nexus 4 is still working and running Android 9 custom ROM thanks to XDA Developer!
Samsung have done something bad, and it is to charge same amount to repair the phone as buying a new phone
So instead of repairing dead audio Note 9 at Samsung its better to do it unofficially I think :silly:

silvaBR said:
Following here, my father Note 9 same problem and he think it very very bad work by Samsung to put out such devices to break after only 1.5 year of use, His old Nexus 4 is still working and running Android 9 custom ROM thanks to XDA Developer!
Samsung have done something bad, and it is to charge same amount to repair the phone as buying a new phone
So instead of repairing dead audio Note 9 at Samsung its better to do it unofficially I think :silly:
Click to expand...
Click to collapse
How much did they quote because one guy was quoted 18,000 I was quoted 26,500,
Yes I agree we save up for years or take out 2-3 year EMI to pay for these phones and then they don't last even 2 years. Samsung can not even explain why it failed. My Water sensor is not tripped. Phone has never been dropped or has a single scratch on it.
Im now using a 5 year old one plus that saw my daughter thru school and collage and its still going strong. Even after multiple drops in water.
Anyway if your interested I am importing all the Audio ICs 10 of each and plan to repair it myself.
The problem with getting outside guys to work on it is they try to reball the existing IC. And if that does not work They put in used parts.
Lets see if this is a s/w issue or a hardware issue if we can get a last_kmesg log file from a working phone we should be good to go.
I found this in the log.
audio_hw_proxy_9810: fast_out-proxy_open_playback_stream: PCM Device is not ready with Sampling_Rate(48000) error(cannot open device '/dev/snd/pcmC0D2p': No such file or directory)!
I really want to go back to Android 9. I don't even mind triping my Knox now.

RonChinoy said:
So I got this idea. To figure out if its a software issue or a hardware issue. Need to see if the device drivers are loading or not.
This info can be found by bootin up into recovery mode then view log. Open log last-kmsg
Its a pain to read. And I have not figured out a way to access the data via adb most of the instructions do not work on non rooted phones.
Can anybody with a working note see if the get this message in their log.
star-madera sound: Failed to parse codec DAI for uaif -517
@34%
max98512 6-0039 failed to read [0x0402][-121]
[max98512 _debug] max98512_i2c_probe: failed to read 0x402 [-121]
max98512: probe of 6-0039 failed with error -121
@56%
ALSA DEVICE LIST
no soundcards found
warning unable to open console
I need to know what is the text that shows up on the line after ALSA DEVICE LIST on a working phone.
The TWO ICS handling audio are max98512 and CS47L90 Ignore my earlier comments Indian Note 9 is different audio IC.
By this I can figure out if its a file corruption issue or a hardware failure issue.
Click to expand...
Click to collapse
hi, please guide me how to read logs. I have note 9 SM-N960F on android Pie Indian firmware.
@34% it is showing some frequency logs and 56% about some gamma values and pannel .
---------- Post added at 11:25 AM ---------- Previous post was at 11:04 AM ----------
here i found this method on samsung website to dump the logs.
SysDump tool:
Launch the Phone app.
Enter *#9900# to launch the SysDump tool.
If the Debug Level is Disabled/LOW, tap to select MID. This restarts the device.
Reproduce the issue that you would like to troubleshoot.
Repeat steps 1 to 2 to launch the SysDump tool.
Tap Run dumpstate/logcat.
Tap Copy to sdcard. This copies a timestamped .log file to the folder /log, which you can access through My Files in your personal space.
You can send the file to Knox Support, using one of these methods:

well found max98512 6-0039
for "ALSA DEVICE LIST" please share pic, it may help to find it.

The way I got to see my last_Kmesg was to go into system recovery i.e. power on with 3 buttons pressed. You get the menu which allows you to re-set the phone or wipe cache partition in that screen there is an option to view logs. From there I read the log.
Its a tiny font and took me 2 hours lol.
But chk this out. Just google Just google android 10 mic fix or android 10 audio problems.
And you will see that a lot of phones have been hit by this.
Not just samsung. But many brands. Some have found solutions some have not.
I think the first step for us is to figure out how to go back to Android 9.
If even after doing that the problem is not resolved then we have to replace the Audio ICs.
I belive the problem was caused by the update. And then it gets bad to the point where it destroys the audio IC.
Pixel phones had a similar problem where the android 10 spoilt sensors at the hardware level.
I was not able to find a directory /log or any files following your steps.
When you google Note 9 audio IC you get this link.
https://www.deviceparts.com/9896b-audio-ic-for-samsung-galaxy-note-9-ori.html
I have placed the order for this along with Max98512 but I can not find any reference to the 9896b IC is any of the Samsung Service manuals.
Lets focus on how to roll back to android 9. Because I think there were some massive changes to how audio is handled in android 10 and that is what spoilt our phones.
Basically due to overheating after the update. It was a crapshoot to see which IC lost contact.
Some people lost on display IC and some on Audio.
My Max98512 IC has arrived.

As to Samsung Claiming offically in writing to me that there were no Audio related problems reported after the update.
Show the lying [email protected]#[email protected]@ this simple google link.
https://www.google.com/search?newwi...TIuMZgBAKABAaoBB2d3cy13aXrAAQE&sclient=psy-ab
Can we use this method to roll back to Android 9 ? I heard rollback is not possible. ?.
Can somebody clarify ?.
https://www.rprna.com/news/how-to-rollback-from-one-ui-2-0-beta-android-10-to-one-ui-1-1-android-9/

it only possible if you have beta version of andriod 10 installed in your phone. if you have updated to stable version of andriod 10 then it is not possible.

Munawar Mehmood said:
it only possible if you have beta version of andriod 10 installed in your phone. if you have updated to stable version of andriod 10 then it is not possible.
Click to expand...
Click to collapse
a. I hope the Deves on XDA can fix this problem and figure out a way for us to roll back.
b. We put enough pressure on Samsung to allow us to roll back. Which I doubt as so many failures suits their agenda of getting you to buy a new phone.
c. We just address the parts that have failed and hope that they last.
==========================
Latest Update:
I was able to get my back cover off. Without cracking the glass or scratching anything it took me an hour but I took it slow on purpose.
Right chuffed with myself. Next step is to chk the speakers with a Multi Meter Then extract the board and inspect it. Water sensors are ok they were not tripped.
The Fingerprint flex was a nightmare to get off in the end it popped off on its own. And the flex nearly tore but did not.
The next step is to try and extract the mainboard and do a physical inspection and look for any damaged parts and to try and locate the Max98512 and the Audio Codec chip.
Im struggling here without the schematics. But my suspicion was right there is heating up all over the board. At the audio and you can see where the solder paste balls have separated from components. I see it near the display chips and near the audio chips.
There are tiny balls of melted solder all over the board.
Everything from the main chips to small components like SMD caps and resistors have over heated and shed these tiny balls of lead all over the board.
Im working without a microscope using a plastic pocket scope we use to read plugs.
Plan is to clean out all these melted balls and then put some flux and re-flow the lead. The Max98512 I will have to lift to see what the heat has done to the pads below.
I can't see any conformal coating on the board. This means if you live in places like India were we see humidity off 80-90% it can wreak havoc with your phone without even tripping the water sensors.
Today's plan is to pull the main board off. Wash it in Iso. Then used compressed air to blow off all the tiny balls of lead. Then fresh flux and lead. And then if I can get it to work. To coat the complete mainboard in a moisture-proof conformal coating.
I can't imagine why they would not coat the boards.
If you open up a Honda ECU after 25 years you will find that the board is still shiny. The lead looks fresh. And the reason is that they use a conformal coating.
And the reason why the audio and display ICs are getting hit the worst is that they have zero heat sinks. Im no expert but why would you run an Audio Amplifier IC with no heat sink. Makes zero sense to me.
============================

If you have an audio problem and are working with the 98512 here are the other parts you will need around it. These are the supporting components.
SCH Part # Part Desc
C8004 2203-009859 / 22000nF,20%,10V,X5R,TP,1608,T (Damaged)
C8002 2203-009858 / 10000nF,20%,10V,X5R,TP,1005,T
L8002 2703-005505 / 1uH,20%,2016,T1,0.043Ohm,42
Top
R8052 2007-007741 / 10KOHM,1%,1/20W,TP,0603
C8006 2203-007796 / 1000NF/1uf,20%,10V,X5R,TP,0603,0.
C8014 2203-008860 / 1000NF,20%,16V,X5R,TP,0603,0.
Btm
C8000 2203-008097 / 100NF/0.1uf ,10%,25V,X5R,TP,0603,0.3
C8002 2203-009859 /22000nF /22uf,20%,10V,X5R,TP,1608,T
C8004*2203-009858 /10000nF / 10uf,20%,10V,X5R,TP,1005,T
C8077 2203-008466 / 0.033nF,5%,16V,C0G,TP,0402,0.
C8003 2203-007621 / 100nF,10%,6.3V,X5R,TP,0402,T0

Thanks guys I solved my problem.
Purchased a Microscope, a soldering station, and a Max98512 AMP IC.
It took me 3 months but I did it.
I did try taking it to a shop. He soldered the IC on so poorly that the phone stopped booting up. And one 10K resistor blew. So decided to do it myself. Samsung Service will not do board level repair. ANd those out there offering this service 90% are uneducated without the right tools for the job.

Related

[Q] Network and SMS working, call is mute for me and other person

A few weeks ago my phone started to have a problem on calls. Sometimes everything works properly (usually when I just turn on the phone).
BUT, after first call, or a few seconds, the phone complete call, starts counting the call time, but I can't hear anything and other side also can't hear me.
The network and the messages are working fine.
I have already installed several ROMs, originals and custom ... the problem persists.
Has anyone experienced this? Or has any idea what problem is this?
Thanks!
you are not the first and not the last. I'm into this too. i think it's a hardware issue. I've tried everything, even this from S3, I opened the phone but I can't find the corespondent chipset. Si if someone will look into this and point to the chipset to press, I'll test it
tofanpc said:
you are not the first and not the last. I'm into this too. i think it's a hardware issue. I've tried everything, even this from S3, I opened the phone but I can't find the corespondent chipset. Si if someone will look into this and point to the chipset to press, I'll test it
Click to expand...
Click to collapse
This is hardware issue and some people from http://4pda.ru reporting successful repair.
I can only suggest, how to avoid the problem.
Aviod overheating, especially when flashing new ROM. Do it in cool place with battery cover open and do not close, until "Android is upgrading" message has gone.
can you explain/link the repair method? (point me to the 4pda topic and I'll try gtrans)
So if I flash the rom in a cold place the problem will be gone until the first overheat of the phone, which will be with the first over 5 min call, and that means it is a temporary solution until MB replaced?
Решил проблему со звуком при звонках у своего Active путём прогрева соседнего с предыдущим перепаянным (WCD9310) чипа "325A",
Translated:
Problem solved by heating (soldering) chip near previously replaced 325A
Another post explains, that chip was replaced because it was overheated and burned because missing experience.
yep. i think that right. I just found this on t-mobile support forum.
For those that haven't had any luck trying various software, firmware, setting fixes, be aware that there is a hardware problem related to this.
If you have all of the following symptoms:
-no dial (ringing) tone in the earpiece when connecting
-phone call connects but mic doesn't work
-phone call connects but no audio for both parties (where neither parties can hear)
There may be either a faulty 325A audio switch IC chip, or the solder points on the 325A chip is bad. The chip is located on the back of the motherboard, if your looking at it with the volume switch on the left with the two extension for the headphone jack on the top. You can find the chip if you follow the right headphone jack extension straight down and it's directly above the silver heatshield (basically the first IC chip you run into following the extension), it should say 325A on it. If you have a phone repair store nearby with a hot air rework station, they can reflow the solder and see if it helps or they might have to remove the chip and reball the solder on the chip. Or you can simply have them replace the chip with a new one, new chips cost like 9+ bucks, plus labor. Or if you're really brave (or stupid), you can buy a hot air soldering station with a small tip for like 60 bucks and try and reflow it yourself, but I'd advise against if you don't have experience soldering IC chips. If it's still under warranty, obviously get a new replacement handset because no amount of fiddling with software, firmware or settings will fix a hardware related problem.
Missing incall sound FIXED!!!
Following this tutorial I removed the mainboard and took it to a good friend who did a reflow to 325A chip. Reassembled the phone and after 2 calls the bug was on again. Reopened the phone and my friend did another reflow to WCD9319 chip (see picture in post 5). Since then no more missing sound. I played some games and listen some music from sdcard to overheat the under-flash zone (when there was heat, sound was not working) but the heating never happened again.
tofanpc said:
Missing incall sound FIXED!!!
Following this tutorial I removed the mainboard and took it to a good friend who did a reflow to 325A chip. Reassembled the phone and after 2 calls the bug was on again. Reopened the phone and my friend did another reflow to WCD9319 chip (see picture in post 5). Since then no more missing sound. I played some games and listen some music from sdcard to overheat the under-flash zone (when there was heat, sound was not working) but the heating never happened again.
Click to expand...
Click to collapse
Thank you, reflow the two chips and no more sound problem with call for two days now.
Sent from my SGP321 using XDA Free mobile app
d8389 said:
Решил проблему со звуком при звонках у своего Active путём прогрева соседнего с предыдущим перепаянным (WCD9310) чипа "325A",
Translated:
Problem solved by heating (soldering) chip near previously replaced 325A
Another post explains, that chip was replaced because it was overheated and burned because missing experience.
Click to expand...
Click to collapse
Thank you very mutch. Its really work.

Rear camera turn black when use it

Whenever I try to use the rear camera the display turns black while only showing the HUD. The HUD works fine, but the camera doesn't work at all. Nothing is blocking it either.
When switching camera modes (to manual mode for example), an error pops up saying that the "camera is not available"
IMPORTANT NOTE: The front facing camera is working perfectly fine.
Things I tried to do (aside from shipping it for repair):
1. Android repair via the PC companion software
2. Internal reset
3. Safe mode
4. Clearing cache files for the built-in camera app
5. Installing an alternative camera app (the built-in one was disabled)
6. downgrade and upgrade
7.change camera for new one (tested)
I had same situation with regular Z3. Someone brings it to service where I'm working and my first think was camera fault but changing camera didn't fix it. Near camera connection You can see some small capacitors, we call it filters. It looks like capacitors but it's soldered not only on opposite sides but 2 points on both sides. In regular Z3 there was 5 elements like this to change and after that camera starts working. I don't remember how exactly it's made in Z3c but it's really possible that it's the same issue and same way to fix it.
One more thing, if You can check one one more camera to exclude camera itself cause most issues like this are caused by faulty camera. I had many phones (most Z1 and Z1c) with this issue and changing camera always was the solution.
Good luck.
Same Here. Need help too.
Sent from my D5803 using XDA Free mobile app
I have three cameras and two z3c, I interchange camera and phone and always the same result
At this moment I don't have any Z3c to disassembly (except mu own but under warranty) to check where those capacitors are but if You could take a picture of camera connector on motherboard and near area I can mark which one should change.
@Chamelleon
Main camera not working
I have the same issue with my Z3 compact. The issue started happening on the 11th month of my one year warranty, I sent it for repair (14 business days y + shipping time back and forth). It came back with the same issue. Sent it back right away. After another three weeks without my phone, I got it back. Guess what? EXACT SAME ISSUE!
I called their support line explaining what happened, the guy told me that there is nothing they can do about it since my warranty expired. Of course they didn't have in consideration that I sent my phone before it expired and it took about seven weeks back and forth. There wasn't any sort of damage on my phone, was never dropped or damaged in any way, I never submerged it even if in theory, that would be ok. The report said "it has reviewed the functioning of the unit, unfortunately the defect is in the PCB so it is not able to undergo repairs to it."
The guy on the phone told me what he thought the report meant. It means there is damage on the main board(not caused by me) and the one year warranty manufacturer warranty department won't repair it. Maybe, if I had bought the 2 year "extended" warranty, they could do something about it. I asked if the issue is that my one year warranty was expired or if it is something that they just don't fix unless you get the "extended" warranty. He couldn't answer me and the only thing he said was "is there anything else I can help you with?"
From what I understood, there are two completely different departments, the one year manufacturer warranty that only cover some things. Not even sure what, because if it's broken screen, water damage or any physical abuse, they won't fix it. If it's a problem with the main board or PCB, they won't fix it either. It is a mystery to me what gets fixed in that department. The other department is the 2 year extended warranty. I'm not sure what they are willing to fix there, but from what they guy on the phone told me, it's more than the one year regular warranty.
Long story short, after two trips to FedEx, at least 8 hours total on phone calls, more than 7 weeks without my phone, I ended where I started. Sorry Sony, never again. Worst customer support I have ever experienced.
At this photo I can see only 4 of this capacitors and marked it, maybe it should be four or one I missed cause quality. Anyway regular Z3 has 5 like this and after changing all 5 camera start working again. You can desolder it from most Sony phones, I used capacitors from MK16 (Xperia Pro). So find some Sony board with capacitors like this and ask someone with good hot air solder station (if You don't have one) to change it.
Any news to this problem? I bought used Z3C with black rear camera problem because it was cheap. (Yes, the front facing camera is working perfectly fine). So far I have only tried software fixes and obviously they didn't help. I ordered new camera module from ebay and I'm now waiting for it. Has anyone tried soldering new capacitors if the new camera module doesn't help?
EDIT: Here is another thead with same problem: http://forum.xda-developers.com/z3-compact/help/rear-camera-hardware-detected-black-t3231509
As I said I've done it only in regular Z3 but If You gonna try give me some info is this solution is also working in Z3c case.
Chamelleon said:
As I said I've done it only in regular Z3 but If You gonna try give me some info is this solution is also working in Z3c case.
Click to expand...
Click to collapse
I'm still waiting for new camera module. If the new module is not working I will try soldering new capacitors. I will keep you up to date here .
Any news??
Completely forgot to post this, hope it help someone. I made the same thing with black camera on my Z3c. After I broke audio port in my Z3c and had to send it to warranty I took my gf phone, Z3c also. I restored my TWRP backup to her phone and all except camera was working. Camera was completely black but only main, front was OK. After that I was afraid that it's another hardware problem like Yours but after reflashing to stock problem gone. I repeated it few times to check if I'm right and I was. After flashing backup from another phone even without TA and Kernel backup there is a problem with camera.
So I was wrong saying it's only hardware problem. If anyone still has this issue and didn't reflashed his phone check it first.
@Chamelleon yes it's somehow a software problem (if we could say that ). For me i did fix it.
I did a Nandroid backup for my black Z3 compact (camera works properly) an restored it on my new White Z3 compact (also camera woks fine). after restoring the white z3c rear camera shows black screen, the front one is good.
=> i did a format factory reset : didn't work.
=> flashed a TFT file : didn't work.
=> flashed a D5803_23.4.A.1.232_Customized FR.ftf : IT WORKS !
and then i remembered that my phone was from "SFR" , a french network provider.
i hope this helps also
Edit: too new account, would be nice if a mod unlocks the posting of the direct image links and fixes the links - I think they are useful as this is a common problem and i already invested hours translating russian and documenting my research nobody else should have to do it
for me it was a hardware problem after dropping it.. I even changed the camera module.
Did some reseach, russian sites have some input:
Layout1: directupload.net/file/d/4472/9andayji_jpg.htm
Layout2: directupload.net/file/d/4472/vzvgbqqo_jpg.htm
It was loose, but when i tried to push it down with a hot metal to "solder" it, at some point it jumped away and was lost because it is so tiny!
Missing part: directupload.net/file/d/4472/qmut35qt_jpg.htm
The russian site suggest this soldering of bridges, however its not clear to me if they mean one of this electronic pieces (4pins each) or also the lower one.
Russian: directupload.net/file/d/4472/ag43kmda_jpg.htm
The question is now how these (likely) filters (because so close to the camera have to be bridges, it seemed to have worked for some russians:
Pins: directupload.net/file/d/4472/k86j53hr_png.htm
Not sure if there are 4 indipendend pins or if for those small footprints of electronic devices they use only the edges and then they have the same signal.
I was not able to see any text written on those two things, however i didnt have any magnifying glass.
basmok said:
Edit: too new account, would be nice if a mod unlocks the posting of the direct image links and fixes the links - I think they are useful as this is a common problem and i already invested hours translating russian and documenting my research nobody else should have to do it
for me it was a hardware problem after dropping it.. I even changed the camera module.
Did some reseach, russian sites have some input:
Layout1: directupload.net/file/d/4472/9andayji_jpg.htm
Layout2: directupload.net/file/d/4472/vzvgbqqo_jpg.htm
It was loose, but when i tried to push it down with a hot metal to "solder" it, at some point it jumped away and was lost because it is so tiny!
Missing part: directupload.net/file/d/4472/qmut35qt_jpg.htm
The russian site suggest this soldering of bridges, however its not clear to me if they mean one of this electronic pieces (4pins each) or also the lower one.
Russian: directupload.net/file/d/4472/ag43kmda_jpg.htm
The question is now how these (likely) filters (because so close to the camera have to be bridges, it seemed to have worked for some russians:
Pins: directupload.net/file/d/4472/k86j53hr_png.htm
Not sure if there are 4 indipendend pins or if for those small footprints of electronic devices they use only the edges and then they have the same signal.
I was not able to see any text written on those two things, however i didnt have any magnifying glass.
Click to expand...
Click to collapse
So I changed my camera because I thought it was a hardware failure (tried every other method before: going back to stock, wiping camera files etc.) and it STILL is black. Did you have any success with your camera?
mrfrantastic said:
So I changed my camera because I thought it was a hardware failure (tried every other method before: going back to stock, wiping camera files etc.) and it STILL is black. Did you have any success with your camera?
Click to expand...
Click to collapse
Try flashing stock ROM based on your country as i mentioned up.
mrfrantastic said:
So I changed my camera because I thought it was a hardware failure (tried every other method before: going back to stock, wiping camera files etc.) and it STILL is black. Did you have any success with your camera?
Click to expand...
Click to collapse
Me not (also changed the HW cam), the guys on the russian site yes (even with other similar sony).
Just check if there is something loose, maybe you are lucky and its a software problem *fingers crossed*. To me it happend exactly after dropping (and changing the screen which went without problems) so I was quite sure its HW based.
basmok said:
Me not (also changed the HW cam), the guys on the russian site yes (even with other similar sony).
Just check if there is something loose, maybe you are lucky and its a software problem *fingers crossed*. To me it happend exactly after dropping (and changing the screen which went without problems) so I was quite sure its HW based.
Click to expand...
Click to collapse
Hi basmok,
First off thanks for the research and for the pictures!
I have a similar story, phone was dropped, rear camera won't work, tried different ROMs without any luck then took phone apart and saw that one of the four tiny capacitors
just fell off and now it's MIA...
The last pic from your post (directupload.net/file/d/4472/k86j53hr_png.htm) which I assume shows the soldering of the bridge doesn't seem to work...
Do you still have that pic?
Also did you make any progress on the camera fix or gave up?
Thanks,
Ati
AtiGala said:
Hi basmok,
Do you still have that pic?
Also did you make any progress on the camera fix or gave up?
Thanks,
Ati
Click to expand...
Click to collapse
You were lucky, they were already in the recycle bin and deleted on the camera. Best I could do picturewise, i dont have a macro lens. Here we go, added all to imgurl so hopefully they survive longer: http://imgur.com/a/Of1DY
And no, didnt make any progress as i dont know what component they are. Normally all components have lasered some code but not sure if its just too tiny for my eyes or if they dont have it. I was a bit unlucky as i didnt have a soldering tool, so i tried it by pushing the pin down with a paperclip which i headed with a lighter --- well it jumped away and was not the best approach

Moto service center f-kd up my phone? What happened here?

Bought my phone in November and until May it was working perfectly, I thoroughly enjoyed the phone.
During the installation of the April security patch my phone got stuck and I had to reboot it.
As a result, Android didnt work anymore. Even after hard resetting the phone was super slow and full of errors.
I sent it back to an official Moto service center; so they could reset the firmware.
When I finally received my phone back, I notice there were marks on the back-glass that werent there before.
the "repair paper" said that "broken parts have been replaced".
The phone works quick again, except that the loudspeaker cracks really bad on 80% volume... and when calling I can hear a very soft but subtle abnormality in the speaker as well.
I also notice a small delay with the fingerprint scanner, which wasn't there before.
When I look into the android recovery menu I can see that this phone has a different serial number than the one I sent to them.
- Do you also think they gave me someone elses phone? Because my loudspeaker didnt crack at all at high volume.
- Is this legal ?
Simply repairing android doesn't require opening up the phone to "replace the motherboard", right?
Seems like they had to replace mainboard. Which is logical, because Android errors might have been a result of damaged memory.
At least this would explain serial number change.
And the speaker problem might be a result of incorrect assembly after the repair. (this happened once to me, when I received my Lumia 930 after the repair, headphones jack was not working correctly. It did not react when headphones were connected - fortunately, when I started to move the plug in the socket, the socket "jumped in" into its place and it started to work again)
I'd return the phone and request them to fix the problems you described. I don't think much more can be done on the discussion forum

Question Redmi 9T suddenly blackout after rebooted accidentally

Help me please. Just now my Redmi 9T doesn’t want to open after I accidentally rebooted it after charging. I already tried the long press power button also the volume up and down.
Is it overheated?
Will it power on with the charger connected?
It’s not over heated. No, the power won’t open even if I tried to charged it again. My friends said that it’s dead boot and idk what that is.
Sounds like a mobo failure.
Maybe someone here has seen this before.
Someone said from a group that it’s a system failure update.
maeyyang said:
Someone said from a group that it’s a system failure update.
Click to expand...
Click to collapse
Bricked? Damn...
I don't update my 10+... now you know one of the reasons why.
You may have no other option but to bring that thing to a service center near you
@maeyyang can I ask if you updated its system prior to the incident?
I also am encountering this problem you posted. How's your phone now?
I also facing this issue.. any updates on your device?
Delabytes said:
I also facing this issue.. any updates on your device?
Click to expand...
Click to collapse
brought it to the nearest service center, they said i have to wait for 1-2 months :/
they said that it's a mainboard's problem
I search videos on YouTube. The same issues occurred on Poco M3. They said that the issue is on the main board, specifically the power IC.The solution is just reheating the soldered IC on the board.
Here is the sample video:
Delabytes said:
I search videos on YouTube. The same issues occurred on Poco M3. They said that the issue is on the main board, specifically the power IC.The solution is just reheating the soldered IC on the board.
Here is the sample video:
Click to expand...
Click to collapse
That's a BGA. The heat has to be precisely controlled with a hot air station by someone that knows what they're doing. Too little heat/time nothing happens, too much you destroy it and the PCB maybe too.
These are the hardest SMs to deal with.
There's no guarantee that that's the problem and no way to inspect it without a factory test rig*.
All the contacts are underneath. It maybe another SM component that has the cracked solder joint. There are a lot of components in the power section. That maybe a common problem but not the only one...
*you can try gently pressing down on the chipset to see if it triggers an event.
I think it's better to just take it to the service center for the mainboard replacement and I heard about users who did the same method in the video had recurring problems after doing that.
Opening the back cover of the handset also voids the warranty and that's really bad.
derunheimlich said:
I think it's better to just take it to the service center for the mainboard replacement and I heard about users who did the same method in the video had recurring problems after doing that.
Click to expand...
Click to collapse

Pixel 4 XL System UI keeps stopping and other things

FYI: I already posted the same thing on r/GooglePixel, it can be found here:
- Sometimes on startup the phone displays that System UI isn't responding, and at other times System UI actually stops, showing no status bar and a black homescreen background. The phone proceeds to soft-restart and the problem persists. This happens even after I factory reset the phone, either through settings or through recovery mode. I tried re-installing the OTA update using ADB and a .zip file from here.
- Sound isn't working, neither the earpiece nor the bottom-firing are making any noise.
- When resetting the phone in recovery mode, I noticed this message:
E:can't send spi message try again
yet the reset supposedly happens without problems. I suspect this to be a security thing and this could be a main cause of my issues.
- I bought this phone as a spares and repairs item for cheap, that might be a dead giveaway to how screwed up it is
- It's on Android 12, the November 2021 update to be specific.
- Boot time in general is long considering the age of the phone
My main worry as of now is whether this is a software issue or a hardware issue. It would be great if this can be fixed through software like downgrading the OS perhaps.Sorry if this post is a bit long, I just wanted to document it as well as possible for anyone who is in a similar situation.
HELP.
Update:
Turns out that even flashing a full image instead of OTA doesn't solve the issue. I tried Android 10, 11 and 12 and used both manually downloading the image and flashing it through my computer's terminal, and using the Android Flash Tool online.One thing that did kinda help is changing the wallpaper from the stock live pixel 4 one. That removed the "SystemUI isn't responding" message. But the bootloop still occurs after I put the phone to sleep.
Sounds like a mobo failure... sorry.
A custom rom might bypass the area of damage... or not.
With the millions of semiconductor junctions alone it never ceases to amaze me these devices are as reliable as they are.
blackhawk said:
Sounds like a mobo failure... sorry.
A custom rom might bypass the area of damage... or not.
With the millions of semiconductor junctions alone it never ceases to amaze me these devices are as reliable as they are.
Click to expand...
Click to collapse
Guess this phone might be completely screwed up after all...
ukasa said:
Guess this phone might be completely screwed up after all...
Click to expand...
Click to collapse
Take a look inside. Make sure the battery has enough capacity to meet power requirements.
Depending on the phone sometimes a failed (or wrong part) C port PCB can cause bizarre behavior.
Look for bad contacts on the ribbon cable connectors, solder cracks, etc.
-Gently- flex the mobo, chipsets while booted to see if you can provoke it. A pencil eraser works well.
Unfortunately the BGA chipsets solder joints are impossible to inspect, use care flexing near them!
Look for mistakes from previous repairs.
Make sure all ground pathways are good, some devices use unconventional methods like the frame rail or even a slightly longer through screw.

Categories

Resources