Database Users

[Guide][P600 Only] - Guide to return to stock with links to files!

I created a spot on my website for the stock Odin Tar's that I use for the P600.
I posted the US / XAR Region Stock Odin. I also posted the ML1 Asian base I used as well.
As I gather newer ones I will put them up and updated this thread.
Although this guide is written for the p600 it would, in theory work on any P60x device so long as you have the proper Odin files!
Note: This will not "untrip knox"!!!!!!!!
Here is the download page on my site:
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Enjoy!​

Currently Hosted:
P600UEUBMK1_P600XARBMK1_XAR (Shipped US ROM / XAR Region)
P600ZTUBML1_P600ZZTBML1_BRI (Asian Based ROM / BRI Region)
Other Odin Tar resources: Sammobile. Must be a member but they have tons of them.

How to Return to stock
This mini guide assumes the following...
You were able to root and or install a custom recovery or ROM therefore the drivers are installed on your PC for the tablet. So here we go...
Download Odin from the links in the OP
Extract the the .md5 file from the zip file you downloaded above.
Boot tablet into "Download" mode. You can do this by holding Power and Volume - (down) when the device is shut off. I note on this device it can be a little trickier so you may have to try a couple times. You should now see this on your tablet
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Connect Tablet to PC using known good USB Cable
Start Odin and Press the "AP" button to load the tar.md5 file. This may take a minute as it is also calculating the MD5 to ensure you have a good file. A bad file means bad issues and it wont let you flash it (good fail safe).
Once Odin sees the Tar and loads it completely AND Odin sees the tablet press the Start button to begin. Can takes about 5 to 10 minutes so be patient. Do NOT check or uncheck mark ANY other Options in Odin unless you know what you are doing!
Once it complete you will have a factory image on your tablet. Yay!
But we are not done. You may also want to, at this point, reboot to recovery and do a full data wipe. This method of Odin leaves the SD card and user data intact. To get into recovery hold Power and Volume + until you see the stock Android recovery. Select format Data, reboot. Boom, your tablet is like brand new!

Guided added!
I am not the best technical writer so if you need help understanding what I am saying dont hesitate to ask!

Bumped so people can find this...
Mods moved it so no one looking will actually see it...

scrosler said:
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
Click to expand...
Click to collapse
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!

Vexelius said:
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Click to expand...
Click to collapse
Indeed!

What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?

kaneelias said:
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
Click to expand...
Click to collapse
If you can see samsung screen you can odin back to stock.
The directions I posted should hold true about getting to Odin / Download Mode

Thanks for this guide, I agree, it should definitely be in the development section.

Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks

Thanks for this Scott and a great ROM!!!!
Sent from my SAMSUNG-SGH-I317 using Tapatalk

tahrang said:
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Click to expand...
Click to collapse
Yes, this is returning you to stock like when you turned it on for the very first time.
No one knows how to untrip knox.

Is it Knox that blocks the ota updates, or is it the rooting itself?

starfall42 said:
Is it Knox that blocks the ota updates, or is it the rooting itself?
Click to expand...
Click to collapse
Not sure. Never tried to Ota with KNOX.
Maybe ask in the Q/A forums.

Just to be safe, and If I do this the tablet will be as if it was completely new, right? I'm going to exchange it for another one and I want to be sure it's as new. Are there any flash counters or stuff like that I should be worried about?
Sent from my Nexus 5

So when a system update comes out we could use these directions to flash the stock rom with out loosing data, apps, settings, etc? Then be able to get the stock OTA?
Coming from the Nexus world, This is a bit different. Google seems to have no interest in the 10 inch sector though, so here we are.

Never have we had a tablet so heavily defended with so many issues. 6 tablets and this one stands out.
Via my Note 3

Tripping out?
scrosler said:
Note: This will not "untrip knox"!!!!!!!!
Click to expand...
Click to collapse
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.

iTelegraph said:
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
Click to expand...
Click to collapse
1. As far as anyone knows, Knox cannot be untripped.
2. If you Odin a FACTORY IMAGE it WILL NOT trip Knox. Only custom roms/rooting trips AFAIK.
3. I'm not 100% sure as I haven't tried, but I think I've seen discussions where the bootloader wasn't changed so you could go back. Again, I'm not 100% sure. Maybe we could get clarification from someone who tried.
Sent from my SM-P600 using Tapatalk

[GUIDE] Baseband/Radio "stuck" and not updating? Here's how to fix it!

Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.

Nice....it helped me :good:
Thanks :highfive:

neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband

nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.

neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.

IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that

Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app

Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD

Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.

neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.

I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?

neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.

MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.

not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?

jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.

[Q] SM-T530NU Android version 5.0.2

I had my Tab 4 rooted with CF auto root and was happy!.
Over about 3 months it seemed there were some performance issues so I used super su to un-root, and went for a factory re-set.
I tried to do a software update once back up and running but, got the pop-up telling me it couldn't up-date b/c of knox (actually said system has been altered etc..)
So,,,,,
I plugged into my samsung keys and to update and next thing I knew I had gone from KitKat 4.4.2 to Android 5.0.2.
This also changed my build number, to LRX22G.T530NUUEU1BOE5.
I WANT MY ROOT BACK, , , question is HOW?
None of the numbers aside from model number (SM-T530NU) match up with the CF auto-root now, as they did before.
I'd like to be rooted before heading back to Lagos Nigeria on Monday 6/22/2015,, but I don't want to brick this thing prior to leaving and end up tab-less.
ANYONE HAVE TIME TO HELP?:fingers-crossed:
[email protected]

rnerger said:
I had my Tab 4 rooted with CF auto root and was happy!.
Over about 3 months it seemed there were some performance issues so I used super su to un-root, and went for a factory re-set.
I tried to do a software update once back up and running but, got the pop-up telling me it couldn't up-date b/c of knox (actually said system has been altered etc..)
So,,,,,
I plugged into my samsung keys and to update and next thing I knew I had gone from KitKat 4.4.2 to Android 5.0.2.
This also changed my build number, to LRX22G.T530NUUEU1BOE5.
I WANT MY ROOT BACK, , , question is HOW?
None of the numbers aside from model number (SM-T530NU) match up with the CF auto-root now, as they did before.
I'd like to be rooted before heading back to Lagos Nigeria on Monday 6/22/2015,, but I don't want to brick this thing prior to leaving and end up tab-less.
ANYONE HAVE TIME TO HELP?:fingers-crossed:
[email protected]
Click to expand...
Click to collapse
It's really easy to root 5.0.2 (I have the exact same model). What you need to do is flash TWRP through Odin and immediately boot into recovery and install superSU. Actually I think the download link is broken on that thread, so here is a working link. Download the tar file to your PC, and download the zip file from here and save to your tablet. I'll write more detailed instructions in a minute
---------- Post added at 11:09 AM ---------- Previous post was at 11:05 AM ----------
OK so once you have the files where they need to be, power off your tablet and boot it into download mode. Run Odin on your PC. Make sure to disable the auto-reboot option in Odin, this is crucial. Flash the recovery tar file with the AP button. Now when the flashing is done, your tablet will not automatically reboot (good), but just sit there, the only way to tell it's done is when Odin says it's done (Pass or Reset). Power off the tablet manually, then immediately boot into recovery (home, power, vol+). Install that superSU zip file. Boot system normally, run the superSU app and follow the prompts. Congrats, you're rooted on lollipop.

Sry to ask but, could you??? do a step by step?? for the worried
Or point me to the location of where something along a step by step is posted already. I'm not bad on computers but android I'm still a serious noob.

