Database Info

[Q] OPO 64GB Bricked ; acces to fastboot and recovery

Hi folks,
Here is a resumé of what i've tried so far
Actual symptoms : Cyanogenmod logo with animation looping (no bootloop)
I've access to fastboot and philz recovery (but errors are shown, see below)
I've got the phone as it is, no idea of what the previous owner has done.
Can someone help me ?
I tried to unbrick using various methods :
ColosOS : device is displayed as FORGE HS-USB QDLOader 9008 or Qualcomm HS-USB QDLOader 9008
OPO recovery tool 1.1 : connected to com5, 8974_msimage.mbn: OK
that's the only thing shown, then the OPO vibrates and nothing happen
Flash zip bacon 33R and 44S via OTG => error status 7
Code:
Installing : /storage/usbdisk/cm-11.0-XNPH44S-bacon-signed-fastboot.zip
E: Can't mount /cache/recovery/last_install
E: faile to open last_install : File exists
Finding update package
Opening update Package
Installation update
Installation aborted
Code:
[U]Errors when booting Philz Recovery :[/U]
E: could not mount /data to setup /data/media path!
E: Can 't mount /cache/recovery/command
E: Can 't mount /cache/recovery/log
E: Can 't open /cache/recovery/log
E: Cannon mount path for settings file :/data/philz-touch/phils-touch6.ini
E: Can 't mount /cache/recovery/last_log
E: Can 't open /cache/recovery/log
E: Can 't mount /cache/recovery/last_install
E: Can 't open /cache/recovery/last_install
[U]Logs :[/U]
W; failed to mount /dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 (File exists)
mount : mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed : Invalid argument
Code:
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
finished. total time: 0.008s
OnePlus One ZIP with 3 bats and fastboot :
Code:
######### This patch is Created by ONEPLUS Technical Support. #######
###### This patch should only be used for ONEPLUS ONE 64GB Global Version. ####
#
...
OKAY [ 0.003s]
finished. total time: 0.003s
erasing 'persist'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'persist' (4244 KB)...
OKAY [ 0.138s]
writing 'persist'...
FAILED (remote: flash write failure)
finished. total time: 5.221s
erasing 'reserve4'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.167s]
writing 'reserve4'...
FAILED (remote: flash write failure)
finished. total time: 5.251s
target reported max download size of 536870912 bytes
sending 'boot' (5578 KB)...
OKAY [ 0.181s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 5.232s
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'recovery' (7510 KB)...
OKAY [ 0.243s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 5.295s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 1.800s]
writing 'modem'...
FAILED (remote: flash write failure)
finished. total time: 6.851s
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
FAILED (remote: flash write failure)
finished. total time: 5.065s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
FAILED (remote: flash write failure)
finished. total time: 5.056s
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.015s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 5.067s
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
FAILED (remote: flash write failure)
finished. total time: 5.062s
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
FAILED (remote: flash write failure)
finished. total time: 5.064s
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.308s]
writing 'LOGO'...
FAILED (remote: flash write failure)
finished. total time: 5.361s
rebooting...
finished. total time: 0.005s
It is done Now :)
Appuyez sur une touche pour continuer...

I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#

DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
Click to expand...
Click to collapse
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...

DrNinjaa said:
I would ask for trying twrp recovery and trying flashing a ROM...
If that did not help, there is a thread for unbricking the oneplus using Qualcomm drivers, in which adb is not required.... try it and many have recovered their device... I'll post the the thread link, once I get to a laptop.
#HappyFlashing#
Click to expand...
Click to collapse
Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Seems the guy you buy the phone has relock bootloader
In kitkat that was problem ....

Qiou said:
Hi DrNinjaa,
Already tried to boot twrp and flash rom using OTG USB to get the zip, nothing happens, got an error status 7 ...
Using the qualcomm drivers and OPO Recovery tool did not work, like I said, the phone is detected, then flash begins, then a red message (but in chinese UTF8) appears, then a sahara error ...
Click to expand...
Click to collapse
Status 7 message is due to improper twrp recovery..... flash the latest.... and unlock the bootloader once again.... may be that will help.
Really want to help u.... because, once i had bricked my device and lost efs also, and I know how bad it feels .... but thanks to my backups, i was saved...
#HappyFlashing#

@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.

Qiou said:
@DrNinjaa
Actually, I can't flash a new recovery, when I try with fastboot, I get an error (flash write failure) and also when I try to erase it.
Click to expand...
Click to collapse
im having this exact problem... anyone managed to find a fix? Even putting it back to stock doesn't work!

BLL-L22 Firmware and Help

Hello,
I need help to unbrick my phone please,
After trying to back to stock i got stuck while dload method with BLL-L22C636B150 (android 6.0) Firmware after flashing RollbackPackage from same firmware (android 7.0 to 6.0)
My phone's screen is now only black, no boot logo anymore or recovery.
It's only show connected fastboot while plug in, i can only reboot to fastboot.
PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.006s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.007s]
finished. total time: 0.008s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.005s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7XXXX
(bootloader) IMEI:8646XXXX
(bootloader) IMEI1:8646XXXX
What can i do please ?

Try team mt tool for unbrick provide file from marshmallow update.app

siddhrsh said:
Try team mt tool for unbrick provide file from marshmallow update.app
Click to expand...
Click to collapse
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode

Demodark said:
13:00:27: All images are found, everything is ready for the unbricking process.
13:00:29: Unbricking started. Your computer may freezes during the process.
13:00:29: flash boot "C:\adb\348\boot.img"
13:00:31: The Boot image is flashing successfully
13:00:31: flash system "C:\adb\348\system.img"
13:03:26: The System image is flashing successfully
13:03:26: flash cust "C:\adb\348\cust.img"
13:03:49: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 13.115s]
writing 'cust' 1/2...
OKAY [ 3.142s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.109s]
writing 'cust' 2/2...
OKAY [ 0.035s]
finished. total time: 16.401s
13:03:49: Error#1
13:03:49: flash recovery "C:\adb\348\recovery.img"
13:03:51: The Recovery image is flashing successfully
13:03:51: Completed
13:03:51: Something went wrong (((
Still black screen rebooting only on fastboot mode
Click to expand...
Click to collapse
Did you flash marshmallow files

Images
Yes i tried to unbrick with : Huawei_GR5_2017_BLL-22_C636B150_South_East_Asia_6.0.zip
17:49:30: All images are found, everything is ready for the unbricking process.
17:49:32: Unbricking started. Your computer may freezes during the process.
17:49:32: flash boot "C:\adb\B150\boot.img"
17:49:34: The Boot image is flashing successfully
17:49:34: flash system "C:\adb\B150\system.img"
17:52:03: The System image is flashing successfully
17:52:03: flash cust "C:\adb\B150\cust.img"
17:52:26: target reported max download size of 471859200 bytes
sending sparse 'cust' 1/2 (458414 KB)...
OKAY [ 12.833s]
writing 'cust' 1/2...
OKAY [ 3.181s]
sending sparse 'cust' 2/2 (4100 KB)...
OKAY [ 0.114s]
writing 'cust' 2/2...
OKAY [ 0.045s]
finished. total time: 16.173s
17:52:26: Error#1
17:52:26: flash recovery "C:\adb\B150\recovery.img"
17:52:29: The Recovery image is flashing successfully
17:52:29: flash userdata "C:\adb\B150\userdata.img"
17:52:36: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 3.784s]
writing 'userdata'...
OKAY [ 1.013s]
finished. total time: 4.797s
17:52:36: Error#1
17:52:36: Completed
17:52:36: Something went wrong (((
Huawei Multi-Tool by Team MT v. 8.0.3.1 beta
I dont know wich one i can try now ?
http://pro-teammt.ru/firmware-database/?firmware_model=bll-l22&firmware_page=0

Black Screen
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.

Demodark said:
I tried to unbrick with update.zip (full OTA B150 version) script said all done without bug, but still black screen (no light) stuck in fastboot mode.
Click to expand...
Click to collapse
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot

shashank1320 said:
Just flash the small data file via dload method.it should be 700-800 MB i guess. Once flashed, reboot to stock recovery and factory reset and boot
Click to expand...
Click to collapse
What is "the small data file" please ?

PS C:\adb> fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.007s
PS C:\adb> fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NRD90M test-keys
finished. total time: 0.005s
PS C:\adb> fastboot oem get-product-model
...
(bootloader) HUAWEI BLL-L22
OKAY [ 0.006s]
finished. total time: 0.006s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/spcseas
finished. total time: 0.006s
PS C:\adb> fastboot oem get-psid
...
(bootloader) SN:YCP7N17609000963
(bootloader) IMEI:864646034450028
(bootloader) IMEI1:864646034717855
OKAY [ 0.005s]
finished. total time: 0.005s
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
PS C:\adb>

Demodark said:
What is "the small data file" please ?
Click to expand...
Click to collapse
Let me check the firmware and get the link for you

shashank1320 said:
Let me check the firmware and get the link for you
Click to expand...
Click to collapse
News ?

Demodark said:
News ?
Click to expand...
Click to collapse
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine

shashank1320 said:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1277/g104/v74004/f1/full/hw/spcseas/
Unzip and see if there is update.app file in it, if so, dload it and it should be fine
Click to expand...
Click to collapse
Link is dead.

Demodark said:
Link is dead.
Click to expand...
Click to collapse
Let me recheck

What can i do ?
Always black screen, but phone detected as fastboot mode, reboot only leads to fastboot mode.

have you tried unlocking again your bootloader? updating or rollbacking of EMUI makes your bootloader locked by default.
try to unlock it first and flash your OS
if you want to use the dload way. try flashing the stock recovery after unlocking your bootloader.

Demodark said:
Link is dead.
Click to expand...
Click to collapse
K.. But after that how reset the DNS to its original state

Flash TWRP into eRecovery with Oreo

My phone is a MHA-L29 C432 B368. Is there a way to flash TWRP into the eRecovery partition (recovery2)?
When I try it, I either get "partition length get error" or "Command not allowed"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash erecovery_ramdisk TWRP_3.2.1-0_OREO_V3.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (16506 KB)...
OKAY [ 0.362s]
writing 'erecovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.375s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery2_ramdisk TWRP_3.2.1-0_OREO_V3.img
target reported max download size of 471859200 bytes
sending 'recovery2_ramdisk' (16506 KB)...
OKAY [ 0.361s]
writing 'recovery2_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.374s

Stuck in fastboot

Hi all,
I need help with my phone being stuck in fastboot...
Today i tried to flash Lineage OS using this guide. I did this from scratch with a stock phone, not rooted or unlocked or anything.
Everything went fine until Step 4 under ROM Installation. My phone refused to start into TWRP. It didn't even start the lineage rom, it always just warned me about my phone being a risk because it is unlocked and then proceeded to start the stock Rom. So i tried the whole thing over and over again a couple of times, always with the same result. Then i read someone writing about how he first had to use wipe > format data before flashing the Rom in TWRP in the Guide Thread (Page 3). So i tried that too. But i must have done something wrong because it now led to my phone restarting into a fastboot mode, which didn't look like the fastboot screen it booted into before e.g. different font style, black background without the little android thingy on the top, and it now says "oem_locked" again.
When i try to boot the system it says:
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
I tried to unlock the phone again using "fastboot oem unlock MYKEY" on my computer it says:
(bootloader) feature disabled
OKAY [ 0.003s]
finished. total time: 0.004s
So i tried to flash back to the stock image as described here.
But i get a "remote failure" error after every command.
Here is the output from Powershell:
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.002s
PS D:\Minimal ADB and Fastboot> ./fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (45 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.055s
PS D:\Minimal ADB and Fastboot> ./fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.249s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.437s
PS D:\Minimal ADB and Fastboot> ./fastboot flash modem_a NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem_a' (65396 KB)...
OKAY [ 2.147s]
writing 'modem_a'...
(bootloader) Invalid partition name modem_a
FAILED (remote failure)
finished. total time: 2.158s
PS D:\Minimal ADB and Fastboot> ./fastboot flash fsg_a fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg_a' (11684 KB)...
OKAY [ 0.379s]
writing 'fsg_a'...
(bootloader) Invalid partition name fsg_a
FAILED (remote failure)
finished. total time: 0.392s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.010s
PS D:\Minimal ADB and Fastboot> ./fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.027s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dsp_a adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp_a' (16384 KB)...
OKAY [ 0.531s]
writing 'dsp_a'...
(bootloader) Invalid partition name dsp_a
FAILED (remote failure)
finished. total time: 0.538s
PS D:\Minimal ADB and Fastboot> ./fastboot flash logo_a logo.bin
target reported max download size of 536870912 bytes
sending 'logo_a' (1285 KB)...
OKAY [ 0.046s]
writing 'logo_a'...
(bootloader) Invalid partition name logo_a
FAILED (remote failure)
finished. total time: 0.057s
PS D:\Minimal ADB and Fastboot> ./fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (32768 KB)...
OKAY [ 1.085s]
writing 'boot_a'...
(bootloader) Invalid partition name boot_a
FAILED (remote failure)
finished. total time: 1.093s
PS D:\Minimal ADB and Fastboot> ./fastboot flash dtbo_a dtbo.img
target reported max download size of 536870912 bytes
sending 'dtbo_a' (1760 KB)...
OKAY [ 0.058s]
writing 'dtbo_a'...
(bootloader) Invalid partition name dtbo_a
FAILED (remote failure)
finished. total time: 0.066s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_a' (258873 KB)...
OKAY [ 8.397s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.409s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_a' (249260 KB)...
OKAY [ 8.139s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.153s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_a' (262081 KB)...
OKAY [ 8.677s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.693s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system_a' (262141 KB)...
OKAY [ 8.533s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.540s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system_a' (257008 KB)...
OKAY [ 8.366s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.374s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system_a' (242308 KB)...
OKAY [ 7.906s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 7.912s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system_a' (262060 KB)...
OKAY [ 8.585s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.596s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system_a' (255940 KB)...
OKAY [ 8.420s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.436s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.8
target reported max download size of 536870912 bytes
sending 'system_a' (261918 KB)...
OKAY [ 8.584s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 8.594s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_a system.img_sparsechunk.9
target reported max download size of 536870912 bytes
sending 'system_a' (83808 KB)...
OKAY [ 2.728s]
writing 'system_a'...
(bootloader) Invalid partition name system_a
FAILED (remote failure)
finished. total time: 2.738s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system_b' (262140 KB)...
OKAY [ 8.349s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.357s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system_b' (262024 KB)...
OKAY [ 8.368s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 8.376s
PS D:\Minimal ADB and Fastboot> ./fastboot flash system_b system_b.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system_b' (43968 KB)...
OKAY [ 1.414s]
writing 'system_b'...
(bootloader) Invalid partition name system_b
FAILED (remote failure)
finished. total time: 1.423s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'vendor_a' (259120 KB)...
OKAY [ 8.524s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 8.531s
PS D:\Minimal ADB and Fastboot> ./fastboot flash vendor_a vendor.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'vendor_a' (147628 KB)...
OKAY [ 4.843s]
writing 'vendor_a'...
(bootloader) Invalid partition name vendor_a
FAILED (remote failure)
finished. total time: 4.850s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_a oem.img
target reported max download size of 536870912 bytes
sending 'oem_a' (103040 KB)...
OKAY [ 3.370s]
writing 'oem_a'...
(bootloader) Invalid partition name oem_a
FAILED (remote failure)
finished. total time: 3.377s
PS D:\Minimal ADB and Fastboot> ./fastboot flash oem_b oem_other.img
target reported max download size of 536870912 bytes
sending 'oem_b' (185456 KB)...
OKAY [ 6.032s]
writing 'oem_b'...
(bootloader) Invalid partition name oem_b
FAILED (remote failure)
finished. total time: 6.044s
PS D:\Minimal ADB and Fastboot> ./fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.016s
PS D:\Minimal ADB and Fastboot> ./fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot oem fb_mode_clear
...
OKAY [ 0.001s]
finished. total time: 0.005s
PS D:\Minimal ADB and Fastboot> ./fastboot reboot
rebooting...
finished. total time: 0.001s
And now i'm pretty lost and don't really know how to proceed. It would be great if somebody hat some advice

This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.

kry52 said:
This situation takes place when you switch to the empty Slot B without copying contents of Slot A there. I have exactly the same problem and my phone has been put to the box, until a proper solution can be found, if any. I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Thats unfortunat
I tried the blankflash too, with the same outcome. Then i guess i'll do the same.... put in the box and wait for a solution, if there will ever be any :fingers-crossed:
Anyway... thank you for the reply

Tried switching slots?
To check active slot
Code:
fastboot getvar current-slot
To change to slot a
Code:
fastboot --set-active=a
To change to slot b
Code:
fastboot --set-active=b
To toggle from active to inactive Slot
Code:
fastboot set_active other
Sent from my mata using XDA Labs
---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------
kry52 said:
... I have downloaded blankflash files recently, but the command line shows only "waiting for device", in such a way I havent managed to use it propely.
Click to expand...
Click to collapse
Was phone in emergency download mode?
Sent from my mata using XDA Labs

In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE

@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?

bondu546 said:
@sd_shadow Switching slots does nothing. I always get the "remote failure" error massage. And when i'm trying to switch to slot b it tells me there wouldn't be a slot b.
Here the output of the suggested commands:
D:\Minimal ADB and Fastboot>fastboot getvar current-slot
current-slot:
finished. total time: 0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=a
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>fastboot --set-active=b
Slot b does not exist. supported slots are:
a
D:\Minimal ADB and Fastboot>fastboot set_active other
Setting current slot to 'a'...
(bootloader) Command is not allowed
FAILED (remote failure)
finished. total time: -0.000s
D:\Minimal ADB and Fastboot>
@Geoffrey I was able to put it into EDL. It shows up in my Device Manager as Qualcomm HS-USB QDLoader 9008 but when im trying to run the blankflash like in the guide i get this result:
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>.\qboot.exe blank-flash
Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM4
[ 0.001] Detecting device
[ 4.007] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.007] Check qboot_log.txt for more details
[ 4.009] Total time: 4.012s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
D:\Downloads\Moto\blankflash_ocean_PDOS29.114-134-2 (1)>pause
Drücken Sie eine beliebige Taste . . .
Here is the Log File:
**** Log buffer [000001] 2019-11-02_19:45:56 ****
[ 0.000] Opening device: \\.\COM4
[ 0.002] Detecting device
[ 4.010] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.010] Check qboot_log.txt for more details
[ 4.011] Total time: 4.014s
[ 4.011]
[ 4.011] qboot version 3.40
[ 4.011]
[ 4.011] DEVICE {
[ 4.011] name = "\\.\COM4",
[ 4.011] flags = "0x64",
[ 4.011] addr = "0x61FE4C",
[ 4.011] api.bnr = "0xFF2F20",
[ 4.011] }
[ 4.011]
[ 4.011]
[ 4.011] Backup & Restore {
[ 4.011] num_entries = 0,
[ 4.011] restoring = "false",
[ 4.011] backup_error = "not started",
[ 4.011] restore_error = "not started",
[ 4.011] }
[ 4.011]
Any suggestions?
Click to expand...
Click to collapse
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...

jodytejada said:
I have the same issue x.x is really hard to unbrick this phone at this point :C my phone boot into a diferent type of bootloader with the START in green color and no android logo, and my pc doesn't recognize de device...
Click to expand...
Click to collapse
My PC shows "Android ADB Interface" when the phone is loaded in this emergency fastboot mode, but anyway - ADB commands don't work, fastboot commands bring failures because of the partitions issue and more than that - this emergency fastboot loader is oem_locked and can't be unlocked in a standard way

Will this 134-2 file work on a phone updated to 134-4 ??
Geofferey said:
In this mode phone will not be in EDL, but you can place it into by issuing `fastboot oem blankflash`. See `fastboot oem help` Afterwards you should be able to restore phone using blank flash file, see this HERE
Click to expand...
Click to collapse
This is a 134-2 blankflash file - will it work on 134-4 ??
Despite everyone else being able to flash to a different variant of the XT1955 firmware - apparently the Verizon XT1955-6 is OEM locked at the boot.img stage.
Currently there is no PDOS29.114-134-4 firmware to download at https://mirrors.lolinet.com/firmware.../official/VZW/ to repair it by a re-install of the firmware with - and one cannot install an earlier version . . . unless you know of a way . . .
Everything will re-flash but boot.img and dtbo.img
The Lenovo MOTO Smart Assistant comes back and says it is not supported . . . after recognizing it
Is there a way to re-set the OEM issues of the phone to take earlier versions of the OS - or other variants that you know of ??
Even factory reset is not available - I will look for a fastboot command that can do it - because that is all I can do - it boots right to fastboot now only

estofjlw said:
This is a 134-2 blankflash file - will it work on 134-4 ??
...
Click to expand...
Click to collapse
It should work for any XT1955-5
Sent from my ocean using XDA Labs

sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse

estofjlw said:
sd_shadow said:
It should work for any XT1955-5 /QUOTE]
OK I can try it. I have a xt1955-6 - Verizon
Everything flashes with a xt1955-5 RETUS firmware except the boot.img and dtbo.img
If blank flash is an OEM signed file - maybe it will push over the existing boot.img
I will see if in the middle of the flash - the oem get_unlock_data has changed with the retail bootloader on the phone
From what I saw in vars - some vars had changed in the bootloader
But what I read at https://forum.xda-developers.com/g5/help/how-to-develop-blank-flash-t3791525 it seems to say of the boot.img file is newer - the blank flash will fail
Click to expand...
Click to collapse
I believe the boot.img in the blank flash can be updated too.
Sent from my mata using XDA Labs
Click to expand...
Click to collapse

What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???

jodytejada said:
What happend when the device is not recognized by the blank flash and onlly appears Moto ADB Interface???
Click to expand...
Click to collapse
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs

VZW update locks out any other firmware
sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too. /QUOTE]
That would be great except if it updates to newer than the RETUS firmware boot.img - which will cause a pre-flash error instead of an oem boot.img error
I have not tried yet . . . but the RETUS 134-4 firmware is older than the VZW 134-4 firmware which has not been posted on the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ website.
No other ocean variant I looked at is newer either - some have the 11/04 modify date - but inside the folder it is not the 134-4 firmware that is for that date.
Verizon's 134-4 update came down between November 2 and 4 in three updates as 1, 2 and then straight to 4 - behind my back on wifi and since the bootloader is still oem locked - and because it is Verizon - not eligible for an unlock code from Motorola due the Verizon ordering it as an oem branded phone, unless I can make it look like a RETUS bootloader to Motorola in the middle of the flash while the bootloader can be unlocked so they provide an unlock code for it _ I am betting I am screwed until the https://mirrors.lolinet.com/firmware/moto/ocean/official/VZW/ site has a post for the 134-4 VZW firmware
Right now it boots to fastboot mode immediately - so I do not want to make it worse and actually brick it
I looked inside the blank flash zip and there is no boot.img - but from my understanding the blank flash contacts the boot img and updates it - to what and how I do not know - in my case it needs to "downgrade" it an earlier date - I sure I had Magisk so it could patch the boot.img and fix this. See https://www.reddit.com/r/MotoG/comments/cdsbw6/quick_reference_moto_g7_power_manually_flashing/
The trouble is of course there is no access to ADB copy, push and pull commands in fastboot
I have a XT1955-5 True Factory unlocked Retail US Phone on the way - and this one will have to be shelved
Click to expand...
Click to collapse
Click to expand...
Click to collapse

sd_shadow said:
It's not in Emergency Download Mode
PC should see it as
Qualcomm QHSUSB_Bulk or qloader
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Any solution at this point? or onlly a brick to my collection?

sd_shadow said:
estofjlw said:
I believe the boot.img in the blank flash can be updated too.
Click to expand...
Click to collapse
Well I have my answer . . . the Verizon XT1955-6 version restricts using blankflash and it will not go in EDL at all
C:\>fastboot oem blankflash
...
(bootloader) command restricted
FAILED (remote failure)
Since I can flash the RETUS bootloader can anyone suggest another work around to get past boot.img and DTBO.img
Click to expand...
Click to collapse

I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5

KeRbYRoK said:
I'm having a similar problem. After flashing firmware is stuck in fastboot with the OEM relocked and the unlock code does not unlock it. Mine is retus xt1955-5
Click to expand...
Click to collapse
Look for retus blank flash

Thanks man.
Ok what I did was hit it with blankflash. That still wouldn't clear out the faulty bootloader that was from the wrong firmware. But I found a new Android 10 firmware flashed it all checks were good and I'm sending this message from it right now.

OP6 bootloop issue FAILED (remote: Failed to load/authenticate boot image: Load Error

Hi all,
Long story short, I did wanna install Snapchat, but my phone was rooted with magisk, so I did wanna do an reinstall of the latest OP6 10 andr. version.
But now I get in a bootloop the issue I see now when I try with ADB on Windows laptop is the following: "FAILED (remote: Failed to load/authenticate boot image: Load Error)".
My commands I tried:
PS C:\adb> fastboot flash recovery_a C:\adb\twrp-3.4.0-1-enchilada.img
target reported max download size of 805306368 bytes
sending 'recovery_a' (31072 KB)...
OKAY [ 0.792s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 0.819s
PS C:\adb> fastboot flash recovery_b C:\adb\twrp-3.4.0-1-enchilada.img
target reported max download size of 805306368 bytes
sending 'recovery_b' (31072 KB)...
OKAY [ 0.793s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 0.834s
PS C:\adb> fastboot boot C:\adb\twrp-3.4.0-1-enchilada.img
downloading 'boot.img'...
OKAY [ 0.794s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.833s
PS C:\adb>
Help... I know how to unbrick this device, but I can't lose the WhatsApp data etc, I didn't back up.
Thanks!

Hey! I've run over a similar issue on op6t.
I'd recommend you doing what I've mentioned in this reply: https://forum.xda-developers.com/showpost.php?p=82995393&postcount=2