Develop Bugs

Any one had the FOTA update yet?

http://www.htc.com/europe/support.aspx
Update – HTC Desire Firmware Over The Air (FOTA) update
In our commitment to providing you with the best user experience, we are pushing out a new firmware update to your phone. Your phone will receive a notification of this update when it is made available. Simply press OK to accept the update via a data connection such as Wi-Fi or GPRS/3G. After installing the update, you can confirm a successful update by confirming the Software Number (From the Home Screen go to MENU> Settings> About Phone> Software information> Software number). The new software number after the update will be 1.15.405.4 for an HTC phone.

Haven't had it pushed out, but have done a manual update.
Went on fine.

Looks like us T-Mobile users are gonna have to wait ages.
I wanted to try an update before having the handset swapped for the pink hue issue. ffs

Yep, was notified there was an update available yesterday evening.
Downloaded and installed, can't notice any differences on the front-end, must have done something though!

Just noticed that there is another post RE this -
http://forum.xda-developers.com/showthread.php?t=656371

Arthur Hucksake said:
Looks like us T-Mobile users are gonna have to wait ages.
I wanted to try an update before having the handset swapped for the pink hue issue. ffs
Click to expand...
Click to collapse
Mine is T-Mobile, but came from mobiles.co.uk as opposed to direct.

400ixl said:
Haven't had it pushed out, but have done a manual update.
Click to expand...
Click to collapse
How did you do it manually? Can i do it too with my t-mobile desire?

shaliru said:
How did you do it manually? Can i do it too with my t-mobile desire?
Click to expand...
Click to collapse
No, T-Mobile not done any updates as yet.
I've tried the Manual update and there is nothing as yet.

no update for me yet!

Hey guys,
I am so jealous that everyone has Mango and I dont. And upon further research, it seems like I havn't gotten any updates!
I have a LG Optimus 7 (e900 i believe). I am in Canada on Telus network. I do have a valid developer account on the marketplace and my phone is unlocked through the official tool.
I didn't force nodo (and now i dont even believe I have nodo since everyone had a higher OS version even before updating to mango).
I havnt installed anything other then apps from marketplace and no mods either.
My info
OS version: 7.0.7392.0
Firmware revision number: 1.0.5.10
Hardware revision number: 1.0.0.0
radio software version: 1.0.5.10
radio hardware version: 0.3.5.0
bootloader version: 1.5.1.0
Chip SOC version: 0.30.2.0
I tried reinstalling zune but the installer said I already have the latest version (4.8).
Should I just be patient? I dont want to do the whole force the update thing.

You have NoDo. In fact, you have NoDo plus the security update that was release a couple of months after NoDo. NoDO was 7390. The security update was 7392.
So, unless you want to try the disconnect trick, you should just be patient. You'll get your update notice within the next 2-3 weeks at the most.

I forced the update on O2 UK TouchHD7 by following these instructions
FOR THOSE THAT IT WONT WORK FOR READ THIS!
click check for update like normal but have your phone in hand and ready to set to airplane mode at the time where you would normally dc your computers internet.
I did not have to dc my computers internet, just the phones and it worked perfectly for me.
In my case I had to switch to airplane mode at ~34 seconds.
It helps if you time it the first time and see how long it takes to tell you your
phone is up to date and then subtract about a second. GL hope this helps
from this thread
http://wmpoweruser.com/simple-trick-to-force-the-mango-update/#

I'm on Telus with an HTC Surround. No updated yet. Using RTM version.

Just force the update

you can try this link :http://forum.xda-developers.com/showthread.php?t=1287505

Still no update, should I force it now or give it more time? I read somewhere that forcing may not update my drivers and I want everything to be udpated.

masfenix said:
Still no update, should I force it now or give it more time? I read somewhere that forcing may not update my drivers and I want everything to be udpated.
Click to expand...
Click to collapse
I recommend against it. The update you'll get may well not be the specific update meant for your phone. There can be various issues with the wrong update.

masfenix said:
Still no update, should I force it now or give it more time? I read somewhere that forcing may not update my drivers and I want everything to be udpated.
Click to expand...
Click to collapse
I'd force it. Microsoft themselves has referred to it as cutting in line. I believe I've also heard the guys on the Windows Phone Radio podcast (which is official) mention that they told their friends to do it.

same for my new HD7s
this same thing is going on with my new HD7s. Stuck at 7392. Just received it, yesterday, from AT&T. Do we know anything further about this?
matt

I'm on T-mobile with Omnia 7 and no update for me yet

any takju 4.0.4 people in the US release OTA yet.

the other thread is getting way too long and still no clear answer if anyone in the US is getting the OTA normally or through clearing services framework method. i believe some people were able to get it that way, but in UK

I'm on 4.0.04 takju and still haven't received the OTA update. My check now button is starting to wear out haha
On a side note, how does google determine who gets the update first?

got restless and just updated using toolkit 7.3 and booting to custom recovery. jelly bean is awesome.

does new OTA remove universal search?
Is the new OTA on verizon galaxy nexi the one that removes universal search?

CoronaDelux said:
I'm on 4.0.04 takju and still haven't received the OTA update. My check now button is starting to wear out haha
On a side note, how does google determine who gets the update first?
Click to expand...
Click to collapse
Lol agreed. I'm wearing out the check button as well but I'm still seeing "Your system is currently up to date".
Sigh.

Mounta1n said:
Is the new OTA on verizon galaxy nexi the one that removes universal search?
Click to expand...
Click to collapse
There's no OTA for the Verizon one, and we probably won't see it for a couple months.
And no, 4.1.1 doesn't remove universal search. Its probably going to be removed with updates to the Search app via the Play Store. It doesn't need an OS update.
blurryat2am said:
Lol agreed. I'm wearing out the check button as well but I'm still seeing "Your system is currently up to date".
Sigh.
Click to expand...
Click to collapse
The "check now" button isn't going to do anything if your IMEI hasn't been selected to take the OTA. They roll out in waves and it doesn't matter where you are or what your carrier is. Just wait for it and stop worrying, or flash it manually.

Finally....a New USA Firmware Update - NPNS25.137-35-5

But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
https://mobilesupport.lenovo.com/us/en/solution/MS118647

Pig Vomit said:
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
https://mobilesupport.lenovo.com/us/en/solution/MS118647
Click to expand...
Click to collapse
I'm on the NPN25.137.35 with the latest security patch level showing from January. Phone is telling me it is up to date Not sure it maters but I'm in Salt lake City, UT.

I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk

redbeard1083 said:
I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk
Click to expand...
Click to collapse
Stange, why would you have had the update for a week and I havn't even received it yet?

emoney1219 said:
Stange, why would you have had the update for a week and I havn't even received it yet?
Click to expand...
Click to collapse
It's very typical for carriers and manufacturers (including Google for Nexus/Pixel) to do staggered rollouts of updates. It reduces server load, but more importantly, if there is a bug the people who get it early (there are typically not that many who get it early) would report the bug. Then the second batch of people getting it is bigger, then the third even bigger. Rollouts can last 3-4 weeks. I wouldn't panic. We are their beta testers.
Location probably doesn't matter. I'm based in OC, but currently in the Palm Springs area.

redbeard1083 said:
I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk
Click to expand...
Click to collapse
Flashable from TWRP or fastboot?
Edit: Question Answered

Pig Vomit said:
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
Click to expand...
Click to collapse
Hi,
Identical to the RETEU update from the last week! Still waiting for a "real" update.

Still nowt for retgb

I tried to adb sideload the zip above but I get an error. Any ideas? I dropped the name "BLUR version" and renamed the zip "update.zip"...got the error. I redownloaded and renamed to NPNS25.137-35-5...same error
Edit: here is the error message "package expects build thumbprint of 7.0/NPNS25.137-35-5/5 user release-keys or 7.0/NPN25.137-35/37 user release keys; this device has 7.0/NPN25.137-33/35 user/release -keys"
Is there another firmware that I need to download and apply first?
Edit 2: does motorola require fastboot all the files (unzipped) instead of adb? In my other phones I just put the update.zip file on the root directory and applied with stock recovery. That did not work either. Same error message.

long2ski said:
I tried to adb sideload the zip above but I get an error. Any ideas? I dropped the name "BLUR version" and renamed the zip "update.zip"...got the error. I redownloaded and renamed to NPNS25.137-35-5...same error
Edit: here is the error message "package expects build thumbprint of 7.0/NPNS25.137-35-5/5 user release-keys or 7.0/NPN25.137-35/37 user release keys; this device has 7.0/NPN25.137-33/35 user/release -keys"
Is there another firmware that I need to download and apply first?
Edit 2: does motorola require fastboot all the files (unzipped) instead of adb? In my other phones I just put the update.zip file on the root directory and applied with stock recovery. That did not work either. Same error message.
Click to expand...
Click to collapse
You should probably just wait until the OTA pops up on your device.

Nothing yet for me. Pennsylvania, RETUS. Will notify once I have it available.

arhncmh said:
Nothing yet for me. Pennsylvania, RETUS. Will notify once I have it available.
Click to expand...
Click to collapse
I'm in NYC and just got it. I installed it but it was weird, my security updates updated to May 2017, but my build number is still NPNS25.137-33-5. I checked again for updates but it said I'm current. Also, my kernel is 3.18.31 dated 5/11/2017. Did I update?

