{
"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 10, 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. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki https://wiki.lineageos.org/devices/gta4xlwifi
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Warning: 17.1 is now discontinued, use 18.1 instead
Builds: https://download.lineageos.org/gta4xlwifi
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS
reserved
reserved
Congrats @Linux4 , you're "official" Lineage maintainer for GT4XLWIFI now.
any plans the lte edition, it really is sad people dont make anything for this version I don't actually care for the lte I just happened to have bought it second hand. EDIT: nevermind just saw the actual version
Works great for me!
For anyone interested: Netflix and Nanolx microG patcher do not work out-of-the-box.
Edit: Netflix does work after using MagiskHide Props and selecting the Galaxy Tab S5e Fingerprint, clearing the Playstore Cache and activating Magisk Hide for Netflix.
Well done, switching asap!
Edit: can this version be dirty flashed over the unofficial one?
SvenHee said:
Well done, switching asap!
Edit: can this version be dirty flashed over the unofficial one?
Click to expand...
Click to collapse
No, I'm sorry, you can't dirty flash official over unofficial, there are two reasons for this:
1. It's signed with other keys (lineage ones)
2. It has FBE enabled like my unofficial 18.1 has, while unoffcial 17.1 had FBE disabled
Ok, thanks for the quick reply. Will clean flash
OK, I have followed the directions on the LineagOS Wiki, got the bootloader unlocked, went into the system again, got onto the WiFi, verified that Allow OEM Unlock was greyed out in the on position. I then flashed the LineageOS Recovery in ODIN and booted into it, then did a Factory Reset/Wipe Data and then used adb sideload to install the latest nightly and ARM64 Stock OpenGAPPs and then reboot, I am then stuck on the boot screen for LineageOS. Any ideas on what I need to do?
bose301s said:
OK, I have followed the directions on the LineagOS Wiki, got the bootloader unlocked, went into the system again, got onto the WiFi, verified that Allow OEM Unlock was greyed out in the on position. I then flashed the LineageOS Recovery in ODIN and booted into it, then did a Factory Reset/Wipe Data and then used adb sideload to install the latest nightly and ARM64 Stock OpenGAPPs and then reboot, I am then stuck on the boot screen for LineageOS. Any ideas on what I need to do?
Click to expand...
Click to collapse
Have you taken the correct gapps version, for Android 10???
First lineage flashing, then rebooting and then gapps flashing, the first time
mu1989 said:
Have you taken the correct gapps version, for Android 10???
First lineage flashing, then rebooting and then gapps flashing, the first time
Click to expand...
Click to collapse
I tried the slightly smaller step down GAPPS and it worked fine, must be something with that package or something.
Thank you Linux4. I love LineagOS.
I have an Installation generic Problem for this device.
SM-P610 flash --> Only official released binaries are allowed to be flashed(RECOVERY)
Hello, I cannot install TWRP either LineagOS on my new GALAXY TAB S6 Lite WIFI Here is my example with TWRP (same with LineagOS) Device Info : download mode: Product Name SM-P610 (SAMSUNG TAB S6 LITE) Current Binary : Samsung Official...
forum.xda-developers.com
I you have any Idea...Perhaps you already had this...
Thank you for your job.
Best Regards.
I tried installing the update 0601 yesterday and that went wrong, kept booting to twrp.
I did a factory reset an installed the same version again but it seems to be throwing all kinds of problems.
At first some but not all apps would not start.
I factory-reset again and installed agian.
Now apps do start but not all apps reinstalled from the google backup.
I now want to install autodesk sketchbook but I get a message to place an sd card, which in fact is present and can be read.
I just now looked at what is available in the internal storage but that seems litterally all to be mangled, even though the apps I could install all seem to work.
Not a single recognizable folder present.
Did I omit anything with wipe/factoryreset?
SvenHee said:
I tried installing the update 0601 yesterday and that went wrong, kept booting to twrp.
I did a factory reset an installed the same version again but it seems to be throwing all kinds of problems.
At first some but not all apps would not start.
I factory-reset again and installed agian.
Now apps do start but not all apps reinstalled from the google backup.
I now want to install autodesk sketchbook but I get a message to place an sd card, which in fact is present and can be read.
I just now looked at what is available in the internal storage but that seems litterally all to be mangled, even though the apps I could install all seem to work.
Not a single recognizable folder present.
Did I omit anything with wipe/factoryreset?
Click to expand...
Click to collapse
Please just stick to lineage recovery,
I'm almost sure all of these are being caused by TWRP.
Probably the reboot to twrp thing was even caused by TWRP messing with FBE again ... Did it show "Android Rescue Party Trigger" maybe ?
Linux4 said:
Please just stick to lineage recovery,
Click to expand...
Click to collapse
Thanks for the quick reply!
Is this a general lineage twrp thing, or specific to the s6-L?
I had read the guide saying to install lineage recovery but not to only use it.
Will give it a go later today.
SvenHee said:
Thanks for the quick reply!
Is this a general lineage twrp thing, or specific to the s6-L?
I had read the guide saying to install lineage recovery but not to only use it.
Will give it a go later today.
Click to expand...
Click to collapse
It should be a general problem on every device running a ROM with FBE enabled but decryption not working in TWRP
Actually you can use twrp as long as you don't touch /data (wipe and such things) but looks like OTAs through twrp don't work too..
Or did your gapps addon.d maybe not run after the OTA? That would effectively have gapps uninstalled and might cause a reboot to recovery too
Linux4 said:
It should be a general problem on every device running a ROM with FBE enabled but decryption not working in TWRP
Actually you can use twrp as long as you don't touch /data (wipe and such things) but looks like OTAs through twrp don't work too..
Or did your gapps addon.d maybe not run after the OTA? That would effectively have gapps uninstalled and might cause a reboot to recovery too
Click to expand...
Click to collapse
I had the same problem with an installation with Heimdall. After that I have installed the version 1230 without problem
dgo65 said:
Thank you Linux4. I love LineagOS.
I have an Installation generic Problem for this device.
SM-P610 flash --> Only official released binaries are allowed to be flashed(RECOVERY)
Hello, I cannot install TWRP either LineagOS on my new GALAXY TAB S6 Lite WIFI Here is my example with TWRP (same with LineagOS) Device Info : download mode: Product Name SM-P610 (SAMSUNG TAB S6 LITE) Current Binary : Samsung Official...
forum.xda-developers.com
I you have any Idea...Perhaps you already had this...
Thank you for your job.
Best Regards.
Click to expand...
Click to collapse
At the end I found the solution. After the "Preparing for installation" process I had to follow this procedure.
Fix Missing OEM Unlock Toggle on Samsung Galaxy Devices (Guide)
Are you facing the missing OEM unlock issue on your Samsung Galaxy device? That's because your phone has entered the Prenormal RMM/KG state. However, if you'd like to bypass it, then you can follow…
www.thecustomdroid.com
Before to follow with the installation.
Only if anybody as the same problem.
Any ideas how to enable MIDI over USB in this ROM?
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"
}
Pixel Experience for Lenovo Tab 4 8 Plus (TB8704F/X/N)
What is this?
Pixel Experience is an AOSP/CAF 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
What's working?Wifi
Mobile data
GPS
Camera (both photo, video, and also flashlight working)
Bluetooth
FMRadio
Sound / vibration
Facelock
Known issues
Fingerprint scanner not detected; no option to set up in Settings
November 2019 security patch
Android 9.0 Pie
ROM download
Don't flash GAPPS, they are already included
Download latest build here
XDA:DevDB Information
PixelExperience, ROM for the Lenovo Thinkpad Tablet
Contributors
ChasTech
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Created 2019-11-21
Last Updated 2019-11-22
Installation:
Make sure you are running stock Lenovo firmware and not another custom ROM like LineageOS. If you aren't running stock Lenovo firmware, restore to it using Lenovo Moto Smart Assistant and allow for the first boot to complete. If you are already running it, factory reset it then allow for the 'first boot' to complete.
Boot TWRP into RAM through the following command:
HTML:
fastboot boot twrpfilename.img
and backup recovery image to USB OTG or microSD card. Then flash the TWRP image to recovery using TWRP (ADB push it to internal storage them use install image to flash it).
Install ROM from external storage or ADB sideload then boot into system.
Quickly set it up, then reboot into TWRP, restore recovery backup from external storage, then reboot into system.
Factory reset in System Settings. After this you may flash TWRP back again.
Pixel Experience should now be installed and stable on your device. Enjoy!
Building from source
Create working directory, initialise Pixel Experience repo and download sources:
HTML:
mkdir WORKING_DIRECTORY
cd WORKING_DIRECTORY
repo init -u https://github.com/PixelExperience/manifest -b pie
repo sync
Go out and have lunch somewhere or go on a big shopping trip whilst waiting for the sources to download. This will take some time.
Once they've finished downloading, you cannot just lunch and build as the Tab4 8 Plus is not officially supported with Pixel Experience. You must download the device tree, kernel, and vendor files first. Do so with the following commands:
HTML:
git clone https://github.com/ChasTechProjects/android_device_lenovo_TB8704 -b aosp-9.0 device/lenovo/TB8704
git clone https://github.com/ChasTechProjects/android_device_lenovo_tb-common -b aosp-9.0 device/lenovo/tb-common
git clone https://github.com/lenovo-devs/android_kernel_lenovo_msm8953 -b lineage-16.0 kernel/lenovo/msm8953
git clone https://github.com/lenovo-devs/proprietary_vendor_lenovo -b lineage-16.0 vendor/lenovo
For Pixel Experience, you must add the following line to device/Lenovo/TB8704/aosp_TB8704.mk, or else it will not lunch successfully:
HTML:
TARGET_GAPPS_ARCH=arm64
Now, time to build!
HTML:
source build/envsetup.sh
lunch aosp_TB8704-userdebug
brunch aosp_TB8704-userdebug
The ROM installation zip should be in the folder out/target/product/TB8704. Install it by following the instructions in the above reply. Please note that if you already have Pixel Experience installed on your device all you have to do is flash your build on top of the existing build and it should work.
Hi can you explain how you boot twrp into ram. Sorry I'm a bit of a noob. Would like to try the rom
andyskelly said:
Hi can you explain how you boot twrp into ram. Sorry I'm a bit of a noob. Would like to try the rom
Click to expand...
Click to collapse
HTML:
fastboot boot twrpfilename.img
Replace twrpfilename.img with the TWRP image file name.
You'll need fastboot installed on your PC and your device booted into the bootloader for this.
Hi. Installed the ROM as your instructions. Seems to work really well. Thanks for your work.
Well worth installing.
andyskelly said:
Hi. Installed the ROM as your instructions. Seems to work really well. Thanks for your work.
Well worth installing.
Click to expand...
Click to collapse
Fingerprint is working?
mujju85 said:
Fingerprint is working?
Click to expand...
Click to collapse
No, I'm not sure why because it works on LineageOS 16 which has the same device tree, kernel, and proprietary vendor files as Pixel Experience.
The fingerprint scanner is the only thing that doesn't work.
andyskelly said:
Hi. Installed the ROM as your instructions. Seems to work really well. Thanks for your work.
Well worth installing.
Click to expand...
Click to collapse
I do not own this device (yet) and am still waiting for the 8704x to arrive. I will try this once I have the device-in the meantime can anyone comment on whether this ROM or the lineage 16 have any echo effect for the receiver/person at the other end hearing their own voice for a phone call made through/with this device? This has been an issue on Samsung tablet phone devices (something to do with mic feedback/gains as tablets maybe have a different arrangement of speaker and mic) (somehow stock on Samsung tabs never had the issue but all aosp/lineage ROMs had this issue-have no experience with non-Samsung android tabs that have calling capability and with lineage/aosp/cm)
thanks..anyone
Nice work, just setting up and installing apps.
One thing though and I'm not sure it's related to the rom or not - but trying to download netflix - it's says this tablet not supported?
I had this issue when also installing stock rom 8.1 - lenovo were next to useless with their support!
So anyone got a workaround?
The tb8704v version of Lenovo 8 4 plus is not mentioned. Does this ROM work for "V"?
oobatz said:
Nice work, just setting up and installing apps.
One thing though and I'm not sure it's related to the rom or not - but trying to download netflix - it's says this tablet not supported?
I had this issue when also installing stock rom 8.1 - lenovo were next to useless with their support!
So anyone got a workaround?
Click to expand...
Click to collapse
Sideload the APK?
scott.e said:
The tb8704v version of Lenovo 8 4 plus is not mentioned. Does this ROM work for "V"?
Click to expand...
Click to collapse
Not sure, worth a shot though.
I have the tb8704v rooted and TWRP 3.3.1-0 installed on my tb8704v, I can do a factory reset from TWRP. This shortens the procedure you outlined and does not require a PC. Or should I go through the recommended procedure using the Lenovo app on my PC? Also, does Magisk need to be installed to run Netflix and other programs that will not work with a rooted device?
scott.e said:
I have the tb8704v rooted and TWRP 3.3.1-0 installed on my tb8704v, I can do a factory reset from TWRP. This shortens the procedure you outlined and does not require a PC. Or should I go through the recommended procedure using the Lenovo app on my PC? Also, does Magisk need to be installed to run Netflix and other programs that will not work with a rooted device?
Click to expand...
Click to collapse
Follow my procedure, not sure if TWRP works.
Magisk Hide is required for apps with root detection even if not using root as long as the bootloader is unlocked.
Does USB OTG work with this rom?
I' ve never managed to flash lineage rom, i was always stuck on boot logo. I' m on twrp 3.2.3 and i don't have stock to flash first. Do i have any chances with your rom?
gzdc said:
I' ve never managed to flash lineage rom, i was always stuck on boot logo. I' m on twrp 3.2.3 and i don't have stock to flash first. Do i have any chances with your rom?
Click to expand...
Click to collapse
You need to follow the install instructions on the first page of the Pixel Experience ROM thread. These instructions also work for LineageOS 16.0, just use the lineage zip instead. You don't need to have a TWRP backup of the stock ROM, you just need access to a Windows PC with Lenovo Moto Smart Assistant installed.
Doing a clean flash of either ROM without stock 7.1/8.1 installed first will result in being stuck on the Lineage logo.
ChasTech said:
You need to follow the install instructions on the first page of the Pixel Experience ROM thread. These instructions also work for LineageOS 16.0, just use the lineage zip instead. You don't need to have a TWRP backup of the stock ROM, you just need access to a Windows PC with Lenovo Moto Smart Assistant installed.
Doing a clean flash of either ROM without stock 7.1/8.1 installed first will result in being stuck on the Lineage logo.
Click to expand...
Click to collapse
no need for lineage rom this rom is awesome, thanks again DEV
{
"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
WLAN and USB tethering
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8504, https://github.com/lenovo-devs/android_device_lenovo_tb-common/tree/lineage-16.0-msm8937
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo/tree/lineage-16.0-msm8937
2020-03-19
Fixed USB flash mounting when using OTG
mailru: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200319-UNOFFICIAL-TB8504.zip
Previous versions:
2020-03-13
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
mailru: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200313-UNOFFICIAL-TB8504.zip
2020-03-04
first release
mailru: lineage-16.0-20200304-UNOFFICIAL-TB8504.zip
gdrive: lineage-16.0-20200304-UNOFFICIAL-TB8504.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 or one from link below
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
TWRP
Built from omnirom android 9.0 source (twrp 3.3.1), includes same kernel as Lineage build, with support for pstore (kernel logs after crash), exfat, ntfs, reboot to EDL mode.
mailru: twrp-3.3.1-1-TB8504.img
gdrive: twrp-3.3.1-1-TB8504.img
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8504f/x] LineageOS 16.0 for Lenovo TAB4 8, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-tb8504
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2020-03-04
Last Updated 2020-03-19
hero - thank you
Can this be installed on my 8704v?
jcthrower said:
Can this be installed on my 8704v?
Click to expand...
Click to collapse
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
highwaystar_ru said:
No, it is only for 8504, it has different SOC.
Update here
Fixed graphical issues
Fixed USB modem mode
Selinux now enforcing
Click to expand...
Click to collapse
ok thanks for the response. Are you still planning on updating Lineage 16.1 for the 8704v?
Thank you so much for that rom, I'll be trying to flash it next week!
I have question - is there any possibility to get working stock Dolby atmos which is different from that one we can find in other threads
Or
You prefer Viper4android?
Edit: does Netflix work fluently?
Thanks a lot!
Installation went smooth, so far everything seems to be working.
Still need to set up the tab, but I'm glad I finally got rid of the Lenovo bloatware (like kidoz).
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Update:
2020-03-19
Fixed USB flash drives mounting connected by OTG
Lucinde said:
Does anybody know perhaps if it is possible to create restricted profiles in LineageOS? Not by default in this ROM, I'm now trying to figure out if it can be enabled.
Click to expand...
Click to collapse
If anyone else would have the same question: I found a workaround. You can create a new user via adb with the command "adb shell pm create-user --restricted <username>".
I didn't find a way to create the restricted profile from the settings menu, but once created, it can be managed via the menu.
In the meantime I installed some apps and so far, so good. From the limited time I worked with it, it seems to run smoother than with the stock ROM :good:
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Previously problem with installing process and bricked now fixed using MI lash and successfully installed lineageos see post 18 and later how to install:
https://forum.xda-developers.com/showpost.php?p=82142685&postcount=18
And 2088, in second twrp thread, for 100% working restoring stock system solution:
https://forum.xda-developers.com/showpost.php?p=82095401&postcount=2088
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Managed to install Lineage on my TB-8504F, but it doesnt get past the Lineage boot animation, no matter how long I leave it.
Pushed TWRP to Recovery, formatted as required. Had to amend the Lineage image to remove the device checks, as although I definately have TB-8504F, it didnt like that TWRP reported it as TB_8504f - ?
Installed and installed GAPPS, cant get past load screen.
I do have a backup, so not concerned, but frustrated!
Any help appreciated
BigBrother84 said:
Thank you @Plant
I have never been trying to restore using fastboot commands, only by twrp.
The problem is that both twrps aren't working good on my device. Every partition formating and updating, it stucks. Once time I decided to wait and after 2 h 13 min nothing happened. I tried to format data using fastboot
Code:
fastboot format data
but error occurred. It said that partition format is " " but twrp said it's ext4 maybe that's why they stuck.
In second twrp 3.2.3 thread, Strephon Alkhalikoi helped me and suggested using MiFlash. It worked and after 4 system updates and personalising I decided not to modify it anymore. The only explanation why it doesn't work may be my first stupid move in twrp - not to modify system - and forced shutdown. Rest should work...
Whole situation It is funny cause I "played" with 5 Sony phones flashing e.g. in two of them, android 9 where stock was 6. Everything was working fluently and fast.
Strange errors surprised me here but I'm really happy that you cared about my situation and try to help :good: thank you!
Click to expand...
Click to collapse
Sorry it took me so long to see this, but I had similar problems as you initially. It turns out you actually have to install TWRP to the tablet for it to mount /system properly, booting into it from fastboot doesn't work for some reason - that was what fixed it for me at least. It may be different for your device but I had to run the flash recovery command twice for it to stick..
Also want to say thanks to highwaystar_ru, the past few builds have been running great
Slack3r said:
It turns out you actually have to install TWRP to the tablet for it to mount /system properly
Click to expand...
Click to collapse
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
BigBrother84 said:
Thank you for that important information!
You suggest it may work on my tb-8504f If I install twrp using:
Code:
fastboot flash recovery PATCHTO/twrp.3.x.x.img
After that am I able to boot into twrp using
Code:
fastboot reboot recovery
or buttons combination? Hmh i tried to install TWRP using booted TWRP but stock recovery was booting instead of it. Strange...
Ok so let's imagine theoretically that I did it, but my problems aren't ending on it, I have to modify script installing LOS as @Plant said. (TWRP ERROR 7 - your device is tb_8504f zip is for tb-8504f)
With all that steps you think it may work?
OK, so let's imagine theoretically that it crashed one more time (why not). Am I able to restore everything with twrp installed if I will twrp backup all partitions? Or just reflash everything using MiFlash. Will fastboot flash recovery, modify device recovery permanently? Does MiFlash restores stock recovery? (what is the name of .img that I have to find into system package. Something like recovery.img)? Am I able to unzip just that file, or backup it using some fastboot command and transfer it to my computer?
Thank you for caring!
Click to expand...
Click to collapse
Yep, you'd need to flash TWRP via that fastboot command and boot to recovery by holding vol up/power. I put the ROM and gapps files on a MicroSD card which was picked up by TWRP.
I had similar problems with the ROM not being compatible after the first failed flash, you should be able to modify the updater-script file located at META-INF\com\google\android to include "tb_8504" as a compatible device. I didn't test this method however, as I reflashed the stock image which combined with installing TWRP on the device solved my issues.
If you need to, the full stock image can be flashed using QFIL and the instructions from here, but I'd recommend trying to restore the backup posted by Plant as the QFIL method can take some time to get figured out. I'm not sure how this compares to MiFlash but that would likely produce the same results.
Hope this helps!
screen rotation
Does anybody have problem with auto rotation for screen? In mine TB-8504F it doesn't work. Installed some apps which are testing sensors and none sensor responsible for screen rotation is vsible after flashing this system.
---------- Post added at 04:43 AM ---------- Previous post was at 04:24 AM ----------
If you will brick your device as me you can always use Qualcomm Flash Image Loader (QFIL) with proper files for your device. Note for mine works QFIL v2.0.0.1. Newer versions won't work with my device. It will load stock android 7 then under TWRP you can wipe and flash Lineageos. Firstly was bricked while was going from And 8.0 and not flashed but only booted TWRP. As mentioned above need to flash TWRP
I tried restoring the backup, but after I tried booting into system I got a black screen I can't fix. Power buttons don't work, I can't boot into recovery / anything else. No logos or text. It's like the battery is dead, but I can't power it on. Tried charging it, because the battery was around 10% when I tried restoring the backup, but I don't think that will help. Any other ideas? I think I lost this device for good.
Hi,
After coming from stock 8.0, I’ve got everything up and running which appears to run great.
However, I am struggling to get my PS4 controller working.
It will connect fine via Bluetooth, but no input is detected.
Any ideas?
{
"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 10, 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. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Boot to recovery
Flash the latest build
Boot to recovery again
Flash gapps
Reboot
Downloads :
Builds : http://download.lineageos.org/voyager
SemcCamera addon : https://androidfilehost.com/?w=files&flid=305730
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][voyager][10] LineageOS 17.1, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2020-04-21
Last Updated 2020-04-21
[ protip: These builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261777345 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
cecja said:
Hey Luk,
thanks for working on this great phone.
I sadly got some problems while installing your release on a H4413 (DUAL SIM).
I come from Sailfish OS and flashedH4413 50.2.A.0.400 Customized_NOBA via EMMA.
After that I follow the instructions from the linage install page.
It all seems to work but after I do a "adb reboot" the phone starts to go into a bootloop flashing
the Sony Logo and then for just sec a generic Android Logo after that it goes to a blank screen.
Whats strange is that after the initial flash of the lineage build twrp shows the there is no os installed warning
and sometimes it shows the install twrp app screen both times the result is the same. Bootloop.
Do you have any hint how to go from here? (After restore through emma the phone works normal again)
best cecja
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Ask me again on irc; I don't like guessing on forums.
cecja said:
twrp version: twrp-3.3.1-1-voyager
lineage version: lineage-17.1-20200427-nightly-voyager-signed
Click to expand...
Click to collapse
Bootloop here too, from SFOS.
Back to Omnirom, no problem.
Thanks.
magullo said:
Bootloop here too, from SFOS.
Back to Omnirom, no problem.
Thanks.
Click to expand...
Click to collapse
Same to you, if you join irc I may be able to help.
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:
1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
hamirali said:
OK I wanted to try LineageOS 17.1 and was able to flash it successfully on voyager H4493. Here's what I did:
1. Used newflasher to flash 50.2.A.3.22-R3B. I had deleted the mentioned above files. Also newflasher asked if I wanted it flashed to both slots and I pressed y. As such, it was n enter, n enter and y enter.
2. Did not do item 6 above.
3. From twrp recovery 3.3.0-0 I flashed LineageOS 17.1 and after pressing reboot system - I pressed do not install twrp. I booted successfully into the system.
4. Again from twrp, I flashed gapps - again pressed do not install twrp.
5. Issue with Google service - I reset the phone from settings.
6. Success!
7.At the moment restoring my apps and stuff
Click to expand...
Click to collapse
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
LuK1337 said:
Skipping step 6 was kinda silly from your end. Newflasher only flashes few partitions to both slots rather than all of them, making this /feature/ almost useless.
Click to expand...
Click to collapse
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
hamirali said:
Most definitely your assessment is correct, since you are the expert. What would be your advice? Should I perform step 6 now anyway? Especially since I don't seem to have any issues as yet. Thanks!
Click to expand...
Click to collapse
I guess just to be safe, yes.
LuK1337 said:
I guess just to be safe, yes.
Click to expand...
Click to collapse
Done!
LuK1337 said:
I guess just to be safe, yes.
Click to expand...
Click to collapse
Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
hamirali said:
Just a query, I have downloaded and flashed a version which is no longer appearing on LineageOS voyager page. Should I flash now the one which is appearing (an earlier version) or should I just wait for a newer version, whenever it is available? Thanks in advance.
Click to expand...
Click to collapse
Wait for newer one.
LuK1337 said:
Wait for newer one.
Click to expand...
Click to collapse
When will a new one come?
EmmJottAah said:
When will a new one come?
Click to expand...
Click to collapse
This year.
LuK1337 said:
This year.
Click to expand...
Click to collapse
Perfect:good:
LuK1337 said:
This year.
Click to expand...
Click to collapse
I just wanted to report a somewhat minor issue just for record purposes.
When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.
I don't restart that often and otherwise all works fine, so not much of an issue for me.
H4493 Voyager
LineageOS 4.30.2020
hamirali said:
I just wanted to report a somewhat minor issue just for record purposes.
When I try to restart my device, it gets stuck at the LineageOS logo. I have then have to enter into twrp recovery and reboot to system.
I don't restart that often and otherwise all works fine, so not much of an issue for me.
H4493 Voyager
LineageOS 4.30.2020
Click to expand...
Click to collapse
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
LuK1337 said:
This year.
Click to expand...
Click to collapse
Nooooooooooooo!!!!!!!!!!!!!!!!! .... (waits impatiently)
LuK1337 said:
It's a magisk related issue that I can't reproduce here... Also booting to lineage recovery is supposedly enough too.
Click to expand...
Click to collapse
Reporting an issue: H4493 Voyager updated to the latest version lineage-17.1-20200529-nightly-voyager.
Cannot seem to make any calls - No service - requests to turn off airplane mode to make calls. However, the airplane mode is infact already off.
Also, strangely enough (for me at least) I can receive calls and sms.
I (maybe stupidly) thought it might be installation error, so I flashed the latest version from recovery - reinstalled everything.
No luck.
Should I not be able to sort it out, I will have to revert back to my previous version. What would you advise?
{
"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"
}
Moto X 2014
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto X 2014, codename victara.
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
None.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll find no support for these.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto X 2014
Contributors
npjohnson, jeferson1979, linckandrea, tortel
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Newest firmware available for your variant/locality
Based On: LineageOS
Version Information
Status: Stable
Created 2020-05-15
Last Updated 2020-05-15
Hello,
this Android version don't have navigation bar?
franciscorizzo said:
Hello,
this Android version don't have navigation bar?
Click to expand...
Click to collapse
If you want the old behavior, you have to set in settings/system/gestures
Just to confirm, we can't root our devices running this version of LOS, right?
idksomuch said:
Just to confirm, we can't root our devices running this version of LOS, right?
Click to expand...
Click to collapse
Soon it will be available a fix for magisk, it's in test yet, if you want to try, I've build one version with the fix. You can install at recovery, and after boot install the manager. It will ask you extra setup and reboot. Available here: https://sourceforge.net/projects/victara-universe/files/Android10/Lineage-17-1/Magisk/
jeferson1979 said:
Soon it will be available a fix for magisk, it's in test yet, if you want to try, I've build one version with the fix. You can install at recovery, and after boot install the manager. It will ask you extra setup and reboot. Available here: https://sourceforge.net/projects/victara-universe/files/Android10/Lineage-17-1/Magisk/
Click to expand...
Click to collapse
That worked, thanks!
Confused, only seeing LOS 16 builds on the official link from above?
jwhite5840 said:
Confused, only seeing LOS 16 builds on the official link from above?
Click to expand...
Click to collapse
17.1 nightlies will be available soon. Hold with us a litlle :fingers-crossed:
Official nightlies available :highfive:
Installed without a hitch! Thanks guys!
(Dirty install using TWRP & factory reset, I'll see how it behaves).
Installed latest lineage-17.1-20200530 build today. Found the following bugs:
1. In commit by @npjohnson CID 0x0 moved to XT0197's guard. So my XT1095 with 0x0 detected now as 1097. Purely cosmetic, but maybe it needs a correction.
2. No MCC and MNC codes or operator names visible on the roaming network. This bug was present also in 16.0. Last time it worked with 14.1.
3. rild crashes when I try to manually select a network (Network & internet -> Mobile network -> unselect Automatically select network) and I get 'Couldn't find networks. Try again.' in GUI. logcat attached.
Amazing work! That my XT1095 which shipped with Android 4.4.4 can now run 10 is remarkable. The 5/30 build is working great so far, using the beta Magisk from a few posts back.
Prior to LOS 17.1, I was running LOS 15.1 (unofficial). I noticed that neither official LOS 17.1 nor LOS 16 (which I used for 1 day, and then 17.1 came out!) can drop the screen brightness as low as 15.1 could. Is it possible to bring back the lower-than-OEM brightness feature?
lantsem said:
Installed latest lineage-17.1-20200530 build today. Found the following bugs:
1. In commit by @npjohnson CID 0x0 moved to XT0197's guard. So my XT1095 with 0x0 detected now as 1097. Purely cosmetic, but maybe it needs a correction.
2. No MCC and MNC codes or operator names visible on the roaming network. This bug was present also in 16.0. Last time it worked with 14.1.
3. rild crashes when I try to manually select a network (Network & internet -> Mobile network -> unselect Automatically select network) and I get 'Couldn't find networks. Try again.' in GUI. logcat attached.
Click to expand...
Click to collapse
I'm aware of this and now a potential fix wich I will test tomorrow. (Rild on searching). Thanks for the log
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
ywlke said:
Amazing work! That my XT1095 which shipped with Android 4.4.4 can now run 10 is remarkable. The 5/30 build is working great so far, using the beta Magisk from a few posts back.
Prior to LOS 17.1, I was running LOS 15.1 (unofficial). I noticed that neither official LOS 17.1 nor LOS 16 (which I used for 1 day, and then 17.1 came out!) can drop the screen brightness as low as 15.1 could. Is it possible to bring back the lower-than-OEM brightness feature?
Click to expand...
Click to collapse
We will look for it ASAP
Just attempted to install LOS 17.1 official nightly 20200601 using TWRP 3.2.1-0 today.
Clean flash completed without error but on reboot got "Encryption Failed" splash screen indicating a factory reset was needed.
Went ahead with that - it booted to TWRP and did a wipe, then rebooted again to the same splash.
Detailed steps were:
(1) Successfully boot OS to LOS 16 20200419
(2) Mount internal storage and copy lineage-17.1-20200601-nightly-victara-signed.zip and open_gapps-arm-10.0-stock-20200530.zip
(3) Boot to recovery TWRP 3.2.1-0
(4) Standard wipe (factory reset)
(5) Install lineage-17.1-20200601-nightly-victara-signed.zip
(6) Wipe cache/dalvik
(7) Install open_gapps-arm-10.0-stock-20200530.zip
(8) Wipe cache/dalvik a second time
(9) Attempt to boot OS to LOS 17.1 20200601 - got LOS boot animation followed by "Encryption Failed" splash indicating factory reset needed
(10) Accepted factory reset "Erase Everything" button
(11) Boot to recovery automatically
(12) Automatically perform factory reset wipe
(13) Attempt to boot OS to LOS 17.1 20200601 - got LOS boot animation followed by "Encryption Failed" splash indicating factory reset needed
... loop ...
Was able to restore from TWRP LOS 16 20200419 backup without issue.
Any suggestions?
jwhite5840 said:
Just attempted to install LOS 17.1 official nightly 20200601 using TWRP 3.2.1-0 today.
Clean flash completed without error but on reboot got "Encryption Failed" splash screen indicating a factory reset was needed.
Went ahead with that - it booted to TWRP and did a wipe, then rebooted again to the same splash.
[...]
Was able to restore from TWRP LOS 16 20200419 backup without issue.
Any suggestions?
Click to expand...
Click to collapse
Interesting, I got the same screen dirty flashing over 16.0 and just thought it was due to my dirty rom (I messed something up before, regular 16.0 updates wouldn't boot) or me screwing up the update process. But since you got it on a clean flash, maybe it's something different?
For completeness, I followed the guide from the updater (see here), namely:
- LOS 16.0 2019-12-27 installed (with opengapps)
- (make a backup in TWRP)
- (not wiping anything)
- reboot to sideload
- reboot to TWRP and use sideload there (regular wasnt working for some reason)
- sideload 17.1 2020-06-01
- flash new opengapps (as per instructions) from TWRP (not sideload, because that wouldn't apply my gapps.config)
- reboot "Encryption failed"
- (restore to backup and give up for the moment)
Also not to mention, I didn't have my phone encrypted on 16.0
Answer to all points: you need to be full ext4 at your filesystem for lineage-17.1. As well dirty flash Android version to another never delivered good results.
jeferson1979 said:
Answer to all points: you need to be full ext4 at your filesystem for lineage-17.1.
Click to expand...
Click to collapse
DATA was f2fs - switched to ext4 and repeated previous steps, worked like a charm. Thanks!
magisk does not work
Any solution? already installed beta version and it doesn't work
Does anyone else experience bootloops if you try to boot the device with Secure Startup enabled?
esjarc said:
Does anyone else experience bootloops if you try to boot the device with Secure Startup enabled?
Click to expand...
Click to collapse
As you commented on issue, connected you are able to boot?
{
"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 11 (R), 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. 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.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
Device tree source code: LineageOS/android_device_htc_m8
Kernel source code: LineageOS/android_kernel_htc_msm8974
Working:
WiFi
Bluetooth
ANT+
Camera (including video recording)
FM Radio
Telephony (Calls, MMS/SMS and Mobile data)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Broken / not yet supported:
MHL
NFC
Compatibility:
Single SIM variants:Builds are compatible with all M8 single SIM variants (m8ul, m8vzw and m8spr).Dual SIM variants:Builds are compatible with all M8 Dual SIM variants (m8dug and m8dwg).In both cases, all builds are based off the HTC's Android 6.0.1 firmware and kernel with binaries from Android 6.0 GPe.
Downloads:
Single SIM variants:
lineage-18.0-20201109-UNOFFICIAL-m8.zip
Dual SIM variants:
lineage-18.0-20201109-UNOFFICIAL-m8d.zip
Installation:
Reboot to recovery (TWRP by @Captain_Throwback) - Direct link
Wipe /system, /data and /cache
Install LineageOS zip package
[*]Install [optional] a Google Apps package of your choice (Open GApps is advisable, but stock and super variants are not recommended!!!)
Credits & collaborations
This work is due to efforts from everyone involved in M8 development. The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Device wiki:
Single SIM variants:
Official wiki link
Dual SIM variants:
Official wiki link
Please note that M8 GPe partition layout is no longer supported. The device must first be converted to Sense firmware, otherwise installation will fail.
Can not find Gapps for m8.
---------- Post added at 10:51 PM ---------- Previous post was at 10:28 PM ----------
BitGapps will this work? Any other option?
https://bitgapps.cf/
https://bitgapps.cf/arm/R/
Initial expression everything working. Nice job
Gapps Link: https://bitgapps.cf/arm/R/
had a few teething troubles, first the clicky bootloop (speaker popping) on the lineage animation, then an "entering recovery" loop (my twrp had disappeared (probably because I was using an out of date one), got back to fastboot and flashed twrp-3.4.0-1-m8.img and all is well until booting lineage, then powering off and entering recovery, at which point it's gone again and it just reboots normally. Reverting to a fresh 17.1 and the recovery remains intact.
works nicely with the Gapps above,
sadly my banking apps don't, Is this because it's signed with public keys?
Out of all the ROMS i've tried, only your variant of 17.1 worked correctly
In addition to not being able to boot into recovery as mentioned earlier, It would appear that Setting up screen lock results in a boot loop (Verizon Variant) otherwise looks pretty solid
fela4 said:
In addition to not being able to boot into recovery as mentioned earlier, It would appear that Setting up screen lock results in a boot loop (Verizon Variant) otherwise looks pretty solid
Click to expand...
Click to collapse
Same here. Furthermore, now I cannot install fastboot drivers and reinstall twrp recovery. Any solution? Can't even install gapps.
adem_7 said:
Same here. Furthermore, now I cannot install fastboot drivers and reinstall TWRP recovery. Any solution? Can't even install gapps.
Click to expand...
Click to collapse
The GApps at https://bitgapps.cf/arm/R work fine
You should be able to boot TWRP using fastboot
download the TWRP image and open a terminal in that directory
I use Linux so this came in handy
Code:
sudo $(which fastboot) boot twrpxxx.img
**replace twrpxxx with your TWRP image file name
Your device should boot TWRP and you can flash your zips
Installation removes twrp recovery
I used Linux and fastboot to reinstall latest twrp recovery image.
Too many issues at the minute for use so going back to previous or other 10 ROM.
cexcells said:
Installation removes twrp recovery
I used Linux and fastboot to reinstall latest twrp recovery image.
Too many issues at the minute for use so going back to previous or other 10 ROM.
Click to expand...
Click to collapse
No issue at all, Just You need to install twrp after the gapps installation is completed through twrp, do not leave twrp before install twrp image.
LineageOS 18 also look good, i am using it as my daily driver.
Just follow this=> Goto TWRP recovery and install these one by one.Don't leave twrp before install twrp.img
1. install lineageOS 18
2. Install Gapps
3. install twrp
To install Twrp through twrp=> goto install again, then tap install image(bottom right), select Your twrp file, then select recovery, then conform simple.
Dynamo_anik said:
No issue at all, Just You need to install twrp after the gapps installation is completed through twrp, do not leave twrp before install twrp image.
LineageOS 18 also look good, i am using it as my daily driver.
Just follow this=> Goto TWRP recovery and install these one by one.Don't leave twrp before install twrp.img
1. install lineageOS 18
2. Install Gapps
3. install twrp
To install Twrp through twrp=> goto install again, then tap install image(bottom right), select Your twrp file, then select recovery, then conform simple.
Click to expand...
Click to collapse
I also had the issue of a bootloop every time immediately after getting to the home screen.
cexcells said:
I also had the issue of a bootloop every time immediately after getting to the home screen.
Click to expand...
Click to collapse
i did clean installation and i didn't face any issue.
Dynamo_anik said:
i did clean installation and i didn't face any issue.
Click to expand...
Click to collapse
So did I. I only got the boot loop after setup and synching my Google account. First time I rebooted I had the boot loop and couldn't do anything. Waiting for a newer build. It may have something to do with trying to set a pin for the lockscreen.
cexcells said:
So did I. I only got the boot loop after setup and synching my Google account. First time I rebooted I had the boot loop and couldn't do anything. Waiting for a newer build. It may have something to do with trying to set a pin for the lockscreen.
Click to expand...
Click to collapse
Use bitgapps
https://bitgapps.cf/arm/R/
there is no google account setting up at the starting.
Flashing this rom on my M8 worked perfectly fine.
Thanks a lot for your work!
took the plunge
cexcells said:
I also had the issue of a bootloop every time immediately after getting to the home screen.
Click to expand...
Click to collapse
Followed your 3 step install and all great so far.
Skipped setting lock screen during set up as a precaution, is it OK to set one up?
Installing apps from an OTG USB is going great
Hi
My phone is in S-ON mode and Flashing this rom on my M8, but when I switch the phone to TWRP recovery mode, TWRP recovery was removed.
When will the official lineage 18 update be released?
text1 said:
Hi
My phone is in S-ON mode and Flashing this rom on my M8, but when I switch the phone to TWRP recovery mode, TWRP recovery was removed.
When will the official lineage 18 update be released?
Click to expand...
Click to collapse
For now S-on / s-off.. ..twrp recovery mode will removed. So you've to flash again via fastboot
ainaz said:
For now S-on / s-off.. ..twrp recovery mode will removed. So you've to flash again via fastboot
Click to expand...
Click to collapse
I get the message "waiting for device" the adb drivers installed but the PC does not see the phone. Also now it is not possible to get root, and TWPR cannot be installed via the app.
Is there a solution for this
thanks in advance.
Phone is unlcked and S-off
Hboot-3.19.0.0000
Radio-1.25.214500021.06G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-
eMMc-boot 2048MB
JAN 15 2015,22:51:08.2452
Martoost said:
I get the message "waiting for device" the adb drivers installed but the PC does not see the phone. Also now it is not possible to get root, and TWPR cannot be installed via the app.
Is there a solution for this
thanks in advance.
Phone is unlcked and S-off
Hboot-3.19.0.0000
Radio-1.25.214500021.06G
OpenDSP-v62.2.2-00593-M8974_HM.1118
OS-
eMMc-boot 2048MB
JAN 15 2015,22:51:08.2452
Click to expand...
Click to collapse
Adb driver is not enough for that, you also have to install the HTC mobile driver. If it's still the same try changing the USB cable