[ROM][11] DarkJoker360 AOSP 11 for Huawei P8 Lite 2017

Search This thread

latviandude

Senior Member
Jun 2, 2019
202
259
If it supports gsi/treble it will probably work.
BTW i'd recommend the crDRom11 from here it has lot's of features and works pretty good on my P10 Lite.
I use the crdrom-v306-210428-arm64-avZ.img.xz version.
C'mon dude, show some respect here! Your at AOSP 11 thread and ur talking here about some other project.. It's not cool. Btw AOSP 11 will give u more stability and performance, battery usage than any other GSI rom, so decide what you want.. And again watch where u post things..
 

latviandude

Senior Member
Jun 2, 2019
202
259
HI,
I followed ypur guide but i am getting bootloop. also tried another GIS image.
when should i flash decrypt zip file?

When i flashed the zip for decrypting it ran successfully. Currently i am installing the stock rom and flashing the rom again .

Thanks in advance
That's why you always have to read instructions first, but who does that..
 

latviandude

Senior Member
Jun 2, 2019
202
259
Hi
I make a lot of tests with my phone (PRA-LX1), I found 2 problems:
- The cast broadcast does not work (the phone will reboot when I activate it), i have test with an androidtv and with a Windows 10 (same problem)
- I can't activate VoLTE (no options in the setting menu)
Everything else seems to work (I have a doubt about the GPS which I do not find very sensitive)


Does anyone have some solutions ?
Could u please learn to read manuals? Thanks.
 
That's why you always have to read instructions first, but who does that..
I was able to do this in my honor 8 lite pra al00x
0. stock rom factory reset
1.unlock bootloader , twrp
2. flash this https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
in twrp.
(the one mentioned by darkjocker doesnt work for me)
3. install treble / GSI image as SYSTEM IMAGE in twrp
4. REBOOT TO RECOVERY (reboot else the system partition size will be shown as 4mb or something )
4. resize system using advanced wipe
5. reboot enjoy (wait for 5 minutes for first boot)

I am writing this so someone else can benefit

Thanks
 
Last edited:

11spqr

New member
Jun 27, 2019
3
2
Gentelmen,
Recently I've unlocked my Mate p10 Lite using latest patatonv service point method, and It is working ( I have bootloader unlocked right now), at this point I would ask you a question(especially the developer DarkJoker360), since RNE-L21 is also the hi6250 device could anyone tell me if is it save/possible to install this rom on my device, or some needed stuff was removed from kernel/android tree during the "optimalisation and stability" process for P8 Lite 2017 devices and it is almost sure RNE will not boot or its HW will have isuues on this rom?
Thanks in advance,
P.
 
Gentelmen,
Recently I've unlocked my Mate p10 Lite using latest patatonv service point method, and It is working ( I have bootloader unlocked right now), at this point I would ask you a question(especially the developer DarkJoker360), since RNE-L21 is also the hi6250 device could anyone tell me if is it save/possible to install this rom on my device, or some needed stuff was removed from kernel/android tree during the "optimalisation and stability" process for P8 Lite 2017 devices and it is almost sure RNE will not boot or its HW will have isuues on this rom?
Thanks in advance,
P.
should be able to flash this image or any other project treble images as long as project treble is supported by your device.
i think it should be supported
 

AltairFR

Member
Apr 22, 2021
34
13
Huawei P8lite/P8 Lite
New AOSP 11 update

  • Synced with latest AOSP 11 source code based on r36
  • Merged May 2021 security patches
  • Restored Android 10 signal indicator behavior

Check OP for more infos and download !

Donations
Support Group
NFC and CAST not working

For NFC : logcat show an error :

05-04 18:42:53.960 746 746 E NxpHal : i2c_fragmentation_status existing
05-04 18:42:53.960 746 746 E NxpFwDnld: NULL handler : unable to load the library file, specify correct path
05-04 18:42:53.960 746 746 E NxpFwDnld: Image extraction Failed - invalid imginfo or imginfolen!!
05-04 18:42:53.961 746 746 E NxpFwDnld: Error loading libpn54x_fw !!
05-04 18:42:53.961 746 746 E NxpHal : Wrong FW Version >>> Firmware download not allowed
05-04 18:42:53.961 746 746 E hw-IPCThreadState: binder thread pool (1 threads) starved for 120 ms
 

DarkJoker360

Recognized Developer / Recognized Contributor
Oct 20, 2015
2,623
3,655
18
Aradeo
NFC and CAST not working

For NFC : logcat show an error :

05-04 18:42:53.960 746 746 E NxpHal : i2c_fragmentation_status existing
05-04 18:42:53.960 746 746 E NxpFwDnld: NULL handler : unable to load the library file, specify correct path
05-04 18:42:53.960 746 746 E NxpFwDnld: Image extraction Failed - invalid imginfo or imginfolen!!
05-04 18:42:53.961 746 746 E NxpFwDnld: Error loading libpn54x_fw !!
05-04 18:42:53.961 746 746 E NxpHal : Wrong FW Version >>> Firmware download not allowed
05-04 18:42:53.961 746 746 E hw-IPCThreadState: binder thread pool (1 threads) starved for 120 ms
Do a proper flash of nfc fix.
 

AltairFR

Member
Apr 22, 2021
34
13
Huawei P8lite/P8 Lite
05-07 08:08:25.089 1135 1853 E AdbDebuggingManager: Caught an exception opening the socket: java.io.IOException: No such file or directory
05-07 08:08:25.582 3151 4466 E libnfc_nci: [ERROR:rw_mfc.cc(528)] RW_MfcDetectNDef
05-07 08:08:25.585 3151 4466 E libnfc_nci: [ERROR:rw_mfc.cc(877)] rw_mfc_readBlock: RW_MFC_SUBSTATE_WAIT_ACK
05-07 08:08:26.509 0 0 E [ 3619.847656s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.530 0 0 E [ 3619.859283s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.549 0 0 E [ 3619.879241s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.559 755 4469 E NxpTml : _i2c_write() errno : 5
05-07 08:08:26.559 755 4469 E NxpTml : PN54X - Error in I2C Write.....
05-07 08:08:26.560 755 4471 E NxpHal : write error status = 0x1ff
05-07 08:08:26.560 755 755 E NxpHal : write_unlocked failed - PN54X Maybe in Standby Mode - Retry
05-07 08:08:26.569 0 0 E [ 3619.899108s][pid:4469,cpu3,[email protected]][E/nfc] pn547_dev_write: i2c_master_send returned -121
05-07 08:08:26.569 0 0 E [ 3619.902435s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.589 0 0 E [ 3619.919189s][2021:05:07 08:08:26][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.error info -121, slave addr 0x28.
05-07 08:08:26.609 0 0 E [ 3619.939178s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.619 755 4469 E NxpTml : _i2c_write() errno : 5
05-07 08:08:26.619 755 4469 E NxpTml : PN54X - Error in I2C Write.....
05-07 08:08:26.620 755 4471 E NxpHal : write error status = 0x1ff
05-07 08:08:26.620 755 755 E NxpHal : write_unlocked failed - PN54X Maybe in Standby Mode - Retry
05-07 08:08:26.629 0 0 E [ 3619.958923s][pid:4469,cpu0,[email protected]][E/nfc] pn547_dev_write: i2c_master_send returned -121
05-07 08:08:26.629 0 0 E [ 3619.961853s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.649 0 0 E [ 3619.979187s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.669 0 0 E [ 3620.000061s][pid:4469,cpu1,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.679 755 4469 E NxpTml : _i2c_write() errno : 5
05-07 08:08:26.680 755 4469 E NxpTml : PN54X - Error in I2C Write.....
05-07 08:08:26.680 755 4471 E NxpHal : write error status = 0x1ff
05-07 08:08:26.680 755 755 E NxpHal : write_unlocked failed - PN54X Maybe in Standby Mode - Retry
05-07 08:08:26.689 0 0 E [ 3620.019256s][pid:4469,cpu3,[email protected]][E/nfc] pn547_dev_write: i2c_master_send returned -121
05-07 08:08:26.690 0 0 E [ 3620.022369s][pid:4469,cpu2,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.719 0 0 E [ 3620.049591s][pid:4469,cpu2,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.739 0 0 E [ 3620.070098s][pid:4469,cpu3,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.749 755 4469 E NxpTml : _i2c_write() errno : 5
05-07 08:08:26.750 755 4469 E NxpTml : PN54X - Error in I2C Write.....
05-07 08:08:26.750 755 4471 E NxpHal : write error status = 0x1ff
05-07 08:08:26.750 755 755 E NxpHal : write_unlocked failed - PN54X Maybe in Standby Mode - Retry
05-07 08:08:26.759 0 0 E [ 3620.089263s][pid:4469,cpu0,[email protected]][E/nfc] pn547_dev_write: i2c_master_send returned -121
05-07 08:08:26.759 0 0 E [ 3620.092315s][pid:4469,cpu1,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.789 0 0 E [ 3620.119659s][pid:4469,cpu1,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.809 0 0 E [ 3620.140045s][pid:4469,cpu1,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.819 755 4469 E NxpTml : _i2c_write() errno : 5
05-07 08:08:26.820 755 4469 E NxpTml : PN54X - Error in I2C Write.....
05-07 08:08:26.820 755 4471 E NxpHal : write error status = 0x1ff
05-07 08:08:26.820 755 755 E NxpHal : write_unlocked failed - PN54X Maybe in Standby Mode - Retry
05-07 08:08:26.829 0 0 E [ 3620.159210s][pid:4469,cpu1,[email protected]][E/nfc] pn547_dev_write: i2c_master_send returned -121
05-07 08:08:26.829 0 0 E [ 3620.162261s][pid:4469,cpu3,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.849 0 0 E [ 3620.179595s][pid:4469,cpu0,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.869 0 0 E [ 3620.199890s][pid:4469,cpu1,[email protected]]i2c_designware-hs fdf0d000.i2c: error info -121, slave addr 0x28.
05-07 08:08:26.879 755 4469 E NxpTml : _i2c_write() errno : 5
05-07 08:08:26.880 755 4469 E NxpTml : PN54X - Error in I2C Write.....
05-07 08:08:26.880 755 4471 E NxpHal : write error status = 0x1ff
05-07 08:08:26.880 755 755 E NxpHal : write_unlocked failed - PN54X Maybe in Standby Mode (max count = 0x6)
05-07 08:08:26.889 0 0 E [ 3620.219238s][pid:4469,cpu1,[email protected]][E/nfc] pn547_dev_write: i2c_master_send returned -121
05-07 08:08:27.209 755 755 E hw-IPCThreadState: binder thread pool (1 threads) starved for 703 ms
05-07 08:08:27.210 3151 4466 E libnfc_nci: [ERROR:nfc_ncif.cc(1689)] reset notification!!:0xa0
05-07 08:08:27.210 3151 4466 E libnfc_nci: [ERROR:nfc_ncif.cc(137)] nfc_ncif_cmd_timeout
05-07 08:08:27.221 3151 4466 E libnfc_nci: [ERROR:NativeNfcManager.cpp(819)] nfaDeviceManagementCallback: NFA_DM_NFCC_TIMEOUT_EVT; abort
05-07 08:08:27.222 3151 4466 E libnfc_nci: [ERROR:NativeNfcManager.cpp(860)] nfaDeviceManagementCallback: crash NFC service
05-07 08:08:27.223 3151 4466 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4466 (Thread-2), pid 3151 (com.android.nfc)
05-07 08:08:27.092 1135 1853 E AdbDebuggingManager: Caught an exception opening the socket: java.io.IOException: No such file or directory
05-07 08:08:27.322 4883 4883 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-07 08:08:27.323 4883 4883 F DEBUG : Build fingerprint: 'Android/prague/aosp_prague:11/RP1A.200720.011/prague:userdebug/test-keys'
05-07 08:08:27.323 4883 4883 F DEBUG : Revision: '0'
05-07 08:08:27.323 4883 4883 F DEBUG : ABI: 'arm64'
05-07 08:08:27.324 4883 4883 F DEBUG : Timestamp: 2021-05-07 08:08:27+0200
05-07 08:08:27.324 4883 4883 F DEBUG : pid: 3151, tid: 4466, name: Thread-2 >>> com.android.nfc <<<
05-07 08:08:27.324 4883 4883 F DEBUG : uid: 1027
05-07 08:08:27.324 4883 4883 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
05-07 08:08:27.324 4883 4883 F DEBUG : x0 0000000000000000 x1 0000000000001172 x2 0000000000000006 x3 00000071e1c7bd00
05-07 08:08:27.324 4883 4883 F DEBUG : x4 00000074e2b9a000 x5 00000074e2b9a000 x6 00000074e2b9a000 x7 0000000000035094
05-07 08:08:27.324 4883 4883 F DEBUG : x8 00000000000000f0 x9 1dfd16eb271f48ae x10 0000000000000000 x11 ffffffc0fffffbdf
05-07 08:08:27.324 4883 4883 F DEBUG : x12 0000000000000001 x13 0000000000000052 x14 00032115f66242b0 x15 00002e65f33536ed
05-07 08:08:27.324 4883 4883 F DEBUG : x16 00000074df891c80 x17 00000074df873870 x18 00000071e1648000 x19 0000000000000c4f
05-07 08:08:27.324 4883 4883 F DEBUG : x20 0000000000001172 x21 00000000ffffffff x22 00000071e1c7d000 x23 00000071e9a793f0
05-07 08:08:27.324 4883 4883 F DEBUG : x24 00000071e9613810 x25 00000071e9613810 x26 00000000ffffc400 x27 00000071e955af22
05-07 08:08:27.324 4883 4883 F DEBUG : x28 00000071e1c7c921 x29 00000071e1c7bd80
05-07 08:08:27.324 4883 4883 F DEBUG : lr 00000074df8272a0 sp 00000071e1c7bce0 pc 00000074df8272cc pst 0000000000000000
05-07 08:08:27.333 4883 4883 F DEBUG : backtrace:
05-07 08:08:27.334 4883 4883 F DEBUG : #00 pc 000000000004e2cc /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 88826ef406dbbed88068a41b1da6c056)
05-07 08:08:27.334 4883 4883 F DEBUG : #01 pc 0000000000035d4c /system/lib64/libnfc_nci_jni.so (android::nfaDeviceManagementCallback(unsigned char, tNFA_DM_CBACK_DATA*)+2724) (BuildId: fc5532d5132a05c44ce2890b77f7a054)
05-07 08:08:27.334 4883 4883 F DEBUG : #02 pc 000000000004278c /system/lib64/libnfc-nci.so (nfa_dm_nfc_response_cback(unsigned short, tNFC_RESPONSE*) (.cfi)+560) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #03 pc 000000000008a468 /system/lib64/libnfc-nci.so (nfc_ncif_cmd_timeout() (.cfi)+368) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #04 pc 000000000008e17c /system/lib64/libnfc-nci.so (nfc_ncif_proc_reset_rsp(unsigned char*, bool) (.cfi)+856) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #05 pc 0000000000084a88 /system/lib64/libnfc-nci.so (nci_proc_core_ntf(NFC_HDR*) (.cfi)+348) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #06 pc 000000000008addc /system/lib64/libnfc-nci.so (nfc_ncif_process_event(NFC_HDR*) (.cfi)+792) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #07 pc 000000000008f058 /system/lib64/libnfc-nci.so (nfc_task(unsigned int) (.cfi)+760) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #08 pc 00000000000c1494 /system/lib64/libnfc-nci.so (gki_task_entry(void*) (.cfi)+280) (BuildId: 8541b56073bdb4dc921992680dc971a4)
05-07 08:08:27.334 4883 4883 F DEBUG : #09 pc 00000000000afd4c /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64) (BuildId: 88826ef406dbbed88068a41b1da6c056)
05-07 08:08:27.334 4883 4883 F DEBUG : #10 pc 0000000000050288 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 88826ef406dbbed88068a41b1da6c056)
05-07 08:08:27.447 4822 4841 E Surface : freeAllBuffers: 1 buffers were freed while being dequeued!
05-07 08:08:27.448 4822 4841 E Surface : freeAllBuffers: 1 buffers were freed while being dequeued!
05-07 08:08:27.449 1170 1252 E BufferQueueProducer: [Toast#0](id:49200000062,api:0,p:-1,c:1170) disconnect: not connected (req=1)
05-07 08:08:27.923 4883 4883 E crash_dump64: AM data write failed: Broken pipe
05-07 08:08:27.924 688 688 E tombstoned: Tombstone written to: /data/tombstones/tombstone_01
05-07 08:08:28.025 1135 1163 E libprocessgroup: CgroupMap::FindController called for [1135] failed, RC file was not initialized properly
05-07 08:08:28.025 1135 1163 E libprocessgroup: CgroupMap::FindController called for [1135] failed, RC file was not initialized properly
05-07 08:08:28.045 4891 4891 E libprocessgroup: CgroupMap::FindController called for [4891] failed, RC file was not initialized properly
05-07 08:08:28.045 4891 4891 E libprocessgroup: CgroupMap::FindController called for [4891] failed, RC file was not initialized properly
05-07 08:08:28.046 4891 4891 E libprocessgroup: Failed to make and chown /uid_1027: Read-only file system
05-07 08:08:28.236 4891 4911 E libprocessgroup: CgroupMap::FindController called for [4891] failed, RC file was not initialized properly
05-07 08:08:28.237 4891 4911 E libprocessgroup: CgroupMap::FindController called for [4891] failed, RC file was not initialized properly
05-07 08:08:28.243 4891 4914 E libnfc_nci: [ERROR:gki_ulinux.cc(98)] gki_task task_id=0 terminating
05-07 08:08:28.361 755 755 E NxpHal : i2c_fragmentation_status existing
05-07 08:08:28.364 755 755 E NxpFwDnld: Freeing Mem for Dnld Context..
05-07 08:08:28.365 755 755 E hw-IPCThreadState: binder thread pool (1 threads) starved for 122 ms
05-07 08:08:28.453 4891 4915 E libnfc_nci: [ERROR:nfa_ee_act.cc(2154)] nfa_ee_nci_mode_set_rsp p_rsp->status:0x00
05-07 08:08:29.094 1135 1853 E AdbDebuggingManager: Caught an exception opening the socket: java.io.IOException: No such file or directory
05-07 08:08:29.284 4822 4841 E Surface : freeAllBuffers: 1 buffers were freed while being dequeued!
05-07 08:08:29.285 4822 4841 E Surface : freeAllBuffers: 1 buffers were freed while being dequeued!
05-07 08:08:29.285 1170 1172 E BufferQueueProducer: [Toast#0](id:49200000062,api:0,p:-1,c:1170) disconnect: not connected (req=1)

For the problem of the crash followed by a restart of the NFC service in my PRA, the problem is described here https://github.com/phhusson/treble_experimentations/issues/1699
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    hello, first of all, I would like to say that the rom is very nice and fluent, but the camera gives an error to insert sd card and no files can be downloaded from the internet
    Hi.

    I have already signal this bug and post the workaround , in a Lineage 18 post, see :


    So after format data you must set the right permission and owner on /data/media/0 subfolder or (/data/media)

    Just open a terminal in TWRP and type

    cd /data/media
    chown media_rw:media_rw 0
    chmod 770 0
    1
    Restored Q signal strength behavior !

    It's not perfect but now 2,3,4 bars are kinda working like Q.
    Still better than nothing i believe.
    Hi Joker i see that you have build number with 400 C432 without Error. Is that because of new Kernel? If i remember you had 378 C432 on older Screens and working build number.

    if i have latest Stock 398 C432 on my p10 lite i never get it work without error. after downgrade to 378 C432 it works on custom rom without error. so how about that...can i upgrade to stock rom 398 again and get then custom rom then without error in build number.

    How about the selinux status...is permissive possible with the new kernel? But i think i know the answer right now :)

    great thanks for all the work you Hami and all the others doing..love it

    solong
    speedson 🤘 🙃 🤘
    1
    Hi can I ask why cant we set the selinux to permissive in this device
    Hi...

    the stock Kernel does not have funtionallity to set the Selinux State to permissive. Cause of this its not able to get dolby atmos or Viper4Android working. So you need a custom Kernel for that. I found after searching a while the Elemental-KernelV5.8-EMUI8.0.zip and the Version 21 indeed have Selinux permissive but after flashing this Kernel. My WAS-LX1A wasnt possible to connect with Wlan any more. But i did notice that the Developer from this Elemental-KernelV5.8-EMUI8.0.zip is back in Buissnes here on XDA. So we will see if something will coming in the future :)

    solong
    speedson
    🤘 🙃 🤘

    Hey bro i'm running it on build WAS-LX1A 8.0.0.394 (C432), But i'm using this recovery and it lets me boot the system.
    Hi...

    the Problem if i startet from Stock 8.0.0C432B398 is the Build-Number Error. It doesnt work with B398 Firmware and it doesnt matter wich TWRP i used for flashing. The A11 v2.5 AIO fix doesnt help and all other patches also doesnt help ti fix it.
    So one Day take a look at the Screenshot from Darkjoker360 and there was the B378 C432 Firmware in Build Number without Error.
    Cause of this i downgrade to the same for my Device and after that the Error was never seen in my Build Number...wayne wich Firmware i did test.
    Now i see on newer Screen that he have now B400 C432 on his Device. Cause of this i asking him. I know he have p8 lite 2017 and p10 lite but Lineagos 18.1 and AOSP firmware running on on my Device to. Now there is a new Kernel for p8 lite 2017 and same time he have now B400 C432. Is it cause of the new Kernel and did the Kernel running on p10 lite? Thats the big Question that i asking for :)

    BTW i didnt use TWRP 3.4.0.0 cause i often have Problem that i doing the flash step by step like i should and get bootloop. Then i have notice that i didnt get bootloop when i use fastboot and the rest of the step by step and i wonder....it works pretty well. So i change my TWRP to twrp_p10_lite_0.5_test.img. Since that i never have Problems like bootloop.

    solong
    speedson🤘🙃🤘
  • 11
    Hi,

    1566531179-9526.jpg


    DarkJoker360 AOSP 11 for Huawei P8 Lite 2017

    *** Stable Version ***

    About
    Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.



    Working
    * Touchscreen
    * Audio
    * Boot
    * Bluethoot
    * Internal/External storage
    * Mtp / Adb
    * Sensors
    * Wifi
    * RIL
    * Camera
    * NFC
    * FP gestures​


    Not Working
    * You tell me


    NOTE: The signal icon is buggy due to Huawei weird ril implementation, I am still looking to fix it over the new Android 10-11 telephony changes.

    Installation
    * you must have TWRP installed, use this one (make sure to have the unofficial Android 11 one ! )
    WARNING: You must be decrypted before installing it otherwise it won't boot. (Read second post.)
    * go to TWRP
    * format data
    * reboot to TWRP again
    * do a full wipe (system, data, cache, dalvik/art cache) !
    * reboot to bootloader
    * extract AOSP 11
    * run: fastboot flash system <drag system.img here>
    * reboot to TWRP
    * resize system
    * flash gapps (optional)
    * flash NFC.zip
    NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
    * reboot to System
    * Enjoy !!!​


    Update
    * reboot to TWRP and do a wipe cache, dalvik/art cache
    * reboot to bootloader
    * extract AOSP 11
    * run: fastboot flash system <drag system.img here>
    * reboot to TWRP
    * resize system
    * flash gapps (optional)
    * flash NFC.zip
    NOTE: this zip is needed for having working NFC. DO NOT IGNORE IT !
    * reboot to System
    * Enjoy !!!​


    If you are getting Error 70 while flashing gapps just resize system from TWRP !
    If gapps are giving network errors or other kind of errors install them after first boot !

    Download



    Please support my work, it's very important! Thanks
    DONATIONS

    Regards !
    9
    NOTES
    * For root method read this post, for rooting with magisk read this instead.
    * If you face corrupted storage issues you need to go back on emui and re-install the rom.
    * I recommend NikGapps core with SetupWizard add-on.
    * Use 8.0.0.360 or maximum .400 firmware for booting the rom.
    * Gapps can may give "Uncertified device" error and abort the google account login, use this guide to fix it (thanks to @latviandude )
    * If you want VoLTE/Wifi Calling working flash this zip

    ** You must be decrypted for booting this rom **
    Before following the installation steps format data and flash this file via TWRP.
    9
    New AOSP 11 update

    * Synced with latest AOSP 11 source code based on r32
    * Merged March 2021 security patches
    * Fixed bootloop in some cases
    * Fixed ADB
    * Removed useless overlays
    * More build info fixes
    * Fixed AOSP ScreenRecorder
    * Performance improvements
    * Decreased system partition usage (now AOSP will just take 1,3gb)
    * Fixed a gnss service crashing since A10, resulting in costant wakelocks, logspams and gps failures
    * Added dark theme on Dialer and Messaging apps

    NOTE: Clean flash is recommended

    Check OP for more infos and download !

    Donations
    Support Group
    7
    Magisk-phh v22.0 is now working !

    Only the linked version will work.

    1- Install magisk apk
    2- Go to twrp & flash MAGISKA11-a-only
    3- Flash Magisk-v22-canary-phh
    4- Reboot and enjoy

    Download

    Thanks to @Hami_Do
    6
    New AOSP 11 update

    • Synced with latest AOSP 11 source code based on r34
    • Merged April 2021 security patches
    • Fixed animations lags and janks
    • Fixed wired headphones not being detected
    • Fixed gps
    • Fixed ril crashes for dual sim devices
    • Updated APN configs from LineageOS
    • Fixed ril crashes with some carriers
    • Fixed Netflix playback
    • Adjusted screen brightness
    • Fixed minimum brightness too high
    • Enabled Wifi Display
    • Improved Signal Strenght
    • Ignored RSSNR signal implementation, as our RIL is not using it
    • Completely disabled useless gnss_watchlssd_thirdparty service causing drains and logspams

    Check OP for more infos and download !

    Donations
    Support Group