Database Develop

[TIP/HOWTO] For those with new Fire not yet powered up and want to install custom ROM

Tip: When you receive your Fire 2015 tablet, don't setup WiFi if you want to install custom ROM (skip WiFi setup)
Why: They are still shipping with FireOS 5.0.1 and it will autoupdate to 5.1.1 as soon as it sees Internet connection (it doesn't ask and takes over tablet)
Why is that bad: Because it's easier to install custom ROM with 5.0 and still a pain/riskier if from 5.1.1 (as of December 2015)
Why is this method easier/safer: No need to root first, no messing with original ROM (can backup first), no need to enable Developer mode, no need to grant ADB permissions
Prerequisites:
- This method will not work if tablet has upgraded to FireOS 5.1.1 or higher, only 5.0.x works
- Need fastboot tools installed on a computer (Windows tools/drivers here if needed) or (Linux/Mac)
- Download TWRP Recovery here to same computer
- Download your new ROM/support files of choice to an external SD Card
- If on Windows, to keep things simple you might place fastboot command, Recovery image in same folder/directory
Install: Fastboot TWRP Recovery from computer, Install Custom ROM from SD Card
- When you receive Fire, don't power it on (or if you do, don't setup WiFi as it will autoupdate to 5.1.1)
- Copy your downloaded ROM image and support files to an SD card, then insert SD into tablet
- Boot tablet directly into fastboot (power button and volume up button)
- USB attach tablet to computer that has fastboot tools and TWRP recovery image
- Unlock and Boot directly into TWRP image from computer terminal or command line
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot boot TWRP_Fire_2.8.7.0_adb.img
- Takes seconds to transfer file then recovery should appear
- Optional but recommended: From TWRP, Backup Stock Amazon ROM to external SD card
- Factory Reset from TWRP Recovery
- Install ROM and support files from TWRP via external SD card
- Reboot, profit

Just bought another tablet and this method worked again. Went straight to doing this before even booting.

xenokc said:
Just bought another tablet and this method worked again. Went straight to doing this before even booting.
Click to expand...
Click to collapse
Did you buy it from Amazon? I just ordered mine yesterday.

stef-nix said:
Did you buy it from Amazon? I just ordered mine yesterday.
Click to expand...
Click to collapse
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.

xenokc said:
Yes, am interested if yours came with 5.0 or 5.1.1. If you boot, dont setup Wifi (skip setup) or will autoupdate - it doesn't ask so be careful. Can then check version.
Click to expand...
Click to collapse
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.

stef-nix said:
It came with 5.0.1, I'm going to pull out the root script as soon as I turn it on.
Click to expand...
Click to collapse
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.

xenokc said:
You don't need to root it with the above method. Just go straight into fastboot and launch recovery via computer as described, backup stock ROM then install your ROM (then flash or enable root in developer mode within tablet). I trashed a tablet trying to root it with current methods, which is why I came up with this method.
Click to expand...
Click to collapse
Gotcha. As soon as I opened it, I blocked OTA updates. Rooted/installed SuperSU, and backed up the stock ROM.
I'm currently running CM12.1 and it's working perfectly.
I did not like how it auto signed into my Amazon account once connecting to WiFi (with OTAs blocked)

Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!

Parhelius said:
Many thanks for this. I'm completely new to modding in any way, shape or form, so this is very helpful.
I have seen another thread (http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416) which suggests that running CM should be possible now with OS 5.1.1 (my tablet has unfortunately updated since shipping). I have also currently run the script contained within http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804, and was wondering whether it would still be possible to follow the instructions here to install CM, or is it necessary to first restore the Fire tablet back to factory settings (if this is possible)?
Thank you in advance for any help!
Click to expand...
Click to collapse
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?

stef-nix said:
Did your tablet come with 5.1.1 out of the box? Or did you just connect to wifi and the updates came through?
Click to expand...
Click to collapse
I connected to wifi and the updates came through automatically. I hadn't read threads like this one beforehand unfortunately, so I didn't realise that would happen.

Sounds like Amazon is still shipping with 5.0.1 so this method can still apply for those who catch this thread before receiving/booting their tablet. What's nice about this method is you can backup original ROM before modding and don't need to root. Sounds like many have thrashed their tablet trying to root.

