LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
NOTE: This build is unofficial, don't report bugs to the official LineageOS bug tracker.
HOW TO FLASH
Download the ROM from here
Download GAPPS from here
Install TWRP recovery from this thread
Boot to recovery
Wipe Data/Factory reset
Flash LineageOS
Flash GAPPS
Wipe Cache/Dalvik
Boot to system
What works
Audio
Camera
RIL (calls, sms, etc)
GPS
Bluetooth
WiFi
Everything else not listed below
What doesn't work
HDR
WiFi Hotspot
Wireless display
Before asking any question read the FAQ below
Big thanks to @voidzero for letting me use his server to build and for the initial device tree
XDA:DevDB Information
[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s, ROM for the HTC One (M8)
Contributors
root-expert, voidzero
Source Code: https://github.com/M8s-dev/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M firmware base
Version Information
Status: Stable
Beta Release Date: 2018-06-18
Created 2018-06-18
Last Updated 2018-10-27
Changelog
Code:
[B][U]26 October 2018[/U][/B]
* Instagram videos fixed
Code:
[B][U]18 October 2018[/U][/B]
* August/September/October ASB merged
* Use sdFAT instead of exFAT
* Reduce GPS fix time
* Increased speaker volume
* Increased microphone volume
* Increased upper earpiece volume when in-call
* Enabled HDR
* Fixed wakelock
Code:
[B][U]26 July 2018[/U][/B]
* July Android Security updates
* Kernel updated from tag 3.10.49 to tag 3.10.108
* Bluetooth now recognises the correct bt address
* Use low-latency as primary output for notifications and ringtone
* Switched SELinux to enforcing
* When usb composition is on "charge only" adb works
* Enabled audio offloading
* Added the option to disable Double Tap to wake gesture
* Added option to unlock phone with a gesture (you can find it under gestures tab)
* Used newer WiFi configuration files (hope that fixes WiFi problems)
* The name "HTC One M8s" is shown to your pc when connected instead of "Android Phone"
Code:
[B][U]20 June 2018[/U][/B]
[LIST]
[*]Fixed headphones microphone
[/LIST]
Code:
[B][U]18 June 2018[/U][/B]
[LIST]
[*]Initial commit
[/LIST]
Frequently Asked Questions (FAQ)
Q: I flashed the ROM and I'm getting random reboots and crashes
A: Ensure that before flashing this ROM your last stock rom was Android version 6.0. If not follow the instructions on the post below
Q: I found a bug, what should I do?
A: Describe in this thread the issue as best as you can and include steps to reproduce.
Also include a logcat taken the time that the bug happens.
If you had a random reboot don't bother taking a logcat instead pull /sys/fs/pstore/console-ramoops file and atach it to your post.
Q: I want to root this ROM. Should I flash something?
A: Either download su addon from https://download.lineageos.org/extras or flash Magisk.
If you are coming from CM12.1 (Just like I did) then follow these steps
NOTE: If you do not follow these steps, your final Oreo ROM (LOS 15) will crash, you'll suffer randoms reboots and instability problems due to incompatible radio / HTC firmware. This whole update process to Stock 6.0 can take up to 4 hours! So make sure you have the time to do everything correctly, don't cut corners.
I suffered
1. Create a full backup of your ROM using TWRP (v2.8 or v3.0.2.0), Copy your INTERNAL STORAGE and SD Card contents to PC .
During the upgrade from "CM12.1 > 5.0.1 Stock > 6 Stock > LOS 15" you WILL lose your internal data! (because of bootloader relock & unlock again)
2. Relock your bootloader; (Make sure you are using the htc_fastboot.exe)
Turn off phone
Go into bootloader (Hold down VOL DOWN+Power button
Connect USB and enter Fastboot (Should show as FASTBOOT USB)
Open commandprompt;
Code:
htc_fastboot oem lock
The phone should restart and show up as ***RELOCKED***
3. Get your matching RUU from https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If you dont know which RUU to get, follow this thread; https://forum.xda-developers.com/ht...lp-thread-htc-one-m8s-to-stock-howto-t3190238 (M8sQL_UL > Firmware (Expert)>Firmware Crypted (Original HTC))
If you get the "Device halted due to Large Image update fail" error during installation, just try another RUU - but make sure it matches your CID.
I got it working using a "signed" version. The "combined-signed" version did not work for me. Your mileage may very.
Click to expand...
Click to collapse
4. In Android Stock (5.0.1), continue the setup and after that go to: Settings > Software updates (At the bottom) > Check for updates
At first I only got 2 APP updates: "HTC Sense" and some other app (cant remember). Update both apps and reboot.
After a reboot check again for updates. Now you get a ~400Mb update. Download and install.
After the first update check again for updates. Now you get a ~1.23Gb update (Update to Marshmallow, Part 1 of 2). Download and install.
After that check again, and now you'll get a ~700Mb update (Update to Marshmallow, Part 2 of 2.)
That's it for going back to the most recent stock version. You now have Android 6.0 Stock running.
To install TWRP (if you want to flash LOS 15)
1. Unlock your bootloader again.
Go to https://www.htcdev.com/bootloader/ and follow the instructions.
2. Flash TWRP.
Code:
htc_fastboot flash recovery twrp-recovery-image-name-and-version.img
After that:
Wipe Cache/Dalvik, Data and System
Install LOS15
Wipe Dalvik again
Flash Gapps
Wipe Dalvik
Boot
Say thank you to @root-expert for keeping this phone alive with the development and @voidzero for providing the build-environment / mirrors
- Jeroen
Nice job! Great work on the rom and keeping the one m8s alive!
New build up!
Headphones microphone is now fixed.
Grab it as usual from here
-Chris
For the users who want to remove the"root icon" ( the status bar), there is no setting to disable it.
{
"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"
}
To remove it:
Connect your M8s to PC with USB
Open CMD
Code:
adb shell settings get secure icon_blacklist
The output is:
Code:
[COLOR="Red"]rotate,headset[/COLOR]
Now enter the output + su
Code:
adb shell settings put secure icon_blacklist rotate,headset,[COLOR="red"]su[/COLOR]
And after that:
Code:
adb reboot
Now the "#" icon is gone from the status bar.
- Jeroen
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
brunkonjaa said:
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
Click to expand...
Click to collapse
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
root-expert said:
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
Click to expand...
Click to collapse
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
brunkonjaa said:
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
Click to expand...
Click to collapse
I don't believe you have to do that. The only requirement is that your last stock android version was Android 6.0
Post battery statistics here
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
GeoEgbA said:
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
Click to expand...
Click to collapse
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Problem with google play services
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
Click to expand...
Click to collapse
View attachment recovery.log
Try by twrp-3.0.2-0-m8ql.img
View attachment twrp-3.0.2-0-m8ql.zip
GeoEgbA said:
View attachment 4533829
Try by twrp-3.0.2-0-m8ql.img
View attachment 4533830
Click to expand...
Click to collapse
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
monkyMatys said:
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
Click to expand...
Click to collapse
Hello,
Ensure that you flashed GAPPS straight after flashing the ROM WITHOUT rebooting to system. If you reboot to system and then flash GAPPS you'll have problem and crashes like you do. Also ensure that your previous stock andorid version was android 6.0. If not follow the instructions on this thread to revert back to stock and then try to flash the ROM
-Chris
root-expert said:
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
Click to expand...
Click to collapse
Yes yes that why i wrote that need 3.2.1..0 becouse on 3.0.2.0 get error 7. I flash 3.2.1.0 anf LOS and work great for 15h now sorry for confusion
How long should the first boot take? i followed the instructions, twrp 3.2.1 gave a /persist error but everything else seemed fine. its been 20m and im at the lineage os boot screen.
Related
{
"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:
#include <std_disclaimer.h>
/*
[COLOR="Red"]* Your warranty is now void.[/COLOR]
*
* 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.
*/
The "N" is for Nougat
some words of wisdom:
1- This is an Android 7.1 Nougat-based release - update your third party addons to ensure compatibility
2- The CM backupscript.sh in recovery will ignore and remove incompatible applications from your system partition (these are usually non-CM apps that users have opted to install). You must install a compatible app (or app pack) to regain that functionality
3- You can flash CM14.1 nightlies directly from CM13 snapshot or CM 13 nightlies (no need to wipe, BUT for optimum results, better follow Clean Update procedure explain below.), provided you read and followed items 1 and 2
ALLERT:
4- Once one CM14 nightlies, you cannot downgrade back to CM13 – if you are thinking of just exploring the release, then take a backup of your existing installation if you want to go back to it.
5- You’ll need an N compatible recovery, i.e. TWRP 3.0.2-1
Happy Flashing,
Latest features :
XDA:DevDB Information
Cyanogenmod 14.1 for Falcon, ROM for the Moto G
Contributors
matmutant, luca020400, LuK1337, Google, CyanogenMod Team, Motorola
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Firmware Required: CyanogenMod13
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-11-09
Last Updated 2016-11-19
Download & Install
LINKs:
All Downloads
Nightly Changelog
OpenGapps choose ARM>7.1>micro/nano/pico (micro might still be too big... unless you use the custom install options that allows you not to install everything from the package)
Either way, you might want to further customize your installation (both gapps and system apps), refer to this tutorial
REMEMBER:
ONLY use TWRP 3.0.2-1 or up
/!\ Before installing, read post #3. /!\
HOW TO INSTALL
Requirements: Unlocked Bootloader, a Nougat compatible Custom Recovery and the Downloaded Zips.
NB: Since 20161118, with a Lollipop compatible recovery like TWRP 3.0.2-0, you will get stuck to recovery, It is MANDATORY to update to 3.0.2-1.; the following error is still present : E:unknown command [log] but will not prevent install.
Place the rom and other like Gapps on the internal Storage or on a USB OTG
Reboot to recovery using the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Do Wipes (Data, Cache, Dalvik and System partitions) if you are in a different ROM.
Select the Zips
Swipe to install (if using TWRP)
Reboot and wait 2-3 min
-Not confirmed for CM14 as of 20161109- Pro-TIP : To avoid GPS locking issue, refer to #Q7 of the CM12 dedicated FAQ
HOW TO DIRTY UPDATE
Download the rom zip using CM Updater or third party apps like CM downloader, CyanDelta...
Press update.
Wait 2-3 min
HOW TO CLEAN UPDATE : this kind of update helps to avoid any update related issues, you can follow this when coming from CM13 and want to keep you personal data.
ProTip : Read the Changelog and disable features that have been updated between your build and the latest build (this is important when Theme features are updated and it could break things)
Download the rom zip on the CM Website or using CM Updater or third party apps like CM downloader, CyanDelta... make sure you have gapps zip on your device
Reboot to recovery using the power menu or the hotkey ( PowerOff+Vol- => With Vol- Go to Recovery => Select the recovery option with Vol+ )
Format /system, /cache and /dalvik-cache (advance format in wipe menu of TWRP); do NOT Wipe DATA!
Select the Zips
Swipe to install
Reboot and wait 2-3 min
Notes, Bugs, and miscellaneous.
Tips and notes:
When choosing a Gapps package ensure it can fit into /system when flashed.
Nano gapps package is recommended as it fits and provides everything in a base package you will need for gapps support. Then, you can install the other google apps from the store later on if needed.
Remember nightly builds are experimental: they can and will be broken from time to time. Always have a backup at hand.
To transfer files from/to PC when plugged in you will get the charging mode prompt status in the status bar, then click it to change from charging mode to transfer files.
Considering the quite low amount of Falcon users left over here, I'm not sure about making a full-sized FAQ;
For now, the following will take that purpose:
[SIZE=+1]Q1: Where are themes/tiles/whatever gone?[/SIZE]CM14.1 I still at early stage of public development, you should expect to face bugs, missing features, regressions, and other things closely related to WIP. Do not complain about it (even less if someone already discussed it in the thread)
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: Why does swipe to write feature doesn't work although it is enabled? [/SIZE]There is a fix for that "known" issue: see here.
[SIZE=+1]Q35: [?][/SIZE][...]
[SIZE=+1]Q35: [?][/SIZE][...]
reserved
i will try it and will post the results.
Just downloaded the ROM and Pico GApps.
I'm running CM14.1 unofficial before. I'll do the Clean Install anyway.
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Edit: Pressing on "Skip" when I am being asked for my Google Account sends me back to the "Use Mobile Data" screen.
Edit 2: I can receive calls and messages, but can't send a message or call someone myself.
Click to expand...
Click to collapse
working fine on my xt1033 both sims are working, sms are also working didnt try the call yet
legendavey said:
Dual sim works, internet (I use 2G) works and none of the bugs* of the unofficial version.
Don't do a dirty update or a clean update mentioned in the OP.
Just do a clean flash - wipe everything, including data. Worth the extra effort.
*Edit: except the occasional extra swipe up on the lock screen. I've heard abyss kernel fixes this, but I like the stock kernel so not flashing it myself. :angel:
Click to expand...
Click to collapse
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
cooldude5500 said:
Lovely, thanks. Unfortunately the ROM does not seem to pick up my SIM card. Using XT1033. I'll be waiting for a later build.
Click to expand...
Click to collapse
same,sim card not getting detected
edit:reflashed it and both sims are getting detected
Can we disable second sim if we want in this latest nightly of 14.1.
Because I need sim disable feature.
drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
yes
drwierdo said:
Does the home button long press show recents instead of assistant like with the unofficial 14.1?
Click to expand...
Click to collapse
Yes, this was fixed a while ago and it is working in this build, head to Settings > Buttons > Configure your home button action(s).
This is build is very stable and the multitasking is unbelievable. Totally worth it!
Hiraethic said:
yes
Click to expand...
Click to collapse
You can change that in buttons option
matmutant said:
as of CM14.1-20161109
I performed the "clean update" I had wrote before, (before it I reverted to stock theme.)
Install script complained about not being able to "log" the install which is expected as TWRP 3.0 wasn't supposed to support 7.1 logging feature on install.
Code:
E:unknown command [log]
Micro gapps was too big, so I used nano instead.
First boot attempt never went to home; a force reboot made it work.
First full boot was awfully laggy and many apps forced close after the mini setup-wizard (as I didn't wiped data, the wizard only asked for language and wifi), I let it set a few minutes and then reboot it.
Now the UI is really fluid and works perfectly
Some tiles in the quick access menu are missing (you can't add them I mean, or I didn't see them)
I will update in next posts if I encounter interesting things in the next few days.
Click to expand...
Click to collapse
We really appreciate the work you do (in your free time) for our beloved Moto G. I know you guys worked really hard for this to happen, I've been checking the CyanogenMod Gerrit for a while now.
P.S.: I was in no way trying to dissuade anyone from using the dirty update or clean update methods. In my experience, a clean flash is always the most stable in the long run.
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Hiraethic said:
battery icon options circle and landscape mode doesnt work.
Newer builds will hopefully be free of these
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
the reason why my sims were not gettting detected was i flashed supersu 2.78.
Click to expand...
Click to collapse
SuperSU over CyanogenMOD should have caused a bootlop, you were lucky.
running 20161109.
* Dual SIM works fine
*Music app is not opening. Showing me that the app is stopped (Is it just me?)
Long press Home button brings Google Assistant after configuring with Buttons settings. (I tweaked build.prop for bringing up Google Assistant)
Battery percentage is showing only on Icon Portrait. None of other icons are working.
It's been 7 hours since I flashed it. The SoT is not that bad.
May be I'll flash abyss kernel later to check if the battery life will be improved and the swipe is definitely working very well on abyss kernel.
{
"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"
}
Disclaimer:
Code:
/*
* Your 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. Hard. A lot.
*/
About ROM:
This is Experiemental Build of Android 8.0 Oreo for Sony Xperia Z (C6602, C6603), Based on LineageOS.
Thanks To:
Mardon
What's working:
* ROM is experiemental and is not recommended for daily usage *
* Now we have working Audio *
I have not tested whole rom but everything works fine except:
- Flashlight and Camera
- Adaptive Brightness
Please report any bugs in the comments below!
(Special) Install Instructions for Newbies:
Warning: If you flash ROM first time do it at your own risk, You may brick device.
Before resuming remember these things:
- You can't restore TA codes on a custom ROM, TA codes only work on Stock ROMs, So if you ever reflash Stock ROM you can restore them.
- If you're Windows 8/8.1 or 10 User this Tutorial may not work for you as long as you've done This Tutorial
- Read everything Carefully, I wish you Good Luck
1.0 - Backing up TA Codes
- First you need an unlocked bootloader, But before unlocking it you have to backup DRM keys (Optional)
- Download KingoRoot, Root your device with One-Click-Root and then Download Backup-TA Program from Here
1.1 - Unlock Bootloader
- After you've done that, Unlock your bootloader from Here
1.2 - Preparing Drivers
- After you unlock your bootloader Install Sony Flashtool from Here
- Go to Flashtool Folder then go Drivers folder and select Flashtool-drivers.exe
Check the Fastboot and Flashmode drivers then Scrool down and find Xperia Z SO-02E drivers, Check it and Install them.
1.3 - Installing ADB
- Now it's time to download ADB 15 Seconds Installer from Here
Follow the instructions in the program and Install ADB/Fastboot drivers, then locate "C:/adb" folder and open it.
- Download Latest TWRP 3.1.1 from Here and move into adb folder located in "C:/adb"
- Rename TWRP 3.1.1 file to twrp (If your file extensions are shown twrp.img)
- As long as you can't flash TWRP directly as Recovery you must flash it as boot, Your ROM won't start again so back up everything before restarting to ADB!
- After you back up everything just enable USB debugging in your phone (go Settings/About and press Build Number couple times)
- Press Back button and go to Developer Settings and find USB Debugging, Enable it.
- Now go to "C:/adb" and press and hold SHIFT, Then press RMB (Right Mouse Button) and press open command window here.
- Congratulations! Now you're in adb.
1.4 - Flashing TWRP
- Write next ADB Commands:
adb devices (so you will check your device is detected by ADB or not, If adb shows any number row and then DEVICE its okay, If it doesn't then just write):
adb reboot bootloader (Look at your phone and give permissions of USB Debugging to PC, If phone reboots it means you've done everything correctly, If it doesn't then you did something wrong!)
- Well if the phone rebooted you will see blue led in the top of your phone, That means you're in a bootloader!
Write next commands:
fastboot devices (And check your device is detected by fastboot or not, same thing it will show number row and then FASTBOOT, So you did everything correctly, If it doesn't check your installed drivers, You may have little update from Device Manager so comment down below, If drivers are installed wrong and you don't see device number and FASTBOOT just restart phone and wait for the answer in the comments)
- If you see your device number and FASTBOOT enter next commands:
fastboot flash boot twrp.img
- After you've done that and you see that it has flashed without any Errors write next command:
fastboot reboot
- Now you're in TWRP recovery, Congratulations !!
1.5 - CleanFlashing ROM
- If you backed up everything just see if your computer detects your phone's MTP (media file transfer)
Go to My Computer/Xperia Z and see is there Internal Storage or not
- If There is any Storage that's good so make a Fully Clean Install
- Go back in the main menu of TWRP press Wipe, Advanced Wipe and check: Data, Cache, Dalvik Cache, System and Internal Storage, Then swipe to wipe.
- After you wiped your phone go back to the main menu of TWRP, Enter your internal storage folder from your PC and move ROM, Gapps and Rootkit in there.
- After that Press Install, You'll see lineageos, gapps and rootkit in the TWRP so press lineageos file and swipe to flash.
- Then go back (Don't Reboot) and press gapps file, flash it as you flashed lineageos.
- Go back again and flash Rootkit but when it's finished just press wipe dalvik cache and swipe to wipe it!
- After you've done that press Reboot phone.
- Congratulations!! Wait for 10 minute to boot and enjoy your new Android 8.0.0 Oreo!
1.0-2 - Troubleshooting
- If you want to install any other Custom ROMs just resume this tutorial from ADB (adb reboot bootloader) And do the same.
- If ROM doesn't boot up that means you did something incorrectly, So you have to do next steps:
Long Press Power Button and Volume UP, After it vibrates it will vibrate three more times and then release so your phone will shut down.
Get your USB Cable which's connected to PC and hold Volume UP, then connect USB Cable into phone
- You're in a fastboot, resume tutorial from (fastboot flash boot twrp.img)
- If you flashed ROM again and still doesn't work change your gapps version and download gApps-Pico
- Then it will work 100%, Or you can flash LineageOS14.1 and wait for Stable Oreo build.
- Thank you for attention, do it at your own risk and good luck
Downloads:
MOD EDIT: Download link removed.
Download the gApps (ARM, 8.0, Pico)
Download Rootkit if you want (I've tested Magisk and works fine)
- Links updated & No more error7 in TWRP
Short Install Instructions:
Move the ROM/GAPPS/ROOTKIT on your SDCARD
Flash latest TWRP (If you have old version already reflash it using flash image)
Wipe Cache, Data, Dalvik cache and System
Flash ROM
Flash gApps
Flash Rootkit
Wipe dalvik cache
Reboot!
- First boot may take some time for optimizing apps, bootanimation may have a little lag, be patient and wait.
ROM Information:
ROM Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information:
Status: Experiemental
If you like the ROM please hit that Thanks button and give some support
Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3
#iLiKo said:
Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3
Click to expand...
Click to collapse
omg I can't believe this @@
thank you so much for your awesome work ^^
with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?
404 not found
Can't find it!
If you are seeing this error page then the file in question has been deleted from the site and servers. Please contact the developer/uploader for a new link to the file.
cyparisss1 said:
with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?
Click to expand...
Click to collapse
Not TWRP problem at all, don't delete rom because mby link got broken, ill help you to fix tommorow, update-script must be changed
Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Link of old version:
MOD EDIT: Removed download link
not happen
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?
cyparisss1 said:
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?
Click to expand...
Click to collapse
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..
#iLiKo said:
Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Click to expand...
Click to collapse
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.
I am using custom rom and my device model is Xperia Z , it is possible to not verify my phone like c6603 and then the installation fails. See on the screen shots
#iLiKo said:
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..
Click to expand...
Click to collapse
welcome my friend, MOD EDIT: Removed download link
NamenIos said:
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.
Click to expand...
Click to collapse
ill explain u smth this rom is shared and doesnt require any rights to post on websites, also people must have single oreo rom for this phone to try how its like, plus i made whole tutorial of newbies now i think they wont get in problems, also everyone knowns that this is experimental testbuild, but LOSTEAM still want to share only stable.. i think differently, i think people can see how oreo really is, whats the differences and etc.. by themselves. stop it, im not gonna delete rom again.
cyparisss1 said:
welcome my friend, MOD EDIT: Removed download link
Click to expand...
Click to collapse
new link: MOD EDIT: Removed download link
Bug
Camera not working
Lag ui (recent app)
Error 7 script delete assert line
mohammadnadimi48 said:
Camera not working
Lag ui (recent app)
Error 7 script delete assert line
Click to expand...
Click to collapse
Error 7 has been fixed i think so.
Use new link
Thread closed.
#iLiKo said:
ill explain u smth this rom is shared
Click to expand...
Click to collapse
Yes, you are right here - LineageOS can be built from source.
#iLiKo said:
doesnt require any rights to post on websites
Click to expand...
Click to collapse
Not quite correct - you still need to stick to the XDA rules (see rule 12).
You need to accept the fact that the developers of the ROM don't want to release half-baked builds or unfinished work (even if it's open source). Don't we all want a stable daily driver after all?
Thread closed.
{
"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.
{
"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 GAppsFULL 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 Installation1. 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
{
"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:
Wifi
Bluetooth
Audio
LED
USB
RIL
Encryption
Fingerprint
Camera
Hall sensor
DT2W
Selinux Enforcing
Broken
nothing
Source code:
device: https://github.com/lenovo-devs/android_device_lenovo_TBX704
device-common: https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
Important
If you are using this ROM first time, wipe data. Wipe data completely. I mean the option where you need to enter "yes". Use this option and then flash the rom.
This ROM only works with the TWRP I added.
If you want to use GAPPS, flash it directly after flashing ROM. Don't let the ROM boot. Otherwise your device will not get certification, so you will not have Google Access.
Instructions (thx @matshias, just changed few lines to get ROM flashing working)
Put your ROM (and GApps) onto your sdcard (sdcard must be exfat or fat32, NTFS not supported)
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Format data using this tutorial
Flash ROM
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Restart
Download
2019-08-12 (hotfix)
• hotfix: fix camera
• security patch level: 2019-08-01
ROM
TWRP (Use this for TB704L too; you guys don't need 4g in recovery )
You can also get the latest ROM updates from codeworkx here:
https://sourceforge.net/projects/lineageos-on-lenovo/files/16.0/TBX704/
Bulids are same, just update.
Older downloads
2019-07-14
• security patch level: 2019-07-05
ROM
TWRP
2019-06-22 (thx @codeworkx)
• bugfixes and performance improvements
• fix camera detection for ov8856 sensor
ROM
2019-06-09 (thx @codeworkx)
• bugfixes and performance improvements
• set_permissive.zip patch no more required
• TWRP 3.3.0 support
• security patch level: 2019-06-05
ROM
2019-05-14
• fixed sim issue for x704l caused in last update
• fixed a little issue on x704l (should improve battery life)
• added double tap to wake
• latest changes of LineageOS
ROM
2019-05-10
• fixed wifi after fresh installation
• changed scheduler to bfq
• added wireless display broadcast
• improved performance
• removed ril elements from X704F variant
• security patch level: 2019-05-05
ROM
SIM fix for X704L
2019-04-30
• fixed fingerprint bug caused by SELinux
• removed PS3/PS4 controller hid, as it doesn't work
• optimized performance
ROM
2019-04-28
• fixed notifcation led (light was only red for notifications)
• fixed ril values
• added support for PS3/PS4 controller
• SELinux is enforced after boot
ROM
2019-04-24
• fixed hall sensor
• fixed camera
• fixed long time to wake up screen
ROM
2019-04-22
• fixed fingerprint removement after reboot/user switch
• fixed partially camera (same like in 15.1)
• fixed reboot to recovery and bootloader for advanced reboot menu
• fixed long time to wake up screen
• fixed deep sleep
ROM
2019-04-21
• intital release
• TB-X704L is now integrated, no more additional zip required
• You can update from previous version
ROM
Optional downloads
Dolby Digital Plus (use the TWRP one)
GAPPS (use 9.0 arm64; I suggest using pico variant)
Mounting system rw
This is impossible on our tablet. The bootloader enforces verity check, which causes this issue.
The only possibility is to modify bootloader, what is dangerous and requires good knowledge.
there is a workaround using magisk with a mod. which mounts your system rw on mount:
https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259
Thanks
@highwaystar_ru (he gave me the important hint, also used his sources and his thread )
@LumenReaper (for his work with CM14.1, where I took big part of his device tree :fingers-crossed
@Flowah123 for the TB-X704L files :fingers-crossed:
Donations
Thanks to @rorzer, @Preyer11, @Tschumi, @MrMagic, @max_work, @vicenza & 5 x anonymous
Please don't support Lenovo and buy their tablets
Code:
[I]Updates vary depending on the model where our tablets receive Android and security updates after the introduction.
We announced Tab 4 10 Plus in February 2017 and since then it has received seven OTA updates.
However, this model has reached the end of its update cycle and will not receive any more updates in the future.
- Lenovo (2018-05-11)[/I]
Just seven updates and not even one major upgrade, please don't support them.
Reporting bugs
Please tell what mods you are using and what tablet variant (TB-X704F or L or ABCDEFGH..)
If your tablet doesnt start:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files and upload it here.
if your tablet starts and bug appears later:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files
start your tablet normal, let the bug appear, enter adb root
use adb logcat and adb shell dmesg, copy the content to a text file and upload here
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus, ROM for the Lenovo Thinkpad Tablet
Contributors
yener90, codeworkx
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Created 2019-04-21
Last Updated 2019-06-11
Yener, you're amazing. Thanks to you we are on the current Android version. Installation ran without problems. I was so free to attach some screenshots.
What I noticed so far:
- I can confirm the list of things that are working and things that are broken.
- Significantly newer kernel (3.18.138) than LineageOS 15.1 (3.18.115) and of course Nougat (3.18.31).
- Magisk 18.1 works fine (had problems with it under LOS 15.1)
- Waking up the device by pressing the power button or using the fingerprint sensor takes an unusually long time (3-4 seconds). I caught myself several times pressing the button again.
Will you offer a new TWRP 3.3.0?
LumenReaper said:
- Waking up the device by pressing the power button or using the fingerprint sensor takes an unusually long time (3-4 seconds). I caught myself several times pressing the button again.
Click to expand...
Click to collapse
Wiil be fixed tomorrow release. It has the same bugs like the little older brother:
Fixed reboot to recovery and bootloader from reboot menu
Fixed long time to wake up screen
Fixed Deep sleep
Also there is an issue with fingerprint. After restart it doesn't work anymore. This will be also fixed.
LumenReaper said:
- The release is an engineering build. @yener90 isn't it common to release userdebug?
Click to expand...
Click to collapse
Everything is normal, I don't know, why it is like that
LumenReaper said:
Will you offer a new TWRP 3.3.0?
Click to expand...
Click to collapse
I'm not planning to change something on TWRP currently.
yener90 said:
Wiil be fixed tomorrow release. It has the same bugs like the little older brother:
Fixed reboot to recovery and bootloader from reboot menu
Fixed long time to wake up screen
Fixed Deep sleep
Also there is an issue with fingerprint. After restart it doesn't work anymore. This will be also fixed.
Click to expand...
Click to collapse
Okay, thank you very much. I can also confirm the problem with the fingerprint scanner, it occurs not only after a reboot, but also when you switch between two users.
yener90 said:
Everything is normal, I don't know, why it is like that
Click to expand...
Click to collapse
Maybe I can help here: You will get an engineering build if you run lunch lineage_TBX704-eng. If you run lunch lineage_TBX704-userdebug instead, you will get a userdebug build.
LumenReaper said:
Okay, thank you very much. I can also confirm the problem with the fingerprint scanner, it occurs not only after a reboot, but also when you switch between two users.
Click to expand...
Click to collapse
Same bug, will be also fixed.
LumenReaper said:
Maybe I can help here: You will get an engineering build if you run lunch lineage_TBX704-eng. If you run lunch lineage_TBX704-userdebug instead, you will get a userdebug build.
Click to expand...
Click to collapse
I didn't change anything How do you come to this conclusion? in Device Info HW App its listed as userdebug build
yener90 said:
I didn't change anything How do you come to this conclusion? in Device Info HW App its listed as userdebug build
Click to expand...
Click to collapse
Forget it, my mistake. I should read more carefully.
Update
2019-04-22
• fixed fingerprint removement after reboot/user switch
• fixed partially camera (same like in 15.1)
• fixed reboot to recovery and bootloader for advanced reboot menu
• fixed long time to wake up screen
• fixed deep sleep
ROM
I'm impressed!
Nice update @yener90, thank you very much.
Now, here's a good one, dirty flashed the V9 over your V8 and then flashed Gapps and Magisk19.
All went well and I was impressed with how well the tablet ran and its stability, a few apps needed updating and then I used the tablet for about 2 hours or so, no problems whatsoever.
So I did a backup and rebooted, now the tablet powers off after approx 30secs. or so displaying the 'powering off' notification but instead of actually powering off it reboots to TWRP.
I have wiped Dalvik and cache but to no avail.
I used your TWRP to flash the ROM and use the original TWRP to create the backups/restorations to/from Ext SD . TB-X704V (L)
Any ideas please, as it was running very well prior to doing a backup ?
TIA.
thanks yener
flashed it 5min ago and looking for something not working but so far, it runs nice
Sparkrite said:
Nice update @yener90, thank you very much.
Now, here's a good one, dirty flashed the V9 over your V8 and then flashed Gapps and Magisk19.
All went well and I was impressed with how well the tablet ran and its stability, a few apps needed updating and then I used the tablet for about 2 hours or so, no problems whatsoever.
So I did a backup and rebooted, now the tablet powers off after approx 30secs. or so displaying the 'powering off' notification but instead of actually powering off it reboots to TWRP.
I have wiped Dalvik and cache but to no avail.
I used your TWRP to flash the ROM and use the original TWRP to create the backups/restorations to/from Ext SD . TB-X704V (L)
Any ideas please, as it was running very well prior to doing a backup ?
TIA.
Click to expand...
Click to collapse
I'm suprised that it even starts. I really don't know. Maybe encryption got broken or filesystem error.
yener90 said:
I'm suprised that it even starts. I really don't know. Maybe encryption got broken or filesystem error.
Click to expand...
Click to collapse
Why are you surprised, I understood you had incorporated the 'L' fix into the ROM ?
It's doing my head in, it was running well, had rebooted a few times, intentionally, and all was well.
Make a backup and then the problem appears and I don't have time to do much before it re-boots, unfortunately.
Sparkrite said:
Why are you surprised, I understood you had incorporated the 'L' fix into the ROM ?
Click to expand...
Click to collapse
For me it looks like TWRP made some rubbish, which lead to failure on partition.
Normally you would end up in a bootloop. The system wouldn't start.
Use my TWRP then use in TWRP internal file manager.
Go to the location sys/fs/pstore and upload the files here.
Preyer11 said:
thanks yener
flashed it 5min ago and looking for something not working but so far, it runs nice
Click to expand...
Click to collapse
Does SIM work for you? On this release I tried to get it work on wifi and lte variant of tablet.
yener90 said:
Does SIM work for you? On this release I tried to get it work on wifi and lte variant of tablet.
Click to expand...
Click to collapse
sadly not,
i see all the settings in software (grey out) and it keeps asking for a Sim Card but none of my 3 Sim Cards avaible is noticed
could somebody that also use the L confirm this ? not that i am sitting on a broken sim card slot
Preyer11 said:
sadly not,
i see all the settings in software (grey out) and it keeps asking for a Sim Card but none of my 3 Sim Cards avaible is noticed
could somebody that also use the L confirm this ? not that i am sitting on a broken sim card slot
Click to expand...
Click to collapse
Its not broken. There is something wrong.
I need to compare both kernels X704F & X704L and check that issue out.
Hey, just wanted to report i also dirty flashed and it worked without problems, i own the F model. Works great so far, awesome! However i have one little bug (i guess it is one): long pressing an app icon to move it does sometimes not work, nothing happens then. but i have this since the 15.1 version. does anyone also have this?
kind regards
I dirty flashed it over lineage 15, after wiping system and caches. I flashed the gapps after the rom and everything works perfectly so far. No bugs yet or problems with apps and files. Thanks Yener, I had lost all hope of ever seeing this device updated.
hi @Yerner90 installed ROM using the format data method (ie wiped everything), so far everything is working good so thanks again for ROM
@yener90 great job, works a treat and you've fixed the led colours and added screenshot back on. I'm keeping an eye on the battery as it's draining much quicker I think.