Database Develop

[ROOT][BOOTLOADER][RECOVERY][STOCK][ SCH-I705 ] ROOT Verizon Galaxy Tab 2 7.0 LTE

How to root VZW Galaxy Tab 2 7.0 LTE
RECOMMENDED METHOD
07/09/2014
Working root method by geohot. This is now the recommended method!
http://forum.xda-developers.com/showthread.php?t=2783157
CAN ALSO WORK ON VRBMI1
It has been said the following root method: saferoot
Has been able to root VRBMI1. Give this a try before using the system image below.​
****
!!!!WARNING!!!!
Many of you have been complaining about broken wifi and other issues.
I do not own this tablet anymore, which means I can no longer support it.
Verizon/Samusung released a new update: VRBMI1
Check your firmware version
THE LAST VERSION SUPPORTED BY THIS GUIDE IS VRBLL2.
IF VERIZON/SAMSUNG CHANGED THE KEYS THEY SIGN THEIR FIRMWARE WITH, THAN ANY ATTEMPT TO DOWNGRADE/UNLOCK MAY POTENTIALLY BRICK YOUR DEVICE.
This has been seen on the VZW Galaxy S4 and just recently the VZW Galaxy S3 (The VZW Tab 2 is a clone of the S3!)
If you are on the latest build (VRBMI1), then it is entirely possible things will not work. It is also possible the bootloader unlock may brick your device.
If the root method doesn't work, flash a stock odin tar for VRBLL2.
AGAIN... IF VERIZON/SAMSUNG CHANGED THEIR KEYS, YOU MAY BRICK!
If you are on VRBMI1 and have semi-bricked using this method, flash this stock ODIN image using ODIN 3.04.
DO NOT CHECK RE-PARTITION, FLASH LOCK, OR LED CONTROL
VRBMI1
http://-/android/SCH-I705/ROMs/4.1.2/HOME_I705VRBMI1_1415457_REV02_user_low_ship.tar.md5
The above information is unknown to me. Do all at your own risk!
YOU HAVE BEEN WARNED​****
READ FIRST
*** *** *** *** Disclaimer *** *** *** ***
I am not responsible if you break your stuff. READ READ READ
If you DO NOT own a VERIZON Galaxy Tab 2 7.0 SCH-I705 then DO NOT flash this! If you have not verified and flash this on a p3xxx tab, something will break and I will not help you!​
Table of Contents
Step 1: Root
Step 2: Bootloader
Step 3: Recovery
OPTIONAL: Return to Stock​
YOU MUST DO ALL STEPS IN ORDER 1-3
This will probably trip your flash counter!
Step 1 - root Make sure to READ! Select the correct method below.
Root ICS 4.0.4 - Use if you are on STOCK Ice Cream Sandwich ONLY
This is a pre-rooted J1 base system image. It has all the latest updates from Verizon.
*Pre-requisites*
A. Reboot into stock recovery and data wipe / factory reset.
B. Reboot directly into Download Mode.
*Flash Pre-Rooted System Image*
1. Install Samsung drivers for SCH-I705 - Download Here
2. Download stock rooted 7zip archive and extract ODIN image sch-i705_4.0.4_VRLJ1_prerooted_ODIN.7z
3. Open ODIN ODIN 3.04
4. Select the system.ext4.tar.md5 file in the PDA section, uncheck f. Reset time
5. Press START. This process can up to 10 minutes. DO NOT UNPLUG YOUR TAB!!! Reboot.
6. Press the Thanks button
7. Go to Step 2​
Root JB 4.1.2 - Use if you are on STOCK Jellybean ONLY
This is a pre-rooted VRBLL2 base Jellybean system image. It has all the latest updates from Verizon.
*Pre-requisites*
A. Reboot into stock recovery and data wipe / factory reset.
B. Reboot directly into Download Mode.
*Flash Pre-Rooted System Image*
1. Install Samsung drivers for SCH-I705 - Download Here
2. Download stock rooted 7zip archive and extract ODIN image jellybean-4.1.2-rooted_sch-i705.tar.md5-COMPRESSED.7z Just extract it
3. Open ODIN ODIN 3.04
4. Select the jellybean-4.1.2-rooted_sch-i705.tar.md5 file in the PDA section, uncheck f. Reset time
5. Press START. This process can up to 10 minutes. DO NOT UNPLUG YOUR TAB!!! Reboot.
6. Press the Thanks button!!
7. Go to Step 2​Step 2 - Bootloader
Unlock Bootloader
Unlock your bootloader
How to UNLOCK VZW Galaxy Tab 2 7.0 bootloader
Go to Step 3
​Step 3 - Recovery
Custom Recovery
Flash CWM recovery OR TWRP recovery
How to flash unofficial ClockworkMod
How to flash unofficial TWRP​
Once you got custom, NEVER accept an OTA!
Return to Stock
Download stock firmware, ODIN flashable. Extract .md5 from the .zip file. DO NOT EXTRACT ANYTHING OUT FROM THE .md5!
I705VRBLL2_I705VZWBLL2_VZW.zip
Reboot into DOWNLOAD mode.
Connect Device.
Open ODIN, select the .md5 in the PDA section. The ONLY checkboxes that should be checked are Reset Time and Auto Reboot.
Press START and WAIT! DO NOT UNPLUG DEVICE. IT WILL REBOOT ON IT'S OWN!
You are now stock.
​
Original root method for VRALG3 (original factory firmware) was achieved using RootDebugFS.bat
Thanks to
miloj
Noxious Ninja
sparkym3
joYstick61
Ezgoing2406
Scrosler​

Good job man. I hope the vtab gets its own development subforum here. Xda has a request thread for new threads for new devices. All of you with these new tabs should go post in it.
Edit: this is the thread. http://forum.xda-developers.com/showthread.php?t=1660354
I posted in it in hopes of getting it done. Good luck vtabbers

THIS WORKED!
Just wanted to post in this thread too... so ppl know that this method works...
Thanks again MrHyde
Nexttonomy

Thanks for the tip Scottx. Posted there as well and you're welcome nextonomy!

Root Fail SCH-i705 Galaxy 2 Vzn LTE 7.0
cant figure out why this isnt working... could someone give a little more detail about why? followed every step to the letter.
Thanks in Advance

leakim13 said:
cant figure out why this isnt working... could someone give a little more detail about why? followed every step to the letter.
Thanks in Advance
Click to expand...
Click to collapse
Are other apps such as TB, Terminal, or AdFree Android able to gain root privileges? If so, then Busybox Installer may have been denied. Check Superuser and remove it from the Denied list if it's there. After removing it, try again and make sure to tap "Allow" when it asks.
EDIT: Downloaded that app to test. SU asked if I wanted to grant SU permissions, tapped 'Grant'. All is fine. If it's NOT in the SU denied list, Force Close the app. Reopen it and it should ask.

This is awesome. Thanks! One thing - is there a way to stop the OTA update nag?

Xer0daze said:
This is awesome. Thanks! One thing - is there a way to stop the OTA update nag?
Click to expand...
Click to collapse
Do this
MrHyde03 said:
Yes, using titanium you can freeze SDM.
Green icon with a phone and up arrow. Freeze or uninstall with titanium and verizon won't know what hit em.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse

Yes, using titanium backup freeze or remove SDM
Sent from my SCH-I535 using xda app-developers app

Thanks, I did that. I also noticed in system/app there were SDM.apk and SDM.odix. I went ahead an renamed them SDM.apk.bak and SDM.odix.bak. I'm hoping this will get rid of the nag notification. One last thing - the update tried to run overnight once but CWM stopped it. When I woke up the tab was sitting on the CWM screen. Since then every time I reboot the tab it acts as if dalvik cache was cleared (I get the "android is upgrading - optimizing applications" screen before the tab loads). I think OTA set a reboot/clear cache flag somewhere I need to clear, but I don't know where that is set. Any ideas? Thanks again.

That will get rid of it. As for the reboot issue, have you tried clearing cache? Or even a factory reset? Factory reset won't hurt your root any nor restore the update app.

Thanks for the reply - Yep. I factory reset a couple days ago and made the update changes mentioned earlier. I no longer get the OTA notifications (YAY), but every time I restart the device it still rebuilds cache. I've formatted the cache partition, cleared dalvik cache, and as I mentioned, I tried a factory reset as well. This is the only hurdle I have left to clear. Out of curiosity, why are there no custom roms for the VZW version of this device? The VZW version doesn't carry the same model numbers as the retail models (GT-Pxxxx). The verizon device is simply SCH-I705 - there don't seem to be any roms for that. Isn't the only real difference the radio? I've asked around the forums, but not gotten a reply from anyone on this. I'd love to try some custom roms on this tab, and I'm sure that would fix the majority of my issues, but I have yet to find one.

There is actually a big difference between the wifi and lte devices. The i705 is closer related to the i535 (gs3) than it is the wifi tab 2's. And there are no custom ROMs yet becuase there are so few of us that own it, and even fewer (two of us actually..) who are trying to get anything done on it. I'm a novice developer so I'm still learning the process of ROM development. On top of that, I'm very busy working two jobs, saving up for a wedding. Unless someone else is capable of getting more development done we may only have 1 or two custom stock roms floating around, which is what I'm working on ever so slowly. CM10 and the others a bit out of my league right now.
If anyone wants to try to bring more attention to this device, feel free to do so. It'd be helpful to have people who know what they're doing more than me.

MrHyde03 -
Thank you so much for the detailed information. That is exactly what I've been looking for... exactly THAT. Congrats on the upcoming wedding by the way. That's awesome.
I might be willing to donate or lend a device to the right person if potential exists for that to result in a working Rom.I wouldn't know where to begin on that. I am in the Seattle area but can ship if necessary. I like CM10 and have Paranoid Rom (based on CM10) running on my GS3 and I'd absolutely LOVE to have the same features on my SCH-I705. I have the tab mounted in my car and It's a really great device, but the stock rom is HORRIBLE. For one, this 'loud volume warning' (whenever playing music over headphones or line output, it decreases the volume because, according to Samsung, I'm not a big enough boy to make my own decisions with regards to my own hearing) is driving me absolutely crazy. My GS3 did the same thing, but since I've rooted and loaded custom roms on it, I've loved it.
Thank you again for being one of the few to reply to my questions and for providing these details, you are appreciated.

I'm getting this:
Step 1 - Pushing files...
failed to copy 'debugfs' to '/data/local//debugfs': Permission denied
failed to copy 'su' to '/data/local//su': Permission denied
failed to copy 'debugfsinput' to '/data/local//debugfsinput': Permission denied
failed on '/data/local/tmp' - Permission denied
link failed File exists
Rebooting...
Once your devices has finished restarting,
Press any key to continue . . .
Step 2 - Rooting...
For this step, ignore any error messages that say "File not found"
Unable to chmod /data/local/debugfs: No such file or directory
/system/bin/sh: can't open /data/local/debugfsinput: No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/debugfs, No such file or directory
rm failed for /data/local/debugfsinput, No such file or directory
Rooting FAILED! You may want to try running this tool again.
Your device region may not be supported if you see this message again.
Press any key to continue . . .
Could this have anything to do with me not yet having a sim card for the device (region??)?

I get permission denied errors when trying to push su and other files. Cannot obtain root. Any help?

What version android do you have? This is only confirmed on 4.0.4.
Sent from my SCH-I535 using xda app-developers app

MrHyde03 said:
What version android do you have? This is only confirmed on 4.0.4.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
4.0.4
I'm gonna try again today now that I have a sim, but I doubt that's the issue.
---------- Post added at 03:09 PM ---------- Previous post was at 03:02 PM ----------
JelloB said:
4.0.4
I'm gonna try again today now that I have a sim, but I doubt that's the issue.
Click to expand...
Click to collapse
Same thing. No luck.
---------- Post added at 03:11 PM ---------- Previous post was at 03:09 PM ----------
RevosFTS said:
I get permission denied errors when trying to push su and other files. Cannot obtain root. Any help?
Click to expand...
Click to collapse
Looks like we're having the same problem.

Yeah we have the same exact error. I am tempted to try manually pushing the root files through adb. I may have to call the banners though. Perhaps Liquid would be willimg to help.

Damn, if I had only seen this before I went TO the Verizon store, lol.
Oh well. I was just going to root and get a ROM out for everyone.
If anyone finds root let me know and I can start ROMS!
OP: You should put "not working" in title so people dont fill the thread with.. OMG it doesnt work!

[GUIDE] How to root Salaxy Tab S2 T817T

