Database Users

[HOW-TO][EXYNOS/SNAPDRAGON] Root S20 series and upgrade firmware

Applicable Models:
All Exynos models including but not limited to:
SM-G980F or SM-G980F/DS (S20)
SM-G981B or SM-G981B/DS (S20)
SM-G985F or SM-G985F/DS (S20+)
SM-G986B or SM-G986B/DS (S20+)
SM-G988B or SM-G988B/DS (S20 Ultra)
All BL-unlockable Snapdragon models including but not limited to:
SM-G9810 (S20, Hong Kong, Taiwan, China mainland)
SM-G9860 (S20+, Hong Kong, Taiwan, China mainland)
SM-G9880 (S20 Ultra, Hong Kong, Taiwan, China mainland)
SM-G981N (S20, Korea)
SM-G986N (S20+, Korea)
SM-G988N (S20 Ultra, Korea)
Japanese model (SC-*) also use Snapdragon but I can't not confirm that its bootloader is unlockable.
It is known that bootloader can NOT be unlocked on U.S. models (U/U1) .
Frequently used key combinations of S20 series:
FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button.
DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. Release the buttons after you see the "Warning" screen and then press "Volume Up"
RECOVERY MODE: With the phone off, hold "Volume Up" and "Bixby/Power" button.
Some facts:
1. S20 series uses dynamic partition which means there is only one "super" partition (instead of "system", "vendor", "product").
3. S20 series uses A-only partition which means there is only one set of system partition.
3. S20 series uses 2 stage init (2SI).
4. KNOX will be tripped after you flash a custom image. As a result, Samsung Pay and Secure Folder will become permanently (even after restore to stock firmware) unusable and your warranty may be voided. However, many jurisdictions including the European Union has law mandating manufacturer to provide hardware warranty even if user modifies the software.
5. Samsung devices are almost impossible to hard brick (render the device unusable without a hardware-level repair) as critical sections including the bootloader are well-protected. However, if you do things incorrectly, you may soft brick your phone, but that can usually be resolved by resetting to factory settings (wipe data and cache) or restoring to stock firmware (check out Stage 4).
Tools needed:
On your computer:
1. Odin 3.14.4 or newer
2. Samsung Android USB driver
3. SamFirm or other tools/websites to download official firmwares
4. Android Verified Boot Metadata Image with verification disabled (vbmeta_disabled.tar)
On your device:
1. Magisk Manager
Stage 1: Know your model and carrier code (CSC)
1. Open "Settings"
2. Go to "About phone" -> "Software information"
3. Pay attention to "Service provider SW ver."
4. Starting with "SM-", for example "SM-G9810", that's the model of your phone.
5. Immediately after that, there are two 3-letter code, for example "OZL_CHC". The second 3-letter code "CHC" is your CSC.
6. Remember your model and CSC.
{
"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"
}
Stage 2: Unlock the bootloader
WARNING: ALL data on your device, including apps, settings and files in internal storage, will be lost. You do not need to repeat this if you didn't re-lock your bootloader.
1. Open "Settings"
2. Turn on "Developer mode" by going to "About phone" -> "Software information" and pressing "Build number" for several times.
3. Go to main menu of "Settings" and at the bottom you will find "Developer options"
4. Go to "Developer options". You will find a toggle "OEM unlocking". Turn it on.
5. Skip to step 8 if your device reboots to "Unlock bootloader?" screen. Make sure the toggle is on and then turn off your phone.
6. With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via a cable. (don't use charging only cables)
7. Release the buttons after you see the "Warning" screen. Then, hold the "Volume Up" button.
8. You will see "Unlock bootloader?" screen. Proceed and unlock your bootloader by pressing "Volume Up" button.
9. Your device will be reset to factory settings. Proceed with the Setup Wizard. Only connect to network via Wi-Fi or cellular and skip everything else. (to save time as data will be cleared again later.)
10. Repeat step 1-4 to validate that "OEM Unlocking" is on. If it is not, turn it on.
11. Repeat step 6.
12. Release the buttons after you see the "Warning" screen. This time, press (not hold) the "Volume Up" button.
13. You will see "Downloading" screen. On the top left, there are some important info.
14. Pay attention to "OEM LOCK" and "REACTIVATION LOCK". If both of them are "OFF", you have unlocked the bootloader.
Stage 3: Disable Android Verified Boot
1. Reboot to DOWNLOAD mode. If you are already in the download mode, skip to step 2.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power/Bixby" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
View attachment 4990053
With bootloader unlocked and AVB disabled, it is now possible to boot modified images on the device.
If a recovery is available and you don't want to go through the process of downloading official firmware, go to #2.
You can also download a KERNEL TAR archive of your version here:
Exynos: https://github.com/jesec/proprietary_vendor_samsung_xyzs/releases
Snapdragon: https://github.com/jesec/proprietary_vendor_samsung_xyzq/releases
and then skip to Step 6.
Stage 4: Obtain the official firmware and upgrade
1. Open SamFirm
2. Type in your model and your region (CSC) and click "Check Update"
3. "Download" and you will get a zip file.
View attachment 4990061
4. Extract it and you will get 5 files (AP, BL, CP, CSC and HOME_CSC). All files are in tar format and can be opened by 7-Zip, WinRAR or other software.
5. Check the version code, for example (G9810ZCU1ATD1). The last 4 letters (ATD1) indicates the version of the firmware. If the version is the same as your current firmware, skip to Stage 5.
Your data will be preserved if you do it right but it is good to have a backup.
6. Open Odin on your computer and reboot your device to DOWNLOAD mode.
7. Put AP, BL, CP files in their Odin slots. It takes time to verify the firmware so be patient.
8. Put HOME_CSC file in CSC slot. Be careful here. Unlike AP, BL, CP slots, you should NOT use CSC file for CSC slot. Instead, you should use HOME_CSC file. CSC file contains partition table (PIT) which will erase all your data.
9. Put vbmeta_disabled file in USERDATA slot so AVB remains disabled and your data preserved.
10. Click "Start" and wait for it to finish. Allow the device to boot into system to complete the upgrade process. Do NOT interrupt/disconnect phones/hold button. It needs to complete the process without interruption or strange BUGs may appear.
View attachment 4990063
Stage 5: Extract boot (kernel) image from firmware
If you are having trouble creating tar file, you can skip to Stage 6. (NOT RECOMMENDED as AP is basically full system image. It is huge (takes long time to flash/process) and Magisk may misbehave.)
1. Extract boot.img.lz4 from the AP file.
2. Use 7-Zip to create a tar archive which contains boot.img.lz4 only. (or "tar cvf boot.tar boot.img.lz4")
View attachment 4990065View attachment 4990067View attachment 4990069View attachment 4990071
Stage 6: Patch the boot (Kernel) image via Magisk
1. Transfer the tar archive (or the AP file if you skipped stage 5) to your phone.
2. Open Magisk Manager.
3. Click top-right "Install" button
4. Make sure "Recovery Mode" is off in Options.
5. Click "Next" and select "Select and Patch a File" in Method.
6. Select the file you transferred to your phone in step 1.
7. Click "Next" and "LET'S GO".
8. Transfer the patched file (in Download/magisk_patched.tar) to your computer
9. Reboot the device to DOWNLOAD mode.
10. Open Odin, put patched file to AP slot and then click "Start".
11. After reboot, Magisk is installed and you will have the root access.
HOW TO upgrade the firmware
Repeat stage 4-6.
XDA:DevDB Information
Root S20 series and upgrade firmware, Tool/Utility for the Samsung Galaxy S20
Contributors
jesec
Version Information
Status: Stable
Created 2020-04-08
Last Updated 2020-04-08

Other Methods:
You still need to unlock bootloader and disable AVB. (check Stage 2-3)
Recovery Magisk installation:
1. Open Odin on your computer.
2. Reboot your device to DOWNLOAD mode.
3. Put the recovery TAR flashable into AP slot.
4. Click start.
5. Use Volume Up + Power to reboot into recovery mode.
6. Install Magisk via recovery.
My recovery usually includes Magisk in "Select from root" -> ".builtin" folder. Or you can sideload the ZIP flashable of your choice via adb or https://flash.jesec.io/.
Flash pre-patched boot (Kernel) image:
Basically others have done stage 4-6 for you. Be aware that it is always safer to DIY.
You are welcomed to share your patched image to the community by replying to this thread.
Naming convention: model + firmware version (last four letters of build number) + magisk version .tar
1. Make sure that the model and firmware version of the pre-patched image is the exact SAME as yours.
2. Open Odin on your computer.
3. Reboot your device to DOWNLOAD mode.
4. Put pre-patched image into AP slot.
5. "Start"
SM-G9810_ATD1_ef9d077c.tar:
https://drive.google.com/open?id=1SxKXWHqR0aM_g457Yp7pk524_6aqp1k5

Some Interesting Things:
Change your CSC (carrier code):
You have to root your device. There might be some secret codes to trigger the menu without root, though.
Note that you can only change it to carrier configurations already included in your firmware.
WARNING: Your device will be reset to factory settings.
In a local terminal, type:
su
am start -n com.samsung.android.cidmanager/.preconfig.PreconfigActivity

Cheers jesse seems like years since we were on s9 forums nice friendly guide you made here

What is the purpose of disabling android verify boot?

ngoralph said:
What is the purpose of disabling android verify boot?
Click to expand...
Click to collapse
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
ngoralph said:
Am rooted without doing this step will it cause any problems?
Click to expand...
Click to collapse
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
Am rooted without doing this step will it cause any problems?

Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar

bigback said:
Stage 6: Patch the boot (Kernel) image via Magisk
can't Patch the boot (Kernel) image via Magisk
! Unable to repack boot image!
! Installation failed
---update
use 7-zip to creat tar
Click to expand...
Click to collapse
you can extrsct boot and re tar it all in mixplorer then just upload to pc and flash in odin

jesec said:
Android Verified Boot prevents images which are not signed by Samsung to boot on the device. Obviously we don’t have Samsung’s private key and we need to modify images to obtain root access. So it has to be disabled.
Click to expand...
Click to collapse
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.

chieco said:
I'm rooted for weeks now without this... can you explain more in detail what this is for? Why is it advised from you to do this step? maybe in form of examples? like I said rooted without doing this and had no issues so far.
Click to expand...
Click to collapse
Backread he already answered it on my inquiry

ngoralph said:
Backread he already answered it on my inquiry
Click to expand...
Click to collapse
I qouted his answer to your question asking for more details.

Magisk Root on Snapdragon based SM-G9860 S20+?
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.

chieco said:
I qouted his answer to your question asking for more details.
Click to expand...
Click to collapse
jesec said:
You must have done it somewhere in the process. Magisk will patch vbmeta.img for you if you give it a tar archive.
Click to expand...
Click to collapse
AloxeCorton said:
First of all, thanks for putting this guide together - very useful. I did want to share my experience following these instructions.
Everything went well until Stage 6 where I installed the Magisk patched AP file. The AP file was successfully patched with the latest canary Magisk and it also installed properly in Odin (did the full AP file and not the boot image since that encountered errors while trying to repack for some reason).
The problem is that when I reboot, No Magisk installed and No root...
I tried a factory reset just to confirm but same outcome. I did use the same AP file that was used to flash the phone as well.
Anyone successfully root and install Magisk on the Snapdragon based SM-G9860 S20+ (with latest Hong Kong firmware)? I suspect it has something to do with the Magisk not being able to handle the unlocked snapdragon based phones yet (it was like that for the Galaxy 10+ last year - took an extra month to come up with a Magisk branch that was able to handle the phone). I'm also following this thread for Snapdragons based S20 but it doesn't seem to have too many details yet
Cheers
A.A.
Click to expand...
Click to collapse
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.

So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
As it finishes flashing firmware hold volume buttons as it reboots. Then flash patched boot.img and reboot. Worked for me going from ATCH to ATCT today.

jesec said:
My Snapdragon S20 has been rooted with Magisk. I think probably it has problem patching the full AP file. In that case, I recommend you to research how to pack a tar file. I don't recommend you to patch the full AP as it is huge.
Also be aware that all patched file is located in /sdcard/Download and named magisk_patched.*. It is NOT in-place patch. You might accidentally use the unpatched file.
Click to expand...
Click to collapse
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
I had the same issue... I used a tool (lz4_win64_v1_9_2) to uncompress lz4 format... I kept it just as boot.img and packed in boot.tar file and it worked.
Just for info, 7-zip built wrong tar file (don't ask me why...)... I had to use cygwin for it (or a linux if you have)

Orphee said:
So I tried to apply this tutorial to update my phone SM-G981F
And it can't boot. it finish in failsave recovery :
"Can't load ndroid system. your data may be corrupted..... please perform a factory reset...."
I really would like to avoid it... I flashed vbmeta_disabled.tar but no GO...
I was already rooted with Magisk patch on ATCH rom...
Edit : wiped...
Click to expand...
Click to collapse
That's expected.
From Android 10, encryption keys are tied to AVB key (stored in vbmeta). By disabling AVB, you changed the AVB key from Samsung's to none. Though, if I remember correctly, some old versions have security loophole that allows you to boot a patched kernel even if AVB key is intact (recovery is still protected however). That's actually a serious breach of this additional integrity assurance. (your sensitive data is still safe nonetheless as there is a customer key tied to your password/pattern/etc)
Read more: https://source.android.com/security/keystore/version-binding
AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
That should not happen. Here is a screenshot if things are done right:
Make sure you pack the TAR right (see OP for a screenshot of boot.img.lz4.tar) and the file you transfer to your device is the TAR file (boot.img.lz4.tar if you don't change the file name).
Plus, maybe check if Magisk version is right. Make sure you use the Canary builds.

AloxeCorton said:
Thanks for the help. I did try patching the TARed (using 7zip) boot.img.lz4 file but for some reason it just refuses to "repack" from within Magisk (see screen capture attached)- I'm not sure if anyone experienced this or if I'm overlooking something.
Also tried to reformat everything with the Chinese firmware instead of HK (it was a little more recent) but I got the same results. Oddly the full AP file seems to patch fine in Magisk but never produces the expected results (no Magisk installed, no root).
A.A.
Click to expand...
Click to collapse
do it on fone thats what i did mixplorer will tar it for you then move to pc and flash

[GUIDE] How to root, install TWRP, ROMs and mods on a G3s/G3 beat d722 in 2020?

*After I wrote this whole thing as a DM i figured it might be helpful for a couple of people that are struggeling to root and install a custom recovery on their d722.*
Before we start you will need a PC with internet connection and a USB cable.
If you get stuck or need something about the device you can find it here. It's an XDA thread about the d722, it's mods, roms... : https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
First you will need to flash your phone back to 4.4 kitkat firmware to ensure maximum compatibility (this is the only way my device would root) ( find it here: https://lg-firmwares.com/ (type in your model and download a 4.4 firmware closet to your region, language...)). We will do that with the lg flash tool (find it here: https://lgflash.com/download/) + also install lg drivers if you don't have them already (https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560).
1. First enable developer options in phone settings by tapping the build number 7 times. Go to the developer options and there tick usb debugging. Than you want to turn you device off. Hold volume up and plug it into you computer. You will get into download mode. On your PC extract and open the lg flash tool. There you will chose your kdz firmware file you downloaded previously and click normal fash. Choose other instead of korean and your preferred language. When you flash it the tool might report an error but just ignore it and wait for the phone to reach 100% download. It will reboot itself when finished. After that you can close the flash tool and continue to the next step.
2. Now you will root your phone. You will do that with lg one click root (found here: https://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951). Download the latest GUI version, install it onto your PC and open it. When your redy plug your phone into the computer (turned on no apps open) and click start. Wait for it to be done. It's normal for it to restart a few times.
3. Now we will instal the custom recovery to be able to flash ROMs. To do that you will need to dowbload this zip file from here and extract it with 7zip (https://forum.xda-developers.com/showpost.php?p=61220755&postcount=100) and install ADB (remeber install folder) (from here: https://forum.xda-developers.com/showthread.php?t=2588979). Paste aboot file into /sdcard folder (or folder of choice with adjusted path in command) ob your phone uding file manager. Than open CMD and type in
cd *path of your folder*
adb shell
su
dd if=/sdcard/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
If you get an error that says there is no aboot file or something similar than you nees to change this command : dd if= *your phones path*/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot For me it was : dd if=/external_SD/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4. This should have installed a basic version of TWRP on your phone ane booted into twrp recovery but we will be updating it.
To get into recovery from off state hold volume down + power button until you see the LG logo. Relese both for a split second and hold both down again (volume down + power) until you see an option to factory reset (wont actualy reset anything if you did all steps correctly). Click yes and yes again by using volume and power buttons and you will be booted to TWRP.
Alternative is to go to playstore and download root app that boots you to recovery if you do it often.
This version is quite old and not capable of flashing newer ROMs so we will be flashing an updated version (download it here: https://vasy.ru/TWRP/jagnm/ and rename it to .img if it isnt named like that alredy). Easiest way is to download it to your PC and transfer it via USB if your PC detects the phone while in TWRP. If not boot it up transfer the files and boot back to recovery. Now just flash the .img file and reboot.
5. At this point you have root privilages (super SU) and a custom recovery. Now all theres left to do is to flash ROMs and mods.
You boot to TWRP recovery, connect your phone to the PC and transfer the .zip files you want to flash. Tha you click flash in twrp chose your ROM files and click add more, your GAPPS click add more and the mod (if you want to try it of course). Than you flash them, wair for it to finish and click reboot.
If it takes longer than 15 min+ than you probaboy have a bootloop. To fix it take out the battery put it back in and boot into recovery (volume down + power until LG logo pops up, release for half a second hold again, yes and yes). Try factory reseting (type yes). And than just flash the ROM and boot. If it boots go back to recovery and flash GAPPS and mod and it should normaly boot into android.
If nothing fixes your issue you can alway use the firmware and lgflashtool to go back to default unrooted kitkat or lolipop.
My recomendations:
I personaly use this liniage (14.1) 7.1 ROM as it's still getting updates (I also tried 8.1 but it's buggy, laggy and gapps don't work):
https://forum.xda-developers.com/lg-g3/development/cyanogenmod-14-1-lg-g3s-t3508224
And of course you want google apps to go along with it:
https://opengapps.org/ (pick ARM, android version of ROM (7.1 in this case) and how many preinstalled apps (I use nano))
I also have this mod installed which makes colours of your display a bit better:
http://www.mediafire.com/download/6z9yg1d3gooyz37/Sony_Bravia_3.zip
From here you can also get Exposed framework, root apps like LSpeed to speed up your phone even more, greenfy and amplify to improve battery life. Again every mod for this phone along with overclocking and other mods is or was discussed here at one point so dont be afraid to join the conversation in this thread:
https://forum.xda-developers.com/lg-g3/general/lg-g3s-beat-d722-thread-t3110048
And ofcourse google is your friend if you get into any issues. Hope this helps, typed it on my G3s .

Thanks
---------- Post added at 12:28 PM ---------- Previous post was at 11:44 AM ----------
It would be better for our phone to release an android 9 custom, it would be great. Here is the same phone as our processor and video accelerator. Android 9 would work great on our phone https://4pda.ru/forum/index.php?showtopic=633150&view=findpost&p=36961339

Thanks for the guide!
I bought a G3s D722 cheap off ebay to experiment with. I tried to flash four different kitkat roms many times on 2 computers and each time the phone went into boot loop (start tune and logo over and over) so I flashed the first UK Lollipop on the list and all went fine, there are not UK kitkat roms in the link.
The UK kitkat roms must be different is all I can determine anyone know where I can get one?
The preflash OS was V20e-EUR-XX and now its V20d
Any thoughts or suggestions anyone?
Thanks!

I couldn't get this to work so tried the very easy no PC method in the link and it works great!
LG G3/G3s/G3 Beat telekom,orange or any other operator
Hi everyone, I want to show u how to upgade your LG G3s/beat to adroid 7.1.1 lineage OS. It has taken me some time to find and to gather all needed files but i was succesfull :D So I had my lg running on android 5.1 Lollipop but I had problem...
forum.xda-developers.com

[GUIDE] (Exynos) TWRP+Magisk updated guide (June 2021)

Magisk+TWRP for Exynos ONLY
Hi, there are some tutorials out here on the forum but some are outdated, others have dead links and other mix some steps from exynos and snapdragon, so this is a guide on how I did it, My device is the International Exynos LTE Dual sim variant or SM-N985F-DS running android 11 (oneUI 3.1) patch from april 2021 with security patch from may 2021 but this has been tested on many exynos variants.
See DR.Ketan post: https://forum.xda-developers.com/t/guide-how-to-root-n20-ultra-n986b-n9860.4147023/
I based my guide on @dr.ketan 's guide and some bits from the comments and references from that post, so all credit goes to him and the people he reference on his post.
First of all as dr.ketan said:
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
1.- BACK UP ALL OF YOUR DATA, copy your files to a PC, make backups on google and samsung clouds and any other cloud service backup you have (whatsapp for example) becuase in this process all data is wiped TWICE.​
2.- Prepare your PC: ​
I personally recommend using a laptop or a pc with an UPS (backup battery) just to be safe.
2.1 Create a folder fo the files and create 2 folders inside named OLD and NEW (this is merely to keep files organized since they CAN be confused (see next steps), unless said otherwise ALL files and folders go in the OLD folder.
2.2 Download ODIN [CHECK FILES BELOW]
2.3 Download YOUR phone stock firmware (you have several options for this, I personally use sammobile but here you have to google on your own. Remember to extract the contents and you should have 5 files.
NOTE(hehe): to get your exact model name you can check on Settings>About phone>Software information>Baseband version.
2.4 Download Magisk APK and ZIP [CHECK FILES BELOW]
2.5 Download Multidisabler ZIP [CHECK FILES BELOW]
2.6 Download TWRP recovery [CHECK FILES BELOW] and place it in the "NEW" folder you created on step 2.1
IMPORTANT: use only THIS recovery from THIS file, since it's modified for exynos and also to skip a step on the process.
3.- Prepare your Phone:​
3.1 Copy the AP file from your PC (the one from the stock firmware) and the magisk.apk file you downloaded, to your phone.
3.2 Install the magisk app (the apk file)
3.3 Open the magisk app and select the first option, there you will have an option to select a file, select the AP file you copied from your pc an tap continue (or start I dont remember)
3.4 Now you will have a "Masgisk_patched-*********.tar" file on your download folder on your phone, copy that file to your PC and place it in the "NEW" folder you created on step 2.1.
4.- Now we start the process of modifying the phone​
4.1 UNLOCK BOOTLOADER: on your phone go to SETTINGS>ABOUT PHONE>SOFTWARE INFORMATION and tap the "Build Number" repeatedly until you see "You are now a developer" (or something similar)
4.2 Go back to SETTINGS and now you will have at the bottom a new menu called "Developer options", enter and toggle on the OEM unlocking option, this will prompt some warnings and an assistant, follow the instructions and when you finish turn off your phone.
4.3 Press and hold the VOL+ and VOL- buttons at the same time and connect the phone to your PC WHILE HOLDING BOTH BUTTONS, this will prompt DOWNLOAD MODE on your phone and you will see 3 options, Press and hold the VOL+ button to unlock the bootloader, now your phone will reboot and wipe all of your data.
4.4 Confirm OEM Unlock is enabled: after the reboot you will get the initial setup process again (as if the phone were new) skip though all (because it will be wiped again) and repeat the process on step 4.1
Now the OEM unlock setting should be GRAYED OUT and with this your phone is ready to be modified
5.- Flashing custom binaries​
5.1 Turn off the phone and put it into DOWNLOAD MODE again (see step 4.3) but this time use the first option, that is, press the VOL+ button ONCE, this will enter DOWNLOAD mode and put the phone in flashing state.
5.2 Open ODIN on your PC as administrator
5.3 On the Options tab UNTICK the "Auto Reboot" option
5.4 Click on the AP button and locate the "Masgisk_patched-*********.tar" on the "NEW" folder.
5.5 Click Start, wait until you see PASS on the top left corner
5.6 Click on the AP button again and locate the "Exynos no vbmeta recovery.tar" file on the "NEW" folder.
5.7 Click Start, wait until you see PASS on the top left corner.
5.8 THIS STEP IS CRITICAL: disconnect your phone from your PC, now READ AHEAD before doing anything.
Here you will have to do a combination of button presses to boot into recovery. Once your phone is disconnected press and hold VOL- and POWER BUTTON (side key) for approximately 7 seconds, once the phone screen goes black immediately release the VOL- button and press the VOL+ button WHILE KEEP PRESSING THE POWER BUTTON. You will see 1 or 2 warning and a glimpse of the samsung logo, keep pressing the buttons until you see the TWRP (Team Win Recovery) splash screen, at this point you can release the buttons.
5.9 now in the recovery navigate to WIPE tab > FORMAT DATA > and type yes to continue (read instructions on screen). DO NOT RESTART. go back to the starting screen and then navigate to REBOOT > REBOOT TO RECOVERY.
5.10 Your phone will reboot into recovery on its own, no need to press any buttons.
5.11 Once inside the Recovery, connect the phone to your PC, after a few seconds the phone will connect normally as if it were in the OS, now copy this files to your phone from your PC:
Magisk.zip
Multidisabler-samsung-3.1.zip
5.12 Go to INSTALL tab on your phone and select the multidisabler zip and install it (it will prompt you to swipe to install), once finished tap on WIPE CACHE/DATA.
5.13 Now do the same with magisk.zip but this time DO NOT tap the "wipe cache/data" button, instead tap on REBOOT.
6.- First Boot​
NOTE: First boot takes a while but if your phone is not showing the initial setup screen in max 15 minutes something went wrong and you will have to flash back to stock firmware and start over.
6.1 Once you boot do the usual initial setup, here you can do it normally and restore your cloud backups.
6.2 When you are all set up, look for the MAGISK app, open it and follow the instructions. Your phone will reboot so make sure you are all set up BEFORE opening the app.
6.3 ALL DONE!​

Hi there,
Thanks for the updated guide!
Maybe worth mentioning that when done, to get back into TWRP power down phone -> connect USB ->press & hold Power AND VOL- until black screen (7sec) -> Quickly press VOL+ with still holding Power button.
Would you know how to update firmware to latest security patches (downloaded from SamMobile for example) now phone is rooted with Magisk, with TWRP recovery and multidisabled?
Regards,

I followed all directions, and Magisk and TWRP are installed. However, I do not have root access. I have an S10e (SM-G970F, Exynos). To get root access, you have to do the bixby, volume up, and power together. I always get to TWRP. When I had only Magisk installed, I always got stock recovery. How do I get the keys correct?

Also, I understand you must have something in the USB port. I tried mostly connected to the computer, sometimes to a charger, and sometimes not at all. Nothing can get Magisk root access unless it boots me to recovery, and then I can just reboot to system (no root) or recovery (same place, still no root).

Threx71 said:
IMPORTANT: use only THIS recovery from THIS file, since it's modified for exynos and also to skip a step on the process.
Click to expand...
Click to collapse
Where is this TWRP file?

DAVIRO1 said:
Where is this TWRP file?
Click to expand...
Click to collapse
Weird, it was together with all the other files, I'll re-upload it when I get home.

josephgrab said:
Also, I understand you must have something in the USB port. I tried mostly connected to the computer, sometimes to a charger, and sometimes not at all. Nothing can get Magisk root access unless it boots me to recovery, and then I can just reboot to system (no root) or recovery (same place, still no root).
Click to expand...
Click to collapse
Only thing I can think of is you are not flashing the correct magisk zip file on TWRP, try downloading it from magisk's official site. Is the same file for the both procedures, you just have to change the file extension accordingly (.apk or .zip)

Threx71 said:
Weird, it was together with all the other files, I'll re-upload it when I get home.
Click to expand...
Click to collapse
thanks, I have all the files ready to do the flash,

DAVIRO1 said:
thanks, I have all the files ready to do the flash,
Click to expand...
Click to collapse
here you go
Exynos no vbmeta recovery.tar
drive.google.com
EDIT: why the f is xda deleting the file after uploading?

I tried that file. First, I could not flash with odin 2 recovery.img . I used 7-zip to archive it as .tar, and it still would not flash. I do have an SM-G970F, so it is Exynos. I am not sure of the results, but I did flash with newest twrp-3.5.2_9-5-beyond0lte.img.tar .

Threx71 said:
5.6 Click on the AP button again and locate the "Exynos no vbmeta recovery.tar" file on the "NEW" folder.
Click to expand...
Click to collapse
What is this file?

DAVIRO1 said:
What is this file?
Click to expand...
Click to collapse
Here
Exynos no vbmeta recovery.tar
drive.google.com

josephgrab said:
I tried that file. First, I could not flash with odin 2 recovery.img . I used 7-zip to archive it as .tar, and it still would not flash. I do have an SM-G970F, so it is Exynos. I am not sure of the results, but I did flash with newest twrp-3.5.2_9-5-beyond0lte.img.tar .
It was the wrong file, this is the correct one:
Exynos no vbmeta recovery.tar
drive.google.com
Click to expand...
Click to collapse

After flashing that, it would not boot to recovery but just to download.

Thanks! Worked for me! I have a question:
do you know how to Bypass root detection for bank app?

After I flash Exynos no vbmeta recovery.tar this is the error I get
Couldn't find grp7 symbol in main dtb
failed to permorm fixtps in overlay
ufdt overlay apply fail
UFDT DT Overlay FAIL
need kernel: could not find do normal text
vbmeta: Error verifying vbmeta image
vbmeta VERIFICATION_DISABLE bit is set
CUSTOM VBMETA
VBMETA
I cannot read everything it is so small, so there may be some typos

I found out what I did wrong. I am using SM-G970F (S10e), whereas this forum is for SM-N985F.
Great instructions, though.
Thank you. Just wish I could get root. I cannot because of the updated firmware (August 2021).

Hello, thank you for the guide it worked to root my sm-n986b !
Threx71 said:
5.6 Click on the AP button again and locate the "Exynos no vbmeta recovery.tar" file on the "NEW" folder.
5.7 Click Start, wait until you see PASS on the top left corner.
5.8 THIS STEP IS CRITICAL: disconnect your phone from your PC, now READ AHEAD before doing anything.
Here you will have to do a combination of button presses to boot into recovery. Once your phone is disconnected press and hold VOL- and POWER BUTTON (side key) for approximately 7 seconds, once the phone screen goes black immediately release the VOL- button and press the VOL+ button WHILE KEEP PRESSING THE POWER BUTTON. You will see 1 or 2 warning and a glimpse of the samsung logo, keep pressing the buttons until you see the TWRP (Team Win Recovery) splash screen, at this point you can release the buttons.
Click to expand...
Click to collapse
There is just this part that I did differently.
First, to start flashing the twrp at step 5.6 I had to restart the phone in download mode because odin would be stuck at "setup connection" if i tried to flash it just after the file before.
And at step 5.8 I had to keep the phone connected to the PC otherwise it would not boot in recovery menu.
I did all the phone setup and installed "Riru" then "Universal SafetyNet Fix" magisks modules to pass the Safetynet.
I just have one question if someone can tell me if there is a way to not display the bootloader warning message when the phone is booting please.

lilstyle974 said:
I did all the phone setup and installed "Riru" then "Universal SafetyNet Fix" magisks modules to pass the Safetynet.
I just have one question if someone can tell me if there is a way to not display the bootloader warning message when the phone is booting please.
Click to expand...
Click to collapse
I have installed drketanrom and there are a tweak that delete this message.

lilstyle974 said:
Hello, thank you for the guide it worked to root my sm-n986b !
There is just this part that I did differently.
First, to start flashing the twrp at step 5.6 I had to restart the phone in download mode because odin would be stuck at "setup connection" if i tried to flash it just after the file before.
And at step 5.8 I had to keep the phone connected to the PC otherwise it would not boot in recovery menu.
I did all the phone setup and installed "Riru" then "Universal SafetyNet Fix" magisks modules to pass the Safetynet.
I just have one question if someone can tell me if there is a way to not display the bootloader warning message when the phone is booting please.
Click to expand...
Click to collapse
Thanks, I was just about to post this about the safety net since I just did it yesterday to start using google pay.
I'll add it to the Post as EXTRAS along with some other things.
Also sorry to everyone for having this thread so abandoned, I used to get so much spam from XDA that I ended up blocking all emails (?

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 number​1.2. Enable USB debugging in Developer Options​1.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.img​​If 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, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.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 number​1.2. Enable USB debugging in Developer Options​1.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.img​​If 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, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.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 ?

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 number​1.2. Enable USB debugging in Developer Options​1.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.img​​If 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, cache​3.3.2. flash disable_dm_verity​3.3.3. flash multidisabler​3.3.4. Wipe internal storage (Backup might be advisable, if you didn't format data anyways)​3.3.5. reboot recovery​3.3.6. flash chondone with lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img in the same folder renamed to system.mg​3.3.7. Wipe data​3.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
3.3.7 format data or wipe?