[ROMs][TREBLE] OpenKirin AOSP Collection

[OldDroid]

Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.

This is the device support section for: Huawei Mate 8.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.

We support 4 ROMs in total as of now - LineageOS (Unofficial), CarbonROM (Official), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net

Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk

Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw

XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei Mate 8

Contributors
OldDroid, XePeleato, rcstar6696, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS, OmniRom

Version Information
Status: Beta

Created 2018-08-13
Last Updated 2018-08-13

 

[apat26]

Thanks @OldDroid for all the efforts.
I have used all 4 and all are working awesome, especially RR beta 2.
Awesome work....

 

[daser4berlin]

What about the deep sleep issue on 950?
Will it be fixt in the future?

 

[malekowsky]

Hey guys, I have a spare mate 8 which is actually on build 829. Followed the instructions to the letter on Openkirin website, on RR beta 2right now,. But each time I reboot it, it says that decryption is unsuccessful and to reset the device. Is this normal?

 

[apat26]

Hey guys, I have a spare mate 8 which is actually on build 829. Followed the instructions to the letter on Openkirin website, on RR beta 2right now,. But each time I reboot it, it says that decryption is unsuccessful and to reset the device. Is this normal?

Yes, decryption problem remains with OK ROMs. You need to either decrypt with twrp or with fstab through adb shell. Once done, you won't get it again till you flash stock room again.

 

[malekowsky]

Yes, decryption problem remains with OK ROMs. You need to either decrypt with twrp or with fstab through adb shell. Once done, you won't get it again till you flash stock room again.

Thank you buddy, basically same issue I ran in to when I tested AOSP a while ago except that ROMS are now more elaborated and functioning smoothly.

 

[Georgian51]

I try rr beta 2 and omnirom but i have only one sim (sim 2) sim 1 does not exist.Nice sim 2 does not work with all operators. For the idea?

 

[deja_wu]

For everyone else who has been struggling with the decryption issue, I finally figured out how to get OpenKirin's LineageOS image to boot without first encrypting. You lose FDE in the process (a tradeoff I'm willing to make to get a working phone).

1. Start with stock EMUI 8 and a stock recovery. You can get EMUI 8 using the HWOTA packages. If, anywhere in the process you make a mistake, you can restore EMUI by flashing the HuRUpdater zip.
1a. Boot into EMUI 8 to make sure it is intact. You may need to run a factory reset from the recovery (the complete, stock recovery which you can reach by holding Power + VolUp. Do not reset from eRecovery.) Once you see the language select screen you can be satisfied that it works.

2. Boot into fastboot (power off, hold VolDown and plug into USB).

3. Flash your OpenKirin ROM of choice:

fastboot flash system openkirin_ROMNAME.zip

4. Exit fastboot and immediately perform a factory reset from stock recovery, just like the OpenKirin instructions tell you to. Do not boot into the OS first. For me, the factory reset appears to fail. I ran it anyway just to be sure, and it does seem to make a difference even if it fails.

5. Once the reset is done, return to fastboot.

6. Flash this version of TWRP (originally for Mate 9):

fastboot flash recovery_ramdisk twrp_mate9_0.1.img

7. Boot into TWRP recovery: run

fastboot reboot

, unplug the phone, and hold down VolUp until the logo appears. (You have to be quick.)

8. Once in TWRP, load up an adb shell and remount /vendor with write perms:

mount -o remount,rw /dev/block/bootdevice/by-name/vendor /vendor

If your devices differ, use

df -h .

to see what the device name is.

9. Alter the following files, removing any boot flags that say "avb" or "forceencrypt":

/vendor/etc/fstab.f2fs.hi3650
/vendor/etc/fstab.ext4.hi3650

Make sure the comma-separated lists stay valid.

10. Save your files, and tell TWRP to reboot to system.

 

[michii_fr34k]

I try rr beta 2 and omnirom but i have only one sim (sim 2) sim 1 does not exist.Nice sim 2 does not work with all operators. For the idea?

I also had that problem, a developer told me its because of the cdma modem, which is in the AL10 variant. Max connection i got was Edge.
So im back to stock an wait till they fix that problem.

 

[Georgian51]

Are these projects working for mate 8? I see that the rom has not been updated

 

[ceriqdesign]

Are these projects working for mate 8? I see that the rom has not been updated

yup this is for Mate 8..there are few peoples already tested it but seems like there are still got few bugs like signal and etc. i'm waiting for a new build and will test it.

 

[lindsaytheflint]

I'm another that has tested LOS, RR, and OR, and all have the issue with not getting any SIM card signal. Obviously I can't use, as a smartphone without the phone, isn't that smart.

Keenly hoping this gets resolved, as I certainly like the look of these ROMs.

 

[Georgian51]

I'm another that has tested LOS, RR, and OR, and all have the issue with not getting any SIM card signal. Obviously I can't use, as a smartphone without the phone, isn't that smart.

Keenly hoping this gets resolved, as I certainly like the look of these ROMs.

What version did you test?
On AL10 I tried and I had the same problems. I went to
* DL00 and no problems

 

[lindsaytheflint]

What version did you test?
On AL10 I tried and I had the same problems. I went to
* DL00 and no problems

I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.

Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?

If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?

 

[Georgian51]

I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.

Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?

If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?

I made a rebrend at DL00. Try the variant you say, maybe it works

 

[ceriqdesign]

I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.

Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?

If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?

Did you flashed cust after upgraded to B596?if you noticed that you don't have signal or no service at that time?

 

[lindsaytheflint]

Did you flashed cust after upgraded to B596?if you noticed that you don't have signal or no service at that time?

Yes, and signal was fine at B596. Signal is also fine on either stock b829 or KangVIP b828/829.

Firmware Finder's been offline, but looks like it's coming back online soon, so I'll try installing DL00 b829 stock ROM, then OpenKirin, to see if that helps.

(I tried flashing just DL00 b829 Cust.img yesterday, but it didn't seem to make a difference.)


For those that do have working signal on OpenKirin, what full base stock ROM did you come from? i.e. b829, DL00, AL10 etc, and which country region C00, C92, C17, etc?

 

[Brokendroid994]

Hi, looks like I am having the same signal issues as every one else on NXT-AL10. Have flashed back to stock EMUI 8 for now after hard bricking my device and using Dc-Phoenix to recover by shortinng out the testpoints.

Like every one else have been looking in to possible solutions. After booting in to open kirin roms and looking in to phone info in setting I noticed my IMEI was blank. At this point flashed back to stock after hard bricking and loaded in to HCU-client to repair fortunately this was not the case and IMEI was intact.

So digging around other Huawei boards I fond this maybe a possible solution to signal issue. Don't have time to try just now will let you know how it goes.

Honor 6X [GUIDE] Update to EMUI 8

https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806

found in instruction on first post

Bugs Fixing:
Unknown or invalid IMEI:Use any root file manager and go to cust/all/cn/prop/local.prop and edit local.prop change the line full network support: true to false

sounds like the problem we are all having with our devices.

If anyone tries this before me can you let us all know

 

[lindsaytheflint]

Hi, looks like I am having the same signal issues as every one else on NXT-AL10. Have flashed back to stock EMUI 8 for now after hard bricking my device and using Dc-Phoenix to recover by shortinng out the testpoints.

Like every one else have been looking in to possible solutions. After booting in to open kirin roms and looking in to phone info in setting I noticed my IMEI was blank. At this point flashed back to stock after hard bricking and loaded in to HCU-client to repair fortunately this was not the case and IMEI was intact.

So digging around other Huawei boards I fond this maybe a possible solution to signal issue. Don't have time to try just now will let you know how it goes.

Honor 6X [GUIDE] Update to EMUI 8

https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806

found in instruction on first post

Bugs Fixing:
Unknown or invalid IMEI:Use any root file manager and go to cust/all/cn/prop/local.prop and edit local.prop change the line full network support: true to false

sounds like the problem we are all having with our devices.

If anyone tries this before me can you let us all know

Tried this, and confirmed that my IMEI is also missing from OpenKirin, but after changing the local.prop file and rebooting, it was worse. Rather than the SIM being detected, but having no signal, the SIM was no longer being detected at all (slot showing as empty). Tried OpenKirin RR.

 

[acbka]

For everyone else who has been struggling with the decryption issue, I finally figured out how to get OpenKirin's LineageOS image to boot without first encrypting. You lose FDE in the process (a tradeoff I'm willing to make to get a working phone).

9. Alter the following files, removing any boot flags that say "avb" or "forceencrypt":

/vendor/etc/fstab.f2fs.hi3650
/vendor/etc/fstab.ext4.hi3650

10. Save your files, and tell TWRP to reboot to system.

Hello . I modded this files .
remove "avb" flags and change "forceencrypt" to "encryptable" . work fine (Resurrection Remix OS Beta 3
Released September 27, 2018 - 575.05MB , NXT-L29 (dual sim) changed to NXT-DL00)
View attachment hi3650.rar