Related
I have a friend that moved from the Midwest with Silverstar Wireless (http://www.silverstarwireless.com/)
He got a contract on Verizon, but got a crappy Samsung Gem. He's hoping I can get the Droid X to work. I'm hoping I can put a Verizon 2.3.4 ROM on his phone so it will work properly.
BEFORE everyone asks, YES, I spoke to Verizon Level 2 (or 3?) tech support. The tech worked with me for almost an hour trying to get the phone unlocked using the stock Silverstar software. I have all of the unlock codes. Voice and SMS will work properly, but we could not get data to work at all. 3G is completely dead. *228 doesn't work. The tech thought it wasn't communicating properly with Verizon towers; maybe the baseband is bad? Verizon WILL take the device, however, and the IMEI is accepted.
Any ideas? I'll try third party ROMs, such as CM7, etc, but for the sake of ease, I figured a stock rom might be easier.
Current "About Phone" readouts
System version
Version.3.2.6.MB809.ACG.en.US
Model number
Milestone X
Android version
2.2.2
Baseband version
BP_C_02.06.00R
Kernel version
2.6.32.9-ge37fac8
[email protected] #2
Build number
RETAIL
ERI version
1357
PRL version
31411
a) I'm not positive but I think if the phone can work with Verizon, it can do it without being rommed.
b) If you fix it, let me know what you did because I'm on an actual DROID X and started having the same problem late last week (except that I'm not switching carriers). Both Verizon and Motorola seem to be clueless as to how or why.
EDIT: In case they didn't tell you - ##PROGRAM is how you get to all the low-level stuff (password is 000000 I think). But DON'T just change it on your own or if you do make sure you write down what you changed it from.
netraven5000 said:
a) I'm not positive but I think if the phone can work with Verizon, it can do it without being rommed.
b) If you fix it, let me know what you did because I'm on an actual DROID X and started having the same problem late last week (except that I'm not switching carriers). Both Verizon and Motorola seem to be clueless as to how or why.
EDIT: In case they didn't tell you - ##PROGRAM is how you get to all the low-level stuff (password is 000000 I think). But DON'T just change it on your own or if you do make sure you write down what you changed it from.
Click to expand...
Click to collapse
Yes, thanks, these are the codes I had. As I mentioned, a VZ tech walked me through the manual programming, and we got voice and text to work, but no data - basically defeating the purpose of a smartphone. Although ... this is good to know if you ever want to use a smartphone with wifi, on a non-data plan
Try. Qpst program, you need change the nai and. Tethered nai to [email protected] try and post results
Sent from my DROIDX using xda premium
Well, I tried a two different generic MB809 SBF files, which both failed. Then I tried a VZ MB810 SBF ... which bricked my phone.
At this point, I'm guessing I need an MB809 SBF, but I somehow need to change the baseband/radio to a Verizon file. Assuming, of course, that I can unbrick the phone...
carlosirai said:
Try. Qpst program, you need change the nai and. Tethered nai to [email protected] try and post results
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
I'm not quite sure what that means. I have heard of qpst though.
Unbrick DX
I bricked my verizon droid x 2 days ago, got it back up and running using 1KDS live cd that flashed milestone X .604. It also rooted my phone, now I'm good to go. I bricked my phone by trying to sbf back to .602 after recieving ota .621 update. The milestone x is actually for European ntelos carrier but works flawlessly with verizon. I hope this helps. I can't post links yet so I you have to google and find: Download - 1KDStaz_MX_4.5.604.iso (Milestone X 4.5.604 Gingerbread)
210.8mb (210,763,776 bytes)
Try to flash a .15 radio, I had that kind of problem after I sbf my X with Milestone .604 if you want to use a Verizon.
Sent from my DROIDX using xda app-developers app
Orion575 said:
Try to flash a .15 radio, I had that kind of problem after I sbf my X with Milestone .604 if you want to use a Verizon.
Sent from my DROIDX using xda app-developers app
Click to expand...
Click to collapse
How do I get the radio file and get it on the phone?
Has anyone unlocked the bootloader on their Razr M retail version yet? It's been mentioned on some other forums that you can get the unlock code from Motorola website. This should then allow a recovery to be installed onto the phone.
So has anyone attempted it yet?
Not going to happen on retail non developer edition. /thread.
Sent from my SCH-I535 using xda premium
No, he's an Aussie , our RAzr Ms are unlockable.
My Australian Telstra branded Razr M spat out an unlock code via the motorola unlock website just like the dev edition phones do. It says right on that website if your phone is ineligible you will receive an error. And I got the code, not the error.
Ausdroid also says explicitly they have confirmation Aussie Razr M is unlockable via moto website.
PJcons, I notice the same discussion on whirlpool, seriously if you don't believe this answer then go and try it yourself, no point asking repeatedly esp as you are confusing people here who have the US CDMA verizon version not the aussie GSM/LTE1800 Telstra version. Also, there is already an existing thread (me lol) http://forum.xda-developers.com/showthread.php?t=1964862
However re: actually unlocking, I can't confirm the last step i.e. actually doing it. The only reason I haven't actually gone ahead is because there is actually no point at this stage as we don't have access to any remotely mature custom ROMs, and the only CWM floating around is not confirmed working on our variant (though as long as it doesn't touch the radio, theoretically it should). But I'm reluctant to do anything without having a stock Telstra fastboot image as a last resort roll-back option, years and years of flashing droids has taught me that if nothing else. Theoretically though I do not see how it could possibly fail if you have the token.
wintermute000 said:
No, he's an Aussie , our RAzr Ms are unlockable.
My Australian Telstra branded Razr M spat out an unlock code via the motorola unlock website just like the dev edition phones do. It says right on that website if your phone is ineligible you will receive an error. And I got the code, not the error.
Ausdroid also says explicitly they have confirmation Aussie Razr M is unlockable via moto website.
PJcons, I notice the same discussion on whirlpool, seriously if you don't believe this answer then go and try it yourself, no point asking repeatedly esp as you are confusing people here who have the US CDMA verizon version not the aussie GSM/LTE1800 Telstra version
The only reason I haven't actuall gone ahead and unlocked is becuase there is actually no point at this stage as we don't have access to any remotely mature custom ROMs, and the only CWM floating around is not confirmed working on our variant (though as long as it doesn't touch the radio, theoretically it should).
Click to expand...
Click to collapse
Ahh crap my bad. Just having flashbacks of the old razr days of people asking if the BL will get or can get unlocked. Carry on. :good:
Aussie retail Razr M unlocked. Confirmed.
Now does any one know what makes the AU different from the US to allow Unlock ?
Germanese said:
Now does any one know what makes the AU different from the US to allow Unlock ?
Click to expand...
Click to collapse
I think they're all dev editions
Sent from my XT907 using xda app-developers app
Germanese said:
Now does any one know what makes the AU different from the US to allow Unlock ?
Click to expand...
Click to collapse
AU isn't on Verizon...
Sent from my XT907 using Tapatalk 2
FacePalm.
Yes we know AU is on Telstra ...
But what are the changes that causes the lock down.
Is it a Physical chip that has been changed or is it a 128Bit encryption that stops ppl from Unlocking the Verizon version ?
Pretty sure it's encryption... I remember seeing an article on how it was done, but no idea where...
Sent from my XT907 using Tapatalk 2
I think I read somewhere that Motorola uses 256bit encryption, but I could have dreamed that for all I know.
Either way, it's going to be tough to crack.
question on bootloader
I restored my firmware using Matt's Utility 1.20 back to 4.1.2 ( previously rooted, bl unlocked, running a rom) , however I cant unlock the bootloader anymore (the M logo shows up even after reboot) even after using the Motopocolypse from drjbliss. Is there anyway to fix this?
pwucky23 said:
I restored my firmware using Matt's Utility 1.20 back to 4.1.2 ( previously rooted, bl unlocked, running a rom) , however I cant unlock the bootloader anymore (the M logo shows up even after reboot) even after using the Motopocolypse from drjbliss. Is there anyway to fix this?
Click to expand...
Click to collapse
You're still unlocked. Try going into bootloader mode - you should still be status 3 unlocked
Sent from my XT907 using Tapatalk 4
sloosecannon said:
You're still unlocked. Try going into bootloader mode - you should still be status 3 unlocked
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
It says that, but I cant flash any roms from CWM? I used root checker and it says I have root, but the SU doesnt seem to be working?
pwucky23 said:
It says that, but I cant flash any roms from CWM? I used root checker and it says I have root, but the SU doesnt seem to be working?
Click to expand...
Click to collapse
Cwm probably got uninstalled when you flashed stock. Just reflash it and it should work
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Cwm probably got uninstalled when you flashed stock. Just reflash it and it should work
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I reflashed CWM but it didnt do anything? When I install a rom it says that it installed fine but when i boot it up, it just boots with the moto logo and boots into stock
wintermute000 said:
No, he's an Aussie , our RAzr Ms are unlockable.
My Australian Telstra branded Razr M spat out an unlock code via the motorola unlock website just like the dev edition phones do. It says right on that website if your phone is ineligible you will receive an error. And I got the code, not the error.
Ausdroid also says explicitly they have confirmation Aussie Razr M is unlockable via moto website.
PJcons, I notice the same discussion on whirlpool, seriously if you don't believe this answer then go and try it yourself, no point asking repeatedly esp as you are confusing people here who have the US CDMA verizon version not the aussie GSM/LTE1800 Telstra version. Also, there is already an existing thread (me lol) http://forum.xda-developers.com/showthread.php?t=1964862
However re: actually unlocking, I can't confirm the last step i.e. actually doing it. The only reason I haven't actually gone ahead is because there is actually no point at this stage as we don't have access to any remotely mature custom ROMs, and the only CWM floating around is not confirmed working on our variant (though as long as it doesn't touch the radio, theoretically it should). But I'm reluctant to do anything without having a stock Telstra fastboot image as a last resort roll-back option, years and years of flashing droids has taught me that if nothing else. Theoretically though I do not see how it could possibly fail if you have the token.
Click to expand...
Click to collapse
I there are telstra xmls & xt905 twrp backups in the dev forum
I made excite? jajajja .... no, I have no way to unlock just open this topic to see if anyone knows how to unlock the devices that do not have developers edition
From what I understand you have an XT926 which can't be unlocked. Only the XT925 & XT926 dev edition can be unlocked through Motorola
Sent from my XT925 using xda app-developers app
saloums7 said:
From what I understand you have an XT926 which can't be unlocked. Only the XT925 & XT926 dev edition can be unlocked through Motorola
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I have xt925 but i think is not the dev edition
juan272 said:
I have xt925 but i think is not the dev edition
Click to expand...
Click to collapse
There is only 1 version of the XT925 and it can be unlocked through Moto the steps are detailed on the moto page
Sent from my XT925 using xda app-developers app
saloums7 said:
There is only 1 version of the XT925 and it can be unlocked through Moto the steps are detailed on the moto page
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I put the fastboot code into moto page but they say that my device not support bootloader unlock
Is that the only restriction? If a code is it, you could just use a fake code, or hex exit in a new code to the unlocking program.
Sent from my DROID RAZR HD using Tapatalk 2
juan272 said:
I put the fastboot code into moto page but they say that my device not support bootloader unlock
Click to expand...
Click to collapse
Double check to make sure you entered the correct code its pretty big might be a typo in there
Sent from my XT925 using xda app-developers app
saloums7 said:
Double check to make sure you entered the correct code its pretty big might be a typo in there
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
I try about 20 times!!!!!!
If you have any apps frozen, unfreeze them and reboot and maybe that will work. If you've removed anything from withing /system, put it back and put the correct permissions and if you don't have those files (if there was anything deleted) then perhaps someone can provide them for upload, then give that a try.
Lastly, if you flashed a ROM that isn't from you carrier or your country, then perhaps using the appropriate tools (I haven't used them so can't point out what they are, other than to say they exist) to put the stock ROM back will allow you to unlock.
Last resort, you can try to get it replaced under warranty stating that you're a developer and need this feature, however if you're rooted I would guess that they'd would be a lot more inclined to check for that replacing a handset as rooting voids the warranty and unrooting, sadly, doesn't remove the info stored on the device that checks to see if the phone had been rooted in the past. You can unroot and if your countries laws are protective enough, though, you might be able to ask them to show how rooting the device caused the failure. In my case, the contract was signed with my carrier who has to be certified as a reseller and they never showed me any warranty documentation, so I was locked into the purchase of the handset over 24 months and am covered by the verbal details of the warranty, which were "everything but physical damage" since they unboxed it and handed it to me activated after I signed. It wouldn't be hard to cancel my contract and hand back the handset if I was refused a warranty repair on these grounds. That they opened the box without me asking is probably enough. That said, consumer protection is top notch in world here.
Short version of the last part though, you can always try a warranty replacement. You'd have to look into if there's a fee in the case that you weren't covered by the warranty. As long as the bootloader is unlocked (and you aren't rooted), you still have you're warranty since the code didn't activate, and I haven't read the page thoroughly enough, but if the page says receiving the code voids the warranty then you can still argue that it was defective prior to receiving it by citing that the code didn't work. If you can unroot, and you live somewhere that the issue of the evidence of your root, or whatever, can be easily turned over to a consumer protection body, then it might be worth the trouble.
Also, you can probably call and ask for a new code. Any way you go about doing any of the above though though, be persistently polite. It goes a long way over trying to be forceful.
I'm likely about to unlike my phone by the way, assuming I can find a ROM that looks appealing enough to try out. I'll try it with the multitude of frozen system apps and the handful of additional ones still in place, first, and see how it goes.
Would it be possible to root the droid razr maxx hd if it is not a the developers edition?? Please help.
brian_199 said:
Would it be possible to root the droid razr maxx hd if it is not a the developers edition?? Please help.
Click to expand...
Click to collapse
If you're on JB then you need to downgrade to ICS using the appropriate ROM for your carrier, use a tool to root, download an app that will allow you to bakcup the root and unroot the device, then upgrade to ICS, then reinsert the root. The instructions are scattered because there's 2 differant models of the phone to deal with and there isn't any consolidated thread that involves all those steps. I haven't had to downgrade and have a differant model than what the maxx version is so that's really as much help as I can be, but the answer is supposedly "yes, you can do this" and its the prefered way for a lot of people from what I gather.
Be sure to backup any data on your sdcard before you begin. I didn't lose any since mine was just keeping root on an OTA upgrade from ICS to JB, but I don't know if you lose it or now when you downgrade.
Hopefully someone else can be more helpful that what I was. There are threads where various carrier versions for both ICS and Jellybean are hosted, as well, so you'lle need to find your carrier's ICS. If it isn't available in the thread then search my posts and someone linked me off to a download for a Telstra ROM and further back in the URL revelealed hosting a heap of ROMS though I wouldn't know which one you would need specifically.
The only issue I ran into, though my experience is possibly only covering half of what's involved for you, was that after I reinserted root, only apps that had permission prior to the upgrade had root permission; I couldn't add any. Other people have had a problem with superuser being inserted with wrong file permissions. The thing I did was to update the binary, this didn't work, then installed SuperSu and updated the binary which also didn't work, then I did a cleanup for installing another su app from the market from withing SuperSU... can't remember from this point, either installed another root app or uninstalled and reinstalled SuperSu (which scared the hell out of me I'd lose root at the time so I think this is what I did), then updated the binary and things were fine. Note that I never uninstalled the regular SU app that the injection tool for ICS put on the phone during this process though. At the end of it, I ended up with SuperSU and no normal su, which the injection tool installs. There hasn't been a huge issue with this though it has happened to some others.
Hi, this might be a stupid question but I've searched and haven't found an answer. Would my Droid Razr M recieve the 4.4.2 ota since I flashed it to use US gsm using radiocomm? thanks
crazy4android said:
Hi, this might be a stupid question but I've searched and haven't found an answer. Would my Droid Razr M recieve the 4.4.2 ota since I flashed it to use US gsm using radiocomm? thanks
Click to expand...
Click to collapse
Yes. But you'll have to go through the process again to enable domestic GSM usage.
Or use cdma workshop
Sent from my LT30p using Tapatalk
just so I'm sure i understand it correctly...I'll just have to flash the radio with radiocomm using the same method as before..or will 4.4.2 need a different method then 4.1.2? thanks in advance
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