Database Develop

[ROM][UNOFFICIAL][microG][root][OTA][WireGuard][enchilada][9] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This build includes microG, a free and open implementation of the Google Play Services Framework. It allows applications calling proprietary Google APIs to run on AOSP-based ROMs like Replicant and LineageOS. Acting as a replacement for the closed-source Google Apps (GAPPS), it is a powerful tool to reclaim your privacy while enjoying Android core features such as Google Cloud Messaging.
It also includes WireGuard, a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.
I probably won't do other types of builds unless somebody has a really terrific suggestion. These builds exists for my own convenience and I thought I'd share it with the XDA community where I've been lurking and leeching for years.
Features
Embedded root (can be enabled in Developer Settings)
Restricted (system-only) signature spoofing
microG (FakeStore, GmsCore, GsfProxy, legacy mapsv1 implementation)
Mozilla Location Services + Nominatim for network-based location
FDroid (+Privileged Extension)
WireGuard-enabled LineageOS kernel
Monthly automagical OTA updates (signed builds, https)
Reporting Bugs
I just build using the latest official LineageOS (also see this thread), wireguard patch, TheMuppets proprietary files and microG prebuilts. Report any "regular" bugs to those threads and/or Git pages unless you're sure the problem is unique to these builds.
Initial installation
NOTE: TWRP gets replaced by the stock recovery every time you install a ROM zip. Either use fastboot to boot TWRP or flash the TWRP zip file every time after you flash a ROM zip.
OnePlus firmware must be installed on your device on both A/B slots. Hence the instructions below tell you to flash OxygenOS twice.
Wipe system, data and cache.
Flash latest OxygenOS using TWRP.
Reboot to TWRP
Flash OxygenOS again using TWRP.
Reboot to TWRP
Flash the newest build using TWRP.
Reboot to TWRP.
Flash the newest build using TWRP again.
Reboot and enjoy!
OTA Updates
For OTA updates, use the built-in Updater app. Everything should JustWork(TM) without any TWRP/recovery magic.
Downloads
https://lineage.darwinkel.net/builds/full
Delta/partial updates are not supported.
I recommend Aurora Store if you want to download and install apps from Google Play.

Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?

Cygnust said:
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Click to expand...
Click to collapse
This build has a free software alternative to opengapps baked-in. This ROM is probably not what you're looking for if you want to install the regular Google Play Services. No clue about Magisk or a custom kernel surviving OTA.

Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?

Tomatot- said:
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Click to expand...
Click to collapse
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!

perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?

AndroidBolder said:
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
Click to expand...
Click to collapse
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?

Master One said:
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Click to expand...
Click to collapse
I'm not that fond of Magisk and neither are the LineageOS devs. I don't use any apps that use SafetyNet and this works for me personally (I mainly use root for Yalp Store and WireGuard). I have, however, tested it. I enabled DroidGuard and microG's SafetyNet attestation and tested it with an app. Unfortunately, it didn't seem to pass even with root disabled in developer settings. Magisk Hide might help, though.
Toni Moon said:
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
Click to expand...
Click to collapse
I'm pretty sure you can install a Google Play Store APK, but you would have to disable or remove FakeStore for it to work, I think. I personally use Yalp Store to download apps from Google Play (including paid ones).
EDIT: download speeds have been fixed.

1 Question, how to get snapchat and chromecast work?

TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I don't use either of those apps, no clue.

Can I use blue Spark twrp?

noky76 said:
Can I use blue Spark twrp?
Click to expand...
Click to collapse
You can.

@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.

@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?

This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?

Master One said:
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
Click to expand...
Click to collapse
Sounds really interesting, but the way you're putting it, it seems somewhat unstable/unreliable. VoLTE works fine with my carrier so I have no way to test it. If multiple people can confirm it works without causing instability then I'll consider changing build.prop.
Master One said:
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
Click to expand...
Click to collapse
I presume addonsu remove would work, no clue if the 15.1 version works on Pie. Did a quick search but I can't find one for LOS16. Bingo! uploaded by Luk1337, one of the LOS devs.
admiralderp said:
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Click to expand...
Click to collapse
Like most custom roms slightly worse than OxygenOS, but completely fine otherwise!

Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).