Just dont connect to wifi and your fine.

Amazon having a $40 sale, if you ordered one might not setup WiFi when first receiving - re-read first post why.
http://www.amazon.com/Fire-Display-Wi-Fi-GB-Includes/dp/B00TSUGXKE

Just ordered 3 today ... Can't wait to tinker with it.
Thanks for the heads up regarding auto-update!

I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.

percussionking said:
I've gotten 3 in the last week or so. One came from a small town up north (sorry, shipping details have disappeared from my history) with 5.0.1 and the other two came from Ft. Worth, TX with 5.1.1. I too think everyone should enter recovery immediately when the thing arrives, and then fastboot boot twrp.img to see what happens. I was hoping that if I declined the "Link to my Amazon Account" option, they would pull an older one from stock. Looks like I'm 1 for 3. All 3 have some issues (stuck pixels, backlight bleedthrough) so I'm getting a 4th one from Ft. Worth tomorrow.
Click to expand...
Click to collapse
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!

vn33 said:
Did you try the steps in this thread with the 5.1.1 unit sright out of the box?
Does this still work, or behaved differently with 5.1.1 ?
I'm waiting for my units to make their way to me. Really interested to see what your experience with the 5.1.1 units.
Thnx!
Click to expand...
Click to collapse
My 4th one came from Ft. Worth. I immediately booted into recovery mode but could not boot TWRP. Obviously this turned out to be a 5.1.1 system. If this had been a 5.0.1 system, the first full boot would have been to CM rather than to stock. So if 5.1.1 is installed at the factory you can't get your TWRP on this way.

Just got mine today it had 5.0.1 creating a backup now

Hi,
where can you download twrp from their page?
I see their list of devices but none of them says fire 5th generation.
https://twrp.me/Devices/
THANK YOU!

No you get twrp from here http://forum.xda-developers.com/amazon-fire/development/wip-bootable-recovery-kffowi-ford-t3238683

SM-T350 (Wifi) US Firmware

I have been looking for 3 days now for the US firmware for the SM-T550NZASXAR (might be the same as SM-T550NZAAXAR) and I can't find it. Sam mobile has the files for many countries but fails to show the US version. Am I missing something?
The digitizer keeps losing the touch sensing ability but I'm pretty sure it's a software problem as it comes back after maybe 15 minutes then it stops again after about 20 minutes of use. I want to try and re-install the OS with Oden and see if it clears whatever is going on. I'm hoping it's just bad cache or something.

The Canadian version is usually the same but double check just in case
Sent from my SM-T350 using XDA Free mobile app

Same Issue. I been also looking for US firmware for my SM-T350 Samsung Galaxy Tab A. I see it available for all other countries but not for USA. For all people that live in the US like me. We need to all nag Samsung & complain cause obviously they only support it for all other countries & not US. It pisses me off & it's so unfair. I need the firmware for part of the procedure to fix my rooted tab that's in bootloop

Upset with T-350 firmware situation
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx

weaselleaf said:
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
Click to expand...
Click to collapse
http://www.thegalaxytabforum.com/index.php?/topic/33026-recovery-twrp-2871-tab-a/

Twrp tested on sm-t350
weaselleaf said:
I've experienced the same disatisfaction with the non-availability of firmware. I'm also having trouble finding TWRP dedicated for this, kingrooted, device (sm-t350). Any insight? I've read the xda thread on compiling twrp on my own but I'm thinking that's still a bit over my head. I bought multiple cool apps since rooting my device only to find out I need twrp (or cwm) to make use of what these app have to offer.
Thx
Click to expand...
Click to collapse
twrp for SM-T350 is file name twrp-28.71-t350.tar
I can't link or i would link you it. Just google search that file name and there is one from android file host
Flash with Odin 3.10.7
Tested and works perfect
Seth50 gets all the credit just confirming it works

WOW! i have been messing with this for hours and cant believe that the samsung smart switch offered such an easy solution.
i made the mistake of flashing a rooted firmware file before unlocking the bootloader and soft bricked it. the smartswitch asks for the model# (SM-T350) and the serial number (no, im not putting mine here), tells you to enter odin mode and then it does all of the dirty work for you... amazing!
one thing to keep in mind is that the install for smart switch will not work on newer machines unless you install legacy software that you can find here https://www.microsoft.com/en-us/download/confirmation.aspx?id=5582

