[Q] Custom ROM - 'We want ICS' OTA? - HTC Incredible S

There was a system update yesterday but I didnt know whether to flash it. It was a mere 5.36 MB so I decided to flash it anyway. The phone rebooted and took me straight to the android exclamation screen and stayed there for a while. I had to hard reset my phone in order to get it up. No problem since then but when I checked for software updates again in settings it shows me that an install is pending. Do I install it again. Anyone else faced a similar issue? Also how did I get this OTA. Obviously I am on a custom ROM and it clearly shows OTAs disabled in the final update as shown in the link below
http://forum.xda-developers.com/showthread.php?t=1686583

OTA is not disabled in the v3 rom, I also I have received the update, is an official update one S which is the basis of the nik ROM when flashing the update that damages everything so you do not have to do

Related

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)

ICS 4.04 OTA update - random reboots

Wife's Note informed her of an OS update today which is the first update since the initial OTA push of ICS. The original GB ROM rebooted randomly, the first OTA version of ICS was stable with no reboots. Since the update to 4.04 (60MB download) she's having reboots again. Three times today already. Anybody else having this problem, or in fact is it a recognised issue?
Prostheta said:
Wife's Note informed her of an OS update today which is the first update since the initial OTA push of ICS. The original GB ROM rebooted randomly, the first OTA version of ICS was stable with no reboots. Since the update to 4.04 (60MB download) she's having reboots again. Three times today already. Anybody else having this problem, or in fact is it a recognised issue?
Click to expand...
Click to collapse
I think you have to use pc odin to reflash the official stock rom. DONT WIPE AND FACTORY RESET ON ICS.

[Q] Persistent Android L OTA Upgrade Notification

I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
A week passed and no response. Bump. Nobody has any idea how to get rid of this thing??
Koolstr said:
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
Click to expand...
Click to collapse
Is updating your custom rom to 5.1+ an option? Already many custom roms were updated to 5.1 even 5.1.1.
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Koolstr said:
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Click to expand...
Click to collapse
Don't even know what rom it is so its hard to answer. If you prefer a stable rom they yes, you should wait a little more.
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Click to expand...
Click to collapse
You should ask this one in your rom thread, sometime when the update is considered a major update, its recommend to do a full wipe, in some cases you are fine just updating without wiping. You could do a nandroid backup using your custom recovery (save it on your computer, not just on the phone) try to update without wiping. If its working fine, there is no problem, if not you can wipe your phone and restore your backup.
To disable the notification, I would try to go in settings --> apps --> all, search for the updater service, clear cache of that service and then disable it. Then find where the ota file is stored on your phone and delete it. Not sure if it will work, never tried myselef
Is there a way to do a nandroid backup directly to pc? Because I don't have room on my phone, and TWRP Manager only lets internal backups take place.
For some reason I can't search the apps in my ROM. The notification says it is from Google Play Services but I suspect that is simply routed requests from the actual updater service. Do you know what the name of the service is, so I can find it? I have a crazy number of apps and can't find it.
Hi Koolstr,
I know this thread is old, but wanted to let you know I am on an unlocked and rooted HTC One (m7) S-On. I am using TWRP and can backup to external storage using a Micro USB Powered Micro USB Host OTG cable, which I purchased from Amazon.
I am running:
Android version: 5.1
Rom: Google-Plus-Edition-LP_m7_v3.2_072915
Kernel: 3.4.10-NuK3rn3l-Lollipop_v8.00
I am getting a similar Android System Update: Android L upgrade for user/release-keys. I cannot get it to go away. I made a complete nandroid backup and then proceeded applying the update. It will reboot the phone into TWRP recovery and do nothing. The update goes away for a few days and then it comes back. I have tried to look for a way to disable the update, but I am at a stand still. If anyone knows that would be great.
Best,
manderson706
It's something that santod did. I believe there's a post in his topic with the fix. Or just flash the updated GPE from santod

pblem with restart's and stuck device

hi
all, i have nexus 6 device with 6.0 MRA58R and open bootloader and it was update by the device from google,still before that i try to do root and didn't succeedwith 5.1, so i go back to 5.1 and it was update as i said but the device is stuck by the start or just by regular use...something is wrong and i don't know what, there is also sound when it stuck like A screech sound and it stuck
what to do next?
thanks
If your bootloader is unlocked, as mentioned in your other thread, download a stock image from Google and flash its components (except userdata.img) using ADB. As a result of your tinkering, something got messed up on the device, and flashing the stock image should resolve that.
tried these ...didn't help,it stuckes even after good flash with adb cause with OTA it stucks at the middle
You flashed MMB29Q from the shamu section of the page here? That is the absolute latest factory image available. There should be NO OTA update available.
first of all i tried to download the OTA cause i was with root and did unroot and i want to saw thet it get's the OTA's correct ,then i installed the version as you write, but still when i start the wifi or in regular use the device can be stuck and restart.
any idea to solve it? even in safe mode it stucks
No, not really. Like you mention in your other thread, it appears to be a hardware problem.
For the record, downloading the OTA updates is a waste of time when the latest factory image is available. When you get your replacement device, assuming it's not already on 6.0.1, install the image from the link I gave you, as it already includes in the image all the updates Google has released for Android 6.0.1.

February Update Install failed

Hello, i had Dec 5 OTA + Magisk rooted device.
i tried to update but it said failed. so i uninstalled magisk and restored to stock boot.img but still saying update failed.
someone said to relock bootloader. i tried to relock bootloader and my data got erased.
even after that i tried to update OTA and im still getting failed update.
i dont know what to do now. can anyone please help me.
i have the same problem
help us please
after doing a bit of searching i fixed it.
i simply flashed my device with Stock Rom 10.0.0.2 using Mi Flash Tool. (there are plenty of youtube tutorials).
after that my device installed the OTA updaet without any error.
after that i rooted my device with Magisk. [patched_boot is already been posted on this forum]
so far, haven't come across any problem. Just not satisfied with the volume update. i had a magisk module for low volume fix which worked better.
What's really needed is full images from Xiaomi, so we can start flashing them manually without worrying about OTAs
See how well the DAISY thread is being maintained https://forum.xda-developers.com/mi-a2-lite/how-to/ota-v9-6-4-0-odlmiff-t3823913
.
Another repost with the same issue.
Follow this and this
I have flashed the V10.0.13.0.PDLMIXM (and locked back oem) but I still have the google update problem... from June to September 2019 :/... any idea?

Categories

Resources