Hi everyone!
I've just received and successfully installed a system update for Android 5.1.1 and it says exactly zero about itself. Even Android's version hasn't changed.
Does anyone have any idea what it fixes? I surmise it fixes two recent holes but 10MB sounds a little too much for that.
I also got but nothing happened
Sent from my Nexus 5
I got it, I'm updating manually since for some reason my phone never wants to update the regular way.
It addresses the Stagefright vulnerability
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
ApTeM said:
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
Click to expand...
Click to collapse
flash it through ADB
I use this thread as reference just to make sure I don't miss any step but there are a few others threads like this. http://forum.xda-developers.com/google-nexus-5/general/guide-update-rooted-device-to-5-1-lmy47d-t3050789
OTA install error
I got the OTA notification to download & install the Stagefright patch. Every time I try to install it, it says "error!" shortly after it starts to install and shows the android with a red exclamation point.
My nexus 5 is stock & unrooted.
Any idea what's causing this and how to force the install? If not, I can sideload OTA with ADB later tonight.
Thanks!
I think the build number should have changed to LMY48I.
vagosto said:
flash it through ADB
Click to expand...
Click to collapse
adb fastboot
I've had my first freeze and first complete blackout since this small update
This should be the monthly update mentioned on main page
This update is worthless: http://www.theregister.co.uk/2015/0...efright_fix_wont_be_resolved_until_september/
I will skip it.
Related
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
boyansky78 said:
Hi guys, a couple of months ago I've rooted my new S2+ and after Alex posted the new 4.2.2 I've flashed my device with RDS_GT-I9105P-XEO-I9105PXXAMC2 (topic here GT-I9105/I9105P Stock Prerooted Firmware Without loss of warranty(4.2.2) http://forum.xda-developers.com/showthread.php?t=2334103).
So far it is working perfect! This week I've received a notification, that there is a new update available OTA for my device, so I've decided to download and install it. I've downloaded it, the phone restarts and starts to install the "new update", but at 25% shows an error (the Android guy wearing the red triangle etc. and reboots automatically).
After the restart the OS boots normally and is working OK as previous.
My question is: Since my phone has a prerooted stock FW (4.2.2) and is rooted at the same time running CWM, why I can't install the latest updates OTA?
If CW is causing this, why am I able to get the OTA update notification?
Thanks for the replies.
Click to expand...
Click to collapse
that is because it is a modded firmware
safariking said:
that is because it is a modded firmware
Click to expand...
Click to collapse
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
boyansky78 said:
I understand that the FW is modded, as the previous one (4.1.2), which I've downloaded from here and installed on my G2+. But with 4.1.2 at that time I wasn't able to check for any updates for my OS. Every time I've checked manually for updates, the OS gave me error message, that this is not possible. And now with 4.2.2 I am not only able to check if my FW is the latest, but also to download and install 1/4 of the updates. I am trying to find the algorithm here.
Click to expand...
Click to collapse
I will say it again
It is not possible to check for updates because the Firmware is modded and not original anymore that's why!!!
Hi "safariking",
In the current situation we have two identically modded FWs, but a different outcome.
It's very nice of you to take the time to answer my question so fully That's why I'd like to thank you for the effort. Herewith I am closing the topic.
Cheers.
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
safariking said:
No probs guy i will repeat myself 100 times no problem
Verstuurd van mijn GT-I9105P
Click to expand...
Click to collapse
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
nickchk said:
chill down everyone safari bro,this guy trying to say he got updated with mod fw,just when reach certain percent,the downloaded file seems corrupted. Now i understand mod fw can't even received the ota file,but how this process is allowed, and what happened with the ota file he downloaded?
either way,it's pointless,1st the phone fail to update completely(stuck at 25%), 2nd i don't think this problem can be solved.
cheers everyone~ :highfive:
Click to expand...
Click to collapse
Hi Nick,
Thanks for your reply. You are reading my mind. The issue is really interesting & I think it is worth discussing this.
Safari is right, when he says that FW upgrade OTA for customized ROM is not possible. This is of course true and no one has ever doubted it. This is why when I had the 4.1.2 installed on my G2+ no update was even possible. Droid detects immediately, that the OS has been modified and that you are not running stock ROM.
Okay, so far so good.
Now I have pre-rooted 4.2.2 installed on my phone. When I hit the "Check for update button" it detects that my OS is genuine (although it is not), downloads the whole update package (see screenshot), restarts the phone (part of the update process) and starts installing the update. When the installation reaches 25%, an error message appears saying, that an error has occurred. The phone restarts and loads the "old" OS.
I have tested this a several times and it always hangs on 25%.
The question is NOT why I CAN'T install OTA updates on modified ROM. The question is why I CAN download and install OTA updates on modified ROM.
My suggestion is that:
ROM 1 (4.1.2) had a modified kernel. That's why the OTA updates were not possible.
ROM 2 (4.2.2) is pre-rooted. And I assume it is just stock FW (kernel not modified) with few modifications in the user permissions. This would explain the OTA update and why it reaches download mode and hangs on 25% of the installation.
I hope this brings more clarification to the situation and this would be useful to all members of the forum.
Cheers!:highfive:
I have randomly come across and read posts and topics on this in the other devices' forum.
If I remember correctly, it is the custom recovery, i.e Cwm or twrp that blocks or interrupts the OTA process. 2 reasons why: you'll lose root access if the update went through. Secondly, if a user freezes or uninstalls stock apps like S Voice, Chat On etc, there will be trouble.
There are some ways of allowing an OTA to get pass a custom recovery. I think TWRP has this feature. Again, I stand corrected here lol.
Heard of OTA Root Keeper but no idea how it works
Sent from my GT-I9105 using xda app-developers app
Okay so I've just received a refurbished Nexus 5 from Google as my old one had a hardware power button fail. Anyway I've decided this time round I'm not going to root and wanted the phone completely stock so thought I would do all the OTA updates it gives me before I start messing around with it but have a slight problem.
The phone came installed with 4.4.2 and did an over the air update to 4.4.4 it now wants to upgrade to 5.0.1 however whenever I download the update which is 479.5MB it downloads it and tries to 'verify' install and then I get a 'verification failed' every time and it doesn't install, anyone know what's going on? (may I add I have literally not touched the phone it's come straight from Google, the only thing I've done is logged into my Google account and updated whatever stock apps needed updating in the play store)
AdamF77 said:
Okay so I've just received a refurbished Nexus 5 from Google as my old one had a hardware power button fail. Anyway I've decided this time round I'm not going to root and wanted the phone completely stock so thought I would do all the OTA updates it gives me before I start messing around with it but have a slight problem.
The phone came installed with 4.4.2 and did an over the air update to 4.4.4 it now wants to upgrade to 5.0.1 however whenever I download the update which is 479.5MB it downloads it and tries to 'verify' install and then I get a 'verification failed' every time and it doesn't install, anyone know what's going on? (may I add I have literally not touched the phone it's come straight from Google, the only thing I've done is logged into my Google account and updated whatever stock apps needed updating in the play store)
Click to expand...
Click to collapse
Looks like you have a bad download of the ota. By formating the cache partition you delete the downloaded ota and they you can try to download again.
AdamF77 said:
Okay so I've just received a refurbished Nexus 5 from Google as my old one had a hardware power button fail. Anyway I've decided this time round I'm not going to root and wanted the phone completely stock so thought I would do all the OTA updates it gives me before I start messing around with it but have a slight problem.
The phone came installed with 4.4.2 and did an over the air update to 4.4.4 it now wants to upgrade to 5.0.1 however whenever I download the update which is 479.5MB it downloads it and tries to 'verify' install and then I get a 'verification failed' every time and it doesn't install, anyone know what's going on? (may I add I have literally not touched the phone it's come straight from Google, the only thing I've done is logged into my Google account and updated whatever stock apps needed updating in the play store)
Click to expand...
Click to collapse
Hi Adam,
I have the same problem. Did you solve it?
Just fastboot the new system img
Sent from my Nexus 5 using Tapatalk
Hello,
I have a Nexus 5 and installed Android 6.0 OTA and I rooted the phone. I recently got a notice for Android system update (2.5MB) and I have a problem with the update I suppose because of that root.
Update gets downloaded, the device restarts and then on the screen I get an error.
Does anyone know what the problem is and how to make the update?
Thanks!
Yes, I think a great number of people know the answer... I had to ask the same question myself a long time ago.
Since Android 5 (I think) the OTA process looks at the entire system for any changes to the ROM partitions, and it will update only if the ROM is intact and unchanged. Root changes the ROM, therefore no update.
I believe that you can update manually by flashing just the system partition, but you'll then have to re-root the phone.
It was precisely for this reason that I got fed up with root, despite its many advantages, and now run encrypted, unrooted, and with Netguard firewall protecting at least some of my privacy.
NoOne12 said:
Hello,
I have a Nexus 5 and installed Android 6.0 OTA and I rooted the phone. I recently got a notice for Android system update (2.5MB) and I have a problem with the update I suppose because of that root.
Update gets downloaded, the device restarts and then on the screen I get an error.
Does anyone know what the problem is and how to make the update?
Thanks!
Click to expand...
Click to collapse
u should update before making any changes in the system folder or to the recovery.
You should not take the OTA updates while rooted.
One solution would be to download the factory image for the update and fastboot flash system.img from the download, wipe cache, then reinstall supersu.
Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*
KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.
If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!
I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.
That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.
If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.
Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1
No idea why this posted twice.
Thanks!
The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.
39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...
Hello everyone!
I just download the last update via update in the phone and normally it boots me into TWRP then I search install it and thats it. The thing is that this last update unfortunately when the logo is installing in the middle throw me an error E1001 Error 1 and semi brick my phone, when I choose restart it literally throws me back to Fastboot.
Did anyone encounter the same fate? Or maybe my update file got corrupted?
Any ideas how can I fix this and have the last update installed for this ROM?
Thank you!
SebixWolf said:
Hello everyone!
I just download the last update via update in the phone and normally it boots me into TWRP then I search install it and thats it. The thing is that this last update unfortunately when the logo is installing in the middle throw me an error E1001 Error 1 and semi brick my phone, when I choose restart it literally throws me back to Fastboot.
Did anyone encounter the same fate? Or maybe my update file got corrupted?
Any ideas how can I fix this and have the last update installed for this ROM?
Thank you!
Click to expand...
Click to collapse
Try August 1st update. Dev quickly fixed it probably after 31st July build.
Where can I download that? on the webpage the last build with GAPPS is the 31st
Thanks for the reply
I just redownload the update for the 31st with GAPPS and now booted like a charm.
I believe my OTA Updater file got corrupted or something like that.
SebixWolf said:
I just redownload the update for the 31st with GAPPS and now booted like a charm.
I believe my OTA Updater file got corrupted or something like that.
Click to expand...
Click to collapse
Nice to hear that. Sometime, updating directly from phone turn out disaster (4 from 5 in my case). Thus I prefer to download the build in the PC then do the update manually. Please note that it may caused by my network stability also.