@ChampC Yo thank you so much man that blank flash unbricked my phone my model was XT1955-5 (ocean) so if anyone is hard bricked use that blankflash and your life is saved!!!
Many thanks - this blankflash unbricked my XT1955-5 as well. And a tip of the hat as well to vinoxflame for the Moto G7 River Telegram group heads up.This blank flash unbricked my phone: https://mega.nz/#!tVd1VaoZ!epk2yLEqnQBKEwT2QbQaOe8-4675pfj76Hs7pC5kbQE
Hey, i know i'm a bit late to the thread, but what exactly did you do to unbrick your Moto? Mine keeps getting stuck at waiting for firehose to get ready. Even though i have a Moto g7 Power XT1955-4. I'm so confused.This blank flash unbricked my phone: https://mega.nz/#!tVd1VaoZ!epk2yLEqnQBKEwT2QbQaOe8-4675pfj76Hs7pC5kbQE
You have a xt1955-4 , I haven't seen anyone other than you post that they tried the blankflash.Hey, i know i'm a bit late to the thread, but what exactly did you do to unbrick your Moto? Mine keeps getting stuck at waiting for firehose to get ready. Even though i have a Moto g7 Power XT1955-4. I'm so confused.
Yeah you're probably right. Looks like i might be screwed in that case. Regardless thanks for the help.You have a xt1955-4 , I haven't seen anyone other than you post that they tried the blankflash.
It's possible that it's not compatible.
The XT1955-5 is single sim, and I believe the XT-1955-4 is dual SIM, and possible other hardware differences.
Checking in a bit late, but the blankflash should have theoretically worked. Based on what you said, it looks like it is hanging at the point where the programmer is identifying the CPU; it takes about 3 seconds after the "Waiting for firehose to get ready" message for the CPU version ("MSM8953 1.0") to show up and the blankflash to continue. That points to either the programmer.mbn not being compatible with the XT1955-4 variant or that tweaks need to be made to files in the blankflash (e.g., xml edits and/or replacing .bin files with files for that specific variant).Yeah you're probably right. Looks like i might be screwed in that case. Regardless thanks for the help.
Checking in a bit late, but the blankflash should have theoretically worked. Based on what you said, it looks like it is hanging at the point where the programmer is identifying the CPU; it takes about 3 seconds after the "Waiting for firehose to get ready" message for the CPU version ("MSM8953 1.0") to show up and the blankflash to continue. That points to either the programmer.mbn not being compatible with the XT1955-4 variant or that tweaks need to be made to files in the blankflash (e.g., xml edits and/or replacing .bin files with files for that specific variant).
Check the qboot log and after the "qboot version x.xx" line there's a DEVICE { section; confirm in that section that the cpu.id is 186 and the CPU.name is "MSM8953". If the CPU detection is correct then the blankflash probably needs to be tweaked.
Just to be clear do I need to do the block size change after following the tutorial or at step #1 ? I'm about to give this a shot and going to just use one of my Samsung ultra 128 gb sdcards. Just want to make 100% sure when to change the block size. I sure appreciate you uploading the mmcblk.img for the xt1955-5!!You changed the block size to bs=1000000000 ?
like
Code:sudo dd bs=1000000000 if=mmcblk0.img of=/dev/sdb status=progress oflag=sync
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
and rename XT1955.5.mmcblk0.img to mmcblk0.img
or change code like
Code:sudo dd bs=1000000000 if=XT1955.5.mmcblk0.img of=/dev/sdb status=progress oflag=sync
You shouldn't need the mmcblk0.img there is a blankflashYou changed the block size to bs=1000000000 ?
like
---------- Post added at 08:59 PM ---------- Previous post was at 08:54 PM ----------
and rename XT1955.5.mmcblk0.img to mmcblk0.img
or change code like
Just to be clear do I need to do the block size change after following the tutorial or at step #1 ? I'm about to give this a shot and going to just use one of my Samsung ultra 128 gb sdcards. Just want to make 100% sure when to change the block size. I sure appreciate you uploading the mmcblk.img for the xt1955-5!!
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..You shouldn't need the mmcblk0.img there is a blankflash
Here's my log: https://mega.nz/#!cI92gSpZ!IPozK644Kt6swHRxuLgs098bEKtj0NBvhpe8EOqULWsYou shouldn't need the mmcblk0.img there is a blankflash
Sent from my ocean using XDA Labs
you managed to raise the mmcblk0.img of the g7 power ?Update:
I finally got around to Unlocking the bootloader, and rooting.
The Terminal Emulator method wasn't working for me.
I flashed the new TWRP
[PORT] Unofficial TWRP for G7 Power by Geofferey
and used the steps in this thread
[GUIDE] How to create 'mmcblk0.img' from a working device? by kalyansundhar
and used
The mmcblk0.img is almost 30gb, I'm compressing it, and uploading now may take awhile.Code:dd if=/dev/block/mmcblk0 of=/external_sd/XT1955.5.mmcblk0.img bs=1000000000 count=30
Old Post
I believe if someone with a rooted Moto G7 can pull a copy of the mmcblk0.img from their device with
Terminal Emulator
https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
using these commands
GRANT Terminal emulator a Root AccessCode:su
How to Unbrick (Debrick) Qualcomm Android Devices Using your SD CardCode:dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
https://www.aryk.store/2019/09/unbrick-qualcomm-android-using-sd-card.html
and
[GUIDE] How to create 'mmcblk0.img' from a working device? by kalyansundhar
That mmcblk0.img can be used to boot the non-working G7 into Fastboot mode, as described in the links below
and then you just need to reflash the firmware.
[Guide] [Unbrick] How to revive a hard bricked Moto G5 by TheFixItMan
https://forum.xda-developers.com/g5/how-to/rooted-moto-g5-run-morning-post-image-t3776012
https://android.stackexchange.com/questions/125135/how-to-pull-mmcblk0-to-a-windows-pc
Edit:
I first installed the Qualcomm HS-USB QDLoader 9008 driversYou have a xt1955-4 , I haven't seen anyone other than you post that they tried the blankflash.
It's possible that it's not compatible.
The XT1955-5 is single sim, and I believe the XT-1955-4 is dual SIM, and possible other hardware differences.
Sent from my mata using XDA Labs
I made a couple of mmcblk0.img s but to my knowledge no one as got them to work.you managed to raise the mmcblk0.img of the g7 power ?
What is it listed as?I first installed the Qualcomm HS-USB QDLoader 9008 drivers
but they don't appear after restarting the pc,
in device manager /ports does not appear: qualcomm hs-usb qdloader 9008!!!
please help me T.T
it only appears in windows 10 x64, that the usb device is not recognized and appears in the device manager, in universal serial bus controllers: Unknown USB device (device descriptor request error).I made a couple of mmcblk0.img s but to my knowledge no one as got them to work.
Sent from my jerry_cheets using XDA Labs
---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------
What is it listed as?
Sent from my jerry_cheets using XDA Labs
You can select the Qualcomm USB drivers in device manager.it only appears in windows 10 x64, that the usb device is not recognized and appears in the device manager, in universal serial bus controllers: Unknown USB device (device descriptor request error).
I cannot select the QUALCOMM driver, it does not appear.You can select the Qualcomm USB drivers in device manager.
Sent from my mata using XDA Labs
Do you know if this mode exists for the G7 Power?You can select the Qualcomm USB drivers in device manager.
Sent from my mata using XDA Labs
I don't KnowDo you know if this mode exists for the G7 Power?
&t=270s