[Q] Moto X Developer Edition 4.2 Verizon Unlock/Root - Moto X Q&A

Getting my X Dev Ed. this morning. I think it will be running 4.2. Quick question. Do I unlock, then root on 4.2, then update to 4.4, then reroot?
I ask this because I have been reading about updating to 4.4, then downgrading to 4.2.2 camera update (is this Android 4.2 or something else?) I have never unlocked or rooted a phone and want to do it right the first time. Thanks for the help!

On a Developer Edition, just take the updates/upgrades to get to the latest version.
Once that is complete, unlock the bootloader, flash twrp recovery and install root.
Developer Editions are really easy to work with because you can unlock the bootloader., no need to jump through hoops working around a locked bootloader.

tcrews said:
On a Developer Edition, just take the updates/upgrades to get to the latest version.
Once that is complete, unlock the bootloader, flash twrp recovery and install root.
Developer Editions are really easy to work with because you can unlock the bootloader., no need to jump through hoops working around a locked bootloader.
Click to expand...
Click to collapse
Thanks! I have unlimited data as well. I would like to run stock, but NEED to be able to wifi tether via hotspot. What do you recommend flashing to be able to do this natively? or should I uset Android Wifi Router from the play store?

Since you have a developer edition, take any OTA updates... then to root follow -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
For tethering.. there are two options...
On my VZW X Dev Ed, I have been successful using used the wifi_tether_v3_4-experimental1.apk from https://code.google.com/p/android-wifi-tether/
change device profile to galaxy nexus (cdma/lte)
check box: wifi-driver reload
check box: enabled routing fix
Another popular way can be found here -> Native tether for VZW DE 4.4

As far as tether, there is a flashable .zip that makes things really easy. Download and flash ramework-res_VZW_Tether.zip from this here:
http://forum.xda-developers.com/showthread.php?t=2561560

just make sure when you flash the recovery that you boot into recovery before allowing your phone to boot into android or your recovery wont work.

Related

[Q] T-Mobile/Unlocked GSM Moto X Root

Okay, got a strange question here. I plan on going from the N5 to the unlocked GSM MotoMaker Moto X version. All I want is root with stock recovery (don't really care for a custom recovery, plus I'd like to still receive OTAs). Can I unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU? Or do I *have* to flash TWRP to achieve root?
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".
or
use one of the methods in the original android development section to achieve root.
c19932 said:
correct me if im wrong, but I think you can "unlock the Moto X bootloader, load TWRP recovery (instead of flash), and then install SuperSU".
or
use one of the methods in the original android development section to achieve root.
Click to expand...
Click to collapse
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root.
TheCuban said:
Yes, I've looked at those threads. However, in 4.4, a backdoor needs to be introduced in order to maintain root. I'd rather not have to do that and I don't mind unlocking bootloaders. This will be my first, non-Nexus device in awhile, so I just wanted to make sure I can just unlocked the bootloader, load a custom recovery, flash SuperSU and then just have root.
Click to expand...
Click to collapse
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto
Sent on my Moto X
flashallthetime said:
Just unlock your boot loader, flash twrp recovery and finally flash supersu and you're good to go. Ota's can not be accepted and flashed with root or custom recovery on the moto
Sent on my Moto X
Click to expand...
Click to collapse
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
TheCuban said:
Thanks! That's what I thought! I didn't know that root removed the ability to accept OTAs?
Click to expand...
Click to collapse
On the moto yes, nexus devices are a different beast
Sent on my Moto X
Hi I am planing my first root and I am honestly a little confused. I am on TMobile with 4.4 KitKat (Moto X).
I understand how to unlock the Bootloader and that I need to install TWRP before I can activate SU.
I am just not sure about the bugs (if any) with TWRP and what version to use.
The reason for my concern is on the TWRP website the Moto X is not listed as a supported device.
Is this video Tutorial still valid - is this how to do it with 4.4 KitKat?
And is this the latest version that works (what are the known bugs)?

Question about unlocked/rooted VZW Moto X

So I really miss rooting and modding my phones so I was thinking about do that Chinese method of unlocking my verizon wireless moto x. I just have a couple questions if anyone could answer I'd appreciate it. I can't find much info about 4.4.2 for the verizon moto x because before this unlock discovery, it wasn't possible
1. Once I unlock, is rooting just a simple adb command away?
2. Will I still be able receive android updates via OTA from verizon in the future? Assuming I remain on stock rom and don't flash a rom.
3. My main goal would to be able to tether. So is there a xposed mod to enable tethering on stock rom?
I've only seen this info for DE Moto Xs' and outdated info so I just want to be as updated as possible before I decide to do this.
tu3218 said:
So I really miss rooting and modding my phones so I was thinking about do that Chinese method of unlocking my verizon wireless moto x. I just have a couple questions if anyone could answer I'd appreciate it. I can't find much info about 4.4.2 for the verizon moto x because before this unlock discovery, it wasn't possible
1. Once I unlock, is rooting just a simple adb command away?
2. Will I still be able receive android updates via OTA from verizon in the future? Assuming I remain on stock rom and don't flash a rom.
3. My main goal would to be able to tether. So is there a xposed mod to enable tethering on stock rom?
I've only seen this info for DE Moto Xs' and outdated info so I just want to be as updated as possible before I decide to do this.
Click to expand...
Click to collapse
1. after you unlock the bootloader Rooting is as easy as installed TWRP or CWM then flashing SuperSU flashable sip and your rooted.
2. yes you will still get OTA updates. but in order to use the OTA update you will have to reflash the stock recovery. then take the update and reflash TWRP or CWM and SuperSU and your rooted again.
3.yea there is
hope this answered all your questions.
^^ this
Also, with an unlocked bootloader....you now have a phone that is no different than a dev edition. Aside from your warranty.
There's nothing else special about the dev edition. You keep your warranty on a DE.....that's where its specialness ends.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
dray_jr said:
1. after you unlock the bootloader Rooting is as easy as installed TWRP or CWM then flashing SuperSU flashable sip and your rooted.
2. yes you will still get OTA updates. but in order to use the OTA update you will have to reflash the stock recovery. then take the update and reflash TWRP or CWM and SuperSU and your rooted again.
3.yea there is
hope this answered all your questions.
Click to expand...
Click to collapse
Yeah thanks a lot! My plan would be to just run stock software but just add the tethering xposed module. But my main concern was receiving future OTAs so it's good to know that I still can. Is it pretty safe to root/unlock this phone? My galaxy nexus was a breeze(obviously being a nexus), but like my S3, there was no flashing back to stock recovery, taking OTA, an than flashing CWM again. At least it wasn't as easy as you described lol I think because there was always concern about whether the update removed ability to root access. Is that possible with this phone or with the unlocking of the bootloader, does that take that variable out? Thanks again. Oh yeah last question, once I'm unlocked, can I lock it back up again and go back to completely stock if I wanted to for some reason? Or is it a done deal.
tu3218 said:
Yeah thanks a lot! My plan would be to just run stock software but just add the tethering xposed module. But my main concern was receiving future OTAs so it's good to know that I still can. Is it pretty safe to root/unlock this phone? My galaxy nexus was a breeze(obviously being a nexus), but like my S3, there was no flashing back to stock recovery, taking OTA, an than flashing CWM again. At least it wasn't as easy as you described lol I think because there was always concern about whether the update removed ability to root access. Is that possible with this phone or with the unlocking of the bootloader, does that take that variable out? Thanks again. Oh yeah last question, once I'm unlocked, can I lock it back up again and go back to completely stock if I wanted to for some reason? Or is it a done deal.
Click to expand...
Click to collapse
the unlocking the bootloader process is kind of a pain but not too bad.
custom recovery and root are as simple as one command and one flashable zip
as long as you follow directions and read before doing anything then it should be safe. but rooting and modifying your phone is never %100 save.
when you unlock your bootloader you will always be able to root your phone no matter what android version your on. but it is always possible that they make some crazy change and we have issues.
once unlocked you can relock with with "fastboot oem lock" but that stupid warning msg about you bootloader being unlocked won't go away unless you flash a custom boot screen.
i hope i answered all your questions to your full needs and if you have any more please feel free to ask here or PM me if need be.
Unlocking the bootloader is pretty easy if you have adb setup. Don't forget to backup via helium (download to computer or cloud not local.) since unlocking will delete everything and helium can work without root.
Xposed module is great, less intrusive than flashing roms and you can easily get the tethering, etc.
Sent from my Nexus 7 using Tapatalk

Moto X HELP! I think i bricked it after update!

Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Resurrecting A Bricked Moto X
drvoje said:
Hello,
I got my Moto X few days back from America, its Verizon model (I live in Europe)
its not developer edition and bootloader is locked
...and first issue i noticed is when i try to reset to factory with power UP + DOWN volume i couldnt get recovery.. when i go to recovery settings i see moto logo and then verizon picture.. there is no "dead android" and phone boots normaly.
...second thing there was android 4.4 on it and i got notifications to update it, so i was like why not, lets do it... and after i decided to update, phone keeps rebooting itself, and i dont know what to do it stays awake like 10-20sec and reboot again. Cant belive i bricked it that way!
Phone seems that its not rooted or anything, but idk maybe it was and then back to stock.. Is there any solution?
Thanks in advance to any1 who can help me slove the problem
Cheers
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
Is there any way to try to delete chache or factory reset before flashing to stock rom
drvoje said:
Is there any way to try to delete chache or factory reset before flashing to custom rom
Click to expand...
Click to collapse
If its not the developer edition for Verizon, the bootloader is likely locked, so you can NOT flash custom roms (unless you, or a previous owner, got a bootloader unlock code from the China Middleman and used it)
Did you buy the phone used, or new? If used, then it is possible that it was rooted using RockMyMoto, SlapMyMoto or the like... and the boot loop while trying to install an update could be due to that. If so, erasing cache will stop the boot loop. This can be done from stock recovery, or when in Bootloader/FastbootAP mode.
How to Boot into recovery -> http://mark.cdmaforums.com/MotoX-EnterStockRecovery.htm
If that doesn't work, try bootloader/fastboot....
How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup -> http://mark.cdmaforums.com/ADB.htm
How to boot the phone into fastboot mode -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm
from your PC, do a mfastboot erase cache
to reboot the phone, mfastboot reboot
Optionally, you could do a mfastboot erase userdata before rebooting, to remove all data, apps, etc.
If erasing cache fixes the boot loop, you might just want to try using RSDLite and reflashing the STOCK rom, recovery, etc. (Download the Verizon 4.4.4 SBF from -> http://sbf.droid-developers.org/phone.php?device=0 then follow -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 ) It would undo anything that was done to root your device, and put you back to factory fresh. The only reason not to, would be if you care about rooting and disabling write protection..
With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader).
Once your phone is on 4.4.2 or above, you can't properly downgrade the ROM, bootloader and gpt.bin to use the exploits used by SlapMyMoto/MotoWpNoMo. There is a TowelPieRoot which is a temp root that works on 4.4.2. Temp root in the fact that it doesn't survive power off/on, so it needs to be redone each time. Also it doesn't disable write protection, so any changes made to /system or the like are also lost at power off/on (aka hard boot).
Once on 4.4.4, you can't properly downgrade the ROM, bootloader and gpt.bin, and there are no exploits to root, and no way to disable write protection.
If you can use the China Middleman thread to get a bootloader unlock code, then you don't need to worry about the exploits, and you can then root and disable write protection just as if you had a developer edition. Also JCASE may be updating their Sunshine tool to use the exploit found by Dan Rosenberg to unlock the bootloader on the Moto X, but there is no exact date yet of when it will be available (so far "next few weeks" has been said, but nothing more specific), and there is discussion around will it work for those who took the 4.4.4 update or not (no confirmation yet either way).
KidJoe;55503494
If that doesn't work said:
[*]How to get a working AndroidSDK/PlatformTools/ADB/Mfastboot setup ->
[*]How to boot the phone into fastboot mode ->
[*]from your PC, do a mfastboot erase cache
[*]to reboot the phone, mfastboot reboot
[/list]
Click to expand...
Click to collapse
did this with mfastboot image and worked like charm
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
and tnx for the help again mate
drvoje said:
bdw now i will need some time reading what is best to do with my unlockable bootloader verizon phone, if u have any sugestions please let me know.
Click to expand...
Click to collapse
You said its a verizon phone, but not the developer edition..
So at this point, the only way to unlock the bootloader is the China Middleman thread (in the general section). When JCASE updates Sunshine for the X (in the coming week or two), you can try that.
Otherwise, there isn't anything you can do.
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
drvoje said:
and for stock android update? which one is the best for moto x? now it is 4.4.0
shall i rsd lite it to 4.4.2 or 4.4.4 or just stay current one?
bdw i need to rsd lite frimware anyway if i plan to use OTA update again perhaps when android L come? For now i just keep ignoring them
and yes its NOT developer edition phone
Click to expand...
Click to collapse
THe best depends on what you want to do.
Like I said before. IF you have 4.4 (aka 4.4.0) on the phone, and NEVER had anything newer on there (not 4.4.2 or 4.4.4), then stay there, look at SlapMyMoto and MotoWpNoMo to root and disable write protection.
Once you get 4.4.2 on there, you can root, but its temp root, and write protection can NOT be disabled.
4.4.4 you can't root.
Other than that, I can't say I really find too much difference. The camera is better in 4.4.4, but the battery isn't performing as well lately (could be a recent app update).
can i do this on my phone now - without fear of bricking it:
from my pc to run mfastboot again
then to clear chache
then to delete all user data
then to use rsd lite and flash Android 4.4
Blur_Version.140.45.5.ghost_verizon.Verizon.en.US even i alrdy have 4.4 now?
..because i dont know what is done to my phone before and i want to make sure its like "new" device
i know i can not downgrade, but can i flash same frimware? just to make sure thats all stock again
bdw Im stll unable to enter recovery after fastboot :/ is it that because of locked bootloeader? or because it was rooted with any method? i cant find superuser
and then to wait for solution to unlock bootleader?
Thanks in advance
You can always re-flash the same rom that is on your phone.
You just never want to down grade, or flash something older than what is on your phone.
As for not being able to enter Stock Recovery... early versions of the RockMyMoto and such did a trick which made it so that when you picked boot to recovery, it booted to regular system with write protection disabled. If that was used on your phone before you purchased it, that could be the issue. Using RSDLite and flashing back to 100% stock will undo that.
But You never answered if you got the phone new or used.
IF new, then you have some other issue (either you're not doing it right, or there is something wrong with the phone).
If used, you don't know what was done before you received it. Someone might have rooted, etc.. then just removed SuperSU to appear non-rooted when selling, rather than flashing back to stock.
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i made this screenshots, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
drvoje said:
thanks for the reply...
yes phone is used before but same like new... and what i found that phone was rooted by some method.. i found this screenshot in phone, look in attachment..
bdw i dont see super su anywhere in apps? how to remove?
and i got everything rdy to flash it, i was just waiting you to conform if its doable...
Click to expand...
Click to collapse
If you mean you don't see a SuperSU icon in the app drawer, then they probably un-installed SuperSU before selling it rather than completely unrooting. If you mean you have an icon in the app drawer, but don't see it to uninstall under Settings -> Apps.. I don't know why that would be.
drvoje said:
and what did u mean by this:
"With a locked bootloader, If your phone is still on 4.4 (aka 4.4.0), and still has that older bootloader and gpt.bin, you could use SlapMyMoto to root, and MotoWpNoMo to disable write protection. Just don't take any updates. You could cause a bootloop, but more importantly it will re-enable write protection with no way to disable it again (unless you can unlock the bootloader)."
is that what happened to me?
Click to expand...
Click to collapse
Yes, that could be what happened to you. There are many reports of locked bootloader users who used those older root processes who then upgraded using the OTA from 4.4 to 4.4.2 that encountered bootloops and other issues. It was often recomended to reflash to 100% stock.
And what I meant is that if you are on 4.4 (aka 4.4.0) with all its parts, it is vulnerable and the older exploits can still be used to root and disable write protection without unlocking your bootloader. Search for SlapMyMoto for more details. Some people tried to be cute and mix/match parts which caused issues. Mostly the issues around downgrading are caused by GPT.BIN and Motoboot.IMG parts, their versions, if they've been upgraded and no longer match the rest of the rom on the phone, etc. (and that is a LONG story...)
drvoje said:
and have question about one more thing
my country does not support lte and in my region 3g is bad... i have stable signal all the time but i would like to use edge only (GSM), can i do that using some widgets and if can which ones?
Click to expand...
Click to collapse
You can TRY using something like LTE On/Off to open the hidden menu and set for GSM Auto (PRL) or LTE GSM Auto(PRL). I'm not sure which would work best.
Oh, and as for unlocking the bootloader, I've mentioned the China Middleman and JCASE's Sunshine so there are the links to read up if you want to do it.
The China Middleman is just like if you got the code directly from Moto. I don't know what the Jcase tool is like yet.
thanks again!
so i dont see a SuperSU icon in the app drawer - uninstalled probably and that is why i can not enter stock recovery
I am still on android 4.4 didnt do anything yet...
what u recommend me to do? to rsd lite it to 4.4 again? right?
than i will root my device
and about bootloader, my device is 9.2013, so i will wait JCASE's Sunshine and support him
ps. wiget works gr8 :good:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Now you can update to 4.4.4,whichever methods you want, and still root it. Done. ?
drvoje said:
Just want to write some words, i just took jcase tool which is very easy to setup (made for noobs like me) and i got bootloader UNLOCKED on my verizon NON developer edition phone
and now i RSD lite to 4.4 stock rom
would like to hear from KidJoe what is best to do with my moto x now thanks
Click to expand...
Click to collapse
Follow [mention]@KJ[/mention] 's advice and update to 4.4.4, and follow the Dev Edition or Unlocked Bootloader guides to rooting (flash the latest TWRP and root.)

[Q] Need some advice concerning Bootloader Unlocking. (XT1058)

Hi, after some months playing (and loving) my Moto X, I decided it's time to start flashing roms and messing around with it. I used to do this a lot on my Xperia phones, since it was simple. However, Motorola's phones are kind of hard to even root, so for the first time ever, I find myself in the need of unlocking the bootloader because my career will most likely ignore the 5.0 update for the Moto X.
I'm currently using a Xt1058 with 4.4.2. The update for 4.4.4 was just released TODAY, but I'm afraid I won't be able to unlock the bootloader if I update it. So I was wondering if it's possible to unlock the bootloader on 4.4.2 and then flash a 4.4.2/3 ROM from either T-Mobile or generic Brazil (since I heard those update quickly) in order to ensure my update to 5.0. So here are my questions:
1) Is it possible to unlock the BL with my current settings?
2) Is it simple? I've never unocked a BL before.
3) Is it easy (and possible) to flash ROMs from other careers? Will I need to manually install Lollipop if I do that, or will I just get an OTA update?
4) Will I lose all my data?
5) If I mess something up during the process, can it get fixed?
6) Can I unlock bootloader on 4.4.4 and just update my phone via OTA?
1. Sunshine. Google it.
2. Possibly since you never have before
3. Not worth it for your reasons
4. Yes
5. Maybe
6. No

Having issue with 4.2.2 JB. update need help

Just got my Moto x Verizon branded and came with 4.2.2 JB. For some reason when I hit the update it says I'm on the latest firmware. Any idea what's going on here. Im currently situated in Dubai but not sure how that would have anything to do with it. Any help?
Sent from my XT1060 using Tapatalk
yes, update moto update services via playstore. I dont own a vz X but I suggest you check your bootloder unlock option if interested before updating.
Yes root and unlock it now, because 4.4.4 root isn't quite ideal yet.
Sent from my XT1060 using Tapatalk
bushako said:
Just got my Moto x Verizon branded and came with 4.2.2 JB. For some reason when I hit the update it says I'm on the latest firmware. Any idea what's going on here. Im currently situated in Dubai but not sure how that would have anything to do with it. Any help?
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Did you buy it used? If yes, then its possible that the previous owner rooted and disabled the OTA update check. Especially if this is NOT a Developer Edition for Verizon.
Now, if it was purchased new, or the original owner didn't disable the OTA update check, then its likely because you are not on Verizon's network. I've seen this happen on my BB Z10, galaxy S4 and S5, and my Moto X, when running wth my t-mobile sims or on wifi. They will always say either no update found (90% of the time), or Update service not available (10% of the time). I must put my Verizon SIM in to download the update.
Since both the Developer and Non-Developer XT1060 for Verizon use the same ROMs you can download and manually flash the SFB/FXZ files from Moto Directly... -> HERE If you have the Non-Developer XT1060 and you want to unlock the bootloader, do NOT flash anything newer than 4.4.2!!
Use the link in my signature about the Risks of Downgrading to confirm your phone's bootloader version to get a better understanding of your phone's state.
IF you want to root and disable write protection going forward, you need to unlock the bootloader, and you do NOT have the developer edition for Verizon, the only option for that would be to use Sunshine to unlock the bootloader BEFORE you upgrade it to 4.4.4 or higher. For more... see HERE
KidJoe said:
Did you buy it used? If yes, then its possible that the previous owner rooted and disabled the OTA update check. Especially if this is NOT a Developer Edition for Verizon.
Now, if it was purchased new, or the original owner didn't disable the OTA update check, then its likely because you are not on Verizon's network. I've seen this happen on my BB Z10, galaxy S4 and S5, and my Moto X, when running wth my t-mobile sims or on wifi. They will always say either no update found (90% of the time), or Update service not available (10% of the time). I must put my Verizon SIM in to download the update.
Since both the Developer and Non-Developer XT1060 for Verizon use the same ROMs you can download and manually flash the SFB/FXZ files from Moto Directly... -> HERE If you have the Non-Developer XT1060 and you want to unlock the bootloader, do NOT flash anything newer than 4.4.2!!
Use the link in my signature about the Risks of Downgrading to confirm your phone's bootloader version to get a better understanding of your phone's state.
IF you want to root and disable write protection going forward, you need to unlock the bootloader, and you do NOT have the developer edition for Verizon, the only option for that would be to use Sunshine to unlock the bootloader BEFORE you upgrade it to 4.4.4 or higher. For more... see HERE
Click to expand...
Click to collapse
I got it brand new sealed box cost approx $122 16GB, so no chance of it being rooted. I'm glad that it's still JB, read that part of 4.4.4 being not unlockable at the moment. So I just made the payment for Sunshine now waiting for either of the devs to wake up and send me those sweet digits to unlock. The phone came with a Verizon sim card in it but I get a message saying its unrecognizable but that's okay It's customs roms all the way for me from here.
Sent from my XT1060 using Tapatalk
@bushako @hbenz2008 @metaljr81 @KidJoe
You are all now in a new thread.

Categories

Resources