Database Develop

[Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition

Follow directions, do NOT flash this image. Flashing the image will bootloop you (easily fixed by flashing proper boot.img). You must only BOOT this image. Again DO NOT FLASH IT, I won't help you out of any mess you get yourself into with this.
Unlock your device with Motorola's site
Boot Image
Device will boot up, install su and quickly reboot.
Then install Chainfire's SuperSU from the Play Store
unzip pure2014sb.zip
adb reboot bootloader
fastboot boot pure2014sb.img

Running up in Moto X Retail BR, Tks

Thanks!!! Now my weekend is complete.
Sent from my SCH-I545 using XDA Free mobile app

I am a new user can you elaborate how should i start?
I have a Pure Edition Indian Variant

Does this wipe your phone data at all? My phone data was completely wiped when I unlocked the bootloader, so I want to make sure that doesn't happen again.

TBayTom said:
Does this wipe your phone data at all? My phone data was completely wiped when I unlocked the bootloader, so I want to make sure that doesn't happen again.
Click to expand...
Click to collapse
No man, wipe completely is only when unlock bootloader.

Can Someone help me with elaborated steps ?

kartik.bose said:
Can Someone help me with elaborated steps ?
Click to expand...
Click to collapse
Check your inbox.
Sent from my Sexus X XT1095

Can you send that info my way too please? I've unlocked my bootloader but not sure where to go from here...

jcase, awesome as always. You are such a great help to all of us "regular people" here at XDA.

From Droidviews: http://www.droidviews.com/root-motox-2014-pure-edition-with-superboot/
Prerequisites
A Moto X 2014 with unlocked bootloader. You can unlock the bootloader by following the instructions given at Motorola official page.
Set up ADB and Fastboot on your computer or download the minimal ADB and fastboot tool from here (unzip it).
Install Motorola USB Drivers on your computer.
Download the modified boot image by jcase: pure2014sb.zip
Open Settings> Developer options and enable USB Debugging on your device.
Root MotoX 2014 Pure Edition with Superboot
Having taken care of the prerequisites mentioned above, you can now proceed to root your Moto X 2014. Just follow the steps given below.
1. Extract the pure2014sb.zip file and copy the pure2014sb.img file into the platform-tools folder (in case you have Android SDK installed) or copy the files into the mfastboot v2 folder.
2. While the folder with ADB and fastboot files is open, right-click on an empty space and select “Open command window here” option to launch a cmd.
3. Connect your Moto X 2014 to computer using a USB cable.
4. Now type the following command in the cmd window and press the Enter key:
adb reboot bootloader
5. Your phone will reboot into the Fastboot mode.
6. Then issue the following command:
fastboot boot pure2014sb.img
7. When the phone boots up, install su and quickly reboot it.
8. When the device boots up again, go to Google Play store and install the SuperUser app.

Motorola site says my phone is not elgible for unlocked bootloader. Have Tmo pure edition 2014 Moto X. Any ideas?

So for the rest of us that got a carrier phone (not the pure edition) -
I got the ATT one with all the bloat on it. I'd really like to get rid of that crap.
Is there some way I could flash one of the factory gsm images here? via the stock recovery or via adb?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

iNiREALiZED said:
Motorola site says my phone is not elgible for unlocked bootloader. Have Tmo pure edition 2014 Moto X. Any ideas?
Click to expand...
Click to collapse
I had the same issue go through the whole code and make sure all spaces are gone including in front of the first character and you should be good

cpolly69 said:
So for the rest of us that got a carrier phone (not the pure edition) -
I got the ATT one with all the bloat on it. I'd really like to get rid of that crap.
Is there some way I could flash one of the factory gsm images here? via the stock recovery or via adb?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Click to expand...
Click to collapse
As of now, no you cant. ATT may or may not (probably not) get a bootloader unlock. It probably will eventually get root though, and when it does you can use a root app to uninstall those system apps from ATT. No guarantee the phone will work properly after you get rid of them though, it is possible that some OS modifications rely on parts of those apps.

yeah i pretty much can't wait until i get root access -
i'm pretty confident killing the att bloat isn't going to affect the it- i disabled every one of their apps within 10 minutes of having the phone...
i just wish i could load up ti backup and get rid of them...

bostonirishguy13 said:
From Droidviews: http://www.droidviews.com/root-motox-2014-pure-edition-with-superboot/
Prerequisites
A Moto X 2014 with unlocked bootloader. You can unlock the bootloader by following the instructions given at Motorola official page.
Set up ADB and Fastboot on your computer or download the minimal ADB and fastboot tool from here (unzip it).
Install Motorola USB Drivers on your computer.
Download the modified boot image by jcase: pure2014sb.zip
Open Settings> Developer options and enable USB Debugging on your device.
Root MotoX 2014 Pure Edition with Superboot
Having taken care of the prerequisites mentioned above, you can now proceed to root your Moto X 2014. Just follow the steps given below.
1. Extract the pure2014sb.zip file and copy the pure2014sb.img file into the platform-tools folder (in case you have Android SDK installed) or copy the files into the mfastboot v2 folder.
2. While the folder with ADB and fastboot files is open, right-click on an empty space and select “Open command window here” option to launch a cmd.
3. Connect your Moto X 2014 to computer using a USB cable.
4. Now type the following command in the cmd window and press the Enter key:
adb reboot bootloader
5. Your phone will reboot into the Fastboot mode.
6. Then issue the following command:
fastboot boot pure2014sb.img
7. When the phone boots up, install su and quickly reboot it.
8. When the device boots up again, go to Google Play store and install the SuperUser app.
Click to expand...
Click to collapse
what mean's :
7. When the phone boots up, install su and quickly reboot it
install su = superSU apk ?
thanks for help

jonata said:
what mean's :
7. When the phone boots up, install su and quickly reboot it
install su = superSU apk ?
thanks for help
Click to expand...
Click to collapse
This 7th step is automatic. The phone will boot and install su files and quickly reboot after that.
Once it boots up, go to the store and download SuperSU.

MaKTaiL said:
This 7th step is automatic. The phone will boot and install su files and quickly reboot after that.
Once it boots up, go to the store and download SuperSU.
Click to expand...
Click to collapse
and where is su files ?
or, where I can Find it ?
need to copy in the memoty of phone ?
thanks for help

I would think the su files are in the img file that was previously flashed in an earlier step. Please correct me if I'm wrong!

[Q&A] [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition

Q&A for [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

MotoX Pure - UnRoot To Update Firmware
I used the Jcase method (fastboot boot pure2014sb.img) to root my new MotoX Pure. Worked great. However, the next day I received a notification on the phone that a firmware update is available: "New FIrmware Available" "Update to get the lastest Motorola Sensor. . ."
Because this method uses fastboot boot vs fastboot flash, I don't understand how I can go back to stock in order to update firmware.
Wondering if someone could school me on what the heck it actually means to fastboot boot vs fastboot flash. Basically looking for a way to be able to un-root, apply firmware update, and then re-root.
A

You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk

tyea said:
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
if they said they would, then i'm glad. getting worried here lol

root moto x 2014 followed by ota lollipop update
The moto x is delivered with KitKat initially and then updated via ota later once powered up etc. If I follow your method as soon as I get the phone and then later accept the ota update to lollipop, will it cause problems or lose root?

bootloop
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me

deelv said:
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
Click to expand...
Click to collapse
The same thing happened to me but I've gotten out of the boot loop by getting to fastboot (hold down the power button till the screen turns off and then you have to guess and hold the power and volume down button for about 5 seconds and then release the power button but hold down the volume button until you see the fastboot. If it doesn't get to fastboot try it again.)
When you're at the fastboot, connect to a computer and cmd a command "fastboot erase userdata" and then "fastboot erase cache" to pretty much factory reset and get you out of the boot loop. Then it should boot and tell you to set up the device.
I would recommend looking for the root boot image from chainfire them self, they recently released it. Just look for your model # (e.g. xt1095) and "fastboot boot (insert boot image)"
My Moto x 2014 is currently rooted with chainfire's boot image. It works like a charm.

XT1092 bootloop after OTA
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers

HamRack said:
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
Click to expand...
Click to collapse
Boot this boot.img : http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Its for xt1095 but some have confirmed working on xt1092
Sent from my Moto X 2014 Pure Edition

does it work on Android 5.0?

Yes, I'm currently running Android 5.0 Lollipop.
Sent from my Moto X 2014 Pure Edition

Bootloop
Stuck in a bootloop. Followed all your instructions carefully. :/ Not able to boot into bootloader.

Formatted Telus Moto X (2014) SD card and all data ... recovered.
I might make a tutorial video on how to recover from a mistake like mine, and I may not have done it correctly, but the phone is back operational.
What I did to screw it up :
1) Unlocked the bootloader and installed TWRP without doing research about development for the phone
2) The phone is already almost stock android and that's one of it's selling points so I don't know why I wanted to unlock and root
3) Got frustrated and wiped / formatted internal SD ... since I use to flash ROM's on my older Huawei this way ... it must be the same right ... smh.
4) Freaked the eff out, had thoughts of just running it over with the car because that qualifies under my 2-year warranty, since I voided it by unlocking.
5) Thought I knew it all when I really don't understand most of the lingo still
What I did to 'TRY' to fix it :
1) Scoured the internet for ROMS / Zips.
2) I was in 'Android Studio' ... unnecessary.
3) Tried flashing .zips in TWRP by draggin and dropping .zips ... contanst 'FAILED' signs.
4) Tried sideloading as I was grasping at straws by this point. 'FAILED'
5) Considered buying an OTG cable.
6) Spent hours going in circles
What I did to fix it :
1) Downloaded the SDK ... 'adt-bundle-windows-x86_64-20140702'
2) Installed the 'Google USB drivers' as I checked 'Device Manager' and there was an exclamation ... this is why when I went typed 'ADB devices' nothing showed up. I 'manually' installed the drivers. VOILA, first step.
3) Found a .ZIP file I believe was the correct one ... ;RETCA_XT1097_4.4.4_KXE21.187-42_cid14_CFC.xml.zip' (From this website I believe)
4) Watched a few youtube tutorials on how to flash from within 'SDK' > 'Platform-Tools'
5) Extracted the .ZIP file into 'Platform-Tools'
6) Had phone booted into fastboot mode
7) Opened the CMD from within 'Platform-Tools' with that .ZIP file within that folder, held 'SHIFT' 'Right-click" > 'Run CMD'
8) This is where I didn't do it properly, but the phone is booted for now and working ... with these Commands
- fastboot flash boot boot.img;
- fastboot.exe flash system system.img_sparsechunk.0
- fastboot.exe flash system system.img_sparsechunk.1
- fastboot.exe flash system system.img_sparsechunk.2
- fastboot.exe flash system system.img_sparsechunk.3
- fastboot.exe flash system system.img_sparsechunk.4
Got that nice Motorola earth screen and booted to the welcome screen. Froze. I reset. Froze. Walked away from phone, came back and tried to see if I could press 'OK' and it worked.
All-in-All , not worth it for the average consumer and not worth it for someone such as myself who was stupid and just wanted to 'play around' with a brand new 2-year warrantied $500 phone.

TELUS Moto X (XT1097) doesn't boot after last OTA. Help!

Hey guys,
I have rooted my Moto X 2014 (XT1097) with Chainfire auto root method about 6 months ago and I decided to accept the OTA update I got today from TELUS (22.121.11.en.CA). If I remember correctly I was on 5.0.1 before accepting this OTA.
Now the phone is stuck in the custom boot logo screen that I installed after rooting and even if I try to shut it down, it just boots up and gets stuck in the logo screen.
What should I do? I can access the bootup screen by holding power and volume down.

bobitza said:
What should I do?
Click to expand...
Click to collapse
Let me reply myself so that maybe others can use this info to fix their devices as well.
Step 1: You need to install the ADB platform tools (should be plenty of threads about that)
Step 2: You need to find a system.img and a boot.img to match your needs. I have a XT1097 with TELUS in Canada, so I have found this thread and downloaded the big .zip file (big thanks to Steve-x!). For US people the graffixnyc site has images for XT1095 that you can use. Move those .img files where your fastboot.exe file is found
Step 3: Boot your device in bootloader mode (hold power and volume down) and connect it to your PC
Step 4: Install the images with the fastboot command by typing this in a cmd window
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
Or in the case of the TELUS image, the system image is split into 7 files ... just flash system them one after the other. Steve mentioned something about the recovery.img, but wasn't sure how to flash that so I did it this way.
Step 5: (Optional) If you had something else installed you will get some errors, here's how to fix them. Boot back in the bootloader and choose Recovery, then when you see the screen with the "sick" Android, keep Power pressed and tap on Vol Up to enter Recovery Menu. Choose to delete data and delete cache. Reboot.
If you used Steve's image you should be booting into TELUS Android 5.0.1, just before the cursed update. You can even do now the 5.0.1+ update OTA. You're back in stock ROMs world

