[Help Thread][ Moto G7 ](2019) Ask Any Question, Noob Friendly

Search This thread

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,694
2
9,396
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting
[/SIZE]​
[SIZE=+2]Specific to[/SIZE]

Moto G7
2019


Please feel free to share issues, questions and offer help. Noob questions are welcomed.

It is always best to use the Thanks button , in lieu of simply posting "Thank you".

attachment.php

Please keep discussion focused, on questions pertaining to this Device
attachment.php
List of supporters
...
...
...
...​
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!

Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here.
 
Last edited:

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,694
2
9,396
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
Specs
https://www.phonemore.com/models/motorola/moto-g7/
XT1962-1 Single-sim ..... Canada, USA.
XT1962-4 Dual-sim ....... Latin America, Brazil
XT1962-5 NFC Dual-sim Europe, Various (International)


If you flash an older Firmware than the current version on the phone.
  • The bootloader needs to be unlocked.
  • Do not install OTA Updates, they will likely brick the device.

Do not install OTA Updates if
  • The device is rooted;
  • A Custom recovery is installed
  • Firmware was downgrated

FAQs

Flashing Firmware and Updates

Custom Roms/Recovery/Root/



News.
 
Last edited:

thaunknownartist

Senior Member
Aug 17, 2011
194
330
30
New York
I will be picking up my Moto g7 within the next hour or so and I will begin trying to see how far I can get before I get back to streaming later
 

fix-this!

Senior Member
Apr 15, 2012
4,263
737
midwest
i just got mine yesterday at best buy. its a great phone compared to the g6. good design, lightweight and smooth Ui.

---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------

Does anybody know how to download full ROM from Moto/Lenovo?
I may try to make patched boot.img for root
I am not gonna make TWRP because I don't know how to do

each phone has its own partition table soo im not sure? the full rom probably isnt available yet.
 

aquinteros

New member
Jun 13, 2017
4
0
will there be a magisk release for the G7? if so, when will it be released? how long does the development process usually take ?
 

mingkee

Senior Member
How do I know if my G7 bought at Best Buy yesterday is "open market"? What other types are there?

I have two
One bought from Best Buy
One bought from B&H
Both are rooted and bootloader unlocked

---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------

will there be a magisk release for the G7? if so, when will it be released? how long does the development process usually take ?

Just use the current version to patch boot.img and install Manager
 

mingkee

Senior Member
So, is the one from Best Buy 'open market'?

More importantly for me, how exactly would I unlock the bootloader and root the G7. Can it be unrooted if necessary? I thought that was all still in development including no twrp recovery available.

I have both rooted by patching boot.img with Magisk
Since I downloaded full ROM, I can revert it to clean stock if I want to
 
  • Like
Reactions: maybeme2

HueyT

Senior Member
Apr 3, 2014
4,781
2,164
New Albany, IN
OnePlus 7T
So I've been trying to perform a stock update but can't get my device to use magisks OTA ability. So I'm trying to flash the recent OTA with RSD but can't get the program to detect my device. I'm at a loss, would someone be able to help me out?

RSD only recognize phones with Windows 7. Windows 10 will run RSD but won't recognize any phones (even in compatibility mode)

---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------

I have both rooted by patching boot.img with Magisk
Since I downloaded full ROM, I can revert it to clean stock if I want to

What is your exact model from BestBuy and BH Photo? Are they the same? Will they both work for Verizon? I assume RETUS or RETAIL? XT1962-1?
 
Last edited:

mingkee

Senior Member
rsd only recognize phones with windows 7. Windows 10 will run rsd but won't recognize any phones (even in compatibility mode)

---------- post added at 04:36 pm ---------- previous post was at 04:35 pm ----------



what is your exact model from bestbuy and bh photo? Are they the same? Will they both work for verizon? I assume retus or retail? Xt1962-1?

xt1962-1
retus
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    [SIZE=+2]This thread has been created
    for
    Questions & Answers/Troubleshooting
    [/SIZE]​
    [SIZE=+2]Specific to[/SIZE]

    Moto G7
    2019


    Please feel free to share issues, questions and offer help. Noob questions are welcomed.

    It is always best to use the Thanks button , in lieu of simply posting "Thank you".

    attachment.php

    Please keep discussion focused, on questions pertaining to this Device
    attachment.php
    List of supporters
    ...
    ...
    ...
    ...​
    To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
    If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!

    Supporters: If you want to be put on or off the list, just make a request here in the thread!
    Before posting anything, I strongly advise you to read
    Please look for a similar thread when visiting another device forum.
    If you would like to create a [Help Thread] please Click Here.
    3
    I am trying to flash to stock firmware back into my Moto g7 but every time I do I get several failures during the flashing process. Right now my phone is soft bricked and will only bootloop the start up screen saying that my device cant be trusted due to an unlocked boot loader and then it will bring up the blue Moto screen with the M logo for just a few seconds then it will start it all over again. I can get into fastboot and I can open TWRP if its connected through usb to the computer. This is what happens every time I try to flash the stock firmware I got through the Motorola/Lenovo web site:


    C:\New folder\subfolder\Motorola_Moto_G7_XT1962-1_RIVER_PPO29.80-10_cid50_XT1962-1_9\Motorola_Moto_G7_XT1962-1_RIVER_PPO29.80-10_cid50_XT1962-1_9\Firmware>echo off
    max-sparse-size: 268435456
    finished. total time: 0.016s
    ...
    OKAY [ 0.000s]
    finished. total time: 0.000s
    target reported max download size of 536870912 bytes
    sending 'partition' (45 KB)...
    OKAY [ 0.000s]
    writing 'partition'...
    (bootloader) Validating 'gpt.default.xml'
    (bootloader) Committing 'gpt.default.xml'
    (bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
    (bootloader) Flashing primary GPT image...
    (bootloader) Flashing backup GPT image...
    OKAY [ 0.094s]
    finished. total time: 0.094s
    target reported max download size of 536870912 bytes
    sending 'bootloader' (7419 KB)...
    OKAY [ 0.181s]
    writing 'bootloader'...
    (bootloader) Validating 'bootloader.default.xml'
    (bootloader) Security version downgrade
    (bootloader) Image tz failed validation
    (bootloader) Preflash validation failed
    (bootloader) Security version downgrade
    (bootloader) Image devcfg failed validation
    (bootloader) Preflash validation failed
    (bootloader) Cancelling 'bootloader.default.xml'
    FAILED (remote failure)
    finished. total time: 0.399s
    target reported max download size of 536870912 bytes
    sending 'modema' (65340 KB)...
    OKAY [ 1.434s]
    writing 'modema'...
    (bootloader) Invalid partition name modema
    FAILED (remote failure)
    finished. total time: 1.434s
    target reported max download size of 536870912 bytes
    sending 'fsga' (11352 KB)...
    OKAY [ 0.250s]
    writing 'fsga'...
    (bootloader) Invalid partition name fsga
    FAILED (remote failure)
    finished. total time: 0.265s
    target reported max download size of 536870912 bytes
    sending 'dspa' (16384 KB)...
    OKAY [ 0.360s]
    writing 'dspa'...
    (bootloader) Invalid partition name dspa
    FAILED (remote failure)
    finished. total time: 0.360s
    target reported max download size of 536870912 bytes
    sending 'logoa' (2747 KB)...
    OKAY [ 0.062s]
    writing 'logoa'...
    (bootloader) Invalid partition name logoa
    FAILED (remote failure)
    finished. total time: 0.062s
    target reported max download size of 536870912 bytes
    sending 'boota' (32768 KB)...
    OKAY [ 0.766s]
    writing 'boota'...
    (bootloader) Invalid partition name boota
    FAILED (remote failure)
    finished. total time: 0.781s
    target reported max download size of 536870912 bytes
    sending 'dtboa' (564 KB)...
    OKAY [ 0.015s]
    writing 'dtboa'...
    (bootloader) Invalid partition name dtboa
    FAILED (remote failure)
    finished. total time: 0.031s
    target reported max download size of 536870912 bytes
    sending 'systema' (262141 KB)...
    OKAY [ 5.706s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.706s
    target reported max download size of 536870912 bytes
    sending 'systema' (262140 KB)...
    OKAY [ 5.680s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.696s
    target reported max download size of 536870912 bytes
    sending 'systema' (242217 KB)...
    OKAY [ 5.281s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.296s
    target reported max download size of 536870912 bytes
    sending 'systema' (262141 KB)...
    OKAY [ 5.688s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.703s
    target reported max download size of 536870912 bytes
    sending 'systema' (246923 KB)...
    OKAY [ 5.393s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.408s
    target reported max download size of 536870912 bytes
    sending 'systema' (262142 KB)...
    OKAY [ 5.690s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.705s
    target reported max download size of 536870912 bytes
    sending 'systema' (262141 KB)...
    OKAY [ 5.743s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.758s
    target reported max download size of 536870912 bytes
    sending 'systema' (252260 KB)...
    OKAY [ 5.466s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.466s
    target reported max download size of 536870912 bytes
    sending 'systema' (262140 KB)...
    OKAY [ 5.750s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 5.765s
    target reported max download size of 536870912 bytes
    sending 'systema' (60336 KB)...
    OKAY [ 1.313s]
    writing 'systema'...
    (bootloader) Invalid partition name systema
    FAILED (remote failure)
    finished. total time: 1.313s
    target reported max download size of 536870912 bytes
    sending 'system_b' (255208 KB)...
    OKAY [ 5.531s]
    writing 'system_b'...
    OKAY [ 1.093s]
    finished. total time: 6.624s
    target reported max download size of 536870912 bytes
    sending 'system_b' (262140 KB)...
    OKAY [ 5.702s]
    writing 'system_b'...
    OKAY [ 1.047s]
    finished. total time: 6.749s
    target reported max download size of 536870912 bytes
    sending 'system_b' (55588 KB)...
    OKAY [ 1.203s]
    writing 'system_b'...
    OKAY [ 0.250s]
    finished. total time: 1.453s
    target reported max download size of 536870912 bytes
    sending 'vendora' (262143 KB)...
    OKAY [ 5.655s]
    writing 'vendora'...
    (bootloader) Invalid partition name vendora
    FAILED (remote failure)
    finished. total time: 5.670s
    target reported max download size of 536870912 bytes
    sending 'vendora' (252824 KB)...
    OKAY [ 5.499s]
    writing 'vendora'...
    (bootloader) Invalid partition name vendora
    FAILED (remote failure)
    finished. total time: 5.514s
    target reported max download size of 536870912 bytes
    sending 'vendora' (119568 KB)...
    OKAY [ 2.575s]
    writing 'vendora'...
    (bootloader) Invalid partition name vendora
    FAILED (remote failure)
    finished. total time: 2.590s
    target reported max download size of 536870912 bytes
    sending 'oema' (71128 KB)...
    OKAY [ 1.562s]
    writing 'oema'...
    (bootloader) Invalid partition name oema
    FAILED (remote failure)
    finished. total time: 1.562s
    target reported max download size of 536870912 bytes
    sending 'oem_b' (41292 KB)...
    OKAY [ 0.907s]
    writing 'oem_b'...
    OKAY [ 0.187s]
    finished. total time: 1.094s
    erasing 'modemst1'...
    OKAY [ 0.016s]
    finished. total time: 0.016s
    erasing 'modemst2'...
    OKAY [ 0.016s]
    finished. total time: 0.016s
    erasing 'userdata'...
    OKAY [ 0.062s]
    finished. total time: 0.062s
    erasing 'DDR'...
    OKAY [ 0.000s]
    finished. total time: 0.000s
    target reported max download size of 536870912 bytes
    sending 'fsga' (11352 KB)...
    OKAY [ 0.250s]
    writing 'fsga'...
    (bootloader) Invalid partition name fsga
    FAILED (remote failure)
    finished. total time: 0.265s
    ...
    OKAY [ 0.141s]
    finished. total time: 0.141s

    1. The firmware you're trying to flash is older than your current. You will brick your phone that way. The current firmware is here assuming you're in the US.

    2. The commands are:
    Code:
    fastboot getvar max-sparse-size
    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    fastboot flash modem NON-HLOS.bin
    fastboot flash fsg fsg.mbn
    fastboot erase modemst1
    fastboot erase modemst2
    fastboot flash dsp adspso.bin
    fastboot flash dtbo dtbo.img
    fastboot flash logo logo.bin
    fastboot flash boot boot.img
    fastboot flash system system.img_sparsechunk.0
    fastboot flash system system.img_sparsechunk.1
    fastboot flash system system.img_sparsechunk.2
    fastboot flash system system.img_sparsechunk.3
    fastboot flash system system.img_sparsechunk.4
    fastboot flash system system.img_sparsechunk.5
    fastboot flash system system.img_sparsechunk.6
    fastboot flash system system.img_sparsechunk.7
    fastboot flash system system.img_sparsechunk.8
    fastboot flash system system.img_sparsechunk.9
    fastboot flash system_b system_b.img_sparsechunk.0
    fastboot flash system_b system_b.img_sparsechunk.1
    fastboot flash system_b system_b.img_sparsechunk.2
    fastboot flash vendor vendor.img_sparsechunk.0
    fastboot flash vendor vendor.img_sparsechunk.1
    fastboot flash vendor vendor.img_sparsechunk.2
    fastboot flash oem oem.img
    fastboot flash oem_b oem_other.img
    fastboot erase userdata
    fastboot erase DDR
    fastboot oem fb_mode_clear

    You don't need to specify the 'a' partition. When you did you also made typos. For example you tried to flash to 'fsga' instead of 'fsg_a' and 'oema' instead of 'oem_a'. Flashing to '_a' partitions is unnecessary. Just use the commands above.
    2
    Does the Moto G7 support hdmi video out on the USB-C port? Thanks!
    I don't see any specs that say for sure, but I expect it will not as the G6 line did not.
    2
    @Terminator145
    Relocking a Motorola bootloader is not for novices.
    Many posts from people who tried and bricked their phones.
    You are better off selling it as unlocked and buying a locked one.
    2
    Good Afternoon all,
    To start, I do apologize if this has been asked before. Currently, i have a moto G7 that i ended up unlocking the bootloader and rooting back in 2020 after my phone bricked bricked itself because of a bad sd card (i had rooted initially to attempt to recover some photos off the sd, didn't have backups enabled at the time. Learned that lesson quick).

    Recently, i have been having issues with the device, and what i am looking to do is unroot the device and re-lock the bootloader, and re-flash the base version of android back onto it, but haven't found anything super helpful, nor have i found any links to the correct files i would need to do so. I have attempted use Magisk's 'complete uninstall' feature, but rebooting still shows the warning that the bootloader is unlocked, and I am unable to install the android security updates still that are pending (they seem to fail at around 23% when installing).

    Device name: moto G7 (XT1962-1)
    Carrier: RetCA (Retail Canada)
    Security Patch Level: August 1, 2020
    Build number: QPUS30.52-16-2-5
    If anyone has guidance on how to properly finish unrooting my device, it would be much appreciated!

    You can get back to the latest version of un-rooted stock by using the Motorola RSA program but this will not re-lock the bootloader. I've used RSA to re-image several Moto devices including a Moto G7 Power a few times:

    Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
    https://forum.xda-developers.com/t/rescue-and-smart-assistant-lmsa-motorola-lenovo-only.3951714/

    As to re-locking the bootloader, supposedly that can be done but in the past I've heard that attempting to do so can result in a hard brick. That being said, my knowledge about that is dated and there are others here who could better speak to that.