Database Develop

[ROM][LineageOS15.1][Oreo][Android 8.1.0] NightOwl Beta3

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is the NightOwl LineageOS 15.1 Android 8.1.0 Beta3 built from source for the Galaxy Note 1 GT-N7000/GT-N7000B
This LineageOS 15.1 based ROM is in Beta state and not ready for all day usage.
The main functions are working but there will be bugs!
Code:
Use my Roms only if you are sure about the risks of flashing custom Roms/Kernel to your device. I'm not responsible for any damage caused by using one of my files.
NOTE:
Because of the Rom Size and the ART runtime since Android 5 all Apps will need more space. If you want to install the rom together with Gapps you need to repartition your internal storage.
You can find more informations in the Howto Install section.
Changes:
Beta3:
* Updated los sources
* August security patches
* Fix mic-gain when multiple input streams are used
* Go settings without lowram flag set
* Acelerometer fixed
Older Changes:
Alpha2:
* Updated los sources
* April security patches
* First start wizard is working with installed gapps
* Youtube is working
* Added power profile settings
* Video playback mostly working
* Whatsapp videocalls working
Alpha1:
* First public release
Known Bugs Beta3:
* Installed gapps will cause a battery drain about 10%/h in standby
A part of the battery drain is caused by Wifi scanning which keeps Wifi always active.
Turn Wi-Fi Scanning off here: Settings -> Security & Privacy -> Location -> Scanning ->Wi-Fi scanning
This will reduce the battery drain but still something other (Ril?) is draining the battery too.
* If you get asked to instal/fix root/supersu in the recovery select no!
* Usb dialog not working. you can enable mtp mode in the developer settings
* Adoptable storage is not working (don't format your sdcard as internal!)
* Because of the rom size you need to repartition your /system and /data partition if you want to install gapps
How to Install:
If you are running a custom Kitkat(4.4) or newer Rom:
1. Copy Rom + Google Apps + recovery-twrp3.1.0-build2-isorec-n7000.zip + lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip to your external sdcard
2. Boot into recovery
3. Factory Reset + Format the /system partition
4. Flash the Rom zip file (without gapps in this step)
5. Flash recovery-twrp3.1.0-build2-isorec-n7000.zip
6. Reboot the recovery to enter the twrp isorec recovery
7. Flash lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip (Read the instructions in How to repartition your device!)
8. Flash gapps
9. Reboot
The steps to install it from an stock samsung rom are:
If you have already an samsung 4.1.x running you can skip step 1
1.flash N7000ZSLR1_N7000OZSLR1_BRI (or any other other 4.1.2) stock rom using odin
2.Copy Rom + Google Apps + recovery-twrp3.1.0-build2-isorec-n7000.zip + lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip to your external sdcard
3.flash PhilZ-cwm6-XXLT6-XSA-5.06.1.tar.md5 (https://www.androidfilehost.com/?fid=745425885120702299) to get cwm recovery with odin
4. boot into recovery
5. flash this kernel http://forum.xda-developers.com/devdb/project/dl/?id=20863 to get an updated recovery
(this step will make your old rom unbootable stuck in the n7000 screen but you can boot into recovery with press and hold "home" and "volume+" buttons and power on your phone)
6. you need to reboot! your device now to recovery
7. you are now in the updated recovery and you need to do a factory reset + format the /system partition
8. Flash the Rom zip file (without gapps in this step)
9. Flash recovery-twrp3.1.0-build2-isorec-n7000.zip
10. Reboot the recovery to enter the twrp isorec recovery
11. Flash lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip (Read the instructions in How to repartition your device!)
12. Flash gapps
13. Reboot
Updating If you are running an earlier NightOwl LineageOS 15.1 alpha version:
1. Copy Rom + recovery-twrp3.1.0-build2-isorec-n7000.zip + lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip to your external sdcard
2. Boot into recovery
3. Flash recovery-twrp3.1.0-build2-isorec-n7000.zip
4. Reboot the recovery to enter the twrp isorec recovery
5. Flash lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip (Read the instructions in How to repartition your device!)
6. Flash the Rom zip file
7. wipe dalvik cache
8. Reboot
How to repartition your device:
Because of partition size limitations you need to repartition your device to fit the rom together with gapps on the /system partition.
My example repit file (in the Downlodas section) will also enlarge the /data partition because the default size is to small for android 5+ if you want to install some apps.
Lanchon has made a tool which makes it possible to repartition your device in the recovery without loosing your data
https://github.com/Lanchon/REPIT
You need to have a working TWRP Recovery (CWM and Philz will not work)!
Make sure that you have at least 5GB free space on your internal sdcard0 before you start!
Make sure that your battery is charged and connect your device to the charger because repartitioning can take some time!
Installing the repit zip from the sdcard will fail the first time (because the sdcard is in use and can't unmounted) but the file gets copied to /tmp in this step.
After this select the repit zip to install from /tmp again and it should work
How to enable root:
1. Go to Settings-System-About phone and tip 7 times on Build number to enable the Developer options
2. Go to Settings-Developer options-Root access and set it to Apps and ADB
Don't install supersu (it will give you a boot loop!)
Downloads:
LineageOS 15.1 Beta3:
https://www.androidfilehost.com/?fid=3700668719832239373
Google Apps for lineage 15.1 (Use only after you have repartitioned your device! Suggested versions: micro, nano or pico):
http://opengapps.org/?arch=arm&api=8.1&variant=nano
Recovery flashable TWRP 3.1.0-0 build2 recovery (IsoRec)
https://www.androidfilehost.com/?fid=11050483647474832011
lanchon-repit-20170115-system=1536M+keep-data=6G+keep-sdcard=max+keep-preload=same+keep-n7000.zip
https://www.androidfilehost.com/?fid=11050483647474832009
Older Versions:
LineageOS 15.1 Beta2:
https://www.androidfilehost.com/?fid=11050483647474833224
LineageOS 15.1 Beta1:
https://www.androidfilehost.com/?fid=11050483647474832010
LineageOS 15.1 Alpha2:
https://forum.xda-developers.com/devdb/project/dl/?id=29271
LineageOS 15.1 Alpha1:
https://forum.xda-developers.com/devdb/project/dl/?id=29024
A big THX to:
LineageOS Team
rINanDO (Many parts in this Rom are based on his work for the i9100)
forkbomb444
XDA:DevDB Information
[ROM][LineageOS15.1][Oreo][Android 8.1.0] NightOwl Beta3, ROM for the Samsung Galaxy Note GT-N7000
Contributors
bauner
Source Code: https://github.com/bauner
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Kitkat(4.4) or newer compatible custom recovery
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Beta Version: Beta3
Beta Release Date: 2018-08-12
Created 2018-03-30
Last Updated 2019-03-07

Awesome news incredible history. Many thanks Dev @bauner
Sent from my Redmi 4X using XDA Labs

Thanks a lot for the Rom @bauner
Clean flashed it on my GT-N7000 now and so far couldn't find any bugs that aren't known yet
Since it's my 2nd Phone I can't test anything RIL related but I'll try to check for any other bugs.
Do you know if we'll ever be able to install Magisk to our Note / What's the reason that we can't install it? I've read something about our Devices Ramdisk being different.

Dear bauner
Wow! Thank you so much!
Sincerely

Oh my!!! @bauner you're an absolute legend! Can't thank you enough for giving us the opportunity to try out the latest and greatest version of Android on our beloved Galaxy note!
I'll give it a try in a few days. I'm so excited. Thanks so much.
Cheers ?

whew my eyes...
btw first time trying f2fs installation on n7000, and it booted (unexpected as I see most of n7000 rom thread wrote nothing on f2fs support) gonna try it out
phone seems couldn't power on while charging with this kernel. Nice charging screen tho, love it
Thanks Bauner
EDIT: It seems won't boot (stuck at the charging screen) only if the battery is too low.
EDIT 2 : I don't know whether this is because of f2fs or what, I can feel that it performs much better than nougat (i mean on first boot of both rom)

Kiddos like screenies ~ :3
The lines in screenshot only applies to screenshot file - see statement by OP in first post

Thank you Bauner!

Thank you alot Bauner❤❤❤

Bugs I've seen so far since yesterday
•Youtube video playback broken (i can watch youtube on gello)
•Split screen
•occassional signal loss which requires reboot to be back again
•camera picture settings
•no signal sometimes whenwver i reboot, i have to reboot again for the aignal to come back

haveyouseenthisboi said:
Bugs I've seen so far since yesterday
•Youtube video playback broken (i can watch youtube on gello)
•Split screen
•occassional signal loss which requires reboot to be back again
•camera picture settings
•no signal sometimes whenwver i reboot, i have to reboot again for the aignal to come back
Click to expand...
Click to collapse
The youtube video problem is known
The rom is a android go build which does not support split screen
Can you reproduce the signal loss or will it happen randomly?
Which camera setting will not work for you?

Can't test it in this level (Daily phone and all)
just wanted to say thank you Bauner for supporting Note!

haveyouseenthisboi said:
Bugs I've seen so far since yesterday
•Split screen
Click to expand...
Click to collapse
Split screen works perfectly, but to use split scrren, you need to set the low ram flag in build.prop to false
*You will notice a slight change in ui such as recents and screen off animation

Oh i found out that it was not really a signal loss but a random no simcard. It is random everytime i reboot the phone. I have to reboot again for the system to "detect" the sim again

haveyouseenthisboi said:
Oh i found out that it was not really a signal loss but a random no simcard. It is random everytime i reboot the phone. I have to reboot again for the system to "detect" the sim again
Click to expand...
Click to collapse
Welp I also face this problem since months ago (during last year, running rros nougat)... Tried several time of clean install of nougat but didn't help, even with a different sim. Hopefully as for now the issue has not come back again for me on los15.
I tot I'm the only one facing this issue ._. as I'm expecting this is hardware related problem. I'm highly confident this is not software related. My sis and my mom they both using n7000 as daily driver with rros nougat running since clean install during earlier last year, and they didn't hv this/any problem until now. (My mom make many phone calls everyday. ) Guess should be due to the worsening condition of the modem chip, maybe is because of the heat released from CPU is too much?

Interestingly I only got the no sim bug on bauner's cm12 and los15.1

Seems like it was unable to boot sometimes, when the phone is charging, even when it already charged full. Best to remove charger and boot. Else sometimes it will stuck at charging screen, then will need to reboot by long pressing the power button.
Sometimes shutdown or reboot, it will like stuck for a moment before reset.(should be kernel related?) Like if in TWRP, if press reboot, it will stuck there for around 5 seconds or more, in my case 15 seconds longest, before it really reset.
There's no thermal sensors detected. Can't see the temperature of system.
Until today still smooth like hell. No idea why haha I'm using lowram flag = false.
Surprisingly there aren't any MTP Host related FC Dialog anymore 0.0 I will try out MTP soon.
Overall, what a legend! Thanks OP! It seems like it is a joke to tell people that note 1 is running Oreo :laugh:
But not.

Is there any way to get trusted face without mano gapps

ritik jaiswal said:
Wanted to flash nano gapps
In Pico no voice assistant, no voice unlock, no face unlock
Neither the Google app
Is there any way
Click to expand...
Click to collapse
With the default /system partition size you will not have enough free space to install nano gapps.
To fit bigger gapps as pico with lineage 15.1 you need to repartition the /system partition too.
https://forum.xda-developers.com/showpost.php?p=66341193&postcount=2071

bauner said:
With the default /system partition size you will not have enough free space to install nano gapps.
To fit bigger gapps as pico with lineage 15.1 you need to repartition the /system partition too.
https://forum.xda-developers.com/showpost.php?p=66341193&postcount=2071
Click to expand...
Click to collapse
Thank you for this.
Anyways, my internal storage shows as corrupted in 8.1.0. Not able to access it. Did I miss something?
Apart from this, everything is working great! Thank you once again for keeping this phone alive @bauner.

[ROM][UNOFFICIAL][11] LineageOS 18.1 [T710][T715][T715Y][T810][T815][T815Y]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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 us for messing up your device, I will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: Whenever I try flashing any lineage-18.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Q-based rom within a version of TWRP older than 3.5. Simply flash the linked below version 3.5 or higher, reboot back into recovery, and flash the rom zip again.
Q: Will any of the variants ever receive official builds from LineageOS?
A: In short, no. The reason is that, in order to get a modern version of Android working properly on an ageing device some legacy commits needed to have been re-introduced into the current source branch. These include a fix for something as fundamental as Wi-Fi.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
ROMs
- SM-T710: gts28wifi
- SM-T715/Y: gts28ltexx
- SM-T810: gts210wifi
- SM-T815/Y: gts210ltexx
Open GApps
Magisk
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 18.1 variant, which corresponds to the model of your tablet!
How to flash LineageOS and Open GApps​FULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode,
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your tablet and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the tablet.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- The microphone is able to record sound, but the sound is very faint. This is due to Samsung's proprietary drivers, as determined by Skulldron.
- T710 & T715/Y: Camera viewfinder is misaligned with the dimentions of the display, such that the shutter button is almost off the screen
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- bonuzzz, McFy, Skulldron, RaymanFX, CTXz, T_I, and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the gts28ltexx, gts28wifi, gts210ltexx, and gts210wifi.
Sources
- LineageOS
- universal5433
XDA:DevDB Information
LineageOS 18.1, ROM for the Samsung Galaxy Tab S2
Contributors
ripee, ananjaser1211
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 11
Stable Release Date: 2021-09-17
Created 2018-12-15
Last Updated 2020-12-29

Join us on Telegram!
LineageOS is part of the Tab S2 ROM Universe, courtesy of Skulldron.

Reserved

Thanks for the hard work, Ripee.
The ROM works great on my T815; good battery life and performance.

mixer paths
low mic gain and speaker volume seem to be related to the mixer , 2 other roms that are based on stock dont seem to have these issues, will try to port over a fix for the audio. so far everything else works . t710

715 working without problems
Hi, nice to have a dedicated new thread (after the slow dying of bonuzz's thread).
I installed the latest version on my SM-T715 and using it without any problems until now.
Using Magisk v18.
All my apps work after restoring them from Titanium Backup.
No problems with fingerprint (using left hand finger and right hand thumb).
Thanks for your support.

710 new build 1216
Camera works, window still not sized correctly
Mic gain not good
Checking audio

Anybody else also experiencing slower charging of the T810 than before? Mine needs several hours (3+) to be fully charged, before maybe 90 Minutes.
Or maybe its the battery, too old.

dombo1970 said:
Anybody else also experiencing slower charging of the T810 than before? Mine needs several hours (3+) to be fully charged, before maybe 90 Minutes.
Or maybe its the battery, too old.
Click to expand...
Click to collapse
Yes, I actually felt the same, although I didn't measure the time and I have only charged once with this ROM.
Not a big deal though and everything else works great. Battery life seems improved too.

Changelog
Build 1217 for all variants
* Speaker and mic gain fixed, courtesy of Skulldron
* Synced with LineageOS sources

Thanks for your great work! Nice to see that the t815 will receive updates after LOS has dropped it.
Is it possible to provide check-sums for the download files? THX!

ripee said:
Changelog
Build 1217 for all variants
* Speaker and mic gain fixed, courtesy of Skulldron
* Synced with LineageOS sources
Click to expand...
Click to collapse
Great job.

Had to switch back to Nougat.
Telephone didn't work - I could call but nobody could here me. People called me today but I didn't reveive it (nothing, no ring, no message).
And my usual VPN-Connection to my Fritz-Box didn't work.

ThaiDai said:
Had to switch back to Nougat.
Telephone didn't work - I could call but nobody could here me. People called me today but I didn't reveive it (nothing, no ring, no message).
And my usual VPN-Connection to my Fritz-Box didn't work.
Click to expand...
Click to collapse
Did you try Google's own dialer app? AOSP apps can be buggy with uncommonly used functions, such as calling on a tablet.

ripee said:
Did you try Google's own dialer app? AOSP apps can be buggy with uncommonly used functions, such as calling on a tablet.
Click to expand...
Click to collapse
No, I didn't. Simply need a working phone - no time for trying different solutions (I missed a call from school informing me that my daughter is sick).
May try again in the christmas holidays.

Nope no sound on 710

Somehow, in messenger lite, during videochat even if I see myself and the other party, the other party can't see me, just connecting video appears on the screen forever. T810 12.11 build.

Anybody with T815... How is idle drain? ROM works like an absolute champ but noticing strange idle drains while on airplane mode and everything off. Will check BBS overnight tonight to see if it sleeps at all.

Meakii said:
Anybody with T815... How is idle drain? ROM works like an absolute champ but noticing strange idle drains while on airplane mode and everything off. Will check BBS overnight tonight to see if it sleeps at all.
Click to expand...
Click to collapse
No deep sleep for me also, couldn't find any solution so far!

tripLr said:
Nope no sound on 710[/Q
Sound works fine (WiFi not LTE)
Click to expand...
Click to collapse

[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera
Audio
FM radio
Torchlight
LED
USB and WLAN tethering
Fingerprint sensor
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8704, https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
2020-03-20
Enable DT2W
Update Lineage code
mailru: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200320.img (source code)
Previous versions:
2019-12-27
Fixed fingerprint scaner issue
mailru: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200316.img (source code)
2019-12-25
Fixed OTG mode
enable target ttl for thethering with some operators
Updated Lineage code
mailru: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
2019-08-11
Fixed insert/remove detection for 3.5'' headset plug
Updated Lineage code
mailru: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
2019-07-14
Initial release
mailru: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F)
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TB-8704V (Verizon)
If you have TB-8704V tablet, you have to additionaly flash boot.img from link above after rom intsallation. This tablet has some hardware differences from x and f and requires custom kernel to work,
Thanks
Big thank to @mistersixt, who donated $$ for device.
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-wip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2019-07-21
Last Updated 2019-08-11

Installed it and everything seems to be working great. Many thanks for your work

Can't seem to get it boot on tb8704v (boot loop). I have unlocked rebooted and made sure oem unlock was still checked and installed twrp-3.2.3-0-tb_8704v and then installed rom and gapps. But it just boot loops on restart. I'm missing something?

Thank you so much for all your hard work.

I am unable to install gapps, its stuck on "mounting /persist /system" is there any work around?

wow! can't wait to flash this! thanks so much!
Just noticed in the OP you have "ROM OS Version: 7.x Nougat" Don't you mean 9.x?

Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.

Acel337 said:
Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.
Click to expand...
Click to collapse
Are you on tb8704f?

hunnia41 said:
Are you on tb8704f?
Click to expand...
Click to collapse
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.

Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
I did the same . but I had stock 8.1 installed. I installed mindthegapps as well as the ROM and rebooted and everything seems to be working fine.

I also had 14.1 installed before. Unfortunately I have the same problem as Acel337. I have the tb8704x.
Has anyone found a solution yet?
14.1 starts without problems after flashing again.

I dirty flashed over los 14. Then flashed openGapps 9 pico. Then reflashed the latest magisk. ROM boots after about 5 minutes without any issues.
Chrome reloads on occasion. I have root, don't have rw. The remount script doesn't work. Netflix casts well. That's as far as I've got.
Thank you for this!
Update: rw now working

Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
For me evrythin works
8.0 stock rom
install magisk
install twrp
system writable
erase system data.
sideload pie and gapps.
Everyhing works perfectly.
Maybe the difference, that I started from 8.1 stock
Just a thought. It could be, that indirectly the (wrong) encryption cause the problem. Since when booting, the program tries to populate the data partition, and if it cannot do it, since it appears as 0 storage, it might just stuck in a loop.

How do you get /system to be writable?

Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014

Hemphiz said:
Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014
Click to expand...
Click to collapse
"I'll be sending a Donation "
I did too. The first time in my life for firmware. I have no problem so far. (Used it 24 hours.)
---------- Post added at 06:51 AM ---------- Previous post was at 06:34 AM ----------
Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
Seemingly you did everything, which had to be done. If it is a problem with the firmware, maybe it has to do with the encryption. (Cannot encrypt the data.) Just a guess, since it works for so many people.
maybe you should reflash the 8.1 stock rom. If it works, try again to reinstall lineage pie. If it still fails, go back to stock until problem is solved.

The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.

Could we get some gamepads working up on this mofo please? That would be the Cherry

same here, TB-8704F stuck on lineage bootanimation too
Acel337 said:
The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.
Click to expand...
Click to collapse
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation

robidick said:
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation
Click to expand...
Click to collapse
I did exactly the same thing with the following exceptions. (whether they are significant or not I do not know.
1. Went into twrp without installing it and unrooted with Magisk. (side load)
(Then I do not remember whether I booted up in stock, to check by magisk whether dm-verify was off. It should be)
then I rebooted into fastboot and installed twrp and in my case I made system writable.
After this I proceeded as you discribed.

[9.0][TREBLE]PixelExperience / PixelExperience Plus Pie [UNOFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Moto Z2 Play [albus]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Install stock oreo before installing Custom ROMs, see notes below for further info
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Moto Mods/Moto Snaps
Encryption
FM Radio
Known issues
VoLTE/VoWIFI
Moto Snap Hasselblad Zoom Camera
Moto Snap Projetor is unknown to work
DON'T FLASH GAPPS, ALREADY INCLUDED
Download PixelExperience from AFH
Download PixelExperience Plus from AFH
Telegram channelD
Z2 Play Custom ROMs Group
Z2 Play Global Group​
Instructions:
Always have a backup of the EFS partition made with TWRP stored somewhere, as you may lose IMEI. Restore it if you get 0 as IMEI when booted into the ROM.
Before installing, make sure oreo was the last stock ROM you installed. See notes below if you come from Stock Pie
Download Official TWRP from twrp.me
Flash the TWRP via fastboot
Enter TWRP, go to wipe menu and Wipe Dalvik, Cache, Data, System and Internal Storage.
In TWRP Wipe Menu, do Format Data, then reboot into recovery
Flash the latest build
Reboot
Notes
TWRP
If the touchscreen doesn't work when rebooting into recovery, press the power button twice to turn off and on the screen. The touchscreen will now work just fine.
GSIs
This LineageOS build ships with Project Treble compatibility (lite VNDK), meaning you can flash a GSI as System Image from TWRP. Please don't report GSI bugs here, report them instead to the GSI's maker. A Format Data from TWRP is required after flashing a GSI in order to avoid problems.
Technical details on our Treble implementation:
This device is a community-treble device, meaning other devs before us made it compatible with Project Treble (lite VNDK), using the oem partion as a vendor. GSIs still have some problems regarding cpu frequency scaling and camera. You have been warned.
Coming from stock pie?
For the sake of simplicity, I said that coming from stock oreo was needed. In reality you just need to flash the oreo modem files. There's a script that does exactly that, made by @juniorpassos: https://mega.nz/file/IRxjGDjL#vkdvh4JcMy-LuWgQz4rHhgpWV80029X4ql0_zcMpVug. The script will erase your userdata and cache.
Before starting this script, make sure you have a backup of your EFS partition stored somewhere safe, outside phone's internal storage. After the backup is done, you can reboot your phone into fastboot mode and start the script. Now reboot into TWRP, go into "Wipe" menu and Format Data. Now you can reboot into the ROM. If you get 0 as IMEI, or any other problem related to RIL, go into TWRP and restore the EFS backup made previously.
Wanna help?
If you find a problem or a bug, please share a logcat with us, alongside an explanation of the problem and steps to reproduce. We won't accept bug reporting without a logcat. Collect logcat with:
Code:
adb logcat -b all > logcat.txt
Thanks
Many thanks to @marcost22 for the pair-working we are doing in this adventure, to @davidsonsjesus for his work on KVT, to @jeferson1979 for his help and teaching. Thanks to all the testers that have helped us testing this ROM.
Sources
Device tree
Vendor tree
Kernel
ROM Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
PixelExperience 9.0, ROM for the Moto Z2 Play
Contributors
EmaMaker, marcost22, rahulsnair, @erfanoabdi @vache @kubersharma @jeferson1979
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Based On: PixelExperience
Version Information
Status: Stable
Current Stable Version: 9.0
Stable Release Date: 2020-09-27
Created 2020-09-27
Last Updated 2020-09-30

Reserved

Changelog
2020-12-08: Cleanup and uprev kernel (3.18.113->3
18.116). Update camera blobs: fix Electronic Image Stabilization, bring back laser focus sensor, fix recording in WhatsApp., fix issues with video recording in Snap cam Fix encryption and decryption (official twrp over at twrp.me is needed for this to fully work). SeLinux is now Enforcing. Update VNDK to full enforcement. Update graphics props. This is the final build for Android Pie 9.0. We will will soon start the Q bringup, and will not be building any Pie ROM anymore, unless some critical bug is discovered:
https://www.androidfilehost.com/?w=files&flid=317960
2020-09-26: Initial build https://www.androidfilehost.com/?w=files&flid=317960

Great! The Z2 is still alive! What's the diference between the normal and the plus version?

Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage

OldUncle said:
Failed to mount '/data' (Invalid argument)
...done
Unable to mount storage
Click to expand...
Click to collapse
Enter TWRP and Format Data, then reboot to TWRP again. You may need to repeat this a couple of times

ramelco said:
Great! The Z2 is still alive! What's the diference between the normal and the plus version?
Click to expand...
Click to collapse
Normal version is plain PixelExperience. Plus version includes some tweaks we all like: a bit of customization for status bar and themes (dark theme included for system and notifications!), some gestures like the three-finger-screenshot, advanced restart and others. I think you can find more info on the PE website

when i flash and then boot to system, it prompts me to enter a password, but...i don't have one.
edit: i have not gotten it to work. i just reflashed it.
when i did that, i wiped the cache and dalvik and all that, but rebooted back to bootloader, then ran the script (i came from 9.0 stock), and it flashed, everything rebooted, i got into the phone, and it doesn't think there's a cellular signal. the IMEI seems fine, it's the right string of numbers, but nothing i do will get it to actually register the sim is in.. or rather, it does read the sim. it knows what phone number is on it, but absolutely nothing else.
is this a case where i have to restore me EFI? when i try to do that, it tells me i failed to select a partition, but there's no partition to actually select...

Tried re installing the script? Or flash the oreo modem file via fastboot

ramelco said:
Tried re installing the script? Or flash the oreo modem file via fastboot
Click to expand...
Click to collapse
yeah. i tried that, and then i even went back to stock 9.0 (no idea how to go back to 8, i've tried just flashing normally through fastboot like you do for 9, but it just doesn't work), flashed the 8.0 modem, nada. even on stock 9 i my cellular radio just doesn't seem to work.
in twrp, when i go to restore my EFS backup, it complains that there was no partition selected, but i don't actually get a partition to select. i honestly have no idea what the hell i did to achieve this, but i did.
edit: i was able to get the radio working in stock pie, by fastboot loading erase modemst1/st2 but that doesn't appear to work on this rom
edit 2: let me describe the steps i'm taking here. i boot into twrp, i wipe dalvik/cache, cache, system, data, storage, reboot back into twrp, format data and reboot back into twrp. flash the rom, reboot to bootloader, run the script, boot back into twrp and flash data.
i don't see anything i'm doing wrong, but maybe i am?

likehelly said:
yeah. i tried that, and then i even went back to stock 9.0 (no idea how to go back to 8, i've tried just flashing normally through fastboot like you do for 9, but it just doesn't work), flashed the 8.0 modem, nada. even on stock 9 i my cellular radio just doesn't seem to work.
in twrp, when i go to restore my EFS backup, it complains that there was no partition selected, but i don't actually get a partition to select. i honestly have no idea what the hell i did to achieve this, but i did.
edit: i was able to get the radio working in stock pie, by fastboot loading erase modemst1/st2 but that doesn't appear to work on this rom
edit 2: let me describe the steps i'm taking here. i boot into twrp, i wipe dalvik/cache, cache, system, data, storage, reboot back into twrp, format data and reboot back into twrp. flash the rom, reboot to bootloader, run the script, boot back into twrp and flash data.
i don't see anything i'm doing wrong, but maybe i am?
Click to expand...
Click to collapse
Why would you go back to stock pie, when the instructions clearly say stock Oreo. There's a tutorial on the forums and everything, flashing any version of stock is the same procedure, you just need the specified Oreo version listed in the firmware section of the OP. Not that hard

[ROM][BETA][UNOFFICIAL][11] LineageOS 18.1 for Galaxy A70

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Flashlight
Keystore
Fingerprint
FOD
Known issues:
VoLTE
Selinux is permissive
Bluetooth
Voice calls on second sim slot
Instructions :
If you're on Pie firmware, flash OneUI 2.X firmware.
Download the latest build.
Reboot to recovery
Optional: Create backup of your current rom.
Flash the latest build.
Optional: Flash GApps for Google Services.
Optional: Flash forceencrypt disabler
Reboot
Downloads :
Google Drive
NikGapps (Opengapps haven't released 11 yet.)
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][BETA][UNOFFICIAL][11] LineageOS 18.1 for Galaxy A70], ROM for the Samsung Galaxy A70
Contributors
@ataberkozen @Grarak
Source Code: https://github.com/LineageOS
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
ROM Firmware Required: OneU 2.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2021-01-10
Created 2021-01-10
Last Updated 2021-01-10

Changelogs :
Public Beta 2 - 10/01/2021 :
Fix WIFI on some models.
Public Beta 1 - 10/01/2021 :
First beta release.

I will NOT accept your bug report if you are using a custom kernel.
I will NOT accept your bug report if you are using a modification (Like some magisk modules etc.).
I will NOT check your bug report if you didn't provide any logs (I may still check some.).

I might be slow to respond due incoming very important high education exam. But I'll be active on my free time.

I'm on a A705MN and Using TWRP with full wipe and no other rom installed, but keep getting error:
E2001: Failed to update vendor image. Updater process ended with ERROR
I cannot figure out what to do? I really don't wan to have to Odin flash stock, and start over to have the same error come up. Any ideas?

gaderderian said:
I'm on a A705MN and Using TWRP with full wipe and no other rom installed, but keep getting error:
E2001: Failed to update vendor image. Updater process ended with ERROR
I cannot figure out what to do? I really don't wan to have to Odin flash stock, and start over to have the same error come up. Any ideas?
Click to expand...
Click to collapse
Can you type "blockdev --getsize64 /dev/block/bootdevice/by-name/vendor" in twrp terminal and send output here so I can quickly build update for you ?

ataberkozen said:
Can you type "blockdev --getsize64 /dev/block/bootdevice/by-name/vendor" in twrp terminal and send output here so I can quickly build update for you ?
Click to expand...
Click to collapse
output = 1048576000

gaderderian said:
output = 1048576000
Click to expand...
Click to collapse
Vendor size is exact match. Try flashing grarak's latest twrp and be sure zip is not corrupted.

New update is up.

ataberkozen said:
Vendor size is exact match. Try flashing grarak's latest twrp and be sure zip is not corrupted.
Click to expand...
Click to collapse
Okay I update TWRP to twrp.3.4.0.0-26112020-a70q.img
Now I get error
E3004: This package is for device: a70q: this device is .
I'm on A705MN

gaderderian said:
Okay I update TWRP to twrp.3.4.0.0-26112020-a70q.img
Now I get error
E3004: This package is for device: a70q: this device is .
I'm on A705MN
Click to expand...
Click to collapse
Hi. please unmount system first or reboot recovery.

ataberkozen said:
Hi. please unmount system first or reboot recovery.
Click to expand...
Click to collapse
I'm not sure what you mean. Nothing is mounted. I reboot recovery, wipe cache, dalvik, system, and data
Then I try and install your Rom and same E3004 error

gaderderian said:
I'm not sure what you mean. Nothing is mounted. I reboot recovery, wipe cache, dalvik, system, and data
Then I try and install your Rom and same E3004 error
Click to expand...
Click to collapse
Just reboot recovery. Don't wipe this time and install rom.

ataberkozen said:
Just reboot recovery. Don't wipe this time and install rom.
Click to expand...
Click to collapse
I did. Same error. There is no OS installed

I did not see you updated to v3. I'll downloaded and try again

ataberkozen said:
Just reboot recovery. Don't wipe this time and install rom.
Click to expand...
Click to collapse
Okay v3 flashed. It then bootlooped but I flashed the forceencrypt disabler and it looks to be booting up. I'll see how it runs

gaderderian said:
Okay v3 flashed. It then bootlooped but I flashed the forceencrypt disabler and it looks to be booting up. I'll see how it runs
Click to expand...
Click to collapse
It's been on the linageOS animation for about 15 minutes without getting into the setup wizard.

gaderderian said:
It's been on the linageOS animation for about 15 minutes without getting into the setup wizard.
Click to expand...
Click to collapse
You have to wipe your data. At first boot your data got encrypted.

ataberkozen said:
You have to wipe your data. At first boot your data got encrypted.
Click to expand...
Click to collapse
It's still stuck so I will try, but I'm not sure which wipe you are referring to. If I boot back into TWRP, do I have to advance wipe data, or do the format and type "yes"?

gaderderian said:
It's still stuck so I will try, but I'm not sure which wipe you are referring to. If I boot back into TWRP, do I have to advance wipe data, or do the format and type "yes"?
Click to expand...
Click to collapse
Yep.