Related
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!
In case people did not know, T-Mobile has an update status page for Android devices. You can see how far along the 5.0 update has come for your device. It was mentioned on Phonearena.
https://support.t-mobile.com/community/phones-tablets-devices/software-updates#tmoSUPDocTitle
Bit pointless for this section, as there's no Z3...
Sent from my D6603 using XDA Free mobile app
It means Sony has not updated TMO with the info yet. That is understandable considering the international models don't even have a test version according to PTRCB. Once it's in testing (for TMO version: D6616) it will be listed.
Since you have the international version you will probably get it much earlier than us.
The Z1/Z3 are finally mentioned, status shows as "Manufacturer Development".
Now Z1s and Z3 in 2nd stage.
Sent from my D6616 using Tapatalk
ngvuanh said:
Now Z1s and Z3 in 2nd stage.
Sent from my D6616 using Tapatalk
Click to expand...
Click to collapse
Proof? I still see them in Manufacturer Development.
My bad. I thought those devices listed under T-Mobile Testing are updated list.
Sent from my D6616 using Tapatalk
I doubt we will get it before the international versions.
abhinav.tella said:
I doubt we will get it before the international versions.
Click to expand...
Click to collapse
Yep. Seems like a long wait..
Looks like bad news for the Z3, they are saying update is "Months" away not weeks.
"We’re working very hard on the Xperia Z3 Lollipop update for T-Mobile customers – and to ensure customers get the best possible experience with this update. We’re hoping to roll it out in upcoming months and will share more details as they’re available." -T-Mobile
Source:
http://www.theverge.com/2015/5/1/85...to-t-mobile-but-android-lollipop-update-could
Got root now...don't even care anymore!
That was fast, great timing lol.
lvlonkey said:
Got root now...don't even care anymore!
Click to expand...
Click to collapse
Same here. Sony and T-Mobile are probably sad that this phone is now rooted lol I'm surprised that they tried very hard to block people from rooting it but screw them!
Root alone won't let you update to a generic 5.0.2 ROM though. Still need to unlock the bootloader.
Artood2s said:
Root alone won't let you update to a generic 5.0.2 ROM though. Still need to unlock the bootloader.
Click to expand...
Click to collapse
No you do not. You can have root on a Sony lollipop rom with a locked bootloader.
However, if you mean CM or AOSP etc, then you always need an unlocked bootloader for that
gregbradley said:
No you do not. You can have root on a Sony lollipop rom with a locked bootloader.
However, if you mean CM or AOSP etc, then you always need an unlocked bootloader for that
Click to expand...
Click to collapse
i had rooted and installed recovery in my d6616 already, that means my phone can flash international rom 5.0 ????
lethang90b said:
i had rooted and installed recovery in my d6616 already, that means my phone can flash international rom 5.0 ????
Click to expand...
Click to collapse
If you have recovery you can create a pre-rooted flashable zip from a lollipop FTF for your device and flash it.
gregbradley said:
If you have recovery you can create a pre-rooted flashable zip from a lollipop FTF for your device and flash it.
Click to expand...
Click to collapse
thanks. i found some rooms that have pre-rooted, such as [D66XX]{5.0.2} Flashable stock Lollipop pre-rooted collection & XZ dualrecovery
I assume that wifi calling will be lost with an international ROM. How about HD voice?
T-Mobile Z3 update got certified! (23.1.C.0.381)
https://www.ptcrb.com/vendor/complete/view_complete_request_guest.cfm?modelid=26399
Not yet listed as "testing" on TMO site though, so I don't know if they received it it yet.
Source: David Schuster - https://plus.google.com/+DavidSchuster/posts/cV4vDyyMmw2
LATEST UPDATE [06-19-2015]
Full deployment has started for US Retail, Brazil Retail and Rogers in Canada.
Source: David Schuster - https://plus.google.com/+DavidSchuster/posts/bEVD4De32Uo
UPDATE [06-09-2015]
"I wanted to give a quick update on where we are with the Lollipop upgrades for the 2013 Moto X (1st Gen) devices.
We have started full soak testing in France and Germany retail this week with the expectation of full deployment next week if all goes well.
In addition, we have addressed an issue we found in a previous soak test and should start full soak testing in the US and Brazil for retail later this week. If all goes well, full deployment can happen the following week.
There were some questions about support for Lollipop upgrades from our carrier channels. We are in a number of the carrier labs now so we don't anticipate issues in getting the upgrades deployed. As you guys know.... the carrier channels typically take longer.
UPDATE: If all goes well with the soak testing this week we expect to start deployment for 2013 Moto X (1st gen) in India next week."
Source: David Schuster - https://plus.google.com/+DavidSchuster/posts/ETpoNrkmmrA
UPDATE [04-22-2015]
Due to the "leaks" about 5.1 "updates rolling out" in Brazil, here's some trusted words in regard to 5.1 current state:
"We're still in testing. We'll post something in the parked comments when it moves to the Soak stage and then again when full deployment happens. Don't always believe what you read online."
Source: Motorola Forums Manager (Mark).
Awsome
Kustaa said:
So, it's kind of official now, we'll have to wait a little longer, but 5.1 will be definitely here for our 2013 X
source: David Schuster - https://plus.google.com/+DavidSchuster/posts/cV4vDyyMmw2
Click to expand...
Click to collapse
good stuff. im no longer annoyed at the update taking so long again
This is great news, it can surely only be a matter of weeks now before it is officially released
I'm still on 4.4.4... Should I take the official or just wait for a rooted version?
Also assuming there is still issues with xposed?
mroneeyedboh said:
I'm still on 4.4.4... Should I take the official or just wait for a rooted version?
Also assuming there is still issues with xposed?
Click to expand...
Click to collapse
You can't take nothing yet lol
Good news, I can survive with 4.4.4 till 5.1.
5.0.2 still have issues.
Cool stuff!
I kinda feel bad for the people who won't be able to return to stock 4.4.4 now. :s
Sweet. Can't wait to rock this in 2017!
I'm just getting an error when I click the link?
Sent from my XT1060 using Tapatalk
wiidbzxt said:
Cool stuff!
I kinda feel bad for the people who won't be able to return to stock 4.4.4 now. :s
Click to expand...
Click to collapse
Do you mean those who installed 5.0.2 test drive?
I don't think Motorola would leave the official MFN testers on an incomplete test drive version, furthermore it makes sense to use the same testers to test 5.1, so as soon as those users get 5.1 it will leak and those who sideloaded 5.0.2 will have the upgrade.
Otherwise, it would be as easy as return to 4.4.4 temporary (skipping gpt and motoboot) and sideload the 5.1 upgrade, not big deal.
No matter what, the situation is not to feel bad about them, maybe they'll even get the upgrade before you do.
I have an brazilian XT 1058 and take the soak. I will be able to update to 5.1?
Logically yes.
Sent from my XT1052 using XDA Free mobile app
I'm glad for this. 5.1 didn't address the memory leak did it?
crazyxzer0 said:
I'm glad for this. 5.1 didn't address the memory leak did it?
Click to expand...
Click to collapse
I'm pretty sure it did, at least for the nexus 6
I think the memory leak was also addressed via xposed module so less of an issue for xposed users
Sent from my XT1053 using Tapatalk 2
wiidbzxt said:
Cool stuff!
I kinda feel bad for the people who won't be able to return to stock 4.4.4 now. :s
Click to expand...
Click to collapse
I can confirm, that downgrading of bootloader from 30.BC back to 30.B7 IS possible. I bricked one my phone for test: 4.4.4->5.0.2 (via OTA)->4.4.2->bricked by OTA via WiFi. Now it's running again Thanks to Tenigima
good news i hope soak 5.1 for all regions not only for brazil as with 5.0.2
Ii there a specific date ??
Moto-x said:
good news i hope soak 5.1 for all regions not only for brazil as with 5.0.2 [emoji14]
Ii there a specific date ??
Click to expand...
Click to collapse
In android world there's never a specific date unfortunately.
Enviado desde mi XT1060 mediante Tapatalk
sylarm said:
Good news, I can survive with 4.4.4 till 5.1.
5.0.2 still have issues.
Click to expand...
Click to collapse
Have you even used it?
I'm not saying Moto did or did not fix anything, but so many people keep saying "Ohhh its version XXXX which has XXXX bug!"
1.) We don't run AOSP
2.) When google updates android, all of those changes are published. 5.1 is NOT a full re-write, sections of code are fixed. These fixes are published and if moto REALLY felt like it they could apply all the same code changes to a 5.0.1 base... At that point what is "version number" is is kinda semantics....
Moto started work on 5.0.2, so that is what their build is called, there is no reason they cannot include the already published bug fixes from later versions of android so they they can release their tested a developed build rather then throwing everything away and starting with a new base every time google updates.
On twitter autoprime tweeted a few days ago
The incoming LG G4 unlock from LGVIET will be for "v0" qfuse only. Hope you USA users didn't take an ota. Congrats to LGVIET and company.
Click to expand...
Click to collapse
And later on this discussion:
[...]will work on all locked v0 G4's.. tho Verizon needs a bit of extra fiddling.
Click to expand...
Click to collapse
Source: https://twitter.com/utoprime/status/649654317939601408
Maybe we will see unofficial unlock on all carrier devices soon
But what means "v0"? Where can I see whether my phone is "v0"?
Edit: Link to LGVIET Forum thread:
http://lgviet.com/forum/threads/twp...t-lg-f500l-lg-f500k-lg-f500s-by-lgviet.48299/
great news... but yah what's v0???
Sent from my LG-H815 using Tapatalk
So we will see the twrp bump for all the g4 versions? WAAAOW
V0 has to do with the anti rollback flag that newer firmwares install. A newer firmware will change v0 to v1 or v2 etc. Flashing older firmware will make the phone very unhappy. It's why, on several US based phones, trying to downgrade will brick the phone COMPLETELY. Search for my PSA thread.
As far as I know this does not affect H815 international or am I wrong?
Sent from my LG-H815 using Tapatalk
Thats mean we dont lose the warranty if we unlcock unoficially ?
Enviado desde mi LG-H815 mediante Tapatalk
V0 is the shipped firmware that your device came with, at least it is with Verizon. I think the firmware version (for Verizon) is 10b. I've stayed on it this whole time so I'm hoping it pays off.
The guy that originally posted about the bootloader unlock has been really quiet though. I hope he plans to release.
Looks like I have a bit to wait. I checked it in your PSA thread before not knowing what it meant but now I do. I'm on v2. :/
For the most part I'm probably better off waiting for that official bootloader unlock if it should ever come.
Trying not to think of D3. v1.1 here, rooted, bloat gone, Google sms & keyboard, ota nutered, Tether & Mobil hotspot mod. G2 was so fast it tripped over itself. G4 with 8 cores? we are moving forward. Fingers crossed on bootloader unlock.
Is it worth unlocking now that marshmallow is not that far from coming up in our devices?
How to check bootloader
How do i check my boatloader version
Will 11a work or should I just go ahead and sell this crap before my disappointment arrives?
You can checked by looking at this thread
S1L3nTShaDoWz said:
Will 11a work or should I just go ahead and sell this crap before my disappointment arrives?
Click to expand...
Click to collapse
if you have a USA G4 and ever took an OTA update (forced or manual) then you are not on v0.
11a was an OTA update.
For those asking what version they're on... see this post http://forum.xda-developers.com/showpost.php?p=62842317&postcount=16
notice the antirollback option at the very bottom. don't have that option? then you can't check with that menu.
If you ever flashed a KDZ to a USA G4.. then you are no you are not at v0. All USA KDZ's are at least v1.
95% of all the USA G4 users are at v1 or higher. Unless you went out of your way to block OTA updates on the device within the first few weeks of releases.. it's probably already taken an update or two.
If you have a non-USA G4 then you are on v0.
mu3g said:
Hi Autoprime,
Attached is my screenshot of AT&T LG G4 H810 running 10g and rooted. It says the Sub S/W version is 0....does that indicate the anti-rollback feature is NOT enabled, i.e., I might be on v0 and therefore unlock my bootloader?
Click to expand...
Click to collapse
you're v1
g_ding84 said:
I bought Verizon G4 last week and it came with 11a.
So I guess it was forced before I bought it. If I'm reading correctly, I would not be able to unlock the boot loader. Correct?
Click to expand...
Click to collapse
correct, at least a bootloader unlock method made for v0 devices. v1+ isn't impossible... but less likely someone will post an exploit for those devices any time soon.
NighthawkXL said:
This doesn't apply to the H811 correct? I thought our bootloader was unlocked from the start.
Click to expand...
Click to collapse
correct
dsilx said:
What if we were att bricked an was forced pr firmware
Because im new to this all an also is h810Pr10A v 1 or nah thanks in advance
Click to expand...
Click to collapse
v1
autoprime said:
if you have a USA G4 and ever took an OTA update (forced or manual) then you are not on v0.
11a was an OTA update.
Click to expand...
Click to collapse
That sucks, oh well. Congrats to everyone else then .
autoprime said:
if you have a USA G4 and ever took an OTA update (forced or manual) then you are not on v0.
11a was an OTA update.
Click to expand...
Click to collapse
Hi Autoprime,
Attached is my screenshot of AT&T LG G4 H810 running 10g and rooted. It says the Sub S/W version is 0....does that indicate the anti-rollback feature is NOT enabled, i.e., I might be on v0 and therefore unlock my bootloader?
EDIT: Attached the bottom half of the page as well..2 screenshots. Thanks for your help!
Confused
Does this mean im on v1
autoprime said:
if you have a USA G4 and ever took an OTA update (forced or manual) then you are not on v0.
11a was an OTA update.
Click to expand...
Click to collapse
I bought Verizon G4 last week and it came with 11a.
So I guess it was forced before I bought it. If I'm reading correctly, I would not be able to unlock the boot loader. Correct?
This doesn't apply to the H811 correct? I thought our bootloader was unlocked from the start.
Pr firmware
autoprime said:
if you have a USA G4 and ever took an OTA update (forced or manual) then you are not on v0.
11a was an OTA update.
Click to expand...
Click to collapse
What if we were att bricked an was forced pr firmware
Because im new to this all an also is h810Pr10A v 1 or nah thanks in advance
*EDIT*
Disregard PSA, SunShine works on SU4TL-44 and SU4TL-49 now.
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
hm,i only choose to update the offical mm...but thx to warning us
gangrenius said:
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a soak test.
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
@ChazzMatt is speaking of the Marshmallow soak test. @smooth781 is speaking of the Droid Turbo OTA that is still 5.1 (23.21.49.en.US). Both were mentioned in op.
jcase said:
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
gangrenius said:
Where is this or what is this beta u speak of?
Click to expand...
Click to collapse
ChazzMatt said:
It's a soak test.
Click to expand...
Click to collapse
smooth781 said:
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
Click to expand...
Click to collapse
Please actually read the thread before replying. The op clearly mentioned the 6.0 beta and someone asked about it. I answered.
6.0 beta = the Marshmallow soak test.
The Marshmallow soak test is by invitation only and is not an OTA update. Emails went out several days ago.
One of the Quarks (XT1225) already has Marshmallow, and now the Verizon Droid Turbo is being tested for Marshmallow. Chop Chop action is removed in official Marshmallow ROM, or at least it was by the final soak test of the Brazil XT1225 Soak Test #3. It was still there in Soak Test #1.
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
ChazzMatt said:
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
Click to expand...
Click to collapse
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
TheSt33v said:
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
Click to expand...
Click to collapse
Motorola removed it from the Quark Marshmallow ROM, final soak test #3.
CM dev then removed it -- at least for now. Resurrection Remix is CM based.
Skrilax_CZ said:
The reason is proprietaries have been updated to soak #3 as well. It'll keep it disabled until I learn more about why it was disabled.
Click to expand...
Click to collapse
It may be added back in the future.
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
KOAO said:
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
Click to expand...
Click to collapse
I assume if your bootloader is unlocked and you are rooted that you have TWRP custom recovery. Pretty sure OTA would fail. But that's not a bad thing. You don't want to be the one to find out the OTA locks your bootloader permanently. (Probably wouldn't, since you are already unlocked, and having custom recovery will prevent the OTA from installing -- but still you don't want to be the one to find out this time Verizon did something very sneaky.)
If your bootloader is unlocked, you would manually flash the eventual official Marshmallow XT1254 update manually -- not taking it as an "OTA". There will be download links available here on XDA. And you would wait until others have done it first.
Or you would flash a custom Marshmallow ROM, again manually -- either one by @computerfreek274 which would be stock-based (not available yet) or a CM13-based ROM (CM13 or Resurrection Remix) or an AOSP-based ROM (Mokee).
We already have three custom Marshmallow ROMs for ALL Quarks -- CM13, Resurrection Remix, Mokee and Motorola recently finalized stock ROM for the other Quark, the XT1225.
As soon as Motorola/Verizon get their act together for the XT1254/XT1250, you will have a stock Marshmallow ROM available to flash for the XT1254 and @computerfreek274 will also release a "stock-based" ROM for people to flash -- if you want to stay with pure stock or stock-based.
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
drizzzzzz said:
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
Click to expand...
Click to collapse
Yeah, the OTA update was basically worthless -- just an excuse to prevent Sunshine from working to unlock the bootloader.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
jorgkrkmo said:
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
Click to expand...
Click to collapse
Don't lock it. Leave it unlocked, even if you send it in.
is there a chance sunshine will be updated to unlock the new version as well?
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
Theres a "chance" but a very slim one. The sunshine devs are not going to pour time and effort into it, but if they do find an exploit they will update it
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
The exploit they used has been closed.
Wynnded said:
The exploit they used has been closed.
Click to expand...
Click to collapse
can the phone be reverted to an unlock able version?
rhcreed said:
can the phone be reverted to an unlock able version?
Click to expand...
Click to collapse
No. Stock firmware with locked bootloader is not downgradeable.
People were told from the very beginning NOT to take the update unless your bootloader was unlocked first. Not just in this thread but several others.
Anyone who took the SU4TL-49 update with a locked bootloader does not care about unlocking their bootloader.
1) the Sunshine exploit has been available since November 2015. People have had six months to unlock their bootloaders! Why is it suddenly important now?
2) the Android SU4TL-49 update only showed up less than two weeks ago (early May 2016). It's the first firmware update since the exploit was released.
3) People were warned Android SU4TL-49 would close the Sunshine exploit. But even common sense would tell people that -- knowing control freak Verizon and their locked down bootloaders.