Sorry, I have problems with my device. May @Manoj could help you with this.
I am on a test Pie version that will not work. You will have to check for the build.prop from an oreo device
A different solution was proposed by @Phie from the /e/ Dev team …check the thread here a different TWRP solved the issue for him.
1 Like
First time poster here, with the same problem of not hearing any sound during calls with a Mi A1.
The phone is not rooted, but I have been trying to follow the method highlighted by @Erekoze in a reply on Jun 11, '19. It appears that /system/build.prop can be pulled, edited locally on the PC, then pushed back to the phone and without requiring root access.
I have an authorization problem that is preventing me from doing this.
The phone is recognized by adb devices when the phone is booted normally. I selected Always accept connections when asked to do so. However, when the phone is booted in recovery mode, adb devices shows that the device is unauthorized. It’s very strange. Without authorization, I cannot pull or push files to/from the phone. I’ve been going around in circles wondering why the phone is not recognized in recovery mode, but is recognized when booted normally.
I’m stuck with a silent phone until I can solve this.
My other option is to root the phone, but I am not confident about doing this and do not want to wipe the phone if I can avoid it. This is the reason why I have been pursuing the option of editing /system/build.prop.
Do you have a suggestion about how to fix this authorization problem?
Phone is running Android 8.1.0 / LineageOS 0.7-o-2019122435222-dev-tissot according to the recovery screen.
Thanks.
I got exactly the same error with the same file dated 24/12/2019 Oreo. I upgraded to pie and everything is working fine, @YZkFixye
Thanks, @Erekoze. That’s good to know. It appears that version upgrades (eg Oreo to Pie) are not handled OTA, so I’ll follow the wiki instructions. I hope this will not require wiping the phone … deep breath 
I’m a bit confused about the exact process to upgrade. This thread indicates the need to upgrade Mi A1 firmware, and flash a stock Pie ROM prior to installing LineageOS/Pie. The wiki mentions none of this and I do not know whether the prior requirements have been superseded by a newer ROM version.
I’ll be using the ROM image mentioned in this thread unless you can suggest a more suitable one.
Thanks for your help with this. You have saved me a lot of time and frustration!
Hi @YZkFixye the upgrade to stock Pie is required if you are moving from nougat /Oreo builds to /e/ Pie. This is because there are firmware updates required to make the /e/ Pie run correctly.
It is not covered in the wiki because the official build of /e/ is still running on Oreo.
Downgrading the MiA1 from Pie to Oreo does not work and can cause issues.
So if you are currently running stock Pie build on your MiA1 do not flash /e/ Oreo builds on it. You would need to flash a Pie build on it . Currently we only have unofficial Pie builds for MiA1.
Official OS upgrades is planned for most devices but currently under testing.
Hi @Manoj, and thanks for your reply. Phone is running Android 8.1.0 / LineageOS 0.7-o-2019122435222-dev-tissot, so I guess not “Stock” Oreo.
Is this the upgrade process then?
- Upgrade firmware
- Flash Stock Pie (overwriting LineageOS Oreo)
- Flash new LineageOS Pie ROM (e-0.7-p-20191024-UNOFFICIAL-tissot)
Is step 1 still required if firmware updates are included in the Stock Pie ROM?
Will all this completely wipe my phone, or are the OS changes happening in a separate partition from my data? (I know it’s important to backup first, and I have done so.)
Sorry for the noob questions.
Thanks.
Flashing the stock Pie ROM will update the firmware. Post that you can flash the /e/ Pie unofficial ROM
OK. And will this completely wipe the phone?
When I tested this out the step that I followed are documented here. As mentioned there I formatted and then wiped system + data + cache before the install.
Flashing a StockROM firmware deletes everything on the device irrevocably.
It’s therefore necessary to back up your important personal data before flashing.
Thanks. I’ll proceed with caution 
Not a great start. I’m stuck in a boot loop after flashing the phone with the fastboot image from tissot_images_V10.0.16.0.PDHMIXM_20191206.0000.00_9.0_494f11505e.tgz using MiFlash 2018.5.28.0.
The phone is now in fastboot mode waiting for my next move. Right now, it is winning and I am losing.
What should I do next?
Is the 10.0.16 the latest stock build for the MiA1 ? Try with the latest stock and MiFlash…the guide was written some time back and they were the latest versions then.
10.0.16 is the latest fastboot image available from this site.
There is a newer MiFlash (20191206) available here. I’ve installed it but it generates an error during the early stages of flashing “couldn’t find script” when I select the “save user data” option, as directed by the installation instructions.
Just mentioned in passing: There are also TWRP Flashable Firmware *.zips available for the Xiaomi Mi A1.
I found a twrp flashable zip and start with it. It was a pie december updated
Thanks @archie and @Erekoze , but I don’t have TWRP installed. Is there an advantage in doing so? Being a noob, I’m trying to stick to specific instructions like these rather than using methods that rely on a level of overall understanding that I do not yet possess. Happy to pursue a TWRP option if you think it will help.