Database Develop

Exynos 8890 SM-N935F/DS, TWRP, Root, Encryption, Verizon VoLTE Enabled

Was not comfortable exposing TWRP, Rooted phone without encryption. Averge Joe who knows TWRP can easily get into my phone. I also needed Verizon VoLTE which requires TWRP/Root. hence the research and results of the guide below.
Should applicable equally to S7/S8/N8
All instructions were taken from following threads.
N935F TWRP
S7 Encryption
Verizon CSC VoLTE
S7 CSC Selection
Start with a stock N935F/DS XME CSC and Verizon Sim Card already activated and provisioned for VoLTE
Although N935F/DS does not support CDMA, it does have all verizon LTE, can be used fully with VoLTE enabled
Basic Setup -- enable optional encryption
0. Copy files extracted from TWRP_Root.zip (attached) into SD card. insert SD card with Verizon Sim Card. Download TWRP image from N935F TWRP
1. Ensure RMM is not enabled
-- boot to download mode (vol down+home+power), if "RMM State: Prenormal", then you need keep phone on, connect to internet, wait for 168 hrs
2. If already on Stock ROM then skip to 3 below, otherise
-- Flash via ODIN Stock Rom, in ODIN, turn off auto-reboot, use CSC not HOME_CSC.
-- when finished, push vol. down+home+power until screen turns black
-- right when screen turns black, immediately re-push and hold vol. down+home+power again to get into download mode again
-- this is to avoid reboot the phone and potentially trigger RMM again
3. Flash via ODIN TWRP 3.2.1-0 (turn off auto-reboot) via AP
4. Disconnect USB, hold home+vol. down+power to exist download mode, when screen becomes blank, immediately hold vol.up+home+power to boot to TWRP
5. Install RMM-State_Bypass_Mesa.zip -- to fix RMM first
6. Format data partition
7. Install tweakpro-tima.zip -- to allow encryption
8. Install no-verity-opt-encyrpt-5.1.zip -- to diable verty and disabling enforce encryption. allow to choose encryption or not during initial setup
9. Format data partition !!
11. Reboot and run through setup wizard
-- when asked to "activating device protection features" it is asking if you want to encrypt the phone i.e. the data partition
-- set a PIN/password to enable. TWRP won't be able to read or backup data partition anymore (not possible on samsung devices)
you might still be able to use "adb pull /dev/block/dm-0 /tmp/dm0backup.img" to back up to PC, and use "push" to restore
12. Reboot once, and then reboot to TWRP. verify encryption was enabled a). ask for boot PIN/password b). can not mount data partition in TWRP
13. Install Magisk-v16.0.zip through TWRP.
-- Magisk must be installed AFTER encryption has been enabled via initial setup process.
-- with Magisk installed, data won't be encrypted even if you activate the device protection features during setup
[OEMXME-RMM-ENCRYPT-ROOT-SYS02]
14. reboot to system. Open Magisk Manager, and verify SafteyNet pass
15. download estrong file manager, turn on root access
16. open /system/built.prop to make sure/set
ro.security.vaultkeeper.feature=0
ro.config.tima=0
17. download "CSC feature expert for samsung"
DisableAntiMalware = TRUE
=== Profit, now you have a RMM removed, verity disabled, rooted, encrypted NoteFE===
=== NOTE: if ecryption was enabled, and you need to reset phone or format data partition:
-- once Magisk is installed, data partition will not be encrypted anymore during intial setup
-- if you want to encrypt, need to uninstall Magisk (zip included), setup phone, and install Magisk again
=== Optional - 1 ====
Enable Verizon VoLTE only, without installing US CSC
1. rename /system/csc/customer.xml to customer.xml.bak
2. copy vzw_customer.xml (attached, was extracted from S8 VZW CSC) to /system/csc/customer.xml and set chmod 755 (rw-r-r-)
3. download "CSC Features Expert for Samsung" (these are not neccessary, just good to have)
Message_DisableSmsToMmsConversionByTextInput = TRUE (disable auto convert long sms to mms)
Setting_CustNetworkSelMenu4 = LTEONLY (enable LTE only network mode)
SystemUI_SupportDataUsageViewOnQuickPanel = TRUE (data usage shown in quick panel)
Wifi_SupportAdvancedMenu = TRUE (advanced wifi options)
Wifi_SupportMobileApOnTrigger = TRUE
====== Optional -2 ====
Install US CSC and enable Verizon VoLTE. (it is safe to apply this after applying Option - 1 above "Enable Verizon VoLTE only without installing US CSC"
-- not needed to enable VoLTE, but might be needed to enable WifiCalling. I have not tested
-- this does mess with system files, and deletes all original CSC files under /system/csc and replace with /system/omc structure
-- might lose some dual sim functions, I only found one so far: native phone/contact app does not support dual sim
a). download CSC_selection v1.3.0 from S7 CSC Selection
b). replace updater-script and csc_script.sh with ones attached
c). copy to sd card and flash via TWRP
-- select XAA and XAA, DO NOT select VZW (in VZW CSC many dual sim functions gets messed up)
-- during flash, stay away from CSC tweaks that are related to phones. "Enable LTE only" is safe
d). after finish, DO NOT Reboot yet
e). rename /system/omc/XAA/customer.xml to customer.xml.bak and copy /system/omc/VZW/customer.xml to /system/omc/XAA/customer.xml
f). reboot
==== To upgrade ROM in future if you selected encryption ===
- Flash the latest full stock firmware package but this time use HOME_CSC
- Let it reboot into stock recovery and do the upgrade process.
- It should end up on the secure Startup page asking for your password. No password will work at this point because your data was encrypted in TIMA state "0".
- Reboot to download mode and flash TWRP.
- Reboot to TWRP
- Flash the TIMA prop and verity zips.
- Reboot into to Android (password should work now)
- Let it finish the upgrade.

Tmobile works too
Thanks a lot for the guide. I was able to get TWRP, encryption, Magisk, Xposed (non-systemless), and VoLTE on T-mobile USA working. I used the customer.xml located in "XAA/TMB" folder (located in zip file) from CSC selection 2.50 thread you have linked. I am on Android 7.0. Just wanted to post for those who were interested.
Only thing I changed was to keep the customer.xml file rw- r-- r-- 644 instead of the suggested 755. Don't think it makes a difference.
I did try multiple times to get Systemless Xposed working, but it would always freeze up on the screen with the unlocking icon when booting up. If anyone gets stuck there, just hold Vol Down + Home + Power until phone restarts. Power the device off when you can (will be able to access the power menu on the secure boot password screen). Go back to recovery -> format data -> go through setup process again. After setup is complete, the phone will not have an encrypted /data partition. You have to go back into recovery -> run Magisk uninstaller -> format data -> install tweakpro-tima.zip / no-verity-opt-encyrpt-5.1.zip -> go through setup again. You might be able to run Magisk uninstaller on the first boot to recovery, but I am just posting the process I went through.
If anyone is able to get Systemless Xposed working, please do share. I hate running phones without XPrivacyLua.

So I've hit a snag with this whole process, i waited for 7 days got TWRP installed, rooted and everything,(encryption was not important to me), but attempted option 1 for getting Verizon Volte working with no luck. (things never seem to work the easy way), so i did option 2 with installing the US CSC per the instructions and that went all fine and dandy.. but when I boot up the phone into the system and it ask me to choose the network for my sim it shows 2 options VZW and VZW. When selecting first option it says device needs to reboot to apply features so I click OK and it attempts to reboot but then goes straight into recovery blocking whatever process it was doing. If i select the second VZW it just does nothing. Was curious if any insight or advice can be given on this. I'm in no way at a pro at all this just want to enjoy a Samsung phone with a psychical home button and a none weird screen ratio haha. Thanks and much appreciated ahead of time!

Volte for india
Is it work for india to get the volte option...(where I can get the indian CSC)

Root Samsung P580 Nougat while keeping encryption

Hi,
I couldn't find any information about so I thought i'd share. I wanted Nougat with encryption and root! Finally managed it, probably didn't need all the steps but this is what worked for me after much trial and error.
You can transfer the zips to a SD card beforehand or just use adb sideload within TWRP.
You will have to go to developer options and enable OEM Modifications.
1. Get all the files needed
Magisk-v16.0.zip from XDA Dev Magisk
no-verity-keep-encrypt-6.0.zip This is my own file with the encryption script commented out. I had to open it and edit from the archive and NOT create a new zip as I got verify errors from TWRP
P580UEU1BQK1_P580XAR1BQK1_XAR.zip which I obtained from sam mobile
ODIN
2. Flash Nougat
AP = AP_P580UEU1BQK1_CL12479655_QB15699972_REV00_user_low_ship_meta.tar.md5
BL = BL_P580UEU1BQK1_CL12479655_QB15699972_REV00_user_low_ship.tar.md5
CSC = CSC_XAR_P580XAR1BQK1_CL12479655_QB15699972_REV00_user_low_ship.tar.md5 OR HOME_CSC_XAR_P580XAR1BQK1_CL12479655_QB15699972_REV00_user_low_ship.tar.md5
Let it boot the device.
EDIT
I flashed my phone after but decided not to flash the DM Verity; it is a Samsung A3 2017 so should be the same here. I basically flashed TWRP, then formatted Data, flashed Magisk and followed step 5 below.
3. Flash TWRP Recovery & DM Verity
Boot into download mode by holding down power + volume down + home
Press volume up
In ODIN put TWRP into the AP box and flash - remember to disable auto reboot
Press the download mode key combination and quickly press volume up when screen blacks while holding down the buttons
DO NOT SWIPE TO MAKE MODIFICATIONS
Format DATA
Flash the no verity zip file
Reboot
4. Magisk 16
Reboot to recovery DO NOT SWIPE TO MAKE MODIFICATIONS
Format DATA this might not be needed but I can't confirm
Flash the magisk zip
Format DATA doubt it is needed but this is what I did
Reboot
5. Enable Encrypt and Update Magisk
Encryption will be off, under security it will say Encrypt Device
Open Magisk App
Tick preserve encryption and untick preserve dm-verity
Update Magisk
Install and select direct Install
Reboot and Encryption should be enabled
Hope this helps! Good luck

How to ROOT Samsung Galaxy Tab Active 2 T395 - SOLVED !

First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!

How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.

Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!

I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.

[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)

Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you

oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.

RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew

Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,

Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.

Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.

Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt

Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?

Hello, did you manage to remove the "format as internal" lock?

Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?

alguma fortma?

My steps for a 9.5.4 (as of writing), Root+TWRP and saftynet passing

First there are shortcuts for this, but I wanted to be sure I covered every step and where one is at each point, since it can be helpful for recovery or simply to see where one is. There are of course other ways but I just went through on a GM1917 and verified each of these steps, so that others do not need to piece together multiple threads. I'm assuming here we want to start from scratch, never a bad idea if you are willing to lose data, or else you have no choice and need to start from scratch.
Posts used:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I'm going to disable Encryption as well, because when written TWRP was not decrypting it and also because I find it a pain and simply put I do not need it on my phone, but those steps are optionally shown below, as well as root.
Next I'm doing this using files for the GM1917 (US/Internaltional), but you can replace both the fastboot version and the OTA for your device and the current version.
Before you begin: I'm assuming an unlocked boot loader
Be warned the steps below result in total loss of all DATA on the phone
Time: This takes about 45 minutes to an hour to complete.
I'm assuming you can get to fastboot mode, beyond that your phone can be seriously messed up, but as we are starting from scratch it should be ok.
Boot into Fastboot mode: (Vol- & Vol+ & power)
Use: 9.5.3-GM21AA-OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_aa37bad-FASTBOOT to restore a prestine copy of 9.5.3 to slot A (only writes slot A)
Force it to power off on reboot (Vol+ & Power)
Reboot to fastboot mode (vol- & vol+ & power)
Now you should check which slot are you using with this command "fastboot getvar current-slot"
Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
Now we have TWRP on Slot B and 9.5.3 on Slot A we are on Slot B
If asked to decrypt, if not skip this step: Format Data, Then Internal Storage, Data and cache
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
Reboot -> Select Slot A
Reboot Select Recovery
We now have TWRP on slots A and B. 9.5.3 on Slot A and 9.5.4 on Slot B
Back in TWRP we are now on Slot A:
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
We now have TWRP on slots A and B. 9.5.4 Slots A and B
At this point you can boot up 9.5.4 Stock from Slot A by selecting Reboot System or we can root / disable encryption
To disable encryption (suggested if you do not care as it makes TWRP easier):
Optional: block the ROM from encrypting storage as we can not currently decrypt.
upload the zip: adb push Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip /cache
- Install -> /cache -> Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Note: this only affects the current slot (A in this case) which is fine
Reboot->System
At this point you have 9.5.4 Stock without Encryption on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B.
Complete inital setup (I do the minimal at this point)
- Set a password, to verify if Dm-Verity_ForceEncrypt is working or not
Enable Developers Options
Enable Advanced Reboot in Developers Options
Note: My suggestion is to now power off and restart to ensure you have Wifi, as this is picky for some reason, and it is best to be sure.
Power -> Off
Power back on and verify that Wifi is still working, it should be.
If you want root:
Power -> Recovery
Upload Magisk: adb push Magisk-v19.2.zip /cache
- Install -> /cache -> Magisk-v19.2.zip
Wipe Dalvik
Reboot System
Finally: Verify that Safenet is passing in Magisk, it should be
You have 9.5.4 Stock with Encryption and Root on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B. I hope having this in one place can help others, as I've tried to lay out exactly what I did each step of the way.
Parting suggestion: Maybe a good time to create a backup, one with EFS and Modem to just to be safe!
ERIC

I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks

reaper000 said:
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
Click to expand...
Click to collapse
I'm using A pattern, and fingerprint without issues. on 9.5.3 and 9.5.4.
ERIC

trying to use this guide and getting fastboot: unrecognised option `--set-active=b'

reaper000 said:
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
Click to expand...
Click to collapse
I saw o xXx Telegram that you can decrypt 7 Pro and also have lock screen security...

I too can confirm working lockscreen while remaining decrypted. Much appreciation to the OP!
Though I took a few shortcuts and used an otg USB drive, it still worked. Here's what I did:
(keep in mind that I am on 9.5.3, already had an unlocked bootloader, and had already used a patched boot.img that I injected via fastboot to achieve root)
To decrypt:
- downloaded dm_verity disable zip, magisk 19.2, and TWRP installer zip, and copied them to USB drive. Also, backup internal storage.
- used Magisk manager app to flash TWRP installer and Magisk 19.2
- reboot to recovery
- formatted internal storage (type yes, completely formatted the data partition and lost all media, photos, downloads, etc)
- twrp factory reset
- flashed dm-verity disabler zip and magisk 19.2 from otg USB drive
- reboot to system
Complete initial setup, repopulate internal storage with mefia (mp3, downloads, etc) from backup.
To upgrade to 9.5.4 once decrypted:
- download full 9.5.4 zip
- reboot to TWRP
- flash 9.5.4 zip and TWRP installer
- reboot to TWRP
- flash dm_verity disable zip and Magisk
- wipe dalvik
- reboot to system
Life is so much better decrypted.

earthbend said:
trying to use this guide and getting fastboot: unrecognised option `--set-active=b'
Click to expand...
Click to collapse
Need a newer version of fastboot this that case.

reaper000 said:
I too can confirm working lockscreen while remaining decrypted. Much appreciation to the OP!
Though I took a few shortcuts and used an otg USB drive, it still worked. Here's what I did:
(keep in mind that I am on 9.5.3, already had an unlocked bootloader, and had already used a patched boot.img that I injected via fastboot to achieve root)
To decrypt:
- downloaded dm_verity disable zip, magisk 19.2, and TWRP installer zip, and copied them to USB drive. Also, backup internal storage.
- used Magisk manager app to flash TWRP installer and Magisk 19.2
- reboot to recovery
- formatted internal storage (type yes, completely formatted the data partition and lost all media, photos, downloads, etc)
- twrp factory reset
- flashed dm-verity disabler zip and magisk 19.2 from otg USB drive
- reboot to system
Complete initial setup, repopulate internal storage with mefia (mp3, downloads, etc) from backup.
To upgrade to 9.5.4 once decrypted:
- download full 9.5.4 zip
- reboot to TWRP
- flash 9.5.4 zip and TWRP installer
- reboot to TWRP
- flash dm_verity disable zip and Magisk
- wipe dalvik
- reboot to system
Life is so much better decrypted.
Click to expand...
Click to collapse
I have tried your steps, but failed to decrypt the data partition.
I also tried different ways to flash:
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip
* Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
but all failed.
My 1+7 Pro is GM1910.
Decryption is quite easy on my OnePlus 5T. Could you help me with some hint?

