Database Develop

[KINDA SOLVED] Can't relock Bootloader [UPDATED 2015-08-27]

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:
Code:
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:
Code:
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.
Code:
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;
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:
@Mr_S have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message
Code:
...
(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
Code:
fastboot oem lock begin
first, then flash a factory image and end the process with
Code:
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
Code:
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.
Code:
127|[email protected]:/ # 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
karandpr said:
Advisory :
Refrain from using boot images & bootloader images by Teamkang.
This member has passed off Nexus Q boot images as Nexus 6.
The bootloader is far from Nexus 6 bootloader as shown by member @rbox
http://forum.xda-developers.com/showpost.php?p=61817885&postcount=18
-karandpr
XDA Staff
Click to expand...
Click to collapse

I would urge you to reconsider locking your bootloader. There's no reason to unless you are returning it for repair.
With that said, if you really want to relock, follow this guide > http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302

cam30era said:
I would urge you to reconsider locking your bootloader. There's no reason to unless you are returning it for repair.
With that said, if you really want to relock, follow this guide > http://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Click to expand...
Click to collapse
Thank you, I've been reading that thread already. But as I said, whenever I try to lock the bootloader I get "start with fastboot oem lock begin" followed by the error message written in the thread title. Also when trying to flash the factory image with the flash-all.bat file, I end up with the error message "Error: Update Package Missing System.img".

nitrous² said:
Also when trying to flash the factory image with the flash-all.bat file, I end up with the error message "Error: Update Package Missing System.img".
Click to expand...
Click to collapse
Flash all doesn't work. You'll need to flash each .img file separately. And make sure your Android SDK is up to date. Google updated fastboot back in November to enable flashing the very large Lollipop system.img.

nitrous² said:
Thank you, I've been reading that thread already. But as I said, whenever I try to lock the bootloader I get "start with fastboot oem lock begin" followed by the error message written in the thread title. Also when trying to flash the factory image with the flash-all.bat file, I end up with the error message "Error: Update Package Missing System.img".
Click to expand...
Click to collapse
Flash all doesn't work. You have to flash the images individually. Follow method 2 in the sticky thread in general forum.

Evolution_Tech said:
Flash all doesn't work. You have to flash the images individually. Follow method 2 in the sticky thread in general forum.
Click to expand...
Click to collapse
Thank you. That was my guide when I flashed the image manually. But I'll give it another go soon.
Update July 7th 2015
Nope. No matter what I do, there's always the same error message. Has anyone ever managed to relock this thin anyway? I actually need it as I want to return it.

Seriously, has anyone an idea why I can't relock my bootloader? I tried it as described in these methods posted above but no luck. I must be overlooking something. I'm not doing it for fun either; I have burn ins on its AMOLED panel and the earpiece doesn't work so I have to return it for RMA.
Also my post from another thread with further information:
@Mr_S have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message
Code:
...
(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
Code:
fastboot oem lock begin
first, then flash a factory image and end the process with
Code:
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
Code:
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.

nitrous² said:
Seriously, has anyone an idea why I can't relock my bootloader? I tried it as described in these methods posted above but no luck. I must be overlooking something. I'm not doing it for fun either; I have burn ins on its AMOLED panel and the earpiece doesn't work so I have to return it for RMA.
Also my post from another thread with further information:
@Mr_S have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message
Code:
...
(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
Code:
fastboot oem lock begin
first, then flash a factory image and end the process with
Code:
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
Code:
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.
Click to expand...
Click to collapse
My guess is not flashing something right. Start from scratch. Flash all the images. Reboot. Make sure unlock is checked in developer options. Then fastboot oem lock. Never seen the fastboot oem lock begin message. Here are all the correct fastboot commands. No need to really run the erase and format commands but don't hurt except will have nothing to boot which is good enough for RMA. lol
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
fastboot flash radio {radio.img}
Step #2
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot format vendor {don't need for phone}
fastboot format cache
fastboot format userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot flash userdata {userdata.img}
fastboot reboot
adb reboot bootloader
fastboot oem lock

Heres how. flash this bootloader: http://forum.xda-developers.com/attachment.php?attachmentid=3399990&d=1436618712
Using
Code:
fastboot flash bootloader Teamkang-Shamu-Bootloader-Flashable.img
And then do
Code:
fastboot oem lock
and you should be locked.

Teamkang said:
Heres how. flash this bootloader: http://forum.xda-developers.com/attachment.php?attachmentid=3399990&d=1436618712
Using
Code:
fastboot flash bootloader Teamkang-Shamu-Bootloader-Flashable.img
And then do
Code:
fastboot oem lock
and you should be locked.
Click to expand...
Click to collapse
That is an unknown process and shouldn't be used. Should never blind download. Learn to do it correctly or don't do it at all.

prdog1 said:
That is an unknown process and shouldn't be used. Should never blind download. Learn to do it correctly or don't do it at all.
Click to expand...
Click to collapse
True but it works. you can just put the orginal bootloader back if you want if it wont work.

Still getting the same error message. Here's the full CMD log if you think I might have missed something. The only posts I could finde on the internet where the line "please run fastboot oem lock begin first" command is wirtten are related to the Moto X and some other Motorola devices. Have any of you guys had your bootloader successfully (re-)locked?
BTW; It doesn't matter whether I use mfastboot or normal fastboot since both give me the same error messages. Both saying "(...) missing system.img" and/or "(...) sst lock failure". I just read that using mfastboot the error "(...) missing system.img" upon flashing a factory image via flash-all.bat would be solved.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\xxxxx>M:
M:\>cd M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase bo
ot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.030s]
finished. total time: 0.031s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase re
covery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.019s]
finished. total time: 0.020s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase sy
stem
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 1.138s]
finished. total time: 1.139s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase us
erdata
erasing 'userdata'...
OKAY [ 19.200s]
finished. total time: 19.203s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase ca
che
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.057s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash bo
otloader bootloader-shamu-moto-apq8084-71.10.img
target max-sparse-size: 256MB
sending 'bootloader' (3807 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.293s]
finished. total time: 0.423s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot reboot-b
ootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash ra
dio radio-shamu-d4.0-9625-02.101.img
target max-sparse-size: 256MB
sending 'radio' (85419 KB)...
OKAY [ 2.743s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.231s]
finished. total time: 3.977s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot reboot-b
ootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash bo
ot boot.img
target max-sparse-size: 256MB
sending 'boot' (7731 KB)...
OKAY [ 0.254s]
writing 'boot'...
OKAY [ 0.211s]
finished. total time: 0.470s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash re
covery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (8321 KB)...
OKAY [ 0.275s]
writing 'recovery'...
OKAY [ 0.115s]
finished. total time: 0.394s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash sy
stem system.img
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (259609 KB)...
OKAY [ 9.039s]
writing 'system'...
OKAY [ 3.280s]
sending sparse 'system' (262074 KB)...
OKAY [ 9.176s]
writing 'system'...
OKAY [ 3.457s]
sending sparse 'system' (258556 KB)...
OKAY [ 9.355s]
writing 'system'...
OKAY [ 3.674s]
sending sparse 'system' (252069 KB)...
OKAY [ 8.969s]
writing 'system'...
OKAY [ 3.227s]
sending sparse 'system' (257573 KB)...
OKAY [ 9.353s]
writing 'system'...
OKAY [ 4.308s]
sending sparse 'system' (258051 KB)...
OKAY [ 9.256s]
writing 'system'...
OKAY [ 3.577s]
sending sparse 'system' (189345 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 2.393s]
finished. total time: 85.806s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>fastboot flash cac
he cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.015s]
sending 'cache' (6248 KB)...
OKAY [ 0.209s]
writing 'cache'...
OKAY [ 0.100s]
finished. total time: 0.331s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>fastboot flash use
rdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.184s]
sending 'userdata' (138868 KB)...
OKAY [ 4.463s]
writing 'userdata'...
OKAY [ 1.983s]
finished. total time: 6.639s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\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
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>

Teamkang said:
True but it works. you can just put the orginal bootloader back if you want if it wont work.
Click to expand...
Click to collapse
This could also brick the device since no one knows where it comes from. Also for RMA it would have a bootlegged bootloader that may not pass RMA inspection. His problem has nothing to do with bootloader. There is nothing wrong with the stock bootloaders. I lock and unlock all the time. XDA is here to develop and teach. Although it does encompass hacks we prefer that they learn why it works and understand the repercussions. Blind downloading files is not a good idea unless don't mind bricks and spyware.
---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ----------
nitrous² said:
Still getting the same error message. Here's the full CMD log if you think I might have missed something. The only posts I could finde on the internet where the line "please run fastboot oem lock begin first" command is wirtten are related to the Moto X and some other Motorola devices. Have any of you guys had your bootloader successfully (re-)locked?
BTW; It doesn't matter whether I use mfastboot or normal fastboot since both give me the same error messages. Both saying "(...) missing system.img" and/or "(...) sst lock failure". I just read that using mfastboot the error "(...) missing system.img" upon flashing a factory image via flash-all.bat would be solved.
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
C:\Users\xxxxx>M:
M:\>cd M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase bo
ot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.030s]
finished. total time: 0.031s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase re
covery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.019s]
finished. total time: 0.020s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase sy
stem
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 1.138s]
finished. total time: 1.139s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase us
erdata
erasing 'userdata'...
OKAY [ 19.200s]
finished. total time: 19.203s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot erase ca
che
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.057s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash bo
otloader bootloader-shamu-moto-apq8084-71.10.img
target max-sparse-size: 256MB
sending 'bootloader' (3807 KB)...
OKAY [ 0.126s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.293s]
finished. total time: 0.423s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot reboot-b
ootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash ra
dio radio-shamu-d4.0-9625-02.101.img
target max-sparse-size: 256MB
sending 'radio' (85419 KB)...
OKAY [ 2.743s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.231s]
finished. total time: 3.977s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot reboot-b
ootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash bo
ot boot.img
target max-sparse-size: 256MB
sending 'boot' (7731 KB)...
OKAY [ 0.254s]
writing 'boot'...
OKAY [ 0.211s]
finished. total time: 0.470s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash re
covery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (8321 KB)...
OKAY [ 0.275s]
writing 'recovery'...
OKAY [ 0.115s]
finished. total time: 0.394s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>mfastboot flash sy
stem system.img
target max-sparse-size: 256MB
Sparse-Flash is enabled!
sending sparse 'system' (259609 KB)...
OKAY [ 9.039s]
writing 'system'...
OKAY [ 3.280s]
sending sparse 'system' (262074 KB)...
OKAY [ 9.176s]
writing 'system'...
OKAY [ 3.457s]
sending sparse 'system' (258556 KB)...
OKAY [ 9.355s]
writing 'system'...
OKAY [ 3.674s]
sending sparse 'system' (252069 KB)...
OKAY [ 8.969s]
writing 'system'...
OKAY [ 3.227s]
sending sparse 'system' (257573 KB)...
OKAY [ 9.353s]
writing 'system'...
OKAY [ 4.308s]
sending sparse 'system' (258051 KB)...
OKAY [ 9.256s]
writing 'system'...
OKAY [ 3.577s]
sending sparse 'system' (189345 KB)...
OKAY [ 6.716s]
writing 'system'...
OKAY [ 2.393s]
finished. total time: 85.806s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>fastboot flash cac
he cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.015s]
sending 'cache' (6248 KB)...
OKAY [ 0.209s]
writing 'cache'...
OKAY [ 0.100s]
finished. total time: 0.331s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>fastboot flash use
rdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.184s]
sending 'userdata' (138868 KB)...
OKAY [ 4.463s]
writing 'userdata'...
OKAY [ 1.983s]
finished. total time: 6.639s
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\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
M:\SHAMU\FACTORY IMAGE\LMY47z\shamu-lmy47z\image-shamu-lmy47z>
Click to expand...
Click to collapse
Did you unzip second folder in image to get get all the images. The flash all bat doesn't work. Never used mfastboot. No need for it. Looks like you trying full image. Need to unzip it all and use the single images.

prdog1 said:
This could also brick the device since no one knows where it comes from. Also for RMA it would have a bootlegged bootloader that may not pass RMA inspection. His problem has nothing to do with bootloader. There is nothing wrong with the stock bootloaders. I lock and unlock all the time. XDA is here to develop and teach. Although it does encompass hacks we prefer that they learn why it works and understand the repercussions. Blind downloading files is not a good idea unless don't mind bricks and spyware.
---------- Post added at 12:34 PM ---------- Previous post was at 12:31 PM ----------
Did you unzip second folder in image to get get all the images. The flash all bat doesn't work. Never used mfastboot. No need for it. Looks like you trying full image. Need to unzip it all and use the single images.
Click to expand...
Click to collapse
No, I actually unzipped the folder. As you can see in the CMD log, I flashed the content of said zip file (system.img/recovery.img/boot.img/userdata.img/cache.img) manually using both mfastboot and the commands you posted above. Rersult is the same. Also, this is shown in BL in "Bootloader Logs" (see attachment below).
Code:
cmd: oem lock
hab check failed for boot
failed to validate boot image

nitrous² said:
No, I actually unzipped the folder. As you can see in the CMD log, I flashed the content of said zip file (system.img/recovery.img/boot.img/userdata.img/cache.img) manually using both mfastboot and the commands you posted above. Rersult is the same. Also, this is shown in BL in "Bootloader Logs" (see attachment below).
Code:
cmd: oem lock
hab check failed for boot
failed to validate boot image
Click to expand...
Click to collapse
Looks like all flashes took. Did you boot the phone before trying to lock it.
---------- Post added at 12:49 PM ---------- Previous post was at 12:44 PM ----------
Also could have corrupted image with corrupt boot.img from download. Have seen that before. I had corrupt system.img before.

