[Q] [HELP] GT-N8013 - Soft Bricked(ODIN MODE ONLY) - Galaxy Note 10.1 Q&A, Help & Troubleshooting

[Q] [HELP] GT-N8013 - Soft Bricked(ODIN MODE ONLY) - Galaxy Note 10.1 Q&A, Help & Troubleshooting

GT-N8013
Blue/Gray
16GB Wifi Only Model
I was watching a youtube video, my tablet froze for an hour, died, then I let it charge and it rebooted into the samsung logo. After that it decided to go white screen and goes to a white screen every time it's booted. I've been trying to resolve this on my own with various resources for about a month now.
I can get to ODIN mode no problem, but I can't flash anything. I have recently bought a new OEM Samsung USB cable and tried multiple versions of ODIN on two different machines. Directly connected to the motherboard and not USB 3.0 ports.
I think the solution to my problem may be answered:
Here: http://forum.xda-developers.com/showthread.php?t=2268735
or
Here: http://forum.xda-developers.com/showthread.php?t=2713297
It is hard for me to comprehend the English used in the first link as I think Authors first language is not English. I think what he is saying is that if ODIN is not working then you have to flash the PIT file via adb and a SD card, but I cannot access Recovery, and I don't recall fully how to use ADB in Downloading Mode, if that's possible at all. He also states I may need to downgrade my bootloader version based on the last ROM that I had on my tablet. If someone could educate me on that I'd appreciate it.
The 2nd link says I need the stock firmware for my country(I live in the U.S. of A.) and to nand erase all but I feel like that should be used as a last resort. I did download both N8013UEALI3(4.0.4) & N8013UEUCMI3(4.1.2) from sammobile.com though.
When I try to flash just a Recovery/ROM, with Autoreboot checked, I get the PIT error message below:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, with Auto Reboot & Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT by its self, Re-partition checked, I get the error message:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
When I try to flash a PIT w/ Recovery/ROM, Re-partition Checked and Auto-Reboot checked, I get:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Any assitance would be greatly appreciated, I've been without my tablet for a month now. I have any backup, I don't recall the ROM I flashed because it was so long ago, but I'm pretty sure the version was Jellybean. I know my recoevry was one of the later CWM TouchScreen Rom recoverys but I can't recall the version. Thanks for any help, please let me know what information I'm lacking or what I can do, thank you all for your time.

Update
Any assistance would be greatly appreciated. I have tried to different PIT files for the PIT mapping and they both failed. Getting pretty desperate now. I can't even NAND Erase All, I gave that a shot and it failed:
When I select NAND Erase All, stock rom(4.0.4 or 4.1.2), Pit, & Re-Partition checked, Nand Erase all Checked, I get the following in ODIN 3.07 and 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8013UEALI3_N8013XARALI3_1081475_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Erase...
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think its the ECCM and maybe I need a JTAG repair. Like I said before, I can't get into recovery, I just get a all white screen. When the tablet first died I got the Samsung logo and then it rebooted and went White, I never got the Samsung logo again. Any help please? Even if it's just recommendations for trusted JTAG repair sites, because I don't trust the ones I've found ths far. Or know PIT files that have worked for flashing on the N8013. Anything at all.

BUMP
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.

onlysafonne said:
I found this article here: http://www.sammobile.com/forum/showthread.php?t=23562
Exact same problem I am having, I think I'm going to need a JTAG repair. I just posted a request to get some fresh PIT files from multiple android versions. I ill keep posting updates on how this is going, I feel alone in this issue since no one has said anything but I get multiple views...but I see more and more people are starting to post in the help section for this particular brand of tablet in the past 3-5months, it sounds terrible but I'm glad I'm not alone since I feel like im talking to myself here.
Just contacted Mobiletechvideos guys, I hope they are legit. I'm will to pay $50 for a jtag repair if i can have this tablet back.
Click to expand...
Click to collapse
@onlysafonne what file fails? I see your log above

carl1961 said:
@onlysafonne what file fails?
Click to expand...
Click to collapse
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!

onlysafonne said:
I've tried to use both ODIN & Heimdall. All files are failing for me. I tried stock 4.0.4 & 4.1.2 Roms, 3 different PIT files, I even tried to NAND erase all with a stock rom and ODIN continues to fail for me. I installed a virutal box on multiple machines running XP SP3 since windows 7/8 weren't working for me as well, that failed as well. When I try to flash the PIT files I get the output from ODIN in my OP, nothing is working for me. I'm just thinking I experienced instant death on this tablet for no reason at all. The most success i've had is with Heimdall just being able to reboot the tablet for me and then go back to Downloading mode, but nothing else is responding for me.
I'f I can get some fresh pit files from fully operational devices I will know that I've done everything I can excluding JTAG repair myself. If I can't get some fresh PIT files from multiple android versions, then I might just have to send it to the Mobiletechvideos guys to see if they can repair.
Thanks for the reply and interest in my issue!
Click to expand...
Click to collapse
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you

Heimdall
carl1961 said:
no I got the pit file from here http://forum.xda-developers.com/showthread.php?p=41158546#post41158546
tell me how to grab it and I will get it from my tablet now for you
Click to expand...
Click to collapse
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.

