yashsingh1/xdaforums huggingface dataset:
[Huawei P10 Lite Questions & Answers] Arun J01:
Step by step video to fix your bricked P10 Lite

This video is made to help everyone to successfully fix your Bricked Huawei P10 Lite

Few months Before I bricked my Huawei P10 Lite and searched a lot of sites and blogs , and finally fixed my BRICKED MOBILE .

Follow the below youtube video link clearly to unbrick your Huawei

https://youtu.be/0vDgDXePAR4

Cheers.....:o
[Huawei P10 Lite Questions & Answers] Sohail Wazir:
Sir can you explain dload with three buttons method?
[Huawei P10 Lite Questions & Answers] clonephone82:
Oeminfo bricked?

Hi, I have bricked my phone. I can flash a ROM as an example no I have flashed the Elite ROM v7.7 but the oeminfo is bricked. Because the build number says: elemental als the IMEI numbers are missing so it looks strange. My problem is I do not know my build number and I have no backup. So I know that my phone is a WAS-LX1 with 32GB ROM and 3GB RAM. And I am from Europe/Austria.

Can I use that Files here to fix the phone?

many thanks
[OnePlus 5 Guides, News, & Discussion] fil0s0f0:
An easy fix to be able to fix the can't mount data after you install any oreo roms

If you installed any oreo rom and you decided to go back to nougat from a usb otg sideload and you still want to keep all your data afetr install the rom but keeps saying unencrypted unsuccessful, and won't let you boot to android.

Just install omni oreo rom from an external device and you'll be able to acces your data and go back to nougat without wiping you internal storage
[OnePlus 5 Guides, News, & Discussion] glockman4519:
I'm going to search for the rom but if you have a link to the Oreo Omni build I would greatly appreciate it. I installed an AOSO Oreo build and even thought I am unencrypted and can see my internal stage in the rom, my data partition (in TWRP) won't mount so I can't do anything right now. And I really want to get the heck out of Oreo until it's a bit more stable.

Thank you for the tip
[OnePlus 5 Guides, News, & Discussion] fil0s0f0:
https://darkobas.ddns.net:8443/zl1/omni-8.0.0-20171029-oneplus5-HOMEMADE.zip

Install the rom , like any rom, Don't forget the no verity op5 zip, restart , check if you can see your files, go back to recovery and check if you can see your data
[OnePlus 5 Guides, News, & Discussion] glockman4519:
Yes, thank you. I had an issue getting anything into my device to flash since I couldn't see my internal storage while in TWRP. I could see everything just fine while booted to system thought.

I ended up adb pushing the stock firmware over onto my device and going back to stock. Then just started all over again. I will be leaving Oreo alone until this issue gets fixed...lol
[OnePlus 5 Guides, News, & Discussion] fil0s0f0:
You could have install it from a USB
[MTCD  Android Head Units Q&A] s.rahus:
Hello All,

I have the new PX3-2GB-Android 7.1.2 unit with XRC MCU. The only issue I have with this unit is that the built-in microphone or any external microphone is not working (not at all working) outside the bluetooth application. The microphone is working flawlessly inside the bluetooth application (during a phone call for example). However, its not picking up the sound when used with other applications. (OK google won't work for example).

I tried different external microphones and even the USB microphones without any luck. Also, I tried different ROMs (even the Malaysk one has this issue) and MCU versions- nothing solves the issue. Because of this I am not able to use MTC dialer or google assistant which are very useful.

I have seen many other users also having this issue but for some devices its working though.

Could this be a hardware/mic wiring issue? Or an MCU issue? Thoughts?

Note: I searched and could not find a thread for this issue, for the PX3-2GB-Anddroid 7.1.x devices. As this is an issue with the new devices I am starting a thread in the hope to fix this with our combined effort.

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] dbenet:
I have the same issue. I have also MTCD_XRC (2.58_1 version) unit with Android 7.1.2 and i didn't find any solution. I hope it's a software issue as the internal mic works good with bluetooth calls.
[MTCD  Android Head Units Q&A] s.rahus:
Can you please send me the purchase link to your device? I tried different ROMs and tried various versions of MCU, without luck. Also I have seen devices with same MCU and same ROM has the mic working flawlessly. Now I am on Malaysk ROM and still has the same issue. So I guess this is a hardware issue. I too have a XRC device.

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] kiru:
I have the same unit and reached out to the seller. His response was "this is not supported"
[MTCD  Android Head Units Q&A] s.rahus:
What unit you have?

