ok guys, watched the n00b disclaimer video, and of course I searched high and low, but cannot seem to find a thread on this. Both my wife and I have VZW droid 1's. I take very good car of mine so it has been flawless, unfortunately, her screen appears to be dead (only lights up, no response to touch screen, will not display images) She has USB debugging turned off so I cant access the phone from what I can tell. My question here is can I simply put her motherboard in my phone and get her information off of it? maybe turn on usb debugging while its in my case?
I know it's alot of work, but she has a lot of information stored on the phone and needs it out of it.
Any help would be appreciated. Also, if anyone has any idea what is wrong with the screen let me know, i looked at all the cables and they seem perfect. it seems like most people that have dead displays still have touch, but this has nothing, could it be simply a software issue and have nothing wrong with the hardware?
Thanks in advance guys!
Your motherboard swap should be fine.
I bought a broken droid off ebay exhibiting your issues, all it took to fix it was unplugging and replugging in the display cable. I then switched the motherboard with the one from my milestone and it worked fine, and without issue
I got my HD7 via UPS yesterday. It was completely brand new, but when I powered it on there was some weird flickering lines all over the screen. The intensity of it has diminished but they are still present. I can't see them on black or white colors, but I can clearly see them on every other color. I have no idea what is wrong. Anybody know what is wrong or how I can fix it?
send it back.
hd7 screen issues
if you have not foundan answer, here is a post from HTC
Thanks HTC:
Dear xxxx xxxx,
thank you for contacting me about this issue.
I have looked at the forums and seen that this is a fault found on quite a few of the handsets.
The fault is not the operating system or something that Microsoft has done. It is the graphics chip located on the main board of the device.
All that needs doing is what’s known as a resink. Basically the chip is blasted with hot air to melt the flux holding the chip in place and re-establish a proper and full connection between the chip and the board.
How ever, we will require you to call into the centre so that we can book the device in for repair.
If you have any more problems, then please do not hesitate in getting in touch with us again.
Regards
Carl
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.
Hi,
I am looking for a ROM without any hardware test on BOOT.
I have a small problem. if anyone can help me out please help.
Recently I cracked my screen and hence went to a local shop to get it replaced. Once replaced my phone was not booting. I thought it maybe a software issue. Later I realized this happens due to hardware and maybe some connection is not made, like the headphone jack.
I opened my nexus and checked. Turns out that guy dropped my light sensor which is close to the front camera. There is no light sensor now in the phone. I cannot go back to him.
Can anyone please suggest me some ROM which skips this hardware test? or any other solution please?
No need to open multiple threads. You already have one here:
http://forum.xda-developers.com/nexus-4/help/unique-problem-please-help-t3489723/post69358472
Thread closed
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.