Database Info

[Q] P6810 Problem! - Won't go to Recovery - Bootloop

Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.

edwing29 said:
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
Click to expand...
Click to collapse
You don't need a bootloader, it was already "flashed" when he flashed the stock official firmware - bootloader would have been included in that and PIT
If done correctly, the PIT should work, if not - unfortunately, most likely back for repair............ bummer
Without actually checking the above is HC, have you tried the official HoneyComb firmware ? Just don't factory reset in HC recovery

P6810 ICS LPP Bootloader
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure ONLY "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.

UpInTheAir said:
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
Click to expand...
Click to collapse
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:

edwing29 said:
Hi, thanks for your assistance...
I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the has is invalid.
Can you check them and re-upload if there's no problem?
Thanks again! :good:
Click to expand...
Click to collapse
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium

UpInTheAir said:
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, I just edited the previous reply.
Check it out, Thanks.

edwing29 said:
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
Click to expand...
Click to collapse
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.

UpInTheAir said:
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
Click to expand...
Click to collapse
Tried the steps above and still the same.
I had to flash back to the stock HC firmware because the ICS led into an infinite loop, at least HC let me turn off the device.
I'll wait for any other suggestions, thanks!
Sent from my GT-I9100 using xda app-developers app

All I can suggest is to send it away for repair.
JTag (riff box) by a 3rd party or Samsung.
If it's NOT a hardware issue, JTag should be much cheaper, and if successful, faster.
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
Sent from my GT-I9500 using xda premium

[Q] Need help! Can't unroot/unbrick Galaxy S3!

So let me start from the beginning;
I have Verizon's Galaxy S3 and had CyanogenMod 10.2 installed on it. After installing CM 10.2, I no longer had 4G/3G connection. After some research, I had discovered that it had to do with my device's APN. Anyways, what I found online was to unroot, and flash to a stock ROM, and wipe/reset factory settings, etc.
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop. After pulling the battery, I tried flashing the image again in ODIN, but the same thing happened, I figured this is what was known as a "soft brick". I followed another guide on here to unroot/unbrick the phone, which had me download another stock rom (stock.vzw_root66), as well as VRALEC.bootchain.tar.md5, and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5. Following the instructions had me PDA flash the VRALEC-bootchain.tar.md5 first, followed by the bootloader, and finally the stock image. However, I continued to get "FAIL!" after attempting to flash the VRALEC-bootchain.tar.md5.
Following another guide, it said to just try flashing the stock.vzw_root66 file, which I had done, and it succeeded, however, after the phone reboots, it says that I am using unauthorized firmware on my device, and to bring my phone to the nearest Verizon store.
Now, I have no idea what to do.
I'm using ODIN3 v3.07
Both the VRLEC.bootchain.tar.md5 and BOOTLOADER-I535VRALF2-618049-REV09-user-low-ship.tar-2-.md5 fails when trying to flash them onto my phone, and I don't want to proceed from here unless I know how to fix it, as to not damage the phone any further. Any help would be greatly appreciated!
The phone still boots into a stock recovery, and can still enter download mode. At this point, I just want my phone completely stock, as if I had just purchased it.

You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?

Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2

BattsNotIncld said:
You shouldn't be getting the "unauthorized firmware" warning after flashing root66, as that is a stock image. You could try to boot into stock recovery and perform a factory reset from there. I'm not even sure if that's possible I haven't used stock recovery in so long .
Besides that I don't know what would help you. Maybe try reflashing the root66 file or try a different stock image. Do you have a link to the exact root66 file you are using?
Click to expand...
Click to collapse
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
BadUsername said:
Boot into download mode and post what it says on the top left corner.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!

