I desperate need help!!! - Google Pixel 2 XL Questions & Answers

Idk what else to do. I've run all the scripts and still can't get booted. It started with unlocking and trying to flash nitrogen. Made it to the nitrogen boot animation and it just hung. Tried to flash the factory img and haven't been in system since. I tried deuces, skipsoft, manual factory flashing etc. I just don't know what to do. Can anyone help me here?
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: Device already : unlocked!)
Finished. Total time: 0.000s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s
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' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'bootloader_a' (36380 KB) OKAY [ 1.031s]
Writing 'bootloader_a' OKAY [ 0.281s]
Finished. Total time: 1.312s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Sending 'radio_a' (60412 KB) OKAY [ 1.606s]
Writing 'radio_a' OKAY [ 0.859s]
Finished. Total time: 2.465s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' OKAY [ 0.010s]
Finished. Total time: 0.020s
Sending 'bootloader_b' (36380 KB) OKAY [ 0.914s]
Writing 'bootloader_b' OKAY [ 0.296s]
Finished. Total time: 1.210s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Sending 'radio_b' (60412 KB) OKAY [ 1.500s]
Writing 'radio_b' OKAY [ 0.844s]
Finished. Total time: 2.344s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.010s]
Finished. Total time: 0.020s
Sending 'abl_a' (540 KB) OKAY [ 0.010s]
Writing 'abl_a' OKAY [ 0.010s]
Finished. Total time: 0.040s
Sending 'aes_a' (52 KB) OKAY [ 0.010s]
Writing 'aes_a' OKAY [ 0.000s]
Finished. Total time: 0.010s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 1.000s]
Writing 'boot_a' OKAY [ 0.573s]
Finished. Total time: 1.589s
Sending 'cmnlib_a' (220 KB) OKAY [ 0.000s]
Writing 'cmnlib_a' OKAY [ -0.000s]
Finished. Total time: 0.016s
Sending 'cmnlib64_a' (288 KB) OKAY [ 0.016s]
Writing 'cmnlib64_a' OKAY [ 0.016s]
Finished. Total time: 0.031s
Sending 'devcfg_a' (60 KB) OKAY [ -0.000s]
Writing 'devcfg_a' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.203s]
Writing 'dtbo_a' OKAY [ 0.047s]
Finished. Total time: 0.250s
Sending 'hyp_a' (256 KB) OKAY [ 0.000s]
Writing 'hyp_a' OKAY [ 0.031s]
Finished. Total time: 0.047s
Sending 'keymaster_a' (308 KB) OKAY [ 0.016s]
Writing 'keymaster_a' OKAY [ 0.016s]
Finished. Total time: 0.031s
Sending 'laf_a' (29800 KB) OKAY [ 0.728s]
Writing 'laf_a' OKAY [ 0.437s]
Finished. Total time: 1.166s
Sending 'modem_a' (60404 KB) OKAY [ 1.468s]
Writing 'modem_a' OKAY [ 0.391s]
Finished. Total time: 1.874s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.016s]
Writing 'pmic_a' OKAY [ -0.000s]
Finished. Total time: 0.016s
Sending 'rpm_a' (232 KB) OKAY [ 0.016s]
Writing 'rpm_a' OKAY [ 0.000s]
Finished. Total time: 0.016s
Sending 'tz_a' (1900 KB) OKAY [ 0.047s]
Writing 'tz_a' OKAY [ 0.016s]
Finished. Total time: 0.078s
Sending 'vbmeta_a' (4 KB) OKAY [ -0.000s]
Writing 'vbmeta_a' OKAY [ -0.000s]
Finished. Total time: -0.000s
Sending 'vendor_a' (354932 KB) FAILED (data write failure (Unknown error))
Finished. Total time: 11.980s
---------- Post added at 10:41 PM ---------- Previous post was at 10:32 PM ----------
I'm at my wit's end man. I've run every script here. I've downloaded several factory img and tried running them. It stays stuck on the Google splash screen and goes no further. I just don't know what to do anymore.
---------- Post added at 11:05 PM ---------- Previous post was at 10:41 PM ----------
PS C:\Users\kaoat\Desktop\platform-tools> fastboot oem device-info
...
(bootloader) Verity mode: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ -0.000s]
finished. total time: -0.000s
PS C:\Users\kaoat\Desktop\platform-tools> fastboot getvar all
(bootloader) keep_efs:no
(bootloader) is_oem_unlocked:yes
(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:yes
(bootloader) off-mode-charge:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4109
(bootloader) version-laf:1.0.3
(bootloader) version-baseband:g8998-00202-1802061358
(bootloader) version-bootloader:TMZ12g
(bootloader) version-abl:TMZ12g
(bootloader) version-aes:TMZ12g
(bootloader) version-cmnlib:TMZ12g
(bootloader) version-cmnlib64:TMZ12g
(bootloader) version-devcfg:TMZ12g
(bootloader) version-hyp:TMZ12g
(bootloader) version-keymaster:TMZ12g
(bootloader) version-pmic:TMZ12g
(bootloader) version-rpm:TMZ12g
(bootloader) version-xbl:TMZ12g
(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:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:5
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:a,b,
(bootloader) secure:yes
(bootloader) serialno:712KPTM1289625
(bootloader) product:taimen
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) qem:0
all:
finished. total time: 0.141s

MatthewRobinson said:
Idk what else to do. I've run all the scripts and still can't get booted. It started with unlocking and trying to flash nitrogen. Made it to the nitrogen boot animation and it just hung. Tried to flash the factory img and haven't been in system since. I tried deuces, skipsoft, manual factory flashing etc. I just don't know what to do. Can anyone help me here?
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: Device already : unlocked!)
Finished. Total time: 0.000s
This will say "failed" if already unlocked - ignore
Running Unlock_critical
Look at your device,
press up arrow and Power to confirm
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.000s
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' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'bootloader_a' (36380 KB) OKAY [ 1.031s]
Writing 'bootloader_a' OKAY [ 0.281s]
Finished. Total time: 1.312s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Sending 'radio_a' (60412 KB) OKAY [ 1.606s]
Writing 'radio_a' OKAY [ 0.859s]
Finished. Total time: 2.465s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Slot _b does not exist. supported slots are:
a
b
Setting current slot to 'b' OKAY [ 0.010s]
Finished. Total time: 0.020s
Sending 'bootloader_b' (36380 KB) OKAY [ 0.914s]
Writing 'bootloader_b' OKAY [ 0.296s]
Finished. Total time: 1.210s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Sending 'radio_b' (60412 KB) OKAY [ 1.500s]
Writing 'radio_b' OKAY [ 0.844s]
Finished. Total time: 2.344s
rebooting into bootloader OKAY [ -0.000s]
Finished. Total time: -0.000s
Slot _a does not exist. supported slots are:
a
b
Setting current slot to 'a' OKAY [ 0.010s]
Finished. Total time: 0.020s
Sending 'abl_a' (540 KB) OKAY [ 0.010s]
Writing 'abl_a' OKAY [ 0.010s]
Finished. Total time: 0.040s
Sending 'aes_a' (52 KB) OKAY [ 0.010s]
Writing 'aes_a' OKAY [ 0.000s]
Finished. Total time: 0.010s
fastboot: error: cannot load 'apdp.img': No such file or directory
Sending 'boot_a' (40960 KB) OKAY [ 1.000s]
Writing 'boot_a' OKAY [ 0.573s]
Finished. Total time: 1.589s
Sending 'cmnlib_a' (220 KB) OKAY [ 0.000s]
Writing 'cmnlib_a' OKAY [ -0.000s]
Finished. Total time: 0.016s
Sending 'cmnlib64_a' (288 KB) OKAY [ 0.016s]
Writing 'cmnlib64_a' OKAY [ 0.016s]
Finished. Total time: 0.031s
Sending 'devcfg_a' (60 KB) OKAY [ -0.000s]
Writing 'devcfg_a' OKAY [ 0.016s]
Finished. Total time: 0.016s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.203s]
Writing 'dtbo_a' OKAY [ 0.047s]
Finished. Total time: 0.250s
Sending 'hyp_a' (256 KB) OKAY [ 0.000s]
Writing 'hyp_a' OKAY [ 0.031s]
Finished. Total time: 0.047s
Sending 'keymaster_a' (308 KB) OKAY [ 0.016s]
Writing 'keymaster_a' OKAY [ 0.016s]
Finished. Total time: 0.031s
Sending 'laf_a' (29800 KB) OKAY [ 0.728s]
Writing 'laf_a' OKAY [ 0.437s]
Finished. Total time: 1.166s
Sending 'modem_a' (60404 KB) OKAY [ 1.468s]
Writing 'modem_a' OKAY [ 0.391s]
Finished. Total time: 1.874s
fastboot: error: cannot load 'msadp.img': No such file or directory
Sending 'pmic_a' (52 KB) OKAY [ 0.016s]
Writing 'pmic_a' OKAY [ -0.000s]
Finished. Total time: 0.016s
Sending 'rpm_a' (232 KB) OKAY [ 0.016s]
Writing 'rpm_a' OKAY [ 0.000s]
Finished. Total time: 0.016s
Sending 'tz_a' (1900 KB) OKAY [ 0.047s]
Writing 'tz_a' OKAY [ 0.016s]
Finished. Total time: 0.078s
Sending 'vbmeta_a' (4 KB) OKAY [ -0.000s]
Writing 'vbmeta_a' OKAY [ -0.000s]
Finished. Total time: -0.000s
Sending 'vendor_a' (354932 KB) FAILED (data write failure (Unknown error))
Finished. Total time: 11.980s
---------- Post added at 10:41 PM ---------- Previous post was at 10:32 PM ----------
I'm at my wit's end man. I've run every script here. I've downloaded several factory img and tried running them. It stays stuck on the Google splash screen and goes no further. I just don't know what to do anymore.
---------- Post added at 11:05 PM ---------- Previous post was at 10:41 PM ----------
PS C:\Users\kaoat\Desktop\platform-tools> fastboot oem device-info
...
(bootloader) Verity mode: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ -0.000s]
finished. total time: -0.000s
PS C:\Users\kaoat\Desktop\platform-tools> fastboot getvar all
(bootloader) keep_efs:no
(bootloader) is_oem_unlocked:yes
(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:yes
(bootloader) off-mode-charge:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4109
(bootloader) version-laf:1.0.3
(bootloader) version-baseband:g8998-00202-1802061358
(bootloader) version-bootloader:TMZ12g
(bootloader) version-abl:TMZ12g
(bootloader) version-aes:TMZ12g
(bootloader) version-cmnlib:TMZ12g
(bootloader) version-cmnlib64:TMZ12g
(bootloader) version-devcfg:TMZ12g
(bootloader) version-hyp:TMZ12g
(bootloader) version-keymaster:TMZ12g
(bootloader) version-pmic:TMZ12g
(bootloader) version-rpm:TMZ12g
(bootloader) version-xbl:TMZ12g
(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:7
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:5
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) slot-suffixes:a,b,
(bootloader) secure:yes
(bootloader) serialno:712KPTM1289625
(bootloader) product:taimen
(bootloader) max-download-size:0x20000000
(bootloader) kernel:uefi
(bootloader) qem:0
all:
finished. total time: 0.141s
Click to expand...
Click to collapse
I read about your issue in another thread as well. Sorry your having a rough go my friend, this stuff can get frustrating. By chance, have you tried going to your stock recovery and doing a factory reset? Yeah, it'll wipe your data, but since your not making any headway with everything else, you might as well try starting from scratch.

MatthewRobinson said:
Idk what else to do. I've run all the scripts and still can't get booted. It started with unlocking and trying to flash nitrogen. Made it to the nitrogen boot animation and it just hung.
Click to expand...
Click to collapse
I would download the full June image and flash manually AGAIN. Confirm you have the latest adb/fastboot binaries from May. Do that and post your screen. Unless you have a some sort of hardware issue, this will wipe partitions/slots and install the stock ROM to your device, ELSE it will error out and give you a clue.

What type of USB cable are you using to connect to your PC? Make sure it's not a USB c to USB c. You want a USB c to USB a
Sent from my Pixel 2 XL using XDA Labs

Thank heavens I've been using my USB from the HTC M10. It's a USB a to C. Apparently, it wasn't working on the USB slots I had it plugged in. I switched slots and Bam it worked fine suddenly. These pixels have given me crap since they added that slot A/B mess. I can't stand it man.

I had a similar problem a few days ago. I had DU installed and then tried to go back to stock. I did a factory reset. Was running fine until I installed Magisk. It booted up showing the DU animation??! Didn't get past the animation. So I installed TWRP wiped slot A then slot B. Then flashed the factory image into slot A. Switched to slot B and flashed the factory images there. I kept -w flag in the 'fastboot update -w' to erase all data when flashing. Switched back to slot A to boot up and works fine (truth be told: I'm terrified of switching to slot B!)

Triscuit said:
What type of USB cable are you using to connect to your PC? Make sure it's not a USB c to USB c. You want a USB c to USB a
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Can you elaborate on this, please ?

Myrrhman said:
Can you elaborate on this, please ?
Click to expand...
Click to collapse
He basically means something like this :good:
Anker [2-Pack, 6ft] PowerLine+ USB-C to USB-A, Double-Braided Nylon Fast Charging Cable, for Samsung Galaxy S9/S9+/S8/S8+/Note 8, MacBook, LG V20/G5/G https://www.amazon.com/dp/B071G5YCS6/ref=cm_sw_r_other_apap_JWNBWzHNngMVA

Triscuit said:
What type of USB cable are you using to connect to your PC? Make sure it's not a USB c to USB c. You want a USB c to USB a
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Badger50 said:
He basically means something like this :good:
Anker [2-Pack, 6ft] PowerLine+ USB-C to USB-A, Double-Braided Nylon Fast Charging Cable, for Samsung Galaxy S9/S9+/S8/S8+/Note 8, MacBook, LG V20/G5/G https://www.amazon.com/dp/B071G5YCS6/ref=cm_sw_r_other_apap_JWNBWzHNngMVA
Click to expand...
Click to collapse
Yes i got that.
Sorry, maybe my post was unclear
I meant, why cant we use a USB C to USB C for flashing ?

Myrrhman said:
Yes i got that.
Sorry, maybe my post was unclear
I meant, why cant we use a USB C to USB C for flashing ?
Click to expand...
Click to collapse
They are known to have issues when trying to transfer data, not sure why.
Sent from my Pixel 2 XL using XDA Labs

Myrrhman said:
Yes i got that.
Sorry, maybe my post was unclear
I meant, why cant we use a USB C to USB C for flashing ?
Click to expand...
Click to collapse
Triscuit could probably explain it better than I. However, from what I've read, and personal experience, that it simply doesn't work well, if at all in most cases. Case in point. When I got the device, I used the enclosed USB A to C adapter, which worked fine for data transfer from my 6p to my P2XL. However, it did nothing on my pc. So I used my old 6p USB A to USB C cable, and it worked flawlessly. I can't explain the technical aspects of it, however, if you read through many of the threads on this topic, you'll see that the #1 cause of failed flashes and no data transfer to/from your pc have been cable related. And there ya go

I dont think a computer has USB C, i could be wrong.
After doing dueces flash all script, have you tried going back to a May Firmware or April.
Also try going to recovery and factory reset.

Triscuit said:
They are known to have issues when trying to transfer data, not sure why.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Badger50 said:
Triscuit could probably explain it better than I. However, from what I've read, and personal experience, that it simply doesn't work well, if at all in most cases. Case in point. When I got the device, I used the enclosed USB A to C adapter, which worked fine for data transfer from my 6p to my P2XL. However, it did nothing on my pc. So I used my old 6p USB A to USB C cable, and it worked flawlessly. I can't explain the technical aspects of it, however, if you read through many of the threads on this topic, you'll see that the #1 cause of failed flashes and no data transfer to/from your pc have been cable related. And there ya go
Click to expand...
Click to collapse
Ah, ok. Thanks for clarifying, guys !
lucky_strike33 said:
I dont think a computer has USB C, i could be wrong.
After doing dueces flash all script, have you tried going back to a May Firmware or April.
Also try going to recovery and factory reset.
Click to expand...
Click to collapse
You mean YOUR computer ?
I use the cable that came with the phone on my PC to transfer files a lot and it always works. (so USB C to USB C)
But its maybe different when trying to flash software.

Something very similar like this happened to me last week, i was completely shut out from flashing anything and lost complete control of the device. What i would recommend you do shut your computer down and turn on. get your pixel in bootloader mode and flash the stock file. I am assuming you have the june files and platform tools. Try that and see, smetimes a fresh start isnt that bad, it took me 6 hours of trying everything since i removed everything even system partition.
Oh btw the sometimes the phone dont get recognised dont freak out just keep trying

lucky_strike33 said:
I dont think a computer has USB C, i could be wrong.
After doing dueces flash all script, have you tried going back to a May Firmware or April.
Also try going to recovery and factory reset.
Click to expand...
Click to collapse
My laptop is over a year old and it has a type c Port. I personally don't have issued with data transfer like some only do with my c to c cord

Myrrhman said:
Ah, ok. Thanks for clarifying, guys !
You mean YOUR computer ?
I use the cable that came with the phone on my PC to transfer files a lot and it always works. (so USB C to USB C)
But its maybe different when trying to flash software.
Click to expand...
Click to collapse
Yea I would go ahead and try using something other than the charging cable that came with your phone, I use a cable like this personally, got this with my Nexus 6P a while back and it works great.
Sent from my Pixel 2 XL using XDA Labs

Triscuit said:
Yea I would go ahead and try using something other than the charging cable that came with your phone, I use a cable like this personally, got this with my Nexus 6P a while back and it works great.
Click to expand...
Click to collapse
That looks familiar :laugh:

Badger50 said:
That looks familiar :laugh:
Click to expand...
Click to collapse
Badger, did we ever cross paths on the 6P forums? I don't remember ever seeing your name pop up, granted it's been a little while.
Sent from my Pixel 2 XL using XDA Labs

Triscuit said:
Badger, did we ever cross paths on the 6P forums? I don't remember ever seeing your name pop up, granted it's been a little while.
Click to expand...
Click to collapse
Pretty sure we did my friend. Then again, my aging memory ain't what it used to be :laugh:

Badger50 said:
Pretty sure we did my friend. Then again, my aging memory ain't what it used to be :laugh:
Click to expand...
Click to collapse
Likewise......
Sent from my Pixel 2 XL using XDA Labs

Related

Bricked after trying to lock bootloader

Hello Guys, after unlocking the bootloader and using custom ROMs for some time, i tryed to lock the bootloader again and all gone wrong.
All i can reach is fastboot.
Any tentative of flashing return a validation error.
Getvar info:
PS C:\Users\fanel\Desktop\Nova pasta (2)> .\mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.CD
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 0034595812
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 4445E80800000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 355644082056579
(bootloader) meid:
(bootloader) date: 06-23-2017
(bootloader) sku: XT1710-07
(bootloader) carrier_sku:
(bootloader) battid: SNN5983B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jan 31 2:30:44 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:8.0.0/OPSS27.
(bootloader) ro.build.fingerprint[1]: 76-12-25-3/4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.201.4.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M8953P_41.50.07.63R ALBUS_BRAZILDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gb7e088c (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri May 25 03:07:55 CDT 2018
(bootloader) sbl1.git: git=MBM-NG-VC0.CD-0-g4650d8f
(bootloader) rpm.git: git=bd19194
(bootloader) tz.git: git=5fda3f8-dirty
(bootloader) devcfg.git: git=5fda3f8-dirty
(bootloader) keymaster.git: git=5fda3f8-dirty
(bootloader) cmnlib.git: git=5fda3f8-dirty
(bootloader) cmnlib64.git: git=5fda3f8-dirty
(bootloader) prov.git: git=5fda3f8-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.CD-0-g361b83a
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.031s
Now i cant flash any ROM.
Do you guys have any idea?
Edit:
Flashing a 8.0 ROM i got this errors:
-
PS C:\Users\fanel\Desktop\Nova pasta (3)\ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> .\fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.409s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.219s]
finished. total time: 0.627s
-
PS C:\Users\fanel\Desktop\Nova pasta (3)\ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> .\fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.500s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.516s
-
PS C:\Users\fanel\Desktop\Nova pasta (3)\ALBUS_OPS27.76-12-25_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml> .\fastboot flash system system.img_sparsechu
nk.0
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.223s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.238s
You need right firmware to lock, must be the signed one.
You need the October one. Locking is tricky, the only way I could do it was as I described here: https://forum.xda-developers.com/z2...igned-boot-t3749041/post78082103#post78082103
Cupcake 1.5 said:
You need right firmware to lock, must be the signed one.
You need the October one. Locking is tricky, the only way I could do it was as I described here: https://forum.xda-developers.com/z2...igned-boot-t3749041/post78082103#post78082103
Click to expand...
Click to collapse
That could be the problem, but im not that interessed in locking anymore, just to make it work again.
Anyway, i will look for the firmware and give it a go.
Edit:
After trying ALBUS_OPSS27.76-12-25-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC firmware, i've seen in bootloader logs the message "image is too large" in pink letters.
Bump!
Malboritus said:
Bump!
Click to expand...
Click to collapse
Are you sorted out yet?
kewlzter said:
Are you sorted out yet?
Click to expand...
Click to collapse
not even close.
Malboritus said:
not even close.
Click to expand...
Click to collapse
I have some suggestions.
Flash 7.1 first. Then upgrade to 8.0
The error you are getting sounds like you are flashing the wrong firmware. I've seen this same size error once, and that was the issue for me.
Hold tight, I'll put you together a care package together.
kewlzter said:
I have some suggestions.
Flash 7.1 first. Then upgrade to 8.0
The error you are getting sounds like you are flashing the wrong firmware. I've seen this same size error once, and that was the issue for me.
Hold tight, I'll put you a package together.
Click to expand...
Click to collapse
*hope intensifies*
Malboritus said:
*hope intensifies*
Click to expand...
Click to collapse
Try this, Make sure to unzip the folder.
http://sendanywhe.re/3B86UE8G
Link expires in 47hr
kewlzter said:
Try this, Make sure to unzip the folder.
http://sendanywhe.re/3B86UE8G
Link expires in 47hr
Click to expand...
Click to collapse
Thanks! im away from home, but will have the phone in 3 days. I let you know if i have any sucess.
Dear All, this is Sudip here. I am not sure is this is he correct place to post the question, but I kinda helpless after searching for the answer for my question and not finding it...can anyone please tell me if moto z2 play will have any simultaneous dual 4g support (for example using 2 JIO sim) in any on the custom Roms? does this facility needs any builtin hardware or it just the software that can enable the facility? Any heads up will be appreciated..
sd.malakar said:
Dear All, this is Sudip here. I am not sure is this is he correct place to post the question, but I kinda helpless after searching for the answer for my question and not finding it...can anyone please tell me if moto z2 play will have any simultaneous dual 4g support (for example using 2 JIO sim) in any on the custom Roms? does this facility needs any builtin hardware or it just the software that can enable the facility? Any heads up will be appreciated..
Click to expand...
Click to collapse
if anyone can please share an update on the above.
kewlzter said:
Try this, Make sure to unzip the folder.
http://sendanywhe.re/3B86UE8G
Link expires in 47hr
Click to expand...
Click to collapse
Sorry for the long time!
No luck.
Code:
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.031s]
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 failure)
finished. total time: 0.106s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.134s]
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 failure)
finished. total time: 0.352s
target reported max download size of 534773760 bytes
sending 'logo' (2163 KB)...
OKAY [ 0.082s]
writing 'logo'...
OKAY [ 0.041s]
finished. total time: 0.125s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.409s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.214s]
finished. total time: 0.626s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.506s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.527s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.381s]
writing 'dsp'...
OKAY [ 0.120s]
finished. total time: 0.504s
target reported max download size of 534773760 bytes
sending 'oem' (232923 KB)...
OKAY [ 5.310s]
writing 'oem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.357s
target reported max download size of 534773760 bytes
sending 'system' (517131 KB)...
OKAY [ 11.792s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 11.855s
target reported max download size of 534773760 bytes
sending sparse 'system' (506895 KB)...
OKAY [ 12.461s]
writing 'system'...
OKAY [ 3.346s]
sending sparse 'system' (16048 KB)...
OKAY [ 0.396s]
writing 'system'...
OKAY [ 0.084s]
finished. total time: 16.295s
target reported max download size of 534773760 bytes
sending sparse 'system' (522123 KB)...
OKAY [ 12.724s]
writing 'system'...
OKAY [ 3.198s]
sending sparse 'system' (2120 KB)...
OKAY [ 0.074s]
writing 'system'...
OKAY [ 0.024s]
finished. total time: 16.025s
target reported max download size of 534773760 bytes
sending 'system' (521179 KB)...
OKAY [ 11.888s]
writing 'system'...
OKAY [ 2.774s]
finished. total time: 14.665s
target reported max download size of 534773760 bytes
sending 'system' (513079 KB)...
OKAY [ 11.707s]
writing 'system'...
OKAY [ 3.052s]
finished. total time: 14.761s
target reported max download size of 534773760 bytes
sending 'system' (520497 KB)...
OKAY [ 11.894s]
writing 'system'...
OKAY [ 3.155s]
finished. total time: 15.052s
target reported max download size of 534773760 bytes
sending 'system' (250221 KB)...
OKAY [ 5.732s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 6.345s
error: cannot load 'system.img_sparsechunk.7'
target reported max download size of 534773760 bytes
sending 'modem' (75092 KB)...
OKAY [ 1.721s]
writing 'modem'...
OKAY [ 0.513s]
finished. total time: 2.238s
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.032s]
finished. total time: 0.033s
target reported max download size of 534773760 bytes
sending 'fsg' (2936 KB)...
OKAY [ 0.102s]
writing 'fsg'...
OKAY [ 0.056s]
finished. total time: 0.161s
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.023s
erasing 'userdata'...
OKAY [ 0.067s]
finished. total time: 0.068s
rebooting...
Really sorry about the delay.
bump
Try one of these (or the latest) from here:
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
Make sure you use these fastboot commands:
Code:
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 dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot erase userdata
fastboot erase cache
fastboot oem fb_mode_clear
fastboot reboot
After it reboots, if it's still giving you problems , here is what I did.
I re-entered the ADB fastboot menu and on the side, using the volume keys , I selected "FACTORY" and then clicked the power button. I know sounds stupid, but that got my phone to boot to the OS.

xt1792 failed to lock bootloader "Still require signed boot.img"

Hello!
I trying to re-lock the bootloader of my moto g5s xt1792. I tried multiple commands, stock roms and a LMSA downloaded rom but i still receive the message "Still require signed boot.img".
I tried to do a rescue in lmsa but without success.
I searched too alot in xda and in similar forums, i have been in this problem for several months.
Code:
fastboot oem lock
fastboot oem lock
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 erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system system.img_sparsechunk.9
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot reboot
Code:
Microsoft Windows [versão 10.0.17763.1397]
(c) 2018 Microsoft Corporation. Todos os direitos reservados.
C:\Users\henrique\Desktop\retbr>fastboot oem lock
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.010s]
Finished. Total time: 0.010s
C:\Users\henrique\Desktop\retbr>fastboot oem lock
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.009s]
Finished. Total time: 0.009s
C:\Users\henrique\Desktop\retbr>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.000s
C:\Users\henrique\Desktop\retbr>fastboot oem fb_mode_set
OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\henrique\Desktop\retbr>fastboot flash partition gpt.bin
(bootloader) is-logical:partition: 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) Flashing backup GPT image...
OKAY [ 0.090s]
Finished. Total time: 0.295s
C:\Users\henrique\Desktop\retbr>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.349s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.557s]
Finished. Total time: 0.940s
C:\Users\henrique\Desktop\retbr>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (67978 KB) OKAY [ 2.838s]
Writing 'modem' OKAY [ 1.074s]
Finished. Total time: 3.990s
C:\Users\henrique\Desktop\retbr>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (3560 KB) OKAY [ 0.335s]
Writing 'fsg' OKAY [ 0.120s]
Finished. Total time: 0.500s
C:\Users\henrique\Desktop\retbr>fastboot erase modemst1
Erasing 'modemst1' OKAY [ 0.041s]
Finished. Total time: 0.041s
C:\Users\henrique\Desktop\retbr>fastboot erase modemst2
Erasing 'modemst2' OKAY [ 0.030s]
Finished. Total time: 0.050s
C:\Users\henrique\Desktop\retbr>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.835s]
Writing 'dsp' OKAY [ 0.316s]
Finished. Total time: 1.207s
C:\Users\henrique\Desktop\retbr>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2195 KB) OKAY [ 0.220s]
Writing 'logo' OKAY [ 0.113s]
Finished. Total time: 0.404s
C:\Users\henrique\Desktop\retbr>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.630s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.480s]
Finished. Total time: 1.327s
C:\Users\henrique\Desktop\retbr>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.820s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 1.015s]
Finished. Total time: 1.865s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256294 KB) OKAY [ 10.125s]
Writing 'system' OKAY [ 4.450s]
Finished. Total time: 14.725s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256762 KB) OKAY [ 10.182s]
Writing 'system' OKAY [ 3.325s]
Finished. Total time: 13.580s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (255764 KB) OKAY [ 10.380s]
Writing 'system' OKAY [ 3.540s]
Finished. Total time: 14.040s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260630 KB) OKAY [ 10.360s]
Writing 'system' OKAY [ 3.420s]
Finished. Total time: 13.882s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257521 KB) OKAY [ 10.419s]
Writing 'system' OKAY [ 3.372s]
Finished. Total time: 13.880s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (245941 KB) OKAY [ 9.810s]
Writing 'system' OKAY [ 3.210s]
Finished. Total time: 13.080s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (258569 KB) OKAY [ 10.242s]
Writing 'system' OKAY [ 3.265s]
Finished. Total time: 13.550s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (251493 KB) OKAY [ 10.060s]
Writing 'system' OKAY [ 3.770s]
Finished. Total time: 13.990s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (257933 KB) OKAY [ 10.150s]
Writing 'system' OKAY [ 3.770s]
Finished. Total time: 14.147s
C:\Users\henrique\Desktop\retbr>fastboot flash system system.img_sparsechunk.9
(bootloader) is-logical:system: not found
Sending 'system' (214096 KB) OKAY [ 8.465s]
Writing 'system' OKAY [ 3.831s]
Finished. Total time: 12.360s
C:\Users\henrique\Desktop\retbr>fastboot flash oem oem.img
(bootloader) is-logical:oem: not found
Sending 'oem' (247426 KB) OKAY [ 9.880s]
Writing 'oem' OKAY [ 3.290s]
Finished. Total time: 13.240s
C:\Users\henrique\Desktop\retbr>fastboot erase cache
Erasing 'cache' OKAY [ 0.010s]
Finished. Total time: 0.020s
C:\Users\henrique\Desktop\retbr>fastboot erase userdata
Erasing 'userdata' OKAY [ 4.688s]
Finished. Total time: 4.695s
C:\Users\henrique\Desktop\retbr>fastboot erase DDR
Erasing 'DDR' OKAY [ 0.020s]
Finished. Total time: 0.030s
C:\Users\henrique\Desktop\retbr>fastboot oem fb_mode_clear
OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\henrique\Desktop\retbr>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.000s]
Finished. Total time: 0.010s
C:\Users\henrique\Desktop\retbr>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.000s]
Finished. Total time: 0.009s
I would appreciate any help
Thank you
Try
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
Fastboot reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
And the rest...
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
Fastboot reboot bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
And the rest...
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I can't lock bootloader due to "(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer"
Now i have the oem unlocking greyed out, i can't allow oem unlock because it says that is already unlocked. I flashed twrp and rooted with magisk to force allow oem unlocking but it failed. In a second try i did a factory reset after rooting but it also failed to allow oem unlock.
Code:
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.000s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>Fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.000s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.000s]
Finished. Total time: 0.000s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem lock
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem lock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.008s]
Finished. Total time: 0.016s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
Finished. Total time: 0.000s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
OKAY [ 0.000s]
Finished. Total time: 0.008s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
(bootloader) is-logical:partition: not found
Sending 'partition' (45 KB) OKAY [ 0.163s]
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) Flashing backup GPT image...
OKAY [ 0.116s]
Finished. Total time: 0.311s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.358s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.578s]
Finished. Total time: 0.968s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (67978 KB) OKAY [ 2.589s]
Writing 'modem' OKAY [ 1.070s]
Finished. Total time: 3.713s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (3560 KB) OKAY [ 0.296s]
Writing 'fsg' OKAY [ 0.120s]
Finished. Total time: 0.448s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
Erasing 'modemst1' OKAY [ 0.040s]
Finished. Total time: 0.040s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
Erasing 'modemst2' OKAY [ 0.033s]
Finished. Total time: 0.040s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.772s]
Writing 'dsp' OKAY [ 0.282s]
Finished. Total time: 1.078s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2195 KB) OKAY [ 0.256s]
Writing 'logo' OKAY [ 0.112s]
Finished. Total time: 0.400s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.613s]
Writing 'boot' (bootloader) Image signed with key bad key
OKAY [ 0.378s]
Finished. Total time: 1.231s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.761s]
Writing 'recovery' (bootloader) Image signed with key bad key
OKAY [ 0.414s]
Finished. Total time: 1.195s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (256294 KB) OKAY [ 9.651s]
Writing 'system' OKAY [ 4.120s]
Finished. Total time: 13.850s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256762 KB) OKAY [ 9.515s]
Writing 'system' OKAY [ 3.308s]
Finished. Total time: 12.883s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (255764 KB) OKAY [ 9.226s]
Writing 'system' OKAY [ 3.520s]
Finished. Total time: 12.858s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (260630 KB) OKAY [ 9.383s]
Writing 'system' OKAY [ 3.412s]
Finished. Total time: 12.846s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (257521 KB) OKAY [ 9.228s]
Writing 'system' OKAY [ 3.391s]
Finished. Total time: 12.655s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (245941 KB) OKAY [ 8.820s]
Writing 'system' OKAY [ 3.200s]
Finished. Total time: 12.044s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (258569 KB) OKAY [ 9.291s]
Writing 'system' OKAY [ 3.262s]
Finished. Total time: 12.612s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (251493 KB) OKAY [ 9.190s]
Writing 'system' OKAY [ 3.742s]
Finished. Total time: 13.034s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (257933 KB) OKAY [ 9.402s]
Writing 'system' OKAY [ 3.731s]
Finished. Total time: 13.272s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_sparsechunk.9
(bootloader) is-logical:system: not found
Sending 'system' (214096 KB) OKAY [ 7.731s]
Writing 'system' OKAY [ 2.703s]
Finished. Total time: 10.466s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
(bootloader) is-logical:oem: not found
Sending 'oem' (247426 KB) OKAY [ 8.946s]
Writing 'oem' OKAY [ 3.281s]
Finished. Total time: 12.290s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
Erasing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.031s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.216s]
Finished. Total time: 0.216s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase DDR
Erasing 'DDR' OKAY [ 0.000s]
Finished. Total time: 0.016s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
OKAY [ 0.016s]
Finished. Total time: 0.016s
C:\Users\henrique\Downloads\XT1792_MONTANA_RETBR_8.1.0_OPPS28.65-37-7-11_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem lock
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.000s]
Finished. Total time: 0.016s
fastboot getvar all
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8937-BC.12
(bootloader) product: montana
(bootloader) board: montana
(bootloader) secure: yes
(bootloader) hwrev: P3
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8937
(bootloader) serialno: 0044243152
(bootloader) cid: 0x0032
(bootloader) channelid: 0x17
(bootloader) uid: EBC7344E00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 535822336
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: ---------------------hidden
(bootloader) meid:
(bootloader) date: 02-19-2018
(bootloader) sku: XT1792
(bootloader) carrier_sku:
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/montana/montana:8.1.0/OPP
(bootloader) ro.build.fingerprint[1]: S28.65-37-7-11/7f8a6:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.281.15.montana.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8937_37.13.03.75R MONTANA_BRAZILDSDS_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g1c8179f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.8 (GCC)
(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Sun Aug 11 12:40:44 CDT
(bootloader) kernel.version[3]: 2019
(bootloader) sbl1.git: git=MBM-NG-VBC.12-0-g77d3670
(bootloader) rpm.git: git=bd76357-dirty
(bootloader) tz.git: git=57946dd
(bootloader) devcfg.git: git=57946dd
(bootloader) keymaster.git: git=57946dd
(bootloader) cmnlib.git: git=57946dd
(bootloader) cmnlib64.git: git=57946dd
(bootloader) prov.git: git=57946dd
(bootloader) aboot.git: git=MBM-NG-VBC.12-0-g0b9dae9
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: timbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.290s
What i can do?
obs: the only boot.img that the xt1792 recognized as signed was the magisk_patched.img
Hey did you manage to lock the bootloader? I'm having the same issue in my Motorola one p30 play which is a dual partition slot device.

Trying to unbrick my XT1710-07. Any hope for me?

Today I was using my stock (bootloader locked, no twrp) XT1710-07 and it suddenly froze. I could reboot once, past the PIN screen ok, and then it rebooted and never got out of the Moto Logo screen.
So I entered fastboot, tried to get to Recover mode, but I was getting an error like 'Linux failed to boot', instructing to get Software Repair Assistant.
So I downloaded it, it downloaded the following firmware: ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.
When I hit Rescue, it gets to 47% and then I get the error: "Fastboot Flash failed. Please try again."
Then I started digging all threads here that could help me revive my phone.
Once I got to this, I ran the bat file inside LMSA downloaded rom folder and got this:
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>bat_flashfile_retus_7.bat
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.004s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
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) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.090s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.116s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.351s]
finished. total time: 0.472s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62728 KB)...
OKAY [ 1.349s]
writing 'modem'...
OKAY [ 0.531s]
finished. total time: 1.884s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (4124 KB)...
OKAY [ 0.091s]
writing 'fsg'...
OKAY [ 0.067s]
finished. total time: 0.162s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.032s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.019s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.352s]
writing 'dsp'...
OKAY [ 0.159s]
finished. total time: 0.515s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.083s]
writing 'logo'...
OKAY [ 0.053s]
finished. total time: 0.140s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.322s]
finished. total time: 0.692s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.450s]
writing 'recovery'...
OKAY [ 0.388s]
finished. total time: 0.842s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.872s]
writing 'system'...
OKAY [ 4.517s]
finished. total time: 10.392s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262143 KB)...
OKAY [ 5.691s]
writing 'system'...
OKAY [ 4.308s]
finished. total time: 10.004s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (258109 KB)...
OKAY [ 5.582s]
writing 'system'...
OKAY [ 5.062s]
finished. total time: 10.648s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (257493 KB)...
OKAY [ 5.527s]
writing 'system'...
OKAY [ 4.124s]
finished. total time: 9.655s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (230133 KB)...
OKAY [ 4.994s]
writing 'system'...
OKAY [ 3.684s]
finished. total time: 8.682s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 5.611s]
writing 'system'...
OKAY [ 4.173s]
finished. total time: 9.788s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 5.627s]
writing 'system'...
OKAY [ 4.250s]
finished. total time: 9.880s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (254369 KB)...
OKAY [ 5.535s]
writing 'system'...
OKAY [ 4.337s]
finished. total time: 9.875s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (250337 KB)...
OKAY [ 5.446s]
writing 'system'...
OKAY [ 4.844s]
finished. total time: 10.294s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.638s]
writing 'system'...
OKAY [ 4.201s]
finished. total time: 9.844s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (249593 KB)...
OKAY [ 5.355s]
writing 'system'...
OKAY [ 3.984s]
finished. total time: 9.345s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.11
target reported max download size of 534773760 bytes
sending 'system' (240710 KB)...
OKAY [ 5.150s]
writing 'system'...
OKAY [ 25.195s]
finished. total time: 30.352s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.12
target reported max download size of 534773760 bytes
sending 'system' (89960 KB)...
OKAY [ 1.926s]
writing 'system'...
OKAY [ 1.424s]
finished. total time: 3.355s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.13
error: cannot load 'system.img_sparsechunk.13': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135836 KB)...
OKAY [ 2.910s]
writing 'oem'...
OKAY [ 12.723s]
finished. total time: 15.636s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.037s]
finished. total time: 0.038s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.006s]
finished. total time: 0.007s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.004s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>pause
No luck: oem fb_mode set and clear don't work, and flashing gpt doesn't work as well.
Now, when I power on the phone, it falls back to fastboot screen with:
Failed to verify hab image boot
failed to validade boot image
ERROR: Failed to pass validation. backup to fastboot
Boot up failed
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-albus_retail-b625135-190911
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 003967xxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: C286B05500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: ---removed---
(bootloader) meid:
(bootloader) date: 10-25-2017
(bootloader) sku: XT1710-07
(bootloader) carrier_sku:
(bootloader) battid: SNN5983B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Oct 24 9:34:20 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:9/PPS29.133-3
(bootloader) ro.build.fingerprint[1]: 0/ab8b4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.30.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M8953P_52.61.07.98R ALBUS_BRAZILDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g764584c (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Wed Sep 11 13:20:26 CDT 2019
(bootloader) sbl1.git: MBM-2.1-albus_retail-5e07748-190911
(bootloader) rpm.git: MBM-2.1-albus_retail-218e5af-190911
(bootloader) tz.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) devcfg.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) keymaster.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) cmnlib.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) cmnlib64.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) prov.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) aboot.git: MBM-2.1-albus_retail-b625135-190911
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.046s
Any chance for my phone to work again (stock or not, locked or not...)?
Is it possible to backup data partition to SD card at this point (fastboot working)?
I really appreciate any help.
No, here the guys see your questions (or not) and just ignore them.
bigods said:
Today I was using my stock (bootloader locked, no twrp) XT1710-07 and it suddenly froze. I could reboot once, past the PIN screen ok, and then it rebooted and never got out of the Moto Logo screen.
So I entered fastboot, tried to get to Recover mode, but I was getting an error like 'Linux failed to boot', instructing to get Software Repair Assistant.
So I downloaded it, it downloaded the following firmware: ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.
When I hit Rescue, it gets to 47% and then I get the error: "Fastboot Flash failed. Please try again."
Then I started digging all threads here that could help me revive my phone.
Once I got to this, I ran the bat file inside LMSA downloaded rom folder and got this:
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>bat_flashfile_retus_7.bat
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.004s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
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) Flashing backup GPT image...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.090s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.116s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.351s]
finished. total time: 0.472s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62728 KB)...
OKAY [ 1.349s]
writing 'modem'...
OKAY [ 0.531s]
finished. total time: 1.884s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (4124 KB)...
OKAY [ 0.091s]
writing 'fsg'...
OKAY [ 0.067s]
finished. total time: 0.162s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.032s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.019s]
finished. total time: 0.024s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.352s]
writing 'dsp'...
OKAY [ 0.159s]
finished. total time: 0.515s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2192 KB)...
OKAY [ 0.083s]
writing 'logo'...
OKAY [ 0.053s]
finished. total time: 0.140s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.322s]
finished. total time: 0.692s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.450s]
writing 'recovery'...
OKAY [ 0.388s]
finished. total time: 0.842s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.872s]
writing 'system'...
OKAY [ 4.517s]
finished. total time: 10.392s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262143 KB)...
OKAY [ 5.691s]
writing 'system'...
OKAY [ 4.308s]
finished. total time: 10.004s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (258109 KB)...
OKAY [ 5.582s]
writing 'system'...
OKAY [ 5.062s]
finished. total time: 10.648s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (257493 KB)...
OKAY [ 5.527s]
writing 'system'...
OKAY [ 4.124s]
finished. total time: 9.655s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (230133 KB)...
OKAY [ 4.994s]
writing 'system'...
OKAY [ 3.684s]
finished. total time: 8.682s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 5.611s]
writing 'system'...
OKAY [ 4.173s]
finished. total time: 9.788s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 5.627s]
writing 'system'...
OKAY [ 4.250s]
finished. total time: 9.880s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (254369 KB)...
OKAY [ 5.535s]
writing 'system'...
OKAY [ 4.337s]
finished. total time: 9.875s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (250337 KB)...
OKAY [ 5.446s]
writing 'system'...
OKAY [ 4.844s]
finished. total time: 10.294s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.638s]
writing 'system'...
OKAY [ 4.201s]
finished. total time: 9.844s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.10
target reported max download size of 534773760 bytes
sending 'system' (249593 KB)...
OKAY [ 5.355s]
writing 'system'...
OKAY [ 3.984s]
finished. total time: 9.345s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.11
target reported max download size of 534773760 bytes
sending 'system' (240710 KB)...
OKAY [ 5.150s]
writing 'system'...
OKAY [ 25.195s]
finished. total time: 30.352s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.12
target reported max download size of 534773760 bytes
sending 'system' (89960 KB)...
OKAY [ 1.926s]
writing 'system'...
OKAY [ 1.424s]
finished. total time: 3.355s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash system system.img_sparsechunk.13
error: cannot load 'system.img_sparsechunk.13': No such file or directory
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (135836 KB)...
OKAY [ 2.910s]
writing 'oem'...
OKAY [ 12.723s]
finished. total time: 15.636s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase carrier
erasing 'carrier'...
OKAY [ 0.037s]
finished. total time: 0.038s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.006s]
finished. total time: 0.007s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot erase DDR
erasing 'DDR'...
OKAY [ 0.003s]
finished. total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.004s
C:\ProgramData\LMSA\Download\RomFiles\ALBUS_PPS29.133_30_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC_SVC.xml>pause
No luck: oem fb_mode set and clear don't work, and flashing gpt doesn't work as well.
Now, when I power on the phone, it falls back to fastboot screen with:
Failed to verify hab image boot
failed to validade boot image
ERROR: Failed to pass validation. backup to fastboot
Boot up failed
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-albus_retail-b625135-190911
(bootloader) product: albus
(bootloader) board: albus
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 5
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2
(bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 003967xxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: C286B05500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: ---removed---
(bootloader) meid:
(bootloader) date: 10-25-2017
(bootloader) sku: XT1710-07
(bootloader) carrier_sku:
(bootloader) battid: SNN5983B
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Oct 24 9:34:20 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/albus/albus:9/PPS29.133-3
(bootloader) ro.build.fingerprint[1]: 0/ab8b4:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.29.11.30.albus.retai
(bootloader) ro.build.version.full[1]: l.en.US
(bootloader) ro.build.version.qcom: LA.UM.7.6.r1-04300-89xx.0
(bootloader) version-baseband: M8953P_52.61.07.98R ALBUS_BRAZILDSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.120-perf-g764584c (hu
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20
(bootloader) kernel.version[2]: 150123 (prerelease) (GCC) ) #1 SMP PREEM
(bootloader) kernel.version[3]: PT Wed Sep 11 13:20:26 CDT 2019
(bootloader) sbl1.git: MBM-2.1-albus_retail-5e07748-190911
(bootloader) rpm.git: MBM-2.1-albus_retail-218e5af-190911
(bootloader) tz.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) devcfg.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) keymaster.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) cmnlib.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) cmnlib64.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) prov.git: MBM-2.1-albus_retail-b272488-190911
(bootloader) aboot.git: MBM-2.1-albus_retail-b625135-190911
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retbr
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.046s
Any chance for my phone to work again (stock or not, locked or not...)?
Is it possible to backup data partition to SD card at this point (fastboot working)?
I really appreciate any help.
Click to expand...
Click to collapse
Have you tried getting your phone into QCOM or 9008 mode? Look up a couple of tutorials, if you can then i think i can help
Rknk said:
No, here the guys see your questions (or not) and just ignore them.
Click to expand...
Click to collapse
It's not that, so much that this issue is kind of non-recoverable, and can be caused by a myriad of things, from dead emmc, to bad flashes, to the security chip on the soc randomly dying
No QCOM
marcost22 said:
Have you tried getting your phone into QCOM or 9008 mode? Look up a couple of tutorials, if you can then i think i can help
Click to expand...
Click to collapse
In the recovery menu, when I select QCOM, I get the same error:
Failed to verify hab image boot
failed to validade boot image
ERROR: Failed to pass validation. backup to fastboot
Boot up failed​
Additionally, when I try to run the blankflash.bat, the prompt gets stuck at "< waiting for device >", although it responds for fastboot commands.
bigods said:
In the recovery menu, when I select QCOM, I get the same error:
Failed to verify hab image boot
failed to validade boot image
ERROR: Failed to pass validation. backup to fastboot
Boot up failed​
Additionally, when I try to run the blankflash.bat, the prompt gets stuck at "< waiting for device >", although it responds for fastboot commands.
Click to expand...
Click to collapse
QCOM or 9008 mode can only be accesed that way if you have working system; look up any of the other way
marcost22 said:
QCOM or 9008 mode can only be accesed that way if you have working system; look up any of the other way
Click to expand...
Click to collapse
I'm trying everything I find to make it enter Qcom mode, no success for now.
I saw your other post with qcom mode directions, but phonlab lessons are paid, and too expensive for me (in dollars). I wonder what other information those lessons contain besides installing all the right Qualcomm USB drivers.
I tried too this other guy idea to force it in QCOM mode by shorting USB cable D+ to GND, but it didn't work too.
I wonder if is there any way to do it without an Octoplus (or another) box.
bigods said:
I'm trying everything I find to make it enter Qcom mode, no success for now.
I saw your other post with qcom mode directions, but phonlab lessons are paid, and too expensive for me (in dollars). I wonder what other information those lessons contain besides installing all the right Qualcomm USB drivers.
I tried too this other guy idea to force it in QCOM mode by shorting USB cable D+ to GND, but it didn't work too.
I wonder if is there any way to do it without an Octoplus (or another) box.
Click to expand...
Click to collapse
I've got nothing for you, that's all i know. Fortunately for me my phone never gave me troubles, so all i know is what i've told you