qixiixiq said:
WOW! i have been messing with this for hours and cant believe that the samsung smart switch offered such an easy solution.
i made the mistake of flashing a rooted firmware file before unlocking the bootloader and soft bricked it. the smartswitch asks for the model# (SM-T350) and the serial number (no, im not putting mine here), tells you to enter odin mode and then it does all of the dirty work for you... amazing!
one thing to keep in mind is that the install for smart switch will not work on newer machines unless you install legacy software that you can find here https://www.microsoft.com/en-us/download/confirmation.aspx?id=5582
Click to expand...
Click to collapse
I realize this is an old thread, but looking for help. Purchased a Wifi-only Galaxy Tab A, and looking for the stock 6.0.1 ROM. The Smart Switch software doesn't downgrade it anymore. They've since updated the software to remove that capability, but even older versions still reapply Nougat. Sammobile.com doesn't seem to have it. Has anyone had success finding the stock MM US ROM for this tablet? If you're asking why, adb restore doesn't work on Nougat and I'm trying to restore backups without root. I have a second SM-T350 fresh out of the box, and restore is working. So, want to downgrade to official MM to restore, then maybe upgrade again if I feel like it....
Edit: Embarrassingly, it's in this same forum.... Download it now...I'll see myself out....
https://forum.xda-developers.com/ga...m-stock-builds-sm-t350-ghost-project-t3529439

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

Anybody find any major bugs?

I had lag and touch sensitivity issues and I upgraded my white note4 dash cam from 4.4.4 to 6.0.1. Factory reset fixed it. I am going to set my white note4 up as close to daily driver as possible and run with it a few days before I upgrade my black note4. In the meantime anything to report? I haven't run into issues. How is reception? Does it still connect to hspa+ when LTE signal is fine or low? Still have 5.1.1 bug where outgoing calls couldn't be made occasionally but receive was fine until reboot?

Everything is good for me.
To anyone that is experiencing problems.
Before you complain that MM is jacked up please try and do a full wipe. (System, Data, Internal Storage)
Then flash PE3 from a stock tar file via Odin.
Yes its inconvenient but still its the cleanest install you can do. Its also the only way you can be certain the the issues you experience is caused by MM and not by a conflict or some other thing you have done to your phone.

+1 for fully functional when flashed properly. My process:
1. Backup
2. Backup your internal data to sd or USB
3. Reboot into recovery, wipe everything (internal and data included)
4. Reboot into download mode
5. Flash with Odin
Optional root:
6. Flash TWRP .tar in Odin. (The best way to get TWRP to stick is to flash it before the ROM boots for the first time. Takes practice and timing, but will save you a headache. )
7. Flash latest seamless root from chainfire in TWRP recovery
Sent from my SM-N910T3 using XDA-Developers mobile app

DeeXii said:
Everything is good for me.
To anyone that is experiencing problems.
Before you complain that MM is jacked up please try and do a full wipe. (System, Data, Internal Storage)
Then flash PE3 from a stock tar file via Odin.
Yes its inconvenient but still its the cleanest install you can do. Its also the only way you can be certain the the issues you experience is caused by MM and not by a conflict or some other thing you have done to your phone.
Click to expand...
Click to collapse
Not experiencing problems. Just trying to find any majors bugs that might hold me off for awhile. Haven't tested with a sim card yet. Just my note4 with a dashcam. Every thing apparently seems fine. Totally stock though. Going to flash TWRP and root of course. Then xposed a week down the road. Need ad blocker and swap back and recent buttons. The I'm going to mod s pen to left side of note for us lefties. Sike! But do wonder if Samsung will ever appease the lefties.
Sent from my SM-N910T using XDA-Developers mobile app

thefanum said:
Optional root:
6. Flash TWRP .tar in Odin. (The best way to get TWRP to stick is to flash it before the ROM boots for the first time. Takes practice and timing, but will save you a headache. )
Click to expand...
Click to collapse
For someone relatively new to the Samsung way (but not flashing in general), what's the best procedure for this particular step?

