Bricked? - Galaxy Tab 3 Q&A, Help & Troubleshooting

I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?

same issue.
Erik1805 said:
I have a problem with my Tab3. When i am in download mode all i get is this. See picture.
I had a problem that the tab always reboots into recovery. So i want to flash a stock firmware. Any ideas?
Click to expand...
Click to collapse
i have come to a similar dead end.
came from fastdreamV6 rom and odin'd in T210RUEU0COB1_T210RXAC0COB1_HOME .tar .md5
pardon my terminology but i guess you'd say i dirty Odin'd it?> did not wipe or revert.
its where things went wroung for me
soo any ways.. looking for helpful and knowledageble people to begin trouble shooting this issue
after the install it rebooted and showed the tab3 splash screen then android package installer full screen before an OS. when the page installer screen disappeared that was the end of any responsiveness from the device.
mine always boots to black screen. no recovery , no audible/visual anything until odin mode.
always a black screen until i walk through the odin/download mode key' sequence blind
i have only half of what should look like a odin/download mode screen, the android guy has disappeared.
WIN7 does find the tab3 thats in [email protected]$$ odin mode in the device manager
odin also sees the tab3 but odin doesnt want to work to upload anything < hangs at setupconnection.. or pit mapping failed even when i have the new pit file being pushed,
ID:0/005> Added!!
<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>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
hemidall gives me communication conflicts
adb .. i currently have no os on the tablet as far as i can tell. maybe somebody can tell me if i can fastboot a command to push a recovery into it. but without adb-communication. i dont see it happening?
i presume i have a corrupted .pit file thats its not allowing me to replace.
OR KITKAT needs its own .pit file and i will need help aquiring one.
or its just a really bad flash alltogether. being boot.img. system img. recover img
how should i proceed if there is a way ? looking to get back to stock 4.4.2.
i can solder and make a usb jig if nessasary.
1 week later; further developments and workaround to boot here:
http://forum.xda-developers.com/gal...ably-hard-bricked-t3057440/page2#post60682636

Related

[Q] Recovery partition corrupt?