Thanks,

Rahul U S
[MTCD  Android Head Units Q&A] kiru:
I have the one that is direct OEM replacement for a 2007 Honda CRV and branded Hizpo.
[MTCD  Android Head Units Q&A] dbenet:
My unit is from Isudar, Aliexpress. It's possible that is a problem with XRC units, don't know. In a forum someone said that mtcd_gs firmware can be installed on XRC but didn't try it.

Enviado desde mi Redmi Note 3 mediante Tapatalk
[MTCD  Android Head Units Q&A] s.rahus:
Hey thanks!

BTW, Isudar is just a seller, not a brand. I have also seen XRC units with working mic, so it's really confusing. Can you point me to discussion where cross compatibility of GS and XRC firmware is discussed?

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] s.rahus:
[MENTION=3590033]Malaysk[/MENTION] [MENTION=5092263]Hal9k_[/MENTION]

What you guys think?

Thanks,

Rahul U S
[MTCD  Android Head Units Q&A] dbenet:
https://translate.google.es/transla...hp?showtopic=838658&st=720&edit-text=&act=url

http://www.androidiani.com/forum/au...hieste-aiuto-e-consigli-sullacquisto-121.html

http://www.androidiani.com/forum/au...droid-rockchip-px5-2-gb-ram-32-gb-rom-42.html
[MTCD  Android Head Units Q&A] typos1:
Most MTCD/E devices can use the MCU software from other MTCD/E units, see [MENTION=4974080]marchnz[/MENTION]'s "Cross compatible MCU" thread.

What XRC units have you seen with the mic working ?

You need to find out whether its just the RK3188/PX3 2Gb units that have this problem.

Maybe someone who upgraded their SoM to the 2Gb SoM can tell us if the problem existed on the 1Gb SoMs ?
[MTCD  Android Head Units Q&A] s.rahus:
Hey Typos1,

I thought I have seen someone reporting working mic on XRC unit, but I guess I am wrong. Its not working for any XRC units it seems. Can it be a problem with MCU firmware? Do you know if GS firmware is cross compatible with XRC?

I have, however seen mic working on the new KLD, PX3, 7.1.2 units.

This one for example has mic working- https://youtu.be/FLB5RuB9Lf8

He has confirmed that the mic is working with google assistant. It's a KLD, PX3, 7.1.2 unit (watch from 17:30 to get the version details).

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] typos1:
Not all MTCB,CD and E units are wired the same - some units the external mic will not work with Android but the internal will, for instance.

I would guess if all XRC units are like this, then its down to the motherboard and it would be a case of finding where the mic wiring is and how to connect it to the SoM. I think it would be simple to do, the hard part would be finding out what tracks on the motherboard go where . . .

Check out the "Cross Compatible MCUs" thread for more info on changing MCU manufacturers. I m not sure it will help but its worth trying.
[MTCD  Android Head Units Q&A] dbenet:
I have checked lots of times [MENTION=4974080]marchnz[/MENTION]'s "Cross compatible MCU" thread but didn't find any information about XRC compatibility with other MTUs. The only information that i found were the links i posted before, but didn't found nobody that has tested it (replace XRC with GS).

I have seen a thread with someone with XRC and mic working (and another person with XRC and same mic problem):

https://xdaforums.com/showpost.php?p=73565517&postcount=49
[MTCD  Android Head Units Q&A] dbenet:
As said in the thread i added in last post maybe it's something related to /system/etc/mixer_paths.xml file.

Maybe changing some values there it can work. I have the stock fimrware so i have no root to modify it, but with [MENTION=3590033]Malaysk[/MENTION] ROM i suppose it can be modified.

There are some values marked as "OFF", "HP_NO_MIC" or "MIC OFF" than maybe can be modified (still don't know much about how to modify that file). Maybe mic is disabled because of mic audio problems in bluetooth calls said in others threads, to have better sound in calls. Don't know...

This is my mixer_path.xml file:

<mixer>

<!-- These are the initial mixer settings -->

<ctl name="Capture MIC Path" value="MIC OFF" />

<ctl name="Playback Path" value="OFF" />

<ctl name="Voice Call Path" value="OFF" />

<ctl name="Voip Path" value="OFF" />

<!-- These are commonly used control sequences -->

<!-- These are useful named paths -->

<path name="speaker">

<ctl name="Playback Path" value="SPK" />

</path>

<path name="main-mic">

<ctl name="Capture MIC Path" value="Main Mic" />

</path>

<path name="headphones">

<ctl name="Playback Path" value="HP_NO_MIC" />

</path>

<!-- Playback paths -->

<path name="media-speaker">

<path name="speaker" />

</path>

<path name="media-headphones">

<path name="headphones" />

</path>

<path name="voice-rec-speaker">

<path name="speaker" />

<ctl name="Voice Call Path" value="SPK" />

</path>

<path name="voice-rec-headphones">

<path name="headphones" />

<ctl name="Voice Call Path" value="HP_NO_MIC" />

</path>

<path name="communication-speaker">

<path name="speaker" />

<ctl name="Voip Path" value="SPK" />

</path>

<path name="communication-headphones">

<path name="headphones" />

<ctl name="Voip Path" value="HP_NO_MIC" />

</path>

<path name="speaker-and-headphones">

</path>

<path name="bt-sco-headset">

<ctl name="Playback Path" value="BT" />

</path>

<!-- Capture paths -->

<path name="media-main-mic">

<path name="main-mic" />

</path>

<path name="voice-rec-main-mic">

<path name="main-mic" />

</path>

<path name="communication-main-mic">

<path name="main-mic" />

</path>

<path name="media-second-mic">

<path name="main-mic" />

</path>

<path name="media-headset-mic">

<path name="main-mic" />

</path>

<path name="bt-sco-mic">

<ctl name="Capture MIC Path" value="BT Sco Mic" />

</path>

<path name="voice-rec-headset-mic">

<path name="main-mic" />

</path>

<path name="communication-headset-mic">

<path name="main-mic" />

</path>

<!-- Off paths -->

<path name="playback-off">

<ctl name="Playback Path" value="OFF" />

</path>

<path name="capture-off">

<ctl name="Capture MIC Path" value="MIC OFF" />

</path>

<path name="incall-off">

<ctl name="Voice Call Path" value="OFF" />

</path>

<path name="voip-off">

<ctl name="Voip Path" value="OFF" />

</path>

</mixer>
[MTCD  Android Head Units Q&A] typos1:
If no one has tried putting a nother MCU on an XRC unit then YOU will have to be the first one to try it ! Its not hard to put it back to standard if it does not work, you cant wait around for someone else to try it !

I very much doubt it is a software problem, I think it is hardware related and I suspect, as I have said, that the SoM does not get any connections to the mic.

After you have tried the MCU from a couple of other manufacturers on your device we will get more of an idea whether it is hardware or software related.
[MTCD  Android Head Units Q&A] dbenet:
About who must be the first to try to put another MCU on a XRC i don't agree with you but don't want to open a debate about that as it's more important for me (i think for rest of readers or participants of that thread) to try to solve that issue. We can discuss that in private if you want.

About the issue problem i think there's just one evidence: internal mic is working with bluetooth calls, so mic audio input is processed by head unit in a specific case, so can't think that it's something cannot be resolved with software (easier or harder to do it, don't know it).

My hypothesis:

- As mic is working with bluetooth calls maybe mic input is going (by hardware) by bluetooth input channel. If is that true maybe playing with mixer_paths.xml is possible to use that input bluetooth channel as

input to voice recording. In mixer_paths.xml there is a Capture Paths section where i suppose you can specify the input channels for every component.

Maybe changing that:

<path name="voice-rec-main-mic">

<path name="main-mic" />

</path>

with that:

<path name="voice-rec-main-mic">

<path name="main-mic" />

<ctl name="Capture MIC Path" value="BT Sco Mic" />

</path>

or something like that can work. I can't try that without root access and for now don't want to change to Malaysk ROM. If there's no risk with that i'll try to put Xposed as i saw in another thread that there's a MOD to change mixer_path.xml with that, and without root.

Original Capture Path section:

<!-- Capture paths -->

<path name="media-main-mic">

<path name="main-mic" />

</path>

<path name="voice-rec-main-mic">

<path name="main-mic" />

</path>

<path name="communication-main-mic">

<path name="main-mic" />

</path>

<path name="media-second-mic">

<path name="main-mic" />

</path>

<path name="media-headset-mic">

<path name="main-mic" />

</path>

<path name="bt-sco-mic">

<ctl name="Capture MIC Path" value="BT Sco Mic" />

</path>

<path name="voice-rec-headset-mic">

<path name="main-mic" />

</path>

<path name="communication-headset-mic">

<path name="main-mic" />

</path>
[MTCD  Android Head Units Q&A] flimsflims:
Hi s.rahus , i've the same unit from Isudar

After upgrading to MTCD_XRC_V2.60 the problem persists :( so I'm considering to install MTCD_KLD_v2.60b_1 like the video you refered to but i do not find that file.

Do anyone know where can i found?

regards
[MTCD  Android Head Units Q&A] s.rahus:
I am on Malaysk ROM, so I tried this, did not work.

I did a quick search, could not find it. http://4pda.ru/ is a good place to search. Please keep us posted.

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] s.rahus:
mixer_paths.xml not valid?

Guys,

I modified the mixer_paths.xml file in various ways, but the issue persists.

So I deleted the file completely, rebooted the unit, made sure that the file is not there, but this made no difference, the audio still plays and mic is working how it was always, no difference whatsoever. So is this file is still valid? Deleting it made no difference at all!!!

Thoughts? Now what? I can try different MCU firwares when I find some time in coming days.

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] dbenet:
https://yadi.sk/d/umCvHqCDzHccr

Here you can find lots of MTCD_XXX firmwares, in "All dmcu for PX3, PX5, Intel Sofia3g" folder. The are some for KLD, including 2.57 and 2.65b, but not 2.60

Be careful with that. I saw in some forums that MTCD_GS firmwares can be compatible with MTCD_XRC ones (but didn't found anybody who has tested), but never saw that KLD ones can be compatible with XRC, so changing XRC with KLD maybe works or maybe not, and can brick the unit.
[MTCD  Android Head Units Q&A] linux33it:
Look at this, installed GS and HA on XRC

http://www.androidiani.com/forum/au...ip-px5-2-gb-ram-32-gb-rom-95.html#post7931243

On my unit for sale on Aliexpress, this note appears

http://www.androidiani.com/forum/au...ip-px5-2-gb-ram-32-gb-rom-98.html#post7931648

https://it.aliexpress.com/item/1024...lgo_pvid=ecd3239f-bde9-4c3c-b7dc-3eafb63990d8
[MTCD  Android Head Units Q&A] typos1:
From reading the Cross Compatible MCU thread I dont think another MCU will brick your unit if its no compatible, you just reflash the original MCU.

As I ve said before, I dont think this is a software issue, I m pretty certain its a hardware issue.

To start to sort it I would try and trace where the mic goes so it can somehow be intercepted and routed to the SoM, of course it would involve some hardware mods.
[MTCD  Android Head Units Q&A] s.rahus:
Hello,

What are you trying to say? GA or HA MCU firmware fixed the issue? I did not fully understand it because of the translation. What is the mentioned in the note?

Thanks,

Rahul U S
[MTCD  Android Head Units Q&A] typos1:
Some sellers say that google voice doesnt work with their units, I m guessing thats what the Aliepxress ad says.
[MTCD  Android Head Units Q&A] s.rahus:
Oh, a sacrifice made to make the bluetooth call quality better? If we have both, the bluetooth call quality will get affected? But was that thread also talking about some fixes?

Thanks for your update! :)

Thanks,

Rahul U S
[MTCD  Android Head Units Q&A] linux33it:
No ,change MCU does not solve the problem

I believe the limitation is hardware
[MTCD  Android Head Units Q&A] s.rahus:
Okay, so hardware limitation, no fix?

Thanks,

Rahul U S
[MTCD  Android Head Units Q&A] linux33it:
Observe these two apparently similar unities

https://it.aliexpress.com/item/1024...lgo_pvid=ecd3239f-bde9-4c3c-b7dc-3eafb63990d8

Limited

https://it.aliexpress.com/store/pro...36.html?spm=a2g0y.12010612.0.0.28028d3e24bsC5

NO Limited

I think the limitation is Hardware
[MTCD  Android Head Units Q&A] s.rahus:
Got it. Thanks much! Sad, though.

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] flimsflims:
Finally I installed KLD v2.65 and GS 2.58.

Both MCU images are fully functional but shows a message warning "Version Unmatch" . Everything works fine (canbus,apps, etc) but the microphone doesn't

I'm afraid the issue is going to be with the hardware. :(
[MTCD  Android Head Units Q&A] typos1:
Have you followed the "Cross Compatible MCUs" thread to find out how to get rid of the mis-match error ?

I dont wanna say I told you so, but I told you so ! - its a hardware issue. You d be better off dismantling your units and tracing where the mic goes and somehow re-rooting it to the SoM or using an external mic. I know external mics have been tried before but I think some software mods would be needed to get one working and I dont think anyone has tried that.
[MTCD  Android Head Units Q&A] typos1:
My RK3188/PX3 Nougat unit is also XRC, voice search doesnt work . . . but it DOES work when an RK3368/PX5 SoM is fitted !

So, its not actually a motherboard issue, its to do with the 2Gb RK3188/PX3 SoMs.

Does anyone know if non XRC RK3188/PX3 Nougat units work with voice search ?

Then we d know if it is a specific Nougat SoM problem or just Nougat SoMs in XRC units.

Unfortunately I sold my Nougat SoM before I found this out, so I cant put it in my non XRC unit to see for myself.
[MTCD  Android Head Units Q&A] s.rahus:
Hey Mate,

Yes, we have people with non XRC units with working voice search.

So how the core board (PX3) reads the mic- From the mainboard, (Mtcd)?

Is it possible to connect the rear mic directly to the Core board(PX3)?

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] typos1:
Specifically non XRC Nougat units, not just general non XRC MTCD/D units ? (Just checking).

Yes, that must be it - the connections must be there if the octacore SoMs work.

How strange that its only XRC units with Nougat SoMs.

My first thought knowing this now would be an MCU issue, I know a couple of different MCUs have been tried, but I think someone needs to try as many different non XRC MCUs as possible using [MENTION=4974080]marchnz[/MENTION]'s "Cross compatible MCU" thread as a guide, to see if any solve it. If none do then move on to looking at other solutions.
[MTCD  Android Head Units Q&A] s.rahus:
Yes! On non XRC Nougat units.

