[Firmware] Unbrick & restore Galaxy Tab 3 7in SM-T210R

[gian20]

my SM-T210 is hard bricked it was I think fully drained. THen the device wont boot anymore, no downlloadmode, odin, recovery no LIFE. It only shows this if plugged in a Windows machine:

On a Linux PC:

$ dmesg
[ 8587.060023] usb 1-1: new full-speed USB device number 19 using uhci_hcd
[ 8587.227045] usb 1-1: New USB device found, idVendor=1286, idProduct=8164
[ 8587.227054] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 8587.227059] usb 1-1: Product: EMEI
[ 8587.227063] usb 1-1: Manufacturer: MARVELL
$lsusb
Bus 001 Device 019: ID 1286:8164 Marvell Semiconductor, Inc.

any idea on how to fix this. what is the resistor setup?

Anybody can help me here? can someone post a bootloader that can be burned to a microSD for this device? SM-T210
ref : https://forum.xda-developers.com/att-galaxy-s6/help/create-debrick-img-stock-rom-t3367325

so i have made my own USB jig (I tested it on my SM-T285 and it went to FACTORY DOWNLOAD MODE) but the SM-T210 is still dead (black screen) still being detected as Marvell EMEI device

 

[xdausernl]

Same problems here while trying to Flash SM-T210

Scrap that, I was able to get it into download mode! What threw me off was there are no pictures! From powered off state I press and hold Home+VolDown+Power, and if I watch really closely the backlight comes on but the screen is empty and black. If I press Vol Up from there I get the download mode with the white text at the top left corner saying "ODIN MODE" etc., but still no picture. Strange!

Anyway next issue: I connect it to Odin 3.09, COM port connects fine, I pick my firmware file linked in the first post, Auto Reboot and F.Reset Time ticked, Re-Partition NOT ticked -- and I get this:

<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0CNI1_T210RXAC0CNI1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> PBL.bin
<ID:0/004> NAND Write Start!! 
<ID:0/004> FAIL!
<ID:0/004> 
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Does it mean the NAND is broken? Will I have to throw it away?

I also tried older versions of Odin v1.87, that gave me the exact same problem as v3.09 with NAND write failure and v1.3 stock at PBL.bin
Yet my Tab3 7.0 8GB has WiFi only, so the chipset would differ from the ones with WiFi and 3G/LTE.
So I was wondering if there's a seperate stock ROM for those tablets with WiFi only, which in that case may explain the cause of trouble, right?
There's also this problem with PIT ... 'get PIT for mapping', is that in any way related to the failures during flashing?

 

[KPandamoneum]

I wanted to ask does this work for SM-217A