onlysafonne said:
To download a copy of your PIT all you have to do is install Heimdall, with zadig driver (Samsung/General Device) , boot your tablet into Download mode, and download a copy of your PIT by going to Heimdall Frontend, clicking utilites, and downloading and saving your PIT to your desktop(or where ever you want) and uploading it for me.
Heimdall can be found here: http://glassechidna.com.au/heimdall/
After you are down with Heimdall, make sure you uninstall the driver from "Device Manager" in your USB Devices, that way, you can use ODIN again. A;; of this should only take about 5-10mins, as all the files are really small. i really appreciate this.
Click to expand...
Click to collapse
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer

carl1961 said:
@onlysafonne
ok I did it also a compair to My-N8013.pit that you said did not work, they or identical so that may be bad news for you.
thread
http://forum.xda-developers.com/showthread.php?t=1916936
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Click to expand...
Click to collapse
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.

onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
if you not under warenty I would maybe buy a used one on ebay that might just have a cracked screen, you might even find a 32GB one
http://www.ebay.com/itm/Samsung-Galaxy-Note-10-1-32-GB-Wi-Fi-GT-N8013-/361155880699?pt=US_Tablets&hash=item54169166fb

onlysafonne said:
Thank you for this post, that helps me alot, it appears it is beyond recovery via ODIN at this point. Thank you for taking the time to compare your PIT to the previous one. I will wait for Mobiletech to contact me back and post an update from there.
Click to expand...
Click to collapse
onlysafonne, I have the same problem. I can use Odin and get to CWM but nothing I flash will get me past the Samsung Galaxy Note 10.1 image I cannot even get it to shut off. It will go black then power right back up.
I have flashed with Nand Erase All checked only
KIES_HOME_N8013UEUCMI3_N8013XARCMI3_813049_REV00_u ser_low_ship.tar
Any ideas? I have not heard of JTAG

I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks

Flying_Phil said:
I have a N8010 and I'm also in this kind of bootloop.
Nothing works.
I had OmniRom 4.4.4 installed and the newest TWRP.
I only can get into Download Mode.
When I try to get into Recovery the blue TWRP Screen pops up for a second and then it's going back to "Samsung Galaxy Note 10.1" Logo.
I even tried to disassemble the battery. But this didn't work either.
Any ideas what I can do? If not, I'll have to take it to repair. Got some warranty left, but I rather fix it myself.
Thanks
Click to expand...
Click to collapse
have you tryed to odin install your firmware? usally the bootloop is caused because you need to do a factory reset to get rid of (in your case OmniRom 4.4.4) your firmware as I see is http://www.sammobile.com/firmwares/confirm/31427/N8010XXUDNE4_N8010BTUDNF1_BTU.zip/

Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or cwm recovery. But there is still twrp.
I can't open your link :-/

