Develop Bugs

System Update Fails (T-Mobile phone)

Yesterday I got notification from Motorola Update Services about system update version OCXS27.1.2 (Android security updates thru March 1 2018). I download but it fails to install. [Software updated unsuccessful - Sorry, there was a problem updating your Moto Z². No changes were Made. √ OK]
I bought the phone used so dunno it's history. After purchase I unlocked bootloader and installed TWRP but have not rooted. I had it carrier unlocked thru an online service that enabled the T-mobile app on the server side (cellunlocker.net), and installed FreedomPop SIM card.
I called Motorola tech support. They first had me reset app preferences then passed me off to level 2 support after that didn't work, who had me factory data reset, and now they're passing me off to level 3 who may call me next week, since that didn't work either. Note when I did the factory data reset, it rebooted into TWRP automatically which asked for my lockcode, before (apparently) handling the reset request. After reboot I skipped the google login to make sure nothing conflicted, but it still won't do the system update.
I'm wondering if it possibly has to do with the phone's history somehow, or because I unlocked bootloader, or because I'm not using a T-Mobile SIM card, or because I installed TWRP. I dunno. I told this to Moto support and they didn't seem to care or think it mattered. They could see my resets from their side after I provided my IMEI.
Any ideas?

Having twrp flashed modifies /boot as our recovery is in the ramdisk in our /boot, which causes ota to fail. Fastboot flash stock boot.img for your current os (ncx26.2, ncx26.7, ocx27 or, ocx27.1) from the corresponding firmware package (flashall .zip) and you should be good to go. The official twrp can be booted now so no need to have it installed. If you do root in the future the same rule will apply as systemless root is also in /boot.
Sent from my Moto Z (2) using XDA Labs

Installing twrp mounted system as rw. You need to actually do a flash all with the official firmware by the Motorola Firmware Team on AFH. I have a thread in the guides section that educates on how to do this. Tier 3 will probably suggest the same.

You are probably getting this same error. It means you need to flash all with an official zip to have the update go through correctly.

Thanks much. I was a little worried as there seems to be an error message about file system, a scary looking warning, and FAILURE message near the end, but seems to have worked, and was able to OTA update after flashall. The only thing the instructions didn't specifically mention was to start phone with volume down+-power for fastboot, once I figured that out all was well.
Code:
Microsoft Windows [Version 10.0.16299.371]
(c) 2017 Microsoft Corporation. All rights reserved.
C:\>mkdir \Z2-Util
C:\>cd \Z2-Util
C:\Z2-Util>dir
Volume in drive C has no label.
Volume Serial Number is B45D-BE40
Directory of C:\Z2-Util
05/06/2018 03:45 PM <DIR> .
05/06/2018 03:45 PM <DIR> ..
12/30/2017 04:19 PM 1,784,320 adb.exe
12/30/2017 04:19 PM 97,792 AdbWinApi.dll
12/30/2017 04:19 PM 62,976 AdbWinUsbApi.dll
01/30/2018 02:22 PM 16,777,216 adspso.bin
01/30/2018 02:22 PM 23,905,510 boot.img
01/30/2018 02:22 PM 10,121,472 bootloader.img
01/30/2018 02:22 PM 4,604,160 BTFM.bin
12/30/2017 04:19 PM 853,504 fastboot.exe
04/23/2018 09:17 PM 1,433 flashall.bat
01/30/2018 04:24 PM 3,009 flashfile.xml
01/30/2018 02:22 PM 5,730,304 fsg.mbn
01/30/2018 02:22 PM 211,712 gpt.bin
01/30/2018 02:22 PM 3,227,518 logo.bin
01/30/2018 04:24 PM 911 NASH_TMO_C_OCX27.109-51_subsidy-TMO_regulatory-DEFAULT_CFC.info.txt
01/30/2018 02:22 PM 99,753,156 NON-HLOS.bin
01/30/2018 02:17 PM 179,898,736 oem.img
01/30/2018 04:23 PM 0 regulatory_info_default.png
01/30/2018 04:24 PM 2,701 servicefile.xml
01/30/2018 04:22 PM 610 slcf_rev_d_tmo_rsu_v1.1.nvm
01/30/2018 04:23 PM 528,589,836 system.img_sparsechunk.0
01/30/2018 04:23 PM 507,000,512 system.img_sparsechunk.1
01/30/2018 04:23 PM 531,596,644 system.img_sparsechunk.2
01/30/2018 04:23 PM 536,338,408 system.img_sparsechunk.3
01/30/2018 04:23 PM 528,569,592 system.img_sparsechunk.4
01/30/2018 04:23 PM 430,677,116 system.img_sparsechunk.5
01/30/2018 04:24 PM 527,547,620 system_b.img_sparsechunk.0
01/30/2018 04:24 PM 314,597,544 system_b.img_sparsechunk.1
27 File(s) 4,251,954,312 bytes
2 Dir(s) 250,683,760,640 bytes free
C:\Z2-Util>flashall
C:\Z2-Util>fastboot oem fb_mode_set
< waiting for any device >
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\Z2-Util>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.012s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.250s]
finished. total time: 0.267s
C:\Z2-Util>fastboot flash bootloader_a bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_a' (9884 KB)...
OKAY [ 0.454s]
writing 'bootloader_a'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.661s
C:\Z2-Util>fastboot flash bootloader_b bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (9884 KB)...
OKAY [ 0.365s]
writing 'bootloader_b'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.243s]
finished. total time: 0.627s
C:\Z2-Util>fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (97415 KB)...
OKAY [ 4.009s]
writing 'modem_a'...
OKAY [ 1.047s]
finished. total time: 5.055s
C:\Z2-Util>fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (5596 KB)...
OKAY [ 0.266s]
writing 'fsg_a'...
OKAY [ 0.078s]
finished. total time: 0.344s
C:\Z2-Util>fastboot flash modem_b NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_b' (97415 KB)...
OKAY [ 3.016s]
writing 'modem_b'...
OKAY [ 1.031s]
finished. total time: 4.063s
C:\Z2-Util>fastboot flash fsg_b fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_b' (5596 KB)...
OKAY [ 0.172s]
writing 'fsg_b'...
OKAY [ 0.078s]
finished. total time: 0.250s
C:\Z2-Util>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Z2-Util>fastboot flash bluetooth_a BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4496 KB)...
OKAY [ 0.172s]
writing 'bluetooth_a'...
OKAY [ 0.047s]
finished. total time: 0.234s
C:\Z2-Util>fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.625s]
writing 'dsp_a'...
OKAY [ 0.156s]
finished. total time: 0.781s
C:\Z2-Util>fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (3151 KB)...
OKAY [ 0.141s]
writing 'logo_a'...
OKAY [ 0.047s]
finished. total time: 0.187s
C:\Z2-Util>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (23345 KB)...
OKAY [ 0.937s]
writing 'boot_a'...
OKAY [ 0.391s]
finished. total time: 1.344s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (516201 KB)...
OKAY [ 20.836s]
writing 'system_a'...
OKAY [ 5.582s]
finished. total time: 26.434s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (495117 KB)...
OKAY [ 20.062s]
writing 'system_a'...
OKAY [ 4.869s]
finished. total time: 24.930s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (519137 KB)...
OKAY [ 20.861s]
writing 'system_a'...
OKAY [ 5.812s]
finished. total time: 26.689s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (523767 KB)...
OKAY [ 22.962s]
writing 'system_a'...
OKAY [ 4.966s]
finished. total time: 27.928s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (516181 KB)...
OKAY [ 25.824s]
writing 'system_a'...
OKAY [ 5.688s]
finished. total time: 31.512s
C:\Z2-Util>fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (420583 KB)...
OKAY [ 18.590s]
writing 'system_a'...
OKAY [ 3.969s]
finished. total time: 22.559s
C:\Z2-Util>fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (175682 KB)...
OKAY [ 7.904s]
writing 'oem_a'...
OKAY [ 1.781s]
finished. total time: 9.686s
C:\Z2-Util>fastboot flash bluetooth_b BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth_b' (4496 KB)...
OKAY [ 0.172s]
writing 'bluetooth_b'...
OKAY [ 0.078s]
finished. total time: 0.250s
C:\Z2-Util>fastboot flash dsp_b adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_b' (16384 KB)...
OKAY [ 0.750s]
writing 'dsp_b'...
OKAY [ 0.156s]
finished. total time: 0.922s
C:\Z2-Util>fastboot flash logo_b logo.bin
target reported max download size of 536870912 bytes
sending 'logo_b' (3151 KB)...
OKAY [ 0.172s]
writing 'logo_b'...
OKAY [ 0.047s]
finished. total time: 0.219s
C:\Z2-Util>fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (23345 KB)...
OKAY [ 0.812s]
writing 'boot_b'...
OKAY [ 0.391s]
finished. total time: 1.203s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (516201 KB)...
OKAY [ 22.460s]
writing 'system_b'...
OKAY [ 5.437s]
finished. total time: 27.898s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (495117 KB)...
OKAY [ 20.393s]
writing 'system_b'...
OKAY [ 4.872s]
finished. total time: 25.281s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (519137 KB)...
OKAY [ 21.401s]
writing 'system_b'...
OKAY [ 5.859s]
finished. total time: 27.260s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_b' (523767 KB)...
OKAY [ 22.156s]
writing 'system_b'...
OKAY [ 4.984s]
finished. total time: 27.141s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_b' (516181 KB)...
OKAY [ 21.069s]
writing 'system_b'...
OKAY [ 5.667s]
finished. total time: 26.767s
C:\Z2-Util>fastboot flash system_b system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_b' (420583 KB)...
OKAY [ 17.404s]
writing 'system_b'...
OKAY [ 3.994s]
finished. total time: 21.398s
C:\Z2-Util>fastboot flash oem_b oem.img
target reported max download size of 536870912 bytes
sending 'oem_b' (175682 KB)...
OKAY [ 6.563s]
writing 'oem_b'...
OKAY [ 1.766s]
finished. total time: 8.328s
C:\Z2-Util>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>fastboot erase ddr
erasing 'ddr'...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Z2-Util>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Z2-Util>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 1.203s]
finished. total time: 1.203s
C:\Z2-Util>fastboot --set-active=other
Setting current slot to 'b'...
(bootloader) WARNING: Bootloader images on target slot b are not valid!!
(bootloader) There is risk of bricking HW. Please flash valid bootloader
(bootloader) into slot b before activating it. OR you could force to
(bootloader) switch to slot b by running the same command again
(bootloader) within 30 s if you understand what you're doing
FAILED (remote failure)
finished. total time: 0.141s
C:\Z2-Util>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Z2-Util>