Glad you got it fired up again. I haven't taken the OTA yet myself with my Moto X's, was hoping to get the entire image with Motorola Device Manager.

Le sigh
Man i'm having nothing but issues. I've done everything that i was supposed to do, but i cant get the files to load.

Moto X4 Bricked - no fastboot - USB 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL

Hi,
i have a pretty bricked Moto X4 - I unlocked the bootloader and bootet twrp via
"fastboot boot twrp-3.2.3-1-payton.img"
I wiped and installed lineage-15.1-20190206-nightly-payton-signed.zip via sideload.
After rebooting the machine is dead. No screen. No fastboot. Power + up or down do not lead to anything.
I can get it to a stage where it shows up on the USB bus as:
Bus 002 Device 119: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
But no adb or fastboot and screen is pitch black.
And chance of reanimating this device?
Flo

Short answer, yes; you should be 'fine'.
I don't have the time at the moment to get you any details nor do I know of what side effects there are after fixing this.

dougo007 said:
Short answer, yes; you should be 'fine'.
I don't have the time at the moment to get you any details nor do I know of what side effects there are after fixing this.
Click to expand...
Click to collapse
I got my way after opening 150 Tabs ob various sites a bit further.
I can get back to fastboot and flash a new bootloader.
But whenever i go back to flashing lineageos -> BOOM. Back to black screen
Here is currently my procedure:
Code:
blankflash/qboot blank-flash blankflash/singleimage.bin
fastboot flash partition PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/gpt.bin
fastboot flash bootloader PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/bootloader.img
fastboot reload-bootloader
fastboot boot twrp-3.2.3-1-payton.img
-> format data
-> wipe system
adb sideload lineage-15.1-20190206-nightly-payton-signed.zip
-> reboot recovery
-> Black screen
My guess is that i am missing something important. After flashing my HTC 10 for 100s of times without any hassle i am puzzled.
Flo

