Database Users

Easy Guide for How to Root Verizon Galaxy Note 4 (updated links and instructions)

==========================================
| How to Root Verizon 910V Samsung Galaxy Note 4 |
==========================================​
Author: Tripper511
Created: September 2nd, 2016
Last Updated: September 29th, 2017
DISCLAIMER: Please do this at your own risk! I am not responsible for any damage or bricking done to phone. This should NOT trip knox or void your warranty however no promises can be made. Device can always be unrooted by flashing back to stock with Odin3. Please read all the steps first and preferably watch included videos so to be aware of what to expect. Average time to perform this should be under an hour assuming you do not run into any problems.
Don't be overwhelmed by all the steps. I intentionally dumbed down the process to prevent any mistakes. I wrote this as I personally rooted my own device with instructions gathered from my own research as I would come across my own challenges in the rooting process. This guide was made for first timers and experts a-like. Links to all the different guides I used and additional troubleshooting information is at the bottom. I suggest you glance at it before beginning. Thank you to all the people on the internet, in the forums and YouTube who asked questions and posted answers; allowing me to unlock my device. My hope is this guide will help ease the process and shrink the learning curve of anyone who reads it.
*If you have any problems AFTER rooting READ the TROUBLESHOOTING section at the bottom of this guide BEFORE posting any questions*​
===================
| Files Needed for Root |
===================​
*Download the most recent version of DRIVERS and unzip if necessary*​
Link to .zip containing ALL THE FILES below: https://www.mediafire.com/?1hn5hzmvu3v3iqg Updated: 10/27/16
1) KingOroot (KingRoot will also work but KingOroot seems to work better) - [This temporarily roots your phone]
2) Minimal ADB and Fastboot v1.4 - [Allows you to place the n4-fix on your phone]
3) samsung_unlock_n4-fix (place this file in the install directory of "Minimal ADB and Fastboot" (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.)) - [Changes your CID to allow permanent root]
4) SuperSU v2.76 (or newer) - [This allows for apps to have root access]
5) TWRP 3.0.2 (or newer) - [Allows you to flash roms and make changes to in boot after successful root]
6) Kies - [Allows PC to communicate with phone]
7) SAMSUNG_USB_Driver_for_Mobile_Phones - [Allows PC to connect with phone]
8) Odin3 v3.12.3 (or newer) - [Needed to flash firmware to phone from PC]
9) systemonlyN910V-5.1.1.tar (Link is at the end of the guide) - [5.1.1 firmware without bootloader so you can keep TWRP recovery]
10) oscar_kernel_v0.2 - [Phone OS for 5.1.1 that lets the software communicate with the hardware]
**If you are coming from another firmware and have to change to 5.1.1 firmware than you will also need:**​
11) N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar.md5 (aka 5.1.1 firmware for North American Verizon Samsung Galaxy Note 4. Link is at the end of this guide) - [This is the 5.1.1 Lollypop firmware]
========
| PHASE 1 |
========​
- Prepping the Phone -​
========================================
| Things to do ON PHONE BEFORE using KingOroot |
========================================​
!!DO NOT OVERLOOK THIS SECTION!! A lot of people have problems because they don't first check/read these 10 prep steps!​
1) BACK UP ALL FILES ON SD CARD TO PC!
Make sure you DO NOT REMOVE YOUR SIM CARD throughout this entire process!
Connect your device to your computer
Make sure the Note 4 is set for media transfer the option will be in the drop down from the top of the phone once USB is connected.
Copy over files from SD card (and phone if you want) to a folder on your PC just like you would with any USB stick.
2) FORMAT SD CARD. *AFTER* backing up the card you will have to format the card through the phone in the settings under: storage > SD Card > Format SD CARD
3) !!MAKE SURE YOU ARE RUNNING ANDROID VERSION 5.1.1.!! If you are not check the forum and video instructions in the links below to change firmware.
4) Download NEWEST VERSIONS of all files from this guide. Best way to do this is do a google search for the file followed by "XDA". i.e. "KingRoot xda". This will bring you to the xda forum to make sure you get authentic, verified and current versions of the files.
5) Make sure to download "eMMc Brick checker" from play store. Run it and make sure the phone CID starts with a "15". If it doesn't STOP HERE! You CANNOT root your phone!
6) Download "Root Checker" to confirm if root was successful after running KingOroot/KingRoot/etc.
7) Make sure "Developer Options" is open and USB debugging is enabled. You can turn it on by going to: Settings > About Phone > then tap on "Build Number" ten (10) times to unlock the option.
8) Also make sure "Reactivation Lock" in UNCHECKED. Go to Settings > (under "Personal") Security > (and under "Find My Mobile") uncheck "Reactivation Lock"
9) Additionally in: Settings > (under "Personal") Security, make sure "unknown sources" is checked.
10) Finally open and run Keis and SAMSUNG_USB_Driver_for_Mobile_Phones to ensure the PC can communicate with the phone (this should also be done BEFORE running Odin3 if you need to change your firmware to 5.1.1).
=========
| PHASE 2 |
=========​
- Rooting the Phone -​
1) Make sure you have at least 80% battery life
2) Run KingOroot (KingRoot works too but the other one seems to be better)
3) After program is finished run Root Checker to confirm root. (If you are using the PC version of KingOroot disconnect the phone from PC FIRST, THEN run Root Checker and proceed to step 4)
4) Connect phone to PC .
5) Place the file "samsung_unlock_n4_fix" in the same folder "Minimal ADB and Fastboot" is installed (make sure the program is installed first)
*Before proceeding to step 6 it is suggested you copy ALL of step 6 into a notepad. You will need to copy and paste these line into the command prompt because if you take too long to input the script then the phone will reset before you're finished causing you to have to redo steps 2 - 4.*​
6) Run "Minimal ADB and Fastboot" and type in (or preferably copy and paste) these lines one by one, pressing "enter" after each line (if after typing the first line and it says "List of devices attached 123a12ab offline" refer to troubleshooting section below):
Scroll down through the code. There are eight (8) lines!
Code:
adb devices
adb push samsung_unlock_n4-fix /data/local/tmp/
adb shell
su
cd /data/local/tmp
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
7) The command window will now display this:
Code:
[+] CID at boot time is/was: 1501xxxxxxxxxxxxxxxxxxxxx
[+] device not yet dev CID, now changing to dev CID
[+] programming new CID 150100523231384d4100657e54fc1200
[+] success! powering off device, power back on and verify CID
[+] then run this binary again to finish the process
8) Allow device to reboot. After full reboot, power down and pull battery.
9) After restarting do steps 2 through 6 again.
10) This time you will get a message in the command prompt that will say:
Code:
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked.
11) Once device is powered down it should go into a boot loop.
12) Pull the battery and SD card. Then place battery back in.
13) Turn phone back on while holding [Volume Down + Home Button + Power Button].
14) You should enter recover mode, when you see the android guy in the top left of the screen will be some text. The third to last line should be gray and say "MODE: Developer" The following line will be blue and say "SECURE DOWNLOAD : ENABLE".
*If you do not see this repeat steps 2 - 6 again*​
15) If you made it this far you are ready for PHASE 3 :fingers-crossed:
=========
| PHASE 3 |
=========​
- Rooted Boot Menu -​
16) While still on the screen showing the android guy with the word "DOWNLOADING..." beneath it, connect phone to PC and open up Odin3 on PC.
17) In Odin3 look at message box on the lower left of the screen. It should have a message saying "Added!" On the top left under "ID:COM" there should be a blue box that says "[0:COM#]" (the # will be a single digit number).
18) Click on the button that says "AP" on the right.
19) Browse to and select: twrp-3.0.2-0-trltevzw.tar.md5 (yours might be different if you have a newer version) *IMPORTANT!* TRIPLE CHECK that you are choosing the right TWRP file!! If you have more then one on your PC you will mess up your phone by flashing the wrong one.
20) Select the "options" tab in Odin3
21) In the "options" tab UNCHECK "auto reboot". Make sure all other boxes are UNCHECKED EXCEPT for "F. Rest Time".
22) Click the "Start" button.
23) If successful you should see a green box that says "PASS!" in the upper left of the Odin3 user interface.
24) Disconnect the phone from the PC.
*READ THESE NEXT FEW STEPS CAREFULLY! They require some quick timing in order to not miss the window to access recovery mode*​
25) While the phone still shows the green android guy (but now with a complete progress bar underneath) place phone into TWRP Recovery Mode. This is done by holding: [Power + Volume Down] simultaneously. You will have to hold it for about 5 seconds. Release the POWER BUTTON and then the VOLUME DOWN button when you see the "Maintenance Boot Mode" screen appear.
26) Using the Volume Rocker press VOLUME DOWN and highlight "Power Down : Turn off your device". Press the HOME BUTTON to select it.
27) AS SOON AS THE SCREEN GOES BLACK hold: [Power Button + Volume Up + Home Key] simultaneously. AS SOON AS YOU SEE WRITING IN THE TOP LEFT OF THE SCREEN release the POWER BUTTON and hold [Volume Up + Home Button] simultaneously.
28) You should now see the splash screen for TWRP Recovery Mode. *If it asks you if you want to go into "Read Only Mode" DO NOT SELECT IT!
29) At this point make sure your SD Card is inserted (if not it's okay to put it in while the phone is in this mode).
30) In the TWRP menu tap the "Wipe" button then "Advanced Wipe" and check "Micro SDCard". Then slide the option to wipe the SD Card.
31) After the wipe is complete press the little "Home" button in the middle of the bottom of the screen.
32) Open the back of the phone and remove the SD card.
=========
| PHASE 4 |
=========​
- Home Stretch, Installing "System Only" Firmware -​
33) Back at the TWRP home screen tap "Reboot" then "Download". You will now be back on the screen with the green android guy.
34) Connect phone to computer while phone is still showing green android guy with the word "Downloading..." under it.
35) Once phone is connected to the PC open Odin3.
36) Using Odin3 click the "AP" button and select the "systemonlyN910V-5.1.1.tar" file. Then click "Start" to flash the firmware. *IMPORTANT!* TRIPLE CHECK that you are choosing the right .tar file!! If you flash the wrong one you will lose root and have to start all over again.
37) After flash is complete TWRP might ask if you want to install "Super SU" now. Say NO and let the phone reboot. (This is important! A lot of guides forget to mention that you need to NOT INSTALL Super SU this way!)
38) Now with the phone still connected to the PC open the phone up like you would a USB drive and copy over "oscar_kernel_v0.2.zip" and "UPDATE-SuperSU-v2.76-20160630161323.zip" to the "PHONE" NOT THE SD CARD!
39) Reboot the phone into TWRP by holding: [Volume Up + Home Button], then select install. From there you can navigate the phones memory and click on the "kernel" zip file first to install it by swiping to install (ONLY INSTALL ONE AT A TIME). Then press the back key on the screen and install the "supersu" file.
40) Finally reboot the system.
41) Once you reboot you should see a new boot screen with an unlocked lock symbol along with a message in red on top saying: "Kernel is not SEANDROID ENFORCING" and below in yellow stating: "set warranty bit : Kernel". If you do not see this then it is a sign you might have missed a step.
42) Once booted up open the app SuperSU in the app drawer. Allow it to give the appropriate apps root permission.
43) Open Root Checker to confirm root.
************* :victory: !!CONGRATULATIONS YOU'RE ROOTED!! :victory: *************​
*At this point you should reboot back into TWRP and MAKE A FULL BACK UP of the phone. Then copy the backup to your computer. In case you make any mistakes messing around with ROMs and root programs, you will always be able to come back here without having to redo this process.* I also suggest you download Titanium Backup as one of the first root apps you get. It will allow you to back up all apps and settings.
==================
| TROUBLESHOOTING |
==================​
Q: After rooting my WiFi isn't working.
A: Some people are having issues with the incorrect modem driver being installed during root. If you are having this problem you can flash over JUST THE MODEM DRIVER to your phone. This can be done AFTER rooting. There is no need to repeat the whole process over. This is done by connecting your phone to your PC and using ODIN to flash over the correct modem driver. For the Verizon phone the BPA1 driver is the correct one, try flashing this one first. If you have a refurbished phone it's possible you have a different modem installed. I have also included the link to all the other types of modem drivers below.
Link for BPA1 Modem Driver: https://www.androidfilehost.com/?fid=24411628330026133
Link for ALL Modem Drivers: https://forum.xda-developers.com/no...mware-firmware-kernel-modem-recovery-t2942937
Q: I can't see my SIM card and/or can't see anything in my rooted phone's Service Menu.
A: For anyone who can't see their SIM card AND can't see anything in their rooted phone's Service Menu I found the solution for both problems after putting together tidbits from many threads here on XDA and elsewhere. The directions in the OP install mostly BPA1 Rom firmware but leave some BOG5 firmware. I updated the BOG5 modem to BPA1 modem firmware (with Odin) and the IMEI came back to the original sticker IMEI, the CSC and phone # and ability to see the SIM card returned. In the process of trying to solve this problem I found the hidden Service Menu could not be seen. After flashing the BPA1 modem the Service Menu also reappeared. Click here for post with a more detailed solution.[Answer submitted by: droidzer1]
Q: I'm stuck in a bootloop from flashing to 5.1.1 firmware and/or can't get out of bootloop by pulling the battery.
A: If stuck in bootloop go into recovery mode (*pull battery and then turn back on while holding [Volume Up + Home Button + Power Button]) and choose full to wipe cache and full factory reset (WARNING THIS WILL ERASE ALL YOUR DATA but it will save your phone. Use as LAST resort!).
Q: I'm stuck in a bootloop after installing TWRP.
A: Return back to TWRP by pulling the battery then reinserting it. Power back up the phone by holding [Volume Up + Home Button + Power Button]. When the writing appears in the upper left release the power button while still holding [Volume Up + Power Button]. This will bring you back to TWRP. At this point make sure your SD Card has been wiped (formatted to FAT32). Try removing the SD Card and reinstalling "systemonlyN910V-5.1.1.tar" with Odin3.
After you have reinstalled the firmware make sure you don't let TWRP install SuperSU automatically. You will only do this manually as stated in step 39.
Q: My phone crashed, I don't know what to do and nothing else is working.
A: Pull your battery and start phone back up holding: [Volume Up + Home Button + Power Button]. If TWRP is still on phone then go to "Reboot" then "Download". Connect your phone to the PC. Open Odin3 on the PC and flash a REGULAR STOCK firmware onto phone (links located below). This will revert it back to stock with everything it needs.
Q: After typing: "adb device" (without quotations) in the command prompt it says "offline" or nothing appears under "devices".
A:
Check that you are using newest version of adb. Older version might not work.
First make sure you are connected to the PC.
Try a different USB cable.
Try plugging into a different USB port.
Close and reopen a fresh instance of ADP then type:
Code:
adb kill-server
Then press ENTER and type:
Code:
adb start-server
Press ENTER again
Next uncheck then recheck USB Debugging which is located in Settings > Developer Mode. Finally type:
Code:
adb device
it should now be online.
===========
| ADB SCRIPT |
===========
Scroll down through the code. There are eight (8) lines!
Code:
adb devices
adb push samsung_unlock_n4-fix /data/local/tmp/
adb shell
su
cd /data/local/tmp
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
=====================
| To Access Service Mode: |
=====================
Service Mode is a special phone mode that will allow you to diagnose and review the settings in your phone. If you are having any issues (or are just curious) this method will allow you to review the internals of your phone.
DIAL this number into your keypad then press SEND:
*#0011#
=======================
| To Access Recovery Mode: |
=======================
Power down device (remove battery if necessary).
Turn back on WHILE HOLDING: [Volume Up + Home Button + Power button]. Then release the POWER BUTTON and hold [Volume Up + Home Button] simultaneously.
=========================================
| Video Instructions on How to Root Verizon Note 4 |
=========================================
RootJunky.com
https://www.youtube.com/watch?v=OoxWDDEFJxQ
Max Lee
https://www.youtube.com/watch?v=cfpehEkhfyg
================================
| Forum on How to Root Verizon Note 4 |
================================
http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
===================================
| Max Lee's Note 4 Root Guide with Pictures |
===================================
http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
===================
| KingRoot XDA Forum |
===================
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
================================
| Video on How to Downgrade Firmware |
================================
https://www.youtube.com/watch?v=2unAeVRqjoQ
=============================
| Link to Firmwares and Instructions |
=============================
Full Firmwares -
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
"System Only" 5.1.1 Firmware -
http://server14.stockroms.net/downl...nly/systemonlyN910V-5.1.1.tar?token=139164672
==============================================================================================================​ *Thank you to all of the developers and hobbyists who helped make this possible*​