tinyfish said:
I have tried your steps, but failed to decrypt the data partition.
I also tried different ways to flash:
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip
* Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
but all failed.
My 1+7 Pro is GM1910.
Decryption is quite easy on my OnePlus 5T. Could you help me with some hint?
Click to expand...
Click to collapse
I suppose "decrypt" is actually a misnomer.
The more accurate description is "disable forced encryption on initial and subsequent boots".
You aren't actually decrypting your current data partition, you're preventing a BLANK data partition from being encrypted upon initial boot of a virgin operating system.
The reason I'm saying all this is the most common reason for the no_verity disable zip to fail is because users have not done a factory reset AND not formatted their internal storage (you have to type the word "yes" or you haven't done it) before flashing no_verity and magisk.
Also ensure your no_verity disabler zip wasn't a bad download (md5 checksum)
If this doesn't work, then you're left with what I've termed a "scorched earth format" (you select everything except usb drive to wipe in advanced wipe, and then format internal storage with a typed yes). You then install FROM A USB DRIVE the latest full ota zip + twrp on both slots with the appropriate twrp reboots, then magisk + no_verity, twrp reboot then magisk yet again and finally system reboot.

reaper000 said:
I suppose "decrypt" is actually a misnomer.
The more accurate description is "disable forced encryption on initial and subsequent boots".
You aren't actually decrypting your current data partition, you're preventing a BLANK data partition from being encrypted upon initial boot of a virgin operating system.
The reason I'm saying all this is the most common reason for the no_verity disable zip to fail is because users have not done a factory reset AND not formatted their internal storage (you have to type the word "yes" or you haven't done it) before flashing no_verity and magisk.
Also ensure your no_verity disabler zip wasn't a bad download (md5 checksum)
If this doesn't work, then you're left with what I've termed a "scorched earth format" (you select everything except usb drive to wipe in advanced wipe, and then format internal storage with a typed yes). You then install FROM A USB DRIVE the latest full ota zip + twrp on both slots with the appropriate twrp reboots, then magisk + no_verity, twrp reboot then magisk yet again and finally system reboot.
Click to expand...
Click to collapse
I have formatted the data partition, and the Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip is valid.
Anyway I succeeded after upgrade to latest H2OS 9.5.5, with the same steps.
Thanks for your help.

