Database Info

[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] Help! My Note 12 is "soft bricked" (I think)

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

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

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

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

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

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

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

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

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

what is "XAR firmware"?

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

ok thanks!

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

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

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

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

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

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

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

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

*[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

Software brick on a tab 2(5113) ?? unable to do anything with the "cache" folder...

Software brick on a tab 2(5113) ?? unable to do anything with the "cache" folder...
HiYall, got my tab 2 (5113 and using Candy6 ROM for 5110) that I carry around cause my memory sux. The other night (4 days ago) was transferring some maps onto my tab 2 and I fell asleep, with the tablet unplugged. To wake up with the tablet's battery dead. Of course, the first thing I did was plug it in (3 mornings ago) to find later a nice message saying that encryption failed? I didn't tell it to encrypt. Now, when I boot, I get that message about failed encryption and 2 options; the back arrow (does nothing) or reset the tablet, ok, s'all good, don't care as I did a backup of all the important things 2 days before. Now, I'm okay with full wipe and reinstall. I searched for the last 3 days all over this forum and google search with no solution.
I have TWRP 3.0.0.0 recovery installed
unrooted ages ago
Candy 6 ROM was installed, love it, oc'ed at 1.5ghz, stable, rarely & very little heat.
I also have an OEM ROM 4.2.2, tried to flash it with ODIN, no go, FAIL
tried the Shakatu 4.2.2 ROM as well, same
tried reflashing the Candy 6, same (using TWRP)
always the same, unable to mount /data (invalid argument)
using TWRP, unable to wipe, format, factory reset
unable to change the file system as well in the cache folder as pointed in a great many threads, it's in EXT4 in the candy 6 ROM, tried all the formats available, EXT3, EXT2, FAT, exFAT, F2FS, all the same error, (unable to mount storage).
Don't take me wrong, I know practically nothing about Linux and only followed instructions to the letter on the procedures to do. I only wish to give you the information that is relevant.
Thanks in advance
So,
Big

Can you post the odin log when it fails?

Lightracer said:
Can you post the Odin log when it fails?
Click to expand...
Click to collapse
Would be my pleasure....
This is the ROM I have:
HTML:
P5113UEUCMK3_P5113XACCND2_HOME.tar.md5
and here is the most recent log, running the flash as I'm typing this...
HTML:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> Sbl.bin
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Judging by the green process bar, seem to be at 40something% - 45% maybe???
"Auto Reboot" & "F. Reset Time" are the only boxes ticked on
I also tried the stock bootloader, pit & kernel to no avail... but this log is with AP only...
HTML:
P5110_JB_SBL.tar.md5
signed_espresso_20120220_16G.pit
espresso-any-root-kernel.tar.md5.zip
I also tried ADB, Simple and full install, none of it successful and I didn't mention that I also killed Skies...
oh yeah, am also using an OEM Samsung cable and running Odin as admin, firewall & AV are off...

diesel13 said:
Would be my pleasure....
This is the ROM I have:
P5113UEUCMK3_P5113XACCND2_HOME.tar.md5
and here is the most recent log, running the flash as I'm typing this...
<ID:0/005> Added!!<OSM> Enter CS for MD5..<OSM> Check MD5.. Do not unplug the cable..<OSM> Please wait..<OSM> Checking MD5 finished Sucessfully..<OSM> Leave CS..<ID:0/005> Odin engine v(ID:3.1205)..<ID:0/005> File analysis..<ID:0/005> SetupConnection..<ID:0/005> Initialzation..<ID:0/005> Get PIT for mapping..<ID:0/005> Firmware update start..<ID:0/005> SingleDownload.<ID:0/005> Sbl.bin<ID:0/005> system.img<ID:0/005> Complete(Write) operation failed.<OSM> All threads completed. (succeed 0 / failed 1)
Judging by the green process bar, seem to be at 40something% - 45% maybe???
"Auto Reboot" & "F. Reset Time" are the only boxes ticked on
I also tried the stock bootloader, pit & kernel to no avail... but this log is with AP only...
P5110_JB_SBL.tar.md5signed_espresso_20120220_16G.pitespresso-any-root-kernel.tar.md5.zip
I also tried ADB, Simple and full install, none of it successful and I didn't mention that I also killed Skies...
oh yeah, am also using an OEM Samsung cable and running Odin as admin, firewall & AV are off...
Click to expand...
Click to collapse
The only thing i can think of is that your system partition seems to be corrupted because Odin failed to flash the system image. Some of our devices have the emmc brickbug which can make the device not boot or do anything (sudden death) or have corrupted partitions. I think the only way to fix it is to either have the motherboard replaced or update the emmc firmware. I might be wrong though but the symptoms and the logs do suggest it could be the emmc brickbug. (Unless your kernel has been patched which fixes this bug)

Lightracer said:
The only thing I can think of is that your system partition seems to be corrupted because Odin failed to flash the system image. Some of our devices have the emmc brickbug which can make the device not boot or do anything (sudden death) or have corrupted partitions. I think the only way to fix it is to either have the motherboard replaced or update the emmc firmware. I might be wrong though but the symptoms and the logs do suggest it could be the emmc brickbug. (Unless your kernel has been patched which fixes this bug)
Click to expand...
Click to collapse
ok, so I reflashed the Kernel I mentioned higher, it passed in Odin, however, when I rebooted, all was the exact same. trying to reflash the most recent publication of the 4.2.2 Samsung ROM, we'll see... edit: just finished and it's a big "O fat failed... "I'll repost the results, thanks a bunch, oh well, if it's dead, it's dead time to blow some money and get another tablet, was thinking of the Chuwi hi13, should do well for me, got very little requirement for power, just want a clear clean large screen to be able to read, check the news and play some Klondike solitaire.
:crying:

diesel13 said:
ok, so I reflashed the Kernel I mentioned higher, it passed in Odin, however, when I rebooted, all was the exact same. trying to reflash the most recent publication of the 4.2.2 Samsung ROM, we'll see... edit: just finished and it's a big "O fat failed... "I'll repost the results, thanks a bunch, oh well, if it's dead, it's dead time to blow some money and get another tablet, was thinking of the Chuwi hi13, should do well for me, got very little requirement for power, just want a clear clean large screen to be able to read, check the news and play some Klondike solitaire.
:crying:
Click to expand...
Click to collapse
Maybe all hope is not lost yet. Have you tried reflashing twrp? :fingers-crossed:

Lightracer said:
Maybe all hope is not lost yet. Have you tried reflashing twrp? :fingers-crossed:
Click to expand...
Click to collapse
nope, didn't even think of that, will try it right now, let you know how it goes
ok ,so here we are...
downloaded the latestTWRP, CMW and Philz(pretty old)
twrp-3.1.0-0-p5110.img
CWM Recovery v6.0.3.6.tar
philz_touch_6.57.8-p5110.tar.md5
Click to expand...
Click to collapse
tried all 3 via ADB and Odin
via ADB, transfer does not progress
via Odin, success but still reboots in TWRP 3.0.0.0

diesel13 said:
nope, didn't even think of that, will try it right now, let you know how it goes
ok ,so here we are...
downloaded the latestTWRP, CMW and Philz(pretty old)
tried all 3 via ADB and Odin
via ADB, transfer does not progress
via Odin, success but still reboots in TWRP 3.0.0.0
Click to expand...
Click to collapse
Well I'm out of ideas, time to get a new tablet I guess ✌

Lightracer said:
Well I'm out of ideas, time to get a new tablet I guess
Click to expand...
Click to collapse
Well I do appreciate your input and am yuppin' a big Kudos and Thank You, Life is Life, we'll all go at some points, the tablets just get there first
Thanks Lightracer :highfive: