Database Info

E:cant mount SD, cant write system.img

Hi,
my NSdoesnt boot and I cant flash another ROM because my NS cant mount SD anymore, so I tryed to restore it back to stock and flash the .imgs with fastboot. Boot.img, recovery.img, userdata.img, without problems, but the system.img gives me the message "write failed" or something. Tryed it multiple times with the Gingerbread system.img, and ICS system.img, same problem.
I can boot into recovery, but the phone doesnt recognize the SD and also the system partition.
Any solutions?
Sorry for my english.

What recovery you using?
Sent from my Nexus S using xda app-developers app

Tried 2 different CMW Recoveries, it's not a recovery problem. My System and SD storage is corrupt or something, I think.

It can't be all that corrupt as you are able to install boot loader and recovery. Try and adb sideload CyanogenMod 10.1. Once you got a booting phone, things tend to play nicely.
Sent from my Nexus S using xda app-developers app

Just tried the adb sideload method.
"Installing update..." for 5 Minutes now. I think it cant write on /system.
I've also tried to erase /system partition via fastboot it gives me also the "failed" message.

system.img write fail error
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...

I've had a similar experience when installing stock ROMs after installing cwm and cm 10. Can you guys not even install cm10?
Sent from my Nexus S using xda app-developers app

Deus Tempestas said:
I have the same problem, can't write a system img to the phone
FASTBOOT STATUS - FAILWrite Fail
I have TWRP but it would not do anything to the system partition.
I tried to flash the stock rom
soju-jzo54k
I ran the flash-all.bat
this is the output
sending 'bootloader' (1536 KB)...
OKAY [ 0.215s]
writing 'bootloader'...
OKAY [ 0.385s]
finished. total time: 0.601s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.601s]
writing 'radio'...
OKAY [ 1.919s]
finished. total time: 3.520s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 33304BC024EC00EC
--------------------------------------------
checking product...
OKAY [ -0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.542s]
writing 'boot'...
OKAY [ 0.587s]
sending 'recovery' (4308 KB)...
OKAY [ 0.567s]
writing 'recovery'...
OKAY [ 0.638s]
sending 'system' (337443 KB)...
OKAY [ 43.476s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 45.956s
Press any key to exit...
Click to expand...
Click to collapse
Same problem here! Did u find solution?

[Q] Nexus 5 killed by EMP?

So... some time ago I was chatting with the girlfriend across town with my brand new N5 (unplugged). in the middle of the chat she said "Wow! That was a BIG bolt of ligtening".. as soon as I read that, my screen began to vibrate... then freeze. That was it for me poor N5. Dead as a doornail.... when i tried to reflash i get
~/src/hammerhead-ktu84p » ./flash-all.sh
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.437s
rebooting into bootloader...
OKAY [ 0.135s]
finished. total time: 0.135s
< waiting for device >
sending 'radio' (45409 KB)...
OKAY [ 1.588s]
writing 'radio'...
OKAY [ 3.115s]
finished. total time: 4.702s
rebooting into bootloader...
OKAY [ 0.130s]
finished. total time: 0.130s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.16
Serial Number........: 048dc649437f5df5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8700 KB)...
OKAY [ 0.490s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 44.872s
------------------------------------------------------------
~/src/hammerhead-ktu84p »
so, I have two questions...
1) i tried to get an RMA for this, but ASUS said I can only get an RMA from theor site, but their site has no way to select N5 as the equipment needed for repair... but that is really a moot point, as I am in Argetina, and getting this Nexus to/from anywhere has about a 1% chance of success.... and by now the warrenty is probably expired (i have no reciept or anything... was brought down here 'discretely' by a friend)
2) I assume my flash rom ws fried by some bizarre EMP from across town... but in any case, would a skilled mobile techy be able to repair this here? i guess replace the flash rom? Is that a completely stupid idea?
Thanks

i tried to get an RMA for this, but ASUS said....
this is an LG phone
contact google they are giving free replacements. you should at least know the manufacturer for your phone
its on the box afterall

ntisithoj said:
So... some time ago I was chatting with the girlfriend across town with my brand new N5 (unplugged). in the middle of the chat she said "Wow! That was a BIG bolt of ligtening".. as soon as I read that, my screen began to vibrate... then freeze. That was it for me poor N5. Dead as a doornail.... when i tried to reflash i get
~/src/hammerhead-ktu84p » ./flash-all.sh
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.437s
rebooting into bootloader...
OKAY [ 0.135s]
finished. total time: 0.135s
< waiting for device >
sending 'radio' (45409 KB)...
OKAY [ 1.588s]
writing 'radio'...
OKAY [ 3.115s]
finished. total time: 4.702s
rebooting into bootloader...
OKAY [ 0.130s]
finished. total time: 0.130s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.16
Serial Number........: 048dc649437f5df5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8700 KB)...
OKAY [ 0.490s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 44.872s
------------------------------------------------------------
~/src/hammerhead-ktu84p »
so, I have two questions...
1) i tried to get an RMA for this, but ASUS said I can only get an RMA from theor site, but their site has no way to select N5 as the equipment needed for repair... but that is really a moot point, as I am in Argetina, and getting this Nexus to/from anywhere has about a 1% chance of success.... and by now the warrenty is probably expired (i have no reciept or anything... was brought down here 'discretely' by a friend)
2) I assume my flash rom ws fried by some bizarre EMP from across town... but in any case, would a skilled mobile techy be able to repair this here? i guess replace the flash rom? Is that a completely stupid idea?
Thanks
Click to expand...
Click to collapse
1. For an EMP to kill your device it would of had to been in your vicinity. It doesn't hit a cross a town, the whole town would of been down. And if it were a real EMP it would of killed your GFs phone immediately.
2. Why are you contacting Asus?
Do you not see the LG logo on the back of the phone or bothered to at least google it?
3. Sound like you have a bad sd contact google to try and RMA the device

