[Huawei Ascend Mate 2] EndlessFall:
RE: MT2 specific boot loop cause identified + new workaround/fix

Got it. I've finally identified & fixed what I believe to be the specific cause of the boot loop.

As I mentioned before, I knew that Google Play Services newer than v11.3.02 was causing some unknown software or hardware incompatibility with the MT2 that induced the boot loop. My previous fix worked, but it depended upon Play Services not being auto-updated beyond v11.3.02. Thankfully, this is now a non-issue!

To uncover the exact cause of the problem, I created and examined logcat files that captured the moment when the boot loop crash occurred.

The bottom line is that Google Play Services newer than v11.3.02 has compatibility issues with Location Services (com.qualcomm.location) bundled in the ROMs.

Here's a basic guide to fix the problem:

*** UDPDATE: Method #2 is found in my post #32 and will be easier/faster for most users. For those of you with a currently boot looping MT2 with an OS that you want to rescue, please skip to post #32. ***

*** UPDATE: If you are installing a ROM newer than 09/02/17, the developer may have already integrated the fix, disabling or removing "com.qualcomm.location" ***

Method #1:

1. Backup your files

2. Install MDMower's TWRP v3.1.N0-0 and boot into recovery.

3. Wipe & format to remove the current OS & get a clean start.

4. Flash the OS of your choice (AOKP, CandyROMs, CM/LineageOS, etc). I recommend, and tested, MDMower's LineageOS 08/19 & 08/29.

5. Before rebooting, flash a GApps package that does not include Play Services newer than v11.3.02 (minimal preferred), followed by the rooting tool of your choice (such as SuperSU v2.82 SR3). You can always use the Developer Tools built-in root instead if the ROM supports it.

6. Boot to system. After the one-time init setup, install an app freezing tool (such as App Freezer or SD Maid), grant root, and configure it to view system files. Freezing is safer than uninstalling.

7. Freeze "Location Services" (com.qualcomm.location). This will NOT disable GPS location from working on the MT2 (for example, Google Maps still works fine). Let's not start discussing UnifiedNlp!

Yes, app "freezing" can be done with the ADB "pm disable" command, but tools like SD Maid are so much nicer to use...

Once Location Services is frozen, the MT2 will be capable of successfully installing & running the latest Play services via GApps packages, standalone Play Services installers (variant 436 or 430 nodpi), and (presumably) auto-updates.

I am currently running LineageOS 08/29 with Play services v11.5.30 beta. I started with Open Gapps pico 08/11/17, applied the workaround, flashed Open GApps 09/01 with Play Services v11.5.09 (to test the latest GApps), and then updated to Play Services v11.5.30 beta via the standalone installer. Not a boot loop in sight.

At the end of the day, this is all experimental. That being said, I have tested this method across multiple OS's and multiple reboots, and my MT2 is stable. As proof of concept, as soon as Location Services is unfrozen, the boot loop begins immediately.

A patched "com.qualcomm.location.apk" or some other official solution may come in the future, but for now this IS the fix.