Database Develop

[Q] Fastboot failure help needed

I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):

You should check out the 'Chinese Middleman' thread. If you get the bootloader unlocked you should be able to fix anything.

I can't unlock the bootloader since this is not a Dev edition. Unless something has changed, I'll check it.

You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk

shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Even though it's not a Dev edition?

Yes you should be able too.
Sent from my XT1053 using Tapatalk

danman421 said:
Even though it's not a Dev edition?
Click to expand...
Click to collapse
All XT1053s can be unlocked, yes. Additionally, if you follow my advice, you don't NEED to unlock. If one of the commands fails, simply skip to the next as I previously advised, and TRY flashing with RSD Lite after you have run the commands I listed.
If you want to check and make sure fastboot is working, type:
fastboot devices
if you see your phone and it's serial number listed, you fastboot IS properly communicating with your phone.
You do not need to unlock your BL to do any of this...but if you are interested in ROOTING, you will need to.

All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?

shamelin73 said:
You should be able to unlock the boot loader but will not have warranty.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.

danman421 said:
All I really want to do is make it so my phone can take the update and any future updates. What do you mean as you previously stated?
Click to expand...
Click to collapse
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
danman421 said:
I tried this as I did before and I get "your device does not qualify for bootloader unlocking". All I need to know is how to fix this from someone.
Click to expand...
Click to collapse
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.

samwathegreat said:
I confused you with a member I had helped previously - sorry. Please disregard the "previously stated" comment.
It does NOT require unlocking the bootloader to flash your carrier's correct ROM. Simply follow the instructions in the "Return to 100% Stock" thread to flash the XT1053 ROM, and you'll be able to take all future updates.
If you DO unlock the bootloader, flash custom recovery, and root your device, you will have to un-do any modifications made before EVERY OTA. If you don't care about root, don't worry about unlocking.
Additionally, if you DO want to unlock, you could try a different browser and make sure you are inputting the unlock data correctly. It is recommended that you copy the unlock data from the command prompt to notepad, remove all spaces and bootloader messages (you ONLY want the code - as one complete string), then copy from notepad into the Unlock website.
And finally, keep in mind that unless you unlock your BL, you will not be able to root and disable write-protect once you update to the latest version.
The real problem here is that you use an "Exploit" to root your device previously. Now you need to return to full stock to restore your partitions to their factory state.
Simply follow the instructions in the Return to stock thread (in general sub-forum), and be sure to flash the LATEST version for your carrier. It should be 4.4.3.
Good Luck.
Click to expand...
Click to collapse
So if I am reading this correctly, there is no way to keep all of my data and take the update?

danman421 said:
So if I am reading this correctly, there is no way to keep all of my data and take the update?
Click to expand...
Click to collapse
You can attempt to, by either editing the XML in the SBF and removing the line that says "erase userdata", or by skipping the erase userdata if you use the manual method, but either way CAN mess everything up.
You used an EXPLOIT previously. Any time you use an exploit, you should -expect- to have to wipe everything and re-install from scratch if you want to get back to stock in order to be able to take updates. Keep this in mind if you use any exploits in the future.

Hi! This hasn't seemed to spelled out yet..... But many Moto x's can be unlocked, not just dev editions. However, you stated in the opening post that you have a Verizon Non dev, which can not be unlocked. Only way is to pay the "China middleman" (See thread in general with that name).
And personally.... I would stay on 4.2.2 and do the Slapmymoto method to get root and write protection disabled. That is the best root scenario, aside from unlocking the bootloader.
If you update to 4.4.2 or higher, you will have write protection enabled always, and no root, or sorta root with towelroot and pie. But that will limit what you can do.
See the How do I root my phone sticky thread in general for your options.

I should have posted earlier. I ran RSDLite and put the newest version on. I am unrooted. My Moto X is a Sept '13 version the the middleman probably wont work anyways. Its not worth it with this phone, im tired of the rooting, I guess im at that point in my life... Thanks for all your help though guys!

danman421 said:
I am running a Verizon Moto X still on 4.2.2. I am rooted. This is NOT the Dev edition. I have plenty of experience with rooting/flashing these phones so back when I first got it the directions on rooting/flashing roms was VERY vague. No one specified you needed the Dev edition to unlock the boot loader. Well I think this came from at one point when I tried to flash TWRP (maybe). Either way, I want to take the OTA update and cannot. Does anyone know how to fix this without doing the RSD, reflash stock method? Here is a picture of what it looks like (thanks for your help in advance):
Click to expand...
Click to collapse
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.

You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.

KidJoe said:
Pardon my jumping in here late but..
I see a big issue here.
Based on that screen shot, you have boot loader 30.B4, that is NOT the bootloader that comes wtih 4.2.2. Did you mean to type 4.4.2? or do you really have 4.2.2 on there?
If you really had 4.2.2 on your phone with a 30.B4 bootloader, then you had 4.4.2 on there at one point, and downgraded!! You need to be REALLY CAREFUL or you will brick your phone.
Click to expand...
Click to collapse
Good catch! ?
OP... Perhaps full disclosure of what you have done on the phone would help.
Or is that how it was?
If it's been downgraded to 4.2.2 after being on 4.4.2... As said above.... You could brick now... Especially if you OTA.
I'd tread lightly at this point.

danman421 said:
You are correct, I was on 4.4.2. My wife's S4 that I just upgraded was on 4.2.2. Sorry for the confusion.
Click to expand...
Click to collapse
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.

Yes, that was a good catch. What I did was RSD Lite to 4.4.4 now which reset all my data.

KidJoe said:
so based on post # 14 of this post... it appears you are all good now? is that the case? Or do you still need help?
Oh, and if your bootloader is locked (Verizon non-DE), you can't get code from China Middle man, and you are on 4.4.2, you could try TowelPieRoot for rooting, but write protection is enabled so it will be kind of limited (compared to SlapMyMoto/MotoWPNoMO or if you had an unlocked bootloader), and there is no root for 4.4.4.
Click to expand...
Click to collapse
Correct, I do not need help anymore but thank you.

Marshmallow MCG24 unlock bootloader root etc?

So I bought the phone just now. Paid quite a lot because they don't exist in my country , but I've wanted it since it got out, and it's in like brand new condition so ehhh, why not I said..
Just checked and phone is on Marshmallow 24.81.5quark_verzion.verzion.enUS
Tried Kingroot and sunshine to at least achieve temproot , they both failed.
What are my options right now here?
Thanks!

No unlock options right now if you are on stock 6.0.1 with a locked bootloader.

ChazzMatt said:
No unlock options right now if you are on stock 6.0.1 with a locked bootloader.
Click to expand...
Click to collapse
Thanks for reply! I guess I'll just live with it. Iphone in motorola's body lol. But for discussions sake, any way to downgrade? I know flashing bootloader triggers the "fuse" but I was succesfull with some weird bootloader downgrades in the past wtih 201M (Japanese softbank version of Razr M) and IS12M (JP KDDI version of Droid Razr).
Only problem is, this phone is way to expensive for me to experiment..

Ej?iSixo said:
Thanks for reply! I guess I'll just live with it. Iphone in motorola's body lol. But for discussions sake, any way to downgrade? I know flashing bootloader triggers the "fuse" but I was successful with some weird bootloader downgrades in the past wtih 201M (Japanese softbank version of Razr M) and IS12M (JP KDDI version of Droid Razr).
Only problem is, this phone is way to expensive for me to experiment..
Click to expand...
Click to collapse
Hmmmm... then you were very lucky because gospel around here is you can never downgrade the Motorola bootloader. If you could downgrade bootloader, then everyone would go back to version where Sunshine worked! First Sunshine worked on Lollipop SU4TL-44 (November 2015), then everyone who procrastinated rushed to take SU4TL-49 (May 2016), hoping it was Marshmallow. Nope, it was just a Verizon "security" update to stop Sunshine from working. They had SIX MONTHS to unlock their bootloader and they didn't do it! Then everyone complained and said if only Sunshine worked on "49", they wouldn't procrastinate anymore. BOOM. A few months later (july 2016) Sunshine found another exploit and it works also on Lollipop "49".
But we are STILL seeing people now taking the Marshmallow OTA (November 2016) without unlocking bootloader first. Not you, you said you bought it with it already installed...
One of the Sunshine team members said he briefly glanced at the 6.0.1 OTA and it might not be impossible to unlock the bootloader. But no promises and no ETA. I don't think this phone is a high priority anymore. This is now a 2-year old phone. Still GREAT, but other newer phones get attention. There's been Sunshine for it since November 2015 and most everyone who wants it has had a chance to get it.

ChazzMatt said:
Hmmmm... then you were very lucky because gospel around here is you can never downgrade the Motorola bootloader. If you could downgrade bootloader, then everyone would go back to version where Sunshine worked! First Sunshine worked on Lollipop SU4TL-44 (November 2015), then everyone who procrastinated rushed to take SU4TL-49 (May 2016), hoping it was Marshmallow. Nope, it was just a Verizon "security" update to stop Sunshine from working. They had SIX MONTHS to unlock their bootloader and they didn't do it! Then everyone complained and said if only Sunshine worked on "49", they wouldn't procrastinate anymore. BOOM. A few months later (july 2016) Sunshine found another exploit and it works also on Lollipop "49".
But we are STILL seeing people now taking the Marshmallow OTA (November 2016) without unlocking bootloader first. Not you, you said you bought it with it already installed...
One of the Sunshine team members said he briefly glanced at the 6.0.1 OTA and it might not be impossible to unlock the bootloader. But no promises and no ETA. I don't think this phone is a high priority anymore. This is now a 2-year old phone. Still GREAT, but other newer phones get attention. There's been Sunshine for it since November 2015 and most everyone who wants it has had a chance to get it.
Click to expand...
Click to collapse
Yeah I read whole how to unlock bootloader thread, from 1st to last page but havent' seen anything marshmallow specific so I opened this topic..
Yeah , I was also surprised, but I spent around 1 month working on it , and it was only working with specific firmwares (fastboot files).
Yeah I wish I checked little more about that issue , I would check phones OS and probably not buy when I see it's MM.. Oh well, no going back now.. Thought that verzion's control freak behavior stopped by the time of droid turbo( used some verzion motorola phones in the past) especially when google bought motorola.
I hope people don't see this phone as outdated, because there is no way it can be called that. Many people including myself figured it like a replacement for nexus , and I think it deserves at least root exploit..
Also asked in Sunshines thread about support for marshmallow , got rather unclear response:
Me:Will there be support for droid turbo on marshmallow? Just purchased the phone, didn't know unlocking bl was possible only on lolli... Thanks
jcase: Known at this point,
EDIT: damn I write yeah a lot lol. P.s if mods want to delete topic because it's useless, feel free. Thanks!
EDIT 2: By checking system updates looks like phone was updates 3 days ago so 1 day before I bought it .. Arrrghhhh!!!

BTW I just remembered, "old" Droid 's ( xt910 ,xt912 etc) bootloader was never ever unlocked , but there was a way around it. Safestrap recovery by Hashcode , which I'm sure you all know about. The project is scraped because dev is busy , but I really wonder if anything like that is possible on droid turbo. I also wonder how does it work exactly and what gets bypassed.
From users standpoint: you installed apk which then installed recovery that "bypassed" locked bootloader and allowed you to install /load custom roms, kernels , radios , root etc.. You could even install more OS's at same time like on another "partitions".
hm...

EjđiSixo said:
BTW I just remembered, "old" Droid 's ( xt910 ,xt912 etc) bootloader was never ever unlocked , but there was a way around it. Safestrap recovery by Hashcode , which I'm sure you all know about. The project is scraped because dev is busy , but I really wonder if anything like that is possible on droid turbo. I also wonder how does it work exactly and what gets bypassed.
From users standpoint: you installed apk which then installed recovery that "bypassed" locked bootloader and allowed you to install /load custom roms, kernels , radios , root etc.. You could even install more OS's at same time like on another "partitions".
hm...
Click to expand...
Click to collapse
sorry for keeping this post alive, but i really really miss Safestrap when i had the Moto Droid Razr, you could have up to 4 different ROMs installed and it took minutes to swap between them. Man those were the good ole days haha
Edit: added word droid

weaver11b said:
sorry for keeping this post alive, but i really really miss Safestrap when i had the Moto Razr, you could have up to 4 different ROMs installed and it took minutes to swap between them. Man those were the good ole days haha
Click to expand...
Click to collapse
I remember being frustrated about never-unlockable bootloader while using safestrap at same tame and then realised, hey wait! What do I need unlocked bootloader anyway , everything works perfect and functionality is even better than on most modded phones (at the time).
Having something like this on droid turbo would make it a perfect phone in my opinion, and for years to come.. Wonder whats the dev's view on droid turbo on that..
Anyway I was playing a little, all within "safe zones" regarding the downgrading . With litlle modding I could flash bootloader.img from QUARK_VERIZON_5.1_SU4TL-49_cid2_subsidy-DEFAULT_CFC.xml.zip and most of partitions related to bootloader I collected from various locations,all from SU4TL but it's obviously not important..
So basically what I can't flash to downgrade is :
gpt.bin
boot.img
system files (system,img_sparsechunk.0 , 1 , 2 etc).. I will investigate more.
Started finally actually using phone , all bloatware can be disabled, so it's actually pretty ok for now. Phone feels awesome ..

Mods , please delete this topic in purpose of cleaning, I'm gonna open 2 topics regarding downgrading experiment and making SBF of new Marshmallow OTA

New update bootloops my phone, help please!

Hey guys, so my mom was using the Turbo yesterday when she was prompted to an update. Now according to a few searches there was a soak test out or something? Not sure, since I have the Turbo 2. But regardless, she went to apply the update and now that phone won't boot up. It lights up with the M logo screen and then goes to andy where he's got the rotating box in his belly, and underneath it says "Erasing...". I can't get to any of the other options from the screen where you hold Volume Down while powering up. All of the options lead to the same erasing screen. The phone will reboot after two or three minutes and go back to the same thing. Been doing this for hours. I have it sitting on a charger and will take a look at it when I come back from work but I'm wondering how to remedy this? I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use. Not familiar with ADB so if that's the route I have to go, I'd appreciate a write up on how to use it. Willing to install custom firmware if I have to as well. I just need to get the phone working asap. My mom works nights and she is currently phoneless, so this is a safety concern of mine.
Also that screen where you hold Volume Down, it says battery okay and all that but it says the phone software is modified. Not sure why, I know that she completely incapable of doing that. And I didn't modify anything when I had the phone. Not that is matters though, it's out of warranty so Verizon or Moto probably won't be too useful.
Any and all help appreciated. Currently not in the position to buy a new phone so I'd prefer fixing this one up if I can. Thanks!

Xelios029 said:
I am familiar with RSD lite and can use it to flash the phone if I can figure out which files to use.
Click to expand...
Click to collapse
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.

Never, which is why I'm confused why it says software status modified. The sunshine and mofo mods were released after I upgraded to the turbo 2 so I never even had a chance. But thank you though! Really appreciate it, I was scared that some part of the memory had failed or something. My only question from here is how do I get the phone into the mode to required to RSD it? Because even if I select the bootloader option from that screen where you hold volume down while powering up, it goes to that erasing screen no matter what.
EDIT: Got home from work and downloaded all the files. RSD 6.1.5, Motorola Device Manager for the drivers, and the FXZ file. No dice. It won't recognize the device in RSD even though windows is making that sound when a device is connected. No luck on RSDLite 6.2.4 either.
EDIT2: Okay ugh, now I don't know what to do. Turns out RSD didnt detect it because the cable was not directly plugged into the motherboard. Took me a while to figure that out. So I got it detected and I flashed that file you put above and I'm still having the same problem. It reboots once everything is finished flashing and then goes back to the "Erasing..." screen.
EDIT3: SUCCESS!!! Thank you so much! I swear I was thinking I was going to have to replace the phone. Let it sit at the Erasing screen after flashing it for a bit and it eventually rebooted itself and started the Droid splash screen. What a huge relief! Hopefully these updates help with someone else who may run into the same problem.

Glad it worked for you!
And it helped you were persistent.

ChazzMatt said:
Glad it worked for you!
And it helped you were persistent.
Click to expand...
Click to collapse
Thanks again, much appreciated!

ChazzMatt said:
Is the phone pure stock? You've never unlocked the bootloader via Sunshine nor installed TWRP custom recovery?
If so, then this is the full firmware version of the most recent update that you would flash via RSD.
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3569334
It should fix your phone -- but you will not be able to unlock the bootloader and install custom recovery because the update blocks Sunshine. If you had wanted an unlocked bootloader you should have done it before now.
Click to expand...
Click to collapse
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk

KARIM9377 said:
Do you think sunshine will update the unlock bootloader for MCG24.251-5-5[
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
You have to ask them. I don't know. But we've been surprised before by their talent.

ChazzMatt said:
you have to ask them. I don't know. But we've been stories surprised before by their talent.
Click to expand...
Click to collapse
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update

KARIM9377 said:
Yes I did I ask
*@beaups and he told me that they will try if they have time for it
Put I asking for is ? did Verizon black the patch that sunshine can unlock bootloader with it ?
I hope they don't and I hope sunshine will do it and update
Click to expand...
Click to collapse
Every time Sunshine released an update to force unlock the Droid Turbo bootloader, Verizon releases an OTA "security update" to block it.
This next rant is not towards you but to other longtime Droid Turbo owners... (Like anyone who has owned a Droid Turbo for over two months. Anywhere from 2 months - 2 years.)
People just need to UNLOCK their bootloaders before taking any updates. NEVER, NEVER, NEVER take an OTA update. If there's anything worthwhile it will be posted HERE on XDA and you can flash it manually. Just unlock your bootloader and you don't have to worry about Verizon "blocking" Sunshine because your bootloader will already be unlocked!

UNLOCK works... and root.

In case anyone is wondering, the unlock process went smoothly. Usual Motorola process, and the usual "orange" warning screen on bootup.
As for root -- see the X4 root thread
Magisk devs are still working on this device... be patient

I've never had a Moto android phone- what is the usual process? I know that you need to send them info from the bootloader, and they email you an unlock code. Can you re-lock/unlock at will now or does every unlock require a new code?

I have never relocked a Moto phone, but would think the code stays the same as it is device-specific.
The process is just that... Go to the moto unlock site, get your code and unlock via fastboot -- the email from Moto contains the code and step by step instructions if you need them.

gee one said:
I've never had a Moto android phone- what is the usual process? I know that you need to send them info from the bootloader, and they email you an unlock code. Can you re-lock/unlock at will now or does every unlock require a new code?
Click to expand...
Click to collapse
When U get a fresh locked phone the status code is 0 and is locked and official... when u unlock it's bootloader the status codes change from 0 to 3 and when u relock it the status code is 2.. u can't permanently lock it (some legends say we need to change mobo)
no u can use the unlock code which u received by email plenty of time's....that's your permanent unlock code but if u do the same process ie goto moto bootloader page and blabla.. then the code which u received again can be used plenty of time's and the 2nd code will become your perm code and the 1st code won't work again!!

mightysween said:
In case anyone is wondering, the unlock process went smoothly. Usual Motorola process, and the usual "orange" warning screen on bootup.
As for root -- without custom recovery, Magisk was the best bet. But is unable to properly patch boot.img. The good news is that I was able to modify and flash a different boot.img, test it, and then return to stock boot.img (on both A and B partitions) without any trouble. Theoretically, Magisk Beta build is supporting Pixel type A/B partitioning, so perhaps there is hope...
Click to expand...
Click to collapse
Well shiitt. Just picked up a Moto X4 as a replacement for my Moto X Pure. What is your current status with safety net, root, magisk etc????????

SR3TLAW said:
Well shiitt. Just picked up a Moto X4 as a replacement for my Moto X Pure. What is your current status with safety net, root, magisk etc????????
Click to expand...
Click to collapse
Root is fine (except for OTA updates)... pretty much nothing else works

mightysween said:
Root is fine (except for OTA updates)... pretty much nothing else works
Click to expand...
Click to collapse
lol i've seen your around the X4 forums. we're a bit short on support so far ey lol
glad to know someone else is interested

SR3TLAW said:
lol i've seen your around the X4 forums. we're a bit short on support so far ey lol
glad to know someone else is interested
Click to expand...
Click to collapse
I have been on it nearly a month... Hit the dev thread and help with my device tree and TWRP

mightysween said:
I have been on it nearly a month... Hit the dev thread and help with my device tree and TWRP
Click to expand...
Click to collapse
I am no developer but work as a computer network engineer by day (Cisco). This new "slotted" partition scheme is different. Once we are are able to side-load TWRP "temporarily" we should be good. I have a retail version (-1) from best buy sitting new in box downstairs. If there is anything you need from that specfiic unmodified device let me know. I have not unlocked boot loader yet as I see no reason too unless root privileges can be guaranteed; which i know from my last 3 hours of reading you're working your a.s.s off with lol.

Question about root. XT1900-1

I picked up the Best Buy unlocked version. Which I assumed was the Android One version(?) but I'm not seeing anything about it on this phone. Anyways, I'm not familiar with some of the lingo for this phone in the threads, so I'm not sure what to look for compatibility-wise. I came from the S9+ so I have to figure all that out. Is it bootloader unlockable, and rootable? Is it the A1 version? Is there a benefit to changing the firmware to A1(if that's even possible, running 8.1)?
Thanks for all the input.

Android One has the badge or logo on the back. You can use Motorola's website to definitively determine if your phone call be unlocked. Typically, the one from Amazon isn't.

Neffy27 said:
Android One has the badge or logo on the back. You can use Motorola's website to definitively determine if your phone call be unlocked. Typically, the one from Amazon isn't.
Click to expand...
Click to collapse
To be clear, you're talking about the bootloader? The phone itself is the best buy unlocked version. I really would like to flash Android One on it, as long as everything is working correctly.

I don't know of anything else besides "unlock of bootloader".
Just be aware, there's no return from unlock of bootloader. You do that process, safety net is broken and modified flag is tripped. There are no factory signed official images provided by Lenovo. If all steps are followed to a T from these forums, phone will always be functional. You have ways around safety net via Magisk if Google Pay is important to you.

Neffy27 said:
I don't know of anything else besides "unlock of bootloader".
Just be aware, there's no return from unlock of bootloader. You do that process, safety net is broken and modified flag is tripped. There are no factory signed official images provided by Lenovo. If all steps are followed to a T from these forums, phone will always be functional. You have ways around safety net via Magisk if Google Pay is important to you.
Click to expand...
Click to collapse
I meant as in sim unlocked. Do I need the bootloader unlocked in order to root or flash A1? If I unlock it will I still receive updates and function a normal if I keep it stock rom?

I have been trying to find up to date directions to unlock the bootloader on my phone with absolutely no luck. No where does it say a compatible unlock to work with the new 8.1 software. I would love to install A1 on my sim unlocked version of my x4. I can't find an up to date version to root or anything. It's so annoying that I am about to just return this phone and buy something else. The development for it on here is ridiculous. The communication and instructions are just as bad.

Nickdroid86 said:
I have been trying to find up to date directions to unlock the bootloader on my phone with absolutely no luck. No where does it say a compatible unlock to work with the new 8.1 software. I would love to install A1 on my sim unlocked version of my x4. I can't find an up to date version to root or anything. It's so annoying that I am about to just return this phone and buy something else. The development for it on here is ridiculous. The communication and instructions are just as bad.
Click to expand...
Click to collapse
You're obviously not looking hard enough and clearly your first time with an A/B partition phone. Motorola has their website to unlock the bootloader. One quick Google, first result: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Install twrp, and you can flash root of your choice. Magisk or SuperSU. https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-root-moto-x4-install-twrp-t3806460
Not sure what you mean by ridiculous. A few people have been hard at work to give us 3 custom ROMs already.
Not to mention the instructions to get a specific stock firmware flashed.
---------- Post added at 06:35 AM ---------- Previous post was at 06:18 AM ----------
Nickdroid86 said:
I meant as in sim unlocked. Do I need the bootloader unlocked in order to root or flash A1? If I unlock it will I still receive updates and function a normal if I keep it stock rom?
Click to expand...
Click to collapse
The phone will work with any sim. Though recommend you verify the bands the phone is compatible with the carrier of choice. Unlocking bootloader as it's been said multiple times in these forums, breaks OTAs. Topjohnwu has guide around it:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
---------- Post added at 06:36 AM ---------- Previous post was at 06:35 AM ----------
Or just then the phone.

Neffy27 said:
You're obviously not looking hard enough and clearly your first time with an A/B partition phone. Motorola has their website to unlock the bootloader. One quick Google, first result: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Install twrp, and you can flash root of your choice. Magisk or SuperSU. https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-root-moto-x4-install-twrp-t3806460
Not sure what you mean by ridiculous. A few people have been hard at work to give us 3 custom ROMs already.
Not to mention the instructions to get a specific stock firmware flashed.
---------- Post added at 06:35 AM ---------- Previous post was at 06:18 AM ----------
The phone will work with any sim. Though recommend you verify the bands the phone is compatible with the carrier of choice. Unlocking bootloader as it's been said multiple times in these forums, breaks OTAs. Topjohnwu has guide around it:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
---------- Post added at 06:36 AM ---------- Previous post was at 06:35 AM ----------
Or just then the phone.
Click to expand...
Click to collapse
I'm not finding anything saying it's compatible with certain build numbers and/or 8.1 and I'm not looking to brick my phone which seems like people are. I can do a quick Google search but it's not going to say what's compatible.

Nickdroid86 said:
I'm not finding anything saying it's compatible with certain build numbers and/or 8.1 and I'm not looking to brick my phone which seems like people are. I can do a quick Google search but it's not going to say what's compatible.
Click to expand...
Click to collapse
FWIW, I picked up a carrier unlocked Moto X4 from Best Buy this morning and I was able to get a bootloader unlock code from the Motorola site, install Magisk & restore apps via TitaniumBackup. YMMV.

Nickdroid86 said:
I'm not finding anything saying it's compatible with certain build numbers and/or 8.1 and I'm not looking to brick my phone which seems like people are. I can do a quick Google search but it's not going to say what's compatible.
Click to expand...
Click to collapse
I'm not understanding what you're saying. Is what compatible? The build number is firmware related which is what I'm assuming you want to switch, between firmwares.