Database Info

[TWRP 3.2.1-1] [ROOT] A8+ sm-a730f - 21/01/2018

Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
{
"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"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* 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
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: beta
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU

NOTE:
This may be a dead duck in the water before it even installs due to the fact Samsung currently seem to be locking bootloaders on all recent devices even devices with previously unlocked bootloaders.
BEFORE attempting to install this software please ensure you have the stock firmware available (this can be found on updato.com) and that you are able to flash it with Odin.
.

1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.

If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)

tibey said:
If you do one for the the a530f i would be glad to test it ! (if there's no risk of complete brick of course)
Click to expand...
Click to collapse
No risk as long as you've got the firmware handy.

ashyx said:
1.1k views, 120 downloads and not one report or tap of a thanks.
XDA truly is about community spirit.
Cheers guys.
Click to expand...
Click to collapse
It's amazing.
I would very much like to know if this is locked from factory, but no one reports if it can be flashed or not :/

Guide on TWRP recovery for A8
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* 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
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Hello @ashyx, I have made a guide based on your thread: http://techbeasts.com/install-twrp-recovery-root-galaxy-a8-plus-2018/
Just wanted to notify.

Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.

tibey said:
Sucks that no one is reporting anything, but tbh in europe it seems that only the A8 (A530f) has been released so far.
Do you think it would be easy to port for that model ? I think there's a couple of us waiting for this port, would be much appreciated and would test it asap.
Click to expand...
Click to collapse
It will be ready at some point today.

@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.

ashyx said:
@tibey
Here you go, good luck: https://androidfilehost.com/?fid=746010030569951180
.
Click to expand...
Click to collapse
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)

tibey said:
Seems to work great on a530f ! Just followed the instructions (had just a minor issur with MTP not working in TWRP)
Thanks a lot :good:
Edit : Guess you should post it there : https://forum.xda-developers.com/ga...18-roms-kernels-recoveries--other-development (damn that forum is invisible in search)
Click to expand...
Click to collapse
Yep it seems Samsung are forcing the use of their own MTP driver in the kernel as I couldn't disable it.

And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.

ashyx said:
And it continues, now 2.2k views and 199 downloads and still not one downloader could be bothered to post.
Click to expand...
Click to collapse
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.

travis82 said:
Well samsung mtp isn't in a8+ defconfig i just looked. So post your device tree and the partition layout and fstab from stock kernel and I will see if I can help.
Click to expand...
Click to collapse
I know it isn't which is why it isn't included.
Seems like they are forcing their own driver.
There is probably a way to fix it by modifying the make files, but I won't spend any more time on it until people can be bothered to take the time to respond.

Not working
ashyx said:
Unofficial release -TWRP recovery for the Galaxy A8+ - SM-A730F, EXYNOS 7885
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
* 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
Update 21/1/2017
TWRP 3.2.1-1 NN build released.
Current status: Testing stage
NOTE: THIS IS AS YET UNTESTED. IF YOU DECIDE TO TRY THIS OUT PLEASE REPORT ANY ISSUES WITH DETAILS. POSTS LIKE 'NOT WORKING' WILL BE IGNORED
Features:
MTP >> to be confirmed
ADB working >> to be confirmed
SEANDROID warning fix
TWRP and Kernel built from latest source
Raw SYSTEM image backup
NTFS support
F2FS support >> To be added
Twrp app support
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SamMobile or updato.com in case of problems. This will trip the knox counter.
Instructions:
Flash with odin in the AP slot.
Put your device in DOWNLOAD MODE. (POWER +VOL DOWN +VOL UP)
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN
As soon as the screen goes blank change to POWER + VOL UP
You should now see TWRP recovery.
FAILURE TO FOLLOW THE ABOVE STEPS WILL RESULT IN TWRP BEING REPLACED BY STOCK RECOVERY
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
twrp_3.2.1-1_sm-a730f_210117
To Root:
Flash the latest SuperSU or Magisk release with TWRP:
SUPERSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
MAGISK - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption and mount internal storage (/DATA):
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
DONATE ME HERE IF YOU WANT TO BUY ME A BEER/COFFEE OR HIT THE THANKS BUTTON IF I HELPED YOU
Click to expand...
Click to collapse
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops

akshaygpt2 said:
Not Working Properly its give bootloop
i try according to this method but not working it restart after the first logo of the phone.
odin show passed message but phone get bootloops
Click to expand...
Click to collapse
.
What are your phone specs and build number?

ashyx said:
.
What are your phone specs and build number?
Click to expand...
Click to collapse
Android 7.1.1
Galaxy A8 plus
Sent from my SM-A730F using Tapatalk

akshaygpt2 said:
Android 7.1.1
Galaxy A8 plus
Click to expand...
Click to collapse
I need your firmware build.

ashyx said:
I need your firmware build.
Click to expand...
Click to collapse
Build Firmware -
NMF26X.A730FXXU1ARAC
Sent from my SM-A730F using Tapatalk

[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO]

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
INFORMATION:​
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing or rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Read more about TWRP here: https://twrp.me/about/​
NOTE : ​
This build of TWRP is based on the kernel source code and no prebuilt kernel was used for building. Because, it is the first build, testers are very welcome for providing feedback regarding the build. ​
CHANGELOG (3.2.3.0) :​
WHAT'S NEW?
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files​
CHANGELOG (3.3.0.0) :​
WHAT'S NEW?
* Merge AOSP 9.0 r3 (Dees_Troy)
* Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
* Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
* vold decrypt updates (CaptainThrowback and nijel8)
* Support vibration on LED class devices (notsyncing)
* Metadata decrypt support for Pixel 3 (Dees_Troy)
* Support rotating the display via build flag (vladimiroltean)
* Reboot to EDL mode button (mauronofrio)
* Support MTP on FFS devices (bigbiff)
* Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
* Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
* Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
* TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
* Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
* Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)​
* Also, there was a major bug with the previous build which prevented the flashing of any file because of the "digest-verification" has been fixed with this release. Enjoy!
CHANGELOG (3.3.1-0) :
WHAT'S NEW?
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff​
DOWNLOAD :​
You can download the latest build of the TWRP from the official site here:​
TWRP(Official)​
BUGS:​
Encryption (for MIUI)
INSTRUCTIONS :​
Download the recovery image and place it in some folder on your desktop and open the Terminal/Command Prompt/Powershell in the said folder.
Connect your device to the PC and boot into the fastboot mode using H/W keys or by typing :
Code:
adb reboot bootloader
Now, type :
Code:
fastboot flash recovery twrp-3.3.0-0-violet.img
OR,
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
Download the recovery image from the link.
Reboot to TWRP.
Hit Install and tap the "Images..." button in the lower right
Browse to the location of the TWRP image on your device and select it.
Select recovery from the partition list and swipe to flash.
For users who are running MIUI : ​
Thanks to Snehashis Sarkar for a short tutorial.
Your data will get wiped before flashing the recovery so take a backup of the internal storage.
Reboot to fastboot.
Wipe the Userdata via fastboot.
Flash this recovery.
Boot into the recovery and format the data (just format it, don't go for the "advanced wipe" section .
Flash this image file: Patched fstab + vbmeta + thermal configs for better performance
Reboot and enjoy.
CREDITS: ​
TwrpBuilder for trees​
Kernel Source : ​
Link: android_kernel_xiaomi_sm6150
XDA:DevDB Information
[RECOVERY][OFFICIAL][TWRP - 3.3.1-0][Xiaomi Redmi Note 7 PRO], Tool/Utility for the Xiaomi Redmi Note 7 Pro
Contributors
Doomsday101
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-11
Current Beta Version: 3.3.0-0
Beta Release Date: 2019-04-03
Created 2019-04-02
Last Updated 2019-05-23

Reserved

Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.

Thank you for your build !
Do you know if someone started to work on porting ROMs ?

diamantik said:
Thank you for your build !
Do you know if someone started to work on porting ROM's ?
Click to expand...
Click to collapse
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.

Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Can you send me the logcat of the kmsg file present in the /proc directory using adb shell when the twrp is stuck on bootlogo?

Doomsday101 said:
I don't know if someone is working on ROMs but it is likely because of the unreliable kernel source ATM by Xiaomeme.
Click to expand...
Click to collapse
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive

diamantik said:
Ok thank you
I had order my device , when i will receive it , i will try to help the community with what i can , i will be glad to test things , and develop them , hopefully we can get more devs , and together we can maintain the development for RN7 Pro alive
Click to expand...
Click to collapse
Sure thing ?

It will boot, try fastboot erase userdata, but you can't flash any ROM (MIUI) atm, as it has encryption bug, which needs to be fixed by the OP!
Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse

Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw

moriyaprateek said:
Has anyone else tested this and does it seem to be working fine? I'm quite scared in flashing recoveries :/
---------- Post added at 09:28 PM ---------- Previous post was at 08:34 PM ----------
twrp's stuck on the twrp logo btw
Click to expand...
Click to collapse
The recovery has the encryption bug atm as stated by @talk2indrajit in the last post. So, you will have to erase userdata via fastboot first. I suggest you take a backup, get rid of Miui and continue with the said process and flash the newly built LOS16 by @Dyneteve (if you seek to flash a custom ROM).

Can anyone update the twrp to 3.0.3?

Not able to flash vbmeta.img fastboot mode..
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..

Aj51 said:
Is any other way to flash vbmeta without fastboot mode because my platform tools fastboot not work gives error unknown fastboot command.. Please replay..
Click to expand...
Click to collapse
Download latest adb from here
https://developer.android.com/studio/releases/platform-tools

When can it decrypt /data?

Vatumb said:
Not able to Boot.
1. Fastboot boot twrp_violet.img not working.. Phone reboots normally.
2. So booted TWRP manually (Volume Up + Power) And Phone stuck on TWRP Logo Screen.
See the attachments for more info.
Click to expand...
Click to collapse
Same problem happen with me

kishangupta009 said:
Same problem happen with me
Click to expand...
Click to collapse
Don't use this command, it was mentioned somewhere, it doesn't work for now, you need to flash it , fastboot flash recovery recname.img.

Guys this TWRP is not working , gets stuck at TWRP logo !
Try the another : https://forum.xda-developers.com/re...ficial-3-2-3-redmi-note-6-pro-violet-t3912400

ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.

kuhru said:
ok, so here's an anecdote.
when i flashed it for the first time using fastboot command, i got it stuck on the logo as well. then i looked it up, and i found this vbmeta thing, which i don't really know what is. got it to flash using platform tools (vbmeta), then flashed the other twrp on this site, and booted into it. (went with the other twrp because that is what the youtube video was using as well, and i just wanted to get over the loop, didn't think to test out)
so, successfully booted into twrp(OTHER)
from there i had to flash the lineage vendor patch cuz can't load any roms (that i tried) without it. tried flashing rom and gapps, worked. this works, no problem. (maybe some of you might want to check if the vbmeta thing was required, or if you can straight flash the older twrp from commands.)
then i went back, wiped out stuff (cache,dalvik, system and data, NOT vendor) and i flashed twrp(THIS) using twrp(OTHER), just to see
got twrp(THIS) to boot successfully.
problem here now is that it spits an error on fkin digest verification for any rom. if i can't even flash a rom, i can't get beyond that. error being "digest verification failed" or something like that.
im tired of this twrp, someone should maybe test things out further, idk where to go from here. this just flat out doesn't work.
Click to expand...
Click to collapse
Thank you for trying it out previously. I have released a new build today with the latest TWRP version (3.3.0.0) and now the "digest-verification" bug has been fixed.

[ROM][UNOFFICIAL][10] LineageOS 17.1 for Galaxy J4+ [j4primelte]

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Common Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][10] LineageOS 17.1 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: OneUI, U2
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.1
Beta Release Date: 2020-02-25
Created 2020-02-25
Last Updated 2020-03-10

Changelogs :
Public Beta 3 - 18/03/2020 :
Fixed a issue which some users have broken ril.
Fixed a issue which some users have broken nfc.
Public Beta 2 - 10/03/2020 :
Merge Security Patch: 5 March 2020
Fix audio on second sim: @Geckyn
Fix HDR on Camera.
Fix FM Radio.
Fix torch releated issues.
Fix Mac Adress releated issues.
LineageOS Source Upstream.
Public Beta 1 - 26/02/2020 :
First public release.

Special Thanks :
@BarryBlackCat for non-stop, day and night testing builds.
@Geckyn for pointing out some stuff. Thanks man.

I will NOT accept your bug report if you are using a custom kernel.
I will NOT accept your bug report if you are using a modification (Like some magisk modules etc.).
I will NOT check your bug report if you didn't provide any logs (Some bugs may will be checked).

Camera doesn't take HDR photo (or hang when switching between HDR and non HDR mode), it also happened on other custom ROM as well.
No magisk module or custom kernel installed.
Here is the logcat with "camera" keyword as filter: https://pastebin.com/RrDvAtjw

Andhika24kd said:
Camera doesn't take HDR photo (or hang when switching between HDR and non HDR mode), it also happened on other custom ROM as well.
No magisk module or custom kernel installed.
Here is the logcat with "camera" keyword as filter: https://pastebin.com/RrDvAtjw
Click to expand...
Click to collapse
Thanks.

KotaMangga said:
Ashyx kernel sir?
Click to expand...
Click to collapse
Let me make the steps clear for you:
1) You must be on Android Pie (custom or stock ROM doesn't matter). If you're on Samsung Oreo (U2), upgrade to Samsung Pie first so the device bootloader will be upgraded to U4 or newer.
2) If you're on Samsung Pie, flash TWRP and do all the required steps (this includes flashing RMM bypass, flashing encryption disabler, and formatting your data). If you're already using custom ROM, just skip this step.
3) Go to TWRP. As far as I remember, you can boot directly to TWRP by pressing POWER + VOL UP when the device is off.
4) In TWRP, swipe to allow modifications. Go to wipe - advanced wipe - and select dalvik/ART, system, data, and cache - swipe to wipe. You may also want to wipe your internal/external storage to avoid dirty data from previous ROM and apps.
5) Go to install - select your ROM zip and flash it - also flash Magisk and GApps after that (if needed)
6) Reboot system. If asked to install TWRP system app, just unselect all checkboxes and press do not install.
7) You're done. First boot will take a while, be patient.
No, kernel is already shipped within the ROM itself. No ROM comes with no kernel (lol). Moreover, most custom kernels on the J4+ forum may not be compatible for Android 10 yet. The OP also stated do not flash custom kernel if you want to get his support. However, if you insisted, make sure to reflash Magisk (if installed before) after flashing custom kernel. Alternatively, flash the custom kernel first before flashing Magisk.
No, OrangeFox recovery is not tested. If you're having trouble flashing the ROM using OrangeFox, unpack TWRP tar file and flash the recovery.img as recovery inside OrangeFox. After reboot, you will have TWRP again as your recovery (press POWER + VOL UP, as stated earlier).
ROM screenshot: (Stock apps are actually there and just like in LOS 16, sorry I already uninstalled most of them)

Andhika24kd said:
Let me make the steps clear for you:
1) You must be on Android Pie (custom or stock ROM doesn't matter). If you're on Samsung Oreo (U2), upgrade to Samsung Pie first so the device bootloader will be upgraded to U4 or newer.
2) If you're on Samsung Pie, flash TWRP and do all the required steps (this includes flashing RMM bypass, flashing encryption disabler, and formatting your data). If you're already using custom ROM, just skip this step.
3) Go to TWRP. As far as I remember, you can boot directly to TWRP by pressing POWER + VOL UP when the device is off.
4) In TWRP, swipe to allow modifications. Go to wipe - advanced wipe - and select dalvik/ART, system, data, and cache - swipe to wipe. You may also want to wipe your internal/external storage to avoid dirty data from previous ROM and apps.
5) Go to install - select your ROM zip and flash it - also flash Magisk and GApps after that (if needed)
6) Reboot system. If asked to install TWRP system app, just unselect all checkboxes and press do not install.
7) You're done. First boot will take a while, be patient.
No, kernel is already shipped within the ROM itself. No ROM comes with no kernel (lol). Moreover, most custom kernels on the J4+ forum may not be compatible for Android 10 yet. The OP also stated do not flash custom kernel if you want to get his support. However, if you insisted, make sure to reflash Magisk (if installed before) after flashing custom kernel. Alternatively, flash the custom kernel first before flashing Magisk.
No, OrangeFox recovery is not tested. If you're having trouble flashing the ROM using OrangeFox, unpack TWRP tar file and flash the recovery.img as recovery inside OrangeFox. After reboot, you will have TWRP again as your recovery (press POWER + VOL UP, as stated earlier).
Click to expand...
Click to collapse
OK , thanks for the tutorial also the full explanation

