Related
From the Motorola website:
https://motorola-global-portal.cust...ldYaksyY0VsIiwic2Vzc2lvbklEIjoiV1hqSzJjRWwifQ..
I would be surprised if we didn't. It's only a matter of how much time Motorola decides to take pushing this update.
Moto X | Stock Unrooted
abiezer said:
From the Motorola website:
https://motorola-global-portal.cust...ldYaksyY0VsIiwic2Vzc2lvbklEIjoiV1hqSzJjRWwifQ..
Click to expand...
Click to collapse
Sweet! Now we just need a date.
dapezboy said:
Sweet! Now we just need a date.
Click to expand...
Click to collapse
I actually reckon we shouldn't get a date.. Issues may pop up that may delay release.. Remember the feeling of frustration when Punit Soni announced that Dev editions would be released in days and it didn't happen for weeks?
Sent from my XT1058
dr3wster said:
I actually reckon we shouldn't get a date.. Issues may pop up that may delay release.. Remember the feeling of frustration when Punit Soni announced that Dev editions would be released in days and it didn't happen for weeks?
Sent from my XT1058
Click to expand...
Click to collapse
Funny you mention that:
"We are moving directly to 4.4. I dont like to discuss timing. It just puts a lot of stress on the team, and there is always a chance we find something which delays us a bit.
Rest assured, we are on it. You have seen the speed with which we are moving as a Google company, that shall continue."
- Punit Soni, https://plus.google.com/+PunitSoni/posts/LAKKMnEE6CQ , scroll way down (or just Ctrl-F a phrase from that quote)
I'm just looking forward to all the awesome things we have in store; just got my MotoX yesterday and got it activated today; less than 12 hours with an activated and working phone, and I love everything it does already. Getting 4.4 is just icing on the cake for me.
Don't get me wrong.. I'm equally impatient lol... But then again, the Moto X runs amazingly on 4.2.2 already
Sent from my XT1058
I'm just wondering, will the bootloader have to be relocked in order to receive the OTA?
sookster54 said:
I'm just wondering, will the bootloader have to be relocked in order to receive the OTA?
Click to expand...
Click to collapse
No, just like the previous update, someone will come up with a flashable zip.
sookster54 said:
I'm just wondering, will the bootloader have to be relocked in order to receive the OTA?
Click to expand...
Click to collapse
The bootloader does not have to be relocked! just make sure that you flash back to stock format including your recovery. And you'll be able to take any and all updates. After you update to Kit Kat you should be able to flash superuser zip in CWM or TWRP. To gain Root.
Sent from non rooted motoX :'(
matt99017d said:
The bootloader does not have to be relocked! just make sure that you flash back to stock format including your recovery. And you'll be able to take any and all updates. After you update to Kit Kat you should be able to flash superuser zip in CWM or TWRP. To gain Root.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
OK that makes sense, I can always restore back to stock then.
I'm keeping my hopes high and my expectations low. I still remember the Atrix after all. New Motorola or not, even if they plan to ship out 4.4 quickly, there is still the carrier issue. I'll believe it when the soak invites go out.
Sent from my XT1058 using Tapatalk
I kept telling all you guys that Motorola was skipping 4.3 and going directly for kit Kat now its come to fruition. You're welcome
Hi,
I have my moto x with the last OTA, i kept root with a tuto that's here.
I want to flash the stock firmware with rsd, my question is if it will take it as downgrade.
I want to wait for KitKat un-rooted.
Thanks
I just got off the phone with a guy from Motorola Brazil.
He clarified a lot of things. Some are good news, others not really.
DISCLAIMER: I am not responsible for any actions you take after reading this. If you try anything and it doesn't work, it's you to you to find a way out. You can always post it here and the community will try to help you. It's your phone. Your actions.
Release Date
He didn't give me a date, rather, he told me the roadmap to it. Motorola is scaling upwards.
G > X > G2 > X+1 > Maxx/Turbo
Reminder: Verizon says when Turbo gets it after Motorola ships it to Verizon.
They are testing the waters on smaller and cheaper devices. Apparently the "under-the-hood" changes are pretty complicated and giving them some headaches. I'd say it makes sense to what @Chainfire has been saying for quite a while now. Many security changes that are affecting how you can interact with the kernel and the init.d process, for example.
Bootloader Unlockability
Moto Maxx is unlockable. All you need is to go to their website and follow instructions. In KITKAT
Apparently, Motorola still hasn't confirmed if they'll allow their customers to unlock the bootloader once Lollipop hits.
Like I said, there's no confirmation. Motorola can always just be a good pal and keep on allowing it, it's all just speculations.
Recovery Firmware
It's the same firmware as the Moto X AND the Moto X 2014. It's up to you to try it out. I might try it next weekend if I got the time.
There are no devs working on Maxx/Turbo AFAIK. However, we can apparently use the firmwares from Moto X or the Moto X 2014.
This topic is the sole reason I added the disclaimer up there. Read it!
The guy told me this, but understand that even though its not a confidential thing, it certainly is extra official. For those who thought a Moto X 2014 TWRP or CWM would brick their devices. Well, apparently, it won't. I'll remove the apparently when I have confirmation on this. Anyone feeling lucky, post your results here or just PM me.
Root
Root is a complicated matter.
In Kitkat.
With the previous information, we might be able to root it following Moto X 2014's instructions. More news in the future.
In Lollipop.
For those who don't know, we should be able to use root, once we patch up the kernel to boot the device allowing root. @Chainfire got it to work without the patch on the Nexus line in SuperSU 2.27, but it's really simple for Google to patch it. Don't expect it to last. Considering the amount of work it takes, we might end up with the shorter stick here. Unless some cool dev decides make it work for us as well, or if the patch for the Nexus 6 somehow work with the Maxx.
Someone will have to try it.
That's it for now. I'll try to update this as new info comes out.
Please, leave a THANKS if you enjoyed it.
Surely these are quite good news. But officially, based on moto website, maxx is not unlockable by now. But these stuff being true is worth of not getting kitkat OTA, to keep the supposed unlockable state, using custom roms, if they someday become available.
ska4fun said:
Surely these are quite good news. But officially, based on moto website, maxx is not unlockable by now. But these stuff being true is worth of not getting kitkat OTA, to keep the supposed unlockable state, using custom roms, if they someday become available.
Click to expand...
Click to collapse
I unlocked mine already. It's just as the site says: get the code, send it to them, they reply with the unlock code
Nice! Thanks for the clarification!
alexcreto said:
Release Date
He didn't give me a date, rather, he told me the roadmap to it. Motorola is scaling upwards.
G > X > G2 > X+1 > Maxx/Turbo
Reminder: Verizon says when Turbo gets it after Motorola ships it to Verizon.
They are testing the waters on smaller and cheaper devices. Apparently the "under-the-hood" changes are pretty complicated and giving them some headaches. I'd say it makes sense to what @Chainfire has been saying for quite a while now. Many security changes that are affecting how you can interact with the kernel and the init.d process, for example.
Click to expand...
Click to collapse
So according to your source, we should be getting Lollipop after all the G's and X's were updated?, if this is the case, I think we should be getting Lollipop really soon, because most of the devices already have Android 5.
:highfive:
Galaxo60 said:
So according to your source, we should be getting Lollipop after all the G's and X's were updated?, if this is the case, I think we should be getting Lollipop really soon, because most of the devices already have Android 5.
:highfive:
Click to expand...
Click to collapse
I don't think that's the case. Both of those devices have a soak test in progress but lollipop has not officially been released to either. Unless I missed a few updates. .
cyberr8der said:
I don't think that's the case. Both of those devices have a soak test in progress but lollipop has not officially been released to either. Unless I missed a few updates. .
Click to expand...
Click to collapse
The soak tests were made before Lollipop was officially released (before Nov 13), but Motorola already made an official state about this here:
http://motorola-blog.blogspot.mx/2014/11/its-time-to-unwrap-android-5-lollipop.html
It seems that Lollipop was already released.
Looks like you're correct. Based on that it seems it is released for certain models. Surprised to see that yet the soak test hasn't started for the turbo. Thanks for sharing.
ska4fun said:
Nice! Thanks for the clarification!
Click to expand...
Click to collapse
I've put my oem unlock key in Motorola website and it says my device is unlockable, but I didn't proceed
I will proceed with the release of the first compatible recovery.
Galaxo60 said:
The soak tests were made before Lollipop was officially released (before Nov 13), but Motorola already made an official state about this here:
http://motorola-blog.blogspot.mx/2014/11/its-time-to-unwrap-android-5-lollipop.html
It seems that Lollipop was already released.
Click to expand...
Click to collapse
Just saw this as well. Seems the soak test for the Verizon Moto X is under way.
http://m.androidcentral.com/soak-test-invites-going-out-2014-moto-x-verizon
The guy mentioned they were testing an internal build for the G2
Firmware for moto x and Moto x 2014 obviously doesn't work,not even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Jaocagomez said:
Firmware for moto x and Moto x 2014 obviously doesn't work, but even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Click to expand...
Click to collapse
yeah I think it's just a first line of support or something like that
Jaocagomez said:
Firmware for moto x and Moto x 2014 obviously doesn't work, but even recovery, first of all the devices are different in hardware and have different device trees, it will simple not flash whoever in motorola that told you that, doesn't know how all this works.
Click to expand...
Click to collapse
I thought it was weird. I even double checked. "Moto X+1 with the Moto X recovery??" and the guy said that he'd done it himself.
Go figure...
Sent from my XT1225 using XDA Free mobile app
Nexus 6 have a same hardware, anyone think if works in maxx?
The recovery for the 6 is for LP and is markedly different than a KK recovery. Also be aware that Troy Dees (TWRP) is on record as saying the recoveries for LP are much more involved than KK and to expect a relatively slow roll out for them to a broader range of devices. He did not say it but the impression I have from reading his comments on this are that marginal devices in terms of number of owners may be waiting a long time or never see a TWRP recovery for LP.
matheus_sc said:
Nexus 6 have a same hardware, anyone think if works in maxx?
Click to expand...
Click to collapse
if nexus 6 already has twrp recovery check if it works, thats the same hardware. just unlock moto maxx bootloader first.
worst case escenario its that TWRP wont work and you'll have to flash stock recovery.img again.
Jaocagomez said:
if nexus 6 already has twrp recovery check if it works, thats the same hardware. just unlock moto maxx bootloader first.
worst case escenario its that TWRP wont work and you'll have to flash stock recovery.img again.
Click to expand...
Click to collapse
once u flash recovery u will lose all ur data
danger2u said:
once u flash recovery u will lose all ur data
Click to expand...
Click to collapse
No... Once u unlock boot loader u loose all your data!
I am not sure what is holding up the root.. Or 5.1, but assuming that a bootloader unlock is not going to swiftly follow the root do you guys think the root will be released in 4.4.4 or will we have to wait until 5.1 is out in the wild for the turbo?
aka848 said:
I am not sure what is holding up the root.. Or 5.1, but assuming that a bootloader unlock is not going to swiftly follow the root do you guys think the root will be released in 4.4.4 or will we have to wait until 5.1 is out in the wild for the turbo?
Click to expand...
Click to collapse
Nobody really knows anything at this point about root, bootloader unlock, or the Lollipop update. I'm assuming (more often than not, though, assumptions are not correct) that the root will be released on KitKat as that is what it was tested on (in the videos you can see he's using KitKat, not a prerelease Lollipop build or anything).
Droid Turbo video uploading to the Root Junky YT channel tonight, according to RJ's G+ post. Here's another post:
There is a new update coming our way.
http://www.androidpolice.com/2015/0...mini-and-droid-maxx-get-a-maintenance-update/
Yeah more B.S. I can't believe this isn't 5.1 this is beyond ridiculous its laughable at this point. At least I'm unlocked and running cm 12.1
sent from "my kungfu is stronger then yours" XT1080
Probably locking down potential exploits.
Sent from my XT1080 using Tapatalk
Hopefully fixing Bluetooth and reception. Both got a lot worse since they started messing with HD voice.
Sent from my XT1080 using Tapatalk
Are they fixing KingRoot and CrashXL's root methods? Even if it was 5.0 though, I wouldn't want to lose root for it after waiting a year or so for it. I hate Verizon...
It's a minor update to fix a rare issue for people making emergency calls on an encrypted phone on boot up. The phone would deliver audio in only one direction, so when you made the emergency call the dispatcher can not hear you.
There was a story about this a few weeks ago, that there was an update coming to the Ultra/Maxx, Turbo, and 2013 X on Verizon, but it isn't Lollipop.
See https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105254
I suppose it's possible that they included other patches, but I am betting it's just this.
[edit] I first saw this a few weeks ago on Droid Life: http://www.droid-life.com/2015/05/0...ntenance-update-coming-to-nexus-6-and-moto-x/
Thanks for the info doogald I won't even bother with this update. I will just wait for 5.1 not worth going back to stock to take the update.
sent from "my kungfu is stronger then yours" XT1080
Just installed the update. I have no idea what it changed.
It may patch the 2 root methods we have.
I used KingRoot to root & put a corrupt version in cache. Lol.
What else could I do with 1hr root?
I have unlocked boot loader and on 4.4.
Do any of these updates lock the boot loader again?
s_u_n said:
I have unlocked boot loader and on 4.4.
Do any of these updates lock the boot loader again?
Click to expand...
Click to collapse
While it is possible, it has never been reported to have happened.
Just installed this update. It did not re-lock the bootloader and I didnt lose root.
chevyrado14 said:
Just installed this update. It did not re-lock the bootloader and I didnt lose root.
Click to expand...
Click to collapse
Thank you for the update; this community is awesome!
Ok said I wasn't going to update and I did I just can't help myself. I hope we get 5.1 soon the moto x is soak testing in a few days so we should be right around the corner. What I can't believe is my wife's turbo still doesn't have 5.1
sent from "my kungfu is stronger then yours" XT1080
Took the OTA update.
Kept Unlocked Bootloader.
SuperUser Root Survival checkecked = Kept Root
Didn't even re-enable bloatware (I always disable all apps/bloatware possible, I do not ever delete them): Took OTA with no problem.
Entitlement Bypass v1.2 Still works.
Definitely noticed one annoying bug that was fixed so far:
After exiting out of Google Play, and collapsing the Google Play app from the Recent Apps list, the Google Play icon would previously re-appear in my notification bar (I believe when left in the notification bar, it was draining more battery, I used to have to Clear data/cache on the Google play App, and then collapsing from the Recent Apps list, in order to avoid it from turning back on. Now, no need for all that. It does not show up in my notification bar any more.
I will update this post if I notice a couple of other bugs that may have been addressed.
Request
Anyone with an unlocked bootloader, willing to test if this OTA patches one of our existing root exploit?
http://forum.xda-developers.com/dro...4-4-su-6-7-t3117552/post60947050#post60947050
Use SuperSu to unroot.
Test out the KingRoot method.
Taking the the ota will unroot as reboot/ota occurs
Try to root with KingRoot.
So, I took four updates since this morning. Bootloader was already unlocked via SunShine and I had root.
I was on 4.4 (19.xxx).
Took the first OTA - moved to 4.4.4 (21.xx). Verified bootloader was unlocked and I was still rooted
Took the second OTA - moved to 23.xx. Verified bootloader was unlocked and I was still rooted
Took the third OTA - moved to 24.xx. Verified bootloader was unlocked and I was still rooted
Took the fourth OTA - moved to 24.13.2. Verified bootloader was unlocked and I was still rooted
So, this dispels the myth that Motorola/ Verizon re-locks the bootloader due to OTA.
I have observed that the battery temperature of the phone has gone up after the updates. Higher battery temperatures mean poor performance.
Earlier the max I had seen was 44. Now, I see 46 as well. The only change is I have switched from a GSM network to CDMA. Maybe CDMA takes up more power and somehow this is heating up the battery.
All temperatures are during charging.
Id agree the mini and ultra will probably never get 5.0. Glad this isnt my personal device, verizon sucks hard.
I've heard Motorola is giving 222.14.x update to what seems like International Moto X. Hopefully, I can get a guy from there to gimme what I need. x)
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105221
mr_verystock said:
I've heard Motorola is giving 222.14.x update to what seems like International Moto X. Hopefully, I can get a guy from there to gimme what I need. x)
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105221
Click to expand...
Click to collapse
I read somewhere that Brazil Moto X 2013 got a Lollipop soak test a few weeks ago
With all the information and side convo - is it possible to be on 444 rooted, and sideload the 5.1 update and still be rooted? If yes, i'd like to see a thread to describe the process, as search yields to much to read in this lifetime, especially witht he xt1225 and not the 1254, and if no, that's great also, and i'll stick to the Nexus 6.
wrecklesswun said:
With all the information and side convo - is it possible to be on 444 rooted, and sideload the 5.1 update and still be rooted? If yes, i'd like to see a thread to describe the process, as search yields to much to read in this lifetime, especially witht he xt1225 and not the 1254, and if no, that's great also, and i'll stick to the Nexus 6.
Click to expand...
Click to collapse
if you are talking about the turbo go check out the development thread there is much written on it. everybody is on rooted LP now i believe. You are still on a mofo rooted turbo running KK?
johnbravado said:
if you are talking about the turbo go check out the development thread there is much written on it.
Click to expand...
Click to collapse
The XT1254 he mentions is the Droid Turbo. Whereas you just said "Turbo", which also is one of the model names of the XT1225 (Moto Turbo).
The XT1225 was released as both the Moto Turbo and Moto Maxx.
To avoid confusion, he stuck to model numbers, not partial model names.
But yes, in the Development section are plenty of 5.1 rooted images for the XT1254 Droid Turbo.
ok so let me understand - the xt1254 can be rooted using mofo, which i have - if i sideload the LLPop, it will still be rooted?
wrecklesswun said:
ok so let me understand - the xt1254 can be rooted using mofo, which i have - if i sideload the LLPop, it will still be rooted?
Click to expand...
Click to collapse
As long as you didn't take the 5.1 OTA, you are OK.
Images and instructions here:
http://forum.xda-developers.com/dro...xt1254-21-44-12-quarkrootwifihotspot-t3064908
http://forum.xda-developers.com/showthread.php?p=61636335
http://forum.xda-developers.com/showthread.php?p=61752986
wrecklesswun said:
ok so let me understand - the xt1254 can be rooted using mofo, which i have - if i sideload the LLPop, it will still be rooted?
Click to expand...
Click to collapse
If you choose a pre-rooted Lollipop 5.1 image to flash, then yes.