How to Root Samsung Tab S2 T817T (Step-By-Step Guide)
Obligatory notices
This procedure is only for the Samsung Tab S2 SM-T817T
Performing any of the operations in this post risks bricking your device
Performing any of the operations in this post will irreversibly void your warranty
Performing any of the operations in this post will irreversibly trip Knox and make it unusable for Samsung Pay (and any other features which require Knox)
I am not using a SIM card with my device, so I have no idea how this procedure will impact that functionality. People on the XDA thread (forum.xda-developers.com/tab-s2/help/sm-t817t-root-t3206079) where I pieced together these instructions from suggested that the SIM card still works for mobile data. UPDATE: Later in this thread people have confirmed that mobile data DOES work after rooting. Yay!
Introduction
OK, so a brief story of how/why I was forced to figure this method out. I found a listing on eBay for the Samsung Tab S2 T810N, paid $300 for it and received it into my impatient hands. Without checking the specific version of the tab I push right into the rooting procedure I had thoroughly researched for the T810N. Suddenly my tablet is in a bootloop and I am panicking that it is ruined. In the recovery mode I see that I have the T817T. Anger towards the seller aside, I frantically research how to recover the T817T. There is virtually no documentation for this procedure, so I am forced to mix-and-match. After about 5 hours, the tablet is finally up, running, and rooted!
TL;DR - verify your model number before attempting root
Files
All the files can be found here (drive.google.com/folderview?id=0BxPb6XhrMsaoa01zdjVUVWMzQWs&usp=sharing). Let me explain what each file is:
T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (drive.google.com/file/d/0BxPb6XhrMsaoeGpmbnRoeFA5MUU/view?usp=sharing) - This is an Android 5.1.1 image for Samsung Tab S2 T817T. You may not even need this, but just in case. If you use this, unzip the file to get the .md5 file!
SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.51.0.exe (drive.google.com/file/d/0BxPb6XhrMsaoc09qNm41OFhKLWc/view?usp=sharing) - Necessary Windows drivers for Samsung devices. Install this!
Odin3_v3.10.6.zip (drive.google.com/file/d/0BxPb6XhrMsaoLWtkek9UYWZGNGM/view?usp=sharing) - A flashing tool for Windows. Unzip these files!
twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) - This is a custom recovery tool for Android. Although designed for the T810 series, it does work on the T817T. Do not untar these files!
Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) - A custom bootloader for the T817T which is required to root. Do not unzip these files!
BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) - A newer version of SuperSu which works on the T817T. Do not unzip these files!
Preparation
Download all the files above. Install, unzip, and untar (or not) as instructed.
Settings -> About device - Verify that you have the SM-T817T
Settings -> About device - Verify that you are running Android 5.1.1
Backup all your files, contacts, apps, etc.
Verify that your device has at least 80% charge
Rooting Procedure
(OPTIONAL) Flash Android 5.1.1 image. This step is not necessarily required. If you are running Android 5.1.1, then you should be fine. However, this is what I had to do, since I got into a bootloop by not checking my version number first (yes, stupid me). Further, if you have any errors or issues below you absolutely will need to perform this step to recover and restart the rooting procedure. Anyway:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select T817TUVS2AOL1_T817TTMB2AOL1_T817TUVS2AOL1_HOME.tar.md5 file
Press "Start" button and wait for Green "PASS" message to appear. This will take a long time since this is a large file
Your device will automatically reboot
Perform basic setup procedures on Android so that you can access the Settings menu
From this point onward your must perform every step in the exact order as stated. Not doing so seriously risks putting your device into a bootloop or bricking it. You should be able to recover from that, but still...
Enable developer options:
Settings -> About device - click on "Build number" like 10 times until "Developer options" are enabled and button is added to Settings menu
Settings -> Developer options - enable:
Developer options - ON
OEM unlock - ON
USB debugging - ON
Flash TWRP recovery software:
Turn off your tablet
Boot into 'download mode' by holding POWER + VOLUME DOWN + HOME. Verify by pressing VOLUME UP
Run program Odin3 v3.10.7.exe
Plug your device to the computer with a USB cable
Verify that Odin message window states "<ID:#/###> Added!!"
Click the "AP" button in Odin and select twrp_2.8.7.1_LL_5.1.1_t810.tar (drive.google.com/file/d/0BxPb6XhrMsaoN0N6V3JzX290aGc/view?usp=sharing) file
Press "Start" button and wait for Green "PASS" message to appear
Your device will automatically reboot, verify that the tablet boots properly
Copy bootloader and SuperSu to tablet:
With your tablet on, attach it to your computer with a USB cable
Navigate to the root directory of the tablet storage
Copy Tab_S2_t817T_boot.zip (drive.google.com/file/d/0BxPb6XhrMsaob0hyME0zV2EtSnc/view?usp=sharing) and BETA-SuperSU-v2.52.zip (drive.google.com/file/d/0BxPb6XhrMsaoNk9uWkxRZ0wwTE0/view?usp=sharing) files to the root directory
Detach tablet from your computer
Flash custom bootloader with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select Tab_S2_t817T_boot.zip and click "Install"
Verify install with slider
STOP HERE!!! READ THE NEXT STEPS CAREFULLY!!!
TWRP will now offer to install SuperSu for you. DON'T DO IT!! Doing this will cause your tablet to bootloop because it is not the right version of SuperSu
Decline the SuperSu installation and restart your tablet
Verify that the tablet boots properly
REPEAT "Flash TWRP recovery software:" instructions. This is a necessary step. Without it your tablet will go into a bootloop and you will need to start the root procedure over. Weird, I know. Just do it.
Flash SuperSu with TWRP:
Turn off your tablet
Boot into 'recovery mode' by holding POWER + VOLUME UP + HOME
Select "Install"
Select BETA-SuperSU-v2.52.zip and click "Install"
Verify install with slider
Reboot the tablet
DONE! Assuming your tablet boots properly your should now be rooted and see the SuperSu app installed on your tablet.
Recovery
If you need to recover from some error you will need to start over completely. Use the Android 5.1.1 image file T817TUVS2AOL1_T817TTMB2AOL1_TMB.zip (same as above) to perform this. You can also use this Android image to restore the device to an unrooted version. This will not restore your warranty or Knox.
Extras
To get rid of the pesky KNOX security notification which will persist, use a program like ROM Toolbox Lite (play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=en). In the App Manager select the following apps and 'freeze' them:
SecurityLogAgent 4.1.4 (this one is critical to freeze!)
KNOX 2.3.0
KNOX 2.3.1
KNOX II 2.3.0
KNOX SetupWizardClient 2.3.0
KnoxFolderContainer 2.4.0
To get rid of the "No SIM card inserted" notification (if you aren't using a SIM card) use the build.Prop Editor in ROM Toolbox Lite. Add the following entry:
Property Name: ro.config.donot_nosim
Property Value: 1
Conclusions
I put this guide together for people who are having trouble finding a simple and easy-to-follow guide for rooting the T817T. Hopefully this can save you a number of frustrating and worrisome hours (not that rooting your Android device is ever a calm undertaking).
Please let me know if there are any errors in the procedure or if you have any suggestions regarding the steps or presentation of the material. Enjoy being a super-user!
Original content: blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T/

phduhblog said:
Long time user, first time poster.
First off, let me say, THANK YOU XDA! You guys have been a crazy valuable resource over the years.
However, with regard to the T817T, the documentation is lacking severely. I have created a comprehensive step by step guide to rooting the T817T. Unfortunately, as a first time poster, I cannot post links or anything like that so...if somebody could fix that I would appreciate it. I spent a long time formatting the posting and adding file download links with the XDA formatter so that it wouldn't look like I was link whoring to my blog, just to be told to **** off... . Seeing as that's not possible, here is the url to my blog with the rooting instructions:
blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Click to expand...
Click to collapse
http://blog.mchristian.co/blogs/post/How-to-Root-Samsung-Tab-S2-T817T
Thanks my friend
Edit: Completely professional and well done how to.. written just the way I like it, fantastic!! I think you should just edit your first post and paste all this in here on XDA... and ill be happy to carry your url link for you.

Complete text of the GUIDE
Edited and posted it above. Good luck with the rooting. Thanks!

An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!

patrioticparadox said:
An excellent guide. I'd spent the last few hours reading post after post gathering the correct information for the T817T specifically. I had come to the same basic conclusion as your guide states but its great to have some confirmation! I have a few differences in my install process than you did though. I did things in this order:
Enable developer options:
Copy bootloader and SuperSu to tablet:
THEN
Flash TWRP recovery software:
and between 6 and 7
Uncheck AutoReboot in the Options tab
7. Press "Start" button and wait for Green "PASS" message to appear
8. Use Power+VolumeDown+Home to reboot from bootloader and AS SOON as the screen goes black slide your finger from VolumeDown to VolumeUp
This should boot you into TWRP
Flash custom bootloader with TWRP:
after 4:
press "add another zip" and select the SuperSU zip as well.
5. Verify install with slider
6. Reboot
Done
By booting directly into TWRP the stock recovery doesn't have a chance to overwrite it. It won't need to be flashed a second time. You can also flash the kernel (...boot.zip) and SuperSU zip in the same pass. Saves a couple steps.
Either way I can confirm this works and all of the files are correct!
Thanks again for organizing all of this and making this great guide!
Click to expand...
Click to collapse
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
I had actually tried the non-auto-reboot from Odin method too, but couldn't time the change to VOLUME UP correctly. After a couple times I just gave up and tried things the long way around. Never thought to flash the zip files in the same TWRP session though. I generally like doing things the long way around and getting confirmation that things still work after each and every step. Whatever works though!
Thanks for the reply

phduhblog said:
I'm glad you have figured out another way! This is turning into what a proper thread on rooting should look like
Click to expand...
Click to collapse
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.

patrioticparadox said:
Indeed it is.
Are your volume buttons functioning properly after this? Just noticed yesterday mine aren't adjusting the volume.
Click to expand...
Click to collapse
Hmmm, odd. Sorry to hear that. Yes, mine work just fine.

Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.

patrioticparadox said:
Turns out my volume buttons are fuctioning just fine. I think I just pressed it wrong and didn't have a minute to double check it at the time.
Click to expand...
Click to collapse
Whew! I'm glad to hear that. Now people can root their T817T without concern!

Yep! Been using this for two weeks now and no problems!

Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.

phduhblog said:
Can anyone confirm that the mobile internet still work when you have a SIM card in? Thanks.
Click to expand...
Click to collapse
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.

androidcues said:
SIM does not work-- just restored back to stock.. going to wait a little bit before re-rooting.
Click to expand...
Click to collapse
Hmmm. Well that's good to know at least. Thanks for the update!
Also I'm glad you were able to revert to stock and get it working.

Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless ?)
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app

