Related
Hello,
This is a short (hopefully) guide on how to downgrade your Moto X 2013 from Android 5.1 to 4.4.4 (and lower).
The procedure is fairly simple and takes about 10-15 minutes, once you get the files you need.It does however needs some technical understanding of how to use fastboot, command prompt and eventually unlocking your bootloader.Fairly strong reading skills recommended.
WIth that said, make sure you read thorough and even few times before you take any actions.
This method has now been proven to be working by multiple people, on many different versions of Moto X 2013, including GPE
Disclaimer
Although this procedure has been tested by me and some friends numerous times, it still has some risk involved.You MUST be aware of the potential risks of modifying your phone software and performing actions that may lead to complete defunct of your device.
As you may expect I will not take any responsibility or be accountable for any damage or loss you may incur by following this guide.
Performing a system downgrade WILL void your warranty and it is NOT supported by Motorola/Lenovo or their service network.
I also recommend you read This post by KidJoe about the potential risks that downgrade might involve.
This guide has came up being needed as many people were afraid to downgrade after reading the post of KidJoe and I don't blame them, it is possible something to go wrong and you end up with non-working device.
HOWEVER, this has been tested on more than 10 separate Moto X 2013 and more than 12 times on my own device, which makes me to believe that it's generally safe.
Prerequisites
You need your bootloader unlocked.Motorola and their bootloader does NOT support downgrading and it will spit errors in fastboot.
WHEN YOU UNLOCK YOUR BOOTLOADER ALL YOUR PERSONAL DATA ON YOUR DEVICE WILL BE LOST.MAKE SURE YOU BACKUP YOUR FILES AND THEN PROCEED.
You can find how to unlock your bootloader HERE or just use the search here in the forums, plenty of info on that matter.
If you cannot or don't want to unlock your bootloader, then you CANNOT downgrade.
Files Needed
For this tutorial we`ll do downgrade from 5.1 to 4.4.4.This is the safest downgrade and it will be successful if you follow all the steps w/o any skipping.
The Android image used is for XT1052, but if you got different model, you can find the image for your own model and use that instead.
1.First you need a signed image of Android 4.4.4 for Moto X 2013.You can find one Filefactory or RetailEU here <=> RetailGB here <=> RetailDE here
If you want to download the image faster, use the Yandex-hosted images, FileFactory is slow.
2.Motorola Device Drivers: You can find them Here
3.Motorola Fastboot and generic adb/fastboot tools package: You can find it attached to this post or click Here
Flashing your device
0.Charge your device's battery to at least 35%.
1.Extract the archive with the signed images somewhere (in this case I`ll use C:\temp , but you can use any drive or directory if you so desire).
2.Extract the android-tools archive in the same directory.You should have boot.img, recovery.img, system.img and mfastboot in same directory.
3.Reboot your device in bootloader (Power your device off -> Hold Volume Down and Press Power button -> then release).
!!THIS WILL DELETE YOUR USER FILES EVEN IF YOU HAVE YOUR BOOTLOADER ALREADY UNLOCKED!!!
4.Open a command prompt and navigate to C:\temp and execute the following commands:
Code:
mfastboot erase cache
mfastboot erase userdata
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot erase userdata
mfastboot reboot
DO NOT skip erasing the userdata, doing so , you'll most likely end up with soft brick.Just don't do it.
Result
Congratz, now you have successfully downgraded your device to Android 4.4.4
The device will take some time the first boot to create dalvik cache and some other stuff, but it should not take more than 5 minutes.
When your device boots, it will ask you at some point to downgrade the motorola services bla bla, agree to that, your device will reboot and it will tell you that the downgrade was successful.I did this more than 10 times, seems to be totally safe.
Any feedback will be appreciated, you may ask questions, but don't expect me to answer to every single one.
If I missed something, I'll add up/fix as soon as I can.
FAQ
What if I want to downgrade to Android 4.4.2 / 4.3 / 4.2.2 ?
This is possible, the procedure is the same as listed above.You just have to know that if you do such downgrade, you should never update via OTA update, at any cost.This will corrupt the bootloader of your device and you won't be able to restore it.If you downgrade to anything below 4.4.4 and you want at some point to upgrade, you should do it ONLY by official signed image and NOT OTA.
You've been warned.
I can't find the exact same firmware that my device runs, eg. AsiaRetail.Is it possible to use firmware image from a different region/operator?
While it's recommended to use your exact firmware image, it is not necessary. You can use an image from other region, but you should follow some simple rule. Try to stick to the same phone model, eg XT1052 firmware.
I updated via OTA but I've recently rooted and installed a custom rom. Is it necessary to go back to stock 5.1 to downgrade?
No need, as long as your custom rom/kernel didn't mess with the fs of the partitions.
Why is this flashing procedure cut down, omg there are other commands that I've read in other guides and they say that I must flash modem, fsg, delete some magical modem states, why you didn't include these?!?
While it is true that other guides suggest you flash modem, fsg and some other things, these are mainly driven from the Motorola's own procedure xml file, flashing these is not necessary at all, this is used to repair eventual errors in these parts, but usually there is no problem there at all.
Another thing is that these parts are cross-compatible and leaving them as they are is perfectly fine.
How do I go back to 5.1 stock?
1.Do NOT update by OTA, just to be on the safe side.
2. Use the same procedure as described, but with image of 5.1 instead.
How do I disable the OTA notifications?
1. If you're rooted, then just delete or revoke permissions of /system/priv-app/3c_ota.apk
2. If you're not rooted, then don't install the Motorola Update Services from the Play Store. If you already updated them, then just uninstall the update and that's all.
I'm getting "Not enough space" errors, when I try to flash the system.img.I'm using mfastboot, but still the same problem?!?
Use this and it will work:
mfastboot flash system system.img -P
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
legend.in.boxers said:
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
Click to expand...
Click to collapse
Having custom recovery doesn't affect anything. This process will flash the stock recovery.
You don't need to enter any mode in the list, just leave the phone in the bootloader menu.
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
SanD-82 said:
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
Click to expand...
Click to collapse
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
I also have a problem with the optimising apps bug every time I reboot. Going to downgrade today. Hopefully everything will go well
liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
SanD-82 said:
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
Click to expand...
Click to collapse
That's not the case either, it was set to never keep it on during sleep and scaning always available was not allowed.The wifi just wont go off durring sleep and that's it.Tried all possible settings to no avail.Actually wifi was the 2nd highest battery consumer in the stats after the screen.This problem does not exist in 4.4.4.
I see...
It's actually hard to see how in 2015, Android keeps having these deal breaker issues...
I somehow feel that the best version of my xt1058 was when it was at 4.2.2... After the subsequent updates, bugs started to appear, and on 5.1 i got the first big issue...
Sent from my XT1058
Works!
Successfully downgraded. Thank you so much!
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
SanD-82 said:
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
Click to expand...
Click to collapse
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
IS Android 4.4.2 or 4.2.2 files avalable for indian moto x (xt1052 asian retail)
liveroy said:
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
Click to expand...
Click to collapse
WHere can i find those files??
visheshjotshi said:
WHere can i find those files??
Click to expand...
Click to collapse
Check the first post, the File Factory link, you can find tons of images there, the moto x 2013 is codenamed Ghost, if there is no model listed.
Good Luck.
Cant find files
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
visheshjotshi said:
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
Click to expand...
Click to collapse
Try searching 4pda.
Also, you don't need exactly your original firmware to begin with, it's recommended, but not necessary.
Thank you for this information. I dont have the wifi bug. But i have the mobile data bug. (Even turning it off it still continues to sap battery)
Sent from my XT1052 using XDA Free mobile app
I was looking for a post like this becouse my WiFi doesn't work on XT1058 5.1... i thought was a Lollipop related issue so wanted to downgrade to 4.4.4 and see if the problem really was related to android version, but it isn't. I downgraded successfully from 5.1 to 4.4.4 with your tutorial, but the WiFi problem persist. Now i know i'm really screwed up becouse i tried i believe everything possible... airplane mode, factory reset, cache wipe, full wipe, custom rom, custom kernel, android 5.1, android 4.4.4, different AP's and routers, delete supplicant conf... So i don't know what to do. Te specific problem is that WiFi can see available networks, but randomly some of them disappear and others show up, and when i try to connect por ex to my home network, it says "connecting" and then "saved", with all networks happens the same. Does anyone has a clue? BTW, thanks for your post!
Download the archive from this link https://app.box.com/s/idnxxhunecvtxf1mbqve0bpooyogvxng
unzip it on your device and copy the files to /persist.You need root to do that. Set the permissions to rw-r-r--- and rw-rw---- for the .bt_nv.bin
Reboot and see if something changes.
Hello guys,
Like many of you my Moto G XT1068 is dead because of downgrading from XT1069 MM 6.0 SOAK test Firmware to 4.4.4 and OTA update to 5.0.2 leaving it to "QualComm Emergency Download Mode" a.k.a Qualcomm Hs Usb Qdloader 9008 . For past several days I was experimenting with Blank-Flash Method available for Moto G (1st gen only). I am a full Linux/Ubuntu Guy. What I have found is that there are two files to construct, Programmer.mbn and Singleimage.bin for XT1068.
I am experimenting with possible replacement of SBL1 in Programmer.mbn and tz, rpm, DDR,and SBL1 partitions found in the singleimage.bin. But what I don't know as my device is hard-bricked is the full partition layout.
Is there anybody (rooted) willing enough to give the following info+dump of partition layout for XT1068 variant then I can try to integrate it those two files.
What you need to do is simple enough, just follow the instructions:
Requirements: Rooted XT1068
App: Partitions Backup & Restore
Instructions:
Start the app with root permission.
Backup All the partitions except SYSTEM (If you have enough space)
Upload the partitions to somewhere (If possible try Mega or Google Drive for faster speed)
Provide Screenshots of the partitions from that app screen.
You can also create 100mb of partitions dump. Click on the options in the app and click "Backup first partitions".
Please mention which Firmware you are using for instance 4.4.4 or 5.0.2 or 6.0, If possible give a Screenshot of Settings >> "About device".
If you know how to use adb then please provide the partition info, follow this wonderful instructions from this XDA thread [GUIDE] Making Dump Files Out of Android Device Partitions. Provide Screenshots like this post and if possible you can also provide me the dump data.
PS:
## I know the programmer.mbn and singleimage.bin is checksum protected, I will try to look into that later.
## Its quite impossible to accomplish what I am trying to do to help me and so many of other left there device as a paper weight, but you will never know if you don't try.
## Please don't raise your hope yet and please comment only technical info if you wanna help, so that moderator won't close this thread.
## This is my first post, so If I break any posting rules, forum moderator please let me know and If it is on wrong forum then move this thread to the right one.
I am looking forward to your help. Thanks in advance.
[Reserved]
I will post my findings related to blank-flash in future here.
UPDATE: 1
Creating singleimage.bin is easy enough. Its basically a gtp partition disk image with four patitions - Aboot, DDR, tz and rpm. If you have linux(ubuntu/Centos) editing this partition to include Aboot(emmc_appsboot), tz and rpm from OTA(4.4.4/5.0.2/6.0) update of Moto G 2014 is easy enough using gdisk tools in linux. I have already created that but the problem is that qboot utility doesn't pass to send singleimage.bin to phone. If anyone want I will give a full guide to create singleimage.bin.
Problem: The main problem is creating the programmer.mbn file. Recreating it is quite impossible if we don't get it from leak. I guess the existing programmer.mbn from Moto G (1st gen) is that it possibly check for bootloader, device id etc. There are a lot of posts about these topics in XDA, If anyone interested just search for the keywords singleimage.bin, mprg8226, Sahara protocol, PBL, Qualcomm qDloader 9008 commands etc.
Status:
with all the informations I gathered this week is that the unbricking a Hard-Brick Qualcomm device process is like follows:
flasher send the Flash Programmer (file) to phone in 9008 mode.
send signal to restart(possibly) phone and execute Flash Programmer (programmer.mbn in our case). It is a bootloader for rescuing phone to flash gpt partion containing second bootloader SBL1 and fastboot in aboot partition.
If you want to see what exactly is sent to your phone and the response the moto g gives after using qboot, use this command to execute qboot:
In Windows (Edit blank-flash.bat )
qboot.exe --debug=2 blank-flash
pause
In Ubuntu (from terminal)
./qboot --debug=2 blank-flash
you will see in the verbose debug output that phone stuck at executing programmer.mbn before accepting singleimage.bin.
Linux guy here too.
So, roughly you want to know every partition's size and content to make a new partition table? Dumping every partition with adb should be relatively easy. I'd like to help you, but I'm on Minimal OS 5.1.1, XT1063, with Lollipop bootloader. I don't know if the hardbrick problem is only related to XT1068 phones though, as I tried before to downgrade to kitkat's bootloader and nothing happened.
[HELP] Need Partition Layout Info+Dump of XT1068 for re-creating blank-flash
Hello
I have a blocked xt1068. And I want to participate, I start working with Qualcomm QPST.
I'm missing some information for a used wisely.
I am French. sorry for bad English.
DepressedDead said:
Linux guy here too.
So, roughly you want to know every partition's size and content to make a new partition table? Dumping every partition with adb should be relatively easy. I'd like to help you, but I'm on Minimal OS 5.1.1, XT1063, with Lollipop bootloader. I don't know if the hardbrick problem is only related to XT1068 phones though, as I tried before to downgrade to kitkat's bootloader and nothing happened.
Click to expand...
Click to collapse
hardbrick problem is not related to XT1068. It happened for Moto G(1st gen also) also for downgrading from Lolliop => Kitkat or MM => Kitkat then OTA update to Lollipop. I looked at the OTA, contains bootloader update and gpt partition. maybe updating a bootloader through OTA from a downgrade caused the problem though sounds silly.
previously I flashed XT1063 Lollipop SOAK test to my XT1068 and it worked like charm, though I didn't flash the bootloader. SO, I think it wouldn't be much problem to use XT1063's partition layout. I guess they wouldn't be much different.
If you have time please provide me your partition info + dump. At least I would get some idea about the gpt partition map
Finger Slensh said:
Hello
I have a blocked xt1068. And I want to participate, I start working with Qualcomm QPST.
I'm missing some information for a used wisely.
I am French. sorry for bad English.
Click to expand...
Click to collapse
QPST won't work I guess. LG, ONEPLUS, HTC have same mechanism but motorolla have different implementation of Qualcomm emergency download mode. Read these links are useful.
http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload/
and
http://www.androidbrick.com/unbrick-all-qualcomm-snapdragons-from-qualcomm-hs-usb-qdloader-9008-if-you-have-the-right-kind-of-rom-qhsusb_dload/
@kernelpanic.bd
There's some info about the partitions. I'll upload 34 (out of 39) images of almost every partition in a few hours, or maybe minutes. Except for recovery, userdata, system, boot, and cache. Ya' know, they're pretty useless since there are already images of those partitions, although if you want I could upload them (it would take me an eternity), or you could ask to someone else with better bandwith to dd those partitions since they're pretty large (500mb+).
Please hold on.
[EDIT]
What I've backed up: abootBackup, aboot, cid, clogo, ddr, deviceinfo, dhob, fsc, fsg, ftmlog, hob, kpan, logo, logs, misc, modem, modemst1, modemst2, padA, padB, pds, persist, rmp, rpmBackup, sbl1, sdi, sdiBackup, sp, ssd, tz, tzBackup, utags, utagsBackup, mmcblk0rpmb (this one isn't shown in parted).
What I didn't back up: boot, cache, recovery, system, userdata
Here's the link.
Please note that even if the .tar.gz is only around 25mb it'll be 130mb once you extract it. I've added detailed outputs in .txt files and a checksums.md5 file, so don't forget md5sum -c checksums.md5 to check all the files. As I don't know which extension should be used for every partition I left them all without extension, which I don't think that could be a big deal. If it is, then I'll be using FlashFire (I didn't use it because it only shows 20 partitions, when really there are more than 39 in our device).
If there's any corrupted dd'ed file please tell me.
More info: XT1063, Minimal OS 5.1.1, Lollipop bootloader.
DepressedDead said:
@kernelpanic.bd
There's some info about the partitions. I'll upload 34 (out of 39) images of almost every partition in a few hours, or maybe minutes. Except for recovery, userdata, system, boot, and cache. Ya' know, they're pretty useless since there are already images of those partitions, although if you want I could upload them (it would take me an eternity), or you could ask to someone else with better bandwith to dd those partitions since they're pretty large (500mb+).
Please hold on.
[EDIT]
What I've backed up: abootBackup, aboot, cid, clogo, ddr, deviceinfo, dhob, fsc, fsg, ftmlog, hob, kpan, logo, logs, misc, modem, modemst1, modemst2, padA, padB, pds, persist, rmp, rpmBackup, sbl1, sdi, sdiBackup, sp, ssd, tz, tzBackup, utags, utagsBackup, mmcblk0rpmb (this one isn't shown in parted).
What I didn't back up: boot, cache, recovery, system, userdata
Here's the link.
Please note that even if the .tar.gz is only around 25mb it'll be 130mb once you extract it. I've added detailed outputs in .txt files and a checksums.md5 file, so don't forget md5sum -c checksums.md5 to check all the files. As I don't know which extension should be used for every partition I left them all without extension, which I don't think that could be a big deal. If it is, then I'll be using FlashFire (I didn't use it because it only shows 20 partitions, when really there are more than 39 in our device).
If there's any corrupted dd'ed file please tell me.
More info: XT1063, Minimal OS 5.1.1, Lollipop bootloader.
Click to expand...
Click to collapse
You completely rock . Yes, I don't need cache, recovery, system, userdata but if possible please upload boot.img, motoboot.img and gpt.bin of the firmware you flashed and using now.
bro issue the parted command on mmcblk0
parted /dev/block/mmcblk0
then in the parted menu write "p" to print partition layout with size info and gimme an screenshot of that or the output in a text file. I will possibly update my post with my theory and screenshots of my findings maybe tomorrow or the next day. Thanks again, much appreciated.
If you guys get this right and fix all these bricked xt1068 phones I'll give you a million thanks here !!
@kernelpanic.bd
I used this to update my bootloader, then flashed again the whole stock 4.4.4 rom because there was no mobile signal. What's strange is that it didn't let me downgrade the bootloader and there was a warning about mismatched partitions (idk), but the bootloader was indeed updated.
https://mega.nz/#F!wtlQGQoK!bOrNQEpvYzIKmB68V3qPEg!58tSmQyI
boot (KK), motoboot (KK), gpt.bin (KK) from my stock 4.4.4 carrier rom used to recover mobile signal + current dde'ed boot image.
https://mega.nz/#!y9xCWYgL!6d8biMw1OXOjJqr-wyEgUI2P2grYJiEJX7rnx2bYEFY
Thanks. Downgrading to 4.4.4 doesn't create any issue. If you then upgrade to 5.0.2 through ota that's cause the hradbrick. Mine was fine flashing 4.4.4 from 6.0 xt1069 SOAK test fw. But when I update from 4.4.4 to 5.0.2 ota through the default recovery, it was hard bricked.I guess the bootloader and gpt.bin in the 5.0.2 OTA causes this issue.
kernelpanic.bd said:
Thanks. Downgrading to 4.4.4 doesn't create any issue. If you then upgrade to 5.0.2 through ota that's cause the hradbrick. Mine was fine flashing 4.4.4 from 6.0 xt1069 SOAK test fw. But when I update from 4.4.4 to 5.0.2 ota through the default recovery, it was hard bricked.I guess the bootloader and gpt.bin in the 5.0.2 OTA causes this issue.
Click to expand...
Click to collapse
I concur completely.. That's exactly what happen to my phone too.
same
garyben60 said:
I concur completely.. That's exactly what happen to my phone too.
Click to expand...
Click to collapse
I'm in the same case
I found files here ....but they are moto g 2013
https://mega.nz/#!rgoSGS7B!d2LKiBm29aSSy9dYxy-4aQutjcA5Vwy6bcAE9Sh3nLY https://mega.nz/#!rgoSGS7B!d2LKiBm29aSSy9dYxy-4aQutjcA5Vwy6bcAE9Sh3nLY
updated my findings in the second post.
kernelpanic.bd said:
updated my findings in the second post.
Click to expand...
Click to collapse
.. Sorry I saw one update on #2. Is there anything further? I Wish I knew more about this so I could also help
when you guys solve the problem . can tell me ? My gmail- [email protected] thank you...
no solution......
We still waiting :crying::crying::crying:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
kernelpanic.bd said:
updated my findings in the second post.
Click to expand...
Click to collapse
plz check out this link bro.. is it working for xt1068 or not..?
and jst wanted to know that are u still working for the blankflash or started waiting for a superman to come with a solution jst like us
c_/\/\_k said:
plz check out this link bro.. is it working for xt1068 or not..?
and jst wanted to know that are u still working for the blankflash or started waiting for a superman to come with a solution jst like us
Click to expand...
Click to collapse
Not working for my moto g.
Good luck guys.
I hope they get a solution, my case was that too, to soak 6.0 4.4.4 downgrade.
When booting TWRP using fastboot, without flashing it to the recovery partition, eg. "fastboot boot twrp-sanders-r20.img", only for the purpose of taking a partition backup, once done the device wont longer take OTA's!
That is IMHO a very unexpected behavior, as booting this way and keeping system read only should mean that nothing on the phone gets changed (well except the data partition if a backup is saved on these one).
One would expect this not to mess with the OTA process.
Now, this twrp at least: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910 does, after some investigation i found out that it is mounting the oem partition writable and modifying it adding a .twrp file to the root. Since the OTAs are checking and patching this partition of cause they will fail.
Luckily there is a way out, you can reflash the OEM partition for example from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
that is assuming that you are running the first Oreo 8.1 update, if you had an other version when the issue hit, you will need to find the right OEM partition image for you actual build.
IMHO this behavior of TWRP is unacceptable and should be fixed in a new release ASAP.
DavidXanatos said:
When booting TWRP using fastboot, without flashing it to the recovery partition, eg. "fastboot boot twrp-sanders-r20.img", only for the purpose of taking a partition backup, once done the device wont longer take OTA's!
That is IMHO a very unexpected behavior, as booting this way and keeping system read only should mean that nothing on the phone gets changed (well except the data partition if a backup is saved on these one).
One would expect this not to mess with the OTA process.
Now, this twrp at least: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910 does, after some investigation i found out that it is mounting the oem partition writable and modifying it adding a .twrp file to the root. Since the OTAs are checking and patching this partition of cause they will fail.
Luckily there is a way out, you can reflash the OEM partition for example from here: https://forum.xda-developers.com/moto-g5s-plus/how-to/tutorial-fhash-oreo-8-1-stock-global-t3852967
that is assuming that you are running the first Oreo 8.1 update, if you had an other version when the issue hit, you will need to find the right OEM partition image for you actual build.
IMHO this behavior of TWRP is unacceptable and should be fixed in a new release ASAP.
Click to expand...
Click to collapse
Agreed; received today a security update for my moto G5S plus (didn't root till i got the official 8.1 Oreo update) and every time i try to install takes me to TWRP and i keep it as READ ONLY (since TWRP itself says if u modify u won't b able to receive OTA updates) and... even without the modification i still can't get the update. this has to be fixed ASAP by TWRP
I did discover that if you keep the OTA files for older updates, you can re-run them to update the OEM partition. Unfortunately it only works one update generation.
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
pizzaboy192 said:
I did discover that if you keep the OTA files for older updates, you can re-run them to update the OEM partition. Unfortunately it only works one update generation.
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
Click to expand...
Click to collapse
keep us posted man
pizzaboy192 said:
I wonder if we just delete the .TWRP file if it can recover it. I'll test later this week. The OTA has a way to repair partitions
Click to expand...
Click to collapse
imho 99% sure, it still will fail, the partition does not just have to be semantically unchanged it must be 1:1 bit wise identical with what is expected.
I'll see what happens. I'm not a developer but I have pointed this out a few times to the developers of both TWRP threads, along with sharing these issues on the telegram group, but everyone else is focused on the latest custom ROM and doesn't care about stock, so the issues have fallen on deaf ears
in a nutshell how can i receive the last OTA security? do i revert to stock , install then root again? holy moly that's a lot of work
TheKicKer69 said:
in a nutshell how can i receive the last OTA security? do i revert to stock , install then root again? holy moly that's a lot of work
Click to expand...
Click to collapse
Unfortunately until they fix TWRP so it doesn't damage the OEM partition, you need a clean copy of the OEM partition to take the OTA.
However, there is a way you can prevent this, but it is a little hairy (you can't use any magisk modules). You can use the magisk app to patch the boot.img file that is from a slightly older Oreo firmware and flash that with fastboot, without using TWRP.
---------- Post added at 07:35 AM ---------- Previous post was at 07:30 AM ----------
DavidXanatos said:
imho 99% sure, it still will fail, the partition does not just have to be semantically unchanged it must be 1:1 bit wise identical with what is expected.
Click to expand...
Click to collapse
Yup. Just confirmed that deleting the .twrp file does not fix it.
I've reached out to Motorola to update their Lenovo Motorola Smart Assistant tool to support the official Oreo OTA which will allow us to download the latest full firmware file, which would give us the OEM partition to reflash before the next OTA.
I'll bother the TWRP devs again this week to get this unexpected behavior removed so we don't need to bother anyone in the future.
Update: none of the TWRP maintainers currently have replied to me about this issue.
@CheckYourScreen hasn't been active for a while but hasn't responded to a few different attempts to point this issue out (Been over a month since first notification with no acknowledgement)
@MasterAwesome has a custom TWRP that is latest, but they're still working on it. They're our best bet to possibly get it fixed since they're actively working on it. They've also been made aware, but no response yet (4 days since notifying and it was a weekend, so hopeful)
@GeneticEnginer was notified today. They developed the first unofficial TWRP (3.1.1) and might be able to help, but not holding my breath
I've also contacted a few people who do unofficial TWRP ports for some tips on unpacking one of our existing TWRP files and fixing it myself. It may be the way to go.
Hi guys. Final update. I've fixed TWRP temporarily. If we're not going to run custom ROMs, use this TWRP to backup. It does a bitwise backup of OEM and doesn't mount it as RW so it WILL work for restoring fully OTA capable stock ROM. It is NOT treble compatible as the treble compatible ones do weird things that I haven't documented.
https://forum.xda-developers.com/mo...-r20-stock-t3869192/post78205758#post78205758
So I have a Moto E5 Plus (hannah) XT1924-8
and I'm in a jam.
I'm new to moto phones I just moved over to this phone 4 days ago from my HTC M9 yeah I have been a HTC guy for a long time.
My stock rom is fubar, when it boots up I get that encrypt storage thing & reset phone etc.... (no password box) but reset phone is not fixing it.
The boot loader is unlocked
& my twrp is on twrp-3.2.3-0-hannah.img got it from twrp.me
So my problem is that I want to re-flash my stock rom but "Lenovo Moto Smart Assistant" witch did worked 4 times this week but now does not want to work anymore.
It comes back at me with "this device is not supported" & that is not true.
So Now I can't get back to stock & I have not been able to get any custom rom to work me as well.
So my ?s to all of you:
Is there some kind of fix for the "Lenovo Moto Smart Assistant"?
and if not then where do I get a copy of the stock rom & some info on how I should go about installing it
and yes I have the newest adb all installed & I think I have the right driver installed "Motorola_Mobile_Drivers_64bit_v6.4.0.msi" Motorola ADB Interface 7/7/2013 v2.0.2.0
Any help will be much appreciated
Also is the phone default encryption getting in the way of me installing Lineage 15.1 or Bootleggers ??
When ever I try to installing a custom rom I get the dreaded 'To Start Android, Enter Password'
also in twrp /data does not mount when ever I booted into twrp, I had to change the format from ext4 to exfat & then change it back to ext4, from that point on it mounts no problem.
My HTC m9 phone did not have encryption on so I'm not use to working around it.
Well I'm going to return this thing & stay with my HTC m9 with only a 10% working battery.
It seems that no one is going to help me.??
there might be reasons why people wouldn't respond
1. this board isn't active like you'd expect it to be
2. there's already threads out there to save yourself from this
anyway, on twrp, you'd need to FORMAT data to have it de-encrypted... and you'd need to flash a certain boot image that prevents it from auto-encrypting, which is in one of the threads. you'd also never would want to use the smart assistant, because as you can see, it won't work. i don't know if there's a stock rom for your variant, so i can't really link you to yours, but getting it from the moto assistant isn't ideal, it's better to get it from here on the forums or something.
so, in order to install a custom rom, flash the boot.img that doesn't have encrypt, and then flash the gsi system image, and then flash magisk in twrp.
There should already be a thread with the xt1924-8 stock firmware in here somewhere just gotta search. If not I'd suggest trying to re-flash the stock recovery and boot images if you have those and then just try to do a recovery from within.
well I already returned it.
I did read many many many guides on here & on other websites before asking for help.
most of them did not say anything about the book.img to turn off the auto-encrypting.
again I never had to work around auto-encrypt before.
Also @wihzard
I did look for a stock rom for (hannah) XT1924-8 but did not find it.
anyways I returned it & now I'm looking for a unused M9 to replace my old one,
I will end up putting LineageOS 16.0 on it.
Thanks for replying
my moto e5 plus is bricked im pretty sure ...any help anyone?
E-TARD_The_LifeCaster said:
well I already returned it.
I did read many many many guides on here & on other websites before asking for help.
most of them did not say anything about the book.img to turn off the auto-encrypting.
again I never had to work around auto-encrypt before.
Also @wihzard
I did look for a stock rom for (hannah) XT1924-8 but did not find it.
anyways I returned it & now I'm looking for a unused M9 to replace my old one,
I will end up putting LineageOS 16.0 on it.
Thanks for replying
Click to expand...
Click to collapse
………………………………………….
I need help as well haven't had much time to get on here and try to get help. I have the XT1924-7 varriant. I had discovered a hidden network that was placed on there by an ex to track me. So I factory reset I had AEX pie installed on it. Come to find out factory reset didn't even get ride of had to follow some extra steps to erase partitions that weren't wiped during the reset with TWRP. So my problem is once booted and going through setup process these pop up start popping up(screen shots below)the first is the modem keeps stopping. I get that about 25 times of hitting ok then I get one last one stating internal error need to factory reset. IVE DONE THAT COMPLETELY DELETED IT ALL RESTORED ALL. I've flashed NON-HLOS alone withe the erase modem 1&2. And still I've done diffent methods of trying to restore and get nowhere. Any help would be appreciated
Hey folks. I got a new Moto G7 Plus (XT1965-T) and wanted to install TWRP and custom ROM, as done on my G5 Plus. Long story short... I accidentally flashed a recovery image for my G5 Plus, and hard-bricked the phone. I managed to unbrick, thanks to luiz_neto's "[ULTIMATE GUIDE] How To Unbrick your Moto G7 Plus" post (BIG shout out). However, when in drop to Recovery Mode, TWRP v3.2.1-0 as was installed on the G5+, is displayed. The screen then locks up requiring a hard reset. I can boot to the Factory ROM and the phone functions normally, however am unable to figure out how to reinstall the OEM recovery. All procedures to revert back to full OEM seem to reference flashing a factory "Image". I can only find .zip files on the stock ROM. Any clues out there as to how I can fix this problem would be greatly appreciated?
My recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
jwoegerbauer said:
and incompleteMy recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
My thoughts too, but stock ROMS are in xml.zip fromat, and I have no idea how to install. Some guidance indicates that extracted files are manually flashed in sequence. This seems odd and instructions are incomplete. Where can the stock ROM, what will be the format, and where can I find accurate and complete instructions?
I previously had a Motorola G7 Power device and I know that's not the same device you have here but I do recall our factory images were on a server and you had to really be careful which one you installed. There were six or seven different Moto G7 power device models and that many stock rom/ images. I can help you look and try and see if there is anything out there.
What is the exact model of your device or just post a screenshot of your "about phone" in settings if you'd like.... Please tell me your build number in phone settings when you get a minute I'm trying to figure out exactly what model device you have. Sometimes Motorola can be kinda tricky.
I'm not saying these links are to firmware that is made for your device. I need to know exactly what model you have to determine that but you may want to check out these:
Sidenote: I had a Moto that had the same exact XTxxxx number as another model is why I want to be for sure about this .
[Flash ROM.bat][Android 9] Flash Stock ROM of your MOTO G7 PLUS!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus. Just put it in the stock Rom folder along with the fastboot files and run the file. For those who...
forum.xda-developers.com
If there is anything out there I, like others here have already commented would suggest flashing the factory image /stock rom, whatever you want to call it that's made for your device and also at some point formatting data. fastboot -w
flash713 said:
I previously had a Motorola G7 Power device and I know that's not the same device you have here but I do recall our factory images were on a server and you had to really be careful which one you installed. There were six or seven different Moto G7 power device models and that many stock rom/ images. I can help you look and try and see if there is anything out there.
What is the exact model of your device or just post a screenshot of your "about phone" in settings if you'd like.... Please tell me your build number in phone settings when you get a minute I'm trying to figure out exactly what model device you have. Sometimes Motorola can be kinda tricky.
I'm not saying these links are to firmware that is made for your device. I need to know exactly what model you have to determine that but you may want to check out these:
Sidenote: I had a Moto that had the same exact XTxxxx number as another model is why I want to be for sure about this .
[Flash ROM.bat][Android 9] Flash Stock ROM of your MOTO G7 PLUS!!!
FOR MOTO G7 PLUS ONLY!!! Hello, everyone. I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus. Just put it in the stock Rom folder along with the fastboot files and run the file. For those who...
forum.xda-developers.com
If there is anything out there I, like others here have already commented would suggest flashing the factory image /stock rom, whatever you want to call it that's made for your device and also at some point formatting data. fastboot -w
Click to expand...
Click to collapse
Device is a Moto G7 Plus model: XT1965-T. It is/was Android 10. I thought I had a good stock rom and flash procedure, but following a latenight attempt, I was obviously wrong. I am now stuck in a boot-loop. I can still get to fastboot and it is recognized adb tools., but that is it. Step one, get the build number before 'zucking' with it. Blew that! Would understand if you walked. Anyway, if your still here, I think the ROM is correct, Motorola_Moto_G7_Plus_XT1965-T_RETUS_LAKE_QPWS30.61-21-18-7-3_10.zip from motostockrom.com. If so, I obviously have no idea how to flash using adb tools and fastboot. Also, I see ROMs ending in .xml.zip, vice .zip. Just packaging? Where to from here? Frame it and find a wall? I'll hold off a couple of days before zucking with it some more. I have a septic tank lid to fix. Way more fun and greater chance of success!
cliffgi said:
Device is a Moto G7 Plus model: XT1965-T. It is/was Android 10. I thought I had a good stock rom and flash procedure, but following a latenight attempt, I was obviously wrong. I am now stuck in a boot-loop. I can still get to fastboot and it is recognized adb tools., but that is it. Step one, get the build number before 'zucking' with it. Blew that! Would understand if you walked. Anyway, if your still here, I think the ROM is correct, Motorola_Moto_G7_Plus_XT1965-T_RETUS_LAKE_QPWS30.61-21-18-7-3_10.zip from motostockrom.com. If so, I obviously have no idea how to flash using adb tools and fastboot. Also, I see ROMs ending in .xml.zip, vice .zip. Just packaging? Where to from here? Frame it and find a wall? I'll hold off a couple of days before zucking with it some more. I have a septic tank lid to fix. Way more fun and greater chance of success!
Click to expand...
Click to collapse
RETUS is retail US model device. On my G7 Power there were multiple firmwares that could be used. Idk if this is it but check out "RETAIL" from here: https://mirrors.lolinet.com/firmware/motorola/lake/official/RETAIL/
I didn't see a RETUS firmware. G7 Plus is codename "LAKE" correct ?
Yes. Aaccording to multiple references, LAKE is the codename for the XT1965-T. My OEM box clearly states XT1965-T. It is an unbranded unlocked, full price phone, new out of the box. When I search for "stock ROM", I only find _LAKE_ along with the words "_RETAIL_" or "_RETUS_" in the zip name. Not certain of that though.
cliffgi said:
Yes. Aaccording to multiple references, LAKE is the codename for the XT1965-T. My OEM box clearly states XT1965-T. It is an unbranded unlocked, full price phone, new out of the box. When I search for "stock ROM", I only find _LAKE_ along with the words "_RETAIL_" or "_RETUS_" in the zip name. Not certain of that though.
Click to expand...
Click to collapse
I think RETUS means Retail US. Again, just wagging.
cliffgi said:
I think RETUS means Retail US. Again, just wagging.
Click to expand...
Click to collapse
Maybe check the RETAIL firmware on Lake device section and see if you can find anything that resembles the firmware that you are currently on. Look at dates of the firmware packages. Download a few and unpack them and look inside. That's what I would do. When I look up your model it shows two models .. The T-Mobile Moto G7 Plus and the Unlocked G7 Plus. I'd scope out the contence of the RETAIL firmware and see what all is inside once unpacked.. You should be able to tell by that if the retail is indeed RETUS which is yes retail US.
Where the RIVER firmware is at the link I pasted here in the thread , if you scroll down there is a telegram group link: https://t.me/lolinet
Maybe someone there knows more about all this. Worth a shot.
One last thing, inside the firmware, once it's unpacked I believe there is a script for flashing it. Open it to see order of partitions flashed.. If you do NOT already have a backup of your IMEI you should most definitely back them up as soon as you are able to. Then if you end up with no signal and your IMEI disappears you can fastboot the backed up files and your good. If not and you lose them, you're SOL and you have a paperweight. i remember on my G7 Power I messed mine up and luckily had a backup of them or I would have been screwed.
Once you get up and running again to copy your efs you can use termux terminal or another terminal emulator app and type: su then grant root once it pops up on your phone screen. Them type these two lines, one at a time and it will backup your efs to your sdcard and you can transfer them to your PC, a cloud or USB drive where they're safe.
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048 (then push enter)
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048 (enter)
Edit added: This guy knows about Motorola. His thread(s) may be helpful https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/
cliffgi said:
I think RETUS means Retail US. Again, just wagging.
Click to expand...
Click to collapse
flash713 said:
Maybe check the RETAIL firmware on Lake device section and see if you can find anything that resembles the firmware that you are currently on. Look at dates of the firmware packages. Download a few and unpack them and look inside. That's what I would do. When I look up your model it shows two models .. The T-Mobile Moto G7 Plus and the Unlocked G7 Plus. I'd scope out the contence of the RETAIL firmware and see what all is inside once unpacked.. You should be able to tell by that if the retail is indeed RETUS which is yes retail US.
Where the RIVER firmware is at the link I pasted here in the thread , if you scroll down there is a telegram group link: https://t.me/lolinet
Maybe someone there knows more about all this. Worth a shot.
One last thing, inside the firmware, once it's unpacked I believe there is a script for flashing it. Open it to see order of partitions flashed.. If you do NOT already have a backup of your IMEI you should most definitely back them up as soon as you are able to. Then if you end up with no signal and your IMEI disappears you can fastboot the backed up files and your good. If not and you lose them, you're SOL and you have a paperweight. i remember on my G7 Power I messed mine up and luckily had a backup of them or I would have been screwed.
Once you get up and running again to copy your efs you can use termux terminal or another terminal emulator app and type: su then grant root once it pops up on your phone screen. Them type these two lines, one at a time and it will backup your efs to your sdcard and you can transfer them to your PC, a cloud or USB drive where they're safe.
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048 (then push enter)
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048 (enter)
Edit added: This guy knows about Motorola. His thread(s) may be helpful https://forum.xda-developers.com/t/guide-using-fastboot-exe-with-motorola-devices.4042039/
Click to expand...
Click to collapse
A BIG THANKS FOR ALL THE HELP.
Did what you suggested. Extracted and located a "Flashfile.bat"... runs a long list of fastboot cmds, as I'm sure you are familiar. Similar to but more involved than the mannual I ran last night(did not work, broke to boot-loop. Also located a file called LAKE_QPWS30.61-21-18-7-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt Contents are as follows:
BUILD REQUEST INFO:
SW Version: lake-user 10 QPWS30.61-21-18-7-3 284d4d release-keysM636_21.71.02.66R
Modem Version: M636_21.71.02.66R
FSG Version: FSG-660-10.108
MBM Version: MBM-3.0-lake_retail-efaf0cccb-210129
Build Fingerprint: motorola/lake/lake:10/QPWS30.61-21-18-7-3/284d4d:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 30.201.3.lake.retail.en.US
Model Number: moto g(7) plus
Android Version: 10
Build Id: QPWS30.61-21-18-7-3
SW Display Build ID: QPWS30.61-21-18-7-3
Build Date: Fri Jan 29 08:46:03 CST 2021
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
eLabel SHA1: da39a3ee5e6b4b0d3255bfef95601890afd80709
Blur Version: Blur_Version.30.201.3.lake.retail.en.US
Version when read from CPV: lake-user 10 QPWS30.61-21-18-7-3 284d4d release-keys
AB Update Enabled: True
Full Treble Enabled: True
Seems obvious that RETUS stand for Retail US, and all appears to be all correct for my device.
As for a the IMEI it is printed on the box. I have no softcopy.
Very familiar with dd. Excellent idea. Will do, as well as get a full TWRP backup, when get it running.
The unzipped ROM file creates directories: Driver, Firmware, and RSD Flash Tool, as well as credits.txt and How to Flash.txt. How to Flash.txt simply says to install drivers, I have already done; connect device which I know how to do (fastboot devices confirmation), and run the previously mentioned flashfile.bat from the Firmware directory.
Questions:
What It does not say is that this zip was designed for Windows, not Linux (as I ran last night). I also assume that it should be run as administrator. The Windows machine already has Adb Tools and Fastboot installed. I haven't really touched a Windows machine in ten years (TG), but from what I recall, unlike Linux/UNIX, the current working directory is automatically added to the search path. Is this stil the case for Win10 and will the current working directory be searched first, or is there a possibility that there might be a cmd/file version mismatch between the two installs? I have no idea what the directory of RSD Flash Tools is for. ? Any additional thought before I take the pill? A BIG THANKS FOR ALL THE HELP.
On Moto G7 power device the devs changed the firmware install commands and lefts out a few that they said weren't needed. Check out G7 power guides section of xda. There are fastboot guides there. Having a physical backup of your efs is important. It's not the same as just knowing your imei. The only way your imei can be restored is if you backup the efs partitions and if/when you have issues, (many do!) you can fastboot flash them back to your device.
I can't stand Windows. I'm a Linux guru and wish I would have discovered it sooner. I have a Asus Chromebook that I use now and i immediately installed crouton and Ubuntu same day it arrived from Amazon. ChromeOS is actually not bad but fact that its a MAJOR Target for malware and viruses is an issue for me. I'm quite sure the files are for windows. Things still usually are that way much of the time in my experience.. I hope you get it resolved and fixed. I came across more links earlier. I'll go grab them and add them to my post here after I post this. I actually found a G7 Plus fastboot firmware flash guide too. Idk if it's correct or not but lemme go get the links.
This may or may not be helpful. Careful what all you fastboot flash. These Moto devices, the G7, G7+, Power...They can be confusing as far as correct firmware. I also remember on G7 Power our stock firmware, not all of the stock rom partitions would flash.. Some would work for some people and not for others.. See this is a danger zone for the possibility of messing up your efs and losing IMEI.. If anything is flashed that doesn't belong it can screw that up and then you'd lose data and not be able to restore them to fix device.. That's why I mentioned it earlier..
The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy...
forum.xda-developers.com
The guide on that thread with the fastboot directions is how we flashed our firmware on G7 Power.
May want to read here: https://lineageosroms.com/lake/
The G7 Plus is codename LAKE. I keep thinking RIVER but RIVER is codename for the regular Moto G7 device.
Edit added:
Didn't you mention something about attempting to install recovery TWRP before you bricked? You can try flashing stock boot.img to both slots and reboot system and see if device boots up. Just open terminal and get a stock firmware boot.img from extracted firmware for LAKE device and in terminal and while phones in bootloader mode: sudo fastboot flash boot boot.img --slot all
That will get boot.img on both slot A&B and should fix anything you did with TWRP and boot partition,, if there is anything in your boot partition that's causing phone not to boot. Just make sure boot.img is from LAKE firmware.
When you connect to your PC and open terminal and do: adb reboot bootloader
And then : sudo fastboot getvar all
does anything appear to be not okay? Definitely check that out. I would if I were you. Good luck man. I had found a thread that had firmware fastboot directions. It was dated 19 months ago but "if" it was correct im quite sure it would still apply now . Good luck man.
Well tried to flash stock ROM and got error messages/failure. See attached screenshot.
jwoegerbauer said:
My recommendation: Re-flash Stock ROM to get rid off of all modifications you applied so far.
Click to expand...
Click to collapse
flash713 said:
On Moto G7 power device the devs changed the firmware install commands and lefts out a few that they said weren't needed. Check out G7 power guides section of xda. There are fastboot guides there. Having a physical backup of your efs is important. It's not the same as just knowing your imei. The only way your imei can be restored is if you backup the efs partitions and if/when you have issues, (many do!) you can fastboot flash them back to your device.
I can't stand Windows. I'm a Linux guru and wish I would have discovered it sooner. I have a Asus Chromebook that I use now and i immediately installed crouton and Ubuntu same day it arrived from Amazon. ChromeOS is actually not bad but fact that its a MAJOR Target for malware and viruses is an issue for me. I'm quite sure the files are for windows. Things still usually are that way much of the time in my experience.. I hope you get it resolved and fixed. I came across more links earlier. I'll go grab them and add them to my post here after I post this. I actually found a G7 Plus fastboot firmware flash guide too. Idk if it's correct or not but lemme go get the links.
This may or may not be helpful. Careful what all you fastboot flash. These Moto devices, the G7, G7+, Power...They can be confusing as far as correct firmware. I also remember on G7 Power our stock firmware, not all of the stock rom partitions would flash.. Some would work for some people and not for others.. See this is a danger zone for the possibility of messing up your efs and losing IMEI.. If anything is flashed that doesn't belong it can screw that up and then you'd lose data and not be able to restore them to fix device.. That's why I mentioned it earlier..
The Complete Noob Guide to Rooting MetroPCS XT1955-5 Qualcomm Variant
This tutorial is for people like me than ran into problems rooting the Moto G7 Power XT-1955-5 (MetroPCS Qualcomm Variant) running on stock Pie. I got two of these literally today brand new in the box after swapping out that mess Samsung Galaxy...
forum.xda-developers.com
The guide on that thread with the fastboot directions is how we flashed our firmware on G7 Power.
May want to read here: https://lineageosroms.com/lake/
The G7 Plus is codename LAKE. I keep thinking RIVER but RIVER is codename for the regular Moto G7 device.
Edit added:
Didn't you mention something about attempting to install recovery TWRP before you bricked? You can try flashing stock boot.img to both slots and reboot system and see if device boots up. Just open terminal and get a stock firmware boot.img from extracted firmware for LAKE device and in terminal and while phones in bootloader mode: sudo fastboot flash boot boot.img --slot all
That will get boot.img on both slot A&B and should fix anything you did with TWRP and boot partition,, if there is anything in your boot partition that's causing phone not to boot. Just make sure boot.img is from LAKE firmware.
When you connect to your PC and open terminal and do: adb reboot bootloader
And then : sudo fastboot getvar all
does anything appear to be not okay? Definitely check that out. I would if I were you. Good luck man. I had found a thread that had firmware fastboot directions. It was dated 19 months ago but "if" it was correct im quite sure it would still apply now . Good luck man.
Click to expand...
Click to collapse
Got it 100% fixed. Principle problems in recovery from this zuck-up were scoping the problem, locating the proper Stock ROM, figuring out fastboot, and lastly, identifying a defective adb fastboot install on the Windows 10 system I was using. Switched to my primary Linux system and life got a whole lot better.
MANY MANY THANKS to you ( flash713) for suffering through my stupidity without insult, and helped me ID the correct ROM and provide good links that helped me figure out what to do with it once I had it. Seriously, I could not have done without your help. For the Moto G7 Plus XT1965-T, the stock ROM is LAKE_RETAIL_10_QPWS30.61-21-18-7_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip. The image below was from my first attempt with the correct ROM. I discovered that ADB Tools and Fastboot install on my Windows10 system was corrupt. GO LINUX!!!
I use Lubuntu (a lightweight Ubuntu) on Chromebook. My regular laptop died so I use my CB all the time now. Linux most definitely #1 always imo!! Really glad you got it going!!