So... CyanogenMod is dead. LineageOS is taking it's place. The ROM is basically CyanogenMod but with changes to the name.
This is completely 'stock' from their source code and will be prerooted (under Developer options in Settings)
Changelog is available at LineageOS Gerrit
There are no apparent bugs, but any bug reports will be welcome.
Gapps are available at OpenGapps.
These should build almost every night
Installation
Download latest release from here
Install it in TWRP recovery
Install the downloaded opengapps package
XDA:DevDB Information
LineageOS/CyanogenMod 14.1 Nightlies, ROM for the Nexus 7 (2013)
Contributors
hazzer
Source Code: https://github.com/LineageOS/
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-01-08
Last Updated 2017-01-08
May you upload some Screenshots? Can I dirty flash? I'm on CyanogenMod 14.1 20161225
Just clean installed, no big difference from Cyanogen,.. Not even the logo.
Everything seams to be working as it did on cyanogen nightly.
Regards,
Me
Thank you
Sent from my Nexus 6 using XDA Free mobile app
Thanks for this, great job.
@hazzer I'd like to grab your image but your website seems down?
Edit: I see it's back up, thanks!
Can you enable your rom to use the built in updater?
Which opengapps do you suggest?
Poslano z mojega ONE E1003 z uporabo Tapatalk
@hazzer there are still two bugs first being hangouts crashes when you try to message someone over unless it's from the notification. This works fine on my other lineage devices. Second is Allo's message sounds use a don't play because it doesn't like the codec. This works in regular Android but seems to be a Lineage specific bug.
@jstsmblaz
pico works fine for me.
Sent from my Nexus 7 using XDA Labs
Edit :
(I use pico for testing. If I need more I use a gapps-config file.)
Lost Root
Root access in Developer Options is greyed out. Only options are Disable and ADB. I am using TWRP 3.0.2. Yes, bootloader is unlocked. I had root with CM 1/25/2016 and when restored to that version, Root returned.
When I installed 1/16/2017, I did not wipe Data.
Am I missing something in Developer Options? Any thoughts?
I stated at the start of this 'project', I am balancing this alongside school work. Unfortunately, it's just become too much to manage alongside time consuming A levels.
This means:
Builds will be less frequent (perhaps once or twice a week)
I'm not going to be available on XDA or IRC very often (if at all)
I apologise I haven't been the best at communicating or fixing issues, but I just didn't envisage having to invest the amount of time I have.
If anyone would like to take over, give me a shout. You can borrow my server for hosting and my blog article if you're willing to learn.
You might see me again sometime around July. Thanks everyone for helping me with an incredible learning process into the depths of Android.
pclewis said:
Root access in Developer Options is greyed out. Only options are Disable and ADB. I am using TWRP 3.0.2. Yes, bootloader is unlocked. I had root with CM 1/25/2016 and when restored to that version, Root returned.
When I installed 1/16/2017, I did not wipe Data.
Am I missing something in Developer Options? Any thoughts?
Click to expand...
Click to collapse
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.
When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.
Members of the Lineage team decided to (by default) remove root from Lineage builds (in the last few days), so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).
If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
SuperSU
hazzer said:
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.
When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.
Members of the Lineage team decided to (by default) remove root from Lineage builds (in the last few days), so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).
If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
Click to expand...
Click to collapse
SuperSU will not root with TWRP, since root is built into TWRP. It just looks for a missing binary,
@pclewis
That's odd. What version of twrp and SuperSU are you using?
I have been using SuperSU with no problems since the cm-20161231 build.
- I didn't try phh, normally I use phh when SuperSU does not work.
Note :
I initially installed the rom, gapps and SuperSU using twrp. - Completely clean install.
Sent from my Nexus 7 using XDA Labs
ipdev said:
@pclewis
That's odd. What version of twrp and SuperSU are you using?
I have been using SuperSU with no problems since the cm-20161231 build.
- I didn't try phh, normally I use phh when SuperSU does not work.
Note :
I initially installed the rom, gapps and SuperSU using twrp. - Completely clean install.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I use TWRP 3.0.2 and it has root built in. Works fine with 1/25/2016 but root is lost with the Linage. I tried SuperSU 2.79, but it is looking for binary that does not exist.
The decision to not support root is not consistent with the Linage teams. I have updated two phones to Linage since CW and both maintain root. I think they need to reconsider. Most of us run TWRP and simply want to root with that.
So im on the 1112017 build and was wondering if anyone else is experiencing screen rotation issues. Is it a software issue or just my tablet being old?
pclewis said:
I use TWRP 3.0.2 ….. I tried SuperSU 2.79
Click to expand...
Click to collapse
Thanks, I wanted to make sure I was using the same files.
I think you may have a few things mixed up.
pclewis said:
The decision to not support root is not consistent with the Linage teams.
Click to expand...
Click to collapse
Lineage changed that. (With the current and newer builds the biggest change the user will see, is selinux enforcing and non rooted. This way clean installs with work with banking apps and pass SafetyNet.)
pclewis said:
I use TWRP 3.0.2 and it has root built in. Works fine with 1/25/2016 but root is lost with the Linage.
Click to expand...
Click to collapse
This has nothing to do with TWRP itself. Lineage removed root access from their builds.
TWRP has root access to modify your device. - All recoveries do.
(Recovery is limited by the developer depending on what they allow the user to do. This is why we can not just install what we want with stock recovery and need custom recoveries like TWRP or Clockwork.)
TWRP will NOT root your rom automatically, you will need to install a su and manager.
SuperSU (Download link in OP of thread.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
SuperSU-v2.79-201612051815.zip
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- - - Now back to your prior post.
pclewis said:
SuperSU will not root with TWRP ..... It just looks for a missing binary,
Click to expand...
Click to collapse
Initially you can not install su binary from the apk.
Install one of the following using twrp. (These are the current SuperSU zip files.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
SuperSU-v2.79-201612051815.zip
All three worked for me regardless.
I installed 20170113 and pico gapps only. Ran through the setup and then dirty flashed 20170116. (Lost root access.) Rebooted into twrp and installed SuperSU-v2.79-201612051815.zip. Rebooted and SuperSU took over root access.
Sent from my Nexus 7 using XDA Labs
20170120 : lineage boot animation?
Sent from my SM-G935F using XDA-Developers Legacy app
ipdev said:
Thanks, I wanted to make sure I was using the same files.
I think you may have a few things mixed up.
Lineage changed that. (With the current and newer builds the biggest change the user will see, is selinux enforcing and non rooted. This way clean installs with work with banking apps and pass SafetyNet.)
This has nothing to do with TWRP itself. Lineage removed root access from their builds.
TWRP has root access to modify your device. - All recoveries do.
(Recovery is limited by the developer depending on what they allow the user to do. This is why we can not just install what we want with stock recovery and need custom recoveries like TWRP or Clockwork.)
TWRP will NOT root your rom automatically, you will need to install a su and manager.
SuperSU (Download link in OP of thread.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
SuperSU-v2.79-201612051815.zip
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- - - Now back to your prior post.
Initially you can not install su binary from the apk.
Install one of the following using twrp. (These are the current SuperSU zip files.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
SuperSU-v2.79-201612051815.zip
All three worked for me regardless.
I installed 20170113 and pico gapps only. Ran through the setup and then dirty flashed 20170116. (Lost root access.) Rebooted into twrp and installed SuperSU-v2.79-201612051815.zip. Rebooted and SuperSU took over root access.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Thanks, I get it. I really don't root the phones I use. I let them update OTA and need the security. The older ones I used to use Titanium and needed root. Now a TWRP BU is fine and I really don't need root I suppose. Thanks for your reply and I understand the logic.
Why do some devices allow root to be turned off and on in developer options for either apps, adb or both?
BTW, just installed 11/20/2017. Seems to work fine and does not have root. I will run this for a while. Thanks again?
Phil
Related
Custom Treble-ready TWRP with F2FS encryption
Features:
Code:
* Treblize button for automated Treble conversion;
* New /vendor mount points in place;
* F2FS encryption and decryption support;
* Upstreamed Lambda Kernel tailored down for recovery.
Downloads:
All prebuilt recovery images are available on Github, the current tag is 08062018.
XDA:DevDB Information
Unofficial Treble-ready TWRP with F2FS encryption, Tool/Utility for the LeEco Le Pro3
Contributors
GalaticStryder, codeworkx
Source Code: https://github.com/GalaticStryder/android_bootable_recovery
Version Information
Status: Testing
Stable Release Date: 2018-04-20
Created 2017-03-11
Last Updated 2018-08-07
Reserved
Reserved
It sounds like if you are already rooted and have twrp installed all you need to download the multi rom apk. Is it that easy to have two three rom to jump back and forth?
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
It sounds like if you are already rooted and have twrp installed all you need to download the multi rom apk. Is it that easy to have two three rom to jump back and forth?
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
MultiROM app will install a new TWRP and the trampoline chainloader.
You can have as many as you'd like to test... Just don't put a password on lockscreen to avoid the credentials bug.
The vanilla TWRP is the latest you can get and has decryption support for testing, so it's a good shot flashing it as well if you're not going to multirom.
Sent from my LEX720 using Tapatalk
Does all rom have to be rooted? I usually like rom to be none rooted for work related email dam app checks for root
Sent from my LEX727 using XDA-Developers Legacy app
toanau said:
Does all rom have to be rooted? I usually like rom to be none rooted for work related email dam app checks for root
Sent from my LEX727 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Only first slot ROM needs root but it's not mandatory as trampoline integrates the Kernel not the system and so won't need root for the basic functions. You'll only need root when using the app to install the modification, manual install doesn't need as I said but it's strongly recommended on first slot.
Sent from my LEX720 using Tapatalk
GalaticStryder said:
Only first slot ROM needs root but it's not mandatory as trampoline integrates the Kernel not the system and so won't need root for the basic functions. You'll only need root when using the app to install the modification, manual install doesn't need as I said but it's strongly recommended on first slot.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Hey @GalaticStryder,
I flashed this Recovery on my x727 but it looks like it's not passing encryption. :crying: Any ideas on what I can do? It asks me to decrypt with password upon booting recovery.
Ascertion said:
Hey @GalaticStryder,
I flashed this Recovery on my x727 but it looks like it's not passing encryption. :crying: Any ideas on what I can do? It asks me to decrypt with password upon booting recovery.
Click to expand...
Click to collapse
Probably system's vold didn't work for decryption. Could you flash previous version on fastboot? I have a script to extract the blobs from system just in case but I wanted to test the built-in feature from TWRP.
I've tested on LineageOS and it worked but my device is Chinese.
Sent from my LEX720 using Tapatalk
GalaticStryder said:
Probably system's vold didn't work for decryption. Could you flash previous version on fastboot? I have a script to extract the blobs from system just in case but I wanted to test the built-in feature from TWRP.
I've tested on LineageOS and it worked but my device is Chinese.
Sent from my LEX720 using Tapatalk
Click to expand...
Click to collapse
Unfortunately, same thing. I am greeted by a Enter Password screen upon booting either after flashing in Fastboot. I am using command below.
Fastboot flash recovery TWRP_zl1_20170302.img
It looks like it'd work perfect but has the encryption issue on x727 variants. My guess is Lineage is also based on the x720 and doesn't encrypt the OS when it boots?
Ascertion said:
Unfortunately, same thing. I am greeted by a Enter Password screen upon booting either after flashing in Fastboot. I am using command below.
Fastboot flash recovery TWRP_zl1_20170302.img
It looks like it'd work perfect but has the encryption issue on x727 variants. My guess is Lineage is also based on the x720 and doesn't encrypt the OS when it boots?
Click to expand...
Click to collapse
Not actually that way, but we can say that. Does any other recovery decrypt properly on your device? Probably recoveries with built-in blobs or blobs extracted from system.
Hello. I have a problem with the kernel of VillarLeg AOKP. The problem is that as soon as I try to change some parameters of some governor you restart the device. I reported the problem to this Centre dev and he said that without MultiROM there are no such problems. Can it be solved?
Inviato dal mio LEX720 utilizzando Tapatalk
Can someone make a zip file that erases lock screen realted files in data/system folder?
TWRP offers file manger only on primary rom, not on other multi roms. So if you have locks on 2nd, 3rd... roms, you are screwed.
If such zip file can be made, it would be easy to fix the mistake/problem.
4K2K said:
Can someone make a zip file that erases lock screen realted files in data/system folder?
TWRP offers file manger only on primary rom, not on other multi roms. So if you have locks on 2nd, 3rd... roms, you are screwed.
If such zip file can be made, it would be easy to fix the mistake/problem.
Click to expand...
Click to collapse
if you swipe rom?
Inviato dal mio LEX720 utilizzando Tapatalk
GalaticStryder said:
Not actually that way, but we can say that. Does any other recovery decrypt properly on your device? Probably recoveries with built-in blobs or blobs extracted from system.
Click to expand...
Click to collapse
The one from the Lineage thread works fine, but it's TWRP 3.0.2.0. I don't see a source for it though.
Ascertion said:
The one from the Lineage thread works fine, but it's TWRP 3.0.2.0. I don't see a source for it though.
Click to expand...
Click to collapse
My TWRP device tree uses Lineage 13.0 to build but different Kernel and no blobs. Could post here the screens asking for passwd and a dmesg inside recovery?
GalaticStryder said:
My TWRP device tree uses Lineage 13.0 to build but different Kernel and no blobs. Could post here the screens asking for passwd and a dmesg inside recovery?
Click to expand...
Click to collapse
Unfortunately, it looks like /system or /storage doesn't mount either so I'm not able to get a dmesg log or take screenshots. This is a picture from my other phone. Is there a different way to grab the log?
In vanilla TWRP_zl1_20170311 if i choose reboot in recovery mode it always reboot in system mode
Can this new TWRP version be used without MultiROM? I currently use the build of codeworkx (https://forum.xda-developers.com/le-pro3/development/lineageos-development-t3553180).
flotux said:
Can this new TWRP version be used without MultiROM? I currently use the build of codeworkx (https://forum.xda-developers.com/le-pro3/development/lineageos-development-t3553180).
Click to expand...
Click to collapse
Sure. TWRP is vanilla, TWRP_multirom (suffix) is for MultiROM which can also be used without MultiROM without problems.
Vanilla: TWRP_zl1_20170311.img
MultiROM: TWRP_multirom_zl1_20170302-01.img
MultiROM stuff is never pushed to Android File Host because I need a static download URL for the MultiROM app and AFH servers aren't static, they shut down every day and switch the file in their servers so it rotates every time.
giogio1 said:
In vanilla TWRP_zl1_20170311 if i choose reboot in recovery mode it always reboot in system mode
Click to expand...
Click to collapse
Seems to boot fine to recovery for me, not encrypted.
Greetings!
The latest beta (v14.1) of Magisk just dropped (Magisk Beta Thread), which is the first release to officially support Pixel (XL).
Before I spend more time investigating TWRP and Magisk combination, please refrain from flashing Magisk through TWRP installed in your boot image (because Magisk cannot get a 100% stock boot backup)
The recommended way to install Magisk on Pixel (XL) are
Fastboot boot this TWRP Image, and flash the Magisk zip
Get a stock boot image (download the full factory image here), and patch via Magisk Manager, then flash the patched boot by fastboot
Once you got over the ""initial pain" and get Magisk installed with proper stock boot image backup, it is very easy to migrate Magisk across OTA updates on Pixel devices.
This thread is not a support thread, all bug reports should be in the Magisk Beta Thread, discussions should be in Magisk General Discussions
------------------------------------------------------------------------------------------------
The followings are for Pixel (XL) developers:
I've written some descriptions on how Magisk works on Pixel devices in my Release Notes for v14.1.
You can directly check MagiskInit's code here. The code is fairly simple so you should get the idea.
However, I'm still fairly new to Pixel development, and I'm not sure how current custom roms and custom kernels workaround the skip_initramfs thing. Instead of trying all custom roms and custom kernels out, I think it would be easier for me to just open a thread and ask
I would like to have some insight from developers whether my Magisk solution can work well with current Pixel development projects. Since all my work is open source, if you have some suggestions to improve my work, please tell me and I'll be really grateful.
I've been waiting for this for a long time.Thank you.
Yaaay! Thank you! I've been waiting for official
Keep up the good work, and congrats!
Works fine here " Android 8.0 "
ElementalX + Magisk 14.1 + Twrp 3.1.1-0 ( Twrp Sticks ) Root also works.
Thanks OP!!!!
WOOOOT WOOOOT
Tylog said:
Works fine here " Android 8.0 "
ElementalX + Magisk 14.1 + Twrp 3.1.1-0 ( Twrp Sticks ) Root also works.
Click to expand...
Click to collapse
How did you flashed them what is your Order ?
I literally booted into recovery (via fastboot) nandroid backed up my boot partition and then flashed magisk so if anything goes wonky I have a backup
tessut said:
How did you flashed them what is your Order ?
Click to expand...
Click to collapse
Stock Boot img , TWRP , MagisK , reboot .
Back to recovery
ElementalX , TWRP , MagisK , reboot.
Done.
Hello
I am currently on stock , so for me the steps will be :
Fastboot TWRP , install Magisk and reboot
Reboot to recovery
EX kernel , TWRP, Magist and reboot
Correct ?
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
I'm still on a custom rom based on 7.1.2 and all i had to do is flash magisk 14.1 zip using twrp RC2. Everything works fine. Had to manually install magisk manager tho.
chowtom said:
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
Click to expand...
Click to collapse
No problem here was 8.0 stock latest installed 14.1 and everything works.
If i'm already rooted and on Su and SuHide, how does one go about installing Magisk
Rockstar! Nice to be certified once again...
Thank you
---------- Post added at 01:13 PM ---------- Previous post was at 01:08 PM ----------
Nexus6pMyPhone said:
If i'm already rooted and on Su and SuHide, how does one go about installing Magisk
Click to expand...
Click to collapse
Hello,
Follow the instructions on the SULite site for removal and also uninstall the SU app itself. Download the full September Oreo zip and remove the -w from the bat file. Then execute the bat file from bootloader which will flash the full Oreo image. This will give you a new boot image that is not rooted and one Magisk can patch.
Cheers
chowtom said:
Everything works fine except mobile network connection after install 14.1 beta.
Can make/receive call, but can't connect to mobile network.
My install step is:
1.flash-all with opr3 full package.
2.Setup Pin code. ( mobile network works)
3.Flash both boot slot with stock boot.img. (mobile network works)
4.Boot to twrp 3.1 and install ElementalX 2.01 than reboot. (mobile network works)
5..Boot to twrp 3.1 and install Magisk 14.1beta than reboot. (mobile network fail)
6.Full uninstall Magisk with Magisk Manager than reboot. (mobile network works again)
Anyone has the same problem?
Click to expand...
Click to collapse
Yep, worked fine after flashing rom then magisk. Rebooted to flash EX kernel, after coming back magisk manager said it wasn't installed. Rebooted, flashed magisk again, came back and I had no mobile network connection, and my wifi connection appeared to work fine but in actuality nothing loaded. Also, camera was totally blank.
Update: Magisk 14.2 (just released) seems to fix issues with networking and camera. Running EX and Magisk together without issue, except...
SafetyNet check in Magisk shows both checks as false, and I can confirm as I'm unable to sign into snapchat lol.
One more update: Netflix and root checker behave how they should with Magisk hide enabled, but SafetyNet test, Magisk's SafetyNet checker, and Snapchat don't. Have tried turning off USB debugging, Magisk Hide box is checked, and SELinux is Enforcing. Just trying to be thorough with info I give.
Are you able to use the sky go app with Magisk 14.1 on the Pixel? Suhide fails to hide root from sky go
any one have the issue where you don't have magisk manager installed after flashing 14.2? or am i doing something wrong?
[email protected] said:
any one have the issue where you don't have magisk manager installed after flashing 14.2? or am i doing something wrong?
Click to expand...
Click to collapse
you have to download and install the apk separately
EDIT: hm... not seeing a download for the 5.3.5 version of the app :S
EDIT 2: https://github.com/topjohnwu/MagiskManager/releases
there should be version 5.3.5
WarningHPB said:
you have to download and install the apk separately
EDIT: hm... not seeing a download for the 5.3.5 version of the app :S
Click to expand...
Click to collapse
yup, I didnt see it either so i assumed it must install apk while flashing like it used to.
i dont see any apk to download and i dont see anything mentioned about this.
attaching recovery log. hope it helps @topjohnwu
[email protected] said:
yup, I didnt see it either so i assumed it must install apk while flashing like it used to.
i dont see any apk to download and i dont see anything mentioned about this.
attaching recovery log. hope it helps @topjohnwu
Click to expand...
Click to collapse
apologies i edited my post a few times you might not have seen the second one there's a download link on the git hub
EDIT 2: https://github.com/topjohnwu/MagiskManager/releases
there should be version 5.3.5
Click to expand...
Click to collapse
Hello community, so I have successfully done it as in title,
but I still have some steps which not very clear and would hope xda community could enlighten me about it.
so my steps are like this:
1. unlock bootloader with Mi unlock tool
2. flash stock MIUI10.3.8 android 9 rom
2.1 transfer 'Disable force encryption treble' and 'Magisk 19.4' to phone storage
3. fastboot, adb flash twrp 3.2.3-1, boot into twrp 3.2.3-1
4. install the 2 zip files in twrp
reboot system, and it went through..
I know I was lucky, so got some questions here:
1. TWRP mention it's necessary to do dm-verify disable. but I review seems I never did it and got no warning message or error about it. I wonder reason for this? is it because I never modify system partition anyway.
2. 'Disable force encryption treble' file has Magisk built in. I was surprised to see it in log, but nevertheless went to flash higher version 19.4 file. all went through I wonder any issue could be caused from this.
3. I review and realize didn't do the 'wipe data/cache' step before install the 2 zip files. It went through without issue surprisingly.. I wonder the reason for this.
3.1 and if I follow the guide to wipe data and cache first, the 2 zip files will still be there? kind of weird not sure how the emulated storage works..
3.2 Is this 'Disable force encryption treble' file step necessary? I read TWRP can auto settle this encryption thing in newer versions.
and I also wonder whether it means my current phone state is 'not encrypted' state. I check in settings 'encrypt with lock screen password' is off.
Thanks in advance guys
poor me no reply and magisk hide to be punched by safetynet enhance..
phileasx said:
poor me no reply and magisk hide to be punched by safetynet enhance..
Click to expand...
Click to collapse
You followed and old guide.
The latest stable for the poco is 11.0.6 (Android 10)
and the latest magisk is 20.3
Dfe is needed only if you don't want encryption. Otherwise it's not.
The question is what do you want to do.
Custom ROMs/stock ROMs, Android 9/10 there's a different procedure for each one.
sotosgolf said:
You followed and old guide.
The latest stable for the poco is 11.0.6 (Android 10)
and the latest magisk is 20.3
Dfe is needed only if you don't want encryption. Otherwise it's not.
The question is what do you want to do.
Custom ROMs/stock ROMs, Android 9/10 there's a different procedure for each one.
Click to expand...
Click to collapse
Thanks for your reply. Yep I used an older version as I needed something proven working. I'm fine with just MIUI10 android 9 and magisk 19.x.
Do you know about the Dm-verify thing, is it optional also?
phileasx said:
Thanks for your reply. Yep I used an older version as I needed something proven working. I'm fine with just MIUI10 android 9 and magisk 19.x.
Do you know about the Dm-verify thing, is it optional also?
Click to expand...
Click to collapse
Keeping dm-verity is an extra barrier for your device to not be exploited.
If you don't have any reason to turn it off, leave it as it is.
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.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 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.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it 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: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
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.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 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
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.
Hello everyone,
I am trying to (completely) unroot the lineageos version of Android x86. The only thing I need is an old pc can run Android without root since the app I am about to use does not work if the device (android) is modified. I tried several different ways:
DIsable root in settings
Physically remove su binary
Using Gearlock to install custom recovery then able to install Magisk, but could not hide the root (Safetynet) using Magisk
None of them works in order to run the app.
Would some one have experience on this? Thank you in advance.
2. Have your removed all of it?
https://download.lineageos.org/extras
How about using some other build?
https://www.xda-developers.com/tag/android-x86/
CXZa said:
2. Have your removed all of it?
https://download.lineageos.org/extras
How about using some other build?
https://www.xda-developers.com/tag/android-x86/
Click to expand...
Click to collapse
Thanks for your reply. I already tried to flash the su removal addon from lineageos but the thing is, it is unable to have TWRP with android x86 for now (as I know), so the only custom recovery is Gearlock but it is failed to flash su removal via Gealock
Android x86 only has two releases of lineageOS which is 13.0 and 14.1. I tried both and same issue.
Thanks again
lnguy193 said:
Thanks for your reply. I already tried to flash the su removal addon from lineageos but the thing is, it is unable to have TWRP with android x86 for now (as I know), so the only custom recovery is Gearlock but it is failed to flash su removal via Gealock
Android x86 only has two releases of lineageOS which is 13.0 and 14.1. I tried both and same issue.
Thanks again
Click to expand...
Click to collapse
Signed zips can be flashed in stock recovery...
Here are the files that it removes...
/system/system/addon.d/51-addonsu.sh
/system/system/bin/su
/system/system/etc/init/superuser.rc
/system/system/xbin/su
Why it has to be lineage? You could get pie, also bliss has it.
https://www.android-x86.org/changelog.html
CXZa said:
Signed zips can be flashed in stock recovery...
Here are the files that it removes...
/system/system/addon.d/51-addonsu.sh
/system/system/bin/su
/system/system/etc/init/superuser.rc
/system/system/xbin/su
Why it has to be lineage? You could get pie, also bliss has it.
https://www.android-x86.org/changelog.html
Click to expand...
Click to collapse
For some weird reasons the app I will mainly use always work only the lineage version, but crashed on others. I haven't tried pie and bliss yet! I just only removed the 2 su binaries in /bin and /xbin. I will try to reflash or remove the other two files that you recommended. Thanks
lnguy193 said:
For some weird reasons the app I will mainly use always work only the lineage version, but crashed on others. I haven't tried pie and bliss yet! I just only removed the 2 su binaries in /bin and /xbin. I will try to reflash or remove the other two files that you recommended. Thanks
Click to expand...
Click to collapse
Yes same here, I am also looking for an unrooted lineage OS(works well), or any other unrooted Android OS.
Can anyone help finding a stable unrooted OS.