[HELP]Blank Flash For Moto G7 Power

[WetWilly]

I've tried the blankflash 12-15 times and doesn't work. I have metro g7 power.. I'll try it again and post the log in 20-30 minutes of exactly what it says when I hold buttons down and get it going..

I have the Metro G7 Power and was able to recover it with the blankflash. I'm not sure the link you gave has the answer (at least based on the Google Translate version of that page) because their blankflash programmer started to flash the partition table while with yours the programmer didn't even get to the point of correctly identifying the CPU. From your log It looks that qboot can talk to the phone but the programmer cannot. Have you tried the blankflash under Windows instead of Linux?

 

[KUSANAGUI]

I finally got a copy uploaded.
XT1955.5.mmcblk0.img.zip
https://mega.nz/#!WKgHmIaB!CO57014-m-5NPcrI9Jt2-MCdnW4e7dajS7O5CpjeapY
Note: you have to change the block size in the command

bs=1000000000

it needs to be unzipped, and then follow steps in
[Guide] [Unbrick] How to revive a hard bricked Moto G5 by TheFixItMan

It should work for anything with a Snapdragon 632
G7, G7 Play but not the G7 Plus that has a Snapdragon 636

I did all the steps to the letter and it doesn't work.
But thanks for uploading it

MY model is XT1955-2

 

[flash713]

I have the Metro G7 Power and was able to recover it with the blankflash. I'm not sure the link you gave has the answer (at least based on the Google Translate version of that page) because their blankflash programmer started to flash the partition table while with yours the programmer didn't even get to the point of correctly identifying the CPU. From your log It looks that qboot can talk to the phone but the programmer cannot. Have you tried the blankflash under Windows instead of Linux?

I am just now home and purchased my most hated os ( windows) again and I'm about to give it a run. I'll report back in a few. Funny before I read your comment here that's what my plan was. lol. Here goes . brb


Sent from my mi mix 2 Bootlegged 10

 

[flash713]

I have the Metro G7 Power and was able to recover it with the blankflash. I'm not sure the link you gave has the answer (at least based on the Google Translate version of that page) because their blankflash programmer started to flash the partition table while with yours the programmer didn't even get to the point of correctly identifying the CPU. From your log It looks that qboot can talk to the phone but the programmer cannot. Have you tried the blankflash under Windows instead of Linux?

log on windows 10 on different laptop:

**** Log buffer [000001] 2020-01-22_20:24:05 ****

[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 186 (0xba)
[ 0.000] ...cpu.sn = 839264944 (0x32062ab0)
[ 0.000] Opening singleimage
[ 0.000] Loading package
[ 0.010] ...filename = singleimage.pkg.xml
[ 0.010] Loading programmer
[ 0.010] ...filename = programmer.mbn
[ 0.010] Sending programmer
[ 0.309] Handling things over to programmer
[ 0.309] Identifying CPU version
[ 0.315] Waiting for firehose to get ready
[ 60.802] Waiting for firehose to get ready
[121.222] ...MSM8953 unknown
[121.222] Determining target secure state
[121.222] Waiting for firehose to get ready
[181.697] ...secure = no
[181.760] Initializing storage
[181.760] Waiting for firehose to get ready
[242.265] Configuring device...
[242.265] Waiting for firehose to get ready
[302.715] Waiting for firehose to get ready
[363.209] Waiting for firehose to get ready
[423.680] Waiting for firehose to get ready
[484.139] Initializing storage
[484.139] Waiting for firehose to get ready
[544.628] Configuring device...
[544.628] Waiting for firehose to get ready
[605.105] Waiting for firehose to get ready
[665.590] Waiting for firehose to get ready
[726.071] Waiting for firehose to get ready
[786.562] Waiting for firehose to get ready
[847.065] Configuring device...
[847.065] Waiting for firehose to get ready
[907.571] Waiting for firehose to get ready
[967.995] Waiting for firehose to get ready
[1028.463] Waiting for firehose to get ready
[1088.940] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1088.940] Check qboot_log.txt for more details
[1088.940] Total time: 1088.950s
[1088.940] There were some hiccups in backup and restore.
[1088.940] Please save the following files and see a Bootloader member.
[1088.940] 1) ./qboot_log.txt
[1088.940] 2) ./backup_0x32062AB0_2020-01-22_202706.img

 

[topgman80]

Blank flash file for g7 Power

The blank flash file for Moto g7 Power "ocean" can be found here:
https://mirrors.lolinet.com/firmware/moto/ocean/

 

[sd_shadow]

https://forum.xda-developers.com/showpost.php?p=81355251&postcount=70

Sent from my perry_f using XDA Labs

 

[WetWilly]

log on windows 10 on different laptop:

This still smells like a communication issue because that blankflash should work - and has worked for a good number of people with the XT1955-5 variant. What about the cable - are you using the cable that came with the phone? Non-OEM cables can be YMMV for flashing tasks.

Edit: Have you also tried different USB ports, both USB 2.0 and 3.0?

 

[flash713]

This still smells like a communication issue because that blankflash should work - and has worked for a good number of people with the XT1955-5 variant. What about the cable - are you using the cable that came with the phone? Non-OEM cables can be YMMV for flashing tasks.

Edit: Have you also tried different USB ports, both USB 2.0 and 3.0?

I ended up getting it to work on my laptop on Linux mint 19.3. What got it going is I opened multiple windows in terminal and ran one ./blank-flash.sh after another and unplugged and plugged back in every now and tben, held power and volume buttons and let em go.... Just kept on that track and I looked away for a few seconds then looked back and my phone was in bootloader node.

 

[WetWilly]

I ended up getting it to work on my laptop on Linux mint 19.3. What got it going is I opened multiple windows in terminal and ran one ./blank-flash.sh after another and unplugged and plugged back in every now and tben, held power and volume buttons and let em go.... Just kept on that track and I looked away for a few seconds then looked back and my phone was in bootloader node.

Congrats on the perseverence. Nothing like the feeling when watching a bricked phone come back to life. :good:

 

[flash713]

Congrats on the perseverence. Nothing like the feeling when watching a bricked phone come back to life. :good:

Most definitely!!! I actually bricked it again since then and brought it back again using blank flash. ? Fr.

I just wanted to make another comment on a time frame of how long it took me to actually get this to work. I spent HOURS every day after work and sometimes in the morning pressing buttons down, letting them go at 3 seconds-10 seconds, 2 seconds, I tried different USB ports, different USB cords, plugged it in, unplugged, switch ports all the while running 20- different sessions of this blank flash at the same time. This was NOT some set down and boom it's back on kinda deal for me. It probably took over eight hours or so of messing with to finally get it to take off and finish atw.

I say this because it's true and if it wasn't for some of you guys telling me it should have worked on my phone I wouldn't have gotten it to work. I thank you all for your comments. Don't give up. IDC what error it throws out keep on trying. I did and my phone is now alive and I'm using it now on crDroid rom and it's bad ass!! Appreciate you all!

Setup: Toshiba Qosmio 505, Linux Mint 19.3
Worked best using One plus Dash charging USB cord


Sent from my moto g(7) power using XDA Labs

 

[DenhamsOwnSmoky]

I used the blankflash an was able to get it into fastboot mode but the bootloader relocked itself an every firmware i try says validation failed. Can someone please point me in the rite direction on this?

(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ocean_t-f71f50d-190924
(bootloader) product: ocean
(bootloader) board: ocean
(bootloader) secure: yes
(bootloader) hwrev: PVT1
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX hB8aP> RV=08 PV=03 FV=0000000034303030
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=01 M8=5F
(bootloader) cpu: SDM632
(bootloader) serialno: ZY326J4CQH
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 687C4E4A00000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from normal boot mode
(bootloader) imei: 359527094180659
(bootloader) meid:
(bootloader) date: 07-28-2019
(bootloader) sku: XT1955-5
(bootloader) carrier_sku: XT1955-5
(bootloader) battid: SB18C46718
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Nov 12 23: 9:32 UTC 2019"
(bootloader) ro.build.fingerprint: <not found>
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full: <not found>
(bootloader) ro.build.version.qcom: LA.UM.7.6.2.r1-04600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 4.9.112-perf+ ([email protected]
(bootloader) kernel.version[1]: v.co.uk) (gcc version 4.9.x 20150123 (pr
(bootloader) kernel.version[2]: erelease) (GCC) ) #2 SMP PREEMPT Fri Apr
(bootloader) kernel.version[3]: 19 02:18:33 CEST 2019
(bootloader) sbl1.git: MBM-2.1-ocean_t-b508f3a-190924
(bootloader) rpm.git: MBM-2.1-ocean_t-22daab3-190924
(bootloader) tz.git: MBM-2.1-ocean_t-8798b8e-dirty-190924
(bootloader) devcfg.git: MBM-2.1-ocean_t-8798b8e-dirty-190924
(bootloader) keymaster.git: MBM-2.1-ocean_t-8798b8e-dirty-190924
(bootloader) cmnlib.git: MBM-2.1-ocean_t-8798b8e-dirty-190924
(bootloader) cmnlib64.git: MBM-2.1-ocean_t-8798b8e-dirty-190924
(bootloader) prov.git: MBM-2.1-ocean_t-8798b8e-dirty-190924
(bootloader) aboot.git: MBM-2.1-ocean_t-f71f50d-190924
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: metropcs
(bootloader) current-slot: a
(bootloader) running-boot-lun: 0
(bootloader) running-slot: _a
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: No
(bootloader) slot-successful:_b: No
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
all: listed above
finished. total time: 0.452s

 

[flash713]

@DenhamsOwnSmoky
If bootloader is indeed locked the only thing that can fix it would maybe be jtag.. I've been looking at these programming boxes. (jtag, octopus, madusa..) From what I've read you can write straight to the device using something like that but I'm not [emoji817] sure of it and that doesn't help here but you could do a search in your area for jtag and see if anything pops up and if so ask them.. I recently recovered my Metro 1955-5 from it's fifth hard brick. (my son's doing) (now it's mine again. lol.) But this last time I was left with no baseband, no IMEI/MEID, and sim and data were messed up. After Googling and researching and trying all kinds of things for about two weeks I was able to finally fix it by entering my fastboot commands multiple times each and I flashed the same firmware that was on it previous to it messing up. All those things played some type of roll in giving me back my baseband and IMEI and fixing my data sim issue. I did everything there is out there that came up in my search results and nothing worked. If you know what firmware you were on before it bit it you can try repeating the commands and keying each one in manually 3-4 times. Some of the commands for me would "FAIL" but when I paused a few seconds and reentered the command a few times it completed with the "OKAY" at the end.

Sent from my Moto G7 Power (AOSiP)

 

[DenhamsOwnSmoky]

thanks ima try that… is there any way to check what the last firmware was?i think i had flashed RETUS or RETAIL but my g7 was metroPCS versions… an i installed lineage right before i bricked it reflashing one of the stock firmewares… any way i can find out what firmware version needed?

 

[flash713]

thanks ima try that… is there any way to check what the last firmware was?i think i had flashed RETUS or RETAIL but my g7 was metroPCS versions… an i installed lineage right before i bricked it reflashing one of the stock firmewares… any way i can find out what firmware version needed?

From what I've read for metro the RETUS are good to go. I'm currently using the RETUS (retail US): XT1955-5_OCEAN_RETUS_9.0_PPOS29.114-134-7-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
and all has been good. I couldn't get some other firmwares to flash. There are a few others who speak good about the second firmware in the RETUS list from the top. I've heard the first one doesn't work well..
Here's the link to where the firmware is located:
https://mirrors.lolinet.com/firmware/moto/ocean/official
I hope you can get it fixed. Did you by chance have insurance? I heard some guy at the local metro the other day telling the lady who worked there that his phone was in the Gulf Of Mexico. I didn't even look up I just heard what he said and to me he sounded like he was lying. ? Also if you're using any type of script to enter the fastboot commands don't just type them in manually. That also seemed to work better than running one of my scripts that runs the commands real quick... Also not sure if you saw the thread or not but there's a thread here somewhere that shows how to boot off an sdcard. Just basically make the card same as your phone and it's said to work. I know a few of the guys who say it works really know their stuff so maybe check that out too. .

 

[DenhamsOwnSmoky]

thanks… i dl the firmware u used an as soon as i get access to a laptop again Ima try doin how you said an let u know if it worked

 

[DenhamsOwnSmoky]

i tried the firmware plus every tmobile firmware i could find an i aint had no luck. I tried LMSA an it wont recognize the phone as a moto G7 power… Im wondering if it has something to do with this:

(bootloader) cid: 0xDEAD

is there any way to fix that would that keep it from validating my firmware?

 

[Miinoru]

I ended up getting it to work on my laptop on Linux mint 19.3.

install the same version of linux mint 19.3, but do you need to install any additional drivers or command? Thanks for the help

./blank-flash.sh

[  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  = "0x6D0530C8",
[  0.000]   serial_nix.device_pathname = "/sys/bus/usb/devices/1-8/1-8:1.0/ttyUSB0",
[  0.000]   api.bnr = "0x2181870",
[  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]

 

[flash713]

install the same version of linux mint 19.3, but do you need to install any additional drivers or command? Thanks for the help

No it does not need any additional drivers. However I did already have adb and fastboot tools installed and updated to the latest versions and did my sudo apt update and sudo apt upgrade and had everything updated I had already installed on my pc. Not sure if that's mandatory or not but I use mint Tricia 19.3 and I've successfully brought my device back from hard brick six times. Don't give up and keep trying is what someone here told me and I did that and my phone is not dead.

(Edit)

Just run the: sudo ./blank-flash.sh over and over and when it freezes on you don't kill that windows just minimize it open a new window and start running it again. I don't believe there is a set method to get this to work. I say that because for me there was not. I messed with my phone and blank flash for over a month and I must have ran it 500-600 times before it competed and my phone turned on to bootloader mode.

If you have more than one USB cord switch em up too and change ports. But leave the terminal windows that freeze up open. I swear that had something to do with mine finishing and I read all this here and on other blank flash Moto forums during my blank flash intro. Also change up holding power and volume. Sometimes for me when I did this the six times I did when it worked finally there was never a similarly from a past completion. It was always random but play with your power button and volume and change that up as well from time to time. You know like hold power and volume down count to 10 or 12 in seconds plug USB into your device and already have the blank flash "waiting for device" when you plug up then soon as you see it begin to run and start release all buttons.. Seems like I got it to run more that way but it was still random sometimes the final run that completed for me was one where I just held power down and counted eight seconds and when I plugged in and had computer terminal waiting for device sometimes if keep holding down whatever combo for 10-12 seconds and sometimes i'd release immediately.

Six times I did it and completed it was always a different way or so it seemed but that's what I learned in my experience here. It took me 8 days one time of about 2 hours or so a day of non stop running the blank flash to finally get my phone to bootloader and complete. Don't give up. Just set it down when it gets on your nerves and return later or the next day. Every time I finally got one to work and complete I about fell out my chair I was so surprised after all the attempts I had done previous. ?

PS: And I wouldn't study whatever the blank flash errors are because mine were crazy different every time. Just run the **** outa it. I know all this may sound a bit nuts and it is but it did work for me six different times and there are others who know these things I type here are legit.

 

[Miinoru]

Just run the: sudo ./blank-flash.sh over and over and when it freezes on you don't kill that windows just minimize it open a new window and start running it again. I don't believe there is a set method to get this to work. I say that because for me there was not. I messed with my phone and blank flash for over a month and I must have ran it 500-600 times before it competed and my phone turned on to bootloader mode.

thanks for the reply!
indeed, no drivers are needed. but if sudo is necessary before the command.

sudo ./blank-flash.sh

I will keep trying and I will share any good result.
a questions:
1) you disconnect the phone when you run a new terminal and the other windows minimize ?

Example:
- Windows commands freeze 
- Minimized terminal
- Disconnect phone from pc
- Run sudo ./blank-flash.sh in new terminal
- "waiting for device"
- Press button power + volume down for 10 seconds in the phone
- Connect to pc
- Release buttons
- Wait and repeat the steps?

2) when did it work ... is fast the process in finish? because after the "MSM8953 unknown" takes too long to wait for it to end and start over. (sorry me english)

 

[flash713]

thanks for the reply!
indeed, no drivers are needed. but if sudo is necessary before the command.


I will keep trying and I will share any good result.
a questions:
1) you disconnect the phone when you run a new terminal and the other windows minimize ?



2) when did it work ... is fast the process in finish? because after the "MSM8953 unknown" takes too long to wait for it to end and start over. (sorry me english)

Try running the blank flash command with phone not plugged in to USB then when terminal says "waiting for device" hold power and volume button down and count out 10-12 seconds plug the end of your USB cable in to your phone while still holding down buttons then soon as it begins to run the blank flash release the buttons and see but I believe that way got it to start more so and go further for me.

One of the times mine finished and my screen came on I had previously only held power button down like I explained in my previous sentence. Another time I had previously held volume up and power another time previous to the blank flash working for me I held volume down and power. That's why I say it's crazy ? I was looking for any type of pattern or anything but never saw one. Also different USB cables worked for me. At first the first time I completed it my new OnePlus dash charging cable was the magic one then it didn't work on round two when my son bricked it then it worked when I used my previous phones Moto cable and a type c adapter, then it worked using my pixel phone USB. But about the terminal windows I had read that on xda and on Lenovo Motorola forums and somewhere else but every time mine finished , I would run command and if it froze up on me, stopped for more than 20-30 seconds seconds or so I would minimize that terminal window and open a new one, change ports and begin running it again and kept that up over and over until I thought there was no hope or wanted to smash everything and I'd stop for a day or a few days then when I had time and felt like it id go back at it again.

I won't brick again. I finally understand the whole AB partition layout deal and we have the copy partition ab zip and people who kindly pointed me to the right directions to use far as flashing factory image on my metro G7 power 1955-5. The thread to follow for metro people is the "How to root for noobs" thread in our forums. I was only guilty of two of the bricks. My son tried to compete with me and won I guess on the whole brick deal. ? If I ever brick again I will for a fact shoot video on me doing it and time lapse it and slap it up on YouTube or something. But not gonna push my luck. I can't believe this phone made it through six. ?

When i saw it compete and my phone turned on it was fast. I'd say it appeared to be maybe 35-45 seconds from start to finish but I only saw it complete once with me looking at it because the other times it finished in one of the terminal windows I had previously opened and minimized....