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?

Looks like 217 OTA was released today?

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

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:

When Will I get Android 7.0 OTA?

Hello all, I have a Nexus 6 and I'm using it on Verizon's network. I have yet to receive the Android 7.0 OTA update. Should I have gotten this already or is there something possibly wrong with my situation? I've searched online and it seems like I should have gotten the update already. I appreciate any help.

You should have had it by now (unless you have modified your phone in any way that might interfere with the OTA process)
Your best bet would be to sideload the OTA from https://developers.google.com/android/ota

Yeah, it's a bone stock Nexus 6. I got it from Amazon around this time last year, and I received the 6.0.1 OTA update and I receive the android security patch updates. Just no update to 7.0.

When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.

I think that there are a lot of N6 (mine is on T-mobile) out there that have not seen an OTA. I got the 6.01 November secuity patch last week. Was expecting 7.0.

I went ahead and did a sideload of the OTA 7.0. This won't break any future OTA updates, will it?

xdatastic said:
When my Australian carrier delays updates I used to change my SIM to a foreign one (cambodia, vietnam, thailand, or whatever) and the update used to immediately appear. The SIM doesn't even need to be active.
Now that Google publish the OTA files, it's easier just to sideload it.
Anyway, try a different SIM (t-mobile or whatever you can find locally) and see if it appears (you need to reboot). Otherwise, Verizon only just approved the update a few days ago so might take a while to roll out to you.
Click to expand...
Click to collapse
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.

russ4h said:
Ah.. I'm kind out of the loop these days, but I thought the Nexus devices got their updates straight from the Google. So I figured the carrier had nothing to do with how or when you got your updates.
Click to expand...
Click to collapse
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/

xdatastic said:
The updates come from Google, but some carriers in some countries require an approval process (it's the same for Apple iphone, but is done more seamlessly and under NDA). Here in Australia, any devices sold by a carrier must go thru an approval process to make sure the software doesn't violate any compliance regulations (such as ability for emergency calling when no sim is present). Once Google get the go-ahead, they push the update to the phone with the relevant sim card in (or in some cases the IMEI). This can sometimes (dependant on current software version) be bypassed by changing the sim to one that doesnt require approval or has already been approved. Bear in mind however, you may get a software build not intended for your carrier.
Here's verizon's update info from a few days ago:
https://www.verizonwireless.com/support/google-nexus-6-update/
Click to expand...
Click to collapse
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?

russ4h said:
Hey, thanks! I guess I just needed to wait a little while longer haha. I just finished the sideload and everything seems to be working well. Do you know if the sideload process somehow breaks future OTA updates?
Click to expand...
Click to collapse
Nope, the sideload doesn't break future OTA updates (however it theoretically could if you flashed a build not intended for your carrier, however usually Google just send a 'Full OTA' which a large download to your device to get it back on the correct build).
Enjoy.

I was offered 7.0 and it took rooted
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.

tbared said:
So ive been rooted since u bought the phone when it came it in 2014 and have sideloaded any updates and i received the 7.0 notice OTA and i figuredbid just see if it would update. It did and then i list root , wh?? Im green with Android but i struggke through it to get ehat i need done so im sorry if this is a noob question.
Nexus 6
Was the 59 build first series.
I was rooted with SuoerSU.
Click to expand...
Click to collapse
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.

I joined (then left) the Beta program so i can get a stable release of 7.0 Nougat a little over a month ago. Good so far but what I'm concerned about is security patches. Ever since I got on Nougat, my N6 no longer gets OTA security patches. I'm still on the October security patch. Anyone know what's going on?

Regardless, even with a mod'd phone, I got the 7.0 nag 2 weeks ago - which spurred me to wipe everything and flash it with NRT.

alryder said:
I always lose root when flashing an image or installing an OTA update. It is normal for that to happen. You just need to root your phone again by installing SuperSU . The latest version is SuperSU v2.78 SR5 and can be found here.
Click to expand...
Click to collapse
Thanks as soon as i have some time i will reinstall and flas..