flohoff said:
I got my way after opening 150 Tabs ob various sites a bit further.
I can get back to fastboot and flash a new bootloader.
But whenever i go back to flashing lineageos -> BOOM. Back to black screen
Here is currently my procedure:
Code:
blankflash/qboot blank-flash blankflash/singleimage.bin
fastboot flash partition PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/gpt.bin
fastboot flash bootloader PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/bootloader.img
fastboot reload-bootloader
fastboot boot twrp-3.2.3-1-payton.img
-> format data
-> wipe system
adb sideload lineage-15.1-20190206-nightly-payton-signed.zip
-> reboot recovery
-> Black screen
My guess is that i am missing something important. After flashing my HTC 10 for 100s of times without any hassle i am puzzled.
Flo
Click to expand...
Click to collapse
You need to flash the lineage zip with twrp. You can't sideload. Just remember it installs to the opposite slot.
Read this thread https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265

ptn107 said:
You need to flash the lineage zip with twrp. You can't sideload. Just remember it installs to the opposite slot.
Read this thread https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
Click to expand...
Click to collapse
I know i have 2 system partitions - But after flashing Lineage with or without TWRP the bootloader is gone - I cant power on with power up/down and get to the bootloaders fastboot menu. And from my understanding the bootloader is not part of the A/B partitioning - right?
So i am puzzled on what is going on. Flashing LineageOS from TWRP breaks something on the phone letting the Bootloader fail and go back to the QDL safe mode.
Flo

