{
"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"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on castor.
Downloads
castor: Download LineageOS 17.1 for Xperia Tablet Z2 LTE
castor_windy: Download LineageOS 17.1 for Xperia Tablet Z2 WiFi
If you prefer TWRP over Lineage recovery, you can get it here.
Recommended Google Apps package: Open GApps (choose ARM as Platform and 10.0 as Android, use the Variant you want. Recommended nano package)
Source code
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.
The device specific source code can be found in the LineageOS Github repo.
Tablet Z2 LTE device tree
Tablet Z2 Wi-Fi device tree
Sony Shinano common device tree
Sony MSM8974 common device tree
Sony MSM8974 kernel
The used defconfig is lineageos_shinano_castor_defconfig.
Changelog:
Changes for castor
Bug reports:
Please submit bugs and other errors in this thread
How to submit a bug report
LineageOS GitLab
Donate to support development:
Donate via PayPal to vware
Donate via PayPal to LineageOS
Contributors
Georg Veichtlbauer
NeoArian (Common)
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2020-12-29
Last Updated 2021-02-04
[reserved]
Great to hear about a new ROM alternative. Could you please share any information about what is working and what is not working? Thinking about changing from AICP to your ROM.
pretty much everything should be working. tested and confirmed: lte, wifi, gps, audio, bluetooth, sensors (accelerometer, gyrometer & co) ...
i am a lineage team member, been running my tablet on lineage for weeks. if people do find bugs, please post them here. this is the last stage of testing with a broader audience before the builds will go official.
Hi everybody,
Looks likes things turned bad for me when trying to flash this ROM.
Here is my story:
- I have a SGP511 Castor Windy. Before trying to upgrade, I had a twrp 3.2 recovery (from SpiritCroc's CarbonROM thread) and a AICP 14 ROM. Nothing to complain with this combo except frequent Wifi connection issues.
- I started flashing SpiritCroc's twrp 3.4 recovery and everything went flawlessly (maybe that's my mistake). No troubles booting system or Recovery.
- Following this thread, I flashed (with sideload mode when in TWRP 3.4) the Los17.1 ROM and Magisk 20.4 respectively (after data + system + cache wipes of course) No warning or error during this process.
Things turned bad at reboot : blank screen, no notification LED, not even the usual xperia logo at startup . . . My tablet looks bricked !
Forcing restart with the power button brings only a small vibration, but both screen and led stay blanked. I tried to boot in recovery mode: no way.
The only thing I can do is to boot in fastboot mode (blue LED is on) I tried a fastboot reboot recovery: no chance. If I try a simple fastboot reboot, nothing hapens except a flashing red led as long as the tablet usb is connected to the PC. When I disconnect the USB, led turns out and screen remains black ....
I'm stuck with no idea to go further. I'm afraid the only solution left is to go back to stock with flashtool ?
If anybody has a better idea, I take it !
Sorry for being so long and thank you for your assistance.
creditabricole said:
Hi everybody,
Looks likes things turned bad for me when trying to flash this ROM.
Here is my story:
- I have a SGP511 Castor Windy. Before trying to upgrade, I had a twrp 3.2 recovery (from SpiritCroc's CarbonROM thread) and a AICP 14 ROM. Nothing to complain with this combo except frequent Wifi connection issues.
- I started flashing SpiritCroc's twrp 3.4 recovery and everything went flawlessly (maybe that's my mistake). No troubles booting system or Recovery.
- Following this thread, I flashed (with sideload mode when in TWRP 3.4) the Los17.1 ROM and Magisk 20.4 respectively (after data + system + cache wipes of course) No warning or error during this process.
Things turned bad at reboot : blank screen, no notification LED, not even the usual xperia logo at startup . . . My tablet looks bricked !
Forcing restart with the power button brings only a small vibration, but both screen and led stay blanked. I tried to boot in recovery mode: no way.
The only thing I can do is to boot in fastboot mode (blue LED is on) I tried a fastboot reboot recovery: no chance. If I try a simple fastboot reboot, nothing hapens except a flashing red led as long as the tablet usb is connected to the PC. When I disconnect the USB, led turns out and screen remains black ....
I'm stuck with no idea to go further. I'm afraid the only solution left is to go back to stock with flashtool ?
If anybody has a better idea, I take it !
Sorry for being so long and thank you for your assistance.
Click to expand...
Click to collapse
try:
fastboot flash recovery twrp.img
fastboot reboot
while the sony logo is displayed, push vol+ and vol- a couple of times in succession to get into recovery. if that does not work, something is seriously awry that can't have anything to do with this rom.
do please contact me via pm if you have further troubles
I already tried to re-flash recovery (both twrp 3.2 & 3.4) and reboot from fastboot mode but no way: I can't even have the Sony logo at startup: both screen and notification led stay blank . . .
I'll give it another try tonite and let you know. Thank you for your support.
creditabricole said:
I already tried to re-flash recovery (both twrp 3.2 & 3.4) and reboot from fastboot mode but no way: I can't even have the Sony logo at startup: both screen and notification led stay blank . . .
I'll give it another try tonite and let you know. Thank you for your support.
Click to expand...
Click to collapse
No chance: I had another try flashing recovery + fastboot reboot with no more success
Hey there,
Just flashed it, no major problems, apart from :
- automatic screen rotation does not work, except when forced by an app (more buggy than with AICP 15)
- bluetooth keeps crashing and is unusable
- some random reboots
Using Xperia Z2 Tablet WiFi
creditabricole said:
No chance: I had another try flashing recovery + fastboot reboot with no more success
Click to expand...
Click to collapse
I had the same problem. I was able to solve it by re-flashing the boot file from AICP15 & the recovery from TWRP. Then the tablet starts normally (with LineageOS).
@SirBoss1st
Thank youuuuu so much ! You saved my life. I was desperate to see my device booting one day. I have to fess up I would never dare to flash another ROM boot image ! Anyway I still had another issue flashing directly:
Code:
C:\Util\adb-fastboot>fastboot flash boot boot.img
fastboot: error: Couldn't parse partition size '0x'.
So I did that:
Code:
C:\Util\adb-fastboot>fastboot flash:raw boot boot.img
Sending 'boot' (7664 KB) OKAY [ 0.254s]
Writing 'boot' OKAY [ 0.524s]
Finished. Total time: 0.787s
C:\Util\adb-fastboot>fastboot flash recovery TWRP-34.img
Sending 'recovery' (13258 KB) OKAY [ 0.414s]
Writing 'recovery' OKAY [ 0.903s]
Finished. Total time: 1.367s
C:\Util\adb-fastboot>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
And then, at least, the Sony logo appeared and LoS 17.1 first boot was on the way.
I'm not very skilled in android stuff but looks like my boot partition has been corrupted during the first ROM flash.
Hope that can be useful to others and maybe developers . . .
One more time thank you for saving my tablet and your efficiency guys !
so, everyone experiencing problems is on castor_windy?
Coming from AICP 15, updated TWRP to the 3.4.0 version in OP, did a factory reset (cache, dalvik, system wipe) and installed this ROM together with Gapps. Works!!
Got a pop-up that Bluetooth has stopped, indeed. And had one spontaneous reboot (more to come?). Will continue testing but it looks very hopeful. Thanks for keeping my old device alive!
Edit: Btw it's a castor_windy. And I have had no more reboots, only the one.
I am experiencing a stable ROM so far. Only issue I had is a message "Bluetooth keeps stopping" during first start of LineageOS at welcome screen. Now Bluetooth is working fine, I am using a Bluetooth keyboard. Wifi is also fine. No reboot so far. I came from AICP 15 and installed LOS in combination with Gapps nano. Main applications running on my device are Chrome, Nova Launcher and for sure PlayStore. Thank you very much for this great work!
JP_TouchDiamond said:
Only issue I had is a message "Bluetooth keeps stopping" during first start of LineageOS at welcome screen.
Click to expand...
Click to collapse
I had the same message, but I don't use Bluetooth. I came from AICP 15 and I often had reboots in standby mode. Now in Los 17.1 with OpenGapps pico, I haven't had a single reboot yet. It is a good Rom, Thank you for this work!
How will that work with updates, weekly or more on demand?
Hi everybody,
Some feedback after a couple of days using Los 17.1 on my Castor-Windy: Wifi, GPS and many more work nicely. I have no Gapps installed. No reboot to complain about.
What is not working:
- Bluetooth crashes at startup. If I try to use it later I get forcecloses every time.
- double tap wake up does not work
Battery drain looks a little bit higher that with AICP ROM (in sleep mode) but nothing to worry about.
Thank you for this nice ROM !
Oh God, Finally !!!
Let me thank you 1 milion times man.
I try all the custom roms made for the SGP521, but no one had work.
Every rom goes random reboot when the tablet goes deep sleep.
Till now the only one that work for me was the stock 6.0.1 - 23.5.A.1.291.
Finally with this one the problem seems to be gone.
Am not used the rom deeply but till now I can say that, am on castor, Gapps Pico installed, no reboot, Wifi, GPS, NFC and other work without issue. Bluetooth keep crashing, no MAC Address.
Automatic screen rotation does not work in lock screen, when unlocked is ok.
Can't access system when open the settings, everytime the tablet came back at home screen.
The rom start with AICP 15 boot.img.
With the original from lineage the tablet doesn't start, led flash red and tablet reboot.
Can't install magisk either in recovery (TWRP 3.4.0 from spiritcroc) that in Magisk manager, the message is "unsupported/unknow image format" after boot unpacking. Tryed almost every versions either in stable that in canary chanel with patched boot.img.
Make my donation minutes ago. Wish for a more stable release. Thank you for keep our tablet alive !
I am not really experienced with installing custom roms. Unfortunately installing the lineage zip after wiping the tablet did not work. I had before this, installed aicp_castor_windy_q-15.0-WEEKLY-20210115, but I could not get rooting working on it. So I thought lets give this one a try.
After installing I got a black screen, so I flashed the magisk patched boot.img from the aicp rom zip which I still had, and now it is booting. However sensors are not working.
I noticed someone else having the same problem in this thread. Could this be due to having old firmware or so? (Never changed anything on this tablet)
I have tried this rom, but tablet would not boot. When I flashed the boot.img from the aicp rom, I could get it to boot.
I am not really familiar with installing custom roms. Could using a boot.img from a different rom disable the sensors?
What could be the reason that my tablet is not booting with your default lineage boot.img?
Anybody succesfully root the rom? If yes could explain how? Thank you.
Related
Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks
I begging by thanking everyone in this site for their great effort and support (this is the best site for these topic).
I have a problem with newly install lineageOS, I will explain the procedure I made so far:
-I have a sumsang note 3 neo with the code name: SM-N7505ZWADBT.
-I rooted my phone using: CF-Root-SM-N7505-5.1.1.zip and Odin3 v3.10.7 (after I tried other roots but they didn’t work).
-I then installed then: twrp-2.8.7.0-hlltexx-4.4.img.tar from their official website.
-When go to recovery mode the message: Recovery is not Seandroid Enforcing. I can still access the recovery mode and this warning only shows when I access recovery mode. Also if I do nothing and want to poweroff, they ask me that this machine seam not to have root installed, so I skipped it.
-I wiped the stock ROM without back up (huge mistake).
-I flashed then lineage-14.1-20170526-UNOFFICIAL-hllte.zip (without GAPPS, I don’t want them), which was successful beside two lines which appear in red saying: E: unknown command [log]
-I then turned on phone, ( Recovery is not Seandroid Enforcing doesn’t appear, it only appear in recovery mode).
-The lineageOS took to long for first boot, so I took off the battery and went back to recovery mode.
-After wiping and flashing multiple times, it worked and I could get the lineageOS running.
-When I enter they ask to parametrize the phone.
-Everything seam to work alright, except wifi, phone calls and camera: wifi adress show up but when I try to conenct they try logging but can’t, sms messages work fine but when I call I can’t hear anything and so the other person, speakers are working, camera does not work.
So there I gave a details approach of what I did to get to this situation, I tried to download stock firm with the same code but I couldn’t find the exact number (SM-N7505ZWADBT).
I would realy like to make lineageOS work, so if you can help me I would really appreciate it, also if it is impossible, then how to get my previous stock ROM.
Hello,
I was running SailfishOS on my H3223, but I decided to go back to Android. I used the EMMA tool, and restored the latest "service" to the device. Everything worked perfectly. Then, I flashed Lineage 17.1, and again, everything worked, and I used the ROM for several days until I noticed that my GPS wasn't working. The latest firmware version available in the EMMA tool was 50.1, so I figured that must be the problem. I used XperiFirm to download the H3223 Customized US firmware which is 50.2, and then I used newflasher to flash it. Everything worked perfectly, including the GPS.
This is where the problem started. I then tried to flash Lineage 17.1 again. The flash completed without errors, but once I reboot it, I just get a black screen. If I change the volume, the volume dialog shows on the screen, but nothing else - it's like the initial setup has frozen, or the launcher failed to start or something. If I force it to reboot, it hangs on the lineageos boot animation. Since then I've tried using EMMA to restore, I've flashed a few different firmware's using newflasher. Every time, I get the same results - the Sony firmware works perfectly. Anything else I try and flash boots to a black screen. The volume dialog will always show up. If the ROM has ADB enabled, and I plug in a cable, the ADB authorization window will show, but otherwise the screen is just black. Forcing it to reboot either hangs on the boot animation, or boot loops. I've tried flashing Lineage 16.0, Lineage 17.1, AlaskaLinuxUser's AOSP 9 and 10, and all behave the same.
I feel like I have to be missing something simple, because any version of a Sony ROM that I use works perfectly.
Any ideas?
Hi,
last week I successfully installed LineageOS as of March 15 on my OP6 and it worked perfectly.
This morning, I applied the system update to the latest version as of March 22. It took a long time to process (about 5 minutes), then rebooted as usual, but then surprisingly stuck in Crashdump mode.
After some switching off and on again with the same result, I found I still could boot into recovery by VolDown + Power (it’s the simple lineage recovery, not TWRP).
Since then, I tried several times to reinstall both Lineage versions as of 15th and 22nd the usual way, but the phone never would boot any system. The recovery works perfectly, system can be flashed by ADB sideload and reports success, but after rebooting from recovery into system, it either runs into Crashdump or back into fastboot.
Bootloader is unlocked.
I have applied the copy-partition tool to make sure there is no bad software in the other slot but that didnt help either.
I have done factory reset / format all and re-flashed Lineage (latest and older version) but same result - fastboot or Crashdump.
Any hints what I can try to get a working Lineage again?
--ks
Update: It was possible to flash OxygenOS by MsmDownload, which booted perfectly and is running through its setup procedure now. Though I prefer LineageOS by far, I won’t switch back unless I am sure this won’t happen again
Browsing a bit further through this forum, I got the impression this is quite common on OnePlus phones from OP6 on, and so might happen at random intervals even with the manufacturer’s OS. In other words, a built-in fault. I want my wonderful OP 5T back
--ks
I installed Lineage on my Moto G7 Power a few days ago, and after rebooting it yesterday, it's stuck in bootloop (the Lineage starting animation is displaying), i have left it for 4 hours with nothing changing. can reboot it by holding the power button and I am able to get into recovery. USB debugging still works aswell.
I installed the newest nightly Lineage build for ocean (19.1), along with MindTheGapps and TWRP.
This has happened again, 2 days ago. I tried dirty flashing the same lineage version and nothing happened. I ended up completely restoring my phone using the official tool motorola provides.
then, after reinstalling lineage and twrp this time (so i would have access to my data if it were to happen again), and setting everthing up again, it just happened again yesterday.
things I've tried:
- clearing the cache using twrp
- letting it boot for hours on end
- repairing the file system with twrp (idek what that does, but I had hopes)
I would really like to just find a solution to this, as I very much enjoyed using Lineage (when it was working), but reinstalling everything every 2 days is not an option. this **** is driving me insane, i haven't been able to find a decently answered forum post on this anywhere.
so yeah, i would be eternally grateful for any help I can get.
thank you <3
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
greenmatrix said:
Hello,
Did you ever find a solution to this? I am unable to boot into LineageOS as well, the boot just hangs. Posted on this thread: https://forum.xda-developers.com/t/official-lineageos-19-1-for-the-moto-g7-g7-power.4436929/page-7
Click to expand...
Click to collapse
no, I'm sorry, I have nothing. I gave up after the fourth time of wiping everything and am back to using the motorola rom. a real shame
good luck tho and if you find something that works, do let me know please!!
Bummer. I will let you know if I figure it out.
Got it working, see https://forum.xda-developers.com/t/...or-the-moto-g7-g7-power.4436929/post-87342621