Database Info

[Q] Samsung Focus doesn't boot

Hi, please help me. My Samsung Focus 1.3 doesn't boot, only starts and gets stuck on samsung blinking screen. I've tryed to make hard reset, but keys don't work. It only accept download mode. What can I do?

Try either restoring a Zune update, or re-flashing the stock ROM. There should be downloads and instructions for the latter in the device-specific part of the forum.

Alternatively, make sure the SD card (if you use one) is seated correctly. However, I think the most likely problem is just hardware failure, in which case you probably need to get the phone replaced (I assume it's under warranty).

Hi, it's impossible to start on MAGLDGR mode. This phone only accept Download mode, the yellow triangle. There is another way to re-flash from download mode?
After flashing with Focus 1.3 i917 AT&T USA and i917R ROGERS CANADA RETAIL ROMs, using WP7 downloader v. 7.21, it's stucked and just displays SAMSUNG.
Sorry, almost forget, Zune doesn't recognize my device.

I re-flash using I917UCK3 with similar results. This are the processes on WP7:
Open Phone image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_phone_cetus_att.bin
Open Eboot image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_eboot_cetus_att.eb0
Open PDA image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_pda_cetus_att.nb0
Open CSC image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_csc_cetus_att_i917attjk2.csc
Detect COM17 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Erase MIBIB Region
[Channel 0] Write MIBIB Data
[Channel 0] MIBIB Download Success!!
[Channel 0] Erase FSBL Region
[Channel 0] Write FSBL Data
[Channel 0] FSBL Download Success!!
[Channel 0] Erase OSBL Region
[Channel 0] Write OSBL Data
[Channel 0] OSBL Download Success!!
[Channel 0] Erase AMSS Region
[Channel 0] Write AMSS Data
[Channel 0] AMSS Download Success!!
[Channel 0] Erase DSP1 Region
[Channel 0] Write DSP1 Data
[Channel 0] DSP1 Download Success!!
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] APPSBL Download Success!!
[Channel 0] Erase CSC Region
[Channel 0] Write CSC Data
[Channel 0] CSC Download Success!!
[Channel 0] Erase PDA Region
[Channel 0] Write PDA Data
[Channel 0] PDA Download Success!!
[Channel 0] FLASH LOCK
Detect COM17 Port

Samsung Focus doesn't boot
jmweb said:
I re-flash using I917UCK3 with similar results. This are the processes on WP7:
Open Phone image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_phone_cetus_att.bin
Open Eboot image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_eboot_cetus_att.eb0
Open PDA image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_pda_cetus_att.nb0
Open CSC image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_csc_cetus_att_i917attjk2.csc
Detect COM17 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Erase MIBIB Region
[Channel 0] Write MIBIB Data
[Channel 0] MIBIB Download Success!!
[Channel 0] Erase FSBL Region
[Channel 0] Write FSBL Data
[Channel 0] FSBL Download Success!!
[Channel 0] Erase OSBL Region
[Channel 0] Write OSBL Data
[Channel 0] OSBL Download Success!!
[Channel 0] Erase AMSS Region
[Channel 0] Write AMSS Data
[Channel 0] AMSS Download Success!!
[Channel 0] Erase DSP1 Region
[Channel 0] Write DSP1 Data
[Channel 0] DSP1 Download Success!!
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] APPSBL Download Success!!
[Channel 0] Erase CSC Region
[Channel 0] Write CSC Data
[Channel 0] CSC Download Success!!
[Channel 0] Erase PDA Region
[Channel 0] Write PDA Data
[Channel 0] PDA Download Success!!
[Channel 0] FLASH LOCK
Detect COM17 Port
Click to expand...
Click to collapse
Hello, i have got the same probleme, please how did you resolve the problème ?

[Q] Omnia W Flashing

Hi, I'm using i8350XXKK4_PLSKK4
CSC_I8350PLSKK4.csc
EBOOT_I8350XXKK4_REV0.eb0
PDA_I8350XXKK4_REV0.nb0
PHONE_WEMBLEY_16002402_open_KK1_rev00_RC1.bin
Flasher:
WP7_Downloader_Ver_3.8_for_Secure_and_SMD_change_Parttiton_and_Support_Retail_binary
Then I made this steps:
- Phone into Download Mode: ( Volume Up Key + Camera Key + Power ).
- Connect USB cable to Phone
- Click Start button to update the phone.
But after a second there is an error message:
APPSBL WRITE FLASH Failed!
Open PDA image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\PDA_I8350XXKK4_REV0.nb0
Open CSC image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\CSC_I8350PLSKK4.csc
Open Phone image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\PHONE_WEMBLEY_16002402_open_KK1_rev00_RC1.bin
Open Eboot image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\EBOOT_I8350XXKK4_REV0.eb0
Detect COM3 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] CheckSum Data set TRUE
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Ask the device type.
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] Write APPSBL Data Fail!!!
Any help please?

Presently this flashing tool is not working with omnia w.

[Q] Razr HD XT926 Kit Kat VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip

Hi all, still a newbie here - so i cannot post this in Development forum
i would like to share the following file:
'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'
@SamuraiHL i'm sure youve been waiting for this.
special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.
link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing

stras1234 said:
Hi all, still a newbie here - so i cannot post this in Development forum
i would like to share the following file:
'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'
@SamuraiHL i'm sure youve been waiting for this.
special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.
link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing
Click to expand...
Click to collapse
OMG yes we needed this so bad. I wish you had spelled my username correctly so I'd have seen this sooner. LMAO! THANK YOU!

Thanks stras1234!
The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.
BBB
Crack for Crackers

realbbb said:
Thanks stras1234!
The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.
BBB
Crack for Crackers
Click to expand...
Click to collapse
What is the difference?

realbbb said:
Thanks stras1234!
The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.
BBB
Crack for Crackers
Click to expand...
Click to collapse
jldr said:
What is the difference?
Click to expand...
Click to collapse
The version number and release signing keys used. That's IT. I don't much care as those who are bricked now (and I have a bunch of people who attempted to downgrade to JB cause they "didn't like KK" ) can fix their phones. if they want the "official" FXZ later, it's a matter of using my RSD Script Generator and flashing it. They won't even lose data in the process.

Virtually nothing. BUT, I ran OTA to 182.46.10. It was problematic. Factory wipe did not fix the battery drain, random crashes, audio hiss. Went to OTA 183.46.10. Issues have gone away.
BBB
Lost in Code.

Oh awesome. So I'll be able to flash from rooted, unlocked CM11 straight to stock KitKat now?

Yup, you can.

Outstanding. Eagerly awaiting your awesome instructions!
I know I asked that same damn question 5 times, I think I'm done now!

http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I've updated my thread on droidrzr. Thanks again, Stras! Really appreciated!

@stras1234 thank you so much!
@SamuriHL what the hell would this forum do without us? And yet still no SS backup of a rooted stock system lol

LOL I know, right? Hopefully someone will be able to provide that. Am curious if the idea will work.

SamuriHL said:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I've updated my thread on droidrzr. Thanks again, Stras! Really appreciated!
Click to expand...
Click to collapse
I gave that a try with my bricked Maxx HD and it failed when writing the system image

You need to post the exact error you're getting if you want me to help. It definitely works, so, it's something in your environment preventing it.

SamuriHL said:
You need to post the exact error you're getting if you want me to help. It definitely works, so, it's something in your environment preventing it.
Click to expand...
Click to collapse
Where can I find the info you need? I was rooted and unlocked when OTA forced hit me. In the AP Fastboot menu I am showing locked now with status code 0.

qqjjz said:
Where can I find the info you need? I was rooted and unlocked when OTA forced hit me. In the AP Fastboot menu I am showing locked now with status code 0.
Click to expand...
Click to collapse
In your RSD folder, look for an SWDL txt file and post it here so I can look at it. Do not worry about the locked status. It's only a temporary thing until we fix the failed flash. Don't panic. This can be fixed.

I think it's because you used the universal script which doesn't update the GPT partitioning. If you're going from JB to KK for the first time, you probably need it to do that.
Basically your partitions are hosed now and you need to find a way to fix them.
EDIT: Never mind, SamuraiHL knows what he's talking about, ignore me.

killrhythm09 said:
I think it's because you used the universal script which doesn't update the GPT partitioning. If you're going from JB to KK for the first time, you probably need it to do that.
Basically your partitions are hosed now and you need to find a way to fix them.
Click to expand...
Click to collapse
Naw, you don't have to flash gpt. I've had others not flash it and it worked fine for them.

SamuriHL said:
In your RSD folder, look for an SWDL txt file and post it here so I can look at it. Do not worry about the locked status. It's only a temporary thing until we fix the failed flash. Don't panic. This can be fixed.
Click to expand...
Click to collapse
Oh no man I am good. I've been poking around my phones and rooting for a few years but I've never encountered anything like this. I am glad I did though because I need to know all this stuff. I'm running on my backup phone right now so what we're repairing here is just to let me have a dev phone and another backup phone
If there is one thing I know about Motorola, they're very sneaky with backdoors and tools when it comes to software. I've worked with them for several years in software testing.
I really appreciate all you guys help btw. Here is the data.
05/22/14 19:11:02 --------------------------------------------------------------------------------
05/22/14 19:11:02 New Log Started For Software Download.
05/22/14 19:11:39 The FlashLog key is turned off.
05/22/14 19:12:49 Multi upgrade started for 1 phones
05/22/14 19:12:49 [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn"
05/22/14 19:12:50 [Device ID: 0] 2/15 flash sbl2 "sbl2.mbn"
05/22/14 19:12:51 [Device ID: 0] 3/15 flash sbl3 "sbl3.mbn"
05/22/14 19:12:52 [Device ID: 0] 4/15 flash rpm "rpm.mbn"
05/22/14 19:12:53 [Device ID: 0] 5/15 flash aboot "emmc_appsboot.mbn"
05/22/14 19:12:54 [Device ID: 0] 6/15 flash modem "NON-HLOS.bin"
05/22/14 19:13:09 [Device ID: 0] 7/15 flash fsg "fsg.mbn"
05/22/14 19:13:10 [Device ID: 0] 8/15 erase modemst1
05/22/14 19:13:11 [Device ID: 0] 9/15 erase modemst2
05/22/14 19:13:12 [Device ID: 0] 10/15 flash logo "logo.bin"
05/22/14 19:13:14 [Device ID: 0] 11/15 flash boot "boot.img"
05/22/14 19:13:21 [Device ID: 0] 12/15 flash recovery "recovery.img"
05/22/14 19:13:27 [Device ID: 0] 13/15 flash system "system.img"
05/22/14 19:14:04 ERROR: 13/15 flash system "system.img" -> Phone returned FAIL. - on device ID 0.
05/22/14 19:14:04 [Device ID: 0] 13/15 flash system "system.img" -> Phone returned FAIL.
05/22/14 19:14:04 ERROR: Failed flashing process. - on device ID 0.
05/22/14 19:14:04 Multi upgrade finished.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.

I'm guessing you have one of the following problems that you need to resolve:
o) Latest Moto USB driver must be installed
o) Must be a USB 2 port, *NOT* a USB 3 port
o) Must be original OEM cable that came with the phone (yes, it matters)
Basically it failed to send system to your phone...and it's a large freaking file so the transfer failed.

[Q] RDS Lite error reboot-bootloader -> No arrival message notification

Hi i tried to return to stock rom using RDS lite v6.1.5 . i have an Atrix 2 ATT
I did use this file
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285
The process stop on this step
[Device ID: 0] 5/20 reboot-bootloader -> No arrival message notification
After that error my phone is not responding. i have tried
volume up + down
volume up + down + power up
None of above option had worked. Please share any information to have it working back again
here is the log from RSD Lite
06/13/15 00:08:07 Multi upgrade started for 1 phones
06/13/15 00:08:07 [Device ID: 0] 1/20 flash mbm "allow-mbmloader-flashing-mbm.bin"
06/13/15 00:08:08 [Device ID: 0] 2/20 reboot-bootloader
06/13/15 00:08:17 [Device ID: 0] 3/20 flash mbmloader "mbmloader.bin"
06/13/15 00:08:17 [Device ID: 0] 4/20 flash mbm "mbm.bin"
06/13/15 00:08:18 [Device ID: 0] 5/20 reboot-bootloader
06/13/15 00:15:28 000012d4 Phone.cpp 1571 0 ERROR Waiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
06/13/15 00:15:28 ERROR: 5/20 reboot-bootloader -> No arrival message notification - on device ID 0.
06/13/15 00:15:28 [Device ID: 0] 5/20 reboot-bootloader -> No arrival message notification
06/13/15 00:15:28 ERROR: Failed flashing process. - on device ID 0.
06/13/15 00:15:29 Multi upgrade finished.

vald3zss said:
Hi i tried to return to stock rom using RDS lite v6.1.5 . i have an Atrix 2 ATT
I did use this file
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285
The process stop on this step
[Device ID: 0] 5/20 reboot-bootloader -> No arrival message notification
After that error my phone is not responding. i have tried
volume up + down
volume up + down + power up
None of above option had worked. Please share any information to have it working back again
here is the log from RSD Lite
06/13/15 00:08:07 Multi upgrade started for 1 phones
06/13/15 00:08:07 [Device ID: 0] 1/20 flash mbm "allow-mbmloader-flashing-mbm.bin"
06/13/15 00:08:08 [Device ID: 0] 2/20 reboot-bootloader
06/13/15 00:08:17 [Device ID: 0] 3/20 flash mbmloader "mbmloader.bin"
06/13/15 00:08:17 [Device ID: 0] 4/20 flash mbm "mbm.bin"
06/13/15 00:08:18 [Device ID: 0] 5/20 reboot-bootloader
06/13/15 00:15:28 000012d4Phone.cpp15710ERRORWaiting for phone's handle is setted successfully after restart [430000 ms] completion. failed
06/13/15 00:15:28 ERROR: 5/20 reboot-bootloader -> No arrival message notification - on device ID 0.
06/13/15 00:15:28 [Device ID: 0] 5/20 reboot-bootloader -> No arrival message notification
06/13/15 00:15:28 ERROR: Failed flashing process. - on device ID 0.
06/13/15 00:15:29 Multi upgrade finished.
Click to expand...
Click to collapse
Was the phone on ICS or GB before you started trying to flash it? If it was ICS then it's hard bricked because you're flashing the GB FXZ.

Nexus 5 stuck in boot animation?

Hi,
my Nexus 5 was plugged on my laptop.
After a while I saw, that my phone rebooted. I saw the google logo.
I pressed and hold the "Power Button".
My phone booted again and stuck in the booting animation.
This happened three days ago.
I tried so many things. It's not working.
Maybe I messed up the partition.
The first thing I tried was to flash the android factory image like this (Flashing instructions - don't forget to press the button "ACKNOWLEDGE"):
https://developers.google.com/android/images
I first thought, that maybe the eMMC is fried.
I checked this like this ( https://forum.xda-developers.com/showthread.php?t=1284196 ):
Code:
adb shell
dmesg | grep mmc0
I didn't get a message like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
I read, that I should change to usb 2.0 port and the usb cable.
I've also a Galaxy nexus. I've tried to flash a new stock with WugFresh. Everything worked with the usb 2.0 port and the usb cable.
When I tried to do that with my nexus 5 nothing works. I get this failure messages:
FAILED (remote: flash write failure)
I used TWRP (twrp-3.0.3-0-hammerhead.img) and clockwork mod (recovery-clockwork-touch-6.0.4.4-hammerhead.img).
The main errors I get:
Can't mount /data
...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovers/log
E: Can't open /cache/recovers/log
...
I really don't know what to do.
Is there a method to build the partition new? Or what else can I do?
Thank you for any help.

Does the bootloader relock when rebooted after being unlocked? Have you tried flashing the stock KK ROM?

Yes. It relocks when rebooted.

Do you mean Kit Kat? No, I didn't. I've tried only the new versions like 6.0.1 (MOB31E), 6.0.1 (M4B30Z, Dec 2016).
I will try KK Rom later.

I've downloaded this factory image:
"hammerhead" for Nexus 5 (GSM/LTE)
4.4.4 (KTU84P)
from here: https://developers.google.com/android/images
This is the original "flash-all.bat" file:
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've changed the "flash-all.bat" a little bit. I added this line "fastboot oem unlock". When I not add "fastboot oem unlock", I get a message like "not unlocked":
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
[B]fastboot oem unlock[/B]
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've started the "flash-all.bat". This is the output:
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
< waiting for any device >
...
OKAY [ 4.109s]
finished. total time: 4.109s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.844s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
< waiting for any device >
...
OKAY [ 6.250s]
finished. total time: 6.250s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
wiping cache...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 04ae306b2524b05b
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ20f'.
Update requires 'HHZ11k'.
finished. total time: 0.594s
Press any key to exit...

Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.

audit13 said:
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
Click to expand...
Click to collapse
I have the same problem and after doing that I can see that my eMMC is in fact fried since the bootloader relocks. I was wondering, where is the bootloader/fastboot stored on the device? On the CPU/GPU/RAM stack or on the eMMC. If I swap out the eMMC chip, will I still be able to access it (the bootloader) with a blank eMMC or is it on the eMMC as well? I'm trying to find out what are the steps to format and partition the eMMC after a new one is installed...

I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.

audit13 said:
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
Click to expand...
Click to collapse
Thank you very much for sharing your experience!
I would assume that the bootloader is located on the eMMC since I can't write to the bootloader (or any other) partition from fastboot. I'll have to look into solutions during the weekend since I don't have much time until then, but replacing the MB is a no go for me because of the price.

I'm not sure where you are located but I live in a big city in Canada where I can find deals for people selling Nexus 5 phones with smashed screens and working internal components.
Good luck and please share your results. Thanks.

@audit13: When I unlock the bootloader and then reboot the phone into fastboot. The bootloader relocks.
Is the memory chip now really damaged? Can't I do nothing? My N5 is three years old. I don't want to pay a lot of money for a main board.

The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.

I bought a display damaged nexus 5. It arrived today. Changed the main board. And Voila! It's working.
The other guy has installed this build:
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (MOB30H)
No my question: Which factory image should I install?
https://developers.google.com/android/images
"hammerhead" for Nexus 5 (GSM/LTE)
...
6.0.1 (MOB30H)
6.0.1 (MOB30M)
6.0.1 (MOB30P)
6.0.1 (MOB30Y)
6.0.1 (MOB31E)
6.0.1 (M4B30X, Oct 2016)
6.0.1 (M4B30Z, Dec 2016)
I'm not sure, because the last two has dates. Are they meaning something (I mean, are they special builds), because the other factory images don't have dates.

Or should I do this:
https://developers.google.com/android/ota
OTA binary image files that allow you to manually update your Nexus or Pixel device. This has the same effect of flashing the corresponding factory images, but without the need of wiping the device.
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (M4B30Z)
Is OTA better than factory images?

OK. I've installed this version 6.0.1 (M4B30Z, Dec 2016). Everything works.