Database Info

Absolutely Dead after Failed Flash

Phone (Droid Charge) is completely unresponsive after I tried flashing to the factory ROM using Odin per this link: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11. (Two attempts to flash to this ROM aborted in CWM.)
When I used Odin, I got only <OSM> messages in the message box, ending with this one:
<OSM> All threads completed. (succeed 0 / failed 0)
The green status bar never appeared, and the "Start" button reactivated. I did this twice with repeatable results - nothing flashed. I then made the (apparently) huge mistake of removing the USB cable from the phone. It is now a paperweight. No response to power button, no response to plugging phone into wall outlet for charging (battery symbol doesn't appear).
Any ideas, or am I totally screwed?

My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.

My experience is nothing compared to others but I had a situation similar but for some reason I ended up using the Samsung Flash program instead of Odin and after hours of screwing around it worked.

imnuts said:
My guess is that Odin never picked up your phone when you attempted to flash. Have you tried to re-enter download mode to flash again? Make sure Odin detects your device, otherwise, nothing will happen.
Click to expand...
Click to collapse
I have tried to do this. Nothing appears on the screen when I connect the phone with the volume-down button depressed.
By the way, before I flashed the ROM (or tried to) I first did the PIT thing per the following thread: [HOW-TO]Fix your phone
Additional info: here is the log of ODIN messages.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI510_VZW_EP4_ALL_ONE-LTE-CP_REV03_user_CL706183_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!

Did you check "re-partition" in Odin before you flash?
If your phone doesn't display logo "Samsung" then your bootloader is shot. The phone is brick for good. Only by miracle it may come back to life. Just let it rest for a day then retry....it's in coma...sorry.

buhohitr said:
Did you check "re-partition" in Odin before you flash?
Click to expand...
Click to collapse
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Look, guys, I think it's clear that I'm hosed. But don't hesitate to ask for more details so that fixes can be developed to help prevent the next guy from suffering the same fate. Rooting has been an expensive, time-wasting exercise for me, and I'd rather it not be for anyone else, if possible.

based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.

buhohitr said:
based on what you described and the logs(you did everything right), you may have communication(driver) issue between your pc and your phone which cause corruption during flashing. This is the only reason I can come up with. I did pit file and factory stock 6 or 7 times already and no issue.
Click to expand...
Click to collapse
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.

The only time removing the USB cable during a flash can result in a brick is while it is flashing sbl.bin AFAIK because that is what contains the "download mode". You can usually recover it without too much trouble otherwise. I don't think that was the root cause.
Sent from my SCH-I510 using Tapatalk

MaxBuck said:
Your explanation sounds reasonable. And it sounds like the kind of unpredictable problem that could cause bricking for other people who go this route. In other words, not only does your phone need to be handled right, but things related to your main PC setup can also cause the process to go awry.
My goal here is to communicate to people that rooting is by no means "safe" or easy. Got no problem with those who wish to root, but doing so for trivial reasons like "I hate seeing all the bloatware" or "I don't like the way my screen looks" is pretty stupid IMO. In my own case, all the problems that I hoped rooting might solve (battery life; problematic Bluetooth; file backup) were not really solved by rooting - indeed, things got worse. And now I have a $700 paperweight.
Click to expand...
Click to collapse
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable) you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
If I read it right you flashed just the rom with repartition selected one of those times?
Sent from my SCH-I510 using xda premium

Hindle1225 said:
humor me while I go through this.... First things first.. You can't get into download mode? (Using a usb port on back of pc preferable)
Click to expand...
Click to collapse
That is correct - I can get no response whatever from my phone whether I attempt any of the following:
- going into download mode with battery removed OR installed, using the USB port directly on my computer.
- turning on the phone normally
- turning on the phone with the home button depressed
Hindle1225 said:
you opened odin, took battery out f phone, held volume button and than plugged usb end into phone right?
Click to expand...
Click to collapse
Correct.
Hindle1225 said:
there are a few bad pit files out there. Flashed pit file with the original froyo rom? You flashed pit file and stock froyo rom at the same time with repartition selected right?
Click to expand...
Click to collapse
PIT file came from here: [HOW-TO]Fix your phone
ROM installed at the outset of this process came from here: [12-14-11][ROM][EP4D] InfinityROM
ROM I was trying to flash to came from here: [ODIN][ROM][EP4D][FACTORY] Full factory restore 2.3.6 with radio - unrooted 12/7/11
Hindle1225 said:
If I read it right you flashed just the rom with repartition selected one of those times?
Click to expand...
Click to collapse
Not sure what you're asking here.

Again my knowledge is very limited but all of what you described I went through and eventually recovered. I pulled the cable out while installing. It didnt see it in Odin. Says it installed but didnt. And Im sure several other things. In my mind this thing is really hard to totally brick. I reinstalled all samsung drivers, downloaded the files again but used the Samsung Flash program to get back up.I tried different ports, cables etc.I went through the stuff you are for almost 8 hours lol before I finally got it running but it did. Cant hurt to try everything one more time. If you feel it is a paper weight then and have no recourse such as warranty sell it.Crap I might buy it cheap to waste a couple of hours(lol) just to see what I could do.

MaxBuck said:
I did that before I did the "PIT" thing. Then when flashing the ROM, I unchecked the Re-Partition box and then checked the Auto Reboot and F.Reset Time boxes as directed here. Checked only the PDA box and downloaded the ROM file to actually flash.
Click to expand...
Click to collapse
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.

MaxBuck said:
Not sure what you're asking here.
Click to expand...
Click to collapse
I was making sure I knew the steps you went through. If you really can't get into download mode, thats bad news.
imnuts said:
There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time.
Click to expand...
Click to collapse
This is what I was getting at.
Sent from my SCH-I510 using xda premium

imnuts said:
I have no idea what you're talking about with PIT thing. There is a PIT, you flash it with a ROM at the same time. You can't flash just the PIT to the phone. You have to flash a ROM at the same time. You also shouldn't need to use a PIT file when flashing 99% of the time with the Charge. As for what you can do, you can try a download mode jig, but you may want to figure out your communication issue on your computer before you try anymore flashing, and also read more and learn what you're doing before you ruin another phone.
Click to expand...
Click to collapse
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).

imnuts said:
...
2. Open up Odin, click PDA, and select the package you downloaded
3. Click on PIT and select the PIT file that you downloaded.
4. Get your phone into Download mode.
...
7. Press "Start" and flash the package.
Click to expand...
Click to collapse
It seems that step 2 is what you were confused on - while I can't speak to how others interpret this my interpretation is that there is something in both PDA and PIT before pressing start. I seem to remember something about folks that "unbricked" phones for something like $40 - mobiltech video or unbrickable mod are terms that come to mind. In the same How-To thread the above instructions are quoted from are folks mentioning such things at least.

Just get your phone unbricked for 40 bucks. then I would either get a new comp to flash with or borrow a friends comp. I suggest using spc latency checker on your comp to see if you have latency issues. Also, try a new cable. I have found that many cables don't work well.
Sent from my SCH-I510 using XDA App

MaxBuck said:
Look at the steps as I outlined them above. The "How to fix your phone" thread says that once you connect to the phone via Odin, you first check ONLY the "Re-Partition" box and press the PIT button in Odin -- that's what I did, and Odin indicated successful flashing of the charge.pit file.
Then, without disconnecting the phone or doing anything else, I unchecked the Re-Partition box, and checked the Auto Reboot and F.Reset Time boxes, checked the box next to the PDA button, and then pressed the PDA button. I was using the "stock" ROM identified above. The process stalled at the message, "<ID:0/03> Completed..", with no green progress bar at the top.
I think you and buhohitr are correct in that there is a communication issue associated with the USB connection between my computer and phone. That could happen to other people also (I have no other issues when using my computer USB ports) without advance warning. Hence my caution that rooting can be dangerous, even if you follow instructions here to the letter, as I believe I did.
Oh, and don't worry -- I won't be rooting any more phones. This whole experience has been a nightmare. Your comment that I should "learn what I'm doing first" is a nice cheap shot; I read all the threads here on rooting thoroughly before I started anything with the phone, and the initial rooting and flashing went flawlessly, which suggests I read the instructions pretty carefully. BTW, I have BS and MS engineering degrees and substantial computer experience (though no Linux experience whatever, which may in part be my problem).
Click to expand...
Click to collapse
I'm pretty sure you did it wrongly.
Like others comment, you only need press START button once, AFTER you select PIT file and ROM file (in PDA section), tick the Re-partition (and leave the other unchanged). No need to press START button twice (it seems you press it twice? based on your explanation) ...
If you still able to enter DOWNLOADING MODE, maybe better if you try to reinstall your samsung driver and maybe change the usb port used to flash, or if needed restart your computer ... and after it is detected by ODIN, do it again in the correct way ...
Hope you can unbrick your phone ...

For what it's worth, I've flashed the PIT file by itself in Odin with no problem. Completely acceptable but like was mentioned, you shouldn't really need it in most cases, even situations like this. But I wonder if somehow Odin attempted to flash sbl.bin and failed. That has the potential to hard brick the phone for sure since that file contains download mode. Does anyone know of another way to push the bootloader files to the phone?
Sent from my SCH-I510 using Tapatalk

