Develop Bugs

[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] Odin Failed when Trying to India 4.3 To Hong Kong 4.3

i updated from 4.1.2 Turkey rom to New Indian rom. And it has wi fi issiue and Not have multilanguage (Turkish is not) in Turkish forums i read there is Turkish support in Hong Kong rom and the most stabil rom is that. I downloaded it, i put on Odin and click start, it says :
<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)
<ID:0/003> Removed!!
Why? Is there anyway?

Try second time or with the different version of Odin - e.g. for me Odin 3.04 works pretty much always (I had this problem with it just once) but I was never able to flash anything with Odin 3.09 - it always fails for me. Ensure that Kies is not running before starting Odin and connecting phone. Try with different USB cable and different USB port.

yeah some user also said that odin 3.09 always show error..

[Q] Soft bricked? Need to restore back to stock

Hey yall,
Neighbor's kid handed me his Sprint galaxy s3 today and asked if I could fix it. It's not working at all right now. I'd like to think I know a thing or two about technology but I know jack about Android...I use the other brand of phones. Anyway, lots of searches led me here to ask for help.
Far as I can tell it's a Spring LPH-710 Samsung Galaxy S3. When I turn it on it has the firmware upgrade encountered an issue screen and it doesn't do anything else. I can't get VOLUP+HOME+POWER to work (recovery mode I think) but download mode works with VOLDOWN+HOME+POWER.
I went and downloaded the Kies program from samsung but it fails to load the software. here's the error message; CAN'T POST LINKS! arrrgggg. It says "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now?" It then says I should enter some recovery code from another PC which I don't have.
It also has some small red text on the phone screen after I saw the Kies error message. It says SW REV CHECK FAIL : Fused 2 > Binary 1. That makes no sense to me but it's red and Kies error out so I'm going to assume that's not good.
I don't have a recovery key to use and the kid tells me he never backed it up to a computer before. I've read Odin is the preferred method to use for stock recovery but I don't know what files to download and use. Apparently, people are pretty unhappy with Kies...kinda like iTunes I guess. Why can't the Kies software wipe and reload the phone? Am I doing something wrong?

The device malfunctioned or had an error when he tried doing an update / flash. And if Kies is malfunctioning you can try PC Odin.
Download Sammy drivers of device, download the stock .tar image of the sprint s3 ( L710VPUDND8 ), download Odin v3.07
- At PC. Open Odin in admin mode. Click PDA and select the .tar image file and let that load and leave everything else alone in the program.
- On device press vol dn + home + power to get into download mode, press vol up to continue.
- Plug in device and let driver installation be completed. If a box in Odin ( on PC ) doesn't show a COM:##, replug device or try different ports and cables.
- Once you have that all set up click start and leave it to flash. It takes roughly 15 minutes to flash the whole thing or lesser.
If all else fails tell him to bring it in for servicing.
Posted via XDA Mobile

Thanks for the reply Sparks. I downloaded Odin 3.07, uninstall Kies and rebooted the PC. When I loaded the .md5 file, I then plugged in the phone and saw it look for drivers. The phone shows up on COM3. Below is what I see after I press start. Doesn't look good to me! Did I get the right file?
I've read that attepting to alter the operating system will void the warranty. Would this line on the download screen indicate he tried to do that? Current Binary: Custom. He said the contract is up in March so I'd hate for him to get screwed over by this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUDND8_L710SPRDND8_L710VPUDND8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

That's the right file. Says md5 is valid.
Binary custom and/or warranty bit 1 means he already tried to flash something and it ticked the counters so he's out of luck getting it repaired.
Go download the Galaxy S3 Samsung drivers through the official site and install them, reboot pc and try the method again in a different USB PORT ( Preferebly 2.0 slots ) some ports and different cables can be iffy at times.
Posted via XDA Mobile Free

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!

SM-T800 Soft-bricked, Odin stuck initialization. Stuck Samsung logo bootloop.

