Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 46

Thread: Error odin to 4.4.2 (NAND Write Start ... fail) and can not use recovery mode.

  1. #11
    Junior Member
    Join Date
    Jun 2014
    Posts
    10
    Quote Originally Posted by diego67ratten [ Login above or register to see download links. ]
    hello, which is the recovery file you installed it?: Confused:
    Hello. I got the Stock Recovery Partition File from [ Login above or register to see download links. ]. It is a rooting method using a custom recovery file (ClockWorkMod) but they also have a link to the stock file.

  2. #12
    Junior Member
    Join Date
    Jun 2014
    Posts
    10
    Quote Originally Posted by diego67ratten [ Login above or register to see download links. ]
    hello, which is the recovery file you installed it?: Confused:
    Hello Diego.

    I downloaded the GT-N8000 Stock Recovery File from [ Login above or register to see download links. ], but I recall there is a pinned thread with the different CWM recovery files and also the stock recovery files in the Samsung Galaxy Note 10.1 sub-forum index.

    I hope it helps.
    Last edited by J4m4cuc0; 24-06-2014 at 10:57. Reason: Syntax & added info.

  3. #13
    Junior Member
    Join Date
    Mar 2013
    Posts
    7
    Quote Originally Posted by J4m4cuc0 [ Login above or register to see download links. ]
    Hello Diego.

    I downloaded the GT-N8000 Stock Recovery File from [ Login above or register to see download links. ], but I recall there is a pinned thread with the different CWM recovery files and also the stock recovery files in the Samsung Galaxy Note 10.1 sub-forum index.

    I hope it helps.

    thanks for replying , but does not work , still I get the problem:

    <ID:0/004> Added!!
    <OSM> Enter CS for MD5..
    <OSM> Check MD5.. Do not unplug the cable..
    <OSM> Please wait..
    <OSM> N8000-Stock-Recovery.tar.md5 is valid.
    <OSM> Checking MD5 finished Sucessfully..
    <OSM> Leave CS..
    <ID:0/004> Odin v.3 engine (ID:4)..
    <ID:0/004> File analysis..
    <ID:0/004> SetupConnection..
    <ID:0/004> Initialzation..
    <ID:0/004> Get PIT for mapping..
    <ID:0/004> Firmware update start..
    <ID:0/004> recovery.img
    <ID:0/004> NAND Write Start!!
    <ID:0/004>
    <ID:0/004> Complete(Write) operation failed.
    <ID:0/004> Added!!
    <OSM> All threads completed. (succeed 0 / failed 1)

    [ Login above or register to see download links. ]



    I'll be looking for the solution online xD

  4. #14
    Junior Member
    Join Date
    Jun 2014
    Posts
    10
    Quote Originally Posted by diego67ratten [ Login above or register to see download links. ]
    thanks for replying , but does not work , still I get the problem:

    <ID:0/004> Added!!
    <OSM> Enter CS for MD5..
    <OSM> Check MD5.. Do not unplug the cable..
    <OSM> Please wait..
    <OSM> N8000-Stock-Recovery.tar.md5 is valid.
    <OSM> Checking MD5 finished Sucessfully..
    <OSM> Leave CS..
    <ID:0/004> Odin v.3 engine (ID:4)..
    <ID:0/004> File analysis..
    <ID:0/004> SetupConnection..
    <ID:0/004> Initialzation..
    <ID:0/004> Get PIT for mapping..
    <ID:0/004> Firmware update start..
    <ID:0/004> recovery.img
    <ID:0/004> NAND Write Start!!
    <ID:0/004>
    <ID:0/004> Complete(Write) operation failed.
    <ID:0/004> Added!!
    <OSM> All threads completed. (succeed 0 / failed 1)

    [ Login above or register to see download links. ]



    I'll be looking for the solution online xD
    Too bad.
    Did you mess with the PIT file..? I think I didn't go that far...

  5. #15
    Junior Member
    Join Date
    Oct 2011
    Posts
    1
    did you get the solution??

  6. #16
    Junior Member
    Join Date
    Jan 2013
    Posts
    14
    i have the same situation as diego67ratten. is NAND erase all an option? i tried every other solution i know of(Flashing pit(alone or with firmware), flashing kernels, flashing bootloaders, flashing roms(one file or multi-part), removing batteries, flashing the latest kitkat rom (UDNE4, UDNE5, UDNE6),flashing recovery, reinstalling drivers, using different cables, using different computers, using different ports, using heimdall, modding roms(removing sboot.bin and tz.img)), but all to waste. in download mode, i can still see my model number, so i don't think it has half sds. now NAND erase all is the only think that i didn't try yet (except those which weren't included in the large parenthesis).

    i want to make send the device to samsung the last resort possible, so i want to be out of options first before i hand it over.

    Sorry if i shouldn't have posted this as a separate thread, but i am new to using forums, and i really don't know whether it is okay or no

    Thanks in advance
    Last edited by yousef_badr23; 10-08-2014 at 21:12.

  7. #17
    Junior Member
    Join Date
    Mar 2013
    Posts
    7
    for all, I say that I have found no solution online.
    * now will try to install a custom android ...

    send to my n8000 samsung technical center, I got the solution to replace the motherboard, very expensive .....

  8. #18
    Junior Member
    Join Date
    Aug 2014
    Posts
    10
    i am having the same problem, i have been trying to fix it for several days now.

    the good SAMMobile moderators have given me some great help, even though it ended up fixing nothing, if it can help, you can read my thread here.
    [ Login above or register to see download links. ]

    perhaps you won't be able to access it, it requires premium access, not sure why.

    but perhaps there will be something in it that will help you.

  9. #19
    Junior Member
    Join Date
    Aug 2014
    Posts
    10
    I found a thread on xda developers that could be helpful. This guy indicate the NAND write start error is not caused by a dusty hardware or chewed up cable and such but rather a change on international standards regarding TAR packaging.

    I haven't given it a try myself because I lend my phone to pro for repair and i found this afterward. but for those with still the NAND Write Start error, this is worth a try, it is not extremele difficult to do the fix but it will require a PIT file, and so, you need to make sure you have the right one to avoid bricking your phone for good.

    [ Login above or register to see download links. ]

  10. #20
    Junior Member
    Join Date
    Sep 2014
    Posts
    1
    I installed a wrong firmware on my SHW-M440S so I got a Soft Bricked on it. I need a pit file for that model but I don't find it. Could anyone help me? I'm from Venezuela and I love that Galaxy S3.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •