yashsingh1/xdaforums huggingface dataset:
[Moto G7 Power Guides, News, & Discussion] LikeaG7:
I can't get it to work either. Hopefully someone finds a fix

Motorola qboot utility version 3.40

[ 0.000] Opening device: \\.\COM3

[ 0.000] Detecting device

[ 0.010] ...cpu.id = 186 (0xba)

[ 0.010] ...cpu.sn = 1705912611 (0x65ae2923)

[ 0.010] Opening singleimage

[ 0.010] Loading package

[ 0.010] ...filename = singleimage.pkg.xml

[ 0.010] Loading programmer

[ 0.010] ...filename = programmer.mbn

[ 0.010] Sending programmer

[ 0.299] Handling things over to programmer

[ 0.299] Identifying CPU version

[ 0.299] Waiting for firehose to get ready

[ 60.612] Waiting for firehose to get ready

[121.021] ...MSM8953 unknown

[121.021] Determining target secure state

[121.021] Waiting for firehose to get ready

[181.413] ...secure = no

[181.429] Initializing storage

[181.429] Waiting for firehose to get ready

[242.055] Configuring device...

[242.055] Waiting for firehose to get ready

[302.413] Waiting for firehose to get ready

[362.858] Waiting for firehose to get ready

[423.621] Waiting for firehose to get ready

[484.369] Initializing storage

[484.369] Waiting for firehose to get ready

[545.073] Configuring device...

[545.073] Waiting for firehose to get ready

[605.806] Waiting for firehose to get ready

[666.495] Waiting for firehose to get ready

[727.121] Waiting for firehose to get ready

[787.841] Waiting for firehose to get ready

[848.558] Configuring device...

[848.558] Waiting for firehose to get ready

[909.321] Waiting for firehose to get ready

[969.961] Waiting for firehose to get ready

[1030.710] Waiting for firehose to get ready

[1091.427] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[1091.427] Check qboot_log.txt for more details

[1091.427] Total time: 1091.427s

[1091.427] There were some hiccups in backup and restore.

[1091.427] Please save the following files and see a Bootloader member.

[1091.427] 1) ./qboot_log.txt

[1091.427] 2) ./backup_0x65AE2923_2020-03-18_164830.img

[1091.427]

FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[Moto G7 Power Guides, News, & Discussion] flash713:
I had this same exact situation word per word in my Linux terminal a few times and was able to recover my device. It's all about your connection, usb cord you use... port and button press and release and running multiple windows and just staying on it, running the blank flash until you do it do much the cat looks at you strangely. I've made many posts here about exactly what I did in detail to recover hard brick using this blank flash on my 1955-5 six different times. May wanna see previous posts I made describing exactly what I did.. Stay with it and I believe you'll get it back going again. Took me many many hours each time i suceeded but in the end it was worth it.

Probably my best detailed post about what I did: https://xdaforums.com/showthread.php?p=81979257

I don't care what anyone says the errors meant nothing on my device. Each time I succeeded recovering it from hard brick it had different errors in terminal. The ONLY thing I believe that makes this not work is being on the latest uodated firmware past the December RETUS. I say that in reference to my 1955-5 metro variant Moto G7 power idk anything about other variants because I did this six times on my 1955-5.

I was never on newer firmware than this https://photos.app.goo.gl/T5WG1y3XhFAkJvek6 when I did these blank flashes, on my 1955-5 metro device..
[Moto G7 Power Guides, News, & Discussion] LikeaG7:
Unfortunately I am on the newest firmware. I got the February update a couple days before I bricked it lol. I'll have to wait for a new method or the lastest blankflash.
[Moto G7 Power Guides, News, & Discussion] flash713:
Have you read up on Moto g7 power telegram group? I saw someone some days ago was putting together different packages or trying to help with this problem..

Join «G7 Power Discussion» on Telegram: https://t.me/mG7Power

If you search and read backwards somewhere in that group there are people who dealt with this same thing ..I'm not sure whether they were able to solve it or not but maybe 2-3 days ago I believe I read something about it. Worth a shot to peep it out if you haven't already done so. I wish I knew more about it. Lenovo Moto forums also have a blank flash thread but to me xda has more information. Kinda weird. You'd think it would be the other way around. Lol. If I owned such a company it would definitely be maxed out to the roof about this type of information! I wish Google would have kept Motorola. ? Lenovo isn't in the top 10 list but Motorola is still a gem because they haven't joined the whole "encrypt our bootloader's because it's safer" group. I sure hope they never do that. I'll keep buying phones from them as long as they keep that out of the picture. ;)
[Moto G7 Power Guides, News, & Discussion] mightytaco:
Any updates?

Any update to blank flash with newer firmware? I was using the lenovo moto smart assistant to update my phone. I had the ota feb update installed and i went in to the moto program to do a backup and noticed it said there was a newer version of the firmware. Something like 134-114-10 I think i had 134-114-7-1. The update failed and my phone is bricked. I have tried using this blank flash for days and keep getting an error.
[Moto G7 Power Guides, News, & Discussion] Nico95f:
need a updated blankflash please i need help :crying:
[Moto G7 Power Guides, News, & Discussion] jakson2090:
we could donate to a motorola technician to provide us with this blankflash myself i am available to donate, but i don't know any technician
[Moto G7 Power Guides, News, & Discussion] theblack334:
I need the blank flash for the xt1955-1

he was in the patch February 1, 2020
[Moto G7 Power Guides, News, & Discussion] Ishran:
.xml file invalid error with blankflash

Hello everyone! A wholehearted thank you for all of the people involved in trying to solve to Moto G7 PowerBrick!

Unfortunately I seem to have bricked it myself. Current the only Blankflashes that seem to do something are these:

- BlankFlash-MotoG7power-OCEAN-SDM632- PPOS29.114-134-10

- blankflash_sdm632_PDOS29.114-134-9

They both seem to throw an error involving an invalid .xml file. Does anybody have any idea what it means or how I can solve it?

This is the logging:

[ 0.000] Opening device: /dev/ttyUSB0

[ 0.000] Detecting device

[ 0.003] ...cpu.id = 186 (0xba)

[ 0.003] ...cpu.sn = 1954709566 (0x7482803e)

[ 0.003] Opening singleimage

[ 0.003] Loading package

[ 0.006] ...filename = singleimage.pkg.xml

[ 0.008] Loading programmer

[ 0.008] ...filename = programmer.mbn

[ 0.008] Sending programmer

[ 0.283] Handling things over to programmer

[ 0.283] Identifying CPU version

[ 0.286] Waiting for firehose to get ready

[ 3.292] ...MSM8953 1.0

[ 3.292] Determining target secure state

[ 3.294] ...secure = yes

[ 3.317] Configuring device...

[ 3.321] Flashing GPT...

[ 3.321] Flashing partition with gpt.bin

[ 3.323] Initializing storage

[ 3.331] ...blksz = 512

[ 5.284] Target NAK!

[ 5.284] ...num_partition_sectors=8192

[ 5.284] ...num_physical_partitions=3

[ 5.284] ...MFR_ID=19

[ 5.284] ...Product name=S0J9N8

[ 5.284] ...{"storage_info": {"total_blocks":8192, "block_size":512, "page_size":512, "num_physical":3, "mfr_id":19, "serial_num":357028312, "fw_version":"4","mem_type":"eMMC", "prod_name":"S0J9N8"}}

[ 5.284] ...XML (0 bytes) not validated

[ 5.284] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK

[ 5.284] Check qboot_log.txt for more details

[ 5.284] Total time: 5.284s

[ 5.285]

[ 5.285] qboot version 3.40

[ 5.285]

[ 5.285] DEVICE {

[ 5.285] name = "/dev/ttyUSB0",

[ 5.285] flags = "0x140",

[ 5.285] addr = "0x2965D238",

[ 5.285] serial_nix.device_pathname = "/sys/bus/usb/devices/1-1/1-1:1.0/ttyUSB0",

[ 5.285] sahara.current_mode = "0",

[ 5.285] api.buffer = "0x7FC144371010",

[ 5.285] cpu.serial = "1954709566",

[ 5.285] cpu.id = "186",

[ 5.285] cpu.sv_sbl = "0",

[ 5.285] cpu.name = "MSM8953",

[ 5.285] storage.type = "eMMC",

[ 5.285] sahara.programmer = "programmer.mbn",

[ 5.285] module.firehose = "0x22E1C50",

[ 5.285] api.firehose = "0x22E5C30",

[ 5.285] cpu.ver = "256",

[ 5.285] cpu.vername = "1.0",

[ 5.285] fh.max_packet_sz = "1048576",

[ 5.285] fh.storage_inited = "1",

[ 5.285] }

[ 5.285]

Thank you! :)
[Moto G7 Power Guides, News, & Discussion] disobey:
I bought a Google Pixel 3 to solve my issue about 2 weeks after my G7 Power bricking. Since then, this G7 has been used as a paperweight, a doorstop, an object to yeet at my cat when she's annoying, and on a daily basis as a surface for breaking up ganja on. I had a lucid dream last night, and I woke up recalling "chopping" my phone in my dream for the flashlight. I have my Pixel 3 "edges" remapped to turn the light on and off when I squeeze that phone, but recalling the dream made me miss the chop. Also I miss the insane battery life on my G7. So I just plugged it in, and of course, it's the same issues as before. I've tried all kinds of button press combos, cords and ports. I'm still determined to get this phone unbricked.
[Moto G7 Power Guides, News, & Discussion] googleverifysux:
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?
[Moto G7 Power Guides, News, & Discussion] roadkill42:
From what I heard keep doing it and should flash eventually there is another new blank out there not sure we're it is I have seen it and it worked for the ones trying it especially if u had the latest security up date
[Moto G7 Power Guides, News, & Discussion] flash713:
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. ?
[Moto G7 Power Guides, News, & Discussion] AngelMedina123:
me aparece eso

ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[1097.404] Check qboot_log.txt for more details

[1097.404] Total time: 1097.408s

[1097.405] There were some hiccups in backup and restore.

[1097.405] Please save the following files and see a Bootloader member.

[1097.406] 1) ./qboot_log.txt

[1097.407] 2) ./backup_0x9DB9900A_2020-04-07_165429.img

[1097.407]

FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[Moto G7 Power Guides, News, & Discussion] googleverifysux:
Big thanx to theblack334's answer in a newer, less viewed Q&A from April 1st. I cannot post URLs, but it's in the Q&A section, titled:

Moto G7 Power XT1955-5 unlocked retail US. Hard bricked blankflash latest update?

This one did the trick for me on the 1st run, finished in 30-60 seconds.

The previous dozens of attempts w/ other blankflashes hung for ~18 minutes/per.

CrDRoid v.6.4 is up & running.
[Moto G7 Power Guides, News, & Discussion] roadkill42:
Thanks for giving him the better answer I haven't gotten this phone figured out yet to remember everything this phone dose on blank flashing cause this will be my first a/b device so I will be following u when I bite the bullet lol
[Moto G7 Power Guides, News, & Discussion] jonymelavo:
XT1955-2 (Ocean-womcl)

I brick my phone (XT1955-2 Ocean -WOMCL) :cyclops:

The last ROM was:

mirrors.lolinet.com/firmware/moto/ocean/official/WOMCL/XT1955-2_OCEAN_WOMCL_9.0_PPOS29.114-134-10_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

but Miracast (Screen Mirroring- Transmitir Pantalla) was unable. So i decide install CrDroid V6.5 ROM

sourceforge.net/projects/crdroid/files/ocean/6.x/crDroidAndroid-10.0-20200412-ocean-v6.5.zip/download

withthe Gapps of LineageOS 17.1 (Android 10 Based and ARM64)

cyanogenmods.org/downloads/pico-opengapps-for-android-10-arm64

Well! Instalation of TWRP was easy but wen i install the CrDroid 6.5 ROM + Gapps (All at the same time = 2 Zips option on TWRP ) my phone was Bricked. I try with all the FLASHBLANK (Even one that was based on the stock ROM: OCEAN_WOMCL_9.0_PPOS29.114-134-10_cid50) but nothing happens. My phone wont start.

The rom installation with TWRP has no problems, but when TWRP installed the second zip (Gapps) shows an error (I dont remember what error was) and then my phone dont start.

I never let the ROM start.

I really need help on this one :crying:
[Moto G7 Power Guides, News, & Discussion] dzikarczi120:
Moto g7 power hard brick

Hello, recently after installing lineage os 17 on moto g7 power after restarting the phone turned off and after connecting to the phone to the computer it displays as qualcomm and the same way is detected is one way to restore it namely the qfil program but I do not have the necessary files to restore system, please help if someone could send files or explain how it can be done I would be very grateful. My model is moto g7 power xt1955-4.
[Moto G7 Power Guides, News, & Discussion] iFelipe97:
Whad do you do for worked i dont see de qualcomm in device manager

---------- Post added at 08:18 PM ---------- Previous post was at 07:37 PM ----------

Look i dont like this xda page because anybody respond
[Moto G7 Power Guides, News, & Discussion] zfk110:
Hi, mine showing Quectel QDLoader 9008 under device manager but no matter what I do it will never read the phone, mine screen is black, no sign of life at all, but USB chimes.
[Moto G7 Power Guides, News, & Discussion] capomaximus:
thank you

Thank you man you save my moto g7 river.
[Moto G7 Power Guides, News, & Discussion] harryspar:
The linked files are down. Can you share the files with me somehow?
[Moto G7 Power Guides, News, & Discussion] flash713:
Link seems fine. Oh you were referring to firmware...?
[Moto G7 Power Guides, News, & Discussion] nomadman1:
a Hickup...

This is the error I received. Not sure what to do next...

Who do I contact, if anyone?

[1091.398] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[1091.414] Check qboot_log.txt for more details

[1091.414] Total time: 1091.414s

[1091.414] There were some hiccups in backup and restore.

[1091.414] Please save the following files and see a Bootloader member.

[1091.414] 1) ./qboot_log.txt

[1091.414] 2) ./backup_0xA163F679_2020-05-02_170124.img

[1091.414]

FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

Any ideas?
[Moto G7 Power Guides, News, & Discussion] logicsticks:
[ -0.000] Opening device: \\.\COM4

[ 0.004] Detecting device

[ 0.009] ...cpu.id = 186 (0xba)

[ 0.009] ...cpu.sn = 3289984524 (0xc4192e0c)

[ 0.009] Opening singleimage

[ 0.010] Loading package

[ 0.017] ...filename = singleimage.pkg.xml

[ 0.021] Loading programmer

[ 0.022] ...filename = programmer.mbn

[ 0.025] Sending programmer

[ 0.367] Handling things over to programmer

[ 0.368] Identifying CPU version

[ 0.375] Waiting for firehose to get ready

[ 62.228] Waiting for firehose to get ready

[122.375] ...MSM8953 unknown

[122.375] Determining target secure state

[122.385] Waiting for firehose to get ready

[182.528] ...secure = no

[182.615] Initializing storage

[182.624] Waiting for firehose to get ready

[243.636] Configuring device...

[243.650] Waiting for firehose to get ready

[304.204] Waiting for firehose to get ready

[364.360] Waiting for firehose to get ready

[425.179] Waiting for firehose to get ready

[485.402] Initializing storage

[485.410] Waiting for firehose to get ready

[545.541] Configuring device...

[545.561] Waiting for firehose to get ready

[605.985] Waiting for firehose to get ready

[666.231] Waiting for firehose to get ready

[726.355] Waiting for firehose to get ready

[786.494] Waiting for firehose to get ready

[846.897] Configuring device...

[846.902] Waiting for firehose to get ready

[907.223] Waiting for firehose to get ready

[1756.184] Waiting for firehose to get ready

[1817.066] Waiting for firehose to get ready

[1877.196] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

[1877.196] Check qboot_log.txt for more details

[1877.196] Total time: 1877.203s

[1877.197] There were some hiccups in backup and restore.

[1877.197] Please save the following files and see a Bootloader member.

[1877.197] 1) ./qboot_log.txt

[1877.198] 2) ./backup_0xC4192E0C_2020-05-06_124638.img

[1877.198]

FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error

any help ? ive tried this 4 times but sadly nothing :(
[Moto G7 Power Guides, News, & Discussion] Strakios:
Unbrick Moto G7 Power XT1955-2.

Link of Autoinstaller by Strakios:

drive.google.com/file/d/1Wi85_qqKNBxRDzVkTUUcU2HTtiuz6hHt/view

Strakios 14/05/2020

XT1955-2 OCEAN_PPOS29.114-134-13. Actualizado Mayo 2020

Todo el Contenido se Instala en C:\XT1955-OCEAN

1 - INSTALAR DRIVERS

2 - ACTIVAR EDL MODE(EMERGENCY DOWNLOAD MODE)

3 - INSTALAR SLOT A/B (BLANKFLASH)

4 - DESCARGAR ROM STOCK PARA XT1955-2 OCEAN

5 - FLASHEAR STOCK FIRMWARE

drive.google.com/file/d/1Wi85_qqKNBxRDzVkTUUcU2HTtiuz6hHt/view
[Moto G7 Power Guides, News, & Discussion] sgurdekili38:
need introduction using a mac to perform blankflash

i have a 1955-5 won't turn on after failed flash trying to recover imei. I'm noob and need guidance/instructions performing this on a mac because I'm not able to a windows pc.
[Moto G7 Power Guides, News, & Discussion] theburrus1:
I've got a real problem. I kept trying to flash the TWRP image in fastboot and then reboot into TWRP but it never did. IT would boot to system or just bootloop. So I told it to getvar make-active=b, it gave me the following warning:

oot@latitude-E7470:/home/kevin# fastboot --set-active=slot b
Slot slot does not exist. supported slots are:
a
b
root@latitude-E7470:/home/kevin# fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) WARNING: Bootloader images on target slot b are not valid!!
(bootloader) There is risk of bricking HW. Please flash valid bootloader
(bootloader) into slot b before activating it. OR you could force to
(bootloader) switch to slot b by running the same command again
(bootloader) within 30 s if you understand what you're doing
FAILED (remote failure)
finished. total time: 0.182s
root@latitude-E7470:/home/kevin# fastboot --set-active=b
Setting current slot to 'b'...
OKAY [ 0.423s]
finished. total time: 0.423s
root@latitude-E7470:/home/kevin# fastboot boot /home/kevin/Downloads/twrp.img
downloading 'boot.img'...
OKAY [ 0.819s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 1.275s

Then while plugged in still to my computer, it shut off and hasnt come back on at all. I mean it wont charge, nothing. Dead.