The MCU from a mic working non XRC Nougat unit was tried as well without luck (KLD MCU was tried).

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] typos1:
You didnt read my reply properly - I said "I know a couple of different MCUs have been tried, but I think someone needs to try AS MANY DIFFERENT NON XRC MCUs AS POSSIBLE using [MENTION=4974080]marchnz[/MENTION]'s "Cross compatible MCU" thread as a guide", not just one.
[MTCD  Android Head Units Q&A] s.rahus:
I saw that but was thinking that a working MCU from another unit should do the trick (as it already has the code to read the mic) I understood your intentions though.

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] typos1:
Not all MCUs are cross compatible, it could be that KLD and XRC are not and that is why it does not work - indeed there was a mis match error on the KLD MCU and the poster did not say whether he used the thread to try and remove the error. This is why as many as possible need to be tried.
[MTCD  Android Head Units Q&A] blitzkriegoutlaw:
So I just purchased a Hizpo UNZ132F (Android 7.1 2GB PX3) and I was so happy that the microphone works fine, at least it does on my unit. I tried right away by clicking on the microphone on the screen in google maps and it recognized my voice. It took me a couple of days to figure out how to get "OK Google" working.

After I updated everything including Google and Google Play Services. I then tried to install Google Assistant and that failed saying it was incompatible. I followed all the directions on Google's website with no avail. I then tried to set Google to support "OK Google" on all screens but it seemed to fail after my first of three voice trainings. Silly me I just had to scroll the screen up. Now I can say "OK Google" even with the radio going and it will respond. A little slow but I noticed these units use marginal hardware.

I also cleared out all the data for Google and Google Play Services after I upgraded. Not sure if it was necessary but it certainly had some of the old settings from before the upgrade.
[MTCD  Android Head Units Q&A] linux33it:
NO, also on PX5 android 6 XRC , does not work
[MTCD  Android Head Units Q&A] typos1:
Please tell us what your MCU is so we know what unit you have.
[MTCD  Android Head Units Q&A] s.rahus:
Okay, now the million dollar question- What MCU you have?

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] blitzkriegoutlaw:
I'll have to take a picture tonight. I took my other car to work today.
[MTCD  Android Head Units Q&A] blitzkriegoutlaw:
2.58_1. See attachment
[MTCD  Android Head Units Q&A] s.rahus:
Yours is XRC unit and still the mic works outside Bluetooth app as well!!

Well, this is getting very complicated. Are you using any external mic or just the mic that is built into the unit?

Cheers,

Rahul U S
[MTCD  Android Head Units Q&A] dbenet:
I have the same XRC firmware version, and exactlly the same Android version. So it doesn't seem i's a firmware/rom version.

Maybe it's any configuration file or some hardware difference. Can you post your /etc/mixer_path.xml file?

Thanks
[MTCD  Android Head Units Q&A] blitzkriegoutlaw:
Maybe it is a driver. I'll see if I can get if I can get a adb remote session going tonight and capture the entire etc directory and files listing with date and sizes (ls -lR).

I have had the unit in the car for only a week so still finding my way around. The settings screen seemed very stripped down and as far as I know these units have not been rooted without hijacking the entire rom.

---------- Post added at 05:06 PM ---------- Previous post was at 05:02 PM ----------

Just the mic on the unit itself. No external mic. No Bluetooth to a earpiece or anything like that. I have my phone paired for calls but I'm pretty sure it is using the mic on the unit.
[MTCD  Android Head Units Q&A] typos1:
Maybe it IS a software issue after all ?
[MTCD  Android Head Units Q&A] cecengazi:
I think its a software problem

Im on xrc 2.58.1 and "ok google" not work.
[MTCD  Android Head Units Q&A] blitzkriegoutlaw:
I have given up on the battle of getting adb going remotely using WIFI without a USB cable. I have copied off XML files from /etc using a terminal emulator. See attachment.
[MTCD  Android Head Units Q&A] blitzkriegoutlaw:
Had something weird happen today. The microphone only worked for phone calls and not in any apps. I couldn't figure out how to perform a cold reboot so I had to disconnect the battery and reconnect. I was wondering if some app was holding onto the microphone. Maybe it would be worth while looking at the catlog for problems?

Does anyone know how to perform a cold reboot? Connect adb? Thanks
[MTCD  Android Head Units Q&A] s.rahus:
Goto factory settings, password is 126. Change something, apply and exit. It will prompt for reboot.

Thanks,

Rahul U S