Flying_Phil said:
Yes, I did try that. Is still in bootloop afterwards. I also tried to flash stock recovery or can recovery. But there is still twrp.
I can't open your link :-/
Click to expand...
Click to collapse
try this N8010 recovery with the included 3.07 odin put in PDA slot and do no check re-partiton look at picture
@Flying_Phil
yes samfirmware is picky go here and search your N8010 you most likly need to signup (it's free) and as you see most odin updates or "home" which means it does not do a factory reset which is ok if your updating a stock unrooted rom so you need to do a factory reset when coming from a custom rom.

well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!

Flying_Phil said:
well I tried to flash your attached file. Odin said "Pass!" but my Tablet still does the bootloop.
Like I said, I tried to flash several firmwares. All with this same result. First I tried the German version, then the Austrian and the Australian.
Now yours was the version for new zealand.
I have no clue, why this doesn't work.
Here is the log from Odin and I attached a screenshot.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_N8010XXUDNK1_N8010NZCDNK1_Recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Click to expand...
Click to collapse
ok so did you try and reboot to stock recovery and do a factory reset

carl1961 said:
ok so did you try and reboot to stock recovery and do a factory reset
Click to expand...
Click to collapse
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.

Flying_Phil said:
sorry, I forgot to tell about it.
Yes I tried to go into Recovery, but there ist still TWRP on it and it still crashes after a second.
I even tried the flash without checking "Auto reboot", so I could boot directly into recovery, but it worked neither.
Click to expand...
Click to collapse
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB

carl1961 said:
ok lets backtrack
what is your tablets stock info? and or you 16 GB or 32 GB
Click to expand...
Click to collapse
GT-N8010 16GB. Need more?

Related

P6810 Odin fail

Hello guys,
i have problem with my P6810 16gb Wifi tablet, the problem started when i flashed CWM touch and then my touch screen stoped working so i tried to flash firmware and i got odin fail, from then when i turn it on it says "Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again"..
Odin message:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6810OZSLP8_P6810ZSLP8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
How can i fix this problem?
Cheers!!

bajki_ktm said:
Hello guys,
i have problem with my P6810 16gb Wifi tablet, the problem started when i flashed CWM touch and then my touch screen stoped working so i tried to flash firmware and i got odin fail, from then when i turn it on it says "Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again"..
Odin message:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P6810OZSLP8_P6810ZSLP8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
How can i fix this problem?
Cheers!!
Click to expand...
Click to collapse
If you have kies installed in your computer, please try to disable or uninstalled it. As I know, Samsung KIES and ODIN could not get along with together....

cakrabayu said:
If you have kies installed in your computer, please try to disable or uninstalled it. As I know, Samsung KIES and ODIN could not get along with together....
Click to expand...
Click to collapse
I don't have installed KIES..

Sorry....Did you follow this guide while using odin? http://forum.xda-developers.com/showthread.php?t=1469635 just wondering why you encounterred a problem. Thx.
Sent from my GT-P6800

cakrabayu said:
Sorry....Did you follow this guide while using odin? http://forum.xda-developers.com/showthread.php?t=1469635 just wondering why you encounterred a problem. Thx.
Sent from my GT-P6800
Click to expand...
Click to collapse
I was doing everything like in tutorial, tablet was full charged and i got this error, that's the story..
What could possibly go wrong?

bajki_ktm said:
I was doing everything like in tutorial, tablet was full charged and i got this error, that's the story..
What could possibly go wrong?
Click to expand...
Click to collapse
Really sad about your problem bro.... something wrong with the procedure or your firmware.. there are many cases like you.. you can refer to :
http://androidforums.com/samsung-ga...help-firmware-flashing-failed-using-odin.html
http://forum.xda-developers.com/showthread.php?t=1877308&page=2
http://forum.xda-developers.com/showthread.php?t=1984717
http://forums.whirlpool.net.au/archive/1919243
but it is up to you to give it a try. Luckily for me, I did not encounter the same problem like yours while flashing with pc odin. I prefer using mobile odin. it is safe and easy. Good luck bro...

I am having the same issue on my P6810 (16gb). I cannot use the emergency recovery in Kies because I don't have the recovery code that it asks for (I bought the device as used faulty so don't know the update history). When I try to use the firmware upgrade / initialisation function to reset the tablet, Kies downloads the firmware but fails to connect to the tablet when I plug it in (in download mode, which I can access).
I have tried flashing a downloaded firmware using Odin3 v1.85 and it appears to start okay and copies cache.img but quickly hangs at the factoryfs.img stage.
I have tried different both win7x64 and winXP PCs with no success. I did try Heimdall, which uses a different USB driver, and while I did not have an appropriate Heimdall compatible firmware to flash, I was able to get a display of the current PIT information, so the tablet was communicating OK.
Does my device need repartitioning? I have seen many references to a PIT file, but don't know where to download it from.
This seems to be a common problem from what I can tell so far.
Any help appreciated.
Thanks.

Hello i have the same problem. I read all of your suggestions and guess that should be use a pit-file. Is this overwrite a system. I have troubled ROM compiled and want to install the new one downloaded from sammobiles fo my country. Am I right? Please help me?

Can't get into download mode. Tablet only shows a phone, a triangle and a computer...

I can't get download mode.
My tablet was off... when I turned on, was on a bootloop. I couldn't get into recovery, then I've enter into download mode. I tried to flash a stock rom, but odin failed.
Then I lost download mode and the tablet only shows a phone, a triangle and a computer.
When I plug to charger, doesn't shows the battery icon, but battery charges.
Maybe this is a brick?...
Thanks!

help
ofwise said:
I can't get download mode.
My tablet was off... when I turned on, was on a bootloop. I couldn't get into recovery, then I've enter into download mode. I tried to flash a stock rom, but odin failed.
Then I lost download mode and the tablet only shows a phone, a triangle and a computer.
When I plug to charger, doesn't shows the battery icon, but battery charges.
Maybe this is a brick?...
Thanks!
Click to expand...
Click to collapse
I might not be able to help but you can, can you let us know what ROM/recovery/what you were doing before you turned off your tab and anything else you can think of that may be relevant
Thanks

It's download mode with a different interface Reflash your Tab, use Odin.

I've installed cyanogen 10.1 RC without problems. The tablet worked fine. Then I plugged the tablet to charge. When I took again the tablet (after 10 hours more or less) it was off.
In this mode (triangle, computer, phone), I'm trying flashing a stock rom. Without pit file, odin fails saying "write error", and with pit file and repartion checkbox marked sais "there's no pit partition".
Only way to turn off the tablet is quitting the battery. When I put again the battery, the tablet still is off; but when I try to turn on/get into download mode/get into recovery... only shows the triangle, phone and computer screen...
I think that my galaxy tab is bricked... :crying:
Sorry about my bad english and thanks for your answers.

Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

ofwise said:
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try heimdall. Never tried by myself flashing system partition using it but work for recovery, boot, and param partition.

ofwise said:
Odin shows this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P3100XWALD2_P3100OXXALE2_P3100XXLD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> system.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to go into download mode and flash a custom recovery using odin. I recommend CWM. Then try to go into recovery mode and wipe data, cache, dalvik cache and factory reset (NOTE: It will delete EVERYTHING and your tab will be like out of the box). Now try to boot into android, if android doesn't boots up then use odin to flash a custom rom or find a stock rom for your device and then your tablet should be fine.
Good luck :thumbup: and happy flashing .
And if you found this helpful then don't forget to hit the thanks button.
Sent from my GT-P3100 using xda app-developers app

