Related
So we have confirmation that superoneclick and aroot doesn't work on the new atrix update. If any dev will work on this please use this thread.
EDIT: Please don't comment on this thread anymore. Go to Ririal's v2 root method
I just updated and it does seem smoother to me. Might just stick with it.
please everyone, this thread is for getting root on the update. if you want to comment on the update itself, use my thread on the general forum
Not cool... so they locked the damn phone down even more.
rjohnstone said:
Not cool... so they locked the damn phone down even more.
Click to expand...
Click to collapse
Maybe this is your first piece of electronics, but it's completely expected that everytime a software update for a piece of hardware is released, exploits are closed. Apple does it, Sony does it, Microsoft does, HTC does it, Motorola does it, Nokia does it...The list goes on.
This WAS EXPECTED. I always found it entertaining how whenever an update was released for my EVO the forum here on XDA would get absolutely flooded with people saying how they lost root NO MATTER HOW MANY TIMES THEY WERE WARNED! It could take 5 minutes, 5 hours, 5 days, 5 weeks, 5 years, or eternity for root to be regained after an update. There's no way to know.
any way of installing 3rd party non-market apps, like amazon appstore?
phobos512 said:
Maybe this is your first piece of electronics, but it's completely expected that everytime a software update for a piece of hardware is released, exploits are closed. Apple does it, Sony does it, Microsoft does, HTC does it, Motorola does it, Nokia does it...The list goes on.
This WAS EXPECTED. I always found it entertaining how whenever an update was released for my EVO the forum here on XDA would get absolutely flooded with people saying how they lost root NO MATTER HOW MANY TIMES THEY WERE WARNED! It could take 5 minutes, 5 hours, 5 days, 5 weeks, 5 years, or eternity for root to be regained after an update. There's no way to know.
Click to expand...
Click to collapse
No... this is not my first rodeo, but still uncool regardless.
I expected it too, but still a bit peeved they did it.
im sure it is the "5 min" to regain root (hopefully!!!)
franciscojavierleon said:
So we have confirmation that superoneclick and aroot doesn't work on the new atrix update. If any dev will work on this please use this thread.
Click to expand...
Click to collapse
The update JUST came out. Not everyone who was accepted has even received the update yet. Be patient please.
Ririal said:
The update JUST came out. Not everyone who was accepted has even received the update yet. Be patient please.
Click to expand...
Click to collapse
Pretty sure that's why he made the thread - we're being patient, just looking for someone to work on this fix. I'm ashamed I even posted on this comment, but if you're not going going to help fix it, you shouldn't be either....
Hey everyone, if you want to sideload apps just use the ADB INSTALL method it works for me.
I still have my root after update
Hello,
I just ran the update, it shows in the system version as 4.1.57 yet I still have my superuser permissions and can tether without adding to my plan. Not sure how or why, but it happened.
GarciaM25 said:
Pretty sure that's why he made the thread - we're being patient, just looking for someone to work on this fix. I'm ashamed I even posted on this comment, but if you're not going going to help fix it, you shouldn't be either....
Click to expand...
Click to collapse
I would be helping fix it if I had the update. I'm still waiting for the notification, but thanks The OP is just forum clutter, and it's pretty rude to be making these requests minutes after the update is even pushed, and a BETA update, at that. That was my point.
Where are you guys located, getting the update already. I just checked and it said mine is up to date and I still have 4.1.26. Wierd!
Does any one know how to get the message to stop showing up I don't want to loose root and I don't want to be reminded every hour
Sent from my Motorola Atrix using Tapatalk
milesjohnson said:
Does any one know how to get the message to stop showing up I don't want to loose root and I don't want to be reminded every hour
Sent from my Motorola Atrix using Tapatalk
Click to expand...
Click to collapse
My update failed and I just didnt click on syste update again. Try a reboot
cheleken said:
Hello,
I just ran the update, it shows in the system version as 4.1.57 yet I still have my superuser permissions and can tether without adding to my plan. Not sure how or why, but it happened.
Click to expand...
Click to collapse
Did you flash back to stock before the update or did you do the update on a rooted/gingerblured phone? Do you know if you were using 1.2.6 or 1.5.2? Have you tried running su in a terminal to make sure root actually works?
Was worried bout flashing without stock software already installed think ill go back to stock anyway to try it the official way first.. Can always go back and upgrade after rooted though if this works consistently.
The security hole that allowed for root on the phone is CLOSED in this update. There is no way of rooting your phone after this, save going back to one of the available SBFs. Confirmed by designgears as well.
As someone said earlier, "for now" the root method is disabled, and there is no way of rooting your phone after the update "at this moment".
I have confidence everything will be OK.
Boy am I glad I decided to stay away from this "update." I got accepted but when I go to check for updates it says I need a social networking account setup. When I then hit setup nothing happens so I said forget it lol.
I just got off the phone with VZW. Apparently, they've stopped rolling out the OTA because of "software issues," though he didn't specify beyond that. So, for all of you who have been waiting for the OTA over the past few days, off the top of his head, the tech guesstimated it'll be around a month before they begin rolling it out again. Lame.
Edit: You can still install the .217 leak...but if the update has been pulled for software issues, that obviously means .217 is no longer the official OTA.
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
alex94kumar said:
What? thats BS! even though im on Eclipse ICS 1.2, its still BS for anyone still on GB!
Click to expand...
Click to collapse
Yeah, I've been mashing the "systems update" option habitually now for a couple days, but also avoided just manually updating to the .217 leak for this very reason. Either way, it is kind of disappointing.
honestly, if I were you, I would jump on either the 217 leak, or if you want a custom rom that's slightly themed and has extra features/no bloat, go with Eclipse
It wasn't supposed to be released for the general OTA, they did that on accident, only people who were signed up for the motorola feedback network test were supposed to get it, but for some reason they pushed it to all devices. It should be officially pushed in a week or so, because it appears the soak test isn't showing up any major issues.
Sent from my DROID4 using xda premium
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Rafterman414 said:
EDIT: Did NOT work
I called VZW tech support earlier today because it was not working and they did not mention anything about it being halted, but it probably depends on which tech you speak with.
I am not sure if this works or not but the guy I spoke with did tell me that performing a factory reset can sometimes trigger the upgrade. I don't have anything on there that I can't live without or easily re-install so I am going to go ahead and give it a shot.
EDIT: Just tried above. Did NOT work
Click to expand...
Click to collapse
As mentioned above, there was no planned general release yet. Moto did a release for "a few thousand" phones, of which only a small portion are official MFN soak testers. The test will end soon, and it looks like no show-stopper issues have been found, so, if things go as usual, the general release will roll out, probably in groups, over the next several days.
Sounds like the OP spoke to someone in VZ who really didn't know why the release wasn't available and made something up. (And I bet you never thought a VzW rep would do that!)
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
highlandsun said:
Keep in mind, even if they had decided to halt it due to a showstopper bug, they've already released it to several thousand owners. Which means they're obligated to provide anyone on .217 with a way to get back onto the upgrade path, if they decide to release a newer update down the road.
All in all - if you're impatient, just install the current .217 files - you'll still be able to upgrade again later if you need to.
Btw: I'm on it now, and I ABSOLUTELY HATE the Dialer and Contacts being split apart into totally separate apps. I always hit the Dialer icon first, and then if I can't remember a person's phone number, I now have to back out of it and look up the contact first. Whereas on GB I just had to select the Contacts tab and go on. So from a human interface perspective, this new design sucks.
Click to expand...
Click to collapse
When your in at the dialer screen just push menu then search it goes to your contact list. So its a matter of hitting 2 buttons but you can get to it from dialer. I also miss the other way but im getting used to this and it doesnt bother me anymore
Sent from my DROID4 using xda premium
It's happened to me twice now in the last two days that I was unable to hear the people calling me. Switching to speaker mode or rebooting the phone fixed this. Actually only rebooting. Alternating between speaker and normal mode is just a temporary fix as long as I'm in speaker mode. Plug in the headset and it works. Take it out en again no sound... I think it happens after I use BT.
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Lum_UK said:
Maybe people who are on this update officially could raise a bit of fuss about this and ask to be put back onto Gingerbread?
As we all know this currently can't be done due to the highly restrictive bootloader, perhaps we could wangle a better bootloader out of this?
Click to expand...
Click to collapse
Well, we can certainly dream, but given a choice between unlocking the bootloader and shrugging apologetically and insisting nothing can be done, I'm dead sure Verizon will require Motorola to do the latter. :crying:
Installing OTA right now on my wife's D4
Sent from my DROID BIONIC using xda premium
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Rafterman414 said:
Seems like more people are getting it now. I just got too antsy and went ahead and installed the .217 leak floating around, I bet if I had waited another day I could have gotten the OTA. Hopefully I did not ruin my ability to get future OTA updates.
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
tcrews said:
You didn't. .217 is .217 no matter how you got it. Anyone on the "leaked" .217 is on the official update path as that is what was pushed as OTA.
Click to expand...
Click to collapse
If you had a nickel for every time you had to tell somebody that you could probably retire! LOL
Droid 4 - AOKP K1L0
Update fails anyway
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this? I pressed the volume up button and it says:
Verifying current system...
assert failed: apply_patch_check("/system/app/music2.apk", "cbb199983ab1cb9beee6b20ec4db659ccd49d757", "25d8789a15715fdd931ef2a2ee93b637bfef06b0")
E:Error in /cache/Blur_Version 6.13.219.XT894.Verizon.en.US.zip
(Status 7)
Installation aborted.
Saloobian said:
I received the update this morning, and after attempting to install, it fails within 30 seconds and reboots. I factory reset, erasing everything, downloaded the update again, and same result. Anybody have any information on this?
Click to expand...
Click to collapse
Just install from a PC via FastBoot.
ROM: http://sbf.droid-developers.org/cdma_maserati/list.php
Instructions: http://www.droidforums.net/forum/dr...otorola-droid-4-xt894-stock-windows-only.html
Note. Do not download one of the two ROMs that post suggests, use the 217 ROM from my link above. Do not attempt to downgrade via this method either, it will not work. You might also want to skip steps 6-9 if you don't want to reset your data. Not sure how well this will work after an upgrade.
The soak test is over and "the software is officially released and will be rolling out in stages"....
Sent from my DROID4
:good:
Fantastic! I restored to stock and downloaded the update again, and it's currently installing without a hitch! Thanks!
I did not get the 7.2.1 update. I moved a file called otacerts.zip to a different file, I saw this in another thread and will have to look for it to give proper credit. I also have super User blocking ota's but that is no guarantee.
I have not been forced to update automatically as well, I have only installed Voodoo OTA RootKeeper. Would rather not update.
I saw in another thread ota root keeper did not work. Some one used it and still got the update.
i switched off all automatic/silent updates and deleted otacerts.zip earlier.
Should i expect my KFHD to be updated in any ways and one day Amazon will bring me an easter egg, surprise? or this is just enough and we see the problems at those guys who forgot to turn off the auto update mode. Please let me know.
so far so good
andrewstamina said:
i switched off all automatic/silent updates and deleted otacerts.zip earlier.
Should i expect my KFHD to be updated in any ways and one day Amazon will bring me an easter egg, surprise? or this is just enough and we see the problems at those guys who forgot to turn off the auto update mode. Please let me know.
so far so good
Click to expand...
Click to collapse
No one really knows, what needs to be removed to stop force updates, because I have done nothing but voodoo, and I have not received it. So its all question marks for me at the moment.
Still on 7.1.5 after removing otacerts.zip before...
vadimus123 said:
Still on 7.1.5 after removing otacerts.zip before...
Click to expand...
Click to collapse
Same. However, no evidence that an OTA attempt happened yet. Might be they are pushing in waves.
Scarey! I'm just a noob, (but I don't want to be, lol) and I have worked so hard to get this thing the way I like it. Sometimes hours and hours. If I have to do it over I think I will scream, and maybe take a hammer to it???
Let me explain: So I got the OTA overnight, and when I woke up (to my alarm clock) I accidentally accepted the update. I had planned to root my phone and looked into keeping root through the OTA. I postponed it for the last two days, trying to figure out how to root/keep root through OTA. I've been busy with work and had to put it aside until I had a day off. To get to my question, am I screwed or will there be a way to root this phone after the update? This is my first Motorola phone, so pardon me if this is a dumb question. Thanks for any and all comments.
Sent from my XT1060 using xda app -developers app
pborner said:
Let me explain: So I got the OTA overnight, and when I woke up (to my alarm clock) I accidentally accepted the update. I had planned to root my phone and looked into keeping root through the OTA. I postponed it for the last two days, trying to figure out how to root/keep root through OTA. I've been busy with work and had to put it aside until I had a day off. To get to my question, am I screwed or will there be a way to root this phone after the update? This is my first Motorola phone, so pardon me if this is a dumb question. Thanks for any and all comments.
Sent from my XT1060 using xda app -developers app
Click to expand...
Click to collapse
screwed for the time being. jcase already verified there's other ways to root the update but won't release them yet. in due time I'm sure someone will release something. I'm patiently waiting too.. bought a used moto x with the update already applied. sucks.
If its still within the return time, shoot compressed air in the ear piece and speakers. It'll screw it up, take it in and get a replacement. Then don't screw up the next time around.
gokart2 said:
If its still within the return time, shoot compressed air in the ear piece and speakers. It'll screw it up, take it in and get a replacement. Then don't screw up the next time around.
Click to expand...
Click to collapse
Um... As much as I'm in favor of screwing Verizon (and all other multi-national corporations), why not just search the threads for how to use RSDLite to reflash the original stock firmware, then don't accept the OTA until you've waded through the process for keeping root? Or, you can destroy a perfectly good piece of technology for no reason.
hazenberger said:
Um... As much as I'm in favor of screwing Verizon (and all other multi-national corporations), why not just search the threads for how to use RSDLite to reflash the original stock firmware, then don't accept the OTA until you've waded through the process for keeping root? Or, you can destroy a perfectly good piece of technology for no reason.
Click to expand...
Click to collapse
You cannot downgrade firmware.
mandrsn1 said:
You cannot downgrade firmware.
Click to expand...
Click to collapse
I'm pretty sure you can:
http://forum.xda-developers.com/showthread.php?t=2446515
hazenberger said:
I'm pretty sure you can:
http://forum.xda-developers.com/showthread.php?t=2446515
Click to expand...
Click to collapse
Nope. When you bootloader updates as part of the camera update, it prevents firmware downgrades. That link is just for restoring to stock if you haven't updated.
mandrsn1 said:
Nope. When you bootloader updates as part of the camera update, it prevents firmware downgrades. That link is just for restoring to stock if you haven't updated.
Click to expand...
Click to collapse
Sorry. You're right.
So go ahead and screw Verizon using the air trick. Or wait until someone finds a new root exploit for this firmware.
hazenberger said:
Sorry. You're right.
So go ahead and screw Verizon using the air trick. Or wait until someone finds a new root exploit for this firmware.
Click to expand...
Click to collapse
There are other known, but unreleased, root exploits. They aren't going to be released until another major firmware upgrade (e.g., 4.4).
Thanks for the heads up guys. Not really in favor of the air method. There's nothing wrong with this phone unrooted, actually the first phone I can say that about. Just wanna tweak some things, preferably a CM MOD. Will wait for a new method.
Sent from my XT1060 using xda app-developers app
pborner said:
Thanks for the heads up guys. Not really in favor of the air method. There's nothing wrong with this phone unrooted, actually the first phone I can say that about. Just wanna tweak some things, preferably a CM MOD. Will wait for a new method.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
if you are on verizon and you go to a verizon store, they are typically pretty nice there. Basically, you could walk in say that you accidentally took the OTA and you wanted to root so can give you me a new one. They will probably say yes. Or you can just say your battery drain is really bad and you have spent hours trying to fix it but people on forums said you needed to return it. The guy at my store doesn't even ask or look at my phone anymore if i bring it in...
mandrsn1 said:
There are other known, but unreleased, root exploits. They aren't going to be released until another major firmware upgrade (e.g., 4.4).
Click to expand...
Click to collapse
This is good to hear... Do you happen to know if there's been any solid progress made on a bootloader unlock for Verizon? I wish I knew the first thing about Android programming so I could help out in this effort. I love my Moto X as is, but would love to see permanent root methods so we could have access to custom kernels (and so I can try to get rid of the damn NLP wakelocks).
Lucky me, just got my Note 4 yesterday and checked for software updates just now and low and behold I'm receiving Lollipop, its a 1161.38mb download..
you sure it's lollipop? i know my note 4 received two updates in the past month.
Getting an update on SM-N10A(stock. not rooted) on ATT network. . Its a 1161.38 MB file. Will update on which version does it get updated to shortly.
Update 1: 2.20PM CT: LOL. Installation failed. Try again in 21 hours. Sigh!
SeraldoBabalu said:
you sure it's lollipop? i know my note 4 received two updates in the past month.
Click to expand...
Click to collapse
AT&T started rolling out 5.0.1 this morning to Note 4.
Stupid me
I checked for an update last night and now have to wait 9hrs before being able to check again. Oh well. At work anyways.
sherpa said:
AT&T started rolling out 5.0.1 this morning to Note 4.
Click to expand...
Click to collapse
nice. hopefully not much longer for the canadian releases.
SeraldoBabalu said:
nice. hopefully not much longer for the canadian releases.
Click to expand...
Click to collapse
Just sent a tweet to Rogers telling them AT&T rolled it out now and asking how long it will take for us to get it. I'm not holding out much hope for a reply.
spexwood said:
Stupid me
I checked for an update last night and now have to wait 9hrs before being able to check again. Oh well. At work anyways.
Click to expand...
Click to collapse
You can manually change your date/time to sometime tomorrow and get the update today.
TheIgster said:
Just sent a tweet to Rogers telling them AT&T rolled it out now and asking how long it will take for us to get it. I'm not holding out much hope for a reply.
Click to expand...
Click to collapse
They will just point you here.
HTML:
http://communityforums.rogers.com/html/assets/OSUpgrade.html
And tell you it's TBD. My old co-worker who now works at Rogers looked into it and apparently Samsung isn't releasing that information. As he said it's policy it classify devices that don't get support as TBD as to not piss off customers. Aka it's a coin toss if they are going to release it.
AT&T isn't the same as our devices. The closest we can get is T-Mobile. If and when TMO gets the update we won't be far behind. At least we shouldn't.
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
TheIgster said:
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
What are these phone updates of which you speak? Yes, I'm on Verizon.
cyprian64 said:
What are these phone updates of which you speak? Yes, I'm on Verizon.
Click to expand...
Click to collapse
lol...yeah, I guess it's not just those of us in Canada. Really missing my Nexus 5 right now with updates right away straight from Google.
TheIgster said:
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
I was referring to the 5.0.1 update. It's very possible they will just lazily skip it and go for 5.1
If thats the case we most likely won't see a LP update this year. Remember Samsung had the oportunity to start LP in June and it has taken them 9 months just to get to this point. Considering no Canadian Carriers have been informed of the update even arriving, meaning they have not tested them and that in turn could create another month or two of testing. It's also been disclosed that Samsung has no plans on working on 5.1 at the moment. Let's assume that they wait to give us 5.1 instead of pushing 5.0.1 out. Since they have not even started 5.1 we can assume they might start in two months (Highly doubt it would be that quick). Then if we take the first time frame we add another 9 months plus the fact they wait a month after they build (check the build logs) we are at a total time frame of 12 months out for a single update. Skipping 5.0.1 would mean a total of 21 months of development time before the first actual LP update.
Of course remember this is all assumptions and theory based on what we have seen so far and I could be totally off. At least I hope I am.
airwa1kin7 said:
Of course remember this is all assumptions and theory based on what we have seen so far and I could be totally off. At least I hope I am.
Click to expand...
Click to collapse
Sure hope you're wrong. LOL. I would be pretty pissed off if they don't send out a Lollipop update this year.
SeraldoBabalu said:
you sure it's lollipop? i know my note 4 received two updates in the past month.
Click to expand...
Click to collapse
Yep, it sure was
Showing as Android version 5.0.1
TheIgster said:
Yeah, I know of that link and they have pointed me there before. I've had a dialog going with them actually. I would like to rattle their cages "in public" as much as possible and Twitter is a good way to do that. I really was surprised to just get the Note 4 about 2 weeks ago, thinking it was the current flagship phone and then find out they have no idea when they are going to release Lollipop on it. Just bizarre.
A coin toss? How can a phone that hasn't been out for even 5 months yet not get Lollipop?
Click to expand...
Click to collapse
You'd think that right
How can one of the newest flagships not be on a higher priority?
Sent from my SM-N910W8 using Tapatalk
Are more bloatwares included in this update?
sherpa said:
You can manually change your date/time to sometime tomorrow and get the update today.
Click to expand...
Click to collapse
Oh I know. It's OK though. I was at work with no wifi anyways (and I dont work a desk job either). I have the update downloading now though.
LTE-X said:
Are more bloatwares included in this update?
Click to expand...
Click to collapse
Just the usual AT&T crap... Google Service needs to be updated after Lollipop installs, GS took multiple attempts to finally install, otherwise you keep getting a notice that the update is required.. Not sure if was just me but I had to reboot a few times to finally get the Install option to pop up..
So far I'm liking Lollipop, Visually much more appealing..
Captpt said:
Just the usual AT&T crap... Google Service needs to be updated after Lollipop installs, GS took multiple attempts to finally install, otherwise you keep getting a notice that the update is required.. Not sure if was just me but I had to reboot a few times to finally get the Install option to pop up..
So far I'm liking Lollipop, Visually much more appealing..
Click to expand...
Click to collapse
Just updated to lollipop and I am experiencing memory leak. I performed a factory reset and is doing much better now.