09-20-2019 07:35 PM - edited 09-20-2019 07:38 PM
It seems Moto Agents disregard all the G7 owners having problem with software updates. Shame on them and on Levono. This is far away from what customer support means.
By the way software update issue is not the only one G7 has since its release (almost 1 year).
1. Bad audio quality during recording
2. Stripes/Lines on dark photos
If these are hardware related and cannot be resolved via software update the phone should be recalled by the manufacturer.
In the past I owned many Motorola (Atrix 2, G5, Moto X 2013, Moto X2) and never had issue with these.
From my perspective I'm going to try the manual upgrade via RSDLite once I'm back from vacation and if it does not work I will return the phone to the seller and never by Motorola again.
09-21-2019 01:13 AM
Friday the 13th this month was not an unlucky day... i solved it and succeeded flashing 1. August 2019 update to my RETEU2 MotoG7+
I posted a long text describing lots of background here .. it disappeared....
maybe it was deleted automatically, because it contained a link to the G7 plus firmware that can be found on lenovo/motorolas own servers...
well.. lets see what happens to this post.
What worked for me finally was manual fastboot flashing
with the following commands: ( you will erase all your data on the phone ! )
First download install official LMSA form Lenovo
and let it download and extract
the latest firmware from Motorola ( I had LMSA Version 126.96.36.199)
You should find the firmware in the IMGDIR below.
cd C:\Program Files (x86)\Lenovo Moto Smart Assistant
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition %IMGDIR%\gpt.bin
fastboot flash bootloader %IMGDIR%\bootloader.img
fastboot flash modem_a %IMGDIR%\NON-HLOS.bin
fastboot flash fsg_a %IMGDIR%\fsg.mbn
fastboot flash bluetooth_a %IMGDIR%\BTFM.bin
fastboot flash dsp_a %IMGDIR%\dspso.bin
fastboot flash logo_a %IMGDIR%\logo.bin
fastboot flash boot_a %IMGDIR%\boot.img
fastboot flash dtbo_a %IMGDIR%\dtbo.img
fastboot flash system_a %IMGDIR%\system.img_sparsechunk.0
fastboot flash system_a %IMGDIR%\system.img_sparsechunk.1
fastboot flash system_a %IMGDIR%\system.img_sparsechunk.2
fastboot flash system_a %IMGDIR%\system.img_sparsechunk.3
fastboot flash system_a %IMGDIR%\system.img_sparsechunk.4
fastboot flash system_b %IMGDIR%\system_b.img_sparsechunk.0
fastboot flash system_b %IMGDIR%\system_b.img_sparsechunk.1
fastboot flash vendor_a %IMGDIR%\vendor.img_sparsechunk.0
fastboot flash vendor_a %IMGDIR%\vendor.img_sparsechunk.1
fastboot flash oem_a %IMGDIR%\oem.img
fastboot flash oem_b %IMGDIR%\oem_other.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
2 things seem critical for success:
- always specify the complete partition name ( _a / _b )
relying on the default did not work for me.
- you cannot downgrade bootloader (without unlocking it .... what would void warranty....)
you only can flash a bootloader (and the rest) of the same or of a higher version !
the date in some vars
shown by "fastboot getvar all"
gives a hint whats on the device:
(bootloader) git:abl: MBM-3.0-lake_retail-c37f6b5-190802
Good luck !
09-21-2019 01:32 AM
just what I think:
The issue with LMSA flashing is
1) LMSA does not use correct partition names with _a
2) LMSA just calls "fastboot flash" commands in an "fire and forget" way
It does not check the result of the command
to show a Warning or Error in case something goes wrong
This 1) lead to a new gpt and bootloader beeing flashed,
but the rest of the flash commands fail because of nonexistent partitions without warning beeing displayed
Now if the new gpt/bootloader is backward compatible or it boots a fallback image,
you are still on the same or even older version....
@LENOVO LMSA dev:
when running the external flash commands, it would be really great if you create a logfile from their stdout/stderr
And even better to pass errors up to GUI and show that something went wrong ;-)
09-22-2019 09:24 AM - edited 09-22-2019 09:26 AM
09-23-2019 01:45 PM
> Did you really manage to update your RETEU2 phone within RETEU firmware?
Yes. From all what I read here and in other forums it looks like the firmware itself is the same.
Looks like the software channel is sent to the Moto Servers to decide wether to roll out the OTA Update or not...
09-25-2019 02:40 PM - edited 09-25-2019 02:50 PM
Lenovo just release a new version of LMS v188.8.131.52 and I was able to update my Moto G7 Plus to LAKE_RETEU_PPWS29.98_111_3_subsidy_DEFAULT_regulatory_DEFAULT_CFC without a problem.