[Galaxy Tab 3 Q&A, Help & Troubleshooting] kal swift:
SOLVED

got my tab(SM-T210R) back up and running,,

been at it a few hours a day all this week,

kies firmware upgrade and initializaton somewhat didnt work. it installed it but always booted a black screen and backlight no sound. no vibiration,

so i am back to help the OP' and all others with this specific issue of dirty flashing directly to 4.4.2 from a rooted custom recovery tab3 that now have a messed up black screen problem but can still sneek into download mode thats looking all messed up> with the fallowing message

ODIN MODE

PRODUCT NAME: SMT210R

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

HW REV: 0x5

and then get PIT file errors and setup connection hangs.

please be shure you dont still have your custom recovery. you just have to hold home and vol+ ten seconds longer then usual after releasing the power button when the backlight appears. i thot i didnt have mine. until after i did this. now im just not shur if i held the buttons long enough then.

(if you need to get your current binary to offical please use odin's firmware and initialization process.. it will go thru and your binary will be changed to official but you will still have the black screen boot even though kies installed everything. proceed to next)

to get your brick back to being a useful loaf

this is what you need.

factory usb cable

odin 3.07

LT02.pit file from a 4.4.2 firmware (not 100%on that) ask me for the one i extracted if all eles fails

and T210.TWRP.2.8.0.0.tar.md5

start with opening odin

set your pit file and load the twrp recovery_

you want repartition checked for this (loading pit file should automatically fill the check box)

also autoreboot and f.reset time , checkboxes are checked

get your bricked device into download mode and connect

confirm odin sees the device and flash

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> T210.TWRP.2.8.0.0.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> recovery.img

<ID:0/005> NAND Write Start!!

<ID:0/005> RQT_CLOSE !!

<ID:0/005> RES OK !!

<ID:0/005> Removed!!

<ID:0/005> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)

at this point within 15 seconds after the reboot i got a splash screen and it booted up into 4.4.2 checked the status, device status of custom.

restarts and power offs are safe at this point. just take 5 seconds longer than normal.

so now we have an operating tablet with recovery and a messed up but working download mode.

checked download mode screen STILL CORRUPTED with the same weird message

ODIN MODE

PRODUCT NAME: SMT210R

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

HW REV: 0x5

i checked for twrp to operate it did. just took longer to boot it

PLEASE DO NOT AT THIS POINT wipe everything. it only got me back to the black screen with no booting.

and not being able to odin the .md5 package stock firmwares

it put me back an hour to get back to where these instructions end.

if this happends to you run keis firmware and intialize, to get the stock package back in and return to the corrupted download mode to see binary samsung offical.. then continue my odin instructions.

FALLOW UP:

had some time to experiment. i got back to %100 official system/binary and normal download mode with the green android guy being back.

i had updated to the latest TWRP and rooted.

i then unrooted with the super su app

then with the new kies program called SMARTSWITCH i again did the firmware and initialize and it went through and booted. without a hitch.

try it then go ahead and check for stock recovery and android man in download mode

-your welcome

b.t.w it seems in all the mess im still HW-rev 0x5 and it never installed the knox warraty bit..., blessing in disguise?

if this works for people somebody wanna make a sticky and add it to a 4.4.2 unbricking guide?

be aware that this is what worked for me. if you feel a different recovery or pit file may work go ahead. this is my results and wont be held accountable for what happens to you.

> DISCLAIMER> TRY AT YOUR OWN RISK< I AM NOT RESPONSIBLE