yashsingh1/xdaforums huggingface dataset:
[Android] ErickNoz:
UPDATED NAND FIX 2015

First of all I saw Some people saying Nand Write Fail And No Fix

Can Do it....!​

Cygwin For Windows

NotePad++

7Zip

AABox

Odiin

your brick (i mean phone)

Stock Firmware or any TAR with 4file better

USB Drivers and all SAmsung Drivers

Getting Ready

Please Dont use Aabox Vit Packet 1 or SupperSS Nand if you are doing this Method

Cygwin - use as Linux Shell​

Cygwin For windows

NotePad++ - for Editing All Codes​

Note Pad ++ Download

7 Zip for Open zip​

And Extracting Tar Md 5 and zips download here

AABOx for Verify and Sum Coding​

AA-box is need for coding rom for tar and its download link is not available at because of Under Maintenance and update. Its Ok i will guide you the coding manually

Odin​

We Need Odin .85 or 65 if you have " AAbox 2 " its solved. odin3 1.85 download

UPDATING WAIT...!

//----------------------------------Below is old Post 1---------------------------------------------//​

nand write start fail on odin soluction

Tired of flashing with odin and fail....

What you need

Rom or firmware tar

Cygwin for windows

7zip

Odin3 1.3v

Device correct pit file

A good brain

Extract all files on tar to cywin home folder

Open cygwin and cd home

Then tar your files in this order

1.slb or blm or your bin file

2.boot

3. Modem

4. Cache

5. System

6.recovery

7. Others

Tar command

tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar

And enter

Wait to finish

Now odin tick repartition update bootloader reset and autostart and pit

Pda your repair tar

Then flash it

Enjoy...

Note- Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..

And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.

Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..

Press thanks if you done.

Mod Edit:- : Links Removed & Thread Closed.
[Android] eniac0:
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.

I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?

I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
[Android] ErickNoz:
Updated

Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..

And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.

Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
[Android] eniac0:
wow, i would not have figured that out, but it certainly explains why that error has started appearing so often in different threads and sites now.

I had stopped trying various ways to flash my phone to avoid doing something stupid but i think I'll give your method a try now that i understand where it comes from. I am not super eager to mess with pit files but i believe to have found the right one so I'll give it a try.

Thx.
[Android] ErickNoz:
You are welcm... keep in mind friend don't us bad or different pit files u will be bricked.

Always keep in mind to have a breathing phone... if its dead .....you will have to use it as a paperweight.

So use correct pit

Use correct sbl and other bin files to flash

Ur bootloader or download mode is for wake up from sleep.. not done if dead.

If you press thanks button that my secret
[Android] msl:
Hi

Thank you for your possible solution. Unfortunately, I have never used Cygwin before, and I am not sure how to follow your steps. Is there any chance you could write the procedure in a little more detail?

I have been ROM Flashing for a while, but I have not tried this method for solving the NAND write problem. I have been trying to deal with this, since the KitKat release came out, but now, becaue I cannot upgrade, some of my apps have stopped working.

Thank you!
[Android] ErickNoz:
Can I know you device history before nand write
[Android] msl:
I have a Samsung Galaxy N8000 bought in China about 2 years ago.

When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.

However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.

Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.

I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for :)

Here is the Odin Log

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> SingleDownload.

<ID:0/003> sboot.bin

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL!

<ID:0/003>

<ID:0/003> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Android] ErickNoz:
Woooow Nand write

Wooow this is the correct nand write fail caused by md5 or tar prob.

Only Use odin1.87 or 1.3 version

And untar ur md5 or tar firmware

Then tar back with the given order by me above 1st post.

It will be ok. Realy...
[Android] msl:
Hi

But, if it was a problem with the md5 or tar file, wouldn't everyone else also have the same problem? This md5 is from sammobile, it should be an official Samsung release, and I am sure thousands of others are using it.

Secondly,

How do I untar the file exactly, I have never done this before, I am not familiar with the software you describe in the original post.

Do you know where I can find instructions on doing this, or would you have time to write a very quick instruction ?

It sounds like I have to take the file apart and put it back together again.
[Android] ErickNoz:
Update

Use Cygwin for tar and untar

Install cygwin first google it

Or

Use Tar box by AFx
[Android] namhsif:
Hi, I downloaded a ROM from sammobile and I don't have all those files.

My files are:

boot.bin

cache.img

factoryfs.img

hidden.img

modem.bin

param.lfs

sbl.bin

zImage

Should I do like you said until the 4 (because I have the first 4 files from the tar command) and then write the others or I need to find one ROM that have system and recovery?

I hope my pit files is right too.

And another question:

I don't understand everything from this:

1- Tick repartition

2- Update bootloader

3- Click reset

4- tick Auto reboot

