yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Questions & Answers] zgfg:
Usually, OTA should update from c432 b182 to b210 (still MarshMallow) and then to b378

To receive OTA notifications, you must have WiFi, but also a valid SIM card.

For successful OTA, phone must not be rooted, and you must not have TWRP.

You can also speed-up/trigger OTA by checking in Settings/System Updates

Even if OTA is not coming, you can reboot to eRecovery (switch off, connect to Charger, press and keep pressing Vol+, press Pow) and choose Download and install latest firmware and recovery

You can also try to upgrade from HiSuite (not sure if eRecovery and HiSuite options work for MM)

--

Don't know for which reason you were not able to get proper OTA updates.

You then messed up the order of builds by manual flashing (b210->b182->b361)

By Fastboot answers, your phone still reports it is on b182 (not on b361)?!

How did you flash b361 - by DLOAD, and did you use FullOTA-MF-PV package (DLOAD fails with FullOTA-MF without PV)?

Eg, on Firmware Finder (you can install to any Android phone, just Add device: EVA-L09c432, you can also Install to PC), I see PV for b360 and b378, but not for b361 (!)

--

Can you boot to eRecovery (see above) and try with Download and install latest firmware (you must have WiFi available)

If not, maybe you can try installing b360 by DLOAD, but it must be FullOTA-MF-PV, see screenshot, package number #71496

Alternatively to FirmwareFinder, you can browse through:

https://pro-teammt.ru/online-firmware-database-ru/

--

If DLOAD to b360 (or to b378) will not work, you may try to reinstall b182 by DLOAD (your Fastboot still declares b182 for the current version), but you need to have complete c432 b282 package - one should be available from here

https://xdaforums.com/showpost.php?p=72153575&postcount=2

There is also the so-called Service Restore b210:

https://androidhost.ru/3xa

Must be unzipped, untarred, (may have zip and tar archives per folders and subfolders) until you find and unpack the following folders:

Software

Documentation

In Documentation, you will find oHuaeei original instructions for their Service shops - for DLOAD (please read)

In Software, there will be update* zip zip files (do mot unzip) that must be used for DLOAD.

If so (if you go for b182 or b210), you will be again on MM, then retry OTAs (and/or eRecovery, HiSuite) per instructions above
[Huawei P9 Questions & Answers] werindam:
sorry it was b360, but i think its changes nothing..

can't do anything through eRecovery - says getting package info failed.

i will try to download these dload packages and try to install

//edit//

cant install any update via dload ;/ shows error

i think only one way is to unlock bootloader with dc unlocker and then flash system in fastboot
[Moto G7 Questions & Answers] Phillen13:
Hi,

I accidentally applied an OTA in my rooted device and then Did somethings that caused a brick. Now my device is detected in the PC as Port 3 (Qualcomm HS-USB QDLoader 9008) and since Motorola is

not providing the Blankflash file needed to rescue the device, the only way to rescue my device is to generate a Loader.img from any of the good people who are using a Motorola g7.

Somebody Please help me out.

I will post the steps below.

1. Get another exact variant of your device and INSERT an SD Card on it. The device chipset must be the same. Thus, if your device (bricked) is MSM8269, the required device CPU has to be MSM8269, too.

2. Root the working (exact variant) device and install Terminal Emulator on it.

3. Download and install Busybox on the device. You may download Busybox from here

4. Once BusyBox is installed, launch/open it and run/install its dependencies/files by clicking on the appropriate key.

5. Now, launch/open Terminal Emulator on the device and follow these procedures:

a. On Terminal EmulatorType:

su

and hit/tap the Enter key. You will be prompted to GRANT Terminal emulator a Root Access, click GRANT.

b. Then, type:

dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960

and hit/tap the Enter key.

6. Wait few minutes or until Terminal Emulator completes the process.

7. Now, check the Root Folder/Directory of the SD Card inserted on the phone. You will notice that a file named Loader.img has been created.

GOOD! That's your Qualcomm device Unbrick file.

I have referred this article here

https://www.aryk.tech/2017/02/how-to-unbrick-debrick-qualcomm-android.html?m=1

Someone please be kind enough to post a Loader for Moto g7 as there are many people who needs it.

Thanks in advance.
[Moto G7 Questions & Answers] skuppej:
Here is my Loader.img for:

Model Number (SKU): XT1962-1

Baseband Version: M632_12.52.01.86R RIVER_NA_CUST

Bootloader: MBM-2.1-river_retail-b89272e-190401

Kernel: 4.9.112-perf+ #1 Mon Apr 1 21:51:39 CDT 2019

Build #: PP029.114-16-5-2

https://drive.google.com/open?id=1Bb45SC7YU2NnyIlGsHJKbbnq7mKHQ1aj

MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e

MD5: a1a03e2225dd723c5c3549568ad7f4b1

Good luck!
[Moto G7 Questions & Answers] Phillen13:
Thanks a lot skuppej. You saved my phone. Let me try with this file and post the results for other people here.:good::good::fingers-crossed::fingers-crossed::fingers-crossed::victory::victory::victory:

Thanks a lot again for spending the time needed to extract the Loader file. Only if there were more people like you.
[Moto G7 Questions & Answers] khawks:
thanks for the loader.img - im not unbricked yet

Thank you for taking the time to generate the loader.img file skuppej. (and Phillen13 for posting a possible solution)

I hard-bricked my XT1962-1 with magisk somehow, and it only shows up in windoze dev manager as the qualcomm 9008 com3:

i used rufus and then diskimagerev2 to write the image to a 8GB card, but then had no luck getting the phone to do anything using the buttons. i will try to write the loader.img using my linux box and see what happens.

the referenced article is a bit weak when it comes to the step of booting the loader.img and i have not been able to find any secondary reference for using a loader.img as a process for recovering.

i would like to know what the file size (and ideally a MD5 hash) for the loader.img its possible that the 165M file on GD is too small?

i tried a 16GB card and imaged with disk imager in ubuntu, inserted card into phone, and could not see any action no lights etc, by holding down the power button for various time lengths, then holding down power and vol down buttons.. the only response i discern is the windows sound of a USB device being inserted three tones down, then recognised three tones up. (Qualcomm HS-USB QDLoader 9008 in DevMan as COM3:)

to respond below, yes i used unofficial TWRP then magisk to patch boot.img and got a bunch of red errors...
[Moto G7 Questions & Answers] maybeme2:
May I ask how you successfully rooted your Moto G7?

I successfully unlocked my bootloader but when I used Magisk to patch the boot.img I got stuck in bootloops that finally required a phone reset to get out of.

So, how did you root your G7? Did you use the unofficial twrp? (As far as I know there's no official twrp yet).

Thanks.
[Moto G7 Questions & Answers] skuppej:
No problem! But I am still dubious. Did this actually work for you? I've been in a pickle and had to use a loader.img file for a previous phone and it worked, but I just want to make sure what I produced is good.

I will try making another loader.img and checking/comparing the hashes. I feel you man!

For me, on both G7's I've owned, I updated to the latest OTA, unlocked the BL, installed unofficial TWRP, and then just flashed magisk.zip in TWRP. Crazy to me that other people are running into issues with this! My phone is US Retail, purchased directly from Motorola.

---------- Post added at 12:07 PM ---------- Previous post was at 11:12 AM ----------

I re-generated the loader.img and compared the MD5 and it was the same as the last one I generated.

Updated my link & added the MD5.
[Moto G7 Questions & Answers] maybeme2:
I'm one of those who ran into loads of trouble following the instructions from

https://xdaforums.com/moto-g7/how-to/root-g7-magisk-t3907084

I was wary of using the unofficial twrp but will do so now. Thanks.

My bootloader is already unlocked but when I needed to reset the phone to get out of the bootloops I lost my ota system update. Is there a way to flash the system updates after rooting?
[Moto G7 Questions & Answers] skuppej:
Yeah I don't recommend following those older instructions...the latest magisk.zip flashes just fine in TWRP....

When it comes to it, I'm hoping I won't have any trouble flashing the latest OTA from https://mirrors.lolinet.com/firmware/moto/river/official/RETAIL/ or from LMSA (I'd probably try this first..since it seems like it would be more 'official')

Right now I am on PP029.114-16-5-2 which I think is the latest...at least OTA didn't want to go any further before I rooted etc.

If you are having trouble with OTA and you don't mind losing your data, I'd do a full magisk uninstall, re-lock of the bootloader/flash using LMSA files.
[Moto G7 Questions & Answers] khawks:
loader.img failing MD5

I downloaded loader.img using this link: (Thank you skuppej)

xxxx://drive.google.com/file/d/17Wd...GkJygj25PjEYJU - hmm cant post links yet thats ridiculous

MD5: ec2ff9fd90ba8869a1cc5d9021d8f175

actually downloaded it twice and both times failed MD5 hash:

my check....a1a03e2225dd723c5c3549568ad7f4b1

so i added the file to my google drive (assuming that GD uses hash checking, pretty sure it does with file & sync). I am now figuring out how to generate MD5 data on my google drive to see if its good. OK google drive MD5 fails as well.

i have ran into this kind of thing before, skuppej would you be willing to put the loader.img into a container such as a .zip file and out that on your GD please?
[Moto G7 Questions & Answers] skuppej:
That's odd!

OK NP, I've updated https://xdaforums.com/showpost.php?p=79702551&postcount=2 with the .zip and the MD5 for both.

I was able to download it/extract/get matching MD5 sums from an external location, so it should all be good..
[Moto G7 Questions & Answers] Phillen13:
I have not tried flashing it till now. Been busy with work. I will let you know once I have finished. Thanks for the updated .zip file .You are really a very helpful person.
[Moto G7 Questions & Answers] khawks:
trying loader.img

Phillen13:

Did you find time to try the loader.img file?

The MD5 hash for the .zip file matches, but I am having trouble getting the loader.img file itself to agree with:

MD5 (zip): 533fd344eb29590ec285f3e5fd50e47e

MD5: ec2ff9fd90ba8869a1cc5d9021d8f175 ----my check....a1a03e2225dd723c5c3549568ad7f4b1

It would be helpful to have more members messing with this.

K.
[Moto G7 Questions & Answers] skuppej:
Hi khawks. I just generated another and checked the MD5 and it is actually a1a03e2225dd723c5c3549568ad7f4b1, the same as you have checked.

So I guess the new Loader file in the zip is the correct one..extremely sorry for the wild goose chase! I must have confused it with the old one
[Moto G7 Questions & Answers] khawks:
anyone else had luck getting loader.img to boot?

I have not been able to get my G7 to boot (holding vol down and power keys) (or all three) using a UHS-1 8GB card or a class 4 16gb card with loader.img on it.

Anyone else have any luck?
[Moto G7 Questions & Answers] TerrestrialHost:
So I was able too boot using this Loader file..... but I'm stuck from that point. The bootloader shows as locked, won't allow me to unlock it, won't allow me to boot anything, and most fastboot commands return FAILED (remote failure). Does anyone have any advice on how to proceed from this point?
[Moto G7 Questions & Answers] khawks:
Could you please post specific into such as the size and class of your SD card you used to put the loader.img on?
[Moto G7 Questions & Answers] TerrestrialHost:
Yeah, I used a 128GB Class 10 which I had empty. I used this software to put the image on the SD card: https://www.balena.io/etcher/

I then completely turned my phone off, and then booted using Power/VolDown with the card inserted.
[Moto G7 Questions & Answers] skuppej:
I'm wondering if the BL version needs to match? OTAs I've noticed do change BL versions..

I'll give it a shot myself if I can find a spare microsd card somewhere
[Moto G7 Questions & Answers] TerrestrialHost:
I think there's a good possibility that my problem is related to the bootloader version. I had just flashed the PPOS29.114-16-7-2 version stock rom.

Anyone here have that version, and might be willing to create a Loader.img file? Hell, I'd appreciate it enough to send them some bitcoin in gratitude, or whatnot.
[Moto G7 Questions & Answers] maybeme2:
I would help if I know how.

I just checked and I have PPO29.114-16-7-2 installed. Note that it is PPO29 not "PPOS29". Mine has no S in case that makes a difference.
[Moto G7 Questions & Answers] TerrestrialHost:
Do you have your phone rooted? Or is your bootloader unlocked so you can boot into TWRP?

If so, you can follow the instructions on the 1st post, either in an "adb shell" from your computer (if you're booted into TWRP), or in a terminal on your device if it's rooted.

Let me know if any part of his original instruction is unclear, and I can clarify for you.
[Moto G7 Questions & Answers] maybeme2:
My phone is rooted and I have the unofficial twrp installed. I also have an extra SD card installed.

Can I produce the file via twrp? I don't have a terminal or busybox installed.

---------- Post added at 03:39 AM ---------- Previous post was at 03:25 AM ----------

OK, I have the file but it is too big to attach in this message. How do you want me to get it to you? I don't use Google drive.
[Moto G7 Questions & Answers] TerrestrialHost:
Wow, that was quick! You're awesome! I made a MEGAdrop folder, which you can access here without setting up an account:

https://mega.nz/megadrop/5ddFu6BpClQ

If it works out, I can post a link here for others to access (if you don't mind -- as I understand it, doesn't contain any privately identifiable data).
[Moto G7 Questions & Answers] maybeme2:
Uploaded. Hope it helps.
[Moto G7 Questions & Answers] HT123:
My build number is PPOS29-114-16-7-2. (in case the S matters)

I just uploaded PPOS29-114-16-7-2.img

MD5 hash of file PPOS29.114-16-7-2.Loader.img:

55 d3 f5 b1 b4 0a b9 d5 2e 8d c9 93 b1 8d a2 e5
[Moto G7 Questions & Answers] khawks:
Did you get this to work?

Can anyone verify this is a viable recovery method from 9008 mode?
[Moto G7 Questions & Answers] TerrestrialHost:
So, I really appreciate y'all providing Loader.img files. Unfortunately, neither of the files uploaded changed anything. While I was able to boot to a bootloader, it still showed the device as locked and didn't permit me to do anything from the computer's fastboot command prompt. It shows as bootloader locked, IMEI as all 000000000, and can't unlock bootloader (states: "feature disabled").

So, while it seemed like a feasible solution initially, it hasn't gotten me anywhere (though, doubtless I am no professional -- so if anyone has any idea for things to try I'm all ears).

As an alternative fix, there seems to be some..... sort-of..... method for generating a blankflash file, as documented here:

https://androidforums.com/threads/guide-how-to-create-partition-xml-gpt.1125433/

I have fixed the .ods file provided to actually properly obtain the "starting LBA of partition" and "ending LBA of partition" from the gpt.bin file provided in the ROM flash files (the OP didn't take into account that integer sizes in bin2hex are read/recorded in reverse-ish).

I've included all the files from the post, as well as my attempt at generating a partition.xml file. I have been unable to use that partition.xml to generate the necessary blankflash files (as per instructions in later posts).

If anyone has an interest in digging through that prior post/guide, as well as the files I have so far created, feel free. Maybe you see and understand something that I don't, or are able to parse the information more effectively.

Here's the link to the files I have so far (as well as the Loader.img files provided by previous posters ---THANKS BTW!!).

https://mega.nz/#F!k34SmA7S!Om-aPScPoxwClRusffnbJw

Good luck. And let me know if there is something I missed that I can manually work through to assist any and all of us poor folks with bricked G7's.

If the link is inaccessible, let me know, I'll make the files available via some alternate means.
[Moto G7 Questions & Answers] HT123:
RSD

Did you try to flash it with RSD lite? Not like it can work any less.
[Moto G7 Questions & Answers] skuppej:
Sorry homie...I took a look at that guide but, honestly, I can't make heads or tails of it.

I downloaded the files..but, beyond that, if you'd like to provide me specific instructions then I'll perform those.

I assume, to start, I'll need the adb/fastboot binaries for my Linux installation...but..OpenOffice......really??

Lmk
[Moto G7 Questions & Answers] khawks:
It is my understanding that in order to utilize RSD lite, the phone needs to be in fastboot mode. Myself and others are stuck in 9008 mode which means we need the "firehose" mode "MDMxxxx. Otherwise known as blankflash.

This post started with a method of booting from a memory card using a loader.img file generated by functional members phones.

I have not had success with this method, my phone shows no indication at all except for 9008 mode when holding down button and power buttons.

If I am missing something please let me know
[Moto G7 Questions & Answers] HT123:
I thought he said the loader image got him into the bootlaoder. I may have misunderstood.

The general idea was use the img to boot to bootloader, then try RSDLite.

Alternately, not sure of Motorola is still putting out mfastboot which may be worth a try as well. I had luck with a previous Motorola device with mfastboot where fastboot commands failed. I'm just spitballing ideas at this point though, but as i said before. It is not like these methods can work less the current one that does not work.

good luck
[Moto G7 Questions & Answers] skuppej:
Did anyone here ever get their bricked device fixed?
[Moto G7 Questions & Answers] patrick10K:
Does it work in MotoG7power?
[Moto G7 Questions & Answers] TerrestrialHost:
I did, both on Windows 10 and 7 installs. Throws remote error, same one I get from attempting fastboot flash. :-/

Also tried Lenovo MOTO smart assistant, which refuses to recognize there connected device as the appropriate model for recovery flash.
[Moto G7 Questions & Answers] HT123:
Stupid question but have you tried fastboot --set_active=a. Need the newest fastboot. Or booting twrp from fastboot and seeing what happens?
[Moto G7 Questions & Answers] TerrestrialHost:
I did try that. It doesn't recognize any valid boot slots, and reports gpt table as corrupt.

Unfortunately, when booted from the sd card I don't think it recognizes internal storage. I think booting from the sd card causes it to assume the sd card is the internal memory, and attempt to access it using incorrect hardware interface or whatnot. It seems oblivious to actual internal storage.

This is just assumptions based on my various attempts to cajole the fastboot bootloader off the sd card image into being useful. I'll provide a couple logs when i get a chance, just in case they offer anyone a different assessment of what's happening.
[Moto G7 Questions & Answers] fearlessiron:
UPDATE: A working blankflash is available here or via the Telegram group.

I managed to bring my hard-bricked XT1962-5 (RETEU) river back from the dead by adapting the blank flash posted over in the ocean forum. The programmer.mbn in that blank flash also works for river, probably because ocean also has the SDM632 processor. Using the star.exe from the blank flash, I extracted all files in bootloader.img from the XT1962-5 stock firmware that I had flashed before bricking my phone. I then put the extracted files into singleimage.bin (also using star.exe). I was very happy indeed to see the bootloader again after running blank-flash.bat:

Motorola qboot utility version 3.40
[ 0.000] Opening device: \\.\COM6
[ 0.000] Detecting device
[ 0.000] ...cpu.id = 186 (0xba)
[ 0.000] ...cpu.sn = 3144750707 (0xbb711673)
[ 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.300] Handling things over to programmer
[ 0.300] Identifying CPU version
[ 0.300] Waiting for firehose to get ready
[ 3.312] ...MSM8953 1.0
[ 3.312] Determining target secure state
[ 3.328] ...secure = yes
[ 3.359] Configuring device...
[ 3.359] Flashing GPT...
[ 3.359] Flashing partition with gpt.bin
[ 3.359] Initializing storage
[ 3.375] ...blksz = 512
[ 3.437] Re-initializing storage...
[ 3.437] Initializing storage
[ 3.483] Flashing bootloader...
[ 3.499] Flashing aboot_a with emmc_appsboot.mbn
[ 3.767] Flashing rpm_a with rpm.mbn
[ 3.829] Flashing tz_a with tz.mbn
[ 4.127] Flashing devcfg_a with devcfg.mbn
[ 4.173] Flashing cmnlib_a with cmnlib_30.mbn
[ 4.408] Flashing cmnlib64_a with cmnlib64_30.mbn
[ 4.627] Flashing keymaster_a with keymaster64.mbn
[ 4.862] Flashing prov_a with prov.mbn
[ 4.940] Flashing sbl1_a with sbl1.mbn
[ 5.068] Rebooting to fastboot
[ 5.084] Total time: 5.084s
[Moto G7 Questions & Answers] HueyT:
Blankflash file is also avail from the Tele$ram group of Moto G7
[Moto G7 Questions & Answers] cou94114:
If I understand the process, I could create a singleimage.bin file from the bootloader.img file any new firmware for the G7.

I downloaded PPOS29.114-134-4 a few days ago. I used the star.exe command from your zip file and got all the files you used to then load onto your device using the qboot.exe command. My device is currently operational so I don't want to try my plan, but this is very good information to have for future use. Thank you.
[Moto G7 Questions & Answers] clau_la2:
hi!

I dont know if root or not my G7, how to full unroot if I want to install android 10 (when its available)? first need to create a blank flash? only this?? or how to make a full backup??
[Moto G7 Questions & Answers] sd_shadow:
Best way to unroot is flash full firmware

Check which software channel your device is on in

Settings/about phone

Blankflash is leaked from chip maker.

You cannot create one.

You can make a backup in Twrp.

Or create a mmcblk0.img

See Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
[Moto G7 Questions & Answers] mattmsr82:
Is there any chance you could upload the custom blankflash? I have the same model as you. Thanks
[Moto G7 Questions & Answers] HueyT:
Avail. On Tele$ram
[Moto G7 Questions & Answers] gigawatt:
Hi, how do I extract the boot.img with the star.exe utility, I tried

star.exe extract bootloader.img and it didn't work
[Moto G7 Questions & Answers] schoeller:
Dear fearlessiron,

would you mind sharing the zipped recovery for XT1962-5?

Kind regards
[Moto G7 Questions & Answers] sd_shadow:
I'm pretty sure recovery is part of the boot.img now
[Moto G7 Questions & Answers] lolcos:
How do I use it?

It stops at "waiting for firehose to get ready"

---------- Post added at 05:33 PM ---------- Previous post was at 05:15 PM ----------

found this in another thread but now I need Firehose, does anyone have one? xt1962-4 RIVER