Database Develop

What version is the latest and will I get updates although I'm in GSM mode?

Hi! My Software-Version is 5.5.959, I heard about a version 5.6.890. What is the latest version that most people have and will I get OTA updates as my Droid 3 is rooted and I am using it in GSM-Mode in Germany?
Thanks

Additional info: Of course I changed some apk's names to bak in /system/app/ will this prevent me from getting updates, too?

To address both your questions -
1) You will be able to get updates on GSM mode - no problem. But only after they are published on Motorola servers - you will not be able to receive PUSH OTA from Verizon. Which is not end of the world since eventually you will get the update once it is released officially (forget about soak tests/etc).
2) Altering stuff in /system will 100% prevent you from getting update. You must restore content the way it was stock before trying to apply an update or it will fail to proceed due to checksum errors.

Thanks for your explanations

Received an F/W update from Samsung Yesterday!!! India

Hi All,
Im on the Official ICS ROM INDIA...4.0.3 DDLP4
Yesterday, when i checked kies, there was an update waiting (No Update on OTA). The downloading of firmware was taking ages to download(3.2mbps connection) and after about 70 percent the downloading stopped and Kies said "Connection stopped"....
Any body who has downloaded the F/W can you please post the change log (If you find any).. I mainly wanna know, if the laggness of the lock screen and slowness to open contact's and capturing pics has been rectified.

Ramith123
Ah glad that i have company.sad at the same time!! Even i have the same problem after the 7mb OTA update. The andriod process closes often and hangs the phone.The phone was literally unusable. Hence i tried to install custom gingerbread rom on it. Now its almost completely bricked.How irresponsible is samsung to roll these things out without testing it thoroughly.
***PLEASE DON'T INSTALL THE 7MB ICS OTA UPDATE***
hopefully we can save some.

I also tried to update through OTA but it was failed and message popped up that do update through Kies. Now I got update through Kies and my firmware changed from DDLP4 to DDLPA. However I lost Root.

I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8

dushy4 said:
I also received the update notification. Downloaded the 7.8 mb update within a minute and asked for reboot. Everything worked fine and nothing special noticed. It just changed the build no. from IML74K.DDLPA to IML74K.DDLP8
Click to expand...
Click to collapse
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.

Hey guys basically its stability update. my phone feels much smoother now. i updated OTA via wifi, i also faced update not installed issue and i found out the problem, basically we all root our device that means we change SU binaries so when updating phone OTA it checks for those binaries and if these binaries are not official OTA update get aborted. i solved this problem like this,
1) I have downloaded STOCK LP8 firmware from samobile.com when it released
2) As my phone is rooted my SU binaries are changed so OTA update is aborted.
3) So FLASHED Stock rom LP8 from PC ODIN which kept my all DATA, APPS intact i just lost my root and some mods like 15toggles status bar and so..
4)then i started updating my phone using S/W update in settings, its 7.85MB file.
5)In few minutes my phone is updated to LPA
6)Now i again rooted my phone and my all data apps are intact and mob is much improved in stability.
Hope this will help you guys.

anjath said:
you mean LP8 to LPA? check your kernel version date. if it shows 12 June then fine, else your kernel has not been updated.
Click to expand...
Click to collapse
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.

dushy4 said:
It still shows 12 may,,, But i read in some other thread that kernel was not updated in this update.
Click to expand...
Click to collapse
kernel is definitely updated in LPA. just flash LPA ROM file using Odin.
I also agree with what mullarameez has pointed out. rooting might be the reason for kernel being skipped. because if u flash LPA with odin you will lose root and hence get the new kernel.

Is there a way to update Kernel without flashing the whole 650 mb rom?

with all the issues in ICS, i think it would be safest if you would flash using the whole LPA ROM. I know its a pain to download but worth it in the end.

OMG! just a 7Mb update took 2hrs to download.. Hmmmm...
My main prob was with Lock screen, camera and contacts.. Noting has been resolved on this new Update!!!

what is the issue? is it lag?

This is confusing..
I have everything stock on my phone..All updates done OTA since i bought the phone..Not rooted..
Still the kernel says 12 May after the 7mb update..Why?? Although the deep sleep issue (sore point for me) seems to have been resolved after this update...
PS: The build info after *#1234# says 12 June, if that matters..

yes, almost all the users who updated OTA have the same issue. you may flash the new LPA using PC Odin from doc's post (anyways you're not rooted so no problem)

Nexus 6 (Verizon) still running MOB31H (6.0.1). Should I manually update via OTA?

I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.

1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.

Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?

Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.

October OTA Update 4BQJ2 is out

Just got my OTA update notification. Update went smoothly (sorry, forgot to check file size before updating. Confirmed BlueBorne vulnerability is fixed.

Not sure if this is unique to me, but post-update, my phone is now telling me my SD card is unsupported and asking me if I want to format. Really hoping to avoid backing up a 200GB card, formatting and restoring this weekend. Not sure if anyone else is having this issue too or if just my luck to have to deal with, but just a warning out there to those who may decide they want to unmount their SD cards before updating.

FWIW, my device seems to be running just a bit smoother after a day of use. No noticeable change in battery life. Pleased with the update so far.

quick newbie question, I have the G935A , fully stocked, but using it on a Canadian network, I was told I won't get the update via OTA so I installed Smart Switch, but it also says my device is up to date which has the May security patch installed (that's what it came with when I bought it last month). Any idea where I can find just the OTA patch and update the phone ?

bestjsg said:
quick newbie question, I have the G935A , fully stocked, but using it on a Canadian network, I was told I won't get the update via OTA so I installed Smart Switch, but it also says my device is up to date which has the May security patch installed (that's what it came with when I bought it last month). Any idea where I can find just the OTA patch and update the phone ?
Click to expand...
Click to collapse
If you aren't running on an AT&T network, you might seriously consider switching to the U firmware. Of course, Samsung conveniently forgets the U firmware exists too, so that might not gain you a whole lot at the moment.

I have the U firmware and I've been checking for updates, but nothing (I'm on the August security patch). Is there a way to force the update or use Odin or side load it? My phone was originally built for the Sprint network, then the previous owner flashed it to work on AT&T. I was not able to get any updates (was stuck on the May security patch). I used Odin to put the U firmware on it and then got 3 security patch updates after that.

caferacer73 said:
I have the U firmware and I've been checking for updates, but nothing (I'm on the August security patch). Is there a way to force the update or use Odin or side load it? My phone was originally built for the Sprint network, then the previous owner flashed it to work on AT&T. I was not able to get any updates (was stuck on the May security patch). I used Odin to put the U firmware on it and then got 3 security patch updates after that.
Click to expand...
Click to collapse
The U firmware always lags the carrier firmware. August is sadly the current date for the unlocked devices for now.

All I had to do was be patient. I got the newest update (4BQJ5 - November security patch) this morning.

Any way to force 8.1 OTA on Project Fi X4?

Greetings, I have a Project Fi Android One X4. Two days ago I went back to Project Fi Oreo stock after being rooted in order to receive the OTA. I received the January, February, and March security updates. But once I attempt to get the April one with 8.1, the system says I am up to date. I attempted to sideload the April OTA but got the message many get about not being able to mount. I know that these updates are not rolled out all at once, but I see many here in the forum already got it. Is there any way I can force the OTA? Thanks in advance for the help!

I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.

jfalls63 said:
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
Click to expand...
Click to collapse
Same issue for me. The ADB sideload/SD card problem doesn't make sense.

Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.

ptn107 said:
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
Click to expand...
Click to collapse
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.

rczrider said:
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
Click to expand...
Click to collapse
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.

Thanks for all the responses! I see that I am not the only one with this issue. I think that like jfalls63 said, of we don't get the update in the coming days we will have to wait for the full firmware release. It is not convenient since I want to root and wanted to do it in 8.1, but there is not much we can do about it if we cannot find an alternative.

QWZR II said:
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Click to expand...
Click to collapse
You're right; I haven't had any reason to do either since the update and it wasn't until after I posted that I saw another thread mentioning this issue. Sure enough, same is true for me.
Still, the update was pushed to one of our phones only a couple of days ago, so if they pulled it, it's only been within the last 72 hours or so.

I'm experiencing a similar thing (https://forum.xda-developers.com/moto-x4/help/oreo-8-1-update-stuck-loop-t3788293), so this seems to be a prevalent problem.
When I have time, I'll go through the Moto forums and see if anyone has any helpful information.

I'm on Fi and I received the 8.1 update just fine. I haven't unlocked my bootloader yet to root it, but otherwise I'm on the gravy train. Once they release a full sized firmware I plan to reflash to get my space back, and then root.

The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.