How to root a 10.1 Tab 4 also links for 8.0, 7.0
This should work provided you use the correct recovery for your model
Preparation: Read everything and make sure you understand. I attached Odin v3.09, v3.10.6, v3.10.7 and 3.11.1. Odin 3.11.1 is recommended. Download the one you want and extract the zip to PC desktop. Also on the tablet enable usb debugging and mock locations in developer settings. Make sure you have the proper USB drivers for your PC. A quick note on file names: development code names for the Tab 4 series are as follows: matisse = 10.1, millet = 8.0, degas = 7.0
Download the twrp-3.0.0.9_matisse_20160314-0843.tar file (this is a twrp recovery that works for wifi, 3g, and lte 10.1 models) and save to PC. Download the superSU zip file and save to tablet storage. Obviously save the files somewhere easy to remember, and easy to navigate to.
Power off tablet. Boot into download mode (hold vol-, home, and power all at once in that order), then hit vol+ to continue
Run Odin. Connect tablet via USB. Hit AP button in Odin, select the TWRP tar file
Disable the "Auto-Reboot" and "Re-Partition" options in Odin, this is critical to success
Flash (click start). When it's done, the progress bar will be full and Odin should say something like "RESET!"
Hold the power button to power down the tablet. Then immediately hold vol+, home, and power (all at once, in that order) to boot into recovery. THIS MUST BE DONE BEFORE REBOOTING NORMALLY!
Install the SuperSU zip file that is saved to your tablet (tap the install option in TWRP, navigate to the zip file).
Reboot system (normal reboot). When android is booted, run the superSU app and follow the prompts; i.e. update the binary if it asks you to, choose normal install, be patient while it installs (takes a while) and reboot if it tells you to
Accompanying screenshots:
Step 3:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4:
Step 5:
Step 7:
Tab 4 8.0 TWRP: Tab 4 8.0 unified TWRP (remember millet = 8.0; matisse = 10.1)
Tab 4 7.0 TWRP: SM-T230/NU/T231 (credit to sub77), SM-T230NT (Philz), SM-T235/Y (credit to CTXz), SM-T237P use Philz
Credit of course goes to sub77 for the 10.1, 8.0, and 7.0 TWRP builds, CTXz for TWRP for degaslte moonbutt74 for Philz CWM, and to chainfire for all things superSU. I'm just trying to help and/or point people in the right direction

USB and Remote installation
Prior to getting started should USB debugging be enabled? As well as Allow mock installations??

rnerger said:
Prior to getting started should USB debugging be enabled? As well as Allow mock installations??
Click to expand...
Click to collapse
Yes

Double-checking
Hi and thanks for this info! This is my first post here.
I am seeking to root my SM-T530NU so that I can [attempt to] remote control the device using AirDroid for my business. Currently, I am stuck with TeamViewer which works reasonably well enough but comes with a *very* pricey license north of $60 a month which I am having a hard time stomaching. However- I need to have full mirror over the web, so I am stuck with TV unless I can find another option. (Open to suggestions here.)
Anyhow- I want to try and root the device, however I have never rooted before and am somewhat confused by the info I am finding. Your post here just says I need to match the model number, while others I have come across claim that I need to match the build number as well. In my case, the build number is: LRX22G.T530NUUEU1BOE5.
Please clarify on whether or not the method you posted above should work on this build. If you could also direct me to a good resource for what I need to do to back up my device in case root attempt bricks it, that would be much appreciated as well!

mcmarturano said:
Anyhow- I want to try and root the device, however I have never rooted before and am somewhat confused by the info I am finding. Your post here just says I need to match the model number, while others I have come across claim that I need to match the build number as well. In my case, the build number is: LRX22G.T530NUUEU1BOE5.
Please clarify on whether or not the method you posted above should work on this build. If you could also direct me to a good resource for what I need to do to back up my device in case root attempt bricks it, that would be much appreciated as well!
Click to expand...
Click to collapse
This method will root your device, it's intended for all 10.1 models, but I have the exact same model and firmware as you and this is how I rooted. Flash this file through Odin in case you somehow brick, but if you follow the directions you'll be fine and won't need it
Back up any files, media, etc you have stored on internal storage, but again, you shouldn't need this, it's just to be safe

Thanks for the link to the file! I've been trying to use Odin and so far... no go. I disabled Windows Defender, switched to a shorter stock USB cord from Samsung. When I hit "Start" it initiates, then just gets stuck on recovery.img and nothing happens.
I've also tried Heimdall and can't seem to get that to work either. When I go to save the PIT, it fails. I was also reading a recent thread on github about an issue with newer bootloaders,, so maybe that is the problem with Heimdall.
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
I wish that Odin would just work... any thoughts on what else to try?

mcmarturano said:
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
Click to expand...
Click to collapse
I don't know exactly what your setup here is but it sounds like you're doing something wrong. It should be tablet > USB cable > USB port on either laptop or PC:
Also Odin has been known to be finicky it's best to use the USB cable that came in the box with the tablet. That said, any usb to micro usb cable capable of transferring files to/from the tablet in normal android should theoretically be able to work with Odin, I've rarely had issues using different cables.
I've never needed to use Heimdall so unfortunately I can't help you there, although I can say it should not be needed for this task.

mcmarturano said:
Thanks for the link to the file! I've been trying to use Odin and so far... no go. I disabled Windows Defender, switched to a shorter stock USB cord from Samsung. When I hit "Start" it initiates, then just gets stuck on recovery.img and nothing happens.
I've also tried Heimdall and can't seem to get that to work either. When I go to save the PIT, it fails. I was also reading a recent thread on github about an issue with newer bootloaders,, so maybe that is the problem with Heimdall.
One thing that might be a problem..? I have an Asus Transformer and am using the USB port on the keyboard because I don't have a micro-to-micro cord. Could that be it?
I wish that Odin would just work... any thoughts on what else to try?
Click to expand...
Click to collapse
Hi . You must run guide from here http://androidxda.com/flash-samsung-stock-rom-using-odin Only instead stock rom you must to use this recovery http://android.comtek-wiebe.de/OpenRecovery/openrecovery-twrp-2.8.6.0-matisse_wifi_3g_lte.tar .
Download to device to external sdcard this file http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 .
Go to recovery and install tis zip from external sdcard .
Reboot .
Now you have root .

Meh nevermind
---------- Post added at 10:52 AM ---------- Previous post was at 10:38 AM ----------
mcmarturano said:
I wish that Odin would just work... any thoughts on what else to try?
Click to expand...
Click to collapse
It appears the tar file for version 2.8.7.0 is malfunctioning, did you try the 2.8.6.0 tar file?
I just flashed the 2.8.6.0 tar file through Odin successfully, I guess there just must be some problem with the 2.8.7.0 file unfortunately

TWRP 2870 fixed

Yes- That is my basic setup. I have the micro-USB port on the tablet connected to a regular USB port on the computer using the cord that came from Samsung. At first I tried another cord I had that was longer, then learned the length/quality of the cord could cause FAIL, so then I tried the stock cord. Unfortunately, that did not work either.
I was just wondering if the problem might be the USB port. First off, I had trouble at first getting the tablet to connect properly.... it kept connecting/disconnecting. What I tried to remedy this issue was to remove the port driver from Device Manager and reboot the computer to re-install it. After that, the tablet stayed connected... but still FAIL on flashing the recovery image.
The device I'm trying to flash from is a Asus Transformer Book... it has two USB ports- a regular 3.0 port connecting through the keyboard and a mini port on the screen/motherboard component. Since these two components can detach from one another, I'm just wondering if maybe the connection isn't good enough for Odin.
I have another laptop I can try to flash from, so I guess I will try that next. Unless you have any other thoughts/suggestions?
Thanks again for your help!

mcmarturano said:
Yes- That is my basic setup. I have the micro-USB port on the tablet connected to a regular USB port on the computer using the cord that came from Samsung. At first I tried another cord I had that was longer, then learned the length/quality of the cord could cause FAIL, so then I tried the stock cord. Unfortunately, that did not work either.
I was just wondering if the problem might be the USB port. First off, I had trouble at first getting the tablet to connect properly.... it kept connecting/disconnecting. What I tried to remedy this issue was to remove the port driver from Device Manager and reboot the computer to re-install it. After that, the tablet stayed connected... but still FAIL on flashing the recovery image.
The device I'm trying to flash from is a Asus Transformer Book... it has two USB ports- a regular 3.0 port connecting through the keyboard and a mini port on the screen/motherboard component. Since these two components can detach from one another, I'm just wondering if maybe the connection isn't good enough for Odin.
I have another laptop I can try to flash from, so I guess I will try that next. Unless you have any other thoughts/suggestions?
Thanks again for your help!
Click to expand...
Click to collapse
Setup is OK, were you using 2.8.7.0 or 2.8.6.0? Try 2.8.6.0 if you haven't already