Love it! TY!

does this apply to all versions? Iam currently on 5.0.1

bell boy said:
does this apply to all versions? Iam currently on 5.0.1
Click to expand...
Click to collapse
You can use this guide for any version. However if Youarent currently running 5.1.1 then you will need to flash your firmware to 5.1.1 using odin3. The firmware and odin3 are included in the install file at the top of the guide. A link to video instructions on how to use odin3 and flash to 5.1.1 is at the bottom of the guide.

what if i,m in 6.0.1?

gokudo86 said:
what if i,m in 6.0.1?
Click to expand...
Click to collapse
I had 6.0.1 too. Just download the 5.1.1 firmware (located in the included zip file or from the xda forum link in the bottom) and use odin3 to flash back to 5.1.1. Just be aware that you will lose all your data so do a back up first.

can not obtain root.
I started by downgrading to the firmware included in your package, I then systematically tried Kingoroot and Kingroot. I started with PC versions then tried apks. I have run all 4 variations of the procedure 15 times and I have yet to obtain root. any idea what could be holding me back?

Erik_65 said:
I started by downgrading to the firmware included in your package, I then systematically tried Kingoroot and Kingroot. I started with PC versions then tried apks. I have run all 4 variations of the procedure 15 times and I have yet to obtain root. any idea what could be holding me back?
Click to expand...
Click to collapse
For me it was the same.Then i tried it after kingoroot said it was rooted but root checker twice said no root.That worked for me.Hope they may a guide like this to go to 6.0.1 and keep root.I'm on stock 5.1.1 its a little unstable but i have root weee .Oh it took about 12 hours to get it to this point.

Erik_65 said:
I started by downgrading to the firmware included in your package, I then systematically tried Kingoroot and Kingroot. I started with PC versions then tried apks. I have run all 4 variations of the procedure 15 times and I have yet to obtain root. any idea what could be holding me back?
Click to expand...
Click to collapse
If you're having trouble getting temp root with kingoroot/kingoroot you can also try their PC version which attempts root through the PC via a USB cable. You can also try alternate version to the kingOroot programs by googling for alternatives. Unfortunately the temp root part of the process is the most unstable. For some reason one of those apps (whether through the PC or phone) seems to work better for some peoples phones compared to others. Another thing I realized is that if your phone starts to become hot from to many attempts it's best to remove the battery, let it cool down a litter and then try again.
Also make sure you do a full factory reset and clear all your cache BEFORE flashing to stock 5.1.1. I would try to do the factory reset, clear everything, then reflash stock 5.1.1. After that make sure you're connected to wifi and attempt the rooting methods again to see if you have better luck.
Let us know what works for you in case anyone else in the future reads this with a similar problem.

I did not begin the process with a factory reset before the firmware downgrade. I will try this and report back, it may not be until the morning though. Thank you for your work on the guide and taking the time to help me individually.
Update: your solution worked flawlessly on the first try with kingoroot. Thank you!
Now the issue I arrive at is "1|[email protected]:/data/local/tmp $ chown root.root samsung_unlock_n4-fix
chown: samsung_unlock_n4-fix: Operation not permitted"

