Le Pro 3 Elite (X722) Lineage OS

Nov 7, 2017
43
5
0
we have opened the petition on the website change org write in search of Kernel sources for LeEco Le Pro 3 Elite X722 and подпишистесь please. We will try to reach leeco
Just ordered the x722 with the hope it will be unlocked soon.. It was this one or the Meizu M6 note without band 20 which will give me slight problems in my country..

Give me the link of the petition I hope for the best :) Maybe some chinese developpers should be involved?
 

ilya515

Member
Nov 8, 2017
12
2
0
Saint Petersburg
=)

Just ordered the x722 with the hope it will be unlocked soon.. It was this one or the Meizu M6 note without band 20 which will give me slight problems in my country..

Give me the link of the petition I hope for the best :) Maybe some chinese developpers should be involved?
10 messages are necessary to me that I could throw off the reference)))
 

slothdnk

Member
Apr 30, 2010
16
11
0
X722 Kernel Source

The x722 kernel source is in the x727 source tree. the only change I made to get Lineage 15.0 running was to the binary blob of the gpu (sd820 != sd821)
So it is not the kernel thats missing. If you were to put the GPU blob in the Lineage 14.1 build most (if not all) will be working.
 
  • Like
Reactions: sk8223 and evlo
Nov 7, 2017
43
5
0
The x722 kernel source is in the x727 source tree. the only change I made to get Lineage 15.0 running was to the binary blob of the gpu (sd820 != sd821)
So it is not the kernel thats missing. If you were to put the GPU blob in the Lineage 14.1 build most (if not all) will be working.
Really? You cracked the code..? How come no-one has ever seen this? And maybe more importantly can you tell the world how you did it(in less tech language pls :) )?
 

ilya515

Member
Nov 8, 2017
12
2
0
Saint Petersburg
firmware

The x722 kernel source is in the x727 source tree. the only change I made to get Lineage 15.0 running was to the binary blob of the gpu (sd820 != sd821)
So it is not the kernel thats missing. If you were to put the GPU blob in the Lineage 14.1 build most (if not all) will be working.
and when you release an insertion? :)
 

evlo

Senior Member
Oct 6, 2008
144
23
18
Really? You cracked the code..? How come no-one has ever seen this? And maybe more importantly can you tell the world how you did it(in less tech language pls :) )?
He/she already wrote detailed guide in los15 for x720/x727 thread, you can trying same changes for los14 build config and upload it for everyone.
OS life :D

https://forum.xda-developers.com/showpost.php?p=74446314&postcount=150
I guess just get cm-14.1 from lineage repo and you are golden.

I don't know if you can crated build scrip for zl0 that would include getting all the binary drivers etc. and push it to git to be included as that would really help community. I guess you will just get permission denied, but definitely worth a try.
I vaguely remember there is something like proposal on github for patches, so maybe that is the way?

There is also nice guide for zl1 on lineage wiki you can use when you are lost.
 
Last edited:
Nov 7, 2017
43
5
0
He/she already wrote detailed guide in los15 for x720/x727 thread, you can trying same changes for los14 build config and upload it for everyone.
OS life :D

https://forum.xda-developers.com/showpost.php?p=74446314&postcount=150
I guess just get cm-14.1 from lineage repo and you are golden.

I don't know if you can crated build scrip for zl0 that would include getting all the binary drivers etc. and push it to git to be included as that would really help community. I guess you will just get permission denied, but definitely worth a try.
I vaguely remember there is something like proposal on github for patches, so maybe that is the way?

There is also nice guide for zl1 on lineage wiki you can use when you are lost.
As I'm pretty new to the android world, and since my package didn't arrive yet, I don't think I'm the right person for performing this step, however if someone tries you can def confirm this over here!
 

evlo

Senior Member
Oct 6, 2008
144
23
18
I'm trying, but i don't have powerful enough pc or large enough hdd to build it, so i'm trying on the server i rented for this.

My point was more in a way like there is lot of users with this phone and anyone can learn and do it and not ask again and again, if anybody wanted to do it he/she would do it even without asking, obvs.

UPDATE: it is not possible to get OEM binary drivers and stuff without root, so i installed magisk, tried to access root in x-plore file manager, but it is not able to access it, working till infinity, same thing when i tried root checker app from play store, so I guess it is the end for me, i don't understand the root witchcraft, i thought adb would just call su, but it is something weird. Also i thought i would see some magisk manager in app drawer or something, but nothing is there
Also when file extractor hits java part i just get outOfMemory exceptions from my VM so i guess i really don't have powerful enough pc
 
Last edited:
  • Like
Reactions: sk8223
Oct 13, 2017
34
3
0
I have built the latest lineage-15.0 repo. Unfortunately I'm seeing black screen during boot.
Don't know what's wrong. I have replaced a530_zap files but perhaps they are incorrect?

folder path in the repo: vendor/leeco/zl1/proprietary/vendor/firmware/
folder path in the generated system.new.dat (system.img): /system/vendor/firmware
Code:
2e9ddbd0569cd468e4f510ba78161f5f  a530_gpmu.fw2
f7efa6802cb6793bafdfc0fee770e6cb  a530_pfp.fw
a37bd5b4c74ef04c29e5ed7c8d46bc90  a530_pm4.fw
bb28299602fe8d061c3999b91695bafb  a530_zap.b00
5ad3007e4ddc16b896b851a1f87e9c8e  a530_zap.b01
3d49a1b70c906b950d25c6502748110c  a530_zap.b02
39a7aa872313f20c95c2f4ccbc36c153  a530_zap.elf
86d572d397558759964f41d02cf19058  a530_zap.mdt
509665e3c3c13194c6a9780085f8ba37  a530v1_pfp.fw
5e04bd3c82303a1f09554548ffa8f827  a530v1_pm4.fw
105095e441b51baf624fe4caf4a6314c  a530v2_seq.fw2
169b8c19d944b88d5ad9df114e111f5c  a530v3_gpmu.fw2
d0de184692249ff12eebc90c4560a8ac  a530v3_seq.fw2
32fe4175f974eb62779db4387205a25c  libpn548ad_fw.so
416516bc90ee3738ba669ebac4cda909  widevine.b00
d4460cd335e495d82ada8bcfde5ca0d5  widevine.b01
a3d849b3a643a7c93b9ec297e0c5ad3d  widevine.b02
c5b7d4081abe9268decfaa9826dfb557  widevine.b03
2700b13b90a9ad06141f124208b519d6  widevine.b04
d34d4aed4fbe9d696719f69182d0bceb  widevine.b05
ab7dd30552e48aa3ea6fbc1f6687231f  widevine.b06
d826c2d41eb86c513f10d1485d8ed64c  widevine.mbn
9badb8177597d45943a160a4720e37b1  widevine.mdt

and listing:

-rw-r--r-- 1 root root   8052 Jan  1  2009 a530_gpmu.fw2
-rw-r--r-- 1 root root  15876 Jan  1  2009 a530_pfp.fw
-rw-r--r-- 1 root root  19572 Jan  1  2009 a530_pm4.fw
-rw-r--r-- 1 root root    148 Jan  1  2009 a530_zap.b00
-rw-r--r-- 1 root root   6536 Jan  1  2009 a530_zap.b01
-rw-r--r-- 1 root root   4900 Jan  1  2009 a530_zap.b02
-rw-r--r-- 1 root root  17188 Jan  1  2009 a530_zap.elf
-rw-r--r-- 1 root root   6684 Jan  1  2009 a530_zap.mdt
-rw-r--r-- 1 root root  11388 Jan  1  2009 a530v1_pfp.fw
-rw-r--r-- 1 root root  15424 Jan  1  2009 a530v1_pm4.fw
-rw-r--r-- 1 root root   2604 Jan  1  2009 a530v2_seq.fw2
-rw-r--r-- 1 root root   8184 Jan  1  2009 a530v3_gpmu.fw2
-rw-r--r-- 1 root root   2604 Jan  1  2009 a530v3_seq.fw2
lrw-r--r-- 1 root root     29 Jan  1  2009 btfw32.tlv -> /bt_firmware/image/btfw32.tlv
lrw-r--r-- 1 root root     29 Jan  1  2009 btnv32.b15 -> /bt_firmware/image/btnv32.b15
lrw-r--r-- 1 root root     29 Jan  1  2009 btnv32.bin -> /bt_firmware/image/btnv32.bin
-rw-r--r-- 1 root root  38031 Jan  1  2009 libpn548ad_fw.so
-rw-r--r-- 1 root root    456 Jan  1  2009 widevine.b00
-rw-r--r-- 1 root root   6664 Jan  1  2009 widevine.b01
-rw-r--r-- 1 root root 266795 Jan  1  2009 widevine.b02
-rw-r--r-- 1 root root  34752 Jan  1  2009 widevine.b03
-rw-r--r-- 1 root root    480 Jan  1  2009 widevine.b04
-rw-r--r-- 1 root root    160 Jan  1  2009 widevine.b05
-rw-r--r-- 1 root root   2736 Jan  1  2009 widevine.b06
-rw-r--r-- 1 root root 325808 Jan  1  2009 widevine.mbn
-rw-r--r-- 1 root root   7120 Jan  1  2009 widevine.mdt
and attached build.prob.txt from the generated system.new.dat

@slothdnk : Could you please attach md5s for your files and check build.prob for comparison. I used rhash (rhash -r --md5 *).

---------- Post added at 01:04 PM ---------- Previous post was at 01:03 PM ----------

I'm trying, but i don't have powerful enough pc or large enough hdd to build it, so i'm trying on the server i rented for this.

My point was more in a way like there is lot of users with this phone and anyone can learn and do it and not ask again and again, if anybody wanted to do it he/she would do it even without asking, obvs.

UPDATE: it is not possible to get OEM binary drivers and stuff without root, so i installed magisk, tried to access root in x-plore file manager, but it is not able to access it, working till infinity, same thing when i tried root checker app from play store, so I guess it is the end for me, i don't understand the root witchcraft, i thought adb would just call su, but it is something weird. Also i thought i would see some magisk manager in app drawer or something, but nothing is there
Also when file extractor hits java part i just get outOfMemory exceptions from my VM so i guess i really don't have powerful enough pc
see post above, if you could post yours. I could build 14.1 as well after this issue is fixed :)
 

Attachments

Last edited:

evlo

Senior Member
Oct 6, 2008
144
23
18
I don't understand what exactly would you like me to share.

I was not able to extract all the files [i guess magisk root just don't work for me, when i try some app that uses root it hangs till infinity, even just su in terminal the on phone, i don't see any reason why it would work for adb], so I was trying zl0 mixed with 102 files that were missing/not extracted that i used from zl1, interestingly 502 files were still different.

Also i think the qcom common dependency (from 8996 common) error where preparing or compiling is bogus and the binaries from "extract files" are just not prepared how they should be for current LOS build tools.

Do you still want files, I extacted, that you should use to replace zl1 in vendor directory and build prep i prepaired for my build?

Do you know if there is any provider of trial service with machine powerful enough to build? It seems that reasonable minimum would be 8G ramd and 100G SDD + some recent CPU. All the ones I have found are 4G and that just fails on out of memory or if I set XMS to 3G it fails on being too slow :D, I can't run VM on my PC as I can't give it more then 2G ram.
 
Last edited:
Oct 13, 2017
34
3
0
I don't understand what exactly would you like me to share.
I'm trying to figure out if my issue is related to a invalid/missing file(s) or config. If you could
compare your a530_zap hashes against mine in case I'm using wrong source ROM. I used ROM image for
"extract files" step.
@slothdnk do you think you could upload your ROM zip? Diffing files might reveal the reason. I can provide you server if needed.
 

evlo

Senior Member
Oct 6, 2008
144
23
18
a530 only from zl0:

Code:
MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530v1_pfp.fw:
509665e3c3c13194c6a9780085f8ba37

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530v1_pm4.fw:
5e04bd3c82303a1f09554548ffa8f827

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530v2_seq.fw2:
105095e441b51baf624fe4caf4a6314c

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530v3_gpmu.fw2:
169b8c19d944b88d5ad9df114e111f5c

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530v3_seq.fw2:
d0de184692249ff12eebc90c4560a8ac

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_gpmu.fw2:
2e9ddbd0569cd468e4f510ba78161f5f

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_pfp.fw:
f7efa6802cb6793bafdfc0fee770e6cb

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_pm4.fw:
a37bd5b4c74ef04c29e5ed7c8d46bc90

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_zap.b00:
bb28299602fe8d061c3999b91695bafb

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_zap.b01:
5ad3007e4ddc16b896b851a1f87e9c8e

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_zap.b02:
3d49a1b70c906b950d25c6502748110c

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_zap.elf:
39a7aa872313f20c95c2f4ccbc36c153

MD5 hash of vendor\leeco\zl1\proprietary\etc\firmware\a530_zap.mdt:
86d572d397558759964f41d02cf19058
all i managed to export from zl0: https://pastebin.com/SZfWfHrd


I randomly picked a530v2_seq.fw2 from yours and mine export and result is:
105095e441b51baf624fe4caf4a6314c < yours
105095e441b51baf624fe4caf4a6314c < mine
so same
And just for fun, zl1 a530v2_seq.fw2 MD5?
105095e441b51baf624fe4caf4a6314c
same

---------- Post added at 08:23 PM ---------- Previous post was at 08:17 PM ----------

UPDATE: I compared ALL files in \proprietary\etc\firmware\ between ZL0 and ZL1 export and the result is:



... 323 files export into /vendor/zl1 (don't get confused here here by accident :D ) are different between zl0 and zl1 exports

I guess the rest of the different files are in qcom common folder

---------- Post added at 08:25 PM ---------- Previous post was at 08:23 PM ----------

a530_zap.b01:
yours: 5ad3007e4ddc16b896b851a1f87e9c8e
mine: 5ad3007e4ddc16b896b851a1f87e9c8e
zl1: 4f9b7d28ab442197faa839bd66e6a785

Seems that you are set and there aren't issues with, for example exporting encrypted files or something

---------- Post added at 08:36 PM ---------- Previous post was at 08:25 PM ----------

BTW is ti possible to use any rom image with extract files? I thought you could only do it with LOS zips.

Sorry for different formating, i'm on windows so I used different tool to get MD5s
I hope this helps at least a bit, i'm bit confused about /etc/firmware I have vs only /firmware you and @slothdnk have
 
Last edited:
Oct 13, 2017
34
3
0
BTW is ti possible to use any rom image with extract files? I thought you could only do it with LOS zips.
Thanks, wanted rule that one out.
I used "X722_stable_20s_NoRoot_tora33.zip" ROM as my source for "Extract proprietary blobs" step and Adreno driver (a530_zap) files.

Ik will try to build it later today as It don't have my desktop right now. Do you have a zip that we can have meanwhile ?
Great, let us know your findings! In order to build on my distro I had to downgrade both python (from v3 to v2) and 'curl' app. @slothdnk 's guide doesn't mention about picking patches which I did.

If there's a way to enable file logging (or logcat) for GPU and boot events that might help track if you face the same boot-time issue.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone