Develop Bugs

[RECOVERY][arm64]TWRP Recovery [3.2.2-r1] [10 July 18]

{
"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 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This is my own unofficial customized build of 64 bit twrp for athene. It can be used on both Nougat and Oreo (32 bit and 64 bit ROMs) without any problem.
Known Bugs:
Encryption will not work. (Will be hopefully fixed in future builds) Not tested yet.
Changelog:
~~ -r2
* Overhaul twrp tree and add arm64 support
~~ -r1
* Based on AOSP/OmniROM 8.0.0_r32 release
* Fix stuck on 'black' screen entering recovery
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
How to flash:
By fastboot:
* You should have an unlocked bootloader and adb and fastboot set on your computer properly. Check this thread if you haven't done it already.
* Download the .img file on your computer and keep it in your adb folder (Windows only)
* Boot to fastboot mode and then connect your phone to the computer. Open a command window/terminal and
type this command:
To temporarily boot twrp:
Code:
fastboot boot <filename.img>
To flash it to the recovery partition:
Code:
fastboot flash recovery <filename.img>
~Note: Linux users might want to add "sudo" before the respective commands.
*Now manually reboot to the recovery mode using the volume down keys. The current ROM will patch the recovery partition to its earlier state if this step isn't performed and you directly reboot to the system.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
~From presently installed TWRP on the device:
* Copy the .img file to your phone and reboot to recovery
* Tap Install > Choose Flash Image > Navigate to the path where you copied the .img file and choose it.
* Choose Recovery Partition
* After the install being successful, go to home and tap Reboot > Reboot Recovery.
At this point, twrp should greet you and after you allow modifications, do whatever you want to. :good:
Downloads:
Latest build: Direct Link
Older Builds: [url]https://sourceforge.net/projects/twrp-athene/files/[/URL]
XDA:DevDB Information
twrp-athene, Tool/Utility for the Moto G4 Plus
Contributors
tywinlannister7
Source Code: [url]https://github.com/omnirom/android_bootable_recovery[/URL]
[url]https://github.com/rajatgupta1998/android_kernel_motorola_msm8952[/URL]
Version Information
Status: Beta
Created 2017-12-20
Last Updated 2017-12-20

is it compatible with shreps twrp backup?

Ayan Uchiha Choudhury said:
is it compatible with shreps twrp backup?
Click to expand...
Click to collapse
Yes, should work :good:

thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem

arun4777 said:
thanksss dev for your work dev
i have noob qn
can i restore aosp oreo Rom data backup to lineage rom without problem
Click to expand...
Click to collapse
That's not related to twrp. Restoring the whole data partition from one rom to another causes problems for sure. Better to use titanium backup and backup/restore user apps with it.

This should work with the G4 (Regular non Plus model) Right?

Vaizen said:
This should work with the G4 (Regular non Plus model) Right?
Click to expand...
Click to collapse
Yes [emoji106]
Sent from my Moto G4 Plus using Tapatalk

tywinlannister7 said:
Yes [emoji106]
Click to expand...
Click to collapse
Actually it didn't let me flash latest RR. Had to flash official version for it to flash correctly.

Update: 30 Dec 2017
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download

tywinlannister7 said:
Changelog
*Add support for flashing 64 bit ROMs
*Fix bugs from -r1 except encryption :3
Download:
https://sourceforge.net/projects/twrp-athene/files/twrp-3.2.1-r2-arm64-tywinlannister7.img/download
Click to expand...
Click to collapse
Will i able to flash 32 bit also and does backup restores?

Can I Flash 32 bit ROM and 64 with this recovery?

Luis Infante said:
Can I Flash 32 bit ROM and 64 with this recovery?
Click to expand...
Click to collapse
Yes u can

StevenFernandes said:
Yes u can
Click to expand...
Click to collapse
Thanks

i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev????

arun4777 said:
i m facing a minor bug in my recovery it does not show exact time of device
and i had to set wrong time zone for see accurate time in recovery ......
is it a known bug?? or am i the only one facing it?
im on LOS 15.1 WITH stock kernal
thanks for fast update dev
Click to expand...
Click to collapse
It's a bug found on many twrp builds. I don't know if it's device specific.

I notice they Ghost touch with they USB cable and PC connected for ADB Sideload (and this affect to the ROMs)
---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------
I forgot to say that in this recovery for arm64 3.2.1.0 I don't have the arrow of the mouse appearing sometimes in the center of the screen (always on recovery, and sometimes on the system)

When i flash via fastboot the reovery, fastboot send me this error?
target reported max download size of 536870912 bytes
sending 'recovey' (14840 KB)...
OKAY [ 0.589s]
writing 'recovey'...
(bootloader) Invalid partition name recovey
FAILED (remote failure)
finished. total time: 0.597s
Click to expand...
Click to collapse

striplex said:
When i flash via fastboot the reovery, fastboot send me this error?
Click to expand...
Click to collapse
Yeah, see what you type: "recovey" but the partitions name is recovery

work roms 32 and 64 bits?

biel.paes said:
work roms 32 and 64 bits?
Click to expand...
Click to collapse
If you looked a few posts before you would clearly know that, yes, this build of twrp supports both 32 and 64 bit roms. Please use the search function before posting!

[OFFICIAL] TeamWin Recovery Project 3.3.1 For Zuk Z2 Plus

{
"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"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for our ZUK Z2 / Lenovo Z2 Plus (z2_plus, z2131, z2132).
This is an official recovery support thread.
Known Issues
None
Requirements
Unlocked bootloader
Common sense and a Z2
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.

Reserved !!

Reserved!
Thanks for the wonderful job!

Why we are going back to the old days that mounting /factory as /vendor? Does it affect flashing GSI?

getting an error in twrp saying "Failed to mount '/vendor' (Invalid argument)
Edit : I had flashed stock ROM , locked bootloader and then unlocked it back and flashed the latest twrp , and it works like a charm. Thanks for the new twrp mate

akshay pro said:
getting an error in twrp saying "Failed to mount '/vendor' (Invalid argument)
Click to expand...
Click to collapse
Same here...

Gibranibang said:
Same here...
Click to expand...
Click to collapse
Bro , u gotta flash vendor to factory from the current twrp and flash the latest twrp , then the problem will be solved

akshay pro said:
Bro , u gotta flash vendor to factory from the current twrp and flash the latest twrp , then the problem will be solved
Click to expand...
Click to collapse
Still same unable to mount vendor
I flshed vendor to factory and reboot(twrpbuilder)
Then flashed official factory twrp and reboot.
Any solution ?

akshay pro said:
Bro , u gotta flash vendor to factory from the current twrp and flash the latest twrp , then the problem will be solved
Click to expand...
Click to collapse
I've followed the steps, but i kept getting error everytime i try to install the factory rom

Gibranibang said:
I've followed the steps, but i kept getting error everytime i try to install the factory rom
Click to expand...
Click to collapse
So go via my original way , flash stock rom , update it to the latest version and flash the twrp recovery now. Done

Support you

Hey guys, TWRP 3.3.0 is out
Go and download it in the first post
The branch has also been changed to android-9.0 for z2_plus meanwhile

DD3Boh said:
Hey guys, TWRP 3.3.0 is out
Go and download it in the first post
The branch has also been changed to android-9.0 for z2_plus meanwhile
Click to expand...
Click to collapse
There is no link for 3.3.0! Is not up yet?

mondechristo1 said:
There is no link for 3.3.0! Is not up yet?
Click to expand...
Click to collapse
Yeah it will be out soon
It's weird because for z2 row it has been built already.

TWRP 3.3.0 is up now!
https://eu.dl.twrp.me/z2_plus/twrp-3.3.0-0-z2_plus.img.html

mondechristo1 said:
TWRP 3.3.0 is up now!
https://eu.dl.twrp.me/z2_plus/twrp-3.3.0-0-z2_plus.img.html
Click to expand...
Click to collapse
Deleted

PLEASE MAKE TWRP 3.3.0 for Vendor based ROM Devs
DD3Boh said:
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for our ZUK Z2 / Lenovo Z2 Plus (z2_plus, z2131, z2132).
This is an official recovery support thread.
Known Issues
None
Requirements
Unlocked bootloader
Common sense and a Z2
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.
Click to expand...
Click to collapse
Sir please make TWRP 3.3.0 for Vendor ROM or Make one TWRP that supports both vendor as well as factory by just flashing v2f or f2v in one single TWRP it will be more easy thank you very much for this TWRP.

A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery

DD3Boh said:
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
Click to expand...
Click to collapse
Hey dev i just have a question ..... Is it possible to add a pattern lock in twrp ???? I know it's silly but at the same time it will secure or phones surely ..... I'm just curious about it

[RECOVERY][3.5.2_9-2][Mi A2 Lite] Unofficial TWRP recovery for Xiaomi Mi A2 Lite

{
"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 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Open Source
- Payload.bin support (ROM flashing works)
- Proper MTP support (for both 4.9 and 3.18 kernels)
- Working decryption for both FBE and FDE
- Adoptable Storage is working
- Android 11 support (No bootloops to recovery mode)
- NTFS, F2FS, exFAT, FAT32 support for SD Cards and USB drives
- Ability to flash splash images directly to the splash partition
- Adjusted theme to account for the notch (the clock doesn't overlap with the notch)
- No TWRP app installation prompts
- Older 3.4.0 button-style reboot menu instead of the newer listbox-style one
- Addon.d script to make TWRP survive ROM updates
Download:
TWRP image: https://drive.google.com/file/d/19ysSbW31NG4QF5OClbox-mArIb17KbpT/view?usp=sharing
TWRP Installer: https://drive.google.com/file/d/1-wk_0kOe_e-2XDDiv08BxJhn1ixWXjUw/view?usp=sharing
Installation Instructions:
- Make sure your bootloader is unlocked. If not, unlock it first.
- Reboot to Bootloader (aka Fastboot mode)
- Execute:
Code:
fastboot boot twrp-3.5.2_9-2-daisy-unofficial.img
- Flash the TWRP Installer zip to keep TWRP permanently
Notes:
- You can ignore any "Failed to unmount /vendor: Device or resource busy" errors since they do not cause any issues (this
happens when switching the active slot while the vendor partition is mounted).
- This TWRP does not have the newer 3.5.0 theme changes in the reboot menu because it is confusing for a significant amount
of users and does not match the rest of the button-style design.
- The TWRP app checks and prompts have been completely removed due to the app causing a lot of issues including bootloops
since it is not designed for A/B devices.
- The portrait_hdpi theme has been adjusted to have more padding in the status bar and to account for the presence of the
notch (the clock's position has been modified in order for the clock not to get overlapped by the notch)
- TWRP's addon.d will only work in the following scenarios:
a) When updating your ROM through the ROM's Updater application
b) When dirty-flashing a newer build of the same ROM you have installed from recovery
- TWRP's addon.d (TWRP survival) may not work in all ROMs as some ROMs choose not to have permissive update-engine domain. This essentially results in SELinux denials, preventing the addon.d script from executing when SELinux is enforcing. You can read more about the said issue here (https://github.com/topjohnwu/Magisk/commit/cba0d040000d6ff38c6646bb9d7daa12beae2878)
Source code:
Recovery Source: https://github.com/LinkBoi00/android_bootable_recovery
Device tree: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Kernel source: https://github.com/LinkBoi00/twrp_kernel_xiaomi_daisy
XDA:DevDB Information
TWRP-3.5.2_9-2-Unofficial, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
LinkBoi
Source Code: https://github.com/LinkBoi00/twrp_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-2
Stable Release Date: 2021-05-04
Created 2020-10-19
Last Updated 2021-05-04

Reserved

Reserved

i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have

Antho02 said:
i'll give a try. still using twrp-3.3.1-dees_troy-daisy cuz its the only one that doenst ask a decrypt key that i dont have
Click to expand...
Click to collapse
decryption does not work in this build, im looking into a fix. Custom roms do not support decryption anyways so it's a minor issue for now

The handling of the "Adoptable Storage" still broken.
E:Failed to mount decrypted adoped storage device
Click to expand...
Click to collapse
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)

PC295 said:
The handling of the "Adoptable Storage" still broken.
DATA is not encrypted (I use a custom ROM with Force-Encryption-Disabler)
Click to expand...
Click to collapse
Can you send me logs of that issue (advanced > copy log > tick the "include kernel log" option and swipe in the "bar")? After doing this can you also try official twrp and tell me if that has the same issue?
Thanks for the feedback
PS: Can you join a telegram group (https://t.me/XMiA2Lite)? If /When you join there, mention me (@runrunrun00) and your issue, thanks in advance

The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...

PC295 said:
The problem is with all TWRPs. (Official, Offain, this)
I have to use OTG to install Custom ROMs etc.
It is probably not a TWRP problem but one of the CustomROMs?
Unfortunately, I also find that there are adoptable storage issues in many custom ROMs.
It got noticeably worse with Android 10 ROMs.
For example the migration via key file (/data/misc/vold/....key) does not work everywhere.
Or the memory only works after setting up the microSD several times.
Log attached...
Click to expand...
Click to collapse
i might have found a way to fix this issue (in the bootable twrp, the installed one depends on your rom)

again, with twrp Bogdan, for my work fine, no problem with storage external

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what problem do you have with external storage?

dochdoc said:
again, with twrp Bogdan, for my work fine, no problem with storage external
Click to expand...
Click to collapse
what's your issue exactly?

nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me

dochdoc said:
nothing, no problem with this custom recovery (TWRP 3.3.1 by @ScaryMen1325), work fine with me
Click to expand...
Click to collapse
And what's the issue with this recovery regarding external storage (not scarymen's)?

LinkBoi said:
And what's the issue with this recovery regarding external storage (not scarymen's)?
Click to expand...
Click to collapse
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.

PC295 said:
If you only boot from TWRP, you can't access Adptable Storage.
There is an installed TWRP required.
Click to expand...
Click to collapse
Is it possible to contact me on telegram again? I have one version in test that most likely fixes your issue

When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.

Yyres55 said:
When I use Offain TWRP PC output is like this
Code:
downloading 'boot.img'...
OKAY [ 15.830s]
booting...
OKAY [ 0.748s]
finished. total time: 16.578s
and then phone reboot to stock Android
When I use TWRP from this thread PC output is same but phone boot Android Recovery and it says Can't load Android system. Your data be corrupt and there are 2 options Try Again and Factory Reset when I try again it boots to stock.
Click to expand...
Click to collapse
If you want, you can contact me on telegram, I might have a fixed version there

LinkBoi said:
If you want, you can contact me on telegram, I might have a fixed version there
Click to expand...
Click to collapse
It worked. I tried another USB port and it's okay

hi, is there any plan to support encryption??

biladina.id said:
hi, is there any plan to support encryption??
Click to expand...
Click to collapse
Yup, of course. In the next release, 3.5.0, every bug I listed will be fixed, including Decryption, Android 11 support and more. If you want to test the release candidate (which is still 3.4.0 because twrp hasn't released 3.5.0 yet), you can join the telegram group below:
www.t.me/DaisyTestflight
New update will be released in XDA when TeamWin releases 3.5.0

Development [ROM][OFFICIAL][lemonadep][12] LineageOS 19

{
"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 :
https://wiki.lineageos.org/devices/lemonadep
Downloads :
https://download.lineageos.org/lemonadep
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (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:

This is pretty ****ing huge

Flashing...

Unlike other AOSP 12 ROMs, does it have to be on the latest version of oos12 ?

alb94 said:
Unlike other AOSP 12 ROMs, does it have to be on the latest version of oos12 ?
Click to expand...
Click to collapse
If that's what the installation / upgrade guide says...

alb94 said:
Unlike other AOSP 12 ROMs, does it have to be on the latest version of oos12 ?
Click to expand...
Click to collapse
Yes! It's higlighted on lineage instructions page:
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
[SOURCE: https://wiki.lineageos.org/devices/lemonadep/install]

LuK1337 said:
If that's what the installation / upgrade guide says...
Click to expand...
Click to collapse
Sorry for the question, English is not my native language, sometimes the translations are confusing kk. Thanks for the reply, and congratulations for the work.

EugenStanis said:
Yes! It's higlighted on lineage instructions page:
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
[SOURCE: https://wiki.lineageos.org/devices/lemonadep/install]
Click to expand...
Click to collapse
Can't it flashed from 11.2.10.10?-Never mind, it needs the vendor_boot
Can we use this boot.img for Magisk 24.3?

I got Qualcomm Crash Dump when I tried to upgrade from Lineage 18.1. I'll try a clean install directly from Oxygen 12 later today.

C.Flat said:
I got Qualcomm Crash Dump when I tried to upgrade from Lineage 18.1. I'll try a clean install directly from Oxygen 12 later today.
Click to expand...
Click to collapse
All according to plan. Both install/upgrade says that A12 FW is required, and there's /fw_upgrade page that you can follow before sideloading lineage 19 (just don't do fastboot reboot ^.^).

try to upgrade the fw with this tutorial:
Update firmware on lemonadep | LineageOS Wiki
wiki.lineageos.org
if i start:
fastboot flash --slot=all abl abl.img
i get:
"fastboot: error: Could not check if partition abl has slot all"
if i try:
fastboot flash --slot=a abl abl.img
i get:
"
Sending 'abl' (2132 KB) OKAY [ 0.054s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed"
why ? what is the failure ?

LuK1337 said:
All according to plan. Both install/upgrade says that A12 FW is required, and there's /fw_upgrade page that you can follow before sideloading lineage 19 (just don't do fastboot reboot ^.^).
Click to expand...
Click to collapse
Can we flash the recovery after flashing the vendor_boot?

xerves78 said:
try to upgrade the fw with this tutorial:
Update firmware on lemonadep | LineageOS Wiki
wiki.lineageos.org
if i start:
fastboot flash --slot=all abl abl.img
i get:
"fastboot: error: Could not check if partition abl has slot all"
if i try:
fastboot flash --slot=a abl abl.img
i get:
"
Sending 'abl' (2132 KB) OKAY [ 0.054s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed"
why ? what is the failure ?
Click to expand...
Click to collapse
You aren't in fastbootd.

benhidalgo said:
Can we flash the recovery after flashing the vendor_boot?
Click to expand...
Click to collapse
No clue why you'd flash either of these manually when you're upgrading from 18.1.

LuK1337 said:
No clue why you'd flash either of these manually when you're upgrading from 18.1.
Click to expand...
Click to collapse
I was on the latest OOS12 LE2123_11.C.47: LE2123_11.C.47_1470_202203102117
reboot to bootloader
flashed vendor_boot.img
flashed lineage-19.1-20220530-recovery-lemonadep.img slot b
then reboot to recovery and fail
then tried slot a and now is looping to bootloader

benhidalgo said:
I was on the latest OOS12 LE2123_11.C.47: LE2123_11.C.47_1470_202203102117
reboot to bootloader
flashed vendor_boot.img
flashed lineage-19.1-20220530-recovery-lemonadep.img slot b
then reboot to recovery and fail
then tried slot a and now is looping to bootloader
Click to expand...
Click to collapse
Try to also flash https://mirrorbits.lineageos.org/full/lemonadep/20220531/dtbo.img?

LuK1337 said:
You aren't in fastbootd.
Click to expand...
Click to collapse
yes, this was the problem
but now i get a Qualcomm Crash Dump after upgrade the fw and upgrade los via sideload commands and reboot

LuK1337 said:
Try to also flash https://mirrorbits.lineageos.org/full/lemonadep/20220531/dtbo.img?
Click to expand...
Click to collapse
I keep looping back to bootloader

LuK1337 said:
Try to also flash https://mirrorbits.lineageos.org/full/lemonadep/20220531/dtbo.img?
Click to expand...
Click to collapse
This fixed my fastboot loop.

benhidalgo said:
I keep looping back to bootloader
Click to expand...
Click to collapse
Flashing dbto and then reflashing the recovery image fixed my loop.

[OFFICIAL] LineageOS 20 for the Google Pixel 2

{
"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 2
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.[/CENTER]
Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 2.
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.
walleye - Official builds​
walleye - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
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_wahoo

hi Downloads: link no20,only 19.1

github-wang said:
hi Downloads: link no20,only 19.1
Click to expand...
Click to collapse
yup, minor issues, rebuilding tonight

Thank you for keeping my old device up to date.
The recovery image does not seem to work. Flashes fine onto the device. Fastboot output:
Code:
target reported max download size of 536870912 bytes
sending 'boot_b' (32768 KB)...
OKAY [ 0.091s]
writing 'boot_b'...
OKAY [ 0.161s]
finished. total time: 0.253s
But when I reboot the device, it says "ERROR: BootLinux Failed: Bad Buffer Size" and I am unable to boot into recovery or into the System.

lineage-20.0-20221109-recovery-walleye,the boot damage ,But when I reboot the recovery， it says "ERROR: BootLinux Failed: Bad Buffer Size" and I am unable to boot into recovery or into the System.

try booting into the recovery rather than flashing. same issue on PE13 just booting into it worked out fine

DrupadSachania said:
try booting into the recovery rather than flashing. same issue on PE13 just booting into it worked out fine
Click to expand...
Click to collapse
good i try thanks

Hi @npjohnson , I've just downloaded your latest build for lineageos 20.
I'm getting the same Error BootLinux error.
When i follow the guide, it won't allow me to boot into the latest '....20' recovery.
Thankyou for all your work.
I even tried installing your latest 19.1 and following the upgrade guide. ADB reboot sideload, adb sideload package ....20.
I had the error about downgrading, but after installation, same error at bootloader

Hawkeye77 said:
Hi @npjohnson , I've just downloaded your latest build for lineageos 20.
I'm getting the same Error BootLinux error.
When i follow the guide, it won't allow me to boot into the latest '....20' recovery.
Thankyou for all your work.
I even tried installing your latest 19.1 and following the upgrade guide. ADB reboot sideload, adb sideload package ....20.
I had the error about downgrading, but after installation, same error at bootloader
Click to expand...
Click to collapse
Working on it, should be an easy fix.
taimen works fine

Thankyou @npjohnson , just installed the Latest unofficial LOS 20 13th.
It ran faultless.
You are a magician.
Edit: only thing I've found so far is it's not passing safety net. Play store is not certified and wallet won't allow bank card.
Will this, or can this be fixed in future updates? Or do you suggest the Magisk route?

Hawkeye77 said:
Thankyou @npjohnson , just installed the Latest unofficial LOS 20 13th.
It ran faultless.
You are a magician.
Edit: only thing I've found so far is it's not passing safety net. Play store is not certified and wallet won't allow bank card.
Will this, or can this be fixed in future updates? Or do you suggest the Magisk route?
Click to expand...
Click to collapse
Aware, this build as "Get it out there for feedback" the next several will tune all that stuff.

Thank you very much @npjohnson for your continued work on this old device.
Could you please share your change for this "bad buffer size" boot error. Magisk has got the same problem. Thanks.

tblr0ne said:
Thank you very much @npjohnson for your continued work on this old device.
Could you please share your change for this "bad buffer size" boot error. Magisk has got the same problem. Thanks.
Click to expand...
Click to collapse
It's published. Download newest.

npjohnson said:
It's published. Download newest.
Click to expand...
Click to collapse
I meant the code, so that Magisk could be fixed as well.

tblr0ne said:
I meant the code, so that Magisk could be fixed as well.
Click to expand...
Click to collapse
it's not code, I included too many things lol - our boot image is too small.

npjohnson said:
it's not code, I included too many things lol - our boot image is too small.
Click to expand...
Click to collapse
Hm, do you see a possibility on your side to get root working? That would be great.
(Magisk installs fine, but afterwards there is this "bad buffer size" boot error again.)

tblr0ne said:
Hm, do you see a possibility on your side to get root working? That would be great.
(Magisk installs fine, but afterwards there is this "bad buffer size" boot error again.)
Click to expand...
Click to collapse
Likely no. I can look.

tblr0ne said:
非常感谢 @npjohnson 继续使用这台旧设备进行工作。
您能否分享您对这个“缓冲区大小错误”引导错误的更改。Magisk 也有同样的问题。谢谢。
Click to expand...
Click to collapse
tblr0ne said:
I meant the code, so that Magisk could be fixed as well.
Click to expand...
Click to collapse
tblr0ne said:
Thank you very much @npjohnson for your continued work on this old device.
Could you please share your change for this "bad buffer size" boot error. Magisk has got the same problem. Thanks.
Click to expand...
Click to collapse
Hello, you can try this, with magisk can be rooted，i use it on lineages os 20-11.13 ，can boot ，it for tg groups
Google Pixel 2/XL | Chat，Of course, I still hope that sir can fix it​

Thanks, but since LOS is shipping with its own recovery this might lead to update issues.
And more important, please don't be offended, I won't recommend installing (pre-rooted) images from untrusted sources!

tblr0ne said:
Thanks, but since LOS is shipping with its own recovery this might lead to update issues.
And more important, please don't be offended, I won't recommend installing (pre-rooted) images from untrusted sources!
Click to expand...
Click to collapse
yes,I still hope that sir can fix it