Database Info

[Q] A real brick? Odin flash stock ROM just can be done but not work!

My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?

knightxmu said:
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
Click to expand...
Click to collapse
Did you try these instructions and files?
http://forum.xda-developers.com/showthread.php?t=1116251
Sent from my SGH-I997 using xda premium

nelomen said:
Did you try these instructions and files?
http://forum.xda-developers.com/showthread.php?t=1116251
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yes, but stucked too! it's the UCKD5 stock ROM.

re: unbrick
knightxmu said:
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
Click to expand...
Click to collapse
No wonder it did not work. He did not flash using the Ultimate Unbrick found here with step by step instructions:
http://forum.xda-developers.com/showthread.php?t=1116251
The filenames are all wrong in PIT/PDA/PHONE ........
Also the phone is NOT bricked at all.
Just need to remove battery, replace battery then go into download mode, Load Odin
with the correct files and while pressing both volume buttons plug usb cable into phone.
Then when com: lights up yellow with a number in it click START in odin window and
wait til the phone reboots into stock Froyo.

Misterjunky said:
No wonder it did not work. He did not flash using the Ultimate Unbrick found here with step by step instructions:
http://forum.xda-developers.com/showthread.php?t=1116251
The filenames are all wrong in PIT/PDA/PHONE ........
Also the phone is NOT bricked at all.
Just need to remove battery, replace battery then go into download mode, Load Odin
with the correct files and while pressing both volume buttons plug usb cable into phone.
Then when com: lights up yellow with a number in it click START in odin window and
wait til the phone reboots into stock Froyo.
Click to expand...
Click to collapse
it have been done, but not work!
my picture show another stock ROM, that is UCKE3. the UCKD5 stock ROM you mentioned have been tested! all the 3 files were loaded and the Re-Partition was checked, and flash it step by step 3 or 5 times.
i'm not a noob, i used to flash the stock ROM to unbrick my phone many times, but, i have no ideal with his device.....

help is needed!

I'm having the exact same issue
knightxmu said:
it have been done, but not work!
my picture show another stock ROM, that is UCKE3. the UCKD5 stock ROM you mentioned have been tested! all the 3 files were loaded and the Re-Partition was checked, and flash it step by step 3 or 5 times.
i'm not a noob, i used to flash the stock ROM to unbrick my phone many times, but, i have no ideal with his device.....
Click to expand...
Click to collapse
ive tried multiple methods found here and from google and androidcentral.com
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_UCKD5.tar.md5 is valid.
<OSM> PHONE_UCKD5.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> factoryfs.rfs
<ID:0/005> dbdata.rfs
<ID:0/005> cache.rfs
<ID:0/005> param.lfs
<ID:0/005> zImage
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!

sigh similar problems

MisterJunky is correct.
You have the wrong files loaded into Odin.

I am a noob but If it were me, here is a list of steps that I would try, one at a time, until I have tried everything. Yes, I know ODIN says passed, but try each step anyway. One step at a time, try ODIN and see if it works.
1. Make sure your Anti-virus is disabled and start ODIN as Admin(win7)
2. If you are running Win7, start ODIN with XP SP2 compatabilty. ( I don't need to do this but I have read of others doing this to make it work)
3. Make sure Win7 has no other programs running and leave the computer alone while it is downloading to the phone.
4. Remove all other USB devices connected to your computer (except keyboard and mouse) and change the USB port you have the phone plugged in to. No extended cables. Direct to the motherboard no USB hubs or through a USB connection on another device (this was one of my problems)
5. Boot CWM recovery (red) and format everything; boot, system, data, cache, sdcard and wipe Dalvik cache and battery stats. Pull out you SD card and format it with windows (not a quick format but a full format. Depending on the size coule take 15-20 minutes).
6. Delete all ROM files and ODIN files and download everything again. (constant problem when I had a HTC Inspire) Boot CWM and wipe everything again.
6. Uninstall all Samsung drivers, clean you registry, reboot, download current Samsung drivers. boot CWM and wipe everything again.
7. Scream, boot cwm and wipe everything again
Good Luck,
6

knightxmu said:
My friend's Infuse just bricked for flashing some wrong ROM maybe. I told him to flash the stock ROM with odin. The flashing process just can passed successfully but the device stucked at the first screen (SAMSUNG logo). UCKD5 stock stucked normally, and UCKE3 stock will stucked with a little rainbow.
He checked odin at this status:
and passed the flashing:
When the device is power off, he plug the data cable, the screen just show the very frist screen (a cricle) but no battery comes up.
Is his Infuse became a real brick? Any other thing he can do?
Click to expand...
Click to collapse
Rainbow???? Does your friend have a Rogers Infuse?
If his is from Rogers and not AT&T, you need the Rogers Gingerbread UXKG3 unbrick. It tends to get buried deep down in the forums since there are far more AT&T users than Rogers users.

[Q] Help! My Note 12 is "soft bricked" (I think)

Hi!
I need help.
I have the Galaxy Note 12.2, SM-P900 (wifi only version). The device is rooted but running stock recovery and ROM.
I was using Titanium backup as I do with all of my devices and chose to "Integrate Updates Into ROM". It seemed to go successfully but things went wrong once I went to reboot the device.
Upon rebooting, I saw the Samsung logo pop up then the screen went black, not off because I could see the faint glow of the screen lights at the edges, but the screen stayed black. It wouldn't boot. I left it for 10-15 minutes and nothing.
So I then held down the buttons to get into the standard recovery mode, which worked. I tried wiping cache and rebooting. Same thing.
So next I tried going into download mode, which I did, but that's an area I'm not sure what to do with.
I opened up Kies and connected the device but it wouldn't find it.
So I left it with nothing to do until the battery ran down.
Today I picked it up again, hoping that it would magically start up. Nope.
I put it back in recovery mode, wiped cache and did a factory reset, but that didn't work. I can still get into recovery mode and odin mode.
Please help! I really am hoping that I don't have a really expensive brick.

Followup information
To followup on my original post.
I was able to successfully put the Galaxy Note 12.2 into Odin mode, load up Kies on my PC and connect the Note to the PC.
In the "ID:COM" box it now says "0:[COM5]" with a yellow background and in the "Message" box it shows "<ID:0/005> Added!!".
So can I be hopeful that I might be able to use Odin to recover the Note?!
Thanks again for any help any of you can give. It is certainly appreciated.

Download odin 3.09
Go to samsung-updates.com site (thos s not Samsung's site, but there you can find firmwares for all sam's devices).
Choose sm-p900 (your model) section and download package for your country (CSC code)
Unzip downloaded package - you should have a file ending with .md5.
Click on AP button *Center to right in Odin), and select unzipped file that ends up with md5.
Wait until file is checked by odin, it can take some time - and click start.
Important: do not tick / untick anything on left side of Odin - do not tick repartition! Leave as it is when you start Odin.
And that's it - wait iunit process ends up. In case no boot, try to wipe data / cache again.

Unable to find SM-P900 firmware for the USA?
jba.33a said:
Download odin 3.09
Go to samsung-updates.com site (thos s not Samsung's site, but there you can find firmwares for all sam's devices).
Choose sm-p900 (your model) section and download package for your country (CSC code)
Click to expand...
Click to collapse
Hi Thanks for responding so quickly and thoroughly! I went to the updates site as directed and chose my device, but none of the firmwares shown are for the US. I searched online and it shows that the codes for the US are "AWS, CLW, DOB, TMB".
Any further suggestions?
Thanks again.

jopop said:
Hi Thanks for responding so quickly and thoroughly! I went to the updates site as directed and chose my device, but none of the firmwares shown are for the US. I searched online and it shows that the codes for the US are "AWS, CLW, DOB, TMB".
Any further suggestions?
Thanks again.
Click to expand...
Click to collapse
Try BTU - since this is wifi model it shold not really matter - and BTU is British one...

I am having this same exact issue...
I had root access, downloaded Rom Manager and clicked to install TWRP and it rebooted my tablet and did the same things you describe.
I am still downloading the stock image (it's pretty huge, over 1GB) and hope that this will work
I seriously JUST got this tablet. I hope it's not a goner, otherwise that's a ton of money down the drain.... I'll post back with any results once I try running the stock image through Odin.
Edit:
OK, so I was out all day while my tablet was in perpetual blank screen-on mode after the Samsung boot animation. I left it unplugged because there was nothing I could do about it until later anyway. So I let the battery die, and I just got home, plugged it in for a few minutes, boot it up like normal (just using the power button, no Odin or stock recovery) and it prompts me to sign into all of my accounts and stuff, as if I had just gotten the device. I had to re-enter all my info, download all of my apps again, and enable developer options, so I am assuming somehow my tablet reformatted itself into factory conditions after the battery died? I even still have root and supersu on my device, so yeah. I have no idea what ROM Manager did to my device but hopefully it was nothing permanent.
If anyone is having this issue, before you mess around with Odin and trying to reflash a stock image, maybe just let the battery run down, wait a while and boot up like normal?
I'll report back here if my tablet starts going crazy for any unknown reasons, but so far, it seems OK. Hopefully it really did just do a factory image restore by itself and my precious tablet is OK!

Where did you get the stock image? I used Odin to flash a rooted ROM but Odin failed and I now get a message that says the firmware upgrade failed. I can get into download mode and Odin recognizes my tablet but I don't have a file that works. What has me panicked is that it says my Knox counter is 1! I really regret now trying to root this. All I really wanted was to be able to add more apps to multi-window. That was not worth the trouble I'm in now. Please help!
Sent from my SM-N900V using XDA Free mobile app

jopop said:
Hi Thanks for responding so quickly and thoroughly! I went to the updates site as directed and chose my device, but none of the firmwares shown are for the US. I searched online and it shows that the codes for the US are "AWS, CLW, DOB, TMB".
Any further suggestions?
Thanks again.
Click to expand...
Click to collapse
jba.33a said:
Try BTU - since this is wifi model it shold not really matter - and BTU is British one...
Click to expand...
Click to collapse
XAR is the region code that you want.
I have a copy if you are in need of it.
larkhillv said:
I am having this same exact issue...
I had root access, downloaded Rom Manager and clicked to install TWRP and it rebooted my tablet and did the same things you describe.
I am still downloading the stock image (it's pretty huge, over 1GB) and hope that this will work
I seriously JUST got this tablet. I hope it's not a goner, otherwise that's a ton of money down the drain.... I'll post back with any results once I try running the stock image through Odin.
Edit:
OK, so I was out all day while my tablet was in perpetual blank screen-on mode after the Samsung boot animation. I left it unplugged because there was nothing I could do about it until later anyway. So I let the battery die, and I just got home, plugged it in for a few minutes, boot it up like normal (just using the power button, no Odin or stock recovery) and it prompts me to sign into all of my accounts and stuff, as if I had just gotten the device. I had to re-enter all my info, download all of my apps again, and enable developer options, so I am assuming somehow my tablet reformatted itself into factory conditions after the battery died? I even still have root and supersu on my device, so yeah. I have no idea what ROM Manager did to my device but hopefully it was nothing permanent.
If anyone is having this issue, before you mess around with Odin and trying to reflash a stock image, maybe just let the battery run down, wait a while and boot up like normal?
I'll report back here if my tablet starts going crazy for any unknown reasons, but so far, it seems OK. Hopefully it really did just do a factory image restore by itself and my precious tablet is OK!
Click to expand...
Click to collapse
Vlip3 said:
Where did you get the stock image? I used Odin to flash a rooted ROM but Odin failed and I now get a message that says the firmware upgrade failed. I can get into download mode and Odin recognizes my tablet but I don't have a file that works. What has me panicked is that it says my Knox counter is 1! I really regret now trying to root this. All I really wanted was to be able to add more apps to multi-window. That was not worth the trouble I'm in now. Please help!
Sent from my SM-N900V using XDA Free mobile app
Click to expand...
Click to collapse
you guys are going to need a couple of things...
the XAR firmware from Sammobile.
ODIN 3.09
CF-AutoRoot from General Section and the bc3 boot img.
If you need files I have them...
Also I have thread in the general section that you can use to un-brick and fix your tablet.
I have bricked and unbricked my device several times. Just remember don't panic and you will be fine. Let me know what you guys need and we will get you up and running again.
Bizack

1st thing. When you root your tab knox gets tripped. no way around this. So if this is a deal breaker, step on it and take it back. you will not get root love however.
If you do want Root, knox is tripped so why not? Follow these steps.
1. charge your tablet.
2. Down load these files.
Recovery Boot img nb3
TWRP Custom Recovery
Stock NC5 Firmware
CF-AutoRoot (go to His Post in General Section)
When charged, boot into download mode and flash the full stock package. (PDA in 3.07, AP in 3.09 ODIN) don't mess with the check boxes, when it finisheh verifying the md5 just hit start... Go take a break...
When that is done you will be back to stock, original just like you bought it.
Now boot back in to download mode and this time you are going to flash the NB3 recovery image tar... same place in ODIN as before. ( uncheck reboot in ODIN)
When that completes, disconnect your tablet and boot it back into download mode.
When you are back in Download mode, then you can safely flash the CF-AutoRoot.... (leave checks default and flash it in same slot in ODIN.
Finally, when that reboots, go back into odin and flash the custom recovery and then you will be able to boot into recovery and make a back up, (always good to make a back up) you can restore back to point in time. (that you made the backup.)
after you are all done, you can get Xposed installed and tweak the hell out if your rom. At minimum install Titanium Back up and freeze all of the knox apps.

what is "XAR firmware"?

ornobohornish said:
what is "XAR firmware"?
Click to expand...
Click to collapse
That, for some reason, is our Region code for Samsung firmwares...

ok thanks!

Stock Firmware Recovery Failing at system.img
Bizack said:
When charged, boot into download mode and flash the full stock package. (PDA in 3.07, AP in 3.09 ODIN) don't mess with the check boxes, when it finisheh verifying the md5 just hit start... Go take a break...
Click to expand...
Click to collapse
Hi Bizack.
Thank you for coming in and giving detailed information on restoring our devices. It has been maddening to say the least.
I downloaded all of the files that you linked to and followed your instructions.
However, when during the first step for flashing the full stock package, it fails at system.img
Right now it is giving me the "Firmware upgrade encountered an issue" screen, then there is some message in Chinese or Korean at the bottom of that.
I have tried Kies Emergency Firmware Recovery and it just doesn't recognize the device as needing it or being valid I guess.
So do you have any idea why it works up until system.img?
I had previously been able to use Odin to flash the firmware for China, then replaced it with New Zealand and those never failed at system.img.
But I really want it back to US firmware.
Thanks again for any help, suggestions or advice you can give.
Jo Pop

I was continuing to try to find answers online, and there found some questions about a "pit" file when people are changing regions?
Could this be part of the problem? I had accidentally flashed the Chinese firmware and then flashed the New Zealand firmware, but since then I can never get the United States (XAR) firmware to flash.
If it is, where would I find the right PIT file?
Thanks again.

jopop said:
I was continuing to try to find answers online, and there found some questions about a "pit" file when people are changing regions?
Could this be part of the problem? I had accidentally flashed the Chinese firmware and then flashed the New Zealand firmware, but since then I can never get the United States (XAR) firmware to flash.
If it is, where would I find the right PIT file?
Thanks again.
Click to expand...
Click to collapse
Flash it again in odin, this time Check "nand erease all", this will clear out any residual crap left over from failed flash attempts.
You did get the full firmware for the p900 from me?
Sent from my SM-P900 using XDA Premium 4 mobile app

Odin Failed at erase all nand while flashing XAR NC5 firmware
Bizack said:
Flash it again in odin, this time Check "nand erease all", this will clear out any residual crap left over from failed flash attempts.
You did get the full firmware for the p900 from me?
Click to expand...
Click to collapse
Yes I downloaded all of the files you provided links to and followed your instructions again. This last time I checked "nand erase all" as I was flashing the NC5 firmware you provided.
It failed at Erase.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Erase...
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
These problems only seem to happen when trying to flash back to the original XAR firmware. I had no problems when I had flashed the Chinese and New Zealand firmwares.
I'm at a loss, but I'm hoping that you are not.
I don't know if this helps, but on the Odin screen I have the following information:
Product Name: SM-P900
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 1
AP SWREV: A1
Also, when I go into recovery mode, on the bottom left it says that it is applying the CSC code of XAR even though the firmware currently installed on it is the XXU (New Zealand) one. EXCEPT for the one screen when you first go into download mode, before clicking up to accept, that screen is in Chinese or Korean.
If you have any other ideas, suggestions, need more info, pictures of any screens, whatever, please let me know.
My continued thanks for your help. I have spent a dozen hours on the phone with different Samsung people who have told me to do a factory reset and it will be fine, use Kies and do a recovery which never works, etc. So you have provided more actual technical help than any of them have.

Further info after Odin Fail during Erase
After I posted my last message, I went to reboot the device into recovery. It did load in, but at the bottom left there are error messages that were not there before.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I don't know if that helps more or means that I'm really screwed now.
At the top by the way it shows that the following: Android system recovery <3e> KOT49H.P900XXUANB3

jopop said:
After I posted my last message, I went to reboot the device into recovery. It did load in, but at the bottom left there are error messages that were not there before.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
E:failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
I don't know if that helps more or means that I'm really screwed now.
At the top by the way it shows that the following: Android system recovery <3e>
I am at a loss with the chinese firmware.
If you can live with the new zealand, go for it.
Somrthing has to have been changed witht the other firm wares if you cannot successfully flash the stock package.
You are on the nb3 recovery boot loader so you should be able to flash back to stock.
I would try and switch the usb port, remove device open kies reinstall drivers change port let the dirves re install and then try to flash it again. nand erease all and keep switching ports till it works. Find a usb2 port sometimes odin hates usb 3. Try odin 3.07 or 3.09.
I will be on the strip all week\weekend so I will try and look out for your post...
Good luck.
Sent from my SM-P900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

No progress. Tried reversing what I did in the first place.
Bizack said:
jopop said:
I am at a loss with the chinese firmware.
If you can live with the new zealand, go for it.
Click to expand...
Click to collapse
So after continued no luck, even after erasing the nand when flashing the XAR firmware, I went ahead and flashed the XXU firmware, no problem. Then I realized that I initially went from XAR to the Chinese version then to the XXU. So I factory reset everything and I reflashed the Chinese firmware (P900ZCUAND4_P900CHNAND4_CHN). No problem. Flashing went fine. Rebooted into Chinese.
So I again went in to recovery, did a factory reset, then rebooted into recovery, reloaded Odin 3.09 and attempted to flash the firmware that you linked to (P900UEU1ANC5_P900XAR1ANC5_HOME.tar).
And again it failed at the system.img.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> recovery.img
<ID:0/008> sboot.bin
<ID:0/008> system.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm at a complete loss why those other two firmwares can be flashed and reflashed with no issue, but the XAR version can not and Kies doesn't recognize it as needing help or when I try to force it to do something, it then says that it can not update my version of the device. I'm guessing that is because I am not in New Zealand or China.
Anyone have anything for this?
Click to expand...
Click to collapse

You might try getting into recovery and formatting the system partition, if stock won't try flashing the TWRP Recovery and format everything, but try system first.

[Q] Accidentally installed Chinese firmware, please help!

Hi.
The other day, I "soft bricked" my SM-P900 (Galaxy Note Pro 12.2 wifi only version) and as unable to get it to boot at all. Thanks to jba.33a, I was able to download and install (through Odin), a new firmware. Unable to find a firmware for the US, he suggested downloading the one for Britain.
So I downloaded and installed what I *THOUGHT* was the British firmware. Turns out, I accidentally installed the *CHINESE* firmware, P900ZCUAND4_P900CHNAND4_CHN. Now I'm "stuck" with it because I can't get rid of it or install over it.
When I booted it up, I was all excited to see the boot screen until it came up in Chinese. I switched the language to English, but it is still completely different. No Google apps, all kinds of Chinese icons and setup stuff, etc.
So I did end up finding and downloading the correct firmware for the US, P900UEU1ANC5_P900XAR1ANC5 which is for "Cellular South".
My problem is, I can not install any new firmware. When I attempt it through Odin 3.09, it reads the firmware file and everything seems fine until I click start, it goes through part of the process then it says "FAIL".
After it fails, it gets stuck in a firmware update failed mode. So to recover it, I followed another thread and installed TWRP.
The tablet boots again, but is still on the Chinese firmware. I have been unable to switch it using Odin or Kies.
PLEASE HELP! I need to install the Cellular South firmware and eliminate the Chinese firmware. Does anyone know how to do this?
Thanks for any and all help, it very much is appreciated!
Jo Pop

Most likley a bad download. Download it again. I also installed the chinese firmware just to see how it worked. As you said... No google apps. So i re downloaded the english version and flashed it with no problem.
Sounds to me like you just had a bad download (happens a lot)
Sent from my HTC6435LVW using Tapatalk

No luck redownloading? Any other suggestions?
Serinety said:
Most likley a bad download. Download it again. I also installed the chinese firmware just to see how it worked. As you said... No google apps. So i re downloaded the english version and flashed it with no problem.
Sounds to me like you just had a bad download (happens a lot)
Click to expand...
Click to collapse
Hi again.
Okay, so I've downloaded the firmware from a couple of different locations, but during the install, Odin 3.09 keeps failing right at "system.img".
Any other suggestions?
Is there a way to flash a firmware or ROM for the Galaxy Note 12.2 through TWRP?
Thanks again for any help that you can give.

jopop said:
Hi again.
Okay, so I've downloaded the firmware from a couple of different locations, but during the install, Odin 3.09 keeps failing right at "system.img".
Any other suggestions?
Is there a way to flash a firmware or ROM for the Galaxy Note 12.2 through TWRP?
Thanks again for any help that you can give.
Click to expand...
Click to collapse
Odin 3.07 will work. NOT 3.09. Use Odin 3.07.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

Partial luck but still not working.
Android.Ninja said:
Odin 3.07 will work. NOT 3.09. Use Odin 3.07.
Click to expand...
Click to collapse
Okay. So I rebooted the computer, etc. and I used Odin 3.07. It still would not let me put in the XAR (Cellular South) firmware, but I was able to get it to install the XXU (New Zealand) firmware. That seemed to be successful.
HOWEVER, once I rebooted the device and did the happy dance, I noticed that the device would NOT connect to wifi. I got a "Security Notice" that unauthorized changes were made and since that notice, I can not get wifi on.
So I tried installing the XAR firmware again, got to the "Firmware upgrade encountered an issue", which I know how to correct by reinstalling TWRP.
Interestingly, when I first go into Download Mode (Volume Up/Home/Power) and in the "Firmware Upgrade encountered an issue" screens, they are still in Chinese, so some remnant of that Chinese firmware is remaining in this tablet. Perhaps that is a source of some of the issues?
I promise there is a beer (or a drink of your choice) in your future if you can help me get this working with my XAR rom and wifi. Luckily I had done a full Titanium backup two days before this originally happened, so I have all of the backup files on Dropbox for when I get it working again.
Again, thanks for any and all help, it certainly is appreciated.

jopop said:
Okay. So I rebooted the computer, etc. and I used Odin 3.07. It still would not let me put in the XAR (Cellular South) firmware, but I was able to get it to install the XXU (New Zealand) firmware. That seemed to be successful.
HOWEVER, once I rebooted the device and did the happy dance, I noticed that the device would NOT connect to wifi. I got a "Security Notice" that unauthorized changes were made and since that notice, I can not get wifi on.
So I tried installing the XAR firmware again, got to the "Firmware upgrade encountered an issue", which I know how to correct by reinstalling TWRP.
Interestingly, when I first go into Download Mode (Volume Up/Home/Power) and in the "Firmware Upgrade encountered an issue" screens, they are still in Chinese, so some remnant of that Chinese firmware is remaining in this tablet. Perhaps that is a source of some of the issues?
I promise there is a beer (or a drink of your choice) in your future if you can help me get this working with my XAR rom and wifi. Luckily I had done a full Titanium backup two days before this originally happened, so I have all of the backup files on Dropbox for when I get it working again.
Again, thanks for any and all help, it certainly is appreciated.
Click to expand...
Click to collapse
No problem. lol.
Ok, so lets see. Originally you installed the Chinese firmware and now needing to get back to XAR = Cellular South, correct? Ok if so, it shouldn't be a big problem. I'll see if I can help you. First of all, don't worry. If you have a "Good Download" of the firmware and also Odin, this can be fixed, so don't worry. it's almost impossible to actually "Brick" the device.
If you have to repeat anything, don't worry just do it again so you can make sure that there is no questionable doubt that it's been done, or you have a good copy etc.
1. Go ahead and create a folder on your desktop and name it "P900 Old Firmware". Put any and all firmwares that you've downloaded in the folder. Lets not use those and just assume that theres a possibility of a bad download or something.
2. Now, go ahead and download a fresh copy of the XAR = Cellular South firmware. Just create another folder on your desktop and label it "P900 Working Firmware." Save the firmware to this folder.
3. Once downloaded, boot you device in recovery and wipe everything. If on the factory recovery, just choose the proper selection to delete, reset, erase everything etc. If on TWRP, choose wipe everything using the advanced options. ** You need to make make sure that when you boot into TWRP, go to the "Settings" button and put a "X" on "USE RM -rf instead of formatting." This is ABSOLUTELY Necessary for it to properly erase everything. Then choose to wipe everything. **
4. After everything is wiped. Boot the device into "Download Mode."
5. Make sure the device is connected good.
6. Now try installing the firmware again. Make absolutely sure that you do NOT touch anything else like repartition etc.
7. Let me know exacty what happens. Any types of messages, errors, etc.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

Details of the XAR firmware flashing failures so far...
Android.Ninja said:
7. Let me know exacty what happens. Any types of messages, errors, etc.
Click to expand...
Click to collapse
Hi Android.Ninja.
Thank you so very much for responding to my post and offering to help. I had forgot to click on "Instant Email Notification" so I didn't realize that you had responded. I had started another thread when I though I made some progress and was receiving alerts from there but just came back to this one.
Anyway, so today I spent the day trying yet again to make this happens.
You asked for *exactly* what happens, well I think I typed every freaking detail I could as this was happening. Hopefully it can help.
Here is a detailed version of events that has led me to where I am now, which is unable to reflash the firmware for the United States, XAR on my Galaxy Note Pro 12.2.
When I first got it, I rooted it using Chainfire's root method but kept the original recovery.
I was using it fairly regularly and enjoying it until one day I used Titanium Backup to "integrate updates" into the system ROM on a bunch of apps. It basically became soft bricked.
Kies was unable to help me.
I tried all kinds of things that I found on XDA and elsewhere, all to no avail.
So someone suggested that I flash a new firmware. Unable to find one labeled "United States" someone suggested just picking one since they are all basically the same. I accidentally chose the Chinese one. However it flashed with no problem. I was then able to flash over to the New Zealand firmware (XXU) with no problem.
Then someone told me that I needed the XAR firmware.
And that's where the troubles started.
No matter what I tried, which version of Odin, 3.07 or 3.09, which USB (2.0) port I used, rebooting the PC, reinstalling Kies 3 and reintalling the drivers, would allow me to reflash the XAR firmware.
However, I could flash and reflash the Chinese and New Zealand firmwares back and forth with no problem.
The only thing I noticed is that even when I have flashed the New Zealand firmware that the first screen you see when going into download mode by holding the buttons is in Chinese.
So today, in order to give you as much information as I can, I went through the whole process again in great detail. Hopefully this might allow you to see something that I was doing wrong that I didn't catch.
Here we go...
I flashed from the New Zealand to the Chinese firmware (P900ZCUAND4_P900CHNAND4_HOME.tar) using Odin 3.07.
The only options selected in Odin were "Auto Reboot" and "F.Reset Time". The rest were unchecked. The firmware was put in the PDA slot.
All good.
When device rebooted, I went to About Device, unlocked Developer Mode and turned on USB Debugging.
Rebooted the device.
All good.
Everything in Chinese firmware.
Then I went into recovery, at the top it had:
Android system recovery <3e>
KOT49H.P900ZCUAND4​
Then on the bottom left it had:
# MANUAL MODE #
--Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.​
Even though I flashed the Chinese firmware, my original CSC code is there.
So now I rebooted the device again, then put it in download mode.
In download/Odin Mode, it had the following in the top left corner:
ODIN MODE
PRODUCT NAME: SM-P900-CHN
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 1
AP SWREV: A1​
I then opened up Odin 3.07 and keping the same options selected as I did earlier, I inserted the firmware file I am trying to restore my device back to, P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 into the PDA slot. I waited for it to completely check the MD5 and the "Leave CS.." message to appear.
I then clicked "Start", and here is the result of that:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> recovery.img
<ID:0/008> sboot.bin
<ID:0/008> system.img
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)​
At this point when I try to reboot the device, I get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." There is also a bunch of stuff in Chinese below that.
I had a friend forward a photo of the stuff in Chinese along to a friend of another friend who translated it and said that it basically says the same thing about the firmware upgrade encountering and issue.
I've discovered through the 2-3 dozen times that I've tried this and tried doing different things that at this point, I can just flash TWRP using Odin 3.07 and the device will reboot or that I can just reflash the Chinese firmware to get back to where I was with the official recovery.
However in this case, I chose to flash in TWRP 2.7.0.2 and reboot the device.
Everything worked and it was still using the Chinese firmware.
I then rebooted into Recovery. Going into "Settings" in TWRP, I selected "Use rm -rf instead of formatting?".
On the Wipe menu, I chose "Advanced Wipe" then selected to wipe "Dalvik Cache", "Cache", "Data" and "System".
Here is the output of the wipe:
Updating partition details...
Full SELinux support is present.
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Removing all files under '/cache'
Wiping data without wiping /data/media...
Done.
Removing all files under '/system'
Updating partition details...​
To be safe and thorough, I did the same wipe a second time. Then I went back to the main TWRP menu and hit "Reboot", choosing the option to reboot into "Download Mode".
It gave me a warning about no operating system installed.
When I rebooted into Download Mode, there was no information at the top left corner where it usually said "Odin Mode". There was just the green Android in the middle with "Downloading... Do not turn off target !!" message underneath of it.
I then, using a newly downloaded copy of the XAR firmware that I got from sammobile.com and put in a new folder as you suggested, opened up Odin 3.07, keeping the same options selected as I had earlier. I set the PDA slot to the newly downloaded firmware file P900UEU1ANC5_P900XAR1ANC5_HOME.tar.
I let it do it's check of the MD5 file then I clicked start.
Here is the result of that:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900UEU1ANC5_P900XAR1ANC5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> recovery.img
<ID:0/008> sboot.bin
<ID:0/008> system.img
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)​
Another failure.
At this point, I shut down Odin and then rebooted the device into download mode.
This time, it has the following on the top left:
ODIN MODE
PRODUCT NAME: SM-P900
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A1​
I reconnected the cable, and reopened Odin 3.07.
At this point, rather than repeating the process over and over, which I have dozens of times, I went into Kies 3 to see if it would recognize it or if it would restore the firmware for me.
After I go into "Firmware Upgrade and Initialization", it asks me for my device model, which I enter "SM-P900" followed by my serial number. A window pops up saying "Prepare for firmware upgrade", it does a few things and then a couple of seconds later a screen pops up and says "This device's version cannot be updated." So I click ok, and close the useless Kies program.
When I attempt to reboot at this point, it gives the "Firmware upgrade encountered an issue" blah blah blah.
So I decided to try something different. I reflashed TWRP. Went in, setup the advanced wipe and wiped everything again.
This time I chose to wipe everything including internal storage.
The wipe was complete and successful so I again rebooted into Download Mode.
NOTE: The first screen you get to when you push the buttons to go into download mode as been all in Chinese ever since I first flashed the Chinese firmware, even when I flashed the XXU firmware for New Zealand, etc.
Anyway, after rebooting into Download Mode, I had the following in the top left corner:
ODIN MODE
PRODUCT NAME: SM-P900
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX WARRANTY VOID: 1
AP SWREV: A1​
I guess not having anything in /system is considered custom?
So using Odin 3.07 I chose the New Zealand firmware P900XXUANC4_P900NZCANA3_HOME.tar and put it in the PDA slot and pressed start.
Here is the result of that:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P900XXUANC4_P900NZCANA3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> cache.img
<ID:0/008> hidden.img
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!​
So that's two different firmwares that I can successfully flash.
The device reboots and shows up in English with "English (New Zealand) greeting me on the welcome screen.
I confirm in the About Device/Settings that the current build number is KOT49H.P900XXUANC4.
Time to reboot into Recovery.
Going into recovery I have the following at the top:
Android system recovery <3e>
KOT49H.P900XXUANC4​
Then on the bottom left it had:
# MANUAL MODE #
--Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.​
So that worked.
I have repeated this process in various ways over and over, and yes, over again with the same results.
I've downloaded the XAR firmware about 15 times.
For some reason, my device is blocking me from reflashing the XAR firmware and it boggles my mind, especially since I can go between Chinese and New Zealand so freely.
At one point, during this process, I followed someone's advice to click the "nand erase all" to clean up the crap from all the flashing. Here is the post where I posted those results. http://forum.xda-developers.com/showpost.php?p=53289858&postcount=16
I hope that was enough detail and information for you or someone to see or catch on to something that will help me.
A sincere thank you for any and all help.

Ok, Let me see what I can find out. Should be able to get this fixed with no problem. I'm going to try and see what needs to be done to fix it. I'll get back with you. Thanks for all the details. More is better in this case so don't worry.
Be back with you soon....
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

Android.Ninja said:
Ok, Let me see what I can find out. Should be able to get this fixed with no problem. I'm going to try and see what needs to be done to fix it. I'll get back with you. Thanks for all the details. More is better in this case so don't worry.
Be back with you soon....
Click to expand...
Click to collapse
Thank you so much for looking into it. That is much appreciated.

Any luck?
Android.Ninja said:
Ok, Let me see what I can find out. Should be able to get this fixed with no problem. I'm going to try and see what needs to be done to fix it. I'll get back with you. Thanks for all the details. More is better in this case so don't worry.
Be back with you soon....
Click to expand...
Click to collapse
Hi Android Ninja.
Have you had any luck with what I might be able to do to fix things? I've talked ad nauseum to different Samsung people to no avail. One woman somewhere up their chain wanted me to send the tablet to them and told me that it would take "4 to 6 weeks to fix". Meanwhile, my wife has figured out that I messed up the tablet.
Thanks again for all your help.

jopop said:
Hi Android Ninja.
Have you had any luck with what I might be able to do to fix things? I've talked ad nauseum to different Samsung people to no avail. One woman somewhere up their chain wanted me to send the tablet to them and told me that it would take "4 to 6 weeks to fix". Meanwhile, my wife has figured out that I messed up the tablet.
Thanks again for all your help.
Click to expand...
Click to collapse
Sorry I haven't had a chance to get back with you. I've been in the hospital. I'm better and at home now, and I will still try look into this for you as soon as I can.
Developers don't need no stinkin' signature!
If I've been able to help you, please hit the "Thanks" button.

jopop said:
Hi.
The other day, I "soft bricked" my SM-P900 (Galaxy Note Pro 12.2 wifi only version) and as unable to get it to boot at all. Thanks to jba.33a, I was able to download and install (through Odin), a new firmware. Unable to find a firmware for the US, he suggested downloading the one for Britain.
So I downloaded and installed what I *THOUGHT* was the British firmware. Turns out, I accidentally installed the *CHINESE* firmware, P900ZCUAND4_P900CHNAND4_CHN. Now I'm "stuck" with it because I can't get rid of it or install over it.
When I booted it up, I was all excited to see the boot screen until it came up in Chinese. I switched the language to English, but it is still completely different. No Google apps, all kinds of Chinese icons and setup stuff, etc.
So I did end up finding and downloading the correct firmware for the US, P900UEU1ANC5_P900XAR1ANC5 which is for "Cellular South".
My problem is, I can not install any new firmware. When I attempt it through Odin 3.09, it reads the firmware file and everything seems fine until I click start, it goes through part of the process then it says "FAIL".
After it fails, it gets stuck in a firmware update failed mode. So to recover it, I followed another thread and installed TWRP.
The tablet boots again, but is still on the Chinese firmware. I have been unable to switch it using Odin or Kies.
PLEASE HELP! I need to install the Cellular South firmware and eliminate the Chinese firmware. Does anyone know how to do this?
Thanks for any and all help, it very much is appreciated!
Jo Pop
Click to expand...
Click to collapse
Hi, I've been following your thread with interest and one thing that I've not been able to work-out is what lead you are using. There have been various reports of people unable to correctly flash their tablets with the USB3 lead and when they tried again with a standard USB2 lead it worked.
Just a thought!

USB 2 lead or USB 3 lead?
Dr Nicky said:
Hi, I've been following your thread with interest and one thing that I've not been able to work-out is what lead you are using. There have been various reports of people unable to correctly flash their tablets with the USB3 lead and when they tried again with a standard USB2 lead it worked.
Just a thought!
Click to expand...
Click to collapse
Interesting. I will have to try it. I've tried a number of the USB cables for the Note 3, but I've used them in a USB 2.0 port as some had suggested. I have not tried using a regular USB 2 cord with the USB 2 port.
Thanks for the suggestion, I hope it works.
Jo Pop

Hopefully you are ok?
Android.Ninja said:
Sorry I haven't had a chance to get back with you. I've been in the hospital. I'm better and at home now, and I will still try look into this for you as soon as I can.
Click to expand...
Click to collapse
I'm sorry to hear that you were in the hospital. Hopefully everything worked out and that you will be ok!

No luck with USB 2 cable and a USB 2 port
Dr Nicky said:
Hi, I've been following your thread with interest and one thing that I've not been able to work-out is what lead you are using. There have been various reports of people unable to correctly flash their tablets with the USB3 lead and when they tried again with a standard USB2 lead it worked.
Click to expand...
Click to collapse
Hi Dr Nicky.
I tried your suggestion about trying a USB 2 cable, but I had the same results. It wouldn't let me flash any of the copies of the XAR firmware that I downloaded (many) but I was then able to successfully flash as before, both the Chinese and New Zealand firmwares. This is maddening to say the least.
Thanks for your suggestion. Please feel free to send along any others.

*[HELP]* Need help unbricking Galaxy Note 10.1

Hi guys,
My galaxy note 10.1(2013) is was on <Stock> Android Kitkat .
Out of curiosity of rooting, i flashed CF Auto Root using odin.
The device restarted, and features seemed fine with new Root App too.
In few minutes however, device rebooted.. and went into a bootloop. :crying:
which still is, as long as device is on - has battery.
SUMMARY:
1. Recovery mode is not accessible now - device goes into recovery mode and restarts.
2. Normal boot is going into bootloop.
3. Download mode - HOWEVER is available !
PROBLEM :
-on trying to reflash stock rom/any Tar File for my device using odin,
odin fails with message :
NAND WRITE START
FAIL
----------------------------------------------------------------------------------------------------------------
Please help solve.
I do not want my beloved<soft bricked> device to die a sudden death .
Will appreciate you guys putting life back in it !

Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.

chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now

chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
will get back with update tomorrow.

glorifiedg said:
Having the exact same problem.
Tryed:
Flashing a 4.0.4 stock rom trough odin: sucess flash but still bootloop
Flashing a 4.0.4 stock rom trough odin + pit file for 8010 4.0.4: sucess flash but still bootloop
Flashing CWM and TWRP trough ODIN with auto-reboot and without autoreboot checked: sucess flash but still bootloop and no access do recovery
Flashing 4.1.2 or 4.4.2 stock: same error as OP
Getting pretty desperate now
Click to expand...
Click to collapse
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.

Anand.prashar said:
.. mine is not exactly the same.
you are able to write/flash onto NAND .. odin success for you.
My nand write itself fails.
End result is same, true there.
Click to expand...
Click to collapse
'Cause you probably didn't try the 4.0.4. I have nand write fail with the most recent versions also :S

Suggestion to no avail
chrismin13 said:
Oh, that's weird. Try updating your drivers and using Odin 3 1.85. Tell me if that helps.
Click to expand...
Click to collapse
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.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> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?

Anand.prashar said:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNE6_N8000ODDDNE4_N8000DDUCNE2_HOME.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> Firmware update start..
<ID:0/006> system.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing OS failed.
What could be hindering or preventing NAND write ?
Click to expand...
Click to collapse
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.

[/COLOR]
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.[/QUOTE
same problem here but i thing we need to clear all those built up cache in order to proceed right? but no boot recovery just the Odin downloading image. now if we can find a way to clear all those cache i'm sure'll work but don't know how to clear it from the "downloading do not turn off target" unless somebody figure this out.
Click to expand...
Click to collapse

* Serious issue awaiting resolution *
chrismin13 said:
You have the N8000. Correct? If you're working on a desktop try plugging the tablet in the back ports of your pc without using a USB hub or a usb 3.0 port. It sounds weird, I know, but that was the problem multiple times for me because the front ports of the computer use a usb hub that sometimes creates issues. And if you flash twrp what happens? I hope that it's not the chipset that's damaged. Also, what does download mode say? Does it write in binary status official? If yes, then flash stock frimware and recovery and try going it for warranty replacement. They won't understand what has happened I believe. And if all of this doesn't do anything try a different computer and a new usb cable. A computer with an OS older than Windows 8 would be great and without usb 3.0 ports. You can also try re-downloading all the files. Have you seen zedomax's video about unbricking our tablet? It covers everything I told you and much more so here's a link. Another idea is to use a toolbox for our device. Just tell me if anything of all of these methods works. I hope something does the trick!
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
Wow. Have you realized how many people have issues with kitkat? So many people report broken devices and they all run kitkat. That's wierd.
Click to expand...
Click to collapse
Sorry for delay, work kept busy.
You have the N8000. Correct?
-Yes
If you're working on a desktop ?
-No
- On laptop :
same laptop i used to root my tab using CF-Auto Root.
and have flashed ones in past on the older rom for this tab.
- Port : used USB 2.0
TWRP recovery ?
- Getting same error on odin as stock Rom.
<< I am attaching 3 snapshots >>
- Odin desktop Software in work
- Download mode of device
- Texts on download mode screen of device
<i believe it says custom, coz i had already 'seemingly' rooted stock rom>
------------------------------------------------------------------------------------------------------------
It would be worthwhile to mention the last flashing trial.
- it was upgraded to Kitkat released for this device
2 months ago : using Odin [as i had rooted the previous Default firmware too]
- having gotten bored with non-SU controls,
i flashed CF Auto Root
that would give me "SuperSU app" control without changing existing Firmware.
- Device rebooted after flashing (hopefully correct steps, i think)
"Super SU" app was available for me.
- Note : Upon opening app, i was prompted with a message
"KNOX has been detected on this device... would i like to remove/disable ?"
- I hit Yes.
Got a popup soon, that KNOX was successfully removed.
- and then, it went FINE for about an hour.
AND THEN CAME THE BOOTLOOP all of a sudden.
------------------------------------------------------------------------------------------------------------
Summary:
I am not able to figure out what could have caused this...
flashing/knox/ anything else ?

I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.

ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
Did you already tried to flash the 4.4 leaked version with the 5 files over odin?
And also the pit file provided there.
That solved my problem a couple of months ago.

ayeladawy said:
I have the same problem except that I can get too Recovery mode, but it's useless. It's been since April, so far no hope.
Click to expand...
Click to collapse
hey,
what do you mean by "useless" ?
please explain clearly.
i just got one of these the other day,gt-n8013, maybe it's possible to whip up a fix.
a thought i have is that a boned odin install may take on the same behaviour
as a certain kernel function where a temporary kernel to be booted to
may be being stored into ram, meaning when you reboot to odin mode
you basically pick up where you left off. poweroff your tab and then plug in
your charger like normal. if your battery image shows up then, your kernel is intact or mostly so.
if that's the case maybe running your battery dead or disconnecting it will
work like pulling the cmos battery in a pc to correct a bad bios configuration.
meaning after the power is finally and truly off then ram will clear completely and when
you recharge and reboot back to odin you will be at baseline again.
the above approach has worked with some lower end tabs i've owned
including the galaxy tab 2 7.0
m

Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?

dough30i said:
Hey, I ran the battery dead on it and when plugged there no charging indictor but instead it power back on but blank black screen no boot logo or nothing what does that mean?
Click to expand...
Click to collapse
okay, try for odin now, but try recovery first.
@dough30i
going back through this thread if you did the same thing with cf-root-crap you may have
damaged you bootloader. which is very not good. if you've gotten recovery up let me know.
you will need to get adb running and just for verification i need your model i.d.

No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...

dough30i said:
No recovery but I can get into Odin.see I done try all the step and every step no go. It something got to do with NAND FILE it won't write or something...
Click to expand...
Click to collapse
okay, are you trying to write a full firmware image or just a recovery or boot tar.md5?
or is it flat out no go?

Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-

dough30i said:
Full Firmware..oh i forget to mention at the beginning I had recovery boot logo, but then my stupid ass just had to mess with it more in the Odin to PC thing while I was trying to fixed it -_- my dumb ass got to anxious so I thought that when "NAND file not writing" I figure ohh maybe I needed to clear cache right so in the Odin I check repartition and I think that's why I have no samsung logo and recovery and now I back to somewhat square if u call it that. -__-
Click to expand...
Click to collapse
okay,
first, we do not put ourselves down. technology is unnatural, we make mistakes.
second, we do not panic or act rashly.
that being said if you can still get into odin, all is not yet lost. while i am pulling the pit file from
my device you will need to look up the correct way to write it to your device using odin.
i will be back in about 10 - 15 minutes.
use the force.
m

@dough30i
okay,
this is the pit file pulled from my n8013 . what i've read it should do the trick.
however, let's be clear.
1 you are in a bad situation, with nothing to lose.
2 this may not work but, then again it might.
3 you are the the final say as to wether or not you will attempt this
4 you have secured the correct knowledge on applying the pit file and writing in odin.
if yes to all of the above, download the attached file and remove the .txt extension
m
this is the thread i pulled the information from
http://forum.xda-developers.com/showthread.php?t=2268735

Custom Binary Blocked by FRP Lock

I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!

mryanmarkryan said:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
Click to expand...
Click to collapse
If you can't even mount it on Windows or get into recovery that's not good.

True Dat!
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?

mryanmarkryan said:
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
Click to expand...
Click to collapse
I would suggest pushing the root kernel to it anyway just to see if it will go.. I do have an FRPbypass but it's an apk meaning you need to install it and if you cannot mount to push it and then try to do adb shell pm install FRPbypass.apk then there's no point in that either.. Can you even get into download mode? If not the last thing I could suggest is the PIT file to repartition it. Unless someone else has a better idea? I do have the PIT file for odin too.
Also I think you're past the point of losing your data and if you can hold the volume down button and power button at the same time until it shuts off and turns back on again you can select factory reset and that's going to ruin all data..

My god, this happened to me on my first Note 5 I had. I was trying to restore it to stock before selling it and like an asshole I forgot to check for "OEM Unlock" and ran into that exact message. It put the fear of god into me. Like you I didn't have the serial number written down and I couldn't get it from anywhere. T-Mobile tech reps tried to tell me the IMEI number acts as a serial number, cool, that doesn't help me. I gave up on Kies and just played around with Odin after I was FINALLY able to find a stock firmware. I can't believe how difficult that was to get. I managed to flash the stock firmware thru Odin and I got the phone back! Stock as it came out the box.
I can't remember how I was able to get it into download mode but whatever button order I kept trying I finally did because Odin recognized the mofo and I flashed that stock firmware as fast as I could. It rebooted and I saw that beautiful stock welcome screen once more. Try to do this, I didn't need to do anything else.
For this reason I now keep a copy of stock firmware along with screen shot of my phone's status screen showing the serial number and everything else. All that's backed up to one of my external drives. Alone with several nandroid backups of various stages of owning this second Note 5 I have now. I'm running V10 of Darthstalker but I haven't heard of other users running into FRP lock. That would mean something tripped their OEM unlock option but how would that happen without you doing it? Is there something inside the ROM (a bug) that's tripping the option in Developer Options?
Best of luck with this, I know how stressful this can be. As far as getting your data back, yeah that's likely a no go. At this point you should be hopeful of getting a working phone back, let alone recover any personal data. Hope you can sort this.

More Info
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..

mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Yeah if you can get it into download mode and you've got the stock firmware you should be good to go and flash tru Odin. That's key. If I were you I'd be like, "To hell with my personal data! Get me a working phone back!".
Good luck.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!

MrMike2182 said:
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
Click to expand...
Click to collapse
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..

mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
Try downloading the newest odin version sometimes that can help.. Can you tell me how it's failing? Like what exactly happens when you try to do all the flashing? Did you try the adb commands that I suggested? You only need to install minimal adb and Fastboot on the windows pc and then connect your device and then open a terminal in the same exact folder where adb and Fastboot were installed and then type Fastboot devices or adb devices if it give you a bunch of numbers it means that it can see the device and we can then manually push and install the firmware. The other thing I suggest you try to do is flash the Lollipop 5.1 T-mobile firmware because I think it doesn't have frp on it yet and before flashing it go into the actual firmware you downloaded and delete cm.bin then rezip the firmware again and flash that one without the cm.bin but first try flashing the entire firmware as is with the md5 and all before resorting to deleting cm.bin.. Don't try flashing the Marshmallow 6 rom because that's where they started that frp bullcrap if you ask me. FRP stands for Factory Reset Protection... I understand the need for it and it's importance but Google could have been a lot more open about it and explaining to its customers what it's for and what it does not just do it and let most of us learn the hard way!!
When you try to flash in Odin tell me what file it fails on.
If none of this works this page is your last bet buddy
https://www.sammobile.com/forum/showthread.php?t=31136

I'm working on it now! Give you guys a summary of what happened as I as check off your suggestions..

SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol

Progress!
mryanmarkryan said:
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Click to expand...
Click to collapse
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Advice?
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
mryanmarkryan said:
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.

mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
It stopped right while trying to flash the recovery part of it so here's what I suggest you try to do.. unzip the 5.1.1 firmware you downloaded and unzip it again until you can see all the files in it and then manually flash them 1 by 1 in the AP slot but don't allow the phone to auto reboot uncheck that option and after 1 files flashed hold the volume down button and power button until you can select shut down device or turn off whichever then again hold the buttons to get into download mode again and continue until they are all flashed and then finally again hold the volume down button and power button and when it comes back on then select factory reset.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
E-POUND said:
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
Click to expand...
Click to collapse
If he flashes the latest firmware with the security updates he can never go back to 5.1.1 so I don't suggest he do that yet

Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?

mryanmarkryan said:
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
Click to expand...
Click to collapse
You're not rooted at all right now but you should not have needed to turn the imgs back into md5s again you should have just flashed them the way they were they don't need md5 just to flash. Try holding the volume down button and power button until it shuts off and turns back on again then select factory reset if that doesn't work then go into download mode again and connect to a Windows pc and use Smart Switch to try and fix it.

The reason I converted them was because Odin wouldn't find the files.. I tried just running them by typing a *.img but it didn't work. I'll go read about smart switch.. I"m learning stuff here
Update,: On a hunch I went back and ran the firmware install again, but just in it's original format. It succeeded and I'm setting up the phone now.. Thanks for your help MrMike. I appreciate you putting the time in..

mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
You are using the wrong stock firmware. Download the DPG1 firmware since that is was darthstalker v.11 is on. If you backed up your ROM then you don't have any troubles at all. Just ODIN back to stock, root, twrp recovery data only and done. But not all at once. First get the firmware going and reboot your phone. Once you know it's working the try rooting. Once you are rooted download TWRP and recover your data only.
Btw - FRP is when you log into your google account in the beginning of the setup so don't do that if you want to flash other ROMs.
P.S. I'be been running Darthstalker v.11 since it came out with no problems.