androidcues said:
Yeah... Ive fully unrooted and gone back to samsung for a bit.. wont be long because I automatically gravitate back to CM. hehe.
vibration doesnt work on CM... that was a big thing because i rely on tactile vibration for notifications.... (i am deaf so.. the noisy parts are useless )
but anyway... taking a moment to thank you again for your writeup...i really needed that...soon after i read your blog i was rooted and rocking!
But Samsung sucks bro... i cant stand all these ****ty apps on my tablet so maybe I'll come back sooner.
0x1
Sent from my Nexus 5X using XDA Premium HD app
Click to expand...
Click to collapse
Yep, I can definitely see why vibration notifications would be important for you!
As much as I dislike bloatware, from any company, Samsung just makes the most powerful tablets/phones. My best solution is to root and disable all the bloatware.
I'm glad the guide was well received and it seems to work for people.

My mobile data and SIM functions all work fine. Not sure why yours didn't

patrioticparadox said:
My mobile data and SIM functions all work fine. Not sure why yours didn't
Click to expand...
Click to collapse
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!

phduhblog said:
Awesome! That is weird it didn't work for the other guy. Did you flash the provided Android version first or just go straight into the rooting? Thanks for the update!
Click to expand...
Click to collapse
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?

patrioticparadox said:
Sorry for the late reply. I Odined the latest firmware to reset everything to a stock base before then flashing as your steps suggest (with the noted exceptions from my first post). My mobile data has worked flawlessly and I have had zero SIM related issues. In fact, I have had no issues what-so-ever. (I did think I had an issue with my volume rocker not working but that was user error. I have my tablet in a case of sorts and was not pressing hard enough). @phduhblog and @androidcues are you both still experiencing mobile data and SIM issues as of now?
Click to expand...
Click to collapse
Wording changed! Thanks for the update.