prdog1 said:
This could also brick the device since no one knows where it comes from. Also for RMA it would have a bootlegged bootloader that may not pass RMA inspection. His problem has nothing to do with bootloader. There is nothing wrong with the stock bootloaders. I lock and unlock all the time. XDA is here to develop and teach. Although it does encompass hacks we prefer that they learn why it works and understand the repercussions. Blind downloading files is not a good idea unless don't mind bricks and spyware.
True but its the best way to do it. also i don't think a bootloader can have a spyware in it. nor do i think it will brick.
Click to expand...
Click to collapse

Redownload the image or find a stock boot.img. That looks like the problem. Boot.img is corrupt in that download.
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Teamkang said:
prdog1 said:
This could also brick the device since no one knows where it comes from. Also for RMA it would have a bootlegged bootloader that may not pass RMA inspection. His problem has nothing to do with bootloader. There is nothing wrong with the stock bootloaders. I lock and unlock all the time. XDA is here to develop and teach. Although it does encompass hacks we prefer that they learn why it works and understand the repercussions. Blind downloading files is not a good idea unless don't mind bricks and spyware.
True but its the best way to do it. also i don't think a bootloader can have a spyware in it. nor do i think it will brick.
Click to expand...
Click to collapse
Best way to do it is the way it was designed to be done.
Click to expand...
Click to collapse

prdog1 said:
Redownload the image or find a stock boot.img. That looks like the problem. Boot.img is corrupt in that download.
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Teamkang said:
Best way to do it is the way it was designed to be done.
Click to expand...
Click to collapse
True. but im still helpful as i have a 5.1.1 shamu factory image laying around so OP won't have to download the whole image again.
Click to expand...
Click to collapse

nitrous² said:
Seriously, has anyone an idea why I can't relock my bootloader? I tried it as described in these methods posted above but no luck. I must be overlooking something. I'm not doing it for fun either; I have burn ins on its AMOLED panel and the earpiece doesn't work so I have to return it for RMA.
Also my post from another thread with further information:
@Mr_S have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message
Code:
...
(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
Code:
fastboot oem lock begin
first, then flash a factory image and end the process with
Code:
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
Code:
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.
Click to expand...
Click to collapse
Like prdog said try another 5.1.1 shamu boot.img i have this boot.img from eariler today that i can confirm works. as i flashed it 2 hours ago

prdog1 said:
Redownload the image or find a stock boot.img. That looks like the problem. Boot.img is corrupt in that download.
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Teamkang said:
Best way to do it is the way it was designed to be done.
Click to expand...
Click to collapse
Relock attempt after rebooting into android before bl lock command results in same error message.
Teamkang said:
prdog1 said:
Redownload the image or find a stock boot.img. That looks like the problem. Boot.img is corrupt in that download.
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
True. but im still helpful as i have a 5.1.1 shamu factory image laying around so OP won't have to download the whole image again.
Click to expand...
Click to collapse
I appreciate your efforts. 5.1.1 boot.img should be about 7,5-8MB. The one you posted has 3,7MB. What's the deal with that?
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Noob difficulty in flashing stock marshmallow

I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
Code:
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 4.620s
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.

spudbynight said:
I'm having some difficulty flashing Marshmallow onto my Nexus 6. It is the first time I am flashing a rom onto this.
I'm running Linux for this. (Mint 17.2) as I ran into trouble with Windows 10 and OSX El Capitan and recognising my device.
I've got the rom unpacked but when I go to flash with flash-all.sh I get an error.
It then dumps me back to the bootloader on the device. I did come across this thread from a while back.
http://forum.xda-developers.com/nexus-6/help/flash-factory-images-flashing-image-t2948624/page3
It hasn't resolved my problem. I've tried following the long method for installing the rom but it isn't working. I can't get the first stage to execute. I don't seem to actually have a file called bootloader.img anywhere. Is that the problem? Is it missing in this rom?
I'm perfectly happy to completely wipe the device. (It is only 3 days old) I just want to get the stock firmware up and running.
Click to expand...
Click to collapse
Looks like your fastboot binary is out of date. Did you get it from the latest sdk?

I've downloaded the SDK, but (yes, noob alert) I can't figure out how to actually install it.
I've downloaded fastboot from the terminal and it says I have the latest version.

OK - I installed the SDK. I followed the instructions here
When attempting to flash it seems to go a little bit further but is still failing.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.394s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.693s]
finished. total time: 1.087s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.084s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.555s]
finished. total time: 5.639s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.15
Baseband Version.....: D4.01-9625-05.27+FSG-9625-02.104
Serial Number........: ZX1G425T8L
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.003s]
sending 'boot' (8197 KB)...
OKAY [ 0.269s]
writing 'boot'...
OKAY [ 0.125s]
sending 'recovery' (8915 KB)...
OKAY [ 0.300s]
writing 'recovery'...
OKAY [ 0.133s]
sending 'system' (2043261 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.841s
From there I went into the "long way" and flashed the files individually from system.img
I selected recovery and rebooted. I got an Android with a red triangle but held power and volume up. The phone rebooted without me being asked to wipe data/factory reset.
Currently booted up and restoring. How do I check this is stable? I want to make sure I get OTA updates...

So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.

KnifeSkills said:
So the bootloader and radio worked, then it failed. Is this using the flash-all script?
I'd try extracting the contents of image-shamu-mra58k.zip and flashing each of them manually with fastboot. I've had trouble like that when using the flash-all script.
Click to expand...
Click to collapse
Sorry, I edited my post with an update...

This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?

spudbynight said:
This seems to be working OK now on Marshmallow.
How do I ensure I get OTA updates from here? Do I need to lock the bootloader again?
Click to expand...
Click to collapse
Nope. Just stay 100% stock. No root, no mods.

Cheers

i cant lock the bootloader of my nexus 6

hello i can't lock the bootloader of my nexus 6 since i received it from the technical service of motorola. before i send it to them it was closed and when i received it it was unlock and another no padlock its apear when is booting. ive traid every thing but nothing work
i can flash factory images but i cant relock it. fastboot oem lock works on my nexus 7 but not on my nexus 6

You should use the correct command, as google documents it.
But locking your bootloader is a pretty bad idea, and will prevent you from having any ability to fix anything if it fails to boot. If you cannot boot into android, you cannot enable unlock, and will be locked out for good with no recourse other then to send it in.
See this page
https://source.android.com/security/verifiedboot/verified-boot.html
Scroll down to "changing the device state" and use the given fastboot command.

i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem

alex482 said:
i want to lock it because motorola say to me if the bootloader is open there is no wanrranty so thats my problem
Click to expand...
Click to collapse
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.

istperson said:
If it boots you can lock it. If it doesn't boot, then they won't know either.
But if you lock it, and an OTA mucks it up, then you can send it to repair, and won't have a phone for weeks.
Click to expand...
Click to collapse
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly

alex482 said:
i dont know i was tried :
fastboot oem lock and fastboot flashing lock and its doesnt work
but on my nexus 7 its work perfectly
Click to expand...
Click to collapse
Do other adb/fastboot commands work?

What does
Code:
fastboot devices
say?

yes its work adb devices , adb reboot, adb reboot bootloader, fastboot flash...., fastboot devices , fastboot reboot and fastboot reboot-bootloader

istperson said:
What does
Code:
fastboot devices
say?
Click to expand...
Click to collapse
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot

C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.077s
that it what it say when i tried to lock it but i also tried to flash the factory image its work but then when i try to lock it the same massage appear again

Please paste here the output of flashing the factory image.

istperson said:
Please paste here the output of flashing the factory image.
Click to expand...
Click to collapse
yes when its finish i copy and past everything here

I'd be curious what specific error it gives with the fastboot flashing lock says, as that should be the command now assuming your on MM and using up to date SDK.

C:\Program Files (x86)\platform-tools>adb devices
List of devices attached
ZX1G423BMR device
C:\Program Files (x86)\platform-tools>adb reboot bootloader
C:\Program Files (x86)\platform-tools>fastboot devices
ZX1G423BMR fastboot
C:\Program Files (x86)\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Program Files (x86)\platform-tools>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
C:\Program Files (x86)\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.014s]
finished. total time: 0.016s
C:\Program Files (x86)\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.617s]
finished. total time: 0.617s
C:\Program Files (x86)\platform-tools> fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
target reported max download size of 536870912 bytes
sending 'bootloader' (10387 KB)...
OKAY [ 0.409s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.685s]
finished. total time: 1.102s
C:\Program Files (x86)\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
C:\Program Files (x86)\platform-tools>fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
target reported max download size of 536870912 bytes
sending 'radio' (115487 KB)...
OKAY [ 4.283s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.522s]
finished. total time: 5.808s
C:\Program Files (x86)\platform-tools>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\platform-tools>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 20.071s]
writing 'system'...
OKAY [ 6.964s]
sending sparse 'system' (515137 KB)...
OKAY [ 20.267s]
writing 'system'...
OKAY [ 7.088s]
sending sparse 'system' (518219 KB)...
OKAY [ 20.493s]
writing 'system'...
OKAY [ 7.188s]
sending sparse 'system' (492726 KB)...
OKAY [ 19.042s]
writing 'system'...
OKAY [ 6.804s]
finished. total time: 107.938s
C:\Program Files (x86)\platform-tools>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8197 KB)...
OKAY [ 0.316s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.431s
C:\Program Files (x86)\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8915 KB)...
OKAY [ 0.334s]
writing 'recovery'...
OKAY [ 0.126s]
finished. total time: 0.463s
C:\Program Files (x86)\platform-tools>fasboot flash cache cache.img
"fasboot" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.
C:\Program Files (x86)\platform-tools>fastboot flash cache cache.img
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.057s]
sending 'cache' (6248 KB)...
OKAY [ 0.237s]
writing 'cache'...
OKAY [ 0.137s]
finished. total time: 0.446s
C:\Program Files (x86)\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.349s]
finished. total time: 1.349s
C:\Program Files (x86)\platform-tools>fastboot flash userdata userdata.img
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.165s]
sending 'userdata' (138868 KB)...
OKAY [ 5.070s]
writing 'userdata'...
OKAY [ 3.001s]
finished. total time: 9.236s
C:\Program Files (x86)\platform-tools>fastboot oem lock
...
(bootloader) Please flash valid signed images firstly!
FAILED (remote failure)
finished. total time: 0.070s
C:\Program Files (x86)\platform-tools>fastboot reboot
rebooting...
finished. total time: -0.000s

