BOOTLOADER UNLOCK (NON-PAID)
This thread simply is to get a team together, (Team Droid). And figure out a way to unlock the Droid Ultra(Maxx)'s BOOTLOADER A.K.A Nightmare to gain full root capabilities such as Write-Protection Off, TWRP, and Flashing ROMS. If interested just start a conversation here and work on it daily. If any success post it here.
DAWKTERDROID
It will be better if developer focus on rooting kitkat firmware rather than downgrading to older version of android os, because downgrading is impossible till we unlock the bootloader. But rooting kitkat firmware is seems to possible any how...
I would rather be stuck on 4.4.4 without root than go back to 4.4 and have root. Like someone else said I would much rather have root and WP off on 4.4.4 but I can wait.
Sent from my XT1080 using Tapatalk
miketoasty said:
I would rather be stuck on 4.4.4 without root than go back to 4.4 and have root. Like someone else said I would much rather have root and WP off on 4.4.4 but I can wait.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
No what i meant is to downgrade the bootloader to a previous version then flash the system img. of the 4.4.4 update, an exploit for the bootloader will need to be written before you can downgrade the gpt.bin, but keep the current version of android the bootloader of the previous version booted a 4.4.2 stock rom for the moto x so I am sure it will boot a stock 4.4.4 rom. This is just so safestrap will boot into write protect off mode since the new bootloader blocks it.
Won't happen. With 4.4.4 you can't downgrade. Even with unlocked bootloader.
i thought people said 4.4.4 upgrade got a new BL?
so the "team" should focus more on 4.4.4's bl rather than the old ones?
If it got a new bootloader, wouldn't that mean that bootloader unlocked phones would relock upon upgrading? If that's the case, definitely not a new bootloader
xxBrun0xx said:
If it got a new bootloader, wouldn't that mean that bootloader unlocked phones would relock upon upgrading? If that's the case, definitely not a new bootloader
Click to expand...
Click to collapse
No, getting a new boot loader version doesn't lock phones again. Although in theory, a command could be ran in an update to re-lock but in that case just unlock again. So no a new BL doesn't automatically mean locked again.
Well..sold one of my "Unlocked" XT1080M's..put another one on eBay..getting ready for Moto's next, upcoming device..If its unlockable that is..I certainly hope you'all here figure it out..
Sent from my:
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Topsnake is correct. It will not make a change unless there is a specific script running during the update that tells the bootloader to relock. Recovery has also been updated to a new version, but as of now I don't know what has changed in it.
Cant we request Motorola Verizon to turn off write protection atleast.. Lol..
iAjayIND said:
Cant we request Motorola Verizon to turn off write protection atleast.. Lol..
Click to expand...
Click to collapse
You must be from Colorado, because you're smoking something!
Einsteindks said:
You must be from Colorado, because you're smoking something!
Click to expand...
Click to collapse
OMGoodness..
Sent from my:
Jaocagomez Debloated ROM
4.4.4_21.11.21 (Unlocked)
XT1080M Droid Maxx #2
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
Related
Here we go again with another fun how to thread will all my Moto X videos and more to come hope this can help out some noobs
Moto X Review
Moto X bootloader Unlock
Moto X VS. Moto G
Moto X unbrick and restore Tool
Moto X Safe Strap Recovery video
How to install TWRP on the unlocked Moto X
How to install CyanogenMod 11 KitKat Rom
More to come please subscribe to this thread
Mods please sticky I think this will really help people out will be adding more soon
Added video to OP
Video added to OP
New CM11 Video added to OP
Awesome!
I'll be linking to this as well as the complete Moto x guide by @dray_jr I usually link to when people open threads without searching, before I report it. LOL
Great job!
Sent from my N5 cell phone telephone....
kj2112 said:
Awesome!
I'll be linking to this as well as the complete Moto x guide by @dray_jr I usually link to when people open threads without searching, before I report it. LOL
Great job!
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
thanks glad that you like it will be adding more soon
Tomsgt said:
thanks glad that you like it will be adding more soon
Click to expand...
Click to collapse
For sure some will be far less confused SEEING this stuff instead of just reading words.
Sent from my N5 cell phone telephone....
kj2112 said:
For sure some will be far less confused SEEING this stuff instead of just reading words.
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
Yeah I really hope this can help out some noobs.
Mods please sticky this post if you think it will help
Tomsgt said:
Here we go again with another fun how to thread will all my Moto X videos and more to come hope this can help out some noobs
Moto X Review
Moto X bootloader Unlock
Moto X VS. Moto G
Moto X unbrick and restore Tool
Moto X Safe Strap Recovery video
How to install TWRP on the unlocked Moto X
How to install CyanogenMod 11 KitKat Rom
More to come please subscribe to this thread
Mods please sticky I think this will really help people out will be adding more soon
Click to expand...
Click to collapse
Thanks, is there a link on how to root Moto X? It's kinda mentioned at the end of the unlock bootloader video.
x2h said:
Thanks, is there a link on how to root Moto X? It's kinda mentioned at the end of the unlock bootloader video.
Click to expand...
Click to collapse
Check the twrp recovery install video it should have the root in it. Once the bootloader is unlocked just install twrp then flash supersu.zip in recovery to get root. It's pretty easy.
sent from my Galaxy Note 3 running HyperDrive.
Tomsgt said:
Check the twrp recovery install video it should have the root in it. Once the bootloader is unlocked just install twrp then flash supersu.zip in recovery to get root. It's pretty easy.
sent from my Galaxy Note 3 running HyperDrive.
Click to expand...
Click to collapse
'Thanks. Where's the superSU file?
x2h said:
'Thanks. Where's the superSU file?
Click to expand...
Click to collapse
You can get it at rootjunksdl.com or of xda if you Google supersu.zip you will see it.
sent from my Galaxy Note 3 running HyperDrive.
So what if you want to move from 4.4 to 4.4.2 from an ATT, rooted, non Dev, non custom recovery moto x? I was under the impression using this boot loader unlock method only worked for Dev editions..
Sent from my XT1058 using XDA Premium 4 mobile app
NameLessThugZero said:
So what if you want to move from 4.4 to 4.4.2 from an ATT, rooted, non Dev, non custom recovery moto x? I was under the impression using this boot loader unlock method only worked for Dev editions..
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are correct. Bootloader unlock method only works for Dev Editions, and phones from T-Mobile, Sprint and other carriers where Moto gives out bootloader unlock codes. If you have an ATT or Verizon retail or Moto Maker X, and were not lucky enough to buy an unlock code from the Chinese seller (before it got shut down), you can not unlock your bootloader and use TWRP to root.
If you have a LOCKED (and not unlockable) bootloader, like ATT/Verizon, and you are on rooted 4.4 using SlapMyMoto and disabled write protection by using MotoWpNoMo, taking the 4.4.2 OTA update will revert the effects of MotoWpNoMo, patch the exploit used, and write protection will become re-enabled. You will likely keep root, but with write protection enabled, any changes you make to /system or the other protected folders will be lost at power off/on, making root less useful. Since 4.4.2 also patches the exploit used to gain root, if you hadn't rooted before taking 4.4.2, you wont be able to root it once its on your phone.
HOWEVER... If you are rooted & write protection disabled with 4.4, you could consider using SafeStrap with 4.4.2. I don't know how well it works (I have a Dev Edition, so I haven't tried it), but it is an option for using 4.4.2
Bump for noobs
Sent from my SM-G900V using Tapatalk
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
rockketman123 said:
Ok so my whole problem is that im on system version 183.46.15.XT907 when its supposed to be 183.46.10.XT907. My question is that is there a way to get to 183.46.10.XT907. again? I've been at this for hours and i'm in desperate need for help.
If you would like to see a picture of exactly please PM it will not let me place a picture as i am a new user
Click to expand...
Click to collapse
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini
That's a bummer, but for root part, maybe or maybe not. I don't think it's possible as Motorola took out some vital codes from Kit Kat ROM which allows root.
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
rockketman123 said:
ATTACK said:
As of now there is no way of rooting or downgrading with a locked bootloader.
Sent from my Scorpion Mini[/QUOTEO
I was able to flash it down to .10 but my kernel was after June 3rd, something like July 27th or whatever and yeah this doesnt allow it to work. Oh well, I'm switching to an S3 In less than a month.
Click to expand...
Click to collapse
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
I suspect it's already unlocked as it's impossible to downgrade the kernel on a locked RAZR M (OEM signatures, you know).
AndyYan said:
rockketman123 said:
Unlocked or locked? Kernel date and screenshot as proof please, including the AP Fastboot screen.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
as I'm a new user I cant post a screen shot but the imgur link is i(.)imgur(.)com/xiZuIyq(.)jpg and i(.)imgur(.)com/cA6W6Oi(.)jpg
I went from 4.1.2 Rooted and was never able to unlock the bootloader then flashed to 4.4.2 on the .15 then flashed to .10
Click to expand...
Click to collapse
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
EDIT: I looked at the pictures, however, I am suspicious of the claim. The reason being, the bootloader will check the kernel version, and if it's not agreed with the bootloader security key file (tz.mbn), the bootloader will refuse to touch it. If anyone else with the locked phone tries this harebrained experiment and come out without a softbrick, I may have to eat my sock.
Dr. Mario said:
You're outta luck. You ahould have flashed .10 first and unlocked the bootloader before you hop between the ROM version... .15 version permanently lock the bootloader.
Click to expand...
Click to collapse
yeah when i flashed over i "accidentally" did the wrong version (tut linked me to a wrong version I suppose) and now im piss out of luck, but like i said im not worrying about it since s3 within a few weeks or so. Hopefully one day it's able to Root though B)
EDIT: what exactly are you suspicious of? The claim that I went from 4.1.2 flashed to 4.4.2 but on .15 then down to .10?
If the eventual RAZR M update gets screwed up like the first one, it may get unlocked but I have grave doubt because Verizon have learned their lesson on this one: root = bootloader unlock, at least in the case of early Kit Kat update.
fellas i have received two moto M today and seems like this cant either root because this stupid 9mb of .15 update, since the kernal is after jun 3
towelroot
well any new exploit around the coner to try?
No root exploits right now, unfortunately. It's getting harder and harder to exploit the Kit Kat.
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
JulesJam said:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
Click to expand...
Click to collapse
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
I can't imagine the OTA would lock the bootloader, but who knows...
fury683 said:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
Click to expand...
Click to collapse
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.
Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.
JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.
fury683 said:
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.
fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand
But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.
For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.
So yeah, as you said...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse
superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.
it leaves a copy of the fxz on your computer.
sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.
Any Updates on this situation?
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.
Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.
The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.
I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.
Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
breakthestatic said:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
Click to expand...
Click to collapse
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Maverick-DBZ- said:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked
I HAVE ROOTTED DROID RAZOR M 183.46.10 4.4.2 UPDATED CAN ANY ONE TELL ME HOW TO UNLOCK BOOTLOADER I HAVE TRIED EVERYTHING LIKE motopocalypse PLEASE HELP !!!!!!!!!
For now - sigma box with pack 2 only.
There is no 'free" ways to unlock your device at this moment....
jamil.ah said:
I HAVE ROOTTED DROID RAZOR M 183.46.10 4.4.2 UPDATED CAN ANY ONE TELL ME HOW TO UNLOCK BOOTLOADER I HAVE TRIED EVERYTHING LIKE motopocalypse PLEASE HELP !!!!!!!!!
Click to expand...
Click to collapse
See index
[INDEX] Motorola Droid Razr M (2015)
Sent from my XT1028 using Tapatalk
FWIW, the APK version didn't seem to want to work for me, but the zip worked fine from my PC. You need to use the OEM Moto USB cable (or identical one), too. Just did it twice the past few days.
topshot said:
FWIW, the APK version didn't seem to want to work for me, but the zip worked fine from my PC. You need to use the OEM Moto USB cable (or identical one), too. Just did it twice the past few days.
Click to expand...
Click to collapse
What are you talking about? You unlocked bootloader with .zip'ed motopocalypse on latest firmware?
Shmaks said:
What are you talking about? You unlocked bootloader with .zip'ed motopocalypse on latest firmware?
Click to expand...
Click to collapse
If you bother to read the OP (or the title), he's not using the latest firmware (and neither am I) so he can still unlock it. However, if he updates to the latest BEFORE unlocking, he indeed will be screwed.
topshot said:
If you bother to read the OP (or the title), he's not using the latest firmware (and neither am I) so he can still unlock it. However, if he updates to the latest BEFORE unlocking, he indeed will be screwed.
Click to expand...
Click to collapse
Except it's not the system version that matters it's the kernel version that does.
Greetings!
As of today there is a method to completely unlock the bootloader on all variants (yes, this includes the Verizon and AT&T models). The one stipulation is you need to have root.
DISCLAIMER #0: This is NOT MY WORK. I'm merely posting steps to use other peoples' work (with permission) in order to achieve an unlocked device. Do not donate to me for this. Any donations sent to me for this post will be promptly returned and you will be publicly shamed, most likely Game of Thrones style, for not reading the entire OP and following directions.
DISCLAIMER #1: Unlocking your device is dangerous! I am in no way responsible for anything that happens to you, your device, your significant other, or any random person that you feel the need to harm after this destroys your device! You are making the decision to run these tools and you alone are responsible for the consequences!
DISCLAIMER #2: As of right now this method has ONLY been tested on variants running kitkat (4.4) roms/bootloaders. Do not be the first to try it on a lollipop version without first understanding the risks. If you try and successfully use this method on lollipop (5.x) please let me know so I adjust this post accordingly.
DISCLAIMER #3: Do not attempt to re-lock your bootloader after using Sunshine. It is unclear how the device will act and you may end up with one of these.
PREFACE:
- You're going to want adb and fastboot set up on your computer. If you don't know what these are, or don't know how to set them up, google it. Having these tools is insanely helpful anyway for debugging and getting logs for developers later. You're going to want these in the long run.
- This method in the end is going to set you back $25. Sunshine is the tool used to unlock the bootloader and the people that develop this spend insane amounts of time developing/breaking/buying devices. Trust me, its worth it.
- Enable Unknown sources in Settings > Security before starting
STEP 1: Root (This root method only works on 4.4. If you are already rooted, say via mofo or another method, you may skip to step 2)
- You just skipped to this step didn't you? Go read the disclaimers and the preface. They are extremely important.
- Root your phone using KingRoot (obviously click the image with the little android guy on it) mirror
Code:
adb install -r <filename>.apk
- Run it from your app drawer and follow the prompts. I did have it fail a couple times, if that happens, try rebooting and running it again. I also had it say it failed a couple times, but still was able to gain root by typing 'su' in an adb shell.
- KingRoot is a temp root, which means upon a reboot, you will lose root and need to run it again. That's fine for our purposes here, it gives us the in we need for the bootloader exploit (see step 2)
STEP 2: Unlock That Bootloader
- This step involves running an app called Sunshine. Download the apk from there and install it:
Code:
adb install -r <filename>.apk
- Again, this unlock will cost you a one time fee of $25, more info on their FAQ. There seems to be a lot of animosity about this, but in the end the choice is yours. An extreme amount of development time goes in to these types of exploits and these guys do a fantastic job. It is worth it.
- Follow the prompts, get out the wallet, and enjoy an unlocked bootloader!
STEP 3: Install a custom recovery
- This could be considered an optional step, but there's really no reason to go through all of this if you don't plan to do some custom things. Custom recovery allows you to install/backup/restore ROMs on your phone.
- Follow the instructions here now that you have an unlocked bootloader in order to install TWRP.
STEP 4: Enjoy!
- You now have a completely unlocked phone! Start installing roms, enjoy yourself! Be careful though! Make sure you are only flashing things that are known to work on this device.
SunShine 3.1.16 is out, better support for MotoX 2014, including custom roms
Just ran Sunshine 3.1.17 on my 5.1 XT1097 rooted via MoFo, device is unlocked and working flawlessly.
invisiblek said:
(This root method only works on 4.4. If you are already rooted, say via mofo or another method, you may skip to step 2)
Click to expand...
Click to collapse
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
JulesJam said:
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
Click to expand...
Click to collapse
Only way to know is try if okay with the risks.
We talked about it in the general thread. Sometimes it even works on other devices running 5.1.1 (even not officially supported). I cannot assume the risk being my only phone to try.
Visi0nofExcellence2 said:
There are posts of it working for other devices. It will fail a couple of times and then just work. Also cases where the phone won't boot anymore. More of the latter now.
Not attempting and I suggest others dont either. Risk outweighs rewards with this being my main phone.
Click to expand...
Click to collapse
Visi0nofExcellence2 said:
jcase said:
Kingroot shouldnt cause the phone to stop booting, odd. Thanks for makign the thread btw
Click to expand...
Click to collapse
Not bootng is horribly ambiguous wording on my part.
chicodelta said:
My shield is running 5.1..1. I tried kingroot 4.5, since others have reported success and now my tablet won't boot past the nvidia screen. Anyone else encountered this issue?
Click to expand...
Click to collapse
http://forum.xda-developers.com/shield-tablet/general/root-kingroot-t3112722/page4
Click to expand...
Click to collapse
JulesJam said:
Kingroot is available for MX14 XT1085 (Chinese MX14) running 5.1. Do you think it will work on a MX14 XT1096 running 5.1?
Click to expand...
Click to collapse
I tried it (several times). It doesn't.
Sent from my XT1096 using Tapatalk
I did mofo yesterday and did SunShine today, worked great. I had 5.0 on my 1096.
Sent from my XT1096 using XDA Free mobile app
Any known root methods for 5.1 yet? AT&T Moto X via OTA.
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
christopher68369 said:
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
Click to expand...
Click to collapse
No
Sent from my XT1096 using Tapatalk
christopher68369 said:
I have tried both kingroot and mofo. Neither work for the xt1097 att variant on 5.1. However looking on some pages on xda noticed that the xt1097 from Brazil has the same specs as the att variant. The files look pretty much the same as well. Do you think it would be possible to flash the 5.1 Brazil to the att without bricking? Bootloader is also the same. Flash the Brazil over the att and then try Motorola unlock tool online
Click to expand...
Click to collapse
It won't work. You can't flash the firmware from other carriers with a locked bootloader. It will fail when you try.
Sent from my XT1095 using Tapatalk
Only firmware you can flash with a locked bootloader has to contain the same signature of the firmware your on, which is literally only that firmware. EG. ATT 5.1 sig does not match any other sig.
Yes I realised that after doing research. Butbim wondering if we were able to change the cid to lets say the Brazil variant if we would be able to flash the firmware. If we could maybe change the cid from dfs software or GSM tools software and then try to flash the firmware if it would work. If someone knew how to change the cid without root I wouldn't mind trying it out to see if it would work. I'm planning on buying the moto x pure edition that comes out on Sept 2 but i f I was able to unlock the bootloader then I wouldn't really mind waiting on a new phone for another year since the moto x 2014 is really a great phone and with root has alot of potential
Same problem, you can't do that either without root and bootloader unlocked. There is no way to do it until someone can find a vulnerability in the 5.1 firmware. For now you are stuck.
Sent from my XT1095 using Tapatalk
I don't understand. Motorola officially provides the way to unlock bootloaders. Why does this method exist? Does this method help unlock bootloaders of devices that cannot be unlocked or something like that?
Yes, this is only for the Verizon xt1096 and the AT&T xt1097. Those 2 models cannot unlock their bootloader from motorola's website. This is a method to get around that and unlock it anyway.
Sent from my XT1095 using Tapatalk
So I have a Verizon model XT1096 running 5.0.
From the searches I've performed and from what I've read so far, Root can be achieved via Mofo (kingroot failed) and then I can unlock the bootloader via sunshine and then flash TWRP, flash a 5.1.1 ROM and I'm good to go?
There are several threads with a little info here and there, so I apologize for the questions. I just want to get my ducks in a row.
You are correct.
Sent from my XT1095 using Tapatalk
Ed Murray said:
So I have a Verizon model XT1096 running 5.0.
From the searches I've performed and from what I've read so far, Root can be achieved via Mofo (kingroot failed) and then I can unlock the bootloader via sunshine and then flash TWRP, flash a 5.1.1 ROM and I'm good to go?
There are several threads with a little info here and there, so I apologize for the questions. I just want to get my ducks in a row.
Click to expand...
Click to collapse
Kingroot said that it failed for me but sunshine still worked normally afterwards. If you haven't already paid for mofo then you can just pay for sunshine
Sent from my XT1095 using Tapatalk
Moto X 2013 (Verizon and ATT) got root on 5.1 with locked bootloader. Maybe we can use the same exploit?
http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125