nksonfire said:
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
Click to expand...
Click to collapse
It works on most custom ROMs as long as you use Maps 9.82.1

Thank you a TON for providing these builds. This finally gives me a path to move off of OxygenOS. Installed, tested, everything working beautifully *including VoLTE and VoWiFi* (on U.S. T-Mobile).
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I have managed a way to get at the very least Snapchat working on this ROM.
Flash as normal.
After that, flash Magisk from TWRP.
Add the *Nanodroid*, not official, microG repo to F-Droid and install the DroidGuard Helper from there. You'll have to web-search "nanodroid fdroid repo" as I cannot provide external links on this new account.
(I've not tested any of this with the official repo's DroidGuard Helper, but there are issues on microG's Github repo suggesting that SafetyNet will only pass with Nanodroid's version of DroidGuard Helper.)
Install a file manager with root capability (such as Amaze on F-Droid) and navigate to /data/app where you will find the DroidGuard Helper under "org.microg.gms.droidguard-randomstringhere". Move this folder to /system/priv-app and reboot.
Make sure SafetyNet is on in microG Settings and ensure it is using the official server (by hitting the three dots in the corner, selecting Advanced and selecting "Use official server".)
Enable Magisk Hide in Magisk Manager and enable hiding for Snapchat and DroidGuard Helper.
Try SafetyNet attestation under Magisk Manager. Hopefully both checks should pass.
Enjoy.
I did a test OTA (the current 1/30/19 version is available there, so I just downloaded and installed it again) and the only changes to be made were to re-flash TWRP and Magisk then re-install DroidGuard Helper and move it to /system/priv-app. All microG and Magisk Manager settings were retained.

As your post says, I have a really terrificant suggestion.
Why don't you try to port Sailfish Os on op6?
If you think that my suggestion is not terrificant I will understand. I would like to port it but I can't do that. For many reasons. Bye and congrats for this build. it looks like great.
Ceers

[CLOSED] [ROM][CUSTOM][O][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte)

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of our LOS 15.1 builds.
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
The /e/ app store has been removed completely (read FAQ #0 why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules defined by /e/.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is PIE (Android 9) RIL will not work in this ROM. I am trying to fix that currently but while it works when your STOCK firmware/bootloader stack is on Oreo or earlier it stops working when you ever upgraded to pie
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
Latest TWRP build based on Oreo sources (build by myself) can be found here: click
Do a full Nandroid backup before doing anything!
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/oreo/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
nailyk
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-oreo_custom, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: NOUGAT/OREO only - if you have stock PIE installed RIL won't work!
Based On: Lineage OS
Version Information
Status: Beta
Created 2020-08-05
Last Updated 2020-09-09

-
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
TL;DR answer is: who knows...
Background:
/e/ points to LineageOS requirements which need to be met first. LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
No I personally do not have any plans in going official atm. That might change though.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-

Reserved

Encryption of storage works?

jw96 said:
Encryption of storage works?
Click to expand...
Click to collapse
Haven't tested yet
Sent from my OnePlus 7T Pro using XDA Labs

I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.

Morceaux said:
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Click to expand...
Click to collapse
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-

steadfasterX said:
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
Click to expand...
Click to collapse
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?

Morceaux said:
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Click to expand...
Click to collapse
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-

steadfasterX said:
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
Click to expand...
Click to collapse
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)

Morceaux said:
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Click to expand...
Click to collapse
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-

steadfasterX said:
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)

Morceaux said:
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Click to expand...
Click to collapse
https://sfirmware.com/samsung-sm-j530f/

goodjob

steadfasterX said:
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged

jaggedN said:
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
Click to expand...
Click to collapse
Oof .. Well i don't have much time atm but i need that phone as my navigation device for my motor bike. so i need to fix it
Sent from my OnePlus 7T Pro using XDA Labs

New eOS v1-oreo build *20200909* has finished!
Changes:
- kernel: commits
- Device tree: commits
- Common Device tree: commits
Download: see OP
Known issue with the OTA Update!
Unfortunately it will work with the next update first. There was a missing entry in the fstab causing the install to fail. You can still use the Updater to download the package though!
1. Open Settings —> System
2. Expand Advanced & select Updater
3. Refresh if not listed already
4. Download
5. Reboot to TWRP
6. browse to /data/lineageos_updates/ and select the zip from here
BREAKING NEWS
I've decided to create a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
The second one will also show sha256sums of every build for those who need it.
.-

No more OREO builds!
The reason is that almost everyone has flashed stock PIE in the meanwhile and I switched to Android 10 already. A10 works great so far and so backporting whatever is needed is not worth it.
Check it out: j5y17lte - Android 10 / Q
Thread closed.
.-

[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL

{
"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"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9

Going to try it now.
Thank you!

npjohnson said:
​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?

ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.

Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team

What is the official way to obtain root access? or is there one any more?

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed

adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!

cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.

First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!

Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.

Haven't been able to use twrp since Android 9 far as i know

lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.

Nevermind, user error.

ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.

npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1

ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.

How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.

ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.

[11][OFFICIAL] CarbonROM | cr-9.0 [fajita]

{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot fajita-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-fajita-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
​

FINALLY! YES! WOOHOO!

I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever

void4ever said:
I just want to confirm based on the top post, that for the 6T we are indeed using the A10 base since that is still the "Latest Stable Build"?
Void4ever
Click to expand...
Click to collapse
Indeed, the current required base is the latest Android 10 stable.

Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.

Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
void4ever said:
Thx @Myself5 I appreciate the info. Hopefully I don't run into the same Android Auto issues I did with 8.0. However to be 100% fair I ran into those issues with multiple other roms as well. Something to do how OxygenOS handles the detection of USB vs ASOP I assume on the 1+ hardware. Literally the only thing thats kept me from running custom roms.
Click to expand...
Click to collapse
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look

Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
I would be happy to provide logs if/when i run into an issue.
I can give some background right now, which may not be very useful since we don't know if 9.0 is going to have the same issue. I don't recall if it was you @Myself5 or the dev from Paranoid, but we had a short discussion about this a while ago. If I recall one of you suggested it might be the modules you were using from the ASOP libs maybe? I'd have to go search through the old threads.
The only car I have to test with is my 2019 Traverse. AA works perfect everytime with stock Oxygen, and the only other ROM I ever ran into that seemed to work fine was AOSIP, however the rom itself was unstable on my hardware and I had to remove it due to my alarm not going off cuz the phone would crash overnight. So perhaps there's something in the way they implemented USB detection.
The last rom I tested (I forget which) I noticed that the phone wasn't even popping up the USB notification (where you can select File Transfer, USB tethering, MIDI, PTP, No data transfer) when connecting to the car.
Anyways this is far more info than we need until I can test it. Hopefully this weekend if not sooner.

Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?

Mckillagorilla said:
Bit rusty running custom Rom
I was able to install perfectly fine, running perfectly just a bit iffy on Rooting afterward.
Can we install Magisk through CarbonRecovery? Do we need to keep the Carbon Recovery as the defacto Recovery for this Rom? Can I go back TWRP?
Click to expand...
Click to collapse
Yes you can install Magisk through Carbon Recovery. TWRP should be just fine, especially as the Recovery isn't used for updates etc as that is all done through Seamless updates in CarbonDelta on the system itself.

When i installed the rom i had to install the gapps after i was done with the phone setup. Otherwise the Android Setup would crash as soon as android booted.
The screen would then go cracy (blinking button icons) and I couldn't do anything.
I also can't update using the ota update.
Just tells me "Update could not be installed".
Other than that it works great
Edit: I didn't see the message about the video playing fix in some apps.
Updated from to latest version and now all videos work

Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
I havn't had issues with Android Auto in the VW Discover Pro on any devices so far. Unfortunately the only car I can test it with, and the Emulator is working fine as well. If it's still broken for you I'd greatly appreciate if you can provide logs of the issue and I'll try to take a look
Click to expand...
Click to collapse
Thank you for this great rom .
I had a problem with Android Auto, It's solved but I report if someone faces the same issue.
With Nikgapps basic on cr-9.0, Android Auto was not working: the phone was detected by the car (Peugeot 2008 from 2018), but when I initiated the connection the phone hangs and freeze, nothing happens on the car and I often had to reboot the phone.
It was an error related to usb permission in the logs.
It was solved using the stock package of Nikgapps (the problem is reported on other other devices as well). I was using the basic package of nikgapps on carbonrom cr-8.0 without problem, I don't know what changed that made the stock package needed.
I did not try for other gapps providers, but at first glance, this problem doesn't seems related to the rom itself but more to the gapps package.

My facebook and insta videos r not playing.. can't able to see them .. how to fix it

Prabhuraj 0 said:
My facebook and insta videos r not playing.. can't able to see them .. how to fix it
Click to expand...
Click to collapse
By updating to the latest build as mentioned a few posts above yours.
On that note:
I've found and fixed an issue where the device would not be reported as an A/B device properly which resulted in the integrated updater being broken. It will be fixed in wednesdays build (along with August ASBs) but you will need to manually update (through recovery) to that build.

So I haven't had a chance to install because I had to be OnCall for my job this week, no messing with my phone...... BUT that may have been a blessing?
I see the Stable A11 was released today for the 6 and 6T. Are there plans to rebase Carbon 9.0 to this?
Void4ever

Solid ROM! I haven't used Carbon since the Epic 4g phone. I'm running latest without Gapps, and I have to ask is there a better camera available outside of the play store? I know its a long shot but thought I'd try.

Google Camera, just google up gcam ports

only reason fr nt using Carbon is there is no
face unlock

Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks

Wishmasterflo said:
Why is there no new download link from 25/8 for fajita. I can see the update on my phone but I want to flash the update.zip file from recovery.
Thanks
Click to expand...
Click to collapse
The last version also took a while (~4-7 days, not sure) until it was available on the website

I see it now. Probably didn't wait long enough!
Also @Myself5 is this by chance based on A11 now, or still A10?

Question Y700 ROMs

Hi Y700 owners, of future owners
So to have a dedicated forum for the Y700, we need to open threads in other "remotely related forums" and have some interesting discussions.
Therefore opening this one as an attempt to get a little more organized Y700 posts and, especially, to get visibility and get our own forum
I'm not too much familar in 2022 with ROMs and other stuff (i was playing with those things a few years back and a lot has changed since), but i understand there are some GSI (generic system image) ROMs that are available, from what i understand, for several devices that don't have a dedicated ROM. That is something new to me i have to say.
@FIERA03 , i hope you don't mind me quoting you here, but as you have done some interesting testing, to give it more visibility, i'll paste your results here from another thread.
I have flashed a lot of GSI on this tablet so far.
Here is a summary of the bugs and other issues that I have noticed in them.
※All of them are Android 12L except for the ones without special notes.
①Corvus OS, Descendant OS...Lock screen does not rotate. Probably because it is based on Google Pixel ROM. Corvus also does not have face unlock.
②Ancient OS(Android 12.0)...Lock screen does not turn to landscape. Also, when I change the username or photo at the top of the settings, the settings app crashes. Also note that the settings app crashes if you change the username or photo above the settings.
③Proton AOSP...When I restarted to set up Magisk, the settings app repeatedly stops. Deleting app data and cache had no effect.
④Havoc OS(Android 11)...The startup logo does not appear in the first place and comes back to the bootloader.
⑤Superior OS...It started, but the FPS dropped extremely. I judged that it is difficult to use regularly.
⑥Pixel Experience…The screen is still not landscape. Also, it seems that it is not optimized for tablets any more than Descendant, and when I call the dock while launching an app(the feature of 12L), the icon looks like it has been split in half.
⑦All of NipponGSI...Like Havoc OS, it comes back to the bootloader. It may be a bad compatibility.
⑧Lineage OS…There was a switch "Rotate lock screen" in the settings. But I don't use it, because the "su" binary is still in the root file and can't delete it ,so interferes with SafetyNet.
⑨Arrow OS...This also allows the lock screen to be turned landscape and is also very light. Although the lack of face unlock is a demerit (LSPosed module didn't work→https://forum.xda-developers.com/t/11-universalauth-face-unlock-for-all-roms.4419343/).But there are few complaints for me. So I'm using it regularly.
I'm sorry if it's hard to read because I'm not good at English. Thank you.
Click to expand...
Click to collapse
Thanks a lot @FIERA03 for these information. Very valuable for anyone interested in flashing its Y700.
This was your status on May 22nd.
Of course you need to unlock the bootloader, which you can do after entering IMEI and email at this website: https://www.zui.com/iunlock (Thanks for @NisseGurra for posting this link in another thread).
Are there any other interesting experience that anyone can share with either those GSI or other images?
Thanks a lot for your contributions to have some kind of Lenovo Legion Y700 community started

For the GSI Y700 users, there is an treble app update from phh (attached). It enable magnetic cases wake and close screen.

I'm pleased to report that I have tested a ROM that I had not tried before and have confirmed that it meets all of my requirements.
The Nazim's crDroid GSI is the best ROM for the Legion Y700 (I didn't like the logo, so I didn't use it until now).
Below is a list of the outstanding features of this ROM.
・It doesn't have a fixed lock screen in portrait orientation like Corvus or Descendant.
・It doesn't contain superfluous and undeletable files like "su" like Lineage.
・It includes face unlock unlike ArrowOS (by the way, crDroid and ArrowOS are built by the same person, I wonder why he didn't include face unlock in the latter).
・It doesn't cause any noticeable glitches like ProtonAOSP or Pixel Experience (it still runs the Alpha version of the Lawnchair Magisk Module without crashing).
・This ROM is so customizable that you don't even need the Magisk or LSPosed module that you have been using. The status bar can be customized, and even the volume step can be adjusted.
・The default wallpaper of this ROM is very beautiful (my personal opinion ).
・It can pass SafetyNet. most other 12L GSIs could not do this.
Of course, this ROM alone is still not enough in some areas, but I think that can be improved with the App placed by Mr. @NisseGurra and the modules in this link
(Click the "Magiskモジュールのダウンロード" button to jump to Google Drive and download it). This module enables automatic brightness change of the screen, and also allows assignment to the right switch (originally the game mode activation switch) using the Button Mapper.
I hope all Y700 users will use this ROM. Thank you.

Thanks for the report Fiera03.
How about streaming services with GSI ROMs? Netflix and other are working fine in HD?

I don't know because I'm not registered with Netflix, but according to Mr. SMART ASW (who I showed in the module link), you can get HD playback if you forge the model name using MagiskHide Props Config (he forged a Yoga Tab to a Pixel 6). However, he says that doing this may cause DT2W to stop functioning. So be careful.

I get 1080 at amazon prime, can seem to get 4 k tho

NisseGurra said:
I get 1080 at amazon prime, can seem to get 4 k tho
Click to expand...
Click to collapse
Well, my Galaxy tab s6 has the same resolution and doesn't get 4k, which makes sense since these devices aren't 4K (1440p is a good fit in YouTube but it's not an option in prime video if I'm not mistaken)

@FIERA03 can you provide an instruction "how to install crDroid to Y700"?

vanaduym23 said:
@FIERA03 can you provide an instruction "how to install crDroid to Y700"?
Click to expand...
Click to collapse
OK. here's a installing process.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the CrDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while CrDroid will start.
If you have any stumbling blocks, please ask me again.

By the way, is anyone using Phusson's AOSP with Y700?
I want to know if it has been improved, because I had a bug before and the screen didn't come on after sleep.

FIERA03 said:
I'm pleased to report that I have tested a ROM that I had not tried before and have confirmed that it meets all of my requirements.
The Nazim's crDroid GSI is the best ROM for the Legion Y700 (I didn't like the logo, so I didn't use it until now).
Below is a list of the outstanding features of this ROM.
・It doesn't have a fixed lock screen in portrait orientation like Corvus or Descendant.
・It doesn't contain superfluous and undeletable files like "su" like Lineage.
・It includes face unlock unlike ArrowOS (by the way, crDroid and ArrowOS are built by the same person, I wonder why he didn't include face unlock in the latter).
・It doesn't cause any noticeable glitches like ProtonAOSP or Pixel Experience (it still runs the Alpha version of the Lawnchair Magisk Module without crashing).
・This ROM is so customizable that you don't even need the Magisk or LSPosed module that you have been using. The status bar can be customized, and even the volume step can be adjusted.
・The default wallpaper of this ROM is very beautiful (my personal opinion ).
・It can pass SafetyNet. most other 12L GSIs could not do this.
Of course, this ROM alone is still not enough in some areas, but I think that can be improved with the App placed by Mr. @NisseGurra and the modules in this link
(Click the "Magiskモジュールのダウンロード" button to jump to Google Drive and download it). This module enables automatic brightness change of the screen, and also allows assignment to the right switch (originally the game mode activation switch) using the Button Mapper.
I hope all Y700 users will use this ROM. Thank you.
Click to expand...
Click to collapse
Its been a few months since you made this post, thank you!
I was wondering if you have any updates on this. Is this still your recommended Rom?
If not, which one are you running now?
I noticed the developer of crdroid has a lot bunch of newer builds available, have you tried those?
Thanks for your input keeping this device alive

stokedcrf said:
Its been a few months since you made this post, thank you!
I was wondering if you have any updates on this. Is this still your recommended Rom?
If not, which one are you running now?
I noticed the developer of crdroid has a lot bunch of newer builds available, have you tried those?
Thanks for your input keeping this device alive
Click to expand...
Click to collapse
I've also tested several Android 13 ROMs, and none of them seem to be optimized for tablets yet (at 1st I found a severe bug in the standard launcher).
Therefore, I still consider crDroid GSI's 8.13 to be the most suitable ROM for this device. The next best is Mr. AndyYan's LineageOS (Secure), which is easy to use.

@FIERA03 could I ask where you found your IMEI on this device? I got the stock rom switched over to english but I cannot find the IMEI anywhere :/

stokedcrf said:
@FIERA03 could I ask where you found your IMEI on this device? I got the stock rom switched over to english but I cannot find the IMEI anywhere :/
Click to expand...
Click to collapse
Is there a sticker writing device's information on the tablet ?
The number under the barcode is the S/N=IMEI.

Anyone else notice the unlocking website no longer accepts the serial number?
{
"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"
}

FIERA03 said:
OK. here's a installing process.
①Unlock bootloader with SN.img. This procedure is the same as for other Lenovo tablets such as the Xiaoxin Pad, so I'll skip this step.
②Put the tablet in Fastboote"d" mode. I usually enter this mode by pressing and holding the volume down and the power button to activate fastboot mode, then selecting "Enter Fastboot" from the recovery menu.
③You have to download the arm64 version from the CrDroid GSI link that the text my first post in this thread. I recommend arm64-BgN-vndklite.
④I will assume that you have already configured Android Studio. Start a command prompt and type the command fastboot flash system (the img file you downloaded and unzipped) You can also do this by dragging and dropping the img file into the window before flashing system.
⑤Operate the tablet; proceed to Enter recovery→Wipe data/factory reset to initialize the tablet's data. Otherwise, it will freeze at the title.
⑥Reboot system now and after a while CrDroid will start.
If you have any stumbling blocks, please ask me again.
Click to expand...
Click to collapse
Hi, I am a noob who's trying to try update the rom as per your instruction. However my y700 is came with 'global rom' which is installed by Aliexpress seller. It seems the machine already unlocked. Is it ok/safe to follow your instruction guide even it's not ZUI original chinese rom? I would much appreciated. Currently Having trouble to having google playstore error on games, and experiencing strangely lagging speed on loading microSD card.

stokedcrf said:
Anyone else notice the unlocking website no longer accepts the serial number?
View attachment 5768701
Click to expand...
Click to collapse
I have encountered this too when I was thinking to unlock my y700

hi, i success install rom following your guide, can you help me to root the device
FIERA03 said:
I'm pleased to report that I have tested a ROM that I had not tried before and have confirmed that it meets all of my requirements.
The Nazim's crDroid GSI is the best ROM for the Legion Y700 (I didn't like the logo, so I didn't use it until now).
Below is a list of the outstanding features of this ROM.
・It doesn't have a fixed lock screen in portrait orientation like Corvus or Descendant.
・It doesn't contain superfluous and undeletable files like "su" like Lineage.
・It includes face unlock unlike ArrowOS (by the way, crDroid and ArrowOS are built by the same person, I wonder why he didn't include face unlock in the latter).
・It doesn't cause any noticeable glitches like ProtonAOSP or Pixel Experience (it still runs the Alpha version of the Lawnchair Magisk Module without crashing).
・This ROM is so customizable that you don't even need the Magisk or LSPosed module that you have been using. The status bar can be customized, and even the volume step can be adjusted.
・The default wallpaper of this ROM is very beautiful (my personal opinion ).
・It can pass SafetyNet. most other 12L GSIs could not do this.
Of course, this ROM alone is still not enough in some areas, but I think that can be improved with the App placed by Mr. @NisseGurra and the modules in this link
(Click the "Magiskモジュールのダウンロード" button to jump to Google Drive and download it). This module enables automatic brightness change of the screen, and also allows assignment to the right switch (originally the game mode activation switch) using the Button Mapper.
I hope all Y700 users will use this ROM. Thank you.
Click to expand...
Click to collapse

aisidetpipo said:
hi, i success install rom following your guide, can you help me to root the device
Click to expand...
Click to collapse
This guide (use google translate for english) should work: https://smartasw.com/archives/15704

Hi everybody.
I've also bought now the Y700 (to replace my old MiPad 4) and installed as recommended the crDroid image from Nazim. Really like it a lot, only miss adaptive brightness.
I've therefore tried to install the Magisk module from smartasw (guide is here).
Does is work for you @FIERA03 or anybody else?
The re-mapping for the game button has been successful, but I cannot see any automatic changes in the brightness nor any additional settings entry (not sure if such a thing should be expected).
It seems that the overlay apk cannot be installed correctly. Tried to debug using this and it has a problem with the idmap:
Code:
TB-9707F:/ $ cmd overlay dump me.phh.treble.overlay.lenovo.y700
me.phh.treble.overlay.lenovo.y700:0 {
mPackageName...........: me.phh.treble.overlay.lenovo.y700
mOverlayName...........: null
mUserId................: 0
mTargetPackageName.....: android
mTargetOverlayableName.: null
mBaseCodePath..........: /system/product/overlay/treble-overlay-lenovo-y700.apk
mState.................: STATE_NO_IDMAP
mIsEnabled.............: true
mIsMutable.............: false
mPriority..............: 15
mCategory..............: null
mIsFabricated..........: false
}
IDMAP OF me.phh.treble.overlay.lenovo.y700
<missing idmap>
Does it work for any of you guys?