Database Develop

4.4.2 Factory Images, the correct links

Someone at Google's mess the links. Here are the correct ones...
NEXUS 5 hammerhead:
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
NEXUS 7 2013 razor:
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
NEXUS 7 2013 razorg
https://dl.google.com/dl/android/aosp/razorg-kot49h-factory-49789b24.tgz
NEXUS 4 occam:
https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz
NEXUS 10 mantaray:
https://dl.google.com/dl/android/aosp/mantaray-kot49h-factory-174ba74f.tgz
NEXUS 7 2012 nakasi:
https://dl.google.com/dl/android/aosp/nakasi-kot49h-factory-5e9db5e1.tgz
NEXUS 7 2012 nakasig:
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz

How did u found the correct links?
btw, downloading, THANKS

C4SCA said:
How did u found the correct links?
btw, downloading, THANKS
Click to expand...
Click to collapse
The last 8 chars of the link really are the first 8 chars of the SHA-1 Checksum (that is correct).

You rock man! Thanks!

Does google release odex versions ?
Sent from my SM-N900T using Tapatalk

alleyezondisromo said:
Does google release odex versions ?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Yes, these images are odexed.

thanks [email protected]!!!!
flashing!

Thanks pal. really needed this.

Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!

Sfkn2 said:
Thanks! Was just about to flash my phone when I realized the links on Google's website doesn't work!
Click to expand...
Click to collapse
lol me too...I was all excited, then I realized I just get a 404 error. I actually thought they just hadn't finished uploading the images and jumped the gun posting links. Glad I saw this thread!!

Thank you. I downloaded Android SDK, copied the dll's and fastboot/adb from the platform-tools folder to C:\windows\syswow64\ and then extracted the occam-kot49h tgz and modified the flash-all.bat as to remove the "-w" (wipe) command from the fastboot update command and then I threw my phone into fastboot mode and opened up a command prompt and ran that flash-all.bat, upgraded from 4.4 to 4.4.2 seamlessly with no data loss. Of course I did lose root as expected and I suppose I should have removed/commented out the flashboot radio command line so I could have kept LTE, oh well I'll fix that later. Thanks again.

hi thanx for the links
after downloading i had this error:
Code:
[email protected]:~/occam-kot49h$ sudo sh flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.766s]
finished. total time: 0.869s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 2.128s]
writing 'radio'...
OKAY [ 2.805s]
finished. total time: 4.934s
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...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.98
Serial Number........: 0216337d9153f835
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.301s]
writing 'boot'...
OKAY [ 0.334s]
sending 'recovery' (6888 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.392s]
erasing 'system'...
OKAY [ 0.716s]
sending 'system' (713960 KB)...
OKAY [ 33.568s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 47.589s
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)

activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.

VivaErBetis said:
Are you using the latest SDK? That error usually means that the version of the fatsboot command isn't one liked by the bootloader.
Click to expand...
Click to collapse
ok i will download the "SDK Tools Only" package, thats all what i need right?

activexda said:
ok i will download the "SDK Tools Only" package, thats all what i need right?
Click to expand...
Click to collapse
Yes, and inside it the latest “platform tools“.

VivaErBetis said:
Yes, and inside it the latest “platform tools“.
Click to expand...
Click to collapse
ok, after trying with latest sdk i still have the same problem
is there anybody managed to install the factory image?

Maybe you messed up the script.

gm007 said:
Maybe you messed up the script.
Click to expand...
Click to collapse
i don't think so
script:
Code:
#!/bin/sh
# Copyright 2012 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
fastboot flash bootloader bootloader-mako-makoz30d.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img
fastboot reboot-bootloader
sleep 5
fastboot update image-occam-kot49h.zip

Maybe download the file again.

activexda said:
i need some help
(BTW i executed the flash-all.sh script after deleting the "-w" option and deleting userdata.img)
Click to expand...
Click to collapse
gm007 said:
Maybe download the file again.
Click to expand...
Click to collapse
I would definitely download the file again. Did you check the MD5 sum?

LMY47O 5.1 Factory Image now up at Google's site!

Direct download link:
https://dl.google.com/dl/android/aosp/occam-lmy47o-factory-cae68e81.tgz
md5sum: 293a98009cfbcb5d398c05302a86ee8c
sha1sum: cae68e81d5a1758f92b77520f829400da205111f
Goggle's Factory Images page:
https://developers.google.com/android/nexus/images

Tip for those upgrading without flashing via factory image. After you flash cache.img boot into your custom recovery of choice and wipe the cache partition. Otherwise you're going to be stuck on the lollipop circles for a long time. This is specific to nexus 4.
Sent from my Nexus 7 using Tapatalk

How can i root it ?

Virtxer said:
How can i root it ?
Click to expand...
Click to collapse
You're kidding right?

Yep

Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app

Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Hi there, long time no see
I was gonna do a flashable version but my pc was acting up again so i'll see if I can do it tomorrow after work if someone else doesn't do it by then :good:

does only me have problem with - remote partition table doesn't exist,when try to install twrp,or this is a comon isue?
i install stock image(unzip it with 7z),install with flash all. everything pass ok. when i turn on usb debuging and try to install twrp with fastboot i get this error.
i try to install stock image manuallu with fastboot. in that case i must to do a factory resset when boot,or phone will stuck with boot. also this pass ok,but fasboot cant install only twrp. old version,new,same error. fastboot recognize nexus,commands working,

Zehlek said:
Hopefully someone will make a flashable stock rom based off of the images
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I'm using the latest Simple AOSP for Nexus 4 (Android 5.1.0), which was built today, with the LMY47O binary file, no random reboot so far.
Here is everything you need: http://chromloop.com/2015/04/how-to-install-android-5-1-lollipop-custom-rom-nexus-4/

5.0.1 (LRX22C) factory to 5.1.0 (LMY47O) factory
My bootloader was already un-locked. Hold the volume down key and hit the power button to power on the phone into fastboot mode.
Windows 7
Front USB 2.0 ports
7-zip
[TOOL]Updated ADB (version 1.0.32) and Fastboot [16-OCT-14]
http://forum.xda-developers.com/htc-one/general/tool-updated-adb-version-1-0-32-fastboot-t2932160
extract - fastboot_adb(1.0.32)_071114_r21.rar
extract - occam-lmy47o-factory-cae68e81.tgz
extract - occam-lmy47o-factory-cae68e81.tar
Move all of the files into the fastboot_adb(1.0.32)_071114_r21 folder.
Open the folder. Hold down the shift key and right click. Click on "open command windows here"
type in: flash-all.bat or fl and hit the tab key.
FAIL:
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>flash-all.bat
< waiting for device >
sending 'bootloader' (2264 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
OKAY [ 0.281s]
finished. total time: 0.374s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.560s]
writing 'radio'...
OKAY [ 2.480s]
finished. total time: 4.040s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 854497332 bytes
error: update package missing system.img
Press any key to exit...
Extract image-occam-lmy47o.zip into the fastboot_adb(1.0.32)_071114_r21 folder.
Run the following commands.
There is no need to update the bootloader and modem. You can see on the screen the current bootloader and modem build were updates from the last step.
Commands found via http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img ***took apx 8 mins before seeing anything being written to the screen and phone.***
fastboot flash boot boot.img
fastboot flash recovery recovery.img *** don't do this if you have TWRP installed ***
fastboot format cache
fastboot reboot
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.234s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash system system.img
erasing 'system'...
OKAY [ 0.827s]
sending 'system' (834470 KB)...
OKAY [ 50.747s]
writing 'system'...
OKAY [ 46.519s]
finished. total time: 98.140s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash boot boot.img
sending 'boot' (6394 KB)...
OKAY [ 0.250s]
writing 'boot'...
OKAY [ 0.374s]
finished. total time: 0.624s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery recovery.img
sending 'recovery' (6956 KB)...
OKAY [ 0.265s]
writing 'recovery'...
OKAY [ 0.374s]
finished. total time: 0.640s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot format cache
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
erasing 'cache'...
OKAY [ 0.078s]
sending 'cache' (10984 KB)...
OKAY [ 0.437s]
writing 'cache'...
OKAY [ 0.608s]
finished. total time: 1.139s
C:\Users\test\Desktop\fastboot_adb(1.0.32)_071114_r21>fastboot reboot
rebooting...
finished. total time: -0.000s
It took apx 11 mins to boot up. It was optimizing the 100+ apps. All my apps and config settings were there.
Optional....
I powered off and when back into fastboot mode to flash TWRP so I can create a backup image.
http://dl.twrp.me/mako/
fastboot flash recovery twrp-2.8.6.0-mako.img
Use the arrow keys to reboot into recovery mode to boot into TWRP. Do not boot into the system.

Ok, managed to get my laptop working again. Rom is uploading, will post a link to the thread when done :good:
EDIT: Thread link: http://forum.xda-developers.com/nexus-4/development/rom-stock-flashable-rom-t3084656

If you get ANY Errors during Updating via the flash-all script - try to update ADB itself. I was using an old version and got errors until i downloaded and used a new ADB version.

Where is the 5.1.1?

Mirkoitalia said:
Where is the 5.1.1?
Click to expand...
Click to collapse
I don't know. When did you see it last?

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
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.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
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.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

Working Root for ze550kl

Hello Guys,
Now it s finally here
working root for ze550kl, a very big thanks to @shakalaca,
he developed this, full credit goes to him. :fingers-crossed:
Version 1.13.40.496
original thread source
http:// www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=111151&extra=page=1
Steps to Root
1- Download the full version of firmware patch:
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
2- Descompress system.img.7z with 7zip program
3- Copy the boot.img / system.img / recovery.img to (adb/fastboot) folder.
4- Execute this commands in sequence:
-adb device
-adb reboot bootloader
-fastboot devices
-fastboot erase userdata
-fastboot erase cache
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash system system.img
-fastboot reboot
system will take some time to ready, if stuck at asus splash screen, restart in recovery, wipe cache, format data partition, restart mobile.
install any super user you wish.
Enjoy,
 @shakalaca thanks again
Tried adaway working well.

HOLY!!! Thank you very much

thanks to @shakalaca
and you for information
http://zenfonlaser.blogspot.in/
How to Root ASUS Zenfone 2 Laser ZE550KL/Z00LD
How to Flash:
turn on usb debugging in mobile
connect your mobile to pc
after detecting your mobile in pc discconect it
All files link:
https://drive.google.com/folderview?id=0B_j7tYFbJZThclhsZnRPOEFUWXc
Download Flashtool and Extract it to a folder
Download system.img move it to Flashtool folder
( download all parts then put inside one folder then use 7zip software to extract system.img by opening system.img.7z.001 )
Download recovery.img and move it to Flashtool folder
Download boot.img and move it to Flashtool folder
1) now enter in to fast boot mode
methode 1: Turn Off Zenfone 2 Laser and Enter fastboot Mode (Power+Volume up)
methode 2: go to recovery and there enter boot loader mode
methode 3: by adb shell
Connect Zenfone 2 Laser with PC/Laptop
At Flashtool/fastboot folder press shift+Right Click then Open Command Here
-adb device
-adb reboot bootloader
if use methode 1 or 2 Connect Zenfone 2 Laser with PC/Laptop
At Flashtool/fastboot folder press shift+Right Click then Open Command Here
2) Enter this command:
fastboot flash boot boot.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24545 KB)...
OKAY [ 0.828s]
writing 'boot'...
OKAY [ 0.625s]
finished. total time: 1.453s
3) Enter this command:
fastboot flash recovery recovery.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (26507 KB)...
OKAY [ 0.891s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.453s
4) Enter this command:
fastboot flash system system.img
u will see in cmd window:
G:\asus\FlashTools>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 6.953s]
sending sparse 'system' (259338 KB)...
OKAY [ 13.109s]
writing 'system'...
OKAY [ 5.765s]
sending sparse 'system' (257277 KB)...
OKAY [ 13.093s]
writing 'system'...
OKAY [ 5.625s]
sending sparse 'system' (257278 KB)...
OKAY [ 12.843s]
writing 'system'...
OKAY [ 5.781s]
sending sparse 'system' (257277 KB)...
OKAY [ 12.906s]
writing 'system'...
OKAY [ 5.656s]
sending sparse 'system' (262102 KB)...
OKAY [ 13.312s]
writing 'system'...
OKAY [ 6.312s]
sending sparse 'system' (257122 KB)...
OKAY [ 13.390s]
writing 'system'...
OKAY [ 6.625s]
sending sparse 'system' (260005 KB)...
OKAY [ 13.171s]
writing 'system'...
OKAY [ 7.218s]
sending sparse 'system' (252193 KB)...
OKAY [ 12.390s]
writing 'system'...
OKAY [ 5.734s]
sending sparse 'system' (258041 KB)...
OKAY [ 12.859s]
writing 'system'...
OKAY [ 6.156s]
sending sparse 'system' (258041 KB)...
OKAY [ 12.953s]
writing 'system'...
OKAY [ 5.937s]
sending sparse 'system' (261502 KB)...
OKAY [ 13.187s]
writing 'system'...
OKAY [ 6.593s]
sending sparse 'system' (139273 KB)...
OKAY [ 7.109s]
writing 'system'...
OKAY [ 3.890s]
finished. total time: 653.488s
5) Enter this command:
fastboot oem reboot-recovery
u will see in cmd window:
G:\asus\FlashTools>fastboot oem reboot-recovery
...
OKAY [ 0.016s]
finished. total time: 0.016s
6) Wipe data/factory reset from recovery menu
use volume key for up and down
and power key for select press yes in second menu
now reboot form recovery menu
Done your Zenfone 2 Laser is Rooted.

Thank you again.. it's working and this is my feedback

How big is the patch??
---------- Post added at 01:03 PM ---------- Previous post was at 12:53 PM ----------
Btw the original image is for zenfone selfie. Will it work on 550KL

caldent said:
How big is the patch??
---------- Post added at 01:03 PM ---------- Previous post was at 12:53 PM ----------
Btw the original image is for zenfone selfie. Will it work on 550KL
Click to expand...
Click to collapse
No, this is not for selfie, this is for ze550kl.
build nos of zenfone laser and selfie are different.
This one based on latest version of zenfone laser ze550kl.

Thank you @rajiki for the news and thx to @shakalaca ....will tey this soon
Sent from my ASUS_Z00LD using Tapatalk

Superb work
I am new to Zenfone laser Ze550kl. I have two queries below
1.We need to unlock Boot-loader to execute this?
2.and this is void warranty?
Thanks for your work.

eugineprakash said:
I am new to Zenfone laser Ze550kl. I have two queries below
1.We need to unlock Boot-loader to execute this?
2.and this is void warranty?
Thanks for your work.
Click to expand...
Click to collapse
You don't need to unlock the bootloader and I'm not sure about warranty but it is usually safe to assume that you will void your warranty.
The good thing is that you can always reflash the stock rom and that should return it to factory condition but can't guarantee your warranty won['t be voided. Someone else might be able to confirm for sure.

when you flash stock firmware that will re-flash everything & your warranty would not be void.

Hey Buddy, I am in Big Trouble this time. While Flashing System.img file, i am getting the following error
Command - fastboot flash system system.img
error - cannot load system.img
Can you tell me what's the issue here? or can you provide me your Fastboot ADB Zip file will be great helpful
waiting for your answer

ArshArora said:
Hey Buddy, I am in Big Trouble this time. While Flashing System.img file, i am getting the following error
Command - fastboot flash system system.img
error - cannot load system.img
Can you tell me what's the issue here? or can you provide me your Fastboot ADB Zip file will be great helpful
waiting for your answer
Click to expand...
Click to collapse
Just wait & let command got completed,it will take some times as file too big to send.
it will sparse & send in parts, whole process will complete around 15 minute.

rajlko said:
Just wait & let command got completed,it will take some times as file too big to send.
it will sparse & send in parts, whole process will complete around 15 minute.
Click to expand...
Click to collapse
command is not starting at all. just showing error like screenshot i attached

what is the size of image size, did you extract file correctly ?
actual size of system image is 2.84 GB (3,05,09,60,328 bytes).
other commands executed or not ?

ArshArora said:
command is not starting at all. just showing error like screenshot i attached
View attachment 3524359
Click to expand...
Click to collapse
go in the extracted folder where system.img.7z.001-006 file is. click on anyone of these six files and decompress with 7-zip file manager.
now u will get a single file SYSTEM.img of about 2.4 gb. put this system.img in the adb and fastboot folder.
now flash the system.
happened the same with me a few hours ago.

