Database Develop

[GUIDE] Nexus 7 (2012) factory image w/root

I know a couple people asked for a guide and I didn't see anything concise had been posted (Mods feel free to remove if it's a duplicate.). Things are still a bit fresh, but this should be a short list of steps to perform the upgrade of your Nexus 7 (2012) WiFi to Lollipop.
As with other guides, I make no expressed or implied warranties - you break it, it's on you.
This is how I was able to get Lollipop working on my own Nexus 7 (2012). I was coming from a rooted factory image of 4.4.4.4 which was the previous most-recent factory image released by Google for this device. I like my device as bone stock as possible and wanted to upgrade and keep it that way.
I assume the following:
You know how to use both adb and fastboot and have already configured your system to use these utilities.
You have already performed an oem unlock on your device.
That out of the way, on to the guide...
It goes without saying, but I'll call it out anyway... Take a backup of your current device setup. Most likely this is within your custom recovery or TiBu. If your not familiar with how to do so, consult the help pages for those apps.
Download & unpack the requisite files
LRX21P factory image from Google.
CF-Auto-Root from Chainfire.
OPTIONAL Only if you're upgrading from a version of Android prior to the JWR66Y Android 4.3 factory image, download the KRT16S factory image from Google.
Start by rebooting your device to the bootloader.
Code:
$ adb reboot bootloader
OPTIONAL If you have ignored my assumption and haven't already done so, now would be the time to oem unlock the bootloader
Code:
$ fastboot oem unlock
Run the following commands to prep your device to install Android L. NOTE:This will erase your device
Code:
$ fastboot erase cache
$ fastboot erase recovery
$ fastboot erase system
$ fastboot erase userdata
OPTIONAL If you are upgrading from a version of Android prior to the 4.23 bootloader release which was originally released along with the Android 4.3 JWR66Y factory image, then you will need to upgrade the bootloader also. The bootloader included in the Android L factory image is not correct and will fail to install. Your best bet is to download the KRT16S factory image from Google and use the bootloader-grouper-4.23.img file from that factory image. Be sure whatever version of the bootloader-grouper-4.23.img file you use has the correct md5sum.
Code:
$ md5sum nakasi-krt16s/bootloader-grouper-4.23.img
df53028033c9eccf4fe5ba7bc198ce24 nakasi-krt16s/bootloader-grouper-4.23.img
$ fastboot erase boot
$ fastboot flash bootloader nakasi-krt16s/bootloader-grouper-4.23.img
Now, install the actual Android L system
Code:
$ fastboot -w update image-nakasi-lrx21p.zip
Your device will automatically reboot at this point and when it does, you will be running Android L (5.0) 100% stock and WITHOUT ROOT. This boot usually takes a very long time (~5-10 minutes) as it's performing the initial setup of the OS. When the device is back up fully, you will have to go through the setup steps as if it were a new device. Once that's done, proceed to the next step.
Now that Android L is freshly-installed, not only have you lost root, but you've also lost the Developer Options menu and the USB Debugging option contained therein. So, before we proceed, we need to enable Developer options & USB Debugging in the settings menu so that adb & fastboot will work recognize the device. Again, if you have any experience with running adb & fastboot, you will know how to do this. The process is exactly the same as with previous versions, so there should not be any surprises here.
Go to the Settings menu and scroll down to and tap on "About Tablet"
On the next screen tap on the "Build Number" field seven (7) times and you'll be presented with a message of "You're now a Developer!"
Hit the back "triangle" and go into the Developer Options menu and turn on USB Debugging.
Just be sure to accept the key on your device when you connect it to your computer.
Now, we can use adb to reboot the device so we can apply the CF-Auto-Root patches and SuperSU from the bootloader
Code:
$ adb reboot bootloader
Once in the bootloader you will need to apply the cf-auto-root. Use the following command.
Code:
$ fastboot boot image/CF-Auto-Root-grouper-nakasi-nexus7.img
NOTE: Windows users have reported that the file is in the same directory so just double-check the path to the file.
This will boot the device onto a custom kernel, install the kernel fix to allow root and also install the latest beta version of SuperSU (2.20) for Android L.
You will now end up with a device running Android L with root. I did not mention at any point about installing a custom recovery. These steps will remove a custom recovery, so if you want to install that, you will need to consult the instructions for your custom recovery of choice. I usually use the CM instructions for installing CWM as they're easy to find. This is not strictly necessary for root. Similarly, my main purpose for rooting was to use Titanium Backup. The current production version of TiBu doesn't support Android L, but the TiBu team has released a test version for L via their twitter feed. Here's a direct link or you can go to their twitter feed for more info...
Questions? Comments? Did I miss something? Let me know.
EDIT: Seems that the performance has really gone down over the past few days. Not really sure what the cause of the performance degradation is but it's quite severe. I noticed last night after having left it plugged in all night that the device wouldn't even turn on or took an inordinately long amount of time (many minutes) to wake from sleep. As it stands I attempted to play a game that's slightly intensive and after a short period of time the device got really hot and started really having performance issues to the point where it rebooted on it's own. Further, I noticed a number of things aren't working that probably should... Bluetooth & "Battery Saver" mode are the first two that come to mind.
Anyone else experiencing similar issues?

worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!

SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.

petenatas said:
SuperSU is there. It does not complain about the binary. But TitaniumBackup can't find SU...
EDIT: Found the solution for TB in another thread.
Click to expand...
Click to collapse
Would you mind pointing me to it?

If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!

jasoraso said:
worked for me, with 2 changes:
- I had to enable developer mode on my first boot into L before I could execute the command "adb reboot bootloader"
Click to expand...
Click to collapse
added
- on my Windows machine, I had unzipped the root zip file, so I executed the command this way: "fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img", leaving out the "image/"
Thanks for your guide!
Click to expand...
Click to collapse
Not sure about on Windows, but on Linux when I unzipped the root zip file, there was a directory layout as such...
Code:
cf-auto-root/
cf-auto-root/image/
cf-auto-root/image/CF-Auto-Root-grouper-nakasi-nexus7.img
cf-auto-root/root-linux.sh
cf-auto-root/root-mac.sh
cf-auto-root/root-windows.bat
cf-auto-root/tools/
cf-auto-root/tools/AdbWinApi.dll
cf-auto-root/tools/AdbWinUsbApi.dll
cf-auto-root/tools/fastboot-linux
cf-auto-root/tools/fastboot-mac
cf-auto-root/tools/fastboot-windows.exe
In any case, you were able to find it. Should be pretty obvious which file I'm referring to...

apocope said:
Would you mind pointing me to it?
Click to expand...
Click to collapse
Added a link in the paragraph at the end.

Yes!
I needed my root. (The stock kernel underclocks like crazy, making the tablet nearly unusable.)

Thanks for the guide brother. You are awesome
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know

A very very very very usefull guide!!!!
All working fine!!!!
Thanks!!!!!!!

pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
OMG corrupted bootloader AGAIN.
GOOGLE what's wrong with you???

Thanks for the guide! Works fantastically on my aging N7.
Short rundown video by me on YouTube here:

Does it wipe internal storage?

abobobilly said:
Thanks for the guide brother. You are awesome
Click to expand...
Click to collapse
:good:
I am now on a Rooted Android L tablet, thanks to the CF-Root 'boot.img' by Chainfire.
Click to expand...
Click to collapse
:good::good:
I have a question though. I wanted to ask ... this specific boot.img by chainfire seems to have automatically upgraded my SuperSU app to v2.20, so i didn't flash the 2.19 BETA. How did this happen? Any idea? (Did that CF-Root get updated after you made this guide?) i am curious to know
Click to expand...
Click to collapse
I made a mistake on the version number that I listed in my instructions. When I did my N7, I had originally just tried flashing SuperSU via the standard zip file method. The most recent version of SuperSU available in the SuperSU XDA thread is/was 2.19, so I just assumed that it was the same version being used in the CF-Auto-Root. But as you correctly point out, the process installs 2.20 not 2.19. I updated the version number in the guide. Thanks.

ToucherCD said:
Does it wipe internal storage?
Click to expand...
Click to collapse
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.

pyrostic said:
If you're like me and haven't updated your bootloader to 4.23 you will need to do so... sadly that which is included with the most recent files is corrupt (yes the files from google.) download the krt16s version and overwrite your bootloader-grouper-4.23.img file. Then from the command line like before type "fastboot flash bootloader bootloader-grouper-4.23.img" then "fastboot reboot-bootloader" and follow the directions above!
Enjoy!
Click to expand...
Click to collapse
Added a link to the KRT16S factory image which contains a proper bootloader-grouper-4.23.img file that you could use.

jetsaredim said:
Yes, unfortunately it does.
I wouldn't recommend trying to upgrade without wiping user data. There may be internal changes to the file system and layout that could make a Kit Kat install (4.4.X) incompatible with this. Best to save off your data and start from scratch.
Click to expand...
Click to collapse
Hi. Good job on the guide. Very detailed. That's good.
Thanks for the tip with booting CFautoroot img. I was wandering why superSU 2.16 was not working and was looking for modified karnel all morning.
BTW. I know it's not recommended, even my Tapatalk signature says it
but I didn't wipe user data while upgrading. See my post here with details.
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.

Can I just ask about the bootloader?
I'm seeing alot of users reporting there's an issue within the bootloader that is included on the LRX21P image for Grouper, I performed a clean flash yesterday and flashed the leaked image for grouper, I haven't had any single issue flashing all of the images, even bootloader that came from the lollipop image doesn't seem to cause an issue.
Btw, everyone's suggesting to flash the bootloader from JB & KK on this lollipop build, is there any impact on the performance of why's that recommended to flash the old bootloader?
And I didn't really expect this but lollipop made it worst to run on this device! Even if it's a 2012 device, why's that it can't handle lollipop smoothly? I can't even drop the status bar down at a rate of 60fps as promised by Google, can't even swipe the screen smoothly and it's freezing as hell! It feels like something's wrong with this build.
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?

JovieBrett said:
We can't always tell the reason that this is a very old device so that it performs really bad, how come that my 2011 device with a CM11 installed that is still functioning well and smoothly performing operations on just top of its single core 1Ghz and 512 megabytes of RAM? Rather than this quad core tegra device that is WAY MORE faster supposedly?
Click to expand...
Click to collapse
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.

Natakranta said:
Because Asus used chip silicon chips as requested by Google to bring the cost down. They degrade with time and slow down. My wife's 32GB Grouper is unusable in my standards (using Nexus 5 for list year and OnePlus One now), it lags as hell no matter what, F2FS or ext4, stock or custom ROM, it lags. I so much regret I didn't convince her to change it to N7 2013 last year, as she didn't feel the need to spend money...
I was so looking forward to N9, but not for the price they ask. 16GB is useless, so 32GB is the only option, but 489 EUR (=610 USD) they ask in Europe is way over what I'd spend on YouTube player (that's what she most uses it for) with, wait, wrong screen aspect to watch videos!
/rant
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
Click to expand...
Click to collapse
Yup, I all agree of what have you said. I tried ext4, f2fs etc etc, none of them improves the N7's performance or at least the stock one has the best performance and stability for me.
Heard alot of users blaiming about the tegra chip for this, they said that tegra chips are getting worst every year and if all of these are true, I have doubts about Nexus 9's performance since even the one of the famous 'Android Police' senior editors have found that there are unusual freezes and glitches from the device itself, idk if that happened on the latest build for N9.
The 2011 device I'm currently comparing to is an Xperia Mini, snapdragon chip with 1Ghz single core, 512MB of RAM, I'll look away from tegra based devices...
Btw, do you have an N7 2013? I'm planning to buy one this December to replace my 2011 device. Can I trust this 2013 model with snapdragon processor? I always trust these snapdragon based devices.

A new Start !!

Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not iirc <71.08 shouldn't be flashed onto 71.08 existing BL right or was it 71.10 ?? (idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all. Heard a few CM roms had BL packed into ROMs and the updte to 5.1.x + lower BL caused hardbrick, a.k.a bootloop + noTWRP with Fastboot lockedout ).
So here's my to-do list sorry to post this long but seems like this is start for me....Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & Nexus 6 information....
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - MultiROM working guide on 5.1.1 plus M latest release anyone, will try the official thread tho, any info on whre to start would be awesome !!
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful posts/threads that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!

Ashtrix said:
Hello fellas,
After a long time I've decided to be back on Nexus, can't enjoy without nexus phones, ZF2 developement is stagnant as ASUS is not releasing src, a great HW stuck by OEM limtations.
So I've got my N6 today, I've learnt a few things before like not downgrading bootloader, had a post saying which versions are safe and ones that are not(idk why will anyone want to downgrade unless they want OTAs based on Fi, root is superior to all). So here's my to-do list sorry to post this here but seems like this is start for me.Please correct me If I understood anthing wrong....as It's been a long time since I used a nexus (Maguro was my first nexus and things rapidly changed these days..)
1 - mFastboot for flashing
2 - OEM unlock check prior to unlock the phone (shipped with 5.1 LMY47D so I may need to do this before proceeding)
A few questions -
3 - Does NRT has mFastboot ? I have it in my computer tho.
4 - Can any one give me crash course for SuperSU + MultiROM with 5.1.1 (Need Xposed:silly, 6.x & a few Nexus 6 information, any useful links would do the job.
a- Like If I OEM unlock my n6 now and use 5.1.1 CM based it has pre-root right ? So I shouldn't bother with SuperSU BETA 2.6x right, next is the systemless root is because of M's warning messages ? why all this hassle of
**root** as of lately with L and M, Is it because of SELinux policies + M's changes with System related messages ?
b - Does MultiROM work on 5.1.1 plus M latest release ?
5- I should be good if I unlock the nexus and use an EX / Lean / Despair / Blu-Spark / or any kernels - these do have modified system so how about the M's warning msgs? are the custom ROMs on M are modded to avoid any nagging messages like that?
6- Please link me any useful links that are updated to reflect latest changes like SU or any old information that is essential !! thanks !!
Click to expand...
Click to collapse
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use

AlkaliV2 said:
1.) I don't think you need mFastboot. I think you just want standard fastboot with Nexus phones
2.) I'm not sure what this means, but just follow the beginner guide in the General section to unlock the device
2a.) Follow the advice in answer 2 for fastboot information as well
3.) NRT installs standard fastboot and adb into C:\Program Files(x86)\WugFresh Development\NRT\Data\ folder
4.) Can't do it, I don't use multi-rom.
5.) There are special instructions for installing custom kernels. Follow the directions mentioned within the threads
6.) This information will be available in the custom ROM or kernel threads you choose to use
Click to expand...
Click to collapse
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..

Ashtrix said:
Thanks,
Last time I had a nexus 6 just for a couple of days which I returned for various reasons, I had the firmware error upon flashing the imgs from 5.0.x to 5.1.1, after googling a bit I used that mFastboot, but wanna confirm it..
Click to expand...
Click to collapse
I'm pretty sure mFastboot is made directly for a Verizon variant, but since the Nexus 6 is unlocked and your Verizon SIM card dictates the network you are on, I would say stick with normal Fastboot for your flashing endeavors. Good luck and read twice, flash once :good:
Edit: Quick side note, love the avatar. Good choice.

Thankyou :highfive:
Just did an OEM unlock and wierdly after that, the bugdroid loading doesn't end at all. Did an factory img flash of 5.1.1 Shamu-LMY48Y and booted in less than a min Lol.
And yes the fastboot is working, wow things are definitely wierd with Shamu (volume normalization, mFastboot previous xperience, bootloader bricks...seems like Qcom fixed that after CM brickbug and no one can help the manual bricking) but I'm ok with all these , just love this device, massive, powerful and sexy looking piece
EDIT :
Well everything's going fine but this bugdroid loading doesn't seem to be fixed at all, after bootup 23Gb was there so I did a format and again stuck, this time around I tried using TWRP to flash (CM12.1)after doing fastboot commands - fastboot format userdata, cache. Now it says unable to flash on so&so data partition, So formatted from the OS and now MTP says generical heirarchial. I don't remember any device with that format...
EDIT 2 : Device won't boot with that bugdroid formatting the Data partition. Needs to be fastboot flashed else stuck there forever again same 23Gb bootissue if I do that & Using fastboot format userdata command it formats into the 64GB - 54Gb available space but with TWRP It fails to flash - the same error, can't flash on data parition. So repeat fastboot and it's a damn cycle. Will try to flash MM if it won't then. I may have to return again...OMG
EDIT 3 : http://forums.androidcentral.com/go...ys-formatting-data-yellow-text-any-ideas.html
http://forum.xda-developers.com/google-nexus-5/help/help-stuck-formatting-data-t2737793

EDIT : Tried MM and after 10 mins formatted succesfully now gotta try a ROM or any, hope its fine !!

Again the GH FS is back with MTP and doesn't flash at all with TWRP. If I go for a re-lock and it it fails to boot with formatting properly...then bam nothing but a bricked Nexus !!
TWRP did the format but the device is messed up, sliptscreen issue..
I'm going to return this, enough of the hassle had me messed up totally :crying:
Seems like 6P seems better than having all these issues. Or wait for the 2016 device...
EDIT : Sorry for the GH format seems like it's normal, but the flashing issue is too wierd..

I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.

scryan said:
I dont know what the **** a bugdroid is.... But just use fastboot to flash things. Post up console messages and we can help.
If you flash userdata.img, its for the 32 gig model... But you can use TWRP to expand the partition to give your space back.
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
Just read, its really really easy.
Click to expand...
Click to collapse
I know this issue, just a factory reset fixed this thing on my old N6 that I had for 2 days, but this takes too much of time to format....Just had TWRP do the job and flashed the Temasek but ALAS !! Splitscreen issue.

Moto g5s xt-1799-2 rr

Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint

dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?

irewer said:
Sorry for mb inappropriate question: Do you have a physical device? If you do, did you unlock and root it (cos i have some issues with that)?
Click to expand...
Click to collapse
Yes i do..
I unlocked bootloader and rooted

dmilz said:
Managed to succesfully port Ressurection Remix (7.1) to the Moto Green Pomelo (xt1799). Rom boots and all features work apart from Fingerprint reader.
Need help with fixing fingerprint
Click to expand...
Click to collapse
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.

sixtheninth said:
Have you figured the problem out yet? Is there any other known custom ROMs working on Pomelo? Also how did you do it? I don't see Montana in Downloads section for the ROM.
Click to expand...
Click to collapse
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2

dmilz said:
No, i didnt get the chance to figure it out as i broke my moto screen completely. There are no custom roms for the xt-1799-2, wish i had shared it. But if you are interested you can easily port the roms for any moto g5s over to your xt-1799-2
Click to expand...
Click to collapse
Yeah, I am very interested. I tried RR, LineageOS, Viper for other montanas, all crashed after boot back into bootloader. Also I'd be interested getting Oreo based ROMs. So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.

sixtheninth said:
So far I m stuck with chinese ZUI 3.1 which prevents me from flashing or installing Gapps.
Click to expand...
Click to collapse
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
sixtheninth said:
Also I'd be interested getting Oreo based ROMs.
Click to expand...
Click to collapse
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here

irewer said:
You can unclock (XT1799-2 may be 'secretly' unlocked already), root your device, flash custom TWRP (escpecially for Moto G5S XT1792/1794 and Green Pomelo XT1799-2) - and then you'll be able to install Open GApps via TWRP/root.
Also you can simply open special Lenovo App Store on your ZUI-based phone (look for it carefully!), install Google Store's apk from out there - and be enjoying with any GApps and other official apk's.
If you will flash bootloader version 07 (not 06 as you have on any available ZUI stock ROMs), you'll be able to flash distinct Oreo firmware (XT1792 for Brasil/India/EU) in straight way (thread 1; thread 2). BUT YOU'RE GOING TO LOSE NFC and SELFIE-CAMERA in cause of special drivers lack!!! And you will have no way for downgrading of firmware in cause higher version bootloader.
* also you would prefer to flash Moto G5s' stock Android 7.1.1 firmaware (XT1794) on your Green Pomelo (XT1799-2), using this manual.
** stock Green Pomelo's ZUI-based Android 7.1.1 firmware you can find here
Click to expand...
Click to collapse
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
Click to expand...
Click to collapse
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.

careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2

sixtheninth said:
Thanks a lot! I was unable to Flash Gapps 7.1 in TWRP due to incorrect architecture error. I see that Oreo original ROM will probably never arrive to this phone, so I'll stick to 7.1. What buzzes me the most is that there is no custom rom compatible with XT1799 without losing some of its extra functions. I wonder how hard it will be to port Lineage, RR or similar to enjoy. I've been always using custom roms and now I feel kinda left out
---------- Post added at 10:31 AM ---------- Previous post was at 10:23 AM ----------
Update, I just fastboot flashed the Firmware from the links provided, but managed to hard brick my phone!!!!!! ((( Don't know what to do now.
Click to expand...
Click to collapse
Hope this helps to unbrick
http://motog5szuirom.blogspot.com/2018/01/zui-31-for-moto-g5s-stock-rom.html

dmilz said:
careful with flashing other moto g5s model roms on the xt-1799-2, its different and so you might get a brick. The best you can do is port like i said. You can unlock bootloader by "fastboot oem flashing" if that doesnt work for you try "fastboot oem unlock". I will be back on the pomelo xt-1799-2 soon as i am planning to order another one. Infact you guys will need a section dedicated to the xt-1799-2
Click to expand...
Click to collapse
I agree, a since it is a slightly different phone a independent section can be great. Now, I am not a developer, so things like porting ROMs is not in my skillset, but I understand that selfie cam and nfc will not work on any custom ROM even if ported simply due to driver issue. I have rooted my phone previously, so I was past unlocking. Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode, which was strange as it had stock ROM updated by reseller into a global version. Then I tried to flash various custom ROMs without any luck. Pretty much tried any Montana ROM I could find, but as I said, I don't know how to port so I got stuck in recovery loop. Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7 without me realising this. I found out nfc and selfie camera not working, so I wanted to downgrade to stock chinese firmware and just install gapps manually. After I fastboot flashed the nougat firmware - my phone hard bricked and won't even respond it seems dead. Thus your link will not help. Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Thank you anyway and if by chance you stumble upon some cool compatible ROM or to be honest a ROM that works really good - I don't really need NFC, but fingerprint scanner, turbo charger, selfie camera and reasonable battery management (some ROMs apparently drain it too quickly) would surely be features to keep. Also, if you have at hand a guide on how to port these roms which I can learn, I'd be very grateful.
Thank you
Six

sixtheninth said:
Problem was that I soft bricked moment I pressed 'factory reset' - the phone would just endlessly keep booting into recovery mode ...
Click to expand...
Click to collapse
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
sixtheninth said:
... Then I found out about Oreo project and tried to fastboot flash that. That was a major mistake. It upgraded bootloader to 7* without me realising this ... I wanted to downgrade to stock chinese firmware ... my phone hard bricked and won't even respond it seems dead ...
Click to expand...
Click to collapse
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
sixtheninth said:
Anyway I am already on a mission to try to revive it using following method: https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1
Click to expand...
Click to collapse
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread

irewer said:
At the moment you could use TWRP menu* 'Reboot - Bootloader' to boot in Fastboot Flash Mode (yes, it's bootloader) - and then press Power button (with 'START' tag in front of it).
But you have preferred to experiment ... You lost bootloader in due of custom 'chinese suppliers' firmware (non-original ROM) and forbidden factory reset with it.
* if you had stock recovery, you need to change mode with Volume buttons to Fastboot Flash Mode - and do the next steps in the same way; also you would be able directly to boot in Fastboot mode (bootloader) using long press Power button + Volume Down button
I warned you in straight way at that my post with a load of links to instructions and threads ('... you will have no way for downgrading of firmware in cause of higher version bootloader ...'). But you are bustler and illiterate, pardon me. By the way... do you know English or just use Google Translate?
* I have some unapproved info that OPP28.65-37[-2] firmware even uses bootloader version 12 (BL: BC12)
Yes, it may be will help you to boot in Fastboot menu. Please, read all method instructions carefully (RTFM!!!), don't experiment on your own risk/luck.
On Russian forum we have some examples of 'reviving' XT1799-2 with XT1794 mmcblk0.img - but it's the question of bootloader version and disk partition. May be now you have either bootloader version 06 and partition again or corrupted/mixed software or something else, so may be you'll be need to use distinct XT1799-2 mmcblk0.img. I have it ('Repair' folder), but there aren't any proved mentions of it's compatibility / applicability / integrality - all our XT1799-2 'bricks' were re-covered with XT1794 mmcblk0.img finally.
If you know Russian language or wanna risk to translate with Google Tranlsate (omg, please, don't do that ) - you may use Russian 4pda forum because at this very moment it has the most full load of info about XT1799-2 flashing and repairing (yes, all Slavs are misers and adventurers) not in Chinese language.
dmilz, I sincerely beg your pardon for messing up in your RR port thread
Click to expand...
Click to collapse
Well as irony had it, I did the operation literally seconds before I have read your warning. I was desperate of being stuck in either chinese rom or recovery loop. Anyway, I am amidst of transferring mmcblk0.img for XT1795 to my SD drive via Rufus. Problem is that it won't let me to choose GPT only MBR, so I hope that can still work. Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.

sixtheninth said:
Another problem is that I don't how to check the actual bootloader version I am having there installed right now should I manage to get there.
Click to expand...
Click to collapse
The version of installed bootloader you can check in Fastboot Flash Mode (bootloader as actually, Power + Volume Down buttons pressing and so on).
The version of non-installed firmware you can find into special '.info' file, for example: file 'MONTANA_RETCN_NZS26.68-108_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC_montana_retcn.info' inside ZUI-based MONTANA_RETCN_NZS26.68-108 ROM has this line:
Code:
MBM Version: BC.06

I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black (

sixtheninth said:
I used Win 10 and Rufus on XT-1799-2 using XT-1794 and 95 files, both holding power button for over 1min but screen remained black
Click to expand...
Click to collapse
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?

[/COLOR]
irewer said:
Because there were Android 7.1.1 images of mmcblk0 with corresponding partition and bootloader version (BC.07; and you may be need BC.08-BC.12 at this moment :shrugging: ).
Have you tried XT1799-2 mmcblk0.img (7.1.1)?
Have you ever found XT1794 Android 8.1.0-based mmcblk0.img ?
Click to expand...
Click to collapse
The results so far are underwhelming. I did the operation in Linux following https://forum.xda-developers.com/showpost.php?p=75932514&postcount=1 . Dowloaded both .img XT1794 and 95, checked the MD5 and flashed them on my sd card. Neither of them worked. Light was flashing at various intervals, but even after two minutes of holding the power button screen remained pitch black. I downloaded your image file for 1799-2, but ended with the very same result. I have not found XT1794 Android 8.1.0-based mmcblk0.img, yet. Would you know anything about it?

1799-2
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.

nikolaiderho said:
Hello. I installed OREO 8.1 on MOTO 1799-22. The front camera and NSF do not work. No one will tell you the solution? Thank you friends.
Click to expand...
Click to collapse
But did you recover it from hard brick by using mmcblk0.img based on Oreo?

Have you done with your RR port for xt1799 yet?
I have purchased the xt1799 Green Pomelo,unlocked bootloader,and installed the twrp. I tried to flash many 7.1 Roms that were intended for g5s and always failed. please notify me if you are still working on the port.

[MOD][1 APR] Android One Moto X4 [Pie 9.0][GSM][CDMA]

Is there a way to enable Moto's one button nav for the Android One variant Moto X4 without root access? Upgraded to Android Pie, Moto actions doesn't have an option for one button nav. Fingerprint nav was one of my favorite features.

Yes, but not as easy as it once was with Android 7.1.
You would have to flash the Retail version without erasing data (you can do this without unlocking bootloader). You will then have the ability to enable One Button Nav in the Motorola app.
At this point I would recommend just sticking with the Retail version as I have found nothing that I missed from Android One (other than the boot animation, maybe). You still get OTA updates just fine - in fact more timely than Android One.
This is what I have done with my second X4 (Android One/Fi). I switched to Retail without unlocking bootloader, and have been getting OTAs just fine.
But to get back to the Android One version, you would do the same process as above but with the Android One firmware, and your One Button Nav preference will stay (but lose the setting to turn it off).
Firmware:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flashing guide with some useful information:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I have attached my batch file (just remove the .txt extension).

jhedfors said:
Yes, but not as easy as it once was with Android 7.1.
You would have to flash the Retail version without erasing data (you can do this without unlocking bootloader). You will then have the ability to enable One Button Nav in the Motorola app.
At this point I would recommend just sticking with the Retail version as I have found nothing that I missed from Android One (other than the boot animation, maybe). You still get OTA updates just fine - in fact more timely than Android One.
This is what I have done with my second X4 (Android One/Fi). I switched to Retail without unlocking bootloader, and have been getting OTAs just fine.
But to get back to the Android One version, you would do the same process as above but with the Android One firmware, and your One Button Nav preference will stay (but lose the setting to turn it off).
Firmware:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flashing guide with some useful information:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
I have attached my batch file (just remove the .txt extension).
Click to expand...
Click to collapse
Thank you

Pooched Moto G7+ TWRP Install, Recovery Mode Not Responsive

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!!