I have the same problem, but I do not have TWRP installed. Only booted into it, to install Magisk(and root). Otherwise, I'm stock image and stock bootloader.

Unseeablething said:
I have the same problem, but I do not have TWRP installed. Only booted into it, to install Magisk(and root). Otherwise, I'm stock image and stock bootloader.
Click to expand...
Click to collapse
You installed magisk which mounted a partition as r/w

Uzephi said:
You installed magisk which mounted a partition as r/w
Click to expand...
Click to collapse
Got it! Guess at this point, I'll just go over to DU.

So is there anything we can do to keep root and install updates?

teradark said:
So is there anything we can do to keep root and install updates?
Click to expand...
Click to collapse
Not really. The Motorola OTA checks the hash sum of each partition and if there is any discrepancy on partitions you wouldn't be able to edit without unlocking, it will fail as shown in the ota error message image a few posts back.

So if root is in a particular part of the partition, could I flash that specific part where root is stored, then perform the update, then re root?

teradark said:
So if root is in a particular part of the partition, could I flash that specific part where root is stored, then perform the update, then re root?
Click to expand...
Click to collapse
Root mounts system and maybe other partitions as read/write when they aren't supposed to be, making the hash sum different. You would need to at least flash the official system sparses from the Motorola firmware team's flash all if not more than that. (Root is nestled in boot, so you'd need to flash that as well).

Well I can't update again but for some other reason, even after flashall.
Previously it was cuz of TWRP so flashall then OTA update no problem. Then I installed magisk and adaway and all fine. Then I was trying to figure out how to get rid of tmobile stuff, tried a couple apps on playstore, including titanium backup, but couldn't figure it out. Then I saw someone wrote an exe to do it (debload) and running that made phone not boot. flashall again, try debload, it works, happy, but can't find update (different message, says there are no updates). Disappointed but decide rather have no t-mobile apps than update, so move on and install magisk. Then it can't boot. Decide I'd rather have adaway than no t-mobile so flashall again, but still can't update.
So other than installing magisk or twrp, what could make it so I can't update immediately after flashall? I imagine that debload did something that flashall doesn't undo, but there's no real detail or source/etc about what it's doing other than removing oem partition, but I see flashall puts that back so doesn't seem like that's it...

So I flash all and installed the OTA, does this mean that since i installed the OTA that i cant install the flash all manual update(btw updating this device is a pain on linux)

Android P [9.0.0 (PPR2.181005.003, Oct 2018)] OTA auto update killed my Pixel 2 xl

This past Aug I upgraded via OTA update to Android P 9.0 - Didn't like the updates but mostly was just visual disappointment with the GUI stuff. Earlier today I noticed my device asking me to restart to apply a new update, and being hesitant I decided to hold off.
Few hours later pulled my device out of my pocket to find a screen displaying in recovery mode only two options
1) Try Again
2) Factory data reset
I tried to just reboot by holding down the power but again it default loops to recovery mode with those two options.
Recovery mode displays the following information (which basically tells me my device decided to update itself even though I was holding off on it)
9/PPR2.181005.003/4284323
After realizing this was a real issue I found that I am able to get into fastboot mode and download mode however I am not sure this can help me.
Below is a list of the fastboot set variables
(bootloader) keep_efs:no
(bootloader) is_oem_unlocked:no
(bootloader) have_oem_lock_id:yes
(bootloader) avb_stored_rollback_indexes:
(bootloader) avb_user_settable_key_set:no
(bootloader) avb_version:1.0.0
(bootloader) hw-color:RCW
(bootloader) hw-variant:GA00138-US
(bootloader) hw-revision:rev_10
(bootloader) cid:00000000
(bootloader) erase-block-size:0x1000
(bootloader) logical-block-size:0x1000
(bootloader) unlocked:no
(bootloader) off-mode-charge:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4249
(bootloader) version-laf:1.0.7
(bootloader) version-baseband:g8998-00253-1805232234
(bootloader) version-bootloader:TMZ20k
(bootloader) version-abl:TMZ20k
(bootloader) version-aes:TMZ20k
(bootloader) version-cmnlib:TMZ20k
(bootloader) version-cmnlib64:TMZ20k
(bootloader) version-devcfg:TMZ20k
(bootloader) version-hyp:TMZ20k
(bootloader) version-keymaster:TMZ20k
(bootloader) version-pmic:TMZ20k
(bootloader) version-rpm:TMZ20k
(bootloader) version-xbl:TMZ20k
(bootloader) variant:MSM UFS
(bootloader) partition-type:laf_b:raw
(bootloader) partition-size:laf_b: 0x3000000
(bootloader) partition-type:laf_a:raw
(bootloader) partition-size:laf_a: 0x3000000
(bootloader) partition-type:dtbo_b:raw
(bootloader) partition-size:dtbo_b: 0x800000
(bootloader) partition-type:dtbo_a:raw
(bootloader) partition-size:dtbo_a: 0x800000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2800000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2800000
(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-typeersist:ext4
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x1C26BFB000
(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) has-slot:laf:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:dtbo:yes
(bootloader) has-slot:vbmeta:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slotmic:yes
(bootloader) has-slot:abl:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:radio:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:1
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:a,b,
(bootloader) secure:yes
(bootloader) serialno:711KPFX0872315
(bootloader) product:taimen
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) qem:0
I feel that since it's sort of locked up I am kinda screwed software wise. IDK...
I also run into a screen sometimes just before powering down that reads "Can't find valid operating system. The device will not start Visit this link on another device g.co/ABH ID C382B665"
--
I do not want to wipe the userdata because I have information that is far more valuable then this device is worth.
I am wondering if anybody has some suggestions on ways to obtain the userdata?
I would rip this device apart if I have to just to have a better chance of securing my data so please let me know if you have any ideas.
Thanks!

Flash the latest update on device using flashall.bat. make sure -w option is removed from the batch file. Might be able to get you up and running without losing data.
This can be done from bootloader mode
Sent from my Pixel 2 XL using Tapatalk

piyush7243 said:
Flash the latest update on device using flashall.bat. make sure -w option is removed from the batch file. Might be able to get you up and running without losing data.
This can be done from bootloader mode
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
All locked up and cannot flash it.
C:\Users\hacktron\Desktop\taimen-ppr2.181005.003-factory-f0a1d2c1\taimen-ppr2.181005.003>flash-all.bat
< waiting for any device >
Sending 'bootloader_a' (36336 KB) OKAY [ 0.810s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.827s
rebooting into bootloader OKAY [ 0.004s]
Finished. Total time: 0.005s
Sending 'radio_a' (60388 KB) OKAY [ 1.352s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.369s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ20k
Baseband Version.....: g8998-00253-1805232234
Serial Number........: XXXXXXXXXXX
--------------------------------------------
Checking product OKAY [ 0.007s]
Checking version-bootloader OKAY [ 0.004s]
Checking version-baseband OKAY [ 0.006s]
extracting boot.img (40 MB) to disk... took 0.184s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.027s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2207 MB) to disk... took 11.183s
archive does not contain 'system.sig'
extracting system_other.img (322 MB) to disk... took 1.791s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (351 MB) to disk... took 1.894s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (40960 KB) OKAY [ 0.892s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 20.825s
Press any key to exit...

have you tried deuces recovery script i think it overwrites the lock state.

sideload OTA.
use the last version you had on the phone while it was working.

As stated above suggesting the ota file is your best option I have a pixel that corrupts itself if I try updating any other way and it works without losing data

Your bootloader apparently is locked. To add to what the two previous posters have said, an OTA image can be sideloaded regardless of the lock status of the bootloader. Since the OTA image is a complete ROM you should be able to get up and running with minimal fuss.

Strephon Alkhalikoi said:
Your bootloader apparently is locked. To add to what the two previous posters have said, an OTA image can be sideloaded regardless of the lock status of the bootloader. Since the OTA image is a complete ROM you should be able to get up and running with minimal fuss.
Click to expand...
Click to collapse
Tried the above with no luck. I cannot side load OTA because I do not have access to adb, only fastboot. However I did try the deuces script two times, once to continue without unlocking and again with the to unlock bootloader options, but it failed to flash.
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 (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: 'Flashing Unlock is not allowed
')
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.007s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.824s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.836s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.006s
Sending 'radio_a' (60388 KB) OKAY [ 1.353s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.365s
rebooting into bootloader OKAY [ 0.004s]
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.008s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.820s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.831s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_a' (60388 KB) OKAY [ 1.355s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.369s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
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.007s
Sending 'abl_a' (540 KB) OKAY [ 0.014s]
Writing 'abl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.023s
Sending 'aes_a' (48 KB) OKAY [ 0.004s]
Writing 'aes_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 0.885s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.895s
Sending 'cmnlib_a' (220 KB) OKAY [ 0.007s]
Writing 'cmnlib_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'cmnlib64_a' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'devcfg_a' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.189s
Sending 'hyp_a' (264 KB) OKAY [ 0.009s]
Writing 'hyp_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'keymaster_a' (308 KB) OKAY [ 0.010s]
Writing 'keymaster_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'laf_a' (29800 KB) OKAY [ 0.648s]
Writing 'laf_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.658s
Sending 'modem_a' (60380 KB) OKAY [ 1.315s]
Writing 'modem_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.326s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.003s]
Writing 'pmic_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'rpm_a' (232 KB) OKAY [ 0.008s]
Writing 'rpm_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'tz_a' (1868 KB) OKAY [ 0.042s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.052s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.012s
Sending 'vendor_a' (360340 KB) OKAY [ 7.858s]
Writing 'vendor_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.868s
Sending 'xbl_a' (2620 KB) OKAY [ 0.061s]
Writing 'xbl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.073s
Flashing System A
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.134s]
Writing sparse 'system_a' 1/5 FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 16.946s
Flashing System B
Sending 'system_b' (330216 KB) OKAY [ 7.412s]
Writing 'system_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.422s
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.008s
Sending 'abl_b' (540 KB) OKAY [ 0.016s]
Writing 'abl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.032s
Sending 'aes_b' (48 KB) OKAY [ 0.005s]
Writing 'aes_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_b' (40960 KB) OKAY [ 0.924s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.939s
Sending 'cmnlib_b' (220 KB) OKAY [ 0.009s]
Writing 'cmnlib_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'cmnlib64_b' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'devcfg_b' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.187s]
Writing 'dtbo_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.202s
Sending 'hyp_b' (264 KB) OKAY [ 0.009s]
Writing 'hyp_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.025s
Sending 'keymaster_b' (308 KB) OKAY [ 0.011s]
Writing 'keymaster_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.027s
Sending 'laf_b' (29800 KB) OKAY [ 0.672s]
Writing 'laf_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.689s
Sending 'modem_b' (60380 KB) OKAY [ 1.363s]
Writing 'modem_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.379s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_b' (52 KB) OKAY [ 0.004s]
Writing 'pmic_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'rpm_b' (232 KB) OKAY [ 0.007s]
Writing 'rpm_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'tz_b' (1868 KB) OKAY [ 0.044s]
Writing 'tz_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.053s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.011s
Sending 'vendor_b' (360340 KB) OKAY [ 8.112s]
Writing 'vendor_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 8.122s
Sending 'xbl_b' (2620 KB) OKAY [ 0.063s]
Writing 'xbl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.078s
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.009s
Format Userdata[Y/N]?
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 40c24edc-c81a-11e8-8c97-ad6213ea0a12
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4672 KB) OKAY [ 0.109s]
Writing 'userdata' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.620s
Press any key to continue . . .
Finished Flashing... if you are still having bootloops, you may need to format userdata in factory recovery
DO NOT LOCK THE BOOTLOADER UNLESS YOU ARE SURE IT IS OPERATING PROPERLY

You need to boot into recovery mode, which you said your phone was on when you removed it from pocket, once in there hold volume up and press the power button.
Then you can go to option Apply update from ADB, select that and sideload will be possible.
If you want you can also temporarily launch twrp from fastboot, and try installing the OTA that way.
This will not install a new recovery or modify anything on your phone.
>fastboot boot c:\twrp.img

hacktron said:
Tried the above with no luck. I cannot side load OTA because I do not have access to adb, only fastboot. However I did try the deuces script two times, once to continue without unlocking and again with the to unlock bootloader options, but it failed to flash.
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 (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.002s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: 'Flashing Unlock is not allowed
')
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.007s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.824s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.836s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.006s
Sending 'radio_a' (60388 KB) OKAY [ 1.353s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.365s
rebooting into bootloader OKAY [ 0.004s]
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.008s
Sending 'bootloader_a' (36336 KB) OKAY [ 0.820s]
Writing 'bootloader_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.831s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
Sending 'radio_a' (60388 KB) OKAY [ 1.355s]
Writing 'radio_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.369s
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.004s
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.007s
Sending 'abl_a' (540 KB) OKAY [ 0.014s]
Writing 'abl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.023s
Sending 'aes_a' (48 KB) OKAY [ 0.004s]
Writing 'aes_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 0.885s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.895s
Sending 'cmnlib_a' (220 KB) OKAY [ 0.007s]
Writing 'cmnlib_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'cmnlib64_a' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'devcfg_a' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.180s]
Writing 'dtbo_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.189s
Sending 'hyp_a' (264 KB) OKAY [ 0.009s]
Writing 'hyp_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'keymaster_a' (308 KB) OKAY [ 0.010s]
Writing 'keymaster_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'laf_a' (29800 KB) OKAY [ 0.648s]
Writing 'laf_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.658s
Sending 'modem_a' (60380 KB) OKAY [ 1.315s]
Writing 'modem_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.326s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.003s]
Writing 'pmic_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.016s
Sending 'rpm_a' (232 KB) OKAY [ 0.008s]
Writing 'rpm_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.019s
Sending 'tz_a' (1868 KB) OKAY [ 0.042s]
Writing 'tz_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.052s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.012s
Sending 'vendor_a' (360340 KB) OKAY [ 7.858s]
Writing 'vendor_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.868s
Sending 'xbl_a' (2620 KB) OKAY [ 0.061s]
Writing 'xbl_a' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.073s
Flashing System A
Sending sparse 'system_a' 1/5 (524284 KB) OKAY [ 12.134s]
Writing sparse 'system_a' 1/5 FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 16.946s
Flashing System B
Sending 'system_b' (330216 KB) OKAY [ 7.412s]
Writing 'system_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 7.422s
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.008s
Sending 'abl_b' (540 KB) OKAY [ 0.016s]
Writing 'abl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.032s
Sending 'aes_b' (48 KB) OKAY [ 0.005s]
Writing 'aes_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_b' (40960 KB) OKAY [ 0.924s]
Writing 'boot_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.939s
Sending 'cmnlib_b' (220 KB) OKAY [ 0.009s]
Writing 'cmnlib_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'cmnlib64_b' (288 KB) OKAY [ 0.009s]
Writing 'cmnlib64_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.020s
Sending 'devcfg_b' (60 KB) OKAY [ 0.004s]
Writing 'devcfg_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'dtbo_b' (8192 KB) OKAY [ 0.187s]
Writing 'dtbo_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.202s
Sending 'hyp_b' (264 KB) OKAY [ 0.009s]
Writing 'hyp_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.025s
Sending 'keymaster_b' (308 KB) OKAY [ 0.011s]
Writing 'keymaster_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.027s
Sending 'laf_b' (29800 KB) OKAY [ 0.672s]
Writing 'laf_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.689s
Sending 'modem_b' (60380 KB) OKAY [ 1.363s]
Writing 'modem_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.379s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_b' (52 KB) OKAY [ 0.004s]
Writing 'pmic_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.017s
Sending 'rpm_b' (232 KB) OKAY [ 0.007s]
Writing 'rpm_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.018s
Sending 'tz_b' (1868 KB) OKAY [ 0.044s]
Writing 'tz_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.053s
Sending 'vbmeta_b' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.011s
Sending 'vendor_b' (360340 KB) OKAY [ 8.112s]
Writing 'vendor_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 8.122s
Sending 'xbl_b' (2620 KB) OKAY [ 0.063s]
Writing 'xbl_b' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.078s
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.009s
Format Userdata[Y/N]?
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 40c24edc-c81a-11e8-8c97-ad6213ea0a12
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4672 KB) OKAY [ 0.109s]
Writing 'userdata' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 0.620s
Press any key to continue . . .
Finished Flashing... if you are still having bootloops, you may need to format userdata in factory recovery
DO NOT LOCK THE BOOTLOADER UNLESS YOU ARE SURE IT IS OPERATING PROPERLY
Click to expand...
Click to collapse
Maybe I'm wrong, and maybe I'm not understanding what's going on, but unlocking the bootloader completely wipes the phone. Including user data.

@exist2resist: His bootloader is apparently locked, meaning he cannot temp boot TWRP.
@Soured Lie: You would be correct. Attempting to unlock the bootloader would wipe the data.
@hacktron: Why are you attempting to unlock the bootloader when no one told you to do so? If you had succeeded you would have lost all that data you say is more valuable than the phone itself. You would have had no one to blame but yourself. Since you're having difficulty, this page may be of use to you. Follow its instructions and you should have no issue restoring your device.

Strephon Alkhalikoi said:
@exist2resist: His bootloader is apparently locked, meaning he cannot temp boot TWRP.
@Soured Lie: You would be correct. Attempting to unlock the bootloader would wipe the data.
@hacktron: Why are you attempting to unlock the bootloader when no one told you to do so? If you had succeeded you would have lost all that data you say is more valuable than the phone itself. You would have had no one to blame but yourself. Since you're having difficulty, this page may be of use to you. Follow its instructions and you should have no issue restoring your device.
Click to expand...
Click to collapse
Ok so I'm not confused then. He should be happy he didn't succeed. I was wondering wth he was doing if he wanted to keep his data.

Soured Lie said:
Ok so I'm not confused then. He should be happy he didn't succeed. I was wondering wth he was doing if he wanted to keep his data.
Click to expand...
Click to collapse
I am soo happy it didn't succeed! I Just didn't know if I screwed it all up already or not. It's been a few years since I have played around devices. Should have kept on it.
@Strephon Alkhalikoi - Hear you load and clear. I assumed ADB was not able to connect but I am going to go back when I have a chance and make sure the drivers are all there, then try to sideload OTA again as it was originally suggested.
Really appreciate the feedback from y'all.

@Strephon Alkhalikoi
What does he do if he didn't have debugging enabled from settings?

Soured Lie said:
@Strephon Alkhalikoi
What does he do if he didn't have debugging enabled from settings?
Click to expand...
Click to collapse
You don't need to enable ADB to connect in recovery. It is required only to connect when phone is booted and running.

So I just got back and checked it out. Seems like my device is only recognized by device manager in the following ways...
bootloader mode (fastmode) as Lemobile Android Device
download mode as USB Serial Device (COMX)
When in Recovery mode its not recognized at all and my recovery mode menu is just those two options as originally described.
Any ideas?

hacktron said:
So I just got back and checked it out. Seems like my device is only recognized by device manager in the following ways...
bootloader mode (fastmode) as Lemobile Android Device
download mode as USB Serial Device (COMX)
When in Recovery mode its not recognized at all and my recovery mode menu is just those two options as originally described.
Any ideas?
Click to expand...
Click to collapse
Since you want to keep your data, your best bet is to borrow/beg/steal a computer,
copy adb file set into it, and run adb sideload ota.zip.
Small package is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip

michaelbsheldon said:
Since you want to keep your data, your best bet is to borrow/beg/steal a computer,
copy adb file set into it, and run adb sideload ota.zip.
Small package is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
I am confused lol
I have a computer. I just also installed android studio and updated the sdk usb drivers, and I thought I had previously installed the drivers because I have been using this phone and pc together for sometime now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[baby bird needs a spoon feeding ]

You may have reached an big, ugly fork in the road:
1.) pay big $$ to forensic technician to retrieve the phone's data
2.) do what it says, wipe the phone, and if no hardware issues present, it should run fine

michaelbsheldon said:
You may have reached an big, ugly fork in the road:
1.) pay big $$ to forensic technician to retrieve the phone's data
2.) do what it says, wipe the phone, and if no hardware issues present, it should run fine
Click to expand...
Click to collapse
figures!
Lesson learned, don't leave your phone stock and lose faith in Google too!
Thx all for your help!

Z2 Force dead, just turn on with USB connected, don't charge

Hi, guys!
I just found XDA on internet search and hope you guys help me
I have a Z2Force and it don't turns on unless the USB are connected on charge or PC. When I connect the cable, the charge icon display appears but stays on an infinite loop and does not show the charge percentage.
When I try to turn on the phone (with charge connected), it goes into infinite loop on Motorola logo.
I can get into the fastboot menu pressing power + vol - , but only with USB connected. There on that screen, it says "Power OK".
I tried to flash stock rom using Minimal ADB and fastboot, I got the ROM on "lolinet dot com" (I can't post links, 'cause I'm new user). I downloaded on nash/official/RETBR (my Z2F is from Brasil). I used this commands:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase cache
fastboot erase carrier
fastboot erase ddr
fastboot reboot
the installation goes to the end, but after restarting, the phone keeps looping on the logo screen...
I don't know if this information will be helpful, but the bootloader is locked (oem_locked).
I don't have developer knowledge, but I can follow your guidance, just tell me what to do.
I will be happy to pay a beer for those who help me
Please, guys, help me, I don't have another phone
Thank you very much in advance.
Edit: I got this phone from a friend, he tried to use a custom ROM, the phone worked but without Play Store, he tried to restore to stock ROM and got to this situation. So, he gave me the phone, because my Z2Play fell on water and died

Anyone??
Please, can anyone help me? :/

Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.

41rw4lk said:
Go into fastboot and type 'fastboot -w' w/o quotes and see if that will let you boot. It is a must when moving between stock and custom roms.
Click to expand...
Click to collapse
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/

AgrippaJr said:
That's the result:
C:\Users\Junior\Downloads\adb_fastboot_binaries_Motorola_Z2_Force_XT1789-05>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.251s]
finished. total time: 0.252s
Still on bootloop... :/
Click to expand...
Click to collapse
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?

41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
Yeah, this one...

41rw4lk said:
This is the latest retbr firmware, is this what you flashed? RETBR/XT1789-05_NASH_RETBR_8.0.0_OPXS27.109-34-21_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The commands in your flashall look haphazard as well, where did you get it?
Click to expand...
Click to collapse
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737

AgrippaJr said:
I downloaded the ADB and Fastboot from this guide: https://forum.xda-developers.com/z2-force/how-to/guides-bootloader-twrp-custom-roms-root-t3805737
Click to expand...
Click to collapse
Not adb/fastboot, the flashall.bat that you're using where did you get that?

41rw4lk said:
Not adb/fastboot, the flashall.bat that you're using where did you get that?
Click to expand...
Click to collapse
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...

AgrippaJr said:
From that guide too...
I followed the "E" section from the guide...
The rom flashes all OK, no errors, but still loopboot...
Click to expand...
Click to collapse
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.

41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
OK... I will try here... I'll let u know

Test result, questions
41rw4lk said:
There are a lot of firmwares, phone variants, and flashalls and what works for one might not work for another. I've attached an xml to bat convertor. Scrap the unzipped firmware you have and the flashall, and using a clean firmware zip follow the directions in the convertor zip to make a flashall exclusively for your firmware. You'll want the flashfile that wipes your device.
Click to expand...
Click to collapse
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?