Time-Saver!
QUOTE=egandt;79606005]First there are shortcuts for this, but I wanted to be sure I covered every step and where one is at each point, since it can be helpful for recovery or simply to see where one is. There are of course other ways but I just went through on a GM1917 and verified each of these steps, so that others do not need to piece together multiple threads. I'm assuming here we want to start from scratch, never a bad idea if you are willing to lose data, or else you have no choice and need to start from scratch.
Posts used:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I'm going to disable Encryption as well, because when written TWRP was not decrypting it and also because I find it a pain and simply put I do not need it on my phone, but those steps are optionally shown below, as well as root.
Next I'm doing this using files for the GM1917 (US/Internaltional), but you can replace both the fastboot version and the OTA for your device and the current version.
Before you begin: I'm assuming an unlocked boot loader
Be warned the steps below result in total loss of all DATA on the phone
Time: This takes about 45 minutes to an hour to complete.
I'm assuming you can get to fastboot mode, beyond that your phone can be seriously messed up, but as we are starting from scratch it should be ok.
Boot into Fastboot mode: (Vol- & Vol+ & power)
Use: 9.5.3-GM21AA-OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_aa37bad-FASTBOOT to restore a prestine copy of 9.5.3 to slot A (only writes slot A)
Force it to power off on reboot (Vol+ & Power)
Reboot to fastboot mode (vol- & vol+ & power)
Now you should check which slot are you using with this command "fastboot getvar current-slot"
Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
Now we have TWRP on Slot B and 9.5.3 on Slot A we are on Slot B
If asked to decrypt, if not skip this step: Format Data, Then Internal Storage, Data and cache
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
Reboot -> Select Slot A
Reboot Select Recovery
We now have TWRP on slots A and B. 9.5.3 on Slot A and 9.5.4 on Slot B
Back in TWRP we are now on Slot A:
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
We now have TWRP on slots A and B. 9.5.4 Slots A and B
At this point you can boot up 9.5.4 Stock from Slot A by selecting Reboot System or we can root / disable encryption
To disable encryption (suggested if you do not care as it makes TWRP easier):
Optional: block the ROM from encrypting storage as we can not currently decrypt.
upload the zip: adb push Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip /cache
- Install -> /cache -> Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Note: this only affects the current slot (A in this case) which is fine
Reboot->System
At this point you have 9.5.4 Stock without Encryption on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B.
Complete inital setup (I do the minimal at this point)
- Set a password, to verify if Dm-Verity_ForceEncrypt is working or not
Enable Developers Options
Enable Advanced Reboot in Developers Options
Note: My suggestion is to now power off and restart to ensure you have Wifi, as this is picky for some reason, and it is best to be sure.
Power -> Off
Power back on and verify that Wifi is still working, it should be.
If you want root:
Power -> Recovery
Upload Magisk: adb push Magisk-v19.2.zip /cache
- Install -> /cache -> Magisk-v19.2.zip
Wipe Dalvik
Reboot System
Finally: Verify that Safenet is passing in Magisk, it should be
You have 9.5.4 Stock with Encryption and Root on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B. I hope having this in one place can help others, as I've tried to lay out exactly what I did each step of the way.
Parting suggestion: Maybe a good time to create a backup, one with EFS and Modem to just to be safe!
ERIC[/QUOTE]
Hello @tinyfish
Just dropping a note to thank you for the procedure. I wanted to achieve the same thing and I have been doing so through my own trial-and-error (and I'm actually documenting my steps as I go with the same intention of sharing to the community).
Apparently someone already beat me to it and I even used this written procedure. It worked for me. Although there are a few "differences" in the way I did it:
1. Instead of OOS version 9.5.4 I used OOS version 9.5.13 which is the latest Android Pie for the OnePlus 7 Pro as of this writing.
2. I used the latest version of the "DM-Verity and Forced Encrypt Disabler" zip which is version 10.20.2019 as of this writing. The older version didn't work and resulted to "Settings" app force-closing and thereby preventing me from booting. I didn't investigate but I assume that the reason is because the 05.21.2019 version is "older" than the OOS version 9.5.13 that I was flashing. I could be wrong. But it is important that I write it here so that it is made known and investigated by someone who has the time/knowledge/energy for it.
There are certain important apps that I use that couldn't run properly on Android 10, so I had to revert to Android 9 (Pie).
Thank you once again!

Any magisk module that can make sd card as adopted storage on Android 10?

Did google remove the option of adopted storage? I don't see it on my SM-T295. I rooted it so I was wondering if there is a Magisk Module that can make sd card act like adopted storage.
Thank you.

Can you tell how did you root your tab please.

Dharmtej said:
Can you tell how did you root your tab please.
Click to expand...
Click to collapse
I have tried many methods dude
Before Installing Magisk​
Installing Magisk WILL trip KNOX
Installing Magisk for the first time REQUIRES a full data wipe (this is NOT counting the data wipe when unlocking bootloader). Backup your data before continue.
Download Odin (only runs on Windows) that supports your device.
Unlocking Bootloader​Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Instructions​
Use either samfirm.js, Frija, or Samloader to download the latest firmware zip of your device directly from Samsung servers.
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
Reboot to download mode. Open Odin on your PC, and flash magisk_patched.tar as AP, together with BL, CP, and CSC (NOT HOME_CSC because we want to wipe data) from the original firmware.
Your device should reboot automatically once Odin finished flashing. Agree to do a factory reset if asked.
If your device does NOT have boot ramdisk, reboot to recovery now to enable Magisk (reason stated in Magisk in Recovery).
Install the Magisk app you’ve already downloaded and launch the app. It should show a dialog asking for additional setup.
Let the app do its job and automatically reboot the device. Voila!
I have tried this one
I have tried flashing unofficial twrp
unofficial twrp 3.4.0 Root Samsung SM-T295 - unofficial twrp
download twrp 3.4.0 root Samsung SM-T295, user who own Samsung SM-T295 can root it by following the below instructions
unofficialtwrp.com
Can you help me please ?