Hi!
After flashing many custom kernels and swapping them a lot of times with Mobile Odin, I have noticed two days ago that my Recovery (CWM) is fried. Whenever I try entering it I just end with a bootloop, that carries on for a few times, even if I try booting normally. Then everything works fine.
I didn't care too much until today, I am willing to try some custom roms and I am not able to flash them, and I am not able to Nandroid...
So I said "Let's flash the recovery again!" Hell no... Odin 3.04 just stays on Write Nand Start forever, it's been 20 minutes this time (tried 10 times with diferrent files, usb ports, cables, computers EVERYTHING). I am putting the file in PDA section.
I suppose the recovery partition got corrupted somehow? These are the kernels I swapped: Perseus, Note2Core, NEAK, Different versions of stock and others I don't even remember.
Now I don't even see my build number in Settings->About. It just shows "$" WTF?!
What should I do? I would really like to try some of those beautiful custom roms! I am sick tired of Touchwizz and its lags...
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> tmp/recovery.img
<ID:0/017> NAND Write Start!!
Flash pit file first then recovery.
4l3xXx said:
Hi!
After flashing many custom kernels and swapping them a lot of times with Mobile Odin, I have noticed two days ago that my Recovery (CWM) is fried. Whenever I try entering it I just end with a bootloop, that carries on for a few times, even if I try booting normally. Then everything works fine.
I didn't care too much until today, I am willing to try some custom roms and I am not able to flash them, and I am not able to Nandroid...
So I said "Let's flash the recovery again!" Hell no... Odin 3.04 just stays on Write Nand Start forever, it's been 20 minutes this time (tried 10 times with diferrent files, usb ports, cables, computers EVERYTHING). I am putting the file in PDA section.
I suppose the recovery partition got corrupted somehow? These are the kernels I swapped: Perseus, Note2Core, NEAK, Different versions of stock and others I don't even remember.
Now I don't even see my build number in Settings->About. It just shows "$" WTF?!
What should I do? I would really like to try some of those beautiful custom roms! I am sick tired of Touchwizz and its lags...
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> tmp/recovery.img
<ID:0/017> NAND Write Start!!
Click to expand...
Click to collapse
A good start would be to start reading threads about root, flashing, Odin, recovery, custom roms and kernels. If you don`t know what you`re doing you`are about to crash and burn your device
dr.ketan said:
Flash pit file first then recovery.
Click to expand...
Click to collapse
Pit file failed as well, at getting pit for mapping, but in the end I solved by flashing TWRP through Note 2 toolkit. I don't know what the problem was, I'm happy I solved it though. Possibly there was something going on with kies/drivers/odin 3.04 (toolkit uses 3.07) or God knows what else.

[Q] Bricked phone, need lots of help :(

NT-7100 model.
So, I was trying out different ROMs on my phone last night and the one I ended up on before I went to sleep kept freezing a lot, so I ended up booting into recovery and I wiped everything a few times and then reflashed it. The one time I did this, it failed (I can't remember what it said) and I couldn't flash the file. I tried re-wiping everything, but nothing. I was pretty tired and must've hit reboot by mistake, because the next thing I know, I'm stuck on the Samsung boot screen.
Now, I can only go into downloading mode, but it currently says:
Product Name; (blank)
Custom Binary: No
Current Binary: Samsung Official
System Status: Custom
I can get it recognized on Odin (3.04), but whenever I try to flash stock ROM, it says one of two things: 1) (most common) Can't open serial (COM), and 2) (JUST happened as I was trying again to reflash) There is no PIT partition.
The second one is new, I assume I have to get a PIT file from somewhere to fix that?
The first one, if it comes back, how should I deal with that?
(Is it really bad that it doesn't have anything after Product Name? )
Thanks in advance. I'd really like to get this fixed up ASAP T_T
Hikiri said:
NT-7100 model.
So, I was trying out different ROMs on my phone last night and the one I ended up on before I went to sleep kept freezing a lot, so I ended up booting into recovery and I wiped everything a few times and then reflashed it. The one time I did this, it failed (I can't remember what it said) and I couldn't flash the file. I tried re-wiping everything, but nothing. I was pretty tired and must've hit reboot by mistake, because the next thing I know, I'm stuck on the Samsung boot screen.
Now, I can only go into downloading mode, but it currently says:
Product Name; (blank)
Custom Binary: No
Current Binary: Samsung Official
System Status: Custom
I can get it recognized on Odin (3.04), but whenever I try to flash stock ROM, it says one of two things: 1) (most common) Can't open serial (COM), and 2) (JUST happened as I was trying again to reflash) There is no PIT partition.
The second one is new, I assume I have to get a PIT file from somewhere to fix that?
The first one, if it comes back, how should I deal with that?
(Is it really bad that it doesn't have anything after Product Name? )
Thanks in advance. I'd really like to get this fixed up ASAP T_T
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1896696 try here post 4 has the pit file flash that then boot into download mode again and flash the stock rom
I actually found that a little bit before your response and I've been trying to flash it, but it either says it can't connect to serial (COM) or just fails and doesn't say why...ONE TIME it went to the "PIT for mapping" part and then just stalled for hours.
The serial one I assumed was drivers or just the USB port I was using, so I reinstalled the drivers and I've tried different ports, still no change.
The drivers didn't find any updates, but I assume there aren't really any?
Not really sure where to go from here... Is there something else that could be causing the serial thing?
EDIT: This is what it does when I restart download mode and immediately plug it into Odin and try to flash the PIT. It only does it the first time and then it sticks on SetupConnection.
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Hikiri said:
I actually found that a little bit before your response and I've been trying to flash it, but it either says it can't connect to serial (COM) or just fails and doesn't say why...ONE TIME it went to the "PIT for mapping" part and then just stalled for hours.
The serial one I assumed was drivers or just the USB port I was using, so I reinstalled the drivers and I've tried different ports, still no change.
The drivers didn't find any updates, but I assume there aren't really any?
Not really sure where to go from here... Is there something else that could be causing the serial thing?
EDIT: This is what it does when I restart download mode and immediately plug it into Odin and try to flash the PIT. It only does it the first time and then it sticks on SetupConnection.
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
well delete all old Samsung drivers and kies if any any remove all temp file left over restart you pc
install SAMSUNG_USB_Driver 1.5.23.0 stop the update from the right tray and it will install the drivers fine
now use odin 3.04 and right click as administrator (disable antivirus or any other conflicting drivers if you have any)
if this dont work and then try installing drivers through http://forum.xda-developers.com/showthread.php?t=1923956 here and see if it works but i blv the first one will get you ahead
if nothing works then try http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 rescue firmware from here the verison N7100XXDLJ2_OXA_FACTORY as it contain pit file too and go through the flashing process and selecting individual file for flash
shhbz said:
well delete all old Samsung drivers and kies if any any remove all temp file left over restart you pc
install SAMSUNG_USB_Driver 1.5.23.0 stop the update from the right tray and it will install the drivers fine
now use odin 3.04 and right click as administrator (disable antivirus or any other conflicting drivers if you have any)
if this dont work and then try installing drivers through http://forum.xda-developers.com/showthread.php?t=1923956 here and see if it works but i blv the first one will get you ahead
if nothing works then try http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 rescue firmware from here the verison N7100XXDLJ2_OXA_FACTORY as it contain pit file too and go through the flashing process and selecting individual file for flash
Click to expand...
Click to collapse
Well, I tried all of those and it didn't work. Still getting the same error as before, unless I reboot into downloading mode and immediately plug in the phone to the PC, in which case I get:
"<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
"
Every try after that says the serial error.
I assume that the main issue is the drivers not working right? It says it's been successfully installed and all of that, but then it's not connecting or something? You said to get rid of "temp files", how's the best way to go about that? That could be one of the issues, because I wasn't sure what you meant by that.
If the drivers don't end up working, is the only way to continue trying to fix it to go from a different computer?
Hikiri said:
Well, I tried all of those and it didn't work. Still getting the same error as before, unless I reboot into downloading mode and immediately plug in the phone to the PC, in which case I get:
"<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
"
Every try after that says the serial error.
I assume that the main issue is the drivers not working right? It says it's been successfully installed and all of that, but then it's not connecting or something? You said to get rid of "temp files", how's the best way to go about that? That could be one of the issues, because I wasn't sure what you meant by that.
If the drivers don't end up working, is the only way to continue trying to fix it to go from a different computer?
Click to expand...
Click to collapse
i bricked one last week and dr ketan helped me out, i think your drivers are fine. i had to plug in before opening odin, wipe data, wipe partition from recovery, flash pit, if it dont work try another, till pass, then flash with firmware together. double check with ketan. oh an make sure u use rear usb port. pit is in post 4 of his tut.
Hikiri said:
Well, I tried all of those and it didn't work. Still getting the same error as before, unless I reboot into downloading mode and immediately plug in the phone to the PC, in which case I get:
"<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
"
Every try after that says the serial error.
I assume that the main issue is the drivers not working right? It says it's been successfully installed and all of that, but then it's not connecting or something? You said to get rid of "temp files", how's the best way to go about that? That could be one of the issues, because I wasn't sure what you meant by that.
If the drivers don't end up working, is the only way to continue trying to fix it to go from a different computer?
Click to expand...
Click to collapse
use your uninstaller software to unistall your drivers as it delete all traces of file . then ccleaner to clean registry and click clean.
go to start menu-run -type %temp% press enter delete all . reboot and install drivers and use the driver version in mentioned and skip upgrade
at this point your driver install will be clean so it should pass the flash remember antivirus as it can block the operation too.
try the rescue firmware
Okay so here's what I did:
Uninstalled drivers and the program (add/remove programs in control panel and in device manager), deleted temp files, restarted computer, reinstalled drivers, not connected to internet so it didn't try to update, opened odin (3.07, from the toolkit) and plugged in the phone into the usb and then turned phone on into download mode, it said it was searching for drivers etc, recognized the phone, showed up in odin, put the pit+4 files from toolkit, and hit to flash.
Now, it's saying (set partition) above the COM 3, and it's hanging on "get pit for mapping.."
It shouldn't be taking a really long time, right? Cause I've heard it's nearly instant...
I'm not sure what the problem is cause it does this the first time, then goes back to the serial issue.
EDIT: This time, I redid everything again and tried Odin 3.04 and it said this:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
So, it skipped the "getting the PIT file" part, but it failed again. Should I try to do it without the PIT file or something? Like, it's always said that there was no PIT when I did that.
Okay, so I just tried to do everything on a different computer and still not working. Every time it comes up with "Get PIT for mapping" even though I add the PIT for flashing...
Does this mean that my phone is a lost cause? Or is there something else I can try?

[Q] Sph-L710 Hard brick.

Hiiyaa..
Mkk, ive tried all solutions, nothing works..
I was randomly using my S3 on stock software, it shut off and now it will not turn on.. Absolute hard bricked, not even a jig will kick this on..
So i made a recovery sd card, finally it kicked it into dl mode..
PROBLEM:
It tries to write 15988 sectors, then pops up FLASH WRITE FAILURE
ODIN MODE.
SYSTEM STATUS: NONE.
Okay, Ive tried flashing stock rom through odin, it will get close and then pops up the error No PIT partition found..
I tried to flash a pit file, it fails.
Im using a rear usb port, different cables. Nothing works..
I tried to do a nand wipe through odin, it gets to userdata partition and then fails when it tries to repartition..
Im at a loss here, any help will be amazing...
EDIT:
Heres the error that odin is giving me
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010>
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Some questions you can answer to give more of a frame:
1. What software build are/were you on?
2. If the software had KNOX, had you done anything to attempt to remove/disable it?
3. The firmware was stock, were you also on stock recovery?
Sent from my iPod touch using Tapatalk
thenexusgeneration said:
Some questions you can answer to give more of a frame:
1. What software build are/were you on?
2. If the software had KNOX, had you done anything to attempt to remove/disable it?
3. The firmware was stock, were you also on stock recovery?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
I was on JB 4.1.2, it didnt have knox, and i was on stock recovery,
Johnnysauur said:
Hiiyaa..
Mkk, ive tried all solutions, nothing works..
I was randomly using my S3 on stock software, it shut off and now it will not turn on.. Absolute hard bricked, not even a jig will kick this on..
So i made a recovery sd card, finally it kicked it into dl mode..
PROBLEM:
It tries to write 15988 sectors, then pops up FLASH WRITE FAILURE
ODIN MODE.
SYSTEM STATUS: NONE.
Okay, Ive tried flashing stock rom through odin, it will get close and then pops up the error No PIT partition found..
I tried to flash a pit file, it fails.
Im using a rear usb port, different cables. Nothing works..
I tried to do a nand wipe through odin, it gets to userdata partition and then fails when it tries to repartition..
Im at a loss here, any help will be amazing...
EDIT:
Heres the error that odin is giving me
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010>
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What did you do to make this recovery sd card? i got the same problem and the jig did nothing!!!!

Samsng Tab 3 7.0 probably hard bricked

My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
untamed1 said:
My Samsung SM-T210R is in trouble . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless).
The report on screen upper left says:
ODIN MODE
PRODUCT NAME: SMT210R
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
HW REV: 0x5
From there attempting to flash a number of roms including stock fails. The MD5 checks are always successful. The failure modes are 2 different ones.
The first involves a PIT Partition missing. It happens when attempting to flash non stock roms
The second, flashing a stock rom (the latest: T210RUEU0COB1 and also: T210RUEAMK1 ) or also TWRP Recovery shows:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.. (It hangs at this point for a very long time)
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did a lot of searching for a pit file for my tablet model without coming up with it.
Can someone help me to solve this please?
Click to expand...
Click to collapse
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
bierma32 said:
Are you tried the search Funktion?
http://forum.xda-developers.com/showthread.php?t=2625163
Here are what you want.
Click to expand...
Click to collapse
Thank you for your response.
First if with search function you mean by using google, I have done a lot of of that, but so far with no luck.
I am pretty good with this stuff but not good enough. I would like to find someone who has either a lot of knowledge or has resolved a situation like mine and is willing to help.
The link you suggested is probably good, but does not totally relate to my situation. They had a working device they were simply trying to root. I instead don't have a working device and not even access to recovery mode. I don't even know right now what files and folders are on my device.
Thank you for the pit file though; now I have to find out whether repartitioning with it would be good, or whether it would push me down deeper in the hole.
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
bierma32 said:
You can also use the search Funktion here at this forum.
All wath you must do is simular to flash a recovery with Odin.
Download the Stockton from sammobile.com
Boot your tab into download mode
Startup odin
Check autoreboot , repartion and factory reset.
Under Pit you select the Pit.file
Under PDA you select your downloaded Stockrom what you have unziped,so that have a *.tar.md5 extension.
Press Start and Walt some minutes and the Tab will reboot.
Click to expand...
Click to collapse
Bierma32,
first of all thank you for spending the time to assist me it is very much appreciated. I followed your procedure and unfortunately it went nowhere fast. This is the report from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T210RUEU0COB1_T210RXAR0COB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
This is what happened earlier with the only difference being the "Set PIT file" command.
Any idea?
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Rom's for Samsung Tab 3 7.0 SM-T210R
Doom1337 said:
Hi. Im not able to help you, but im having issues aswell. I tried flashing some different things trying to root my device.. it seems it worked, but it never rooted it or anything even though my system status is Custom and the build number ****ing changed. Could you please tell me where you found your stocks for your device? To unroot.. i'd really appreciate it. I can't find any.
Click to expand...
Click to collapse
For non stock ROM's:
http://forum.xda-developers.com/galaxy-tab-3/development-7
For Stock ROM's:
http://www.sammobile.com/firmwares/
For stock there are faster download sources also, do some google searching. By the way my issue has nothing to do with rooting.
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
I had found another PIT file as well, that looked very promising but did not work. I will try these two. Thanks.
:fingers-crossed:
Continuation
bierma32 said:
It looks like that Pit.file isnt working. Take a look in this link for a other Pit.file
http://forum.xda-developers.com/showthread.php?t=2722948
Click to expand...
Click to collapse
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
untamed1 said:
Tried both PIT files at that link with no success. Thanks for you help anyway. I am starting to loose hope and to wonder whether the problem is really not with the PIT file and partition tables. I just wish I knew linux.
Click to expand...
Click to collapse
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
No battery picture
vinay said:
When you connect charger do tab shows battery charging.
If it shows then probably your kernel is working.
(i don't know about Samsung too much as they have download mode instead of fastboot.)
Sent from my D2212 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
untamed1 said:
No, I am at a lower level than the kernel, I am sure. The only thing ever showing is the wording at the download mode screen.
Another curious thing that seems to be happening is that the battery seems to discharging or not charging since I can only enter download mode only while or after connecting the charger.
Any way thanks for your response.
Click to expand...
Click to collapse
you just hard bricked your device.
but download mode is working so still a hope.(untill power end)
which version of odin are you using.?
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
untamed1 said:
I am using 3.06. Battery is not really a problem, other than for the unknown reason why it discharges or does not charge completely. I am questioning whether all the trial and errors I have done, since the issue occurred, may have caused some collateral damage. In any case, I can still start download mode after a short time charging
Click to expand...
Click to collapse
When this happen.
What was you doing.
Like
Your tab was running you turned off and it won't turn on. Or you flashed a rom/kernel and it won't turn on.
Sent from my D2212 using XDA Free mobile app
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
untamed1 said:
Vinay, as I said in my first post...
. . . . . . . It all started after flashing a rom, I believe it was TranchidaKat v 4.3, However after that I have tried so many things that the start means little now.
Situation:
The tablet does not boot either to regular boot or into recovery. It actually appears pretty dead when trying, unless one pays attention to the back lighting of the screen.
Eventually I managed to consistently boot into download (actually ODIN) mode although without the large texting with the warnings and the instruction to press the up volume button (which I do nonetheless). . . . . . . . .
I hope you have some specific ideas or suggestions on what I can try. Without that I have pretty much given up.
Click to expand...
Click to collapse
First of all update your odin to 3.09 or higher if there is. And try flashing again.
(btw is that rom was made for your variant)
Sent from my Xperia E3 using XDA Free mobile app
same issue
i also have an unresponsive sm-t210r that has the OP's issues of a broken looking download screen, no boot and no recovery
pit file problems in odin and timeouts and now not postitive if my device made it to the 4.4.2 locked bootloader. looking to get it back to stock.
will help with files, time etc.
-ty
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
kal swift said:
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
Click to expand...
Click to collapse
I still cant get it working, i keep getting stuck with it saying it doesnt have a pit file even when i try to load it

Note 2 seems bricked after trying to go back to stock firmware. Help needed!

Hi all,
I was using my Galaxy Note 2 with the latest Resurrection Remix ROM, but wanted to revert back to the stock firmware .
I downloaded the latest stock firmware and tried to flash it directly with ODIN.
Unfortunately, the process stopped at about 3/4 of the progress bar. I tried several time, changing USB ports and slots; even computer. After one try, the messages changed and the process stopped event before trying to write with the message : "There is no PIT partition".
The download mode shows the usual warning and download screen. But if I try to go in recovery mode or just boot normally, I get the "Firmware upgrade encountered an issue...".
What I've tried so far:
. Flashing several stock firmwares via several version of ODIN.
. Kies upgrades (tried about everything there).
I also tried a PIT file, but got the message: "Re-Partition operation failed".
I really don't know what to try anymore
Any help would be greatly appreciated!!!
(edit -> oh, and I've also tried with firewall and antivirus out)
FixB said:
Hi all,
I was using my Galaxy Note 2 with the latest Resurrection Remix ROM, but wanted to revert back to the stock firmware .
I downloaded the latest stock firmware and tried to flash it directly with ODIN.
Unfortunately, the process stopped at about 3/4 of the progress bar. I tried several time, changing USB ports and slots; even computer. After one try, the messages changed and the process stopped event before trying to write with the message : "There is no PIT partition".
The download mode shows the usual warning and download screen. But if I try to go in recovery mode or just boot normally, I get the "Firmware upgrade encountered an issue...".
What I've tried so far:
. Flashing several stock firmwares via several version of ODIN.
. Kies upgrades (tried about everything there).
I also tried a PIT file, but got the message: "Re-Partition operation failed".
I really don't know what to try anymore
Any help would be greatly appreciated!!!
(edit -> oh, and I've also tried with firewall and antivirus out)
Click to expand...
Click to collapse
Hi,you did all wipe from custom recovery before reinstalling the stock firmware?
Unfortunately, no
I did not do anything before trying to flash the stock firmware :'
FixB said:
Unfortunately, no
I did not do anything before trying to flash the stock firmware :'
Click to expand...
Click to collapse
Try and see if it works!
Thanks: I would... but I can't access recovery mode. I can only go into Download mode (recovery go to the "Firmware upgrade encountered an issue..." screen )
FixB said:
Thanks: I would... but I can't access recovery mode. I can only go into Download mode (recovery go to the "Firmware upgrade encountered an issue..." screen )
Click to expand...
Click to collapse
Now, I've got this message when trying to flash:
"<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)"
FixB said:
Now, I've got this message when trying to flash:
"<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)"
Click to expand...
Click to collapse
What you're trying to flash firmware 4.4.2 i hope, because if you're trying to flash a 4.3 is impossible the downgrade to do so because of Knox!
I was trying 4.4.2.... Does it matter if I was on a 5.x ROM?
FixB said:
I was trying 4.4.2.... Does it matter if I was on a 5.x ROM?
Click to expand...
Click to collapse
Did you try a different USB cable or different Odin version?
Yes, I tried several USB cables and USB ports and PCs and about 10 different Oding version
I'm starting to think it's hopeless
I flashed CWP recovery from here : http://forum.xda-developers.com/showthread.php?t=2000138
And it worked (at least Odin finished saying it was flashed ok). But if I try to go into recovery, I now get a 'Downloading' screen. When going to download mode, I have the normal screen, with a number of custom binary download increased by 1.
Anyone could advise on next steps I should try?
Thanks!
I managed to get back TWRP v2.8.7.0.
What would be the next steps to try and revert to the stock firmware?? Thanks!!
I used TWRP to reset and wipe everything, then ODIN to flash stock firmware.... And everything is now fine I've got the phone working perfectly with stock firmware!
Thanks!

Categories

Resources