One question pls. I have the T817V tab 9.7 w/OEM bootloader option button. Is any of this available to use for my tab? TWRP recovery maybe? Any files? Any reply is appreciated. Novice seeking knowledge. Thank you so much.

Root for people on G920TUVU5EQC2

Okay, so thanks to this thread here: https://forum.xda-developers.com/tmo...t3382856/page6 and the person who did it (to my knowledge) @AZWildcat
Copy & pasted @ktrinh4213
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Sorry if I did tagging wrong I usually lurk

Flash TWRP and then the SuperSU ZIP.

Also auto root still work. At least it did on mine phone

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
The baseband isn't listed on Autoroot which is why I've not used it.

Obievil said:
The baseband isn't listed on Autoroot which is why I've not used it.
Click to expand...
Click to collapse
That is the same reason I havent either ;-;

EncryptedCurse said:
Flash TWRP and then the SuperSU ZIP.
Click to expand...
Click to collapse
sorry it has been a long time since i rooted my phone i know how to install twrp and supersu but how does just installing supersu root my phone i thought you had to have a rooted phone to install supersu

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
what was your base?

timspotatochips said:
sorry it has been a long time since i rooted my phone i know how to install twrp and supersu but how does just installing supersu root my phone i thought you had to have a rooted phone to install supersu
Click to expand...
Click to collapse
Super SU does require root. I was confused by his answer as well. I wondered if I could use the latest Base for my phone from Autoroot but I'm not willing to risk it without knowing for sure.

Obievil said:
Super SU does require root. I was confused by his answer as well. I wondered if I could use the latest Base for my phone from Autoroot but I'm not willing to risk it without knowing for sure.
Click to expand...
Click to collapse
Yeah haha well i dont mind testing it in a few weeks and I can let you know unbricking usually isnt hard just flashing stock usually will fix it I was also curious if I could downgrade by flashing stock roms cause i dont care about knox

timspotatochips said:
what was your base?
Click to expand...
Click to collapse
EQC1, I think... the one before this one... there's actually a tread on how to root s6 with mm

britchel said:
EQC1, I think... the one before this one... there's actually a tread on how to root s6 with mm
Click to expand...
Click to collapse
oh okay do you have the link please and thank you ))?

timspotatochips said:
Yeah haha well i dont mind testing it in a few weeks and I can let you know unbricking usually isnt hard just flashing stock usually will fix it I was also curious if I could downgrade by flashing stock roms cause i dont care about knox
Click to expand...
Click to collapse
My phone is out of contract so I don't care about knox anymore, It's been so long I am still a little afraid of bricking it. the last phone I rooted was the Galaxy S3, believe it or not lol!

Obievil said:
My phone is out of contract so I don't care about knox anymore, It's been so long I am still a little afraid of bricking it. the last phone I rooted was the Galaxy S3, believe it or not lol!
Click to expand...
Click to collapse
oh dang last phone I rooted was my nexus 6 and knox is useless im sure you can still encrypt your phone without it and well samsung pay is ass and you can get a new kernal for fingerprint scanner if it no longer works but ill let you know if I am able to root my phone I assume youre on the same firmware as me?

timspotatochips said:
oh dang last phone I rooted was my nexus 6 and knox is useless im sure you can still encrypt your phone without it and well samsung pay is ass and you can get a new kernal for fingerprint scanner if it no longer works but ill let you know if I am able to root my phone I assume youre on the same firmware as me?
Click to expand...
Click to collapse
Yes I am, it's how I landed on this thread.

Obievil said:
Yes I am, it's how I landed on this thread.
Click to expand...
Click to collapse
haha i assumed so just wanted to clarify

Just out of stupidity, and morbid curiosity I tried to Autoroot the last known good rom from that site. And it failed with a FRP lock error message. I'm surprised it didn't brick.

Hey why don't you make your own rom. Pretty easy... you customize it to your like, I made mine and it's pretty stable. And it roots it from pc

britchel said:
Also auto root still work. At least it did on mine phone
Click to expand...
Click to collapse
britchel said:
Hey why don't you make your own rom. Pretty easy... you customize it to your like, I made mine and it's pretty stable. And it roots it from pc
Click to expand...
Click to collapse
I don't think you understand. The rom isn't the issue here, It's getting root access that's the problem.

Okay, so thanks to this thread here: https://forum.xda-developers.com/tm...oot-samsung-galaxy-s6-sm-g920t-t3382856/page6 and the person who did it (to my knowledge) @AZWildcat
Copy & pasted @ktrinh4213
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Sorry if I did tagging wrong I usually lurk

This worked, I just rooted my device! Thank you for linking this!

