Related
Here is an instruction how to install Play Store (and Play Services) on Chinese version of Nokia N1
DISCLAIMER: you're doing it on your own risk, it can probably even eat your kitten
Credits should go to rumambo who has described everything in this thread.
Original credits from rumambo:
Thanks a lot sadfrog_lin for right link
Great Thanks social-design-concepts for Tools and working solution !!!
This was successfully done by me on A5CN507 build. IMO it should work the same good on other versions of Lollipop, but I cannot promise anything.
Prerequisites
I assume that you have Intel Drivers up and running http://opensource.dell.com/releases...ition/FlashTool/IntelAndroidDrvSetup1.5.0.exe
I assume that you have adb/fastboot up and running http://forum.xda-developers.com/showthread.php?t=2317790
I assume that you have usb debugging enabled
I assume that yu have a basic knowledge how to use these tools
Installing GApps
Download GApps from this thread. I have used Nano version for Android 5.x, direct link here.
Copy it to your sdcard (any method is fine, but adb will do: adb push <filename> /sdcard/).
Download and extract IntelAndroid-FBRL-05-16-2015.7z.
Connect N1 via USB and run launcher.bat
Type ACCEPT (all capital) and select T4 method.
N1 should reboot and do a lot of things, then you should end up in temporary CWM Recovery session.
Choose install zip (volume up/down + power to select) and find and select the previously uploaded file.
After it finish reboot the tablet
Final fixes
After reboot you should have initial selection of Google Apps (including Play Store) installed. However Play Music will crash on start and GMail won't work (Play Services crashes). The reason for that is that GApps package is probably not fully prepared for x86 - but now you can simply fix it.
Go to ApkMirror and install Google Play services with -470 suffix, it is Lollipop x86 version (on the time of writing this the newest version was here ). Now both Play Music and GMail should work correctly.
An another issue is that Play Store reporting some apps (like Chrome, Google Maps, Google Earth, Chromecast, etc) as incompatible with the device. It probably could be fixed by hacking build.prop, however I haven't had time for it yet. The easiest method is to download them from ApkMirror and side install. Drawback is that you won't get autoupdates for them.
Enjoy!
reserved
reserved for a future use
For information the next update fails with this log...
I:verify_file returned 0
Installing update...
Verifying current system...failed to stat "/system/app/QuickSearchBox/QuickSearchBox.apk": No such file or directory
file "/system/app/QuickSearchBox/QuickSearchBox.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
"/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
E:Error in /cache/A5CN51C_update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
This really works! Thanks a lot.
After the installation, a few days later I found out that there was an update for N1. I could not make the update successfully. Probably the GAPP issue. So in the end, we still need the Taiwan ROM so far. So that the system update can also be made.
I installed GAPPS, but disabled root(in SuperSU's settings). I can run the OTA update (A5CN51C) successfully.
After the update, "google service is stopped" appears again. I think re-flush GAPPS and SuperSU is needed.
bricked
Hi Guys,
after the issue with the update I started replacing new files with the originals from the previous update. I've checked md5 of every file I used and compared it with update script from the new update - so I'm sure every file was correct. Actually everything was working fine with these original files.
However after the update I got a boot-loop. If I remember correctly it was something abt OpenGL in logcat. I was not able to run recovery by pressing volume up and power, but since adb was working I did it via adb. I came with an idea to clear user data. That was mistake!
Now I still have the boot-loop but developer mode was disabled by cleaning the data. My plan is to reflash with A5CN507 which contains a full system partition image. To do so I need to boot into recovery or download mode.
Do you guys have any ideas how to boot into recovery or download mode if volume up (and down) doesn't work?
Thanks in advance.
Can confirm the boot loop. I was able to get into the CMW session again and tried to restore the backup I made before installing the gapps but CMW got stuck while restoring the system partition.
The device is now stuck in the "Powerd by Android" screen, any help is warmly welcome
Can't root by the method after update to latest 5.1.1 firmware. Pls update the method
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
Your tablet bootloader is locked by the update. I've not found any ways to unlock it and install google play.
same here 5.1.1 messed everything up
Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
same here - so I thought I redo the whole thing with Gapps for 5.1.1, but now Fastboot Tethered Recovery Launcher doesn't recongnize my N1 anymore. Can anybody help? Thanks in advance
Any chance that the following common command work ?
Code:
fastboot oem unlock
jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
It's used to make your device unlocked, but only limited to some devices.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you,
I tried that, it didn't work - it says "waiting for device", but it waits forever. As to the Fastboot Tethered recovery launcher, this time I used the one from Jul, 27, before I had an earlier version. Could it be that the older version would work, but not the latest one? It does recognize my device, but it says unauthorized, although it OEM-unlocked and USB debugging is authorized. Thanks for any help.
and that's the end of it, good night N1
Since my N1 is still bricked, hung halfway through bootloading, I talked to an Android-Repair-shop. They said it cannot be unbricked, I would need a new motherboard... but motherboards for the N1 are not available.
Does anyone hv better news?
Hi,
so I came back to the problem today - and I managed to unbrick my device. Somehow (vol-up + power) I managed to enter fastboot. Then I rebooted into recovery and sideloaded a full update.zip with 701.
Now I'm trying to change Chinese version to Taiwanese one.
my nokia n1 stuck
my Nokia n1 stuck at boot screen i lost my recovery too my tablet only open at fastboot mode.Pls HELP
i need boot.img and recovery.img for NOKIA N1(A5CNS1C)
Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19
sasha2910 said:
Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19
Click to expand...
Click to collapse
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...
LineArc said:
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...
Click to expand...
Click to collapse
Can't wait for that! :good::good::good::good::good::good:
There is a lot of discussion about the m8s here: http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
That thread involves different ROMs, returning to a locked bootloader and lots of other stuff. I found it hard to search through it and obtain the information I needed to root my device. Because of that I thought I would make this post. I hope it is of some use to people. Thanks to posters who helped me out on previous threads.
To root your device
You will need fastboot installed on your computer. On a linux machine this will probably be easiest by installing android-tools. On a windows machine you can install htc-fastboot linked to from the first post here: http://forum.xda-developers.com/htc-one-m8/help/make-custom-recovery-htc-one-m8s-t3114245
- unlock your bootloader following instructions on htc-dev.com [you will have to register for an account]
- download twrp-recovery-2.8.6.0-m8s-qlul.img [linked to from this post http://forum.xda-developers.com/htc...c-one-m8s-t3114245/post62216780#post62216780]
- download the latest SuperSU beta [http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133]
- obtain a flashable version of busybox from here: http://forum.xda-developers.com/showthread.php?t=1929852 [I chose the Stericsson one]
- copy both SuperSU and busybox .zip folders to your phone
- From the folder on you have download twrp to on your computer execute the following command [on linux machine]
Code:
sudo fastboot boot twrp-recovery-2.8.6.0-m8s-qlul.img
- once in TWRP install SuperSU and then busybox
And that's it. You now have a rooted Stock rom .
Thank you wageslave. I also found the thread somewhat confusing and appreciate your summary here. I was wondering if you could answer me this: Since you "just" root and continue to use your stock rom, will your stuff still be on the phone after rooting (independently of your answer here, I'll do a backup).
2)
Thank you wageslave, this should be stickied.
Not to hijack, but I have a related question I've tried asking a few times but has gone unanswered. Given the limited internal storage on the M8S (16GB, but let's face it, it's actually 9GB), I've been trying to use Link2SD to link apps onto a 64GB MicroSD card.
After a successful root, I seem to be hitting a wall. Link2SD fails to mount the second partition (ext4) at boot, and even when a quick reboot fixes that problem, it fails again when I try to install apps to the external sd.
I presume this is mostly to dow ith not being able to S-Off, would this be correct?
If so, are there any other ways to get around this? I see someone mentioning on another thread that you need to disable System Write Protection, but I can't find a guide to doing this relating to the M8S.
I haven't yet installed BusyBox, I will this evening.
Thanks for any help and advice!
I was also pretty confused..
So you are saying that with your method I don't have to think about that RUU thing?
I can just use the twrp and flash it using cmd?
Hi, I'd love to use twrp on my M8s, however, the twrp link doesn't work for me (the ruu.lalleman site).
Is there anyone kind enough to make the img downloadable through something like Google drive or Dropbox? That'd be so cool, I've been searching for days to find a working custom recovery.
How to I Install Xposed on Rooted Amazon Fire TV 2? (Guide Please)
Do I download XposedInstaller_3.0_alpha4.apk? and xposed-v78-sdk21-arm64.zip?
Please Help
Could I Use Flashfire?
You can't install xposed since there is no custom recovery
Tried with Flashfire where no custom recovery is needed ? what version of xposed should i try?
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
yeah I've had no luck, just have to wait I guess
ians325 said:
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
Click to expand...
Click to collapse
Did you encounter boot loop or soft-brick when you attempted this?
z_thompsonpa said:
Did you encounter boot loop or soft-brick when you attempted this?
Click to expand...
Click to collapse
No
ians325 said:
No
Click to expand...
Click to collapse
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
I couldn't run this command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
[*]SELinux enforces more policies when Busybox is installed
[*]Setting SELinux to Permissive has no effect
EDIT: **Details in my next post**
z_thompsonpa said:
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
SELinux enforces more policies when Busybox is installed
Setting SELinux to Permissive has no effect
Click to expand...
Click to collapse
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
fldash said:
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
Click to expand...
Click to collapse
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
keep up the good work
z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
fldash said:
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
Click to expand...
Click to collapse
I haven't had to break out the USB A-A cable yet... thankfully (except for root of course).
I used Flashfire to backup my /system partition as RAW backup before I started all of this experimentation. I have just been restoring back to this known good state using Flashfire after each time I corrupt the system partition.
I intended on trying this method, and if it didn't work to fall back to the method mentioned in the root thread. I checked the logs last night and Flashfire seems to be succeeding at this task, at least.
Right now, I am picking through the Xposed installer script source and using the Flashfire logs to debug why it is failing. It appears to be a permissions issue, but a lot of the stdout/stderr is suppressed so its hard to tell exactly where. When I get home today, I am going to try to modify the installer script to produce more output so I can debug the issue further. If I cant figure it out, I'll post my findings either way.
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
z_thompsonpa said:
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
Click to expand...
Click to collapse
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
fldash said:
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
Click to expand...
Click to collapse
I think so... I am pretty sure its a dead end. I also tested using adb to write the files and it failed on /system/lib/libart.so, as well. It's, I believe, because the object is loaded in memory?? don't quote me on that... but loading through preloader, I think, would avoid this limitation as ART is not running.
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
sconnyuk said:
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
Click to expand...
Click to collapse
Use this method, I've slightly modified the text from another post & added it into a text file for you, this works a 100% but as usual I take no responsibility if you do any thing wrong & brick the Fire Tv2.
Enjoy & press that thanks button If this helped you
Thanks for this. I will try it shortly and report back if it works for me. I have stumbled upon another thread that the guys seem to be working on playstore issues, http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
Made a guide here if anyone wants to install
http://forum.xda-developers.com/fire-tv/general/installing-xposed-fire-tv-2-guide-t3314142
Hi folks,
I need your help.
A few days ago I have received my brand new HTC 10. I updated to latest Android 7 Nougat and began to root remaining stock.
I followed the official guide and unlocked the bootloader, flashed latest TWRP (3.1.1.0) and SuperSU v.2.82SR1 and even got S-OFF by SunShine.
System is up an running and readily booting but...
Fact is I cannot mount /system in TWRP without the option "read-only". When I try to install apps via TWRP I get repeated messages saying "Failed to mount '/system' (Invalid argument) " and usually the apps do not install properly - flashed apps do not show up in the system after reboot.
In the system I have tried to rename a file audio_effects.conf (this is needed to install Viper4Android) in the folder /vendor/etc/ on the device but the folder is strictly read only. Any attempts to mount the folder as RW (using "adb shell", "su", "mount -o remount,rw /system" and similar) have failed. I have tried to gain access to files in the system folder using Root Explorer and Total Commander but the files remain strictly read only. I just get error messages trying to change file attributes, permissions,names).
SuperSU seems to work and according to Root Checker I am properly rooted but I doubt this. Somehow /system seems to be locked and not accessible.
Any ideas what I could do ?
Many thanks for your help ! :good:
Well, I simply flashed Viper10 ROM and the issue was gone.
Feel free to suggest solutions to the problem as somebody else might come accross this thread struggling with a similar issue. I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Buddha1979 said:
Well, I simply flashed Viper10 ROM and the issue was gone.
I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Click to expand...
Click to collapse
No, it's not an incompatibility issue.
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
plz help a noob
LibertyMonger said:
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
Click to expand...
Click to collapse
I also just recently updated to nougat and when i tried to root using the latest (TWRP 3.0.3-11) it seems I get stuck on a screen with red text that says, "This build is for development purpose only . Do not distribute outside of htc without htc's permission."
I know this is not the original question but was hoping someone with more experience could help instead of starting a new thread :/
Thanks much!
I just ran the latest Verizon RUU and I am still getting this error when trying to flash Viper10_5.9.0_MAGISK. Seems system is not mounting, I don't know I will appreciate any help Thank you.
Hi,
a lot has probably been written about this, but I'd appreciate a pointer to the relevant tutorial.
I am trying to install Lineage 17.1 on a OnePlus 7 (guacamoleb), but it gets stuck at the boot animation. I am a noob in terms of Lineage development (but know how to administer a Linux server).
My question is how do I extract the relevant log files when Lineage fails to boot. I think I can always get into recovery (I installed TWRP in both slots), but I am lost as to where the log files from the previous (failed) boot attempt can be found and how I can extract them with TWRP. I suspect that one of the many partitions that Lineage expects, is not property formatted or has some mandatory parts missing, but without the log files, I am flying blind and don't know where to look.
Any help is very much appreciated.
Thanks,
Gloria
gloria13 said:
Hi,
a lot has probably been written about this, but I'd appreciate a pointer to the relevant tutorial.
I am trying to install Lineage 17.1 on a OnePlus 7 (guacamoleb), but it gets stuck at the boot animation. I am a noob in terms of Lineage development (but know how to administer a Linux server).
My question is how do I extract the relevant log files when Lineage fails to boot. I think I can always get into recovery (I installed TWRP in both slots), but I am lost as to where the log files from the previous (failed) boot attempt can be found and how I can extract them with TWRP. I suspect that one of the many partitions that Lineage expects, is not property formatted or has some mandatory parts missing, but without the log files, I am flying blind and don't know where to look.
Any help is very much appreciated.
Thanks,
Gloria
Click to expand...
Click to collapse
I normally monitor Boot process with adb logcat. Debugging should not be necessary, if you follow installation instructions from lineageos.org - especially having up-to-date stock ROM and not installing twrp app.