[Mate 8 Android Development] luckymerlin:
WOW! Thank you so much for that very detailed tutorial and the shared files. I am sure that will be very useful, also for others here that might be in a similar situation.

Of course I could not wait and tried the other method I linked to in my last post ("Edit:" at the end). It was "successful" in terms of: yes, B560 was running. But you are right, the way there is a bit troublesome and I did not manage to get it into a "normal"/official state with locked bootloader, so I basically got stuck at Step 7 of the tutorial there (OP): the factory reset fails at around 99% and reboots to system, where you can set the basic settings again, as if the factory reset was successful. But then I noticed that the Bootloader is still unlocked (and also displays additionally "FRP unlocked"), but I am

not

able to connect to it via adb/fastboot and relock by the common commands for that - they fail ("failed (remote: root type is risk)"). I was though able to flash TWRP (twrp-3.1.0-0-next.img, which I think is the correct version for EMUI 5?) without error, but you'll end up with a boot-loading screen when trying to actually start the recovery mode. So it was also not possible to make a wipe/factory reset through TWRP.

However, then I saw your post here and aborted my experiments, trying to get it working properly. I flashed the official rollback image for the Mate 8 and B192 stock afterwards by dload, so I am back at B192 again for now. (Maybe I should post a Link to our posts here in the other thread, just in case someone else wants to try and finds the other thread first, just like me :D)

So, of course I tried your two first methods (HiCare and eRecovery) already. HiCare still doesn't work out, neither using the preinstalled HiCare-App, the App you attached or the one that can be downloaded via Play store. I tried all of them having set the region to Ireland (and Germany separately) - no luck. eRecovery also fails, right at the beginning after being successfully connected via WiFi: "Getting package info failed". No luck there either it seems - but I tried that before already with the same result, so my hope was not really big :D

So, method 3 remains, yet untested by me ... but I thought I'd call the Huawei Service Hotline (number to be found in the HiCare App) first, before I try that. As I am now at the latest official firmware, bootloader locked, etc., maybe worth a try. (I could not call them on the weekend and yesterday was a bank holiday here in germany.)

I got the following information from them: The rollout period (8 weeks from release of B560) is not over yet, so maybe my device is indeed not yet priviledged to get the official OTA. But: the rollout period is, according to the hotline employee, ending

next week

officially. (Meaning ... by then everyone should actually be able to get the OTA instantly. And if not, there might be something wrong with the installed FW.) So I should try again and again via HiCare and/or call again next week, if I still not get the OTA offered. Then, after the rollout period ended, they would be able to "push" it manually - as of today he claimed not to have access to these options yet. I don't know if this info about the rollout period is already known here - that's why I mention it in this detail.

So well ... I am unsure now what to do right now. Maybe I should be more patient and wait that week - it will be hard! :laugh:. In any case, I'll report back here - especially if I later decide to try your method 3 anyway. I already downloaded the files, just in case. (I hope it's okay to post it as a reply in this thread then, even though all of this is actually more troubleshooting/general stuff than directly Kang related :cool:.) And of course I would be happy to read any other reports about the above method 3, if someone tries (before I do) ^^