AgrippaJr said:
Still on bootloop... (when I say bootloop: It keeps turning on and off... It turns on, shows the blue screen with red M logo, then shut off and turn on again, until I disconnect the USB cable from it... Is this the bootloop?)
I'm using Windows 10, last version of Motorola drivers and the original phone's USB-C cable on my computer's USB 2.0. I follow this steps:
1. Unzip converter;
2. Extract clean firmware zip content to converter folder;
3. Execute '2-rsd-flash-flashfile-windows' ;
4. Connect cable and turn on phone on fastboot mode;
5. Execute flashfile.bat.
This is the flash log:
C:\Users\Junior\Downloads\RSD_Lite_Motorola_XML_To_Batch_Script\Motorola_XML_To_Batch_Script\Place_Extracted_Firmware_Here>echo off
max-sparse-size: 268435456
finished. total time: 0.003s
...
OKAY [ 0.009s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'partition' (206 KB)...
OKAY [ 0.009s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) - flashing 'gpt_main1.bin' to 'partition:1'
(bootloader) - flashing 'gpt_main2.bin' to 'partition:2'
(bootloader) - flashing 'gpt_main3.bin' to 'partition:3'
(bootloader) - flashing 'gpt_main4.bin' to 'partition:4'
(bootloader) - flashing 'gpt_main5.bin' to 'partition:5'
OKAY [ 0.215s]
finished. total time: 0.227s
target reported max download size of 536870912 bytes
sending 'bootloader' (9884 KB)...
OKAY [ 0.310s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'xbl.elf' to 'xbl'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'pmic.elf' to 'pmic'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'storsec.mbn' to 'storsec'
(bootloader) - flashing 'prov64.mbn' to 'prov'
OKAY [ 0.202s]
finished. total time: 0.515s
target reported max download size of 536870912 bytes
sending 'modem_a' (97431 KB)...
OKAY [ 2.977s]
writing 'modem_a'...
OKAY [ 1.037s]
finished. total time: 4.017s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.172s]
writing 'fsg_a'...
OKAY [ 0.064s]
finished. total time: 0.238s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.140s]
writing 'bluetooth_a'...
OKAY [ 0.058s]
finished. total time: 0.201s
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.501s]
writing 'dsp_a'...
OKAY [ 0.154s]
finished. total time: 0.658s
target reported max download size of 536870912 bytes
sending 'logo_a' (3524 KB)...
OKAY [ 0.108s]
writing 'logo_a'...
OKAY [ 0.041s]
finished. total time: 0.151s
target reported max download size of 536870912 bytes
sending 'boot_a' (23357 KB)...
OKAY [ 0.717s]
writing 'boot_a'...
OKAY [ 0.384s]
finished. total time: 1.103s
target reported max download size of 536870912 bytes
sending 'system_a' (516200 KB)...
OKAY [ 15.760s]
writing 'system_a'...
OKAY [ 5.477s]
finished. total time: 21.245s
target reported max download size of 536870912 bytes
sending 'system_a' (522116 KB)...
OKAY [ 16.027s]
writing 'system_a'...
OKAY [ 5.308s]
finished. total time: 21.337s
target reported max download size of 536870912 bytes
sending 'system_a' (519014 KB)...
OKAY [ 15.962s]
writing 'system_a'...
OKAY [ 5.753s]
finished. total time: 21.718s
target reported max download size of 536870912 bytes
sending 'system_a' (516292 KB)...
OKAY [ 15.274s]
writing 'system_a'...
OKAY [ 5.146s]
finished. total time: 20.428s
target reported max download size of 536870912 bytes
sending 'system_a' (523200 KB)...
OKAY [ 16.024s]
writing 'system_a'...
OKAY [ 5.543s]
finished. total time: 21.574s
target reported max download size of 536870912 bytes
sending 'system_a' (413511 KB)...
OKAY [ 12.452s]
writing 'system_a'...
OKAY [ 3.986s]
finished. total time: 16.466s
target reported max download size of 536870912 bytes
sending 'system_b' (515182 KB)...
OKAY [ 15.568s]
writing 'system_b'...
OKAY [ 5.129s]
finished. total time: 20.704s
target reported max download size of 536870912 bytes
sending 'system_b' (319609 KB)...
OKAY [ 9.575s]
writing 'system_b'...
OKAY [ 3.188s]
finished. total time: 12.767s
target reported max download size of 536870912 bytes
sending 'oem_a' (163065 KB)...
OKAY [ 4.912s]
writing 'oem_a'...
OKAY [ 1.662s]
finished. total time: 6.576s
erasing 'modemst1'...
OKAY [ 0.084s]
finished. total time: 0.086s
erasing 'modemst2'...
OKAY [ 0.083s]
finished. total time: 0.084s
erasing 'carrier'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.087s
erasing 'userdata'...
OKAY [ 0.341s]
finished. total time: 0.342s
erasing 'ddr'...
OKAY [ 0.092s]
finished. total time: 0.093s
target reported max download size of 536870912 bytes
sending 'fsg_a' (5600 KB)...
OKAY [ 0.251s]
writing 'fsg_a'...
OKAY [ 0.144s]
finished. total time: 0.397s
target reported max download size of 536870912 bytes
sending 'bluetooth_a' (4500 KB)...
OKAY [ 0.232s]
writing 'bluetooth_a'...
OKAY [ 0.148s]
finished. total time: 0.382s
...
OKAY [ 0.098s]
finished. total time: 0.099s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
Is there nothing I have to do before/after following the steps above? :|
IDK if it's relevant on this situation, but my bootloader is locked and I can't unlock it. I have the keycode and tried by fastboot:
COMMAND USED: 'fastboot oem unlock (code received by Motorola)'
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.005s]
finished. total time: 0.006s
I don't want to sound silly, but although in the fastboot menu it says 'Power OK', do you think this problem with the device only turning on when connected to USB could be causing this bootloop? Elsewhere I've read that this symptom may be battery related... Do you think this may be due to a critical charge percentage?
Click to expand...
Click to collapse
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.

41rw4lk said:
It could be your battery plain and simple, but I thought you might as well try to flash a clean rom to see if that would solve it before going to that conclusion. That output is a little weird but maybe that's normal for your variant. If you're able to boot into recovery, pull the sim and sdcard if present, reboot to recovery and do a factory reset. To verify some info what is the model listed by the charger port on the phone xt1789-??
Can you post the flashall.bat that was created by the convertor tool? The only thing left to try before ruling it a battery problem is a blankflash to rebuild your pbl. Post back with info and results of factory reset if you were able to do so.
Click to expand...
Click to collapse
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...

AgrippaJr said:
So I tried the flash and it didn't work out ...
When you speak in recovery mode, do you say enter fastboot mode and choose recovery mode? I chose, it restarts and bootloop on the Motorola logo again... I did it without SIM or SD card on it.
My phone model is the XT-1789-05... Below is the flashfile.bat generated by the converter tool:
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
What do you sugest, my friend? Maybe a Blankflash? If yes, can you give me the steps?
Thank for your effort on helping me...
Click to expand...
Click to collapse
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.

What is your battery voltage when you fastboot getvar all?

Uzephi said:
What is your battery voltage when you fastboot getvar all?
Click to expand...
Click to collapse
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...

41rw4lk said:
Nevermind about the servicefile, go ahead and try the blankflash here.
https://forum.xda-developers.com/showpost.php?p=77623934&postcount=5
---------- Post added at 06:10 AM ---------- Previous post was at 05:59 AM ----------
If a blankflash and clean firmware install doesn't sort it, I'd blame the battery or something else. Either way it's beyond me.
Click to expand...
Click to collapse
I follow all the tutorial steps, in two different PC's, windows versions and cables, cmd says 'waiting for device'... It don't detect the phone...
When i do the 'devices' command at adb and fastboot:
C:\Users\Junior\Desktop\adb and fastboot>adb devices
List of devices attached
C:\Users\Junior\Desktop\adb and fastboot>fastboot devices
0042953957 fastboot
Did i miss something?

AgrippaJr said:
Hi! the command gave me this value: (bootloader) battery-voltage: 7996
The phone only turns on when usb connected or with moto snap battery attached...
Click to expand...
Click to collapse
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.

Uzephi said:
7996 def means a battery issue. It shouldn't be above 4200. Seems it might be reporting wrong. That is saying the battery is sending almost 8 volts to your phone which would fry it if that was true.
Click to expand...
Click to collapse
I see... And where do you think the defect is? Maybe the battery or something else? What can I do about it? :|
maybe I should open and measure the battery voltage with a multimeter... What do you think?
If you have another solution, let me know

[CLOSED] T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!

Here is a patched MSM download tool for TMobile OP7T.
It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.
1) Download the patched MSM download tool: [removed]
2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.
3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
Code:
fastboot flashing unlock_critical
4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495
How to enter EDL mode:
VQ30DE said:
[...] Getting into EDL mode took me a while because I'd never had to do that on any previous phone way back when I used custom ROMs. Note that in EDL mode the screen is blank, and apparently it times out after 10 seconds. So the way to do it is to power off the phone and disconnect the USB if it's connected. Then press both volume UP and DOWN at same time, then while holding those buttons down, insert the USB which should already be connected to your computer. The best way would be to have the MSM program already open on your PC, then put phone into ELD mode. I had my left hand holding the volume buttons on the phone (press hard with two fingers to be sure), used right hand to plug in USB, then right hand on the mouse to work MSM. Once the USB is plugged in, watch the MSM window and look for it to say "Connected". Then just click the Start button. You can then release the volume buttons on the phone and let MSM do its thing. [...]
Click to expand...
Click to collapse

Thanks you very murch

Tested and working? If something goes wrong is it easily fixed/corrected? This is to bypass the 7 day waiting period for the unlock token?

Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.

I can confirm steps 2 and 3 work. Step 2 for my case took 234 seconds so be patience. Now trying step 4.

Superboy58 said:
Tested, 100% working.
No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
Click to expand...
Click to collapse
Confirmed! Presently bootloader unlocked and global rom installed. Will receive my unlock token on Friday......hee hee.
Wanted to say thank you for putting this together and making it dummy proof.

