Database Develop

[Q] Questions about Moto X versions

First post! - joined at first to read posts but now have one of my own mixed with a number of questions.
I recently picked up a used Moto X from Craiglist and the guy claimed it is an unlocked T-Mobile version with an already unlocked bootloader. The whole point of this purchase was so I could experiment and learn more about what goes on with phones.
How can I verify that the guy is really telling me the truth about the version? I used imei.info and it told me it was an XT1055. However, swappa.com told me it was XT1053. I saw on some post here that XT1053 matches the T-Mobile/Dev version which would make sense with what the Craigslist guy told me. Both sites claim it is not 100% accurate so how else can I verify actual version? There is no logo of T-Mobile on the back of this device. Is there some serial number lookup database?
This led me to wonder if it's possible to flash different software variants onto this phone? In theory, could I download the images for an ATT variant and flash them onto my supposed T-Mobile version? Apart from the potential of overwriting the unlocked bootloader and preventing me from downgrading versions (from the other posts that I've read here), would the phone work assuming my SIM/network is ATT? The IMEI would remain the same, right? How much of the underlying hardware configuration is tied to version of the software that I flash onto the phone?
Could the guy have purchased this phone to whatever carrier XT1055 matches to - rooted or unlocked the bootloader, and flashed the XT1053 images?
At this point, using mfastboot I was able to verify that the bootloader was unlocked but went ahead and performed the same process on Moto's site anyway (and this seemed to work - did this for experimenting). I then downloaded TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC to reflash onto the phone. This whole process might have seemed redundant but I just wanted to ensure the used phone that I had purchased matched a stock set of images (minus the unlocked bootloader).
Thanks! Apologies in advance if there was another similar post - I tried searching but maybe not hard enough.

klxavier said:
First post! - joined at first to read posts but now have one of my own mixed with a number of questions.
I recently picked up a used Moto X from Craiglist and the guy claimed it is an unlocked T-Mobile version with an already unlocked bootloader. The whole point of this purchase was so I could experiment and learn more about what goes on with phones.
How can I verify that the guy is really telling me the truth about the version? I used imei.info and it told me it was an XT1055. However, swappa.com told me it was XT1053. I saw on some post here that XT1053 matches the T-Mobile/Dev version which would make sense with what the Craigslist guy told me. Both sites claim it is not 100% accurate so how else can I verify actual version? There is no logo of T-Mobile on the back of this device. Is there some serial number lookup database?
This led me to wonder if it's possible to flash different software variants onto this phone? In theory, could I download the images for an ATT variant and flash them onto my supposed T-Mobile version? Apart from the potential of overwriting the unlocked bootloader and preventing me from downgrading versions (from the other posts that I've read here), would the phone work assuming my SIM/network is ATT? The IMEI would remain the same, right? How much of the underlying hardware configuration is tied to version of the software that I flash onto the phone?
Could the guy have purchased this phone to whatever carrier XT1055 matches to - rooted or unlocked the bootloader, and flashed the XT1053 images?
At this point, using mfastboot I was able to verify that the bootloader was unlocked but went ahead and performed the same process on Moto's site anyway (and this seemed to work - did this for experimenting). I then downloaded TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC to reflash onto the phone. This whole process might have seemed redundant but I just wanted to ensure the used phone that I had purchased matched a stock set of images (minus the unlocked bootloader).
Thanks! Apologies in advance if there was another similar post - I tried searching but maybe not hard enough.
Click to expand...
Click to collapse
If you are using a SIM in it, it is NOT an XT1055 - those are sim-locked.
You probably have a real XT1053.
There is absolutely NO REASON to ever flash another carrier's firmware. It's dangerous and you gain nothing. Stick with your proper firmware - you can already use it on any carrier you wish.
P.S. Look on the bottom of the back of the phone. In TINY print should be the model number...

Thanks! I did not notice that tiny print - it seems to fade out with the glare in normal lighting conditions.
samwathegreat said:
If you are using a SIM in it, it is NOT an XT1055 - those are sim-locked.
You probably have a real XT1053.
There is absolutely NO REASON to ever flash another carrier's firmware. It's dangerous and you gain nothing. Stick with your proper firmware - you can already use it on any carrier you wish.
P.S. Look on the bottom of the back of the phone. In TINY print should be the model number...
Click to expand...
Click to collapse

klxavier said:
Thanks! I did not notice that tiny print - it seems to fade out with the glare in normal lighting conditions.
Click to expand...
Click to collapse
Same, I did not notice it on a white back. Also if it says Developer Edition on the back then it is most likely a 1053 also.

[Q] XT1056 (SPRINT) GSM flashable zip to custom roms

Hi . Not so long ago i've bought a Moto X device, locked with Sprint. I've unlocked the gsm to all carriers, but flashing a custom rom i saw that my Moto X didn't see the sim card.
I've learnd that all custom roms just doesn't have apk's wich are responsible for gsm signal and these apk's are in the open source of the kernel.
My question is if someone can make a flashable zip to AOSP/CM roms with these apk. If someone helps me, i'll make a good donation and i think thatsuch a thing will be very helpful to xt1056 owners. Thank you.

vetalko000 said:
Hi . Not so long ago i've bought a Moto X device, locked with Sprint. I've unlocked the gsm to all carriers, but flashing a custom rom i saw that my Moto X didn't see the sim card.
I've learnd that all custom roms just doesn't have apk's wich are responsible for gsm signal and these apk's are in the open source of the kernel.
My question is if someone can make a flashable zip to AOSP/CM roms with these apk. If someone helps me, i'll make a good donation and i think thatsuch a thing will be very helpful to xt1056 owners. Thank you.
Click to expand...
Click to collapse
When you use a custom rom, you have to set the config carrier.....
fastboot oem config carrier T-MOB010
^should do the trick. If not, try:
fastboot oem config carrier 11111111

Ok. I'll try.

samwathegreat said:
When you use a custom rom, you have to set the config carrier.....
fastboot oem config carrier T-MOB010
^should do the trick. If not, try:
fastboot oem config carrier 11111111
Click to expand...
Click to collapse
This doesn`t work. Any other thoughts?

vetalko000 said:
This doesn`t work. Any other thoughts?
Click to expand...
Click to collapse
Find the correct carrier ID for *your carrier* and program it with fastboot:
fastboot oem config carrier YOUR_ID_HERE
(see this post: http://forum.xda-developers.com/showpost.php?p=54468353&postcount=126 )

What i gonna do, when there is no my carrier? I am from ukraine.

vetalko000 said:
What i gonna do, when there is no my carrier? I am from ukraine.
Click to expand...
Click to collapse
Your carrier is not on this list?
http://forum.xda-developers.com/showthread.php?t=2445289
fastboot oem config carrier 11111111 should have worked....
If not, stick with stock Sprint firmware.

Error when i try to unlock my Moto x

Hi. I have the Moto X xt1058 (AT&T) and I bought the code on 2 different pages. In one them they gave me 2 codes to try and when I tried to put the codes the phone showed an error to unlock the network and then in the other page they gave me the same 2 codes. I've reseted the phone and it keeps showing me the same error when I try to unlock it.
I have android system 4.4.4 stock.

Taling said:
Hi. I have the Moto X xt1058 (AT&T) and I bought the code on 2 different pages. In one them they gave me 2 codes to try and when I tried to put the codes the phone showed an error to unlock the network and then in the other page they gave me the same 2 codes. I've reseted the phone and it keeps showing me the same error when I try to unlock it.
I have android system 4.4.4 stock.
Click to expand...
Click to collapse
I thought AT&T unlocked phones if you requested it due to that law that was put into effect for global capable phones?

I don't know how to do that process and I have another moto X from AT&T which I unlocked by buying the unlock code on a page.

very often its not working because custom ROM or custom baseband flashed, so please make sure that your phone is completely stock

its completely i updated by OTA to 4.4.4

First, you can try -> https://www.att.com/deviceunlock/?#/ it appears by the conditions that even NON-ATT customers can request the SIM/Carrier unlock code now.
Also, there was discussion about some SIM or Carrier Unlock codes not working on devices with a particular series of IMEI numbers... I don't know the specifics because I don't have an ATT X. See -> http://forum.xda-developers.com/moto-x/general/sim-unlock-moto-x-gens-t3011662 and start around Post #21 for more details, and more importantly post #31 of that thread for a possible resolution.
And be careful, I'm not sure how many attempts you get to enter the SIM/Carrier unlock code.

i try here https://www.att.com/deviceunlock/?#/ but dont work cuz said me: "Error: We found no record of the IMEI Number you entered. Check your device's 15-digit IMEI Number by dialing *#06# (errorCode.ULP2003)"
i bought another unlock code on ebay... i will try again

Taling said:
i try here https://www.att.com/deviceunlock/?#/ but dont work cuz said me: "Error: We found no record of the IMEI Number you entered. Check your device's 15-digit IMEI Number by dialing *#06# (errorCode.ULP2003)"
i bought another unlock code on ebay... i will try again
Click to expand...
Click to collapse
What are the first 5 digits of the IMEI? Is it 35321? If so, did you see -> http://forum.xda-developers.com/showpost.php?p=60680211&postcount=31

Yes, is 35321 but i have other Moto X start 35321 and i can unlock, but this one i cant do it....

Taling said:
Yes, is 35321 but i have other Moto X start 35321 and i can unlock, but this one i cant do it....
Click to expand...
Click to collapse
And that is why I pointed you to that post... it is another forum member explaining the exact situation you are having, and how he resolved it. (FOR FREE)
Its worth a try... if you would only take a few minutes to read the discussion, and that post.

Saythis said:
I thought AT&T unlocked phones if you requested it due to that law that was put into effect for global capable phones?
Click to expand...
Click to collapse
That's SIM unlock, not bootloader.
There's no official support from anyone on either side, AT&T or Motorola, for unlocking the bootloader on the XT1058. In fact if you call them and ask, they'll just tell you "no".
Furthermore, even senior developers for the platform like jcase have said that unlocking the bootloader on the XT1058 running KitKat 4.4.4 is more-or-less impossible (at the moment).

DarkWolffe said:
That's SIM unlock, not bootloader.
There's no official support from anyone on either side, AT&T or Motorola, for unlocking the bootloader on the XT1058. In fact if you call them and ask, they'll just tell you "no".
Furthermore, even senior developers for the platform like jcase have said that unlocking the bootloader on the XT1058 running KitKat 4.4.4 is more-or-less impossible (at the moment).
Click to expand...
Click to collapse
The OP was asking about SIM Unlocking (or carrier unlocking)... notice the BOLD/Italic I added to the following quote...
Taling said:
Hi. I have the Moto X xt1058 (AT&T) and I bought the code on 2 different pages. In one them they gave me 2 codes to try and when I tried to put the codes the phone showed an error to unlock the network and then in the other page they gave me the same 2 codes. I've reseted the phone and it keeps showing me the same error when I try to unlock it.
Click to expand...
Click to collapse

Yes i order another unlock code and all web page send me the sames code that i used :l

Taling said:
Yes i order another unlock code and all web page send me the sames code that i used :l
Click to expand...
Click to collapse
PLEASE READ -> http://forum.xda-developers.com/showpost.php?p=60680211&postcount=31 and follow what is described there (email to the address listed)... Make sure you ask for SIM Unlock aka Network Unlock... and don't just say "unlock"
Let us know how you make out.

i read that and i send a email to [email protected] and they said me cant help me :l

Taling said:
i read that and i send a email to [email protected] and they said me cant help me :l
Click to expand...
Click to collapse
Was your subject line ATTN: Donald Hicks - Global Leader Service Operations as stated in that post?
Did HE reply? or someone from Moto support? Did they explain why they can't help?

This:
Hello Starling,
Thank you for contacting Motorola. Unfortunately, as SIM issues are largely carrier-related, the spectrum of assistance we have to offer on the manufacturer's side of things is rather limited. When trying to use the subsidy unlock code to unlock your device, are you trying this with the new SIM card or the old one in your device? You should input the subsidy unlock code with the new SIM card if you have not already done so and try it again. If you have reset the device and you're still experiencing the issue, you will likely need to contact AT&T about this issue and they can look into things more fully on their end. The IMEI of your device shows as valid in our system, so if AT&T is having an issue with it, that would be on their end and you would also need to contact them about that. If you would be more comfortable with it, either a member of our tech support team or myself could reach out to you and make a conference call with AT&T to get this resolved for you as well.
Please let me know how you would like to proceed and I will assist you to the best of my ability.
Thank you for choosing Motorola and have a great day!
Cas
Motorola Mobility
Click to expand...
Click to collapse

Taling said:
This:
Click to expand...
Click to collapse
I would take them up on their offer in the final sentence of the first paragraph... To have a member of Moto support reach out to you and make a conference call with AT&T to get this resolved.

KidJoe said:
The OP was asking about SIM Unlocking (or carrier unlocking)... notice the BOLD/Italic I added to the following quote...
Click to expand...
Click to collapse
Whoops! Sorry about that, I guess my eyes skipped over that bit.
In that case, yeah! You should be able to grab it from AT&T's website or by calling in and asking about it.

I spoke with ATT and Motorola Agent and NOTHING.!
Motorola only help me to contact with ATT and they said me... "We cant help you with that, sorry"

Expanding SamDunk bootloader unlock exploit to AT&T Galaxy S5?

I looked into using SamDunk for unlocking the bootloader for my AT&T galaxy s5 but noticed that the code posted on the git was Verizon-specific (in that the bits it writes over in the cid of the phone is verizon-specific). This makes it to where running the code does not unlock the bootloader on a AT&T galaxy s5.
I wrote some python code parsing my original cid and the cid resulting from the current exploit code and noticed that the only difference pertained to the product's serial number (bits 47-16 of the cid). Even then, only certain bits within the product serial number are different. I suspect that some bits within product serial pertain to carrier, and some bits pertain to the bootloader, but I could be wrong.
My hunch is that if I can figure out which bits from the original cid's product serial number correspond to developer bootloader access then I may be able to modify the SamDunk code to allow for unlocking AT&T bootloaders. Or provide some method of calculating a dev bootloader cid from an original.
Has anyone else looked into this, and is this worth pursuing?
edit: looking further through SamDunk code. It appears that there is a dev signature associated with the cid (?) that gets written to aboot. Not sure if this is different between phones... If so then experimenting with only the cid may be futile.
product serial numbers are different for the first 12 bits then bits 25-32. I could post a link to my git if anyone is interested in experimenting with their cids

_ibis said:
I looked into using SamDunk for unlocking the bootloader for my AT&T galaxy s5 but noticed that the code posted on the git was Verizon-specific (in that the bits it writes over in the cid of the phone is verizon-specific). This makes it to where running the code does not unlock the bootloader on a AT&T galaxy s5.
I wrote some python code parsing my original cid and the cid resulting from the current exploit code and noticed that the only difference pertained to the product's serial number (bits 47-16 of the cid). Even then, only certain bits within the product serial number are different. I suspect that some bits within product serial pertain to carrier, and some bits pertain to the bootloader, but I could be wrong.
My hunch is that if I can figure out which bits from the original cid's product serial number correspond to developer bootloader access then I may be able to modify the SamDunk code to allow for unlocking AT&T bootloaders. Or provide some method of calculating a dev bootloader cid from an original.
Has anyone else looked into this, and is this worth pursuing?
edit: looking further through SamDunk code. It appears that there is a dev signature associated with the cid (?) that gets written to aboot. Not sure if this is different between phones... If so then experimenting with only the cid may be futile.
product serial numbers are different for the first 12 bits then bits 25-32. I could post a link to my git if anyone is interested in experimenting with their cids
Click to expand...
Click to collapse
I wouldn't mind taking a look.

NavSad said:
I wouldn't mind taking a look.
Click to expand...
Click to collapse
Thanks man, I appreciate all the help I can get.
I read further into the Verizon S5 bootloader unlock thread and it appears that only changing the cid may not work. If I remember correctly (looked at it yesterday) the cid is hashed/compared to the aboot somehow to determine whether its a developer edition or not. If we could get a regular cid/aboot and compare it to the verizon regular cid/aboot, then cross compare to the verizon dev edition cid/aboot then we may have a shot at possibly re-creating a at&t dev edition cid/aboot

_ibis said:
Thanks man, I appreciate all the help I can get.
I read further into the Verizon S5 bootloader unlock thread and it appears that only changing the cid may not work. If I remember correctly (looked at it yesterday) the cid is hashed/compared to the aboot somehow to determine whether its a developer edition or not. If we could get a regular cid/aboot and compare it to the verizon regular cid/aboot, then cross compare to the verizon dev edition cid/aboot then we may have a shot at possibly re-creating a at&t dev edition cid/aboot
Click to expand...
Click to collapse
If the bootloader uses SHA1 it may be easier.

Meanwhile us CID 11s over here just watching you guys from the distance..lol

AptLogic said:
Meanwhile us CID 11s over here just watching you guys from the distance..lol
Click to expand...
Click to collapse
I'm CID 11 too.

NavSad said:
I'm CID 11 too.
Click to expand...
Click to collapse
Oh okay lol.. really wish we could unlock all of the S5 bootloaders instead of just CID 15... what if we try doing like MultiROM with the "no-hardboot" thing like they do on HTC devices? We wouldn't need to patch the Kernel so we'd be able to flash other ROMs.

I know we have Odin mode instead of fastboot and we can not do the "OEM Unlock" in the Developer Options as it does not show up in there. I found this thread (https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/) on how to discover hidden fastboot commands.
So I followed the instructions there to extract the aboot.img (bootloader) and then "read" the contents of that to see what fastboot commands are available. To my surprise, it has "oem unlock" listed and a few other oem options, see attached image. Although, back to the beginning of my post, we can not fastboot in.
I would assume we could unlock the bootloader via fastboot commands if we only had a way in for it. I am not that experienced with Odin but I think that is only to flash images. I spent most of this weekend searching for any way to alternately try to fastboot in or use Odin but came up with nothing feasible. I used ADB to reboot the phone into all modes and tried doing "fastboot devices" in all modes but it just came back with nothing.
I just wanted to post this in the case of being useful in our attempt to unlock the bootloader.

What do you mean by a way in ?

There is no way, that I know of, to put the s5 in fastboot mode. I was thinking that if there is a way to boot to fastboot, or at least have the phone listed as a fastboot device in ADB, we could possibly run the oem unlock command.

Ok that's what I thought u had meant .... I used to have a few HTC devices I believe was the my touch 4g I'm thinking about ...Anyway some of the roms I had to use ADB and fastboot to flash a kernal sometimes ADB wouldn't pick up device to communicate with fastboot someone had found that by installing PDA.net (I think this was name of app for Windows) it enabled ADB to see the device at any rate .... I no it's a long shot but something to look into if your bored sometime lol I'm not sure why or how it worked or if wouldn't help us at all but I no for a fact it worked on a HTC device so felt was worth mentioning

I'll have a look at that when I get a chance. Anything is worth mentioning as you never know what little piece completes the puzzle!

sorry guys, been out of it for the last two weeks. Projects got crazy but should be able to begin working on this again soon.

I'm fairly certain Thier is still a bounty on this .... I no I pledged 100 bux to whoever unlocks my bootloader and saves me from having to buy a new phone lol but been waiting damn near 4 years not gonna start holding my breath now lol

Towelroot gives kernel memory access, downgrade, use kexec.
This is the easiest way and only one that is guaranteed to work since all exploits have already been made.

Guicrith said:
Towelroot gives kernel memory access, downgrade, use kexec.
This is the easiest way and only one that is guaranteed to work since all exploits have already been made.
Click to expand...
Click to collapse
If, of course, we could get kexec to WORK. Any modification of the Kernel breaks the chain of trust and the phone goes into a bootloop.

We dont need to modify the kernel, TowelRoot would write kexec from a file(/system/userlandbootloader.img) into the kernel after boot, then the kernel would boot a new kernel from /system/oskernel.img (which is writable on rooted 4.4-5.0)
The only kernel being modified is the one running in ram and that is deleted and replaced every reboot so trust chain is never broken.

Guicrith said:
We dont need to modify the kernel, TowelRoot would write kexec from a file into the kernel after boot, then the kernel would boot a new kernel from /system/oskernel.img (which is writable on rooted 4.4-5.0)
The only kernel being mdifyed is the one running in ram and that is deleted and replaced every reboot so trust chain is never broken.
Click to expand...
Click to collapse
But for everything to work correctly we need to be able to hardboot to the new kernel, so we need to patch the existing one to support it.

Why?
If you have kernel access you can just set all values to there boot time default.(unless there is hardware locked values like the gameboy color bootloader)
Clear the mmu mappings.
memset((void*)0x00000000, 0x00, sizeof(systemram));
Now it is in a pre boot state.
If that does not work triggering a crash that does not reload the kernel from rom but hardboots the system may work too.

Guicrith said:
Why?
If you have kernel access you can just set all values to there boot time default.(unless there is hardware locked values like the gameboy color bootloader)
Clear the mmu mappings.
memset((void*)0x00000000, 0x00, sizeof(systemram));
Now it is in a pre boot state.
If that does not work triggering a crash that does not reload the kernel from rom but hardboots the system may work too.
Click to expand...
Click to collapse
If we can code this and get consistent successful results we'd basically have a workaround for most locked BL devices to boot a custom ROM.
Of course the only theoretical hurdle left would be to actually code something like this.

(US) T-Mobile version G7+ may come

https://www.xda-developers.com/motorola-moto-g7-plus-t-mobile/
It has NFC and B71 which G7 doesn't have.
Hopefully bootloader will be unlockable. If so, I may get one and paid in full and have it SIM unlocked, and flash RETAIL ROM

Any update on this? Been holding out on upgrading for this if it's true

If this is right it could be the revvl 3 or 3 plus as product sku is tmo revvl this is from wifi alliance

It's the g7 plus and g7 play https://www.tmonews.com/2019/07/t-mobile-revvlry-official-specs-price/

Can we root it using g7 plus method and unlock bootloader same way I currently have the phone

You can try to get bootloader unlock code it won't hurt nothing but as far as rooting I don't know but should be the same

krazy_smokezalot said:
Can we root it using g7 plus method and unlock bootloader same way I currently have the phone
Click to expand...
Click to collapse
If you can unlock the bootloader, then rooting will be the easy part as you can usually just flash Magisk (or create a patched boot.img in Magisk Manager and flash the patched boot.img). TWRP may even work too, assuming T-Mo didn't heavily modify the underlying software and kernel.
The only question is gonna be unlocking the bootloader as it's not technically branded a Moto device (although is allegedly has the same codename). Moto may not ship a bootloader code to you, you may need to go thru T-Mobile in some way first.

Jleeblanch said:
If you can unlock the bootloader, then rooting will be the easy part as you can usually just flash Magisk (or create a patched boot.img in Magisk Manager and flash the patched boot.img). TWRP may even work too, assuming T-Mo didn't heavily modify the underlying software and kernel.
The only question is gonna be unlocking the bootloader as it's not technically branded a Moto device (although is allegedly has the same codename). Moto may not ship a bootloader code to you, you may need to go thru T-Mobile in some way first.
Click to expand...
Click to collapse
But T-MOBILE don't offer bootloader unlock I work for them. Well just gonna try cause it's given the code name lake on cpu z and the manufacturer is Motorola

krazy_smokezalot said:
But T-MOBILE don't offer bootloader unlock I work for them. Well just gonna try cause it's given the code name lake on cpu z and the manufacturer is Motorola
Click to expand...
Click to collapse
Knowing they (as in T-Mo) doesn't offer codes, which I figured they didn't, then I'd at least try to paste your unlock code on Moto's site. Worst that'll happen is a message will pop up saying you device doesn't qualify.

t mobile g7 plus bootloader unlock
i can confirm that the bootloader for the t mobile moto g7 plus is locked and could not get a unlock from Motorola website it probably has to be paid for to get a unlock. i am unable to confirm at this time if you can get a unlock i got mine on JOD jump on demand. if someone out there gets one paid for and trys for a bootloader unlock please confirm if you can or not after it is paid for. i think you could but i cant confirm that at this time please any ones feed back would be a big help we should all work to gather on this i hope for a bootloader unlock or a work around if someone figures something out but as fas as i know at this time if you owe on 1 there is no boot loader unlock but just maybe the possibility after it is paid i am not shure if you would have to go though t mobile first to get a unlock thanks and anyone's feed back would be very much appreciated.
Also this is probably the same moto g7 build lake as the one off there website but with t mobile branding and a locked down bootloader so twrp and magisk root should work if you can get a bootloader unlock. if someone does please confirm here if it does work or not thanks and i welcome your feedback from anyone.

REVVLRY+ is indeed G7 plus

Jimhackthorn said:
i can confirm that the bootloader for the t mobile moto g7 plus is locked and could not get a unlock from Motorola website it probably has to be paid for to get a unlock. i am unable to confirm at this time if you can get a unlock i got mine on JOD jump on demand. if someone out there gets one paid for and trys for a bootloader unlock please confirm if you can or not after it is paid for. i think you could but i cant confirm that at this time please any ones feed back would be a big help we should0 all work to gather on this i hope for a bootloader unlock or a work around if someone figures something out but as fas as i know at this time if you owe on 1 there is no boot loader unlock but just maybe the possibility after it is paid i am not shure if you would have to go though t mobile first to get a unlock thanks and anyone's feed back would be very much appreciated.
Also this is probably the same moto g7 build lake as the one off there website but with t mobile branding and a locked down bootloader so twrp and magisk root should work if you can get a bootloader unlock. if someone does please confirm here if it does work or not thanks and i welcome your feedback from anyone.
Click to expand...
Click to collapse
Ok I'll try it cause it got it for free and it's paid off. Got it from my job as a gift. So I'll definitely check it out then I'm even more interested. But I kinda doubt it cause the bootloader has the name revvl in it in CPU Z. Bootloader goes by MBM-3.0lake_revvl-43c7c77-190517

Ok so no I tried fastboot oem unlock and nothing happens on the phone anyone else has any idea they want me to try. I'm able to check oem unlock but in fastboot the command oem unlock does nothing on the phone

unlock instructions
krazy_smokezalot said:
Ok so no I tried fastboot oem unlock and nothing happens on the phone anyone else has any idea they want me to try. I'm able to check oem unlock but in fastboot the command oem unlock does nothing on the phone
Click to expand...
Click to collapse
That's because you got to get a unlock key from Motorola. you will first need to make a account with Motorola https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
here is your instructions on how to get a key
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android ADB (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000 EXAMPLE
Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page.
then get the key put in your email address and you will get UNIQUE_KEY
then in adb put in fastboot oem unlock ((UNIQUE_KEY)) here
then fastboot reboot
If yours is paid for please let me know if it works mine is not paid for.

Jimhackthorn said:
That's because you got to get a unlock key from Motorola. you will first need to make a account with Motorola https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
here is your instructions on how to get a key
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android ADB (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000 EXAMPLE
Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page.
then get the key put in your email address and you will get UNIQUE_KEY
then in adb put in fastboot oem unlock ((UNIQUE_KEY)) here
then fastboot reboot
If yours is paid for please let me know if it works mine is not paid for.
Click to expand...
Click to collapse
Cool thanks for this I'll follow this instructions to unlock bootloader. I'll post back my findings

krazy_smokezalot said:
Cool thanks for this I'll follow this instructions to unlock bootloader. I'll post back my findings
Click to expand...
Click to collapse
This is a common method to unlock Motorola smartphone bootloader.
Hopefully you will be lucky to get the code, but you may wait up to 2 weeks after initial release.

I can confirm that Motorola will give you the unlock code.

Findings
UNLOCKING AND LOCKING BOOTLOADER WILL WIPE YOUR DEVICE> BACKUP PERSONAL DATA IF YOU WANT TO KEEP IT.
I unlocked the bootloader and flashed the moto G7 plus RETAIL firmware. Everything worked fine except google pay, and verity being disabled.
Installing TWRP would always give me a recovery boot loop, so I stopped trying, instead just booting into TWRP with fastboot.
I cannot get verity enabled, even after flashing stock and locking the bootloader, so that means no Google Pay, no Google Fi, no whatever else requires verity.
Looking at
Code:
fastboot getvar all
Shows a flag that verity is disabled and another flag that warranty is void, even after flashing stock.
The stock firmware I found in a firmware repo, because I failed to do a full backup of my system (I only backed up boot, system, and data).
Would anyone be willing to unlock their bootloader, boot into TWRP, do a full backup, and share it, to see if I can get back to stock with verity enabled? I'd love Google Pay back.

BanterJSmoke said:
I can confirm that Motorola will give you the unlock code.
Click to expand...
Click to collapse
Wow!!!
This is HUGE!!!
Pay in full to get SIM unlocked first followed by bootloader unlock and flash RETAIL ROM and become G7 Plus
CDMA support is unknown

mingkee said:
Wow!!!
This is HUGE!!!
Pay in full to get SIM unlocked first followed by bootloader unlock and flash RETAIL ROM and become G7 Plus
CDMA support is unknown
Click to expand...
Click to collapse
Except it's nearly $100 less expensive to just buy an unlocked g7+