Did you ever get this phone recovered and/or try one of those $40 programs someone mentioned? I am in the same boat it seems. =(

[Q] Odin FAIL at modem.bin

Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_HOME.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> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried already two different Firmwares but both seem to fail at the same point. I only installed the USB drivers not KIES so i guess it is not the reason.
Any help what is going wrong or what i should try to do?
Thanks a lot far any help.
Dave

Usual reply would be a faulty firmware file download another .
Other reply would usually be try a different Odin try different motherboard usb port .
A guess is that Chinese one is somehow different if nothing works .
jje

JJEgan said:
Usual reply would be a faulty firmware file download another .
Other reply would usually be try a different Odin try different motherboard usb port .
A guess is that Chinese one is somehow different if nothing works .
jje
Click to expand...
Click to collapse
Hi, thanks for your comment although it does not help me much.
I tried already 2 different firmwares which seemed to work with others and also tried different USB port.
As i mentioned both firmwares fail when reaching modem.bin however because the second firmware flashed in a different sequence doing the system.img before modem.bin it somehow added all the google apps on it and working so that's good news as it was not present before.
The PDA also shows the correct flashed version but CSC shows unkown now.
Anyway i want to be able to flash without any failures.
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
I still hope someone had this before and solved it.
Thanks for any comments.

davaze said:
Hi, thanks for your comment although it does not help me much.
I tried already 2 different firmwares which seemed to work with others and also tried different USB port.
As i mentioned both firmwares fail when reaching modem.bin however because the second firmware flashed in a different sequence doing the system.img before modem.bin it somehow added all the google apps on it and working so that's good news as it was not present before.
The PDA also shows the correct flashed version but CSC shows unkown now.
Anyway i want to be able to flash without any failures.
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
I still hope someone had this before and solved it.
Thanks for any comments.
Click to expand...
Click to collapse
perhaps a different version of ODIN? just spit balling here
EDIT: oops jje already said that, wipe cache, dalvik, factory reset??

davaze said:
Anyway i want to be able to flash without any failures.
No such animal exists .
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Lot different / fake / clone stuff from China posted on XDA that does not update flash or root properly .
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
CSC is not required to use a phone enter APN settings manually .
Try CSC changer from the market .
jje
Click to expand...
Click to collapse

JJEgan said:
davaze said:
Anyway i want to be able to flash without any failures.
No such animal exists .
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Lot different / fake / clone stuff from China posted on XDA that does not update flash or root properly .
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
CSC is not required to use a phone enter APN settings manually .
Try CSC changer from the market .
jje
Click to expand...
Click to collapse
Hi thanks for your comments!
Is there anyway to flash without modem.bin? What does modem.bin include?
Rooting the device works with no problem, installed the clockwork recovery and SU succesfully.
When trying the CSC changer it gives me no options.
The device seems to work normal but i must say that i never cleared any cache before starting to flash. The reason is that in some tutorials it is not mentioned unitl after the flashing completed. Also i'm a little affraid now to try it before flashing because i don't know what will happen if it fails again and i cleared cache etc. before.
I'm still hoping someone experienced the same issue and found a reason or solution to this. Untill now i'll do nothing as it seems to work inlcuding the google apps. Not sure if the unknown CSC will cause any issues in the future with specific functions though.
Will keep following this topic to hopefully find someone with similar experience.
Thanks to all that leave some help or comments!
Click to expand...
Click to collapse

Modem.bin is the radio you use to make and receive calls, use 3g internetsms and mms with. You should be able to flash a separate modem.bin file either through cwm or through ODIN...

I have similar issue. My tablet crashed outta nowhere when peel remote tried updating. My tablet never been unlocked or rooted. It stays stuck on nite 10.1 boot screen. Tried using Odin to reflash firmware. But it gets stuck on "NAND Write". I've left it there for hours/all night. I'm pissed because my tablet has performed flawless up till this point.
ODIN recognizes and confirms it connected/communicating. I properly unzipped firmware to show file with proper extension needed for flashing.
Can anyone give any insight or help. Or else I will have to call customer service since I'm still coveted under 1yr. Manufacturer warranty. I have so many pics n video of family on it. I really hope I don't loose anything. I may to try to install Odin on my second laptop to see if it makes a difference.

demandarin said:
I have similar issue. My tablet crashed outta nowhere when peel remote tried updating. My tablet never been unlocked or rooted. It stays stuck on nite 10.1 boot screen. Tried using Odin to reflash firmware. But it gets stuck on "NAND Write". I've left it there for hours/all night. I'm pissed because my tablet has performed flawless up till this point.
ODIN recognizes and confirms it connected/communicating. I properly unzipped firmware to show file with proper extension needed for flashing.
Can anyone give any insight or help. Or else I will have to call customer service since I'm still coveted under 1yr. Manufacturer warranty. I have so many pics n video of family on it. I really hope I don't loose anything. I may to try to install Odin on my second laptop to see if it makes a difference.
Click to expand...
Click to collapse
ODIN 3.07 didn't work for me, switched to 3.04 and that worked, not sure the version you have
I have rooted, unrooted and flashed a bit on mine with no issues, you seem to have attention to detail, but just make sure it's the right firmware for your model some folks have flashed regular galaxy tab ROMs with tragic results
EDIT: does KIES recognize it?

Ill check which version I have. Nit sure. I do have the correct firmware for 8013 model.
Kies doesn't recognize it in regular mode anymore. Now if I put the tablet in recovery/download mode, it recognizes but hangs on connecting. Before I never had issue with kies. I was gonna try restore through lies but since it didn't work, I went Odin route. Now Odin recognizes and confirms its linked/communicating with tablet in download mode. The process starts off good then stops on "nand write". Ill try different version of Odin to see if that works.
Thanks for reply. I hope I can recover it.
edit: my version says Odin3 v1.85
where do i find the newer ones or the ones you used? i got mines from the sticky thread i believe.
update: i found the other versions. i tried 3.04. it got passed Nand Write start. but then said failed. it went straight from nand write to operation failed. i didnt see the other stuff in between like op has. at least its progress..lol ill try again then try a different usb port. if those still dont work then ill try to download another firmware file from somewhere. anyone has a link to latest jellybean firmware for 8013 model? one thats known to work.

demandarin said:
Ill check which version I have. Nit sure. I do have the correct firmware for 8013 model.
Kies doesn't recognize it in regular mode anymore. Now if I put the tablet in recovery/download mode, it recognizes but hangs on connecting. Before I never had issue with kies. I was gonna try restore through lies but since it didn't work, I went Odin route. Now Odin recognizes and confirms its linked/communicating with tablet in download mode. The process starts off good then stops on "nand write". Ill try different version of Odin to see if that works.
Thanks for reply. I hope I can recover it.
edit: my version says Odin3 v1.85
where do i find the newer ones or the ones you used? i got mines from the sticky thread i believe.
update: i found the other versions. i tried 3.04. it got passed Nand Write start. but then said failed. it went straight from nand write to operation failed. i didnt see the other stuff in between like op has. at least its progress..lol ill try again then try a different usb port. if those still dont work then ill try to download another firmware file from somewhere. anyone has a link to latest jellybean firmware for 8013 model? one thats known to work.
Click to expand...
Click to collapse
does auto play pop up when you plug the tablet in? that's how I manage my media anyway. I only use KIES if I have to, only recognizes the note like every third time I plug it in. and it says that my gs3 is unsupported. I feel like the Samsung drivers get screwy sometimes
EDIT: just curious can you get into recovery mode?

jaydubbbbs said:
does auto play pop up when you plug the tablet in? that's how I manage my media anyway. I only use KIES if I have to, only recognizes the note like every third time I plug it in. and it says that my gs3 is unsupported. I feel like the Samsung drivers get screwy sometimes
EDIT: just curious can you get into recovery mode?
Click to expand...
Click to collapse
i get the notification thing on computer going off only when tablet is in recovery mode. by recovery mode you mean by pressing power and volume down at same time. then when it gets on warning screen you press volume up. then it goes into ODIN/Downloading mode. i can get there. i tried 3.04 and 3.07. both give me same deal. After Nand Write goes through its paces then itll say all threads or operations complete. Write Nand Failed. then itll show Failed up top in that other box also. i tried different usb ports also. so not sure what in the world is the deal. the firmware i got from the official firmware download thread. then i got the one for 8013. its a zip. i extracted it so the file with proper md5 extension would be visible.
before all this, i had no issues with KIES with my Note 10.1 or SG3. now KIES wont recognize it. Only ODIN will, once tablet is in ODIN MODE.

demandarin said:
i get the notification thing on computer going off only when tablet is in recovery mode. by recovery mode you mean by pressing power and volume down at same time. then when it gets on warning screen you press volume up. then it goes into ODIN/Downloading mode. i can get there. i tried 3.04 and 3.07. both give me same deal. After Nand Write goes through its paces then itll say all threads or operations complete. Write Nand Failed. then itll show Failed up top in that other box also. i tried different usb ports also. so not sure what in the world is the deal. the firmware i got from the official firmware download thread. then i got the one for 8013. its a zip. i extracted it so the file with proper md5 extension would be visible.
before all this, i had no issues with KIES with my Note 10.1 or SG3. now KIES wont recognize it. Only ODIN will, once tablet is in ODIN MODE.
Click to expand...
Click to collapse
recovery is hold power and volume up, I added a pic of what it looks like. A factory reset will erase everything on your tablet. I'm not a pro, but thats why I asked if you could access the tablets files through auto play
EDIT: I need to learn ADB there might be a way to fix your problem through that. wish I could be more helpful
EDIT 2: it always takes me a couple times to get into recovery, it seems to be a timing thing

jaydubbbbs said:
recovery is hold power and volume up, I added a pic of what it looks like. A factory reset will erase everything on your tablet. I'm not a pro, but thats why I asked if you could access the tablets files through auto play
EDIT: I need to learn ADB there might be a way to fix your problem through that. wish I could be more helpful
EDIT 2: it always takes me a couple times to get into recovery, it seems to be a timing thing
Click to expand...
Click to collapse
ok...nope...cant reach that screen. when i try it tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" only mode that works is ODIN mode from pressing power and volume down.
hmm....i kinda know how to adb from my Nexus7 usage as i recovered one of my n7 that had a similar crash. but i havent seen a guide or whatever for commands to enter in for galaxy note 10.1. or any kind of tool like n7 has. ill check the other tools i have loaded as i think some were capatilble with more than one device. ill keep trying to see if i can get in recovery mode. i had redownloaded and extracted the correct firmware. so ima see if that changes anything.

demandarin said:
ok...nope...cant reach that screen. when i try it tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" only mode that works is ODIN mode from pressing power and volume down.
hmm....i kinda know how to adb from my Nexus7 usage as i recovered one of my n7 that had a similar crash. but i havent seen a guide or whatever for commands to enter in for galaxy note 10.1. or any kind of tool like n7 has. ill check the other tools i have loaded as i think some were capatilble with more than one device. ill keep trying to see if i can get in recovery mode. i had redownloaded and extracted the correct firmware. so ima see if that changes anything.
Click to expand...
Click to collapse
like I said, it takes me like three tires to get the timing on the recovery mode. wish I knew more, good luck!

since i cant get into recovery, i tried using ODIN to reflash stock recovery. everything goes fine at first. then it says Write failed. for some reason anything i try to write to my tablet is failing. i see in odin 3.07 version they have an option called Nand erase/reset or something. i guess thats to erase everything i have on NAND. but i thinking that would clean tablet clean of everything. do you know anything about that option?
just tried a second time to flash stock recovery. its failing. i think i might be left with no choice but to call samsung customer service for a warranty claim.
this is crazy because my tablet was pure stock. no root or unlocking. and a simple update of that damned peel remote app crashed my $%^^ and put it in the state its in now. this is the only issue ive ever had since owning the tablet since summer time. makes no sense!
i appreciate the ideas though.

demandarin said:
since i cant get into recovery, i tried using ODIN to reflash stock recovery. everything goes fine at first. then it says Write failed. for some reason anything i try to write to my tablet is failing. i see in odin 3.07 version they have an option called Nand erase/reset or something. i guess thats to erase everything i have on NAND. but i thinking that would clean tablet clean of everything. do you know anything about that option?
just tried a second time to flash stock recovery. its failing. i think i might be left with no choice but to call samsung customer service for a warranty claim.
this is crazy because my tablet was pure stock. no root or unlocking. and a simple update of that damned peel remote app crashed my $%^^ and put it in the state its in now. this is the only issue ive ever had since owning the tablet since summer time. makes no sense!
i appreciate the ideas though.
Click to expand...
Click to collapse
No idea about the NAND options, ODIN 3.07 didn't work for me, I have 3.04 and haven't used it since I updated to 4.1.2. That sucks that the peel update borked your %¢#! . Especially because it's a stock app! I updated peel about a week ago with no issue. Not being able to get into recovery is probably a bad sign. I keep hoping someone smarter than I would chime in. I hope Samsung takes care of you

thank you for the suggestion to use another version of ODIN....i have been screwing with this for a day and half thinking that every version of stock rom that i tried was broken in some way....turned that ODIN v3.07 does not work so well...found ODIN v3.04 and worked perfectly.

Recovery mode is easy, from power off hold down volume up and power. Hold both buttons in until you see the samsung logo, release power but keep holding volume up until recovery appears... Works everytime...

Same problem - half solved
davaze said:
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_HOME.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> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried already two different Firmwares but both seem to fail at the same point. I only installed the USB drivers not KIES so i guess it is not the reason.
Any help what is going wrong or what i should try to do?
Thanks a lot far any help.
Dave
Click to expand...
Click to collapse
Hi Dave and all
I am i EXACTLY the same situation - Just bought n8000 in china with chinese firmware and wanted to change for European. I encounterted the same problem.
After formum research and many tests of softwares/ usb ports/ odin versions. I got to a point when after crashing during instalation (like in davids situation) i couldnt turn on the device anymore (black screen saying that i should do recovery via kies)
I installed CWM via Odin and it helped.
The tablet started again with european system and applications and seemd to work well.
UNFORTUNATELY: The S note is crashing before it's even loaded and while using tablet i experiece lags for ex when typing address in internet app.
I made a factory reset and cleaned cache - still nothing.
Please help if you have any ideas.
David: How did you managed to solve your problem? Did you managed to finish the update withou a crash?
Best regards
Filip

[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

Bricked GT-P5110 - Need Help

Here's my problem with my Galaxy Tab 2 10.1 GT-P5110.
I never had a problem in almost 3 years until now, but it has been used alot more than normal over the past few months due to ill health. I had used it in the evening with no issues. Next morning it wouldn't turn on. So id pressed the power button for 10 or so seconds and it started to boot. It got to the Galaxy Tab 2 screen and hung and wouldn't boot any further.
After googling I found loads of sites saying you could press the power button along with the volume up button ect to get it to boot or to get you into recovery mode, these didn't work but did take me to the download page. After googling again I found that you can flash the rom ect so I used Odin and the correct firmware file.
It worked, I used it for half hour or so then put it on charge !
After an hour charging I went to use it and it was dead again and wouldn't boot past the Galaxy Tab logo as before. I tried pressing the power and volume buttons again with no luck so as flashing it fixed it before I did the same again.
It didn't work this time, all that is now on screen is a message stating " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" it wont power off but just reboots to that screen.
I tired connecting to Kies but it isn't detected. Ive tried using older versions of Odin with the firmware that work previously and still the same issue. Also tried a different cable, different USB ports and a different PC. Only way it turns off is when the battery dies.
Im not too fused about loosing and data as I can reinstall apps ect but I really don't want to loose my Tab as its my lifeline at the mo as I'm recovering from a spinal injury and spend alot of time laid down. If anyone can help id really appreciate it, thanks in advance

I should add, when i try flashing it again it fails at, NAND Write Start!!

Here's my problem with my Galaxy Tab 2 10.1 GT-P5110.
I recently had the same problem of finding the correct Oden download because I wanted to root and install a different ROM. Factory firmware has to much clutter and junk I will never use. This is what I did and it works. Odin 3 v1.85, CF-Auto Root espresso 10 WiFi, Shakatu recovery clockwork unofficial 6.0.3.1 p5110.tar, and finally downloaded Cyanogen Mod (CM12). Try that Odin version and try again with the factory firmware.
I never had a problem in almost 3 years until now, but it has been used alot more than normal over the past few months due to ill health. I had used it in the evening with no issues. Next morning it wouldn't turn on. So id pressed the power button for 10 or so seconds and it started to boot. It got to the Galaxy Tab 2 screen and hung and wouldn't boot any further.
After googling I found loads of sites saying you could press the power button along with the volume up button ect to get it to boot or to get you into recovery mode, these didn't work but did take me to the download page. After googling again I found that you can flash the rom ect so I used Odin and the correct firmware file.
It worked, I used it for half hour or so then put it on charge !
After an hour charging I went to use it and it was dead again and wouldn't boot past the Galaxy Tab logo as before. I tried pressing the power and volume buttons again with no luck so as flashing it fixed it before I did the same again.
It didn't work this time, all that is now on screen is a message stating " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" it wont power off but just reboots to that screen.
I tired connecting to Kies but it isn't detected. Ive tried using older versions of Odin with the firmware that work previously and still the same issue. Also tried a different cable, different USB ports and a different PC. Only way it turns off is when the battery dies.
Im not too fused about loosing and data as I can reinstall apps ect but I really don't want to loose my Tab as its my lifeline at the mo as I'm recovering from a spinal injury and spend alot of time laid down. If anyone can help id really appreciate it, thanks in advance[/QUOTE]

Ive tried using Odin 3 v1.85 with the same rom that worked for me before, but it fails again, below is the log
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5110XXDNH2_P5110OXADNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should i be looking at the PIT file and flashing that, if so please could someone help me locate it and advise how i should flash that, thanks

Same probs here