[RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A80 - Samsung Galaxy A80 Real Life Review

[RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A80 - Samsung Galaxy A80 Real Life Review

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.
HTML:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* y
Let’s start with the installation process
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
If you already installed a previous version of TWRP, start with step 4.
If you already have TWRP installed and just want to root, start with step 5.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta.tar then go into download mode on your device. Put vbmeta.tar to AP in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
Developers specific details
Sources
https://github.com/blacktox/r1q
https://github.com/Grarak/android_bootable_recovery-1
Downloads
https://github.com/blacktox/r1q/releases
To flash it in Odin pack it as tar with 7zip or a compression tool of your liking.
XDA:DevDB Information
twrp galaxy a80, Tool/Utility for the Samsung Galaxy A80
Contributors
blackbuga
Version Information
Status: Testing
Created 2019-11-09
Last Updated 2019-11-09

Good day. Excuse me, where is vbmeta.tar located?
---------- Post added at 11:19 PM ---------- Previous post was at 10:48 PM ----------
Can find out. Is this accurate for the SM-A805? I hope it doesn’t matter F / DS and others? And what does the root look like? Can Magisk be installed?

If of course you can? Describe the points more clearly, since the description indicates points 1 2 3 4 but they are not! There is only a TWRP installation. And as I understand it ROOT. But in the archive folder r1q-3.3.1. As I understand it, just sew this archive through TWRP?

I understood your instructions. I did everything as expected! In TWRP, the car does not work! I can’t press anything.

Twrp booted but no touch. I cannot control twrp. Installed SG7 fw and now TWRP stucks on teamwin logo.

I will upload new build with fix for touch
Sent from my SM-A805F using Tapatalk

Now it just doesn't load further than the logo! !(

blackbuga said:
I will upload new build with fix for touch
Sent from my SM-A805F using Tapatalk
Click to expand...
Click to collapse
Awesome!

https://github.com/blacktox/r1q/releases/download/TWRP/recovery.img
NEW BUILD FOXED TOUCHSCREEN

Anyone managed to get this recovery fully working and flash a gsi?

Is it possible to flash a GSI with this TWRP? If anyone has successfully done so please post install instructions...

Related

AOSP N for DOOGEE X30

ROM is still under development.
Downloads
20180427-1610
20181006-1451
XDA:DevDB Information
DOOGEE_X30_AOSP, ROM for all devices (see above for details)
Contributors
ttomovcik, VeteranoX, SoaringLake
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 20181127-1452
Beta Release Date: 2018-11-27
Created 2018-05-24
Last Updated 2018-11-28

Reserved

Reserved
Due to some bugs in TWRP, we recommend to charge your device to AT LEAST 70% and keep the device plugged in. I'm still waiting for DOOGEE to respond (emailed them if they can send the kernel source). So In the meantime, enjoy overheating and quick battery discharge in TWRP.
New build out! This addresses the following bugs:
Camera FC when opening settings
Camera slow-mo not working
Perfrmance issues
Enabled on-screen navbar - hardware buttons will remain enabled, however, changing Generic.kl will result in HW buttons not working
Changelog
20181018-1337 (Created by SoaringLake)
[FIX] Missing launcher
[ADDED] Face recognition
20181006
Removed Gallery2 - caused problems, needs to be replaced with GApps
Added sqlite3
Taking screenshots now works
20180427-1610
Initial release
Features / what's working
GPS
Phone calls / mobile data
Wi-Fi
DuraSpeed
Brightness (can be adjusted lower than stock)
Volume changing works (stock ROM doesn't have this for some reason)
Youtube supports VR
MiraVision
Bugs / feature requests
Settings > about phone is showing some random indian guy as maintainer. This is due to the fact that this ROM is ported from another device to X30. Will fix that later, probably
When quickboot is active, phone will charge when off without the charging screen animation
NVRAM ERROR is showing in Wi-Fi networks
Google Play services not updating automatically
Unable to open Google Assistant, opens up multitasking view instead
Split screen buggy
No mediatek gestures
Instagram videos rendering incorrectly (SoaringLake)
Camera FC when going to settings
FM Radio volume issues
Camera slow-mo not working
Installation
Unlock bootloader and flash TWRP/CWM (1)
Flash ROM and GApps in one go. DO NOT REBOOT BETWEEN ZIP FLASHING (2)
Wipe cache
Reboot
(1) - Installing TWRP
Enable OEM unlocking in developer options
Download TWRP from here
Reboot into bootloader (Power off and then power on while holding volumeUp)
On your PC, flash it with: "fastboot flash recovery <filename>.img"
Reboot into recovery (Power off, then Power on while holding VolumeUp and select Recovery)
(2) - Flashing ZIP images
Make sure to wipe device
Flash the ROM from device or SD card. Sideload will result in no OS installed error
(Optional) Flash any variant of openGapps - ARM/7.1.1

thread closed until the download links will be available @ttomovcik pm us when you`re ready to share the links
-=-=-
thread re-opened

How can I root?
Hey can you publish the instructions about to root and install Twrp?
And thanks for your work.

mediafire.com/file/3zifgay1h0c334g/TWRP%20dogee%20x30.rar
install via fastboot "fastboot flash recovery recovery.img", only remember to unlock bootloader 1. in developer options> allow OEM unlock 2. In fastboot "fastboot OEM unlock"
the first result on google after entering doogee x30 root

I'm Stuck!
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?

VeteranoX said:
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?
Click to expand...
Click to collapse
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop

SoaringLake said:
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop
Click to expand...
Click to collapse
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.

VeteranoX said:
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.
Click to expand...
Click to collapse
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo

Phliz Touch recovery 6.59.0
for those willing to give a link to philz touch recovery in version 6.59.0, I worked on ClockWokMod but can not see the external sd card
mega.nz/#!PbpHlbjR!VfIomQYwPQQ6f5-1mT7tIF3x66X692rcBiYUQeusLto

I got it!
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
SoaringLake said:
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo
Click to expand...
Click to collapse
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.

VeteranoX said:
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
Click to expand...
Click to collapse
1. go to the developer options in the system, select allow OEM unlock and debug usb.
2, issue the command in ADB "adb reboot-bootloader"
3. issue the command "fastboot oem unlock"
4. restart the "Fastboot reboot" phone
5. allow for wipe data,
6. go to fastboot,
7. issue the command "fastboot flash recovery $ image"
$ image = name with the extension image recovery

I got it!
Hey now is workin (rom and root) i'm testing now and i will send a feedback later but now just i can say
Faster!
Thank you!

Does anyone know how to fix the error: NVRAM WARRNING: Err 0x02

[RECOVERY][STABLE]Unoffical TWRP for Xiaomi Mi A3[laurel_sprout]

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:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Whats Working?
Everything is working
Can change Slot A/Slot B on twrp
SDcard and OTG working
Decryption of Data working
Flashing of roms work pie and even Q roms work.
HOW TO UPDATE a ROM and Keep TWRP and ROOT:
Before all Disable all magisk modules for boths methods
- Put rom.zip, twrp installer.zip and magisk.zip on your internal storage or sdcard;
- Flash Rom;
- Flash TWRP Installer;
- Flash magisk(recommend to use Magisk v19.4);
- Reboot.
Download:
TWRP 3.3.1-2 Unofficial Installer by Nikesh Kataria
TWRP 3.3.1-2 Unofficial by Nikesh Kataria
Donations:
Credits:
Thanks to @mauronofrio for a great help to make a stable recovery
Thanks to @Typhus_ for hardcore testing
Thanks to @prakash78 for testing
Contributors
Nik001
Source Code: https://github.com/Nikesh001/android_device_xiaomi_laurel_sprout-twrp
Version Information
Status: Stable
Created 2019-10-21

Reserved

This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!

Typhus_ said:
This man -> @Nik001 deserves a beer!!!
Thank you for delivering us a fully working TWRP for laurel_sprout!
Cheers!
Click to expand...
Click to collapse
Welcome and thank you for testing twrp.:fingers-crossed:

Thank u peru sir

A3 real modding let's start

Good Job @Nik001

Anyone tell how to flash twrp... proper commands
Please
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Is that tested anyone.

Stock fw 10.3.8 (global) not booting with this twrp - in 10.3.8 audio modules have strange dependence "saved_command_line" symbol from kernel. For loading this modules need patch kernel sources -
diff --git a/init/main.c b/init/main.c
index 6d1880f0b852..2106f54a7008 100644
--- a/init/main.c
+++ b/init/main.c
@@ -128,6 +128,7 @@ void (*__initdata late_time_init)(void);
char __initdata boot_command_line[COMMAND_LINE_SIZE];
/* Untouched saved command line (eg. for /proc) */
char *saved_command_line;
+EXPORT_SYMBOL_GPL(saved_command_line);
/* Command line for parameter parsing */
static char *static_command_line;
/* Command line for per-initcall parameter parsing */
Click to expand...
Click to collapse

Proper install method explained
Hello!
Please, @Nik001, update the OP with the install method that I'm going to describe next, ok?
It's just to avoid future complications (lost of Wi-Fi, sound, etc...) for "not that experienced users".
Your bootloader must be unlocked. If it's not, then follow step 1 of the instructions provided HERE.
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (being on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot getvar current-slot (to check what's your current active slot)
fastboot set_active b (if your active slot was a, if it was b then change it to a)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
When TWRP recovery boots, if you have a stock boot.img that matches the build on this "currently active" slot, flash it into boot partition. If you don't have, then just ignore this step...(it's not mandatory)
Install the TWRP zip (always install the latest build available)
Change slot to the one that was active on the beginning of these steps and reboot to Recovery (just to make sure that the slot, in fact, was changed)
Reboot to System
Why do I suggest this?
By doing this method (which seems more complicated but, trust me, it's how it should be done) we will flash TWRP img into the "inactive" slot, thus, not breaking anything on the "currently active" slot. When TWRP boots, it will patch both slots boot ramdisks. But the thing is, on the "currently active" slot (the one inactive on the beginning) it will patch the TWRP img but, on the "currently inactive" slot (the one that was active on the beginning), it will patch the stock boot.img, thus, no bug will happen that usually appears when a user accidentally flashes the wrong boot.img into boot partition.
On the other hand, if we have a stock boot.img, that matches the build on the "inactive" slot, we could flash it into boot partition before installing the zip that patches ramdisk. By doing this we will patch both stock boot.img present on both slots (instead of patching TWRP img and boot.img).
Cheers!

Sapper Morton said:
The method Typhus shared works 100% of the times; however I must say, I don't use it, just preference; as it follows, instead of flashing into the inactive slot, I flash the pre_patched boot image into the active slot, this of course will mostly like break network and other components on the ROM, if you mismatch image versions; however, if you flash the stock boot image (using install button, inside TWRP, tapping into 'images', select your stock boot.img) and then patch it using the TWRP Installer right after, you will be using the right image, so no problem will occur, and mostly important, no slot change is needed. Both methods works, choose what you prefer, just read it carefully and I repeat, always use the same boot image from your firmware, a lot of confusion comes to the fact, that when you uses TWRP.img or Magisk.img they aren't boot images, but they are; A/B partition scheme doesn't use some individual partitions anymore, as /recovery, thus is extremely important to patch your boot image, where the recovery, kernel and other components now lives.
Click to expand...
Click to collapse
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!

Typhus_ said:
So, in other words, your method is this (correct me if I'm wrong):
Download TWRP zip file and copy it to your device (internal or external storage)
Download TWRP img file and and store it, on the folder where you have adb and fastboot files, on your PC
Open a cmd line and execute these commands (beeing on that folder, of course):
adb devices (to make sure your device is detected)
adb reboot bootloader (to reboot into fastboot mode)
fastboot erase boot
fastboot flash boot twrp-3.3.1-2-unofficial-laurel_sprout.img
fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System)
Flash stock boot.img that matches your current build using TWRP install Image feature, into boot partition
Install the TWRP zip (always install the latest build available)
Reboot to System
Is that it?
If it is, the only downside I see is that, when a new version comes out (through OTA for example), you'll first need to get your hands on a stock boot.img that matches the new build.
Right?
Cheers!
Click to expand...
Click to collapse
As someone who just wants to root his phone with TWRP and few magisk modules, and not miss out on OTAs, seeing these many methods is so confusing and overwhelming ?

After flashing recovery from pc..then go for fastboot reboot from minimal adb and " volume+ key" i saw error in my phone "no command"

Sapper Morton said:
Use the method Typhus explained, it's more simple in the long run; there will be no need to manually flash stock boot image afterwards, since Magisk will have done a proper backup, thus, you will only need to use 'restore image' feature inside Magisk Manager; When taking an OTA, make sure to read the complete Magisk documentation before proceeding:
https://topjohnwu.github.io/Magisk/tutorials.html
Click to expand...
Click to collapse
Thank you! I will do that. But one more thing I'd like to ask. Do you know where I could find the boot image for 10.3.8.0.PFQMIXM? I checked git for dumps, but I couldn't find the boot image for this one.

Sapper Morton said:
Sure, read the OP; Typhus has linked a couple of boot images, including 10.3.8.0 PFQMIXM.
https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509
Click to expand...
Click to collapse
Sick! Thank you very much, sir!

What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.

Makishima said:
What about flashing this on an already rooted phone with Magisk modules and the previously available TWRP by mauronofrio? Any complicated procedures? Is slot changing etc still necessary?
Click to expand...
Click to collapse
Just flash the zip in twrp that you have.
That's what I did and it worked no problem on pe ROM

Typhus_ said:
In that case, obviously, simply flash the new TWRP zip.
The install method I've explained is for everyone who never had TWRP, or Magisk patched boot, installed on the device.
Click to expand...
Click to collapse
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?

Makishima said:
I did as you said but it says 'NOTE: You are now unrooted!'. Do I need to flash Magisk again?
Click to expand...
Click to collapse
Yes, that's right.

[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]

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 you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* 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.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.6.x
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing a custom recovery for the first time, open Odin on your pc. Download both the latest recovery and the vbmeta_disabled file attached below. Boot your phone in download mode.
2) Untick "autoreboot" and flash the vbmeta_disabled.tar file in the AP slot.
3) Follow the instructions on your phone's screen to reboot the phone.
4) Quickly repeat the steps to go back in download mode.
5) Untick "auto reboot" and flash the recovery.tar you downloaded in the AP slot
6) Follow the instructions on your phone's screen to reboot the phone.
7) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.6.x
8) Go to wipe, and format your data.
9) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
10) You now have twrp 3.6.x
Download
Twrp 3.6.x for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99

Fix etc/fstab "system_root" to "system" please

Thanks for this amazing build. Never ceases to surprise me.

can we have this twrp without root on phone .... ?
sorry for my silly question

Can you install this on the A10e? (A102)

koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
no

howdeedodat said:
can we have this twrp without root on phone .... ?
sorry for my silly question
Click to expand...
Click to collapse
yeah

UPDATE NOTICE:
Twrp 3.5.1 released

Chatur27 said:
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 you getting fired because the alarm app failed. Please
* do some research if you have any concerns about this recovery
* 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.
Installation
Method 1
1) If you already have twrp on your phone, extract recovery.img from the tar file using Zarchiver (Download here).
2) Reboot your phone and boot into recovery.
3) Flash the recovery.img as "recovery"
4) Finally reboot to recovery to enjoy new twrp 3.5.1
Method 2 (WARNING: YOU WILL LOSE YOUR DATA)
1) If you are installing custom recovery for the first time, open Odin on your pc and load the tar file (download below) in the AP slot.
2) On the left of Odin, click on options and untick (remove the tick from) "autoreboot"
3) Boot your phone into download mode and connect it to the pc.
3) Flash the file in Odin. When flashing is complete in Odin, hold power + volume down keys on your phone to reboot
4) As soon as the screen turns off, release all keys and press power + volume down keys till you boot into twrp 3.5.1
5) Go to wipe, and format your data.
6) Flash disable_dm_verity.zip (attached in post) in twrp to avoid fbe error.
7) You now have twrp 3.5.1
Download
Twrp 3.5.1 for A10
Maintainer
Gabriel260
Support
Contact maintainer on telegram to report any bug → Gabriel
Thanks
TWRP team
Topjohnwu for root
afaneh92
Topser99
Click to expand...
Click to collapse
Where is the tar file?

LemonadeSnake said:
Where is the tar file?
Click to expand...
Click to collapse
Download and install 7zip and right click "recovery.img" file > Select 7-Zip from openned menu>Select "Add to Archive" > Replace "Archive Format" to TAR > Click OK > Wait To Compressing... ANDD Ready your TAR file, WALA!
Nice Day!

What has changed compared to the previous version?
Thanks for ALL!

CrazyGenius said:
Download and install 7zip and right click "recovery.img" file > Select 7-Zip from openned menu>Select "Add to Archive" > Replace "Archive Format" to TAR > Click OK > Wait To Compressing... ANDD Ready your TAR file, WALA!
Nice Day!
Click to expand...
Click to collapse
well too late oof i tried another method by somebody else and my phone is now bootlooping

EDIT:
Okay, now everything works, I did it according to this tutorial:[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)
Hello,
I have a problem installing TWRP, turned on OEM unlock, then unlocked the bootloader, then when the phone rebooted and went into OEM setup it was turned off so I turned it on. I put my phone into download mode and tried to load twarp via Odin and got the message "Only official released binaries are allowed to be flashed (RECOVERY).
Now, after starting the phone, when I enter programming options, the OEM unlock option is gone
Can I do something about it now? I have SM-A105FN
{
"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"
}

LemonadeSnake said:
well too late oof i tried another method by somebody else and my phone is now bootlooping
Click to expand...
Click to collapse
If you want to get rid of this thing, you can download the Official Firmware, extract it from the compressed file (and extract AP* file), make the necessary changes (replace stock "recovery.img" with TWRP img file, replace stock "vbmeta.img" with custom vbmeta and sarees...) and re-compress all extraxted and changed files to TAR file. Unselect "Auto Reboot" from Odin, select modified AP file from Odin AP menu and flash. If flashing complated, reboot phone directly recovery mode and flash all files.

CrazyGenius said:
If you want to get rid of this thing, you can download the Official Firmware, extract it from the compressed file (and extract AP* file), make the necessary changes (replace stock "recovery.img" with TWRP img file, replace stock "vbmeta.img" with custom vbmeta and sarees...) and re-compress all extraxted and changed files to TAR file. Unselect "Auto Reboot" from Odin, select modified AP file from Odin AP menu and flash. If flashing complated, reboot phone directly recovery mode and flash all files.
Click to expand...
Click to collapse
i can't access download mode without a jig, because it can't even get to the samsung loop animation without restarting.

JUST A NOTICE:
Twrp for A10 is now official !
Cheers

koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
koyo said:
Can you install this on the A10e? (A102)
Click to expand...
Click to collapse
If you need twrp please send me stock recovery.img

Topser99 said:
If you need twrp please send me stock recovery.img
Click to expand...
Click to collapse
I don't have the phone. I was gonna buy it on the basis that it had TWRP but it doesn't so I bought the Moto G7 Play

Staniczek said:
EDIT:
Okay, now everything works, I did it according to this tutorial:[Guide/Magisk] Root for the Galaxy A10 Series & Flash TWRP (Unlocked Exynos only, A10s not supported)
Hello,
I have a problem installing TWRP, turned on OEM unlock, then unlocked the bootloader, then when the phone rebooted and went into OEM setup it was turned off so I turned it on. I put my phone into download mode and tried to load twarp via Odin and got the message "Only official released binaries are allowed to be flashed (RECOVERY).
Now, after starting the phone, when I enter programming options, the OEM unlock option is gone
Can I do something about it now? I have SM-A105FN
View attachment 5251963
Click to expand...
Click to collapse
If you are 100% sure of having your bootlaoder unlocked, reflash the stock rom you are on. It worked for me yesterday night.

Unable to Boot TWRP in Recovery mode, bootloop issues

Hello guys, I'm a beginner in this flashing stuff. I have watched youtube over a guy flashing Android 10 on his Samsung note 3. I carefully took his steps and i make sure that my model is compatible with said ROM, Mine is Samsung note 3 lte (N9005), Snapdragon. The issues that i am currently having is on flashing TWRP on my Samsung Note 3, because it won't boot on recovery mode despite i press the exact button as the Video describe, it just boots in recovery and then restarted on the same logo boot repeatedly. I have tried flashing LineAgeOs using the tutorial provided by LineAgeOs team and again, i make sure that the rom is fully compatible and still end up same result. Please help me on this issue. Thank you very much for giving your time reading my problems

Please describe your issue again with more details.

From you're post, it seems as though you are having issues with TWRP. Below I will give you a full tutorial on how to get TWRP up and running for your specific device. Do give this a go, as I have done the research for your specific model, and it should work just fine.
First things first, unlock your devices bootloader. You may not have done this correctly, so if it is possbile to boot into android, then try this:
How to unlock Bootloader on Samsung Galaxy Note 3 | Softstribe
Unlocking bootloader in Samsung Note 3 made easy and you can simply enable developers mode where you can perform OEM unlock.
softstribe.com
If you're bootloader is already unlocked, then proceed.
Now that the bootloader in unlocked, we need to install TWRP for your specific device. Your device is the N9005, which is the international snapdragon model. It's codename is hlte, or hlte*. For TWRP, it is also categorised as the Europe/American model (hltexx).
For flashing TWRP correctly to a samsung device, we will need odin. Odin is a flashing software for samsung devices.
Download Odin.zip from here:
Samsung Odin - Root Android download page for one click root
Samsung odin download - Root android and oneclickroot for flash / install custom ROM with one click root method
odindownload.com
(Download the latest version (v13.4.1 at the time of writing this)
Now, extract Odin.
Once we have Odin downloaded, we will need to install the correct usb drivers for Samsung phones.
Download the file below, then extract the zip and run the installer:
Samsung_USB_Driver_v1.7.31.0
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Now that odin and the drivers are ready, we need the actual twrp image which we need to flash to our device.
Here is the link, download the latest .img.tar file (3.6.1_9-0 at the time of writing):
Download TWRP for hlte
Download TWRP Open Recovery for hlte
dl.twrp.me
Do not download the normal .img file, as that cannot be flashed via odin.
Now that we're past the prerequisites, we need to actually flash twrp to your device. To begin, we must put your note 3 into download mode. To enter download mode, power off your phone completely and then press Power+Home+Vol Down at the same time and keep these three buttons pressed until your phone shows a "download mode, do not power off target!!!" screen, you can follow this video tutorial below:
Now that we are in download mode on the device, we need to get back to our computer and configure odin to flash twrp. First things first, open odin. Now, connect your phone to the computer. You should see a little "COM-" show up in one of the empty boxes in the top row under the word "ID:COM". This is good, it means that your pc successfully recognises your device.
Now, go to the options tab on the left side, makse sure that repartition is UNCHECKED. Now, click on the "AP" button, and navigate to and select the TWRP.img.tar file that you downloaded earlier. After you have selected it, click on start at the bottom right. Now it will begin to flash twrp, which should not take long. Make sure that you do not disconnect the device while flashing, wait for the phone to complete. Once it is done, the phone will reboot.
Now, just remove the battery, then put it back in. To enter TWRP recovery, keep Power+Home+Vol Up pressed, then once you see the samsung boot logo upon the phone powering on, let go of power, but keep home and volume up pressed.
Congrats! You've just flashed TWRP to your device, amazing!
Now you can go and look for custom roms to flash to your device. Since your model is the N9005, look for hlte/hlte* roms, don't use any roms if they don't support the hlte/hlte* variant.

Alright, now since you have mentioned that you want to use lineage os, here's a guide for that too.
So currently, it is recommended to use android 11 lineage os nightly builds as they are stable and official, so they should not have any bugs. So unfortunately, I cannot recommend installing lineage os android 10, as you had originally wanted, though the installation process for that will be somewhat similar. It is still not recommended to use old or unofficial builds due to bugs and lack of security updates.
First, we need to download lineage os for this device onto our pc, here's the link to the latest nightly build:
https://mirrorbits.lineageos.org/full/hlte/20220319/lineage-18.1-20220319-nightly-hlte-signed.zip
Next we need to download a GApps package for google play functionality. OpenGApps is recommended as it is open source, secure and reliable, usually with no bugs. I recommend using the nano package instead of pico if your device can handle it (your's can handle it just fine), as it contains google play functionality, and some extra google features which cannot be downloaded from google play. Here is the link to the nano package for your device (only for android 11 roms):
https://sourceforge.net/projects/opengapps/files/arm/20220215/open_gapps-arm-11.0-nano-20220215.zip/download?use_mirror=udomain&r=&use_mirror=autoselect
Now, if you want to get your device play protect certified, you will also need to download magisk for rooting, and magisk modules (so that you can download netflix and use banking apps etc.), but that is something you can do later on, and you can find any tutorial online for this.
Once the download is complete, move the lineage and opengapps .zip files to an sd card and insert it into the phone. Enter TWRP, go to wipe and click on Advanced. From here, wipe System+Data+Cache+Dalvik/ART Cache. Your files such as photos and media will not be wiped.
Next, go back to the TWRP main menu and select install. Click the select storage button at the bottom left and click on Micro SD Card. Now, click on the lineage os zip file, then click on the Add Zips to Queue button and select the opengapps zip file, then click install. This will take some time, do not interrupt it. Once it is complete, you can reboot the phone. The first reboot will take some time, and the first boot may be slow, after setting up your device, make sure to reboot it at least once.
Congrats, you've just installed a custom rom with google play functionality via TWRP!
Unfortunately, sometimes there are issues. If you still cannot get into lineage os despite waiting at least 10 minutes on the boot screen, then follow these steps below:
The lineage team says that booting issues may be due to incompatible recoveries, this means that we will have to use lineageos's own recovery to flash the rom.
For this, download the lineage os recovery.img from here:
https://mirrorbits.lineageos.org/recovery/hlte/20220319/lineage-18.1-20220319-recovery-hlte.img
Now copy this image file to your sd card and insert it into the phone.
Enter TWRP. First of all, click on wipe, then click on advanced and select System+Data+Cache+Dalvik/ART Cache and wipe. Now, go back to the main menu and click install. At the bottom right or left, there will be a button to "Install Image". Click on that button, and select the lineage recovery zip file and install it. Now go back to the main menu and click on the reboot button, then click on reboot to recovery.
Now you will boot into the lineage os recovery, from here you can install lineage os and the gapps zip files. Here is a tutorial:
This tutorial is for a oneplus phone, but it will be the same process on your samsung device.
Once it is complete, you can restart the device. If you would like TWRP back after flashing, just follow the steps from my first post and use odin to flash the twrp file again. I recommend that after installing lineage os, flash twrp again, as twrp recovery is much better than lineage recovery, and you dont need lineage recovery after installing lineage os.

If I helped you out, please mark my post as the solution, Thanks!

PhotonIce said:
If I helped you out, please mark my post as the solution, Thanks!
Click to expand...
Click to collapse
I did exactly with all your instructions. The end result is still the same that it won't boot TWRP after flashing, I don't really understand what the heck is wrong with my Samsung Note 3 Hlte. However i did try again with Lineageos Recovery, heck same thing too! This is really frustracting man, it just restarted itself and goes into normal boot.

LeEpic69 said:
I did exactly with all your instructions. The end result is still the same that it won't boot TWRP after flashing, I don't really understand what the heck is wrong with my Samsung Note 3 Hlte. However i did try again with Lineageos Recovery, heck same thing too! This is really frustracting man, it just restarted itself and goes into normal boot.
Click to expand...
Click to collapse
Did you follow my instructions from the beginning, using the files I linked, instead of your own?
How did you even try lineage recovery if you can't boot into TWRP? You need to boot into TWRP to flash lineage recovery..
HECK, how did you even flash lineage os if you can't boot into twrp???
Please answer these questions, as it is literally impossbile to do what your doing without entering twrp.
Just follow my instructions step by step, using only the files I linked, then tell us what happens.
I think your problem is that you aren't even entering recovery mode. You need to keep Power+Home+Volume Up pressed, then once the samsung logo appears, wait for 2 seconds and let go of power, without letting go of home or volume up. Now keep home and volume up pressed, eventually you will boot into twrp.
If you can't get into twrp, it means that you didn't flash it correctly, in which case make sure that your bootloader is unlocked.
It is also possible that your devices buttons or broken or something, in that case, download platform tools from here:
https://magiskupdate.com/wp-content/uploads/2021/12/platform-tools_r31.0.3-windows.zip/
Next, download and install adb and fastboot drivers from here:
Download in progress... - My USB Drivers
Preparing your download... Please wait...! Facing issues downloading the file or the download link is broken? You can report us here.
myusbdrivers.com
Install the drivers, then reboot. After that, extract platform tools and open the folder. Note the location of the folder (e.g. C:\Users\Name\Downloads\platform-tools). Now open a command prompt window (cmd), then type:
cd location of platform tools folder here
e.g.
cd C:\Users\Name\Downloads\platform-tools
Now, boot your phone into download mode (power+home+vol down), then connect it to the pc. Type:
adb reboot recovery
and
fastboot reboot recovery
This will force your device to boot into recovery, if your device still doesn't boot into twrp, then you have incorrectly flashed twrp to your device. If that's the case, please carefully follow my instructions from the first post, using my linked files only.

PhotonIce said:
Did you follow my instructions from the beginning, using the files I linked, instead of your own?
How did you even try lineage recovery if you can't boot into TWRP? You need to boot into TWRP to flash lineage recovery..
HECK, how did you even flash lineage os if you can't boot into twrp???
Please answer these questions, as it is literally impossbile to do what your doing without entering twrp.
Just follow my instructions step by step, using only the files I linked, then tell us what happens.
I think your problem is that you aren't even entering recovery mode. You need to keep Power+Home+Volume Up pressed, then once the samsung logo appears, wait for 2 seconds and let go of power, without letting go of home or volume up. Now keep home and volume up pressed, eventually you will boot into twrp.
If you can't get into twrp, it means that you didn't flash it correctly, in which case make sure that your bootloader is unlocked.
It is also possible that your devices buttons or broken or something, in that case, download platform tools from here:
https://magiskupdate.com/wp-content/uploads/2021/12/platform-tools_r31.0.3-windows.zip/
Next, download and install adb and fastboot drivers from here:
Download in progress... - My USB Drivers
Preparing your download... Please wait...! Facing issues downloading the file or the download link is broken? You can report us here.
myusbdrivers.com
Install the drivers, then reboot. After that, extract platform tools and open the folder. Note the location of the folder (e.g. C:\Users\Name\Downloads\platform-tools). Now open a command prompt window (cmd), then type:
cd location of platform tools folder here
e.g.
cd C:\Users\Name\Downloads\platform-tools
Now, boot your phone into download mode (power+home+vol down), then connect it to the pc. Type:
adb reboot recovery
and
fastboot reboot recovery
This will force your device to boot into recovery, if your device still doesn't boot into twrp, then you have incorrectly flashed twrp to your device. If that's the case, please carefully follow my instructions from the first post, using my linked files only.
Click to expand...
Click to collapse
I did follow your instructions using your own files that you provided for me. I did press Power + Home + volume up exactly as you told me to and let go of power button and keep pressing Volume up and Home, It just won't boot correctly into Twrp and restarted itself. There is alternative than using TWRP which is Lineageos Recovery os, i flashed that on my Samsung Note 3 HLTE, but it also don't work as well. However the link you sent to me right now is broken. Mind sending new one?

i forgot to mention one thing, i already unlocked the bootloader on Devs setting by turning on USB Debugging. There is no saying about bootloader option. I'm 100% sure i am doing it correctly. I downloaded literally everything from you and did as the instruction told. Even when i keep pressing Home + Volume up, it goes into bootloop without any successful attempt into booting twrp correctly and once i let go of Home + volume up button will boot my Samsung note 3 hlte into Normal boot and work as normal.

there should be an oem unlocking option in developer options. you need to select that, then reboot into downlaod mode and confirm to unlock your bootloader. To check it if it is unlocked, boot into download mode and send a picture of the text which it shows at the top right here on this forum and ill be able to confirm it for you.

N9005 does not have a locked bootloader .
Check its actually a N9005

PhotonIce said:
there should be an oem unlocking option in developer options. you need to select that, then reboot into downlaod mode and confirm to unlock your bootloader. To check it if it is unlocked, boot into download mode and send a picture of the text which it shows at the top right here on this forum and ill be able to confirm it for you.
Click to expand...
Click to collapse
You can see the video for the devs option, there is only usb debugging, i turn it off so that you can notice it and turn it back on in the video. You can try look at the download mode picture too. Let me know if i am doing anything wrong. Anyways the SDK Platform tool link you sent me is broken bro, i haven't try that solution yet.

JJEgan said:
N9005 does not have a locked bootloader .
Check its actually a N9005
Click to expand...
Click to collapse
It is N9005 my bro, I checked the spec with CPUZ and also reFlashed with Stock ROM N9005 with same Country region just for sure and it works fine. After i flash the stock rom, it can boot into recovery mode with no issues. However, with TWRP... It just won't work... I don't know why...

Will an older TWRP 2.8.70 etc flash , it could then upgrade TWRP .

JJEgan said:
Will an older TWRP 2.8.70 etc flash , it could then upgrade TWRP .
Click to expand...
Click to collapse
I'll try flashing Old twrp version and soon update about it.

Okay. it seem to be work out. But i realised that my Samsung note 3 hlte lcd screen is not original... So is this the reason why i can't flash custom rom? Or is there any alternative that may help me flash any good custom rom other than stock?

LeEpic69 said:
Okay. it seem to be work out. But i realised that my Samsung note 3 hlte lcd screen is not original... So is this the reason why i can't flash custom rom? Or is there any alternative that may help me flash any good custom rom other than stock?
Click to expand...
Click to collapse
Changed parts doesnt affect the installation of a custom rom. What issue are you encountering, you said that it worked out..? Just use twrp to wipe system+data+cache+dalvik, then flash acustom rom which is compatible with the hlte

PhotonIce said:
Changed parts doesnt affect the installation of a custom rom. What issue are you encountering, you said that it worked out..? Just use twrp to wipe system+data+cache+dalvik, then flash acustom rom which is compatible with the hlte
Click to expand...
Click to collapse
Twrp 2.8.70 is too old to read modern custom rom, it seem that i can't flash Lineageos 18.1 at all. That's what i mean, although Android 7.1 Lineageos seem to work out on my samsung note 3 hlte

flash 2.8.70, then install a 3.3x image via twrp's "install image" option in the install menu

[HOWTO]/[ROM] [UNOFFCIAL] How to Flash Lineage OS 19.0

Here is a quick how-to guide to flash LineageOS 19.0 to the A51
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number1.2. Enable USB debugging in Developer Options1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...1.4 After triggering OEM unlock option shutdown your phone.1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.When flashing is complete hold Vol - and Power until reboot.Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.
3. Actual Flashing:
3.1. Necessary Files:Make sure to load all files necessary to your SD before flashing:ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)As for the LOS Image I used this file here, which already includes gapps:lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.imgIf you don't want gapps pick an image that says "BvS" instead of "bgs"3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache3.3.2. flash disable_dm_verity3.3.3. flash multidisabler3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)3.3.5. reboot recovery3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg3.3.7. Wipe data3.3.8. Reboot
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.

Reserved 1

Reserved 2

Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"

exault said:
Lineage 19 flash worked but after flashing my TWRP recovery bootloops (flashing twrp logo).
TWRP that loops is twrp-a51-3.5.0_10-1_ianmacd.
Do you have a working TWRP for this version of Lineage ?
Tried TWRP v3.6.1 A51 tree but it doesn't work and boots into download mode with "DT Entry not found / DT Load Failed / VB Meta sign errors"
Click to expand...
Click to collapse
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers

DerTopher said:
I added a download link to the TWRP img I used to my initial post. Let me know if it works.
cheers
Click to expand...
Click to collapse
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.

ALL sensors ok ?
Fingerprint ok ? In this ROM

exault said:
Nope TWRP does not work. When using the one you linked (as all other 3.6.1 ones) it just jumps back to download mode with DT Entry not found & VBMeta not signed errors.
Click to expand...
Click to collapse
Sorry to hear mate. Unfortunately I cannot hell you solve this issue. There is a telegram channel for custom roms on the A51 with many motivated people. One of them might have the answer you need!
See: https://t.me/samsunga51
If you find it, please post it, so others can profit from it. With your agreement I would also like to add info about the solution - should you find it - to my initial post.
hacker812c said:
ALL sensors ok ?
Fingerprint ok ? In this ROM
Click to expand...
Click to collapse
Don't know about fingerprint as I do not want to provide biometric data to my phone. Maybe someone else using the ROM can answer this; Or you, if you decide to flash it post your results.
Apart from that I have not had any problems with the ROM apart from the following:
-The resulotion of the native lineage camera app is not satisfactory. When I find an app that works better, I'll let you know.
- Restarting the phone after empty battery requires a soft reset sometimes (power+vol -)
-> A solution to this problem might be given in this post. Will try it later.

Thank you, @DerTopher , but unfortunately the link to your LOS file does not work any more. How do I get the file now?

THIS GUIDE ONLY WORKS ON ANDROID 12!!!
sunnyy15 said:
I have concluded all my experiments, and now I can confirm that the "twrp-a51-3.5.0_10-1_ianmacd.tar" on this website only works for Android 10 as instructed by Admin. This does not for Android 11. For Android 11 you have to flash a different file called "Twrp+vbmeta_A11.tar". Details are given in the following link: https://forum.xda-developers.com/t/...-sm-a515f-one-ui-3-0-dub1-android-11.4231543/
Click to expand...
Click to collapse
@DerTopher , please change your OP to specify that this guide ONLY works for Android 12. I just bootlooped my device when trying this on Android 10 stock firmware
See this excelent post for more info: https://forum.xda-developers.com/t/...-ui-2-5-ctj1-android-10.4213443/post-84750027

Anyone knows how to remove the native SU, so that magisk doesn't complain about "abnormal state" su file ?

when i flash something in twrp i have an error failed to mount '/odm4 no such file or directory Can some help me please i am stuck here

DerTopher said:
Here is a quick how-to guide to flash LineageOS 19.0 to the A51
Disclaimer: I am not the maintainer of any of the files I link to here. I just wanted to share my experience to make the process of Flashing los19 to the a51 easier for others.
Prerequisites:
1. Unlocked Bootloader
This step is crucial. You need to unlock the bootloader of the A51 before trying any of this. If not, you are likely to brick your device.1.1. Unlock developer mode by standard procedure: Settings > Info > Tab 7 times on build number1.2. Enable USB debugging in Developer Options1.3. Enable OEM unlocking in Developer Options -> To see OEM unlock option I needed to connect to my WIFI, then set the phone date manually to March 7th 2019. Only then the OEM unlock option became visible in Developer Options. Yes, this is super dumb and inconvenient...1.4 After triggering OEM unlock option shutdown your phone.1.5 Enter Download mode by: Pressing Volume+ and Volume - while at the same time plugging in the USB cable that is already in your PC.1.6. To finally unlock bootloader, you will see a green screen on which you need to press Vol + for some time. THIS WILL VOID YOUR WARRANTY. It will also erase all data on your phone!1.7 After reboot repeat steps 1.1. - 1.5. again. This time you can actually enter download mode by pressing Vol + shortly on the green screen.
2. Flash Twrp
You can now flash TWRP via Odin. The TWRP img I used is here: https://www.mediafire.com/file/0h14t0263oujhna/TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar/file. I flashed it as AP. Make sure to uncheck Auto reboot before flashing.When flashing is complete hold Vol - and Power until reboot.Immediately when rebooting hold Vol + and Power until Samsung logo appears, then let Power go but hold Vol + to enter TWRP.
3. Actual Flashing:
3.1. Necessary Files:Make sure to load all files necessary to your SD before flashing:ChonDoe_Flasher, Disable_Dm_Verity, Multidisabler, LOS-Imagefile, Magisk(optional)As for the LOS Image I used this file here, which already includes gapps:lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.imgIf you don't want gapps pick an image that says "BvS" instead of "bgs"3.2. You need to move your LOS-Image to the same folder as ChonDoe_Flasher and rename the file to "system.img"
3.3 Flashing Sequence:
In TWRP Follow this sequence:
3.3.1. Wipe data, dalvik, cache3.3.2. flash disable_dm_verity3.3.3. flash multidisabler3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)3.3.5. reboot recovery3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg3.3.7. Wipe data3.3.8. Reboot
That should be it. First startup takes some time, your phone should boot to LOS 19.
4. Anger Management
If you softbrick your device you can try to go back to stock rom by accessing download mode and flashing it via Odin. Will take some fiddling around with the button combinations.
If you hardbrick your device don't hold me responsible and good luck to you!
Thanks to
Kyau Sana, Vadim Kupriyanov, Knoyan GTR-X and Sara Lins and other, from the telegram-group, who helped me figure out the process.
Click to expand...
Click to collapse
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS

dmudo said:
Hello friends, how are you? Could someone post the ROM link again, the link is broken.
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS
Click to expand...
Click to collapse
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net

i have a question
in step 3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg
i try to flash chondoe and i tried to add de system.img, and it prompt me to what partition
This are the partitions that apears to me
- Boot
- DTBO Image
- Optics Image
- Prism Image
- Recovery
- Param
- VBmeta Samsung
- VBMeta Samsung
- Super (system vendor product odm)
Does anyone know where ?

Database Users

welcome