Database Develop

Got the new Android 2.0.1 on my G1

Hey Guys, did anyone else get the update for the new android 2.0.1 notification on their phone.
I just got it and i started downloading it...

Really? post the log so we can get the download link

http://i6.photobucket.com/albums/y225/Makaveli6924_7/2009-12-29-144007.jpg

How do i get the log?

Why put this in this section?

why does it say for motorola droid??

This thread is putting my BS meter into overdrive. Of course, its also putting my stupidity meter into overdrive too LOL
~DM

That's why i posted my question here to see if anyone else got the notification, it's weird man.. what do you think is happening, i have a rooted phone also?

What rom did you have when you received the update notfication?

I have the first 1.6 root, i can't remember who made the rom.

http://i6.photobucket.com/albums/y225/Makaveli6924_7/2009-12-29-153540.jpg

I might not too sure then. You could try it and see if it works and check if the camera works. Although I can't be held responsible if anything goes wrong. Try and look up on how to get a log so we can also get a link to the ota update.

Not really possible if you ask me. It's from Verizon, which shouldn't hit your phone unless you're on their network from what I understand and that isn't possible because Dreams don't support CDMA.
As for the update, it would be much larger than 10.2MB, which means what you're downloading is the update to go from 2.0 on a DROID to 2.0.1.

M..N said:
I might not too sure then. You could try it and see if it works and check if the camera works. Although I can't be held responsible if anything goes wrong. Try and look up on how to get a log so we can also get a link to the ota update.
Click to expand...
Click to collapse
if he has root, he shouldn't be getting ota updates, should he?
it makes me suspicious because it gives the verizon site and refers to the phone as "your Motorola DROID"

I wouldn't touch that "update" with a 10ft pole! Either fake, he forced the download, or something seriously messed up is going on, but that does not look to be a legit update for the G1.

grandomegabosses said:
if he has root, he shouldn't be getting ota updates, should he?
it makes me suspicious because it gives the verizon site and refers to the phone as "your Motorola DROID"
Click to expand...
Click to collapse
You can still get OTA updates with root, it just depends on what ROM you use. I believe very old CyanogenMOD and other ROMs had OTA still turned on.
OP - While you're posting pictures, can we see a picture from under Settings > About Phone? Be sure to include firmware version :]

My guess would be that his build.trout.prop has the droid fingerprint/keys/device id in it, or he is using a droid build.prop and he will most likely soft brick his device. I hope there is no radio update, so it doesn't get true bricked.

jerhoyet said:
You can still get OTA updates with root, it just depends on what ROM you use. I believe very old CyanogenMOD and other ROMs had OTA still turned on.
OP - While you're posting pictures, can we see a picture from under Settings > About Phone? Be sure to include firmware version :]
Click to expand...
Click to collapse
you're not supposed to be getting them. weird. i haven't gotten one ota update notification ever since i rooted. and that was more than a year ago. pre-cupcake.

Ok guys i got bad news, the stupid update didn't do anything to my phone. Once the download completed, I restarted the phone and still was running my rooted 1.6. Also I checked the system update and it is still shows the Android 2.0.1 update.

afghanali said:
Ok guys i got bad news, the stupid update didn't do anything to my phone. Once the download completed, I restarted the phone and still was running my rooted 1.6. Also I checked the system update and it is still shows the Android 2.0.1 update.
Click to expand...
Click to collapse
Are you sure you're running a 1.6 ROM?
Can we see a screenshot or picture from Settings > About Phone?

Incredible OTA Update 1.65.605.2

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.

OTA 139.15.1 keep root

All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?

First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X

Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...

You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X

The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X

mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.

dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X

mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk

juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191

will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.

MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!

boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you

dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.

will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.

jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.

will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.

jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being

2013 Lollipop update didn't work?

[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.

AT&T Software update as of 7/9/15 - 146.75MB

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: