[Nexus 6 Q&A, Help & Troubleshooting] nitrous²:
I fell victim to a fraud. The device sold to me was a defective one. The owner was obliged by Motorola to return the defective device to a certified retail shop after he received a replacement Nexus 6! Instead, he sold it to me. Unfortunately this is all I can tell you as I may have to take legal action. I will never buy a used device again. If one day, you can't sell your old phone, be sure to send out your kind Thank You letters to aforementioned guy.

What happened so far

The standard procedure of manually flashing the factory image and locking the bl afterwards has been proven unsuccessfull. Please stop suggesting me to do it! I did it literally a thousand times already!​

Starting to think that the repair centre (Device was sent for RMA in Germany, Gießen at Saturn Elektromarkt) flashed a non-relockable bootloader onto it. Seriously, I think I literally tried everything on the internet.

Here is a chronological summary:

First encounter of unlocked bootloader.

Noticed screen burn in. Prepare for RMA starts here.

Noticed earpiece not working.

First attempt to locking bootloader after succesfull manual factory image flash.

-Results in:

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s

Try "fastboot oem lock begin" method.

-Results in:

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>[COLOR="Red"]fastboot oem lock begin[/COLOR]
...
[COLOR="red"](bootloader) Ready to flash signed images[/COLOR]

OKAY [ 0.121s]
finished. total time: 0.123s
M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (7731 KB)...
OKAY [ 0.252s]
writing 'boot'...
[COLOR="red"](bootloader) Preflash validation failed
FAILED (remote failure)[/COLOR]
finished. total time: 0.271s

M:\SHAMU\FACTORY IMAGE\shamu-lmy47z>

Notice messages in "Bootloader Logs" within bootloader menu.

cmd: oem lock
hab check failed for boot
failed to validate boot image

A bad download is assumed. Kind members upload their boot.img for testing purposes if downloads are actually corrupt.

-Results in same error.

Try everything again on Mac.

-Results in same error.

Try everything on Linux Ubuntu.

-Results in same error.

Try everything with Factory Image provided by MotoFirmware.

-Results in same error.

Panic.

Open thread on MototFirmware.

Assume conspiracy.

Wait for answers...

-Still waiting...

Make a video about it;

[YOUTUBE]watch?v=CDBGUBQOxG8[/YOUTUBE]

Please tell me I'm doing something wrong or overlooking something.

Hi. I'm very new to the Nexus 6 but quite familiar with the Nexus family. Owned all of them except the 6. I bought it from eBay and upon opening it, the first things I did was to check whether the bootloader was unlocked or not. It was already unlocked (Status 3).

For initial testing, I wanted to relock the bootloader but always ended up with an error saying I'd have to start with "fastboot oem unlock begin", flash a factory image and end the process with "fastboot oem lock". However, I can't do that because I get the famous "Error: Update Package Missing System.img" error.

I hope I understood this correctly. According to the info I gathered, in order to lock the bootloader I'd have to do the following:

1- Reboot to bootloader

2- "fastboot oem lock begin"

3- flash factory image via "flash-all.bat" with latest image

4- after flash process ends, reboot to bootloader

5- "fastboot oem lock"

Since I can't do step 3 because of "Error: Update Package Missing System.img" error, I replace step 3 with "flash all .imgs manually". After successfully flashing the factory image I typed "fastboot oem lock" and got the same error message as written in the title. I'd really appreciate your answers as I'm really worried being sold a "bad" device.

Here is an example of what happens:

[MENTION=5020010]Mr_S[/MENTION] have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message

...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s

Turns out I have to type

fastboot oem lock begin

first, then flash a factory image and end the process with

fastboot oem lock

However that doesn't work as upon finishing flashing BL and radio .imgs, the updater script tells me that system.img is missing, press any key to exit. The process aborts. Ending this process with

fastboot oem lock

gives out the same error message as above. Flashing the factory image manually and it's the same all over again. Now I'm desperate for a solution.

If the partition table is of any help, here it is.

127|root@shamu:/ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 61079552 mmcblk0
179 1 114688 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 384 mmcblk0p3
179 4 56 mmcblk0p4
179 5 16 mmcblk0p5
179 6 32 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 512 mmcblk0p9
179 10 500 mmcblk0p10
179 11 4156 mmcblk0p11
179 12 384 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 256 mmcblk0p14
179 15 512 mmcblk0p15
179 16 500 mmcblk0p16
179 17 4 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 1024 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 16384 mmcblk0p24
179 25 2048 mmcblk0p25
179 26 32768 mmcblk0p26
179 27 256 mmcblk0p27
179 28 32 mmcblk0p28
179 29 128 mmcblk0p29
179 30 8192 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 2528 mmcblk0p32
259 1 1 mmcblk0p33
259 2 8 mmcblk0p34
259 3 16400 mmcblk0p35
259 4 9088 mmcblk0p36
259 5 16384 mmcblk0p37
259 6 262144 mmcblk0p38
259 7 65536 mmcblk0p39
259 8 1024 mmcblk0p40
259 9 2097152 mmcblk0p41
259 10 58351488 mmcblk0p42
179 32 4096 mmcblk0rpmb
254 0 58351488 dm-0