I'm pretty sure those download mode stats you have are from the new bootloader. When you said this:
I started by flashing a stock ROM found on this site (don't remember the name) however, after rebooting, my phone had gotten stuck in the white Verizon logo loop.
Click to expand...
Click to collapse
... I'm thinking you flashed a stock 4.3 ROM in ODIN and therefore locked your bootloader. This would also explain the yellow triangle when trying to flash root 66 afterwards. If I am correct, the good news is all you have to do is flash a stock 4.3 ROM to get back up and running. The bad news is you re-locked your bootloader and are stuck with TouchWiz.

WildWildWest42 said:
Sorry, I meant that it says unauthorized software, and it has the yellow triangle. I've tried reflashing the root66 file, which is the only thing that actually "PASS"'s in ODIN, whilst everything else consistently fails.
Since then, I've followed this tutorial (Specifically section 5)
http://forum.xda-developers.com/showthread.php?t=1762709
And downloaded that "VRALG1 4.0 ICS-http://www.mediafire.com/download/kk...w_ship.tar.zip" file that was recommended, and after trying to flash it in the PDA box of ODIN (With auto-reboot and F. Reset Time checked), it FAIL's.
After looking at the screen with download mode still on, right after the above file failed in ODIN, it reads:
_______________________________
ODIN MODE
Product Name: SCH-I535
Custom Binary Download: Yes (3 counts)
Current Binary: Samsung Official
System Status: Custom
Qualcomm Secureboot: Enable
Warranty Bit: 0
Bootloader AP SWREV: 1
SW Rev Check Fail : Fused 1 > Binary 0 **(This part I believe was added after the FAIL of trying to flash the VRALG1 4.0 ICS file.)
_______________________________
So far, the only file I've been able to successfully flash in ODIN is the stock.vzw_root66 file. Everything else constantly FAILs. Thanks for the ongoing help!
Click to expand...
Click to collapse
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
OK, you need to follow this guide, then your phone will be back to normal.
http://forum.xda-developers.com/showthread.php?t=2586319
Then read this entire thread to understand what you can do with the update.
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You're a life-saver! I just did this and my phone now works again! I couldn't thank you enough!

Rooted now wont boot ! Help please

Recently rooted my Tmobile Tab 2 with no issues that I could see, got my superuser going and verified the root with Root Checker all was good. Then went to boot into recovery and saw that I had not TWRP so I grabbed a recovery installed via Odin and then restarted tablet and when it did I had it boot into recovery gave me the message "recovery booting" then would just turn off anytime I would try the Download mode or Booting it would just flash the recovery booting, what can I do to fix this an start from scratch. ADB ? if so does anyone have some resources to link me to try

chilango1986 said:
Recently rooted my Tmobile Tab 2 with no issues that I could see, got my superuser going and verified the root with Root Checker all was good. Then went to boot into recovery and saw that I had not TWRP so I grabbed a recovery installed via Odin and then restarted tablet and when it did I had it boot into recovery gave me the message "recovery booting" then would just turn off anytime I would try the Download mode or Booting it would just flash the recovery booting, what can I do to fix this an start from scratch. ADB ? if so does anyone have some resources to link me to try
Click to expand...
Click to collapse
Yeah there is a bit of a trick to get recovery going the first time, and it's not mentioned much. After you flash the recovery if your tab starts to reboot it will rewrite the original recovery. You have to catch it and do the power + volume down to get it to go straight to recovery. It's all about the timing. It took me flashing it about five times before I caught it just right. Just keep flashing it in Odin until you get it, you're doing it right your tab is just fighting it. After you get it the first time you'll have no more issues.

or uncheck "Auto-Reboot" inside Odin and use the Button-Combi to boot directly from Download-Mode into recovery after flashing
First time my Counter = 5 until i got it work

Android-Andi said:
or uncheck "Auto-Reboot" inside Odin and use the Button-Combi to boot directly from Download-Mode into recovery after flashing
First time my Counter = 5 until i got it work
Click to expand...
Click to collapse
I was able to finally get it into download mode and flashed a new recovery and that fixed the error , I am now unable to load a rom onto my tablet keep getting the Status 7 error , maybe im just not understanding what the instructions mean from the sticky I saw about it, but anyway anyone can elaborate on it.

wich recovery installed? (please post name & versionnumber)

This was the exact recovery I used http://forum.xda-developers.com/showthread.php?t=2101044

chilango1986 said:
This was the exact recovery I used http://forum.xda-developers.com/showthread.php?t=2101044
Click to expand...
Click to collapse
What's your model number to your Tab? A ROM is specific to that model number...
Sent from my GT-P5110 using XDA Premium 4 mobile app

chilango1986 said:
This was the exact recovery I used http://forum.xda-developers.com/showthread.php?t=2101044
Click to expand...
Click to collapse
There is no new Rom out for your ATT / TMOBILE Galaxy Tab 2 10.1
Don't use Roms from P5100, P5110 or P5113 - this meight brick your Dervice!

SGH-T779 Model #
So with my type of tablet I can only use roms that are for the SGH-T779 or just go back to a stock rom?

chilango1986 said:
SGH-T779 Model #
So with my type of tablet I can only use roms that are for the SGH-T779 or just go back to a stock rom?
Click to expand...
Click to collapse
Yes, that's right! Or do you like to have a bricked device?
Never flash things from a different device to yours!
If you have a SGH-T779 - only use SGH-T779 -Files (e.g. Roms, Recoverys)
There's some development on CM for your device only, but no Rom released: http://forum.xda-developers.com/showthread.php?t=2364028

Android-Andi said:
Yes, that's right! Or do you like to have a bricked device?
Never flash things from a different device to yours!
If you have a SGH-T779 - only use SGH-T779 -Files (e.g. Roms, Recoverys)
There's some development on CM for your device only, but no Rom released: http://forum.xda-developers.com/showthread.php?t=2364028
Click to expand...
Click to collapse
So with the link you provided would I need to do the status 7 fix which is deleting the asserts line or is that necessary with this CM 10.1

don't remove assert lines - this will keep your device alive! there is no Custom rom out for your device! only a stockbased one.

[Q] Status 7 Error flashing Cyanogenmod 11

Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq

Zackpip said:
Whenever I attempt to flash a Cyanogenmod Rom for P3110 (Using that because I have a P3113) I get a Status 7 Error.
Anyone know how to fix this?
I use this to get the Rom: http://forum.xda-developers.com/showthread.php?t=2583316
Picture: http://prntscr.com/43qdlq
Click to expand...
Click to collapse
Flash the latest @Android-Andi Philz Touch or TWRP recovery and that should solve the problem (I recommend flashing the recovery with Odin or Heimdall.) Status 7 error usually means outdated recovery.
Link to @Android-Andi's recovery thread: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989

Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.

Zackpip said:
Well, that may have worked but before I did anything I let it charge, this is the message I got though: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
How should I go about this? I cannot do anything in Kies because the P3113 won't turn on. Whenever I plug it in to the PC if makes the sound of connecting, then disconnecting over and over again.
Click to expand...
Click to collapse
What exactly did you do that it did this? Did you attempt to flash the recovery in Odin or Heimdall? If Odin, which version?
Sent from my SGH-T989

Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.

Zackpip said:
Since the Cyanogenmod Rom failed flashing I tried to flash the stock firmware using Odin v.1.83 (Odin v3.09 and v3.07 wouldn't open) in order to get a Rom, then I tried to re-root it using v1.83, but it died when I was trying to. So, I decided to charge it and that's what happened. At least that's what I remember. My USB connector works but doesn't charge when connected to the PC, that's why it died. Other than that I do not believe anything else was done to it.
Click to expand...
Click to collapse
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989

jrc2 said:
OK, that makes more sense. If your device died during installation that will happen. If I use Odin, I usually use v1.85, but I have found Heimdall to be more stable and consistent. Can you boot into download mode?
Edit: also, what version of windows are you running?
Sent from my SGH-T989
Click to expand...
Click to collapse
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.

Zackpip said:
I am using Windows 8.1. Sorry for the late reply, had a little Family Reunion.
Click to expand...
Click to collapse
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989

jrc2 said:
There have been known problem using Odin on Windows 8, but I've done it multiple times. (I had kies installed if it makes any difference)
Anyway, do you have a Linux computer laying around somewhere? Depending on what happened during I installation, one can be used to maybe trip the device into a bootloop and then from there you can boot into recovery and flash a ROM. (I had to do this with my S2 after a power glitch while using Odin.) Odin isn't needed to root the tab. All you have to do us use Odin or Heimdall to flash a custom recovery (CWM or TWRP) and then flash SuperSU.zip in recovery.
Sent from my SGH-T989
Click to expand...
Click to collapse
I do not have a Linux machine anywhere.. Would that be the only way to fix it?

Zackpip said:
I do not have a Linux machine anywhere.. Would that be the only way to fix it?
Click to expand...
Click to collapse
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989

jrc2 said:
Not necessarily but it was just what I used and what worked. Does Odin detect the device on the firmware upgrade encountered an error screen?
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.

Zackpip said:
What do you mean by that? Odin shows this when I plug it in: http://prntscr.com/44yzf2
Nothing looks out of the ordinary.
Click to expand...
Click to collapse
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989

jrc2 said:
Odin does detect the device. So you SHOULD be able to go to www.samfirmware.com , click on "Firmware Database" and select the options in the drop down boxes for your tablet. Download the zip file (you'll need a sammobile account) and then extract the zip file. You should have a tar.md5 or a tar file that you can flash in Odin. Make sure your tab is charged and you run Odin as admin. After you flash that, reboot into recovery (will be stock recovery) and do a factory reset and wipe cache. Now you should be able to reboot into stock android (with TouchWIZ of course). To root from here, use Odin to flash latest @Android-Andi TWRP recovery and the flash @Chainfire's SuperSU.zip and you'll be rooted!
As always, I am not responsible for what happens to your device. Doing this will raise your flash counter and void your warranty, which is probably void already if you flashed anything before.
Sent from my SGH-T989
Click to expand...
Click to collapse
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.

Zackpip said:
Well, that partially worked. It does not show that anymore and it shows the Charging animation, but I can not boot into Odin/Download mode, or Recovery mode.
Click to expand...
Click to collapse
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.

jrc2 said:
That is quite weird. I have done the same thing at least 2 or 3 times. Try going to https://builds.casual-dev.com/jodin3/ Make sure you plug in your device before loading the above page. Your device should be detected when the page loads. In PDA put the latest TWRP tar file. Click start. It will say something like it needs a pit file and will reboot to find it. Click OK. It might fail but thats fine. Unplug your device. It will reboot and should show a bootloop. Now you should be able to reboot into recovery. If not, you might have to JTag but I don't know. For future reference, if a ROM is bootlooping, don't flash stock in Odin. Just do a full wipe and reflash the ROM and that should fix it.
Sent from my SGH-T989
EDIT: if the tab died during installation of an important file, it can ruin the device. www.mobiletechvideos.com does have JTAG service that can be used as a last resort. It costs around 50 US Dollars.
Click to expand...
Click to collapse
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!

Zackpip said:
I used Odin to re-download the stock firmware, and that worked. Thank you so much for all your help, it is working now!
Click to expand...
Click to collapse
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989

jrc2 said:
So you mean you redownloaded the firmware from sammobile and flashed with Odin or what? I couldn't figure out exactly what you meant. Glad to hear your tab is working again!
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did exactly that.

Zackpip said:
Yes, I did exactly that.
Click to expand...
Click to collapse
So it must have been a bad download then. You used Odin v1.87 or what? Also, you should add [SOLVED] to the thread title.
Sent from my SGH-T989

My tab sm t211 is not working

Dear sir
gkaxy tab sm t211 not working firstly i installed a new firmware with odin now its rebboting only in recovery and struçk in it show can not open dst can not find directory aftee struck in formating cache i tried to reinstall firmware with odin but its gives error completed write operation fail i unable to write anything in it tried to install twrp recovery still same error when i placw twrp zip in sd card it gives signature error kindly help me out
thanks in advanve

It sounds like you have softbricked your device you need to find original stock firmware and flash it
Sent from my Nexus 6 using Tapatalk

mack1234 said:
Dear sir
gkaxy tab sm t211 not working firstly i installed a new firmware with odin now its rebboting only in recovery and struçk in it show can not open dst can not find directory aftee struck in formating cache i tried to reinstall firmware with odin but its gives error completed write operation fail i unable to write anything in it tried to install twrp recovery still same error when i placw twrp zip in sd card it gives signature error kindly help me out
thanks in advanve
Click to expand...
Click to collapse
Try these troubleshooting steps for failed Odin flash.
https://forum.xda-developers.com/galaxy-s2/general/guide-t2345831
You might have to find a copy of the pit file for your specific model number and flash it in Odin along with the stock firmware. The PIT file tells Odin how to fix your partition table in case you have corrupted your partitions. If you don't understand how to use the PIT then you need to research to understand it, if you dont do it correctly, it can make things worse.
J_byrd said:
It sounds like you have softbricked your device you need to find original stock firmware and flash it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you read their post then you should have seen where they tried Odin but it failed. Telling them to do something that they already tried and failed at doesn't help them. Helping them figure out why it failed would be considered helping them.
Sent from my SM-S903VL using Tapatalk

Well considering that he has tried to flash that same file and is getting no were it is safe to say that it is corrupted​ or is not compatible with his device and it is safe to say that he is not trying to flash a stock rom otherwise what's the point. So instead of sending him on a mission to troubleshoot​ the problem that will end him finding a stock zip anyway. I suggested finding his stock zip and getting his device back before the troubleshooting begins.
Sent from my Nexus 6 using Tapatalk

J_byrd said:
Well considering that he has tried to flash that same file and is getting no were it is safe to say that it is corrupted​ or is not compatible with his device and it is safe to say that he is not trying to flash a stock rom otherwise what's the point. So instead of sending him on a mission to troubleshoot​ the problem that will end him finding a stock zip anyway. I suggested finding his stock zip and getting his device back before the troubleshooting begins.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just because they didn't have success flashing with Odin, doesn't mean that what they flashed was not made for their device nor does it mean the file they have is corrupted. There are many other reasons for failing with Odin than just a problem with the file, all of which are much more likely to be the issue than the firmware or file being wrong. Odin frequently fails even when using the correct firmware. It's usually a problem with the device itself or user error and not the firmware being flashed. Odin uses .tar and .tar.md5 to flash firmware by the way, not .zip.
With that being said, troubleshooting the Odin flash is the most logical course of action.
Unless, of course, the firmware is, as you said, for a different device. That's easily discovered by asking. @mack1234, is the firmware you flashed made for your specific model number?
Sent from my SM-S903VL using Tapatalk
---------- Post added at 05:52 PM ---------- Previous post was at 05:43 PM ----------
J_byrd said:
Well considering that he has tried to flash that same file and is getting no were it is safe to say that it is corrupted​ or is not compatible with his device and it is safe to say that he is not trying to flash a stock rom otherwise what's the point. So instead of sending him on a mission to troubleshoot​ the problem that will end him finding a stock zip anyway. I suggested finding his stock zip and getting his device back before the troubleshooting begins.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You told them to flash their stock firmware, In the OP, they posted they already tried that, all you suggested was that they try what they already tried which would only result in the same failure they got the first time, you didn't say a thing about how to get it to flash correctly this time.
I, on the other hand, actually read their post and understood that they already tried flashing the stock firmware, so instead of telling them to "flash their stock firmware", I took note of the fact that using Odin failed. Hence, the reason why I gave them the troubleshooting steps to understand WHY Odin failed and HOW to get it CORRECT this time.
Sent from my SM-S903VL using Tapatalk

Noted I am fully aware of things that can go wrong other than the firmware. And I have no time for a pissing match with you . That has not helped this young man fix his tablet at all. So please take your ego and your 8000+ post and **** off? Cheer's
Sent from my Nexus 6 using Tapatalk