[Honor 9  ROMs, Kernels, Recoveries, & Other Develo] overflyer:
So somewhere I kinda messed up, but I do not really know where. Just a heads up, I kinda know my way around a lot on unix systems, even a little bit of coding and compiling. However, I seem to not have fully grap how partitions on a smartphone work together. My only guess is that I messed up something while trying to recover from the frozen boot screen I kept on getting using the system.img in the OP. Yes, I rebooted several times and Wiped data/factory reset and cache. I WAS ON OREO C432 before! Anyways then I started to reflash my old system. Boot was still frozen. So I tried manually flashing my old system with fastboot. That is when things got worse, however, by now I can report that everything is restored as it should be I guess, just the boot mechanism is not working. I keep getting stuck at the screen "Your device has been unlock. It cannot be trusted. <more text>" then "Device is booting now...". I get no boot animation even. It will just reboot a second time into that same screen which will then go to eRecovery. Fastboot, Recovery and eRecovery are working. For some reason I cannot get ADB over TWRP. That would help. Btw, can we have TWRP 3.2.1. This would be so great since it fixes the createTarFork() failed ERROR 255 (I made sure that no paritions which were to be restored where mounted!) when trying to restore TWRP backup. Surdu you can also tell me where to pull the TWRP 3.2.1 git and how to compile the recovery image for the honor 9 myself that would be nice.

So this was the general state information of my phone to give you a quick overview. What I have tried until now to fix my phone:

- Flash ROMS (wont work since partition names got renamed from Nougat to Oreo. Took me a while to figure that out. This is also why I dont know how to fix boot in Oreo since fastboot flash boot boot.img I extracted from UPDATE.APP wont work. Why is there no more BOOT.img in Oreo?). Also flashing generates more <something>TarFork() ERRORS.

- dload update.zip methods

- push command file to /cache/recovery/ update method (Basically I followed the HOW TO GET OREO FOR YOUR HONOR 9, again. In both ways: First Oreo and then Rollback. For ALL update.zip methods when I boot into stock recovery whether it is nougat or oreo it goes to 5% and then tells me that Software update has fails with a bis red exclamation point and a link to a dead URL)

- MULTITOOL method (tried Unbrick, flash boot/kernel etc, nothing helped, boot flashing always reports "got partition length error") Why are there so many tools developed for windows for this, I had to do a windows installation for that, I despise windows :(

- Huawei extracted images from UPDATE.APP method with manual flash

- Flash stock ROMS (like I said flashing with TWRP generates more <something>TarFork() ERRORS)

- DC-Loader method

- I read 2 hard unbrick threads and tried more stuff

- I died many wipes even data, internal storage and system. I tried to repair and reformat them and then reflash .img files with fastboot. Worked but did not help.

- ServiceRecovery (xda thread that provides a RAR file with an insane file name length, gave me problems on NTFS -.-) Method B130, extract all images, reflash manually

- I tried using the twrp terminal to give myself an overview over the partition layout etc and then dd rewrite from twrp terminal. did not screw up anything, but also dd not help.

So like I said something is not right with the phone recognizing the system when it was flashed. It seems like it does not attempt to boot it but is stuck somewhere. I think this problem persists because A LOT changed in OREO and there are no good informations on this, yet. Just for nougat.

What would help me would be:

- Flashable zip file of your ROM in OP :)

- TWRP 3.2.1 for compiled for Honor 9 (or manual instructions, I already found the xda build guide. But a BoardConfig.mk file from surdu would be great, thanks in advance man)

- Someone who tells me as many fastboot flash <partition name OREO> <image_name> as possible, especially the ones that fix boot operation

and also tells me what OREO ROM he would extract the images from. Like I said fastboot flash boot boot.img does not work for OREO.

- Fix adb connection for TWRP so I can get a adb shell

- Fix MTP mount for TWRP

- Maybe available Linux tools for huawei instead of windows

- Any other advice is highly appreciated.

- A OREO Honor 9 partition layout. What partition is what /dev/mmcblkp0* block device. What is it's corresponding partition name. What stock rom image file is suitable to restore it. What is the size of those partitions and what is there native file system as provided in standard configuration by Huawei Honor. What files and partitions are responsible to have a working boot operation?

- A clean TWRP backup of afresh oreo system with ALL partitions

I would love my phone back :( *sigh*

I probably forgot to mention a million things. Be easy on me. I have a bad bad cold with fever plus I destroyed my phone last night :/

over

EDIT:

Now I will try to clean my TWRP backups with either https://github.com/BuildingAtom/CleanTwrpTar or this https://github.com/venerjoel99/TarProject since they could fix the createTarFork() error for TWRP 3.1.x. Lets see how that goes. Official bug report: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/964