videodave1 said:
...Hope they may a guide like this to go to 6.0.1 and keep root.I'm on stock 5.1.1 its a little unstable but i have root weee .Oh it took about 12 hours to get it to this point.
Click to expand...
Click to collapse
As of now(as far as I know) there is no way to root from 6.0.1. However once you have rooted on 5.1.1 there are many custom ROMS that use 6.0.1 interface and options. Flashing different kernels and ROMS are what will open your phone up to all the possibilities.
As soon as I root a phone the first thing I do is set it up the way I like it with the stock firmware. Then I make a backup in case I need to go back and then start messing around with different ROMS and Kernels to find what I like. There is even a ROM out that turns your phone into a Note 7! I've also read you can flash the 6.0.1 firmware of the Note 4 that is made to run on different carriers like Sprint.

Erik_65 said:
I started by downgrading to the firmware included in your package, I then systematically tried Kingoroot and Kingroot. I started with PC versions then tried apks. I have run all 4 variations of the procedure 15 times and I have yet to obtain root. any idea what could be holding me back?
Click to expand...
Click to collapse
Oh one thing I just realized is make sure you are doing the steps correctly when you run Minimal ADP and Fastboot. The lines of code I put up in the guide that you type into the command window doesn't show the last line when you inject the "N4" file. You need to scroll down to see it. Make sure you didn't miss doing that command. Also try running Minimal ADP as an administrator by right clicking the .exe file and selecting "Run as administrator". That might help too.

Link for Note 7 UI ROM: http://forum.xda-developers.com/note-4-verizon/development/note-4-grace-7-t3434155
For anyone who wants to try out new features beyond firmware 5.1.1. This is to be used AFTER successfully rooting.

Tripper511 said:
Oh one thing I just realized is make sure you are doing the steps correctly when you run Minimal ADP and Fastboot. The lines of code I put up in the guide that you type into the command window doesn't show the last line when you inject the "N4" file. You need to scroll down to see it. Make sure you didn't miss doing that command. Also try running Minimal ADP as an administrator by right clicking the .exe file and selecting "Run as administrator". That might help too.
Click to expand...
Click to collapse
That is the error I made. The omitting the final command in the sequence. Thank you for pointing it out!

Is there another way to download files.. 7 hrs to download one is a bit looooooooooooong

doubledragon5 said:
Is there another way to download files.. 7 hrs to download one is a bit looooooooooooong
Click to expand...
Click to collapse
Yeah I know, I'm sorry about that but that website is the only one I could find that would host a 4 GB file for free. If you know of another site please let me know and I'll upload it there. Also if you want me to place it in a google drive account or Dropbox that you have I'd be happy to do that too (unfortunately I don't have enough room in my own). If you'd be willing to share it with the community even better!
Alternatively almost everyone of the files can be found separately online by googling the name. Most are on the xda forum. Any that are not have a description next to it and can be found in one of the video tutorials or forums from the link at the bottom of the guide.

thank you
I have problem in adb
Unable to open samsung_unlock_n4-fix: No such file or directory
and samsung_unlock_n4-fix in folder adb ?

FH.1989 said:
thank you
I have problem in adb
Unable to open samsung_unlock_n4-fix: No such file or directory
and samsung_unlock_n4-fix in folder adb ?
Click to expand...
Click to collapse
When you install the program "Minimal ADB and Fastboot" it will make a folder for itself where your other programs are located. You need to place the "samsung_unlock_n4-fix" file in that same folder. That is where it will look for the file and is the reason you are getting the message "No such file or directory".
At the top of the guide, under Files Needed For Root this is explained in #3. The comment says: "place this file in the install directory of "Minimal ADB and Fastboot" (Usually C:\Program Files (x86)\Minimal ADB and Fastboot.)"

Quote from Tripper511
36) Using Odin3 click the "AP" button and select the "systemonlyN910V-5.1.1.tar" file. Then click "Start" to flash the firmware. *IMPORTANT!* TRIPLE CHECK that you are choosing the right .tar file!! If you flash the wrong one you will lose root and have to start all over again.
I didn't know you could upgrade firmware without losing root. This will save me quite a bit of time. I'm on 5.0.1 with root and want to upgrade.
Thanks, Geno

FH.1989 said:
thank you
I have problem in adb
Unable to open samsung_unlock_n4-fix: No such file or directory
and samsung_unlock_n4-fix in folder adb ?
Click to expand...
Click to collapse
Turbogeno said:
Quote from Tripper511
36) Using Odin3 click the "AP" button and select the "systemonlyN910V-5.1.1.tar" file. Then click "Start" to flash the firmware. *IMPORTANT!* TRIPLE CHECK that you are choosing the right .tar file!! If you flash the wrong one you will lose root and have to start all over again.
I didn't know you could upgrade firmware without losing root. This will save me quite a bit of time. I'm on 5.0.1 with root and want to upgrade.
Thanks, Geno
Click to expand...
Click to collapse
Be aware you can only upgrade to 5.1.1 at the moment because that is a special version of the firmware. It has the boot loader removed which is why it is called "systemonlyN910V-51.1.tar". Because the boot loader is removed you still keep TWRP and root access. If you try to flash a stock version of 5.1.1 or any other firmware you would LOSE root.

Root or ROMs for 2019 Tab A 8.0" (SM-P200/5)

I realize this may be quite hard to answer but hopefully someone has some idea
I'm really tempted by the new galaxy tab a 8 with s pen (sm-p200/sm-p205). It's the perfect size for quick note taking
Thing is, I really want root and custom roms for it, does anyone have any thoughts as to how likely these are to eventuate? It shares the same chipset (exynos 7885) as the 2018 Galaxy A8 phone which has been rooted
Is this device likely to get root or custom rom support?

It seems we have magisk root here :
https://blog.gsm-social.com/2019/07/p205-u1-9-and-magisk/
But I don't understand Arabic. Can anyone check this site?

Could someone update on any feedback if they managed to get the P200/205 rooted?
Thanks a lot for the info

I've actually try this method on my P205 (China/ Hong Kong version) but could not make it work. It's possible that maybe works on an international version of the P205 or on the P200. Has anyone else tried this method with any success?
http://androidbiits.com/root-samsung-galaxy-tab-a-sm-p205-wisdom-easily/

VeEuzUKY said:
I've actually try this method on my P205 (China/ Hong Kong version) but could not make it work. It's possible that maybe works on an international version of the P205 or on the P200. Has anyone else tried this method with any success?
http://androidbiits.com/root-samsung-galaxy-tab-a-sm-p205-wisdom-easily/
Click to expand...
Click to collapse
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb

flushback666 said:
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
Click to expand...
Click to collapse
Thanks a lot for the info! I'm on a Hong Kong/Chinese Global ROM (stock of course). What version of Android are you running in your rooted device now and do you have the WiFi or LTE version?
Thanks again

VeEuzUKY said:
Thanks a lot for the info! I'm on a Hong Kong/Chinese Global ROM (stock of course). What version of Android are you running in your rooted device now and do you have the WiFi or LTE version?
Thanks again
Click to expand...
Click to collapse
Hi,
i have the LTE Version SM-P205. As it arrived it had an old firmware so I first updated to the current stock Firmware P205DXU2ASH2 with the normal Samsung Update.
I downloaded the correspondending firmware files again for magisk patching with samfirm tool or if you or prefer from the usual samsung firmware download pages.
As i have a CSC from malaysia i took the XME CSC Firmware. From there on you can just fellow the magisk tutorial. Hopefully someone compiles a twrp recovery as firmware sources are available. So now i am on stock rooted firmware P205DXU2ASH2 .
I am using the LTE Version here in germany without any problems.
flushb
Download Mode Key Combo is VOL - + Vol +

flushback666 said:
Hi,
successfuly rooted mine. It is the malaysian version of the tab. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the keycombination for booting from the recovery partition. ( Vol Up + Power).
Use the tutorial from the readme on the magisk github page
Link: https://topjohnwu.github.io/Magisk/install.html
flushb
Click to expand...
Click to collapse
flushback666 said:
Hi,
i have the LTE Version SM-P205. As it arrived it had an old firmware so I first updated to the current stock Firmware P205DXU2ASH2 with the normal Samsung Update.
I downloaded the correspondending firmware files again for magisk patching with samfirm tool or if you or prefer from the usual samsung firmware download pages.
As i have a CSC from malaysia i took the XME CSC Firmware. From there on you can just fellow the magisk tutorial. Hopefully someone compiles a twrp recovery as firmware sources are available. So now i am on stock rooted firmware P205DXU2ASH2 .
I am using the LTE Version here in germany without any problems.
flushb
Download Mode Key Combo is VOL - + Vol +
Click to expand...
Click to collapse
Thanks again for the info. I will try follow the same steps and attempt to root again. I've had endless Samsung devices and this is the first time I am having problems trying to get one rooted.. Then again this is a much different process than the usual and we don't have Recovery yet. Given the limited sales and interest in this Tab (which is really a shame), probably there won't be too much development around it. This is actually the best price/features Tab Samsung makes now and the perfect form factor/size. If only the hardware was a bit faster and the camera a bit bigger.. but hey, can't have everything, haha
Thanks again for sharing the info, much appreciated

VeEuzUKY said:
Thanks again for the info. I will try follow the same steps and attempt to root again. I've had endless Samsung devices and this is the first time I am having problems trying to get one rooted.. Then again this is a much different process than the usual and we don't have Recovery yet. Given the limited sales and interest in this Tab (which is really a shame), probably there won't be too much development around it. This is actually the best price/features Tab Samsung makes now and the perfect form factor/size. If only the hardware was a bit faster and the camera a bit bigger.. but hey, can't have everything, haha
Thanks again for sharing the info, much appreciated
Click to expand...
Click to collapse
Hi,
no problem if you have questions just ask.
Attached screenshoot from root check
flushb

flushback666 said:
Hi,
no problem if you have questions just ask.
Attached screenshoot from root check
flushb
Click to expand...
Click to collapse
You know, I have received lots of PM regarding root as no one seems to be successful at it. You should start a new thread, call it something like "SM-P205 ROOT ACHIEVED" and post a step-by-step guide on how you did it. Not many people are following this thread here and news of root for this Tab will make thousands of people very happy worldwide.
If you have the time, you should do it. The whole community here appreciation is guaranteed
Thanks again

VeEuzUKY said:
You know, I have received lots of PM regarding root as no one seems to be successful at it. You should start a new thread, call it something like "SM-P205 ROOT ACHIEVED" and post a step-by-step guide on how you did it. Not many people are following this thread here and news of root for this Tab will make thousands of people very happy worldwide.
If you have the time, you should do it. The whole community here appreciation is guaranteed
Thanks again
Click to expand...
Click to collapse
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb

flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
Very cool, and I'll contribute to the thread with my feedback as much as I can myself too. Thanks again

flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
yes, please when you have time, do a tutorial. thanks a lot!!!

VeEuzUKY said:
Very cool, and I'll contribute to the thread with my feedback as much as I can myself too. Thanks again
Click to expand...
Click to collapse
Done!
Samsung Galaxy Tab A 8.0 (2019) with S Pen (SM-P205) ROOT ACHIEVED / Howto
flushb

flushback666 said:
Hi, yes will do so but i dont have much time today.
Hopefully i get it done tomorrow.
flushb
Click to expand...
Click to collapse
flushback666 said:
Done!
Samsung Galaxy Tab A 8.0 (2019) with S Pen (SM-P205) ROOT ACHIEVED / Howto
flushb
Click to expand...
Click to collapse
Awesome, I'll check it out now

Just bought the wifi variant of this tablet here in Germany too.....Seems to be a good 8" alternative. Looking forward to installing twrp and a Lineage ROM. Any news for that?

