Database Users

Flash help. Image won't load

To say the least, I got into more than I really wanted to. I have a Motorola droid razr m model XT907. It's rooted and GSM unlocked. I'm using it on Straight Talk currently. I'm pretty sure the bootloader's unlocked. Anyway, I tried to do a full restore from TBU. Granted, I probably did it wrong. When finished, it seemed like everything error-ed with it telling me that app or service has stopped working. So, I tried to reset back to factory. It would never finish booting. I tried to restore with the same result. There's no backup or anything on the SD card. Since then I've been trying to flash a new rom in it. I used House of Moto. It seemed the simplest way. After a lot of confusion, I finally figured out how to do it, maybe. I downloaded the correct files and arranged them according to the instructions. When I run it, it seems to do fine until the end, then it says it couldn't load the image file. So now I have an operating system that can't finish booting because it has nothing inside. Here's the log from House of Moto:
Please ensure your phone is:
o] Charged
o] Connected to USB using your OEM cable
o] USB drivers are installed
o] Booted to AP Fastboot mode: [power off, hold volume down and press power]
Ready to flash...
Press any key to continue . . .
Flashing: FULL_xt907.bat
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
1 file(s) copied.
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.014s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.296s
sending 'sbl1' (100 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.562s]
finished. total time: 0.581s
sending 'sbl2' (126 KB)...
OKAY [ 0.020s]
writing 'sbl2'...
OKAY [ 1.308s]
finished. total time: 1.330s
sending 'sbl3' (512 KB)...
OKAY [ 0.050s]
writing 'sbl3'...
OKAY [ 1.315s]
finished. total time: 1.365s
sending 'rpm' (140 KB)...
OKAY [ 0.066s]
writing 'rpm'...
OKAY [ 0.569s]
finished. total time: 0.638s
sending 'tz' (192 KB)...
OKAY [ 0.025s]
writing 'tz'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.319s
sending 'aboot' (256 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 1.429s]
finished. total time: 1.461s
sending 'modem' (30720 KB)...
OKAY [ 2.311s]
writing 'modem'...
OKAY [ 2.793s]
sending 'modem' (17576 KB)...
OKAY [ 5.446s]
writing 'modem'...
OKAY [ 4.869s]
finished. total time: 15.423s
sending 'fsg' (2794 KB)...
OKAY [ 0.221s]
writing 'fsg'...
OKAY [ 2.268s]
finished. total time: 2.491s
erasing 'modemst1'...
OKAY [ 0.931s]
finished. total time: 0.932s
erasing 'modemst2'...
OKAY [ 1.319s]
finished. total time: 1.320s
sending 'logo' (1709 KB)...
OKAY [ 0.140s]
writing 'logo'...
OKAY [ 2.580s]
finished. total time: 2.720s
sending 'devtree' (512 KB)...
OKAY [ 0.049s]
writing 'devtree'...
OKAY [ 1.196s]
finished. total time: 1.248s
sending 'boot' (10240 KB)...
OKAY [ 1.148s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 1.458s
sending 'recovery' (10240 KB)...
OKAY [ 0.778s]
writing 'recovery'...
OKAY [ 3.790s]
finished. total time: 4.570s
sending 'cdrom' (30720 KB)...
OKAY [ 2.587s]
writing 'cdrom'...
OKAY [ 4.473s]
sending 'cdrom' (22538 KB)...
OKAY [ 6.005s]
writing 'cdrom'...
OKAY [ 7.602s]
finished. total time: 20.671s
error: cannot load 'system.img.ext4'
erasing 'cache'...
OKAY [ 2.697s]
finished. total time: 2.698s
erasing 'userdata'...
OKAY [ 2.843s]
finished. total time: 2.844s
erasing 'tombstones'...
OKAY [ 1.698s]
finished. total time: 1.699s
rebooting...
finished. total time: 0.009s
Press any key to continue . . .
I tried the last two firmwares on this list. I have Android 4.1.2 installed. (Or at lease I did)
I used the fastboot scripts and rsd scripts from here
I don't know what I'm doing. I hope somebody can tell me what part is wrong. Help! I need my phone back.

Boot in to fast boot menu... Power device off then power on while holding all three buttons...volume up + volume down + power... Please provide the information listed on screen... Boot loader status..fast boot menu version and date...
Sent from my XT907 using xda app-developers app

:AP fastboot info
Here ya go:
AP Fastboot Flash Mode (S)
10.98(*) (sha-1e9f577, 2012-10-21 17:10:35)
EMMC Info: Size 8GB
I think I read it right, but here's a pic

Try this...http://forum.xda-developers.com/showthread.php?t=2249773 option one... Then make sure you unlock the boot loader before any update or you won't be able to later
Sent from my XT907 using xda app-developers app

Alright I'm ready to go for it, but the first thing I saw was "DO NOT USE THIS UTILITY ON THE LATEST 4.1.2 OTA UPDATE". Are they talking about my Android version, or the 98.18.78 update?

Update .78/.3... The version on your device is older then the one it flashes
Sent from my XT907 using xda app-developers app

That worked perfectly. All I have to do now is root it, unlock the bootloader and GSM again. I'll take the latest OTA when I finish that.
I can't thank you enough

Happy it worked for you...
Sent from my XT907 using xda app-developers app

I have a custom rom for this phone that's been debloated. Can I just swap the system image and XML document in the razr utility and flash it like I just did?

system.img fails to send/flash.

Manually flashing a a stock rom as the flashall.bat freaks out and this is what happens,.
sending 'boot' (5898 KB)...
OKAY [ 0.922s]
writing 'boot'...
OKAY [ 0.297s]
finished. total time: 1.219s
sending 'recovery' (6398 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.609s
sending 'userdata' (98413 KB)...
OKAY [ 3.864s]
writing 'userdata'...
OKAY [ 5.012s]
finished. total time: 8.876s
sending 'system' (523357 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 420.405s

Have you tried to change USB ports/ cables?

Bouncer5 said:
Manually flashing a a stock rom as the flashall.bat freaks out and this is what happens,.
sending 'boot' (5898 KB)...
OKAY [ 0.922s]
writing 'boot'...
OKAY [ 0.297s]
finished. total time: 1.219s
sending 'recovery' (6398 KB)...
OKAY [ 1.250s]
writing 'recovery'...
OKAY [ 0.359s]
finished. total time: 1.609s
sending 'userdata' (98413 KB)...
OKAY [ 3.864s]
writing 'userdata'...
OKAY [ 5.012s]
finished. total time: 8.876s
sending 'system' (523357 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 420.405s
Click to expand...
Click to collapse
Have you tried just flashing the system.img on its own? Is it just me, or does that system image seem excessively large for a stock image? I would try a new cable, and maybe try redownloading the system img just in case.

ariesgodofwar said:
Have you tried just flashing the system.img on its own? Is it just me, or does that system image seem excessively large for a stock image? I would try a new cable, and maybe try redownloading the system img just in case.
Click to expand...
Click to collapse
Yea it is quite large, I have tried flashing the system.img on its own, It also eventually times out. I have also tried different system.img files. I have tried different USB cables, different USB ports, heck last night I even tried a different computer and OS! Still always fails.
At this point the only thing I was able to do with my phone was get Ubuntu Touch on it so it is just slightly more useful than a paperweight.

With Ubuntu Touch I have managed to get Cyanogenmod.zip onto the phone reflash the recovery and install the .zip I am now back on android, I cannot however get back to a stock image.

Help! soft brick while upgrading to update 3.0

TLDR/update: false alarm, after a pc reboot. and leaving the shield unplugged for a few min. i was able to "adb reboot bootloader" then reflash with fastboot, all good now. mods feel free to delete this bs...
i downloaded the official 3.0 recovery image from nvidia and commented out the bit to flash there recovery so i could keep twrp just like i have previously w/o issues. now im stuck and cant seem to access the bootloader by holding the power button, adb, or fastboot. what other options do i have? flashing from update.zip on sd card?
Code:
./flash-all.sh
< waiting for any device >
target reported max download size of 67108864 bytes
sending 'staging' (3091 KB)...
OKAY [ 0.091s]
writing 'staging'...
OKAY [ 0.152s]
finished. total time: 0.243s
target reported max download size of 67108864 bytes
sending 'boot' (21772 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 1.024s]
finished. total time: 1.551s
rebooting...
finished. total time: 0.059s
< waiting for any device >
sending 'system' (1578475 KB)...
FAILED (command write failed (Protocol error))
finished. total time: 0.000s
target reported max download size of 67108864 bytes
erasing 'vendor'...
OKAY [ 0.164s]
sending sparse 'vendor' (65498 KB)...
OKAY [ 1.606s]
writing 'vendor'...
OKAY [ 3.285s]
sending sparse 'vendor' (65472 KB)...
OKAY [ 1.582s]
writing 'vendor'...
OKAY [ 2.895s]
sending sparse 'vendor' (65532 KB)...
OKAY [ 1.611s]
writing 'vendor'...
OKAY [ 3.437s]
sending sparse 'vendor' (48152 KB)...
OKAY [ 1.196s]
writing 'vendor'...
OKAY [ 2.448s]
finished. total time: 18.223s
rebooting...
if it didnt sent the reboot command i could have seen the error and hopefully fixed it. guess i gave nvidia too much credit for error detection in there script.

P8 Lite ALE-L21 bootloop or dead

Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?

as far as i can see,you have flashed system.img and he work,now try again to flash via adb only system.img,wen is done,run command fastboot reboot an remove usb cable from phone and press and hold on volume button up to enter in recovery mod,once in recovery wipe data factory reset and wipe cache,it wiil delete all your memory phone,but it my work,so good luck

Hello Cristi,
Thank you for reply, i will try to flash only with system.img and then reboot.
Then I'll come back with the result.
There any other method to flash full memory ? (e.g. with SP_Flash_Tool ) Delete all data and then complete installation with full fw?

Bad News,
After I flash adb only with system.img and then reboot, push volume + & power, only light red light flashing slower.
Is possible that the bottom Volume UP, may not work

Do you have a NAND backup through TWRP?
What FW are you trying to flash?
What happened so that it shows this?

Try to flash with other version ... try to flash with b170

@ - Hello oziboy;
I don`t have a backup and i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common));
I don`t know the history .... the device has got to me so broken
@ - Hello VladHD;
i will try , thk for info.

Hi....
try first to flash with fastboot firmware b049 or b052,
when finished flashing then factory reset and wipe....
then local update 171 or 170....

ingerul_danutz said:
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
Click to expand...
Click to collapse
you can try here http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977

I did get another motherboard, and now the phone is total functional.

K
Sent from my ALE-L21 using XDA-Developers mobile app

ingerul_danutz said:
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
Click to expand...
Click to collapse
My p8lite phone also soft bricked can you tell how did you unlocked your boot loader?

I use this method:
- Open Huawei Product ID Generator, then complete:
Product Model: U8815,
Product IMEI: imei from sim1;
and now you have Product ID generated;
now, Connect your phone via data cable to PC;
Switch it off and then by pressing volume down and power together make it in fastboot mode (in this mode you will see "Phone locked" in green color at bottom of screen)
- enter https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail login with ID facebook or create an account; and then complete with:
Product Model: U8815 - like Huawei Product ID Generator;
Product Serial Number: 16 characters ; will be found on the box of device or type command "fastboot devices", when you connect the phone in fastboot mode (volume down + power botton);
Product IMEI: imei from sim1 ;
Product ID: the code generated from Huawei Product ID Generator program;
Verification code: characters from picture;
and then submit; if everything is OK, the code will be generated;
type command: "fastboot oem unlock **************** "
where ************** is code generated on emui.huawei.com;
Good luck

ingerul_danutz said:
I did get another motherboard, and now the phone is total functional.
Click to expand...
Click to collapse
Where did you buy new motherboard?

8.1 Developer Preview released

Download: https://developer.android.com/preview/download.html
Credit to @skaforey for the scoop over at the Pixel2 XL forum, and at this point just about every other android tech site.

Interesting change to the navigation bar. Looks like they're trying to reduce the burn in problem people are getting.

Does this use visualcore

It keeps telling me I don't have any eligible devices.. as I type this on my fully stock Pixel 2.
Edit: I'm now able to enroll!

TLDR; Make sure you update your fastboot first!
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!

pvillegeek said:
TLDR; Make sure you update your fastboot first!
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Download the factory and flash-all.bat?

Chronzy said:
Download the factory and flash-all.bat?
Click to expand...
Click to collapse
I tried that. It appeared to flash correctly, but didn't help.
Code:
platform-tools>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.125s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00049000
(bootloader) Updating: cmnlib @0008D000 sz=00038000
(bootloader) Updating: devcfg @000C5000 sz=0000F000
(bootloader) Updating: hyp @000D4000 sz=00040000
(bootloader) Updating: keymaster @00114000 sz=00046000
(bootloader) Updating: lockbooter @0015A000 sz=00016000
(bootloader) Updating: pmic @00170000 sz=0000D000
(bootloader) Updating: rpm @0017D000 sz=0003A000
(bootloader) Updating: tz @001B7000 sz=001DB000
(bootloader) Updating: xbl @00392000 sz=003A2000
(bootloader) Updating: apdp @00734000 sz=00004000
(bootloader) Updating: msadp @00738000 sz=00004000
(bootloader) Updating: hosd @0073C000 sz=01E31000
(bootloader) Updating: abl @0256D000 sz=00065000
OKAY [ 1.016s]
finished. total time: 1.141s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 0.172s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.547s]
finished. total time: 0.734s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 57071874048
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13933563
Block groups: 426
Reserved block group size: 1024
Created filesystem with 11/3489792 inodes and 265112/13933563 blocks
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA79C1A05734
--------------------------------------------
checking product...
OKAY [ 0.016s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot_a' (32768 KB)...
OKAY [ 0.109s]
writing 'boot_a'...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.188s]
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 2.219s]
writing 'system_a' 1/4...
OKAY [ 4.782s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 2.109s]
writing 'system_a' 2/4...
OKAY [ 4.813s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 2.219s]
writing 'system_a' 3/4...
OKAY [ 4.798s]
sending sparse 'system_a' 4/4 (322300 KB)...
OKAY [ 1.328s]
writing 'system_a' 4/4...
OKAY [ 2.954s]
erasing 'system_b'...
OKAY [ 0.203s]
sending sparse 'system_b' 1/2 (524284 KB)...
OKAY [ 2.188s]
writing 'system_b' 1/2...
OKAY [ 4.798s]
sending sparse 'system_b' 2/2 (80600 KB)...
OKAY [ 0.359s]
writing 'system_b' 2/2...
OKAY [ 0.750s]
erasing 'vendor_a'...
OKAY [ 0.188s]
sending 'vendor_a' (346964 KB)...
OKAY [ 1.062s]
writing 'vendor_a'...
OKAY [ 3.188s]
Setting current slot to 'a'...
OKAY [ 0.031s]
erasing 'userdata'...
OKAY [ 0.750s]
sending 'userdata' (140906 KB)...
OKAY [ 0.438s]
writing 'userdata'...
OKAY [ 1.516s]
rebooting...
finished. total time: 41.536s
Press any key to exit...

pvillegeek said:
I tried that. It appeared to flash correctly, but didn't help.
Click to expand...
Click to collapse
Read up over at the 2XL forum: https://forum.xda-developers.com/pixel-2-xl/how-to/8-1-developer-images-available-t3694556/page3
Some talk about having to extract and flash files individually. Maybe that'll help. I've had to do that on devices in the past.

dude, beware flashing this, thought I bricked my device, had to manually flash everything.... wtf google

I'm waiting for the OTA tomorrow. Looking forward to the colored nav bar and fading buttons! It's nice to see Google taking action on something rather than having to enable an accessibility service for a 3rd party app to color the navigation bar, and the fading buttons are a nice touch.

Chronzy said:
Read up over at the 2XL forum: https://forum.xda-developers.com/pixel-2-xl/how-to/8-1-developer-images-available-t3694556/page3
Some talk about having to extract and flash files individually. Maybe that'll help. I've had to do that on devices in the past.
Click to expand...
Click to collapse
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.

pvillegeek said:
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
Click to expand...
Click to collapse
Wow, that's quite the hook up. Do you have the insurance?

Has anyone noticed a difference in the HDR+ processing speed or something like that? (preliminary Pixel core was enabled with this 8.1 DP1)
www.androidpolice.com/2017/10/26/an...ual-core-chip-now-enabled-developers-can-use/

Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.

quakeaz said:
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
Click to expand...
Click to collapse
Also waiting here.

pvillegeek said:
Thanks, I tried that, but still no luck. I ended up contacting google support and they are sending a replacement.
Click to expand...
Click to collapse
You fastboot flashing unlock_critcal? I doubt it's bricked.
Sent from my Nexus 6 using Tapatalk

quakeaz said:
Who's received the update via OTA after signing up for the beta? I'm still waiting here on my Pixel 2.
Click to expand...
Click to collapse
Still waiting...

The developer preview from Pixel 2 is at moment down, I think they make changes.
Gesendet von meinem Pixel 2 mit Tapatalk

How stable are the developer previews, in general?

cb474 said:
How stable are the developer previews, in general?
Click to expand...
Click to collapse
In general they are rather stable, but there are exceptions.
As to any particular phone, you can wait a couple of days and see if there are many reports of problems.
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
Does anyone have the direct link to the OTA they are pushing out?
See https://forum.xda-developers.com/showpost.php?p=74307421&postcount=88 for the link for the Pixel 2 XL.