Database Users

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

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***

mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?

That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.

mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.

Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.

mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe

Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)

Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.

VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.

mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.

I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.

apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.

mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!

Okay I can't add anything special but daaamn this community is amazing. So much help I love you all

To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse

Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw

mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.

VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.

5S/5G Roms and Root Mega thread [Updated November 2022]

Nubia Red Magic 5G and 5S Roms and Root support Thread
Second post for TWRP and Magisk installation. Mirror for all roms and tools at end of post
Latest Official Rom updates
Android 11
US/Asia - V8.70 Nubia Link MD%: will update soon
EU - V7.70 Nubia Link MD5: will update soon
China - V9.50 Nubia Link MD5: 361AC13CA52AB83C239783FBAB088CEA
Android 10
US/Asia - V8.12 Nubia Link MD5: 6e930fc2431b3daeae2d94145926a6c1
EU - V7.15 Nubia Link MD5: bb9e3153716851e87f196ae6b4f44a2e
China - V6.23 Nubia Link MD5: BD447840ACA4D48F9443B94D2EAD890F
Change Log - 8.70 / 7.70 Android 11
- Security Patch October 2022
- Game Space enhancements
- Game space Gyro sensitivity menu
- game space touch sample rate improvement
- Fixed: corner of screen non-touchable in some cases
- Fixed: issue where game would fail to close
- Fixed: location of caller display
-Fixed: screen tearing when using 144hz
-
Bugs -
in Testing
- Always on display notification not showing
- memory leak in nubia launcher (requires forced close often to stop phone from lagging)
- small window mode for telegram and discord have wrong zoom/ aspect levels.
_____________________________________________________________________________________________________________
UNBRICK TOOL for 5S - Courtesy of @johnny886
Use this tool, with directions on the thread to restore your device to USA/Asia 8.07
you can then install TWRP and after flash any region rom after creating a somewhat universal unbrick tool for those in different regions.
Follow directions on the thread. but here is a link to the Thread. A Mirror for the tool is in my Personal Mirror at the bottom of this thread post.
Link to Thread
Confirmed working with 5G devices - but its recommended to update as soon as you unbrick.
_____________________________________________________________________________________________________________
For unlocked bootloader
Fix your fingerprint sensor.
here Link
--------------------------------
Update Instructions.
Note
for Android 11 do not flash through TWRP you will softbrick.
____________________________________________________________________
For Stock devices without root
- disable security. No pin, no face unlock, no finger print, no pattern. remove all security.
-download zip file
-go to system update tap three dots and select local update
-Navigate to update.zip and select.
-your phone will reboot and install new rom
- you phone will reboot once more and you will be greeted with your lock screen
- setup Phone with security options as before flash.
For devices with "LOCKED bootloader" Root / TWRP (not tested on A11)
- take backup of vbmeta and recovery partitions in TWRP
- change the name of both files to vbmeta.img and recovery.img
(VBmeta is often 64kb big and Recovery is often 90+mb big.)
- copy and paste these new img files into the update zip.
- flash through TWRP
- go back to main menu, select advanced, then select option
"disable replace TWRP" to keep TWRP as your recovery.
for devices with "Unlocked bootloader" (not tested on A11)
-make full backup
-download zip
-install zip through TWRP
-reboot
__________________________________________________________________________________
Custom Roms and Kernels
Kernel
Mattofthedead's Redmagic 5S kernel for LOS and Stock roms LINK
Roms
Rom Builder Ra's Custom Roms - Please post any bugs or issues in the related threads.
Pixel Experience Plus
Ressurection Remix
NOTE : to boot any Custom rom on the 5S device. Flash the Rom following the directions. then flash Matts LOS kernel Version 3
__________________________________________________________________________________
------------------------------
Old roms
Android 11
V8.65 Nubia Link MD5: 3d52e18c66366d3d23744184425d3926
V8.64 Nubia Link MD5: a7e61f5e2f7c377a6850cf6ac3a62aa7
V7.65 Nubia Link MD5: 746dad5b6145dfba1108355095a6ad46
V7.64 Nubia Link MD5: 55371ee8e5728aee2bc7df5b3a7d6585
V9.42 Nubia Link MD5: D492B92DD83B366508CDD74DE7D152A3
V9.40 Nubia Link MD5: D28F26289A9B75F771EF4F623F0BB367
V8.57 Nubia Link MD5: 266819d4b09c2c52aadb39e948dc84bc
V8.59 Nubia Link MD5: d7e32b7a3e833adc57fcf734aa47f5a3
V7.57 Nubia Link MD5: 81ee71869f660a28b631d871ffb59524
V7.60 Nubia Link MD5:
V9.26 Nubia Link MD5: 8997375CD97D8F7F261F21121FC8EFAA
Android 10
v6.18 Link MD5: 9AC5EA5F64835C1995E4A81D4973FB71
V6.13 Link MD5: F38ED2D7CB58252D308B29D1D4517DB9
V7.07 Link MD5: ffc3fdaf4afc522aa3a084d9275f2cb6
V7.14 Link MD5: 0f879160fbf8b556de5303207b93d0d1
V8.07 Link MD5: b30dab221be73292c5da7884afc0363f
V8.11 Link MD5: 85d9366a3017112cb68d66041e725ce6
________________________________________________________
Personal Mirror - Located in Eastern Canada
________________________________________________________

TWRP and root guide for 5S and 5G on Android 10 only - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked during and after process is complete.
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put an installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file found at the end of this post
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted. (CD = Change Directory)
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable replace TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Reboot to system for the first time and complete the initial setup. this is to create the user space partitions data/media ( preferably do not make a pin or pattern at this stage)
13. once in the rom, connect to PC and copy over the Magisk zip to the internal memory. then reboot holding Volume up
14. once back into TWRP (if you created a pin during setup TWRP will ask you for your pin to access data) go into install and flash the Magisk.zip you moved in step 13 then reboot. once back into the rom, you will see a Magisk app, tap it and allow to update, the APK will install latest version of the manager.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have an update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini - zip updated with Magisk 21.4 zip
MD5 for ADBfastbootmini.zip: 0ad97a9ae1539b26ef78c849b169e807
I'm working on a process that will update to Android 11, through TWRP and root, without losing data. Much like a stock update.
I will update the thread once my tests are complete.

Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated

josehdx said:
Hello. I can not flash (i cant even copy) the zip via TWRP. I see the storage device on my windows laptop. I have wipe data cache and dalvik, but it does not copy it and i can not restore my device. Help will be appreciated
Click to expand...
Click to collapse
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)

Patrick Morgan said:
Try putting update zip on a USB key and connect via OTG and flash this way. Moving files with TWRP for some reason corrupts or does not complete transfer.
Make sure to factory reset. If you're coming from a used update, backup your data partition and wipe everything. Then check to see if the partition is in fact empty. ( I noticed sometime my data partition did not erase)
Click to expand...
Click to collapse
Thanks
Working fine after full data partition wipe.
I have an additioal question regarding further updates, and i would not want to open a new topic. so, after flashing the zip, i "lost" TWRP but i already have root access. I wonder if is possible to flash upcoming updates with the default recovery built in on the phone, if not, i would assume i need to install TWRP again.in any case, will side loading update make any problem with the current system? i hope my question and context is clear

As these are official ROMs, they will replace the recovery and remove root from the phone.
If you do not have root, flashing these zips from the system menu local update should work. But if you have root or TWRP it's better to flash through TWRP.
You could just flash TWRP again after flash, but I personally modify the zip and add the recovery to it to save me going into fastboot after each update.

Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.

Darkvenum79 said:
Is it possible to install the US rom on a device with EU rom?
in the EU version I can't set the frame rate to 144 hz.
Click to expand...
Click to collapse
I've spoken with another EU rom user, that has the same issue before. it seems it was an error in the stock rom.
reinstalling 7.07 from the links above should fix your problem.
both 7.07 (the EU rom) and 8.07 (the US rom) are exactly the same. the only difference is the languages from what I can tell.

I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks

josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
No it wont.
There is a specific step by step that is required to get it functioning again. And it only survives until your next full wipe, which i assume you will do more often flashing non official roms.
I can grab the steps and edit this post for you.
Edit -
Prep.
have a black / very dark brown leather. (belt, wallet, etc)
a soft gel plaster / Bandaid
(something skin textured and in a pink / light beige colour) texture and colour are important.
First step is clear data in the infingerprint app in app info and remove permissionfor data memory - (you need to show system apps to find it)
- digit in call phone code:
*#9959#
(android 11 use Activity launcher (playstore) to enter fingerprint menu)
- uncheck performance checkbox , check only calibration checkbox
Steps -
1. Press start then wait.
2.Press next and with plaster / bandaid press on circle
3.Press next and use wallet / belt ( the display becomes black for black calibration)
4.Press next and use gel plaster / bandaid again but pinch it in so only the part with your finger touches the circle.
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access to data memory then reboot device.
Enjoy your Finger Print once more!
P.S. = do this procedure in a very dark room to improve the chances of it succeeding.
Thanks to qtr1st (Salem) and mikekrunk (Mike) for the steps and information.

josehdx said:
I have a silly question. Unfortunately i unlocked bootloader and i lost the fingerprint capability. I have tried many times to do the calibration without success. I wonder if a factory flash (EDM or any nubia tool) can restore the capability and then use this guide to do the rooting? Thanks
Click to expand...
Click to collapse
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
Patrick Morgan said:
TWRP and root guide for 5S - (these steps will NOT unlock your bootloader) - these steps use a bypass method to install a recovery without unlocking bootloader. the command below is to allow flashing of partitions. bootloader status is still locked after process is complete.
Pretty short step by step to get twrp and Magisk if you want, on your phone. (Red Magic 5S)
Note. if you already have ADB and fastboot drivers installed, this folder will work as is. if not I put a installer in the folder too to install a mini adb fastboot setup. which needs windows driver signing turned off (windows 8-10) this can be done by going to advanced startup and choosing to boot without driver signing.
1. Download zip file attached or mirrored
2. Extract to root of C: drive
3. open CMD prompt with admin privileges
4. CD to the ADB folder you extracted.
5. Connect your device in Fastboot mode (power off. hold volume down +Power until it vibrates. then release power but continue to hold volume down)
6. Once in fastboot mode, with cable connected to the computer run these commands
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.
More NOTES.
this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
its also recommended to have a update.zip of your current rom (which you can download from the post above), incase you need to reinstall the rom after flashing the new recovery or VBmeta.
OEM unlocking in the developer options is NOT needed. since you are not unlocking your bootloader. this step can be ignored.
I'll update this tutorial with newer steps if needed.
Thanks to those that created all these great tools.
@wzsx150 - for their version of TWRP
John Wu - for Magisk
@mslezak vbmeta_skip
If i've helped you root your device, please hit thanks.
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
where is the link of twrp.img

sansha1211 said:
where is the link of twrp.img
Click to expand...
Click to collapse
Patrick Morgan said:
Link ADBmini
MD5 for ADBfastbootmini.zip: e49f162080c6a2124c243716546ad710
Click to expand...
Click to collapse
that file called Link ADBmini has all you need

Is it ok to flash Eu rom to my NA/asia rom?

After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please

Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
reboot to bootloader by... power off device -> press and hold volume down and power button until you see the logo -> connect device to your computer then do the steps 7 to 12
also once you are in TWRP make sure you ... this must be done on a clean system. you need to wipe all data partitions to boot to system. re writing VBMETA causes encryption to break. until you reboot. so you lose everything Make a backup of your data partition on to your PC before doing anything.
7. fastboot oem nubia_unlock NUBIA_NX659J (this allows you to flash the device partitions)
8. fastboot flash recovery TWRP-xxx.img (xxx being the version number of the TWRP image you choose to install)
9. fastboot flash vbmeta vbmeta_skip.img
10. reboot to recovery (from the fastboot menu) it should load TWRP
11. if TWRP does not ask you to keep recovery from being over written, go to advanced and choose disable overwrite TWRP. to keep TWRP as your recovery, and stop the system from re writing the stock recovery.
12. Magisk zips files are in the folder. copy to device and flash through twrp. and install the apk after boot. done twrp and root.