samsung unlockBL downgraderoot AutoBootCharge autoSd3HrIdle Charge to 65%
It is sharing of experience only without any liability or warranty.
Why: I use the tab very rarely but in critical requirement, I am getting it in discharged condition when i needed. Good news is that , in off condition it consumes around 1% per 10 days. I did not want to root it, but this tab at least shoud have have scheduled shutdown like other makes. The battery protect mode does not function properly. However thanks to Samsung for leaving the facility to unlock the Bootloader, rooting etc for advanced users (I feel definitely it has the capability to lock fully like apple )
Pre requirements
1. Samsung Tab A 2019 P200 (I have no experience on other models) charged more than 50%
2. Usb cable
3. Samsung USB Drivers
4. Windows 10 PC with UPS
5. Firmware suitable to your phone / region
6. Odin3-v3.14.4
7. 7Z ZS
8. Magisk Manager
9. Root explorer
I. Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
The following worked for me
• Installed Samsung USB driver on PC
• Allow bootloader unlocking in Developer options → OEM unlocking
• Disconnect the USB cable
• Power off the device
• Press and hold Volume Up & Down keys
• Insert USB cable
• Long press Volume up key
• Press Volume up ( yes) to unlock BootLoader
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
• Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
• Enable developer options, and confirm that the OEM unlocking option exists and grayed out! (yes it happened in my case) The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
• Your bootloader now accepts unofficial images in download mode.
II. Downgrade Flash instructions
1. Extract (unzip) the Samsung firmware file. Recommended using 7-Zip ZS
2) Install Samsung USB driver on PC if already not installed
3. , Extract Odin ZIP file Odin Tool 3.14.4 Downloaded, Open Odin execute file
4.) Remove Samsung . Google etc accounts from Tab
5. Reboot Samsung phone in Download Mode (hold Power + Volume Up buttons, it will booted to Recovery, select reboot to bootloader, Downloading screen will come then plug-in cable)
6. Connect you Samsung phone and wait until you get a blue symbol with com port no in Odin
7. Add the 1 file Samsung firmware to AP/PDA or 4 files Samsung firmware (AP/BL/CP/CSC) to it's slots (for P205 it will be 5 files)
8. Make sure re-partition is NOT ticked at Options at Odin
9. Click the START button, sit back and wait few minutes
Downgrading BootLoader-Theory
Downgrading BootLoader is Not possible unless you modify the BL….. .tar.md5 by removing the .bin files in it, then tar it up and flash in odin (- NOT TRIED).
The secure bootloader (sboot.bin) won't allow the downgrade of itself. you can't downgrade because the bootloader is protected by Rollback Prevention, So apparently I can only install firmware files which come with the same Bootloader.
We need to know what your current "Build Number" is on the phone. You also can't downgrade to other bootloaders that are lower then your current one, so if you're on bootloader 5 you need to use the Oreo bootloader 5 version firmware or it will not work. (Bootloader # is the 5th spot from the right.
Rollback Prevention (RP)
Rollback Prevention blocks the device from loading or flashing an approved but old version of boot components. Old versions of software may contain known vulnerabilities that attackers can exploit. Rollback prevention checks the version of the bootloader and kernel during both boot and updates, and blocks these processes from continuing if versions are unacceptably old. The lowest acceptable version of the bootloader is stored in secure hardware fuses when the device is flashed, and the lowest acceptable version of the kernel is stored in the bootloader itself. Whenever a vendor-applied update occurs, the lowest acceptable version can be incremented in the fuses. Because this value is kept in fuses, it cannot be decremented even through physical tampering. Rollback Prevention fuses are set at manufacturing time in the Samsung factory to prevent old firmware versions from overwriting newer ones.
Present version on device: P200ZHU2ASK2 (Settings>About Tabet>Software information>Build No XXXX XXXXXXX P200ZHU2ASK2, Service Provider SW ver ………….TGY// i.e Hongkong) , tried and failed is : P200ZHU1ASG1 , but now downgraded (bootloader is same version) P200ZHU2ASH2.
III. Rooting
Notes Installing Magisk
• Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
• Installing Magisk WILL trip KNOX (void Warranty)
• Installing Magisk for the first time REQUIRES a full data wipe, backup before continue
• You have to have your bootloader unlocked before following the instructions
Instructions on Rooting
1. Unzip the firmware P200ZHU2ASH2 on PC and copy the AP tar file to your Phone. It is normally named as AP_P200ZHU2ASH2_CL16717766_QB25581052_REV01_user_low_ship_meta_OS9.tar.md5
2. Install the latest Magisk Manager
3. In Magisk Manager: Install → Install > select and patch file> browse to location of file > tap and hold to select >open e.g AP tar file> working version / build is MagiskManager-v7.5.1.apk) (internet connection will make install button visible )
4. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
5. Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
It will be copied to PC at C:\Users\......\AppData\Local\VirtualStore\Program Files (x86)\Minimal ADB and Fastboot
6. Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options !
7. Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
8. We now want to boot into the stock recovery to factory reset our device.
9. Disconnect the phone.
10. Full data wipe is mandatory! Do not skip this step.
Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the combo key (Power + Volume Up) to boot to recovery continue pressing the volume up button until you see the stock recovery screen (Not patched recovery , as it has Factory data reset, try again, view recovery logs only) as we need it.
11. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
12. This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key (Power + Volume Up) to recovery. After seeing the bootloader warning screen (first screen), release all buttons so it can boot to the system.
13. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
14. After the device is booted up, done the usual initial setup. The following steps will need an internet connection.
15. I have manually installed the APK , downloaded in step 2 and continued to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
16. Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
17. As this is a new device from 2019 with System-as-Root and Android 9.0 Magisk must be installed to the recovery partition. Everytime you reboot you must press the key combination for booting from the recovery partition. ( Vol Up + Power) but in my case it is always booting to Magisk.
Theory: Since some devices no longer use ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
After installing Magisk in recovery:
• (Powering up normally) → (System with NO Magisk) or if required reboot phone once OS is loaded
• (OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
• (OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
In my case (for my version of firmware) once magisk system is booted as above , every time it is loading magiskpatched system if shutdown is used (while charger is not connected ), but if we use reboot it is rebooting to Stock system- further, if we shutdown while charger is connected it is will shutting down and start charging with charging animation (means if we press power button it will boot to stock system) great advantage as stock (partially rooted?) also can be booted when required.
Additional Info
• Magisk actually patches 3 partitions on your device:
o vbmeta: replace with empty vbmeta image to disable partition verification
o boot: remove the signature of the image to prevent soft bricks
o recovery: this is where Magisk is actually installed
• Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
• If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
• If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Release Keys ( P&V+) for System with Magisk
Keep pressing volume up for Actual recovery
IV. Splash screen and warning screen change
1. Download the correct firmware of your Samsung
2. Unzip the firmware files with an extractor (winrar, etc)
3. Open the BL file WITH 7-ZIP EXTRACTOR (example) BL
4. BL_P200ZHU2ASH2_CL16717766_QB25581052_REV01_user_low_ship.tar.md5
5. Extract the param.bin.lz4 file WITH 7-ZIP EXTRACTOR
6. Open the param.bin.lz4 file WITH 7-ZIP EXTRACTOR and extract the param.bin file
7. Extract param.bin WITH 7-ZIP EXTRACTOR. All images are extracted in a folder.
8. edit logo.jpg and svb_orange.jpg or any other file suitably
9. select all files(not folder) and right click and select 7-Zip ZS Add archive > select archive format tar>ok to get param.bin.tar
10. Close 7-zip ZS, now change the name of above file from param.bin.tar to param.bin.
11. Right click on above param.bin select 7zip ZS > add archive…> select select archive format tar>ok to get param.bin.tar again
12. Change its name to BL_param.bin_only_to_change_logo (just to remind it is BL) Now we have the param.tar file ready for ODIN.
13. Open ODIN 3.13.3, start your phone in download mode, load the param.bin.tar file in the BL section and click on start.
Note: At the end of the flashing with ODIN the phone restarts showing the modified image, but it starts in recovery mode, you just have to accept restarting the phone, and it will start normally without losing data or the configuration of your Samsung Tab A P200
V. Auto Boot Charger connected once charged to more than 5 %
1. This is a bonus, if magisk is in effective condition, it will auto boot when charger is connected.
i.e. If it boots on auto when charger is connected that means that the sytem is magisk patched
(no need to edit lpm, however if we modify lpm, phone will hang at power symbol screen in non-magisk mode –to reset it, remove charger connection , press power+VolUp+VolDown simultaneously still phone restarts )
VI. Auto shutdown on 3 hours idle
1. Install Automate app
2. Import file
“Boot to on and Auto Shutdown by 3hr idle (reset by Foreground GMusicFMusicPAmp or Charge or 11 min on) V8.flo”
3. At automate settings select Run on System start up
3. Start flow
VII. Auto stop charging at preset max and restart charging preset min shutdown phone at preset battery low
1. Install latest AccA 1.0.23 app from github and connect to internet
(older beta app was changing battery % with every booting , showing fast draining without any actual drain etc, if charger is connected instead of rising battery level , it is showing as decreasing , i.e. battery sync , ghost effect issues)
Or
If above does not work uninstall AccA and connect to internet , open magisk manager >options>downloads>search for acc >install Advanced Charging Controller 2019.7.21-r1 (201907211) > install > rebotot)
Or if above is also not working properly please use battery charge limit v1.1.1 from play store (it will not have all options of AccA.
2. Configure as required like max charge 65 , re charging start level at 35 % shutdown at 5 % etc by editing config.txt file at root>data>adb>acc-data> capacity= 5, 101, 35-65 (101 not to stop intermittently between 35-65 % charging) and save
Now one can connect phone always to power source without wearing out Battery.
It my experince only and thanks and regards to all who contributed on respective sections / fields.

hi,
thx for the comprehensive instruction.
I have successfully rooting my sm-p205
I have 2 questions if u pls help me :
1. I want root my sm-p205 because I want to use tincore keymapper. but although now I have successfully rooted it, it seems that I have to set the selinux to permissive.
I have tried all I've found, from using selinuxmodechanger, selinuxswitch, or even using terminal with su 0 setenforce 0, and all not working. that selinux still enforcing.
can u pls help me how to change the selinux ?
2. if I couldnt change the selinux, than it's no use for me to still on root. Is there anyway to go back to original stock firmware and unroot ? because I read on the last instruction of magisk that I may not flash it again with usual ap file that it may make it brick ?
thx

Any custom ROM available for this tablet? I can't find one anywhere. Thanks

At my wits end

So I'm trying to get Magisk installed on my bootloader/OEM Unlocked S10+ (SM-G975F beyond2lte) device.
I can do that fine by downloading the latest official firmware for my device, installing that (BL/AP/CP/CSC) through Odin v3.14.
That installs fine.
Then I sideload Magisk v23.0, and the AP file I just flashed via Odin over adb via push.
I install Magisk, recovery-patch the AP file, usd adb to pull the file back over onto my desktop. I restart the phone in download mode and once again populate Odin with the BL/AP/CP/CSC files, but this time the AP file is the one I got from Magisk.
Start that, let Odin restart my phone whilst I'm holding Bixby/Power-Up/Power, I release those three once the bootloader warning message comes up.
I set the phone up like normal, but there's the issue - my 128GB device only reads as having 32GB - I can setup Magisk fine, it asks me to download an extra bit, then auto-restarts the phone after 5 seconds.
Yay, I have root! Boo, I'm missing 96GB of free space...
I've read that installing TWRP can help fix this, fair enough, I try to install TWRP (I've tried through both the "dd" method via adb shell, and patching the twrp 3.5.2_9-3 via Magisk, and installing with vbmeta over Odin), but that then eliminates Magisk.
I've been trying this now for days, literally days, reading through different forum posts, detailing my steps to myself in notepad++ step-by-step so I can see what it is I'm doing.
I'm left with zero clue what to do now except reach out and hope for some help from this forum.

Should have known... Now that I've posted on XDA it's fixed... In-case anybody else is having trouble here are the steps I've written down for myself.
Phone is S10+ SM-G975F (beyond2lte) - Bootloader / OEM Unlock is already unlocked.
******************************************************************
FLASHING STOCK ROM (ALWAYS GOOD PLACE TO START):
******************************************************************
1. Phone into Download mode (Vol Down + Bixby button, insert USB (Don't use power button))
2. Odin, AP in AP, BL in BL, CP in CP, CSC in CSC (NOT the HOME one). USERDATA stays EMPTY!
3. Phone may restart/erase several times, in the end inbuilt recovery will turn up. Use this to factory reset.
4. Wait for it to continue like normal after factory reset.
5. Setup INCLUDING with WiFi. WiFi REQUIRED. No need to add your account
6. Make sure OEM Unlock is still checked.
*************************************************************************************************
ROOT INSTRUCTIONS: https://www.thecustomdroid.com/samsung-galaxy-s10-root-guide/
*************************************************************************************************
1. Use adb push to shunt over Magisk Manager (download latest one), and the "AP" file
2. Install Magisk Manager
3. Open, select install, make sure "Recovery" is ticked, next, select "Select and Patch a File"
4. Select the AP file, then click "Let's Go"
5. Use adb pull, as the MTP file transfer ****s up the large patched files Thanks Microsoft!
6. (adb reboot bootloader) Restart phone in Download mode
7. Open Odin, & flash the patched Magisk AP file in AP, BL in BL, CP in CP, CSC (NOT the HOME one) in CSC.
8. Let device reboot while holding POWER, BIXBY, and VOL UP, and release all 3 buttons on bootloader warning screen.
a. NOTE: If you end up with a bootloop, hold POWER, BIXBY, VOL UP until you enter the built-in recovery menu, and do a factory reset.​
9. Set device up like normal, remember to enable the WiFi
a. Check device internal storage, should be XXX out of 128GB (Or whatever you have)​
10. Search installed apps for the Magisk one, it won't have a proper icon to begin with
11. Open it, and continue the setup as it instructs. It’ll reboot the phone.
12. Device is now rooted.
********************************************************************************************
TWRP INSTRUCTIONS: https://www.thecustomdroid.com/samsung-galaxy-s10-twrp-magisk-root-guide/
********************************************************************************************
Phone must be rooted for this to work!
1. Copy the un-magisked file "twrp-3.5.2_9-3-beyond2lte.img" onto phone
2. Open Magisk, select install, make sure "Recovery" is ticked, next, select "Select and Patch a File"
3. Patch the "twrp-3.5.2_9-3-beyond2lte.img" file
4. Copy that patched file onto your PC, and rename it magisk_patched.img
5. Open powershell in same folder, and type
a. mv magisk_patched.img recovery.img​b. tar cf twrp-beyond2lte.img.tar recovery.img​
6. Enter into Bootloader mode
7. Load up Odin, untick auto-reboot, and put the magisk-patched TWRP.tar file in AP
8. Press PWR and VOL-DOWN to exit Download Mode, as soon as screen goes black, switch to PWR, BXBE, VOL-UP, release PWR & BXBE when you see bootloader warning, keep VOL UP
9. In TWRP, swipe to allow modifications
10. Flash multidisabler-samsung.zip
11. Go to wipe - format data - yes, after go back to TWRP home screen
12. Click Reboot > Recovery (NOT SYSTEM), you now have a TWRP enabled device.
13. Reinstall Magisk, and check root status, it should ask you to do the whole re-download/5 second reboot thing because you did the wipe > yes thing in TWRP.
UPDATE: After restarting my phone I lost root (Magisk was still installed, but it didn't have an "installed" version listed). To get past this I...
*************************************************************************************************************************
Magisk reinstallation via TWRP:
[ROM][Signature Spoofing]LineageOS 18.1 for S10E/S10/S10+ Exynos
oHello my friends, please someone could make a video to activate root? I can't even do it with the key combinations... Please help me I can't get into the bank apps :(
forum.xda-developers.com
*************************************************************************************************************************
1. Copy the "beyond2lte-boot-magisk.img" onto phone (see URL above)
2. Run Magisk, patch the "beyond2lte-boot-magisk.img" file, then copy it over onto your MicroSD (I just find it easier)
3. Boot into TWRP > Install > Install Image button (Bottom Right)
a. If TWRP has vanished, follow steps above to get it back​
4. Flash the patched file to "Boot"
5. Go to TWRP Home screen > Reboot into Recovery (not into System)
6. Check Magisk Manager should have Root again (Don't update Magisk via app though, or you’ll bollocks the whole thing up, and have to start all over from the start.)

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?