Nothing...
I've tried Heimdall and doesn't detect my device. I've tried to install another one CWM and the same problem...
I've reinstalled the samsung drivers into 2 computers, differents usb ports... no recovery, no download mode and the charging icon (battery icon) doesn't appear (but charges).
I think my tab is dead... I don't know how more I can do it.
Thanks for the ideas

OK, first off, that screen is a FORCED DOWNLOAD MODE, it will happen for several reasons (usually a bad ROM flash), all you had to do was flash the stock .tar file via Odin.
Your first mistake was checking "repartition" in Odin, YOU NEVER EVER WANT TO DO THAT EVER, now since you didn't have a PIT hopefully it just cancelled out before doing anything bad. try reflashing in Odin with the stock ROM.
Heimdall will not work just because you have the drivers for Odin, infact Heimdall has it's own DRIVER that will override the Samsung driver Odin uses on the USB port (and usually any other USB on that stack) you connect the tablet to when you do the driver install step in Heimdall.
FYI, if you are on windows 8 there is a good chance you still can't do jack yet, to my knowledge windows 8 PC's are a no go for android ROM flashing.

The computers I've tried to flash with odin are with windows 8. But I flash my phone without problems...
Maybe with another windows version. I'll give a try this afternoon at home.
Thanks!!

daniel644 said:
OK, first off, that screen is a FORCED DOWNLOAD MODE, it will happen for several reasons (usually a bad ROM flash), all you had to do was flash the stock .tar file via Odin.
Your first mistake was checking "repartition" in Odin, YOU NEVER EVER WANT TO DO THAT EVER, now since you didn't have a PIT hopefully it just cancelled out before doing anything bad. try reflashing in Odin with the stock ROM.
Heimdall will not work just because you have the drivers for Odin, infact Heimdall has it's own DRIVER that will override the Samsung driver Odin uses on the USB port (and usually any other USB on that stack) you connect the tablet to when you do the driver install step in Heimdall.
FYI, if you are on windows 8 there is a good chance you still can't do jack yet, to my knowledge windows 8 PC's are a no go for android ROM flashing.
Click to expand...
Click to collapse
I've only used Windows 8 for flashing so far and works perfectly fine in my experience

Trying with a pc on windows xp and the same situation... odin sais allways the same...
I've put a pit file that I found called "signed_espresso_20120220_16G.pit". I can't remember if I used another time... I'm not sure. But this last time I use it.
Could I do something more??...

ofwise said:
Trying with a pc on windows xp and the same situation... odin sais allways the same...
I've put a pit file that I found called "signed_espresso_20120220_16G.pit". I can't remember if I used another time... I'm not sure. But this last time I use it.
Could I do something more??...
Click to expand...
Click to collapse
YOU shouldn't EVER use a PIT file in Odin, especially if your not even sure it's the right one, using an incorrect PIT file can totally screw up your device.
The ONLY time you could ever need a PIT file is if you flashed a ROM that changed the format of the partition tables (like rfs to mtd or bml) which to my knowledge non of the ROM for these tablets do that.

Hrmmm... Have you tried to see if Samsung Kies can do anything about it?
I mean, really. Your system partition is corrupt so i doubt it can detect anything.
As a last resort could you open up the tab and pull out the battery? Or even let the battery completely run out?

I've already pulled out the battery many times. Letting the tab without battery at least 1 hour... 1 day... and when I plug it and try to access to download mode... only the same screen (triangle, phone and computer).

ofwise said:
I've already pulled out the battery many times. Letting the tab without battery at least 1 hour... 1 day... and when I plug it and try to access to download mode... only the same screen (triangle, phone and computer).
Click to expand...
Click to collapse
Check this out ofwise- h**ps://www.youtube.com/watch?v=pJnoiMTw5cY&feature=youtube_gdata_player
Note-replace (**) in the link with (tt).
Sent from my GT-P3100 using xda app-developers app

Fastboot sais "Waiting device"...

ofwise said:
Fastboot sais "Waiting device"...
Click to expand...
Click to collapse
Well, your f*cked.
Sent from my GT-P3113 using Tapatalk HD

[Q] Root attempt gone wrong

Hi All,
I've attempted to root my SM-900, using Odin 3.09 and followed all the usual steps.
Suddenly I got different coloured horizontal lines on screen and that probably means my attemp didn't go that well...
I've read I should go back to the original firmware using kies, and then try again.
So how do I restore the original firmware?
I have an image (.img) and understand I need samsung Kies.
Question: Do I use Kies or the new KIES3?
How to go from there?
Or is there another way to restore the firmware?
Thanks in advance!

I figured it out already....
I un-tar-red the recovery file. Leaving it as .tar solved the issue.

bricked
my tablet is stuck,tried different usb ports,different odins,different cables .gets stuck on set up connection,now all i get on screen is FIRMWARE UPGRADE ENCOUNTERED AN ISSUE

wolverinex66 said:
my tablet is stuck,tried different usb ports,different odins,different cables .gets stuck on set up connection,now all i get on screen is FIRMWARE UPGRADE ENCOUNTERED AN ISSUE
Click to expand...
Click to collapse
Please describe what is showing on tab's screen
Sent from my GT-S7562 using XDA Premium 4 mobile app

fixed
I was able to flash the stock recovery thanks

Had the same issues. Solved it by reinstalling the USB drivers. Via Kies 3, under the Tools menu. Worked perfectly after that. (Edit. ...for CFautoroot)
Sent from my SM-P900 using Tapatalk

Man that's gotta be a scary moment...
Sent from my SM-P900 using Tapatalk

Need advice
Frank_H said:
I figured it out already....
I un-tar-red the recovery file. Leaving it as .tar solved the issue.
Click to expand...
Click to collapse
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank you

wilsto said:
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank
Since the recovery image was downloaded as aan .tar file, which is a container file like .zip or.7z, I thought that I needed to unzip it.
You can mount the .tar file in Odin as it is, without unzipping it first.
You can find the recovery download location in the CF-root thread.
Click to expand...
Click to collapse

wilsto said:
I have the same problem... root failed with several colored line. and doesnt start anymore.
Can you explain to me what do you mean by "I un-tar-red the recovery file. Leaving it as .tar solved the issue." ?
Thank you
Click to expand...
Click to collapse
Mine did that after flashing a different firmware and trying to root. I solved it by first flashing the stock recovery in chainfires thread then rooting.
Sent from my SCH-I605 using XDA Premium 4 mobile app

Duly.noted said:
Mine did that after flashing a different firmware and trying to root. I solved it by first flashing the stock recovery in chainfires thread then rooting.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yep me too..

I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.

Install Kies 3, then go into the Tools menu and reinstall the USB drivers. Reboot. Try auto root again. Should work on the first try.
Sent from my SM-P900 using Tapatalk

dodo99x said:
Install Kies 3, then go into the Tools menu and reinstall the USB drivers. Reboot. Try auto root again. Should work on the first try.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
---------- Post added at 08:39 AM ---------- Previous post was at 08:35 AM ----------
heldc said:
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Click to expand...
Click to collapse
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?

paulskerr said:
I am having the same issue tried different computer with xp same result. Did you ever get it working or no? and if you did get working how?
Click to expand...
Click to collapse
I did. I did the uninstaller for the USB drivers several times, with no luck. So finally I just deleted the Samsung folders in program files and program files x86. I did not reinstall Kies, just the USB drivers from samsung.com. I used odin 3.09, and it went flawlessly. Well, mostly-wifi took a *long* time to reconnect the first time after boot, but I'd also installed the update just before rooting, so dunno if it was the rooting or the update.

heldc said:
I did. I did the uninstaller for the USB drivers several times, with no luck. So finally I just deleted the Samsung folders in program files and program files x86. I did not reinstall Kies, just the USB drivers from samsung.com. I used odin 3.09, and it went flawlessly. Well, mostly-wifi took a *long* time to reconnect the first time after boot, but I'd also installed the update just before rooting, so dunno if it was the rooting or the update.
Click to expand...
Click to collapse
I finally go also. I did exactly what you did. Thank you

Frank_H said:
Hi All,
I have an image (.img) and understand I need samsung Kies.
Click to expand...
Click to collapse
Where do I get this image?

How many are remembering to unhide developer options and then select usb debugging? The moment I did that everything worked

Whwre did you find the USB drivers on samsung.com? When selecting the SM-P900 it does not offer any for download.

heldc said:
I'm having this same problem. I downloaded CF-Auto-Root-v1awifi-v1awifixx-smp900.zip from download.chainfire.eu. I extracted the zip file, leaving me with a tar.md5 file. I try to flash that file, and end up with multicolor bars across the screen, exactly like if the video card dies on a mobile.
Here's what Odin has output as of when the error occurs. It flashes up a big red failed in the upper left box.
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-v1awifi-v1awifixx-smp900.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I flashed the original recovery from http://forum.xda-developers.com/showpost.php?p=50492301&postcount=234 and got a working but unrooted tablet. And I flashed CF with both 3.09 and 3.07, with a flash back to stock before each. Same thing every time-picture of a dying video card, except display is fine once flashed back to stock. Pic of the display added, on the off chance it helps.
Click to expand...
Click to collapse
So this happened to me, and this is my first time rooting. I have the tar file for recovery. How do I proceed? I haven't unplugged my note pro, can I just put in the new file in the pda and start, or do I need to restart odin? Really kind of worried...

[Q] Samsung says our GT-P3113 is "dead." Is it?

Son was playing Words With Friends and this Samsung Galaxy Tab 2 7" GT-P3113 was acting up. Only other recent change was my wife downloaded a Southern Living magazine. The screen went dark blue like it was on but not responsive.
None of the lengthy holding down the Power or Power and Volume Up would ever produce a reboot, only a battery symbol. I did get it into the load an alternate OS screen, but didn't try it.
Took into a Samsung Experience desk at Best Buy and they said it was DEAD. Apologized that this year and a half old unit was done and said that was "probably not what we were expecting as far as lifespan of the unit." Ya think????
Came home, as a complete noob with nothing to lose and downloaded Odin and the files to try and load the recovery. Odin recognized the device and tried to start installing but got to the first step and FAILED. Something about NAND.
So in your opinion is this completely dead or maybe I don't have the right files? If you have current links to the right files please point them out to me. I've spent tons of times find links that are dead.
Thanks!

