Develop Bugs

I need stock firmware from ANYONE SM-t807A it does not exist on the web.

I have spent days looking, turn on goes to kies firmware screen yet when i put in the model and s/n it shuts and the new samsung app to replace kies is of no help. I can get to the download screen and odin shows it up but no ATT 10.5 Tab S Sm-T807A firmware ANYWHERE.
Please help this is a very very expensive paperweight and im not affiliated with ATT so them helping me is out of the question.

Samobile.com

info.sven said:
Samobile.com
Click to expand...
Click to collapse
They dont have it for the SM-T807A

0 Results found
You searched for "sm-t807a"

It would better if you just explain what state the tablet is in and how it got to that state.
There is no official software for the t807a.

OK here how it goes,
The tablet was completely fine.
The original owner ( a family member) tried to root it and didnt accomplish it, somehow through his process it ended up softbricked.
I can enter he download mode for odin but no firmware for this LTE model.
When I turn it on it goes to the kies screen but kies doesnt recognize it, and when I enter the serial it buffers for 2 seconds then closes the process of kies.
Also it says device isnt supported and yes I have installed the right drivers and uninstalled kies numerous times.
The new replacement prog for Kies (forgot the name) is no help either.
Im terrified of what to do next as it does go to the odin screen just no firmware as I stated.

Any update, or could someone upload the stock firmware so i can use Odin on it.
Samsung told me ATT can flash it for free onto it so its deff a possibility however I do not have a ATT account so they cant help me.

It doesn't boot because the stock recovery has been wiped/replaced.
Thats assuming you have tried to boot recovery?
The att models are all bootloader locked.
I'm surprised a bootloader locked device even allowed an unsigned image to flash or did they use something like flashify?
The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image.

I was used with something like kingroot.
"The stock ota update was posted by someone here a while back. Your only chance is to pull the recovery from it and try and flash it in download mode. However odin may refuse to flash it.
If I can find it I can pull out the recovery.img and post a modified cf_autoroot which will try and flash the original recovery, that's if odin will even accept the image."
this i would highly appreciate as the firmwares not deleted just corrupted.

i have searched the whole web.
here is the link to the pulled stock sm-t807a files from a xda member
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing

PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files

synphonica said:
PowerfulJY, any successfull update with your SM-T807A journey?
I have the same problem as you, and Odin refuses to flash your firmware files
Click to expand...
Click to collapse
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.

I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.

also odin was used.

ashyx said:
The images won't flash as they are raw unsigned images.
The update should contain a signed recovery image, but may still not flash with odin as the tar package you make will not be signed either and odin may refuse to flash
There may be a way though, another member managed to brick their device by flashing twrp using Heimdall, but couldn't then flash back the stock recovery with Heimdall.
If somehow the stock recovery can be forced to flash with Heimdall then there's a chance of unbricking the device.
Click to expand...
Click to collapse
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.

PowerfulJY said:
I worked just flashed the FW part through AP did it on a friends pc all is back to new.
if you need a link for the ripped files just pm me.
Click to expand...
Click to collapse
Please explain in more detail what you have done for the benefit of others.
---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------
synphonica said:
Unfortunately, Heimdall shows the same behaviour as Odin has.
AFAIK they are using the same protocol and seems that recovery CRC/sign check done via device internally, not via flashing tool.
Click to expand...
Click to collapse
Did you use command line or gui?

I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.

PowerfulJY said:
I used GUI, i didnt do the bootloader or choose any special clickies, I simply tried another pc with the same FW and it flashed in a hearbeast with PASS.
USB hubs are the devil, TRY EVERY USB PORT YOU HAVE
Kies sucks so does the new one.
any issues PM me and ill set you straightm any public questions ask away.
You have to download the IMG files and use the IMG to TAR app, I will provide a ZIP with all tars included but I assure you dont start ****ing around with bootloader images stick to AP.
AT&T is he devil.
The new Rockstar Whipped Strawberry OWNS, Oraneg Creme is Meh.
Click to expand...
Click to collapse
The gui question was for synphonica about Heimdall.
Are you saying you flashed the images with odin? Which version and which images?
This has been tried before and failed.
Also what do you mean you tried a pc with the same firmware, same firmware as what?