Lol you contacted Asus? Wtf!

if you contact Asus, they will replace your N5 with a N7.

jayRokk said:
1. For an EMP to kill your device it would of had to been in your vicinity. It doesn't hit a cross a town, the whole town would of been down. And if it were a real EMP it would of killed your GFs phone immediately.
2. Why are you contacting Asus?
Do you not see the LG logo on the back of the phone or bothered to at least google it?
3. Sound like you have a bad sd contact google to try and RMA the device
Click to expand...
Click to collapse
she was on her computer, i was on my phone... but yes, probably not EMP, but it was an extremely rare coincidence.
I never had the box to this phone, hbut holy crap! you are right! it says "LG" on the back. I can not remember the details as to how i 'learned' it was an ASUS (as it was months), but really embaressing that I overlooked that. So thanks

repaired bootloop

i repaired bootloop sucessfull but right now i want flash latest pack rom
see pls if theres some wrong
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.499s
rebooting into bootloader...
OKAY [ 0.108s]
finished. total time: 0.109s
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.596s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.701s
rebooting into bootloader...
OKAY [ 0.062s]
finished. total time: 0.064s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 04deb0810a65d5be
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.099s]
sending 'boot' (8852 KB)...
OKAY [ 0.499s]
writing 'boot'...
FAILED (remote: not supported in locked device)
finished. total time: 1.302s
Press any key to exit...

Looks like your bootloader is still locked

even when i unlock it suudenly after restart bootloader locked why

abumaha said:
even when i unlock it suudenly after restart bootloader locked why
Click to expand...
Click to collapse
that looks like bad emmc, use download mode instead to try

so i think
how download mode ?

abumaha said:
so i think
how download mode ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

Deep trouble with my N5 (after rooting) and cannot flash factory image

Hi there,
First, sorry for my english.
I'm not a newbie in rooting, but it's the first time i've got a N5. So, after getting my N5, the phone update to 4.4.4, after to 5.0.1 and after to 5.1.1.
After that, i've flash CWM, but i don't know why but this method give me many error (like the /sdcard cannot be mounted, etc) and i'm in a bootloop. So i've install TWRP, and i've see something weird, it's like all the folder /system, /data, etc cannot be mount because is not there.
So, i'Ve decide to download the factory image 5.1.1 (LMY48B) of the N5, and execute the "flash-all.bat", but it's stock to "writing 'system' ...
sending 'bootloader' (3119 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.719s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
sending 'radio' (45425 KB)...
OKAY [ 1.547s]
writing 'radio'...
OKAY [ 3.235s]
finished. total time: 4.797s
rebooting into bootloader...
FAILED (status read failed (Too many links))
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: (sorry it's personal)
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8980 KB)...
OKAY [ 0.501s]
writing 'boot'...
OKAY [ 0.766s]
sending 'recovery' (9696 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 0.798s]
sending 'system' (1021744 KB)...
OKAY [ 32.562s]
writing 'system'...
Click to expand...
Click to collapse
What's the problem????

Try flashing the individual files separately
Sent from my Nexus 5 using Tapatalk

Soft brick help!!

I've had my nexus 5 for awhile now and decided that I should try to root it. So I followed a guide and youtube and it worked. I then followed a guide to install the android M developer preview, just to check out what had changed. From there I decided to install Cyanogenmod 12.1 . So I was looking at this guide when all of a sudden i noticed my root was gone for some reason. (im new to all this, not sure if that was supposed to happen). So then I followed the same rooting steps I used for the first youtube guide I watched. everything seemed to go fine until i realized that i was in a boot loop. I then decided to go ahead and install Cyanogenmod 12.1 anyway. It worked and my phone was fine. Until i woke up this morning and saw that it was in a boot loop again, but now I can't even get into my custom recovery (TWRP). I dowloaded this program to completely return my phone to stock but every time it tries to flash something to my phone, it gets this "flash write failure" message. Now I'm really lost and do not know what to do. I really rather not buy a new phone.
If anyone can help it would be really appreciated!!! If you do, I will need you to assume I do not know anything, as I'm not very familiar with everything.

Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk

ldubs said:
Can you get into fastboot mode? If so from there flash the factory images.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This is what happens when I tried to flash it.. After trying to turn my phone back on, it tries to load up with the cyanogenmod logo still there.
Mathieus-MacBook-Pro:hammerhead-lmy48i mathieulaflamme$ ./flash-all.sh
sending 'bootloader' (3119 KB)...
OKAY [ 0.202s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.403s
rebooting into bootloader...
OKAY [ 0.110s]
finished. total time: 0.110s
sending 'radio' (45425 KB)...
OKAY [ 1.535s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.759s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 06ed88372115a3f5
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.752s]
sending 'recovery' (9696 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s