AT&T GS5 Active Crazy unroot?
To start off, I've had my phone rooted since probably around February 2015 or some eary month of 2015. Anyways, I'm on 4.4.4 and haven't upgraded or downgraded but for my whole time of root I've been on 4.4.4. My phone with root was working fine until about 2 days ago. There was a random software update that said was complete maybe 4 days ago when I picked up my phone to check the time but I did not authorize it. It still says im on the same 4.4.4 but now SU opens to a black screen and none of my apps can obtain root access. I assume this issue was caused by the unauthorized software update because all my root apps were working fine until this "update". Anyone else have this problem? What can I do to fix it?
Same here
The same thing happened to me, but it happened with the 4.4.2 update. I really need to get this fixed, so any help would be appreciated.
Pretty sure you all are hosed.
With the stagefright issue and the manufacturers allegedly stating they will be patching systems more often, I'm pretty sure that the days of "authorizing" software "patches" are gone.
I would not doubt that a stagefright fix was pushed plus some.
dicksteele said:
Pretty sure you all are hosed.
With the stagefright issue and the manufacturers allegedly stating they will be patching systems more often, I'm pretty sure that the days of "authorizing" software "patches" are gone.
I would not doubt that a stagefright fix was pushed plus some.
Click to expand...
Click to collapse
So do you think we would be able to reflash our to the stock rom and we'd be fine?
VauIt said:
So do you think we would be able to reflash our to the stock rom and we'd be fine?
Click to expand...
Click to collapse
As long as the bootloader is not included in the ODIN package it should work. Once it tries to write the sboot.bin file it will barf.
Related
Has anyone else received this update?
Not here.
Los Angeles, CA
lol figures once i get root an update starts rolling out, it probably enables wifi n like they released for the EVO today.
1.22.605.2 is the software version i have (rooted)
It adds 3G Mobile hotspot and fixes the signal issue, im in a pickle now though lol. cant remove superuser
Not exactly a pickle - just don't do the upgrade, wait for someone else to take the OTA download and make it root-safe.
where did you confirm this info as to what the update offers?
I guess i am confused, what would happen if we did the update with our rooted phones?
Nothing. Because with rooted phones you won't see the OTA Update...but if you were to manually upgrade without it being root proofed....you'd loose root.
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
Incredible OTA Update 1.65.605.2
I'm confused to, so if you are rooted, you won't see this update? or you will see it and if you do it, you lose root? I have the stock rom, which is what I thought disabled your OTA's is this an incorrect thinking?
giantcrazy said:
Wait - weren't we already at 1.22.605.2? That's what rev I'm running, and I haven't taken an OTA since the first few days after launch.
Click to expand...
Click to collapse
The name of this post is Incredible OTA Update 1.65.605.2 so even though we are at 1.22.605.2 that is not 1.65.605.2
Thats the thing, i was rooted and did get the OTA update notifications, hit accept for the update by mistake. And the only reason why i confirmed that info is because i have it on my inc.
P.S sorry lol made a type in the title of the post, its 1.35.605.2
So if you updated as root, did you lose your Root? It is not guaranteed that you would loose it, just likely is all. I feel like they released it to break our Root, and nothing more... but maybe they fixed a few issues too... we have the same screen grounding issue the EVO had, and the recent update fixed theirs... but who knows...
EDIT: Posted an article to an outdated update. Oops...
so i assume you lost root?
Yes i did.
I haven't seen it yet. <-- OHIO
have you tried redoing root? did you loose recovery?
I havent tried redoing the root process again, but how is that going to work? isn't the root process based off of the original software? the baseband is different as well.
Haven't seen it yet either <-- Rhode Island
Didn't find any information on it either. Was their a "more info" link included with yours? as with other OTA updates. Changelog, etc.?
Better question would be, do you have a screen shot of your About Phone page (baseband, software version, etc.)
somebody who gets the update needs to upload the file so a dev can do something with it.
So I got the 217 OTA release today on my D4. Anyone else? Seems good so far.
--Randall
randallman said:
So I got the 217 OTA release today on my D4. Anyone else? Seems good so far.
--Randall
Click to expand...
Click to collapse
It is not available on mine yet.
I got the email, but never got the update. My phone died around lunch and I didn't have a charger until after 5p. I'm wondering if I missed a window.
640k said:
I got the email, but never got the update. My phone died around lunch and I didn't have a charger until after 5p. I'm wondering if I missed a window.
Click to expand...
Click to collapse
Yeah, I never asked to be on a soak test or anything... so I dunno if I was just randomly chosen or if it was released today... I suppose it doesn't really matter. Either way, it's pretty nice I guess A bit late given the fact that JB is the 'new hotness' now
randallman said:
Yeah, I never asked to be on a soak test or anything... so I dunno if I was just randomly chosen or if it was released today... I suppose it doesn't really matter. Either way, it's pretty nice I guess A bit late given the fact that JB is the 'new hotness' now
Click to expand...
Click to collapse
JB doesn't really mean anything. it's an incremental update and I'd be willing to bet some devs whip together a ROM with it included. There's still a chance we'll get it officially for our phone. A SLIGHT chance, but because its only an incremental update, with no new real requirements, it's a decent possibility.
Moto originally committed to 18 months of updates. We basically have until late next year to get it. By then, Klondike will be out and everyone will hate.
I got the update for mine but didnt do it. Mainly because I am rooted and wanted to see if I can first. Only thing I did was root so I can use wifi teather. I left everything else alone. I used to put diff roms in my original droid and got sick of setting it up again.
Were you rooted when you did the update? If so did was there any issues?
prowler9 said:
I got the update for mine but didnt do it. Mainly because I am rooted and wanted to see if I can first. Only thing I did was root so I can use wifi teather. I left everything else alone. I used to put diff roms in my original droid and got sick of setting it up again.
Were you rooted when you did the update? If so did was there any issues?
Click to expand...
Click to collapse
I'm not the OP, but I was rooted using the MotoFail exploit and the update applied without issue. I did have to re-acquire root with Razr's Edge, however, but that was painless.
prowler9 said:
I got the update for mine but didnt do it. Mainly because I am rooted and wanted to see if I can first. Only thing I did was root so I can use wifi teather. I left everything else alone. I used to put diff roms in my original droid and got sick of setting it up again.
Were you rooted when you did the update? If so did was there any issues?
Click to expand...
Click to collapse
I am rooted... I used OTA Rootkeeper to backup and restore root afterwards. I made sure to update the su binary as well from the superuser application as I had read some horror stories about people who lost root and couldn't get it back due to outdated superuser.apk and/or su binaries.
Additionally, my first attempt to install failed... I believe it was because I had added lines to loadpreinstalls.sh and mount_ext3.sh in /system/bin to ensure that the 'adb always root' local.prop file and the su binary was copied back into /data/ and /system/bin respectively every time I booted in case I lost root somehow. I had to remove the extra lines and then start over.
--Randall
Historically, how long before the update is widespread? My phone doesn't see it yet.
Folks, just an FYI.
The full XML.zip of fastboot images for this build has already been released in the development section by Skrillaz_CZ.
This not only means that you dont have to wait for the update at all, but also that we have the best safeguard against any mishaps from modding and flashing possible. You can recover your phone to the current release build no matter what happens using RSD Lite or the fastboot binary and ADB.
Incredibly quick work by Skrillax_CZ to pull this off their server right away like this!
randallman said:
So I got the 217 OTA release today on my D4. Anyone else? Seems good so far.
--Randall
Click to expand...
Click to collapse
Was this a previously owned device? An eBay or other like new used device?
Sent from my DROID4
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Rexxen said:
Hi,
I have a rooted I9295, after the last ota update (2 weeks ago) i noticed that my wifi stopped working and i get an annoying message "Prevention Information". I think the update failed on the radio part which is causing this.
I'm currently on android 4.2.2 with baseband version MF5 and ML3 buildnumber.
can anyone point to a fix ?
thx !
Click to expand...
Click to collapse
I'm not sure if this is the right modem, but it could be. Hopefully somebody else will reply with a proper solution.
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Miami_Son said:
The latest OTA update was for 4.3. Looks like you didn't update at all, but the process borked something up on your phone. Maybe a factory reset will fix your phone. Yeah, major pain, but had you gotten the 4.3 update you'd really be screwed since going back would not be an option and you would have lost root.
Click to expand...
Click to collapse
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Rexxen said:
Unfortunately we're not so lucky in Europe, still no 4.3 update.
The latest OTA update we had here added some more Samsung bloatware and a nice message warning you to close the flappy charge port after charging.
I had a rooted 4.2.2, and i think that caused the problem.
Going to try to update the radio with Odin.
Click to expand...
Click to collapse
Did this work out for you? I'm having the same issue.
Sent from my SAMSUNG-SGH-I537 using Tapatalk
So i ended up doing this:
First i flashed the entire phone (since i couldn't find just the modem)
http://honai-android.blogspot.nl/2014/01/how-to-update-galaxy-s4-active-i9295.html
After that i rooted the phone again
http://androidxda.com/root-samsung-galaxy-s4-active-gt-i9295
And that fixed the issues.
Everything works fine again, and i didn't loose any data in the process.
[solved]
Tried to update the phone to 5.1 OTA. I have unlocked bootloader, TWRP, Root, completely stock 4.4.4 TMO other than that. I flashed the stock recovery back, and I understand that the update will break root. Then I downloaded the OTA, and went to install. It began to install in stock recovery, then rebooted after just a few seconds. Got a message that says something like "sorry there was a problem updating your moto x no changes were made" I accidentally closed the window before writing down exactly what it said, but that was basically it. Any ideas?
Now the OTA isn't even available if I check for it in settings, which is a bummer, but I understand that's probably because of it being a soak test... I just want to be ready for it when it does become available again.
Any helps is appreciated!
------
UPDATE: Solved on Reddit. For those who don't know, you can't flash an OTA if you have rooted, even if you haven't done anything with root. I didn't think this was the case, as it hasn't been an issue with different devices previously, but apparently that changed with lollipop.
rickathenrystuff said:
[solved]
Tried to update the phone to 5.1 OTA. I have unlocked bootloader, TWRP, Root, completely stock 4.4.4 TMO other than that. I flashed the stock recovery back, and I understand that the update will break root. Then I downloaded the OTA, and went to install. It began to install in stock recovery, then rebooted after just a few seconds. Got a message that says something like "sorry there was a problem updating your moto x no changes were made" I accidentally closed the window before writing down exactly what it said, but that was basically it. Any ideas?
Now the OTA isn't even available if I check for it in settings, which is a bummer, but I understand that's probably because of it being a soak test... I just want to be ready for it when it does become available again.
Any helps is appreciated!
------
UPDATE: Solved on Reddit. For those who don't know, you can't flash an OTA if you have rooted, even if you haven't done anything with root. I didn't think this was the case, as it hasn't been an issue with different devices previously, but apparently that changed with lollipop.
Click to expand...
Click to collapse
If you were part of the MFN soak test, you do acknowledge and agree to flashing back to 100% stock if you are rooted, when you accept entrance into the test.
Not being 100% stock HAS been an issue in the past. That is why this thread -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 and its predecessors existed.
.
I never agreed to anything with this one. The update just showed up on my phone. I wasn't a part of the official soak test... Probably just part of the initial rollout/soak test/whatever-it's-called.
Regarding root being an issue before, that simply hasn't been the case for me previously, at least on different phones. It's always been understood that taking the ota would break root, but not that I had to remove root prior to taking it. Even the post you quoted indicates that... "You should expect to lose root when you take an OTA."
Regardless of what it was before, it's worth noting to future people who run in to this issue, that yes, you have to completely remove root in order to accept the ota.
rickathenrystuff said:
I never agreed to anything with this one. The update just showed up on my phone. I wasn't a part of the official soak test... Probably just part of the initial rollout/soak test/whatever-it's-called.
Click to expand...
Click to collapse
I wasn't aware it was being sent out to anyone but those who were invited by the MFN yet... then again, I haven't been on as often lately and might have missed it.
rickathenrystuff said:
Regarding root being an issue before, that simply hasn't been the case for me previously, at least on different phones. It's always been understood that taking the ota would break root, but not that I had to remove root prior to taking it. Even the post you quoted indicates that... "You should expect to lose root when you take an OTA."
Click to expand...
Click to collapse
{bold added by me} And that is the biggest issue we've seen... comparing what happened on other phones to the 2013 X...
I see it happen all too often.
And yes, those posts do say you should expect to lose root... but they also discuss the pre-flash validations, and that returning to stock is required.
rickathenrystuff said:
Regardless of what it was before, it's worth noting to future people who run in to this issue, that yes, you have to completely remove root in order to accept the ota.
Click to expand...
Click to collapse
Oh, I completely agree.
Not sure what this is yet. Non rooted, stock image.
5.1.1?? Will report back...
Not 5.1.1
No idea as they haven't posted changelog, but hopefully a fix for MicroCell issues everyone is experiencing.
Let us know if you see any changes.
Update downloaded.
Real upgrade from OE2 to OF3. Thats all it says.
@Globalrebel where are you looking for change logs?
Update just finished. Yeah Android version is still 5.0.2. Baseband G925AUCU2AOF3 now.
Getting it now.
http://www.att.com/esupport/softwar...are&siteId=JAF5WzpxbKM-uxPru.0S4qk9EABb6wNW3Q
Change Log
Ssj237 said:
http://www.att.com/esupport/softwar...support/sharedSegments/supportViewService.jsp
Change Log
Click to expand...
Click to collapse
Session timed out. Please use the back button, reload and try again.
That build date of june 18th piss anyone else off lol
veener79 said:
Session timed out. Please use the back button, reload and try again.
Click to expand...
Click to collapse
Should be fix now
msfguard said:
That build date of june 18th piss anyone else off lol
Click to expand...
Click to collapse
You mean since 5.1.1 was supposed to hit the S6's "in June?"
This is getting ridiculous, we need an update from 5.0.2, the memory issues I'm dealing with even on XtreStoLite are almost unbearable
Exactly and as updates for 5.1 come out for other carriers we get updates for random att crap that are almost a month old
It's sad to say that the latest AT&T OTA patches the export for ping pong root, don't take the OTA, because you cannot downgrade the Odin fails
dnp77 said:
It's sad to say that the latest AT&T OTA patches the export for ping pong root, don't take the OTA, because you cannot downgrade the Odin fails
Click to expand...
Click to collapse
how you know? you ota it ?
i was "downloading" then saw your post. so i reboot my phone to cancel it.
netnerd said:
how you know? you ota it ?
i was "downloading" then saw your post. so i reboot my phone to cancel it.
Click to expand...
Click to collapse
They know because it says on the Ping Pong Root thread not to update for anything past May 15th as the method for root has been patched
I'm curious if there are any other undocumented changes besides the 2 official changes listed earlier. It feels like a fairly big patch for a fix to an phone location and a kernel security fix.
Is there any hope, luck or signs of achieving root on this new firmware
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Wow, what a crappy push out by AT&T.
In any case, what process do i need to freeze in TB to stop my phone from trying to download and/or annoying me with that pop-up when it does happen?
aidanipod said:
Is there any hope, luck or signs of achieving root on this new firmware
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
Please see just ONE post above yours........ we have just been talking about the exploit being patched
Globalrebel said:
Wow, what a crappy push out by AT&T.
In any case, what process do i need to freeze in TB to stop my phone from trying to download and/or annoying me with that pop-up when it does happen?
Click to expand...
Click to collapse
AT&T Software Update is the main one, but there are a few others - I don't have an AT&T ROM on mine right now to help out, but it's been posted a few times already (I think I even posted those once)
Just freeze att software update. Then it can't even run so no downloads. I got lucky I clicked on update after reading it in Android central but didn't want to install it. Postponed couple of times but somehow it automatically loaded the update process. I was like sh#t. When it booted up it said a problem updating. And then I blocked the updater. My root almost gone lol
Sent from my SAMSUNG-SM-T337A using Tapatalk
saketkutta said:
Just freeze att software update. Then it can't even run so no downloads. I got lucky I clicked on update after reading it in Android central but didn't want to install it. Postponed couple of times but somehow it automatically loaded the update process. I was like sh#t. When it booted up it said a problem updating. And then I blocked the updater. My root almost gone lol
Sent from my SAMSUNG-SM-T337A using Tapatalk
Click to expand...
Click to collapse
Same thing happened to me being rooted. It just tried to install automatically. Woke up to my phone restarting but then I got the error "problem updating". I was pretty relieved on that error lol... :victory: