[Guide] Recovering from a hard brick

Search This thread

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,548
2
9,075
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
So I screwed something up when flashing. I had my bootloader unlocked and I believe I forgot to wipe the partitions before flashing. Oops. I then switched to slot b. Oops...... Now all I get is the "AP fastboot flash mode (secure)" screen. However to my horror I see OEM_locked...... so now nothing I try works including the blankflash files. Am I done with this phone? I did buy a new Motorola g power phone and so I decided to mess around with my G7 Power.

In all my years of flashing this would be my first complete hard brick if I can't recover this.
Device needs to be in EDL mode to use blankflash.
Try
Code:
fastboot oem blankflash
If it is in emergency download mode it will turn screen black and Windows device manager will list it as Qualcomm device.
 
  • Like
Reactions: prisoner1969

prisoner1969

Senior Member
Sep 8, 2015
596
259
Salt Lake City, Utah

jacobhin233

Member
Apr 2, 2021
7
0
United Kingdom
The phone has a black screen when connecting to a PC?
But the PC makes the USB connect sound?
usb seems dead, pc says it has malfunctioned, screen always black, only thing i can think to do is buy a new phone
(sorry for the wait on the reply I went to sleep) (In UK)

edit: i don't know whether it's worth buying an EDL cable if device seems fully dead
 

nomadman1

Member
May 2, 2020
5
2
I'm stuck:
**** Log buffer [000001] 2021-06-03_20:14:24 ****

[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] ERROR: device_open()->error opening device
[ 0.000] Check qboot_log.txt for more details
[ 0.000] Total time: 0.000s
[ 0.000]
[ 0.000] qboot version 3.40
[ 0.000]
[ 0.000] DEVICE {
[ 0.000] name = "/dev/ttyUSB0",
[ 0.000] flags = "0x60",
[ 0.000] addr = "0x3E1F6C88",
[ 0.000] serial_nix.device_pathname = "/sys/bus/usb/devices/1-2/1-2:1.0/ttyUSB0",
[ 0.000] api.bnr = "0x1824780",
[ 0.000] }
[ 0.000]
[ 0.000]
[ 0.000] Backup & Restore {
[ 0.000] num_entries = 0,
[ 0.000] restoring = "false",
[ 0.000] backup_error = "not started",
[ 0.000] restore_error = "not started",
[ 0.000] }
[ 0.000]
 

Rod_Ems

New member
Jun 12, 2021
2
0
This guide aims to recover your G7 power from a hard brick that leaves it in emergency download (EDL) mode.

Will this work with my device?
This should work on any device in EDL mode. To check for this mode, first try entering fastboot by holding the power button and volume down at the same time. If the screen comes on, use this guide instead.
If your device can't enter fastboot, connect it to a computer using it's USB-c cable, and open device manager using the search bar. Scroll down to "Ports" and open it, then look for a device called "qualcomm hs-usb qdloader 9008". if it appears, you might just be in luck.

The fix
Recovering from this brick is quite a simple process, as a blank flash is available.
  1. Connect your device to a computer
  2. Download blankflash.zip from https://mega.nz/#!tVd1VaoZ!epk2yLEqnQBKEwT2QbQaOe8-4675pfj76Hs7pC5kbQE onto your computer, and extract it to it's own folder
  3. Run "blank-flash.bat", and wait for it to finish

If you receive an error message like "ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error" on your computer, try holding the power button on your phone for about 10 seconds and trying again, or unplug and reconnect your phone.

After Running blank-flash.bat
From here, your phone should be able to start. If it enters recovery mode, boot loops or has other problems, but CAN now boot, follow this guide to reset your phone to stock, or you can use Lenovo smart assistant's recovery option.

Thanks to ChampC for finding the blankflash to make this recovery possible.
Hello, my moto g7 power has a similar problem, it only starts in fastboot mode, when I wanted to block the devia bootloader, phone locked and nothing else, this phone is still unusable, and the link of the blank flash is down, can you update it please? I have been with this problem since yesterday and the truth is that now a long time to buy this phone, I would appreciate your help.
 

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,548
2
9,075
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
Hello, my moto g7 power has a similar problem, it only starts in fastboot mode, when I wanted to block the devia bootloader, phone locked and nothing else, this phone is still unusable, and the link of the blank flash is down, can you update it please? I have been with this problem since yesterday and the truth is that now a long time to buy this phone, I would appreciate your help.
What does getvar all say? (remove imei before posting)
Code:
fastboot getvar all
 
Jul 4, 2021
1
0
This happened after I wiped the A / B partition, I wiped everything by TWRP, when I restarted it was like this. Look at the image below.
Please!!!
Me ajude, não sei o que fazer !!!

XT1955-1

fastboot getvar all

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-201128
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: c2c828c
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(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: MBM-2.1-ocean_retail-7fd887897c6-201128
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.153s
 

Attachments

  • Capturar.PNG
    Capturar.PNG
    470.2 KB · Views: 16
Last edited:

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,548
2
9,075
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
This happened after I wiped the A / B partition, I wiped everything by TWRP, when I restarted it was like this. Look at the image below.
Please!!!
Me ajude, não sei o que fazer !!!

XT1955-1

fastboot getvar all

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_retail-7fd887897c6-201128
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB MICRON S0J9N8 RV=08 PV=10 FV=0000000000000004
(bootloader) ram: 4GB MICRON LP3 DIE=8Gb M5=FF M6=01 M7=00 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: c2c828c
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) factory-modes: disabled
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(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: MBM-2.1-ocean_retail-7fd887897c6-201128
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
(bootloader) current-slot:
(bootloader) running-boot-lun: must + g->mlen
(bootloader) running-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
(bootloader) pcb-part-no:
all: listed above
finished. total time: 0.153s
You are going to need a blankflash for ocean
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/

and then put the device in EDL mode
 

snoopsean88

New member
Apr 11, 2022
3
0
I had an unknown device in device manager "QUSB_BULK". I had to downlaod and install the driver. I used this and it worked. I had to use the installer, i couldnt extract and install manually. Also, i had to press the power button for 10 seconds on the g7 before it showed back up with the correct name
Qualcomm HS-USB QDLoader 9008


I also kept trying to do the blankflash, but it kept failing. Foer the record, the blankflash should take less than 8 seconds to complete. For me, the fix was i needed a different blankflash (im on XT1955-5, not sure if retail or retus). I got it from here, and it ran the first time without issue.

I then had to do a complete wipe of my phone to get it working again. At least im not out 300 bucks!
 
Last edited:

ianos21

Member
Jan 6, 2017
17
1
Dayton
I had an unknown device in device manager "QUSB_BULK". I had to downlaod and install the driver. I used this and it worked. I had to use the installer, i couldnt extract and install manually. Also, i had to press the power button for 10 seconds on the g7 before it showed back up with the correct name
Qualcomm HS-USB QDLoader 9008


I also kept trying to do the blankflash, but it kept failing. Foer the record, the blankflash should take less than 8 seconds to complete. For me, the fix was i needed a different blankflash (im on XT1955-5, not sure if retail or retus). I got it from here, and it ran the first time without issue.

I then had to do a complete wipe of my phone to get it working again. At least im not out 300 bucks!
I have the same phone XT1955-5, on latest android 10 firmware, and I bricked it after flashing TWRP to the "...something recovery ramdisk" partition from TRWP, black screen with no response. I installed the drivers and used this version of blankflash and it got me back to fastboot. Then I let lenovo assistant tool/app restore the stock firmware. I tried the blankflash for my firmware version at https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/ and I just kept getting "waiting for firehose." Thanks all.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    This guide aims to recover your G7 power from a hard brick that leaves it in emergency download (EDL) mode.

    Will this work with my device?
    This should work on any device in EDL mode. To check for this mode, first try entering fastboot by holding the power button and volume down at the same time. If the screen comes on, use this guide instead.
    If your device can't enter fastboot, connect it to a computer using it's USB-c cable, and open device manager using the search bar. Scroll down to "Ports" and open it, then look for a device called "qualcomm hs-usb qdloader 9008". if it appears, you might just be in luck.

    The fix
    Recovering from this brick is quite a simple process, as a blank flash is available.
    1. Connect your device to a computer
    2. Download blankflash.zip from https://mega.nz/#!tVd1VaoZ!epk2yLEqnQBKEwT2QbQaOe8-4675pfj76Hs7pC5kbQE onto your computer, and extract it to it's own folder
    3. Run "blank-flash.bat", and wait for it to finish

    If you receive an error message like "ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error" on your computer, try holding the power button on your phone for about 10 seconds and trying again, or unplug and reconnect your phone.

    After Running blank-flash.bat
    From here, your phone should be able to start. If it enters recovery mode, boot loops or has other problems, but CAN now boot, follow this guide to reset your phone to stock, or you can use Lenovo smart assistant's recovery option.

    Thanks to ChampC for finding the blankflash to make this recovery possible.
    2
    Is this the way forward, to join another walled garden and be subjected to more spam & feed the <$latest platform> until they too sell out? I am unfamiliar w/ the specifics of the XDA Exodus, and frankly, have seen enough fragmented sites over 20 years to know I will get by w/o buying in to the orchestrations. I already struggle logging in to my account I setup here, as I have forgotten the password & that email has been dead for close to a decade... the Scroogle verification nonsense, notwithstanding.


    O-T:
    I have managed to flash most ROMs(AOSPs, RR, LOS, etc) in this forum up to the latest CrDroid without many problems(no bricks). I recently went straight from crDroidAndroid-9.0-20200215-ocean-v5.11 to crDroidAndroid-10.0-20200324-ocean-v6.4.

    I found it the new v6 to be a bit buggy w/ my setup, so I went back to the previously skipped crDroidAndroid-9.0-20200312-ocean-v5.12. The 1st attempt gave me a black screen, but managed to get into bootloader to reflash stock. I tried a 2nd attempt, and now it is bricked... no bootloader, no recovery, no sounds/light/vibrations. Windows does detect it as Q HS-USB QDLoader 9008 after installing drivers(formerly QUSB_BULK).

    I have run 15 attempts with blankflash_ocean_PDOS29.114-134-2, & received varying errors each time it fails. Anyone have any other suggestions outside of Telegram?

    I hear you and I can relate. Only reason I'm on stupid telegram is because there are things there that aren't here.. I hear you on joining another group... But imo if that's where it's going down I'm there. Not like i voted to move to telegram. Hell I didn't even know what telegram was until a few months ago seeing a link here in a devs op. To each his own. On my 1955-5 since my last hard brick, it's probably been a few months I've flashed my device probably about 100-120 times or so and no bricks. The method I use is manually boot to bootloader, open terminal and make sure I'm in slot a which I'm usually in slot b because I'm flashing another rom from a rom here so I do: fastboot set_active a and get in proper slot then reboot bootloader and I proceed to boot orange fox recovery: fastboot boot OF.img then I install copy-partitions-AB.zip and make sure by reading my screen it indeed copied correctly with no errors, if it did have errors I format data then flash copy partitions AB zip again in recovery then flash my rom, reboot bootloader, fastboot boot OF.img again, flash gapps, flash latest magisk canary zip,, reboot system. Works every tiime.

    Sometimes I format and wipe data just before I reboot system at the end and sometimes I don't and it'll prompt me to via stock recovery usually and I just wipe data factory reset and done.

    I too received different errors each time and I ran the blankflash for weeks ok end and for hours at a time and eventually recovered my 1955-5 more than a few times from a hard brick. I was however on firmware RETUS 9.0_PPOS29.114-134-7-1_cid50 previously each time . I posted all over the og blankflash threads as to some of the different methods of getting it to finish that I used. I about fell out my chair backwards every time it woke up in bootloader mode. Couldn't believe it. Each time it resurrected it was almost spiritual. God knows i ran ./blankflash.sh thousands of times during my adventures to unbrick and in the end every time it came on. Thinking about putting in for a user name change here and switching it to blankflashsh or something. Haha. ?
    2
    Woooha! :D

    I did it!
    Code:
    < waiting for device >
    Motorola qboot utility version 3.40
    [ -0.000] Opening device: \\.\COM4
    [  0.003] Detecting device
    [  0.007] ...cpu.id  = 186 (0xba)
    [  0.010] ...cpu.sn  = xxxxxxxxxxxxxxxxxxxxxxxx)
    [  0.010] Opening singleimage
    [  0.023] Loading package
    [  0.029] ...filename = singleimage.pkg.xml
    [  0.033] Loading programmer
    [  0.035] ...filename = programmer.mbn
    [  0.035] Sending programmer
    [  0.322] Handling things over to programmer
    [  0.323] Identifying CPU version
    [  0.329] Waiting for firehose to get ready
    [  3.335] ...MSM8953 1.0
    [  3.336] Determining target secure state
    [  3.337] ...secure = yes
    [  3.361] Configuring device...
    [  3.367] Flashing GPT...
    [  3.368] Flashing partition with gpt.bin
    [  3.371] Initializing storage
    [  3.385] ...blksz = 512
    [  3.452] Re-initializing storage...
    [  3.452] Initializing storage
    [  3.506] Flashing bootloader...
    [  3.510] Flashing aboot_a with emmc_appsboot.mbn
    [  3.740] Flashing rpm_a with rpm.mbn
    [  3.799] Flashing tz_a with tz.mbn
    [  4.051] Flashing devcfg_a with devcfg.mbn
    [  4.078] Flashing cmnlib_a with cmnlib_30.mbn
    [  4.284] Flashing cmnlib64_a with cmnlib64_30.mbn
    [  4.476] Flashing keymaster_a with keymaster64.mbn
    [  4.663] Flashing prov_a with prov.mbn
    [  4.715] Flashing sbl1_a with sbl1.mbn
    [  4.821] Rebooting to fastboot
    [  4.822] Total time: 4.827s

    What I did:
    - Removed my "ping-command" mentioned in my first post.
    - Ran 3 instances of the script as administrator.
    - Random clicked buttons / removed cable / port

    As far as I can say/remember: On the sucessful try I pressed all (power /volume (middle)) buttons and reconnected the USB-cable - took me ~15min. (today) but I guess it was kind of much luck :silly:

    PS: For those wondering - If you succeed - the 9008-connection will be gone, the 3 instances of the script (infinite loop) will not rune it / reboot / re-blank-flash the device.

    Thanks for your support :good::D
    1
    One problem I was having was using the wrong blankflash. Got this one off lolinet and it worked like a charm.

    Be sure to use copy partitions.zip before flashing a custom rom