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

s7 edge G935F with FRP lock & DRK error

hi, I flashed the latest stock ROM of s7 edge from sammobile ( G935FXXS8ETC1 ) then I had dm-verity error / the developer options off / FRP on and I can't do anything I cant flash TWRP I can't flash any unofficial files ...... help, please !!!!!

leonardo8877 said:
hi, I flashed the latest stock ROM of s7 edge from sammobile ( G935FXXS8ETC1 ) then I had dm-verity error / the developer options off / FRP on and I can't do anything I cant flash TWRP I can't flash any unofficial files ...... help, please !!!!!
Click to expand...
Click to collapse
Xda's search bar is your best friend mate, be sure to use it before posting
Sent from my hero2lte using XDA Labs

1. Download a U8 firmware for your device which is SM-G935F. You can download it in sammobile.com , updato.com or samfw.com
2. After the download is completed, you need to extract the downloaded rom (I recommend using apps like 7zip or Winrar)
7-zip: https://www.7-zip.org/download.html
3. After you extract the file, you will be greeted with files saying
AP_XXXXXXXXXXX
BL_XXXXXXXXXXX
CP_XXXXXXXXXXX
CSC_XXXXXXXXXX
Home_CSC_XXXXXXXXX
4. Extract the AP_XXXXXXXXX with 7-zip or Winrar
5. In my case, 3 files and 1 folder were extracted which were
system.img.lz4
boot.img.lz4
recovery.img.lz4
meta-data (This is a folder)
Note: In your case, there might be different amount of files with different extensions
6. Copy "boot.img.lz4" to another folder (lets call the folder Hello for now) and rename the boot.img.lz4 to "recovery.img.lz4"
7. Make a backup of the original "recovery.img.lz4" and "boot.img.lz4" and "meta-data" and delete those files/folders
8. Copy the "recovery.img.lz4" file from Hello to your folder which contains system.img.lz4
9. Now, your folder should only contain system.img.lz4 and recovery.img.lz4 (renamed boot.img.lz4)
10. Download the Auto Tar folder
https://www.mediafire.com/file/ah20h...s.com.rar/file
11. Extract the autotar file using 7-zip or winrar
12. Copy all the content inside the autotar file and paste it to your folder containing system.img.lz4 & recovery.img.lz4 (renamed boot.img.lz4)
13. Open the Autotar application
14. Select system.lz4.img and recovery.img.lz4
15. Press on make .md5 & type the name on the box beside select files
Note: There should not be any special characters in the name, I recommend not using any spaces, numbers, capital letters or special characters like [email protected]#
16. Then, wait until it says done, usually took us around 15 Minutes
17. Open Odin, if you dont have odin download it
https://odindownload.com/download/#.Xq6i9pnBXDc
18. In Ap tab, choose the newly created .md5 file and do the same for CSC, CP & BL
19. Connect your phone to the PC in download mode
20 Then, flash
Note: If the verification fails, rename the newly created .tar.md5 file and remove .md5 from its name, then we will be left with .tar file
21. Set up your phone and before switching off/ restarting or doing anything "Special" enable OEM unlock, or charge your phone if it has less battery, which was the issue in my case
22. Restart your phone and you will be greeted with No Command screen. The first time I saw that again, I got freaked out but dont worry the solution is pretty simple due to the fact we dont have FRP lock anymore
23. Go to download mode and flash UNMODIFIED CP, CSC, AP & BL
24. You will get the no command screen again, no worries though, go to TWRPP websiet and download TWRP for your device
https://twrp.me/
25. Enter download mode and flash the recovery through the AP tab
26. Download this
https://zackptg5.com/downloads/Disab...03.04.2020.zip
27. You will be rebooted to the TWRP screen. And by the way, ALLOW SYSTEM MODIFICATIONS
28. Connect your phone to the PC and transfer the previously downloaded Dm verity file and copy it to your phone
29. Go to Install in your TWRP screen and locate the file and install it
30. Clear Dalvik Cache and reboot
Edit: Alternatively, In the last steps, you can flash turbo luke's twrp instead of official twrp, then select format option in twrp wipe, then flash no-verity-force-encrypt
Then flash magisk from here : https://github.com/topjohnwu/Magisk/releases/tag/v20.4
In all of doing this, don't swipe for system modifications in twrp, it is basically useless and obsolete now, as magisk does everything without modifying system.
Ofcourse, this only applies to stock rooted rom and stock based debloated custom roms (which have non-modified system)
Edit 2: This a copy pasta
Credit: @turbolukex5 @shah22
Sources:
https://forum.xda-developers.com/s7-edge/help/bricked-s7-edge-t4039153
https://forum.xda-developers.com/s7-edge/help/rip-s7-edge-g935fd-one-help-t4082203
https://forum.xda-developers.com/s7-edge/development/recovery-upstreamed-twrp-android-8-1-t3921785

but frp is on how can i flash twrp @Rapidfayaround

leonardo8877 said:
but frp is on how can i flash twrp @Rapidfayaround
Click to expand...
Click to collapse
Bruh....Did you read that properly. First flash the modified AP, then you will boot then enable OEM Unlock which will disable FRP Lock, then you can flash TWRP. Or just tell me the CSC for your country, I will do all this and send you the modified AP.

Have the same problem with G935FXXS8ETC1
Rapidfayaround said:
Bruh....Did you read that properly. First flash the modified AP, then you will boot then enable OEM Unlock which will disable FRP Lock, then you can flash TWRP. Or just tell me the CSC for your country, I will do all this and send you the modified AP.
Click to expand...
Click to collapse
Hallo, i have the same problem after i disabled develeper options after root(G935FXXS8ETC1)
My country code is DBT, can you send me please the modded AP File. Thanks.

Autotar application dont works for me
I have done all steps but autotar does not work for me. There is no output. Only 1kb in MD5.
That can not work.

Fixed your problem ?
leonardo8877 said:
hi, I flashed the latest stock ROM of s7 edge from sammobile ( G935FXXS8ETC1 ) then I had dm-verity error / the developer options off / FRP on and I can't do anything I cant flash TWRP I can't flash any unofficial files ...... help, please !!!!!
Click to expand...
Click to collapse
I tried to convert the img,lz4 file with auto tar . No chance. Next time i will try to flash a combination rom.
Perhaps this will solve my oem unlock problem. i can not aktivate it, thats the main problem. I waited 7 Days, but oem unlock ist still not possible.:crying:
I have the same problem. FRP ON, no twrp or custom rom. OEM can not be unlocked to flash twrp.
DId you have success in any way?
LG

@chris1abc download 7zip from this link: https://www.7-zip.org/download.html after installing it on your pc select two files system and recovery ( renamed boot ) file then select 7zip like the photo below then select open archive then choose the file type and make it tar.
images link: https://drive.google.com/open?id=1rxbY-Ytxsb1yzcQ4io5yZE6gJHoTRQP_

leonardo8877 said:
@chris1abc download 7zip from this link: https://www.7-zip.org/download.html after installing it on your pc select two files system and recovery ( renamed boot ) file then select 7zip like the photo below then select open archive then choose the file type and make it tar.
images link: https://drive.google.com/open?id=1rxbY-Ytxsb1yzcQ4io5yZE6gJHoTRQP_
Click to expand...
Click to collapse
Thanks, i managed to convert the files. Still on stock rom. I had no sucess, flashed the files in different ways.
BL CP HOMESCS; only ap etc. etc.... I spendend many hours but sometimes the phone did not boot,when it booted I was not able to unlock oem in developer options.
I will wait new 7 days, perhaps i have luck. Grrrrrr....... **** Samsung I WANT MY TWRP BACK. With Samsung S5 i had not this trouble.
Cause of this i will not buy any Samsung products neither Tv or anything else. SAMSUNG WANTS TO FORBID THE PEOPLE TO ROOT AND FLASH THEIR PHONES.
Hey, I am over 18.
s7,s8, S9,s10, S20 the people get often problems to root their phones. Will see what happens after 7 days.

