Database Develop

[OFFICIAL] [NIGHTLIES] 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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 16.0, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo Firmware
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-03-03
Last Updated 2020-01-12

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071

{
"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.
Known issues: (as of May 19, 2020)
- FM Radio app doesn't work; It actually works, just once every two attempts: If it crashes the first time, select close app, clear apps from background and try again; I'll find a definite fix soon;
- Wi-Fi signal strength doesn't show on status bar, only in the wireless screen;
- Fingerprint reader doesn't work;
- SELinux is currently set to permissive;
Instructions:
- This is a FULL ROM build, meaning your BOOT, DTBO, SYSTEM and VENDOR partitions will be overwritten. Backup first!
- You need firmware version 11.x.y (preferably 11.3.169 - recovery encryption only tested with that version), any will do. 10.5 will not work
- Download TWRP from the files section, fastboot flash it (if you don't have custom recovery yet)
- Download patched vbmeta.img
- Download the latest build
- (Optional) Download Gapps (arm64 9.0, any flavor) and Magisk
- Boot to recovery (whichever you have), flash the new recovery
- Reboot to recovery, now your data is decrypted, flash vbmeta, latest build, magisk and gapps
- Format DATA completely to start from scratch since encryption is different
- Reboot
Downloads:
Builds: https://sourceforge.net/projects/lineageos-lenovo-z5s/files/
Source code:
LineageOS: https://github.com/LineageOS
Kernel and Device Tree: https://github.com/jacoghi
Reporting Bugs:
DO NOT Report bugs if you're not following the instructions!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

Changelog:
May 19, 2020:
- Initital release, everything working except for FM and fingerprint reader;
- Kernel is completely overhauled and updated to LA.UM.7.8.r1-08500-SDM710.0;
- Audio drivers are stock 11.3.169 (we don't have the sources);
- Wifi is open-source, with MAC randomization currently being tested;
- Call recording already works;
- BT Audio works for calls and everything else, HD codecs being optimized;
- Wifi Display works perfectly on my cheap chinese Android TV Box. Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
- Camera2API is active, RAW pictures are also enabled;
- Build will automatically encrypt your device, I had to fool Lenovo's BS keymaster to make it work, so it has to be enabled;
- As of now, I don't care if your apps work or not, that's not my problem, just let me know about hardware issues;

jacoghi said:
Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
Click to expand...
Click to collapse
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!

carlshark said:
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
Click to expand...
Click to collapse
Thanks for confirming that to me, great to know. Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd? And you can use magisk without any issues, I'm using it here right now, no problems.

jacoghi said:
Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd?
Click to expand...
Click to collapse
No, sorry. If that changes, I will let you know
I can imagine most of the users that are here are currently using a GSI. The stock 11.3.169 from here can actually be installed via TWRP. Flashing it would revert to stock recovery so users need to reinstall the TWRP recovery image during the same session. That's how I ensured that I was running an 11.x firmware after using all those GSIs from 4PDA. Hopefully this helps others to revert to stock so they can use your LOS build.

Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download

And what is apparently massive news for us, our phone will get an Android 10 official update, meaning we'll be able to boot lineage 17.1 with the updated audio drivers (in theory). Anybody in China or who knows how to trick their system and able to get ahold of these files?
https://club.lenovo.com.cn/thread-5849244-1-1.html

jacoghi said:
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
Click to expand...
Click to collapse
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.

carlshark said:
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
Click to expand...
Click to collapse
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man

jacoghi said:
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
Click to expand...
Click to collapse
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.

jacoghi said:
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
Click to expand...
Click to collapse
Oh, right, I totally forgot all about that. Should have tried enabling compression or saving to internal storage.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
Click to expand...
Click to collapse
I've found a 4PDA post regarding updating to 11.5 and reposted the good stuff here. Hope it helps. Thanks for your good work!
---------- Post added at 06:38 AM ---------- Previous post was at 06:35 AM ----------
seisa said:
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
Click to expand...
Click to collapse
I know this is the wrong thread to answer this, but we can't really help you out without some more details. Were you trying to install through recovery? Through QFIL?
From the looks of it, sounds like you have a bootloop. Try doing QFIL again and unlocking bootloader, or the other way around - sometimes it works for me that way.

I have Z5s 6GB/128GB model, sold as Global Version & Global ROM.
It does have EU LTE bands, so it probably is somewhat "global".
The downside: I am at 10.5 version with no updates available. Seller also told that there are no updates.
Two questions:
1. Is it absolutely necessary to have 11.3+ to install this LineageOS ROM? What is blocking installation if I have 10.5? Can I brick it?
-- EDIT: I will answer myself: Yes it is needed. LineageOS did not flash over 10.5 and gave an error. That was validation error before flashing, so no harm done.
2. Is it safe to install Chinese ROM on this device? Is it possible to loose something in the process? Like LTE bands or something else important?
-- EDIT: Seems to be ok.
I really want to install LineageOS or some other google free AOSP ROM. But I do not want to loose important features or brick it in the process.
Thanks.
EDIT: I installed Arrow OS GSI at the moment over 10.5 and it seems to work. But still looking forward to get pure LineageOS installed.

I have one problem that is hardware related:
Microphone level is quite low compared to my previous phone and people are complaining about low volume when I call.
Is there any way to add more gain? I tried to search but did not find easy and straightforward answer. Most solutions refer to methods/files that do not exist on this ROM.
What I found was complaint that there is still no way to easily manage audio stuff in android...
Mic Test (lauresprojects.com.mictest) app confirms that recording levels are considerably lower in both direct sound and communication mode when comparing to my other phone.
Otherwise seems to working quite nicely. Thanks for your good work.

I can't use face unlock with this ROM.

Is there still some active development at this project?
Is there some active development at this project?

What's the correct procedure to upgrade from LineageOS 18.1 to 19.1? [SOLVED]

Hi!
Didn't find anyone else describing my predicament, so I'll post it here.
I have kept my S10+ up to date with official LineageOS 18.1 weekly updates for a long time now. Today I discovered that I can't update it with the updater app anymore, because Linux4 has transitioned the official ROM to 19.1, and version upgrades should be done manually.
{
"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"
}
Reading through that page I noticed the warning:
Code:
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
This immediately raised a red flag for me because 18.1 is Android 11 of course. Thinking that the warning might be a mistake and it should still be possible to do the upgrade from 18.1 to 19.1, I downloaded the 19.1 nightly, rebooted the phone to the recovery, and sideloaded lineage-19.1-20220504-nightly-beyond2lte-signed.zip. When the phone started the verification, it told me that I need Android 12 firmware and did not proceed with the upgrade.
Linux4's own page also says that This firmware can only be used with LineageOS 19.1!
Googling around I found that this guy here was able to upgrade his Pixel 4a to version 19 without any previous Android 12 requirements.
And now to my question(s): how should I get my phone to Android 12 firmware if I can't get LineageOS 19.1 installed in the first place? Seems like a chicken and egg situation to me. Is it even possible without losing my data? Do I have to use Odin and flash an official Samsung Android 12 ROM first and then start from scratch? It feels like I have missed something (what?) and therefore I'm puzzled about how to continue. Any advice? Thanks!
Aprold

aprold said:
....
And now to my question(s): how should I get my phone to Android 12 firmware if I can't get LineageOS 19.1 installed in the first place? Seems like a chicken and egg situation to me. Is it even possible without losing my data? Do I have to use Odin and flash an official Samsung Android 12 ROM first and then start from scratch? It feels like I have missed something (what?) and therefore I'm puzzled about how to continue. Any advice? Thanks!...
Click to expand...
Click to collapse
This problem usually occurs afaik when bootloader gets changed/upgraded by Samsung during firmware upgrade.
So your assumption is correct to flash 12 stock first.
So Imo you gotta start from scratch by using Odin or Heimdall.

SOLVED! It turned out that I tried to make an ass out of u and me e.g. *assumed* that the firmware on the Linux4's page was the full firmware when in reality it was only a bootloader and exactly the thing that was needed to complete the transition. Flashed it to BL slot with Odin and after that everything went as it was supposed to. Data partition intact and such. Thanks to bmwdroid and contributors on other threads to put me on the right track!

This did't work for me. When I first flashed the correct new bootloader from 19.1 (lineage-19.1-20220505-recovery-beyond0lte.img) I still couldn't install the new lineage 19.1.
I always got the error, that I need the Android 12 bases firmware.
What I had to do is the following:
unpack the following file
Code:
META-INF/com/google/android/updater-script
from the zip (lineage-19.1-20220505-nightly-beyond0lte-signed.zip) and remove the line
Code:
assert(exynos9820.verify_bootloader_min("G") == "1" || abort("ERROR: This package requires Android 12 based firmware. Please upgrade firmware and retry!");
and replace the file in the original .zip via:
Code:
zip lineage-19.1-20220505-nightly-beyond0lte-signed.zip META-INF/com/google/android/updater-script
This file I could sideload (I had to accept that the signature is not correct).
With that the upgrade von lineage 18.1 to lineage 19.1 worked without a loss of data.

msna said:
This did't work for me. When I first flashed the correct new bootloader from 19.1 (lineage-19.1-20220505-recovery-beyond0lte.img) I still couldn't install the new lineage 19.1.
I always got the error, that I need the Android 12 bases firmware.
What I had to do is the following:
unpack the following file
Code:
META-INF/com/google/android/updater-script
from the zip (lineage-19.1-20220505-nightly-beyond0lte-signed.zip) and remove the line
Code:
assert(exynos9820.verify_bootloader_min("G") == "1" || abort("ERROR: This package requires Android 12 based firmware. Please upgrade firmware and retry!");
and replace the file in the original .zip via:
Code:
zip lineage-19.1-20220505-nightly-beyond0lte-signed.zip META-INF/com/google/android/updater-script
This file I could sideload (I had to accept that the signature is not correct).
With that the upgrade von lineage 18.1 to lineage 19.1 worked without a loss of data.
Click to expand...
Click to collapse
If i follow this, it tells me could not start Android, try reset data

Bluestar01 said:
If i follow this, it tells me could not start Android, try reset data
Click to expand...
Click to collapse
After reset data, device boots succesfully to 19.1

aprold said:
SOLVED! It turned out that I tried to make an ass out of u and me e.g. *assumed* that the firmware on the Linux4's page was the full firmware when in reality it was only a bootloader and exactly the thing that was needed to complete the transition. Flashed it to BL slot with Odin and after that everything went as it was supposed to. Data partition intact and such. Thanks to bmwdroid and contributors on other threads to put me on the right track!
View attachment 5608451
Click to expand...
Click to collapse
@aprold Hi I been searching for the threads you related your success with upgrading s10+ but cant find it. Where or what thread did you get the info to been able to upgrade it? And if there are a step by step tutorial for upgrading to Lineage 19.1 from 18.1 I would be really happy! Best regards Per

[GSI] [Android 13] Nord N10 GSI flasher. EU and Global.

First of all I'm not a developer. I`m not skilled enough to compile stuff myself.
I'm only using available stuff and write some basic scripts.
About
This is a simple script that will automatically delete the "Product" partition, resize the "System" partition to its maximum size, and flash the GSI image onto the device.
Make sure that your OnePlus runs latest (11.0.10) firmware. Tested on my personal device - EU variant. Global variant untested. Using at your own risk.
How to? Instrucions are available in zip file
Download
EU : https://mega.nz/file/7QxX3CJS#3eEyW61h9GAqubtgB8vtrF9c258Um9Iezb-uayBePSY
GLOBAL : https://mega.nz/file/2JBSgSID#9QR6I2nc5mJ0IVhoFtMwRZj3Eu4RbsuGOx59a5FFCI4
GSI LIST : https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
SafetyNet-Fix (Magisk Module) : https://github.com/kdrag0n/safetynet-fix/releases
Since it's GSI, bugs are expected. I only recommend this for testing ROMs features/customizability. If you want stable ROM for now you need to stay on stock. Just wait for more expirienced dev to port LineageOS to our awasome device.​

18.02.2023 :
-EU variant updated to 11.0.10, global still 11.0.8
-Added LineageOS recovery maded by kronflux
15.011.2022 :
-Files updated to 11.0.8 version.
05.09.2022 :
-Misc script improvments.
16.08.2022 :
-Files updated to 11.0.7 version.
-Added stock "boot.img" for those who don't wanna root.
27.07.2022 :
-Initial relesae.

Will this work for the BE86AA version?

How's it working out for you op?

Has anyone got fingerprint work in GSI? When I tried it last time, it worked only to unlock the device. It didn't work on any apps that uses biometric. Will you update script to 11.0.7?

Anyone have tested GSI rom ?

msi68 said:
Has anyone got fingerprint work in GSI? When I tried it last time, it worked only to unlock the device. It didn't work on any apps that uses biometric. Will you update script to 11.0.7?
Click to expand...
Click to collapse
Gonna update when the links for 11.0.7 OTA will be available.

Virgoraheel said:
Anyone have tested GSI rom ?
Click to expand...
Click to collapse
I use this as my daily: https://sourceforge.net/projects/gsi-projects/files/v415/ArrowOS-12.1/
I picked this one: ArrowOS-12.1-arm64_bgN-vndklite-Unofficial.img.xz
Tried LineageOS both 18 and 19 and it can't boot with magisk installed.
ArrowOS booting and passing safetynet. The only bug i found is bluetooth audio. The rest works just fine.

adi_adi said:
I use this as my daily: https://sourceforge.net/projects/gsi-projects/files/v415/ArrowOS-12.1/
I picked this one: ArrowOS-12.1-arm64_bgN-vndklite-Unofficial.img.xz
Tried LineageOS both 18 and 19 and it can't boot with magisk installed.
ArrowOS booting and passing safetynet. The only bug i found is bluetooth audio. The rest works just fine.
Click to expand...
Click to collapse
How's battery timing with arrows os and with Gapps

Bluetooth audio not working?

msi68 said:
Has anyone got fingerprint work in GSI? When I tried it last time, it worked only to unlock the device. It didn't work on any apps that uses biometric. Will you update script to 11.0.7?
Click to expand...
Click to collapse
Updated!

Anyone else besides OP attempted this with the US/GLOBAL variant of this phone? I tried this two days ago, soft bricked my phone and the last error I got was something about the partition being too small and eventually lead me to "qualcomm crash dump mode" but I thankfully got my device back up and running with the MSM tools provided by another XDA member, despite the issues I've encountered I'm still excited to try a GSI with this device eventually lol.

it's not working on my BE86AA (global)
how can i make it run?, im really tired of stock rom
{
"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"
}

fersabi said:
it's not working on my BE86AA (global)
how can i make it run?, im really tired of stock rom
View attachment 5702009
Click to expand...
Click to collapse
Make sure you have installed latest ADB and fastboot.
Edit: If you expirienced error like this you probably booted to bootloader mode. You need to reboot your device to fastboot mdoe.

Any theories on getting this working on the BE2028?. Im rooted on the pixel rom? As my previous post mentions the script didn't work for this device. I'm interested in getting at least android 12 on this device any help would be greatly appreciated. I'm aware of the risks!
I figured out a safer way to test them thanks though.

Hello,
Trying to flash same arrow rom as OP and following the instructions step by step, but I can't get to fastbootd. Regular fastboot works fine as i unlocked the bootloader. Tried fastboot reboot fastboot, but it reboots to a menu with a choice of languages, navigation works only through volume, power buttons. Any advice?
Thanks

Hematogenas said:
Hello,
Trying to flash same arrow rom as OP and following the instructions step by step, but I can't get to fastbootd. Regular fastboot works fine as i unlocked the bootloader. Tried fastboot reboot fastboot, but it reboots to a menu with a choice of languages, navigation works only through volume, power buttons. Any advice?
Thanks
Click to expand...
Click to collapse
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

user76543210 said:
but I can't get to fastbootd
Click to expand...
Click to collapse
AFAIK Fastbootd was a thing in later versions of android which allowed certain partitions to be resized dynamically (e.g. with OTA updates). While Google I believe supported it in A10, other manufacturers may not have implemented it until later versions. I've never seen it on the Nord N10, but I stopped using this phone for a while.
Thus... you likely have only the OnePlus recovery and fastboot partitions - not the ones that OP had for whatever was running prior to flashing Arrow (Maybe a later OOS version, or another ROM? Sorry, too lazy to read the whole thread).
As long as you end up with the right partitions in the end, what you used to load them doesn't matter. While I haven't tried a GSI on the N10, IIRC they don't use a lot of the partitions that OnePlus ships with and you are probably fine. What happens if you just flash through the old-school fastboot?
(Also... you understand the whole A/B thing, right? This is the root of like 80% of flashes that go south).

Hematogenas said:
Hello,
Trying to flash same arrow rom as OP and following the instructions step by step, but I can't get to fastbootd. Regular fastboot works fine as i unlocked the bootloader. Tried fastboot reboot fastboot, but it reboots to a menu with a choice of languages, navigation works only through volume, power buttons. Any advice?
Thanks
Click to expand...
Click to collapse
This is fastbootd. When you are in this menu run "fastboot devices" command to confirm that. I belive that OnePlus integrated somehow recovery and fastbootd because the menu are almost identical in both. But in recovery or bootloader you can't use my script it will only work in fastbootd mode.

Is there any chance of you making a version for the US BE2026 variant?

Question How to root Redmi Note 11?

Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
{
"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"
}

The first step is to unlock your bootloader which usually takes a week. Do that first, then you can browse more and wait for answers while you wait

I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img

parker_04 said:
Hi. I am new to this site.
I want to root my Redmi Note 11 but I don't know how to.
I tried looking up online but all I could find were guides on other devices. And outdated too.
I read about Magisk and Magisk Hide which allows you to pass SafetyNet but I also read that it's developer joined Google. So I don't know if it will work or not.
Please help me.
How can I root my phone and pass SafetyNet?
Device Specs:
View attachment 5807325
Click to expand...
Click to collapse

notBradPitt said:
Make sure to backup all your data before unlocking bootloader as it will wipe them.
I strongly recommend flashing Xiaomi.eu Stable ROM first as it offers more features than stock and also, you don't have to look for the boot.img again. But in case you want to keep it stock, you want to find the flashboot ROM with the exact same version as the one you have right now and extract the boot.img from it. Then you want to get magisk on your phone, transfer the boot.img to your phone, patch it, transfer it back to your computer, and then use ADB to flash the boot.img
Click to expand...
Click to collapse
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.

parker_04 said:
Thank you for replying.
I am quite newbie in rooting.
I can understand enough to follow your instructions but not enough to really know what I am doing.
Can you please elaborate each step and what it does?
Or maybe refer me to a trusted guide where I can understand the tidbits.
Click to expand...
Click to collapse
I think this sums it pretty well: https://forum.xda-developers.com/t/installing-miui-eu-rom-and-root.4426937/
- Backing up data: Back up your data so it won't be lost during bootloader unlock
- Unlock bootloader: allows you to flash into your phone
- Flashing Xiaomi.eu (optional): Their ROM is based on MIUI Global/China which has way more features than region based ROMs and no bloatware. Cons is you have to manually update it and you can't update system apps (as they're also modified to disable ads). Pros is, you know the version you just flashed and the boot.img is also there.
- Finding boot.img: This is the file you want to patch if you want to root your phone. You can find this by extracting the fastboot ROM and it should be inside. In case of stock MIUI, you have to download the exact version that you have right now on https://xiaomifirmwareupdater.com/ , get the flashboot version, extract, and boot.img should be inside
The rest should be explained in the post above and I think this will also help in installation of Magisk https://topjohnwu.github.io/Magisk/install.html

@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download

parker_04 said:
@notBradPitt Hey, is this the correct fastboot rom for my device?
https://sourceforge.net/projects/xi...MNote11_V13.0.5.0.SGKMIXM_v13-12.zip/download
Click to expand...
Click to collapse
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)

notBradPitt said:
Yes. After unlocking bootloader, make sure USB debugging is enabled (because you just reset the phone), boot into flashboot mode, and run the "first install" script. Make sure your cables are connected properly so it doesn't corrupt any files. First time booting will take around 15-20 minutes for me, so this is normal and you shouldn't panic.
After that you can continue with the root process. The boot.img should be in "images" folder. Once you are done with it, you can try the tools listed here (https://www.xda-developers.com/how-to-pass-safetynet-android/) to pass SafetyNet. You can test the SafetyNet using the tool in Magisk or you can use YASNAC (from Google Play or GitHub)
Click to expand...
Click to collapse
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.

parker_04 said:
Thank a lot for your help!
Reply from recently flashed Xiaomi Eu ROM.
Click to expand...
Click to collapse
No problem How do you like it? Have you proceeded with root yet?

notBradPitt said:
No problem How do you like it? Have you proceeded with root yet?
Click to expand...
Click to collapse
It's nice.
Xiaomi eu is certainly cleaner than stock. Adless and bloatless. It has new features although some of the stock's features are missing. Play Store is jittery for unknown reasons.
And when I try to open a file in another app, the app list appears quite late and it's laggy too. But that's all and I don't mind it.
Thanks again for recommending it.

notBradPitt said:
Have you proceeded with root yet?
Click to expand...
Click to collapse
Yeah. Rooting with magisk is so easy. And it's uninstallation is easy too.

parker_04 said:
I have already requested Mi for permission to unlock bootloader. I had to wait 5 days and today is the last day.
Click to expand...
Click to collapse
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?

creepystaircase66 said:
Yo I'm new to rooting ,so during the 168 hours period can I switch from data to Wi-Fi and use it for like watching videos and playing games?
Click to expand...
Click to collapse
Yes, data is only needed when you request for permission

Assuming you have unlocked the bootloader
Step by Step Guide:
1. Download Magisk APK and install it
2. Patch your Recovery (Stock, TWRP, Skyhawk, etc) in magisk app and copy the patched img to Computer
3. Switch it off, then boot to bootloader, and type "fastboot flash boot recovery_patched.img" where recovery_patched.img is your file name.
4. Reboot (Might take longer than usual) and open magisk to confirm the the result of actions.