Develop Bugs

[RECOVERY][GEEHRC] TWRP-3.0.3-3

{
"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"
}
TeamWin's TWRP Touch Recovery for LG Optimus G (geehrc).
https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/​
Screenshots:
​
Flashing Instructions:
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise use adb.
Remember to do backup of your current recovery before installing.​
Changes:
compiled on omnirom-7.1 source
latest twrp updates included
updated device trees
prebuilt kernel
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
permissive selinux
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
enabled usb-otg support
enabled modem backup
Download Links:
TWRP-3.0.0-0: geehrc
​
Device Source:
https://github.com/Split-Screen/android_device_lge_geehrc
https://github.com/TeamHorizon/android_kernel_lge_gee
XDA:DevDB Information
Unofficial TWRP-3.0.3-3 for LG Optimus G variants by dadi11, Tool/Utility for the LG Optimus G
Contributors
dadi11
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2016-02-06
Last Updated 2017-01-27

Reserved
Changelog:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
Click to expand...
Click to collapse

E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')

Great work! Im new to this how do i install it?

enapah said:
E975 flashed this image with TWRP 2.8.7.0 and has official CM12.1 ROM, log file starts with:
E: invalid block device on '(...)':
system
cache
data
persist
firmware
boot
recovery
misc
radio
sbl[1-3]
tz
rpm
aboot
E:Unable to locate storage partition
Unable to find partition for '/system' (and '/cache')
Click to expand...
Click to collapse
I have the same errors

can someone create a flashable zip?

@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".

Guys sorry for errors. I have no OG anymore but still wanted to release something for you guys! I will try to fix it and release update in some minutes
please download and try this one: https://mirrors.c0urier.net/android/Dadi11/TWRP/TWRP-3.0.0-0_GEEHRC.img

enapah said:
@iakoboss7 Given the errors I have experienced in my E975, if you rely on the flashable zip alone then you really shouldn't try this version... you'll have to learn the hard way how to flash the img file via fastboot (or something else) to recover your recovery.
It's not rocket science and doesn't take that much, but it's far better if you go in prepared rather than deal with it "in despair".
Click to expand...
Click to collapse
He can easily flash TWRP or CWM by using FreeGee App.
I have done this 10minutes ago.
---------- Post added at 08:31 PM ---------- Previous post was at 08:16 PM ----------
Now recovery is working very well!
AROMA Installers are working too

pawelelos said:
Now recovery is working very well!
AROMA Installers are working too
Click to expand...
Click to collapse
Thanks for confirmation

good job

Thanks dadi11. Very generous, especially considering LGOG is not your primary device anymore.

@dadi11 Thank you very much for your time, specially given this is no longer a device at your hand.
I do have one "small" request to make, for those of us who run the official CM builds, it would mean the world to us if we had an image with e975 as device name (instead of geehrc). Any chance you could make one extra build?
Code:
ro.build.product=e975
ro.product.model=LG-E975
ro.product.device=e975

Stable, not bugs:
http://xyyx.ga/nitrogen-os/geehrc/twrp-geehrc-3.0.0.zip

File manager doesn't work properly, cannot list contents in some folders (ex: system)

hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it

gledis96 said:
hey guys can anyone help me how to flash twrp cause i did it some time ago with the 2.8.7.0 version and wanted to do the 3.0.0 but i totally forgot how to do it
Click to expand...
Click to collapse
Install as any other zip, then chose reboot recovery from ur recovery which u use.

tiennhu89 said:
Install as any other zip, then chose reboot recovery from ur recovery which u use.
Click to expand...
Click to collapse
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now

gledis96 said:
i tried that but it didnt work tried with the way like i did with the 2.8.7.0 but that didnt work either
(edit)
anyway i should shut my mouth i didnt do it properly before thanks man it perfectly works now
Click to expand...
Click to collapse
Ok.u r wellcome.☺

tiennhu89 said:
Ok.u r wellcome.
Click to expand...
Click to collapse
another thing do you know how to install xposed cause i tried flashing it but my phone gets stuck in boot i have this rom
http://forum.xda-developers.com/optimus-g-intl/orig-development/rom-aosp-5-1-1r8-optimus-g-t3160195

[RECOVERY] TWRP 3.3.1-0 (lilac) [UPDATE: 2019-09-16]