Can we get some screenshots?

any temp fix for VoLTE and sec sim voice

swarupgolui said:
any temp fix for VoLTE and sec sim voice
Click to expand...
Click to collapse
Maybe you could try sending logcat when attempting voice (call?) on SIM 2. There is a handy app on Play Store called "Logcat Reader" to catch & filter logs easily, just press to round button to record the logs.
I currently can't do it since I don't have someone important to call.

swarupgolui said:
any temp fix for VoLTE and sec sim voice
Click to expand...
Click to collapse
Samsung's ims is heavily OneUI framework dependent. Fixing it is kinda miracle. I don't think it will be ever fixed. But if you contact me on telegram, we might try to fix it. Also trying to fix voice of second sim.

This rom for j6+ sir? , I cant flash it .

KotaMangga said:
This rom for j6+ sir? , I cant flash it .
Click to expand...
Click to collapse
Check the thread on j6+ forum.

ataberkozen said:
Samsung's ims is heavily OneUI framework dependent. Fixing it is kinda miracle. I don't think it will be ever fixed. But if you contact me on telegram, we might try to fix it. Also trying to fix voice of second sim.
Click to expand...
Click to collapse
telegram link?

swarupgolui said:
telegram link?
Click to expand...
Click to collapse
MacTavishAO

ataberkozen said:
MacTavishAO
Click to expand...
Click to collapse
already send the msg reply plz
my id @metalgod_IN

ataberkozen said:
Check the thread on j6+ forum.
Click to expand...
Click to collapse
no, I mean it's for j4+?
E3004 : This package is for j6primelte ; your device is j4primelte.

KotaMangga said:
no, I mean it's for j4+?
E3004 : This package is for j6primelte ; your device is j4primelte.
Click to expand...
Click to collapse
Don't click on "Download Latest Version", click on zip name with j4primelte.

I has installed the rom sir , this rom more faster.
I see little problem :
1. when i change to power saver , battery indicator going red . but after switch mode , its back normal

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S22 Ultra (Exynos)

