Hi,
I'm rooted and have CWM Recovery installed running android revolution 1.3.3. GSM and still getting that stupid notification to do the system update to 4.0.2
I'm waiting for android revolution to update when it's on 4.0.3 but in the meantime, this notification is bothering me.
I'm just wondering if these instructions can apply for our phones to make it go away. http://forum.xda-developers.com/showthread.php?t=1388778 I have a nandroid backup and everything for a just in case situation.
Related
my GNex is of the Takju Build.
I'm on Stock Rom.
I've not rooted the phone.
This is kind of weird, I've not heard about this problem with anyone before.
I received the Android 4.2 update a few days ago, It downloaded, and I clicked Install & Restart.
Everything was normal, the Green Bot appeared, showing that the update was installing. After it completed, a Bot appeared with a Red
exclamation.
And when the phone booted, I was still running 4.1.2.
Now, its been days, I have not received the OTA update again.
I beleive all of the Takju builds would have received the update by now.
Need Help please!
Hey folks,
I rooted my GS3 right after I got it and everything has been functioning fine. I actually like the stock ROM so I have stuck with it and just removed the bloat. Recently an OTA update was released and I followed an article on putting my updater back to stock to receive the OTA update. I tried updating but it was unable to complete. Now when I go into software updates there is an option that says "continue update" that is grayed out. Is there a workaround to this or do I need to flash back to stock, receive the new update and reroot? If that's the case a link to a walk through would be appreciated. Thanks
anyone?
I was able to get to 4.1 successfully with kies this morning
So I had my phone rooted sometime around the point when the 4.1.2 OTA came out. I went back to stock recovery and a nandroid backup that I made before rooting. Now, about once a week, I get the notification that the update is available but it doesn't work. My phone reboots like its going to update, I get the android guy with the spinning graphic thing, then it reboots the same as it was before.
I tried searching but couldn't find a solution...if my searching skills suck just let me know
THANKS!
Came home from work today and found a notification for a small (8.0 MB) system update. I already updated to 4.3 JSS15Q when I first turned on the device. I am currently rooted with stock 4.3 JSS15Q via the Wugfresh toolkit. If I install this system update will I lose root? Will anything wonky happen? Not having the update doesn't bother me but the constant notification that I can't dismiss does. I know a custom ROM will fix that and I do plan on flashing something soon but not quite yet.
I'll attach a screenshot of the update screen. Any and all feedback is appreciated. Thanks!
http://forum.xda-developers.com/showthread.php?t=2404833
I purchased a second hand One M8 which had CyanogenMod installed on it. My aim was to revert it to stock (either on O2 UK or standard HTC ROM) with the abillity to get OTA updates.
I checked the CID (O2__001) and got a stock recovery image and nandroid backup for it. I then used fastboot to flash TWRP as the recovery image, and used that to restore the nandroid backup. That worked fine and it was working with the O2 ROM, so I flashed the stock recovery image as well.
After this it prompted for an OTA update so I thought all was going well. I installed the update and that all worked as expected until it booted up. All the functionality is there, but the Wifi won't turn on at all. If I tap the option to turn it on, it just hangs in the "off" position. It's the same whether I do it through the settings menu or from notification bar. I tried doing a factory reset but it makes no difference. It's very frustrating because other than this, everything is working the way I would like to.
What could cause the Wifi to stop working after an OTA update?
Why ? Low version backup for high version hboot.
You need correct backup for your hboot version.
What's hboot no. ?
Never mind, I managed to sort it out.
The first few OTA updates had a Wifi firmware update which stopped it working. I used mobile data to continue updating and once it got to Android 4.4.4 it all worked as it should.