when i do a fastboot oem get_unlock_code, i get the following error message
FAILED (remote: Unknow command)
finished. total time: 0.006s
May I know where did i went wrong?
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
step 8 flash-all.bat, i got the following error messages, is it serious?
< waiting for any device >
Finished. Total time: 8.649s
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/5 (523144 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 17.884s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 17.760s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.005s
Press any key to continue . . .
---------- Post added at 02:13 AM ---------- Previous post was at 01:52 AM ----------
I tried flash-all.bat again, there is no error message but the fastboot oem get_unlock_code, i get the following error message
FAILED (remote: 'Unknow command')
fastboot: error: Command failed
I checked the Build Number, it is indeed the version i downloaded.
Anyone can help?
---------- Post added at 02:26 AM ---------- Previous post was at 02:13 AM ----------
Guys, my dual sim is working and I no longer see the T-mobile locked. Is that all i need?

@warlord2045 you don't ever have to run the command you run "fastboot oem get_unlock_code".
Follow the instructions in the first post, it will work.

Thank you so much!
Superboy58 said:
@warlord2045 you don't ever have to run the command you run "fastboot oem get_unlock_code".
Follow the instructions in the first post, it will work.
Click to expand...
Click to collapse

Brilliant. If anyone is attempting this on Linux, I'd recommend getting the latest platform-tools straight from Google. Even the fastboot version from 2019 available in my repository was too old to perform a lot of the steps.

I wonder who'll be the first to convert a McLaren to International??

inneyeseakay said:
I wonder who'll be the first to convert a McLaren to International??
Click to expand...
Click to collapse
We are on the 7T forum.
That being said, I made the same kind of tool for McLaren, but it only allows to unlock it's bootloader. There's no international firmware for McLaren. Unfortunately, there is no hardware equivalent for the McLaren sold as an international phone (it was easy for the 7T to convert because it's the same hardware, or at least very very close).

maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine
edit----
something is wrong with the conversion...
c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s

SALHERO said:
maybe is a dumb question but what firmware i need download and install because, when i try the process all is ok. but the wireless is deactivated, not turn on (automatically turn off and not detect any signal). when i return to stock tmobile 1.0.3 all is working fine
edit----
something is wrong with the conversion...
c:\adb\OnePlus 7T T-Mobile 10.0.3\10.0.12-GLOBAL-OnePlus7TOxygen_14.O.18_OTA_018_all_2007240040_cce2fc-FASTBOOT>flash-all.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?Y
Erasing 'userdata' OKAY [ 0.118s]
mke2fs 1.44.4 (18-Aug-2018)
Creating filesystem with 25477509 4k blocks and 6373376 inodes
Filesystem UUID: a431573c-e970-11ea-899c-8f976991a228
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (4616 KB) OKAY [ 0.110s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.006s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 1.307s
Sending 'boot_a' (98304 KB) OKAY [ 2.126s]
Writing 'boot_a' OKAY [ 0.485s]
Finished. Total time: 4.778s
Sending 'dtbo' (16384 KB) OKAY [ 0.357s]
Writing 'dtbo' OKAY [ 0.066s]
Finished. Total time: 0.628s
Sending 'modem_a' (165396 KB) OKAY [ 4.820s]
Writing 'modem_a' OKAY [ 0.720s]
Finished. Total time: 7.672s
Sending 'reserve' (250136 KB) OKAY [ 9.648s]
Writing 'reserve' FAILED (remote: '(reserve_a) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 3.539s]
Writing 'recovery' OKAY [ 0.477s]
Finished. Total time: 5.811s
Sending 'vbmeta' (8 KB) OKAY [ 0.005s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.063s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.012s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.042s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.035s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.012s]
Writing 'aop' OKAY [ 0.003s]
Finished. Total time: 0.072s
Sending 'bluetooth' (828 KB) OKAY [ 0.027s]
Writing 'bluetooth' OKAY [ 0.005s]
Finished. Total time: 0.190s
Sending 'cmnlib' (384 KB) OKAY [ 0.019s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.021s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.008s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 2.171s]
Writing 'dsp' OKAY [ 0.394s]
Finished. Total time: 3.617s
Sending 'hyp' (480 KB) OKAY [ 0.020s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.010s]
Writing 'imagefv' OKAY [ 0.003s]
Finished. Total time: 0.062s
Sending 'keymaster' (248 KB) OKAY [ 0.012s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.294s]
Writing 'LOGO' OKAY [ 0.034s]
Finished. Total time: 0.576s
Sending 'multiimgoem' (16 KB) OKAY [ 0.007s]
Writing 'multiimgoem' OKAY [ 0.003s]
Finished. Total time: 0.050s
Sending 'odm' (912 KB) OKAY [ 0.027s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.064s]
Writing 'oem_stanvbk' OKAY [ 0.016s]
Finished. Total time: 0.175s
Sending 'opproduct' (586912 KB) OKAY [ 19.483s]
Writing 'opproduct' OKAY [ 2.505s]
Finished. Total time: 31.632s
Sending 'qupfw' (72 KB) OKAY [ 0.014s]
Writing 'qupfw' OKAY [ 0.002s]
Finished. Total time: 0.063s
fastboot: error: cannot load 'storsec.img': No such file or directory
Sending 'tz' (3092 KB) OKAY [ 0.077s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.016s]
Writing 'uefisecapp' OKAY [ 0.003s]
Finished. Total time: 0.068s
Sending 'xbl' (3120 KB) OKAY [ 0.080s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.012s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
Sending 'system' (2292492 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.115s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product' 1/2 (785436 KB) OKAY [ 18.167s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.008s
Click to expand...
Click to collapse
I don't know why you were not able to boot into fastbootd (it says "Failed to boot into userspace fastboot" which means failed to boot into fastbootd).
But it's because of this error that all the warnings "Flashing is not allowed for Critical Partitions" are appearing.
If your fastboot executable is too old, the command "fastboot reboot fastboot", which allows you to boot in fastbootd, will not work. So I suggest you download the latest platform tools zip from Google, so you'll be using the latest adb and latest fastboot : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then ensure that in the terminal, the right version of fastboot is used (pay attention to the existing environment variables which might make your terminal use the old fastboot executable in another location).
Then run again the script flash-all.bat.
Please update,
Thanks

Congrats!

Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.

Thank you allowed me to unlock the bootloader on my wifes 7t and convert to global firmware then i relocked the bootloader the global firmware and software just runs so much smoother than the T-Mobile software not sure why.

Hello,
is anybody know can this guide somehow help me to get my OnePlus 7T unlocked? I mean Network unlocked...
Please if somebody can help me with that I would really appreciate it. Thank you!

@floopidze please read the first post.

Shortychance said:
Umm would this by any chance work on a sim locked OnePlus 7t with an unpaid balance?? I bought one and got scammed cause when I called TMobile to unlock the phone they said they can't because it has money owned on it which the seller never told me. I geus would just be really nice if I could still do something about it and get it to work.
Click to expand...
Click to collapse
It will work on a simlocked device, but it will not sim unlock the phone.
Please read the first post.

Question Xiaomi pad 5 fastboot error

Hello!
I'm writting this post because I have a problem and I'm going nuts. The only thing I want is to flash fastboot global version (I have the EU one). I flashed it and this is what I found:
product: nabu
erasing 'boot_ab'...
(bootloader) Partition boot_a erase successfully
(bootloader) Partition boot_b erase successfully
OKAY [ 0.017s]
finished. total time: 0.017s
target reported max download size of 805306368 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.010s]
writing 'crclist'...
OKAY [ 0.007s]
finished. total time: 0.018s
target reported max download size of 805306368 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.009s]
writing 'sparsecrclist'...
OKAY [ 0.003s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'xbl_ab' (4054 KB)...
OKAY [ 0.164s]
writing 'xbl_ab'...
(bootloader) Partition xbl_a flashed successfully
(bootloader) Partition xbl_b flashed successfully
OKAY [ 0.037s]
finished. total time: 0.201s
target reported max download size of 805306368 bytes
sending 'xbl_config_ab' (120 KB)...
OKAY [ 0.016s]
writing 'xbl_config_ab'...
(bootloader) Partition xbl_config_a flashed successfully
(bootloader) Partition xbl_config_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.028s
target reported max download size of 805306368 bytes
sending 'abl_ab' (204 KB)...
OKAY [ 0.013s]
writing 'abl_ab'...
(bootloader) Partition abl_a flashed successfully
(bootloader) Partition abl_b flashed successfully
OKAY [ 0.008s]
finished. total time: 0.021s
target reported max download size of 805306368 bytes
sending 'tz_ab' (3115 KB)...
OKAY [ 0.120s]
writing 'tz_ab'...
(bootloader) Partition tz_a flashed successfully
(bootloader) Partition tz_b flashed successfully
OKAY [ 0.021s]
finished. total time: 0.141s
target reported max download size of 805306368 bytes
sending 'hyp_ab' (476 KB)...
OKAY [ 0.025s]
writing 'hyp_ab'...
(bootloader) Partition hyp_a flashed successfully
(bootloader) Partition hyp_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.037s
target reported max download size of 805306368 bytes
sending 'devcfg_ab' (53 KB)...
OKAY [ 0.015s]
writing 'devcfg_ab'...
(bootloader) Partition devcfg_a flashed successfully
(bootloader) Partition devcfg_b flashed successfully
OKAY [ 0.010s]
finished. total time: 0.025s
target reported max download size of 805306368 bytes
sending 'storsec' (20 KB)...
OKAY [ 0.008s]
writing 'storsec'...
OKAY [ 0.005s]
finished. total time: 0.013s
target reported max download size of 805306368 bytes
sending 'bluetooth_ab' (1020 KB)...
OKAY [ 0.041s]
writing 'bluetooth_ab'...
(bootloader) Partition bluetooth_a flashed successfully
(bootloader) Partition bluetooth_b flashed successfully
OKAY [ 0.013s]
finished. total time: 0.055s
target reported max download size of 805306368 bytes
sending 'cmnlib_ab' (385 KB)...
OKAY [ 0.024s]
writing 'cmnlib_ab'...
(bootloader) Partition cmnlib_a flashed successfully
(bootloader) Partition cmnlib_b flashed successfully
OKAY [ 0.012s]
finished. total time: 0.036s
target reported max download size of 805306368 bytes
sending 'cmnlib64_ab' (503 KB)...
OKAY [ 0.025s]
writing 'cmnlib64_ab'...
(bootloader) Partition cmnlib64_a flashed successfully
(bootloader) Partition cmnlib64_b flashed successfully
OKAY [ 0.011s]
finished. total time: 0.036s
target reported max download size of 805306368 bytes
sending 'modem_ab' (108236 KB)...
OKAY [ 3.986s]
writing 'modem_ab'...
(bootloader) Partition modem_a flashed successfully
(bootloader) Partition modem_b flashed successfully
OKAY [ 0.437s]
finished. total time: 4.423s
target reported max download size of 805306368 bytes
sending 'dsp_ab' (65536 KB)...
OKAY [ 2.193s]
writing 'dsp_ab'...
(bootloader) Partition dsp_a flashed successfully
(bootloader) Partition dsp_b flashed successfully
OKAY [ 0.267s]
finished. total time: 2.460s
erasing 'metadata'...
FAILED (remote: Erase of metadata is not allowed in merging state)
finished. total time: 0.003s
Erase metadata error
I've changed the USB cable, the USB port, tryed a windows and linux pc, erased data with xiaomi's recovery... And no idea what else to do. The bootloader is unlocked. Thanks in advance.

Well, it seems I've hit the nail on the head. I have tried to flash by fasboot with linux and with windows, change the cable and ports, with different miflash... and nothing.
I found this link (https://source.android.com/devices/t...l_ab/implement) to know what happens with the fastboot protocols because of the "merging state" problem, so I tried the following command to find out what status the tablet was in: fastboot getvar snapshot-update-status. It said it was in "merging" As a last resort I went to the miui updater and downloaded the rom from there again and updated from it. It was updated and I entered the same command again for fastboot: fastboot getvar snapshot-update-status. It said it was set to "none". From there I flashed the rom by fastboot running flash_all.bat and I have the global rom.
For those who, having the same problem as me, do not boot the tablet and go back to fastboot automatically, take the boot.img of the fastboot rom from the area that had the rom (in my case it was the European one) and open the cmd and put the following command: fastboot flash boot boot.img. Reboot and it should be back to normal. All this should work as long as you have the same error as me and the data and metadata partitions have not been deleted. I hope that it would be useful to someone.