Related
THIS THREAD IS FOR DEVELOPERS ONLY!
Please do not post your problems with ROM here.
Post your ideas about working on ICS or CM7 and your problems with compiling sources or similiar.
I posted my p350 sources on github:
https://github.com/pax0r
You will find an instruction how to download mine soruces and compile it by yourself at:
https://github.com/pax0r/android_device_lge_pecan
Here we can speak how to improve this ROM ( 7.2 ) and also how to work on ICS. On my github you can find branch "ics" - it is somehow releated to my work on ICS but it's not complete.
So let's make our device EPIC!
For the begining I will post my problems releated to working on P350:
The problem I have with 7.2 release is that BT is not working - drapalyuk fixed it somehow in last release but I don't know how. If any one have idea what was changed from 1910 to 2010 drap release please let me know!
Also I started to port .35 kernel for our phone - but it's not working yet. Kernel boots and console via adb is usable at this moment but Android itself does not start on it. I will post more in this topic later.
now syncing the source
hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele
hi pax0r,
the market crash few times at the begin but after I reboot it seems to be fine.
I attached the logcat.
Gabriele
megasoft78 said:
hi pax0r,
I'm trying to build CM 7.2 using your guide and source code but I notice a couple of issue that maybe create problems to someone beginner like me:
1) if you run ./extract-files.sh on a phone with CM 7.2 (vivekkalady) the extraction will fail on 3 files: libloc-rpc.so, libloc.so, libcommondefs.so. Maybe they are located in a different path.
2) I think this line of code in extract-files.sh is wrong:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.default.so
it should be:
Code:
adb pull /system/lib/hw/gralloc.default.so ../../../vendor/$MANUFACTURER/$DEVICE/proprietary/lib/hw/gralloc.pecan.so
to avoid issue later.
I'd like to try to compile ics. What do you think is missing to make it works?
Best Regards,
Gabriele
Click to expand...
Click to collapse
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P
pax0r said:
Thanks for your contribute
For me there are no missing libs - I was running it on 7.1 so mby Vivek 7.2 is missing them?
About gralloc - there should be two libraries gralloc.default.so and gralloc.pecan.so
About ICS I have no idea yet and now no time to look at it - studies, work and 7.2 rom is everything I can do at once ;P
Click to expand...
Click to collapse
I think the problem about missing libs is related with vivek 7.2 rom.
it's strange but I can't see gralloc.pecan.so. Anyway I'll check it this evening.
I was able to build everything using your tutorial but now I want to try with ICS. I need a bit of searching on internet.
Thank you for your work,
Gabriele
Hm I've checked it and it fact there were no gralloc.pecan in extract - it was obviously a bug, I pulled everything from device, then I was making some refactoring and I didnt check it after that. I will push commit with fixes today.
Thanks for pointing it!
I see a keylayout headset push, how did you make the headset button works? I replaced both keylayout (qwerty with the haptic fix and 7k), but the dammed button still with problems =/
Thanks
PD: The new implementation of gralloc will fix the dammn warning of prelink? (on the log)
I'm not sure if this keylayout will make headset work as I don't have one but it was suggested that it may help but this need test. New gralloc is because it is open source comparing to the original propriety one and I'm testing its speed - it is at least the same so I will leave it
To solve a problem with prelink there should be a prelink.map created but I dont know exatly how to build one. It is not a critical error but with prelink.map the boot process could be faster.
I still didnt fixed copybit ;/
If you have some idea how to help refer to this post:
http://forum.xda-developers.com/showpost.php?p=21592280&postcount=28
EDIT: copybit fixed
hey could some one with the headset use this app:
https://market.android.com/details?id=aws.apps.keyeventdisplay
click headset buttons few times and post output of this app (if any)?
BTW do the headset buttons works on Vivek ROM?
Let me compile it with the new changes and I will try
At least, I'm currently using 7.1.0 (your 7.1.0) and nothing happens. (EDITED)
call\music button problem
paxor can u rectify the call\music button for wired headset
Can you compile ICS with your new files and send it to me ??
I will try to port ICS with your new files
Hey pax0r, are you sure with the fix? Compiled, installed... but I get a weird screen on menu =S
Thanks
I get a minor success at porting .35 kernel for p350. It boots and works but it still to bugged to public release. However if you have any dev experience you can grab it here https://github.com/pax0r/lge-kernel-msm7x27 and help me fix it!
I don't know exactly how Android handles GUI, IDK how to help right now, but I just can told you about the bug when android it's displaying interface.
Can you upload your compiled ICS so that we can tweak it to get it working!
I've removed my built version and now my source code wont even build :/
Hi Pax0r! well, i want to become a dev, i have some kind of linux knowledgement and have a good willing to learn, could you please point me out to some basic tutorials about building from cyanogen source? i've searched myself in the wiki but i didnt saw anything about lg pecan, any information you can give me, I will study it and maybe then become of help in dev community! thanks in advance!!
There is not much info about anything for P350 as it is not very popular device. Everything you need to start building CM for P350 is here, in mine Readme file:
https://github.com/pax0r/android_device_lge_pecan/blob/gingerbread/README.mkdn
Everything else you need to get by yourself =p but I will try answer all your questions
I learned everything by checking avaibale info for similar devices (MSM7227 board, for example: LG P500, ZTE Blade) and source codes.
i want to build a kernel by myself .so i
download the source code from HTCdev.com ,
then compile it
finally ，i got a bootable kernel
but it seems that the GPU dosenot work，
when sliding the screen ，it looks like a mess
i did a test with antutu,the 3Dgraphic test only got 5~7fps
everything else working well
what should i do to fix this ？
Hello guys
as you know ım working on 3.10 kernel for ancora and(for the other samsung msm7x30s too)
Kernel status:
-all ther device drivers and specific changes applied,updated to 3.10
-kernel is compilable atm
-offmode charging seems to working
but
-kernel isnt booting
ı cant see second bootlogo(ı mean "samsung galaxy w" title)
ı can see first bootlogo(only the "samsung" title) but as ı said no second logo
ı uploaded my work and kernel to my git (so everyone with needed skills can colloborate into this project)
we need DEBUGGİNG
ı need to look into kernel boot logs but unfortunatly adb isnt woreking because in my mind kernel hangs before starting to load init.rc files because of this adb isnt working
ı tried to connect UART for two days but ı dont have good soldering skills plus ı dont have any equipment(like resistors for UART) so ı couldnt connect to it
Kernel sources:https://github.com/sirmordred/android_kernel_qcom_msm7x30
The SElinux status is acting in permissive or in enforcing mode?
Cause either i cannot access adb from PC with enforcing status with a ROM recently released and it didn't pass the boot either
So i switched to permissive
Btw awesome job man
@Mordred : thanks you . you great . This is work hard . May @Christopher83 and @arco68 will help us to fix .
my experience told me you have to move all drivers and edit all kconfig and makefiles + you need to setting up configurations close to stock kernel to get boot, i try that on my s2+ and take about entire week just to add the arch of the kernel, well if patches are compatibile, why not..
Hmmm, looking for some experience on porting kernel 3.10. I stucked with my current device.
bangprovn said:
Hmmm, looking for some experience on porting kernel 3.10. I stucked with my current device.
Click to expand...
Click to collapse
which device do you have bangprovn?
Code:
/*
* Your probably long dead warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
This thread is organized into different posts so that people dont quote the whole OP.
Please read all the posts and updates, before flashing.
Changelog Summary:
For full changelog follow the link.
#FINAL: 28 Jan 2018
Repo synced with latest LineageOS 14.1 sources.
Updated system webview to 64.
Added postinstallzip due to kernel not being flashed.
Added Magsik 15.3 support in ramdisk.
#4: 14 Nov 2017
New feature: UA:CMA
Added back Device Settings.
#3: 14 Nov 2017
Switched to a more stable kernel with improvments
Fixed Camera
Fixed Bootanimation
#2: 12 Nov 2017
Enabled OpenGLES 2.0
Fixed Audio/Video Playback.
Fixed Webview.
#1: 11 Nov 2017
Initial build.
Latest Download:
You need to flash lineage-14-postinstall.zip after installing the ROM, or else it wont boot.
For some reason ramdisks arent being flashed.. and I cant be bothered to figure out why..
lineage-14.1-20180127-UNOFFICIAL-galaxysmtd.zip
lineage-14-postinstall.zip
Older builds
#4 lineage-14.1-20171117_140654-UNOFFICIAL-galaxysmtd.zip
#3: lineage-14.1-20171114_062105-UNOFFICIAL-galaxysmtd.zip
#2: lineage-14.1-20171112_085706-UNOFFICIAL-galaxysmtd.zip
#1: lineage-14.1-20171111_094959-UNOFFICIAL-galaxysmtd.zip
XDA:DevDB Information
GalaxyS1 Resurrected Nougat Project, ROM for the Samsung Galaxy S I9000
Contributors
(°_o), ColdwindOfnowhere, xc-racer99
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Beta
Created 2017-11-11
Last Updated 2017-11-14
XDA:DevDB Information
GalaxyS1 Resurrected Nougat Project, ROM for the Samsung Galaxy S I9000
Contributors
(°_o), ColdwindOfnowhere, xc-racer99
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2017-11-11
Last Updated 2018-01-28
Working List:
Boots
RIL (SMS, Call)
WiFi
Audio/Video Playback (fixed in build#2)
Camera Pictures (fixed in build#3)
Not Working List:
RIL Data
FAQ:
Dont install too many apps obviously
The first boot should be faster than previous nougat roms.. Since I have now used pre-odexed /system.
Known Issues:
Lagginess ofc, due to our device being old
Sometimes SystemUI gets killed due to low memory and we get Black Screen of Death
Install Instructions :
[WARNING]:
You must be already on at least Lollipop/Marshmallow ROM and have latest TWRP 3.1.1.
You must format /data as f2fs in TWRP.
Bootanimation is working since build #3.
You should already been familiar with flashing custom ROMs before.
And know how togo from gingerbread -> nougat.
Please check other threads for that..
If someone wants to contribute install instructions for this ROM.
I will be happy to add here and give credits.
Gapps
I havent tested GAPPS.. but I can guess the performance will be horrible with it.
However, I have included the patch for microG GmsCore signature spoofing. So you could try that.
Additional Info:
Built from latest LineageOS 14.1 Sources.
Latest kernel from @xc-racer99 aosp-7.1 branch
Live wallpapers, LineageOS Updater, Weather Service removed for low memory footprint.
Reserved.811919
Reserved.224232
Credits:
@xc-racer99 and @Coldwindofnowhere for getting the device upto android 7.1.1
And all others who had worked from beginning till now on this device.
Sources
Galaxy S1 Resurrected: Project Nougat
Device Trees:
https://github.com/galaxys1-resurrected/
https://github.com/galaxys1-nougat
Kernel:
https://github.com/galaxys1-resurrected/android_kernel_samsung_aries
I'm delighted that there's still someone who is working on this device. I'll be appreciated to wait for a more stable version of nougat.
The rom is indeed quite stable.
However, Webview doesn't seem to work. I think you should take a look here.
Also, built-in root with the Su-addon doesn't work.
And flashing a Magisk or SuperSu zip (made by @xc-racer99 ) resulted in a bootloop, but I was able to access the recovey.
MYEUHD said:
The rom is indeed quite stable.
However, Webview doesn't seem to work. I think you should take a look here.
Also, built-in root with the Su-addon doesn't work.
And flashing a Magisk or SuperSu zip (made by @xc-racer99 ) resulted in a bootloop, but I was able to access the recovey.
Click to expand...
Click to collapse
Expect lot of stuffs dont work at the moment.. listed in Not working.
About webview I will try to replace it.
Magisk and SuperSu try to patch boot.img and ramdisk.. and our device uses a very hacky way to load ramdisks.
I will create a patched ramdisk with latest Magisk then..
This has to be the fastest Nougat ROM I've flashed on this phone! Thanks for keeping this amazing phone alive. Can't wait to see it become more stable in the future
Full changelog: build #2
Fixed Audio/Video playback
I had to remove ffmpeg codecs as they were causing hardware decoding to not work.
Hardware decoding is working fine and 720p playback is smooth too..
I've tested without bigmem mode.. I havent implemented bigmem libs for 720p playback.
So please try without bigmem before reporting issues with it.
Fixed Webview
AOSP Webview was somehow not working on our device.. as pointed out by @MYEUHD
The solution he linked was to revert to older webview.
But that is outdated and unsafe so I tried with latest Android System Webview.
It seemed to work so I set it to default.
I havent tried but we can also use Chrome as our Webview..
Switched to OpenGL 2.0
We were stilling using OpenGL 1.4 for rendering.. this shouldnt affect much.. but animations should be smoother
Since we no longer get Shader errors with OpenGL 2.0
Let me know if you find any difference performance wise compared to build #1.
Downloads are in OP.
Status Update:
Project discontinued.
Status Update:
You can skip this paragraph if are not intrested in my long story cut short.
So I have been trying to fix stuffs which means.. rebuilding and flashing the ROM.
Wiping data .. getting logs.. testing if something works.. Repeat
I hadnt really used my Galaxy S1 phone.. It was just lying around a corner of my table getting dust.
Until one day I thought, let's build Oreo for this old time phone.. turns out the battery was RIP due
to not charging it for so long.. so I got a replacment battery then booted to see cm-14.1 build by
Coldwindofnowhere and missing IMEI which I sucessfully restored after creating a thread here.
Again thanks for that to @xc-racer99 and @MYEUHD
So I started out device trees and repos based on Coldwindofnowhere and xc-racer99
and made it compatabile with Oreo. And thanks to rInanD0 I was able to pick stuffs necessary on
kernel side.
Then me and @xc-racer99 discussed some stuff and I picked changes from Unlegacy-Android gerrit to properly do some stuff.. I fixed lots of stuffs.. but I couldnt get the display to initialize... so I decided
to wait for Unlegacy-Android for their take on Galaxy Nexus which shares same GPU as us to bring up Oreo first.
In the mean time, I thought again.. why not build Nougat for now.. so I again setup device tree and repos for
nougat. and we are here..
Okay so I havent really used my Galaxy S1 let alone this ROM.
This ROM does seem fast while moving around just after a first boot.
And really I hadnt installed or used any apps besides the one that came with LineageOS.
But today while trying to fix Camera, I had to actually take photos. Oh, and the reason camera was not working
was due to I had disabled building of Camera HAL in Oreo which stuck around... big derp
So camera preview was working now.. Snap camera wasnt savinf photos at first..
so I thought to install Open Camera.. I installed F-Droid.. then Open Camera..
Then I clicked some photos which seemed to be saved.
There were a lot of photos created so I decided to delete them.
But Files app wasnt deleting them.. must be a permission issue?
So i installed a file manager from F-Droid and deleted the photos.
Good enough.. then I thought I need to download these apps again after a data wipe..
Lets backup them.. so I installed an apk backup again from F-Droid.
While it was downloading.. BAM Screen went all BLACK.
I tried clicking home button but nothing.. then I clicked power button nothing.
Then I hold power button.. i got the options...
Now I was reminded of this bug which has been around since Lollipop? or Marshmallow days..
Screen going all black.. back then Coldwindofnowhere predicted it might due to out of memory issues..
And he is right.. I had adb running so I checked free memory and swap.. The swap file was and memory was nearly full.
I checked dmesg for logs... then I saw lowmemorykiller killing all kinds of stuff.. but there was only one time it killed this..
Code:
lowmemorykiller: Killing 'system:ui' (5642), adj 902,
And thats the reason for the black screen.. Now we all know this device doesnt have much memory.
So the option would be to not install many or any apps.. on this option..
Ofcourse I could try to get CMA working properly.. which adds just around 70-80mb I guess..
And we could just white list system ui to not get killed.. but then it would kill other important processes..
So I've decided to stop working on Nougat. I dont wanna give people false hope of *stable* nougat.
I will still upload a build with Camera fixed.. Well video recording still doesnt work.. Looking at logs.. i need to resurrect
the old way of video buffer. which got removed in Nougat.
And while Project Nougat is offically discontinued, Project Oreo is still alive just paused.
I will at least get Oreo bootanimation on this device.
Thanks for trying out this short lived nougat ROM.
Full changelog: build #3
Switched kernel from @Coldwindofnowhere to @xc-racer99
I think xc-racer99 kernel has better memory management. since the lowmemory killer doesnt kill many processes..
However I did make some changes to it.
Disabled CMA
Enabled and set zRAM to 1/4 of total memory
Some kernel build optimizations.
Note that.. this kernel doesnt have BigMem Support so wer'e stuck with 383MiB ram for now.
Fixed Bootanimation
Yeah.. that was a my mistake.. err..
At least you know its booting now.. but since we use pre-odexed ROM first boot shall be done in 5 minutes now..
Fixed Camera
Taking pictures should work now. Video recording is broken.. It needs to updated for Nougat..
Added Magisk in ramdisk
Latest version 14.0. Just install magisk manager AND DONT TRY TO PATCH BOOT.IMG..
We use very differnet system for boot.img and ramdisks..
I will try to update Magisk to latest version.
Fixed a big mistake in updater
https://github.com/galaxys1-nougat/...mmit/a6f51178503a01f6b1e7b0c8222e875392af8a8e
Flashing boot.img would actually result in wiping it in some cases..
If you had troubles installing this ROM or any ROMs in the past.. this might be the case..
The flash over mm dont work for me i have an error 7 i try to reflash and now no twrp i need to restore via odin any help?
laharl_22 said:
The flash over mm dont work for me i have an error 7 i try to reflash and now no twrp i need to restore via odin any help?
Click to expand...
Click to collapse
Error 7 is assert error... which I guess is coming from updater script..
You dont need to restore whole stock ROM..
I have built a twrp only recovery image... so you can just straight boot to recovery after Odin..
You can also flash recovery.img from heimdall .
https://drive.google.com/drive/folders/1KthyR6QWPswaIT8fw2nbiR4fathP-QU0?usp=sharing
How is this Rom compared to the LineageOS 4.4.4?
Hey xdas,
i just received my new Samsung Galaxy z Fold 4
SAOMC_SM-F936B_OXM_EUX_12_0045 EUX /-/EUX/EUX
Kernel : 5.10.81-afaneh92-gd8d6af751972 (flashed for twrp)
I would like to install nethunter on the device with a working kernel
I tired my best to understand the docu on kali but its not the best
i am also new to compiling kernels at that level so maybe someone can help here
I attached as much as i could
So the steps i took so far is
Unlocked Bootloader
installed the twrp ( like descriped here : https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-z-fold4-snapdragon.4498743/ )
installed magisk
Then for nethunter
(https://www.kali.org/docs/nethunter/)
i downloaded the kernel source :
https://opensource.samsung.com/uploadSearch?searchValue=SM-F936 (my device is EUX see infos for device above)
downloaded the proper=? toolchain , there is an readme_kernel inside the kernel_source with a link to the toolchain , i am unsure about this
https://opensource.samsung.com/uploadSearch?searchValue=toolchain
there are two options i took the S22(Exynos) file ( hope thats right ?)
now we come to the difficult part :-(
first i tried to compile via the instructions on kali docs
unpack the kernel file i did and there a subfolders so i decided to use the subfolder common as the root mentioned in the docs:
you can begin by cloning our kernel builder to the root of your kernel’s folder, and prepare the environment:
from common folder i did git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
cd kali-nethunter-kernel
I did not change the configs as i am new to that so i know there are some exports inside the build config inside the kernel file but i dont know how get them together
./build.sh
S. Setup Environment and download toolchains.
2. Configure & compile kernel from scratch
It found the devconfig so i took it as mentioned in the docs (Select your device’s defconfig, then save and exit to start the building process.)
did not edit the kernel config till jet
and ran into the error attached in the error txt
I would like to understand how i can build the kernel the normal way , without the nethunter tool
and maybe someone could help to make this working with nethunter that would be great !
i want to understand the process and i am willing to help , so i am not asking for a final kernel , more for the way to go in general to also give the community a benefit for the next new kernel we want to port
as mentioned the docs are not the best !
thanks for your time
@yesimxev / @V3rB0se / @afaneh92 need some help here
Which toolchain to you use in nethunter kernel builder? I'd recommend clang-12.
https://android.googlesource.com/platform/prebuilts/clang/host/linux-x86/+archive/refs/tags/android-12.0.0_r12/clang-r416183b1.tar.gz
Download, extract somewhere and add it's path to kali-nethunter-kernel/config (clang-10 is the default). no need for setup environment again.
Any luck with this? i am in the same situation trying to build a nethunter kernel for my zfold4
Wanttoknowthings said:
Hey xdas,
i just received my new Samsung Galaxy z Fold 4
SAOMC_SM-F936B_OXM_EUX_12_0045 EUX /-/EUX/EUX
Kernel : 5.10.81-afaneh92-gd8d6af751972 (flashed for twrp)
I would like to install nethunter on the device with a working kernel
I tired my best to understand the docu on kali but its not the best
i am also new to compiling kernels at that level so maybe someone can help here
I attached as much as i could
So the steps i took so far is
Unlocked Bootloader
installed the twrp ( like descriped here : https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-z-fold4-snapdragon.4498743/ )
installed magisk
Then for nethunter
(https://www.kali.org/docs/nethunter/)
i downloaded the kernel source :
https://opensource.samsung.com/uploadSearch?searchValue=SM-F936 (my device is EUX see infos for device above)
downloaded the proper=? toolchain , there is an readme_kernel inside the kernel_source with a link to the toolchain , i am unsure about this
https://opensource.samsung.com/uploadSearch?searchValue=toolchain
there are two options i took the S22(Exynos) file ( hope thats right ?)
now we come to the difficult part :-(
first i tried to compile via the instructions on kali docs
unpack the kernel file i did and there a subfolders so i decided to use the subfolder common as the root mentioned in the docs:
you can begin by cloning our kernel builder to the root of your kernel’s folder, and prepare the environment:
from common folder i did git clone https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-kernel
cd kali-nethunter-kernel
I did not change the configs as i am new to that so i know there are some exports inside the build config inside the kernel file but i dont know how get them together
./build.sh
S. Setup Environment and download toolchains.
2. Configure & compile kernel from scratch
It found the devconfig so i took it as mentioned in the docs (Select your device’s defconfig, then save and exit to start the building process.)
did not edit the kernel config till jet
and ran into the error attached in the error txt
I would like to understand how i can build the kernel the normal way , without the nethunter tool
and maybe someone could help to make this working with nethunter that would be great !
i want to understand the process and i am willing to help , so i am not asking for a final kernel , more for the way to go in general to also give the community a benefit for the next new kernel we want to port
as mentioned the docs are not the best !
thanks for your time
Click to expand...
Click to collapse
Great research bro , same as here.
Difference is I am doing it for M21 .
And to flash the kernel I need to do port twrp for vA12 M21 too.
Great respect bro.
Anyone can help with kernel? u need AR9271 and rtl8188EUS drivers on ysl Android 9
https://forum.xda-developers.com/t/arm64-rom-unofficial-9-0-0-ysl-lineageos-16-0-18-08-2019.3958696/ <----- this rom
Phone: codename-[ysl]
Redmi s2
i have been trying to make it myself but always gets fails
im having the same issue at this step... anyone willing to show the part on how to setup the toolchain properly>?
heres a screenshot of my issue
this is local.config file
kluongo said:
heres a screenshot of my issue
Click to expand...
Click to collapse
It shows the error, do apt install flex
yesimxev said:
It shows the error, do apt install flex
Click to expand...
Click to collapse
Will do, thanks... You know I was looking through the process and missed that line... I suppose next time I should take more time and look more carefully
kluongo said:
Will do, thanks... You know I was looking through the process and missed that line... I suppose next time I should take more time and look more carefully
Click to expand...
Click to collapse
Great, I'll add to the setup env script so it won't be missed. It shouldn't happen in the first place though