yes im on 6.0 marshmallow and the sdk with the latest update

Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?

istperson said:
Just a couple of questions. If you go to Settings, is Developer mode off or on? If it's not on, please turn it on and check if Enable OEM unlocking is on or off.
But this as well can be an incompatible hardware error. Why did you send it for repairs?
Click to expand...
Click to collapse
yes its all turn on i send to it to change the rear camera because it was factory failure

Then it too must be a hardware problem.

do you think so?

alex482 said:
do you think so?
Click to expand...
Click to collapse
It seems, you did everything right. The line "(bootloader) Please flash valid signed images firstly!" is returned by the bootloader, and the bootloader is, opposite to adb and fastboot, closed source. So no help from the source.
I googled it, and it appeared on the Moto G 2014 device.

error getting device locked state No Response

anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.155s
< waiting for any device >
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: unknown
Serial Number........: 98011FFC4004AN
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'unknown'.
Update requires 'flame' or 'coral'.
fastboot: error: requirements not met!
Press any key to exit...

thatotherguy.. said:
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.036s]
Finished. Total time: 0.155s
< waiting for any device >
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: unknown
Serial Number........: 98011FFC4004AN
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' FAILED
Device product is 'unknown'.
Update requires 'flame' or 'coral'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse
Is this the first time this has happened?
Fastboot up to date?
Are you using power shell?
Tried USB A to USB C cables and different USB ports?
Did you extract the factory image and place all the contents in the platform-tools folder?
Device drivers are up to date?
Did you see your phone ID # when you typed in "fastboot devices"?

Badger50 said:
:
Click to expand...
Click to collapse
Is this the first time this has happened? someone was trying to flash stock before
Fastboot up to date? Yes it is, I just flashed another phone just fine before this one
Are you using power shell? no I am using cmd
Tried USB A to USB C cables and different USB ports? yes I have
Did you extract the factory image and place all the contents in the platform-tools folder? yes
Device drivers are up to date? yes they are
Did you see your phone ID # when you typed in "fastboot devices"? yes it show up, but it no picture show on screen even though the pc see it

thatotherguy.. said:
Is this the first time this has happened? someone was trying to flash stock before
Fastboot up to date? Yes it is, I just flashed another phone just fine before this one
Are you using power shell? no I am using cmd
Tried USB A to USB C cables and different USB ports? yes I have
Did you extract the factory image and place all the contents in the platform-tools folder? yes
Device drivers are up to date? yes they are
Did you see your phone ID # when you typed in "fastboot devices"? yes it show up, but it no picture show on screen even though the pc see it
Click to expand...
Click to collapse
Are you sure the bootloader is unlocked?

Badger50 said:
Are you sure the bootloader is unlocked?
Click to expand...
Click to collapse
I'm not 100% sure of that, the other phone they have it was unlocked. but this one doesn't show baseband as unknown