dailyvideo said:
Son was playing Words With Friends and this Samsung Galaxy Tab 2 7" GT-P3113 was acting up. Only other recent change was my wife downloaded a Southern Living magazine. The screen went dark blue like it was on but not responsive.
None of the lengthy holding down the Power or Power and Volume Up would ever produce a reboot, only a battery symbol. I did get it into the load an alternate OS screen, but didn't try it.
Took into a Samsung Experience desk at Best Buy and they said it was DEAD. Apologized that this year and a half old unit was done and said that was "probably not what we were expecting as far as lifespan of the unit." Ya think????
Came home, as a complete noob with nothing to lose and downloaded Odin and the files to try and load the recovery. Odin recognized the device and tried to start installing but got to the first step and FAILED. Something about NAND.
So in your opinion is this completely dead or maybe I don't have the right files? If you have current links to the right files please point them out to me. I've spent tons of times find links that are dead.
Thanks!
Click to expand...
Click to collapse
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from www.sammobile.com exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.

No logo for reboot, which sammobile files?
tetakpatak said:
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from sammobile exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
Click to expand...
Click to collapse
Tetakpatak,
Thanks for jumping in!!!
1. That's the thing. We can never get the unit itself to the logo screen using that method, only the battery screen with a little sunshine symbol inside of it and only when the unit is plugged in.
2. I found sammobile before but my search for GT-P3113 produces only Cellular South files. This is a wifi tab only without a carrier. Does that make a difference? Can I use any of the listed files? Should I try each one?
Thanks!!!

No luck with sammobile files yet
tetakpatak said:
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from sammobile exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
Click to expand...
Click to collapse
tetakpatak, thanks for your help! please see my other reply.
i went ahead and tried one of the sammobile files. guessing as to which one because this is a wifi not cellular tab. when i ran it i got...
>Firmware update start
>SingleDownload
>boot.img
>NAND Write Start!!
>FAIL!
>
>Complete(Write) operation failed.
>All threads completed. (succeed 0 / failed 1)
Does this mean it is completely dead or do I need to keep trying files from sammobile?
Thanks!!!

dailyvideo said:
tetakpatak, thanks for your help! please see my other reply.
i went ahead and tried one of the sammobile files. guessing as to which one because this is a wifi not cellular tab. when i ran it i got...
>Firmware update start
>SingleDownload
>boot.img
>NAND Write Start!!
>FAIL!
>
>Complete(Write) operation failed.
>All threads completed. (succeed 0 / failed 1)
Does this mean it is completely dead or do I need to keep trying files from sammobile?
Thanks!!!
Click to expand...
Click to collapse
Hmmm, it isn't definitely dead, of course. That guy in the service was anyway bit dumb IMO.
With JTAG, man of skills can repair any device, no matter how hard bricked.
Actually to get further, it would help to know if you can reach download mode or recovery mode?

Tried two more from sammobile
tetakpatak said:
Does it mean you could reach the download mode? That would mean your Tab is not "dead".... (what kind of guy was that in the service?)
Try to see if you can get into the recovery mode (keep pressed power button & volume up and after Samsung logo appears second time, release the power button and keep the other one still pressed for about 5sec). If you get there, make factory reset and reboot. This will wipe your data....
Or if you can access download mode (power & volume down) turn it on again and download some recent firmware from sammobile exactly for your Tab model. In such case, reply my post and I will write you how to flash it with Odin.
Click to expand...
Click to collapse
Tetakpatak,
Tried two more from sammobile and both failed. Once mentioned NAND and the other did not. I see there is a NAND Erase option in Odin. Is that something I should be checking before Starting?
Not sure what else to do.
Thanks.

Reply
tetakpatak said:
Hmmm, it isn't definitely dead, of course. That guy in the service was anyway bit dumb IMO.
With JTAG, man of skills can repair any device, no matter how hard bricked.
Actually to get further, it would help to know if you can reach download mode or recovery mode?
Click to expand...
Click to collapse
Sure, I can hold Power and Volume Down to get to the screen to load a custom OS.
I'm
1. Opening Odin
2. Loading in the file from sammobile in the AP field
3. Leaving Auto Reboot and F, Reset Time checked.
4. Letting Odin check the validity of the sammobile file
5. Then plugging in the GT-P3113 and hitting Start in Odin
Thanks.

dailyvideo said:
Sure, I can hold Power and Volume Down to get to the screen to load a custom OS.
I'm
1. Opening Odin
2. Loading in the file from sammobile in the AP field
3. Leaving Auto Reboot and F, Reset Time checked.
4. Letting Odin check the validity of the sammobile file
5. Then plugging in the GT-P3113 and hitting Start in Odin
Thanks.
Click to expand...
Click to collapse
OK, @dailyvideo don't flash any P3110 build because the bootloaders differ in something!!
I have got meanwhile for you download links of an excellent stock UEUCMK3 firmware for your P3113 click HERE or you can also download it HERE
Now your flashing checklist:
use entirely Odin v1.85 or 3.04
run Odin as administrator
choose any stock firmware for your Tab and download (you probably did already), unzip it and you will get one tar-md5 file
tap in Odin on PDA, choose that extracted single tar.md5 file
run now (not before) your Tab into download mode
connect it with USB cable
Odin must display "Added" in status bar, left on the bottom
Odin must also display ID:COM port numer above it
If both there, click on "START"
Good luck!

Didn't work
I was using Odin 3.09 so I went back to 3.04 per your suggestion. I tried UEUCMK3 firmware I had already downloaded. Still didn't work...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Suppose I could try to use the firmware link you provided in case it is different. It's still downloading. Any other thoughts?
Thanks so much for your help.

dailyvideo said:
I was using Odin 3.09 so I went back to 3.04 per your suggestion. I tried UEUCMK3 firmware I had already downloaded. Still didn't work...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Suppose I could try to use the firmware link you provided in case it is different. It's still downloading. Any other thoughts?
Thanks so much for your help.
Click to expand...
Click to collapse
NAND is vital part of the device, IDK if it has to do with the bootloader. We might need a developer's advice, @Android-Andi, what do you think- can we help this poor mate?

Still trying
Ran again with your firmware and got the same results...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

I tought I just wrote back....? My post is gone...
NAND is vital part of the device, may consist bootloader or some other really important things.... IDK exactly, we might need a developer's advice here. @Android-Andi what do you say about this problem?

Thanks, next?
tetakpatak said:
I tought I just wrote back....? My post is gone...
NAND is vital part of the device, may consist bootloader or some other really important things.... IDK exactly, we might need a developer's advice here. @Android-Andi what do you say about this problem?
Click to expand...
Click to collapse
Tetapatak, Thanks for all your attempts to help! Super appreciate that.
Did you need me to reach out to @Android-Andi or did you post do that automatically?
I saw another post where someone did a partition and then came back and did your procedure and it worked but it wasn't for a GT-P3113. Not sure if that would work. I won't try it unless directed to.
Thanks.

