[badmania98] Huawei P40 (Lite, Pro, Plus) Guides, News, Discussion & Support

[badmania98]

MicroG GmsCore v0.2.23.214816 has been released on 2022-01-25.

This is a MAJOR release with significantly improved features and a number of important bug fixes, including specific fixes for Android 12. Also, it brings back the ability to pass Safetynet under the same conditions that would allow this with Gapps instead. Changelog / Release Notes: Exposure Notifications: Add support for validating signatures on key files (only for DE and CH for now). Thanks @cgrigis Add support for more detailed API and use Advertisement version 1.1. Thanks @Elsensee Improve permission checks, especially for Android 12. Thanks @bubu, @fynngodau Cloud Messaging: Improve reconnecting logic. Thanks @grote SafetyNet / DroidGuard: Implement DroidGuard without additional helper. Allow using external DroidGuard via network Easy check for SafetyNet functionality in settings Device profiles: Allow to spoof device identity Import device details from profile file Location: Update UnifiedNlp to v2.0-alpha7 Improved reliability of service Improvements and bug fixes (as always) New features SafetyNet / DroidGuard The updated SafetyNet implementation runs proprietary DroidGuard code privileged in the com.google.android.gms package name. This is required on at least some devices to pass SafetyNet. However this features is disabled by default. If you don't want to run proprietary code by Google on your device do not enabled SafetyNet. As of now, microG SafetyNet implementation, once enabled, should work on all devices and ROMs that would pass SafetyNet attestation with original Google Play Services. This means that ROMs that are rooted (= come with a su binary that allow privilege escalation), with unlocked bootloader, or for some other reason do not pass the CTS or trigger the SafetyNet system will fail SafetyNet attestation. Hiding or spoofing such details from DroidGuard/SafetyNet is out of scope for this project, but techniques to allow passing SafetyNet on custom ROMs should equally work with microG.

Device profiles This features is mostly useful for Huawei devices or other devices that are banned from accessing Google services. Choosing a profile of a non-banned device should allow using the device with Google services. For now, two device profiles are included with microG (Nexus 5X with Android 8.1.0 and Moto G with LineageOS 14.1). If you are a developer, you can easily create a device profiles based on data gathered from a device. See this file for a sample device profile. Once created, you can import device profiles in microG settings (under "Device registration") to test the profile. If you are a custom ROM developer, you can add a custom device profile for your ROM by placing an appropriate device profile in /system/etc/microg_device_profile.xml. This can be useful to spoof the details of the original vendor ROM.

========== END RELEASE NOTES ==========
Closed repository issues likely fixed with this release: #1567, #1606, #1644, and others. Downloads are available via F-Droid microG repo and Github. Native F-Droid packages will arrive a bit later. 3rd-party installer bundles will be updated as per each developer's workflow. (MinMicroG has released a new STABLE build based on this microG version. See the announcement for it here: https://t.me/microG/54913 Github release page for this update: https://github.com/microg/GmsCore/releases/tag/v0.2.23.214816 Here's our summary of the previous update released on 2021-08-23: https://t.me/microG/39598

Great. How can we use this in our phones?

 

[kwstpap_93]

it says

"This features is mostly useful for Huawei devices or other devices that are banned from accessing Google services. Choosing a profile of a non-banned device should allow using the device with Google services. "

 

[badmania98]

it says

"This features is mostly useful for Huawei devices or other devices that are banned from accessing Google services. Choosing a profile of a non-banned device should allow using the device with Google services. "

If you already tried, just let us know more info.

 

[yellowhornet13]

@yellowhornet13: If 21.24.56 - 040408 doesn't work, you can try 21.24.56 - 120400 too (just my opinion).
May matter, for some cars, the differences between dpi and nodpi versions ...

Now it works. I must has been related to GPS. Thank you.

 

[badmania98]

Now it works. I must has been related to GPS. Thank you.

So. It works? What was wrong?

 

[yellowhornet13]

So. It works? What was wrong?

Yesterday I updated GPS to your version with different dpi. Today I checked it and can confirm, it works.

 

[badmania98]

Yesterday I updated GPS to your version with different dpi. Today I checked it and can confirm, it works.

So, with 21.24.56 - 040408 it doesnt work but with 21.24.56 - (xxxxxx -other version) works?

 

[yellowhornet13]

So, with 21.24.56 - 040408 it doesnt work but with 21.24.56 - (xxxxxx -other version) works?

I had - Google Play Services- 20.21.17 (120400) - won't work

and now have 21.24.56 - 040408 - works

 

[badmania98]

I had - Google Play Services- 20.21.17 (120400) - won't work

and now have 21.24.56 - 040408 - works

Ok. It is clear now. I saw you thanked to Shymmy and I thought my solution was wrong.

 

[yellowhornet13]

Ok. It is clear now. I saw you thanked to Shymmy and I thought my solution was wrong.

My mistake. Your solution helped me again. I did some donation to U.

 

[badmania98]

My mistake. Your solution helped me again. I'll donate U.

Received. Thank you.

 

[Racer_]

Hello, I misclicked and upgraded GPS to 21.48.15 (100400-414534850). Is it possible to downgrade it because now I have the message "This device isn`t Play Protect certfied" when try to open Play Store. Also similar error when I try to open Chrome.

 

[badmania98]

Sure. After that you have to clear cache and force stop the apps (Play Store, Maps, etc). Better use V1-V4 from first page.

 

[almircuric]

A short history of EMUI firmware versions on P40 Pro C432
( on other phones type or region could be different versions but some how similar)
​

10.1.0.121 = I suggest to use this version to install GMS. It is more compatible to upgrade to the next versions of EMUI . I never updated EMUi to a higher version than 11.0.0.186. In this case, my phone has a working Fast Charge and transfer data through USB cable from/to computer.
This is the version that I use on my P40 Pro and I disabled EMUi/software upgrade.