Root for Note 8 Exynos on Pie? Help appreciated. SOLVED

When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting. I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging.

jwils1236 said:
When attempting to flash any/latest TWRP I continually get message 'Only official binaries are allowed to be flashed(RECOVERY)'. I purchased this phone new just recently and paid quite a bit for it, solely to be rooted (specifically global version SM-N950F/DS). I didn't imagine that the global version with the exynos processor would give me so much trouble rooting and wouldn't have bought it if I would have known (or at least not updated to Pie). I updated to Pie, because I knew the OEM unlock option would be accessible in developer options and thought it would make the process of rooting simpler, not more challenging/impossible. Any help would be appreciated and if a solution is brought to light, I am gladly offering $. This could easily be considered a device with best hardware and when rooted, access to best software -- I didn't see significant enough improvements in Note 9 and figured by now the support from XDA community would be abundant for the exynos processor. Turning out ridiculous waste of money if I can't root it (already purchased silver carbon fiber skin, 256 GB Samsung Evo Select SD card, attachable portable wireless charging pack, etc.). Please help!
Click to expand...
Click to collapse
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.

Its just easy step
Things u needed before proceed
* SD card
*Magisk latest version
*Odin
* Twrp zip file
1. Reflash ur device with proper firmware
2. After done go download mode and flash Twrp zip on odin. After done reboot ur device to Twrp again
3. After boot up to Twrp go to Wipe and do a factory restore . After this done u must install Magisk or u will get official binary only after reboot to system
4. After all the step are followed u are good to go. Cheers

stonedpsycho said:
You need to disable/delete 'security log agent' on first boot or the only official binary message will appear on reboot, you also have to patch rmm state, or it will keep happening too, which can read about here-
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
I believe all the roms have already patched this which could save you the hassle, if you just want a stock rooted rom, try Dev-Base.
Click to expand...
Click to collapse
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.

jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
Also, for anyone reading this with the same issue, extracting the boot image from stock firmware (can be done through command prompt/terminal dump or by extracting from stock firmware -- AP Odin file) and patching with Magisk will not flash or work/give root access either unless this device is fully unlocked -- OEM unlock doesn't matter, if RMM still says "Prenormal" in download mode.

jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I am quite sure it is still rootable on bootloader 6, so updating would be fine.
The trick to get the OEM toggle is a bit hit and miss, the guide below is the method that has had a higher success rate for me, if followed exacty as written.
https://www.google.com/amp/s/www.xd...-samsung-galaxy-s8-samsung-galaxy-note-8/amp/

jwils1236 said:
I see. After research, it appears I'm not unlocked like I thought I was -- was thinking since OEM unlock option is accessible and valid in recovery it would be possible to flash TWRP, but didn't consider RMM state. Do you have any idea if it is safe to upgrade to the 'latest' Pie and if the bootloader would change capacity of root? Wouldn't mind being on the latest in the meantime, while I hope and wait 7 days. Also, not sure if the workaround on changing the clock would work or if any info on this to make work -- tried with no luck. Don't want to wait 7 days and seems like there could or should be a workaround, but whatever needs to be done I suppose. Appreciate your assistance.
Click to expand...
Click to collapse
I ended up using Chimera Tool to bypass RMM state. Worked instantly. This seems to be a common issue for many Samsung devices, at least on Pie. Not sure there is an alternative solution, currently. Only one I could find for my device.

Question Wont boot after root

Hi all. Succesfully rooted my S8 Tab Ultra and was running fine for the past week.
Just rebooted the tablet and its showing "Custom Binary(boot) Blocked due to remaining installment balance" I've read around the forum and apparently its for people who haven't paid for the device fully which I have, paid in full on pre order.
The only way it seems to get it to boot is to flash the original firmware my model is SM-X900NZAFXAR and I can't find the firmware does anyone know how I can get the tablet to boot?
Tried Samsung support but they didn't help

