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. And if you would like to contribute to LineageOS, please visit our Wiki.
Important Info
DON'T USE TWRP 3.0.2-0 OR OLDER WITH LINEAGEOS. IT DOES NOT WORK CORRECTLY. USE VERSION 3.2.1.0 HERE
Current lineage 16.0 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
If you already have those you don't need to flash them again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS OFFICIAL: https://download.lineageos.org/shamu
Latest build dates back to april 1st 2020 and there will be no new OFFICIAL builds as shamu has been promoted to LineageOS 17.1.
LineageOS UNOFFICIAL: lineage-16.0-20201107-UNOFFICIAL-shamu.zip
Includes November 2020 Android Security Bulletins.
Here is its md5sum.
Google apps: MindTheGapps or OpenGAPPS <= nano
HEADS UP:
When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
If you are migrating from an OFFICIAL build to the UNOFFICIAL build you have 2 options:
Wipe data and do a clean install of UNOFFICIAL build
Dirty flash thanks to an intermediate MIGRATION build
First flash the MIGRATION build (lineage-16.0-20200430-MIGRATION-shamu.zip md5sum), boot to it and then flash the UNOFFICIAL build and boot to it.
SU addon zip: Addon Install zip / Addon Removal zip
NOTE: LineageOS does not come with root, so this is now provided for those that want it.
The install zip is a one time flash, like gapps.
Meaning, it persists when updating to a new LineageOS nightly.
Changelog
Builddate: 2019.03.01
Changes:
[new] Initial LineageOS 16.0 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
You're also welcome to use npjohnson's personal builds, but these are experimental, and likely to destroy your data. These builds include GApps, and Pixel-Goodies, among other things -- you'll find no support for these, so please don't discuss these here.
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, Elektroschmock, dwardo
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-03-01
Last Updated 2020-11-07
Reserved
Please read how to
- Properly report a bug: https://wiki.lineageos.org/bugreport-howto.html
- Capture a log https://wiki.lineageos.org/logcat.html
Clean flashed Lineage 16.0, Gapps 9.0 Mini, Magisk 18.0. I was not encrypted on LOS 15.1
Edit: Had a hiccup on the setup screen (phone froze). Restarted and all good.
Edit: Pixel Launcher doesn't seem work for me. Crashes every time going to home screen. Had to go to APKMIRROR and download latest version. Was working for 5 minutes or so, but now crashes again. Still messing with it.
Edit: Clean flashed a second time with 16, Gapps 9.0 FULL, and Magisk 18.0. Setup screen froze again. I'm gonna restore my 15.1 backup as I've run out of time to mess around.
FYI - I'm not looking for help.. just posting my experience.
Confirming everything is good here with 16.0.
I basically followed the steps on the LOS wiki (upgrading from 15.1, unencrypted, no wiping-data):
1. Format /system partition in TWRP
2. Sideload 16.0 ROM
3. Sideload Opengapps 9.0
4. Sideload Magisk
5. Reboot
Everything working.
Only thing I noticed (which may be just how Lineage OS is designed) was my homescreen setup was overwritten by the Lineage OS defaults so I had to set up widgets again.
Great work bro as always @Electroshmock :good:
Just a small reminder, if a user is going to post about issues with the ROM, please attach logs for the OP to help look into the issue.
Hi, I lost the /data partition (error: Failed to mount '/data' (Device or resource busy)), how to get it back?
Initially I had the latest 15.1, and did all instructions to my best understanding. All went well, but when I was ready to finally reboot, TWRP 3.2.1.0 said I have no OS installed. Then I formatted data, and the problems started.
EDIT: /data became OK after I rebooted to recovery. Now I installed again the same way, before final reboot TWRP said I have no OS installed. But I ignored that and rebooted. Now the system seems to work, at least I'm currently settings up the phone again.
But the question is: why does TWRP inform that I have no OS installed?? Any ideas?
wrsg said:
Confirming everything is good here with 16.0.
I basically followed the steps on the LOS wiki (upgrading from 15.1, no wiping-data):
1. Format /system partition in TWRP
2. Sideload 16.0 ROM
3. Sideload Opengapps 9.0
4. Sideload Magisk
5. Reboot
Everything working.
Only thing I noticed (which may be just how Lineage OS is designed) was my homescreen setup was overwritten by the Lineage OS defaults so I had to set up widgets again.
Click to expand...
Click to collapse
This method worked for me as well. :good:
amroj said:
Hi, I lost the /data partition (error: Failed to mount '/data' (Device or resource busy)), how to get it back?
Initially I had the latest 15.1, and did all instructions to my best understanding. All went well, but when I was ready to finally reboot, TWRP 3.2.1.0 said I have no OS installed. Then I formatted data, and the problems started.
Click to expand...
Click to collapse
Probably need to add that to OP. You cannot be encrypted. Need to format (not wipe) user data partition in TWRP. You will lose everything there, so backup to PC or usb flash drive.
TWRP 3.2.1-0
data was formatted and encrypted with Lineage 14, upgraded to 15 and now 16.
Flashed LineageOS 16.0 + MindTheGapps + Magisk 18.1
After reboot: message from OS: your password is correct but the data is corrupted, factory reset is needed
Tried to reboot to TWRP: password not correct
Rebooted to OS and did factory reset: same message (password correct but data corrupted).
I have an offline backup on a PC with LineageOS 15 + data.
Wiping data does not help (same problem after reboot), I guess I have to format it.
Ideas ?
everdium said:
TWRP 3.2.1-0
data was formatted and encrypted with Lineage 14, upgraded to 15 and now 16.
Flashed LineageOS 16.0 + MindTheGapps + Magisk 18.1
After reboot: message from OS: your password is correct but the data is corrupted, factory reset is needed
Tried to reboot to TWRP: password not correct
Rebooted to OS and did factory reset: same message (password correct but data corrupted).
I have an offline backup on a PC with LineageOS 15 + data.
Wiping data does not help (same problem after reboot), I guess I have to format it.
Ideas ?
Click to expand...
Click to collapse
sideload
wrsg said:
sideload
Click to expand...
Click to collapse
So format data and then sideload LineageOS 15 or 16 ?
OP says that data can not be decrypted by TWRP if encrypted by LOS 16.
everdium said:
TWRP 3.2.1-0
data was formatted and encrypted with Lineage 14, upgraded to 15 and now 16.
Flashed LineageOS 16.0 + MindTheGapps + Magisk 18.1
After reboot: message from OS: your password is correct but the data is corrupted, factory reset is needed
Tried to reboot to TWRP: password not correct
Rebooted to OS and did factory reset: same message (password correct but data corrupted).
I have an offline backup on a PC with LineageOS 15 + data.
Wiping data does not help (same problem after reboot), I guess I have to format it.
Ideas ?
Click to expand...
Click to collapse
Same here
rivernov said:
Same here
Click to expand...
Click to collapse
I formatted data, rebooted and now in the LineageOS 16 initial setup.
If that works, the only problem is how to restore the data partition from the LOS 15 backup.
Well, the good old stability and smoothness of LOS!
All pretty fine here! Franco Kernel working fine!
Please dev. Any root solution to remove brighness slider from quick settings?
everdium said:
I formatted data, rebooted and now in the LineageOS 16 initial setup.
If that works, the only problem is how to restore the data partition from the LOS 15 backup.
Click to expand...
Click to collapse
It worked. After a reboot, its now reinstalling all my apps.
There is still the matter of restoring the LOS 15 backup but I have all my data in the cloud. Maybe its better not to restore the backup and see whatever settings need to be reapplied manually.
But now my data is encrypted by LineageOS 16 and the OP says that TWRP can not decrypt it.
everdium said:
So format data and then sideload LineageOS 15 or 16 ?
OP says that data can not be decrypted by TWRP if encrypted by LOS 16.
Click to expand...
Click to collapse
Did you try doing that, in spite of TWRP not being able to decrypt it? What error did you get?
edit: I guess it's too late for you to try this, I didn't read your latest reply until after typing that.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
everdium said:
It worked. After a reboot, its now reinstalling all my apps.
There is still the matter of restoring the LOS 15 backup but I have all my data in the cloud. Maybe its better not to restore the backup and see whatever settings need to be reapplied manually.
But now my data is encrypted by LineageOS 16 and the OP says that TWRP can not decrypt it.
Click to expand...
Click to collapse
I had the same issue, I solved it by using an option from inside the Android settings, I think it was reset phone or something like that.
L.F.B. said:
Well, the good old stability and smoothness of LOS!
All pretty fine here! Franco Kernel working fine!
Please dev. Any root solution to remove brighness slider from quick settings?
Click to expand...
Click to collapse
Umm, is Franco Kernel even being updated for the Shamu anymore? It doesn't seem so, not sure why you are even flashing it. It'll be behind on performance and security updates.
wrsg said:
Did you try doing that, in spite of TWRP not being able to decrypt it? What error did you get?
edit: I guess it's too late for you to try this, I didn't read your latest reply until after typing that.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
I had the same issue, I solved it by using an option from inside the Android settings, I think it was reset phone or something like that.
Click to expand...
Click to collapse
So after the problems with mounting data, I formatted it with TWRP. Rebooted, finished the LOS 16 setup and all my apps where reinstalled.
Everything seems to work and guess what, I rebooted into TWRP and it is able to read everything on data. The strange thing is, it doesn't ask for the PIN.
Maybe its not encrypted ? I thought LineageOS 16 would encrypt it on install. How can I check ?
everdium said:
So after the problems with mounting data, I formatted it with TWRP. Rebooted, finished the LOS 16 setup and all my apps where reinstalled.
Everything seems to work and guess what, I rebooted into TWRP and it is able to read everything on data. The strange thing is, it doesn't ask for the PIN.
Maybe its not encrypted ? I thought LineageOS 16 would encrypt it on install. How can I check ?
Click to expand...
Click to collapse
LineageOS 16.0 does not force the encryption of your data. If you need a bit of security you can encrypt your data from within settings.
I wonder why some of you have problems with upgrading. I tried several combinations. Perhaps because TWRPs format is also broken and you didn't use the fastboot format command.
Related
Introduction
Hello all, this is my version of TWRP for the Nexus 6P, which includes the ability to convert your /data and /cache partitions to F2FS. This will stay inline with TWRP's changes for the most part, the changes will be listed below.
What in the world is F2FS?
From Wikipedia:
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
F2FS was designed on a basis of a log-structured file system approach, which it adapted to newer forms of storage. Jaegeuk Kim, the principal F2FS author, has stated that it remedies some known issues of the older log-structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. In addition, since a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), it supports various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms.
Click to expand...
Click to collapse
Before diving into this, I would recommend reading the official F2FS documentation to understand why this may be good for you. This is potentially unstable, F2FS is a file system that is very much in active development. There is a reason that most OEMs go with ext4 out of the box. But I digress, I am NOT here to sell you on F2FS; it makes zero difference to me if you use it or not, I am merely providing you with a tool to do so.
Changelog + differences
Differences:
f2fs-tools bumped to 1.7.0 (Omni's 6.0 branch is on 1.4.0)
TWRP app installation offer disabled by default
Conversion procedure
Download TWRP from the link above
Grab a kernel that supports F2FS (I use my own as I know it works)
Back up any important data as this will wipe your entire internal storage
Boot into the bootloader and flash the recovery
Boot into TWRP and go into Wipe > Advanced Wipe
Select Data and then hit "Change or Repair File System"
Hit Change File System
Choose F2FS and slide to confirm
Repeat the previous three steps for cache
Reboot and move all of your files back over (if restoring through TWRP, make sure to check the option to use rm -rf instead of formatting)
If you have any issues with this, you may need to ask your ROM developer to merge the two commits below.
Bug reports
You are NOT in ANY circumstance to report ANY bugs to the TWRP team.
If you have an issue with flashing something in TWRP, copy the recovery log to your sdcard and post it here.
If swapping to F2FS does not stick, try formatting your data with TWRP (Wipe > Format Data) or fastboot format userdata first.
If your phone does not boot after swapping to F2FS, either your kernel or ROM does not have proper support; post in their thread.
Additionally, check out some of these helpful posts:
https://forum.xda-developers.com/showthread.php?p=70699197
https://forum.xda-developers.com/showthread.php?p=71074016
Adding support to ROM
In order to properly support the initial conversion to F2FS, please add these two commits to your source:
https://github.com/omnirom/android_system_core/commit/1c6700a8fb31c6e314df4f031fa23fa9178c7ca7
https://github.com/omnirom/android_system_vold/commit/c879edb2fecae709f404c2d71c1d47ceac3a325e
The reason some people have issues converting is fs_mgr will try to read the block device as ext4 and destroy the f2fs block. This commit skips that check, allowing F2FS to pass through.
Sources
TWRP is licensed under GPLv3, meaning my changes must be disclosed. I also inline a custom kernel so that source is included as well. I also add in the other repos I modify.
Recovery: https://github.com/nathanchance/android_bootable_recovery/tree/android-7.1
Kernel: https://github.com/nathanchance/angler/tree/7.1.2-flash
Device tree: https://github.com/nathanchance/twrp_device_huawei_angler/tree/android-6.0
f2fs-tools: https://github.com/nathanchance/android_external_f2fs-tools/tree/android-6.0
First!
Thanks for the recovery. Been using it with flash kernel. I see considerable performance improvement in asphalt Xtreme game( idk if its the f2fs or kernel ).
Nice !!! :fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Thank you, and thank you for the exemplary GPL compliance. It's noticed and appreciated.
Now this is awesome... On it, will report soon
Much appreciated!
Sent from my Nexus 6P using Tapatalk
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Nitrogen : yes
Somebody must report it and i will update my post.
ThNks
ariefabuzaky said:
So what rom is compatible with f2fs ?
Lineage : yes
RR : yes
UberRom : of course
pN : idk
DU : idk
Somebody must report it and i will update my post.
ThNks
Click to expand...
Click to collapse
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Worked perfect! Thanks Flash!!!
I tried this with PN and am now stuck in a boot loop. I flashed the twrp with F2FS support then tried to change the file system followed by installing the latest vendor, latest flashable bootloader+radio, latest pure nexus and gapps, flash kernel, and latest su. Didnt work. Im not stuck in a boot loop I cant get out of. Ive tried every combination of the above. I also tried restoring my backup but that gives me an error. I also tried changing the file system back to ext4. Nothing works. Anyone experience this or have any suggestions?
---------- Post added at 09:09 AM ---------- Previous post was at 08:58 AM ----------
jochem86 said:
Nitrogen should also work but i am doing something wrong... PN should only work with data to f2fs... i am trying different ways right now.
I restored everything to ext4 but i get bootloops now with everyrom... reboots constand... damnit
restored my twrp to latest 3.0.3 but i still get bootlooping... whay did i wrong :S Going back to complete stock latest google image... can anoyone tell me what i did wrong here?!
Restoring factory worked... back on 3.0.3 twrp and with PN rom installed. I will wait a couple of days on how to get it working properly on PN
Click to expand...
Click to collapse
Im in the same boat.....what steps did you do to get back to stock?
Data keeps reverting back to ext4 after 1st boot.
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
Mine too....Im stuck in a bootloop. Are you?
Whats also weird is switching too f2fs wiped my storage but once the data reverted back to ext4....my original storage came back too!! Im not sure how or why that is happening either.
I just followed OP and formatted everything first, now i have SAOSP running with flash on f2fs..
Works great, so far it doesn't feel like a huge improvement though..
Sent from my Nexus 6P using XDA-Developers Legacy app
vnphantom said:
Data keeps reverting back to ext4 after 1st boot.
Click to expand...
Click to collapse
What makes you say that?
Back then when I was using Temasek on my Note 3, he incorporate a script that automatically format the system partition to F2FS when flashing his ROM. That is if the system partition is already in f2fs and I think that was pretty amazing but short live. I wonder if other ROM developer could go the same route if formatting F2FS system was popular enough. That would make updating new rom one step easier. Just for thought.
---------- Post added at 09:38 AM ---------- Previous post was at 09:16 AM ----------
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
minhgi said:
Hi All,
Make sure to restore your backup with "Use rm -rf instead of formating"; else the restore will reformat the partition back to the file system use in the backup.
Click to expand...
Click to collapse
I wish you told this earlier....This is exactly what happened and I had to clean install
NoobInToto said:
I wish you told this earlier....This is exactly what happened and I had to clean install
Click to expand...
Click to collapse
It wouldn't matter though, I get a warning that the backup was made with EXT4 and that backup may not boot unless changed back to it
Iceburn1 said:
What makes you say that?
Click to expand...
Click to collapse
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
Exactly doing the same....
vnphantom said:
Because that's what's happening to me. Maybe it's because I'm on PN. At this time f2fs has not been widely adopted by too many devs so compatibility could be an issue. I think I'll stick with ext4 a bit until f2fs is fully mature.
Click to expand...
Click to collapse
That's too bad its not working for you, its working on my side no problem, did you format in twrp if its not sticking? Im on RR with Flash kernel.
Hello everyone,
A friend of mine has a Galaxy S3 i9300 which I installed years ago CM13. I don't what update he installed but now the phone starts with the screen "Preparing X of Y apps" => when we think it's over (because the phone restarts at the end), well it does another "Preparing X of Y apps", and so on
I don't know what I should do : repair it by flashing the old zip (cm13-2016...-.zip) but maybe I have to "wipe cache" and "wipe dalvik" before?
Or maybe I have to wipe everything (wipe cache, wipe dalvik...) in order to flash LineageOS ? I'd like to follow this path anyway but how can I save the data of my friend such as SMS, Contacts.. ?
It has TWRP and I can mount the partitions and access them via PC
Thank you for your help
Go back to the older gapps.
shivadow said:
Go back to the older gapps.
Click to expand...
Click to collapse
That's what could cause the problem ? Do you have a link about which version of Gapps should I install ? I'm gonna try that by flashing them via TWRP
Should I do a wipe or anything else ?
The only thing you could wipe is cache without having to start over. I doubt that'll fix anything. You can try sourcing another copy of that version to see if the one you have is corrupt.. Otherwise it's probably going to be that it simply doesn't support your os.
shivadow said:
The only thing you could wipe is cache without having to start over. I doubt that'll fix anything. You can try sourcing another copy of that version to see if the one you have is corrupt.. Otherwise it's probably going to be that it simply doesn't support your os.
Click to expand...
Click to collapse
What apps did he install?
Some apps make the system crash. It's a bug that only happens in cm12/13 based roms. Try upgrading his phone to lineageos or install android 4.4
JCFB said:
What apps did he install?
Some apps make the system crash. It's a bug that only happens in cm12/13 based roms. Try upgrading his phone to lineageos or install android 4.4
Click to expand...
Click to collapse
If it's me I'd upgrade to LineageOS 14.1 directly But I was thinking about its data such as SMS, MMS...
I just did a Nandroid Backup using TWRP => is it possible after installing LineageOS 14.1 using clean method (after wiping data, cache and system I think ?) that I can retrieve the data by restoring TWRP backup ? (without the cm13 of course)
skype007 said:
If it's me I'd upgrade to LineageOS 14.1 directly But I was thinking about its data such as SMS, MMS...
I just did a Nandroid Backup using TWRP => is it possible after installing LineageOS 14.1 using clean method (after wiping data, cache and system I think ?) that I can retrieve the data by restoring TWRP backup ? (without the cm13 of course)
Click to expand...
Click to collapse
I am not sure, try restoring only the data partition over a clean lineage install. I don't like dirty flashing, but you have no solution other than try this. If it doesn't work it's time to start from zero.
I was almost forgetting, try flash cm13 zip, then restore data partition from twrp and if you can boot, do a Titanium backup of the data you want. Then do a clean install of lineage and try to restore the titanium backup
JCFB said:
I am not sure, try restoring only the data partition over a clean lineage install. I don't like dirty flashing, but you have no solution other than try this. If it doesn't work it's time to start from zero.
I was almost forgetting, try flash cm13 zip, then restore data partition from twrp and if you can boot, do a Titanium backup of the data you want. Then do a clean install of lineage and try to restore the titanium backup
Click to expand...
Click to collapse
I tried to flash old cm13 zip that I have (without gapps) => it boots
Then I tried via TWRP to restore only data partition => Stuck again with "Preparing apps" xP
What If I flash LineageOS 14.1 from scratch but use Titanium Backup to extract data from Nandroid backup ?
skype007 said:
I tried to flash old cm13 zip that I have (without gapps) => it boots
Then I tried via TWRP to restore only data partition => Stuck again with "Preparing apps" xP
What If I flash LineageOS 14.1 from scratch but use Titanium Backup to extract data from Nandroid backup ?
Click to expand...
Click to collapse
I think you need the Pro version of Titanium to do that. I don't know any alternative
After many attempts, I finally managed to make it work again
Here's what I do (maybe it could help other people)
Step 1: I restored the Nandroid backup I made via TWRP
=> At this point Cyanogenmod13 is back
Step 2: I found a Cyanogenmod14.1 zip file somewhere on internet (cm-14.1-20161225-NIGHTLY-i9300.zip)
=> I flashed it before/after wipe cache/dalvik
Step 3: I flashed Gapps for this version of Android thanks to open-gapps website
=> Last wipe cache/dalvik before Reboot
Step 4: Enjoy
Good evening, gentlemen, I have a Redmi Note 3 Pro Kate and I like to try out some ROMS. I was using the Pixel Experience on Android 8.1 normally, with everything working. I saw that the version with Android 9.0 (Pie) had been released and I installed it through TWRP.
The ROM worked normal except for the camera, since dealing with a beta is acceptable. I decided to back up the backup I had made by TWRP and guess what, the camera was not working too.
I tried other ROMS like Lineage OS 14.1, Havoc OS and then came back I reinstalled Pixel Experience 8.1 cleanly.
Every time I reinstall, the native ROM camera application is not installed along with the other applications and even installing other applications seems like the "camera service" has not been installed.
Has anyone been through this and can you help me?
AlphaHook said:
Good evening, gentlemen, I have a Redmi Note 3 Pro Kate and I like to try out some ROMS. I was using the Pixel Experience on Android 8.1 normally, with everything working. I saw that the version with Android 9.0 (Pie) had been released and I installed it through TWRP.
The ROM worked normal except for the camera, since dealing with a beta is acceptable. I decided to back up the backup I had made by TWRP and guess what, the camera was not working too.
I tried other ROMS like Lineage OS 14.1, Havoc OS and then came back I reinstalled Pixel Experience 8.1 cleanly.
Every time I reinstall, the native ROM camera application is not installed along with the other applications and even installing other applications seems like the "camera service" has not been installed.
Has anyone been through this and can you help me?
Click to expand...
Click to collapse
First thing is stay on latest twrp 3.2.3.
Also flash latest firmware zip.
Your cam is crashing or not showing coz May be data and internal storage was encrypted in previous rom.
Before installing new rom. Format data in twrp. I m not talking about wipe data.
Format data will format you data and internal storage.
If you encrypt your device. Camera will crash or wont work.
So go to twrp
First > Format data < must do
Then you can do wipe data reset
Flash rom
Flash gapps
Reboot
naik2902 said:
First thing is stay on latest twrp 3.2.3.
Also flash latest firmware zip.
Your cam is crashing or not showing coz May be data and internal storage was encrypted in previous rom.
Before installing new rom. Format data in twrp. I m not talking about wipe data.
Format data will format you data and internal storage.
If you encrypt your device. Camera will crash or wont work.
So go to twrp
First > Format data < must do
Then you can do wipe data reset
Flash rom
Flash gapps
Reboot
Click to expand...
Click to collapse
My God, man, I can not believe it worked.
Thank you very much!
GooglecrDroid ROM 14-01-2020
FULL last openG(OOGLE)APPS included! (v.12-01-2020)
Last stable crDroid 6.2 based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe data, cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
I don't use this ROM, help each other who use it. Thnx.
DOWNLOAD SF
DOWNLOAD AF
Updates, previous and all ROMs here: LINK
Known issues: don't know
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140 (not my work)
ROM info: Q10 Lineage 17.1, system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 14-01-2020 V0 version
Last Updated 14-01-2020
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
You're welcome.
I'd like to get feedback on whether VOLTE is working? Thanks.
wow thanks i'm gonna test now
---------- Post added at 07:26 AM ---------- Previous post was at 07:11 AM ----------
can you share device tree, kernel, vendor for android 10??
szanalmas said:
GoogleDroid ROM 2019-12-27
FULL open GOOGLE APPS included!
Last stable crDroid based ROM.
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA!
Make sure you have a custom recovery installed (TWRP (or clones) is the preferred recovery)
Boot into recovery
Wipe dalvik, system, data, cust (vendor), cache partitions
If your /data partition secured, maybe need format /data.
Flash Rom (sideload or copy any storage)
Flash Magisk Root (Optional)
Reboot (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 5 minutes!
Turn ON wifi, or mobile network.
Add google account.
After first setting, upgrade all apps in your Google Play!
Refinish settings.
DOWNLOAD ROM
*
Screenshots: LINK
OS source: LINK
ROM OS Version: 10.x Q
ROM Kernel: Linux 3.18.140
ROM info: Q10 system_root partition, Android quota removed (easier to go back to earlier 7.x-9.x ROMs).
Created 2019-12-27 V0 version
Last Updated 2019-12-27
Click to expand...
Click to collapse
Thanks for you great rom again, @szanalmas :good:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
I cant install magisk
please make a original TWRP 3.3.1 like 3.2.1
GonzaloxCOM said:
Thanks for this rom. I have tried it and liked it a lot, except for two problems I have been able to find:
1. VoLTE does not work.
2. DT2W does not work. I've flashed the fix you've put in other topics and it didn't work either.
Thank you for your work and time!
Click to expand...
Click to collapse
Unfortunately, I can't test VOLTE, Hungarian Telekom is filtering phone model the use of VOLTE...
DT2W works for me, no need to fix it. (I built it into /vendor.)
Your welcome!
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Use Canary: LINK
(But i haven't tested Magisk yet.)
Kittendusttvabv said:
I cant install magisk
Click to expand...
Click to collapse
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
cpglbitm said:
Install attached apk(Magisk Manager) file and flash attached magisk zip file it is working 100%
I m using it.
Click to expand...
Click to collapse
I can't install this version either. It always ends with error 1.
Endys111 said:
I can't install this version either. It always ends with error 1.
Click to expand...
Click to collapse
Use orangefox recovery.
cpglbitm said:
Use orangefox recovery.
Click to expand...
Click to collapse
Thanks, already installed.
Can I flash this rom in Redmi Y1
arvind787 said:
Can I flash this rom in Redmi Y1
Click to expand...
Click to collapse
I do not think so.
Y1 Q10 vendor image and Y1 kernel would be nice.
But I don't know for sure.
If the kernel starts, it is possible. If the LCD and touchscreen match, then the cameras are in question.
But I know that the kernel does not have msm8940 support and Y1 uses 8940 as far as I know.
So you probably won't boot the kernel.
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
1.) Can I go from 14.1 to 16.0, or is there a reason 15.1 should be flashed first?
2.) Will any version ≥ TWRP 3.2.x.x official or unofficial work for both Oreo and Pie?
3.) Is this a correct order of operations:
a.) Boot into FOTA recovery
b.) Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage (also, is there a difference between Format Data and Advanced Wipe > Internal Storage?)
c.) Install .zip for LoS from external SD card (or should I sideload via adb?)
4.) Installing gapps is listed as optional, so I can skip installing an opengapps .zip?
5.) Installing addonsu .zip can be done later?
Thank you!
remi_kamahl said:
I have a SGP321 (Pollux LTE | Xperia Tablet Z) on unofficial LineageOS 14.1; the TWRP is the one built into the boot.img (v. 3.1.1).
I'd like to get to 16.0.
Click to expand...
Click to collapse
Hello!
1. Yes, you can.
2. For Oreo and Pie 3.2.x.x and 3.3.x.x are optimal.
3a. Check FOTA recovery version, if <3.2.x.x i suggest updating first.
3b. The difference is, that formatting data doesn't wipe internal storage (as far as i remember).
3c. External SD is better (though it's your choice).
4. If you don't GAPPS you can skip it.
5. Yes it can be done later, but i see no reason to not installing it in 3c.
Also think of root management solution, suitable best for you. Will it be internal root manager of LOS (with the help of addonsu binary) or you will use Magisk, which is more complex and has it's benefits too.
Good luck with flashing!
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
This is specifically what I did:
1. Pushed lineage-16.0-20200511-UNOFFICIAL-pollux.zip & twrp-3.3.1-0-pollux.img to external_sd via adb root
2. adb reboot recovery; verified md5sums via terminal
3. In terminal: # dd if=/external_sd/twrp-3.3.1-0-pollux.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
4. Reboot into FOTA recovery; made sure the version = 3.3.1-0
5. Wipe: Format Data
6. Advanced Wipe: Dalvik + System + Cache + Data + Internal Storage
7. Install the lineage .zip
8. Wipe Cache/Dalvik and reboot system
After the "Sony Xperia" logo pops up, the Lineage boot animation runs for about 2.5 minutes, then the tablet drops into TWRP (RescueParty).
I can restore a 14.1 backup I made before flashing, and the tablet will boot again successfully.
Not sure where to go from here/not sure which specific log file would be necessary—or even available—to diagnose the problem (dmesg, logcat, Console-ramoops).
remi_kamahl said:
Thank you for the info!
I'm getting dropped into TWRP after flashing the latest 16.0 .zip.
Click to expand...
Click to collapse
This happens sometimes. Try to wipe everything ones again and flash LOS via TWRP.
FYI lineage-16.0-20200609-UNOFFICIAL-pollux.zip build is available.