dailyvideo said:
Tetapatak, Thanks for all your attempts to help! Super appreciate that.
Did you need me to reach out to @Android-Andi or did you post do that automatically?
I saw another post where someone did a partition and then came back and did your procedure and it worked but it wasn't for a GT-P3113. Not sure if that would work. I won't try it unless directed to.
Thanks.
Click to expand...
Click to collapse
He will see our mentioning and check this as soon as he can (he works now).
Try to google a bit about NAND partition, don't panic and have bit of patience, we will try to solve it.
Service can solve it for sure (not the dumb guy you've talked to )

Will wait
tetakpatak said:
He will see our mentioning and check this as soon as he can (he works now).
Try to google a bit about NAND partition, don't panic and have bit of patience, we will try to solve it.
Service can solve it for sure (not the dumb guy you've talked to )
Click to expand...
Click to collapse
Thanks will wait to hear back from you guys. Really can't tell you how thankful I am.
To the guy's credit at the Samsung Experience desk at Best Buy he couldn't get the OS screen to come up. I have trouble with it too at times unless there is enough of a charge. He said if he could get it to a certain point he could drill in and work with the code and really wanted to. I think because he could get to the OS screen he just assumed it was dead. To his credit too his dad died within 48 hours of our visit to the store.
Looking forward to the wizard advice.

dailyvideo said:
Tetapatak, Thanks for all your attempts to help! Super appreciate that.
Did you need me to reach out to @Android-Andi or did you post do that automatically?
I saw another post where someone did a partition and then came back and did your procedure and it worked but it wasn't for a GT-P3113. Not sure if that would work. I won't try it unless directed to.
Thanks.
Click to expand...
Click to collapse
Can you give this firmware a shot ?
http://terafile.co/82942a5b4d57/P3113UEUCMK3_P3113XARCMK3_XAR.zip
and one more mirror link if download speed is slow from above URL :
http://rapidgator.net/file/ec20cf98f5f712958760fd2b0457f939
But please make sure only Auto-reboot and Reset time are checked inside odin.......

No luck with new firware
Thanks lokesh, but still no luck. Here were the results...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

dailyvideo said:
Thanks lokesh, but still no luck. Here were the results...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Brother, Try using this .pit file that i am gonno share :
https://www.dropbox.com/s/wvn09tw1780irei/gt-p3110.pit
click on PDA in Odin and navigate to .pit file you have downloaded.
Now select the firmware you have downloaded as PDA and make sure only reboot option,,Repartition and reset time are checked.
Try this and give me a feedback soon.

Clarifying
lokesh.3440 said:
Brother, Try using this .pit file that i am gonno share :
https://www.dropbox.com/s/wvn09tw1780irei/gt-p3110.pit
click on PDA in Odin and navigate to .pit file you have downloaded.
Now select the firmware you have downloaded as PDA and make sure only reboot option,,Repartition and reset time are checked.
Try this and give me a feedback soon.
Click to expand...
Click to collapse
Lokesh,
Thanks for hanging in there with me. Just to clarify. Are you saying load your .pit file with the PIT button because when I click PDA to try and load that a .pit is not a valid extension.
Also, are you saying to load the .pit with PIT and the .md5 file with PDA ans Start with the Auto Reboot, Re-Partition, and F. Reset Time Options checked?
Just making sure I have all this right.
Thanks.

dailyvideo said:
Lokesh,
Thanks for hanging in there with me. Just to clarify. Are you saying load your .pit file with the PIT button because when I click PDA to try and load that a .pit is not a valid extension.
Also, are you saying to load the .pit with PIT and the .md5 file with PDA ans Start with the Auto Reboot, Re-Partition, and F. Reset Time Options checked?
Just making sure I have all this right.
Thanks.
Click to expand...
Click to collapse
You should choose in Odin just like last time: firmware under PDA. In addition, also choose PIT file under PIT. The PIT file will ensure your system partitions will be set properly.
If this also fails, it is possible that your internal memory is maybe corrupted and nothing can be written on the card.

Can't restore note 5 to stock

I am trying to restore my phone to stock because only stock modified rom works with VR, but doesn't play nice with android wear.
So back to stock I go, however when I put it in download mode load up AP with the file, and hit start it says "FAIL!" I have team win installed and that is how I get to download mode. I only had Auto Reboot and F. Reset time selected as well.
Can anyone advise me on what I may be doing wrong?
Here is the log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> cm.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!

Download the stock firmware again the one you're using might be corrupt, also make sure drivers are installed

I have the drivers installed, also tried 2 firmwares, trying one more now.
Was following this guide:
http://www.droidviews.com/restore-t-mobile-galaxy-note-5-sm-n920t-to-stock-5-1-1-lollipop-firmware/

no firmware seems to be working. I also tried a new cable and a few ports. No change.

tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.

Are you using 3.10.7?

I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.

Drachnem said:
tried a different odin, got a bit further but ran into the get PIT for mapping...
Seriously, whoever can get me back to stock, i'll send a paypal donation to say thanks.
Click to expand...
Click to collapse
How are you entering download mode?
Sent from my SM-N920T using Tapatalk

I've done it by using teamwin, also by holding pwr + home + volume down

guaneet said:
Are you using 3.10.7?
Click to expand...
Click to collapse
tried two...3.10.6, and 3.10.7

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
You have to pay 10.00 to download the files

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
Last time I checked you donated if you wanted, not forced to

Drachnem said:
Last time I checked you donated if you wanted, not forced to
Click to expand...
Click to collapse
Donated to try this fix, hope it works...

Drachnem said:
You have to pay 10.00 to download the files
Click to expand...
Click to collapse
As I recollect the fee is for the latest PAC, the others are free.

So it got further with the files and the pit file, but it didn't seem to fully work and I want to understand what may be wrong. It said failed in the first box but continued then the next box said pass.
The phone is now booted in setup mode but I wanted to understand what i may run into with this error or if I am fine...
Here is the log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_TMB_N920TUVS2COKC_N920TTMB2COKC_CL5966591_QB7480468_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/004> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:1/004> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:1/004> File analysis..
<ID:1/004> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Set PIT file..
<ID:1/004> DO NOT TURN OFF TARGET!!
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> SingleDownload.
<ID:1/004> sboot.bin
<ID:1/004> NAND Write Start!!
<ID:1/004> param.bin
<ID:1/004> cm.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img
<ID:0/005> Can't open the serial(COM) port.
<ID:1/004> modem.bin
<ID:1/004> cache.img
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)

audscott said:
I experienced the same problem. I was rooted, running whatever custom ROM my heart desired, but unable to flash to stock....until I tried one too many times and had a soft brick. After some research I found I needed a PAC file. You can get it here: http://dl.samfirm.net/page/2. There's not too much to say. Each segment is loaded seperately and take your time. If this works for you I'm happy for you and want nothing more than to help a fellow traveler.
Click to expand...
Click to collapse
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
I don't often have an answer, but after being the benefactor of the knowledge and kindness of others through the years, I'm glad to help when I can.

Drachnem said:
I've done it by using teamwin, also by holding pwr + home + volume down
Click to expand...
Click to collapse
That's the problem you are using twrp enter download mode by volume up+pwr+home
Sent from my SM-N920T using Tapatalk

Drachnem said:
These files did end up working out, ran pit first then the other file. Gave me an error but seems to be working fine for now.
Thanks again.
Click to expand...
Click to collapse
Are you able to post the files here (if that doesn't violate an XDA rule)? Trying to get the old ones and they seems to be gone and really don't want to have to pay, but I guess I will if I have to.

Hey Guys,
Having an issue getting one of my Galaxy Note 5 (SM-N920T) back to stock. I am able to flash stock firmware in Odin 3.10.7 but the phone is bricked. When I flash any stock firmware the phone reboots and is stuck at the Note 5 Splash Screen. If i reboot into recovery and try to do the factory wipe it tells me it can't find "E:" and fails. Only way I can get the phone to boot is if I flash a rooted kernel. Then I noticed it says the Baseband is unknown in settings. I was going to try flashing through ADB but it tells me ADB is disabled, same with flashing from external storage. I cant even get it to reboot into bootloader. I am starting to think the phone needs IMEI repair..

Database Info

welcome