System update notification problem - Xperia Z5 Q&A, Help & Troubleshooting

Hello guys,
Last days my phone has not been playing very nicely with me.
I did a complete wipe (using flashtool and wiped everything).
Then I reflashed latest 32.3.A.2.33 firmware and custom kernel (sunkernel 376_Aigoo_1_6_7) as can be seen on my screenshot.
So right now I am on .33 firmware and everything is fine, except that I keep still getting a notification that a system update is available (which is the same .33 update).
So I downloaded it and tried to install it, but it fails and then again I keep getting notified with this update... while im already on the latest firmware.
Any idea's how I can fix it?
- I've already tried reflashing firmware again 2 times.
- I tried unrooting and installing the update but again it failed.
Sony Xperia Z5 Nougat 32.3.A.2.33 + sunkernel 376_Aigoo_1_6_7
Any suggestions would be appreciated, well accept for flash firmware again, as im tired of that at the moment
Thanks :good:

Delete with Root Explorer the Sony Software Update App in system.
Make first a backup with TT Backup.
Reboot.
Thats what I always do.

Related

no update found

Ok, i know its been posted before but i couldnt find anything relevant in search (maybe im searching for the wrong thing?)
I know im not the only person with the "There is no update for your device" problem. I had an update available but like an idiot i forgot to unfreeze some apps and it failed. Now its not showing the update again.
Tried wiping the device, no luck
Tried manually updating to ..26 (was on .26) which would restore all frozen apps, then OTA to JB, no luck
Tried manually updating to .30 to see if it would OTA to JB from there, no luck
Tried downgrading to .26 and use the dlpkgfile method to upgrade to 30 from 26 and OTA from there to JB, still no luck.
Tried rebooting power + volume up and clearing cache, still no updates available.
Am i missing something? Most of the methods that people have said work are not working for me... What do i do next? How do i OTA to JB and maintain root?
Bootloader is still locked. I have root. Im currently on .30 but can downgrade if needed it only takes a few minutes.
Halp?

[Q] OTA Update on rooted GT-I9105P

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

New firmware update from Sony Today

Hello
I received a new update from Sony today of 18.1MB.
I'm unable to install it due to being on custom kernel/root.
I am just curious if anyone else received it ?
The version number is same as my previous version 15.3A.0.26!
Attachments are for your reference.
UPDATE : I got my exam tomorrow so I will leave it here. I flashed new STOCK ROM and it showed update again via Sony PC companion and Update Centre. However, I am unable to carry forward with this update. I end up receiving an error via PC companion / Update Centre. I have now even formatted my internal memory but still its not helping. I will try to update you by Friday evening after my exam!
Also I have started to notice bugs/ crashes after I reflashed my STOCK rom. I think I will flash again with dump files to see it that helps (I skipped extra data this time in Flashtool)
I clearly understand the new update is 15.3.A.0.27 but I am still trying to figure out why I got this 18MB update which I am not able to flash. I will try to make an FTF file from SONY PC COMPANION UPDATE DUMP that I downloaded. IF that clears it out or brings any improvement, I will certainly update you all!
Update 2 :
Well, I tried reflashing my old FTF (4.2.2) and I still get the same update on PC companion and update centre. However, I can not flash it successfully. I tried everything that I could think to make this work, but I couldnot. Therefore, i think this is some kind of a bug which is showing the update.
Update screen shot
I dont have it... I'm from Philippines... How about you?
Its the same firmware update lol
amnher said:
I dont have it... I'm from Philippines... How about you?
Click to expand...
Click to collapse
aniketroxx said:
Its the same firmware update lol
Click to expand...
Click to collapse
UK sim free C2105
I received the update last time on the day it was launched !
Hnk1 said:
UK sim free C2105
I received the update last time on the day it was launched !
Click to expand...
Click to collapse
what custom kernel are you using?
amnher said:
what custom kernel are you using?
Click to expand...
Click to collapse
I was using STOCK kernel with few mods that I made myself. However, I have reverted back to STOCK and now I am updating my firmware via Sony PC companion! PC companion showed me an update as well !
I think it is bugs fixing update without any firmware number change (or maybe there is )! I will write back to you when I have successfully updated!
Hnk1 said:
I was using STOCK kernel with few mods that I made myself. However, I have reverted back to STOCK and now I am updating my firmware via Sony PC companion! PC companion showed me an update as well !
I think it is bugs fixing update without any firmware number change (or maybe there is )! I will write back to you when I have successfully updated!
Click to expand...
Click to collapse
BUT The new Firmware is. . 27 and even certified by Sony
No update here in India too..
I updated my phone. There are still Screen flickering and moving from phone to sd card bugs. The only changed thing I have seen is play store update.
And also, new update came for album and movies.
Sent from my C2105 using xda app-developers app
saurabh007 said:
No update here in India too..
Click to expand...
Click to collapse
How about the camera?
Sent from my C2105 using xda app-developers app
This isn't update
Hnk1 said:
Hello
I received a new update from Sony today of 18.1MB.
I'm unable to install it due to being on custom kernel/root.
I am just curious if anyone else received it ?
The version number is same as my previous version 15.3A.0.26!
Attachments are for your reference.
UPDATE : I got my exam tomorrow so I will leave it here. I flashed new STOCK ROM and it showed update again via Sony PC companion and Update Centre. However, I am unable to carry forward with this update. I end up receiving an error via PC companion / Update Centre. I have now even formatted my internal memory but still its not helping. I will try to update you by Friday evening after my exam!
Also I have started to notice bugs/ crashes after I reflashed my STOCK rom. I think I will flash again with dump files to see it that helps (I skipped extra data this time in Flashtool)
I clearly understand the new update is 15.3.A.0.27 but I am still trying to figure out why I got this 18MB update which I am not able to flash. I will try to make an FTF file from SONY PC COMPANION UPDATE DUMP that I downloaded. IF that clears it out or brings any improvement, I will certainly update you all!
Click to expand...
Click to collapse
This is just a bug when you use custom kernel's happened to me when i reverted back to my kernel and it started to push updates i tried to update but it failed.
Conclusion revert to stock kernel or any other latest kernel or ignore the update
but I did not get the update, whether it's renewing the kernel?
Navneet Suresh said:
This is just a bug when you use custom kernel's happened to me when i reverted back to my kernel and it started to push updates i tried to update but it failed.
Conclusion revert to stock kernel or any other latest kernel or ignore the update
Click to expand...
Click to collapse
I am getting this update regardless of kernel and flashing FTF. Every time I flash a new FTF file (FTF made by me from my own phone with UK firmware), I always get the update again. However, it always fails with an error.
I think this is a bug as well. It's annoying to see an update on your phone and you have to force close update centre every time!
Hi,
I just got an update to 4.2.2 in Belguim, completely stock apart from being rooted, which apparently i have to redo, since all my root apps have been refused...
edit-camera,album,movies and walkman apps pdated too.
OMG!!!
http://talk.sonymobile.com/t5/Xperia-L/New-firmware-15-3-A-0-27-coming-soon/td-p/467271/page/5
OK??
I got this update weeks ago here in the US. Only firmware updates for Album and Walkman apps.
Sent from my C2104 using xda app-developers app

[Q] OTA update from xpeia sl

I have xperia SL version 4.0.4. Actually, it used to be 4.1.2 but I flashed it to MIUI then I flashed it back to firmware 4.0.4 (becasue of some problems found while using MIUI) because I could not find the firmware 4.1.2. Luckily, I got OAT update of version 4.1.2 LT26ii_6.2.B.0.200. When I completed download the update, and press install update, my phone turned off and then it turned on again with the message: could not install update. I tried download that again but the same thing happened. I tried to use Sony pc companion to update through computer. Yes, it has found the latest update for it 4.1.2 LT26ii_6.2.B.1.96. But I dont know why? while I am downloading the update, it never completes. when it is nearly 100 percent then it started to download again with like 0 percentage. I also tried that twice, the same thing happened, Why?
Btw, I am new to the website and I know very little about android. thank in advance!

