Related
I have a motomaker moto x on vzw which is obviously locked...im rooted on 4.4 because i need gravity box at least since i cant get custom roms(ugh) so i havent upgraded to 4.4.2 yet because it hasnt been rooted...my question was has it been rooted because i cant find anything about it anywhere...and if not is anyone working on it? as much as i love this phone i really miss unlocking and rooting
chris420o said:
I have a motomaker moto x on vzw which is obviously locked...im rooted on 4.4 because i need gravity box at least since i cant get custom roms(ugh) so i havent upgraded to 4.4.2 yet because it hasnt been rooted...my question was has it been rooted because i cant find anything about it anywhere...and if not is anyone working on it? as much as i love this phone i really miss unlocking and rooting
Click to expand...
Click to collapse
there is no root method for 4.4.2 (covered extensively). your only option (for now) is to sit on your current version or apply a ROM that gives you 4.4.2 functionality (but you're still on 4.4 kernel).
BUMPING for interest
I feel ya man. I'm also sitting on rooted 4.4 wishing I could update to 4.4.2. I like the stock OS on this phone so I don't feel the need to have an unlocked bootloader, but I would love to be able to have the latest OS version. Although I don't think it's a huge update anyways. I've seriously thought about going back to stock and updating to 4.4.2, but I would miss root WAY too much. I love being able to tether without asking for Verizon's permission.
At least you have root. I'm sitting on 4.4.2 waiting for root. So wish I could use xposed...
underdog1799 said:
At least you have root. I'm sitting on 4.4.2 waiting for root. So wish I could use xposed...
Click to expand...
Click to collapse
Did you order your x from the moto design website? Or from verizen?
doitinthedirt said:
Did you order your x from the moto design website? Or from verizen?
Click to expand...
Click to collapse
Woodback VZW MotoMaker here...
doitinthedirt said:
Did you order your x from the moto design website? Or from verizen?
Click to expand...
Click to collapse
I ordered it from the moto maker website
When did you order it? I placed an order two days ago for a design your own.. a guy here posted he got his two days ago and it had 4.4 on it so thought mine might come with 4.4
doitinthedirt said:
When did you order it? I placed an order two days ago for a design your own.. a guy here posted he got his two days ago and it had 4.4 on it so thought mine might come with 4.4
Click to expand...
Click to collapse
Mine was ordered a month ago or so. I think it probably is hit or miss whether it has been updated or not. But mine was actually on 4.4 and it updated to 4.4.2 overnight
If you realllllly want root....i'd return the phone and get a dev edition. Otherwise you may be stuck on 4.4.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
Or sell it and add some cash for the dev edition if you can't return it. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
If you realllllly want root....i'd return the phone and get a dev edition. Otherwise you may be stuck on 4.4.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
Or sell it and add some cash for the dev edition if you can't return it. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
Well 4.4 would be fine, Im stuck on 4.1.2 as of now on my razrM since they quit updating than.
The first fone i rooted was the razrM and i changed the entitlementcheck to get tethering for my unlimited data.. since than ive accepted two OTA and lost root but the change i made to entitlement check when i had root and write protection disabled still stayed after root was wiped by the OTA. This is puzzling i dont see why guys are loosing entitlement check after losing root with 4.4.2 on moto x
doitinthedirt said:
Well 4.4 would be fine, Im stuck on 4.1.2 as of now on my razrM since they quit updating than.
The first fone i rooted was the razrM and i changed the entitlementcheck to get tethering for my unlimited data.. since than ive accepted two OTA and lost root but the change i made to entitlement check when i had root and write protection disabled still stayed afyer root was wiped by the OTA. This is puzzling i dont see why guys are loosing entitlement check after losing root with 4.4.2 on moto x
Click to expand...
Click to collapse
Basically I think moto saw the exploit and simply closed the door on it. ?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Yeah I'm dying hoping someone will swoop in and help us get a root exploit going. I'm not quite sure why no one has done it...maybe we need to make a thread like the bootloader unlock one where the dev would make some money if they got root going.
Unlocking the bootloader does solve all this. And the bounty is huge.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
You are asking about root, but if you want usable root on the X you need two parts 1. Root Exploit, and 2. An Exploit that allows for disabling Write Protection.
When Write Protection is enabled (the phone's default state with locked bootloader, or the state you are in after you take the 4.4.2 OTA), any changes made to /system, or the like, (including, but not limited to, App installs, file modifications, deletions, renames, etc) are not permanent and are lost at power off/on.
Even if you have root, but lost Write Protection, any apps you've installed that need to write to system can't permanently save their changes (you have to re-do every time your phone powers off/on), and any Root type app, or app that gets installed to /system after WP is enabled will be lost at power off/on.
MotoWpNoMo was used on 4.4. and below to Disable Write Protection. Part of the 4.4.2 update patches the exploit that MotoWpNoMo used, so it wont work on 4.4.2.
SlapMyMoto/RockMyMoto/etc, used on 4.4 and lower, involved downgrading the rom to use an exploit in 4.2.2 to gain root. But with 4.4.2 you can't downgrade the rom safely, without risk of bricking your phone, anymore.
JCASE has already posted he has an exploit to use to gain root on 4.4.2, but due to job and family, wont release it until the fall. Who knows what ROM Moto will push out by then, and if they will have patched the exploit already. BUT before you get made at JCASE for waiting so long, that doesn't address a Write Protection dis-abler. I've not seen any talk about work on that for locked bootloaders (when you unlock the bootloader, like on Dev Editions, the write protection is disabled). So JCASE could release his Root exploit, he or someone could develop that process, but it would be kind of useless without the ability to disable write protection.
Trust me, *IF* or when a Root and Write Protection bypass is out, you will see threads on it. Until then, you have to sit tight.
If you are rooted with write protection disabled, you might want to check out the SafeStrap discussions over at Rootzwiki.com. That might at least afford you a way to run 4.4.2
And of course @kj2112 suggestion of getting a Develpper Edition so you can unlock the bootloader and root no matter what rom version, is the best advice. Yes, its more expensive than a subsidized X, signing a contract, but its worth it if you *NEED* or *WANT* root & write protection disabled. (and selling your current X is an option to get cash towards the Dev Edition)
This website claims root on 4.4.2.
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
Anyone hear or try it yet?
zenofase said:
This website claims root on 4.4.2.
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
Anyone hear or try it yet?
Click to expand...
Click to collapse
It's already being discussed here. I don't think it works as that site claims it does though.
zenofase said:
This website claims root on 4.4.2.
http://www.youmobile.org/blogs/entry/Root-Moto-X-KitKat
Anyone hear or try it yet?
Click to expand...
Click to collapse
As @The Tallest says, its already being disucssed in that other thread.
Even so, *IF* it safely works, it is only a potential root, but does nothing for write protection.
Too bad. At least it's a possible step in the right direction.
So when my Pure Edition Moto X gets here, should I hold off on taking the Lollipop OTA? This is the first non carrier phone i've had since the Galaxy Nexus (~2011) so idk how locked bootloaders and no root works with these phones.
I know with the GS3 and GS4 i made the mistake of taking an OTA that locked the boot loader then i was screwed
Just wondering if I would be better off waiting for some good Roms and flashing them. Or if I can take the OTA then flash roms later if I decide to
Pure edition isn't going to be locked down after updates. You can always unlock the boot loader and wait on ROM's. Being unlocked doesn't keep you from updating. Rooting will stop OTA's though.
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.
Hi All,
I have a non-developer edition AT&T Moto X and I'm thinking about going the route of a custom rom now that it's slowed down a bit since it was new. I've had 4 or 5 android phones in the past, and this is the first one that I have not rooted/modified. So, I suppose my question is, if I'm currently on 4.4.4 with my bootloader locked, will I hinder my ability to later root and flash a new rom if I take the upgrade to 5.1?
Thanks for the help!
Maximum Bob Lutz said:
Hi All,
I have a non-developer edition AT&T Moto X and I'm thinking about going the route of a custom rom now that it's slowed down a bit since it was new. I've had 4 or 5 android phones in the past, and this is the first one that I have not rooted/modified. So, I suppose my question is, if I'm currently on 4.4.4 with my bootloader locked, will I hinder my ability to later root and flash a new rom if I take the upgrade to 5.1?
Thanks for the help!
Click to expand...
Click to collapse
If you are wondering if you can root or unlock your phone to use a custom ROM, I'm pretty sure for that device there isn't currently any way to root or unlock it, there may be some temporary root methods, but don't really know, but unlocking the bootloader would only be if a new exploit is found with Sunshine, or if the China middleman reappears, which is how I unlocked
So I bought the phone just now. Paid quite a lot because they don't exist in my country , but I've wanted it since it got out, and it's in like brand new condition so ehhh, why not I said..
Just checked and phone is on Marshmallow 24.81.5quark_verzion.verzion.enUS
Tried Kingroot and sunshine to at least achieve temproot , they both failed.
What are my options right now here?
Thanks!
No unlock options right now if you are on stock 6.0.1 with a locked bootloader.
ChazzMatt said:
No unlock options right now if you are on stock 6.0.1 with a locked bootloader.
Click to expand...
Click to collapse
Thanks for reply! I guess I'll just live with it. Iphone in motorola's body lol. But for discussions sake, any way to downgrade? I know flashing bootloader triggers the "fuse" but I was succesfull with some weird bootloader downgrades in the past wtih 201M (Japanese softbank version of Razr M) and IS12M (JP KDDI version of Droid Razr).
Only problem is, this phone is way to expensive for me to experiment..
Ej?iSixo said:
Thanks for reply! I guess I'll just live with it. Iphone in motorola's body lol. But for discussions sake, any way to downgrade? I know flashing bootloader triggers the "fuse" but I was successful with some weird bootloader downgrades in the past wtih 201M (Japanese softbank version of Razr M) and IS12M (JP KDDI version of Droid Razr).
Only problem is, this phone is way to expensive for me to experiment..
Click to expand...
Click to collapse
Hmmmm... then you were very lucky because gospel around here is you can never downgrade the Motorola bootloader. If you could downgrade bootloader, then everyone would go back to version where Sunshine worked! First Sunshine worked on Lollipop SU4TL-44 (November 2015), then everyone who procrastinated rushed to take SU4TL-49 (May 2016), hoping it was Marshmallow. Nope, it was just a Verizon "security" update to stop Sunshine from working. They had SIX MONTHS to unlock their bootloader and they didn't do it! Then everyone complained and said if only Sunshine worked on "49", they wouldn't procrastinate anymore. BOOM. A few months later (july 2016) Sunshine found another exploit and it works also on Lollipop "49".
But we are STILL seeing people now taking the Marshmallow OTA (November 2016) without unlocking bootloader first. Not you, you said you bought it with it already installed...
One of the Sunshine team members said he briefly glanced at the 6.0.1 OTA and it might not be impossible to unlock the bootloader. But no promises and no ETA. I don't think this phone is a high priority anymore. This is now a 2-year old phone. Still GREAT, but other newer phones get attention. There's been Sunshine for it since November 2015 and most everyone who wants it has had a chance to get it.
ChazzMatt said:
Hmmmm... then you were very lucky because gospel around here is you can never downgrade the Motorola bootloader. If you could downgrade bootloader, then everyone would go back to version where Sunshine worked! First Sunshine worked on Lollipop SU4TL-44 (November 2015), then everyone who procrastinated rushed to take SU4TL-49 (May 2016), hoping it was Marshmallow. Nope, it was just a Verizon "security" update to stop Sunshine from working. They had SIX MONTHS to unlock their bootloader and they didn't do it! Then everyone complained and said if only Sunshine worked on "49", they wouldn't procrastinate anymore. BOOM. A few months later (july 2016) Sunshine found another exploit and it works also on Lollipop "49".
But we are STILL seeing people now taking the Marshmallow OTA (November 2016) without unlocking bootloader first. Not you, you said you bought it with it already installed...
One of the Sunshine team members said he briefly glanced at the 6.0.1 OTA and it might not be impossible to unlock the bootloader. But no promises and no ETA. I don't think this phone is a high priority anymore. This is now a 2-year old phone. Still GREAT, but other newer phones get attention. There's been Sunshine for it since November 2015 and most everyone who wants it has had a chance to get it.
Click to expand...
Click to collapse
Yeah I read whole how to unlock bootloader thread, from 1st to last page but havent' seen anything marshmallow specific so I opened this topic..
Yeah , I was also surprised, but I spent around 1 month working on it , and it was only working with specific firmwares (fastboot files).
Yeah I wish I checked little more about that issue , I would check phones OS and probably not buy when I see it's MM.. Oh well, no going back now.. Thought that verzion's control freak behavior stopped by the time of droid turbo( used some verzion motorola phones in the past) especially when google bought motorola.
I hope people don't see this phone as outdated, because there is no way it can be called that. Many people including myself figured it like a replacement for nexus , and I think it deserves at least root exploit..
Also asked in Sunshines thread about support for marshmallow , got rather unclear response:
Me:Will there be support for droid turbo on marshmallow? Just purchased the phone, didn't know unlocking bl was possible only on lolli... Thanks
jcase: Known at this point,
EDIT: damn I write yeah a lot lol. P.s if mods want to delete topic because it's useless, feel free. Thanks!
EDIT 2: By checking system updates looks like phone was updates 3 days ago so 1 day before I bought it .. Arrrghhhh!!!
BTW I just remembered, "old" Droid 's ( xt910 ,xt912 etc) bootloader was never ever unlocked , but there was a way around it. Safestrap recovery by Hashcode , which I'm sure you all know about. The project is scraped because dev is busy , but I really wonder if anything like that is possible on droid turbo. I also wonder how does it work exactly and what gets bypassed.
From users standpoint: you installed apk which then installed recovery that "bypassed" locked bootloader and allowed you to install /load custom roms, kernels , radios , root etc.. You could even install more OS's at same time like on another "partitions".
hm...
EjđiSixo said:
BTW I just remembered, "old" Droid 's ( xt910 ,xt912 etc) bootloader was never ever unlocked , but there was a way around it. Safestrap recovery by Hashcode , which I'm sure you all know about. The project is scraped because dev is busy , but I really wonder if anything like that is possible on droid turbo. I also wonder how does it work exactly and what gets bypassed.
From users standpoint: you installed apk which then installed recovery that "bypassed" locked bootloader and allowed you to install /load custom roms, kernels , radios , root etc.. You could even install more OS's at same time like on another "partitions".
hm...
Click to expand...
Click to collapse
sorry for keeping this post alive, but i really really miss Safestrap when i had the Moto Droid Razr, you could have up to 4 different ROMs installed and it took minutes to swap between them. Man those were the good ole days haha
Edit: added word droid
weaver11b said:
sorry for keeping this post alive, but i really really miss Safestrap when i had the Moto Razr, you could have up to 4 different ROMs installed and it took minutes to swap between them. Man those were the good ole days haha
Click to expand...
Click to collapse
I remember being frustrated about never-unlockable bootloader while using safestrap at same tame and then realised, hey wait! What do I need unlocked bootloader anyway , everything works perfect and functionality is even better than on most modded phones (at the time).
Having something like this on droid turbo would make it a perfect phone in my opinion, and for years to come.. Wonder whats the dev's view on droid turbo on that..
Anyway I was playing a little, all within "safe zones" regarding the downgrading . With litlle modding I could flash bootloader.img from QUARK_VERIZON_5.1_SU4TL-49_cid2_subsidy-DEFAULT_CFC.xml.zip and most of partitions related to bootloader I collected from various locations,all from SU4TL but it's obviously not important..
So basically what I can't flash to downgrade is :
gpt.bin
boot.img
system files (system,img_sparsechunk.0 , 1 , 2 etc).. I will investigate more.
Started finally actually using phone , all bloatware can be disabled, so it's actually pretty ok for now. Phone feels awesome ..
Mods , please delete this topic in purpose of cleaning, I'm gonna open 2 topics regarding downgrading experiment and making SBF of new Marshmallow OTA