repey6 said:
TWRP 2870 fixed
Click to expand...
Click to collapse
OK I will try that too. Thanks!

thisisapoorusernamechoice said:
Setup is OK, were you using 2.8.7.0 or 2.8.6.0? Try 2.8.6.0 if you haven't already
Click to expand...
Click to collapse
SUCCESS! 2.8.6.0 worked like a charm. Thanks a million!

Still have not done this but intend to soon. What about UN-root??
Is there a special way that I will have to go about UN-rooting ???

I just got the SM-T537A variant for my wife, will this procedure work for that model as well?

PDADoc said:
I just got the SM-T537A variant for my wife, will this procedure work for that model as well?
Click to expand...
Click to collapse
No, sorry, you can't have a custom recovery or custom kernel on that model because of the locked bootloader. I think people have been routing that model with towelroot or kingroot

SM-G9287 Root?

Any Information of the root of this version? I haven't found anything yet

johnyx1989 said:
Any Information of the root of this version? I haven't found anything yet
Click to expand...
Click to collapse
Nor me

It is rooted, however the information is in Chinese on bbs.52samsung.com
Will trip Knox, will require 3rd party kernel, come with rwrp 2.8.7.0
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

Using arter97's 928C kernel. Works fine for me.

Rooting G9287
kebong said:
Using arter97's 928C kernel. Works fine for me.
Click to expand...
Click to collapse
This is a promising quote. I've been onto various chinese website and translated the pages, downloaded various TWRPs for the G9287 but flashing it doesn't complete. It doesn't fail but it doesn't pass either. Kebong. If you've managed to root a G9287 please could you go into a bit more detail? I can see on chinese forums that there are ROMs so it must be possible to root. So close yet so far.
Thank you.

i also fails, this is what i got try flash both TWRP and Philt all fails with this message (i dont understand chinese). I try to work on research and found that it might need to download Crom service from galaxy store to unlock bootloader, but i cant find in my Galaxy Apps store (any one have link for APK so i can try it). Or anyone knows what is going on attached is the screen shot i got

Hi, ive tried both arter97's kernel and the one in the chinese forum. Both work, but in the chinese kernel NFC wont turn off so i ditched it for the former kernel despite the 9287c not being formally supported.
I first installed the PhilZ touch recovery and flashed the kernel as you normally would. No issues so far and it is my daily driver.

kebong said:
Hi, ive tried both arter97's kernel and the one in the chinese forum. Both work, but in the chinese kernel NFC wont turn off so i ditched it for the former kernel despite the 9287c not being formally supported.
I first installed the PhilZ touch recovery and flashed the kernel as you normally would. No issues so far and it is my daily driver.
Click to expand...
Click to collapse
Have you guys tried using CROM Settings app from the samsung store first and then rebooting in download mode and installing respective recoveries?
Give it a go

kapeedp said:
Have you guys tried using CROM Settings app from the samsung store first and then rebooting in download mode and installing respective recoveries?
Give it a go
Click to expand...
Click to collapse
can you uploaded me crom apk i cant download it in samsung store i wanna flash cuatoms recovery. thanks

kebong said:
Hi, ive tried both arter97's kernel and the one in the chinese forum. Both work, but in the chinese kernel NFC wont turn off so i ditched it for the former kernel despite the 9287c not being formally supported.
I first installed the PhilZ touch recovery and flashed the kernel as you normally would. No issues so far and it is my daily driver.
Click to expand...
Click to collapse
Happy things, G9287C ROOT has been completed today
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

china chenli! thanks for good news but can you please tell us how you managed the root?

System Update - no command - in recovery
china chenli said:
Happy things, G9287C ROOT has been completed today
Click to expand...
Click to collapse
I found CROM system app which fixed the first stumbling block. Finally I could flash a custom (Philz) recovery via odin. It passed. Brilliant. However I press all the buttons at the same time to get out of bootloader. I can't stop it booting up, but I just power down again then boot into recovery.
At this point it shows a lying down android and says 'system update...'. After a few seconds it says 'no command' then boots into the stock recovery with no apparent change. It still boots up but not changes seen. I've had a search around forums. The issue is mentioned but no solution found.
So close, yet so far!
---------- Post added at 03:16 PM ---------- Previous post was at 02:27 PM ----------
Bathhope said:
I found CROM system app which fixed the first stumbling block. Finally I could flash a custom (Philz) recovery via odin. It passed. Brilliant. However I press all the buttons at the same time to get out of bootloader. I can't stop it booting up, but I just power down again then boot into recovery.
At this point it shows a lying down android and says 'system update...'. After a few seconds it says 'no command' then boots into the stock recovery with no apparent change. It still boots up but not changes seen. I've had a search around forums. The issue is mentioned but no solution found.
So close, yet so far!
Click to expand...
Click to collapse
Okay - so, when you've flashed via odin, hold down all the buttons to reboot but DON'T HOLD THEM FOR TOO LONG! Immediately jump to to home, vol up and power and hold that. It's all about the speed. When I did this it booted straight into Philz. Don't let it reboot. That's the key. After 3 weeks of trying. I'm finally rooted.
For CROM Settings - do an internet search. I found one that said it was for standard S6. It worked fine for S6 Edge+.

Here you go guys CROM Settings

What are you guys using the CROM for? @[email protected]

We use CROM because otherwise cannot flash anything by odin. I just successfully root.
Anybody able to create International Samsung Keyboard in flashable zip.? Samsung Chinese keyboard lack a lot of language and also not applying keyboard according to theme change. I try push SamsungIme and Lib file from G928C dump file and set permission with no luck. I think flashable zip should running fine.

using http://bbs.gfan.com/android-8073937-1-1.html
for me - nice rom
only must translate aurora setting and weather in english- have russian only
http://postimg.org/image/sunlpbo9f/
http://postimg.org/image/st8735lxh/
http://postimg.org/image/4ocye724z/

ROOT
With me is under baseband version: G9287ZHU1AOH5. Can I root my phone too?
How to use this CROM (APK)?Is there Philz for my G9287?

SM-G9287 root via Odin
To root Samsung Galaxy S6 Edge+ SM-G9287 variant or with G9287ZHU1A0H5 baseband version via Odin, follow these instructions:
****WARNING: This will trip your device's KNOX WARRANTY.****
I am not responsible if during the rooting process you brick your device or make it completely dead.
This is just a guide how to root your device.
1. Download these files to your PC:
> CROM Service​4shared.com/mobile/2CaRP69sba/CROM_Service.html​> Odin3 v.3.10.7​4shared.com/rar/74xTnC-Rce/Odin3_v3107.html​> Smart Switch​samsung.com/us/smart-switch/assets/downloads/Smart_Switch-PC_4.0.15093_11.exe​> G9287 Tar File​4shared.com/file/PBnmMkgsba/G9287-Root.html​2. Install Smart Switch in to your PC.
3. Transfer CROM Service into your device and install it.
4. Open CROM Service and choose option that unlocks your device.
5. Unzip and run Odin3 to your PC.
6. Make sure your device has a battery life at least 60%.
7. In your device, enable OEM unlock and USB debugging.
8. Turn off your device and reboot to the Recovery Mode (push Volume Down + Home key + Power key buttons for 2-3 seconds).
9. Push Volume Up button to continue.
10. Connect your device to your PC. Odin3 must notice that you have connected your device, so on the tool you must see the “added” message displayed along with the ID:COM section which now should be blue.
11. In Odin3, click "AP" button then search for the tar file you had downloaded.
12. Select "Start" from Odin3 and wait while your device is being updated or rooted.
13. Finally, when the installation procedure is over on Odin3 you will see the “pass” message displayed and your device will automatically reboot.
14. Disconnect your device from your PC.
14. CONGRATULATIONS! Your device is now rooted.
**all credits goes to netded.com. :highfive:

where can I find Debud and OEM? I do not find it.