What I have is a SM-T800 Wifi Samsung Galaxy Tab S 10.5. Below what odin mode states:
Product Name: SM-T800
Current Binary: Samsung Official
System status: Official
Secure Download: Enabled
KNOX WARRANTY VOID: 0 (0x0000)
RP SWREV: A1
On to the problem: Device stuck at "Samsung Galaxy Tab S" (bootloop). It also will not boot into recovery. It will, however, boot into download mode. Therefore, I booted it into download mode, hooked it up to Odin 3.09, downloaded the latest stock firmware from sammobile, and attempted to flash via Odin. Latest Samsung drivers (1.5.55.0) are installed, and Odin definitely recognizes the device. However Odin always stuck at initialization. I have research and it sounded like the "Half SDS" symptoms in that thread (You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.).
I have been researching this problem for a while now (2 days and one very late night) and I have read all sorts of threads ( http://forum.xda-developers.com/galaxy-tab-s/help/to-event-soft-brick-disaster-t2838473/post54618555#post54618555 , http://forum.xda-developers.com/galaxy-tab-s/help/how-to-unbrick-tablet-model-t800-t2863246 , http://forum.xda-developers.com/galaxy-tab-s/help/mannage-to-soft-brick-t3025447 , http://theunlockr.com/2014/08/09/how-to-unroot-the-samsung-galaxy-tab-s-10-5-wifi/ , http://forum.xda-developers.com/galaxy-tab-s/help/wiped-accident-t2832346 , http://forum.xda-developers.com/galaxy-tab-s/help/stuck-sudden-bootloop-t3067280/) from forums in every corner of the Internet, but I'm still completely stuck. Any help is greatly appreciated.
What I have done so far and the results:
1. Kies 3 = Input Model & SN then selected firmware update and initialisation. Download then when come to software update and initialization, the progress stuck at 0% for forever.
2. Smart switch = same result as Kies 3.
3. ADB_fastboot = It would not list samsung device.
4. TWRP (twrp-2.8.7.0-chagallwifi.img.tar) = odin stuck initialization
5. Odin 1.85, 3.04, 3.07, 3.09, 3.10.6 (T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar) -> stuck initialization. I also downloaded PIT from ( http://forum.xda-developers.com/galaxy-tab-s/help/t800-pit-file-t2818817) and try repartition but still got same result. Also Kies is not running the background during my Odin attempts.
For the record, I don't know any details about the exact version of Android the tablet ran before it failed (I bought this tablet online used). I also used OEM cable then swapped with 4 other cables and switch between window 8.1 and 7 pc. Switched USB ports (Used USB 3.0 and 2.0 ports).
Does stock SM-T800 Tablet has locked bootloader? Do I have to try bootchain? I'm at the end of my wits. Short of an actual eMMC failure, I can't see any reason why this tablet would be permanently hard bricked or why ODIN refuses to cooperate. Can anyone suggest anything?
Finally I have submitted a repair ticket with Samsung but my device is 1yr 4 months old so no warranty. However I check the warranty for my tablet (via http://imeidata.net/warranty/samsung) and it say its has Factory Warranty Coverage until October 31, 2016. What does that mean and would that cover anything with regard to my problem?
P.S. Sorry for long post.

Never has KIES on my PC, only the samsuns and usb driver installed. (only my way) Also for my HTC devices i ever only install the drivers, because of there are complications with ADB, flashing, etc. if you have the HTC Device Manager on your PC. Perhaps for samsung is the same. But I don't know.
I have also used Odin3_v3.10.6. for flashing recovery, but I and many other user here use TWRP 2.8.7.2 from @ashyx .
For command line search for Heimdall. A tool made for Linux user but works also on Win.

First things first. You need to post a screen shot of odin when it fails so we can assess the situation.

@ashyx, thanks for you help.

ashyx said:
First things first. You need to post a screen shot of odin when it fails so we can assess the situation.
Click to expand...
Click to collapse
Thank you for responding.
Newbie to this forum. I don't see attachment icon on desktop version . When I select insert image, it ask for URL and I can't add outside link? I have try it on old tablet and firefox and chrome. Is it because I need to have 10 posts before I can add picture?
I'll research more how to add picture.
Anyways here the Odin log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T800XXU1BOJ1_T800XAR1BOJ1_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>
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

OK, which version of odin are you using and which slot have you placed the firmware file in?

ashyx said:
OK, which version of odin are you using and which slot have you placed the firmware file in?
Click to expand...
Click to collapse
I have used alot of odin version (v1.85, 3.04, 3.07, 3.09, latest 3.10.6). I put the md5 file in the AP/PDA slot. I downloaded the T800XXU1BOJ1_T800XAR1BOJ1_HOME.tar.md5 from sammobile.com with XAR (which I confirmed with Kies 3).

I have the exact same problem with T700 and I'm running out of ideas!
Any luck??

Sorry mate, in my instance there was nothing left that could be done on my end. I finally send it to samsung repair service last week and they repaired for me (under warranty luckily). Apperantly it was hardware failure, they replaced the whole PBA. I suggest talking with samsung tech at best buy or something to see if you can do the same. If you don't have warranty you might need to pay for the repair. Again sorry to be bearer of bad news cause I was in same boat as well. Good luck.

Ditto the symptoms on an 18 month old SMT800.

Same thing for me on my SM-T805.
Odin 3.10.7 says the following:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
there it's stuck forever.
I've tried twrp_3.0.2-1_sm_t805.tar as well as CF-Auto-Root-chagalllte-chagallltexx-smt805.tar.md5 (Odin -> AP).
I've tried different USB cables and PCs on top of that.
Latest Samsung drivers are installed (1.5.51.0).
Somewhere I read that it helps to unplug the battery beforehand. Did anyone try that yet?
I'm kind of hesitant to disassemble my tablet, but may try it soon as last resort. My warranty is already void/expired anyway.
Cheers
Michael

Phear666 said:
Same thing for me on my SM-T805.
Odin 3.10.7 says the following:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
there it's stuck forever.
I've tried twrp_3.0.2-1_sm_t805.tar as well as CF-Auto-Root-chagalllte-chagallltexx-smt805.tar.md5 (Odin -> AP).
I've tried different USB cables and PCs on top of that.
Latest Samsung drivers are installed (1.5.51.0).
Somewhere I read that it helps to unplug the battery beforehand. Did anyone try that yet?
I'm kind of hesitant to disassemble my tablet, but may try it soon as last resort. My warranty is already void/expired anyway.
Cheers
Michael
Click to expand...
Click to collapse
Put it in download mode.

ashyx said:
Put it in download mode.
Click to expand...
Click to collapse
the device was in download mode (Vol Down+Home+Power, on warning screen Vol Up)... That's why I even tried to rule out connection issues by trying different USB cables, USB ports and different PCs.