flohoff said:
I know i have 2 system partitions - But after flashing Lineage with or without TWRP the bootloader is gone - I cant power on with power up/down and get to the bootloaders fastboot menu. And from my understanding the bootloader is not part of the A/B partitioning - right?
So i am puzzled on what is going on. Flashing LineageOS from TWRP breaks something on the phone letting the Bootloader fail and go back to the QDL safe mode.
Click to expand...
Click to collapse
Okay - got a bit further - Side B never had a bootloader - Stock did never do a software update so side B never had been flashed. Now it does not fall back to QDL mode anymore. Still lineageos does not boot.
So i guess i fail some partition content from Stock ROM in the B side.
Flo

I'm glad you're fining your way.
I would suggest a complete flash of stock based on your variant ex. XT1900-1.
Make sure your phone is still good and start from step one.
Then make sure you use the copy partitions zip; I think is what was screwing up someone before.
Either it was that or they tried to flash multiple things at the same time (magisk, google, TWRP).

dougo007 said:
I'm glad you're fining your way.
I would suggest a complete flash of stock based on your variant ex. XT1900-1.
Click to expand...
Click to collapse
I am having a hard time identifying which of the STOCK images belong to which Moto X4 variant.
For me its a XT1900-7 - And i have a page listing hundrets of variants of images but i fail to identify anything common.
I tried looking for strings in the image binaries and failed.
Am am booting to LineageOS now after flashing side B with stuff i found - i am not shure whether it fits my Phone model.
Flo

Based on this:
https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92
It appears that the XT1900-1 firmware runs on a XT1900-7 device, but I'm not 100% about LTE coverage (US vs EU)
---------- Post added at 08:04 PM ---------- Previous post was at 07:51 PM ----------
Here is the best 'visual' as too see how many partitions are used.
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
There are two copies of everything but there is no dedicated recovery or cache partition anymore in an A/B treble system.
Based on your question of the boot loader, I'm not sure you used the copy partitions zip (although I'm not 100% what it does but I assume it means all of the content in A is copied to B).
If something doesn't seem to be running properly, I'd suggest flashing the firmware from here:
https://forum.xda-developers.com/showpost.php?p=77490529&postcount=2
Use the one listed last and run this in bootloader.

@flohoff, I had the same problem when I tried to install LineageOS 15.1 without copying partitions (A→B ) first. It's frustrating that the LineageOS install instructions don't mention this step.
After using BlankFlash to unbrick it, and reading the LineageOS 15.1 install instructions here on XDA, and copying the partitions, I soon succeeded. Have you managed to get past this as well?

Revvlry+ to Moto G7 Plus conversion guide

Hi, i will not waste anyones time, i just want to share with you the steps that i took to convert my T-mobile Revvlry+ into a Moto G7 Plus, obviously, this is just a software conversion, also with this conversion, you will now have Android 10 on your device, and if you want to, Root, so, lets get started.
DISCLAIMER
Please read the guide completely before trying anything on your device, i will not be responsible for anything that happens to your phone, if you dont understand something or you dont feel comfortable doing one of the steps, please clear all of your doubts in the comment section, ill try my best to help you trough the steps.
Also, because the first steps involve unlocking your bootloader, your warranty will now be void.
Prerequisites:
Motorola device drivers: HERE
android sdk platform-tools: HERE
Moto g7 plus retail android 10 firmware: HERE for this i used the QPWS30.61-21-11 build
Flash conversion.bat: at the end of the post
logo.bin: HERE thanks to @luiz_neto for this mod, please thank him on his post
Instructions:
First download all the files, install the motorola device drivers if you dont have them already, extract the platform-tools to your desktop for easy access and inside of this folder extract the firmware, logo.bin and flash conversion.bat files, the platform-tools will now be a working ADB and Fastboot enviroment, if you are using windows 10 please follow THIS guide to enable this folder in powershell, just change the path of the guide for the path where you extracted the platform-tools folder.
Now you need to unlock your bootloader, you have to know that this will erase all your data, so please first backup all of your files, then go to settings and enable the developer settings by clicking 7 times on the "Build number" option in the "About phone" section, then go into system>developer settings and enable "oem unlock", now turn off your phone and pressing volume down, connect the usb cable, the phone will boot into bootloader, some drivers will automaticaly install, after this, go to the Motorola bootloader unlock website HERE and log in or create an account, after this just follow the steps on the website to unlock your bootloader, you will use platform-tools as your ADB and Fastboot enviroment for this, just download it and extract it to your desktop for easy access.
Basicaly what you have to do is send a fastboot command to get some info out of the phone
Code:
fastboot get oem_unlock_data
this is done on windows command prompt (CMD), after sending this command, the phone will return bunch of text, you select and copy this text and put it trough the data scrubbing tool present on the motorola website to get only the alfanumeric string of data, you put this data on the website and it will thell you wheter your bootloader can be unlocked or not, the Revvlry+ is an unlockable model, now at the bottom of the page a button will appear to ask for the unlock code, this code will get delivered to your email, now you just have to run a command twice and your bootloader will be unlocked
Code:
fastboot oem unlock UNIQUE KEY
The unique key is the one that motorola will send to your email.
At this point you can root your phone, install TWRP and a custom rom, but i will not go intos this, the guides made for the Moto G7 plus work for our phone, now we will proceed to make the conversion.
If you are using this guide with a newer build, please open the flash conversion.bat with notepad++ and check that the files mentioned on the .bat match the files on the newer firmware, if its missing a file, or it has more files listed, just add or erase the line that points to it, specialy the sparsechunk files wich can vary from firmware versions.
Now you just have to run the flash conversion.bat and wait, the script will automaticaly flash the moto g7 plus firmware including the modded logo.bin that will hide the unlocked bootloader warning screen, it takes a few minutes to do so, just be patient.
When the script finishes it will close and your phone will reboot, just give it a few minutes and you will be greeted with the android 10 setup wizard and thats it, your Revvlry+ is now a Moto G7 Plus softwarewise, at this point you can follow a guide to install TWRP and Root your phone, the guides for the Moto G7 Plus are aplicable for our device.
And thats it, thank you for your time and i hope this guide is helpful to you.

I actually tried it in another Revvlry+ 3 months ago but the boot warning is not removed and safetynet does not pass it, in bootloader state it says:flashing locked instead of being restored as oem_lock in bootloader

darkherman said:
I actually tried it in another Revvlry+ 3 months ago but the boot warning is not removed and safetynet does not pass it, in bootloader state it says:flashing locked instead of being restored as oem_lock in bootloader
Click to expand...
Click to collapse
None of the g7 plus varients can restore the oem lock....just the flashing lock.... I use a mod boot logo .for the bootloader Msg
If you are rooted
Flash magisk mods riru core and riru edxposed. install hidden core modules.apk......reboot and enabled the hidden core mod in edexposed mgr
Clear cache and data for playstore and Google play services...then reboot.....enable cts check in magisk...reboot....
Use this command to flash logo
fastboot flash logo Developer_Logo.bin

KtownJeff said:
None of the g7 plus varients can restore the oem lock....just the flashing lock.... I use a mod boot logo .for the bootloader Msg
If you are rooted
Flash magisk mods riru core and riru edxposed. install hidden core modules.apk......reboot and enabled the hidden core mod in edexposed mgr
Clear cache and data for playstore and Google play services...then reboot.....enable cts check in magisk...reboot....
Use this command to flash logo
fastboot flash logo Developer_Logo.bin
Click to expand...
Click to collapse
no thanks too many modifications for logo.bin and not pass safetynet

Is it like a full ROM flash?
Will VoLTE and Wi-Fi Calling stay intact after conversation to Android 10?

darkherman said:
no thanks too many modifications for logo.bin and pass safetynet
Click to expand...
Click to collapse
well this is the only solution for the safety net issue..... If you find or develop a new one please post

mingkee said:
Is it like a full ROM flash?
Will VoLTE and Wi-Fi Calling stay intact after conversation to Android 10?
Click to expand...
Click to collapse
Yes its a full flash but i believe that VoLTE will not work, im in mexico and VoLTE and Wifi Calling is not a thing so i cant test it