Database Develop

[Q] Moto G Bootloop

Hi,
I have moto g 2014 dual sim. today I tried to reflash the os but got "Failed to validate system image" upon reboot. So I unlocked the bootloader and again reflashed the os but got bootloop.. Please tell me how to boot my moto G 2014?

Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.

If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app

Sorry for posting in different section, but I need help
eksasol said:
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
Click to expand...
Click to collapse
Let me tell you the series of events that led me to have bricked Moto G 2014:
1. I had X1068 Moto G 2-14
2. Wanted to reflash firmware and followed the steps provided in 4.2 section here http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
3. I got "Failed to Validate System Image" when I tried to reboot.
4. I was advised to unlock bootloader and reflash firmware. I did the same but got bootloop when I tried to reboot.
5. Now when I power on the phone, bootloader unlocked warning message comes and the screen blinks with the same message..
Please help Bro..

Who ever told you to unlock bootloader to flash firmware is giving bad advice. It is not required to unlock the bootloader to flash the factory firmware.
Make sure you're using the driver from here: http://www.mymotocast.com/download/MDM?platform=windows
(If you have other Android ADB drivers installed, uninstall them first, before installing this one.)
Make sure you are using mfastboot.exe, not the regular fastboot.exe.
Make sure your downloaded firmware is not corrupt and you got the correct version of the firmware for your device, there are different ones.
Download the firmware from here: http://sbf.droid-developers.org/phone.php?device=36
I believe your file is "Blur_Version.21.11.14.titan_retaildsds.retaildsdsall.en.03", but check on it.
After you reflash, make sure you boot into recovery mode and do a factory wipe.
The firmware for this phone is split into 3 files, so make sure you flash all three of them.

Issue Resolved
DillonFixDroids said:
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks bro.. It was my mistake not to flash all files in the firmware folder.. apart from three system files (0,1,2), we also need to flash fourth system file (3) in the firmware folder... Thanks again bro...

MotoG 2nd Gen
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.

4dglobal said:
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
Click to expand...
Click to collapse
Please be more presice, have you unlocked bootloader, before trying to flash the recovery?

Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.

joserodriguezv said:
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
Click to expand...
Click to collapse
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS

reefuge said:
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
Click to expand...
Click to collapse
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!

A New Problem
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution

Goutham_SRIRAM said:
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Click to expand...
Click to collapse
ota can only be installed to non rooted stock roms with stock recovery
tbh you need to minimum factory reset
but I believe you will need to install stock rom from scratch
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
joserodriguezv said:
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
Click to expand...
Click to collapse
Never had or seen this all I can suggest is a factory reset twice and a few reboots to see if settles down

Guys i need help! I have the european Dual Sim Moto 2nd gen, locked bootloader and i tried to install Android Marshmallow via the indian zip (soak test) that i found in XDA. After installing the update via internal storage, it got stuck in optimizing 157 apps/158, it bootlooped and now it stucked it 1/1 optmizing ... What can i do???
Please, anything.

Stuck on NRD90M test-keys

I updated to beta Nougat using a non-official-beta method and am somehow stuck with NRD90M test keys as my build number. The rom works ok for the most part, the only thing which doesn't seem to work properly is Themes.
Would now like to know what the appropriate process is to go to the new and official stock Nougat for EVA-L19. Thanks community!

So was I and I posted about it here and got the right advice to roll back:
forum.xda-developers.com/p9/help/nougat-update-borked-p9-2-imeis-t3534530#post70475746

thank you zemblance! so it would appear that i would have to rollback to stock then only update to official nougat using the built-in updater huh?

Which recovery did u use ? I got that same problem when I flashed with 3.0.0.0 instead of 3.0.2.0
Edit: here's the one http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331/page13

z4d02 said:
Which recovery did u use ? I got that same problem when I flashed with 3.0.0.0 instead of 3.0.2.0
Edit: here's the one http://forum.xda-developers.com/p9/development/wip-twrp-support-t3372331/page13
Click to expand...
Click to collapse
not sure which TWRP i used but its fixed now. i did the rollback to lollipop. now on B190 but now Themes is being wonky and I have no magazine unlock. :/

Flash 136 again, there should be two folders hw and dt that need to be in the dload folder too.
If they aren't there you could try flashing the l09 136 first then the l19 one straight after.
Sent from my EVA-L09 using Tapatalk

Ya tone obnaveli eto rom no skajite pojalusta kak vernutsya moy zovoskoy emui 4.1 honor 6x

So I managed to get myself into this bind as well back in January, but I just didn't have the stamina to fight it and I've been running that crap ever since. Now I thought it time to take care of it.
This is the scenario. I got an unlocked EVA-L09 with TWRP 3.0.2.0 running build NRD90M test-keys and I want to "fix it" and update it to the latest version.
What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
And I can as well ask if the Huawei builds are preferable or perhaps there's some other ROM/mod out there worth using instead? I was on CM for years before I got the P9, though such a ROM is of course unlikely to ever be made for the P9, maybe there's a good mod..?

Farmfield said:
What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?
And I can as well ask if the Huawei builds are preferable or perhaps there's some other ROM/mod out there worth using instead? I was on CM for years before I got the P9, though such a ROM is of course unlikely to ever be made for the P9, maybe there's a good mod..?
Click to expand...
Click to collapse
You need to download and flash the appropriate hw data update zip for the ROM that you installed.
And if you check out this forum you will see there is both Lineage OS (aka CM) and CM13 ROMs for the P9 :good:
Peace.

chris5s said:
You need to download and flash the appropriate hw data update zip for the ROM that you installed.
And if you check out this forum you will see there is both Lineage OS (aka CM) and CM13 ROMs for the P9 :good:
Peace.
Click to expand...
Click to collapse
Eh, yeah, that I know, but I'm not going to try to figure this out myself again as last time I did, I spent two days trying to get my phone to boot at all - and that's a first since I started messing with ROM's back in the HTC Hero days.
And I thought the undocumented SoC made "real" custom ROM's on P9 impossible - or did Huawei release the doc's?

Farmfield said:
Eh, yeah, that I know, but I'm not going to try to figure this out myself again as last time I did, I spent two days trying to get my phone to boot at all - and that's a first since I started messing with ROM's back in the HTC Hero days.
And I thought the undocumented SoC made "real" custom ROM's on P9 impossible - or did Huawei release the doc's?
Click to expand...
Click to collapse
Ok, so get the 2 files for the ROM you want, and flash update zip then hw data update zip next.
It worked in either TWRP or dload method for me. Of course, for dload method you need to unzip and flash each zip in turn, or TWRP can flash one after the other. Flashing will relock your bootloader...

Well, if you note my post count and alike, I'm not really a newbie here, I got 10 years experience messing about with custom Android ROM's and about the same experience of general Linux experience on top of that, so when I don't wanna do this without some trustworthy information on the workflow, etc, you should get there's good reason. So posting replies like -Oh, just flash something, it'll work out!, that looks a lot to me you just having been really lucky not getting into the situation I did.
So I will repost the question I posed and hopefully someone with that know how will reply.
I got an unlocked EVA-L09 with TWRP 3.0.2.0 running build NRD90M test-keys and I want to "fix it" and update it to the latest version. What do I need to do and in what order. Like, do I need to unroot/restore the Huawei bootloader, do I need to rollback to Android 6 before starting over, etc..?

Just to clarify....
I had an unlocked EVA-L09 with TWRP, running build NRD90M test-keys, and I wanted to fix it....
So, I downloaded update.zip and update_data_full_hw_eu.zip and flashed them one after the other using dload method. It worked. That was my workflow.
Just trying to help out, don't get shirty about it....or you can wait for someone who's been on the forum longer than me, or who has a higher post count than me. Btw, I've received help before from folks with very low post count and I know it's no indication or predictor of noob-ness.
Peace out...

*I* did the exact same thing and then spent the following 30 hours trying to get it to even boot.
And I really didn't want to be rude, but if I got that kinda post number, I'm not likely to ask for help with something like this unless I really needed it. As I said, I have a lot of experience of this stuff and I still messed up immensely trying this the first time, so I'm not even going to try before I have someone who really knows what *NOT* to do give me some hints on how to avoid getting into the same spot - because I'm not doing another 30h trying to save this phone if I mess up again, I'll just smash it and buy something else, like a used Nokia 3310, because it's just not worth the stress.

Moto E5 XT1920-15 (PETTYL) unlock bootloader)root/flashing GSIs

Deleted

bubba1601 said:
Hi
I have this new device but it's not any of the versions listed here (Nora/Rhyanna)
It's the UK version XT1920-15 sim unlocked, I'm just wandering if the steps to unlock/root are the same on this device as the other versions?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-e5-play/
I used this guide to unlock it. I also have this phone, but mine is from latin america, and it should work for yours. :good:

Deleted

bubba1601 said:
Your device is not the same.
The American / latin American version has android 8.0, 2 GB ram and a 5.2 inch screen.
The UK version has android 8.1, 1gb of ram and a 5.3 inch screen.
All such tutorials that work for the US version DON'T work on the UK version and TWRP installation fails completely.
Please be mindful when advising users things "should" work, as it doesn't work and your device is completely different to mine, so should not be attempted from that link.
Click to expand...
Click to collapse
No my phone has 1Gb of Ram and 16gigs of storage space along with 8.1 and TWRP installed. I used that guide to unlock the bootloader the TWRP in that guide doesn't work for our phones. I managed to find the TWRP version of the phone.

Deleted

bubba1601 said:
The guide says it's for android 8.0 though?
I still can't unlock the bootloader!
Click to expand...
Click to collapse
fastboot oem get_unlock_data
"Now command will return a string which you need to copy the string to a notepad with a single line by deleting all spaceNotepad
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)"
"To Get Bootloader Key for Moto E5 Play - Open the website Motorola’s unlock the bootloader site by Signing up or Log in in via Google Plus account"
Link:https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Make an account, also check if your device can even be unlocked on the website.
"Once you click the "Can my Device be unlocked?" you will receive a mail with unlock key.
Now copy the unlock key and type the following command and enter.
fastboot oem unlock UNLOCK_KEY
Here UNLOCK_Key is the place where you have to paste the unlock key which you copied from the email.
That's it! Your device will unlock. hah! Have fun!"
That's how you unlock the boot loader
Link for TWRP for PETTYL:https://mega.nz/#!anwAACZT!MJ95FCiIDH-kkLaZLpFvnKT5j_3Fe2goU-aZmSVeCKo
I couldn't find on XDA so I uploaded it to mega.

Deleted

Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing

did the op get it sorted

Deleted

bubba1601 said:
I'm running stock again.
No root, no twrp and as far as I'm concerned, project treble ROMs/images are complete waste of time, especially for this device where half the posted steps don't work, supplied resources don't work or twrp images and twrp back ups supposedly for this device don't work
Worse still, I had to pay to redownload my firmware.
Click to expand...
Click to collapse
No idea why it dosent work for you I maneged to flash twrp and root it with magisek also tried linege and ResurexionRemix it works fine only xposed dosent work

Deleted

plscotland said:
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
Click to expand...
Click to collapse
Can I flash this Recovery to XT1920-16 pettyl?
The file Moto_E5_XT1920-15-recovery.img is TWRP or STOCK recovery?
Also i'm loocking for Stock recovery for XT1920-16

Deleted

I just build custom recovery for pettyl -- ORANGE FOX , download at orangefox.tech
thanks. enjoy!
~whodat aka flash

Deleted

bubba1601 said:
There's already three different TWRPs for PETTYL.....two work one doesn't.
I made a TWRP for pettyl and it works 100% , The reason the others do not work is because they have EXT4 filesystem set to data partitions in the fstabs they were made with. Data partition is set to f2fs and thus it cannot be read. I also made a decrypt.zip for pettyl aswell, and I do not even own this device... I have only dove into android dev less than 2 months ago
Many people are already confused about twrp so do we really need another one to confuse everyone even more?
Click to expand...
Click to collapse
*triple facepalm* are you serious ?!?!
Maybe this site and android modifications is not for you bubba.
---------- Post added at 12:44 PM ---------- Previous post was at 12:32 PM ----------
bubba1601 said:
The comment you quoted says it's a TWRP file and I've not seen the stock recovery available for PETTYL .
Just bear in mind that I'm assuming the xt1920-15 that I have and txt1920-16 you have are identical, but I obviously cannot confirm that or do I know if they work the same I'm just assuming they do.
Click to expand...
Click to collapse
lol to get stock recovery file all you have to do is fastboot boot TWRP or OrangeFox and make a backup of recovery. Its that simple, but what would anyone want with stock recovery anyway?
If you really want it you can get the full stock firmware here, extract it and you will have stock recovery.img along with stock boot.img and everything else....
https://mirrors.lolinet.com/firmware/moto/pettyl/official/
Again, ENJOY!

Deleted

bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
He explained y other recoveries had prob and y his wouldn't next it has added features such as built in magisk and etc. test it to see other extra features instead of being a lil upset and taking it out on ppl being nice and fixing ur recovery probs

bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
Don't be a d*$k lashing out at a dev who does this work FOR free using up HIS free time to make it possible for you to make this complaint. We developers have to research to gain this knowledge. Be courteous and try to search the web to find the answers you seek and to fill in the blanks. Possibly guide others users in the right direction based on the knowledge you discover.
Don't bite the hand that feeds you. Listen to some nine inch nails, you might learn a thing or two about how to properly human.
He doesn't even own that device yet goes out of his way to provide support for it just for ungrateful individuals such as yourself to lash out at him for not explaining things clearly enough. If you lack the knowledge to fill in the blanks that he may have missed, that just shows that you're at risk of bricking your device from lack of knowledge on the subject. It won't hurt you to do a bit of research for yourself.
Sincerely,
The guy helping to guide that developer you lashed out at to supporting 64bit for YOUR DEVICE.

XT1965-T T-Mobile REVVLRY+ Stock rom

I got the T-mobile REVVLRY+ today, and naturally, I wanted to put the stock motorolla firmware on it. Partly to see if I could, partly to get rid of the T-Mobile bloat and see what Motorola features T-Mobile had removed.
Everything went swimmingly, I have PPW29.98-107 installed, I even have WIFI Calling. What I did lose, however, is VoLTE. I did use TWRP to perform a backup before flashing, so I tried restoring it to get a better look at how VoLTE works in the T-Mobile firmware. This is where things got hairy. I stupidly only backed up boot, system, and data. When I use TWRP to restore them, I get stuck in a boot loop. The built in boot loop fix in TWRP didn't help.
1. Any ideas on getting as close to stock as I can with only the boot, system, and data partitions?
2. Does anyone have access to a REVVLRY+ that would be willing to do a full backup that I may try to restore?
*Edit* SO I used the code *#*#4636#*#* and VoLTE provisioned is enabled, so maybe I do have VoLTE?
*Edit 2* Google Pay doesn't work, even after locking the bootloader. The device says that the operating system has been modified. Still trying to get it to restore.

FOUND IT!
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.

BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.

serris-chan said:
Where did you find it at? I would like to know because I'm trying to port Lineage OS to this phone. However, once I unlock the bootloader, I won't have an OS to use for it and i'll be screwed.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/lake/official/TMO/

HOW to
Hi, I just picked up the Revvlry+. Do you have step by step to install the Stock Moto firmware? I miss some of the features of the Moto. Also, was it easy to restore the TMO firmware just in case?

did you make any progress into the volte research? im on a unlocked xt1965-2 and using metro but i dont get volte in any of the stock roms or custom roms. i have tried flashing the modem from the stock tmo rom which didnt really do anything. i will probably try to flash the entire tmo rom tonight and see if it boots. im thinking if i get volte in the tmo rom and backup the persist, vendor and efs. then if i restore them onto a working cutom rom with volte enabled, volte should work.
i have also read about different scenarios in where you have to install workarounds to enable volte on treble roms. like installing the ims.apk to route the calls to volte and flashing a volte enabler to inject the correct files into the vendor partition.
my other device is a moto g5 plus which has numerous volte issues when switching between stock and custom roms or between different versions of android.

Did you use the Moto G7 Plus TWRP? I just picked up a Revvlry+ and I'm looking to root to install lawnchair or pixel launcher as a system app.

successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset

ghostdogg49504 said:
successfully unlocked the bootloader of my t-mobile revvlry which is a rebranded moto g7 i did it using this method but i'm going to be a little cautious on rooting unless i know it's safe and won't brick i could use some help with this https://www.androidinfotech.com/root-moto-g7-plus-pie/ i have the revvlry not the plus i want to try multirom installer and install ubuntu touch on it but i don't want to screw up my only phone but the only way i can try it is if i had root permissions to do so to install linux tried userland but i couldn't get unity desktop to work i'd rather have full root instead of fakeroot update: i was able to boot twrp before but now it doesn't work i think my firmware updated cause now when i run fastboot boot twrp.img nothing happens and i end up with remote failed reboot the phone and it goes directly to recovery with the only option is to do a factory reset
Click to expand...
Click to collapse
Are you saying with a Tmobile Revvlry, you were able to just go to the Motorola bootloader unlock page, paste your unlock codes, and presto as if it was just a normal Moto phone? If so, that is awesome!
I am thinking of swapping my Moto G7 Play with a Revvlry because of the 3gb RAM and NFC (the size of the G7 Play is perfect, I don't want to be forced to carry around a giant phone), but would love to flash the stock Moto G7 Play ROM over the Tmobile version. Not sure I'm willing to risk it, but if anyone has tried, I'd love to hear about it.

Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?

ultracoolguy said:
Logged into my account for this. Sorry if this is a little offtopic, but I want to see if this phone is compatible(or rather, how compatible it is) not only with Stock ROMs, but also with custom ROMs. For those REVVLRY owners, what have been your experience with this?
Click to expand...
Click to collapse
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.

tri_cchan said:
Phone works great with stock ROMs. I haven't tested out any custom ROMs, but I do have root on my REVVLRY.
Click to expand...
Click to collapse
nice man

Relocking Bootloader
Would I do the OEM lockbootloader command to lock it back

Can confirm flashing Moto g7 play firmware on T-Mobile revvlry. Caveat, you can no longer take OTA's and NFC is broken. Also can be bootloader unlocked through the Moto website.

Wouldn't you need to flash the G7 plus firmware for NFC to work?

guitardoc64 said:
Wouldn't you need to flash the G7 plus firmware for NFC to work?
Click to expand...
Click to collapse
That makes sense, the SD632 is NFC capable however I'm on the G7 play not the plus (I know, I know wrong forum)

I can't get the stock rom to work. It just bootloops every time. I tried all 3 versions. Any ideas?

Hey friends, would one of you kind sould who own the Revvlry+ be kind enough to post this Wallpaper?
Thanks in advance!

BanterJSmoke said:
I found a repo of firmware that has the TMO firmware! flashing now!
I can't share the external link yet.
Click to expand...
Click to collapse
Did you manage to restore it with firmware? Because I have a bootloop and I'm looking for a solution

quiet boy
I just solved the problem I had like 4 crazy hours with solve bootloop, the problem that I commanded automatic flash, not flashing the vendor partition and then flashed the manual vendor partition
mfastboot flash vendor vendor.img and ready
edit:
for users with Revvlry+ variant (XT1965-T) use this Flash.bat

Unofficial Unofficial TWRP and Gsi Android 11 or 12(kinda)

Hi guys. First post here and I'm not around my files so it will be a straight forward guide with no downloads right now, you're smart, you know where to source them...
Ok first and foremost, Unlock your bootloader, Motorola makes it easy and there are good guides on this site to do that.
Once your bootloader is unlocked your going to look for an Unofficial TWRP package for the Lenovo K12 Pro... "What?", You say... Yep K12 Pro. Download it and jump over to your boot loader and flash it or just boot to it through fastboot and now you have a way to install root permanently, or not if you would rather not, but you have that option now.
Next find the lastest Magisk apk and get that joker installed using TWRP. Now reboot into system and everything should load up as normal BUT now you have root with TWRP recovery. I have did this at least 100 times since figuring it out and sometimes I do this with a fresh factory flash and sometimes I do this as is without even wiping user data before or after. I'm no expert and I don't care to lose my files so on the rare occasion that I do have a boot loop or soft brick, I get myself into recovery and flash ANY of the cebu firmwares and do it all over again...
Ok, so now we know how to get root and custom recovery... Next find an AB version of Gsi 11 or "borrow" the latest system.img from an Android 12 update or firmware image and open up fastboot again and flash only the system.image to the system partition. Wipe or don't wipe, up to how lucky you're feeling, and then reboot to system... 11 will take 2-3 minutes to boot the first time and I had nearly all functionality when it did. 12, well, that's a little different, it took 3-4 minutes to boot to the setup screen and then lagged like crazy BUT it eventually started downloading a few files it was missing and got better. I couldn't get my calls or messaging to work right but I could hear my phone ring but it never called the phone app to open and let me answer... Weird stuff BUT FYI 12 is a pretty nice to look at OS and maybe one of you guys can take this to the next level and get some true usefulness out of it. I know it's not very technical but when one of you true geniuses try it and get it worked out please feel free to post a true guide with proper instruction and proper terms.
That's all I got guys. Thanks for reading this and ALSO if anybody has a complete list of fastboot and adb commands for the g9 Power or the K12 Pro please share them with me. I've gotten better at getting around but I'm not near as good as if like to be.

Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.

mistersmee said:
Obligatory safety PSA:
The Lenovo K12 Pro is just the Moto G9 Power sold under a different name, however, there could be minor differences that could cause problems.
Also, while searching for this unofficial TWRP build, I only found it on websites like unofficialtwrp.com, and the like. I couldn't find one on XDA. I was unable to find the device tree, or the kernel sources used by this website anywhere on the internet, and as such, the TWRP images provided on such websites are literal blackboxes.
TWRP images created and shared on XDA can be trusted, the source code used to create the image is displayed on the posts of the images, and XDA itself is a trusted site.
Here is what the official TWRP team have to say on the matter:
Unofficial TWRP Downloads
Like the TWRP team say, it is up to you to flash these images or not, but be careful.
Click to expand...
Click to collapse
Agreed, I posted as a proof of concept so people with more know how could improve upon. Use this at your own discretion and have fun in doing so.

Is there a way you could post a detailed, step by step instructions of this, please?
I've found the unofficial twrp, but haven't rooted a phone in over 2 years, so I'm a bit rusty, plus things have changed a lot these last couple years.
I'd really appreciate if you could take your time for that.
Thanks in advance.

I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
That would be awesome mate!
I really appreciate that!
Thanks in advance.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock

zfk110 said:
I was able to boot into TWRP but when I flash Twrp.img to recovery it won't stick, I always had to do fastboot into recovery if I try to boot into recovery it just reboots back into system, also can't remove any junkware from system, it always gives me error when I tried to remove it using root browser, im still on stock
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-2-cebu.4279917/
for TWRP.
As for removing junkware, as you may or may not know, dynamic partitions is a thing since Android 10. In it, the /system, /product and /vendor partitions have been subsumed under a /super partition. And Google has conveniently used a type of ext4 filesystem for that /super partition, that is read-only.
TL;DR: You cannot modify Android using any sort of "root browser" or inside TWRP, for that matter, anymore.
Off the top of my head, the only way you can remove "junkware" is through some Magisk modules, and even they might not even work.

There are three ways to debloat AFAIK:
Magisk - this is my preferred method. You either replace apks you want removed or empty the /product/etc/nondisable folder so they can be disabled. Takes minimal effort to figure out how to make modules and no scripting knowledge required.
Cross-flashing - you can flash retail software, often including modem firmware, to most Moto phones. The result is a clean system with no carrier junkware.
System R/W Scripts - this is the most nonsensical of the options(IMO), but this option exists if you look around and want to experiment. The big drawback here is that you have to redo everything after every update.

Dauksza72 said:
I don't mind helping you out but I can't post publicly because the rules of the forum and the fact that it's unofficial. I'll get a guide wrote up and PM you. I've had no issues with my device at all but remember it is use at your own discretion.
Click to expand...
Click to collapse
Hello. I know you're new and welcome. I just want you to know, being an unofficial twrp isn't necessarily bad by itself. It's that the sources can't be verified. Lots of devces don't have official TWRPs, yet still have a rockin development section with TWRP instructions, as long as it's shared on a trusted site (I only trust 1 other) and lists it's sources and, even then, it should have the warning. Lots of scam sites target root noobs, as you've probably noticed. I don't think sharing instructions would have been against the rules, but should include a warning to let people know it's a questionable twrp build and it poses a risk, but all of our phones are at risk anyway. We don't have to worry about it anymore though since we have an official and still we are at risk, just far less risk. It comes with the territory. On the other hand, I've been I've been doing this for a very long time with countless phones and I've never noticed any malicious activity on any on any of them.