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!
hELLO..
I have had a moto g5 with oreo and magisk installed I tried to unistall magisk from magisk app after reboot it told me that startup failed then flashed an nougat rom and it worked perfectly but without imei numbers so i deleted cache from twrp recovery and tried to install the same software again but it gave me the error at the end ..what should I know now to fix the mobile knowing that when i try to select recoverymode it tells me ersing and then takes m back to fastboot
note the first time i just opened a bat file with the software that installed the software automatically..
the bat file told me that
<bootloader> slot-count not found
<bootloader> slot suffixes not found
<bootloader>has-slot:fsg not found
Flash this firmware https://drive.google.com/file/d/1cESQyuRpeUAmmEn67_to0sQ0KLhkMnWM/view (Oreo 8.1, February 2019 security patch) using fastboot and commands below. All the data in the internal storage of the phone will be erased.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Any ideas?
pablito1984 said:
Hi. Mine G5 is bricked as well.
When I`m trying to do what u said Andrej I got that:
Any ideas?
Click to expand...
Click to collapse
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
https://mirrors.lolinet.com/firmware/moto/cedric/official/
TheFixItMan said:
The firmware you are trying to flash is too old hense the security downgrade error
You must use firmware that is equal to or newer than what was previously flashed on it
Firmware available at
Click to expand...
Click to collapse
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
pablito1984 said:
Thank you for your reply.
I`ve downloaded XT1675_CEDRIC_RETGB_SS_8.1.0_OPPS28.85-13-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
as my phone model is XT1675.
I don`t know why, but when I`m trying to put fastboot oem fb_mode_set and it gives me that error
Click to expand...
Click to collapse
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logical: partition: not found
Sending 'partition' (45 KB) OKAY [ 0.169s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
pablito1984 said:
Thanks for explaining me that
I`ve downloaded now CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
And this time it`s not saying anything about downgrade, but I got this:
Click to expand...
Click to collapse
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
TheFixItMan said:
I presume you can get into the bootloader without using a sdcard for a hard bricked device
If so skip gpt and bootloader parts of the firmware - these don't need to be flashed unless your phone was hard bricked (just get a red flashing led if mmcblk0 sdcard not inserted)
Also make sure you have the Motorola drivers installed and that you are using the latest fastboot drivers from the android sdk
Click to expand...
Click to collapse
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Start up failed:
Your device didn`t start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Last time flashing failed
USB Connected
failed to validate recovery iumage
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Click to expand...
Click to collapse
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
C:\platform-tools>fastboot oem fb_mode_set
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.170s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.331s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.240s]
Writing 'logo' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.689s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.694s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.688s]
Writing 'dsp' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.969s]
Writing 'oem' (bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256537 KB) OKAY [ 8.462s]
Writing 'system' (bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256653 KB) OKAY [ 8.529s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (257978 KB) OKAY [ 8.446s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260705 KB) OKAY [ 8.488s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257421 KB) OKAY [ 8.464s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (257865 KB) OKAY [ 8.506s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (252667 KB) OKAY [ 8.402s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (253700 KB) OKAY [ 8.409s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (250301 KB) OKAY [ 8.271s]
Writing 'system' (bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66366 KB) OKAY [ 2.329s]
Writing 'modem' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst1
Erasing 'modemst1' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase modemst2
Erasing 'modemst2' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.258s]
Writing 'fsg' (bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase cache
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase customize
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot erase clogo
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: '')
fastboot: error: Command failed
C:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
Click to expand...
Click to collapse
pablito1984 said:
Yes. I can get into bootloader, but I can`t do anything over there except restarting and checking logs.
After checking the logs I can see :
Tried to use Lenovo Moto smart assistant to fix it, but it doesn`t see the device.
I`ve got all drivers, sdk, etc.
When tried to use fastboot I got this:
Click to expand...
Click to collapse
Either your setup is wrong - try another pc USB cable etc or you have a motherboard fault & need to replace it
TheFixItMan said:
That command is just to tell the phone you are about to flash firmware and the clear command at the end exists this mode
You don't need to use these commands it's just a way of telling the phone what you are doing and to start the phone normally after the flashing
You should be able to start with gpt (presuming you have found a firmware that is the same or newer than what you have on the phone already)
Click to expand...
Click to collapse
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
ghettozo said:
im having the same issue with moto e5play xt1921-1 i dont know what the latest fw is
Click to expand...
Click to collapse
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
TheFixItMan said:
Neither do i as I don't own your phone
Go to your own phone forum or Google for firmware for your device
To flash gpt and bootloader it must be the same or newer than version on device and an unlocked bootloader to avoid permissions errors especially if has been unlocked before
Click to expand...
Click to collapse
thanks. yes im using the forum here and google but im having issues
thankyou\
Hello and thank you for your work, my motorola z2 play came into bootloop from scratch, when it was in stock configuration, then without active debugging usb, bootloader unlocked and being in bootloop I can't unlock anything or even install the official ROM , now I'm trying with Lenovo Moto Smart but I have little hope because the phone keeps turning on and off even when it's in recovery mode. Do you have any advice for me?
Sorry for the poor description but I'm not very experienced, I ask you for advice because I don't know how to do it anymore.
Thank you,
Stephen.
PS: I also tried to unlock the oem with the motorola code but without success
PSS: I copy the account of my tempted to flash the stock rom
>> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash logo logo.bin
>> fastboot flash boot boot.img
>> fastboot flash recovery recovery.img
>> fastboot flash dsp adspso.bin
>> fastboot flash oem oem.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 system.img_sparsechunk.6
>> fastboot flash system system.img_sparsechunk.7
>> fastboot flash modem NON-HLOS.bin
>> fastboot erase modemst1
>> fastboot erase modemst2
>> fastboot flash fsg fsg.mbn
>> fastboot erase cache
>> fastboot erase userdata
>> fastboot erase customize
>> fastboot erase clogo
>> fastboot oem fb_mode_clear
>> fastboot reboot
OKAY [ 0.002s]
Finished. Total time: 0.007s
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.166s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.281s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.214s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.430s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.547s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.639s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logicalem: not found
Sending 'oem' (232923 KB) OKAY [ 5.260s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Sending 'system' (517135 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (506931 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (522215 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (521087 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (518083 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (515569 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (250209 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
(bootloader) is-logical:modem: not found
Sending 'modem' (75092 KB) OKAY [ 1.821s]
Writing 'modem' OKAY [ 0.807s]
Finished. Total time: 2.731s
Erasing 'modemst1' OKAY [ 0.028s]
Finished. Total time: 0.032s
Erasing 'modemst2' OKAY [ 0.028s]
Finished. Total time: 0.032s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.230s]
Writing 'fsg' OKAY [ 0.086s]
Finished. Total time: 0.336s
Erasing 'cache' OKAY [ 0.006s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.277s]
Finished. Total time: 0.281s
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.132s]
Finished. Total time: 0.135s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
"Update"
I tried to use Lenovo moto smart assistant and the result is this message:
Start Up Failed:
Your devices didn't start up successfully.
Use the software repair assistant on computer to repair your devices.
Connect your device[...]
Ap Fastboot Flash Mode (Secure)
ERROR: Failed topass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB connected
thank you guys!
Could you find any solution?
stemonta said:
Hello and thank you for your work, my motorola z2 play came into bootloop from scratch, when it was in stock configuration, then without active debugging usb, bootloader unlocked and being in bootloop I can't unlock anything or even install the official ROM , now I'm trying with Lenovo Moto Smart but I have little hope because the phone keeps turning on and off even when it's in recovery mode. Do you have any advice for me?
Sorry for the poor description but I'm not very experienced, I ask you for advice because I don't know how to do it anymore.
Thank you,
Stephen.
PS: I also tried to unlock the oem with the motorola code but without success
PSS: I copy the account of my tempted to flash the stock rom
>> fastboot flash partition gpt.bin
>> fastboot flash bootloader bootloader.img
>> fastboot flash logo logo.bin
>> fastboot flash boot boot.img
>> fastboot flash recovery recovery.img
>> fastboot flash dsp adspso.bin
>> fastboot flash oem oem.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 system.img_sparsechunk.6
>> fastboot flash system system.img_sparsechunk.7
>> fastboot flash modem NON-HLOS.bin
>> fastboot erase modemst1
>> fastboot erase modemst2
>> fastboot flash fsg fsg.mbn
>> fastboot erase cache
>> fastboot erase userdata
>> fastboot erase customize
>> fastboot erase clogo
>> fastboot oem fb_mode_clear
>> fastboot reboot
OKAY [ 0.002s]
Finished. Total time: 0.007s
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.166s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5115 KB) OKAY [ 0.281s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo: not found
Sending 'logo' (2192 KB) OKAY [ 0.214s]
Writing 'logo' OKAY [ 0.066s]
Finished. Total time: 0.430s
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.547s]
Writing 'boot' (bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:recovery: not found
Sending 'recovery' (20580 KB) OKAY [ 0.639s]
Writing 'recovery' (bootloader) Security version downgrade
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logicalem: not found
Sending 'oem' (232923 KB) OKAY [ 5.260s]
Writing 'oem' (bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Sending 'system' (517135 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (506931 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending sparse 'system' 1/2 (522215 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (521087 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (518083 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (515569 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:system: not found
Sending 'system' (250209 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
< waiting for any device >
fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory
(bootloader) is-logical:modem: not found
Sending 'modem' (75092 KB) OKAY [ 1.821s]
Writing 'modem' OKAY [ 0.807s]
Finished. Total time: 2.731s
Erasing 'modemst1' OKAY [ 0.028s]
Finished. Total time: 0.032s
Erasing 'modemst2' OKAY [ 0.028s]
Finished. Total time: 0.032s
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2932 KB) OKAY [ 0.230s]
Writing 'fsg' OKAY [ 0.086s]
Finished. Total time: 0.336s
Erasing 'cache' OKAY [ 0.006s]
Finished. Total time: 0.011s
Erasing 'userdata' OKAY [ 0.277s]
Finished. Total time: 0.281s
Erasing 'customize' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'clogo' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.132s]
Finished. Total time: 0.135s
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.004s
"Update"
I tried to use Lenovo moto smart assistant and the result is this message:
Start Up Failed:
Your devices didn't start up successfully.
Use the software repair assistant on computer to repair your devices.
Connect your device[...]
Ap Fastboot Flash Mode (Secure)
ERROR: Failed topass validation, backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
USB connected
thank you guys!
Click to expand...
Click to collapse
Can u tell me your model [email protected]
Notice there is a huge issue with the modem in another post https://forum.xda-developers.com/z2-force/help/0-imei-pie-xt-1789-03-sprint-t3957851 please stay tune
I am having an issue with Wifi, I attempted to update lineage os 17.1 did process to clean flash. After did all the process provided with the guide of lineage os official wiki of my moto Z2 when it booted it got stuck on the loop lineage logo for over 15 minutes than usual with it configures. I decided to flash it back to stock, did a script for it of course(using an example of rcmaehl here XDA) due to long periods test fail I was able to boot it in stock oreo, but when I got to set it up, it does not show any wifi and not even data of carrier. went to the bootloader again to notice that broadband is unknown(not found). long story short I have a half soft brick phone. Any idea and suggestion.
The script I was able to make flash to stock oreo:
Code:
@echo off
adb reboot bootloader
fastboot --set-active=a
ECHO Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a 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_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to rebooting to flash to B.
pause
adb reboot bootloader
pause
adb --set-active=b
echo Switched to partition A press any key to continue flashing...
pause
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash gpt gpt.bin
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a 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_a oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase ddr
fastboot flash fsg_a fsg.mbn
fastboot flash bluetooth_a BTFM.bin
fastboot oem fb_mode_clear
echo Finished. Press any key to reboot.
pause
fastboot reboot
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
41rw4lk said:
Looks like your script is wonky. It flashes everything from slot_a to slot_a, fine. Then it switches to slot_b and flashes everything to slot_a again. You just need a basic flashall. I've attached a zip with newer adb/fastboot files if neededm but the is also a flashfile convertor script courtesy of RootJunky. Just put the script in your extracted firmware folder and run it, it will create a flashall for that firmware. Then you can use the flashall to flash stock properly.
As far as installing Los17.1, follow the install guide, and use the prep zip to copy your modem etc to the other slot.
Click to expand...
Click to collapse
I attempted as avised with script convertor of RootJunky. First attempt running the script
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.000s]
Finished. Total time: 0.000s
(bootloader) is-logical:partition: not found
Sending 'partition' (206 KB) OKAY [ 0.016s]
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.185s]
Finished. Total time: 0.216s
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (9884 KB) OKAY [ 0.331s]
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.169s]
Finished. Total time: 0.501s
(bootloader) is-logical:modem__a: not found
Sending 'modem__a' (97431 KB) ^CTerminate batch job (Y/N)? n
Sending 'fsg' (5596 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.135s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:dsp__a: not found
Sending 'dsp__a' (16384 KB) OKAY [ 0.594s]
Writing 'dsp__a' (bootloader) Invalid partition name dsp__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:logo__a: not found
Sending 'logo__a' (3151 KB) OKAY [ 0.085s]
Writing 'logo__a' (bootloader) Invalid partition name logo__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:boot__a: not found
Sending 'boot__a' (23357 KB) OKAY [ 0.721s]
Writing 'boot__a' (bootloader) Invalid partition name boot__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516201 KB) OKAY [ 16.038s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (495129 KB) OKAY [ 15.564s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (519125 KB) OKAY [ 16.524s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (523779 KB) OKAY [ 16.152s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (516309 KB) OKAY [ 16.016s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system__a: not found
Sending 'system__a' (420583 KB) OKAY [ 13.061s]
Writing 'system__a' (bootloader) Invalid partition name system__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:system_b: not found
Sending 'system_b' (515183 KB) OKAY [ 16.010s]
Writing 'system_b' OKAY [ 2.907s]
Finished. Total time: 25.177s
(bootloader) is-logical:system_b: not found
Sending 'system_b' (307220 KB) OKAY [ 9.615s]
Writing 'system_b' OKAY [ 1.648s]
Finished. Total time: 14.835s
(bootloader) is-logical:oem__a: not found
Sending 'oem__a' (175682 KB) OKAY [ 5.476s]
Writing 'oem__a' (bootloader) Invalid partition name oem__a
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'modemst1' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'modemst2' OKAY [ 0.001s]
Finished. Total time: 0.005s
Erasing 'carrier' OKAY [ 0.001s]
Finished. Total time: 0.004s
Erasing 'cache' OKAY [ 0.000s]
Finished. Total time: 0.004s
Erasing 'userdata' OKAY [ 0.075s]
Finished. Total time: 0.082s
Erasing 'ddr' OKAY [ 0.001s]
Finished. Total time: 0.006s
(bootloader) is-logical:fsg__a: not found
Sending 'fsg__a' (5596 KB) OKAY [ 0.173s]
Writing 'fsg__a' (bootloader) Invalid partition name fsg__a
FAILED (remote: '')
fastboot: error: Command failed
(bootloader) is-logical:bluetooth__a: not found
Sending 'bluetooth__a' (4500 KB) OKAY [ 0.137s]
Writing 'bluetooth__a' (bootloader) Invalid partition name bluetooth__a
FAILED (remote: '')
fastboot: error: Command failed
OKAY [ 0.001s]
Finished. Total time: 0.004s
I notice the error, then proceeded to fix which it should be flash. all it flashes well, but went attempt to reboot to see if system boots up and go back to bootloader .
I'm aware that my scripting is the worst:laugh:, but funny part it got the job done to able to see the system up and running of course without data or wifi connection. :silly: I do appreciate the assistance and Hopefully keep having the assist with suggestions or guides of course. thankfully I have back up the phone(Not Moto z2) but really wish to go back this phone to able to use it as my main again...
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
insanegrim said:
it flashed successfully, but modem(wifi not working)when attempted to choose a connection . it is quite odd...that is not working. any ideas?
Click to expand...
Click to collapse
Go back to fastboot and flash the modem only.
fastboot flash modem (drag and drop the NON-HLOS.bin from your firmware here)
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
If that doesn't work it may be possible that your persist partition is full and not letting the modem initialize. You'll need root for this.
adb shell
su
cd /mnt/vendor/persist/cache/recovery
rm log
rm last_log
exit
exit
adb reboot
41rw4lk said:
If you look at your output you can see that it's putting double__underscores before the partition name, that's incorrect. To save a lot of time and trouble and since you're on Sprint which is the same as TMO when it comes to flashalls, I'll attach a flashall that will flash both slots so you should have a clean slate to start with. Also the rebooting to bootloader is because fastboot oem fb_mode_set wasn't cleared at the end, no big deal. The flashall I've attached should clear it when it's done.
Click to expand...
Click to collapse
This soft bricked and now it bootloops my xt1789-04