{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (https://download.lineageos.org/pdx203)
gapps (http://downloads.codefi.re/jdcteam/javelinanddart/gapps)
Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
flash latest recovery via fastboot
reboot to recovery
adb sideload path/to/rom.zip
adb sideload path/to/magisk.zip
format data (recommended)
reboot to system
enjoy!
Update installation:
<!-- change according to your needs -->
reboot to recovery
adb sideload path/to/rom.zip
adb sideload path/to/magisk.zip
reboot to system
enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Device sources:
local manifest: https://github.com/SirRGB/local_manifests/blob/main/pdx203/A12crDroid.xml
kernel source: https://github.com/LineageOS/android_kernel_sony_sm8250
Download:
ROM github
Known issues:
Horizontal grid recents
Qs pulldown lags
Flash in camera app
Special thanks to @clfbbn for maintaining the Lineage OS trees
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Code:
21st Jan 2023
upstream to 8.13
drop misc debugging packages
fix power button location
5th Jan 2023
fix bt audio
4th Jan 2023
fix changelog overlay
enable compact cashed app heaps
27th Dec 2022
Initial ota support
Hello! I am curious as to if notification light works on this ROM or if all lineage problems are also persistent here. Presently I am using lineage on Xperia 1 ii and notification light does not work. I would swap ROMs if so. Thank you!
-Tom
Well it does light up while charging, didnt know it was borked on lineage 20. I assume it worked on 19.1 as well...
I dont know if it works for notifications tho.
Yes, it works flawlessly for charging but not for notification. Please let me know if this works and I'd love to switch Roms! Sadly 19.1 and 20 both did not work, I've used both on multiple devices for months.
Sorry abt that, but I use the official lineage trees, so it is not working...
SirRGB said:
Sorry abt that, but I use the official lineage trees, so it is not working...
Click to expand...
Click to collapse
No worries! Thanks for the prompt responses to my questions! It saves me a lot of headache in swapping just to find out LOL. Thank you!
.- Wiping data... Formatting /data. Formatting /metadata... Data wipe complete. Now send the package you want to apply to the device with "adb sideload<filename>".. Supported API:3 Finding update package... Verifying update package. ERROR:recovery: failed to verify whole-file signature Update package verification took 134.6 s(result Y. ERROR:recovery: Signature verification failed ERROR:recovery:error:21 Installing update.. ERROR:recovery: Current SPL:2023-02-05 Target SPL:2023- 01-05 this is considered a downgrade ERROR:recovery: Denying OTA because it's SPL downgrade stall completed with status 1. istallation aborted.
I honestly dont know why that happens, sorry.
What rom are you coming from? You can try to use other custom recoveries such as twrp.
SirRGB said:
I honestly dont know why that happens, sorry.
What rom are you coming from? You can try to use other custom recoveries such as twrp.
Click to expand...
Click to collapse
ues twrp(OrangeFox)，crdroid ready to start。
@SirRGB there is new version of crdroid 9.12 rom do you continue to upgrade it? The current version is very good, but there are 2 problems: there is no call recording and notification light when receiving news. can you fix the notification light showing when a message comes in?
P.U 93 said:
@SirRGB there is new version of crdroid 9.12 rom do you continue to upgrade it? The current version is very good, but there are 2 problems: there is no call recording and notification light when receiving news. can you fix the notification light showing when a message comes in?
Click to expand...
Click to collapse
Crdroid doesnt really develop crdroid 8 anymore and I built crdroid 9 already. As for the notification light that should be fixed in v9, so I could pick it into v8, but since it doesnt seem to be maintained anymore idk if it is worth it...
As for call recording it is illegal in some countries, so I wont add anything over crdroid in that regard...
SirRGB said:
I have also used the lineageos rom it has call recording and a good notification light for incoming notifications but no cdroid's great customization. I hope you can fix notifications and recording errors. May I ask if you could add the original dynamic vibration and hs.power apps? Thank you very much for maintaining and developing this perfect rom.
Click to expand...
Click to collapse
Thank you so much for your great contribution
Im sorry, I dont know how to do that. Im just using the standard lineage trees for the most part.
sz26190823 said:
.- Wiping data... Formatting /data. Formatting /metadata... Data wipe complete. Now send the package you want to apply to the device with "adb sideload<filename>".. Supported API:3 Finding update package... Verifying update package. ERROR:recovery: failed to verify whole-file signature Update package verification took 134.6 s(result Y. ERROR:recovery: Signature verification failed ERROR:recovery:error:21 Installing update.. ERROR:recovery: Current SPL:2023-02-05 Target SPL:2023- 01-05 this is considered a downgrade ERROR:recovery: Denying OTA because it's SPL downgrade stall completed with status 1. istallation aborted.
Click to expand...
Click to collapse
You simply have to install an older recovery dated before 2023-01-05. I took the one from LineageOS:
https://mirror.kumi.systems/lineageos/full/pdx203/20230101/
I flashed boot, recovery, dtbo and vbmeta to get it running.
itsttime206 said:
Hello! I am curious as to if notification light works on this ROM or if all lineage problems are also persistent here. Presently I am using lineage on Xperia 1 ii and notification light does not work. I would swap ROMs if so. Thank you!
-Tom
Click to expand...
Click to collapse
I also have a Xperia 1ii with lineageOS 20 running. since 1 month now.
everything is running fine!
Also mobile payment banking did work for a while, now since last update the Banking updates do not work anymore because of CTS but the rest works like a charm. (also the signaling)
The camara app in LineageOS 20 is simple but works perfectly, occasionally I miss the advanced camera options like diaphragm setting as in the pro app of Sony
I do not need root, I only want to extend the lifetime of my phone with full safety and latest android updates in stead of the 2 years of Sony.
Is there a possibility to run lineage and to bootlock so all CTS issues are solved, but it still has the ability to update OTA and also the major updates?
And did someone get the pro app running in LineageOS 20?
Well Idk if I will update this rom since I already did crd9 builds. Idk how to sign builds either, but I doubt you can lock the bootloader on any rom atm if you dont have the public key of that rom and flash it to the device, which I didnt see anyone doing yet. Im currently not planning to do ota updates, tho it isnt impossible...
Anyways, thx for using the rom, enjoy.
[EXTRA] Stock Camera && Cinema Pro && Photo Pro For AOSP
You MUST satisfy following condition: * My Device Tree Based ROM (Not SODP) * A PDX206 (Xperia 5 II ) User Download Link: Stock Camera if (ANDROID_VERSION == 10 && STOCK_VENDOR == 10) Using 52_RHE Cinema Pro [52_RHE] Photo Pro [52_RHE] if...
forum.xda-developers.com
The photo app can be found here, I didnt test it myself...
Related
{
"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 thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's 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. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18
first (always wanted to do that)
thanks for this, nice work everyone!!!
Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.
??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
fixed, can remove this.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
fixed, can remove post now.
Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?
npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:
MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?
{
"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 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 Moto Z2 Force.
Join our Moto Z2 Force Discord!
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.
nash
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
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 LineageOS, as the normal proximity sensor works fine.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
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.
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.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and 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.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8998
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
PrivyetCyka said:
How did you find this? I got an alert that lineage 18 came out but went to the website less than five minutes ago and it wasn't available for nash yet ?
*Edit* I just checked again it's not available for download even though it's listed ..weird
Click to expand...
Click to collapse
Am the developer - and it is building on official servers tonight, check back in 24 hours.
npjohnson said:
Am the developer - and it is building on official servers tonight, check back in 24 hours.
Click to expand...
Click to collapse
Oh awesome. Thank you for the hard work ! Glad to see roms still being made for this phone
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
I fixed it! Please make sure to flash lineage from your computer when you are updating to a new version of lineage... NP Johnson makes this clear in his instructions. Unfortunately it has been awhile since I have flashed a rom onto a phone and I forgot that step...
here is how I did it
fastboot flash boot_b recovery-nash.img
factory reset your phone
flash the lineage zip from your computer using adb sideload lineage 18.1 nightly
Very good upgrade, thanks for the hard work and making this real
Thank you for not letting our device die
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
The clock app is not working and I think usb tethering is not working.
Vibration is not working
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Big_Brother_Is_Watching said:
Just flashed on my t-mobile device from recovery. My phone is bricked. The battery life on my z2 force was getting old anyway so I am probably going to have to get a new phone if I can't fix it.
If you have a t-mobile device DO NOT FLASH FROM RECOVERY!!!
Click to expand...
Click to collapse
Flashing from recovery is fine - so long as you can see the zip, it's no problem. Not sure where your problem hit.
But thank you for ultimately flowing the guide and using your PC, it just raised and more seamless.
vivebatu said:
Thanks a ton for keeping our device up to date! I see that the efficiency mode is working for the battery mod, amazing!!
Click to expand...
Click to collapse
Yup! And will from here on out
Big_Brother_Is_Watching said:
The clock app is not working and I think usb tethering is not working.
Click to expand...
Click to collapse
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
Manuelmartad said:
Vibration is not working
Click to expand...
Click to collapse
It works, your motor may have died.
wyldwilly said:
Firstly, THANKS FOR THIS!
I get the following error when opening the Camera app: dlopen failed: library "libmcf-jni.so" not found.
HDR mode is missing and you still can't save to SD - otherwise seems to work OK
Install steps taken:
1. adb sideload lineage-18.1-20210401-nightly-nash-signed.zip
2. Reboot into the newly-updated 18.1 recovery
3. adb sideload MindTheGapps-11.0.0-arm64-20210328_143848.zip
Since I was updating from 17.1 with Google Apps, I did not perform a factory reset per the upgrade instructions here: https://wiki.lineageos.org/devices/nash/upgrade
Was this wrong? Should I have done a clean install?
Click to expand...
Click to collapse
dlopen, HDR, and save to SD: all expected and WIP. Working on them
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
wyldwilly said:
Noice/Thanks!
Oh, I'd like to report that my Mophie external battery seems to be working better than it did in 17.1.
Click to expand...
Click to collapse
That's efficiency mode and proper battery mod support for ya! Haha.
npjohnson said:
Yup! And will from here on out
Clock app works, maybe gapps overwrite it with a broken one? Will try usb tethering locally.
It works, your motor may have died.
dlopen, HDR, and save to SD: all expected and WIP. Working on them
Click to expand...
Click to collapse
no, its not working i tried it on;stock and it works well
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
idelgador said:
Wifi is not working, everything else looks fine. No using cellular (no chip in device). Any ideas?
Click to expand...
Click to collapse
sounds like a persist issue - did you ever flash pie firmware?
npjohnson said:
sounds like a persist issue - did you ever flash pie firmware?
Click to expand...
Click to collapse
Is that related to a previous flash of pie? :O
{
"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.
{
"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 10, 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. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
What's working:
Everything except bugs
Known issues / bugs:
- MTP (Menu from QS doesn't work. Developer option menu does.)
- Bluetooth audio (audio only)
- SELinux permissive
- Encryption (ROM is decrypted)
Notes:
- For MTP, enable developer options and select "Default USB configuration".
Flashing instructions:
1. Flash S001142 OTA (do NOT use different versions!)
2. Wipe Dalvik, Cache, Internal storage and Data. (do NOT wipe vendor).
3. Flash ROM.
4. Flash Gapps / Magisk (Optional.)
5. Reboot.
Device Sources
device_lenovo_X505L
Kernel is currently prebuilt due to Lenovo not releasing sources.
Big thanks to @ud4 for his help!
Download
Reserved.
can we flash it on x505x?
UDONTHAVERIGT said:
can we flash it on x505x?
Click to expand...
Click to collapse
Yes it should work on x505x.
I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip
What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)
sinhus said:
I am reporting with an X505f, Lineage OS logo appears but goes into a bootlop ending up TWRP? How can i debug more? Any advice?
For reference OTA is at TB-X505F-S001142-210804_ROW.zip
Click to expand...
Click to collapse
Please format data and enable ADB On boot.
DominicNoobAtRoming said:
What do i do when i have S001137? Can i just normally install this? TB-X505F
(I have twrp btw)
Click to expand...
Click to collapse
I recommend upgrading to S001142 for safety reasons (since I'm not really sure about the changes Lenovo did between the updates).
tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.
How do i install the update safely becauss im worrying about bricking my tab
yukeiw said:
tried this rom on a x505f.
A few issues:
1. I couldn't get it to start unless gApps was installed.
2. I also can't get the wifi to work at all.
Click to expand...
Click to collapse
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?
henloboii said:
1. I didn't need GApps here. What do you mean "can't get it to start"? Care to be specific?
2. WiFi works OOTB here, but it may be due to kernel (highly unlikely tho as I tested kernels of all 3 tabs on my X505L). Were you on S001142?
Click to expand...
Click to collapse
I have same issue S001142, no WiFi on X505F, toggle just flicks on/off instantly.
However works fine without GApps (only because it wouldn't install, not enough system space Err70 apparently)
Same problem on my X505F, no WiFi. GApps worked well.
Can any X505F users send logs? I would like to take a look.
henloboii said:
Can any X505F users send logs? I would like to take a look.
Click to expand...
Click to collapse
happy to assist if you tell me what logs/where to pull them from, someone on telegram group said they were updating the image?
I tried this on my X505L and I couldn't get it to boot using S001142 and TWRP following the instructions exactly, is there a way to log or debug it if it doesn't boot, or do I have to reflash the firmware and hope for a better attempt?
Hi,
I tried it on my X505F and it was not as easy as I thought. I already had S001142 and started with installing TWRP as denoted here:
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Installing Magisk led to some problems, though, as the wipe of /data afterwards prevented me from flashing the ROM ("Magisk binaries not found"). I had to install Magisk again *and* create a symlink from /data/adb/magisk to /data/magisk to be able to uninstall it again (additionally to renaming it to uninstall.zip etc.). Then I was able to flash this LineageOS.
It didn't boot, though, but was stuck at the Lenovo logo (very early boot phase). I flashed it again, but it didn't help. What *did* help was installing Magisk via TWRP Now the tablet booted into LineageOS, but only with an Android popup that some internal error occured and I should contact my vendor.
After having a black screen for a minute or so the LinageOS setup UI appeared and I was able to set up the clock. When reaching the WiFi page, I wasn't able to switch it on (like the other reported).
Attached you find a logcat and the dmesg output. I hope that's what you need.
I would love to try this but i do use bt audio so i look forward to any updates. i dont think ill ever see this thing run anything past android 10, but im not too worried about that, i know its an old cheap tablet. are you able to expand internal storage to an sdcard? my number one complaint about this thing is it always complaining of low storage.
Hay dose anyone have a copy of the stock firmware (so
TB-X505F-S001142-210804_ROW.zip)
I had the exact same experience as this. Ah well... It would've been nice to strip out this Lenovo bloated ROM with something sleeker.
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
[*]Gapps Included
[*]Magisk 25.0 or newer for root (after first boot) - (Download from here)
First time installation:
Flash MAY Firmware
reboot bootloader
fastboot -w update rom_name.zip
Update installation:
fastboot update rom_name.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_google_pantah
Download:
ROM: Download
Changelog:
Known issues:
you tell me
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
Changelog:
==== 05 May, 2023 =====
=== Rom Source ===
- Initial crDroid 9.5 release
- Updated to May 2023 security patches (android-13.0.0_r43)
- Added pixel style lockscreen weather based OmniJaws
- opengl: fix resource leak when dlsym failed
- Switch latest clang to 17.0.1
- Updated themed icons
- Updated translations
- Allow pause/suspend app feature with parallel space
- Settings: Expose radio info (*#*#4636#*#*)
- Added QS Header Image option
- Wallpaperpicker: fix overlapping when scrolling
- WallpaperPicker2: Remove the use of smaller images for thumbnails
- Updated libvpx, bionic
- Updated translations
- Add a toggle to force LTE_CA
- Added back 2 button navigation
- Fixed/Reworked switch to unlink ringtone and notifications volume
- Fixed process can't start because of mPendingStart is true problem
- Fixed SystemUI restart due to network traffic meter
- NetworkTraffic: Simplify stats calc to prevent issues
- PixelPropsUtils: Spoof user build
- Settings: Show memory usage in app info
- SystemUI: Rework dismiss all view in QS
- SystemUI: Handle more exceptions for firewall
- Prevent crash with pin protected user and taskview
- Fix hang when dumping local window
- Updated Webview to 112.0.5615.136
- Updated bionic, lmkd, sqlite
- Updated translations
=== Device ===
May Security Patch
New Kernel: MadKali thanks @Duhjoker
Removed Scrolling Tweaks/Fix Lags
===== 27 April, 2023 =====
-Resync Rom Source
-Qs Header Images
-Fix Safetynet OOTB
-Fixed NGA
-Other Tweaks and Optimizations
another one just in case
I've been waiting for this release to try something other than stock. Thank you for your hard work and this variant! Much appreciated!
Coming from your last unofficial version, is it necessary to install google april factory version first or can I just update crdroid rom (clean or dirty flash?)
Thanks in avance.
Bestiole222 said:
Coming from your last unofficial version, is it necessary to install google april factory version first or can I just update crdroid rom (clean or dirty flash?)
Thanks in avance.
Click to expand...
Click to collapse
Yes you need to install April firmware
Do you plan to release a vanilla version without gapps?
gap30 said:
Do you plan to release a vanilla version without gapps?
Click to expand...
Click to collapse
No it's a pixel so that's why I include the gapps
omariscal1019 said:
Yes you need to install April firmware
Click to expand...
Click to collapse
Ok, there are two april firmware panther-tq2a.230405.003.e1-factory-ae8e7da5.zip and panther-t3b3.230413.003-factory-14b0dd69.zip the second appears after your rom it's ok for you or I must flash the first one. Which kernel is included with your rom ,Kirisakura _ Raviantah if yes which version?.
Bestiole222 said:
Ok, there are two april firmware panther-tq2a.230405.003.e1-factory-ae8e7da5.zip and panther-t3b3.230413.003-factory-14b0dd69.zip the second appears after your rom it's ok for you or I must flash the first one. Which kernel is included with your rom ,Kirisakura _ Raviantah if yes which version?.
Click to expand...
Click to collapse
The OP shows the kernel.
rspkt said:
The OP shows the kernel.
Click to expand...
Click to collapse
Thanks
Noticed something strange with this build. When I attempted to enable Zygisk on Magisk stable it would immediately fail to boot. I could only get it to work by using the latest canary. Flashed after clean-flashing April to both slots.
stompysan said:
Noticed something strange with this build. When I attempted to enable Zygisk on Magisk stable it would immediately fail to boot. I could only get it to work by using the latest canary. Flashed after clean-flashing April to both slots.
Click to expand...
Click to collapse
No issue here.
Tried replicating on 26.1 several times, works without issues for me.
I've used crDroid on my Mix 2 and I loved it. I'll be trying this for sure.
Question: I have a JP version of Pixel 7, that have Sony Felicia chip (for transport and payments). Will that still work with this Rom? I'm not talking about 'custom rom'/'root' checks, I'm talking about rom compatibility with the japanese version hardware. Thank you.,
new update
04/27
Finally installed the ROM and rooted with Magisk v26.1 by patching the init_boot file in the ROM .zip and flashing via fastboot. No issues with either the install or rooting. Restored the majority of my apps with Swift Backup and everything seems good to go so far.
First time using this ROM and I'm pretty impressed at the amount of customization and features it has. Reminds me a lot of the customization found in ROMs like Resurrection Remix which was a favorite ROM of mine on an earlier model Pixel phone. Only complaint is the amount of pre-installed apps that I could do without but just disabled/froze them via Titanium Backup's freeze feature. I do love that it comes pre-packaged with Kirisakura Raviantah kernel though since it's my favorite to-date and was planning on installing it anyway.
Thanks for the hard work @omariscal1019 and hope this becomes official eventually.
EDIT: One question... what is the best method for updating the ROM from the 4/19 to 4/27 build? Thanks in advance.
EDIT #2: Nevermind. Just booted into the bootloader and flash with 'fastboot update crdroid_panther_04_27.zip' without the -w flag to preserve my data and update went flawlessly as well. Thanks again.
rspkt said:
Finally installed the ROM and rooted with Magisk v26.1 by patching the init_boot file in the ROM .zip and flashing via fastboot. No issues with either the install or rooting. Restored the majority of my apps with Swift Backup and everything seems good to go so far.
First time using this ROM and I'm pretty impressed at the amount of customization and features it has. Reminds me a lot of the customization found in ROMs like Resurrection Remix which was
Click to expand...
Click to collapse
Oh, nice to know that the kernel already include
My holiday has begun, time to flash it
Just finished install rom and root with magisk
May I ask, when I reboot phone, it always show a notice of your phone is in unsafe state, and I need to manually press power button to continue. It only for me or it's normal when using rooted pixel?
hungragezone said:
Just finished install rom and root with magisk
May I ask, when I reboot phone, it always show a notice of your phone is in unsafe state, and I need to manually press power button to continue. It only for me or it's normal when using rooted pixel?
Click to expand...
Click to collapse
This screen appears when bootloader is unlocked, it's normal.
hungragezone said:
Just finished install rom and root with magisk
May I ask, when I reboot phone, it always show a notice of your phone is in unsafe state, and I need to manually press power button to continue. It only for me or it's normal when using rooted pixel?
Click to expand...
Click to collapse
You don't technically "need to manually press power button to continue" as it should after a few moments continue the boot process after a short delay regardless. If you want it to boot a few seconds faster, then you can hit the power button twice and essentially speed up this notification dismissal and resume the boot process. Once your phone is unlocked (rooting is not the reason why) you will always see this message during the boot process and it's 100% normal as @Bestiole222 already stated.