Bricked Pixel 2 help - Google Pixel 2 Questions & Answers

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

Related

[Q] Universal Linux Toolkit v2.1.0 error

hi, I tried to root my nexus 7, and all ok, but when I tried to exec flash google factory image, I've the following output
Downloading Factory Image...
--2013-01-24 02:07:53-- URL rejected
Resolving dl.google.com (dl.google.com)... 74.125.225.238, 74.125.225.224, 74.125.225.230, ...
Connecting to dl.google.com (dl.google.com)|74.125.225.238|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 291197311 (278M) [application/x-tar]
Saving to: `factory.tgz'
100%[===================================================================================>] 291.197.311 365K/s in 16m 6s
2013-01-24 02:24:00 (294 KB/s) - `factory.tgz' saved [291197311/291197311]
< waiting for device >
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.128s]
finished. total time: 0.129s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.238s]
finished. total time: 0.238s
erasing 'recovery'...
OKAY [ 0.136s]
finished. total time: 0.137s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.217s]
finished. total time: 0.218s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 3.612s]
finished. total time: 3.612s
sending 'bootloader' (2096 KB)...
OKAY [ 0.280s]
writing 'bootloader'...
OKAY [ 1.952s]
finished. total time: 2.232s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
sending 'radio' (16384 KB)...
OKAY [ 2.071s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.086s
rebooting into bootloader...
OKAY [ 4.012s]
finished. total time: 4.012s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 488804800 bytes
error: update package missing system.img
Press ENTER to return to the main menu...
I tred using another USB port, and cable, moving the app to another folder and re-run, but I've the same output.
This is awfull cause I can't boot my nexus, only re-flashing the recovery, I can boot it, but the O.S. not. My nexus is dead, what I can do?
My, OS, is Linux Mint Nadia

Flashing Nexus S

Hi
Can I flash stock i9020 rom on Korean variant m200 ?
I want remove unwanted korean apps in it..can I do it ?
Dwars said:
Hi
Can I flash stock i9020 rom on Korean variant m200 ?
I want remove unwanted korean apps in it..can I do it ?
Click to expand...
Click to collapse
You can find the stock (factory image) firmware here.
Using the method in this guide, you can flash the image easily. Please be sure to download the latest image for m200 (sojuk, 4.1.1 (JRO03E) and not other Nexus S variants. Also, the guide is not for m200 but the procedure followed is same, so do not forget to replace the file names while performing the flashing process. :good:
help
can any one help me in flashing a custom rom to my nexus s m200... i have rooted my phone with unlock root.. runing jellybean 4.1.1 (official rom).. please explain me step by step..
ishan.ranatunga said:
can any one help me in flashing a custom rom to my nexus s m200... i have rooted my phone with unlock root.. runing jellybean 4.1.1 (official rom).. please explain me step by step..
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2034264
DJBhardwaj said:
You can find the stock (factory image) firmware here.
Using the method in this guide, you can flash the image easily. Please be sure to download the latest image for m200 (sojuk, 4.1.1 (JRO03E) and not other Nexus S variants. Also, the guide is not for m200 but the procedure followed is same, so do not forget to replace the file names while performing the flashing process. :good:
Click to expand...
Click to collapse
tried this method and files but when writing system.img showing failed.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.094s]
finished. total time: 2.094s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.031s]
finished. total time: 0.031s
C:\ADBFAST>fastboot erase system
erasing 'system'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
error: cannot load 'bootloader-crespo-i9020xxlc2.img'
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.250s]
writing 'bootloader'... OKAY [ 0.359s]
finished. total time: 0.609s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020uclh1.img
sending 'radio' (12288 KB)... OKAY [ 1.938s]
writing 'radio'... OKAY [ 1.844s]
finished. total time: 3.781s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot -w update image-sojua-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020UCLH1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.672s]
writing 'boot'... OKAY [ 0.547s]
sending 'recovery' (4308 KB)... OKAY [ 0.719s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337599 KB)... OKAY [ 54.859s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 57.422s
and when tried with 2nd file. now not able to erase userdata and system and at end system writing failed too.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.141s]
finished. total time: 2.141s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.031s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... FAILED (remote: Erase Fail)
finished. total time: 0.000s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.266s]
writing 'bootloader'... OKAY [ 0.375s]
finished. total time: 0.641s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020xxki1.img
sending 'radio' (12288 KB)... OKAY [ 1.922s]
writing 'radio'... OKAY [ 1.750s]
finished. total time: 3.672s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot -w update image-soju-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.641s]
writing 'boot'... OKAY [ 0.563s]
sending 'recovery' (4308 KB)... OKAY [ 0.734s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337443 KB)... OKAY [ 55.547s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 58.141s
my nexus info
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
all:
help me what is going wrong?
gsm city said:
tried this method and files but when writing system.img showing failed.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.094s]
finished. total time: 2.094s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.031s]
finished. total time: 0.031s
C:\ADBFAST>fastboot erase system
erasing 'system'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
error: cannot load 'bootloader-crespo-i9020xxlc2.img'
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.250s]
writing 'bootloader'... OKAY [ 0.359s]
finished. total time: 0.609s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020uclh1.img
sending 'radio' (12288 KB)... OKAY [ 1.938s]
writing 'radio'... OKAY [ 1.844s]
finished. total time: 3.781s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot -w update image-sojua-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020UCLH1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.672s]
writing 'boot'... OKAY [ 0.547s]
sending 'recovery' (4308 KB)... OKAY [ 0.719s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337599 KB)... OKAY [ 54.859s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 57.422s
and when tried with 2nd file. now not able to erase userdata and system and at end system writing failed too.
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.141s]
finished. total time: 2.141s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot erase system
erasing 'system'... FAILED (remote: Erase Fail)
finished. total time: 0.031s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... FAILED (remote: Erase Fail)
finished. total time: 0.000s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.266s]
writing 'bootloader'... OKAY [ 0.375s]
finished. total time: 0.641s
C:\ADBFAST>fastboot flash radio radio-crespo-i9020xxki1.img
sending 'radio' (12288 KB)... OKAY [ 1.922s]
writing 'radio'... OKAY [ 1.750s]
finished. total time: 3.672s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADBFAST>fastboot -w update image-soju-jzo54k.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: I9020XXKI1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.000s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.641s]
writing 'boot'... OKAY [ 0.563s]
sending 'recovery' (4308 KB)... OKAY [ 0.734s]
writing 'recovery'... OKAY [ 0.609s]
sending 'system' (337443 KB)... OKAY [ 55.547s]
writing 'system'... FAILED (remote: Write Fail)
finished. total time: 58.141s
my nexus info
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
all:
help me what is going wrong?
Click to expand...
Click to collapse
Let me know the exact model number of your Nexus S?
I902OT, I92023, I9020A, M200, D720?
DJBhardwaj said:
Let me know the exact model number of your Nexus S?
I902OT, I92023, I9020A, M200, D720?
Click to expand...
Click to collapse
SHW-M200K (under battery)
and fastboot mode:
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
gsm city said:
SHW-M200K (under battery)
and fastboot mode:
Code:
INFOproduct: herring
INFOserialno: 3531430F809D00EC
INFOversion-hardware: REV 11
INFOversion-baseband: I9020XXKI1
INFOversion-bootloader: I9020XXLC2
INFOsecure: yes
INFOunlocked: yes
INFOoff-mode-charge: 1
Click to expand...
Click to collapse
So, which factory image are you using exactly?
DJBhardwaj said:
So, which factory image are you using exactly?
Click to expand...
Click to collapse
sojua-jzo54k-factory-1121b619
soju-jzo54k-factory-36602333
both tried
http://www.droidviews.com/nexus-s-guide-flash-android-4-1-2-jzo54k-factory-image/
gsm city said:
sojua-jzo54k-factory-1121b619
soju-jzo54k-factory-36602333
both tried
http://www.droidviews.com/nexus-s-guide-flash-android-4-1-2-jzo54k-factory-image/
Click to expand...
Click to collapse
Seems like you have the Korean variant. Go for m200 - sojuk
sorry for previous (i am trying a wrong img for my cell)
now i am trying with 4.1.1 sojuk-jro03e-factory-93a21b70
now downloaded from below link (sojuk for Nexus S (Korea version, m200)
https://developers.google.com/android/nexus/images#mysidspr
but still same problem.
important isue:
when trying to erase system and userdata.........process failed every time.
i think therefore this failed to writing system.img
Code:
C:\ADBFAST>fastboot devices
3531430F809D00EC fastboot
C:\ADBFAST>fastboot erase boot
erasing 'boot'... OKAY [ 0.031s]
finished. total time: 0.031s
C:\ADBFAST>fastboot erase cache
erasing 'cache'... OKAY [ 2.109s]
finished. total time: 2.109s
C:\ADBFAST>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADBFAST>fastboot erase system
erasing 'system'... [B][COLOR="Red"]FAILED[/COLOR][/B] (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot erase userdata
erasing 'userdata'... [B][COLOR="red"]FAILED[/COLOR][/B] (remote: Erase Fail)
finished. total time: 0.016s
C:\ADBFAST>fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
sending 'bootloader' (1536 KB)... OKAY [ 0.250s]
writing 'bootloader'... OKAY [ 0.359s]
finished. total time: 0.609s
C:\ADBFAST>fastboot flash radio radio-crespo-m200krkc1.img
sending 'radio' (12288 KB)... OKAY [ 2.016s]
writing 'radio'... OKAY [ 1.828s]
finished. total time: 3.844s
C:\ADBFAST>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADBFAST>fastboot -w update image-sojuk-jro03e.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: I9020XXLC2
Baseband Version.....: M200KRKC1
Serial Number........: 3531430F809D00EC
--------------------------------------------
checking product... OKAY [ 0.016s]
checking version-bootloader... OKAY [ 0.000s]
checking version-baseband... OKAY [ 0.000s]
sending 'boot' (3964 KB)... OKAY [ 0.766s]
writing 'boot'... OKAY [ 0.547s]
sending 'recovery' (4308 KB)... OKAY [ 0.719s]
writing 'recovery'... OKAY [ 0.594s]
sending 'system' (294030 KB)... OKAY [ 48.094s]
writing 'system'... [B][COLOR="red"]FAILED [/COLOR][/B](remote: Write Fail)
finished. total time: 50.766s
my device is M200k korean
and i downoaded image files from developers google site
but these images are for crespo board.
and my cell board is herring
now where to download herring board image files for my device.
any help please?

Help to relock bootloader

hi
i want to relock my phone x1032 gpe with the android 5.1 img and i got some error in the "adb"
here is my log and my phone is x1032 gpe and i was have a custom rom before that with unlock bootloader
please help me
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 2.767s]
finished. total time: 2.783s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash partition
gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.094s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.421s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash motoboot m
otoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.156s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.092s]
finished. total time: 1.264s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash logo logo.
bin
target max-sparse-size: 256MB
sending 'logo' (76 KB)...
OKAY [ 0.094s]
writing 'logo'...
OKAY [ 0.094s]
finished. total time: 0.187s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash boot boot.
img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.452s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.905s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash recovery r
ecovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.452s]
writing 'recovery'...
OKAY [ 0.780s]
finished. total time: 1.232s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257288 KB)...
OKAY [ 9.454s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.859s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (260812 KB)...
OKAY [ 9.578s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.656s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (262141 KB)...
OKAY [ 9.580s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 9.674s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash system sys
tem.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (18680 KB)...
OKAY [ 0.764s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.827s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash modem NON-
HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49368 KB)...
OKAY [ 1.858s]
writing 'modem'...
OKAY [ 1.498s]
finished. total time: 3.372s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.016s]
finished. total time: 0.031s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot flash fsg fsg.mb
n
target max-sparse-size: 256MB
sending 'fsg' (708 KB)...
OKAY [ 0.109s]
writing 'fsg'...
OKAY [ 5.589s]
finished. total time: 5.714s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.265s]
finished. total time: 0.281s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 5.023s]
finished. total time: 5.023s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>mfastboot oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.016s]
finished. total time: 0.031s
C:\Users\ליאור ביטון\Desktop\ליאור ביטון\mfastboot-v2>
Click to expand...
Click to collapse
any help please
I don't know, sorry!

bootloader Unknown Partition preflash validation failed

HI
i am facing the issue in my moto g xt1033
i cant move from here i have struck in bootloader v41.1a* and device is locked, if i try to unlock this but it shows bootloader unlock is disabled and also trying to flash bootloader with same bootloader v41.1a and other v41.18 it always shows the same error i.e bootloader unknown partition here are the error msg i attest down
Installing the new bootloader
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.132s
applying the changes...
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
checking...
getvar:version-bootloader FAILED (command write failed (Too many links))
finished. total time: 0.085s

[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.

Categories

Resources