Moto G5 Plus totally dead, stuck on AP Fastboot Flash Mode (Secure)

Hello friends,
Plz help my Moto G5 Plus xt686 is totally dead. I tried flashing stock rom via fastboot. But it's not working, phone still in fastboot stuck condition. Also tried RSD lite tool and Lenovo repair assistant both are not reading my device. Tried unlocking bootloader but getting read datablock error. Tried flashing naugat and oreo roms. Plz spare your valuable time to help me out. Regards.
Kumarvicky12 said:
Hello friends,
Plz help my Moto G5 Plus xt686 is totally dead. I tried flashing stock rom via fastboot. But it's not working, phone still in fastboot stuck condition. Also tried RSD lite tool and Lenovo repair assistant both are not reading my device. Tried unlocking bootloader but getting read datablock error. Tried flashing naugat and oreo roms. Plz spare your valuable time to help me out. Regards.
Click to expand...
Click to collapse
Did you Try flashing latest stock firmware, and did bootloader and gpt got flashed successful?
Nothing got flashed, bootloader, gpt everything failed.
Kumarvicky12 said:
Nothing got flashed, bootloader, gpt everything failed.
Click to expand...
Click to collapse
What error it give?
riyan65 said:
What error it give?
Click to expand...
Click to collapse
plz go through logs
C:\Minimal ADB and Fastboot>echo off
max-sparse-size: 268435456
finished. total time: 0.000s
...
FAILED (remote failure)
finished. total time: 0.016s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
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 failure)
finished. total time: 0.086s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.125s]
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 failure)
finished. total time: 0.328s
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 1.578s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.594s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.369s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.377s
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.047s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.672s
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 5.670s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.718s
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 5.660s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.676s
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 5.473s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.489s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.770s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.785s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.771s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.786s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.779s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.795s
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 5.542s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.558s
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 5.802s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.833s
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 5.614s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.629s
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.315s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.362s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'DDR'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.000s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
...
FAILED (remote failure)
finished. total time: 0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .
I believe you have a problem with your phone internal memory.
Enviado de meu Moto G (5) Plus usando o Tapatalk
You flashed stock Oreo using fastboot commands or using a zip file and TWRP recovery? Was the bootloader unlocked before flashing? You never want to downgrade the firmware for risk of bricking due to the bootloader version. From the picture it looks like you have the Oreo bootloader.
Just guessing, but if trying to unlock the bootloader then you also need access to Motorola's website...at least that's what this web article says: https://devsjournal.com/moto-g5-plus-unlocking-the-bootloader.html
Kumarvicky12 said:
plz go through logs
C:\Minimal ADB and Fastboot>echo off
max-sparse-size: 268435456
finished. total time: 0.000s
...
FAILED (remote failure)
finished. total time: 0.016s
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ -0.000s]
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 failure)
finished. total time: 0.086s
target reported max download size of 534773760 bytes
sending 'bootloader' (5115 KB)...
OKAY [ 0.125s]
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 failure)
finished. total time: 0.328s
target reported max download size of 534773760 bytes
sending 'modem' (71921 KB)...
OKAY [ 1.578s]
writing 'modem'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 1.594s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.369s]
writing 'dsp'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition dsp
FAILED (remote failure)
finished. total time: 0.377s
target reported max download size of 534773760 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.047s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.062s
target reported max download size of 534773760 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.375s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.547s
target reported max download size of 534773760 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.453s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.672s
target reported max download size of 534773760 bytes
sending 'system' (258396 KB)...
OKAY [ 5.670s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.718s
target reported max download size of 534773760 bytes
sending 'system' (256514 KB)...
OKAY [ 5.660s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.676s
target reported max download size of 534773760 bytes
sending 'system' (246302 KB)...
OKAY [ 5.473s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.489s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.770s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.785s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.771s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.786s
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 5.779s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.795s
target reported max download size of 534773760 bytes
sending 'system' (250531 KB)...
OKAY [ 5.542s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.558s
target reported max download size of 534773760 bytes
sending 'system' (262059 KB)...
OKAY [ 5.802s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.833s
target reported max download size of 534773760 bytes
sending 'system' (254142 KB)...
OKAY [ 5.614s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 5.629s
target reported max download size of 534773760 bytes
sending 'oem' (104608 KB)...
OKAY [ 2.315s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.362s
erasing 'modemst1'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'modemst2'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.016s
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: -0.000s
erasing 'DDR'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.000s
target reported max download size of 534773760 bytes
sending 'fsg' (3012 KB)...
OKAY [ 0.063s]
writing 'fsg'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.078s
...
FAILED (remote failure)
finished. total time: 0.000s
-------------------------------------------------------------------------
please scroll up and check your flash for any errors
-------------------------------------------------------------------------
Press any key to continue . . .
Click to expand...
Click to collapse
Mostly you device gpt table got corrupted or your emmc storage is failing. I suggest you to flash gpt table of different firmware ,Maybe it will help.
Ok will give a try
roundaway said:
You flashed stock Oreo using fastboot commands or using a zip file and TWRP recovery? Was the bootloader unlocked before flashing? You never want to downgrade the firmware for risk of bricking due to the bootloader version. From the picture it looks like you have the Oreo bootloader.
Just guessing, but if trying to unlock the bootloader then you also need access to Motorola's website...at least that's what this web article says: https://devsjournal.com/moto-g5-plus-unlocking-the-bootloader.html
Click to expand...
Click to collapse
i never tried any custom ro on this mobile. it was neither unlocked. it automatically got in this condition. i didn't done anything with it.
cybernetus said:
I believe you have a problem with your phone internal memory.
Enviado de meu Moto G (5) Plus usando o Tapatalk
Click to expand...
Click to collapse
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: 6839d8c1
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 4FA26E6C00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.156s
riyan65 said:
Mostly you device gpt table got corrupted or your emmc storage is failing. I suggest you to flash gpt table of different firmware ,Maybe it will help.
Click to expand...
Click to collapse
Different firmware means from other moto devices....??
roundaway said:
You flashed stock Oreo using fastboot commands or using a zip file and TWRP recovery? Was the bootloader unlocked before flashing? You never want to downgrade the firmware for risk of bricking due to the bootloader version. From the picture it looks like you have the Oreo bootloader.
Just guessing, but if trying to unlock the bootloader then you also need access to Motorola's website...at least that's what this web article says: https://devsjournal.com/moto-g5-plus-unlocking-the-bootloader.html
Click to expand...
Click to collapse
my device is not getting recognised as adb device, but only fastboot device, i am unable to get unlock data. plz check below
C:\Minimal ADB and Fastboot>adb device
adb: usage: unknown command device
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot devices
6839d8c1 fastboot
C:\Minimal ADB and Fastboot>
How about the gpt table? You try to flash t this?
Enviado de meu Moto G (5) Plus usando o Tapatalk
---------- Post added at 10:58 PM ---------- Previous post was at 10:56 PM ----------
Kumarvicky12 said:
Different firmware means from other moto devices....??
Click to expand...
Click to collapse
From another rom. Lineage etc. I believe.
Enviado de meu Moto G (5) Plus usando o Tapatalk
Kumarvicky12 said:
my device is not getting recognised as adb device, but only fastboot device, i am unable to get unlock data. plz check below
C:\Minimal ADB and Fastboot>adb device
adb: usage: unknown command device
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot devices
6839d8c1 fastboot
C:\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Here's what I recommend. Download the official Motorola G5 Plus (Potter) Oreo firmware, POTTER_RETAIL_8.1.0_OPSS28.85-17-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from whatever site you can find it (https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/). Extract the zip file in the same folder as fastboot.exe.
With the phone in fastboot mode execute each of the following commands one at a time:
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
If the phone reboots and starts up then great. After it starts go to Settings and enable Developer Options. In Developer Options enable ADB and OEM Unlock.
If the phone doesn't boot properly then sorry. You will have tried to install the official retail version.
Kumarvicky12 said:
Different firmware means from other moto devices....??
Click to expand...
Click to collapse
Different firmware= different region firmware like retain
same phone same error
I have the same phone and got these results with roundaway suggestion
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.018s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.048s
the phone shows no IMEI "0000000" no baseband "blank space" and no product/variant "potter 0000000000000000" i belive it is a hardware malfunction at this point I have tried everything I could find in the forums
MaxPowell2 said:
I have the same phone and got these results with roundaway suggestion
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
C:\Users\Ema-Maby\Desktop\Programas\motoG5PPLUS\CEDRIC_RETAIL_8.1.0_OPPS28.85-16-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.018s]
writing 'partition'...
(bootloader) no suitable package!
FAILED (remote failure)
finished. total time: 0.048s
the phone shows no IMEI "0000000" no baseband "blank space" and no product/variant "potter 0000000000000000" i belive it is a hardware malfunction at this point I have tried everything I could find in the forums
Click to expand...
Click to collapse
Confirm the ROM you tried to install is the correct one for your phone:
Moto G5 Plus = potter
Moto G5 = cedric
Also, the files to be flashed should be in the same folder as the fastboot.exe files.
There are multiple problems with the phones. One is it won't accept a fastboot flash of factory firmware. Second problem might show up after/if the phone reboots and that is the infamous IMEI = 0.
The OP's getvar all command didn't reveal the (bootloader) ro.build.fingerprint information which would tell us the firmware version installed. However, the bootloader number appears to be the current Oreo version. That was one reason for flashing the latest version of the Oreo firmware.
The only other thing to try would be to download the latest version of TWRP into the same folder as fastboot.exe and try:
fastboot boot twrp.img (where twrp.img is the filename of the latest twrp)
If the phone boots into twrp then download the latest twrp flashable Oreo and copy and paste to the phone. Try and Install it. Big longshot because the bootloader is probably locked..
Dont worry dude, I have been there and came out of it.
First of all sorry for being late.
What you have to do is
1. connect your phone to your pc with with a pc or laptop.
L2. Download Lenovo Moto Smart Assistant lll from the Official website. Just search on google.
3. Make sure you install it on the C: Drive only, with administrative rights.
4. Run it, it will ask for your Lenovo login id. Now you need to go to Lenovos website from the browser, register a new one.
And after 5-10 mins login with the same id.
5. Well, if you are unable to login due to un responsive page, use a vpn .
6. After you login go for "Rescue".
7. Choose the option which says, Phone not able to boot or start.
8. It would automatically detect your device if it's connected to a pc with a cable and is in fastboot mode.
9. It fails to detect sometimes, so you can try manually enter your device.
10.Now it would download the latest stock rom, there would be a small download text which is hyperlinked.
11. Once completed it might ask to "Rescue".
It will start working, it might look like it's stuck, but it not, it can take from 5 mins to 30 mins or even more.
12. After the process is complete, just boot your phone normally, or it might boot automatically.
13. Enjoy.
If there's something wrong any problem or error,
Let me know.
Akahat27 said:
Dont worry dude, I have been there and came out of it.
First of all sorry for being late.
What you have to do is
1. connect your phone to your pc with with a pc or laptop.
L2. Download Lenovo Moto Smart Assistant lll from the Official website. Just search on google.
3. Make sure you install it on the C: Drive only, with administrative rights.
4. Run it, it will ask for your Lenovo login id. Now you need to go to Lenovos website from the browser, register a new one.
And after 5-10 mins login with the same id.
5. Well, if you are unable to login due to un responsive page, use a vpn .
6. After you login go for "Rescue".
7. Choose the option which says, Phone not able to boot or start.
8. It would automatically detect your device if it's connected to a pc with a cable and is in fastboot mode.
9. It fails to detect sometimes, so you can try manually enter your device.
10.Now it would download the latest stock rom, there would be a small download text which is hyperlinked.
11. Once completed it might ask to "Rescue".
It will start working, it might look like it's stuck, but it not, it can take from 5 mins to 30 mins or even more.
12. After the process is complete, just boot your phone normally, or it might boot automatically.
13. Enjoy.
If there's something wrong any problem or error,
Let me know.
Click to expand...
Click to collapse
This didn't work. Smart Assistant couldn't detect the device I am trying to Rescue. Can you suggest something else?

[Moto G8 XT2045-1] How to enter EDL when phone died?

Hello, there!
I recently bought a XT2045-1 and wanted to install a custom ROM. Bellow are the results of the fastboot get_var all when the phone had it bootloader still locked:
Spoiler: fastboot getvar all
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-rav_retail-a863e9dc07-220131
(bootloader) product: rav
(bootloader) board: rav
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: XXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x19
(bootloader) uid: 15FEC0E5
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 805263360
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: XXXXXXXX
(bootloader) imei2: XXXXXXXX
(bootloader) meid:
(bootloader) date: 02-13-2020
(bootloader) sku: XT2045-1
(bootloader) carrier_sku: XT2045-1
(bootloader) battid: SB18C51711
(bootloader) battery-voltage: 4040
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retbr
(bootloader) ro.build.fingerprint[0]: motorola/rav_retail/rav:11/RPJS31.
(bootloader) ro.build.fingerprint[1]: Q4U-47-35-15/39557:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.qcom: LA.UM.9.11.r1-02100-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.49R RAV_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.180-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Mon J
(bootloader) kernel.version[4]: an 31 04:01:49 CST 2022
(bootloader) git:xbl: MBM-3.0-rav_retail-1186df2c3-220131
(bootloader) git:xbl_config: MBM-3.0-rav_retail-1186df2c3-220131
(bootloader) git:rpm: MBM-3.0-rav_retail-2579863-220131
(bootloader) git:tz: MBM-3.0-rav_retail-1374152f-220131
(bootloader) git:hyp: MBM-3.0-rav_retail-1374152f-220131
(bootloader) git:devcfg: MBM-3.0-rav_retail-1374152f-220131
(bootloader) git:cmnlib: MBM-3.0-rav_retail-1374152f-220131
(bootloader) git:cmnlib64: MBM-3.0-rav_retail-1374152f-220131
(bootloader) git:keymaster: MBM-3.0-rav_retail-026953b-220131
(bootloader) git:prov: MBM-3.0-rav_retail-1374152f-220131
(bootloader) git:abl: MBM-3.0-rav_retail-a863e9dc07-220131
(bootloader) git:qupfw: MBM-3.0-rav_retail-919849b-220131
(bootloader) git:uefisecapp: MBM-3.0-rav_retail-1374152f-220131
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C68362
(bootloader) primary-display: tm_nt36526_hd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total time: 0.065s
Searching XDA, I've found that all SOFIAR ROMs require that the phone has Android 10 installed. As my phone already had Android 11, I unlocked the bootloader and used this guide to downgrade:
How to downgrade Android 11 to 10
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to...
forum.xda-developers.com
I used XT2045-1_RAV_RETBR_10_QPJS30.63-35-1-15_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet as ro.carrier: retbr, and it seemed that the flash worked as showed below, but got a bootloop.
Spoiler: flash android 10
Code:
max-sparse-size: 268435456
Finished. Total time: 0.000s
OKAY [ 0.005s]
Finished. Total time: 0.005s
Sending 'partition' (37 KB) OKAY [ 0.003s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.361s]
Finished. Total time: 0.365s
Sending 'bootloader' (14204 KB) OKAY [ 0.812s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 11 vs 19
OKAY [ 0.009s]
Finished. Total time: 0.012s
Sending 'radio' (199049 KB) OKAY [ 8.096s]
Writing 'radio' (bootloader) Validating 'radio.default.xml'
(bootloader) Committing 'radio.default.xml'
(bootloader) - flashing 'NON-HLOS.bin' to 'modem'
(bootloader) - flashing 'fsg.mbn' to 'fsg'
(bootloader) - erasing 'modemst1'
(bootloader) - erasing 'modemst2'
OKAY [ 0.918s]
Finished. Total time: 9.024s
Sending 'bluetooth_a' (4608 KB) OKAY [ 0.274s]
Writing 'bluetooth_a' OKAY [ 0.084s]
Finished. Total time: 0.359s
Sending 'dsp_a' (32768 KB) OKAY [ 1.571s]
Writing 'dsp_a' OKAY [ 0.196s]
Finished. Total time: 1.768s
Sending 'logo_a' (1696 KB) OKAY [ 0.086s]
Writing 'logo_a' OKAY [ 0.054s]
Finished. Total time: 0.142s
Sending 'boot_a' (65536 KB) OKAY [ 2.443s]
Writing 'boot_a' OKAY [ 0.557s]
Finished. Total time: 3.571s
Sending 'dtbo_a' (8192 KB) OKAY [ 0.471s]
Writing 'dtbo_a' OKAY [ 0.115s]
Finished. Total time: 0.618s
Sending 'recovery_a' (65536 KB) OKAY [ 2.486s]
Writing 'recovery_a' OKAY [ 0.718s]
Finished. Total time: 3.219s
Sending 'super' (262140 KB) OKAY [ 11.432s]
Writing 'super' OKAY [ 0.058s]
Finished. Total time: 11.575s
Sending 'super' (261932 KB) OKAY [ 11.285s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 13.278s
Sending 'super' (261820 KB) OKAY [ 11.394s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 12.592s
Sending 'super' (261928 KB) OKAY [ 10.722s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.871s
Sending 'super' (261092 KB) OKAY [ 10.227s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.398s
Sending 'super' (249276 KB) OKAY [ 9.868s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.197s
Sending 'super' (262140 KB) OKAY [ 10.308s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.456s
Sending 'super' (262140 KB) OKAY [ 10.065s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.305s
Sending 'super' (262140 KB) OKAY [ 9.511s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 10.663s
Sending 'super' (262140 KB) OKAY [ 10.117s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.262s
Sending 'super' (262140 KB) OKAY [ 9.694s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 10.855s
Sending 'super' (262140 KB) OKAY [ 10.307s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.487s
Sending 'super' (262140 KB) OKAY [ 10.144s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.377s
Sending 'super' (262140 KB) OKAY [ 10.039s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 11.182s
Sending 'super' (147836 KB) OKAY [ 5.548s]
Writing 'super' OKAY [ 0.001s]
Finished. Total time: 6.737s
Erasing 'carrier' OKAY [ 0.040s]
Finished. Total time: 0.814s
Erasing 'userdata' OKAY [ 0.195s]
Finished. Total time: 0.196s
Erasing 'metadata' OKAY [ 0.042s]
Finished. Total time: 0.043s
Erasing 'ddr' OKAY [ 0.044s]
Finished. Total time: 0.044s
OKAY [ 0.003s]
Finished. Total time: 0.003s
-----------------------------------------------------------------------------------------------
English - Process concluded!
Português - Processo concluído!
English - Press any key to restart the phone!
Português - Pressione qualquer tecla para reiniciar o celular!
-----------------------------------------------------------------------------------------------
Done - Press enter to exit
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.201s
Then I decied to use a blankflash to erase eveything and start anew. I used blankflash_rav_retail_QPJS30.63-35-1-15 from lolinet as it had the same version as the ROM I had just flashed, and it also seemed to work fine, as shown below.
Spoiler: blankflash
Code:
Motorola qboot utility version 3.86
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.002] ...cpu.id = 266 (0x10a)
[ 0.002] ...cpu.sn = 3854630421 (0xe5c0fe15)
[ 0.002] Opening singleimage
[ 0.048] Loading package
[ 0.051] ...filename = pkg.xml
[ 0.052] Loading programmer
[ 0.055] ...filename = programmer.elf
[ 0.055] Sending programmer
[ 0.219] Handling things over to programmer
[ 0.219] Identifying CPU version
[ 0.219] Waiting for firehose to get ready
[ 3.277] ...SM_NICOBAR 1.0
[ 3.277] Determining target secure state
[ 3.281] ...secure = yes
[ 3.316] Configuring device...
[ 3.323] Flashing GPT...
[ 3.348] Flashing partition with gpt.bin
[ 3.352] Initializing storage
[ 3.398] ...blksz = 512
[ 26.573] Re-initializing storage...
[ 26.573] Initializing storage
[ 26.726] Flashing bootloader...
[ 26.727] Flashing abl_a with abl.elf
[ 26.825] Flashing cmnlib_a with cmnlib.mbn
[ 26.880] Flashing cmnlib64_a with cmnlib64.mbn
[ 26.932] Flashing devcfg_a with devcfg.mbn
[ 26.978] Flashing hyp_a with hyp.mbn
[ 27.031] Flashing keymaster_a with keymaster.mbn
[ 27.093] Flashing tz_a with tz.mbn
[ 27.395] Flashing uefisecapp_a with uefi_sec.mbn
[ 27.551] Flashing prov_a with prov64.mbn
[ 27.587] Flashing rpm_a with rpm.mbn
[ 27.638] Flashing qupfw_a with qupfw.elf
[ 27.662] Flashing xbl_config_a with xbl_config.elf
[ 27.691] Flashing xbl_a with xbl.elf
[ 28.020] Wiping multiimgoem_a
[ 28.027] Wiping multiimgqti_a
[ 28.035] Rebooting to fastboot
[ 28.039] Total time: 28.039s
but the phone did not boot to the bootloader, the screen simply remained blank. And no matter what I do, I cannot boot the phone in EDL anymore, what is very strange. I did not found much info online about forcing the XT2045-1 into EDL mode, so I started this thread:
[Moto G8 XT2045-1] How to force EDL mode
This thread is supposed to be a guide for anyone with a hard bricked XT2045-1 to be able to unbrick the device by forcing it into EDL mode to flash a new firmware. It is a work in progress and I will update it with the proper guide as soon as all...
forum.xda-developers.com
If anyone has any info about how to force EDL mode or unbrick the phone some other way, it will be greatly appreciated!
I got it fixed after a long time... It seems that my unit had a problem with some component connected to the pads to force EDL mode, that is why it did not work when the phone died. Luckily I have found a good person who offered to re-solder it for free so I could test if it would work, and it indeed worked! Below is a pic of the board when I noticed the component was loose.
Spoiler: board pic
{
"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"
}
I will update the other post here about how to force EDL, but basically the picture shows the correct pads (TP2312 and TP2313). You can remove the fingerprint sensor and display cable while doing all the process, connect them back only when you are sure the phone is booting back in fastboot (bootloader mode, not fastbootd) normally again. Of course, only connect and disconnect things after you have disconnected the battery first.
Two important things:
1. Make sure the phone is off and plug the USB cable after connecting the pads. This is very important and I have not seen this mentioned anywhere. Disconnect the battery for a few seconds if in doubt, be gentle when disconnecting/connecting things. If it worked, the computer will detect a Qualcomm device a short while after connecting the cable. If you see an unknown USB device, you need to install the drivers, the Motorola RSA (Rescue and Smart Assistant) tool installs them. You can also use it to reflash stock firmware, but it will always flash the latest version. On Linux there is no need for a driver, of course, you can use dmesg -w to watch for the connection, and make sure you run blank-flash.sh with superuser privileges so it can write to /dev/ttyUSB0.
2. There is some anti-rollback feature, at least from RPJS31.Q4U-47-35-15 and up. This means you cannot use the blankflash files from lolinet if the version that was working on the phone is newer. Luckily also, there is a thread on Reddit that explains how to build your own.
That is why the device died when I tried to use an older blankflash file: the bootloader did not downgrade, so flashing a non compatible gpt.bin hard bricked the device. I will attach here the one that I used, it also works with RPJS31.Q4U_47_35_17, as it seems both use the same bootloader version (the number at the and seems to be the build date or something like this):
Code:
RPJS31.Q4U-47-35-15
version bootloader: MBM-3.0-rav_retail-a863e9dc07-220131
RPJS31.Q4U_47_35_17
version bootloader: MBM-3.0-rav_retail-a863e9dc07-220330
I hope it helps someone else. Cheers!

Categories

Resources