Develop Bugs

[Unofficial] HTC U11+ TWRP Recovery

{
"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"
}
It have been about 2 years, I finally get a U11 plus to make TWRP device tree with working decrypt function.
Source: https://github.com/sabpprook/android_device_htc_ocm
Please download latest TWRP build in following link.
[Android 8.0]
twrp-3.3.1-0-ocm_171001.img
twrp-3.3.1-0-ocm_171201.img
twrp-3.3.1-0-ocm_180601.img
twrp-3.3.1-0-ocm_180901.img
twrp-3.3.1-0-ocm_181001.img
twrp-3.3.1-0-ocm_181101.img
[Android 9.0]
PS. watch out the last 6 digits at the filename, it must equal to your system's android patch level. e.g. 2017-12-01 (Dec, 2017) = 171201, otherwise TWRP will not decrypt data partition.
PS2. U11+ already get Android Pie update, but this update will break data decrypt function in TWRP recovery.
@nkk71, thanks all the works you've done for us.

Thank you very much!
https://i.imgur.com/71t8xrY.png
https://i.imgur.com/qebNB0C.png
https://i.imgur.com/ubxYZsN.png
https://i.imgur.com/gsbaG2K.png
https://i.imgur.com/xIW8llN.png
https://i.imgur.com/Fzrdhwt.png

Awesome!!

yay. now to get more dev support behind this!

excellent! Please, try to put up a github repo for it, if not already
Hopefully it works fine.
If HTC rolls out kernel sources, I might try some blind development, as I don't have the device, but wanna support it.

Should you need to unlock the official htcdev before they can put?

mapleshadow said:
Should you need to unlock the official htcdev before they can put?
Click to expand...
Click to collapse
Yes, unlock then you can boot it.

Thanks for this! Going to try and get it up and running later today - Need to unlock the BL first.

Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
OKAY [ 10.112s]
finished. total time: 11.006s
Click to expand...
Click to collapse
Any idea what's going on?

aurelienlux said:
Thanks for this however it doesn't seem to work for me. I've unlocked the bootloader, rebooted into bootloader mode via adb (adb reboot bootloader), tried to boot the twrp image (fastboot boot twrp-3.1.1-2_unofficial-ocm_2.img) and all I get is a black screen even though the commands seem to work at first:
Any idea what's going on?
Click to expand...
Click to collapse
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
http://featuresunlocker.com/root-install-twrp-recovery-htc-u11/
Yet sent from my amazing silver U11

jauhien said:
Did you flash the custom recovery ..?
P.S. Nothing of linked below worked out?
Yet sent from my amazing silver U11
Click to expand...
Click to collapse
I didn't flash since I wanted to test it out before using the fastboot boot command recommended in the original post. However this does not seem to work. I wanted to get twrp running so I could use magisk for root

Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.

aurelienlux said:
Went ahead and flashed it anyway and I'm happy to report that it worked and did not brick my device. So I still don't know why it won't let me fastboot boot but at least TWRP is now installed.
Click to expand...
Click to collapse
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.

tbalden said:
Be aware that you're now lacking the ability to ota update if you cannot get ahold of a stock recovery.
That's why booting only and making a backup of stock recovery boot and full system partition, is highly recommended.
Click to expand...
Click to collapse
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version

aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
Click to expand...
Click to collapse
OK, that's very professional. :good:
Just others be aware that you should make sure you have a way backwards.

aurelienlux said:
I bought the right version of the stock rom I'm running from en.pars-hamrah.com. It's a slightly sketchy looking site and it cost me 9$ but it should allow me to go back to stock easily
I'll share it here if people are interested. It's version 1.05.400.13 which is the latest version for the Hong Kong version
Click to expand...
Click to collapse
That would be fantastic and very good of you if you could share it. Many thanks!

@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly

sabpprook said:
@nkk71 Any idea of decryption problem?
Seems "/firmware" not symlink and "/vendor/bin/qseecom" sepolicy not set correctly
View attachment 4342230
Click to expand...
Click to collapse
Looks like you're building in android 7.1 for Oreo decrypt, won't work without the needed sepolicy changes and plat/non_plat contexts, please check the current gerrit updates for the standard HTC U11:
TWRP vold_decrypt patch: https://gerrit.omnirom.org/c/26652/
EDIT2: U11 Oreo decrypt device tree changes needed for a 7.1 build: https://gerrit.twrp.me/c/2756/
If you end up with decryption successful, but it doesn't actually mount /data, then you may even need an updated kernel https://gerrit.twrp.me/c/2761/
which is what we needed. EDIT: Obviously that's a U11 kernel update not a U11+ one, so don't try to use that kernel
Some things will still get changed. I also recommend you build in real DEBUG mode, the straces have much more info than a log or dmesg. by using TW_CRYPTO_SYSTEM_VOLD_DEBUG := true

Prot02018 said:
That would be fantastic and very good of you if you could share it. Many thanks!
Click to expand...
Click to collapse
There you go: https://drive.google.com/open?id=1nkzK_wbSgC6HSlOsNqOc79f94p7v_3wz
That's version 1.05.400.13. I managed to decrypt it successfully using the latest RUU Decryption Tool on Windows. I have a decrypted boot.img and system.img but I haven't yet uploaded those to my drive.

Waiting for your Good news.

[ROM][10.0][ARM64] crDroid v6.13 [CHANNEL][18.12.2020]

{
"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/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP(Download from here)
(optional) GAPPS(Download from here)
First time installation:
Download TWRP and run in terminal
Code:
fastboot boot TWRP.IMG
On your phone tap "Advanced", then "ADB Sideload"
On your computer run
Code:
adb sideload PATH/TO/CRDROID.ZIP
Repeat steps 2-3 for gapps or root
Back on the main screen click "Wipe", "Format data", Read warning then proceed to type "yes"
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Deivid21/android_kernel_motorola_sdm632
Download:
ROM https://sourceforge.net/projects/cr...roid-10.0-20201217-channel-v6.13.zip/download
Known issues:
You tell me
Visit official website @ crDroid.net
Moto g7 Play Telegram
crDroid Community Telegram
Donate to help me pay server costs

Screenshots - thanks to @Yshmanson

00p513 said:
Screenshots - thanks to @Yshmanson
View attachment 5160959View attachment 5160961View attachment 5160963View attachment 5160965View attachment 5160967View attachment 5160969
Click to expand...
Click to collapse
Hello, and thank you.
What's new in ver 6.13 ?

what steps would i take to load this onto phone with unlocked bl

yashor said:
Hello, and thank you.
What's new in ver 6.13 ?
Click to expand...
Click to collapse
Forget my comment above.
I had ver 6.11 & updated yesterday via OTA. I noticed when phone sleeps, update installing pauses. So, I had to keep screen awake until the process was completed.
Great work, thank you.

Hello @00p513
The 6.13 version is working well, installed 2 days before.
Bugs
1. The much needed MOTO EXTRAS not wrorking, giving force close error.
2. Ambient Dispplay not working, giving fore close error.
And also the rom is without ROOT access.

Is this 64bit rom? no special caution needed when using twrp adb sideload?

muhahsan2004 said:
Hello @00p513
The 6.13 version is working well, installed 2 days before.
Bugs
1. The much needed MOTO EXTRAS not wrorking, giving force close error.
2. Ambient Dispplay not working, giving fore close error.
And also the rom is without ROOT access.
Click to expand...
Click to collapse
I installed 6.13 one week ago, Moto Extras working fine!

CorleoneG said:
what steps would i take to load this onto phone with unlocked bl
Click to expand...
Click to collapse
Flash TWRP, then flash this rom. Wipe data and flash gapps if necessary

Lopwidth said:
Is this 64bit rom? no special caution needed when using twrp adb sideload?
Click to expand...
Click to collapse
all fine if your recovery is up to date!

muhahsan2004 said:
Hello @00p513
The 6.13 version is working well, installed 2 days before.
Bugs
1. The much needed MOTO EXTRAS not wrorking, giving force close error.
2. Ambient Dispplay not working, giving fore close error.
And also the rom is without ROOT access.
Click to expand...
Click to collapse
Unfortunately I cannot include root. Moto extras and ambient display works fine for me too. Can you back up your data and try a factory reset?

00p513 said:
Unfortunately I cannot include root. Moto extras and ambient display works fine for me too. Can you back up your data and try a factory reset?
Click to expand...
Click to collapse
What steps to follow to install root on our device?

yashor said:
What steps to follow to install root on our device?
Click to expand...
Click to collapse
You should be able to flash the "modded phh superuser" by Spaceminer

00p513 said:
Unfortunately I cannot include root. Moto extras and ambient display works fine for me too. Can you back up your data and try a factory reset?
Click to expand...
Click to collapse
OK, I'll try resetting the device in some spare time. Thanks

00p513 said:
You should be able to flash the "modded phh superuser" by Spaceminer
Click to expand...
Click to collapse
hello,
I flashed "modded phh superuser" and installed "phh-su" and reboot as normal. but when ES file explorer asks root permission it displays "root access not installed".
This is my 1st rooting, what am I doing wrong?

yashor said:
hello,
I flashed "modded phh superuser" and installed "phh-su" and reboot as normal. but when ES file explorer asks root permission it displays "root access not installed".
This is my 1st rooting, what am I doing wrong?
Click to expand...
Click to collapse
This keeps displaying: "su_binary is out of date"

yashor said:
This keeps displaying: "su_binary is out of date"
Click to expand...
Click to collapse
I think crDroid ships with its own root for adb debugging, maybe this is conflicting?

00p513 said:
I think crDroid ships with its own root for adb debugging, maybe this is conflicting?
Click to expand...
Click to collapse
So, what do you recommend I do to obtain root?

00p513 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/10.0/README.mkdn
Flashing Instructions:
Pre-installation:
TWRP(Download from here)
(optional) GAPPS(Download from here)
First time installation:
Download TWRP and run in terminal
Code:
fastboot boot TWRP.IMG
On your phone tap "Advanced", then "ADB Sideload"
On your computer run
Code:
adb sideload PATH/TO/CRDROID.ZIP
Repeat steps 2-3 for gapps or root
Back on the main screen click "Wipe", "Format data", Read warning then proceed to type "yes"
Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: Deivid21/android_kernel_motorola_sdm632
Download:
ROM https://sourceforge.net/projects/cr...roid-10.0-20201217-channel-v6.13.zip/download
Known issues:
You tell me
Visit official website @ crDroid.net
Moto g7 Play Telegram
crDroid Community Telegram
Donate to help me pay server costs
Click to expand...
Click to collapse
so to install twrp i have to do "fastboot flash twrp-3.4.0-0-channel.img"? (that's the name of the file once downloading, just asking to make sure since the forums are all crazy, then i just flash the rom in twrp with the gapps right, i have flashed roms on another phone but i'm double checking. thanks

alpole said:
so to install twrp i have to do "fastboot flash twrp-3.4.0-0-channel.img"? (that's the name of the file once downloading, just asking to make sure since the forums are all crazy, then i just flash the rom in twrp with the gapps right, i have flashed roms on another phone but i'm double checking. thanks
Click to expand...
Click to collapse
no use fastboot boot

[OFFICIAL] LineageOS 18.1 for the OnePlus One

{
"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"
}
OnePlus One
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the OnePlus One.
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.
Official Builds:
bacon
Unofficial - built once a month by me, includes GApps and Pixel goodies:
bacon
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Hardware-backed encryption is broken thanks to Google dropping support for legacy credential storage from AOSP 11.0, so we just feel back to software-backed encryption. This means it is a little slower, and taxing on the CPU, in addition to the fact upgrades from older LineageOS versions are not supported. The Wiki upgrade guide notes this as well.
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!
Kernel Source: https://github.com/LineageOS/android_kernel_oppo_msm8974

@npjohnson Thank you for your continued efforts into maintaining official builds for bacon. Thanks a lot. Really appreciate this.

@npjohnson Thanks a lot for maintaining it. Can't wait to flash it. Also, do you have any idea when the build will be available?

Unable to download 18.1. Not available on LineageOs website.

@npjohnson mate, I successfully installed it but there's this weird bug which isn't allowing me to get past the security lock. After entering the security pattern, the screen kind of blanks out and then refreshes back to the lock screen. After a while, the entire screen shuts off.
I did the whole installation process again, now the display is kinda dead. The lockscreen doesn't show, but the power options after long pressing the power buttin is shown. Is this a first build bug?? I'm reverting to LOS 17.1 for now

Oswald Boelcke said:
@npjohnson THREAD CLOSED as placeholder are not accepted! Further information.
Please advise the moderators team (best via the report function) to re-open the thread when a download is available, what's currently not the case via the provided download link, AND a link to your kernel source is available to achieve compliance with GPLv2.
Thread re-opened as I realised the build is now available for download.
@npjohnson Please provide a link to your kernel source within the next 5 days to avoid a new closure of the thread. Reference: XDA and the GPL
Click to expand...
Click to collapse
The kernel source, as our wiki clearly states (which I link, and even has build guides), that the link is https://github.com/LineageOS/android_kernel_oppo_msm8974

Purple-_-Tears said:
@npjohnson mate, I successfully installed it but there's this weird bug which isn't allowing me to get past the security lock. After entering the security pattern, the screen kind of blanks out and then refreshes back to the lock screen. After a while, the entire screen shuts off.
I did the whole installation process again, now the display is kinda dead. The lockscreen doesn't show, but the power options after long pressing the power buttin is shown. Is this a first build bug?? I'm reverting to LOS 17.1 for now
Click to expand...
Click to collapse
You need to format data before you upgrade.

done
Oswald Boelcke said:
Thanks for the information. I'd appreciate if you add this link to your OP. Please review the reference that I provided in my earlier post. Direct links are mandatory.
Click to expand...
Click to collapse

npjohnson said:
You need to format data before you upgrade.
Click to expand...
Click to collapse
so.. then.. not dirty update is possible?

drezz2 said:
so.. then.. not dirty update is possible?
Click to expand...
Click to collapse
Correct, as the OP and Wiki both say.

installation work as described, but i still went back to 17.1 because as i want to install my paid app's Play-Store want's me to pay again. Is this a Mindthegapps problem, or with android11

gerald_raaf said:
installation work as described, but i still went back to 17.1 because as i want to install my paid app's Play-Store want's me to pay again. Is this a Mindthegapps problem, or with android11
Click to expand...
Click to collapse
idk why - this affects some users randomly, wipe, and re-install - chances are it won't happen again.

Thank you LineageOS developers.
I'd like to suggest using the official microG release:
bacon
Track release status:
OnePlus One - LineageOS 18.1
LineageOS 18.1 Changelog for OnePlus One (bacon). This page is listing the official LineageOS 18.1 (Android 11 11.0) changes and downloads for OnePlus One (bacon).
www.lineageoslog.com

npjohnson said:
Correct, as the OP and Wiki both say.
Click to expand...
Click to collapse
not the same guide as previous versions? in older versions if I was able to do the dirty install

I have TWRP as my recovery with 17.1. Can I use my existing TWRP to install the 18.1 zip? Do I have to use adb sideload?

zzjea said:
I have TWRP as my recovery with 17.1. Can I use my existing TWRP to install the 18.1 zip? Do I have to use adb sideloa
Click to expand...
Click to collapse
I used the same TWRP recovery I used with 17.1. I installed the zip file, no problem just remember to format data.

cmpque said:
I used the same TWRP recovery I used with 17.1. I installed the zip file, no problem just remember to format data.
Click to expand...
Click to collapse
Thanks, that's what I thought. I have Google Backup on so most of my stuff will be recovered after the format and install.

Unfortunately I stuck on boot loop after install LSposed or Edxposed (clean install), any solution?!

gerald_raaf said:
installation work as described, but i still went back to 17.1 because as i want to install my paid app's Play-Store want's me to pay again. Is this a Mindthegapps problem, or with android11
Click to expand...
Click to collapse
A workaround for this issue is to install Aurora Store and login with your Google account. You'll be able to download your paid apps through Aurora Store, and then they'll be regularly updated via Play Store.

Had to go back to Lineage 17.1 because the new version doesn't let me recover my backups from my google account. Will wait for newer versions and will wait until there's open gapps for android 11.

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.

Question Denying OTA because it is a SPL downgrade

Hello.
I am trying to install LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip
I followed the instructions from LineageOS (main) https://wiki.lineageos.org/devices/lemonadep/install
but, of course, using the LineageOS for Microg recovery lineage-19.1-20220607-microG-lemonadep-recovery.img and zip.
I installed the dtbo.img and vendor_boot.img from the latest LineageOS repo - https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220628/
All good - until I flash the zip in recovery.
The I get:
E: Current SPL: 2022-06-05 Target SPL: 2022-05-05 this is considered a downgrade
E: Denying OTA because it's a SPL downgrade
How can I remedy the SPL error and flash successfully LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip?
{
"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"
}

anarchotaoist said:
Hello.
I am trying to install LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip
I followed the instructions from LineageOS (main) https://wiki.lineageos.org/devices/lemonadep/install
but, of course, using the LineageOS for Microg recovery lineage-19.1-20220607-microG-lemonadep-recovery.img and zip.
I installed the dtbo.img and vendor_boot.img from the latest LineageOS repo - https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220628/
All good - until I flash the zip in recovery.
The I get:
E: Current SPL: 2022-06-05 Target SPL: 2022-05-05 this is considered a downgrade
E: Denying OTA because it's a SPL downgrade
How can I remedy the SPL error and flash successfully LineageOS for Microg - lineage-19.1-20220611-microG-lemonadep.zip?View attachment 5650677
Click to expand...
Click to collapse
There's your issue, you are using a different vendor_boot and dtbo version. Notice how you downloaded the 20220628 files instead of the 20220611 ones, and also your recovery version is not matching either. Unfortunately, it seems you can't find files that exactly match your build, but I will do my best to point you in the right direction.
Try using https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ first. If that doesn't work, try https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220614/. Those builds are closer in date that the latest one, so this might remedy your issue.

razercortex said:
There's your issue, you are using a different vendor_boot and dtbo version. Notice how you downloaded the 20220628 files instead of the 20220611 ones, and also your recovery version is not matching either. Unfortunately, it seems you can't find files that exactly match your build, but I will do my best to point you in the right direction.
Try using https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ first. If that doesn't work, try https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220614/. Those builds are closer in date that the latest one, so this might remedy your issue.
Click to expand...
Click to collapse
Thanks for your reply! Yes, I suspected that! I tried 20220503 - as it was the earliest! It then failed to boot to recovery, so I restored the latest - but also had to flash boot.img.
Why do you recommend 0607? Hmm, are the earlier ones for LOS18 perhaps??
I will try in the morning!
Thanks!

anarchotaoist said:
Thanks for your reply! Yes, I suspected that! I tried 20220503 - as it was the earliest! It then failed to boot to recovery, so I restored the latest - but also had to flash boot.img.
Why do you recommend 0607? Hmm, are the earlier ones for LOS18 perhaps??
I will try in the morning!
Thanks!
Click to expand...
Click to collapse
I recommend 0607 only because the build date is closer to the LOS+microG version you are trying to flash.

anarchotaoist said:
Thanks for your reply! Yes, I suspected that! I tried 20220503 - as it was the earliest! It then failed to boot to recovery, so I restored the latest - but also had to flash boot.img.
Why do you recommend 0607? Hmm, are the earlier ones for LOS18 perhaps??
I will try in the morning!
Thanks!
Click to expand...
Click to collapse
I also double checked and the two builds I mentioned are indeed the earliest versions of LOS 19.1 for the OnePlus 9 Pro.

razercortex said:
I recommend 0607 only because the build date is closer to the LOS+microG version you are trying to flash.
Click to expand...
Click to collapse
Yes! I stupidly thought the LOS4microg build would have been based off the earliest LOS build - and it is, but that repo holds the 18 version also!
I see what you mean that it is the closest build now after checking https://download.lineageos.org/lemonadep

SOLUTION: The 0607 files did indeed fix the issue. LOS4microg now installed.

Having the same issue here, and the link :https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ is no longer available, tried looking for it in the WayBackMachine but they only stored the page not the file itself, guess because of its size, can't find it anywhere else, can anyone who downloaded it re-upload it again to solve the same issue @anarchotaoist ?
Waited for the MicroG team to update their builds, but they still did not.

Droid_Player said:
Having the same issue here, and the link :https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ is no longer available, tried looking for it in the WayBackMachine but they only stored the page not the file itself, guess because of its size, can't find it anywhere else, can anyone who downloaded it re-upload it again to solve the same issue @anarchotaoist ?
Waited for the MicroG team to update their builds, but they still did not.
Click to expand...
Click to collapse
You should use dtbo, vendor_boot and boot images latest from may
or you can dump the rom's payload.bin and use those already included in the rom
you can try crDrod or stagOs (they both suport sign-spoofing) with spare microG

razercortex said:
There's your issue, you are using a different vendor_boot and dtbo version. Notice how you downloaded the 20220628 files instead of the 20220611 ones, and also your recovery version is not matching either. Unfortunately, it seems you can't find files that exactly match your build, but I will do my best to point you in the right direction.
Try using https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220607/ first. If that doesn't work, try https://mirror.math.princeton.edu/pub/lineageos/full/lemonadep/20220614/. Those builds are closer in date that the latest one, so this might remedy your issue.
Click to expand...
Click to collapse
Same problem, this solution worked
I went onto lineage downloads and grabbed the oldest files (about a month old) and since I had the newest microg image it accepted it.
I did older dtbo, vendor_boot, and recovery. idk if that is excactly what was required but since it covered everything in the lineage instructions I went that route and it worked. I later realized that microg has a specific recovery, but never used it because the aforementioned flow worked.

Psk.It said:
or you can dump the rom's payload.bin and use those already included in the rom
Click to expand...
Click to collapse
Circling back here again, because believe it or not, I ran it to this on an additional phone. My previous post is the easy way, find the right dates, if possible. If the microg files are older then the other method is to dump the payload, as quoted. For anyone like me, not knowing how to do that,
GitHub - vm03/payload_dumper: Android OTA payload dumper
Android OTA payload dumper. Contribute to vm03/payload_dumper development by creating an account on GitHub.
github.com
You're going to need to have python install, you need an update as per the instructions there, and there is one more problem, the requirements.txt needs to be modified because it will throw an error, follow the error message and you will get there, eventually. I did, but it was a headache. I hope this helps anyone who has run into this problem but is not familiar with payload dumper.

I just want to thank you @Psk.It for suggesting crDroid. It has been running on the One Plus 9 Pro pretty smoothly, and after 6 months it is just as snappy as it was in the beginning. Great helpful community in the Telegram group as well. Your reply was the reason I considered an alternative to LineageOS, as it was giving me many problems because of no support of spoofing, so again your comment is much appreciated along with all the all the community.