Rai972 said:
After reboot it ask me for verify pin and now I can't load the TWRP.img Partition volume Full error help me please
Click to expand...
Click to collapse
if you have not removed your pin before flashing any of the roms. it asks you for YOUR own pin that you made when you setup the phone. so use your own pin.
the process of rooting your device, clears a security partition. (the VBmeta partiton)
this deletes the encryption you had on your phone. so the devices partitions are unaccessable and need to be wiped before you can boot to system.
you need to clear data. all data. then check in TWRP file browser if your data partition is clear. .. if you see folders with random letters its not been formatted correctly.
so, in the wipe menu on TWRP you should go into advanced and change the partition type to ext4 then back to f2fs to clear the partition of data.
once your phone is clear you should be able to wipe cache and davik then reboot to system for it to start like a factory reset.

sansha1211 said:
esy re-lock bootloader fingrperint work fine without calibration
---------- Post added at 12:13 PM ---------- Previous post was at 12:08 PM ----------
where is the link of twrp.img
Click to expand...
Click to collapse
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?

josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
adb devices
adb reboot bootloader
fastboot devices
fastboot flashing lock

josehdx said:
How should i relock the bootloader? Via cmd, command doesn't work. Should i lock also via developer options?
Click to expand...
Click to collapse
via cmd -- fastboot flashing lock

After i reboot in TWRP and disable replace TWRP, i install magisk from a USB otg, and then i wipe all data, then i reboot system but it keeps opening TWRP in every reboot, i had to install Stock Rom to have my phone back but without root, what im doing wrong?? thanks
Edit: now it worked, tried a few times and worked don't know what failed

