Database Info

How long does flashing a kernel with Odin take?

I'm trying to get my wife's Infuse from stock UCLB3 (no root, not CWM) to CM10. The first step I tried to take was to root the phone so I could install TiBu and back up everything.
I tried flashing a custom kernel (Entropy's DD) that included CWM. Odin saw the phone, I clicked PDA and located the tar.md5 file as the instructions said to do. Clicked Start... got this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 2012.04.05-ODIN-Entropy_DD-GB-zImage.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..
Click to expand...
Click to collapse
And it's been sitting there about 20 minutes now. Nothing else happening with Odin. My HD activity light is flashing, so something is happening, but, I thought it should be rather quick.
Has Odin actually done anything on the phone? Is it bricked at this point??
EDIT 1: Gave up, yanked the cable and Odin showed "Failed." Power cycled the phone and got the "uh-oh" Download Mode screen (phone-!-pc). Reconnected to PC, Odin saw it, clicked Start again and the process went all the way through and rebooted the phone. Now I'm looking at the Samsung logo and the female computer voice just told me I had about 2 minutes remaining.
EDIT 2: Phone rebooted. Have red recovery now. All is well. SuperUser installed. Installing TiBu right now.

Sounds like you're on your way. Just make sure that you flash an ICS rom before flashing a JB rom.
But to answer your question, it should only take 10 secs or so to flash a kernel.
Sent from my SGH-I997 using xda premium

Nice job- for a little while I thought we might be reading a story about you sleeping on the couch.
good work !

Pony Express said:
Nice job- for a little while I thought we might be reading a story about you sleeping on the couch.
good work !
Click to expand...
Click to collapse
Yeah, you and me both!! lol

Kies failed installation
Hello,
Thank you for your help with this.
I was trying to free up some space on my wifes Samsung Galaxy Europa GT-I5500 but for some reason Kies 2.2 did not detect pics and vids and asked me to install a firmware update which may resolve this, which I attempted to do somewhat unsuccessfully. I sourced the firmware it recommended and began the installation which it gave an error for and then left her phone somewhat bricked I think.
That's when I started checking the forums because I've updated a few Android phones to new OS's using a variety of aps, I came across this xda-developers blog about how to use odin v.1.85 to correctly install the pda software.
I began the process and then ran into a problem which is instead of flying through the steps it hung at the setup connection stage. I waited over an hour on the second attempt to see if it would continue but no joy, I did keep checking the processes in task manager to see if the software was still responding okay and it seemed fine I checked the communications through com port an there was data being written to the handset aswell.
When I disconnect the phone it does not go in to download screen for what was timed as 40 mins, I am also not sure why this is.
After more reading and research on the concern I found Odin v4.28 worked with Europa_I5500_v1.0.ops which I have somewhat adjusted using a development package but there are other ops files available for many of the handsets on market. This software installed the firmware I downloaded GT-I5500 H3G. I realize the difference in the s/w where one does not support ops files
Its 12:30 now and it is all done phone working okay. No thanks to Kies which caused a me a lot of grief this evening and a wasted night.
Thank you for all your help, if it wasn't for people like you I would still be trying to fix the handset so many thanks.

[Q] Skyrocket Bricked odin stuck

Hi you all guys, few days ago i purshaced an skyrocket sgh i727 and it was working perfect, then when i was using the
internet browser my phone ramdomly turn off, i just powered on but it never boot up so i decide to boot it up on clockwork
mode and restore to factory data after that the phone did no boot anymore neither in clockwork mode, when i try to power it
on it shows the samsung splash but stuck there, the phone can be put on download mode which is a good signal however when i
try to install a stock rom from odin this does no start, it keep saying initializing step, i though my battery was
discharged and i tried the battery in a friend's phone but the battery was full charged, so i discarded that was a battery
issue, i installed the lastest kies driver, i got differents odin version, downloaded few times differents stock rom version and re tried to intalled; but odin keep sticking on initializing step, tried differents batteries (full charged), differents usb cables, differents computers, but its seems the phone is completely bricked i tried almost everything also i found that kies can make an emergency restore but when i try to do it, kies request me the error code to proceed, but i dont have such code since my phone never give me an error on installing, it just doest start the restore with odin, when i plug my phone its recognized from odin and shows as added, can you suggest me something? im tired of trying all what i described above and the phone does no have warranty since i purshaced it on ebay and the seller doesnt no accepted to be responsible since the phone worked when he sold it, i cant find any place to purshace a main board but before to purshace one i think there will be posibility to fix it since its still easy to power it on download mode without the JTAG, i cant get it on clockwork mode anymore http://forum.xda-developers.com/images/smilies/crying.gif

First off, I can't really make complete heads or tails of your problem. Please use sentences and paragraphs.
Second, is Odin recognizing your phone when you plug it in? Read the ODIN sticky.
Third, how long is your phone "stuck" on the Sammy splash for? You're definitely booting into CWM recovery and not factory recovery, right?
Honestly, if your phone turns on, it's not hard-bricked and it can be saved. There are lots of stickies here that walk you through how to root/unroot, restore to stock, use ODIN, etc. Read through those and that'll give you your best shot at finding an answer.

response
Hi im sorry if i writed it with sentences and paragraphs, well actually odin does recognized the phone and shows as added, but when i start the restore the phone keep in download mode and odin just stuck in the step that says initializing.
I used another battery, another usb cable and other computer but odin keep sticking in that step.
I tried downloading differents odin versions and differents stock rom version from differents sites but i can see its not a corrupt download.
the phone had CWM but in the time i made a factory reset from the CWM the phone did no boot anymore on CWM neither the OS because it stuck on the Samsung splash, this splash stuck permanently maybe hours if i dont remove the battery.
I think im booting on CWM im not sure because (it does no appear the menu to install zips make factory reset, clear cache partition etc)
Kies recognize my phone also but unable me to make an emergency restore until i put the error code in the box that pop up (i dont have such error code since my phone does no give me any error the process just doesnt start)
i tried killing kies in the task manager because i read sometimes kies intefere with oding while restoring, i can make put the phone in download mode as i said but im not able to make the restore because ODIN Stuck on INITIALIZING MODE.
I read some forums and post before i post but i havent found nobody with the same issue i just found this http://forum.xda-developers.com/showthread.php?t=1240333 but this didnt work for me

jakeharriss said:
I think im booting on CWM im not sure
Click to expand...
Click to collapse
In fairness, at least you're not out flashing ROMs and saying this.
How are you trying to boot into recovery? Are you holding both volume buttons and the power button down, and keeping them down until the Sammy splash comes up? Or are you just using the power button? If you're just pressing power, you're trying to boot a phone that has no ROM, and you'll have the same result every time.
Second, are you positive you're using the right version of Odin? v1.85?
Third, when you plug your phone into the computer and Odin, does the screen look like the screenshot in the OP of this thread?
http://forum.xda-developers.com/showthread.php?t=1773659
I'll be really honest, this screams of user error, and that's really the only explanation I can think of--especially because the phone can apparently still be forced into download mode. Maybe someone more experienced has seen this happen before and can help more than I can, but from the panicked style of posting and your asking questions about whether it's booting into recovery or not, I have to assume that it's user error. We just have to figure out what that error was.

thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb

jakeharriss said:
thanks for your answer to my post i apreciate you all your time, well actually i use the both odin version the Odin v1.85 and the odin v3.04 also the odin rom installer (i mean the odin package that you just need to plug the phone and then press start to update it) yes i hold the both volume button + the power button and i release it when the samsung splash comes up but now it does no give me the CWM since i used it to factory reset the phone and i think neither the factory recovery menu, however i can hold the volume down + plug the phone and then start it on download mode by presing the volume up button.
When i turn the phone in download mode, the phone appear in my odin as added like in the screenshot you sent me, then i select in the pda checkbox, then i choose the stock rom from my desktop, i leave the other checkbox selected like when oddin start ( i mean selected the options on auto reboot and F. Reset Time) then i press start, odin verify the rom and when it follow to the next step, odin stuck on initializing procees but my phone stays on download mode and do not pop any error neither the odin, as i said i dont think is a corrupt rom because i downloaded different isc version isc 4.04 and isc 4.03 also android froyo 2.3.5 but nothing works also i used different computers and usb cables and tried with a friend battery full charged maybe i dont have the OS in my phone as you say but my question is how to reinstall it if oddin doesnt seems to work on my phone also i have a galaxy s3 and i installed the jelly bean without a problem in the same computer with the same odin and cable usb
Click to expand...
Click to collapse
read this, its a sticky for newbs, follow it to the t, read the the whole post 3x b4 you proceed http://forum.xda-developers.com/showthread.php?t=1652398, if that doesnt work, either user error or hardware problem with nand

Make sure in Odin Only the reset time and reboot boxes are checked. Don't re partition.

Hmm... Well I occasionally have your initial problem, where my phone randomly turns off. Here, it doesnt boot right away, but I have to remove all power sources (battery, cable), put the battery back in, then it turns on fine, no questions asked.
What ROM were you using at the time? My phone started doing this after I installed the Liquid Beta 2Jellybean Rom. If you were using that at the time, it may have just been a ROM issue. Hope I helped...
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Brick LOGS PIT
Hi, well actually i was running the stock rom 2.3.5 GINGERBREAD, that was the rom that came with my phone, i tried the step to enter my skyrocket in recovery mode but im not able to do it, the odin keep sticking on initializing i have tried the steps you gave me, is there a way i can get an error code to try the emergency restore from kies? because i dont know where to get an error code,
i tried to re flash the CWM but odin also stick on initializing
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
and this is the log when i disconnect the phone from my computer
\<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
i have reading a post about PIT
PIT – the PIT file refers as ‘Partition Information Table’. This is only useful for fixing bricked devices if somehow something changed with the partition table layout of the phone’s system memory. But in normal flashing, you should not use this file, or you may screw up your phone if handed carelessly.
does anyone have any idea how can i remap my partition in my phone or if it nessesary?
also here i leave the log when i try to make a restore with odin to an stock rom
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation.. (in this step my phone stuck while trying to install and never advance)
when i unplug this is what appear
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007>
<ID:0/007> Get PIT for mapping..
<ID:0/007> Removed!!
<ID:0/007> There is no PIT partition. (It keep saying i dont have a PIT partition)
<OSM> All threads completed. (succeed 0 / failed 1)
do you all guys have any idea what is going wrong? i tried to turn in restore mode following this steps
ENTERING IN TO RECOVERY MODE IS THE SAME METHOD FOR BOTH STOCK AND A CUSTOM RECOVERY (CWM)
Now turn off your phone, unplugged(might work plugged in)
Press and keep both volume keys down
Then press the power button while still holding down the volume keys
When you feel the phone vibrate or see a logo on the screen, release the power button but not the volume keys.
When screen goes black release the volume keys.
Wait a few seconds to boot in to recovery
You are now in recovery mode
But when i release the power but and keep holding the volume button my screen keep stuck in the samsung splash even when i release the volume butto + the power button after the splash comes up
I appreciate your time and im sorry if i dont write in paragraph senteces etc i just tried to explain my issue as it was posible for me thanks

i think your problem was this "odin v3.04 also the odin rom installer", never heard of the odin rom installer used for our phones, you could of fracked up the partitions, but i dont know the fix for that, if there is even a way to fix it
edit: nvm, i read that it was a prob b4 you tried that, then its a bad nand, there might be a way to push a recovery back onto the phone using adb, just cant find the post on how
here it is, it will get you started, you need to learn how to use adb http://forum.xda-developers.com/showpost.php?p=31172875&postcount=19

Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?

jakeharriss said:
Can you explain me what does NAND mean please, well when i mean odin installer i mean a comprimed package of odin that comes with the rom but you dont need to download the rom separately because this package include exerything its the same like the other odin but instead of use the PDA box you just plug the phone and once is added, you just press start and this does everything, the only thing that looks weird for me is that the phone can be put on download mode without any problem, and you said that if the phone can be put in download mode without j tag this mean its not breaked, do you have any information about if if i can make a re partition in my phone and resolve the PIT issue that odin says?
Click to expand...
Click to collapse
The thing you are taking about is an Odin one click.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?

jakeharriss said:
Yes, this is absolutely what im trying to say but i didnt know how to say it, tried to flash a leaked 4.04 isc, that previously worked perfect for 3 skyrockets i had and i updated them without a problem, the matter was i never meant to update this phone but i had to try it due in that moment the phone ramdomly turned off and it did no allow me to boot up my OS, so i got into CWM and press factory reset and then i reset the phone but it never boot up back it just keep sticking in the samsung splash, then i tried to go back to the CWM again but now i couldnt do it again, so i tried to install the rom leaked 4.0.4 with odin one click but it never passed, just stuck in the intializing step, then i tried to use the odin 1.85 and downloading an stock rom and putting in the box PDA, but also kept in sticking in the Intializing step never transfered anything to my phone my phone was always in download mode and never gave me an error, i did tried the odin 3.04 that i used to flash the rom in my galaxy s3 i9300 but also kept with the same issue, im not sure if it hard bricked because i can get into the download mode easily, but im unable to get in the recovery mode following the right steps, im thinking is a PIT issue here i found this threat for another model
http://forum.xda-developers.com/showthread.php?t=1760107
this guy explain he had his phone hard bricked and flashed a PIT file to his phone and could restore it back
Do any of you all guys have ever flashed a pit file or have any idea about what is happening to my phone?
Click to expand...
Click to collapse
We don't have a pit file for the skyrocket. At least as far as i know. You should be able to flash the stock firmware if you can get into dl mode. Use Odin 1.85 and follow vincoms guide
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Yes so do i think the same, however for any extrange reason everytime i put my phone in download mode my phone stick in this step
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I727UCLF6_I727ATTLF6_I727UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation.. (in this step my phone stuck while trying to install and never advance)
i tried using differents odin version, differents stock roms, different usb cables, differents usb ports and computers, also reinstalled the right drivers for my phone and i verified it in the device manager from my computer, so i can say the issue is in the phone
i tried to reinstall the CWM but it also keep on the initializing step so if this dont pass there is no way to get in CWM and neither to the factory recovery mode, as i said everytime i try to get in factory recovery mode i cant due my phone stuck in the samsung splash and never goes black as it should to say that now is on factory recovery mode.

Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

xcrazydx said:
Install kies, Run odin as administrator, use sammobile stock firmware.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I did it but keep sticking in download mode with the odin in initializing step even my kies download the emergency restore firmware and it stuck while trying to install is there a way a can make a dual boot without the cwm or factory recovery working?

I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?

UBetchYa said:
I am having the exact same problem and have done just about all the same steps you outlined before I came across this thread. What was the final resolution for getting past the "Initialization.." phase in Odin?
Click to expand...
Click to collapse
Hi well i tried the whole method i could but i realized that would be quicker buying a new motherboard for the phone i got it on 50 usd on ebay it was a look that a guy tried to change his broken screen but he couldnt and decided to put his phone on auction i won and i repaired my phone however i send the mainboard to a friend of mine and he said the he couldnt repair it, i talked with a guy that said he could create the partition map again but i couldnt understand him maybe you can talk to him but he explained me that what killed my phone was to put a leaked firmware and make a wiping on the partition from the restore mode http://forum.xda-developers.com/member.php?u=3597010 this is the guy just send him a message wish you good luck with that

[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