Hello! Get SamFirm at https://samfirmtool.com/ (v0.5.0 is the latest), for model put SM-X900, for Region put XAR. I haven't received mine yet (not until the middle of next month), but this is the closest I could find to what should be the correct firmware. Click "Check Update", then click "Download". It's been too long for me away from Samsung - I don't remember if it matters if you let it decrypt automatically or not. The answer should become apparent, though. At worst, you'll just have to redownload the firmware with the option to decrypt unchecked in SamFIrm.
You can check your CSC (Region) by (copying/pasting someone else's instructions):
go to settings - about - software information - service provider SW ver. The region code (CSC) will be written there.
I don't know if your CSC will match XAR. I don't find anything for XAA or XAS yet in SamFirm.
Good luck! This is concerning since I had planned on rooting mine.

Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers

Jono0907 said:
Thanks for the reply. I've downloaded the XAR firmware but now I have another problem getting the USB device not recognised. Device descriptor request failed. Tried locking the bootloader again now its stuck with a Hash fail on boot and wont turn off. Can't unlock the bootloader again. 99% sure its not the laptops fault its the one i rooted on but will try another pc tomorrow. Will have to try Samsung again as although I have rooted which voids warrenty its there mistake on my device thinking it has finance outstanding that has caused the failure.
Cheers
Click to expand...
Click to collapse
You got the latest Samsung drivers installed, as linked to in the SamFirm\Samsung Driver subfolder? (link leads to https://samsungusbdriver.com/category/download)

Wait... Is OEM Unlock still enabled in Dev Options? It might be salvageable even though you have locked the bootloader...

Thank you edor for the help the tablet is running again now however it is unrooted now and the OEM unlock option is missing. The USB fault was resloved using a different PC not sure whats going on with my laptop.
Once in download mode i was able to download the XAR version of the Tab S8 Ultra fimrware from SamFirm and reflash with Odin which brought it back.
I'm not sure if running XAR csc will cause problems? I am in the UK I think my csc originally was OXM which is the universal one but cant find an OXM version at the moment.
fkofilee I actually locked the bootloader from the download mode menu which i shouldnt have. I don't have the option now so think I need to wait for the OEM unlock to show in settings.
For anyone else who has the "Custom Binary(boot) Blocked due to remaining installment balance" Need to reflash back to original firmware to boot and apparently it will re-check in 7 days so cannot be rooted in that time.
I have an open ticket with Samsung to try and find out why my tablet thinks it has finance. The confirmed on the phone that it was paid in full.
I wonder if the S7 Bootloader that i rooted had anything to do with it. Will retry with the bootloader when i can and report back.

@Jono0907 I'm glad you got it back working. I apologize if the XAR firmware has anything to do with your OEM unlocking not being available. Thank you for the advice for myself and for others to follow if we encounter the same problem. You had used the S7 bootloader? I would expect that to be the problem but as I said, I'm rusty on Samsung, and totally unexperienced in Samsung tablets - I only know what I've read in this section so far.

My tablet is working because of your advise so I'm happy. Found the EUX firmware which feels like it should be what my tablet should be running so will flash that and see if Unlock comes back. Tried all the tricks with date/time to try and trick it but no luck.
Also was going to add my experience with Samsung support. He agreed that if the tablet was wrongly reporting it was in finance then it wouldn't have been my fault but also said Samsung would not help because I had rooted the device. He didnt talk about reflashing firmware just said that I needed to send it to them for a new motherboard to repair Knox at a cost of at least $400(£300)

I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks

It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it

ivanox1972 said:
I planned to root s8 ultra, now afraid. So, is it safe to root it, and can someone put here whole procedure?
Many thanks
Click to expand...
Click to collapse
I want clearly explanation, I don't know about this.

Jono0907 said:
It's pretty much always safe because you can go back to "Download Mode" and reflash the original firmware.
It will however trip Knox which is Samsungs securityh (Done by breaking a physical fuse on the motherboard) which cannot be undone. This voids the warrenty and could cause problems with Google Pay and other things.
The basic process for rooting the S8 is
1. The process requires OEM Unlocking which some carriers in USA seem to be blocking. If you can OEM unlock it will be an option within the developers options in settings. Sometimes it doesn't show up right away.
2. Download SamFirm and get the firmware for your device. The Model for the Non-5G Tab S8 is SM-X900 and put in the CSC code for your region. Samsung simplified CSC codes before the release of the Tab S8 so you can see the list on wikipedia when searching for the tablet it is probably better to look up how to check your CSC code on your tablet to make sure you are getting the right one.
3. Install Magisk Manager on your tablet. Extract the firmware and copy the AP file to your tablet. Open Magisk Manager and point it at the AP file that you copied. Once complete it should give you a Magisk Patched file copy it back to your computer.
4. Install Odin and Samsung USB drivers. In Odin Select the Magisk Patched file for AP then add the BL file that you downloaded from SamFirm and the CSC file. (This will factory reset the tablet). You can leave CP and Userdata blank.
5. Reboot the tablet into Download Mode. This can be done by powering it off connecting it the the PC and when you see the charge symbol hold down Volume up and Volume down till you get to the Download Mode Menu. From here you need to press the option for OEM Unlock and then go to the download screen. Now press start in Odin.
That's pretty much it
Click to expand...
Click to collapse
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?

emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Sorry mate never done the HOME CSC flash I've always been happy to wipe the device hopefully someone here knows?

emko7 said:
Succesfully rooted a magisk patched AP. Then later I tried to flash another one with an updated firmware, resulting in a soft brick. Does reflashing unpatched stock rom via Odin wipe all my data? Even if I flash HOME_CSC?
Click to expand...
Click to collapse
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.

lloydsw said:
Uh-oh. I was just getting ready to update to the latest firmware, Maybe I'll have to wait, see how this plays out.
Click to expand...
Click to collapse
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.

roirraW edor ehT said:
For what it's worth on my S8 Ultra, I updated from rooted April update to rooted May's update perfectly fine without wiping data. Always do backups, though, things happen.
Click to expand...
Click to collapse
Yup, worked fine on my S8. Sigh of relief!