10.1.0.131= The last version that can be used to install GMS.

10.1.0.176 = This is the minimum version that you can reach when downgrade from a EMUI11 no higher than 11.0.0.186, using original HiSuite, if you never upgraded to a higher version than EMUI11.0.0.186. Downgrade from this version to a lower version (10.1.0121 or 131) will be done using ”pen-drive+USBC OTG” or ”NM card”.

11.0.0.186 = The last EMUI11 version that allows downgrade to a lower version (no lower than 10.1.0.176) using original HiSuite, if you never upgraded to a higher version than EMUI11.0.0.186. If you upgrade to higher EMUi version than 11.0.0.186, next time when you downgrade it, the phone will loose Fast Charge and transfer data through USB cable from/to computer. To fix this issues you have to upgrade back till the newest version of EMUI11. I suggest you to not upgrade to a newer version than 11.0.0186 and to disable software updates (EMUI), if you never upgraded to a higher version than EMUI11.0.0.186.

11.0.0.193 = It can NOT be downgraded to a lower version with original HiSuite. You can use HiSuite proxy or other method to downgrade to a lower version. After downgrade the phone will loose Fast Charge and transfer data through USB cable from/to computer. To fix this issues you have to upgrade back till the newest version of EMUI11, using OTA (frrom phone menu) or eRecovery (wifi). I sugest you to upgrade to 11.0.0.202 (no higher than 11.0.0.230) and disable software upgrade (EMUI).

11.0.0.202 = First EMUI11 that gets back Fast Charge and the transfer data through USB cable from/to computer after downgrade to EMUI10.1 and upgrade (several times) through OTA or eRecovery.

11.0.0.230 = Last firmware version that can be used to downgrade with HiSuite Proxy. It can NOT be downgraded to a lower version with original HiSuite. You can use HiSuite proxy or other method to downgrade to a lower version. After downgrade to EMUI10.1 the phone will loose Fast Charge and the transfer data through USB cable from/to computer. To fix this issues you have to upgrade back till the newest version of EMUI11, using OTA (frrom phone menu) or eRecovery (wifi). I sugest you to upgrade to 11.0.0.202 (no higher than 11.0.0.230) and disable software upgrade (EMUI).

11.0.0.260 = First firmware that will not allow downgrade to the previous firmwares with HiSuite Proxy. You have to dowgrade first to EMUI11.0.0.230 (or other, no lower than 11.0.0.202) that have USB connection to computer. This first downgrade will be done using ”pen-drive+USBC OTG” or ”NM card”. After that you can use HiSuite proxy or other method to downgrade to EMUI10.1 in one step. After downgrade to EMUI10.1 the phone will loose Fast Charge and the transfer data through USB cable from/to computer. To fix this issues you have to upgrade back till the newest version of EMUI11, using OTA (frrom phone menu) or eRecovery (wifi). I sugest you to upgrade to 11.0.0.202 (no higher than 11.0.0.230) and disable software upgrade (EMUI).

12.0.0.218 = First stable EMUi12 firmware. It can be downgrade to 11.0.0.260 using the last version of original HiSuite. If you already installed GMS, on previous EMUI version, before upgrade to EMUI12, it will work.

Now you can return on first message of the thread and read next ones.

​

Very very useful infos i this post. Congratulations ! This is expert's way. All precise and clear and certain. Thanks a lot in the name of all Huawei lovers. Bravo

 

[korppi12ww]

Hello,

i just bought cheap second hand 130€ p40 pro

everything works, but i cannot connect to pc, usb stick etc.

i have done all the basic tricks to get it working. (mtp, debugging etc.)

Just OTA updated to 11.0.0.230

charging works

it has damage backside just where the usb c connects to the mainboard. The back glass has shattered and bent inwards just where the connector is.

So should i have usb back with 11.0.0.230 or the connector inside broken? (havent opened it yet)

 

[badmania98]

Hello,

i just bought cheap second hand 130€ p40 pro

everything works, but i cannot connect to pc, usb stick etc.

i have done all the basic tricks to get it working. (mtp, debugging etc.)

Just OTA updated to 11.0.0.230

charging works

it has damage backside just where the usb c connects to the mainboard. The back glass has shattered and bent inwards just where the connector is.

So should i have usb back with 11.0.0.230 or the connector inside broken? (havent opened it yet)

Install HiSuite on computer. Run it and follow the guide to connect the phone. On 11.0.0.230 is no issue regarding USB connection.
About USB stick: should be NTFS or FatEx format.

 

[korppi12ww]

Install HiSuite on computer. Run it and follow the guide to connect the phone. On 11.0.0.230 is no issue regarding USB connection.
About USB stick: should be NTFS or FatEx format.

I tried hisuite now, nothing happens. Phone starts only charging when i connect it to pc. I get no option to choose between transfer files or charging only.

Usb stick has been ntfs, exfat, fat32, no connection. Stick works on my girlfriends samsung immediately.

Deveploper setting is mtp

I guess usb problems should be gone by 11.0.0.230

 

[korppi12ww]

I got the phone so cheap that there must be something wrong in it

 

[badmania98]

I tried hisuite now, nothing happens. Phone starts only charging when i connect it to pc. I get no option to choose between transfer files or charging only.

Usb stick has been ntfs, exfat, fat32, no connection. Stick works on my girlfriends samsung immediately.

Deveploper setting is mtp

I guess usb problems should be gone by 11.0.0.230

See here no. 6. Set it on HiSuite Mode.

 

[korppi12ww]

See here no. 6. Set it on HiSuite Mode.

View attachment 5522355

I did that too, nothing happens

Phone only starts charging, hisuite says device not connected