{
"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 S22 Ultra S908B
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S22 Ultra: AFH: b0s twrp and kernel / Drive: b0s twrp and kernel
3. Reboot to download mode
4. Put the TWRP TAR for your device with Odin in the AP slot, vbmeta_disabled_R.tar in USERDATA slot and click start.
5. Reboot to recovery via recovery key combo (Vol up + power + USB connected).
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.​- Go back to Wipe > Format Data > type yes.​- Reboot to recovery.​7. Flash custom kernel and magisk apk in twrp.
8. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
@Dan_FFM (David Dean) for helping with convert readonly f2fs vendor to readwrite
Donators
Sources:
Kernel tree
Device tree

Changelog:
GitHub History

Note1: You need a custom permissive kernel to boot with R/W vendor.
Note2: If you got bootloop on Samsung logo, reboot to TWRP and wipe metadata from Advanced Wipe section.

Any love for s22/s22+?

Hi, this it's Really cool, But no more official releases?

NisseGurra said:
Any love for s22/s22+?
Click to expand...
Click to collapse
Soon, join the group and provide me with some files

ANyone already test it?
Does it works stable?

dantist_140 said:
ANyone already test it?
Does it works stable?
Click to expand...
Click to collapse
No Problems so far.. Installed and decrypted since 6 Days now

Daniel210191 said:
No Problems so far.. Installed and decrypted since 6 Days now
Click to expand...
Click to collapse
I cant delete any in /system/ directory via Solid Explorer or TWRP File Manager - "rm -rf ERROR 1."
What am I doing wrong ?
==============
UPD: There are no /system/ in Backup or Format tabs...
UPD2: I tryed for remount it by a cmd:
mount -o rw,remount /system_root
and have output:
'/dev/bloc/dm-0' is read-only.
Filesystem on /system - F2FS.
Total: /system/ directory is read only. I have no way to remount it to RW to make a changes...

So when making a backup what partitions do I need to check? There is a lot more partitions these days some I've never heard of before lol just got the s22 ultra as an upgrade coming from Note 9. oh how i already miss my headphone jack and sd card lmao holding on to this old note as looong as I can. But yea just a little confused note 9 had way less partitions and I know some aren't needed for backups just can't remember and don't know about these new partitions ie: Super, Prism , Etc

dr.ketan said:
Super + data should be enough. Though you can backup prism + optics
As S22 have system ro nothing going to change in system, product,etc except vendor. For that purpose you needs super backup. Prism and optics for csc related.
Click to expand...
Click to collapse
dr.ketan:
Here some my thoughts and explanation about TWRP backup and restore
Firstly brief explanation about what does partition contains.
Boot : It is Kernel
Recovery : It is Recovery
super : That contains odm,product,system and vendor partitoin all togather.
optics : CSC files (where we routinely making changes for csc features) and network settings depending on your carrier
prism : carrier related apps and other stuff . In odin when you flash CSC*_ or Home_CSC* these two optics and prism gets flashed.
data : That is all your installed app and made changes in settings
Now what to backup/restore?
boot - Helps if something messed up with magisk or waht to restore kernel after flashing custom.
recovery - usually it doesn't require but if you flash some other recovery(TWRP) and you want to restore one in backup, that helps
super : As stated above these is main system, if something you have messed up in system/vendor (usually with flashing something, or erasing something) you can restore by super.img.
optics and prism : as explained above are CSC files, Rather than restoring it, I prefer to flash HOME_CSC*.tar.md5 to make csc compartment clean. So to backup or not not much important.
data : This very sensible part. I prefer to make data backup when there is no samsung a/c or Lockscreen protection there. Also don't restore it cross version of ROM. Also some common mistakes user making is, He/She clen install ROM and then restore data partiton of previous ROM. This is worst then even dirty installing ROM, never do it. It is just false sense of satisfaction that you made a clean install. According me, data partiton backup best to be made just after complete clean install ROM and setting up device without adding any account and lockscreen protection. So when you restore this backup, you will have a device just like you recently completed clean install and save your time to setup initial wizard
Backup Application,Call logs,Contacts,SMS etc
Titanium backup was ruling for decade for these but since A11 it's not trust worthy and on A12 almost useless.
Swift Backup is now my choice (Some other like Migrate, App dash (by RD XDA dev flar2) also alternatives)
For contacts : I do prefer google sync. Just adding google ac everything will be restore on it's own, provided you are saving contacts in google. In case you want to make off line backup of contact, there is a built in utility in phone. Contact - settings - export - This will create a file. Similarly browse same file while you want to import contacts. Catch in this is your contact image will not retain size and it just backup thumbnail picture.
Only one utilility I have found that makes offline contact backup without distoring image quality is My Phone Explore client (needs on both PC and Phone). Also this utility is best for wireless file manager.
Schheduled backup - A must needed utility.
I always prefer clean installation (Factory reset withot wiping media files) and really it takes less than 30 minutes to setup everything.
If you enable schedule backup utility in your Backup app (e.g Swift backup have this) and make some profile like
1.Backup - new app at X time then it will auto backup all app that you have new installed at given time
2.Backup updated app at x time - This will make backup of any app that you have updated in store will backup at given time
3.Any app which get data changes frequently and you needs data changes like whatsapp then create a profile favorite app - add whatsapp in favorite and schedule it to make backup daily at given time.
with these your device always remain ready to clean install anytime instead of last moment backup or some urgent clean install needed.
Also Folder Sync is good utility if you needs duplicate copy of files from Internal storage with scheduled operation.
Hope this may helpful and answer lots of queries for many.
Click to expand...
Click to collapse
Passing this info along to anyone else that was confused by which partitions were needed for a basic backup

Any chance we can get the kernel to support OverlayFS so it can emulate system rw? Trying to get this module to work Magisk OverlayFS.
Thanks

Two questions:
1. Is the custom kernel required to be flashed?
I have rooted ROM and Magisk is already installed.
2. Can be TWRP installed on this phone or do I need first back to stock ROM flashing original AP* tar file?

rafal.polska.b said:
Two questions:
1. Is the custom kernel required to be flashed?
I have rooted ROM and Magisk is already installed.
2. Can be TWRP installed on this phone or do I need first back to stock ROM flashing original AP* tar file?
Click to expand...
Click to collapse
1.If you want to use TWRP fully functional, you needs to run multidisabler and that needs to have custom kernel. If you want to use TWRP and don't run multidisabler, it is fine with stock kernel too, but here TWRP have very limited functions like backup partition (except data partition) only to USB storage. SO say, yes you needs custom kernel, else it is useless to have TWRP
2. You can install straighway TWRP (must be included patched vbmeta) if you are already on stock rooted ROM + you needs to run multidisabler + needs to Format data.

dr.ketan said:
1.If you want to use TWRP fully functional, you needs to run multidisabler and that needs to have custom kernel. If you want to use TWRP and don't run multidisabler, it is fine with stock kernel too, but here TWRP have very limited functions like backup partition (except data partition) only to USB storage. SO say, yes you needs custom kernel, else it is useless to have TWRP
2. You can install straighway TWRP (must be included patched vbmeta) if you are already on stock rooted ROM + you needs to run multidisabler + needs to Format data.
Click to expand...
Click to collapse
TWRP installed, custom kernel too.
Everything went OK except Wipe -> Format Data.
It ended with "Successful" final result but generated few errors at the beginnig:
Anyway, when restarting my phhone to recovery TWRP is launched, in system everything is OK.
Now I'm waiting for dr.ketan ROM version S09.
Thanks so far for your explanations @dr.ketan

Guys I have just received a Korean 512GB S908N, the phone seems to have a Snapdragon CPU. Why is it in this Exynos thread?
Please help me understand, searching has not led to any answers so far about what the CPU really is. The internet seems to have mixed feelings.
What is happening?

babyboy3265 said:
Guys I have just received a Korean 512GB S908N, the phone seems to have a Snapdragon CPU. Why is it in this Exynos thread?
Please help me understand, searching has not led to any answers so far about what the CPU really is. The internet seems to have mixed feelings.
What is happening?
Click to expand...
Click to collapse
Install cpu-z or any app that check for cpu and check, also check for bootloader. Might be flashed to different fake software

afaneh92 said:
Install cpu-z or any app that check for cpu and check, also check for bootloader. Might be flashed to different fake software
Click to expand...
Click to collapse
Well it is the weirdest thing... Look at the screenshots.. The phone is original in a box.

babyboy3265 said:
Well it is the weirdest thing... Look at the screenshots.. The phone is original in a box.
Click to expand...
Click to collapse
Let me double check

babyboy3265 said:
Well it is the weirdest thing... Look at the screenshots.. The phone is original in a box.
Click to expand...
Click to collapse
OK you have a snapdragon S22 Ultra, it was mistake maybe samsung changed her mind when I first searched they said exynos.

Development [ROM][13][UNOFFICIAL] LineageOS 20 for Xiaomi 12

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
To find out more about LineageOS visit the official Website.
All the source code for LineageOS is available in the LineageOS Github organization. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
Installation
Warning: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements​
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
LineageOS is provided as-is with no warranty. While we attempt to verify everything works you are installing this at your own risk!
Warning: Before following these instructions please ensure that the device is currently using Android 13 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 13, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the bootloader​Note: The steps below only need to be run once per device. They require a machine running Windows 7 or newer.
Warning: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
Tip: It is highly recommended to have the latest official MIUI stable package installed on the device, before proceeding with unlock.
Create a Mi account on Xiaomi’s website. Beware that one account is only allowed to unlock one unique device every 30 days.
Add a phone number to your Mi account.
Insert a SIM into your phone.
Enable developer options in Settings > About Phone by repeatedly tapping MIUI Version.
Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status.
Download the Mi Unlock app (Windows is required to run the app).
Run the Mi Unlock app and follow the instructions provided by the app. It may tell you that you have to wait up to 30 days. If it does so, please wait the quoted amount of time before continuing to the next step!
After device and Mi account are successfully verified, the bootloader should be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing additional partitions​Warning: This platform requires additional partitions to be flashed for recovery to work properly, the process to do so is described below.
Download the following files from here.
boot.img
dtbo.img
vendor_boot.img
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
fastboot flash boot <boot>.img
fastboot flash dtbo <dtbo>.img
fastboot flash vendor_boot <vendor_boot>.img
Booting a custom recovery using fastboot​
Download Lineage Recovery. Simply download the latest recovery file, named recovery.img.
Important: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
Connect your device to your PC via USB if it isn’t already.
If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Down + Power. Keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable (preferably use a USB Type-A 2.0 one or a USB hub) and port!
Tip: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash a recovery on your device by typing (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to recovery__a /recovery__b rather than recovery_a / recovery_b if you try to flash recovery. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to recovery__a, you must flash to recovery_a.
Now reboot into recovery to verify the installation.
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Note: If your recovery does not show the LineageOS logo, you accidentally booted into the wrong recovery. Please start at the top of this section!
Installing LineageOS from recovery​
Download the LineageOS installation package that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. Keep holding both buttons until the “MI” logo appears on the screen, then release.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage.
Return to the main menu.
Sideload the LineageOS .zip package but do not reboot before you read/followed the rest of the instructions!
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Tip: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
All set!​Once you have installed everything successfully, you can now reboot your device into the OS for the first time!
Click the back arrow in the top left of the screen, then “Reboot system now”.
Note: The first boot usually takes no longer than 15 minutes, depending on the device. If it takes longer, you may have missed a step, otherwise feel free to get assistance.
Download link:
Builds are released here: Releases on GitHub
Warning: These releases include builds for other devices i own, make sure to download files from a release for Xiaomi 12, for example: "LineageOS 20.0 for Xiaomi 2201123G (cupid)"
Note: There are two variants which are not necessarily released at the same time. Vanilla builds are pure LineageOS without additional apps and GMS builds include Google services. The GMS builds are too big for github releases, so they will be uploaded to this shared folder on Google Drive instead
Source Code
Please read this thread about the OSS kernel on Xiaomi 12.
All kernel related source code can be found here.
Device trees for LineageOS can be found here.
Donate to support development:
Donate via PayPal to ArianK16a
Donate via PayPal to LineageOS

MiuiCamera for LineageOS on Xiaomi 12
I have created a Magisk Module to get the MIUI camera app on LineageOS 20. It's extracted from MIUI V14.0.2.0.TLCMICM.

For "new" users you could also give a step by step instruction how to update. Because format data is not always necessary.

i get " low resource device detected" error when trying to install Gapps

Will go official?

McFlypants said:
For "new" users you could also give a step by step instruction how to update. Because format data is not always necessary.
Click to expand...
Click to collapse
I will add that soon
quardier said:
i get " low resource device detected" error when trying to install Gapps
Click to expand...
Click to collapse
That's because the system partitions use erofs, a read only file system without reserved space. You can use the GMS variants if you want to use Google services or install Google apps that use overlay over the partitions.
vyvy said:
Will go official?
Click to expand...
Click to collapse
I aim to get this official one day in future, but this is not really close yet because of a different builds process due to GKI compliance which isn't supported officially in lineage.

outstanding work from the ROMs developer. thank you for bringing stable Lineage to our device

Xiaomi 12 currently no Lineage ROM bug?

Kkjin said:
Xiaomi 12 currently no Lineage ROM bug?
Click to expand...
Click to collapse
It has an error - cannot install Gapps, in TWRP it throws error 1

funciona no redmi note 12 4g?
Mod translation: it works not redmi note 12 4g?

Jadson note12 4g said:
Mod translation: it works not redmi note 12 4g?
Click to expand...
Click to collapse
Greetings, and welcome to XDA. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50

Volte und voWifi calls sometimes show a strange number format.
Sometimes it's the caller number and my own number after each other, sometimes it's both numbers with a & or a + inbetween.
Even if the contact is known, the number in wrong format is shown.
Any help? I'm still on the 20230316 build. Is it fixed on the newest one?

NeoArian said:
MiuiCamera for LineageOS on Xiaomi 12
I have created a Magisk Module to get the MIUI camera app on LineageOS 20. It's extracted from MIUI V14.0.2.0.TLCMICM.
Click to expand...
Click to collapse
Is it possible to make the Xiaomi Leica camera inbuilt? Or a Magisk Module of the Xiaomi Leica Camera App?

Someone tried NFC payment and banking apps with this ROM ? Thank you