Having real trouble updating to Lollipop (recovery help?)

Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Try putting twrp back on and flashing stock Lollipop Rom. http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 You can also try aosp, cm12.1 or any other lollipop ROM.
The Lollipop OTA is very picky, I believe any modifications to the stock firmware will cause the update to fail. You will need to have a completely stock system for the OTA to install successfully. Find the correct KitKat firmware for your phone and flash it then try upgrading.
Hi.
I'm having a similar problem with te OTA being picky (topic here).
Is there a stock firmware "file map" so that we can check manually what is wrong and erase/add needed files ?
Maybe this could be done by checking a flashable stock rom ?
Thanks a lot guys.
EDIT : Found a solution here http://forum.xda-developers.com/mot...osing-apps-t2979971/post57658072#post57658072.
Worked perfectly !
OP, I am in the same situation. I did the same as you, and got the same results. Have you managed to solve it? It would be nice if you tell what you decide to do and what's the outcome. Thanks!
tomisalunatic said:
Alright so I have a 2013 Moto G, and basically in the past while on KitKat I've rooted my phone, given it custom recovery (TWRP), and messed around with the ROM (changed it to CM, PA and a few others and back). Now I've come to update to Lollipop and of course I need stock recovery to update my phone via OTA, and when it first prompted me to update, I had TWRP and I didn't really think, I just updated, this sent my phone into a bootloop, rebooting straight into TWRP every time I turned my phone on. Luckily I had a backup and I just restored to that and that fixed it. Recently I've been trying to fix the correct stock recovery for my phone so I can update, and I found some MotoTool AIO thing, and that changed my recovery back to KitKat stock (or so it says), now when I go into recovery it LOOKS like stock, can do everything you could normally do with stock recovery, but when I came to update it, about a quarter of the way though the update process, it errors and reboots my phone. Luckily this time my phone recognizes it has errored and just cancels the update instead of sending me into a boorloop. Any help would be greatly appreciated.
Thank you,
Tom.
Click to expand...
Click to collapse
Update to 5.1 success..... erm, well it's all relative
Eventually managed to update my XT1039 to 5.1 via ota.
Started with a fully charged phone and flashed 4.4.4 stock firmware (http://forum.xda-developers.com/moto-g/4g-development/xt1039-moto-g-4g-stock-firmware-kxb21-t2805619).
Once completed, powered up phone and signed into google play then updated the motorola update services app.
DO NOT install a custom recovery or root yet or the update will fail!
Start the update by going into settings/about phone/system updates.
After first boot into 5.1, do a factory reset.
To root once the upgrade is completed, download cf autoroot (http://forum.xda-developers.com/moto-g/4g-development/root-xt1039-cf-auto-root-peregrine-t2942406) and unzip to a folder on your pc. Open a command prompt and change directory to this folder. Powerup handset in bootloader mode (hold vol down while switching on), connect USB and run 'root-windows.bat' from the command prompt.
So far I'm hugely disappointed in the update as I use WiFi tethering alot and it appears to be a massive fail. I know it wasn't 100% in 4.4.4 or CM12 5.1 with both reqiuring an occasional reboot, but in 5.1, something's just not right and it's basically unusable (could it be updated radio or something?). Fortunately, USB tethering appears flawless.
Another obsrvation seems to be abscence of a + appearing in the HSPA signal indicator, I seem to be getting just the H appearing regardless.
Also no more bluetooth visibilty timeout setting.
After installing CWM 6.0.5.0, I got gliches with the display in recovery mode but it works.
Now after I have it rooted, ad free and de-bloated, fixed the power on logo and installed CWM 6.0.5.0, I'll stick with it for a while to just to see how the battery lasts.
In hindsight I should've stuck with CM12 5.1.

Categories

Resources