Database Info

[Q] Droid Razr HD XT926 won't boot, different flash errors.

I was given a droid razr hd (xt926). Guy said he took an update and when the phone rebooted, it wouldn't go past the M boot screen. I don't know what build he was on and I don't know the previous status of the phone (root, rom, unlock, etc)
I can access AP Fastboot but I can't access anything else (Recovery, BP Tools, Factory).
I am using a Team Black Hat Cable, the most recent Motorola_End_User_Driver_Installation_6.4.0_32bit Driver, and a Windows 7 computer (my best computer is at ASUS getting fixed).
AP Fastboot Reads:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 03:15:48)
eMMC Info: Size 16GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
usb connected
______________________________________________________________________________
I first tried RSD Lite (using both 6.1.4 and 6.2.4 to flash VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I got:
Code:
Failed flashing process. 1/17 flash partition "gpt.bin" -> phone return FAIL
Trying VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml I had to delete the "getvar" line for it to begin BUT I also get the "gpt.bin" failed message here. If I delete steps in XML (get.bin, sbl1, sbl2, sbl3, etc) the process just gets hung up and fails on the next step
______________________________________________________________________________
Trying the most recent Matt's Utility, Mr.Parkinson's Utility, and SamuriHL's House of Moto (trying each build listed above) I get significant failed messages which I will post below.
Code:
Ready to flash...
Press any key to continue . . .
Flashing: UNIVERSAL.bat
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (127 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.250s
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.218s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.218s
sending 'modem' (30720 KB)...
OKAY [ 2.371s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.434s
sending 'fsg' (165 KB)...
OKAY [ 0.031s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.094s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
sending 'logo' (854 KB)...
OKAY [ 0.078s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.140s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.451s
______________________________________________________________________________
Trying to manually mfastboot in cmd, I get similar errors. I tried boot.img first and got this error
Code:
mfastboot.exe flash boot boot.img
sending 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED <remote failure>
finished. total time: 1.451s
Flashing gpt.bin partition
Code:
mfastboot flash partition gpt.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.250s
Is the phone FUBAR or does anyone have a suggestion how I could fix this?

Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.

eckdawg5 said:
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, just by looking at your screen shots, I can tell you it's hard bricked.
Sent from my VS985 4G

Problems with moto g3 downgrade marshmellow to lollipop

OK I HAVE A MOTO G3 , SKU=XT1541 , VER=P2B , BUILD MP.124.107.55 , SYS VERS=24.61.55OSPREY
It is an unlocked euro version with 1gb ram , i.e not locked to any carrier or ever has been.
I was able to unlock the bootloader , I then followed very carefully the instructions on this site to get the image , usb drivers and everthing required.
However once ono entering the commands at the dos window to start flashing a new rom it comes back with an error , I think I have the incorrect image or there is not one on this site.
I am a complete nuubie can anyone help me please.

D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin

some progress
robin red said:
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.417s
D:\XT1541_OSPREY_RETEU_5.1.1_LPI23.72-66_cid7_subsidy-DEFAULT_CFC.xml>
I get this after entering fastboot flash partition gpt.bin
Click to expand...
Click to collapse
ok I managed to get to the part when I load the sparse files 0-5 , it send them all but reports failure on them all every other command on the list executes correctly.
After this it locked for a while a rebooted in version 6 marshmellow.!!!!! well I guess I am learning.
Anyone any ideas , guess I am lucky I did not brick the thing.

here is what I am getting after entering the third command
C:\Users\Robin L\Desktop\roby>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ -0.000s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.470s

[HELP] Relock Moto G 2015 (XT1540 2GB) Bootloader

Hi there, i unlocked the bootloader of my Moto G 2015 XT1540 to play with it and install custom ROMs, but now i want to relock it because i want to gift it to my mother.
I've tried several tutorials about it but it fails. (I used XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9 firmware from the index on XDA).
Code:
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.027s]
finished. total time: 0.027s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot oem fb_mode_set
...
OKAY [ 0.007s]
finished. total time: 0.007s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.049s]
writing 'logo'...
OKAY [ 0.051s]
finished. total time: 0.107s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.524s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.060s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.527s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.068s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (251797 KB)...
OKAY [ 7.901s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.355s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (257238 KB)...
OKAY [ 8.073s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.112s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.223s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.266s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (262140 KB)...
OKAY [ 8.227s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.302s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (262142 KB)...
OKAY [ 8.238s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.278s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (255933 KB)...
OKAY [ 8.030s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.070s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (112244 KB)...
OKAY [ 3.525s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.555s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36984 KB)...
OKAY [ 1.170s]
writing 'modem'...
OKAY [ 0.562s]
finished. total time: 1.739s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.020s]
finished. total time: 0.024s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.015s]
finished. total time: 0.019s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2159 KB)...
OKAY [ 0.077s]
writing 'fsg'...
OKAY [ 0.059s]
finished. total time: 0.140s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.019s]
finished. total time: 0.024s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.081s]
finished. total time: 0.085s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot erase customize
erasing 'customize'...
OKAY [ 0.018s]
finished. total time: 0.022s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.028s]
finished. total time: 0.032s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot oem fb_mode_clear
...
OKAY [ 0.006s]
finished. total time: 0.011s
C:\Users\victo\Downloads\adb-fastboot-latest_win_linux>fastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.033s]
finished. total time: 0.037s
Thanks in advance

geminis3 said:
Hi there, i unlocked the bootloader of my Moto G 2015 XT1540 to play with it and install custom ROMs, but now i want to relock it because i want to gift it to my mother.
I've tried several tutorials about it but it fails. (I used XT1540_OSPREY_RETUS_2GB_6.0_MPI24.65-25.1_cid9 firmware from the index on XDA).
Thanks in advance
Click to expand...
Click to collapse
The build you're flashing is older than the one that's installed on the phone. That's why you are getting the 'preflash validation failure' message.
Also, I don't see the need to lock the bootloader even if you are giving it to someone else. Just flash the stock firmware. Skip the bootloader and gpt files, flash everything else.

Actually, you are doing this completely wrong... You don't mix oem commands (lock begin and fb_mode_set are exclusive of each other, at least I have never seen a guide that uses them together, so it's deduction), but that isn't your core problem... @adityak1303 hit on that, you are getting "preflash validation errors" which generally means the pieces you are flashing are older than is what is installed. Very common actually since we do not have the latest factory images currently. The kicker here is although you can likely get it functional again, you can't lock the bootloader without being able to flash each piece of a complete ROM image, which you can't do without having a newer image, meaning ALL pieces, you must flash gpt.bin and bootloader, and every piece to relock.
Why the urge to relock? You know it will never go back to the way it was, you will still have to use the modified logo.bin to cover the unlock warning page (that never goes away) and the bootloader and getvar will always show it has been unlocked... There is no point except pure security to relock the bootloader, but you will still know it was once unlocked.

Thanks for your help, I flashed stock ROM (without gpt.bin and bootloader.bin), custom logo.bin and yep it works also I got the January OTA.

Require some help and some advice if possible.

Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
C:\adb>fastboot oem fb_mode_set
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.172s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.319s
C:\adb>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.172s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.687s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.891s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.664s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.883s
C:\adb>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (257278 KB)...
OKAY [ 9.982s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.097s
C:\adb>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (258607 KB)...
OKAY [ 10.125s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.157s
C:\adb>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (258384 KB)...
OKAY [ 10.076s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.107s
C:\adb>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (252313 KB)...
OKAY [ 9.973s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.004s
C:\adb>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (254404 KB)...
OKAY [ 10.017s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.064s
C:\adb>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (258060 KB)...
OKAY [ 10.114s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 10.161s
C:\adb>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (76857 KB)...
OKAY [ 3.038s]
writing 'modem'...
OKAY [ 2.036s]
finished. total time: 5.075s
C:\adb>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adb>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (1864 KB)...
OKAY [ 0.100s]
writing 'fsg'...
OKAY [ 0.109s]
finished. total time: 0.210s
C:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot erase customize
erasing 'customize'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
Click to expand...
Click to collapse

Phatzy said:
Hi There,
I hope someone can advise and possibly provide help resolving this problem.
The Moto G4 XT1622 is not able to boot to OS, It only boots into bootloader, cannot go into recovery and cannot go into Factory Mode etc.
The error i get on the phone is....
"Start Up Failed"
Failed to verify hab image boot
Failed to verify boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
I have tried to clear fb_mode and tried to unlock the bootloader without success.
I have tried various stock roms to get this fixed. The phone has never been unlocked and not been rooted.
Click to expand...
Click to collapse
It looks to me like you're trying to flash a firmware that is a downgrade from what was already on the device. It's probably blocking you because it won't allow a downgrade. Flash the version that the device already had on it or flash a newer version.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks

Phatzy said:
I throught that would be the case but i have tried the 4 roms available for this device and even the 7.0 OTA rom but nothing if able to flash. I cannot even unlock the bootloader.
Thanks
Click to expand...
Click to collapse
You may have to faatboot flash the individual .img(boot, system, cache, recovery, etc..) files by themselves.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Yeah I tried that too. I just get the same errors as this.....
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.094s
Click to expand...
Click to collapse

Phatzy said:
Yeah I tried that too. I just get the same errors as this.....
Click to expand...
Click to collapse
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Hi,
I dont think so as I cannot check due to the phone not able to get pass bootloader. I tried to use the fb_mode command but still goes back to bootloader saying filed to start.
Thanks..
Droidriven said:
Do you have USB debugging enabled?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse

Bricked Pixel 2 help

Hi
Hope you are all doing great, I have limited experience from rooting my own phones, any help will be appreciated a lot.
After buying a pixel 2 (walleye/google store unlocked ) I wanted to root it like my other phones so I proceeded to unlock bootloader, temp boot twrp and installed magisk.
So far it was fine but gave me a notification that android has an internal error. So I decided to go back to stock and retry rooting. Flashed to stock was great. Set the phone up again, did not root it or anything from stock. When re-enabling the developer options & USB debugging I unfortunately locked boot loader up again.
The phone is stuck at bootloader ERROR: Slot Unbootable: Load Error, going to recovery it goes back to same.
Can't flash cos status locked, cant unlock .
Fastboot FAIL not allowed in locked state.
Download mode Error: Operation denied
Interestingly boot-slot is b, tried to change it , of course not allowed.
getvar all dump below, its what I could extract. Let me know if I can get you more info by running logging etc. that I can.
(bootloader) avb_err:0(0)
(bootloader) is_avb_critical_error:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.
(bootloader) version-main:
(bootloader) imei:
(bootloader) boot-mode:FASTBOOT
(bootloader) logical-block-size:0x1000
(bootloader) erase-block-size:0x1000000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3759
(bootloader) version-baseband:g8998-00202-1803121407
(bootloader) version-bootloader:mw8998-002.0069.00
(bootloader) variant:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xD49BFB000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x1F400000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x1F400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xA0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xA0000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:dtbo:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:1
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:6
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
(bootloader) cid:00000000
(bootloader) secure:yes
(bootloader) serialno:
(bootloader) hw-revision:MP1
(bootloader) product:walleye
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
all:

try flashing factory image again.

munchy_cool said:
try flashing factory image again.
Click to expand...
Click to collapse
Hi munchy_cool, first things first , thank you so much for taking out time to reply
I tried flashing stock again, I rechecked if I flashed the right stock (sometimes that is a problem)
----------------------------------------------------------
Sending 'bootloader_b' (38652 KB) OKAY [ 1.055s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.075s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.007s
Sending 'radio_b' (60412 KB) OKAY [ 1.657s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.672s
rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.007s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: mw8998-002.0069.00
Baseband Version.....: g8998-00202-1803121407
Serial Number........: XXXXXX
--------------------------------------------
Checking product OKAY [ 0.006s]
Checking version-bootloader FAILED
Device version-bootloader is 'mw8998-002.0069.00'.
Update requires 'mw8998-002.0067.00'.
fastboot: error: requirements not met!
Press any key to exit...
--------------------------------------------------------------
Then I tried with --slot to try to change it to a , no luck.
I rechecked the radio img and the bootimage but no luck

Try deuces script instead of stock script.
Worked for me

mrorange2108 said:
Try deuces script instead of stock script.
Worked for me
Click to expand...
Click to collapse
HI mrorange
thanks for your suggestion, I looked at deuces script, it does mention its for unlocked bootloader. Ran it anyway, all of it fails with FAILED (remote: Flashing is not allowed in Lock State) Rest of it is below. Any other suggestion that might help would be great.
--------------------------------------------------------------------
Deuces-flash-all-script-V4.5-Windows
for Taimen or Walleye - Google Pixel 2 / XL
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Unlock Bootloader[Y/N]?y
Running Unlock
Look at your device,
press up arrow and Power to confirm
FAILED (status read failed (Too many links))
Finished. Total time: 13.234s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: unknown command)
Finished. Total time: 0.004s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
it is safe to ignore errors about active partition - there are multiple entries to support multiple versions of platform tools
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.013s
Sending 'bootloader_b' (38728 KB) OKAY [ 1.071s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.106s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Sending 'radio_b' (60428 KB) OKAY [ 1.661s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.678s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'bootloader_b' (38728 KB) OKAY [ 1.059s]
Writing 'bootloader_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.078s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Sending 'radio_b' (60428 KB) OKAY [ 1.657s]
Writing 'radio_b' FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 1.678s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'abl_a' (404 KB) OKAY [ 0.027s]
Writing 'abl_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.048s
fastboot: error: cannot load 'aes.img': No such file or directory
Sending 'apdp_a' (16 KB) OKAY [ 0.016s]
Writing 'apdp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.033s
Sending 'boot_a' (32768 KB) OKAY [ 0.909s]
Writing 'boot_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.929s
Sending 'cmnlib_a' (224 KB) OKAY [ 0.015s]
Writing 'cmnlib_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.035s
Sending 'cmnlib64_a' (292 KB) OKAY [ 0.025s]
Writing 'cmnlib64_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.045s
Sending 'devcfg_a' (60 KB) OKAY [ 0.015s]
Writing 'devcfg_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.037s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.228s]
Writing 'dtbo_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.248s
Sending 'hyp_a' (256 KB) OKAY [ 0.016s]
Writing 'hyp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.036s
Sending 'keymaster_a' (280 KB) OKAY [ 0.019s]
Writing 'keymaster_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.040s
fastboot: error: cannot load 'laf.img': No such file or directory
Sending 'modem_a' (60420 KB) OKAY [ 1.640s]
Writing 'modem_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.658s
Sending 'msadp_a' (16 KB) OKAY [ 0.016s]
Writing 'msadp_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'pmic_a' (52 KB) OKAY [ 0.009s]
Writing 'pmic_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.029s
Sending 'rpm_a' (232 KB) OKAY [ 0.016s]
Writing 'rpm_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'tz_a' (1900 KB) OKAY [ 0.066s]
Writing 'tz_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.085s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.014s]
Writing 'vbmeta_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.034s
Sending 'vendor_a' (346964 KB) OKAY [ 9.482s]
Writing 'vendor_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 9.503s
Sending 'xbl_a' (3720 KB) OKAY [ 0.114s]
Writing 'xbl_a' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.136s
Flashing System A
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 16.225s]
Writing sparse 'system_a' 1/4 FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 29.095s
Flashing System B
Sending sparse 'system_b' 1/2 (524284 KB) OKAY [ 16.205s]
Writing sparse 'system_b' 1/2 FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 19.821s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Sending 'abl_b' (404 KB) OKAY [ 0.026s]
Writing 'abl_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.046s
fastboot: error: cannot load 'aes.img': No such file or directory
Sending 'apdp_b' (16 KB) OKAY [ 0.006s]
Writing 'apdp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.026s
Sending 'boot_b' (32768 KB) OKAY [ 0.901s]
Writing 'boot_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.921s
Sending 'cmnlib_b' (224 KB) OKAY [ 0.019s]
Writing 'cmnlib_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.039s
Sending 'cmnlib64_b' (292 KB) OKAY [ 0.021s]
Writing 'cmnlib64_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.041s
Sending 'devcfg_b' (60 KB) OKAY [ 0.011s]
Writing 'devcfg_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.030s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.233s]
Writing 'dtbo_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.252s
Sending 'hyp_b' (256 KB) OKAY [ 0.015s]
Writing 'hyp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.038s
Sending 'keymaster_b' (280 KB) OKAY [ 0.019s]
Writing 'keymaster_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.041s
fastboot: error: cannot load 'laf.img': No such file or directory
Sending 'modem_b' (60420 KB) OKAY [ 1.639s]
Writing 'modem_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 1.659s
Sending 'msadp_b' (16 KB) OKAY [ 0.013s]
Writing 'msadp_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.034s
Sending 'pmic_b' (52 KB) OKAY [ 0.010s]
Writing 'pmic_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.029s
Sending 'rpm_b' (232 KB) OKAY [ 0.017s]
Writing 'rpm_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.037s
Sending 'tz_b' (1900 KB) OKAY [ 0.063s]
Writing 'tz_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.085s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.011s]
Writing 'vbmeta_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.031s
Sending 'vendor_b' (346964 KB) OKAY [ 9.583s]
Writing 'vendor_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 9.604s
Sending 'xbl_b' (3720 KB) OKAY [ 0.109s]
Writing 'xbl_b' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.132s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' FAILED (remote: Slot Change is not allowed in Lock State
)
Finished. Total time: 0.012s
Format Userdata[Y/N]?y
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 13933563 4k blocks and 3489792 inodes
Filesystem UUID: XXXXXXX
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4497 KB) OKAY [ 0.138s]
Writing 'userdata' FAILED (remote: Flashing is not allowed in Lock State)
Finished. Total time: 0.656s

NoobHelp said:
HI mrorange
thanks for your suggestion, I looked at deuces script, it does mention its for unlocked bootloader. Ran it anyway, all of it fails with FAILED (remote: Flashing is not allowed in Lock State) Rest of it is below. Any other suggestion that might help would be great.
Click to expand...
Click to collapse
Surely there is a way to fix this? My getvar returned nearly identical information, except that my slots were all successful.
Did you have any luck with this or know anyone that has?
Thanks,
Alex