When I try to flash a splash screen I get the following:
'splash1' (750 KB)... OKAY [ 0.386s]
writing 'splash1'... FAILED (remote: not allowed)
Any ideas?
Thanks
Sorry wrong board, my bad...
hello,
i've got this lg-D820 stuck in CWM Recovery v6.0.4.5 screen
i want to flash it back to recovery and downloaded 5.1.1 factory image from google developers site
but i always get error while flashing bootloader,something like this-
Code:
sending 'bootloader' (3119 KB)...
OKAY [ 0.334s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.583s
rebooting into bootloader...
OKAY [ 0.076s]
finished. total time: 0.080s
< waiting for device >
i need help to fix this set
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
stuck on logo boot
I can enter recovery mod, but I cant do nothing from there
it says 0 internal storage
here a pictures:
i58.tinypic.com/11al3xi.jpg
i59.tinypic.com/whz5v4.jpg
someone? any help
VanKS said:
someone? any help
Click to expand...
Click to collapse
Maybe help you
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
jordirpz said:
Maybe help you
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
Click to expand...
Click to collapse
Thank you for the respond!!
im getting this when im tryin to do it
and after it my nexus goes to boot loop
Code:
0606de650060d85d fastboot
erasing 'system'...
OKAY [ 0.117s]
sending 'system' (721400 KB)...
OKAY [ 22.793s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 23.093s
sending 'recovery' (9284 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.685s
sending 'boot' (8700 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.667s
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.288s
your Nexus 5 hammerhead 4.4 Restore Installer is now restored! :)
rebooting...
finished. total time: 0.086s
Press any key to continue . . .
VanKS said:
Thank you for the respond!!
im getting this when im tryin to do it
and after it my nexus goes to boot loop
Code:
0606de650060d85d fastboot
erasing 'system'...
OKAY [ 0.117s]
sending 'system' (721400 KB)...
OKAY [ 22.793s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 23.093s
sending 'recovery' (9284 KB)...
OKAY [ 0.505s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.685s
sending 'boot' (8700 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.667s
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.288s
your Nexus 5 hammerhead 4.4 Restore Installer is now restored! :)
rebooting...
finished. total time: 0.086s
Press any key to continue . . .
Click to expand...
Click to collapse
Use dead method
jordirpz said:
Use dead method
Click to expand...
Click to collapse
can you explain or give me a link?
VanKS said:
can you explain or give me a link?
Click to expand...
Click to collapse
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
---------- Post added at 12:06 AM ---------- Previous post was at 12:05 AM ----------
INSTRUCTIONS:
1) If for whatever reason you don't already have your drivers installed on your PC, download and*install*DRIVERS*(Win 8 Driver instructions included).
2) Download and extract*Restore_Nexus_5_KTU84P.zip*
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the phone)
4) Open up folder where you extracted theRestore_Nexus_5_KTU84P.zip*
5) Double Click on the "Recovery_Nexus5.bat" and follow the instructions,,,,it really is that easy!*(watch video and follow along)
6)*If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power), connect phone to PC, and click the "Dead_Nexus5.bat" file found in the folder.
jordirpz said:
forum.xda-developers.com/google-nexus-5/development/tool-06-03-14-one-click-factory-restore-t2513937
---------- Post added at 12:06 AM ---------- Previous post was at 12:05 AM ----------
INSTRUCTIONS:
1) If for whatever reason you don't already have your drivers installed on your PC, download and*install*DRIVERS*(Win 8 Driver instructions included).
2) Download and extract*Restore_Nexus_5_KTU84P.zip*
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the phone)
4) Open up folder where you extracted theRestore_Nexus_5_KTU84P.zip*
5) Double Click on the "Recovery_Nexus5.bat" and follow the instructions,,,,it really is that easy!*(watch video and follow along)
6)*If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power), connect phone to PC, and click the "Dead_Nexus5.bat" file found in the folder.
Click to expand...
Click to collapse
I tried it already, thought you mean to something else :<
Any suggestions ?
VanKS said:
Any suggestions ?
Click to expand...
Click to collapse
bump
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.