5- Choose the downloaded pit file

6- Choose the created tar into PDA

Is it right? If yes, could you explain the "update bootloader" ?

Thanks
[Android] Anand.prashar:
[Query] to same problem

Hi There,

I have been struggling with same problem.. NAND WRITE FAIL

I had initiated a thread too in this context.

Want to know, if your attempt on device solved the problem ?

Thanks
[Android] eniac0:
Hi, ultimately no, i was able to depackage the rom but not fix it. It didn't have all the same components mentionned by erick and i wasn't sure how to compensate for the missing ones, were they mandatory, missing because obsolete, i don't know.

It gave me hope but it ended nowhere. Also all experts i contacted were not able to fix it and samsung won't even touch it because it was rooted.

I am thinking about putting a bounty on xda here to hire some help.
[Android] tajinder571:
didnt fix n7100

Hi I couldnt find the boot.bin on extracrting 3 different md5 files. However, i did the steps as told but didnt work i make the repair.tar with cygwin .
[Android] mooro99:
vmware fusion for macos

Had the same issue using a virtual machine via vmware fusion for macosx. I switched for parallel desktop then flashed the last stock firmware and right pit file (repartition thicked).

At first boot possible boot loop on Samsung logo but resolved by wipe data / factory reset with stock cwm.
[Android] eniac0:
My phone's issue ended up being the eMMC chip busted. Had the phone repaired for about 150$, which i thought was cheaper than a new Note 2.
[Android] Svenarchy:
Solution

I had the same problem until 5 minutes ago and you can solve it by:

Going to

-Developer options-

Allow "USB debugging"

Uncheck the "Veify apps via USB" box

Let me know if it works

Kind regards

SM-N910C

4.4.4

Odin3 v3.07

CF-Auto-Root-trelte-treltexx-smn910c.tar.md5
[Android] barberboy420:
I can't acces developers options because my device is soft bricked. I downloaded the jelly bean firmware because that what firmware the device was on (I believe) a year ago when I rooted the device for a co worker the link is here http://galaxynote3root.com/galaxy-note-3-stock-firmware/ any help would be marvelous so I can unbrick this darn phone TIA
[Android] jabbarh123:
I dont understand these instructions they are too advanced. The title of this post looks very promising as I am basically in an emergency to get my phone fix due to the NAND write fail issue but the OP does not state any helpful information including download links, where to get the files from, which files they are, what to do rather than one word instructions :S - We come on here expecting to get help (and to help others) so please somebody reply to me on what I have to do to get this fixed. (ask me for details if you are kind enough to help)

Thank you.
[Android] eniac0:
i am not sure your expectations of what xda developers offers are correct.

as it names implies, xda dev is first and foremost a dev to dev "chat line" to fix issues or otherwise discuss amongst each other about mobile development.

this isn't a help line for users to demand better explanations or be walked through a problem. Every case is specific and it is next to impossible to write instructions that will work for everybody.

if you wish to be helped in regards to what has already been posted in this thread, start by describing what you have done so far, in details, so that other may even be able to understand your situation.

Respectfully yours,
[Android] jabbarh123:
Okay well I have a Galaxy Note 2 which was the SHV-E250S model. I flashed the GT-N7105 firmware however the ROM was corrupt. I tried to flash a Lollipop ROM for N7105 and I got stuck at the boot screen. Now when trying to flash a UK firmware (downloaded sammobile) it says NAND write FAIL and it also fails when I try to flash a .PIT file.

Help please?
[Android] eniac0:
in my personal case, my phone turned out to be physically broken, so no amount of tar packaging or troubleshooting could fix it. my eMMC chip was busted, apparently Note 2 phones are notorious for it.

The NAND write error i was getting from odin was related to Odin not being able to initiate the flash procedure because the chip was broken.

At this point, I think the safest option in your case is to put it in the hands of pros. If the explanations in this thread are too technical for you, chances are you will end up bricking your phone for good. (without disrespect intended)

This site offers to repair the phone, they can even fix the eMMC chip if you have the same probleme i did. It's pricey, but not as expensive as a new phone.

mobiletechvideos.mybigcommerce.com

if you cannot pay that price, then by all means keep trying but understand that a lot of technical reading will be required from you along with a lot of trial and error and people from xda will not likely help you in the way you want if you're unable to get wet with the gory reading.
[Android] jabbarh123:
Don't worry, I've fixed it :) bye.
[Android] nubpro:
how was it fixed?

I have the same identical issue of yours.
[Android] jabbarh123:
what phone have you got
[Android] nubpro:
GT-N7100
[Android] jabbarh123:
what i did was get a PIT file and a firmware .md5 file and flashed both of them at the same time within odin, im sorry i have no links or downloads, i have the files on my pc at home, i can give you them when i get home if you'd like but i suggest in the mean time you have a look for it, google search for the pit file and firmware (firmware can be obtained from sammobile.com)
[Android] nubpro:
i need 32 GB international variant.
[Android] mojo_jodroid:
can anyone help me?

