Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,805,635 Members 38,712 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Can not write to gnex NAND at all.

Tip us?
 
ron975
Old
(Last edited by ron975; 5th May 2014 at 11:06 PM.)
#1  
Junior Member - OP
Thanks Meter 0
Posts: 3
Join Date: Sep 2012
Default [Q] Can not write to gnex NAND at all.

I'm trying to wipe and restore an unlocked maguro Galaxy Nexus. No custom recovery, no root, stock ROM. But I can't wipe it at all. Recovery Mode factory reset doesn't work, it just reboots, and boots up as if it wasn't wiped at all. fastboot doesn't work, it gives the error 'remote: Wipe Failed'
Code:
fastboot -w
erasing 'userdata'...
OKAY [  0.007s]
formatting 'userdata' partition...
Creating filesystem with parameters:
    Size: 15961423872
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 3896832
    Block groups: 119
    Reserved block group size: 951
Created filesystem with 11/974848 inodes and 103467/3896832 blocks
sending 'userdata' (137971 KB)...
writing 'userdata'...
FAILED (remote: Write Fail)
finished. total time: 264.655s
Even ODIN won't wipe, it fails with and without NAND Erase All. Not even ODIN can wipe the thing.

Without erasing NAND
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!! 
<ID:0/003> bootloader.img
<ID:0/003> radio.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
Erasing NAND
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> odin.takju.jwr66y.4.3.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> Erase...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm starting to think that it's a hardware problem with the NAND itself. I've been looking all over the web and I can't find anyone who has the same problems as I. Where should I go from here?
 
mrgnex
Old
#2  
mrgnex's Avatar
Senior Member
Thanks Meter 287
Posts: 976
Join Date: Jan 2013
Location: Vlaardingen
Lock your bootloader if its still unlocked after doing that your nand is fried.

Sent from my Nexus 10 using XDA Free mobile app
SΛMSUNG/Google Galaxy Nexus
ROM: Vanir Nightly
Kernel: A.S.K.P. Patty Remix

SΛMSUNG/Google Nexus 10
ROM: Vanir Nightly
Kernel: Stock Vanir
 
blabdude
Old
#3  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: Apr 2014
Quote:
Originally Posted by mrgnex View Post
Lock your bootloader if its still unlocked after doing that your nand is fried.

Sent from my Nexus 10 using XDA Free mobile app
Once its unlocked and it reboots, it relocks
 
mrgnex
Old
#4  
mrgnex's Avatar
Senior Member
Thanks Meter 287
Posts: 976
Join Date: Jan 2013
Location: Vlaardingen
Quote:
Originally Posted by blabdude View Post
Once its unlocked and it reboots, it relocks
Your nand has been fried. Sucks man..

Sent from my Galaxy Nexus using XDA Free mobile app
SΛMSUNG/Google Galaxy Nexus
ROM: Vanir Nightly
Kernel: A.S.K.P. Patty Remix

SΛMSUNG/Google Nexus 10
ROM: Vanir Nightly
Kernel: Stock Vanir
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes