I’ve just tried it : I can’t say it was a failure, but … I’ll need more patience and more tests
1/I entered ‘XT1676’ in the site search engine and it offered me an xml.zip which I accepted: no more sound and no more network! (a step backwards)
2/ I tried again, following his advice (but why always do everything the other way round?), i.e. by giving him one of my IMEIs.
He did recognise the device (saying I was out of warranty ;)… but no audio and no 2g/3g network
3/ I switched the Moto off and back on … and I have audio
So I took the opportunity to test the headphones and microphone too: everything’s fine!
4/ But it’s not over yet as I still don’t have an imei (even though motorola used the info to find my device!!! )
That’s not the only problem, as the device keeps booting and rebooting (a problem I had initially and the reason I wanted to get my hands on it).
5/ What can I do? Try /e/OS 2.2 again? (which for the moment has always found the imei ?
Any other suggestions?
(probably start by saving with ? twrp ? or ? )
I’m going to end up dreaming of a phone box in my neighbourhood …
I think you mentioned that it had been your son’s. Did he have it working ok at the end, or did he abandon it due to “issues”?
I would be inclined to stick with stock for say 24 hours and try to search for answers to stock issues. I think it a bit unlikely that a Custom ROM will fix up a compromised device – but of course always fun to play with, but you say it is your main phone. Does it make calls on stock?
Did he have it working ok at the end, or did he abandon it due to “issues”?
no problem (and no issues either in the 2 years I’ve been using it).
The problems only appeared at the beginning of August (I put it down to too many apps installed
Does it make calls on stock?
No: it recognises my sim card (my phone number) but without imei it tells me it only accepts emergency calls ( … an emergency audio call … without sound! )
1/ after a few reboots last night, my G5 caused a problem
Quickly ! adb devices to try and keep some info … but first I had to reactivate the usb link (which was cut, sometimes, after a reboot.) And then … too late, it rebooted !
Those were his only words! and today? nothing
2/ while continuing to search for information I found this post : https://xdaforums.com/t/no-audio.4476947/
It doesn’t tell me anything technically, but it does reassure me that I’m not -completely- crazy yet, because the situation described is exactly the same as mine.
3/ So I kept looking and other similar cases seem to have appeared on an Asus.
… and theses 2 devices have the same Snapdragon™ 430 processor (MSM8937) and if we do a search on this processor we find others audio problems .
This phone was initially marketed under Android 7, then an official update was offered under 8.1.
In order to get off to a good start, I’ve just tried to install version 7, but it’s impossible!
In Android you cannot “Go back”. Not by official upgrade paths anyway. Some fastboot ROMs will downgrade (loosely speaking this is because all partitions are changed at one time, so no partition remains to throw an error like you see).
New test: installation of LineageOs 14 in order to have Android 7 as you suggested:
Successful on this Moto G5 (but boot and reboot as with all my previous attempts). At least I went back in time
So I’m running Android 7 but Motorola is much smarter than me (I had no doubt!!! ) and refuses to install the V.7 stock rom … but I try again by flashing all the other partitions under android7 : yet another failure.
Commandes : flash partition gpt.bin
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
(bootloader) is-logical:partition: not found
Warning: skip copying partition image avb footer (partition partition size: 0, partition image size: 46592).
Sending ‘partition’ (45 KB) OKAY [ 0.172s]
Writing ‘partition’ (bootloader) Validating ‘gpt.default.xml’
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling ‘gpt.default.xml’
FAILED (remote: ‘’)
fastboot: error: Command failed
Erreur lors de l’exécution de la commande : flash partition gpt.bin
I don’t know what this partition thing is, but isn’t there a trick to creating and/or enlarging it?
(probably not, the info would have been published )
Note: after several reboots I’m on Android 7 and the device is configured.
Android 7.0 version
Search for update: the software on your device is up to date.
I don’t understand that last comment! (I have the network via wifi and I managed to search via the search engine)
What should I do now?
1/ To save this android7 first perhaps? (even if no sound or imei)
2/ To hope to come back to android8 in a complete way
Thank you all for your patience in reading my stories … from a bygone era!
The end of my unhappy trials?
I think so, because I haven’t been able to make any progress since last week, and this weekend I found several videos with faults that seem very similar to what I’ve seen on my Moto G5.
The fault would be on the hardware side and would be solved by changing the analogue/digital converter.
Unfortunately I don’t have the skills to play AC/DC !
Removing the chip with a desoldering station, yes … but then absolutely unable
Anyway, thank you for your many ideas and avenues of research: if the device remains broken I’ve already learned a lot and will remember this forum … if one day I manage to discover /e/OS
Hello and thank you for taking an interest in my problem
(I’m replying late, I wasn’t available in September and I’m just now getting back to my phone!)
So here’s the first video … which doesn’t tell us anything, but in which I see the same problem as what I heard on mine.
And two other videos describing how to change the component … but technically, I don’t know how!
The only thing I know for sure is that the problem is not with the speaker.
And one comment: the fault bothered me (microphone, phone calls) for several days. So I’m wondering if it’s not a case of a solder joint having failed and if heating without removing the component wouldn’t enable it to be joined together (random probably and overheating of the useless pcb perhaps?).
)