i've got a galaxy s6 SM-G920I and i do not know where to get my device specific PIT file.

i am still getting the NAND WRITE START fail.

i've been at this for days.. someone please help!!
[Android] Monfil:
Are you fixed it?
[Android] mojo_jodroid:
Yes, not sure if I just got lucky or my method actually works but here's how;

-Downloaded stock firmware and extracted files

-removed .md5 off the end and extracted it again

-inside should be boot.img cache.img recovery.img system.img etc.

-used Unified Android Toolkit to create individual flashable files of each file

-flashed them in the order they came

-everything passed

Again, not sure if it will work for anyone else but good luck and I hope this helps!
[Android] XJShinoda:
How do you create flashable files? Is there any tutorial that i can find? Flashable files is tar file right?
[Android] Villani10:
I'm having the same problem too...
[Android] alkhkifa:
Same issue and really not sure how to follow these steps... i found a lot with same problem but no one knows how to fix... will appreciate detailed easy to understand explanation.. for idiots to fix their mobiles.. thanks
[Android] bungrudi:
Can OP or someone provide a link to correct PIT file for my 910C 32GB?
[Android] t0m4s_g1l:
I did all the steps above but i did not worked for my note 4 SM-N910H i did also some recomendations like remove sim cards and sd card but i have the repair.tar but keep in the same message all the time i tried with odin 1.3,1.85,3.07,3.09 and 3.10.7 with some odins like 1.3 and 3.07 it dosen`t show the message nand write start fail, but it never pass the Get pit for mapping and i tried another pit file olso but i have no luck. thanks for the help anyway. sorry my english
[Android] tornado92:
Is your download mode showing your phones model number??
[Android] t0m4s_g1l:
Yes, look how it shows in the phone

[IMG="Note 4 SM-N910H"]http://i881.photobucket.com/albums/ac19/Astro1992/20130827_235402_zpsouz6znoj.jpg[/IMG]
[Android] tornado92:
Can u enter reovery.mode?? does it show any error??
[Android] t0m4s_g1l:
No, i can enter recovery mode, also i can turn on the phone in android but if the screen turns off i cant turn in on never until i remove batery again. android is corrupt or i dont know... sorry my english

here is a photo of the phone in recovery mode

[IMG="Note SM-N910H in recovery mode"]http://i881.photobucket.com/albums/ac19/Astro1992/IMG_0418_zpsvpemqvdy.jpg[/IMG]
[Android] tornado92:
Try to factory reset in recovery.. does it show any error
[Android] georgeus4:
same problem with my edge g925F please help

here are my problem details:

tryed to root my samsung Edge G925F which failed and got stucked with logo and in the left corner with an red message: "Recovery Is Not Seandroid Enforcing"

- Recovery option which should come when i hold 3 buttons Vol up+power+hold button) NOT WORKING

- Download mode works. and when i trying to reinstall new firmware comming up following message in Odin:

<OSM> Enter CS for MD5..

<OSM> Binary Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1100)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> sboot.bin

<ID:0/004> NAND Write Start!!

<ID:0/004> FAIL!

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

I allready did tried 2 firmware

Please explain to me as you explain to beginers what are the steps to start my phone again.

thank you in advance
[Android] tornado92:
Try 5.1.1 firmware
[Android] georgeus4:
allready tried. Not working
[Android] Mina Elsaued:
plz help

its hard for me to understand how did you do it since iam new to cygwin so my note 4 n910c is tuck on note 4 logo the first logo that appears when starting the phone it happened when the phone was on 5.1.1 lollipop and by mistake i flashed an auto root from chainfire it led to a bootlop i have tried to flash every thing srocks-custom it always says NADA write fall i tried to install custom roms with custom recovery but it sad failed so plz help :crying:
[Android] xbxraka11:
Nand write solevd!!!

[MENTION=5133885]ErickNoz[/MENTION] I used your solution and experimented with it with my own knowledge of flashing. After a few hours of messing about I finally fixed my Samsung S6. I was trying to flash my firmware back to 5.0.2 but accidently the whole Operating System.

Your solution said to reorder the img files in the TAR so thats what I did but it still showed the Failure. After few ideas I thought why not extract the files from the TAR file and TAR them individually to see which file was causing me the FAILURE. I used the cygwin terminal to this to each file:

tar -c "yourfile.img/bin" >> "renametowhatever".tar (dont put speechmarks in the names, this is an example)

After this I did the following (step by step precedure for you guys):

1. Opened Odin3 3.10.6 (you could try the newer ones).

2. Plug your phone to your USB and in to the PC.

3. Click "AP" and browse the TAR file which contains a file from the original Firmware TAR file (like recovery.img in a TAR file).

4. Click on "Option", tick the check boxes for "Auto Reboot" and "F. Reset Time". Make sure the "Re-partition" is unchecked.

5. Click "Start".

Make a list in Microsoft WORD or NotePad with the status of each flash (Pass or Fail). In my case sboot.bin and cm.bin FAILED. But when I rebooted my S6... it worked!!!

The only thing that I find weird is that on my About device in the Settings- the Baseband version is showing as Unknown. I'll try fixing this problem and maybe get back on the results.

PM me if you have any problem. :good:

----------------------------------------------------------Update------------------------------------------------------

Ok guys, i think i know now why odin causes NAND Failure and thats because the firmware I was flashing was not the right version. My phone was unlocked so therefore I needed to flash the firmware which had XEU in the name. XEU is for unlocked phones. All this time I was downloading any S6 5.1.1 firmware just because of the name. But upon furthur research I found out that most people don't download the exact firmware their phones need.

Let me break it down. On Sammobile website, you filter down to the firmware you need. Lets say Galaxy S6 SM-G920F and you want a firmware that corresponds to your phones compatibility. If it is factory locked to a certain brand then choose the firmware that has the exact name in its title.

If your phone is unlocked then download the XEU version.

-> H3G for 3

-> VIR for virgin media

->O2U for O2

-> EVR for EE

-> VOD for vodaphone

Again if you need help or any info PM me. Have a nice day.
[Android] rabbit19:
Hi. I have GT-N7000, stuck with "Firmware upgrade encountered and issue". Tried Kies but the phone can't be recognized, as well with Odin, NAND Write failed. Uninstalled and reinstalled USB Drivers and Kies, started program sa As Admin, But still can't be recognized. Almost tried all tutorials I found but this. I downloaded the cygwin etc, but can't follow the instructions. Any easier method? Please...

TIA
[Android] xbxraka11:
Follow this:

-> Go to your phones recovery mode (hold Volume up + Home button + Power button for few seconds).

-> Wipe cache and then restore to factory settings.

-> Reboot your phone and press and hold (hold Volume down + Home button + Power button for few seconds). You might get the download mode again with these but you will lose all your stuff.

-> Use odin again.

If the Nand write shows failure then that means you are not flashing the right Firmware. Trust me it happened to me. My phone was an unlocked model of S6 but I kept on downloading the Firmwares for the other networks like 3 or O2. I downloaded the XEU version of the 5.1.1 lolipop firmware and flashed it. Guess what happened... it WORKED!!! :D

The method escribed in this forum won't be neccessary. The change in orders don't work properly anyway because the NAND fail occurs on the bin files like sboot.bin or cm.bin.

All of the proper procedure comes from finding the right Firmware mate. Give it a try.
[Android] rabbit19:
no recovery m0de

hi. tnx. i forgot to mention that it doesn't go to recovery mode, download mode only. i downloaded the rom sammobile. it's a local version, but i will try to download another r0m from different network. i just bought it online, it could be that it came from another work.
[Android] xbxraka11:
Custom recovery

[MENTION=487663]rabbit19[/MENTION] Don't worry, you will need to install a custom recovery to enable recovery mode.

-Download TWRP for you phone,

-go to download mode on your phone,

-open odin on your pc,

-click "CP" and find the TWRP file,

-Install it,

-reboot your phone and try going to recovery.
[Android] kvino55:
Samsung galaxy note 2 N7100 indian version 16GB. Nand write start fail issue

I was returned with this error when i tried with prerooted rom from xda.

$ cd home tar -c sboot.bin boot.img modem.bin cache.img system.img recovery.img tz.img hidden.img >> repair.tar

-bash: cd: home: No such file or directory

I extracted the main tar file, and copied the individual files into the cygwin /home directory.

Along with the Re-tared zip file in the same directory.

Please explain the procedure bit more clearly.

Excuse my ignorance, Thank You.
[Android] kvino55:
please explain a bit more.

Returned with no such dirctory error.
[Android] rabbit19:
TWRP Version

HI. Sorry, I'm kinda confused on what TWRP version I should use. I have a Philippine local unit.
[Android] douglasfalves:
You are the best man!!! I tried a lot to work my bricked phone. Just you tip worked!!! Thanks a lot!!!
[Android] aram980:
hi

type like this, its succeed with me

for sygwin :

$ cd c:/cygwin/home

for sygwin64 :

$ cd c:/cygwin64/home

$ tar -c sboot.bin boot.img modem.bin cache.img system.img recovery.img tz.img hidden.img >> repair.tar

with all the best