{
"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 13, 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 our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_murray
https://github.com/XperiaBrickers-10IV/device_sony_pdx225
https://github.com/XperiaBrickers-10IV/vendor_sony_murray
https://github.com/XperiaBrickers-10IV/hardware_sony
Current Bugs:
None
Many thanks to:
@clfbbn
@loipuru
@WindowsDev0
@dylanneve1
@Sakuu
Special thanks to
Sony
@jerpelea
For sending me the device
If some moderator could make us a device forum that would be lovely
King081 said:
View attachment 5856369
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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 our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Basic requirements:
Unlock your bootloader, make sure you are on Android 13 firmware.
Make sure you can send and receive SMS and receive calls (also via WiFi and LTE, if possible). It would be better for you to get VoLTE/VoWiFi utilized once on stock to provision IMS
Currently tested on XQ-CC54 (If it does not work, please report below)
Make sure you have gone through the installation guide once before proceed!
Installation:
Extract the rom and the extract the payload and the continue with steps below (note usb does not work in recovery yet so transfer rom to sdcard)
Flash additional partitions and recovery.
Download the following files from the download link:
dtbo.img
vendor_boot.img
boot.img
Connect your device to your PC via USB if isn't already
If your device is not already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
Flash the downloaded image files to your device by typing:
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
fastboot flash boot <boot>.img
Now reboot into recovery to verify the installation:
fastboot reboot recovery
Installing LineageOS from recovery
Download the lineageos installation package that you would like to install from the download link
If you are not in recovery, reboot into recovery
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu
Sideload the LineageOS package
On the device, select "Apply Update", then "Apply from sd card" to begin flashing rom
Return to the main menu
(Optionally) If you want to install any add-ons, click "Advanced", then "Reboot to Recovery", then when your device reboots, click "Apply Update", then "Apply from sdcard", then chosse your packages in.
Once you have installed everything successfully, click the back arrow in the top left of the screen, then "Reboot system now"
Downloads:
http://GDrive
https://drive.google.com/drive/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR?usp=sharing
Device Trees & Kernel Source:
https://github.com/XperiaBrickers-10IV/kernel_sony_murray
Device Trees will be public soon
Current Bugs:
Sound does not work
screen flickers black
vibration does not work
USB doesn't work in recovery
takes about 3 buttton presses to get out of deep sleep
ENG build so you will get a red border
Many thanks to:
@clfbbn
@lolipuru
@WindowsDev0
@dylanneve1
Click to expand...
Click to collapse
What device is this ROM for?
TheWorldYT said:
What device is this ROM for?
Click to expand...
Click to collapse
pdx225 Xperia 10IV
Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.
litelinux said:
Lovely! Was thinking of building by own with the open devices guide from Sony, but looks like you were faster
It really would be great if we have a device forum.
Click to expand...
Click to collapse
It's not sodp based, it's stock based
Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yeah, don't worry it's my development device, so don't need testers, this is for those that like Trying stuff and mainly to get a forum
Join my telegram group for now https://t.me/Xperia007
King081 said:
It's not sodp based, it's stock based
Click to expand...
Click to collapse
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid
litelinux said:
How does that make a difference in terms of hardware / firmware support or elsewhere? I'm very new to ROM development, sorry if I sound stupid
Click to expand...
Click to collapse
SODP tries to open source all the blobs, while stock based doesn't, due to the difficulty sodp is not really stable compared to stock base
Could Be Anyone said:
Thanks for your hard work.
Looking forward to the bugs getting squashed.
Unfortunately my 10 IV is my only phone so can't help test since I need sound for work calling.
Glad the 10 IV is getting custom rom love, it's the smallest width device I could find to replace my broken XZ2C.
Click to expand...
Click to collapse
Yup, it's the closest thing to my previous phone (xz5c) I can fond on the market! Even the outer frame feels similar.
Could Be Anyone said:
I miss the xperia compacts.
Got small hands and the compacts were perfect.
10 IV is all right but I wish the width was smaller, 65mm would be amazing.
I guess I should be thankful it's just 67mm and not 77mm like the newer google pixels
Click to expand...
Click to collapse
Lol me with the Google Pixel 7
Update available
Changelog:
Sound and Mic now working
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR
Update available
Changelog:
Vibration and SDM work so screen does not flicker anymore and does not take 3 button presses to wake display
Current Bugs:
camera
ENG build
download here at
https://drive.google.com/drive/u/0/folders/1tpg8SwQn3-kV4b-Ta_4yenLwQNHLWiyR
it is now a usable device,
device trees will be public today
Device Tree are now public link available on first post
Could Be Anyone said:
Thanks so much.
Will install and provide feedback.
Is there lineageos recovery? I couldn't find one.
Click to expand...
Click to collapse
You'd have to extract the payload.bin file and flash boot vendor_boot and dtbo in fastbootD then reboot to recovery and flash rom.zip
Could Be Anyone said:
Keep getting an error.
E:Signature verification failed
E:error: 21
Install from SD card completed with status 2
Installation aborted
Click to expand...
Click to collapse
That's weird never happened to me before
Could Be Anyone said:
Well that's weird since I followed your instructions to a T.
Could you port lineageos recovery as well? It'll fix this problem since the stock recovery doesn't have the option to bypass signature verification.
Click to expand...
Click to collapse
You didn't listen then, extract ROM zip extract payload.bin, then flash vendor_boot boot and dtbo then reboot to recovery (Los one) then flash rom zip
Could Be Anyone said:
I couldn't find the los recovery on the first page.
Click to expand...
Click to collapse
I just said to extract it
Could Be Anyone said:
Ah, I my bad, I thought it was just a normal zip you meant to install, sorry about that.
Click to expand...
Click to collapse
No worries lol
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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Work In Progress untested build, my device is about to come, needing testers here!. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
TWRP
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp_lavender.img[/CENTER]
BUGS:
NEEDS A TEST
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
Contributors
Me
TWRP team for Mi A2 Blobs.
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Alpha
Created 2019-03-15
Last Updated 2019-03-15
Its not twrp. It look like oldschool cwm recovery
Looks like CWM. Boots up, but everything is extremely small. Text gets cut off by beveled screen edges. Did successfully flash a rom though.
The important thing at the moment is that it works, and if you could flash a rom it's a good start. The design will be corrected later.
I just built another version, now using updated TWRP sources, can anyone try it?, just flash like the last one.
Link: TWRP v2
Next week i will have my device (Purchased, but still on delivery) and developing will start to get quickly.
josalaito said:
I just built another version, now using updated TWRP sources, can anyone try it?, just flash like the last one.
Link: TWRP v2
Next week i will have my device (Purchased, but still on delivery) and developing will start to get quickly.
Click to expand...
Click to collapse
This build boot fine but phone is encrypted with the default password in chinese twrp so can't do anything. In reboot option, I saw option to boot to slot A and B
josalaito said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Work In Progress untested build, my device is about to come, needing testers here!. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
TWRP
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp_lavender.img[/CENTER]
BUGS:
NEEDS A TEST
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
Contributors
Me
TWRP team for Mi A2 Blobs.
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Alpha
Created 2019-03-15
Last Updated 2019-03-15
Click to expand...
Click to collapse
Seems like the V2 got bugs, anyone tried to fastboot the V1? On the Chinese varient? I don't mind the CWMR, it looks cool anyway:laugh:
ttn.threat said:
Seems like the V2 got bugs, anyone tried to fastboot the V1? On the Chinese varient? I don't mind the CWMR, it looks cool anyway:laugh:
Click to expand...
Click to collapse
They just freed kernel source so i''m building a new version that should have all working, also, i'm starting to work on Lineage OS, i need to wait 360 hours to unlock the device but i'm working on it now.
josalaito said:
They just freed kernel source so i''m building a new version that should have all working, also, i'm starting to work on Lineage OS, i need to wait 360 hours to unlock the device but i'm working on it now.
Click to expand...
Click to collapse
I can help you testing it if you need a tester.
ebautista said:
I can help you testing it if you need a tester.
Click to expand...
Click to collapse
I'm just compiling a new version using updated sources + compiled kernel, will post it here when finished, will mention you.
josalaito said:
I'm just compiling a new version using updated sources + compiled kernel, will post it here when finished, will mention you.
Click to expand...
Click to collapse
Sure man.
ebautista said:
Sure man.
Click to expand...
Click to collapse
Here you have: https://www.mediafire.com/file/0gne12pjz46zg47/twrp_lavender.img/file
Should boot normally with fixed crypto, if not, tell me to provide you a secondary version i just compiled with minor changes.
josalaito said:
Here you have: https://www.mediafire.com/file/0gne12pjz46zg47/twrp_lavender.img/file
Should boot normally with fixed crypto, if not, tell me to provide you a secondary version i just compiled with minor changes.
Click to expand...
Click to collapse
I have this error when flashing on chinese twrp: " Size of image is larger than target device"
Edit: and "Error flashing partition : Volume Full" with fastboot mode
perform a fastboot boot twrp_lavender.img
josalaito said:
perform a fastboot boot twrp_lavender.img
Click to expand...
Click to collapse
This command never work on note 7, but I will try
Thanhbat said:
This command never work on note 7, but I will try
Click to expand...
Click to collapse
i know, thats why i was betting this build was suspected to not boot, i'm building a trimmed version and will upload here
josalaito said:
i know, thats why i was betting this build was suspected to not boot, i'm building a trimmed version and will upload here
Click to expand...
Click to collapse
Now it stuck at redmi logo not bootanimation
This version got a trimmed kernel, this should boot with fixed crypto.
josalaito said:
This version got a trimmed kernel, this should boot with fixed crypto.
Click to expand...
Click to collapse
Fail to decrypt with default password. But system seem successfully mounted because I reboot system without no os installed message
josalaito said:
This version got a trimmed kernel, this should boot with fixed crypto.
Click to expand...
Click to collapse
Booted fine but need to format data coz my phone is encrypted. Will ttry to play it around.
{
"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 12, 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.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4, programminghoch10
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/LineageOS/android_kernel_samsung_gta4xl/tree/lineage-19.1
Requirements:
Any R based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Magisk
I strongly recommend to use Lygisk instead,
which is a fork of Magisk that aims to improve support for devices with FBE that can't (and shouldn't anyways!) decrypt userdata in recovery,
this will also fix OTAs getting stuck while having installed Magisk.
Features
SELinux enforcing
AES-256-XTS FBE encryption
Latest Linux 4.14.x kernel
Known issues
LineageOS specific features like livedisplay (for now)
You tell me
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
fzzt said:
I am on your unofficial 18 and this just pop up in updater, is it safe to do OTA? Thanks for your efforts!
Click to expand...
Click to collapse
Always follow this rule of thumb: it is never safe to dirty flash a completely different build on top of an older build (i.e. flashing 19.0 on top of 18.1, or 18.1 on top of 17.1, etc.). At best, you'll find yourself having random problems all over the place; at worst, the ROM will refuse to load. Best thing to do whenever going from one major release to another (or from one completely different ROM to another) is backup your apps and data, wipe data and caches and perform a clean flash, then restore your apps and data. It's a fair bit of work, to be sure, but it's the best way to avoid problems.
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
electro_vinyl said:
Sim card dont work, IMEI dont show, gapps cant install. Any ideas?
Click to expand...
Click to collapse
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Macuway said:
About the SIM issue, there's two things:
1. (more likely) You flashed the wrong build (gta4xlwifi instead of gta4xl) or in other words, flashed the WiFi only version firmware.
2.(Unlikely but could happen) You corrupted your baseband somehow as I had a similar situation with my Redmi Note 9 with a corrupted baseband so basically the IMEI was all zeros. That was also the reason why the SIM card didn't work.
You could try to install the original firmware with odin and check functionality and try again.
About the gapps issue
Did you install it for the correct architecture (arm64 not arm)?
Does it show error messages?
Click to expand...
Click to collapse
With the latest build, it's all fixed!
Installed Lineage 19 last weekend on my P-610. You can flash the rom.zip, GApps and Magisk in Recovery from SD-card, so no need to sideload with adb. I have a problem with Google Playstore, it lags a lot (pending...) and installing an app like Gmail takes a long time. Now it even stopped working. Will try it later with NikGApps for Android S
Hi, it seems audio is not working.
It's just me?
Any help please.
M
minoltista said:
Hi, it seems audio is not working.
It's just me?
Any help please.
M
Click to expand...
Click to collapse
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Linux4 said:
Are you on today's build already?
If so try again with that please - your device might be hw revision 9 which uses different audio drivers and wasn't supported in my kernel until today
Also could check the output of adb shell getprop ro.boot.revision to confirm it's rev 9
Click to expand...
Click to collapse
Just installed and it works! Thanks !!!
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
langamer101 said:
guys how do you flash this? I follow all the steps and when I do adb sideload <lineage os> it fails at 47%?????
error 21 log on the tab
Click to expand...
Click to collapse
got it working guys. no need to help anymore.
Does anyone know why gboard force closes every time i try to install? I cleared all storage, played with permissions. Nothing worked.
First of all, I want to say thank to @Linux4 for this release Secondly, I want to ask comrads how to install MicroG on this build? If you can step by step, I'm new to custom firmware
how is newest recovery
Screenshots please
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
lobotomite said:
Working nicely, I'm currently getting a weird issue with the 2021-11-27 gta4xl build.
It's extremely weird but with quiet songs there's some kind of audio ducking going on.
Song it was most obvious on was Air - Bad and Sad 4.2 Vagabond Demo for example but it sounds like it's trying to cut out the audio or something.
Device was bought a few days ago so I'm guessing it'll be the latest hw revision.
Click to expand...
Click to collapse
I have the same thing with any sound on the tablet This is especially noticeable when playing songs on spotify.
{
"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.0/README.mkdn
flashing instructions:
for first install:
be on the latest 11 firmware on both slots
download the file named like this: crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip
also download recovery
put it in the same folder where your adb files are
reboot to bootloader
fastboot flash recovery recovery.img
reboot to recovery
choose "Factory reset"
choose "Apply update"
adb sideload "crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip"
reboot recovery
choose "Apply update"
adb sideload "gapps"
reboot to system
to update:
download the file named like this: crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip
put it in the same folder where your adb files are
reboot to recovery
choose "Apply update"
adb sideload "crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip"
reboot recovery
choose "Apply update"
adb sideload "gapps"
reboot system
some large gapps packages will not install due to lack off space
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM download
Changelog: Changelog
crDroid OnePlus 8 Telegram group
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 8T
Contributors
firebird11
Source Code: https://github.com/crdroidandroid
firebird11 said:
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.0/README.mkdn
flashing instructions:
for first install:
be on the latest firmware on both slots
download the file named like this: crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip
also download recovery
put it in the same folder where your adb files are
reboot to bootloader
adb flash recovery recovery.img
reboot to recovery
choose "Apply update"
adb sideload "crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip"
reboot recovery
choose "Apply update"
adb sideload "gapps"
choose "Factory reset"
reboot to system
to update:
download the file named like this: crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip
put it in the same folder where your adb files are
reboot to recovery
choose "Apply update"
adb sideload "crDroidAndroid-12.0-XXXXXXXX-kebab-v8.X.zip"
reboot recovery
choose "Apply update"
adb sideload "gapps"
reboot system
some large gapps packages will not install due to lack off space
Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url
Download:
ROM download
Changelog: Changelog
crDroid OnePlus 8 Telegram group
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
XDA:DevDB Information
crdroidandroid, ROM for the OnePlus 8T
Contributors
firebird11
Source Code: https://github.com/crdroidandroid
Click to expand...
Click to collapse
Great to see you on Android 12, will give this a play with later today.
ROM looks good, but mobile data not working at all.
It registers that Verizon is the network, but still also says No Sim card detected.
Does this rom support pixel shifting(burn-in protection)?
I've been hoping that someone could confirm or refute the comment that mobile data doesn't work. Can anyone say?
Also, which recovery is recommended? The only ones I know of (Orangefox & TWRP) claim not to be A12-ready.
Thanks for any advice.
(P. S. Is this correct?
reboot to bootloader
adb flash recovery recovery.img
Should the second command not be "fastboot"?)
Hi,
Mobile data work,
Flash using fastboot installer,
Nikgapps Core work perfectly.
CDI-78 said:
Hi,
Mobile data work,
Flash using fastboot installer,
Nikgapps Core work perfectly.
Click to expand...
Click to collapse
Hey can I flash Gapps using fastboot installer as well?
Zekedw said:
Hey can I flash Gapps using fastboot installer as well?
Click to expand...
Click to collapse
Rename the Long name from the gapps in GAPPS. Put the renamed GAPPS in your adb Folder, reboot in recovery , in recovery you choose Apply update and then Apply from adb then use this Command: adb sideload GAPPS.zip
GraveDigger176 said:
Rename the Long name from the gapps in GAPPS. Put the renamed GAPPS in your adb Folder, reboot in recovery , in recovery you choose Apply update and then Apply from adb then use this Command: adb sideload GAPPS.zip
Click to expand...
Click to collapse
Do the same with Magisk to root,
Use Magisk 23.0, the 24.1 fail, update in app.
Awsome that it comes without Google spyware, thank you
ramiiiii said:
Awsome that it comes without Google spyware, thank you
Click to expand...
Click to collapse
Yeah, nice to see more ROMs doing that. I might try this on my device soon.
Which recovery should we use? Orange Fox and TWRP are based on 11 so not sure we can go that route.
Look in the Orangefox thread for my comment about TWRP not working but Orangefox working perfectly first time.
[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [OnePlus 8t / 9r] [19-MAY-2023]
OrangeFox Recovery Project /* * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
After struggling for many hours to install this ROM, I'm now very pleased with it and I'm already looking forward to future updates (no pressure...). On that topic I'd just like to ask about the update script, which mentions reinstalling Gapps. Is this actually necessary, as on previous ROMs Gapps "stuck" between updates? Not a problem, just checking.
Edit: Ah, it occurred to me that when updating I guess the update goes into the inactive slot and would therefore require a new set of Gapps. I also guess that from then on Gapps reinstallation wouldn't be needed.
Finally, against the rules, thanks to firebird11 for this great ROM.
(P.S. Magisk 24.1 works fine for me).
I am on 7.12 version of this rom (android 11). Can I update straight to this one (android 12) without having to do a clean install?
I will try and install this ROM as well now.
I'm on op8t and i tried the crdroid 12 but after installation i went back into recovery and it didn't show the internal storage, at first i thought it was recovery (twrp) so i installed orange fox but same result no access to internal storage.
I don't have this problem with android 11 only on 12 has anyone experienced this if yes please help me solve this problem.
kurozarafv0 said:
I'm on op8t and i tried the crdroid 12 but after installation i went back into recovery and it didn't show the internal storage, at first i thought it was recovery (twrp) so i installed orange fox but same result no access to internal storage.
I don't have this problem with android 11 only on 12 has anyone experienced this if yes please help me solve this problem.
Click to expand...
Click to collapse
Both can't decrypt internal storage properly on A12. So, it will not work unless ROM doesn't implement encryption on internal storage.
A nice ROM, at least with your build. I tried building it myself, but my build was very unstable and didn't have the fingerprint sensor working. Maybe it's because whole crDroid was in transition between versions (though this shouldn't be an excuse for anything). Your build of the ROM worked flawlessly. Nice to see a ROM without any Google bloat- and spyware. OP Camera and Gallery apps are a nice addition. I'll be sending my 8T to OP for a minor repair soon, would be glad to see an update and a stable codebase until then. Thanks for your work!
Any news for CrDroid 8.2 update... ?
{
"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 13, 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.
Instructions:
Follow the instructions here
Downloads:
Builds: https://lineage.linux4.de
GApps: MindTheGapps
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
DO NOT Report bugs if you're using TWRP
DO NOT Report bugs while having Magisk installed (especially with Zygisk enabled)
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. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Contributors
Linux4
Source Code: https://github.com/LineageOS
Kernel source: https://github.com/Linux4/android_kernel_samsung_gta4xl/tree/lineage-20.0
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Features
SELinux enforcing
AES-256-XTS FBE encryption
Known issues
VoLTE/VoWiFi
You tell me
Likely more
If we already have LOS 19.1 and recovery, do we still need to install the new recovery and factory reset?
edit: I renamed the new recovery image to recovery.img and then used 7zip to make recovery.tar and flashed it with Odin. But when I booted to recovery, all I got was a blank screen. Had to reflash the 19.1 recovery to get it back.
Linux4 said:
Requirements:
Any Q, R or S based firmware installed on your device.
Pre-Install Instructions
Warning: The following instructions will unlock the bootloader and wipe all userdata on the device.
Connect the device to a Wi-Fi network.
Enable Developer Options by pressing the “Build Number” option in the “Settings” app within the “About” menu
From within the Developer options menu, enable OEM unlock.
Power off the device, and boot it into download mode:
With the device powered off, hold Volume Down + Volume Up and connect USB cable to PC.
Now, click the button that the onscren instructions coorelate to “Continue” and/or “Unlock Bootloader”.
Your device will reboot, you may now unplug the USB cable from your device.
The device will demand you format userdata, please follow the onscreen instructions to do so.
Run through Android Setup skipping everything you can, then connect the device to a Wi-Fi network.
Re-enable Development settings by clicking the “Build Number” option 10 times, in the “Settings” app within the “About” menu, and verify that “OEM Unlock” is still enabled in the “Developer options” menu.
Installing LineageOS for the first time
Flash lineage recovery
Only the provided lineage recovery will be supported,
using TWRP might result in a possible data loss!!
If using Odin rename the lineage recovery image for your model to recovery.img and add it to a .tar archive using e.g 7zip.
If using Heimdall use: heimdall flash --RECOVERY recovery.img --no-reboot
Boot lineage recovery
IMPORTANT: Do not boot into system again before booting recovery, or system will restore stock recovery!
If using Odin untick auto-reboot before flashing.
After flashing reboot by pressing Volume Down and Power for approximately 7 seconds,
immediately hold Volume Up and Power to boot recovery
IMPORTANT: As of OneUI 3 your device needs to be connected to a PC via USB cable in order to be able to
boot recovery via Volume Up, Bixby and Power.
Factory reset using Factory reset -> Format data/factory reset
Warning: Unlike TWRP this will also erase internal storage!
Sideload LineageOS by enabling sideload via Apply Update -> Apply from ADB
Then run adb sideload <path to your lineage.zip> on your PC
Optional:
Sideload GApps and magisk by repeating above step
with their zip/apk
Click to expand...
Click to collapse
May I ask for screenshots? This is amazing work
HippoInWindow said:
May I ask for screenshots? This is amazing work
Click to expand...
Click to collapse
It appears the dev wants you to use Telegram for support and doesn't answer questions here in XDA. But I didn't get much support there either. When I asked what gapps to use, It just pointed to the Nikgapps site. But when I flashed the CORE version for T, Play Store didn't recognize the internet connection. Tried to revert to 19.1 and it wouldn't let me. Claimed it was a downgrade and not allowed. Had to flash the latest stock version via Odin, with all of the Samsung and Google bloat.
Well, I got it to work in spite of the lack of support. Had to use the OMNI version of Nikgapps instead to CORE. One little nit pick discovered so far. /Setup/System/Status Bar setting to change the battery icon to text and show percent doesn't work. But that is easy to live with.
lewmur said:
If we already have LOS 19.1 and recovery, do we still need to install the new recovery and factory reset?
edit: I renamed the new recovery image to recovery.img and then used 7zip to make recovery.tar and flashed it with Odin. But when I booted to recovery, all I got was a blank screen. Had to reflash the 19.1 recovery to get it back.
Click to expand...
Click to collapse
https://dl.linux4.de/lineageos/releases/gta4xlwifi/
LOS 20 recovery here. I do think we have to use same recovery version as the instructions say.
The image has been updated today and now I see the lineage OS 20.0 recovery.
xsw2 said:
https://dl.linux4.de/lineageos/releases/gta4xlwifi/
LOS 20 recovery here. I do think we have to use same recovery version as the instructions say.
The image has been updated today and now I see the lineage OS 20.0 recovery.
Click to expand...
Click to collapse
if flashed it with the old recovery but the zip check false and then you have to flash anyway
i check and the file size of both recovery where the same thought that is just for the ones that need it for flash for the first time
Just downloaden every thing with a AVG Antivirus alert.
For now I'll wait and maybe test later.
edit: the alert was from a know false positive.
For me better safe than sorry.
reef2009 said:
Just downloaden every thing with a AVG Antivirus alert.
For now I'll wait and maybe test later.
View attachment 5705853
Click to expand...
Click to collapse
Well I built that zip myself, I can assure you there's no malware.
BTW Antivirus apps on android are only a waste of resources.
Updated with September securitypatch and more lineage features
Is the changelog link broken? When I try it to see if I want to flash the latest version, it just times out.
lewmur said:
Well, I got it to work in spite of the lack of support. Had to use the OMNI version of Nikgapps instead to CORE. One little nit pick discovered so far. /Setup/System/Status Bar setting to change the battery icon to text and show percent doesn't work. But that is easy to live with.
Click to expand...
Click to collapse
You're not owed support by anyone. OP could flip off every user and **** off forever, but they'd still have done their work for the community. Thanks for the tips, though!
okno13 said:
You're not owed support by anyone. OP could flip off every user and **** off forever, but they'd still have done their work for the community. Thanks for the tips, though!
Click to expand...
Click to collapse
I didn't claim I was owed support. I merely stated that I didn't get any and that I was able to get it working in spite of that.
Device reboots after opening camera. Probably issues with camera hal
So far so good, except I cannot for the life of me get the Google keyboard to work...all other gapps are fine...
Well, the dev for this ROM has convinced me to sell my S6 and buy a newer tablet that has support here in XDA. Apparently, he will only offer support in Telegram because, in that app, he can ban anyone who disagrees with him. So, no support if you want, TWRP, Magisk, Nixgapps, custom kernels or anything else he doesn't like.
lewmur said:
Well, the dev for this ROM has convinced me to sell my S6 and buy a newer tablet that has support here in XDA. Apparently, he will only offer support in Telegram because, in that app, he can ban anyone who disagrees with him. So, no support if you want, TWRP, Magisk, Nixgapps, custom kernels or anything else he doesn't like.
Click to expand...
Click to collapse
What reason would we have to ban people who want support? He doesn't provide support for TWRP because it's a discontinued project and because it worked terribly on the tablet. That's like asking Samsung for help on a flip phone you bought in 1994 that's been discontinued for quite a while. I don't think I recall him actively rejecting people's technical support for Magisk, NikGapps, or Custom Kernels when I was in his Telegram, he only said that he recommends alternatives to Magisk and NikGapps. I don't know if you're writing this after you were banned but the only time he proactively rejected support in people's devices is when TWRP was in the equation.
{Mod edit: Quoted post has been deleted}
It is being actively supported by legacy devices that can't handle encryption and on ROMs made by unknowingly devs.
Also you were told multiple times that encryption is not an optional thing, especially on T. And some users do care about their data not being just accessible when the device gets stolen.
{
"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 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 restores 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 our Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
SUPPORTED DEVICES
- zippo (L78051)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
Please NOTE! As of LineageOS 19.1? We do NOT support bootloader locked! You MUST unlock your bootloader to use this version!
- Make sure your phone is running firmware from at least CN 12.5.332. If not? Please download and install it via recovery. It can be flashed before the ROM
If you want to follow the official instructions for bootloader unlock? Please go to the LineageOS Wiki here:
https://wiki.lineageos.org/devices/zippo/install
If you want to preserve a locked bootloader? Download and follow the instructions in this zip and then follow the official wiki instructions but skip the bootloader unlock section.
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official instructions on the LineageOS Wiki here:
https://wiki.lineageos.org/devices/zippo/update
HOW TO INSTALL LINEAGEOS WITH TWRP
Please NOTE! As of LineageOS 19.1? We do NOT support bootloader locked! You MUST unlock your bootloader to use this version!
- Make sure your phone is running firmware from at least CN 12.5.332. If not? Please download and install it via recovery. It can be flashed before the ROM
- Download the LineageOS and firmware zips. (see Downloads)
- Boot into TWRP.
- Copy the downloaded zip files to the internal storage of the device.
- Perform a backup of your current ROM. (Optional)
- RECOMMENDED: Do a factory reset (clean wipe)! No support if you didn't! (Wipe Dalvik, system, cache and format data)
- NOTE: If coming from stock ROM? You MUST format data (Wipe > tap "Format Data" button > type "yes" > keyboard checkbox)
- Flash firmware and LineageOS zips.
- Optional: Install the Google Apps addon package. (see Downloads)
- Reboot to system.
HOW TO UPDATE LINEAGEOS WITH TWRP
- Download the LineageOS zip(s). (see Downloads)
- Copy the downloaded zip files to the internal storage of the device.
- Reboot to TWRP.
- Flash LineageOS. (Wiping Dalvik and Cache is optional, but recommended)
- Reboot to system.
MAIN DOWNLOADS
TWRP for zippo: Official
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Lineage:
- Official:
LineageOS Downloads
download.lineageos.org
- Unofficial:
Package lineage-20 - lineageos-for-zippo - OSDN
Package lineage-20 - lineageos-for-zippo #osdn
osdn.net
GOOGLE APPS (GAPPS) DOWNLOADS
- MindTheGapps:
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Wichaya GCam APKs - Google Camera Port
Modified Google Camera app by Wichaya.
www.celsoazevedo.com
Recommended version:
https://www.celsoazevedo.com/files/android/google-camera/dev-wichaya/f/dl5/
Recommended config:
https://osdn.net/projects/lineageos-for-zippo/releases/76575
FIRMWARE DOWNLOADS
Minimum required versions:
- zippo (L78051) CN 12.5.365
https://osdn.net/projects/lineageos-for-zippo/releases/p17514
DEVELOPER RESOURCES
https://github.com/lenovo-sm8150/local_manifests/
GitHub - LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_lenovo_zippo
Contribute to LineageOS/android_device_lenovo_zippo development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_lenovo_sm8150
Contribute to LineageOS/android_kernel_lenovo_sm8150 development by creating an account on GitHub.
github.com
HOW TO CONTRIBUTE
Send your patches up for review: https://review.lineageos.org/
Read the guides on the LineageOS Wiki: https://wiki.lineageos.org/
Source Code: https://github.com/LineageOS
DONATIONS
Pay Marc Bourgoin using PayPal.Me
Go to paypal.me/ThEMarD85 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com
KNOWN BUGS
Currently only works with bootloader unlocked
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Fingerprint icon is too low compared to actual location of the scanner
Heyyo, allow me to introduce myself. I am Marc "ThE_MarD" Bourgoin and I maintain LineageOS and TWRP for the LeEco Le Max 2 (X2) and was crowdfunded a zippo which I will maintain LineageOS for (with selinux enforcing of course) and maybe assist with TWRP later. I also own a Motorola Edge 30 (dubai) which I maintain LineageOS for, Asus Zenfone 5z (Z01R), and I was also donated a Motorola Moto X4 (Payton) which I maintain LineageOS and TWRP for.
I'd like to take this moment to also thank anyone who donated to the crowdfunding campaign for my zippo! Without you? I wouldn't have this epic device in my hands to work on.
Also MAJOR thanks to Zhenxiang Chen (aka pasta_con_tonno, Lucchetto) for all the amazing work he has done on zippo.
Special thanks to Einar Gednochsson (aka kanstmablason, pete80pro) for organizing the crowdfunding campaign for my zippo and also a new one for KuranKaname so he can revamp our kernel.
Thanks also to hypnz, chema f, gawin and Lucky for also working in zippo and to HighwayStar who started the initial trees for heart (Lenovo z5 Pro GT) which zippo trees are based upon and Art_Chen for working on heart and zippo and also bringing us FOD Dimming and DC Dimming.
Thanks again to Zhenxiang and Chema f for figuring out and implementing the QFIL recovery and vbmeta while keeping the bootloader locked
Heyyo, LineageOS 20 official is out and the first build for zippo is up!
@ThE_MarD ,
Will you be including this commit the hardware fix/support for the camera (camera: Expose aux cameras in third party apps) from Chemas Evo build in your Lineage build? I'd rather not have google services installed to use GCAM in order to access the other lens' and the ZUI camera does not install correctly anymore for 13 (it did for 12, partially). There are other apps that don't rely on g-services that are able to access the hardware (HIDL?) switch to select which lens is used for image processing.
Heyyo @project_2501 , after checking with other devs about that commit and also how aux cameras are set up? I think for that we can just modify our props in the device tree tbh. The problem we currently have is we are limiting it to only a few app names. We could transition to an aux camera blacklist since there's probably only a handful of apps that would screw up (I can't remember if it was here or my Asus Zenfone 5z, but the Adobe Scan app would screw up and fail to initialize any camera) so we could just tackle a blacklist as crappy apps show up lol
As you can see here, we mainly expose aux cameras to a few apps and others have to essentially find out themselves like gcam mods
android_device_lenovo_sm8150-common/system.prop at lineage-20 · LineageOS/android_device_lenovo_sm8150-common
Contribute to LineageOS/android_device_lenovo_sm8150-common development by creating an account on GitHub.
github.com
@ThE_MarD ,
Will the blacklist instead of a whitelist be applied on the next scheduled build? Thank you for addressing it.
@project_2501 sorry not yet as I need to test it first and I haven't had time yet
Heyyo, lineage-20.0-20230122-UNOFFICIAL-zippo test build is going up! ! It has a new rebased kernel by MikeNG. Please test all functions. It also has a change to swap the aux camera allowed list to an aux camera exclude list to keep things easier and only exclude apps that don't play well with aux cameras so please test a lot of camera apps
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo - OSDN
Release lineage-20 lineage-20.0-20230122-UNOFFICIAL-zippo - lineageos-for-zippo #osdn
osdn.net
@project_2501 if you could please test this build. You can swap between unofficial and official builds at any time
Switching between the camera lens' works (still don't see 48mp for the main lens' resolution); install almost hanged on patching vendor which I found odd. Camera app believes there are six cameras for some odd reason and will crash if selecting the sixth camera, I'm guessing it's also referencing the video profile because it doesn't crash in video mode when selecting the sixth camera (dual lens for video or mixed up with front lens' maybe)? Can you provide a link to the source for the kernel?
@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there
ThE_MarD said:
@project_2501 which camera app are you trying btw?
Source code links are in the first post please check there
Click to expand...
Click to collapse
Open Camera.
I'm unfamiliar with MikeNG and kernel modifications he may have committed when looking at the source code for the kernel, just wondering since you stated it was using a different kernel (than official LOS?).
@project_2501 oh, Open Camera does things a lot differently than other camera apps so tbh I don't think there's a way to configure it... So I'd recommend just sticking with Aperture or use a gcam mod... But from what you said Open Camera is now seeing more camera apps so the change in aux camera lists commit is working then?
@ThE_MarD , yes I can switch between all the lens'. System stability has not been jeopordized, the app will just crash if trying to process from the sixth camera ID. Do you remember what modes the ZUI camera app had? Was there a dual (both front and back camera) mode? Maybe the sixth profile is for the front camera and the app doesn't switch to it when cycling through the lens' (front camera can still be accessed with a different on screen UI switch anyways). The problem in itself is app related; regardless, the commit works and should be included in the next build for others like myself who enjoy a clean minimalist build with full access to the hardware.
Hi, i'm on firmware 11.0.405 ST.
Now i'm still waiting my SN from Lenovo to unlock bootloader.
Newbie question:
After installing TWRP --> Wipe > tap "Format Data" button > type "yes" > keyboard checkbox > Flash firmware CN 12.5.332 > reboot to recovery or reboot to system ?
Thanks a lot for the rom!
Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.
ThE_MarD said:
Heyyo @danz852, after doing the format data, flash firmware and flashing ROM? You can optionally install any addons (such as GApps) and then reboot to system or skip the addons and reboot to system.
Click to expand...
Click to collapse
@ThE_MarD , thanks for the reply. Appreciated
I'm still waiting file from Lenovo to unlock bootloader.
Finally got the file to unlock bootloader.
I flashed twrp > shut down the phone > hold Volume Up + Power > but it cannot boot to recovery, only show fastboot/bootloader.
Then I tried I flashed twrp > shut down the phone > Volume Down + Power > fastboot mode > then i select recovery mode > phone restarted > only returned to fastboot mode again.
Any help to solve this problem? failed to flash twrp recovery.
Thanks in advance.
@danz852 just to check, you're flashing it to the recovery partition?
The TWRP website has the full instructions too
Lenovo Z6 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Code:
fastboot flash recovery twrp.img
Otherwise you can try first via Lineage Recovery and follow the LineageOS wiki instructions
Install LineageOS on zippo | LineageOS Wiki
wiki.lineageos.org
Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.html to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.
danz852 said:
Hi, thanks for fast reply.
Yes i'm flashing it to the recovery partition (fastboot flash recovery twrp.img). The result was success. But still cannot boot to twrp.
FYI: I'm using file from this https://club.lenovo.com.cn/thread-7839615-1-1.htmll to unlock the bootloader because at least until now i didn't receive unlock file from Lenovo.
I tried to flash twrp-3.7.0_12-0-zippo then tried Lineage recovery , flashing was success but still cannot boot to recovery.
After that flashed TWRP 3.4.0 by @mauronofrio. this one is working and boot to twrp recovery. I proceed with Wipe Dalvik, system, cache and format data. Then ADB sideload firmware CN 12.5.332. Continue with ADB sideload LineageOS found no problem with the installation the proceed reboot to System (it's written No OS Installed!), I keep continue to reboot to System anyway. It stuck at Lenovo Logo the restart by itself back to Lenovo logo again and so on.
Maybe because TWRP 3.4.0 is not working for Android 13.
Now I'm trying to sideload firmware L78051_CN_11_5_229_Q_Stable_recovery., because i think it will be working with TWRP 3.4.0 but the result is the same, end up with Lenovo logo then it restart by itself again and again.
Click to expand...
Click to collapse
UPDATE:
Finally it worked out:
I'm still using TWRP 3.4.0. Copy firmware L78051_CN_11_5_229_Q_Stable_recovery to internal storage then flash it. Reboot to System. It said my phone partition is corrupted .
Then i reboot the phone to Fastboot mode. I checked bootloader is Locked > proceed with fastboot flash unlock sn.img > fastboot oem unlock-go > reboot to system. After enable USB debugging in Developer Option > reboot to recovery > Wipe Dalvik, system, cache and format data > flash CN 12.5.332 and LineageOS. > reboot to system > Finally it booted to Lineage.
I'm happy. Thanks again @ThE_MarD for the rom!!!