chris1abc said:
Thanks, i managed to convert the files. Still on stock rom. I had no sucess, flashed the files in different ways.
BL CP HOMESCS; only ap etc. etc.... I spendend many hours but sometimes the phone did not boot,when it booted I was not able to unlock oem in developer options.
I will wait new 7 days, perhaps i have luck. Grrrrrr....... **** Samsung I WANT MY TWRP BACK. With Samsung S5 i had not this trouble.
Cause of this i will not buy any Samsung products neither Tv or anything else. SAMSUNG WANTS TO FORBID THE PEOPLE TO ROOT AND FLASH THEIR PHONES.
Hey, I am over 18.
s7,s8, S9,s10, S20 the people get often problems to root their phones. Will see what happens after 7 days.
Click to expand...
Click to collapse
Still not getting what your problem is mate .. you can boot but not enable oem unlock in developer option ?? This isn't possible ..
Sent from my hero2lte using XDA Labs

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shah22 said:
Still not getting what your problem is mate .. you can boot but not enable oem unlock in developer option ?? This isn't possible ..
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
yes, that is my problem. I was able to install the modified AP and flashed it how you described it. In developer option i can toggle the button,
cause it went back. This problem stays with the modified AP ROM and also on unmodified stock rom.
There is no green light . It just goes back. MY Status is FRP LOCK on while staying on stock rom or AP modified rom. I have no google frp lock only by Samsung.
Odin picture is only for example what i did (removed you see), i must use my s7 edge to take the picture.
AP FILE was flashed with 3 Files:
recovery.img + (renamed boot.img)+ system.img. + boot.img. converted in one AP FILE
with BL CP SCSHOME in Odin. The phone booted now in system, but in dev.options the oem button can be actived but it struggles back. That´s the fact.

chris1abc said:
yes, that is my problem. I was able to install the modified AP and flashed it how you described it. In developer option i can toggle the button,
cause it went back. This problem stays with the modified AP ROM and also on unmodified stock rom.
There is no green light . It just goes back. MY Status is FRP LOCK on while staying on stock rom. I have no google frp lock only by Samsung.
Click to expand...
Click to collapse
You mean when you enable the toggle, it automatically gets off ??
This is weird indeed, first time seeing this..
Did you bought your phone second hand ? It maybe that its hardware is semi modified ..
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
You mean when you enable the toggle, it automatically gets off ??
This is weird indeed, first time seeing this..
Did you bought your phone second hand ? It maybe that its hardware is semi modified ..
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Yes, i bought it second hand , but the people did not modiefie the phone. It had stock rom an KNOX 0+0.
The oem toggle did not go back before I installed TWRP and moro Kernel. Do you know if its possible that oem unlock will not go back automically after waiting for 7 days ?

chris1abc said:
Yes, i bought it second hand , but the people did not modiefie the phone. It had stock rom an KNOX 0+0.
The oem toggle did not go back before I installed TWRP and moro Kernel. Do you know if its possible that oem unlock will not go back automically after waiting for 7 days ?
Click to expand...
Click to collapse
Can't be sure, RMM lock is not implemented on S7 series per my knowledge, but yeah you can try waiting..
Also confirm that your oem unlock toggle automatically turns off when enabled ??
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Can't be sure, RMM lock is not implemented on S7 series per my knowledge, but yeah you can try waiting..
Also confirm that your oem unlock toggle automatically turns off when enabled ??
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
Yes the unlock toggle automatically turns off when enabled . I succsefully flashed AP Rom and also Stock Rom. In both cases the phone boots normally, but there is the problem
with the toggle. Its a pity for the work and lot of tries.

Its the first time im coming across this issue .. don't know then, i tested this solution on many people and it always worked .. you sure your phone isn't a hardware semi-modified snapdragon variant to show itself as a exynos one ? That could make sense why the toggle can't be enabled but still its really weird ..
Sent from my hero2lte using XDA Labs

i have never heared about a semi modified snapdragon. On cpuz or ohter apps it shows me exynos . The last try is too flash the ap file with the meta folder, that i did not tried. Perhaps i mayed a fault while flashing or converting, i dont know. But the phone starts with the modified ap file, but how i said, i was not able to turn oem on.
Next time i will start another try with flashing meta folder in ap file. Perhaps i have luck.
No chance, i installed ap with meta folder. Phone booting in system , oem unlock not possible.

shah22 said:
Its the first time im coming across this issue .. don't know then, i tested this solution on many people and it always worked .. you sure your phone isn't a hardware semi-modified snapdragon variant to show itself as a exynos one ? That could make sense why the toggle can't be enabled but still its really weird ..
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
i have checked with phone info and samsung imei the phone is 100% original.

Oem unlock not possible, still on stock rom 8.
chris1abc said:
i have checked with phone info and samsung imei the phone is 100% original.
Click to expand...
Click to collapse
SM- G935F EXYNOS 8890
After trying a last flash with nand erase and repartion with stock rom binary 8 , the problem still is not solved.
Download mode shows FRP on. Status official.
FRP Lock for hardware is still alive. I normally can sign in to my google account with my device.
The phone boots normally but in dev. options, the oem button automatically goes back. I am not able to solve the problem.
Stock rom works,but no way to flash TWRP cause custom binary blocked by FRP. Its possible to flash different stock roms with binary 8, all is working except s- health.
(notice: phone is rooted, but root has gone). I have no chance to flash a rom below binary 8.
History: I installed TWRP with moro Kernel on Stock rom. All works, after accidentally i disabled the dev. options i got the dead android and i was not able to go back in TWRP
recovery. Twrp had disappeared.
When i start the revovery the "dead android no command" appears and after 1 minute the stock recovery appears.
I read ( Google research) , there was a user who had the same problem with a s7 g930f. He could flash stock roms but no other and he also could not unlock oem in any
rom.
I would be happy to hear from somebody who had a solution. I think there is a new security patch by samsung. Meanwhile i stay on latest stock rom and hope sometime i can unlock oem in dev. options. I have tried all incl. flash with Nand Erase in Odin ( you should not do this, i heard), but nothing worked for me.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.)

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note 20 & Note 20 Ultra Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 Ultra​Only for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu

Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection

FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards

well done sir

Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!

edsoedso said:
Hello! I have a rooted sm-n980f exynos European version. I rooted my phone using magisk patched AP file through odin. I am trying to flash twrp 3.6.1 above and vbmeta.tar using odin but it fails. What shall I do? Thank you!
Click to expand...
Click to collapse
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards

corsicanu said:
Can you attach a screenshot of Odin and eventually tell me if you see anything in particular changing on phone screen? It should throw an error or something below the usual download mode lines. A pic of phone screen would be nice but i'd assume it's your only phone..
Regards
Click to expand...
Click to collapse
Nothing changes in the screen phone. Attached is odin screen. Thank you!

edsoedso said:
Nothing changes in the screen phone. Attached is odin screen. Thank you!
Click to expand...
Click to collapse
Can you please check Kg state line from download mode? What's written there?

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
I installed twrp but it seems that it does not read the internal storage.

corsicanu said:
Can you please check Kg state line from download mode? What's written there?
Click to expand...
Click to collapse
And how to flash the multidisabler? it seems that everything is encrypted and is impossible to locate it in twrp?

I found it!
1. enter into TWRP (after flashing twrp.tar and Vbmeta.tar via odin), format data and reboot again in TWRP
2. Being in TWRP, transfer from PC to your phone multidisabler.zip and magisk zip.
3. flash them both
4. reboot system
That is all!

i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system

Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?

m7mdo_93 said:
i have note 20 5G N918B , i make every thing but my mobile keep restarting in to TWRP recovery , not going to system
Click to expand...
Click to collapse
edsoedso said:
Hello! What can be done to remove encryption from TWRP? I have flashed disabler but it still continues to encrypt. I tried formatting data from twrp, changing file system to EXT4 and back to EXT2 but with no result so far. any help?
Click to expand...
Click to collapse
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
yeah , after flashing multidisabler second time my mobile able to working .. thanks for your help

corsicanu said:
I'm still trying to find the issue, for whatever reason multidisabler needs a second flash to work as far as i seen on my device. So for now please flash multidisabler 2 times in a row, until i find a better solution to this.
Regards
Click to expand...
Click to collapse
Thank You very much. It worked!

A big thank you, it works fine.

hey.
i did everything from this guide, and i got root access+twrp installed.
the problem that i am facing, is that i canot install anything from twrp, due to insufficient space.
the system size that twrp is reading is only 8384kb, so every installation of gapps is failed.
i tried to wipe ,format data, and changing the file system, but nothing helped.
please give me an idea how to solve it.
thanks.

Good day
Does this work for Android 13 One UI 5.1?