hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
Related
Hey guys, i've a big problem.
Yesterday, suddently my nexus s didn't boot. It was stucked on Google logo.
It's rooted and it has the cm7 rom.
I tryed to reflash with cw recovery but i have an issue.
I cannot copy nothing on the sdcard partition.
I mount it with recovery and correctly copy the img from my pc. After i sync and dismount but if i remount the sdcard i cannot see the file that i've copied before.
It seems strange because if i try to format sdcard from recovery it says "done" but the data still remain.
After that i tried to lock and reunlock my phone but it fail.
I launch the command fastboot oem unlock, correctly the two-choices window appear, i select yes but on my pc i see (erase fail) and bootload remain unlocked.
Please give me some advice to resurrect my phone.
Thanks for the support, and sorry for my bad english.
Emiliano
fastboot oem unlock wont lock it, use fastboot oem lock.
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
I had almost the exact same problem yesterday. Tried literally everything and nothing worked. In fact it kept getting a little worse with every battery pull/reboot.
I purposely re locked the boot loader, right before I went to Sprint and paid $38 for a working replacement.
Probably be a good long while before I root another phone.
Sent from my Nexus S 4G using Tapatalk
After 4.0.4 OTA update device is bricked.
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Sounds like hardware issue. Have you tried formatting the sdcard in windows or running chkdsk /F.
I Have Same Problem how can i fix it?
LeeVidor said:
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Click to expand...
Click to collapse
please anyone can help me how can i fix my mobile ...
You can't. It's a hardware common issue without any solution. Better sent it to repair. My two cents
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
sammme problem har you fix it?
benazhack said:
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
Click to expand...
Click to collapse
please help me if u get the solution plz
zaherrrr said:
please help me if u get the solution plz
Click to expand...
Click to collapse
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
OEM unlock FAILED (remote: Erase Fail)
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
TimeClypse said:
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
Click to expand...
Click to collapse
hetile said:
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
Click to expand...
Click to collapse
I'm speechless..hair dryer works for me too!!! THANK YOU GUYS!
I have a Nexus 5 that I purchased from Ebay, and I'm trying to flash stock krt16m to get the device working.
Here are some things that I've noticed:
When I fastboot oem unlock, I will see the lock state change to unlock, but then when I execute fastboot reboot-bootloader, the lock state after reboot will show locked.
This presents a problem when trying to run the script flash-all.sh because upon reboot of the boot-loader I'm unable to flash other images. So, I modified the script to do the following:
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
fastboot oem unlock
sleep 10
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.17.img
fastboot reboot-bootloader
fastboot oem unlock
sleep 10
fastboot -w update image-hammerhead-krt16m.zip
so that I could change the lock state to unlocked after every reboot before flashing the next image.
This succeeds, but when the Nexus 5 boots, it gets stuck in an 'X' boot loop. Sometimes I see messages like Unfortunately google.process.gapps failed, or similar. I'll also get into X boot loops where I don't get error messages, but I do get messages like, "Starting apps" and similar.
I tried factory reset/wipe in recovery mode, to no avail. I get error messages like, "failed to mount cache".
I tried flashing the stock cache, then formatting it, to no avail.
I also tried to sideload the stock images with adb when in recovery mode. Also to no avail.
The Ebay listing didn't give much information, but it did mention that this was a T-Mobile Nexus 5.
Help me! What else can I do?
Sounds like a nand failure. The boot loader staying locked is a key indicator of that. There's not really much more you can do.
theesotericone said:
Sounds like a nand failure. The boot loader staying locked is a key indicator of that. There's not really much more you can do.
Click to expand...
Click to collapse
Just to be clear, we're talking about the part: Sandisk SDIN8DE4 16 GB NAND flash?
Is there anyway that I can prove it's bad, besides the bootloader not staying in an unlocked state?
seanmeir said:
Just to be clear, we're talking about the part: Sandisk SDIN8DE4 16 GB NAND flash?
Is there anyway that I can prove it's bad, besides the bootloader not staying in an unlocked state?
Click to expand...
Click to collapse
The bootloader and the fact that you can't format anything are key signs. It's happened quite a few times on the N5 and I'm not aware of anyone who was able to fix it. Keep in mind I don't have the device in my hand but the symptoms you are describing are those of a bad nand.
I'd also vote for a corrupted NAND (As far as I remember, in the best situation the only way to fix a bad NAND is to power cycle it again.. and good luck doing that.. in the worst its just dead.). You bought a broken phone .
Also you don't need much more: If after rebooting the NAND is in the previous state, whatever you do, the NAND is broken.
Yes, your eMMC is definitely dead/damaged. It has happened to a few people, and it was the exact same every time. RMA or send in for repairs.
No one is going to "fix" the eMMC itself, not even LG, as it isn't worth the effort nor cost to do so. Any repair job will simply be a motherboard swap.
I have been trying to recover from a soft brick that suddenly happened on my phone, I think I can fix it as I can get into fastboot..
However I am trying to flash system and I am getting a write failure.
I am using this guide: https://docs.google.com/document/d/1Fw0hZGJDiHhzpQWkPghtBvSnYiufnMFP4V2XP6wjJE4/edit
and the latest stock android (the newer 5.1.1.)
I was having problems before in steps before that but I actually found that doing a fastboot oem lock / unlock and then trying actually let me get farther then I was able to before (before it failed on the bootloader-hammerhead part)
edit: ... after a write fail on the bootloader it seems that the nexus 5 is hardbricked... the phone will not turn on at all.. no screen ect.. although windows does make a noise when it is plugged in..
Hello to you all, I am new to XDA and it is because of this problem I am having.
The other day, my N5 shut down unexpectedly and kept that virtual power button pressed (I've seen this happen to a lot of people). The next day, it stopped doing that, but the next big issue started: The phone was stuck on boot animation. Since then, I am not able to boot the phone, so I entered the bootloader (which is still functional) and tried to unlock the bootloader (I blame myself for not doing this since the beginning) from my PC but every time it reboots the phone to keep the changes, the bootloader locks itself again, preventing me to fastboot an image to my device
This is the main issue here, I can't start up my phone, the bootloader won't unlock and somehow, I can't ADB because my PC won't recognize the device. In other words, it seems my Nexus is bricked (may be the first Nexus in the history to be bricked).
I believe there must be a solution for this problem, can anyone help me please!?!?!
Thank you all!
this is how I fix mine.
Can you boot into recovery?
hongkongking said:
this is how I fix mine.
Can you boot into recovery?
Click to expand...
Click to collapse
Hey, thanks for this help, I'll let you know how that goes. And yes, I can boot into recovery.
My device isnt recognized on ADB, and everytime I try to unlock the bootloader, when the device restarts, immeditaly locks the bootloader again.
did u factory reset and wipe dalvik / cache? did u install a correct PC driver? did you ever using adb to connect to your phone?
I remember someone said sometimes you need to unlock the bootloader several times to get it unlocked.
from this and this, your nand flash seems has problem.
Try using LG Flash Tool to flash facory image, it doesn't need to unlock bootloader, but i think it's better not to write anything to nand flash as you don't know if it has problem or not, do so might make your phone completely bricked.
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Cactus1ne said:
Hello there
I bought my SM-A125F\DS a few months ago and rooted it. It was working fine. A few weeks ago, I changed my SIM card, made a phone call and put my phone aside and didn't check it for a couple of hours. When I picked it up again, I saw no antenna bars. Turns out I have no IMEI on either SIM slots (says Unknown in About Phone tab). Since I kept no backups, I download the latest ROM from Samfrew and flashed it using Odin. I also ticked Nand Erase and PIT reset. Still no IMEI. And now Android OS is eating 99% of my memory and it just keeps restarting.
Now I am trying to relock the bootloader using ADB before taking it to a service center. Connecting my phone and entering either one of
fastboot flashing lock, fastboot oem lock, and fastboot oem relock
gives me
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Any help on either step of the way is much appreciated.
P.S. I am no tech savvy. The more detailed your answer, the better.
Click to expand...
Click to collapse
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
V0latyle said:
I believe the bootloader is locked in much the same way it is unlocked. Reboot to download mode, hold one of the Volume buttons until the bootloader screen appears, and select the option to relock your device.
Before you do that, though, I would suggest performing a complete flash with data wipe using Odin.
Click to expand...
Click to collapse
Thanks for the quick reply, much appreciated.
I have already tried complete data wipe using Odin; didn't work. But I had totally forgotten about the bootloader screen (rookie mistake). I'll definitely do that after trying what @Jerffelly suggested.
Jerffelly said:
@Cactus1ne
This IMEI bug could be due to rooting.
Try this guide, it helped many people.
Try this guide https://forum.xda-developers.com/t/...y-no-imei-no-sim.4386753/page-2#post-86588571
Click to expand...
Click to collapse
Worked like a charm. Much love to you and @dronkit for the detailed and easy-to-follow guide. I struggled a bit with the stuck on file analysis from Odin and device unauthorized from adb; nothing an xda forum search won't fix though.