I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.

cluver53 said:
I'm new to rooting so be gentle, I just bought a Galaxy Tab S 10.5 sm-t807a (AT&T) with Android 5.0.2 Lollipop. I want to backup the stock ROM (firmware) so I can go back just in case I bricked it when rooting or installing custom ROM. I searched the web but there are no clear instruction on how to do it for an unrooted sm-t807a. Can someone provide me with a step-by-step instruction? I can share my backup of the stock ROM afterward since there does not seem to be one on the web. Thank you in advance for your help.
Click to expand...
Click to collapse
You can only root with Kingroot, don't try any other method or you'll brick it nor can you install a custom kernel or recovery.
Once you have root you can pull the partition images with EFS PRO or PARTITION BACKUP.
The best way to have a back up is to catch the stock Firmware update.
This is tricky so research how to do it.
There is one backup I know of:
https://drive.google.com/folderview?id=0B7ndOWpeCEJ4NFVHZmtvTFN0UFU&usp=sharing

Getting My Tablet Back to Stock Firmware [SM-T800]

Hello XDA,
I am looking to update my Tab S to Lollipop. Problem is, I rooted it almost a year ago and do not know the method in which I did it. I'm guessing without knowing any other information, my best best bet would be downloading 5.0.2 from Sammobile (currently doing so) and using Odin 3.09? Is this the easiest way?
Also, if I'm located in the USA, what region do I want to use for the download? I didn't see anything that applied to me, so I picked an unknown region. Is there something else I should be looking for?
Android Version
4.4.2
Kernel Version
3.4.39-2947015
[email protected] #1
Build Number
KOT49H. T800XXU1ANK1
SE for Android Status
Enforcing
SEPF_SM-T800_4.4.2_0040

The quickest way would be to use Samsung Kies. The download is quicker but it installs immediately so you don't get to keep the download.
EDIT: Also the US region is called Cellular South.
Sent from my SM-T700 using Tapatalk

noxarcana said:
The quickest way would be to use Samsung Kies. The download is quicker but it installs immediately so you don't get to keep the download.
Click to expand...
Click to collapse
Is that what Smart Switch Mobile is? Do you happen to have a link for a short guide? And will I still need to download the stock firmware when using Kies?
And thanks for clearing up the region question.

http://www.samsung.com/in/support/usefulsoftware/KIES/#none
Use the link to download Kies, install, connect tablet to pc and open Kies. From there you'll know what to do. No guide necessary. No need to download the firmware either. Kies is automated once you select upgrade.
EDIT: There are two versions of Kies. Grab Kies3.
Sent from my SM-T700 using Tapatalk

Thank you! You were right, Kies3 immediately recognized that I did not have the latest firmware. So now I'm waiting for the update to download and implement itself.

I am in the exact same situation as you.
Not able to take the OTA even if i undo root via supersu
Kies detected that there was an update. But BEEN HOURS with "Preparing software update components for Galaxy Tab S"
I closed it and I am trying with Smart Switch .. same .. been 1 hour now and nothing happens.
How could I flash the latest firmware? Thanks
nickatnite905 said:
Thank you! You were right, Kies3 immediately recognized that I did not have the latest firmware. So now I'm waiting for the update to download and implement itself.
Click to expand...
Click to collapse

mic141414 said:
How could I flash the latest firmware? Thanks
Click to expand...
Click to collapse
You may want to check with other sources, but my initial thought before getting a response here was to download the current firmware build and use the Odin tool. I'm assuming it would work for you.

nickatnite905 said:
You may want to check with other sources, but my initial thought before getting a response here was to download the current firmware build and use the Odin tool. I'm assuming it would work for you.
Click to expand...
Click to collapse
I have downloaded the stock ROM from some Russian web site which then directed me to some Google drive, a 1.6GB download, in my case SEE-T805XXU1BOD1-20150511102748.zip
I then used Odin to flash it - Select BL for "T805XXU1BOG2_bootloader.tar.md5" (stock bootloader) and AP for "T805XXU1BOD1_T805OXX1BOD1_T805XXU1BOD3_HOME.tar.md5" (stock ROM)
I believe that the above procedure works under almost all circumstances, root or no.
I then made plenty of backups with TWRP so that I do not have to use Odin anymore, I simply restore the stock ROM from backup (plus I get all my applications and system as I want it rather than having to re-do everything from scratch each time).
And just to say that all the OSes I have downloaded so far, they all had problems, so I end up restoring the stock ROM within hours of installing a new OS.

Need some help deodexing stock ROM

I'm new to making modifications on my phone and I need some help deodexing the ROM.
I've got a Note 4 from Sprint running Android 5.01. I've installed TWRP and made a backup. I've also downloaded the version of Xposed that I want to get installed. But when I tried to flash Xposed to the phone, I got a message that a deodexed ROM was required.
I know that Titanium Backup can be used to deodex apps but it doesn't work with the framework. Is there a tool or app that anyone can recommend to me for this? Or is there a deodexed version of Samsung's stock ROM that I can easily swap out with the existing ROM?
Any help would be much appreciated.

Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk

Thank you and some additional questions
samep said:
Android 5.0.1 does require deodexed ROM and this thread should help you or you could try Tickle My Android by ticklefish on XDA to deodex ROM. Google that one but here's the thread for the Xposed you're looking for (Android 5.0 only).
https://forum.xda-developers.com/showpost.php?p=60857320&postcount=1
That may help but I'd recommend either KitKat or Lollipop 5.1 or higher so you could use the Odex stock ROM or custom ROM- Odexed or deodexed. KitKat uses the standard rovo89 Xposed framework for KitKat. Lollipop 5.1 and Marshmallow uses Wanam unofficial Xposed framework; it works for both Odexed and deodexed ROMs though it didn't always when I used it on Lollipop but updates allow for better with Odexed ROMs when adding system apps.
You'd have to provide bootloader version to advise which path to take. Maybe your bootloader is OB7 and you've read warning about updating bootloader past that prohibits using KitKat or Android 5.0.1 again but there are methods that make it possible with the updated bootloader and Android 5.1 kernel but not degradable with Odin.
But IMO, Android 5.0.1 is not a good place to be. Android OS updates are notably benching faster so there's that but others prefer KitKat for simplicity and theme flexibility but less secure. Android 5.0.1 is neither of those and less secure. I'd consider KitKat or higher update but not settle for Android 5.0.1
You can use Galaxy Tools or this app to get your bootloader version.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
But you may want to get your MSL number before updating if you can't get it from Sprint. Sprint will give it to you if you're a Sprint customer with phone paid in full and good standing on account. But I'd get it before updating anyway if you don't have it already.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.

jmalmberg said:
Thank you for all of the information. It sounds like I should probably upgrade to Android 5.1. I'm not sure how I would go about doing that though. Can you point me in the right direction? Is there a guide to do this somewhere? My bootloader version is N910PVPU2BOE1.
Click to expand...
Click to collapse
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk

samep said:
You can upgrade through Odin. There's a stock tar thread here with Odin download link and simplified instructions.
https://forum.xda-developers.com/showthread.php?p=63868221
If you're looking for a custom ROM, decide which ROM, check its update version and follow OP install instructions for flashing help and advice. Get the tar from thread above; it has older versions too.
If you're interested in a Lollipop custom ROM, check out the Note 5 Ultimate ports by tx_dbs_tx to see if they will work for you. Those require stock tar OK1 version and have detailed install instructions that should be followed, if interested.
You're gonna want to stop auto updates immediately after updating and also after flashing custom ROM to avoid update download and nags to update.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?

jmalmberg said:
Thank you for this. I've downloaded Odin but have a couple of additional questions. First, I only see two files with Odin. A .exe and a .ini file. Is that correct?
Second, does is matter which one of the MD5 files I download and flash over or will any of them work for me? Are there any that you consider to be better than the others?
Click to expand...
Click to collapse
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk

samep said:
The .exe is an executable to launch Odin. Place the unzipped contents in an Odin folder or whatever you name it. I prefer to have Odin in my stock tar folder along with TWRP so it easily finds those to load and flash. Grab this img.tar for Odin flash of TWRP:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Be aware that TWRP recovery flash requires you to uncheck Odin option of auto reboot and wait for flash to finish but make sure you see COM added in highlighted field before starting. Upon success, remove USB cable and battery and wait at least 30 seconds and boot into recovery. If you fail to boot into recovery on initial boot after TWRP flash, the stock recovery will restore itself and you won't see TWRP later when booting recovery.
Be aware that Odin flashing tar files will utilize the AP slot to load and flash. Stock tar will take a while to check the md5 so wait until you see you see your device added as COM in the Odin log and highlighted field before you start a flash, particularly stock tar; expect a wait period for md5 verification.
The stock tar you choose would depend on the ROM you choose. I don't know your preference but for Odin, you should limit your choices from OG5 and up to latest. You can downgrade to lollipop or upgrade to marshmallow at will but in your case, I think either is an upgrade for you.
Lots of choices so pick one and look in OP for what update it's based on. Then you'll know which update to download.
I only suggested the Note 5 Ultimate ports because you mentioned lollipop. The ROM is stable but read the OP and see if that's what you want. Custom ROMs usually give a list of broken features and install directions to consider complexity of install and setup and result to expect.
There's also stock ROMs or Cyanogen Mod (CM) ROMs. Each have their own appeal and following.
There is a marshmallow port based on Note7 but the degree of difficulty is higher. There's fix workarounds that may require extra steps and experience that you either have or will learn along the way and glean from searching thread. Up to you what to choose but backup stock first, once you Odin and get TWRP and then backup any ROM you like if seeking alternatives.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.

jmalmberg said:
Since this is my first time doing this, I think I want to keep it as simple as possible. So I'm going to stick with lollipop. The version that I'm thinking of using is:
OJ6 Lollipop TAR: N910PVPU4COJ6_N910PSPT4COJ6_SPR.zip
md5: 13ab3afb59130382b2ce0f9113a193a8
I've opened Odin, put the phone into download mode and attached it. Odin can see the phone but I haven't tried to do anything yet. Sorry to pepper you with questions but I really don't want to brick my phone, so here are a few more.
1. When I flash the new ROM, will my phone still be rooted or will I need to do that again?
2. If I don't repartition the phone, will my data and apps still be there when I reboot?
3. If this doesn't work, can I restore my old system using a backup that I made with TWRP?
Thanks again for the assistance. I really appreciate it.
Click to expand...
Click to collapse
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk

samep said:
Repartition should only be used if there's a problem. Like I said, use the Odin defaults for stock tar.
Stock tar is factory firmware so yes, you must root again. Think of it as out of the box stock but your data and user apps should remain. No guarantee so you should backup to extSdCard but you never really know if the internal memory gets wiped or not. Usually not for those running touchwiz ROMs.
You could restore the backup but if the flash takes then there may be some compatibility issues.
It's often recommended to clean install ROMs for best compatibility so that's up to you if you want to risk keeping your user apps and data on there. You can expect longer boots to optimize the apps but consider the stock tar would boot right up, if installed cleanly.
Custom ROMs will have to optimize applications. If you're also keeping the user apps, they'll have to be optimized again so that makes the initial boot even longer. You should consider cooling with forced air for these initial boots and have ample charge. I recommend 80% or more.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.

jmalmberg said:
OK, I think I'm ready to try this. Just want to make sure I've dotted all the "i"s and crossed all the "t"s.
Can you confirm the following procedures for me.
I've removed most of my apps to make the process go a little more smoothly. I've downloaded the ROM I want to flash. When I open Odin 3.12.3 and connect my phone, under Options, I remove the check mark by auto reboot and leave the box checked by F. Reset Time. Everything else under options is unchecked. Then to the right, I check the box next to the AP button and select the TAR for the ROM. I leave everything else alone. Is that correct?
I'm not sure what to do with the TWRP TAR file you had me download. Do I place that in one of the other boxes?
After that, I select start and wait for it to complete. Is there anything else I should know?
Thank you for your help on this.
Click to expand...
Click to collapse
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk

samep said:
You'll do two flashes with Odin in order to get to update required with Odin defaults, you flash the stock tar and let it auto boot. Close Odin when done.
Flashing TWRP requires the auto reboot unchecked because you need to boot into recovery on first boot after flashing TWRP.
Both are flashed in AP slot on separate Odin sessions because they're tar files. You'll need to Odin TWRP and root again after flashing a stock tar. For custom ROMs, consider the ROM zip is already pre-rooted so all you need is TWRP.
Unless you want to root stock, I'll leave that part out of this post.
Sent from my SM-N920P using Tapatalk
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
Do you have the USB driver for Note 4 installed on PC? If not, goto Samsung support and get the one for Note 4 from the download section.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?

jmalmberg said:
I was able to flash the ROM to the phone without any real issues. Thank you for your help on that. I wouldn't have got that done without your assistance and I really appreciate it.
After I was finished with the ROM, I used CF Auto Root to reroot the phone and then I tried to flash TWRP recovery. I'm having issues with TWRP.
I closed Odin and they reopened it as an administrator. When I click on the button next to the AP slot, it opens a file window. At that point I clicked on the extracted TWRP .tar file you had me download. The program just seems to hang and never actually shows up in the box next to the AP button. Any suggestions?
Click to expand...
Click to collapse
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk

samep said:
You shouldn't unzip or extract img.tar files but flash as downloaded. If it had a .zip extension, yes, but as I recall, it's not zipped nor need extracting.
It's already a tar file for flashing. Tricky annotation but I think it just means that it's been converted from .img to .tar and ready for Odin. I think only TWRP does that extension naming.
Hopefully, it's only hanging because Odin or phone doesn't know what to do with it. Pull battery and check that it still boots recovery and system. Then back to download mode to Odin without extracting img.tar file.
I guess if you extract properly, you're left with an image file but I wouldn't do it by extraction because you can download image files from TWRP without needing to convert. Just so you know, those .img files can be flashed in TWRP recovery to update whenever that happens again.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thank you! It worked.

jmalmberg said:
Thank you! It worked.
Click to expand...
Click to collapse
Now, hopefully you have ROM picked out and on extSdCard ready to flash.
I'd backup stock ROM to extSdCard in TWRP just in case.
Follow the OP on your ROM install. Enjoy!
Sent from my SM-N920P using Tapatalk

I need your all help. dead s9 / bricked

So i have a samsung s9 SM-G960F/DS version. i had have run TWRP on it and magisk + exposed and it worked fine. i had to uninstall exposed to log into some apps and then i would reinstall it agian. but when i ran the exposed unintaller the phone would not boot. i tryed diffrent things and it would not boot unless it had the exposed intalled on it. i did a complete wipe of the phone with TWRP and now i can´t install stock rom. i downloaded the latest stock ROM for my model and the latest odin that can handle the lz4 compression. bur when i but in BL AP CP CSC it just get stuck on system.img all the time. i there is simply nothing i have not tryed. and nothing works for me. The only think working is if i flash the TWRP then i can boot into recovery TWRP. thats it. i am at a point where i will pay anyone who can help me figure this out cause i almost lost all hope for this to work agian. So i really really hope someone here have an ide to what could work for me. every tip and trick i will test and if someone offer help via discord or somthing i would also be glad to hear from you.

Hi
Extract and flash bootload.img or hidden.img file from the main stock rom.
I'll check the actual file name for you when I get home later. Did experience that problem sometime back on my s6 edge.

Usually there is a small error message on the screen of the s9 if odin fails or stalls. It's small blue text, I have a feeling it's either 'magic string error' or 'SYSTEM not [Sec]' or close to it. I find this happens when flashing the wrong firmware for that model. Example, flashing G960N firmware for a G960F.
I just did a reflash and here are my exact steps for my G960F.
1. Download Odin 3.13.1
2. Make sure Samsung Drivers are installed
3. Grab the latest firmware for your device, my device is a G960F so I just picked the latest BRJ3 firmware with November patch from Updato. Just get the firmware for your exact model.
4. Extract the files from the ZIP file
5. Add all the correct BL, AP, CP and CSC files to odin.
6. Select nand erase
7. Boot S9 into download mode
8. Flash to phone.
Don't try to flash TWRP before installing the full firmwares and until the phone is setup.
If all fails, and because you seem to be able to install TWRP, then you can download TGP Kernel ROM and flash that. It is based on stock G960F firmware, has a nice aroma installer for selecting various things and tweaks. It also provides a clean install of Magisk if that's something you like.
Also be sure to flash no-DM Verify.

Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find

*Detection* said:
Make sure you're not trying to downgrade the bootloader, I'm sick of writing out the same guide each time and I just did it earlier today so shouldn't be hard to find
Click to expand...
Click to collapse
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.

zalik20 said:
thanks for the replies. the issue is fixed and the problem was the i last my "magic string" but a friendly person on the forum sent me the things needed to restore it and then restore to prerelease rom so i could upgrade to latest rom agian.
Click to expand...
Click to collapse
Why not ot share those items to help others in the forum.

nsnobel2 said:
Why not ot share those items to help others in the forum.
Click to expand...
Click to collapse
You should look for samfirm or frija tool . Those would help you get latest firmware for your phone. Download it , flash it with odin and everything should be fine. Just remember that its possible that as you would be on latest firmware, you might not be able to downgrade in future.

Samsung Galaxy Tab S7 Model SM-T875 finally Rooted

Hello. I have managed to Root My Samsung Galaxy Tab S7 Model SM-T875 with KNOX value 0x1 and no custom recovery has been installed. I am linking an image from Root Checker
bit.ly/3kOE6NW
Sorry for bitly link guys, this is my first post so not allowed to post url, pls understand
Only for SM-T875
If you have any other models, let me know, I will patch their boot.tar and provide link for the same
Steps for root :
Download and install the latest version of Magisk Manager
Make sure you have an unlocked boot loader
On your PC, download Odin and put your S7 into download mode
Flash the tar file listed here
I am linking the exact boot.tar image I used
bit.ly/3j4mYDw
Sorry for bitly link guys, this is my first post so not allowed to post url, pls understand
In Odin, select the AP option, make sure ur tab is connected in COM1 and then select the boot.tar file. Once flashed, you have to restart your device.
NOTE
Once this boot.img file is flashed you will get this an error saying your device is not on official firmware and you will have to hard reset your device, go ahead and hard reset your device, you might think its in bootloop but it is not. Once hard reset is done, your device will boot twice, make sure to press the power button each time to skip the unlocked bootloader warning. Once done, set up your tab as new one. Now Magisk Manager will not be installed on your device. For root , go ahead and install Magisk Manager again and this time Magisk will be installed in your device and your Knox value will be 0x1 and warranty will be void and device will be rooted
If any questions, please feel free to ask
Hope this helped you

Did someone confirmed?*I wait to got the root before to buy this model specifically

T870
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..

Sushantydv said:
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Click to expand...
Click to collapse
just copy and past the provided link address he gave into your browser and download

jionny said:
just copy and past the provided link address he gave into your browser and download
Click to expand...
Click to collapse
The link is for the t875 version mate.. i need image file for t870

Sushantydv said:
Hi, can you please upload the patched boot img for SM-T870?
Thanks in advanced..
Click to expand...
Click to collapse
Sure, here ya go
bit.ly/33DC7GM
If this img file is not flashing, make sure to tar it using 7-zip and then flash from ODIN.
This is the boot.img from the latest version of Android Q (release Sep 1) so make sure you're on the same version before flashing this.
Let me know if this worked or if you need the boot file for any other version
also, sry for bitly link, am not trying to profit out of this, once my 10 posts are complete, i'll post direct download links.
Thx for understanding