MrBelter said:
Still nowt for retgb
Click to expand...
Click to collapse
I installed this https://www.androidfilehost.com/?fid=961840155545581088 using the toolkit on this forum and works all ok here in the UK.
Wifi, NFC, etc all seem to be working. Even got Google Assitant fired up
Happy days

esoh said:
I'm in NYC and just got it. I installed it but it was weird, my security updates updated to May 2017, but my build number is still NPNS25.137-33-5. I checked again for updates but it said I'm current. Also, my kernel is 3.18.31 dated 5/11/2017. Did I update?
Click to expand...
Click to collapse
yep. they added -5.

redbeard1083 said:
yep. they added -5.
Click to expand...
Click to collapse
I think my security updated to May but I don't think my firmware upgraded. It was on 50MB file.

Adb sideload
Has anyone tried to do a ADB sideload with the OTA yet?
QUOTE=redbeard1083;73003392]I got this update last week. I have the OTA zip if needed.
https://drive.google.com/file/d/0B3psf9d4jji1Ny1lYnFnN3o4WjA/view?usp=drivesdk[/QUOTE]

I would say just be patient. I received the update yesterday. You've waited this long, right?

Pig Vomit said:
But.....the only change listed is that it includes the May, 2017 security update. About a 50MB download.
https://mobilesupport.lenovo.com/us/en/solution/MS118647
Click to expand...
Click to collapse
This update should contain the bugfixes up through the May security bulletins if I understand it correctly.
https://source.android.com/security/bulletin/
Started prompting me for this update last weekend on amz branch.

Im in NYC as well and just got the update. It showed as NPN25.137-35 but it said it was a 20MB download. I have the amazon prime version of the phone and once i finished the update, it still shows NPN25.137.33 and the security patch level still shows Jan1, 2017.
Now when i check for updates, software is up to date. Wierd. Anyone else experience this?

I've checked for a US g5+ support page fairly regularly since getting the phone. It hasn't even been listed on the support page until the last week or so. But, while it's finally listed.......there's only a generic Lenovo placeholder on it. Several months after the phone's release.
https://mobilesupport.lenovo.com/us/en/products/Cell-Phones/Android-Series/Moto-G-Plus-5th-Gen
I've got a Lenovo laptop......their customer service and software upgrades suck. I once sent in my rather expensive Yoga laptop for warranty trackpad repair......and they had it for two months and despite repeated checking their website and calling, I could never get an estimated repair date. Finally, they gave me a date......4 more months. I raised holy hell and they sent me a new, more recent Yoga release. The support page for the laptop seems to update with Lenovo bloatware "upgrades" fairly regularly.....but their support for more important basic drivers is pretty lacking (wifi, bluetooth and graphics drivers from 2015 and 2016, anybody? Yeah, didn't think so.). And, yeah, first thing I do when getting any new PC is a clean install with no bloatware, but Lenovo also makes it tough to keep drivers updated through forced windows updates by using hardware IDs which make it hard for you to install generic component drivers, unimportant drivers like Intel graphics drivers. So you install the latest, and a forced windows update uninstalls the Intel release and installs a mid-2016 driver for you. Thanks! So there are obscure ways to defeat that.
Oh, and then there's the touchpad Synaptics drivers (Lenovo specific) where two finger tap (right click menu) has NEVER been fixed. Takes a registry modification to fix it.
Anyway...enough venting about Lenovo/Moto poor support. I knew it when I purchased the phone, and I'd still buy it again.

Question Still on November update anyway to hurry up January update?

Title says it all, is there a non root way to hurry up the update? I haven't had the popup to update android and was hoping there's a way to check for updates

Settings/system I believe, to check for updates or you can download and sideload the update.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com

Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.

Sideload the OTA

NippleSauce said:
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Click to expand...
Click to collapse
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.

pcriz said:
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
Click to expand...
Click to collapse
You're pretty much correct here. I suppose that Google was a bad example to use. But essentially, the carrier builds allow the applicable carrier to also push apks through when you pull the update OTA. They're not necessarily packaged within the factory image - so I had some horrible word choices in my initial post as they don't really modify the image lmao. But (when looking at the older builds) if you just install the stock build instead of flashing one of the carrier builds, then you won't have to worry about any carrier apps being pulled in along with your OTA update.
But heck, if you're rooted and want to maintain root (and are thus manually updating whilst having OTA disabled), then you wouldn't have to worry about this at all, haha.
Samsung phones were a better example of this, as whenever I would do an OTA update on my S21U, it would also install around 4-5 T-Mobile bloatware apps. But if you manually installed the stock image, that wouldn't happen anymore when updating OTA.