E:cant mount SD, cant write system.img - Nexus S Q&A, Help & Troubleshooting

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?

Related

[Q] [i9020a] Failed 'System' remote Write

Hey all,
My Nexus S i9020a started getting into a bootloop. I went into the stock recovery and performed the wipes (multople times), but it still did the same thing when booting back up. It didn't remove my data either (I can see my widgets on the home screen before it goes into the reboot) even though I did a factory reset which is suppose to wipes out everything.
I decided to try a factory restore with a Google Image, but the two that I tried (4.0.4 and 4.1.2) both make it to the same part and failed. My bootloader is already unlocked (Lock State - Unlocked)
For 4.0.4
> fastboot -w update image-sojua-imm76d.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXKL1
Baseband Version.....: I9020UCKJ1
Serial Number........: 303356BD009100EC
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3444 KB)...
OKAY [ 0.538s]
writing 'boot'...
OKAY [ 0.506s]
sending 'recovery' (3776 KB)...
OKAY [ 0.591s]
writing 'recovery'...
OKAY [ 0.547s]
sending 'system' (282194 KB)...
OKAY [ 44.149s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 46.397s
For 4.1.2
> fastboot -w update image-sojua-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020UCLH1
Serial Number........: 303356BD009100EC
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (3964 KB)...
OKAY [ 0.621s]
writing 'boot'...
OKAY [ 0.606s]
sending 'recovery' (4308 KB)...
OKAY [ 0.655s]
writing 'recovery'...
OKAY [ 0.628s]
sending 'system' (337599 KB)...
OKAY [ 53.689s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 56.368s
Any ideas?
How about
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and format /system partition via CWM before updating?
_android_ said:
How about
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
and format /system partition via CWM before updating?
Click to expand...
Click to collapse
Installed 5.0.2.0, did the wipes and even picked fixed permissions, then tried to flash 4.1.2 factory image again but still failed at the same spot
EDIT: Tried with 6.0.2.5 also, did wipes, fix permissions. tried cm10
was able to push it to sd card, but when I selected it from the menu i get
set_perm: some changes failed
E:Error in /sdcard/cm-10.0.0-crespo.zip
(Status 7)
Installation aborted.
Looks like flash drive, system partition or partition table is corrupted.
Not sure if this will help [HOWTO] "Partitioning" your Nexus S using LVM
Does root need to be installed to flash a ROM from clockwork recovery?
primal2005 said:
Does root need to be installed to flash a ROM from clockwork recovery?
Click to expand...
Click to collapse
No. Root not required to flash ROM. Just CWM.

[Q] Nexus 5 RMA/Stock Recovery

My Nexus 5 recently had some hardware issue and I requested an RMA. The following error comes up when I try to flash the stock recovery system back. Is it okay if I send the Nexus 5 with TWRP installed?
sending 'bootloader' (2508 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.479s
rebooting into bootloader...
OKAY [ 0.126s]
finished. total time: 0.126s
sending 'radio' (42049 KB)...
OKAY [ 1.520s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.741s
rebooting into bootloader...
OKAY [ 0.123s]
finished. total time: 0.124s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-1.0.25.0.23
Serial Number........: 07219a4613c86dd0
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8628 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.728s]
sending 'recovery' (9210 KB)...
OKAY [ 0.541s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.641s
I hate to be the bearer of bad news, but it appears the flash memory is bad on your N5. See here. As for whether it's okay to send it with TWRP installed...hmm. I dunno. I don't think an eMMC failure could be caused by installing TWRP so it shouldn't be considered your fault, but they might make you pay for the repair because of it.
Brushstroke said:
I hate to be the bearer of bad news, but it appears the flash memory is bad on your N5. See here. As for whether it's okay to send it with TWRP installed...hmm. I dunno. I don't think an eMMC failure could be caused by installing TWRP so it shouldn't be considered your fault, but they might make you pay for the repair because of it.
Click to expand...
Click to collapse
Okay, I will post back when I get told about paying for the repair. Thanks.
Wellin said:
Okay, I will post back when I get told about paying for the repair. Thanks.
Click to expand...
Click to collapse
How did you fare with Google and this issue?

stuck on boot logo help

I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Latheman said:
I have a Razr HD (my dad's) he took the newest update last week and now he is stuck at the boot logo.(I have told him to not do it) ADB screen is telling me it is unlocked at stats code 3, (I think a dev edition, he bought it used) now I can't get it to take a recovery to flash stock 4.4.2. I tried this script here (http://forum.xda-developers.com/showthread.php?t=2474393) but it wouldn't restore it to stock and let me use the phone.
Any ideas from the android gurus.
Click to expand...
Click to collapse
is this a 926 or 925
if 926
use rsd lite and this guide form @SamuriHL http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083 i would recommend the full script since you are already unlocked and it was a used phone
if 925
same procedure but with the correct sbf from http://sbf.droid-developers.org/
I did this earlier. Same problem
Latheman said:
I did this earlier. Same problem
Click to expand...
Click to collapse
try this utility. it is a special version to fix certain issues that cant be fixed with fastboot and rsd.
watch the dialog and let me know if any operations fail, or copy and paste the output here for me to see.
i may have to update it for you if a couple specific things fail.
windows or linux?
Latheman said:
windows or linux?
Click to expand...
Click to collapse
windows only
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Latheman said:
windows or linux?
Click to expand...
Click to collapse
flash in fastboot same as the rest.
OK thanks. give me 10 minuets
this phone has the 9/9/14 update that won't be a problem right? just making sure
Latheman said:
this phone has the 9/9/14 update that won't be a problem right? just making sure
Click to expand...
Click to collapse
it wont be a problem, but some parts will fail. im downloading the files now to compare the parts i would like to see work.
either way, try that for now and let me know how it goes. there should be no added danger, the trust zone and partition files are what could fail, neither can be downgraded, so i dont see it making things worse if it doesnt work.
the phone says update gpt-main partition failed then the terminal end is FAILED (remote failure)
here is the output on the computer, sorry it is so long
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] Be VERY aware! This WILL wipe your userdata, including contacts, apps, etc.
[*] I am not responsible if this wipes your internal sdcard, and you should
[*] backup anything worth it to you to your external sdcard and computer before
[*] you choose to continue. You can exit now with the X button on this window.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] This script will also wipe your data (did i mention this will wipe your data
?).
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.156s
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.187s
sending 'sbl2' (126 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.172s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.370s
sending 'rpm' (140 KB)...
OKAY [ 0.029s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.315s
sending 'tz' (210 KB)...
OKAY [ 0.036s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.200s
sending 'aboot' (256 KB)...
OKAY [ 0.039s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.346s
sending 'modem' (30720 KB)...
OKAY [ 2.299s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.464s
sending 'fsg' (165 KB)...
OKAY [ 0.032s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.187s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.083s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'logo' (854 KB)...
OKAY [ 0.083s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.238s
sending 'boot' (10240 KB)...
OKAY [ 0.781s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 0.929s
sending 'recovery' (10240 KB)...
OKAY [ 0.805s]
writing 'recovery'...
Failed to erase partition
Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.969s
erasing 'userdata'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
sending 'system' (30720 KB)...
OKAY [ 2.357s]
writing 'system'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 2.447s
erasing 'tombstones'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.084s
erasing 'cache'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.188s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.009s
Hit ENTER to return.
Latheman said:
here is the output on the computer, sorry it is so long
Click to expand...
Click to collapse
dammm
my file is almost done, let me compare a couple md5's from the old update and ill get right back to ya with what it looks like.
---------- Post added at 06:35 PM ---------- Previous post was at 06:24 PM ----------
@Latheman
ok, they changed the partition table again, not saying the phone is fixable, but this is the best chance i could have wanted to fix it.
its going to take me 1/2 hour to fix the script, and an hour (barring issue) to upload it.
ill send it over as soon as its done, if not tonight, then tomorrow.
Thank-you
Latheman said:
Thank-you
Click to expand...
Click to collapse
test flash on my updated phone, only tz failed because i removed it, but will be in your version as you already took it.
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*] Maintained by bweN diorD
[*] Before continuing, ensure your device is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'partition' (32 KB)...
OKAY [ 0.015s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.859s]
finished. total time: 0.874s
sending 'sbl1' (101 KB)...
OKAY [ 0.019s]
writing 'sbl1'...
OKAY [ 0.648s]
finished. total time: 0.668s
sending 'sbl2' (127 KB)...
OKAY [ 0.183s]
writing 'sbl2'...
OKAY [ 1.033s]
finished. total time: 1.216s
sending 'sbl3' (512 KB)...
OKAY [ 0.052s]
writing 'sbl3'...
OKAY [ 1.113s]
finished. total time: 1.165s
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.473s]
finished. total time: 0.496s
error: cannot load 'tz.mbn'
sending 'aboot' (256 KB)...
OKAY [ 0.193s]
writing 'aboot'...
OKAY [ 1.594s]
finished. total time: 1.788s
sending 'modem' (30720 KB)...
OKAY [ 2.320s]
writing 'modem'...
OKAY [ 2.680s]
sending 'modem' (19212 KB)...
OKAY [ 3.845s]
writing 'modem'...
OKAY [ 1.095s]
finished. total time: 9.944s
sending 'fsg' (165 KB)...
OKAY [ 0.027s]
writing 'fsg'...
OKAY [ 0.855s]
finished. total time: 0.882s
erasing 'modemst1'...
OKAY [ 1.698s]
finished. total time: 1.699s
erasing 'modemst2'...
OKAY [ 1.232s]
finished. total time: 1.232s
sending 'logo' (854 KB)...
OKAY [ 0.076s]
writing 'logo'...
OKAY [ 1.955s]
finished. total time: 2.032s
sending 'boot' (10240 KB)...
OKAY [ 0.784s]
writing 'boot'...
OKAY [ 5.946s]
finished. total time: 6.730s
sending 'recovery' (10240 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 4.749s]
finished. total time: 5.530s
sending 'system' (30720 KB)...
OKAY [ 2.324s]
writing 'system'...
OKAY [ 2.254s]
sending 'system' (30720 KB)...
OKAY [ 5.467s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.223s]
writing 'system'...
OKAY [ 0.015s]
sending 'system' (30720 KB)...
OKAY [ 4.727s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.707s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.983s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.718s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.729s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.646s]
writing 'system'...
OKAY [ 0.023s]
sending 'system' (30720 KB)...
OKAY [ 5.097s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 5.140s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.697s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.662s]
writing 'system'...
OKAY [ 0.021s]
sending 'system' (30720 KB)...
OKAY [ 4.712s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.067s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.677s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.682s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.696s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.232s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.717s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.636s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.750s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.715s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.701s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.703s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 5.604s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (30720 KB)...
OKAY [ 4.694s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.708s]
writing 'system'...
OKAY [ 0.018s]
sending 'system' (30720 KB)...
OKAY [ 4.710s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 5.034s]
writing 'system'...
OKAY [ 0.019s]
sending 'system' (30720 KB)...
OKAY [ 4.686s]
writing 'system'...
OKAY [ 0.020s]
sending 'system' (21722 KB)...
OKAY [ 4.040s]
writing 'system'...
OKAY [ 1.323s]
finished. total time: 285.670s
erasing 'tombstones'...
OKAY [ 2.049s]
finished. total time: 2.049s
erasing 'cache'...
OKAY [ 2.632s]
finished. total time: 2.632s
[*] Flash complete, Rebooting...
rebooting...
finished. total time: 0.005s
Hit ENTER to return.
so what should I do? remove a file from the folder you sent me?
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
no, i was just showing you the new version is built, tested, working and uploading now.
so, when i post it later for you to try, this is pretty much a last resort script. if it doesn't work for you, the phone is likely gone.
---------- Post added at 07:42 PM ---------- Previous post was at 07:05 PM ----------
Latheman said:
so what should I do? remove a file from the folder you sent me?
Click to expand...
Click to collapse
ok she is done
http://www.mediafire.com/download/5mmd0jv84c51rvt/DROID_RAZR_HD_Utility_1.4gpt-2a_KK.rar
edit: just changed the download link to another version containing the tz file i forgot to replace, for whoever might need it in the future.
Thanks I'll try it soon.
Latheman said:
Thanks I'll try it soon.
Click to expand...
Click to collapse
i forgot to drop the tz file back in before i uploaded it, its no big deal and shouldnt matter, but you should drop this into the directory in the rare event it becomes needed.
https://www.dropbox.com/s/f27cfsjyewlnlu4/tz.mbn?dl=0
I tried it, and no soap, I think this one is a loss . (first one of every phone I have worked on). the BL is still unlocked so if anybody ever comes up with something in the future, or I can put something together I might be able to restore it.
Did you try to flash stock with rsd 6.1.5 and editing xml file, say removing tz line

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

Categories

Resources