[Huawei Mate 9 Questions & Answers] Dramacydril:
Hi,

Hope somebody got some more tips or a fix for the following problem i have with my huawei mate 9 C432 (europe version) (bought 2nd hand with this problem)

* Phone came with

not working touch at android lock screen ONLY

(brown wallpaper, water dock, clock works, icons show like normal)

* When i go to recovery everything works fine,

NO touchscreen problem at all.

* Couldnt get my product id number inside settings to generate unlock bootloader code so i used DC PHOENIX, DC UNLOCKER, HCU. FLashed the following with DC phoenix, this unlocked my bootloader.

- Flashed MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Nonspecific_Android_7.0_EMUI_5.0.dgtks

- MHA-L29B_C432B185_Firmware_Switzerland_Nonspecific_Android7.0_EMUI5.0.APP

- L29B_C432B185_update_MHA-L29_hw_eu.APP

(In this order)

After Flashing these 3 files my phone boots like normal and STILL i get the same touchscreen problem at the lockscreen (brown wallpaper). Recovery works fine, fastboot also.

Then i decided to flash only the FACTORY FIRMWARE CHINA NONSPECIFIC 7.0 DGTKS file >>>>>> Now at this lockscreen the touchscreen magically works and i can do whatever i want in the settings (android 4.2 i believe). No problems at all. Problem is i cant stay at this HUAWEI ASCEND (bootlogo) firmware. I want Android 7 / 8 for Huawei mate 9.

After this i also flashed TWRP recovery and did a format CACHE, DALVIK, SYSTEM, DATA and then installed custom firmware RomAur-v2.2 from this forum.

After flash i get the freaking brown bridge lockscreen

AGAIN

with no working touchscreen. The phone doesnt give me any

SETUP (language, wifi etc) option

at all before lockscreen, with Samsung phone roms i usually have to setup the custom rom first. None of that here.

Highlighted some "maybe" important info??

===========================================================

Twrp Custom Rom RomAur-v2.2 flash log:

RomAur B197 v2.2 by auras76

>>> Mounting partitions

>>> Writing system

>>> Creating toolbox symlinks

>>> Setting permissions

>>> Flashing Boot

>>> Installing Busybox

>>> Installing Magisk...

**************************

* Magisk v14.0(1400) Installer

**************************

- Mounting /system, /vendor, /cache, /data

- Device Platform: arm64

- Constructin Enviremonment

- Adding addon.d survival script

- Found Boot Image: /dev/block/sdd32

- Unpacking Boot image

- Checking ramdisk status

- Stock boot image detected!

- Backing up stock boot image

- Patching ramdisk

- Repacking boot image

- Flashing new boot image

- Unmounting partitions

- Done

>>> Enable init.d...

***********************************

System/Less Module Template

***********************************

A simple init.d emulator (@korom42)

***********************************

- Magisk/Systemless Install

- Mounting /system(ro), /vendor(ro), /data, /cache ! Magisk is not installed!

>>> Unmounting partitions

>>> Installation Complete!

script succeeded: result was [>>> Installation Complete!]

Update partition details

....done

So hope it a bit clear for you guys, maybe you can help me??

What could this be? I was think about some corrupt touchscreen related files that are present on the internal space of the phone that are stuck in there and need to delete them?? Maybe some boot image that doesnt get flash.

THANKS