umibuzu said:
Did someone confirmed?*I wait to got the root before to buy this model specifically
Click to expand...
Click to collapse
Not that I should be saying this, but if you want to know, I have done the same steps on both of my Tab S7's and bot are working while being rooted. If you still want someone else to confirm, im totally fine with it. Thx for replying tho.

Sushantydv said:
The link is for the t875 version mate.. i need image file for t870
Click to expand...
Click to collapse
T870 XAR version. Be sure to select the proper ver... TH1 or TI4 or TJ4.
Updated 11-2-20
https://forum.xda-developers.com/galaxy-tab-s7/how-to/magisk-t4159291

Could you do t878?

jhill110 said:
T870 XAR version. Be sure to select the proper ver... TH1 or TI4 or TJ4.
Updated 11-2-20
https://forum.xda-developers.com/galaxy-tab-s7/how-to/magisk-t4159291
Click to expand...
Click to collapse
Is there a working custom recovery (TWRP) for the T875/870 yet? Haven't found anyone mention it so far.

rosrog said:
Is there a working custom recovery (TWRP) for the T875/870 yet? Haven't found anyone mention it so far.
Click to expand...
Click to collapse
Unfortunately no.

I have T875 TabS7 brand new I have Build number
QP1A.190711.020.T875XXU1ATI4 and device says upd are available ATJ4 Something. with october patch. The boot image you have linked is of which firmware ?. Should I update and then root.
EDIT:
Anyways i followed this guide by Dr ketan for rooting which i used for my Note 20 Ultra and it didnt work with patching AP file method.
https://forum.xda-developers.com/galaxy-note-20-ultra/how-to/guide-how-to-root-n20-ultra-t4147023
So i downloaded the latest firmware which was ATJ4 my CSC version was CAC so i downloaded same firmware from SAMFW(super website with downloads resumable via google drive option.
1. I extracted boot.img.lz4 from AP file of stock firmware downloaded and made a TAR file of it with 7Zip
2. Put it in phone and used magisk manager on tab to patch this file
3. Copy back to PC and flash via odin 3.14.3 in AP tab and uncheck auto reboot in ODIN
4. Booted straight into stock recovery and wiped/factory reset
5. Now i have root on Tab S7 T785.
Here is a link to boot file patched for TAB S7 N985 LTE Latest ATJ4 Firmware .
http://www.mediafire.com/file/mhss32jmt1b1oza/Patched_BooT_ATJ4_TAB_S7_N985.zip/file

Possible to Root SM-T878U ?

Smoker1 said:
Possible to Root SM-T878U ?
Click to expand...
Click to collapse
Yeah it might be.

I have gotten a TWRP up and running on my Galaxy Tab S7 but it's not functioning properly, I'll post the stable version here in case I figure out one haha.

I have the Tab S6 and I love it. I am thinking to buy the Tab S7+. I was very quick to root the Tab S6 and did not take much notice of the Knox trip. Is there any sell value if the tablet cannot have certain apps working such as secure folder? I understand even if you unroot and relock the bootloader then knox is still going to be changed to 0x1
My Tablet still seems to be 0x0 though.

CamronCamr said:
Yeah it might be.
Click to expand...
Click to collapse
Any luck on this? I also was dumb enough to get this T878U from ATT. I realize I have a signed locked bootloader. Is there any hope for us? I'm fairly technical and can follow directions

I'm in the same boat. Att locked out usb and wifi tethering. A rooted device would be very helpful.

Did you have any luck with magisk hide(safetynet)? I'm still waiting for fingerprint for magisk-hide-props-config.

Is this possible for the SM-T978U?

legokangpalla said:
Did you have any luck with magisk hide(safetynet)? I'm still waiting for fingerprint for magisk-hide-props-config.
Click to expand...
Click to collapse
On the latest Samsung Tab S7 T875 Stock firmware Android 11 and one UI 3.1 , i have it rooted with Magisk V22 , widevine is L1, and safetynet passed .
Running with following magisk modules
1. Magiskhide props Config (Just install no config set
2. Riru
3. Riru Edxposed
4. Universal safetynet Fix V2.00 Test version 2 Thanks to kdrag0n