I experienced that same error on that system.img and solved it by
1st: Not using administrative cmd C:\Users\(pcname)> on cmd
2nd: I just put those 3 files on C:\Users\(pc name)\
only recovery and boot img work when on adb folder.. dunno if it's on windows 10 but I got it working on above directory

just xposed needed now
can we flash xposed zip file in stock recovery?via adb or any other way?
though there is some method of flashing xposed framework without recovery which we used on 551 ML..via adb only..
anyone shed some light on this?

sausuke said:
I experienced that same error on that system.img and solved it by
1st: Not using administrative cmd C:\Users\(pcname)> on cmd
2nd: I just put those 3 files on C:\Users\(pc name)\
only recovery and boot img work when on adb folder.. dunno if it's on windows 10 but I got it working on above directory
Click to expand...
Click to collapse
Awesome dude ! that worked for me finally

ArshArora said:
Awesome dude ! that worked for me finally
Click to expand...
Click to collapse
glad that worked... I hate that system.img problem

followed all guide. Finally the system error was solved and it got flashed . Now the phone is stucked on Asus logo and below bufferring type symbol is going on from past 15 mins. I removed battery and inserted it and pressed power button + vol up continuously still it directly goes to fastboot boot. No options of normal boot or recovery option please help.

Device Locked in fastboot even with unlocked bootloader

Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.

ahsank128 said:
Hi,
I was trying to reflash everything on my phone and wipe. When I boot into fastboot and run fastboot -w, I get an error saying Download is not allowed on locked device. Im using platform tools 29.05.
Click to expand...
Click to collapse
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?

Mackay53 said:
Does the bootloader screen show unlocked?
Have you tried to run the flashing unlock again?
Click to expand...
Click to collapse
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image

ahsank128 said:
Okay, so I locked the bootloader, and unlocked it again. Successfully flashed. But I am geting the following message
"Erase successful, but not automatically formatting. File system type raw not supported"
I cant run the fastboot format (partition) command. I am on latest platform tools and latest factory image
Click to expand...
Click to collapse
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?

Badger50 said:
Does your phone boot up? If so, I would check to see if your still getting good recognition from your pc. What does adb devices show when you enter that with your phone in transfer data mode?
Click to expand...
Click to collapse
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked

ahsank128 said:
Yes, the factory image gets flashed, but now everything seems to be on partition B as opposed to A. I believe everything was going to A when I first got the phone and did the unlock. ADB working fine, managed to root the phone. i enter ADB devices and shows serial. I can boot to fastboot. I wanted to see what would happen if I run fastboot flashing unlock again, and it said device is unlocked
Click to expand...
Click to collapse
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:

Badger50 said:
Well, then I guess all is well for you again. Just FYI going forward, when you fastboot the factory image without the -w, it only flashes to your active slot, whereas, if you leave the -w, it'll flash to both slots, but wipe your device. This is why when I update the factory images every month without the -w, I manually change slots so I get a full flash to both slots. Many think this is overkill, however, I have never had any wonky problems for the last 2+ years with my P2XL, and now my P4XL by using this methodology :good:
Click to expand...
Click to collapse
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol

ahsank128 said:
Right, but the thing is I left the -w in the bat file. Even so it only flashed to b, saying device is locked. I think there is some internal issue going. Im the same guy who cant get the blackenedmod script to run properly lol
Click to expand...
Click to collapse
I know who you are? At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?

Badger50 said:
I know who you are At least your up and running again. But yeah, sounds like your internals might be a little wonky for sure. ?
Click to expand...
Click to collapse
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10

ahsank128 said:
Any idea on the best way to completely wipe the internals and flash again? This would be easy with TWRP or custom recovery, but we've some time before that is made for Android10
Click to expand...
Click to collapse
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:

Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Will attempt this, my attempt last night was to do factory reset within the settings (when phone is booted up) and then flashed with -w. But I will try again using the stock recovery. I even changed computers, this stuff is wonky sometimes

Badger50 said:
Personally, I would factory reset from stock recovery, and then fastboot the factory image with the -w included. In essence, wiping everything twice :good:
Click to expand...
Click to collapse
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)

DELETED

ahsank128 said:
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Click to expand...
Click to collapse
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes

ahsank128 said:
Code:
C:\Users\akhan37\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 5.477s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.203s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 6.178s
Also, hitting adb reboot fastboot takes to to fastbootd screen but I can't flash there (where I get the message can't write to locked device), but I can use flash-all bat from the bootloader screen.
Code:
Sending 'bootloader_b' (8761 KB) OKAY [ 0.349s]
Writing 'bootloader_b' (bootloader) Flashing Pack version c2f2-0.2-5940465
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_b
(bootloader) Flashing partition xbl_config_b
(bootloader) Flashing partition aop_b
(bootloader) Flashing partition tz_b
(bootloader) Flashing partition hyp_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition keymaster_b
(bootloader) Flashing partition devcfg_b
(bootloader) Flashing partition qupfw_b
(bootloader) Flashing partition uefisecapp_b
(bootloader) Flashing partition msadp_b
(bootloader) Flashing partition logfs
OKAY [ 0.435s]
Finished. Total time: 1.046s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
Sending 'radio_b' (82676 KB)
Click to expand...
Click to collapse
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.

Badger50 said:
Interesting. Just a simple experiment if your willing. Go into your platform-tools, and just double click the flash-all.bat file and see if you get the same result, or if it even initializes
Click to expand...
Click to collapse
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
Code:
Sending 'bootloader' (8761 KB) OKAY [ 0.218s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_b' (82676 KB) OKAY [ 2.180s]
Writing 'radio_b' (bootloader) Flashing Pack version SSD:g8150-00041-191016-B-5945070
(bootloader) Flashing partition modem_b
OKAY [ 0.650s]
Finished. Total time: 3.090s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
--------------------------------------------
Bootloader Version...: c2f2-0.2-5940465
Baseband Version.....: g8150-00041-191016-B-5945070
Serial Number........: 99171FFAZ006J5
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.069s]
Checking 'version-bootloader' OKAY [ 0.069s]
Checking 'version-baseband' OKAY [ 0.068s]
Setting current slot to 'b' OKAY [ 0.077s]
extracting boot.img (64 MB) to disk... took 0.387s
archive does not contain 'boot.sig'
Sending 'boot_b' (65536 KB) OKAY [ 2.139s]
Writing 'boot_b' OKAY [ 0.455s]
extracting dtbo.img (8 MB) to disk... took 0.025s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB) OKAY [ 0.310s]
Writing 'dtbo_b' OKAY [ 0.117s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (8 KB) OKAY [ 0.138s]
Writing 'vbmeta_b' OKAY [ 0.072s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.101s]
Writing 'vbmeta_system_b' OKAY [ 0.072s]
archive does not contain 'vendor_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.069s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.006s]
Resizing 'product_b' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.005s]
Resizing 'vendor_a' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
extracting product.img (2127 MB) to disk... took 15.801s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.005s]
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?

bb709394 said:
If you have done a factory reset, you also need to make sure you enable "oem unlocking" in Developer options and usb debugging before you do anything else. Flashing a factory stock image which includes the '-w' in your flash-all.bat file would come afterwards.
I am assuming you are not flashing any kernals on top? Check to make sure you are flashing the correct image, Nov and December had 3 different images each month.
Click to expand...
Click to collapse
No, this issue happens on stock kernel. And yes USB debugging and OEM Unlock both are checked. I believe the image is correct. US Unlocked Pixel from google store. file ends in 011

ahsank128 said:
Wont work from home screen (this is fine? should be in fastboot)
Looks like it flashed this time from the fastbootd screen (so damn strange)
from fastbootd screen:
and got stuck there
One more thing: When on stock boot image, OEM Unlock frozen on bootloader already unlock. But after flashing magsik, I can switch between allow and not allow. This is normal?
Click to expand...
Click to collapse
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?

Badger50 said:
Yes, it only works in fastboot mode.
I don't think it's strange at all. I've never come across the..fastboot -w..command that you were using, which is why I suggested what I did.
Sometimes it takes a while for the script to finish. You might no have been stuck per-se, but just not patient enough. December was a big update, so it takes a little longer.
Yes, this is normal for OEM unlocking while rooted.
So...are you up and running now?
Click to expand...
Click to collapse
I am up and running, I'll check to see if I can get that script running later on

ahsank128 said:
I am up and running, I'll check to see if I can get that script running later on
Click to expand...
Click to collapse
Kinda sounds like you already got the script to work