[DEVICE TREE][PORT][MT6735] Device tree for LG K350xxx

Search This thread

Professor Woland

Senior Member
Mar 10, 2016
353
55
Redmi Note 9 Pro
Hi I have working on this some time and it should work, I'm not a real developer and don't have big knowledge. This is ported from Wileyfox porridge.
I'm posting this here because I don't have a PC to try to build on it (I have single core celeron with 512mb RAM, belive me or not) and also my phone's bootloader is still locked because I don't want to break warranty yet because I had some problems with very low R/W speeds. So if there is anyone who know what should be done and would like to try to build ROM or help with device tree, please feel free to do that.

NOTICE: If you have model other then 8GB K350nds you should edit values of partition sizes in BoardConfig.mk Better solution will be if I known difference in size of partitions for each model, and even than I'm not sure what attribute from /proc/cmdline I should compare to get it right (in init_mm1v.cpp)

Device tree https://github.com/ProfessorWoland/android_device_lge_mm1v
You'll also need common tree https://github.com/LineageOS/android_device_cyanogen_mt6735-common

About kernel if you try to build ROM:
Kernel source is published by LG here http://opensource.lge.com/osSch/list?types=ALL&search=k350
But also there is kernel on Lineage OS repo https://github.com/LineageOS/android_kernel_cyanogen_mt6735
It should work also if you just add muse6735_m1v_m_defconfig file from your kenel source to /arch/arm/configs . Or at last i think that is our _defconfig because it's only one with anything which can be related to our device (m1v)
 
Last edited:
J

joeeboogz

Guest
I bought this phone cheap so I'm going to try to compile today
 

Professor Woland

Senior Member
Mar 10, 2016
353
55
Redmi Note 9 Pro
I bought this phone cheap so I'm going to try to compile today

Nice, but I doubt it will work at first try since I made this without any real knoweledge..
And there is still problem where we can't flash anything without soft brick because of some signature or whatever else checker. Probably in lk (little kernel) partition so we need a good reverse engineer to make check function allways true and don't kill phone in process..
 

bynamnshan

New member
Oct 6, 2017
2
0
Nice, but I doubt it will work at first try since I made this without any real knoweledge..
And there is still problem where we can't flash anything without soft brick because of some signature or whatever else checker. Probably in lk (little kernel) partition so we need a good reverse engineer to make check function allways true and don't kill phone in process..


Sent from my LGE LG-K350 using XDA Labs
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Hi I have working on this some time and it should work, I'm not a real developer and don't have big knowledge. This is ported from Wileyfox porridge.
    I'm posting this here because I don't have a PC to try to build on it (I have single core celeron with 512mb RAM, belive me or not) and also my phone's bootloader is still locked because I don't want to break warranty yet because I had some problems with very low R/W speeds. So if there is anyone who know what should be done and would like to try to build ROM or help with device tree, please feel free to do that.

    NOTICE: If you have model other then 8GB K350nds you should edit values of partition sizes in BoardConfig.mk Better solution will be if I known difference in size of partitions for each model, and even than I'm not sure what attribute from /proc/cmdline I should compare to get it right (in init_mm1v.cpp)

    Device tree https://github.com/ProfessorWoland/android_device_lge_mm1v
    You'll also need common tree https://github.com/LineageOS/android_device_cyanogen_mt6735-common

    About kernel if you try to build ROM:
    Kernel source is published by LG here http://opensource.lge.com/osSch/list?types=ALL&search=k350
    But also there is kernel on Lineage OS repo https://github.com/LineageOS/android_kernel_cyanogen_mt6735
    It should work also if you just add muse6735_m1v_m_defconfig file from your kenel source to /arch/arm/configs . Or at last i think that is our _defconfig because it's only one with anything which can be related to our device (m1v)