I just got the VZW 7.7 update but it was only 29.3 mb, but it was not ICS. Did anyone else get the 29mb update today? :cyclops:
After it downloaded the update and rebooted I got the Android with gear logo then an Android with an exclamation mark in the middle. It then rebooted and came back up. It's no longer offering me the update so I don't know if it was applied correctly or not. The Android with an exclamation mark looked like something I would get if the update had failed. Not sure what it is?
gshaw1967 said:
After it downloaded the update and rebooted I got the Android with gear logo then an Android with an exclamation mark in the middle. It then rebooted and came back up. It's no longer offering me the update so I don't know if it was applied correctly or not. The Android with an exclamation mark looked like something I would get if the update had failed. Not sure what it is?
Click to expand...
Click to collapse
I had the same happen as well as other people on the Verizon forum. 29.3MB update and an android with exclamation mark after install. No changes in the About device screen.
thanks just a little excited!
Try rebooting into the boot loader. Power + down volume. It will boot to Odin and start the real download.
Sent from my Nexus 7 using Tapatalk 2
The update we are looking for is LP10 (ICS 4.0.4).
Received the ics update last night after the 29.3mb update. I had to clear Google Services to get it. Clear the cache, force quit then check for the update again under settings, about device, software updates.
dailong said:
Received the ics update last night after the 29.3mb update. I had to clear Google Services to get it. Clear the cache, force quit then check for the update again under settings, about device, software updates.
Click to expand...
Click to collapse
Just tried this...no luck. I see the last check date change to 1969, but a recheck just says no updates available.
Did the FH01 29-meg "pre-update" work on yours (without an exclamation mark and actually showing FH01 in About prior to ICS)?
Rodney
rhester72 said:
Just tried this...no luck. I see the last check date change to 1969, but a recheck just says no updates available.
Did the FH01 29-meg "pre-update" work on yours (without an exclamation mark and actually showing FH01 in About prior to ICS)?
Rodney
Click to expand...
Click to collapse
Yes the 29.3 update worked with no exclamation mark. I was stock. Initially I forced quit google services, cleared the cache and restarted the device. That didn't work so I cleared the google services cache first, forced quit then checked for updates. Hit the check now button couple of times and it showed up.
dailong said:
Yes the 29.3 update worked with no exclamation mark. I was stock. Initially I forced quit google services, cleared the cache and restarted the device. That didn't work so I cleared the google services cache first, forced quit then checked for updates. Hit the check now button couple of times and it showed up.
Click to expand...
Click to collapse
I tried Clear Data first, then Force Stop on Google Services, but always get the exclamation mark while trying to apply the 29.3MB update. I guess this is stopping the ICS update from coming through. Anyone have any ideas on how to get around this? I was rooted, but I used the Gingerbreak method to unroot and it seemed to work just fine. I am also on the stock recovery.
Has anyone been able to do it if they had installed CWM Recovery? I got an error that it wasn't signed properly and it asked if I wanted to install anyway, so I did and it failed there too.
---------- Post added at 02:21 PM ---------- Previous post was at 01:44 PM ----------
Do you have to be back to stock recovery for this update to work?
This has turned into a very special event. I've talked to Verizon support a couple times (meaning on hold for hours) and this is what seems to be happening.
There is a problem with the update coming from Samsung. I found a forum entry on Verizon reporting the very same problem with the GT 10.1 update a few months ago. Bottom line this isn't the first time this problem has been seen and it's up to Samsung to fix it.
That said as of a couple hours ago Verizon has no record of the problem. I take it most people in this forum don't report errors to Verizon. It has now been reported and is being escalated. If you have a chance to report the problem to Verizon or Samsung it might help speed up the fix.
During my customer support outing Verizon has been very nice but total useless. They routed me to Samsung level 1 who told me no update was taking place and they contacted Samsung level 2 support for me which hung up the phone on me and on the Verizon rep. It was interesting.
I guess it's time to take a break and let it shake out.
dailong said:
Received the ics update last night after the 29.3mb update. I had to clear Google Services to get it. Clear the cache, force quit then check for the update again under settings, about device, software updates.
Click to expand...
Click to collapse
If you have the LP10 update can you post it for everyone else? or is it now gone from your cache folder? What about a Nandroid or have you already started to tinker in the ROM?
Here is the youtube video of ICS on the Verizon Galaxy Tab 7.7
http://www.youtube.com/watch?v=dg9egFXi9FA&feature=plcp
so your update was for FH01 to LP10?
We need to make a thread organizing all this information with updating issues and figure out what people who got the update to work have in common.
Also, someone with the update please post the file from your cache or make a "as stock as possible" nandroid and post that.
"This video does not exist"
fixed
dailong said:
fixed
Click to expand...
Click to collapse
This is getting ridiculous. I also called Verizon, of course tech support is clueless. They didn't even know about any update for our tab since May 2012. Their answer was to Wipe Data/Factory Reset, then try the update..... of course, didn't work. Unrooted, stock recovery... Couldn't be more stock than I am right now. Update will not install. What gives?
Anyone have ANY suggestions on how to kick this thing off? Starting to think I should have stuck with my OG galaxy tab..... Which has Jelly Bean running on it by the way....
dailong said:
Here is the youtube video of ICS on the Verizon Galaxy Tab 7.7
http://www.youtube.com/watch?v=dg9egFXi9FA&feature=plcp
Click to expand...
Click to collapse
Very interesting news. Do you have it rooted yet? Is there any way to root the sucker? Because then it's super easy to grab the rom and make it available for everyone here!
Related
Hi there XDA people.
Normally content to lurk I thought I'd share how I fixed my upgrade issues and updated to the ww version of Jelly Bean ASUS sent out this morning.
I checked for a firmware update first thing this morning (as I've been obsessively doing regularly since the US update was released on the 22nd). To my joy I got that cheeky green arrow in the notifications window so left it to do it's thing. Had a shower, triggered it to update and went to get dressed. Whilst I was out of the room the upgrade failed and the tablet rebooted. My daughter was in the room so I have no idea what happened, my stupid fault for leaving it in the room with her, stupid me.
Long story short, I could no longer find the update via the firmware checker in settings. I tried a number of combinations of cold restarts and stopping various apps along with wiping their cache/data. These usually brought up the check for updates button but none would allow me to redownload the update. Sometimes I got a message saying "update available - check notifications", other times it didn't pick up the update and occasionally I just got a greyed out button. I'm sure this is ringing bells for some of you.
I reasoned that it had downloaded but for some reason something was stopping me download the update again. So using TotalCommander I searched around root directories for the "dlpkgfile" mentioned here - http://forum.xda-developers.com/showthread.php?p=30516010 . Found it (I think in the Cache folder of "File System Root", but this has all changed since the upgrade) and renamed the dlpkgfile to dlpkgfile.bak.
I then temp unrooted with voodoo, cold booted for good luck and then checked for firmware updates. Lo and behold it kicked in straight away, downloaded and updated without a hitch.
Hope this helps some of the folk who have had similar issues getting the firmware update to kick in again after initial issues.
Sent from my ASUS Transformer Pad TF300T using xda premium
gurningchimp said:
Hi there XDA people.
Normally content to lurk I thought I'd share how I fixed my upgrade issues and updated to the ww version of Jelly Bean ASUS sent out this morning.
I checked for a firmware update first thing this morning (as I've been obsessively doing regularly since the US update was released on the 22nd). To my joy I got that cheeky green arrow in the notifications window so left it to do it's thing. Had a shower, triggered it to update and went to get dressed. Whilst I was out of the room the upgrade failed and the tablet rebooted. My daughter was in the room so I have no idea what happened, my stupid fault for leaving it in the room with her, stupid me.
Long story short, I could no longer find the update via the firmware checker in settings. I tried a number of combinations of cold restarts and stopping various apps along with wiping their cache/data. These usually brought up the check for updates button but none would allow me to redownload the update. Sometimes I got a message saying "update available - check notifications", other times it didn't pick up the update and occasionally I just got a greyed out button. I'm sure this is ringing bells for some of you.
I reasoned that it had downloaded but for some reason something was stopping me download the update again. So using TotalCommander I searched around root directories for the "dlpkgfile" mentioned here - http://forum.xda-developers.com/showthread.php?p=30516010 . Found it (I think in the Cache folder of "File System Root", but this has all changed since the upgrade) and renamed the dlpkgfile to dlpkgfile.bak.
I then temp unrooted with voodoo, cold booted for good luck and then checked for firmware updates. Lo and behold it kicked in straight away, downloaded and updated without a hitch.
Hope this helps some of the folk who have had similar issues getting the firmware update to kick in again after initial issues.
Sent from my ASUS Transformer Pad TF300T using xda premium
Click to expand...
Click to collapse
I have the same problem but i can't find the dlpkgfile file. Searched with root explorer in the cache folder and rest of system root but nothing... Also tried temp. unroot with cold boot... :crying:
thanks, the whole morning and afternoon this was driving me crazy... but now its dl again :good:
Finally got it running.
- cleared cache and data of cmclient with titanium backup.
- cleared cache and data of dmclient with titanium backup.
- Temp. unroot in Voodoo (without this update check failed).
- update button available again, hit it and voila a green download arrow.
Update worked fine for me. I Just wiped my data as well
Sent from my R800i using xda app-developers app
bazzio said:
Finally got it running.
- cleared cache and data of cmclient with titanium backup.
- cleared cache and data of dmclient with titanium backup.
- Temp. unroot in Voodoo (without this update check failed).
- update button available again, hit it and voila a green download arrow.
Click to expand...
Click to collapse
I followed these instructions as I couldnt find the dlpkgfile either, unrooted with voodoo, cleared cache on the cm and dm client, it started downloading again, but to my disappointment it failed again during the restart. Had the logo of android on its back with a red triangle. I had to hold in power button to reboot.
What could be causing the update to fail? I havent disabled any system applications or messed with the build.prop file! :crying:
What I did was is this:
-Go to the the Apps section under settings
-Pick the "All" tab
-Then search for CMClient and DMClient and clear both data and cache of both of them
-Check for an update and Viola, green arrow shows up
I'm not sure if it works with root since mine is still unrooted so I don't have titanium backup installed yet.
Ulric099 said:
What I did was is this:
-Go to the the Apps section under settings
-Pick the "All" tab
-Then search for CMClient and DMClient and clear both data and cache of both of them
-Check for an update and Viola, green arrow shows up
I'm not sure if it works with root since mine is still unrooted so I don't have titanium backup installed yet.
Click to expand...
Click to collapse
Tried this, and it let me download and install the update again, but it failed again
mcall_r said:
I followed these instructions as I couldnt find the dlpkgfile either, unrooted with voodoo, cleared cache on the cm and dm client, it started downloading again, but to my disappointment it failed again during the restart. Had the logo of android on its back with a red triangle. I had to hold in power button to reboot.
What could be causing the update to fail? I havent disabled any system applications or messed with the build.prop file! :crying:
Click to expand...
Click to collapse
Im in the same boat as you, I did the same steps but it fails with the red triangle... I even did a factory reset and still doesnt update, could it be becuase of the root?
Have tried everything (dm delete, cm delete, temp unroot, atp tweak uninstall, cold boot, regular boot, etc) after the download failed at 99% and still either can't find or get immediate download failed. No JB love here
Sent from my SGH-I747M using XDA Premium HD app
Could anyone upload EmailWidket.apk from the WW version?
Found one but it says the check sum is not correct when trying to update...
During my update I also got the red triangle, so after a bit of investigation /cache/recovery/last_log pointed me to checksum error of Keyboard.apk. Restored it, fixed CM and DMClient but now it just says no update found. Any other suggestions?
Purchased an open box Galaxy Tab 10.1 today for $238. Brought it home and instantly ran into trouble once the Market updated. Google Play locks up every time now. Cleared Market cache and no go. Google Play still locks up.
I see that ICS should be pushed out. OTA updates don't seem to be hitting my tab yet. I've tried several times.Opened Kies and sure enough it can't find my firmware version. Go figure. My next attempt was download mode and try to do a firmware upgrade via Kies. It gets to the part where it is downloading the firmware and ready for the install and then I get a pop up box in a different language. Needless to say I see nothing else and I guess it fails. Some luck.
Does anyone know of an ODIN with a STOCK ICS ROM that is up to date or know of a way to fix my issue?
atechstl said:
Purchased an open box Galaxy Tab 10.1 today for $238. Brought it home and instantly ran into trouble once the Market updated. Google Play locks up every time now. Cleared Market cache and no go. Google Play still locks up.
I see that ICS should be pushed out. OTA updates don't seem to be hitting my tab yet. I've tried several times.Opened Kies and sure enough it can't find my firmware version. Go figure. My next attempt was download mode and try to do a firmware upgrade via Kies. It gets to the part where it is downloading the firmware and ready for the install and then I get a pop up box in a different language. Needless to say I see nothing else and I guess it fails. Some luck.
Does anyone know of an ODIN with a STOCK ICS ROM that is up to date or know of a way to fix my issue?
Click to expand...
Click to collapse
I believe this is stock ICS stock for your 7510: hxxp://stockroms.net/file/GalaxyTab10.1/ICS/P7510XXLPH_P7510XEULPH_XEU.zip
There might be something wrong with your device and that might explained the reduced price and the open box. You might want to consider installing the latest recovery version from droidbasement and reset your device. Here is an excellent guide: hx*ps://docs.google.com/document/d/1luCfYEjOIH9K4WR8KsCMMFjZ9pXnes7Az41qMgOkrv0/edit (there are many way to install clockworkmod recovery, but this tutorial will help if you brick the device)
Hoping someone can help. After stopping the Google Framework service and clearing data, my 7 will find and download the 4.2 update. When installing the update, at about 25% complete, the Android logo with the red triangle shows up and I have to do a reset to get it to reboot. The update is never found without stopping the framework service. This is a completely stock 7 if it helps.
If this has been answered before I apologize. I did search and didn't see the same issue out there.
Thanks.
blasiusj said:
Hoping someone can help. After stopping the Google Framework service and clearing data, my 7 will find and download the 4.2 update. When installing the update, at about 25% complete, the Android logo with the red triangle shows up and I have to do a reset to get it to reboot. The update is never found without stopping the framework service. This is a completely stock 7 if it helps.
If this has been answered before I apologize. I did search and didn't see the same issue out there.
Thanks.
Click to expand...
Click to collapse
I got the same problem (brand new 32gig N7 bought in Sweden)
I have the same problem as well. Hope someone has some help.
Same here too. ...
Skickat från min GT-I9300 via Tapatalk 2
You said you are completely stock, meaning you have never unlocked, rooted, installed a custom recovery, frozen apps, etc., correct? Unless you got a bad download it should install just fine. Did you get any sort of error message? That can help determine what failed. Be careful with stopping and clearing the framework settings. You will have to delete your Google account and sign back in to be able to use the Play Store again.
---------- Post added at 01:21 PM ---------- Previous post was at 01:13 PM ----------
Take a look at the 'Nexus 7 Update Problem' thread in this forum. You may just have to install a factory image for 4.1.2 or 4.2.
Groid said:
You said you are completely stock, meaning you have never unlocked, rooted, installed a custom recovery, frozen apps, etc., correct? Unless you got a bad download it should install just fine. Did you get any sort of error message? That can help determine what failed. Be careful with stopping and clearing the framework settings. You will have to delete your Google account and sign back in to be able to use the Play Store again.
---------- Post added at 01:21 PM ---------- Previous post was at 01:13 PM ----------
Take a look at the 'Nexus 7 Update Problem' thread in this forum. You may just have to install a factory image for 4.1.2 or 4.2.
Click to expand...
Click to collapse
The only thing I have done is put in my gmailaccount. Thats it. No error messages just the triangle.
I have deleted my google account and made several resets but with the same outcome.
I had a similar issue, before the update it does a comparison of certain system files and system apk's and if it fails it gives you the red exclamation mark.I ended up talking apart a 4.1.2 factory image and replacing various apk's but i had to install twrp in order to find out which ones were bad.
I wouldnt be to keen to update at this point,other than the multiuser function there really isnt anything of benefit in 4.2.
Same here.
I just got my Nexus 7 back from Asus (again...). Factory reset with 4.1.2. Signed in with my Google account, got the update notification, tried to update after it downloaded, N7 rebooted, started process, Android dead with red triangle. Completely reset to factory specs again, signed in with Google account, stopped all downloads and updates, tried update again, same thing.
I'm going to try one more time by not signing in after another factory reset (if I can...never tried it) and see if that does the trick, but I'm not hopeful.
EDIT: It didn't work. Only other thing I can think of is that I'm plugged into a PC (trickle-charge) and because you have to be plugged in to apply the update, MAYBE it's failing during the install due to lack of full power coming through the charge cable. No other reasons I can think of at this point. Anyone else trying to update while on trickle charge? If so, anyone try on full A/C power?
Are you in the US?
Wondering if it's because I am in a foreing country. :thumbdown:
From Guatemala
Sent from my Nexus 7 using xda app-developers app
I got notification out of the blue that the update was available. It failed again. I did a factory data reset hoping that would help. Tried the update again after installing NO apps. Failed again.
Any other suggestions?
I'm having the same issue. I wanted to keep my N7 stock and unrooted, but I may just have to root it and flash the update manually via recovery. It's kinda of a bummer.
Sent from my Galaxy Nexus using xda premium
I tried with a VPN and didn't work.
I'm still receiving the OTA update and every single time it fails.
Then I tried the recovery mode and didn't work.
I'm quitting on this.
Sent from my Nexus 7 using xda app-developers app
Groid said:
Take a look at the 'Nexus 7 Update Problem' thread in this forum. You may just have to install a factory image for 4.1.2 or 4.2.
Click to expand...
Click to collapse
Yes. I had the same issue (similar story to SWBailey), and the only way I could get the update was by flashing Google factory stock 4.2.1.
I have the same problem in Spain, I bougth the tablet (32G) last week. The attach image show you more information about the problem.
same issue, fastboot or root!
i have the same issue... a couple off guys recomended fastboot(doesnt need root as far as i get it)i... i think it might be do to having a 32gb but no 3g version, which i think is only available in countries other than usa... im from serbia for instance im probably gonna end up rooting it and flashing a custom rom
I called to the Asus support, and they sent me an email with the following instructions, I can´t finished all the steps because in the step number 5, the tablet never restarts, Something is wrong. I am going to send the tablet to the seller.
1. If the computer is on, please turn it off.
2. Press the power button volume button (-) and the volume button (+)
at the same time;
3. Press the volume button (-) twice to initiate the procedure "
Recovery "
4 Press power button to select.
5: After you restart the recovery mode hold the button
on and the volume button (+)
6. Use the volume keys to select the option to wipe data / factory reset "and press
the power button to select that option.
7 Scroll down to the Yes option. to clear the data and press the
on to select that option.
Same here...completely stock too! Tried 3 times... :/
If it doesn't work the fourth time, I will try to return it for a new one. Still in my 14 days..
I am on stock rooted MK2 with TWRP recovery installed. I woke up this morning to see that my phone had automatically downloaded the new system sfotware(i assume 4.4.2). The notification cant be removed from the notification bar and just says click to install. i dont want 4.4.2. My wife updated her s4 and it caused all sorts of minor issues with it. She was not rooted however. How can I get rid of the downloaded update and the notification? Also, is there a setting I can change so it wont try to automatically download updates in the future?
thanks
dbenney said:
I am on stock rooted MK2 with TWRP recovery installed. I woke up this morning to see that my phone had automatically downloaded the new system sfotware(i assume 4.4.2). The notification cant be removed from the notification bar and just says click to install. i dont want 4.4.2. My wife updated her s4 and it caused all sorts of minor issues with it. She was not rooted however. How can I get rid of the downloaded update and the notification? Also, is there a setting I can change so it wont try to automatically download updates in the future?
thanks
Click to expand...
Click to collapse
Im sure I will be needing the same information as I am still on 4.3 and want to stay here also, I can tell you I had the same thing with my Galaxy S2 and I remember I had to do something in Titanium backup to stop the update process, but I cant remember the exact steps.
I will be watching this thread closely, Thanks for asking the question!
Search fellas. On the notification . press and hold it. Then you should get a popup of "app info" select it and uncheck "show notification". This will get rid of the annoying update notifications. You can also delete the file from system although I am forgetting right now where.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Search fellas. On the notification . press and hold it. Then you should get a popup of "app info" select it and uncheck "show notification". This will get rid of the annoying update notifications. You can also delete the file from system although I am forgetting right now where.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Did that and deleted the file! It downloads it back and the notifications resurrects again.
I froze Configupdater, Sprint Installer, System Update
Disabled System Update on start up.
Dunno what else can stop this OTA notification!!
For me it's even more dangerous because I have the 720T running sacs for 720, hence the update that the system is trying to intsall is the NAE not NAF.
To be on safe side I'm thinking unroot and get to stock MK5 then upgrade to NAF then flash sacs again. This way the update notification will go away. Tedious but thats the only way I think I can get rid of this annoying notification.
Any thoughts?? Keep in mind I'm on 720T
frukyyy said:
Did that and deleted the file! It downloads it back and the notifications resurrects again.
I froze Configupdater, Sprint Installer, System Update
Disabled System Update on start up.
Dunno what else can stop this OTA notification!!
For me it's even more dangerous because I have the 720T running sacs for 720, hence the update that the system is trying to intsall is the NAE not NAF.
To be on safe side I'm thinking unroot and get to stock MK5 then upgrade to NAF then flash sacs again. This way the update notification will go away. Tedious but thats the only way I think I can get rid of this annoying notification.
Any thoughts?? Keep in mind I'm on 720T
Click to expand...
Click to collapse
interesting... I had recently ODIN'd back to stock and saferoot'd before calling it a day and woke up in the morning to an update. I also know that the update only downloads if you're on wi-fi. I know before I ODIN'd I was already saferoot'd with a whole bunch of crapware "frozen" by TiBackup and I never got the update. not exactly sure which crapware I froze, but I did it again this time around and I still haven't seen an update message for the past week. below is a list of what I froze... if you have the time to weed out the exact crapware needed to disable the update, please let me know! would be nice to uninstall the crapware that wont affect the update from happening while cleaning up the rest of the crapware.
1Weather
ANT HAL Service
ANT Radio Service
ANT+ Plugins
BaconReader
BlurbCheckout
Bubbles
CBS Sports
com.sec.enterprise.knox.attestation
com.sec.knox.eventsmanager
eBay
EpsonPrintService
Flipboard
Google Play Books
Google Play Games
Google Play Magazines
Google Play Movies & TV
Google Play Music
Group Play
HP Print Service Plugin
KLMS Agent
KNOX
KNOX Store
Lookout Security
Lumen Toolbar
Messaging+
Mobeam Service Application
Mobile Print
MobilePrintSvc_CUPS
MobilePrintSvc_CUPS_Backend
Phase Beam
Samsung Apps Widget
Samsung Books
Samsung Games
Samsung Hub
Samsung Music
Samsung Print Service
Samsung Video
Samsung WatchON
Samsung WatchON Video
SamsungHub Updater
Share music
Share video
Smart Device Manager
SNS
Sprint - Discover Apps
Sprint Music Plus
Sprint TV & Movies
Story Album
Story Album Widget
TalkBack
Weather Widget
Yahoo! Finance
Yahoo! News
looks like the inevitable just happened... with all the above items turned off/frozen, I still got the OTA download last night! I'm rooted with the hotspot mod and despite all of that, the OTA still came through. the update is located in /cache.
dimm0k said:
looks like the inevitable just happened... with all the above items turned off/frozen, I still got the OTA download last night! I'm rooted with the hotspot mod and despite all of that, the OTA still came through. the update is located in /cache.
Click to expand...
Click to collapse
Indeed! I gave up on OTA block. The only way I can think of if you stop all framework notifications, but I dont want to do that. Got to NAF and CF rooted. Waiting for stable KK before trying it on 720T. I don't care for sparks.
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
0Gravity said:
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
Click to expand...
Click to collapse
as I stated in my last post, the downloaded update file is located in /cache. for the time being I've deleted that file and created a zero-byte file with the same name and its permissions set to read only. not sure what's going to happen if I try to update with an empty file or if I reboot, but I have it this way to hopefukky assure me that if I accidentally press update that it won't update successfully. I doubt cleaning up the OTA downloads will prevent it from downloading again unless you can somehow fake your version number.
dimm0k said:
as I stated in my last post, the downloaded update file is located in /cache. for the time being I've deleted that file and created a zero-byte file with the same name and its permissions set to read only. not sure what's going to happen if I try to update with an empty file or if I reboot, but I have it this way to hopefukky assure me that if I accidentally press update that it won't update successfully. I doubt cleaning up the OTA downloads will prevent it from downloading again unless you can somehow fake your version number.
Click to expand...
Click to collapse
Doesn't sound like a bad idea! But I can't believe there isn't a fix for this out there though. In my research I found a file for the S2 called fota-killer, you would think something like that wild be available for the S4.
0Gravity said:
As of last night I hadn't received the OTA update yet, so I decided to try to fend it off buy freezing the system update in titanium backup... I swear I'm at 10 minutes went by and I can I receive the OTA notification! So now it looks like I'm in the same boat right next to you...lol
As I said earlier back in my S2 days I remember having to freeze the "System Update" with Titanium, but I think I also remember having to boot into recovery and Wipe a cache or something, because something is placed in the cache that looks to see if the update was downloaded and installed, and if not just keeps downloading until it is. So the steps that I do remember are;
1) Freeze system update with titanium.
2) Delete downloaded system files (I'm not sure where they are located, so please help me out with this one)
3) Boot into recovery and wipe a cache or two (I can't recall if it was one or more then one, and/or which one) so maybe someone could help with that?
I am going to do some searching for the S2 instructions to see if I can find them, maybe they will help with this.... Not sure if the update process is still the same though.
Click to expand...
Click to collapse
OK I tried the fotakill.apk method and so far I have not received the notification like I was eveytime I rebooted earlier go to here http://forum.xda-developers.com/showpost.php?p=30205683&postcount=1 for the instructions I used and a link to the file.... I used the manual method rather then installing the zip thru recovery because they said the zip method is device specific..... I'll stop back in a couple days to update how it's working or b4 that if it doesn't!
0Gravity said:
OK I tried the fotakill.apk method and so far I have not received the notification like I was eveytime I rebooted earlier go to here http://forum.xda-developers.com/showpost.php?p=30205683&postcount=1 for the instructions I used and a link to the file.... I used the manual method rather then installing the zip thru recovery because they said the zip method is device specific..... I'll stop back in a couple days to update how it's working or b4 that if it doesn't!
Click to expand...
Click to collapse
24 hours and still no update message!
OK it's been 4 or do days and this fix worked for me, we have not heard anything from the thread starter so I assume he has also fixed his, thanks for the help guys!
Ive just rebooted my fire tablet after installing some minecraft mods, when I turnt it back on it came up with a promt saying it was installing the latest software or what ever it does when doing the ota, I knew this from upgrading to 5.0.1.
is it possible it was just doing what happens when normal android optimises apps on boot. is there a app to check the installed software version as im not near my pc to unhide and go in and check what firmware im on. I put this in general as it wasnt a question but just to inform that my tablet possibly had a update despite the proper steps taken to hide the ota and updates.
Saw Same Message But No Update (whew)!
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
dubliner52 said:
For a split second I saw that same message too when first starting the Fire up. But nothing happened and nothing updated. So I think it's still blocked. Even checking for updates still fails.
So I think we're OK!
Click to expand...
Click to collapse
Have you tried unhiding to see the software version
Sent from my HTC One_M8 using Tapatalk
I didn't unhide it, but it says I'm still on 5.0.1. There was no update.
I saw the same thing but it didn't seem to update. I know the method i provided works for 5.0.0 to 5.0.1. Until there is a bump to 5.0.2 or whatever we don't know for sure if the "fix" works under 5.0.1.
Same thing happened to me but it was 3 days ago. I had been trying all day to install my adb drivers without success and switched off the device. When I restarted it immediately went into an update and I went into a panic that the new update would block the ability to access google play but immediately after the assumed "update" I successfully installed the adb drivers and google play without problem. I also checked the version and it still showed 5.0.1 so I wondered if my initial update on switching on the fire for the 1st time had somehow been unsuccessful and that had been what had been causing the inability to load the adb drivers although the tablet hadn't seemed to have any other problems and I had already downloaded and used several apps from Amazon.
I let it update upon first booting my Fire to 5.0.1. I was still successful in installing Google Playstore and hiding ads on lockscreen.
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik runtime files after rebooting when an apk is modified. nothing to do with an ota.
julianpaul said:
I'm not sure but i think that 'installing the latest software' screen is the android OS updating the dalvik files after rebooting when an apk is modified. nothing to do with an ota.
Click to expand...
Click to collapse
That is my conclusion also.
I had this happen to me also. Considering amazon patched a root method I made sure to root and nuke any chance of a future OTA unless I wanted it too. That was a cheap move, Amazon.