SteveRiley said:
For someone relatively new to the Samsung way (but not flashing in general), what's the best procedure for this particular step?
Click to expand...
Click to collapse
Guessing from off top of my head but untick reboot after flash. Flash TWRP when Odin finishes rom. This upsets me. Lol. I just factory reset again and setting up my phone. Waiting for apps to DL so I can flash TWRP and root. Ugh. I guess I'll update later or by Friday at least or maybe somebody else will.

My phone is laggy. Did a full wipe as per OP, then flashed stock rom.

SD card tap here to transfer media files
I have a constant notification "SD card tap here to transfer media files." on my Note 4 replaced recently with the T3 version, now that I have done the OTA upgrade to 6.0.1 Marshmallow. Everything else works well. The Galaxy S7 forum has threads on this issue dating back to April 2016 anyway. Is nobody else seeing this on the Note 4? I have a 64 Gig Samsung microSDXC UHS-1 Card. Perhaps this is just cosmetic? Restarting doesn't fix it. Unmounting and remounting from Settings > Storage doesn't fix it. No surprise that taking the card out after power down does eliminate the notification. Replacing the card and restarting brings the notification back.

Saw SD card notification once but not again even after many restarts.
Sent from my SM-N910T using Tapatalk

Everything is fine for me. I've noticed Lego Star Wars The Complete Saga runs way better on 6.0.1 than it did on 5.1.1. I did a factory reset after the upgrade and haven't had a problem yet.

Stuck in 4g mode, unable to recognize finger print unlock and the transfer media filed bug.

How do u fix the screen rotation on marshmallow? Doesnt work.

DeeXii said:
Everything is good for me.
To anyone that is experiencing problems.
Before you complain that MM is jacked up please try and do a full wipe. (System, Data, Internal Storage)
Then flash PE3 from a stock tar file via Odin.
Yes its inconvenient but still its the cleanest install you can do. Its also the only way you can be certain the the issues you experience is caused by MM and not by a conflict or some other thing you have done to your phone.
Click to expand...
Click to collapse
Does OTA not install the update the same as ODIN? I'm dont care for root at the moment as I have in the past.

In the first flash from 5.1.1 to 6.0.1 my phone stalled at the tmobile splash. I just did a factory reset and wiped it down a couple times and it booted up just fine. Been up and running for almost a full 24 hours now and no probles to report. I just installed my gear vr files and ill see how netflix and the theater run.

monkeyass408 said:
How do u fix the screen rotation on marshmallow? Doesnt work.
Click to expand...
Click to collapse
See this post from DeeXii:
http://forum.xda-developers.com/showthread.php?p=67537758
Sent from my SM-N910T using Tapatalk

Has anyone tried secret mode in the Samsung browser? I can't get the fingerprint or password lock on it. In 5.1.1 I could have it so that it needs a fingerprint or password to go into secret mode. I don't see the option to do it now on 6.0.1. I checked on the playstore to see if I have the latest version and I do. It's also not in privacy in settings for the browser.

Waiting on a few more replies before I flash it. Perfect weekend to do it
Sent from my SM-N910T using Tapatalk

Does the phone still show LTE in notification bar when it's available? or does it just show 4G/3G/2G now? I only ask because I am not sure if that's all that's displayed now because all I show is the 4/3/2.
Thanks

can someone on marshmallow please test out the built in video calling? for me it keeps saying preparing display image...
lol laugh out loud .... f-ing tmobile took so much time trying to implement that feature in the dialer and it still fails

monkeyass408 said:
How do u fix the screen rotation on marshmallow? Doesnt work.
Click to expand...
Click to collapse
Did you freeze or uninstall any apps with Titanium Backup?
---------- Post added at 10:24 PM ---------- Previous post was at 10:23 PM ----------
ElCid43 said:
Does the phone still show LTE in notification bar when it's available? or does it just show 4G/3G/2G now? I only ask because I am not sure if that's all that's displayed now because all I show is the 4/3/2.
Thanks
Click to expand...
Click to collapse
The Cell signal icons and behavior are the same as LP.

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!