TWRP
This project provides the TWRP recovery for for the Sony Xperia XZ1 Compact (lilac).
{
"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"
}
FEATURES
File-Based Encryption (FBE) support
EXT4 support
F2FS support
EXFAT support
Provides unzip
Additional languages
This recovery will use the security patch level from the system partition to decrypt data. It should not be tied to a security patch level anymore.
DOWNLOAD
Make sure you download the .img and corresponding .asc.txt file (see INTEGRITY)!
You can always find the latest version of the recovery HERE.
INTEGRETY
The recovery images also come with an GPG armor file (.asc). With that file you verify that the image I created hasn't been altered.
How do you do that?
Download my gpg keyring here: https://cryptomilk.org/gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg.
Download the recovery.img and recovery.img.asc.txt file
Rename the recovery.img.asc.txt file to recovery.img.asc
Verfiy the signature using the following command:
Code:
gpg --keyring ./gpgkey-8DFF53E18F2ABC8D8F3C92237EE0FC4DCC014E3D.gpg --verify recovery.img.asc
A good tutorial is: How to verify signatures for packages from the Tor Project.
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!​
XDA:DevDB Information
recovery_twrp_sony_lilac, Tool/Utility for the Sony Xperia XZ1 Compact
Contributors
modpunk, Dees_Troy
Source Code: https://github.com/cryptomilk/android_device_sony_lilac
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-09-16
Created 2017-11-18
Last Updated 2019-09-16

Nice work!

What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?

Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51

4rz0 said:
What does the STOCK addition in the title mean?
Can't I flash for example LOS with it?
Click to expand...
Click to collapse
RTFM!

aikon96 said:
Nice work! So does that mean that we finally can root our xz1 compact?
And currently this TWRP is not working for security patch November, right? I mean build nr: 47.1.A.5.51
Click to expand...
Click to collapse
No, I need to create one for November. Will do that soon.

modpunk said:
RTFM!
Click to expand...
Click to collapse
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?

4rz0 said:
I did read the OT, if that's what you mean, but it doesn't answer my question.
If the LOS I want to flash comes with the same security patch level, would it work?
Click to expand...
Click to collapse
There is no limitation in flashing. However there is no LOS you can flash yet ...

works perferct! thank you :good:

I got an XZ1. Any chance to get TWRP for it (for testing)?

Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img

TWRP
modpunk said:
Could someone please test
Click to expand...
Click to collapse
ok. I'll test it

modpunk said:
Could someone please test https://xor.cryptomilk.org/android/twrp-lilac/twrp-3.1.1-0-lilac-patchlevel-2017-11-05.img
Click to expand...
Click to collapse
I will indeed test too juhuuu...

it flashes okay via fastboot, and twrp is also working. except for format option under wipe, when typing 'continue' it seems like it doesn't show the inputs, only the last letter 'e'
anyway after i flashed the twrp, i booted it up, and mounted everything except for otg. and then of course i flashed magisk.zip (latest v14) and it also succeeded
but then when i reboot from twrp, it stucks at sony logo, meaning default bootanimation doesn't kick in, and i patiently waited for like 10-15 min
so i assume it's not working. i even tried with a userdebug and regular user build 47.1.A.5.51
now i will try just to boot the twrp without flashing it and then flash magisk.zip while it's booted up via fastboot to see if it boots up normally

a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.

modpunk said:
a) Do you have your partition encrypted and could you mount it, so it asked for a password?
b) TWRP writes a log file you can download adb pull /tmp/recovery.log
c) adb logcat is also working
Note that there is currently no upstream TWRP developement for Oreo ongoing. I just wrote several hacks to get it working.
Click to expand...
Click to collapse
A: it does not ask for password upon bootup so i guess it's not encrypted in that way
B attached here
C is there any specific logcat you want, like error or fatal level etc.

Question just to be clear: do we have to update twrp for evry new securitypatch?

To decrypt the /data partion on a stock ROM, yes you do.

Hi modpunk,
Ur a true star...****
I just want to ask a couple of question's.
Does the bootloader have to be unlocked in order to flash this....?
I have had a Z3 Compact and got it rooted with bootloader locked and also a Z5 Compact using munjen setup.
Install TWRP on it Flashed SuperSU using TWRP was best thing i did.
Do you have a step by step guide how to flash this. I would love to test it for you.
When you flash is it using munjen flashtool...?
Thanks Sham

UPDATE
TRWP is working actually, just figured out that it's magisk that get the phone not to boot, bith 14 and 14.5
and latest supersu both the xperia one and the regular one v.2.82 fails, give error "unzip fail, no proper recovery etc."
Now for fun i will load it up with userdebug firmware and see if i can make it manually root with the "angela" method

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 10 (Snapdragon)