[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?

General Questions, how to flash the SM-T585

hello, I need your help please.
since I use the pixel smartphones, I have no longer flashed. now I got the SM-T585 gift and wanted to flash the https://forum.xda-developers.com/t/unofficial-rom-t585-lineageos-18-x-11-0-64-bit-treble.4511073/ on it. but I'm a bit rusty now and would need your help.
Where do I get latest bootloader and modem?
How do I flash them to the tablet?
When do I flash the repartition script?
How do I get TWRP on the tablet?
How to backup all partitions (it least efs) and store somewhere?
I appreciate any support.
Thanks, Markus from Germany

bavmouse said:
hello, I need your help please.
since I use the pixel smartphones, I have no longer flashed. now I got the SM-T585 gift and wanted to flash the https://forum.xda-developers.com/t/unofficial-rom-t585-lineageos-18-x-11-0-64-bit-treble.4511073/ on it. but I'm a bit rusty now and would need your help.
Where do I get latest bootloader and modem?
Click to expand...
Click to collapse
These are part of the firmware package for your device. You can use programs such as Frija, or websites such as Sammobile to download the latest firmware.
bavmouse said:
How do I flash them to the tablet?
Click to expand...
Click to collapse
Put the tablet in download mode, and use Odin to flash the files. Make sure the bootloader is unlocked. You most likely cannot immediately flash custom binaries after you unlock the bootloader; skip through initial setup, connect to the Internet, ensure OEM Unlocking is still visible in Developer Options.
When in download mode, there should be a line that reads KG STATUS. If this is CHECKING or COMPLETED, you should be OK. If it says PRENORMAL, you need to boot the OEM firmware and ensure OEM Unlocking is visible. This is due to Vaultkeeper - even after the bootloader is unlocked, Samsung throws a few wrenches into the mix to make things tricky.
bavmouse said:
When do I flash the repartition script?
Click to expand...
Click to collapse
After you've installed TWRP.
bavmouse said:
How do I get TWRP on the tablet?
Click to expand...
Click to collapse
The TWRP image for your tablet should be available as an AP.tar file. Once you've ensured Vaultkeeper has unleashed your bootloader, you can flash this using Odin in download mode to the AP slot.
bavmouse said:
How to backup all partitions (it least efs) and store somewhere?
Click to expand...
Click to collapse
You can use TWRP to create a backup.
bavmouse said:
I appreciate any support.
Thanks, Markus from Germany
Click to expand...
Click to collapse
Here to help.

V0latyle said:
These are part of the firmware package for your device. You can use programs such as Frija, or websites such as Sammobile to download the latest firmware.
Put the tablet in download mode, and use Odin to flash the files. Make sure the bootloader is unlocked. You most likely cannot immediately flash custom binaries after you unlock the bootloader; skip through initial setup, connect to the Internet, ensure OEM Unlocking is still visible in Developer Options.
When in download mode, there should be a line that reads KG STATUS. If this is CHECKING or COMPLETED, you should be OK. If it says PRENORMAL, you need to boot the OEM firmware and ensure OEM Unlocking is visible. This is due to Vaultkeeper - even after the bootloader is unlocked, Samsung throws a few wrenches into the mix to make things tricky.
After you've installed TWRP.
The TWRP image for your tablet should be available as an AP.tar file. Once you've ensured Vaultkeeper has unleashed your bootloader, you can flash this using Odin in download mode to the AP slot.
You can use TWRP to create a backup.
Here to help.
Click to expand...
Click to collapse
thank you very much for your detailed answer.
I have now collected all the programs and files.
but could you please give me a brief list of the exact order of procedure in bullet points, that would be very helpful.
and when and how do i unlock the bootloader?
thank you, markus

bavmouse said:
thank you very much for your detailed answer.
I have now collected all the programs and files.
but could you please give me a brief list of the exact order of procedure in bullet points, that would be very helpful.
and when and how do i unlock the bootloader?
thank you, markus
Click to expand...
Click to collapse
Unlock bootloader:
Enable developer options
Toggle OEM Unlocking to ON
Power off device completely (disconnect USB cable)
Start device in download mode: hold both Volume buttons, do not press Power, plug in USB cable from PC, device should start in download mode
Unlock bootloader; hold Volume Up until bootloader unlock screen appears, select Continue. This will wipe data
Disable Vaultkeeper:
Boot device and skip through initial setup. Connect to Internet. Enable Developer Options and ensure OEM Unlocking toggle is still visible. If it is not, Vaultkeeper is still enabled and you won't be able to flash custom binaries.
If OEM Unlocking is visible (should read "Bootloader is already unlocked"), power off device and start in download mode. Look for KG STATUS: If this says COMPLETED or CHECKING, you should be OK. If it says PRENORMAL or BROKEN, you won't be able to flash custom binaries, and you need to go back to step 1 to ensure Vaultkeeper is disabled.
Flash firmware:
Put device in download mode and leave connected to PC
Start Odin, device should appear: blue box under ID: COM, "Added!" in log
Flash firmware - BL goes in BL slot, AP goes in AP slot, etc. There are two CSC files - CSC and HOME_CSC. CSC is for factory reset, HOME_CSC keeps user data. Keep in mind for future update.
Flash TWRP:
Download TWRP for your device
Put device in download mode
Start Odin and flash TWRP .tar in AP slot
When device reboots, hold Volume Up to start in recovery mode
Disable encryption:
Download Multidisabler, transfer to device, flash in TWRP
Format data (Wipe > Format data > type YES)
Install LineageOS:
With device in TWRP mode and connected to computer, download desired LineageOS image
Note: should be arm64, be aware that some of the bvN/bgN "secure" builds may boot loop. VNDKlite not required. bvS/bgS builds have built in root, just need PHH SuperSU app. bvN/bvS builds do not have Gapps, will need to flash a Gapps package such as MindtheGapps (make sure you select the appropriate version)
Transfer LineageOS image to device storage (MTP should work in TWRP)
Install LineageOS (Install > Select Storage> select storage you uploaded the image to > Install Image > select System (DO NOT flash image to /boot, /recovery, or any other partition)
If necessary, install Gapps
Note: if this fails, you may need to resize /system. After flashing LineageOS, go to Wipe > Advanced Wipe > select System > Repair or Change File System > Resize File System
Reboot to system