I'm looking for information on rooting my UK wifi Xoom and the ability to unroot and re-lock the boot loader, thus returning it to 100% stock (just in case...). I seem to have got a little confused as I'm reading that it's not 100% the same as the US Wifi Xoom and that there is a danger of bricking it if I'm following the wrong guide. Could someone point me to the correct guide for this? Not terrible interested in the new kernel, just want that fancy Asus MyWater live wallpaper, so it's just root I'm after.
I had no problems unlocking and rooting my UK Wifi Xoom (Note Don't try on a uk 3G xoom)using on-click root and also installing Tiamat kernel using CWM.
However, DO NOT attempt to re-lock as YOU WILL brick your xoom.
Hopefully, very soon Motorola will release stock wifi recovery images.
If for any reason rooting goes wrong you can flash (using Fastboot) the Canadian images posted..
Cheers
Ody
US already has clean wifi images at http://developer.motorola.com/products/software.
I'm the one that posted the Canadian wifi files up (with help from robbiev80). From what I hear, it's pretty close to the UK version.
Do not relock unless images are straight from Motorola. I'm not willing to test locking with my "clean" Canadian image files.
I'll think I'll hold off until Moto release the images for the UK version tbh, I had some issues when rooting my N1 for the first time so I'd rather not be without the ability to put everything back as it was.
odyseus said:
you can flash (using Fastboot) the Canadian images posted..
Click to expand...
Click to collapse
Do you need to root the Xoom before flashing the Canadian image? I have a US Xoom WiFi and all I want are Swedish system language and spelling. Don't care about anything else that I need root for...
Nope. You simply need to unlock it by doing a "fastboot poem unlock". That is the point in which you are able to flash. Just don't try relocking. Also, be sure to do a "fastboot -w" at the end to clean out your userdata after flashing boot and system.
Thanks! Is there anything "bad" having an unlocked device?
I will search for instructions on howto fastboot later but if I dont find anything I might comeback and ask you if thats ok?
Nothing bad at all about leaving it unlocked.
Anyone know what the warranty for the UK version says about bootloaders and rooting?
Scourge1024 said:
Nope. You simply need to unlock it by doing a "fastboot poem unlock".
Click to expand...
Click to collapse
Just to be 100% sure... You meant "fastboot oem unlock", right?
Nothing comes up when searching for poem...
*EDIT* Never mind, I got it working. I have Swedish system language now.
Scourge1024, thank you very much for your help!
Related
Hi xdadevelpers team unfortunately i have installed an unoficial rom for my device from this link http://forum.xda-developers.com/showthread.php?t=2069935 it works very good and no thing wrong with it but i have to send my phone to the Authorized agent here in egypt because of a problem at the sim card place in the phone so i need to get back to the official kernal which is ics is there any way to do this please help me
have you noticed, that this is the Razr HD section ?
And yes. MOAR fonts
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Xadro said:
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Click to expand...
Click to collapse
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
mostafas60 said:
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
Click to expand...
Click to collapse
What do you mean by saved cid? Is your phone carrier locked? Or what are you trying to say? You should pick a stock fw, which is at least your country/region better also from your carrier. It may also not be available at the site i mentioned.
If it is not available you could try and make a request. See the op of this thread
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Uh thanks for the heads up, wasn't aware of that. I assumed that motorola devices would be all similiar with this.
cellzealot said:
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Click to expand...
Click to collapse
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
mostafas60 said:
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
Click to expand...
Click to collapse
guys is there any one can answer me and how to solve this issue
http://forum.xda-developers.com/forumdisplay.php?f=1622
mostafas60 said:
guys is there any one can answer me and how to solve this issue
Click to expand...
Click to collapse
Probably if you go to the right forum man.
Sent from my PACMAN MATRIX HD MAXX
I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?
impinball said:
Okay... I also have another wonderful problem: my phone consistently gets into fastboot mode upon startup, with my current workaround of doing fastboot continue. Is there any way to fix my currently locked bootloader?
Click to expand...
Click to collapse
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.
RikRong said:
As Jhal said, you can't "fix" your bootloader, it's locked since you're on the newest OTA and it can't be unlocked. With that being said, your phone is not booting into fastboot because you're rooted. It's booting into FB because you tried to flash something that didn't work. What other things have you done or attempted to do, besides rooting? This will help us help you, the info you provided is pretty vague.
Click to expand...
Click to collapse
I have done absolutely nothing beyond rooting it, installing Superuser & SuperSU (both through a script I can attach, but I'm on the wrong computer), and backed up a slew of apps.
This first begun when I modified the script to fix a bug in it (ash in JB 4.2 doesn't have a -f switch in rm, and the script had a 'rm -f'). If that bug didn't exist, then it would've still happened the first of several times (I attempted it about 4-5 times, but only the last caused this). The rm -f was actually doing effectively (with successful root privileges) 'rm -f /system/install-script-2.sh', but the script actually had another script to be put into it at the location /system/install-script.sh.
???
Start by detailing steps in your 2nd paragraph.
Your boot is locked if it was never unlocked before you upgraded to ...79 or later
what a coincidence i just got a xt926 and im at the same spot.. 9.30.1 rooted but locked ... iguess we're screwed huh
impinball said:
I've successfully rooted my Droid RAZR MAXX HD with stock firmware version 9.30.1, but I can't seem to figure out how to unlock the bootloader.
The one catch with my phone being rooted is that it always ends up in fastboot when it boots. A simple
Code:
fastboot continue
fixes the problem, but I was wanting to flash CWM Recovery to install CM.
I have a working su/Superuser.apk, but I can't seem to fix the bootloader dilemma.
Click to expand...
Click to collapse
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".
skeevydude said:
Looks like you either flashed a fastboot or used a tool that used the command "fastboot oem fb_mode_set" which causes the phone to boot directly into fastboot mode. It can usually be fixed with the command "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).
impinball said:
Didn't work. It is still booting there on its own upon start-up.
Also, I will mention that I did commit an act of stupidity: trying to flash against a bootloader that I couldn't verify was unlocked yet. I stupidly ran the command when I wasn't even 50% sure that it was unlocked yet (and is likely the cause of all my problems):
Code:
fastboot flash recovery <cwm-file>.zip
I'm trying my hardest to avoid sending this to Motorola just for them to charge me for the replacement, saying I've voided any warranty that exists with the phone. I have the original firmware to flash just in case, but I don't have the Motorola fastboot (for the dev editions).
Click to expand...
Click to collapse
First, there is no Dev Edition Fastboot....the closest would be Bell ICS since Bell shipped unlocked/unlockable Atrix HD's.
You don't flash zip files with fastboot flash.....Why is this becoming an issue these days?* The kernel is "fastboot flash boot boot.img"
*just thinking out loud
EDIT: Just realized that this was the RAZR HD forums.....just replying to quoted posts this morning....Not sure about RAZR HD Dev Edition fastboots....
Jhall8 said:
The last software version with an unlockable bootloader is 9.16.6.XT926. Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The shame is, I never cared about unlocking the bootloader, as I prefer to stick to OTA's, but I do require root. So that's all I've ever done. I'm successfully rooted with the locked bootloader on 9.30.1, but it seems (at least as far as I've read on here) that I'm stuck there as I can't go anywhere else and maintain root. Would love kitkat, but root is essential.
Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.
killrhythm09 said:
Um, you can unlock the bootloader and still stick to OTAs.
Being able to root at any time and use custom recovery is reason enough for me.
Click to expand...
Click to collapse
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk
iBolski said:
Talk to Verizon. They're the ones preventing the bootloader from being unlocked.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
This. It's no coincidence that the xt925 can be unlocked through Motorola. Carriers are always the problem here in the US.
crazifuzzy said:
I in no way implied I was AVOIDING unlocking due to the desire to stay on OTA's - just that I had no reason to pursue unlocking. This is the first android device I've had that ended up with a sunset where you couldn't unlock it at pretty much any point, so i never had a fear of taking the OTA and losing something in the process. If i had expected that, I certainly would have unlocked prior to 9.30.1 being installed. I honestly have yet to figure out why they don't release a program that would allow unlocking the devices - I'm not sure the manufacture's fear of unlocked bootloaders and root, as any program they release would be loaded with disclaimers - and frankly, it would allow easy restorations to ANY firmware version by service staff at verizon/at&t.
Click to expand...
Click to collapse
Well, in actual reality, the XT926 was never meant to be unlocked. It was only unlockable via an exploit, just like obtaining root for locked devices is an exploit in the security of the OS/device.
So, there never really was a "sunset" for unlocking this device as it wasn't meant to be. Only after the exploit was found did a patch come out to stop that exploit from being utilized on any remaining unlocked phones, current or future.
So, when there is an exploit to unlock a device, your best bet is to take advantage of it immediately.
When I got my RAZR HD, it was as a warranty replacement for my OG RAZR MAXX. When I fired it up, it stated there was an OTA available. I immediately told it no and then went straight to the forums here and on another site to investigate what my options were. When I found out that there was the possibility of my unlocking the bootloader, I immediately went to where the tool was and downloaded it. I then proceeded to read and then ask questions on if my phone couldn't unlock, would it hurt it. SamuriHL helped me out a great deal and that is how I found all his tools and how much help he provides. If it weren't for him, I wouldn't have discovered that I could unlock my bootloader.
Usually, I investigate the phone I'm interested in to see if:
1. Can the bootloader be unlocked (or is it already unlocked)?
2. Is there a known root exploit IF the bootloader cannot be unlocked?
3. What are the ROM options (safestrap, cwm, twrp recovery)?
It's definitely something I normally would look into, but I didn't know that I was going to receive the RAZR HD. Once I discovered the possibility of unlocking the bootloader, I was hoping beyond all hope that it could happen and it did. How I received a replacement phone that wasn't patched to the latest OTA was beyond me, but that is the reason I refused the OTA when I first fired up the phone. I had already read about other "horrors" of people taking an OTA and then finding they couldn't root or do other things with their phones.
Lesson learned is, NEVER take an OTA until you've fully researched what it does and what it might prevent.
Hello, I'm kind of a noob on these things but here we go:
My Razr is stuck on the red Motorola logo (the boot animation when you turn on the phone) I believe this is what you call "bricked" (?).
I found out some methods here about downloading an XML file and replacing it but where can I find this file? And where do I need to replace it, it is on the firmware file, right? I wanted to get a USA firmware because in my country (Mexico) the KitKat update hasn't been liberated for us and I want to be able to update it.
A friend told me that if I put a firmware from USA it would ask me to update but to do this I need to unlock the bootloader.
I saw a tutorial on unlocking it with Motopocalypse but to do this I need to put the phone on Debugging Mode and I can't do that since my phone is bricked.
Is there a way to unbrick my phone and being able to install KitKat?
If not, of course my priority is to just unbrick it asap regardless if it is with KitKat or JB :/
Thank you so much in advance.
First, you need to tell us exactly what you did that "bricked" it. And I say "bricked" because if you can get to the Motorola logo, it probably isn't really bricked.
Either way, your friend's advice sounds like a bad idea to me. The US firmware is meant for the xt926, which uses Verizon's network. You should either wait for firmware to be released in your region or use a custom ROM (something you can do if you end up unlocking the bootloader).
Do the same: http://forum.xda-developers.com/showthread.php?p=57063750 doesn't care if your device is "bricked"
killrhythm09 said:
First, you need to tell us exactly what you did that "bricked" it. And I say "bricked" because if you can get to the Motorola logo, it probably isn't really bricked.
Either way, your friend's advice sounds like a bad idea to me. The US firmware is meant for the xt926, which uses Verizon's network. You should either wait for firmware to be released in your region or use a custom ROM (something you can do if you end up unlocking the bootloader).
Click to expand...
Click to collapse
When I turn it on it is stuck on the red Motorola logo, it goes like that for hours until battery is dead.
I can go into the bootloader options (when you press vol +/- and power) and I have tried wiping all the data to factory settings but the result is the same.
Sorry if I'm using the wrong terminology.
DorianX said:
Do the same: http://forum.xda-developers.com/showthread.php?p=57063750 doesn't care if your device is "bricked"
Click to expand...
Click to collapse
Can I do that even if I have never unlocked my bootloader?
Update:
I tried flashing with my carrier firmware and deleting the proper lines on the .xml file, then opened with RSD but it shows:
"Failed flashing process 14/21 flash boot "boot_signed" -> Phone returned FAIL"
And on the Fastboot manu on the phone it shows:
"Partition (boot) Security Version Downgraded"
"preflash validation failed for boot"
Please help me
mauber said:
Can I do that even if I have never unlocked my bootloader?
Click to expand...
Click to collapse
If you never upgraded to KK you don't need to have unlocked bootloader, but why don't you unlock your bootloader? I see only benefits with.
DorianX said:
If you never upgraded to KK you don't need to have unlocked bootloader, but why don't you unlock your bootloader? I see only benefits with.
Click to expand...
Click to collapse
Is not that I don't want to, it is that I can't. I'm having trouble flashing the firmware.
Just follow the tutorial http://www.grupoandroid.com/topic/71673-instalar-un-firmware-por-fastboot-en-imágenes/ and use Claro Puerto Rico firmware, then take the OTA
DorianX said:
Just follow the tutorial http://www.grupoandroid.com/topic/71673-instalar-un-firmware-por-fastboot-en-imágenes/ and use Claro Puerto Rico firmware, then take the OTA
Click to expand...
Click to collapse
I did but it got stuck on the "boot_signed" step (RSD lite), deleting that line on the XML file and then it showed the "system_signed" step error, deleted that line on the XML and it apparently flashed successfully but the phone is back to where it was before, stuck on the red Motorola logo boot animation.
My phone is boogered up so bad that it just boots into fastboot mode. I have been unsuccessful in flashing the stock ROMs. It's the Canadian version with unlocked GSM. I'm hoping that unlocking the bootloader will help me to flash it and get it working again. I have tried using the Motorola site but it says my phone cannot be unlocked.
Anyone?? Please? I have search these forums for days and cannot find the answer to my question. If it's there I'm finding it. Any help would be appreciated.
I know Rogers allows unlocking the bootloader. As I recall, you're a Fido user (which Rogers owns) right? Are you still looking for the Fido 4.1.2 SBF? I think I can track it down for you. I'm surprised Moto won't unlock the bootloader via the website. Have you tried Motoclypse (I think it's called) to try and unlock it? I guess you'll need a running ROM first.
Lemme know what you need exactly and I'll see if I can hunt it down for you.
CWGSM3VO said:
I know Rogers allows unlocking the bootloader. As I recall, you're a Fido user (which Rogers owns) right? Are you still looking for the Fido 4.1.2 SBF? I think I can track it down for you. I'm surprised Moto won't unlock the bootloader via the website. Have you tried Motoclypse (I think it's called) to try and unlock it? I guess you'll need a running ROM first.
Lemme know what you need exactly and I'll see if I can hunt it down for you.
Click to expand...
Click to collapse
CWG... Thank you! I've scoured a few sites that are still up and running (best one so far is motofirmware.com.) I found and downloaded this.. 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml but cannot flash gpt and boot partitions. I have tried editing the xml file as suggested in other posts to prevail. Is there a way I can positively identify which region my phone is? I purchased it brand new from a Canadian seller on eBay. The listing said that it was a Rogers phone but when I unlocked the GSM the key came back as being from Fido. There was no carrier specific apps on it. I'm at the most current level of firmware on it by the carrier as of a few weeks ago.
I got the bootloader unlocked!!!! I was originally entering the code into Motorola's website through Chrome and something told me to try it through Firefox.... success!!
truebeliever71 said:
I got the bootloader unlocked!!!! I was originally entering the code into Motorola's website through Chrome and something told me to try it through Firefox.... success!!
Click to expand...
Click to collapse
Awesome, so you're good to go or still need a SBF for Fido?
CWGSM3VO said:
Awesome, so you're good to go or still need a SBF for Fido?
Click to expand...
Click to collapse
Nope. I'm good. Installed the one mention before and updated to KitKat.
I'm totally new to the Android world and i spent many hours to read this forum to learn as much as possible about my device and what i can do with it. But now, i need your help on a few things.
KitKat vs Lollipop, does it make sense to upgrade to Lollipop now or should i wait? Is there any major know bugs?
Since that i only have a 8gb device, i would like to clean the apps as much as possible. There's many apps that i don't need but they can't be uninstalled. For example, all the Motorola apps (is there something that we really need from them?), a few google apps like Google+, Google Play Films, Hangouts, etc that i will never use.
I want a stable ROM that i don't need to patch every day to solves problems. When i read about CM12 for Moto G, i see people that have problems here and there and wait for the next daily build to give it a try. I don't want to play that game!
If i install a custom rom, i guest that future updates will not come from Motorola. How the updates work afterward?
It's ok if i must have my device rooted
I have read about stock lollipop optimized version by lost101 but it don't think that the versions currently available will work for me. I'm in Canada and the versions that i see is Brazil or Asia.
thank you for you help!
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Well what I will say is. I'm in the uk using lost101s BR optimized and I'm very pleased with it.
audit13 said:
You have the xt1032? Is there any warranty left? If there is no warranty, I recommend unlocking the bootloader before doing anything. It is easier to restore a bricked phone if you have an unlocked bootloader.
If you intend to stay on stock, you need some of the Motorola apps in order to install OTA updates.
Click to expand...
Click to collapse
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
skoub2 said:
The phone is new but i don't care about the warranty. I've read that i can unlock the bootloader with the Motorola tutorial. I must be honest, i'm a little bit lost. I don't fully understand the difference between "unlocking bootloader" and "phone rooted"!
and yes the model i have is XT1032
Click to expand...
Click to collapse
You must unlock boot loader first then flash a custom recovery (manually or there is a tool in the development section) then rooting next.
Unlocking the bootloader allows you to install non-Motorola software. With a locked bootloader, the only software that can be loaded on your phone would have to be digitally signed by Motorola.
Rooting gives you administrative access to the system files.
You may not need an unlocked bootloader to get root and you do not need root to unlock a bootloader.
Start here to get the bootloader unlock code: https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
I tried to install TWRP (any version available) but it take like 1 minutes to show the home screen and im not able to "swipe to unlock". So i have installed Philz recovery and then installed lost101 Retail Brazil 5.0.2 Stock ROM (Optimized) v1.1a. I'm playing with it right now and so far so good.