kennyshrek said:
where can I find Debud and OEM? I do not find it.
Click to expand...
Click to collapse
you have to enable developer mode click on build number until you get it
---------- Post added at 08:35 PM ---------- Previous post was at 08:28 PM ----------
Yanyan_FTW said:
To root Samsung Galaxy S6 Edge+ SM-G9287 variant or with G9287ZHU1A0H5 baseband version via Odin, follow these instructions:
2. Install Smart Switch in to your PC.
3. Transfer CROM Service into your device and install it.
Click to expand...
Click to collapse
Just wondering.... Why do we need to install smart switch, can't we just transfer CROM to the device and install it. What is Smart Switch needed for. Thanks!

Tab S2 8.0 (T710) Android N Firmware- link

Hello.
I have managed to get the update file for Android N for the T710 variant of the Tab S2. The version I'm linking is for the UK region.
Here is the mega.co.nz https://mega.nz/#!xAAFQDqa!rZSJEqdEjNZpK59xggKxVRKukLXNm2oi472I4Rx-JSs
Make sure the select all three files to flash: AP, BL and CSC.
As Dariusdd pointed out, the update clears all your user settings and files.

only t815 not got yet...

Thank a lot for sharing...much faster download ...

It worked fine, just a future warning for everybody who installs it: it will wipe your internal memory, move your Titanium Backup data to your SD card or PC (don't be like me).

Dariusdd said:
It worked fine, just a future warning for everybody who installs it: it will wipe your internal memory, move your Titanium Backup data to your SD card or PC (don't be like me).
Click to expand...
Click to collapse
Mine stop flashing in user data...
Just use ap file in odin... Or i need all file to flash ?

I only selected the AP part of the install. Did you guys check the BL and CSC MD5's?

hwooei said:
Mine stop flashing in user data...
Just use ap file in odin... Or i need all file to flash ?
Click to expand...
Click to collapse
I did it with AP only as well and it's working fine. Came from stock 6.0.1.

I flashed all 3 files, also I can't seem to find the mobile hotspot options you've told us about. Might be because you didn't flash the other 2 files or because it was a dirty flash?

Dariusdd said:
I flashed all 3 files, also I can't seem to find the mobile hotspot options you've told us about. Might be because you didn't flash the other 2 files or because it was a dirty flash?
Click to expand...
Click to collapse
Thanks for the info. I flashed the rest of the files and the useless options are gone.

for those stuck in Odin, use Odin 3.12.3
Link: https://forum.xda-developers.com/attachment.php?attachmentid=3877298&d=1474046912
---------- Post added at 09:15 PM ---------- Previous post was at 09:12 PM ----------
also just to let you guys know, rooted it with twrp_3.1.0-1_sm-t710 and magisk v12
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Ather said:
for those stuck in Odin, use Odin 3.12.3
Link: https://forum.xda-developers.com/attachment.php?attachmentid=3877298&d=1474046912
---------- Post added at 09:15 PM ---------- Previous post was at 09:12 PM ----------
also just to let you guys know, rooted it with twrp_3.1.0-1_sm-t710 and magisk v12
Click to expand...
Click to collapse
It's been like a year since I used odin so would you mind sharing the step by step instructions you followed to update from 6.0.1 to 7.0 and to root it with magisk?
Thanks!

any issues with wifi 5g for North America? seem to remember having to change router channels last time i did this for 6.0...

Znil said:
It's been like a year since I used odin so would you mind sharing the step by step instructions you followed to update from 6.0.1 to 7.0 and to root it with magisk?
Thanks!
Click to expand...
Click to collapse
First, you need to get Samsung USB Drivers from Here
then get odin from my link in the post, backup all your data because your internal sdcard will be wiped clean
power off your tablet, hold the home button, vol down and power it up, press vol up when asked to continue to Download Mode
Now, run Odin 3.12 and connect your device, you should see Added!! on the left side, extract the rom zip where you'll end up with 3 files (AP,BL,CSC), select the 3 files in their respective slots (AP will take some time) but when you're done, press start and wait for the tab to boot up
for rooting, download this twrp recovery: https://www.androidfilehost.com/?fid=529152257862710032
and download Magisk v12 from here: http://tiny.cc/latestmagisk
copy the magisk zip to your tab, power it off and again enter download mode, connect the tab and run odin, select options (2nd tab) and untick Auto Reboot, select the twrp in AP slot and click start
Once it says pass, hold down Power button and vol down to power off the tablet, but you'll have to quickly enter recovery mode by pressing the home and vol up button along with the power button.
Once in twrp, swipe to allow modifications, click install, browse to the magisk v12 zip file and install it, reboot to System and download magisk manager from play store.
Read all about magisk here
twrp thread here
lemme know if you need anything else

nolook said:
any issues with wifi 5g for North America? seem to remember having to change router channels last time i did this for 6.0...
Click to expand...
Click to collapse
Was just coming here to pust this. No 5GHz for NA, so we will need to hold out for a working copy. If you are intending to root it can be fixed, but I don't intend to.

Will it work on T715 Barnes Noble version?
Sent from my VS995 using Tapatalk

gordec said:
Will it work on T715 Barnes Noble version?
Sent from my VS995 using Tapatalk
Click to expand...
Click to collapse
There is already a T715 version which appeared even earlier yesterday. That one is for Italy, but it should be fine.
Anybody else having issues with their Samsung account after rooting the tablet? I can't seem to be able to connect anymore after rooting, also for other users of SD maid: do not clear anything, it seems that one of the app's options breaks auto brightness and auto rotation.

Dariusdd said:
There is already a T715 version which appeared even earlier yesterday. That one is for Italy, but it should be fine.
Anybody else having issues with their Samsung account after rooting the tablet? I can't seem to be able to connect anymore after rooting, also for other users of SD maid: do not clear anything, it seems that one of the app's options breaks auto brightness and auto rotation.
Click to expand...
Click to collapse
how did you root the tablet? supersu I presume, if yes then that's why it's breaking the brightness and wifi, root with magisk because i remember the note5 and s7 had the same issues when supersu wasn't updated and the ramdisk kept interfering with the drivers

Ather said:
how did you root the tablet? supersu I presume, if yes then that's why it's breaking the brightness and wifi, root with magisk because i remember the note5 and s7 had the same issues when supersu wasn't updated and the ramdisk kept interfering with the drivers
Click to expand...
Click to collapse
I hoped that was the case, so I ended up clean flashing again and rooting with magisk last night, thinking that being a little newer it should work with Samsung's Android N.
I didn't have any issues with SuperSU either for several restarts, so I assumed it might've been because of SDmaid clearing the wrong stuff. Either way, I'll try backing up my /data before trying again, so that I won't have to reset the tablet for the 3rd time in case that was also related. LE: even after several reboots after clearing stuff with SD maid, I have yet to experience the difficulties I had while using SuperSU. Magisk is fine.
Also: I managed to make my Samsung account work properly now. I reset the "Samsung Account" application to its initial state (through SDmaid, but it might work with other stuff as well) and it let me log in properly.

Ather said:
First, you need to get Samsung USB Drivers from Here
then get odin from my link in the post, backup all your data because your internal sdcard will be wiped clean
power off your tablet, hold the home button, vol down and power it up, press vol up when asked to continue to Download Mode
Now, run Odin 3.12 and connect your device, you should see Added!! on the left side, extract the rom zip where you'll end up with 3 files (AP,BL,CSC), select the 3 files in their respective slots (AP will take some time) but when you're done, press start and wait for the tab to boot up
for rooting, download this twrp recovery: https://www.androidfilehost.com/?fid=529152257862710032
and download Magisk v12 from here: http://tiny.cc/latestmagisk
copy the magisk zip to your tab, power it off and again enter download mode, connect the tab and run odin, select options (2nd tab) and untick Auto Reboot, select the twrp in AP slot and click start
Once it says pass, hold down Power button and vol down to power off the tablet, but you'll have to quickly enter recovery mode by pressing the home and vol up button along with the power button.
Once in twrp, swipe to allow modifications, click install, browse to the magisk v12 zip file and install it, reboot to System and download magisk manager from play store.
Read all about magisk here
twrp thread here
lemme know if you need anything else
Click to expand...
Click to collapse
Thanks man, I really appreciate the explenation. It worked perfectly!

Znil said:
Thanks man, I really appreciate the explenation. It worked perfectly!
Click to expand...
Click to collapse
glad i could help