thatotherguy.. said:
anyone seen this before?
Sending 'bootloader_a' (8761 KB) OKAY [ 0.321s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state No Response')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.045s]
Finished. Total time: 0.053s
< waiting for any device >
Sending 'radio_a' (82676 KB) OKAY [ 2.098s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state No Response')
Click to expand...
Click to collapse
thatotherguy.. said:
I'm not 100% sure of that, the other phone they have it was unlocked. but this one doesn't show baseband as unknown
Click to expand...
Click to collapse
Judging from all the "getting device locked state" warnings your getting, I'd say it's still locked.

Badger50 said:
Judging from all the "getting device locked state" warnings your getting, I'd say it's still locked.
Click to expand...
Click to collapse
guessing pretty it done for?

thatotherguy.. said:
guessing pretty it done for?
Click to expand...
Click to collapse
Huh?? If you want to unlock it, make sure OEM unlocking and USB debugging is turned on in developer options. Then go back into fastboot mode and run..fastboot flashing unlock..
This WILL wipe your device :good:

Badger50 said:
Huh?? If you want to unlock it, make sure OEM unlocking and USB debugging is turned on in developer options. Then go back into fastboot mode and run..fastboot flashing unlock..
This WILL wipe your device :good:
Click to expand...
Click to collapse
I've tried unlocked bootloader, give same error
Sent from my Pixel 4 XL using Tapatalk

thatotherguy.. said:
I've tried unlocked bootloader, give same error
Click to expand...
Click to collapse
Then, maybe you have a carrier bootloader locked device??

Pixel 5 after OTA update can't start, stuck fastboot mode

My phone is no flash,no root, no USB debugging. Can't boot after OTA update today, stuck at Fastboot Mode, can't start. the error message is "failed to load/verify boot images"
I download Redfin from Factory Images for Nexus and Pixel Devices, run flash-all.bat, error message:
Code:
Sending 'bootloader_a' (8762 KB) OKAY [ 0.328s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (149796 KB) OKAY [ 3.886s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: r3-0.4-8351081
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 09
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.169s]
Checking 'version-bootloader' OKAY [ 0.178s]
Checking 'version-baseband' OKAY [ 0.139s]
Setting current slot to 'a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Press any key to exit...
I run:
[ICODE]# fastboot flashing unlock
FAILED (remote: 'Error getting device locked state Not Ready')
fastboot: error: Command failed[/ICODE]
fastboot boot boot.img
Sending 'boot.img' (98304 KB) OKAY [ 2.400s]
Booting FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
fastboot devices
09aaaaaaaaaa fastboot
please help me

Have you tried simply re-flashing?

Sewdohe said:
Have you tried simply re-flashing?
Click to expand...
Click to collapse
yes, but it can't open, He still remains in "Fastboot Mode" and cannot be started

Barbet is Pixel 5a.
Redfin is Pixel 5

andybones said:
Barbet is Pixel 5a.
Redfin is Pixel 5
Click to expand...
Click to collapse
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"

Evolv X said:
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Click to expand...
Click to collapse
Did using the correct file fix your problem?

NO, and I use Google Online, Bug can't
V0latyle said:
Did using the correct file fix your problem?
Click to expand...
Click to collapse

Evolv X said:
NO, and I use Google Online, Bug can't
Click to expand...
Click to collapse
Could you be a bit more detailed? I don't understand.

Same, I don't understand. It appears you're trying to flash for the wrong phone...

If your bootloader is locked, you cannot flash anything in fastboot/bootloader.
Try sideloading the OTA again.

Getting this issue...are you able to fix it?