{
"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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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 Models:
Galaxy Note 10 N9700, N970U, N970U1 and N970W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download Note 10: d1q.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Telegram account
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
10.03.2021 - Update to latest TWRP source
- Add terminal multidisabler script
- fstab cleanup.
16.02.2021 - Initial R build for Android 11
01.01.2021 - Initial Release

How are we unlocking the Bootloader? Message me when you have time.

I have Windows 10 and drivers are installed. I got nothing going on today so anytime will work. If today works for you

menace211 said:
How are we unlocking the Bootloader? Message me when you have time.
Click to expand...
Click to collapse
[Android][UNSAMLOCK] Bootloader Unlock for Samsung US/Canada Devices
This thread is @svetius approved Important notice: Do not update to April 2023 security update (XXXXXXXXXXWCX) or later. Examples: G998USQS6EWCA, N986USQU4HWD1. Samsung has patched the bootloader unlock again on those updates. NOTE: The OneUI...
forum.xda-developers.com
USA/Canada - Samsung Bootloader Unlock
You can view and join @Afaneh92UnlockChannel right away.
t.me
I will PM you too.
Gregbmil1 said:
I have Windows 10 and drivers are installed. I got nothing going on today so anytime will work. If today works for you
Click to expand...
Click to collapse
Ok thats fine.

Just wanted to let people know, if you're on the fence about this, its 100% legit. Thanks again!

Question. How do we flash multidisabler in TWRP if its encrypted in TWRP? I can't find anything in it

Gregbmil1 said:
Question. How do we flash multidisabler in TWRP if its encrypted in TWRP? I can't find anything in it
Click to expand...
Click to collapse
Push the file through adb or use Micro SD or USB-OTG.

afaneh92 said:
Push the file through adb or use Micro SD or USB-OTG.
Click to expand...
Click to collapse
OTG worked great!! Thank You.

Anyone having an issue creating a backup in TWRP? I tried saving it with OTG and internal memory. It always gets to about 21% then it reboots back into TWRP with no backup created

Gregbmil1 said:
Anyone having an issue creating a backup in TWRP? I tried saving it with OTG and internal memory. It always gets to about 21% then it reboots back into TWRP with no backup created
Click to expand...
Click to collapse
Android 11?

Yes, Android 11

Gregbmil1 said:
Yes, Android 11
Click to expand...
Click to collapse
TWRP kernel based on Android 10, wait for 11 kernel source to be released.

Changelog:
16.02.2021 - Initial R build for Android 11

So there will not be a way to unlock the phone without paid service? Seems shifty. There are developers here in the XDA community ths

[ROM][12L][OFFICIAL] crDroid 8.x FOR MOTO ONE (DEEN)

{
"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:
crdroid_features/README.mkdn at 12.1 · crdroidandroid/crdroid_features
our main features (why you love us). Contribute to crdroidandroid/crdroid_features development by creating an account on GitHub.
github.com
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
First time installation:
flash crDroid recovery like every other recovery on this phone
Format data
Flash the ROM zip either from adb sideload or internal storage
Reboot in to recovery
Format data
Flash GApps (If wanted)
Reboot and enjoy!
Update installation:
Reboot to recovery
Flash the ROM in twrp or use adb sideload
Reboot and enjoy!
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_motorola_deen
Download:
ROM https://crdroid.net/deen
Changelog: https://crdroid.net/deen/8#changelog
Known issues:
- Dolby broken
- Adb sideload
- Ota Update
- You tell me
Visit official website @ crDroid.net
crDroid Deen Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

20220810
- ADB: Wireless debugging: turns off frequently
- ADB: Wireless debugging: No debuggable process in Android Studio (but other devices works OK); App Inspection & Profiler not working
- ADB: Enable USB debugging -> device restarts (kernel panic?)
In the Logcat I got something like this:
Code:
I/adbd (533): opening control endpoint /dev/usb-ffs/adb/ep0
E/adbd (533): failed to write USB strings: No such device
20220807
- UPDATE: OTA: not working 20220807->20220810: Could not change profiles (https://paste.crdroid.net/J4u9b6). Is it a problem with permissions or problems caused by Magisk's changes into the system?
- UPDATE: sideload update 20220807->20220810 infinity boot loop with Magisk (without Magisk no problem)
- GAPPS: Device is not certified by Google (to solve this problem just follow: https://www.google.com/android/uncertified/)
But this ROM is still awesome! Thank you so much.

I'm trying to fix the root and debug issues

This looks awesome. I'm waiting for the new display to arrive and I'm rocking this phone back. Would this rom enable VoWifi? Or does it need certain hardware for vowifi?

Will come a Version in near future, that has no issues with OTA functionality?
Last 2 updates did not work with OTA. In Telegram Group Deen Brasil was mentioned, that a server is needed to make twpr download possible, before update is installed, cause there is no recovery patition.
Is there not way to add a recovery pation?

Hi their I was wondering when flashing this rom are these steps required? Like the pixel ROM for the Deen:
1. Download Rom
2. Download TWRP
3. fastboot getvar all
4. fastboot boot twrp
5. Do full wipe
6. Format Data
7. Flash ROM
8. Reboot to Bootloader
9. fastboot getvar all
10. If fastboot getvar all (current-slot label) from step 3 equals this from step 9 change the slot to opposite, if a then b if b then a, command is fastboot --set-active=SLOT
11. Boot to TWRP again
13. Flash Magisk (optional)
14. Reboot to system

I tried booting into recovery but i got this error
Edit : That was a long time ago.
tldr - im stupid and didnt unlock the bootloader properly.

Tobyash said:
I tried booting into recovery but i got this error View attachment 5744289
Click to expand...
Click to collapse
Looks like your bootloader is locked.

baseline2016 said:
Looks like your bootloader is locked.
Click to expand...
Click to collapse
Well thats what it seems at first look, but i have the bootloader unlocked. And i checked a few times to be sure.

Tobyash said:
Well thats what it seems at first look, but i have the bootloader unlocked. And i checked a few times to be sure.
Click to expand...
Click to collapse
Maybe you have to run the command in Windows as an administrator. And the command is fastboot boot recovery c:/....img
I followed the steps I mentioned in my post #6 and the ROM works excellent.

How do you update with twrp? It gives me error no matter what slot I choose. CrDroid recovery or OTA doesn't work.

there is a problem, the microphone is recording very low audios, with this crdroid rom.

Hello,
Gapps link is broken. I tried NikGapps but it stuck my boot...
Could you please fix the link?
Thanks in advance!
EDIT:
Found it here, just in case anyone is wondering:
Release Squeak Releases · ChonDoit/TheGappsInstaller
20220607 | Merged June changes | Unified some Overlays | Updated apns list
github.com

I just installed the latest update 2022-12-19 but unfortunately I hear an echo when I'm in a phone call.
Also echo when calling with Signal or Telegram.
Am I the only one?

whats-in-a-name said:
I just installed the latest update 2022-12-19 but unfortunately I hear an echo when I'm in a phone call.
Also echo when calling with Signal or Telegram.
Am I the only one?
Click to expand...
Click to collapse
Solved by installing stock and from there installing lineage-18.1-20220523-UNOFFICIAL-deen.zip

Hi. I'm trying to build a user version of your rom. The build works but I get an error during update (sideload). This happens at the end, after the vendor is flashed and during `Running backuptool scripts`
Code:
Update_engine_sideload [ERROR: postinstall_runner_action.cc] Failed to set backuptool context
I wonder why this could be ? Perhaps I have not reconstructed your manifest correctly?
note: I'm flashing from Recovery using a USB UTG stick and also flashing from TWRP using the same stick..

I have been using the Motorola One with this rom as my main phone for the past day or two, so far ive been enjoying it! Im hoping for more updates in the future.

Good afternoon,
I wanted to share with you my experience trying to install rom 20230414 for the Moto one tx 1941-3.
Although I was able to install and use the previous version without problems, it was impossible for me with this latest version since it stuck to the android logo. It doesn't flash or reset, it just stays there.
I find this system incredible so I would love to use the update
Thank you

[ROM] [UNOFFICIAL] Lineage 20 - scorpio (Mi Note 2)

By entering this zone you agree to the followings:
- Your 'expired' warranty is now void
- I'm not responsible for your girlfriend/boyfriend getting mad at you because the call didn't came through
- Also not responsible for missed alarms due to alarm not firing
- Or loosing your job due to late notifications
You're a great guy. Happy discovering and have a nice day!
Click to expand...
Click to collapse
LineageOS 20 for Mi Note 2
Beware, you are about to enter a dangerous zone!
{
"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"
}
After much tinkering and countless of brain explosions, I have determined that my lineage-20 builds for Mi Note 2 is suitable to be released for the public.
Please note that the ROM bears the "[UNOFFICIAL]" tag for a reason - you might face instability or performance issues.
You are not recommended to use this ROM for daily usage, just to be safe. I am not an experienced developer, hence my changes could be wrong or incomplete,
rendering issues to occur on the device.
Full credits to bgcncm, luk1337, haggertk, joe2k01, and all other xiaomi/msm8996 developers.
This ROM is based on official xiaomi/msm8996 sources by LineageOS, with my changes on top to get lineage-20 working.
Without their work on xiaomi/msm8996's Linux 4.4 kernel, this wouldn't be possible at all. Please consider donating to them or the LineageOS foundation.
Additional, huge credits to ChronoMonochrome and @rINanDO for their huge assistance in my early days of Android development.
Please refer to my github repositories for more information on my commits and changes made on top of official LineageOS repositories.
Things to take note:
- Not all features are fully tested as I do not have the required equipment etc, such as testing Bluetooth audio, Dual SIM network, or Netflix.
- Builds will be SELinux permissive for the time being.
- Builds are using EAS (Energy Aware Scheduling) configuration, rather than the traditional HMP configuration. No PowerHAL is included for the time being.
What's not working:
- SELinux (permissive)
- PowerHAL (excluded for EAS switch)
- Camera HAL log spam
- other untested features (ie. DRM, Bluetooth audio)
- some other non-fatal, kernel side errors and outdated configurations
- you tell me.
What's working:
- everything else.
Installation steps:
1. Update system to latest stock.
2. Unlock bootloader and perform factory reset.
3. Utilize fastboot to flash and boot recovery.img from my Download link below.
fastboot flash recovery recovery.img
fastboot boot recovery.img
You can also boot official TWRP first to make persist and EFS backups. (Highly recommended. )
4. Wipe everything, and sideload ROM zip using adb.
adb sideload lineage-20.0-20230420-UNOFFICIAL-scorpio.zip
5. Flash GAPPS if wanted. Reboot and have a sip of coffee.
Downloads:
https://drive.google.com/drive/u/0/folders/1I3r_LPRZ-2OSAVH6rMrvCDmMCJMj97RP
ROM Information
Variant: LineageOS 20 (Android 13) - UNOFFICIAL
Target: scorpio (Xiaomi Mi Note 2)
Maintainer: lee.wp14 (github.com/leewp14)
Source: https://github.com/hikuii

Latest Release: 20230424
Release Status: Not stable, not unstable, just right.
Release Notes:
- initial release
FAQs:
Spoiler: FAQs
1. What is "Not stable, not unstable, just right"?
A. Because I dare not declaring my builds stable when it is clearly based on expert works (looking timidly at LineageOS maintainers..) and they haven't release lineage-20 for gemini and natrium.
Afterall, there's still huge pile of stuffs to work on before I can slap the word 'stable' to my builds, which I can be most certain it won't happen.
2. Safetynet? Root?
A. Passing SafetyNet requires one additional measure for Android 9 and above: chmod 0640 /sys/fs/selinux/enforcing. I still haven't implement the changes in device tree. Otherwise, without Magisk installed, everything is well-handled and apps should work.
3. Some apps still detect root. Why?
A. This is because some apps are detecting system props, particularly looking for userdebug/test-keys and ro.debuggable=1 props. You could modify build.prop to workaround this, but bear in mind that in Android 13, there are multiple build.prop scattered across /system, /odm, /vendor, /system_dlkm, /system_ext...
4. ETA?
5. Ok... but when you going to update?
A. No definitive answer. I'm doing this in my free time and on a voluntarily basis. New builds will only be released after it passes my quality inspection, and that it actually includes major changes. Maybe there won't be any update at all if all is well.
Screenshots:
Spoiler: Screenshots
This is pure LineageOS, Google for pictures.

Me during development:
Give me praises if you want to keep me happy uwu <3
Cutie Pictures:
Spoiler: DO NOT OPEN

Great rom for a great smartphone!
Many thanks for your job!

Thanks.
-Just reporting. \/
edit 1: How to get rid of decrypt data? im trying to make some backups using twrp.
edit 2: besides the sad decrypt data issue, the instalation process seems to restore the default partition table. It deleted my custom 4gb+ system partition and restored to stock 2,975mb (only a problem to postmarketos/plasma users).

betume said:
edit 1: How to get rid of decrypt data? im trying to make some backups using twrp.
Click to expand...
Click to collapse
oh. Don't think that's possible. A new recompilation of TWRP is required, or if someone did it.
Now new android requires FBE encryption, not even FDE, so old TWRP will not able to decrypt it.
If backup is really important, suggest you to use dd first, or adb pull your files. I don't know how to compile TWRP, so can't build one for now.
betume said:
edit 2: besides the sad decrypt data issue, the instalation process seems to restore the default partition table. It deleted my custom 4gb+ system partition and restored to stock 2,975mb (only a problem to postmarketos/plasma users).
Click to expand...
Click to collapse
I have checked on the installaton steps of postmarket os for scorpio, and I'm stunned. If an image file could "repartition", then no doubt flashing LineageOS will also able to "repartition" it back since android zip builds use image patching too. We actually have to specify the size of partitions in device tree configurations.
I never came across this method of "repartitioning" and couldn't find further information on Google. Do share with me if you know any references about this.